《00018ed211v005_cl.docx》由会员分享，可在线阅读，更多相关《00018ed211v005_cl.docx（19页珍藏版）》请在课桌文档上搜索。
1、TS101603VO.0.5.(2012-11)Machine-to-Machinecommunications(M2M);3GPPInterworking错误!未找到引用源。ReferenCe-DTSM2M-00018ed211-Keywords3GPP,Intenvorking1M2M,ArchitectureETSI650RoutedesLuciolesF-06921SOPhiaAmiPOIiSCedeX-FRANCETel.:+334929442OOFax:+33493654716SiretNo34862356200017-NAF742CAssociationAbutnonIucrat
2、ifenregistr6eaIaSous-PrefecturedeGrasse(06)N07803/88ImPOrtamnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http:WWW.etsi.orThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferencevers
3、ionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSId
4、ocumentsisavailableathttp:PortaI.etsi.ortbStatUSstatus.aspIfyoufinderrorsinthepresentdocument,pleasesendyourcommenttooneofthefollowingservices:httD：portal.etsi.orChairCol7ETSISIJDPOrIaonCOPyrightNotifiCatiOnNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestric
5、tionextendtoreproductioninallmedia.EuropeanTelecommunicationsStandardsInstitute2012.Allrightsreserved.DECT,PLUGTESTS,UMTSandtheETSIlogoareTradeMarksofETSIregisteredforthebenefitofitsMembers.3GPPandLTEareTradeMarksofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners.GSMandtheGS
6、MlogoareTradeMarksregisteredandownedbytheGSMAssociation.ReproductionisonlypermittedforthepurposeofstandardizationworkundertakenwithinETSI.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.ContentsIntellectualPropertyRights5Foreword51 Scope62 References62.1 Normativereferences62.2
7、Informativereferences73 Definitions,symbolsandabbreviations73.1 Definitions73.2 Abbreviations74 3GPPInterworking74.1 General74.2 Identifiers74.2.1 General74.2.2 M2MDeviceZGatewayServiceLayerIdentifiersfor3GPPInterworking84.2.3 IdentificationofM2MApplications84.3 Addressing94.4 3GPPConnectivityand3GP
8、PServices94.5 Mobility94.6 Security94.6.1 Introduction94.6.2 GBA104.6.3 SecuredEnvironmentDomainadministration104.7 Charging114.8 Triggering114.9 Devicemanagement114.9.1 General114.9.2 ReuseofDeviceManagementServerinthe3GPPsystem114.9.3 DistributedDeviceManagementServerinthe3GPPsystemandtheM2MServic
9、eDomain125 ArchitecturalModelfor3GPPsystemM2MServiceCapabilityLayer135.1 ArchitecturalReferenceModel135.1.1 DirectModel135.2 ReferencePoints145.3 FunctionalElements156 ServiceProceduresandInformationFlows15History19IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayh
10、avebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSlSR000314:IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSlinrespectofETSlstandards,whichisavailablefromtheETSISecretariat.Lat
11、estupdatesareavailableontheETSIWebserver(http:iDr.etsi.org).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepr
12、esentdocument.ForewordThisTechnicalSpecification(TS)hasbeenproducedbyETSITechnicalCommitteeMachinetoMachine(ETSITCM2M).1 ScopeTheM2MfunctionalarchitectureisdesignedtomakeuseofanIPcapableunderlyingnetworkastheIPnetworkserviceprovidedby3GPP.ThepresentdocumentcontainstheM2Mfunctionalarchitecture,includ
13、ingtheidentificationofthefunctionalentities,relatedreferencepointsandprocedures,when3GPPsystemisusedastheunderlyingIPnetworkby:- EndorsingtheoptionsandcapabilitiesspecifiedinTS102690andTS102921,Rel-1,neededtointerworkwith3GPPsystemsasspecifiedinRel-11andearlier- DescribinghowtheM2Mservicelayer,NSCL,
14、SUPPOrtSthedifferentmodelsdepictedin3GPPMTCwork(3GPPTS23.682,Rel11)- Identifyingexistingproceduresin3GPPsystemsandspecifyingproceduresinETSIM2Marchitectureneededtocompleteasolutionforinterworkingwith3GPPsystem.NOTE:Updatesofproceduresdeemednecessaryonmla,dla,andmid,willbebroughtaschangestotherelevan
15、tspecifications2 ReferencesReferencesareeitherspecific(identifiedbydaleofpublicationand/oreditionnumberorversionnumber)ornon-specific.Forspecificreferences,onlythecitedversionapplies.Fornon-specificreferences,thelatestversionofthereferenceddocument(includinganyamendments)applies.Referenceddocumentsw
16、hicharenotfoundtobepubliclyavailableintheexpectedlocationmightbefoundathttW/docbox.etsi.org/Reference.NOTE:Whileanyhyperlinksincludedinthisclausewerevalidatthetimeofpublication,ETSIcannotguaranteetheirlongtermvalidity.2.1 NormativereferencesThefollowingreferenceddocumentsarenecessaryfortheapplicatio
17、nofthepresentdocument.1 ETSITS102690:MachinetoMachineCommunications(M2M);Functionalarchileclure”2 3GPPTS23.682:“3rdGenerationPartnershipProject;TechnicalSpecificationGroupSendeesandSystemAspects;Architectureenhancementstofacilitatecommunicationswithpacketdatanetworksandapplicationsv3 ETSlTS123.002:“
18、3rdGenerationPartnershipProject;TechnicalSpecificationGroupServicesandSystemAspects;Networkarchitecture4 ETSITS102921:MachinetoMachineCommunications(M2M);mla,dlaandmidinterfaces5 3GPPTS31.115(V10.1.0):RemoteAPDUStructurefor(U)SIMToolkitapplications(Release10)6 3GPPTS31.116(V10.2.0):RemoteAPDUStructu
19、refor(Universal)SubscriberIdentityModule(U)SIMToolkitapplications(Release10)”7OMA-ERP-DM-VL3,“OMADeviceManagementvl.38 OMa-TS-DM-TND-V1_3,44OMADeviceManagementTreeandDescription”9 OMA-TS-DM_Server_Delegation_Protocol-V1_3,44OMADeviceManagementServerDelegationProtoco,2.2Informative referencesThefollo
20、wingreferenceddocumentsarenotnecessaryfortheapplicationofthepresentdocumentbuttheyassisttheuserwithregardtoaparticularsubjectarea.EXAMPLE:ili2OMA-TS-REST_NetAPl_OneAPlProfile-V3_0-20120327-C.http:/WWW.ODenmobilealliance.org/aDi/APIsInventory.asDX.3Definitions,symbolsandabbreviations3.1DefinitionsFor
21、thepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:example1:textusedtoclarifyabstractrulesbyapplyingthemliterallyNOTE:Thismaycontainadditionalinformation.3.2AbbreviationsAPIGSMAHTTP OMA OneAPl RESTSMS SOAP URI4.1General4.2Identifiers4.2.1GeneralForthepurposesofthepresentdocument,th
22、efollowingabbreviationsapply:ApplicationProgrammingInterfaceGSMAssociationHypertextTransferProtocolOpenMobileAllianceOpennetworkenablerAPIREpresentationalStateTransferShortMessageServiceSimpleObjectAccessProtocolUniformResourceIdentifier3GPPInterworkingWhenmakinguseofa3GPPsystemfortransport,theend-t
23、o-endcommunications,betweenaDSCL/GSCL(andassociatedDAGA)andtheNSCLshallcomplywith3GPPspecifications.Inparticular,forMachinetoMachinecommunications,theidentifiersusedshalladheretoTS23.6822.NOTE:Identifiersusedwithinthe3GPPsystemarespecifiedinTS23.0033.CorrelationofidentifiersforM2Mdevicesandapplicati
24、ons,asdefinedbyTS1026901,isdescribedinthenextclausesinordertofollowthecriteriaestablishedbyTS23.68221andthe3GPPsysteminTS23.0033.Onlythoseidentifierswithrelevancetotheinterworkingwiththe3GPPsystemaredescribed.IntheETSIM2MarchitectureisnecessarytocorrelatetheSCL-Idwithexternalidentifierwhenmakinguseo
25、ftherelated3GPPfunctionalities.Thiscorrelationcanbestaticallypre-provisionedormadedynamically,e.g.atthetimeoftheSCLregistration.Editor,snote:Thecurrenttextonlycoversstaticcasetocorrelateidentifiers.Dynamiccaseofexternalidentifierisexpectedtobedescribeduponresponsefrom3GPP.1.1.2 M2MDevice/GatewayServ
26、iceLayerIdentifiersfor3GPPInterworkingM2MDevicesandGatewaysconnectedtoa3GPPsystemshallbeidentiedbymeansofanexternalidentifier,consistingofaLocalIdentifierandaDomainidentifier.ThisexternalidentifiershalladheretoTS23.6822andtheusemadeofitscomponentsmaydifferdependingontheconnectionmodel: Forindirectmo
27、del,theExternalIdentifierdemandsaDomainIdentifier,toprovidethepointofcontactatthe3GPPMNO(e.g.EU_Operator.co.uk),andaLocalidentifier,usedtoderivetheIMSI.Editorsnote:TheDomainidentifiertobeusedforIndirectmodelisffs. ForDirectModel,thedomainidentifiershallbedeemedirrelevantfortheM2MServiceProvider(i.e.
28、thepointofcontactatthe3GPPMNOshallberesolvedbyusingAPNsassignedtothedevices/gateways)andtheexternalidentifierissimplyusedbythe3GPPMNOtoderivetheIMSI.TheM2MServiceProviderwilluniquelyderivetheLocalIdentifierfromtheSCL-ID.TheLocalIdentifiermaytakethefollowingformsforM2MDevicesZGatewayscomplyingwithTS1
29、026901andconnectedioa3GPPsystem: AnE.164MSlSDN.Insuchacase,theE.164MSISDNshallbeprovisionedtotheM2MServiceProvider,or AnIMSI,incasethe3GPPoperatoristheM2MSe,iceProviderorthe3GPPMNOpolicypermitsit,or Agenericidentifier(e.g.gas_melerOO1)Editorsnote:TheuseofagenericidentifierisFFSinthisspecification.Ed
30、itorsnote:ItisforFFSthattheexternalidentifiercanbeassociatedtomultipleSCL-IDsonthesamedevice/gateways.TheLocalidentifierisdeterminedbythe3GPPMNOandthenprovisionedtotheM2MServiceProvider,Thisprovisioningcanbemadewithinanagreementbetweenthe3GPPMNOandtheM2MServiceProvider,allowingtheM2MServiceProvidert
31、odetermineit.TheprovisioningmechanismisoutofscopeofthisspecificationNOTE:AnycommunicationfromanM2MSen,iceCapabilitiesLayer,notsupportedbymidreferencepoint,willmakeuseofMSISDNorIMSIEditorsnote:Subscriptionlevelidentificationmaybenecessaryintheinterworkingwitha3GPPMNOforchargingcorrelationpurposes.The
32、needofanadditionalmappingforsuchcorrelationisFFS,waitingforthecompletionofcorrelationrequirementsinTS102690.1.1.3 IdentificationofM2MApplicationsEditor,snote:UseofApplicationsIdentifiersisFFSandrequirescoordinationwith3GPP.4.3 Addressing4.4 3GPPConnectivityand3GPPServicesThecompletesolutionforthesup
33、portofM2Mapplicationsusing3GPPnetworksasconnectivity,consistsofterminals,IP-ConnectivityAccessNetworks(ip-can)andPS/CSservices(e.g.SMS),aswellasthespecificfunctionalelementsofthe3GPPnetwork,describedinTS123.(X)23.TheM2MservicesmakeuseoftheIP-CANprovidedby3GPPnetworktotransportsignallingandbearertraf
34、fic.IP-CANsthatmaintaintheservicewhiletheterminalmoves,hidethesemovesfromtheM2MNetworkApplicationandM2Mservicelayerdomains.TheM2Mserviceisindependentofthe3GPPCSdomainalthoughsomenetworkelementsmaybecommonwithit(e.g.SMSinfrastructure).TheNSCLshallbeabletomakeuseoftheservicesofferedbythe3GPPsystemusin
35、gopenaccessmodels(e.g.OSA,OMAorGSMAoneAPIframework).Thesesen,icesincludeaccessto:- IPmultimediacommunications- Messagingcapabilities,i.e.MMS.SMS- 1.ocationservices- Chargingandbillingservices- DeviceinformationandprofilesEditorsnote:ContributionsareinvitedtojustifytheneedtoaccessIPmultimediaCommUniC
36、aliOnS/services.ThisshallbesupportedbyasetofAPsbetweentheM2MNSCLandthe3GPPoperatorsnetworkbymeansofTOECcapability.NOTE:ItispossibleforaM2MNetworkApplicationtomakeuseoftheservicesofferedby3GPPdirectlybyusingthissetofAPs,butsuchabilityisoutofthescopeofthisspecification.AsetofstandardizedAPstoconformwi
37、ththeOnePIprofiledefinedbyOMisspecifiedini-l.ThecompletesetofOMANetworkAPIs,RESTandSOAPbased,isavailableati.2.Editorsnote:WhetherTOECcapabilityisusedoranewenabler/capabilityistobespecifiedisforfurtherdiscussion/study.4.5 Mobility3GPPsystemisdesignedformobilecommunication,whereamobiledevicethatisconn
38、ectedtothemobilenetworkviawirelessconnectionisabletofreelymovearoundwithinthewirelessservicecoverageareaandremainabletocommunicate.The3GPPsystemsattempttofunctioninawaythattheuserorserviceusing3GPPsystemdoesnothavetoconsiderthefactthatthedeviceisusingwirelessconnection,andismobilityenabled.TheIPconn
39、ectivityservicewillremainavailableirrespectiveofmobility.When3GPPsystemisusedastransportforM2M,allrequiredmobilityfunctionalityisprovidedby3GPPsystem.Thelevelofmobilitysupportisdefinedbythemobilenetworksubscription.TheDSCL/GSCLshallmaintaintheM2MPoCresourceupdatedintheNSCLasspecifiedinsection9.3.2.2
40、1of1,andsection4.8(Triggering)ofthisdocument.Editorsnote:ItisFFSifthereisotherspecificneedtoaddressdevicemobilityfromtheM2MServiceCapabilityLayer.4.6 Security4.6.1 IntroductionSecurityontheM2Mservicelayerisanoptionalfeature.Therestofsection4.6specifiesoptionsthatmaybeusedforprovidingsecurityontheM2M
41、servicelayer.4.6.2 GBAForscenarioswheretheM2MServiceProviderandtheoperatoroftheunderlying3GPPnetworkhaveatrustrelationship(includingthecasethattheyareactuallythesameentity),GBAmaybeusedforprovidingsecurityontheM2Mservicelayer.Asspecifiedin1GBAmaybeusedeitherforM2MServiceBootstraporforM2MServiceConne
42、ction(butnotboth).IfthereisanagreementbetweentheM2MServiceProviderandthe3GPPnetworkoperatortousethesecretkeyKinUSIM/ISIMastheM2MRootKey(Kmr),section4.6.2.1applies.Otherwise,whenGBAisused,aKmrshallbebootstrappedandsection4.6.2.2applies.4.6.2.1 GBAforM2MServiceConnection4.6.2.1.1 M2MServiceBootstrapTh
43、esecretkeyKinUSIM/ISIMshallbeusedasKmrandthereforenoServiceBootstrapshallbeperformed.NeCeSSaryM2Mspecificinformatione.g.M2MNodeID,SCLID,etc.shallbepre-configuredintheD/GandintheNetworkDomain.4.6.2.1.2 M2MServiceConnectionForM2MServiceConnection,theGBA-basedprocedureasspecifiedinsection7.2.1of4shallb
44、eperformed.4.6.2.1.3 midsecurityThemidreferencepointshallbesecuredintheformofchannelsecurity.ATLSsecurechannelshallbeestablishedbyusingtheM2MConnectionKeythatisgeneratedintheGBA-basedSen,iceConnectionprocedure,accordingtosection7.2.1of4,4.6.2.2 GBAforM2MServiceBootstrap4.6.2.2.1 M2MServiceBootstrapT
45、heGBA-basedM2MServiceBootstrapprocedureasspecifiedinsection6.2.1of4shallbeperformed.4.6.2.2.2 M2MServiceConnectionForM2MServiceConnection,theTLS-PSKbasedprocedureasspecifiedinsection7.4of41shallbeperformed.4.6.2.2.3 midsecurityThemidreferencepointshallbesecuredintheformofchannelsecurity.ATLSsecurech
46、annelshallbeestablishedbyusingtheM2MConnectionKeythatisgeneratedintheTLS-PSKbasedSen,iceConnectionprocedure,accordingtosection8.2of4.4.6.3 SecuredEnvironmentDomainadministrationDatabelongingtoETSIM2MServiceProvidercontainedinaSecuredEnvironmentDomainhostedonaUICC(e.g.ETSIM2Msubscriptioninformation)s
47、hallbeadministeredunderthecontrolofthe3GPPOperatoronbehalfoftheM2MServiceProviderusingUICCOTAprotocolasspecifiedin3GPPTS31.1155andin3GPPTS31.11661.TheinterfacetoaccesstheOTAplatformisnotdescribedinthisspecification.EditorsNote:FurthercontributionisneededtoclarifythetypeofthesubscriptioninformationthattheM2MSen,iceProviderwouldadministerontheUICC.EditorsNote:ThemappingtofunctionalarchitectureisFFS4.7 ChargingEditor,snote:ChargingimpactsintheServiceLayer,derivedfrominterworkingwith3GPP,areforftrtherstudy/discussi
