Site DB creation and updates

1. Site DB creationand updates 05/08/2006 by Performance Team

2. Introduction RF Design Data RFDS • Concept • - Tuning changes • - Design modyfication • Temporary solutions • - Consistency test results Access „Site DB” Asset3g RND CIQ • Interaction • Creation of “Site DB” and it’s maintenance require interaction between 3 main parties: Ericsson RF team (and its support from ELS, UTRAN & RF Performance Team) – Cingular/Designer RF team – Civil Vendor team. Those parties responsibilities for necessary actions have been color coded with legend on each of the flow charts.

3. Project Phase Three different flow charts are presented according to the three different phases of the tuning project when database creation/modification occurs. • Network Design Phase: during this phase, once the design is certified, the radio configuration site database is created. Once the master site database is generated the other radio configuration databases can be automatically generated. • RF Tuning Phase – Database Update: during the tuning phase many parameter/configuration changes occur typically. It is then fundamental to keep track of these changes and modify the relative master databases accordingly. • RF Tuning Phase – Database Alignment: as part of the tuning process consistency check is performed in order to verify the alignment of the master databases with the implemented network configuration. Eventual inconsistencies in the master databases are then restored (same as for eventual inconsistencies in network configuration).

4. List of Databases The following is the list of databases in use by RF engineers during the tuning project: • Asset “Site dB”:this radio configuration database consists of an Access database and will be referred to as the Master database for radio configuration for the specific market. RF market team lead is responsible for it. • Parameter Baseline:this parameter database consists of an Excel spreadsheet which contains all the Ericsson recommended parameter settings and the Cingular required parameter settings for the specific software release. The parameter baseline contains both radio and transport parameters and is valid for all the markets. TCM national team is responsible for it. • Local Market Exceptions: this parameter database consists of an Excel spreadsheet which contains a list of parameters in case their setting deviates from the national Parameter Baseline. It is used for keeping track of market specific parameter settings that are deviating from the national baseline and is also used as input for parameter consistency check. RF market team lead is responsible for it. Note: RF Parameter Baseline andLocal Market Exceptions databases represent the Master database for parameter setting, same as Asset “Site dB” represents the Master database for radio configuration. • RND-CIQ: this radio configuration database consists of an Excel spreadsheet which mirrors all the information contained in the Access “Site dB”. It is used for generating data script for site configuration and as input for radio configuration consistency check. RF market team lead is responsible for it. For more info on databases refer to proper section in Links_for_phase2_markets.doc

5. Network Design Phase, Radio Configuration Site DB creation Designer/Cingular creates Asset3g site DB and RFDSs Design Certification Update of Asset3g site DB/Simulations UTRAN neighbors IRAT neighbors Scrambling code plan Acceptance of the design NO RND CIQ Change to site configuration YES "RFDS handler" reads site config. info Access "Site DB" Update of RFDSs Civil vendor confirms that certified design can be implemented Asset3g site DB NO RFDSs At this stage at list preliminary RND CIQ has to be ready and handover to TCM group YES Site is constructed and integrated "As build" report and sweeps are issued

6. Network Design Phase, Radio Configuration Site DB creation • Main part of initial stage is creation of “certified design” and update of RFDSs (RF Data Sheets) containing the site configuration information, plumbing diagrams, ect. • Based on that info converted by “RFDS Handler” and additional inputs from RF Designers like “UTRAN NR list”, “IRAT NR list” and “Scrambling Code Plan” Access “Site DB” can be created. • When all the information in “Site DB” is correct the preliminary “RND CIQ” can be created. This is required to be handover to TCM grope some time before first sites will be integrated so they can prepare RNC scripts. • In parallel the Civil vendor should confirm that certified design can be implemented and in case there are some modification required they should be consulted with Cingular/Designer and Ericsson’s RF teams to come with final solution. • Final site configuration (confirmed by Civil vendor) should be updated in RFDSs (by Cingular/Designers) and in Access “Site DB” (by Ericsson market lead) which can result in version of RND CIQ. • When the sites are integrated and “call tested” RF team should receive “As build report” and sweeps from each site. Based on that info another round of updates should be performed to ensure the data base is as close to reality as possible. • In the same time Cingular’s/Designer’s responsibility is to update the RFDSs. • This way all the latest information can be stored in Access “Site DB” and whenever new RND CIQ is needed it can be done straight from the “Site DB”.

7. RF market lead RF performance team ELS Civil vendor Local Cingular/Designer RF Tuning Phase – Master Database Update RF Tuning recommendations Soft Change (e.g. Parameter or Neighbor) Phys Change (e.g. tilt, azimuth…) Request in RFCR Tool Physical Change ? YES Local Market Exceptions NO RND CIQ Civil vendor executes the change Implement Change Access "Site DB" Confirmation of changes is issued Confirmation of change is issued If required ACP simulations Is Parameter setting deviating from national Parameter Baseline ? Update Asset3g site DB NO e.g. Neighbor, primaryCPICHPower maximumTransmissionPower RFDSs YES

8. RF Tuning Phase – Master Database Update • It is very important the master database is always aligned with network configuration, especially during the tuning process where many changes occur very frequently. • The idea is to keep Access “Site DB” as a master radio configuration database for all updates so there is only one place where manual changes have to be done. Once the master database is updated all the other databases (e.g. RND-CIQ, Asset 3g) can be automatically generated. • In case the tuning process (or any other parallel process) requires a parameter setting which deviates from the national Parameter Baseline an additional market-level database, named Local Market Exceptions, has to be created and maintained. Note: in general, as a result of tuning, there are no parameters deviating from the RF Parameter Baseline (or very few) and typically they do not have to be frequently updated • When Ericsson’s RF team is issuing CR for soft or physical changes they should go through the RFCR tool to be registered and distributed to responsible parties for execution. • Every change requested by RF team should be confirmed upon its completion so Access “Site DB” (or eventually Local Market Exceptions dB) can be updated . All pending Change Requests can be tracked down in the RFCR tool. • From the updated Access “Site DB” new RND-CIQ can be produced whenever needed.

9. RF Tuning Phase – Master Database Alignment Consistency Check * List of inconsistencies Local Market Exceptions Change in the network? Parameter Baseline review of inconsistency and preparation final list of changes NO kgetAll - RNC "dump" YES Request in RFCR Tool RND CIQ physical change ? YES Access "Site DB" NO If required ACP simulations Civil vendor executes the change Implement Change Update Asset3g site DB Confirmation of changes is issued (before and after info) Confirmation of change is issued Is Parameter setting deviating from national Parameter Baseline ? NO YES

10. RF Tuning Phase – Master Database Alignment • During tuning process when many changes are requested on almost every site consistency check has to be performed frequently to confirm that the information in the master configuration databases (Access “Site dB” for radio configuration) is consistent with what is implemented in the network and also confirm that the parameters are set according to the Parameter Baseline database(and eventually according to Local Market Exceptions database) • The list of inconsistencies have to be reviewed by the RF engineers and UTRAN support team responsible to decide which are the inconsistencies in the network and which are the ones in the databases. • Three different type of Consistency Check are defined during the tuning process, each with different scope, capabilities and input requirements. For more information on Consistency Check refer to proper section in: Links_for_phase2_markets_PA1.doc