[srslte-users] mme receives invalid QoS combination from srsenb/srsue

[alexander.serkin at gmail.com]

Hey Francisco

Thank you for the hint. I’ll probably do it later on.

Occasionally fixed that with QoS profile changing to

disabled preemption capability.

Preemption capability was enabled initially by HSS.

That is working perfect with release 15 simulating dual connectivity with new radio (5g nsa) which I’m finally able to check on my lab EPC. Great.

Thanks to developers!

 

Cheers,

Alex

 

From: Francisco Paisana <francisco at srs.io> 
Sent: Tuesday, May 25, 2021 8:12 PM
To: alexander.serkin at gmail.com
Cc: srslte-users <srslte-users at lists.softwareradiosystems.com>
Subject: Re: [srslte-users] mme receives invalid QoS combination from srsenb/srsue

 

Hey Alexander,

 

Either you disable the guaranteed bitrates request in the MME S1AP message, or in the rrc_bearer_cfg.cc, you disable the check if the QoS is supported. For the latter, I think it should be sufficient to comment out these lines:

if (req_bitrate > pbr) {
  logger->warning("Provided E-RAB id=%d QoS not supported (guaranteed bitrates)", erab_id);
  cause.set_radio_network().value = asn1::s1ap::cause_radio_network_opts::invalid_qos_combination;
  return SRSRAN_ERROR;
}

Regards,
Francisco

 

On Tue, May 25, 2021 at 2:43 PM <alexander.serkin at gmail.com <mailto:alexander.serkin at gmail.com> > wrote:

Dear colleagues

I upgraded to 21.04 with some issue I can't figure out. I use
srsue<zeromq>srsenb<>third party MME topology.

And it worked for me previously on 20.10. But now after attach accept
message of the following contents (10.20.1.4 - srsenb, 10.20.1.6 - MME):



Tuesday May 25 2021

<<<<OUTBOUND  From sessmgr:4 mme_msg_utils.c:9427 (Callid 00e53c8f)
16:13:20:235 Eventid:153002(3)

NAS Tx PDU, from 10.20.1.6:36412 <http://10.20.1.6:36412>  to 10.20.1.4:41950 <http://10.20.1.4:41950>  (80)



Non Access Stratum (NAS) (80 bytes)

       NAS_MSG_SECURITY_HDR_INTEGRITY_PROTECTED_CIPHERED(0x2)

         MAC = 0x48658704 

         NAS Count = 0x2

  EPS Mobility Management

    Protocol Discriminator

       EPS MOBILITY MANAGEMENT MESSAGES(0x7)

    Security Header Type

       NAS_MSG_SECURITY_HDR_PLAIN_NAS_MSG(0x0)

    Message Type

       ATTACH_ACCEPT(0x42)

    Result

       EPS ONLY(0x1)

    Spare-Half

      (0x0)

    T3412

      (0x1e)

    TAI

        TRACKING AREA LIST

        Type: 1  Length: 1

          ELEMENT 0: MNC[02] MCC[250] TAC[1]

    ESM Container

      EPS Session Management

        Protocol Discriminator

           EPS SESSION MANAGEMENT MESSAGES(0x2)

        EPS Bearer Id

          (0x5)

        Transaction Id

          (0x1)

        Message Type

           ACTIVATE_DFLT_BEARER_REQUEST(0xc1)

        EPS QoS

            QCI=7 

        APN

            gis.mnc002.mcc250.gprs 

        PDN Address

            PDN Address (IPv4 10.20.1.28))

        APN-AMBR

            DN-LNK-APN-AMBR= 256000 kbps (0xfe 0xfa)

            UP-LNK-APN-AMBR= 256000 kbps (0xfe 0xfa)

    EPS Mobile Identity

        GUTI

          PLMN

            (250:02)

          MME GROUP ID

            (0x8100)

          MME CODE

            (0x80)

          M-TMSI

            (0xc0000604)

    T3423

      (0x49)

    Equivalent PLMN List

        PLMN

          (250:02)



I'm getting "Invalid QoS Combination"  S1ap Radio Network Layer Cause in the
answer to initial context setup. 

What has changed, and how I can fix that minor problem?



Thank you!

Alex

_______________________________________________
srslte-users mailing list
srslte-users at lists.softwareradiosystems.com <mailto:srslte-users at lists.softwareradiosystems.com> 
https://lists.softwareradiosystems.com/mailman/listinfo/srslte-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20210525/6590ed44/attachment.htm>