linofex
commented
1 year ago Hi @juansebastiani2cat,
in response to the question: is it possible to instantiate the VoIP application into one of the MEC Hosts instead of the traditional server (As done in the examples)?
The answer is yes.
How to do that
The only constraint for deploying a MEC application in a MEC host is that its .ned module must implement the IMECApp module interface (other than the inet IApp). The latter has some parameters set by the VIM module of the MEC host to configure the addresses and ports. If you want make the VoIPReceiver App a MEC app you have only to create a .ned file like the following:
package simu5g.apps.mec.MECVoIPReceiver;
import inet.applications.contract.IApp;
import simu5g.nodes.mec.MECPlatform.IMECApp;
import simu5g.apps.voip.VoIPReceiver;
simple MECVoIPReceiverApp extends VoIPReceiver like IMECApp
{
parameters:
@display("i=block/app;is=s");
@class("VoIPReceiver");
int packetSize = default(10);
string interfaceTableModule = default("");
int mecAppIndex;
int mecAppId;
int localUePort;
localPort = localUePort; // VoIP receiver app must bind the socket to the port set by the VIM!
string mp1Address = default("");
int mp1Port = default(10021);
//resource required info
double requiredRam @unit("B");
double requiredDisk @unit("B");
double requiredCpu;
// IApp parameters
int timeToLive = default(-1); // if not -1, set the TTL (IPv4) or Hop Limit (IPv6) field of sent packets to this value
int dscp = default(-1); // if not -1, set the DSCP (IPv4/IPv6) field of sent packets to this value
int tos = default(-1); // if not -1, set the Type Of Service (IPv4) / Traffic Class (IPv6) field of sent packets to this value
bool logger = default(false);
gates:
input mePlatformIn;
output mePlatformOut;
}simple MECVoIPReceiverApp extends VoIPReceiver like IMECApp just creates a module that extends the VoipReceiver app with the IMECApp interface. Note the line (in this example) localPort = localUePort. It is necessary to force the VoipReceiver app to bind the socket (from its localPort parameter) with the value set by the VIM module of the MEC host (loalUePort). Otherwise, if more than one MECVoIPReceiverApp apps were deployed in the same MEC host they would use the same default port.
The .h/.cc files of the VoIPReceiver app will be used for the behavior of the app.
The .ned file is saved under apps/mec/MECVoIPReceiver folder (you can choose the folder you prefer).
Then you have to create the Application descriptor as for every MEC App you have. In the same way as for the WarningAlertApp.json, the MECVoIPReceiver.json file is:
{
"appDid" : "VOIPAPP",
"appName" : "MECVoIPReceiverApp",
"appProvider" : "simu5g.apps.mec.MECVoIPReceiver.MECVoIPReceiverApp",
"appInfoName" : "appInfoName_",
"appDescription" : "appDescription_",
"virtualComputeDescriptor" :{
"virtualDisk": 10,
"virtualCpu" : 1500,
"virtualMemory":10
}
}This should complete the operations for creating a MEC app from a standart tcp/ip app.
Best regards, Alessandro
juansebastiani2cat
giovanninardini
Ali-K-Abbas
Dear all,
I am working in a project with multiple MecHosts and a time sensitive application. Using as a base the simulation in singleMecHost.ned, I want to be able to measure the delay from the Car to each of the MEC Hosts. As some issues have suggested, the best method to measure the end-to-end delay is using a timestamp over a VoIP application (As the VoIP application example present in SIMU5G). I want to use this same method, but I'm a bit stuck in the implementation.
My question is, is it possible to instantiate the VoIP application into one of the MEC Hosts instead of the traditional server (As done in the examples)?
If so, could you guide me or provide me some example of how to do it?
Thanks in advance for your help.