From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ericsson vAQM on LTE
Date: Wed, 9 May 2018 11:41:58 +0200 [thread overview]
Message-ID: <A2F25DAA-D779-4F2D-B980-26B677239B24@gmx.de> (raw)
In-Reply-To: <CAA93jw61vRuORbvOYgcecBdUnCoLnU7YF34CFXsxFOTK55F88g@mail.gmail.com>
> On May 9, 2018, at 11:36, Dave Taht <dave.taht@gmail.com> wrote:
>
> 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."
Ooops, who would have thought that "sentient" Skynet will actually wil have spend its formative years as a "self-learning" AQM-system; might explain its propensity to throttle its subjects ;)
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2018-05-09 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 9:36 Dave Taht
2018-05-09 9:41 ` Sebastian Moeller [this message]
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=A2F25DAA-D779-4F2D-B980-26B677239B24@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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