OMEC/Aether and dedicated bearer support

[Yiannis Yiakoumis]

Hi all,

We'd like to use dedicated bearer along with network tokens to demonstrate how operators can expose QoS (and other datapath services) in a way that is user and developer friendly, and also compatible with privacy and net neutrality requirements.  We've already added network token support on upf-epc, and now look to integrate and test with dedicated bearer provisioning. 

My understanding is that dedicated bearer support is still not fully implemented in Aether, but parts of it are implemented in different branches/repos. Couple of questions: 

• Any pointers  to any branch/repo/document that has support for dedicated bearers?
  
• Is there any OMEC and/or Aether deployment that supports dedicated bearer?
  
• Is anyone  that operates a physical testbed interested to work with us and help deploy and test? We want to do this in a physical testbed (instead of CIAB) as we also want to test how phones work with dedicated bearer and what assumptions they make.
  

The demo is around a user-centric, premium network quality service tailored for video calls. Happy to share more on the underlying technology, rational and use cases - please let me know. 

=============================

Brief background on Network Tokens - apologies if you've seen duplicates of this.

Network tokens are an open and secure method for end users and application providers to coordinate with the network about how their traffic is treated ( e.g., to access a 5G slice, a firewall whitelist, or a zero-rating service ). They replace complex, insecure, and privacy-invasive DPI application signatures with a deterministic and unified mechanism to expose datapath services. Network tokens are developed as an IETF standard. More information at links for GitHub, IETF, and mailing list are available at https://networktokens.org . 

Best,

Yiannis

Yiannis .

[Ajay Thakur]

Hi Yiannis,

Please find answers inline below

On Fri, Jun 26, 2020 at 1:20 PM Yiannis Yiakoumis <gyiak...@gmail.com> wrote:

Hi all,

We'd like to use dedicated bearer along with network tokens to demonstrate how operators can expose QoS (and other datapath services) in a way that is user and developer friendly, and also compatible with privacy and net neutrality requirements.  We've already added network token support on upf-epc, and now look to integrate and test with dedicated bearer provisioning. 

My understanding is that dedicated bearer support is still not fully implemented in Aether, but parts of it are implemented in different branches/repos. Couple of questions: 

• Any pointers  to any branch/repo/document that has support for dedicated bearers?
  

>> SPGW - repository-ngic_rtc and branch e-utran-features

>> MME - repository - Nucleus.  We would be starting implementation in first week of July. Might take roughly 2 months or so get it done.

• Is there any OMEC and/or Aether deployment that supports dedicated bearer?
  

>> Not sure. Sprint did develope spgw. They may have more data.

• Is anyone  that operates a physical testbed interested to work with us and help deploy and test? We want to do this in a physical testbed (instead of CIAB) as we also want to test how phones work with dedicated bearer and what assumptions they make.
  

>> ONF network would try dedicated bearers once full dedicated bearer support is available.

The demo is around a user-centric, premium network quality service tailored for video calls. Happy to share more on the underlying technology, rational and use cases - please let me know. 

=============================

Brief background on Network Tokens - apologies if you've seen duplicates of this.

Network tokens are an open and secure method for end users and application providers to coordinate with the network about how their traffic is treated ( e.g., to access a 5G slice, a firewall whitelist, or a zero-rating service ). They replace complex, insecure, and privacy-invasive DPI application signatures with a deterministic and unified mechanism to expose datapath services. Network tokens are developed as an IETF standard. More information at links for GitHub, IETF, and mailing list are available at https://networktokens.org . 

Best,

Yiannis

Yiannis .

--
You received this message because you are subscribed to the Google Groups "OMEC Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omec-dev+u...@opennetworking.org.
To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/omec-dev/kbwnnml3.8fdd7196-71a7-4b91-b860-e4fc6f29b3e2%40we.are.superhuman.com.

[Yiannis Yiakoumis]

Thanks Ajay.

Is ONF's plan to develop dedicated bearer support using the upf-epc datapath or ngic-rtc? 

Best,

Yiannis

[Ajay Thakur]

HI Yiannis,

Very difficult question to answer, since there are multiple stakeholders. Currently ngic-rtc (eutran branch does support dedicated bearers). Eventually we want to move forward with pfcp based Control Plane and data plane. But I am not sure at this time about the timeline.

Thanks

Ajay

[Vikram Barate]

Ngic-rtc e-utran-features branch has support for dedicated bearer, PFCP based control and data plane.

 

Regards,

Vikram.

To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/omec-dev/CACEN5cH%3DcmG_MNDujzEtwyK5JuDboNj0O6LaSbBBN%2BxYVoqvbQ%40mail.gmail.com.

Confidentiality Notice and Disclaimer: This email (including any attachments) contains information that may be confidential, privileged and/or copyrighted. If you are not the intended recipient, please notify the sender immediately and destroy this email. Any unauthorized use of the contents of this email in any manner whatsoever, is strictly prohibited. If improper activity is suspected, all available information may be used by the sender for possible disciplinary action, prosecution, civil claim or any remedy or lawful purpose. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, lost, arrive late, or contain viruses. The sender is not liable whatsoever for damage resulting from the opening of this message and/or the use of the information contained in this message and/or attachments. Expressions in this email cannot be treated as opined by the sender company management – they are solely expressed by the sender unless authorized.

[Yiannis Yiakoumis]

Thanks everyone for your answers. Summarizing findings after talking to a few people, feel free to add/fix if I misunderstood something. 

1.  ngic-rtc e-utran branch supports packet gateway functionality for dedicated bearer.

2. OpenMME doesn't support dedicated bearers yet, so to get e-utran working you need to connect it with an external MME that supports bearers, and depending on scenario, an external PCRF. 

3. ONF is actively working on adding dedicated bearer support to OpenMME, estimated time for completion is end of summer.  

4. There are no active plans for dedicated bearer support on the upf-epc datapath. 

Best,

Yiannis