Nr. Question Authors Name
1. In the ETSI MEC GS 021 Appliction Mobility API (Sect(s) 5.1 & 5.6, pgs 10 & 14), there is a
reference to transfer of "User's Context". Could you please elaborate on where the User profile
is retrieved from/stored/registered in the ETSI MEC and What is the definition of "Context"
and if it is aligned with "Context" in 3GPP 5G NDL and ETSI ENI? Ike A.
2. Do you have any co-operation/intention/plan(s) to incorporate the ETSI smartM2M ASD and
ETSI CIM NGSI-LD for using Semantics and OWL for using Data types/characteristics/granularity for
discovering and inter-operation of MEC Platform, Application(s) and AVT on varios ETSI MEC Hosts or
would you utlize it through the inter-operability with the oneM2M IoT Global Standard Rel 5? Ike A.
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 UE type (by IMEI & MAC as designed or set (e.g. CAT 1-7) for specific Services as
TSN, MCC/MCS, ProSe etc, ) is identified so that the required Latency for the Application/Service is fulfulled? Ike A.