Re: [Apn] [DMM] Regarding APN Usecase in Mobile Core

Uma Chunduri <umac.ietf@gmail.com> Mon, 18 January 2021 20:34 UTC

Return-Path: <umac.ietf@gmail.com>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D365F3A0957; Mon, 18 Jan 2021 12:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HV8pZ1HQc1Bm; Mon, 18 Jan 2021 12:34:52 -0800 (PST)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC8723A0912; Mon, 18 Jan 2021 12:34:51 -0800 (PST)
Received: by mail-yb1-xb2d.google.com with SMTP id y4so13874097ybn.3; Mon, 18 Jan 2021 12:34:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TIjigJvzydaVD+AiU6w+jhkGP9dbTvO1YX8R1pA4Z44=; b=NoxSY34+ehi6Y5mrDq/DvjmltKpbTYZG/E/IhV4azEO5BzeUbplZQKl+oPsKjQokBA LjPHU5ynVuZJ8sJowrrwLyVM7BWvVUy12j4YRJlF8Vn8mgU+VLlMWaEN7RL3ZyALvDqc HwWoyL5uXzqqjs80LB1OgIVfB6hx64LlppxT9UufMiI3jSDdwUKw8nigov2m5Wqu38aN NSM+uYEO3ha4g0NUVt/m4GtRHWLWUJRlJ8ig1pk5EWHMcY1Rr3o98d443pjpSzQHlMUV qCyunEToFzh7r/mMadHXa71mvV30JsagmbS/vMuNxQ2wz+o6A/wxXhRi5izwO9FX2ABi FXIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TIjigJvzydaVD+AiU6w+jhkGP9dbTvO1YX8R1pA4Z44=; b=LKN0NDOuqJgFihAUG+5k1p3w2/LSTic2ifkL3C8f5oZpv3tNjwn69Ym8ZmgDfe4QKH eWWspHY2nhRhMgd1WlfNHgStdicUL/BrEoEoVIKWzhqP9pKo7Ti0pcnhStaN8Sp07bSY OLkyHw/t5Yb0sPcEJkcMr4M5h08ta0CJh4Oo9Zfc+HMms792nQQYGA0f9h3d+B1pq6fS vCQRN7lT76pcSYYYQoVhBhb9TiaanZ21VzHfOCY34vbGy/G2XfJx9siMXltVlKQOPRXS cqtIY0MaUrauNj12Yi3fTQZDxRuykEYOCb3cgoIjaG3w8hYULECWjViiJ1ZEg4klzhQ9 Vpjw==
X-Gm-Message-State: AOAM5325lr7hek363Oo79uxeS8v1cpB1dt2f6UziTfCI7vmMbdbT5LTQ gDXFZGAOisYSVCkSrtfmDd1r+5D5WfV63MxiYC8=
X-Google-Smtp-Source: ABdhPJxo2Vm8Jl4rvsWYKY8UFAc7OWKRfO3AU9Ll1XsaCVLG0UmPm8KKmLte3H7V6FKU+VBAHqOH6o74vZJg7Vy10mw=
X-Received: by 2002:a25:d7d7:: with SMTP id o206mr1329850ybg.265.1611002091099; Mon, 18 Jan 2021 12:34:51 -0800 (PST)
MIME-Version: 1.0
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com> <CAF18ct4nYsk9nNBN0enCeLwhUuSF1Quy+MTUoe7Gb3yYmjOU2w@mail.gmail.com> <DB7PR06MB4792D734DBDBA27A0CB445DEB5A40@DB7PR06MB4792.eurprd06.prod.outlook.com> <CAF18ct66pKjid-xDzahs2-65vJvgc+Xx+UjtJFWUS3u_hE7fpg@mail.gmail.com> <DB7PR06MB47927CDD8EC4A9DD2EB88C9DB5A40@DB7PR06MB4792.eurprd06.prod.outlook.com>
In-Reply-To: <DB7PR06MB47927CDD8EC4A9DD2EB88C9DB5A40@DB7PR06MB4792.eurprd06.prod.outlook.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Mon, 18 Jan 2021 12:34:40 -0800
Message-ID: <CAF18ct5QDh9=JiYwgqQAxY3xz2VotweKgytQ5ZnhivUpsBcU+g@mail.gmail.com>
To: David Lake <d.lake@surrey.ac.uk>
Cc: Lizhenbin <lizhenbin@huawei.com>, "apn@ietf.org" <apn@ietf.org>, dmm <dmm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005f5a3405b932a70f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/iihWNOcQ_wU6EEjGtTMxphnYxBo>
Subject: Re: [Apn] [DMM] Regarding APN Usecase in Mobile Core
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2021 20:34:55 -0000

Indeed & it's better to disambiguate sooner if APN@IETF folks are seeking
to work with cellular domain in general.

--
Uma C.

On Mon, Jan 18, 2021 at 12:27 PM David Lake <d.lake@surrey.ac.uk> wrote:

> Hi
>
>
>
> EEK!   This could be a problem then if we have TWO definitions of APN….
>
>
>
> David
>
>
>
> *From:* Uma Chunduri <umac.ietf@gmail.com>
> *Sent:* 18 January 2021 20:26
> *To:* Lake, David (PG/R - Elec Electronic Eng) <d.lake@surrey.ac.uk>
> *Cc:* Lizhenbin <lizhenbin@huawei.com>; apn@ietf.org; dmm <dmm@ietf.org>
> *Subject:* Re: [Apn] [DMM] Regarding APN Usecase in Mobile Core
>
>
>
> Hi David,
>
>
>
> Many excellent points below w.r.t GTP-u and the Access Point Name (APN)
> which defines the network path for all cellular data connectivity.
>
>
>
> However, I presume Robin was referring to a different APN -
> https://datatracker.ietf.org/wg/apn/about/
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fwg%2Fapn%2Fabout%2F&data=04%7C01%7Cd.lake%40surrey.ac.uk%7C607b41fb513c48c361f908d8bbef44ae%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637465983616671466%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=i%2Fou%2ByUAzdg5kIL1N2sdXlCLM41q%2BWSnBc9lymZbgNo%3D&reserved=0>
>
>
>
>
> --
>
> Uma C.
>
>
>
> On Mon, Jan 18, 2021 at 12:10 PM David Lake <d.lake@surrey.ac.uk> wrote:
>
> The APN provides the linkage between the application profile and the radio
> bearers.  GTP-u is manner by which the traffic is tunnelled to the anchor
> point and you MAY end up with different end points for each of the GTP
> bearers.
>
>
>
> Traffic at both the UE and the PGW (in LTE – UPF in 5G) are directed to
> the correct APN by a Traffic Flow Template (TFT).  This is to ensure that
> traffic goes across both the correct radio bearer and is marked correctly
> in the IP network.
>
>
>
> Users will often be unaware of multiple APNs on their UE; the most common
> hidden APN is one for VoLTE which, with the use of the TFT, will ensure
> that the VoIP frames (media) are put across the QCI 9 radio bearer and into
> the correct class on the IP network.  QCI 9 maps to a specific numerology
> on the Air Interface so that quality can be maintained for the voice call.
>
>
>
> In theory, multiple APNs all with their own TFT rules and potentially
> multiple GTP-u tunnels could be used but this is very rarely done.
>
>
>
> David
>
>
>
> *From:* Apn <apn-bounces@ietf.org> *On Behalf Of *Uma Chunduri
> *Sent:* 18 January 2021 19:17
> *To:* Lizhenbin <lizhenbin@huawei.com>
> *Cc:* apn@ietf.org; dmm <dmm@ietf.org>
> *Subject:* Re: [Apn] [DMM] Regarding APN Usecase in Mobile Core
>
>
>
> Hi Robin,
>
>
>
> In-line..
>
>
>
> Cheers!
> --
>
> Uma C.
>
>
>
> On Mon, Jan 18, 2021 at 5:25 AM Lizhenbin <lizhenbin@huawei.com> wrote:
>
> Hi APNers and DMMers,
>
> I remember that in the mobile core scenarios the GTP-u tunnel can be set
> up according to the user and application requirements, but I do not
> understand the details.
>
>
>
> [Uma]: Obviously, the best reference for GTP-U is TS 29.281. However, uou
> should look into
> https://datatracker.ietf.org/doc/draft-ietf-dmm-5g-uplane-analysis/
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dmm-5g-uplane-analysis%2F&data=04%7C01%7Cd.lake%40surrey.ac.uk%7C607b41fb513c48c361f908d8bbef44ae%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637465983616671466%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=d1al4%2Fco3GeSDbG5EMXSZU7q35vFm%2BFv5sA4WnzTpos%3D&reserved=0>
> where lot more details and other references related this topic was analyzed
> (primarily started after/during REL-15, when  any other use plane other
> than GTP-U is worthwhile is debated for 5G N9 interface).
>
>
>
> I think when the packet tunneled by GTP-u traverses the APN-based
> transport network, it may be mapped to the corresponding tunnel according
> to the user and application requirements to implement the uniform service.
> If you are familiar with the principle of GTP-u in the mobile core, please
> help provide some details.
>
>
>
>
>
> Best Regards,
>
> Zhenbin (Robin)
>
>
>
>
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdmm&data=04%7C01%7Cd.lake%40surrey.ac.uk%7C607b41fb513c48c361f908d8bbef44ae%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637465983616681466%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Rr%2FLGzBbK%2FK0qdUeDoizGiWzS7LWWHIxsBodhu6ScLI%3D&reserved=0>
>
>