Table of Contents Index NMS Glossary Previous Page Next Page (Page 89 of 100 in this chapter) Version


Resource[x].Definitions

Syntax

Resource[x].Definitions = definition

x = 0 (index of the associated resource pool)

Access

Read/Write

Type

String

Default

None.

Allowed Values

Any valid DPF name or identifier.

Example

Resource[0].Definitions = ( echo.ln20_apt100 | dtmf.det_all )

or

Resource[0].Definitions = ( echo.ln20_apt100 & dtmf.det_all )

Description

Provides a relational string of Data Processing Functions (DPFs) that describes the functionality that can occur on a single port, and describes how the functions execute in relation to each other. The DPFs in this string specify the functions that execute on the DSPs and whether they execute simultaneously.

The notation used to express to associate functions that run simultaneously is the AND operator (&). The notation used to associate functions that do not run simultaneously is the ( | ) operator.

Both of these operator, used with the parentheses, determine the relationship between the functions and the calculation of DSP resources. The AND-OR- parentheses notation is used to optimize the allocation of resources by specifying to the board the worst-case resource usage over the duration of the call.

For more information about using DSP resource management keywords and calculating CG 6000C DSP resource usage, refer to Appendix B.

The Resource[x].Definitions specifies the processing functions that are available to applications during the life of a call or channel. For example, if you expect to run echo cancellation at any time on the board, echo must be specified in this keyword. Since echo runs at the same time as the decoder and encoder in the universal ports full duplex implementation, echo must be AND'd (&) with the decoder and the encoder.

Note: Only one echo canceller DPF is capable of running per call. Therefore, there should be only one occurrence of echo cancellation in the Resource[x].Definitions string.

A set of template configuration files are provided with the CG 6000C installation. For more information about using resource management keywords, refer to Section 3.4.1, Board Keyword Files and Section 3.8.1, Resource Management Keywords.

It is not necessary for you to specify the DPFs for the trunk control programs (TCPs) in with the Resource[x].Definitions keyword. To use a TCP, specify the name of the TCP(s) to be used with the Resource[x].TCPs keyword. The on-board resource manager takes care of OR'ing the DPFs with the DPFs specified in the Resource[x].Definitions string.

The structure of a Resource[x].Definitions keyword must start with an open parentheses and end with a closed parentheses. For example:

(( dtmf.det_all & echo.ln20_apt25) & \
(
oki.rec_24 | tone.gen ))

The following example is not correct:

( dtmf.det_all & echo.ln20_apt25) & \
(
oki.rec_24 | tone.gen )

Caution:

If you have not specified a DPF in the Resource[x].Definitions keyword and you attempt to create/start that DPF, it will fail. All DSP DPFs that you plan to use must be specified in Resource[x].Definitions.


For more information about managing on-board resources, refer to
Appendix B.

See Also

Resource[x].Name, Resource[x].Size, Resource[x].TCPNum, Resource[x].TCPs



Table of Contents Index NMS Glossary Previous Page Next Page (Page 89 of 100 in this chapter) Version


Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com
Copyright © 2000, Natural MicroSystems, Inc. All rights reserved.