Patent Application
20070263656
The present disclosure provides a method for the master to configure the slaves for use in a PON system as shown in
201. the slaves generating the ME Support List ME based on their individual hardware configuration;
202. the master obtaining the ME Support List ME from the slaves; and
203. the master configuring the slaves based on the ME Support List ME.
This example describes the present disclosure using the OLT as the master and the ONT as the slave. The method of the present disclosure allows the ONTs in the PON system to automatically generate the ME Support List ME. That is, numbering the supported MEs based on their individual hardware configuration when the ONTs are initialized or have a hardware change, or before or during the configuration. Once the list is generated and depending on the system configuration, the OLT may obtain the current ME list for the ONTs, e.g. the collection of the ME types (referred to as the ME hereinafter) supported by the ONT in three ways:
a. Referring to
b. Referring to
c. Referring to
In the above three methods, information exchange between the ONTs and the OLT is made through passive optical dividing components, and the ONTs may use the MIB Upload or Get Response message for the OMCI standard to report the ME. Upon receiving either message, the OLT knows the ME collection currently generated by the ONT.
The method of the present disclosure allows the ONT to create a special ME type to describe the various MEs it supports. For example, if M types of MEs are supported locally, N types of MEs may be created in response to the Create message received from the OLT. In the above Step 201, the ONT creates the special ME type, and the OLT obtains the special ME type through one of the three methods described above. The OLT knows various MEs supported by the ONT simply by resolving this special ME type and is able to do the subsequent service configuration based on this information so that no ONT incompatible Create messages are initiated from the OLT.
The above method is further described below in conjunction with a specific application.
In the system, there is one OLT and a plurality of ONTs (A, B and C). When the ONTs are initialized or experience a hardware change, the ONTs will generate a new ME to describe the various MEs supported by the ONTs based on their current hardware configuration.
For example, if ONT A supports an Ethernet port whose attributes need to be configured under the control of the OLT, ONT A should support a ME for the Physical Path Termination Point Ethernet user network interface (UNI). In the GPON protocol, the ME for the Physical Path Termination Point Ethernet UNI is numbered 11. The ONT may adopt one of the above three methods to inform the OLT that it supports the ME for the Physical Path Termination Point Ethernet UNI so that the OLT is able to configure the attributes for the Ethernet port in the ONT.
In another example, ONTs B and C support the Plain Old Telephone Service (POTS) port. In the GPON protocol, the ME for the Physical Path Termination Point POTS UNI is numbered 53, and therefore ONT B and C should support ME number 53.
In still another example, ONT A supports creating the ME for the Multicast GEM Interworking Termination Point from the OLT. This type of ME is numbered 281, and both ONT B and C do not support creating this type of ME. The difference in MEs between ONT A and ONTs B and C may be due to different equipment models or different manufacturers, and this is unknown to the OLT in advance. In this case, ONT A supports creating ME type number 281 and ONT B and C do not support creating ME type number 281.
In the present disclosure, all ONTs (A, B, and C) generate a special ME type, e.g. ME Support List ME, and here we assume it is numbered 400. All of the ONTs (A, B and C) support ME type number 400.
The following further defines the ME type numbered 400. The content of the ME is a collection of ME numbers, which are supported or whose creation is supported by the ONT. The specific attribute should include a total and listing data structure that lists the ME numbers that are supported or whose creation is supported by the ONT.
The following table shows the content of the ME Support List ME number 400:
As described and defined in the above, the OLT may obtain the ME collection for ONTs A, B and C in three ways, as shown in the following table.
Once the OLT gets the information shown in the above table, it knows the ME types supported by ONTs A, B and C, or more exactly, it knows the hardware capability and service support capability of ONTs A, B and C. This information will help the OLT to deploy the ONTs and configure the service attributes for the ONTs. For example, the OLT knows that ONT A supports the Ethernet port and multicast service corresponding to the Multicast GEM Interworking Termination Point ME, and that ONT B and C support the POTS port and POTS services.
The OLT user can see the ME Support List ME for ONTs A, B and C from the management interface (command lines or graphic interface), and knows that ONT A supports the Ethernet port while ONTs B and C support the POTS port. The user can then configure ONT A with the Ethernet port related attributes, such as self-negotiation and rate selection including 10 Megabits per second (Mbps) or 100 Mbps, and configure ONTs B and C with the POTS port related attributes, such as load impedance and gain.
In particular, when the user configures ONTs B and C with multicast service, the OLT resolves the user command and finds out that there is a need to create the Multicast GEM Interworking Termination Point ME number 281 on ONTs B and C. As the ME collection for ONTs B and C does not include the number 281 ME, the OLT may directly prompt the user that ONTs B and C do not support multicast service.
From the above, we can see that the method of the present disclosure allows the master to obtain the ME Support List for the slaves so that services can be accurately executed and the master knows exactly what services are supported by the slaves.
The three methods in which the master obtains the ME Support List for the slaves are described in greater detail below.
The first method, A, is shown in
The second method, B, is shown in
The third method, C, is shown in
1. The OLT informs the ONTs of its intention to get the value of the ME Support List ME through the GET command, and sends parameters such as the ME Support List ME numbers and the instance numbers.
2. The ONTs report the value of the ME Support List ME to the OLT in response to the GET command received from the OLT.
As described above, the method of the present disclosure can speed up the service clearance of the ONTs, and quickly identify incompatibility between the OLT and the ONTs as the OLT is informed in advance of the ME types supported by the ONTs. For example, the OLT can identify compatibility problems with the ONTs by comparing its own ME Support List with that of the ONTs. In the absence of the method of the present disclosure, the OLT must send a Create message to the ONTs to get a response message. If the response message indicates a failure, the OLT must first rule out the possibility of a communication fault and an ONT fault before the OLT can determine that the problem is a compatibility problem.
Furthermore, the present disclosure provides a passive optical network (PON) system comprising a master 41 and a plurality of slaves 42 as shown in
a master instruction receiving unit 421 for receiving instructions from the master 41;
an ME Support List ME generating unit 422 for generating the ME Support List ME based on the hardware configuration of the slaves; and
an information reporting unit 423 for reporting the ME Support List ME generated by the ME Support List ME generating unit 422 to the master 41 in response to the instructions received by the master instruction receiving unit 421.
Wherein the master 41 comprises at least:
an ME Support List ME reading unit 411 for reading the ME Support List ME generated by the slaves.
The master 41 further comprises:
an ME Support List ME receiving unit 412 for receiving the ME Support List ME from the information reporting units 423 of the slaves; and
a master instruction transmitting unit 413 for sending control instructions to the slaves 42.
In this embodiment, there is at least one passive optical dividing component connected between the master 41 and a plurality of slaves 42 for transporting the downstream data from the master 41 to individual slaves 42. The optical dividing component is connected to the master and slaves in the same way, works in the same way as the prior art, and need not to be described in greater detail.
In actual application, the ME Support List ME generating unit 422 of the slaves 42 generates the ME Support List ME based on the hardware configuration of the slaves 42 when the system is initialized or when the slaves 42 have a hardware configuration change. The information reporting unit 423 reports the ME Support List ME generated by the ME Support List ME generating unit 422 to the master 41.
The system of the present disclosure may allow the ME Support List ME reading unit 411 of the master 41 to automatically read the ME Support List ME generated by the slaves 42. Additionally, the system of the present disclosure may allow the master instruction transmitting unit 413 of the master 41 to send an instruction for reading the generated ME Support List ME by the reading unit of the slave 41. The master instruction receiving unit 421 of the slaves 42 receives the instruction and the information reporting unit 423 forwards the ME Support List ME generated by the ME Support List ME generating unit 422 to the ME Support List ME receiving unit 412 of the master 41.
As described above, the system of the present disclosure allows the slaves to send service quicker than is possible with the prior art, and is a solution to the technical problem of poor communication between the master and the slaves found with the prior art.
It will be apparent to those skilled in the art that changes or variations to the present disclosure can be made without departing from the spirit and scope thereof. Therefore, if these changes and variations to present disclosure are subject to the claims of present disclosure and equivalent technical scope, then the intent of present disclosure also includes these changes and variations.
| Number | Date | Country | Kind |
|---|---|---|---|
| 200610080542.X | May 2006 | CN | national |
