The objective of 5G-IANA's public acceptance survey is to assess the usefulness of the proposed Automotive Open Experimental Platform (AOEP) and identify potential barriers.
If you are not familiarised with the 5G-IANA platform, please read the following text before answering the questionnaire.
If you have attended a 5G-IANA webinar, you can skip this and go directly to the questions:
- A Network Application (nApp) is a virtual application that can be deployed in a 5G infrastructure and can use 5G services (e.g., connectivity). An Automotive Vertical Service can be composed by one or multiple nApps. A nApp can be composed by one or multiple application and/or network functions (AFs and NFs).
- The AOEP is an enhanced Automotive-related experimentation infrastructure where a repository of AFs and NFs exists, along with the hosting of a number of nApp Starter Kits, i.e., simple examples of different nApps that third parties (i.e., SMEs) can use as a baseline to develop their own nApps or that can be included in Vertical Service chain to consume exposed services.
- It offers functionalities for designing, validating, and benchmarking/experimenting Vertical Services and their components (i.e., nApps and NFs/AFs) and thus, provides functionalities for easing the design and chaining of new Automotive-related services.
- It offers the ability to deploy and orchestrate Vertical Services from the application point of view, and to monitor them at run-time.
- It allows the deployment of services at the edge of the network (on OBUs and RSUs), and by doing so reduces the end-to-end application latency of services, as well as supporting privacy for sensitive application data. Especially, it allows to implement/integrate a “lightweight” orchestration on top of OBUs/RSUs for offering a more flexible and scalable management of Vertical Services and constituent nApps and AFs/NFs.
- It provides the appropriate end user graphical interface, allowing: a) the onboarding of the application components (in form of microservices), b) the editing of the functional application component parameters (e.g., required CPU, Memory, location of image, dependencies on other components etc.), c) the selection or definition of monitoring metrics from the application components, d) the linking of application components to form service nApps combining application-related components (i.e., AFs) and networking related components (i.e., NFs), e) the editing of functional operating parameters (e.g., location, targeted latency and bandwidth limits, linking to access UIs, etc). Overall, it provides a user-friendly and openly accessible environment to experimenters for the experimentation, validation and testing of their applications with ease.