Re: [ipwave] what is C-V2X: PC5 mode 4 'sidelink' without infrastructure, or V2I?

Jérôme Härri <Jerome.Haerri@eurecom.fr> Thu, 28 October 2021 13:56 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 7DC1D3A10BA for <its@ietfa.amsl.com>; Thu, 28 Oct 2021 06:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 doRJC5fzskRp for <its@ietfa.amsl.com>; Thu, 28 Oct 2021 06:56:10 -0700 (PDT)
Received: from smtp.eurecom.fr (smtp.eurecom.fr [193.55.113.210]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8A33A10B8 for <its@ietf.org>; Thu, 28 Oct 2021 06:56:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.87,190,1631570400"; d="scan'208,217";a="4153887"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago1i.eurecom.fr with ESMTP; 28 Oct 2021 15:56:07 +0200
Received: from portege33 (portege33.eurecom.fr [172.17.31.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 54735749; Thu, 28 Oct 2021 15:56:07 +0200 (CEST)
From: Jérôme Härri <Jerome.Haerri@eurecom.fr>
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, 'IPWAVE WG' <its@ietf.org>
References: <b179c0c8-837b-1214-a564-45742385fbf6@gmail.com>
In-Reply-To: <b179c0c8-837b-1214-a564-45742385fbf6@gmail.com>
Date: Thu, 28 Oct 2021 15:56:07 +0200
Organization: EURECOM
Message-ID: <03f801d7cc03$8e2f6d40$aa8e47c0$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03F9_01D7CC14.51BA8730"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQH3VV0Tx1u4xqj50q1qCcNK6vGIEqupWhbw
Content-Language: en
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/ACImyvPQy1uNfv5p9U9usRPdoIo>
Subject: Re: [ipwave] what is C-V2X: PC5 mode 4 'sidelink' without infrastructure, or V2I?
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: Thu, 28 Oct 2021 13:56:16 -0000

Dear Alex,

 

My perception: C-V2X is US terminology and applied initially as LTE V2X rel.14 but now it is used for NR V2X Rel.16 to differentiate from LTE V2X Rel.14 (again, in the US). 

 

My suggestion is: we use the standard names… 3GPP LTE V2X rel.14 or 3GPP NR V2X rel. 16  at least we have a ‘clear’ understanding of what it means and not means (and here, the release numbers are important…as (now wanted to add more confusion), there is a 3GPP LTE V2X rel.15 with a minor modification on the V2X PHY, but which makes it NOT background compatible with 3GPP LTE V2X rel.14…

 

Also, when we refer to 3GPP NR V2X rel.16, we only have one and only one specified scheduler (mode 2(a)) which is more or less the same as the one from LTE V2X rel.14. As far as I know, 3GPP is discussing the other modes (mode 2 (b)(c)(d) in further releases)…and well, any NR V2X rel. 16 mode 1 will not be published and available as we can expect. 

 

Yet, if you want to make it short and generic, we can use LTE V2X and NR V2X, or 5G NR V2X (although the 5G is just for branding in that case).

 

What do you think?


BR,

 

Jérôme

 

From: its <its-bounces@ietf.org> On Behalf Of Alexandre Petrescu
Sent: Thursday, 28 October 2021 15:25
To: IPWAVE WG <its@ietf.org>
Subject: [ipwave] what is C-V2X: PC5 mode 4 'sidelink' without infrastructure, or V2I?

 

A few definitions of C-V2X circulate:

C-V2X is LTE PC5 interface mode 4 'sidelink': it means it works only in a V2V or V2P manner, and thus C-V2X does not need infrastructure.  This has been said a few times.

C-V2X means also V2I.  This is said by e.g. the SIM8100 module description saying "The SIM8100 is a C-V2X module which supports C-V2X functionality through a PC5 interface for vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), and vehicle-toinfrastructure (V2I) applications" at https://www.simcom.com/product/SIM8100.html or "The module will most commonly be found in telematics boxes, telematics control units, advanced driver-assistance systems, C-V2X (V2V, _V2I_, V2P) systems)" at https://www.quectel.com/product/5g-c-v2x-ag55xq-series

What do you think?  Does C-V2X need infrastructure or can C-V2X work without infrastructure?

This is can guide our activity of IPv6 for C-V2X.

Alex