|
|
|
|
||
|
|
| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
A | |
Back to Index | |
Abstract Data Structure |
Abstract Data Structure is also referred to as ADS. |
Abstract Specification File |
A file in which the structure and content of ISUP messages and parameters are textually defined. The file is written in ASN.1+. Abstract Specification File is also referred to as ASF. |
Abstract Syntax Notation One |
A standard developed by the ITU-T and detailed in X.680-X.694 used to describe complex data structures independently from underlying hardware. Abstract Syntax Notation One is also referred to as ASN.1. |
ACC |
ANSI C++ Compiler For more information, refer to the entry for ANSI C++ Compiler. |
Access Control List |
An attribute of the ClassSecurityInfo object which controls access permissions to objects in the HP Opencall SEP Management Information Base (MIB). Access Control List is also referred to as ACL. |
ACG |
Automatic Call Gapping For more information, refer to the entry for Automatic Call Gapping. |
ACL | Access Control List For more information, refer to the entry for Access Control List. |
Action of managed object |
A type of management operation which applies to managed objects. Object actions are triggered by the MIB operation action or occasionally when specific management notifications are received by that object. |
Active/Standby Compatible Mode |
A processing method that can be implemented on a 2-host (duplex) HP Opencall SS7 platform. It provides highly available SS7 stack processing. Active stack processes are maintained on one host while standby stack processes are maintained on a second host, which can take over if the active processes fail. |
AD |
Adjunct For more information, refer to the entry for Adjunct. |
Add/Drop Multiplexer |
A network element in which a part of the carried information can be demodulated (dropped) at an intermediate point and information is entered (added) for subsequent transmission. Add/Drop Multiplexer is also referred to as ADM. |
Address resolution |
A mechanism for identifying the address of a called endpoint in terms of the network, such as an IP address. |
Address translation |
A gatekeeper service for translating an alias address, such as a name or e-mail address, to a transport address. One method of translation uses a translation table, which is updated by the registration messages on the RAS channel. |
Adjacent Point Code |
A point code (MTP3 address) of a network node to which the local node is directly connected. Adjacent Point Code is also referred to as APC |
Adjunct |
A network system that provides service specific information to an AIN switching system using a high speed interface, with TCAP as the application layer protocol. Adjunct is also referred to as AD. |
Adjunct Event |
A message sent from the adjunct to the switching system that requests the switch to perform an action because of asynchronous (with respect to the switch) events in the adjunct. |
ADM |
Add/Drop Multiplexer For more information, refer to the entry for Add/Drop Multiplexer. |
ADPCM |
Adaptive Differential PCM |
ADS |
Abstract Data Structure For more information, refer to the entry Abstract Data Structure. |
Advanced Intelligent Network |
The Bellcore Client Company (BCC)'s service-independent architecture for the 1990s and beyond. The advanced intelligent network is being designed to the BCC programmable to allow BCCs or their agents to quickly and economically create and modify telecommunications services for their subscribers. AIN also provides a framework within which service-providing resources that use new technology (e.g. speech recognition devices) can be gracefully added to the existing network. Advanced Intelligent Network is also referred to as AIN. |
AIN |
Advanced Intelligent Network For more information, refer to the entry for Advanced Intelligent Network. |
AIN Switch Capabilities |
AIN Switch Capabilities is also referred to as ASC. |
Alarm |
An event that may have operational consequences. |
Alarm Handler |
One of four event collector daemon processes. |
American National Standards Institute |
Organization for fostering the development of technology standards in the United States. ANSI works with industry groups and is the U.S. member of the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). The American National Standards Institute is also referred to as ANSI. |
American Standard Code for Information Interchange |
The world-wide standard code used by computers to represent English characters as numbers. American Standard Code for Information Interchange is also referred to as ASCII. |
ANSI |
American National Standards Institute For more information, refer to the entry for American National Standards Institute. |
ANSI C++ Compiler |
Compiler used for HP Opencall. The ANSI C++ Complier is also referred to as ACC. |
APC |
Adjacent Point Code For more information, refer to the entry for Adjacent Point Code. |
API |
Application Programming Interface For more information, refer to the entry for Application Programming Interface. |
Application |
A class of functions designed to provide provisioning, administration, maintenance, and management capabilities for network elements, network systems, software and services. |
Application Guardian |
A feature that provides high availability for user applications. The applications (plug-ins) are managed by the Fault Tolerance Controller (FTC). |
Application Programming Interface |
A set of software calls and routines used by an application program to carry out underlying services performed by the platform's operating system. An API provides applications with a useful way of requesting services from the lower levels of the network. Application Programming Interface is also referred to as API. |
ASC |
AIN Switch Capabilities For more information, refer to the entry for AIN Switch Capabilities. |
ASCII |
American Standard Code for Information Interchange. For more information, refer to the entry for American Standard Code for Information Interchange. |
ASE |
Application Service Element |
ASF |
Abstract Specification File For more information, refer to the entry for Abstract Specification File. |
ASN.1 |
Abstract Syntax Notation One For more information, refer to the entry for Abstract Syntax Notation One. |
ASR |
Automatic Speech Recognition For more information, refer to the entry for Automatic Speech Recognition. |
Attribute |
A unit of information that describes a property of a particular information entity, information relationship, data object, or managed object class and may have different values (within its domain of values) for the different instances of the information entity, information relationship, data object, or managed object class. |
Automatic Call Gapping |
A method by which an overload service avoids congestion on the SEP. By increasing the time gap between TCAP messages from a SSP, traffic flow rate to the SEP is reduced, thus demand on the SEP is reduced. Call Gapping is implemented through the use of Automatic Call Gapping (ACG) messages. Automatic Call Gapping is also referred to as ACG. |
Automatic Speech Recognition |
The identification of spoken words by a computer. The spoken words are digitized (turned into a sequence of numbers) and matched against coded dictionaries in order to identify the words. Automatic Speech Recognition is also referred to as ASR. |
B | |
Back to Index | |
Back-end |
A computer or a set of computers that hosts the user applications in a distributed architecture. The back-end is connected by a LAN to the front-end which runs the SS7 stack processes. Back-end is also referred to as BE. |
Backup |
The process of copying data/programs (possibly including Service Logic Programs (SLPs) generic control programs, and other kinds of programs) into non-volatile storage, for later use to restore the data and/or programs in the event of loss due to such factors as human error, power failure, software failures, etc. |
Backus Naur Form |
A formal notation used to describe the syntax of a given language. Backus Naur Form is also referred to as BNF. |
Basic Call |
A call between two end users that does not require supplementary features (e.g. supplementary switch-based features, IN/1 features or AIN Release 1 features), such as in a POTS call. |
Basic Call Model |
A generic representation of a basic call in terms of the ASC Switch call processing activities required to establish and maintain a basic call. The BCM can be of two types, an originating BCM or a terminating BCM. Basic Call Model is also referred to as BCM. |
Basic Encoding Rules |
Standard rules used to encode the data units as defined in ASN.1. BER is the encoding technique, ASN.1 is the abstract syntax description language. The Basic Encoding Rules are also referred to as BER. See also other encoding rules such as PER. |
BCM |
Basic Call Model For more information, refer to the entry for Basic Call Model. |
BE |
Back-end For more information, refer to the entry for Back-end. |
BER |
Basic Encoding Rules For more information, refer to the entry for Basic Encoding Rules. |
Berkeley System Distribution |
Version of the UNIX operating system that was developed at and distributed from the University of California at Berkeley. A Berkeley System Distribution is also referred to as BSD. |
Big-endian |
Within the context of computer system and network design, a big-endian orientation puts the most significant (largest) digits first in numerical encoding schemes. |
Billing Plug-In |
Billing Plug-In is also referred to as BIPI. |
BIPI |
Billing Plug-In For more information, refer to the entry for Billing Plug-In. |
BNF |
Backus Naur Form For more information, refer to the entry for Backus Naur Form. |
Bridge |
A device used to join call parties within a session. Two types of bridge are supported. TDM bridges join together the voice data streams of two call parties through the TDM bus. SoftDSP bridges can join two or more call parties and can join different types of media streams. |
BSD |
Berkeley System Distribution For more information, refer to the entry for Berkeley System Distribution. |
Bulk Operation |
Data flow between a Service Management System (SMS) and the SEP employs two types of operation, simple and bulk. Simple operations allow the SMS to propagate changes to the SEP database for a single subscriber (for example create, delete, read and write). Bulk operations typically involve access to data for multiple subscribers. For example, when provisioning a new service, bulk operations are used to change large amounts of data in the SEP database. Input and output for bulk operations are file based. |
C | |
Back to Index | |
Call |
An arrangement providing a signaling and/or a transport relation between two or more users, or between one or more end users and the network, for the purpose of exchanging information. |
Call Authorization |
Acceptance or rejection of calls from an H.323 terminal. The gatekeeper may reject calls from a terminal because of restricted access to or from particular terminals or gateways, or restricted access during certain periods of time. Call authorization is an optional gatekeeper service. |
Call Context |
Call specific details containing relevant information on an individual call. |
Call Context Database |
A database maintained by the SEP that consists of information on all on-going Transaction Capability Application Part (TCAP) transactions. The database contains all the information required by the SEP to process and manage open TCAP transactions. There is a one-to-one correlation between open TCAP transactions (as seen by the SS7 network and/or remote Service Switching Points [SSPs]) and call contexts (i.e. entries in the call context database). |
Call Control |
The set of functions used to process a call (e.g. provide service features and establish, supervise, maintain and release connections). |
Call Control API |
A Java API specific to the HP Opencall Media Platform. Call Control API is also referred to as CCAPI. |
Call Control Function |
The application process that provides call/connection processing and control. Call Control Function is also referred to as CCF. |
Call Data Record |
A record containing some data about a call handled by entities in the network. Usually collected for billing purposes. A Call Data Record is also referred to as CDR. |
Call Flow |
A representation used to specify the exchange of protocol messages between network entities. It is defined during the service requirement/specification phase. |
Calling Party |
The end user that originates a two-party call, or a two-party pair on a multi-party call. |
Call Model |
A generic representation of SSP call processing activities required to establish, maintain, and clear a basic call. The call model consists of point in call (PICs), detection points (DPs), and triggers. |
Call Party |
A participant within a call session. A call party has one or two legs. Its main leg is a TrunkLeg connecting it to the network. It may have a secondary leg, a MediaGroupLeg, to connect it to a media group. See Leg for information regarding TrunkLeg and MediaGroupLeg. |
Call Segment |
A grouping of all the legs connected to a particular connection point. Call Segment is also referred to as CS. |
Call Setup |
The call processing modeled by the first six points in call of the originating BCM, or the first four points in call of the terminating BCM. |
Call Setup Routing |
Two alternative modes for routing the call setup (Q.931) and control (H.245) channels. Routed mode routes the call setup and control channel through the gatekeeper. Direct mode forms a direct connection between two endpoints of the setup and control channels. See also Routed Mode and Direct Mode. |
Capability Set |
A coherent and consistent set of network capabilities which have been standardized in a particular release. Capability Set is also referred to as CS. |
CCAPI |
Call Control API For more information, refer to the entry for Call Control API. |
CCF |
Call Control Function For more information, refer to the entry for Call Control Function. |
CCS |
Common Channel Signaling For more information, refer to the entry for Common Channel Signaling. |
CCSession Object |
A session created within an OClet for each call processed by the OClet. The session is created when a call is received via the network or when a call is generated by the application. Each session must have at least one call party. |
CDR |
Call Data Record For more information, refer to the entry for Call Data Record. |
Chai Server |
The Chai server is an HP web-server written in Java that runs in the Java Virtual Machine (JVM). It is embedded in the OCMP and provides the web-serving for the OA&M interface. |
Channel |
A virtual communication path between an SLP and either an ASC switch, another SLP, or the platform. For the case of communication with an ASC Switch, this term is analogous to an Open Communication. |
Checkpoint |
A complete snapshot of the database. The checkpoint operation creates a checkpoint file which is stored on disk. If it is necessary to restore the contents of the in-memory database at any time, all the necessary information is contained in the most recent checkpoint file and associated External Update Notification (EUN) log files. |
CIC |
Circuit Identification Code For more information, refer to the entry for Circuit Identification Code. |
Circuit Identification Code |
A logical identifier used in the ISUP protocol of a voice timeslot. Circuit Identification Code is also referred to as CIC. |
CIT |
Collect Information Tool |
CLI |
Command Line Interface For more information, refer to the entry for Command Line Interface. |
Client |
A computer or an application that requests services within a distributed configuration. |
Cluster |
A group of servers composed by all the front-end of the platform and networked together in a platform. A 2-host cluster contains two host servers to provide High Availability of SS7 processing. A 2-host cluster can operate in active/standby mode or parallel engine mode. A 1-host cluster does not support High Availability. A 2-host cluster was previously called a duplex platform, and a 1-host cluster was previously called a simplex platform. |
CM |
Conference Manager For more information, refer to the entry for Conference Manager. |
CMIS |
Common Management Information System. For more information, refer to the entry for Common Management Information System. |
Collector Plug-In |
Collector Plug-In is also referred to as COPI. |
Command Line Interface |
A programming interface that allows the user to communicate with an operating system. Command Line Interface is also referred to as CLI. |
Common Channel Signaling |
An out-of-band signaling using the SS7 protocol specified by ANSI standards. Common Channel Signaling is also referred to as CCS. |
Common Management Information System |
See Recommendation X.700. Common Management Information System is also referred to as CMIS. |
Conference Manager |
A part of the RADVision H.323 Protocol Stack consisting of functions that implement the core part of H.323 Recommendation. The Conference Manager takes care of initialization and setting up calls and channels, managing the calls and channels, and closing them. The Conference Manager is also referred to as CM. |
Connectionless Service |
A service in which data is sent without first establishing an end-to-end connection with the destination. It is not possible to determine which route the data will take, or to guarantee which that it will arrive in the correct order or at all. |
Connection Point |
The interconnection of legs in a call segment, as represented by a CP object in a connection view. Connection Point is also referred to as CP. |
Controlling Leg |
For IN CS-2, the controlling leg is the leg that represents the local access interface at local exchange or the remote access interface at transit exchange (e.g. the incoming line or trunk in an originating call segment, or the outgoing line or trunk in a terminating call segment). |
COPI |
Collector Plug-In For more information, refer to the entry for Collector Plug-In. |
Counter |
A set of predefined parameters that give information on the cell activity. |
CP |
Connection Point For more information, refer to the entry for Connection Point. |
CPU |
Central Processing Unit |
CS |
Call Segment For more information, refer to the entry for Call Segment. |
CS |
Capability Set For more information, refer to the entry for Capability Set. |
CTI |
Computer Telephony Integration |
Customer Specific Code |
A plug-in user code. |
D | |
Back to Index | |
Daemon |
A program that performs a utility function but that is not invoked explicitly. A daemon waits for a particular event to occur or specific condition to be true before carrying out its defined function. Daemons are usually spawned automatically by the platform, and either exist indefinitely or are regenerated at intervals. |
Database |
A collection of all the customer-related data needed by services executed by the SEP. The definition and contents of this database are completely under the control of the external user; no SEP specific information is stored in the database. A single SEP has a single database, so the active and standby host in a highly available platform each has its own database. A database is composed of one or more namescopes. A namescope is composed of one or more tables. A table is composed of zero (if empty), one or more rows (if not empty). A row is composed of many fields. Fields can be designated as primary or foreign keys to facilitate access to that table from other tables in the database. Data in the database can be read and/or updated by the SCPDB Application Programming Interface (API) as well as by Service Logic Programs (SLPs). The SEP database is held in memory to allow very efficient access. A Database is also referred to as DB. |
Database Management System |
A layer of software between the physical database and the user that manages all requests for database action (for example queries or updates) from the user. It keeps track of the physical details of file locations and formats, indexing schemes and so on. A DBMS also permits centralized control for security and data integrity requirements. A Database Management System is also referred to as DBMS. |
Database Schema |
A description of the structure of the data required for the service in the database, also called database schema. A data model provides the structure of the database. It does not provide any data. |
Data Definition Language |
A language used to describe data types, data models, and managed objects in HP Opencall SEP. The Data Definition Language (DDL) allows users of the HP Opencall SEP to define both the database schema and data types. It is also used to define data types used in the MIB for platform management and SLP. The description of the data is written using DDL notation in an ASCII file. Data Definition Language is also referred to as DDL. |
Datagram |
A packet transport mode where packets are routed independently and may follow different paths. Thus there is no guarantee of sequence delivery. See also Virtual Container. |
Data Management |
Establishing, updating and administering databases in the network. |
dB |
Database For more information, refer to the entry for Database. |
DBMS |
Database Management System For more information, refer to the entry for Database Management System. |
DCS |
Digital Cross Connect DCS is also referred to as DXC. For more information, refer to the entry for Digital Cross Connect. |
DDL |
Data Definition Language For more information, refer to the entry for Data Definition Language. |
Destination Point Code |
A logical network address provided by the Message Transfer Part (MTP) of the SS7 protocol. All point codes are initially allocated by the network. The MTP routing function includes a point code, the DPC, in the MTP3 level routing label to route a message. The MTP routing function usually gets the DPC from the user part such as ISUP or a translated SCCP address. A DPC is used in conjunction with an Originating Point Code for point-to-point routing in the SS7 network. Destination Point Code is also referred to as DPC |
Detection Point |
A point in basic call processing at which a processing event may be reported to the service control function and transfer of processing control can occur. Detection Point is also referred to as DP. |
Dialogue |
A conversation or an exchange of information. |
Digital Cross Connect |
An electronic cross-connect that has access to lower-rate channels in higher-rate multiplexed signals and can electronically re-arrange those channels. Digital Cross Connect is also referred to as DCS and DXC. |
Direct Mode |
Routing of the call setup (Q.931) and control (H.245) channels to form a direct connection between two endpoints without gatekeeper intervention. |
Disk Logger |
One of four event collector daemon processes. The Disk Logger writes to disk the event information it has received from the Event Handler. |
Dispatcher |
A SLP which spawns a new instance of the service for each new incoming transaction from a particular channel. |
Distributed ISUP |
A means that enables multiple applications to be simultaneously connected to the same ISDN user part of MTP on the same SS7 stack. Connecting several instances of the same application provides a loadsharing capacity. |
DP |
Detection Point For more information, refer to the entry for Detection Point. |
DPC |
Destination Point Code For more information, refer to the entry for Destination Point Code. |
DSP |
Digital Signal Processing |
DTMF |
Dual Tone Multi-Frequency For more information, refer to the entry for Dual Tone Multi-Frequency. |
Dual Tone Multi-Frequency |
A method used by the telephone system to communicate the keys pressed when dialing. Pressing a key on the phone's keypad generates two simultaneous tones, one for the row and one for the column. These are decoded by the exchange to determine which key was pressed. Dual Tone Multi-Frequency is also referred to as DTMF. |
Duplex Platform |
2 hosts in HA mode. |
DXC |
Digital Cross Connect DXC is also referred to as DCS. For more information, refer to the entry for Digital Cross Connect. |
E | |
Back to Index | |
E1 |
European telecoms transport mechanism in which data packets are multiplexed into a sequence of thirty-two 8-bit timeslots (or channels), collectively called a frame. |
ECTF |
Enterprise Computer Telephony Forum |
EFD |
Event Forwarding Discriminator For more information, refer to the entry for Event Forwarding Discriminator. |
Endpoint |
H.323 terminal, gateway, or MCU. An endpoint can call and can be called. It generates and/or terminates information streams. |
End User |
An addressable user who uses a loop-start, ground-start, or ISDN access signaling arrangement. |
ESP |
End Signaling Point |
ETSI |
European Telecommunications Standards Institute For more information, refer to the entry for European Telecommunications Standards Institute.. |
EUN |
External Update Notification For more information, refer to the entry for External Update Notification. |
EUN Handler |
SLEE process responsible for replicating changes from the active host to the standby host in the SEP. |
European Telecommunications Standards Institute |
An organization that establishes telecommunications standards for Europe. The European Telecommunications Standards Institute is also referred to as ETSI. |
Event |
The result of a call processing or operations activity in an ASC Switch that may be reported to SCP/Adjunct or to an Operating System (OS). |
Event Collector |
A daemon used to collect events, filter them if necessary then pass them onto the appropriate media (file, printer or display) or to generate actions. The event collector consists of one daemon and one or more instances. There are four event collectors: 1)Alarm Handler 2)Disk Logger 3)Print Logger 4)Event Display. |
Event Display |
One of the four event collector daemon processes. The Event Display provides an interactive view of the latest events generated by the platform displaying event information on an alphanumeric display or an X-terminal running Motif. The selection of events for display is specified by setting Event Forwarding Discriminators (EFDs) in a configuration file which is read when the event display is invoked. Usually this is reserved for events that may require immediate operator action. |
Event Forwarding Discriminator |
User-defined discriminators in the configuration files of all event collectors to control which types of event each collector receives. When an event collector is started the event handler reads the configuration file to create the filters it uses to sort events. One or more EFDs can be defined for each event collector. Each EFD consists of one or more tests which are combined. Each test compares a value from the event with a given constant. If an event matches one or more of the EFDs defined for an event collector, that event is passed to the collector. Event Forwarding Discriminator is also referred to as EFD. |
Event Handler |
Highly available process running on both SEP hosts which acts as the central collector and distributor of events. The event handler runs in the background, thus has no interface. The event handler filters events, for example using severity of events, so that different events can be passed to different event collectors. SEP event handling provides a configurable system for receiving information from monitored processes and passing it to logging and display processes. |
Event Management |
A system integrated in the SEP that is capable of taking events generated across all hosts in the platform and passing them to event collectors such as the Alarm Handler, Disk Logger, Print Logger, and Event Display. |
Execution API |
An HP-supplied component of the HP Opencall plug-in. |
Expandability |
A capability of HP Opencall SS7 which enables a platform to be expanded, increased in capacity or upgraded with minimal disruption to network service. |
External Update Notification |
An entity used to ensure that data is replicated between the active and standby hosts on the SEP. During normal SEP operation, the two hosts, active and hot standby, are running together. Each update to a data field declared in the data model is propagated to the standby host immediately (in real time, over a direct connection between the two Service Logic Execution Environments [SLEEs]) and may also be propagated to a Service Management System (SMS) depending on the replication flag of the data field being updated. Data fields may also be declared as not replicable. If no replication flag is defined, the data is propagated by default to the standby host. All EUNs are also logged to disk on both active and standby hosts. The files containing logged EUNs are known as eunlogs or EUN log files. Event Update Notification is also referred to as EUN. |
F |
|
|
Back to Index |
|
Fault Tolerance Controller |
A software component which provides fault tolerance by stopping, starting and switching processes, as required. It is responsible for the high availability of the platform; it monitors highly available processes and, in the event of a failure, switches processes to restore the service. Fault Tolerance Controller is also referred to as FTC. |
Fault Tolerant State |
Possible states of an individual High Availability (HA) detected by the Fault Tolerance Controller (FTC). It can be in one of eight states: 1)Booting 2)Active 3)Hot Standby 4)Cold Standby 5)Synchronizing 6)Switching 7)Stopping 8)Down. There are also four host (or global) states: 1)Active, 2)Stand-by 3)Down 4)Mixed. |
FE |
Front-End For more information, refer to the entry for Front-end |
FE/BE |
Front End/Back End For more information, refer to the entry for Front End/Back End. |
Finite State Machine |
A system having a finite number of states and specified transitions between states. Finite State Machine is also referred to as FSM. |
Flat File |
A file containing CDRs stored as ASCII character strings. |
Flexible Service Logic |
A feature that enables the flow of control, in an SLP, to be modified according to the value of specified variables. Program logic in an FSL is represented as a decision tree held in the database. This allows the logic to be modified by simply changing the data rather than having to modify and re-compile the service. Flexible Logic Service is also referred to as FSL. |
Flexible TypeDB |
A functionality that provides facilities for parallel service development. It allows the modification of table sizes in a typeDB file, the capability to develop services in parallel, and the ability to merge typeDB files. |
Foreign Key |
Fields sequence of a table identical to the primary key of another table to allow the user to establish relationships between tables. Tables are assigned a primary key for indexing purposes. The name of the table referenced by the foreign key must be explicitly stated. The foreign key referenced by a table must correspond to the primary key of the referenced table. A table may have at most one foreign key, but it's primary key may be referenced as a foreign key by many tables. This allows the creating of tree-like relationships between tables (however circular loops of foreign keys are not permitted). |
Front-end |
A computer or set of computers that hosts the SS7 processes in a distributed architecture. The Front-end is connected by a LAN to the Back-End which runs the user applications. The Front-end also connects to the signaling network via TSUs/TSCs. Front-end is also referred to as FE. |
Front End/Back End |
Platform where the processing is shared between a front end (stack processing) and a back end (user applications processing). Front End/Back End is also referred to as FE/BE. |
FSL |
Flexible Service Logic For more information, refer to the entry for Flexible Service Logic. |
FSM |
Finite State Machine For more information, refer to the entry for Finite State Machine. |
FTC |
Fault Tolerance Controller For more information, refer to the entry for Fault Tolerance Controller. |
G |
|
|
Back to Index |
|
Gatekeeper |
A device that provides address translation, admission control, bandwidth and zone management services to H.323 endpoints. Gatekeeper is also referred to as GK. |
GDI |
Generic Data Interface For more information, refer to the entry for Generic Data Interface. |
Generic Data Interface |
A telecommunications protocol used to send TCAP messages through TCP/IP protocol layers. GDI services must be run on a different stack from SS7 services running over TCAP. Generic Data Interface is also referred to as GDI. |
GK |
Gatekeeper For more information, refer to the entry for Gatekeeper. |
Global Title Table |
A table that contains the global titles for the SCCP users (applications) on the platform. A global title is a symbolic address (or label) that is associated with the combination of point code and sub-system number that identifies an SCCP user. The table lists these associations. In the US, the toll-free prefix 800 is a global title which identifies the application that translates the toll-free number into the true telephone number. |
GUI |
Graphical User Interface |
H |
|
|
Back to Index |
|
H.225.0 |
An ITU-T recommendation that specifies call signaling protocols and media stream packetization for packet-based multimedia communication systems. H.323 refers to H225.0. |
H.245 |
An ITU-T recommendation that defines the Control Protocol for Multimedia Communication. |
H.323 |
An ITU-T recommendation that specifies real-time multimedia communications over protocol-compliant networks. |
HA |
High Availability For more information, refer to the entry for High Availability. |
HeartBeat |
The functionality used by the adjunct to ensure the sanity of SLPs/Platform components by querying the current states of the SLPs/Platform components. |
High Availability |
A characteristic of the product so that a service can always be available. All key components of an active SEP host are replicated on a standby SEP host, allowing the SEP to guarantee continuous service availability in the event of any single failure. Each of the core SEP processes has a logical connection to its peer process via a dedicated LAN. This allows the replicated processes to share information, ensuring the standby SEP host connection is up to date with the changes made on the active SEP. A dual LAN connection exists between the two SEP hosts allowing the logical connections between peer processes to continue to function in the event of a failure in a signal LAN. High Availability is also referred to as HA. |
High Availability API |
HP-supplied components of the HP Opencall Plug-In. |
High Order path |
Notation specific to the OCMP to allow a single interface to work with both SONET and SDH hierarchies. For example, it can represent a VC4 in SDH or an STS-1 in SONET. High Order path is also referred to as HO path. |
Home Network |
The network to which the user is normally connected, or the service provider with which the user is associated. |
HO path |
High Order Path For more information, refer to the entry for High Order Path. |
Host |
A computer on which the SS7 stack and/or SEP stack software component resides. There may be several hosts in a platform. A standalone platform contains one host; a duplex platform contains two hosts. |
HP Opencall Intelligent Network Platform |
An HP netaction product |
HP Opencall Media Platform |
An HP netaction product. A large-scale, carrier-grade voice service platform. |
HP-UX |
An operating system on which the HP Opencall platform software and user applications run. |
HTTP |
Hypertext Transfer Protocol |
I |
|
|
Back to Index |
|
IAC |
Internet Access Controler For more information, refer to the entry for Internet Access Controler. |
IETF |
Internet Engineering Task Force |
IN |
Intelligent Network For more information, refer to the entry for Intelligent Network. |
INAP |
Intelligent Network Application Part For more information, refer to the entry for Intelligent Network Application Part. |
Integrated Services Digital Network |
An end-to-end digital network supporting organized digital technology and providing advanced digital services to sophisticated digital terminals. Integrated Services Digital Network is also referred to as ISDN. |
Intelligent Network |
The telecommunications network architecture that provides flexibility for facilitating the introduction of new capabilities and services, including those under customer control. The main components of an Intelligent Network are: 1) Service Switching Points 2) Signaling System 7 Network 3) Service Control Points 4) Intelligent Peripherals. An Intelligent Network is also referred to as IN. |
Intelligent Network Application Part |
An ETSI defined protocol for Intelligent Network (IN) applications that is contained in layer 7 of the OSI model on top of the Transaction Capabilities Application Part (TCAP) and provides services for applications requiting access to an IN. Intelligent Network Application Part is also referred to as INAP. |
Intelligent Peripheral |
One of the main components of the Intelligent Network (IN). The IP provides resource management of devices such as voice response units, voice announcers and Dual Tone Multi Frequency (DTMF) sensors for caller activated services. The IP is accessed by the SCP when services demand its interaction. Intelligent Peripheral is also referred to as IP. |
International Telecommunications Union-Telecommunications Standards Sector |
A permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing recommendations on them with a view to standardizing telecommunications on a worldwide basis. The International Telecommunications Union-Telecommuncations Standards Sector is also referred to as ITU-T. |
Internet Access Controler |
HP Opencall product. Internet Access Controler is also referred to as IAC. |
Internet Protocol |
A network layer protocol that packages data into a number of independent units, called datagrams, for transmission between networks. This is a connectionless service that does not guarantee delivery of datagrams in the correct order. IP is usually used in conjunction with the TCP transport layer which resolves any delivery problems. Internet Protocol is also referred to as IP. |
Inter Process Communication |
A set of programming interfaces that allows a programmer to create and manage individual program processes that can run concurrently in an operating system. Inter Process Communication is also referred to as IPC. |
IP |
Intelligent Peripheral For more information, refer to the entry for Intelligent Peripheral. |
IP |
Internet Protocol For more information, refer to the entry for Internet Protocol. |
IP Address |
The unique address of a computer attached to a TCP/IP network. IP addresses are 32 bits in length, where each octet is represented in decimal and separated by dots. |
IPC |
Inter Process Communication For more information, refer to the entry for Inter Process Communication. |
IPPI |
IP Plug-In For more information, refer to the entry for IP Plug-In. |
IP Plug-In |
IP Plug-In is also referred to as IPPI. |
ISDN |
Integrated Services Digital Network For more information, refer to the entry for Integrated Services Digital Network. |
ISDN User Part |
A SS7 circuit-related protocol used to set up, tear down and control circuits, that provides signaling messages for switched services and user facilities for voice and non-voice. ISDN User Part is also referred to as ISUP. |
ISUP |
ISDN User Part For more information, refer to the entry for ISDN User Part. |
ITU-T |
International Telecommunications Union-Telecommunications Standards Sector For more information, refer to the entry for International Telecommunications Union-Telecommunications Standards Sector. |
IVR |
Interactive Voice Responder |
J | |
Back to Index | |
JTAPI |
Java Telephony API |
JVM |
Java Virtual Machine |
K | |
Back to Index | |
Kernel |
In the operating system, the kernel is the core portion of the program. It resides in memory and performs the most essential system tasks such as disk input/output and managing system memory. |
L |
|
|
Back to Index |
|
LAN |
Local Area Network For more information, refer to the entry for Local Area Network. |
Layer |
In computer programming, layering is the organization of programming into separate functional components that interact in some sequential and hierarchical way, with each layer usually having an interface only to the layer above and below it. The reference model for communication programs is the Open Systems Interconnection (OSI) model. |
LE |
Local Exchange For more information, refer to the entry for Local Exchange. |
Leg |
An individual resource attached to a call party. CCAPI (CallControl API) supports two different types of leg: 1) A TrunkLeg corresponds to the connection of a call party to a call. 2) A MediaGroupLeg connects a media group to a call party. |
Link |
A physical connection between two nodes of an SS7 network. A link provides a bi-directional path operating at 48.5, 56 or 64 kbits/s and corresponds to one timeslot (V.35, E1 or T1). |
Linkset |
A group of links that connect the same two nodes of the SS7 network. |
Local Area Network |
A group of computers and devices that share a common communications line and typically share the resources of a single processor or server within a relatively limited area. Usually, the server has applications and data storage that are shared in common by multiple computer users. A Local Area Network is also referred to as LAN. |
Local Exchange |
An exchange in which subscriber lines terminate. Local Exchange is also referred to as LE. Synonym : Local Central Office. |
Local Point Code |
Point code (MTP3 address) of the local HP Opencall SS7 platform. There is one LPC for each SS7 stack. Therefore, a multiple stack platform will have more than one LPC. Local Point Code is also referred to as LPC. |
LO path |
Low Order path For more information, refer to the entry for Low Order path. |
Low Order path |
Notation specific to the OCMP to allow a single interface to work with both SONET and SDH hierarchies. For example, it can represent a VC12 in SDH, or VT-1.5 in SONET. Low Order path is also referred to as LO path. |
LPC |
Local Point Code For more information, refer to the entry for Local Point Code. |
M |
|
|
Back to Index |
|
Managed Object |
A view of one or more resources. The abstract view of such a resource that represents its properties as seen by (and for the purpose of) management. Managed Objects are abstractions of the various individual components or resources to be managed in the platform. The parameters that characterize objects are stored as attributes of the object. An object may also have associated notifications and actions. |
Management Function |
A set of processes used for the management of an entity (e.g. database management capabilities covering maintenance of operations, administration, maintenance, and provisioning). |
Management Information Base |
A hierarchical database of managed objects which reflects the structure of the SEP. Management operations are performed by acting upon managed objects stored in the MIB. Operations on these managed objects, and thus access to the MIB, are performed via a specialized Application Programming Interface (API), the MIB API. Management Information Base is also referred to as MIB. |
Management Information Base Application Programming Interface |
An API specifically used to get information on the structure of a MIB schema database. Management Information Base Application Programming Interface is also referred to as MIB API. |
MC/ServiceGuard |
An HP software product that controls switchover decisions for user applications. It is designed for delivering highly available applications. |
MCU |
Multipoint Controller Unit For more information, refer to the entry for Multipoint Controller Unit. |
Media Group |
A collection of media resources that are connected to the media streams of a service terminal. |
Message Set |
A complete set of messages which can be exchanged between the SEP and the SSPs. The actual message set used is defined by the service provider. |
Message Set Customization Tool |
A utility that enables the customizing of a standard message set, thus supporting additional service functionality. MSCT supports the incorporation of operator and service specific messages and parameters into the generic message set, and hence their exchange by a service. The Message Set Customization Tool is also referred to as MSCT. |
Message Signal Unit |
A means to transfer control or network management information though the SS7 network from one signaling point to another. The MSU provides the fields of the Message Transfer Part (MTP) SS7 protocol as well as an additional two fields, the Service Indicator Octet (SIO) and the Service Information Field (SIF). Message Signal Unit is also referred to as MSU. |
Message Transfer Part |
Lowest levels of the SS7 stack that provides node-to-node transmission, basic error detection/correction schemes, message sequencing, routing, message discrimination and distribution functions for the levels and applications above it. There are 3 MTP levels. MTP1, the lowest layer, is the physical layer that deals with the signaling links. MTP2 provides a basic message exchange with simple error correction based on the retransmission of unacknowledged packets. MTP3 is concerned with route and network management. On an HP Opencall SS7 platform, the MTP1 and MTP2 processes run on the telecom signaling cards, and the MTP3 processes run on the (active) host server. Message Transfer Part is also referred to as MTP. |
MIB |
Management Information Base For more information, refer to the entry for Management Information Base. |
MIB Agent |
The agent process for the Management Information Base (MIB). The MIB Agent performs operations on managed objects in the MIB and is capable of emitting notifications on behalf of managed objects. |
MIB API |
Management Information Base Application Programming Interface For more information, refer to the entry for Management Information Base Application Programming Interface. |
MIB Browser |
The MIB Browser is a general purpose user interface application which permits access to any object in the Management Information Base (MIB). This generic application can then be used to act on MIB objects to manage the whole platform. The main purposes of the MIB Browsers are: 1)To access platform management information from the MIB. 2)To perform management operations. 3)To train and validate choices for users wanting to build management applications using the MIB API. |
MIB CLI |
MIB Command Line Interface For more information, refer to the entry for MIB Command Line Interface. |
MIB Command Line Interface |
An Alternative interface to objects in the Management Information Base (MIB) that allows users to write scripts in order to perform repetitive management operations on objects in the MIB. The CLI comprises of a set of programs which internally use the MIB API to access the MIB allowing the standard MIB operations (Get, Set, Action, Create, Delete) to be performed on managed objects. MIB Command Line Interface is also referred to as MIB CLI. |
MIB Operations |
The standard set of operations which can be performed manually or via an automated process on the objects in the Management Information Base (MIB). |
Mobile Switching Center |
Mobile Switching Center is also referred to as MSC. |
MSC |
Mobile Switching Center For more information, refer to the entry for Mobile Switching Center. |
MSC |
Media Stream Container |
MSCT |
Message Set Customization Tool For more information, refer to the entry for Message Set Customization Tool. |
MSU |
Message Signal Unit For more information, refer to the entry for Message Signal Unit. |
MTP |
Message Transfer Part For more information, refer to the entry for Message Transfer Part. |
Multipoint Controller Unit |
An endpoint on the LAN which enables three or more terminals and Gateways to participate in a multipoint conference. A Multipoint Controller Unit is also referred to MCU. |
N |
|
|
Back to Index |
|
Namescope |
Part of the structure of the SEP Database. A namescope defines a set of tables which can make references to each other using foreign keys. A namescope is the grouping of tables where each table has a unique name. In practice, a namescope is defined (using DDL) to encapsulate the collection of tables being used by a particular service. |
NAP |
Network Access Point For more information, refer to the entry for Network Access Point. |
NAS |
Network Access Server For more information, refer to the entry for Network Access Server. |
National ISDN 2 protocol |
National ISDN 2 protocol is also referred to as NI2C. |
Neighbor Gatekeeper |
A mechanism by which the OCMC Gatekeeper optimizes inter-zone communication. A list of Neighbor Gatekeepers and their IP addresses allows the gatekeeper to communicate directly with the gatekeeper called endpoint. As a result, there is no need for the gatekeeper to multicast an LRQ message to the entire network. |
Network Access Point |
The point of connection of a physical entity that provides network access for users. Network Access Point is also referred to as NAP. |
Network Access Server |
Network Access Server is also referred to as NAS. |
Network Manager |
The entity providing the basic switching and transmission capabilities as well as the service execution capabilities (offered by the SCP, SDP, and IP) to the Service Manager. The NM is also responsible for the development and maintenance of the transmission, switching and service execution capabilities. The NM encompasses both the TMN network management functionality and the network element management functionality. Network Manager is also referred to as NM. |
Network Operator |
The network operator is responsible for the development, provision and maintenance of real-time networking services and for operating the corresponding networks. |
Network Provider |
The organization that maintains and operates the network components required for IN functionality. A network provider may also take more than one role, e.g. also acting as Service Provider. |
NI2C |
National ISDN 2 protocol For more information, refer to the entry for National ISDN 2 protocol. |
NM |
Node Management For more information, refer to the entry for Node Management. |
NM |
Network Manager For more information, refer to the entry for Network Manager. |
NM |
Node Manager For more information, refer to the entry for Node Manager |
Node |
A device that is connected to the network and is capable of communicating with other network devices. |
Node Management |
Node Management is also referred to as NM. |
Node Management System |
A set of management applications for managing and monitoring the active and standby SEP hosts. These applications run on a remote workstation to minimize the impact on the processing of TCAP traffic. |
Node Manager |
A system part of an SEP that implements part of the SMF of the IN functional architecture. Node Manager is also referred to as NM. |
No Operation |
Used to indicate that, by default, a method does nothing. If the method is to perform some operations, then it must be customized by supplying the code to perform the desired operations. No Operation is also referred to as NOP. |
NOP |
No Operation For more information, refer to the entry for No Operation. |
Notification |
Information emitted by a managed object relating to an event that has occurred within the managed object. |
O |
|
|
Back to Index |
|
OA&M |
Operation, Administration and Maintenance. An OA&M API is provided for each layer of the SS7 stack. |
OC |
Optical Carrier OC is also referred to as OC-n. For more information, refer to the entry for Optical Carrier. |
OC-3 |
Optical Carrier Type 3. |
OCAL |
Opencall Layer For more information, refer to the entry for Opencall Layer. |
OClet |
Java programs that processes telephony calls in the same way Servlets process HTTP requests. Java service programs (applications) are termed OClets by analogy to the concept of Servlets. |
OCMC |
Opencall Multiservice Controller For more information, refer to the entry for Opencall Multiservice Controller. |
OC-n |
Optical Carrier OC-n is also referred to as OC. For more information, refer to the entry for Optical Carrier. |
OMAP |
Operations and Maintenance Application Part |
OPC |
Originating Point Code For more information, refer to the entry for Originating Point Code. |
Opencall Layer |
Layer used by the NI2C stack to communicate with the upper layers (IAC services which perform the ISUP/NI2C conversion and HA framework). The Opencall Layer is also referred to as OCAL. |
Opencall Multiservice Controller |
Opencall Multiservice Controller is also referred to as OCMC. |
Operational Service Logic Program |
An SLP becomes active when the SlpVersion object in the MIB is enabled. When this happens, an instance of the SLP is loaded into the SLEE, and waits in the initial state. The platform then sends the signal SIG_RUN to this SLP instance. In this case, the SLP instance is known as an Operational Service Logic Program (OSLP). This instance is terminated by the platform sendig the signal SIG_HALT when the SLP is disabled. As the SIG_RUN signal is only sent when the SLP is enabled, there can be only one OSLP per SLP. Note that on Multislee platform (typically IN > 4.0) there is one OSLP per SleeInstance. An Operational Service Logic Program is also referred to as OSLP. |
Operations Support Systems |
Operations Support Systems are also referred to as OSS. |
Optical Carrier |
The basic unit of transmission in SONET. The OCMP supports OC-3 at 155.52Mbit/s. Optical carrier is also referred to as OC and OC-n (where n is the number representing the signal rate in the range 1 to 48). |
Originating Point Code |
A point code (MTP3 address) of the network node that originally sent a message. The Originating Point Code is also referred to as OPC. |
OSLP |
Operational Service Logic Program For more information, refer to the entry for Operational Service Logic Program. |
OSS |
Operations Support Systems For more information, refer to the entry for Operations Support Systems. |
Overload |
State when the rate of ISUP traffic flow from SSPs is so high that the SEP becomes congested. Overload is also referred to as OVL. |
Overload Service |
Service Logic Program (SLP) that monitors specific parameters in the Management Information Base (MIB) which serve as indicators of the current overload state. Depending on the level of overload at given intervals, the Overload Service will implement automatic call gapping to restrict ISUP traffic flow from Service Switching Points (SSPs) in the network. |
OVL |
Overload For more information, refer to the entry for Overload. |
P | |
Back to Index | |
Packed Encoding Rules |
See ASN.1 Packed Encoding Rules is also referred to as PER. |
Parallel Engine Mode |
A method of SS7 processing which can be implemented on an HP Opencall SS7 platform containing two or more hosts (an N-host platform). It enables the load to be distributed across processors and hosts, and provides High Availability of MTP3/SCCP processing. Active MTP3/SCCP processes are maintained on one host while standby MTP3/SCCP processes are maintained on a second host which can take over if the active processes fail. The TCAP processes and user applications are distributed across all hosts of the platform. |
PC |
Point Code For more information, refer to the entry for Point Code. |
PCA |
Plug-In Communications API For more information, refer to the entry for Plug-In Communications API. |
PCI |
Peripheral Component Interconnect For more information, refer to the entry for Peripheral Component Interconnect. |
PCI Mezzanine Card |
An input/output or processor card that connects onto a PCI adapter or base card. The Telecommunication Signaling Cards are PCI Mezzanine Cards. PCI Mezzanine Card is also referred to as PMC. |
PCM |
Pulse Code Modulation |
PDU |
Protocol Data Unit For more information, refer to the entry for Protocol Data Unit. |
PER |
Packed Encoding Rules For more information, refer to the entry for Packed Encoding Rules. |
Peripheral Component Interconnect |
A 32-bit bus, operating at 33MHz that allows peripheral cards to be easily incorporated into a computer or server using a 'plug and play' facility. A Telecommunication Signaling Card is a PCI Mezzanine Card that connects onto a PCI adapter card, which can be accommodated in a PCI slot in a Telecommunication Signaling Unit or directly in a host server. Peripheral Component Interconnect is also referred to as PCI. |
PIC |
Plug-In Container For more information, refer to the entry for Plug-In Container. |
PIC |
Point In Call For more information, refer to the entry for Point In Call. |
PINS |
Plug-In Network Sensor For more information, refer to the entry for Plug-In Network Sensor. |
Plain Old Telephone Service |
A call that requires nothing more than basic call handling. Plain Old Telephone Service is also referred to as POTS. |
Platform |
A collection of hardware, software, firmware and cables that together provide functionality of the SS7 node. This includes the host server(s), the HP Opencall SS7 APIs, the Telecommunication Signaling Unit(s) and Telecommunication Signaling Cards. |
Platform Management Workstation |
A computer from which the IN platform is managed. |
Platform Monitor |
A computer from which the SS7 platform is managed. The Platform Monitor is not a part of the platform, but is part of the product. |
PLMN |
Public Land Mobile Network |
Plug-In |
A facility of Opencall that provides the plug-in container (PIC), the plug-in communications API (PCA), the execution API, the high availability API (HA API), and the registry API. This facility enables customer-written code to benefit from the facilities of HP's Fault Tolerance Controller (FTC) and to communicate with the SLEE. |
Plug-In Communications API |
A component of the SEP plug-in. (This is also the name used to refer to the "channel" through which messages are exchanged between the Plug-In and the SLEE, or other client). The Plug-In Communications API is also referred to as PCA. |
PLUGIN Connection |
A layer in the SLEE that manages a plug-in communications API (PCA) connection with a plug-in server. |
Plug-In Container |
A component of HP Opencall plug-in used to encapsulate user applications (called plug-ins) so that they can be managed by the FTC and can communicate with the SLEE (or other client). Plug-in Container is also referred to as PIC. |
Plug-In Network Sensor |
A sensor that provides the High Availability (HA) property of IP connections for HP Opencall platforms. Its purpose is to make the IP of a duplex platform supporting an HA application seen as a single host from the Internet, therefore making an HP Opencall SEP switchover transparent to other IP hosts connected to the SEP. The PINS also supports dual-LAN configurations for a simplex SEP. Plug-In Network Sensor is also referred to as PINS |
PMC |
PCI Mezzanine Card For more information, refer to the entry for PCI Mezzanine Card. |
Point Code |
An MTP3 level network address which identifies a node. It is made up of three components: the network, the cluster of nodes within the network and, finally, the member node of the cluster. Each point code corresponds to an SS7 protocol stack. Therefore, a node running multiple stacks will have multiple point codes. A unique number is allocated to each node in the SS7 network. The point code allocated to the local server is known as the Local Point Code (LPC). Point codes are allocated to SS7 nodes to which the local server can send messages are Destination Point Codes (DPCs). Point Code is also referred to as PC |
Point In Call |
A generic representation of a sequence of actions (e.g. underlying call processing and access processing actions) at a particular point in basic call processing, as modeled by the Basic Call Model (BCM). Point In Call is also referred to as PIC. |
PostMaster |
A message passing service based on a selective broadcasting mechanism. |
POTS |
Plain Old Telephone Service For more information, refer to the entry for Plain Old Telephone Service. |
Primary Key |
Part of the structure of the SEP Database. Each table in the database has one, and only one, primary key, which is defined as a sequence of fields starting at the beginning of the row. The primary key is used to identify table rows and to retrieve them from the database using the primary key index. |
Primary Route |
A route that is normally used to carry traffic to a destination (provided the required links are available). If the route is down, the traffic is sent via other primary routes. If no primary route is available, the traffic is sent via secondary routes. |
Print Logger |
One of the four event collector daemon processes. The print logger prints event information received from the event handler at print destinations. Multiple print destinations can be controlled from a single print logger. |
Process Identifier |
A number used to identify a process running on a UNIX operating system. |
Propagation |
Mechanism of sending files between the SEP and a Service Management System (SMS) or between the active SEP host and the standby SEP host. |
Protocol |
A set of rules that endpoints in a telecommunication connection use when they communicate. Protocols exist at several levels in a telecommunication connection. There are protocols between each of several functional layers and the corresponding layers at the other end of a communication. Both endpoints must recognize and observe a protocol. |
Protocol Data Unit |
Refer to Recommendation X.200 - OSI Basic Reference Model. Protocol Data Unit is also referred to as PDU. |
PSTN |
Public Switched Telephony Network For more information, refer to the entry for Public Switched Telephony Network. |
Public Switched Telephony Network |
A telecommunications network established to perform telephone services for the public subscribers. Public Switched Telephony Network is also referred to as PSTN. |
Q | |
Back to Index | |
Q.921 |
Layer that provides the specification for the ISDN data link layer for ITU-T. |
Q.931 |
An ITU-T recommendation that specifies procedures for establishing, maintaining and clearing network connections. |
Q.931 Encoding Rules |
Q.931 Encoding Rules is also referred to as QER. |
QER |
Q.931 Encoding Rules For more information, refer to the entry for Q.931 Encoding Rules. |
R | |
Back to Index | |
RAS |
A protocol for registration, admission and status. RAS is included in H.225.0. |
Redundant Link Manager |
Layer of the NI2C stack that provides virtual link management over IP networks. It manages redundant UDP (User Datagram Protocol) links between IAC and the remote NASes. Redundant Link Management is also referred to as RLM. |
Registry API |
A component of the HP Opencall plug-in. |
Relational Database |
A type of database or database management system that stores information in tables (i.e. rows and columns of data) and conducts searches by using data in specified columns of one table to find additional data in another table. In a relational database, the rows of a table represent records (collections of information about separate items) and the columns represent fields (particular attributes of a record). The SEP database is a relational database. |
RLM |
Redundant Link Manager For more information, refer to the entry for Redundant Link Manager. |
Route |
A signal path defined in terms of an Adjacent Point Code and a Destination Point Code. That is, a route is specified by means of a neighbouring node and the destination node, without specifying the nodes in between. Routes can be primary or secondary. See also Primary Route and Secondary Route. |
Routed Mode |
The routing of the call setup (Q.931) and control channel (H.245) through the gatekeeper. See Call Setup Routing. |
Row |
A structural element of a database. |
RTC |
Run Time Control |
S | |
Back to Index | |
SAM |
System Administration Manager For more information, refer to the entry for System Administration Manager. |
SCCP |
Signaling Connection Control Part For more information, refer to the entry for Signaling Connection Control Part. |
SCCP |
Signaling Connection Control Point For more information, refer to the entry for Signaling Connection Control Point. |
SCE |
Service Creation Environment For more information, refer to the entry for Service Creation Environment. |
SCEF |
Service Creation Environment Function. For more information, refer to the entry for Service Creation Environment Function. |
SCEP |
Service Creation Environment Point For more information, refer to the entry for Service Creation Environment Point. |
SCF |
Service Control Function For more information, refer to the entry for Service Control Function. |
SCP |
Service Control Point For more information, refer to the entry for Service Control Point. |
SCPDB API |
SCPDB Application Programming Interface For more information, refer to the entry for SCPDB Application Programming Interface. |
SCPDB Application Programming Interface |
An application programming interface that allows the SMS to interact with the SEP database to create, read, write and delete rows in tables. SCPDB Application Programming Interface is also referred to as SCPDB API. |
SCPS |
Service Control Point Simulator For more information, refer to the entry for Service Control Point Simulator. |
SCSI |
Small Computer System Interface For more information, refer to the entry for Small Computer System Interface. |
SDF |
Service Data Function For more information, refer to the entry for Service Data Function. |
SDH |
Synchronous Digital Hierarchy For more information, refer to the entry for Synchronous Digital Hierarchy. |
SDK |
Software Development Kit |
SDL |
Specification and Description Language For more information, refer to the entry for Specification and Description Language. |
SDL Design Tool |
SDL Design Tool is also referred to as SDT. |
SD-UX |
Software Distributor commands are included with the HP-UX operating system and manage software on a local host. |
SDP |
Service Data Point For more information, refer to the entry for Service Data Point. |
SDT |
SDL Design Tool For more information, refer to the entry for SDL Design Tool. |
Secondary Route |
A low priority route that carries traffic to a destination if no primary routes to that destination are available. |
SEE |
Service Execution Environment For more information, refer to the entry for Service Execution Environment. |
SEP |
Service Execution Platform For more information, refer to the entry for Service Execution Platform. |
SEP Simulator |
The HP-UX processes which run on the SCE platform to simulate the SEP in the SCE validation environment. |
Server |
The side that performs a service for the client in a client/server architecture. |
Service |
A telecommunications-based service (e.g. freephone, call-forwarding or virtual private networking) consisting of one or more integrated features that the network provides to a user and bills to a subscriber. |
Service (OCMP) |
Refer to OClet. |
Service Animation |
A feature of the HP Opencall Service Creation Environment (SCE) which allows SEP users to visualize the flow of service logic. |
Service Control Customization |
Functionality to personalize a stand-alone commercial telecommunications service offering, by the server on behalf of a client. |
Service Control Function |
The application of service logic to control functional entities in providing intelligent network services. Service Control Function is also referred to as SCF. |
Service Control Point |
A network node on which service logic is executed, such as value-added services (e.g. the billing for toll-free numbers). SCPs are often deployed in mated (replicated) pairs and each SCP connects to a pair of Service Transfer Points (STPs). The SEP can be considered to be an SCP once services have been deployed on the SEP. Service Control Point is also referred to as SCP. |
Service Control Point Simulator |
One of three applications that the validation environment of the HP Opencall Service Creation Environment (SCE) is composed of. The Service Control Point Simulator (SCPS) is a complete functional simulation of the HP Opencall SEP. It provides the Service Logic Execution Environment (SLEE), in which Service Logic Programs are executed and exchanges messages, with the Service Switching Point Emulator (SSPE) using Transaction Capabilities Application Part Messages (TCAP messages) over a real SS7 Stack. Service Control Point Simulator is also referred to as SCPS. |
Service Creation |
The process of using the SCE to design a new service, usually based on: 1)A service specification 2)A call model 3)A specific message set |
Service Creation Environment |
The settings, including organizational structure and computing communications resources, in which creation of new services take place before they are deployed on the operational intelligent network. Service Creation Environment is also referred to SCE. |
Service Creation Environment Function |
The set of functions that support the service creation process, the output of which includes both service logic programs and service data. Service Creation Environment Function is also referred to as SCEF. |
Service Creation Environment Point |
A physical entity that implements the service creation environment function. Service Creation Environment Point is also referred to as SCEP. |
Service Creation Platform |
A set of service-independent objects or functions that allow the creation of services in an intelligent network. |
Service Creation Process |
The conception, design and implementation of a capability to provide a service. |
Service Data |
Customer and/or network information required for the proper functioning of a service. |
Service Data Function |
The set of functions that provides for the management of service data in accordance with a service data template. Service Data Function is also referred to as SDF. |
Service Data Point |
A physical entity that implements a service data function. Service Data Point is also referred to as SDP. |
Service Deployment |
The introduction of a service into an Intelligent Network (IN) in a subscriber independent way. |
Service Execution Environment |
The parallel processing environment of multiple SPL instances (organized as multi-SLEEs), running on the Service Execution Platform (SEP). Service Execution Environment is also referred to as SEE. |
Service Execution Platform | The environment used to execute services in HP Opencall. The SEP holds the intelligence that enables services over various types of networks. Service Execution Platform is also referred to as SEP. |
Service Independent Building Block |
Service Independent Building Block is also referred to as SIB. |
Service Logic Execution Environment |
A major SEP process that supplies the environment and resources necessary to run the Service Logic Programs (SLPs) which provide the IN services. Service Logic Execution Environment is also referred to as SLEE. |
Service Logic Execution Language |
The language used by the SEP for defining Service Logic Programs (SLPs). It allows developer's to define exactly the functions a service is required to perform. The SLEL provides instructions for an SLP to interact with any or all of the following: 1)Service Switching Points (SSPs) via the TCAP handler. 2)Other Intelligent Network (IN) elements via Plug-Ins. 3)The SEP event handler. 4)The SEP database. 5)The SEP Management Information Base (MIB). 6)The SLEE log handler for logging data to disk. 7)Timers, counters and signals. Within the HP Opencall SCE, complete SLPs can be developed using SLEL and a graphical editor tool. SLEL is the output of the SCE Graphical Editor and the input of the SLEL compiler. Service Logical Execution Language is also referred to as SLEL. |
Service Logic Program |
A computer code that provides the intelligence to control the operation of the service. This is a program running on the SLEE to implement a service. Service Logic Program is also referred to as SLP. |
Service Logic Program Instance |
An SLPI handles the calls requiring the attention of the service and there can be as many instances as there are calls upon the service. There can be many SLPIs up to a configured limit. An instance may either be created by the platform to handle a new transaction or may be created by another service instance (OSLP or SLPI) depending on the exact application. SLPIs can execute for a configurable, fixed limit of time. If they execute for longer than this time, they are automatically aborted by the platform. This prevents infinite loops which might otherwise block the SLEE. Note that strictly speaking an OSLP is a SLPI. Service Logic Program Instance is also referred to as SLPI. |
Service Management |
The management of user and/or network information required for the proper operation of a service. |
Service Management Access Function |
A functional interface between network operators and/or subscribers and network service management functional entities. Service Management Access Function is also referred to as SMAF. |
Service Management Agent Function |
The entity equivalent to the work station function between network operators and/or subscribers and network service management functional entities. Service Management Agent Function is also referred to as SMAF. |
Service Management Function |
The set of processes that support the management of user and/or network information, including service data and service logic programs that are required for the proper operation of a service. Service Management Function is also referred to as SMF. |
Service Management Platform |
Service Management Platform is also referred to as SMP. |
Service Management Point |
A physical entity that implements a service management function. Service Management Point is also referred to as SMP. |
Service Management System |
The functionality needed to operate and maintain services, to initiate and control subscriber subscriptions involving these services, and to collect and report information on their usage. Additionally, an SMS must allow its own supervision, administration and monitoring as a node in the overall Intelligent Network (IN) architecture. Service Management System is also referred to as SMS. |
Service Manager |
The entity that provides the services to its customers on a contractual basis, and which is responsible for the services offered. The SM uses the service execution, transmission and switching capabilities offered by the Network Manager to offer the services to its customers. Service Manager is also referred to as SM. |
Service Node |
A physical entity that implements a service management function, specialized resource function and service switching/call control functions. Service Node is also referred to as SN. |
Service Switching and Control Point |
The physical entity that contains the service control function, service data function and the service switching/call control functions. Service Switching and Control Point is also referred to as SSCP. |
Service Switching Function |
The set of processes that provide the communication path for interaction between a call control function and a service control function. Service Switching Function is also referred to as SSF. |
Service Switching Point | A switch with the ability to request service information from the SEP. Service requests are made when Trigger Detection Points (TDP) are activated in the call model. These TDPs have to be configured before deploying the service. Service Switching Point is also referred to as SSP. |
Service Switching Point Emulator | A part of the HP Opencall Service Creation Environment (SCE). It provides a way of emulating a Service Switching Point (SSP) in order to test services associated with a specific Message Set in the SCE Simulation environment. Service Switching Point Emulator is also referred to as SSPE. |
Service Terminal | A Service Terminal provides a runtime execution environment for an OClet. Service Terminals are created and started from the OA&M interface. |
Service Validation | The process of using the SCE to validate the new service. |
Session | A set of related messages within the flow of messages exchanged between the Plug-In and the SLEE. |
SIB | Service Independent Building Block For more information, refer to the entry for Service Independent Building Block. |
Signaling | The exchange of information between points in the network that sets up, controls and terminates each telephone call. (In in-band signaling, the exchange of signaling (call control) information is on the same channel that the telephone call itself is using). |
Signaling Connection Control Part | The part of the SS7 that provides communication between signaling nodes by adding circuit and routing information to the signaling message. The ISUP and TCAP use the SCCP and the MTP to transport information. Signaling Connection Control Part is also referred to as SCCP. |
Signaling Connection Control Point | The level 4 protocol in the SS7 Stack, which provides the routing and addressing of other entities in the SS7 network. In the SCE this level is used to connect the SEP simulator to the SSP Emulator as both entities have the same Point Code. Signaling Connection Control Point is also referred to as SCCP. |
Signaling Interface Unit | An HP Opencall SS7 network interface. Signaling Interface Unit is also referred to as SIU. |
Signaling Link Code | The Signaling Link Selection (SLS) value in ITU-T implementations. Signaling Link Code is also referred to as SLC |
Signaling Link Selection | An MTP3 value used to determine the link that is used to send a message. Signaling Link Selection is also referred to as SLS. |
Signaling System 7 | A system that puts the information required to set up and manage telephone calls on a separate network from the telephone call. The SS7 protocol divides signaling specifications into the Message Transfer Part (MTP), the Signaling Connection Control Part (SCCP), the ISDN User Part (ISUP), the Operations and Maintenance Application Part (OMAP), the Application Service Elements (ASE), and Transaction Capabilities Application Part (TCAP). Signaling System 7 is also referred to as SS7. |
Signaling Transfer Point | A signaling network node that provides packet switching. A packet is passed from STP to STP until it reaches its destination. STPs are often deployed in mated (replicated) pairs, where each pair is interfaced to the telephone line via a Service Switching Point (SSP). Signaling Transfer Point is also referred to as STP. |
Signaling Unit | A generic name for a unit of hardware which houses the cards that interface an HP Opencall SS7 platform with the SS7 signaling network. This generally refers to a Telecommunication Signaling Unit (TSU) but can also refer to the discontinued Signaling Interface Unit (SIU). A Signaling Unit is also referred to as SU. |
Simple Network Management Protocol | A standard defined by the IETF for handling management information. It is normally found as an application on top of the user datagram protocol (UDP). Simple Network Management Protocol is also referred to as SNMP. |
Simple Operations | Data flow between the Service Management System (SMS) and the SEP employs two types of operation, simple and bulk. Simple operations allow the SMS to propagate changes for a single subscriber, for example create, delete, read and write. Bulk operations typically involve access to the data for multiple subscribers, for example when provisioning a new service. Simple operations are targeted at a single data item or list of data items from the same row of the same table in the SEP database. In principle they perform only a single data access to the SEP database. |
Simplex | The name used in previous versions of HP Opencall SS7 for a 1-host cluster. See also Cluster |
Single Point of Failure |
Single Point of Failure is also referred to as SPOF. |
SIU | Signaling Interface Unit For more information, refer to the entry for Signaling Interface Unit. |
SLC | Signaling Link Code For more information, refer to the entry for Signaling Link Code. |
SLEE | Service Logic Execution Environment For more information, refer to the entry for Service Logic Execution Environment. |
SLEL | Service Logic Execution Language For more information, refer to the entry for Service Logic Execution Language. |
SLEL in SDL | The language used by the SEP for defining Service Logic Programs (SLPs). It allows developer's to define exactly the functions a service is required to perform. The SLEL provides instructions for an SLP to interact with any or all of the following: 1)Service Switching Points (SSPs) via the TCAP handler. 2)Other Intelligent Network (IN) elements via Plug-Ins. 3)The SEP event handler. 4)The SEP database. 5)The SEP Management Information Base (MIB). 6)The SLEE log handler for logging data to disk. 7)Timers, counters and signals. Within the HP Opencall SCE, complete SLPs can be developed using SLEL and a graphical editor tool. SLEL is the output of the SCE Graphical Editor and the input of the SLEL compiler. The syntax of SLELinSDL instructions differs slightly from those in the SLEL. SLEL is used in the HP Graphical Editor. SLELinSDL is used in the Telelogic Geographical Editor. |
SLP | Service Logic Program For more information, refer to the entry for Service Logic Program. |
SLPI | Service Logic Program Instance For more information, refer to the entry for Service Logic Program Instance |
SLS | Signaling Link Selection For more information, refer to the entry for Signaling Link Selection. |
SM | Service Manager For more information, refer to the entry for Service Manager. |
SMAF | Service Management Access Function. For more information, refer to they entry for Service Management Access Function. |
SMAF | Service Management Agent Function For more information, refer to the entry for Service Management Agent Function. |
Small Computer System Interface | A set of evolving ANSI standard electronic interfaces that allow personal computers to communicate with peripheral hardware such as disk drives, tape drives, CD-ROM drivers, printers, and scanners faster and more flexible than with previous interfaces. Small Computer System Interface is also referred to as SCSI. |
SMF | Service Management Function For more information, refer to the entry for Service Management Function. |
SMP | Service Management Platform For more information, refer to the entry for Service Management Platform. |
SMP | Service Management Point For more information, refer to the entry for Service Management Point. |
SMS | Service Management System For more information, refer to the entry for Service Management System. |
SMS Simulator | The HP-UX processes that run on the SCE platform to simulate the SMP in the creation/validation environment. |
SN | Service Node For more information, refer to the entry for Service Node. |
SNMP | Simple Network Management Protocol For more information, refer to the entry for Simple Network Management Protocol. |
SNMP Traps |
Messages sent when specific pre-defined events occur. The purpose of the traps is to provide the predefined information in a consistent way regardless of its origins. The traps can be displayed at locations specified by using management tools such as HP Open View. |
softDSP | Software Digital Signal Processing For more information, refer to the entry for Software Digital Signal Processing. |
Software Digital Signal Processing | A resource that provides a software environment for developing and running DSP algorithms. Software Digital Signal Processing is also referred to as softDSP. |
SONET | Synchronous Optical NETwork For more information, refer to the entry for Synchronous Optical Network |
Specialized Resource Function | The set of functions that provide for the control and access to resources used in providing services. Specialized Resource Function is also referred to as SRF. |
Specialized Resource Point | Physical node implementing an SRF. Specialized Resource Point is also referred to as SRP. |
Specification and Description Language | A graphical specification language defined by ITU-T which is both formal and object-orientated. This language is intended for the definition of complex, event-driver, real-time and interactive applications involving many concurrent activities that communicate using discrete signals. Specification and Description Language is also referred to as SDL. |
SPOF | Single Point of Failure For more information, refer to the entry Single Point of Failure. |
SRF | Specialized Resource Point For more information, refer to the entry for Specialized Resource Point. |
SRP | Specialized Resource Point For more information, refer to the entry for Specialized Resource Point. |
SS7 | Signaling System 7 For more information, refer to the entry for Signaling System 7. |
SS7 Stack | The SS7 protocol stack comprises of MTP1, MTP2, MTP3, SCCP, TCAP and ISUP protocol layers. In the HP Opencall SS7 documentation, stack is sometimes used to refer to the layers that run on the host server(s): MTP3, SCCP, TCAP and ISUP. |
SSCP | Service Switching and Control Point For more information, refer to the entry for Service Switching and Control Point. |
SSF | Service Switching Function For more information, refer to the entry for Service Switching Function. |
SSN |
Subsystem Number For more information, refer to the entry for Subsystem Number. |
SSP | Service Switching Point For more information, refer to the entry for Service Switching Point. |
SSPE | Service Switching Point Emulator For more information, refer to the entry for Service Switching Point Emulator. |
SSP Emulator | The HP-UX processes that run on the SCE platform to model the SSP behavior in the SCE validation environment. |
Stack Watcher | A daemon process that is part of the Event Management system integral to the SEP. The core functions of Stack Watcher are to generate statistic reports and to generate alarms from objects representing the nodes in the SS7 network. |
State (in FSM) | A description of an entity defined by the values of its object attributes at a given point in time. |
State (in SDL) | A condition in which the action of a process is suspended awaiting an input. |
State Machine |
A diagrammatic representation of a computer program, where states are represented by boxes and events are represented by curved lines joining the boxes. |
STM-1 | Synchronous Transport Module For more information, refer to the entry for Synchronous Transport Module. |
STP | Signaling Transfer Point For more information, refer to the entry for Signaling Transfer Point. |
STS-1 | Synchronous Transport Signal For more information, refer to the entry for Synchronous Transport Signal. |
SU | Signaling Unit For more information, refer to the entry for Signaling Unit. |
Subsystem Number | A subsystem is an application that runs on a network node. The SSN is a local value that identifies a specific application on the node. The SSN combined with the node's point code then provides a unique network address for the application. This address can be replaced with a label called a global title. For example, in the US, the toll-free prefix 800 is a global title that identifies the application that translates the toll-free number into the true telephone number. A subsystem number is also referred to as SSN. |
Switchover | A duplex configuration with an active and standby host allows the SEP to provide continuous service availability in the event of any single failure. Certain states of failure trigger the standby host to assume control of the signaling units and to begin processing incoming Transaction Capabilities Application Part (TCAP) traffic. The process of swapping from active host to standby host is called switchover. Switchovers can also be triggered manually by an operator or external application. |
Synchronous Digital Hierarchy | The technology for carrying many signals of different capacities through a synchronous optical hierarchy (ITU-T standard for Europe). Synchronous Digital Hierarchy is also referred to as SDH. |
Synchronous Optical Network | A standard defined by ANSI for high-speed and high-quality digital optical transmission, recognized as the North American standard for SDH. This is the technology used for carrying many signals of different capacities through a synchronous optical hierarchy. Synchronous Optical Network is also referred to as SONET. |
Synchronous Transport Module | Basic unit of transmission in SDH. Synchronous Transport Module is also referred to as STM-1 |
Synchronous Transport Signal | SONET basic frame Synchronous Transport Signal is also referred to as STS-1. |
System | The highest object level in SDL language. It can be composed of many BLOCKS. |
System Administration Manager | A GUI-based off-line tool that provides a secure way of configuring the HP Opencall SS7 platform from the Platform Manager. The tool allows you to copy the platform configuration files and modify them in a temporary directory. The tool also provides installation and propagation functions. The System Administration Manager is also referred to as SAM. |
T | |
Back to Index | |
T1 | American telecoms transport mechanism in which data packets are multiplexed into a sequence of thirty-two 8-bit timeslots (or channels), collectively called a frame. |
Table | The basic component of the data model. Data is organized in data records which represent a row of the table. Data within a row is grouped into specific fields. All rows of the table have the same fields but different data values. |
TB API | An API used by applications that require access to the data model database. |
TC | Transaction Capabilities For more information, refer to the entry for Transaction Capabilities. |
TCAP | Transaction Capabilities Application Part For more information, refer to the entry for Transaction Capabilities Application Part. |
TCAP Component | Transactions Capabilities Application Part Component For more information, refer to the entry for Transaction Capabilities Application Part Component. |
TCAP Dialogue | Transaction Capabilities Application Part Dialogue For more information, refer to the entry for Transaction Capabilities Application Part Dialogue. |
TCAP Message | Transaction Capabilities Application Part Message For more information, refer to the entry for Transaction Capabilities Application Part Message. |
TCAP-User | Transaction Capabilities Application Part User TCAP-User is also referred to as TC-User. For more information, refer to the entry for Transaction Capabilities Application Part User. |
Tcl | Tool Command Language For more information, refer to the entry for Tool Command Language. |
TCP | Transmission Control Protocol For more information, refer to the entry for Transmission Control Protocol. |
TCP Packets |
TCP Packets are also referred to as TPKT. |
TC-User | Transaction Capabilities Application Part User TC-User is also referred to as TCAP-User. For more information, refer to the entry for Transaction Capabilities Application Part User. |
TDM | Time Division Multiplexing For more information, refer to the entry for Time Division Multiplexing. |
TDP | Trigger Detection Point For more information, refer to the entry for Trigger Detection Point. |
Telecommunication Media Card | The HP OCMP interface card which allows the connection of up to 2016 64Kbps voice channels on a computer in a single PCI slot. It supports either SONET OC-3 (equivalent to 84 T1s) or SDH STM-1 (equivalent to 63 E1s) connectivity to the network with an optical fiber. Telecommunication Media Card is also referred to as TMC. |
Telecommunication Management Network | The entity which provides the means used to transport and process information related to management functions for the telecommunications network. Telecommunication Management Network is also referred to as TMN. |
Telecommunication Signaling Card | A PCI card that provides connectivity to the SS7 signaling network. A TSC can be installed in a Telecommunication Signaling Unit (TSU) or directly in a host server with a PCI bus. A Telecom Signaling Card is also referred to as TSC. |
Telecommunication Signaling Unit | An external chassis which provides PCI slots for Telecommunication Signaling Cards (TSCs) and host interface cards that together interface the HP Opencall SS7 platform to the SS7 signaling network. TSUs connect to the platform host(s) via dedicated LANs. Telecom Signaling Unit is also referred to as TSU. |
Terminal Type | Indicates the type of terminal to SCF (e.g. DTMF phone, ISDN terminal). |
Text To Speech | The automatic conversion of text streams to voice. Text To Speech is also referred to as TTS. |
Time Division Multiplexing | A type of multiplexing where two or more channels of information are transmitted over the same link by allocating a different time interval ("slot" or "slice") for the transmission of each channel. Time Division Multiplexing is also referred to as TDM. |
Timeslot |
See also Link.
|
Time To Live |
Time To Live is also referred to as TTL. |
TMC | Telecommunication Media Card For more information, refer to the entry for Telecommunication Media Card. |
TMN | Telecommunication Management Network For more information, refer to entry for Telecommunication Management Network. |
Tool Command Language | The high-level, interpreted language used for writing SSP Emulator scripts. Tool Command Language is also referred to as Tcl. |
TPKT | TCP Packets For more information, refer to the entry for TCP Packets. |
Traffic Model | A model used to specify the number of messages issued/received per second by each application protocol message the service manipulates. It is used in service reliability/endurance testing and also in sizing platforms. |
Transaction | An association between two TC providers. |
Transaction Capabilities | A peer-to-peer protocol used to support remote operations in telecommunications networks. Transactions Capabilities is also referred to as TC. |
Transaction Capabilities Application Part | The layer of the SS7 stack which is built on top of the SCCP layer and which is concerned with transferring non-circuit related information between SS7 network nodes. Transaction Capabilities Application Part is also referred to as TCAP. |
Transaction Capabilities Application Part Component | The means by which TCAP transmits a request to perform. It is either: 1)An operation (to be performed at the remote end). 2)A reply (to the operation to be returned to the requesting end). Transaction Capabilities Application Part Component is also referred to as TCAP Component. |
Transaction Capabilities Application Part Dialogue | A succession of TCAP messages exchanged between two TCAP-users. It allows, as an option: 1)The transfer and negotiation of "application context". 2)The transparent transfer of "user information". Two kinds of dialogue facilities are provided: 1)Unstructured dialogue: TC-users can send components that do not need the formation of a dialogue. Such an unstructured dialogue is supported in the protocol by the unidirectional message. There is no initiation or termination associated with an unstructured dialogue. 2)Structured dialogue: Alternatively, TC-users can send components that need the formation of a dialogue. TC-users should indicate the beginning, the continuation and the end of a dialogue; this is referred to as a structured dialogue. Transaction Capabilities Application Part Dialogue is also referred to as TCAP Dialogue. |
Transaction Capabilities Application Part Message | A TCAP message refers to a data buffer than can be exchanged by two network entities. It may contain zero, one or more TCAP components, within the limits of the message size supported by the underlaying layer. Transaction Capabilities Application Part Message is also referred to as TCAP Message. |
Transaction Capabilities Application Part User | An application that is using TCAP services. Transaction Capabilities Application Part User is also referred to as TCAP-User or TC-User. |
Transmission Control Protocol | A set of rules (protocol) used along with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. While IP takes care of handling the actual delivery of data, TCP takes care of keeping track of individual units of data (called packets) that a message is divided into for efficient routing through the internet. TCP is responsible for ensuring that a message is divided into packets that IP manages and for reassembling the packets back into the complete message at the other end. Transmission Control Protocol is also referred to as TCP. |
Trigger |
A stimulus for initiating an action. |
Trigger Detection Point | A detection point in basic call processing that is statically armed. Trigger Detection Point is also referred to as TDP. |
Trunk |
See also Linkset. |
Trunk Group | A group of channels characterized by a couple of HO path and LO path within the OCMP. A trunk group is the equivalent to an E1 or a T1. |
TSC | Telecommunication Signaling Card For more information, refer to the entry for Telecommunication Signaling Card. |
TSU | Telecommunication Signaling Unit For more information, refer to the entry for Telecommunication Signaling Unit. |
TTL | Time To Live For more information, refer to the entry for Time To Live. |
TTS | Text To Speech For more information, refer to the entry for Text To Speech. |
TUP |
Telephone User Part |
Type Database | A repository for information about data types used in the SEP and Service Logic Programs (SLPs) executing in it. The type database also contains information on all primitive types and all types given identifiers by the Data Definition Language (DDL) compiler. Type database information is specified in DDL then compiled to a binary file, type_DB, using the DDL compiler. Type Database is also referred to as typeDB. |
typeDB | Type Database For more information, refer to the entry for Type Database. |
U | |
Back to Index | |
UDP | User Datagram Protocol For more information, refer to the entry for User Datagram Protocol. |
User | An entity external to the network that uses its service(s). |
User Datagram Protocol | An unreliable transport layer on top of IP. User Datagram Protocol is also referred to as UDP. |
User Friendly Name | A user definable ID tag set as an attribute for some user definable object entities (e.g. counters). User Friendly Names facilitate the object use in services, scripts, configuration files etc. as an alternative to the more anonymous numeric ID assigned by the SEP to these processes. User Friendly Names are set when the object is defined in configuration files that are read when the SEP is started. |
V | |
Back to Index | |
VC | Virtual Container For more information, refer to the entry for Virtual Container. |
Virtual Container | Terminology specific to the SDH hierarchy. Virtual Container is also referred to as VC. |
W | |
Back to Index | |
WAP |
Wireless Application Protocol |
X | |
Back to Index | |
XML |
Extensible Markup Language |
Z | |
Back to Index | |
Zone |
A collection of terminals, gateways, and MCUs managed by a single gatekeeper in H.323 networks. A zone must include at least one terminal and may include several LAN segments connected by routers. |