1 / 14

EPC CUPS Overview

EPC CUPS overview

hemraj3k
Download Presentation

EPC CUPS Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Prepared: Hemraj Kumar Senior 5G Technology Consultant EPC CUPS Architecture

  2. EPC Core 2

  3. Enhanced Packet Core (EPC) Enhanced Packet Core (EPC) E-UTRAN Overall control of the UE within the LTE architecture is handled by the core network. The core network (also known as EPC in SAE) is also responsible for establishing the bearers. The main components of the EPC are: PDN Gateway (P-GW) § Serving Gateway (S-GW) § Mobility Management Entity (MME) § 13

  4. EPC Entities Function 4

  5. EPC CUPS Architecture 5

  6. CUPS Overview CUPS architecture for EPC was first introduced in 3GPP release 14. All earlier EPC specification follows NON-CUPS architecture. CUPS introduce 3 new interfaces, Sxa, Sxb and Sxc between the CP and UP functions of the SGW, PGW, and TDF respectively. Control-/User Plane Separation (CUPS) in mobile networks refer to the complete separation between control plane functions (which take care of the user connection management, as well as defining QoS policies, performing user authentication, etc.) and user plane functions (which deal with data traffic forwarding). The main motivation for CUPS is to make user plane functions scale independently, allowing operators for a more flexible deployment and dimensioning of the network. For instance, if data traffic increases, more data plane nodes can be added without affecting the control plane functions. The Application protocol (AP) generates control signal and the CP encapsulates the signal bearers used to transmit control signals from the gNB to the UE. The UP provides the data bearers used to carry UE data from the DN to the UE using the GTP-U. The principle of CUPS supports the SDN technology which is already adopted in the 5GCN utilizing a service-based architecture. 6

  7. EPC Control and User Plane Separation (CUPS) SGSN-C 3GGP AAA HSS S2a-C ePDG- C S2b-C S6b PCRF SaMOG- C OCS Gx MME Gy S1 1 Gn- C SGW- C PGW- C Gz/Bp CG/BS SGSN-C S5-C/S8-C S4-C Sxa Sxb SGSN- U S4-U Operator Services SGi SGW- U PGW- U S5-U/S8-U S1- U E- Gn-U UTRA N § 5G Core Network inherits control and user plane separation architecture from 3GPP Release 14. § In 4G EPC, S/PGWs are decomposed to S/PGW-C and S/PGW-U to provide an efficient scaling independently. SGSN- U (CUPS) S12 RNC ePDG- U S2b-U S2a-U SaMOG- U of services 7

  8. CUPS Architecture Principles EPC w/o CUPS CUPS introduces 3 new interfaces, Sxa, Sxb and Sxc between the CP and UP functions of the SGW, PGW and respectively. TDF EPC with CUPS 8

  9. Principles of CUPS The CP function terminates the Control Plane protocols: GTP-C, Diameter (Gx, Gy, Gz). A CP function can interface multiple UP functions, and a UP function can be shared by multiple CP functions. An UE is served by a single SGW-CP but multiple SGW-UPs can be selected for different PDN connections. A user plane data packet may traverse multiple UP functions. The CP function controls the processing of the packets in the UP function by provisioning a set of rules in Sx sessions, i.e. Packet Detection Rules for packets inspection, Forwarding Action Rules for packets handling (e.g. forward, duplicate, buffer, drop), Qos Enforcement Rules to enforce QoS policing on the packets, Usage Reporting Rules for measuring the traffic usage. All the 3GPP features impacting the UP function (PCC, Charging, Lawful Interception, etc) are supported, while the UP function is designed as much as possible 3GPP agnostic. For example, the UPF is not aware of bearer concept. Charging and Usage Monitoring are supported by instructing the UP function to measure and report traffic usage, using Usage Reporting Rule(s). No impact is expected to OFCS, OCS and the PCRF. The CP or UP function is responsible for GTP-u F-TEID allocation. A legacy SGW, PGW and TDF can be replaced by a split node without effecting connected legacy nodes. 9

  10. Advantage and Disadvantage of CUPS Advantage of CUPS : Reducing Latency on application service, e.g. by selecting User plane nodes which are closer to the RAN or more appropriate for the intended UE usage type without increasing the number of control plane nodes. § Supporting Increase of Data Traffic, by enabling to add user plane nodes without changing the number of SGW-C, PGW-C and TDF-C in the network. § Locating and Scaling the CP and UP resources of the EPC nodes independently. § Independent evolution of the CP and UP functions. § Enabling Software Defined Networking to deliver user plane data more efficiently. § Disadvantage of CUPS The major disadvantages of CUPS is that it introduces complexity, standardization of interfaces between CP and UP and high cost of operation which may result in deployment delays . § 10

  11. EPC without CUPS GW (SGW/PGW) Function : Vertically integrated control plane (CP) and user plane (UP) function. CP function of GWs : proposed separately for each GW. Expensive customized of GWs and high expansion costs as user traffic increase. Unlimited scalability of GWs and high expansion costs as user traffic increase. Centralized deployment of all GWs. EPC MME S1-MME S11 LTEUu Data Network (e.g. operator or Internet) S5 S1-U SGi P-GW eNB S-GW LTE UE E-UTRAN MME : Mobility Management Entity. S-GW : Serving Gateway P-GW : PDN Gateway PDN : Packet Data Network. § § § § 11

  12. EPC with CUPS GW functions : separated into CP and UP functions. CP functions of GWs : processed centrally . Inexpensive commodity hardware based architecture. Scaling CP and UP functions independently (Enabling to add Only GW_Us independently as user traffic increased.) Enabling flexible deployment of GW-Us (closer to RAN) to reduce latency. Independent evolution of CP and UP function. S5-C S11 Control Plane EPC NAS PGW CP SGW CP MME S1-MME Sxb Sxa User Plane LTEUu S5-U Data Network (e.g. operator or Internet) SGi SGW UP PGW UP eNB LTE UE Note : CUPS introduce 3 new interfaces, Sxa, Sxb and Sxc between the CP and UP functions of the SGW, PGW, and TDF respectively. 12

  13. EPC with CUPS SGW/PGW-CP(GW-C) : Gateway Control Plane  SGW/PGW-UP(GW-U) : Gateway User Plane  BBU : Baseband Unit (or DU : Digital Unit )  RRH : Remote Radio Head (or RU : Radio Unit) PCRF HSS  Gx Rx S6a S10 EPC NAS S5 SGW/ PGW CP S11 Control Plane MME User Plane Sx LTE RRC LTE PDCP LTE Uu Data Network (e.g. operator or Internet) S1-U SGi SGW/ PGW UP eNB LTE UE E-UTRAN EPC Note : In this architecture ,control plane & user plane of GWs (SGW + PGW) are separated . 13

  14. EN-DC Core Architecture Enables through connectivity Option 3 UE anchored to network over LTE/EPC control plane Wide area coverage through LTE with NR as capacity boost early introduction of NR PCRF HSS Gx Rx S6a S10 S5 S11 SGW/ PGW CP MME S1-MME Sx Data Network (e.g. operator or Internet) LTE CP + UP S1-U SGi SGW/ PGW UP eNB LTE RAN S1-U X2-C X2-U LTE + NR UE NR UP gNB NR RAN 14

More Related