call re report delpan1 final

Nokia Standard Document Template

TABLE OF CONTENTS

31.introduction

32.objective

33.feature overview

33.1Introduction

33.2GSM Specifications

44.counters and kpi

44.1TCH drop call %, area, real, before re-establishment, S3 (dcr_3i)

44.2TCH drop call %, area, real, after re-establishment, S7 (dcr_3j)

55.Parameter settings and implementation

55.1Phase-1 parameter settings



76.CDR generation in msc

77.analysis

77.1Drop Call Ratio

87.2Number of drops and TCH re-establishments

87.3Requests for Re-establishments

97.4SDCCH and TCH Blocking

98.conclusion

109.Appendix-I

1210. Appendix-II

1. introduction

Call Re-establishment is a standard feature in the Nokia BSS. The feature allows the MS to re-establish a connection after losing the radio link to the base station. The feature is supported by the MSC, which does not release the call after a radio link failure, and waits for the MS to re-establish a connection.

2. objective

The objective of the trial is to try the feature of call re-establishment in a limited area before deciding to implement it network-wide. The main objectives of the trial are listed below:

Test the usefulness of the feature in reducing the TCH drop call ratio

See the performance of call re-establishments

3. feature overview

3.1 Introduction

Call re-establishment allows a MS to re-establish a radio link to the BTS after the failure of a radio link. In such a case, the MSC does not release the circuits and thus gives time to the MS to reestablish the connection on the air interface to the same cell or to another cell. The feature allows call re-establishment to occur in case of a basic call as well as in case of a FACCH call setup. The information about whether call re-establishment is allowed in the cell is transmitted on the BCCH in System Information Messages under the RACH Control parameters.

Normally, the network and the MS notice the loss of radio connection at different times. Therefore the MSC may wait for the re-establishment request of the MS for a while before clearing the call. When the re-establishment request is received in the MSC, the connection is resumed, i.e. the ciphering mode and the channel mode are set to the same mode as in the previous connection, if possible. Otherwise the connection is released. The operator activates and deactivates call re-establishment.

Call re-establishment is not possible in the new MSC after an inter-MSC handover (unless the call is re-established back to the controlling MSC), because the IMSI of the mobile station is not transferred between the MSCs during an inter-MSC handover.

In case of MS attempting to re-establish a call, after receiving the IMMEDIATE_ASSIGNMENT message, the MS tunes to the assigned SDDCH channel and then sends a layer3 CM_SERVICE_REQUEST to the BSS. The establishment cause is specified as CM_Reestablishment_Request.

3.2 GSM Specifications

The GSM specifications 5.08, Chapter 6.7.2 describe the algorithm to be used by an MS in case it attempts a call-reestablishment:

In the event of a radio link failure, call reestablishment may be attempted (according to the procedure in GSM04.08). The MS shall perform the following algorithm to determine which cell to use for the call reestablishment attempt.

i)The received level measurement samples taken on the carriers indicated in the BA (SACCH) received on the serving cell and on the serving cell BCCH carrier in the last 5seconds shall be averaged, and the carrier with the highest average received level with a permitted NCC as indicated on the SACCH of the serving cell (see subclause7.2) shall be taken.

ii)On this carrier the MS shall attempt to decode the BCCH data block containing the parameters affecting cell selection.

iii)If the parameter C1 is greater than zero, it is part of the selected PLMN, the cell is not barred, and call reestablishment is allowed, call reestablishment shall be attempted on this cell.

iv)If the MS is unable to decode the BCCH data block or if the conditions in iii) are not met, the carrier with the next highest average received level with a permitted NCC shall be taken, and the MS shall repeat steps ii) and iii) above.

v)If the cells with the 6strongest average received level values with a permitted NCC have been tried but cannot be used, the call reestablishment attempt shall be abandoned, and the algorithm of subclause6.7.1 shall be performed.

The mobile station is under no circumstances allowed to access a cell to attempt call reestablishment later than 20 seconds after the detection within the mobile station of the radio link failure causing the call reestablishment attempt. In the case where the 20 seconds elapses without a successful call reestablishment the call reestablishment attempt shall be abandoned, and the algorithm of subclause6.7.1 shall be performed.

4. counters and kpi

There is a different formula (dcr_3j) for TCH drop call ratio that takes the call re-establishments into account. All the KPIs are collected from the Network Doctor report #204, which runs in the NMS cron job everyday for the BSC.

4.1 TCH drop call %, area, real, before re-establishment, S3 (dcr_3i)

The KPI indicates how much % of calls is dropped after TCH seizure.

Formula:

100-csf_4u =

. sum(tch_radio_fail+tch_rf_old_ho+tch_abis_fail_call+tch_abis_fail_old+

. tch_a_if_fail_call+tch_a_if_fail_old+tch_tr_fail+tch_tr_fail_old+

. tch_lapd_fail+tch_bts_fail+tch_user_act+tch_bcsu_reset+tch_netw_act+

. tch_act_fail_call)

100* ---------------------------------------------------------------------------- %

sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch) ;(DR calls)

-sum(a.tch_succ_seiz_for_dir_acc) ;ref.1

+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup

Counters from table(s):

a = p_nbsc_traffic

c = p_nbsc_ho

Ref.1. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.4.2 TCH drop call %, area, real, after re-establishment, S7 (dcr_3j)

The formula gives the drop call ratio of TCH after taking call-reestablishments into account.

Formula:

100-csf_4v =

. sum(tch_radio_fail+tch_rf_old_ho+tch_abis_fail_call+tch_abis_fail_old+

. tch_a_if_fail_call+tch_a_if_fail_old+tch_tr_fail+tch_tr_fail_old+

. tch_lapd_fail+tch_bts_fail+tch_user_act+tch_bcsu_reset+tch_netw_act+

. tch_act_fail_call

- sum(b.tch_re_est_assign) ;(call re-establishments)100* ---------------------------------------------------------------------------- %

sum(a.tch_norm_seiz) ;(normal calls)

+ sum(c.msc_i_sdcch_tch+c.bsc_i_sdcch_tch+c.cell_sdcch_tch) ;(DR calls)

-sum(a.succ_tch_seiz_for_dir_acc) ;ref.2

+ sum(a.tch_seiz_due_sdcch_con) ; calls started as FACCH call setup

- sum(b.tch_re_est_assign) ;(call re-establishments)

Counters from table(s):

a = p_nbsc_traffic

b = p_nbsc_service

c = p_nbsc_hoRef.2. Compensation needed since in case of Direct Access to super reuse TRX the tch_norm_seiz is triggered in parallel with cell_sdcch_tch.5. Parameter settings and implementation

5.1 Phase-1 parameter settings

The following parameter setting was done in Phase-1 of the trial. These were implemented on the night of 28-29 Jan, 2002.

In phase-1, the call re-establishment was enabled in all cells of BSC DELPAN1. The list these cells is listed in Appendix-I. The above setting means that the MSC waits for 10 sec for the MS to re-establish a call before releasing the circuits.


The following parameter setting was done in Phase-2 of the trial. These were implemented on the night of 2-3 Feb, 2002.

The change in parameters from Phase-1 is in the adjacent cell parameters. Call RE was enabled in all cells adjacent to cells in BSC Delpan1 and belonging to the same BSC as Delpan1. This was done considering that in a network wide call re-establishment scenario, all neighboring cells would have call RE enabled, thus giving the MS a chance to re-establish call on the best available cell from among the adjacent cell list.


The following parameter setting was done in Phase-2 of the trial. These were implemented on the night of 7-8Feb, 2002.

The BTS and adjacent parameter settings from Phase-2 were retained while the MAX WAIT TIME OF RE-ESTABL REQ in the MSC was changed from 10 sec to 15 sec. The change was done to see the effect on the number of re-establishments as well as on the success rate of SDCCH to TCH assignments in case of call re-establishments.

6. CDR generation in msc

An issue regarding the CDR (charging data record) generation in the MSC was raised by Globe before the trial begun. It was to be confirmed in case of call re-establishment that:

1. Only one CDR is generated for the call that is re-established.

2. The time from the detection of radio link failure to the time the MS re-establishes a call on TCH, is not charged to the subscriber.

Globes Data Transcript & Testing dept carried out a trial to confirm the above. It was found that from the time MSC detects a radio link failure (but does not release the circuit since call RE is enabled in the cell), to the time the MS re-establishes a call on the TCH, the MSC stops the charging pulses for that call. Thus it was noticed that only one CDR record is generated for the particular call and the charging time is less than the difference between the charging-start and charging-end timings. A copy of the detailed report from Globe is attached in the Appendix-II as a reference.

7. analysis

7.1 Drop Call Ratio

The difference in the two drop call ratio formulae was observed to be 0.06% in the Phase-1. This denotes the reduction in the overall drop call ratio after the implementation of call RE. A similar value of 0.05% was observed in the Phase-2. However, after the change of timer in the MSC in Phase-3, this value increased to an average of 0.08%. This can be attributed to the improvement in the SDCCH to TCH allocation success rate for the SDCCH/TCH seizures due to call RE.

The SDCCH to TCH allocation success rate, which was about 35%, increased to 49% in Phase-3. The increased timer value in phase-3 allows the MSC to wait longer for the MS to appear on the TCH.

7.2 Number of drops and TCH re-establishments

The above chart compares the number of TCH seizures for RE with the number of TCH drops. The number of TCH drops is the product of Number of Calls and the drop call ratio (dcr_3i). It is seen that about 2.5% of the TCH drops were being re-established in Phase-1 and Phase-2. In Phase-3, this value increased to about 3.4%.7.3 Requests for Re-establishments

The requests for re-establishments did not change significantly over the three phases of the trial. Note that in Ph-3 the number of TCH seizures for call RE went up even thought the number of SDCCH seized for call RE has remained the same.

7.4 SDCCH and TCH Blocking

The blocking figures on SDCCH and TCH were observed after the call re-establishment was enabled. The implementation of call-RE did not lead to an increase in these figures. This is because the number of SDCCH/TCH re-establishments is a very small percentage of the total seizures. This value is only 0.03% for SDCCH and 0.04% for TCH seizures.

8. conclusionThe trial for call re-establishment improved the TCH drop call ratio by 0.07% to 0.08% points across the whole BSC area. The other KPIs did not degrade or maintained their trend. Considering the positive results of the trial, it is recommended that:

1. Call Re-establishment be implemented across the whole network in a phased manner. It may be enabled on MSC-by-MSC-area basis.

2. The timer MAX WAIT TIME FOR RE-ESTAB REQ in all the MSCs be set to 15 sec.

9. Appendix-I

List of Cells in BSC DELPAN1 where call RE was enabled:

NMSMSCbsc_idbcf_idbsc_namebts_idcell_idbts_namela_id_lac

PIONEER1MSCVC4486881DELPAN1111030DELPAN11002



PIONEER1MSCVC4486884DELPAN1412030DELPANX11002



PIONEER1MSCVC4486887DELPAN1711046MADRID11002

PIONEER1MSCVC4486887DELPAN1821046MADRID21002

PIONEER1MSCVC44868810DELPAN11012046MADRIDX11002

PIONEER1MSCVC44868810DELPAN11122046MADRIDX21002

PIONEER1MSCVC44868813DELPAN11311048MORIONES11002



PIONEER1MSCVC44868816DELPAN11611016NORHARBOR11002



PIONEER1MSCVC44868819DELPAN11912016NORHARBOX11002



PIONEER1MSCVC44868822DELPAN12211012SOUHARBOR11002



PIONEER1MSCVC44868825DELPAN12511007DIVISORIA11002



PIONEER1MSCVC44868828DELPAN12812007DIVISORIAX11002



PIONEER1MSCVC44868831DELPAN13111025ELCANO11002

PIONEER1MSCVC44868831DELPAN13221025ELCANO21002

PIONEER1MSCVC44868834DELPAN13411026JUANLUNA11002

PIONEER1MSCVC44868834DELPAN13521026JUANLUNA21002

PIONEER1MSCVC44868837DELPAN13721057STOCRISTO21002

PIONEER1MSCVC44868840DELPAN14011021TUTUBAN11002



PIONEER1MSCVC44868843DELPAN14312021TUTUBANX11002



PIONEER1MSCVC44868846DELPAN14631060YLAYA31002

PIONEER1MSCVC44868849DELPAN14919018CENTERMAL11002

PIONEER1MSCVC44868852DELPAN15211024ASUNCION11002

PIONEER1MSCVC44868852DELPAN15321024ASUNCION21002

PIONEER1MSCVC44868855DELPAN15512024ASUNCIONX11002

PIONEER1MSCVC44868855DELPAN15622024ASUNCIONX21002

PIONEER1MSCVC44868858DELPAN15811001BINONDO11002



PIONEER1MSCVC44868861DELPAN16112001BINONDOX11002



PIONEER1tiMSCVC44868864DELPAN16411037CONDESA11002

PIONEER1MSCVC44868866DELPAN16631037CONDESA31002

PIONEER1MSCVC44868867DELPAN16719016EQUIBINON11002

PIONEER1MSCVC44868873DELPAN17311051PAREDES11002

PIONEER1MSCVC44868874DELPAN17421051PAREDES21002

PIONEER1MSCVC44868876DELPAN17611027REGENTE11002

PIONEER1MSCVC44868876DELPAN17731027REGENTE31002

PIONEER1MSCVC44868879DELPAN17912027REGENTEX11002

PIONEER1MSCVC44868879DELPAN18032027REGENTEX31002

PIONEER1MSCVC4486882DELPAN18112012SOHARBORX11002



PIONEER1MSCVC4486883DELPAN18412048MORIONESX11002



< Back to Phase-1 Parameter Settings

10. Appendix-II

Report on CDR generation in case of call re-establishment Data Transcript and Testing Dept, Globe Telecom:

< Back to CDR Generation in MSC

Call Re-establishment Trial

For

Globe Telecom

Week4 Week7, 2002

NOKIA

Ph-1

Ph-2

Ph-3

Ph-1

Ph-2

Ph-3

Ph-1

Ph-1

Ph-2

Ph-3

Ph-2

Ph-3

_1075525586.doc

Reference No.

D&T-REP-01-2002

Subject

DATA AND TESTING REPORT

Date Report

16/01/2002

Title

VERIFICATION REPORT : CDR GENERATION FOR CALL RE-ESTABLISHMENT

Page 4 of 5

REV.

DATE

DETAIL

PREPARED BY

NOTED BY

16-Jan-2002

Anthony Del Rosario

Data Transcript & Testing BSS Section

Investigation:

Anthony Del Rosario

Oliver Blando

Manuel Lorico

Data Transcripts & Testing BSS Section

Anthony F. Mangaliman

Data Transcript & Testing Manager

IIntroduction

IIObjective

III Presentation and Analysis of Findings

IV Annexes

I.INTRODUCTION

The BSC has a feature called Call Re-establishment. This is a feature designed to facilitate the reconnection of the Air (Um) interface once radio link connection is lost before NSS circuits are released.

Since NSS circuits will not be released, it is theorized that the Charging Data Record (CDR) for that particular call will not be closed for another to be opened for a re-connected call.

II. OBJECTIVE

The objective of this investigation is to verify if there will be only one CDR for a call that has gone through several call re-establishments.

III.PRESENTATION and ANALYSIS OF FINDINGS

To simulate a scenario wherein a radio-link between the mobile station (MS) and the Base Station (BS) will fade to the noise floor (>-100 dBm) without the possibility of a handover, the simulation was done on a Testbed. The MS was locked to the frequency of the Test BTS and it was gradually moved farther from the BTS until radio-link was no longer possible. To have a cue for this no radio-link situation, an Air-Interface test equipment (TEMS) was used to view protocol messages and RF conditions relating to radio link disconnection. Audio cues (dead air) was also used to verify that the radio link is lost. After the cues had been received, the timer Radio Link Timeout (RLT) was permitted to expire and the MS was then moved to a location of higher signal strength to facilitate radio link reconnection (call re-establishment). After the said procedures are done, the charging data record (CDR) for that particular call was extracted and examined. There should only be one CDR that will be generated since the same NSS (Switching) resources was used as it was not released in the first place.

For this particular testing, we came up with an air-interface trace with a call re-establishment message, see figure 1. The CDR for this particular call was extracted. And as expected, only one CDR was produced for a call that has undergone a call re-establishment procedure. An MSC trace was also extracted to confirm that a call re-establishment procedure had indeed occurred.

ANNEXES

Figure 1

( Back

Figure 2

Generated CDR

Record length : 223 (dec) df (hex)

MOC_RECORD_TYPE, ( 2) 01

MOC_RECORD_NUMBER, ( 3) 02603906

MOC_RECORD_STATUS, ( 7) 00

MOC_CHECK_SUM, ( 8) 530c

MOC_CALL_REFERENCE, ( 10) 41380035aa

MOC_EXCHANGE_ID, ( 15) 639170000007ffffffff

MOC_INTERMEDIATE_RECORD_NUMBER, ( 25) 00

MOC_INTERMEDIATE_CHARGING_IND, ( 26) 00

MOC_NUMBER_OF_SS_RECORDS, ( 27) 00

MOC_CALLING_IMSI, ( 28) 515020200192074f

MOC_A_SUBSCRIBER_IMEI, ( 36) 520329510233870f

MOC_A_SUBSCRIBER_NUMBER, ( 44) 639176888951ffffffff

MOC_CALLING_CATEGORY, ( 54) 00

MOC_CALLING_MS_CLASSMARK, ( 55) 03

MOC_CALLED_IMSI, ( 56) 515020100199800f

MOC_B_SUBSCRIBER_IMEI, ( 64) 520329510038910f

MOC_B_TYPE_OF_NUMBER, ( 72) 06

MOC_CALLED_NUMBER, ( 73) 9175880619ffffffffffffff

MOC_CALLED_CATEGORY, ( 85) 00

MOC_CALLED_MS_CLASSMARK, ( 86) 03

MOC_DIALLED_DIGITS, ( 87) 09175880619fffffffffffff

MOC_A_SUBS_FIRST_LOC_LAI, ( 99) 0063

MOC_A_SUBS_FIRST_LOC_CELL_ID, (101) b1f3

MOC_A_SUBS_LAST_LOC_EX_ID, (103) 639170000007ffffffff

MOC_A_SUBS_LAST_LOC_LAI, (113) 0063

MOC_A_SUBS_LAST_LOC_CELL_ID, (115) b1f3

MOC_B_SUBS_FIRST_LOC_LAI, (117) 0063

MOC_B_SUBS_FIRST_LOC_CELL_ID, (119) b1f3

MOC_B_SUBS_LAST_LOC_EX_ID, (121) 639170000007ffffffff

MOC_B_SUBS_LAST_LOC_LAI, (131) 0063

MOC_B_SUBS_LAST_LOC_CELL_ID, (133) b1f3

MOC_OUT_CIRCUIT_GROUP_NR, (135) 0390

MOC_OUT_CIRCUIT_NR, (137) 0012

MOC_BASIC_SERVICE_TYPE, (139) 00

MOC_BASIC_SERVICE_CODE, (140) 11

MOC_FACILITY_USAGE, (141) 00ff

MOC_NON_TRANSPARENCY_IND, (143) ff

MOC_CHANNEL_RATE_INDICATOR, (144) 38

MOC_SET_UP_START_TIME, (145) 17:29.11,11-01-2002

MOC_IN_CHANNEL_ALLOCATED_TIME, (152) 17:29.12,11-01-2002

MOC_CHARGING_START_TIME, (159) 17:29.20,11-01-2002

MOC_CHARGING_END_TIME, (166) 17:32.06,11-01-2002

MOC_ORIG_MCZ_DURATION, (173) 000157

MOC_SUCCESS_INDICATOR, (176) 00000000

MOC_ORIG_MCZ_CHRG_TYPE, (180) 0000

MOC_CALL_TYPE, (182) 03

MOC_ORIG_MCZ_TARIFF_CLASS, (183) 000012

MOC_ORIG_MCZ_PULSES, (186) 0000

MOC_DTMF_INDICATOR, (188) 00

MOC_AOC_INDICATOR, (189) 00

MOC_DD_TYPE_OF_NUMBER, (190) 04

MOC_PNI, (191) ffffff

MOC_REDIRECTED_INDICATOR, (194) 00

MOC_CALLED_MSRN_TON, (195) 06

MOC_CALLED_MSRN, (196) 9170007801ffffffffffffff

MOC_LOC_LAI_A_SUBS_CHARGING_AREA, (208) ffff

MOC_CALLED_CHARGING_AREA, (210) ffff

MOC_CALLING_NUMBER_TON, (212) 05

MOC_CUG_INTERLOCK, (213) ffffffff

MOC_CUG_OUTGOING_ACCESS, (217) ff

MOC_NUMBER_OF_IN_RECORDS, (218) 00

MOC_REGIONAL_SUBS_INDICATOR, (219) ff

MOC_REGIONAL_SUBS_LOCATION_TYPE, (220) ff

MOC_ROUTING_CATEGORY, (221) 00

MOC_SPEECH_VERSION, (222) 02

( Back

Figure 3

Call Re-establishment message as seen on the MSC Trace

MAIN LEVEL COMMAND

DX 200 MSCMR4 2002-01-11 17:31:03

MSC OBSERVATION REPORT FROM STU-1

REPORTING TIME : 2002-01-11 17:31:03.77

REPORT NUMBER : 000004

TRACED IMSI : 515020200192074

TRACING REFERENCE : 00002

OMC ID : 1

TRACE TYPE : ALL, BASIC, UNPRIOR

TRACE TYPE USED : ALL, BASIC, UNPRIOR

START TIME : 2002-01-11 17:31:03.77

END TIME : 2002-01-11 17:31:03.77

RECORDING ENTITY : 639170000007

REPORT REASON : EVENT

INVOKING EVENT : HANDOVER

HO OBS. TYPE : SUBSCRIBER OBSERVATION

OBJECT SUBSCRIBER

IMSI NUMBER : 515020200192074

IMEI NUMBER : 520329510233870

HANDOVER

TYPE : CALL RE-ESTABLISHMENT

TIME : 2002-01-11 17:31:03.77 DURATION(ms) : 8920

REASON : RADIO IF FAILURE

RESULT : SUCCESSFUL

LAC CI PCM TSL TYPE

OLD CHANNEL : 00099 45555 0972 13

NEW CHANNEL : 00099 45555 0972 15 FULL

NEIGHBOUR LIST :

END OF REPORT

DX 200 MSCMR4 2002-01-11 17:32:06

MSC OBSERVATION REPORT FROM STU-1

REPORTING TIME : 2002-01-11 17:32:06.53

REPORT NUMBER : 035023

TRACED IMSI : 515020200192074

TRACING REFERENCE : 00002

OMC ID : 1

TRACE TYPE : ALL, BASIC, UNPRIOR

TRACE TYPE USED : ALL, BASIC, UNPRIOR

START TIME : 2002-01-11 17:29:12.65

END TIME : 2002-01-11 17:32:06.35

RECORDING ENTITY : 639170000007

REPORT REASON : EVENT

INVOKING EVENT : SUBS(A)

CALL ID : 02C7H-56C2H-401DH-4138H-0035H-AAH-05E9H-A2H

CALL START : 2002-01-11 17:29:12.65 CALL PHASE : RELEASE

SIGNALLING COMPLETE : 2002-01-11 17:29:16.09 STAT STATE : IDLE

ANSWER : 2002-01-11 17:29:20.64 CLEAR CODE : 0000H

CHARGING END : 2002-01-11 17:32:06.35 CLEAR INFO : AIF_SS 0001H 0B2FH

PAGING TIME : 1430 CLEAR PART : SUB B

EXT CLEAR CODE : 0010H SIGNALLING : MS CC

EXTERNAL FORWARDING COUNTER : 0

CALLING NUMBER : I 639176888951

CALLED NUMBER : N 9175880619

OUT PULSED NUMBER : I 639175880619

CONNECTED NUMBER : I 639175880619

ROAMING NUMBER : N 9170007801

ADDRESS NUMBER : U 09175880619

OBJECT SUBSCRIBER A (TRACED) SUBSCRIBER B

IMSI : 515020200192074 515020100199800

IMEI : 52032951023387 52032951003891

CGR/BSC/PCM-TSL : 0390/0100/0972-15 0390/0100/0972-12

LAC/CI/CELL BAND : 00099/45555/GSM 00099/45555/GSM

CHANNEL RATE : FRP / / FR FR2 / / FR

SPEECH VERSION : FR2 FR2

PRIORITY : 3 3

MS CLASSMARK : 3 DUAL BAND 3 DUAL BAND

END OF REPORT

( Back

FILENAME :

d&t Rep 01 CDR Generation on Call Re-establishment.doc

Page18.02.02

_935227290.doc

call re report delpan1 final

Documents