October 2011
IEEE P802.22
Wireless RANs doc.: IEEE 802.22-10/0038r02
TGa Conference Call Minutes (September-December)
Date: 2011-10-17
Author(s):
Name
Ranga Reddy
Company
Self
Address
400 Deal Lake Drive, Apt
2B, Asbury Park, NJ 07712
Phone
732-693-5812 email ranga.reddy@me.com
1. Attendance Abstract
This document contains minutes for TGa teleconference calls that discussed development contributions and text for the new task group's work.
October 03, October 10, October 17,
2011 2011 2011
Ranga Reddy Self X X
R0: Contains the initial version of this document for the call on October 03, 2011
Apurva Mody BAESystems X X
R1: Contains the minutes from the call on October 10, 2011
R2: Contains the minutes from the call on October 17, 2011
Jerry Kalke
CRC
CBS
X
X
X
X
X
X
X
X
2. October 03, 2011
1) Record Attendance:
Meeting started at 20:09 ET and the attendance was noted ( 4 people on the call).
2) Ask if everyone is familiar with the IEEE patent policy: http://standards.ieee.org/board/pat/pat-slideset.pdf
Everyone on the call was familiar with the IEEE patent policy.
3) Approve the agenda: a.
Discuss development of wranDevMib group in 22-11/107r1 b.
Discuss IETF PAWS requirements
The agenda was approved as presented.
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
4) contributing individual(s) or organization(s). The material in this document is subject to change in form and content after
Approval of the minutes of the previous telecon
There were no minutes to approve.
5)
Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution,
Discussion on topics assigned to the working group participants
Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit
A) Discuss Development of wranDevMib group in 22-11/107r1
R Reddy: went on to describe MIB work, gave overview of some of the variable types and structure.
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
A Mody: remove reference to postal address
A Mody: Consider having a trap control/traps for database service.
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 <
R Reddy: Will finish wranIfCpeMib, then move on to the database MIB group. Database Service have questions, contact the IEEE Patent Committee Administrator at < patcom@ieee.org
> .
B) Discuss IETF PAWS requirements:
Submission page 1 Ranga Reddy, Self

October 2011 doc.: IEEE 802.22-10/0038r02
A Mody: PAWS requirements document is empty. PAWS has our primitives, but no concept of our conops. dot11AF has provided this. Our system is completely different from dot11af
G Chouinard: PAWS has our USE case, but has not developed them into requirements. G
Chouinard then reviewed the submission he discussed in Ottawa last week.
R Reddy: Does the .22 diagram need to air interface specific? Do we need to consider FDD?
G Chouinard: The basic operation of the protocol between BS and database service doesn't change if the air interface is FDD-based. We can consider FDD later.
R Reddy: Do we have a time table from PAWS?
A Mody: Not yet, takes action to keep in contact with IETF PAWS workgroup.
A Mody: We don't have specification of the spectral mask specification in database primitives.
We need to ad this.
G Chouinard: We didn't need this because we planned to meet spectral mask in every domain. We can.
A Mody: Also want to make updates to Annex A with regard to specifying the spectral mask per domain.
R Reddy/G Chouinard: Doing so may not be in scope. MIB/ASN.1, updates to clause 10 primitives, and development of non-clause 10 primitives are in scope
G Chouinard: note that some of this (regarding providing spectral mask data as input) is a moving target, so we have to be cautious moving forward. Displayed Ofcom's thoughts on database access.
6) Any other business
The meeting was adjourned at 22:02 ET .
3. October 10, 2011
1) Record Attendance:
Meeting started at 20:09 ET and the attendance was noted (4 people on the call).
2) Ask if everyone is familiar with the IEEE patent policy: http://standards.ieee.org/board/pat/pat-slideset.pdf
Everyone on the call was familiar with the IEEE patent policy.
3) Approve the agenda: a.
Discuss development of wranIfCpeMib group in 22-11/107r2 b.
IETF PAWS requirements
The agenda was approved as presented.
4) Approval of the minutes of the previous telecon: a.
DCN 22-11/122r0: https://mentor.ieee.org/802.22/dcn/11/22-11-0122-00-0mib-tga-conference-call-minutesseptember-december.doc
The minutes were approved.
5) Discussion on topics assigned to the working group participants
Submission page 2 Ranga Reddy, Self

October 2011 doc.: IEEE 802.22-10/0038r02
A) Discuss Development of wranIfCpeMib group in 22-11/107r2
R Reddy: Started reviewing group with wranIfCpeConfiguration table. Some items may not be needed. Specifically, wranIfCpeUsMapProcTime and wranIfCpeRangCmdProcTime.
G Chouinard: For wranIfCpeUsMapProcTime, DSMap tells when US subframe starts, so this item is not necessary. For wranIfCpeRangCmdProcTime, CPE has length of DS subframe to execute command. BS could schedule a CPE's RNG-CMD burst earlier if a CPE needed more time. to execute
G Chouinard: Need to update range of EIRP threshold to +36dBm. There are two ranges for
EIRP. On pg 55 (of 802.22-2011) EIRP per subcarrier, on pg 83 max transmit EIPR over all subchannels. Should consider having traps for both EIRP "values".
R Reddy: The wranIfCpeRangCmdProcTime was a holdover from 802.16. It could used to give
CPE more time to process RNG-CMD, but is not needed. Recommendation is to remove it, for the reason G Chouinard pointed out.
R Reddy: Will finish wranIfCpeMib, then move on to the database MIB group. Database Service
MIB group needs to get done, and I will add the database service traps/trap control at that time.
B) IETF PAWS :
A Mody: Was not able to follow up with Gabor.
G Chouinard: We still have to wait until end of October 2011 for items from PAWS.
6) Any other business
A) Starting putting revision/maintenance/corrigendum PAR
R Reddy: There are several items already in wranIfCpeMib that requires updates to the based standard. The PAR process should be started as soon as possible.
A Mody: We can't submit a revision/maintenance until TGa is done. We can at best target submitting one in March 2012, if the WG decides to.
G Chouinard: R Reddy and I will update our current lists for changes that are required, and send to A Mody. Working group will then decide what will be necessary.
The meeting was adjourned at 22:00 ET .
4. October 17, 2011
1) Record Attendance:
Meeting started at 21:09 ET and the attendance was noted (x people on the call).
2) Ask if everyone is familiar with the IEEE patent policy: http://standards.ieee.org/board/pat/pat-slideset.pdf
Everyone on the call was familiar with the IEEE patent policy.
3) Approve the agenda: a.
Discuss addition of EIRP per Subcarrier and Max EIRP alarms as discussed from 10/10 telecon b.
Start developing response to IETF PAWS requirements
The agenda was approved as presented.
Submission page 3 Ranga Reddy, Self

October 2011 doc.: IEEE 802.22-10/0038r02
4) Approval of the minutes of the previous telecon: a.
DCN 22-11/122r1: https://mentor.ieee.org/802.22/dcn/11/22-11-0122-01-0mib-tga-conference-call-minutesseptember-december.doc
The minutes were approved.
5) Discussion on topics assigned to the working group participants
A) Discuss addition of EIRP per Subcarrier and Max EIRP alarms as discussed from 10/10 telecon
R Reddy: No one had issue with the updates for traps for EIRP per subcarrier or Max EIRP over
60 subchannels.
B) Start building response to PAWS requirements:
A Mody: Displayed email listing some discussion on the requirements. We will create a new document to contain our discussion of and proposals to changes.
R Reddy: Begin discussion with Data Model Requirements. D.1 is met by the enlistment request primitive 10.7.1.3, it's a 1 byte value that encodes the height in AGL.
G Chouinard: Do we specify AGL and HAAT?
A Mody: Don't we need both?
G Chouinard: Our primitive can give AGL, but with lat/lon can be used to derive absolute height above sea-level. HAAT is also necessary, but the database is better positioned to know, calculate this info as necessary.
J Kalke: HAAT calculations are complex, what radius are we expecting?
G Chouinard: ~30km. Operators shouldn't be burdened.
A Mody: For D.1, how does antenna gain pattern encoded?
R Reddy: It's described in 10.7.1.3 primitive.
R Reddy: Do we expect the ID in D.2 to be just device ID and serial #?
G Chouinard: They need both, they should also get device type (see 10.7.1.5)
A Mody: How should we add in the "RF mask" consideration?
G Chouinard: consider an indices to a defined table that contains RF mask defined on a per domain.
R Reddy: For D.3, Do they really need the accurarcy? we control access control and can deny registration if we're not confident of a devices location?
G Chouinard: we have location info, in NEMA
G Chouinard: For D.4/D.5 we should clarify if returned channel list returns the EIRP per channel
G Chouinard: For D.6, 802.22 will generate an intersection of device locations and use that to build a query. Our approach is to query on a device basis
Submission page 4 Ranga Reddy, Self

October 2011 doc.: IEEE 802.22-10/0038r02
G Chouinard: D.7, not necessary for .22. Devices will be fixed or Mode II and will be geolocated.
6) Any other business
A) Will continue discussion during TG2 call on 10/19/2011
The meeting was adjourned at 22:50 ET .
Submission page 5 Ranga Reddy, Self