Initial web server implementation

common/utils/websrv/helpfiles/cmd_channelmod_show_channelid.html

@@ -0,0 +1 @@
+This option asks for a model id and lists the parameters of this model.  Some parameters can be then modified

common/utils/websrv/helpfiles/cmd_channelmod_show_current.html

@@ -0,0 +1 @@
+When a oai component, as the rf simulator, instanciates a channel model, the instanciation is added in the list of current models. The id of the instanciation is used when using the "show channelid" option. 

common/utils/websrv/helpfiles/cmd_channelmod_show_predef.html

@@ -0,0 +1 @@
+Predefined channel model are a set of modelisation algorithm's, identified by a name, available in oai code.

common/utils/websrv/helpfiles/rfsimu_show_models_algorithm.html

@@ -0,0 +1 @@
+Available channel modelisation algorithm's can be listed using the "channelmod"/"show predef" command. A more convenient mechanism to select this will be implemented in a next version.

common/utils/websrv/helpfiles/rfsimu_show_models_model_index.html

@@ -0,0 +1 @@
+The model index can be used to modify a model parameter, using the "channelmod"/"show channelid" commands

common/utils/websrv/helpfiles/rfsimu_show_models_model_name.html

@@ -0,0 +1 @@
+Models parameters are defined in the oai configuration file under the section "channelmod.<channel list>". <channel list> describes the parameters for each <model name>. Several <channel list> can be defined, the loaded list is defined by the "channelmod.modellist" parameter. Model names are defined by the channel modelisation "user": for example the model "rfsmu_channel_ue0" is applied by the gNB rfsimulator on the signal received from ue0, the first connecet UE. 

common/utils/websrv/helpfiles/rfsimu_show_models_module_owner.html

@@ -0,0 +1 @@
+When the rfsimulator is effectively using a channel model to modify a received signal he becomes the owner of that model.

common/utils/websrv/helpfiles/scope_control_dataack.html

@@ -0,0 +1 @@
+when enabled, back-end will stop sending data when too much data have not been acknowledge by the frontend. Currently the back-end limits to 200 the number of data messages waitting for ack.

common/utils/websrv/helpfiles/softmodem_show_threadsched_nice.html

@@ -0,0 +1 @@
+Nice value, relevant for other and batch scheduling can be changed via the "oai priority" field

common/utils/websrv/helpfiles/softmodem_show_threadsched_oai_priority.html

@@ -0,0 +1,7 @@
+the oai priority field is used to provide the linux scheduling mode, priority and nice value in a single field.
+Priority value is mapped to linux scheduling mode, priority and nice as listed below:
+  -101 to -199: real time, Round-Robin 1 to 99
+  -1 to -99   : real time, fifo 1 to 99
+  0 to 39     : time sharing, nice value -20 to 19
+  40 to 79    : batch, nice value -20 to 19
+  >80         : idle

common/utils/websrv/helpfiles/softmodem_show_threadsched_priority.html

@@ -0,0 +1 @@
+Linux priority field, relevant for real-time scheduling mode (Round-Robin or fifo) can be modified using the "oai priority" field

common/utils/websrv/helpfiles/softmodem_show_threadsched_sched_policy.html

@@ -0,0 +1 @@
+scheduling policy can be modified using the "oai priority" field.