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

3GPP TS 24.385 V2.0.0 (2017-02) Technical Specification 3rd 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) 69 Release 14 Keywords V2X, Management object 3GPP Postal address 3GPP support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.org Copyright Notification No 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 members 3GPP? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE? is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association Contents Foreword 6 1 Scope 7 2 References 7 3 Definitions and abbreviations 8 3.1 Definitions 8 3.2 Abbreviations 8 4 V2X Communication Provisioning MO 8 4.1 Overview 8 5 MO configuration parameters 12 5.1 General 12 5.2 Node: <X> 13 5.3 <X>/Name 13 5.4 Configuration parameters for V2X provisioning 13 5.4.1 <X>/V2XProvisioning 13 5.4.2 <X>/V2XProvisioning/V2XControlFunctionAddress 13 5.4.3 <X>/V2XProvisioning/ToConRefs 13 5.4.4 <X>/V2XProvisioning/ToConRefs/<X> 14 5.4.5 <X>/V2XProvisioning/ToConRefs/<X>/ConRef 14 5.5 Configuration parameters for V2X communication over PC5 14 5.5.1 <X>/V2XoverPC5 14 5.5.2 <X>/V2XoverPC5/Expiration 14 5.5.3 <X>/V2XoverPC5/ServedByEUTRAN 15 5.5.4 <X>/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs 15 5.5.5 <X>/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/<X> 15 5.5.6 <X>/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/<X>/PLMN 15 5.5.7 <X>/V2XoverPC5/NotServedByEUTRAN 15 5.5.8 <X>/V2XoverPC5/NotServedByEUTRAN/Authorized 16 5.5.9 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters 16 5.5.10 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X> 16 5.5.11 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ RadioParametersContents 16 5.5.12 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea 17 5.5.13 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea/Polygon 17 5.5.14 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea/Polygon/<X> 17 5.5.15 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea/Polygon/<X>/Coordinates 17 5.5.16 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea/Polygon/<X>/Coordinates/<X> 18 5.5.17 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea/Polygon/<X>/Coordinates/<X>/Latitude 18 5.5.18 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ GeographicalArea/Polygon/<X>/Coordinates/<X>/Longitude 18 5.5.19 <X>/V2XoverPC5/NotServedByEUTRAN/RadioParameters/<X>/ OperatorManaged 18 5.5.20 <X>/V2XoverPC5/AuthorizedV2XServiceList 19 5.5.21 <X>/V2XoverPC5/AuthorizedV2XServiceList/<X> 19 5.5.22 <X>/V2XoverPC5/AuthorizedV2XServiceList/<X>/ V2XServiceIdentifier 19 5.5.23 <X>/V2XoverPC5/AuthorizedV2XServiceList/<X>/ DestinationLayer2ID 19 5.5.24 <X>/V2XoverPC5/PPPPtoPDBMappingRule 19 5.5.25 <X>/V2XoverPC5/PPPPtoPDBMappingRule/<X> 20 5.5.26 <X>/V2XoverPC5/PPPPtoPDBMappingRule/<X>/ ProSePerPacketPriority 20 5.5.27 <X>/V2XoverPC5/PPPPtoPDBMappingRule/<X>/ PacketDelayBudget 20 5.5.28 <X>/V2XoverPC5/TimerT5000 20 5.6 Configuration parameters for V2X communication over LTE-Uu 21 5.6.1 <X>/V2XoverLTEUu 21 5.6.2 <X>/V2XoverLTEUu/Expiration 21 5.6.3 <X>/V2XoverLTEUu/ToConRefs 21 5.6.4 <X>/V2XoverLTEUu/ToConRefs/<X> 21 5.6.5 <X>/V2XoverLTEUu/ToConRefs/<X>/ConRef 21 5.6.6 <X>/V2XoverLTEUu/AuthorizedPLMNs 22 5.6.7 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X> 22 5.6.8 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/PLMN 22 5.6.9 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig 22 5.6.10 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig/ TMGI 23 5.6.11 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig/ SAIList 23 5.6.12 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig/ SAIList/<X> 23 5.6.13 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig/ SAIList/<X>/SAI 23 5.6.14 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig/ Frequency 24 5.6.15 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/V2XASMBMSConfig/ SDPInV2XASMBMSConfig 24 5.6.16 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated 24 5.6.17 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs 25 5.6.18 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X> 25 5.6.19 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig 25 5.6.20 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig/TMGI 25 5.6.21 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig/SAIList 26 5.6.22 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig/SAIList/<X> 26 5.6.23 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig/SAIList/<X>/SAI 26 5.6.24 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig/Frequency 26 5.6.25 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XMBMSConfigs/<X>/V2XMBMSConfig/ SDPInV2XMBMSConfig 27 5.6.26 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XASAddresses 27 5.6.27 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XASAddress/<X> 27 5.6.28 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XASAddress/<X>/L3Address 27 5.6.29 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XASAddress/<X>/UDPPort 28 5.6.30 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XASAddress/<X>/ GeographicalArea 28 5.6.31 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierUnrelated/V2XASAddress/<X>/GeographicalArea/Polygon 28 5.6.32 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated 28 5.6.33 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList 29 5.6.34 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X> 29 5.6.35 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/ V2XServiceIdentifier 29 5.6.36 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/ V2XMBMSConfigs 29 5.6.37 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/ V2XMBMSConfigs/<X> 30 5.6.38 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig 30 5.6.39 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig/TMGI 30 5.6.40 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig/SAIList 31 5.6.41 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig/SAIList/<X> 31 5.6.42 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig/SAIList/<X>/SAI 31 5.6.43 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig/Frequency 31 5.6.44 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/V2XMBMSConfigs/<X>/ V2XMBMSConfig/SDPInV2XMBMSConfig 32 5.6.45 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/AuthorizedV2XServiceList/<X>/ V2XASAddresses 32 5.6.46 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs 32 5.6.47 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X> 32 5.6.48 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig 33 5.6.49 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig/TMGI 33 5.6.50 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig/SAIList 33 5.6.51 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig/SAIList/<X> 33 5.6.52 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig/SAIList/<X>/SAI 34 5.6.53 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig/Frequency 34 5.6.54 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XMBMSConfigs/<X>/ V2XMBMSConfig/SDPInV2XMBMSConfig 34 5.6.55 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses 35 5.6.56 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses/<X> 35 5.6.57 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses/<X>/TypeOfData 35 5.6.58 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/ DefaultV2XASAddresses/<X>/V2XMessageFamily 35 5.6.59 <X>/V2XoverLTEUu/AuthorizedPLMNs/<X>/ V2XServiceIdentifierRelated/DefaultV2XASAddresses/<X>/ V2XASAddresses 36 5.7 <X>/Ext 36 Annex A (informative): V2X Communication Provisioning MO DDF 37 Annex B (informative): Change history 69 Foreword This 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.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. 1 Scope The 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_2[3]. 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.386[4]. 2 References The 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. [1] 3GPPTR21.905: "Vocabulary for 3GPP Specifications". [2] 3GPPTS23.285: "Architecture enhancements for V2X services". [3] OMA-ERELD-DM-V1_2: "Enabler Release Definition for OMA Device Management". [4] 3GPPTS24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3". [5] OMA-TS-DM_Protocol-V1_2: "OMA Device Management Protocol". [6] ISO8601:2004: "Data elements and interchange formats -- Information interchange -- Representation of dates and times". [7] 3GPPTS23.003: "Numbering, addressing and identification". [8] 3GPPTS36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC) protocol specification". [9] 3GPPTS23.032: "Universal Geographical Area Description (GAD)". [10] ISOTS17419ITS-AIDAssignedNumbers: http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf [11] 3GPPTS36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception". [12] 3GPPTS23.303: "Proximity-based Services (ProSe); Stage2". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPPTR21.905[1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPPTR21.905[1]. For the purposes of the present document, the following terms and definitions given in 3GPPTS23.003[7] apply: TMGI 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPPTR21.905[1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPPTR21.905[1]. DDF Device Description Framework MO Management Object PDB Packet Delay Budget PPPP ProSe Per-Packet Priority SAI Service Area Identifier SDP Session Description Protocol V2X Vehicle-to-Everything 4 V2X Communication Provisioning MO 4.1 Overview The V2X communication provisioning MO is used to manage the V2X configuration parameters in a UE supporting 3GPPTS24.386[4]. 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_2[3]) 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_2[5]) 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_2[5]; 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) 5 MO configuration parameters 5.1 General This clause describes the configuration parameters of the V2X communication provisioning MO. 5.2 Node: <X> 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/A This node is mandatory if the UE supports the UE role specified in 3GPPTS24.386[4]. NOTE: One node is normally used. More nodes are only used in case the terminal supports multiple UICCs. 5.3 <X>/Name This node contains a name for the V2X configuration parameters. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: <User displayable name> 5.4 Configuration parameters for V2X provisioning 5.4.1 <X>/V2XProvisioning The V2XProvisioning node contains the configuration parameters for V2X provisioning. - Occurrence: One - Format: node - Access Types: Get, Replace - Values: N/A 5.4.2 <X>/V2XProvisioning/V2XControlFunctionAddress The V2XControlFunctionAddress leaf indicates the V2X control function address. - Occurrence: ZeroOrOne - Format: chr - Access Types: Get, Replace - Values: an FQDN or an IP address 5.4.3 <X>/V2XProvisioning/ToConRefs The 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/A 5.4.4 <X>/V2XProvisioning/ToConRefs/<X> This run-time node acts as a placeholder for each reference to connectivity parameters. - Occurrence: OneOrMore - Format: node - Access Types: Get, Replace - Values: N/A 5.4.5 <X>/V2XProvisioning/ToConRefs/<X>/ConRef The ConRef leaf indicates a specific linkage to connectivity parameters. - Occurrence: One - Format: chr - Access Types: Get, Replace - Values: <A network access point object> 5.5 Configuration parameters for V2X communication over PC5 5.5.1 <X>/V2XoverPC5 The V2XoverPC5 node contains the configuration parameters for V2X communication over PC5. - Occurrence: One - Format: node - Access Types: Get, Replace - Values: N/A 5.5.2 <X>/V2XoverPC5/Expiration The 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 <X>/V2XoverPC5/ServedByEUTRAN The 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/A 5.5.4 <X>/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs The 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/A 5.5.5 <X>/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/<X> 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/A 5.5.6 <X>/V2XoverPC5/ServedByEUTRAN/AuthorizedPLMNs/<X>/PLMN The 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: <