Re: [alto] Introducing costs for wireless networks

"Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com> Mon, 13 March 2017 15:11 UTC

Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 089691296F7 for <alto@ietfa.amsl.com>; Mon, 13 Mar 2017 08:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 iRWbAf6V5k8C for <alto@ietfa.amsl.com>; Mon, 13 Mar 2017 08:11:43 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 0CB5A1296D8 for <alto@ietf.org>; Mon, 13 Mar 2017 08:11:43 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 6E7574FB60641; Mon, 13 Mar 2017 15:11:38 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id v2DFBdYv003178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Mar 2017 16:11:40 +0100
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id v2DFBYAc026512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Mar 2017 15:11:38 GMT
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.59]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0301.000; Mon, 13 Mar 2017 16:11:34 +0100
From: "Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com>
To: Qin Wu <bill.wu@huawei.com>, IETF ALTO <alto@ietf.org>
Thread-Topic: Introducing costs for wireless networks
Thread-Index: AdKZojiEUqpNUxTCQp64Vr71m8gmugCJRQnQABCWy9A=
Date: Mon, 13 Mar 2017 15:11:34 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A017F974EB1@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <A7A5844EB93EB94AB22C2068B10AD65A017F974862@FR711WXCHMBA01.zeu.alcatel-lucent.com> <B8F9A780D330094D99AF023C5877DABA9A797697@nkgeml513-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9A797697@nkgeml513-mbs.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_A7A5844EB93EB94AB22C2068B10AD65A017F974EB1FR711WXCHMBA0_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ucJBM0dWx6CsOm-_iCIaRMdDnNY>
Subject: Re: [alto] Introducing costs for wireless networks
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2017 15:11:46 -0000

Hi Qin,

Thanks for your answer, please see inline,
Sabine


From: Qin Wu [mailto:bill.wu@huawei.com]
Sent: lundi 13 mars 2017 08:07
To: Randriamasy, Sabine (Nokia - FR) <sabine.randriamasy@nokia-bell-labs.com>; IETF ALTO <alto@ietf.org>
Subject: RE: Introducing costs for wireless networks

Hi, Sabine:
Interesting topic, I think if this Cellular connection cost is needed? It should go to ALTO performance metric draft, right?
[SR     ] Yes, this would be a preferred placeholder.
I also believe Cost value context is very valuable since it allows expose several value for a single metric. But this cost value context is technology specific?
[SR     ] Indeed, the utilized cost value context parameter is specific to the context in which the cost value is used. For instance:  “uda”, “udna” is specific to LTE networks; “uplink”, “downlink” may apply to different technologies such as cellular, wifi and fixed.
Or you want to have a generic schme for cost value context?
[SR     ] yes, a generic scheme is specified in [draft-randriamasy-alto-cost-context] to use context parameters in conjunction with costs. This scheme applies to any technology that would need it. The current draft proposes use cases for wireless networks but is not restricted to.  Other use cases are more than welcome.
In addition, I want to know whether Celluar costs is used to measure cell congestion or cell load?
[SR     ] there can be several metrics for cellular networks, including cell congestion, cell load and others. Again any proposal is welcome.
How do you measure it in the wireless networks? Is there any 3GPP specification we can reference?
[SR     ] it depends on the metrics. The metric values may be inferred from aggregated measurements but not only. They may also involve non-measured ingredients reflecting e.g. policy, may be unitless or not.

-Qin
发件人: alto [mailto:alto-bounces@ietf.org] 代表 Randriamasy, Sabine (Nokia - FR)
发送时间: 2017年3月10日 21:30
收件人: IETF ALTO
主题: [alto] Introducing costs for wireless networks

Hi all,

Any thoughts in the WG on the following?
Thanks,
Sabine

Pursuant to previous ALTO work on wireless networks and relating to the WG item on ALTO metrics, there are a number of abstracted metrics reporting on cellular and wireless networks worth considering. For instance, applications on UEs may like to know about the connection costs associated to the cells it is likely to connect to. These costs may for instance be impacted by the cell load, see section 2.1 of [draft-randriamasy-alto-cost-context].

Using cellular costs requires introducing a new address type and a new identifier namespace for cells. Based on 3GPP standards, we may opt for the name space "ECGI" and the related address format as suggested in section 4 of [draft-rauschenbach-alto-wireless-access] that also proposes that to map cells to PIDs covering cell IDs.

Cellular connection costs (CCC for short) can be conveyed by for instance the (Filtered) Cost Map (FCM) service or an extension of the Endpoint Property (EPS) that could be added to [draft-roome-alto-unified-props].

A PID in a Network Map can cover a cell with an address from the address space "ECGI". A PID thus hides the underlying technical aspects. The CCC in a F/CM between a UE and a cell/PID can be encoded in the bi-directional, uplink and downlink directions, within or across PIDs.  A UE can retrieve its “serving PID” via the Endpoint Property "PID" applied to its service cell ID.