TS22.185V1.0.0(2016-02)TechServicerequirementsforV2Xservices.docx

3GPPTS22.185V1.0.0(2016-02)TechnicalSpecification3rdGenerationPartnershipProject;TechnicalSpecificationGroupServicesandSystemAspects;ServicerequirementsforV2Xservices;Stage1(Release14)35国Thepresentdocumenthasbeendevelopedwithinthe3n,GenerationPartnershipProject(3GPP)andmaybefurtherelaboratedforthepurposesof3GPP.Thepresentdocumenthasnotbeensubjecttoanyapprovalprocessbythe3GPPOrganizationalPartnersandshallnotbeimplemented.ThisSpeciflcationisprovidedforfuturedevelopmentworkwithin3GPPonly.TheOrganizationalPartnersacceptnoliabilityforanyuseofthisSpecification.SpecicationsandReportsibrimplementationof(he3GPPtmsystemshouldbeobtainedviathe3GPPOrganizationalPartners'PublicationsOffices.MCCselectskeywordsfromstocklist.Keywords<keyword,keyword,.>3GPPPostaladdress3GPPSUPPOrtOffiCeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:+334929442OOFax:+33493654716Internethttp7www.3gpp.orgCOPyrigMNOtifiCatiOnNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©2015.3GPPOrganizationalPartners(ARIB,ATIS,CCSA,ETSI,TSDSI,TTA,TTC).Allrightsreserved.UMTSisaTradeMarkofETSIregisteredforthebenefitofitsmembers3GPPisaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartnersLTEisaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartnersGSM®andtheGSMlogoareregisteredandownedbytheGSMAssociationContentsForeword41 Scope52 References53 Definitionsandabbreviations53.1 Definitions53.2 Abbreviations54 OverviewonV2X(informative)64.1 TypesofV2Xapplicationsupportin3GPP64.12Vehicle-Lo-Vehicle(V2V)application4.13Vehicle-to-Infrastructure(V2I)application4.14Vehicle-to-Network(V2N)application4.15Vehicle-to-Pedestrian(V2P)application.5 Requirements5.1 OverallRequirements5.1.1 SpecificServiceRequirements5.1.2 1.atency/ReliabilityRequirements5.1.3 MessageSizeRequirements5.1.4 FrequencyRequirements5.1.5 RangeRequirements5.1.6 SpeedRequirements5.2 SecurityRequirements6 7 7 7 778889999 OAnnexA:ChangehistoryForewordThisTechnicalSpecificationhasbeenproducedbythe3njGenerationPartnershipProject(3GPP).ThecontentsofthepresentdocumentaresubjecttocontinuingworkwithintheTSGandmaychangefollowingformalTSGapproval.ShouldtheTSGmodifythecontentsofthepresentdocument,itwillbere-releasedbytheTSGwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:Versionx.y.zwhere:xthefirstdigit:1 presentedtoTSGforinformation;2 presentedtoTSGforapproval;3 orgreaterindicatesTSGapproveddocumentunderchangecontrol.ytheseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.zthethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthedocument.1 ScopeThepresentdocumentprovides3GPPsupportforV2XservicerequirementstobesupportedbyLTEtransport.TheserequirementsareidentifiedbytakingintoaccounttheV2XservicerequirementsdefinedinotherSDOs,e.g.ETSIITS,USSAE.Thespecificationincludesrequirementsofsafetyandnon-safetyaspects.2 ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.-1 3GPPTR21.9()5:"Vocabularyfor3GPPSpecifications".2 3GPPTR22.885:"StudyonLTESupportforV2XServices".3 ETSITR102638VI.1.1:"IntelligentTransportSystems(ITS);VehicularCommunications;BasicSetofApplications;Definitions".3 Definitionsandabbreviations3.1 DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgivenin3GPPTR21.9051andthefollowingapply.Atermdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameterm,ifany,in3GPPTR21.9051.RoadSideUnit:AstationaryinfrastructureentitysupportingV2XapplicationsthatcanexchangemessageswithotherentitiessupportingV2Xapplications.NOTE:RSUisatermfrequentlyusedinexistingITSspecifications,andthereasonforintroducingtheterminthe3GPPspecificationsistomakethedocumentseasiertoreadfortheITSindustrj,.RSUisalogicalentitythatcombinesV2XapplicationlogicwiththefunctionalityofaneNB(referredtoaseNB-typeRSU)orUE(referredtoasUE-typeRSU).3.2 AbbreviationsForthepurposesofthepresentdocument,theabbreviationsgivenin3GPPTR21.9051andthefollowingapply.Anabbreviationdefinedinthepresentdocumenttakesprecedenceoverthedefinitionofthesameabbreviation,ifany,in3GPPTR21.905l.UINPVXS22222RvvvvvRoadSideUnitVehicle-to-1nfrastructureVehicle-Io-NetworkVehicle-to-PedestrianVehicle-to-VehicleVehicle-to-Everything4 OverviewonV2X(informative)4.1 TypesofV2Xapplicationsupportin3GPP4.1.1 GeneralTheV2Xapplicationsinthepresentspecification,referredtoasVehicle-Io-Everything(V2X),containthefollowingfourdifferenttypes:- Vehicle-to-Vehicle(V2V)- Vehicle-Io-Infrastructure(V2I)- Vehicle-to-Network(V2N)- Vehicle-to-Pedestrian(V2P)Figure4.1.1-1:TypesofV2Xapplications(V2V,V2P,V2NandV2l)ThesefourtypesofV2Xapplicationscanusewco-operativeawarenessntoprovidemoreintelligentservicesforendusers.Thismeansthatentities,suchasvehicles,roadsideinfrastructure,applicationserverandpedestrians,cancollectknowledgeoftheirlocalenvironment(e.g.,informationreceivedfromothervehiclesorsensorequipmentinproximity)toprocessandsharethatknowledgeinordertoprovidemoreintelligentservices,suchascooperativecollisionwarningorautonomousdriving.TheseintelligenttransportationservicesandtheassociatedmessagesetshavebeendefinedinautomotiveSDOsoutside3GPP.ThreebasicclassesofapplicationsIbrprovidingITSservices:roadsafely,trafficefficiency,andotherapplicationscanbefoundine.g.,3.3GPPonlyhandlesthetransportofthesemessagestosupportdifferenttypesofV2Xapplications.Themessagetransportexpectationsaredescribedinrequirementsdefinedinthisspecification.4.1.2 Vehicle-to-Vehicle(V2V)applicationV2VapplicationsexpectUESthatareinproximityofeachothertoexchangeV2Vapplicationinformation.3GPPtransportofmessagescontainingV2VapplicationinformationrequirestheUEtohaveavalidsubscriptionandauthorizationfromanetworkoperator.TransportforavalidsubscriberisprovidedwhethertheUEisservedornotservedbyE-UTRAN.TheUEsupportingV2VapplicationstransmitsmessagescontainingV2Vapplicationinformation(e.g.location,dynamics,andattributes).Themessagepayloadsmaybeflexibleinordertoaccommodatevaryingamountofinformation.3GPPtransportofmessagecontainingV2Vapplicationinformationispredominantlybroadcast-basedasillustratedinFigure4.1-2.Such3GPPtransportincludesthetransportbetweenUEsdirectlyand/or,duetothelimiteddirectcommunicationrange,thetransportbetweenUEsviainfrastructuresupportingV2Xcommunication,e.g.,RSU,applicationserver,etc.Error!Objectscannotbecreatedfromeditingfieldcodes.Figure4.1.2-1:Broadcast-basedV2Vcommunications4.1.3 Vehicle-to-1nfrastructure(V2l)applicationTheUEsupportingV2IapplicationstransmitsmessagescontainingV2IapplicationinformationtoanRSU.AnRSUtransmitsmessagescontainingV2IapplicationinformationtooneormoreUEssupportingV2Iapplications.4.1.4 Vehicle-to-Network(V2N)applicationTheUEsupportingV2NapplicationscommunicateswithanapplicationserversupportingV2Napplications.BothpartiescommunicatewitheachotherviaEPS.Theapplicationserveranditslocationareoutof3GPPscope.4.1.5 Vehicle-to-Pedestrian(V2P)applicationV2PapplicationsexpectUEsthatareinproximityofeachothertoexchangeV2Papplicationinformation.3GPPtransportofmessagescontainingV2PapplicationinformationrequirestheUEtohaveavalidsubscriptionandauthorizationfromanetworkoperator.TransportforavalidsubscriberisprovidedwhethertheUEisservedornotservedbyE-UTRAN.TheUEsupportingV2PapplicationstransmitsmessagescontainingV2Papplicationinformation.ItisexpectedthatV2PapplicationinformationcanbetransmittedeitherbyaUEsupportingV2Xapplicationinavehicle(e.g.,warningtopedestrian),orbyaUEsupportingV2Xapplicationassociatedwithavulnerableroaduser(e.g.,warningtovehicle).3GPPtransportofmessagescontainingV2PapplicationinformationincludesthetransportbetweenUEsdirectlyand/or,duetothelimiteddirectcommunicationrange,thetransportbetweenUEsviainfrastructuresupportingV2Xcommunication,e.g.,RSU,applicationserver,etc.NOTE:Themaindifferencebetween3GPPtransportofmessageswithV2PandV2V叩PliCationinformationisduetothepropertiesoftheUE.AUEsupportingV2Papplicationsusedbypedestrianmight,forexample,havelowerbatterycapacity,theradiosensitivitymightbelimited,e.g.duetoantennadesign,andthereforeitmaynotbeabletosendmessageswiththesameperiodicityasUEssupportingV2Vapplication,and/orreceivemessages.5 Requirements5.1 OverallRequirementsR-5.1-001Themessagetransmissionshallbeundercontrolofthe3GPPnetworkwhenthetransmittingUEisservedbytheE-UTRAN.R-5.1-002jAUEsupportingV2Xapplicationshallbeabletobepre-configuredbythe3GPPnetworkwithparameterstobeusedforthetransmissionandreceptionofmessageswhennotservedbyE-UTRANsupportingV2Xcommunication.R-5.1-003AUEsupportingV2Xapplicationshallbeabletotransmitandreceivemessageswhensen,edornotservedbyE-UTRANsupportingV2Xcommunication.R-5.1-004AnRSUshallbeabletotransmit/receivemessagesto/fromaUEsupportingV2Xapplication.IR-5.1-005The3GPPsystemshallbeabletosupportmessagetransferbetweenUEswhenservedornotservedbythesamePLMNsupportingV2Xcommunications.R-5.1-006The3GPPsystemshallbeabletoprovidemeanstoprioritizemessagetransmissionamongUEssupportingV2XapplicationR-5.1-007The3GPPsystemshallbeabletoprovidemeanstoprioritizetransmissionofmessagesaccordingtotheirtype(e.g.safetyvs.non-safety).R-5.1-(X)8The3GPPsystemshallbeabletoVarythetransmissionrateandrangeoftheV2Xcommunicationbasedonserviceconditions(e.g.,UEspeed,UEdensity).R-5.1-009The3GPPsystemshallbeabletodistributeinformationinaresourceefficientwaytolargenumbersofUEssupportingV2Xapplication.R-5.1-010AUEsupportingV2XapplicationshallbeabletoidentifywhetherE-UTRANsupportsV2Xcommunication.R-5.1-011The3GPPsystemshallbeabletoprovidemeansforanapplicationserverandtheRSUtocontroltheareaandthesizeoftheareawherethemessagesarebeingdistributed.R-5.1-012TheE-UTRA(N)shallbeabletosupportahighdensityofUEssupportingV2Xapplication.R-5.1-013BoththeHPLMNandVPLMNoperatorsshallbeabletochargefornetworkresourceusagewhenmessagesaretransferredbyaUEsupportingV2Xapplication.R-5.1-014ForUEsupportingV2Xapplicationwithlimitedresources(e.g.,battery),theimpactonitsresources(e.g.,batteryconsumption)duetomessagetransfershouldbeminimized.IR-5.1-015The3GPPnetworkshouldmakeavailableanysupportedpositionalaccuracyimprovementtechniques(e.g.,DGPSand/orOTDOA)inaresourceefficientwaytoasubscribedUEsupportingV2Xapplication.5.1.1 SpecificServiceRequirements5.1.2 1.atency/ReliabilityRequirementsR-5.2.1-001TheE-UTRA(N)shallbecapableoftransferringmessagesbetweentwoUEssupportingV2VPapplication,directlyorviaanRSU,withamaximumlatencyof100ms.R-5.2.1-(X)2Forparticularusage(i.e.,pre-crashsensing)only,theE-UTRA(N)shouldbecapableoftransferringmessagesbetweentwoUEssupportingV2Vapplicationwithamaximumlatencyof20ms.R-5.2.1-003TheE-UTRA(N)shallbeC叩ableoftransferringmessagesbetweenaUEsupportingV2IapplicationandanRSUwithamaximumlatencyof100ms.IR-5.2.1-004TheE-UTRANshallbecapableoftransferringmessagesvia3GPPnetworkentitiesbetweenaUEandanapplicationserverbothsupportingV2Napplicationwithanend-to-enddelaynolongerthan1000ms.R-5.2.1-(X)5TheE-UTRA(N)shallbeabletosupporthighreliabilitywithoutrequiringapplication-layermessageretransmissions.5.1.3 MessageSizeRequirementsR-5.2.3-(X)lTheE-UTRA(N)shallbecapableoftransferringperiodicbroadcastmessagesbetweentwoUEssupportingV2Xapplicationwithvariablemessagepayloadsof50-3(X)bytes,notincludingsecurity-relatedmessagecomponent.R-5.2.3-0021TheE-UTRA(N)shallbeC叩ableoftransferringevent-triggeredmessagesbetweentwoUEssupportingV2Xapplicationwithvariablemessagepayloadswhichcanbeupto1200bytes,notincludingsecurity-relatedmessagecomponent.NOTE:3GPPonlyhandlesthetransportofmessagesforV2Xservicesalicationsbasedonmessagecharacteristics(e.g.,latency,messagesize)andisagnostictomessagetypes.5.1.4 FrequencyRequirementsR-5.2.3-(X)lTheE-UTRA(N)shallbeabletosupportamaximumfrequencyof1()messagespersecondperUEorperRSU.NOTE:ItisassumedthatV2Xapplicationprovidesmessagesto3GPPlayerIbrtransporteitherperiodicallyand/ortriggeredbycertainevents.5.1.5 RangeRequirementsR-5.2.4-001TheE-UTRANshallbeC叩ableofSUPPortingacommunicationrangesufficienttogivethedriver(s)ampleresponsetime(e.g.4seconds).5.1.6 SpeedRequirementsR-5.2.5-001The3GPPsystemshallbecapableoftransferringmessagesbetweenUEssupportingV2Vapplication,whilethemaximumrelativevelocityoftheUESis280km/h,regardlessofwhethertheUE(s)areservedornotservedbyE-UTRANsupportingV2Xcommunication.R-5.2.5-002The3GPPsystemshallbecapableoftransferringmessagesbetweenUEssupportingV2VandV2Papplication,respectively,whiletheUE'smaximumabsolutevelocityis160km/h,regardlessofwhethertheUE(s)areservedornotservedbyE-UTRANsupportingV2Xcommunication.R-5.2.5-0031The3GPPsystemshallbeC叩ableoftransferringmessagesbetweenaUEandanRSUbothsupportingV2Iapplication,whiletheUE,smaximumabsolutevelocityis160km/h,regardlessofwhethertheUEortheRSUisservedornotservedbyE-UTRANsupportingV2Xcommunication.5.2 SecurityRequirementsR.5.3-OO1The3GPPnetworkshallprovideameansfortheMNOtoauthorizeaUEsupportingV2XapplicationtoperformV2XcommunicationwhenservedbyE-UTRANsupportingV2Xcommunication.R.5.3-(X)2The3GPPnetworkshallprovideameans(e.g.,pre-authorization)fortheMNOtoauthorizeaUEsupportingV2XapplicationtoperformV2XcommunicationwhennotservedbyE-UTRANsupportingV2Xcommunication.R.5.3-0031The3GPPnetworkshallprovideameansfortheMNOtoauthorizeUEssupportingV2XapplicationseparatelytoperformV2Ncommunication.R.5.3-OO4The3GPPsystemshallsupporttheanonymityofUEsupportingV2Xapplicationandtheintegrityprotectionofthetransmission.R.5.3-005The3GPPsystemshouldbeabletosupportUEprivacyforV2Xcommunications,byensuringthataUEcannotbetrackedoridentifiedbyanyotherUEbeyondacertainshorttime-periodrequiredbytheapplication.R.5.3-0061Subjecttoregulatoryrequirementsand/oroperatorpolicy,the3GPPsystemshallsupportUEprivacyforV2Xcommunication,suchthatUEscannotbetrackedoridentifiedbytheoperatororathirdparty.AnnexA:ChangehistoryChangehistoryDateTSG#TSGDoc.CRRevSubjecVCommentOldNew2015-11SA/#72Skeleton0.0.00.1.02016-02SAl#73Additionofscope,definition,overview,servicerequirementscontentagreedatSAIff730.1.00.2.02016-02SA7ISP-160099Raisedtov.1.0.0farpresentationtoone-stepapprovaltoSA0.2.01.0.0