Re: [DMM] MPTCP Proxy for Mobile Networks

Jouni Korhonen <jouni.nospam@gmail.com> Fri, 21 February 2014 08:53 UTC

Return-Path: <jouni.nospam@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 205FF1A0040 for <dmm@ietfa.amsl.com>; Fri, 21 Feb 2014 00:53:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 SrGCqUfmUtcj for <dmm@ietfa.amsl.com>; Fri, 21 Feb 2014 00:53:04 -0800 (PST)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF621A0070 for <dmm@ietf.org>; Fri, 21 Feb 2014 00:53:03 -0800 (PST)
Received: by mail-lb0-f181.google.com with SMTP id z11so2143007lbi.12 for <dmm@ietf.org>; Fri, 21 Feb 2014 00:52:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IcfIsGHZNcwmaY8OraoUry65KFRIkH76N5zhuK2RMOc=; b=rPlJW6Jte2yL1xJSBPD/LVUMHxaMLzloiOXEDG9Wbu6E0PjzzvCSER9fMCowzaqCsp CLi0gaMqUSOI63KzVP77lO46F0+8RrI4pj7YErHz/AiCiGxqBv786LOnAiCewT6BzY5l d3+MxTSacF9rvrF0JeBwduULsnvoaTtjaG9f0L6S5wBEmILtwHvCrVVg4YAeiSJRWmKe fvETZDUkEDg9y5GDS3xH5fbN0w8eUT0tBuvfnp3EV22UGNNqQXxhBIRYf8gxrV+kJ1NO sOY52kMEfj/jayDldOX02WE7aAWhqzahzWO7u8vd1M4Q0LJrogE8h80jcBjxvjHqMv2F Uukg==
X-Received: by 10.112.142.230 with SMTP id rz6mr3562567lbb.0.1392972779483; Fri, 21 Feb 2014 00:52:59 -0800 (PST)
Received: from [192.168.250.222] ([194.100.71.98]) by mx.google.com with ESMTPSA id rt7sm6976174lbb.0.2014.02.21.00.52.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 00:52:57 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <6B53974F43BA3C40A96CA7FDE0C9BBD0410FEE49@nkgeml507-mbs.china.huawei.com>
Date: Fri, 21 Feb 2014 10:52:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <50BE6A8A-2242-468C-964B-B52A77AC3E34@gmail.com>
References: <6B53974F43BA3C40A96CA7FDE0C9BBD0410FEE49@nkgeml507-mbs.china.huawei.com>
To: Xiongchunshan <sam.xiongchunshan@huawei.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/UM9z-FABbwZEDmIc7n5UZIcPHGg
Cc: "dmm@ietf.org" <dmm@ietf.org>
Subject: Re: [DMM] MPTCP Proxy for Mobile Networks
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Feb 2014 08:53:07 -0000

Do you mean draft-deng-mptcp-mobile-network-proxy-00 I-D ?

- Jouni


On Feb 21, 2014, at 9:18 AM, Xiongchunshan (Sam) <sam.xiongchunshan@huawei.com> wrote:

> Hello folks,
>  
> Here I have some comments on this document:
>  
> 1)
> 5.2  Traffic mediation
>    (a) Anchoring of sub-flow traffic: On one hand, it is not always
>    possible for a single GW be sitting on the path of every sub-flow
>    from a MPTCP session, hence explicit traffic anchoring to enable a
>    single point of general control over MPTCP sub-flows should be
>    considered.
>    (b) Mediation of sub-flow traffic: On the other hand, for fine-
>    grained mediation of sub-flow traffic, both static and dynamic
>    selection/offloading/pooling policies should be allowed. For
>    instance, "always prefer Wi-Fi over 3GPP" could be a static policy
>    for bulk data transfer services, while "use 3GPP only for backup
>    unless Wi-Fi is congested" could be a dynamic offloading policy for a
>    un-prioritized VoIP service.
> [xcs]Question for clarification: How does the MPTCP proxy know the binding information between the IP and RAT ?  The mobile node knows which IP is allocated from which RAT, but it is very hard for the MPTCP Proxy in the core network to know these mapping information.
> One possible solution is the PCRF (defined in the 3GPP) to provide these binding information to the MPTCP proxy if the MPTCP proxy performance the traffic mediation or let the mobile to do the traffic mediation.
>  
> Another question is how the rules (e.g. "always prefer Wi-Fi over 3GPP") are provided to the MPTCP Proxy or the mobile ? For the MPTCP proxy, it is again the PCRF; for the mobile , it is the ANDSF ?
>  
>  
> 2)
> 4.2 Resource pooling for reduced expense
>    Due to its low construction and operation expenses, Wi-Fi has been
>    adopted by mobile operators as a complementary RAT for their
>    traditional 3GPP networks. However, different construction and
>    operation expenses of various radio networks result in differences in
>    charging rates/policies for different RATs.
>    For instance, Wi-Fi access may be charged by the access duration,
>    while the 3GPP access may be charged by the consumed data volume.
>    Even if using the same policy, Wi-Fi service is expected to be much
>    cheaper than 3GPP data service.
>    Moreover, different subscription packages may offer various data
>    plans for various RATs. For instance, a basic 4G package may contain
>    free data volume as well free Wi-Fi access too.
>    By enabling MPTCP session between UE and network proxy, via mediating
>    sub-flow data traffic based on their Radio access types and the
>    user’s subscription package, it is possible to further reduce the
>    usage expenses from both sides of the network and user.
>  
> [xcs] it will benefit the user if the user’s expense of data usage is reduced, if the WiFi connection is available and charging fee is very low, maybe all the traffic from the 4G are moved to the WiFi by the MPTCP proxy, and the mobility and QoS of the service maybe aren’t ensured, so it is proposed to adding the following sentence to the end of this chapter:
> The QoS/QoE/Service continuity of the current data services are still kept when the MPTCP proxy is used to reduce the user’s usage expenses.
>  
> A assumption for reducing user expense is that the WiFi connection is activated beforehand, but sometimes the WiFi connection isn’t activated or a wrong WiFi AP is selected by the user( that MPTCP Proxy can’t access the WiFi IP flow), that is, one hand, the network need to control the MPTCP Proxy to mediate the IP flows, another hand, the network should tell the mobile to open which RAT/WiFi to make the MPTCP Proxy work.  i.e. the network should provide some information to the UE , to guide the UE to select and open another RAT to enable the MPTCP.
>  
>  
> 3)
> 4.1 Dynamic traffic offloading based on network information
>    For real-time interactive services with higher QoS requirements it is
>    expected that 3GPP network can provide better guarantees on the
>    average case. For bulk data transfer who is satisfied with best-
>    effort delivery, Wi-Fi would be a great choice. But the vertical
>    partition does not fit everywhere for the wireless condition itself
>    is quite dynamic and hard to predict. It is important to implement
>    adaptive offloading mechanisms in order to achieve higher resource
>    utility with ever changing radio environment for a possibly moving
>    terminal based on network status, e.g. cell load, AP’s signal
>    intensity, user’s subscription type, etc.
> [xcs]The same question from 1):  How does the MPTCP Proxy/UE know the network status ? The PCRF/ANDSF provides these information to the MPTCP Proxy/UE ?
>  
>  
>  
> BRs
> Chunshan Xiong
> Huawei Technologies Co., Ltd.
>  
>  
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm