Sie sind auf Seite 1von 72

Nokia Siemens Networks / NWS / VIPT R&D

IMPLEMENTATION SPECIFICATION

Release M16.1

FN923
Radio network parameter upgrade
FC010401 Increase the amount of BTS/SA objects

Key Words:
<type key words here - use abbreviations, names and terms as in
standards - set PI field "keywords" accordingly>
Author:
8.Jun.2011
Kaj Lahti

Approved by:
<dd mon yyyy>
<name>

Doc. version
[1. 2 ]

File Name
269159133.doc

Company Confidential

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

2 (72)
Feature 923

CONTENTS

1. INTRODUCTION
2. CONCEPTS
2.1

Abbreviations

2.2

Terms

3. REFERENCES
4. DESCRIPTION OF THE FEATURE
4.1

Feature usage requirements and limitations

4.2

Feature and functionality interworking

4.3

Restrictions

4.4

Compliancy information

5. OPERATOR INTERFACE
5.1
Operation and administration point of view
5.1.1 Activation of the feature
5.1.2 Deactivation of the feature
5.1.3 Management of the feature
5.1.4 Billing principles
5.1.5 Usage tips
5.2
Implementation point of view
5.2.1 MML
5.2.1.1
BTHAND, EP BTS AND SA HANDLING
5.2.1.2
LAHAND, EL LOCATION AREA HANDLING
5.2.1.3
BCOHAN, ED CELLULAR NETWORK CONTROLLER HANDLING
5.2.1.4
NRHAND, E3 NRI AND POOL AREA CONFIGURATION HANDLING
5.2.2 Parameters
5.2.3 Reports
5.2.3.1
ASCII report
5.2.3.2
XML report
5.2.3.3
Key Performance Indicators (KPI)
5.2.4 Announcements
5.2.5 Cause codes
5.2.6 Alarms
5.2.7 Files

6. SUBSCRIBER INTERFACE
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

3 (72)
Feature 923

7. EFFECTS ON EXTERNAL INTERFACES


7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
7.1.6
7.1.7
7.1.8
7.1.9
7.1.10
7.1.11
7.1.12
7.1.13
7.1.14
7.1.15
7.1.16
7.1.17
7.1.18
7.1.19
7.1.20
7.1.21
7.1.22
7.1.23
7.1.24
7.1.25
7.1.26

PSTN/ISDN (ISUP, C-TUP)


TCP/IP and OSI interfaces
Iu-CS
A-INTERFACE
MAP
Gr (MAP2)
Gf (MAP3)
AIR-INTERFACE
PBX (30B+D, 23B+D, DPNSS1)
CORE-INAP, CAP (Camel)
Gs (BSSAP+)
RANAP
SSAP (CCBS)
MSC SRR
MSC HLR
MSC/HLR- Nokia NetAct
HLR- RoamFree Gateway
HLR- OMD
HLR- SCP
HLR- SRRi
HLR- USSDC
BICC
SIP (IP trunk)
SIP (MSS-MSS)
SIP (GCS-CPS)
H.248

8. IMPLEMENTATION DESCRIPTION
8.1
General
8.1.1 Control of the feature optionality
8.1.2 Functioning in products
8.2
Architecture and functionality
8.2.1 Implementation architecture
8.2.2 Feature functionality
8.3
Changes in network elements and signaling
8.3.1 Protocols and signaling
8.3.1.1
AIF
8.3.1.1.1 Call related
8.3.1.1.2 Assignment
8.3.1.1.2.1 Modification assignment
8.3.1.1.2.2 Directed retry
8.3.1.1.3 Handovers and relocations
8.3.1.1.3.1 Intra MSS
8.3.1.1.3.2 Inter MSS
8.3.1.1.3.3 Subsequent handovers and relocations
8.3.1.1.4 Call and non-call related BSSAP/RANAP procedures
8.3.1.1.5 Supplementary services
8.3.1.1.5.1 Call waiting (CW), Intermediate calls
8.3.1.1.5.2 Multiparty (MP)
8.3.1.1.5.3 Multicall (MC)
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

4 (72)
Feature 923

8.3.1.1.5.4 Other supplementary services


8.3.1.1.6 Non call releated services
8.3.1.1.7 External interfaces
8.3.1.2
MAP
8.3.1.3
ISUP
8.3.1.4
TUP/ITUP
8.3.1.5
IUP
8.3.1.6
R2
8.3.1.7
R1/ANSI-MF
8.3.1.8
Decadic
8.3.1.9
DSS1
8.3.1.10 Iu
8.3.1.11 DPNSS
8.3.1.12 INAP
8.3.1.13 CAP
8.3.1.14 BSSAP
8.3.1.15 RANAP
8.3.1.16 BICC
8.3.1.17 SIP
8.3.1.18 H.248
8.3.2 VLR
8.3.2.1
Application
8.3.2.2
Database
8.3.2.3
Statistics
8.3.2.3.1 Measurements
8.3.2.3.1.1 VLR measurement
8.3.2.3.1.2 AC/VLR measurement
8.3.2.3.2 Subscriber observations
8.3.2.3.3 Supervisions
8.3.2.3.4 Other services of statistics
8.3.2.3.5 Changes to statistical program blocksMML
8.3.3 SPD
8.3.3.1
Application
8.3.3.2
Database
8.3.3.3
Statistics
8.3.3.3.1 Measurements
8.3.3.3.1.1 SPD measurement
8.3.3.3.2 Subscriber observations
8.3.3.3.3 Other services of statistics
8.3.3.3.4 Changes to statistical program blocks
8.3.3.4
MML
8.3.4 HLR
8.3.4.1
Application
8.3.4.2
Database
8.3.4.2.1 CDR Changes
8.3.4.2.2 New CDR fields
8.3.4.2.3 Changed CDR fields
8.3.4.2.4 CDR generation parameters
8.3.4.2.5 Changes to charging program blocks
8.3.4.3
Statistics
8.3.4.3.1 Measurements
8.3.4.3.1.1 Load observation
8.3.4.3.1.2 HLR measurement
8.3.4.3.2 Subscriber observations
8.3.4.3.2.1 Subscriber observation
8.3.4.3.2.2 HLR observation
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

5 (72)
Feature 923

8.3.4.3.3 Supervisions
8.3.4.3.4 Other services of statistics
8.3.4.3.5 Changes to statistical program blocks
8.3.4.4
MML
8.3.5 AUC
8.3.5.1
Application
8.3.5.2
Database
8.3.5.3
Statistics
8.3.5.3.1 AC/HLR measurements
8.3.5.4
MML
8.3.6 EIR
8.3.6.1
Application
8.3.6.2
Database
8.3.6.3
Statistics
8.3.6.3.1 EIR measurements
8.3.6.4
MML
8.3.7 SRR
8.3.7.1
Application
8.3.7.2
Database
8.3.7.3
Charging
8.3.7.3.1 CDR Changes
8.3.7.3.2 New CDR fields
8.3.7.3.3 Changed CDR fields
8.3.7.3.4 CDR generation parameters
8.3.7.3.5 Changes to charging program blocks
8.3.7.4
Statistics
8.3.7.4.1 Measurements
8.3.7.4.1.1 Load observation
8.3.7.4.1.2 SRR measurement
8.3.7.4.2 Supervisions
8.3.7.4.3 Other services of statistics
8.3.7.4.4 Changes to statistical program blocks
8.3.7.5
MML
8.3.8 MGW
8.3.8.1
Rel.99 Application (ATM Module)
8.3.8.2
Rel.4 Application (MSC server network)
8.3.8.3
Rel.5 Application (GCS controlled)
8.3.9 MSC
8.3.9.1
Applications
8.3.9.1.1 CRMPRB
8.3.9.1.2 CRHPRB
8.3.9.1.3 RNEUPD
8.3.9.1.4 RNZPRB
8.3.9.2
SMS Applications
8.3.9.3
Originating basic call state model (OBCSM)
8.3.9.3.1 O_Null
8.3.9.3.2 Authorize_origination_attempt
8.3.9.3.3 Collect_Information
8.3.9.3.4 Pre_Analyze_Information
8.3.9.3.5 Analyze_Information
8.3.9.3.6 Select_Route
8.3.9.3.7 Authorize_call_setup
8.3.9.3.8 Send_Call
8.3.9.3.9 O_Alerting
8.3.9.3.10 O_Active
8.3.9.3.11 O_Suspended
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

6 (72)
Feature 923

8.3.9.3.12 O_disconnect
8.3.9.3.13 O_stop
8.3.9.3.14 O_abandon
8.3.9.3.15 Control_of_interrupt
8.3.9.3.16 O_exception
8.3.9.3.17 CSMLIB
8.3.9.4
Terminating basic call state model (TBCSM)
8.3.9.4.1 T_null
8.3.9.4.2 Authorize_termination_attempt
8.3.9.4.3 T_get_routing_data
8.3.9.4.4 Select_facility
8.3.9.4.5 Present_call
8.3.9.4.6 T_alerting
8.3.9.4.7 T_active
8.3.9.4.8 T_suspended
8.3.9.4.9 T_disconnect
8.3.9.4.10 Select_termination
8.3.9.4.11 T_abandon
8.3.9.4.12 Control_of_interrupt
8.3.9.4.13 T_exception
8.3.9.4.14 T_stop
8.3.9.4.15 CSMLIB
8.3.9.5
Calling Party Services
8.3.9.5.1 Calling Party Supplementary Services interface services (CGPLIB)
8.3.9.5.2 CMREAD
8.3.9.6
Called Party Services
8.3.9.6.1 Called Party Supplementary Services interface services (CDPLIB)
8.3.9.6.2 CMREAD
8.3.9.7
Data services
8.3.9.7.1 Data service interface services (DATLIB)
8.3.9.7.2 OCFPRB
8.3.9.7.3 IWFSEB
8.3.9.7.3.1 IW1PRB
8.3.9.7.3.2 RLMCON
8.3.9.7.3.3 EMCPRO
8.3.9.7.3.4 Effects to old data features implementation
8.3.9.7.3.5 Effects to CDSU pool in general / implementation aspects
8.3.9.8
Call forwarding services
8.3.9.8.1 Call forwarding interface services (CFWLIB)
8.3.9.8.2 CFOPRB
8.3.9.9
Signaling services
8.3.9.9.1 Signaling services interface services (SIGLIB)
8.3.9.9.2 Timers interface services (TIMLIB)
8.3.9.10 Charging
8.3.9.10.1 Charging interface services (CHALIB)
8.3.9.10.2 Accounting counters
8.3.9.10.3 Changes to charging program blocks
8.3.9.10.4 Time charging services
8.3.9.10.4.1 Network charging
8.3.9.10.4.2 IN controlled charging
8.3.9.10.5 CDR changes
8.3.9.10.5.1 New CDR fields
8.3.9.10.5.2 Changed CDR fields
8.3.9.10.5.3 CDR generation parameters
8.3.9.11 Statistics
8.3.9.11.1 Supervisions
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

7 (72)
Feature 923

8.3.9.11.2 Measurements
8.3.9.11.2.1 Traffic measurements
8.3.9.11.2.1.1 Cell measurement
8.3.9.11.2.2 Handover measurements
8.3.9.11.3 Changes to statistics program blocks
8.3.9.11.4 HSPPRB
8.3.9.11.5 HMOBLI
8.3.9.11.6 BOBLIS
8.3.9.11.7 TRAMNT
8.3.9.12 Routing
8.3.9.12.1 Routing interface services (ROULIB)
8.3.9.12.2 CMREAD
8.3.9.13 Announcement
8.3.9.13.1 Announcement interface services (ASELIB)
8.3.9.13.2 ASEPRB, CASSIG
8.3.9.14 Service switching function
8.3.9.14.1 IN interface (INIF) services
8.3.9.14.2 SREPRB
8.3.9.14.3 GAPPER
8.3.9.14.4 CZAPRB
8.3.9.14.5 CZGPRB
8.3.9.15 Echo cancelling
8.3.9.15.1 Echo cancelling interface services (ECCLIB)
8.3.9.15.2 ECCPRB
8.3.9.15.3 RMAPRB
8.3.9.16 Switching
8.3.9.16.1 Switching interface services (SWILIB)
8.3.9.16.2 RMAPRB
8.3.9.16.3 SWICOP
8.3.9.17 MML
8.3.9.17.1 BTHAND
8.3.9.17.2 LAHAND
8.3.9.17.3 BCOHAN
8.3.9.17.4 NRHAND
8.3.10
NEMU
8.3.10.1 HLR/SRR Work Station (WS)
8.3.10.2 FSM/MVR
8.3.10.3 WS/SMM/ICP
8.3.10.4 N+X
8.3.10.5 CMDM
8.3.10.6 NEBS
8.3.11
Integrated MSC Server (MSS)
8.3.12
Standalone MSS and Gateway Control Server (GCS)
8.3.13
Circuit Switched Data Server (CDS)
8.3.14
CPS
8.3.15
HSS

9. PROPOSED ENVIRONMENT DEFINITIONS


9.1
Services
9.1.1 Changes to old service definitions
9.1.2 New service definitions
9.1.2.1
[Service_name_as /_ss] provided by [XXXPRB] / [ZZZSEG]
Use of service
Service Interface
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8 (72)
Feature 923

9.2
Messages
9.2.1 Changes to old message definitions
9.2.2 New message definitions
9.2.2.1
check_sa_r4_compab_to_la_s
9.2.2.2
output_rel_of_bsc_req_s
9.2.2.3
output_rel_of_bsc_resp_s
9.2.2.4
output_data_of_bts_req_s
9.2.2.5
output_data_of_bts_resp_s
9.2.2.6
all_cells_msg_s
9.2.2.7
check_bts_or_sa_existence_s
9.2.2.8
check_bts_or_sa_exist_ack_s
9.3
Types
9.3.1 Changes to old type definitions
9.3.1.1
Msc_int_cell_nbr_t
9.3.1.2
la_conf_data_t
9.3.1.3
Bts_adm_nbr_and_name_t
9.3.1.4
Bts_basic_data_t
9.3.1.5
Bts_identifiers_t
9.3.1.6
Bts_data_in_la_t
9.3.1.7
Bts_data_t
9.3.1.8
Sac_data_t
9.3.1.9
La2_data_t
9.3.1.10 sta_sub_data_t
9.3.2 New type definitions
9.3.2.1
Object_number_t
9.3.2.2
Cell_name_t
9.4

License

9.5
PRFILE Parameters
9.5.1 Changed parameters
9.5.2 New parameters
9.5.3 Used parameters
9.6
Files
9.6.1 Changes to old file definitions
9.6.1.1
Btsfil_t
9.6.2 New file definitions
9.7
Alarms
9.7.1 Changes to old alarm definitions
9.7.2 New alarm definitions

10.

HARDWARE CONSIDERATIONS AND CAPACITY CONSIDERATIONS

10.1
HW
10.1.1
HW Changes and requirements
10.1.2
HW Configuration and system maintenance
10.2
Capacity
10.2.1
CPU and MB capacity
10.2.2
Link capacity
10.2.3
I/O capacity
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

10.2.4

11.

9 (72)
Feature 923

Process and resource considerations

SW CONFIGURATION, TESTING AND UPGRADE CONSIDERATIONS

11.1

SW Configuration management

11.2
Release upgrade considerations
11.2.1
Conversion programs
11.2.1.1 BTSCNVMX
11.2.1.2 ZF4CNVMX
11.2.1.3 ZF7CNVMX
11.3
Feature testing information
11.3.1
Functional testing
11.3.2
Performance testing
11.3.3
Delivery Verification
11.3.4
Release upgrade testing
11.3.5
System Verification (SyVe)

12.

RISKS

13.

ANNEXES

DOCUMENT REVISION HISTORY

Instructions (except this sentence) are written in italic with Instruction-style. If they are not shown,
please, do the following: Tools->Options->Check the Hidden Text check box. If you want the
instructions disappear do the following: Tools->Options->Uncheck the Hidden Text check box

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

1.

10 (72)
Feature 923

INTRODUCTION
The purpose of this feature is to increase the maximum amount of 3G service areas
and 2G cells in MSS radio network configuration. New radio access types like Femto
and I-HSPA seems to require greater amount of service areas (SA) as legacy 3G. In
addition to that Multipoint Iu/A may require higher amount of service areas/cells than
the current maximum. With this Feature Component the maximum amount of 3G
service areas and/or 2G cells will be increased from 50 000 to 200 000. Note that
200 000 is the total amount of both SAs and cells, so in one MSS there can be e.g.
50 000 cells and 150 000 SAs.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

2.

CONCEPTS

2.1

Abbreviations
ABBR

2.2

11 (72)
Feature 923

Explanation

Terms
Term

Explanation

Binary search
algorithm

Search in which an ordered set of items is divided into


two parts, one of which is rejected. The search is
repeated in the accepted part until it is completed.

CI

Cell Identity in 2G networks. The cell identity is unique


when presented together with location area identification
(LAI)

SAC

Service Area Code in 3G networks. A part of the service


area identifier (SAI) which uniquely identifies a service
area within a location area.

Femto cell

Femtocells are the basic elements of the femtocell


network and provide WCDMA radio coverage, for
example, inside private homes.

Femto cell network

Radio access network that consists of one or more


femto access points and one or more femto gateways.

I-HSPA

I-HSPA is a flat architecture standardized by 3GPP Rel7. In I-HSPA the basestation (NodeB) is directly
connected to CS core via standard Iu-cs control. Part of
RNC functionality is also moved to NodeB.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

3.

12 (72)
Feature 923

REFERENCES
Public references:
/1/

3GPP TS 23.003 v.9.0 Numbering, addressing and identification

/2/ 3GPP TS 25.413 v.9.0 UTRAN Iu Interface RANAP signaling


/3/ 3GPP TS 48.008 v.9.0 Mobile Switching Centre Base Station system interface
; layer 3 specification
Internal references:
[Company confidential]
/A/ FN 923 Radio Network parameter upgrade
/B/ FN 1952 I-HSPA Support in MSc Server
/C/ FN 1449 Multipoint Iu Interface
/D/ FN 1564 Multipoint A Interface

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

4.

13 (72)
Feature 923

DESCRIPTION OF THE FEATURE


Maximum amount of service ares and cells are increased from 50 000 to 200 000 in
one MSS. However the maximum amount of cells or service areas in one location
area is 65535 (according the 3GPP specifications). Because some of the service
area and cell identity values are reserved for special purposes, the maximum
amount of service areas/cells in one location area is 65530.
Increased amount of service areas and cells require that the administrative BTS/SA
object numbering is extended from 1-65535 to 1-999999. However the cell identity
(CI) and service area code (SAC) value range stays unchanged (in range 0-65535
according the 3GPP specifications).

4.1

Feature usage requirements and limitations


The maximum amount of service areas or cells in one location area is 65530.
Typically different location areas are used for 2G and 3G, but if 2G and 3G is
defined in the same location area total amount of 3G SAs and 2G Cells is 65530, so
one location area can contain e.g. 30 000 SAs and 35 530 Cells.
With more than 65536 service areas/cells in a MSS, reusage of same CI/SAC
values in different location areas must be utilized.
The Multipoint export/import functionality (E3X/E3Y) is time consuming when large
radio network configurations are handled. The exporting and importing MML
execution time can take up to several hours.

4.2

Feature and functionality interworking

4.3

Restrictions
Maximum amount of servicea areas and/or cells in one location area is 65530. It is
possible to have e.g 30 000 SAs and 35 530 Cells in one location area.

4.4

Compliancy information
Feature is compliant with 3GPP standards.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

5.

OPERATOR INTERFACE

5.1

Operation and administration point of view

5.1.1

Activation of the feature

14 (72)
Feature 923

New increased SA/Cell amount is controlled with capacity LICENSE Extended SA


and Cell capacity in MSS.
The availability of extended administrative BTS/SA numbering range is generic and
requires no LICENSE activation.
5.1.2

Deactivation of the feature


Feature is deactivated by setting LICENSE Extended SA and Cell capacity in MSS
to OFF state.

5.1.3

Management of the feature

5.1.4

Billing principles

5.1.5

Usage tips

5.2

Implementation point of view

5.2.1

MML

5.2.1.1

BTHAND, EP BTS AND SA HANDLING


Administrative max BTS/SA object number is increased in following commands:
ZEPC Create BTS or Service Area
ZEPD Delete BTS or Service Area
ZEPS Change BTS or Service Area Administative State
ZEPB Define LA-BTS-BSC Relation
ZEPF Define LA-SA-MGW Relation
ZEPR Modify BTS or Service Area Parameters
ZEPH Modify Parameters of Handover Due to Traffic Reason

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

15 (72)
Feature 923

ZEPI Modify Resource Indication Parameters


ZEPN Modify BTS Neighbourhood
ZEPO Output BTS or Service Area Data
Optimisation in interrogating of BTS/ SA objects:
ZEPO Output BTS or Service Area Data

5.2.1.2

LAHAND, EL LOCATION AREA HANDLING


Administrative max BTS/SA object number is increased in following commands:
ZELO Output Location Area Data
ZELM Modify Auxiliary Location Area Data
ZELJ Output Auxiliary Location Area Data

5.2.1.3

BCOHAN, ED CELLULAR NETWORK CONTROLLER HANDLING


Administrative max BTS/SA object number is increased in following commands:
ZEDO Output Cellular Network Controller Data

5.2.1.4

NRHAND, E3 NRI AND POOL AREA CONFIGURATION HANDLING


Administrative max BTS/SA object number is increased in following commands:
ZE3X Export Pool Area RN Configuration of MSS
ZE3Y Import Pool Area RN Configuration to MSS
ZE3V Activate RN Configuration of Pool Area
Support for 200 000 BTS/SA objects in export/import functionality & new enhanced
execution printout with export/import progress indicated:
ZE3X Export Pool Area RN Configuration of MSS
ZE3Y Import Pool Area RN Configuration to MSS

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

5.2.2

Parameters

5.2.3

Reports

16 (72)
Feature 923

There is no change in the report formats. Only the number of objects is increased in
the following measurement as follows:

5.2.3.1

Measurement

Object size change

Cell measurement (22/16H).

50000 200000

ASCII report
No change.

5.2.3.2

XML report
No change.

5.2.3.3

Key Performance Indicators (KPI)


N/A

5.2.4

Announcements

5.2.5

Cause codes

5.2.6

Alarms

5.2.7

Files
Increase of 3G SA / 2G Cell amount will increase also the file sizes. Record amount
variable (msc_int_cell_nbr_t) will need now 4 octect instead of 2 octects (if
record_number_t is used , no changes required).
BTSFIL
Record amount of BTSFIL is increased from 50 000 to 200 000. Record size is
increased from 120 to 186 (object number increased with 2 bytes and neigh BTS list
increased with 64 bytes)
Small changes to following BTSFIL file handling C-routines:
btsfil_f_r__adm_bts_number, btsfil_f_s__lac_ci, btsfil_f_s__lac,
btsfil_f_r__record_bts, btsfil_f_r__lac_ci_bts, btsfil_f_r__state_bts,
btsfil_f_r__name_bts, btsfil_f_r__bsc_no_bts and btsfil_f_w__record_bts.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

17 (72)
Feature 923

CDAFIL
Record amount of CDAFIL is increased from 50 000 to 200 000.
CERFIL
Record amount of CRMPRB work file CERFIL is increased from 50 000 to 200 000.
ZF4FIL
Record size of ZF4FIL is increased from 620 to 622 (int Cell ID increased with 2
bytes).
ZF7FIL
Record size of ZF7FIL is increased from 16 to 18 (int Cell ID increased with 2 bytes).
CEFFIL
Record amount of CEFFIL is increased from 50 001 to 200 001.
HCALAR
Record amount of HCALAR is increased from 50 000 to 200 000.
BSBLIS
Record amount of BSBLIS is increased from 50 000 to 200 000.
BSTRAF
Record amount of BSTRAF is increased from 50 001 to 200 001.
HM1LIS
Record amount of HM1LIS is increased from 50 000 to 200 00.

Following SA and cell related files needs to be increased:


File

Rec
size

Rec
count

Cur
size

New
rec
size

New
rec
count

New
size

CPU units

BTSFIL

120

50 000

6.0 MB

186

200 000

37.2 MB

CMU,OMU,GISU

CDAFIL

72

50 000

3.6 MB

14.4 MB

CMU,OMU,BSU,CCSU,
CASU,PAU, GSU,TGSU,
SIGU, SCPU, GISU

CERFIL

42

50 000

2.1 MB

8.4 MB

CMU (CRM work file). Uses

200 000

200 000

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

18 (72)
Feature 923

BTSFIL rec count when


creating file.
ZF4FIL

620

300

0.19 MB

622

300

0.19 MB

CMM, OMU, SCPU, CCSU,


SIGU, GISU

ZF7FIL

16

1024

0.016 MB

18

1024

0.018 MB

CMM, OMU, SCPU, GISU

CEFFIL

22

50 001

1.1 MB

200 001

4.4 MB

STU

HCALAR

47

50 000

2.35 MB

200 000

9.4 MB

STU (work file)

BSBLIS

50 000

0.25 MB

200 000

1 MB

STU,OMU

BSTRAF

128

50 001

6.4 MB

200 001

25.6 MB

STU (work file)

HM1LIS

15

50 000

0.75 MB

200 000

3 MB

STU, OMU

SCALLF

541
6

12 000

65 MB

65 MB

STU (work file), int_cell nbr


within sta_sub_data_t, spare
bytes taken in use

Following SA and cell related files needs to be increased:


File

Rec
count

New
rec
count

CPU units

BTSFIL

50 000

200 000

CMU,OMU,GISU

200 000
CDAFIL

50 000

CMU,OMU,BSU,CCSU,
CASU,PAU, GSU,TGSU,
SIGU, SCPU, GISU

CERFIL

50 000

200 000

CMU (CRM work file). Uses


BTSFIL rec count when
creating file.

CEFFIL

50 001

200 001

STU

HCALAR

50 000

200 000

STU (work file)

BSBLIS

50 000

200 000

STU,OMU

BSTRAF

50 001

200 001

STU (work file)

HM1LIS

50 000

200 000

STU, OMU

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

19 (72)
Feature 923

Memory consumption calculations:


UNIT

OLD

NEW

INCREASE

OMU

6+3.6+0.25+0.75=10.6 MB

37.2+14.4+1+3=55.6 MB

CMU

6+3.6+2.1=11.7 MB

37.2+14.4+8.4=60 MB

45 MB
48.3 MB

BSU/CCSU/CASU
/
PAU/GSU/TGSU/
SIGU/SCPU

10.8 MB
3.6 MB

14.4 MB

STU

1.1+2.35+0.25+6.4+0.75=10.8
5 MB

4.4+9.4+1+25.6+3=43.4
MB

CMM

0.19+0.016=0.21 MB

0.19+0.018=0.21 MB

GISU

6+3.6+0.19+0.016=9.8 MB

37.2+14.4+0.19+0.018=
51.8 MB

42 MB

OMU DISK

6+3.6+1.1+0.25+0.75=11.7 MB

37.2+14.4+4.4+1+3=60
MB

48.3 MB

32.55 MB
-

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

6.

20 (72)
Feature 923

SUBSCRIBER INTERFACE

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

7.

21 (72)
Feature 923

EFFECTS ON EXTERNAL INTERFACES


Note! The pictures 1-4 do not contain all possible interfaces and network elements
but give a general idea of most common interfaces and interworking network
elements. Add missing elements and interfaces as necessary. Remove unnecessary
pictures

7.1.1

PSTN/ISDN (ISUP, C-TUP)

7.1.2

TCP/IP and OSI interfaces

7.1.3

Iu-CS

7.1.4

A-INTERFACE

7.1.5

MAP

7.1.6

Gr (MAP2)

7.1.7

Gf (MAP3)

7.1.8

AIR-INTERFACE

7.1.9

PBX (30B+D, 23B+D, DPNSS1)

7.1.10

CORE-INAP, CAP (Camel)

7.1.11

Gs (BSSAP+)

7.1.12

RANAP

7.1.13

SSAP (CCBS)

7.1.14

MSC SRR

7.1.15

MSC HLR

7.1.16

MSC/HLR- Nokia NetAct


The increased amount of sevice areas/ cells effects the radio network configuration
uploading time from MSS to NetAct.
The changed max BTS/SA object number range effects the configuration
Management in NetAct.
The object amount is changed by this feature for the following measurement:
Measurement

Object size change

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

Cell measurement (22/16H).

7.1.17

HLR- RoamFree Gateway

7.1.18

HLR- OMD

7.1.19

HLR- SCP

7.1.20

HLR- SRRi

7.1.21

HLR- USSDC

7.1.22

BICC

7.1.23

SIP (IP trunk)

7.1.24

SIP (MSS-MSS)

7.1.25

SIP (GCS-CPS)

7.1.26

H.248

22 (72)
Feature 923

50000 200000

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.

IMPLEMENTATION DESCRIPTION

8.1

General

8.1.1

Control of the feature optionality

23 (72)
Feature 923

New increased SA/Cell amount is controlled with capacity LICENSE Extended SA


and Cell capacity in MSS (fc_t_ext_sa_cell_capacity_in_mss, FCxxxx). Capacity
can be increased in 50 000 steps. Up to 3 steps can be bought with a total
maximum SA/Cell amount of 200 000 objects (basic capacity + 3 x 50 000). Basic
capacity without LICENSE is 50 000.
Note! If customer has FC10568 with 65k SA/Cell capacity activated from M15.1 then
this Capacity License overrule that PRFILE controlled intermediate capacity
extension.
Allowed maximum amount of SAs/Cells is checked when creating new SA/Cell with
EPC-command. Command allows only creation of allowed amount of SAs/Cells.
The availability of extended administrative BTS/SA numbering range (1-999999) is
generic and requires no LICENSE activation.

8.1.2

Functioning in products
Feature supported in both DX MSS and ATCA MSS. Futhermore available in both
integrated and standalone DX MSS.

8.2

Architecture and functionality

8.2.1

Implementation architecture

8.2.2

Feature functionality

8.3

Changes in network elements and signaling

8.3.1

Protocols and signaling

8.3.1.1

AIF
Some changes to write_to_log calls where
(WORD changed to DWORD).

msc_int_cell_nbr_t is involved

Table size of paging data (la_conf_data_t) is increased to include up to 65530


BTSs/SAs int cell numbers (dword) per location area. AIFPRB&CRMPRB stack
needs to be increased accordingly.
la_conf_data_t increase calculation:
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

BTS/SAC

65530 x 4 B = 262 120 B

BSC

500 x 6 B = 3000 B

RNC/I-BTS headers

3 x 6 B = 18 B

RNC/I-BTS

16000 x 2 B = 32 000 B

Total la_conf_data size

= 297138 =~297 200 B

24 (72)
Feature 923

Searching SA int_cell number from la_buffer/CDAFIL according SAI (SAC + LAI)


value can be slow if there exist a lot of service areas in a location area. Therefore a
binary search algorithm is taken in use to find the correct SA int_cell number faster
from the la_buffer. CRMPRB takes care of building the LA configuration data
according this method (see CRMPRB chapter 8.3.9.1.1 for detailed information) so
that AIFPRB can utilize the binary search algorithm for faster search.

8.3.1.1.1

Call related
Effects for MOC, MTC, emergency call and data calls.

8.3.1.1.2

Assignment
Effects for MSS A and A, reversed CRCT reservation functionality.

8.3.1.1.2.1

Modification assignment
Support and non-support mode for RAB modification assignment.

8.3.1.1.2.2

Directed retry
Effects for MSS A and A, intra- and inter system.

8.3.1.1.3

Handovers and relocations

8.3.1.1.3.1

Intra MSS
Effects for MSS A and MSS A.

8.3.1.1.3.2

Inter MSS
Effects for MSS A and MSS A.

8.3.1.1.3.3

Subsequent handovers and relocations


Source MSS and target MSS.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.1.1.4

Call and non-call related BSSAP/RANAP procedures

8.3.1.1.5

Supplementary services

8.3.1.1.5.1

Call waiting (CW), Intermediate calls

8.3.1.1.5.2

Multiparty (MP)

8.3.1.1.5.3

Multicall (MC)

8.3.1.1.5.4

Other supplementary services

25 (72)
Feature 923

Call transfer etc.


8.3.1.1.6

Non call releated services


Location services, trace invocation etc.

8.3.1.1.7

External interfaces
Effects for A, A, A+, Iu, Gs and E-interface, e.g. encoding/decoding.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.1.2

MAP

8.3.1.3

ISUP

8.3.1.4

TUP/ITUP

8.3.1.5

IUP

8.3.1.6

R2

8.3.1.7

R1/ANSI-MF

8.3.1.8

Decadic

8.3.1.9

DSS1

8.3.1.10

Iu

8.3.1.11

DPNSS

8.3.1.12

INAP

8.3.1.13

CAP

8.3.1.14

BSSAP

8.3.1.15

RANAP

8.3.1.16

BICC

8.3.1.17

SIP

26 (72)
Feature 923

The SIP Group Profile configuration file ZF4FIL record size is changed and file need
to be handled wth conversion during upgrade.
The Mapping between the Location ID and CGI file ZF7FIL record size is changed
and file need to be handled wth conversion during upgrade.
8.3.1.18

H.248

8.3.2

VLR

8.3.2.1

Application

8.3.2.2

Database

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.2.3

Statistics

8.3.2.3.1

Measurements

8.3.2.3.1.1

VLR measurement

8.3.2.3.1.2

AC/VLR measurement

8.3.2.3.2

Subscriber observations

8.3.2.3.3

Supervisions

8.3.2.3.4

Other services of statistics

8.3.2.3.5

Changes to statistical program blocksMML

8.3.3

SPD

8.3.3.1

Application

8.3.3.2

Database

8.3.3.3

Statistics

8.3.3.3.1

Measurements

8.3.3.3.1.1

SPD measurement

8.3.3.3.2

Subscriber observations

8.3.3.3.3

Other services of statistics

8.3.3.3.4

Changes to statistical program blocks

8.3.3.4

MML

8.3.4

HLR

8.3.4.1

Application

8.3.4.2

Database

27 (72)
Feature 923

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.4.2.1

CDR Changes

8.3.4.2.2

New CDR fields

8.3.4.2.3

Changed CDR fields

8.3.4.2.4

CDR generation parameters

8.3.4.2.5

Changes to charging program blocks

8.3.4.3

Statistics

8.3.4.3.1

Measurements

8.3.4.3.1.1

Load observation

8.3.4.3.1.2

HLR measurement

8.3.4.3.2

Subscriber observations

8.3.4.3.2.1

Subscriber observation

8.3.4.3.2.2

HLR observation

8.3.4.3.3

Supervisions

8.3.4.3.4

Other services of statistics

8.3.4.3.5

Changes to statistical program blocks

8.3.4.4

MML

8.3.5

AUC

8.3.5.1

Application

8.3.5.2

Database

8.3.5.3

Statistics

8.3.5.3.1

AC/HLR measurements

8.3.5.4

MML

8.3.6

EIR

8.3.6.1

Application

8.3.6.2

Database

28 (72)
Feature 923

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.6.3

Statistics

8.3.6.3.1

EIR measurements

8.3.6.4

MML

8.3.7

SRR

8.3.7.1

Application

8.3.7.2

Database

8.3.7.3

Charging

8.3.7.3.1

CDR Changes

8.3.7.3.2

New CDR fields

8.3.7.3.3

Changed CDR fields

8.3.7.3.4

CDR generation parameters

8.3.7.3.5

Changes to charging program blocks

8.3.7.4

Statistics

8.3.7.4.1

Measurements

8.3.7.4.1.1

Load observation

8.3.7.4.1.2

SRR measurement

8.3.7.4.2

Supervisions

8.3.7.4.3

Other services of statistics

8.3.7.4.4

Changes to statistical program blocks

8.3.7.5

MML

8.3.8

MGW

29 (72)
Feature 923

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.8.1

Rel.99 Application (ATM Module)

8.3.8.2

Rel.4 Application (MSC server network)

8.3.8.3

Rel.5 Application (GCS controlled)

8.3.9

MSC

8.3.9.1

Applications

8.3.9.1.1

CRMPRB

30 (72)
Feature 923

Controlling SA/BTS amount per LA:


Maximum amount of service areas or cells in one location area is 65530. CRM check
that this amount is not exceeded each time when a service area or cell is unlocked
by
MML
command
(with
ZEPS-command
and
receives
message
crm_upd_paging_data_s). If no free space for the service area/cell then status
crm_error_code_t_conf_lim_exc_c is returned to RNEUPD in message
crm_upd_paging_data_ack_s.

LA_buffer&binary search algorithm usage:


Default paging response timer value changed from 2s to 1s.
Table size of paging data (la_conf_data_t) is increased to include up to 65530
BTSs/SAs int cell numbers (dword) per location area. AIFPRB&CRMPRB stack
needs to be increased accordingly. For calculation of la_conf_data_t size see AIF
chapter 8.3.1.1.
Searching SA int_cell number from la_buffer/CDAFIL according SAI (SAC + LAI)
value can be slow if there exist a lot of service areas in a location area. Therefore a
binary search algorithm is taken in use to find the correct SA int_cell number faster
from the la_buffer. CRMPRB takes care of building the LA configuration data
according this method so that AIFPRB can utilize the binary search algorithm for
faster search. Only SA part of the la_buffer is arranged for binary search.
Int_cell number in la_buffer is arranged according ascending value of SAC from
CDAFIL. So for example (see figure 1) SA int_cell number 41 is written in the first
index (pointing to lowest SAC value 1 in CDAFIL) and SA int_cell number 1 is written
in the last index (pointing to the highest SAC value 501 in CDAFIL).

Example of use (see figure 1): AIF needs to find the int_cell number according SAC
value 1.
With old functionality correct SA int_cell number would have been found after 5
consequtive searches. With new functionality correct SA int_cell number is found
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

31 (72)
Feature 923

with 3 consequtive searches. The effectiveness of the binary search algorithm


improves significantly when the amount of SAs increases per LA. For example with
65530 SAs per LA, the worst case scenario in old search functionality would require
up to 65530 consequtive searches wheras the binary search algorithm produce the
same result in maximum of 16 searches.

Figure 1: LA_buffer table vs. CDAFIL arranged according binary search algorithm

Log writings:
Some changes to write_to_log calls where msc_int_cell_nbr_t is used (WORD
changed to DWORD).
Master:
Master of CRMPRB creates CERFIL work file according the size BTSFIL, now this
file will increase from 50 000 to 200 000 records. CERFIL contains loading
information of 2G cells in case of Resource Indication feature is activated. CERFIL
is currently created even the feature is not set ON. (Feature is not used in live
networks).
CRMUPD hand:
In
update_paging_data
and,
update_aux_paging_data
and
update_paging_data2 procedures handling of int_cell_id variable have to be
changed.
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

32 (72)
Feature 923

CRMCEL hand
check_out_cri, clear_crmhoc_pid procedures
crm_resource_ind_s,
crm_bsc_reset_ind_s
crm_set_resource_req_s
crm_cell_load_enq_s crm_t_cell_overload_t6 transitions write_to_log calls

C-routines:
move_data_to_sac_buffer,
reserve_la_buf_and_wri,
r_int_cell_from_la_buf, move_data_to_bsc_buffer

8.3.9.1.2

add_cell_id_to_la_buffer,

CRHPRB
Some changes to write_to_log calls where msc_int_cell_nbr_t is used (WORD
changed to DWORD).

8.3.9.1.3

RNEUPD
-

When creating a new BTS/SA (receiving of message bts_create_req_s) the max


allowed BTS/SA capacity is checked by adding the capacity limit value from
license Extended SA and Cell capacity in MSS to basic capacity 50 000. If
license read fail or license is not activated then basic 50 000 capacity is used (65
000 if FC10568 PRFILE activated from M15.1 release!). And if basic capacity +
extended license capacity limit value exceeds 200 000 then 200 000 is used as
the max amount of BTS/SA objects. If reserved BTSFIL record amount is bigger
or equal to max allowed BTS/SA amount then DX error capacity_limit_ec is
returned to BTHAND MML.

Message crm_upd_paging_data_s is sent to CRM when a service area/cell is


unlocked. If no free space for the service area/cell in la_buffer (max 65530 per
location area) then status crm_error_code_t_conf_lim_exc_c is returned in
message crm_upd_paging_data_ack_s. RNEUPD map this error to DX error
dm_object_table_full_ec in message rne_change_bts_sac_state_ack_s to
BTHAND
MML.

In write_to_log and test_write_to_log is called and object number is outputted


the number need to be outputted as dword instead of word.

In delete BTS/SA service the neighbour BTS record index should be handled as
dword instead of word (function check_neighbourhood in rneh02mx.c)

In BTS/SA state change service the object number need to be handled as dword
instead of word when values of resource indication is sent to CRMPRB

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

33 (72)
Feature 923

(state_is_changed_upd_res_ind in rneh00mx.sdl & read_resource_ind_param in


rneh02mx.c)

8.3.9.1.4

In BTS/SA modify service the object number need to be handled as dword


instead of word when values of resource indication is sent to CRMPRB
(update_res_ind_param_to_crm in rneh00mx.sdl & read_resource_ind_param in
rneh02mx.c). Furthermore when checking that there will not be too many BTS
with periodic resource indication method activated we need to handle the BTS
object number as dword instead of word (count_max_num_unl_period_bts in
rneh02mx.c). When defing a new object number (PDC9432) the object number
must be handled as DWORD instead of WORD.

In modify BTS neighbourhood service the object number need to be handled as


dword instead of word (add_neigh_bts & remove_neigh_bts in rneh02mx.c)

RNZPRB
-

In write_to_log and test_write_to_log is called and object number is outputted


the number need to be outputted as dword instead of word.

In BTS/SA output service the object number need to be handled as dword


instead of word (ask_from_crm_load_lev_of_cell in rnz1sjmx.sdl and
read_resource_ind_param in rnzh02mx.c). Furthermore when filling up the
neighbour BTS list the BTS object number needs to be handled as dword
instead of word (get_neigh_bts_list in rnzh02mx.c)

In interrogate BTS relation under BSC service the last handled BTS/SA object
number in message output_rel_of_bsc_req_s is changed from word to dword.

In BTS/SA existence service the BTS/SA object number in message


check_bts_or_sa_existence_s and check_bts_or_sa_exist_ack_s is changed
from word to dword.

Optimisation change of ZEDO-command (to speed up the interrogation of huge


amount of BTS/SA objects and to minimise OMU CPU load):
-

In interrogate BTS relation under BSC service the last handled BTS/SA object
number (output_rel_of_bsc_req_s) will be changed to last handled record
number. RNZPRB returns in message output_rel_of_bsc_resp_s the record
index of last handled BTS/SAC in list. MML returns this same record index in
next request so that RNZPRB can continue search from rec_nbr+1 instead of
searching the last returned BTS/SAC with rec_scan for each continuos search.
This is a optimisation enhancement.

Optimisation changes of ZEPO-command (to speed up the interrogation of


huge amount of BTS/SA objects and to minimise OMU CPU load):
Interrogate one service (ranges output with && sign):
To request message output_data_of_bts_req_s is added new release_hand field of
bool type. Currently each object number in the given range is interrogated one by
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

34 (72)
Feature 923

one (own hand in RNZPRB is reserved for each object interrogation). This is
optimised so that same RNZPRB hand will handle whole command execution of all
given ranges. With the new field release_hand in the request message MML will
indicate when all objects in all ranges are interrogated and RNZPRB can release its
hand process.
Furthermore in first request of a range the new field range_count is filled to indicate
the range (max 500). RNZPRB stores the found objects into a table with 500
elements of record_number_t type. So when receiving the first message RNZPRB
reads through the BTSFIL once and fills into each element the record index where
object is found in BTSFIL. And if it is not found then record_number is 0xFFFFFFFF.
So when interrogation of next number is received to this hand it directly reads the
BTSFIL record index from the 500 element table (without need for searching the
whole BTSFIL again, causing massive CPU load of 90-100%).
Interrogate one service:
Separate the interrogate search by object number, name and CI/SAC+LAC.
By object name:
Currently when interrogate by name the btsfil_f_s__rec_id_by_obj_name returns
already all needed data. So current code where we continue reading LAC+CI/SAC
with btsfil_f_r__lac_ci_bts according object number. And after this we search again
the correct record by calling btsfil_f_s__lac_ci. These additional searches are
needless.
By object number:
Currently when interrogate by number we could call a new function which returns at
once all needed data (for example btsfil_rec_int_cell_bts in rnzh02mx.c). Currently
we first read LAC+CI/SAC with btsfil_f_r__lac_ci_bts according object number. And
after this we search again the correct record by calling btsfil_f_s__lac_ci. These
additional searches are needless.

Interrogate all service:


To message output_data_of_bts_req_s and output_data_of_bts_resp_s is added
new last_handled_index field of record_number_t type. In first request message this
value is record_number_t_illegal_c. RNZPRB returns the record number where
returned object was found. MML sends this same record number in next request.
RNZPRB continue BTS/SA object search from received last_handled_index +1
instead of finding the last found object always with rec_scan search.
Other optimisation:
In the function btsfil_f_r__lac_ci_bts the btsfil_f_r__lac_ci call is not needed
because LA record number, CI/SAC and RN object type is got from rec_scan return
parameters.
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

35 (72)
Feature 923

Output_state_of_bs_as service:
In the response message 0x2660 all_cells_msg_s is added a new filed including the
cell names (150). RNZPRB fills in the cell names to this field into same index as the
cell number info is written.

8.3.9.2

SMS Applications

8.3.9.3

Originating basic call state model (OBCSM)

8.3.9.3.1

O_Null
dp_orig_attempt

8.3.9.3.2

Authorize_origination_attempt
dp_orig_attempt_auth

8.3.9.3.3

Collect_Information
dp_info_collected

8.3.9.3.4

Pre_Analyze_Information
dp_info_preanalyzed

8.3.9.3.5

Analyze_Information
Ana_info__rou_cha_att
Ana_info__get_dest
dp_info_analyzed

8.3.9.3.6

Select_Route
Sel_rou__get_sub_dest
Sel_rou__get_cha
dp_route_selected

8.3.9.3.7

Authorize_call_setup
dp_call_setup_auth

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.9.3.8

36 (72)
Feature 923

Send_Call
Send_call__wf_seiz_point
Send_call__wf_acm
Send_call__wf_alerting
dp_o_term_seized

8.3.9.3.9

O_Alerting
dp_o_answer
dp_o_release_in_answer

8.3.9.3.10

O_Active
dp_o_suspended
dp_o_mid_call

8.3.9.3.11

O_Suspended
dp_o_reanswer
dp_o_disconnect

8.3.9.3.12

O_disconnect
O_disconnect__select_release
O_disconnect__wf_a_release
O_disconnect__wf_b_release
O_disconnect__complete
dp_o_disconnect_completed

8.3.9.3.13

O_stop

8.3.9.3.14

O_abandon
dp_o_abandon

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.9.3.15

Control_of_interrupt

8.3.9.3.16

O_exception

37 (72)
Feature 923

dp_exception
8.3.9.3.17

CSMLIB

8.3.9.4

Terminating basic call state model (TBCSM)

8.3.9.4.1

T_null
dp_termination_attempt

8.3.9.4.2

Authorize_termination_attempt
dp_term_attempt_authorized

8.3.9.4.3

T_get_routing_data
dp_t_rou_info_received

8.3.9.4.4

Select_facility
dp_facility_sel_and_available

8.3.9.4.5

Present_call
Present_call__send_setup
Present_call__wf_acm
Present_call__wf_alerting
dp_call_accepted

8.3.9.4.6

T_alerting
dp_t_answer
dp_t_release_in_answer

8.3.9.4.7

T_active
dp_t_mid_call
dp_t_suspend

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.9.4.8

38 (72)
Feature 923

T_suspended
dp_t_re_answer
dp_t_disconnect

8.3.9.4.9

T_disconnect
T_disconnect__select_release
T_disconnect__wf_a_release
T_disconnect__wf_b_release
T_disconnect__complete
dp_t_disconnect_complete

8.3.9.4.10

Select_termination

8.3.9.4.11

T_abandon
dp_t_abandon

8.3.9.4.12

Control_of_interrupt
dp_exception

8.3.9.4.13

T_exception

8.3.9.4.14

T_stop

8.3.9.4.15

CSMLIB

8.3.9.5

Calling Party Services

8.3.9.5.1

Calling Party Supplementary Services interface services (CGPLIB)

8.3.9.5.2

CMREAD

8.3.9.6

Called Party Services

8.3.9.6.1

Called Party Supplementary Services interface services (CDPLIB)

8.3.9.6.2

CMREAD

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

39 (72)
Feature 923

8.3.9.7

Data services

8.3.9.7.1

Data service interface services (DATLIB)

8.3.9.7.2

OCFPRB

8.3.9.7.3

IWFSEB

8.3.9.7.3.1

IW1PRB

8.3.9.7.3.2

RLMCON

8.3.9.7.3.3

EMCPRO

8.3.9.7.3.4

Effects to old data features implementation

8.3.9.7.3.5

Effects to CDSU pool in general / implementation aspects

8.3.9.8

Call forwarding services

8.3.9.8.1

Call forwarding interface services (CFWLIB)

8.3.9.8.2

CFOPRB

8.3.9.9

Signaling services

8.3.9.9.1

Signaling services interface services (SIGLIB)

8.3.9.9.2

Timers interface services (TIMLIB)

8.3.9.10

Charging

8.3.9.10.1

Charging interface services (CHALIB)

8.3.9.10.2

Accounting counters

8.3.9.10.3

Changes to charging program blocks

8.3.9.10.4

Time charging services

8.3.9.10.4.1 Network charging


8.3.9.10.4.2 IN controlled charging
8.3.9.10.5

CDR changes

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

40 (72)
Feature 923

8.3.9.10.5.1 New CDR fields


8.3.9.10.5.2 Changed CDR fields
8.3.9.10.5.3 CDR generation parameters

8.3.9.11

Statistics

8.3.9.11.1

Supervisions
Cell Supervision shall be able to support the maximum amount of 3G service areas
and/or 2G cells, which is increased from 50 000 to 200 000.
Handover Supervision shall be able to support the maximum amount of 3G service
areas and/or 2G cells, which is increased from 50 000 to 200 000.

8.3.9.11.2

Measurements
Due to the increased number of 3G service areas and 2G cells in MSS the object list
size shall be also increased for Cell measurement (22/16H).

8.3.9.11.2.1 Traffic measurements


8.3.9.11.2.1.1

Cell measurement

This measurement shows the number of call events handled by each cell during the
measurement period. The measured object of the measurement is the LAC and CI /
SAC (Cell location area and Cell identifier / Service Area Code). The measurement
supports all the possible cells per MSS.
The record number of Cell object list file BSBLIS is increased from 50 000 to
200 000 while the record number of Base station traffic file BSTRAF is increased
from 50 001 to 200 001. The structure of the files remains the same. This way, the
measurement will support all the possible total cells.
8.3.9.11.2.2 Handover measurements
In Handover measurement report, part 2 (337/151H) the handovers are shown
based on the Cells/Service areas. The number of objects is limited to 5000. This
number is not changed, however it shall be provided that the measurement would
be able to handle the maximum amount of service areas and cells that are
increased from 50 000 to 200 000 on MSS level.
The record number of Handover Measurement object list file HM1LIS is
increased from 50 000 to 200 000. The HANDOVER MEASUREMENT OBJECT
LIST HANDLING MML program block HMOBLI shall also be changed to support
the whole increased cell range.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.9.11.3

Changes to statistics program blocks

8.3.9.11.4

HSPPRB

41 (72)
Feature 923

In HSPPRB there is an index table for the cell based handover measurement Handover measurement report, part 2 (337/151H) that is used to address the
proper cell related record in HAMMER. This index table shall be adjusted to the
maximum amount of 3G service areas and/or 2G cells, which is now increased to
200000.
8.3.9.11.5

HMOBLI
In the framework of FC010568, the MML was changed in a way that it is using the
rec_count() FISLIB library function to determine the record number of HM1LIS file.
As this is a general solution no further change is needed.

8.3.9.11.6

BOBLIS
In the framework of FC010568, the MML was changed in a way that it is using the
rec_count() FISLIB library function to determine the record number of BSBLIS file.
As this is a general solution no further change is needed.
The cell names array (150) field added in the 0x2600 all_cells_msg_s msg should
be ignored.

8.3.9.11.7

TRAMNT
TRAMNT inquires cell information from RNZPRB in each period, each cell needs
one integration msg. In case of large cell number configured in MSS, the inquiry msg
consumes longer time than report interval. If this inquiry is not finished, cell
measurement report could not be generated. Considering this performance issue,
inquiry interface to RNZPRB is changed.
TRA sends 0x2550 msg to RNZ master with operation = bs_op_type_t_int_all_cell_c
(0x2) instead of bs_op_type_t_int_one_cell_c(0x1). If RNZ answers with 0x2551
msg and the status in msg is process_is_too_busy_c TRA will set a 1sec timer.
When this timer out, TRA sends 0x2550 to RNZ again. In normal situation RNZ
answers with 0x2600 msg with 150 cells included and more = 0x1 indicating more
messages are needed. TRA sends msg 0x2550 to RNZ hand (who replies) at the
second time with operation = bs_op_type_t_send_more_c (0x3). RNZ answers with
msg ox2600 including next 150 cells and more = 0x1 indicating more messages are
needed. More inquiring 0x2550 msgs are sent to RNZ hand until RNZ answers with
msg 0x2600 with last cells(1-150) included and more = 0x0 indicating last messages
are received. The cell names (150) field should be added in the 0x2600 msg. This
interface is changed due to case, performance issue should be doubled checked
when cell nbr is changed to 200000.
Example:
1.
2.

TRA RNZ MASTER: MSG 0x2550 with operation=bs_op_type_t_int_all_cell_c (0x2)


TRA RNZ HAND X: MSG 0x2660 with 150 cells included and more=0x1 (more messages)

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

3.
4.
5.
6.

42 (72)
Feature 923

TRA RNZ HAND X: MSG 0x2550 with operation=bs_op_type_t_send_more_c (0x3)


TRA RNZ HAND X: MSG 0x2660 with next 150 cells included and more=0x1 (more messages)
etc
TRA RNZ HAND X: MSG 0x2660 with last cells (1-150) included and more=0x0 (last message)

Due to this interface and msg change, TRA need some other modifications:
1. Add a array to save all cell status. The status of cells which do not include in
0x2600 will set to false. It wil be used to indicate forming code the cells status.
2. When RNZ does not reply 0x2600 msg during 1sec, TRA will estimate the
0x2600 msg which miss from RNZ whether is the last msg, if this 0x2600 should
be the last msg, TRA will start to generate report at once.
For msc_int_cell_nbr_t extension, some loop variables in TRA should be changed
from WORD to DWORD.

8.3.9.12

Routing

8.3.9.12.1

Routing interface services (ROULIB)

8.3.9.12.2

CMREAD

8.3.9.13

Announcement

8.3.9.13.1

Announcement interface services (ASELIB)

8.3.9.13.2

ASEPRB, CASSIG

8.3.9.14

Service switching function

8.3.9.14.1

IN interface (INIF) services

8.3.9.14.2

SREPRB

8.3.9.14.3

GAPPER

8.3.9.14.4

CZAPRB

8.3.9.14.5

CZGPRB

8.3.9.15

Echo cancelling

8.3.9.15.1

Echo cancelling interface services (ECCLIB)

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

8.3.9.15.2

ECCPRB

8.3.9.15.3

RMAPRB

8.3.9.16

Switching

8.3.9.16.1

Switching interface services (SWILIB)

8.3.9.16.2

RMAPRB

8.3.9.16.3

SWICOP

8.3.9.17

MML

8.3.9.17.1

BTHAND

43 (72)
Feature 923

New enhanced BTS/SA administrative object numbering range 1 - 999 999 is


available as a generic SW change. Possibility to create more than 50 000 BTS/SA
objects is possible, when new LICENSE Extended SA and Cell capacity in MSS is
activated (this is checked by co-PRB RNEUPD).
ZEPC - Create BTS or Service Area
Value range of paramater NO (object number) increased from 165535 to 1
999999.
Value range of paramater RNO (reference object number) increased from 165535
to 1999999.
The object number needs to be changed to be handled as dword instead of word.
By default CI/SAC number will receive the same number as given for the object
number. This need to be changed so that if bigger object number than 65535 is
given then CI/SAC parameter will be obligatory to be given. Because max CI/SAC
number will remain as 65535.
Max allowed BTS/SA amount is checked by RNEUPD co-PRB, RNEUPD return
status capacity_limit_ec if amount is exceeded and MML outputs standard DX error
text /*** CAPACITY LIMIT EXCEEDED ***/ to user.
ZEPD Delete BTS or Service Area
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
Neighbour BTS list is printed if relation exist for requested BTS (error situation). In
this printout we must allow six digits to be outputted instead of existing 5 digits.
ZEPS Change BTS or Service Area Administative State
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

44 (72)
Feature 923

Value range of paramater NO (object number) increased from 165535 to 1


999999.
The object number needs to be changed to be handled as dword instead of word.
If receive DX error dm_object_table_full_ec in message
rne_change_bts_sac_state_ack_s from RNEUPD own clarifying text is outputted
after the DX error:
/*** MAX AMOUNT OF 65530 BTS/SA PER LA EXCEEDED ***/.
ZEPB Define LA-BTS-BSC Relation
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
ZEPF Define LA-SA-MGW Relation
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
ZEPR Modify BTS or Service Area Parameters
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
ZEPH Modify Parameters of Handover Due to Traffic Reason
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
ZEPI Modify Resource Indication Parameters
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
ZEPN Modify BTS Neighbourhood
Value range of paramater NO (object number) increased from 165535 to 1
999999.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

45 (72)
Feature 923

Value range of paramater NNO (neighbour object number) increased from 165535
to 1999999.
The object number and neighbour object number needs to be changed to be
handled as dword instead of word.
When added/removed neighbour BTS list is printed. In this printout we must allow
six digits to be outputted instead of existing 5 digits as the object number.
ZEPO Output BTS or Service Area Data
Value range of paramater NO (object number) increased from 165535 to 1
999999.
The object number needs to be changed to be handled as dword instead of word.
Neighbour BTS list is printed after BTS data (optional feature). In this printout we
must allow six digits to be outputted instead of existing 5 digits as the object number.
Optimisation changes (to speed up the interrogation of huge amount of BTS/SA
objects and to minimise OMU CPU load):
Interrogate one service (includes ranges output with && sign):
To message output_data_of_bts_req_s is added new release_hand field of bool
type. Currently each object number in the given range is interrogated one by one
(own hand in co PRB RNZPRB is reserved for each object interrogation). This is
optimised so that same RNZPRB hand will handle whole command execution of all
given ranges. With the new field release_hand in the request message MML will
indicate when all objects in all ranges are interrogated and RNZPRB can release its
hand process.
Furthermore in first request of a range the new field range_count is filled to indicate
the range (max 500) and in next request the range_count field is filled with 0xFFFF
to indicate a continuous search within a given range.
Interrogate all service:
To message output_data_of_bts_req_s and output_data_of_bts_resp_s is added
new last_handled_index field of record_number_t type. In first request message this
value is record_number_t_illegal_c. RNZPRB returns the record number where
returned object was found. MML sends this same record number in next request to
tell RNZPRB where to continue search for next reserved record.
Other changes:
-

check_sa_r4_compab_to_la_s (0xBD7D), object number change from word to


dword, not used in the code currently, but for possible future use good to change

Messages where object number change is visible due to datatype changes:


bts_create_req_s (0xC653),

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

46 (72)
Feature 923

bts_create_resp_s (0xC652),
bts_delete_req_s (0xC651),
bts_delete_resp_s (0xC650),
modify_bts_param_req_s (0xC649),
modify_bts_param_resp_s (0xC648),
output_data_of_bts_req_s (0xC647),
output_data_of_bts_resp_s (0xC646),
rne_change_bts_sac_state_s (0xD31B),
rne_change_bts_sac_state_ack_s (0xD31A),
modify_neigh_bts_list_req_s (0xC656),
modify_neigh_bts_list_resp_s (0xC654)
check_bts_or_sa_existence_s (0xBA8B)
check_bts_or_sa_exist_ack_s (0xBA8A)
8.3.9.17.2

LAHAND
ZELO Output Location Area Data
When outputting relation data of location areas the BTS/SA object number must
allow six digits to be outputted instead of existing 5 digits.
There seems to be no changes in LA relation service (message
output_rel_of_la_req_s). But the need for optimisation need to be verified by module
testing. After all, the BTS/SA amount is hugely increased.
ZELM Modify Auxiliary Location Area Data
The messages output_data_of_bts_req_s and output_data_of_bts_resp_s are
changed. This service is used to check that the given default Aux SA is attached to
this particular auxiliary LA. No functionality changes, just new fields in the
messages.
ZELJ Output Auxiliary Location Area Data
When outputting relation data of auxiliary location areas the auxiliary SA object
number must allow six digits to be outputted instead of existing 5 digits.
Other changes:
-

8.3.9.17.3

Messages where object number change is visible due to datatype changes:


check_bts_or_sa_existence_s (0xBA8B)
check_bts_or_sa_exist_ack_s (0xBA8A)

BCOHAN
ZEDO Output Cellular Network Controller Data
When outputting BTSs under BSC relation data, the BTS object number must allow
six digits to be outputted instead of existing 5 digits.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

47 (72)
Feature 923

Optimisation changes:
Furthermore the last handled BTS/SA object number in message
output_rel_of_bsc_req_s is changed to record number instead. In first request
message this value is record_number_t_illegal_c. And in next message the record
index is same as received in output_rel_of_bsc_resp_s from RNZPRB. In this way
RNZPRB can continue search from rec_nbr+1 instead of searching the last returned
BTS/SAC with rec_scan for each continuos search.

8.3.9.17.4

NRHAND
ZE3X Export Pool Area RN Configuration of MSS
The record amount of transfer files NPCFIL02 (BTS data) and NPCFIL04 (SA data)
is increased from 50 000 to 200 000. Furthermore the BTS/SA object number
changed from word to dword.
The default aux SA object number in transfer file NPCFIL05 (LA2 data) changed
from word to dword.
Exporting of big configuration takes some time so the exporting progress is
outputted to user as percentage of exported objects. The percentage represents the
% written of the theroetical maximum amount of objects. Example when max
amount of objects in file is 50 000, then when 5000 objects written we indicate that
10% written. So when importing 5001 objects (out of 50 000) we write 10% and then
jump right to 100%. BTS/SA object progress is indicated with 5% steps because of
the high amount.
Execution printout example:

E3X:DNAME=EXPORT:;
MSCi

MI091000

2011-03-16

23:31:17

RN CONFIGURATION EXPORTED
===========================================
POOL IDENTIFICATION:
POOL AREA NAME................. POOLNAME . : POOL1
MSS NAME....................... MSSNAME .. : MSS1
MSS CONFIGURATION TYPE......... CONFSEL .. : PRIMARY
EXPORTED OBJECTS:
LA LIST:
NAME
LA1
LA2
LA3

LAC
00001
00002
00003

MCC
123
123
45

MNC
321
321
30

AUX LA LIST:
NAME

LAC

MCC

MNC

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

48 (72)
Feature 923

NETWORK LA LIST:
LAC
65011

MCC
310

MNC
10

EXPORTING BTSs
100%
EXPORTING SAs AND AUXSAs
10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80% 85% 90% 95% 100%
EXPORTING BSCs
100%
EXPORTING RNCs
100%
TOTAL COUNT OF
LA.......
AUXLA....
NETLA....
SA.......
AUXSA....
BTS......
BSC......
RNC......

EXPORTED OBJECTS:
:3
:0
:1
:200000
:0
:0
:0
:1

COMMAND EXECUTED

ZE3Y Import Pool Area RN Configuration to MSS


The record amount of transfer files NPCFIL02 (BTS data) and NPCFIL04 (SA data)
is increased from 50 000 to 200 000. Furthermore the BTS/SA object number
changed from word to dword.
The default aux SA object number in transfer file NPCFIL05 (LA2 data) changed
from word to dword.
The temporary work file for BTS/SA objects is changed. The record amount of
temporary work file is increased from 50 000 to 200 000. And furthermore the
BTS/SA object number changed from word to dword.
In case of error in MML execution the problematic/conflicting object data is outputted
on screen. In this output the BTS/SA object number need to be outputted as 6 digits
instead of 5 digits.
Importing of big configuration takes some time so the exporting progress is
outputted to user as percentage of imported objects. The percentage represents the
% written of the theroetical maximum amount of objects. Example when max
amount of objects in file is 50 000, then when 5000 objects written we indicate that
10% written. So when importing 5001 objects (out of 50 000) we write 10% and then
jump right to 100%. BTS/SA object progress is indicated with 5% steps because of
the high amount.
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

49 (72)
Feature 923

Also the progress of RN import file creation is outputted to user.


Execution printout example:
E3Y:DNAME=EXPORT:;
MSCi

MI091000

2011-03-17

00:16:39

RN CONFIGURATION IMPORTED
===========================================
POOL IDENTIFICATION:
POOL AREA NAME................. POOLNAME . : POOL1
MSS NAME....................... MSSNAME .. : MSS1
MSS CONFIGURATION TYPE......... CONFSEL .. : PRIMARY
CREATING RN IMPORT FILES
LAFILE ... DONE
LA2FIL ... DONE
NLAFIL ... DONE
BTSFIL/CDAFIL/CECFIL ... DONE
BCTFIL/BCNIND ... DONE
RNBFIL ... DONE
IMPORTED OBJECTS:
LA LIST:
NAME
LA1
LA2
LA3

LAC
00001
00002
00003

MCC
123
123
45

MNC
321
321
30

AUX LA LIST:
NAME

LAC

MCC

MNC

LAC
65011

MCC
310

MNC
10

NETWORK LA LIST:
IMPORTING BTSs
100%
IMPORTING SAs AND AUXSAs
10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80% 85% 90% 95% 100%
IMPORTING BSCs
100%
IMPORTING RNCs
100%
TOTAL COUNT OF
LA.......
AUXLA....
NETLA....
SA.......
AUXSA....
BTS......
BSC......

IMPORTED OBJECTS:
:3
:0
:1
:200000
:0
:0
:0

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

50 (72)
Feature 923

RNC...... :1
COMMAND EXECUTED

ZE3V Activate RN Configuration of Pool Area


No changes.

8.3.10

NEMU

8.3.10.1

HLR/SRR Work Station (WS)

8.3.10.2

FSM/MVR

8.3.10.3

WS/SMM/ICP

8.3.10.4

N+X

8.3.10.5

CMDM

8.3.10.6

NEBS

8.3.11

Integrated MSC Server (MSS)

8.3.12

Standalone MSS and Gateway Control Server (GCS)

8.3.13

Circuit Switched Data Server (CDS)

8.3.14

CPS

8.3.15

HSS

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

51 (72)
Feature 923

9.

PROPOSED ENVIRONMENT DEFINITIONS

9.1

Services

9.1.1

Changes to old service definitions

9.1.2

New service definitions

9.1.2.1

[Service_name_as /_ss] provided by [XXXPRB] / [ZZZSEG]


Use of service
Service Interface
[in

Message_1_s (0x0000) ]

[out

Message_2_s (0x0000) ]

[in/out

Message_3_s (0x0000) ]

9.2

Messages

9.2.1

Changes to old message definitions

9.2.2

New message definitions

9.2.2.1

check_sa_r4_compab_to_la_s
Used by BTHAND MML.
signal check_sa_r4_compab_to_la_s = 0xBD7D
(
nbr_of_sac_ranges byte;
sacs
ARRAY (10) OF STRUCT
range_start_value object_number_t;
range_end_value
object_number_t;
ENDSTRUCT;
nbr_of_sanames byte;
sanames ARRAY (10) OF administ_name_t;
mgw
bsc_number_t;
mgwname administ_name_t;
lai
location_area_identification_t;
laname
administ_name_t;
);

9.2.2.2

--> Changed type


--> Changed type

output_rel_of_bsc_req_s
Used by BCOHAN MML & RNZPRB.
signal

output_rel_of_bsc_req_s = 0xCEB6

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

52 (72)
Feature 923

(
admin_number
relation_type
last_handled_bts_or_sac

bsc_number_t;
rne_la_rel_type_t;
record_number_t; --> Changed type

);

9.2.2.3

output_rel_of_bsc_resp_s
Used by BCOHAN MML & RNZPRB.
signal output_rel_of_bsc_resp_s = 0xC657
(
admin_number
bsc_number_t;
count
word;
bts_list
array (bts_basic_data_t_max_in_msg_c) of
bts_basic_data_t;
last_handled_bts_or_sac record_number_t; --> New field
status
error_t;
);
/************************ FIELD DESCRIPTIONS ***********************
...
LAST_HANDLED_BTS_OR_SAC
Record number of last BTS/SAC in bts_list. MML returns this in
next request so that co PRB can continue search from rec_nbr+1
STATUS
Status of executed operation. General dx error codes are
used as a status.
MORE_DATA_EC = message contains relation data to be printed.
NO_MORE_DATA_EC = end of message sequence.
*/

9.2.2.4

output_data_of_bts_req_s
Used by BTHAND & LAHAND MMLs & RNZPRB.
signal output_data_of_bts_req_s = 0xC647
(
rnobj_type
rnobj_type_t;
bts_identifiers
bts_identifiers_t;
ident_mask_array
bts_ident_mask_array_t;
bts_data_group
bts_data_group_t;
range_count
word;
--> New field
last_handled_index
record_number_t; --> New field
release_hand
bool; --> New field
);

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

53 (72)
Feature 923

/************************ FIELD DESCRIPTIONS ***********************


...
RANGE_COUNT
Relevant in interrogate BTS/SA ranges with &&-sign:
In this field is indicated the range count given. This is
relevant
in first message of a range interrogation.
Example: NO=200&&499 range given, then RANGE_COUNT=200
If a range is not given then this field is 0xFFFF.
LAST_HANDLED_INDEX
Relevant in interrogate all cases:
BTS or SAC record number index (depending on rnobj_type value),
which MML has already printed.
In first request message this value is
record_number_t_illegal_c.
RELEASE HAND
Relevant if interrogate ranges of objects:
To indicate when last object in the last range is outputted.
Set as T when the hand can be released. When F Co-PRB is
expected to receive more requests.
*/

9.2.2.5

output_data_of_bts_resp_s
Used by BTHAND & LAHAND MMLs & RNZPRB.
signal output_data_of_bts_resp_s = 0xC646
(
sac
bool;
adm_nbr_and_name
bts_adm_nbr_and_name_t;
parameters
bts_parameters_t;
count
byte;
neigh_bts_list
basic_neigh_lst_t;
last_handled_index
record_number_t; --> New field
status
error_t;
);
/************************ FIELD DESCRIPTIONS ***********************
...
LAST_HANDLED_INDEX
Record number index of returned BTS/SAC. MML returns this in

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

54 (72)
Feature 923

next request so that co PRB can continue search from rec_nbr+1.


*/

9.2.2.6

all_cells_msg_s
Used by BOBLIS, TRAMNT & RNZPRB.
signal all_cells_msg_s
(
more
count
all_cells
all_cells_name
);

= 0x2600
byte;
word;
array (150) of cgi_cell_nbr_t;
array (150) of cell_name_t;
--> New field

/************************ FIELD DESCRIPTIONS ***********************


...
ALL_CELLS_NAME
Array for cell names.
*/

9.2.2.7

check_bts_or_sa_existence_s
Used by BTHAND & LAHAND MMLs & RNZPRB.
signal check_bts_or_sa_existence_s = 0xBA8B
(
sa
bool;
bts_or_sa_nbr
object_number_t; --> Changed type
check_by_name
bool;
bts_or_sa_name
administ_name_t;
check_by_rec_nbr bool;
rec_nbr
record_number_t;
);

9.2.2.8

check_bts_or_sa_exist_ack_s
Used by BTHAND & LAHAND MMLs & RNZPRB.
signal check_bts_or_sa_exist_ack_s = 0xBA8A
(
sa
bool;
bts_or_sa_nbr
object_number_t; --> Changed type
bts_or_sa_name
administ_name_t;
bts_rec_nbr
record_number_t;
laf_rec_nbr_of_lai record_number_t;
ci
cell_identity_t;

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

status

55 (72)
Feature 923

error_t;

);

9.3

Types

9.3.1

Changes to old type definitions

9.3.1.1

Msc_int_cell_nbr_t
TYPE msc_int_cell_nbr_t
CONSTANT
not_def_c = 65535; 0xFFFFFFFF
REPRESENTATION
word; dword
ENDTYPE msc_int_cell_nbr_t
COMMENT '#E: MSC internal cell number (used only in MSC) '
'#F: MSC:n sis{inen solunumero (k{ytet{{n vain MSC:ss{) ';
This type definition is quite videly used in MSS. The effected
definitions are listed below. The definitions do not need changes as
such, but they will ease to identify needs for change in the code.

9.3.1.2

la_conf_data_t
Used by AIF_SSMX, CRM_SJMX & DTOLIBMX
TYPE la_conf_data_t
CONSTANT table_size_c = 297200;
REPRESENTATION
ARRAY (table_size_c) OF byte;
ENDTYPE la_conf_data_t;

9.3.1.3

changed from 114300 to 297200

Bts_adm_nbr_and_name_t
Used by BTHAND, LAHAND, RNEUPD & RNZPRB.
Used
in
bts_create_req_s,
bts_create_resp_s,
bts_delete_req_s,
bts_delete_resp_s,
modify_bts_param_req_s,
modify_bts_param_resp_s,
output_data_of_bts_resp_s,
rne_change_bts_sac_state_s,
rne_change_bts_sac_state_ack_s,
modify_neigh_bts_list_req_s
and
modify_neigh_bts_list_resp_s messages.
TYPE bts_adm_nbr_and_name_t
CONSTANT
p_cnt_c
= 2

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

56 (72)
Feature 923

COMMENT '#E: Count of bts identifiers.'


'#F: Bts:n tunnisteiden lukum{{r{.' ;
nbr_c
= 0;
name_c
= 1
COMMENT '#E: Identifications of bts number and name in mask
array.';
REPRESENTATION STRUCT
adm_bts_no
object_number_t --> Changed type
COMMENT '#E: Base transceiver station administrative number. '
'#F: Tukiaseman hallinnollinen numero.' ;
bts_name
administ_name_t
COMMENT '#E: Base transceiver station name.'
'#F: Tukiaseman nimi.' ;
ENDSTRUCT;
ENDTYPE bts_adm_nbr_and_name_t
COMMENT '#E: Administrative number and name of bts.'
'#F: Bts:n hallinnollinen numero ja nimi' ;

9.3.1.4

Bts_basic_data_t
Used by BCOHAN, BTHAND, LAHAND, RNEUPD & RNZPRB.
Used
in
bts_delete_resp_s,
output_data_of_bts_resp_s,
modify_neigh_bts_list_resp_s and output_rel_of_bsc_resp_s messages.
TYPE bts_basic_data_t
CONSTANT
max_in_msg_c = 52
COMMENT '#E: Count of bts basic data in bsc output.';
REPRESENTATION STRUCT
adm_bts_no
object_number_t --> Changed type
COMMENT '#E: Base transceiver station administrative number. ';
bts_name
administ_name_t
COMMENT '#E: Base transceiver station name.';
bts_state
element_state_t
COMMENT '#E: Base transceiver station state.';
lai
location_area_identification_t
COMMENT '#E: Location area identification.';
ci

cell_identity_t
COMMENT '#E: Cell identity.';

ENDSTRUCT;
ENDTYPE bts_basic_data_t
COMMENT '#E: Basic data of bts.';

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

9.3.1.5

57 (72)
Feature 923

Bts_identifiers_t
Used by BTHAND, LAHAND & RNZPRB.
Used in output_data_of_bts_req_s message.
TYPE bts_identifiers_t
CONSTANT
p_cnt_c
= 4
COMMENT '#E: Count of bts identifiers.'
'#F: Bts:n tunnisteiden lukum{{r{.' ;
nbr_c
= 0;
name_c
= 1;
cell_id_c
= 2;
la_id_c
= 3
COMMENT '#E: Identifications of bts identifiers in mask array.'
'#F: Bts:n tunnisteiden identifiointi
maskaustaulukossa.' ;
REPRESENTATION STRUCT
adm_bts_no
object_number_t --> Changed type
COMMENT '#E: Base transceiver station administrative number. '
'#F: Tukiaseman hallinnollinen numero.' ;
bts_name
administ_name_t
COMMENT '#E: Base transceiver station name.'
'#F: Tukiaseman nimi.' ;
ci
cell_identity_t
COMMENT '#E: Cell identity.'
'#F: Solunumero.' ;
lac
location_area_code_t
COMMENT '#E: Location area code.'
'#F: Sijaintialueen numero.' ;
ENDSTRUCT;
ENDTYPE bts_identifiers_t
COMMENT '#E: Indentifiers of bts.'
'#F: Bts:n tunnisteet' ;

9.3.1.6

Bts_data_in_la_t
Used by LAHAND & RNZPRB.
Used in output_rel_of_la_resp_s message. LAHAND MML & RNZPRB.
TYPE bts_data_in_la_t
CONSTANT
max_no_bts_c = 45
COMMENT '#E: Count of bts basic data in la output.'
'#F: Bts:n perustietojen lukum{{r{ la:n tulostuksessa.' ;
REPRESENTATION STRUCT
adm_bts_no
object_number_t --> Changed type
COMMENT '#E: Base transceiver station administrative number. '
'#F: Tukiaseman hallinnollinen numero.' ;

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

58 (72)
Feature 923

bts_name
administ_name_t
COMMENT '#E: Base transceiver station name.'
'#F: Tukiaseman nimi.' ;
bts_state
element_state_t
COMMENT '#E: Base transceiver station state.'
'#F: Tukiaseman tila.' ;
ci
cell_identity_t
COMMENT '#E: Cell identity.'
'#F: Solunumero.' ;
ENDSTRUCT;
ENDTYPE bts_data_in_la_t
COMMENT '#E: Bts data in la output.'
'#F: Bts:n tiedot la:n tulostuksessa' ;

9.3.1.7

Bts_data_t
Used by NRHAND.
This is defined in Multipoint related transfer file NPCFIL02.SDT. Not in sack!
TYPE bts_data_t
CONSTANT
max_cha_area_c

= 10;

REPRESENTATION
STRUCT
/* BTSFIL */
adm_bts_no
object_number_t --> Changed type
COMMENT '#E: BTS administrative number, '
'allowed value 1...0xF423F (1...999999).';
bts_name
administ_name_t
COMMENT '#E:BTS name, 10 ASCII-characters'
'in 15 bytes field.';
...
ENDSTRUCT;
ENDTYPE bts_data_t
COMMENT 'BTS data from BTSFIL, CDAFIL and CECFIL'
'Size of type: 175 bytes. ';
/* Record Structure */
TYPE npcfil02_t
REPRESENTATION UNION
npcfil_id
STRUCT
npcfil_id_and_chksum
ENDSTRUCT;
bts_cda_cec_data
STRUCT

npc_id_data_t;

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

59 (72)
Feature 923

bts_data
bts_data_t;
ENDSTRUCT;
ENDUNION;
ENDTYPE npcfil02_t
COMMENT 'BTS data from BTSFIL, CDAFIL and CECFIL'
'Size of record: 175 bytes.';

9.3.1.8

Sac_data_t
Used by NRHAND.
This is defined in Multipoint related transfer file NPCFIL04.SDT. Not in sack!
TYPE sac_data_t
CONSTANT
max_cha_area_c

= 10;

REPRESENTATION
STRUCT
/* BTSFIL */
adm_sa_no
object_number_t --> Changed type
COMMENT '#E: SA administrative number, '
'allowed value 1...0xF423F (1...999999).';
sa_name
administ_name_t
COMMENT '#E:SA name, 10 ASCII-characters'
'in 15 bytes field.';
...
ENDSTRUCT;
ENDTYPE sac_data_t
COMMENT 'SAC data from BTSFIL, CDAFIL and CECFIL'
'Size of type: 88 bytes. ';
/* Record Structure */
TYPE npcfil04_t
REPRESENTATION UNION
npcfil_id
STRUCT
npcfil_id_and_chksum
npc_id_data_t;
ENDSTRUCT;
bts_cda_cec_data
STRUCT
sac_data
sac_data_t;
ENDSTRUCT;
ENDUNION;
ENDTYPE npcfil04_t
COMMENT 'SAC data from BTSFIL, CDAFIL and CECFIL'
'Size of record: 88 bytes.';

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

9.3.1.9

60 (72)
Feature 923

La2_data_t
Used by NRHAND.
This is defined in Multipoint related transfer file NPCFIL05.SDT. Not in sack!
TYPE la2_data_t
REPRESENTATION
STRUCT
...
def_auxsa
object_number_t --> Changed type
COMMENT '#E: Default auxiliary SAs adm. number.';
...
ENDSTRUCT;
ENDTYPE la2_data_t
COMMENT 'LAC data from LA2FIL.'
'Size of type: 51 bytes. ';
/* Record Structure */
TYPE npcfil05_t
REPRESENTATION UNION
npcfil_id
STRUCT
npcfil_id_and_chksum
ENDSTRUCT;
la2fil_data
STRUCT
la2_data
ENDSTRUCT;
ENDUNION;
ENDTYPE npcfil05_t
COMMENT 'LAC data from LA2FIL. '
'Size of record: 51 bytes.';

9.3.1.10

npc_id_data_t;

la2_data_t;

sta_sub_data_t
Due to the change of the field first_int_cell_nbr with the type of msc_int_cell_nbr_t
(word dword) the spare bytes at the end of the structure shall be decreased:
TYPE sta_sub_data_t
REPRESENTATION STRUCT
imsi
imei

imsi_t;
imei_t;

/* Spares for future use. */


spare_b
ARRAY (5) OF byte; /* CHANGED */
spare_dw
ARRAY (4) OF dword;
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

61 (72)
Feature 923

ENDSTRUCT;
ENDTYPE sta_sub_data_t
COMMENT '#E:Call information for one subscriber in statistics';

9.3.2

New type definitions

9.3.2.1

Object_number_t
TYPE object_number_t
CONSTANT
not_def_c = 0x0;
max_cell_no_c = 999999;
REPRESENTATION dword;
ENDTYPE object_number_t
COMMENT '#E: Radio Network object number.';

9.3.2.2

Cell_name_t
TYPE cell_name_t
CONSTANT max_len = 10
REPRESENTATION array ( max_len ) of byte;
ENDTYPE cell_name_t
COMMENT '#E: Cell name.';

9.4

License

Feature name of the licence: Extended SA and Cell capacity in MSS


Feature Code: FCxxxx
Licence type: Capacity licence
Capacity step: 50 000.
Maximum capacity: 200 000
Basic capacity: 50 000 (without license)
Users: RNEUPD
Example: Capacity license limit activated with steps 2 (2x50 000). Overall SA/Cell
capacity is (50 000 + 2x50 000)=150 000 SAs/Cells.
Note that if customer has FC10568 with 65k SA/Cell capacity activated from M15.1
then this Capacity License overrule that PRFILE controlled intermediate capacity.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

62 (72)
Feature 923

The availability of extended administrative BTS/SA numbering range is generic and


requires no LICENSE activation (1-999999).

9.5

PRFILE Parameters

9.5.1

Changed parameters
No effect.

9.5.2

New parameters
No effect.

9.5.3

Used parameters
No effect.

9.6

Files
Increase of 3G SA / 2G Cell amount will increase also the file sizes. Record amount
variable will need now 4 octect instead of 2 octects. See chapter 5.2.7 for memory
consumtion calculations of file changes.
BTSFIL,CDAFIL, CERFIL, Z4FFIL, ZF7FIL, CEFFIL, HCALAR, BSBLIS, BSTRAF
and HM1LIS are affected files and therefore need a new file notification (FIDAS).
Following files uses MAX_BTS_AMOUNT constant in FIDAS: BTSFIL, CDAFIL,
CEFFIL, BSBLIS, BSTRAF
Following files are not using MAX_BTS_AMOUNT constant in FIDAS: HCALAR,
HM1LIS. In the new file notifications the record count shall be set to the
MAX_BTS_AMOUNT for these two files.
Describe the proposed changes and additions to environment definitions (DA). Note
that the proposed names used in IS don't need to be updated according to final ED

9.6.1

Changes to old file definitions

9.6.1.1

Btsfil_t
Used by NRHAND, LAEUPD, RNEUPD, RNZPRB, CRMPRB & CRHPRB.
This is defined in BTSFILMX.SDT.
TYPE btsfil_t
CONSTANT
dword_search_mask_c

= 0xFFFFFFFF;

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

word_search_mask_c
adm_bts_offset_c
bsc_offset_c
la_offset_c
ci_offset_c
state_offset_c
rnobj_type_offset_c
bsc_no_def_c

=
=
=
=
=
=
=
=

0xFFFF;
0x0;
0x13 COMMENT
0x15 COMMENT
0x17 COMMENT
0x19 COMMENT
0x72 COMMENT
0x0;

'#E:
'#E:
'#E:
'#E:
'#E:

63 (72)
Feature 923

Decimal
Decimal
Decimal
Decimal
Decimal

19';
21';
23';
25';
114';

-->
-->
-->
-->
-->

Changed
Changed
Changed
Changed
Changed

REPRESENTATION
STRUCT
adm_bts_no
object_number_t
--> Changed type
COMMENT '#E: Base transceiver station administrative number, '
'allowed value 1...0xF423F (1...999999).';
bts_name
administ_name_t
COMMENT '#E: Base transceiver station name, 10 ASCII-characters'
'in 15 bytes field.';
bsc_no
bsc_number_t
COMMENT '#E: Base station controller number, allowed value '
'1...0x0FFF (1...4095) or 0x0000 (undefined) or'
'0xFFFE (SA is in MSS-mode / Rel4, read rather'
'from rnobj_type field in M13).';
la_rec_nbr
word
COMMENT '#E: Record reference to location area in lafile'
'(BTS or SA) or la2fil (AUXSA), depends on'
'rnobj_type field. LAI (MCC+MNC+LAC) and CGI'
'can be read from same record number of CDAFIL'
'or from lafile/la2fil with this record index.';
ci

cell_identity_t
COMMENT '#E: Cell identity, allowed '
'values CI: 0...0xFFFF (0...65535).';

...
neigh_bts_list
adj_bts_list_t
--> size of type changed
COMMENT '#E: Neighbour base transceiver station list,'
'record index list, allowed values 0...0x30D3F'
'(0...199999) or 0xFFFFFFFF (undefined).';
rnobj_type
rnobj_type_t
COMMENT '#E: Indicates the type of the radio network object.'
'Fields meaning when type is other than bts:'
'- adm_bts_no = admin SA number'
'- bts_name
= admin SA name'
'- bsc_no
= MGW number, if SA is rel99'
'- la_rec_nbr = record number in LAFILE or'
'
LA2FIL, depends on SA type'
'- ci
= SA code, can be different than'
'
admin SA number.'
'- bts_state = SAC state';
File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

64 (72)
Feature 923

spare
bts_spare_t
COMMENT '#E: Reserved for future use';
ENDSTRUCT;
ENDTYPE btsfil_t;
TYPE btsfil_record_ptr_t
REPRESENTATION
POINTER FAR( btsfil_t );
ENDTYPE btsfil_record_ptr_t;
/* Abstract File Definition *****************************************/
ABSTRACT TYPE btsfil_f
REPRESENTATION
file_handle_t;
OPERATORS
...
r__adm_bts_number(
IN/OUT FAR adm_bts_number object_number_t, --> Changed type
IN
int_bts_number msc_int_cell_nbr_t
) -> error_t, FAR =>
COMMENT ' Function reads the administrative BTS (or SAC) number'
' to the user buffer according to the MSC internal cell
number ';
...
r__record_bts(
IN/OUT FAR buffer_ptr
btsfil_t,
IN
adm_bts_number object_number_t --> Changed type
) -> error_t, FAR =>
COMMENT ' Function reads a BTSFIL record to the user buffer'
' according administrative BTS/SA number.';
r__lac_ci_bts(
IN/OUT FAR la_rec_nbr
word,
IN/OUT FAR ci
cell_identity_t,
IN
adm_bts_number
object_number_t, --> Changed type
IN/OUT FAR rnobj_type
rnobj_type_t
) -> error_t, FAR =>
COMMENT ' Function reads the LA record number, CI and'
' rnobj_type to the user buffer according '
' the administrative BTS or SA number, '
' LAFILE/LA2FIL (focus of la_rec_nbr) can'
' be determinated with rnobj_type: '
' rnobj_type_t_auxsa_c means LA2FIL, '
' otherwise it is LAFILE.';
r__state_bts(
IN/OUT FAR bts_state

element_state_t,

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

65 (72)
Feature 923

IN
adm_bts_number object_number_t --> Changed type
) -> error_t, FAR =>
COMMENT ' Function reads the BTS (or SA) state to the user buffer'
' according to the administrative BTS/SA number ';
r__name_bts(
IN/OUT FAR name
byte,
IN
adm_bts_number object_number_t --> Changed type
) -> error_t, FAR =>
COMMENT ' Function reads the BTS (or SA) name to the user buffer'
' according to the administrative BTS/SA number.';
r__bsc_no_bts(
IN/OUT FAR bsc_no
bsc_number_t,
IN
adm_bts_number object_number_t --> Changed type
) -> error_t, FAR =>
COMMENT ' Function reads the number of the BSC (or AMO) which
controls'
' the BTS (or SA) in question. ';
...
ENDTYPE btsfil_f COMMENT 'Prefix "BTSFIL_F_" is added to all function
names.';

9.6.2

New file definitions

9.7

Alarms
No new alarms.

9.7.1

Changes to old alarm definitions

9.7.2

New alarm definitions

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

66 (72)
Feature 923

10.

HARDWARE CONSIDERATIONS AND CAPACITY CONSIDERATIONS

10.1

HW

10.1.1

HW Changes and requirements

10.1.2

HW Configuration and system maintenance

10.2

Capacity

10.2.1

CPU and MB capacity

10.2.2

Link capacity

10.2.3

I/O capacity

10.2.4

Process and resource considerations


See chapter 5.2.7 for memory calculations of file expansions.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

67 (72)
Feature 923

11.

SW CONFIGURATION, TESTING AND UPGRADE CONSIDERATIONS

11.1

SW Configuration management

11.2

Release upgrade considerations

11.2.1

Conversion programs

11.2.1.1

BTSCNVMX
The BTSFIL file changes require that the file is converted with BTSCNVMX during
upgrade.
- The administartive object number needs to be converted from word to dword.
- The neighbour BTS list record indexes needs to be convered from word to dword.

11.2.1.2

ZF4CNVMX
The msc_int_cell_nbr_t changes (WORD to DWORD) require that the ZF4FIL file is
converted with ZF4CNVMX during upgrade.
- The field int_cell_id of msc_inr_cell_nbr_t type needs to be converted from word to
dword.

11.2.1.3

ZF7CNVMX
The msc_int_cell_nbr_t changes (WORD to DWORD) require that the ZF7FIL file is
converted with ZF7CNVMX during upgrade.
- The field int_cell_id of msc_inr_cell_nbr_t type needs to be converted from word to
dword.

11.3

Feature testing information


Creating maximum radio network configuration is time consuming. One of the
biggest time consumers is the unlocking of BTS/SA objects. For each BTS/SA state
change CRMPRB will wait for 2s for acknowledgement from any AIFPRB
(BSU&GISU units). If no negative acknowledgement is received during this time then
the BTS/SA state change is accepted. This timer can however be set to 0s in test
environment to fasten the BTS/SA state change MML-commands.
Calculations:

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

68 (72)
Feature 923

Unlocking 200 000 BTS/SA objects with 2s timer causes a delay of approx. 111
hours (~4 days) compared to timer setting of 0s. Total unlocking time for 200 000
BTS/SA with 2s timer will take around 6 days. Wheras unlocking time with 0s will
take around 1 days. So saving in time is 4 days by just modifying the timer in
UTPFIL.
UTPFIL patch to modify the timer value:
1. Patch following two records to UTPFIL (file_id=5AC001D) in active CM unit and
distribute changes and update changes to disk. Wait for 1 minute for the timer
change to take effect.
a) General CRM timer checking patch (if some CRM timer is already controlled
with UTPFIL then this record already should exist with some max read timer
index):
31 01 = CRM pid
00 00 = index to indicate setting of max timer index
36 00 00 00 = Max read timer index (all timer indexes below this are read)
CM-0

FILE N:O 05AC001D RECORD N:O 00000000

31 01 00 00 36 00 00 00

1...6...

b) Timer (0x35) value patch:.


31 01 = CRM pid
35 00 = Timer index
00 00 00 00 = Timer value (0s)
CM-0

FILE N:O 05AC001D RECORD N:O 00000001

31 01 35 00 00 00 00 00

1.5.....

2. To set the timer 0x35 back to 2s either remove timer patch (with zeroes) or set
timer value to 2s (200ms=C8 in HEX)
CM-0

FILE N:O 05AC001D RECORD N:O 00000001

00 00 00 00 00 00 00 00

.....

or
CM-0

FILE N:O 05AC001D RECORD N:O 00000001

31 01 35 00 C8 00 00 00

11.3.1

1.5.....

Functional testing
-

Full radio network configuration needs to be verified. With the maximum 65530
SAs/Cells per location area.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

69 (72)
Feature 923

Multipoint related export/import functionality needs to be tested with maximum


radio network configuration. Execution will take several hours.

Statistics:

11.3.2

There should be tested the possibility to add the increased number of objects to
the Cell measurement.

It shall be tested that the Cell measurement is able to support the whole
increased range of cells.

It shall be tested that Cell Supervision, Handover Supervision and Handover


measurement report is able to handle any cell as object from the whole
increased range of cells.

Performance testing
Statistics:
During PET special attention should be paid to the load caused by the running
statistical measurement especially Cell measurement - with the increased number
of objects.

11.3.3

Delivery Verification
Not needed.

11.3.4

Release upgrade testing


BTSCNVMX, ZF4CNVMX and ZF7CNVMX conversion needs to be executed. And
file size expansions needs to be verified.

11.3.5

System Verification (SyVe)


Not needed.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

12.

70 (72)
Feature 923

RISKS

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

13.

71 (72)
Feature 923

ANNEXES

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>

IMPLEMENTATION SPECIFICATION
Company Confidential

NWS / VIPT R&D

72 (72)
Feature 923

DOCUMENT REVISION HISTORY


DATE: 08.02.2011
AUTHOR: Kaj Lahti
Summary of main
changes:

ISSUE: 0.1 draft


Approved by: <name>
Draft version.

DATE: 04.03.2011
AUTHOR: Kaj Lahti
Summary of main
changes:

ISSUE: 0.2 draft


Approved by: <name>
Application STA parts added.

DATE: 09.03.2011
AUTHOR: Kaj Lahti
Summary of main
changes:

ISSUE: 1.0
Approved by: <name>
First version stored to Sharenet.

DATE: 15.03.2011
AUTHOR: Kaj Lahti
Summary of main
changes:

ISSUE: 1.1
Approved by: <name>
Platform STA parts added + BOBLIS, RNZPRB and
NRHAND parts updated.

DATE: 06.06.2011
AUTHOR: Kaj Lahti
Summary of main
changes:

ISSUE: 1.2
Approved by: <name>
Modification of message
check_bts_or_sa_existence_s and
check_bts_or_sa_exist_ack_s added (BTHAND,
LAHAND and RNZPRB). + other minor updates.

File name:

Doc. status:

Author:

Approved by:

269159133.doc

1. 2

Kaj Lahti

<name>