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

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Mon, 01 February 2021 03:33 UTC

Return-Path: <gengxuesong@huawei.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 996323A134A; Sun, 31 Jan 2021 19:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 zBOrb1wsV_jt; Sun, 31 Jan 2021 19:33:23 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3114A3A133E; Sun, 31 Jan 2021 19:33:23 -0800 (PST)
Received: from fraeml708-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DTYNK096Kz67XjD; Mon, 1 Feb 2021 11:29:53 +0800 (CST)
Received: from dggeme751-chm.china.huawei.com (10.3.19.97) by fraeml708-chm.china.huawei.com (10.206.15.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Mon, 1 Feb 2021 04:33:19 +0100
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by dggeme751-chm.china.huawei.com (10.3.19.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Mon, 1 Feb 2021 11:33:17 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.2106.006; Mon, 1 Feb 2021 11:33:17 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Kaippallimalil John <john.kaippallimalil@futurewei.com>, Uma Chunduri <umac.ietf@gmail.com>, Lizhenbin <lizhenbin@huawei.com>
CC: "apn@ietf.org" <apn@ietf.org>, dmm <dmm@ietf.org>
Thread-Topic: [DMM] [Apn] Regarding APN Usecase in Mobile Core
Thread-Index: AQHW8DvwXJtnK5wofEqwUcHMfFEdSqo+ZbEw///y2ICABFvS8A==
Date: Mon, 01 Feb 2021 03:33:17 +0000
Message-ID: <11c35afa61d845a0a4e14531630bcfab@huawei.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com> <CAF18ct4nYsk9nNBN0enCeLwhUuSF1Quy+MTUoe7Gb3yYmjOU2w@mail.gmail.com> <aae1d163a31b4ff8b31c4f90751c3d0c@huawei.com> <SA0PR13MB408027C75E2F3FAACCC8404CE8A19@SA0PR13MB4080.namprd13.prod.outlook.com> <6c0e8164b76748e5ab21fc6f2d280e2b@huawei.com> <SA0PR13MB4080548CA69DDD2FAD89A83DE8B99@SA0PR13MB4080.namprd13.prod.outlook.com>
In-Reply-To: <SA0PR13MB4080548CA69DDD2FAD89A83DE8B99@SA0PR13MB4080.namprd13.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.242.209]
Content-Type: multipart/alternative; boundary="_000_11c35afa61d845a0a4e14531630bcfabhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/sRQQGkOjM-RmNoDtkHr7xqeRm9o>
Subject: Re: [DMM] [Apn] Regarding APN Usecase in Mobile Core
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2021 03:33:27 -0000

Hi John,

Thanks for your comments.
Please find some response inline.

Best
Xuesong


From: Kaippallimalil John [mailto:john.kaippallimalil@futurewei.com]
Sent: Saturday, January 30, 2021 12:56 AM
To: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>; Uma Chunduri <umac.ietf@gmail.com>; Lizhenbin <lizhenbin@huawei.com>
Cc: apn@ietf.org; dmm <dmm@ietf.org>
Subject: RE: [DMM] [Apn] Regarding APN Usecase in Mobile Core

Hi Xuesong,
The point on using GTP-u extension header for classifying each packet was that unlike classifying using DSCP (which is in the IP header), finding the QCI in GTP extension requires more searches. And the control fields in GTP-u are for signaling between the 2 GTP end points (gNB, UPF, etc).
[Xuesong] According to the email from Sridhar, does "requires more searches" mean that: gNB/UPF needs to first read  QFI in GTP-u extension header, then map it to the 5QI via the QFI, and determines QoS processing based on 5QI?

Now with regard to DSCP, since it is a mutable field, the value can be changed on path. It may be suitable in some deployments but not as a general solution.
[Xuesong] Sorry I'm a little confused here. What does "control fields" refer to in GTP-u here? The signaling is in control plane or data plane?

In a gNB or UPF, there is already the subscriber context for a session and identifiers like radio bearers or IP address (upstream/downstream) to classify incoming packets.
[Xuesong] "DSCP is a mutable field" may be an important limit as the interworking identifier between transport network and mobile network. But I'm not sure whether DSCP is also used in gNB or UPF, rather than transport network, for session context index?

E.g., a UPF may look up session context indexed by a UE IP address, retrieve QoS, reliability, etc , classify and select MPLS label L (or a DSCP value in some cases).
[Xuesong] The concept of "session context" is very interesting here. It seems like "session context" could be indexed by UE IP address and it could indicates QoS , reliability. Can I find more detailed specification about this in other documents?

However, when there is a gNB or UPF function deployed in one network and IP transport is provided by another network, DSCP may not be able to convey slice aspects for a path across two different networks (this apart from DSCP being mutable).
[Xuesong] Network slicing brings more complexity here. Do you think the issue of 5QI->DSCP could also be discussed together with network slicing mapping? Or we could keep them independently first?


Best Regards,
John

From: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com<mailto:gengxuesong@huawei.com>>
Sent: Friday, January 29, 2021 4:01 AM
To: Kaippallimalil John <john.kaippallimalil@futurewei.com<mailto:john.kaippallimalil@futurewei.com>>; 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 John,

You mentioned that "5QI/QCI etc are in the GTP extension header which may not be ideal to lookup to classify each packet in the transport network". This is slightly different from my understanding about this: 5QI/QCI belongs to control plane information, and when the base station encapsulates the packet with GTPu, it maps the 5QI/QCI into the DSCP in  IP header outside GTPu encapsulation. Do I have any misunderstanding about this point?

Best
Xuesong

From: Kaippallimalil John [mailto:john.kaippallimalil@futurewei.com]
Sent: Friday, January 22, 2021 5:25 AM
To: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com<mailto:gengxuesong@huawei.com>>; 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 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-dmm-5g-uplane-analysis%2F&data=04%7C01%7Cjohn.kaippallimalil%40futurewei.com%7C8d3a8d34ea0049ed523f08d8c43ccbc9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637475112703506588%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=r6m55gGEQqmacjcKy21wzksXsCzvxLBF%2Fx%2FqUFFxFPU%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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fdmm&data=04%7C01%7Cjohn.kaippallimalil%40futurewei.com%7C8d3a8d34ea0049ed523f08d8c43ccbc9%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637475112703506588%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5lmTCot3wizMZWRXkGRQDP8c03xbCGVOqNIBo1tplx0%3D&reserved=0>