top button
Flag Notify
    Connect to us
      Facebook Login
      Site Registration

Facebook Login
Site Registration

5G: How attach procedure call flow differ in CUPS based network compared to the normal LTE network ?

+1 vote
5G: How attach procedure call flow differ in CUPS based network compared to the normal LTE network ?
posted Apr 3, 2018 by Harshita

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

CUPS stands for Control and User plane separation. LTE EPC nodes such as SGW and PGW contribute for control and user plane both. In CUPS architecture, both the existing EPC nodes divided into control and user plane nodes i.e. SGW-C, SGW-U, PGW-C and PGW-U. Moreover, two another nodes named as TDF-C and TDF-U introduced.
Because of these separations, new interfaces Sxa, Sxb and Gxc have been introduced. Sxa is the interface between SGW-C and SGW-U. Sxb is the interface between PGW-C and PGW-U and Sxc is the interface between TDF-C and TDF-U.
All the Sxx interfaces uses Packet Forwarding Control Plane (PFCP) protocol which runs over the UDP.
There are few changes in the attach procedure call flow. I am going to list down the changes only.

  1. There is no change in MME functionality or interfaces at MME.
  2. Once SGW receives Create Session Request from MME, it perform SGW-U selection procedure. SGW-U selection criteria is completely vendor specific implementation. After SGW-U selection, SGW-C prepares and sends the Sxa Session Establishment Request message to SGW-U.
  3. SGW-U allocates FTEID-U if it does not come from SGW-C within the Sxa Session Establishment Request message.
    Apart from user plane tunnel allocation, SGW-U perform various steps and finally responds to SGW-C by using the Sxa Session Establishment Response message.
  4. After receiving Sxa Session Establishment Response message from SGW-U, SGW-C prepares and sends Create Session Request as it use to send earlier.
  5. PGW-C receives the Create Session Request message from SGW-C and performs the PGW-U selection. Similar to SGW-U, PGW-U selection is also vendor specific implementation.
  6. After PGW-U selection, PGW-C prepares and sends Sxb Session Establishment Request message to PGW-U. The request message may contain TEID-U if it is implemented at PGW-C.
  7. PGW-U responds to PGW-C using the Sxb Session Establishment Response. The response message may contain FTEID-U if it is allocated at PGW-U.
  8. PGW-C sends Create Session Response to SGW-C with the allocated FTEID-U. SGW-C sends Sxa Session Modification Request to SGW-U to inform F-TEID-U of PGW-U.
  9. Now SGW-U and PGW-U both have information of its peer tunnel end points. SGW-U responds to SGW-C with Sxa Session Modification Response message.
  10. After receiving Modify bearer request from MME, SGW again initiate Sxa Modification procedure to update the eNodeB side S1-U tunnel id at SGW-U.

These are the major changes in attach call flow under the CUPS architecture.
If someone has details on TDF, please share.

answer Apr 5, 2018 by Vikram Singh
Contact Us
+91 9880187415
#280, 3rd floor, 5th Main
6th Sector, HSR Layout
Karnataka INDIA.