Changes for examples/demo6/golang/README.md: 7 added lines, 7 removed lines.
Original line number
Diff line number
Diff line
@@ -80,15 +80,15 @@ After the login step, it is mandatory to request the list of available network s
### Get scenario description
This option (S) uses the index of the network scenario (starting from 0) to retrieve the description of the selected network scenario.
This option (S) uses the index of the network scenario (starting from 0 i.e. S 0) to retrieve the description of the selected network scenario.
### Activate a network scenario
This option (a) uses the index of the network scenario (starting from 0) to activate the selected network scenario. This command requests the MEC Sandbox instance to start all the MEC services attached to the activated network scenario.
This option (a) uses the index of the network scenario (starting from 0 i.e. a 0) to activate the selected network scenario. This command requests the MEC Sandbox instance to start all the MEC services attached to the activated network scenario.
### Deactivate a network scenario
This option (d) uses the index of the network scenario (starting from 0) to deactivate the selected network scenario. This command requests the MEC Sandbox instance to terminate all the MEC services attached to the activated network scenario.
This option (d) uses the index of the network scenario (starting from 0 i.e. d 0) to deactivate the selected network scenario. This command requests the MEC Sandbox instance to terminate all the MEC services attached to the activated network scenario.
### Get MEC services list
@@ -117,13 +117,13 @@ Theses commands provides some example of access to the MEC services available wi
- The option (y) sends a confirm-ready to the MEC platform to indicate a READY state.
- The option (r) registers the MEC application to the MEC platform (optional).
- The option (Rr) de-registers the MEC application from the MEC platform (optional).
- The option (R) de-registers the MEC application from the MEC platform (optional).
### MEC Service Managenment (MEC 011 service)
### Get V2X UU unicast setting (MEC 030 service)
- The option (Y) retrieves the UU Unicast settings from the MEC 030 service. To use it, the V2X network scenarion shall be activated (see [Activate a network scenario](#activate_a_network_scenario)).
- The option (Y) retrieves the UU Unicast settings from the MEC 030 service. To use it, the V2X network scenario shall be activated (see [Activate a network scenario](#activate_a_network_scenario)).
- The option (z) creates a subscription on V2X messages.
- The option (Z) deletes a subscription.
@@ -135,8 +135,8 @@ The option (Q) provides the demo6 application status. If a Login commands was ex
Current status: Sandbox: sbxqvgq4q4, appsInfo.Id: d75d8536-cf94-45a6-91a3-fc5b033f9630, Subscription: sub-wwJ_uzHOwqPntaia, Demo6 app not registered
```
In the example above, the MEC Platfor identifier is sbxqvgq4q4, the MEC application identifier is d75d8536-cf94-45a6-91a3-fc5b033f9630 and a subscription to the applicationTerminationNotifcation was created: sub-wwJ_uzHOwqPntaia. Note that the MEC application is not registered to the MEC Platform.
In the example above, the MEC Platform identifier is sbxqvgq4q4, the MEC application identifier is d75d8536-cf94-45a6-91a3-fc5b033f9630 and a subscription to the applicationTerminationNotifcation was created: sub-wwJ_uzHOwqPntaia. Note that the MEC application is not registered to the MEC Platform.
## Terminate the demo6 application
The command Quit (q) terminates the demo6 application. If a Login commands was executed, the termination process does the logout, deletes all subscriptions and de-registers the MEC appliction is a register was done.
The command Quit (q) terminates the demo6 application. If a Login commands was executed, the termination process does the logout, deletes all subscriptions, de-registers the MEC appliction if a register was done and terminates an existing MEC sandbox instance.
