|
1 | 1 | # Demo3 |
| 2 | +Demo3 scenario showcases the _Edge Platform Application Enablement_ and _Application Mobility_ edge services. |
2 | 3 |
|
3 | | -Demo 3 demonstrates how to use AdvantEDGE mec services showcasing Application Mobility Service (AMS) and Edge Application Enablement Service API. |
4 | | - |
5 | | -Demo 3 is a user MEC application that can be integrated within an AdvantEDGE scenario or used as an external application with [ETSI MEC Sandbox](https://try-mec.etsi.org/). |
6 | | - |
7 | | - |
8 | | - |
9 | | - |
10 | | -Demo3 MEC Application provides a dashboard GUI that allow a user to visualize interactions with MEC Service such as: |
11 | | - |
12 | | -1. MEC011 - Application Enablement and Service Enablement Services: |
13 | | - |
14 | | -- MEC Application registration/deregistration |
15 | | -- MEC Service discovery & offering |
16 | | -- Monitor event notifications about service and application availability |
17 | | - |
18 | | -2. Application Mobility Service provides support for relocation of user context and/or application instance between MEC hosts enabling: |
19 | | - |
20 | | -- MEC Assisted state transfer operationn |
21 | | - |
22 | | - |
23 | | - |
24 | | -## Getting Started: |
25 | | -Demo 3 can be used with an AdvantEDGE deployment or with the ETSI MEC Sandbox public deployment. |
26 | | -#### AdvantEDGE procedure overview |
27 | | -- Demo3 is built and dockerized using provided bash scripts |
28 | | -- Demo3 scenario (provided) is imported in AdvantEDGE |
29 | | -- Demo3 scenario is deployed on AdvantEDGE |
30 | | -#### MEC Sandbox procedure overview |
31 | | -- Demo3 is built using provided bash scripts |
32 | | -- Demo3 executable and frontend are copied to a common folder |
33 | | -- A MEC Sandbox is created and configured on ETSI MEC Sandbox [site](https://try-mec.etsi.org/) |
34 | | -- Demo3 configuration files (provided) are updated with your environment values |
35 | | -- Demo3 application is executed and accesses the ETSI MEC Sandbox |
36 | | - |
37 | | -### Using Demo3 with ETSI MEC Sandbox |
38 | | - |
39 | | -- Demo 3 does not have any prior knowledge or configuration information of the MEC services offered by the MEC platform |
40 | | - |
41 | | -The following steps need to be done prior to running demo 3 |
42 | | - |
43 | | -| Operation: | Notes: | |
44 | | -| --------- | ------ | |
45 | | -| 0a. Build demo3 server and frontend by invoking `Advantedge/examples/demo3/build-demo3.sh` | | |
46 | | -| 0b. Create work directories of your choice on the system of your choosing; we'll use `~/demo3-mep1` and `~/demo3-mep2` for this example and create a folder named `static` inside each one of the folders. The structure should look like this <br> |
47 | | - ├── demo3-mep1 |
48 | | - ├── static |
49 | | - ├── demo3-mep2 |
50 | | - ├── static |
51 | | -**IMPORTANT** ``` For this demo to work, the system running demo applications must be at a public IP address so that notifications sent by the ETSI MEC Sandbox can be received by demo applications. If the system is behind a firewall, ports will need to be opened. ``` |
52 | | - |
53 | | -| | | |
54 | | -| --------- | ------ | |
55 | | -| 0c. For each application instance, copy Demo3 server (`/AdvantEDGE/examples/demo3/bin/demo-server/demo-server`) in the work directories and copy Demo3 frontend bundle `/AdvantEDGE/example/demo3/bin/demo-frontend/*` in the static folder <br> The resulting should look like this <br> |
56 | | - ├── demo3-mep1 |
57 | | - ├── demo-server |
58 | | - ├── static |
59 | | - ├── bundle.css |
60 | | - ├── bundle.js |
61 | | - ├── img |
62 | | - ├── AdvantEDGE-logo-NoTagline_White_RGB.png |
63 | | - ├── ID-Icon-01-idcc.svg |
64 | | - ├── network.png |
65 | | - ├── index.html |
66 | | - ├── demo3-mep2 |
67 | | - ├── demo-server |
68 | | - ├── static |
69 | | - ├── bundle.css |
70 | | - ├── bundle.js |
71 | | - ├── img |
72 | | - ├── AdvantEDGE-logo-NoTagline_White_RGB.png |
73 | | - ├── ID-Icon-01-idcc.svg |
74 | | - ├── network.png |
75 | | - ├── index.html |
76 | | -| | | |
77 | | -| --------- | ------ | |
78 | | -| 1. Login via the MEC Sandbox frontend | | |
79 | | -| 2. Deploy a Dual MEP scenario and create two Application Instance IDs calles `demo3`, one on MEP1 and one on MEP2 respectively | | |
80 | | -| 3. Using provided `demo3-config.yaml` template, create a configuration file for each of the MEP1 and MEP2 applications and save each configuration files in their respective work folder created in step 0 <br> The resulting structure should look like this <br>` mode: 'sandbox'` - demo3 runs against ETSI MEC Sandbox <br> ` https: true ` - ETSI MEC sandbox uses https<br>`sandbox: 'https://try-mec.testfqdn.dev/mep1' `- URL to your sandbox, this info is available in the ETSI MEC Sandbox frontend <br> `mecplatform: 'mep1'`- the MEP where the instance is running, one of your application should be mep1 and the other mep2<br> `appid: '' ` - these are created in the ETSI MEC Sandbox frontend<br> ` localurl: 'http://'` - the public IP address where demo3 instance is running<br> `port: ''` - the port number that demo3 is listening on for incoming traffic<br> |
81 | | -| 4. Start the demo3 instances `./demo3-server demo3-config.yaml` -- after starting the servers, the frontend can be accessed at `<your-ip-address>:<your-port>` <br> From the frontend, demo3 can register to MEC011 and then devices present in the scenario can be added. |
82 | | - |
83 | | -Example of a configuration file |
84 | | -```sh .env |
85 | | -# This file defines the configuration of Demo3 edge application |
86 | | -# Required to define if application will run on MEC Sandbox or AdvantEDGE. Expected Values: sandbox or advantedge |
87 | | -mode: 'sandbox' |
88 | | -# Field to define MEC platform URL that app will run on. Example: http://{Mec_IP_Address}/{Sandbox_name}/{Mep_name}/ |
89 | | -https: true |
90 | | -sandbox: 'https://try-mec.testfqdn.dev/sbx-1234abcd/mep1' |
91 | | -# Field to define MEC platform name. Example: mep1 |
92 | | -mecplatform: 'mep1' |
93 | | -# Field to define user-application ID that can be generated using MEC Sandbox frontend |
94 | | -appid: 'cd9e4234-d7b7-4d49-be64-850ca436e24c' |
95 | | -# Local I.P address application will run on |
96 | | -localurl: 'http://1.2.3.4' |
97 | | -# Port number of user-application example: port: '8093' |
98 | | -port: '31111' |
99 | | - |
100 | | -``` |
101 | | - |
102 | | -### Build Demo 3 Server and Frontend |
103 | | - |
104 | | -``` shell |
105 | | -cd AdvantEdge/examples/demo3 |
106 | | -./build-demo3.sh |
107 | | -``` |
108 | | -### Using Demo3 with AdvantEDGE |
109 | | - |
110 | | -### Demo server & Demo frontend |
111 | | - |
112 | | -Demo server is a web server that will run internally in AdvantEdge as the backend of demo 3 application. The frontend is a dashboard to provide information on the MEC application instance in the scenario. One capability When the external UE moves in the network and transitions from one edge instance to another, the "UE state" (e.g. the counter value) is transferred using the application state transfer. On the demo server, it maintains a state of external UE as a counter that will continue incrementing (e.g. not reset to zero) when the UE moves in the network. |
113 | | - |
114 | | - |
115 | | - |
116 | | -The following steps need to be done prior to using this scenario |
117 | | - |
118 | | -#### Configure demo frontend and obtain binaries |
119 | | -| Operation | Notes | |
120 | | -| --------- | ------ | |
121 | | -| 0. Build and dockerize demo3 by invoking `AdvantEDGE/examples/demo3/build-demo3.sh` and `AdvantEDGE/examples/demo3/dockerize.sh`| | |
122 | | -| 1. Import provided `demo3-scenario.yaml` in AdvantEDGE and save it | | |
123 | | -| 2. Deploy `demo3-scenario` from the frontend | this scenario uses geo-localization, therefore it is necessary to provision a map as described [here](https://interdigitalinc.github.io/AdvantEDGE/docs/overview/features/gis/#map-provisioning) | |
124 | | - |
125 | | - |
126 | | -## Scenario composition |
127 | | - |
128 | | -The scenario is composed of two instance of same MEC applications running on two different mec platform |
129 | | - |
130 | | -MEC Application instance 1 on MEC Platform mep1 coverage area: zone01 (PoA:4g-macro-cell-1) |
131 | | -MEC Application instance 2 on MEC Platform mep2 coverage area: zone2, zone3 (PoA: 4g1 & wifi1) |
132 | | - |
133 | | -The scenario is composed of the following components: |
134 | | - |
135 | | -- 2 instance of the same edge application: demo-app and demo-app2 |
136 | | -- 1 MNO that has 3 Zones |
137 | | - - Zone1 has 1 Edge node |
138 | | - - Zone2&3 has 1 Edge node |
139 | | -- 3 UEs with pre-defined route will move interchangeably from mep 1 to mep2 |
| 4 | +For more details, check out the [Demo3 Documentation](https://interdigitalinc.github.io/AdvantEDGE/docs/usage/usage-demo3) |
0 commit comments