Milegate Cps Handling Procedures: Engineering Bulletin
Milegate Cps Handling Procedures: Engineering Bulletin
Milegate Cps Handling Procedures: Engineering Bulletin
MileGate
MileGate
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
CPS handling procedures
Table of Content
3 Background information 18
3.1 CPS types and revisions 18
3.1.1 Introduction 18
3.1.2 CPS naming convention 18
3.1.3 CPS revision format 19
4 Annex 24
4.1 Terms and abbreviations 24
4.2 References 25
4.3 Document history 26
4.4 Technical support 27
4.5 Product training 28
Tables
interop yes
request the detailed questionnaire from test OK ?
the KEYMILE customer support
no
fill in the questionnaire and send it back send the parameter change request to
to the KEYMILE customer support the KEYMILE customer support
download the CPS file with the CPS tool KEYMILE customer support releases the
of MCST 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.
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 .
the MileGate configuration is not import the new ESW file with the ESW import the CPS file with the CPS tool of import the CPS file with the CPS tool of
changed . package manager of MCST into the
MCST into the management system MCST into the management system
Unit services are not interrupted management system
download the ESW file to the download the CPS file with the CPS tool download the CPS file with the CPS tool
corrsponding unit of MCST to the network element (NE) of MCST 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 not interrupted only if package manager of MCST into the
the unit has been restarted management 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 element manager in the
directory
C:\Documents and Settings\<user_name>\
.com_KEYMILE_util_localfilesystembackend\
cps\CustomParameterSet\v_1.00.00.
An updated MCST release will access the same CPS files as the previous
MCST release.
In MileGate the CPS has to be compatible with the unit ESW release accord-
ing to the table below:
Please note:
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.
Please note:
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 MileGate 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 MCST 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
MCST:
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 MCST automatically creates the CPS
directory in the element manager:
→ C:\Documents and Settings\<user_name>\
.com_KEYMILE_util_localfilesystembackend\
cps\CustomParameterSet\v_1.00.00
→ 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 cor-
responding CPS name. To unselect a CPS file click on the button.
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 "[304] User Guide
“MileGate & MCST”".
To make use of a CPS, it must be configured in the MCST and the configu-
ration must be applied to the MileGate network element.
The PCOM1, PCOM2, IPSS2, IPSS3, IPSM2 or IPSM3 CPS configuration is
done on the access point AP: /unit-x, Configuration, on the “CPS” tab:
Applying the configuration with a changed CPS does not interrupt the Mile-
Gate 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 MileGate services.
3 Background information
3.1.1 Introduction
1) Hard coded:
Parameters defined at ESW compile time, same values for all custom-
ers.
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 MileGate 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 MileGate 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.
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:
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 Mile-
Gate. 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 MileGate 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 > CPS function version, e.g.
ESW_R2, CPS_R1) 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 MCST “Preview…” window,
even though they are not used by the ESW.
The following table shows the CPS related error and warning messages of
the MCST/UNEM:
4 Annex
4.2 References
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 select “Services - Training” from the
menu.