Re: [L3sm] [L2sm] R: Using VPN to offer eMBB, URLLC, mMTC service

Qin Wu <bill.wu@huawei.com> Wed, 11 October 2017 06:00 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005D4132D4B; Tue, 10 Oct 2017 23:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 eocW9fSJR2B2; Tue, 10 Oct 2017 23:00:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 545491320C9; Tue, 10 Oct 2017 23:00:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQH64746; Wed, 11 Oct 2017 06:00:44 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 11 Oct 2017 07:00:42 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.199]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Wed, 11 Oct 2017 14:00:36 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>, Aijun Wang <wangaijun@tsinghua.org.cn>, "l3sm@ietf.org" <l3sm@ietf.org>, "l2sm@ietf.org" <l2sm@ietf.org>
Thread-Topic: [L2sm] R: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service
Thread-Index: AdM7jwmvOhRxeqNQTXyc1m2Qg+iqpwGxuOjA
Date: Wed, 11 Oct 2017 06:00:36 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9ABA8B25@nkgeml513-mbx.china.huawei.com>
References: <38ffa9f963344f7baa746da6fc0edd57@TELMBXB02RM001.telecomitalia.local>
In-Reply-To: <38ffa9f963344f7baa746da6fc0edd57@TELMBXB02RM001.telecomitalia.local>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.163]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9ABA8B25nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59DDB38C.0139, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.199, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c9ce9bb04e7955aa5610a0474d9edcd8
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/xLedP-hIdSBraJ7nqWhMNZEb9Zg>
Subject: Re: [L3sm] [L2sm] R: Using VPN to offer eMBB, URLLC, mMTC service
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Oct 2017 06:00:51 -0000

Thanks Giuseppe for the proposed change, this is what I thought at this moment as well.

-Qin
发件人: L2sm [mailto:l2sm-bounces@ietf.org] 代表 Fioccola Giuseppe
发送时间: 2017年10月2日 23:18
收件人: Aijun Wang; l3sm@ietf.org; l2sm@ietf.org
主题: [L2sm] R: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service

Hi Aijun,
That looks like a reasonable proposal to me. The first thing we can do is to add new qos-profiles for eMBB, URLLC, mMTC services (see below).
Also service-oam  can be useful to verify the resource allocation and the end to end performance.
So, of course, we can use VPN service model to offer these services and, we can consider that the service orchestrator is responsible of the mapping between service characteristics and slicing by using L2SM.

Best Regards,

Giuseppe


    identity customer-application {

     description

      "Base identity for customer application.";

    }

    identity web {

     base customer-application;

     description

      "Identity for Web application (e.g., HTTP, HTTPS).";

    }

    identity mail {

     base customer-application;

     description

      "Identity for mail application.";

    }

    identity file-transfer {

     base customer-application;

     description

      "Identity for file transfer application (e.g., FTP, SFTP).";

    }

    identity embb {

     base customer-application;

     description

     “Identity for eMBB application;”;

    }

    identity urllc {

     base customer-application;

     description

     “Identity for URLLC application;”;

     }

     identity mmtc {

      base customer-application;

      description

      “Identity for mMTC application;”;

     }


Da: L3sm [mailto:l3sm-bounces@ietf.org] Per conto di Aijun Wang
Inviato: sabato 30 settembre 2017 09:52
A: l3sm@ietf.org<mailto:l3sm@ietf.org>; l2sm@ietf.org<mailto:l2sm@ietf.org>
Oggetto: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service

Hi, All:
IP convergence is continuing to drive new classes of devices to begin communicating via IP.  Examples of such devices could include STB boxes for IP video distribution, cell tower electronics (macro or micro cells), infrastructure Wi-Fi access points, and devices for machine-to-machine (M2M) or Internet of Things (IoT) applications.
In some cases, these classes of devices represent a very large deployment base, on the order of thousands or even millions of devices network-wide. In 5G slicing case, three typical services offered to these devices are
1. Enhanced Mobile Broadband(eMBB)
2. Ultra-Reliable and Low Lantency Communication (URLLC)
3. Massive Machine Type Communications (mMTC)
These services demand the network performance with wide variety of characteristics such as data rate, latency, loss rate, reliability and many other parameters.
My question is the followings:

1.       Can we use VPN service model to offer such kind of new services to customers?

2.       Should we define new services characteristic that is based on the new slicing capabilities provided by network devices?


Best Regards.

Aijun Wang
Network R&D and Operation Support Department
China Telecom Corporation Limited Beijing Research Institute,Beijing, China.



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

Rispetta l'ambiente. Non stampare questa mail se non è necessario.