Wireshark · Wireshark-dev: [Wireshark-dev] F1AP Messages are not getting dissected correctly.

[Simran Kumawat <kumawat.simran@xxxxxxxxxxxxx>]

Hi Sir/Ma'am,

This is Simran Kumawat, Project Associate at 5G-TestBed Project, IIT Hyderabad.
I am working on the F1AP interface currently, I observed a few things as mentioned below.
Wireshark is dissecting f1ap msgs like this -
1. Initiating Message ----------------------> Initiating Message
2. SuccessfulOutcome Message--------> Initiating Message
3. UnsuccessfulOutcome Message-----> SuccessfulOutcome Message
The information contained is also the same but the problem is  only at this moment. for example ,

wireshark is dissecting F1SetupResponse ------------> F1SetupRequest and  

                                      F1SetupFailure----------------> F1SetupResponse
with the same content. There is no problem in the code because after decoding at receiver side, I am printing the info contained in the packet.
I am attaching the wireshark capture for your reference and logs from sender and receiver side.

I request you to please check with the issue mentioned above.
In case of any query, please get back to me.

Thanks and Regards,
Simran Kumawat
Project Associate, 5G-TestBed
IITH 

Disclaimer:- The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this email. Please notify the sender immediately and destroy all copies of this message and any attachments. The views expressed in this E-mail message (including the enclosure/(s) or attachment/(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of IIT Hyderabad. Before opening any mail and attachments please check them for viruses, malware, and the sender email address is indeed from IITH domain. IITH does not accept any liability for malware infected mails.

 12-16-2020 13:13:34.245931 [ INFO ] | [gNB  ] | wn5gNrBsPsF1apTst.c +208 |  main    | Listening
 12-16-2020 13:13:38.655137 [ INFO ] | [gNB  ] | wn5gNrBsPsF1apTst.c +219 |  main    | Accepted
 12-16-2020 13:13:38.655151 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apSctpApi.c +237 |  wnF1apRecvSctpMsg | F1 SCTP succefully received msg
 12-16-2020 13:13:38.655154 [ INFO ] | [gNB  ] | wn5gNrBsPsF1apTst.c +228 |  main    | After SCTP received data is 40
 12-16-2020 13:13:38.655180 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1CDecoder.c +57 |  wnF1apDecodePdu | F1AP decoding successfull
UnsuccessfulOutcome ::= {
    procedureCode: 1
    criticality: 0 (reject)
    value: F1SetupFailure ::= {
        protocolIEs: ProtocolIE-Container ::= {
            F1SetupFailureIEs ::= {
                id: 78
                criticality: 0 (reject)
                value: 20
            }
            F1SetupFailureIEs ::= {
                id: 0
                criticality: 1 (ignore)
                value: 0 (unspecified)
            }
        }
    }
}
 12-16-2020 13:13:38.655200 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apHandler.c +4516 |  wnF1SetupFlr | TranscationID is 20
 12-16-2020 13:13:38.655204 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apHandler.c +4521 |  wnF1SetupFlr | radioNetwork is 0
 12-16-2020 13:13:38.655206 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apHandler.c +4523 |  wnF1SetupFlr | Transport is 0
 12-16-2020 13:13:38.655207 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apHandler.c +4525 |  wnF1SetupFlr | protocol is 0
 12-16-2020 13:13:38.655209 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apHandler.c +4527 |  wnF1SetupFlr | misc is 0
 12-16-2020 13:13:38.655281 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apSctpApi.c +237 |  wnF1apRecvSctpMsg | F1 SCTP succefully received msg

 12-16-2020 13:13:38.654944 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1CEncoder.c +56 |  wnF1EncodePdu | Encoded data is 18
 12-16-2020 13:13:38.654964 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apApi.c +2331 |  wnF1StupFail | F1AP | encoding successful
 12-16-2020 13:13:38.654977 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1CDecoder.c +58 |  wnF1apDecodePdu | F1AP decoding successfull
<F1AP-PDU>
    <unsuccessfulOutcome>
        <procedureCode>1</procedureCode>
        <criticality><reject/></criticality>
        <value>
            <F1SetupFailure>
                <protocolIEs>
                    <F1SetupFailureIEs>
                        <id>78</id>
                        <criticality><reject/></criticality>
                        <value>
                            <TransactionID>20</TransactionID>
                        </value>
                    </F1SetupFailureIEs>
                    <F1SetupFailureIEs>
                        <id>0</id>
                        <criticality><ignore/></criticality>
                        <value>
                            <Cause>
                                <radioNetwork><unspecified/></radioNetwork>
                            </Cause>
                        </value>
                    </F1SetupFailureIEs>
                </protocolIEs>
            </F1SetupFailure>
        </value>
    </unsuccessfulOutcome>
</F1AP-PDU>
 12-16-2020 13:13:38.655023 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apSctpApi.c +150 |  wnConnSocket | F1AP socket created successfully
 12-16-2020 13:13:38.655100 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apSctpApi.c +172 |  wnConnSocket | F1AP sock connected : 0 3

 12-16-2020 13:13:38.655115 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apSctpApi.c +200 |  wnSendF1Msg | F1AP | Send success
 12-16-2020 13:13:38.655118 [ INFO ] | [gNB  ] | ../csrc/wn5gNrBsPsF1apApi.c +2347 |  wnF1StupFail | SCTP Sending Successful
<F1AP-PDU>
    <unsuccessfulOutcome>
        <procedureCode>1</procedureCode>
        <criticality><reject/></criticality>
        <value>
            <F1SetupFailure>
                <protocolIEs>
                    <F1SetupFailureIEs>
                        <id>78</id>
                        <criticality><reject/></criticality>
                        <value>
                            <TransactionID>20</TransactionID>
                        </value>
                    </F1SetupFailureIEs>
                    <F1SetupFailureIEs>
                        <id>0</id>
                        <criticality><ignore/></criticality>
                        <value>
                            <Cause>
                                <radioNetwork><unspecified/></radioNetwork>
                            </Cause>
                        </value>
                    </F1SetupFailureIEs>
                </protocolIEs>
            </F1SetupFailure>
        </value>
    </unsuccessfulOutcome>
</F1AP-PDU>

Attachment: F1apMsg.pcapng
Description: Binary data