Вы находитесь на странице: 1из 14

CHANGE REQUEST

FORM

1 (14)

NET/GSM/EDGE BSS R&D

BSS PARAMETER CHANGE REQUEST for release S12


(This process and template concerns only parameters in BSDATA-database in BSC)

CHANGE INFORMATION
Owner:
CRQ Status:
CRQ ID #:
Document ID:
Final location:

Vesa Krkkinen / Seulanto Henri


Approved
1028
340456059.doc
http://xeswww001.ext.nokia.com:8080/pddb < Release >< Version >

CHANGE REQUEST HISTORY

1.

Issue

Date

Handled by

Comments

0.0.1
0.0.2
0.0.3

5.6.2007
29.6.2007
11.7.2007

Vesa Krkkinen
Vesa Krkkinen
Seulanto Henri

0.1.0
1.0.0

31.7.2007
15.8.2007

Seulanto Henri
Seulanto Henri

First draft
BSC > schedulingWeight parameters removed
Add update from Parameter document; related
feature information update (BSS20106
information removed)
Review
Minor correction in 3.4.1

INTRODUCTION AND REFERENCES

CRQ TITLE: S12 CRQ1028


RELATED S-RELEASE PROGRAM CR (ID): No S12 CR. S12 Internal findings +
PR: 32765ES09P

Nature of the Change: Internal corrections


Reason for the change: Fault corrections

CRQ Template

CHANGE REQUEST
FORM

2 (14)

NET/GSM/EDGE BSS R&D

Additional information: [e.g. email conversations, attachments]


S12 CRs in PI
The CRQs are stored in the PI.
Intranet: PDDB CRQ approved
Extranet: PDDB CRQ approved
Comments:

VS EQOS parametri
VS VS EQOS
VS VS PR
FW BSC
C:\USERS\RE RAC#7
ongelma FB validoinnissa.em
param
l etri ongelma FB validoinnissa.em
33173ES09P FBPP
l
Error
pieToSubscriberType.em
during provisioning when
Regression
l setting DTM
E104677
to YES.em
NOK lstate report.

CRQ Template

CHANGE REQUEST
FORM

3 (14)

NET/GSM/EDGE BSS R&D

CONTENTS
CHANGE INFORMATION..................................................................................................................... 1
Change Request History....................................................................................................................... 1
1. Introduction and References.........................................................................................................1
2. NEW parameter(s)........................................................................................................................ 4
2.1
< Managed object class name >...........................................................................................4
2.1.1
< parameter abbrevName (Full Name) >.........................................................................4
3. MODIFIED parameter(s)...............................................................................................................5
3.1
BSC........................................................................................................................................ 5
3.1.1
pieToSubscriberType (Subscriber Type)..........................................................................5
3.1.2
inactCriteria (EGPRS Inactivity Criteria)..........................................................................5
3.1.3
inactEventsPerHour (Events Per Hour For EGPRS Inactivity Alarm)...............................5
3.1.4
supervisionPeriod (Supervision Period Length For EGPRS Inactivity Alarm)...................5
3.2
BTS........................................................................................................................................ 6
3.2.1
transportType (Transport Type)........................................................................................6
3.2.2
inactEndTimeHour (EGPRS Inactivity Alarm End Time Hour)..........................................6
3.2.3
inactEndTimeMinute (EGPRS Inactivity Alarm End Time Minute)....................................6
3.2.4
inactStartTimeHour (EGPRS Inactivity Alarm Start Time Hour).......................................6
3.2.5
inactStartTimeMinute (EGPRS Inactivity Alarm Start Time Minute).................................7
3.2.6
inactWeekDays (EGPRS Inactivity Alarm Weekdays)......................................................7
3.2.7
pcuIdentifier (PCU Identifier)...........................................................................................7
3.2.8
psei (Packet Service Entity Identifier)..............................................................................7
3.2.9
cs3Cs4Enabled (Coding Schemes CS3 And CS4 Enabled)............................................7
3.3
DAP........................................................................................................................................ 9
3.3.1
bcsuID (BCSU ID)........................................................................................................... 9
3.3.2
psei (Packet Service Entity Identifier)..............................................................................9
3.4
LAPD...................................................................................................................................... 9
3.4.1
abisSigChannelSubSlot (Sub TSL)..................................................................................9
3.5
NSE...................................................................................................................................... 10
3.5.1
nsEntityId (NSEI)........................................................................................................... 10
3.5.2
psei (Packet Service Entity Identifier)............................................................................10
3.6
PCU...................................................................................................................................... 10
3.6.1
bcsuID (BCSU ID)......................................................................................................... 10
3.6.2
gbIfType (GB Interface Type).........................................................................................11
3.6.3
pcuID (PCU Index).........................................................................................................11
3.6.4
pcuIdentifier (PCU Identifier)..........................................................................................11
3.6.5
pcuRearrangeEnabled (Rearrange Enabled).................................................................11
3.6.6
piuType (Plug-in Unit Type)............................................................................................11
3.6.7
psei (Packet Service Entity Identifier).............................................................................11
3.7
RA........................................................................................................................................ 12
3.7.1
psei (Packet Service Entity Identifier)............................................................................12
4. DELETED parameter(s):............................................................................................................. 12
4.1
< Managed object class name >..........................................................................................12
4.1.1
< parameter abbrevName (Full Name) >.......................................................................12
5. Guidelines................................................................................................................................... 13

CRQ Template

CHANGE REQUEST
FORM
NET/GSM/EDGE BSS R&D
2.

NEW PARAMETER(S)

2.1

< Managed object class name >

2.1.1

< parameter abbrevName (Full Name) >

CRQ Template

4 (14)

CHANGE REQUEST
FORM

5 (14)

NET/GSM/EDGE BSS R&D


3.

MODIFIED PARAMETER(S)

3.1

BSC

3.1.1

pieToSubscriberType (Subscriber Type)

3.1.2

3.1.3

3.1.4

Parameter
Dictionary field

Current value

Proposed value

Notes

Required on creation:

mandatory

Optional

PR: 32765ES09P

inactCriteria (EGPRS Inactivity Criteria)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

inactEventsPerHour (Events Per Hour For EGPRS Inactivity Alarm)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

supervisionPeriod (Supervision Period Length For EGPRS Inactivity Alarm)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

CRQ Template

CHANGE REQUEST
FORM

6 (14)

NET/GSM/EDGE BSS R&D


3.2

BTS

3.2.1

transportType (Transport Type)

3.2.2

3.2.3

3.2.4

Parameter
Dictionary field

Current value

Proposed value

Default value:

255

Notes

inactEndTimeHour (EGPRS Inactivity Alarm End Time Hour)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

inactEndTimeMinute (EGPRS Inactivity Alarm End Time Minute)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

inactStartTimeHour (EGPRS Inactivity Alarm Start Time Hour)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

CRQ Template

CHANGE REQUEST
FORM

7 (14)

NET/GSM/EDGE BSS R&D

3.2.5

3.2.6

3.2.7

3.2.8

3.2.9

inactStartTimeMinute (EGPRS Inactivity Alarm Start Time Minute)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

inactWeekDays (EGPRS Inactivity Alarm Weekdays)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20071: PCU
Performance
Optimization
(standard) AND
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSC GPRS Param


Enabled (GPRS O&M in
BSC) (39) (optional)
BSS20062: (E)GPRS
Inactivity Alarm / DXpart (standard)

BSS20071 is not
visible to customer
is S12

pcuIdentifier (PCU Identifier)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

psei (Packet Service Entity Identifier)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

cs3Cs4Enabled (Coding Schemes CS3 And CS4 Enabled)

Parameter
Dictionary field
CRQ Template

Current value

Proposed value

Notes

CHANGE REQUEST
FORM
NET/GSM/EDGE BSS R&D
Description

CRQ Template

With this parameter you


define whether the Coding
Schemes CS3 and CS4
capability is enabled in the
BTS. The Coding Schemes
CS3 and CS4 can be used in
GPRS-enabled TRXs, which
are EDGE-capable. The
GPRS must be enabled in
the segment, BTS SW and
PCU card must support the
Coding Schemes CS3 and
CS4 in order to use Coding
Schemes CS3 and CS4 in
the BTS.

With this parameter you


define whether the Coding
Schemes CS-3 and CS-4
capability is enabled in the
BTS. The Coding Schemes
CS-3 and CS-4 can be used
in GPRS-enabled TRXs,
which are EDGE-capable.
The GPRS must be enabled
in the segment, BTS SW and
PCU card must support the
Coding Schemes CS-3 and
CS-4 in order to use Coding
Schemes CS-3 and CS-4 in
the BTS.

With the rates of 14.4 and


20.0 kbit/s of coding
schemes CS3 and CS4 a
considerable gain in data
rate can be achieved for
GPRS Mobile Stations not
supporting EGPRS. Coding
schemes CS3 and CS4 can
be used without EGPRS
feature due to fact that it is
possible to use coding
schemes CS3 and CS4 both
in GPRS and in EGPRS
territories. However Coding
Schemes CS3 and CS4 can
be used with EGPRS as
well.

With the rates of 14.4 and


20.0 kbit/s of coding
schemes CS-3 and CS-4 a
considerable gain in data
rate can be achieved for
GPRS Mobile Stations not
supporting EGPRS. Coding
schemes CS-3 and CS-4 can
be used without EGPRS
feature due to fact that it is
possible to use coding
schemes CS-3 and CS-4
both in GPRS and in EGPRS
territories. However Coding
Schemes CS-3 and CS-4
can be used with EGPRS as
well.

The parameter can be


enabled only for Nokia
MetroSite, Nokia UltraSite
and Nokia Flexi EDGE
having EDGE, if the BTS SW
supports the Coding
Schemes CS3 and CS4
application software, the
TRXs under the BTS are
using Dynamic Abis, and the
PCU card supports Coding
Schemes CS3 and CS4
Parameter defines whether
the coding Schemes CS3
and CS4 feature used in the
BTS. With the rates of 14.4
and 20.0 kbps of coding
schemes CS3 and CS4 a
considerable gain in data
rate can be achieved for
GPRS Mobile Stations not
supporting EGPRS.

The parameter can be


enabled only for Nokia
MetroSite, Nokia UltraSite
and Nokia Flexi EDGE
having EDGE, if the BTS SW
supports the Coding
Schemes CS-3 and CS-4
application software, the
TRXs under the BTS are
using Dynamic Abis, and the
PCU card supports Coding
Schemes CS-3 and CS-4.
Parameter defines whether
the coding Schemes CS-3
and CS-4 feature used in the
BTS. With the rates of 14.4
and 20.0 kbps of coding
schemes CS-3 and CS-4 a
considerable gain in data
rate can be achieved for
GPRS Mobile Stations not
supporting EGPRS.

8 (14)

CHANGE REQUEST
FORM

9 (14)

NET/GSM/EDGE BSS R&D


3.3

DAP

3.3.1

bcsuID (BCSU ID)

3.3.2

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Dynamic Abis (54)


(optional) AND
( Enhanced GPRS
(EGPRS) Usage (51)
(optional) OR Coding
Schemes CS-3 And CS4 (83) (optional) )
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Dynamic Abis (54)


(optional) AND
( Enhanced GPRS
(EGPRS) Usage (51)
(optional) OR Coding
Schemes CS-3 And CS4 (83) (optional) )
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

BSS20106 is not
visible to customer
is S12

psei (Packet Service Entity Identifier)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Dynamic Abis (54)


(optional) AND Gb
Over IP (82) (optional)
AND ( Enhanced GPRS
(EGPRS) Usage (51)
(optional) OR Coding
Schemes CS-3 And CS4 (83) (optional) )
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Dynamic Abis (54)


(optional) AND Gb
Over IP (82) (optional)
AND ( Enhanced GPRS
(EGPRS) Usage (51)
(optional) OR Coding
Schemes CS-3 And CS4 (83) (optional) )
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

BSS20106 is not
visible to customer
is S12

Current value

Proposed value

Notes

SubTimeslot of the
PCM where the LAPD
link will be created.

SubTimeslot of the
PCM where the LAPD
link will be created.

E104677 NOK state


report

Value range and step:


BitRate 16 kBit/s:
0,2,4,6
BitRate 32 kBit/s: 0,2,4
BitRate 64 kBit/s: Not
Defined

Value range and step:


BitRate 8 kBit/s: 0..7
BitRate 16 kBit/s:
0,2,4,6
BitRate 32 kBit/s: 0,2,4
BitRate 64 kBit/s: Not
Defined

3.4

LAPD

3.4.1

abisSigChannelSubSlot (Sub TSL)


Parameter
Dictionary field
Description

NOTE:
NetAct internal value
range:
BitRate 16 kBit/s: UI
value /2
BitRate 32 kBit/s: UI
value /2
CRQ Template

NOTE:
NetAct internal value
range:
BitRate 8 kBit/s: UI
value
BitRate 16 kBit/s: UI

CHANGE REQUEST
FORM

10 (14)

NET/GSM/EDGE BSS R&D


BitRate 64 kBit/s: -1
NOTE: No RNW MML
interface

Short description

SubTimeslot of the
PCM where the LAPD
will be created.BitRate
16 kBit/s, Sub TSL =
0,2,4,6. BitRate 32
kBit/s, Sub TSL =
0,2,4. BitRate 64
kBit/s, Sub TSL = Not
Defined

Range and step

0..6, step 2

NOTE: No RNW MML


interface
SubTimeslot of the
PCM where the LAPD
will be created. BitRate
8 kBit/s, Sub TSL =
0..7. BitRate 16 kBit/s,
Sub TSL = 0,2,4,6.
BitRate 32 kBit/s, Sub
TSL = 0,2,4. BitRate
64 kBit/s, Sub TSL =
Not Defined
0..7, step 1

Parameter
Dictionary field

Current value

Proposed value

BSC MML
Commands

S11.5 and earlier: FWC,


FWO, FWR; S12 and further:
FXC, FXI, FXK, FXO, FXR

FXC, FXI, FXK, FXO, FXR

3.5

NSE

3.5.1

nsEntityId (NSEI)

3.5.2

value /2
BitRate 32 kBit/s: UI
value /2
BitRate 64 kBit/s: -1

Notes

psei (Packet Service Entity Identifier)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

3.6

PCU

3.6.1

bcsuID (BCSU ID)

CRQ Template

CHANGE REQUEST
FORM

11 (14)

NET/GSM/EDGE BSS R&D


3.6.2

3.6.3

3.6.4

3.6.5

3.6.6

3.6.7

gbIfType (GB Interface Type)

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

pcuID (PCU Index)

pcuIdentifier (PCU Identifier)


Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

pcuRearrangeEnabled (Rearrange Enabled)


Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

piuType (Plug-in Unit Type)


Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

psei (Packet Service Entity Identifier)


Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional)
BSS20106: Packet
Control Unit (PCU2)

Gb Over IP (82)
(optional)

BSS20106 is not
visible to customer
is S12

CRQ Template

CHANGE REQUEST
FORM

12 (14)

NET/GSM/EDGE BSS R&D


pooling (standard)

3.7

RA

3.7.1

psei (Packet Service Entity Identifier)

4.

Parameter
Dictionary field

Current value

Proposed value

Notes

Related features

Gb Over IP (82)
(optional) AND
Multipoint Gb (98)
(optional)
BSS20106: Packet
Control Unit (PCU2)
pooling (standard)

Gb Over IP (82)
(optional) AND
Multipoint Gb (98)
(optional)

BSS20106 is not
visible to customer
is S12

DELETED PARAMETER(S):

4.1

< Managed object class name >

4.1.1

< parameter abbrevName (Full Name) >

CRQ Template

CHANGE REQUEST
FORM

13 (14)

NET/GSM/EDGE BSS R&D


5.

GUIDELINES

The process for accepting/rejecting and implementing changes in


frozen BSS parameter content: (This process and template concerns only
parameters in BSDATA-database in BSC)
The formal change control applies to baseline BSC Parameter dictionary
(http://xeswww001.ext.nokia.com:8080/pddb/) i.e., once the Dictionary is frozen
and all parameters are locked against editing the upcoming changes need to
pass the CRQ process. In BSC S-release programs, it is targeted to get first
frozen parameter content in PDDB in E2 milestone.
This parameter CRQ process does not replace programs own CR process. It
means that normal CR process must be followed if the change affects to the RS
and/or IS or needs specification and implementation commitment itself.
Program CR template contains information, where CR writter have to specify, if
CR effect to BSS parameter and CRQ is needed..
The parameter CRQ process will only enable that changes can be updated to
the dictionary and it is ensured that also implementation documentation and
network management system people are aware of parameter changes.
Change Requests for the Parameter dictionary will be made using this template.
All relevant fields of the template must be updated. Below each heading there
is a short description what kind of information should be written to that part of
the document.
It is possible to add several parameter changes to the one parameter CRQ
document. So it is not required to make own CRQ from every parameter
change.
When the CRQ is ready, the changes must be approved before it is possible to
update parameters to the dictionary.
Parameter CRQ approval
Originator of the Program CR have to fill Parameter CRQ and sends it by e-mail
(including attached CRQ(s)) to the Parameter CRQ coordinator (currently Heidi
Valtanen/Comprog Oy). The Parameter CRQ coordinator and Nokia parameter
coordinator (currently Henri Seulanto) will then check the CRQ(s).
After that Nokia parameter coordinator forwards the e-mail including the CRQ(s) to the
people belonging to 'BSS parameter CRQ' distribution list for commenting. Comments
must be sent to all in this list. People have three working days available to comment
changes.
Nokia Parameter Coordinator will accept CRQ after three working days, if there are no
major arguments for rejecting it! When the CRQ is approved the Nokia parameter
coordinator will inform the Parameter CRQ coordinator, who will update the related
parameters in PDDB.
When the parameters are updated to the dictionary or if CRQ is rejected, the
Parameter CRQ coordinator will inform the 'BSS parameter CRQ' distribution list.
The CRQs are stored in the PI. Template and instructions are saved to Internet
specifications, BSC-NMS folder.
Intranet: Interface specifications, BSC-NMS
Extranet: Interface specifications, BSC-NMS
CRQ Template

CHANGE REQUEST
FORM

14 (14)

NET/GSM/EDGE BSS R&D


(Include BSS Parameter CRQ template, BSS Parameter CRQ process, Intructions How to add
parameters to PDDB and Quick Guide to PDDB)

CRQ Template

Вам также может понравиться