Flexible scheduling of resources in a noisy environment

1.

FIELD OF THE INVENTION

0001The present invention relates generally to communication over an Ethernet-Class network and, more specifically to communication over a power line network.

2.

BACKGROUND ART

0002The 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.

0003While 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.

0004There 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.

0005Although 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.

0006The 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.

0007With many power outlets available for plugging in a new networked device at any time, the issues involving the management and coordination of the networked devices bring about concerns regarding the overall throughput of the network, Quality of Service (QoS) for each connection, authentication, coordination, and sharing of the network resources. Accordingly, there is a need in the art for management and coordination schemes that can effectively and efficiently address such concerns. <patcit id="pcit0001" dnum="EP1179919A"><text>EP-A-1 179 919</text></patcit> discloses an access contention scheme having both multi-level priorities and a contention-free access indicator for use by a station in a network of stations.

0008<patcit id="pcit0002" dnum="US7623542A"><text>US-A-7 623 542</text></patcit> discloses a method of operating in a network in which stations communicate over a shared medium. The method provides regularly repeated contention free intervals, CSMA communication during times outside the contention free intervals, and distributed control over the initiation and makeup of the contention free intervals to a plurality of stations so that any of the plurality of stations can independently initiate transmission within the contention free interval.

0009<patcit id="pcit0003" dnum="US6587474A"><text>US-A-6 587 474</text></patcit> describes a data bus which is shared by several components. The components possess a hierarchical transmission token and are synchronized by a synchronization pulse. A clock signal of the synchronization pulse has a rate which is between the duration of transmission of the component with the highest priority token and the cumulative duration of transmission of all components.

SUMMARY OF THE INVENTION

0010The present invention is defined in the attached independent claim. Further, preferred features may be found in the dependent claims appended hereto.

0011Other 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

0012The 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: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> illustrates an overview of a HPAV (HomePlug Audio Video) system,</li><li><figref idref="f0002">FIG. 2A</figref> illustrates a diagram of an exemplary powerline network configuration for the HPAV system in <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0002">FIG. 2B</figref> illustrates a diagram of another exemplary powerline network configuration for the HPAV system in <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0002">FIG. 2C</figref> illustrates a diagram of another exemplary powerline network configuration for the HPAV system in <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0003">FIG 3</figref> illustrates a diagram of an exemplary HPAV transceiver for HPAV system 100 in <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0004">FIG 4</figref> illustrates a diagram of an exemplary beacon period.</li></ul>

DETAILED DESCRIPTION OF THE INVENTION

0013Moreover, 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.

0014The 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.

0015<figref idref="f0001">FIG. 1</figref> 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. { XE " System block diagram" }

0016HPAV 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.

0017<figref idref="f0002">FIG. 2A</figref> illustrates an exemplary Audio Video Logical Network (AVLN) for HPAV system 100 in <figref idref="f0001">FIG. 1</figref>. 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).

0018As shown in <figref idref="f0002">FIG. 2A</figref>, AVLN 202 includes stations A, B, C, and D and CCo1. 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 <figref idref="f0002">FIG. 2A</figref>, indicates an ability for two stations, such as station A and CCo1, to communicate on the PHY level. Also shown in <figref idref="f0002">FIG. 2A</figref>, all stations can communicate with each other and, consequently, the PhyNet of all stations is the same set {A, B, C; D, CCo1}, 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 <figref idref="f0002">FIG. 2A</figref>, AVLN 202 coincides with the PhyNet of each station in AVLN 202. <tables id="tabl0001" num="0001"><table frame="all"><title><b>Table 1</b></title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="17mm" /><colspec colnum="2" colname="col2" colwidth="28mm" /><colspec colnum="3" colname="col3" colwidth="31mm" /><colspec colnum="4" colname="col4" colwidth="25mm" /><thead><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b>Physical Networks (PhyNets) in ...</b></entry></row><row><entry valign="top"><b>Station</b></entry><entry valign="top"><figref idref="f0002"><b>Figure 2A</b></figref></entry><entry valign="top"><figref idref="f0002"><b>Figure 2B</b></figref></entry><entry valign="top"><figref idref="f0002"><b>Figure 2C</b></figref></entry></row></thead><tbody><row><entry align="center">A</entry><entry align="center">{A,B,C,D,CCo1}</entry><entry align="center">{A,B,CCo1}</entry><entry align="center">{A,B,CCo1}</entry></row><row><entry align="center">B</entry><entry align="center">{A,B,C,D,CCo1}</entry><entry align="center">{A,B,CCo1}</entry><entry align="center">{A,B,CCo1}</entry></row><row><entry align="center">C</entry><entry align="center">{A,B,C,D,CCo1}</entry><entry align="center">{C.D,CCo2}</entry><entry align="center">{C,D,CCo1}</entry></row><row><entry align="center">D</entry><entry align="center">{A,B,C,D,CCo1}</entry><entry align="center">{C,D,CCo2}</entry><entry align="center">{C,D}</entry></row><row><entry align="center">CCo1</entry><entry align="center">{A,B,C,D,CCo1}</entry><entry align="center">{A,B,CCo1,CCo2}</entry><entry align="center">{A,B,C,CCo1}</entry></row><row><entry align="center">CCo2</entry><entry align="center">N/A</entry><entry align="center">{C,D,CCo1,CCo2}</entry><entry align="center">N/A</entry></row></tbody></tgroup></table></tables>

0019<figref idref="f0002">FIG. 2B</figref> illustrates two exemplary AVLNs for HPAV system 100 in <figref idref="f0001">Figure 1</figref>. As shown in <figref idref="f0002">FIG. 2B</figref>, AVLN 210 includes stations A and B and CCo1 and AVLN 212 includes CCo2 and stations C and D. The PhyNet for each station in <figref idref="f0002">FIG. 2B</figref> is shown in Table 1.

0020<figref idref="f0002">FIG. 2C</figref> illustrates an exemplary AVLN for HPAV system 100 in <figref idref="f0001">Figure 1</figref>. As shown in <figref idref="f0002">FIG. 2C</figref>, AVLN 220 includes CCo1 and stations A, B, C, and D. The PhyNet for each station in <figref idref="f0002">FIG. 2C</figref> is shown in Table 1.

0021<figref idref="f0003">FIG. 3</figref> shows a diagram of an exemplary HPAV transceiver for HPAV system 100 in <figref idref="f0001">FIG. 1</figref>. 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 <figref idref="f0001">Figure 1</figref>) receives its inputs from the MAC layer (e.g. MAC layer 120). Three separate processing chains are shown in <figref idref="f0003">FIG. 3</figref> 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.

0022At 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.

0023In the present invention, the CCo of a network (e.g. CCo1 of AVLN 202 in <figref idref="f0002">FIG. 2A</figref>) 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 <figref idref="f0004">FIG. 4</figref>. 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.

0024Each HPAV station (e.g. stations A, B, C, and D in <figref idref="f0002">FIG. 2A</figref>) monitors the channel for the presence of HP1.0 devices. When a station detects the presence of HP1.0 devices, it notifies the CCo (e.g. CC01 in <figref idref="f0002">FIG. 2A</figref>), which in turn switches the network (e.g. AVLN 202 in <figref idref="f0002">FIG. 2A</figref>) to the HPAV Hybrid mode. In the Hybrid mode operation, HPAV networks avoid interference from HP1.0 stations by coaxing the HP1.0 stations to transmit only in the CSMA/CA region of the beacon period. Thus HPAV stations and HP1.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.

0025<figref idref="f0004">FIG. 4</figref> illustrates an exemplary beacon period synchronized to an exemplary powerline cycle, according to one example of the present invention. As shown in <figref idref="f0004">FIG. 4</figref>, 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 example, beacon period 402 can be precisely equal to two periods of powerline cycle 404. As further shown in <figref idref="f0004">FIG. 4</figref>, the start of beacon period 402 can be offset from the start of a powerline cycle by a fixed duration.

0026As also shown in <figref idref="f0004">FIG. 4</figref>, 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.

0027Information 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: <ol id="ol0001" compact="compact" ol-style=""><li>(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);</li><li>(b) an additional CSMA period (e.g. when the CCo senses high level of collisions in the regular CSMA period; and</li><li>(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.</li></ol>

0028The 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 <figref idref="f0002">FIG. 2A</figref>) in the network (e.g. AVLN 202 in <figref idref="f0002">Figure 2A</figref>) to know the schedule, even if they occasionally fail to receive the beacon.

0029In addition to the Persistent Schedule, the system (e.g. HPAV system 100 in <figref idref="f0001">Figure 1</figref>) 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 miss beacon reception without losing schedule information.

0030In 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).

0031The 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.

0032Thus, as discussed above, the present invention provides an HPAV system including stations that communicate via a powerline in a powerline network, where one of the stations, which is designated as a CCo (Central Coordinator), generates a beacon that is synchronized to the powerline and includes Persistent and Non-persistent Schedules. As a result, the present invention achieves an HPAV system that advantageously provides flexible scheduling of resources in a powerline network environment.

0033From 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 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.