Re: [ipwave] SATCOM for cars

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 02 June 2020 14:39 UTC

Return-Path: <Fred.L.Templin@boeing.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 38BE33A0824 for <its@ietfa.amsl.com>; Tue, 2 Jun 2020 07:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com
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 nPyXj05o7lkW for <its@ietfa.amsl.com>; Tue, 2 Jun 2020 07:39:15 -0700 (PDT)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 671B13A0816 for <its@ietf.org>; Tue, 2 Jun 2020 07:39:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 052EdBJG025936; Tue, 2 Jun 2020 10:39:13 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1591108753; bh=IJrvXbZpCprWDwCaiM+Yz9HtgrhARdkhyErGUg1YLVw=; h=From:To:Subject:Date:From; b=ptC4pskRJ0hv/PVTNKL46qA70cDZIE6Vrt7qURmwTv7yfOAWXmv1NIdEDhUljo83E BiHQFVw7l/I8tuVrqUhNfFA8U7bj+FCKDv9S6D4t8KUC0bwMxaumrIlQimccOPca67 ujbz2uJ5wWuJaI2d87J+x1eu51or5pbuQffjSf/rR5aW+lbkIX1Rh5rHx0xi9ZpINw kPHsjz2z2e7y8M6vkQKDqWi8lrJcakOMMlEaWMoEJAXU0vEoykfW6MIspVQ9OQkcn2 Jju4aoWuWPFoy3aNSbYylXT+MFJVxhg5qGtE1yuLINQsYMsr3bRE/FSjolcoozDe24 r0qMAIZNNIUyA==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 052Ed2SG025453 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 2 Jun 2020 10:39:02 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1979.3; Tue, 2 Jun 2020 07:39:01 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1979.003; Tue, 2 Jun 2020 07:39:01 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "its@ietf.org" <its@ietf.org>
Thread-Topic: [ipwave] SATCOM for cars
Thread-Index: AdY46mKts7MTHx0PQxeOL53GdO6Lxg==
Date: Tue, 02 Jun 2020 14:39:01 +0000
Message-ID: <3ec38c37bee44aebbc2e0eb7fa17da38@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 208D876B678F5109657C0D8C83749A1DABCF4039881FD8910CEEF20D3B2C81B02000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/r3GTCI1NhwjdM2c3VEbFsJLPER8>
Subject: Re: [ipwave] SATCOM for cars
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: Tue, 02 Jun 2020 14:39:17 -0000

Hi Alex, you mentioned about the logistics and clutter associated with putting
up satellite constellations and I think you are right in general but both Starlink
and Iridium Next have launched and their satellites are on-station in orbit. So,
maybe we already have all we need?

I do recall now however that my Toyota did in fact come with a satellite
receiver that I keep getting  service activation offers for. I used it during the
free trial period and found that it did not work well in the mountainous
region I live in so I never purchased the service plan. But, with Starlink
and Iridium providing a low-orbit, many-satellite constellation maybe the
service would be better. I think it is possible that cars might want to try
to tap into such a service.

Thanks - Fred

> -----Original Message-----
> From: its [mailto:its-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Tuesday, June 02, 2020 5:39 AM
> To: its@ietf.org
> Subject: [EXTERNAL] Re: [ipwave] SATCOM for cars
> 
> 
> Le 02/06/2020 à 01:27, Templin (US), Fred L a écrit :
> > Hi, I got interested in whether cars will in the future include
> > SATCOM access technologies the way airplanes do and came across
> > this:
> >
> > https://www.youtube.com/watch?v=_oNgGOL6Yto
> >
> > The clip is an interview of Elon Musk and asks for his assessment as
> >  to whether future Teslas will come equipped with Starlink gear. If
> > you listen to the clip, Elon Musk seems to be saying "not now, but
> > possibly feasible in the future" whereas the narrator seemed to
> > articulate a more negative viewpoint.
> >
> > But, thinking about it, a SATCOM service in cars would offer a true
> > multilink capability when coupled with 5G, OCB, etc. And, it would
> > provide service continuity outside of metropolitan areas. Lots of
> > considerations to think about - antenna and base station size, power,
> > cost, etc. - but I think would pass the mythbusters plausibility
> > test. Will we see cars with SATCOM in the not-too-distant future?
> 
> It's a very good question.
> 
> I agree a multilink data capability to the automobile is an essential
> tool, going beyond the 5G vs G5 (OCB) competitions.
> 
> Satellite-like Digital Audio Broadcast is rolling out in high end
> automobiles recently, and probably that is just a premise to satellite.
> 
> You mention Tesla, but earlier I heard also Toyota also considering
> their own mini satellite constellation for their cars.  Some specific
> car antennas were mentioned like Kymeta, which are small, without moving
> parts.
> 
>  From the infrastructure perspective, of course, there is the question of
> putting and operating many satellites up there.  But more down to earth
> there are questions of equipping tunnels with GPS (and other
> satellite-issued) signal relayers, for more coverage.
> 
> Satellite to the car might also be an issue of cost.  If Tesla avoids
> substituting lidars for radars in the car because of cost, it's natural
> to imagine one would avoid putting satellite receivers because of same
> reason (not the cost of receiver, but the cost of satellite up there).
> One does not want to produce a fully and permanently connected
> automobile that is too expensive to buy for the middle class in a new
> G-X country (G7, G20, G-whatever).
> 
> Finally, but an equally important point: satellite constellations might
> make many automobiles happy but might make other people unhappy, like
> deep space observers, debris worriers, and more.  All these are very
> much inter-related.
> 
> Alex
> 
> >
> > Fred
> >
> > _______________________________________________ its mailing list
> > its@ietf.org https://www.ietf.org/mailman/listinfo/its
> >
> 
> _______________________________________________
> its mailing list
> its@ietf.org
> https://www.ietf.org/mailman/listinfo/its