Middleware integration with 5G Testbed proposal about middleware

[adrianLIrobotics]

5gSlicing.docx

Added notes from confrence with 5g partners

[Artonus]

As a part of the SliceManager implementation, we will need to think about how we will store the information that some Edge or Cloud has access to the Network Slices.

[Artonus]

To be completed:

• Connection and communication with the Slice Manager API
• Storage of the SIM Card number for the Robot
• Create a new endpoint for Slice Manager to POST the data about the available slices. It should have a path data/slice, which means it has to be put in RedisInterface
• Prepare a logic to start the Middleware and call Slice Manager for available slices on startup.
• Storing globally (in Redis) the information about the slicing mechanism available at some locations with the types of Slices available (Slices are attached to an Edge or Cloud). When an update is made from Slice Manager, Middleware should override the existing Slice configuration.

Additional information:

Based on the additional analysis, I suggest moving the functionality of connecting to the SliceManager to Orchestrator. ResourcePlanner is unsuitable because it is only responsible for planning, not an instantiation of the resources. On top of this, a Resource planner can be called with an option to only provide the proposed resources, without their deployment. Association of an imsi with the Slice would be a part of the resource instantiation.

When the deployment is scheduled, the information about the selected slice should be passed with the deploy plan message and Orchestrator should initiate the connection to the SliceManager, when the deployment is certain.