Re: [ipwave] 5G deployment status

<Dirk.von-Hugo@telekom.de> Thu, 17 October 2019 08:36 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
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 CE31112004E for <its@ietfa.amsl.com>; Thu, 17 Oct 2019 01:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.297
X-Spam-Level:
X-Spam-Status: No, score=-4.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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=telekom.de
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 dSIL8o2b34RQ for <its@ietfa.amsl.com>; Thu, 17 Oct 2019 01:36:36 -0700 (PDT)
Received: from mailout11.telekom.de (mailout11.telekom.de [194.25.225.207]) (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 B5D80120115 for <its@ietf.org>; Thu, 17 Oct 2019 01:36:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1571301377; x=1602837377; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KIx+UiJYSi1vLBduC8ByH7xy6ZFBLRFu0kB7niHOGHw=; b=8BdVeb2MZCZhaihiZ1av2+WYTy6zKPthoXMQvhXNNe8OrTF2Wp4giB+T Ir82IimblMADplrfrKbpmmjySCeo2AdlRvLh4c39XO9mdL0S+AEax4+f2 yCdzj4e3aCKM7IB8ePRc6txjR+3hIExCDtsslpwd1gwO4FWz+HMFVuaI5 3P9n/6vOKz21LFao9oLh9SVVKee4blcm/IGSFzLfUkgWiS0vjJhUNfC8f sdc5OpujFlQA9HdnFUY/L8xHr4t8BJ3D0GmK5cQQH7rXV+SytjgdU+8nE 4qtOIRmwUMkFLfUlU5rOjpRW/bSJaVppFQ0Tt8kswhKlZDryXJKmomBKs A==;
Received: from qde8e4.de.t-internal.com ([10.171.255.33]) by MAILOUT11.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Oct 2019 10:36:14 +0200
IronPort-SDR: PvBq+rBghldZnf1oo42xdgY9bDxGt1YBlBoH6VIbfut0TWcKnwwQzWZ2zGoSJb+e7PrUr0wpe5 NvF1UvhZT5eHjTVfw78WNhj5bBRiHQKKk=
X-IronPort-AV: E=Sophos;i="5.67,307,1566856800"; d="scan'208,217";a="650978722"
X-MGA-submission: MDG71onew7Vz4ydVIBc/Oa/lJoOCio5X+9jM9lrCwjNQMPHZpZ/VaVp40azKMO1KWWBKoP/tZwrvSrq+6+oq7tGe/bWOx+LV4dAXHrLCrWwlnO0wVXiRXhNrG0wwaqOvLQszUVYoZBEWeszEvAnp4DH5WhUmWgHapWEIvVN8cY47oQ==
Received: from he105712.emea1.cds.t-internal.com ([10.169.118.43]) by QDE8PP.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 17 Oct 2019 10:36:30 +0200
Received: from HE105715.EMEA1.cds.t-internal.com (10.169.118.51) by HE105712.emea1.cds.t-internal.com (10.169.118.43) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 17 Oct 2019 10:36:30 +0200
Received: from HE104160.emea1.cds.t-internal.com (10.171.40.36) by HE105715.EMEA1.cds.t-internal.com (10.169.118.51) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 17 Oct 2019 10:36:30 +0200
Received: from GER01-FRA-obe.outbound.protection.outlook.de (51.4.80.23) by O365mail03.telekom.de (172.30.0.232) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 17 Oct 2019 10:36:27 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ewrkOEHVjUQ+RGb5a4o3yT3k+DvDEUKoEEWsX9F4q1ccd5bmFEyXL2KQhHCdpF7OJ6fD9KXOAVn6lFe7T26opVvww9QrBhx6BoJRd/mdjdgjyfHaO38ZrIBKm0TchXlmkTHl3yS7o0XxdhZVb+SlOEUr1AGxznMX4XPFS0cjhI1yGndzDNH4/UopXwz8VXjsfYYcaRG4z962+4llzABsAcHynsjRetMwymhBz9hvJvObB9vU4o3u7pYFf+LaToflgEofOdAaerI6xBTeK9XeFnP99k/CnabI5cVlg+PO00nAirxeM49qLivFeEi1IFh+x+JR4c4dgKRND4VhN3GChQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KIx+UiJYSi1vLBduC8ByH7xy6ZFBLRFu0kB7niHOGHw=; b=gJrNiDpS+NM8xreQFw4N9l8ZfRGP2mlqmyxWXWedWGlT3qc3gRy+Anonm4IZcuIWCQ15XUAZeg73r33fPiSNqbL2zpjmLY66Uolup4JXwdxalhmi/D8ppwOM7UAG4kiO6g32GmRtfMPDFoWTfncMy30Y3ofKfYr9FlKbg+CcIdVtBvgI5dFMLsd0njLo+0SPcrIdbmi2HhqFAzK7qN6YtjKcBHo4R/6ZgbjlJti439AKZkeY/jkITTm88mF4NRhx+XYqVKZSBIBe3GCr5l6hmU3iF13OcagC68xetunpgRdpleTQjM285xRDR5rG6gc6jrTgcsVEVrMz5KHi3dhPFA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from LEXPR01MB1246.DEUPRD01.PROD.OUTLOOK.DE (10.158.162.154) by LEXPR01MB0927.DEUPRD01.PROD.OUTLOOK.DE (10.158.168.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.22; Thu, 17 Oct 2019 08:36:29 +0000
Received: from LEXPR01MB1246.DEUPRD01.PROD.OUTLOOK.DE ([fe80::303c:2e60:563f:d8f]) by LEXPR01MB1246.DEUPRD01.PROD.OUTLOOK.DE ([fe80::303c:2e60:563f:d8f%4]) with mapi id 15.20.2347.023; Thu, 17 Oct 2019 08:36:29 +0000
From: Dirk.von-Hugo@telekom.de
To: jaehoon.paul@gmail.com, alexandre.petrescu@gmail.com
CC: skku_iotlab_seminar@googlegroups.com, its@ietf.org
Thread-Topic: [ipwave] 5G deployment status
Thread-Index: AQHVdGj7BMyNYjGrXUClhaSY6oEJTKc+CZ4AgCCYHeA=
Date: Thu, 17 Oct 2019 08:36:29 +0000
Message-ID: <LEXPR01MB12462990E23CB5916B16E082D16D0@LEXPR01MB1246.DEUPRD01.PROD.OUTLOOK.DE>
References: <156862357770.28196.6343819812576579929@ietfa.amsl.com> <d6358cfd-9c8f-3c27-28a5-d7ae20280ec8@joelhalpern.com> <EE82B5CD-B2AC-4590-9F6C-8543E30A68FF@gmail.com> <B452A31E-150E-4AE4-A693-A18AA630AB87@cisco.com> <109358A7-6F14-44DF-9113-3F36DE2194B5@getnexar.com> <BN6PR22MB00364FB9221E42BB7862C424DE890@BN6PR22MB0036.namprd22.prod.outlook.com> <d41c82441d50469ba13955af54fe6577@NALASEXR01H.na.qualcomm.com> <A175A6F452C44636ACCAEEC48CF8B1A7@SRA6> <3EAFD2B8-5FA0-475C-B436-A6ACFB32EED5@getnexar.com> <f1976b08-9fbb-6237-c7a4-fb0b84f636df@gmail.com> <3519a3de-d1b9-9651-6f9f-1baf2a93e3e3@gmail.com> <CAPK2Deyqvy51sY+_+hb8DJgvsSYwubg-TOE9GbLRSKqNLnV_tA@mail.gmail.com>
In-Reply-To: <CAPK2Deyqvy51sY+_+hb8DJgvsSYwubg-TOE9GbLRSKqNLnV_tA@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Dirk.von-Hugo@telekom.de;
x-originating-ip: [212.201.104.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6fb35d66-8883-4aae-1353-08d752dd1b75
x-ms-traffictypediagnostic: LEXPR01MB0927:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <LEXPR01MB092726047E1D9D0143E1F46DD16D0@LEXPR01MB0927.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:5797;
x-forefront-prvs: 01930B2BA8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(346002)(136003)(396003)(39860400002)(53754006)(189003)(199004)(102836004)(229853002)(478600001)(790700001)(6246003)(3846002)(6116002)(486006)(53546011)(4326008)(66556008)(8676002)(86362001)(66446008)(66476007)(64756008)(606006)(66066001)(14454004)(413944005)(966005)(66574012)(325944009)(7736002)(316002)(5660300002)(54906003)(476003)(55016002)(6306002)(54896002)(110136005)(81166006)(15188155005)(236005)(7696005)(9686003)(2906002)(81156014)(186003)(16799955002)(11346002)(26005)(66946007)(256004)(14444005)(8936002)(76176011)(76116006)(33656002)(71200400001)(71190400001)(446003); DIR:OUT; SFP:1101; SCL:1; SRVR:LEXPR01MB0927; H:LEXPR01MB1246.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: UiTOg/dYWB1RKMQr7j3OrUhJhPpFy/dmgCIhobCVKigUz0seAjQe6YAfdDUxxq4A9DMT3KbuTEVTZaqL4REgNsDn31X3ieZgQrqJDCmqDf/y1u+qVZmhxH/bL2aPT1QuSyrsl/2kqVGwFBzinQkUbUbmyydDHFd2Rjlbo1zagkEdqUugw2dPk2S3W0fcOvnPrgK/r2cVcAGn6lHMAC9xZjGMV5+MWUYP2iNBUqn34bS/Jg3cap4GX+yS1BIBdN09JSCh5zpd8nB0lRvHi9im29MXiY78CYBm+f7nsqs0kt+SMu9v5yDJ+9D3EzGQX24FkjyGwFAkFUAyGxtE48LVw5Ygl1WSblS5g37iFD3jNYqDG6IOACPw5ksqRGsYZHbiVg4by9sgjIJSofrOc0ckOKr783+vHOlHGOBNbRuAseWDin/Pedj2pHbrBVdxtWgzLcBvNHE5aLizKs+l2eF8nw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LEXPR01MB12462990E23CB5916B16E082D16D0LEXPR01MB1246DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6fb35d66-8883-4aae-1353-08d752dd1b75
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Oct 2019 08:36:29.7192 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: H6yQfmL3shOdCKeFZ4PSLOtMS2Cy0uMzLTnPVNI/s7qPy+7hshEtJ/nsqICVfCDIwD6kEE64WwLrJSD0P/9/UfLFXOkP8WAFxOFtJXYdCYQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEXPR01MB0927
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/ryPBjwhllHcH7ZhSta87tNOnIGU>
Subject: Re: [ipwave] 5G deployment status
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, 17 Oct 2019 08:36:40 -0000

Hi all,
this information may be interesting for some of you also:

Dear All,
ETSI, in partnership with 5GAA and with the support of the European Commission, is organizing the 1st C‑V2X Plugtests™ event, hosted by DEKRA in Malaga from 02 to 06 December 2019.
The registrations for the 1st CV2X Plugtests event is now open. The deadline to register is 15 November 2019.

https://www.etsi.org/events/1659-cv2x-plugtests

Kind regards
Dirk

From: its <its-bounces@ietf.org> On Behalf Of Mr. Jaehoon Paul Jeong
Sent: Donnerstag, 26. September 2019 16:47
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: skku_iotlab_seminar@googlegroups.com; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>; its@ietf.org
Subject: Re: [ipwave] 5G deployment status

Hi Alex,
Thanks for your opinion and status of 5G.

I think IPWAVE needs to consider IPv6 over C-V2X based on 5G because
C-V2X has higher bandwidth than 802.11-OCB based on WAVE.

My SKKU group is studying how to efficiently support IPv6 over C-V2X in vehicular networks.
This will be a possible WG item for IPWAVE WG.

Thanks.

Paul

On Thu, Sep 26, 2019 at 9:50 PM Alexandre Petrescu <alexandre..petrescu@gmail.com<mailto:alexandre.petrescu@gmail.com>> wrote:


Le 25/09/2019 à 16:13, Alexandre Petrescu a écrit :
> Hi
>
> Le 20/09/2019 à 04:23, Sharon Barkai and Dick Roy ([RR]) wrote:
> [...]
>>> */[RR] This is a really long story, however, C-V2X is being specified
>>> as an alternative to US DSRC, not as a cellular access technology
>>> since that’s already available and deployed.  The reason LTE Release
>>> 14 and successors is being specified has nothing to do with its
>>> lineage as a child of cellular; in fact, it is provably a square peg
>>> being forced into a round hole and we all know how that generally
>>> ends up, and that’s a story for another day/*
>>>
>>> The 5G evolution is supposed to match the latency of peer to peer WiFi.
>
> When that matches, WiFi will have leaped forward to below
> 100micro-second latency.  This was so (cellular catching up with a
> leaping forward WiFi latency) since the invention of WiFi 20 years ago,
> and it wont change.  It's a constant of evolution.
>
>>> */[RR] 5G is nothing but hype at the moment
>
> Here is a more precise status, according to my personal understanding.
> This obviously differs from many people's understandings, who may be
> more knowledgeable.
>
> In France, frequencies for use in 5G radio would start to be discussed
> now in September, with allocation towards December.  The allocation is
> similar, but not quite like, the process that was used for 3G: auction
> sales.  The differences from 3G are: (1) it is not expected to generate
> huge revenues for gov't and (2) some sales, like of the 3.5GHz band,
> would actually be a re-allocation from what was previously allocated to
> wimax operators  (e.g. SDH in France) and to City Authority (like Mayor)
> in places where there was no operator).
>
> Obviously, until these frequencies are allocated one cant really talk
> about 5G deployment on public roads, even if...
>
> If one wants to talk about 5G like when talking a higher bandwidth and
> lower latency than 4G, then one assumes 4G to be 50ms latency and
> 2Mbit/s bandwidth.  One can talk then about 25ms latency and 10Mbit/s,
> and claim that to be 5G.  But it is not 5G.  It is just another Class or
> Category of 4G.  In theory, one can still be 4G and run at 1Gbps (e.g.
> Category 16).
>
> Also, one can talk about a higher bandwidth outdoors network by running
> 802.11 WiFi on 5.4 GHz and, why not, at 5.9GHz.
>
> Colleagues call these 'acrobatics 5G'.
>
> This is when one wonders: what is 5G anyways? with its associated
> question: why was the predecessor of 5G called 'LTE' (Long Term
> Evolution), or where is the long term?  Is 5G LTE?
>
> With respect to other countries, I heard two recent announcements, about
> Spain and Germany.
>
> They both claim 5G is deployed in the respective areas.
>
> This claims 15 cities in Spain on June 15th, by Vodafone:
> https://www.xataka.com/empresas-y-economia/red-5g-comercial-vodafone-espana-tiene-fecha-lanzamiento-15-ciudades-15-junio
>
>
> This claims 5 cities in Germany, but it does not say when, by Deutsche
> Telekom:
> https://www.telekom.de/start/netzausbau?wt_mc=alias_1070_netzausbau
>
> As hardware for end users, this is the situation now:
> - there is no 5G smartphone for sale in France.  I guess it is the same
>    in more countries.  If it were different, it would be an isolation
>    easily spot by many.
> - iphone 11 just launched features 'Gigabit-class LTE' and 'LTE
>    Advanced' but no '5G'.  They run on 'LTE Bands' which are your typical
>    frequencies below 5GHz for cellular communications, but nowhere like a
>    26GHz of 5G.  No such band is called a '5G band'.

Further details after searches of public documents:

iphone 11 pro understands a 5G frequency band:

it is specified to understand several frequency bands, among which also
TD-LTE Band number 42, which is 3400MHz - 3600MHz.  This band is a 5G
band.  Part of this band (3490MHz - 3600MHz) is being considered for
allocation by regulator ARCEP.  It has not yet been allocated, but under
discussion.

ARCEP considers to also allocate Band 43 at 3600MHz - 3800MHz, for 5G.
But this band is not covered by iphone 11 specs.

ARCEP is silent about the range 3400MHz-3490MHz.  I suspect there might
be some errors here.

iphone 11 pro also understands TD-LTE Band 46 at 5150 MHz - 5925 MHz,
which covers WiFi 5.4GHz and 802.11-OCB at 5.9GHz.  I suspect there
would be some clashes here between deployed Road-Side Units and iphones.

For highways and roads requirements, ARCEP seems to plan to require the
licensee to cover them by December 2025.  And the required bandwidth is
between 50mbit/s to 100Mbit/s and 10ms latency.  These figures are
obviously little incitative, because 2025 is very late, 50mbit/s is what
4G already does and 10ms is much higher than 1ms 802.11-OCB today.

On another hand, ARCEP requires the 5G licensee to support IPv6,
starting end of 2020. (in French: "Le  titulaire  est  tenu  de  rendre
son  réseau  mobile  compatible  avec  le  protocole  de  routage  IPv6
à compter du 31décembre2020.").  This means that by that time, if IPv6
under its form IPv6-over-OCB does not see a huge deployment compared to
just 802.11-OCB WSMP, it might be that IPv6-over-5G on routes would be
more likely.  Which may raise a question of the potential usefulness of
a spec IPv6-over-5G.

So, this is to say that where I live it is not very clear how these
things will unfold.

Alex


> - one can buy off the shelf modules, like miniPCIe (I have a list) that
>    go very high in terms of bandwidth, well beyond what normal 4G would
>    do, but couldnt really use them at that high parameters.
>
> Alex
>
>>> and simply matching the latency would be no reason to switch from
>>> DSRC to another access technology for V2V safety, though nothing
>>> prevents the addition of 5G NR access technologies in ITS stations
>>> (aka OBUs) for other uses. /*
>
> I agree.
>
> [...]
>
> Alex
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org<mailto:lisp@ietf.org>
> https://www.ietf.org/mailman/listinfo/lisp

_______________________________________________
its mailing list
its@ietf.org<mailto:its@ietf.org>
https://www.ietf.org/mailman/listinfo/its


--
===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Associate Professor
Department of Software
Sungkyunkwan University
Office: +82-31-299-4957
Email: jaehoon.paul@gmail.com<mailto:jaehoon.paul@gmail.com>, pauljeong@skku.edu<mailto:pauljeong@skku.edu>
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php<http://cpslab.skku.edu/people-jaehoon-jeong.php>