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.23 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 Home appliances information model and mapping Recommendation ITU-T Y.4500.23 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS, NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMA
3、RT CITIES GLOBAL INFORMATION INFRASTRUCTURE 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 Performa
4、nces Y.800Y.899 INTERNET PROTOCOL 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.
5、1600Y.1699 Operation, administration 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 arc
6、hitecture Y.2200Y.2249 Service aspects: 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 mobilit
7、y Y.2800Y.2899 Carrier grade open 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, connectivit
8、y and networks Y.4250Y.4399 Frameworks, 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,
9、please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.4500.23 (03/2018) i Recommendation ITU-T Y.4500.23 oneM2M Home appliances information model and mapping Summary Recommendation ITU-T Y.4500.23 describes the oneM2M defined information model for home appliances, including the description
10、 of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T Y.4500.23 2018-03-01 20 11.1002/1000/13513 Keywords Home appliance information
11、 model, oneM2M, ontology, resource mapping. * 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, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Y.4500.23 (03/2018) FOREWORD The
12、International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technica
13、l, 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 meets every four years, establishes the topics for study by the ITU-T study groups which, in
14、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 purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. N
15、OTE 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 voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure
16、, 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“ and the negative equivalents are used to express requirements. The use of such words does n
17、ot 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 involve the use of a claimed Intellectual Property Right. ITU takes no position concerning th
18、e 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 Recommendation, ITU had not received notice of intellectual property, protected by patents, w
19、hich 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 at http:/www.itu.int/ITU-T/ipr/. NOTE The structure of this Recommendation departs slightl
20、y 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, without the prior written permission of ITU. Rec. ITU-T Y.4500.23 (03/2018)
21、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 1 5 Conventions 2 6 Home appliance information model . 2 6.1 Introduction 2 6.2 Design principle of the home appliance informatio
22、n model 3 6.3 ModuleClasses . 4 6.4 Device models 19 6.5 Enumeration type definitions . 24 6.6 Universal and common properties for device models 28 7 The principle of resource mapping for home appliance information model 30 7.1 Introduction 30 7.2 The resource mapping rules . 30 7.3 Short names 31 7
23、.4 containerDefinition values . 38 7.5 XSD definitions 40 8 Mapping with other information models from external organizations . 43 9 Ontology for the home appliance information model aligned with oneM2M base ontology 43 Annex A oneM2M specification update and maintenance control procedure . 45 Appen
24、dix I Resource mapping examples . 46 I.1 Introduction 46 I.2 Example for device model deviceAirConditioner 46 I.3 Example of ModuleClass binarySwitch . 50 I.4 Example of Action toggle . 52 Bibliography 54 Rec. ITU-T Y.4500.23 (03/2018) 1 Recommendation ITU-T Y.4500.23 oneM2M Home appliances informat
25、ion model and mapping 1 Scope This Recommendation describes the oneM2M defined information model for home appliances, including the description of how it is mapped with other information models from external organizations. It also explains the ontology for the home domain information model. The Reco
26、mmendation contains oneM2M Release 2 specification - oneM2M Home Appliances Information Model and Mapping V2.0.0 and is equivalent to standards of oneM2M partners including ARIB, ATIS b-ATIS.oneM2M.TS0023, CCSA b-CCSA M2M-TS-0023, ETSI ETSI TS 118 123, TIA, TSDSI b-TSDSI STD T1.oneM2M TS-0023, TTA b
27、-TTAT.MM-TS.0023 v2.0.0 and TTC b-TTC TS-M2M-0023. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommen
28、dations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly pu
29、blished. 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.1 Recommendation ITU-T Y.4500.1 (2018), oneM2M Functional architecture. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the fol
30、lowing terms defined elsewhere: 3.1.1 application entity(AE) b-ITU-T Y.4500.11: Represents an instantiation of application logic for end-to-end M2M solutions. 3.1.2 common services entity (CSE) b-ITU-T Y.4500.11: Represents an instantiation of a set of common service functions of the M2M environment
31、s. 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 Device Class ID: URN to identify the device model definition. 3.2.2 ModuleClass ID: URN to identify the ModuleClass model
32、definition. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AE Application Entity CSE Common Services Entity HEMS Home Energy Management System 2 Rec. ITU-T Y.4500.23 (03/2018) IPE Interworking Proxy application Entity M2M Machine to Machine RGB Red, G
33、reen and Blue (Colour mode) SDT Smart Device Template URN Uniform Resource Name 5 Conventions The key words “Shall“, “Shall not“, “May“, “Need not“, “Should“, “Should not“ in the present document are to be interpreted as described: Shall/Shall not: Requirements 1) effect on Standard: Standard needs
34、to describe the required feature (i.e., specify a technical solution for the Requirement); 2. effect on products: every implementation (M2M Solution that complies to this Standard) must support it; 3) effect on deployments: every deployment (M2M Service based on this Standard) must use the Standardi
35、zed feature where applicable otherwise e.g., interoperability problems with other services could arise. Should/Should not Recommendation 1) effect on Standard: Standard needs to describe a solution that allows the presence and the absence of the feature; 2) effect on products: an implementation may
36、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 Standard: Standard needs to describe a solution that allows the presence and the absence of the required fea
37、ture; 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 Home appliance information model 6.1 Introduction The present document intends to provide the unified means in the oneM2M system by defining a home appliance info
38、rmation model for the home domain devices such as TV, refrigerator, air conditioner, clothes washer, oven and robot cleaner. For the reasons of interworking with external technologies and efficiency, the principle of the home appliance information model is designed based on HGI SDT 3.0 b-HGI SDT. Th
39、e principle of defining the home appliance information model is introduced in clause 6.2. ModuleClasses which oneM2M systems support are explained in clause 6.3. In the subsequent clause 6.4, device models are defined. Rec. ITU-T Y.4500.23 (03/2018) 3 6.2 Design principle of the home appliance infor
40、mation model 6.2.1 Basic design principle of information modelling The design principle of the oneM2M abstract information model of home appliances, is to use smart device template (SDT) 3.0 as introduced in oneM2M TR-0017 b-oneM2M TR-0017. Note that those terms starting with a capital letter in thi
41、s clause are SDT terms and are explained in b-HGI SDT. Domain is a unique name which acts like a namespace (e.g., “org.oneM2M.home.modules“). It is set by the organization creating the SDT, allowing reference to a package of definitions for the contained ModuleClasses and device models. ModuleClasse
42、s specify a single service (e.g., audioVolume, powerOn/Off) with one or more Actions, Properties, DataPoints and Events. Each service which is described as a ModuleClass can be re-used in many Devices. Device model is a physical, addressable, identifiable appliance, sensor and actuator with one or m
43、ore Modules, Properties and SubDevices. SubDevice is a device which may be embedded in a Device and/or is addressed via another Device. Module is an instantiation of a ModuleClass for a specific Device or SubDevice. Figure 6.2.1-1 depicts the basic structure of SDT 3.0. Figure 6.2.1-1 Design structu
44、re of the home appliance information model using SDT 3.0 6.2.2 Description rules for Module Classes and device models When the Home Appliance Information Model is described based on SDT, the following rules shall be applied: Rule 1: CamelCase rule: When naming each element, lowerCamelCase shall be u
45、sed. Rule 2: Rule for description of Action, DataPoint: DataPoint shall be used to represent stateless operations. (e.g., powerState of binarySwitch for on/off operations). Action shall be used when describing stateful condition, handling unknown internal state conditions (e.g., upVolume/downVolume
46、by increasing/decreasing the audioVolume in steps, handling transactional procedures, or checking integrity using username plus password at the same time). Rule 3: Rule for description of DataPoint and Property: 4 Rec. ITU-T Y.4500.23 (03/2018) Non-functional information shall be described as a Prop
47、erty. Functional information shall be described as a DataPoint. (E.g., non-functional information: version, id; functional information: targetTemperature, targetVolume). Rule 4: Definition of the Domain: The Domain, in the case of the home appliance information model, is specified as “org.onem2m.hom
48、e“. The sub-domain for Device and ModuleClass shall be specified as “org.onem2m.home.devices“ and “org.onem2m.home.moduleclasses“ respectively. Rule 5: Naming rule for the element: the name of each element should be concise and avoid repeating its parent element name; but it may include the name of
49、its parent element for readability (e.g., lightDimmerUp, lightDimmerDown under lightDimmer). Rule 6: Criteria for marking elements as optional or mandatory: An element shall only be defined as mandatory if its foreseen to be universally mandatory to all implementing technologies. Rule 7: Enumeration type: When describing the meaning of values for enumeration type elements, they may be described in another clause. The enumeration types for hom
