Re: [Teas] 5G use-case for Framework draft

[Daniele Ceccarelli <[e-mail]>]

Hi Krzysztof,

I agree with everything you say, and given the huge overlap between RAN and transport in C-RAN I’m just suggesting to remove the RAN box and the RS arrow from the picture simply to avoid giving the wrong impression that INS_3 and INS_4 (in this specific case) are part of the RS or that the IETF network slice is slicing the RAN…it’s simple crisis prevention.

[cid:image001.png@01D845B2.A4653120]

Cheers,
Daniele


From: Krzysztof Szarkowicz <[e-mail]>
Sent: den 31 mars 2022 18:08
To: Daniele Ceccarelli <[e-mail]>
Cc: Adrian Farrel <[e-mail]>; Lou Berger <[e-mail]>; WG Chairs <[e-mail]>; Vishnu Pavan Beeram <[e-mail]>; TEAS WG <[e-mail]>; Rokui, Reza <rrokui=[e-mail]>
Subject: Re: [Teas] 5G use-case for Framework draft

Hi Daniele,

We could easily see FN, MN and BN connectivity matrices multiplexed on the same physical link. Even more, multiple FNs/MNs/BNs (from different slices and/or end devices) multiplexed over the same physical link (or, over the same transport infrastructure in general). So, the diagrams provided by Reza provide logical view (not physical view).

And, yes, CU is part of the RAN, regardless of actual physical location of the CU (i.e, pleaced on the same DC as the packet core functions), based on the specs. So, logical connections between RU and DU INS_3, and DU-CU (INS-4) are part of RAN from that perspective. At the same time, INS-4 of one slice, could be multiplexed with INS_1 of another slice other the same physical link (or, over the same transport infrastructure in general), depending on the mobile function locations in each slice.

I agree, that MN and BN is like any other TN. FN has, on the other hand, much more strict requirements regarding latency comparing to typical MN/BN.

My 2 cents

Cheers,
Krzysztof



On 2022 -Mar-31, at 17:04, Rokui, Reza <rrokui=[e-mail]<mailto:rrokui=[e-mail]>> wrote:

I am fine with your suggestion Daniele.  The idea is to illustrate a use-case which is clear and give more practical context to Framework document.

Cheers,
Reza

From: Daniele Ceccarelli <[e-mail]<mailto:[e-mail]>>
Date: Thursday, March 31, 2022 at 11:00 AM
To: Rokui, Reza <rrokui=[e-mail]<mailto:rrokui=[e-mail]>>, Adrian Farrel <[e-mail]<mailto:[e-mail]>>, Lou Berger <[e-mail]<mailto:[e-mail]>>, WG Chairs <[e-mail]<mailto:[e-mail]>>, Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>, TEAS WG <[e-mail]<mailto:[e-mail]>>
Cc: Rokui, Reza <[e-mail]<mailto:[e-mail]>>
Subject: [**EXTERNAL**] RE: 5G use-case for Framework draft
Hi Reza,

I agree on the fact that the most interesting use case is cloud RAN but I don’t really like the way it’s illustrated (I know it’s difficult).
From the picture it seems that INS3 and INS4 are part of the radio slice, while they are not. The same applies to the RAN box. DU, and mostly CU, might be deployed even further into the network (the CU could easily be together with the Core), that would make the RAN extend all over till the Core.
Moreover the FN and MN from our point of view are like any other TN  (and if the core moves to the right all the TNs become MNs ?

My suggestion is to remove RS and CS from the picture and explain them verbally and call on the transport network TNs.

BR
Daniele

From: Teas <[e-mail]<mailto:[e-mail]>> On Behalf Of Rokui, Reza
Sent: den 30 mars 2022 18:23
To: Adrian Farrel <[e-mail]<mailto:[e-mail]>>; Lou Berger <[e-mail]<mailto:[e-mail]>>; WG Chairs <[e-mail]<mailto:[e-mail]>>; Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>; TEAS WG <[e-mail]<mailto:[e-mail]>>
Cc: Rokui, Reza <[e-mail]<mailto:[e-mail]>>
Subject: [Teas] 5G use-case for Framework draft

Hi Adrian,

As per discussion during the TEAS presentation at IETF 113, attached please find the application of IETF network slicing on 5G use-case.
Please note that I have included the applicability of IETF network slices in three different deployments for completeness. If you want to pick one of these use-cases and include them in Framework document, my suggestion is to include the very last one (I.e., C-RAN) use-case. Please reach out if you need more information on these use-cases.

Reza

_______________________________________________
Teas mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/teas