[srslte-users] srsEPC multiple SIM with same IMSI

laurent laurent.thomas at open-cells.com
Fri Dec 7 13:35:40 UTC 2018


Hi,

The 3GPP standard base is a uniq IMSI per connected device.

By this way, it is possible to accept incoming calls, paging, ...

it is also identify a subscription, so a commercial contract with the 
customer.

Regards,

Laurent

On 07/12/2018 12:09, Ignas Jarusevicius wrote:
> Hi Pedro,
>
> Thank you for your answers.
>
> The SIM's with same IMSI use XOR algorithm.
>
> Regards,
> Ignas
>
> On 2018-12-07 12:56, Pedro Alvarez wrote:
>> Hi Ignas --
>>
>> See my reply inline:
>>
>> On Fri, Dec 7, 2018 at 8:00 AM Ignas Jarusevicius
>> <i.jarusevicius at limemicro.com> wrote:
>>> Hello,
>>>
>>> I have multiple test SIM cards with same IMSI/keys. Does srsEPC support
>>> connection of multiple UEs with the same IMSI? From my initial testing
>>> it seems that the second UE (with same IMSI) is unable connect once one
>>> is connected.
>> This is not a supported feature at the moment. This is probably not
>> very hard to implement, but I won't have the time to look into this
>> for a while.
>> I'll try to get a look at this at the end of next week, just to see
>> how much work is involved. Just to be clear, these SIM's use XOR as
>> the authentication algorithm, correct?
>>
>>> Also, some time ago Pedro sent me a patch to make srsEPC work with sony
>>> Xperia F3111 phones:
>>>
>>>> diff --git a/lib/src/asn1/liblte_mme.cc b/lib/src/asn1/liblte_mme.cc
>>>> index 5cb00e5..59a86d9 100644
>>>> --- a/lib/src/asn1/liblte_mme.cc
>>>> +++ b/lib/src/asn1/liblte_mme.cc
>>>> @@ -320,7 +320,7 @@ LIBLTE_ERROR_ENUM
>>>> liblte_mme_pack_mobile_id_ie(LIBLTE_MME_MOBILE_ID_STRUCT  *mob
>>>>               odd = false;
>>>>           }else if(LIBLTE_MME_MOBILE_ID_TYPE_TMSI ==
>>>> mobile_id->type_of_id){
>>>>               id32 = mobile_id->tmsi;
>>>> -            length = 4;
>>>> +            length = 5;
>>>>               odd = false;
>>>>           }
>>>>           }else{
>>> However, it is still not in master. Is there a reason why it is not
>>> included? Does it cause issues for others devices?
>> Not sure why this didn't get into master. When I was trying to debug
>> the Xperia issue I tried multiple different things that In the end had
>> nothing to do with the actual issue.
>> When merging the actual solution back into next I probably just forgot
>> to add this part. Sorry about that, it's in next now and will be in
>> master for the next release.
>>
>>> Regards,
>>> Ignas
>> Cheers,
>> Pedro
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: laurent_thomas.vcf
Type: text/x-vcard
Size: 309 bytes
Desc: not available
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20181207/6f5c0fd8/attachment.vcf>


More information about the srsran-users mailing list