RM520N-GL Ethernet PDU / TSN configuration on firmware RM520NGLAAR05A01M4G_01.300.01.300

IoT Modules 5G Module
1

Hello,

I am testing Ethernet PDU / TSN on a Quectel RM520N-GL module.

Firmware version:

RM520NGLAAR05A01M4G_01.300.01.300

My goal is to make the UE send a PDU Session Establishment Request with Ethernet PDU type, or understand the correct AT command sequence required to do that on this firmware.

Supported commands shown by the module

AT+QMAP=?

The output includes:

+QMAP: "ETH_PDU",("enable","disable")
+QMAP: "connect",(0-3),(0,1)
+QMAP: "MPDN_status"
+QMAP: "MPDN_rule",(0-3),(1-16),(0,2-255),(0-3),(0,1),<IPPT_info>

AT+QNWCFG=?

The output includes:

+QNWCFG: "eth_cfg",(0,1),(1,2)

Current modem state

AT+QMAP="ETH_PDU"
+QMAP: "ETH_PDU","enable"

AT+QNWCFG="eth_cfg"
+QNWCFG: "eth_cfg",0

AT+QWDSCFG="profile"
+QWDSCFG: "profile",1,"IP","tsn",0,0
+QWDSCFG: "profile",2,"IPV4V6","ims",0,0
+QWDSCFG: "profile",3,"IPV4V6","sos",0,0

Commands I tried

AT+CGDCONT=1,"ETH","tsn"

Result:

ERROR

AT+QWDSCFG="profile",1,"ETH","tsn",0,0

Result:

ERROR

AT+QMAP="ETH_PDU","enable"

Result:

OK

AT+QMAP="connect",0,1

In the failing case, result is:

ERROR

Behavior seen in signaling

On NGAP / NAS signaling trace, I can see:

  • successful registration

  • registration accept

  • registration complete

But in the failing Ethernet-PDU case, I do not see a PDU Session Establishment Request from the UE.

So it looks like the modem may be failing locally before it even sends the NAS request.

My questions

  1. What is the correct AT command sequence on firmware RM520NGLAAR05A01M4G_01.300.01.300 to make the module request an Ethernet PDU session?

  2. Is AT+QMAP="ETH_PDU","enable" alone sufficient, or is an additional command required?

  3. What is the meaning of:

    AT+QNWCFG="eth_cfg"
+QNWCFG: "eth_cfg",0

    and how should eth_cfg be configured for Ethernet PDU / 5G LAN?

  4. If AT+CGDCONT and AT+QWDSCFG="profile" do not accept "ETH", how is the Ethernet PDU type actually configured on this firmware?

  5. Does this firmware fully support user-configurable Ethernet PDU / TSN / 5G LAN through public AT commands?

If needed, I can also provide full AT logs and signaling traces.

Thank you.

2

Dear @zivl
Please refer to topis.
Modem Quectel RM520N-GL: Ethernet PDU support with WaveShare 5G M.2 TO Gigabit ETH support - IoT Modules / 5G Module - Quectel Forums

image
image1232×576 53.8 KB

3

Hi Silvia,

I followed the Ethernet PDU instructions from the forum on my module:

Quectel
RM520N-GL
Revision: RM520NGLAAR05A01M4G
Firmware: RM520NGLAAR05A01M4G_01.300.01.300

Could you please confirm whether RM520NGLAAR05A01M4G_01.300.01.300 is the correct firmware for Ethernet PDU on RM520N-GL?

Current configuration

AT+QMAP="ETH_PDU","enable"
AT+QNWCFG="eth_cfg",1,2
AT+QWDSCFG="profile",4,"Ethernet","tsn"
AT+QMAP="mpdn_rule",0,4,0,0,1
AT+QMAP="auto_connect",0,1

Readback:

AT+QMAP="ETH_PDU"
+QMAP: "ETH_PDU","enable"

AT+QNWCFG="eth_cfg"
+QNWCFG: "eth_cfg",1

AT+QWDSCFG="profile"
+QWDSCFG: "profile",1,"IP","internet",0,0
+QWDSCFG: "profile",2,"IPV4V6","ims",0,0
+QWDSCFG: "profile",3,"IPV4V6","sos",0,0
+QWDSCFG: "profile",4,"Ethernet","tsn",65535,65535

AT+QMAP="mpdn_rule"
+QMAP: "MPDN_rule",0,4,0,0,1
+QMAP: "MPDN_rule",1,0,0,0,0
+QMAP: "MPDN_rule",2,0,0,0,0
+QMAP: "MPDN_rule",3,0,0,0,0

Difference from the forum example

On my firmware:

AT+QMAP="mpdn_rule",1,4,0,0,1

returns ERROR.

But this works:

AT+QMAP="mpdn_rule",0,4,0,0,1

So on my build, rule 0 works, not rule 1.

Also:

AT+QMAP="connect",0,1

always returns ERROR.

Problem

The UE can register to 5G (AT+C5GREG? -> 0,1), but with the Ethernet profile configured, the UE never sends a PDU Session Establishment Request.

In signaling trace I see:

  • Registration Request

  • Authentication / Security

  • Registration Accept

  • Registration Complete

  • then normal UE context release

But no PDU Session Establishment Request after attach.

Questions

  1. Is RM520NGLAAR05A01M4G_01.300.01.300 the correct firmware for Ethernet PDU on RM520N-GL?

  2. On this firmware, is rule 0 the correct one for Ethernet PDU instead of rule 1?

  3. If AT+QMAP="connect",0,1 always returns ERROR, what is the correct way to trigger Ethernet PDU session establishment?

  4. Is AT+QNWCFG="eth_cfg",1,2 the correct required setting on this firmware?

  5. Should the UE request the Ethernet PDU session automatically after attach, or is host-side Ethernet traffic required to trigger it?

If needed, I can provide the signaling trace.

Thank you.