[6gip] 6G and V2X

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 13 January 2021 09:47 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: 6gip@ietfa.amsl.com
Delivered-To: 6gip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8459B3A0B35 for <6gip@ietfa.amsl.com>; Wed, 13 Jan 2021 01:47:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.668
X-Spam-Level:
X-Spam-Status: No, score=0.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] 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 OGrCbvsfQCoN for <6gip@ietfa.amsl.com>; Wed, 13 Jan 2021 01:47:36 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 D55C53A0B33 for <6gip@ietf.org>; Wed, 13 Jan 2021 01:47:35 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 10D9lYvO029856 for <6gip@ietf.org>; Wed, 13 Jan 2021 10:47:34 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F400B20C23F for <6gip@ietf.org>; Wed, 13 Jan 2021 10:47:33 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id EAAFF20C221 for <6gip@ietf.org>; Wed, 13 Jan 2021 10:47:33 +0100 (CET)
Received: from [10.14.9.243] ([10.14.9.243]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 10D9lXWe024100 for <6gip@ietf.org>; Wed, 13 Jan 2021 10:47:33 +0100
To: "6gip@ietf.org" <6gip@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <ca6b76f8-bd61-2095-6aee-7b1748f80b0e@gmail.com>
Date: Wed, 13 Jan 2021 10:47:33 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/6gip/KPCoPZPQQtPO-PuLdx3FN_sKiRI>
Subject: [6gip] 6G and V2X
X-BeenThere: 6gip@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IP Issues in 6th Generation Mobile Network System \(6gip\)" <6gip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6gip>, <mailto:6gip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6gip/>
List-Post: <mailto:6gip@ietf.org>
List-Help: <mailto:6gip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6gip>, <mailto:6gip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jan 2021 09:47:38 -0000

Hi,

I would like to discuss about V2X in 6G.

There is currently lots of works about V2X in general, such as the
ETSI's CAM messages in Europe and the BSM messages in US (Cooperative
Awareness and Basic Safety Messages).  If I remember correctly, some V2X
messages such as the CAMs are specified in 3GPP documents as well.  In
trial deployments these CAM messages were sent on UDP on IP and on 3G
and on 4G; presumably it will be easy to be put on 5G as well.  The most
recent 5G demo for self-driving automobiles was in Sweden at the
beginning of October of year 2020; it is not clear whether that used V2X
messages, or just 5G.

Are CAM messages link-layer messages in 5G-V2X?

In my oppinion, in the future, there will be no specific 5G-V2X
deployment, no more than 2G, 3G or 4G had anything specific about V2X.
There might be something like specific 5G slices for automobiles, but no
V2X messaging.  It means that the V2X messages will not be at the link
layer in 5G.  This is a speculation of my part, but that is what I think
at this time.  I might be wrong.

This brings me to the reason of why mentioning V2X.

It might be appropriate to specify how are the V2X messages used on 3G
and 4G.  This is to put CAM on UDP on IP.  Maybe BSM would be done the
same.  Maybe then 3GPP could put both CAM Mand BSM in 3GPP specs, not
only CAM as it stands now (IIRC).  This is a great opportunity for
specification that is in relationship with deployments.  Whether 3GPP
accepts to put BSM in 3GPP specs might be a matter of time.  Is it too
late?  Then do it on 6G.  Is BSM already in 3GPP specs?  Then we have a
problem of interop between e.g. an 5G-enabled US car and a server in Europe.

I would like to say that V2X is not all there is to be about automobiles
and 5G.  There are also a number of automobile-related use-cases that
need some specific features from 5G.  E.g. tele-operated driving is one
such use-case, and we could work on others.  These use-cases require the
bandwidth/latency of 5G but that might not be enough.  New use-cases
related to automobiles might take more advantage of higher bandwidths
and even lower latencies at 6G.

Finally, allow me to make a speculation about spectrum use on cellular
networks.  A year ago there was a public consultation of FCC considering
to take spectrum from the 5.9Ghz space that is typically allocated to
non-cellular technologies like DSRC.  It seems to me that consultation
has not reached a decision.  I do not know.  It might be that there will
be no spectrum at 5.9GHz for cellular technologies and that 5.9GHz will
stay for WiFi-like technos (802.11-OCB, .11bd, etc).  If things at
5.9Ghz stay the way they are now, then this would be even more support
for considering that V2X in 5G will not be anything like CAM as a 5G
link layer message, so again, V2X will be more like UDP on IP.  It might
be that 5G does not accept that.

Alex