1、EN50090-6-2June2025EuropeanstandardNormeeuropeenneEuropaischenormICS97.120;35.240.67SupersedesEN50090-6-2:2021EnglishVersionHomeandBuildingElectronicSystems(HBES)-Part6-2:IoTSemanticOntologymodeldescriptionSystemeselectroniquespourIesfoyersdomestiquesetIesElektrischeSystemtechnikfurHeimundGebaude(ES
2、HG)-batimerits(HBES)-Partie6-2:DescriptiondumodeleTeil6-2:BeschreibungdesIoTSemantischenontologieSemantiqueIoTOntologiemodellsThisEuropeanStandardwasapprovedbyCENELECon2025-05-12.CENELECmembersareboundtocomplywiththeCEN/CENELECInternalRegulationswhichstipulatetheconditionsforgivingthisEuropeanStanda
3、rdthestatusofanationalstandardwithoutanyalteration.Up-to-datelistsandbibliographicalreferencesconcerningsuchnationalstandardsmaybeobtainedonapplicationtotheCEN-CENELECManagementCentreortoanyCENELECmember.ThisEuropeanStandardexistsinthreeofficialversions(English,French,German).Aversioninanyotherlangu
4、agemadebytranslationundertheresponsibilityofaCENELECmemberintoitsownlanguageandnotifiedtotheCEN-CENELECManagementCentrehasthesamestatusastheofficialversions.CENELECmembersarethenationalelectrotechnicalcommitteesofAustria,Belgium,Bulgaria,Croatia,Cyprus,theCzechRepublic,Denmark,Estonia,Finland,France
5、Germany,Greece,Hungary,Iceland,Ireland,Italy,Latvia,Lithuania,Luxembourg,Malta,theNetherlands,Norway,Poland,Portugal,RepublicofNorthMacedonia,Romania,Serbia,Slovakia,Slovenia,Spain,Sweden,Switzerland,TurkiyeandtheUnitedKingdom.CENELECEuropeanCommitteeforElectrotechnicalStandardizationComiteEuropeen
6、deNormalisationElectrotechniqueEuropaischesKomiteeflirElektrotechnischeNormungCEN-CENELECManagementCentre:RuedeIaScience23,B-1040Brussels2025CENELECAllrightsofexploitationinanyformandbyanymeansreservedworldwideforCENELECMembers.ContentsPageEuropeanforeword31 Scope42 Normativereferences43 Terms5defin
7、itionsandabbreviations43.1 Termsanddefinitions43.2 Abbreviations104 HBESInformationModel114.1 Introduction114.1.1 General113/.5.6JJJJ24.4.4.4.4.TaxonomyVersioningAvailabilityIRIsandNamespacesSemanticDictionary.13,161617,18.123J2.3/J23J23J23/.5.6NNN33.3.3.3.44.4.4.4.55.5.5.5.66.s6.s6.6.44444444444444
8、44444444444ContentSemanticDictionaryVersioning:CoreModel:Introduction2Classes:Relations;Examples-LocationModelIIntroductionClasses，RelationsJExamplesTagModelIntroductionCardinalitiesIClassesIRelations7HBESModelIIntroductionEIRISchemeIURNSchemeIClassesI123J222255.5.5.5.5.Relations101Examples107Append
9、ix113SemanticExport113Examples117General117RoomTemperatureControl118LightSwitchControl123Bibliography128EuropeanforewordThisdocument(EN50090-6-2:2025)hasbeenpreparedbyCLC/TC205ttHomeandBuildingElectronicSystems(HBESf.Thefollowingdatesarefixed: latestdatebywhichthisdocumenthastobe(dop)2026-06-30imple
10、mentedatnationallevelbypublicationofanidenticalnationalstandardorbyendorsement latestdatebywhichthenationalstandards(dow)2028-06-30conflictingwiththisdocumenthavetobewithdrawnThisdocumentsupersedesEN50090-6-2:2021andallofitsamendmentsandcorrigenda(ifany).EN50090-6-2:2025includesthefollowingsignifica
11、nttechnicalchangeswithrespecttoEN50090-6-2:2021:certainHBESconceptsweresplittohaveabetterdistinctionbetweendefinitionsandtheirtypes(e.g.datapoitsandtheirtypes);一improvedlinkingbetweendifferentconceptssuchasdevicesandapplicationfunctions;一copiesofexternalontologypartswereremovedfromtheHBESontologyand
12、replacedbyreferences.Attentionisdrawntothepossibilitythatsomeoftheelementsofthisdocumentmaybethesubjectofpatentrights.CENELECshallnotbeheldresponsibleforidentifyinganyorallsuchpatentrights.Anyfeedbackandquestionsonthisdocumentshouldbedirectedtotheusers,nationalcommittee.Acompletelistingofthesebodies
13、canbefoundontheCENELECwebsite.1 ScopeThisdocumentdefinestheHBESInformationModelandacorrespondingdataexchangeformatfortheHomeandBuildingHBESOpenCommunicationSystem.2 NormativereferencesThefollowingdocumentsarereferredtointhetextinsuchawaythatsomeoralloftheircontentconstitutesrequirementsofthisdocumen
14、t.Fordatedreferences,onlytheeditioncitedapplies.Forundatedreferences,thelatesteditionofthereferenceddocument(includinganyamendments)applies.EN50090-1:20115HomeandBuildingElectronicSystems(HBES)-Part1:StandardizationstructureEN50090-6-3:2023,HomeandBuildingElectronicSystems(HBES)-Part6-3:3rdPartyHBES
15、IoTAPI3 Terms5definitionsandabbreviations3.1 TermsanddefinitionsForthepurposesofthisdocument,thetermsanddefinitionsgiveninEN50090-1:2011andthefollowingapply.ISOandIECmaintainterminologicaldatabasesforuseinstandardizationatthefollowingaddresses:一IECElectropedia:availableathttps:WWW.electropedia.orQ/一
16、ISOOnlinebrowsingplatform:availableathttps:WWWjSOQrqobp .1.1actuatorpointperforminganactuation(executedbyaspecificprocedure,withanexpectedresult)thatchangesanInstallationstateduringRuntimeNote1toentry:一ThetermActuatorcanbemappedtososa:ActuatorintheSSNOntology. Thesubjectactuationcanbemappedtososa:Ac
17、tuationintheSSNOntology. Thesubjectprocedurecanbemappedtososa:ProcedureintheSSNOntology. Thesubjectresultcanbemappedtososa:ResultintheSSNOntology.3.1.2ApplicationFunctionuseofasetofFunctionstoachievethedesiredbehaviourofatechnicalsystem,typicallyusingacombinationofdevicesexchanginginformationviathei
18、rinputandoutputDatapointsNote1toentry:AnApplicationFunctionmaybesplitintoseveralFunctionalBlockswiththeirinputandoutputDatapointsthatarelogicallyconnectedtoeachother.TheFunctionalBlocksmaybelocatedinoneormoredevices.EXAMPLEApplicationFunctionsexamplesare,tdirectelectricalheating,electricalheatingwit
19、haccumulators，warmwaterheating,jfancoilair-conditioning.Note2toentry:TheApplicationFunctionandApplicationaremeanttobethesame.Reasontointroduceanaliastermistouseaclear(understandable)referencefromApplication/ApplicationFunctiontothecorrespondingKIMclass:ApplicationFunctionortotheFunctionintheManageme
20、ntClient.3.1.3aspectspecificperspectiveonasystemthatcontainsthingswithdifferentproperties,orreferencingmechanismtoorganizeKIMelementsinaspecificperspectiveEXAMPLEAFunctionPointisanexofficioAspectwithanimportantspecificperspective.ItisareferencingmechanismtoorganizetogetheralltoaFunctionPointinterope
21、ratingPoints(allGOslinkedtoaGA).3.1.4BIMBuildingInformationModeldigitalprocesstodescribeanddocumentabuildinginallitslifecyclephases,fromitsplanning,construction,operationuptoitsdemolition3.1.5channelcollectionofDatapointsofadevicethatarelogicallyrelatedtoeachothertypicallybyassociationwithahardwaref
22、eatureoraspecificfunctionofthatdeviceNote1toentry:TheseDatapointsmaybederivedfromoneormoredefinedFunctionalBlocksormaybeanexpansionaboveandbeyonddefinedFunctionalBlocksormaybeindependentofaFunctionalBlockifnoneisdefinedforthefunctionassociatedwiththeChannel.TheconceptofaChanneliswell-understoodbythe
23、marketparticipant,e.g.installers.3.1.6datapointlogicalinputentityofadeviceactingasrecipientofInstallationstatedata,whereasalogicaloutputofadeviceactsassourceofInstallationstatedataNote1toentry:IncaseofimplementationasaGroupObject,statedataarecommunicatedwiththeuseofFunctionPoints.Note2toentry:Theter
24、mDatapointisthecommonterm;tospecificallydenoteaDatapointavailableonanIoT3rdPartyAPI,thetermIoTDatapointisused.3.1.7devicephysicalelementthatispartofthenetworkNote1toentry:Itisaphysical,concreteobjectthatacustomercanbuy.3.1.8endpointentrypointtoaservice,aprocess,oraqueueortopicdestinationinservice-or
25、ientedarchitecture3.1.9FeatureofInterestFOIabstractionofareal-worldthing(phenomenon,equipment,person,event.)definedbyitsobservableoractuatablepropertiesNote1toentry:Incolloquialterms,aFOIisapropertycarrier.Note2toentry:ASensoroperatesonaFOIwithobservableproperties,anActuatorwithactuatableproperties.
26、Note3toentry:AFOIisnota,tclassification/typetagitself;theclassification/type5isaccomplishedwiththehelpoftags.Examplesaredefinedin4.5.1.4.3.1.10functionpartoftheintendedbehaviourofaFunctionalBlockinabuildingcontext3.1.11FunctionalBlockFBoneormoreFunctionsthatbelongtogetherandthatcannotbeseparatedacro
27、sstwodevicesbutbigenoughthatadevicewithonlyonesuchFunctionalBlockcouldbemarketedNote1toentry:AFunctionalBlockhasawell-definedblackboxbehaviour.3.1.12FunctionPointFPruntimesystemstateinformationofaspecificApplicationFunctionNote1toentry:SharedbyatleasttwoDatapoints.Note2toentry:Hasauniqueidentifierth
28、ataddressesagroupofcontrolledobjects.ThisidentifieriscalledaGroupAddress.EXAMPLEinlivingroomonoff,whereastheistheFunctionPointname3.1.13GroupAddressGAnumericalidentifierofaFunctionPoint3.1.14GroupCommunicationcommunicationmodelinwhichonesendercommunicatesinformationtooneandtypicallymorereceiversNote
29、1toentry:InIoT5thiscanberealizedbysimpleUDPcommunicationorbyusingamessagebrokersystemorother.3.1.15GroupObjectGOobjectwhichisforeseenforGroupCommunicationusingGroupAddress(es),whichmaybeaccessedviapoint-to-pointcommunicationwithoutanassignedGroupAddressandbecomingamemberofthatFunctionPointrepresente
30、dbytheGroupAddresswhenassignedGroupAddress3.1.16HBESInformationModelontologybasedmodelofHBESSystemrelevantparts,includingadditionalsemantic(dictionary)informationNote1toentry:ItismanagedbytheKNXAssociation,hencetheabbreviationKIM.3.1.17IndustryFoundationClassesIFCopenstandardtodescribeBIMdatainadigi
31、talwayNote1toentry:IFCdataandmodelsarespecifiedinISO16739-1.3.1.18installationassemblyofmaterialsandcomponents(devices)placedinpositiontoprovideaserviceNote1toentry:AnInstallationisadeployedsystem(e.g.HVACsystemorfireprotectionsystem)andconsistsofequipmentandFunctionsthatareusedforaparticularpurpose
32、Note2toentry:Inrelationtothistermcreateddatacorrelatestotheinstallationmodel,describedin4.2.SOURCE:ISO6707-1:2020,modified-added”(devices)andNotestoentry.3.1.19IoTDatapointEndpointatanIoT3rdPartyAPIthat:a) correspondstooneormoreFunctionPoints5suchasastatedatarepresentationofadiscretestateinabuildin
33、gcontext;andb) isafullyqualifiedURLe.g.providedbyanIoT3rclPartyServerEXAMPLE 1 brightnessdiscretestate,brightnessisrepresentedbythevalue65(percent)EXAMPLE 2 https:QateWaV.knx.localksxaaiv1datapointsld3.1.20IoTFunctionFunctionatanIoT3rdPartyAPIthat:isasacollectionofIoTDatapointsthatfulfilsa-bytheuser
34、intendedbehaviourEXAMPLElivingroom-rearlightdimming,jkitchen-floorheatingNote1toentry:InaMac,anIoTFunctionisinstantiateddataofaMaCFunctioninanInstallationrespectivelyMaCproject.TheMaCFunctionitselfmaybaseonanApplicationFunction.3.1.21IoT3rdPartyAPIsetofrequirementsandregulationsthroughwhichpartiala
35、ccesstoanInstallationcanbegainedbyofferingacollectionofEndpoints3.1.22IoT3rdPartyClientdeviceorserviceinteractingwiththeInstallationfromoutsideusingtheIoT3rcPartyAPINote1toentry:TheIoT3rdPartyClientconnectstoasingledevicethatprovidestheIoT3rdPartyAPIandcanusethissingledevicetofullyinteractwiththeIns
36、tallation,possiblydependingonaspecifiedauthorizationmechanism.EXAMPLE 1 Amobilephone(frominsidethenetwork,orfromanInternetconnection)withtypicallyshortperiodconnections.EXAMPLE 2 AweatherservicepermanentlyfeedinginitsweatherinformationusingtheIoT3rc*PartyAPI.3.1.23IoT3rdPartyServerdevicethatimplemen
37、tstheIoT3rcPartyAPINote1toentry:Thiscanbeadedicateddevice;thiscanbeafunctionofadevicethatsupportsotherHBESIoTandnonHBESfunctionalities;itmaybelocatedwithinthelocalLANoftheIoTinstallationoroutside.3.1.24MaCCatalogEntrycreatedmanagementclientdatacorrelatingtotheproductmodel,describedin4.23.1.25MaCFunc
38、tionApplicationFunctioncreatedbytheMaCandassignedtoabuildingstructureelement,groupingseveralGroupAddresses3.1.26MaCProjectprojectcreatedbyaMaCdocumentingtheConfigurationofanInstallation3.1.27ManagementClientMaCmeanstoconfigureandcommissionDevicesaswellastoplan,designanddiagnoseanentireInstallationNo
39、te1toentry:TheMaCisusedtoconfigureandcommissionDevices,aswellastoplan,designanddiagnoseanentireInstallation.AsafinalsteptheMaCwritesspecificconfigurationdatasuchasDeviceparameterstotheDevices.3.1.28ontologyconceptualdescriptionsofthingsthathaveareal-worldcommonalitysharingtheknowledgeofadomain,mainl
40、yexpressedwithOWLNote1toentry:Ontologiesareastructuredwaytodescribethemeaningofdatainontologyclassesandshouldnotbemixedupwithcommondatamodelstructures.3.1.29ObjectPropertyOP in0WLbuilt-inconceptthatconnectspairsofindividualsNote1toentry:Anobjectpropertyexpressionrepresentsthe(entire)relationshipbetw
41、eenthepairsofindividuals.3.1.30OWLOWL2WebOntologyLanguage3informallyOWL2,specifiedbytheWorldWideWebConSortiIJm(W3C),mainlyserializedwithXMLsyntaxforRDF(RDF/XML)Note1toentry:InthisspecificationtheabbreviationOWLisalwaysanexplicitreferencetoOWL2.3.1.31pointinterfacetodatainthesystemNote1toentry:Thisdo
42、cumentusesthetermPointasanumbrellafordatathatcanbeaccessedfromoutsideoftheDevice,forinstancetointeractwithotherPointsfromotherDevices.Consequently,termPointisagenericsupersetofthetermDatapoint(whichdescribesmorepreciselythetechnicshowthe,datainthesystemarestructuredand/orcoded).3.1.32PointAPIsimpleR
43、ESTfuI(CoAPorHTTP)applicationprogramminginterfacedesignedfor,butnotlimitedto,constrainedclass2devicesRFC7228supportingdeviceindividualization,devicelinkingandaccessingdeviceruntimedataEXAMPLEFunctionalBlockorChannelDatapoints.3.1.33QualityKindQKcertaincombinationofobservableoractuatableproperties,av
44、ailableaspredefinedpartsoftheSemanticDictionaryorcreatedindividuallyduringConfiguration,itbeingthecasewhenaQualityKindwiththeintendedcombinationofpropertiesrespectivelytagsisnot(yet)partofthedictionaryNote1toentry:AQKisnota,classification/typetagitself;the“classification/type“isaccomplishedwiththehe
45、lpoftags.Examplesaredefinedin4.5.1.4.3.1.34RDFResourceDescriptionFrameworkstandardmodelfordatainterchangeontheWebNote1toentry:RDFisspecifiedbythehttps:WWW.w3.orqRDFNote2toentry:RDFisaframeworktorepresentinformationinthewebbyusingtriples.TheinformationcanbeserializedandstoredinmanyformatssuchastheTUR
46、TLEorJSON(-LD)format.ThegeneralRDFconceptdescriptioncanbefoundunderhttps:WWW.w3.orq/TRrdf11-concepts/SOURCE:https:/www.w3.orq/RDF/,Notes1and2toentryadded.3.1.35runtimeprocess-to-processcommunicationofdatabetweendevices,opposingtoConfigurationNote1toentry:ThisconcernsmainlythecommunicationofDatapoint
47、values(controlandstatusinformation).3.1.36SemanticExportprojectexportedbytheMaCreflectinganInstallationinalinkeddataformatNote1toentry:Theexporteddataare: structuredaccordingtotheKIM,suchasusingObjectPropertiesdefinedinKIM; annotatedwithadditionalsemanticinformationfromtheSemanticDictionary; referencingconceptsofexternalOntologies.3.1.37semanticdictionarysetofstandardizedtermsallowingtoannotatereq
