January 2007 Doc IEEE 802 22 070019 r

  • Slides: 11
Download presentation
January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PHY Single Channel Specifications

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PHY Single Channel Specifications IEEE P 802. 22 Wireless RANs Date: 2007 -01 -09 Notice: This document has been prepared to assist IEEE 802. 22. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802. 22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures http: //standards. ieee. org/guides/bylaws/sb-bylaws. pdf including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard. " Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair Carl R. Stevenson as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802. 22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at patcom@iee. org. > Submission Runcom Technologies Ltd. 1 Eli Sofer, Runcom 1

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PHY Single Channel Specifications

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PHY Single Channel Specifications Submission Runcom Technologies Ltd. 2 Eli Sofer, Runcom 2

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 General The 802. 16

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 General The 802. 16 Phy has been studied extensively and is suitable for fixed and nomadic scenarios including outdoor to indoor and use of Beam. Forming which will play a critical role in WRAN. Submission Runcom Technologies Ltd. 3 Eli Sofer, Runcom 3

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations Preambles

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations Preambles • We recommend use of a single frame preamble with pilots every third SC (3 repetitions in the time domain with length of 1 OFDM symbol) • This preamble which will also serve as the superframe preamble (in the first frame) will allow the following estimation mechanism: • Coarse time synchronization based on the repetition property in the time domain. • Coarse frequency shift ( f) estimation and fine time synchronization • Adaptive channel estimation in both fixed and nomadic applications Submission Runcom Technologies Ltd. 4 Eli Sofer, Runcom 4

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations (Cont.

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations (Cont. ) Extensive analytical and simulation studies show that all of these objectives are attainable in different and harsh environment with a single preamble symbol. Thus, obviously this preamble concept will satisfy the 802. 22 requirements. DL Pilots • We propose to use cluster scheme (PUSC) as the basic allocation of data within the frame. The cluster pilots will allow a robust computation and the random and time varying frequency offset which will facilitate low cost synthesizer in the CPE. • We note that the use of pilots such that their union on adjacent symbols satisfies Nyquist will allow much more robust channel estimation in fixed and mobile scenarios Submission Runcom Technologies Ltd. 5 Eli Sofer, Runcom 5

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 DL Subchannel Scheme Submission

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 DL Subchannel Scheme Submission Runcom Technologies Ltd. 6 Eli Sofer, Runcom 6

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations (Cont.

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations (Cont. ) UL Pilots • We recommend use of PUSC scheme (Cluster) in the UL both with and without subchannel rotation. The use of cluster scheme with subchannel rotation will allow the receiver (BS) to benefit from robust channel estimation and frequency diversity. • PUSC without rotation will allow a very attractive means for receive beamforming techniques that will probably be invoked in rural scenarios. • The use of PUSC clusters will also ease the scheduling process since it gives every cluster the pilots it needs for adaptive channel estimation ( as UL solution tha relies on UL preambles significantly complicate the scheduler and does not retain enough pilots for Rx beamforming) Submission Runcom Technologies Ltd. 7 Eli Sofer, Runcom 7

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations (Cont.

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 Phy Design Considerations (Cont. ) Super. Frame Preamble The Superframe preamble shall be identical in format to the Frame preamble ( different PN sequences can be allocated to superframe and frames) Frame Preamble The first frame preamble (F 0) should be eliminated in a way that the superframe preamble will act on behalf of the first frame. This will ease the computational burden which is needed in the first frame. Submission Runcom Technologies Ltd. 8 Eli Sofer, Runcom 8

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 SF preamble Superframe Structure

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 SF preamble Superframe Structure Accommodating Single Channel o x DL MAP SCH o x Frame preamble x FCH x F 0 F 1 x No preamble No need for additional Frame preamble in F 0. Serves the Single channel requirement for less complexity. No impact or adverse consequences concerning the MAC layer and Submission Runcom Technologies Ltd. 9 Eli Sofer, Runcom 9

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PN Sequences • Our

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PN Sequences • Our recommendation is to use the PN Sequences proposed in Runcom`s contribution and used in IEEE 802. 16. The big advantage of these sequences presides on the fact that they have been chosen to optimize PAPR at the transmitter and have been verified through extensive simulation studies by numerous parties. Only one symbol is required for preamble • Together with the proposal for identical preambles for Superframe and frames, the usage of the above mentioned PN sequences offer a large set of sequences with the important factor of simplicity of realization. For instance, the allocation of a subset of the PN sequences to Frame preamble and disjoint subset to Superframes preambles. This will allow the user to distinguish between Superframes and Frames and different set CPEs or Base Stations Submission Runcom Technologies Ltd. 10 Eli Sofer, Runcom 10

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PAPR Comparison Submission Runcom

January 2007 Doc. : IEEE 802. 22 -07/0019 r 0 PAPR Comparison Submission Runcom Technologies Ltd. 11 Eli Sofer, Runcom 11