Monday, April 3, 2017

Why 3GPP did not choose OpenFlow as the protocol for Sx interface (Control / User plane separation)

3GPP introduced control / user plane separation for the EPC in Release 14 and the protocol work for the Sx interface between the control plane and the user plane is now largely complete (few editor's note still need to be resolved). A question often comes up why 3GPP chose to design the PFCP protocl in TS 29.244 similar to GTP and why it did not adopt OpenFlow. The reason is well captured in this discussion paper presented by me in 3GPP CT4#74 at Tenerife in July, 2016.

The discussion paper is available here

In the same meeting another discussion paper on mapping the list of features on Gx and Sd interfaces to the Sx interface was also presented by me in this paper. This provided the basis for defining the features on the TS 29.244 spec.

2 comments:

  1. This Spec talks about EPC Nodes ( i am assuming this is restricted to EPC networks) but how this will be mapped in 5G ( across UPF and SMF) ?

    I guess there is a new reference point defined but will that reference point align to this Spec.

    ReplyDelete
    Replies
    1. Thanks for your comment and asking this question. When Sx was designed, the idea was to make it usable for N4 reference point in 5G. Of course some modifications to PFCP protocol is needed (for example there is no concept of a bearer in 5G) - but largely the concepts of the protocol will remain intact.

      It is bit early to say whether 3GPP CT4 will select / extend PFCP for N4 as the stage 3 study of 5G has just started. By march 2018 we will have a definite clarity on this.

      Delete