Received ADS-B TC=31 message with non-existent version 3?
I've decoded the message with my own decoder. I don't claim it is bug free, but it is designed to follow the 1090ES MOPS (ADS-B Minimum Operational Performance Standards) very closely and gives warnings when messages deviate from the standard. I forced decoding conforming to version 2 of the MOPS, which is the latest standard. 

HEX: 8DAE022EF8000000206143635C24
Aircraft Operational status message (airborne format)
    Capability Class:
        TCAS op.          false
        1090ES IN         false
        Reserved [13,14]      0
        ARV rep. cap.     false
        TS report cap.    false
        TC rep. cap. lvl      0
        UAT IN            false
        ADS-R rsvd flag   false
        Reserved              0
    Airborne Operational Mode (OM)
        TCAS RA active    false
        IDENT             false
        Reserved [ATC]    false
        Single Antenna    false
        SDA               0
        Reserved [33-40]  32
     MOPS version     3
     NIC supp. A      false
     NACp             1
     GVA              1
     SIL              0
     SIL supp.        true
     NIC baro         0
     Heading ref.     True North
     Reserved [56]    true


The 1090ES MOPS version is indeed indicated as version 3, which is not yet published.
Also, the ME-bits 35 and 56 are set to 1. In version 2 of the 1090ES MOPS these are reserved bits, so they shall be 0. 

Version 3 of the 1090ES MOPS is not yet published, so transponders should not use it. 

Perhaps these messages are from an experimental transponder, which does not conform to the MOPS.