Communication method and apparatus in a passive optical network and computer readable medium

Abstract

The present application relates to a communication method and device in a passive optical network and a computer readable medium. According to an embodiment, a communication method implemented at an optical network unit can include receiving an optical network unit management and control interface (OMCI) message from an optical line terminal, the OMCI message including configuration information of a synchronization status message incoming (SSM-IN) managed entity, receiving synchronization status information from the optical line terminal, and processing the received synchronization status information according to the configuration of the SSM-IN managed entity.

Description

Technical Field

[0001] This application relates generally to the field of communications, and more particularly to communication methods and apparatus for use in passive optical networks, as well as computer-readable media. Background Technology

[0002] This section serves to provide background or context for the exemplary embodiments disclosed below. The description herein may include concepts that can be traced, but are not necessarily concepts that have been previously conceived, implemented, or described. Therefore, unless expressly stated otherwise herein, the description in this section is not intended to be prior art as described in this application, nor is it acknowledged as prior art simply because it is included in this section.

[0003] Synchronous Ethernet (SyncE) is a technology that uses Ethernet link streams to recover the clock. Synchronous Ethernet utilizes Ethernet physical layer chips to insert additional clock information bits into the transmitted data stream at the transmitting end, and recovers the transmitting end's clock information at the receiving end, thus achieving the required synchronization at the physical layer. At this time, the clock quality at the receiving end is the same as the clock at the transmitting end. The transmitting end also provides a Synchronization Status Message (SSM) indicating the clock quality level to the receiving end, allowing the receiving end to have the ability to trace the optimal clock source, correctly determine the clock source, and prevent timing loops.

[0004] As one of the physical layer synchronization network elements, passive optical network (PON) systems such as GPON, XGPON and NGPON2 also support synchronous Ethernet technology through PON hardware.

[0005] The following are some abbreviations or shorthand terms that may be used in this application or in its context:

[0006] GEM GPON Encapsulation Method

[0007] GPON is a passive optical network with gigabit-capable speeds (PON).

[0008] ME Managed Entity

[0009] Next-generation passive optical network with gigabit capability under NGPON2 (Next Next GPON)

[0010] OAN (Optical Access Network)

[0011] ODN (Optical Distribution Network)

[0012] OLT (Optical Line Terminal)

[0013] OMCI ONU Management and Control Interface

[0014] ONT (Optical Network Terminal)

[0015] ONU (Optical Network Unit)

[0016] PLOAM Physical Layer Operation, Administration and Maintenance

[0017] PON (Passive Optical Network)

[0018] PPTP Physical Path Termination Point

[0019] SyncE stands for Synchronous Ethernet.

[0020] SSM Synchronization Status Message

[0021] TP (Termination Point)

[0022] UNI (User Network Interface)

[0023] XGPON is a passive optical network with 10-gigabit-capable PON. Summary of the Invention

[0024] According to a first aspect of this application, a communication method implemented at an optical network unit (ONU) is provided. The communication method may include: receiving an ONU Management and Control Interface (OMCI) message from an optical line terminal (OLT), the OMCI message including configuration information of a synchronization status message passed to an SSM-IN managed entity; receiving synchronization status information from the OLT; and processing the received synchronization status information according to the configuration of the SSM-IN managed entity.

[0025] According to a second aspect of this application, an optical network unit is provided. The optical network unit may include at least one processor and at least one memory, the memory storing instructions. When executed by the processor, the instructions cause the optical network unit to perform the communication method described above.

[0026] According to a third aspect of this application, a communication device implemented at an optical network unit (ONU) is provided. The communication device may include: a first receiving module for receiving an ONU Management and Control Interface (OMCI) message from an optical line terminal (OLT), the OMCI message including configuration information of a synchronization status message passed to an SSM-IN managed entity; a second receiving module for receiving synchronization status information from the OLT; and a first processing module for processing the received synchronization status information according to the configuration of the SSM-IN managed entity.

[0027] According to a fourth aspect of this application, a computer-readable medium is provided. The computer-readable medium may store instructions that, when executed by at least one processor in an optical network unit, cause the optical network unit to perform the communication method described above.

[0028] According to a fifth aspect of this application, a communication method implemented at an optical line terminal is provided. The method may include: sending an Optical Network Unit Management and Control Interface (OMCI) message to an optical network unit, the OMCI message including configuration information of a synchronization status message passed to an SSM-IN managed entity; and sending synchronization status information to the optical network unit.

[0029] According to a sixth aspect of this application, an optical line terminal is provided. The optical line terminal may include at least one processor and at least one memory, the memory storing instructions. When executed by the at least one processor, the instructions cause the optical line terminal to perform the communication method described above.

[0030] According to a seventh aspect of this application, a communication apparatus implemented at an optical line terminal is provided. The communication apparatus may include a first transmitting module and a second transmitting module. The first transmitting module is configured to transmit an Optical Network Unit Management and Control Interface (OMCI) message to an optical network unit, the OMCI message including configuration information of a synchronization status message passed to an SSM-IN managed entity. The second transmitting module is configured to transmit synchronization status information to the optical network unit.

[0031] According to an eighth aspect of this application, a computer-readable medium is provided. The computer-readable medium may store instructions that, when executed by at least one processor in an optical line terminal, cause the optical line terminal to perform the communication method described above. Attached Figure Description

[0032] Figure 1 A schematic diagram illustrating a communication system that may implement exemplary embodiments of this application;

[0033] Figure 2 An interaction diagram illustrating a communication method according to an exemplary embodiment of this application is shown;

[0034] Figure 3 An interaction diagram illustrating a communication method according to another exemplary embodiment of this application;

[0035] Figure 4 A flowchart illustrating a communication method implemented at an optical line terminal according to an exemplary embodiment of this application;

[0036] Figure 5 This diagram illustrates a functional block diagram of an optical line terminal according to an exemplary embodiment of this application.

[0037] Figure 6 A flowchart illustrating a communication method implemented at an optical network unit according to an exemplary embodiment of this application;

[0038] Figure 7 This invention illustrates a functional block diagram of an optical network unit according to an exemplary embodiment of the present application; and

[0039] Figure 8 This diagram illustrates a structural block diagram of an electronic device according to an exemplary embodiment of this application. Detailed Implementation

[0040] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. It should be understood that the present application should not be construed as limited to the exemplary embodiments described herein, but can be implemented in various other forms; these exemplary embodiments are provided only for a more thorough and complete understanding of the present application. It should also be understood that the accompanying drawings are given by way of example only and are not intended to limit the precise form of the embodiments or to limit the scope of protection of the present application.

[0041] Figure 1 A schematic diagram of a passive optical network (PON) communication system 100, which may implement exemplary embodiments of this application, is shown. Figure 1 As shown, the passive optical network 100 may include an optical line terminal (OLT) 110 and multiple optical network units (ONUs) or optical network terminals (ONTs) 130 communicating with the OLT 110 via an optical distribution network (ODN) 120. For ease of description, only optical network units are referred to below, but it should be understood that embodiments of optical network terminals are also covered.

[0042] Optical line terminal 110 is connected to the root of one or more optical distribution networks 120 and provides a Service Node Interface (SNI) (not shown). Optical distribution network 120 is a point-to-multipoint fiber optic infrastructure. Figure 1 A simple optical distribution network 120 is shown, which includes a splitter 122. Upstream, the splitter 122 can be connected to a PON port on an optical line terminal 110 via a single optical fiber, and downstream, it can be connected to multiple optical network units 130 via multiple optical fibers. Figure 1 Three optical network units 130a, 130b, and 130c are shown as examples. A composite optical distribution network may include two or more passive optical distribution segments interconnected by active devices such as range extenders; each passive optical distribution segment can itself be a simple optical distribution network. Optical network unit 130 is connected to a leaf of optical distribution network 120 and is connected to various user terminals (not shown) via a user network interface (UNI) 132, thereby providing network access services to the terminal devices. Figure 2 User network interfaces 132a, 132b, and 132c, respectively, associated with optical network units 130a, 130b, and 130c, are shown. It can be understood that optical network unit 130 can be connected to multiple user terminals through multiple UNI ports.

[0043] like Figure 1As shown, an optical line terminal 110 can be connected to multiple optical network units 130a, 130b, and 130c through an optical distribution network 120, forming a tree structure. Data sent from the optical line terminal 110, such as synchronization status messages (SSMs), can be received at each of the optical network units 130a, 130b, and 130c. The optical line terminal 110 can manage the optical network units 130a, 130b, and 130c through the ONU Management and Control Interface (OMCI). However, optical line terminals and optical network units from different manufacturers may define different synchronization status message configurations. Therefore, the synchronization status messages sent from the optical line terminal 110 may not be correctly understood by the optical network units 130a, 130b, and 130c from different manufacturers, and consequently, the optical network unit 130 may not be able to correctly forward the synchronization status messages to the user terminal.

[0044] An exemplary embodiment of this application provides a method for managing synchronization status messages via an OMCI management channel. This method is simple and suitable for implementation between an optical line terminal and an optical network unit, thereby enabling the configuration, interpretation, and further processing of synchronization status messages. Exemplary embodiments of this application also provide apparatus and computer program products for managing synchronization status messages.

[0045] Optical line terminals (OLTs) can manage optical network units (ONUs) by operating managed entities (MEs) on the OMCI management channel, including configuration management, fault management, performance management, and security management. In some embodiments of this application, two new managed entities are defined: a Synchronization State Message Incoming (SSM-IN) managed entity and a Synchronization State Message Outgoing (SSM-OUT) managed entity, used for managing synchronization state messages.

[0046] SSM-IN regulated entities

[0047] SSM-IN managed entities are used to manage the incoming (received) synchronization status messages on optical network units (ONUs). SSM-IN managed entities can enable and disable the function of receiving synchronization status messages from the PON port of an optical line terminal (OLT) on the ONU, and determine whether to submit the synchronization status messages received from the PON port to a processor, such as a central processing unit (CPU), for processing. SSM-IN managed entities may have a class number. When an ONU has the capability to support SSM-IN managed entities, it can report this capability to the OLT, thus informing the OLT that it can use SSM-IN managed entities to manage the ONU. For example, an ONU can set its managed entity capability attribute to appropriate bit values ​​to indicate that it has the capability to support SSM-IN managed entities. Instances of SSM-IN managed entities can be created and deleted by the OLT, and actions that the OLT can perform on SSM-IN managed entities may include getting and setting. A single instance of an SSM-IN managed entity can be associated with an optical network unit managed entity.

[0048] SSM-IN managed entities may have the following attributes:

[0049] - Managed Entity Identifier (ID): This attribute uniquely identifies each instance of this managed entity;

[0050] - Virtual LAN (VLAN) ID: This is an optional attribute used to determine the VLAN ID of the synchronization status message that will be submitted to the processor for processing;

[0051] -Admin State: This attribute is used to enable and disable the functions performed by this managed entity, namely, to enable and disable the function of receiving synchronization status messages from the PON port of the optical line terminal.

[0052] It should be understood that SSM-IN managed entities may also have other attributes.

[0053] SSM-OUT Managed Entities

[0054] SSM-OUT managed entities are used to manage the transmission of synchronization status messages on optical network units (ONUs). SSM-OUT managed entities are associated with Physical Path Termination Point (PPTP) User Network Interface (UNI) managed entities, such as PPTP Ethernet UNI managed entities and PPTP Voice UNI managed entities, and can enable and disable the function of sending synchronization status messages to UNI ports on the ONU. SSM-OUT managed entities may have a class number. When an ONU supports an SSM-OUT managed entity, its managed entity capability attributes can be set to appropriate bit values ​​to indicate that it has the capability to support SSM-OUT managed entities. This allows the optical line terminal (OLT) to use the SSM-OUT managed entity to manage the transmission of synchronization status messages on the UNI ports associated with that ONU. Instances of SSM-OUT managed entities can be created and deleted by the OLT. Actions that the OLT can perform on SSM-OUT managed entities may include getting and setting. An instance of an SSM-OUT managed entity can be associated with a UNI termination point.

[0055] SSM-OUT managed entities can have the following attributes:

[0056] - Managed Entity Identifier (ID): This attribute uniquely identifies each instance of this managed entity;

[0057] -PPTP UNI pointer: This property is associated with the PPTP UNI managed entity to indicate the PPTP UNI bound to the instance of the SSM-OUT managed entity. A value of 0xFFFF indicates a null pointer.

[0058] -Admin State: This attribute enables and disables the functions performed by this managed entity, namely, enabling and disabling the function of sending synchronization status messages to the UNI port.

[0059] It should be understood that SSM-OUT managed entities may also have other attributes.

[0060] The following describes an embodiment of managing synchronization status messages for optical network units using SSM-IN and SSM-OUT managed entities. Figure 2 An interactive diagram of a communication method according to an exemplary embodiment of this application is shown. This communication method can be executed between an optical line terminal and an optical network unit in a passive optical network, for example, as shown above. Figure 1The optical line terminal 110 described herein performs an operation with the optical network unit 130.

[0061] Reference Figure 2 In step 210, the optical line terminal 110 can send SSM-IN and SSM-OUT managed entity configuration information to the optical network unit 130 via the OMCI management channel. For example, the OMCI message or frame sent from the optical line terminal 110 to the optical network unit 130 may include a creation function to create instances of SSM-IN and SSM-OUT managed entities at the optical network unit 130 initially registered in the passive optical network, and / or may include a setting function to set the attribute values ​​of the instances of SSM-IN and SSM-OUT managed entities already created at the optical network unit 130. The configuration information of the SSM-IN and SSM-OUT managed entities may be sent to the optical network unit 130 in one or more OMCI message frames. As previously described, an instance of an SSM-IN managed entity can be associated with optical network unit 130 to manage the process by which optical network unit 130 receives synchronization status messages from optical line terminal 110; an instance of an SSM-OUT managed entity can be associated with user network interface terminal point (UNI TP) 132 connected to optical network unit 130 to manage the process by which optical network unit 130 sends synchronization status messages to user network interface terminal point 132.

[0062] In step 212, the optical line terminal 110 may send a synchronization status message to the optical network unit 130 on a GPON encapsulation method (GEM) port, such as a broadcast GEM port. In some exemplary embodiments, the processor in the optical line terminal 110 may use the best clock source selected from multiple clock sources as the synchronization clock and generate a synchronization status message packet. The generated synchronization status message packet may be sent by the interworking function (IWF) module to the optical network unit 130 connected to the optical line terminal 110 on the broadcast GEM port. The synchronization status message packet may include packet identification information indicating the packet type and information indicating the synchronization status quality level. In some embodiments, the synchronization status message packet may also include virtual local area network (VLAN) identification information, clock source identification information, hop count, and other information.

[0063] In step 214, the optical network unit 130 can process the received synchronization status message packets according to the current configuration of the SSM-IN managed entity. For example, when the SSM-IN managed entity is configured to enable the synchronization status message inbound (receive) function, the switch chip in the optical network unit 130 can submit the synchronization status message packets received on the broadcast GEM port to a processor, such as a central processing unit, for further processing. When the VLAN ID attribute of the SSM-IN managed entity is set to a valid value, the switch chip in the optical network unit 130 can submit synchronization status message packets with the same VLAN ID to the processor for further processing. When the SSM-IN managed entity is configured to disable the synchronization status message inbound (receive) function, the optical network unit 130 can ignore the synchronization status messages broadcast by the optical line terminal 110 on the broadcast GEM port.

[0064] When an SSM-IN managed entity is configured to enable the synchronization status message inbound (receive) function, in step 216, the processor of the optical network unit 130 can further process the synchronization status message according to the current configuration of the SSM-OUT managed entity. For example, if an instance of an SSM-OUT managed entity associated with a UNI port is configured to enable the synchronization status message outbound function, the optical network unit 130 can replace the source media access control (MAC) address of the received synchronization status message with the UNI port MAC address, and then send the synchronization status message on that UNI port to the user terminal connected to that UNI port. As another example, if an instance of an SSM-OUT managed entity associated with a UNI port is configured to disable the synchronization status message outbound function, the optical network unit 130 will not send the received synchronization status message on that UNI port.

[0065] Therefore, in Figure 2 In the process shown, the optical line terminal 110 and the optical network unit 130 can achieve collaborative management of synchronization status messages based on the SSM-IN and SSM-OUT managed entities, thereby enabling the correct interpretation of synchronization status messages between the optical line terminal 110 and the optical network unit 130. Moreover, the optical network unit 130 can use the SSM-OUT managed entity to independently control the transmission of synchronization status messages on multiple UNI ports.

[0066] Figure 3 An interaction diagram of a communication method according to another exemplary embodiment of this application is shown. This communication method can be performed between an optical line terminal and an optical network unit in a passive optical network, for example, as shown above. Figure 1 The optical line terminal 110 described herein performs an operation with the optical network unit 130. Figure 3 The process shown is similar in some respects to Figure 2The process is illustrated below, so the main focus will be on describing the differences between the two, while omitting some repetitive descriptions.

[0067] Reference Figure 3 In step 220, the optical line terminal 110 can send SSM-IN and SSM-OUT managed entity configuration information to the optical network unit 130 via the OMCI management channel. Step 220 can be combined with... Figure 2 Step 210 is similar, so a repeated description of it is omitted here.

[0068] In step 222, the optical line terminal 110 can send a synchronization status message (SSM) quality information to the optical network unit 130 via a Physical Layer Operation Management and Maintenance (PLOAM) message, indicating the current synchronization quality level of the optical line terminal 110. In some exemplary embodiments, the processor in the optical line terminal 110 can select the optimal clock quality from multiple clock sources and send the SSM quality information to the optical network unit 130 via a PON MAC port. The PLOAM message can be a unicast message or a broadcast message. In some embodiments, the optical line terminal 110 can send the SSM quality level information to multiple optical network terminals 130 connected to it via a PLOAM broadcast message. The PLOAM broadcast message can be sent when the synchronization status quality level at the optical line terminal 110 changes, or it can be sent periodically at predetermined time intervals. In some embodiments, the PLOAM message carrying the SSM quality level information may include a field indicating the target optical network unit (in a broadcast message, it indicates all optical network units), a message ID field indicating that the message carries the SSM quality level information, and a message content field containing the SSM quality level information, etc. SSM quality level information may include predefined codes indicating the quality level, such as the European Telecommunications Standards Institute (ETSI) SSM quality level code or the American National Standards Institute (ANSI) SSM quality level code. Figure 2 Unlike the synchronization status message sent on the broadcast GEM port in step 212, in step 222, it is only necessary to send the SSM quality level information, without generating a complete synchronization status message.

[0069] In step 224, the optical network unit 130 can process the received synchronization status quality information according to the current configuration of the SSM-IN managed entity. For example, when the SSM-IN managed entity is configured to enable the synchronization status message inbound (receive) function, the optical network unit 130 can decode the PLOAM message containing synchronization status quality level information received on the MAC port to obtain the synchronization status quality level information and store the obtained synchronization status quality level information. When the SSM-IN managed entity is configured to disable the synchronization status message inbound (receive) function, the optical network unit 130 can ignore the PLOAM message containing synchronization status quality information.

[0070] When the SSM-IN managed entity is configured to enable the synchronization status message inbound (receive) function, in step 226, the processor of the optical network unit 130 can further process the synchronization status quality level information according to the current configuration of the SSM-OUT managed entity. For example, if the instance of the SSM-OUT managed entity associated with the UNI port is configured to enable the synchronization status message outbound function, the optical network unit 130 can generate a synchronization status message packet based on the received synchronization status quality level information, using the UNI port MAC address as the source MAC address in the synchronization status message packet, and then send the synchronization status message packet on the UNI port to the user terminal connected to the UNI port. As another example, if the instance of the SSM-OUT managed entity associated with the UNI port is configured to disable the synchronization status message outbound function, the optical network unit 130 will not send the generated synchronization status message packet on the UNI port.

[0071] Therefore, in Figure 3 In the process shown, the optical line terminal 110 and the optical network unit 130 can achieve collaborative management of synchronization status messages based on the SSM-IN and SSM-OUT managed entities, thereby enabling the correct interpretation of synchronization status messages between the optical line terminal 110 and the optical network unit 130. Moreover, the optical network unit 130 can use the SSM-OUT managed entity to independently control the transmission of synchronization status messages on multiple UNI ports.

[0072] Figure 4 This illustrates an exemplary embodiment of the optical line terminal, for example, as shown above. Figure 1 A flowchart describing the communication method implemented at optical line terminal 110. It will be understood that... Figure 4 Some details of the method shown have been referred to above. Figure 2-3 The description was provided during the process, so it will be briefly described here.

[0073] Reference Figure 4In step 310, the optical line terminal 110 may send an OMCI frame or message to the optical network unit 130 connected to it. The OMCI message may include configuration information of the SSM-IN managed entity. As mentioned above, the SSM-IN managed entity may be associated with the optical network unit 130 and may include attributes such as managed entity ID, VLAN ID, and management status. In some embodiments, the OMCI message may also include configuration information of the SSM-OUT managed entity. As mentioned above, the SSM-OUT managed entity may be associated with the user network interface UNI and may include attributes such as managed entity ID, PPTP UNI pointer, and management status. In some embodiments, the optical line terminal 110 may send configuration information of the SSM-IN and SSM-OUT managed entities through multiple OMCI messages.

[0074] In step 320, the optical line terminal 110 may send synchronization status information to the optical network unit 130 connected to it. In some embodiments, the synchronization status information sent by the optical line terminal 110 may include a synchronization status message message. For example, such as Figure 2 As shown in step 212, the optical line terminal 110 can send a synchronization status message to the optical network unit 130 on the broadcast GEM port. In other embodiments, the synchronization status information sent by the optical line terminal 110 may include synchronization status quality level information. For example, as... Figure 3 As shown in step 222, the optical line terminal 110 can send a PLOAM message including synchronization status quality level information to the optical network unit 130. The optical line terminal 110 can send synchronization status information to the optical network unit 130 when the synchronization status changes, or it can send synchronization status information periodically.

[0075] Figure 5 An optical line terminal according to an exemplary embodiment of this application is shown, for example, as shown above. Figure 1 The functional block diagram of the optical line terminal 110 is described. It will be understood that... Figure 5 The functional blocks shown can be implemented by hardware, software, or a combination of hardware and software to perform the operations described herein, and Figure 5 The functional blocks shown can be combined or divided into sub-blocks to implement the principles of this application described above. Therefore, the description herein also supports feasible combinations, divisions, or further definitions of the various functional blocks.

[0076] Reference Figure 5The optical line terminal 110 may include a first transmitting module 112 and a second transmitting module 114. The first transmitting module 112 may be configured to send an OMCI message to the optical network unit 130. This OMCI message may include configuration information of the SSM-IN managed entity, such as the managed entity ID, VLAN ID, and management status values ​​of the SSM-IN managed entity. In some embodiments, the OMCI message sent by the first transmitting module 112 may also include configuration information of the SSM-OUT managed entity, such as the managed entity ID, PPTP UNI pointer, and management status values. In some embodiments, the first transmitting module 112 may send the configuration information of the SSM-IN and SSM-OUT managed entities through multiple OMCI messages.

[0077] The second sending module 114 can be configured to send synchronization status information to the optical network unit 130. In some embodiments, the second sending module 114 can be configured to send a synchronization status message packet on a broadcast GEM port. In other embodiments, the second sending module 114 can be configured to send synchronization status quality level information via a PLOAM message. The second sending module 114 can send synchronization status information to the optical network unit 130 when the synchronization status changes, or it can send synchronization status information periodically.

[0078] Figure 6 This illustrates an exemplary embodiment of an optical network unit, for example, as shown above. Figure 1 A flowchart describing the communication method implemented at optical network unit 130. It will be understood that... Figure 6 Some details of the method shown have been referred to above. Figure 2-3 The description was provided during the process, so it will be briefly described here.

[0079] Reference Figure 6 In step 410, the optical network unit 130 can receive an OMCI message from the optical line terminal 110. This OMCI message may include configuration information of the SSM-IN managed entity, such as the managed entity ID, VLAN ID, and management status values ​​of the SSM-IN managed entity. In some embodiments, the OMCI message may also include configuration information of the SSM-OUT managed entity, such as the managed entity ID, PPTP UNI pointer, and management status values. In some embodiments, the optical network unit 130 may receive the configuration information of both the SSM-IN and SSM-OUT managed entities in separate OMCI messages.

[0080] In step 420, the optical network unit 130 can receive synchronization status information from the optical line terminal 110. In some embodiments, the optical network unit 130 can receive synchronization status message packets on the broadcast GEM port. In other embodiments, the optical network unit 130 can receive synchronization status quality level information carried in a PLOAM message. The second sending module 114 can send synchronization status information to the optical network unit 130 when the synchronization status changes, or it can send synchronization status information periodically.

[0081] In step 430, the optical network unit 130 can process the received synchronization status information according to the current configuration of the SSM-IN managed entity. For example, when the SSM-IN managed entity is configured to enable the synchronization status message inbound (receive) function, the optical network unit 130 can submit the synchronization status message packet received on the broadcast GEM port or the synchronization status quality level information received in the PLOAM message to a processor, such as a central processing unit, for further processing. The optical network unit 130 can also store the received synchronization status information. When the SSM-IN managed entity is configured to disable the synchronization status message inbound (receive) function, the optical network unit 130 can ignore the synchronization status message packet received on the broadcast GEM port and the synchronization status quality level information received in the PLOAM message.

[0082] In step 440, the optical network unit 130 can further process the received synchronization status information according to the current configuration of the SSM-OUT managed entity. As mentioned above, the synchronization status information can be a synchronization status message received on the broadcast GEM port or synchronization status quality level information received in a PLOAM message. When an instance of the SSM-OUT managed entity associated with the UNI port is configured to enable synchronization status message transmission, the optical network unit 130 can generate a synchronization status message based on the received synchronization status information and send the synchronization status message on the UNI port. If an instance of the SSM-OUT managed entity associated with the UNI port is configured to disable synchronization status message transmission, the optical network unit 130 will not send the generated synchronization status message on the UNI port.

[0083] Figure 7 An optical network unit according to an exemplary embodiment of this application is shown, for example, as referenced above. Figure 1 The functional block diagram of the optical network unit 130 is described. It will be understood that... Figure 7 The functional blocks shown can be implemented by hardware, software, or a combination of hardware and software to perform the operations described herein, and Figure 7The functional blocks shown can be combined or divided into sub-blocks to implement the principles of this application described above. Therefore, the description herein also supports feasible combinations, divisions, or further definitions of the various functional blocks.

[0084] Reference Figure 7 The optical network unit 130 may include a first receiving module 132, a second receiving module 134, a first processing module 136, and a second processing module 138. The first receiving module 132 is configured to receive OMCI messages from the optical line terminal 110. These OMCI messages may include configuration information of SSM-IN managed entities, such as the managed entity ID, VLAN ID, and management status values ​​of the SSM-IN managed entity. In some embodiments, the OMCI messages received by the first receiving module 132 may also include configuration information of SSM-OUT managed entities, such as the managed entity ID, PPTP UNI pointer, and management status values. In some embodiments, the first receiving module 132 may receive configuration information of both SSM-IN and SSM-OUT managed entities in multiple OMCI messages.

[0085] The second receiving module 134 can be configured to receive synchronization status information from the optical line terminal 110. For example, in some embodiments, the second receiving module 134 can be configured to receive synchronization status message packets sent on the broadcast GEM port, or in other embodiments, the second receiving module 134 can be configured to receive synchronization status quality level information in a PLOAM message.

[0086] The first processing module 136 can be configured to process the received synchronization status information according to the configuration of the SSM-IN managed entity. For example, when the SSM-IN managed entity is configured to enable the synchronization status message ingress function of SSM-IN, the first processing module 136 can process the received synchronization status information, such as decoding the OMCI message or PLOAM message to obtain the synchronization status information, and submit the synchronization status information to the second processing module 138 for further processing; when the SSM-IN managed entity is configured to disable the synchronization status message ingress function of SSM-IN, the first processing module 136 can ignore the received synchronization status information, that is, ignore the OMCI message and PLOAM message containing the synchronization status information.

[0087] The second processing module 138 can be configured to process the received synchronization status information according to the configuration of the SSM-OUT managed entity. In some embodiments, when the SSM-OUT managed entity is configured to enable the SSM-OUT function for transmitting synchronization status messages, the second processing module 138 can generate a synchronization status message packet based on the received synchronization status information and send the generated synchronization status message packet on the UNI port associated with the SSM-OUT managed entity. In some embodiments, when the SSM-OUT managed entity is configured to disable the SSM-OUT function for transmitting synchronization status messages, the second processing module 138 will prohibit the transmission of synchronization status message packets on the UNI port associated with the SSM-OUT managed entity.

[0088] Figure 8 This diagram illustrates a structural block diagram of an electronic device 500 according to an exemplary embodiment of this application. The electronic device 500 can be implemented as the optical line terminal 110 or the optical network unit 130 described above. Figure 8 As shown, the electronic device 500 may include one or more processors 510, one or more memories 520, and one or more network interfaces 530, which can communicate with each other via a bus system 540.

[0089] Processor 510 may be, for example, a central processing unit (CPU), a general-purpose processor, a controller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. Processor 510 may execute instructions in memory 520 and / or exchange data with it, thereby controlling other components coupled via bus 540 to operate collaboratively and perform the methods, steps, or functions described above.

[0090] The memory 520 may be implemented using any suitable data storage technology, examples of which include, but are not limited to, non-volatile and volatile memories, semiconductor memories, magnetic memories, optical memories, network memories, flash memory, electrically erasable programmable read-only memories, buffer memories, registers, etc. The memory 520 may include computer instructions 522, which may be executed by the processor 510, thereby enabling the processor 510 to control other components coupled via the bus 540 to operate collaboratively and perform the methods, steps, or functions described above in relation to the optical line terminal 110 or the optical network unit 130.

[0091] Network interface 530 may include one or more electrical interfaces and / or optical interfaces. For example, optical line terminal 110 and optical network unit 130 may be connected to each other via optical interfaces. Optical line terminal 110 may be connected to an upstream switch via an optical interface or an electrical interface, and optical network unit 130 may be connected to a downstream user terminal via an electrical interface. In some embodiments, network interface 530 may also include one or more transceiver antennas to facilitate wireless communication.

[0092] Embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, the computer program including instructions that, when executed by a processor, cause an electronic device to perform the communication methods, steps, or functions described above with respect to the optical line terminal 110 or the optical network unit 130.

[0093] Embodiments of this application also provide the computer program product described above, stored on a computer-readable storage medium. The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a local computing device, partially on a local computing device, as a standalone software package, partially on a local computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0094] Computer-readable storage media may take the form of any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0095] The basic principles of this application have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this application are merely examples and not limitations, and should not be considered as essential features of each embodiment of this application. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the application to the necessity of employing the aforementioned specific details for implementation.

[0096] It should also be noted that in the apparatus, devices, and methods of this application, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered equivalent solutions of this application. The execution order of the steps in the methods described in this application is not limited to the order described; for example, two steps can be performed in different orders or simultaneously, unless the context clearly indicates that the steps should be performed in a specific relative order.

[0097] The term "comprising" and its variations as used in this application are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment". Other terms should be understood in a similar manner to the above interpretations unless the context otherwise describes.

[0098] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this application. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects without departing from the scope of this application. Therefore, this application is not intended to be limited to the aspects shown herein, but rather to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A communication method implemented at an optical network unit, comprising: The optical network unit receives an optical network unit management and control interface (OMCI) message from the optical line terminal. The OMCI message includes configuration information for the synchronization status message input (SSM-IN) managed entity, which is used to manage the synchronization status message input function of the optical network unit. Receive synchronization status information from the optical line terminal; as well as The received synchronization status information is processed according to the configuration of the SSM-IN managed entity.

2. The method as described in claim 1, wherein, The SSM-IN managed entity is associated with an optical network unit.

3. The method as described in claim 1, wherein, The SSM-IN managed entity includes one or more of the following attributes: Regulated entity identifier; The virtual local area network (VLAN) identifier of the managed entity, indicating the VLAN used by the managed entity; and Management status indicates whether to enable or disable the SSM-IN function for synchronizing status messages.

4. The method of claim 1, wherein, The received synchronization status information includes: Receive synchronization status messages transmitted on the GEM port of the broadcast gigabit-ratio passive optical network encapsulation method; or Receive physical layer operation management and maintenance PLOAM messages, which include synchronization status quality information.

5. The method of claim 1, wherein, Processing the received synchronization status information according to the configuration of the SSM-IN managed entity includes: When the SSM-IN managed entity is configured to enable the synchronization status message input SSM-IN function, the processor processes the received synchronization status information; or When the SSM-IN managed entity is configured to disable the function of receiving synchronization status messages into SSM-IN, the received synchronization status information is ignored.

6. The method of claim 1, wherein, The OMCI message also includes configuration information for the managed entity from which the synchronization status message SSM-OUT is transmitted.

7. The method of claim 6, wherein, The SSM-OUT managed entity is associated with the user network interface.

8. The method of claim 6, wherein, The SSM-OUT managed entity includes one or more of the following attributes: Regulated entity identifier; A physical path endpoint user network interface pointer, indicating the user network interface associated with the SSM-OUT managed entity; and Management status indicates whether the SSM-OUT function for transmitting synchronization status messages is enabled or disabled.

9. The method of claim 6, wherein, When the SSM-IN managed entity is configured to enable the synchronization status message inbound SSM-IN function, the method further includes: The received synchronization status information is processed according to the configuration of the SSM-OUT managed entity.

10. The method of claim 9, wherein, Processing the received synchronization status information according to the configuration of the SSM-OUT managed entity includes: When the SSM-OUT managed entity is configured to enable the SSM-OUT function for transmitting synchronization status messages, it generates a synchronization status message based on the received synchronization status information and sends the synchronization status message on the user network interface associated with the SSM-OUT managed entity; or When the SSM-OUT managed entity is configured to disable the SSM-OUT function for transmitting synchronization status messages, the transmission of synchronization status messages is prohibited on the user network interface associated with the SSM-OUT managed entity.

11. An optical network unit, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the optical network unit to perform the method of any one of claims 1 to 10.

12. A communication device implemented at an optical network unit, comprising: The first receiving module is used to receive Optical Network Unit Management and Control Interface (OMCI) messages from the optical line terminal. The OMCI messages include configuration information of the Synchronization Status Message Ingress (SSM-IN) managed entity, which is used to manage the synchronization status message ingress function of the optical network unit. The second receiving module is used to receive synchronization status information from the optical line terminal; as well as The first processing module is used to process the received synchronization status information according to the configuration of the SSM-IN managed entity.

13. The apparatus of claim 12, wherein, The second receiving module is configured as follows: Receive synchronization status messages transmitted on the GEM port of the broadcast gigabit-ratio passive optical network encapsulation method; or Receive physical layer operation management and maintenance PLOAM messages, which include synchronization status quality information.

14. The apparatus of claim 12, wherein, The first processing module is configured as follows: When the SSM-IN managed entity is configured to enable the synchronization status message ingress SSM-IN function, it processes the received synchronization status information; or When the SSM-IN managed entity is configured to disable the function of receiving synchronization status messages into SSM-IN, the received synchronization status information is ignored.

15. The apparatus of claim 12, wherein, The OMCI message also includes configuration information for the managed entity from which the synchronization status message SSM-OUT is transmitted.

16. The apparatus of claim 15, further comprising: The second processing module is used to process the received synchronization status information according to the configuration of the SSM-OUT managed entity when the SSM-IN managed entity is configured to enable the synchronization status message transmission SSM-IN function.

17. The apparatus of claim 16, wherein, The second processing module is configured as follows: When the SSM-OUT managed entity is configured to enable the SSM-OUT function for transmitting synchronization status messages, it generates a synchronization status message based on the received synchronization status information and sends the synchronization status message on the user network interface associated with the SSM-OUT managed entity; or When the SSM-OUT managed entity is configured to disable the SSM-OUT function for transmitting synchronization status messages, the transmission of synchronization status messages is prohibited on the user network interface associated with the SSM-OUT managed entity.

18. A computer-readable medium having instructions stored thereon, which, when executed by at least one processor in an optical network unit, cause the optical network unit to perform the method of any one of claims 1 to 10.

19. A communication method implemented at an optical line terminal, comprising: Send an Optical Network Unit Management and Control Interface (OMCI) message to the optical network unit. The OMCI message includes configuration information for the Synchronization Status Message Ingress (SSM-IN) managed entity, which is used to manage the synchronization status message ingress function of the optical network unit. as well as Send synchronization status information to the optical network unit.

20. The method of claim 19, wherein, The SSM-IN managed entity is associated with an optical network unit.

21. The method of claim 19, wherein, The SSM-IN managed entity includes one or more of the following attributes: Regulated entity identifier; The virtual local area network (VLAN) identifier of the managed entity, indicating the VLAN used by the managed entity; and Management status indicates whether to enable or disable the SSM-IN function for synchronizing status messages.

22. The method of claim 19, wherein, Sending synchronization status information includes: Send a synchronization status message on the GEM port of the broadcast gigabit-capacity passive optical network encapsulation method; or Send a physical layer operation management and maintenance PLOAM message, which includes synchronization status quality information.

23. The method of claim 19, wherein, The OMCI message also includes configuration information for the managed entity from which the synchronization status message SSM-OUT is transmitted.

24. The method of claim 23, wherein, The SSM-OUT managed entity is associated with the user network interface.

25. The method of claim 23, wherein, The SSM-OUT managed entity includes one or more of the following attributes: Regulated entity identifier; A physical path endpoint user network interface pointer, indicating the user network interface associated with the SSM-OUT managed entity; and Management status indicates whether the SSM-OUT function for transmitting synchronization status messages is enabled or disabled.

26. An optical line terminal, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the optical line terminal to perform the method of any one of claims 19 to 25.

27. A communication device implemented at an optical line terminal, comprising: The first sending module is used to send an Optical Network Unit Management and Control Interface (OMCI) message to the Optical Network Unit. The OMCI message includes configuration information of the Synchronization Status Message Ingress (SSM-IN) managed entity, which is used to manage the synchronization status message ingress function of the optical network unit. as well as The second transmitting module is used to send synchronization status information to the optical network unit.

28. The apparatus of claim 27, wherein, The second sending module is configured as follows: Send a synchronization status message on the GEM port of the broadcast gigabit-capacity passive optical network encapsulation method; or Send a physical layer operation management and maintenance PLOAM message, which includes synchronization status quality information.

29. The apparatus of claim 27, wherein, The OMCI message also includes configuration information for the managed entity from which the synchronization status message SSM-OUT is transmitted.

30. A computer-readable medium having instructions stored thereon, which, when executed by at least one processor in an optical line terminal, cause the optical line terminal to perform the method of any one of claims 19 to 25.

Images