Fd Rnc Signaling Plan Parameters Ru40

129
WCDMA RAN, Rel. RU40, Operating Documentation, Issue 07, Parameters Signaling Plan Parameters for Flexi Direct RNC DN0931068 Issue 05A Approval Date 2013-11-20

description

Fd Rnc Signaling Plan Parameters Ru40

Transcript of Fd Rnc Signaling Plan Parameters Ru40

Page 1: Fd Rnc Signaling Plan Parameters Ru40

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 07, Parameters

Signaling Plan Parameters for Flexi Direct RNC

DN0931068Issue 05AApproval Date 2013-11-20

Page 2: Fd Rnc Signaling Plan Parameters Ru40

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 07, Parameters

Signaling Plan Parameters for Flexi Direct RNC

DN0931068Issue 05AApproval Date 2013-11-20

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may notbe used except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“Agreement”) under which this document is distributed. No part of this document may be used, copied,reproduced, modified or transmitted in any form or means without the prior written permission of NokiaSolutions and Networks. If you have not entered into an Agreement applicable to the Product, or if thatAgreement has expired or has been terminated, You may not use this document in any manner and Youare obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Youassume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TOANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OFERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this documentmay be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle thisproduct and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety andEnvironmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services weoffer, please contact us at Nokia Solutions and Networks for any additional information.

Page 3: Fd Rnc Signaling Plan Parameters Ru40

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may notbe used except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“Agreement”) under which this document is distributed. No part of this document may be used, copied,reproduced, modified or transmitted in any form or means without the prior written permission of NokiaSolutions and Networks. If you have not entered into an Agreement applicable to the Product, or if thatAgreement has expired or has been terminated, You may not use this document in any manner and Youare obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Youassume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TOANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OFERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this documentmay be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle thisproduct and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety andEnvironmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services weoffer, please contact us at Nokia Solutions and Networks for any additional information.

Page 4: Fd Rnc Signaling Plan Parameters Ru40

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 07, Parameters

Signaling Plan Parameters for Flexi Direct RNC

DN0931068Issue 05AApproval Date 2013-11-20

Page 5: Fd Rnc Signaling Plan Parameters Ru40

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 07, Parameters

Signaling Plan Parameters for Flexi Direct RNC

DN0931068Issue 05AApproval Date 2013-11-20

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may notbe used except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“Agreement”) under which this document is distributed. No part of this document may be used, copied,reproduced, modified or transmitted in any form or means without the prior written permission of NokiaSolutions and Networks. If you have not entered into an Agreement applicable to the Product, or if thatAgreement has expired or has been terminated, You may not use this document in any manner and Youare obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Youassume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TOANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OFERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this documentmay be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle thisproduct and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety andEnvironmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services weoffer, please contact us at Nokia Solutions and Networks for any additional information.

Page 6: Fd Rnc Signaling Plan Parameters Ru40

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may notbe used except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“Agreement”) under which this document is distributed. No part of this document may be used, copied,reproduced, modified or transmitted in any form or means without the prior written permission of NokiaSolutions and Networks. If you have not entered into an Agreement applicable to the Product, or if thatAgreement has expired or has been terminated, You may not use this document in any manner and Youare obliged to return it to Nokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and Youassume full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe process of continuous development and improvement of the documentation.

This document and its contents are provided as a convenience to You. Any information or statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions and Networks will correct errors that You identify in this document. But,Nokia Solutions and Networks' total liability for any errors in the document is strictly limited to the correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TOANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OFERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this documentmay be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks. All rights reserved.

Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle thisproduct and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety andEnvironmental Information” part of this document or documentation set.

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services weoffer, please contact us at Nokia Solutions and Networks for any additional information.

Page 7: Fd Rnc Signaling Plan Parameters Ru40

1. IntroductionThe purpose of this document is to assist users in finding parameters, their meanings, specifications, and default values. The managed objects and parameters are listed in alphabetical order.

2. How to read this excel reportThe excel report provides a full information on the parameter dictionary. It shows the full set of parameter attributes including the change information.

The excel report consists of two main sections:- MO Class Tree- Parameter List

2. 1 MO Class TreeThis section shows the full Managed Object Class tree with the names of classes. Rows are grouped into respective class levels for structured and convenient view. Use unfold (+) and fold (-) buttons in the left panel to browse the tree.

2.2 Parameter ListThis section shows the full parameter information including the following:- abbreviated names- managed objects- parent/child parameter relationships- default values- range and step- field descriptions- change information

2.2.1 Field descriptionsField descriptions are provided in the second row of Parameter List section. Use fold (-) and unfold (+) buttons on the left panel to respectively hide and show the field descriptions.

2.2.2 Change informationChange information is a part of Parameter List section and is available in the following ways:

1. Definition on whether the parameter is new, removed, changed, or has been moved to another location in the structure (for example, to another managed object class). That definition is provided in the following columns:

- Changes between issues ... which shows the changes since the previous issue of the document.- Changes between releases ... which shows the changes since the latest issue of the document in the previous product release.

If the cell is empty, the parameter is not changed, nor new, nor removed, nor moved.Note that removed parameters are listed in the very bottom and they are marked with red font.

Filters are enabled for convenient browsing of the change categories.

2. Detailed change information showing the current and previous values of parameter attributes. That information is provided in the following columns:

- <parameter attribute> in issue ... which shows the value in the previous issue of the document.- <parameter attribute> in release ... which shows value in the latest issue of the document in the previous product release.

The columns are grouped into attribute-specific sections for structured and convenient view. Use unfold (+) and fold (-) buttons in the top bar to browse the attribute-specific change details. Use unfold all (2) and fold all (1) buttons on the left hand side of the top bar to respectively show and hide the change details for the whole report.

Note that for all parameters except new and removed ones, the field values for previous issue and previous release are always provided to show total history information. Additionally, the changed attributes of parameters are highlighted with grey color. Highlights are enabled to specify whether there is a change between issues or releases.

Page 8: Fd Rnc Signaling Plan Parameters Ru40

1. IntroductionThe purpose of this document is to assist users in finding parameters, their meanings, specifications, and default values. The managed objects and parameters are listed in alphabetical order.

2. How to read this excel reportThe excel report provides a full information on the parameter dictionary. It shows the full set of parameter attributes including the change information.

The excel report consists of two main sections:- MO Class Tree- Parameter List

2. 1 MO Class TreeThis section shows the full Managed Object Class tree with the names of classes. Rows are grouped into respective class levels for structured and convenient view. Use unfold (+) and fold (-) buttons in the left panel to browse the tree.

2.2 Parameter ListThis section shows the full parameter information including the following:- abbreviated names- managed objects- parent/child parameter relationships- default values- range and step- field descriptions- change information

2.2.1 Field descriptionsField descriptions are provided in the second row of Parameter List section. Use fold (-) and unfold (+) buttons on the left panel to respectively hide and show the field descriptions.

2.2.2 Change informationChange information is a part of Parameter List section and is available in the following ways:

1. Definition on whether the parameter is new, removed, changed, or has been moved to another location in the structure (for example, to another managed object class). That definition is provided in the following columns:

- Changes between issues ... which shows the changes since the previous issue of the document.- Changes between releases ... which shows the changes since the latest issue of the document in the previous product release.

If the cell is empty, the parameter is not changed, nor new, nor removed, nor moved.Note that removed parameters are listed in the very bottom and they are marked with red font.

Filters are enabled for convenient browsing of the change categories.

2. Detailed change information showing the current and previous values of parameter attributes. That information is provided in the following columns:

- <parameter attribute> in issue ... which shows the value in the previous issue of the document.- <parameter attribute> in release ... which shows value in the latest issue of the document in the previous product release.

The columns are grouped into attribute-specific sections for structured and convenient view. Use unfold (+) and fold (-) buttons in the top bar to browse the attribute-specific change details. Use unfold all (2) and fold all (1) buttons on the left hand side of the top bar to respectively show and hide the change details for the whole report.

Note that for all parameters except new and removed ones, the field values for previous issue and previous release are always provided to show total history information. Additionally, the changed attributes of parameters are highlighted with grey color. Highlights are enabled to specify whether there is a change between issues or releases.

Page 9: Fd Rnc Signaling Plan Parameters Ru40

1. IntroductionThe purpose of this document is to assist users in finding parameters, their meanings, specifications, and default values. The managed objects and parameters are listed in alphabetical order.

2. How to read this excel reportThe excel report provides a full information on the parameter dictionary. It shows the full set of parameter attributes including the change information.

The excel report consists of two main sections:- MO Class Tree- Parameter List

2. 1 MO Class TreeThis section shows the full Managed Object Class tree with the names of classes. Rows are grouped into respective class levels for structured and convenient view. Use unfold (+) and fold (-) buttons in the left panel to browse the tree.

2.2 Parameter ListThis section shows the full parameter information including the following:- abbreviated names- managed objects- parent/child parameter relationships- default values- range and step- field descriptions- change information

2.2.1 Field descriptionsField descriptions are provided in the second row of Parameter List section. Use fold (-) and unfold (+) buttons on the left panel to respectively hide and show the field descriptions.

2.2.2 Change informationChange information is a part of Parameter List section and is available in the following ways:

1. Definition on whether the parameter is new, removed, changed, or has been moved to another location in the structure (for example, to another managed object class). That definition is provided in the following columns:

- Changes between issues ... which shows the changes since the previous issue of the document.- Changes between releases ... which shows the changes since the latest issue of the document in the previous product release.

If the cell is empty, the parameter is not changed, nor new, nor removed, nor moved.Note that removed parameters are listed in the very bottom and they are marked with red font.

Filters are enabled for convenient browsing of the change categories.

2. Detailed change information showing the current and previous values of parameter attributes. That information is provided in the following columns:

- <parameter attribute> in issue ... which shows the value in the previous issue of the document.- <parameter attribute> in release ... which shows value in the latest issue of the document in the previous product release.

The columns are grouped into attribute-specific sections for structured and convenient view. Use unfold (+) and fold (-) buttons in the top bar to browse the attribute-specific change details. Use unfold all (2) and fold all (1) buttons on the left hand side of the top bar to respectively show and hide the change details for the whole report.

Note that for all parameters except new and removed ones, the field values for previous issue and previous release are always provided to show total history information. Additionally, the changed attributes of parameters are highlighted with grey color. Highlights are enabled to specify whether there is a change between issues or releases.

Page 10: Fd Rnc Signaling Plan Parameters Ru40

1. IntroductionThe purpose of this document is to assist users in finding parameters, their meanings, specifications, and default values. The managed objects and parameters are listed in alphabetical order.

2. How to read this excel reportThe excel report provides a full information on the parameter dictionary. It shows the full set of parameter attributes including the change information.

The excel report consists of two main sections:- MO Class Tree- Parameter List

2. 1 MO Class TreeThis section shows the full Managed Object Class tree with the names of classes. Rows are grouped into respective class levels for structured and convenient view. Use unfold (+) and fold (-) buttons in the left panel to browse the tree.

2.2 Parameter ListThis section shows the full parameter information including the following:- abbreviated names- managed objects- parent/child parameter relationships- default values- range and step- field descriptions- change information

2.2.1 Field descriptionsField descriptions are provided in the second row of Parameter List section. Use fold (-) and unfold (+) buttons on the left panel to respectively hide and show the field descriptions.

2.2.2 Change informationChange information is a part of Parameter List section and is available in the following ways:

1. Definition on whether the parameter is new, removed, changed, or has been moved to another location in the structure (for example, to another managed object class). That definition is provided in the following columns:

- Changes between issues ... which shows the changes since the previous issue of the document.- Changes between releases ... which shows the changes since the latest issue of the document in the previous product release.

If the cell is empty, the parameter is not changed, nor new, nor removed, nor moved.Note that removed parameters are listed in the very bottom and they are marked with red font.

Filters are enabled for convenient browsing of the change categories.

2. Detailed change information showing the current and previous values of parameter attributes. That information is provided in the following columns:

- <parameter attribute> in issue ... which shows the value in the previous issue of the document.- <parameter attribute> in release ... which shows value in the latest issue of the document in the previous product release.

The columns are grouped into attribute-specific sections for structured and convenient view. Use unfold (+) and fold (-) buttons in the top bar to browse the attribute-specific change details. Use unfold all (2) and fold all (1) buttons on the left hand side of the top bar to respectively show and hide the change details for the whole report.

Note that for all parameters except new and removed ones, the field values for previous issue and previous release are always provided to show total history information. Additionally, the changed attributes of parameters are highlighted with grey color. Highlights are enabled to specify whether there is a change between issues or releases.

Page 11: Fd Rnc Signaling Plan Parameters Ru40

Managed Object Class

ASSOCSPCCSSNM3UAP

LCLASRMTAS

SSN

SSNSCCPPSCCTPSCTPPSSPFT

SIGNAL 

SAP 

SCCDPC 

SCCOPC 

Page 12: Fd Rnc Signaling Plan Parameters Ru40

Name of Managed Object Class

Signaling FragmentSCTP AssociationConcerned Point CodeConcerned SubsystemM3UA LimitsSignaling Service Access PointLocal Application ServerRemote Application ServerDestination Signaling Point CodeSCCP SubsystemOrigination Signaling Point CodeSCCP SubsystemSCCP LimitsSCCP Timer ProfileSCTP ProfileSCCP Subsystem Status Prohibited Filter Timer

Page 13: Fd Rnc Signaling Plan Parameters Ru40

Abbreviated Name

adminState

assoId

Changed commType

connState

Changed exchangeMode

Changed localAsName

Changed Changed localClientPort

Changed localIP

Changed Changed localServerPort

Changed node

Note:See the How to Read This Report tabfor instructions on the usage of Parameter List

Changes between issues 05 and 05A

Changes between releases RU30 and RU40

Page 14: Fd Rnc Signaling Plan Parameters Ru40

Changed remoteAsName

Changed remoteIP

Changed remotePort

role

Changed sctpName

New vrfName

Changed assn

Changed cspName

Changed sp

Changed assn

Changed cssnName

Changed ssn

Page 15: Fd Rnc Signaling Plan Parameters Ru40

Changed localAsId

Changed localAsName

Changed Changed routingContext

Changed routingKey

Changed trafficMode

New baseReconnTime

New incReconnTime

New m3uaId

New m3uaStep1RetransmitTime

New m3uaStep2RetransmitTime

New maxLocalAS

New maxLocalASP

Page 16: Fd Rnc Signaling Plan Parameters Ru40

New maxM3uaRetransmits

New maxM3uaStep1Retransmits

New maxReconnTime

New maxRemoteAS

New maxRemoteASP

New maxSG

Changed New maxSctpConn

New maxUsrPerASP

Changed commType

New includeNAInOutMessage

New includeRCInOutMessage

pendingTimer

Page 17: Fd Rnc Signaling Plan Parameters Ru40

Changed remoteAsId

Changed remoteAsName

remoteAsState

Changed Changed routingContext

Changed routingKey

Changed trafficMode

nwAppearance

nwIndicator

nwType

Changed sapId

Changed sapName

New sccpTimerName

Page 18: Fd Rnc Signaling Plan Parameters Ru40

destPointCodeState

Changed remoteAsName

Changed signDestPointIdentifier

Changed localAsName

originPointCodeState

Changed signOwnPointIdentifier

New nwType

New sccpTimerName

New tCongestion

New tConnEst

New tGuard

New tIar

Page 19: Fd Rnc Signaling Plan Parameters Ru40

New tIas

New tInterval

New tReassembly

New tRelease

New tRepeatRelease

New tReset

New ta

New td

assocMaxRetransmits

Changed bundling

dscp

heartbeatInterval

Page 20: Fd Rnc Signaling Plan Parameters Ru40

maxInitRetransmits

pathMTU

pathMaxRetransmit

rtoInit

rtoMax

rtoMin

sackPeriod

Changed sctpName

validCookieLife

id

ssn

ssnId

Page 21: Fd Rnc Signaling Plan Parameters Ru40

Changed ssnName

ssnState

ssn

ssnId

ssnName

ssnState

New adminState

New filterTimer

New id

Removed fromTemplate

Page 22: Fd Rnc Signaling Plan Parameters Ru40

MO Class Parent Structure

ASSO

ASSO

ASSO

ASSO

ASSO

ASSO

ASSO

ASSO

ASSO

ASSO

Page 23: Fd Rnc Signaling Plan Parameters Ru40

ASSO

ASSO

ASSO

ASSO

ASSO

ASSO

CSPC

CSPC

CSPC

CSSN

CSSN

CSSN

Page 24: Fd Rnc Signaling Plan Parameters Ru40

LCLAS

LCLAS

LCLAS

LCLAS

LCLAS

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

Page 25: Fd Rnc Signaling Plan Parameters Ru40

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

M3UAP

RMTAS

RMTAS

RMTAS

RMTAS

Page 26: Fd Rnc Signaling Plan Parameters Ru40

RMTAS

RMTAS

RMTAS

RMTAS

RMTAS

RMTAS

SAP

SAP

SAP

SAP

SAP

SAP

Page 27: Fd Rnc Signaling Plan Parameters Ru40

SCCDPC

SCCDPC

SCCDPC

SCCOPC

SCCOPC

SCCOPC

SCCTP

SCCTP

SCCTP

SCCTP

SCCTP

SCCTP

Page 28: Fd Rnc Signaling Plan Parameters Ru40

SCCTP

SCCTP

SCCTP

SCCTP

SCCTP

SCCTP

SCCTP

SCCTP

SCTPP

SCTPP

SCTPP

SCTPP

Page 29: Fd Rnc Signaling Plan Parameters Ru40

SCTPP

SCTPP

SCTPP

SCTPP

SCTPP

SCTPP

SCTPP

SCTPP

SCTPP

SIGNAL

SSN

SSN

Page 30: Fd Rnc Signaling Plan Parameters Ru40

SSN

SSN

SSN

SSN

SSN

SSN

SSPFT

SSPFT

SSPFT

SCTPP

Page 31: Fd Rnc Signaling Plan Parameters Ru40

Child Parameters Full Name

Administrative State

Association Identifier

Communication Type

Connection State

Exchange Mode

Local Application Server Name

Local Client Port

Local Ip Address

Local Server Port

Node Name

Page 32: Fd Rnc Signaling Plan Parameters Ru40

Remote Application Server Name

Remote Ip Address

Remote Port

Role

SCTP Profile Name

VRF name

Affected subsystem

Concerned Signaling Point

Affected subsystem

Concerned Subsystem Name

Concerned Subsystem

Concerned Signaling Point Code Name

Page 33: Fd Rnc Signaling Plan Parameters Ru40

Local Application Server Identifier

Local Application Server Name

Routing Context

Routing Key

Traffic Mode

Base Reconnection Timeout

Incremental Reconnection Timeout

M3UA Identifier

Maximum Local Application Server

Maximum Local Signaling Process

M3UA Step1 Retransmission Timeout

M3UA Step2 Retransmission Timeout

Page 34: Fd Rnc Signaling Plan Parameters Ru40

Maximum M3UA Retransmission

Maximum Reconnection Timeout

Maximum Signaling Gateway

Maximum SCTP Connections

Maximum User Parts Per ASP

Pending Timer

Maximum M3UA Step-1 Retransmission

Maximum Remote Application Server

Maximum Remote Signaling Process

Application Server Communitation Type

Network Appearance included or not in outgoing message

Routing Context included or not in outgoing message

Page 35: Fd Rnc Signaling Plan Parameters Ru40

Remote Application Server Identifier

Remote Application Server Name

Remote Application Server State

Routing Context

Routing Key

Traffic Mode

Network Appearance Code

Network Indicator

Network Type

Service Access Point Identifier

Service Access Point Name

SCCP Timer Profile Name

Page 36: Fd Rnc Signaling Plan Parameters Ru40

Remote Application Server Name

Local Application Server Name

Signaling Own Point Code Identifier

Network Type

SCCP Timer Profile Name

SCCP Congestion Timer

Guard Timer

Inactivity Receive Timer

Destination Signaling Point Code State

Signaling Destination Point Code Identifier

Origination Signaling Point Code State

SCCP connection establishment timer

Page 37: Fd Rnc Signaling Plan Parameters Ru40

Inactivity Send Timer

Interval Timer

Reassembly Timer

Release Timer

Repeat Release Timer

Reset Timer

Timer Ignore MTP-STATUS

Timer Delay

Bundling

Differential Services Code Point

Heartbeat Interval

Association Maximum Re-transamission

Page 38: Fd Rnc Signaling Plan Parameters Ru40

Maximum Initial Re-transmission

Path Maximum Transmission Unit

Path Maximum Re-transamission

Initial Re-transmission Timeout

Maximum Re-transmission Timeout

Minimum Re-transmission Timeout

Sack Period

SCTP Profile Name

Valid Cookie Life

Instance id

Subsystem

Subsystem Identifier

Page 39: Fd Rnc Signaling Plan Parameters Ru40

Subsystem Name

Subsystem State

Subsystem

Subsystem Identifier

Subsystem Name

Subsystem State

Administrative State

SSP Filter Timer

SSPFT Identifier

Template SCTP Profile Name

Page 40: Fd Rnc Signaling Plan Parameters Ru40

3GPP Name Data Type Parameter Group

Enumeration

m3UALinkTpId Number

m3UAEntityType Enumeration

m3UALinkTPState Enumeration

Enumeration

String

sCTPAssocLocalAddr Number

sctpAssocLocalAddr String

sCTPAssocLocalAddr Number

String

Page 41: Fd Rnc Signaling Plan Parameters Ru40

String

sctpAssocRemoteAddr String

sCTPAssocRemoteAddr Number

Enumeration

String

String

String

String

String

String

String

String

Page 42: Fd Rnc Signaling Plan Parameters Ru40

Number

m3UALinkSetTPId String

Number

m3UAEntityPointCode String

trafficMode Enumeration

Number

Number

Number

Number

Number

Number

Number

Page 43: Fd Rnc Signaling Plan Parameters Ru40

Number

Number

Number

Number

Number

Number

Number

Number

m3UAEntityType Enumeration

Enumeration

Enumeration

Number

Page 44: Fd Rnc Signaling Plan Parameters Ru40

Number

String

Enumeration

Number

destinationPc String

Enumeration

Number

networkIndicator Enumeration

Enumeration

Number

String

String

Page 45: Fd Rnc Signaling Plan Parameters Ru40

Enumeration

signRouteSetNePartId userLabel String

Number

m3UAEntityPointCode String

Enumeration

Number

Enumeration

String

Number

Number

Number

Number

Page 46: Fd Rnc Signaling Plan Parameters Ru40

Number

Number

Number

Number

Number

Number

Number

Number

Number

Enumeration

Number

Number

Page 47: Fd Rnc Signaling Plan Parameters Ru40

Number

Number

Number

Number

Number

Number

Number

String

Number

Number

Enumeration

Number

Page 48: Fd Rnc Signaling Plan Parameters Ru40

String

Enumeration

Enumeration

Number

String

Enumeration

Enumeration

Number

Number

Page 49: Fd Rnc Signaling Plan Parameters Ru40

Classification Multiplicity

1

1

1

1

1

64

1

5

1

1

Page 50: Fd Rnc Signaling Plan Parameters Ru40

64

5

1

1

1

1

1

1

1

1

1

1

Page 51: Fd Rnc Signaling Plan Parameters Ru40

1

1

1

1

1

1

1

1

1

1

1

1

Page 52: Fd Rnc Signaling Plan Parameters Ru40

1

1

1

1

1

1

1

1

1

1

1

1

Page 53: Fd Rnc Signaling Plan Parameters Ru40

1

1

1

1

1

1

1

1

1

1

1

1

Page 54: Fd Rnc Signaling Plan Parameters Ru40

1

1

1

1

1

1

1

1

1

1

1

1

Page 55: Fd Rnc Signaling Plan Parameters Ru40

1

1

1

1

1

1

1

1

1

1

1

1

Page 56: Fd Rnc Signaling Plan Parameters Ru40

1

1

1

1

1

1

1

1

1

1

1

1

Page 57: Fd Rnc Signaling Plan Parameters Ru40

1

2

1

1

1

2

1

1

1

Page 58: Fd Rnc Signaling Plan Parameters Ru40

Description Range and step

Defines unique identifier for the SCTP association. 1...22000, step 1

IPSP (0), SGASP (1)

SINGLE (0), DOUBLE (1)

1...10 characters

1025...65535, step 1

7...15 characters

1025...65535, step 1

1...255 characters

Defines the administrative state of the SCTP association. Possible values are: enableddisabled

DISABLED (0), ENABLED (1)

Defines the communication type with the peer. Possible values are:ipspsgasp

Defines the state of the SCTP association or application server process.

CONNECTION_DOWN (0), ASP_DOWN (1), ASP_INACTIVE (2), ASP_ACTIVE (3)

Defines the application server process exchange mode. Possible values are:singledouble

Defines the local application server name to which the SCTP association belongs.The name can contain the following characters: letters a-z, A-Z, numbers 0-9, and underscore (_).

Defines the client port of the local end point of the SCTP association. This port is mandatory when ASSO role is client.

Defines the IP address of the local end point of the SCTP association.The address is specified in the conventional dot notation [0-255].[0-255].[0-255].[0-255].

Defines the server port of the local end point of the SCTP association. This port is mandatory when ASSO role is server.

Defines the node name within the cluster to which the local end point belongs. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, minus sign(-), underscore(_) and slash(/).

Page 59: Fd Rnc Signaling Plan Parameters Ru40

1...10 characters

7...15 characters

1025...65535, step 1

CLIENT (0), SERVER (1)

1...10 characters

1...15 characters

1...10 characters

1...10 characters

1...10 characters

1...10 characters

1...10 characters

1...10 characters

Defines the remote application server name to which the SCTP association belongs. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore(_).

Defines the IP address of the remote end point of the SCTP association. The address is specified in the conventional dot notation [0-255].[0-255].[0-255].[0-255].

Defines the port of the remote end point of the SCTP association.

Defines the role of the local end point of the SCTP association. Possible values are:clientserver

Defines the SCTP profile name from which SCTP socket settings are to be applied to SCTP association. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, minus(-), underscore (_).

virtual routing and forwarding (VRF) name to which multihomed local IP is mapped.

Defines affected subsystem name. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Defines unique identifier for concerned signaling point code. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Defines the concerned signaling point code. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Defines the affected subsystem name. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Defines unique identifier for concerned subsystem. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Defines the concerned subsystem name. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Page 60: Fd Rnc Signaling Plan Parameters Ru40

1...50, step 1

1...10 characters

0...4294967294, step 1

1...8 characters

1...86400 s, step 1 s

0...86400 s, step 1 s

1...1, step 1

1...1200 s, step 1 s

1...1200 s, step 1 s

Defines maximum number of local application server. 1...50, step 1

Defines maximum number of local application server process. 1...200, step 1

Defines unique identifier for the local application server. Used to identify the object within the stack.

Defines unique name for local application server. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

Defines routing context for the routing key which is mapped to the local application server.

Defines routing key for the local application server. The range is 1...16777215. The real range is restricted by standard restrictions(ITU, ANSI, JAPAN, CHINA), of which ITU allows range 1-16383.

Defines the traffic mode for the local application server. Generally, loadshare mode shall be used such as Iucs, Iups, Iur. Iu-PC shall use override mode when association priority is to be taken into use.

LOADSHARE (0), BROADCAST (1), OVERRIDE (2)

'Base Reconnection Timeout' along with 'Incremental Reconnection Timeout' and 'Maximum Reconnection Timeout' are used for establishing or re-establishing the M3UA association with random variation in the re-connection intervals.

'Base Reconnection Timeout' along with 'Incremental Reconnection Timeout' and 'Maximum Reconnection Timeout' are used for establishing or re-establishing the M3UA association with random variation in the re-connection intervals.

Defines unique identifier for the M3UA. Internal parameter is always one instance in the system.

This parameter defines the time interval at which un-acknowledged or lost M3UA ASP traffic maintenance (ASPTM) messages and ASP state maintenance (ASPSM) messages are retransmitted initially i.e. maximum of maxM3uaStep1Retransmits attempts. The timeout value for This parameter defines the time interval at which un-acknowledged or lost M3UA ASP traffic maintenance (ASPTM) messages and ASP state maintenance (ASPSM) messages are retransmitted after the maximum attempts for step1 retransmission are exhausted.

Page 61: Fd Rnc Signaling Plan Parameters Ru40

0...2400, step 1

0...1200, step 1

1...86400 s, step 1 s

Defines maximum number of remote application server. 1...214, step 1

1...200, step 1

1...5, step 1

Defines maximum number of SCTP connections. 1...200, step 1

1...50, step 1

IPSP (0), SGASP (1)

Defines if routing context included or not in outgoing message.

0...4294967295, step 1

This parameter defines the maximum value of the re-transmission attempts, which includes the total value of both step1 & step2 retransmissions. These attempts must be higher than or equal to the maximum number of step1 retransmissions. When the maximum attempts are exhausted, The parameter defines the maximum value of the number of step1 retransmission attempts. The maximum number of these attempts must be lower than or equal to the maximum number of retransmission attempts defined in the M3UAP–maxM3uaRetransmits parameter.'Base Reconnection Timeout' along with 'Incremental Reconnection Timeout' and 'Maximum Reconnection Timeout' are used for establishing or re-establishing the M3UA association with random variation in the re-connection intervals.

Defines maximum number of remote application server process.

Defines maximum number of signaling gateway. It is targeted to MGW and not I-HSPA, thus it can only be uploaded.

Defines maximum number of user parts per application server process. Currently only SCCP is supported as ASP user part. Default value shall suffice for I-HSPA.

Defines the communication type with the peer. Possible values are:ipspsgasp

Defines if network appearance is included or not in outgoing message.

NOT INCLUDED (0), INCLUDED (1)

NOT INCLUDED (0), INCLUDED (1)

Defines time in seconds for which application server stays in pending state and M3UA buffers the application server data being pumped from user.

Page 62: Fd Rnc Signaling Plan Parameters Ru40

1...214, step 1

1...10 characters

Defines the state of the local application server.

0...4294967294, step 1

1...8 characters

Defines the network appearance for the signaling network. 0...4294967294, step 1

Defines the service access point identifier. 1...10, step 1

1...10 characters

1...10 characters

Defines unique identifier for the remote application server. Used to identify the object within the stack.

Defines unique name for remote application server. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

AS_DOWN (0), AS_INACTIVE (1), AS_ACTIVE (2), AS_PENDING (3)

Defines routing context for the routing key which is mapped to the remote application server.

Defines routing key for the remote application server. The range is 1...16777215. The real range is restricted by standard restrictions(ITU, ANSI, JAPAN, CHINA), of which ITU allows range 1-16383.

Defines the traffic mode for the local application server. Generally, loadshare mode shall be used such as Iucs, Iups, Iur. Iu-PC shall use override mode when association priority is to be taken into use.

LOADSHARE (0), BROADCAST (1), OVERRIDE (2)

Defines the network indicator.Possible values are:NA0: national network 0NA1: national network 1IN0: international network 0

NA0 (0), NA1 (1), IN0 (2), IN1 (3)

Defines the network type.Possible values are:ITUANSICHINESE

ITU (0), ANSI (1), CHINESE (2), JAPANESE (3)

Defines unique name for service access point name. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

It's used to specify sccp timer profile which includes Tiar, Tias etc. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, minus sign (-), underscore (_).

Page 63: Fd Rnc Signaling Plan Parameters Ru40

Defines the destination signaling point code state.

1...10 characters

1...1024, step 1

1...10 characters

Defines the origination signaling point code state.

1...1024, step 1

1...10 characters

SCCP Congestion timer. 1...10 s, step 1 s

SCCP connection establishment timer. 60...120 s, step 1 s

1380...1500 s, step 1 s

270...1260 s, step 1 s

INACCESSIBLE (0), CONGESTED (1), ACCESSIBLE (2)

Defines the remote application server name which maps to the signaling destination point code. Remote application server is configured at M3UA stack layer. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).This parameter defines unique identifier across all signaling own point codes i.e. ‘SIGNAL/SAP/SCCOPC-signOwnPointIdentifier’ and signaling destination point codes i.e. ‘SIGNAL/SAP/SCCDPC-signDestPointIdentifier’.

Defines the local application server name which maps to the signaling own point code. Local application server is configured at M3UA stack layer. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

INACCESSIBLE (0), CONGESTED (1), ACCESSIBLE (2)

This parameter defines unique identifier across all signaling own point codes i.e. ‘SIGNAL/SAP/SCCOPC-signOwnPointIdentifier’ and signaling destination point codes i.e. ‘SIGNAL/SAP/SCCDPC-signDestPointIdentifier’.

Defines the network type. Possible values are:ITUANSICHINESEJAPANESE

ITU (0), ANSI (1), CHINESE (2), JAPANESE (3)

It's the name specifying the sccp timer profile.The name can contain the following characters: letters a-z, A-Z, numbers 0-9, minus sign (-), underscore (_).

Timer indicates the waiting time for resuming to normal procedure for temporary connection sections during the restart procedure.

Timer indicates the waiting time to receive a message on a connection section. The length of the receive inactivity timer must be longer than the length of the send inactivity timer.

Page 64: Fd Rnc Signaling Plan Parameters Ru40

90...600 s, step 1 s

50...60 s, step 1 s

5...20 s, step 1 s

Timer indicates the waiting time for release complete message. 10...20 s, step 1 s

10...20 s, step 1 s

10...20 s, step 1 s

60...600 ms, step 10 ms

1...10 s, step 1 s

1...15, step 1

no (0), yes (1)

Defines the setting for differential service code point. 0...63, step 1

10...300000 ms, step 10 ms

Timer indicates the delay in sending a message on a connection Inactivity Test on a connection section when there are no messages to be sent. The length of the receive inactivity timer must be longer than the length of the send inactivity timer.Timer indicates the waiting time for release complete message; or to release connection resources, freeze the LRN and alert a maintenance function after the expiry of the initial tRelease timer.

Timer indicates the waiting time for receiving all the remaining segments of a segmented message after receiving its first segment. If nwType is ansi, the range is 5-20s, for other nwType, the range is 10-20s.

Timer indicates the waiting time for release complete message; or to repeat sending released message after the expiry of the initial 't-release' timer.

Timer indicates the waiting time for releasing temporary connection section or alert maintenance function after reset request message is sent.

Timer that indicates the time period during which the MTP-STATUS primitives are ignored for setting.

Timer that indicates the delay in decrementing the MTP restriction level and restriction sub-level after congestion has abated.

Defines the maximum number of consecutive retransmissions to a peer before an endpoint considers that the peer is unreachable and closes the association.

Defines if bundling of multiple chunks be allowed in a single message. Bundling shall be disabled for delay sensitive service.

Defines the interval when a HEARTBEAT chunk is sent to a destination transport address to monitor the reach ability of an idle destination transport address.

Page 65: Fd Rnc Signaling Plan Parameters Ru40

1...15, step 1

540...9000, step 1

1...15, step 1

10...60000 ms, step 10 ms

10...20000 ms, step 10 ms

Defines the timeout period for a delayed SACK. 0...50000 ms, step 10 ms

1...10 characters

10...500000 ms, step 10 ms

Defines the instance id of the Signaling 1...1, step 1

Defines subsystem.

Defines unique identifier for the subsystem. 1...255, step 1

Defines the maximum number of times an INIT chunk or a COOKIE ECHO chunk is retransmitted before an endpoint aborts the initialization process and closes the association.

Defines the path maximum transmission unit at SCTP socket level. This should not be used if interface level maximum transmission unit is needed.

Defines the maximum number of consecutive retransmissions over a destination transport address of a peer endpoint before it is marked as inactive.

Defines the initial value of RTO (retransmission timeout) that is used in RTO calculations.

Defines the maximum value of RTO (retransmission timeout) that is used in RTO calculations.

200...120000 ms, step 10 ms

Defines the minimum value of RTO(retransmission timeout) that is used in RTO calculations.

Defines unique name for SCTP profile. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, minus(-), underscore (_).

Defines the maximum lifespan of the Cookie sent in an INIT ACK chunk.

RANAP (142), RNSAP (143), PCAP (249)

Page 66: Fd Rnc Signaling Plan Parameters Ru40

1...10 characters

Defines the subsystem state.

Defines subsystem.

Defines unique identifier for the subsystem. 1...255, step 1

1...10 characters

Defines the subsystem state.

Defines time for SCCP subsystem status prohibited filtering.

1...1, step 1

Defines unique name for SCCP subsystem. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

UNREGISTERED (0), REGISTERED (1), NOT ALLOWED (3), ALLOWED (4)

RANAP (142), RNSAP (143), PCAP (249)

Defines unique name for SCCP subsystem. The name can contain the following characters: letters a-z, A-Z, numbers 0-9, underscore (_).

UNREGISTERED (0), REGISTERED (1), NOT ALLOWED (3), ALLOWED (4)

Defines the administrative state of the SSP filtering. Possible values are:ENABLEDDISABLED

DISABLED (0), ENABLED (1)

500...300000 ms, step 100 ms

Defines unique identifier for SCCP subsystem status filter timer.

Page 67: Fd Rnc Signaling Plan Parameters Ru40

Formula for Getting Internal Value Default Value

DISABLED (0)

internal_value = gui_value -

IPSP (0)

-

SINGLE (0)

internal_value = gui_value -

internal_value = gui_value 2905

internal_value = gui_value -

internal_value = gui_value 2905

internal_value = gui_value -

gui ==> internalDISABLED ==> 0ENABLED ==> 1

gui ==> internalIPSP ==> 0SGASP ==> 1

gui ==> internalCONNECTION_DOWN ==> 0ASP_DOWN ==> 1ASP_INACTIVE ==> 2ASP_ACTIVE ==> 3gui ==> internalSINGLE ==> 0DOUBLE ==> 1

Page 68: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

-

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

gui ==> internalCLIENT ==> 0SERVER ==> 1

Page 69: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

-

internal_value = gui_value 5 s

internal_value = gui_value 5 s

internal_value = gui_value -

internal_value = gui_value 2 s

internal_value = gui_value 30 s

internal_value = gui_value 5

internal_value = gui_value 5

gui ==> internalLOADSHARE ==> 0BROADCAST ==> 1OVERRIDE ==> 2

Page 70: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value 180

internal_value = gui_value 150

internal_value = gui_value 1200 s

internal_value = gui_value 200

internal_value = gui_value 200

internal_value = gui_value -

internal_value = gui_value 200

internal_value = gui_value 5

IPSP (0)

INCLUDED (1)

NOT INCLUDED (0)

internal_value = gui_value -

gui ==> internalIPSP ==> 0SGASP ==> 1

gui ==> internalNOT INCLUDED ==> 0INCLUDED ==> 1

gui ==> internalNOT INCLUDED ==> 0INCLUDED ==> 1

Page 71: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value -

internal_value = gui_value -

-

internal_value = gui_value -

internal_value = gui_value -

-

internal_value = gui_value -

-

-

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

gui ==> internalAS_DOWN ==> 0AS_INACTIVE ==> 1AS_ACTIVE ==> 2AS_PENDING ==> 3

gui ==> internalLOADSHARE ==> 0BROADCAST ==> 1OVERRIDE ==> 2

gui ==> internalNA0 ==> 0NA1 ==> 1IN0 ==> 2IN1 ==> 3gui ==> internalITU ==> 0ANSI ==> 1CHINESE ==> 2JAPANESE ==> 3

Page 72: Fd Rnc Signaling Plan Parameters Ru40

-

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

-

internal_value = gui_value -

-

internal_value = gui_value -

internal_value = gui_value 1 s

internal_value = gui_value 60 s

internal_value = gui_value 1380 s

internal_value = gui_value 270 s

gui ==> internalINACCESSIBLE ==> 0CONGESTED ==> 1ACCESSIBLE ==> 2

gui ==> internalINACCESSIBLE ==> 0CONGESTED ==> 1ACCESSIBLE ==> 2

gui ==> internalITU ==> 0ANSI ==> 1CHINESE ==> 2JAPANESE ==> 3

Page 73: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value 90 s

internal_value = gui_value 50 s

internal_value = gui_value 10 s

internal_value = gui_value 10 s

internal_value = gui_value 10 s

internal_value = gui_value 10 s

internal_value = gui_value 60 ms

internal_value = gui_value 1 s

internal_value = gui_value -

-

internal_value = gui_value 34

internal_value = gui_value -

gui ==> internalno ==> 0yes ==> 1

Page 74: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value -

internal_value = gui_value 0

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value -

internal_value = gui_value 1

-

internal_value = gui_value -

gui ==> internalRANAP ==> 142RNSAP ==> 143PCAP ==> 249

Page 75: Fd Rnc Signaling Plan Parameters Ru40

internal_value = gui_value -

-

-

internal_value = gui_value -

internal_value = gui_value -

-

ENABLED (1)

internal_value = gui_value 5000 ms

internal_value = gui_value -

gui ==> internalUNREGISTERED ==> 0REGISTERED ==> 1NOT ALLOWED ==> 3ALLOWED ==> 4gui ==> internalRANAP ==> 142RNSAP ==> 143PCAP ==> 249

gui ==> internalUNREGISTERED ==> 0REGISTERED ==> 1NOT ALLOWED ==> 3ALLOWED ==> 4gui ==> internalDISABLED ==> 0ENABLED ==> 1

Page 76: Fd Rnc Signaling Plan Parameters Ru40

Default Value Notes Special Value

IANA registered port for M3UA. User can change it.

IANA reserved port for M3UA. User can change it.

Page 77: Fd Rnc Signaling Plan Parameters Ru40
Page 78: Fd Rnc Signaling Plan Parameters Ru40
Page 79: Fd Rnc Signaling Plan Parameters Ru40
Page 80: Fd Rnc Signaling Plan Parameters Ru40
Page 81: Fd Rnc Signaling Plan Parameters Ru40
Page 82: Fd Rnc Signaling Plan Parameters Ru40

Default value is 34 for control plane.

Page 83: Fd Rnc Signaling Plan Parameters Ru40

In the LDAP, this parameter will be optional. So if this is not administered, it will have value 0. This indicates that pmtu at socket level will not be defined

If 0 is used, pathMTU at socket level is not used (0)

Page 84: Fd Rnc Signaling Plan Parameters Ru40
Page 85: Fd Rnc Signaling Plan Parameters Ru40

Related Functions Modification

On-line

Not modifiable

Not modifiable

Not modifiable

Requires object locking

Requires object locking

Requires object locking

Requires object locking

Requires object locking

Not modifiable

Page 86: Fd Rnc Signaling Plan Parameters Ru40

Requires object locking

Requires object locking

Requires object locking

Not modifiable

Requires object locking

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Page 87: Fd Rnc Signaling Plan Parameters Ru40

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Requires object locking

Requires object locking

Not modifiable

Requires object locking

Requires object locking

Requires object locking

Requires object locking

Page 88: Fd Rnc Signaling Plan Parameters Ru40

Requires object locking

Requires object locking

Requires object locking

Requires object locking

Requires object locking

Not modifiable

Requires object locking

Requires object locking

Not modifiable

On-line

On-line

Not modifiable

Page 89: Fd Rnc Signaling Plan Parameters Ru40

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

On-line

Page 90: Fd Rnc Signaling Plan Parameters Ru40

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

On-line

On-line

On-line

On-line

Page 91: Fd Rnc Signaling Plan Parameters Ru40

On-line

On-line

On-line

On-line

On-line

On-line

On-line

On-line

On-line

On-line

On-line

On-line

Page 92: Fd Rnc Signaling Plan Parameters Ru40

On-line

On-line

On-line

On-line

On-line

On-line

On-line

Not modifiable

On-line

Not modifiable

Not modifiable

Not modifiable

Page 93: Fd Rnc Signaling Plan Parameters Ru40

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

Not modifiable

On-line

On-line

Not modifiable

Page 94: Fd Rnc Signaling Plan Parameters Ru40

Required on Creation Related Parameters

Optional

Mandatory

Mandatory

Value set by the system

Optional

Mandatory

Optional

Mandatory

Optional

Mandatory

Page 95: Fd Rnc Signaling Plan Parameters Ru40

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Value set by the system

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Page 96: Fd Rnc Signaling Plan Parameters Ru40

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Optional

Optional

Mandatory

Optional

Optional

Optional

Optional

incReconnTime of M3UAP - See Description field (public)maxReconnTime of M3UAP - See Description field (public)

baseReconnTime of M3UAP - See Description field (public)maxReconnTime of M3UAP - See Description field (public)

m3uaStep2RetransmitTime of M3UAP - null (public)maxM3uaRetransmits of M3UAP - null (public)maxM3uaStep1Retransmits of M3UAP - null (public)

m3uaStep1RetransmitTime of M3UAP - null (public)maxM3uaRetransmits of M3UAP - null (public)maxM3uaStep1Retransmits of M3UAP - null (public)

Page 97: Fd Rnc Signaling Plan Parameters Ru40

Optional

Optional

Optional

Optional

Optional

Value set by the system

Optional

Optional

Mandatory

Optional

Optional

Mandatory

m3uaStep1RetransmitTime of M3UAP - null (public)m3uaStep2RetransmitTime of M3UAP - null (public)maxM3uaStep1Retransmits of M3UAP - null (public)

m3uaStep1RetransmitTime of M3UAP - null (public)m3uaStep2RetransmitTime of M3UAP - null (public)maxM3uaRetransmits of M3UAP - null (public)

baseReconnTime of M3UAP - See Description field (public)incReconnTime of M3UAP - See Description field (public)

Page 98: Fd Rnc Signaling Plan Parameters Ru40

Mandatory

Mandatory

Value set by the system

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Optional

Page 99: Fd Rnc Signaling Plan Parameters Ru40

Value set by the system

Mandatory

Mandatory

Mandatory

Value set by the system

Mandatory

Mandatory

Mandatory

Optional

Optional

Optional

Optional

Page 100: Fd Rnc Signaling Plan Parameters Ru40

Optional

Optional

Optional

Optional

Optional

Optional

Optional

Optional

Mandatory

Mandatory

Optional

Mandatory

Page 101: Fd Rnc Signaling Plan Parameters Ru40

Mandatory

Optional

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Mandatory

Page 102: Fd Rnc Signaling Plan Parameters Ru40

Mandatory

Value set by the system

Mandatory

Mandatory

Mandatory

Value set by the system

Optional

Optional

Mandatory

Page 103: Fd Rnc Signaling Plan Parameters Ru40

Related Features References

Page 104: Fd Rnc Signaling Plan Parameters Ru40
Page 105: Fd Rnc Signaling Plan Parameters Ru40
Page 106: Fd Rnc Signaling Plan Parameters Ru40
Page 107: Fd Rnc Signaling Plan Parameters Ru40
Page 108: Fd Rnc Signaling Plan Parameters Ru40
Page 109: Fd Rnc Signaling Plan Parameters Ru40
Page 110: Fd Rnc Signaling Plan Parameters Ru40
Page 111: Fd Rnc Signaling Plan Parameters Ru40
Page 112: Fd Rnc Signaling Plan Parameters Ru40

Validation Pattern

[a-zA-Z][0-9a-zA-Z_]{0,9}

IPv4

[_/A-Za-z0-9-]+

Page 113: Fd Rnc Signaling Plan Parameters Ru40

[a-zA-Z][0-9a-zA-Z_]{0,9}

IPv4

[-_A-Za-z0-9]+

###

[_A-Za-z0-9]+

[_A-Za-z0-9]+

[_A-Za-z0-9]+

[A-Za-z_0-9]+

[_A-Za-z0-9]+

[A-Za-z_0-9]+

Page 114: Fd Rnc Signaling Plan Parameters Ru40

[_A-Za-z0-9]+

[1-9][0-9]{0,7}

###

###

###

###

###

###

###

Page 115: Fd Rnc Signaling Plan Parameters Ru40

###

###

###

###

###

###

###

###

###

###

Page 116: Fd Rnc Signaling Plan Parameters Ru40

[_a-zA-Z0-9]+

[1-9][0-9]{0,7}

[_a-zA-Z0-9]+

[-_a-zA-Z0-9]+

Page 117: Fd Rnc Signaling Plan Parameters Ru40

[_a-zA-Z0-9]+

[_a-zA-Z0-9]+

###

[-_A-Za-z0-9]+

###

###

###

###

Page 118: Fd Rnc Signaling Plan Parameters Ru40

###

###

###

###

###

###

###

###

Page 119: Fd Rnc Signaling Plan Parameters Ru40

[-_a-zA-Z0-9]+

Page 120: Fd Rnc Signaling Plan Parameters Ru40

[_a-zA-Z0-9]+

[_a-zA-Z0-9]+

###

###

###