Quectel modem internal data diagnosis

Technical Subjects Driver
1

Hi Quectel Support Team and community,

I am a graduate student of the wireless cybersecurity lab, working on a 5G O-RAN testbed using OpenAirInterface with a Quectel RM500Q-GL modem connected to an Ubuntu PC as the UE. I observed certain end-to-end performance degradation under some 5G security configurations and would like to further diagnose whether the issue is related to the UE side, especially the internal data path of the RM500Q-GL. I have checked basic modem and network status using AT commands, but the available information is still coarse-grained and does not expose detailed user-plane behavior such as packet processing delay, buffering, queuing delay, or modem-side data path delay. I have also tried using the DM port with QLog to collect QMDL files, and I would like to confirm whether QLog/QMDL and QXDM are the right tools for this purpose.

I have a few questions:

  1. Does a QMDL file collected by QLog contain internal modem information related to user plane data processing, such as packet processing delay, buffering, or queuing delay?

  2. If this information is available, can QXDM identify it precisely? Are there specific log masks, diagnostic profiles, or views that should be used for RM500Q-GL user plane analysis?

  3. Besides QXDM, are there any Quectel or Qualcomm tools that can help diagnose the internal user plane data path of the RM500Q-GL?

  4. Can QXDM monitor this diagnostic information in real time when the DM port is enabled?

  5. When collecting QMDL files, I need to stop ModemManager using pkill ModemManager to make QLog collection stable. However, doing this disconnects the Ubuntu UE from active traffic, such as live YouTube video. In this case, would the collected QMDL file still reflect the actual user plane traffic, or would it only capture the modem state after the data connection has already been interrupted?

Could QLog/QMDL and QXDM provide visibility into the RM500Q-GL internal data path, especially packet processing delay, buffering, and queuing delay? Any recommended logging configuration or alternative diagnostic method would be greatly appreciated.

Thank you very much for any guidance or suggestions.