Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
XMC20
XMC20
XMC20 CPS Handling Procedures Engineering Bulletin
Copyright and Confidentiality Copyright in this document vests in KEYMILE. This document contains confi-
dential information which is the property of KEYMILE. It must be held in con-
fidence by the recipient and may not be used for any purposes except those
specifically authorised by contract or otherwise in writing by KEYMILE. This
document may not be copied in whole or in part, or any of its contents dis-
closed by the recipient to any third party, without the prior written agreement
of KEYMILE.
Disclaimer KEYMILE has taken reasonable care in compiling this document, however
KEYMILE accepts no liability whatsoever for any error or omission in the
information contained herein and gives no other warranty or undertaking as
to its accuracy.
KEYMILE reserves the right to amend this document at any time without
prior notice.
Published by KEYMILE
http://www.keymile.com
Engineering Bulletin
XMC20 CPS Handling Procedures
Content
3 Background Information 16
3.1 CPS Types and Revisions 16
3.2 CPS Release Handling 19
3.3 CPS Operation 20
4 Annex 22
4.1 Terms and Abbreviations 22
4.2 References 22
4.3 Document History 23
4.4 Technical Support 23
4.5 Product Training 23
With a new XMC20 installation using a VOIP1 unit, the following procedure
has to be followed:
interop yes
request the detailed questionnaire from
test OK ?
the KEYMILE customer support
no
fill in the questionnaire and send it back to send the parameter change request to the
the KEYMILE customer support KEYMILE customer support
download the CPS file with the CPS tool KEYMILE customer support releases the
of ECST to the network element (NE) final CPS
select the CPS in the unit „Configuration“ with any new ESW release KEYMILE
access point , apply and save the customer support will create an updated
configuration version of the CPS and send it to the
customer
Certain CPS parameters require a restart of the unit in order that a modifica-
tion becomes applied and operational. These parameters are marked with a
“#” prefix in the parameter description. Select a CPS and click the “View...”
button to display the CPS content.
With an existing XMC20 installation using a VOIP1 unit, the following ESW
and CPS upgrade procedures have to be followed.
KEYMILE recommends the use of the newest ESW and CPS in all installa-
tions since this eliminates bugs and deficiencies of legacy ESW and CPS.
No new ESW included . New ESW included . No new ESW included . New ESW included .
No new CPS included . No new CPS included . New CPS included . New CPS included .
import the new ESW file with the ESW import the CPS file with the CPS tool of
the XMC20 configuration is not changed. import the CPS file with the CPS tool of
package manager of ECST into the man- ECST into the management system
Unit services are not interrupted. ECST into the management system
agement system
download the ESW file to the correspon - download the CPS file with the CPS tool download the CPS file with the CPS tool
ding unit of ECST to the network element (NE) of ECST to the network element (NE)
select the new ESW in the unit „Main“ select the CPS in the unit „Configuration“ select the CPS in the unit „Configuration“
access point , apply and save the access point and apply and save the
access point and apply the configuration
configuration and start the unit configuration
the unit will reboot with the new ESW . the unit applies the new CPS .
Unit services are interrupted if required restart the unit Unit services are not interrupted
the unit applies the new CPS . import the new ESW file with the ESW
Unit services are interrupted only if the package manager of ECST into the man-
unit has been restarted agement system
Certain CPS parameters require a restart of the unit in order that a modifica-
tion becomes applied and operational. These parameters are marked with a
“#” prefix in the parameter description. Select a CPS and click the “View...”
button to display the CPS content.
Note that the imported CPS files are stored on the ECST element manager
in the directory
C:\Users\<user_name>\AppData\Local\CST\filesystembackend\
cps\CustomParameterSet\v_1.00.01.
Please note:
The access path on your machine may not be exactly the same as shown
above.
An updated ECST release will access the same CPS files as the previous
ECST release.
In XMC20 the CPS has to be compatible with the unit ESW release.
Please note:
For compatible combinations of ESW and CPS releases please refer to [012]
Release Note “XMC20”
In general each new ESW release requires also a new CPS release.
Using an old CPS with a new ESW is possible:
• The alarm “Incomplete CPS Version” is set.
• For missing parameters the default value of the ESW is used.
• Parameters that are no longer used are ignored.
Using a new CPS with an old ESW is possible:
• The ESW will ignore the parameters of the extended CPS structure.
If you need a CPS other than the default CPS you first have to fill in a ques-
tionnaire. The questionnaires for the different XMC20 applications can be
ordered at the KEYMILE technical support:
Please refer to the KEYMILE Extranet (via http://www.keymile.com) for sup-
port contact information.
Normally the questionnaires are filled in in close cooperation with the KEY-
MILE technical support. Finally the filled in questionnaire has to be returned
to the KEYMILE technical support who then will create the requested CPS.
The CPS creation requires in maximum 2 weeks.
The new CPS is delivered to the project leader or directly to the customer.
Please note:
CPS files can not be modified or renamed by a customer. Any change of a
CPS must be performed by KEYMILE.
Unless not already installed, you must first install your ECST element man-
ager before you can install any CPS file.
The CPS files received from KEYMILE have to be imported to the manage-
ment system and downloaded to the network element with the CPS tool of
ECST:
To import a CPS file from the file system to the management system press
the button.
The left part of the CPS tool displays all imported CPS files, i.e. CPS files
that are available on the management system.
Please note:
With the import of the first CPS file the ECST automatically creates the CPS
directory in the element manager (the access path on your machine may not
be exactly the same as shown below):
→ C:\Users\<user_name>\AppData\Local\CST\filesystembackend\
cps\CustomParameterSet\1.00.01
→ The CPS files of all applications are stored in the same directory.
→ Do not copy or delete any CPS files manually to or from the CPS
directory.
Selected CPS files are downloaded from the management system to the
network element with the button. To select a CPS file click on the corre-
sponding CPS name. To unselect a CPS file click on the corresponding CPS
name while pressing the “CTRL” button on your keyboard.
The right part of the CPS tool displays all CPS files available on the network
element, i.e. CPS files that have been downloaded. Only CPS files available
on the network element can be selected in the unit configuration.
For more information on the CPS tool handling, refer to [355] User Manual
“ECST”.
To make use of a CPS, it must be configured in the ECST and the configura-
tion must be applied to the XMC20 network element.
The VOIP1 CPS configuration is done on the access point AP: /unit-x, Con-
figuration, on the “CPS” tab:
Applying the configuration with a changed CPS does not interrupt the
XMC20 services.
Please note:
Certain CPS parameters require a restart of the unit in order that a modifica-
tion becomes applied and operational. These parameters are marked with a
“#” prefix in the parameter description.
→ The restart of a unit interrupts the XMC20 services.
3 Background Information
3.1.1 Introduction
1) Hard coded:
Parameters defined at ESW compile time. The parameters have the
same values for all customers.
3) Profile:
Global set of parameters, provisioned. Multiple profiles can be edited
in the GUI or CLI and re-used in configurations.
4) GUI:
Individual provisional parameters.
A Custom Parameter Set is a set of pre-provisioned (i.e. not GUI-controlled)
parameters that define an environment-specific behaviour of XMC20 units.
The environment is the sum of the operator’s service requirements, the
applicable telecommunication standards, the type and release of the inter-
working equipment as well as the type and release of the XMC20 units:
− the parameter value is the same for the whole customer network
− the parameter is difficult to be understood by the network operator
− the parameter is global per unit
The advantages of this approach are:
− simplifies the GUI.
− parameters are pre-provisioned rather than hard coded, resulting in
higher flexibility (customization), e.g. to solve interoperability prob-
lems.
− the number of combinations of parameter settings is limited and under
control of KEYMILE and the customer.
The name of a CPS typically consists of prefix, name, revision and exten-
sion:
prefix_name_revision.extension
The prefix is used to distinguish the different types of custom parameter set
files:
CPS structure, template file and value file versions are for KEYMILE internal
use only.
Please note:
If the structure of the CPS changes, i.e. the function version, then the imple-
mentation version remains and does not start with A again (e.g. R2B Þ R3B).
This use case describes the setting of the custom parameters in the XMC20.
The custom parameters are pre-provisioned parameters.
• Pre conditions:
A custom parameter set has to fulfil the following requirements to be visi-
ble to the user:
− The name prefix must be correct
− The CPS file has to be imported into the element manager and down-
loaded to the XMC20 network element.
• Result:
The correct custom parameter set is applied to the configuration.
This use case describes the situation, when an old CPS (from a former ESW
revision) is used with a new ESW function revision that requires an extended
CPS structure.
• Result:
When an old CPS which is not compatible with the ESW in respect of the
CPS structure (ESW function version newer than the CPS function ver-
sion) is provided to the ESW, the alarm “Incomplete CPS Version” is
set.
For missing parameters the default value of the ESW is applied, i.e. the
unit is working but the behaviour is untested.
Parameters that are in the CPS but no longer used in the ESW are
ignored.
This use case describes the situation, when a new CPS (with an extended
CPS structure) is used with a former ESW that does not support the
extended structure.
• Result:
It is allowed to apply a new CPS with extended structure (different func-
tion version) to an old ESW revision.
The ESW will ignore the parameters of the extended structure, as they
are not known.
Note that all parameters will be shown in the ECST “Preview…” window,
even though they are not used by the ESW.
The following table shows the CPS related error and warning messages of
the ECST/UNEM:
4 Annex
4.2 References
Any version(s) and/or release(s) indicated with the below listed document
titles identify the specific state of the software and/or feature set at the crea-
tion time of the present document. If the present document is published as
part of a document collection, the hyperlinks might open a document valid for
a newer version/release. That updated version is valid in the context of all
units and features described in the document collection.
Please note:
For the new HTML-based documentation site there are no interdocument
hyperlinks realized yet.
→ Please find the required document via the navigation tree on the left.
Training courses are available for a wide range of KEYMILE products and
applications.
For contact information, course descriptions, locations and dates, go to the
Website: http://www.keymile.com, then search for “product training”.