《oneM2M-ARC-2013-0142R03-Pool_Mapping.docx》由会员分享，可在线阅读，更多相关《oneM2M-ARC-2013-0142R03-Pool_Mapping.docx（13页珍藏版）》请在课桌文档上搜索。
1、INPUTCONTRIBUTIONInitialrequirementssubsetGroupName:*JointREQ-ARC-WGsTitle:*PoolMappingofM2MSystemattributesSource:*Cisco,Huawei,TelecomItalia,ETRI,ILSTechnologyContact:LionelFlorit(IfIOritCiSC)forcontentrelatedtothiscontributionYiChen(Yi.chen)forcontentrelatedtoCCSAJYAhn(ahnjy(etri.re.kr)forcontent
2、relatedtoTTAEnricoScarrone(enrico.scarronetelecomitalia.it)forcontentrelatedtoETSIMihaiVoicu(mvoicu(5)andMitchTseng(mitch(T-)forcontentrelatedtoTIAYongjingZhang(ZhangyOngjing(5)forcontentrelatedtoCCSAandETSIDate:*2013-2-25Abstract:*Thepurposeofthiscontributionistomapthecontentrelatedtoarchitecturewh
3、ichhasbeencontributedbytype1partnersandiscurrentlydepositedintothepool.AgendaItem:*ArchitectureWorkitem(s):ARC1-0001tobeconfirmedDOCUmem(三)Impacted*TRnumbertbdIntendedpurposeofDecisiondocument:*区DiscussionInformationOtherDecisionrequestedorWGapprovalofinclusionintothearchitecturedraftTR(Part1:Analys
4、isofrecommendation:*architecturesproposedfortransfertooneM2M).?oneM2MIPRSTATEMENTParticipationin,orattendanceat,anyactivityofoneM2M,constitutesacceptanceofandagreementtobeboundbyallprovisionsofIPRpolicyoftheadmittingPartnerType1andpermissionthatallcommunicationsandstatements,oralorwritten,orotherinf
5、ormationdisclosedorpresented,andanytranslationorderivativethereof,maywithoutcompensation,andtotheextentsuchparticipantorattendeemaylegallyandfreelygrantsuchcopyrightrights,bedistributed,published,andpostedononeM2M,swebsite,inwholeorinpart,onanon-exclusivebasisbyoneM2MoroneM2MPartnersType1ortheirlice
6、nseesorassignees,orasoneM2MSCdirects.DISCLAIMERThisdocumenthasbeencreatedbythecompanieslistedonthiscontribution.Itdoesnotcontainmaterialtransferredbythetype1partners.Itisintendedtohelpthemembersnavigatethepool.Introduction2Overviewofthepool,scontent3Detailedreferences4Referencedocuments9CCSADocument
7、References10TTADocumentReferences13IntroductionThepurposeofthiscontributionistohelpmembersnavigatethecontentrelatedtoarchitecturewhichhasbeencontributedbypartnersandiscurrentlydepositedintothepool.Thegoalofthiscontributionistoprovidethefollowinginformation:- HelpmembersassessthelevelofadvancementofM
8、2Marchitecturecontributedbytypeonepartners- Classifybylogicalfunctionsthecontentsubmittedinthepoolatthetimeofthiscontribution- Indicatewhichpartnerisstillworkingonwhichtopic- GiveexposuretodocumentsnotwritteninEnglishTheATISM2Mfocusgrouphasproducedalistofitemspresentingataveryhighlevelthebuildingblo
9、cksofanM2Marchitecture(reftooeM2M-ARC-2012-0007R02).Werecognizethatthislistisnotexhaustiveandcompletebutitcanbeusedasawaytoorganizetheinformationcontributedbythepartners.BelowisatablewiththenamesforeachATISbuildingblockineachrow.ThedefinitionprovidedbyATISislocatedafterthetable.Alldocumentsmentioned
10、belowshouldbeavailableintheoeM2Mpooldirectoryftp:/ftp.onem2m.org/PoolorinotherdirectoriesononeM2M.orgOverviewofthepool,scontentTablenomenclature:wReqtsnmeansthereisrequirementsrelatedcontentinthepooluArchnmeansthereisarchitecturerelatedcontentinthepool*4Promeansthereisprotocolrelatedcontentinthepool
11、*4NocontemeansthatnorelatedcontenthasbeencontributedinthepooluWIPmeansthepartnerisworkingontherelatedtopicPartnerCCSATIATTAETSISubscriptionInformationHandlingArchNoContentArchandWIPReqts,Arch,ProtDeviceManagementArchArchWIPReqts,Arch,ProtSecurityReqts,Arch7WIPReqtS,Arch,ProtApplicationandDeviceRegis
12、trationsArchandWIPArchWIPReqts,Arch,ProtResourceManagementArchandWlPArchArchandWIPReqts,Arch,ProtContentpush/pullServicesReqtsArchNocontentReqts,Arch,ProtStoreandForwardMessagingArchandWIPArchNocontentReqts,Arch,ProtProtocolTranslation(binding)NocontentWIP:2012-2517T-YDNoContent?(notcertain)Reqts,Ar
13、ch,ProtSubscribeZNotificationArchandWIPArchandWIPNocontentReqts,Arch,ProtPolicyFrameworkNocontentNoContentNocontentNocontentLocationandGeoFencingNocontentNoContentArchandWIPReqts,Arch,ProtGroupsManagementWIPNoContentArchandWIPReqts,Arch,ProtDeviceTriggeringNocontentNoContentNocontentNocontentAccessC
14、ontrolNocontentArchWIPReqts,Arch,ProtDataProcessingandStorageWIPNoContentWIPReqts,Arch,ProtConsumptionStatisticsZrecordsNocontentNoContentNocontentArchAPIManagementNocontentArchArchReqts,Arch,ProtDetailedreferencesReferencesforarchitecturerelatedcontentwhentheyexistareprovidedbelow.Thetextdescribing
15、thelineitemshasbeenextractedfromoeM2M-ARC-2012-0007R02.SubscriptionInformationHandling-OnboardnewdevicesbycreatingnewsubscriptioninthecommonM2Mservicelayerandnetworklayer;activate/deactivate/suspend/resumenetworkandservicesubscriptions.CCSAYDT2399-2012sect5.1.7WIP:2012-2549T-YD(eUICCsubscriptionprov
16、ision)sect5,6&8.2.4ETSIPlatformonlyTTATTAK.KO-06.0168section6-USNmeta-datamodelsWIP:Consortiumdraft1.1-e-healthsystemrequirementdescriptionontheinitializationprocedure.:WIPwillbecontributedTTAdraft2.1-highlevelmodelofM2Minterworking:WIPwillbecontributed2Q2013DeviceManagement-Manageallaspectsofthedev
17、icesincludingconfiguration,firmwareupgrades,applicationlifecyclemanagement,devicelockandwipeCCSAYDT2399-2012sect4(fc5WIP:2012B93sect5,7&9.2TIATIA-4940-020M2M-SmartDeviceCommunications;ProtocolAspects(Section6SecurityCommands.)TIATSB-4940SmartDeviceCommunications;SecurityAspectTTAConsortiumdraft1.2-s
18、marthomeusecase:WIPwillbecontributedConsortiumdraft1.1-e-healthsystemrequirementdescriptionontheremotemanagementofthedevices:WIPwillbecontributedTTAdraft2.3-M2Mdeviceregistrationanddiscovery:WIPwillbecontributed2Q2013ETSITS103092(OMADMcompliantmodel),2)TS103093(BBFTR069compliantmodel)ETSITS102690Sec
19、t5&9,annexB&EETSITS102921Sect10,AnnexEETSITS101603Sect4.9Security-generaterelevantkeymaterialforsecurecommunications;Authenticatedevicesbeforetheycanregisterandmodifyresources.PreventunauthorizedentitiesfromsendingIPpacketstothedevices.ProvideasecureconnectiontothedeviceCCSAYDT2399-2012Sect4.4,5.2ET
20、SI102690Sect5.2.6,5.4.6,8TTAConsortiumdraft1.2-smarthomeusecase:WIPwillbecontributedApplicationandDeviceRegistrations-Applicationanddeviceswillbeabletoregisterwiththeservicelayerentityforvariousservices.Registrationwillinvolveauthenticationorverificationofcredentialsandcreationorallocationofresource
21、swithintheserverandthedatabase.Aprofilewiththecapabilitiesofthedeviceandthetypeofservicesallowedfortheapplicationsarecreated.CCSAYDT2399-2012sect4.3.1,AnnexB,G(devicereg);AnnexH(appreg)2012-0336T-YDsect6,9(req.)WIP:2012B93sect9.1(devicereg)WIP:2012B93sect9.3(appreg)TIATIA-4940-005SmartDeviceCommunic
22、ations;ReferenceArchitectureTIA-4940-020(Section5BasicCommandsandSection6SecurityCommands)TTATTAdraft2.1-highlevelmodelofM2Minterworking:WIPwillbecontributed2Q2013TTAdraft2.4-requirementsofP2P:WIPwillbecontributed2Q2013ETSI102690Sect7.3ApplRegsect9&9.3.2.8.2DeviceReg8&9ResourceManagement-Application
23、sanddeviceswillbeabletocreate,update,anddeleteresourceobjectscontainingvariousattributesintheservicelayer.Entitieswillbeabletodiscoverresources.CCSA2012-0336T-YDsect9,11(req.)YDB064-2011sect6.1,9.1WIP:2012B93sect9.1,9.2,9.8(mostrelatedtotheconceptofresourcemanagementdefinedbelow)TIATIA-4940-005(Gene
24、ral)TIA-4940-020(Section5BasicCommands)TTATTAK.KO-06.0282sectio5.3TTAK.KO-06.0167section4,5,6-directoryservicerequirement&interfacespecificationformanagingmetadataofUSNresourcesTTAK.KO-06.0168section5-USNresourceidentifiersrequirementsTTAdraft2.1-highlevelmodelofM2Minterworking:WIPwillbecontributed2
25、Q2013ETSI102690Sect9Contentpush/pullServices-ProvideAPIforapplicationstoperformunicastandmulticastdatapushtospecifieddeviceswithinthespecifiedtimewindow.Pushmayberesultofanotificationthatistriggeredasaresultofmodificationofaresource.ProvideAPIforapplicationstopulldatafromoneormoredeviceswithinthespe
26、cifiedtimewindoworspecifiedperiodicityorotherpoliciesthathavebeenestablished.CCSANocontent(note:requirementaddressedin2012-0336T-YDsect5.4.4,YDB064-2011sect5.2.3andYDB100-2012sect4.4.1)TIATIA-4940-020(newSection5)TIA-4940-050M2M-SmartDeviceCommunications;Capabilities(willinclude“PushandPulF,)-Workin
27、progressTTAETSI102690Sect9StoreandForwardMessaging-Applicationsmayrequestmessagestobesenttooneormoredevicesthatmaynotberegisteredwiththenetworkatthattime.Inthiscasethecommunicationsmanagemententityshallstoreandaggregatethemessagesandforwardthemtothedevicesatalatertimewhenthedeviceswakeup.CCSAYDT2399
28、-2012sect3.2,3.3,4,3,4.4.3.1.3.3,5.1,AnnexE)WIP:2012B93sect4,7,9.7TIAOnlyhigh-leveldescription.TTAETSI102690Sect9.1.1ProtocolTranslation-Translateprotocolsbetweenapplicationanddeviceasneeded.Forexample,applicationsmayuseHTTPwhiledevicesmayuseConstrainedApplicationProtocol(CoAP)orZigbeeSE2.0protocol.
29、CCSANocontent(note:requirementaddressedin2012-0336T-YD,YDB064-2011andYDB100-2012)WIP:2012-2517T-YDTIANoContent(AssumedtobeProtocolagnostic.)TTATTAdraft2.5-UM3protocols:WIPwillbecontributed4Q2013(?)ETSI102921SectbindingSubscribeZNotification一Applicationanddevicesshouldbeabletosubscribetoreceivenotifi
30、cationsuponcertaineventsorwhencertainresourcesareupdated.Eventsmaybespecifiedasrulesoncertainresourcedata.CCSAYDT2399-2012sect5.1.5WIP:2012B93sect4,7,9.7(subscribe/notificationisconsideredaspartofstoreandforwardninthisTR)TIATIA-4940-020(Section5).TIA-4940-050-workinprogress;TTAETSI102690Sect9PolicyF
31、ramework-Frameworktoestablishandincorporateinthesessionorchestration,dataaggregationandstorage,thenetworkproviderandapplicationproviderpolicies.Examplesincludeincorporatingalocationtagortimestamponalldata,policyrestrictingsessionsonlytocertainhoursoftheday.Nocontent1.ocationandGeoFencing-Providedevi
32、ceandnetworkbasedlocationandlocationrelatedservicessuchascreatingageo-fenceoridentifyingagroupofdeviceswithinaregionoraddingalocationtagtothedevicedataETSI102690Sect9and9.3.2.13TTATTAK.KO-06.0170section4.6.2-USNserviceplatformrequirementsforprovidingWIPe-areaapplicationservicedeploymentTTAdraft2.2-M
33、2Mspecificfunctionalrequirements:WIPwillbecontributed2Q2013GroupsManagement-Frameworkforcreationofgroupsbyspecifyingthemembersofthegroupthroughoneoftheidentifiersofthedevice,addingadditionalmembersorremovingmembers;settinggroupattributesCCSAWIP:2012B93sect4,7,9.8TIANoContentTTATTAK.KO06.0283section4
34、,section5-thisdocumentisforuUSNresourcecommunitywhichimpliesthegroups-managementofresources.Consortiumdraft1.2-smarthomeusecase:WIPwillbecontributedTTAdraft2.2-M2Mspecificfunctionalrequirements:WIPwillbecontributed2Q2013ETSI102690Sect9DeviceTriggering-Providethecapabilitytotriggerthedevicetoregister
35、withthenetworkandanapplicationthroughasecondarymeanssuchasanSMS.Provideinformationaboutthestatusofthedeviceinthenetwork.NocontentAccessControl-Controltheaccesstothedatacollectedfromthedevicesbasedonaccessrestrictionsspecifiedbyapplicationsintermswhichusersordevicescanaccesswhatresources.TIATIA-4940-
36、020(Section5).ETSIBymeansoftheassociationofproperaccessrightresources(102690section9).TTAConsortiumdraft1.2-smarthomeusecase:WIPwillbecontributedDataProcessingandStorage-Providetemporaryandpermanentstoragefordatacollectedfromdevices.Processqueriesondatacollected.Providethresholdandexpressionrulesset
37、tingandexecutiononthevariousdatacollectedfromthedevices.Notificationscouldbetriggeredbasedontheoutcomeoftherulestesting.CCSAWIP:2012B93sect4,7,9.7ETSI102690Sect9relatedtothecontainerentity,itsabilityofhistorizecontainerinstances.Thanitusesnotifications.ETSIM2Mhasalsoabasicsearchmechanismbasedonsearc
38、hstringsandsomebasicexpressions(Date/time,numberofinstances,etc)butisnotsosophisticated.WediscussedheavilyinETSIM2MinthepastbutWelinkedthedesignofmoresophisticatedmechanismtothedevelopmentofsemanticaspects.TTAConsortiumdraft1.1-e-healthsystemrequirementdescriptiononthepre-definitionofthealarmlevel:W
39、IPwillbecontributedConsortiumdraft1.3-Fleetmanagementusecase:WIPwillbecontributedConsumptionStatisticsZrecords-Processqueriesregardingtheusageofnetworkresourcesbyadeviceoragroupofdevicesforbillingreconciliation.ETSIyesbutsection?APIManagement-ManageAPIusage,suchasauthenticationandauthorizationofcall
40、stoAPIsprovided.CCSANocontentTIATIA-4940-020(Section6).ETSIThefunctionisincluded.Onmid(DGNetwork)isfullydevelopedOndlaandmlaisafunctionthatisexplicitlyrequested,butthatleftforimplementationintheinitialphaseunderthefollowingrationale- Fordlainmainlyaninternaldevice(oranareanetworkaspectincaseofD,)- O
41、nmlaisaserviceproviderapplicationissueThereareclearlyintentioninsomecompanytodevelopfurtherthispartTTATTAK.KO-O.0282sectio6.3,7.2.2,7.2.4-ThesectiondescribestherequirementsonWeb-basedopenAPIs,SemanticopenAPIsservice,andSemanticqueryprocessing.ReferencedocumentsThecontributorsfeltatranslationofthetab
42、leofcontentofthekeydocumentsnotwritteninEnglishwouldbehelpfultoputthereferencedsectionsincontext.GoogleTranslatewasusedtoproducethetablesbelow.CCSADocumentReferences2012-0336T-YDRequirementDocumentGeneralRequirementsonWANBasedRemoteMeasurementandControlApplicationsforIntelligentAgricultureIntroducti
43、onIllNormativereferences4Abbreviations4 Termsanddefinitions5 businessdefinition55.1 Overview55.2 Operationalcharacteristics55.3 Thescopeofbusiness55.3.1 businessoperationsside55.3.2 Businessusers55.3.3 rangeofservices65.4 businesssegments65.4.1 DataAcquisitionclassbusiness65.4.2 DataViewclassbusines
44、s6Videomonitoringclassbusiness5.4.36Informationexchangesclassbusiness5.4.46Alarmclassbusiness5.4.565.4.6 RemoteControlclassbusiness65.4.7 .Linkagecontrolclassbusiness75.4.8 DeviceManagerclassbusiness75.4.9 extendedclassbusiness7ApplicationArchitecture76.1 SystemArchitecture76.1.1 Fieldnetworkdomain8
45、6.1.2 remotebusinessdomain96.2 functionalentities96.2.1 smartagricultureremotemonitoringandcontrolgateway96.2.2 .Sensornodes106.2.3 Applicationlayer106.3 InterfaceDefinition116.3.1 ofThingsterminalsensornodesinterface116.3.2 Theinterfacebetweenthesensornodesandsmartagricultureremotemonitoringandcont
46、rolgateway116.3.3 .Intelligentagricultureremotemonitoringandcontrolgatewayserviceadaptationmoduleinterface.116.3.4 withintheapplicationlayerinterface116.3.5 .Third-partyapplicationsandtheabilitytoopenthegatewayinterface12Perceptualextendinglayerrequirements127.1 overallrequirements127.2 Technicalrequirements127.2.1 .Gatewayrequirements127.2.2 sensingnoderequirements127.2.3 Sensorcategory127.2.4 Actuatorcategories138networklayerrequirements138.1 overallrequirements138.2 Technicalrequirements13Applicationlayerrequirements139.1 overallrequirements139.2 Technicalrequirements149.2.1 servic
