FieldTests HAR2009 » History » Version 1
laforge, 02/19/2016 10:47 PM
har2009 page
1 | 1 | laforge | What I think we have to do before HAR is as follows: |
---|---|---|---|
2 | |||
3 | == Actual code == |
||
4 | |||
5 | === absolutely required === |
||
6 | |||
7 | * finish and test the SMS implementation [Harald] |
||
8 | * make sure we enable MS power control and impose a global limit of 100mW for the uplink (MS->BSC) direction by means of the MS POWER IE's and the BCCH information. That sounds like something for Dieter to figure out, especially since he has measurement equipment ;) |
||
9 | * test dual-BTS-on-single-E1-card config [Harald] |
||
10 | * up to now, we have only tested with two nanoBTS, not BS-11 ! |
||
11 | * test dual-TRX operation of BS-11 on OpenBSC [Stefan/Daniel, can you do that?] |
||
12 | * channel allocator can be tweaked to give 2nd TRX a preference for debugging |
||
13 | |||
14 | === optional === |
||
15 | |||
16 | * implement a 'provisioning mode' to OpenBSC that |
||
17 | * acccepts every new IMSI the first time we see it |
||
18 | * sends a SMS with a auth token to that mobile |
||
19 | * disconnects that mobile immediately |
||
20 | * implement a web site / cgi script |
||
21 | * once user enters correct tuple of ISMI + auth code, we |
||
22 | * assign him a number (user cannot choose, we assign) |
||
23 | * set authorized=1 in the sql table |
||
24 | * implement a web site bug tracker for user bug reports |
||
25 | * the should include detailed information about the phone model, his phone number and the exact timestamp, so we can match it in the pcap's |
||
26 | * add more introspection code for the VTY interface to explore the run-time data structures in OpenBSC |
||
27 | * implement different TCH assignment schemes (early / very early / OCASU) |
||
28 | * do we really want a SDCCH/8 or is SDCCH/4 for each BTS sufficient? |
||
29 | * some more testing with two BTS |
||
30 | * in case we call a user who is currently offline/busy, generate SMS about missed call and store it in the SMS table |
||
31 | * web interface ideas |
||
32 | * SMS gateway where people can send SMS from the web site |
||
33 | * SMS spam function for us in case we want to inform users about something |
||
34 | * simplistic phone book |
||
35 | * enhance vty interface with administrative functions such as |
||
36 | * ability to close arbitrary channels (i.e. terminate a call) |
||
37 | * ability to kick-ban a user out of the network |
||
38 | * set authorized=0 |
||
39 | * perform authentication procedure with reject at its end |
||
40 | * make sure we store all the 'this phone was registerd before to MCC/MNC/LAC' from the LOC UPD REQ data |
||
41 | * make sure we really store the classmark1/2/3 together with IMEI in SQL table |
||
42 | |||
43 | == Things to bring to the event == |
||
44 | |||
45 | * spectrum analyzer [from CCCB] |
||
46 | * stable OCXO reference to calibrate BS-11 internal clock |
||
47 | * this could be done before the event, but Harald has no precision clock source |
||
48 | * trace mobiles / monitor mode mobiles (if anyone has some) |
||
49 | * some poles to which we can mount the BS-11 ? |
||
50 | |||
51 | == Misc == |
||
52 | |||
53 | * draft 'usage terms & conditions' to be put on the registration web site and the HAR2009 wiki, indicating |
||
54 | * all signalling and traffic data will be stored for R&D purpose |
||
55 | * we do not employ authentication and/or encryption |
||
56 | * we do not provide any service guarantee |
||
57 | * this is for evaluation+testing only |
||
58 | * no handover/roaming and/or external calls |
||
59 | * no warranty for any damage to MS, SIM, ... |
||
60 | * IMSI/IMEI information will not be disclosed by us, but people can sniff it |