PoC Topics: Difference between revisions
(Created page with "= Rationale = ENI PoC Topics are specific areas, often linked to a Work Item, where input or feedback from the ENI Proofs of Concept is needed. ENI PoC Topics help to focus...") |
Korycinska (talk | contribs) |
||
| Line 6: | Line 6: | ||
= ENI PoC Topics = | = ENI PoC Topics = | ||
As described in the ENI PoC Framework, a PoC Team proposal shall address at least one goal relevant to ENI i.e. related with an ENI Use Cases | As described in the ENI PoC Framework, a PoC Team proposal shall address at least one goal relevant to ENI i.e. related with an ENI Use Cases, an ENI Requirements or the suitability of an ENI System Architecture aspect. The output of the PoC should provide feedback to the ISG ENI that should support the improvement of the output of the existing WIs. Alignment with existing activities is required. See table below. | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 12:56, 18 May 2018
Rationale
ENI PoC Topics are specific areas, often linked to a Work Item, where input or feedback from the ENI Proofs of Concept is needed. ENI PoC Topics help to focus PoC Projects on the most relevant topics for the ISG ENI, and to increase the relevance of their contributions.
ENI PoC Topics are identified and documented by ISG ENI. ENI PoC Topics may include templates for the PoC Contributions and deadlines to ensure that the PoC Contributions arrive on-time to be taken into account by the targeted WIs.
ENI PoC Topics
As described in the ENI PoC Framework, a PoC Team proposal shall address at least one goal relevant to ENI i.e. related with an ENI Use Cases, an ENI Requirements or the suitability of an ENI System Architecture aspect. The output of the PoC should provide feedback to the ISG ENI that should support the improvement of the output of the existing WIs. Alignment with existing activities is required. See table below.
| Level 1 | Level 2 | |
|---|---|---|
| Use Case | Network Operations | Policy-driven IP managed networks |
| Radio coverage and capacity optimization | ||
| Intelligent software rollouts | ||
| Policy-based network slicing for IoT security | ||
| Intelligent fronthaul management and orchestration | ||
| Service Orchestration and Management | Context aware VoLTE service experience optimization | |
| Intelligent network slicing management | ||
| Intelligent carrier-managed SD-WAN | ||
| Network Assurance | Network fault identification and prediction | |
| Assurance of service requirements | ||
| Infrastructure Management | Policy-driven IDC traffic steering | |
| Handling of peak planned occurrences | ||
| Energy optimization using AI | ||
| Requirement | Service and network requirements | General requirements |
| Service orchestration and management | ||
| Network planning and deployment | ||
| Network optimization | ||
| Resilience and reliability | ||
| Security and privacy | ||
| Functional requirements | Data Collection and Analysis | |
| Policy Management | ||
| Data Learning | ||
| Interworking with Other Systems | ||
| Non-functional requirements | Performance requirements | |
| Operational requirements | ||
| Regulatory requirements | ||
| Non-functional policy requirements |
Addressing a PoC Topic in a PoC Project
PoC Teams specify the targeted PoC Topic(s) in their PoC Proposal, and commit to provide the expected input or feedback in the requested format (template, if applicable) in a timely manner.
Feeding back the results
As soon as experimental results relevant for a given ENI PoC Topic are available (no need to wait for the PoC Project to be completed), the PoC Team creates a contribution and informs the ISG ENI by email (if the PoC Topic had a specific template for feedback contributions, it should be used). PoC Teams are also encouraged to contribute additional results and lessons learned during the PoC Project to the ISG ENI.