Schedule data downlink for tramission on Gateway Server issue

Hi everyone,

I’m new to TTN and have build a LoraWAN Node with ESP32 Board (LMIC Library). I have a question about Schedule data downlink for tramission on Gateway Server. My Node only sends data to TTN, but sometime it receives Schedule data downlink for tramission on Gateway Server (RX Delay:5, althought i didn’t send a downlink message) and then automatically sends a message with Data rate, SNR, RSSI back (without payload?). Could anyone please explain for me, where the downlink message from is and why my Node received that as well as sended a uplink message without payload back? Thank you very much!!!
ttn

Downlink message, i also didn’t understand here UNCONFIRMED_DOWN, etc…

{
  "name": "ns.down.data.schedule.attempt",
  "time": "2022-11-21T14:59:15.214272006Z",
  "identifiers": [
    {
      "device_ids": {
        "device_id": "eui-70b3f",
        "application_ids": {
          "application_id": "esp32lo"
        },
        "dev_eui": "70D005205F",
        "join_eui": "70B3D12D2F",
        "dev_addr": "2612"
      }
    }
  ],
  "data": {
    "@type": "type.googleapis.com/ttn.lorawan.v3.DownlinkMessage",
    "raw_payload": "YBL1CyaFoAADUf8AAQ1i2rw=",
    "payload": {
      "m_hdr": {
        "m_type": "UNCONFIRMED_DOWN"
      },
      "mic": "DWLavA==",
      "mac_payload": {
        "f_hdr": {
          "dev_addr": "26012",
          "f_ctrl": {
            "adr": true
          },
          "f_cnt": 160,
          "f_opts": "A1H/AAE="
        },
        "full_f_cnt": 160
      }
    },
    "request": {
      "downlink_paths": [
        {
          "uplink_token": "CiYKJAoYc3RhZHRibAxEghwdv8AVgUIdBCLrMOyARoMCMKk7psGEMu3mPgCIPi1kN7y1BEqDAjCpO6bBhDA4sLdAg=="
        },
        {
          "uplink_token": "CiYKJAoYc3RhZHRib25uLTA0Eghwdv8AVgUJbBDzzf+DBxoMCMKk7psGEJOStfcCILjK+Jz3sisqDAjCpO6bBhDA4sLdAg=="
        },
        {
          "uplink_token": "CiYKJAoYc3RhZHRib25uLXN3YiEghwdv8AVgUGkhDj9ZCTBhoMCMKk7psGEIThz/MCILiNmLyFus0BKgwIwqTumwYQwOLC3QI="
        },
        {
          "uplink_token": "CiYKJAoYc3RhZHRib25uLXN3Yi1nhwdv8AVgUJaRDrm9tFGgwIwqTumwYQ27D88gIg+LvR0KD2VyoMCMKk7psGEMDiwt0C"
        }
      ],
      "rx1_delay": 5,
      "rx1_data_rate": {
        "lora": {
          "bandwidth": 125000,
          "spreading_factor": 7,
          "coding_rate": "4/5"
        }
      },
      "rx1_frequency": "867300000",
      "rx2_data_rate": {
        "lora": {
          "bandwidth": 125000,
          "spreading_factor": 9,
          "coding_rate": "4/5"
        }
      },
      "rx2_frequency": "869525000",
      "priority": "HIGHEST",
      "frequency_plan_id": "EU_863_870_TTN"
    },
    "correlation_ids": [
      "gs:conn:01GJ1XRT1RGS7J3CJF0NRCBRG6",
      "gs:up:host:01GJ1XRT22T86161PJRCN95RXR",
      "gs:uplink:01GJDB6N6TK0E63M2CZ1EMAEWS",
      "ns:downlink:01GJDB6NMEQ8NY6ZXJAN7KK3FX",
      "ns:transmission:01GJDB6NMEW4HVWDBM43N71WCN",
      "ns:uplink:01GJDB6N6VSSYC5NZH6X8G4FC6",
      "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01GJDB6N6T2PQSMTSC7TP3CQ58"
    ]
  },
  "correlation_ids": [
    "gs:conn:01GJ1XRT1RGS7J3CJF0NRCBRG6",
    "gs:up:host:01GJ1XRT22T86161PJRCN95RXR",
    "gs:uplink:01GJDB6N6TK0E63M2CZ1EMAEWS",
    "ns:downlink:01GJDB6NMEQ8NY6ZXJAN7KK3FX",
    "ns:transmission:01GJDB6NMEW4HVWDBM43N71WCN",
    "ns:uplink:01GJDB6N6VSSYC5NZH6X8G4FC6",
    "rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01GJDB6N6T2PQSMTSC7TP3CQ58"
  ],
  "origin": "ip-10-100-5-146.eu-west-1.compute.internal",
  "context": {
    "tenant-id": "CgN0dG4="
  },
  "visibility": {
    "rights": [
      "RIGHT_APPLICATION_TRAFFIC_READ"
    ]
  },
  "unique_id": "01GJDB6NME1TCAXWWZRX3041KK"
}

The LNS may send your node MAC commands to configure the device and/or optimise network behaviour. Often the Node will be required to acknowledge receipt and confirm acceptance and appropriate action or reject LNS requests… would need more detail before we could say more…

Have you edited the above? Some info e.g. the DevAddr looks wrong/short/inconsistent etc.

How long have you got - because this may take a while. No, wait, read this:

Section 5 onwards!