Versions Compared

Key

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

...

      1.       In the ETSI MEC GS 021 Appliction Mobility API (Sect(s) 5.1 & 5.6, pgs 10 & 14), there is a

               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 (is/would that         be addressed in the coming oneM2M MEC WP?                                                                                                        Ike A.


    3. With regard to ETSI MEC GS 014 "UE Identity API" Sect. 5.1  p.7 indicates that it "has for "purpose

...

    with the ETSI ENI API Broker?                                                                                                                          Ike A.                                                    


5. With reference to ETSI MEC GS 013 Location API Sect 5.3 related to UE Location Subscription,

   please be so kind to elaborate on: UE equipment setting through IMEI/MAC management for Access and

   Services settings of the UE and SIM/UICC settings for Subscription Identity Management (MSISDN/IMSI/GUTI/SUPI/SUCI)

   also stored in the Network (3GPP Nodes HLR/HSS/UDR) a storing Subscription Data (and how is this

   handled by the ETSI MEC Architecture) and for some Services (e.g. ProSe/TSN/MCC/MCS) UE is defined as

   UE Relay and introduction of IP anchor node. Location on UE is also subject to Policy/Security/Storage and

   Privacy Management as it requires in the LCS Platform explicit User/Subscription consent (also subject to

   written consent for EU citizens/company employees through GDPR Article 4). With reference in Sect. 5.3.7 to

   ETSI MEC Application ability to obtain Radio Node Location through connection to 3GPP defined LSC Solution

   (with E-SMLC, GMLC and GIS (WGS 84 or NAD 83)), would you consider to elaborate on

    the ability to add on/elaborate on the ability to obtain/get access to 3GPP enhanced Positioning Methods

    as support to Satellite Positioning (GEO; LEO, MEO) and NR UL/DL EOTDA/OTDA, AoA, AoD (via NR/RAN PRS/SRS/RSRP)

   enabling Horizontal and Vertical Positioning for LCS Services.                                                                       Ike A.


View file
nameInput Ike A to ETSI MEC Dario S Walter F on 5G UP GW SNA 5G PALS April 2021.pdf
height250