Commit c3ad7018 authored by Yann Garcia's avatar Yann Garcia
Browse files

Update docs

parent 432af9dc
Loading
Loading
Loading
Loading
+5 −4
Original line number Original line Diff line number Diff line
@@ -13,13 +13,13 @@ This guide contains step-by-step procedure for creating and configuring a UE app
# Definitions
# Definitions


- MEC application
- MEC application
This is an application or a MEC service hosted by a MEC platform
This is an application or a MEC service onboarded to the MEC platform


- User application (or UE Application)
- User application (or UE Application)
This is an application or a MEC service hosted by a user terminal (UE) described in a [network scenarion](./network-scenarios.md)
This is an application or a MEC service hosted by a user terminal (UE) described in a [network scenarion](./network-scenarios.md)


- MEC application instantiation
- MEC application instantiation
A UE Application can request instantiation of an onboarded 
A UE Application can request instantiation of an onboarded MEC application


# Creating a UE Application
# Creating a UE Application


@@ -58,10 +58,11 @@ Using a text editor, you need to update the networkLocations.physicalLocations.p


# Update MEEP-DAI micro-service
# Update MEEP-DAI micro-service


The MEEP-DAI micro service is acting as the xxx core element in a MEC architecture with some limitations:
The MEEP-DAI micro service is acting as the UALCMP entity in a MEC architecture (see MEC-003 Clause 6 Reference architecture) with some limitations:
1) MEC application are onboarded runtime when the MEC Sandbox is launched
1) MEC application are onboarded at runtime when the MEC Sandbox is launched
2) Only Mx2 interface (MEC-016) is supported
2) Only Mx2 interface (MEC-016) is supported
3) MEC-016 subscriptions and Notifications are not supported
3) MEC-016 subscriptions and Notifications are not supported
4) MEC-016 Location constraint look-up is not supported


## Technical details
## Technical details