TS 24.385 V2.0.0 (2017-02) V2X services Management Object (MO)

3GPP TS 24.385 V2.0.0 (2017-02)Technical Specification3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;V2X services Management Object (MO) (Release 14)The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented.This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification.Specifications and Reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners Publications Offices.3GPP TS 24.385 V2.0.0 (2017-02)69Release 14KeywordsV2X, Management object3GPPPostal address3GPP support office address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16Internethttp:/www.3gpp.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media. 2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).All rights reserved.UMTS is a Trade Mark of ETSI registered for the benefit of its members3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersLTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational PartnersGSM and the GSM logo are registered and owned by the GSM AssociationContentsForeword61Scope72References73Definitions and abbreviations83.1Definitions83.2Abbreviations84V2X Communication Provisioning MO84.1Overview85MO configuration parameters125.1General125.2Node: 135.3/Name135.4Configuration parameters for V2X provisioning135.4.1/V2XProvisioning135.4.2/V2XProvisioning/V2XControlFunctionAddress135.4.3/V2XProvisioning/ToConRefs135.4.4/V2XProvisioning/ToConRefs/145.4.5/V2XProvisioning/ToConRefs/ConRef145.5Configuration parameters for V2X communication over PC5145.5.1/V2XoverPC5145.5.2/V2XoverPC5/Expiration145.5.3/V2XoverPC5/ServedByEUTRAN155.5.4/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs155.5.5/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/155.5.6/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/PLMN155.5.7/V2XoverPC5/NotServedByEUTRAN155.5.8/V2XoverPC5/NotServedByEUTRAN/Authorized165.5.9/V2XoverPC5/NotServedByEUTRAN/RadioParameters165.5.10/V2XoverPC5/NotServedByEUTRAN/RadioParameters/165.5.11/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ RadioParametersContents165.5.12/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea175.5.13/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea/Polygon175.5.14/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea/Polygon/175.5.15/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea/Polygon/Coordinates175.5.16/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea/Polygon/Coordinates/185.5.17/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea/Polygon/Coordinates/Latitude185.5.18/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ GeographicalArea/Polygon/Coordinates/Longitude185.5.19/V2XoverPC5/NotServedByEUTRAN/RadioParameters/ OperatorManaged185.5.20/V2XoverPC5/AuthorizedV2XServiceList195.5.21/V2XoverPC5/AuthorizedV2XServiceList/195.5.22/V2XoverPC5/AuthorizedV2XServiceList/ V2XServiceIdentifier195.5.23/V2XoverPC5/AuthorizedV2XServiceList/ DestinationLayer2ID195.5.24/V2XoverPC5/PPPPtoPDBMappingRule195.5.25/V2XoverPC5/PPPPtoPDBMappingRule/205.5.26/V2XoverPC5/PPPPtoPDBMappingRule/ ProSePerPacketPriority205.5.27/V2XoverPC5/PPPPtoPDBMappingRule/ PacketDelayBudget205.5.28/V2XoverPC5/TimerT5000205.6Configuration parameters for V2X communication over LTE-Uu215.6.1/V2XoverLTEUu215.6.2/V2XoverLTEUu/Expiration215.6.3/V2XoverLTEUu/ToConRefs215.6.4/V2XoverLTEUu/ToConRefs/215.6.5/V2XoverLTEUu/ToConRefs/ConRef215.6.6/V2XoverLTEUu/AuthorizedPLMNs225.6.7/V2XoverLTEUu/AuthorizedPLMNs/225.6.8/V2XoverLTEUu/AuthorizedPLMNs/PLMN225.6.9/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig225.6.10/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig/ TMGI235.6.11/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig/ SAIList235.6.12/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig/ SAIList/235.6.13/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig/ SAIList/SAI235.6.14/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig/ Frequency245.6.15/V2XoverLTEUu/AuthorizedPLMNs/V2XASMBMSConfig/ SDPInV2XASMBMSConfig245.6.16/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated245.6.17/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs255.6.18/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/255.6.19/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig255.6.20/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig/TMGI255.6.21/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig/SAIList265.6.22/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig/SAIList/265.6.23/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig/SAIList/SAI265.6.24/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig/Frequency265.6.25/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/V2XMBMSConfig/ SDPInV2XMBMSConfig275.6.26/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XASAddresses275.6.27/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XASAddress/275.6.28/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XASAddress/L3Address275.6.29/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XASAddress/UDPPort285.6.30/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XASAddress/ GeographicalArea285.6.31/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierUnrelated/V2XASAddress/GeographicalArea/Polygon285.6.32/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated285.6.33/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList295.6.34/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/295.6.35/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/ V2XServiceIdentifier295.6.36/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/ V2XMBMSConfigs295.6.37/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/ V2XMBMSConfigs/305.6.38/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig305.6.39/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig/TMGI305.6.40/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig/SAIList315.6.41/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig/SAIList/315.6.42/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig/SAIList/SAI315.6.43/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig/Frequency315.6.44/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/V2XMBMSConfigs/ V2XMBMSConfig/SDPInV2XMBMSConfig325.6.45/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/ V2XASAddresses325.6.46/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs325.6.47/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/325.6.48/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig335.6.49/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig/TMGI335.6.50/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig/SAIList335.6.51/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig/SAIList/335.6.52/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig/SAIList/SAI345.6.53/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig/Frequency345.6.54/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/ V2XMBMSConfig/SDPInV2XMBMSConfig345.6.55/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses355.6.56/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses/355.6.57/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses/TypeOfData355.6.58/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses/V2XMessageFamily355.6.59/V2XoverLTEUu/AuthorizedPLMNs/ V2XServiceIdentifierRelated/DefaultV2XASAddresses/ V2XASAddresses365.7/Ext36Annex A (informative):V2X Communication Provisioning MO DDF37Annex B (informative):Change history69ForewordThis Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:Version x.y.zwhere:xthe first digit:1presented to TSG for information;2presented to TSG for approval;3or greater indicates TSG approved document under change control.ythe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.zthe third digit is incremented when editorial only changes have been incorporated in the document.1ScopeThe present document defines Management Object (MO) that is used to configure the UE for V2X services.The MO is compatible with the OMA Device Management (DM) protocol specifications, version1.2 and upwards, and is defined using the OMA DM Device Description Framework (DDF) as described in the Enabler Release Definition OMA-ERELD-DM-V1_23.The MO consists of relevant parameters for provisioning and authorization of V2X communication at the UE.The protocol aspects for V2X are described in 3GPPTS24.3864.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the present document.-References are either specific (identified by date of publication, edition number, version number, etc.) or nonspecific.-For a specific reference, subsequent revisions do not apply.-For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.13GPPTR21.905: Vocabulary for 3GPP Specifications.23GPPTS23.285: Architecture enhancements for V2X services.3OMA-ERELD-DM-V1_2: Enabler Release Definition for OMA Device Management.43GPPTS24.386: User Equipment (UE) to V2X control function; protocol aspects; Stage 3.5OMA-TS-DM_Protocol-V1_2: OMA Device Management Protocol.6ISO8601:2004: Data elements and interchange formats - Information interchange - Representation of dates and times.73GPPTS23.003: Numbering, addressing and identification.83GPPTS36.331: Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification.93GPPTS23.032: Universal Geographical Area Description (GAD).10ISOTS17419ITS-AIDAssignedNumbers: http:/standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf113GPPTS36.101: Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception.123GPPTS23.303: Proximity-based Services (ProSe); Stage2.3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the terms and definitions given in 3GPPTR21.9051 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPPTR21.9051.For the purposes of the present document, the following terms and definitions given in 3GPPTS23.0037 apply:TMGI3.2AbbreviationsFor the purposes of the present document, the abbreviations given in 3GPPTR21.9051 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPPTR21.9051.DDFDevice Description FrameworkMOManagement ObjectPDBPacket Delay BudgetPPPPProSe Per-Packet PrioritySAIService Area IdentifierSDPSession Description ProtocolV2XVehicle-to-Everything4V2X Communication Provisioning MO4.1OverviewThe V2X communication provisioning MO is used to manage the V2X configuration parameters in a UE supporting 3GPPTS24.3864.The MO identifier is: urn:oma:mo:ext-3gpp-V2X-communication-provisioning:1.0.The OMA DM access control list (ACL) property mechanism (see OMA-ERELD-DM-V1_23) can be used to grant or deny access rights to OMA DM servers in order to modify nodes of the V2X communication provisioning MO.In order to request provisioning of the V2X communication provisioning MO, the UE includes in the Package 1 (see OMA-TS-DM_Protocol-V1_25) a Generic Alert message (along with other commands):-with the Type element set to urn:oma:mo:ext-3gpp-V2X-communication-provisioning:1.0;-with the LocURI element (inside the Source element) set to the address of the V2X communication provisioning MO as specified by OMA-TS-DM_Protocol-V1_25; and-without the Data element.The V2X communication provisioning MO consists of the nodes described in figure4.1-1.NOTE:In this release of the document, charging configuration parameters in the V2X communication provisioning MO are not specified.Figure4.1-1: The V2X communication provisioning MO (part 1)Figure4.1-2: The V2X communication provisioning MO (part 2)Figure4.1-3: The V2X communication provisioning MO (part 3)Figure4.1-4: The V2X communication provisioning MO (part 4)Figure4.1-5: The V2X communication provisioning MO (part 5)Figure4.1-6: The V2X communication provisioning MO (part 6)Figure4.1-7: The V2X communication provisioning MO (part 7)Figure4.1-8: The V2X communication provisioning MO (part 8)5MO configuration parameters5.1GeneralThis clause describes the configuration parameters of the V2X communication provisioning MO.5.2Node: This node acts as a placeholder for one or more accounts for a fixed node.-Occurrence: OneOrMore-Format: node-Access Types: Get, Replace-Values: N/AThis node is mandatory if the UE supports the UE role specified in 3GPPTS24.3864.NOTE:One node is normally used. More nodes are only used in case the terminal supports multiple UICCs.5.3/NameThis node contains a name for the V2X configuration parameters.-Occurrence: One-Format: chr-Access Types: Get, Replace-Values: 5.4Configuration parameters for V2X provisioning5.4.1/V2XProvisioningThe V2XProvisioning node contains the configuration parameters for V2X provisioning.-Occurrence: One-Format: node-Access Types: Get, Replace-Values: N/A5.4.2/V2XProvisioning/V2XControlFunctionAddressThe V2XControlFunctionAddress leaf indicates the V2X control function address.-Occurrence: ZeroOrOne-Format: chr-Access Types: Get, Replace-Values: an FQDN or an IP address5.4.3/V2XProvisioning/ToConRefsThe ToConRefs node is used to allow application to refer to a collection of connectivity definitions. Several connectivity parameters can be listed for a given application under this node.This node contains configuration parameters for establishment of the PDN connection for reaching the V2X control function. -Occurrence: ZeroOrOne-Format: node-Access Types: Get, Replace-Values: N/A5.4.4/V2XProvisioning/ToConRefs/This run-time node acts as a placeholder for each reference to connectivity parameters.-Occurrence: OneOrMore-Format: node-Access Types: Get, Replace-Values: N/A5.4.5/V2XProvisioning/ToConRefs/ConRefThe ConRef leaf indicates a specific linkage to connectivity parameters.-Occurrence: One-Format: chr-Access Types: Get, Replace-Values: 5.5Configuration parameters for V2X communication over PC55.5.1/V2XoverPC5The V2XoverPC5 node contains the configuration parameters for V2X communication over PC5.-Occurrence: One-Format: node-Access Types: Get, Replace-Values: N/A5.5.2/V2XoverPC5/ExpirationThe Expiration leaf indicates the expiration time of validity of the configuration parameters for V2X communication over PC5.-Occurrence: One-Format: int-Access Types: Get, Replace-Values: a 40 bits unsigned integer value indicating a UTC time, in seconds since midnight UTC of January 1, 1970 (not counting leap seconds).5.5.3/V2XoverPC5/ServedByEUTRANThe ServedByEUTRAN node contains the configuration parameters for V2X communication over PC5 when the UE is served by E-UTRAN.-Occurrence: One-Format: node-Access Types: Get, Replace-Values: N/A5.5.4/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNsThe AuthorizedPLMNs node contains a list of PLMNs in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRAN.-Occurrence: One-Format: node-Access Types: Get, Replace-Values: N/A5.5.5/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/This node acts as a placeholder for a PLMN in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRAN.-Occurrence: ZeroOrMore-Format: node-Access Types: Get, Replace-Values: N/A5.5.6/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/PLMNThe PLMN leaf indicates a PLMN code of a PLMN in which the UE is authorized to use V2X communication over PC5 when the UE is served by E-UTRAN.-Occurrence: One-Format: chr-Access Types: Get, Replace-Values: