TS 29.389 V1.0.0 (2017-03) Inter-V2X Control Function Signalling aspects (V6);

3GPP TS 29.389 V1.0.0 (2017-03)Technical Specification3rd Generation Partnership Project;Technical Specification Group Core Network and Terminals;Inter-V2X Control Function Signalling aspects (V6);Stage 3(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 29.389 V1.0.0 (2017-03)20Release 14.Keywords3GPP, V2X3GPPPostal 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 AssociationContentsForeword51Scope62References63Definitions and abbreviations73.1Definitions73.3Abbreviations74General Description74.1Introduction75Procedure Description75.1Introduction75.2V2X Service Authorization75.2.1General75.2.2Detailed behaviour of the V2X Control Function in the HPLMN85.2.3Detailed behaviour of the V2X Control Function in the VPLMN96Protocol Specification and Implementations96.1Introduction96.1.1Use of Diameter base protocol96.1.2Securing Diameter Messages96.1.3Accounting functionality96.1.4Use of sessions96.1.5Transport protocol106.1.6Routing considerations106.1.7Advertising Application Support106.1.8Diameter Application Identifier106.1.9Use of the Supported-Features AVP106.2Commands116.2.1Introduction116.2.2Command-Code values116.2.3ProSe-Authorization-Request (PAR) Command116.2.4ProSe-Authorization-Answer (PAA) Command126.3Information Elements126.3.1General126.3.2V2X-Authorization-Data136.3.3V2X-Permission-in-VPLMN146.3.4V2X-Application-Server146.3.5Application-Server146.3.6Geographical-Information146.3.7OC-Supported-Features146.3.8OC-OLR146.3.9DRMP146.4Result-Code AVP and Experimental-Result AVP Values156.4.1General156.4.2Success156.4.3Permanent Failures156.4.3.1General156.4.3.2DIAMETER_ERROR_USER_UNKNOWN (5001)156.4.3.3DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION (5690)156.4.3.4DIAMETER_ERROR_V2X_NOT_ALLOWED (5691)15Annex A (normative):Diameter overload control mechanism16A.1General16A.2Responding V2X Control Function behaviour16A.3Requesting V2X Control Function behaviour16Annex B (Informative):Diameter overload node behaviour18B.1Message prioritization18Annex C (normative):Diameter message priority mechanism19C.1General19C.2V6 interfaces19C.2.1General19C.2.2V2X Control Function behaviour19Annex D (informative): Change history20ForewordThis Technical Specification 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 describes the Diameter-based interfaces between the V2X Control Function in the HPLMN and the V2X Control Function in the VPLMN (V6 interface).This specification defines the Diameter application for V6 reference points between the V2X Control Functions. The interactions between the V2X Control Functions are specified.The stage 2 description for V2X service features in EPS is specified in 3GPPTS23.2852.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; Stage 2.3IETFRFC6733: Diameter Base Protocol. 43GPPTS33.210: 3G Security; Network Domain Security; IP Network Layer Security.5IETFRFC4960: Stream Control Transmission Protocol.63GPPTS29.229: Cx and Dx interfaces based on the Diameter protocol.7IETFRFC5234: Augmented BNF for Syntax Specifications: ABNF.83GPPTS23.003: Numbering, addressing and identification.93GPPTS29.228: IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements.103GPPTS29.272: Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol.113GPPTS29.329: Sh Interface based on the Diameter protocol.12IETFRFC7683: Diameter Overload Indication Conveyance.133GPPTS29.336: Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications.143GPPTS32.299: Telecommunication management; Charging management; Diameter charging applications.15IETFRFC7944: Diameter Routing Message Priority. 163GPPTS29.388: V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4).173GPPTS29.345: Inter-Proximity-services (ProSe) Function signalling aspects.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.example: text used to clarify abstract rules by applying them literally.3.3AbbreviationsFor 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.ProSeProximity-based ServicesV2XVehicle-to-Everything4General Description4.1IntroductionThe V6 reference point is defined between a V2X Control Function in the HPLMN and a V2X Control Function in the VPLMN.The definition of the V6 reference points and related functionalities are given in 3GPPTS23.2852.As defined in 3GPPTS23.2852, the V6 reference point is used for:-HPLMN control of service authorization for V2X.5Procedure Description5.1IntroductionThis subclause describes the Diameter-based V6 interface related procedures and Information elements exchanged between functional entities.In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the Cat. column. For the correct handling of the Information Element according to the category type, see the description detailed in clause6 of the 3GPPTS29.2289.5.2V2X Service Authorization5.2.1GeneralThe V2X Service Authorization Procedure shall be used between the V2X Control Function in the HPLMN and the V2X Control Function in the VPLMN to obtain service authorization information for V2X services. The procedure shall be invoked by the V2X Control Function in the HPLMN of the UE and is used:-to request service authorization information for V2X related to the UE from the V2X Control Function in the VPLMN;-to provide the V2X Control Function in the VPLMN with the UE identity (IMSI or MSISDN) in order to allow to perform charging:This procedure is mapped to the commands ProSe-Authorization-Request/Answer (PAR/PAA) in the Diameter application specified in clause6. Table5.2.1-1 specifies the involved information elements for the request.Table5.2.1-2 specifies the involved information elements for the answer.Table 5.2.1-1: V2X Service Authorization RequestInformation element nameMapping to Diameter AVPCat.DescriptionUE Identity(See 3GPPTS29.33613)User-IdentifierMThis information element shall contain either the user IMSI, formatted according to 3GPPTS23.0038, subclause2.2, or the user MSISDN, formatted according to 3GPPTS29.32911.PLMN Id(See 3GPPTS29.27210)Visited-PLMN-IdMThis IE shall contain the PLMN-Id (3GPPTS23.0038) of the network in which the V2X Control Function is located.Supported Features(See 3GPPTS29.2296)Supported-FeaturesOIf present, this information element shall contain the list of features supported by the origin host.Table 5.2.1-2: V2X Service Authorization AnswerInformation element nameMapping to Diameter AVPCat.DescriptionResult(See 6.4)Result-Code / Experimental-ResultMThis IE shall contain the result of the operation.The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter Base Protocol.The Experimental-Result AVP shall be used for V6 errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.The following errors are applicable:- User Unknown- Unauthorized Service- Unauthorized Service in this PLMNSupported Features(See 3GPPTS29.2296)Supported-FeaturesOIf present, this information element shall contain the list of features supported by the origin host.V2X Authorization Data(See 6.3.2)V2X-Authorization-DataCThis Information Element shall contain the V2X authorization information of the user. It shall be present if success is reported.Editors Note:It is FFS on how to support charging for V2X service.5.2.2Detailed behaviour of the V2X Control Function in the HPLMNThe V2X Control Function in the HPLMN shall make use of this procedure to request service authorization information for V2X related to the UE from the V2X Control Function in the VPLMN. The V2X Control Function shall include in the request the UE identity (IMSI or MSISDN) and the PLMN-Id identifying the PLMN of the requesting V2X Control Function.When receiving a V2X Service Authorization response from the V2X Control Function in the VPLMN, the V2X Control Function in the HPLMN shall check the result code. If it indicates SUCCESS, the V2X Control Function shall merge with its own policy.5.2.3Detailed behaviour of the V2X Control Function in the VPLMNWhen receiving a V2X Service Authorization request, the V2X Control Function in the VPLMN shall, in the following order:1.Check whether the UE Identity (IMSI or MSISDN) exists. If not, a Result Code of DIAMETER_ERROR_USER_UNKNOWN shall be returned.2.Check whether V2X is authorized for this UE Identity. If not, a Result Code of DIAMETER_ERROR_UNAUTHORIZED_SERVICE shall be returned.If there is an error in any of the above steps then the V2X Control Function shall stop processing the request and shall return the error code specified in the respective step. If the V2X Control Function cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or any of the required actions cannot be performed, it shall stop processing the request and set the Result Code to DIAMETER_UNABLE_TO_COMPLY.Otherwise, when the UE is authorized to use V2X over PC5 or V2X over MBMS in this PLMN, the V2X Control Function shall include the V2X-Authorization-Data AVP in the response to return V2X permissions and the V2X Application Server information, and shall set the Result Code to DIAMETER_SUCCESS.6Protocol Specification and Implementations6.1Introduction6.1.1Use of Diameter base protocolThe Diameter base protocol as specified in IETFRFC67333 shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified.6.1.2Securing Diameter MessagesFor secure transport of Diameter messages, see 3GPPTS33.2104.6.1.3Accounting functionalityAccounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the V6 interface.6.1.4Use of sessionsBetween the V2X Control Functions, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server.The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions.The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO_STATE_MAINTAINED (1), as described in IETFRFC67333. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses.6.1.5Transport protocolDiameter messages over the V6 interface shall make use of SCTP IETFRFC49605.6.1.6Routing considerationsThis subclause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host.The Destination-Realm AVP shall contain the network domain name of the targeted V2X Control Function. The network domain name is either known by the sending V2X Control Function or derived from the PLMN-Id of the targeted V2X Control Function to construct the EPC Home Network Realm/Domain, as indicated in 3GPPTS23.0038, subclause19.2.If a V2X Control Function knows the address/name of the V2X Control Function in charge of a given UE, and the associated network domain name, both the Destination-Realm and Destination-Host AVPs shall be present in the request. If a V2X Control Function knows only the network domain name, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Realm AVP is declared as mandatory and the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by a V2X Control Function. If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes.6.1.7Advertising Application SupportThe V2X Control Functions shall advertise support of the Diameter Inter V2X Control Functions Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands.The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETFRFC67333.6.1.8Diameter Application IdentifierThe Diameter Inter V2X Control Functions Application protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (http:/www.iana.org/assignments/enterprise-numbers) is 10415.The Diameter application identifier assigned to the Diameter Inter V2X Control Functions application is 16777356 (allocated by IANA). The Diameter application identifier is used over the V6 interface.6.1.9Use of the Supported-Features AVPWhen new functionality is introduced on the V6 interface, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. The usage of the Supported-Features AVP on the V6 interface is consistent with the procedures for the dynamic discovery of supported features as defined in subclause7.2 of 3GPPTS29.2296.When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. As defined in 3GPPTS29.2296, the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another.6.2Commands6.2.1IntroductionThis subclause defines the Command code values and related ABNF for each command described in this specification.6.2.2Command-Code valuesThis csublause defines Command-Code values for the Diameter Inter V2X Control Functions application used over the V6 interface as allocated by IANA.Every command is defined by means of the ABNF syntax IETFRFC52347, according to the rules in IETFRFC67333. In the case, the definition and use of an AVP is not specified in this document, the guidelines in IETFRFC67333 shall apply. The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node.NOTE:The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with