TS 29.388 V1.0.0 (2017-03) V2X Control Function to Home Subscriber Server (HSS) aspects (V4);

《TS 29.388 V1.0.0 (2017-03) V2X Control Function to Home Subscriber Server (HSS) aspects (V4);》由會(huì)員分享，可在線閱讀，更多相關(guān)《TS 29.388 V1.0.0 (2017-03) V2X Control Function to Home Subscriber Server (HSS) aspects (V4);（27頁(yè)珍藏版）》請(qǐng)?jiān)谘b配圖網(wǎng)上搜索。

3GPP TS 29.388 V1.0.0 (2017-03) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; V2X Control Function to Home Subscriber Server (HSS) aspects (V4); 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.388 V1.0.0 (2017-03) 27 Release 14 Keywords 3GPP, V2X, HSS 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 5 1 Scope 6 2 References 6 3 Definitions and abbreviations 7 3.1 Definitions 7 3.2 Abbreviations 7 4 General Description 7 4.1 Introduction 7 5 Procedure Description 7 5.1 Introduction 7 5.2 V2X Subscriber Information Retrieval 7 5.2.1 General 7 5.2.2 Detailed Behaviour of the V2X Control Function 8 5.2.3 Detailed Behaviour of the HSS 8 5.3 Update V2X Subscriber Data 9 5.3.1 General 9 5.3.2 Detailed behaviour of the V2X Control Function 10 5.3.3 Detailed behaviour of the HSS 11 5.4 Notification Procedure 11 5.4.1 General 11 5.4.2 Detailed Behaviour of the V2X Control Function 12 5.4.3 Detailed Behaviour of the HSS 12 5.5 Reset 13 5.5.1 General 13 5.5.2 Detailed behaviour of the V2X Control Function 13 5.5.3 Detailed behaviour of the HSS 14 6 Protocol Specification and Implementations 14 6.1 Introduction 14 6.1.1 Use of Diameter base protocol 14 6.1.2 Securing Diameter Messages 14 6.1.3 Accounting Functionality 14 6.1.4 Use of Sessions 14 6.1.5 Transport Protocol 14 6.1.6 Routing Considerations 15 6.1.7 Advertising Application Support 15 6.1.8 Diameter Application Identifier 15 6.1.9 Use of the Supported-Features AVP 15 6.2 Commands 16 6.2.1 Introduction 16 6.2.2 Command-Code Values 16 6.2.3 ProSe-Subscriber-Information-Request (PIR) Command 16 6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command 17 6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command 17 6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command 18 6.2.7 ProSe-Notify-Request (PNR) Command 18 6.2.8 ProSe-Notify-Answer (PNA) Command 18 6.2.9 Reset-Request (RSR) Command 19 6.2.10 Reset-Answer (RSA) Command 19 6.3 AVPs 20 6.3.1 General 20 6.3.2 V2X-Subscription-Data 21 6.3.3 V2X-PC5-Allowed-PLMN 21 6.3.4 V2X-Update-Flags 21 6.3.5 V2X-Notify-Flags 21 6.3.6 OC-Supported-Features 22 6.3.7 OC-OLR 22 6.3.8 DRMP 22 6.4 Result-Code AVP and Experimental-Result AVP Values 22 6.4.1 General 22 6.4.2 Success 22 6.4.3 Permanent Failures 22 6.4.3.1 General 22 6.4.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) 22 6.4.3.3 DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION (5690) 23 6.4.3.4 DIAMETER_ERROR_V2X_NOT_ALLOWED (5691) 23 Annex A (normative): Diameter overload control mechanism 24 A.1 General 24 A.2 HSS behaviour 24 A.3 V2X Control Function behaviour 24 Annex B (Informative): Diameter overload node behaviour 25 B.1 Message prioritization 25 Annex C (normative): Diameter message priority mechanism 26 C.1 General 26 C.2 V4 interface 26 C.2.1 General 26 C.2.2 HSS and V2X Control Function behaviour 26 Annex D (informative): Change history 27 Foreword This 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.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 describes the Diameter-based V4 interface between the V2X Control Function and the Home Subscriber Server (HSS) defined for V2X services. This specification defines the Diameter application for V4 reference point between the V2X Control Function and the HSS. The interactions between the V2X Control Function and the HSS are specified. The stage 2 description for V2X service features in EPS is specified in 3GPPTS23.285[2]. 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; Stage 2". [3] IETFRFC6733: "Diameter Base Protocol". [4] 3GPPTS33.210: "3G Security; Network Domain Security; IP Network Layer Security". [5] IETFRFC4960: "Stream Control Transmission Protocol". [6] 3GPPTS29.229: "Cx and Dx interfaces based on the Diameter protocol". [7] IETFRFC5234: "Augmented BNF for Syntax Specifications: ABNF". [8] 3GPPTS23.003: "Numbering, addressing and identification". [9] 3GPPTS29.228: "IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and Message Elements". [10] 3GPPTS29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on Diameter Protocol". [11] 3GPPTS29.329: "Sh Interface based on the Diameter protocol". [12] IETFRFC7683: "Diameter Overload Indication Conveyance". [13] IETFRFC7944: "Diameter Routing Message Priority". [14] 3GPPTS23.007: "Restoration procedures". [15] 3GPPTS29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects". 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]. example: text used to clarify abstract rules by applying them literally. 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]. ProSe Proximity-based Services V2X Vehicle-to-Everything 4 General Description 4.1 Introduction The V4 reference point between the V2X Control Function and the HSS is defined in the 3GPPTS23.285[2]. This document describes the V4 interface related procedures, message parameters and protocol specifications. The V4 interface allows the V2X Control Function to retrieve V2X related subscription data in order to authorise access from the UE for V2X services. 5 Procedure Description 5.1 Introduction This subclause describes the Diameter-based V4 interface related procedures and information elements exchanged between the V2X Control Function and the HSS. 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.228[9]. 5.2 V2X Subscriber Information Retrieval 5.2.1 General This procedure shall be used between the V2X Control Function and the HSS for authorization of the UE for V2X services. The procedure shall be invoked by the V2X Control Function and is used: - to request V2X related subscription data. This procedure is mapped to the commands ProSe-Subscriber-Information-Request/Answer (PIR/PIA) in the Diameter application specified in clause6. Table5.2.1-1 and table5.2.1-2 detail the involved information elements. Table 5.2.1-1: V2X Subscriber Information Retrieval Request Information Element Name Mapping to Diameter AVP Cat. Description IMSI User-Name (See IETFRFC6733[3]) M This information element shall contain the user IMSI, formatted according to 3GPPTS 23.003[8], subclause2.2. Supported Features (See 3GPPTS29.229[6]) Supported-Features O If present, this information element shall contain the list of features supported by the origin host. Table 5.2.1-2: V2X Subscriber Information Retrieval Answer Information Element Name Mapping to Diameter AVP Cat. Description Result (See 6) Result-Code / Experimental-Result M This 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 V4 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 - Unknown V2X Subscription - V2X Not Allowed V2X Subscription Data (See 6.3.2) V2X-Subscription-Data C This information element shall contain the V2X Subscription Data that gives the user permission to use V2X. MSISDN (See 3GPPTS29.329 [11]) MSISDN C This information element shall contain the user MSISDN, formatted according to 3GPPTS29.329 [11]. It shall be present if available. Visited PLMN Id (See 3GPPTS29.272[10]) Visited-PLMN-Id C This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPPTS23.003[8]. It shall be present if the UE is roaming in a PLMN different from the Home PLMN. Supported Features (See 3GPPTS29.229[6]) Supported-Features O If present, this information element shall contain the list of features supported by the origin host. Reset-IDs (See 3GPPTS29.272[10]) Reset-ID O The Reset-ID uniquely identifies a fallible resource in the HSSs realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. 5.2.2 Detailed Behaviour of the V2X Control Function The V2X Control Function shall make use of this procedure to request V2X related subscription data. If the V2X Control Function retrieved the V2X related subscription data, the V2X Control Function shall perform the authorisation for V2X as described in the 3GPPTS23.285[2]. 5.2.3 Detailed Behaviour of the HSS When receiving a V2X Subscriber Information Retrieval Request the HSS shall check if the IMSI for whom data is requested exists in the HSS. If not, an Experimental-Result of DIAMETER_ERROR_USER_UNKNOWN shall be returned. If the IMSI exists but there is not any V2X subscription data for the IMSI, the HSS shall return an Experimental-Result of DIAMETER_ERROR_UNKNOWN_V2X_SUBSCRIPTION. If the UE is not allowed to use V2X in the visited PLMN, the HSS shall return an Experimental-Result of DIAMETER_ERROR_V2X_NOT_ALLOWED. Otherwise, the HSS shall return a Result-Code of DIAMETER_SUCCESS and shall store V2X Control Function identity (the V2X Control Function identity is received within the Origin-Host AVP) and download the V2X subscription data to the V2X Control Function. The HSS shall provide the Visited PLMN ID of where the UE is registered if the UE is roaming in a PLMN different from the Home PLMN. 5.3 Update V2X Subscriber Data 5.3.1 General The Update V2X Subscriber Data procedure shall be used between the V2X Control Function and the HSS to update the subscriber related data downloaded by means of the V2X Subscriber Information Retrieval operation (see subclause5.2) and stored in the V2X Control Function. It shall be used to update subscriber related data in the V2X Control Function due to administrative changes of the user data in the HSS, i.e. if the user was given a subscription and the subscription has changed. It shall be used at least to perform the following: - update of all of V2X subscription data of the subscriber, - update of a subset of the V2X subscription data of the subscriber, - deletion of the V2X subscription data of the subscriber. The procedure will also be triggered when the VPLMN has changed. This procedure is mapped to the commands Update-ProSe-Subscriber-Data-Request/Answer (UPR/UPA) in the Diameter application specified in clause6. Table5.3.1-1 specifies the involved information elements for the request. Table5.3.1-2 specifies the involved information elements for the answer. Table 5.3.1-1: Update V2X Subscriber Data Request Information element name Mapping to Diameter AVP Cat. Description IMSI User-Name (See IETFRFC6733[3]) M This information element shall contain the user IMSI, formatted according to 3GPPTS23.003[8], subclause2.2. Supported Features (See 3GPPTS29.229[6]) Supported-Features O If present, this information element shall contain the list of features supported by the origin host. V2X Subscription Data (See 6.3.2) V2X-Subscription-Data C This information element shall contain the V2X Subscription Data that gives the user permission to use V2X service. Visited PLMN Id (See 3GPPTS29.272[10]) Visited-PLMN-Id C This IE shall contain the MCC and the MNC of the PLMN where the UE is registered, see 3GPPTS23.003[8]. It shall be present if the UE is roaming in a PLMN different from the Home PLMN. V2X Update Flags (See 6.3.4) V2X-Update-Flags M This Information Element shall contain a bit mask. See subclause6.3.6 for the meaning of the bits. Reset-IDs (See 3GPPTS29.272[10]) Reset-ID O The Reset-ID uniquely identifies a fallible resource in the HSSs realm on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. Table 5.3.1-2: Update V2X Subscriber Data Answer Information element name Mapping to Diameter AVP Cat. Description Supported Features (See 3GPPTS29.229[6]) Supported-Features O If present, this information element shall contain the list of features supported by the origin host. Result (See 6.4) Result-Code / Experimental-Result M This 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 V4 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 in this case: - User Unknown - Unknown V2X Subscription 5.3.2 Detailed behaviour of the V2X Control Function When receiving an Update V2X Subscriber Data request, the V2X Control Function shall check whether the IMSI is known. If it is not known, a result code of DIAMETER_ERROR_USER_UNKNOWN shall be returned. If it is known, the V2X Control Function shall update the corresponding data according to the indication as sent in the request, and acknowledge the Update V2X Subscriber Data message by returning an Update V2X Subscriber Data Answer. If the V2X-Update-Flags indicates that the V2X subscription data is to be deleted, the V2X Control Function shall delete the associated V2X UE context if it has been stored before. If the update of the subscription data succeeds in the V2X Control Function, the Result-Code shall be set to DIAMETER_SUCCESS. If the V2X Control Function cannot fulfil the received request for other reasons, e.g. due to a database error, it shall set the Result-Code to DIAMETER_UNABLE_TO_COMPLY. In this case, the V2X Control Function shall mark the subscription record "Subscriber data to be restored in the HSS". 5.3.3 Detailed behaviour of the HSS The HSS shall make use of this procedure to update the relevant subscriber related data in the V2X Control Function to replace a specific part of the user data stored in the V2X Control Function with the data sent. If the V2X related subscription data is updated or revoked, the HSS sends the updated V2X subscription data to the V2X Control Function. The HSS shall include the V2X-Update-Flags to indicate which part of the data is updated. If all of the V2X subscription data is to be removed, the HSS shall set the "Removal of all V2X Subscription Data" bit of the V2X-Update-Flags, and the HSS shall delete the V2X Control Function Identity if it is stored for this subscriber. 5.4 Notification Procedure 5.4.1 General This procedure shall be used between the V2X Control Function and the HSS when the HSS needs to be notified about: - revocation of authorization for V2X service on one PLMN. - removal of the subscription data from the V2X Control Function either by an MMI interaction or automatically. This procedure is mapped to the commands ProSe-Notify-Request/Answer (PNR/PNA) in the Diameter application specified in clause6. Table5.4.1-1 and table5.4.1-2 detail the involved information elements. Table 5.4.1-1: V2X Notify Request Information Element Name Mapping to Diameter AVP Cat. Description IMSI User-Name (See IETFRFC6733[3]) C This information element shall contain the user IMSI, formatted according to 3GPPTS23.003[8], subclause2.2. It shall be present if the revocation is for a specific UE. Supported Features (See 3GPPTS29.229[6]) Supported-Features O If present, this information element shall contain the list of features supported by the origin host. PLMN ID (see 3GPPTS29.272[10]) Visited-PLMN-Id C This information element shall contain the MCC and the MNC of the PLMN where the UE’s authorization for V2X service is revoked, see 3GPPTS23.285 [2]. It shall be present if the V2X Control Function revokes the authorization for V2X service in a specific PLMN. V2X Notify Flags (see 6.3.5) V2X-Notify-Flags C This Information Element shall contain a bit mask. See 6.3.7 for the meaning of the bits. Table 5.4.1-2: V2X Notify Answer Information Element Name Mapping to Diameter AVP Cat. Description Result (See 6) Result-Code / Experimental-Result M This 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 AV