Changes between Version 121 and Version 122 of GENILTE/LTEDeployment


Ignore:
Timestamp:
06/22/17 17:03:14 (7 years ago)
Author:
hdempsey@bbn.com
Comment:

misc minor fixes

Legend:

Unmodified
Added
Removed
Modified
  • GENILTE/LTEDeployment

    v121 v122  
    391391
    392392== Populating the OAI Database ==
    393 The OAI ePC software delivers an SQL script to install database, which is run only once:
     393The OAI ePC software delivers an SQL script to install the database.  Run the script only once:
    394394{{{
    395395$ ~/openair-cn/scripts/run_hss -i ~/openair-cn/src/oai_hss/db/oai_db.sql
    396396}}}
    397397 
    398 The OAI ePC delivers a database with the following  tables: apn, mmeidentity, pdn, pgw and users. The Database definitions initially modified to include the BBN installation can found it this SQL dump file [https://raw.githubusercontent.com/GENI-NSF/geni-support/master/wireless/oai_db.sql  oai_db.sql]. The BBN installation used the existing Access Point Name (APN) "orbitA" which was entered in the Packet Data Network (PDN) table definitions.  Modifications were made to the OAI ePC database to add Rutgers UE devices. A SQL dump of the BBN OAI database including the Rutgers devices can be seen in the  [https://raw.githubusercontent.com/GENI-NSF/geni-support/master/wireless/oai_db-rutgers-devices.sql oai_db-rutgers-devices.sql] file.
    399 
    400 A ruby script [https://raw.githubusercontent.com/GENI-NSF/geni-support/master/wireless/fill_sql.rb fill_sql.rb ] was provided by Rutgers to make database changes for adding the mmeidentity entry for the user and pdn tables. Modifications were made to set the BBN realm, mme and hss values in the script:
     398The OAI ePC delivers a database with the following  tables: apn, mmeidentity, pdn, pgw and users. The database definitions that were initially modified to include the BBN installation can found it this SQL dump file:   [https://raw.githubusercontent.com/GENI-NSF/geni-support/master/wireless/oai_db.sql  oai_db.sql]. The BBN installation used the existing Access Point Name (APN) "orbitA," which was entered in the Packet Data Network (PDN) table definitions.  Modifications were also made to the OAI ePC database to add Rutgers UE devices. A SQL dump of the BBN OAI database including the Rutgers devices can be seen in the  [https://raw.githubusercontent.com/GENI-NSF/geni-support/master/wireless/oai_db-rutgers-devices.sql oai_db-rutgers-devices.sql] file.
     399
     400A Ruby script [https://raw.githubusercontent.com/GENI-NSF/geni-support/master/wireless/fill_sql.rb fill_sql.rb ] was provided by Rutgers to make database changes for adding the mmeidentity entry for the user and pdn tables. Modifications were made to set the BBN realm, mme and hss values in the script:
    401401{{{
    402402< realm = '.donotdelete.ch-geni-net.instageni.gpolab.bbn.com'
     
    438438Once the Base Station was configured and reachable, it was added to  [http://www.airspan.com/netspan/ NetSpan], an SNMP based Web interface tool by [http://www.airspan.com Airspan], which is used to manage  Radio Access Network elements in the RAN (4G & 5G) and Backhaul domains. The Rutgers !NetSpan installation was used in this effort and was accessible from BBN over the LTE Multipoint VLAN at this address location "{{{http://10.3.0.252}}}".
    439439
    440 This section captures the !NetSpan Configuration for the BBN base station, other site will have different Node Types, Radio Profiles and Network Profiles.  In particular for the Radio profile, the site's assigned frequency must be considered, more details in the Cell Radio Profile section below.
     440This section captures the !NetSpan Configuration for the BBN base station, other sites will have different Node Types, Radio Profiles and Network Profiles.  In particular for the Radio profile, the site's assigned frequency must be considered.  More details are provided in the Cell Radio Profile section below.
    441441 
    442442== Configure eNodeB Settings ==
    443443
    444 This captures the procedure used for creating the BBN eNodeB node entry in !NetSpan. It is assumed other site will use this as a reference, but keeping in mind that changes are required for your sites Node Types, Radio Profiles and Network Profiles.  Instructions below assume access to !Netspan.
     444This captures the procedure used for creating the BBN eNodeB node entry in !NetSpan. Other sites can use this configuration as a reference, but must change the Node Type, Radio Profile and Network Profile to be appropriate for their site.  Instructions below assume access to !Netspan.
    445445
    446446=== Select an eNodeB to Clone ===
    447447
    448 To access list of available nodes that can be cloned, select "Nodes" in the lower left corner home page.  Double click on "nodes" and a list of nodes appears in the main panel:
     448To access the list of available nodes that can be cloned, select "Nodes" in the lower left corner on the home page.  Double click on "nodes" and a list of nodes appears in the main panel:
    449449
    450450[[Image(NodesToChoose.jpeg)]]
    451451
    452452 
    453 On the resulting page, in the main panel a list of nodes is shown that can be used for duplication.  In the resulting list, double click on node to be cloned and in the resulting page rename the cloned node to use your site, in our case "BBN eNodeB" was used. Click "Validate" and then click "OK" to save new node.
     453On the resulting page, in the main panel, a list of nodes that can be used for duplication appears.  Double click on node from this list that will be cloned, and in the resulting page rename the cloned node to a name for your site.  For BBN, we used the name "BBN eNodeB."  Click "Validate" and then click "OK" to save the new node.
    454454
    455455
     
    462462=== Configure Your eNodeB Node ===
    463463
    464 Access node configuration details, by selecting "Nodes" in the lower left corner of the home page and a list of nodes will be shown in the main panel.  In our case we double click on the  "BBN eNodeB" entry. In the resulting page, select the "Provision" tab, scroll to the bottom of the page and click "Edit" to modify settings.  Following is a capture of the "BBN eNodeB" settings which use the Rutgers MMS and the BBN Cell Radio Profile:
     464To access node configuration details, select "Nodes" in the lower left corner of the home page, and then the main panel will display a list of nodes.   In our case, we double click on the  "BBN eNodeB" entry. In the resulting page, select the "Provision" tab, scroll to the bottom of the page and click "Edit" to modify settings.  Following is a capture of the "BBN eNodeB" settings, which use the Rutgers MMS and the BBN Cell Radio Profile:
    465465
    466466[[Image(BBN-eNodeB.jpeg)]]
    467467
    468468
    469 The "BBN_band-41" Cell Radio Profile was created for the BBN Base Station. Each site must create its own Cell Ratio Profile and requires that you first know the EUTRA Absolute radio-frequency channel number (EARFCN) assignment for your site. The [http://wimax.orbit-lab.org/wiki/aaOperations#OperationsObjectives Orbit-Lab Site Operation Resources] page provides a table of Sites with '''Lower Frequency (MHz)''' and '''Upper Frequency (MHz)''' allocated for that sites in the GENI LTE effort.  The BBN Base Station configured in this example has the Lower Frequency 2573 MHz and the Upper Frequency 2583 MHz with a 10 MHz range, therefore the '''Center Frequency''' to use 2578 MHz.
    470 
    471 To calculate the  EARFCN DL value for the BBN Cell Radio Profile a [http://niviuk.free.fr/lte_band.php LTE Frequency Calculator] was used and the '''Center Frequency''' 2578 MHz was entered in the [http://niviuk.free.fr/lte_band.php LTE Frequency Calculator] to determine the '''Band Value''' and '''EARFCN DL''' values to be used in our Radio Cell Profile:
     469The "BBN_band-41" Cell Radio Profile was created for the BBN Base Station. Each site must create its own Cell Radio Profile, which thus requires that you know the EUTRA Absolute radio-frequency channel number (EARFCN) assignment for your site. The [http://wimax.orbit-lab.org/wiki/aaOperations#OperationsObjectives Orbit-Lab Site Operation Resources] page provides a table of Sites with '''Lower Frequency (MHz)''' and '''Upper Frequency (MHz)''' allocated for that sites in the GENI LTE effort.  The BBN Base Station configured in this example has the Lower Frequency 2573 MHz and the Upper Frequency 2583 MHz with a 10 MHz range, therefore the '''Center Frequency''' to use 2578 MHz.
     470
     471To calculate the EARFCN DL value for the BBN Cell Radio Profile an [http://niviuk.free.fr/lte_band.php LTE Frequency Calculator] was used and the '''Center Frequency''' 2578 MHz was entered in the [http://niviuk.free.fr/lte_band.php LTE Frequency Calculator] to determine the '''Band Value''' and '''EARFCN DL''' values to be used in our Radio Cell Profile:
    472472
    473473[[Image(EARFCN.jpeg,65%)]]
    474474
    475475
    476 Next we insert the calculated Band and EARFCN DL values in the Cell Radio Profile. Note the EARFCN value is based on '''your Frequency'''.  Following is the BBN Cell Radio Profile:
     476After you have determined the right values for your site,  insert the calculated Band and EARFCN DL values in the Cell Radio Profile. Note the EARFCN value is based on '''your site frequency'''.  Following is the BBN Cell Radio Profile:
    477477
    478478[[Image(RadioCellProfile.jpeg)]]
    479479
    480480
    481 The Network Profile for BBN defined to use the BBN MME is captured here:
     481The Network Profile for the BBN site as defined to use the BBN MME is captured here:
    482482
    483483
     
    485485
    486486
    487 Note that some test runs used the MME at Rutgers, which includes these settings for the Network Profile using the Rutgers MME:
     487For some test runs, the BBN site used the MME at Rutgers, which includes these settings for the BBN site Network Profile using the Rutgers MME:
    488488
    489489[[Image(AmeriSoftNetworkProfile.jpeg)]]