IETF Logo Mail Archive

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

Uma Chunduri <umac.ietf@gmail.com> Mon, 18 January 2021 19:17 UTC

Return-Path: <umac.ietf@gmail.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 4F5CA3A0317; Mon, 18 Jan 2021 11:17:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=gmail.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 g6xx3M1KxJjv; Mon, 18 Jan 2021 11:17:03 -0800 (PST)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F1F73A02BC; Mon, 18 Jan 2021 11:17:03 -0800 (PST)
Received: by mail-yb1-xb2b.google.com with SMTP id f6so13641391ybq.13; Mon, 18 Jan 2021 11:17:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0sgKJl9RArTyLh0v2qvY08ajY2wT1Gbov9SqZZiN7hQ=; b=snf0L1idan1ymegNw2wnR1+0ssXfOqoMSI0yQcGlhFS5UcacgTQ7lan7fZ65pAqREi U7O2qd8Okchb1WqwNqzMxL8vVKW8DrCrmGA2NnQH+FSvpA9HNO82Bo/EYCCPTe+p2PGg hM6D81OFtc7NfStDxkiC++drAbDUSOr5PzSvnMAtsxOTnRDcyuxkYxS6/xCMD7HdFOxP 2BJGtSLNndw5Uf3754hBlH/m8UOGdTWEDaVTses1hPFBAApm2eErIM4+yIOzC5qzNfkz NlbrlBFFG5iGs0ml0mfl8Yniuc6xtNreckiF7/elDP2OjElLXDBb75alWfnPI1yb5Sgs k8fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0sgKJl9RArTyLh0v2qvY08ajY2wT1Gbov9SqZZiN7hQ=; b=Z4hqOOTcriHEFmvjBJ9fW+DVAo0u2FcgbKO5xYkP054iV0q2c4RDdIGnNTL8snAaUr Cp8XrhpPujlZWBUoLEW+m1MRbgUc8Tk8CTZZm7ELRY2vj+oGw6Rj9r5JcZ87rTj6Qv5w L1JDu+kJ5vWLOFxct9g98B3zWmLQpx26JzR/QOqL7n2hp83WeJFbbQ3TXjYC+M3x333g QMTm9a/KvD6uIxlPwq07L/05N+OcrSUXVUwQL0dW5eKigdXser4hOTf8akL6q56bdQxB GaPCQ9HpNpKQ8cdwAG83oX0hUizczWxXSgih5I6slMUdbrr+poKF5ct/NRFkzQdNmn9V qeUQ==
X-Gm-Message-State: AOAM530RkkTQkH/EuSRY6jvWI/7cJ4m5A1KT45EArxXUZQAXH8t3KKyA tfGQddcMHMrwXD+B74d5knOrwasPUZADbgc1vB8=
X-Google-Smtp-Source: ABdhPJwS+r4BZiC6iSkqk7lW+XUoPD4YtQDtjMGkR6Za8WpA4yOdIa/0fi2/pobsQqlDn+xGq70R5cjOqiYaZT1yC0I=
X-Received: by 2002:a25:1f87:: with SMTP id f129mr836444ybf.142.1610997422771; Mon, 18 Jan 2021 11:17:02 -0800 (PST)
MIME-Version: 1.0
References: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D939966D9@DGGEMM532-MBX.china.huawei.com>
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Mon, 18 Jan 2021 11:16:52 -0800
Message-ID: <CAF18ct4nYsk9nNBN0enCeLwhUuSF1Quy+MTUoe7Gb3yYmjOU2w@mail.gmail.com>
To: Lizhenbin <lizhenbin@huawei.com>
Cc: "apn@ietf.org" <apn@ietf.org>, dmm <dmm@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001e528b05b93191f0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/U1mx-f5JrUpm_VsUDc7IGa0uJ7k>
Subject: Re: [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: Mon, 18 Jan 2021 19:17:06 -0000

Hi Robin,

In-line..

Cheers!
--
Uma C.

On Mon, Jan 18, 2021 at 5:25 AM Lizhenbin <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/ 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
> https://www.ietf.org/mailman/listinfo/dmm
>

v2.23.0 | Report a Bug | By Email