IETF Logo Mail Archive

[tsvwg] <tsvwg> Using NQB in mobile network

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Thu, 05 December 2019 07:13 UTC

Return-Path: <gengxuesong@huawei.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A8E120096 for <tsvwg@ietfa.amsl.com>; Wed, 4 Dec 2019 23:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 2TkmBpvKX0rM for <tsvwg@ietfa.amsl.com>; Wed, 4 Dec 2019 23:13:47 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 623DF120059 for <tsvwg@ietf.org>; Wed, 4 Dec 2019 23:13:47 -0800 (PST)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 2A413BDB0EEBEAA28002 for <tsvwg@ietf.org>; Thu, 5 Dec 2019 07:13:44 +0000 (GMT)
Received: from dggeme707-chm.china.huawei.com (10.1.199.103) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 5 Dec 2019 07:13:43 +0000
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by dggeme707-chm.china.huawei.com (10.1.199.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 5 Dec 2019 15:13:41 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.1713.004; Thu, 5 Dec 2019 15:13:41 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: "g.white@cablelabs.com" <g.white@cablelabs.com>
CC: tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: <tsvwg> Using NQB in mobile network
Thread-Index: AdWrOkUS8qn5HmQvT+m1P+g9Yq/snw==
Date: Thu, 05 Dec 2019 07:13:41 +0000
Message-ID: <1d3ae9e5e17743aca5c96a3ce4d0bbb6@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.169.123]
Content-Type: multipart/alternative; boundary="_000_1d3ae9e5e17743aca5c96a3ce4d0bbb6huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/cs50wvYTS6N-XPJdEqyEVvPfUB0>
Subject: [tsvwg] <tsvwg> Using NQB in mobile network
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2019 07:13:49 -0000

Hi Greg,

Thank you for your work about NQB.
I notice that in section 7.2, you mentioned that "To support the NQB PHB, the mobile network MUST be configured to give UEs a dedicated, low-latency, non-GBR, EPS bearer ...or Data Radio Bear...". I'm a little confused about why NQB is limited to provide service for non-GBR service. I think considering the low latency and congestion avoidance feature of NQB, it is more suitable for delay-critical GBR defined in 3GPP TR23.501, or do you have any other considerations in this point?

Best Regards
Xuesong

v2.23.0 | Report a Bug | By Email