Re: [Apn] [DMM] Regarding APN Usecase in Mobile Core
Uma Chunduri <umac.ietf@gmail.com> Mon, 18 January 2021 20:26 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 C9FDE3A0475; Mon, 18 Jan 2021 12:26:00 -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 pKQVnE5Y_me0; Mon, 18 Jan 2021 12:25:58 -0800 (PST)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 BFD203A046B; Mon, 18 Jan 2021 12:25:58 -0800 (PST)
Received: by mail-yb1-xb30.google.com with SMTP id b11so11576818ybj.9; Mon, 18 Jan 2021 12:25:58 -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=9E8jLc9VSFergk/QWTk6m7QvZ7gp5T7jFRa2ufD6dwk=; b=nHs09tpxwjAlIohIMw39s5AjfOt3QeKVKhCIr5QifxrVFF6LAXKggBydQsG6Vrw0zT VgVfAgKmzIUxc6RACyxOAGryyCCAkezI1+p3rXI++y740KzZYNPY4n+P4LQTW9EkMV4D WlWFkBWlYgqq9rc9j/yEYKWXr1Lc2U9/pCEAnY3uyQOoVtdNbcATOZYh1ELaAqOEwaqZ Nnhm7B9ao+nrxYmbId3kSj2YR9jWsxQMp/Ya16mRd3tDy+xzpPWt0YiBLpG1Fp/UOyYL U2/JawF/QuC9ujDwFn0TswkiSGcxoVmdrS+JNNfv1Auyu5hhEjLPI2OMVXrkkCJIgdoh K7JQ==
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=9E8jLc9VSFergk/QWTk6m7QvZ7gp5T7jFRa2ufD6dwk=; b=n4l0AT3FveqCva/1vontPNMrEG0kUeqOF3bj65ISteJ2GBCbO83W8rdFWW6QQ/AcNp BILTrctAA7uGdgvHSg9vr+zICCPnnJQdqHj2KKe9y5bBUqb88Pc2ck4jbgatrcTKsTX4 6QRl5tnOBCX0igp89w7AFDG1ZDqmqCcudEq/fxBWvsGJU3zEE5o+UWQFNNnRxf8y5bSR EFHM/l9QqV5nKnkK5KIE5M6Wm3Y2sva9Xs1kT8EBAtR18CQZvCLdY3kiPudhd6bLyla6 uFAeQZ9pat6QaBXI5y8NQf+VvvLjMfPebhE9N7PKCXRIKwRQdHaVAgO3lhdIc7u5XC5x aJ0A==
X-Gm-Message-State: AOAM531Oi8pPRIsxID3KPbyl8X2rNqicYsqX4v5RX8dcXYf5fOBWaL5U 382Q1UJ8tUon4Rw3jbWnj8J92JytRI/ZTQWow9JmF2ccK68=
X-Google-Smtp-Source: ABdhPJyJ+W/G1G3lrdPbBC4YR8A0SAXaxa0csA0pePi4foijG9gGxPzizxqK/C0lrUUNZUb7rUlQtnV7Fce30iKGlm0=
X-Received: by 2002:a25:1f87:: with SMTP id f129mr1152199ybf.142.1611001557992; Mon, 18 Jan 2021 12:25:57 -0800 (PST)
MIME-Version: 1.0
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com> <CAF18ct4nYsk9nNBN0enCeLwhUuSF1Quy+MTUoe7Gb3yYmjOU2w@mail.gmail.com> <DB7PR06MB4792D734DBDBA27A0CB445DEB5A40@DB7PR06MB4792.eurprd06.prod.outlook.com>
In-Reply-To: <DB7PR06MB4792D734DBDBA27A0CB445DEB5A40@DB7PR06MB4792.eurprd06.prod.outlook.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Mon, 18 Jan 2021 12:25:47 -0800
Message-ID: <CAF18ct66pKjid-xDzahs2-65vJvgc+Xx+UjtJFWUS3u_hE7fpg@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="00000000000098c73c05b9328706"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/bwW2cGVdRvEAMILkRiFlGtdidYw>
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:26:01 -0000
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/ -- 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%7C984c8fa55bbf4ea5b98908d8bbe5aa2d%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637465942368442430%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=namC6OofWdMQvTEjFwNkZT0ornR2gx1Q%2BV8SXxIHUis%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%7C984c8fa55bbf4ea5b98908d8bbe5aa2d%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637465942368452424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=00LmTEJXUJZfwFAMcs5abdCXTBvrrVSEMFeykW175u8%3D&reserved=0> > >
- [Apn] Regarding APN Usecase in Mobile Core Lizhenbin
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Uma Chunduri
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… David Lake
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Uma Chunduri
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… David Lake
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Uma Chunduri
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Gengxuesong (Geng Xuesong)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… duzongpeng@foxmail.com
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Kaippallimalil John
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Sridhar Bhaskaran
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… David Lake
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Linda Dunbar
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Gengxuesong (Geng Xuesong)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Gengxuesong (Geng Xuesong)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Gengxuesong (Geng Xuesong)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Sridhar Bhaskaran
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Kaippallimalil John
- [Apn] 回复: [DMM] Regarding APN Usecase in Mobile C… 刘 鹏
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Pengshuping (Peng Shuping)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Gengxuesong (Geng Xuesong)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Gengxuesong (Geng Xuesong)
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Sridhar Bhaskaran
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Uma Chunduri
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Linda Dunbar
- Re: [Apn] [DMM] Regarding APN Usecase in Mobile C… Pengshuping (Peng Shuping)