Communicating schedule and network information in a powerline network

Description of equivalent WO 2007016032 A2

COMMUNICATING SCHEDULE AND NETWORK INFORMATION IN

A POWERLINE NETWORK

0003RELATED APPLICATIONS This application claims priority from U.S. Provisional Application No. 60/702,717, filed on July 27, 2005, which is hereby incorporated by reference in its entirety. The following U.S. Patent Applications are also incorporated by reference in their entireties and made part of the present application:

0004U.S. Patent Application Serial No. , titled " ," Attorney Docket No. 0120142, filed concurrently with the present application;

0005U.S. Patent Application Serial No. , titled " ," Attorney

0006Docket No. 0120143, filed concurrently with the present application;

0007U.S. Provisional Application No. 60/705,720, titled "Communicating in a Network that includes a Medium having Varying Transmission Characteristics, filed August 2, 2005; U.S. Patent Application Serial No. 11/339,293, titled "Time Synchronization in a

0008Network," filed January 24, 2006;

0009U.S. Patent Application Serial No. 11/337,946, titled "Communicating in a Network that includes a Medium having Varying Transmission Characteristics," filed January 23, 2006; U.S. Patent Application Serial No. , titled "Synchronizing Channel Sharing with Neighboring Networks," filed on , Attorney Docket No. SLAl 890, assigned to Sharp Laboratories of America, Inc.;

0010U.S. Provisional Application No. 60/703,236, titled "Method for Sharing the Channel with Neighbor Networks," filed July 27, 2005; U.S. Patent Application Serial No. , titled "Method for Providing

0011Requested Quality of Service," filed on , Attorney Docket No. SLAl 891, assigned to Sharp Laboratories of America, Inc.;

0012U.S. Provisional Application No. 60/703,317, titled "Method for Providing Requested Quality of Service," filed July 27, 2005; and U.S. Patent Application Serial No. 11/337,963, titled "Managing Contention-Free

0013Time Allocations in a Network," filed January 23, 2006.

0014BACKGROUND OF THE INVENTION 1. FIELD OF THE INVENTION The present invention relates generally to communication over an Ethernet-Class network and, more specifically to communication over a power line network. 2. BACKGROUND ART

0015The vision of the networked home has driven many a business plan, but product offerings to date have been too limited in capability or in market potential to achieve the dream. Home networking is different than networking in the workplace. The applications are different, the traffic patterns are different, and the media available to carry the data are different. Certainly home networking users will want to transfer files between their computers and share peripherals such as printers. They will want gateways to broadband access so they can share their Internet connection between multiple devices. Users will also want other services, such as voice-over-IP (VoIP), streaming media for entertainment, and support for multi-player networked games.

0016While some newer houses are wired with cables suitable for Ethernet, most are not. Thus, if choices for home network physical media are limited to phone wiring, wireless, and power line, there are a mixed bag of attributes.

0017There has been a proliferation of wireless networking and related components in recent years. However, wireless communication suffers from limited range and less than universal coverage, i.e. certain areas of the home cannot communicate with others. These issues are particularly prominent in certain types of construction that result in poor signal propagation, such as those using steel frame and brick walls. Solutions to these issues are expensive and complex, and require some technical acumen not available to the average homeowner.

0018Although telephone line networking may at first appear to be a solution, many households lack phone jacks at convenient locations to achieve the foreseeable benefits of home networking. For instance, some older houses may only have one phone jack located in the kitchen for use in the kitchen and other living areas (e.g. living room, family room, etc). Thus, it may be inconvenient or messy to provide network connections to remote devices. This picture is particularly unfavorable in less developed countries. Power plugs, on the other hand, are located in almost every room in the home, and some homes have multiple power outlets located on every wall of every room. The power line appears to be the most difficult medium of these three for communication, but it does have two appealing attributes. First, as with phone lines, no RF conversion hardware is needed and, thus, the cost can be low compared to wireless solutions. But more importantly, power outlets are almost everywhere someone might want to use a networked device at home. The power line medium is a harsh environment for communication. For instance, the channel between any two outlets in a home has the transfer function of an extremely complicated transmission line network with many unterminated stubs and some having terminating loads of varying impedance. Such a network has an amplitude and phase response that varies widely with frequency. At some frequencies the transmitted signal may arrive at the receiver with relatively little loss, while at other frequencies it may be driven below the noise floor. Worse, the transfer function can change with time. This might happen because the homeowner has plugged a new device into the power line, or if some of the devices plugged into the network have time-varying impedance. As a result, the transfer function of the channel between outlet pairs may vary over a wide range. In some cases, a broad swath of bandwidth may be suitable for high quality transmission, while in other cases the channel may have a limited capacity to carry data.

0019With the potential for multiple networked devices communicating over the power line medium at any time, the issues involving the management and coordination of the networked devices bring about concerns regarding interference between networked devices and coordination and sharing of network resources. Accordingly, there is a need in the art for communication and coordination schemes that can effectively and efficiently address such concerns.

SUMMARY OF THE INVENTION

0021The present invention is directed to method and system for communicating schedule and network information in a powerline network. More specifically, the invention provides a method and system for synchronizing transmissions of all networked devices and communicating schedule information and basic network parameters to all networked devices to achieve optimal resource utilization in a powerline network.

0022In one aspect, a powerline network includes a number of stations including a central coordinator for coordinating transmissions of each of the stations. The central coordinator includes a system clock and a network timer and is configurable to transmit a number of network timer values. Each of the network timer values can have 32 bits, for example. Each of the network timer values can be transmitted by the central coordinator in one of a number of beacons. Each of the beacons can include a frame control including a number of powerline network parameters. Each of the other stations is configurable to utilize the network timer values and a corresponding number of local timer values to estimate a frequency error between the system clock and a local clock and an offset between the network timer and a local timer.

0023The network timer (maintained at the CCo) and the local timer (maintained at non- CCo stations) are controlled by the system clock (i.e. the CCo' s clock) and the local clock, respectively. Each of the other (i.e. non-CCo) stations is further configurable to utilize the frequency error and the offset to synchronize the local timer to the network timer. Each of the other stations is further configurable to utilize the frequency error and the offset to adjust the local clock for synchronized signal processing. The central coordinator is further configurable to transmit a schedule including resource allocations to each of the other stations. Other features and advantages of the present invention will become more readily apparent to those of ordinary skill in the art after reviewing the following detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

0024The features and advantages of the present invention will become more readily apparent to those ordinarily skilled in the art after reviewing the following detailed description and accompanying drawings, wherein: FIG. 1 illustrates an overview of a HPAV (HomePlug Audio Video) system, according to one embodiment of the present application;

0025FIG. 2A illustrates a diagram of an exemplary powerline network configuration for the HPAV system in FIG. 1.

0026FIG. 2B illustrates a diagram of another exemplary powerline network configuration for the HPAV system in FIG. 1.

0027FIG. 2C illustrates a diagram of another exemplary powerline network configuration for the HPAV system in FIG. 1.

0028FIG. 3 illustrates a diagram of an exemplary HPAV transceiver for HPAV system 100 in FIG. 1. FIG. 4 illustrates a diagram of an exemplary beacon period for HPAV system 100 in

0029FIG. 1.

0030FIG. 5 illustrates a flow diagram for synchronizing local timers to a network timer according to one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

0032Although the invention is described with respect to specific embodiments, the principles of the invention, as defined by the claims appended herein, can obviously be applied beyond the specifically described embodiments of the invention described herein. Moreover, in the description of the present invention, certain details have been left out in order to not obscure the inventive aspects of the invention. The details left out are within the knowledge of a person of ordinary skill in the art.

0033The drawings in the present application and their accompanying detailed description are directed to merely example embodiments of the invention. To maintain brevity, other embodiments of the invention which use the principles of the present invention are not specifically described in the present application and are not specifically illustrated by the present drawings. It should be borne in mind that, unless noted otherwise, like or corresponding elements among the figures may be indicated by like or corresponding reference numerals. FIG. 1 illustrates an overview of HPAV (HomePlug Audio Video) system 100, according to one embodiment of the present application. As shown, HPAV system 100 includes PHY (Physical) layer 110, MAC (Media Access Control) layer 120 and convergence layer 130. When HPAV system 100 is in transmit mode, PHY layer 110 performs error- control correction, mapping into OFDM (Orthogonal Frequency Division Multiplexing) symbols, and generation of time-domain waveforms; MAC layer 120 determines the correct position of transmission, formats data frames into fixed-length entities for transmission on the channel and ensures timely and error-free delivery through Automatic Repeat Request (ARQ); and convergence layer 130 performs bridging, classification of traffic into connections, and data delivery smoothing functions. Conversely, when HPAV system 100 is in receive mode, PHY layer 110, MAC layer 120 and convergence layer 130 perform the corresponding functions in the reverse.

0034HPAV system 100 utilizes OFDM modulation technique due to its inherent adaptability in the presence of frequency selective channels, its resilience to narrow band interference, and its robustness to impulsive noise. Through the use of time-domain pulse shaping of the OFDM symbols, deep frequency notches can be achieved without the additional requirement of transmit notch filters. HPAV system 100 employs 1155 carriers, in the range from 1.80 MHz to 30.00 MHz.

0035FIG. 2A illustrates an exemplary Audio Video Logical Network (AVLN) for HPAV system 100 in FIG. 1. An AVLN comprises a set of stations or devices that have the same Network Membership Key (NMK). In an AVLN, which is also generally referred to as a "powerline network" in the present application, one of the stations or devices becomes the Central Coordinator (CCo) device, which is responsible for coordinating the transmissions of all of the stations in the network, in order to achieve maximum overall network throughput as well as good QoS for each connection. The CCo is also responsible for authenticating stations that wish to join the network, managing encryption keys, and coordinating sharing of resources with neighbor networks. A CCo can either be preconfigured as such or be automatically selected through a specified selection procedure; however, only one station in an AVLN can function as a Central Coordinator (CCo) at one time. It is noted that the stations in an AVLN (i.e. a powerline network) can communicate via a powerline (i.e. an AC line).

0036As shown in FIG. 2A, AVLN 202 includes stations A, B, C, and D and CCoI. The Physical Network (PhyNet) of a given station is the set of stations that can physically communicate with the station - at least at the level of Frame Control (FC) and ROBO (robust) mode. A PhyNet is relative to a given station, and it is possible for PhyNets of physically close-by stations to be distinct. In the present application, it is noted that a double arrow line, such as double arrow line 204 in FIG. 2A, indicates an ability for two stations, such as station A and CCoI, to communicate on the PHY level. Also shown in FIG. 2 A, all stations can communicate with each other and, consequently, the PhyNet of all stations is the same set {A, B, C, D, CCoI }, as shown in Table 1. Two stations belonging to an AVLN can communicate with each other if they belong to each other's PhyNet. Further shown in FIG. 2A, AVLN 202 coincides with the PhyNet of each station in AVLN 202.

0037<img file="WO2007016032A2_D0001.tif" />

0038Table 1

0039FIG. 2B illustrates two exemplary AVLNs for HPAV system 100 in Figure 1. As shown in FIG. 2B, AVLN 210 includes stations A and B and CCoI and AVLN 212 includes CCo2 and stations C and D. The PhyNet for each station in FIG. 2B is shown in Table 1.

0040FIG. 2C illustrates an exemplary AVLN for HPAV system 100 in Figure 1. As shown in FIG. 2C, AVLN 220 includes CCoI and stations A, B, C₅ and D. The PhyNet for each station in FIG. 2C is shown in Table 1. FIG. 3 shows a diagram of an exemplary HPAV transceiver for HPAV system 100 in

0041FIG. 1. HPAV transceiver 300 includes transmitter side 310, which uses OFDM modulation, and receiver side 360. On transmitter side 310, the PHY layer (e.g. PHY layer 110 in Figure 1) receives its inputs from the MAC layer (e.g. MAC layer 120). Three separate processing chains are shown in FIG. 3 for different encoding for HomePlug 1.0.1 Frame Control (FC) data 312, HomePlug AV Frame Control data 314 and HomePlug AV Payload data 316, which are processed by 1.0.1 FC encoder 320, AV FC encoder 330 and AV payload data encoder 340, respectively. The outputs of the three encoders lead into a common OFDM modulation structure, including mapper 350, Inverse Fast Fourier Transform (IFFT) processor 352, cyclic prefix insertion, symbol window and overlap block 352, and preamble insertion 356, which eventually feeds Analog Front End (AFE) module 358 that couples the signal to power line medium 390.

0042At receiver side 360, AFE 365 operates with an Automatic Gain Controller (AGC) 368 and a time-synchronization module 370 to feed separate frame control and payload data recovery circuits. The frame control data is recovered by processing the received sample stream through 384-point FFT 372 for HomePlug 1.0.1 delimiters, and 3072-point FFT 374 for HomePlug AV, and through separate frame control decoders 380 and 382 for respective HomePlug 1.0.1 and HomePlug AV modes. The payload portion of the sampled time domain waveform, which contains only HomePlug AV formatted symbols, is processed through 3072-point FFT 374, demodulator 375, and through de-interleaver 385, turbo convolutional decoder 386, and de-scrambler 387 of AV payload data decoder 384 to recover the AV payload data.

0043In the present invention, the CCo of a network (e.g. CCoI of AVLN 202 in FIG. 2A) transmits a special signal called the beacon, which contains system-wide information, such as the network ID, the number of neighboring networks with which it coordinates, the current schedule of transmissions (e.g. which station is allowed to transmit and when), and the mode of the network (e.g. if it is in HPAV or in HPAV Hybrid mode). The beacon can also contain responses to messages from specific stations that request resources, request to join the network, or are delivered an encryption key, etc. The beacon is sent by the CCo at regular intervals that are tied to a specific phase of the power cycle, as discussed below in relation to FIG. 4. The beacon is transmitted in a so-called ROBO (Robust) mode, which is used for reliable reception of the beacon by other stations, where each station experiences a different channel characteristic from the CCo to the station. In the ROBO mode, modulation is independent of the characteristics of the channel, and robustness is achieved through low rate coding, low density modulation, and repetition and interleaving of the payload.

0044Each HPAV station (e.g. stations A, B, C, and D in FIG. 2A) monitors the channel for the presence of HP 1.0 devices. When a station detects the presence of HP 1.0 devices, it notifies the CCo (e.g. CCOl in FIG. 2A), which in turn switches the network (e.g. AVLN 202 in FIG. 2A) to the HPAV Hybrid mode. In the Hybrid mode operation, HPAV networks avoid interference from HP 1.0 stations by coaxing the HP 1.0 stations to transmit only in the CSMA/CA region of the beacon period. Thus HPAV stations and HP 1.0 stations can coexist on the same medium, while HPAV stations maintain all the advantages of scheduled transmissions in the contention-free portion of the period.

0045FIG. 4 illustrates an exemplary beacon period synchronized to an exemplary powerline cycle, according to one embodiment of the present invention. As shown in FIG. 4, beacon period 402 (i.e. the time between two consecutive beacon transmissions) is substantially equal to two periods of powerline cycle 404. For example, for a powerline frequency of 60 Hz (i.e. for a 60 Hz system), the beacon period is nominally equal to 33.33 milliseconds (ms). For example, for a powerline frequency of 50 Hz (i.e. for a 50 Hz system), beacon Period 402 is nominally equal to 40 ms. In one embodiment, beacon period 402 can be precisely equal to two periods of powerline cycle 404. As further shown in FIG. 4, the start of beacon period 402 can be offset from the start of a powerline cycle by a fixed duration.

0046As also shown in FIG. 4, beacon period 402 includes beacon region 406, CSMA (Carrier Sense Multiple Access) region 408, and reserved region 410. Beacon region 406 includes the beacon, which is generated by a CCo and can include a Preamble, a Frame Control, and a beacon payload. The CCo ensures that the beacon remains synchronized to the powerline cycle, independent of the CCo local clock frequency.

0047Information describing allocations within beacon period 402 is broadcast in the beacon payload by using one or more beacon entries. Beacon region 406 also includes information regarding the duration of CSMA region 408 and reserved region 410. CSMA region 408 includes persistent shared CSMA allocation region 416, which is allocated to connections (i.e. sessions between transmitting and receiving stations) that use CSMA channel-access mechanism. Reserved region 410, which is the section of beacon period 402 during which only one station has permission to transmit, is further divided into persistent allocation region 412 and non-persistent allocation region 414. Persistent allocation region 412 is allocated to connections (i.e. sessions between transmitting and receiving stations), where the connections require QoS (Quality of Service). Non-persistent allocation region 414 is allocated to one or more of the following:

0048(a) active connections that have allocation in persistent allocation region 412 but may need extra capacity, either because the channel has deteriorated for a brief or longer period of time, or because the requirements of a particular application have increased (e.g. during video or audio fast forward); (b) an additional CSMA period (e.g. when the CCo senses high level of collisions in the regular CSMA period; and

0049(c) special system needs, such as a discover beacon, whose purpose is to discover hidden nodes (i.e. stations) that cannot detect or hear the CCo.

0050The allocations in persistent allocation region 412 and the allocations in persistent shared CSMA allocation region 416 are controlled by a "Persistent Schedule," and the allocations in non-persistent allocation region 414 are controlled by a "Non-persistent Schedule." Both the Persistent Schedule and the Non-persistent Schedule are included in Broadcast messages in the beacon. The Persistent Schedule is valid for the current beacon period as well as for a number of subsequent beacon periods, where the number of subsequent beacon periods is indicated in the beacon. Since the Persistent Schedule remains valid for a number of subsequent beacon periods, it (i.e. the Persistent Schedule) allows all of the stations (e.g. stations A, B, C, and D in FIG. 2A) in the network (e.g. AVLN 202 in Figure 2A) to know the schedule, even if they occasionally fail to receive the beacon.

0051In addition to the Persistent Schedule, the system (e.g. HPAV system 100 in Figure 1) can support a Preview Schedule, which provides a preview of the next schedule. Thus, when a schedule change is necessary, the new schedule can be announced before it actually takes effect. The beacon can utilize a counter to indicate how many beacon periods will pass before the new schedule takes effect, for example. The Preview Schedule also allows some stations to lose beacon reception without losing schedule information. hi contrast to the Persistent Schedule, the Non-persistent Schedule is valid only for the beacon period in which it is announced. Consequently, if a station does not receive the beacon in a certain period, the station simply does not use any portion of non-persistent allocation region 414 during that period. On the other hand, when a station does receive the current beacon, it (i.e. the station) can take advantage of any allocation in non-persistent allocation region 414, either for its own use, or for the benefit of the system as a whole (e.g. in the form of the discover beacon).

0052The Persistent and Non-persistent Schedules advantageously allow a more reliable distribution of the schedule in an unreliable medium, while at the same time allowing a swift reaction to rapidly changing conditions, or implementation of system functions without specific allocation of resources to such functions.

0053The CCo assumes a special role in coordinating the activities of the powerline network, and ensuring maximal resource utilization. The CCo employs a beacon in its interactions with the rest of the stations in the powerline network. The format, timing, and sharing of the beacon between the various network functions is a critical aspect of the efficiency, high reliability, and functionality of the HPAV system (e.g. HPAV system 100 in FIG. 1). The beacon is transmitted by the CCo and received by all other stations in the powerline network, and it (i.e. the beacon) is synchronized to the powerline cycle (e.g. powerline cycle 404 in FIG. 4). The synchronization of all transmissions from all stations to the beacon is critical in the powerline channel, because many interfering devices may cause disturbances, such as change of channel gain and phase, and level of noise, that are synchronous to the powerline cycle and occupy only a portion of that cycle. Synchronizing all transmissions to the powerline cycle allows superior resource utilization. This function is achieved by specifying transmission regions in the beacon period (i.e. the time interval between two consecutive beacon transmissions) in terms of the position of the beacon transmission.

0054Synchronization of the signal processing clock (i.e. the local clock) of all stations to the CCo minimizes inter-channel interference between carriers of the OFDM (Orthogonal Frequency Division Multiplexing) signal, and loss of performance due to frequency error estimation at the receiver, which in turn allows optimal capacity utilization of the available links. In one embodiment, this function is performed by including the value of a 25-MHz clock at the CCo referred to as NTB (Network Time Base) in the beacon, and requiring all stations to observe the values of the NTB in multiple Beacon instances and estimate the difference between the NTB values and the corresponding local 25-MHz timer values, called LTmr (Local Timer).

0055The LTmr is either expressly adjusted to follow the NTB, or its frequency difference with the NTB is estimated and is used in correcting the operation of the local station. For example, the local station may use this estimate to resample a digital waveform it generates with its local clock to generate a waveform that would be generated with a perfectly synchronized signal processing clock.

0056Referring now to FIG. 5, there is shown exemplary flowchart 500 depicting a method for synchronizing local timers in respective stations to a network timer in a CCo in a powerline network in accordance with one embodiment of the present invention. Certain details and features have been left out of flowchart 500 of FIG. 5 that are apparent to a person of ordinary skill in the art. For example, a step may consist of one or more sub-steps or may involve specialized equipment, as known in the art. While steps 502 through 508 shown in flowchart 500 are sufficient to describe one embodiment of the present invention, other embodiments of the invention may utilize steps different from those shown in flowchart 500.

0057Beginning at step 502, one station of a group of stations (e.g. stations A, B, C, and D in FIG. 2A) in a powerline network (e.g. AVLN 202 in FIG. 2A) is designated as CCo (e.g. CCoI). The CCo can be designated as CCo either by being preconfigured as such or by being automatically selected through a specified selection procedure, for example. At step 504, the CCo transmits values of a network timer to each other station in the powerline network. The network timer, which is maintained by the CCo and which is also referred to as the Network Time Base (NTB), is controlled by the CCo 's system clock. For example, the network timer can be clocked by a 25 MHz clock that is derived from the CCo' s system clock. For example, the network timer can be a 32-bit timer. Each network timer value is transmitted by the CCo in a beacon, which is located in a beacon region (e.g. beacon region 406 in FIG. 4) of a beacon period (e.g. beacon period 402 in FIG. 4).

0058The CCo's system clock and the network timer are used to correct (i.e. adjust) the local clock used for processing of transmit and receive signals at all of the non-CCo stations in the powerline network, announcing the further beacon position and schedule within the beacon period (e.g. beacon period 402 in FIG. 4), and derive an ATS (Arrival Time Stamp) and perform a jitter control function. The network timer value can be embedded into a frame control of a beacon as a 32-bit BTS (Beacon Time Stamp). The BTS is the value of the NTB (i.e. network timer) at the BTT (Beacon Transit Time), which is defined as the time instant at which the first non-zero sample of the beacon PPDU (PHY Protocol Data Unit) appears on the transmitter's analog output.

0059At step 506, each non-CCo station utilizes the network timer values and corresponding local timer values to estimate a frequency error between the system clock and a local clock and to estimate an offset between the network timer and a local timer, which is controlled by the local clock. When a beacon is detected by each non-CCo station, the non- CCo station can store the value (e.g. a 32-bit value) of its local timer at the time of reception of the beginning of the AV preamble signal of beacon n, denoted as LTmr_n (i.e. the local timer value corresponding to beacon n). The received beacon includes the beacon time stamp (i.e. the network timer value), which is denoted as BTS_n. Propagation delay between CCo (i.e. the transmitter) and each non-CCo station (i.e. a receiver) can be ignored; however, if it is known, it could be compensated for in the computation of the offset.

0060The following formulas can be used to estimate the clock frequency and timer offset errors:

0061FreqErrori = (BTS₁ - BTS₀) / (LTmT₁ - LTMr₀) - 1 (formula 1); Offset = BTS₁ - LTmT₁ (formula 2);

0062FreqErroT_n = FreqError_n-1 + w_f • ((BTS_n - BTS_n-1) / (LTmr_n - LTmT_n-1) - 1 - FreqError_n-1), for n >2 (formula 3); and

0063Offset = Offset_n-1 + FreqError_n • (LTmr_n - LTmr_n-1) + W₀ • ((BTS_n - LTmr_n) (Offset_n-1 - FreqError_n • (BTS_n - LTmr_n-1))), for n >2 (formula 4). hi respective formulas 3 and 4, W_f and W₀ are weighting constants of the form Vz ^k, where k is a positive integer. Larger values of k provide better filtering of the uncertainty between each BTS _n and LTmr_n pair caused by factors such as preamble detection jitter. Larger values of k result in a longer period of time to achieve convergence to the correct estimate of frequency error. When tracking a beacon, it is recommended that a small value of k be used for the first samples and increased to the ultimate value.

0064Once FreqError_n (in formula 3) and Offset_n (in formula 4) are known to be accurate, the relationship between the network time base estimate (NTB_STA;) and the local timer at instance i (LTmr;) can be determined by the formulas:

0065NTB_STAj = LTmri + Offset_n + FreqError_n • (LTmT₁ - LTmT_n) (formula 5); and

0066LTmri - (NTB_STAj + FreqError_n • LTmr_n - Offset_n) / (1 + FreqError_n) (formula 6). hi formulas 5 and 6, Offset_n, FreqError_n, and LTmr_n are the values computed from the most recently received beacon. At step 508, each of the non-CCo stations in the powerline network utilize the frequency error and the offset to synchronize the local timer to the network timer. The local timer, which can be a 32-bit timer, for example, is synchronized in frequency and absolute value to the network timer of the CCo. Each of the non-CCo stations can utilize the frequency error and offset to adjust their local clock to achieve synchronized processing of transmit and receive signals.

0067The network ID, the number of neighbor powerline networks with which the powerline network in the present embodiment is coordinating, and the mode of the powerline network (i.e. whether it has sensed the presence of HP 1.0 devices and is running in the Hybrid mode that accommodates HP 1.0 coexistence) are fields in the frame control of the beacon. These fields are fixed and are included in every transmission of the beacon, and are of interest to all stations in the powerline network, as well as the CCo' s of neighboring powerline networks. This feature allows fast parsing of the fields and appropriate action by the receiving stations.

0068The schedule defines the structure of the beacon period (e.g. beacon period 402 in FIG. 4), such as the division into beacon regions, CSMA/CA region(s), persistent CFP (contention-free period), and non-persistent CFP. The schedule further defines the allocation of specific regions with the CFP to specific connections. The schedule may also be of interest to all network stations in whole or in part, and is contained in a broadcast message because its length and complexity can vary depending on the current traffic profile on the network.

0069In addition to defining the network timing and management of the wire resource, the CCo performs association, authentication and key distribution functions, and coordination of resources with neighboring powerline networks. These functions are accomplished by including MAC Management Messages or Entries (MME' s) within the beacon payload. Most often these messages are unicast to a particular station that is involved in the function. Neighbor powerline networks are formed when stations that have the potential and capability to communicate with each other do not belong to the same community of interest, such as when HPAV networks are set up in two neighboring apartments. Each community of interest is formed during the authorization process under guidance from its owner.

0070Thus, as discussed above, the present invention provides an HPAV system including stations that communicate via a powerline in a powerline network, where a CCo (central coordinator) transmits a network timer value to each station, and where the network timer value is transmitted in a beacon. In the invention's HPAV system, each station in the powerline network utilizes the network timer value to synchronize its local timer to a network time controlled by the CCo' s system clock. As a result, the present invention advantageously achieves effective and efficiency communication of schedule and network information in an HPAV system. From the above description of the invention it is manifest that various techniques can be used for implementing the concepts of the present invention without departing from its scope. Moreover, while the invention has been described with specific reference to certain embodiments, a person of ordinary skill in the art would recognize that changes could be made in form and detail without departing from the spirit and the scope of the invention. For example, it is contemplated that the circuitry disclosed herein can be implemented in software and/or hardware, and the software may be stored in any storage medium or memory. The described embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that the invention is not limited to the particular embodiments described herein, but is capable of many rearrangements, modifications, and substitutions without departing from the scope of the invention.