General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] ericsson vAQM on LTE
Date: Wed, 9 May 2018 02:36:33 -0700	[thread overview]
Message-ID: <CAA93jw61vRuORbvOYgcecBdUnCoLnU7YF34CFXsxFOTK55F88g@mail.gmail.com> (raw)

It takes a while to get to the point, but I am encouraged. Maybe we
don't have to rebuild/reverse enginer a few 5g implementations from
scratch.

https://www.ericsson.com/assets/local/publications/ericsson-technology-review/docs/2018/virtual-aqm-for-mobile-networks.pdf

"Figure 3 illustrates vAQM in two scenarios: Packet Data Network
Gateway (PDN GW) of Evolved Packet Core (EPC) in 4G and in the User
Plane Function (UPF) of 5G core. In 5G, vAQM will be deployed as a
network function by the UPF of the 5G core. It will be configured per
PDU session, per SDF (Service Data Flow)/QoS flow – that is, the
guaranteed bitrate (GBR) or nonGBR QoS flow. The non-GBR QoS flows of
one PDU session will be aggregated and handled by one vAQM, whereas
each GBR QoS flow will be allocated a vAQM with a dedicated virtual
buffer. The Session Management Function (SMF) will configure vAQM and
its virtual buffers for the QoS flows during the PDU session
establishment/ modification phase. Configuration will occur when SMF
provides the UPF with a QoS Enforcement Rule that contains information
related to QoS enforcement of traffic including an SDF template (in
other words, packet filter sets), the QoS-related information
including GBR and maximum bitrate, and the corresponding packet
marking information – in other words, the QoS Flow Identifier (QFI),
the transport-level-packet-marking value. vAQM is self-learning,
making it fully automated without any parametrization."

-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

             reply	other threads:[~2018-05-09  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09  9:36 Dave Taht [this message]
2018-05-09  9:41 ` Sebastian Moeller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw61vRuORbvOYgcecBdUnCoLnU7YF34CFXsxFOTK55F88g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox