Network Working Group K. Taniuchi
Internet-Draft Y. Ohba
Expires: April 13, 2008 Toshiba
D. Subir
Telcordia
October 11, 2007
IEEE 802.21 Basic Schema
draft-ohba-802dot21-basic-schema-01
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 13, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract
This document describes the basic schema for IEEE 802.21 Media-
Independent Information Service, an RDF (Resource Description
Framework) schema defined in IEEE 802.21. This document serves as
the Specification required by the IANA to maintain a global registry
for storing the RDF schema.
Taniuchi, et al. Expires April 13, 2008 [Page 1]
Internet-Draft IEEE 802.21 Basic Schema October 2007
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. RDF Schema for IEEE 802.21 Basic Schema . . . . . . . . . . . 4
3. Security Considerations . . . . . . . . . . . . . . . . . . . 19
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
6.1. Normative References . . . . . . . . . . . . . . . . . . . 20
6.2. Informative References . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 21
Intellectual Property and Copyright Statements . . . . . . . . . . 22
Taniuchi, et al. Expires April 13, 2008 [Page 2]
Internet-Draft IEEE 802.21 Basic Schema October 2007
1. Introduction
IEEE 802.21 is a standard that specifies 802 media access-independent
mechanisms that optimize handovers between heterogeneous 802 systems
and between 802 systems and cellular systems [802.21].
IEEE 802.21 provides a set of handover-enabling functions within the
protocol stacks of the network elements and a new entity created
therein called the Media-Independent Handover Function (MIHF). A
media independent Service Access Point (called the MIH_SAP) and
associated primitives are defined to provide MIHF users with access
to the services of the MIHF. The MIHF provides the following
services. 1) The Media Independent Event Service (MIES) detects
events and delivers triggers from both local as well as remote
interfaces. 2) The Media Independent Command Service (MICS) provides
a set of commands for the MIHF users to control handover relevant
link states. 3) The Media Independent Information Service (MIIS)
provides the network elements with the information about neighboring
networks, thus enabling making of more effective handover decisions
across heterogeneous networks. The first two services are out of the
scope of this document.
The MIIS defines information models and query mechanisms where a
query mechanism depends on the information model which it is based
on. There are two types of information models in the MIIS for
representing the same set of pre-defined pieces of information in
different ways. One information model is based on identifying each
piece of information by a unique integer value. The other
information model is based on RDF (Resource Description Framework)
[RDF] in which each piece of information is identified by a URI
(Uniform Resource Identifiers) [RFC3986]. The two information models
have different characteristics in terms of namespace management as
well as query capability. This document is intended for the latter
type of information model.
In RDF, an information model is described in the form of RDF schema
[RDFS]. To provide extensibility in terms of defining new pieces of
information in addition to the pre-defined ones, the RDF schema
definition for MIIS consists of two parts; the basic and the extended
schema. An MIHF is pre-provisioned with the basic schema for
querying information defined in the 802.21 specification. The basic
schema requires a persistent URL for its definition. An extended
schema is used for querying vendor-specific information and it does
not require a persistent URL for its definition.
This document describes the IEEE 802.21 basic schema, or an RDF
schema used for IEEE 802.21 MIIS. This document serves as the
Specification required by the IANA to maintain a global registry for
Taniuchi, et al. Expires April 13, 2008 [Page 3]
Internet-Draft IEEE 802.21 Basic Schema October 2007
storing the RDF schema [RFC3688]. The basic schema definition is
described in Section 2. Information required by IANA for assigning a
global registry for the basic schema is described in Section 4.
2. RDF Schema for IEEE 802.21 Basic Schema
<?xml version="1.0"?>
<!DOCTYPE rdf:RDF [
<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
<!ENTITY mihbasic "URL_TO_BE_ASSIGNED">
<!ENTITY owl "http://www.w3.org/2002/07/owl#">
<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
]>
<rdf:RDF xmlns:rdf="&rdf;" xmlns:rdfs="&rdfs;"
xmlns:mihbasic="&mihbasic;" xml:base="&mihbasic;"
xmlns:owl="&owl;" xmlns:xsd="&xsd;">
<owl:Ontology rdf:about="">
<rdfs:label>
Basic Schema for IEEE 802.21 Information Service
</rdfs:label>
<owl:versionInfo>1.0</owl:versionInfo>
</owl:Ontology>
<owl:DatatypeProperty rdf:ID="ie_type_identifier">
<rdfs:subPropertyOf rdf:resource="&rdfs;label"/>
<rdfs:range rdf:resource="&xsd;hexBinary"/>
<rdfs:comment>
A type identifier values for Information Elements.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_container_list_of_network">
<mihbasic:ie_type_identifier>10000300</mihbasic:ie_type_identifier>
<rdfs:range rdf:resource="#LIST_OF_NETWORKS"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="LIST_OF_NETWORKS">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_container_network"/>
<owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:minCardinality>
</owl:Restriction>
Taniuchi, et al. Expires April 13, 2008 [Page 4]
Internet-Draft IEEE 802.21 Basic Schema October 2007
</rdfs:subClassOf>
</owl:Class>
<owl:ObjectProperty rdf:ID="type_ie_container_network">
<mihbasic:ie_type_identifier>10000301</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#LIST_OF_NETWORKS"/>
<rdfs:range rdf:resource="#NETWORK"/>
<rdfs:comment>
This class contains General Information depicting and Access
Network Specific Information.
</rdfs:comment>
</owl:ObjectProperty>
<owl:Class rdf:ID="NETWORK">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_network_type"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_operator_identifier"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_container_poa"/>
<owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:ObjectProperty rdf:ID="type_ie_network_type">
<mihbasic:ie_type_identifier>0x10000000</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#NETWORK_TYPE"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="NETWORK_TYPE">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#link_type"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
Taniuchi, et al. Expires April 13, 2008 [Page 5]
Internet-Draft IEEE 802.21 Basic Schema October 2007
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="link_type">
<rdfs:domain rdf:resource="#NETWORK_TYPE"/>
<rdfs:range rdf:resource="&xsd;unsignedInt"/>
<rdfs:comment>
Link type of a network. The following values are assigned:
1: Wireless - GSM
2: Wireless - GPRS
3: Wireless - EDGE
15: Ethernet
18: Wireless - Other
19: Wireless - IEEE 802.11
22: Wireless - CDMA2000
23: Wireless - UMTS
24: Wireless - cdma-2000-HRPD
27: Wireless - IEEE 802.16
28: Wireless - IEEE 802.20
29: Wireless - IEEE 802.22
</rdfs:comment>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="revision">
<rdfs:subPropertyOf rdf:resource="#bit_number"/>
<rdfs:domain rdf:resource="#NETWORK_TYPE"/>
<rdfs:comment>
The range of #bit_number is 0-63.
</rdfs:comment>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="type_ie_operator_identifier">
<mihbasic:ie_type_identifier>0x10000001</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#OPERATOR_ID"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="OPERATOR_ID">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#operator_namespace"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
Taniuchi, et al. Expires April 13, 2008 [Page 6]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<owl:Restriction>
<owl:onProperty rdf:resource="#operator_name"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="operator_namespace">
<rdfs:domain rdf:resource="#OPERATOR_ID"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
A value of Operator Type:
0: GSM/UMTS
1: CDMA
2: REALM
3: ITU-T/TSB
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="operator_name">
<rdfs:domain rdf:resource="#OPERATOR_ID"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
The value is a non NULL terminated
string whose length shall not exceed 253 octets.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="type_ie_service_provider_identifier">
<mihbasic:ie_type_identifier>0x10000002</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
A non-NULL terminated string whose length shall not exceed 253 octets.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="type_ie_access_network_identifier">
<mihbasic:ie_type_identifier>0x10000100</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
A non-NULL terminated string whose length shall not exceed 253 octets.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="type_ie_access_network_aux_id">
Taniuchi, et al. Expires April 13, 2008 [Page 7]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<mihbasic:ie_type_identifier>0x10000101</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
It is SSID if network type is IEEE 802.11.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_roaming_partner">
<mihbasic:ie_type_identifier>0x10000102</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#OPERATOR_ID"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="type_ie_cost">
<mihbasic:ie_type_identifier>0x10000103</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#COST"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="COST">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#cost_unit"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#cost_value"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#cost_currency"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="cost_unit">
<rdfs:domain rdf:resource="#COST"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
Taniuchi, et al. Expires April 13, 2008 [Page 8]
Internet-Draft IEEE 802.21 Basic Schema October 2007
The unit of the cost:
0: second
1: minute
2: hours
3: day
4: week
5: month
6: year
7: free
8: flat rate
9-255: Reserved
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="cost_value">
<rdfs:domain rdf:resource="#COST"/>
<rdfs:range rdf:resource="&xsd;double"/>
<rdfs:comment>
The cost value in Currency/Unit
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="cost_currency">
<rdfs:domain rdf:resource="#COST"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
A three-letter currency code(e.g. "USD") specified by
ISO 4217.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="bit_number">
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
This property represents a bit number that has
the value as true.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_network_security">
<mihbasic:ie_type_identifier>0x10000105</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#NETWORK_SECURITY"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="NETWORK_SECURITY">
</owl:Class>
Taniuchi, et al. Expires April 13, 2008 [Page 9]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<owl:ObjectProperty rdf:ID="type_ie_network_qos">
<mihbasic:ie_type_identifier>0x10000106</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#QOS_LIST"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="QOS_LIST">
</owl:Class>
<owl:DatatypeProperty rdf:ID="num_qos_types">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="throughput">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="&xsd;unsignedInt"/>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="packet_error_rate">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="&xsd;unsignedShort"/>
</owl:DatatypeProperty>
<owl:Class rdf:ID="COS">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#cos_id"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#cos_value"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="cos_id">
<rdfs:domain rdf:resource="#COS"/>
<rdfs:range rdf:resource="&xsd;unsignedShort"/>
<rdfs:comment>
A type to represent a class of service identifier.
</rdfs:comment>
</owl:DatatypeProperty>
Taniuchi, et al. Expires April 13, 2008 [Page 10]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<owl:DatatypeProperty rdf:ID="cos_value">
<rdfs:domain rdf:resource="#COS"/>
<rdfs:range rdf:resource="&xsd;unsignedShort"/>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="cos_min_packet_transfer_delay">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="#COS"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="cos_avg_packet_transfer_delay">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="#COS"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="cos_max_packet_transfer_delay">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="#COS"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="cos_packet_transfer_delay_jitter">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="#COS"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="cos_packet_loss_rate">
<rdfs:domain rdf:resource="#QOS_LIST"/>
<rdfs:range rdf:resource="#COS"/>
</owl:ObjectProperty>
<owl:DatatypeProperty rdf:ID="type_ie_network_data_rate">
<mihbasic:ie_type_identifier>0x10000107</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="&xsd;unsignedInt"/>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_network_ip_config_methods">
<mihbasic:ie_type_identifier>0x10000108</mihbasic:ie_type_identifier>
<rdfs:subPropertyOf rdf:resource="#bit_number"/>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:comment>
The range of #bit_number is 0-31.
</rdfs:comment>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="type_ie_network_capabilities">
<mihbasic:ie_type_identifier>0x10000109</mihbasic:ie_type_identifier>
<rdfs:subPropertyOf rdf:resource="#bit_number"/>
Taniuchi, et al. Expires April 13, 2008 [Page 11]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:comment>
The range of #bit_number is 0-31.
</rdfs:comment>
</owl:ObjectProperty>
<owl:DatatypeProperty rdf:ID="type_ie_supported_lcp">
<mihbasic:ie_type_identifier>0x1000010A</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_container_poa">
<mihbasic:ie_type_identifier>0x10000302</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#NETWORK"/>
<rdfs:range rdf:resource="#POA"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="POA">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_poa_mac_address"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_poa_location"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_poa_channel_range"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_poa_system_information"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
Taniuchi, et al. Expires April 13, 2008 [Page 12]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<owl:Restriction>
<owl:onProperty rdf:resource="#type_ie_poa_subnet_information"/>
<owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:minCardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:comment>
This class contains all the information depicting a PoA.
</rdfs:comment>
</owl:Class>
<owl:ObjectProperty rdf:ID="type_ie_poa_mac_address">
<mihbasic:ie_type_identifier>0x10000302</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#POA"/>
<rdfs:range rdf:resource="#TRANSPORT_ADDRESS"/>
</owl:ObjectProperty>
<owl:ObjectProperty rdf:ID="type_ie_poa_location">
<mihbasic:ie_type_identifier>0x10000201</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#POA"/>
<rdfs:range rdf:resource="#LOCATION"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="LOCATION">
</owl:Class>
<owl:Class rdf:ID="BINARY_GEO_LOCATION">
<rdfs:subClassOf rdf:resource="#LOCATION"/>
<rdfs:comment>
This class has properties that represent geographic coordinate.
The format is based on the Location Configuration Information (LCI)
defined in RFC 3825.
</rdfs:comment>
</owl:Class>
<owl:DatatypeProperty rdf:ID="la_res">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="latitude">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;double"/>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="lo_res">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
Taniuchi, et al. Expires April 13, 2008 [Page 13]
Internet-Draft IEEE 802.21 Basic Schema October 2007
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="longitude">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;double"/>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="altitude_type">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
Following codes are defined:
1: Meters: in 2s-complement fixed-point 22-bit integer part with
8-bit fraction. If AT = 1, an AltRes value 0.0 would indicate
unknown altitude. The most precise Altitude would have an AltRes
value of 30. Many values of AltRes would obscure any variation
due to vertical datum differences.
2: Floors: in 2s-complement fixed-point 22-bit integer part with
8-bit fraction. AT = 2 for Floors enables representing altitude in
a form more relevant in buildings which have different
floor-to-floor dimensions.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="alt_res">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
Altitude resolution. 6 bits indicating the number of valid bits
in the altitude. Values above 30 (decimal) are undefined and
reserved.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="altitude">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;double"/>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="datum">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
Following codes are defined:
1: WGS
Taniuchi, et al. Expires April 13, 2008 [Page 14]
Internet-Draft IEEE 802.21 Basic Schema October 2007
2: NAD 83 (with associated vertical datum for North American
vertical datum for 1998)
3: NAD 83 (with associated vertical datum for Mean Lower Low Water
(MLLW))
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="geo_lo_method">
<rdfs:domain rdf:resource="#BINARY_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
Way location information was derived or discovered:
0: GPS
1: Assisted GPS
2: Manual
3: Provided by DHCP
4: Triangulation
5-255: Reserved
</rdfs:comment>
</owl:DatatypeProperty>
<owl:Class rdf:ID="XML_GEO_LOCATION">
<rdfs:subClassOf rdf:resource="#LOCATION"/>
</owl:Class>
<owl:DatatypeProperty rdf:ID="xml_geo_location">
<rdfs:domain rdf:resource="#XML_GEO_LOCATION"/>
<rdfs:range rdf:resource="&xsd;String"/>
<rdfs:comment>
Geo address elements as described in RFC4119.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:Class rdf:ID="BINARY_CIVIC_LOCATION">
<rdfs:subClassOf rdf:resource="#LOCATION"/>
<rdfs:comment>
This class has properties that represent civic address.
The format is defined in IETF RFC 4676.
</rdfs:comment>
</owl:Class>
<owl:DatatypeProperty rdf:ID="civic_country_code">
<rdfs:domain rdf:resource="#BINARY_CIVIC_LOCATION"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
Two-letter ISO 3166 country code in capital ASCII letters.
</rdfs:comment>
Taniuchi, et al. Expires April 13, 2008 [Page 15]
Internet-Draft IEEE 802.21 Basic Schema October 2007
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="civic_addr_elem">
<rdfs:domain rdf:resource="#BINARY_CIVIC_LOCATION"/>
<rdfs:range rdf:resource="#CIVIC_ADDR_ELEM"/>
<rdfs:comment>
This property contains the civic address elements.
The format of the civic address elements is described
in Section 3.4 of IETF RFC 4676 with a TLV pair
(whereby the Type and Length fields are one octet long).
</rdfs:comment>
</owl:ObjectProperty>
<owl:Class rdf:ID="CIVIC_ADDR_ELEM">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#catype"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#cavalue"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="catype">
<rdfs:domain rdf:resource="#CIVIC_ADDR_ELEM"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
A one-octet descriptor of the data civic address value.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="cavalue">
<rdfs:domain rdf:resource="#CIVIC_ADDR_ELEM"/>
<rdfs:range rdf:resource="&xsd;string"/>
<rdfs:comment>
The civic address value.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:Class rdf:ID="XML_CIVIC_LOCATION">
<rdfs:subClassOf rdf:resource="#LOCATION"/>
Taniuchi, et al. Expires April 13, 2008 [Page 16]
Internet-Draft IEEE 802.21 Basic Schema October 2007
</owl:Class>
<owl:DatatypeProperty rdf:ID="xml_civic_location">
<rdfs:domain rdf:resource="#XML_CIVIC_LOCATION"/>
<rdfs:range rdf:resource="&xsd;String"/>
<rdfs:comment>
Geo address elements as described in RFC4119.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_poa_channel_range">
<mihbasic:ie_type_identifier>0x10000202</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#POA"/>
<rdfs:range rdf:resource="#CHANNEL_RANGE"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="CHANNEL_RANGE">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#low_channel_range"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#high_channel_range"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="low_channel_range">
<rdfs:domain rdf:resource="#CHANNEL_RANGE"/>
<rdfs:range rdf:resource="&xsd;unsignedInt"/>
<rdfs:comment>
Lowest channel frequency in MHz
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="high_channel_range">
<rdfs:domain rdf:resource="#CHANNEL_RANGE"/>
<rdfs:range rdf:resource="&xsd;unsignedInt"/>
<rdfs:comment>
Highest channel frequency in MHz
</rdfs:comment>
</owl:DatatypeProperty>
Taniuchi, et al. Expires April 13, 2008 [Page 17]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<owl:ObjectProperty rdf:ID="type_ie_poa_system_information">
<mihbasic:ie_type_identifier>0x10000203</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#POA"/>
<rdfs:range rdf:resource="#SYSTEM_INFORMATION"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="SYSTEM_INFORMATION">
</owl:Class>
<owl:ObjectProperty rdf:ID="type_ie_poa_subnet_information">
<mihbasic:ie_type_identifier>0x10000204</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#POA"/>
<rdfs:range rdf:resource="#IP_SUBNET_INFO"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="IP_SUBNET_INFO">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#subnet_address"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#ip_prefix_len"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:ObjectProperty rdf:ID="subnet_address">
<rdfs:domain rdf:resource="#IP_SUBNET_INFO"/>
<rdfs:range rdf:resource="#TRANSPORT_ADDRESS"/>
</owl:ObjectProperty>
<owl:DatatypeProperty rdf:ID="ip_prefix_len">
<rdfs:domain rdf:resource="#IP_SUBNET_INFO"/>
<rdfs:range rdf:resource="&xsd;unsignedByte"/>
<rdfs:comment>
The bit length of the prefix of the subnet to which subnet_address
property belongs. The prefix_length is less than or equal to 32
for IPv4 subnet and less than or equal to 128 for IPv6 subnet.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:ObjectProperty rdf:ID="type_ie_poa_ip_address">
Taniuchi, et al. Expires April 13, 2008 [Page 18]
Internet-Draft IEEE 802.21 Basic Schema October 2007
<mihbasic:ie_type_identifier>0x10000205</mihbasic:ie_type_identifier>
<rdfs:domain rdf:resource="#POA"/>
<rdfs:range rdf:resource="#TRANSPORT_ADDRESS"/>
</owl:ObjectProperty>
<owl:Class rdf:ID="TRANSPORT_ADDRESS">
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#address_type"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="#address_value"/>
<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1
</owl:cardinality>
</owl:Restriction>
</rdfs:subClassOf>
</owl:Class>
<owl:DatatypeProperty rdf:ID="address_type">
<rdfs:domain rdf:resource="#TRANSPORT_ADDRESS"/>
<rdfs:range rdf:resource="&xsd;unsignedShort"/>
<rdfs:comment>
An Address Family defined in
http://www.iana.org/assignments/address-family-numbers.
</rdfs:comment>
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:ID="address_value">
<rdfs:domain rdf:resource="#TRANSPORT_ADDRESS"/>
<rdfs:range rdf:resource="&xsd;hexBinary"/>
<rdfs:comment>
An address value specific to address_type.
</rdfs:comment>
</owl:DatatypeProperty>
</rdf:RDF>
3. Security Considerations
Beyond the considerations described in [RFC3688], there are no
additional security considerations other than that was already found
with any other IANA registry.
Taniuchi, et al. Expires April 13, 2008 [Page 19]
Internet-Draft IEEE 802.21 Basic Schema October 2007
4. IANA Considerations
The IEEE 802.21 basic schema requires an IANA-assigned registry for
an RDF schema. According to [RFC3688], the following is the
information needed by IANA.
URI (please assign)
The URI that identifies the IEEE 802.21 basic schema.
Registrant Contact
Yoshihiro Ohba
Toshiba America Research, Inc.
1 Telcordia Drive
Piscataway, NJ 08854
USA
Phone: +1 732 699 5365
Email: yohba@tari.toshiba.com
XML
The exact XML to be stored in the registry is described in
Section 2, except that the word "URL_TO_BE_ASSIGNED" in the XML
definition needs to be replaced with IANA-assigned URL for the
stored XML.
5. Acknowledgments
TBD.
6. References
6.1. Normative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[RDF] W3C Recommendation, "Resource Description Framework (RDF)
- Concepts and Abstract Syntax
(http://www.w3.org/TR/rdf-concepts/)", February 2004.
[RDFS] W3C Recommendation, "RDF Vocabulary Description Language
1.0: RDF Schema (http://www.w3.org/TR/rdf-schema/)",
February 2004.
Taniuchi, et al. Expires April 13, 2008 [Page 20]
Internet-Draft IEEE 802.21 Basic Schema October 2007
6.2. Informative References
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005.
[802.21] Institute of Electrical and Electronics Engineers, "Draft
IEEE Standard for Local and Metropolitan Area Networks:
Media Independent Handover Services", IEEE Standard
802.21/D07-01, 2007.
Authors' Addresses
Kenichi Taniuchi
Corporate R&D Center, Toshiba Corporation
1, Komukai-Toshiba-cho, Saiwai-ku
Kawasaki, Kanagawa 212-8582
Japan
Phone: +81 44 549 2230
Email: kenichi.taniuchi@toshiba.co.jp
Yoshihiro Ohba
Toshiba America Research, Inc.
1 Telcordia Drive
Piscataway, NJ 08854
USA
Phone: +1 732 699 5365
Email: yohba@tari.toshiba.com
Subir Das
Telcordia
1 Telcordia Drive
Piscataway, NJ 08854
USA
Phone: +1 732 699 2483
Email: subir@research.telcordia.com
Taniuchi, et al. Expires April 13, 2008 [Page 21]
Internet-Draft IEEE 802.21 Basic Schema October 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Taniuchi, et al. Expires April 13, 2008 [Page 22]
