Content for TS 29.343 Word version: 17.0.0
1 Scope p. 7
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 TS 23.303. The PC2 reference point lies between the ProSe Function and ProSe Application Server.
2 References p. 7
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.303: "Proximity-based services (ProSe); Stage 2".
[3] Void.
[4]
RFC 791: "Transmission Control Protocol".
[5]
RFC 4960: "Stream Control Transmission Protocol".
[6]
TS 33.303: "Proximity-based Services (ProSe); Security aspects".
[7]
TS 29.345: "Inter-Proximity-services (ProSe) Function signalling aspects; Stage 3".
[8]
RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".
[9]
RFC 2234: "Augmented BNF for syntax specifications".
[10]
TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to Proximity-services (ProSe) Function Protocol aspects; Stage 3".
[11]
RFC 8583: "Diameter Load Information Conveyance".
[12]
RFC 6733: "Diameter Base Protocol".
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
For the purposes of the present document, the terms and definitions given in TR 21.905 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. The term definition in the present document has a reference to that in TS 23.303.
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.
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 p. 8
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
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 p. 8
4.1 PC2 reference model p. 8
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 TS 23.303.The relationships between the functional entities are depicted in Figure 4.1.1.
4.2 Functional elements p. 9
4.2.1 ProSe Function p. 9
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;
- Exchange of signalling with 3rd party Application Servers for application registration and identifier mapping;
- Generates and maintains the ProSe Discovery UE ID (PDUID) for restricted ProSe direct discovery.
- Initiates authorization of the discovery requests over PC2 reference point.
4.2.2 ProSe Application Server p. 9
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.
