Eclipse Community Forums: Eclipse Titan » Problem with built-in APER codec with F1AP interface

Help

Home

Home » Eclipse Projects » Eclipse Titan » Problem with built-in APER codec with F1AP interface

Show: Today's Messages :: Show Polls :: Message Navigator

Problem with built-in APER codec with F1AP interface [message #1867722]

Thu, 04 July 2024 14:57

Franciszek Maroszek

Messages: 2
Registered: July 2024

Junior Member

Hi,
We are using Eclipse Titan for TTCN-3 testing of our 5G CU product, mostly on NGAP, RRC and F1AP interfaces.
We've been using asn1c as a PER codec (as described here) but we decided to try switching when we noticed that the new Titan version has a built-in support.
It works ok for NGAP and RRC but we see some errors for F1AP Initial UL RRC Message Transfer - C-RNTI field gets lost.

Problematic message looks like this:

    template F1AP_PDU initialUlRRCMsg := {
        initiatingMessage := {
            procedureCode := id_InitialULRRCMessageTransfer,
            criticality := ignore,
            value_ := {
                InitialULRRCMessageTransfer := {
                protocolIEs := {
                    {
                    id := id_TransactionID,
                    criticality := ignore,
                    value_ := {
                        transactionID := 0
                    }
                    },
                    {
                    id := id_gNB_DU_UE_F1AP_ID,
                    criticality := reject,
                    value_ := {
                        gNB_DU_UE_F1AP_ID := 10
                    }
                    },
                    {
                    id := id_NRCGI,
                    criticality := reject,
                    value_ := {
                        nRCGI := {
                        pLMN_Identity := '00F110'O,
                        nRCellIdentity := '000000000000000000000000000001101100'B,
                        iE_Extensions := omit
                        }
                    }
                    },
                    {
                    id := id_C_RNTI,
                    criticality := reject,
                    value_ := {
                        c_RNTI := 5
                    }
                    },
                    {
                    id := id_RRCContainer,
                    criticality := reject,
                    value_ := {
                        rRCContainer := '0820000040A6'O
                    }
                    },
                    {
                    id := id_DUtoCURRCContainer,
                    criticality := reject,
                    value_ := {
                        dUtoCURRCContainer := '40008000'O
                    }
                    }
                }
                }
            }
        }
    };

What we would expect (decoding by Wireshark, Marben and our product built-in codec) would be:

'000b4037000006004e4002000000290002000a006f00090000f11000000006c0005f000300000500320007060820000040a6008000050440008000'O

but what we get is:

'000b4036000006004e4002000000290002000a006f00090000f11000000006c0005f0002000500320007060820000040a6008000050440008000'O

This is also marked as malformed by Wireshark and Marben.

I made a package with a sample test file and ASN files for demonstration, it's enclosed as a .zip.
Do you know what could be causing that? Is it related to issue #730 ?

Best Regards,
Franciszek Maroszek