Discovery and registration in multi-channel passive optical networks (PONs)

Abstract

An ONU includes: a receiver for receiving a discovery grant message from an OLT, the discovery grant message including a channel assignment field and a discovery information field, the channel assignment field indicating transmission characteristics of a plurality of channels, the discovery information field indicating 25G uplink capability and a 25G discovery window; and a processor coupled to the receiver and for processing the discovery grant message. A method implemented in an ONU includes: generating a 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.

Description

[0001] Related applications cross-application

[0002] This invention claims priority to U.S. Non-Provisional Patent Application No. 15 / 960,758, filed April 24, 2018, entitled “Discovery and Registration in a Multi-Channel Passive Optical Network (PON),” which in turn claims priority to U.S. Provisional Patent Application No. 62 / 491,661, filed April 28, 2017, by Futurewei Technologies, Inc., entitled “Discovery and Registration in a Multi-Channel Passive Optical Network (PON),” the contents of which are incorporated herein by reference. Technical Field

[0003] This invention relates to the field of passive optical network (PON) technology, and more specifically, to multi-channel PON. Background Technology

[0004] PON is a system used to provide network access in the last mile, which is the final part of a telecommunications network that provides communication to customers. PON is a P2MP network that includes an OLT at the CO (Customer Center), an ONU at the customer premises, and an ODN (Operational Device Network) that couples the OLT to the ONU. PON can also include an RN (Receiver Unit) located between the OLT and ONU, such as at the end of the road where multiple customers are located.

[0005] NG-PON can combine TDM and WDM to support higher capacity, allowing a single OLT to provide sufficient bandwidth for each user to serve more users. In this type of TWDM PON, WDM PON can be overlaid on top of TDM PON. Therefore, different wavelengths can be multiplexed together to share a single backbone fiber, and each wavelength can be shared by multiple users via TDM. Summary of the Invention

[0006] In one embodiment, the present invention includes an ONU, the ONU comprising: a receiver for receiving a discovery grant message from an OLT, the discovery grant message including a channel assignment field and a discovery information field, the channel assignment field indicating transmission characteristics of a plurality of channels, the discovery information field indicating 25G uplink capability and a 25G discovery window; and a processor coupled to the receiver and for processing the discovery grant message. In some embodiments, the channel assignment field includes: 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 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 within a window; the discovery information field also indicates: 50G uplink capability, 50G discovery window, 100G uplink capability, and 100G discovery window; the discovery grant message includes an opcode field, the opcode field including the value 0x0017; the discovery grant message also includes a grant length field; the grant length field includes: a first field indicating the transmission opportunity duration; a second field indicating the discovery grant message; a third field indicating whether a report frame should be published for the granted LLID; and a fourth field indicating whether fragmentation is allowed; the discovery grant message also includes a granted LLID field indicating broadcast LLID.

[0007] In another embodiment, the present invention includes a method implemented in an OLT, the method comprising: generating an authorization message, the authorization message being either a discovery authorization message or a normal authorization message, the authorization 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, an authorization length field, and a synchronization (sync) time field; when the authorization message is a discovery authorization message, the authorization message further including a discovery information field, the channel assignment field indicating the transmission characteristics of multiple channels corresponding to different wavelengths; and transmitting the authorization message to an ONU. In some embodiments, the channel assignment field includes: 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 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 the duration of the transmission opportunity; a second field indicating the grant message; a third field indicating whether a grant LLID report frame should be issued; and a fourth field indicating whether fragmentation is allowed; the grant message also includes an opcode field, wherein the opcode field includes the value 0x0017.

[0008] In another embodiment, the present invention includes 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 an OLT. In some embodiments, the opcode field includes the value 0x0014; the discovery information field further indicates 50G uplink capability and a 50G registration attempt; and the discovery information field further indicates 100G uplink capability and a 100G registration attempt.

[0009] In another embodiment, the present invention includes an OLT, the OLT comprising: a processor for generating a registration message, the registration message including a destination address field, a source address field, a length / type field, an opcode field, a timestamp field, and a default channel configuration field, the default channel configuration field indicating whether a transmitter in an ONU is enabled or disabled; and a transmitter coupled to the processor and used to transmit the registration message to the ONU. In some embodiments, the default channel configuration field is an octet; the default channel configuration field includes four bits dedicated to the downlink channel; the default channel configuration field includes four bits dedicated to the uplink channel.

[0010] Any of the above embodiments can be combined with any other above embodiments to create new embodiments. These and other features will become clearer in the following detailed description taken in conjunction with the accompanying drawings and claims. Attached Figure Description

[0011] To gain a more thorough understanding of the present invention, reference is now made to the following brief description, which is illustrated in conjunction with the accompanying drawings and specific embodiments, wherein the same reference numerals denote the same parts.

[0012] Figure 1 This is a schematic diagram of a PON.

[0013] Figure 2 This is a message sequence diagram illustrating the discovery and registration of the ONU.

[0014] Figure 3 This is a discovery authorization message according to an embodiment of the present invention.

[0015] Figure 4 This is a discovery authorization message according to another embodiment of the present invention.

[0016] Figure 5 This refers to the channel assignment field in the discovery authorization message according to an embodiment of the present invention.

[0017] Figure 6 This refers to the channel assignment field in the discovery authorization message according to another embodiment of the present invention.

[0018] Figure 7 This refers to the discovery authorization length (EQ) field in a discovery authorization message according to an embodiment of the present invention.

[0019] Figure 8 This refers to the discovery information field in a discovery authorization message according to an embodiment of the present invention.

[0020] Figure 9 This refers to the discovery information field in a discovery authorization message according to another embodiment of the present invention.

[0021] Figure 10 This refers to the discovery information field in a discovery authorization message according to yet another embodiment of the present invention.

[0022] Figure 11 This refers to the discovery information field in a discovery authorization message according to yet another embodiment of the present invention.

[0023] Figure 12 This is a registration request message according to an embodiment of the present invention.

[0024] Figure 13 This refers to the discovery information field in a registration request message according to an embodiment of the present invention.

[0025] Figure 14 This refers to the discovery information field in the registration request message according to another embodiment of the present invention.

[0026] Figure 15 This refers to the discovery information field in a registration request message according to yet another embodiment of the present invention.

[0027] Figure 16 This refers to the discovery information field in a registration request message according to yet another embodiment of the present invention.

[0028] Figure 17 This refers to the discovery information field in a registration request message according to yet another embodiment of the present invention.

[0029] Figure 18 This is a registration message according to an embodiment of the present invention.

[0030] Figure 19 This is a registration message according to another embodiment of the present invention.

[0031] Figure 20 This refers to the default channel configuration field in the registration message according to an embodiment of the present invention.

[0032] Figure 21 This is a registration response message according to an embodiment of the present invention.

[0033] Figure 22 This is a registration response message according to another embodiment of the present invention.

[0034] Figure 23 This is an authorization message according to an embodiment of the present invention.

[0035] Figure 24 This is an authorization message according to another embodiment of the present invention.

[0036] Figure 25 This is a report message according to an embodiment of the present invention.

[0037] Figure 26 This is a report message according to another embodiment of the present invention.

[0038] Figure 27 These are multiple reporting fields in a reporting message according to an embodiment of the present invention.

[0039] Figure 28 This is a hibernation authorization message according to an embodiment of the present invention.

[0040] Figure 29 A flowchart illustrating a method for generating and transmitting authorization messages according to an embodiment of the present invention is provided.

[0041] Figure 30A flowchart illustrating a method for generating and transmitting registration request messages according to an embodiment of the present invention is provided.

[0042] Figure 31 This is a schematic diagram of an apparatus according to an embodiment of the present invention. Detailed Implementation

[0043] First, it should be understood that although illustrative embodiments of one or more examples are provided below, the disclosed systems and / or methods can be implemented using any number of techniques, whether currently known or existing. The invention should not in any way be limited to the illustrative embodiments, drawings, and techniques described below, including the exemplary designs and embodiments illustrated and described herein, but can be modified within the full scope of the appended claims and their equivalents.

[0044] The following abbreviations and acronyms apply:

[0045] ASIC: Application-Specific Integrated Circuit

[0046] Ch: Channel

[0047] CO: Central Office

[0048] CPU: Central Processing Unit

[0049] DS: Downstream

[0050] DSP: Digital Signal Processor

[0051] EO: Electrical-to-optical

[0052] EPON: Ethernet PON

[0053] EQ: Envelope quant(a,um)

[0054] FCS: Frame Check Sequence

[0055] FPGA: Field-Programmable Gate Array

[0056] G: gigabits per second

[0057] Gb / s: gigabits per second

[0058] ID: Identifier

[0059] IEEE: Institute of Electrical and Electronics Engineers

[0060] LLID: Logical Link ID

[0061] MAC: Media Access Control

[0062] MLID: Management Link ID

[0063] MPCPDU: Multipoint MAC Control Protocol dataunit

[0064] NG-PON: Next-generation PON

[0065] ns: nanosecond (s)

[0066] ODN: Optical Distribution Network

[0067] OE: Optical-to-Electrical

[0068] OLT: Optical Line Terminal

[0069] ONT: Optical Network Terminal

[0070] ONU: Optical Network Unit

[0071] opcode: operation code

[0072] PLID: Physical Layer ID

[0073] PON: Passive Optical Network

[0074] P2MP: Point-to-Multipoint

[0075] RAM: Random-access memory

[0076] RF: Radio frequency

[0077] RN: Remote Node

[0078] ROM: Read-only memory

[0079] RX: Receiver unit

[0080] SRAM: Static RAM

[0081] sync: synchronization

[0082] TCAM: Triple content-addressable memory

[0083] TDM: Time-division multiplexing

[0084] TDMA: Time-division multiplexing access

[0085] TWDM: Time-and-wavelength-division multiplexing

[0086] TX: Transmitter unit

[0087] US: Upstream

[0088] WDM: Wavelength-division multiplexing.

[0089] Figure 1This is a schematic diagram of PON 100. PON 100 includes OLT 110, ONU 120, and ODN 130 that couples OLT 110 to ONU 120. PON 100 is a communication network that can distribute data between OLT 110 and ONU 120 without active components. Instead, PON 100 can use passive optical components in ODN 130 to distribute data between OLT 110 and ONU 120.

[0090] The OLT 110 communicates with another network and the ONU 120. Specifically, the OLT 110 acts as an intermediary between the other network and the ONU 120. For example, the OLT 110 forwards data received from the other network to the ONU 120, and data received from the ONU 120 to the other network. The OLT 110 includes a transmitter and a receiver. When the network protocol used by the other network is different from the protocol used in the PON 100, the OLT 110 includes converters that convert the network protocol to the PON protocol and vice versa. The OLT 110 is typically located in a central location such as the CO, but can also be located in other suitable locations.

[0091] 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 ONU 120. Optionally, these components include active components such as optical amplifiers that require power. In the branch configuration shown, the ODN 130 extends from the OLT 110 to the ONU 120, but the ODN 130 can be configured in any other suitable P2MP configuration.

[0092] The ONU 120 communicates with the OLT 110 and customers, acting as an intermediary between the OLT 110 and the customers. To this end, the ONU 120 includes an optical transceiver that receives optical signals from the OLT 110, converts the optical signals into electrical signals, and provides the electrical signals to the customers. The transceiver also receives electrical signals from the customers, converts the electrical signals into optical signals, and transmits the optical signals to the OLT 110. The ONU 120 is similar to the ONT, and these terms are used interchangeably. ONU 120s are typically located in distributed locations, such as at customer premises, but they can also be located in other suitable locations.

[0093] The expectation is that PON 100 will provide enhanced data rates. To this end, IEEE P802.3ca / D0.07, "Draft Standard for Ethernet Amendment: Physical Layer Specifications and Management Parameters for 25Gb / s, 50Gb / s, and 100Gb / s Passive Optical Networks" ("IEEE 802.3 Draft"), published in January 2018, describes PONs, including EPONs that implement TDMA and provide data rates of 25Gb / s, 50Gb / s, and 100Gb / s PONs. The content of this draft is incorporated herein by reference. However, better implementation of discovery and registration is still needed in those PONs.

[0094] This document discloses embodiments of discovery and registration in multi-channel PON. The embodiments include messages for implementing data rates of 25Gb / s, 50Gb / s, and 100Gb / s. These messages include discovery authorization messages, registration request messages, registration messages, registration response messages, authorization messages, report messages, and sleep authorization messages.

[0095] Figure 2 The message sequence diagram 200 illustrates the discovery and registration process of ONU 120. Message sequence diagram 200 also shows report and hibernation messages. At step 210, OLT 110 transmits a discovery authorization message to ONU 120, authorizing the discovery transmission window and indicating the capabilities of OLT 110. At step 220, ONU 120 transmits a registration request message to OLT 110, requesting registration in PON 100 and indicating the capabilities of ONU 120. At step 230, OLT 110 transmits a registration message to ONU 120, instructing ONU 120 to register and assigning an ID to ONU 120. At step 240, ONU 120 transmits a registration response message to OLT 110, responding to the registration message and carrying the same ID. By completing step 240, ONU 120 completes discovery and registration and enters normal operation.

[0096] At step 250, OLT 110 transmits an authorization message to ONU 120, authorizing a normal transmission window. The authorization message at step 250 is similar to the discovery authorization message at step 210. For comparison with the discovery authorization message at step 210, the authorization message at step 250 can also be called a normal authorization message. At step 260, ONU 120 transmits a report message indicating the queue status to OLT 110. Finally, at step 270, OLT 110 transmits a sleep authorization message to ONU 120, notifying ONU 120 that it will not receive any data during the indicated time period. The discovery authorization message in step 210, the registration request message in step 220, the registration message in step 230, the authorization message in step 250, and the report message in step 260 are expanded upon below. The sleep authorization message in step 270 is described below.

[0097] Figure 3 This is a discovery authorization message 300 according to an embodiment of the present invention. The discovery authorization message 300 is for implementing... Figure 2 The standard message for discovering the authorization message in step 210. As described below, the discovery authorization message 300 is similar to... Figure 2 The authorization message in step 250. The discovery authorization 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 authorization length (EQ) field 340, a 2-octet synchronization time field 345, a 2-octet discovery information field 350, a 28-octet padding field 355, and a 4-octet FCS field 360.

[0098] The destination address field 305 is the MAC address of the receiver, the port of the receiver, or multiple receivers. In this case, the receiver is ONU 120 or one of the receivers is ONU 120. If the MAC address is the MAC address of multiple receivers, then the MAC address is a MAC multicast address. The source address field 310 is the MAC address of the port on which the message was transmitted. In this case, the port is part of OLT 110. The length / type field 315 indicates the MAC type field value assigned for Ethernet type MAC. The opcode field 320 includes a value indicating the specific MPCPDU being encapsulated. In this case, the opcode field 320 includes the value 0x0017 indicating a discovery authorization message 300. The timestamp field 325 indicates the local time register at the time of message transmission. The start time field 335 indicates the start time of the authorization. In this case, the authorization is a discovery authorization. The synchronization time field 345 indicates the synchronization time required by the receiver of OLT 110. The padding field 355 is an empty field including zeros and ignored upon reception. The FCS field 360 indicates FCS data. The following describes the channel assignment field 330, the discovery grant length (EQ) field 340, and the discovery information field 350.

[0099] Figure 4 This is a discovery authorization message 400 according to another embodiment of the present invention. The discovery authorization message 400 is for implementing... Figure 2 The non-standard message for discovering authorization in step 210. Discovering authorization message 400 is similar to... Figure 3 The discovery authorization message 400 includes a 6-octet destination address field 405, a 6-octet source address field 410, a 2-octet length / type field 415, a 2-octet opcode field 420, a 4-octet timestamp field 425, a 1-octet channel assignment field 430, a 4-octet start time field 435, a 3-octet flag / authorization length (EQ) field 445, a 2-octet synchronization time field 450, and a 2-octet... The discovery information field 455, the 26-octet padding / reservation field 460, and the 4-octet FCS field 465 are similar to the destination address field 305, source address field 310, length / type field 315, opcode field 320, timestamp field 325, channel assignment field 330, start time field 335, discovery authorization length (EQ) field 340, synchronization time field 345, discovery information field 350, padding field 355, and FCS field 360, respectively.

[0100] However, unlike the discovery grant message 300, which includes an opcode field 320 with a value of 0x0017, the opcode field 420 has a value of 0x0012. Furthermore, the discovery grant message 400 also includes a two-octet grant LLID field 440. The grant 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.

[0101] Figure 5 This refers to the channel assignment field 500 in the discovery authorization message according to an embodiment of the present invention. The channel assignment field 500 is for implementing... Figure 3 Channel assignment field 330 or Figure 4 The channel assignment field 430 is a standard field. The 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 is used 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 is reserved for future use. Fields 505, 510, 515, and 520 can carry a value of 0 to indicate that channels 0, 1, 2, or 3 are unavailable for transmission, or carry a value of 1 to indicate that channels 0, 1, 2, or 3 are available for transmission.

[0102] Figure 6 This refers to the channel assignment field 600 in the discovery authorization message according to another embodiment of the present invention. The channel assignment field 600 is for implementing... Figure 3 Channel assignment field 330 or Figure 4 The channel assignment field 430 is a non-standard field. The 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, and 620 indicate the grant for channels 0, 1, 2, and 3, respectively. Field 625 is ignored upon reception. Fields 605, 610, 615, and 620 can carry a value of 0 to indicate that a transmission opportunity is not applicable to channels 0, 1, 2, or 3, or carry a value of 1 to indicate that a transmission opportunity is applicable to channels 0, 1, 2, or 3, respectively. Figure 5 The channel assignment field 500 and Figure 6 The channel assignment field 600 in the code indicates the transmission characteristics of multiple channels.

[0103] Figure 7 For example, the discovery authorization length (EQ) field 700 in the discovery authorization message according to an embodiment of the present invention. Alternatively, Figure 7 This refers to the Flags / Authorization Length (EQ) field. The EQ field value of 700 was found to be an implementation... Figure 3 The discovery authorization length (EQ) field is 340 or Figure 4 The non-standard field 445 of the flag / authorization length (EQ) field. The discovery authorization length (EQ) field 700 includes the authorization length field 705 in bits 0 to 20, the discovery flag field 710 in bit 21, the mandatory report field 715 in bit 22, and the fragmentation flag field 720 in bit 23.

[0104] The Authorization Length field 705 indicates the duration of the authorized transmission opportunity, in units of EQ. When the Authorization Length (EQ) field 700 is found... Figure 2 When the authorization message in step 250 is found to contain a value of 0 in the flag field 710; or when the authorization length (EQ) field 700 is found to contain a value of 0. Figure 2 In step 210, during the discovery authorization message, the discovery flag field 710 carries a value of 1. When no action is required, the forced report field 715 carries a value of 0; when a report frame should be published for the authorized LLID under the appropriate transport opportunity, the forced report field carries a value of 1. When creating new fragments in the authorization is not allowed, the fragmentation flag field 720 carries a value of 0; when fragmentation is allowed in the authorization, the fragmentation flag field 720 carries a value of 1. Fragmentation refers to transmitting a single message across different transport opportunities.

[0105] Figure 8 This refers to the discovery information field 800 in a discovery authorization message according to an embodiment of the present invention. The discovery information field 800 is for implementing... Figure 3 The discovery information field 350 or Figure 4 The discovery information field 455 is a standard field. The discovery information field 800 includes field 805 in bit 0, field 810 in bit 1, field 815 in bit 2, field 820 in bits 3 to 4, field 825 in bit 5, field 830 in bit 6, and field 835 in bits 7 to 15.

[0106] Field 805 is reserved for future use and will be ignored during reception. Field 810 indicates whether the OLT 110 has 10G capability; if the OLT 110 does not support 10Gb / s reception, this field carries a value of 0; if the OLT 110 supports 10Gb / s reception, this field carries a value of 1. Field 815 indicates whether the OLT 110 has 25G capability; if the OLT 110 does not support 25Gb / s reception, this field carries a value of 0; if the OLT 110 supports 25Gb / s reception, this field carries a value of 1. Field 820 is reserved for future use and will be ignored during reception. Field 825 indicates whether the OLT 110 is currently opening a 10G discovery window; if the OLT 110 cannot receive 10Gb / s data within the window, this field carries a value of 0; if the OLT 110 can receive 10Gb / s data within the window, this field carries a value of 1. Field 830 indicates whether the OLT 110 is opening a 25G discovery window. When the OLT 110 cannot receive 25Gb / s data within the window, this field carries a value of 0; when the OLT 110 can receive 10Gb / s data within the window, this field carries a value of 1. Field 830, along with... Figure 3 Channel assignment field 330 or Figure 4 The channel assignment field 430 is used together such that if field 830 carries a value of 1, ONU 120 can transmit the registration request message 220 on either the channel assignment field 330 or the channel assignment field 430. Field 835 is reserved for future use and is ignored upon reception.

[0107] Figure 9 This refers to the discovery information field 900 in a discovery authorization message according to another embodiment of the present invention. The discovery information field 900 is for implementing... Figure 3 The discovery information field 350 or Figure 4 The discovery information field 455 is a non-standard field. The discovery information field 900 includes field 905 in bit 0, field 910 in bit 1, field 915 in bits 2 and 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.

[0108] Field 905 indicates whether the OLT 110 has 1G uplink capability. When the OLT 110 does not support 1Gb / s reception, this field carries a value of 0; when the OLT 110 supports 10Gb / s reception, this field carries a value of 1. Field 910 indicates whether the OLT 110 has 10G uplink capability. When the OLT 110 does not support 10Gb / s reception, this field carries a value of 0; when the OLT 110 supports 10Gb / s reception, this field carries a value of 1. Field 915 indicates whether the OLT 110 has 25 / 50 / 100G uplink capability. When the OLT 110 does not support 25 / 50 / 100Gb / s reception, this field carries a value of 00; when the OLT 110 supports 25Gb / s reception on channel 0, this field carries a value of 01; when the OLT 110 supports 50Gb / s reception on channels 0 and 1, this field carries a value of 10; when the OLT 110 supports 100Gb / s reception on channels 0 to 3, this field carries a value of 11. Field 920 indicates whether the OLT 110 is opening a 1G discovery window. When the OLT 110 cannot receive 1Gb / s data within the window, this field carries a value of 0; when the OLT 110 can receive 1Gb / s data within the window, this field carries a value of 1. Field 925 indicates whether the OLT 110 is currently opening a 10G discovery window. When the OLT 110 cannot receive 10Gb / s data within the window, this field carries a value of 0; when the OLT 110 can receive 10Gb / s data within the window, this field carries a value of 1. Field 930 indicates whether the OLT 110 is currently opening a 25 / 50 / 100G discovery window. When no 25 / 50 / 100G discovery window is open, this field carries a value of 0; when the OLT 110 is opening a 25 / 50 / 100G discovery window, this field carries a value of 1. Field 935 is reserved for future use and is ignored during reception.

[0109] Fields 940, 945, 950, and 955 carry a value of 0 to indicate that uplink channels 0, 1, 2, or 3 are powered off by default, or carry a value of 1 to indicate that uplink channels 0, 1, 2, or 3 are powered on by default, respectively. Fields 960, 965, 970, and 975 carry a value of 0 to indicate that downlink channels 0, 1, 2, or 3 are powered off by default, or carry a value of 1 to indicate that downlink channels 0, 1, 2, or 3 are powered on by default, respectively. Fields 960, 965, 970, and 975 can be optional.

[0110] Figure 10 This refers to the discovery information field 1000 in a discovery authorization message according to another embodiment of the present invention. The discovery information field 1000 is for implementing... Figure 3 The discovery information field 350 or Figure 4 The discovery information field 455 is a non-standard field. The discovery information field 1000 is similar to... Figure 9The discovery information field 900. Specifically, the discovery information field 1000 includes fields 1005, 1010, 1015, 1020, 1025, 1030, and 1035, which are similar to fields 905, 910, 915, 920, 925, 930, and 935 in the discovery information field 900.

[0111] However, unlike the one-bit field 930, field 1030 is two bits. This field carries a value of 00 when the OLT 110 cannot receive 25 / 50 / 100G data; a value of 01 when the OLT 110 is opening a 25Gb / s window on channel 0; a value of 10 when the OLT 110 is opening a 50Gb / s window on channels 0 and 1; and a value of 11 when the OLT 110 is opening a 100Gb / s window on channels 0 to 3. Furthermore, unlike the one-bit field 935, field 1035 is eight bits. Additionally, the discovery information field 1000 does not include fields 940, 945, 950, 955, 960, 965, 970, and 975. Field 1030 describes channel behavior, therefore, when the ONU 120 receives data as... Figure 3 The discovery information field 350 or Figure 4 When the discovery information field 455 and the discovery information field 1000 are in the ONU 120, they can be ignored respectively. Figure 3 Channel assignment field 330 or Figure 4 The channel assignment field 430 is specified in the ONU 120. Since field 1030 indicates the channel to be used, it can be ignored. Figure 3 Channel assignment field 330 or Figure 4 The channel assignment field 430 in the middle.

[0112] Figure 11 This refers to the discovery information field 1100 in a discovery authorization message according to another embodiment of the present invention. The discovery information field 1100 is for implementing... Figure 3 The discovery information field 350 or Figure 4 The discovery information field 455 is a non-standard field. Discovery information field 1100 is similar to... Figure 10 The discovery information field 1000. Specifically, the discovery information field 1100 includes fields 1105, 1110, 1120, 1125, and 1130, which are similar to fields 1005, 1010, 1020, 1025, and 1035, respectively.

[0113] However, unlike discovery information field 1000, which indicates 25 / 50 / 100G uplink capability in a single field 1010, discovery information field 1100 indicates 25G, 50G, and 100G uplink capability in three fields: 1135, 1140, and 1145. Furthermore, unlike discovery information field 1000, which indicates the 25 / 50 / 100G discovery window in a single field 1030, discovery information field 1100 indicates the 25G, 50G, and 100G discovery window in three fields: 1155, 1160, and 1165. Additionally, discovery information field 1100 includes three additional fields 1115, 1150, and 1170, which are reserved for future use and ignored during reception. Because fields 1155, 1160, and 1165 indicate 25G, 50G, and 100G discovery windows, and therefore indicate the use of channel 0, channel 0 to 1, and channel 0 to 3 respectively, ONU 120 can be ignored. Figure 3 Channel assignment field 330 or Figure 4 The channel assignment field 430 in the middle.

[0114] Figure 12 This is a registration request message 1200 according to an embodiment of the present invention. The registration request message 1200 is for implementing... Figure 2 The standard message for the registration request message in step 220. 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 authorization 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 padding field 1255, and a 4-octet FCS field 1260.

[0115] The destination address field 1205, source address field 1210, length / type field 1215, opcode field 1220, timestamp field 1225, padding field 1255, and FCS field 1260 can be as described above. Unlike other registration request messages, the opcode field 1220 has a value of 0x0014 instead of 0x0004. The flag field 1230 indicates specific registration requirements. The discovery information field 1240 is described below. The laser on time field 1245 indicates the time required for ONU 120 to turn on its laser at the start of transmission. The laser off time field 1250 indicates the time required for ONU 120 to turn off its laser at the end of transmission.

[0116] Figure 13 This refers to the discovery information field 1300 in a registration request message according to an embodiment of the present invention. The discovery information field 1300 is for implementing... Figure 12 The standard field of discovery information field 1240. Discovery information field 1300 includes field 1305 in bit 0, field 1310 in bit 1, field 1315 in bit 2, field 1320 in bit 3, field 1325 in bit 4, field 1330 in bit 5, field 1335 in bit 6, and field 1340 in bits 7 to 15.

[0117] Field 1305 indicates whether the ONU 120 has 1G uplink capability. When the ONU 120 transmitter does not have 1Gb / s capability, this field carries a value of 0; when the ONU 120 has 1Gb / s capability, this field carries a value of 1. Field 1310 indicates whether the ONU 120 has 10G uplink capability. When the ONU 120 transmitter does not have 10Gb / s capability, this field carries a value of 0; when the ONU 120 has 10Gb / s capability, this field carries a value of 1. Field 1315 indicates whether the ONU 120 has 25G uplink capability. When the ONU 120 transmitter does not have 25Gb / s capability, this field carries a value of 0; when the ONU 120 has 25Gb / s capability, this field carries a value of 1. Field 1320 is reserved for future use and is ignored during reception. Field 1325 indicates a 1G registration attempt; it carries a value of 0 when no 1Gb / s registration attempt is made, and a value of 1 when a 1Gb / s registration attempt is made. Field 1330 indicates a 10G registration attempt; it carries a value of 0 when no 10Gb / s registration attempt is made, and a value of 1 when a 10Gb / s registration attempt is made. Field 1335 indicates a 25G registration attempt; it carries a value of 0 when no 25Gb / s registration attempt is made, and a value of 1 when a 25Gb / s registration attempt is made. Field 1340 is reserved for future use and is ignored upon reception.

[0118] Figure 14 This refers to the discovery information field 1400 in the registration request message according to another embodiment of the present invention. The discovery information field 1400 is for implementing... Figure 12 The discovery information field 1240 is a non-standard field. Discovery information field 1400 is similar to... Figure 13The discovery information field 1300. Specifically, the discovery information field 1400 includes field 1405 in bit 0, field 1410 in bit 1, field 1415 in bits 2 and 3, field 1420 in bit 4, field 1425 in bit 5, field 1430 in bits 6 and 7, and field 1435 in bits 8 to 15. These fields are similar to fields 1305, 1310, 1315, 1325, 1330, 1335, and 1340, respectively.

[0119] However, unlike fields 1315 and 1335, fields 1415 and 1430 add 50 / 100G information. Field 1415 indicates whether the ONU 120 has 25 / 50 / 100G uplink capability. When the ONU 120 transmitter does not have 25 / 50 / 100Gb / s capability, this field carries a value of 0; when the ONU 120 transmitter has 25Gb / s capability on channel 0, this field carries a value of 01; when the ONU 120 transmitter has 50Gb / s capability on channels 0 and 1, this field carries a value of 10; when the ONU 120 transmitter has 100Gb / s capability on channels 0 to 3, this field carries a value of 11. Field 1430 indicates whether a 25 / 50 / 100G registration attempt exists. When no multi-channel registration attempt is made, this field carries a value of 00; when a 25Gb / s registration attempt is made on channel 0, this field carries a value of 01; when a 50Gb / s registration attempt is made on channels 0 and 1, this field carries a value of 10; and when a 100Gb / s registration attempt is made on channels 0 through 3, this field carries a value of 11. Furthermore, the discovery information field 1400 does not include the reserved fields between fields 1415 and 1420.

[0120] Figure 15 This refers to the discovery information field 1500 in the registration request message according to another embodiment of the present invention. The discovery information field 1500 is for implementing... Figure 12 The discovery information field 1240 is a non-standard field. Discovery information field 1500 is similar to... Figure 13 The discovery information field 1300. Specifically, the discovery information field 1500 includes field 1505 in bit 0, field 1510 in bit 1, field 1515 in bits 2 and 3, field 1520 in bit 4, field 1525 in bit 5, field 1530 in bits 6 and 7, field 1535 in bit 8, and field 1555 in bit 12. These fields are similar to fields 1305, 1310, 1320, 1325, 1330, 1340, 1315, and 1335, respectively.

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

[0122] Figure 16 This refers to the discovery information field 1600 in the registration request message according to another embodiment of the present invention. The discovery information field 1600 is for implementing... Figure 12 The discovery information field 1240 is a non-standard field. Discovery information field 1600 is similar to... Figure 13 The discovery information field 1300. Specifically, the discovery information field 1600 includes field 1605 in bit 0, field 1610 in bit 1, field 1615 in bit 2, field 1625 in bit 4, field 1630 in bit 5, field 1635 in bit 6, and field 1665 in bit 12. These fields are similar to fields 1305, 1310, 1315, 1325, 1330, 1335, and 1340, respectively.

[0123] However, unlike discovery information field 1300, discovery information field 1600 also includes field 1620 in bit 3, field 1640 in bit 7, field 1645 in bit 8, field 1650 in bit 9, field 1655 in bit 10, field 1660 in bit 11, field 1670 in bit 13, field 1675 in bit 14, and field 1680 in bit 15. Field 1620 indicates whether the ONU 120 has multi-channel uplink capability. When the ONU 120 transmitter does not have multi-channel capability, this field carries a value of 0; when the ONU 120 transmitter has multi-channel capability, this field carries a value of 1. Field 1640 indicates a channel 1 registration attempt. When no registration attempt is made on channel 1, this field carries a value of 0; when a registration attempt is made on channel 1, this field carries a value of 1. Field 1645 indicates a registration attempt on channel 2. This field carries a value of 0 if no registration attempt is made on channel 2, and a value of 1 if a registration attempt is made on channel 2. Field 1650 indicates a registration attempt on channel 3. This field carries a value of 0 if no registration attempt is made on channel 3, and a value of 1 if a registration attempt is made on channel 3.

[0124] Field 1655 indicates whether ONU 120 has uplink capability on channel 1. When ONU 120 does not have uplink capability on channel 1, this field carries a value of 0; when ONU 120 has uplink capability on channel 1, this field carries a value of 1. Field 1660 indicates whether ONU 120 has uplink capability on channel 2 / 3. When ONU 120 does not have uplink capability on channel 2 / 3, this field carries a value of 0; when ONU 120 has uplink capability on channel 2 / 3, this field carries a value of 1. Field 1670 indicates whether ONU 120 has downlink capability on channel 0. When ONU 120 does not have downlink capability on channel 0, this field carries a value of 0; when ONU 120 has downlink capability on channel 0, this field carries a value of 1. Field 1675 indicates whether ONU 120 has downlink capability for channel 1. When ONU 120 does not have downlink channel 1 transmission capability, this field carries a value of 0; when ONU 120 has downlink channel 1 transmission capability, this field carries a value of 1. Field 1670 indicates whether ONU 120 has downlink capability for channel 2 / 3. When ONU 120 does not have downlink channel 2 / 3 transmission capability, this field carries a value of 0; when ONU 120 has downlink channel 2 / 3 transmission capability, this field carries a value of 1.

[0125] Figure 17 This refers to the discovery information field 1700 in the registration request message according to another embodiment of the present invention. The discovery information field 1700 is for implementing... Figure 12 The discovery information field 1240 is a non-standard field. Discovery information field 1700 is similar to... Figure 16 The discovery information field 1600 is included. Specifically, the discovery information field 1700 includes fields 1705, 1710, 1715, 1720, 1725, 1730, 1735, 1750, 1755, 1765, 1770, and 1775, which are similar to fields 1605, 1610, 1615, 1620, 1625, 1630, 1635, 1675, 1680, 1655, 1660, and 1665, respectively. However, unlike fields 1640, 1645, and 1650, which indicate a registration attempt using a single channel, field 1740 indicates a multi-channel registration attempt. This field carries a value of 0 when no multi-channel registration attempt is made, and a value of 1 when a multi-channel registration attempt is made. In addition, the discovery information field 1700 also includes fields 1745 and 1760, which are reserved for future use and ignored upon receipt.

[0126] Figure 18 This is a registration message 1800 according to an embodiment of the present invention. The registration request message 1800 is for implementing... Figure 2 The standard message for the registration message in step 230. 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 assignable port (PLID) field 1830, a 2-octet assignable port (MLID) field 1835, a 1-octet flag field 1840, a 2-octet synchronization 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 field 1870.

[0127] 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, padding field 1865, and FCS field 1870 can be as described above. The assign port (PLID) field 1830 indicates the ONU's PLID. The assign port (MLID) field 1835 indicates the ONU's MLID. The cached license count response field 1850 indicates the number of future licenses that the ONU 120 can cache before activation.

[0128] Figure 19 This is registration message 1900 according to another embodiment of the present invention. Registration message 1900 is for implementing... Figure 2 The registration message in step 230 is a non-standard message. Registration message 1900 is similar to... Figure 18 Registration message 1800. Specifically, registration message 1900 includes a 6-octet destination address field 1905, a 6-octet source address field 1910, a 2-octet length / type field 1915, a 2-octet opcode field 1920, a 4-octet timestamp field 1925, a 2-octet assignable port (PLID) field 1930, a 1-octet flag field 1935, a 2-octet synchronization time field 1940, a 1-octet cache grant response field 1945, a 1-octet target laser on time field 1950, and a 1-octet... The target laser off time field 1955, the 31-byte padding / reservation field 1965, and the 4-byte FCS field 1970 are similar to the destination address field 1805, source address field 1810, length / type field 1815, opcode field 1820, timestamp field 1825, assigned port (PLID) field 1830, flag field 1840, synchronization time field 1845, buffered license response field 1850, laser on time field 1855, laser off time field 1860, padding field 1865, and FCS field 1870. However, registration message 1900 includes a 1-byte default channel configuration field 1960 instead of the assigned port (MLID) field 1835. The default channel configuration field 1960 is described below.

[0129] Figure 20 This refers to the default channel configuration field 2000 in the registration message according to an embodiment of the present invention. The default channel configuration field 2000 is used to implement... Figure 19The default channel configuration field 1960 is a non-standard field. The 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, and 2020 indicate whether downlink channels 0, 1, 2, or 3 are enabled; when the downlink transmitter for channel 0, 1, 2, or 3 is disabled, the value of the corresponding field is set to 0; when the downlink transmitter for channel 0, 1, 2, or 3 is enabled, the value of the corresponding field is set to 1. The downlink transmitter can be a transmitter in the OLT 110. Fields 2025, 2030, 2035, and 2040 indicate whether uplink channels 0, 1, 2, or 3 are enabled, respectively. When the uplink transmitter for channel 0, 1, 2, or 3 is disabled, the value of the corresponding field is set to 0; when the uplink transmitter for channel 0, 1, 2, or 3 is enabled, the value of the corresponding field is set to 1. The uplink transmitter can be a transmitter within the ONU 120. In the default channel configuration field 2000, "disabled" and "enabled" indicate the default state of the transmitter, with "disabled" representing the transmitter's power-off state. Therefore, 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.

[0130] Figure 21 This is a registration response message 2100 according to an embodiment of the present invention. The registration response message 2100 is for implementing... Figure 2 The standard message for the registration response message in step 240. The registration response 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 assign port response (PLID) field 2135, a 2-octet assign port response (MLID) field 2140, a 2-octet synchronization time response field 2145, a 33-octet padding field 2150, and a 4-octet FCS field 2155.

[0131] 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 can be as described above. The Port Assignment Response (PLID) field 2135 indicates that ONU 120 is in Figure 18 The assigned port (PLID) field in 1830 or Figure 19The PLID received in the Assigned Port (PLID) field 1930. The Assigned Port Response (MLID) field 2140 indicates that the ONU 120... Figure 18 The MLID received is in the Assigned Port (MLID) field 1835. The Synchronization Time Response field 2145 indicates the synchronization time required by the OLT110 as previously announced. For example, the required synchronization time is pre-determined in advance. Figure 18 The synchronization time field in 1845 or Figure 19 The synchronization time field in the announcement is from 1940.

[0132] Figure 22 This is a registration response message 2200 according to another embodiment of the present invention. The registration response message 2200 is for implementing... Figure 2 The registration response message in step 240 is a non-standard message. Registration response message 2200 is similar to... Figure 21 The registration response message 2100 is included in the context of the registration response message 2200. Specifically, the registration response message 2200 includes a 6-octet destination address field 2205, a 6-octet source address field 2210, a 2-octet length / type field 2215, a 2-octet opcode field 2220, a 4-octet timestamp field 2225, a 1-octet flag field 2230, a 2-octet assign port response (PLID) field 2235, a 2-octet synchronization time response field 2240, and 34 octets... The group's padding / reservation field 2250 and the four octet FCS field 2255 are similar to the destination address field 2105, source address field 2110, length / type field 2115, opcode field 2120, timestamp field 2125, flag field 2130, assigned port response (PLID) field 2135, assigned port response (MLID) field 2140, synchronization time response field 2145, padding field 2150, and FCS field 2155, respectively. However, the registration response message 2200 includes a one-octet default channel configuration response field 2245 instead of the assigned port response (MLID) field 2140. The default channel configuration response field 2245 indicates to ONU120 that... Figure 19 The value received in the default channel configuration field 1960.

[0133] Figure 23 This is an authorization message 2300 according to an embodiment of the present invention. Authorization message 2300 is for implementation... Figure 2The standard message for the authorization message in step 250. Authorization message 2300 includes a 6-octet destination address field 2303, a 6-octet source address field 2305, a 2-octet length / type field 2307, a 2-octet opcode field 2310, a 4-octet timestamp field 2313, a 1-octet channel assignment field 2315, a 4-octet authorization start time field 2317, a 0 or 2-octet LLID#1 field 2320, a 0 or 3-octet authorization length#1 field 2323, a 0 or 2-octet LLID#2 field 2325, a 0 or 3-octet authorization length#2 field 2327, and a 0 or 2-octet LLID#3 word. Segment 2330, Authorization length of 0 or 3 octets #3 field 2333, LLID #4 of 0 or 2 octets field 2335, Authorization length of 0 or 3 octets #4 field 2337, LLID #5 of 0 or 2 octets field 2340, Authorization length of 0 or 3 octets #5 field 2343, LLID #6 of 0 or 2 octets field 2345, Authorization length of 0 or 3 octets #6 field 2347, LLID #7 of 0 or 2 octets field 2350, Authorization length of 0 or 3 octets #7 field 2353, Padding / Reserved field of 0 to 30 octets 2355, and FCS field of 4 octets 2357.

[0134] The destination address field 2303, source address field 2305, length / type field 2307, opcode field 2310, timestamp field 2313, padding / reservation field 2355, and FCS field 2357 can be as described above. The channel assignment field 2315 can be... Figure 5 The channel assignment field 500 or Figure 6 The channel assignment field 600 is the same as the channel assignment field 600. The license start time field 2317 indicates the start time of the license. In this case, the license is a normal operating license. The LLID fields 2320, 2325, 2330, 2335, 2340, 2345, and 2350 indicate the LLID of each license. The license length fields 2323, 2327, 2333, 2337, 2343, 2347, and 2354 indicate the length of each license. The length can indicate the duration in EQ units. Each of the LLID fields 2320, 2325, 2330, 2335, 2340, 2345, and 2350 forms a tuple with its subsequent license length fields 2323, 2327, 2333, 2337, 2343, 2347, and 2353. The use of each tuple is optional. The number of octets in the padding / reservation field 2355 can depend on how many tuples are used.

[0135] Figure 24 This is an authorization message 2400 according to another embodiment of the present invention. Authorization message 2400 is for implementation... Figure 2 The authorization message in step 250 is a non-standard message. Authorization message 2400 is similar to... Figure 23 The authorization message 2300 is included in the authorization message. Specifically, the authorization 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 authorization LLID#1 field 2420, a 3-octet flag / authorization length#1 field 2423, and an authorization LLID# of 0 or 2 octets. 2. Field 2425, Flags / License Length of 0 or 3 Octets #2. Field 2427, License LLID of 0 or 2 Octets #3. Field 2430, Flags / License Length of 0 or 3 Octets #3. Field 2433, License LLID of 0 or 2 Octets #4. Field 2435, Flags / License Length of 0 or 3 Octets #4. Field 2437, License LLID of 0 or 2 Octets #5. Field 2440, Flags / License Length of 0 or 3 Octets #5. Field 2443, License LLID of 0 or 2 Octets #6. Field 2445, The following fields are specified: Flag / Authorization Length #6 (0 or 3 octets) field 2447; Authorization LLID #7 (0 or 2 octets) field 2450; Flag / Authorization Length #7 (0 or 3 octets) field 2453; Padding / Reservation field (0 to 30 octets) field 2455; and FCS field (4 octets) field 2457. These fields are similar to Destination Address field 2303, Source Address field 2305, Length / Type field 2307, Opcode field 2310, Timestamp field 2313, Channel Assignment field 2315, Authorization Start Time field 2317, and L... The following fields are listed: LID#1 field 2320, Authorization Length #1 field 2323, LLID#2 field 2325, Authorization Length #2 field 2327, LLID#3 field 2330, Authorization Length #3 field 2333, LLID#4 field 2335, Authorization Length #4 field 2337, LLID#5 field 2340, Authorization Length #5 field 2343, LLID#6 field 2345, Authorization Length #6 field 2347, LLID#7 field 2350, Authorization Length #7 field 2353, Padding / Reserved field 2355, and FCS field 2357.

[0136] However, unlike the LLID#1 field 2320, which is 0 or 2 octets, the license LLID#1 field 2420 is 2 octets. Furthermore, unlike the license length #1 field 2323, which is 0 or 3 octets, the flag / license length #1 field 2423 is 3 octets. Additionally, unlike the license length #1 field 2323, license length #2 field 2327, license length #3 field 2333, license length #4 field 2337, license length #5 field 2343, license length #6 field 2347, and license length #7 field 2353, and flag / license length #1 field 2423, flag / license length #2 field 2427, flag / license length #3 field 2433, flag / license length #4 field 2437, flag / license length #5 field 2443, flag / license length #6 field 2447, and flag / license length #7 field 2453 may include... Figure 7 The three one-bit fields 710, 715, and 720, and the 21 bits of the authorized length.

[0137] Figure 25 This is a report message 2500 according to an embodiment of the present invention. Report message 2500 is for implementing... Figure 2 The standard message for the report message in step 260. 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 non-empty queue number field 2515, a 4-octet report 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, and a 2-octet LLID#2 field. The following fields are listed: ID#3 field 2530, queue length #3 field 2533, LLID#4 field 2535, queue length #4 field 2537, LLID#5 field 2540, queue length #5 field 2543, LLID#6 field 2545, queue length #6 field 2547, LLID#7 field 2550, queue length #7 field 2553, padding field 2555 (0 to 35 octets), and FCS field 2557 (4 octets).

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

[0139] Figure 26 This is a report message 2600 according to another embodiment of the present invention. Report message 2600 is for implementing... Figure 2 The non-standard message in step 260 of the report message. Report message 2600 is similar to... Figure 25The report message 2500 is included in the report message. 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, and a 2-octet authorized LLID#2 field. Segment 2625, queue length of 3 octets #2; Field 2627, authorized LLID of 2 octets #3; Field 2630, queue length of 3 octets #3; Field 2633, authorized LLID of 2 octets #4; Field 2635, queue length of 3 octets #4; Field 2637, authorized LLID of 2 octets #5; Field 2640, queue length of 3 octets #5; Field 2643, authorized LLID of 2 octets #6; Field 2645, queue length of 3 octets The column length #6 field 2647, the 2-octet authorized LLID #7 field 2650, the 3-octet queue length #7 field 2653, the 0-octet padding / reservation field 2655, and the 4-octet FCS field 2657 are similar to the destination address field 2503, source address field 2505, length / type field 2507, opcode field 2510, timestamp field 2513, report time field 2517, LLID #1 field 2520, and queue, respectively. The fields are: Length #1 (2523), LLID #2 (2525), Authorization Length #2 (2527), LLID #3 (2530), Queue Length #3 (2533), LLID #4 (2535), Queue Length #4 (2537), LLID #5 (2540), Queue Length #5 (2543), LLID #6 (2545), Queue Length #6 (2547), LLID #7 (2550), Queue Length #7 (2553), Padding field (2555), and FCS field. However, report message 2600 includes a multipart report field 2615, which is a single octet, instead of the non-empty queue number field 2515. The multipart report field 2615 is described below.

[0140] Figure 27 This refers to a multi-part report field 2700 in a report message according to an embodiment of the present invention. The multi-part report field 2700 is for implementing... Figure 6The multipart reporting field 2615 is a non-standard field. Multipart reporting field 2700 includes field 2705 in bits 0 to 3 and field 2710 in bits 4 to 7. Field 2705 indicates the number of reports in the message and is optional. Field 2710 indicates the number of remaining report messages in the ONU 120.

[0141] Figure 28 This is a hibernation authorization message 2800 according to an embodiment of the present invention. The hibernation authorization message 2800 is for implementing... Figure 2 The sleep grant message in step 270 is a non-standard message. The sleep grant message 2800 indicates that the 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 padding / reservation field 2850, and a 4-octet FCS field 2855.

[0142] The destination address field 2805, source address field 2810, length / type field 2815, opcode field 2820, timestamp field 2825, padding / reservation field 2850, and FCS field 2855 can be as described above. The channel assignment field 2830 can be... Figure 5 The channel assignment field 500 or Figure 6 The channel assignment field 600 is the same as in the previous example. The start time field 2835 indicates the local time when the ONU120's channel receiver enters a low-power state. The PLID field 2840 indicates the PLID of the ONU120 to be addressed by message 2800. The sleep length (EQ) field 2845 indicates the duration, in EQ units, for which the channel receiver remains in a low-power state. One EQ is equivalent to approximately 2.56 ns.

[0143] First, unless otherwise indicated, the described messages and fields may be as defined in the IEEE 2015 edition of “IEEE Ethernet Standards – Section 5,” which is incorporated herein by reference, or as defined in the IEEE 802.3 draft. Second, aspects of different messages and fields may be combined in any suitable manner. For example, a discovery authorization message may include… Figure 3 The fields of the discovery authorization message 300 and Figure 4The authorization LLID field 440 in the discovery authorization message 400. Third, fields within fields, such as field 505 in the channel assignment field 500, can be called subfields. Fourth, the channel can correspond to a wavelength and can be specified as λ. n , where n is a non-negative integer. Similarly, different channels can correspond to different wavelengths. Fifth, a message can be called a frame. Sixth, bit values ​​can be changed in any suitable way. For example, for Figure 5 In field 505, although the value 0 is described as indicating that channel 0 cannot be used for transmission, and the value 1 is described as indicating that channel 0 can be used for transmission, the value 0 can also indicate that channel 0 can be used for transmission, and the value 1 can indicate that channel 0 cannot be used for transmission.

[0144] Figure 29 A flowchart illustrating a method 2900 for generating and transmitting an authorization message according to an embodiment of the present invention is provided. An OLT, such as OLT 110, implements method 2900. At step 2910, an authorization message is generated. This authorization message is either a discovery authorization message or a normal authorization message. The authorization 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, an authorization length field, and a synchronization time field. When the authorization message is a discovery authorization message, it also includes a discovery information field. The channel assignment field indicates the transmission characteristics of multiple channels corresponding to different wavelengths. For example, OLT 110 generates discovery authorization message 300, discovery authorization message 400, authorization message 2300, or authorization message 2400. Finally, at step 2920, the authorization message is transmitted to an ONU. For example, OLT 110 transmits the authorization message to ONU 120.

[0145] Figure 30 A flowchart illustrating a method 3000 for generating and transmitting a registration request message according to an embodiment of the present invention is provided. 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 a 25G registration attempt. Finally, at step 3020, the registration request message is transmitted to the OLT. For example, ONU 120 transmits the registration request message to OLT 110.

[0146] Figure 31This is a schematic diagram of a device 3100 according to an embodiment of the present invention. The device 3100 can implement the disclosed embodiments. The device 3100 includes an input port 3110 and an RX 3120 for receiving data; a processor, logic unit, baseband unit, or CPU 3130 for processing data; a TX 3140 and an output port 3150 for transmitting data; and a memory 3160 for storing data. The device 3100 may further include an OE component, an EO component, or an RF component coupled to the input port 3110, RX 3120, TX 3140, and output port 3150 for the input and output of optical signals, electrical signals, or RF signals.

[0147] Processor 3130 is any combination of hardware, middleware, firmware, or software. Processor 3130 includes any combination of one or more CPU chips, cores, FPGAs, ASICs, or DSPs. Processor 3130 communicates with ingress port 3110, RX 3120, TX 3140, egress port 3150, and memory 3160. Processor 3130 includes discovery and registration components 3170 that implement the disclosed embodiments. Therefore, including discovery and registration components 3170 significantly improves the functionality of device 3100 and enables transitions of device 3100 to different states. Alternatively, memory 3160 stores discovery and registration components 3170 as instructions, which processor 3130 executes.

[0148] Memory 3160 includes any combination of a disk, tape drive, or solid-state drive. Apparatus 3100 may use memory 3160 as an overflow data storage device to store programs that apparatus 3100 selects to execute, and to store instructions and data read by apparatus 3100 during program execution. Memory 3160 may be volatile or non-volatile, and may be any combination of ROM, RAM, TCAM, or SRAM.

[0149] In one example embodiment, apparatus 3100 includes an authorization message module for generating an authorization message, which may be 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. When the authorization message is a discovery authorization message, it also includes a discovery information field. The channel assignment field indicates the transmission characteristics of multiple channels corresponding to different wavelengths. The apparatus also includes a transmission module for transmitting the authorization message to an optical network unit (ONU). In some embodiments, apparatus 3100 may include other or additional modules for performing any step or combination of steps described in the embodiments. Furthermore, any additional or alternative embodiments or aspects of the methods described as shown in any of the figures or in any of the claims are also contemplated to include similar modules.

[0150] In one example embodiment, apparatus 3100 includes a registration request module for generating a registration request message, the 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, the discovery information field indicating a 25 gigabit per second (G) uplink capability and a 25G registration attempt; and a transmission module for transmitting the registration request message to an optical line terminal (OLT). In some embodiments, apparatus 3100 may include other or additional modules for performing any or a combination of steps described in the embodiments. Furthermore, any additional or alternative embodiments or aspects of the methods described as shown in any of the figures or in any of the claims are also contemplated to include similar modules.

[0151] In one example embodiment, the ONU includes: a receiver unit for receiving a discovery grant message from the OLT, the discovery grant message including a channel assignment field and a discovery information field, the channel assignment field indicating the transmission characteristics of multiple channels, and the discovery information field indicating 25G uplink capability and 25G discovery window; and a processor unit coupled to the receiver unit for processing the discovery grant message.

[0152] While this invention provides several specific embodiments, it should be understood that the disclosed systems and methods can also be embodied in many other specific forms without departing from the spirit or scope of the invention. Examples of the invention should be considered illustrative rather than restrictive, and the invention is not limited to the details set forth herein. For example, various elements or components may be combined or integrated in another system, or certain features may be omitted or not implemented.

[0153] Furthermore, without departing from the scope of the invention, the technologies, systems, subsystems, and methods described and illustrated as discrete or separate in the various embodiments can be combined or incorporated with other systems, components, technologies, or methods. Other items shown or discussed as coupled or directly coupled or communicating with each other may also be indirectly coupled or communicating via an interface, device, or intermediate component in an electrical, mechanical, or other manner. Other variations, substitutions, and alterations will be apparent to those skilled in the art and do not depart from the spirit and scope of the disclosure herein.

Claims

1. An optical network unit (ONU), characterized in that, include: The receiver is used to receive a discovery grant message from an optical line terminal (OLT). The discovery grant message includes an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field. The channel assignment field indicates the transmission characteristics of multiple channels corresponding to different wavelengths. The discovery information field indicates the uplink data rate supported by the OLT and the discovery window. The discovery authorization length field includes a first field and a second field, wherein the first field is used to indicate the duration of the transmission opportunity, and the second field is used to indicate whether fragmentation is allowed; as well as A processor, coupled to the receiver, is used to process the discovery authorization message.

2. The ONU according to claim 1, characterized in that, The channel assignment field includes: The first field indicates whether uplink channel 0 can be used for transmission; and The second field indicates whether uplink channel 1 can be used for transmission.

3. The ONU according to claim 2, characterized in that, The channel assignment field also includes: The third field indicates whether uplink channel 2 can be used for transmission; The fourth field indicates whether uplink channel 3 can be used for transmission; and The fifth field is a reserved field.

4. The ONU according to any one of claims 1 to 3, characterized in that, The discovery information fields include: The first field indicates whether the OLT supports 25 gigabits per second (Gb / s) reception; and The second field indicates whether the OLT can receive 25Gb / s of data within the window.

5. The ONU according to claim 4, characterized in that, The discovery information field also indicates: 50G uplink capability 50G discovery window 100G uplink capability, and 100G discovery window.

6. The ONU according to claim 1, characterized in that, The discovery authorization length field also includes: The third field indicates the discovery authorization message; and The fourth field indicates whether a report frame should be issued for the Authorized Logical Link Identifier (LLID).

7. The ONU according to claim 1, characterized in that, The discovery authorization message also includes an authorization logical link identifier (LLID) field indicating the broadcast LLID.

8. A method implemented in an optical line terminal (OLT), characterized in that, The method includes: A discovery grant message is generated, which includes an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field. The channel assignment field indicates the transmission characteristics of multiple channels corresponding to different wavelengths. The discovery information field indicates the uplink data rate supported by the OLT and the discovery window. The discovery authorization length field includes a first field and a second field, wherein the first field indicates the duration of the transmission opportunity, and the second field indicates whether fragmentation is allowed; and The authorization message is transmitted to the optical network unit (ONU).

9. The method according to claim 8, characterized in that, The channel assignment field includes: The first field indicates whether uplink channel 0 can be used for transmission; and The second field indicates whether uplink channel 1 can be used for transmission.

10. The method according to claim 9, characterized in that, The channel assignment field also includes: The third field indicates whether uplink channel 2 can be used for transmission; The fourth field indicates whether uplink channel 3 can be used for transmission; and The fifth field is a reserved field.

11. The method according to claim 8, characterized in that, The discovery authorization length field also includes: The third field indicates the authorization message; and The fourth field indicates whether a report frame should be issued for the Authorized Logical Link Identifier (LLID).

12. An optical line terminal (OLT), characterized in that, include: The processor is used to generate a discovery grant message, which includes an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field. The channel assignment field indicates the transmission characteristics of multiple channels corresponding to different wavelengths. The discovery information field indicates the uplink data rate supported by the OLT and the discovery window. The discovery authorization length field includes a first field and a second field, wherein the first field is used to indicate the duration of the transmission opportunity, and the second field is used to indicate whether fragmentation is allowed; as well as The transmitter is coupled to the processor and is used to transmit the discovery authorization message to the optical network unit (ONU).

13. The OLT according to claim 12, characterized in that, The channel assignment field includes: The first field indicates whether uplink channel 0 can be used for transmission; and The second field indicates whether uplink channel 1 can be used for transmission.

14. The OLT according to claim 13, characterized in that, The channel assignment field also includes: The third field indicates whether uplink channel 2 can be used for transmission; The fourth field indicates whether uplink channel 3 can be used for transmission; and The fifth field is a reserved field.

15. The OLT according to claim 12, characterized in that, The discovery authorization length field also includes: The third field indicates the authorization message; and The fourth field indicates whether a report frame should be issued for the Authorized Logical Link Identifier (LLID).

16. A method implemented in an optical network unit (ONU), characterized in that, The method includes: The system receives a discovery grant message from the optical line terminal (OLT). This discovery grant message includes an operation code (opcode) field, a channel assignment field, a discovery information field, and a discovery grant length field. The channel assignment field indicates the transmission characteristics of multiple channels corresponding to different wavelengths. The discovery information field indicates the uplink data rate supported by the OLT and the discovery window. The discovery authorization length field includes a first field and a second field, wherein the first field indicates the duration of the transmission opportunity, and the second field indicates whether fragmentation is allowed; and The discovery authorization message is processed, and the OLT is communicated according to the channel and rate indicated by the discovery authorization message.

17. The method according to claim 16, characterized in that, The channel assignment field includes: The first field indicates whether uplink channel 0 can be used for transmission; and The second field indicates whether uplink channel 1 can be used for transmission.

18. The method according to claim 16 or 17, characterized in that, The discovery information fields include: The first field indicates whether the OLT supports 25 gigabits per second (Gb / s) reception; and The second field indicates whether the OLT can receive 25Gb / s of data within the window.

19. The method according to claim 18, characterized in that, The discovery information field also indicates: 50G uplink capability 50G discovery window 100G uplink capability, and 100G discovery window.

20. The method according to claim 16, characterized in that, The discovery authorization length field also includes: The third field indicates the discovery authorization message; and The fourth field indicates whether a report frame should be issued for the Authorized Logical Link Identifier (LLID).

21. The method according to claim 16, characterized in that, The discovery authorization message also includes an authorization logical link identifier (LLID) field indicating the broadcast LLID.

Images