HK1191769A - Energy efficient ethernet power management via siepon protocol - Google Patents

Abstract

The invention discloses an energy efficient Ethernet power management via SIEPON protocol. Systems and methods are provided to allow a service provider to manage, query, and dynamically configure the protocols on network facing interfaces as well as the devices on that domain where the service provider may be provisioning services using the IEEE P1904.1 Standard for Service Interoperability in Ethernet Passive Optical Networks (SIEPON). Systems and methods are provided for using SIEPON to update an Energy Efficient Ethernet (EEE) configuration of a Customer Premise Equipment (CPE) device and for using SIEPON to gather information from a CPE device.

Description

Energy efficient Ethernet power management over SIEPON protocol

Cross reference to related applications

This application claims the benefit of U.S. provisional patent application No. 61/668,731 filed on 6/7/2012 and U.S. patent application No. 13/926,941 filed on 25/6/2013, the entire contents of which are incorporated herein by reference.

Technical Field

The present invention relates to Energy Efficient Ethernet (EEE), and more particularly, to EEE power management.

Background

EPON (ethernet passive optical network) technology is the leading technology for FTTx (fiber optic access) access networks. In response to the rapid development of EPON technology, the marketplace is looking for open, internationalized system-level specifications that promote multi-vendor interoperability. This has created a need for a new standard, and in 12 months 2009, the IEEE standards institute announced a project to form the IEEE P1904.1 working group to develop a standard for Service Interoperability (SIEPON) for ethernet passive optical networks. The team plans, in part, to bring EPONs to the next level, i.e., the global level.

The purpose of the SIEPON standard project is to develop a system level specification in a multi-vendor environment that targets "plug-and-play" interoperability for the transport, service, and control planes. SIEPON aims to build on top of the IEEE802.3ah (1G-EPON) and IEEE802.3av (1 OG-EPON) physical layer and data link layer standards and to generate system level and network level standards, allowing full "plug and play" interoperability of the transport, service and control planes in a multi-vendor environment.

With a trend that has increased in recent years, energy costs continue to escalate. Thereby, different industries are becoming increasingly sensitive to the impact of these rising costs. One area that has brought about increasingly stringent scrutiny is the IT infrastructure. Many companies now look at the power usage of their IT systems to determine whether energy costs can be reduced. To this end, industry's concentration on energy-efficient networks has led to an increased cost of using IT equipment in general (e.g., PCs, displays, printers, servers, network elements, etc.).

Modern network elements increasingly implement Energy Consumption and Efficiency (ECE) control mechanisms. Typical ECE mechanisms (e.g., power supply limits) are also used in the network. Some modern ECE control mechanisms allow physical layer elements to enter and leave low power states. The ECE control policy controls when and where the ECE controls active physical layer elements to enter and leave low power states. The device control strategy plays a key role in maximizing savings while minimizing performance impact on the network.

One example of an ECE control mechanism is the IEEE p802.3az standard, also known as Energy Efficient Ethernet (EEE). Systems and methods are provided for allowing a service provider to manage, query, and dynamically configure network-oriented interfaces and protocols on devices over a domain, wherein the service provider may provide services using SIEPON.

Disclosure of Invention

According to one aspect of the invention, there is provided an apparatus comprising:

(1) an apparatus, comprising:

an interface; and

a Service Interoperability (SIEPON) operations, administration, and maintenance (OAM) client of an Ethernet passive optical network, wherein the SIEPON OAM client is configured to:

determining an Energy Efficient Ethernet (EEE) control policy setting for a Customer Premises Equipment (CPE) device,

generating first OAM information based on the EEE control policy settings, an

And sending the first OAM information to the CPE device through the interface.

(2) The apparatus of (1), wherein the apparatus is implemented on a network of:

an Ethernet Passive Optical Network (EPON),

EPON (EPoC) over wired cable, or

The Data Over Cable Service Interface Specification (DOCSIS) provisioning (DPOE) network of EPON.

(3) The apparatus of (1), wherein the EEE control policy of the CPE device is set to a setting that places the CPE device in a sleep mode or a low power mode.

(4) The apparatus of (1), wherein the SIEPON OAM client is implemented on an Optical Line Terminal (OLT).

(5) The device of (1), wherein the SIEPON OAM client is further configured to:

receiving a recommendation to enter a sleep mode or a low power mode;

updating a control strategy based on the recommendation;

generating second OAM information based on the updated control policy; and

and sending the second OAM information to the CPE device through the interface.

(6) The device of (5), wherein the SIEPON OAM client is further configured to:

periodically receiving the recommendation to enter the sleep mode or the low power mode;

periodically updating the control strategy based on the recommendation;

periodically generating the second OAM information based on the updated control policy; and

and periodically sending the second OAM information to the CPE device through the interface.

According to another aspect of the present invention, there is also provided a system comprising:

(7) a system, comprising:

a Service Interoperability (SIEPON) operation, administration and maintenance (OAM) client of an Ethernet passive optical network; and

a Network Power Manager (NPM), wherein the NPM is configured to:

determining Energy Efficient Ethernet (EEE) control policy settings for Customer Premises Equipment (CPE) devices, an

And guiding the SIEPON OAM client to generate first OAM information based on the EEE control strategy setting.

(8) The system of (7), further comprising:

an Optical Network Unit (ONU), wherein the ONU is configured to receive the first OAM information and to transmit the first OAM information to the CPE device.

(9) The system of (7), wherein the EEE control policy of the CPE device is set to a setting that places the CPE device in a sleep mode or a low power mode.

(10) The system of (7), wherein the system is implemented on a network of:

an Ethernet Passive Optical Network (EPON),

EPON (EPoC) over wired cable, or

The Data Over Cable Service Interface Specification (DOCSIS) provisioning (DPOE) network of EPON.

(11) The system of (7), wherein the NPM is further configured to:

receiving a recommendation to enter a sleep mode or a low power mode;

updating a control strategy based on the recommendation;

generating second OAM information based on the updated control policy; and

and sending the second OAM information to the CPE device.

(12) The system of (11), wherein the NPM is further configured to:

periodically receiving the recommendation to enter the sleep mode or the low power mode;

periodically updating the control strategy based on the recommendation;

periodically generating the second OAM information based on the updated control policy; and

and periodically sending the second OAM information to the CPE device.

According to another aspect of the present invention, there is also provided a method of:

(13) a method, comprising:

determining an Energy Efficient Ethernet (EEE) control policy setting for a Customer Premises Equipment (CPE) device;

generating, using a Service Interoperability (SIEPON) operation, administration, and maintenance (OAM) client of an Ethernet passive optical network, first OAM information based on the EEE control policy settings; and

and sending the first OAM information to the CPE device.

(14) The method of (13), wherein the SIEPON OAM client is implemented on an Optical Line Terminal (OLT).

(15) The method of (13), wherein the Network Power Manager (NPM) determines the EEE control policy settings.

(16) The method of (13), wherein sending the first OAM information to the CPE device further comprises: transmitting the first OAM information to an Optical Network Unit (ONU), wherein the ONU receives the first OAM information and transmits the first OAM information to a CPE device.

(17) The method of (13), wherein the EEE control policy of the CPE device is set to a setting that places the CPE device in a sleep mode or a low power mode.

(18) The method of (13), further comprising:

receiving a recommendation to enter a sleep mode or a low power mode;

updating a control strategy based on the recommendation;

generating second OAM information based on the updated control policy; and

and sending the second OAM information to the CPE device through the interface.

(19) The method of (18), wherein a Network Power Manager (NPM) updates the control strategy based on the recommendation.

(20) The method of (18), further comprising:

periodically receiving a recommendation to enter the sleep mode or the low power mode;

periodically updating the control strategy based on the recommendation;

periodically generating the second OAM information based on the updated control policy; and

and periodically sending the second OAM information to the CPE device.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and, together with the general description given above and the detailed description of the embodiments given below, serve to explain the principles of the disclosure. In the figure:

FIG. 1A is a schematic diagram of a Passive Optical Network (PON);

FIG. 1B is a block diagram of a typical Optical Line Terminal (OLT);

fig. 2A illustrates an Ethernet Passive Optical Network (EPON) in which a central office and a plurality of subscribers are coupled together by optical fibers and passive optical splitters;

fig. 2B shows a passive optical network comprising a single OLT and a plurality of ONUs;

fig. 3 is a diagrammatic representation of an EPON system including a network power manager in accordance with an embodiment of the present disclosure;

fig. 4A is a diagram illustrating the coverage of the IEEE802.3 standard and the IEEE P1904.1SIEPON standard according to an embodiment of the present disclosure;

fig. 4B is a diagram illustrating in more detail the functions performed by the OLT user, according to an embodiment of the present disclosure;

FIG. 4C is a diagram illustrating in more detail the functions performed by an ONT user, according to an embodiment of the present disclosure;

FIG. 5 illustrates a block diagram of a system for EEE power management using SIEPON in accordance with an embodiment of the present disclosure;

FIG. 6 is a flow diagram of a method for EEE power management using SIEPON in accordance with an embodiment of the present disclosure;

fig. 7 is a flow chart of a method of updating EEE interfaces on an ONU and a CPE device based on information collected from the CPE device using a SIEPON according to an embodiment of the present disclosure.

The features and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, in which like reference characters identify corresponding parts throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which a component first appears is indicated by the leftmost digit(s) in the corresponding reference number.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent, however, to one skilled in the art, that the present disclosure, including structures, systems and methods, may be practiced without these specific details. The descriptions and illustrations herein are of a general type used by those skilled in the art to most effectively convey the substance of their work to others skilled in the art. In other instances, well-known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present disclosure.

References in the specification to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

1. Overview

Typically, control strategies within a Customer Premises Equipment (CPE)/ONU arrangement connected to an EPON are preprogrammed into the arrangement. As a result, CPE devices must be customized (e.g., to work with the Original Equipment Manufacturers (OEMs)/Original Design Manufacturers (ODMs) of these service providers) for the needs of the provider, and users cannot plug-and-play the devices into the network. Furthermore, in general, control strategies cannot be easily managed without adding special control channels, which cause additional complexity and cost. Once the control strategies are programmed into the device, the device cannot be freed from these control strategies. The service provider cannot change the control policy within the access device to which the programming is customized because the service provider cannot access the control policy for the device in the home for configuration and/or programming. On a link of a television inserted into an access link for Video On Demand (VOD), the service provider cannot manage EEE policies.

Systems and methods according to embodiments of the present disclosure allow a service provider to manage, query, and dynamically configure EEE protocols on a CPE device that is located on a customer premises and connected to an ONU (e.g., a set-top box) that communicates with the service provider to provide services. In doing so, the service provider can dynamically update EEE policies based on usage (statistics of network EEEs can be aggregated up through the siepn link to the service provider/Central Office (CO)), time, and services offered. Embodiments of the present disclosure enable a service provider to manage EEE policies for CPE devices, such that the policies are not limited to policies that are typically pre-programmed on the CPE devices. A method according to one embodiment defines specific capabilities of a service provider to query, configure and manage EEE control policies and power management on network interfaces and devices within a network domain using operations, administration, maintenance (OAM) functions of the SIEPON protocol. Protocol messages may be exchanged to implement the method.

Further, the service provider and its partner OEMs may support agreements rather than specific control policies. This can be further extended for devices that handle services provided, for example Video On Demand (VOD) services provided to EEE capable televisions. The protocol according to embodiments of the present disclosure enables a service provider to manage the control policies used by a television (and corresponding switch), including a configurable level of aggressiveness to save power and a configurable wake-up time. In addition, information about the usage data and configuration files may be sent back to the service provider from the CPE device.

The disclosed systems and methods enable service providers to dynamically promote control policies and to enter service providers into EEE domains for additional devices/services within a particular home. The disclosed systems and methods enable users to take advantage of the plug-and-play feature of end-user devices. The disclosed systems and methods may also be implemented using, for example, a SIEPON system running over a cable EPON (EPoC) (rather than EPON) and/or a Data Over Cable Service Interface Specification (DOCSIS) Provisioning (DPOE) implementation of EPON/SIEPON's EPON.

2. Passive optical network topology

A Passive Optical Network (PON) topology is now described with reference to fig. 1 and 2.A PON is a point-to-multipoint network structure that includes an Optical Line Terminal (OLT) at a service provider and an ONU at a user for providing broadband services to the user. New standards have been developed to define different types of PONs, each for a different purpose. For example, various PON types known in the related art include broadband PON (bpon), Ethernet PON (EPON), gigabit ethernet PON (10G-EPON gigabit), gigabit PON (gpon), gigabit PON (XG-PON 1), next-generation PON NGPON2, and the like.

An exemplary diagram of a typical PON100 is schematically illustrated in fig. 1. The PON100 includes N ONUs 120-1 through 120-N (collectively referred to as ONUs 120) connected to an OLT130 by a passive optical splitter 140 and optical fibers. In an EPON, for example, traffic data transmission is accomplished using two optical wavelengths (one for the downstream direction and the other for the upstream direction). Thus, downstream transmissions from OLT130 are broadcast to all ONUs 120. Each ONU120 filters its respective data according to a pre-assigned label (e.g., LLID within EPON). In one embodiment, optical splitter 140 is a 1 to N optical splitter (i.e., an optical splitter capable of distributing traffic between a single OLT130 and N ONUs 120).

In most PON architectures, upstream transmissions are shared among ONUs 120 in a Time Division Multiple Access (TDMA) -based access scheme controlled by OLT 130. TDMA requires OLT130 to first discover the ONUs and then measure their Round Trip Time (RTT) before being able to allow coordinated access to the upstream link. For this purpose, in the ranging state, the OLT130 attempts to determine the distance between the OLT130 and the terminal unit (i.e., the ONU 120) to at least find the RTT between the OLT130 and each ONU 120. The RTT for each ONU120 is required in order to coordinate TDMA-based access to the shared upstream link for all ONUs 120. In a normal mode of operation, the distance between OLT130 and ONU120 may change over time due to temperature variations on the fiber link (which are caused by different signal propagation times on the fiber). Accordingly, OLT130 continuously measures the RTT and adjusts the TDMA scheme of each ONU accordingly.

As schematically shown in fig. 1B, OLT130 (operable, for example, in an EPON) includes an electrical module 150 and an optical module 160. The electrical module 150 is responsible for processing the received upstream burst signal and generating the downstream signal. Electrical module 150 typically includes a network processor and a Media Access Control (MAC) adapter designed to process and operate upstream and downstream signals in accordance with the respective PON standards.

In most cases, the optical module 160 is implemented as a small form-factor pluggable (SFP) transceiver that receives optical burst signals transmitted from an ONU (e.g., ONU 120) and transmits continuous optical signals to the ONU. Signals are received and transmitted over two different wavelengths. For example, in EPON, in the downstream direction, optical module 160 generates optical signals from 1480nm to 1500nm (referred to as 15 XY), and in the upstream direction, optical module 160 receives optical signals from 1260nm to 1360 nm.

The optical module 160 includes a laser driver diode 161 coupled to a transmit laser diode that generates an optical signal based on an electrical signal provided by the laser diode driver 161. The optical module 160 also includes a limiter amplifier 162 coupled to receive a photodiode that produces a current proportional to the amount of light of the optical input burst signal. The limiter amplifier 162 generates two current levels representing whether the received burst signal is a '1' or '0' logic value.

The receiver/transmitter optical components (i.e., photodiodes and laser diodes) are implemented as a bidirectional optical subassembly (BoSa) module 163 that can transmit and receive high-rate optical signals. Optical module 160 also includes a controller 164 that communicates with electrical module 150 via an I2C interface and performs tasks related to calibration and monitoring of the transceiver.

OLT vendors typically develop and manufacture the electrical module 150 of the OLT130, while the optical module 160 is typically an off-the-shelf transceiver, e.g., SFP, XFP, etc. Thus, the interface between the electrical module 150 and the optical module 160 is a standard interface compatible with any type of SFP transceiver. As shown in fig. 1B, the interface includes wires for Receive (RX) data, Transmit (TX) data, enable TX signal, reset RX signal, and I2C for interfacing between electrical module 150 and controller 164. The I2C interface is a slower serial interface with data rates up to 4 Mb/sec. In contrast, the RX data and TX data interfaces are high-speed interfaces, where the data rate of the signals on these interfaces is similar to that of a PON.

2.1 Ethernet passive optical network topology

Ethernet Passive Optical Networks (EPONs) combine an ethernet packet framework with PON technology. Thus, these networks provide simple and scalable ethernet for cost-effective and high-capacity passive optics. In particular, because optical fiber has a high bandwidth, EPONs are capable of accommodating broadband voice, data, and video traffic simultaneously. Furthermore, EPON is more suitable for Internet Protocol (IP) traffic because ethernet frames can directly encapsulate native IP packets having different sizes, whereas ATM Passive Optical Networks (APONs) use fixed-size ATM cells and therefore require packet fragmentation and reassembly.

Typically, EPONs are used within the "first mile" of the network, which provides connectivity between the service provider's central office and commercial or residential subscribers. Logically, the first mile is a point-to-multipoint network, with a central office serving multiple users. A tree topology may be used in an EPON in which one fiber couples a central office to a passive optical splitter that divides downstream optical signals, distributes them to subscribers, and combines the subscribers' upstream optical signals (see fig. 2A).

intra-EPON transmissions are typically made between an Optical Line Terminal (OLT) and Optical Network Units (ONUs) (see fig. 2B). The OLT is typically located within a central office (e.g., central office 210 in fig. 2A) and couples the fiber access network to a metro backbone, which is typically an external network belonging to an ISP or local switching operator. An ONU can be located either at the curb or at an end-user location and can provide broadband voice, data, and video services. The ONUs are typically coupled to a 1xN passive optical coupler, where N is the number of ONUs, and the passive optical coupler is typically coupled to the OLT through a single optical link. This configuration can achieve a substantial savings in the amount of fiber and the amount of hardware required by an EPON.

Communications within an EPON may be divided into upstream traffic (from ONUs to OLT) and downstream traffic (from OLT to ONUs). In the upstream direction, the ONUs need to share channel capacity and resources because there is only one link coupling the passive optical coupler with the OLT. In the downstream direction, due to the broadcast nature of the 1xN passive optical coupler, downstream data frames are played out by the OLT into all ONUs and subsequently extracted by their destination ONUs according to their individual Logical Link Identifiers (LLIDs). The LLID carries the physical address information of the frame and decides which ONU is allowed to extract the frame.

Fig. 2A illustrates an Ethernet Passive Optical Network (EPON) in which a central office and a number of subscribers are coupled together by optical fibers and passive optical splitters. As shown in fig. 2A, a plurality of subscribers are coupled to a central office 210 via optical fibers and passive optical splitters 220. The passive optical splitter 220 may be located near the end user location, minimizing initial fiber deployment costs. The central office 210 may be coupled to an external network 230, such as a metropolitan area network operated by an Internet Service Provider (ISP). It is noted that although fig. 2A illustrates a tree topology, EPONs may also be based on other topologies, such as rings or buses.

Fig. 2B illustrates an EPON that includes a single OLT and multiple ONUs. The OLT201 is located within a central office (e.g., central office 210 in fig. 2A) and is coupled to an external network 230 through an interface 203. OLT201 is coupled to ONU202 by fiber and passive optical splitter 220. As shown in fig. 2B, an ONU (e.g., any of ONUs 202) may house a plurality of network devices, e.g., personal computers, telephones, video equipment, network servers, etc. One or more network devices belonging to the same class of service are typically assigned a logical link id (llid), as defined in the IEEE802.3 standard. LLID204 may represent, for example, a user or a user service, or they may be used for some other purpose. The LLID establishes a logical link between the ONU (e.g., any of ONUs 202) and the OLT (e.g., OLT 201) and may define specific Service Level Agreement (SLA) requirements. In this example, LLID #1204a is assigned to the regular data service of ONU202a, LLID #2204b is assigned to the voice service of ONU202b, LLID #3204c is assigned to the video service of ONU202b, and LLID #4204d is assigned to the critical data service of ONU202 c. LLID #5204e is assigned to set top box 206.

2.2 energy efficient Ethernet and SIEPON within PON

In a conventional PON supporting an Energy Efficient Ethernet (EEE) and a SIEPON, there is no unified power saving control strategy supporting both the EEE and the SIEPON. Instead, the EEE control policy manages Energy Consumption and Efficiency (ECE) between the ONU202 and CPE devices (e.g., set-top box 206), and the SIEPON control policy manages ECE between the OLT201 and the ONU 202. Embodiments of the present disclosure provide systems and methods that enable a service provider to dynamically update EEE control policies at an ONU202 and/or CPE device based on a SIEPON control policy using a unified control policy. In an embodiment, a unified control strategy is enforced by a Network Power Manager (NPM). FIG. 3 adds an integrated NPM300 to the topology of FIG. 2B in accordance with an embodiment of the present disclosure. For example, the NPM300 may be implemented within the OLT201 and/or within one or more ONUs 202. Alternatively, the NPM300 may be implemented within a stand-alone device (e.g., in communication with the OLT 202). Power management using EEE and SIEPON is now described in more detail.

3. Energy efficient Ethernet

The ECE control mechanism may be used to control the energy consumption and efficiency of the device. Generally, these ECE mechanisms are designed to reduce energy consumption and improve efficiency while maintaining acceptable performance levels.

An example of an ECE control mechanism is the IEEE p802.3az standard, also known as Energy Efficient Ethernet (EEE), which is incorporated herein by reference. EEE is an IEEE standard designed to conserve Ethernet power over a selected set of physical layer devices (PHYs). Example PHYs referenced within the IEEE Standard include 100BASE-TX and 1000BASE-T PHYs as well as the emerging 10GBASE-T technology and backplane interface, e.g., 10 GBASE-KR.

EEE capable devices may have their ECE features managed by a type of configuration instruction called a control policy. The control strategy generation may take into account different types of power information (e.g., traffic patterns over time, traffic, performance characteristics, type and attributes of traffic, and other relevant information that may help decide when to use the EEE function). Control policy generation may also be determined by treating the activity of the hardware subsystem as a proxy for the actual traffic analysis. Broadly, the power information may include any configuration, resource, and power usage information for all network hardware, software, and traffic relevant to ECE optimization.

For example, a control policy of a switch may describe the times and situations when the switch enters and exits the power-saving low-power state. The control strategy may be used to control one or more physical or virtual devices in the system. For example, a control strategy (also referred to as a physical control strategy or a device control strategy) adds an additional control layer to the EEE capable device. In an embodiment, a general approach to energy consumption and efficiency initiatives is to reduce the power consumed by as many network elements/links as possible for as long a time as possible. To this end, the network elements/links are put into a sleep state or a low power state when data is not being transmitted through the network. Signals are periodically transmitted over the link to refresh the receiver at the destination and thus keep the link active.

For example, each ONU202 may use EEE control policies to control energy consumption of EEE ports and use those EEE ports to control CPE devices connected thereto. For example, the ONU202a may use the EEE control policy to place a CPE device (e.g., the set-top box 206) connected to it in a sleep state (or low power state) when data is not being transmitted to the CPE device. ONU202a may also enter a sleep state (or low power state) when ONU202a determines that no data is transmitted to or from any CPE device connected thereto. The EEE control policy at each ONU may determine the frequency at which each ONU enters the sleep state. If power consumption is not managed efficiently, unacceptable performance losses may result within the network. For example, each device that is powered off (enters a sleep state or low power state) should be woken up within a reasonable time to perform the desired function. While the CPE device (e.g., set-top box 206) is powered down (e.g., enters a sleep state or a low-power state), the corresponding ONU202 (e.g., ONU202 a) periodically sends a signal to keep the link active.

4、SIEPON

After approving the ieee802.ah (EPON) standard, different operators develop their own proprietary specifications for higher layer EPON functions. SIEPON is an umbrella standard that defines a common reference structure to ensure that an EPON maintains a single ecosystem, as opposed to a multi-country controlled and/or fragmented ecosystem. SIEPON projects attempt to address the different requirements associated with multiple service models, different provisioning and management teams, and various deployment scenarios of EPON in a consistent and unified manner.

Since it is difficult to test a large number of EPON configurations compatible with siepn, siepn employs a "setup menu" approach that groups EPON features into supporting data packets. For example, an EPON feature may be a general function or a characteristic of an EPON device, such as a power saving feature. Other SIEPON features include power save features, trunk and tree protection features, software download features, authentication features, and Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) features.

SIEPON attributes are configured for a particular implementation or feature. SIEPON power saving attributes include an OLT driven power saving mechanism, a power saving mechanism that supports ONU activation/response, and/or an OLT driven power saving mechanism having multiple sleep periods. SIEPON attributes are grouped into packets. Each SIEPON packet contains a set of attributes that represent the complete specification of the OLT and ONU that are interoperating. For example, the first packet (packet a) is a global cable industry targeted specification aligned with the DOCSIS provisioning (DPoE) specification of EPON, the second packet (packet B) is a japanese local telephone carrier market targeted specification aligned with the japanese telecom telephone company (NTT) specification, and the third packet (packet C) is a chinese local telephone carrier market targeted specification aligned with the Chinese Telegraph Code (CTC) specification.

In an EPON-based access system, siepn includes the service interoperability features of the system. These features include operation, administration, maintenance (OAM) features of the access link and power saving protocols for the link, which span the OLT (e.g., OLT 201) and ONU link partners (e.g., ONU 202). However, in actual deployment, an ONU (e.g., ONU202 a) is part of a system, e.g., a Customer Premises Equipment (CPE) device, and the CPE device itself is installed within the user's home or business. The CPE device has its own control strategy and energy saving protocol.

Fig. 4A is a diagram showing the coverage of the IEEE802.3 standard and the IEEE P1904.1SIEPON standard. As shown in fig. 4A, the physical layer, MAC, and link management of EPON are defined by IEEE802.3 standard 404. The IEEE P1904.1SIEPON standard 402 provides services for higher layer users. These higher layer clients include MAC clients of ONU202a and OLT201, MAC control clients, and operations, administration, and maintenance (OAM) clients that communicate over Optical Data Network (ODN) 411. In an embodiment, the clients described herein are software clients that define the high-level performance of ONU202a and OLT201 and can be implemented in each OLT201 and ONU202a using one or more processors. However, it should be understood that in embodiments, these clients may also be implemented directly in hardware. By providing services to these clients, SIEPON can be used to control the higher layer performance of the OLT and ONUs.

As shown in fig. 4A, the functions covered by the IEEE802.3 standard 404 are represented as a line OLT function 406a and a line ONU function 406b, and are performed by the IEEE802.3 layered model 412. The services covered by the P1904.1SIEPON standard 402 are denoted as a client OLT function 408a and a client ONU function 408b and are performed by the IEEE802.3 client 414. The service specific functions 416 not covered by either of these two standards are denoted as serving OLT function 410a and serving ONU function 410 b. The line OLT function 406a and the line ONU function 406b may be used to send and receive ethernet frames, including OAM frames, but the line OLT function 406a and the line ONU function 406b cannot perform higher-level functions, such as discovery and registration. These higher-level functions are performed by the OLT client 414a and the ONU client 414b using the client OLT function 408a and the client ONU function 408b, respectively.

The ONU202a and the OLT201 communicate via the ODN411 and are connected to each other via Media Dependent Interfaces (MDIs) 403a and 403 b. OLT client 414a connects line ONU function 406b through line interface OLT-LI405a (equivalent to the MAC service and OAM service interface of IEEE 802.3), and ONU client 414b connects to line ONU function 406b through line interface ONU-LI405 b. The OLT client 414a is connected with the service specific function 416a through the user interface OLT-CI407a and the ONU client 414b is connected with the service specific function 416b through the client interface ONU-CI407 b. The OLT service specific function 416a is connected to the external network 230 through a network-to-network interface (NNI) 409a, and the ONU service specific function 416b is connected to the CPE device (e.g., set top box 206) through a client network interface (UNI) 409 b.

4.1OLT client

Fig. 4B shows the OLT client 414a in more detail. OLT client 414a includes OAM client 418a, MAC control client 418b, and MAC client 418 c. The OAM client 418a performs higher layer OAM functions 417 for the line OLT function 406a, e.g., for: internet Group Management Protocol (IGMP), Simple Network Management Protocol (SNMP), power saving, protection, alarm, statistics, provisioning, and authentication functions. The MAC control client 418b performs higher layer MAC control functions for the line OLT function 406a, which includes functions for: discovery and registration, GATE generation, and REPORT handling. The MAC client 418c performs higher layer MAC user functions for the line OLT function 406a, including functions for: virtual Local Area Network (VLAN) mode, tunneling, multicasting, quality of service (QoS) features, buffering, and scheduling functions.

SIEPON provides a unified provisioning model for the MAC client 418c datapath, including functional blocks for inputs 426a, classifiers 426b, modifiers 426c, policers/shapers 426d, cross-connectors 426e, queues 426f, schedulers 426g, and outputs 426 h. Input block 426a receives a frame from NNI409 a. The classifier block 426b classifies the input frame by comparing the frame header with a predetermined value. The modifier block 426c modifies the frame field by adding a field, replacing a field, or removing a field of the frame. The policer/shaper block 426d enforces the policy by delaying incompatible frames (shaping) or marking incompatible frames to be dropped (policing). The cross connect block 426e moves the frame to the appropriate queue. The queue block 426f holds the frame in the queue until the scheduler block 426g is ready for processing. The scheduler block 426g multiplexes the frames into an output block 426h based on a scheduling algorithm. The output block 426h outputs the frame into an interface (e.g., to OLT-LI405 a). As shown in fig. 4B, MAC client 418c includes a corresponding series of functional blocks for processing data received from line OLT function 406a for transmission to external network 230 via NNI409 a.

The MAC client 418c, OAM client 418a, and MAC control client 418b may connect with the line OLT function 406a using service primitives. For example, when MAC client 418c sends data (e.g., when output module 426h outputs a frame), MAC client 418c generates a MA _ data.request service primitive 424 a. When the MAC client receives data transmitted from the line OLT function 406a, the MAC client 418c receives the MA _ data.indication service primitive 424 b. Likewise, the MAC control client 418b and the line OLT function 406a use the MA _ control.indication service primitive 422a and the MA _ control.request service primitive 422b to send and receive information to and from each other. The OAM client 418a and the line OLT function 406a are connected using at least two sets of service primitives. When the OAM client 418a wishes to send OAM information to an ONU, the OAM client 418a generates an OAM mpdu.request service primitive 420b and/or an OAM _ ctrl.request service primitive 420 d. When the OAM client 418a receives OAM information from an ONU, the OAM client 418a receives an OAM mpdu.indication service primitive 420a or an OAM _ ctrl.indication service primitive 420 c.

4.2ONU client

Fig. 4C is a diagram illustrating ONU client 414b in more detail. The ONU client 414b includes an OAM client 428a, a MAC control client 428b, and a MAC client 428 c. The OAM client 428a performs higher layer OAM functions 427 for the line ONU function 406b, e.g. for: internet Group Management Protocol (IGMP), Simple Network Management Protocol (SNMP), power saving, protection, alarm, statistics, provisioning, and authentication functions. The MAC control user 428b performs higher layer MAC control functions for the line OLT function 406b, including for: discovery and registration, GATE generation, and REPORT handling. The MAC client 428c performs higher layer MAC client functions for the line OLT function 406b, including functions for: virtual Local Area Network (VLAN) mode, tunneling, multicasting, quality of service (QoS) features, buffering, and scheduling functions. MAC client 428c connects with CPE devices (e.g., set top box 206) through NNI409 b.

4.3SIEPON Power management

In an embodiment, the OLT201 enforces ECE policies to control the energy consumption and efficiency of the ONUs 202. For example, if OLT201 has no data to send to ONU202a, and ONU202a has not sent data to OLT201, OLT201 can direct ONU202a to enter sleep mode or low power mode. If the OLT201 has no data to send to any of the ONUs 202a, and if the ONUs 202 have not sent data to the OLT201, the OLT201 may enter a sleep mode or low power mode. Embodiments of the present disclosure provide systems and methods for enforcing an ECE control policy not only on connected ONUs, but also on CPE devices (e.g., set-top box 206) using SIEPON.

5. Performing EEE power management using SIEPON

Embodiments of the present disclosure provide systems and methods for using OAM functions within a SIEPON to define specific capabilities of a service provider to query, configure, and manage EEE control policies and power management on network interfaces and devices within a network domain. For example, the EEE control strategy may be used to implement power saving features on devices external to the EPON (e.g., set top box 206 in fig. 2B). The set-top box 206 may be directed based on the control strategy, sleep frequency, traffic level at which the EEE protocol is activated, time to enter sleep mode, etc. However, the home device need not be initially configured with these protocols. Embodiments of the present disclosure use the SIEPON protocol to reconfigure the EEE control protocol within set-top box 206 (and other user devices).

This allows a service provider (e.g., connected to the set-top box 206 via the external network 230) to have a level of control over the configuration of the energy efficiency policy of the set-top box 206. The service provider may also query the set-top box 206 for statistics and performance using SIEPON and send updates based on information collected from the set-top box 206. For example, if the service provider determines that more energy may be saved by adjusting its control policy (e.g., based on day/night) after operating set top box 206 for months (or some other period of time), the service provider may initiate an update to set top box 206 using the OAM features. It should be understood that several different types of set-top boxes may be used by the end user. Some set-top boxes are relatively simple, having only one setting, and such settings are updatable. More complex set-top boxes may be configured in a variety of configurations.

For example, when the OLT directs ONU202a to power down based on the SIEPON policy, embodiments of the present disclosure enable ONU202a (or any other ONU 202) to recommend powering down the CPE device (e.g., set-top box 206) connected to ONU202 a. When ONU202a reduces power based on its EEE policy, embodiments of the present disclosure also enable ONU202a to recommend reducing the power of the OLT 201.

5.1 network Power manager

In one embodiment, a Network Power Manager (NPM) 300 may be used to manage control policies for devices within a network. FIG. 3 adds an integrated NPM300 to the topology of FIG. 2B in accordance with an embodiment of the present disclosure. As described above, conventional approaches to ECE within a network do not provide end-to-end management of network elements. This lack of ECE management is particularly important relative to implementing ECE improvements. In the topology of fig. 2B, for example, there is no central management of different ECE capabilities, control policies, and other power saving features with different network elements.

It should be understood that the particular set of power information received, the analysis performed on the power information, and the process of generating configuration instructions based on the power information may depend on the implementation. In an embodiment, NPM300 may connect with and/or manage OLT user 414a of fig. 4B and ONU user 414B of fig. 4C. For example, the NPM300 may collect information from the ONU202a and the OLT 201. Such information may include, for example: (1) operational characteristics such as wake-up time, link speed, buffer size, manufacturer, location of the device on the network, and configuration options; (2) policy information implemented, e.g., sleep triggers and buffering requirements; and/or (3) control policy settings (e.g., how forcefully to enforce the low power mode, when to set a wake-up timer, etc.).

The NPM300 may be placed in any of a number of locations within the EPON topology of fig. 3 in accordance with embodiments of the present disclosure. For example, in an embodiment, the NPM300 is implemented as an OLT201 module. Alternatively, NPM300 may be implemented as a module of one or more ONUs 202. NPM300 may also be implemented within one or more CPE devices coupled to ONU202 (e.g., within set-top box 206). The NPM300 may also be implemented as a separate module coupled to the OLT201, the ONU202, and/or CPE equipment coupled to the ONU 202. Furthermore, an EPON system may have a single NPM or multiple NPMs. It should be understood that the NPM300 may be implemented in hardware or software (or a combination of hardware and software), for example. Furthermore, in an embodiment, the NPM300 need not be implemented as part of a network element to collect power information and send configuration instructions to the element. For example, in an embodiment, the NPM300 may be implemented as a stand-alone device in communication with the OLT201 and/or the ONUs 202 a.

5.2 updating EEE configuration of CPE device using SIEPON

When transporting a CPE device (e.g., set top box 206), certain default settings are typically configured within the CPE device to support EEE functionality. Embodiments of the present disclosure enable a service provider to change these default settings to update EEE functionality of CPE devices using OAM of the EPON.

Fig. 5 illustrates a block diagram of a system for EEE power management using SIEPON in accordance with an embodiment of the disclosure. In fig. 5, OLT201 communicates with ONU202a over a network link and set-top box 206 is coupled to ONU202 a. In an embodiment, the system of fig. 5 is an EPON system. However, it should be understood that embodiments of the present disclosure are not limited to EPONs. For example, in an embodiment, the system of fig. 5 may be a cable-based EPON (epoc) system or a system using a Data Over Cable Service Interface Specification (DOCSIS) provisioning for cable service (DPOE) implementation of EPON/SIEPON.

In an embodiment, the set-top box 206 is configured with an EEE control policy 500. The control strategy 500 may be a single control strategy or a series of several different control strategies. The EEE control strategy 500 may be used to implement power saving features on the set-top box 206. For example, the set-top box 206 may be directed based on the control policy 500, the sleep frequency, the traffic level at which the EEE protocol is activated, the time to enter the sleep mode, and the like. A service provider servicing the set-top box 206 using the system of fig. 5 may use the siepn management policy 500. In an embodiment, the service provider's central office is located at OLT201, and the service provider manages policies 500 of OLT 201. However, it should be understood that in one embodiment, the service provider may also manage policies 500 through the ONU202a and/or the external network 230.

Since the IEEE P1904.1SIEPON standard serves higher layer users 402 (e.g., OAM client 418a of OLT201 and OAM client 428a of ONU202 a), SIEPON can be used to control the higher layer OAM performance of OLT201, ONU202a, and set top box 206. When the OLT directs to place the ONU202a in the sleep mode or the low power mode, the service provider may use SIEPON to direct the OAM user 418a of the OLT201 to send an OAM message to the set-top box 206 to place the set-top box 206 in the sleep mode or the low power mode. Thus, embodiments of the present disclosure enable a service provider to set a unified ECE control policy for an entire network managed by the service provider.

In an embodiment, the OAM message is generated in a format that the ONU202a can process. For example, in an embodiment, OLT201 sends OAM messages to ONU202 using OAM Protocol Data Units (PDUs) 202 a. These OAM PDUs may contain control information (e.g., information that directs set top box 206 to be placed in sleep mode). In an embodiment, to send OAM messages from OLT201 to OLT202a, OAM subscriber 418 generates a service primitive to request OAM PDUs to be delivered from OLT201 to ONU202 a. For example, in an embodiment, OAM subscriber 418a generates an OAM mpdu.request service primitive 420b and/or an OAM _ ctrl.request service primitive 420d to send an OAM PDU to ONU202a through line OLT function 406 a. These OAM PDUs may include OAM power save PDUs to direct set top box 206 to change policy 500 to place set top box 206 in a sleep mode or a low power mode if set top box 206 is not currently in use.

Once OAM subscribers 418a generate OAM PDUs, line OLT function 406a sends these OAM PDUs to ONU202a using IEEE802.3 function 404. For example, in an embodiment, OAM PDUs are sent to ONU202a in one or more ethernet data frames, and then ONU202a extracts the data frames based on their respective Logical Link Identifiers (LLIDs), which carry the physical address information of the frames and determine which ONU is allowed to extract the frames. As shown in fig. 3, the set top box is assigned LLID204e, and therefore, ONU202a assigns LLID204e to one or more data frames to be sent to ONU202 a.

Once the ONU202a receives the data frames, they are sent to the OAM client 428a of the ONU202a via the service primitives OAM mpdu. These frames are then sent from OAM client 428a to MAC client 428c by OAM function 427. MAC client 428c may be used to communicate OAM information to set top box 206 to direct set top box 206 to change policy 500. As discussed above with respect to the OLT202, the MAC client 428c contains a set of functional blocks for processing data to be transmitted. Likewise, the MAC client 428c of the ONU202a also contains a set of functional blocks for processing the data to be transmitted. Cross-connect block 426d of MAC client 428c moves the frames into the appropriate queue for output on NNI409 b.

Since these frames are assigned to LLID204e, they are sent by ONU202a to set top box 206 through NNI409 b. Once the set top box 206 receives the frame, the set top box 206 changes the policy 500 to direct the set top box 206 to enter a sleep mode or low power mode if the set top box 206 is not currently in use.

In an embodiment, the service provider manages the policy 500 using the NPM 300. However, it should be understood that in an embodiment, the service provider may manage the policy 500 without using a network power manager. In an embodiment, NPM300 manages OAM functions 417 of OLT201 and directs OLT201 to send OAM PDUs through OAM client 418a each time NPM300 determines that policy 500 should be updated. Further, in an embodiment, the NPM300 may manage EEE control policies for various CPE devices coupled to the ONU 202.

In an embodiment, one or more of the OLT201, the ONU202a, and/or the set-top box 206 may comprise a processor 502. For example, in an embodiment, the processor 502a may process instructions of the client OLT function 408 a. Further, in an embodiment, the processor 502a may process instructions of the NPM 300. In another embodiment, the NPM300 has its own dedicated processor. In an embodiment, processor 502b may process instructions of client ONU function 408 b. Further, in an embodiment, processor 502c may process instructions of set top box 206 and/or policy 500.

Fig. 6 is a flow diagram of a method for EEE power management using SIEPON in accordance with an embodiment of the present disclosure. In step 600, the service provider determines new control policy settings. For example, in an embodiment, if the set-top box 206 is not currently in use, the service provider determines that the control policy 500 of the set-top box 206 should be modified to direct the set-top box 206 to enter a sleep mode or a low power mode. In step 602, the OLT201 generates OAM information based on the new control policy settings. For example, the OAM client 418a of the OLT201 generates an OAMPDU of the new control policy setting using the oampdu.request service primitive 420b and/or the OAM _ ctrl.request service primitive 420 d. In step 604, the OLT201 transmits OAM information to the CPE device through the ONU. For example, OLT201 sends OAM information to ONU202a, and MAC client 428c of ONU202a receives the OAM information and sends one or more frames to set top box 206, directing set top box 206 to change policy 500. In step 604, the OLT201 may modify the EEE control policy of the ONU202a and may send a new EEE control policy instruction to the CPE device.

5.3 collecting information from CPE devices using SIEPON

Embodiments of the present disclosure also enable a service provider to use OAM features in a SIEPON to obtain information about the performance mode of a CPE device so that the service provider can more efficiently control the EEE functions of the device through the SIEPON. For example, in an embodiment, the service provider may gather information from set-top box 206.

In an embodiment, when ONU202a enters sleep mode or low power mode based on its EEE control policy, ONU202a may advise OLT201 to also enter sleep mode or low power mode. For example, in an embodiment, the OAM client 428a of the ONU202a generates an OAM mpdu.request service primitive 420b and/or an OAM _ ctrl.request service primitive 420d to send an OAM PDU to the OLT201 through the line ONU function 406 b. Since the ONU202a is not currently in use, these OAM PDUs may include OAM power save PDUs to suggest placing the OLT201 in a sleep mode or a low power mode.

Once the OAM PDUs are generated by the OAM subscriber 428a, the line ONU function 406b uses the IEEE802.3 function 404 to send these OAM PDUs to the OLT 201. For example, in an embodiment, the OAM PDUs are sent to OLT201 in one or more ethernet data frames, and then OLT201 extracts the data frames. Once the OLT201 receives the data frame, the data frame is transmitted to the OAM client 418a of the OLT201 through the service primitives OAM mpdu. In an embodiment, the OAM client 418a sends OAM information to the NPM 300. The service provider may use the OAM information to determine whether to place the OLT201 in a sleep mode or a low power mode. For example, if the OLT201 is still sending or receiving information from another ONU (e.g., ONU202 b), the service provider may determine not to place the OLT201 in a sleep mode or low power mode.

In an embodiment, a service provider may continuously collect OAM information from multiple CPE devices over a network. By monitoring the power usage of the CPE device, the service provider can dynamically modify the EEE policy of the CPE device as the usage pattern of the customer changes. In an embodiment, the service provider determines the manner in which EEE policy information is collected and managed using the NPM 300. However, it should be understood that in an embodiment, the service provider may collect and manage EEE policy information without using the NPM 300.

Fig. 7 is a flow chart of a method of updating EEE interfaces on an ONU and a CPE device based on information collected from the CPE device using SIEPON in accordance with an embodiment of the present disclosure. In step 700, the OLT201 receives a recommendation to enter a sleep mode or a low power mode (e.g., from the ONU202 a). For example, in an embodiment, ONU202a sends the recommendation to OLT201 when ONU202a enters sleep mode or low power mode. Based on the recommendation, OLT201 optionally updates the control policy in step 702. For example, OLT201 may determine whether to enter a sleep mode or a low-power mode more or less frequently based on data received from ONU 202. Alternatively, OLT201 may determine not to change its control policy. In step 704, OLT201 may generate OAM information based on the new control policy settings. For example, the OLT201 may use its updated control policy to change when to direct the ONU202a to enter sleep mode or low power mode. In step 706, the OLT201 sends OAM information to a CPE device (e.g., the set-top box 206) through an ONU (e.g., the ONU202 a).

6. Conclusion

It is to be understood that the detailed description section, and not the abstract section, is intended to be used to interpret the claims. The abstract section may set forth one or more (but not all) exemplary embodiments of the disclosure as contemplated by the inventors, and is therefore not intended to limit the disclosure and the appended claims in any way.

The present disclosure has been described above with the aid of functional building blocks illustrating the implementation of specific functions and relationships thereof. The boundaries of these functional elements have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.

The foregoing description of the specific embodiments will so fully reveal the general nature of the disclosure that others can, by applying knowledge within the skill of the art, readily modify and/or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general principles of the present disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance.

The representative signal processing functions described herein may be implemented in hardware, software, or a combination thereof. For example, from the discussion provided herein, those skilled in the art will appreciate that signal processing functions can be implemented using a computer processor, computer logic, an application specific circuit (ASIC), a digital signal processor, and the like. Accordingly, any processor that performs the signal processing functions described herein is within the scope and spirit of the present disclosure.

The above systems and methods may be implemented as a computer program executing on a machine, a computer program product, a tangible and/or non-transitory computer-readable medium having stored instructions. For example, the functions described herein may be embodied by computer program instructions that are executed by a computer processor or any of the hardware devices described above. The computer program instructions cause the processor to perform the signal processing functions described herein. The computer program instructions (e.g., software) may be stored in a tangible, non-transitory computer-usable medium, a computer program medium, or any storage medium accessible to a computer or processor. Such media include memory devices (e.g., RAM or ROM) or other types of computer storage media (e.g., computer diskette or CD ROM). Thus, any tangible, non-transitory computer storage medium having computer program code that causes a processor to perform the signal processing functions described herein is within the scope and spirit of the present disclosure.

While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims (10)

1. An apparatus, comprising:

an interface; and

a Service Interoperability (SIEPON) operations, administration, and maintenance (OAM) client of an Ethernet passive optical network, wherein the SIEPON OAM client is configured to:

determining an Energy Efficient Ethernet (EEE) control policy setting for a Customer Premises Equipment (CPE) device,

generating first OAM information based on the EEE control policy settings, an

And sending the first OAM information to the CPE device through the interface.

2. The device of claim 1, wherein the device is implemented on a network of:

an Ethernet Passive Optical Network (EPON),

EPON (EPoC) over wired cable, or

The Data Over Cable Service Interface Specification (DOCSIS) provisioning (DPOE) network of EPON.

3. The device of claim 1, wherein the SIEPON OAM client is further configured to:

receiving a recommendation to enter a sleep mode or a low power mode;

updating a control strategy based on the recommendation;

generating second OAM information based on the updated control policy; and

and sending the second OAM information to the CPE device through the interface.

4. The device of claim 3, wherein the SIEPON OAM client is further configured to:

periodically receiving the recommendation to enter the sleep mode or the low power mode;

periodically updating the control strategy based on the recommendation;

periodically generating the second OAM information based on the updated control policy; and

and periodically sending the second OAM information to the CPE device through the interface.

5. A system, comprising:

a Service Interoperability (SIEPON) operation, administration and maintenance (OAM) client of an Ethernet passive optical network; and

a Network Power Manager (NPM), wherein the NPM is configured to:

determining Energy Efficient Ethernet (EEE) control policy settings for Customer Premises Equipment (CPE) devices, an

And guiding the SIEPON OAM client to generate first OAM information based on the EEE control strategy setting.

6. The system of claim 5, wherein the NPM is further configured to:

receiving a recommendation to enter a sleep mode or a low power mode;

updating a control strategy based on the recommendation;

generating second OAM information based on the updated control policy; and

and sending the second OAM information to the CPE device.

7. The system of claim 6, wherein the NPM is further configured to:

periodically receiving the recommendation to enter the sleep mode or the low power mode;

periodically updating the control strategy based on the recommendation;

periodically generating the second OAM information based on the updated control policy; and

and periodically sending the second OAM information to the CPE device.

8. A method, comprising:

determining an Energy Efficient Ethernet (EEE) control policy setting for a Customer Premises Equipment (CPE) device;

generating, using a Service Interoperability (SIEPON) operation, administration, and maintenance (OAM) client of an Ethernet passive optical network, first OAM information based on the EEE control policy settings; and

and sending the first OAM information to the CPE device.

9. The method of claim 8, further comprising:

receiving a recommendation to enter a sleep mode or a low power mode;

updating a control strategy based on the recommendation;

generating second OAM information based on the updated control policy; and

and sending the second OAM information to the CPE device through the interface.

10. The method of claim 9, further comprising:

periodically receiving a recommendation to enter the sleep mode or the low power mode;

periodically updating the control strategy based on the recommendation;

periodically generating the second OAM information based on the updated control policy; and

and periodically sending the second OAM information to the CPE device.