Method for implementing an omci management instance based on a configuration document

Abstract

The present application relates to a method for implementing an OMCI management instance based on a configuration document. The method is constructed on a passive optical fiber network. The passive optical fiber network includes an ONU and an OLT. The OLT creates a management entity in the ONU by using an OMCI protocol as a management protocol. The method includes: executing computer software for the ONU to start an OMCI process; and checking, by the computer software, whether a configuration document exists under a specific system path of the ONU; if the configuration document exists, loading the configuration document by the computer software, and configuring the management entity according to the configuration document.

Description

Technical Field

[0001] This invention relates to the field of fiber optic access network technology, and in particular to a method for implementing OMCI management based on a configuration file. Background Technology

[0002] Gigabit-capable Passive Optical Network (GPON) is an emerging standard that provides users with faster data services, typically including the Internet, telephone, or television broadcasting.

[0003] Figure 1 This diagram shows a typical passive optical fiber network 100.

[0004] The passive optical network 100 includes multiple optical network units (ONUs), such as 101-1 to 101-3, which are connected to an optical line termination (OLT) 103 via a passive optical splitter 102. Downlink data is broadcast from the OLT 103 to all ONUs 101, and each ONU 101 filters out the data it needs. The OLT 103 allocates different time intervals to each ONU 101, and each ONU 101 sends its own uplink data to the OLT 103 within its allocated time interval. The passive optical splitter 102 splits a single line into multiple lines.

[0005] The management of the ONU 101, including configuration management, fault management, performance management, and security management, is implemented through the management module of the OLT103's Optical Network Unit Management and Control Interface (OMCI). To address various complex network application problems, the OMCI protocol, as defined in Section 11.2.4 of the G.988 protocol, supports over four hundred management instances. However, for commonly used service configurations, only a few dozen management instances are actually needed.

[0006] After connecting to the OLT 103, the ONU 101 must first complete access authentication, including discovery, authentication, and registration. However, due to inconsistencies in the understanding of standards among different vendors when developing the OMCI management modules for their OLTs, compatibility issues frequently arise when ONUs connect to OLTs developed by different vendors. In fact, during the registration and service configuration scenarios between the ONU 101 and the OLT 103, the OLT 103 often requires the ONU 101 to support certain undeveloped management instances, or, even if implemented management instances exist, further modifications to certain attribute values ​​are still required.

[0007] In detail, for situations where support for certain undeveloped management instances is required, the common practice is to modify the software, recompile the code to generate firmware, and then upgrade the firmware to the singleboard. However, modifying the software inevitably takes more time, thus increasing the development cycle.

[0008] Regarding the situation where "it is necessary to further modify certain attribute values ​​in the implemented management instances," the common practice is to achieve this by modifying the software (especially the software parameters) or by modifying the attribute values ​​via commands. However, modifying attribute values ​​via commands often cannot cover all management instances and attribute values. In fact, modifying certain attribute values ​​often involves engineering projects such as modifying code, compiling firmware, and upgrading firmware, which requires continuous attempts until access certification is achieved, making it extremely inefficient.

[0009] Therefore, there is an urgent need to propose a more efficient method for OMCI management in order to eliminate or mitigate the above problems. Summary of the Invention

[0010] In view of this, the present invention is a method for implementing OMCI management instances based on "configuration documents," thereby significantly improving the efficiency of solving OMCI interaction problems. Here, in the field of computer technology, a configuration document, also known as a "configuration file," is a computer file that configures parameters and initial settings for certain computer programs. In this invention, the configuration document enables "batch initialization of parameters" and "batch addition and removal of OMCI management instances."

[0011] Regarding batch parameter initialization, because the configuration document has a fixed format, one or more parameters of one or more OMCI-managed instances can be specified and reinitialized, allowing users to flexibly select and modify parameters according to their own needs. The parameters can be manually entered by the user or generated using a script to meet different scenario requirements. Furthermore, generating configuration documents based on others' data can also be considered, allowing for comparison of the differences between configuration documents generated from one's own data and those generated from others' data.

[0012] Regarding the batch addition and removal of OMCI management instances, because the configuration document has a fixed format, unsupported OMCI management instances can be added in batches. These added OMCI management instances can interact normally, but they do not implement the specific functions of OMCI management instances. Similarly, because the configuration document has a fixed format, it is easy to specify and delete one or more supported OMCI management instances, which helps to free up storage or computing resources. Furthermore, some OLTs have limited capabilities. When the ONU's reporting capacity exceeds the OLT's receiving capacity, these OLTs may force the ONU to fail authentication. In this case, it is necessary to delete some OMCI management instances.

[0013] In view of this, according to one aspect of the present invention, a method for implementing OMCI management instances based on configuration documents is proposed. The method is characterized by being built on a passive optical fiber network, the passive optical fiber network including an ONU and an OLT, wherein the OLT uses the OMCI protocol as the management protocol to create a management entity in the ONU. The method includes: executing computer software on the ONU to start the OMCI process; and checking, through the computer software, whether a configuration document exists in a specific system path of the ONU; if the configuration document exists, loading the configuration document through the computer software, and configuring the management entity according to the configuration document.

[0014] Optionally, or preferably, configuring the management entity according to the configuration document includes modifying parameters of one or more supported OMCI management instances within the management entity.

[0015] Optionally, or preferably, configuring the management entity according to the configuration document includes adding one or more unsupported OMCI management instances to the management entity, or deleting one or more supported OMCI management instances from the management entity.

[0016] Optionally, or preferably, the configuration document is in TXT format.

[0017] Optionally, or preferably, the configuration document comprises multiple lines, each line describing a management instance, or multiple attributes of a management instance are described across multiple lines.

[0018] Optionally, or preferably, the configuration document describes the attributes of the OMCI management instance as defined in accordance with the G.988 protocol, including classId, instanceId, attrMask, or attrVal.

[0019] Optionally, or preferably, the method of the present invention further includes generating the configuration document via a script.

[0020] Optionally, or preferably, generating the configuration document via script includes selecting a data analysis mode.

[0021] Optionally, or preferably, generating the configuration document via a script includes: capturing an authenticated OMCI message from another ONU and loading the authenticated OMCI message into the script.

[0022] Optionally, or preferably, programming tools are used to analyze and organize the captured certified OMCI messages, thereby generating the configuration document through the script.

[0023] Optionally, or preferably, the configuration document is generated based on data from a third party.

[0024] Optionally, or preferably, the configuration document can be uploaded to the system path of the ONU using the computer software via tftp / ftp.

[0025] Optionally, or preferably, if the configuration document does not exist, the management entity will be configured using an OMCI management instance with default initial values.

[0026] Optionally, or more preferably, the method of the present invention further includes: after configuring the management entity, uploading the management information database to the OLT.

[0027] Optionally, or preferably, the method of the present invention further includes: after configuring the management entity, starting to receive OMCI operations from the OLT, the OMCI operations including SET, GET, CREATE, or DELETE.

[0028] Optionally, or preferably, the method of the present invention further includes: after receiving an OMCI interaction message, checking whether the OMCI management instance involved in the OMCI interaction message has been supported; if the OMCI management instance has been supported, then normal processing is performed according to the original logic of the ONU; if the OMCI management instance has not been supported, then the configuration document replies with the result.

[0029] Other objects, advantages, and novel features of the present invention will become more apparent from the following detailed description in conjunction with the accompanying drawings. Attached Figure Description

[0030] Figure 1 This diagram shows a typical passive optical fiber network.

[0031] Figure 2 This shows an example of a configuration document for one embodiment of the present invention.

[0032] Figure 3 This diagram shows a flowchart of an embodiment of the present invention for implementing OMCI management instances based on configuration documents.

[0033] Figure 4 This diagram illustrates a flowchart of generating a configuration document according to an embodiment of the present invention.

[0034] In the picture,

[0035] 100 Passive Fiber Networks

[0036] Optical Network Units (ONUs) 101, 101-1, 101-2, 101-3

[0037] 102 Passive Optical Splitter

[0038] 103 Optical Line Terminal (OLT). Detailed Implementation

[0039] The following provides different embodiments of the present invention. These embodiments are used to illustrate the technical content of the present invention and are not intended to limit the scope of the invention. A feature of one embodiment can be applied to other embodiments through suitable modifications, substitutions, combinations, or separations.

[0040] It should be noted that, unless otherwise specified, the term "one" in this document is not limited to having a single element, but may include one or more of the elements.

[0041] Furthermore, unless otherwise specified, the ordinal numbers such as "first," "second," etc., used herein are merely for distinguishing multiple elements with the same name and do not indicate any hierarchy, order of execution, or process sequence among them. A "first" element and a "second" element may appear together in the same component or separately in different components. The presence of an element with a higher ordinal number does not necessarily indicate the presence of another element with a lower ordinal number.

[0042] In this document, unless otherwise specified, the term "characteristic A" or "and / or" and "characteristic B" means that A exists alone, B exists alone, or A and B exist simultaneously; the term "characteristic A" and "and" or "and" and "and" and "characteristic B" means that A and B exist simultaneously; the terms "including", "containing", "having", and "containing" mean, but are not limited to, these.

[0043] Furthermore, in this document, "preferred" or "more preferred" is used to describe optional or additional elements or features, that is, elements or features that are not necessary and may be omitted.

[0044] Furthermore, unless otherwise specified herein, the term "suitable" or "appropriate" for one element means that the other element is not part of the subject matter of the application but is exemplary or referentially helpful in conceiving the nature or application of the element; similarly, unless otherwise specified herein, the term "suitable" or "appropriate" for one element means that the element is characterized by a configuration or an action, and does not imply that the configuration has been set or the action has been performed.

[0045] Furthermore, unless otherwise specified herein, the electrical connection between two components may include a direct connection or an indirect connection. In an indirect connection, one or more other components, such as resistors, capacitors, or inductors, may be present between the two components. An electrical connection is used to transmit one or more signals, such as DC or AC current or voltage, depending on the specific application.

[0046] Furthermore, either the terminal or the server may include the aforementioned components or be implemented in the manner described above.

[0047] The method of implementing OMCI management instances based on configuration documents in this invention is built on a GPON network. The GPON network includes one or more ONUs connected to an OLT. The OLT uses the OMCI protocol as the management protocol to create a management entity (ME) in the ONU. The management entity includes one or more supported OMCI management instances. The ONU can report its capabilities, thereby informing the OLT how to control the ONU. The specific execution logic of the OLT is controlled by the OLT itself.

[0048] Next, the computer software developed according to this invention is executed. This computer software can modify the contents of the one or more supported OMCI management instances in the ONU, for example, attribute values ​​and their initial values. Furthermore, the computer software can also add one or more unsupported OMCI management instances to the management entity in the ONU, or delete one or more supported OMCI management instances from the management entity.

[0049] In particular, according to the present invention, the computer software can import configuration documents, such as TXT format configuration documents, to perform the above-mentioned modifications, additions, or deletions.

[0050] Figure 2 This shows an example of a configuration document for one embodiment of the present invention.

[0051] like Figure 2As shown, the configuration document describes multiple OMCI management instances in multiple rows. However, in addition to describing one OMCI management instance per row, in other embodiments, multiple attributes of a management instance can also be described across multiple rows, meaning one management instance occupies multiple rows.

[0052] Figure 2 The configuration document's header displays multiple OMCI parameters or attributes, including: tableMask indicates the use of a bit mask to specify which fields in the configuration document are used, such as privateME, index, and InstantId; privateME indicates whether the data in this row is a private management instance, which is reserved by G.988 for user-defined instances; index is used to count the number of rows; classId, InstantId, attrMask, and attrVal are understood in accordance with the G.988 protocol specification and will not be elaborated here; attrLenStr is used to extend OMCI, specifying the length of the attribute value; encrypted indicates whether the attrVal in the TXT document is encrypted, but is not limited to this, and more OMCI parameters can be introduced depending on the actual application requirements; and according to this invention, when new protocols are introduced in the future, the configuration document of this invention can easily introduce more OMCI parameters.

[0053] The configuration documentation is formatted to partially or fully conform to the definitions listed in the G.988 protocol. Figure 2 In the example, parameters such as classId, instanceId, attrMask, and attrVal are defined according to the G.988 protocol, while other parameters are user-defined. Therefore, because the configuration document has a fixed format, as long as the content is entered according to this fixed format, the computer software can batch process the initialization of OMCI parameters or batch add / remove OMCI management instances based on the configuration document. Furthermore, given the convenience of the TXT format, the configuration document can be generated using a script. Commonly used scripting tools include Python and Shell, and the specific steps will be explained in detail below. This avoids the labor, time, and potential for errors associated with manual input. Even further, it is possible to generate the configuration document based on third-party data. This allows for comparison of the differences between configuration documents generated from one's own data and those generated from third-party data.

[0054] The method of this invention can quickly implement the required OMCI management instance, significantly improve the efficiency of OMCI interaction issues, and avoid lengthening the software development cycle.

[0055] Figure 3This diagram shows a flowchart of a method for implementing OMCI management instances based on a configuration document, according to an embodiment of the present invention.

[0056] The method for implementing OMCI management instances based on configuration documents according to the present invention begins in step S11: executing computer software on the ONU to start the OMCI process and enter the OMCI process initialization process. As mentioned above, the OLT and ONT exchange information through the OMCI protocol.

[0057] After the OMCI process starts in step S11, a judgment step T11 is executed: check if a configuration document exists in a specific system path of the ONU? If a configuration document exists (judged as "yes"), then step S12 is executed: load the configuration document to perform the initialization process. The configuration document is provided through an additional step S10: generating a configuration document in a specific format, as detailed in [link to details]. Figure 4 The relevant instructions are as follows. Conversely, if no configuration document exists (determined as "No"), the required OMCI management instance attribute values ​​will use the default initial values, and the process will skip directly to step S15: receiving OMCI operations from the OLT.

[0058] After step S12, step S13 is executed: according to the relevant fields of the configuration document, the OMCI management entity is re-initialized. The initialization process mainly includes adding or deleting OMCI management instances. For example, adding a private management instance of China Telecom to obtain Logic ID (LOID) authentication to meet China Telecom's authentication requirements; or modifying the attribute values ​​of supported OMCI management instances, such as the Vendor ID, Version, serial number, and other attribute values ​​in ONU-G of management instance 9.1.1.

[0059] Next, step S14 is executed: the Management Information Base (MIB) is uploaded to the OLT. The MIB is the set of ONU capabilities reported by the ONU. Before reporting the MIB, the OLT will ask the ONU whether it has already reported the MIB. If it has, the ONU does not need to report it again. However, it can also be configured so that even if it has already been reported, the ONU still needs to report it again.

[0060] Then, step S15 is executed: Start receiving OMCI operations from the OLT, such as SET, GET, CREATE, or DELETE operations.

[0061] During the OMCI process interaction, upon receiving an OMCI interaction message, step T12 is executed: Checking whether the OMCI management instance involved in the OMCI interaction message supports it. If the OMCI management instance supports it (determined as "yes"), step S16 is executed: Normal handling is performed according to the ONU's existing logic. Normal handling primarily involves converting OMCI operations such as setting, obtaining, creating, or deleting issued by the OLT into ONU-local execution logic, and converting the data issued by the OLT into ONU-local data structures, processing this data according to the ONU's local execution logic. Conversely, if the OMCI management instance does not support it (determined as "no"), step S17 is executed: The configuration document provides the result.

[0062] Figure 4 This diagram illustrates a flowchart of generating a configuration document according to an embodiment of the present invention.

[0063] The method for generating configuration documents according to the present invention begins with step S21: running a programming tool script. The programming tool is, for example, Python, but other software may also be used.

[0064] Next, proceed to step S22: Select the data analysis mode.

[0065] Meanwhile, in step S20, the analyzer captures the OMCI message from another ONU that has successfully registered and authenticated. Then, the OMCI message is loaded into the programming tool script.

[0066] Subsequently, step S23 is executed: the captured OMCI messages are analyzed and organized using programming tools, thereby generating a configuration document in a specific format through the script.

[0067] Next, proceed to step S24: Modify the configuration document according to the actual needs of the specific use case. In particular, users must, based on experience, select OMCI management instances with significant differences, reinitialize the supported OMCI management instances, or add or remove OMCI management instances.

[0068] Next, step S25 is executed: the configuration document is provided to the ONU board. For example, the configuration document in TXT format exists in flash memory and can be uploaded to a specific system path of the ONU using TFTP / FTP.

[0069] Next, proceed to step S26: attempt to register with the OLT via the configuration document. This step corresponds to... Figure 3 Step S10, specifically, after Figure 4The configuration document generated from this series of steps will participate Figure 3 This method uses a configuration document to manage instances via OMCI. However, if the current configuration document fails to register with the OLT, step S24 must be executed again to manually modify the configuration document.

[0070] Although the invention has been described through various embodiments, it should be understood that many other possible modifications and variations may be made without departing from the spirit of the invention and the claims.

Claims

1. A method for implementing management instances of the Optical Network Unit Management and Control Interface (OMCI) based on configuration documents, characterized in that, The method is built on a passive optical fiber network, which includes optical network units (ONUs) and optical line terminals (OLTs). The OLT uses the OMCI protocol as the management protocol to create a management entity in the ONU. The method includes: Execute computer software on the ONU to start the OMCI process; The computer software checks whether a configuration document exists under a specific system path on the ONU; if the configuration document exists, the computer software loads the configuration document and configures the management entity according to the configuration document; and The method further includes: after receiving an OMCI interaction message, checking whether the OMCI management instance involved in the OMCI interaction message has supported it; if the OMCI management instance has supported it, then processing it normally according to the original logic of the ONU; if the OMCI management instance does not support it, then the configuration document will reply with the result.

2. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, Configuring the management entity according to the configuration document includes modifying parameters of one or more supported OMCI management instances within the management entity.

3. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, Configuring the management entity according to the configuration document includes adding one or more unsupported OMCI management instances to the management entity, or deleting one or more supported OMCI management instances from the management entity.

4. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, The configuration document is in TXT format.

5. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, The configuration document comprises multiple lines, arranged such that each line describes a management instance, or multiple attributes of a management instance are described across multiple lines.

6. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, The configuration document describes the attributes of the OMCI management instance as defined according to the G.988 protocol, including classId, instanceId, attrMask, or attrVal.

7. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, Also includes: The configuration document is generated using a script.

8. The method for implementing OMCI management instances based on configuration documents as described in claim 7, characterized in that, The process of generating the configuration document via script includes: selecting a data analysis mode.

9. The method for implementing OMCI management instances based on configuration documents as described in claim 7, characterized in that, The step of generating the configuration document via script includes: capturing the authenticated OMCI message of another ONU and loading the authenticated OMCI message into the script.

10. The method for implementing OMCI management instances based on configuration documents as described in claim 9, characterized in that, The captured certified OMCI messages are analyzed and organized using programming tools, and the configuration document is generated through the script.

11. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, The configuration document was generated based on data from a third party.

12. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, The configuration document is uploaded to the system path of the ONU using the computer software via TFTP / FTP.

13. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, If the configuration document does not exist, the management entity will be configured using an OMCI management instance with default initial values.

14. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, Also includes: After configuring the management entity, the management information database is uploaded to the OLT.

15. The method for implementing OMCI management instances based on configuration documents as described in claim 1, characterized in that, Also includes: After configuring the management entity, it begins to receive OMCI operations from the OLT, including SET, GET, CREATE, or DELETE operations.

Images