Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 22.803  Word version:  12.2.0

Top   Top   Up   Prev   Next
1…   5…   5.1.7…   5.2…   5.2.7…   6…   B…

 

5  Use Cases and Scenariosp. 13

5.1  General Use Casesp. 13

5.1.1  Restricted ProSe Discovery Use Casep. 13

5.1.1.1  Descriptionp. 13

This use case describes a basic scenario for ProSe Discovery that can be used for any application. A social networking application is used as an example to illustrate this use case.

5.1.1.2  Pre-Conditionsp. 13

An operator offers a service which makes use of the ProSe feature, in which:
  • A ProSe-enabled UE of a given user is able to discover and be discoverable by the ProSe-enabled UEs of his/her friends;
  • A social networking application is enabled to use this ProSe feature.
Mary, Peter and John use a given social networking application. In the context of this application, the following relationships are established:
  • Mary and John are friends;
  • John and Peter are friends;
  • Mary and Peter are not friends;
  • There might be hundreds of other ProSe-enabled UEs in the vicinity of Mary using the same or other applications.
In addition, the following assumptions are made:
  • Mary, Peter and John use ProSe-enabled UEs;
  • Mary, Peter and John are subscribed to the same cellular operator;
  • Mary, Peter and John are currently residing on their HPLMN;
  • Mary, Peter and John are subscribed to an operator service that allows them to use ProSe;
  • Mary has given permission to John to discover her and vice versa;
  • John has given permission to Peter to discover him and vice versa.
The social networking application used by Mary, Peter and John is enabled by the operator to benefit from ProSe.
Up

5.1.1.3  Service Flowsp. 14

Mary decides to look for a friend via her application, and so do John and Peter. Thus (e.g. following interaction with her application), as Mary's UE comes into proximity of John's and Peter's UEs, the user experience is such that, without any further user interaction with the device:
  • Mary's UE detects (for example using direct radio signals or via the operator's network) that John's UE is in its proximity;
  • John's UE detects that Mary's UE is in its proximity;
  • Mary's social networking application learns that John is in or out of her proximity;
  • John's social networking application learns that Mary and Peter are in or out of his proximity;
  • Mary's UE does not detect that Peter's UE is in its proximity;
  • Peter's UE does not detect that Mary's UE is in its proximity;
  • Mary's social networking application does not detect that Peter is in or out of her proximity;
  • Peter's social networking application does not detect that Mary is in or out of his proximity.
As the social network application of Mary detects that John is in her proximity, Mary may decide to transfer data to John via the social networking application.
ProSe Discovery is achievable without any location information.
Up

5.1.1.4  Post-Conditionsp. 14

None

5.1.1.5  Potential Requirementsp. 14

General
[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.
[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.
[PR.2]
A discovering UE shall be able to determine whether or not another 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 authorized applications on the discovering UE.
[PR.3]
Operator policy and user choice can set the ProSe feature of:
  • a ProSe-enabled UE to discover other UEs in its proximity but not be discoverable;
  • a ProSe-enabled UE to be discoverable by other UEs but not be able to discover other UEs in its proximity;
  • a ProSe-enabled UE to discover other UEs in its proximity and be discoverable by other UEs;
  • a ProSe-enabled UE to disable the ability to be discoverable by other UEs and to disable the ability to discover other UEs;
  • a ProSe-enabled UE to revoke being discoverable by a ProSe-enabled UE (i.e. be discoverable by a UE at one time, and then not discoverable by the same UE at another time);
  • a ProSe-enabled UE to discover ProSe-enabled UEs of interest, where interest is defined in a ProSe-enabled application per user, group of users, or category of users;
  • a ProSe-enabled UE to restrict discoverability to ProSe-enabled UEs of interest, where interest is defined in a ProSe-enabled application per user, group of users, or category of users.
[PR.97]
Operator policy disabling or limiting individual ProSe features shall override any user choice.
[PR.4]
ProSe Discovery shall support a minimum of three range classes - for example short, medium and maximum range.
[PR.5]
The operator shall be able to authorize per subscription which range classes ProSe Discovery is allowed to use.
[PR.6]
The ProSe Discovery process shall enable authorized applications to request and to use a certain range class when discovering other UEs.
[PR.xy]
The ProSe Discovery process shall enable authorized applications to request and to use a certain range class when the UE is being discovered by other UEs.
[PR.7]
The impact of ProSe Services (Discovery and Communications) on radio usage, network usage and battery consumption should be minimized.
[PR.8]
Subject to user and operator settings, a ProSe-enabled UE shall be discoverable only by other UEs in proximity that are explicitly permitted by the discoverable UE.
[PR.9]
ProSe shall support the simultaneous operation of a large number of applications on a UE, ensuring that the 3GPP system provides ProSe Discovery proximity information only to applications that were authorized by the 3GPP system.
[PR.10]
An operator shall be able to authorize the use of ProSe Discovery information by an application.
[PR.11]
A user shall be able to allow the use of ProSe Discovery information by an application.
ProSe Feature Authorization
[PR.12]
The operator shall be able to enable or disable the ProSe Discovery feature in its network.
[PR.13]
The operator shall be able to authorize discovery operations for each individual UE.
[PR.14]
The operator shall be able to authorize the ability of a UE to be discoverable by other UEs.
[PR.15]
The operator shall be able to authorize the ability of a UE to discover other UEs.
Charging
[PR.16]
Both the HPLMN and VPLMN operators shall be able to charge for ProSe Discovery features including:
  • The ability for a UE to be discoverable, including based on the range class;
  • The ability to discover other UEs, including based on the range class;
  • The event of discovering a UE, including based on the range class.
Up

5.1.2  Open ProSe Discovery Use Casep. 15

5.1.2.1  Descriptionp. 15

This use case describes a case in which UEs discover other UEs without permission by the discoverable UEs.

5.1.2.2  Pre-Conditionsp. 15

Mary uses a given application. In the context of this application, the following assumptions are made:
  • Mary, Store A and Restaurants A, B and C use ProSe-enabled UEs;
  • Mary and the owners of the store and restaurant UEs are subscribed to an operator service that allows them to use ProSe;
  • There might be hundreds of other stores/restaurants with ProSe-enabled UEs in the vicinity of Mary;
  • The operator has enabled the application to access this ProSe feature.

5.1.2.3  Service Flowsp. 16

As Mary walks into the neighbourhood where Store A is located, Mary is notified of the proximity of Store A.
Mary then decides to look for a restaurant, and thus (e.g., following interaction with her application), Mary is notified of the proximity of Restaurant A. Mary is not notified of the proximity of other establishments which are not determined to be of interest according to the application she is using. After she starts walking towards Restaurant B, Mary is notified of the proximity of Restaurant B, and also of Restaurant C.
Up

5.1.2.4  Post-Conditionsp. 16

Mary's application is aware of Store A, Restaurants A, B and C.

5.1.2.5  Potential Requirementsp. 16

[PR.17]
Subject to user and operator settings, a ProSe-enabled UE shall be discoverable by all other ProSe-enabled UEs in proximity without explicit permission. The UEs can be
  • Served by the same PLMN, including when roaming;
  • Served by different PLMNs, including when roaming.

5.1.3  Discovery Use Case with Subscribers from Different PLMNsp. 16

5.1.3.1  Descriptionp. 16

This use case describes discovery between UEs camped on different PLMNs.

5.1.3.2  Pre-Conditionsp. 16

The same pre-conditions as in clause 5.1.1 apply except that
  • Mary is a subscriber to operator A and camps on operator A's network;
  • John is a subscriber to operator B and camps on operator B's network.

5.1.3.3  Service Flowsp. 16

As John moves towards Mary, the user experience is such that, without any further user interaction with the UE:
  • Mary is notified that John is in her proximity;
  • John is notified that Mary is in his proximity.

5.1.3.4  Post-Conditionsp. 16

John and Mary are aware of their proximity to each other.

5.1.3.5  Potential Requirementsp. 16

[PR.18]
Based on operator policy and user choice, the proximity of two ProSe-enabled UEs camped on different PLMNs shall be determinable.
[PR.19]
The operator shall be able to authorize the ability of a UE to discover UEs camping on other PLMNs.
[PR.20]
The operator shall be able to charge for the ability to discover UEs camping on other PLMNs.

5.1.4  Discovery Use Case with Roaming Subscribersp. 16

5.1.4.1  Descriptionp. 16

This use case describes discovery between UEs in different PLMNs under roaming conditions.

5.1.4.2  Pre-Conditionsp. 17

The same pre-conditions as in clause 5.1.1 apply except that
  • Mary is a subscriber to operator A and camps on operator A's network (i.e. her HPLMN);
  • John is a subscriber to operator C in a different country and currently roams in operator B's network, which is located in the same country as operator A's network.

5.1.4.3  Service Flowsp. 17

As John moves towards Mary, the user experience is such that, without any further user interaction with the UE:
  • Mary is notified that John is in her proximity;
  • John is notified that Mary is in his proximity.

5.1.4.4  Post-Conditionsp. 17

John and Mary are aware of their proximity to each other.

5.1.4.5  Potential Requirementsp. 17

[PR.21]
All requirements for ProSe Discovery also apply when one or both of the UEs involved in ProSe Discovery are roaming.
[PR.22]
The VPLMN operator shall be able to enable or disable the ability for all the inbound roamers from a specific PLMN to be discovered using ProSe Discovery.
[PR.23]
The HPLMN operator shall be able to authorize the ability of a UE to discover other UEs in case of roaming in a VPLMN.
[PR.24]
The HPLMN operator shall be able to authorize the ability of a UE to be discoverable by other UEs in case of roaming in a VPLMN.
[PR.25]
Both the HPLMN and VPLMN operators shall be able to charge for discovery features including:
  • The ability to be discoverable;
  • The ability to discover;
  • The event of discovering a UE.
Up

5.1.5  Network ProSe Discovery Use Casep. 17

5.1.5.1  Descriptionp. 17

In this use case, the 3GPP network provides ProSe Discovery for ProSe-enabled UEs.

5.1.5.2  Pre-Conditionsp. 17

  • Mary and Peter use ProSe-enabled UEs, subscribe to the same MNO, and currently reside on the HPLMN.
  • The MNO network supports ProSe Discovery and Communication.

5.1.5.3  Service Flowp. 17

  • Mary uses an application on her UE to connect with Peter, causing her UE to request ProSe Discovery from the MNO network.
  • The MNO network verifies that Mary's UE has permission to discover Peter's UE and is in proximity of Peter's UE.
  • The network informs Mary's and Peter's UEs that they are in proximity.

5.1.5.4  Post-Conditionsp. 18

Mary's and Peter's UEs have discovered each other.

5.1.5.5  Potential Requirementsp. 18

[PR.26]
An application on a ProSe-enabled UE shall be able to request the network to determine the proximity of another ProSe-enabled UE; the network shall be able to determine proximity of two ProSe-enabled UEs and inform them of their proximity.
[PR.91]
The operator shall be able to charge for network ProSe Discovery.

5.1.6  Service Continuity between Infrastructure and E-UTRA ProSe Communication pathsp. 18

5.1.6.1  Descriptionp. 18

In this use case UEs communicate initially via an infrastructure path, then via a ProSe Communication path and finally return to an infrastructure path.

5.1.6.2  Pre-Conditionsp. 18

An operator offers a service which makes use of the ProSe feature, in which:
  • The operator is able to establish a new user traffic session using E-UTRA ProSe communication;
  • The operator is able to switch user traffic from an infrastructure communication path to an E-UTRA ProSe communication path.
In addition, the following assumptions are made:
  • Mary and Peter use ProSe-enabled UEs;
  • Mary and Peter are subscribed to the same cellular operator;
  • Mary and Peter are currently residing on their HPLMN;
  • Mary and Peter are subscribed to an operator service that allows them to use ProSe;
  • Mary and Peter have performed ProSe discovery and initiation of ProSe communications.
Up

5.1.6.3  Service Flowsp. 18

Mary and Peter are engaged in a data session (including one or more flows) that is being routed over the MNO's core network infrastructure.
As Peter moves within proximity of Mary, one or more flows of the data session is switched to an E-UTRA ProSe communication path.
At some point later, the data session is switched back to the infrastructure path.
The user experience is such that the switching of the data path is not perceived by the users.
The user experience of the ongoing user traffic sessions is such that any un-switched data flows are not negatively impacted by the switching of other data flows.
Up

5.1.6.4  Post-Conditionsp. 18

None

5.1.6.5  Potential Requirementsp. 18

[PR.99]
The operator shall be able to dynamically control the proximity criteria for ProSe communication. Examples of the criteria include: range, channel conditions, achievable QoS.
[PR.27]
Subject to operator policy and user consent, the system shall be capable of establishing a new user traffic session with an E-UTRA ProSe Communication path, and maintaining both of the E-UTRA ProSe Communication path and the existing infrastructure path, when the UEs are determined to be in range allowing ProSe Communication. The UEs can be:
  • Served by the same PLMN, including when roaming;
  • Served by different PLMNs, including when roaming.
[PR.28]
The 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.
[PR.29]
The system shall be capable of monitoring the communication characteristics (e.g. channel condition, QoS of the path, volume of the traffic, etc.) on the E-UTRA ProSe communication path, regardless of whether there is data transferred via infrastructure path.
[PR.30]
The 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.
[PR.31]
The user shall not perceive the switching of user traffic sessions between the E-UTRA ProSe Communication and infrastructure paths when triggered by the network.
[PR.31.1]
The user shall not perceive the switching of user traffic sessions between the E-UTRA ProSe Communication and infrastructure paths when triggered by the UE.
[PR.32]
The system shall be capable of switching each flow it is aware of between the E-UTRA ProSe Communication and the infrastructure paths, independently.
[PR.33]
The establishment of a user traffic session on the E-UTRA ProSe Communication path and the switching of user traffic between an E-UTRA ProSe Communication path and an infrastructure path are under control of the network.
[PR.92]
The HPLMN operator shall be able to authorize the ability of a UE to use ProSe Communication, separately for the HPLMN and for roaming in VPLMNs.
[PR.93]
The HPLMN operator shall be able to authorize the ability of a UE to use ProSe Communication to communicate with a ProSe-enabled UE served by a different PLMN.
[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.
[PR.34]
The Radio Access Network shall control the radio resources associated with the E-UTRA ProSe Communication path.
[PR.35]
The ProSe mechanism shall enable the operator to change the communication path of a user traffic session without negatively affecting the QoS of the session.
[PR.36]
The ProSe mechanism shall enable the operator to change the communication path of a user traffic session of a ProSe-enabled UE without negatively affecting the communication paths of other ongoing user traffic sessions of this or other ProSe-enabled UEs.
[PR.37]
The ProSe mechanism shall enable the operator to change the communication path of a user traffic session based upon the QoS requirements of the session and the QoS requirements of other ongoing sessions of this or other ProSe-enabled UEs.
[PR.38]
The system shall be capable of selecting the most appropriate communications path, according to operator preferences. The criteria for evaluation may include the following, although not restricted to:
  • System-specific conditions: backhaul link, supporting links or EPC performance;
  • Cell-specific conditions: for example cell loading;
  • ProSe Communication and infrastructure path conditions: communication range, channel conditions and achievable QoS;
  • Service-type conditions: APN, service discriminator.
[PR.95]
Both the HPLMN and VPLMN operators shall be able to charge for ProSe Communication.
Up

Up   Top   ToC