October 2011doc.: IEEE 802.22-11/0127r0
IEEE P802.22
Wireless RANs
Date: 2011-10-18
Author(s):
Name / Company / Address / Phone / email
Charles W. Einolf, Jr. / NABA / 3007 Argentina Place
Mitchellville, MD 20716 USA / +1-301-806-1544 /
Victor Tawil / MSTV / 4100 Wisconsin Avenue
Washington, DC 20016 / +1-202-966-1956 /
Requirements
D. Data Model Requirements:
D.1: The Data Model MUST support specifying the
- Antenna Parameters
- Height Parameters (From device to the database)
- mandatory AGL in meters: Unsigned INT, 1 Byte (0 – 255 m)
- Our assumption is that the database will compute the HAAT in meters from the AGL and (lat, long)
- Gain Parameters (From the device to the database)
- Antenna directionality information of the device in dB: relative to the main lobe maximum gain for every 5 degree azimuth clockwise starting from the direction of the maximum antenna gain expressed in unit of 0.25 dB over the range –63.75 dB (encoded 0x00) to 0 dB (0xFF). Character String 72 bytes
- Antenna azimuthInteger2 bytesAntenna azimuth in degrees, clockwise from true North.
- RF Mask Parameters (From the device to the database)
- Regulatory Domain (3 ASCII Letters), Device Type (Regulatory Class e. g. Fixed, Personal Portable, Mobile etc) (INT), Mask Number Index (Long INT) (where Mask Number Index corresponds to a particular RF Mask of an equipment that is stored in the database and that has passed the regulatory certification)
D.2: The data model MUST support specifying an ID of the subject. This ID would be the ID of the device used to be certified by a regulatory
body for a regulatory domain
Name / Type / Length / DescriptionDevice Type / Integer / 1 byte / The value identifies the type of device at the geo-location registering
0x00 = Fixed base station
0x01 = Fixed CPE
0x02 = Personal/portable mode
0x03-0xFF = Reserved
Device-ID Length / Integer / 2 bytes / Length of Device-ID field (# of characters)
Device-ID / Character String / Variable / In US, this is FCC-ID
Serial Number Length / Integer / 2 bytes / Length of Serial Number field (# of characters)
Serial Number / Character String / Variable
D.3: The Data Model MUST support specifying the location of the subject
and accuracy of location determination
Name / Type / Length / DescriptionLocation Data String Length / Integer / 2 bytes / Length of Location Data String field (# of characters)
Location Data String / Character String / NMEA 0183 Character String / The value identifies the location of the device (latitude, longitude).20F[1]
Timestamp Length / Integer / 2 bytes / Length of Timestamp field (# of characters)
Timestamp / Character String / NMEA 0183 $ZDA string / Timestamp of the present request at time of transmission and as encoded in the $ZDA substring of the NMEA 0183 string.
NMEA GPGGA String is the subset of the NMEA 0183
D.4: The Data Model MUST support specifying a list of available channel
list and time constrains for the channel list availability.
Name / Type / Length / DescriptionDevice-ID Length / Integer / 2 bytes / Length of Device-ID field (# of characters)
Device- ID / Character String / Variable / In US, this is FCC-ID
Serial Number Length / Integer / 2 bytes / Length of Serial Number field (# of characters)
Serial number / Character String / Variable
Number of Channels Available / Integer / 1 byte
{ If( Number of Channels Available > 0) / If the number of channels is equal to 0, this means that the device cannot operate.
For (i=1; i≤ Number of Channels Available; i++) {
Channel_Number
Max_Allowed_EIRP (dBm)
Availability schedule
} / Vector of 2xN bytes and a number of pairs of NMEA 0183 $ZDA strings / Variable / List of available channel numbers and corresponding maximum allowed EIRP expressed in dBm over the range –64 dBm (encoded 0x00) to +63.5 dBm (encoded 0xFF) as well as the availability schedule (start and stop date/time) for each channel in Universal date and time system.
}
Status Message / Character String / Variable / Various status messages coming from the database service (e.g., unapproved device flag)
Timestamp Length / Integer / 2 bytes / Length of Timestamp field (# of characters)
Timestamp / Character String / NMEA 0183 $ZDA string / Copied from the timestamp in the M-DB-AVAILABLE-CHANNEL-REQUEST.
D.5: The Data Model MUST support specifying the maximum output power of
the subject.
Please see above. We need the Maximum EIRP.
D.6: The Data Model MUST support specifying channel availability information for multiple locations.
802.22 BS shall act as a proxy and query the database for each device. If a query is to be grouped or made in a batch mode, all the information related to each device shall be provided to the BS (i. e. the database is not to perform the intersection for all these devices and locations).
D.7: The Data Model MUST support specifying channel availability
information for an area around a specified location.
Does not apply to the 802.22
P. Protocol Requirements:
P.1: The protocol MUST provide a mechanism for the subject to discover
the WS Database it has to use at a given location.
P.2: The protocol MUST support regulatory domain discovery.
P.3: The protocol between the master device and the WS Database MUST
support pushing updates in channel availability changes to subjects
P.4: The protocol between the master device and the WS Database MUST
support mutual authentication and authorization.
P.5: The protocol between the master device and the WS Database MUST
support integrity and confidentiality protection.
P.6: The protocol MUST support both username/password and digital
certificates based authentication.
O. Operational Requirements:
O.1: A master device MUST query the WS Database for the available
channels as often as required by the regulation (eg, FCC requires once
per day) to verify that the operating channels continue to remain available.
O.2: A master device MUST determine its location with the accuracy
required by the regulation (eg, FCC requires +/- 100m) before placing a
query to the DB
O.3: A master device which changes its location during its operation,
MUST query the WS Database for available operating channels each time
it moves more than the distance specified by the regulation (eg FCC specifies 100m) from the location it previously made the query from.
O.4: The WS Database MUST provide the available channel list when
requested and MAY also provide time constraints for the channel list
and maximum output power to the master device.
O.5: A master device MUST query the WS Database and include the FCC ID
of the slave device in the query before allowing the slave device to
use the available channel.
O.6: A master device MUST be capable to validate the digital
certificate of the WS Database.
O.7: A master device MUST be capable to check the validity of the WS
Database certificate and whether it has been revoked or not.
Submissionpage 1Apurva N. Mody, BAE Systems
[1] See footnote 3.