﻿<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
<!ENTITY RFC5545 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5545.xml'>
<!ENTITY RFC5139 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5139.xml'>
<!ENTITY RFC5491 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.5491.xml'>
<!ENTITY RFC2426 PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2426.xml'>
<!ENTITY I-D.ietf-paws-problem-stmt-usecases-rqmts PUBLIC ''
'http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-paws-problem-stmt-usecases-rqmts.xml'>


]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="yes" ?>
<rfc ipr="trust200902" category="exp" docName="draft-caufield-paws-protocol-for-tvws-01.txt">
   <front>
      <title abbrev="Protocol to query WS DB">Protocol to query a
White Space Database</title>
      <author initials="J" surname="Caufield" fullname="Jesse Caufield" >
         <organization>Key Bridge</organization>
         <address>
                <postal>
                    <street>1600 Tysons Blvd, Suite 450</street>
                    <city>McLean</city>
                    <code>VA 22102</code>
                    <country>USA</country>
                </postal>
                <email>jesse.caulfield@keybridgeglobal.com</email>
            </address>
      </author>


      <date year="2011"/>
      <area>Applications</area>
      <workgroup>PAWS</workgroup>
      <keyword>Internet-Draft</keyword>
      <keyword>TV White Space</keyword>
      <keyword>Cognitive Radio</keyword>
<abstract>
  <t>
    Regulatory entities in many countries are making spectrum previously
    used by television stations available for secondary use as a result of
    the switch from analog to digital. The spectrum in such cases is still
    owned by the primary user to whom it is licensed. However parts of the
    spectrum may be unused at a given location or time and hence can be
    made available for secondary use. In order to use such spectrum a
    device has to query a database in order to obtain a list of available
    channels or spectrum at a given location and time. This document
    specifies protocol elements that can be used to query a white space
    database and obtain a response by a device.
  </t>
</abstract>
   </front>

   <middle>
      <!-- ================================================================== -->

      <section anchor="introduction" title="Introduction">
	<t>
	  Regulatory entities in many countries are making spectrum previously
	  used by television stations available for secondary use as a result of
	  the switch from analog to digital. The spectrum in such cases is still
	  owned by the primary user to whom it is licensed. However parts of the
	  spectrum may be unused at a given location or time and hence can be
	  made available for secondary use. In order to use such spectrum a
	  device has to query a database in order to obtain a list of available
	  channels or spectrum at a given location and time. This document
	  specifies protocol elements that can be used to query a white space
	  database and obtain a response by a device.
	</t>
	<t>
	  The problem statement, use cases and requirements for the use of
	  white space spectrum and the associated protocol is captured in the
	  document: <xref target="I-D.ietf-paws-problem-stmt-usecases-rqmts"/>.
	</t>

      </section>
<!-- introduction -->

<!-- ================================================================== -->

      <section anchor="terms" title="Terminology and Abbreviations">
         <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
            NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as
            described in <xref target="RFC2119"/>. </t>
<t>
  This document relies on the terminology specified in <xref
target="I-D.ietf-paws-problem-stmt-usecases-rqmts"/>.
</t>

 </section>
     <!-- terminology -->

      <!-- ================================================================== -->

      <section title="Background">
         <t>
           Spectrum is a scarce resource and hence it is essential
           that technology provide a means to use this resource in an
           optimal manner. Spectrum has been generally licensed or
           granted or reserved for specific use by regulatory bodies
           and governments. Some spectrum such as the ISM band has
           been made publicly available for use without any licenses
           but still with a set of regulations. In many cases spectrum
           that has been licensed to an entity or reserved is either
           not utilized or under utilized. As the demand for services
           over wireless medium continues to grow the need for
           additional spectrum is increasing. Cognitive radio and
           white space technology is a solution that allows the use of
           spectrum by a secondary user at a given location if the
           primary user is either not using the spectrum at a given
           time and without causing interference to the primary
           user. Regualtions to this effect have been specified by the
           FCC in the US and other regulatory bodies in many other
           countries are also studying similar approaches for parts of
           the spectrum.
         </t>
	 <t>
	   One of the approaches to determining if spectrum is
	   available at a given location and time is to query a
	   centralized database and obtain information about what
	   channels or spectrum can be used. There may exist multiple
	   databases from which such information can be obtained. A
	   standardized query/response mechanism is in the scope of
	   the PAWS working group. This document proposes a data
	   format for the query and response aspects of the protocol.
	 </t>

      </section>


      <!-- ================================================================== -->

      <section title="Problem Statement">
	<t>
          The query/response protocol to obtain information about
          available channels or spectrum can be specified using
          various means. LDAP is an example of a protocol that can be
          used for this purpose. However one of the objectives of this
          protocol is to ensure that it is globally applicable and can
          be adapted for use in various regulatory environments. The
          elements of the query and response can vary depending on the
          country or region where a device is making a query to a
          database. As a result of this objective, flexibility of the
          protocol in terms of the attributes and parameters carried
          in the query and response are quite important.
	</t>
      </section>

      <section title="Protocol approach">
	<t>
	  This document does not specify the complete protocol
	  itself. The protocol can be split into three parts:
	</t>
	<t>
	  <list style="numbers">
            <t>The data model</t>
	    <t>The transport protocol</t>
	    <t>The security solution</t>
	  </list>
	</t>
	<t>
	  A data model for the query/response protocol is proposed in
	  this document. A hierarchical object model approach is
	  used for defining the query/response and its attributes. The
	  figure below is a high-level view of how the data model is
	  structured:
	</t>
	<t>
	  <figure align="center" anchor="object_model" title="Data Model">
	    <artwork align="center"><![CDATA[


	                   -------------
	    		   |WS Protocol|
			   -------------
				 |
				 |
		 -------------------------------------
	    	 |                                   |
	    ---------                            ------------
	    |wsQuery|  				 |wsResponse|
	    --------- 				 ------------
		|      	       	       	       	       |
	    ----------				  ----------
	    |Element1| ...5, 6, 7                 |Elementx| ... y,z
	    ----------	  .  . 	.	       	  ----------	 . .
	       	|	  .  .	.      	       	       |       	 . .
       	    ------------  .  .	.      	       	  ------------	 . .
	    |Attributes| o o o o o     	       	  |Attributes| o o o
	    ------------	  		  ------------

           ]]></artwork>
	  </figure>

	</t>
      </section>

	<section title="Data Model details">
	  <t>
	    The data model includes two main objects, the wsQuery and
	    wsResponse objects. Each of these objects contain a list
	    of elements. The elements are further comprised of
	    attributes. The wsQuery object is sent by a WS Master
	    device to a database and the database responds with a
	    wsResponse object. The actual message and header in which
	    this object is carried is not specified here and is
	    expected to be specified elsewhere. Neither does this
	    document specify how the device discovers the database or
	    how the object is transported or secured.
	  </t>
	  <section title="White Space Query Object">
	    <t>
	      The whitespaceQuery object is a data object carried in a
	      request message that any white space client (e.g. a
	      white space device, software application, coexistence
	      manager, etc.) may use to request information from a
	      white space database, as part of a Rules-compliant data
	      transaction. 
	    </t>
	    <section title="Query object definition">
	      <t>
	      <figure align="center" title="whitespaceQuery Object">
		<artwork align="center"><![CDATA[
<xs:complexType name="whitespaceQuery">
		<xs:all>
			<xs:element name="station" 	type="station"/>
			<xs:element name="schedule" 	type="schedule" minOccurs="0"/>
			<xs:element name="extension" 	type="xs:string" minOccurs="0"/>
		</xs:all>
		<xs:attribute name="uuid" 		type="xs:string" use="required"/>
		<xs:attribute name="protocolVersion" 	type="xs:float" use="required"/>
		<xs:attribute name="messageType" 	type="xs:string" use="required"/>
</xs:complexType>

               ]]></artwork>
	      </figure>
	      </t>
	    </section>
	  </section> <!-- WSQuery -->

	  <section title="White Space Response Object">
  <t>
    A whitespaceResponse object is a generalized message response
    structure that any white space administrator (e.g. a white space
    database implementation) may use to communicate white space information
    in a Rules-compliant data transaction. 
  </t>
  <t>
    The whitespaceResponse object structure is intended to accommodate
    various responses to information queries from different white space
    client such as, for example, white space devices (for transmission),
    management systems (not for transmission) and consumers (not for
    transmission). 
  </t>

  <section title='Response Object Definition'>
    <t>
      <figure align="center" title="whitespaceResponse Object">
	<artwork align="center"><![CDATA[

<xs:complexType name="whitespaceResponse">
		<xs:sequence>
			<xs:element name="station" 	type="station"/>
			<xs:element name="whitespaceFrequencyList" type="whitespaceFrequency" 
				    nillable="true" minOccurs="1" maxOccurs="unbounded"/>
			<xs:element name="extension" 	type="xs:string" minOccurs="0"/>
		</xs:sequence>
		<xs:attribute name="uuid" 	type="xs:string" use="required"/>
		<xs:attribute name="effectiveDate" 	type="xs:dateTime" use="required"/>
		<xs:attribute name="expirationDate" 	type="xs:dateTime" use="required"/>
		<xs:attribute name="messageType" 	type="xs:string" use="required"/>
		<xs:attribute name="protocolVersion" 	type="xs:float" use="required"/>
		<xs:attribute name="statusIndicator" 	type="xs:int" use="required"/>
		<xs:attribute name="timeStamp" 	type="xs:dateTime" use="required"/>
</xs:complexType>

       ]]></artwork>
      </figure>
    </t>
    
    </section>
  </section> <!-- WSResponse -->

  <section title="Elements of the Query and Response objects">
    <t>
      The whitespaceQuery and whitespaceResponse objects include
      multiple elements. Some of the elements are common across the
      query and response objects. The following sections define these
      elements. 
    </t>
    <section title="Station element">
      <t>
	A WSIF station object contains information about the inquiring
	station including antenna, location, transmitter details,
	etc. 
      </t>
      <t>
	<figure align="center" title="Station Element">
	<artwork align="center"><![CDATA[

<xs:complexType name="station">
		<xs:sequence>
			<xs:element name="channelList"	type="channel" maxOccurs="unbounded"/>
			<xs:element name="contactList"	type="contact" maxOccurs="unbounded"/>
			<xs:element name="location"	type="location"/>
			<xs:element name="antenna"	type="antenna" minOccurs="0"/>
			<xs:element name="schedule"	type="schedule" minOccurs="0"/>
			<xs:element name="stationRxList"	
				    type="station" minOccurs="0" maxOccurs="unbounded"/>
			<xs:element name="transmitterList"	
				    type="transmitter" minOccurs="0" maxOccurs="unbounded"/>
			<xs:element name="extension"	
				    type="xs:string" minOccurs="0"/>
			<xs:element name="x-licenseInformationList"
			
				    type="licenseInformation" 
				    minOccurs="0" maxOccurs="unbounded"/>
		</xs:sequence>
		<xs:attribute name="uuid"	type="xs:string" use="required"/>
		<xs:attribute name="name"	type="xs:string" use="required"/>
		<xs:attribute name="stationClass"	type="xs:string" use="required"/>
		<xs:attribute name="description"	type="xs:string"/>
		<xs:attribute name="stationType"	type="xs:string"/>
	</xs:complexType>
       ]]></artwork>
      </figure>

	</t>
    </section> <!--Station-->
    <section title="Schedule element ">
      <t>
	Type: Schedule
      </t>
      <t>
	A schedule object is used by white space devices to request
	temporary spectrum access (i.e. less than 24 hours). The
	schedule element is intended to enable the recording,
	persistence and distribution of standardized
	iCalendar-compatible messages. The format of the Schedule
	object is defined in <xref target="RFC5545"/>. 
      </t>
    </section><!--Schedule -->
    <section title="ChannelList element">
      <t>
	Type: Channel
      </t>
      <t>
	A list of channels (i.e. frequency ranges) that are occupied
	by the transmitter(s) at this station.
      </t>
    </section><!--ChannelList-->

    <section title="ContactList element">
      <t>
	Type: Contact
      </t>
      <t>
	A list of contacts associated with this station. For example, a
	facility or on-site technical manager, administrator, and operational
	contacts may be identified. 
      </t>
    </section><!--ContactList-->
    <section title="Location element">
      <t>
	This element describes the station's physical and geographic
	location.  
      </t>
            <t>
	<figure align="center" title="Location Element">
	<artwork align="center"><![CDATA[
<xs:complexType name="location">
		<xs:all>
			<xs:element name="address" 	type="address" minOccurs="0"/>
			<xs:element name="coordinate" 	type="coordinate" minOccurs="0"/>
		</xs:all>
		<xs:attribute name="uuid" 	type="xs:string" use="required"/>
		<xs:attribute name="name" 	type="xs:string" use="required"/>
		<xs:attribute name="locationType" 	type="xs:string"/>
		<xs:attribute name="x-geocode" 	type="xs:string"/>
		<xs:attribute name="x-haat" 	type="xs:float"/>
		<xs:attribute name="x-timeZone" 	type="xs:string"/>
</xs:complexType>
       ]]></artwork>
      </figure>
      </t>
    </section><!--LocationElement-->
    
    <section title="Antenna element">
      <t>
	A description of this station’s (transmit or receive) antenna,
	including the required antenna parameters like pointing and
	elevation information plus the radiation pattern. 
      </t>
            <t>
	<figure align="center" title="Antenna Element">
	<artwork align="center"><![CDATA[
<xs:complexType name="antenna">
		<xs:sequence>
			<xs:element name="radiationPattern" 	type="radiationPattern"/>
		</xs:sequence>
		<xs:attribute name="directional" 		type="xs:boolean" use="required"/>
		<xs:attribute name="rotation" 			type="xs:float" use="required"/>
		<xs:attribute name="heightAboveGround" 		type="xs:float" use="required"/>
		<xs:attribute name="manufacturer" 		type="xs:string"/>
		<xs:attribute name="model" 			type="xs:string"/>
		<xs:attribute name="x-elevationModel" 		type="xs:string"/>
		<xs:attribute name="x-govtAntennaId" 		type="xs:int"/>
		<xs:attribute name="x-haat" 			type="xs:float"/>
		<xs:attribute name="x-rcAmsl" 			type="xs:float"/>
	</xs:complexType>
       ]]></artwork>
      </figure>
      </t>
    </section><!--AntennaElement -->

    <section title="StationRxList element">
      <t>
	Type: Station
      </t>
      <t>
	For wireless services that include multiple stations, and
	especially for wireless services with multiple TXRX stations,
	each receiving station may indicate its respective upstream
	transmitting stations by adding that transmitting station to
	this receiving stationís rxStationList element. Example uses
	of this element include Television translator stations, MVPD
	receive sites, etc. 
      </t>
    </section><!--StationRxList-->

    <section title="TransmitterList element">
      <t>
	Type: Transmitter
      </t>
      <t>
	A station may support multiple transmitters operating within
	the same geographic area and on the same schedule.  For
	example, several wireless microphones may operate
	simultaneously within the geographic contour defined within
	this stationís location element. If the stationType attribute
	indicates this station is receive-only then this element
	SHOULD be null.  
      </t>
    </section><!--TransmitterList-->

    <section title="Address element">
      <t>
	Type: Address
      </t>
      <t>
	This element specifies the civic location of the station. The
	structure of this element is described in
	<xref target="RFC5139"/>.  
      </t>
    </section><!--Address Element-->

    <section title="Coordinate element">
      <t>
	Type: Coordinate
      </t>
      <t>
	this element specifies the geolocation of the station. The
	structure of this element is described in <xref target="RFC5491"/>.
      </t>
    </section><!--Coordinate -->

    <section title="RadiationPattern element">
      <t>
	Type: RadiationPattern
      </t>
      <t>
	A radiation pattern representing the directional (azimuth)
	dependence of the strength of the radio signal from the
	antenna. The radiationPattern represents the directional
	(azimuth) dependence of the strength of the radio signal from
	the antenna. 
      </t>
      <t>
	A WKT MULTIPOINT SFA Geometry implementation. The azimuthal field
	values are encoded as a well known text (WKT) MULTIPOINT object with
	[azimuth, radial value] pairs encoded according to the format
	POINT(x,y) = POINT(azimuth, field_value).  
      </t>
            <t>
	<figure align="center" title="RadiationPattern Element">
	<artwork align="center"><![CDATA[
<xs:complexType name="radiationPattern">
		<xs:sequence>
			<xs:element name="radiationPattern" 	type="xs:string"/>
		</xs:sequence>
		<xs:attribute name="source" 			type="xs:string" use="required"/>
		<xs:attribute name="description" 		type="xs:string"/>
		<xs:attribute name="x-interpolated" 		type="xs:boolean"/>
	</xs:complexType>
       ]]></artwork>
      </figure>
      </t>
    </section><!--RadiationPattern-->

    <section title="Contact Element ">
      <t>
	The contact represents a generalized container for individual
	(person) and company (organization) contact information. The
	structure of this element is defined in <xref target="RFC2426"/>. 
      </t>
    </section><!--Contact-->

    <section title="Extension element">
      <t>
	Type: xs:string
      </t>
      <t>
	A URL-ENCODED string containing key/value pairs that
	requesting devices may implement and administrators may
	support at their discretion to provide supplementary
	information or to otherwise extend this object. 
      </t>
    </section><!--Extension-->

    <section title="WhiteSpaceFrequencyList element">
      <t>
	Contains a complete and canonical list of available and valid
	white space frequencies that is appropriate for the inquiring
	message's criterion. For white space devices, the
	whitespaceFrequencyList element represents all channels
	available for unlicensed operation at the inquiring deviceís
	location or indicated geographic area and according to the
	schedule in this element.Contains one or more occurencies of
	WhiteSpaceFrequency elements.  
      </t>
    </section><!--WhitespaceFrequencyList -->

    <section title="WhiteSpaceFrequency element">
      <t>
	<figure align="center" title="WhiteSpaceFrequency Element">
	<artwork align="center"><![CDATA[
<xs:complexType name="whitespaceFrequency">
		<xs:all>
			<xs:element name="channel" 	type="channel"/>
			<xs:element name="location" 	type="location"/>
			<xs:element name="schedule" 	type="schedule"/>
			<xs:element name="extension" 	type="xs:string" minOccurs="0"/>
		</xs:all>
		<xs:attribute name="uuid" 	type="xs:string" use="required"/>
		<xs:attribute name="maxEirp" 	type="xs:float" use="required"/>
</xs:complexType>

       ]]></artwork>
      </figure>

      </t>
    </section><!-- WhitespaceFrequency -->
    
    <section title="Channel Element">
      <t>
	A channel describes a fully qualified and canonical frequency range. 
Channel object definitions support positive definitions of colloquial
	channel identifiers (e.g. TV channel 24) through
	identification of the authorizing regulatory definition and
	the TV channelís frequency range. 
      </t>
      <t>
	<figure align="center" title="Channel Element">
	  <artwork align="center"><![CDATA[
<xs:complexType name="channel">
		<xs:attribute name="allocation" 	type="xs:string" use="required"/>
		<xs:attribute name="channel" 	type="xs:float" use="required"/>
		<xs:attribute name="minFreq" 	type="xs:double" use="required"/>
		<xs:attribute name="maxFreq" 	type="xs:double" use="required"/>
</xs:complexType>

]]></artwork>
	</figure>
      </t>
    </section><!-- Channel element -->

    <section title="Transmitter Element">
      <t>
	The transmitter object provides an extensible software
	template to contain and exchange required and optional but
	otherwise useful transmitter information.  
      </t>
      <t>
	A transmitter provides an object template for common
	device-related attributes and may be optionally used directly
	or, more likely, may be extended by other, more specific
	transmitter descriptions that fully describe a certain type
	wireless device. For this reason all transmitter attributes
	and elements are defined as optional by default. Attribute and
	element validity is expected to be defined in
	transmitter-derived objects. The transmitter is designed to
	support, through extension, the communication of required and
	optional but otherwise useful information about licensed and
	unlicensed wireless devices including transmitters, receivers
	and transceivers.  
      </t>
      <t>
	<figure align="center" title="Transmitter Element">
	<artwork align="center"><![CDATA[
<xs:complexType name="transmitter">
		<xs:sequence>
			<xs:element name="channel"	type="channel" minOccurs="0"/>
			<xs:element name="extension"	type="xs:string" minOccurs="0"/>
		</xs:sequence>
		<xs:attribute name="frequency"	type="xs:double"/>
		<xs:attribute name="deviceId"	type="xs:string"/>
		<xs:attribute name="deviceSn"	type="xs:string"/>
		<xs:attribute name="description"	type="xs:string"/>
		<xs:attribute name="ea"	type="xs:string"/>
		<xs:attribute name="erp"	type="xs:float"/>
		<xs:attribute name="isDigital"	type="xs:boolean"/>
		<xs:attribute name="manufacturer"	type="xs:string"/>
		<xs:attribute name="model"	type="xs:string"/>
		<xs:attribute name="name"	type="xs:string"/>
		<xs:attribute name="x-digitalModRate"	type="xs:double"/>
		<xs:attribute name="x-digitalModType"	type="xs:string"/>
		<xs:attribute name="x-emissionCode"	type="xs:string"/>
		<xs:attribute name="x-equipmentClass"	type="xs:string"/>
		<xs:attribute name="x-equipmentRuleNum"	type="xs:string"/>
		<xs:attribute name="x-maxErp"	type="xs:float"/>
		<xs:attribute name="x-txWidth"	type="xs:float"/>
	</xs:complexType>
       ]]></artwork>
      </figure>
      </t>
    </section> <!-- Transmitter -->

  </section><!-- Elements -->
  
  <section title="Attributes definition">
    <t>
      This section defines the attributes which are included in the
      various elements of the whitespacequery or whitespaceresponse
      objects. 
    </t>

      <t>
	<t>Channel attribute</t>
	<list style="empty">
	  <t>Type: xs: boolean </t>
	  <t>Description: An indicator for whether the
	  radiationPattern element of this object contains
	  interpolated values. 
	  </t>
	</list>
      </t>

      <t>
	<t>Source attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: The originating source of the data
	    represented in the radiationPattern element. An example
	    value for this attribute is ìus.fcc.cdbsi. 
	  </t>
	</list>
      </t>

      <t>
	<t>Directional attribute</t>
	<list style="empty">
	  <t>Type: xs:boolean </t>
	  <t>Descrition: Indicates whether the antenna is directional
	  (true) or non-directional (false). 
	  </t>
	</list>
      </t>

      <t>
	<t>Rotation attribute </t>
	<list style="empty">
	  <t>Type: xs:float </t>
	  <t>Description: Indicates the offset in degrees azimuth [0,
	  360] from true North that the antenna radiation pattern
	  should be rotated. 
	  </t>
	</list>
      </t>

      <t>
	<t>HeightAboveGround attribute </t>
	<list style="empty">
	  <t>Type: xs:float </t>
	  <t>Description: The antenna radiation center height above
	  ground level. 
	  </t>
	</list>
      </t>

      <t>
	<t>Manufacturer attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: The antenna manufacturer
	  </t>
	</list>
      </t>

      <t>
	<t>x-elevantModel attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: The digital elevation model used to
	  calculate this antenna objectís HAAT (x-haat) and rcAMSL
	  (x-rcAmsl) values. 
	  </t>
	</list>
      </t>



      <t>
	<t>x-govtAntennaId attribute </t>
	<list style="empty">
	  <t>Type: xs:int </t>
	  <t>Description: A reference to the antenna ID record within FCC CDBS
	  </t>
	</list>
      </t>

      <t>
	<t>x-haat attribute </t>
	<list style="empty">
	  <t>Type: xs:float </t>
	  <t>Description: The antenna height above average terrain
	  </t>
	</list>
      </t>

      <t>
	<t>x-rcAmsl attribute </t>
	<list style="empty">
	  <t>Type: xs:float </t>
	  <t>Description: The antenna radiation center above mean sea level
	  </t>
	</list>
      </t>

      <t>
	<t>Frequency attribute </t>
	<list style="empty">
	  <t>Type: xs:double </t>
	  <t>Description: If a specific frequency has been assigned to
	  this transmitter that information may be recorded here in
	  MHz. If only the channel is provided then the
	  assignedFrequency value is set to the center frequency of
	  this transmitterís channel. 
	  </t>
	</list>
      </t>

      <t>
	<t>deviceID attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: The transmitter device's Government provided
	  identifier. 
	  </t>
	</list>
      </t>

      <t>
	<t>deviceSn attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: the transmitting device's
	  manufacturer-provided serial number.
	  </t>
	</list>
      </t>

      <t>
	<t>ea attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: The Government equipment authorization
	  agency from which this device is authorized to operate and
	  which issued the device ID. 
	  </t>
	</list>
      </t>

      <t>
	<t>erp attribute </t>
	<list style="empty">
	  <t>Type: xs: float </t>
	  <t>Description: The transmitting deviceís current effective
	  radiated power (ERP), measured in dBw. 
	  </t>
	</list>
      </t>

      <t>
	<t>isDigital attribute </t>
	<list style="empty">
	  <t>Type: xs:boolean </t>
	  <t>Description: Indicates whether this transmitter is
	  sending a digital (TRUE) or analog (FALSE) carrier. 
	  </t>
	</list>
      </t>

      <t>
	<t>manufacturer attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: the device manufacturer company name
	  </t>
	</list>
      </t>

      <t>
	<t>Model attribute </t>
	<list style="empty">
	  <t>Type: xs:string </t>
	  <t>Description: the antenna product model
	  </t>
	</list>
      </t>

      <t>
	<t> </t>
	<list style="empty">
	  <t> </t>
	  <t>
	  </t>
	</list>
      </t>

      <t>
	<t> </t>
	<list style="empty">
	  <t> </t>
	  <t>
	  </t>
	</list>
      </t>


    <t>
      <t>allocation attribute</t>
      <list style='empty'>
        <t>Type: xs:string</t>
        <t>Description:A dot-delimited reverse domain encoded
          description of the frequency allocation defined according
          the following strategy:</t> 
        <t>[country].[regulator].[allocation].[band range]</t>
        <t>For example, the UHF-high block allocation of TV channels
          38 to 51 within the United States is identified as
          “us.fcc.broadcast.614-698”.</t> 
      </list>
    </t>
    
<!--     <t>categories attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/>, Internet -->
<!--           Calendaring and Scheduling Core Object Specification -->
<!--           (iCalendar).</t>  -->
<!--       </list> -->
<!--     </t> -->
    
    <t>channel attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:float</t>
        <t>Description: The colloquial channel number</t>
        <t>Note: A FLOAT number type is used to accommodate future
          sub-channelization. For the avoidance of doubt channel
          numbers ending in zero shall be interpreted to represent a
          whole channel. i.e. float value channel 38.0 is equivalent
          to integer-value channel 38.</t> 
      </list>
    </t>
    
<!--     <t>classification attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/> -->
<!-- 	</t>  -->
<!--       </list> -->
<!--     </t> -->
    
<!--     <t>created attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!-- 	<t>Type: xs:dateTime</t> -->
<!-- 	<t>Description: Excerpted from <xref target="RFC5545"/></t> -->
<!--       </list> -->
<!--     </t> -->
    
<!--     <t>description attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/></t> -->
<!--       </list> -->
<!--     </t> -->
    
<!--     <t>dtend attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:dateTime</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/>.</t> -->
<!--       </list> -->
<!--     </t> -->
    
<!--     <t>dtstart attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:dateTime</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/></t> -->
<!--       </list> -->
<!--     </t> -->
    
<!--     <t>duration attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/></t> -->
<!--       </list> -->
<!--     </t> -->
    
    <t>effectiveDate attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:dateTime</t>
        <t>Description: The date and time when this white space
          information should be considered effective. The value may be
          set in the future to accommodate frequencies that may become
          available at a later date or time.</t> 
      </list>
    </t>
    
    <t>expirationDate attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:dateTime</t>
        <t>Description: The date and time when this white space
          information expires.</t> 
      </list>
    </t>
    
    <t>locationType attribute</t>
    <t>
      <list style="empty">
	<t>Type: xs:string</t>
	<t>Description: A descriptor string used to classify
	  and organize locations. If the location is derived
	  from another database source, this attribute is a
	  dot-delimited string used to identify this location
	  type and its source. An example value for this
	  attribute is “us.fcc.cdbs.stationClass.CDT”.</t> 
      </list>
    </t>
    
    <t>maxEIRP attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:float</t>
        <t>Description: The maximum allowable equivalent
          isotripically radiated power (EIRP) that a white space
          device may transmit on the indicated channel. Provided in
          dBW.</t> 
      </list>
    </t>
    
    <t>maxFreq attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:double</t>
        <t>Description: The maximum (or end) frequency of the
          indicated channel in MHz.</t> 
      </list>
    </t>
    
    <t>messageType attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description: An enumerated message type. Allowed message types are:</t>
        <t>Message code: ws.messageType.TVBD.QUERY</t>
        <t>Description: The message is a certified client-initiated
          query for white space frequency information for the purposes
          of transmission. Examples of certified clients include
          FCC-certified white space devices and other devices
          authorized to operate within the band (e.g. wireless
          microphones, medical telemetry, PLMRS systems, etc.)</t> 
        <t>Message code: ws.messageType.TVBD.RESPONSE</t>
        <t>Description: The message is a response to a TVBD.QUERY
          request for information.</t> 
        <t>Message code: ws.messageType.INFORMATION.QUERY</t>
        <t>Description: The message is a non-certified
          client-initiated query for general (possibly white-space)
          frequency information NOT for the purposes of
          transmission. Examples of non-certified clients include
          network management and planning systems, client software
          applications, etc.</t> 
        <t>Message code: ws.messageType.INFORMATION.RESPONSE</t>
        <t>Description: The message is a response to an
          INFORMATION.QUERY request for information.</t> 
      </list>
    </t>
    
    <t>minFreq attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:double</t>
        <t>Description: The minimum (or start) frequency of the
          indicated channel in MHz.</t> 
      </list>
    </t>
    
    <t>name attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description: A human readable name or label that may be
          used to identify a location or station. A useful hint is to
          use a memorable place name as might be represented on a map
          (e.g. “Empire State Building”). For licensed wireless
          services it is recommended to use the facility call
          sign. For unlicensed wireless services it is recommended to
          use the venue name.</t> 
      </list>
    </t>
    
    <t>protocolVersion attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:float</t>
        <t>Description: The message protocol version.</t>
      </list>
    </t>
    
    <t>stationClass attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description: Indicates the station
          classification. Classification may be used to determine
          whether and how many elements of this station are required
          for validation. Allowed values are:</t> 
        <t>TX. This is a transmitting station and a transmitter is
          required in the transmitterList element</t> 
        <t>RX. This is a receive-only station and a transmitter
          element is NOT required</t> 
        <t>TXRX. This station is able to both transmit and receive and
          a transmitter is required in the transmitterList element.</t> 
      </list>
    </t>
    
    <t>stationType attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description: A description of this station's operation.</t>
      </list>
    </t>
    
    <t>statusIndicator attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:int</t>
        <t>Description: The number of available white space channels
          included in the message. A negative value indicates that an
          error condition has occured.</t> 
      </list>
    </t>
    
<!--     <t>rrule attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/>.</t> -->
<!--       </list> -->
<!--     </t> -->
    
    <t>timeStamp attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:dateTime</t>
        <t>Description: When the message was created.</t>
      </list>
    </t>

<!--     <t>tzid attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/>.</t> -->
<!--       </list> -->
<!--     </t> -->
    
<!--     <t>uid attribute</t> -->
<!--     <t> -->
<!--       <list style="empty"> -->
<!--         <t>Type: xs:string</t> -->
<!--         <t>Description: Excerpted from <xref target="RFC5545"/>.</t> -->
<!--       </list> -->
<!--     </t> -->
    
    <t>uuid attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description (for use in Location):A universally unique
          identifier (UUID) associated with and permanently assigned
          to this location.</t> 
        <t>Description (for use in Station):A universally unique
          identifier (UUID) associated with and permanently assigned to
          this station.</t> 
        <t>Description (for use in whitespaceFrequency): A
          universally unique idenfifier (UUID) assigned by an
          Administrator that is associated with this freuquency</t>
        <t>Description (for use in whitespaceQuery): A universally
          unique identifier (UUID) created by the inquiring agent
          (i.e. a TV band device, user software, etc.) and associated
          with this whitespace query message. This uuid may be used to
          correlate a whitespaceResponse message with this
          whitespaceQuery and to simplify logging and archival.</t> 
        <t>Description (for use in whitespaceResponse): A
          universally unique identifier (UUID), set to match the
          client's whitespaceQuery.uuid attribute and to simplify
          logging and arhival.</t> 
      </list>
    </t>
    
    <t>x-geocode attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description: An enumerated value indicating whether any
          one of this location object's components have been
          calculated according to another of this location object's
          set parameters.</t> 
        <t>Allowed values are:</t>
        <t>NO (xs:string) (DEFAULT). The coordinate, address and
          geometry elements of this location are not correlated.</t> 
        <t>GC (xs:string). The coordinate.[longitude, latitude] and
          geometry.point values have been calculated and set according
          to a Geo-coding algorithm from the address.</t> 
        <t>RG (xs:string). The address has been calculated and set
          according to a Reverse Geo-coding algorithm from the
          coordinate.[longitude, latitude] value.</t> 
      </list>
    </t>
    
    <t>x-haat attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:float</t>
        <t>Description: The ground height above average terrain
          value at this location’s coordinates, calculated according
          to the methodology described in 47 CFR 73.684(d). The
          elevation model used in the calculation of this location
          attribute is recorded in the coordinate.x-elevationModel
          attribute. This value is used to support TVBD transmit
          antenna compliance with 15.709(b)(2), which states that the
          ground level HAAT must be below 76 meters.</t> 
      </list>
    </t>
    
    <t>x-timeZone attribute</t>
    <t>
      <list style="empty">
        <t>Type: xs:string</t>
        <t>Description: The local time zone at this location. Two
          interchangeable formats are supported, with the zoneinfo
          format preferred:</t> 
        <t>The zoneinfo database format  (e.g. “America/New_York”)</t>
        <t>An offset to Coordinated  Universal Time
          (e.g. “UTC-05:00” or “UTC-5”</t> 
        <t>Note: Three-character notation (e.g. “EDT”) is not supported.</t>
      </list>
    </t>
    
  </section><!-- Attributes definition -->
	</section> <!-- Data model details -->

	

    <section anchor="IANA" title="IANA Considerations">
      <t>
	This document will require actions on the part of IANA to
	assign values for the new messages and attributes.
      </t>
    </section>

    <section anchor="Security" title="Security Considerations">
	    <t>
              This document defines the data model for the database
              query and response protocol to be used between white
              space devices and a database. The actual security for
              the messages that transport these objects needs to be
              specified in the relevant document.
       </t>
    </section>


      <!-- ================================================================== -->

      <section title="Acknowledgements">
        <t>
          This document has been made possible as a result of the
          efforts of Basavaraj Patil and Scott Probasco. 
         </t>
      </section>

      <!-- ================================================================== -->

   </middle>

   <!-- ================================================================== -->

   <back>
      <references title="Normative References">
         &RFC2119;
	 &RFC5545;
	 &RFC5139;
	 &RFC5491;
	 &RFC2426;
      </references>

      <references title="Informative References">

         &I-D.ietf-paws-problem-stmt-usecases-rqmts;
      </references>
   </back>
</rfc>


<!-- For temp use:

    <section title=" ">
      <t>
      </t>
    </section>


      <t>
	<figure align="center" title="Station Element">
	<artwork align="center"><![CDATA[

       ]]></artwork>
      </figure>
      </t>	

      <t>
	<t> </t>
	<list style="empty">
	  <t> </t>
	  <t>
	  </t>
	</list>
      </t>
  
-->

