BROADWAY, IST-2001-32686 <strong>WP</strong>1-<strong>D2</strong> version 1, date 10-10-02 Programme: ISTMobility ofDevicesMobility ofEnvironmentExcess delay tocope withRangeUp to 3 m/sClass A: up to 15 m/sClass B: Up to 15 m/s100-150nsIndoor: 0.5 to 15 metersHL/2, IEEE802.11a assumptionWe should separate the “mobility of devices” and the“mobility of environment”.See section 2.3These parameters will be used for the design of theOFDM parameters.Naturally limited by the wallsDepends on the data rate (see section 2.4)4.2 HIPERSPOT parametersThe following tables contain first values, or range of values, that will be taken as working assumption for theproject. Note that these values are first assumptions, and some of them may change during the project if itturns out that different values would be better.Table 4.2-1: HIPERSPOT system parametersParameter Value CommentsBand59..62 GHzThis band is available worldwideChannelBandwidthsGuardBandwidthbetweenchannels20 MHz … 320 MHzPossibly 40 MHz20 MHz is the HL/2 channel size. For compatibilityreasons, a multiple of 20MHz will be used.The guard band between channels will be large in order toreduce the constraints on the filters. This value is aninitial guess.Table 4.2-2: HIPERSPOT baseband parametersParameter Value CommentsModulationOFDMOFDM is chosen because of its considerable advantagesfor high data rate systems (spectral efficiency, easyequalization, etc.), and for compatibility with existing5GHz WLANs (HL/2, IEEE802.11a) .The 60 GHz channels are expected to have an excessdelay of approx. 100…150 ns. Assuming very shortfilters in the TX/RX, a guard interval size of 200 nsseems to be sufficient (e.g. in the case where only veryGuard Intervalbroad channels are used, the filters become short).50 – 800 nssizeHowever, too short TX/RX filters are expected to lead toperformance drawbacks. In this case, either the guardinterval must be enlarged or means must be provided indigital in order to do some compensation. The 800 nsguard interval might be kept for compatibility reasonswith HL/2.This carrier spacing of 312.5 kHz is used in HL/2. At aCarrier spacing 312.5-2500 kHzfirst guess, this value should be reasonable for 60 GHz,however a phase noise study has to be carried out todetermine if a larger carrier spacing is required.FFT size 64-1024PossibleconstellationsBPSK, QPSK, 16-QAM, 64-QAMThese are the HL/2 constellations. Other constellations(e.g. 8-PSK) may be investigated too.42
BROADWAY, IST-2001-32686 <strong>WP</strong>1-<strong>D2</strong> version 1, date 10-10-02 Programme: ISTNote that Table 4.2-2 contains only the main OFDM parameters. A whole deliverable [14] produced byWork-Package 3 is devoted to the <strong>description</strong> of baseband requirements and parameters. We refer the readerto it for further details.5. Open questions in system design5.1 Multiple access issuesThe choice of the MAC protocol for Broadway has a great importance because it determines the realthroughput available for the users. Since the aim of Broadway is to supply the user with very highthroughput, the selected MAC will have to be able to deal with raw physical layer bit rates of severalhundred of Mbit/s in hot spot scenarios, i.e. when a large number of users access the medium. [Is physicallayer bit rate really dependent on number of users??]On the other hand, Broadway is expected to be as compatible as possible with existing 5GHz WLANs,namely HIPERLAN/2 and IEEE802.11a. However, since the MAC protocols of these two standards aretotally different, it will not be possible to ensure backward compatibility at the MAC layer with both ofthem. Nevertheless, it is desirable to have a certain level of compatibility with one of them. The choice is noteasy since IEEE802.11 MAC protocol relies on CSMA/CA, which is rather suitable for ad hoc networking,while HIPERLAN/2 MAC protocol is based on TDD-TDMA, which generally ensures a better QoS.Since the choice had to be made as soon as possible , because it has an impact on all the <strong>WP</strong>2 studies, <strong>WP</strong>2carried out an analytical comparison between IEEE802.11 and HIPERLAN/2 MAC protocols in terms ofachievable throughput. The complete study will be inserted in [15]. The main conclusion of this study is thatthe CSMA/CA approach implemented as in IEEE802.11 does not support high bit rates. The enhancedimplementation of IEEE802.11e offers much higher throughputs, but still not high enough for theBROADWAY project. Therefore, a direct extension of an existing implementation of a CSMA/CA schemecould not be chosen for Broadway. On the other hand, the TDD/TDMA scheme of HL/2 allows highthroughputs, and even if TDD/TDMA has certain drawbacks for ad hoc networking, it seems at the time tobe the best candidate for the BROADWAY system.5.2 Ad hoc network: to which extent?Under the framework of the BROADWAY project, several ad hoc networking issues will be considered inWork-Package 2. In particular, all scenarios that are possible to consider in one mode of operation (5 or 60GHz) can be considered also for the other. The first and most important consideration is that the defaultmode of operation is the 5 GHz mode. The 60 GHz mode of operation will be used to offload the trafficwhenever necessary. For this reason the AP (Access Point) of BROADWAY will be the main “coordinator”of all the control operations that will be required for the proper system operation. However, part of the APfunctionality can be transferred to certain MTs (Mobile Terminals) known as Cluster Heads (CH).In the following sections a number of connectivity scenarios considered in the BROADWAY project arepresented.5.2.1. Basic Scenario ConsiderationsAn important assumption is that the AP of BROADWAY can operate simultaneously at 5 GHz and 60 GHz.The AP is responsible for handling all kinds of communication (control and data) at 5 GHz. It is evident thatthere will be no such handling for MTs outside the range at 5 GHz. Each MT will start operating at 5 GHz asthe default initial mode. A period of “AP discovery” will follow, in which the MT will try to discover,whether it is in the range of an AP or not. If an AP is found, then an association phase starts that correspondsto particular operations required for the establishment of communication (e.g. exchanging Connection IDs,MAC ID).5.2.1.1. Neighbor Discovery FrequencyThe AP will periodically order each MT to switch to a specific frequency at 60 GHz and run a certainneighbor discovery algorithm. The results will be transferred to the AP. The latter will decide whether aparticular MT belongs to a “cluster” and whether the particular MT could play the role of the CH.43
- Page 3 and 4: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 6 and 7: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 8 and 9: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 10 and 11: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 12 and 13: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 14 and 15: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 16 and 17: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 18 and 19: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 20 and 21: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 22 and 23: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 24 and 25: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 26 and 27: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 28 and 29: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 30 and 31: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 32 and 33: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 34 and 35: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 36 and 37: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 38 and 39: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 40 and 41: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 44 and 45: BROADWAY, IST-2001-32686 WP1-D2 ver
- Page 46: BROADWAY, IST-2001-32686 WP1-D2 ver