Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Related to UPF shunting at the MNO (CSPs) to check the already implemented in 3GPP System Architecture related Local Traffic Routing and Service Steering the functionalities related to multiple N6 UDP sessions and selection and re-selection of UPFs by the AF.
  • If possible, to elaborate why it is selected to refer to UPF deployed in the DC and not the other 3 alternative UPF deployments
  • With regard to MNO/CSP's Network (5G NSA/LTE and/or 5G SBA Network Architecture Configuration) selected functions invoked in the MEC host through partial and/or full intergration of MNO/CSPs Network CCF with ETSI MEC Host Service Registry
  • On the management part, to elaborate on the MEC Host support for Virtualized Infrastructure (and defined on MEC Host support for 3rd Party to provide its own Application and enable its Mangement from its own Management environment without and integration with the MEC Orchestrator.
  • If the aim/purpose of PCEI is to provide an Enablement "Enabler Layer" to briefly elaborate on the MNOs provided Capabilities through SEES/FMSS (in SCEF/NEF) to 3rd party ICPs/ISPs.
  • In order to provide a better understanding to the reader on the maturity/evolvement level of the PCEI Solution, to elaborate whether PCEI current Availability Configuration and or the Rel 4 proposed implementation is a "Demo", "Concept", "Commercial" deployment version and/or there is/are references.
  • The above remarks is also related to the Test Document part related to APIs (test) indicated as "work in progress".
  • Related to Latency in the defined 3GPP UCs ( as eMBB, URLLC, mIoT, V2X as with inidcated standard values for Slicing) is defined and published. It might be useful to add it to provide credibility that PCEI is aware of the required Latency requirements and therein able to contribute to be achieved. The IIoT (industry 4.0) within URLLC (for MCC/MCS - Mission Critical Communication/Mission Critical Services) in terms of Motion Control Discrete Automtion (for Robotics and Packaging) as well as Process Automation - Motion Control (for fluids, Gases, Electricity) is also defined/specified (even the manufacturing areas that shall be covered in terms of 30mx30mx10m and 100mx100mx30m. There is also support for 3GPP and non 3GPP access (3IWG and N3IWG) with ATSSS in order to comply with the QoS requirements for Service "Availability" and Service "Reliability" in MNOs Network.

...