msg files: comments minor cleanup

Author: avarga

src/simu5g/apps/mec/RealTimeVideoStreamingApp/packets/RTVideoStreamingPackets.msg

@@ -27,8 +27,6 @@ class StartRealTimeVideoStreamingAppPacket extends RealTimeVideoStreamingAppPack
     int sessionId;
 }
 
-
-
 class StartSessionRealTimeVideoStreamingAppPacket extends RealTimeVideoStreamingAppPacket
 {
     int fps;

src/simu5g/apps/mec/RnisTestApp/packets/RnisTestAppPacket.msg

@@ -9,11 +9,6 @@
 // and cannot be removed from it.
 //
 
-
-//
-// RnisTestAppPacket used by UeRnisTestApp and MecRnisTestApp
-//
-
 import simu5g.mec.platform.MecPackets;
 
 cplusplus {{
@@ -27,6 +22,9 @@ class nlohmann::json
 
 namespace simu5g;
 
+//
+// RnisTestAppPacket used by UeRnisTestApp and MecRnisTestApp
+//
 class RnisTestAppPacket extends MecPacket
 {
 }

src/simu5g/apps/mec/WarningAlert/packets/WarningAlertPacket.msg

@@ -9,11 +9,6 @@
 // and cannot be removed from it.
 //
 
-
-//
-// IceAlert Packet used by UEIceAlertApp MEIceAlertApp and MEIceAlertService
-//
-
 import simu5g.mec.platform.MecPackets;
 
 namespace simu5g;

src/simu5g/apps/voip/VoipPacket.msg

@@ -9,17 +9,14 @@
 // and cannot be removed from it.
 //
 
-
-
-//
-// Packet used by the ~VoPSender and ~VoipReceiver modules.
-//
-
 import inet.common.INETDefs;
 import inet.common.packet.chunk.Chunk;
 
 namespace simu5g;
 
+//
+// Packet used by the ~VoPSender and ~VoipReceiver modules.
+//
 class VoipPacket extends inet::FieldsChunk {
     unsigned int IDtalk;
     unsigned int nframes;

src/simu5g/stack/mac/packet/LteMacSduRequest.msg

@@ -9,16 +9,16 @@
 // and cannot be removed from it.
 //
 
-//
-// This is the message that asks the RLC layer for a new MAC SDU.
-//
 import inet.common.INETDefs;
 import inet.common.packet.chunk.Chunk;
 
 import simu5g.common.LteCommon;
 
 namespace simu5g;
 
+//
+// This is the message that asks the RLC layer for a new MAC SDU.
+//
 class LteMacSduRequest extends inet::FieldsChunk
 {
     unsigned int sduSize;       // size of the requested SDU

src/simu5g/stack/rlc/packet/LteRlcDataPdu.msg

@@ -75,8 +75,7 @@ cplusplus(LteRlcDataPdu) {{
 }}
 
 //
-// @class LteRlcUmDataPdu
-// @brief Lte RLC UM Data Pdu
+// Lte RLC UM Data Pdu
 //
 // Define additional fields for UM PDU
 //
@@ -87,8 +86,7 @@ class LteRlcUmDataPdu extends LteRlcDataPdu
 };
 
 //
-// @class LteRlcAmDataPdu
-// @brief Lte RLC AM Data Pdu
+// Lte RLC AM Data Pdu.
 //
 // Define additional fields for AM PDU
 //

src/simu5g/stack/rlc/packet/LteRlcPdu.msg

@@ -9,17 +9,13 @@
 // and cannot be removed from it.
 //
 
-//
-// This is the RLC Pdu
-// flowing through LTE stack: basically
-// it contains the fields of a fragment
-// that receiver needs in order to
-// correctly decode the original packet
-//
-
 import inet.common.INETDefs;
 import inet.common.packet.chunk.Chunk;
 
+//
+// RLC PDU flowing through LTE stack. Contains the fields of a fragment that
+// the receiver needs in order to correctly decode the original packet.
+//
 class LteRlcPdu extends inet::FieldsChunk
 {
     // TODO: size 0

src/simu5g/stack/rlc/packet/LteRlcSdu.msg

@@ -9,15 +9,13 @@
 // and cannot be removed from it.
 //
 
+import inet.common.INETDefs;
+import inet.common.packet.chunk.Chunk;
 
 //
 // This is the RLC message flowing through LTE stack.
 // The relevant field is the Main Packet Sequence Number
 //
-
-import inet.common.INETDefs;
-import inet.common.packet.chunk.Chunk;
-
 class LteRlcSdu extends inet::FieldsChunk
 {
     // TODO: size 0

src/simu5g/x2/packet/X2ControlInfo.msg

@@ -29,18 +29,10 @@ class DestinationIdList { @existingClass; }
 // It is attached to the X2InformationElement and contains:
 // - The X2 ID of the source eNodeB
 // - The X2 IDs of the destination eNodeBs (as a user can send an InformationElement to several peers)
-// - a 'init' flag: if set, the X2 Manager uses the IE and the incoming gate to register the user module
-//                  into its internal data structures. This allows the X2 Manager to know which user is
-//                  connected to which gate, so as to forward messages coming from X2 to the correct
-//                  user module.
-
-//
-// @class LteX2ControlInfo
-//
-// This class contains:
-// - Source X2 ID
-// - List of destination IDs
-// - init flag
+// - 'init' flag: if set, the X2 Manager uses the IE and the incoming gate to register the user module
+//   into its internal data structures. This allows the X2 Manager to know which user is
+//   connected to which gate, so as to forward messages coming from X2 to the correct
+//   user module.
 //
 class X2ControlInfoTag extends inet::TagBase {
 	MacNodeId sourceId;                       // Source X2NodeId