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

Jérôme Härri <jerome.haerri@eurecom.fr> Wed, 17 April 2019 13:25 UTC

Return-Path: <jerome.haerri@eurecom.fr>
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 727191200C7 for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 06:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level:
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 42Ktv3QtSBAh for <its@ietfa.amsl.com>; Wed, 17 Apr 2019 06:25:33 -0700 (PDT)
Received: from smtp.eurecom.fr (smtp.eurecom.fr [193.55.113.210]) by ietfa.amsl.com (Postfix) with ESMTP id 54B0E12008D for <its@ietf.org>; Wed, 17 Apr 2019 06:25:32 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.60,362,1549926000"; d="scan'208,217";a="9936787"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago1i.eurecom.fr with ESMTP; 17 Apr 2019 15:25:31 +0200
Received: from xerus29 (unknown [192.168.200.6]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 330613A4C; Wed, 17 Apr 2019 15:25:31 +0200 (CEST)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: Dirk.von-Hugo@telekom.de, alexandre.petrescu@gmail.com, its@ietf.org
References: <abfbf312-be3c-c957-d58e-67b141697a14@gmail.com> <LEXPR01MB06697DF790A19AEBC7E7E4D2D1250@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <LEXPR01MB06697DF790A19AEBC7E7E4D2D1250@LEXPR01MB0669.DEUPRD01.PROD.OUTLOOK.DE>
Date: Wed, 17 Apr 2019 15:25:31 +0200
Organization: EURECOM
Message-ID: <00a401d4f521$07ad70c0$17085240$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01D4F531.CB3AFBB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJ77LBrwb839vTeo9AqYtlEbSGD0QGlz/GYpOU5H7A=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/xrDIHSWXHQsqUwsDxNcAG6SjZAs>
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:25:34 -0000

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)

 

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