...
3. With regard to ETSI MEC GS 014 "UE Identity API" Sect. 5.1 p.7 indicates that it "has for "purpose
of the UE Identity feature is to allow UE specific traffic rules in the MEC system." Could you please
elaborate how the MEC Platform retrieves the UE type (is it using OMA IN ATI interrogation for
UE by IMEI & MAC as designed or set (e.g. LTE UE CAT 1-7) 12) in order to be able to assure that
the UE meets/fulfills the required Latency for specific Services as TSN, MCC/MCS, ProSe etc, .) is i
dentified identified so that the required Latency for the Application/Service is fulfulled? Ike A.
4. ETSI MEC is integrated with ETSI NFV via replacing the MEPM with MEP-V (as ETSI MEC is actually
implemented as a VNF) and with ETSI ZSM and OSM it is integrated on the ETSI MEC System Level via
the OSS and Orchestrator. How (which interface) on the ESTI MEC Host is used for
the use/inter-operability with the ETSI ENI API Broker? Ike A.