Re: [ipwave] LTE-V2X term in Problem Statement document

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 17 April 2019 13:29 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 703031200DF for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 06:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 yLel56xJUXPH for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 06:29:11 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 D7E3012008D for <its@ietf.org>; Wed, 17 Apr 2019 06:29:10 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3HDT8jO010074; Wed, 17 Apr 2019 15:29:08 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 45F28205D5F; Wed, 17 Apr 2019 15:29:08 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 34FCA205CC3; Wed, 17 Apr 2019 15:29:08 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3HDT8U3009547; Wed, 17 Apr 2019 15:29:08 +0200
To: Jérôme Härri <jerome.haerri@eurecom.fr>, Dirk.von-Hugo@telekom.de, its@ietf.org
References: <abfbf312-be3c-c957-d58e-67b141697a14@gmail.com> <LEXPR01MB06697DF790A19AEBC7E7E4D2D1250@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE> <00a401d4f521$07ad70c0$17085240$@eurecom.fr>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <216fe514-ff89-5ef5-a24e-199196ba1752@gmail.com>
Date: Wed, 17 Apr 2019 15:29:07 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <00a401d4f521$07ad70c0$17085240$@eurecom.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/bWuNl1ZKYO7GTFqZQPd_MkOLz90>
Subject: Re: [ipwave] LTE-V2X term in Problem Statement document
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2019 13:29:13 -0000


Le 17/04/2019 à 15:25, Jérôme Härri a écrit :
> Dear Dirk,
> 
> Thanks. I guess we replied with similar thoughts. Now, on your 
> definition, I would also avoid using this:
> 
> LTE-V2X: the transmission of ETSI CAM and DENM messages over IP over a 
> cellular link such as 3GPP 4G – both via base station and directly 
> between vehicles
> 
> JHNOTE: we should not link CAM/DENM on LTE-V2X…these are layered 
> aspect…LTE-V2X can take whatever comes from higher layers, as long as it 
> is packet-based (no streams) and (most likely) periodical (from the 
> semi-persistent scheduling of the LTE Slidelink V2X scheduler), even if 
> this last point can be discussed.
> 
> C-V2X: the transmission of ETSI CAM and DENM messages over IP over a 
> cellular link such as 3G, 4G and successors – both in infrastructure 
> mode (via base station / Uu interface) and ad-hoc mode (direct link / 
> sidelink interface) if available [since sidelink is only specified for 
> 4G/5G]
> 
> JHNOTE: I think we should not use C-V2X, as the denomination ‘C’ is for 
> ‘Cellular’, which might not be fully the case (e.g. LTE Prose mode 4, 
> a.k.a V2X)

Is C-V2X term already defined by Qualcomm?  Or by another SDO?

Alex

> 
> Best Regards,
> 
> Jérôme
> 
> *From:*its [mailto:its-bounces@ietf.org] *On Behalf Of 
> *Dirk.von-Hugo@telekom.de
> *Sent:* Wednesday 17 April 2019 14:32
> *To:* alexandre.petrescu@gmail.com; its@ietf.org
> *Subject:* Re: [ipwave] LTE-V2X term in Problem Statement document
> 
> Hi Alex,
> 
> I strongly agree with you that we need a precise definition on what we 
> mean with cellular V2X (often denoted as C-V2X in general – so covering 
> LTE and 5G/NR) – especially since – as you correctly pointed out - 3GPP 
> has none such official definition as LTE-V2X or NR-V2X .
> 
> However when defining LTE-V2X we should be aware that there are two 
> different modes of operation for V2X communication in 3GPP cellular 
> systems (as also described in Annex A.5 of PS document 
> https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-08).
> 
> E.g. according to 3GPP TR 21.914 giving a Release 14 (i.e. LTE) 
> Description and Summary of Rel-14 Work Items, but similarly also for 
> 5G/NR or Rel. 15 and higher (here in still draft TR 21.915) the modes of 
> operation are described as
> 
> -Direct V2X communication between UEs over a 3GPP sidelink (PC5 interface)
> 
> -V2X communication over LTE-Uu interface (i.e. via base stations / eNBs)
> 
> In addition there are 2 different modes for PC5/sidelink:
> 
> -in coverage of cellular system with LTE assistance
> 
> -out of coverage: ad-hoc mode w/o assistance … very similar to OCB.
> 
> So I would recommend to specify more exactly what we have in mind.
> 
> LTE-V2X: the transmission of ETSI CAM and DENM messages over IP over a 
> cellular link such as 3GPP 4G – both via base station and directly 
> between vehicles
> 
> Or more general:
> 
> C-V2X: the transmission of ETSI CAM and DENM messages over IP over a 
> cellular link such as 3G, 4G and successors – both in infrastructure 
> mode (via base station / Uu interface) and ad-hoc mode (direct link / 
> sidelink interface) if available [since sidelink is only specified for 
> 4G/5G]
> 
> Or one may even reflect differentiation between those modes in the 
> acronym (which I would not recommend here being not in scope for this 
> document)
> 
> Just my 2 cents
> 
> Kind regards
> 
> Dirk
> 
> *From:*its <its-bounces@ietf.org> *On Behalf Of *Alexandre Petrescu
> *Sent:* Mittwoch, 17. April 2019 13:18
> *To:* its@ietf.org
> *Subject:* [ipwave] LTE-V2X term in Problem Statement document
> 
> Hi IPWAVErs,
> 
> The IPWAVE Problem Statement document uses the term 'LTE-V2X' at one 
> point. ("e.g., IEEE 802.11-OCB and LTE-V2X")
> 
> I would like to suggest to make a careful definition of the term 'LTE-V2X'.
> 
> One would expect the term 'LTE-V2X' to be defined precisely at 3GPP or 
> similar.  But that is not the case.  The 3GPP document that is closest 
> to this term is RP-161298, publicly available, defines the term 
> 'LTE_V2X' (remark underscore '_', instead of dash '-').
> 
> I suggest the addition of the following term in the Problem Statement draft:
> 
> LTE-V2X: the transmission of ETSI CAM and DENM messages over IP over a 
> cellular link such as 3G, 4G and successors.
> 
> Alex
>