Re: [6gip] 6G in 3GPP?

"Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com> Thu, 14 January 2021 18:29 UTC

Return-Path: <hannu.flinck@nokia-bell-labs.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 CF0643A12FB for <6gip@ietfa.amsl.com>; Thu, 14 Jan 2021 10:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level:
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 menlOaVCKIzn for <6gip@ietfa.amsl.com>; Thu, 14 Jan 2021 10:29:05 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60131.outbound.protection.outlook.com [40.107.6.131]) (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 2FC9D3A12FA for <6gip@ietf.org>; Thu, 14 Jan 2021 10:29:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VI/FEleH2gIi0wcmYYP9rYsAQJ58Vl7XRHfIinWP8ftACiSUIGMunJvd6Jg6NmTYAEXBlkvj16BCjTEPJIaWsn0Desv1l+Rl1NYJQWEMsZIUpCrkyWzwdY/a/vif9OzVUh3VXxhbxZH+lWZL9Bmz4bTqj19CsZ+CkviCjDaJdE3qvpWAbLg32geq2BddKxppevblAL1D3mYOu31gR/NJ7v3vyY94AVKEbFunBbHwxXDFFUDzJufFM8nLyug8cTZ4PQTWVHloZfdrtTNRA3BtugjCxpxBHpxioRtVMmQMKhBYkY9gdgcawBW/tOVB5e1o3HDUKjME8kvW7X3q3M46WQ==
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=M5b8rQZxcrgiWg0IfPMC9aUazwLdSXOFdmxrL+KZ850=; b=dK5FjSJo44fcIQdvm9Z/IztX7kifqW4ZhRuhOzl4XzNAzXcyle63TjJVG3A/1odudtoNSmj8giK7YjWiTD9PcebmHTwa66F35evWGhSvKr1iB8NIm/DfMi4uZwM/p4YUC7XcVVAmBcK0WC8DHg81HvUSBDPHheuDGjh0QcMNnn6wuSD13xp6J4FBteUAsXH70vcc8+H+FI+L8QD5EtjWuQP6LfnuTjMxcQ2qt0sjClRJ5tjmlZASSN/J+LKuGhUzC/D7t6/qKbL38b9ktbpcdlfYEg3+6aEW2sjPW4JFC5GnjYuMAxRbnjGl9SOKpYBXnRSIDtDbW8zI8ibEi+LQ+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia-bell-labs.com; dmarc=pass action=none header.from=nokia-bell-labs.com; dkim=pass header.d=nokia-bell-labs.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=M5b8rQZxcrgiWg0IfPMC9aUazwLdSXOFdmxrL+KZ850=; b=srAtVU9+X3hNRlqdVsxeSKI+oPYyBEZq7o/A1gzpV9n83kR94NVnqwtoKrtr6B4yFdcZ7QYgF71bQWzJrKZYFgGA1Dvq7wsg1biyny4YfmfzvpuvmgXRwwcHvi0iaN0t+gGwFc+bUr748HJ9MPcOq043lD4GKstAt+0GS6ebHW8=
Received: from HE1PR07MB3386.eurprd07.prod.outlook.com (2603:10a6:7:2d::25) by HE1PR07MB4426.eurprd07.prod.outlook.com (2603:10a6:7:a1::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.2; Thu, 14 Jan 2021 18:28:57 +0000
Received: from HE1PR07MB3386.eurprd07.prod.outlook.com ([fe80::21ac:2e3f:29b6:4a2d]) by HE1PR07MB3386.eurprd07.prod.outlook.com ([fe80::21ac:2e3f:29b6:4a2d%7]) with mapi id 15.20.3763.009; Thu, 14 Jan 2021 18:28:57 +0000
From: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>
CC: "6gip@ietf.org" <6gip@ietf.org>
Thread-Topic: [6gip] 6G in 3GPP?
Thread-Index: AdbpA1Dfe7Zkyd8yTJ67jtGt1oL86wAhGVIAAA7pi9AAM9FyAAAD2LWQ
Date: Thu, 14 Jan 2021 18:28:57 +0000
Message-ID: <HE1PR07MB3386B9F18A356F64A0B6DD359BA80@HE1PR07MB3386.eurprd07.prod.outlook.com>
References: <HE1PR07MB3386A43B4B32BF2CE5DC48C79BAA0@HE1PR07MB3386.eurprd07.prod.outlook.com> <248399ab-7dc1-ee13-928c-751568ea58e5@gmail.com> <HE1PR07MB3386A19851BFFF1ED5DDECAE9BA90@HE1PR07MB3386.eurprd07.prod.outlook.com> <CAC8QAccaYy7hKAdz9Y79wMrE0UFBa_=PsERyeGpiMmYpWESLLw@mail.gmail.com>
In-Reply-To: <CAC8QAccaYy7hKAdz9Y79wMrE0UFBa_=PsERyeGpiMmYpWESLLw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ieee.org; dkim=none (message not signed) header.d=none;ieee.org; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [91.154.146.213]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 0270658d-4879-4534-d874-08d8b8ba41b2
x-ms-traffictypediagnostic: HE1PR07MB4426:
x-microsoft-antispam-prvs: <HE1PR07MB4426C59E587747EA7D14C88F9BA80@HE1PR07MB4426.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: hNBWJrilvlAet6LYb9PjdTc7R7SIJx1tJZJbcjGM+sR9LAZTnpEsKOT7Kv+5fOQyfEBSEG4hPibIMBzb5IUxIGhPNOssd61TdWFuFErh+q8i+efqwl4d/Cwk2jUKOSeHwa/xru2a2Zpc0W9rJLFn1S8FkMBnnpIxo3y6PBERWzpKNUcfNiJGIsYI+BdZo+48bYPeRb16zl1k090lrFYG1xPovQt7fLaUZ8NvlUq+w3cfJN1jMFH8jqQ0apXLxbCHZPlgd4cYLhyyJy9iEW0ARcbgYxrlA+7DhtR96vNT1Go076CigIFKj8vdPTwOxaIqcna7dbXAc6HItOHXJiIMCRTvWHqXxYiDqTMm5/VTpLq2GCuSF4zB00kb0tzwmv95DjN34bb8TWa3nYpqB6sWWUPUaNYmA90mPNgZ2DnGK96OLGvjOyA8ztNJAbqC7ot7f0ecVFPIOqsEMCJBMwRh9YaPF6RO3ClfMeikc2YuP/J2nUZunSGmGrYH+tUyYZdLk0oeqIaS2j/iuO1rxiodp8TFrKq2FTSia7xeuA2QUtcLyGPuzM0lG2sNoyov9KFbHDbhvAVA46LDfxla1zSI0kgCje2kVXeV4NcheqQ2jb0=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:HE1PR07MB3386.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(136003)(39860400002)(346002)(366004)(396003)(376002)(55016002)(66446008)(9686003)(6916009)(7696005)(66556008)(5660300002)(64756008)(66476007)(66946007)(52536014)(53546011)(8676002)(26005)(8936002)(33656002)(166002)(2906002)(478600001)(316002)(966005)(66574015)(6506007)(83380400001)(71200400001)(86362001)(186003)(76116006)(4326008); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: NA7+CCHAZ7kV+KpKIKgYOT5XX/HFhAgRmm57MBeen4HHVfdzNiDPhcwPh+lFyM6HlReRi5edpxEwaAjbJ1vjfdzOON1QDZRMNDJSqLDnozy4nXPhGyWgXF71qe4htkn8ShSEOJrrsN6JRM2WeK49ft6v5nBFBsweew7IAtvEQvWwLJ35P9MxY3T5erCQiA1Q62eaTCHOPYxtEewU2LKwWWDK+cagIJeQ8AWIm0gj3wZoWE1M8jGYurmUqvZUv1NqtnVbbj5kJplaU/MyeJ+rt8WtN5Lai3PO2fcbxMVqTGpYdQUVW7eVlb+FItxB/dVLlij6jcZ3gIJ2TK8jYT3D4yukscC0evqYpBdJFLFEpWMfrdger0FI6gMJsj7C9t+nm0Dn7Cx84pqbY+zdj+Z4pLc8AoL79J2ZkDe0BXj+WLY0rQcql8Qsro/gUeUhOzWr3IopgOkVFt5ESdN4/SM78H1vRlMxLwrJEGlhhdxzs10LwWxyLzt37bxHS+mt+7kqK0S/98a3O7wdReil8L9tg8HA6EdXnR1oTBTG8Xe+Gf8YVh9prqUDxD+yPLHqz+TsD41EIbM5OJ4TiL5WJ0FFkJolsuxNUFB84bxfKBpm42ZZpr78f7uRpiXxeZ/PJqKU5DOMkgByI9KolBAwkMBzyhclbiA11Bla4t4PCXpoon0vngMgDCJ1MWI8wCVTKvC+J1TUi+GbsGlukXGbE1cj7KyzuT9p3fq547xTwZ2F3QjIS+S04lEWRlfEbFGCMKpfBUnMycxF4aZbjDqEEyp3dKQN18r6mhFsbvO57/bDNrkIyxBzPuPjjzW7wlA7gHFrid3A6FeSi8xhnTGeVGfUINbgeLJkQk7KMl9CAmeF0pCKNJK1A3ggWNSQN1j8c++OZGMSIKzaXkfyZVKAZN6D+Zi4PGUgJYHEcacTsJRgky67mwDff1R7fbXl1OCpKeXf2w0dyq3DQjpwNP+mx8UygGSXEj/+BzgPaeLqn1JboZg=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3386B9F18A356F64A0B6DD359BA80HE1PR07MB3386eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3386.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0270658d-4879-4534-d874-08d8b8ba41b2
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jan 2021 18:28:57.6973 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: uzidXVBoDHAo+onhBEPTAwMHWaRyKuGtcXdqvLMot7vG3fVm7IZKljc8yOEGKHWZKRihnQbPdRQs/LkoMSfE1sC6RqX1GKqJnUAl671VieO7FhZuWYAID7N4J834lVeU
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4426
Archived-At: <https://mailarchive.ietf.org/arch/msg/6gip/Gu4MH6QMufLFLdsUkzOf5RAUZic>
Subject: Re: [6gip] 6G in 3GPP?
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: Thu, 14 Jan 2021 18:29:08 -0000

Hello Bechet

In your mail sent  19th of Now you are attaching presentations.
In Alex’ presentation, there is slide titled 6G-related efforts. In that slide the last bullet item reads “• 3GPP Release 17 talks also 6G”.

I can assure you that Rel 17 is not addressing 6G for sure. There are no SA1 study items on 6G.

Please have look at the link that Stefan Alfredsson shared. It is point to a mid-generation step to 5G. What is mid-generation in your opinion?
Isn’t it midway?

Best regards
Hannu

From: Behcet Sarikaya <sarikaya2012@gmail.com>
Sent: Thursday, January 14, 2021 6:31 PM
To: Flinck, Hannu (Nokia - FI/Espoo) <hannu.flinck@nokia-bell-labs.com>
Cc: 6gip@ietf.org
Subject: Re: [6gip] 6G in 3GPP?

Hi Hannu,


On Wed, Jan 13, 2021 at 9:58 AM Flinck, Hannu (Nokia - FI/Espoo) <hannu.flinck@nokia-bell-labs.com<mailto:hannu.flinck@nokia-bell-labs.com>> wrote:
Hello

Neither I know any, nor my colleagues any 3GPP documents about 6G.

I checked our chair slides at  IETF 109 side meeting, we have no mention of 3GPP doing 6G there.

3GPP is currently at mid-way with 5G. There will still be a number of releases left for 5G  to come.

This is wrong.
5G is already here. Samsung had 5G phone in 2019. Apple iPhone 12 was introduced in 2020 with 5G.
There are deployments going on worldwide.

It seems you are confusing 3GPP Releases with 5G deployments. 5G came with the first release that introduced 5G, I think it was Release 15.
So any operator compliant with that release claims to support 5G in its network. In the US almost all major operators claim to have 5G.

Newer releases of course are developed as Release 16, 17, etc. They introduce many nice features. No issues with that.
However, as far as I know the operators usually do not update their networks with any new release that comes up.
With LTE, as far as I remember the most popular release was Release 12, (I think)  which was the most widely deployed.

In fact, I assume that now when 5G is pushing towards new verticals (mIoT, industry, vehicular, etc.) there will be new requirements for protocol work needed for 5G.
For example, consider the discussion about multi-path support for QUIC in QUIC wg. Similar requests are likely to come.

Therefore, I am on the opinion that 6G work, even 6G related protocol research work in the IRTF, should wait for use cases (and radio extensions) that 5G is not able to respond.

We do not have any IRTF request currently, so I can not talk about that, IRTF is another issue.
For our list, we don't have a charter to follow. We are a mailing list,we submitted a short description text to IESG which was approved.
So we can discuss freely all issues around 6G  mostly as they are related to IP, hence the name 6gip.

We plan on continuing to host side meetings, continue to discuss the developments on 6G, as we see projects are popping up all over the world. The conferences are having 6G sessions, special or invited talks on 6G, etc.
So the question of what is 6G is going to get clarified more and more as we go along. If our discussions, the work people do in this list contributes to that, even better.



I believe that one day 3GPP SA1 will start working on developing requirements for 6G. We don't know when, maybe as someone active in 3GPP, you can tell us.

Regards,
Behcet


Best regards
Hannu

-----Original Message-----
From: Alexandre Petrescu <alexandre.petrescu@gmail.com<mailto:alexandre.petrescu@gmail.com>>
Sent: Wednesday, January 13, 2021 10:40 AM
To: Flinck, Hannu (Nokia - FI/Espoo) <hannu.flinck@nokia-bell-labs.com<mailto:hannu.flinck@nokia-bell-labs.com>>; 6gip@ietf.org<mailto:6gip@ietf.org>
Subject: Re: 6G in 3GPP?

Me too I would like to ask I would like whether someone knows of a document on the 3gpp.org<http://3gpp.org> site that has the term '6G' in it?

Le 12/01/2021 à 17:55, Flinck, Hannu (Nokia - FI/Espoo) a écrit :
> Hello Alexandre
>
> In your slides you claim the 6G is discussed in Rel 17. Can you tell
> in which document or WG?
>
> I am involved quite a bit in 3GPP as well as in 6G research and I am
> not aware of any of such discussion.
>
> Without a reference I must consider that statement be misinformation.
>
> Best regards
>
> Hannu

Thanks for having gone through the slides; the slides tried to summarize the discussions on the email list at that time.

It might be that a potential reationship between 3GPP and 6G to be a stretch.

I might bear responsibility of having misread the emails, or read them too quickly, when drawing a conclusion that 3GPP might work on 6G, and writing that down.  Sorry for misunderstanding.

We had some mention on this list of an NGMN alliance (Next Generation Mobile Networks) which initiated a task force on 6G; elsewhere, NGMN is ack'ed as a contributor to 3GPP by a wikipedia article.  That might make it that 3GPP might have some work on 6G.

It might be that some discussions between usual contributors to 3GPP might have mentioned 6G even though there might be no document on 3gpp.org<http://3gpp.org> that reads '6G'.  For my part, I do not know what document is Rel 17 more precisely, but I suspect I could find Rel 17 on 3gpp.org<http://3gpp.org>.

It might be that other industry alliances (e.g. 5GAA) could be outright opposed to work on things deemed "6G".  It might be that such opposition is supported by other funding bodies.  I do not know why the opposition, but that is the way it is.

If, for some reason, 3GPP considers the talk of 6G to be too early, and why not potentially disruptive to the ongoing work of 5G, then that is a 3GPP problem to solve.  That would not be the only problem they should address.  I suspect a ling standing problem is even the name "3G" in a 3GPP working on something else than 3G (e.g. 3GPP working on 4G or 5G).

I want to tell also that there might be other problems of 5G, on which 3GPP works, and which deserve attention.

Such problems could be solved by working on something new, like 6G.

It is a speculation from my part.

I would like to ask others whether someone knows of a document on the 3gpp.org<http://3gpp.org> site that has the term '6G' in it?

Alex

--
6gip mailing list
6gip@ietf.org<mailto:6gip@ietf.org>
https://www.ietf.org/mailman/listinfo/6gip