[srslte-users] Question about srsUE

[Junguk Cho]

If you send us the ue.log we can take a look a it.
-> Thanks. I have some issues in my experiments now. After fixing it, I
will send it to you.

Thanks,
Junguk

On Wed, Apr 11, 2018 at 10:20 AM, Ismael Gomez <
ismael.gomez at softwareradiosystems.com> wrote:

> If you send us the ue.log we can take a look a it.
>
> We tested exactly like you.
>
> On Wed, 11 Apr 2018 at 18:16 Junguk Cho <jmanbal at gmail.com> wrote:
>
>> Hi, Ismael.
>>
>> I tested it with controlling the transmission power of each eNBs which I
>> did it with a regular phone, but it disconnects the source eNB first and
>> connects to target eNB (not handovers).
>> I guess it might be power issues, I will dive into it more and get back
>> to you.
>>
>> Would I know how you tested S1 handover?
>>
>> Thanks,
>> Junguk
>>
>> On Wed, Apr 11, 2018 at 10:01 AM, Ismael Gomez <ismael.gomez@
>> softwareradiosystems.com> wrote:
>>
>>> Then you should do a HO just like you do with a regular phone: either
>>> change the transmission power of each eNodeB or move the UE
>>>
>>> On Wed, 11 Apr 2018 at 17:56 Junguk Cho <jmanbal at gmail.com> wrote:
>>>
>>>> Hi, Ismael.
>>>>
>>>> I use two commercial hardwares (small ip.access) and 3rd party EPC
>>>> which support S1-handover.
>>>>
>>>> Thanks,
>>>> Junguk
>>>>
>>>> On Wed, Apr 11, 2018 at 7:45 AM, Ismael Gomez <ismael.gomez@
>>>> softwareradiosystems.com> wrote:
>>>>
>>>>> What eNodeB do you have access to?
>>>>>
>>>>> On Tue, 10 Apr 2018 at 19:35 Junguk Cho <jmanbal at gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Based on release notes, srsUE supports X2/S1 handover.
>>>>>> If so, would you please explain how to test two handovers with srsUE?
>>>>>>
>>>>>> Thanks,
>>>>>> Junguk
>>>>>> _______________________________________________
>>>>>> srslte-users mailing list
>>>>>> srslte-users at lists.softwareradiosystems.com
>>>>>> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>>>>>
>>>>>
>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20180411/864329a6/attachment.htm>