<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>hi,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>i committed the SIM client process for layer23. it
turns reading and writing jobs (from and to SIM files) into APDUs. because the
SIM reader is not yet finished, it cannot be tested yet.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>after attaching the SIM card, a process in
mobile/subscriber.c will request all required files form that card before
starting the network selection process. (untested, as noted above)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>the mobility management is now cleaned up: TODO
comments in the source code are replaced by SIM update commands to the SIM
client.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>in order to make mobile application work with
public networks, we need to perform the following steps:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>- finish the SIM reader and interface in layer
1<BR>- add BTSAP interface to layer23<BR>- add measurement reports to both TCH
and SDCCH4/8 (*)<BR>- send updates for measurement report from layer23 via l23
api of layer 1<BR>- add crpyto-key request to layer 1 and l1-l2 interface
(dieter ?)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>* tests showed that the measurement report on
SDCCH4/8 is requred. if not <SPAN class=156182111-29082010>sent</SPAN>, the
network releases a call (cleanly) after the mobile stays for a some seconds on
an SDCCH4/8 (probably waiting for measurements, before <SPAN
class=156182111-29082010>completing the call</SPAN>). sending some dummy
measurements completed the call successfully.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT><FONT
face=Arial size=2></FONT><BR><FONT face=Arial size=2>beside that, the following
issues need to be solved soon, in order to make the layer 1 firmware usable
and stable:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>- additional structures for the libosmocore, see
</FONT><A href="http://home.eversberg.eu/osmocore.patch"><FONT face=Arial
size=2>http://home.eversberg.eu/osmocore.patch</FONT></A><BR><FONT face=Arial
size=2>- freeze of layer 1 after about 40-60 data messages, see </FONT><A
href="http://home.eversberg.eu/data.patch"><FONT face=Arial
size=2>http://home.eversberg.eu/data.patch</FONT></A><FONT face=Arial size=2>
for testing. after a few location updates firmware freezes. (the location<SPAN
class=156182111-29082010> </SPAN>update will fail, because the patch disturbs
location updating process, but the bug show up.)<BR>- syncing problem<BR>- clock
drifts away after sync<BR>- subchannels 4..8 of SDCCH/8</FONT></DIV>
<DIV><SPAN class=156182111-29082010><FONT face=Arial size=2>and
maybe</FONT></SPAN></DIV>
<DIV><SPAN class=156182111-29082010><FONT face=Arial size=2>- tch mode l1ctl
message to select signalling only / speech codec of TCH/F / TCH/H. (including
bearer capability processing in layer23)</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT><FONT
face=Arial size=2></FONT><BR><FONT face=Arial size=2>regards,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>andreas<BR></FONT></DIV></BODY></HTML>