Universal private information interaction method and device of OMCI protocol

Abstract

The invention provides a universal private information interaction method and device of an OMCI protocol. Through application of the method and the device, in the optical access network, the attribute access type management message forwarded by the network passes through the entity identifier Entity ID field and the entity identifier Entity ID field, so that the Class ID resource consumption is reduced, the development and maintenance cost is reduced, private message interference of different manufacturers is avoided, and the safety and compatibility of a hybrid networking environment are improved; as T-L-V carrying function parameters do not need to be used, the transmission efficiency of the OMCI Baseline frame is improved, and extra overhead is reduced. The method and the device can be further applied to interaction between the FTTR master device and the slave device and interaction between the FTTR master device and the OLT device.

Description

Technical Field

[0001] This application relates to optical access networks, specifically a general-purpose private information exchange method and device based on the OMCI protocol. Background Technology

[0002] In the OMCI (Optical Management and Control Interface) management protocol, each managed entity (ME) is identified by a unique ME Class ID (Managed Entity Class Identifier) ​​to define its functional category, and a specific instance of that functional category is distinguished by an Entity ID (Entity Identifier). The ME Class ID and its attribute structure for standard functions are defined by ITU-T G.988 (the optical network management standard defined by the International Telecommunication Union). Different functional classes use different Class IDs, and the Entity ID typically corresponds to instance information such as port number and object number.

[0003] In actual deployments, when operators and equipment manufacturers extend private functions beyond the standard ME list, they often apply for a separate ME Class ID for each private function and define a corresponding fixed attribute structure. The ME Class ID and Entity ID are used to distinguish the function category and instance. Alternatively, a general ME Class ID is used, and TLV (Type-Length-Value) encoding is used in the Attribute Data (attribute data area, fixed length 30 bytes) of the class to encapsulate different private function parameter sets.

[0004] As the number of private features increases, the workload of class definition and maintenance increases significantly. The former method consumes a lot of Class ID resources and conflicts may occur between Class IDs defined by different vendors; while the latter method uses the TLV format, which brings additional overhead and significantly reduces the effective payload ratio.

[0005] The attribute access management messages in the OMCI protocol include four types: Set, Set Response, Get, and Get Response. These messages are the basic interaction methods between the OLT (Optical Line Terminal) and ONU (Optical Network Unit) for configuration distribution, execution confirmation, status query, and result return. Their transmission efficiency, space utilization, and parsing complexity directly affect the scalability of proprietary functions and cross-vendor networking compatibility.

[0006] The two existing private function extension methods mentioned above have problems such as high Class ID resource consumption, low payload ratio, bidirectional structural redundancy, insufficient parsing performance, and poor cross-vendor recognition in the OMCI attribute access class management message scenario. Summary of the Invention

[0007] The purpose of this application is to provide a general-purpose private information exchange method and device for the OMCI protocol, thereby improving the efficiency of OMCI Baseline message transmission.

[0008] To achieve the above objectives, this application provides a general-purpose private information exchange method for the OMCI protocol, applied to an optical line terminal. The method includes: setting the message type of a first attribute access class management message to a Set message or a Get message; writing a preset unified general-purpose private class identifier into the Management Entity Class Identifier (ME Class ID) field of the first attribute access class management message; writing a preset specific private function number of the unified general-purpose private class into the Entity Identifier (Entity ID) field of the first attribute access class management message; setting a vendor identifier field at the header of the Attribute Data area of ​​the first attribute access class management message to uniquely identify the device vendor to which the message belongs; setting the remaining bytes of the Attribute Data area of ​​the first attribute access class management message as a function parameter area; and sending the first attribute access class management message to the optical network unit.

[0009] To achieve the above objectives, this application provides a general-purpose private information exchange device based on the OMCI protocol, applied to an optical line terminal. The device includes a processor and a machine-readable storage medium. The machine-readable storage medium stores machine-executable instructions executed by the processor to execute the general-purpose private information exchange method based on the OMCI protocol of the optical line terminal.

[0010] To achieve the above objectives, this application also provides a general private information exchange method for the OMCI protocol, applied to an optical network unit. The method includes: parsing a first attribute access class management message received from an optical line terminal; wherein the message type is a Set message or a Get message; determining that the Management Entity Class Identifier (ME Class ID) field in the first attribute access class management message carries a preset unified general private class identifier; determining that the Entity Identifier (Entity ID) field in the first attribute access class management message carries a locally supported private function number; verifying whether the vendor identifier field of the first attribute access class management message is consistent with the local vendor identifier; if inconsistent, discarding the first attribute access class management message; if consistent and the message type of the first attribute access class management message is a Set message, performing a configuration operation according to the function parameter area of ​​the first attribute access class management message, generating a second attribute access class management message with a corresponding message type of Set response message, and transferring the attribute data. Starting from the first byte of the Data area, the configuration result field is set and the configuration execution result code is written, indicating the success or failure of the configuration execution; or, if they are consistent, the query operation is performed according to the function parameter area of ​​the first attribute access class management message with the message type of query message, generating a second attribute access class management message with the corresponding message type of query response (Get Response message). The specified length of bytes after the Attribute Data area is set as the vendor identifier field and the vendor identifier is written; the first byte after the vendor identifier field is set as the function parameter length field and the function parameter length value is written; the second byte after the vendor identifier field is set as the query identifier field and the query identifier is written; starting from the third byte after the vendor identifier field, the query result data field is set and the query result data is written; the second attribute access class management message is sent to the optical line terminal.

[0011] To achieve the above objectives, this application provides a general-purpose private information exchange device for the OMCI protocol, applied to an optical network unit. The device includes a processor and a machine-readable storage medium. The machine-readable storage medium stores machine-executable instructions executed by the processor to execute the general-purpose private information exchange method of the OMCI protocol for the optical network unit.

[0012] The beneficial effects of this application are that by using the Entity ID field and the Entity ID field, the resource consumption of Class ID is reduced, the development and maintenance costs are lowered, interference from private messages from different vendors is avoided, the security and compatibility of hybrid networking environments are improved, the transmission efficiency of OMCI Baseline messages is increased, and additional overhead is reduced. Attached Figure Description

[0013] Figure 1This application provides an embodiment of a general-purpose private information exchange method for the OMCI protocol. Figure 2 This is a schematic diagram of an interactive embodiment of the setting operation via the OMCI protocol provided in this application; Figure 3 This is a schematic diagram of an interactive embodiment of a query operation via the OMCI protocol provided in this application; Figure 4 A schematic diagram of a general-purpose private information interaction device embodiment of the OMCI protocol provided in this application; Figure 5 This is a schematic diagram of another embodiment of a general-purpose private information interaction device based on the OMCI protocol provided in this application. Detailed Implementation

[0014] The following detailed description will be provided with reference to several examples illustrated in the accompanying figures. In this detailed description, numerous specific details are used to provide a comprehensive understanding of the present application. Known methods, steps, components, and circuits are not described in detail in the examples to avoid obscuring their meaning.

[0015] In the terminology used, the term "including" means including but not limited to; the term "containing" means including but not limited to; the terms "above," "within," and "below" include the number itself; the terms "greater than" and "less than" mean not including the number itself. The term "based on" means based on at least a portion of them.

[0016] Figure 1 This application provides an embodiment of a general-purpose private information exchange method for the OMCI protocol, applied to an optical line terminal. The method includes: Step 101: Set the message type of the first attribute access class management message to either a Set message or a Get message; Step 102: Write the identifier of the preset unified general private class into the management entity class identifier ME Class ID field of the first attribute access class management message; Step 103: Write the specific private function number of the preset unified general private class into the Entity ID field of the first attribute access class management message; Step 104: Set the vendor identifier field in the header of the Attribute Data area of ​​the first attribute access class management message to uniquely identify the device vendor to which the message belongs; Step 105: Set the remaining bytes of the Attribute Data area of ​​the first attribute access class management message to the function parameter area; Step 106: Send a first attribute access class management message to the optical network unit.

[0017] Figure 1 The beneficial effects of this embodiment are that by using the Entity ID field, the consumption of Class ID resources is reduced, development and maintenance costs are lowered, interference from private messages from different vendors is avoided, and the security and compatibility of hybrid networking environments are improved. Since there is no need to use TLV to carry functional parameters, the transmission efficiency of OMCIBaseline frames is improved and additional overhead is reduced.

[0018] Figure 2 This is a schematic diagram of an interactive embodiment of the setup operation via the OMCI protocol provided in this application.

[0019] Figure 2 Taking the configuration of a MAC address blacklist by an OLT device to an ONU as an example.

[0020] OLT21 sets the message type of the OMCI message to Set message, writes the identifier 0xFF4E of the preset unified general private class in the Management Entity Class Identifier ME Class ID field, and writes 0x0001 in the Entity ID field as the number of the specific private function blacklist of the preset unified general private class.

[0021] OLT21 fixes the Attribute Mask field of the OMCI message to 0x0001. This application achieves the goal of defining only a single attribute to carry private function data by fixing the Attribute Mask to 0x0001, thus avoiding the overhead of rearranging the mask each time according to the function.

[0022] OLT21 sets a vendor identifier field in the OMCI message to carry the vendor identifier in numerical or character form, such as H3CT; each vendor identifier field is used to uniquely identify the device vendor, ensuring unique identification across vendors.

[0023] The OLT21 sets the remaining bytes of the Attribute Data area of ​​the OMCI message to the function parameter area, including: setting the first field after the vendor identifier field to a fixed-length 1-byte function parameter total length field; setting the second field after the vendor identifier field to a fixed-length 1-byte opcode field and writing "0x00 indicating the added opcode"; writing "00:11:22:33:44:55" in the remaining bytes after the opcode field, which is the MAC address of the object added to the blacklist operation; and filling any insufficient part of the Attribute Data area with padding bytes of the fixed value 00.

[0024] In this application, the OLT21 can write more than one operation object parameter in the third byte after the manufacturer identification field. The above blacklist operation object MAC address 00:11:22:33:44:55 is only used as an example and does not limit the type or number of operation object parameters.

[0025] The fields of the Set message 201 generated by OLT21 are shown in Table 1 below: Table 1 As shown in Table 1, the Set message 201 generated by OLT21 has 48 bytes, with the AttributeData area starting from the 14th byte. OLT21 sends the Set message 201 to ONU22.

[0026] ONU22 parses the Set message 201 received from the optical line terminal 21; it identifies that the ME Class ID field of the Set message 201 carries the preset unified general private class identifier 0xFF4E; the Entity ID field carries the locally supported private blacklist function number 0x0001.

[0027] The vendor identifier field of the ONU22 check Set message 201 is consistent with the local vendor identifier. The length of the function parameter length field after the vendor identifier field in the attribute data area is 8 bytes. The total length of the function parameter length field, query identifier field, and operation object parameter in the attribute data area of ​​the OMCI message is also 8 bytes.

[0028] ONU22 performs configuration operations based on the function parameter area of ​​the Set message, adding the MAC address 00:11:22:33:44:55 to the blacklist.

[0029] ONU22 generates a Set Response message 202, and writes "0x00 success" as the configuration execution result code to the configuration result field starting from the first byte of the Attribute Data area of ​​the Set Response message 22. In this application, if the ONU22 fails to perform the configuration operation, other characters written in the configuration result field indicate failure, and the insufficient part of the Attribute Data area is filled with padding bytes of the fixed value 00.

[0030] The Set Response message 202 generated by ONU22 is shown in Table 2 below. Table 2 OLT21 receives Set Response message 202 from ONU22, parses the Transaction ID, Device ID, ME Class ID, and Entity ID in Set Response message 202 to correspond to Set message 201 and its managed entity object, parses the execution result code "Configuration successful" in the Attribute Data area of ​​Set Response message 202, and updates the configuration status of the blacklist corresponding to Entity ID field 0x0001 to "Configuration successful".

[0031] Figure 3 This is a schematic diagram of an interactive embodiment of a query operation via the OMCI protocol provided in this application.

[0032] Figure 3 Taking the OLT21 device querying the MAC address blacklist from the ONU22 as an example.

[0033] OLT21 sets the message type of the OMCI message to a Set Get message, writes the identifier 0xFF4E of the preset unified general private class in the ME Class ID field, and writes 0x0001 in the Entity ID field as the number of the specific private function blacklist of the preset unified general private class.

[0034] OLT21 fixes the Attribute Mask field of OMCI messages to 0x0001.

[0035] OLT21 sets a vendor identifier field in the OMCI message to carry the vendor identifier H3CT.

[0036] OLT21 fills the remaining bytes in the Attribute Data area with fixed-value 00 bytes and generates a Get message 301, as shown in Table 3 below.

[0037] Table 3 OLT21 sends a Get message 301 to ONU22.

[0038] ONU22 parses the Get message 301 received from the optical line terminal 21; it identifies that the ME Class ID field of the Get message 301 carries a preset unified general private class identifier 0xFF4E; and the Entity ID field carries the local supported private blacklist function number 0x0001.

[0039] If the vendor identifier field of the ONU22 verification Get message 301 matches the local vendor identifier, then a query operation is performed on the MAC address blacklist.

[0040] In one example, the query result of ONU22 to look up the MAC address blacklist was that the blacklist recorded 5 MAC addresses.

[0041] ONU22 generates the corresponding Get Response message 302, sets the first field of the Attribute Data area to the vendor identifier field and writes the vendor identifier H3CT, and sets the second field of the Attribute Data area to the function parameter length field to record the function parameter length value, such as 8 bytes.

[0042] The ONU queries the identifier field in the second field of the Attribute Data area and writes the query identifier 0x02; it sets the query result data field starting from the 3rd byte after the vendor identifier field and writes the query result data 0x0005 to indicate that the data in the MAC address blacklist is 5. It fills the insufficient part of the Attribute Data area with padding bytes of the fixed value 00.

[0043] The Get Response 302 message generated by ONU22 is shown in Table 4 below: Table 4 ONU22 sends a Get Response message 302 to OLT21.

[0044] OLT22 parses the Transaction ID, Device ID, ME Class ID, and Entity ID of the Get Response 302 message to determine the Get Response 301 message corresponding to the Get Response 302 message and the MAC address blacklist of the managed entity object.

[0045] OLT22 parses the vendor identifier H3CT set in the header of the Attribute Data area of ​​Get Response message 302, confirms its consistency, and parses the length of the function parameter length field after the vendor identifier field in the Attribute Data area of ​​Get Response message 302. The length of the function parameter length field, the representation field, and the training result data field are all 4 bytes. If the total length is equal to 4 bytes, then continue parsing the query identifier field 0X02 in the Attribute Data area of ​​Get Response message 302. The query result data field in the Attribute Data area of ​​Get Response message 302 contains 5 records. The query result data updated to the MAC address blacklist corresponding to the ME Class ID field and the Entity ID field also contains 5 records.

[0046] In the above embodiments, the unified general private ME Class ID value is only an example, and the use of Entity ID0x0001 to represent the private function MAC address blacklist is also only an example and can be set according to specific business scenarios. In the above embodiments, the Attribute Data area of ​​the Set message, Set Response (message), Get message, and Get Response message of the attribute access class management message adopts a fixed field layout to reduce the CPU parsing overhead of the ONU caused by the type / length of TLV encoding.

[0047] Figure 4 This is a schematic diagram of an embodiment of a generic private information exchange device for the OMCI protocol provided in this application. The device 40 is applied to an optical line terminal and includes a processor 41 and a machine-readable storage medium 42. The machine-readable storage medium 42 stores machine-executable instructions executed by the processor 41.

[0048] Processor 41 executes the instruction to perform the following operations: setting the message type of the first attribute access class management message to a Set message or a Get message; writing a preset unified general private class identifier into the MEClass ID field of the first attribute access class management message; writing the preset specific private function number of the unified general private class into the Entity ID field of the first attribute access class management message; setting a vendor identifier field in the header of the Attribute Data area of ​​the first attribute access class management message to uniquely identify the device vendor to which the message belongs; setting the remaining bytes of the Attribute Data area of ​​the first attribute access class management message to the function parameter area; and sending the first attribute access class management message to the optical network unit.

[0049] Processor 41 also performs the following operations by executing this instruction: the Attribute Mask field of the first attribute access class management message is fixed to 0x0001; the vendor identifier field includes numerical values ​​or characters used to represent the vendor's English abbreviation.

[0050] Processor 41, by executing the instruction, also performs the following operations: setting the remaining bytes of the Attribute Data area of ​​a first attribute access class management message to the function parameter area, including: in the function parameter area of ​​a first attribute access class management message whose message type is set to Set message, setting the first field after the vendor identifier field as the total length of function parameters field, setting the second field after the vendor identifier field as the opcode field, writing the remaining bytes of the Attribute Data area to one or more operation object parameters and filling any insufficient parts with fixed-value padding bytes, and writing the total number of bytes calculated from the total length of function parameters field, the opcode field, and the number of bytes of operation object parameters into the total length of function parameters field; or in the function parameter area of ​​a first attribute access class management message whose message type is set to Get message, filling the bytes after the vendor identifier field with fixed-value padding bytes.

[0051] Processor 41, by executing this instruction, also performs the following operations: receiving a second attribute access class management message from the optical network unit; wherein the message type is a Set Response message or a Get Response message; parsing the Transaction ID, Device ID, ME Class ID, and Entity ID in the second attribute access class management message to determine the first attribute access class management message and its management entity object corresponding to the second attribute access class management message; parsing the execution result code of the attribute data area of ​​the second attribute access class management message with the message type of Set Response message, and updating it to the configuration status of the management entity object corresponding to the Entity ID field of the second attribute access class management message; or, parsing the header setting vendor identifier field of the attribute data area of ​​the second attribute access class management message with the message type of Get Response message, confirming consistency, and parsing the attribute data of the second attribute access class management message. The length value of the first byte of the Functional Parameter Length field after the Manufacturer Identifier field in the header of the Data area is parsed; the query identifier of the second byte of the Query Identifier field after the Manufacturer Identifier field in the header of the AttributeData area of ​​the Second Attribute Access Class Management Message is parsed; the query result data field of the third byte after the Manufacturer Identifier field in the header of the Attribute Data area of ​​the Second Attribute Access Class Management Message is parsed; it is determined that the length value is equal to the total length of the Functional Parameter Length field, the Query Functional Parameter Length field, the Query Identifier field, and the Query Result Data field, and the query result data field is updated to the query result data of the management entity object corresponding to the ME Class ID field and the Entity ID field of the Second Attribute Access Class Management Message.

[0052] Figure 5 This is a schematic diagram of another embodiment of a generic private information exchange device using the OMCI protocol provided in this application. The device 50 is applied to an optical network unit and includes a processor 51 and a machine-readable storage medium 52. The machine-readable storage medium 52 stores machine-executable instructions executed by the processor 51.

[0053] Processor 51 executes the instruction to perform the following operations: parses a first attribute access class management message received from the optical line terminal; wherein the message type is either a Set message or a Get message; determines that the Management Entity Class Identifier (ME Class ID) field in the first attribute access class management message carries a preset unified general private class identifier; determines that the Entity Identifier (Entity ID) field in the first attribute access class management message carries a locally supported private function number; verifies whether the vendor identifier field of the first attribute access class management message is consistent with the local vendor identifier; if inconsistent, discards the first attribute access class management message; if consistent and the message type of the first attribute access class management message is a Set message, performs a configuration operation according to the function parameter area of ​​the first attribute access class management message, generates a second attribute access class management message with the corresponding message type of a Set response message, sets the first byte of the Attribute Data area to the configuration result field and writes the configuration execution result code, indicating the success or failure of the configuration execution; or, if consistent, performs a query operation according to the function parameter area of ​​the first attribute access class management message with the message type of a Query message, generates a corresponding Query Response Get message. The second attribute access management message of the Response message sets the specified length of bytes after the Attribute Data area as the vendor identifier field and writes the vendor identifier; sets the function parameter length field and writes the function parameter length value in the first byte after the vendor identifier field; sets the query identifier field and writes the query identifier in the second byte after the vendor identifier field; sets the query result data field and writes the query result data starting from the third byte after the vendor identifier field; and sends the second attribute access management message to the optical line terminal.

[0054] Processor 51 executes this instruction to perform the following operation: fill the remaining bytes in the Attribute Data area of ​​the second attribute access class management message of message type Set Response with a preset invalid value, excluding the configuration result field.

[0055] Before executing the configuration operation based on the function parameter area of ​​the first attribute access class management message by executing the instruction, the processor 51 also performs the following operations: parses the length value of the function parameter length field of the first byte after the vendor identifier field in the attribute data area of ​​the first attribute access class management message of message type Set; checks the total length of the function parameter length field, the query identifier field, and the operation object parameter in the attribute data area of ​​the first attribute access class management message, and finds that it is equal to the length value of the function parameter length field of the first byte after the vendor identifier field in the attribute data area of ​​the first attribute access class management message.

[0056] The processor 51 executes the instruction to perform the following operations: fill the query result data field in the Attribute Data of the second attribute access management message of the message type Get Response and write it into the query result data message of the second attribute access management message of the message type Get Response. The first byte of the Attribute Data field is set to the total length of the returned data field, the second byte is the query operation code field, the remaining bytes are written to the returned parameter values ​​in the preset order corresponding to the function number, and the remaining unused byte positions are filled with preset invalid values.

[0057] In this disclosure, a machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device used to store or contain information (such as executable instructions, data, etc.). For example, any machine-readable storage medium described herein can be any type of random access memory (RAM), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard disk drive), solid-state drive, any type of optical disc (such as an optical disc, DVD, etc.), and similar devices, or combinations thereof. Furthermore, any machine-readable storage medium described herein can be a non-transitory machine-readable storage medium.

[0058] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A general-purpose private information exchange method for the OMCI protocol, applied to optical line terminals, characterized in that, The method includes, Set the message type of the first attribute access class management message to either a Set message or a Get message; Write the identifier of the preset unified general private class into the ME Class ID field of the management entity class identifier in the first attribute access class management message; Write the specific private function number of the preset unified general private class into the Entity ID field of the first attribute access class management message; A vendor identifier field is set in the header of the Attribute Data area of ​​the first attribute access class management message to uniquely identify the device vendor to which the message belongs; Set the remaining bytes of the Attribute Data area in the first attribute access class management message to the function parameter area; Send the first attribute access class management message to the optical network unit.

2. The method according to claim 1, characterized in that, The Attribute Mask field of the first attribute access class management message is fixed at 0x0001; The manufacturer identification field includes numerical values ​​or characters used to represent the manufacturer's English abbreviation.

3. The method according to claim 1, characterized in that, Setting the remaining bytes of the Attribute Data area in the first attribute access class management message to the function parameter area includes: In the function parameter area of ​​the first attribute access class management message whose message type is set to the Set message, the first field after the vendor identifier field is set as the total length of function parameters field, the second field after the vendor identifier field is set as the opcode field, the remaining bytes in the Attribute Data area are written to one or more operation object parameters and the insufficient part is filled with padding bytes of a fixed value, and the total number of bytes calculated from the total length of function parameters field, the opcode field, and the number of bytes of operation object parameters is written to the total length of function parameters field; or In the function parameter area of ​​the first attribute access class management message whose message type is set to the Get message, the bytes following the vendor identifier field are filled with a fixed value of padding bytes.

4. The method according to claim 1, characterized in that, The method also includes, Receive a second attribute access class management message from the optical network unit; The message type is either a SetResponse message or a GetResponse message; Parse the Transaction ID, Device ID, ME Class ID, and Entity ID in the second attribute access class management message to determine the first attribute access class management message and its management entity object corresponding to the second attribute access class management message. Parse the execution result code of the Attribute Data area of ​​the second attribute access class management message with the message type of the Set Response message, and update the configuration status of the management entity object corresponding to the EntityID field of the second attribute access class management message; or, Parse the header of the vendor identifier field in the AttributeData area of ​​the second attribute access class management message, which is of the Get Response message type. Confirm that it matches. Parse the length value of the first byte of the Function Parameter Length field after the vendor identifier field in the header of the Attribute Data area of ​​the second attribute access class management message. Parse the query identifier of the second byte of the Query Identifier field after the vendor identifier field in the header of the Attribute Data area of ​​the second attribute access class management message. Parse the third byte of the Query Result Data field after the vendor identifier field in the header of the Attribute Data area of ​​the second attribute access class management message. Determine that the length value is equal to the total length of the Function Parameter Length field, the Query Function Parameter Length field, the Query Identifier field, and the Query Result Data field. Update the query result data of the Query Result Data field to the query result data of the management entity object corresponding to the ME Class ID field and the Entity ID field in the second attribute access class management message.

5. A general-purpose proprietary information exchange device based on the OMCI protocol, applied to an optical line terminal, characterized in that, The device includes a processor and a machine-readable storage medium; the machine-readable storage medium stores machine-executable instructions executed by the processor to perform a general-class private information exchange method of the OMCI protocol according to any one of claims 1-4.

6. A general-purpose private information exchange method for the OMCI protocol, applied to an optical network unit, characterized in that, The method includes, Parse the first attribute access management message received from the optical line terminal; the message type is either a Set message or a Get message. It is determined that in the first attribute access class management message, the management entity class identifier ME Class ID field carries a preset unified general private class identifier; The first attribute access class management message is identified, and the Entity ID field carries the locally supported private function number; Verify whether the vendor identifier field of the first attribute access management message is consistent with the local vendor identifier; If they are inconsistent, the first attribute access class management message is discarded; If they match and the message type of the first attribute access management message is a setting message, perform a configuration operation according to the function parameter area of ​​the first attribute access management message, generate a second attribute access management message with the corresponding message type of a setting response message, set the first byte of the attribute data area as the configuration result field and write the configuration execution result code to indicate the success or failure of the configuration execution; or... If they match, perform a query operation based on the function parameter area of ​​the first attribute access management message with the message type of query message, and generate a second attribute access management message with the corresponding message type of query response (Get Response message). Set the specified length of bytes after the Attribute Data area as the vendor identifier field and write the vendor identifier; set the function parameter length field after the first byte after the vendor identifier field and write the function parameter length value; set the query identifier field after the second byte after the vendor identifier field and write the query identifier; set the query result data field starting from the third byte after the vendor identifier field and write the query result data. The second attribute access class management message is sent to the optical line terminal.

7. The method according to claim 6, characterized in that, In the second attribute access management message of the message type Set Response, the remaining bytes other than the configuration result field of the Attribute Data area are filled with preset invalid values.

8. The method according to claim 6, characterized in that, Before performing the configuration operation based on the function parameter area of ​​the first attribute access class management message, the method further includes, The parsing message type is the first attribute access class management message of the Set message. The length value of the first byte of the function parameter length field after the vendor identifier field in the attribute data area is equal to the length value of the first byte of the function parameter length field after the vendor identifier field in the attribute data area of ​​the first attribute access class management message. The total length of the function parameter length field, query identifier field and operation object parameter in the attribute data area of ​​the first attribute access class management message is checked.

9. The method according to claim 6, characterized in that, The method also includes, In the AttributeData field of the second attribute access management message of the message type Get Response, the query result data field is filled and written into the query result data of the second attribute access management message of the message type Get Response. The first byte of the Attribute Data field is set to the total length of the returned data field, the second byte is the query operation code field, and the remaining bytes are written to the returned parameter values ​​in a preset order corresponding to the function number. The remaining unused byte positions are filled with preset invalid values.

10. A general-purpose proprietary information exchange device based on the OMCI protocol, applied to an optical network unit, characterized in that, The device includes a processor and a machine-readable storage medium; the machine-readable storage medium stores machine-executable instructions executed by the processor to perform a general-class private information exchange method of the OMCI protocol according to any one of claims 6-9.

Images