[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

stds-802-16: TG2 Comments



Title: TG2 Comments

The following comments are from four sources
- Andy McGregor
- IEEE Project Editor
- Jack Garrison (referring to a recent contribution)
- Barry Lewis (referring to a recent contribution)

Andy McGregor, Spectrum Engineering
Wireless Internet & Mobility Systems
+1 (613) 763-7942 (ESN 393), fax: +1 (613) 765-6257 (ESN 395)
mcgregor@nortelnetworks.com
Dept M200, MS 65D/17/C03, Nortel Networks, PO Box 3511, Station C
Ottawa, Ontario, K1Y 4H7, Canada

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
9

[Starting Line #]
28

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Insert the following definitions in section 3.1

3.1.xx harmonized transmissions
When two operators use a compatible frequency bandplan (FDD) or time slot structure (TDD) such that the base
stations from two operators can share a transmitter site, so as to minimize interference.  For FDD systems this
implies the both operators have base-station transmit in adjacent sub-blocks and terminal transmit in the
corresponding paired blocks.  For TDD systems, harmonization implies frame, slot and direction synchronization.

3.1.yy synchronized transmissions
This implies both operators use the same frame slot and direction synchronization.  That is the same TDD frame
structure (same frame length, timeslot positions and base-transmit timeslots) and also that the timing of the frames is

closely aligned, so that emissions from slot 1 on operator 1 only interfere with slot 1 of operator 2, etc

[Reason for Edit]
This explains some text used elsewhere in the document.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
28

[Starting Line #]
23

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Add a new subsection at the end of section 5.3.1

5.3.1.4 FDD and TDD Coordination
The interference scenarios can be significantly impacted by the level of harmonization and / or synchronization
between transmissions.  This is especially true for co-located base station equipment.  If large guard-bands are used,
co-location may also be possible without negative effects.

5.3.1.4.1 FDD - FDD Coordination
One mechanism to reduce interference for FDD systems is for both base-station transmitters to be co-located.  This
requires harmonized transmissions from both operators.  If a base station of operator "A" transmits in sub-block
"A1" and a base station of operator "B" transmits in sub-block "B1", which are close to one another in frequency
and paired with sub-blocks "A2" and "B2" respectively, which are also close to one another, then the FDD duplex
filter deployed in both bases and terminals helps prevent emissions from A1/B1 block from interfering with
emissions from the paired A2/B2 block.

5.3.1.4.2 TDD - TDD Coordination
One mechanism to reduce interference for TDD systems is for both base-station transmitters to be co-located.  This
requires harmonized transmissions from both operators.  In this case the emissions from both operators must be
synchronized transmissions, otherwise significant interference can occur from one base into the co-located base
station.  Synchronization can include both co-located stations transmitting simultaneously or for low traffic
situations, both base stations transmitting alternately, but NOT when either operators terminals are transmitting.

5.3.1.4.3 TDD - FDD Coordination
Due to the inherently different time frame structures, it is unlikely that TDD and FDD systems can be successfully
coordinated on a single antenna structure without large frequency guard bands.

[Reason for Edit]
This completes a hole in the document identified at the TG2 Interim meeting in Ottawa.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
15

[Starting Line #]
29

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Replace the text for Recommendation 4 with the following:

Resolution of coexistence issues is frequently a bi-lateral process and thus incumbents/first movers should have the
same status as operators who deploy at a later time.  However, practicality suggests that it is also legitimate to weigh

the capital investment that any change would impose on an incumbent operator versus any change in capital
investment that the new operator must make, in order to resolve coexistence issues. The logic behind this
Recommendation is that some coexistence problems cannot be resolved simply by modifications to the system of a
new entrant into a region. Rather, they require the willingness of an incumbent to potentially make modifications as
well. It is recognized that this Recommendation is especially challenging in the AdjCh scenario where the
overlapping territories means the incumbent and the new entrant may be competing for the same clients.  Equally it
is incumbent on the new entrant to make major efforts to avoid interference as he has no imbedded hardware. 
However, for the BWA industry to succeed, the incumbent must be willing to constructively participate in the
application of interference mitigation measures.

[Reason for Edit]
This improves the readability of the text.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
73

[Starting Line #]
21

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
At the TG2 Interim meeting, the Annex B subsection on "30-40 GHz" was deleted.  It is recommended that the
following text be inserted in place of the original text.

38-43.5 GHz
Equation (8) shows a dependency of the psfd on the wavelength lambda.  Thus the psfd limit of -114 dBW/MHz/m2
needs correction to the 38-43.5 GHz band.  At 40 GHz, lambda = 0.075 m and substituting into equation (8)
(retaining other assumptions) gives -111 dBW/MHz/m2.

[Reason for Edit]
Completes some of the technical text and validates the threshold value of -111 dBW/MHz/m2.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
100

[Starting Line #]
2

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
The Bibliography should be marked as Annex G.
Why do the Bibliography items D1 to D27 have the prefix "D"?  If this is because they were once in Annex D, then
they should be updated with their new location e.g. Annex G.  This will also impact the location of any cross-
reference within the document.

[Reason for Edit]
This improves the readability of the text.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
1

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Change the running footer to read
"Copyright 2000 IEEE.  All rights reserved.   This is an unapproved IEEE Standards Draft, subject to change."

[Reason for Edit]
Change recommended by the IEEE Project Editor.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
68

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
All Annexes should be labelled explicitly as Informative.
[Reason for Edit]
Change recommended by the IEEE Project Editor.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
68

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
All figures and tables in annexes should be numbered and numbering resets within each annex.

[Reason for Edit]
Change recommended by the IEEE Project Editor.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
1

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
All notes should be clearly delineated from normative text.  Notes are informative text.

[Reason for Edit]
Change recommended by the IEEE Project Editor.

[Submitter's Last Name]
McGregor

[Submitter's First Name]
Andy

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
1

[Starting Line #]
1

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
E

[Detailed Description of Proposed Insertion, Deletion, Change]
Any text or diagrams taken from outside sources need the permission from the copyright owner.  NOTE the
boilerplate on official IEEE 802.16 contributions typically provides this permission, but may need to check on the
status of extracts from ETSI documents.

[Reason for Edit]
Change recommended by the IEEE Project Editor.

[Submitter's Last Name]
Garrison

[Submitter's First Name]
Jack

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
28

[Starting Line #]
23

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
T

[Detailed Description of Proposed Insertion, Deletion, Change]
Use the content of contribution IEEE 802.16.2c-00/21 to make a new subsection "5.3.1.5 Likelihood of Multiple
Interferers" or in section 6.3.1
Add a suitable cross-reference to this section at other points in the document e.g. in Recommendation 1.

[Reason for Edit]
This proposes new text justifying the use of a -6 dB threshold and the likelihood of multiple dominant interferers.

[Submitter's Last Name]
Lewis

[Submitter's First Name]
Barry

[Membership Status: (M)ember; (O)bserver; (N)either]
M

[Starting Page #]
60

[Starting Line #]
11

[(T)echnical for Content-Related Material; (E)ditorial for typos, grammar, etc.;
(G)eneral to identify a problem but not a solution; (TBD) for a
comment on a section marked "TBD"]
TBD

[Detailed Description of Proposed Insertion, Deletion, Change]
Use the content of contribution IEEE 802.16.2c-00/22 as content for section8.1.10

[Reason for Edit]
This proposes new text completing a TBD section.