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

David Lake <d.lake@surrey.ac.uk> Fri, 22 January 2021 08:15 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 0934E3A0FC7; Fri, 22 Jan 2021 00:15:31 -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, DIET_1=0.001, 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, RCVD_IN_MSPIKE_H2=-0.001, 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 PwoIJW5VBxyj; Fri, 22 Jan 2021 00:15:28 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30126.outbound.protection.outlook.com [40.107.3.126]) (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 C363C3A0FC5; Fri, 22 Jan 2021 00:15:27 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UD+j65ePIlcsV1BzvzWlIu6XvWRIZX6WOVYDYb9J7H9CrfM5RQVwIOwSS3Y4YLobXvKWtBkrGEm4r0WnND7Oo4poPq9Nrj9ZjeOUFf/BNenUuhZFR6hpvNvG50gTKVICcb3opyTBW5ICYCCln/4eORegYTEboQVQVl+JJO1tyOBs9fOKHNDvc026mD9aW8QVYq7KblaPD9Z+5hGz0CtJJ+BTOEFXJ77LZaeWZNP+F3eEfzXH7xWWiaCNU0qUb5PQTW5wwmcJSf2cw6TfQF8ZTvOkZ48sDXiYn6+PYFDELJp4fMxeE9hJA3gT7RDpSHtMEyeH4x12xYF6+kIIQl3PeA==
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=ojrW3YYpWlg6YlO+Ffwr6dBCy8oSviyGucKxJ0Q+m3E=; b=PYv/ZOHrjXz6ZnGOoDr23LDm4j4GDFSRH2e15aZpdlWtVopCabRJlHWtNe5EGTL4ZW0xaSj843sxJCFO9FiKw0IzUAgTh5fI7EGYgckZb4OgIR7Gi2F1QOhRTPDD/U9AK0B3sBhXI+Ri534svYlHMH8UWd3KalAl311/HjNnDwn6xszTzrqbauKHeZkj8O8MuriORaIGbMULiAMt4LG4gn1DGtewC5zKUdB53gD+MEKe+b8sGsRsnApga81uvSS33KPo+2EawOKN5jBwBzsg7uZ3zZgnllXunuPqLbiLKJ4KaRO56Li4ynT+fJoliqz0uo10/I1hffrDX44wlKG6dg==
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=ojrW3YYpWlg6YlO+Ffwr6dBCy8oSviyGucKxJ0Q+m3E=; b=sElt8aSytNPBxlcdiHJq2LmmnKhFiARq78pJmOJ4y+gsm08NhiWm4v5+SI13lvhDLNmInRd0Fc4rFycbdbLjQjcUTaQKjx5qC6DTBvXCcwADnGuRFlrMr9OlHBPtAFLpowJHjJvjgJO+Y7HNL+rjcFc+kk+vQdCi8as/Uk2lGHo=
Received: from DB7PR06MB4792.eurprd06.prod.outlook.com (2603:10a6:10:57::20) by DB6PR0601MB2360.eurprd06.prod.outlook.com (2603:10a6:4:1d::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.15; Fri, 22 Jan 2021 08:15:24 +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.3784.012; Fri, 22 Jan 2021 08:15:24 +0000
From: David Lake <d.lake@surrey.ac.uk>
To: Sridhar Bhaskaran <sridhar.bhaskaran@gmail.com>, Kaippallimalil John <john.kaippallimalil@futurewei.com>
CC: "apn@ietf.org" <apn@ietf.org>, "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>, Uma Chunduri <umac.ietf@gmail.com>, Lizhenbin <lizhenbin@huawei.com>, dmm <dmm@ietf.org>
Thread-Topic: [Apn] [DMM] Regarding APN Usecase in Mobile Core
Thread-Index: AQHW8HirlUlobjaqp0SpVgJfcs2g9qozSuKg
Date: Fri, 22 Jan 2021 08:15:24 +0000
Message-ID: <DB7PR06MB4792E6BC84478020B120C6E8B5A00@DB7PR06MB4792.eurprd06.prod.outlook.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com> <CAF18ct4nYsk9nNBN0enCeLwhUuSF1Quy+MTUoe7Gb3yYmjOU2w@mail.gmail.com> <aae1d163a31b4ff8b31c4f90751c3d0c@huawei.com> <SA0PR13MB408027C75E2F3FAACCC8404CE8A19@SA0PR13MB4080.namprd13.prod.outlook.com> <CA+3a8OYUPpUyd56PFC48g=sr9OvaQb82qOvUv9znYXm3Y+vWQw@mail.gmail.com>
In-Reply-To: <CA+3a8OYUPpUyd56PFC48g=sr9OvaQb82qOvUv9znYXm3Y+vWQw@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: 4da2060c-473e-4bf5-1624-08d8beadde58
x-ms-traffictypediagnostic: DB6PR0601MB2360:
x-microsoft-antispam-prvs: <DB6PR0601MB2360ED26C4D93CC01D865B2DB5A00@DB6PR0601MB2360.eurprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: A1+qBbKExjHLL38WIaDvTCQYs+Jk9qHncaHvek3z+WreqR6A6bHaJR/vwwUi23TeIAt+NE181XjbfDo/ir1VWvc89ap1/8B3EZWX7rn3pGpDo6bhRndG+JewbcevRdTamDm3r1j+DXwzUNWijNBHk98v+gJ90dB//ii6NhN7AKe4qQGYTVAJEqysk/t+iGi079mNYtMYSnkmAnpNLZZyj6yaDDLuKdSxumZzLL6URsO9sapaes6Yi9yVfBO3e85nZa9uThY4TZhk8b8kv2dmyI6OgtAjYPa7WpMLZutUvoxXZrvvAd6qHuUF270YsRNrhdFdUwANcQIUzt0O6Zi6rxGv9YBnbTz0CoyA5YxS26zJlSRckpGeqqZweDgM8MFyQQScYpM0nkqw9+XDCGHt8o7kdtZUj2abt5KhjcpDtIWubZFl1+H0Mi12r71cuBNiz34MP7+gVCP9AG+Z0xmNhQ==
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)(346002)(39840400004)(396003)(136003)(366004)(376002)(86362001)(166002)(966005)(7696005)(76116006)(66446008)(5660300002)(33656002)(66946007)(52536014)(66476007)(66556008)(64756008)(21615005)(9686003)(478600001)(54906003)(110136005)(8936002)(2906002)(26005)(186003)(55016002)(6506007)(53546011)(71200400001)(4326008)(8676002)(786003)(316002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: VbEitK7VjWIR13jMb+vq9hHeL0eRNu0mjaDyX2ilZgxmy3kKEvl0JzCVxyG096AxhXnRyxHvWzgXTY+eN52eEobkEj/fLPu+KUY3HGHOTpaiENjwLwwsaeUUSah4b4ZczcFynTr+SkowdRoWgnaiz5CnJbqg70HQEXP4eMjDKjMlIrVGxElRj/8j58p0tLoH32v3jQdQE2Of5HWmWd5d2m/D79wHFD0yYXny+1iUEvJ+NqnIL4I0vKYIssMXVU1SEcoSGVcpNOUaYZGqdbqqHqjoUeKfWYATddvVJ7lDKCm5X/N4i9Ng/JVYwecAjJu8E49CF2aFH8e9gzhculYEmdlSDNSqOyVID3NxBcWWVpdJTCKURtw5T4sXa3UVWhKwPhdgYcngTlq6iRTO7wV994EqsPWlohM3b2kIzlSniRH652Yc6C02KdHlzDwEht2NkAQRp+btCYUZsmz7kbjVYAbcgMPtLM4vw1WkzoARlznw+RW6KCMElZt7GtmgIJ1Ira+8hp+1ZWoL5XX6JGTMm0qEQSB7ClNycj2S7nrfCl4oNhS2OCC6qoWCEKMcWySkXPB4s52cHZkqm4SgD2zGwC4TA/o9/+tD+1iKlRWGL4c8FIkZh7r73PXo2fNfSqxKMNNBL1YgehpdR+OWVseoOdNplfnFTYst8VIOA79Qyx9oMgMHbuTMuZ/ptUWZMCmeBzo5TUXpd8+S1j8AMWl9FSJjh/URgWyHIIsN/wyddXoAHyqvGbVV4d1hkf7ZIeNbd8JzuFppu8kol5LYV12JYWC7t/T0CpgCa9t9TZ0n7zpV2zMDgmMi5VVYJUDqXbzYrMr+NJzrNoL1neq3UJODZPTGXHMCdN3qrIFB3vwydJeblFMAXlzTh1x29SXi1FMHlsuT+nZuJ93mNlZrFvQySdPsXYvrBGSNmJDy9bfLgOVK5MbYMT6BFUbUBP7MGPovK6lCaTCiJbSGk0jF5wf2WNGfaZkUhbhFlcLG/ifWFZ0=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DB7PR06MB4792E6BC84478020B120C6E8B5A00DB7PR06MB4792eurp_"
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: 4da2060c-473e-4bf5-1624-08d8beadde58
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jan 2021 08:15:24.0900 (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: aLVGn72/Z1Pr4aPbKc///qLaWkFexSx4ZYlJzsfEvjkKw/cFFS5C1XpkFoKMldz8wDtKCsAgI8lsgINoSSuZIA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0601MB2360
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/vAKqiEIX_1K8U3YtmNyeGrhgKnQ>
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: Fri, 22 Jan 2021 08:15:31 -0000

Adding to this.

The various radio bearers will be established based on APN (that is the 3GPP APN, not this one) and there will be several parallel paths between UE and eNB.

The Traffic Flow Template is installed in the UE on EPS Attach and effectively gives "rules" to the UE as to which bearer traffic should be sent on.   That match is primarily on IP 5-tuple.

This is mapped at the eNB to the appropriate GTP tunnel so that QoS can be maintained across the air-interface and the packet core.

https://www.sharetechnote.com/html/Handbook_LTE_TFT.html

A common use for this is for media in VoLTE which is placed into a GBR radio bearer and then passed across a GTP tunnel with a matching set of QoS treatments.  The VoIP traffic is "steered" into the VoLTE APN at the UE by the TFT and then placed into the appropriate GTP tunnel by the eNB.

The same may be translated into 5G which really is no different in terms of protocol and attach architecture from 4G.

David

From: Apn <apn-bounces@ietf.org> On Behalf Of Sridhar Bhaskaran
Sent: 22 January 2021 04:39
To: Kaippallimalil John <john.kaippallimalil@futurewei.com>
Cc: apn@ietf.org; Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>; Uma Chunduri <umac.ietf@gmail.com>; Lizhenbin <lizhenbin@huawei.com>; dmm <dmm@ietf.org>
Subject: Re: [Apn] [DMM] Regarding APN Usecase in Mobile Core

Hi Xuesong,

In addition to what John said, in 3GPP networks there is one GTP-u tunnel per bearer (in case of 4G) and one GTP-u tunnel per PDU session (in case of 5G).

One UE (user equipment - i.e mobile device) may have multiple PDU sessions and hence in the network there may be more than one tunnel for a UE. The scope of GTP-u tunnel is from UPF to gNB only. GTP-u does not go all the way upto UE. The GTP-u header has a field called "TEID" (tunnel endpoint identifier). The TEID in the header identifies a context in UPF and gNB. The context gets established through signalling plane. The context provides information on the QoS to be provided for the bearer,  PDCP ciphering keys applicable for the bearer context etc.,. If there are a million UE that are getting connected to a UPF, there could be few million GTP-u tunnels (TEID).

In summary:
1. The 5QI / QFI marking in the GTP-u extension header provides a lookup for the general QoS characteristic applicable for that 5QI
2. TEID in the GTP-u header provides a lookup for UE and bearer specific contextual information for any differentiated treatment.

Regards
Sridhar

On Fri, Jan 22, 2021 at 2:55 AM Kaippallimalil John <john.kaippallimalil@futurewei.com<mailto:john.kaippallimalil@futurewei.com>> wrote:
Hi Xuesong,

Traffic policy for subscribers is managed per PDU session at the UPF (and gNB).
GTP-u does provide encapsulation between the end points, but its control fields are meant for conveying control semantics between the GTP endpoints: they were not intended for IP transport/ traffic underlays. 5QI/QCI etc are in the GTP extension header which may not be ideal to lookup to classify each packet in the transport network.

The entity that classifies data packets (upstream at gNB and downstream at UPF-PSA) also inserts the DSCP for that GTP packet. The classification is based on subscriber aspects but may also on be based on its content (e.g., using DPI).

Best Regards,
John


From: dmm <dmm-bounces@ietf.org<mailto:dmm-bounces@ietf.org>> On Behalf Of Gengxuesong (Geng Xuesong)
Sent: Wednesday, January 20, 2021 8:23 PM
To: Uma Chunduri <umac.ietf@gmail.com<mailto:umac.ietf@gmail.com>>; 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: [DMM] [Apn] Regarding APN Usecase in Mobile Core

Hi Uma and all,

I have read the document and got a few questions:
In my understanding, in the UPF where traffic policy is enforced, the fine-granularity services are provided. Then what fields in the GTP-u encapsulation indicates the traffic's service requirements? When a GTP-u tunnel goes into a SRv6 policy, according to which fields in the GTP-u encapsulation the DSCP is generated? We know that there are parameters such as 5QI/QCI and QFI, whether they are associated with a GTP-u tunnel?

Best
Xuesong
From: Apn [mailto:apn-bounces@ietf.org] On Behalf Of Uma Chunduri
Sent: Tuesday, January 19, 2021 3:17 AM
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%7Ca43430026077453c0d1608d8be8fcc6a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637468872116232514%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DHZzzrXBa%2BO6Lv5Sf8XpMJtmupMBO3tmwhg8wFSfT4%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%7Ca43430026077453c0d1608d8be8fcc6a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637468872116242509%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vJ6bPTF5T6DTZ28dGO0VhxcGRh2e63T6tJ2yo3XSlGE%3D&reserved=0>
_______________________________________________
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%7Ca43430026077453c0d1608d8be8fcc6a%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C637468872116252500%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fj6gSxtJHdircaflUmtaYgOJPyfYbWKsJT5F2Udm6Zs%3D&reserved=0>


--
 o__
 _>  /__
(_) \(_)... Burn fat not fuel - Bike along to a healthier life and cleaner
world! :)

Sridhar Bhaskaran