Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.752  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…   6.10…   6.20…   6.30…   6.40…   7… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Architecture Requirements and Assumptions 
...

 

1  Scope  p. 12

The objective of this Technical Report is to identify and evaluate architecture enhancements of 5G System design needed to support proximity based services based on SA WG1 requirements defined in TS 22.278, TS 22.261 and TS 22.115 and determine which of the solutions can proceed to normative specifications.

2  References  p. 12

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 22.278: "Service requirements for the Evolved Packet System (EPS); Stage 1".
[3]
TS 22.261: "Service requirements for next generation new services and markets; Stage 1".
[4]
TS 22.115: "Service aspects; Charging and billing; Stage 1".
[5]
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[6]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[7]
TR 22.842: "Study on Network Controlled Interactive Service (NCIS) in the 5G System (5GS); Stage 1".
[8]
TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
[9]
TS 23.303: "Proximity-based services (ProSe); Stage 2".
[10]
RFC 826:  "An Ethernet Address Resolution Protocol".
[11]
TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[12]
TS 29.343: "Proximity-services (ProSe) function to ProSe application server aspects (PC2); Stage 3".
[13]
TS 32.277: "Telecommunication management; Charging management; Proximity-based Services (ProSe) charging".
[14]
TR 23.713: "Study on extended architecture support for proximity-based services".
[15]
TS 32.255: "Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2".
[16]
TS 32.256: "Charging management; 5G connection and mobility domain charging; Stage 2".
[17]
TS 32.291: "Telecommunication management; Charging management; 5G system, charging service; Stage 3".
[18]
TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[19]
TS 22.186: "Service requirements for enhanced V2X scenarios".
[20]
TS 24.334: " Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".
[21]
TS 24.333: " Proximity-services (ProSe) Management Objects (MO)".
[22]
TS 32.290: " Services, operations and procedures of charging using Service Based Interface (SBI)".
[23]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[24]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[25]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[26]
TR 23.733: "Study on architecture enhancements to Proximity Services (ProSe) UE-to-Network relay".
[27]
TR 36.746: "Study on further enhancements to LTE Device to Device (D2D), UE to network relays for Internet of Things (IoT) and wearables".
[28]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[29]
TS 23.280: "Common functional architecture to support mission critical services; Stage 2".
[30]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[31]
TS 33.501: "Security architecture and procedures for 5G system".
[32]
TR 38.836: "Study on NR sidelink relay".
[33]
RFC 4862:  "IPv6 Stateless Address Autoconfiguration".
[34]
TS 33.303: "Proximity-based Services (ProSe); Security aspects".
Up

3  Definitions and abbreviations  p. 13

3.1  Definitions  p. 13

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.
Open ProSe Discovery:
ProSe Discovery without explicit permission from the ProSe-enabled UE being discovered, according to TS 22.278.
Restricted ProSe Discovery:
ProSe Discovery that only takes place with explicit permission from the ProSe-enabled UE being discovered, according to TS 22.278.
5G ProSe Direct Discovery:
A procedure employed by a ProSe-enabled UE to discover other ProSe-enabled UEs in its vicinity by using only the capabilities of the two UEs with NR technology.
5G ProSe Direct Communication:
A communication between two or more UEs in proximity that are ProSe-enabled, by means of user plane transmission using NR technology via a path not traversing any network node.
Direct Network Communication:
One mode of network communication, where there is no UE-to-Network Relay UE between a UE and the 5G network.
Indirect Network Communication:
One mode of network communication, where there is a UE-to-Network Relay UE between a UE and the 5G network.
5G ProSe UE-to-Network Relay:
A UE that provides functionality to support connectivity to the network for Remote UE(s).
5G ProSe UE-to-UE Relay:
A UE that provides functionality to support connectivity between other UEs.
Remote UE:
A 5G ProSe-enabled UE that communicates with a DN via a 5G ProSe UE-to-Network Relay.
Up

3.2  Abbreviations  p. 14

For the purposes of the present document, the abbreviations given in TR 21.905 apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

4  Architecture Requirements and Assumptions  p. 14

4.1  Architecture Requirements  p. 14

Solutions shall build on the 5G System architectural principles as in TS 23.501, including flexibility and modularity for newly introduced functionalities.
In order to satisfy the normative stage-1 general requirements in TS 22.278 and TS 22.261 and TS 22.115, the system shall:
  • enable the direct discovery of the ProSe-enabled UE by other ProSe-enabled UEs within the same PLMNs or different PLMNs, including in coverage and out of coverage.
  • enable the ProSe direct communication functionality.
  • enable the path selection functionality.
  • enable the service authorization and provisioning of the ProSe-enabled UEs.
  • enable QoS support on PC5.
  • enable the operators (HPLMN or VPLMN) charging for the utilization of the ProSe functionality.
  • enable UE-to-Network relay functionality (including service continuity).
  • enable UE-to-UE relay functionality.
Up

4.2  Architecture Assumptions  p. 14

4.2.1  General  p. 14

  • Architecture reference models defined in TS 23.287 (i.e. PC5 based eV2X architecture reference model) are used as reference architecture for supporting ProSe in 5GS.
  • Architecture reference model defined in TS 23.501 are used as basis architecture for supporting ProSe in 5GS.
  • Group management is handled by application layer which is out of this document.
  • NG-RAN is considered; non-3GPP AN is not considered in the release.
  • NR based PC5 is considered.
  • QoS handling for V2X communication over NR PC5 reference point defined in clause 5.4.1 of TS 23.287 to clause 5.4.4 of TS 23.287 is used as basis for supporting PC5 direct communication.
  • The standardized PQI values defined for NR PC5 in TS 23.287 can be used to support performance requirements defined in clause 7.6.2 of TS 22.261 for interactive services if applicable.
  • Alternative QoS Profiles are not supported in UE-to-Network Relay scenarios.
 
The Relay's AMF may interact with Remote UE's AMF and Relay UE's PCF for authorization, and the details are in Solution #30.
  1. Source UE wants to establish unicast communication with target UE, it decides the E2E QoS parameters between source UE and target UE based on the application layer requirements. The Source UE sets up a PC5 QoS Flow with PFI. Then Source UE provides the PFI, E2E QoS parameters, source and target user info to UE-to-UE Relay. The process is similar to the unicast L2 link establishment or modification procedure as defined in clause 6.3.3 of TS 23.287.
  2. Relay splits the E2E QoS parameters into two parts: one part is for the PC5 interface between source UE and Relay (source side PC5 QoS parameters), the other part is for the PC5 interface between Relay and the target UE (target side PC5 QoS parameters).
  3. Relay provides the PFI received from source UE, target side PC5 QoS parameters, source and target user info to target UE. The process is similar to the unicast L2 link establishment or modification procedure as defined in clause 6.3.3 of TS 23.287.
  4. Relay receives the Layer-2 link establishment/modification accept from target UE.
  5. Relay provides the Layer-2 link establishment/modification accept to the source UE with the PFI and the source side PC5 QoS parameters.
Up

4.2.2  Reference Architecture Model  p. 15

V2X architecture as defined in TS 23.287 will be used as baseline.

Up   Top   ToC