PTOlSB/16 (10-05)
`Approved for use through 07/31/2006. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995. no persons are required to respond to a collection of information unless it displays a valid OMB control number.
`PROVISIONAL APPLICATION FOR PATENT COVER SHEET — Page 1 of 2
`This is a request for filing a PROVISIONAL APPLICATION FOR PATENT under 37 CFR1.53(c).
`Express-WWW —
`
`Given Name (first and middle [if any])
`
`Family Name or Surname
`
`Residence
`Cit and either State or Forei-n Countr
`
`ANUP K.
`
`MARK C.
`
`KEVIN L.
`
`AMITAVA
`
`STAVROS
`
`TALUKDAR
`
`CUDAK
`
`BAUM
`
`GHOSH
`
`TZAVIDAS
`
`SCHAUMBURG, IL 60195
`
`ROLLING MEADOWS, IL 60008
`
`ROLLING MEADOWS, IL 60008
`
`BUFFALO GROVE, IL 60089
`
`EVANSTON, IL 60201
`
`
`
`separately numbered sheets attached hereto
`4 II:I
`Additional inventors are being named on the
`TITLE OF THE INVENTION (500 characters max):
`
`MEDIUM ACCESS CONTROL FRAME STRUCTURE IN WIRELESS COMMUNICATION
`SYSTEM
`
`Direct all correspondence to:
`
`CORRESPONDENCE ADDRESS
`
`The address corresponding to Customer Number:
`
`20280
`
`OR
`
`Firm or
`IndeuaI Name
`
`ENCLOSED APPLICATION PARTS (check all that apply)
`
`Application Data Sheet. See 37 CFR 1.76
`Specification Number ofPages 42
`Drawing(s) Number ofSheets
`14
`If the specification and drawings exceed 100 sheets of paper, an application size fee is
`Fees Due: Filing Fee of $200 ($100 for small entity).
`also due, which is $250 ($125 for small entity) for each additional 50 sheets or fraction thereof. See 35 U.S.C. 41 (a)(1 )(G) and 37 CFR 1.16(s).
`
`CI CDts), Number of CDs
`I:I Other (specify)
`
`METHOD OF PAYMENT OF THE FILING FEE AND APPLICATION SIZE FEE FOR THIS PROVISIONAL APPLICATION FOR PATENT
`
`|:|
`I:I Applicant claims small entity status. See 37 CFR 1.27.
`I:I A check or money order is enclosed to cover the filing fee and application size fee (if applicable).
`TOTAL FEE AMOUNT ($)
`I:I Payment by credit card. Form PTO-2038 is attached
`The Director is hereby authorized to charge the filing fee and application size fee (if applicable) or credit any overpayment to Deposit
`Account Number:
`502117
`. Adeplicati‘veeepysf-this-fesmiscnslesed-ferufee-preeessing.-
`USE ONLY FOR FILING A PROVISIONAL APPLICATION FOR PATENT
`This collection of information is required by 37 CFR 1.51. The information is required to obtain or retain a benefit by the public which is to file (and by the USPTO
`to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.11 and 1.14. This collection is estimated to take 8 hours to complete,
`including gathering, preparing, and submitting the completed application form to the USPTO. Time will vary depending upon the individual case. Any comments
`on the amount of time you require to complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent
`and Trademark Office. U.S. Department of Commerce. PO. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR COMPLETED FORMS TO THIS
`ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`If you need assistance in completing the form, call 1-800-PTO-9199 and select option 2.
`
`ZyXEL Communications Corporation Ex. 1013
`Page 1 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 1 of 58
`
`

`

`PROVISIONAL APPLICATION COVER SHEET
`Page 2 of 2
`
`PTO/SB/16(10-05)
`Approved for use through 07/31/2006. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it displays a valid OMB control number.
`
`The invention was made by an agency of the United States Government or under a contract with an agency of the United States Government.
`No.
`
`El Yes, the name of the US. Government agency and the Government contract number are:
`
`
`
`WARNING:
`Petitioner/applicant is cautioned to avoid submitting personal information in documents filed in a patent application that may
`contribute to identity theft. Personal
`information such as social security numbers, bank account numbers, or credit card
`numbers (other than a check or credit card authorization form PTO-2038 submitted for payment purposes) is never required by
`the USPTO to support a petition or an application.
`If this type of personal information is included in documents submitted to
`the USPTO, petitioners/applicants should consider redacting such personal information from the documents before submitting
`them to the USPTO. Petitioner/applicant is advised that the record of a patent application is available to the public after
`publication of the application (unless a non—publication request in compliance with 37 CFR 1.213(a) is made in the application)
`or issuance of a patent. Furthermore, the record from an abandoned application may also be available to the public if the
`application is referenced in a published application or an issued patent (see 37 CFR 1.14). Checks and credit card
`authorization forms PTO—2038 submitted for payment purposes are not retained in the application file and therefore are not
`publicly available.
`
`SIGNATURE lROLAND K. BOWLER ||/
`Date AUGUST 15, 2007
`
`
`TYPED or PRINTED NAME ROLAND K. BOWLER ||
`REGISTRATION No.33 477
`{if appropriate)
`TELEPHONE 847-523-3978 DocketNumber: CML05790
`
`
`
`ZyXEL Communications Corporation Ex. 1013
`Page 2 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 2 of 58
`
`

`

`Atty. Docket No. CML05790
`
`MEDIUM ACCESS CONTROL FRAME STRUCTURE IN
`
`WIRELESS COMMUNICATION SYSTEM
`
`FIELD OF THE DISCLOSURE
`
`[0001]
`
`The
`
`present
`
`disclosure
`
`relates
`
`generally
`
`to wireless
`
`communications and more specifically to medium access control
`
`frame
`
`structures in wireless communication systems with improved latency support.
`
`BACKGROUND
`
`[0002]
`
`An
`
`important
`
`consideration
`
`for
`
`advanced
`
`wireless
`
`communication systems is one-way air-interface latency. Air—interface latency
`
`is primarily dependent on the Medium Access Control (MAC) frame duration.
`
`In the developing IEEE 802.16m protocol, for example, the proposed target
`
`latency is less than approximately 10 msec and some observers have suggested
`
`that a much lower latency may be required to compete with other developing
`
`protocols, for example, with 3GPP Long Term Evolution (LTE). The IEEE
`
`802.16m protocol is an evolution of the WiMAX—OFDMA specification for the
`
`IEEE 802.16e protocol. However, the legacy IEEE 802.16e TDD frame structure
`
`has a relatively long duration and is incapable of achieving the latency targets
`
`set for IEEE 802.16m.
`
`[0003]
`
`Evolutionary wireless
`
`comnlunication systems
`
`should also
`
`support for legacy system equipment. For example, some IEEE 802.16e and
`
`IEEE 802.16m base stations and mobile stations are likely to coexist within the
`
`same network while upgrading to the newer system. Thus IEEE 802.16e
`
`mobile stations should be compatible with IEEE 802.16m base stations, and
`
`IEEE 802.166 base stations should support IEEE 802.16m mobile stations. Thus
`
`ZyXEL Communications Corporation Ex. 1013
`Page 3 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 3 of 58
`
`

`

`Atty. Docket No. CML05790
`
`frame structures for air-interfaces are proposed with a view to achieving lower
`
`latency and in some embodiments to maintaining backward compatibility.
`
`[0004]
`
`A legacy system is defined as a system compliant with a subset of
`
`the WirelessMAN—OFDMA capabilities
`
`specified by
`
`IEEE 802.16-2004
`
`(specification IEEE Std 802.16—2004: Part 16: IEEE Standard for Local and
`
`metropolitan area networks: Air Interface for Fixed Broadband Wireless
`
`Access Systems, June 2004) and amended by IEEE 802.16e-2005 (IEEE Std.
`
`802.16e—2005, IEEE Standard for Local and metropolitan area networks, Part
`
`16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems,
`
`Amendment 2: Physical and Medium Access Control Layers for Combined
`
`Fixed and Mobile Operation in Licensed Bands, and
`
`IEEE Std. 802.16-
`
`2004/ Cor1-2005, Corrigendum 1, December 2005 ) and IEEE 802.16Cor2/ D3,
`
`where the subset is defined by WiMAX Forum Mobile System Profile, Release
`
`1.0 (Revision 1.4.0: 2007-05-02), excluding specific frequency ranges specified
`
`in the section 4.1.1.2 (Band Class Index).
`
`[0005]
`
`The various aspects, features and advantages of the disclosure
`
`will become more fully apparent to those having ordinary skill in the art upon
`
`careful consideration of the following Detailed Description thereof with the
`
`accompanying drawings described below. The drawings may have been
`
`simplified for clarity and are not necessarily drawn to scale.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0006]
`
`FIG. 1 is a wireless conununication system.
`
`ZyXEL Communications Corporation Ex. 1013
`Page 4 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 4 of 58
`
`

`

`Atty. Docket No. CML05790
`
`FIG.
`
`[0007]
`
`sub-frame.
`
`FIG.
`
`FIG.
`
`[0008]
`
`[0009]
`
`cycle.
`
`2 is a legacy protocol frame mapped to a next generation 1:2
`
`3 is a frame structure configuration having a 75 % duty cycle.
`
`4 is another frame structure configuration having a 25 % duty
`
`[00010]
`
`FIG.
`
`5 is a super—frame structure configuration.
`
`[00011]
`
`FIG.
`
`6 is a frame having multiple sub-blocks of equal duration.
`
`FIG.
`
`[00012]
`
`duration.
`
`7 is another frame having multiple sub-blocks of equal
`
`[00013]
`
`FIG.
`
`8 is a frame having multiple sub-blocks of equal duration.
`
`FIG.
`
`[00014]
`
`duration.
`
`9 is a super-frame comprising multiple frames of equal
`
`[00015]
`
`FIG.
`
`10 is an exemplary hybrid frame structure.
`
`FIG.
`
`FIG.
`
`[00016]
`
`regions.
`
`[00017]
`
`regions.
`
`11 is a frame having first and second protocol resource
`
`12 is another frame having first and second protocol resource
`
`Q)
`
`ZyXEL Communications Corporation Ex. 1013
`Page 5 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 5 of 58
`
`

`

`Atty. Docket No. CML05790
`
`[00018]
`
`FIG. 13 is a frame having first and second protocol resource
`
`regions.
`
`[00019]
`
`FIG. 14 is a frame having first and second protocol resource
`
`regions.
`
`[00020]
`
`FIG. 15 is a frame having first and second protocol resource
`
`regions.
`
`[00021]
`
`FIG. 16 is a sequence of radio frames having first and second
`
`resource regions.
`
`[00022]
`
`FIG. 17 is another sequence of radio frames having first and
`
`second resource regions.
`
`[00023]
`
`FIG. 18 is another sequence of radio frames having first and
`
`second resource regions.
`
`DETAILED DESCRIPTION
`
`[00024]
`
`In FIG. 1, the Wireless communication system 100 includes one or
`
`more fixed base infrastructure units forming a network distributed over a
`
`geographical region. A base unit may also be referred to as an access point,
`
`access terminal, Node—B, eNode-B, or by other terminology used in the art.
`
`The one or more base units 101 and 102 serve a number of remote units 103
`
`and 110 within a serving area, for example, a cell, or Within a cell sector. The
`
`remote units may be fixed or terminal. The remote units may also be referred
`
`ZyXEL Communications Corporation Ex. 1013
`Page 6 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 6 of 58
`
`

`

`Atty. Docket No. CML05790
`
`to as subscriber units, mobile stations, users, terminals, subscriber stations,
`
`user equipment (UE), terminals, or by other terminology used in the art.
`
`[00025]
`
`Generally,
`
`base
`
`units
`
`101
`
`and
`
`102
`
`transmit
`
`downlink
`
`communication signals 104 and 105 to serving remote units on at least a
`
`portion of the same resources (time and/ or frequency). Remote units 103 and
`
`110 communicate with the one or more base units 101 and 102 via uplink
`
`communication signals 106 and 113. The one or more base units may comprise
`
`one or more transmitters and one or more receivers that serve the remote
`
`units. The remote units may also comprise one or more transmitters and one
`or more receivers.
`
`[00026]
`
`In one embodiment, the communication system utilizes OFDMA
`
`or a next generation single-carrier (SC) based FDMA architecture for uplink
`
`transmissions,
`
`such as
`
`interleaved FDMA (IFDMA), Localized FDMA
`
`(LFDMA), DPT-spread OFDM (DFT—SOFDM) with IFDMA or LFDMA.
`
`In
`
`OFDM based systems, the radio resources include OFDM symbols, which may
`
`be divided into slots, which are groupings of sub-carriers. An exemplary
`
`OFDM based protocol is IEEE 802.16(e).
`
`[00027]
`
`Generally, the wireless communication system may implement
`
`more than one communication technology as is typical of systems upgraded
`
`with newer technology, for example, the evolution of GSM to UMTS and
`
`future UMTS releases thereof.
`
`In FIG. 1, for example, one or more of the base
`
`units 101 may be legacy technology base stations, for example, IEEE 802.16(e)
`
`protocol base stations, and other base station may be newer generation
`
`technologies, for example, IEEE 802.16(m) protocol base stations.
`
`In these
`
`cases,
`
`it
`
`is generally desirable for the new technologies to be backward
`5
`
`ZyXEL Communications Corporation Ex. 1013
`Page 7 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 7 of 58
`
`

`

`Atty. Docket No. CMLO5790
`
`compatible with the legacy technology. For the evolution of IEEE 802.16(e),
`
`the backward compatibility constraint implies that the legacy frame structure,
`
`for example, the 5 msec duration 802.16(e) frame, must be supported by
`
`802.16(m) base stations. Additionally, in order to efficiently support delay
`
`sensitive applications, 802.16(m) base stations should be able to service both
`
`802.16(m) and legacy terminals within the common frame structure.
`
`[00028]
`
`Regarding frame structure,
`
`it is generally necessary to design
`
`frames having a relatively short duration in order to reduce latency. Thus to
`
`deliver low latency in 802.16m systems with backward compatibility, it is
`
`necessary to develop a sub-frame structure based on the legacy 802.16(e)
`
`frame.
`
`In order to address the latency requirements, it is necessary to design
`
`frames with shorter than 5msec duration. However, to efficiently serve legacy
`
`traffic, it is also necessary that 802.16(m) systems have 5 msec legacy frames.
`
`Thus two broad classes of frames would be required for an 802.16(m) system
`
`having reduced latency and support for legacy 802.16(e) devices. The first
`
`class includes a full-frame (having a 5 msec duration) with one DL interval
`
`and one UL interval similar to the 802.16(e) TDD legacy frames. The second
`
`class of frames includes a sub-frame. For example, a 5 msec frame having N
`
`DL intervals and N UL intervals.
`
`This
`
`frame may also contain N
`
`transmit/ receive transition gap (TTG) and receive/ transmit transition gap
`
`(RTG) intervals. N could be kept small, typically N=2, in order to limit TTG
`
`and RTG related overhead. According to this exemplary scheme, the legacy
`
`802.16(e) TDD frames can only be a full—frame and the 802.16(m) frames are
`
`preferably sub-frame 122, although they could also be full-frames. The h-
`
`frames can be either full-frame or sub-frame 1:2. FIG. 2 illustrates an 802.16(m)
`
`sub-frame 1:2 that is backwards compatible with a legacy 802.16(e) TDD frame,
`
`wherein the first and third blocks are downlink blocks and the second and
`
`6
`
`ZyXEL Communications Corporation Ex. 1013
`Page 8 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 8 of 58
`
`

`

`Atty. Docket No. CML05790
`
`fourth blocks are uplink blocks. In general, the length of the intervals of the
`
`blocks can be different.
`
`[00029]
`
`The 802.16(m) 5 msec frame can be perceived to be composed of
`
`following types of basic regions:
`
`e—DL region used for
`
`transnlission of
`
`downlink traffic to 802.16(e) terminals; e-UL: region allocated for transmission
`
`of data and control messages by 802.16(e) terminals; m-DL: region allocated for
`
`transmission to 802.16(m)
`
`terminals; and m-UL:
`
`region allocated for
`
`transmission by 802.16(m) terminals. The e-DL and e—UL regions can also be
`
`used for transmissions to/ from 802.16(m) terminals. In general, the structures
`
`of the 802.16(m) region (sub-channel and pilot structures) can be different from
`
`those of the 802.16(e) regions. Depending on the population of legacy and
`
`newer generation terminals, it may be necessary to allocate the entire 5 msec
`
`frame for 802.16(e) services or 802.16(m) services.
`
`[00030]
`
`Using these different types of regions, various types of 5msec
`
`frame structures can be created to suit the traffic service requirements. These
`
`are: e—frames composed of only e—DL and e-UL regions used to serve legacy
`
`802.16(e) TDD terminals (802.16(m) terminals can also be served in these
`
`frames in legacy nlode); nl—franles composed of I’ll-DL and I’ll-UL regions only
`
`for serving only 802.16(m) terminals; h-frames containing both e-DL/ e—UL and
`
`m—DL/m—UL regions for serving 802.16(e) and 802.16(m)
`
`terminals. The
`
`802.16(m) portion and the 802.16(e) portion should be time division
`
`multiplexed so
`
`that
`
`the
`
`802.16(m)
`
`control
`
`channel, pilot,
`
`and sub-
`
`channelization can provide flexibility.
`
`[00031]
`
`Depending on the device type population and traffic pattern, it
`
`may be necessary to treat an m—frame or an h-frame as a legacy virtual frame
`7
`
`ZyXEL Communications Corporation Ex. 1013
`Page 9 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 9 of 58
`
`

`

`Atty. Docket No. CML05790
`
`in a cell/ sector. The m—DL and m—UL regions in these frames may have
`
`different sub-channel/ pilot structures than the legacy systems; those regions
`
`need to be treated as ”dead zones", which the legacy terminals should not use.
`
`The full—frame, being similar in structure to the legacy 802.16(e) frame, can be
`
`easily mapped to a legacy virtual frame with full utilization of the frame
`
`resources. However, the sub-frame 1:N, which can also be mapped to legacy
`
`802.16(e) virtual frame, will contain ”dead zone(s)” where no 802.16(e)
`
`(TDD)
`
`transmission can be allowed to ensure DL/ UL synchronization.
`
`[00032]
`
`An 802.16(m) base unit can provide service to legacy 802.16(e)
`
`terminals in full-frames.
`
`To provide service in the sub-frame 1:N,
`
`the
`
`802.16(m) base unit can map a legacy virtual 5 msec frame to N adjacent sub-
`
`frames and the train of sub-frames can be organized as a train of legacy 5msec
`
`virtual frames. There are N choices for the time division duplex frame (TDD)
`
`split position in a legacy virtual frame. The system wide synchronization
`
`requirement
`
`for
`
`the TDD system imposes additional constraints on the
`
`downlink and uplink transmission intervals, creating dead zones during
`
`which no transmission should be done to and from legacy 802.16(e) TDD
`
`terminals. However,
`
`transmissions to and from 802.16(m)
`
`terminals are
`
`possible in these dead zones. FIG. 3 illustrates a first configuration wherein a
`
`legacy 802.16(e) TDD terminal encounters a 5 msec frame having a 75 % duty
`
`cycle. The frame includes a legacy preamble 302, a DL map 304, and a dead
`
`zone 306 during which there is no legacy downlink allocation during the
`
`802.16(m) uplink interval. FIG. 4 illustrates a second configuration wherein
`
`the frame includes a dead zone 406 during which there is no legacy uplink
`
`allocation during the 802.16(m) downlink interval.
`
`ZyXEL Communications Corporation Ex. 1013
`Page 10 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 10 of 58
`
`

`

`Atty. Docket No. CML05790
`
`[00033]
`
`A generic message structure and its parameters to indicate a dead
`
`zone is shown in Table 1.
`
`Table 1 Message parameter for dead zone indication
`Parameter
`value
`
`
`
`location <symbol number>/ <tirne>
`
`
`
`
`
`
`
`dedicated pilot tag
`
`0 or 1
`
`[00034]
`
`In the above message,
`
`the parameter “location" indicates a
`
`position within the frame in time (which may be denoted by the symbol
`
`number within the frame or absolute time or time offset from the start of the
`
`frame or offset from some other specified time); the interpretation of the
`
`parameter ”location" depends on the value of the parameter "dedicated pilot
`I:
`tag .
`
`If ”dedicated pilot tag" is 1, the pilot symbols after ”location" are
`
`dedicated; if it is 0, it indicates that the pilot symbols after the ”location” are
`
`not dedicated pilots. Thus a zone with dedicated pilots can be described by
`
`two occurrences of this message: the first message with dedicated pilot tag=1
`
`and location=”T1”, followed by a 2nd message with dedicated pilot tag = 0 and
`
`location="T2", where T2>=T1; a legacy terminal which has been allocated
`
`resources within this zone should use only pilots within its burst for channel
`
`estimation. A legacy terminal which has not been allocated resources within
`
`this zone will ignore the pilots in this zone and also it will not need to decode
`
`any of the data transmissions within the dedicated pilot zone. This combined
`
`with the BS not making an allocation to any 16e mobile in the zone indirectly
`
`disables or isolates the 16e mobiles from this zone.
`
`Thus, 16e mobile
`
`effectively ignores whatever is in the zone.
`
`ZyXEL Communications Corporation Ex. 1013
`Page 11 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 11 of 58
`
`

`

`Atty. Docket No. CML05790
`
`[00035]
`
`An example message which can be used for indicate dead zones is
`
`the STC_DL_ZONE_IE() of
`
`IEEE 802.16e
`
`specification;
`
`the parameters
`
`"OFDMA symbol offset" and "Dedicated pilots" in this message corresponds
`
`to the parameters ”location” and ”dedicated pilot tag” in the above generic
`
`message in Table 1.
`
`[00036]
`
`Another message structure and its parameters which can be used
`
`to implement dead zones are shown in Table 2.
`
`Table 2 Dead zone message type 2
`Parameter
`value
`
`
`Starting symbol
`<symbol number>/ <time>
`
`
`
`
`
`
`
`
`Starting sub-channel
`
`<sub-carrier number>/ <sub-channel number>
`
`Symbol count
`
`<Number of symbols>/ <duration in time>
`
`Sub—channel count
`
`<number of
`
`sub-carriers>/ <number of
`
`sub—
`
`channels>
`
`[00037]
`
`The four parameters describe a rectangular dead zone of time-
`
`frequency resources.
`
`In this message,
`
`the parameter ”starting symbol"
`
`indicates a position within the frame in time (which may be denoted by the
`
`symbol number within the frame or absolute time or time offset from the start
`
`of the frame or offset from some other specified time) where the dead zone
`
`begins; ”symbol count” indicates the duration of the dead zone, starting from
`
`the "starting symbol". The parameter ”starting sub-channel” indicates the
`
`location in the sub-carrier frequency where the dead zone begins; this is in
`
`units of sub—carrier or sub-channel, which is a group of sub-carriers; ”sub-
`
`channel count" indicates the length of the dead zone in the frequency
`
`dimension. An
`
`example
`
`of
`
`this
`
`generic message
`
`type
`
`is
`
`the
`
`10
`
`ZyXEL Communications Corporation Ex. 1013
`Page 12 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 12 of 58
`
`

`

`Atty. Docket No. CML05790
`
`PAPR_Reduction_and_Safety_Zone_Allocation_IE()
`
`of
`
`the
`
`IEEE 802.16e
`
`specification.
`
`In this message,
`
`the parameters ”OFDMA_symbol_offset”,
`
`"Subchannel offset", ”No. OFDMA symbols" and ”No.
`
`sub—channels"
`
`corresponds to the parameters ”starting symbol”, ”starting sub-channel”,
`
`”symbol count" and "sub-channel count" of the generic dead zone message
`
`type 2,
`
`respectively;
`
`the PAPR_Reducti0n_Safety_Zone parameter in the
`
`PAPR_Reduction_and_Safety_Zone_Allocation_IE() should be set to ”1” to
`
`indicate a reduced interference zone to the legacy terminal; this will effectively
`
`direct the terminal not to perform any uplink transmission in that zone.
`
`[00038]
`
`Striking a balance between efficient
`
`legacy support and low-
`
`latency 802.16(m) service is challenging with a homogeneous frame size. The
`
`full-frames discussed above provide efficient legacy support while sacrificing
`
`latency performance for 802.16(m) terminals. The sub-frames provide low-
`
`latency support for 802.16(m) terminals while sacrificing capacity for legacy
`
`terminals in the form of dead zones.
`
`[00039]
`
`In one embodiment, a heterogeneous configuration contains both
`
`full-frames and sub—frames, wherein the full-frames and sub—frames are
`
`interleaved over time. Within a cell, the full-franles are primarily used for
`
`serving legacy terminals present
`
`in the cell, whereas the sub-frames are
`
`primarily used to serve the 802.16(m) terminals. However, for servicing
`
`packets with urgent delay constraints, either frame type can be used to service
`
`either type of terminal. The full-frames and the sub-frames are organized in a
`
`repeating pattern, called a super-frame.
`
`[00040]
`
`In the super-frame of FIG. 5, the interleaving pattern consists of
`
`two sub-frames 1:2 followed by one full—frame. This pattern is generally the
`11
`
`ZyXEL Communications Corporation Ex. 1013
`Page 13 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 13 of 58
`
`

`

`Atty. Docket No. CML05790
`
`same over all sector/ cells. The first super-frame contains an 802.16(e) TDD
`
`virtual frame configuration with 75% duty cycle and the 2nd super—frame
`
`contains a 802.16(e) TDD Virtual frame configuration with 25% duty cycle.
`
`Generally, for the same 802.16(e) TDD Virtual frame, the configuration options
`
`can be different for different base stations. One base station may employ the
`
`802.16(e) Virtual frame to communicate with a legacy terminal while another
`
`neighboring base station may employ a 16m Sub-frame 1:2 structure to
`
`communicate with a 16m base station without any undesired interference
`
`between uplink and downlink transmissions. The proportion of the different
`
`types of frames and their interleaving pattern in a super-frame is generally
`
`determined by the proportion of 802.16(e) and 802.16(m) terminals in the
`
`system. The configurations may be iInplemented on a system-wide basis to
`
`ensure that there is no conflict between base unit transmission and reception in
`
`adjacent cells (e.g., no conflict in TDD Tx/Rx boundaries among adjacent
`
`cells).
`
`[00041]
`
`Thus a next generation wireless communication infrastructure
`
`entity, for example, an 802.16(m) base unit in FIG. 1, would transmit a super-
`
`frame including a plurality of frames wherein each frame includes at least two
`
`regions. The regions are generally some sort of resource that may be allocated
`
`to the terminals for uplink or downlink communications in the case of a TDD
`
`system. The super-frames are generally transmitted in a sequence. This
`
`superframe structure must be communicated to all base stations in a TDD
`
`system to maintain synchronization of all sectors and cell in order to ensure
`
`that there is no conflict between base unit transmission and reception in
`
`adjacent cells. This structure may be communicated in a control message
`
`specifying a configuration characteristic of the regions within each frame of a
`
`super-frame. The control message may be transmitted to other base stations
`12
`
`ZyXEL Communications Corporation Ex. 1013
`Page 14 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 14 of 58
`
`

`

`Atty. Docket No. CML05790
`
`over the land line network or by other means such as radio communication
`
`links between the base stations. This control message may also be transmitted
`
`to terminals in at least one frame of the superframe. The message may specify
`
`the configuration characteristic of regions within each frame of the same
`
`super-frame in which the message occurs, or in the frames of another super-
`
`frame, for example a subsequent super-frame.
`
`In one embodiment,
`
`the
`
`configuration characteristic of the regions within each frame of the super-
`
`frame is specified in a control message map or by other means. In any case, in
`
`some embodiments, the control message may contain a reference number
`
`specifying the map applicable for the super—frame, thereby enabling terminals
`
`to distinguish among versions of
`
`the control message containing the
`
`configuration characteristic.
`
`[00042]
`
`In one embodiment, the configuration characteristic of the regions
`
`is selected from a group comprising: a number regions; region size; region
`
`type (e.g., uplink or downlink for a TDD system); and the ordering of the
`
`regions. Multiple characteristics may also be specified.
`
`In one embodiment,
`
`for a TDD system, the control message specifies whether the regions of the
`
`frame are uplink regions or downlink regions. Thus the regions are selected
`
`fron1 a group of regions comprising: an uplink region and a downlink region.
`
`The control message may also specify the number of uplink regions or
`
`downlink regions within each frame of a super-frame. In some embodiments,
`
`the control message specifies a size of uplink regions or downlink regions
`
`within each frame of a super-frame.
`
`In FIG.5, the frames generally have
`
`different numbers of resource blocks (a resource block is a downlink or uplink
`
`transmission interval). For example, the first and second 5 msec sub-frames
`
`have four resource blocks, and the third 5 msec sub—frame has two blocks.
`
`13
`
`ZyXEL Communications Corporation Ex. 1013
`Page 15 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 15 of 58
`
`

`

`Atty. Docket No. CML05790
`
`[00043]
`
`There are various ways to configure frames that provide legacy
`
`compatibility and reduce latency based on the proposed framework. Another
`
`factor to consider in the design of a new protocol frame structure is support for
`
`both TDD and FDD. Preferably, similar frame and sub—frame structures can be
`
`applied for both TDD and FDD.
`
`[00044]
`
`In one embodiment, a frame is divided into multiple blocks of
`
`equal size, wherein the blocks may support one or more protocols, for
`
`example, IEEE 802.16(e) and/ or 802.16(m). Such a frame would enable an
`
`802.16(m) wireless communication infrastructure entity to allocate radio
`
`resources to both 802.16(e) and 802.16(m) wireless terminals. Generally, the
`
`radio frame includes a plurality of blocks, including a first block and last
`
`block, wherein each block comprises a plurality of symbols.
`
`In one
`
`embodiment, each block comprises substantially the same number of symbols.
`
`The first block includes a first protocol preamble, for example, a legacy
`
`protocol preamble like 802.16(e). The remaining blocks in the frame are
`
`devoid of the first protocol preamble.
`
`[00045]
`
`Generally,
`
`the radio frame includes at least one first protocol
`
`block and/ or at least one second protocol block, for example, 802.16(6) and/ 0r
`
`802.16(m) blocks.
`
`In some embodiment, the frame includes both first and
`
`second protocol blocks.
`
`In another embodiment, the frame includes only
`
`second protocol blocks, for example, 802.16(m) blocks. The radio frame
`
`includes an allocation control message for allocating resources within a
`
`protocol block.
`
`In frames that include first and second protocol blocks, the
`
`radio frame includes a first protocol allocation control message for allocating
`
`resources in the first protocol block, and a second protocol allocation control
`
`message for allocating resources in the second protocol block.
`14
`
`In one
`
`ZyXEL Communications Corporation Ex. 1013
`Page 16 of 58
`
`ZyXEL Communications Corporation Ex. 1013
`Page 16 of 58
`
`

`

`Atty. Docket No. CMLO5790
`
`embodiment,
`
`the allocation control message is a first protocol allocation
`
`control message for allocating resources within a first protocol block of a radio
`
`frame, for example, a subsequent frame, that is different than the radio frame
`
`within which the first protocol allocation control message is located.
`
`In one
`
`embodiment, the first allocation control message is located in the first block.
`
`The first block may be a first or second protocol block, for example, an
`
`802.16(e) or 802.16(m) block.
`
`[00046]
`
`The sub-blocks may be described based on their position in the
`
`frame and the characteristics of the sub-block. For example, a 5 msec frame
`
`supporting both 802.16(e) and 802.16(m) protocols may be characterized as one
`
`of the region types discussed above. There are five types of 802.16(m) sub-
`
`blocks. Each sub block has a unique characteristic designed to achieve the
`
`backward compatibility goals and efficient 802.16(m) performance. An
`
`802.16(m) DL Lead Sub-Block contains a legacy 802.16(e) pre-amble in the first
`
`symbol. The remaining symbols of the frame may be allocated to 802.16(m).
`
`This sub-block may only be transmitted in the first sub-frame. An 802.16(m)
`
`DL Lead Compatible sub—block also contain a 802.16(e) FCH and 802.16e DL-
`
`MAP in addition to the 16e pre-amble for backward compatibility with legacy
`
`terminals. The remaining symbols are allocated to 802.016(m). The Lead
`
`Compatible sub-block may be transmitted only in the first sub-frame. An
`
`802.16(m) Synchronization Sub—Block contains a broadcast control that may be
`
`used to synchronize an 802.16(m) terminal and describe broader aspects of the
`
`802.16(m) frame. This sub—block occupies a unique position in the 5 ms frame
`
`as a reference for synchronization. The second sub-frame is an appropriate,
`
`but not necessary, position for this synchronization sub—block. An 802.16(m)
`
`DL Sub-Block is a generic 16m sub-block that contains 802.16(m) Downlink
`
`data