Content for TR 22.803 Word version: 12.2.0

6.1 General 6.2 Additional Operational Requirements 6.3 Additional Charging Requirements 6.4 Additional Security Requirements 6.5 Consolidated Potential Requirements

6 Potential Requirements p. 35

6.1 General p. 35

The following contains additional requirements not mentioned in clause 5.

6.2 Additional Operational Requirements p. 35

[PR.124]

The operator network shall be able to continuously control the use of E-UTRAN resources for ProSe Discovery and ProSe Communication between UEs, as long as at least one of these UEs is under E-UTRAN coverage and using operator's spectrum.

[PR.125]

ProSe Communication and ProSe Discovery shall not adversely affect other E-UTRAN services.

[PR.77]

ProSe services are available to ProSe-enabled UEs that are registered to a PLMN, and are under coverage of the E-UTRAN of said PLMN, potentially served by different eNBs. In this case E-UTRAN resources involved in ProSe services will be under real time 3GPP network control.

[PR.79]

The network should be able to collect Discovery information regarding which ProSe-enabled UEs are discovered to be in proximity of a given UE. Restrictions from contracts and regulation on data collection apply.

[PR.80]

ProSe services are not available to ProSe-enabled UEs out of E-UTRAN coverage except in the following case:

ProSe-enabled public safety UEs can use ProSe services when operating on public safety spectrum even when not under E-UTRAN coverage. In this case, at least a one-time pre-authorization to use ProSe services is needed.

[PR.81]

Re-authorization and specific configurations, including spectrum configurations, of public safety UEs shall be subject to public safety operator policy.

[PR.82]

When operating ProSe, the EPS shall be able to support regional or national regulatory requirements, (e.g. lawful interception, PWS).

[PR.120]

The ProSe system shall:

Allow a UE to selectively discover other UEs of interest;
Ensure that 3GPP UE/subscriber identifiers are not disclosed to unauthorized parties when ProSe Discovery and Communication is used;
Allow both granting and revocation of discovery permissions;
Enable applications to individually request the setting of discovery parameters, such as discovery range class.

[PR.116]

Subject to operator policies MOCN networks shall support establishing ProSe Communication between two UEs camping on the same radio access network but served by different MOCN PLMNs.

6.3 Additional Charging Requirements p. 35

[PR.83]

When a ProSe-enabled UE uses ProSe Communication or ProSe-assisted WLAN direct communications, both the HPLMN and VPLMN operators shall be able to collect accounting data for this communication including its:

Activation/deactivation;
initiation/termination;
duration and amount of data transferred;
QoS, if via E-UTRAN (e.g. levels of availability, allocated resource);
inter-operator communication;
inter-operator signalling.

6.4 Additional Security Requirements p. 36

[PR.111]

The system shall ensure the confidentiality of user data and network signalling over ProSe Communication path and Prose-assisted WLAN Direct Communication to a level comparable with that provided by the existing 3GPP system.

[PR.112]

The system shall ensure the integrity of user data and network signalling over ProSe Communication path and Prose-assisted WLAN Direct Communication to a level comparable with that provided by the existing 3GPP system.

[PR.96]

The level of security provided by the existing EPS shall not be adversely affected when ProSe discovery and communications are enabled.

[PR.86]

The system shall ensure the authenticity of the ProSe Discovery information used by an application that is authorized by the operator and the user.

[PR.87]

The system shall be able to restrict ProSe Discovery information to the ProSe-enabled UEs and applications that have been authorized by the users and network operator.

[PR.121]

The permission to be discoverable is given by the user and shall be executed by the system, subject to operator control, on a per-application basis.

[PR.122]

An operator shall be able to configure a UE with the permission to be discoverable or not by one or more UEs, without prior registration to the network, for example to provide the means for an enterprise or Public Safety organization to set permissions for its users.

[PR.113]

Existing 3GPP security mechanisms shall be reused whenever possible and appropriate.

[PR.114]

ProSe services shall respect local regulatory frameworks on the use of licensed spectrum.

[PR.115]

ProSe (Discovery and Communication), shall support regional or national regulatory requirements, (e.g. lawful interception).

[PR.xx]

The system shall ensure the user's identity and privacy are protected when ProSe is used.

6.5 Consolidated Potential Requirements p. 36

6.5.1 Requirements for Proximity Services p. 36

6.5.1.1 General feature requirements p. 36

[CPR.101] [PR.1]

Based on operator policy and user choice, the proximity of two ProSe-enabled UEs shall be determinable; for example, using direct radio signals or via the operator network.

[CPR.102] [PR.2]

A discovering ProSe-enabled UE shall be able to determine whether or not another ProSe-enabled UE is of interest to it. A ProSe-enabled UE is of interest to a discovering ProSe-enabled UE if its proximity needs to be known by one or more authorised applications on the discovering ProSe-enabled UE.

[CPR.103] [PR.8]

Subject to user and operator settings, a ProSe-enabled UE shall be able to be discoverable only by other ProSe-enabled UEs in proximity that are explicitly permitted by the discoverable ProSe-enabled UE.

[CPR.104] [PR.17, PR.18]

Subject to user and operator settings, a ProSe-enabled UE shall be able to be discoverable by all other ProSe-enabled UEs in proximity without explicit permission. The ProSe-enabled UEs can be served by the same or different PLMN, including when roaming.

[CPR.105] [PR.21]

All requirements for ProSe Discovery also apply when one or both of the ProSe-enabled UEs involved in ProSe Discovery are roamuing in a VPLMN.

[CPR.107] [PR.98]

The operator shall be able to dynamically control the proximity criteria for ProSe discovery. Examples of the criteria include radio range and geographic range.

[CPR.6] [PR.4]

ProSe Discovery shall support a minimum of three range classes - for example short, medium and maximum range.

[CPR.109] [PR.5]

The operator shall be able to authorise per subscription the maximum range class ProSe Discovery is allowed to use.

[CPR.110] [PR.6]

The possibility to be informed about and request to use certain ProSe Discovery range classes shall be provided to an application by a ProSe capability feature.

[CPR.111] [PR.7]

The impact of ProSe Discovery, ProSe Communications and ProSe-assisted WLAN communications on E-UTRA radio usage, network usage and battery consumption should be minimized.

[CPR.112] [PR.9]

ProSe shall support the simultaneous operation of a large number of applications on a ProSe-enabled UE, ensuring that the 3GPP system provides ProSe Discovery proximity information only to applications that were authorised by the 3GPP operator.

[CPR.113] [PR.26]

An application on a ProSe-enabled UE shall be able to request the EPC to determine the proximity of another ProSe-enabled UE; the EPC shall be able to determine proximity of two ProSe-enabled UEs and inform them of their proximity.

[CPR.12] [PR.29]

The system shall be capable of monitoring communication characteristics (e.g. channel condition, QoS of the path, volume of traffic etc.) on the E-UTRA ProSe Communication path, regardless of whether there is an existing data session on the infrastructure path.

[CPR.13] [PR.34]

The Radio Access Network shall control the radio resources associated with the E-UTRA ProSe Communications path.

[CPR.117] [PR.28]

The 3GPP system shall be capable of moving a user traffic session from the infrastructure path to an E-UTRA ProSe Communication path, when the ProSe-enabled UEs are determined to be in range allowing ProSe Communication.

[CPR.118] [PR.30]

The 3GPP system shall be capable of moving a user traffic session from an E-UTRA ProSe Communication path to an infrastructure path. At a minimum, this functionality shall support the case when the E-UTRA ProSe Communication path is no longer feasible.

[CPR.122] [PR.92]

The HPLMN operator shall be able to authorise the ability of a ProSe-enabled UE to use ProSe Communication, separately for the HPLMN and for roaming in VPLMNs.

[CPR.123] [PR.93]

The HPLMN operator shall be able to authorise the ability of a ProSe-enabled UE to use ProSe Communication to communicate with a ProSe-enabled UE served by a different PLMN.

[CPR.124] [PR.94]

The VPLMN operator shall be able to turn on or off the ability for all the inbound roamers from a specific PLMN to use ProSe Communication.

[CPR.15] [PR.39, PR.40, PR.42]

ProSe proximity information shall be suitable for integration with the Location and Presence information used by the network to offer its services.

[CPR.129] [PR.43]

ProSe shall be able to accommodate potentially large numbers of concurrently participating ProSe-enabled UEs.

[CPR.132] [PR.77]

The ProSe system shall be available to ProSe-enabled UEs that are registered to a PLMN and under the coverage of the E-UTRAN of said PLMN even if potentially served by different eNBs. In this case, E-UTRAN resources involved in ProSe services will be under real time 3GPP network control.

[CPR.133] [PR.79]

The network shall be able to collect Discovery information from a ProSe-enabled UE regarding which ProSe-enabled UEs are discovered to be in its proximity. Restrictions due to regulation on data collection apply.

[CPR.134] [PR.120]

The ProSe system shall:

Allow a ProSe-enabled UE to selectively discover ProSe-enabled UEs of interest;
Ensure that 3GPP UE/subscriber identifiers are not disclosed to unauthorised parties when ProSe is used;
Allow both granting and revocation of discovery permissions;
Enable applications to individually request the setting of discovery parameters, such as discovery range class.

[CPR.135] [PR.116]

Subject to operator policies MOCN networks shall support establishing ProSe Communication between two ProSe-enabled UEs camping on the same radio access network but served by different MOCN PLMNs.

6.5.1.2 WLAN access requirements p. 38

When a ProSe-enabled UE uses ProSe-assisted WLAN direct communications, both the HPLMN and VPLMN shall be able to collect accounting data for ProSe-assisted WLAN direct communications including:

ProSe-assisted WLAN direct communication duration, amount of data transferred, etc.

[CPR.136] [PR.44]

Subject to operator policy and user consent, a ProSe-enabled UE with WLAN capability shall be able to establish ProSe-assisted WLAN direct communications with another ProSe-enabled UE when in WiFi Direct communications range, based on ProSe Discovery and WLAN configuration information from the 3GPP EPC.

[CPR.137] [PR.45]

The 3GPP EPC shall be able to provide configuration information to ProSe-enabled UEs for the purpose of establishing ProSe-assisted WLAN direct communications.

[CPR.138] [PR.100]

The EPC shall be able to provide configuration information that enables confidentiality and integrity on the ProSe-assisted WLAN direct communications link.

[CPR.139] [PR.101]

The HPLMN operator shall be able to authorise ProSe-assisted WLAN direct communications for a ProSe-enabled UE, separately for use in the HPLMN and when roaming in VPLMNs.

[CPR.140] [PR.102]

The HPLMN operator shall be able to authorise a ProSe-enabled UE to engage in ProSe-assisted WLAN direct communications with a ProSe-enabled UE being served by a different PLMN.

[CPR.141] [PR.103]

The VPLMN operator shall be able to turn on or off ProSe-assisted WLAN direct communications for inbound roamers.

[CPR.142] [PR.104]

Both the HPLMN and VPLMN operators shall be able to charge for ProSe-assisted WLAN direct communications.

[CPR.143] [PR.47]

Subject to operator policy and user consent the EPC and a ProSe-enabled UE shall be capable of negotiating the move of a traffic flow between the infrastructure path and the ProSe-assisted WLAN direct path.

[CPR.145] [PR.105]

The network shall be able to determine whether two ProSe-enabled UEs are within WLAN direct communications range and whether the WLAN direct link can provide the necessary QoS to support the end user application.

[CPR.146] [PR.106]

The network shall ensure service continuity for ProSe-assisted WLAN direct communications flows and be capable of considering QoS requirements of all data flows when negotiating a communications path switch for a given end user application.

[CPR.147] [PR.107]

The system shall be capable of establishing a new user traffic session for a ProSe-assisted WLAN direct communications path.

[CPR.148] [PR.108]

Subject to operator policy and user consent the EPS shall be capable of maintaining existing E-UTRAN infrastructure communications while ProSe WLAN communication is established by a given ProSe-enabled UE.

[CPR.149] [PR.109]

Subject to operator policy and user consent the EPS shall be capable of establishing new E-UTRAN infrastructure communications while ProSe WLAN communication is on-going for a given ProSe-enabled UE.

6.5.1.3 Public Safety specific requirements p. 38

[CPR.21] [PR.55, PR.56, PR.80]

ProSe services shall not be available to ProSe-enabled UEs out of E-UTRAN coverage, except in the following cases:

ProSe-enabled public safety UEs can use ProSe services when operating on public safety spectrum dedicated to ProSe services even when not under E-UTRAN coverage. In this case, at least a one-time pre-authorization to use ProSe services is needed.
A ProSe-enabled public safety UE with ProSe Discovery enabled shall be able to discover other discoverable ProSe-enabled public safety UEs when some or all of the ProSe-enabled UEs involved in ProSe Discovery are out of E-UTRAN coverage.

[CPR.152] [PR.57]

The configuration of a ProSe-enabled public safety UE that allows the ProSe-enabled UE to discover other discoverable ProSe-enabled public safety UEs shall be independent from its configuration to allow or not to allow other ProSe-enabled public safety UEs to discover it.

[CPR.2aa] [PR.xxx]

A ProSe-enabled public safety UE shall be capable of determining autonomously whether a discovered ProSe-enabled UE is a public safety UE.

[CPR.25] [PR.61]

A public safety UE shall be capable of transmitting data to a group of public safety UEs using ProSe Group Communications with a single transmission, assuming they are within transmission range and authorized.

[CPR.26] [PR.62]

A ProSe-enabled public safety UE shall be capable of transmitting data to a group of ProSe-enabled public safety UEs directly using ProSe Group Communications.

[CPR.27] [PR.63]

A public safety UE shall be capable of receiving a ProSe Group Communications transmission, of which it is a group member, regardless of whether or not it has been discovered by the transmitting UE.

[CPR.28] [PR.64]

An authorized public safety UE shall be capable of sending a broadcast message to all authorized public safety UEs within transmission range, regardless of group membership, using ProSe Broadcast Communications in a single transmission.

[CPR.29] [PR.65]

An authorized public safety UE may be capable of acting as a relay for other public safety UEs.

[CPR.30] [PR.66]

An authorized public safety UE shall be capable of being enabled/disabled by a user or system to act as a relay for other public safety UEs.

[CPR.31] [PR.67]

The user of a ProSe-enabled public safety UE acting as a relay should not perceive service degradation due to the relay.

CPR.2YY There shall be a maximum of one ProSe UE-to-Network Relay between a UE and E-UTRAN.

CPR.2YY In the case where communication is relayed between an out of coverage UE and E-UTRAN, by a ProSe UE-to-Network Relay, there shall be no ProSe UE-to-UE Relays between the UE and E-UTRAN.

[CPR.32] [PR.68]

An authorized public safety UE shall be capable of communication using the network infrastructure and off network ProSe concurrently.

[CPR.156] [PR.69]

An authorised ProSe-enabled public safety UE shall be capable of being enabled/disabled to act as a relay to/from the network for other ProSe-enabled public safety UEs unable to access the network.

[CPR.34] [PR.70]

Based on operator policy and user choice, the system shall be able to initiate or move user traffic session of a ProSe-enabled public safety UE that has lost connection to the network to a communication path via a Prose-enabled public safety UE acting as a ProSe UE-to-network relay that is in ProSe Communication range and has connectivity to the network. Service continuity should be provided when the traffic is moved.

[CPR.36] [PR.72]

Based on operator policy, the operator network shall be able to control ProSe Communication between out of E-UTRAN coverage ProSe-enabled public safety UEs that are in ProSe Communication with an in E-UTRAN coverage ProSe-enabled public safety UE, which is acting as their ProSe UE-to-network relay.

[CPR.38] [PR.81]

Re-authorization and specific configurations, including spectrum configurations, of ProSe-enabled public safety UEs shall be subject to public safety operator policy.

6.5.2 Security, Authorization and Privacy p. 39

[CPR.40] [PR.85]

The system shall ensure that ProSe Discovery respects privacy.

[CPR.163] [PR.111, PR.112]

The system shall ensure that the confidentiality and integrity of both user data and network signalling over the direct link is supported to a level comparable with that provided by the existing 3GPP system.

[CPR.164] [PR.96]

The level of security provided by the existing EPS shall not be adversely affected when ProSe discovery and communications are enabled.

[CPR.165] [PR.86]

The 3GPP system shall ensure the authenticity of the ProSe Discovery information provided to the discoverer.

[CPR.42] [PR.87]

The system shall be able to restrict ProSe Discovery information to the ProSe-enabled UEs that have been authorised.

[CPR.44] [PR.82 & 115]

When operating ProSe, the EPS shall be able to support regional or national regulatory requirements, (e.g. lawful interception, PWS).

[CPR.166] [PR.121]

The permission to be discoverable is given by the user and shall be executed by the system, subject to operator control, on a per-application basis.

[CPR.167] [PR.122]

An operator shall be able to configure a ProSe-enabled UE with the permission to be discoverable or not by one or more ProSe-enabled UEs, without prior registration to the network, for example to provide the means for an enterprise or Public Safety organization to set permissions for its users.

[CPR.168] [PR.113]

Existing 3GPP security mechanisms shall be reused whenever possible and appropriate.

[CPR.45] [PR.13]

The operator shall be able to authorise discovery operations for each individual ProSe-enabled UE.

[CPR.169] [PR.114]

When offering ProSe, the 3GPP system shall respect local regulatory frameworks on the use of licensed spectrum.

[CPR.174] [PR.14]

The operator shall be able to authorise the ability of a ProSe-enabled UE to be discoverable by other ProSe-enabled UEs.

[CPR.175] [PR.15]

The operator shall be able to authorise the ability of a ProSe-enabled UE to discover other ProSe-enabled UEs.

[CPR.176] [PR.10]

An operator shall be able to authorise the use of ProSe Discovery information by an application.

[CPR.177] [PR.11]

A user shall be able to allow the use of ProSe Discovery information by an application.

[CPR.178] [PR.19]

The operator shall be able to authorise the ability of a ProSe-enabled UE to discover ProSe-enabled UEs camping on other PLMNs.

[CPR.179] [PR.22]

The VPLMN operator shall be able to turn on or off the ability for all the inbound roamers from a specific PLMN to be discovered using ProSe Discovery.

[CPR.180] [PR.23, PR.24]

When a ProSe-enabled UE is roaming in a VPLMN, its HPLMN operator shall be able to authorise the ProSe-enabled UE to discover and independently be discoverable by other ProSe-enabled UEs via settings which may be different from those for the non-roaming case.

[CPR.48] [PR.49]

The operator network and the ProSe-enabled UE shall provide a mechanism to identify, authenticate and authorise a third-party application to use ProSe capability features.

[CPR.182] [PR.89, PR.90]

The network shall be able to authorise ProSe Discovery preferences (e.g. discover and/or be discoverable) requested by third-party applications.

6.5.3 Charging Aspects p. 40

[CPR.184] [PR.20]

The operator shall be able to charge for the ability to discover ProSe-enabled UEs camping on other PLMNs.

[CPR.186] [PR.88 & 95]

The HPLMN operator shall be able to charge for use of ProSe Discovery and ProSe Communication by an application.

7 Conclusion and recommendations p. 40

The Feasibility Study for Proximity Services (ProSe) Technical Report analyses several use cases of ProSe for both general and public safety use. The use cases address two key aspects of ProSe:

Discovery, and
Communication via an optimized path.

Taking into consideration the Use Cases and Scenarios defined in Clause 5, new potential requirements related to UE operations, network operations, charging and security for ProSe have been identified in Clause 5 with additional potential requirements in Clause 6.1, Clause 6.2, Clause 6.3, and Clause 6.4.

It is recommended to proceed with normative work.

Some aspects in this feasibility study have led to normative specification in TS 22.278 and TS 22.115. The text of the present document will not be updated to align with normative specifications.

A WLAN handling in ProSe p. 42

Discovery:

Discovery of ProSe-enabled UEs is only based on E-UTRA radio.

Communication:

The WLAN communication has no impact on specifications under responsibility of RAN WGs. The 3GPP EPC may provide configuration that includes parameters to be used for setting up WLAN communication.

Use cases that include EPC management of the WLAN session and those that cover use of WLAN without EPC management can be considered.