ly in the prelaunch phase when new sites are integrated in order to verify that launched sites have correct parameters and avoid the negative impact of configuration errors. Checks should also be done prior to any optimisation activities or field test measurements. Actual Versus Default Parameter Values Most RAN parameters are set to default values in prelaunch networks. The actual values in the network should follow the default parameter values set. The default values are set according to operator strategy, network layout and available resources. Scrambling Code Plan Audit The main target of scrambling code planning is to ensure that the same scrambling code is not used in cells close to each other on the same carrier frequency. This is required to ensure that cells with the same scrambling code are not included in a combination of neighbours that an RNC sends to a UE from the neighbour lists that belong to cells that are in the active set. Intrafrequency cells in any neighbour list cannot be combined by the RNC with the neighbour list that is sent to a mobile in a soft handover area; trying to do SO will cause a scrambling code conflict error. The scrambling code plan audit will validate the minimum distance between the same carrier frequency cells with the same primary scrambling code. The scrambling code audit can also validate implementation of the operator nominal scrambling code plan if one exists. Radio Network Planning and Optimisation Adjacency Audit The purpose of the adjacency audit is to check the target cell parameter settings, number of adjacencies, adjacency distance and one-way adjacency definitions. A list of possible checks follows: ADJG (WCDMA to GSM adjacencies) ADJG distance > 20km ADJG inconsistencies - incorrect LAC, NCC or BCC ADJG inconsistencies - incorrect MCC or MNC ADJG inconsistencies - invalid target 2G CID (cell identifier) ADJG one-way neighbours (3G > 2G) ADJG target DN (domain name) empty ADJS(/I) (WCDMA intra/interfrequency adjacencies) ADJS distance > 20 km ADJS inconsistenci