Network Working Group K. Taniuchi Internet-Draft Y. Ohba Expires: May 6, 2009 Toshiba D. Subir Telcordia November 2, 2008 IEEE 802.21 Basic Schema draft-ohba-802dot21-basic-schema-05 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 May 6, 2009. Taniuchi, et al. Expires May 6, 2009 [Page 1] Internet-Draft IEEE 802.21 Basic Schema November 2008 Abstract This document describes an RDF (Resource Description Framework) schema defined in IEEE 802.21 as the basic schema for Media- Independent Information Service. This document serves as the Specification required by the IANA to maintain a global registry for storing the RDF schema. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. RDF Schema for IEEE 802.21 Basic Schema . . . . . . . . . . . 9 4. Security Considerations . . . . . . . . . . . . . . . . . . . 48 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 49 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 50 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 51 7.1. Normative References . . . . . . . . . . . . . . . . . . . 51 7.2. Informative References . . . . . . . . . . . . . . . . . . 53 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 55 Intellectual Property and Copyright Statements . . . . . . . . . . 56 Taniuchi, et al. Expires May 6, 2009 [Page 2] Internet-Draft IEEE 802.21 Basic Schema November 2008 1. Introduction IEEE 802.21 is a standard that specifies media independent mechanisms that optimize handovers between heterogeneous IEEE 802 systems and between IEEE 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 defines a new entity 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) that detects events and delivers triggers from both local as well as remote interfaces, 2) the Media Independent Command Service (MICS) that provides a set of commands for the MIHF users to control handover relevant link states, and 3) the Media Independent Information Service (MIIS) that provides the network elements with the information about neighboring networks, thus enabling 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. 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 capabilities. This document is intended for the latter type of information model. In RDF, an information model is described in the form of an 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 IEEE 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 an RDF schema used for IEEE 802.21 MIIS with some additional texts for clarity and better understanding the content of the schema. This document serves as the Specification required by the IANA to maintain a global registry for storing the Taniuchi, et al. Expires May 6, 2009 [Page 3] Internet-Draft IEEE 802.21 Basic Schema November 2008 RDF schema [RFC3688]. The original IEEE 802.21 basic schema is defined in Annex H of [802.21]. This document captures few additional points that are mentioned below: o New tags on the format and semantics of each class and property including more references in the tags are added for clarity. o Two PLMN identifiers are merged into a single data type property called "plmn_id" since two data type properties for PLMN identifier, i.e., 3gpp_2g_cell_id_plmn_id and link_addr_3gpp_3g_cell_id_plmn_id defined in [802.21] use the same format. o Similarly, three cell identifiers are merged into a single data type property called "cell_id" since three data type properties for cell identifier, i.e., 3gpp_3g_cell_id_cell_id, location_cell_id and sib_cell_id defined in [802.21] use the same format. o Some properties such as dhcp_serv, fn_agent, acc_rtr, proxy_addr_ip and mac_addr that are defined as owl: DatatypeProperty are redefined as owl:ObjectProperty in this document. Also, some properties such as subtype, ie_net_capabilities and ie_net_mob_mgmt_prot that are defined as owl:ObjectProperty are redefined as owl:DatatypeProperty in this document. o In owl:DatatypeProperty op_namespace of the basic schema in [802.21], the namespace value of one (1) to represent CDMA operator names. Since ITU-T/TSB namespace should be used for CDMA operator names, the namespace value of one (1) allocated to represent CDMA operator names in owl:DatatypeProperty op_namespace of the basic schema is allocated is marked "Unused" in this document. o The REALM encoding for Unicode used in the basic schema in this document is based on use of XML Unicode encoding [UNICODE-XML] as opposed to the REALM encoding scheme defined in [I-D.ietf-geopriv-radius-lo] which requires conversion from Unicode to ASCII for non-ASCII characters due to a data type limitation in RADIUS. o A note is added to mention that a cost_unit of 7 (free) and a cost_unit of 8 (flat rate) with a cost_value of 0 may have different semantics in owl:DatatypeProperty cost_unit Taniuchi, et al. Expires May 6, 2009 [Page 4] Internet-Draft IEEE 802.21 Basic Schema November 2008 o A note is added to mention that it is possible to include multiple ie_cost object properties in a single NETWORK class object in owl: ObjectProperty ie_cost. o A new semantic is added to indicate that an International Mobile Subscriber Identity (IMSI) or a Temporary Mobile Subscriber Identities (TMSI) is used as a _3gpp_addr value in owl: DatatypeProperty _3gpp_addr. o A new semantic is added to indicate that a Mobile Identification Number (MIN) is used as a _3gpp_addr value in owl:DatatypeProperty _3gpp2_addr. o A new semantic is added to explain the meaning of each bit in owl: DatatypeProperty ie_net_mob_mgmt_prot. o A note is added to mention that it is possible to include multiple ie_poa_subnet_info object properties in a single POA class object in owl:ObjectProperty ie_poa_subnet_info. o A new semantic is added to explain that an MIIS server may advertise different IP subnets to different MIIS clients in owl: Class IP_SUBNET_INFO. o A new semantic is added to indicate that a non-link-local IP address of the PoA is used for owl:ObjectProperty ie_poa_ip_addr. o The datatype of owl:DatatypeProperty eirp is changed from unsignedByte to byte since EIRP can have a negative value. Taniuchi, et al. Expires May 6, 2009 [Page 5] Internet-Draft IEEE 802.21 Basic Schema November 2008 2. Acronyms The following acronims are used in this document. CoS: Class of Service DCD: Downlink Channel Descriptor D-TDoA: Differencialk Time Difference of Arrival EDGE: Enhanced Data Rates for GSM Evolution FQDN: Fully Qualified Domain Name GPRS: General Packet Radio Service GSM: Global System for Mobile Communication HELD: HTTP Enabled Location Delivery HESSID: Homogeneous Extended Service Set ID HRPD: High Rate Packet Data HSDPA: High-Speed Downlink Packet Access HSUPA: High-Speed Uplink Packet Access ISO: International Organization for Standardization ITU-T: ITU Telecommunication Standardization Sector Taniuchi, et al. Expires May 6, 2009 [Page 6] Internet-Draft IEEE 802.21 Basic Schema November 2008 LbyR: Location by Reference LCI: Location Configuration Information LCP: Location Configuration Protocol LLDP: Link Layer Discovery Protocol MED: Media Endpoint Discovery MCC: Mobile Country Code MIMO: Multiple-Input and Multiple-Output MNC: Mobile Network Code OFDM: Orthogonal Frequency-Division Multiplexing OMA: Open Mobile Alliance OWL: Web Ontology Language PLMN: Public Land Mobile Network PN: System Information Block PoA: Network Point of Attachment QoS: Quality of Service Taniuchi, et al. Expires May 6, 2009 [Page 7] Internet-Draft IEEE 802.21 Basic Schema November 2008 RDF: Resource Description Language UCD: Uplink Channel Descriptor UMTS: Universal Mobile Telecommunications System U-TDoA: Uplink Time Difference of Arrival SIB: System Information Block SPARQL: The SPARQL Protocol and RDF Query Language SUPL: Secure User Plane Location XML: Extensible Markup Language Taniuchi, et al. Expires May 6, 2009 [Page 8] Internet-Draft IEEE 802.21 Basic Schema November 2008 3. RDF Schema for IEEE 802.21 Basic Schema ]> Basic Schema for IEEE 802.21 Information Service 1.0 Section numbers cited in comment tags without a reference to a corresponding document are the section numbers in [802.21]. A data type property to represent Information Element identifiers defined in Annex G. A data type property to represent a bit number that has the value as true. Taniuchi, et al. Expires May 6, 2009 [Page 9] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x10000300 An object property to contain a LIST_OF_NETWORKS class object. 1 A class to represent a list of networks. 0x10000301 An object property of LIST_OF_NETWORKS to contain a NETWORK class object. 1 Taniuchi, et al. Expires May 6, 2009 [Page 10] Internet-Draft IEEE 802.21 Basic Schema November 2008 1 A class to represent an Access Network Container containing information that depicts an access network. 0x10000000 An object property of NETWORK to contain a NETWORK_TYPE class object. A class to represent a network type. A data type property of NETWORK_TYPE to represent a link type. The following values are assigned: 1: Wireless - GSM 2: Wireless - GPRS 3: Wireless - EDGE 15: Ethernet - IEEE 802.3 18: Wireless - Other 19: Wireless - IEEE 802.11 Taniuchi, et al. Expires May 6, 2009 [Page 11] Internet-Draft IEEE 802.21 Basic Schema November 2008 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 A data type property of NETWORK_TYPE to represent a network subtype. The following values are assigned for Ethernet - IEEE 802.3: Bit 0: 10 Mb Bit 1: 100 Mb Bit 2: 1000 Mb Bit 3-63: (Reserved) The above bits represent the link speeds that Ethernet supports. The capability information of twisted pair Ethernet link can be obtained via auto-negotiation as defined in Clause 28 of the 1998 edition of IEEE Std 802.3. The following values are assigned for Wireless - IEEE 802.11: Bit 0: 2.4 GHz Bit 1: 5 GHz Bit 2: 4.9 GHz Bit 3: 3.65 GHz Bit 4: 316 THz Bit 5-63 (Reserved) The above bits represent the frequency band that IEEE 802.11 link supports. The capability information and extended capabilities information of IEEE 802.11 link can further be represented as defined in 7.3.1.4 and 7.3.2.27, respectively, of IEEE Std 802.11-2007. The following values are assigned for Wireless - UMTS: Bit 0: Rel-99 Taniuchi, et al. Expires May 6, 2009 [Page 12] Internet-Draft IEEE 802.21 Basic Schema November 2008 Bit 1: Rel-4 Bit 2: Rel-5 (w/ HSDPA) Bit 3: Rel-6 (w/ HSUPA) Bit 4: Rel-7 (MIMO/OFDM) Bit 5: Rel-8 Bit 6-63: (Reserved) The following values are assigned for Wireless - cdma2000-HRPD Bit 0: Rev-0 Bit 1: Rev-A Bit 2: Rev-B Bit 3: Rev-C Bit 4-63: (Reserved) A data type property of NETWORK_TYPE to represent a generic type extension contained indicating a flexible length and format field. The content is to be defined and filled by the appropriate standard or service provider consortium, etc. The value is a non-NULL terminated string whose length shall not exceed 253 octets. 0x10000001 An object property of NETWORK to contain a OPERATOR_ID class object. Taniuchi, et al. Expires May 6, 2009 [Page 13] Internet-Draft IEEE 802.21 Basic Schema November 2008 1 1 A class to represent an operator identifier. A data type property of OPERATOR_ID to represent an operator name. The value is a non-NULL terminated string whose length shall not exceed 253 octets. A data type property of OPERATOR_ID to represent the namespace of op_name. The following values are assigned: 0: GSM/UMTS This namespace indicates operator names based on Transferred Account Data Interchange Group (TADIG) codes defined in GSM Association Document TD.13. The TADIG Code consists of two fields, with a total length of five ASCII characters consisting of a three-character country code and a two-character alphanumeric operator (or company) ID. Taniuchi, et al. Expires May 6, 2009 [Page 14] Internet-Draft IEEE 802.21 Basic Schema November 2008 1: Unused This namespace is unused. 2: REALM The REALM operator namespace indicates operator names based on any registered domain name. Such names are required to be unique and the rights to use a given realm name are obtained coincident with acquiring the rights to use a particular Fully Qualified Domain Name (FQDN). If a domain name contains Unicode characters, they are encoded based on http://www.w3.org/TR/unicode-xml/. 3: ITU-T/TSB This namespace indicates operator names based on the Mobile Country Code (MCC) and Mobile Network Code (MNC) defined in ITU-T E.212. The MCC/MNC values are assigned by the Telecommunications Standardization Bureau (TSB) within the ITU-T and designated administrators in different countries. The E.212 value consists of three ASCII digits containing the MCC, followed by two or three ASCII digits containing the MNC. 4: General This namespace indicates operator names that are not represented in any of GSM/UMTS, REALM and ITU-T/TSB. 0x10000002 A data type property of NETWORK to represent a service provider identifier. A service provider identifier is a non-NULL terminated string whose length shall not exceed 253 octets. 0x10000003 Taniuchi, et al. Expires May 6, 2009 [Page 15] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of NETWORK to represent a two-letter country code defined in ISO 3166-1. 0x10000100 A data type property of NETWORK to represent a network identifier. A network identifier is non-NULL terminated string whose length shall not exceed 253 octets. 0x10000101 A data type property of NETWORK to represent an auxiliary network identifier. An auxiliary network identifier is homogeneous extended service set ID (HESSID) if network type is IEEE 802.11. 0x10000102 An object property of NETWORK to contain an OPERATOR_ID class object for a roaming partner. Taniuchi, et al. Expires May 6, 2009 [Page 16] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x10000103 An object property of NETWORK to contain a COST class object. It is possible to include multiple ie_cost object properties in a single NETWORK class object. 1 1 1 A class to represent a cost for service or network usage. A data type property of COST to represent the unit of a cost. The following values are assigned: Taniuchi, et al. Expires May 6, 2009 [Page 17] Internet-Draft IEEE 802.21 Basic Schema November 2008 0: second 1: minute 2: hours 3: day 4: week 5: month 6: year 7: free 8: flat rate 9-255: (Reserved) Note that a cost_unit of 7 (free) and a cost_unit of 8 (flat rate) with a cost_value of 0 may have different semantics. For example, the latter may require subscriber authentication while the former may not. A data type property of COST to represent the value of a cost in Currency/Unit. A data type property of COST to represent the currency of a cost A currency is a three-letter currency code (e.g., "USD") specified by ISO 4217. 0x10000105 Taniuchi, et al. Expires May 6, 2009 [Page 18] Internet-Draft IEEE 802.21 Basic Schema November 2008 An object property of NETWORK to contain a QOS_LIST class object. A class to represent a list of measured QoS parameters. See Annex B for definition of each QoS parameter. A data type property of QOS_LIST to represent the number of QoS types. 1 1 A class to represent a Class of Service (CoS). Taniuchi, et al. Expires May 6, 2009 [Page 19] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of COS to represent a CoS identifier. A data type property of COS to represent a QoS parameter value of a specific CoS. An object property of QOS_LIST to contain a COS class object for the minimum packet transfer delay in ms. An object property of QOS_LIST to contain a COS class object for the average packet transfer delay in ms. Taniuchi, et al. Expires May 6, 2009 [Page 20] Internet-Draft IEEE 802.21 Basic Schema November 2008 An object property of QOS_LIST to contain a COS class object for the maximum packet transfer delay in ms. An object property of QOS_LIST to contain a COS class object for the packet transfer delay jitter in ms. An object property of QOS_LIST to contain a COS class object for the packet loss rate. The loss rate is equal to the integer part of the result of multiplying -100 times the log10 of the ratio between the number of packets lost and the total number of packets transmitted in the class population of interest. 0x10000106 A data type property of NETWORK to represent a data rate in kb/s. 0x10000107 Taniuchi, et al. Expires May 6, 2009 [Page 21] Internet-Draft IEEE 802.21 Basic Schema November 2008 An object property of NETWORK to contain a REGU_DOMAIN class object. 1 1 A class to represent a regulatory domain. A data type property of REGU_DOMAIN to represent the country code of a regulatory domain. The country code is a two-letter country code defined in ISO 3166-1. A data type property of REGU_DOMAIN to represent the regulatory class. The regulatory class values are defined in Annex J of IEEE Std 802.11k. Taniuchi, et al. Expires May 6, 2009 [Page 22] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x10000108 A data type property of NETWORK to represent a frequency band in KHz. 0x10000109 An object property of NETWORK to contain an IP_CONFIG class object. 1 A class to represent IP configuration information. A data type property of IP_CONFIG to represent IP configuration methods. The following values are assigned: Taniuchi, et al. Expires May 6, 2009 [Page 23] Internet-Draft IEEE 802.21 Basic Schema November 2008 Bit 0: IPv4 static configuration Bit 1: IPv4 dynamic configuration (DHCPv4) Bit 2: Mobile IPv4 with foreign agent care-of address (FA-CoA) Bit 3: Mobile IPv4 without FA (Co-located CoA) Bits 4-10: reserved for IPv4 address configurations Bit 11: IPv6 stateless address configuration Bit 12: IPv6 stateful address configuration (DHCPv6) Bit 13: IPv6 manual configuration Bits 14-31: (Reserved) An object property of IP_CONFIG to contain a TRANSPORT_ADDR class object for an IP address of a candidate DHCP Server. It is included only when the corresponding bit in ip_cfg_mthds for dynamic address configuration is set. An object property of IP_CONFIG to contain a TRANSPORT_ADDR class object for an IP address of a candidate Foreign Agent. It is included only when the corresponding bit in ip_cfg_mthds for Mobile IPv4 is set. An object property of IP_CONFIG to contain a TRANSPORT_ADDR class object for an IP address of an candidate Access Router. It is included only when the corresponding bit in ip_cfg_mthds for IPv6 Stateless configuration is set. Taniuchi, et al. Expires May 6, 2009 [Page 24] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x1000010A A data type property of NETWORK to represent network capabilities. Bit 0: Security - Indicates that some level of security is supported when set. Bit 1: QoS Class 0 - Indicates that QoS for class 0 is supported when set. Bit 2: QoS Class 1 - Indicates that QoS for class 1 is supported when set. Bit 3: QoS Class 2 - Indicates that QoS for class 2 is supported when set; Otherwise, no QoS for class 2 support is available. Bit 4: QoS Class 3 - Indicates that QoS for class 3 is supported when set; Otherwise, no QoS for class 3 support is available. Bit 5: QoS Class 4 - Indicates that QoS for class 4 is supported when set; Otherwise, no QoS for class 4 support is available. Bit 6: QoS Class 5 - Indicates that QoS for class 5 is supported when set; Otherwise, no QoS for class 5 support is available. Bit 7: Internet Access - Indicates that Internet access is supported when set; Otherwise, no Internet access support is available. Bit 8: Emergency Services - Indicates that some level of emergency services is supported when set; Otherwise, no emergency service support is available. Bit 9: MIH Capability - Indicates that MIH is supported when set; Otherwise, no MIH support is available. Bit 10-31: (Reserved) Taniuchi, et al. Expires May 6, 2009 [Page 25] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x1000010B A data type property of NETWORK to represent a location configuration protocol (LCP). 0: NULL 1: LLDP (Link Layer Discovery Protocol) 2: LbyR (Location by Reference) with LLDP 3-10: (Reserved) 11: LLDP-MED (Media Endpoint Discovery) 12: LbyR with LLDP-MED 13-20: (Reserved) 21: U-TDoA (Uplink Time Difference of Arrival) 22: D-TDoA (Differential Time Difference of Arrival) 23-30: (Reserved) 31: DHCP 32: LbyR with DHCP 33-40: (Reserved) 41: OMA (Open Mobile Alliance) SUPL (Secure User Plane Location) 42: IEEE 802.11 43: LbyR with IEEE 802.11 44-50: (Reserved) 51: HELD (HTTP Enabled Location Delivery) 52: LbyR with HELD 53-255: (Reserved) 0x1000010C A data type property of NETWORK to represent information on supported mobility management protocols. The following values are assigned. Bit 0: Mobile IPv4 (IETF RFC 3344) When this bit is set, it indicates the network has a Mobile IPv4 Home Agent. Taniuchi, et al. Expires May 6, 2009 [Page 26] Internet-Draft IEEE 802.21 Basic Schema November 2008 Bit 1: Mobile IPv4 Regional Registration (IETF RFC 4857) When this bit is set, it indicates the network has a Gateway Foreign Agent (GFA) and supports Mobile IPv4 Regional Registration. Bit 2: Mobile IPv6 (IETF RFC 3775) When this bit is set, it indicates the network has a Mobile IPv6 Home Agent. Bit 3: Hierarchical Mobile IPv6 (IETF RFC 4140) When this bit is set, it indicates the network has a Mobile IPv6 Mobile Anchor Point (MAP). Bit 4: Low Latency Handoffs (IETF RFC 4881) When this bit is set, it indicates the network supports Mobile IPv4 fast handover. Bit 5: Mobile IPv6 Fast Handovers (IETF RFC 5268) When this bit is set, it indicates the network supports Mobile IPv6 fast handover. Bit 6: IKEv2 Mobility and Multihoming Protocol (IETF RFC 4555) When this bit is set, it indicates the network has a node that supports MOBIKE. Bit 7-15: (Reserved) 0x1000010D An object property of NETWORK to contain a PROXY_ADDR class object for the proxy providing access to public safety answering point (PSAP). Taniuchi, et al. Expires May 6, 2009 [Page 27] Internet-Draft IEEE 802.21 Basic Schema November 2008 A class to represent an L3 address of a proxy. An object property of PROXY_ADDR to contain a TRANSPORT_ADDR class object for an IP address of a proxy. A data type property of PROXY_ADDR to represent an FQDN of a proxy. 0x1000010E An object property of NETWORK to contain a PROXY_ADDR class object for a 3GPP Proxy Call Session Control Function (P-CSCF). 0x1000010F Taniuchi, et al. Expires May 6, 2009 [Page 28] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of NETWORK to represent whether the access network itself is mobile. 0x10000302 An object property of NETWORK to contain a POA class object. 1 1 1 1 Taniuchi, et al. Expires May 6, 2009 [Page 29] Internet-Draft IEEE 802.21 Basic Schema November 2008 1 A class to represent all the information depicting a network point of attachment (PoA). 0x10000200 An object property of POA to contain a LINK_ADDR class object. A class to represent a link-layer address. An object property of LINK_ADDR to contain a TRANSPORT_ADDR class object for an IEEE 802 Media Access Control (MAC) address. A class to represent a 3GPP 3G PoA. Taniuchi, et al. Expires May 6, 2009 [Page 30] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of LINK_ADDR_3GPP_3G and LINK_ADDR_3GPP_2G to represent a 3GPP Public Land Mobile Network (PLMN) Identifier. The coding of PLMN Identifier is specified in 3GPP TS 23.003. A data type property of LINK_ADDR_3GPP_3G, LOCATION_CELL_ID and SIB to identify a cell uniquely within 3GPP UTRAN. It consists of radio network controller (RNC)-ID and C-ID as specified in 3GPP TS 25.401. A class to represent a 3GPP 2G PoA. A data type property of LINK_ADDR_3GPP_2G to represent a Location Area Code (LAC). A LAC is a fixed length code (of 2 octets) identifying a location area within a PLMN, as defined in 3GPP TS Taniuchi, et al. Expires May 6, 2009 [Page 31] Internet-Draft IEEE 802.21 Basic Schema November 2008 23.003. A data type property of LINK_ADDR_3GPP_2G to represent a Cell Identity (CI), as defined in 3GPP TS 23.003. A data type property of LINK_ADDR to represent a 3GPP transport address. This is an International Mobile Subscriber Identity (IMSI) or a Temporary Mobile Subscriber Identities (TMSI) defined in 3GPP TS 23.003. A data type property of LINK_ADDR to represent a 3GPP2 transport address. This is a Mobile Identification Number (MIN) defined in 3GPP2 C.S0005-D. A data type property of LINK_ADDR to represent a link layer address other than that is used for IEEE 802, 3GPP or 3GPP2. Taniuchi, et al. Expires May 6, 2009 [Page 32] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x10000201 An object property of POA to contain a LOCATION class object. A class to represent location information. A class to represent Location Configuration Information (LCI) defined in RFC 3825. A data type property of BIN_GEO_LOC to represent LaRes (latitude resolution) of LCI. See RFC 3825 for values and semantics. Taniuchi, et al. Expires May 6, 2009 [Page 33] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of BIN_GEO_LOC to represent Latitude of LCI. See RFC 3825 for values and semantics. A data type property of BIN_GEO_LOC to represent LoRes (longitude resolution) of LCI. See RFC 3825 for values and semantics. A data type property of BIN_GEO_LOC to represent Longitude of LCI. See RFC 3825 for values and semantics. A data type property of BIN_GEO_LOC to represent At (Altitude type) of LCI. See RFC 3825 for values and semantics. A data type property of BIN_GEO_LOC to represent AltRes (Altitude resolution) of LCI. See RFC 3825 for values and semantics. Taniuchi, et al. Expires May 6, 2009 [Page 34] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of BIN_GEO_LOC to represent Altitude of LCI. See RFC 3825 for values and semantics. A data type property of BIN_GEO_LOC to represent Datum of LCI. See RFC 3825 for values and semantics. A class to represent XML-formatted geospatial location information. A data type property of XML_GEO_LOC to represent Geo address elements as described in RFC 4119. Taniuchi, et al. Expires May 6, 2009 [Page 35] Internet-Draft IEEE 802.21 Basic Schema November 2008 A class to represent civic address equivalent to Civic Addresses Configuration Information defined in RFC 4676. A data type property of BIN_CIVIC_LOC to represent a two-letter ISO 3166-1 country code. An object property of CIVIC_ADDR to contain a CIVIC_ADDER class object. 1 1 A class to represent a civic address element defined in RFC 4676. Taniuchi, et al. Expires May 6, 2009 [Page 36] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of CIVIC_LOC to represent a CAtype (Civice Address type) of a civic address element. See RFC 4676 for values and semantics. A data type property of CIVIC_LOC to represent a CAvalue (Civic Address value) of a civic address element. See RFC 4676 for values and semantics. A class to represent XML-formatted civic address location information. A data type property of XML_CIVIC_LOC to represent XML-formatted civic address location information as described in RFC 4119. Taniuchi, et al. Expires May 6, 2009 [Page 37] Internet-Draft IEEE 802.21 Basic Schema November 2008 A class to represent a cell identifier as location information. information. 0x10000202 An object property of POA to contain a CH_RANGE class object. 1 1 A class to represent a channel range. Taniuchi, et al. Expires May 6, 2009 [Page 38] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of CH_RANGE to represent the lowest channel frequency in MHz. A data type property of CH_RANGE to represent the highest channel frequency in MHz. 0x10000203 An object property of POA to contain a SYSTEM_INFO class object. A class to represent system information. An object property of SYSTEM_INFO to contain a NETWORK_TYPE object. Taniuchi, et al. Expires May 6, 2009 [Page 39] Internet-Draft IEEE 802.21 Basic Schema November 2008 An object property of SYSTEM_INFO to contain a LINK_ADDR class object. An object property of SYSTEM_INFO to contain a PARAMETERS class object. A class to represent system information depending on the network type. A class to represent the downlink channel descriptor and the uplink channel descriptor in IEEE 802.16. A data type property of DCD_UCD to represent IEEE 802.16 base station identifier. Taniuchi, et al. Expires May 6, 2009 [Page 40] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of DCD_UCD to represent IEEE 802.16 channel bandwidth in kb/s. A data type property of DCD_UCD to represent an IEEE 802.16 Downlink/Uplink center frequency in KHz. A data type property of DCD_UCD to represent an IEEE 802.16 base station's effective isotropic radiated power level. A signed value of 8 bits in units of 1 dBm. A data type property of DCD_UCD to represent an IEEE 802.16 TTG - transmit/receive transition gap. Taniuchi, et al. Expires May 6, 2009 [Page 41] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of DCD_UCD to represent an IEEE 802.16 RTG - receive/transmit transition gap. A data type property of DCD_UCD to represent an IEEE 802.16 list of FEC Code Type for Downlink burst. See IEEE 802.16Rev2/D5.0. A data type property of DCD_UCD to represent an IEEE 802.16 list of FEC Code Type for Uplink burst. See IEEE 802.16Rev2/D5.0. A data type property of DCD_UCD to represent an IEEE 802.16 initial ranging code. See IEEE 802.16Rev2/D5.0. Taniuchi, et al. Expires May 6, 2009 [Page 42] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of DCD_UCD to represent an IEEE 802.16 handover ranging code. See IEEE 802.16Rev2/D5.0. A class to represent UMTS system information block (SIB). A data type property of SIB to represent UMTS scrambling code, cdma2000 Walsh code. A class to represent cdma2000 system parameters. A data type property of SYS_PARAMS to represent a cdma2000 base station identification as defined in 3GPP2 C.S0005-D. Taniuchi, et al. Expires May 6, 2009 [Page 43] Internet-Draft IEEE 802.21 Basic Schema November 2008 A data type property of SYS_PARAMS to represent a cdma2000 Pilot PN (Pseudo Noise) sequence offset index as defined in 3GPP2 C.S0005-D. A data type property of SYS_PARAMS to represent a cdma2000 carrier frequency identifier as defined in 3GPP2 C.S0002-D. A data type property of SYS_PARAMS to represent a cdma2000 band class as defined in 3GPP2 C.S0005-D. 0x10000204 An object property of POA to contain an IP_SUBNET_INFO class object. It is possible to include multiple ie_poa_subnet_info object properties in a single POA class object. Taniuchi, et al. Expires May 6, 2009 [Page 44] Internet-Draft IEEE 802.21 Basic Schema November 2008 1 1 A class to represent an IP subnet information. An MIIS server may advertise different IP subnets to different MIIS clients. A data type property of IP_SUBNET_INFO to represent 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. An object property of IP_SUBNET_INFO to contain a TRANSPORT_ADDR class object for an IP subnet address of the PoA encoded as Address base type defined in RFC3588. The first 2-octet contains AddressType, which may be either 1 (IPv4) or 2 (IPv6). If AddressType==1, the subnet_address property contains a 4-octet IPv4 address. If AddressType==2, the subnet_address property contains a 16-octet IPv6 address. Taniuchi, et al. Expires May 6, 2009 [Page 45] Internet-Draft IEEE 802.21 Basic Schema November 2008 0x10000205 An object property of POA to contain a TRANSPORT_ADDR class object for a non-link-local IP address of the PoA encoded as Address base type defined in RFC3588. The first 2-octet contains AddressType, which may be either 1 (IPv4) or 2 (IPv6). If AddressType==1, the subnet_address property contains a 4-octet IPv4 address. If AddressType==2, the subnet_address property contains a 16-octet IPv6 address. It is possible to include multiple ie_poa_ip_addr object properties (i.e., multiple TRANSPORT_ADDR class objects each carrying an IP address) in a single POA class object. 1 1 A class to represent a transport address. A data type property of TRANSPORT_ADDR to represent an Address Family defined in Taniuchi, et al. Expires May 6, 2009 [Page 46] Internet-Draft IEEE 802.21 Basic Schema November 2008 http://www.iana.org/assignments/address-family-numbers. A data type property of TRANSPORT_ADDR to represent an an address value specific to address_family. Taniuchi, et al. Expires May 6, 2009 [Page 47] Internet-Draft IEEE 802.21 Basic Schema November 2008 4. 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 May 6, 2009 [Page 48] Internet-Draft IEEE 802.21 Basic Schema November 2008 5. 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 5305 Email: yohba@tari.toshiba.com XML The exact XML to be stored in the registry is described in Section 3, except that the word "URL_TO_BE_ASSIGNED" in the XML definition needs to be replaced with IANA-assigned URL for the stored XML. Taniuchi, et al. Expires May 6, 2009 [Page 49] Internet-Draft IEEE 802.21 Basic Schema November 2008 6. Acknowledgments We would like to thank IEEE 802.21 Working Group members and Jari Arkko for their detailed review of the 802.21 basic schema. Taniuchi, et al. Expires May 6, 2009 [Page 50] Internet-Draft IEEE 802.21 Basic Schema November 2008 7. References 7.1. Normative References [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. Arkko, "Diameter Base Protocol", RFC 3588, September 2003. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC3825] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information", RFC 3825, July 2004. [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object Format", RFC 4119, December 2005. [RFC4676] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information", RFC 4676, October 2006. [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. [UNICODE-XML] W3C Recommendation, "Unicode in XML and other Markup Languages (http://www.w3.org/TR/unicode-xml/)", May 2007. [ISO3166-1] International Organization for Standardization (ISO), "Codes for the representation of names of countries and their subdivisions - Part 1: Country codes". [ISO4217] International Organization for Standardizations (ISO), "Codes for the Representation of Names of Countries". [802.21] Institute of Electrical and Electronics Engineers, "Draft IEEE Standard for Local and Metropolitan Area Networks: Media Independent Handover Services", IEEE P802.21/D14, 2008. [802.11k] Institute of Electrical and Electronics Engineers, "IEEE Std 802.11k-2008, Information Technology - Taniuchi, et al. Expires May 6, 2009 [Page 51] Internet-Draft IEEE 802.21 Basic Schema November 2008 Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications; Amendment 1: Radio Resource Measurement of Wireless LANs.", IEEE Standard 802.11k-2008, 2008. [802.16] Institute of Electrical and Electronics Engineers, "IEEE Std 802.16-2004, Information Technology- Telecommunications and information exchange between system-Local and metropolitan area networks-Specific Requirements-Part 16: Air Interface for Fixed Broadband Wireless Access Systems.", IEEE Standard 802.16-2004, 2004. [802.16Rev2] Institute of Electrical and Electronics Engineers, "DRAFT Standard for Local and metropolitan area networks Part 16: Air Interface for Broadband Wireless Access Systems", IEEE P802.16Rev2/D5, 2008. [3GPP-TS23003] 3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification", 3GPP TS 23.003. [3GPP-TS25401] 3GPP, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN overall description", 3GPP TS 25.401. [3GPP-TS25413] 3GPP, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface RANAP signalling", 3GPP TS 25.413. [3GPP2-CS0002-D] 3GPP2, "Physical Layer Standard for cdma2000 Spread Spectrum Systems Revision D", 3GPP2 C.S0002-D. [3GPP2-CS0005-D] 3GPP2, "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems Release D", 3GPP2 C.S0005-D. [GSM] GSM Association, "TADIG Naming Conventions, Version 4.1", GSM Association TD.13. Taniuchi, et al. Expires May 6, 2009 [Page 52] Internet-Draft IEEE 802.21 Basic Schema November 2008 [E212] ITU Telecommunication Standardization Sector, "The international identification plan for mobile terminals and mobile users, ITU-T Recommendation E.212", ITU-T E.212. 7.2. Informative References [RFC3344] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August 2002. [RFC3755] Weiler, S., "Legacy Resolver Compatibility for Delegation Signer (DS)", RFC 3755, May 2004. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC4140] Soliman, H., Castelluccia, C., El Malki, K., and L. Bellier, "Hierarchical Mobile IPv6 Mobility Management (HMIPv6)", RFC 4140, August 2005. [RFC4555] Eronen, P., "IKEv2 Mobility and Multihoming Protocol (MOBIKE)", RFC 4555, June 2006. [RFC4881] El Malki, K., "Low-Latency Handoffs in Mobile IPv4", RFC 4881, June 2007. [RFC5268] Koodli, R., "Mobile IPv6 Fast Handovers", RFC 5268, June 2008. [I-D.ietf-geopriv-http-location-delivery] Barnes, M., Winterbottom, J., Thomson, M., and B. Stark, "HTTP Enabled Location Delivery (HELD)", draft-ietf-geopriv-http-location-delivery-10 (work in progress), October 2008. [I-D.ietf-geopriv-radius-lo] Tschofenig, H., Adrangi, F., Jones, M., Lior, A., and B. Aboba, "Carrying Location Objects in RADIUS and Diameter", draft-ietf-geopriv-radius-lo-19 (work in progress), January 2008. [802.1AB] Institute of Electrical and Electronics Engineers, "IEEE Standard for Local and metropolitan area networks Station and Media Access Control Connectivity Discovery", IEEE Standard 802.1AB-2005, 2005. [LLDP-MED] Telecommunications Industry Association, "Link Layer Taniuchi, et al. Expires May 6, 2009 [Page 53] Internet-Draft IEEE 802.21 Basic Schema November 2008 Discovery Protocol for Media Endpoint Devices", TIA 1057, 2006. Taniuchi, et al. Expires May 6, 2009 [Page 54] Internet-Draft IEEE 802.21 Basic Schema November 2008 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 May 6, 2009 [Page 55] Internet-Draft IEEE 802.21 Basic Schema November 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). 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. Taniuchi, et al. Expires May 6, 2009 [Page 56]