Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Edge]Usecases_vRAN_add.md #1575

Merged
merged 6 commits into from
May 29, 2020
Merged

[Edge]Usecases_vRAN_add.md #1575

merged 6 commits into from
May 29, 2020

Conversation

Karimrabie
Copy link
Collaborator

Hello,

Thanks to review the content for vRAN use case.
The fourth use case.

@rabi-abdel rabi-abdel added On Hold Needed to wait until another PR progress. and removed New labels May 12, 2020
@rabiabdel rabiabdel added this to the M3 (Freeze Contributions) milestone May 15, 2020
@rabi-abdel rabi-abdel removed the On Hold Needed to wait until another PR progress. label May 16, 2020
@pgoyal01
Copy link
Collaborator

Acronyms at first use need the full term to be defined with the acronym in parentheses.

@pgoyal01
Copy link
Collaborator

I am unable to make a suggestion within the file. I am not sure what the first or second sentence are attempting to say:

"Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing. The requirements for user plane Local Breakout / Termination are common mandating that VASs & Any Gi-LAN applications are locally hosted at the Edge."

Not sure but maybe:
"Ultra-low latency and enhanced Mobile BroadBand (eMBB) use cases benefit from 5G and Edge networking integration. Some of the Value Added Services (VASs) and Gateway Internet LAN (Gi-LAN) applications require them to be hosted at the Edge.

@pgoyal01
Copy link
Collaborator

The following sentence needs to be fixed:
"The Telco Edge is a perfect fit for centralized vRAN deployment and vDU/vCU hosting preserving the latency requirements."

maybe:
"The Telco Edge is a perfect fit for centralized vRAN deployment and vDU/vCU hosting that satisfy the latency requirements."

@Karimrabie
Copy link
Collaborator Author

Karimrabie commented May 20, 2020

I am unable to make a suggestion within the file. I am not sure what the first or second sentence are attempting to say:

"Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing. The requirements for user plane Local Breakout / Termination are common mandating that VASs & Any Gi-LAN applications are locally hosted at the Edge."

Not sure but maybe:
"Ultra-low latency and enhanced Mobile BroadBand (eMBB) use cases benefit from 5G and Edge networking integration. Some of the Value Added Services (VASs) and Gateway Internet LAN (Gi-LAN) applications require them to be hosted at the Edge.

@pgoyal01 I can explain

The following sentence needs to be fixed:
"The Telco Edge is a perfect fit for centralized vRAN deployment and vDU/vCU hosting preserving the latency requirements."

maybe:
"The Telco Edge is a perfect fit for centralized vRAN deployment and vDU/vCU hosting that satisfy the latency requirements."

@pgoyal01
preserving here means that it is a prefect fit as long as it maintains the Fronthanul latency requirements. Otherwise, maybe Telco Edge PoPs won't fit and the cell site deployment might be a better option.

@Karimrabie Thanks. Are you satisfying the "latency requirements"? "Preserving" implies that you are just maintaining the requirements not necessarily meeting/satisfying them through this mechanism.

@pgoyal01
Copy link
Collaborator

Do we monetize "5G network slicing" or we monetize 5G using network slicing?
"Monetizing 5G network slicing by providing eMBB Network slice with distributed CDN as a Service providing UHD Streaming Experience, Video Optimization, Caching for Large files, and other Capabilities that can either bundled by the Network Slice offering or implicitly enabled by the operator."
also unnecessary capitalisations.

Suggest:
"Monetizing 5G by provisioning eMBB network slice with distributed CDN as a service, that enables UHD streaming, Video Optimization, caching for large files, and other capabilities."

@Karimrabie
Copy link
Collaborator Author

I am unable to make a suggestion within the file. I am not sure what the first or second sentence are attempting to say:

"Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing. The requirements for user plane Local Breakout / Termination are common mandating that VASs & Any Gi-LAN applications are locally hosted at the Edge."

Not sure but maybe:
"Ultra-low latency and enhanced Mobile BroadBand (eMBB) use cases benefit from 5G and Edge networking integration. Some of the Value Added Services (VASs) and Gateway Internet LAN (Gi-LAN) applications require them to be hosted at the Edge.

@pgoyal01 I can explain in the call. The original text is describing the coupling between Telco Edge and 5G use cases. The terms eMBB & uRLLC are all 5G terms (Use cases), these are not use cases that benefit from 5G. These are the Core 5G Use cases. In order to deliver such use cases In the form of network slicing, Telco Edge is the main enabler.

@Karimrabie
Copy link
Collaborator Author

Do we monetize "5G network slicing" or we monetize 5G using network slicing?
"Monetizing 5G network slicing by providing eMBB Network slice with distributed CDN as a Service providing UHD Streaming Experience, Video Optimization, Caching for Large files, and other Capabilities that can either bundled by the Network Slice offering or implicitly enabled by the operator."
also unnecessary capitalisations.

Suggest:
"Monetizing 5G by provisioning eMBB network slice with distributed CDN as a service, that enables UHD streaming, Video Optimization, caching for large files, and other capabilities."

Yes. I agree.

@Karimrabie
Copy link
Collaborator Author

I am unable to make a suggestion within the file. I am not sure what the first or second sentence are attempting to say:
"Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing. The requirements for user plane Local Breakout / Termination are common mandating that VASs & Any Gi-LAN applications are locally hosted at the Edge."
Not sure but maybe:
"Ultra-low latency and enhanced Mobile BroadBand (eMBB) use cases benefit from 5G and Edge networking integration. Some of the Value Added Services (VASs) and Gateway Internet LAN (Gi-LAN) applications require them to be hosted at the Edge.

@pgoyal01 I can explain

The following sentence needs to be fixed:
"The Telco Edge is a perfect fit for centralized vRAN deployment and vDU/vCU hosting preserving the latency requirements."

maybe:
"The Telco Edge is a perfect fit for centralized vRAN deployment and vDU/vCU hosting that satisfy the latency requirements."

@pgoyal01
preserving here means that it is a prefect fit as long as it maintains the Fronthanul latency requirements. Otherwise, maybe Telco Edge PoPs won't fit and the cell site deployment might be a better option.

@Karimrabie Thanks. Are you satisfying the "latency requirements"? "Preserving" implies that you are just maintaining the requirements not necessarily meeting/satisfying them through this mechanism.

@pgoyal01 Well, in that case. I believe we are aligned. It is just a matter of choosing the right term. I will change it accordingly. Thanks.

@Karimrabie
Copy link
Collaborator Author

Do we monetize "5G network slicing" or we monetize 5G using network slicing?
"Monetizing 5G network slicing by providing eMBB Network slice with distributed CDN as a Service providing UHD Streaming Experience, Video Optimization, Caching for Large files, and other Capabilities that can either bundled by the Network Slice offering or implicitly enabled by the operator."
also unnecessary capitalisations.
Suggest:
"Monetizing 5G by provisioning eMBB network slice with distributed CDN as a service, that enables UHD streaming, Video Optimization, caching for large files, and other capabilities."

Yes. I agree.

I will just leave the bundling at the end because We are talking about monetisations and this is how the final product will be delivered to market. Either in a bundle with Network Slicing or enabled for all Consumers under certain conditions.

@rabi-abdel
Copy link
Collaborator

@pgoyal01 please re-review based on latest @Karimrabie replies.

@rabi-abdel rabi-abdel requested a review from pgoyal01 May 27, 2020 09:22
@@ -135,7 +135,7 @@ CNTT believes that Edge computing is unique in terms of infrastructure requireme

- **Architecture**

<img width="1089" alt="Screenshot 2020-04-16 at 6 22 58 PM" src="https://user-images.githubusercontent.com/25845305/79684936-635ae400-8235-11ea-9c97-4774aba24d17.png">
<img width="1066" alt="Screenshot 2020-05-17 at 11 34 47 PM" src="https://user-images.githubusercontent.com/25845305/82160627-0172b600-9897-11ea-99ec-7339deb19fce.png">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image needs to be moved to the appropriate figures directory under CNTT

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image needs to be moved to the appropriate figures directory under CNTT

May I know where is this directory?

All acronyms need to be defined on first use.

All figures need to be under CNTT Github scope.

@pgoyal01 I added the definition for the acronyms (eMBB, UHD, & CDN) in the first use cases.
Could you please advice where is the exact folder/directory to be used for the figures?

@@ -117,9 +117,9 @@ CNTT believes that Edge computing is unique in terms of infrastructure requireme

- **Architecture**

<img width="1079" alt="Screenshot 2020-04-14 at 8 37 57 PM" src="https://user-images.githubusercontent.com/25845305/79390856-c536f780-7f70-11ea-88d5-cfd89cf5121a.png">
<img width="1066" alt="Screenshot 2020-05-17 at 11 31 44 PM" src="https://user-images.githubusercontent.com/25845305/82160584-b35db280-9896-11ea-921c-6a7f8e5bb866.png">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image needs to be moved to the appropriate figures directory under CNTT

- **Architecture**

<img width="1068" alt="Screenshot 2020-05-11 at 5 51 34 PM" src="https://user-images.githubusercontent.com/25845305/81582240-15f31200-93b0-11ea-993e-a89f820a5d97.png">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This image needs to be moved to the appropriate figures directory under CNTT

@pgoyal01
Copy link
Collaborator

All acronyms need to be defined on first use.

All figures need to be under CNTT Github scope.

@pgoyal01
Copy link
Collaborator

@Karimrabie

First use examples: Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing.

Figures: the usecase.md is at ../doc/tech/usecases.md and the associated Figures should be in ../doc/tech/figures and the Figure sources should be in ../doc/tech/figures/artefacts

@Karimrabie
Copy link
Collaborator Author

@Karimrabie

First use examples: Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing.

Figures: the usecase.md is at ../doc/tech/usecases.md and the associated Figures should be in ../doc/tech/figures and the Figure sources should be in ../doc/tech/figures/artefacts

Thanks @pgoyal01
I made the changes for the acronyms and submitted a PR for uploading the files.
Thanks to approve.
@ASawwaf @CsatariGergely @rabiabdel @TFredberg @bfcohen

@Karimrabie

First use examples: Telco Edge is commonly coupled with 5G use cases, seen as one of the ingredients of the ultra-low latency/eMBB Network Slicing.

Figures: the usecase.md is at ../doc/tech/usecases.md and the associated Figures should be in ../doc/tech/figures and the Figure sources should be in ../doc/tech/figures/artefacts

Thanks @pgoyal01
I updated the acronyms and submitted 2 PRs for uploading the diagrams and source files.
Thanks to approve.
@ASawwaf @rabiabdel @TFredberg @bfcohen

Copy link
Collaborator

@bfcohen bfcohen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@rabi-abdel
Copy link
Collaborator

@Karimrabie can all figures please be placed in: ./figures?

@rabi-abdel
Copy link
Collaborator

I see all images being added in #1631. so merge this one.

@rabi-abdel rabi-abdel merged commit 9b24ba6 into master May 29, 2020
Edge automation moved this from In progress to Done May 29, 2020
@rabi-abdel rabi-abdel deleted the Karimrabie-patch-3 branch May 29, 2020 07:54
gkunz pushed a commit to gkunz/CNTT that referenced this pull request Jun 4, 2020
* Update usecases.md

* Update usecases.md

* Update usecases.md

* Update usecases.md

* Update usecases.md

* Update usecases.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Edge
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

10 participants