Tech-invite   3GPPspecs   RFCs   Search in Tech-invite

Gen21222324252627282931323334353637384‑5x
FsNEsRPsSBIsIDs Ti+
Top   in Index   Prev   Next

TR 33.853 (SA3) ☆ (Rel-16 draft)
Key Issues and Potential Solutions
for Integrity Protection of the User Plane (UP)

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V0.3.0 (Wzip)  2019/05  15 p.

Rapporteur:  -

User Plane integrity protection allows the network operator and the UE detect that user plane data has been modified in transit between each other.
Recently, several potential attacks on the 3GPP AN interface and AN infrastructure have come to light that can be mitigated by the use of integrity protection on the User Plane over at least the radio interface. This protection is currently available for a 5G AN with a 5G core but not for LTE with EPC, LTE with a 5G Core, or for EN-DC. Integrity protection is currently specified for the control plane to protect signalling messages but is only currently specified for 5G user plane up to 64Kb per bearer.
Furthermore, supporting User Plane Integrity Protection (UP IP) at full data rate for 5G NR with 5G Core has been identified as an issue in Rel-15 and thus a UE capability-based negotiation was introduced in 5G system. Key issues and Potential enhancements to support UP IP up to the full data rate need to be studied while meeting the expected peak data throughput and lower latency as the NR and LTE radio capabilities evolve.
5G and LTE can be implemented independently and together in a number of ways. These are described in TR 38.801 (clause 7.2) and are summarised as:
  • Option 1 - eUTRA with EPC
  • Option 2 - NR standalone with 5G Core
  • Option 3 - EPC based Dual Connectivity of eUTRA and NR RAT
  • Option 4 - 5G core based Dual Connectivity (NR master - eUTRA secondary)
  • Option 5 - 5G core with eUTRA
  • Option 7 - 5G core based Dual Connectivity (eUTRA master - NR secondary)

full Table of Contents for  TR 33.853  Word version:   0.3.0

 

Here   Top