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

Kaippallimalil John <john.kaippallimalil@futurewei.com> Thu, 21 January 2021 21:25 UTC

Return-Path: <john.kaippallimalil@futurewei.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 9F64D3A0CDF; Thu, 21 Jan 2021 13:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 2ytmpx5NAItU; Thu, 21 Jan 2021 13:25:14 -0800 (PST)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2117.outbound.protection.outlook.com [40.107.243.117]) (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 6D01D3A0CDD; Thu, 21 Jan 2021 13:25:14 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ciulbY3LPhyrTfCbz4p4FvXuG/yY7RfBq8/RgvnozOw/pJu4Y5vKPXeXZnjIJkrw5NLOBibt214M/+RGJ2uVLON7NGpcUAWuv8MOBu/PEut9fi1u34Qsk27aFqF9qs/0X6ilk/5D471FYNfivJNlanI/ZdoPV7wBNXMi4/qR3dPQVnqkPjNptFlvN1jxYY0VadT96YkdUMcHy8cE6ACJj/QxdGAmJc5ZnE9NBR8vMwQl/7U+/LlrIjhlUSQB7FgFl8xySmMcXKHHU1DEn6Fy3pGMbNMQ3nbTlbMj+2m+gjDi1a8Ntzz6833xKB4K73mN2AI0Buq6LS8npPs8nFaZIg==
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=iH8VP4jIVS9ZfgXcvwHGdRqIoyEhAOIxWWRNGP/AtTI=; b=EQ20F9v8gZSpWq2rwpfF087NBxarBS22n4FuNO3+fzWdJ4kAkHWeMxB+yDDqUOGfOtifyR/lgAs/u27mrKywxHXa6CeYD5ywZrElT673oeeqrXVhFwk9XqOWHZI+L8Lp+QJjjp9kTuD6fdhL9Kuq8S0hplgxY/ZzansB6oE0Yo7GmAK8H6OXXPyA2FoLKr0AVan3s6bzt7jD0CXL7U0H4K0bVo6G6XAZdO2oERyjJEM3vIvr8r3yypkcJND3WhwHF79UWs/OkoMYMgN6o4EKZyu3cY9RaQZwBRuqUqRfT8d7BYuAjbdh6t7zJ23LF582QizMd0g3mcQ03y+/4PZZEQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iH8VP4jIVS9ZfgXcvwHGdRqIoyEhAOIxWWRNGP/AtTI=; b=K9tbFTKO4ryurkF53TPoGd+zXJsImBHeNG8GR05CNu6lEd0DxIm2/etVtozRgmU7fLc5voObj87xiZk/x/TYw6ZlLmJ1yQQCdn7CZoR7VKdk6oBUsOYEGR4tKAfDlEiVlFXFa+qy6UuY2xt+XBQJAPrO1hF3Q7iRrMgy5Pp2+a0=
Received: from (2603:10b6:806:9b::22) by SN6PR13MB2464.namprd13.prod.outlook.com (2603:10b6:805:62::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.6; Thu, 21 Jan 2021 21:25:10 +0000
Received: from SA0PR13MB4080.namprd13.prod.outlook.com ([fe80::d905:dc1a:7cea:8a79]) by SA0PR13MB4080.namprd13.prod.outlook.com ([fe80::d905:dc1a:7cea:8a79%5]) with mapi id 15.20.3805.005; Thu, 21 Jan 2021 21:25:10 +0000
From: Kaippallimalil John <john.kaippallimalil@futurewei.com>
To: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.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: AQHW75xrkd2Ql7I3CUy/a8odgG8eZqoydang
Date: Thu, 21 Jan 2021 21:25:09 +0000
Message-ID: <SA0PR13MB408027C75E2F3FAACCC8404CE8A19@SA0PR13MB4080.namprd13.prod.outlook.com>
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com> <CAF18ct4nYsk9nNBN0enCeLwhUuSF1Quy+MTUoe7Gb3yYmjOU2w@mail.gmail.com> <aae1d163a31b4ff8b31c4f90751c3d0c@huawei.com>
In-Reply-To: <aae1d163a31b4ff8b31c4f90751c3d0c@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [12.111.81.80]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a767e874-9875-44f3-455c-08d8be530825
x-ms-traffictypediagnostic: SN6PR13MB2464:
x-microsoft-antispam-prvs: <SN6PR13MB24644EEDBA0552A3E6FBC5A3E8A19@SN6PR13MB2464.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Jzluigfyci5J7q8k5MelvDTEZLvTrDtVQTu+xXQcXbg1velkdbOHP8KpP9qa9/oLORffBivJum74+fFM+ltWZppkAQSLD/x8wIpU8FR5IdvbDzlBiprGBZHQoKeI8xeAzjUofPcXeWMK8BAtS0yLRtoSjJFoOVI15D9l0r98OmbS7bI5VyxQrXz+AiE6uZWFK2OdZwMD7avBWYUHx/k8JAEC7+WtllyUKmxlj34OODe62DRXwwWc1rUn3ljP6eREUEcMnhsXDaq76qWNtmjt7hmpfByQqD6G5uqj0fhv9dSvMLUXn0DC4/mcl6fFvtkT8pRXSlORZp7PZnSVO97FeN//zgyc0UTBS0XfBF93R0xC4aRD3KqOPSZD/obXDL0nbwOYOXHGXGNrQLvjfgu6sLSFQBgOz/M/MSjb4x3G1CgAHWrEZNA3zHMrbFO6bSit1ZOzva8CWhCt/i7ERUnC+Q==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SA0PR13MB4080.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39850400004)(366004)(136003)(376002)(396003)(346002)(66446008)(64756008)(9686003)(66476007)(66556008)(8676002)(2906002)(966005)(66946007)(76116006)(316002)(5660300002)(26005)(52536014)(186003)(7696005)(86362001)(8936002)(33656002)(9326002)(53546011)(71200400001)(6506007)(166002)(55016002)(478600001)(4326008)(54906003)(110136005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: 9EAsYopWzihLMu6m3ku5zEbrJVuP36GX+cIAi3gIgeQz0u/X5ksaVWUkOX1nE4zj3cvESUKLp49crkKESMRrxJfHUUMHCh0TUCcpWAFUS2KB72TBcfeZ9Uo15nGNppa0u6UZ0gJETd3fc/ifrQo/YEweqTfmgnFd9Xqa6cKhG8H40aUGrwfcNJ14B6UVPXhm5kWPRSyuS2nO60vpgjo0pI2H5N50vzMPGA62/JZybX29CUYIgUyUCVpi4s2j+zqPuozBQ1Pk16EDKZ/5dIFOIBXFQ9L/oezo+HhaHo9COukdl14LDdgZ7ipR1FpUkq+zSIoaeFgevy9qCQccSVSGubM9AFRqxY8glkHp2W7whUxDo1xZLnFHPTE/R03WhRjAHtgYJU/lg/cAYPWLg8cWUQP9ClX4ZQsmL7seXBzma/M5OOQ3DvFoiQMj3Fko5BB/mMv6T9+Zvb8WmRNQaY2bJIpnJeeX6qug1j6RZD4TsZGxx+AeCG62Q17CLvKI6xTq+Sd6tUSVOrczs2f2wjsIRxGX54rJYL2TZiXNbiYp4hthWD9YOS8tp19UUklcwe7MgB0DrJ/K+F7gveAQHwYW2MrjQR0JmcgQk/7U/mYSNy6T2RY7kq8m+0kIvO5ZMOfd7FH92tNx7b1tPaBae86HdPdBhIGFD/gipVX/P5p/+SEpD4hiqupEjG1ZhcEi+2bO7pWdkFoKkMVO4fBgcDJl4aURt3xWTeWEy2B4tTwztbF9ahllp+VS0wq8WrNg+eX/A7LCqxAt+GhOa+H+8uMAOWiboWE+YwlyJMSsVzd2DR6Cvk/MhqZc/3JjElMjZps9hsWC1O//kRO9bQmOGSbV7kBujsUsFMBFaDdwh6Lcwjs/mkVW/nEE3+iVRF+NW2eiywffOfb+UnppAJxyakWcvAaPzpwhV7jTdL8zi6/kfQNl8TtL4Y9gv/yUUF6VxD2LAjGTMCoSC1mimWV3fZQ84vl984JmWJi5U68gH5qD+qc=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SA0PR13MB408027C75E2F3FAACCC8404CE8A19SA0PR13MB4080namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SA0PR13MB4080.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a767e874-9875-44f3-455c-08d8be530825
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jan 2021 21:25:10.0272 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: shBSNzcuftDAFI/bDmj0KATwzUPN9EPCsmKP7o0GkjjvrAUx3gLK2+26ezM1lGsRNGJlKMJIOp33rrofQ/F9TQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR13MB2464
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/dboanR_n5sXdUDv699RPS5T9Pwc>
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: Thu, 21 Jan 2021 21:25:17 -0000

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> On Behalf Of Gengxuesong (Geng Xuesong)
Sent: Wednesday, January 20, 2021 8:23 PM
To: 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 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>