Method And Apparatus For Time Transport In A Communication Network

Abstract

A method and apparatus for synchronizing nodes in a communication network. A such as an EPoC, PON, or EPoC/PON hybrid access network. The network node receives or originates a ToD value and calculates future ToD value for a second node, which the first node includes in a ToD message for sending to the second node. The ToD message preferably includes a correction based on an OFDM ranging delay value and an adjustment based on a total transmit/receive PHY path asymmetry value with respect to the two nodes. A similar future ToD message is preferably sent to each downstream node that the first node is serving.

Claims

1. A method of facilitating synchronization of nodes in a communication network, comprising: performing OFDM ranging by a first node to determine an OFDM ranging delay value for transmissions between the first node and a second node; receiving a ToD value at the first node; and calculating by the first node a future ToD value for the second node based on at least the received ToD value and a ToD correction value based at least on the determined OFDM ranging delay value.

2. The method of claim 1, further comprising generating a future ToD message based at least in part on the future ToD value and the ToD correction value.

3. The method of claim 2, further comprising transmitting the future ToD message toward the second node.

4. The method of claim 2, wherein the future ToD message comprises the calculated future ToD value and the ToD correction value.

5. The method of claim 2, wherein the future ToD message comprises a corrected future ToD value.

6. The method of claim 1, further comprising determining an MPCP ranging delay value for transmissions between the first node and the second node.

7. The method of claim 6, further comprising storing the MPCP ranging delay value in a memory device.

8. The method of claim 6, wherein the ToD correction value is based at least in part on the MPCP ranging delay value.

9. The method of claim 8, wherein the ToD correction value is based at least in part on the difference between the MPCP ranging delay value and the OFDM ranging delay value.

10. The method of claim 1, further comprising determining a total transmit/receive PHY path asymmetry value with respect to the first node and the second node.

11. The method of claim 10, further comprising adjusting the OFDM ranging delay value based at least in part on the total transmit/receive PHY path asymmetry value.

12. The method of claim 1, further comprising transmitting toward the second node a PHY interface delay difference value for the first node.

13. The method of claim 1, further comprising storing the OFDM ranging delay value in a memory device.

14. The method of claim 1, wherein the first node is a CLT in an access network.

15. The method of claim 1, wherein the second node is a CNU in an access network.

16. The method of claim 1, detecting the second node by the first node.

17. A machine-readable storage medium embodying program instructions that when executed by one or more processors cause a first network node to: perform OFDM ranging to determine an OFDM ranging delay value for transmissions between the first node and a second node; receive a ToD value at the first node; and calculating by the first node a future ToD value for the second node based on at least the received ToD value and a ToD correction value based at least on the determined OFDM ranging delay value.

18. The machine-readable storage medium of claim 17, wherein the program instructions when executed further cause the network node to generate a future ToD message based at least in part on the future ToD value and the ToD correction value.

19. The machine-readable storage medium of claim 17, wherein the program instructions when executed further cause the network node to determine an MPCP ranging delay value for transmissions between the first node and the second node, and wherein the ToD correction value is based at least in part on the MPCP ranging delay value.

20. The machine-readable storage medium of claim 17, wherein the program instructions when executed further cause the network node to determine a total transmit/receive PHY path asymmetry value with respect to the first node and the second node and to adjust the OFDM ranging value based at least in part on the total transmit/receive PHY path asymmetry value.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The present disclosure may be better understood, and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

[0045] FIG. 1 is a simplified block diagram illustrating an exemplary passive optical network.

[0046] FIG. 2 is a simplified block diagram illustrating selected components of a access network according to one embodiment

[0047] FIG. 3 is a simplified block diagram illustrating selected components of an access network according to one embodiment.

[0048] FIG. 4 is a simplified block diagram illustrating selected components of an access-network CLT and a CNU such as the CLT and CNU shown in FIG. 3 according to one embodiment.

[0049] FIG. 5 is a flow diagram illustrating a method according to one embodiment.

DETAILED DESCRIPTION

[0050] The present disclosure is directed relates to time transport, that is, reliably transporting a ToD (time-of-day) value to a remote network node so that it can synchronize clocks with other nodes. This process of course may be frustrated by delays in transmission. As mentioned above, it is inadequate or at least undesirable to simply maintain a clock within each node. The solution presented here is especial advantageous in access networks having an EPoC (Ethernet PON over Coax) component.

[0051] FIG. 1 is a simplified block diagram illustrating an exemplary passive optical network 100. Network 100 as shown here includes an OLT 105, often located in a service-provider central office, and a number of ONUs 120a through 120n. Optical transmissions, both upstream and downstream, traverse a feeder fiber 115 between OLT 105 and an optical splitter 110, which may be located in what is often referred to an outside plant. A number of access fibers 125a through 125n handle the transmissions between the splitter 110 and each individual ONU 120. While in some implementations, each ONU may be located at a subscriber premises, but may also form all or part of an interface with a non-fiber portion (not shown in FIG. 1) of an access network.

[0052] In operation, The OLT 105 of network transmits downstream signals that are distributed to each ONU 120 by the optical splitter 110. Each ONU 120 may then extract its own portion of the downstream transmission and discard the remainder (although the extraction may be done by other components as well). Upstream transmissions from each ONU 120 to OLT 105 traverse the same path, and are often at a different wavelength so as not to interfere with downstream transmissions. In addition, upstream transmissions from different ONUs are typically scheduled by the OLT 105 so as not to interfere with each other.

[0053] Clock synchronization between nodes is, of course, important for maintaining such schedules, and in implementation the usual practice is to synchronize each ONU with the OLT. This may be done, for example, according to the IEEE-1588v2 packet-based precision time protocol. In this case the OLT may itself receive ToD (time of day) input from an external source, upon which an MPCP (multi-point control protocol) TQ (time quanta) counter is timed.

[0054] Time-stamped MPCP messages are then sent from the OLT 105 to each ONU 125, where they are used to maintain an ONU MPCP counter (not shown in FIG. 1). The ONU MPCP counter then returns time-stamped messages of its own to the ONT 105. The OLT ToD and Logic unit 206 can then compare OLT timestamps to ONU timestamps and calculate an RTT (round trip time) between the two nodes. From the data it receives or calculates, ToD and Logic unit 206 may also calculate a future ToD applicable in the ONU at a future time certain. Preferably, The OLT 105 then sends a ToD correction message including the future ToD and perhaps other information, for example according to the IEEE802.1 as protocol, to ONU 120. ONU ToD logic then determines an ONU ToD and may in some cases pass this ONU ToD downstream for use by other components, for example in an EPoC hybrid access network.

[0055] FIG. 2 is a simplified block diagram illustrating selected components of a typical access network 150. In this example, access network 150 includes an OLT 155 and an ONU 160 in communication via an optical fiber 165. ONU 160 is collocated with a CLT 170 in an ONU/CLT node 180. Being co-resident in ONU/CLT node 180, ONU 160 and CLT 170 may share some computing and memory facilities, and a path of communication between them is presumed. CLT 170 is also in communication with CNU 185 via a coax cable 175. This configuration may be useful to form an access network where coax cables to, for example, subscriber premises already exist. Note that although only one of each node/component is shown in FIG. 2, in a given implementation there may be more of some or all of them.

[0056] Time transport or synchronization in this embodiment may proceed substantially as described above in reference to FIG. 1, with the process executing between OLT 155 and ONU 160 essentially being repeating between CLT 170 and CNU 185. This has its disadvantages, however; simply reusing the 802.1 as protocol using and exchange of MPCP may in effect double the time transport error introduced in the OLT-ONU portion of network 150. A new and expectedly less troublesome time transport mechanism is therefore proposed herein.

[0057] FIG. 3 is a simplified block diagram illustrating selected components of an access network 200 according to one embodiment. An EPON (Ethernet PON) portion of the access network 200 includes an OLT 210 and an ONU 220, which components may operate similarly if not identically as described above in related to FIG. 1. An EPoC portion of the network 200 includes a CLT 230 and a CNU 240. In the embodiment of FIG. 3, The ONU 220 and the CLT 230 are combined as a single component, referred to herein as ONU/CLT 250, as may be the case in some implementations. Note again that while only one of each component is illustrated in FIG. 3, there may more. The mechanism described herein in relation to the CLT and a representative CNU is simply replicated for each additional pair that are actually implemented. (The values for each CNU are independent, however, so while it is preferred that the process be performed for each pair in the access network, this is not a requirement unless specifically recited.)

[0058] Each of the components of access network 200 includes a network interface, as shown in FIG. 3. Network interface 211 is associated with OLT 210 and network interface 221 is associated with ONU 220. Similarly, network interface 231 is associated with CLT 230 and network interface 241 is associated with CNU 240. Each of the network interfaces includes a MAC (media access control) layer and a PHY (physical) layer, though with most of the communications discussed herein will in this embodiment pass. Other interfaces (not shown) may be present as well, such as one for the OLT 210 to interact with other components in the central office, and one for each CNU to communicate with, for example, a subscriber network.

[0059] In this embodiment, OLT 210 also includes a slave clock 202 that is maintained by ToD input from outside the OLT 210. The input may, for example, be formatted in packets according to IEEE 1522v2. The clock provides a local ToD to ToD and RTT logic unit 206 and to a TQ counter 204, which in turn provides output to the ToD and RTT logic unit 206 and to the MAC layer of network interface 211.

[0060] In operation, in this embodiment the OLT TQ counter 204 provides timestamped MPCP packets to ONU 220, and specifically to EPON TQ counter 222. The EPON TQ counter 222 of ONU 220 in turn provides to timestamped MPCP packets to the ToD and RTT logic unit 206 of OLT 210. ToD and RTT logic unit 206 calculates the RTT and provides a future ToD and perhaps other correction factors to the ONU 220, for example according to IEEE 802.1 as, as alluded to above.

[0061] In the embodiment of FIG. 3, the correction message is provided to ONU ToD logic unit 224, which determines an ONU ToD and provides it to CLT clock generator 232. In this embodiment, ONU 220 and CLT 230 are co-located, and may even share processing and memory facilities (not shown), although this will not be true in all embodiments. For example, ONU 220 and CLT 230 could in another embodiment be separate units and communicate with each other via an optical fiber between network interface 221 and network interface 231. Note that provision of a ToD value from ONU 220 to CLT 230 may be affected by their manner of communication. Note also that in some embodiments, the ToD input for CLT 230 may arrive from a different source.

[0062] In the embodiment of FIG. 3, the CLT clock generator 232 generates reference clocks to the CLT RTT and ToD logic unit 234 and to the CLT MPCP counter 236. The CLT MPCP counter 236 provides input to the to the CLT network interface 231 MAC layer and to the CLT RTT and ToD logic unit 234. It also provides timestamped MPCP packets to the CNU MPCP counter 242 of CNU 240. The CNU MPCP counter 242 returns its own timestamped MPCP packets to the RTT and Logic unit 234 of CLT 230.

[0063] The RTT & Logic unit 234, which also receives a value for OFDM ranging delay, described below, calculates a future ToD applicable in the CNU 240 at a future time certain. Preferably, the CLT 250 then sends a ToD correction message including the future ToD and perhaps other information to CNU 240. CNU 240 receives this correction message at CNU ToD logic unit 244 and determines a CNU ToD. In this embodiment, ToD logic unit 244 provides this CNT ToD to a CNU master clock 246. CNU master clock 246 may then provide the ToD to other components as well, for example to a router in a home network (not shown).

[0064] FIG. 4 is a simplified block diagram illustrating selected components of an access-network CLT and a CNU such as CLT 230 and CNU 240 shown in FIG. 3. The selected components are, generally speaking, a part of each respective node's PHY interface. The components shown are used to perform OFDM ranging. The CLT frame timing counter 255 receives a reference clock signal and transmits time-stamped frames to CNU 240 via PLC data channel 251 and EPoC CLT PMD 253.

[0065] In this embodiment, the frames from the CLT are received at CNU 240 though EPoC CNU PMD 263, where a clock recovery device 264 recovers the clock and provides a clock signal to CNU frame timing counter 265. Frame timing counter 265 also receives the frames sent by CLT via EPoC CNU PMD 263 and PLC data channel 261, and returns timing frames to CLT 230.

[0066] In this embodiment, when the frames are received at CLT 230 via EPoC CLT PMD and PLC Data Channel 251, the timestamps are extracted and OFDM Ranging Delay Calculator 254 determines the OFDM ranging delay by taking the difference between the CLT timestamp and the CNU timestamp for a particular frame. The delay value for the CNU is then stored in a storage register (not shown).

[0067] In a preferred embodiment, the CLT frame timing counter receives a 204.8 MHz reference clock signal, and the OFDM ranging delay is calculated in units of the 204.8 MHz OFDM clock. As should be apparent, this procedure is preferably repeated for each CNU that is served by the CLT, although only a single CNU is represented in FIG. 4.

[0068] In a particularly preferred embodiment, PHY transmit/receive path asymmetry is also taken into account. That is, it may be the case, especially with multiple manufacturers involved, that the downstream PHY delay does not equal the upstream PHY delay. This may affect the ToD correction calculations. Rather than try to eliminate transmit/receive path asymmetry, however, the proposed solution seeks to compensate for it.

[0069] In this embodiment, the interface delay difference for each node, for example CLT 230 and CNU 240, is defined as the difference in delay between the XGMII to the MDI path and the MDI to the XGMII path. The total transmit/receive PHY path asymmetry with respect to those two nodes is then the difference between their respective interface delay differences.

[0070] Note that FIGS. 1-4 illustrate selected components according to their respective embodiments and some variations are described above. Other variations are possible without departing from the claims of the invention as there recited. In some of these embodiments, for example, illustrated components may be integrated with each other or divided into subcomponents. There will often be additional components in the network node and in some cases fewer. The illustrations components may also perform other functions in addition to those described above, and some of the functions may alternately be performed elsewhere than described in these examples.

[0071] FIG. 5 is a flow diagram illustrating a method 300 according to one embodiment. At Start it is presumed that the components for performing the method are available and operational at least according to this embodiment. The process then begins with receiving (step 305) a ToD input in a CLT of an access network. The ToD value received by the CLT may in fact be received continuously or at periodic intervals. The received ToD value may be in any format, and may but does not have to be converted or adjusted for use in this process. A CLT ToD is established (step 310) based on this input. The CLT ToD is updated as new input is received. In an alternate embodiment (not shown), the ToD value may be generated in the CLT, that is, originated there, but this is not presently preferred.

[0072] In the embodiment of FIG. 5, the process continues with detecting (step 315) the presence of a CNU by a CLT. When this occurs, and perhaps periodically thereafter, the CLT executes (step 320) an OFDM ranging procedure with respect to the CNU. The OFDM ranging delay value is then stored (step 325) in a memory device. The OFDM ranging delay value may be subsequently re-determined (not shown) and, if so, the most current value is stored.

[0073] Although optional, in this embodiment the CLT also determines the PHY interface delay difference (step 330) for the CNU. This may be accomplished, for example, by query to the CNU if it is not automatically supplied during the ranging process, or by directing the CNU to make this determination and report the results. In some cases it may be inferred from other information such as the specific types of components being used by the CNU. In this embodiment, it is presumed that the PHY interface delay for the CLT is already known or may be determined (not separately shown). The process then continues with determining (step 335) the total transmit/receive PHY path asymmetry with respect to those two nodes.

[0074] Note that in an alternate embodiment (not shown), the CLT instead sends a CLT PHY interface delay difference value to the CNU and the adjustments, if any, are applied there. Such adjustments could be mandatory or optional, depending on the implementation.

[0075] In the embodiment of FIG. 5, the MPCP ranging delay with respect to the CNU is determined (step 340) and stored (step 345) in an accessible memory device. In a preferred embodiment, the total transmit/receive PHY path asymmetry is then applied (step 350) to either or both of the ranging delay values to obtain refined ranging delay value. As should be apparent, the ranging delay will be based on one-half of the RTT (round trip time) but will in this preferred embodiment be adjusted in light of the fact that future ToD messages are sent only in the downstream direction.

[0076] In the embodiment of FIG. 5, a future ToD_MPCP value is then calculated (step 355) and a future ToD message is then generated (step 360), which message contains a value for

ToD_MPCP+T_CORR

[0077] where T_CORR=T_OFDM−T_MPCP. T_OFDM and T_MPCP, in turn, are the respective ranging delay values (or adjusted ranging delay values) derived from OFDM and MPCP ranging calculations. Note that although shown as two steps, calculating the future ToD and generating the message including the correction may be done as one (or several) operations, and the value included in the message may be either a single corrected value or values for both ToD_MPCP and T_CORR. The future ToD message is then transmitted (step 365) to the CNU. The process then continues for other CNUs, if any, and for subsequent re-synchronization, if desired.

[0078] Note that FIG. 5 and the description above relate to the process for a single CNU. This process is preferable applied for all CNUs connected to the CLT. In addition, the process for some or all of the CNUs is preferably repeated from time to time to account for possible changes in conditions or environment, and hence different values for the ranging delay and corrections. Note also that when the method 300 is described in an EPoC environment, it may be equally applicable in other environments as well, for example a PON or data center.

[0079] Note that the sequence of operation illustrated in FIG. 5 represents an exemplary embodiment; some variation is possible within the spirit of the invention. For example, additional operations may be added to those shown in FIG. 5, and in some implementations one or more of the illustrated operations may be omitted. In addition, the operations of the method may be performed in any logically-consistent order unless a definite sequence is recited in a particular embodiment.

[0080] In some embodiments, certain aspects of the techniques described above may be implemented by one or more processors of a processing system executing software. The software comprises one or more sets of executable instructions stored or otherwise tangibly embodied on a non-transitory computer readable storage medium. The software can include the instructions and certain data that, when executed by the one or more processors, manipulate the one or more processors to perform one or more aspects of the techniques described above. The non-transitory computer readable storage medium can include, for example, a magnetic or optical disk storage device, solid state storage devices such as Flash memory, a cache, random access memory (RAM) or other non-volatile memory device or devices, and the like. The executable instructions stored on the non-transitory computer readable storage medium may be in source code, assembly language code, object code, or other instruction format that is interpreted or otherwise executable by one or more processors. The executable instructions may, if explicitly recited in a particular embodiment, also be embodied in a propagating signal.

[0081] A computer readable storage medium may include any storage medium, or combination of storage media, accessible by a computer system during use to provide instructions and/or data to the computer system. Such storage media can include, but is not limited to, optical media (e.g., compact disc (CD), digital versatile disc (DVD), Blu-Ray disc), magnetic media (e.g., floppy disc, magnetic tape, or magnetic hard drive), volatile memory (e.g., random access memory (RAM) or cache), non-volatile memory (e.g., read-only memory (ROM) or Flash memory), or microelectromechanical systems (MEMS)-based storage media. The computer readable storage medium may be embedded in the computing system (e.g., system RAM or ROM), fixedly attached to the computing system (e.g., a magnetic hard drive), removably attached to the computing system (e.g., an optical disc or Universal Serial Bus (USB)-based Flash memory), or coupled to the computer system via a wired or wireless network (e.g., network accessible storage (NAS)).

[0082] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any feature(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature of any or all the claims. Moreover, the particular embodiments disclosed above are illustrative only, as the disclosed subject matter may be modified and practiced in different but equivalent manners apparent to those skilled in the art having the benefit of the teachings herein. No limitations are intended to the details of construction or design herein shown, other than as described in the claims below. It is therefore evident that the particular embodiments disclosed above may be altered or modified and all such variations are considered within the scope of the disclosed subject matter. Accordingly, the protection sought herein is as set forth in the claims below.

[0083] Although multiple embodiments of the present invention have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it should be understood that the present invention is not limited to the disclosed embodiments, but is capable of numerous rearrangements, modifications and substitutions without departing from the invention as set forth and defined by the following claims.