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

Qin Wu <> Wed, 11 October 2017 05:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8BEE813303A; Tue, 10 Oct 2017 22:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.22
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tSfZit_yzZkz; Tue, 10 Oct 2017 22:57:36 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 061D81320C9; Tue, 10 Oct 2017 22:57:33 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DQH64345; Wed, 11 Oct 2017 05:57:32 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 11 Oct 2017 06:57:31 +0100
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Wed, 11 Oct 2017 13:57:27 +0800
From: Qin Wu <>
To: Aijun Wang <>, "" <>, "" <>
Thread-Topic: [L3sm] Using VPN to offer eMBB, URLLC, mMTC service
Thread-Index: AdM5wPeX7QC+PzrKQwKPsvwE16mphAIio84w
Date: Wed, 11 Oct 2017 05:57:27 +0000
Message-ID: <>
References: <008a01d339c0$f9049ed0$eb0ddc70$>
In-Reply-To: <008a01d339c0$f9049ed0$eb0ddc70$>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9ABA8B08nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.59DDB2CC.00AA, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c87f7461fbd5a0ae62c7e11d35d39e9b
Archived-At: <>
Subject: Re: [L2sm] [L3sm] Using VPN to offer eMBB, URLLC, mMTC service
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Oct 2017 05:57:37 -0000

Thank Aijun to raise this interesting question,
I think the L3SM model has defined various customer applications by using identity,
Customer applications that can be offered by VPN include web, mail, p2p, voice, video,etc.
but new application  identities may be added through augmentation.
Yes, eMBB, URLLC, mMTC are new emerging  service that can be offered if 5G slicing want to leverage VPN technology.
But one thing I am not sure is whether service model should be aware of network slicing, to me, I think network slicing is more related to
how the service is delivered, how the resource is allocated/isolated/partitioned.
In many cases, we can take advantage of existing models developed by IETF such as I2RS topology model, TE topology model to understand underlying
Network capacity, capability, resource distribution, and then allocate resource based on customer service requirements provided by service model.

Another problem we have to offer such kind of service is:
What kind of network technology can be used to realize such service?
Yes, we can add new application identity for eMBB, URLLC, mMTC service, but I doubt we should add any other new service characteristic besides
Ones we have already defined under QoS profile in service model.

发件人: L3sm [] 代表 Aijun Wang
发送时间: 2017年9月30日 15:52
主题: [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.