Re: [alto] Introducing costs for wireless networks

"Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com> Mon, 13 March 2017 14:53 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 8C9F31295EB for <alto@ietfa.amsl.com>; Mon, 13 Mar 2017 07:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.911
X-Spam-Level:
X-Spam-Status: No, score=-4.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, 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 dGA_GZN0JDdh for <alto@ietfa.amsl.com>; Mon, 13 Mar 2017 07:53:53 -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 CC338129517 for <alto@ietf.org>; Mon, 13 Mar 2017 07:53:52 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id 6FB8BFAA136C1; Mon, 13 Mar 2017 14:53:47 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id v2DErmTC010990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Mar 2017 15:53:49 +0100
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id v2DErSi0026523 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 13 Mar 2017 14:53:46 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 15:53:33 +0100
From: "Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com>
To: "Li, Geng" <geng.li@yale.edu>, "Y. Richard Yang" <yry@cs.yale.edu>, Yichen Qian <92yichenqian@tongji.edu.cn>
Thread-Topic: [alto] Introducing costs for wireless networks
Thread-Index: AdKZojiEUqpNUxTCQp64Vr71m8gmugBtZM+AABJU+IAABoioAAAR3u3Q
Date: Mon, 13 Mar 2017 14:53:33 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A017F974E89@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <A7A5844EB93EB94AB22C2068B10AD65A017F974862@FR711WXCHMBA01.zeu.alcatel-lucent.com> <52257A43-3338-4905-AEC8-867F52F79CF4@tongji.edu.cn>, <CANUuoLpiDTumSAktQigXHfRKrufYHpDpOEJdGeM2bqt2MuYjDg@mail.gmail.com> <SN2PR0801MB2253261A8AABEFC208D7385491250@SN2PR0801MB2253.namprd08.prod.outlook.com>
In-Reply-To: <SN2PR0801MB2253261A8AABEFC208D7385491250@SN2PR0801MB2253.namprd08.prod.outlook.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_A7A5844EB93EB94AB22C2068B10AD65A017F974E89FR711WXCHMBA0_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/0unxwdT_S1OW_mzchy6YunYA4AU>
Cc: IETF ALTO <alto@ietf.org>
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 14:53:55 -0000

Hi Yichen, Richard and Geng,

Thanks a lot for your responses. Please see my answer to your respective e-mails inline,

Thanks,
Sabine


From: Li, Geng [mailto:geng.li@yale.edu]
Sent: lundi 13 mars 2017 07:33
To: Y. Richard Yang <yry@cs.yale.edu>
Cc: Randriamasy, Sabine (Nokia - FR) sabine.randriamasy@nokia-bell-labs.com<mailto:sabine.randriamasy@nokia-bell-labs.com>
Subject: Re: [alto] Introducing costs for wireless networks


Hi Sabine,

[SR     ] Hi Geng,



I'm a new postdoc working with Prof. Yang, and I was majored in wireless communication, LTE mostly, during my PhD career. I quite like your idea, and it happens to be related to my last research interest - user association problem, which needs jointly considering both the radio link quality and load balancing among different stations, especially in the heterogeneous network, where different cells are overlapping and have different capacity.



Your idea of the connection cost is even better for reasons.

1) The value of cost can not only reflect the load condition, and it can be a combination of many other issues, like backhaul, number of hops...

[SR     ] Indeed, ALTO Cost metrics for cellular networks may abstract several and composite considerations

2) Corresponding to "cost", a UE can have the connection "payoff", which is a good abstraction for QoS-related stuff or the term of fairness for users.

[SR     ] Agree,

3) Many fancy tools can help about the optimization, like game theory, economics theory...



The main concern from me is about the quantization of this cost. It should be about both the absolute and relative cost of the connection. The coordination between cells to calculate a uniform value of cost is quite a challenge. Of course, the X2 interface can be used, but we still need to explain what information is needed and how to carry the information properly between cells.

[SR     ] ALTO metrics are meant to convey performances or costs derived from various measurements and they may possibly involve non-measured quantities related to e.g. QoS policy as you mentioned. The important point is to specify what cost and/or performance they report on and how the ALTO Client should interpret and use these values. Information on how ALTO metrics values are inferred should be provided whenever possible.

Defining and incrementing the set of supported  ALTO wireless metrics will be a next step upon WG proposals

But anyway, your idea totally makes sense to me.

[SR     ] looking forward to your ideas.



Best, Geng

[SR     ] best regards,

Sabine







________________________________
From: yang.r.yang@gmail.com<mailto:yang.r.yang@gmail.com> <yang.r.yang@gmail.com<mailto:yang.r.yang@gmail.com>> on behalf of Y. Richard Yang <yry@cs.yale.edu<mailto:yry@cs.yale.edu>>
Sent: Sunday, March 12, 2017 8:25:47 PM
To: Yichen Qian; Li, Geng
Cc: Randriamasy, Sabine (Nokia - FR); IETF ALTO
Subject: Re: [alto] Introducing costs for wireless networks

Sabine,
[SR     ] Hi Richard,

Very interesting direction. As wireless is already a main and future direction of settings of networking access, it makes sense to better support the settings.

Adding support, for example, a new address space, makes sense.

One issue to elaborate more is use cases. A first use case coming to mind is access network selection. Do we do the design in an existing network setting (LTE), or target a more emerging network (e.g., in the context of 5G)?
[SR     ] I'd say both. They are already useful for LTE network and definitely, 5G networks will require additional work.  As for use cases, two are proposed in draft-randriamasy-alto-cost-context for which I will post an update in the next hours.


We have quite some wireless expertise from some members in the group, at least from the past. It will be interesting to hear their feedback.
[SR     ] I am definitely looking forward to having their feedback.

Richard
[SR     ] thanks,
Sabine



On Sun, Mar 12, 2017 at 2:40 PM, Yichen Qian <92yichenqian@tongji.edu.cn<mailto:92yichenqian@tongji.edu.cn>> wrote:
Hi Sabine,
[SR     ] Hi Yichen,

It is interesting to have such extensions to wireless network. I think wireless network is not so stable as wired network. Many factors can influence the cost between a UE and a connection node (such as channels). So it may be difficult to get the accurate cost. Also a UE may have a lot of moments in wireless network which makes it more difficult to get the accurate cost. Is there some ways to solve the problem?
[SR     ] I make a very good point here. Cost and user dynamics are much higher in wireless networks. The cellular ALTO metrics are not meant to convey real time information but will cover periods of, say couple of minutes or couple of tens of seconds.  They are meant to guide applications that either make delay tolerant decisions or involve non real time information in their decisions. Besides ALTO thus avoids causing traffic oscillations. To cope with frequent updates, an ALTO Server may either cover a very local network area and/or provide in one response a Calendar of different time-dependent cost values.

Thanks,
Yichen
[SR     ] thanks, Sabine



On Mar 10, 2017, at 9:30 PM, Randriamasy, Sabine (Nokia - FR) <sabine.randriamasy@nokia-bell-labs.com<mailto:sabine.randriamasy@nokia-bell-labs.com>> wrote:

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.

_______________________________________________
alto mailing list
alto@ietf.org<mailto:alto@ietf.org>
https://www.ietf.org/mailman/listinfo/alto<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_alto&d=DwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=ZKBxqyaKJSFY02EayfSIJqlr2JdBP9wTGW2rF4ftCFM&m=7LZiFJkWcpA8f9wAESQFdF5_f7dnVFBieZW8tzPIJgY&s=SDy9anNl9PT84kKjIgp3-s3r7-sx8VhbTcL00h4kmRg&e=>


_______________________________________________
alto mailing list
alto@ietf.org<mailto:alto@ietf.org>
https://www.ietf.org/mailman/listinfo/alto<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_alto&d=DwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=ZKBxqyaKJSFY02EayfSIJqlr2JdBP9wTGW2rF4ftCFM&m=7LZiFJkWcpA8f9wAESQFdF5_f7dnVFBieZW8tzPIJgY&s=SDy9anNl9PT84kKjIgp3-s3r7-sx8VhbTcL00h4kmRg&e=>



--
--
 =====================================
| Y. Richard Yang <yry@cs.yale.edu<mailto:yry@cs.yale.edu>>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================