Additional Preamble Definitions for 802.16d OFDMAdditional Preamble Definitions for 802.16d OFDM--256256
`
`IEEE 802.16 Presentation Submission Template (Rev. 8.3)
`Document Number: IEEE C802.16d-04/36r2
`
`Date Submitted: 2004-03-17
`
`Source:
`Adam Kerr, Paul Petrus
`ArrayComm, 2480 North First St.
`San Jose, CA 95131-1014
`
`Venue:
`March 14-18 Orlando, Florida, US
`
`Voice:
`Fax:
`E-mail:
`
`408-428-9080
`408-428-9083
`adam@, petrus@arraycomm.com
`
`Purpose:
`To describe the need for multiple preamble definitions for network reuse planning purposes.
`
`Notice:
`This document has been prepared to assist IEEE 802.16. 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.16.
`
`IEEE 802.16 Patent Policy:
`The contributor is familiar with the IEEE 802.16 Patent Policy and Procedures <http://ieee802.org/16/ipr/patents/policy.html>, 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 <mailto:chair@wirelessman.org> 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.16
`Working Group. The Chair will disclose this notification via the IEEE 802.16 web site <http://ieee802.org/16/ipr/patents/notices>.
`
`ERIC-1009
`Ericsson v. IV
`Page 1 of 6
`
`

`
`Additional Preamble Definitions for
`802.16d OFDM-256
`
`Adam Kerr and Paul Petrus
`ArrayComm, Inc.
`March 11, 2004
`
`ERIC-1009
`Page 2 of 6
`
`

`
`Problem Statement
`• Consider a TDD network with a low reuse
`frequency plan:
`– Network will need to be frame synchronized to avoid
`undue interference problems (between
`uplink/downlink)
`– In downlink, SS will detect signals from multiple base
`stations
`– Current long preamble marking the start of the
`downlink frame has only a single definition
`– Interference between multiple BS transmissions of the
`same preamble will result in degraded frame
`synchronization and channel estimation by the SS
`• Similar issues can occur in uplink
`
`ERIC-1009
`Page 3 of 6
`
`

`
`Suggested Remedy
`
`• Design a set of preambles to replace each of the current
`preambles, supporting a reuse pattern:
`– Unique preambles with good cross-, auto-correlation
`– Frequency-spread subchannel preambles
`– Cyclic time shifted versions of the above
`• The preambles for which to consider designing
`replacement sets include:
`– 4x64, 2x128
`– AAS network entry preamble
`– STC preamble
`– Subchannel preambles
`• Support for new preambles would be mandatory for all SS
`
`ERIC-1009
`Page 4 of 6
`
`

`
`Design Issues
`
`• How many distinct preambles in each set
`that replaces current preamble definitions?
`– Are distinct frame start preambles required?
`– Impact on SS performance requirements
`• Low PAR required
`• Good auto-correlation and cross-correlation
`properties required
`
`ERIC-1009
`Page 5 of 6
`
`

`
`Proposal
`
`• Subgroup of interested 802.16 members to discuss detailed
`preamble design for May interim meeting:
`– Naftali Chayat, Alvarion
`– Dale Branlund, BeamReach
`– Hassan Yaghoobi, Minnie Ho, Intel Corp
`– Bogdan Franovici, Redline Communications
`– Roger Bertschmann, SiWorks
`– Martin Lysejko, David Castelow, Ofer Kelman, Airspan
`• To be added, please email adam@arraycomm.com
`
`ERIC-1009
`Page 6 of 6