IETF Logo Mail Archive

[DMM] Regarding APN Usecase in Mobile Core

Lizhenbin <lizhenbin@huawei.com> Mon, 18 January 2021 13:25 UTC

Return-Path: <lizhenbin@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 3F2883A132D; Mon, 18 Jan 2021 05:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 6L50CNn-Ue67; Mon, 18 Jan 2021 05:25:38 -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 15ADA3A132B; Mon, 18 Jan 2021 05:25:38 -0800 (PST)
Received: from fraeml742-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DKC9R5Jyjz67cmj; Mon, 18 Jan 2021 21:21:31 +0800 (CST)
Received: from fraeml742-chm.china.huawei.com (10.206.15.223) by fraeml742-chm.china.huawei.com (10.206.15.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 18 Jan 2021 14:25:36 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by fraeml742-chm.china.huawei.com (10.206.15.223) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Mon, 18 Jan 2021 14:25:36 +0100
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.154]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0509.000; Mon, 18 Jan 2021 21:25:34 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "apn@ietf.org" <apn@ietf.org>, dmm <dmm@ietf.org>
Thread-Topic: Regarding APN Usecase in Mobile Core
Thread-Index: AdbtnTwkvWaRqLjmRvCQ5SUSFivHQA==
Date: Mon, 18 Jan 2021 13:25:33 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.46.16.182]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9DGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/_P5ywp84I1WWEQW5zyolsYBFmbc>
Subject: [DMM] 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, 18 Jan 2021 13:25:40 -0000

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. 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)

v2.23.0 | Report a Bug | By Email