ETSI TS 129 344 V15.1.0 (2019-10)

Universal Mobile Telecommunications System (UMTS); LTE; Proximity-services (ProSe) function to Home Subscriber Server (HSS) aspects; Stage 3 (3GPP TS 29.344 version 15.1.0 Release 15)

RTS/TSGC-0429344vf10

General Information

• Status: Published
• Publication Date: 02-Oct-2019
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Completion
• Completion Date: 03-Oct-2019

Standards Content (Sample)

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Proximity-services (ProSe)
function to Home Subscriber Server (HSS) aspects;
Stage 3
(3GPP TS 29.344 version 15.1.0 Release 15)

3GPP TS 29.344 version 15.1.0 Release 15 1 ETSI TS 129 344 V15.1.0 (2019-10)

Reference
RTS/TSGC-0429344vf10
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 2 ETSI TS 129 344 V15.1.0 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 3 ETSI TS 129 344 V15.1.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 General Description . 7
4.1 Introduction . 7
5 Procedure Descriptions. 7
5.1 Introduction . 7
5.2 ProSe Subscriber Information Retrieval . 8
5.2.1 General . 8
5.2.2 Detailed Behaviour of the ProSe Function . 8
5.2.3 Detailed Behaviour of the HSS . 9
5.3 Update ProSe Subscriber Data . 9
5.3.1 General . 9
5.3.2 Detailed behaviour of the ProSe 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 ProSe 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 ProSe Function . 13
5.5.3 Detailed behaviour of the HSS . 14
5.6 Initial Location Information Retrieval . 14
5.6.1 General . 14
5.6.2 Detailed Behaviour of the ProSe Function . 15
5.6.3 Detailed Behaviour of the HSS . 15
6 Protocol Specification and Implementations . 16
6.1 Introduction . 16
6.1.1 Use of Diameter Base Protocol . 16
6.1.2 Securing Diameter Messages . 16
6.1.3 Accounting Functionality . 16
6.1.4 Use of Sessions . 16
6.1.5 Transport Protocol . 16
6.1.6 Routing Considerations . 16
6.1.7 Advertising Application Support . 17
6.1.8 Diameter Application Identifier . 17
6.1.9 Use of the Supported-Features AVP . 17
6.2 Commands . 17
6.2.1 Introduction. 17
6.2.2 Command-Code Values . 17
6.2.3 ProSe-Subscriber-Information-Request (PIR) Command . 18
6.2.4 ProSe-Subscriber-Information-Answer (PIA) Command . 18
6.2.5 Update-ProSe-Subscriber-Data-Request (UPR) Command . 19
6.2.6 Update-ProSe-Subscriber-Data-Answer (UPA) Command . 19
6.2.7 ProSe-Notify-Request (PNR) Command . 20
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 4 ETSI TS 129 344 V15.1.0 (2019-10)
6.2.8 ProSe-Notify-Answer (PNA) Command . 20
6.2.9 Reset-Request (RSR) Command . 20
6.2.10 Reset-Answer (RSA) Command . 21
6.2.11 ProSe-Initial-Location-Information-Request (PSR) Command . 21
6.2.12 ProSe-Initial-Location-Information-Answer (PSA) Command . 21
6.3 AVPs . 22
6.3.1 General . 22
6.3.2 ProSe-Subscription-Data . 23
6.3.3 ProSe-Permission . 23
6.3.4 ProSe-Allowed-PLMN . 24
6.3.5 ProSe-Direct-Allowed . 24
6.3.6 UPR-Flags. 25
6.3.7 PNR-Flags. 25
6.3.8 Feature-List AVP for the PC4a application . 26
6.3.9 ProSe-Initial-Location-Information . 26
6.3.10 MME-Name . 27
6.3.11 OC-Supported-Features . 27
6.3.12 OC-OLR . 27
6.3.13 Authorized-Discovery-Range . 27
6.3.14 DRMP . 27
6.3.15 Load . 27
6.4 Result-Code AVP and Experimental-Result AVP Values . 27
6.4.1 General . 27
6.4.2 Success . 27
6.4.3 Permanent Failures . 27
6.4.3.1 General . 27
6.4.3.2 DIAMETER_ERROR_USER_UNKNOWN (5001) . 28
6.4.3.3 DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION (5610) . 28
6.4.3.4 DIAMETER_ERROR_ PROSE_NOT_ALLOWED (5611) . 28
6.4.3.5 DIAMETER_ERROR_ UE_LOCATION_UNKNOWN (5612) . 28
Annex A (normative): Diameter overload control mechanism . 29
A.1 General . 29
A.2 HSS behaviour . 29
A.3 ProSe Function behaviour . 29
Annex B (Informative): Diameter overload node behaviour . 30
B.1 Message prioritization . 30
Annex C (normative): Diameter message priority mechanism . 31
C.1 General . 31
C.2 PC4a interface . 31
C.2.1 General . 31
C.2.2 HSS and ProSe Function behaviour . 31
Annex D (normative): Diameter load control mechanism . 32
D.1 General . 32
D.2 HSS behaviour . 32
D.3 ProSe Function behaviour . 32
Annex E (informative): Change history . 33
History . 34

ETSI
3GPP TS 29.344 version 15.1.0 Release 15 5 ETSI TS 129 344 V15.1.0 (2019-10)
Foreword
rd
This Technical Specification has been produced by the 3 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.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 6 ETSI TS 129 344 V15.1.0 (2019-10)
1 Scope
The present document describes the Diameter-based PC4a interface between the Proximity-based Services (ProSe)
Function and the Home Subscriber Server (HSS) defined for ProSe.
This specification defines the Diameter application for PC4a reference point between the ProSe Function and the
HSS.The interactions between the ProSe Function and the HSS are specified.
The stage 2 description for Proximity-based Services (ProSe) features in EPS is specified in 3GPP TS 23.303 [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
non-specific.
- 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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.303: "Proximity based services; Stage 2".
[3] Void.
[4] 3GPP TS 33.210: "3G Security; Network Domain Security; IP Network Layer Security".
[5] IETF RFC 4960: "Stream Control Transmission Protocol".
[6] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".
[7] 3GPP TS 23.003: "Numbering, addressing and identification".
[8] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF".
[9] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and
Message Elements".
[10] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on
Diameter Protocol".
[11] 3GPP TS 23.007: "Restoration procedures".
[12] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol".
[13] void
[14] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane
LCS".
[15] IETF RFC 7683: "Diameter Overload Indication Conveyance".
[16] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol
aspects; Stage 3".
[17] 3GPP TS 24.333: "Proximity-services (ProSe) Management Objects (MO); Stage 3".
[18] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting
packet based services and Packet Data Networks (PDN)".
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 7 ETSI TS 129 344 V15.1.0 (2019-10)
[19] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched
(PS) domain charging".
[20] 3GPP TS 32.298: "Charging Management; CDR parameter description".
[21] IETF RFC 7944: "Diameter Routing Message Priority".
[22] IETF RFC 8583: "Diameter Load Information Conveyance".
[23] IETF RFC 6733: "Diameter Base Protocol".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.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 TR 21.905 [1].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.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
3GPP TR 21.905 [1].
DRMP Diameter Routing Message Priority
DSCP Differentiated Services Code Point
ProSe Proximity-based Services
4 General Description
4.1 Introduction
The PC4a reference point between the ProSe Function and the HSS is defined in the 3GPP TS 23.303 [2].
This document describes the PC4a interface related procedures, message parameters and protocol specifications.
The PC4a interface allows the ProSe Function to retrieve ProSe related subscription data in order to authorise access
from the UE for ProSe.
5 Procedure Descriptions
5.1 Introduction
This clause describes the Diameter-based PC4a interface related procedures and information elements exchanged
between the ProSe 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 clause 6 of the 3GPP TS 29.228 [9].
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 8 ETSI TS 129 344 V15.1.0 (2019-10)
5.2 ProSe Subscriber Information Retrieval
5.2.1 General
This procedure shall be used between the ProSe Function and the HSS for authorization of the UE for ProSe. The
procedure shall be invoked by the ProSe Function and is used:
- to request ProSe related subscription data.
This procedure is mapped to the commands ProSe-Subscriber-Information-Request/Answer (PIR/PIA) in the Diameter
application specified in clause 6. Tables 5.2.1-1 and 5.2.1-2 detail the involved information elements.
Table 5.2.1-1: ProSe Subscriber Information Retrieval Request
Information Element Mapping to Diameter Cat. Description
Name AVP
IMSI User-Name (See M This information element shall contain the user
IETF RFC 6733 [23]) IMSI, formatted according to 3GPP TS 23.003 [7],
clause 2.2.
Supported Features Supported-Features O If present, this information element shall contain
(See 3GPP TS 29.229 [6]) the list of features supported by the origin host.

Table 5.2.1-2: ProSe Subscriber Information Retrieval Answer
Information Element Mapping to Cat. Description
Name Diameter AVP
Result Result-Code / M This IE shall contain the result of the operation.
(See 6) Experimental- The Result-Code AVP shall be used to indicate success / errors
Result as defined in the Diameter base protocol (see
IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a 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 ProSe Subscription
- ProSe Not Allowed
ProSe Subscription ProSe- C This information element shall contain the ProSe Subscription
Data Subscription-Data Data that gives the user permission to use ProSe.
(See 6.3.2)
MSISDN MSISDN C This information element shall contain the user MSISDN,
(See 3GPP TS 29.329 formatted according to 3GPP TS 29.329 [12]. It shall be present
[12]) if available.
Visited PLMN Id Visited-PLMN-Id C This IE shall contain the MCC and the MNC of the PLMN where
(See the UE is registered, see 3GPP TS 23.003 [7].
3GPP TS 29.272 [10]) It shall be present if the UE is roaming in a PLMN different from
the Home PLMN.
Supported Features Supported- O If present, this information element shall contain the list of
(See Features features supported by the origin host.
3GPP TS 29.229 [6])
Reset-IDs Reset-ID O The Reset-ID uniquely identifies a fallible resource in the HSS's
(See realm on which the user (IMSI) depends. In the event of a
3GPP TS 29.272 [10]) 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 ProSe Function
The ProSe Function shall make use of this procedure to request ProSe related subscription data.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 9 ETSI TS 129 344 V15.1.0 (2019-10)
If the ProSe Function retrieved the ProSe related subscription data, the ProSe Function shall perform the authorisation
for ProSe as described in the 3GPP TS 23.303 [2].
5.2.3 Detailed Behaviour of the HSS
When receiving a ProSe 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 ProSe subscription data for the IMSI, the HSS shall return an Experimental-Result
of DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION.
If the UE is not allowed to use ProSe in the visited PLMN, the HSS shall return an Experimental-Result of
DIAMETER_ERROR_PROSE_NOT_ALLOWED. Otherwise, the HSS shall return a Result-Code of
DIAMETER_SUCCESS and shall store ProSe Function identity (the ProSe Function identity is received within the
Origin-Host AVP) and download the ProSe subscription data to the ProSe 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 ProSe Subscriber Data
5.3.1 General
The Update ProSe Subscriber Data procedure shall be used between the ProSe Function and the HSS to update the
subscriber related data downloaded by means of the ProSe Subscriber Information Retrieval operation (see clause 5.2)
and stored in the ProSe Function.
It shall be used to update subscriber related data in the ProSe 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 ProSe subscription data of the subscriber,
- update of a subset of the ProSe subscription data of the subscriber,
- deletion of the ProSe 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 clause 6.
Table 5.3.1-1 specifies the involved information elements for the request.
Table 5.3.1-2 specifies the involved information elements for the answer.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 10 ETSI TS 129 344 V15.1.0 (2019-10)
Table 5.3.1-1: Update ProSe Subscriber Data Request
Information Mapping to Cat. Description
element name Diameter AVP
IMSI User-Name M This information element shall contain the user IMSI, formatted according
(See to 3GPP TS 23.003 [7], clause 2.2.
IETF RFC 673
3 [23])
Supported Supported- O If present, this information element shall contain the list of features
Features Features supported by the origin host.
(See
3GPP TS 29.2
29 [6])
ProSe ProSe- C This information element shall contain the ProSe Subscription Data that
Subscription Subscription- gives the user permission to use ProSe.
Data Data
(See 6.3.2)
Visited PLMN Visited-PLMN- C This IE shall contain the MCC and the MNC of the PLMN where the UE is
Id Id registered, see 3GPP TS 23.003 [7].
(See It shall be present if the UE is roaming in a PLMN different from the Home
3GPP TS 29.2 PLMN.
72 [10])
UPR Flags UPR-Flags M This Information Element shall contain a bit mask. See clause 6.3.6 for the
meaning of the bits.
Reset-IDs Reset-ID O The Reset-ID uniquely identifies a fallible resource in the HSS's realm on
(See which the user (IMSI) depends. In the event of a restart of the fallible
3GPP TS 29.2 resource a Reset message containing the Reset-ID will exactly identify the
72 [10]) impacted subscribers.

Table 5.3.1-2: Update ProSe Subscriber Data Answer
Information Mapping to Cat. Description
element name Diameter AVP
Supported Supported- O If present, this information element shall contain the list of features
Features Features supported by the origin host.
(See
3GPP TS 29.2
29 [6])
Result Result-Code / M This IE shall contain the result of the operation.
(See 6.4) Experimental- The Result-Code AVP shall be used to indicate success / errors as defined
Result in the Diameter base protocol (see IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a 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 ProSe Subscription
5.3.2 Detailed behaviour of the ProSe Function
When receiving a Update ProSe Subscriber Data request, the ProSe 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 ProSe Function shall update the corresponding data according to the indication as sent in the request,
and acknowledge the Update ProSe Subscriber Data message by returning an Update ProSe Subscriber Data Answer. If
the UPR-Flags indicates that the ProSe subscription data is to be deleted, the ProSe Function shall delete the associated
ProSe UE context if it has been stored before.
If the update of the subscription data succeeds in the ProSe Function, the Result-Code shall be set to
DIAMETER_SUCCESS.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 11 ETSI TS 129 344 V15.1.0 (2019-10)
If the ProSe 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 ProSe 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 the ProSe Function to
replace a specific part of the user data stored in the ProSe Function with the data sent.
If the ProSe related subscription data is updated or revoked, the HSS sends the updated ProSe subscription data to the
ProSe Function. The HSS shall include the UPR-Flags to indicate which part of the data is updated. If all of the ProSe
subscription data is to be removed, the HSS shall set the "Removal of all ProSe Subscription Data" bit of the UPR-
Flags, and the HSS shall delete the ProSe Function Identity if it is stored for this subscriber.
5.4 Notification Procedure
5.4.1 General
This procedure shall be used between the ProSe Function and the HSS when the HSS needs to be notified about:
- revocation of authorization for ProSe direct service on one PLMN.
- removal of the subscription data from the ProSe 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 clause 6. Tables 5.4.1-1 and 5.4.1-2 detail the involved information elements.
Table 5.4.1-1: ProSe Notify Request
Information Element Mapping to Diameter Cat. Description
Name AVP
IMSI User-Name (See C This information element shall contain the user IMSI,
IETF RFC 6733 [23]) formatted according to 3GPP TS 23.003 [7], clause 2.2.
It shall be present if the revocation is for a specific UE.
Supported Features Supported-Features O If present, this information element shall contain the list of
(See features supported by the origin host.
3GPP TS 29.229 [6])
PLMN ID (see Visited-PLMN-Id C This information element shall contain the MCC and the
3GPP TS 29.272 [10]) MNC of the PLMN where the UE's authorization for
ProSe direct service is revoked, see 3GPP TS 23.003 [7].
It shall be present if the ProSe Function revokes the
authorization for ProSe direct service in a specific PLMN.
PNR Flags (see PNR-Flags C This Information Element shall contain a bit mask. See
6.3.7) 6.3.7 for the meaning of the bits.

ETSI
3GPP TS 29.344 version 15.1.0 Release 15 12 ETSI TS 129 344 V15.1.0 (2019-10)
Table 5.4.1-2: ProSe Notify Answer
Information Element Mapping to Cat. Description
Name Diameter AVP
Result Result-Code / M This IE shall contain the result of the operation.
(See 6) Experimental- The Result-Code AVP shall be used to indicate success / errors
Result as defined in the Diameter base protocol (see
IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a 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 ProSe Subscription
Supported Features Supported- O If present, this information element shall contain the list of
(See Features features supported by the origin host.
3GPP TS 29.229 [6])
5.4.2 Detailed Behaviour of the ProSe Function
The ProSe Function shall make use of this procedure to revoke authorization for ProSe direct service.
The ProSe Function shall make use of this procedure to inform the HSS when the subscription data is deleted from the
ProSe Function database due to MMI interaction or automatically.
The ProSe Function shall send the updated ProSe Permission and the PLMN ID for which the ProSe Permission is to be
updated. If the revocation is for a single UE in the indicated PLMN, the ProSe Function shall include IMSI in the
request.
5.4.3 Detailed Behaviour of the HSS
When receiving a ProSe Notify Request the HSS shall check if the IMSI, if present in the message, 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 ProSe subscription data for the IMSI and the PLMN ID as indicated by the
Visited-PLMN-Id AVP in the request, the HSS shall return an Experimental-Result of
DIAMETER_ERROR_UNKNOWN_PROSE_SUBSCRIPTION.
If the PNR-Flags indicates revocation of authorization for ProSe direct service, and
- if the IMSI exists and there is ProSe subscription data for the IMSI and the PLMN ID as indicated by the
Visited-PLMN-Id AVP in the request, the HSS shall revoke ProSe direct service as indicated by the PNR Flags
received in the request on that PLMN for the user and update the ProSe Subscription data accordingly. The HSS
shall set the result code to DIAMETER_SUCCESS.
- if IMSI is not present in the message, the HSS shall check if there are any users subscribed to ProSe subscription
for the PLMN as indicated by the Visited-PLMN-Id AVP in the request, and if yes, revoke ProSe direct service
as indicated by the PNR Flags received in the request on that PLMN for all the impacted users and update their
ProSe Subscription data accordingly. The HSS shall set the result code to DIAMETER_SUCCESS.
If the PNR Flags indicates the subscription data is deleted from the ProSe Function, the HSS shall remove the ProSe
Function Identity for the subscriber and set the result code to DIAMETER_SUCCESS.
For any other reasons if the HSS cannot fulfil the received request, e.g. due to a database error, it shall set the result
code to DIAMETER_UNABLE_TO_COMPLY.
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 13 ETSI TS 129 344 V15.1.0 (2019-10)
5.5 Reset
5.5.1 General
The Reset Procedure shall be used by the HSS, after a restart, to indicate to the ProSe Function that a failure has
occurred.
The Reset Procedure may also be used by the HSS as part of operation and maintenance actions e.g. to allow planned
HSS outage without service interruption.
This procedure is mapped to the commands Reset-Request/Answer (RSR/RSA) in the Diameter application specified in
clause 6.
Table 5.5.1-1 specifies the involved information elements for the request.
Table 5.5.1-2 specifies the involved information elements for the answer.
Table 5.5.1-1: Reset Request
Information Mapping to Cat. Description
element name Diameter AVP
User Id List User-Id O This IE shall contain a list of ProSe User-Ids where a ProSe User-Id
(See comprises the leading digits of an IMSI (i.e. MCC, MNC, leading digits of
3GPP TS 29.2 MSIN) and it shall identify the set of subscribers whose IMSIs begin with
72 [10]) the User-Id. The HSS may include this information element if the occurred
failure is limited to subscribers identified by one or more User-Ids.
Supported Supported- O If present, this information element shall contain the list of features
Features Features supported by the origin host.
(See
3GPP TS 29.2
29 [6])
Reset-IDs Reset-ID O If present, this information element identifies together with the HSS's realm
(See the set of impacted subscribers.
3GPP TS 29.2
72 [10])
Table 5.5.1-2: Reset Answer
Information Mapping to Cat. Description
element name Diameter AVP
Supported Supported- O If present, this information element shall contain the list of features
Features Features supported by the origin host.
(See
3GPP TS 29.2
29 [6])
Result Result-Code / M This IE shall contain the result of the operation.
(See 6.4) Experimental- The Result-Code AVP shall be used to indicate success / errors as defined
Result in the Diameter base protocol (see IETF RFC 6733 [23]).
The Experimental-Result AVP shall be used for PC4a 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.
There are no Experimental-Result codes applicable for this command.

5.5.2 Detailed behaviour of the ProSe Function
When receiving a Reset message the ProSe Function shall mark all impacted subscriber records "Subscriber
DataConfirmed in HSS" as "Not Confirmed", as defined in 3GPP TS 23.007 [11]. If the Reset-IDs IE is supported and
received, the ProSe Function shall make use of the Reset-IDs (together with the HSS's realm) in order to determine
which subscriber records are impacted (i.e. check whether at least one received Reset-ID is associated with the
subscriber, and the HSS's realm identity received in the Origin-Realm AVP matches the value stored after successful
ProSe-Subscriber-Information retrieval); otherwise the ProSe Function shall make use of the HSS Identity received in
ETSI
3GPP TS 29.344 version 15.1.0 Release 15 14 ETSI TS 129 344 V15.1.0 (2019-10)
the Origin-Host AVP (by comparing it with the value stored after successful ProSe-Subscriber-Information retrieval)
and may make use of the received User-Id-List (if any) in order to determine which subscriber records are impacted.
5.5.3 Detailed behaviour of the HSS
The HSS shall make use of this procedure in order to indicate to all relevant ProSe Functions that the HSS has restarted
and may have lost the current ProSe Function Identity of some of its subscribers who may be currently roaming in the
ProSe Function Area and that the HSS, therefore, cannot send an Update ProSe Subscriber Data messages when needed.
If the Reset-ID feature is not supported by the ProSe Function and the HSS, the HSS may include a list of User Ids
identifying a subset of subscribers served by the HSS, if the occurred failure is limited to those subscribers.
If the Reset-ID feature is supported by the ProSe Function, the HSS optionally may include one (or several) Reset-ID
AVPs identifying e.g. failed hardware components if the occured failure is limited to those subscribers associated with
e.g. the identified failed hardware components.
5.6 Initia
...