Gemalto is now part of the Thales Group, find out more.

You are here

PLS8-E: incorrect IPv4 Address Count: 0 from MBIM IP_CONFIGURATION query for some APNs | Thales IoT Developer Community

April 24, 2019 - 5:48pm, 2417 views

Hi,

I noticed that PLS8-E mobiles with firmware 04.004 in MBIM **** incorrectly return IPv4 Address *****: 0 from BASIC_CONNECT IP_CONFIGURATION COMMAND_DONE like this

Mobile Broadband Interface Model
    Message Header
        Message Type: COMMAND_DONE (0x80000003)
        Message Length: 108
        Transaction Id: 3
    Fragment Header
        Total Fragments: 1
        Current Fragment: 0
    Device Service Id: UUID_BASIC_CONNECT (a289cc33-bcbb-8b4f-b6b0-133ec2aae6df)
    CID: IP_CONFIGURATION (15)
    Status: SUCCESS (0)
    Information Buffer Length: 60
    Information Buffer
        Session Id: 0
        IPv4 Configuration Available: 0x00000000
            .... .... .... .... .... .... .... ...0 = Address: Not available
            .... .... .... .... .... .... .... ..0. = Gateway: Not available
            .... .... .... .... .... .... .... .0.. = DNS Server: Not available
            .... .... .... .... .... .... .... 0... = MTU: Not available
        IPv6 Configuration Available: 0x00000000
            .... .... .... .... .... .... .... ...0 = Address: Not available
            .... .... .... .... .... .... .... ..0. = Gateway: Not available
            .... .... .... .... .... .... .... .0.. = DNS Server: Not available
            .... .... .... .... .... .... .... 0... = MTU: Not available
        IPv4 Address *****: 0
        IPv4 Address Offset: 0
        IPv6 Address *****: 0
        IPv6 Address Offset: 0
        IPv4 Gateway Offset: 0
        IPv6 Gateway Offset: 0
        IPv4 DNS Server *****: 0
        IPv4 DNS Server Offset: 0
        IPv6 DNS Server *****: 0
        IPv6 DNS Server Offset: 0
        IPv4 MTU: 0
        IPv6 MTU: 0

although an IPv4 address has been assigned by the network

GSM A-I/F DTAP - Activate PDP Context Accept
    Protocol Discriminator: GPRS session management messages (10)
        .... 1010 = Protocol discriminator: GPRS session management messages (0xa)
        1... .... = TI flag: allocated by receiver
        .000 .... = TIO: 0
    01.. .... = Sequence number: 1
    DTAP GPRS Session Management Message Type: Activate PDP Context Accept (0x42)
    LLC Service Access Point Identifier - Negotiated LLC SAPI
        0000 .... = Spare bit(s): 0
        .... 0011 = LLC SAPI: SAPI 3 (3)
    Quality Of Service - Negotiated QoS
        Length: 14
        00.. .... = Spare bit(s): 0
        ..01 0... = Quality of Service Delay class: Delay class 2 (2)
        .... .011 = Reliability class: Unacknowledged GTP/LLC, Ack RLC, Protected data (3)
        1001 .... = Peak throughput: Up to 256 000 octet/s (9)
        .... 0... = Spare bit(s): 0
        .... .010 = Precedence class: Normal priority (2)
        000. .... = Spare bit(s): 0
        ...1 1111 = Mean throughput: Best effort (31)
        011. .... = Traffic class: Interactive class (3)
        ...1 0... = Delivery order: Without delivery order ('no') (2)
        .... .011 = Delivery of erroneous SDUs: Erroneous SDUs are not delivered('No') (3)
        Maximum SDU size: 1500 octets (150)
        Maximum bitrate for uplink: 8640 kbps (254)
        Maximum bitrate for downlink: 8640 kbps (254)
        0111 .... = Residual Bit Error Rate (BER): 1*10-5 (7)
        .... 0100 = SDU error ratio: 1*10-4 (4)
        0000 00.. = Transfer delay: Subscribed transfer delay/reserved (0)
        .... ..10 = Traffic handling priority: Priority level 2 (2)
        Guaranteed bitrate for uplink: 0 kbps (255)
        Guaranteed bitrate for downlink: 0 kbps (255)
        000. .... = Spare bit(s): 0
        ...0 .... = Signalling indication: Not optimised for signalling traffic
        .... 0000 = Source statistics description: unknown (0)
        Maximum bitrate for downlink (extended): 42 Mbps (100)
        Guaranteed bitrate for downlink (extended): Use the value indicated by the Guaranteed bit rate for downlink (0)
    Radio Priority
        .... .010 = Radio Priority (PDP or SMS): priority level 2 (2)
    Packet Data Protocol Address - PDP address
        Element ID: 0x2b
        Length: 6
        0000 .... = Spare bit(s): 0
        .... 0001 = PDP type organization: IETF allocated address (1)
        PDP type number: IPv4 address (33)
        IPv4 address: 10.95.44.201
    Protocol Configuration Options
        Element ID: 0x27
        Length: 8
        [Link direction: Network to MS (1)]
        1... .... = Extension: True
        .... .000 = Configuration Protocol: PPP for use with IP PDP type or IP PDN type (0)
        Protocol or Container ID: Internet Protocol Control Protocol (0x8021)
            Length: 0x04 (4)
            PPP IP Control Protocol
                Code: Configuration Nak (3)
                Identifier: 0 (0x00)
                Length: 4

The problem only seems to happen when the network does not provide DNS servers (which is OK for a MMS APN).

Unfortunately this makes the PLS8-E in MBIM **** currently unusable for at least one MMS APN with our application.

Are there newer PLS8 firmware versions available where this problem has been fixed?

Regards,
Reinhard