Report bug fixes during TTF T043 validation (67b02090) · Commits · MEC - Multi-access Edge Computing / ETSI MEC Sandbox Frontend

README.md

+19 −3

Original line number	Diff line number	Diff line
		@@ -13,7 +13,10 @@ presented via OpenAPI compliant descriptions.
		MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and
		terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behaviour
		and capabilities of the Location (MEC013), Radio Network Information (MEC012), Traffic Management APIs (MEC015), Device Application Interface (MEC016),
		WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, V2X Information API (MEC030) service API and MEC Federation Service API (MEC040) service APIs. Such contextual information can offer
		WLAN Information (MEC028), Edge Platform Application Enablement (MEC011), Application Mobility (MEC021) service APIs, V2X Information API (MEC030) service API,
		MEC IoT API (MEC 033), MEC Federation Service API (MEC040) service APIs and Sensors-Sharing Services (MEC046) service APIs.
		MEC Sandbox provides also a support for Edge Native Connector (3GPP TS 29.222: 3rd Generation Partnership Project; Technical Specification GroupCore
		Network and Terminals; Common API Framework for 3GPP Northbound APIs). Such contextual information can offer
		significant differential performance for edge based MEC applications.
		Application Enablement (MEC011) and Application Mobility (MEC021) service APIs. Such contextual information can offer
		significant differential performance for edge based MEC applications.
		@@ -216,6 +219,19 @@ $ showmount -e
		- `vi ~/etsi-mec-sandbox-frontend/config/values/meep-prometheus.yaml`
		- Set `slack_api_url` to your slack channel webhook url
		- Set `channel` to your slack channel
		- Configure MQTT broker e.g `Mosquitto MQTT`:
		- Install mosquitto.
		- `sudo apt update`
		- `sudo apt install -y mosquitto`
		- Create a config file for mosquitto.
		- `echo -e "listener 1883\nallow_anonymous true" \| sudo tee /etc/mosquitto/conf.d/listener.conf > /dev/null`
		- Restart mosquitto.
		- `sudo systemctl restart mosquitto`
		- Configure vis and federation api to use mqtt broker
		- Set the `MEEP_BROKER` variable with the server IP (where Mosquitto is running) and port 1883 in the following two files:
		- `~/etsi-mec-sandbox/charts/meep-federation/values-template.yaml`
		- `~/etsi-mec-sandbox/charts/meep-vis/values-template.yaml`
		- Example: `MEEP_BROKER: mqtt://192.168.x.x:1882`
		1. Build & Deploy STF Frontend:
		- SSH to MEC Sandbox deployment VM
		- Build STF Frontend:
		@@ -332,5 +348,5 @@ The following procedure should be used to upgrade a running MEC Sandbox deployme
		## Licensing
		MEC Sandbox is a private repo with all rights reserved to ETSI.
		```
		Copyright (c) 2022 ETSI. All rights reserved.
		Copyright (c) 2022-2025 ETSI. All rights reserved.
		```

config/.meepctl-repocfg.yaml

+2 −2

Original line number	Diff line number	Diff line
		# Copyright (c) 2024 The AdvantEDGE Authors
		# Copyright (c) 2025 The AdvantEDGE Authors
		#
		# Licensed under the Apache License, Version 2.0 (the "License");
		# you may not use this file except in compliance with the License.
		@@ -12,7 +12,7 @@
		# See the License for the specific language governing permissions and
		# limitations under the License.

		version: 1.10.0
		version: 1.11.0
		repo:
		name: etsi-mec-sandbox

config/api/loc-serv-api.yaml

+10 −10

Original line number	Diff line number	Diff line
		@@ -375,7 +375,7 @@ paths:
		example:
		userAreaNotification:
		notificationType: 'UserAreaNotification'
		timestamp:
		timeStamp:
		seconds: 1673507343
		nanoSeconds": 0
		address: 'acr:10.0.0.1'
		@@ -697,7 +697,7 @@ paths:
		example:
		userDistanceNotification:
		notificationType: 'UserDistanceNotification'
		timestamp:
		timeStamp:
		seconds: 1673507343
		nanoSeconds": 0
		monitoredUsers:
		@@ -705,7 +705,7 @@ paths:
		address: 'acr:10.0.0.1'
		accessPointId: '001010000000000000000000000000001'
		zoneId: 'zone01'
		timestamp:
		timeStamp:
		seconds: 1673507343
		nanoSeconds": 0
		resourceURL: 'http://meAppServer.example.com/location/v3/queries/users'
		@@ -1033,7 +1033,7 @@ paths:
		example:
		userLocationEventNotification:
		notificationType: 'UserLocationEventNotification'
		timestamp:
		timeStamp:
		seconds: 1673507343
		nanoseconds: 0
		address: 'acr:10.0.0.1'
		@@ -1335,7 +1335,7 @@ paths:
		example:
		- zoneLocationEventNotification:
		notificationType: 'ZoneLocationEventNotification'
		timestamp:
		timeStamp:
		seconds: 1673507343
		nanoseconds: 0
		address: 'acr:10.0.0.1'
		@@ -2472,7 +2472,7 @@ components:
		type: integer
		x-etsi-mec-cardinality: '1'
		x-etsi-mec-origin-type: Enum_inlined
		timestamp:
		timeStamp:
		$ref: '#/components/schemas/TimeStamp'
		uncertaintyRadius:
		description: Present only if "shape" equals 6
		@@ -2812,7 +2812,7 @@ components:
		type: object

		TerminalDistance:
		description: A type containing information about the distance from a terminal to a location or between two terminals, in addition the accuracy and a timestamp of the information are provided.
		description: A type containing information about the distance from a terminal to a location or between two terminals, in addition the accuracy and a timeStamp of the information are provided.
		properties:
		accuracy:
		description: Accuracy of the provided distance in meters
		@@ -2824,7 +2824,7 @@ components:
		type: integer
		x-etsi-mec-cardinality: 1
		x-etsi-mec-origin-type: integer
		timestamp:
		timeStamp:
		$ref: '#/components/schemas/TimeStamp'
		required:
		- distance
		@@ -3084,7 +3084,7 @@ components:
		type: string
		x-etsi-mec-cardinality: '1'
		x-etsi-mec-origin-type: AnyURI
		timestamp:
		timeStamp:
		$ref: '#/components/schemas/TimeStamp'
		zoneId:
		description: The identity of the zone the user is currently within, see note 1.
		@@ -3096,7 +3096,7 @@ components:
		- accessPointId
		- zoneId
		- resourceURL
		- timestamp
		- timeStamp
		type: object
		x-etsi-notes: "NOTE 1:\tAs specified in [5], clause 5.2.2.7.\nNOTE 2: \tAs specified in [5], clause 5.2.2.5."
		x-etsi-ref: 6.2.2

js-apps/frontend/src/js/app-constants.js

+1 −1

Original line number	Diff line number	Diff line
		@@ -3,7 +3,7 @@
		*/

		// Version
		export const MEC_SANDBOX_VERSION = 'v1.10';
		export const MEC_SANDBOX_VERSION = 'v1.11-Beta';

		// Host
		export const HOST_PATH = location.origin;

js-apps/frontend/src/js/components/dialogs/detailed-data-dialog.js

+7 −1

Original line number	Diff line number	Diff line
		@@ -78,7 +78,7 @@ class DetailedDataDialog extends Component {

		mapService(loggerName) {
		//loggerName is a combination of loggerName and mep name
		let prefixes = ['meep-loc-serv', 'meep-federation', 'meep-rnis', 'meep-dai', 'meep-wais', 'meep-app-enablement', 'meep-ams', 'meep-vis', 'meep-tm'];
		let prefixes = ['meep-loc-serv', 'meep-federation', 'meep-rnis', 'meep-dai', 'meep-wais', 'meep-app-enablement', 'meep-ams', 'meep-iot', 'meep-sss', 'meep-vis', 'meep-tm'];
		let prefixStd = '';
		var prefix = '';
		for (var i = 0; i < prefixes.length; i++) {
		@@ -113,9 +113,15 @@ class DetailedDataDialog extends Component {
		case 'meep-vis':
		prefixStd = '030';
		break;
		case 'meep-iot':
		prefixStd = '033';
		break;
		case 'meep-federation':
		prefixStd = '040';
		break;
		case 'meep-sss':
		prefixStd = '046';
		break;
		default:
		prefixStd = 'N/A';
		}