Cellular Network Infrastructure » Core Network (CN) » OsmoHNBGW

Implementation missing in hnbgw_rx_ue_register_req (HNBAP_UE_Identity_PR_iMEI, type=4).

If it is received, we should lookup contrext_ue based on known IMEIs.

It was seen in a osmo-hnbgw in a lab setup against a real hNodeb, MSC, etc.

received 30 bytes from client 
Decoding message HNBAP_UERegisterRequestIEs (hnbap_decoder.c:357) 
UE-REGISTER-REQ with unsupported UE Id type 4 

From wireshark:

UTRAN Iuh interface HNBAP signalling
    HNBAP-PDU: initiatingMessage (0)
        initiatingMessage
            procedureCode: id-UERegister (3)
            criticality: reject (0)
            value
                UERegisterRequest
                    protocolIEs: 3 items
                        Item 0: id-UE-Identity
                            ProtocolIE-Field
                                id: id-UE-Identity (5)
                                criticality: reject (0)
                                value
                                    UE-Identity: iMEI (3)
                                        iMEI: 3522241501421000 [bit length 60, 4 LSB pad bits]
                        Item 1: id-Registration-Cause
                            ProtocolIE-Field
                                id: id-Registration-Cause (12)
                                criticality: ignore (1)
                                value
                                    Registration-Cause: normal (1)
                        Item 2: id-UE-Capabilities
                            ProtocolIE-Field
                                id: id-UE-Capabilities (13)
                                criticality: reject (0)
                                value
                                    UE-Capabilities
                                        access-stratum-release-indicator: rel-6 (3)
                                        csg-capability: not-csg-capable (1)

Hexstream for the message: 0003001a00000300050009303522241501421000000c400140000d00010d