[Apn] 回复: [DMM] Regarding APN Usecase in Mobile Core

刘 鹏 <liupengyjy@outlook.com> Sat, 30 January 2021 01:28 UTC

Return-Path: <liupengyjy@outlook.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 684343A1466; Fri, 29 Jan 2021 17:28:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=outlook.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 zJqUJbpqGvSp; Fri, 29 Jan 2021 17:28:38 -0800 (PST)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255012.outbound.protection.outlook.com [40.92.255.12]) (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 61A8A3A07DF; Fri, 29 Jan 2021 17:28:37 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=m+mhjaYvv6DIN3s0tD5eeyC1N3+BNvHUdAVue14zLnrVFV3NOxO9uTJaiQYrPXv3HcuRvgkjgg4DJ40609NdaXjgoiVb5QwTcOyQLzau2cVVKkcCu0369REiq75ZH1+Yvp+0CUVuli5PLWIZE6uhRM2OsC4hNT+GyEE26oF5o/WT6Xs1sA9Uyzuad9M0fVwNxs8csWBTv2MZEWR510vqP8aQGrDF2qpBxvSOin4v/zaLww31vb1JTOcpLhJiTqth7SEWsBsF9eN1oLoQVOReZdELGx0tNzVDg2Jtmmsrw20zO0tey/MTol49pvnJPVqQz2POraEyDWjim3A1iA2Z8A==
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=FhmcmtnMmYUrUkkMVmyEh1XzkgnU4X7H4hN4ydeiNT8=; b=liwYmYsY+fe7Dz1gn1hgdNo4g88oG2kXGZXEDGBUq0hF8MJikR0LkSEE+jQNNIibKGI0ihei06HuZnv0aPeKG8npcLVd4brmYSLoAyETQj8/ctyE7lPi/3yQcqHqkQqGP4Z10GCC392Pf6v3wXbeD2SmZKKyLma7l8Tyv1Cdv2QZM0MG+OrLSoJFEaBhRAkG7thcWKDftt1CE9fpgJE6MTDOiel73h+6TKj/Be0oexTGI645Mpd6j/f2aSApXSzLHsujyj/fbA3WFDk30nEIZVtRt1l/um/o1fHUaKXq3Ty/wy6FCSYycQ3hHxSz6frqO7d2+bzQrqMvmmzYVht0vg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FhmcmtnMmYUrUkkMVmyEh1XzkgnU4X7H4hN4ydeiNT8=; b=ihlDHlTPMJdUXZDe4osYzGgLsex1vCXglGoUTRkwbJqVbS2DQOWfoBZEGuxjW1nAIn/TU1apkqgkzZ3C6xvh6kzaPdEi7hE8w7vz9ksQn/YuuJY/47LZLdTuDLrZbQkycwF2sVURkLAJUYTU8OyOB4OiIUmS9XL9BSDosqh7ry/cwoA85l5fmTd7FGxC1i+4YW8yjX1OuL2rUEOUVHQSbtThRdnBTADH+X6YDTdJ0YcUgo76y+80VxjMt18CXyuVZ1mTmIH0xEoVQn1fITf9e/wmYLRC1jh3/gnq8AgyGcS5gakIbz6ygUMSsQ/IZiFI8pMcKhwEvmHRPftUnkQsYQ==
Received: from PU1APC01FT015.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebe::4d) by PU1APC01HT125.eop-APC01.prod.protection.outlook.com (2a01:111:e400:7ebe::295) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.11; Sat, 30 Jan 2021 01:28:28 +0000
Received: from OS0P286MB0338.JPNP286.PROD.OUTLOOK.COM (10.152.252.59) by PU1APC01FT015.mail.protection.outlook.com (10.152.252.227) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3784.11 via Frontend Transport; Sat, 30 Jan 2021 01:28:27 +0000
Received: from OS0P286MB0338.JPNP286.PROD.OUTLOOK.COM ([fe80::eddb:5d1d:6c0c:584a]) by OS0P286MB0338.JPNP286.PROD.OUTLOOK.COM ([fe80::eddb:5d1d:6c0c:584a%8]) with mapi id 15.20.3805.016; Sat, 30 Jan 2021 01:28:27 +0000
From: 刘 鹏 <liupengyjy@outlook.com>
To: Sridhar Bhaskaran <sridhar.bhaskaran@gmail.com>, "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.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: AQHW8Hi0HgZhOjAWKk2NjN+61VAewao+bC2AgAAhCgCAAN6/WA==
Date: Sat, 30 Jan 2021 01:28:27 +0000
Message-ID: <OS0P286MB0338CF95D14828B18EE977A9DAB89@OS0P286MB0338.JPNP286.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> <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-incomingtopheadermarker: OriginalChecksum:E4C154D82A3C667024C6F67CAFCB8AD2E0C221DA9A9BEE00666634ADA3512F65; UpperCasedChecksum:D813376E6D0F6234B3A5EFFD6C42052A1A7C3C4521EB120AB3A7AA309C057848; SizeAsReceived:7711; Count:44
x-tmn: [uy7bo8lFDO/dhT5pdHS5y8llgSl/2fmG2Xuxf6uafSwM/MxRqiOE+ZqAQxxfe8KJ]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: b1f92417-9d23-4c3e-579a-08d8c4be57f4
x-ms-traffictypediagnostic: PU1APC01HT125:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: c9p0iPHPqbbAWwHiQRSTFPKpUH2HBo7IU0OH+Hn3arrM+q+SjS9Q2i6osVMo42GKpn3+U0niA8UaufB0XDMfgUdBiOXkMX7kdcwpuVfDHz/uQmc3yO58frfo1B0N5p4/Ylx/zJ5QmxArdKFG0tx1VWtN1dU5f65zwpN+Y/NhEt6N2b9w9zHszkb2Kt1OC2zlTnSTo6i6dDT5MPhNkJmcy4kKoCGnyXRyIXnTA06DOSN5GIY5pVx2VYmN03n4EekEQ/aiXtMjT7eU6vJeCSQrN8jVGuVkIH2seScckilWmmqCbSZvuBCTfXaOn8hB7kMoyUTCvuTe2D3HBWYwUM2lUtx6UJX7HoHwnFx0FxZrc2WltDQMyggfr1Aa0Cg6fZ+MOSU+bEnTnIqN+voMQlyQwNVX/hXOOgup4IDz7m/lrq1E5qcKEchjIZs1ZXFK9Mb4
x-ms-exchange-antispam-messagedata: GsPe5WAduXgS/3HePimiahm8LCwdYersnAwRKstRc2jwvf0etCfsxg8GHRLdE67FrRL91OAcX/xQe0TxGSb58+QOK2uNZPE9GKFt51yesk22L2zS/2Ad3M178IbRLQWBzO7oZkP2nFCF0aVTdWM61lKAwHVG6VqHRpJ0V9GjtTrnIXyHB8OEG/dxIZlUb4KypbnLDC0SeG/Aa84tkc54Lw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_OS0P286MB0338CF95D14828B18EE977A9DAB89OS0P286MB0338JPNP_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: PU1APC01FT015.eop-APC01.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: b1f92417-9d23-4c3e-579a-08d8c4be57f4
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jan 2021 01:28:27.0590 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT125
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/0TTPdQE5X6ZXufZM3U4kx0oWB6M>
Subject: [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: Sat, 30 Jan 2021 01:28:41 -0000

Hi Sridhar and Xuesong,

If the IP network can obtain the QCI, TEID and other information of GTP, it can be considered as 5g's natural support for APN, and can also provide fine-grained services combined with N6 interface and edge computing. However, based on the previous discussion, it may not be able to directly obtain them. The value of DSCP alone may not be enough for APN.

It may need 5g network or UPF to make some additional support. Although it is not sure whether it is feasible, I think this information still has the possibility of potential support in the furture?

Regards,
Peng Liu

________________________________
发件人: Apn <apn-bounces@ietf.org> 代表 Sridhar Bhaskaran <sridhar.bhaskaran@gmail.com>
发送时间: 2021年1月29日 20:05
收件人: Gengxuesong (Geng Xuesong) <gengxuesong@huawei.com>
抄送: 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>
主题: 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