Accelerate3g5 -- neels » History » Version 5
neels, 03/02/2017 11:59 PM
| 1 | 1 | neels | h1. Accelerate3g5 -- neels |
|---|---|---|---|
| 2 | |||
| 3 | {{>toc}} |
||
| 4 | |||
| 5 | h2. Summary |
||
| 6 | |||
| 7 | Implement Osmocom 3G support integrated with the new libvlr, so that standard USIMs with full UMTS AKA can be used with the 3G OsmoMSC. |
||
| 8 | |||
| 9 | 2 | neels | h3. Participants |
| 10 | |||
| 11 | * Neels (nhofmeyr@sysmocom.de) |
||
| 12 | |||
| 13 | 1 | neels | h2. Details |
| 14 | |||
| 15 | For various reasons, the previously integrated HLR functionality is currently being split from OsmoNITB, on the "neels/vlr":http://git.osmocom.org/openbsc/log/?h=neels/vlr branch. UMTS AKA using the Milenage algorithm already works for 2G using that branch, but the "sysmocom/iu":http://git.osmocom.org/openbsc/log/?h=neels/vlr branch still lacks this capability. |
||
| 16 | |||
| 17 | Rebase the sysmocom/iu branch onto the neels/vlr branch and resolve all conflicts. Test and verify that 3G works with the sysmoUSIM-SJS1 using Milenage authentication. |
||
| 18 | |||
| 19 | Related issues are: #1595 #1711 #1593 |
||
| 20 | |||
| 21 | h2. Journal |
||
| 22 | |||
| 23 | _2017-02-28_ |
||
| 24 | A first @git rebase@ resulted in numerous conflicts. Starting to resolve... |
||
| 25 | |||
| 26 | 3 | neels | _2017-03-02_ |
| 27 | Conflicts have been resolved, but of course the result doesn't compile. |
||
| 28 | Fixing all the errors, and will then need to test+debug, and also review all patches in detail. |
||
| 29 | Rate counters and the logging context are at least incomplete, probably more details and corner cases. |
||
| 30 | 4 | neels | _later_ |
| 31 | The merged branch compiled. Now the msc_vlr unit tests fail and there are probably still many other errors to resolve. |
||
| 32 | 3 | neels | |
| 33 | 1 | neels | h2. Conclusions |
| 34 | |||
| 35 | 5 | neels | I thought that GERAN means exactly A-interface and UTRAN means Iu-interface. But there's also GERAN-over-Iu. |
| 36 | RAN is the radio technology, so GERAN _does_ mean 2G BTS, but A and Iu are just the interfaces that these can be controlled with. |
||
| 37 | An MSC may employ an Iu interface to talk to both GERAN and UTRAN radio technology infrastructure. |
||
| 38 | |||
| 39 | And I thought that UMTS means 3G means UTRAN, but UMTS is "just" the R99 (Release 1999) extension of the protocols. |
||
| 40 | UMTS is used in 3G/UTRAN, yes, but for example UMTS Authentication can be negotiated over 2G networks. I know now because I implemented it. |
||
| 41 | As soon as the MSC says it is R99 capable in the SI3 MSCR bit and the MS is operated with a USIM "replies" that it is R99 capable in the Classmark IEs sent during Location Updating, CM Service Request and Paging requests, both sides can/will authenticate using UMTS mutual authentication -- another prerequisite of course is that the HLR has UMTS authentication keys stored for this USIM. |
||
| 42 | |||
| 43 | _todo: have the same UMTS auth over actual UTRAN+Iu_ |
