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

TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Proximity-services (ProSe)
function to ProSe application server aspects (PC2);
Stage 3
(3GPP TS 29.343 version 15.1.0 Release 15)

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

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

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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.343 version 15.1.0 Release 15 2 ETSI TS 129 343 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.343 version 15.1.0 Release 15 3 ETSI TS 129 343 V15.1.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 PC2 reference point . 8
4.1 PC2 reference model . 8
4.2 Functional ele me nts . 9
4.2.1 ProSe Function . 9
4.2.2 ProSe Application Server . 9
5 PC2 procedures . 10
5.1 EPC-level ProSe discovery. 10
5.1.1 Application registration for ProSe . 10
5.1.1.1 General Description . 10
5.1.1.2 Detailed description of the application registration for ProSe procedure . 10
5.1.2 Proximity map request . 10
5.1.2.1 General . 10
5.1.2.2 Detailed description of the proximity map request procedure. 10
5.2 Restricted ProSe direct discovery . 11
5.2.1 Overview . 11
5.2.2 Authorization for Announce Request (model A) . 11
5.2.2.1 General Description . 11
5.2.2.2 Detailed description of the procedure . 11
5.2.3 Authorization for Announce Request with Application-controlled extension (model A) . 11
5.2.3.1 General Description . 11
5.2.3.2 Detailed description of the procedure . 12
5.2.4 Authorization for Monitor Request (model A) . 12
5.2.4.1 General Description . 12
5.2.4.2 Detailed description of the procedure . 12
5.2.5 Authorization for Monitor Request with Application-controlled Extension (model A) . 13
5.2.5.1 General Description . 13
5.2.5.2 Detailed description of the procedure . 13
5.2.6 Authorization for Discovery Permission (model A) . 13
5.2.6.1 General . 13
5.2.6.2 Detailed description of the procedure . 14
5.2.7 Authorization for Match Report (model A/model B). 14
5.2.7.1 General Description . 14
5.2.7.2 Detailed description of the procedure . 14
5.2.8 Authorization for Discoveree Request (model B) . 15
5.2.8.1 General Description . 15
5.2.8.2 Detailed description of the procedure . 15
5.2.9 Authorization for Discoverer Request (model B) . 15
5.2.9.1 General Description . 15
5.2.9.2 Detailed description of the procedure . 15
5.2.10 Authorization for Discovery Permission (model B) . 15
5.2.10.1 General Description . 15
5.2.10.2 Detailed description of the procedure . 15
5.2.11 Discovery Authorization Update . 15
5.2.11.1 General Description . 15
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 4 ETSI TS 129 343 V15.1.0 (2019-10)
5.2.11.2. Detailed description of the discovery authorization update procedure . 15
5.3 Open ProSe direct discovery . 16
5.3.1 Authorization for Announce Request with Application-controlled extension . 16
5.3.3.1 General Description . 16
5.3.3.2 Detailed description of the procedure . 16
5.3.2 Authorization for Monitor Request with Application-controlled Extension . 17
5.3.2.1 General Description . 17
5.3.2.2 Detailed description of the procedure . 17
6 PC2 protocol . 17
6.1 Protocol Support . 17
6.1.1 Use of Diameter base protocol . 17
6.1.2 Transport protocol . 18
6.1.3 Advertising Application Support . 18
6.2 Initialization and maintenance of connection and session . 18
6.3 Security over PC2 reference point . 18
6.4 PC2 specific AVPs . 18
6.4.1 General . 18
6.4.2 Origin-App-Layer-User-Id AVP . 19
6.4.3 Target-App-Layer-User-Id AVP . 19
6.4.4 ProSe-Function-ID AVP . 19
6.4.5 ProSe-Request-Type AVP . 19
6.4.6 PDUID AVP . 20
6.4.7 Application-Data AVP . 20
6.4.8 Allowed-Suffixes-Number AVP . 21
6.4.9 Monitor-Target AVP. 21
6.4.10 ProSe- Code-Suffix-Mask AVP . 21
6.4.11 Suffix-Code AVP . 21
6.4.12 Suffix-Mask AVP . 21
6.4.13 Void . 21
6.4.14 Void . 21
6.4.15 Void . 21
6.4.16 Void . 21
6.4.17 Banned-User-Target AVP . 21
6.4.18 Metadata-Indicator AVP . 22
6.5 PC2 re-used AVPs . 22
6.6 PC2 messages . 23
6.6.1 Command-Code Values . 23
6.6.2 ProXimity-Action-Request (PXR) command . 23
6.6.3 ProXimity-Action-Answer (PXA) command . 24
6.6.4 ProXimity-Application-Request (XAR) command . 24
6.6.5 ProXimity-Application-Answer (XAA) command . 25
6.7 PC2 specific Experimental-Result-Code AVP values . 25
6.7.1 General . 25
6.7.2 Success . 25
6.7.3 Failures . 25
6.7.3.1 DIAMETER_ERROR_ORIGIN_ALUID_UNKNOWN (5590) . 25
6.7.3.2 DIAMETER_ERROR_TARGET_ALUID_UNKNOWN (5591) . 26
6.7.3.3 DIAMETER_ERROR_PFID_UNKNOWN (5592) . 26
6.7.3.4 DIAMETER_ERROR_APP_REGISTER_REJECT (5593) . 26
6.7.3.5 DIAMETER_ERROR_PROSE_MAP_REQUEST_DISALLOWED (5594) . 26
6.7.3.6 DIAMETER_ERROR_MAP_REQUEST_REJECT (5595) . 26
6.7.3.7 DIAMETER_ERROR_REQUESTING_RPAUID_UNKNOWN (5596) . 26
6.7.3.8 DIAMETER_ERROR_UNKNOWN_OR_INVALID_TARGET_SET (5597) . 26
6.7.3.9 DIAMETER_ERROR_MISSING_APPLICATION_DATA (5598) . 26
6.7.3.10 DIAMETER_ERROR_AUTHORIZATION_REJECT (5599) . 26
6.7.3.11 DIAMETER_ERROR_DISCOVERY_NOT_PERMITTED (5600) . 26
6.7.3.12 DIAMETER_ERROR_TARGET_RPAUID_UNKNOWN (5601) . 26
6.7.3.13 DIAMETER_ERROR_INVALID_APPLICATION_DATA (5602) . 26
Annex A (informative): Call Flows over PC2 . 27
A.1 EPC-Level ProSe discovery . 27
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 5 ETSI TS 129 343 V15.1.0 (2019-10)
A.1.1 Application registration for ProSe . 27
A.1.2 Proximity map request . 28
A.2 Restricted ProSe direct discovery . 28
A.2.1 Authorization for Announce Request (model A). 28
A.2.2 Authorization for Restricted Discovery Announce Request with Application-controlled extension
(model A) . 29
A.2.3 Authorization for Monitor Request (model A) . 30
A.2.4 Authorization for Restricted Discovery Monitor Request with Application-controlled extension (model
A). 30
A.2.5 Authorization for Discovery Permission (model A) . 31
A.2.6 Authorization for Match Report (model A/model B) . 32
A.2.7 Authorization for Discoveree Request (model B) . 33
A.2.8 Authorization for Discoverer Request (model B) . 33
A.2.9 Authorization for Discovery Permission (model B) . 34
A.2.10 Discovery Authorization Update . 35
A.2.11 Authorization for Open Discovery Announce Request with Application-controlled extension . 35
A.2.12 Authorization for Open Discovery Monitor Request with Application-controlled extension . 36
B.1 General . 37
B.2 ProSe Function behaviour . 37
B.3 ProSe Application Server behaviour . 38
Annex C (informative): Change history . 39
History . 40

ETSI
3GPP TS 29.343 version 15.1.0 Release 15 6 ETSI TS 129 343 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.343 version 15.1.0 Release 15 7 ETSI TS 129 343 V15.1.0 (2019-10)
1 Scope
This document provides the stage 3 specification of the PC2 reference point. The functional requirements and the
stage 2 procedures of the PC2 reference point are contained in 3GPP TS 23.303 [2]. The PC2 reference point lies
between the ProSe Function and ProSe Application Server.
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 (ProSe); Stage 2".
[3] Void.
[4] IETF RFC 791: "Transmission Control Protocol".
[5] IETF RFC 4960: "Stream Control Transmission Protocol".
[6] 3GPP TS 33.303: "Proximity-based Services (ProSe); Security aspects".
[7] 3GPP TS 29.345: "Inter-Proximity-services (ProSe) Function signalling aspects; Stage 3".
[8] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
[9] IETF RFC 2234: "Augmented BNF for syntax specifications".
[10] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services
(ProSe) Function Protocol aspects; Stage 3".
[11] IETF RFC 8583:”Diameter Load Information Conveyance”.
[12] IETF RFC 6733: "Diameter Base Protocol".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP 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
3GPP TR 21.905 [1]. The term definition in the present document has a reference to that in 3GPP TS 23.303 [2].
Announcing UE: The UE that announces certain information that could be monitored by UEs in proximity that have
permission to discover.
Discoveree UE: The UE that receives the request message and responds with certain information related to the
discoverer UE's request.
Discoverer UE: The UE that transmits a request containing certain information about what it is interested to discover.
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 8 ETSI TS 129 343 V15.1.0 (2019-10)
Monitoring UE: The UE that monitors certain information of interest in proximity of announcing UEs.
EPC-level ProSe Discovery: A ProSe Discovery procedure by which the EPC determines the proximity of two ProSe-
enabled UEs and informs them of their proximity.
Model A: involves one UE announcing "I am here" in restricted ProSe direct discovery.
Model B: involves one UE asking "who is there" and/or "are you there" in restricted ProSe direct discovery.
ProSe Discovery: A process that identifies that a UE that is ProSe-enabled is in proximity of another, using E-UTRA
(with or without E-UTRAN) or EPC.
ProSe Discovery UE ID: A temporary identifier assigned by the ProSe Function in the HPLMN to the UE for the
restricted direct discovery service. It includes the PLMN ID and a temporary identifier that uniquely identifies the UE in
the HPLMN.
ProSe Function ID: An FQDN that identifies a ProSe Function.
Restricted ProSe Application User ID: An identifier associated with the Application Layer User ID in the ProSe
Application Server in order to hide/protect the application level user identity from the 3GPP layer. It unambiguously
identifies the user within a given application. The format of this identifier is outside the scope of 3GPP.
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].
ACE Application-Controlled Extension
ALUID Application Layer User ID
AVP Attribute-Value Pair
EPUID EPC ProSe User ID
PDUID ProSe Discovery UE ID
PFID ProSe Function ID
ProSe Proximity-based Services
RPAUID Restricted ProSe Application User ID

4 PC2 reference point
4.1 PC2 reference model
Proximity Services (ProSe) are services that can be provided by the 3GPP system based on UEs being in proximity to
each other. The PC2 reference point is located between the ProSe Application Server and the ProSe Function. It is used
to define the interaction between ProSe Application Server and ProSe functionality provided by the 3GPP EPS via
ProSe Function (e.g. name translation) for open ProSe direct discovery, restricted ProSe direct discovery and EPC-level
ProSe discovery.
The stage 2 level requirements for the PC2 reference point are defined in 3GPP TS 23.303 [2].The relationships
between the functional entities are depicted in Figure 4.1.1.
NOTE: For EPC-level ProSe discovery the roaming architecture is not specified in this release.
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 9 ETSI TS 129 343 V15.1.0 (2019-10)
SLP
HSSHSS
PC4a
PC4b
ProSe
application
PC 3
ProSe Application
UE A
ProSe Function
Server
PC2
PC1
Figure 4.1.1: PC2 reference point in ProSe Architecture
4.2 Functional elements
4.2.1 ProSe Function
The ProSe Function is the logical function that is used for network related actions required for ProSe. The ProSe
Function plays different roles for each of the features of ProSe. In this version of the specification it is assumed that
there is only one logical ProSe Function in each PLMN that supports Proximity Services.
Over PC2 reference point, the ProSe Function supports EPC-level discovery by the following functionality:
- Storage of a list of applications that are authorized to use EPC-level ProSe Discovery.
- Handling of EPC ProSe User IDs and Application Layer User IDs;
rd
- Exchange of signalling with 3 party Application Servers for application registration and identifier mapping;
The ProSe Function also supports open ProSe direct discovery and restricted ProSe direct discovery by the following
functionality:
- Generates and maintains the ProSe Discovery UE ID (PDUID) for restricted ProSe direct discovery.
- Initiates authorization of the discovery requests over PC2 reference point.
The ProSe Function provides the necessary charging and security functionality for usage of ProSe via the EPC.
4.2.2 ProSe Application Server
The ProSe Application Server supports the following functionality:
- Storage of EPC ProSe User IDs, ProSe Function IDs, ProSe Discovery UE ID, metadata and RPAUIDs;
- Mapping of Application Layer User IDs and EPC ProSe User IDs.
- Mapping of RPAUID and PDUID for restricted ProSe direct discovery.
- Maintaining permission information for the restricted ProSe direct discovery using RPAUIDs;
- Allocation of the ProSe Restricted Code Suffix pool, if restricted direct discovery with application-controlled
extension is used;
- Allocation of the mask(s) for ProSe Restricted Code Suffix, if restricted direct discovery with application-
controlled extension is used;
- Allocation of the mask(s) for ProSe Application Code Suffix, if open direct discovery with application-
controlled extension is used.
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 10 ETSI TS 129 343 V15.1.0 (2019-10)
5 PC2 procedures
5.1 EPC-level ProSe discovery
5.1.1 Application registration for ProSe
5.1.1.1 General Description
The application registration procedure is used by a ProSe Function serving the originating UE to request the ProSe
Application Server to register the UE’s Application Layer User ID (ALUID) with an EPC ProSe User ID (EPUID).
This procedure uses the Diameter commands ProXimity-Action-Request (PXR) and ProXimity-Action-Answer (PXA)
in the Diameter application as specified in clause 6.
5.1.1.2 Detailed description of the application registration for ProSe procedure
The ProSe Function of the UE triggering the ProSe EPC-level discovery application registration procedure shall send
the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific application requested
by the UE in its initial Application Registration message. The ProSe Function shall include in the request the ProSe-
Request-Type AVP with the value APPLICATION_REGISTRATION_FOR_PROSE (0), the Requesting-EPUID AVP
with the EPC ProSe User ID of the originating UE, the Origin-App-Layer-User-Id AVP with the Application Layer
User Identity of the originating UE, and the ProSe-Function-ID AVP with the ProSe Function Identity of the originating
UE.
When receiving a PXR command for application registration from a ProSe Function, the ProSe Application Server shall
process the request and respond to the ProSe Function with a PXA command.
If the ProSe Application Server accepts the PXR command, it acknowledges the reception of the PXR command for
ProSe application registration and sets the Result-Code AVP to "SUCCESS" in the PXA command. When receiving
PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-Code AVP. If it
indicates SUCCESS, the ProSe Function notifies the originating UE, according to the ProSe EPC-level discovery
application registration procedure as specified in clause 7.2.3 of 3GPP TS 24.334 [10]. In case of an unsuccessful
application registration request, applicable value defined in clause 6.7.3 shall be used to indicate the cause.
5.1.2 Proximity map request
5.1.2.1 General
The Proximity map request procedure may be used by the ProSe Function to request the EPC ProSe User identity for a
targeted application user for which the originating UE shall get alerts when in proximity of the targeted UE, and the
identity of the ProSe Function for this targeted UE as well. The identity of the ProSe Function is used in the execution
of the Proximity Request procedure described in 3GPP TS 29.345 [7].
5.1.2.2 Detailed description of the proximity map request procedure
To apply this procedure, the ProSe Function shall send a ProXimity-Action-Request (PXR) command including the
ProSe-Request-Type AVP with the value PROSE_MAP_REQUEST (1), the Origin-App-Layer-User-ID AVP
indicating the application layer user identity of the originating UE and the Target-App-Layer-User-ID AVP indicating
the application layer user identity of the targeted UE.
Upon reception of a PXR command including the Origin-App-Layer-User-ID AVP and the Target-App-Layer-User-ID
AVP, the ProSe Application Server shall determine whether the originating UE is allowed to discover the targeted UE.
The ProSe Application Server shall then send a ProXimity-Action-Answer (PXA) command including the Targeted-
EPUID AVP and ProSe-Function-ID AVP indicating the targeted UE and the corresponding ProSe Function ID
respectively.
In case of an unsuccessful proximity map request, applicable value defined in clause 6.7.3 shall be used to indicate the
cause.
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 11 ETSI TS 129 343 V15.1.0 (2019-10)
5.2 Restricted ProSe direct discovery
5.2.1 Overview
Restricted ProSe direct discovery is a process that a UE detects and identifies another UE in proximity using E-UTRA
direct radio signals with explicit permission of the UE that is being discovered. Detailed description of ProSe direct
discovery refers to 3GPP TS 23.303 [2] clause 5.3. There are two models that restricted ProSe direct discovery applies:
Model A ("I am here")
Two roles of ProSe-enabled UEs are involved in this model: Announcing UE and Monitoring UE. The announcing UE
broadcasts discovery messages at pre-defined discovery intervals and the monitoring UEs that are interested in these
messages read them and process them.
Model B ("who is there?" / "are you there?")
Two roles of ProSe-enabled UEs are involved in this model: Discoverer UE and Discoveree UE. It is equivalent to "
who is there/are you there" since the discoverer UE sends information about other UEs that would like to receive
responses from, e.g. the information can be about a ProSe Application Identity corresponding to a group and the
members of the group can respond.
5.2.2 Authorization for Announce Request (model A)
5.2.2.1 General Description
The announce authorization procedure (model A) is used by the ProSe Function serving the originating UE to obtain
announce authorization information related to restricted ProSe direct discovery. The procedure is invoked by the ProSe
Function and is used for the following purposes:
- to request the ProSe Application Server to map the UE's Restricted ProSe Application User ID (RPAUID) to the
corresponding ProSe Discovery UE ID(s) (PDUID(s)) .
5.2.2.2 Detailed description of the procedure
To apply this procedure, the ProSe Function of the UE triggering the restricted ProSe direct discovery announce request
procedure shall send the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific
application requested by the UE in its initial request message. The ProSe Function shall include in the request the
ProSe-Request-Type AVP with the value AUTHORIZATION_ANNOUNCE (2) and the Requesting-RPAUID AVP
with the RPAUID assigned for this application to the originating UE.
When receiving a PXR command for announce authorization for restricted ProSe direct discovery, the ProSe
Application Server shall acknowledge the reception of the PXR command and shall send a PXA command with the
Result-Code AVP set to "SUCCESS", with one or more PDUID AVPs set to each PDUID associated with the
requesting RPAUID. In case of an unsuccessful announce authorization request for restricted ProSe direct discovery,
applicable value defined in clause 6.7.3 shall be used to indicate the cause.
When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-
Code AVP. If it indicates SUCCESS, the ProSe Function verifies that there exists one received PDUID belonging to the
requesting UE, and notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
5.2.3 Authorization for Announce Request with Application-controlled
extension (model A)
5.2.3.1 General Description
The announce authorization procedure (model A) with application-controlled extension is used by the ProSe Function
serving the originating UE to obtain announce authorization information related to restricted ProSe direct discovery.
The procedure is invoked by the ProSe Function and is used for the following purposes:
ETSI
3GPP TS 29.343 version 15.1.0 Release 15 12 ETSI TS 129 343 V15.1.0 (2019-10)
- to request the ProSe Application Server to map the UE's Restricted ProSe Application User ID (RPAUID) to the
corresponding ProSe Discovery UE ID(s) (PDUID(s));
- to request the ProSe Application Server to allocate ProSe Restricted Code Suffix(es) for the RPAUID based on
application layer information provided by the UE.
5.2.3.2 Detailed description of the procedure
To apply this procedure, the ProSe Function of the UE triggering the restricted ProSe direct discovery announce request
procedure shall send the ProXimity-Action-Request (PXR) command to the ProSe Application Server of the specific
application requested by the UE in its initial request message, the PXR command shall include the ProSe-Request-Type
AVP with the value AUTHORIZATION_ANNOUNCE_ACE (3), the Requesting-RPAUID AVP with the RPAUID
assigned for this application to the originating UE, the Application-Data AVP with the data contained in the Application
Level Container parameter in the initial request message from the originating UE, and the Allowed-Suffix-Number
AVP with the allowed number of suffixes provisioned based on operator policy for this application.
When receiving a PXR command for announce authorization for restricted ProSe direct discovery with application
controlled extension, the ProSe Application Server shall first check if the application supports application-controlled
extension. If yes, the ProSe Application Server shall assign the ProSe Restricted Code Suffix(es) for the requesting
RPAUID based on the Application-Data AVP. The number of ProSe Restricted Code Suffixes allocated shall not
exceed the value in Allowed-Suffix-Number AVP in the PXR command. The ProSe Application Server shall then send
a ProXimity-Action-Answer (PXA) command including the PDUID(s) associated with the requesting RPAUID in one
or more PDUID AVP(s), and one or more ProSe-Restricted-Code-Suffix-Range AVP(s) indicating the assigned ProSe
Restricted Code Suffix(es). In case of an unsuccessful announce authorization request for restricted ProSe direct
discovery with application-controlled extension, applicable value defined in clause 6.7.3 shall be used to indicate the
cause.
When receiving PXA from the ProSe Application Server, the ProSe Function of the originating UE checks the Result-
Code AVP. If it indicates SUCCESS, the ProSe Function verifies that there exists one received PDUID belonging to the
requesting UE, and notifies the originating UE, according to the procedure specified in 3GPP TS 24.334 [10].
5.2.4 Authorization for Monitor Request (model A)
5.2.4.1 General Description
The authorization for monitor request procedure is used by the ProSe Function serving the originating UE to obtain
monitor authorization information related to restricted ProSe direct discovery. The procedure is invoked by the ProSe
Function and is used:
- to request the ProSe Application Server to select eligible target RPAUIDs from the application layer data
enclosed in the monitoring request from the originating UE and provide the corresponding PDUIDs for those
target RPAUIDs .
5.2.4.2 Detailed description of the procedure
To apply thi
...