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

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Mon, 01 February 2021 02:40 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 4372E3A1542; Sun, 31 Jan 2021 18:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level:
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DIET_1=0.001, 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 s-oacYZUSDu3; Sun, 31 Jan 2021 18:40:26 -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 252113A1541; Sun, 31 Jan 2021 18:40:26 -0800 (PST)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DTXCD1pmcz67jYL; Mon, 1 Feb 2021 10:36:56 +0800 (CST)
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by fraeml705-chm.china.huawei.com (10.206.15.54) 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 03:40:22 +0100
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by dggeme754-chm.china.huawei.com (10.3.19.100) 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 10:40:20 +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 10:40:20 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Sridhar Bhaskaran <sridhar.bhaskaran@gmail.com>
CC: "apn@ietf.org" <apn@ietf.org>, Uma Chunduri <umac.ietf@gmail.com>, Kaippallimalil John <john.kaippallimalil@futurewei.com>, dmm <dmm@ietf.org>, Lizhenbin <lizhenbin@huawei.com>
Thread-Topic: [Apn] [DMM] Regarding APN Usecase in Mobile Core
Thread-Index: AQHW9jcrn6qe5zGXHkm+SgQ+I+rJsapClGvA
Date: Mon, 01 Feb 2021 02:40:20 +0000
Message-ID: <1fe994365b33407984374f4cdd224911@huawei.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> <ab90f474c10048f6b552d863e981a945@huawei.com> <CA+3a8OaEA02oZ8Oo2mHTzX+atK1bufkNOei64XG=96uPsVGfYA@mail.gmail.com>
In-Reply-To: <CA+3a8OaEA02oZ8Oo2mHTzX+atK1bufkNOei64XG=96uPsVGfYA@mail.gmail.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_1fe994365b33407984374f4cdd224911huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/zLVLs5B0XeIXreVVWPHO-U1F_NE>
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 02:40:29 -0000

Hi Sridhar,

Thanks for your explanation. It is much clearer for me as the following:

ž   UPF < ----- GTP-u tunnel [PDU session]------ > gNB

ž   PDU session contains multiple QoS flows [QFI marker->5QI]

ž   QFI marker in GTP-u extension header
5QI is not in GTP-u header directly but could be indicated by QFI. So the QoS requirements presented by 5QI can’t be used/seen by transport network in the existing in the current implementation (TEID is similar). And DSCP can act as a mediator between transport network and UPF/gNB.
Maybe the existing question becomes whether DSCP is sufficient for passing information from the mobile network to transport network? whether there is any simplification or omission of information in the mapping to the DSCP?

Best
Xuesong


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

Hi Gengxuesong,

QFI (mapped to 5QI) and TEID are to identify QoS flows and PDU sessions within UPF and gNB. They are not meant for transport network to look into. UPF and gNB map QFI to DSCP marking in the outer IP header which the transport network can use for differentiated services.

Regards
Sridhar

On Fri, Jan 29, 2021 at 3:37 PM Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com<mailto:gengxuesong@huawei.com>> wrote:
Hi Sridhar,

Thank you for your additional information. Can I come to a conclusion that: both 5QI and TEID have the potential to provide additional information for differentiated services in transport network, although the two parameters act in different scopes?

Best
Xuesong

From: Sridhar Bhaskaran [mailto:sridhar.bhaskaran@gmail.com<mailto:sridhar.bhaskaran@gmail.com>]
Sent: Friday, January 22, 2021 12:39 PM
To: Kaippallimalil John <john.kaippallimalil@futurewei.com<mailto:john.kaippallimalil@futurewei.com>>
Cc: 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>>; 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,

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://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%7C77632db844b34a8e561108d8bdb38cb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467926158632424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=5nVGUJhkHBn7FWHUCFPC4lGhwr6lBqtIWNyY1o0dxsg%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%7C77632db844b34a8e561108d8bdb38cb8%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637467926158632424%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=oHJnGPO3hUL9xPkObVLsJ5S1JnwGOF6IeJrLADLrTVA%3D&reserved=0>
_______________________________________________
dmm mailing list
dmm@ietf.org<mailto:dmm@ietf.org>
https://www.ietf.org/mailman/listinfo/dmm


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

Sridhar Bhaskaran


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

Sridhar Bhaskaran