阅读说明：本技术 多信道无源光网络（pon）中的发现和注册 (Discovery and registration in a multi-channel Passive Optical Network (PON) ) 是由 高波 杜安·雷明 弗兰克·埃芬博格 于 2018-04-25 设计创作，主要内容包括：一种ONU,包括：接收器,用于从OLT接收发现授权消息,所述发现授权消息包括信道指配字段和发现信息字段,所述信道指配字段指示多个信道的传输特征,所述发现信息字段指示25G上行能力和25G发现窗口；以及处理器,其耦合到所述接收器并用于处理所述发现授权消息。一种在ONU中实施的方法,所述方法包括：生成注册请求消息,所述注册请求消息包括目的地址字段、源地址字段、长度/类型字段、opcode字段以及发现信息字段,所述发现信息字段指示25G上行能力以及25G注册尝试；以及传输所述注册请求消息至OLT。(An ONU, comprising: a receiver to receive a discovery grant message from an OLT, the discovery grant message including a channel assignment field indicating transmission characteristics of a plurality of channels and a discovery information field indicating a 25G upstream capability and a 25G discovery window; and a processor coupled to the receiver and configured to process the discovery grant message. A method implemented in an ONU, the method comprising: generating a registration request message, the registration request message including a destination address field, a source address field, a length/type field, an opcode field, and a discovery information field, the discovery information field indicating 25G uplink capability and a 25G registration attempt; and transmitting the registration request message to the OLT.)

1. An Optical Network Unit (ONU), comprising:

a receiver for receiving a discovery grant message from an Optical Line Terminal (OLT), the discovery grant message including an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field,

the channel assignment field indicates transmission characteristics of a plurality of channels corresponding to different wavelengths,

the discovery information field indicates an upstream data rate and a discovery window supported by the OLT,

the discovery authorization length field comprises a first field and a second field, wherein the first field is used for indicating the transmission opportunity duration, and the second field is used for indicating whether fragmentation is allowed or not; and

a processor coupled to the receiver and configured to process the discovery grant message.

2. The ONU of claim 1, wherein the channel assignment field comprises:

a first field indicating whether uplink channel 0 can be used for transmission; and

a second field indicating whether uplink channel 1 can be used for transmission.

3. The ONU of claim 2, wherein the channel assignment field further comprises:

a third field indicating whether uplink channel 2 can be used for transmission;

a fourth field indicating whether the uplink channel 3 can be used for transmission; and

and a fifth field which is a reserved field.

4. The ONU of any of claims 1-3, wherein the discovery information field comprises:

a first field indicating whether the OLT supports 25 gigabit per second (Gb/s) reception; and

a second field indicating whether the OLT can receive 25Gb/s data in a window.

5. The ONU of claim 4, wherein the discovery information field further indicates:

the capacity of 50G of uplink is increased,

the window is found in the 50G range,

100G uplink capability, an

100G find window.

6. The ONU of claim 1, wherein the discovery grant length field further comprises:

a third field indicating the discovery authorization message; and

a fourth field indicating whether a report frame should be issued for an authorized Logical Link Identifier (LLID).

7. The ONU of claim 1, wherein the discovery authorization message further comprises an authorized Logical Link Identifier (LLID) field indicating a broadcast LLID.

8. A method implemented in an Optical Line Terminal (OLT), the method comprising:

generating a discovery grant message including an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field,

the channel assignment field indicates transmission characteristics of a plurality of channels corresponding to different wavelengths,

the discovery information field indicates an upstream data rate and a discovery window supported by the OLT,

the discovery authorization length field comprises a first field and a second field, wherein the first field is used for indicating the transmission opportunity duration, and the second field is used for indicating whether fragmentation is allowed or not; and

transmitting the authorization message to an Optical Network Unit (ONU).

9. The method of claim 8, wherein the channel assignment field comprises:

a first field indicating whether uplink channel 0 can be used for transmission; and

a second field indicating whether uplink channel 1 can be used for transmission.

10. The method of claim 9, wherein the channel assignment field further comprises:

a third field indicating whether uplink channel 2 can be used for transmission;

a fourth field indicating whether the uplink channel 3 can be used for transmission; and

and a fifth field which is a reserved field.

11. The method of claim 8, wherein the discovery grant length field further comprises:

a third field indicating the authorization message; and

a fourth field indicating whether a report frame should be issued for an authorized Logical Link Identifier (LLID).

12. An Optical Line Terminal (OLT), comprising:

a processor for generating a discovery grant message including an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field,

the channel assignment field indicates transmission characteristics of a plurality of channels corresponding to different wavelengths,

the discovery information field indicates an upstream data rate and a discovery window supported by the OLT,

the discovery authorization length field comprises a first field and a second field, wherein the first field is used for indicating the transmission opportunity duration, and the second field is used for indicating whether fragmentation is allowed or not; and

a transmitter coupled to the processor and configured to transmit the discovery grant message to an Optical Network Unit (ONU).

13. The OLT of claim 12, wherein the channel assignment field comprises:

a first field indicating whether uplink channel 0 can be used for transmission; and

a second field indicating whether uplink channel 1 can be used for transmission.

14. The OLT of claim 13, wherein the channel assignment field further comprises:

a third field indicating whether uplink channel 2 can be used for transmission;

a fourth field indicating whether the uplink channel 3 can be used for transmission; and

and a fifth field which is a reserved field.

15. The OLT of claim 12, wherein the discovery grant length field further comprises:

a third field indicating the authorization message; and

a fourth field indicating whether a report frame should be issued for an authorized Logical Link Identifier (LLID).

16. A method implemented at an Optical Network Unit (ONU), the method comprising:

receiving a discovery grant message from an Optical Line Terminal (OLT), the discovery grant message including an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field,

the channel assignment field indicates transmission characteristics of a plurality of channels corresponding to different wavelengths,

the discovery information field indicates an upstream data rate and a discovery window supported by the OLT,

the discovery authorization length field comprises a first field and a second field, wherein the first field is used for indicating the transmission opportunity duration, and the second field is used for indicating whether fragmentation is allowed or not; and

and processing the discovery authorization message, and communicating with the OLT according to the channel and the rate indicated by the discovery authorization message.

17. The method of claim 16, wherein the channel assignment field comprises:

a first field indicating whether uplink channel 0 can be used for transmission; and

a second field indicating whether uplink channel 1 can be used for transmission.

18. The method according to claim 16 or 17, wherein the discovery information field comprises:

a first field indicating whether the OLT supports 25 gigabit per second (Gb/s) reception; and

a second field indicating whether the OLT can receive 25Gb/s data in a window.

19. The method of claim 18, wherein the discovery information field further indicates:

the capacity of 50G of uplink is increased,

the window is found in the 50G range,

100G uplink capability, an

100G find window.

20. The method of claim 16, wherein the discovery grant length field further comprises:

a third field indicating the discovery authorization message; and

a fourth field indicating whether a report frame should be issued for an authorized Logical Link Identifier (LLID).

21. The method of claim 16, wherein the discovery authorization message further comprises an authorized Logical Link Identifier (LLID) field indicating a broadcast LLID.

Technical Field

The present invention relates to the field of Passive Optical Network (PON) technologies, and in particular, to a multi-channel PON.

Background

A PON is a system for providing network access in the last mile, which is the last part of a telecommunications network that provides communications to customers. The PON is a P2MP network that includes an OLT at the CO, ONUs at the customer premises, and an ODN that couples the OLT to the ONUs. The PON may also include an RN located between the OLT and the ONUs, e.g., at the end of the road where the plurality of customers are located.

NG-PONs can combine TDM and WDM to support higher capacity so that a single OLT can provide enough bandwidth per subscriber to serve more subscribers. In such a TWDM PON, a WDM PON may be overlaid on top of a TDM PON. Thus, different wavelengths can be multiplexed together to share one trunk fiber, and each wavelength can be shared by multiple users through TDM.

Disclosure of Invention

In one embodiment, the present invention includes an ONU, including: a receiver to receive a discovery grant message from an OLT, the discovery grant message including a channel assignment field indicating transmission characteristics of a plurality of channels and a discovery information field indicating a 25G upstream capability and a 25G discovery window; and a processor coupled to the receiver and configured to process the discovery grant message. In some embodiments, the channel assignment field comprises: a first field indicating whether uplink channel 0 can be used for transmission; a second field indicating whether uplink channel 1 can be used for transmission; a third field indicating whether uplink channel 2 can be used for transmission; a fourth field indicating whether the uplink channel 3 can be used for transmission; and a fifth field which is a reserved field; the discovery information field includes: a first field indicating whether the OLT supports 25Gb/s reception; and a second field indicating whether the OLT can receive 25Gb/s data in a window; the discovery information field further indicates: a 50G uplink capability, a 50G discovery window, a 100G uplink capability, and a 100G discovery window; the discovery grant message includes an opcode field, the opcode field including a value of 0x 0017; sending the discovery grant message further includes a grant length field; the grant length field includes: a first field indicating a transmission opportunity duration; a second field indicating a discovery authorization message; a third field indicating whether a report frame should be issued for an authorized LLID; and a fourth field indicating whether fragmentation is allowed; the discovery grant message also includes a grant LLID field indicating a broadcast LLID.

In another embodiment, the present invention includes a method implemented in an OLT, the method comprising: generating an authorization message, wherein the authorization message is a discovery authorization message or a normal authorization message, the authorization message includes a destination address field, a source address field, a length/type field, an operation code (opcode) field, a timestamp field, a channel assignment field, a start time field, an authorization length field, and a synchronization (sync) time field, and when the authorization message is the discovery authorization message, the authorization message further includes a discovery information field, and the channel assignment field indicates transmission characteristics of a plurality of channels corresponding to different wavelengths; and transmitting the authorization message to the ONU. In some embodiments, the channel assignment field comprises: a first field indicating whether uplink channel 0 can be used for transmission; a second field indicating whether uplink channel 1 can be used for transmission; a third field indicating whether uplink channel 2 can be used for transmission; a fourth field indicating whether the uplink channel 3 can be used for transmission; and a fifth field which is a reserved field; the grant length field includes: a first field indicating a transmission opportunity duration; a second field indicating the authorization message; a third field indicating whether a report frame should be issued for an authorized LLID; and a fourth field indicating whether fragmentation is allowed; the grant message also includes an opcode field, wherein the opcode field includes a value of 0x 0017.

In yet another embodiment, the present invention includes a method implemented in an ONU, comprising: generating a registration request message, the registration request message including a destination address field, a source address field, a length/type field, an opcode field, and a discovery information field, the discovery information field indicating 25G uplink capability and a 25G registration attempt; and transmitting the registration request message to the OLT. In some embodiments, the opcode field includes a value of 0x 0014; the discovery information field also indicates 50G uplink capability and 50G registration attempt; the discovery information field also indicates 100G uplink capability and 100G registration attempt.

In yet another embodiment, the present invention includes an OLT comprising: a processor configured to generate a registration message comprising a destination address field, a source address field, a length/type field, an opcode field, a timestamp field, and a default channel configuration field indicating that a transmitter in an ONU is enabled or disabled; and a transmitter coupled to the processor and configured to transmit the registration message to the ONU. In some embodiments, the default channel configuration field is one octet; the default channel configuration field comprises four bits dedicated to a downlink channel; the default channel configuration field includes four bits dedicated to uplink channels.

Any of the above embodiments may be combined with any other of the above embodiments to create a new embodiment. These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

Drawings

For a more complete understanding of the present invention, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

Fig. 1 is a schematic diagram of a PON.

Fig. 2 is a message sequence chart showing discovery and registration of an ONU.

Fig. 3 is a discovery grant message according to an embodiment of the present invention.

Fig. 4 is a discovery grant message according to another embodiment of the present invention.

Fig. 5 is a channel assignment field in a discovery grant message according to an embodiment of the invention.

Fig. 6 is a channel assignment field in a discovery grant message according to another embodiment of the present invention.

Fig. 7 is a discovery grant length (EQ) field in a discovery grant message according to an embodiment of the present invention.

Fig. 8 is a discovery information field in a discovery grant message according to an embodiment of the present invention.

Fig. 9 is a discovery information field in a discovery grant message according to another embodiment of the present invention.

Fig. 10 is a discovery information field in a discovery grant message according to still another embodiment of the present invention.

Fig. 11 is a discovery information field in a discovery grant message according to still another embodiment of the present invention.

Fig. 12 is a registration request message according to an embodiment of the present invention.

Fig. 13 is a discovery information field in a registration request message according to an embodiment of the invention.

Fig. 14 is a discovery information field in a registration request message according to another embodiment of the present invention.

Fig. 15 is a discovery information field in a registration request message according to yet another embodiment of the present invention.

Fig. 16 is a discovery information field in a registration request message according to yet another embodiment of the present invention.

Fig. 17 is a discovery information field in a registration request message according to yet another embodiment of the present invention.

Fig. 18 is a registration message according to an embodiment of the present invention.

Fig. 19 is a registration message according to another embodiment of the present invention.

Fig. 20 is a default channel configuration field in a registration message according to an embodiment of the invention.

Fig. 21 is a registration reply message according to an embodiment of the present invention.

Fig. 22 is a registration reply message according to another embodiment of the present invention.

Fig. 23 is an authorization message according to an embodiment of the invention.

Fig. 24 is an authorization message according to another embodiment of the present invention.

Fig. 25 is a report message according to an embodiment of the present invention.

Fig. 26 is a report message according to another embodiment of the present invention.

Fig. 27 is a multi-part report field in a report message according to an embodiment of the present invention.

Fig. 28 is a sleep grant message according to an embodiment of the present invention.

Fig. 29 is a flowchart illustrating a method of generating and transmitting an authorization message according to an embodiment of the present invention.

Fig. 30 is a flowchart illustrating a method of generating and transmitting a registration request message according to an embodiment of the present invention.

FIG. 31 is a schematic diagram of an apparatus according to an embodiment of the invention.

Detailed Description

It should be understood at the outset that although illustrative implementations of one or more embodiments are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The present invention should in no way be limited to the illustrative embodiments, drawings, and techniques illustrated below, including the exemplary designs and embodiments illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

The following abbreviations and acronyms apply:

ASIC: application-specific integrated circuit (application-specific integrated circuit)

Ch: channel (channel)

CO: central office (Central office)

A CPU: central processing unit (Central processing unit)

And (2) DS: downstream (downstream)

And (4) DSP: digital signal processor (digital signal processor)

EO: electro-optic (electrical-to-optical)

EPON: ethernet PON (Ethernet PON)

EQ: enveloping quanta (a, um)

FCS: frame check sequence (frame check sequence)

FPGA: field programmable gate array (field-programmable gate array)

G: gigabit per second (gigabits per second)

Gb/s: gigabit per second (gigabits per second)

ID: identification (identifier)

IEEE: the Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics Engineers)

LLID: logical Link ID (local Link ID)

MAC: media access control (media access control)

MLID: management Link ID (management Link ID)

MPCPDU: multi-point MAC Control Protocol data unit (Multipoint MAC Control Protocol data unit)

NG-PON: next-generation PON (Next-generation PON)

ns: nanosecond(s)

And (3) ODN: optical distribution network (optical distribution network)

OE: photoelectric (optical-to-electrical)

OLT: optical line terminal (optical line terminal)

ONT: optical network terminal (optical network terminal)

And ONU: optical network unit (optical network unit)

opcode: operation code (operation code)

PLID: physical layer ID (physical layer ID)

PON: passive optical network (passive optical network)

P2 MP: point-to-multipoint (point-to-multipoint)

RAM: random access memory (random-access memory)

RF: radio frequency (radio frequency)

RN: remote node (remote node)

ROM: read-only memory (read-only memory)

RX: receiver unit (receiver unit)

SRAM: static RAM (static RAM)

sync: synchronization (synchronization)

TCAM: triple content-addressable memory (ternary content-addressable memory)

TDM: time-division multiplexing (time-division multiplexing)

TDMA: time-division multiple access (time-division multiplexing access)

TWDM: time-and wavelength-division multiplexing (time-and wavelength-division multiplexing)

TX: emitter unit (transmitter unit)

US: upstream (upstream)

WDM: wavelength-division multiplexing (wavelength-division multiplexing).

Fig. 1 is a schematic diagram of a PON 100. The PON 100 comprises an OLT 110, ONUs 120, and an ODN 130 coupling the OLT 110 to the ONUs 120. The PON 100 is a communication network that may not require active components to distribute data between the OLT 110 and the ONUs 120. Instead, the PON 100 may distribute data between the OLT 110 and the ONUs 120 using passive optical components in the ODN 130.

The OLT 110 communicates with another network and the ONUs 120. Specifically, the OLT 110 acts as an intermediary between the other network and the ONUs 120. For example, the OLT 110 forwards data received from the other network to the ONU 120, and forwards data received from the ONU 120 to the other network. The OLT 110 comprises a transmitter and a receiver. When the other network uses a network protocol different from the protocol used in the PON 100, the OLT 110 includes a converter that converts the network protocol into the PON protocol and converts the PON protocol into the network protocol. The OLT 110 is typically located at a CO isocentric location, but may be located at other suitable locations.

The ODN 130 is a data distribution network that includes fiber optic cables, couplers, splitters, distributors, and other suitable components. These components include passive optical components that do not require power to distribute signals between the OLT 110 and the ONUs 120. Optionally, these components include active components such as optical amplifiers that require power. In the branching configuration shown, the ODN 130 extends from the OLT 110 to the ONUs 120, but the ODN 130 may be configured in any other suitable P2MP configuration.

The ONUs 120 communicate with the OLT 110 and the customer and act as an intermediary between the OLT 110 and the customer. To this end, the ONU 120 includes an optical transceiver that receives an optical signal from the OLT 110, converts the optical signal into an electrical signal, and provides the electrical signal to a customer. The transceiver also receives electrical signals from the customer, converts the electrical signals to optical signals, and transmits the optical signals to the OLT 110. The ONU 120 and the ONT are similar, and these terms may be used interchangeably. ONUs 120 are typically located at distributed locations, such as at customer premises, but they may be located at other suitable locations.

PON 100 is expected to provide enhanced data rates. For this purpose, IEEE P802.3ca/D0.07 "draft for Ethernet amendment Standard, 1 month 2018: physical Layer Specifications and Management Parameters (Draft Standard for Ethernet Transmission and Management for25Gb/s,50Gb/s, and 100Gb/s Passive Optical Networks) ", which are incorporated herein by reference, describe PONs including PONs that implement TDMA, provide data rates of 25Gb/s,50Gb/s, and 100Gb/s PONs. However, there is still a need to better implement discovery and registration in those PONs.

Embodiments of discovery and registration in a multi-channel PON are disclosed herein. Embodiments include messages that implement 25Gb/s,50Gb/s, and 100Gb/s data rates. These messages include discovery authorization messages, registration request messages, registration reply messages, authorization messages, report messages, and dormancy authorization messages.

Fig. 2 is a message sequence diagram 200 illustrating discovery and registration of an ONU 120. Message sequence diagram 200 also shows report and sleep messages. At step 210, the OLT 110 transmits a discovery grant message to the ONUs 120, granting the discovered transmission window and indicating the capabilities of the OLT 110. At step 220, the ONU 120 transmits a registration request message to the OLT 110 requesting to register in the PON 100 and indicating the capabilities of the ONU 120. At step 230, the OLT 110 transmits a registration message to the ONU 120 instructing the ONU 120 to register and assign an ID to the ONU 120. At step 240, the ONU 120 transmits a registration reply message to the OLT 110, replying to the registration message and carrying the same ID. By completing step 240, ONU 120 completes discovery and registration and enters normal operation.

At step 250, the OLT 110 transmits an authorization message to the ONUs 120 authorizing the transmission window for normal transmission. The grant message at step 250 is similar to the discovery grant message at step 210. The authorization message at step 250 may also be referred to as a normal authorization message for purposes of comparison to the discovery authorization message at step 210. At step 260, the ONU 120 transmits a report message indicating the queue status to the OLT 110. Finally, at step 270, the OLT 110 transmits a sleep grant message to the ONU 120 informing the ONU 120 that it will not receive any data for the indicated time period. The discovery grant message in step 210, the registration request message in step 220, the registration message in step 230, the grant message in step 250, and the report message in step 260 are extended as described below. The sleep grant message in step 270 is described as follows.

Fig. 3 is a discovery authorization message 300 according to an embodiment of the invention. The discovery grant message 300 is a standard message that implements the discovery grant message in step 210 of fig. 2. The discovery grant message 300 is similar to the grant message in step 250 of fig. 2, as described below. The discovery grant message 300 includes a 6 octet destination address field 305, a 6 octet source address field 310, a 2 octet length/type field 315, a 2 octet opcode field 320, a 4 octet timestamp field 325, a 1 octet channel assignment field 330, a 4 octet start time field 335, a 3 octet discovery grant length (EQ) field 340, a 2 octet synchronization time field 345, a 2 octet discovery information field 350, a 28 octet pad field 355, and a 4 octet FCS field 360.

The destination address field 305 is the MAC address of the recipient, the port of the recipient, or multiple recipients. In this case, the receiving party is the ONU 120 or one of the receiving parties is the ONU 120. If the MAC address is a MAC address of multiple recipients, the MAC address is a MAC multicast address. The source address field 310 is the MAC address of the port that transmits the message. In this case, the ports are part of the OLT 110. The length/type field 315 indicates a MAC type field value allocated for the ethernet type MAC. The opcode field 320 includes a value indicating the particular MPCPDU being encapsulated. In this case, the opcode field 320 includes a value of 0x0017 indicating that the grant message 300 is found. Timestamp field 325 indicates the local time register at the time the message was transmitted. The start time field 335 indicates the authorized start time. In this case, the authorization is a discovery authorization. The synchronization time field 345 indicates a synchronization time required by the receiver of the OLT 110. The pad field 355 is a null field that includes zero and is ignored upon receipt. The FCS field 360 indicates FCS data. The channel assignment field 330, the discovery grant length (EQ) field 340, and the discovery information field 350 are described below.

Fig. 4 is a discovery grant message 400 according to another embodiment of the present invention. The discovery grant message 400 is a non-standard message that implements the discovery grant message in step 210 of fig. 2. The discovery grant message 400 is similar to the discovery grant message in fig. 3. Specifically, the discovery grant message 400 includes a destination address field 405 of 6 octets, a source address field 410 of 6 octets, a length/type field 415 of 2 octets, an opcode field 420 of 2 octets, a timestamp field 425 of 4 octets, a channel assignment field 430 of 1 octet, a start time field 435 of 4 octets, a flag/grant length (EQ) field 445 of 3 octets, a sync time field 450 of 2 octets, a discovery information field 455 of 2 octets, a fill/reserve field 460 of 26 octets, and an FCS field 465 of 4 octets, which are similar to the destination address field 305, the source address field 310, the length/type field 315, the opcode field 320, the timestamp field 325, the channel assignment field 330, the start time field 335, the timestamp field 320, the channel assignment field 330, the channel assignment field, and the like, respectively, A discovery grant length (EQ) field 340, a synchronization time field 345, a discovery information field 350, a padding field 355, and an FCS field 360.

However, unlike the discovery grant message 300 which includes the opcode field 320 having a value of 0x0017, the opcode field 420 has a value of 0x 0012. In addition, discovery grant message 400 also includes a 2 octet grant LLID field 440. The authorized LLID field 440 indicates a broadcast LLID. The channel assignment field 430, the flag/grant length (EQ) field 445, and the discovery information field 455 are described below.

Fig. 5 is a channel assignment field 500 in a discovery grant message according to an embodiment of the invention. Channel assignment field 500 is a standard field that implements channel assignment field 330 in fig. 3 or channel assignment field 430 in fig. 4. Channel assignment field 500 includes field 505 in bit 0, field 510 in bit 1, field 515 in bit 2, field 520 in bit 3, and field 525 in bits 4 through 7. Field 505 for uplink channel 0, field 510 for uplink channel 1, field 515 for uplink channel 2, field 520 for uplink channel 3, and field 525 reserved for future use. Fields 505, 510, 515, 520 carry a value of 0 to indicate that channel 0, 1, 2, or 3, respectively, is not available for transmission, or a value of 1 to indicate that channel 0, 1, 2, or 3, respectively, is available for transmission.

Fig. 6 is a channel assignment field 600 in a discovery grant message according to another embodiment of the invention. Channel assignment field 600 is a non-standard field that implements channel assignment field 330 in fig. 3 or channel assignment field 430 in fig. 4. Channel assignment field 600 includes field 605 in bit 0, field 610 in bit 1, field 615 in bit 2, field 620 in bit 3, and field 625 in bits 4 through 7. Fields 605, 610, 615, 620 indicate the authorization of channels 0, 1, 2, 3, respectively. Field 625 is ignored upon receipt. Fields 605, 610, 615, 620 carry a value of 0 to indicate that the transmission opportunity is not applicable to channel 0, 1, 2, or 3, respectively, or a value of 1 to indicate that the transmission opportunity is applicable to channel 0, 1, 2, or 3, respectively. The channel assignment field 500 in fig. 5 and the channel assignment field 600 in fig. 6 both indicate transmission characteristics of multiple channels.

Fig. 7 is a discovery grant length (EQ) field 700 in a discovery grant message according to an embodiment of the invention. Alternatively, fig. 7 is a flag/grant length (EQ) field. The discovery grant length (EQ) field 700 is a non-standard field that implements the discovery grant length (EQ) field 340 in fig. 3 or the flag/grant length (EQ) field 445 in fig. 4. The discovery grant length (EQ) field 700 includes a grant length field 705 in bits 0 through 20, a discovery flag field 710 in bit 21, a mandatory reports field 715 in bit 22, and a fragmentation flag field 720 in bit 23.

The grant length field 705 indicates the granted transmission opportunity duration in EQ units. When the grant length (EQ) field 700 is found in the grant message in step 250 of fig. 2, the discovery flag field 710 carries a value of 0; or when the discovery grant length (EQ) field 700 is in the discovery grant message in step 210 of fig. 2, the discovery flag field 710 carries a value of 1. When no action is required, the force report field 715 carries a value of 0; the mandatory reporting field carries a value of 1 when a reporting frame should be issued for an authorized LLID under the corresponding transmission opportunity. When a new fragment is not allowed to be created in the grant, the fragment flag field 720 carries a value of 0; the fragmentation flag field 720 carries a value of 1 when fragmentation in the grant is allowed. Fragmentation refers to the delivery of a single message in different transmission opportunities.

Fig. 8 is a discovery information field 800 in a discovery grant message according to an embodiment of the present invention. The discovery information field 800 is a standard field that implements the discovery information field 350 in fig. 3 or the discovery information field 455 in fig. 4. The discovery information field 800 includes a field 805 in bit 0, a field 810 in bit 1, a field 815 in bit 2, fields 820 in bits 3 through 4, a field 825 in bit 5, a field 830 in bit 6, and a field 835 in bits 7 through 15.

Field 805 is reserved for future use and is ignored upon receipt. A field 810 indicating whether the OLT 110 is 10G capable, which carries a value of 0 when the OLT 110 does not support 10Gb/s reception; this field carries a value of 1 when the OLT 110 supports 10Gb/s reception. A field 815 indicating whether the OLT 110 is 25G capable, which carries a value of 0 when the OLT 110 does not support 25Gb/s reception; this field carries a value of 1 when the OLT 110 supports 25Gb/s reception. Field 820 is reserved for future use and is ignored upon receipt. A field 825 indicating whether the OLT 110 is opening a 10G discovery window, which carries a value of 0 when the OLT 110 is unable to receive 10Gb/s data in the window; this field carries a value of 1 when the OLT 110 can receive 10Gb/s data in the window. A field 830 indicating whether the OLT 110 is opening a 25G discovery window, which carries a value of 0 when the OLT 110 is unable to receive 25Gb/s data in the window; this field carries a value of 1 when the OLT 110 can receive 10Gb/s data in the window. Field 830 is used in conjunction with channel assignment field 330 in fig. 3 or channel assignment field 430 in fig. 4, such that if field 830 carries a value of 1, then ONU 120 can transmit registration request message 220 in any channel indicated in channel assignment field 330 or channel assignment field 430. Field 835 is reserved for future use and is ignored upon receipt.

Fig. 9 is a discovery information field 900 in a discovery grant message according to another embodiment of the present invention. The discovery information field 900 is a non-standard field that implements the discovery information field 350 in fig. 3 or the discovery information field 455 in fig. 4. Discovery information field 900 includes field 905 in bit 0, field 910 in bit 1, field 915 in bits 2 through 3, field 920 in bit 4, field 925 in bit 5, field 930 in bit 6, field 935 in bit 7, field 940 in bit 8, field 945 in bit 9, field 950 in bit 10, field 955 in bit 11, field 960 in bit 12, field 965 in bit 13, field 970 in bit 14, and field 975 in bit 15.

A field 905 indicates whether the OLT 110 has 1G uplink capability, and when the OLT 110 does not support 1Gb/s reception, the field carries a value of 0; this field carries a value of 1 when the OLT 110 supports 10Gb/s reception. A field 910 indicates whether OLT 110 has 10G uplink capability, and when OLT 110 does not support 10Gb/s reception, this field carries a value of 0; this field carries a value of 1 when the OLT 110 supports 10Gb/s reception. A field 915 indicating whether the OLT 110 is 25/50/100G upstream capable, which carries a value of 00 when the OLT 110 does not support 25/50/100Gb/s reception; this field carries a value of 01 when the OLT 110 supports 25Gb/s reception on channel 0; this field carries a value of 10 when OLT 110 supports 50Gb/s reception on channels 0 and 1; this field carries a value of 11 when the OLT 110 supports 100Gb/s reception on channels 0 to 3. A field 920 indicating whether OLT 110 is opening a 1G discovery window, which carries a value of 0 when OLT 110 is unable to receive 1Gb/s data in the window; this field carries a value of 1 when the OLT 110 is able to receive 1Gb/s data in the window. A field 925 indicating whether the OLT 110 is opening a 10G discovery window, which carries a value of 0 when the OLT 110 is unable to receive 10Gb/s data in the window; this field carries a value of 1 when the OLT 110 can receive 10Gb/s data in the window. A field 930 indicating whether the OLT 110 is opening 25/50/100G discovery window, which carries a value of 0 when no 25/50/100G discovery window is open; this field carries the value 1 when the OLT 110 is opening 25/50/100G discovery window. Field 935 is reserved for future use and is ignored upon receipt.

Fields 940, 945, 950, 955 carry a value of 0 to indicate that upstream channel 0, 1, 2, or 3 is powered down by default, respectively, or a value of 1 to indicate that upstream channel 0, 1, 2, or 3 is powered up by default, respectively. Fields 960, 965, 970, 975 carry a value of 0 to indicate that downlink channel 0, 1, 2, or 3 is powered down by default, or a value of 1 to indicate that downlink channel 0, 1, 2, or 3 is powered up by default, respectively. Fields 960, 965, 970, 975 may be optional.

Fig. 10 is a discovery information field 1000 in a discovery grant message according to yet another embodiment of the present invention. The discovery information field 1000 is a non-standard field that implements the discovery information field 350 in fig. 3 or the discovery information field 455 in fig. 4. The discovery information field 1000 is similar to the discovery information field 900 in fig. 9. In particular, the discovery information field 1000 includes fields 1005, 1010, 1015, 1020, 1025, 1030, 1035 that are similar to the fields 905, 910, 915, 920, 925, 930, 935 in the discovery information field 900.

However, unlike the one-bit field 930, the field 1030 is two bits, which carries the value 00 when the OLT 110 is unable to receive 25/50/100G data; this field carries the value 01 when the OLT 110 is opening a 25Gb/s window on channel 0; this field carries a value of 10 when OLT 110 is opening a 50Gb/s window on channels 0 and 1; this field carries a value of 11 when the OLT 110 is opening a 100Gb/s window on channels 0 to 3. Further, unlike the one-bit field 935, the field 1035 is 8 bits. Further, the discovery information field 1000 does not include fields 940, 945, 950, 955, 960, 965, 970, 975. Field 1030 describes channel behavior, so when ONU 120 receives discovery information field 1000 as discovery information field 350 in fig. 3 or discovery information field 455 in fig. 4, ONU 120 can ignore channel assignment field 330 in fig. 3 or channel assignment field 430 in fig. 4, respectively. Since field 1030 indicates the channel to be used, ONU 120 may omit channel assignment field 330 in fig. 3 or channel assignment field 430 in fig. 4.

Fig. 11 is a discovery information field 1100 in a discovery grant message according to yet another embodiment of the present invention. The discovery information field 1100 is a non-standard field that implements the discovery information field 350 in fig. 3 or the discovery information field 455 in fig. 4. The discovery information field 1100 is similar to the discovery information field 1000 in fig. 10. In particular, the discovery information field 1100 includes fields 1105, 1110, 1120, 1125, 1130 that are similar to fields 1005, 1010, 1020, 1025, 1035, respectively.

However, unlike the discovery information field 1000, which indicates 25/50/100G upstream capability in a single field 1010, the discovery information field 1100 indicates 25G, 50G, and 100G upstream capabilities in the 3 fields, fields 1135, 1140, 1145, respectively. Further, unlike the discovery information field 1000, which indicates 25/50/100G discovery windows in a single field 1030, the discovery information field 1100 indicates 25G, 50G, and 100G discovery windows in the 3 fields of fields 1155, 1160, 1165, respectively. Further, the discovery information field 1100 includes 3 additional fields 1115, 1150, 1170 that are reserved for future use and are ignored upon receipt. Because fields 1155, 1160, 1165 indicate 25G, 50G, and 100G discovery windows and thus indicate the use of channels 0, 0 through 1, and 0 through 3, respectively, ONU 120 may omit channel assignment field 330 in fig. 3 or channel assignment field 430 in fig. 4.

Fig. 12 is a registration request message 1200 according to an embodiment of the invention. Registration request message 1200 is a standard message for implementing the registration request message in step 220 of fig. 2. The registration request message 1200 includes a 6 octet destination address field 1205, a 6 octet source address field 1210, a 2 octet length/type field 1215, a 2 octet opcode field 1220, a 4 octet timestamp field 1225, a 1 octet flag field 1230, a 1 octet pending grant field 1235, a 2 octet discovery information field 1240, a 1 octet laser on time field 1245, a 1 octet laser off time field 1250, a 34 octet pad field 1255, and a 4 octet FCS field 1260.

The destination address field 1205, source address field 1210, length/type field 1215, opcode field 1220, timestamp field 1225, pad field 1255, and FCS field 1260 may be as described above. Unlike other registration request messages, the opcode field 1220 has a value of 0x0014 instead of 0x 0004. The flags field 1230 indicates special requirements for registration. The discovery information field 1240 is described below. The laser on time field 1245 indicates the time required for the ONU 120 to turn on its laser at the beginning of the transmission. The laser off time field 1250 indicates the time required for the ONU 120 to turn off its laser at the end of the transmission.

Fig. 13 is a discovery information field 1300 in a registration request message according to an embodiment of the invention. The discovery information field 1300 is a standard field implementing the discovery information field 1240 in fig. 12. The discovery information field 1300 includes a field 1305 in bit 0, a field 1310 in bit 1, a field 1315 in bit 2, a field 1320 in bit 3, a field 1325 in bit 4, a field 1330 in bit 5, a field 1335 in bit 6, and a field 1340 in bits 7 through 15.

A field 1305 indicates whether the ONU 120 has 1G upstream capability, and when the ONU 120 transmitter does not have 1Gb/s capability, the field carries a value of 0; this field carries a value of 1 when the ONU 120 is 1Gb/s capable. A field 1310 indicating whether the ONU 120 has 10G upstream capability, which carries a value of 0 when the ONU 120 transmitter does not have 10Gb/s capability; this field carries a value of 1 when the ONU 120 is 10Gb/s capable. A field 1315 indicating whether the ONU 120 has 25G upstream capability, which carries a value of 0 when the ONU 120 transmitter does not have 25Gb/s capability; this field carries a value of 1 when the ONU 120 is 25Gb/s capable. Field 1320 is reserved for future use and is ignored upon receipt. A field 1325 indicating a 1G registration attempt, which carries a value of 0 when a 1Gb/s registration is not attempted; this field carries the value 1 when attempting a 1Gb/s registration. A field 1330 indicating a 10G registration attempt, which carries a value of 0 when a 10Gb/s registration is not attempted; this field carries the value 1 when a 10Gb/s registration is attempted. A field 1335 indicating a 25G registration attempt, which carries a value of 0 when a 25Gb/s registration is not attempted; this field carries the value 1 when attempting a 25Gb/s registration. Field 1340 is reserved for future use and is ignored upon receipt.

Fig. 14 is a discovery information field 1400 in a registration request message according to another embodiment of the invention. The discovery information field 1400 is a non-standard field that implements the discovery information field 1240 of fig. 12. The discovery information field 1400 is similar to the discovery information field 1300 in fig. 13. Specifically, the discovery information field 1400 includes a field 1405 in bit 0, a field 1410 in bit 1, a field 1415 in bits 2 through 3, a field 1420 in bit 4, a field 1425 in bit 5, a field 1430 in bits 6 through 7, and a field 1435 in bits 8 through 15, which are similar to the fields 1305, 1310, 1315, 1325, 1330, 1335, 1340, respectively.

However, unlike fields 1315, 1335, fields 1415, 1430 add 50/100G information. A field 1415 indicating whether the ONU 120 has 25/50/100G upstream capability, carries a value of 0 when the ONU 120 transmitter does not have 25/50/100Gb/s capability; this field carries a value of 01 when the ONU 120 transmitter is 25Gb/s capable on channel 0; this field carries a value of 10 when the ONU 120 transmitter is 50Gb/s capable on channels 0 and 1; this field carries a value of 11 when the ONU 120 transmitter is 100Gb/s capable on channels 0 to 3. A field 1430 indicates whether there is an 25/50/100G registration attempt, which carries the value 00 when no multi-channel registration is attempted; this field carries a value of 01 when a 25Gb/s registration is attempted on channel 0; this field carries a value of 10 when 50Gb/s registration is attempted on channels 0 and 1; this field carries a value of 11 when a 100Gb/s registration is attempted on channels 0 through 3. Further, the discovery information field 1400 does not include a reserved field between the fields 1415 and 1420.

Fig. 15 is a discovery information field 1500 in a registration request message according to yet another embodiment of the invention. The discovery information field 1500 is a non-standard field that implements the discovery information field 1240 of fig. 12. The discovery information field 1500 is similar to the discovery information field 1300 in fig. 13. Specifically, the discovery information field 1500 includes a field 1505 in bit 0, a field 1510 in bit 1, a field 1515 in bits 2 through 3, a field 1520 in bit 4, a field 1525 in bit 5, a field 1530 in bits 6 through 7, a field 1535 in bit 8, and a field 1555 in bit 12, which are similar to fields 1305, 1310, 1320, 1325, 1330, 1340, 1315, 1335, respectively.

However, unlike the discovery information field 1300, the discovery information field 1500 also includes a field 1540 in bit 9, a field 1545 in bit 10, a field 1550 in bit 11, a field 1560 in bit 13, a field 1565 in bit 14, and a field 1570 in bit 15. A field 1540 indicates whether the ONU 120 has 50G upstream capability, which carries a value of 0 when the ONU 120 transmitter does not have 50Gb/s capability; this field carries a value of 1 when the ONU 120 is 50Gb/s capable. A field 1545 indicating whether the ONU 120 has 100G upstream capability, which carries a value of 0 when the ONU 120 transmitter does not have 100Gb/s capability; this field carries a value of 1 when the ONU 120 is 100Gb/s capable. Field 1550 is reserved for future use and is ignored upon receipt. A field 1560 indicating a 50G registration attempt, which carries a value of 0 when a 50Gb/s registration is not attempted; this field carries the value 1 when a 50Gb/s registration is attempted. A field 1565 indicates a 100G registration attempt, which carries a value of 0 when a 100Gb/s registration is not attempted; this field carries the value 1 when attempting a 100Gb/s registration. Field 1570 is reserved for future use and is ignored upon receipt.

Fig. 16 is a discovery information field 1600 in a registration request message according to yet another embodiment of the invention. The discovery information field 1600 is a non-standard field that implements the discovery information field 1240 in fig. 12. The discovery information field 1600 is similar to the discovery information field 1300 in fig. 13. Specifically, the discovery information field 1600 includes a field 1605 in bit 0, a field 1610 in bit 1, a field 1615 in bit 2, a field 1625 in bit 4, a field 1630 in bit 5, a field 1635 in bit 6, and a field 1665 in bit 12, which are similar to fields 1305, 1310, 1315, 1325, 1330, 1335, 1340, respectively.

However, unlike the discovery information field 1300, the discovery information field 1600 also includes a field 1620 in bit 3, a field 1640 in bit 7, a field 1645 in bit 8, a field 1650 in bit 9, a field 1655 in bit 10, a field 1660 in bit 11, a field 1670 in bit 13, a field 1675 in bit 14, and a field 1680 in bit 15. A field 1620 indicates whether the ONU 120 is multi-channel upstream capable, and carries a value of 0 when the ONU 120 transmitter is not multi-channel capable and a value of 1 when the ONU 120 transmitter is multi-channel capable. A field 1640 indicates a channel 1 registration attempt, which carries a value of 0 when no registration is attempted on channel 1; this field carries a value of 1 when registration is attempted on channel 1. A field 1645 indicates a channel 2 registration attempt, which carries a value of 0 when no registration is attempted on channel 2; this field carries a value of 1 when registration is attempted on channel 2. A field 1650 indicates a channel 3 registration attempt, which carries a value of 0 when no registration is attempted on channel 3; this field carries the value 1 when registration is attempted on channel 3.

Field 1655 indicates whether ONU 120 has channel 1 upstream capability, and carries a value of 0 when ONU 120 does not have upstream channel 1 transmission capability; this field carries a value of 1 when ONU 120 has upstream channel 1 transmission capability. A field 1660 indicating whether ONU 120 has channel 2/3 upstream capability, which carries a value of 0 when ONU 120 does not have upstream channel 2/3 transmission capability; this field carries a value of 1 when the ONU 120 is equipped with upstream channel 2/3 transmission capability. A field 1670 indicates whether the ONU 120 has channel 0 downlink capability, and when the ONU 120 does not have downlink channel 0 transmission capability, the field carries a value of 0; this field carries a value of 1 when ONU 120 has downlink channel 0 transmission capability. A field 1675 indicates whether the ONU 120 has channel 1 downlink capability, and when the ONU 120 does not have downlink channel 1 transmission capability, the field carries a value of 0; this field carries a value of 1 when ONU 120 has downstream channel 1 transmission capability. A field 1670 indicating whether ONU 120 is capable of downstream channel 2/3, which carries a value of 0 when ONU 120 is not capable of downstream channel 2/3; this field carries a value of 1 when the ONU 120 has the capability of transmitting the downstream channel 2/3.

Fig. 17 is a discovery information field 1700 in a registration request message according to yet another embodiment of the present invention. The discovery information field 1700 is a non-standard field that implements the discovery information field 1240 of fig. 12. The discovery information field 1700 is similar to the discovery information field 1600 in fig. 16. Specifically, discovery information field 1700 includes field 1705, field 1710, field 1715, field 1720, field 1725, field 1730, field 1735, field 1750, field 1755, field 1765, field 1770, and field 1775, which are similar to fields 1605, 1610, 1615, 1620, 1625, 1630, 1635, 1675, 1680, 1655, 1660, 1665, respectively. However, unlike fields 1640, 1645, 1650, which indicate a registration attempt with a separate channel, field 1740 indicates a multi-channel registration attempt, which carries a value of 0 when a multi-channel registration is not attempted; this field carries the value 1 when multi-channel registration is attempted. In addition, discovery information field 1700 also includes fields 1745, 1760 that are reserved for future use and are ignored upon receipt.

Fig. 18 is a registration message 1800 according to an embodiment of the invention. Registration request message 1800 is a standard message that implements the registration message in step 230 of fig. 2. The registration message 1800 includes a 6 octet destination address field 1805, a 6 octet source address field 1810, a 2 octet length/type field 1815, a 2 octet opcode field 1820, a 4 octet timestamp field 1825, a 2 octet assigned Port (PLID) field 1830, a 2 octet assigned port (MLID) field 1835, a 1 octet flag field 1840, a 2 octet sync time field 1845, a 1 octet buffer grant response field 1850, a 1 octet laser on time field 1855, a 1 octet laser off time field 1860, a 30 octet padding field 1865, and a 4 octet FCS 1870.

The destination address field 1805, source address field 1810, length/type field 1815, opcode field 1820, timestamp field 1825, flag field 1840, synchronization time field 1845, laser on time field 1855, laser off time field 1860, pad field 1865, and FCS field 1870 may be as described above. An assigned Port (PLID) field 1830 indicates the PLID of the ONU. An assigned port (MLID) field 1835 indicates the MLID of the ONU. The cached grant number response field 1850 indicates a number of future grants that the ONU 120 may cache before activation.

Fig. 19 is a registration message 1900 according to another embodiment of the invention. Registration message 1900 is a non-standard message that implements the registration message in step 230 of fig. 2. The registration message 1900 is similar to the registration message 1800 in fig. 18. Specifically, the registration message 1900 includes a destination address field 1905 of 6 octets, a source address field 1910 of 6 octets, a length/type field 1915 of 2 octets, an opcode field 1920 of 2 octets, a timestamp field 1925 of 4 octets, an assigned Port (PLID) field 1930 of 2 octets, a flag field 1935 of 1 octet, a synchronization time field 1940 of 2 octets, a buffer grant response field 1945 of 1 octet, a target laser on time field 1950 of 1 octet, a target laser off time field 1955 of 1 octet, a fill/reserve field 1965 of 31 octets, and an FCS field 1970 of 4 octets, which are similar to the destination address field 1805, the field source address 1810, the length/type field 1815, the opcode field 1820, the field 1820 of 31 octets, respectively, A timestamp field 1825, an assigned Port (PLID) field 1830, a flag field 1840, a synchronization time field 1845, a buffer grant number response field 1850, a laser on time field 1855, a laser off time field 1860, a padding field 1865, and an FCS field 1870. However, the registration message 1900 includes a 1 octet default channel configuration field 1960 instead of an assigned port (MLID) field 1835. The default channel configuration field 1960 is described below.

Fig. 20 is a diagram illustrating a default channel configuration field 2000 in a registration message according to an embodiment of the invention. The default channel configuration field 2000 is a non-standard field that implements the default channel configuration field 1960 in fig. 19. Default channel configuration field 2000 includes field 2005 in bit 0, field 2010 in bit 1, field 2015 in bit 2, field 2020 in bit 3, field 2025 in bit 4, field 2030 in bit 5, field 2035 in bit 6, and field 2040 in bit 7. Fields 2005, 2010, 2015, 2020 indicate whether downlink channels 0, 1, 2, or 3, respectively, are enabled; when the downlink transmitter of the channel 0, 1, 2 or 3 is disabled, the value of the corresponding field is set to 0; when a channel 0, 1, 2, or 3 downlink transmitter is enabled, the value of the corresponding field is set to 1. The downstream transmitter may be a transmitter in the OLT 110. Fields 2025, 2030, 2035, 2040 indicate whether uplink channels 0, 1, 2, or 3, respectively, are enabled; when the uplink transmitter of the channel 0, 1, 2 or 3 is disabled, the value of the corresponding field is set to 0; when the channel 0, 1, 2 or 3 uplink transmitter is enabled, the value of the corresponding field is set to 1. The upstream transmitter may be a transmitter in the ONU 120. In the default channel configuration field 2000, disable and enable indicate the default state of the transmitter, with disable representing the power-off state of the transmitter. Thus, by transmitting the default channel configuration field 2000 to the ONU 120, the OLT 110 can configure the receiver and transmitter of the ONU 120.

Fig. 21 is a registration reply message 2100, in accordance with an embodiment of the present invention. Registration reply message 2100 is a standard message that implements the registration reply message in step 240 of fig. 2. The registration reply message 2100 includes a 6 octet destination address field 2105, a 6 octet source address field 2110, a 2 octet length/type field 2115, a 2 octet opcode field 2120, a 4 octet timestamp field 2125, a 1 octet flag field 2130, a 2 octet assigned port response (PLID) field 2135, a 2 octet assigned port response (MLID) field 2140, a 2 octet synchronous time response field 2145, a 33 octet padding field 2150, and a 4 octet FCS field 2155.

The destination address field 2105, source address field 2110, length/type field 2115, opcode field 2120, timestamp field 2125, flag field 2130, padding field 2150, and FCS field 2155 may be as described above. Assigned port response (PLID) field 2135 indicates the PLID that ONU 120 receives in assigned Port (PLID) field 1830 in fig. 18 or assigned Port (PLID) field 1930 in fig. 19. An assigned port response (MLID) field 2140 indicates the MLID that the ONU 120 receives in the assigned port (MLID) field 1835 in fig. 18. The synchronization time response field 2145 indicates the synchronization time required by the OLT 110 as advertised in advance. For example, the required synchronization time is advertised in advance in the synchronization time field 1845 in fig. 18 or the synchronization time field 1940 in fig. 19.

Fig. 22 is a registration reply message 2200 according to another embodiment of the present invention. Registration reply message 2200 is a non-standard message that implements the registration reply message in step 240 of fig. 2. Registration reply message 2200 is similar to registration reply message 2100 in fig. 21. Specifically, the registration reply message 2200 includes a destination address field 2205 of 6 octets, a source address field 2210 of 6 octets, a length/type field 2215 of 2 octets, an opcode field 2220 of 2 octets, a timestamp field 2225 of 4 octets, a flag field 2230 of 1 octet, an assigned port response (PLID) field 2235 of 2 octets, a synchronization time response field 2240 of 2 octets, a fill/reserve field 2250 of 34 octets, and an FCS field 2255 of 4 octets, which are similar to the destination address field 2205, the source address field 2110, the length/type field 2115, the opcode field 2120, the timestamp field 2125, the flag field 2130, the assigned port response (PLID) field 2135, the assigned port response (MLID) field 2140, the synchronization time response field 2145, the sync time response field 2135, the length/type field 2215 of 2 octets, the sync time response field 2220 of 2 octets, the fill/reserved field 2250 of 34 octets, and the FCS, Padding field 2150, and FCS field 2155. However, the registration reply message 2200 includes a 1-octet default channel configuration response field 2245 instead of the assigned port response (MLID) field 2140. Default channel configuration response field 2245 indicates the value that ONU 120 receives in default channel configuration field 1960 in fig. 19.

Fig. 23 is an authorization message 2300, according to an embodiment of the invention. Authorization message 2300 is a standard message that implements the authorization message in step 250 of fig. 2. The grant message 2300 includes a destination address field 2303 of 6 octets, a source address field 2305 of 6 octets, a length/type field 2307 of 2 octets, an opcode field 2310 of 2 octets, a timestamp field 2313 of 4 octets, a channel assignment field 2315 of 1 octet, a grant start time field 2317 of 4 octets, an LLID #1 field 2320 of 0 or2 octets, a grant length #1 field 2323 of 0 or 3 octets, a LLID #2 field 2325 of 0 or2 octets, a grant length #2 field 2327 of 0 or 3 octets, a LLID #3 field 0 of 0 or2 octets, a grant length #3 field 2333 of 0 or 3 octets, a LLID #4 field 2335 of 0 or2 octets, a grant length #4 field 2335 of 0 or 3 octets, a grant length #4 field 2337 of 0 or 3 octets, a grant length #3 field 2330 or 2345 of 0 octets, a grant length #2 field 2335 of 0 or 2345, A grant length #5 field of 0 or 3 octets 2343, an LLID #6 field of 0 or2 octets 2345, a grant length #6 field of 0 or 3 octets 2347, an LLID #7 field of 0 or2 octets 2350, a grant length #7 field of 0 or 3 octets 2353, a fill/reserve field of 0 to 30 octets 2355 and an FCS field of 4 octets 2357.

The destination address field 2303, source address field 2305, length/type field 2307, opcode field 2310, timestamp field 2313, fill/reserve field 2355, and FCS field 2357 may be as described above. Channel assignment field 2315 may be the same as channel assignment field 500 in fig. 5 or channel assignment field 600 in fig. 6. The grant start time field 2317 indicates a start time of the grant. In this case, the authorization is that of normal operation. LLID fields 2320, 2325, 2330, 2335, 2340, 2345, 2350 indicate each authorized LLID. The grant length fields 2323, 2327, 2333, 2337, 2343, 2347, 2354 indicate the length of each grant. The length may indicate a duration in EQ. Each of the LLID fields 2320, 2325, 2330, 2335, 2340, 2345, 2350 forms a doublet with its subsequent grant length field 2323, 2327, 2333, 2337, 2343, 2347, 2353. The use of each doublet is optional. The number of octets in the fill/reserve field 2355 may depend on how many doublets are used.

Fig. 24 is an authorization message 2400 according to another embodiment of the invention. Authorization message 2400 is a non-standard message that implements the authorization message in step 250 of fig. 2. The authorization message 2400 is similar to the authorization message 2300 in fig. 23. Specifically, grant message 2400 includes a 6 octet destination address field 2403, a 6 octet source address field 2405, a 2 octet length/type field 2407, a 2 octet opcode field 2410, a 4 octet timestamp field 2413, a 1 octet channel assignment field 2415, a 4 octet start time field 2417, a 2 octet grant LLID #1 field 2420, a 3 octet flag/grant length #1 field 2423, a 0 or2 octet grant LLID #2 field 2425, a 0 or 3 octet flag/grant length #2 field 2427, a 0 or2 octet grant LLID #3 field 2430, a 0 or 3 octet flag/grant length #3 field 2433, a 0 or2 octet grant LLID #4 field 35, a 0 or 3 octet flag/grant length #3 field 2437, a 0 or2 octet field 2437, a 0 or 3 octet grant length field 2437, An authorized LLID #5 field 2440 of 0 or2 octets, a flag/authorized length #5 field 2443 of 0 or 3 octets, an authorized LLID #6 field 2445 of 0 or2 octets, a flag/authorized length #6 field 2447 of 0 or 3 octets, an authorized LLID #7 field 2450 of 0 or2 octets, a flag/authorized length #7 field 243 of 0 or 3 octets, a fill/reserve field 2455 of 0 to 30 octets, and an FCS field 2457 of 4 octets, which are similar to the destination address field 2303, the source address field 2305, the length/type field 2307, the codope field 2310, the timestamp field 2313, the channel assignment field 2315, the authorized start time field 2317, the LLID #1 field 2320, the authorized length #1 field 2323, the LLID #2 field 2325, the authorized length #2 field 2327, LLID #3 field 2330, grant length #3 field 2333, LLID #4 field 2335, grant length #4 field 2337, LLID #5 field 2340, grant length #5 field 2343, LLID #6 field 2345, grant length #6 field 2347, LLID #7 field 2350, grant length #7 field 2353, padding/reserved field 2355, and FCS field 2357.

However, unlike LLID #1 field 2320 of 0 or2 octets, authorized LLID #1 field 2420 is 2 octets. Further, unlike the grant length #1 field 2323 of 0 or 3 octets, the flag/grant length #1 field 2423 is 3 octets. Further, unlike the grant length #1 field 2323, the grant length #2 field 2327, the grant length #3 field 2333, the grant length #4 field 2337, the grant length #5 field 2343, the grant length #6 field 2347, and the grant length #7 field 2353, the flag/grant length #1 field 2423, the flag/grant length #2 field 2427, the flag/grant length #3 field 2433, the flag/grant length #4 field 2437, the flag/grant length #5 field 2443, the flag/grant length #6 field 2447, and the flag/grant length #7 field 2453 may include 3 one-bit fields 710, 715, 720 and 21 bits of the grant length in fig. 7.

Fig. 25 is a report message 2500 in accordance with an embodiment of the present invention. Report message 2500 is a standard message that implements the report message in step 260 of fig. 2. The report message 2500 includes a 6 octet destination address field 2503, a 6 octet source address field 2505, a 2 octet length/type field 2507, a 2 octet opcode field 2510, a 4 octet timestamp field 2513, a 1 octet number of non-empty queues field 2515, a 4 octet reporting time field 2517, a 2 octet LLID #1 field 2520, a 3 octet queue length #1 field 2523, a 2 octet LLID #2 field 2525, a 3 octet queue length #2 field 2527, a 2 octet LLID #3 field 2530, a 3 octet queue length #3 field 2533, a 2 octet LLID #4 field 2535, a 3 octet queue length #4 field 2537, a 2 octet LLID #5 field 2540, a 3 octet #3 field 2543, a 2 octet queue length #4 field 2537, a 2 octet LLD #5 field 2540, a 3 octet #3 field 2543, A 2 octet LLID #6 field 2545, a 3 octet queue length #6 field 2547, a 2 octet LLID #7 field 2550, a 3 octet queue length #7 field 2553, a 0 to 35 octet padding field 2555, and a 4 octet FCS field 2557.

The destination address field 2503, source address field 2505, length/type field 2507, opcode field 2510, timestamp field 2513, pad field 2555, and FCS field 2557 may be as described above. The number of non-empty queues field 2515 indicates the total number of non-empty queues for all LLIDs in ONU 120. The report time field 2517 indicates the time when the queue information of the fields 2520 to 2553 is collected in the ONU 120. The LLID fields 2520, 2525, 2530, 2535, 2540, 2545, 2550 indicate the LLID for which the queue length fields 2523, 2527, 2533, 2537, 2543, 2547, 2553 apply. The queue length fields 2523, 2527, 2533, 2537, 2543, 2547, 2553 indicate the length of the queue in EQ. Each of the LLID fields 2520, 2525, 2530, 2535, 2540, 2545, 2550 forms a duplet with its subsequent queue length field 2523, 2527, 2533, 2537, 2543, 2547, 2553. The use of each doublet is optional. The number of octets in the padding field 2555 may depend on how many doublets are used.

Fig. 26 is a report message 2600 in accordance with another embodiment of the present invention. Report message 2600 is a non-standard message that implements the report message in step 260 of fig. 2. Report message 2600 is similar to report message 2500 in fig. 25. Specifically, the report message 2600 includes a 6 octet destination address field 2603, a 6 octet source address field 2605, a 2 octet length/type field 2607, a 2 octet opcode field 2610, a 4 octet timestamp field 2613, a 4 octet report time field 2617, a 2 octet authorized LLID #1 field 2620, a 3 octet queue length #1 field 2623, a 2 octet authorized LLID #2 field 2625, a 3 octet queue length #2 field 2627, a 2 octet authorized LLID #3 field 2630, a 3 octet queue length #3 field 2633, a 2 octet authorized LLID #4 field 2635, a 3 octet queue length #4 field 2637, a 2 octet authorized LLID #5 field 2640, a 3 octet queue length #5 field 2643, A 2 octet authorized LLID #6 field 2645, a 3 octet queue length #6 field 2647, a 2 octet authorized LLID #7 field 2650, a 3 octet queue length #7 field 2653, a 0 octet fill/reserve field 2655, and a 4 octet FCS field 2657, which are similar to the destination address field 2503, the source address field 2505, the length/type field 2507, the opcode field 2510, the timestamp field 2513, the report time field 2517, the LLID #1 field 2520, the queue length #1 field 2523, the LLID #2 field 2525, the authorized length #2 field 2527, the LLID #3 field 2530, the queue length #3 field 2533, the LLID #4 field 2535, the queue length #4 field 2537, the LLID #5 field 2540, the queue length #5 field 2543, the LLID #6 field 2545, the LLID #6 field 2547, the LLID #4 field 2550, and the 4 octet FCS field 2657, respectively, A queue length #7 field 2553, a padding field 2555, and an FCS field. However, the report message 2600 includes a 1 octet multi-part report field 2615 instead of a non-empty number of queues field 2515. The multi-part report field 2615 is described below.

Fig. 27 is a multi-part report field 2700 in a report message, according to an embodiment of the invention. The multi-part report field 2700 is a non-standard field that implements the multi-part report field 2615 in fig. 6. The multipart report field 2700 includes a field 2705 of bits 0 to 3 and a field 2710 of bits 4 to 7. Field 2705 indicates the number of reports in the message and is an optional field. Field 2710 indicates the number of report messages remaining in ONU 120.

Fig. 28 is a sleep grant message 2800 according to an embodiment of the invention. Sleep grant message 2800 is a non-standard message that implements the sleep grant message in step 270 of fig. 2. Sleep grant message 2800 indicates that ONU 120 will not receive data for a period of time. The sleep grant message 2800 includes a 6 octet destination address field 2805, a 6 octet source address field 2810, a 2 octet length/type field 2815, a 2 octet opcode field 2820, a 4 octet timestamp field 2825, a 1 octet channel assignment field 2830, a 4 octet start time field 2835, a 2 octet PLID field 2840, a 4 octet sleep length (EQ) field 2845, a 29 octet fill/reserve field 2850, and a 4 octet FCS field 2855.

The destination address field 2805, source address field 2810, length/type field 2815, opcode field 2820, timestamp field 2825, padding/reserved field 2850, and FCS field 2855 may be as described above. Channel assignment field 2830 may be the same as channel assignment field 500 in fig. 5 or channel assignment field 600 in fig. 6. The start time field 2835 indicates the local time at which the channel receiver of ONU 120 enters a low-power state. The PLID field 2840 indicates the PLID of the ONU 120 to which the message 2800 is addressed. The sleep length (EQ) field 2845 indicates the duration in EQ for which the channel receiver remains in a low power state. An EQ corresponds to about 2.56 ns.

First, if not otherwise indicated, the described messages and fields may be as defined in the IEEE 2015 version of "IEEE ethernet standard-section 5", which is incorporated by reference into this text, or may be as defined in the IEEE 802.3 draft. Second, aspects of different messages and fields may be combined in any suitable manner. For example, the discovery grant message may include the fields of the discovery grant message 300 in fig. 3 and the grant LLID field 440 in the discovery grant message 400 in fig. 4. Third, a field of the fields, such as field 505 of channel assignment field 500, may be referred to as a subfield. Fourth, the channel may correspond to a wavelength and may be designated as λ_nWherein n is a non-negative integer. Similarly, different channels may correspond to different wavelengths. Fifth, the message may be referred to as a frame. Sixth, the bit values may be changed in any suitable manner. For example, for field 505 in fig. 5, although a value of 0 is described as indicating that channel 0 may not be used for transmission and a value of 1 is described as indicating that channel 0 may be used for transmission, a value of 0 may also indicate that channel 0 may be used for transmission and a value of 1 may indicate that channel 0 may not be used for transmission.

Fig. 29 is a flow diagram illustrating a method 2900 of generating and transmitting an authorization message, according to an embodiment of the invention. The OLT, e.g., OLT 110, implements method 2900. At step 2910, an authorization message is generated. The authorization message is a discovery authorization message or a normal authorization message. The grant message may include a destination address field, a source address field, a length/type field, an opcode field, a timestamp field, a channel assignment field, a start time field, a grant length field, and a synchronization time field. When the authorization message is a discovery authorization message, the authorization message further includes a discovery information field. The channel assignment field indicates transmission characteristics of a plurality of channels corresponding to different wavelengths. For example, OLT 110 generates discovery grant message 300, discovery grant message 400, grant message 2300, or grant message 2400. Finally, at step 2920, an authorization message is transmitted to the ONU. For example, the OLT 110 transmits the authorization message to the ONUs 120.

Fig. 30 is a flow diagram illustrating a method 3000 of generating and transmitting a registration request message according to an embodiment of the invention. An ONU, such as ONU 120, implements method 3000. At step 3010, a registration request message is generated. For example, ONU 120 generates registration request message 1200. The registration request message may include a destination address field, a source address field, a length/type field, an opcode field, and a discovery information field. The discovery information field may indicate 25G uplink capability and 25G registration attempt. Finally, at step 3020, a registration request message is transmitted to the OLT. For example, the ONU 120 transmits the registration request message to the OLT 110.

Fig. 31 is a schematic diagram of an apparatus 3100 in accordance with an embodiment of the invention. The apparatus 3100 may implement the disclosed embodiments. Apparatus 3100 comprises an ingress port 3110 and RX 3120 for receiving data; a processor, logic unit, baseband unit or CPU3130 for processing data; TX 3140 and egress port 3150 for transmitting data; and a memory 3160 for storing data. Device 3100 may also include OE, EO, or RF components coupled to ingress port 3110, RX 3120, TX 3140, and egress port 3150 for ingress and egress of optical, electrical, or RF signals.

Processor 3130 is any combination of hardware, middleware, firmware, or software. Processor 3130 includes any combination of one or more CPU chips, cores, FGPAs, ASICs, or DSPs. Processor 3130 communicates with ingress port 3110, RX 3120, TX 3140, egress port 3150, and memory 3160. Processor 3130 includes a discovery and registration component 3170 that implements the disclosed embodiments. Thus, the inclusion of the discovery and registration component 3170 may significantly improve the functionality of the device 3100 and enable transition of the device 3100 to different states. Alternatively, memory 3160 stores discovery and registration component 3170 as instructions that processor 3130 executes.

The memory 3160 includes any combination of disks, tape drives, or solid state drives. Device 3100 can use memory 3160 as an overflow data storage device to store programs that device 3100 selects for execution, as well as to store instructions and data that device 3100 reads during program execution. The memory 3160 may be volatile or non-volatile, and may be any combination of ROM, RAM, TCAM, or SRAM.

In an example embodiment, the apparatus 3100 includes a grant message module generating a grant message, which is a discovery grant message or a normal grant message, the grant message including a destination address field, a source address field, a length/type field, an operation code (opcode) field, a timestamp field, a channel assignment field, a start time field, a grant length field, and a synchronization time field, and when the grant message is the discovery grant message, the grant message further including a discovery information field, the channel assignment field indicating transmission characteristics of a plurality of channels corresponding to different wavelengths; and a transmission module for transmitting the authorization message to an Optical Network Unit (ONU). In some embodiments, the apparatus 3100 may include other or additional modules to perform any one or combination of the steps described in the embodiments. Moreover, any additional or alternative embodiments or aspects of the method as illustrated in any of the figures or recited in any claim are also contemplated as including similar modules.

In an example embodiment, the apparatus 3100 includes a registration request module to generate a registration request message including a destination address field, a source address field, a length/type field, an operation code (opcode) field, and a discovery information field indicating 25 gigabit per second (G) upstream capability and a 25G registration attempt; and a transmission module, configured to transmit a registration request message to an Optical Line Terminal (OLT). In some embodiments, the apparatus 3100 may include other or additional modules to perform any one or combination of the steps described in the embodiments. Moreover, any additional or alternative embodiments or aspects of the method as illustrated in any of the figures or recited in any claim are also contemplated as including similar modules.

In an example embodiment, an ONU comprises: a receiver unit for receiving a discovery grant message from the OLT, the discovery grant message including a channel assignment field indicating transmission characteristics of a plurality of channels and a discovery information field indicating a 25G upstream capability and a 25G discovery window; and a processor unit coupled to the receiver unit and configured to process the discovery grant message.

While the present invention provides a number of specific embodiments, it should be understood that the disclosed systems and methods may be embodied in other specific forms without departing from the spirit or scope of the present invention. The present examples are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein. For example, various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.

Moreover, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, components, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may also be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other alterations, substitutions, and alternative examples will now be apparent to those skilled in the art without departing from the spirit and scope of the disclosure.