[alto] Introducing costs for wireless networks

"Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com> Fri, 10 March 2017 13:30 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 EF7BB12956F for <alto@ietfa.amsl.com>; Fri, 10 Mar 2017 05:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 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] 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 gmNizbNBb2JY for <alto@ietfa.amsl.com>; Fri, 10 Mar 2017 05:30:12 -0800 (PST)
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 EB7C412959F for <alto@ietf.org>; Fri, 10 Mar 2017 05:30:11 -0800 (PST)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id E0D25B7517DF2 for <alto@ietf.org>; Fri, 10 Mar 2017 13:30:06 +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 v2ADU9g7002134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Fri, 10 Mar 2017 14:30:09 +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 v2ADU8pa020790 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <alto@ietf.org>; Fri, 10 Mar 2017 13:30:08 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; Fri, 10 Mar 2017 14:30:07 +0100
From: "Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com>
To: IETF ALTO <alto@ietf.org>
Thread-Topic: Introducing costs for wireless networks
Thread-Index: AdKZojiEUqpNUxTCQp64Vr71m8gmug==
Date: Fri, 10 Mar 2017 13:30:07 +0000
Message-ID: <A7A5844EB93EB94AB22C2068B10AD65A017F974862@FR711WXCHMBA01.zeu.alcatel-lucent.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.39]
Content-Type: multipart/alternative; boundary="_000_A7A5844EB93EB94AB22C2068B10AD65A017F974862FR711WXCHMBA0_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/2wYcyemzsT2qxYJLcX0MT4bK7nE>
Subject: [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: Fri, 10 Mar 2017 13:30:15 -0000

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.