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

David Lake <d.lake@surrey.ac.uk> Mon, 18 January 2021 20:27 UTC

Return-Path: <d.lake@surrey.ac.uk>
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 77D323A0809; Mon, 18 Jan 2021 12:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=surrey.ac.uk
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 QM7M5_VYEk9a; Mon, 18 Jan 2021 12:27:25 -0800 (PST)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-he1eur04on071d.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe0d::71d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B08F3A046B; Mon, 18 Jan 2021 12:27:25 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RArIYyKwoPqNUPIeZfNHNJAiNUS9StxsY02LsYY+bofbEn7SWtUN3nUDUj+jRbcESGQFIAJTTNOd2a/Ti6qPY9xu+knbHXG5v1Slcp9iRe6VT7gTwmJhYTIjME+8SDTkT73zgqH9RnwUkMSqQdAgtrah2OgW56ytGNeNBDYBOgXKK9hHDLVi5/T8IDtZcAqh8JiikQGnwMqoApwkLWFG8LGrYSRKPuK5IkC/IM5gcTbUd1D3zmO8DOHUCefJeFh08tj6YeOX/Wvb9JzUJOdRWQsahFKHKIwMgysCXcyjrYZBkj4mDQYwzfZckdbtP4Y4WwniOWybEbG6QIGn8yLLIQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5jam1isCZzafl8gSZbFmasR61zAtN4+AFJbIpoV5ysI=; b=XNrKctTDsZ0AoNWsxdRJOVQHTeutbb3MEZ0210VgkVpfPPKybBdGGWFNaHYTjI8Z+h5rx41vBs/LUxm8ojocdEU79A8zMnQGLY4fCoZ4CGfBB7DbnmQL5zfrF0RICZWBxrWrHjRwHQwyQiG23/xLmyyW8GfIypEp/l4UymxrWIJItiteqknGmcAiUuTrRXvkqYSxh4f1noGxGLmI1bpXva2MW3yQPF9FSYAFZi2hBZAtmleaeOOXrK9ESPSxEXe2ZskDcFRCwc+DU6zdJ0ZmecWB6d9iWMNGh5nRQSnsNqGPbS2mRRSHGCBlrnDMFzTZdjwu4pK64/d7yKIhyn0yeg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=surrey.ac.uk; dmarc=pass action=none header.from=surrey.ac.uk; dkim=pass header.d=surrey.ac.uk; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=surrey.ac.uk; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=5jam1isCZzafl8gSZbFmasR61zAtN4+AFJbIpoV5ysI=; b=zAFE2UbZbv7261d4QjV1xFtcsuYbjM6gb/iBWXHVLxPk63HgJ4YuXfJzRVaUsaagiDCb0HowhrUHFIF2UJlfsnUtOQyran6FuvxYYdv9eRXZB1bXn1y2p+YlUFXbtJ1kngJ62Q7AaMB20uvav8DqkHg/B/WX2TFnZhsKyHCGJhk=
Received: from DB7PR06MB4792.eurprd06.prod.outlook.com (2603:10a6:10:57::20) by DB6PR06MB3015.eurprd06.prod.outlook.com (2603:10a6:6:9::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10; Mon, 18 Jan 2021 20:27:21 +0000
Received: from DB7PR06MB4792.eurprd06.prod.outlook.com ([fe80::eca6:b32c:11fa:21d6]) by DB7PR06MB4792.eurprd06.prod.outlook.com ([fe80::eca6:b32c:11fa:21d6%5]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021 20:27:21 +0000
From: David Lake <d.lake@surrey.ac.uk>
To: Uma Chunduri <umac.ietf@gmail.com>
CC: Lizhenbin <lizhenbin@huawei.com>, "apn@ietf.org" <apn@ietf.org>, dmm <dmm@ietf.org>
Thread-Topic: [Apn] [DMM] Regarding APN Usecase in Mobile Core
Thread-Index: AdbtnTwkvWaRqLjmRvCQ5SUSFivHQAAMT3cAAAFxrYAAAPZ9gAAAB58A
Date: Mon, 18 Jan 2021 20:27:21 +0000
Message-ID: <DB7PR06MB47927CDD8EC4A9DD2EB88C9DB5A40@DB7PR06MB4792.eurprd06.prod.outlook.com>
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>
In-Reply-To: <CAF18ct66pKjid-xDzahs2-65vJvgc+Xx+UjtJFWUS3u_hE7fpg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=surrey.ac.uk;
x-originating-ip: [81.187.83.88]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3cdeafae-ca4d-4ce0-b7fe-08d8bbef75b2
x-ms-traffictypediagnostic: DB6PR06MB3015:
x-microsoft-antispam-prvs: <DB6PR06MB3015D0AB0EB426E27F6F8195B5A40@DB6PR06MB3015.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: fE4GBGqpnBBWcWoA+gHVQyardA9yj3W+oyctVEkXa4B87scwOWVEA6po7UyRuQv26SShGPPPeNkCNrb0GR/jVCLRYD9nQFfbxnR5uH38xCkkdjRymxdIlc97sFuxbVRHSxgt9hsc2TqVKeyJzC6FgsV6fJWzH/shtuDy82BiwqC9sapS6svv+mg218F8Kld36nUMqfN/OZkKi210HjYCDwiOKb4b99ydJU0+b7bChUdRPTCACJGWQlFx65tB8N+/qGVbhsoMxqu9vMpw8NoKwkVqVP24kAQcqu8IyMAWmFL8aOKV+xKnbdDOjf7cDjvdrOA91OfSd8N4wv6v/qoBMH/kVs9Rzl5vU0boyY4t09URNjCf+xKApcIHzJBhhdk/KdzEwFMfsAENWygqtuCnfCYybXDI3ivIW9+lOtpbMTqWqKRIFQxEoX4/dC6TSoAdsqhLFHoC1li+kGH9g7znDA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR06MB4792.eurprd06.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(396003)(346002)(136003)(366004)(39860400002)(316002)(2906002)(966005)(8676002)(71200400001)(9326002)(786003)(6916009)(54906003)(76116006)(186003)(5660300002)(8936002)(55016002)(6506007)(478600001)(26005)(166002)(83380400001)(53546011)(7696005)(52536014)(66556008)(33656002)(64756008)(66476007)(66446008)(4326008)(66946007)(86362001)(9686003); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: wW4dVYYMma6l56bhIGX7jg8mLibDTblAGFuSue5cNcBIg3MUQa0bo6YAgkGjRBZ2dvLataPWGLS3hnmouI80yAQ5CEDZ6SDk6K6sm1eTkUHLelpUPk+Y/VEiLJnjsyDErWdH95gGxxurDvX5dRS4v3WDMvBFReejy4q6zMgs4lo0oqmlq8ZrqzmwPbvmxQ+1m7cEgfKPDc2Y+M2mnGkmMG15FM8GrjIxnjYxv4sBcH8xgp60bgPCBCFpLlhld1ecYVUy7+g+wCpDhZvmufbfJh/yWGAl/rCwG/3hidFBE5VkSTxuayQDKDDkK4+SiKZBbPG4wldsuEMkiXm76t2J3L8jZYMb0dA83hA9rh+bc68bD1+hw4Zg+fjUa5Mu1aMa+hrogFbjIM6ZGSNUWtMvwdnFiALMZoRExAYkpZ6/MFV48DkQZkAdJefPGZTJJZJr7rGVJ5W3QCv4qRF31r20jTO9Vi1gVEOz3CkgsWmLT4G3o0+wCN/6URLMBGYsh2q/IzxKukE486vUKdVI+WZCFAtH/AXHBlu4AtBH2TFiEN5tSBqCY6Guy7ovXPIIDTEqNwirsZdXWyENWBijUcvOnkXYzH0lpudchHKeyDyjcZFI19Ds8WNsFvKvbrzB8IgseAbBRiJDJoFdcZJKG3V2oTWZPAESnnwGaDz3c005FPQ/AomAzmgMRWmMw7mbb+cE9N/q4TLnIT2lNpoCIbyoWTyt4grS5PN6Ph5vPYo3IlSzsPhyXAzQvzHd09pZYill152AW9A+G/0wWGSCHPtCwFHSN+hj1qFU0XVdnLJboBUuZP4nvKqy7ugbImRSEFm7tn1Gm8+1kk9Sy7Kp3B9PozVjFeqogb/rG2j93Z4LeF/IoOlIvTl+C4bkgt3XS78eH8jJTqbK+w8IpsM8y3IyDpZ7grl5p6lkBJibla2NW1IWsRqNFB+Sl35HQYfscHxhxBMTW7PYlPGuj7MHU2XhUST/wW3L6S1YBzWJYVsvhNA=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DB7PR06MB47927CDD8EC4A9DD2EB88C9DB5A40DB7PR06MB4792eurp_"
MIME-Version: 1.0
X-OriginatorOrg: surrey.ac.uk
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DB7PR06MB4792.eurprd06.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3cdeafae-ca4d-4ce0-b7fe-08d8bbef75b2
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jan 2021 20:27:21.7960 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6b902693-1074-40aa-9e21-d89446a2ebb5
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SR+oUJkEpMhuE3iDtjL4IsQPrZhL969wXJJRZql1xKE0i8VJ7Z7cbGFxBvsRQ/7Fi859ZEviAAfzWjbwugzwkg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR06MB3015
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/nzIib6l6me6u8V3xEppOICmuMY8>
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:27:29 -0000

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<mailto: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<mailto:apn-bounces@ietf.org>> On Behalf Of Uma Chunduri
Sent: 18 January 2021 19:17
To: Lizhenbin <lizhenbin@huawei.com<mailto:lizhenbin@huawei.com>>
Cc: apn@ietf.org<mailto:apn@ietf.org>; dmm <dmm@ietf.org<mailto: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<mailto: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<mailto: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>