IETF Logo Mail Archive

Re: [alto] Introducing costs for wireless networks

Yichen Qian <92yichenqian@tongji.edu.cn> Sun, 12 March 2017 18:41 UTC

Return-Path: <92yichenqian@tongji.edu.cn>
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 2416112949E for <alto@ietfa.amsl.com>; Sun, 12 Mar 2017 11:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 D9X25s3B-yEN for <alto@ietfa.amsl.com>; Sun, 12 Mar 2017 11:41:00 -0700 (PDT)
Received: from tongji.edu.cn (mailusrsvr2.tongji.edu.cn [202.120.164.62]) by ietfa.amsl.com (Postfix) with ESMTP id 6A46D129481 for <alto@ietf.org>; Sun, 12 Mar 2017 11:40:58 -0700 (PDT)
Received: from [180.160.1.141] (unknown [180.160.1.141]) by mailusersvr2 (Coremail) with SMTP id PqR4ygAHZyw1lsVYNmbkAA--.18462S2; Mon, 13 Mar 2017 02:40:53 +0800 (CST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2770495C-C67E-498C-BA05-3CAA7792B02C"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Yichen Qian <92yichenqian@tongji.edu.cn>
In-Reply-To: <A7A5844EB93EB94AB22C2068B10AD65A017F974862@FR711WXCHMBA01.zeu.alcatel-lucent.com>
Date: Mon, 13 Mar 2017 02:40:53 +0800
Message-Id: <52257A43-3338-4905-AEC8-867F52F79CF4@tongji.edu.cn>
References: <A7A5844EB93EB94AB22C2068B10AD65A017F974862@FR711WXCHMBA01.zeu.alcatel-lucent.com>
To: "Randriamasy, Sabine (Nokia - FR)" <sabine.randriamasy@nokia-bell-labs.com>
X-Mailer: Apple Mail (2.3124)
X-CM-TRANSID: PqR4ygAHZyw1lsVYNmbkAA--.18462S2
X-Coremail-Antispam: 1UD129KBjvJXoW7AF1DKryxZrW3Xw4kKFWDXFb_yoW8uFWDpF Za9FsxKr4kGFn5Kws7Xr48Ar10krs5AwnxJr13tr1j9345WFn29F1Sqw45KFyUKr4fGa1U XF4j9r4UW3ZIv3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU9ab7Iv0xC_Zr1lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2 AK021l84ACjcxK6xIIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY6xkF7I0E14v2 6r4UJVWxJr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI 0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k08I80eVW5JVWrJwAqx4xG 64kEw2xG04xIwI0_Gr0_Xr1lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r 1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvY0x0EwIxGrwCjr7xvwVCIw2I0I7xG 6c02F41l42xK82IYc2Ij64vIr41l42xK82IY6x8ErcxFaVAv8VWxJr1UJr1l4I8I3I0E4I kC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWU WwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr 0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWr Zr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_Gr UvcSsGvfC2KfnxnUUI43ZEXa7IU8OVy7UUUUU==
X-CM-SenderInfo: qrqrmmmu6w00xjmlhvlgxou0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/2uDXoWsR17egSGJBvAIUQawPsoY>
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: Sun, 12 Mar 2017 18:41:02 -0000

Hi Sabine,

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?

Thanks,
Yichen


> On Mar 10, 2017, at 9:30 PM, Randriamasy, Sabine (Nokia - FR) <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://www.ietf.org/mailman/listinfo/alto>

v2.23.0 | Report a Bug | By Email