Changes between Version 4 and Version 5 of OpenBSCWithSCCP

Show
Ignore:
Timestamp:
05/31/10 05:21:19 (3 months ago)
Author:
zecke2 (IP: 123.192.240.117)
Comment:

rewrite section... remove test plan, document how to create the branch, update the backlog.

Legend:

Unmodified
Added
Removed
Modified

  • OpenBSCWithSCCP

    v4 v5  
    33== Using OpenBSC in a real network == 
    44 
    5 The "holger/on-waves-msc-sccp" is implementing SCCP and the A-interface to hook OpenBSC into a "modern" IP based GSM network and communicate with another MSC. As part of this work a lite version of SCCP, GSM08.08 handling and various bugfixes were contributed to OpenBSC. Future work will create a GSM08 like API and move the MSC code inside OpenBSC over to use this API. 
     5The "on-waves/bsc-master" branch is implementing SCCP and the A-interface over IP to hook OpenBSC into a "modern" IP based GSM network. As part of this work a lite version of SCCP, GSM08.08 handling and various bugfixes were contributed to OpenBSC. Future work will create a GSM0808 like API and move the MSC code inside OpenBSC over to use this API. 
    66 
    7 === How to build === 
    8 TODO 
     7== How to build == 
    98 
    10 === How to run === 
    11 TODO 
     9In general this [wiki:Building_OpenBSC guide] applies to the on-waves/bsc-master branch. The only difference is that when building OpenBSC one needs to switch to the new branch. This can be done by invoking the below command: 
    1210 
    13 === Status === 
    14 TODO 
     11{{{git checkout -b on-waves/bsc-master origin/bsc-master}}} 
    1512 
    16 == SCCP == 
    17 === State of the implementation === 
    18 TODO 
    19  
    20 === SCCP over IP === 
    21 TODO explain the protocol header and such 
    22  
    23  
    24 == MGCP == 
    25 === State of the implementation === 
    26 TODO 
    27 === Explain innerworking === 
    28  
    29 == Manual tests == 
    30 === Success cases === 
    31  
    32 ==== Mobile Originated SMS ==== 
    33 The test is to send a SMS from the MS. Send a SMS to a given number and verify that the sending operationg is properly completed. 
    34  
    35 This will test opening the GSM04.08 layer3 connection (including RSL) with CM Service Request as the first message, the estblishment of SAPI=3 from the MS side. 
    36  
    37 ==== Mobile Originated Call ==== 
    38 The test is to dial from the MS. Dial a given number and verify that the call is established. 
    39  
    40 This will specially test the GSM08.08 Assignment Request and MGCP requests from the call-agent. 
    41  
    42 ==== Mobile Terminated SMS ==== 
    43 The test is to send a SMS to the MS. Send the SMS to the given IMSI. 
    44  
    45 This will test will test the PAGING Command, CipherMode Request, and then the first message with a SAPI=3 that will lead the BSC to queue and send a RSL request to open SAPI=3 and then continue. 
    46  
    47  
    48 === Failure cases === 
    49 TODO 
    50  
     13== Running the real bsc == 
     14After having build OpenBSC a new executable called '''bsc_msc_ip''' is installed. This executable is capable of hooking into a MSC supporting the SCCP over IP encapsulated in the IPA protocol and it is using a configuration based on the one of the '''bsc_hack''' with some additional extensions. The extensions are documented in the [wiki:bsc_hack_VTY VTY] documentation of the '''bsc_hack'''. The most important ones are the port and IP of the MSC. 
    5115 
    5216== Known work items/Backlog == 
    53   * Improve logging in OpenBSC to have filters.., etc, e.g. show me communication happening for this TMSI... 
    54   * Make mgcp and OpenBSC communicate with each other 
    55   * Fix SAPI/Channel release to be less bumpy 
    5617  * Handle GSM08.08 reset coming from the network 
    57   * Expire SCCP connections in case of inactivity 
     18  * Expire SCCP connections in case of inactivity from the network. 
     19  * Send SCCP Protocol Data Error messages to the network 
     20  * Implement more of GSM08.08, e.g. a handover