WIP / RFC for pysim 'next generation;' aka pysim-shell

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/simtrace@lists.osmocom.org/.

bryan coxwell bryancoxwell at gmail.com
Fri Jan 15 00:59:04 UTC 2021


Sounds good to me. 51.011 looks to be unchanged, which I guess is expected. Working on updating 31.102 now.

Thanks,

Bryan Coxwell

> On Jan 11, 2021, at 8:10 AM, Harald Welte <laforge at gnumonks.org> wrote:
> 
> Hi Bryan,
> 
>> On Sat, Jan 09, 2021 at 10:00:58AM -0500, bryan coxwell wrote:
>> I think this is a great idea and I'd love to help out, but I'm new to
>> working on open source projects. What's the best way for me to get started
>> in a way that would be helpful?
> 
> thanks for reaching out.  By now most of the APIs/architecture is sorted
> out, so you could
> 
> a) make sure that ts_51_011.py (sim) / ts_31_102.py (usim) / ts_31_103.py (isim)
>   contain class definitions for all of the files specified in the latest Release 16
>   3GPP specifications
> 
> b) write encoder and decoder methods within the EF classes for the various files
>   of interest.  See the EF_IMSI() as an example. The Decoder method should return
>   a python dict (possibly a hierarchy of dicts) and return the binary representation,
>   while the encoder method should take the dict and produce the binary representation.
> 
> Regards,
>    Harald
> -- 
> - Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the simtrace mailing list