1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Y.4500.12 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2018) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet of things an
2、d smart cities and communities Frameworks, architectures and protocols oneM2M base ontology Recommendation ITU-T Y.4500.12 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INF
3、RASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCO
4、L ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administra
5、tion and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 IPTV over NGN Y.1900Y.1999 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service a
6、spects: Interoperability of services and networks in NGN Y.2250Y.2299 Enhancements to NGN Y.2300Y.2399 Network management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Packet-based Networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade ope
7、n environment Y.2900Y.2999 FUTURE NETWORKS Y.3000Y.3499 CLOUD COMPUTING Y.3500Y.3999 INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Y.4000Y.4049 Definitions and terminologies Y.4050Y.4099 Requirements and use cases Y.4100Y.4249 Infrastructure, connectivity and networks Y.4250Y.4399 Fram
8、eworks, architectures and protocols Y.4400Y.4549 Services, applications, computation and data processing Y.4550Y.4699 Management, control and performance Y.4700Y.4799 Identification and security Y.4800Y.4899 Evaluation and assessment Y.4900Y.4999 For further details, please refer to the list of ITU-
9、T Recommendations. Rec. ITU-T Y.4500.12 (03/2018) i Recommendation ITU-T Y.4500.12 oneM2M base ontology Summary Recommendation ITU-T Y.4500.12 provides normative and informative specifications for the oneM2M base ontology and its instantiation into oneM2M resources. History Edition Recommendation Ap
10、proval Study Group Unique ID* 1.0 ITU-T Y.4500.12 2018-03-01 20 11.1002/1000/13507 Keywords Interworking, ontology, oneM2M, semantics. * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example,
11、http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.4500.12 (03/2018) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardiza
12、tion Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which me
13、ets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts
14、 purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is
15、 voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“
16、and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may in
17、volve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Re
18、commendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database
19、 at http:/www.itu.int/ITU-T/ipr/. NOTE This Recommendation departs slightly from the usual editorial style of ITU-T Recommendations to preserve existing cross-referencing from external documents. ITU 2018 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, wi
20、thout the prior written permission of ITU. Rec. ITU-T Y.4500.12 (03/2018) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 1 4 Abbreviations and acronyms 2 5 Conventions 3 6 General information on the one
21、M2M base ontology 3 6.1 Motivation and intended use of the ontology . 3 6.2 Insights into base ontology . 8 7 Description of classes and properties . 13 7.1 Classes 13 7.2 Object properties 38 7.3 Data Properties . 42 7.4 Annotation properties . 47 8 Instantiation of the base ontology and external o
22、ntologies to the oneM2M system 48 8.1 Instantiation rules for the base ontology 48 8.2 Common mapping principles between the base ontology and external ontologies . 55 9 Functional specification of communication with the generic interworking IPE 56 9.1 Usage of oneM2M resources for IPE communication
23、 . 56 9.2 Specification of the IPE for generic interworking 58 9.3 Specification of the behaviour of a communicating entity in message flows between IPE and the communicating entity . 61 10 FlexContainer specializations for generic interworking . 64 10.1 Introduction 64 10.2 Resource Type genericInt
24、erworkingService 64 10.3 Resource Type genericInterworkingOperationInstance . 68 Annex A oneM2M specification update and maintenance control procedure 74 Annex B OWL representation of base ontology . 75 Appendix I Mappings of selected external ontologies to the base ontology 76 I.1 Mapping of SAREF
25、76 Bibliography. 86 Rec. ITU-T Y.4500.12 (03/2018) 1 Recommendation ITU-T Y.4500.12 oneM2M base ontology 1 Scope This Recommendation specifies the oneM2M base ontology. This Recommendation also specifies an instantiation of the base ontology in oneM2M resources that is required for generic interwork
26、ing. In addition this Recommendation contains the functional specification for an interworking proxy entity (IPE), the oneM2M resources and their usage for generic interworking. The Recommendation contains oneM2M Release 2 specification oneM2M base ontology V2.0.0 and is equivalent to standards of o
27、neM2M partners including ARIB, ATIS b-ATIS.oneM2M.TS0012, CCSA b-CCSA M2M-TS-0012, ETSI b-ETSI TS 118 112, TIA, TSDSI b-TSDSI STD T1.oneM2M TS-0012, TTA b-TTAT.MM-TS.0012 and TTC b-TTC TS-M2M-0012. 2 References The following ITU-T Recommendations and other references contain provisions which, throug
28、h reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying th
29、e most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T Y.4500
30、.1 Recommendation ITU-T Y.4500.1 (2018), oneM2M Functional architecture. ITU-T Y.4500.11 Recommendation ITU-T Y.4500.11 (2018), oneM2M Common terminology. 3 Definitions 3.1 Terms defined elsewhere For the purposes of this Recommendation, the terms and definitions given in oneM2M TS-0011 ITU Y.4500.1
31、1 apply. This Recommendation uses the following terms defined elsewhere: 3.1.1 application entity ITU Y.4500.11: Represents an instantiation of application logic for end-to-end M2M solutions. 3.1.2 common services entity (CSE) ITU Y.4500.11: Represents an instantiation of a set of common service fun
32、ctions of the M2M environments. Such service functions are exposed to other entities through reference points. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 annotation property: Property that can be used to add information (metadata or data about dat
33、a) to classes, individuals and Object/Data properties. 2 Rec. ITU-T Y.4500.12 (03/2018) 3.2.2 concept: Entity of an ontology that has an agreed, well-defined, meaning within the domain of interest of that ontology. NOTE 1 A concept conceptually groups a set of individuals. NOTE 2 Concepts are called
34、 “classes“ as used in web ontology language (OWL) standard ontology language from the World Wide Web Consortium (W3C) (see b-OWL). 3.2.3 data property: Property that relates an individual of a class to data of a specified type and range. 3.2.4 generic interworking: Interworking with many types of no
35、n-oneM2M area networks and devices that are described in the form of a oneM2M compliant ontology that is derived from the oneM2M base ontology. NOTE Generic interworking supports the interworking variant “full mapping of the semantic of the non-oneM2M data model to Mca“ as indicated in clause F.2 of
36、 oneM2M TS-0001 ITU-T Y.4500.1. 3.2.5 interworked device: Non-oneM2M device (NoDN) for which communication with oneM2M entities can be achieved via an interworking proxy entity (IPE). 3.2.6 object property: Property that relates an individual of a domain class to an individual of a range class. 3.2.
37、7 ontology: Formal specification of a conceptualization, i.e., defining concepts as objects with their properties and relationships versus other concepts. 3.2.8 property: In web ontology language (OWL) standard ontology language, a property represents relations among individuals. NOTE Properties can
38、 be subcategorized as object properties, data properties and annotation properties. 3.2.9 proxied device: Virtual device i.e., a set of oneM2M resources together with an interworking proxy entity (IPE) that represents the interworked device in the oneM2M system. 3.2.10 relation; interrelation): Stat
39、ing a relationship among individuals. 3.2.11 restriction: Describes a class of individuals based on the relationships that members of the class participate in. NOTE Restrictions can be subcategorized as: existential restrictions, universal restrictions, cardinality restrictions and has value restric
40、tions. 4 Abbreviations and acronyms For the purposes of this Recommendation, the abbreviations given in oneM2M TS-0011 ITU-T Y.4500.11 and the following apply: AE Application Entity CRUD Create-Read-Update-Delete CSE Common Services Entity IPE Interworking Proxy Entity IRI Internationalized Resource
41、 Identifier MAC Media Access Control NoDN Non-oneM2M Device OWL Web Ontology Language OWL-DL Web Ontology Language-Description Logic RDF Resource Description Framework Rec. ITU-T Y.4500.12 (03/2018) 3 RPC Remote Procedure Call SAREF Smart Appliances Reference SPARQL SPARQL Protocol and RDF Query Lan
42、guage URI Uniform Resource Identifier 5 Conventions The keywords “shall“, “shall not“, “may“, “need not“, “should“, “should not“ in this Recommendation are to be interpreted as described: Shall/shall not: Requirements 1) effect on this Recommendation: This Recommendation needs to describe the requir
43、ed feature (i.e., specify a technical solution for the requirement); 2) effect on products: every implementation (M2M solution that complies with this Recommendation) must support it; 3) effect on deployments: every deployment (M2M service based on this Recommendation) must use the standardized feat
44、ure where applicable otherwise, interoperability problems with other services could arise, for example. Should/should not: Recommendation 1) effect on this Recommendation: This Recommendation needs to describe a solution that allows the presence and the absence of the feature; 2) effect on products:
45、 an implementation may or may not support it; however, support is recommended; 3) effect on deployments: a deployment may or may not use it; however, usage is recommended. May/need not: Permission/option 1) effect on this Recommendation: This Recommendation needs to describe a solution that allows t
46、he presence and the absence of the required feature; 2) effect on products: an implementation may or may not support it; 3) effect on deployments: A deployment may or may not use it. 6 General information on the oneM2M base ontology 6.1 Motivation and intended use of the ontology 6.1.1 Why use ontol
47、ogies in oneM2M? 6.1.1.1 Introduction to ontologies In a nutshell, an ontology is a vocabulary with a structure. The vocabulary applies to a certain domain of interest (e.g., metering, appliances, medicine) and it contains concepts that are used within that domain of interest, similar to the terms d
48、efined in clause 3. An ontology should: capture a shared understanding of a domain of interest; provide a formal and machine interpretable model of the domain. 4 Rec. ITU-T Y.4500.12 (03/2018) The ontology lists and denominates those concepts that have agreed, well-defined, meanings within the domai
49、n of interest e.g., the concept of “device“ has an agreed, well-defined, meaning within the scope of the smart appliances reference (SAREF) ontology see b-SAREFa. Example 1 follows of how external ontologies can be mapped to the base ontology. Example 1 uses the SAREF ontology b-SAREFa. Concepts do not identify individuals, but classes of individuals. Therefore, in the OWL standard ontology language from the World Wide Web Consortium (W3C) (see b-OWL), concepts
