Glossary of Terms and Acronyms
Contents
1 Purpose and Scope
This guide provides all users with alphabetical listings of acronyms, terms, and definitions that are related to IPWorks Operation, Administration, and Maintenance (OAM).
2 Terms
| 3G | Third Generation. Any of the mobile communication systems, including WCDMA, CDMA2000, and ULTRA TDD, that employ high-speed data transfer and radio terminal technology to enable multimedia. | |
| 3GPP | 3rd Generation Partnership Project. A collaboration agreement that brings together a number of telecommunications standards bodies which are known as "Organizational Partners". | |
| AAA | Authentication, Authorization, Accounting. A service that verifies the identity of users who request access to a network, determines, and enforces their policies (the activities, resources, and services they are permitted to use and perform), and measures their use of the network for billing purposes. | |
| Action | An executable operation triggered by setting attributes on an MO. Each action is defined in the related MOC description. | |
| AIN | Advanced Intelligent Network. The Telcordia/Bellcore version of the intelligent network, which is the Public Switched Telephone Network (PSTN) system. The AIN provides enhanced voice, video, and data services and dynamic routing capabilities by using two different networks. The actual voice call is transmitted over a circuit-switched network, but the signalling is done on a separate Packet Switched Network known as SS7. | |
| Alarm |
Raised by the system to indicate an unexpected
behavior of malfunction requiring corrective action by the user. An
alarm has at least state raise (initial detection of the fault) or
clear (when the fault no longer exists). An alarm can also change
state regarding perceived severity. Alarms are also called "stateful"
alarms to emphasize that they have a state. An active alarm is an
alarm that has been raised but not cleared. All alarm state changes including cleared state are recorded in the Alarm Log. Each alarm has an alarm Operating Instructions document. It describes the possible fault reasons, fault locations, and the potential service impact. It also describes the procedure to execute to eliminate the problem and eventually clear the alarm. | |
| Alert | A stateless alarm, that is, an alarm that can only have the raised state. As an alarm, an alert has an associated Operating Instructions document and is reported in real time as an SNMP notification. Alerts are recorded in the Alert Log but are not exposed in any list over the NBI. | |
| Alias Role | Identity of a role, which has meaning to the user. An alias role is an alias for one or more real roles. The definition of alias role allows the user to use names of roles that the user is used to. Also, the same alias can be used for several real roles. The latter can be useful when different types of MEs have defined real roles with different names, but which requires the same (or similar) authority. | |
| Application | A service enabler deployed by service providers, manufacturers, or users. Individual applications are often enablers for a wide range of services. | |
| Application blade | A blade with non-IS infrastructure functions, for example, a Media Gateway. | |
| Application blade system | A blade system with non-IS infrastructure functions, for example, a Media Gateway. | |
| ASDNS | ActiveSelect DNS. Optional extension to the IPWorks DNS Server, which makes DNS more dynamic when responding to queries. Receives monitoring reports from the ActiveSelect DNS Monitors. | |
| Attribute | Represents the configuration. The read-only attributes in the MOs describe configuration state and operational values. The writable attributes control the operation and configuration for the particular network resource. Each attribute is defined in the related MOC description. | |
| AUS | Application Unique String (defined in RFC 3402) | |
| AVP | Attribute-Value Pair. An Attribute-Value Pair (AVP), also known as name-value pair, is a fundamental data representation in computing systems and applications. Designers often desire an open-ended data structure that allows for future extension without modifying existing code or data. In such situations, all or parts of the data model are expressed as a collection of tuples <attribute name, value>; each element is an attribute-value pair. Whether the attribute names are unique or not depends on the particular application and the implementation chosen by programmers. | |
| Authentication | The process of verifying the identity of an entity. | |
| Authorization | The granting of permission based on authenticated identification. | |
| Backplane | A printed circuit board that has several connectors in parallel to each other and connects several printed circuit boards together. In IS, the backplane provides: | |
| BIND | Berkeley Internet Name Domain. An implementation of the Domain Name System (DNS) protocols. Also referred to as ISC BIND. | |
| Blackhole | Specifies a list of addresses that the DNS server does not accept queries from or use to resolve a query. | |
| Blade | A board plus an operating system. A blade is the smallest unit recognized and managed by the Integrated Site (IS). The blade can be a blade system of its own, or it can be a part of a blade system consisting of two or more blades. | |
| Blade system | A system that consists of one or more blades. A blade system has a unique name within the IS and has an active blade system OAM master function (BSOM) on one of its blades. This blade is the master of the blade system, which means that it handles all communication with the IS Management System (ISM) for the blade system. | |
| Cardinality | Can exist in the MOM between MOs in parent-child relationships, and in associations between MOs. | |
| CPI | Customer Product Information. Documentation for an ME, delivered in the Active Library Explorer. | |
| CDMA | Code Division Multiple Access. A method of dividing messages into data packets and transmitting each packet over any available network path then reassembling the packets at their destinations. CDMA allows multiple messages to be sent on the same frequency by encoding them in a digital sequence. Also see CDMA2000. | |
| CDMA2000 | The third generation (3G) of CDMA that supports mobile data communication at speeds ranging from 144 Kbps to 2 Mbps. It provides a wider bandwidth than cdmaOne and moves the core data network from a circuit-switched infrastructure to one that is packet-switched. Also see Code Division Multiple Access (CDMA) and Third Generation (3G). | |
| CIDR | Classless Inter-Domain Routing. Classless Inter-Domain Routing (CIDR), also known as supernetting, is a replacement for the old process of assigning Class A, B, and C addresses with a generalized network prefix. Instead of being limited to network identifiers (or prefixes) of 8, 16 bits or 24 bits, CIDR currently uses prefixes anywhere from 13 to 27 bits. Thus, blocks of addresses can be assigned to networks as small as 32 hosts or to those with over 500,000 hosts. This allows for address assignments that much more closely fit the specific needs of an organization. Also known as Variable Length Subset Masks (VLSM). | |
| CLI | Command-Line Interface. A means by which a user communicates with a system by typing commands into a computer. In contrast, the user of a graphical user interface (GUI) communicates with the system by using a pointer to select items on the screen such as, menu items, buttons, and icons. In the IPWorks product, it is a shell based interface for manipulating the configuration objects in interactive sessions or scripts. ECLI used to control the basic functionality and configuration of various IPWorks components, such as logging and defining parameters. Core network that part of the network that is concerned with the routing data along major data paths rather than with the final destination of that data. | |
| Cluster | A cluster is two or more systems, or nodes, that work together as a single, continuously available system to provide applications, system resources, and data to users. All nodes are connected and work together as a single entity to provide increased availability and performance. | |
| CSR | Customer Service Report. Used during the trouble reporting process to describe the problems identified. | |
| CSV | Comma-Separated Values. A Comma Separated Values (CSV) file is used for the digital storage of data structured in a table of lists form, where each associated item (member) in a group is in association with others also separated by the commas of its set. Each line in the CSV file corresponds to a row in the table. Within a line, fields are separated by commas, each field belonging to one table column. CSV files are often used for moving tabular data between two different computer programs, for example between a database program and a spreadsheet program. | |
| CUDB | Ericsson Centralized User Database (CUDB) is the data storage node used in our UDC solution to allow consolidation of subscriber data for several application front ends. CUDB provides a single point of access and administration to the subscriber data. CUDB node is based on a Distributed Cluster Architecture which guarantees high capacity with an optimal footprint and real-time availability. | |
| D' | The reference point between a pre R6 HSS/HLR and a 3GPP AAA Server. | |
| DAC | Dynamic Authorization Client. The entity originates the Change of Authorization (COA) Requests or Disconnect-Requests. The DAC can co-resident with a RADIUS authentication or an accounting server, however, this is not necessarily the case. | |
| DAS | Dynamic Authorization Server. The entity receives CoA-Request or Disconnects-Request packets. The DAS is a NAS or a RADIUS proxy. | |
| Data Model | A mapping of the contents of an Information Model into a form that is specific to a particular type of data store or repository. A data model is basically the rendering of an information model according to a specific set of mechanisms for representing, organizing, storing, and handling data. In contrast to an Information Model, a Data Model includes implementation (and protocol-) specific details. That is, rules that explain how to map MOs onto lower-level protocol constructs. | |
| Data Node | Each MySql cluster must have at least one Data Node. The Data Node stores the ENUM tables using the in-memory NDB storage engine. | |
| DDNS | Dynamic DNS Updates. Internet protocol which allows DNS clients to register their name and address bindings to the DNS server dynamically. IPWorks DHCP servers support DDNS updates to register name and address bindings in DNS for DHCP clients dynamically. | |
| Derived Data Type | Data type enhanced with extra restrictions and properties. Derived string data types contain, for example, length and content constraints. Derived integer data types contain extra range constraints. Each derived data type is defined in the related MOC description. | |
| DES | Data Encryption Standard. A Data Encryption Standard that operates on a data block (of variable length) using a key (key size varies). | |
| DN | Distinguished Name. The name of an object of an object tree that is shared between the system and the Management System. DN is in 3GPP® format (from root to leave). The DN is used to identify an MO uniquely in the system. It gives the path of the MO in the tree of objects. The system uses 3GPP formatted DNs where each relative DN part consists of the MOC name equal the MO identity. If the key attribute name is not equal to the MOC name plus id, then the key attribute name is also appended to the MOC name separated by a dot. | |
| Enumeration | Integer-name pairs defining a fixed set of named values for an attribute, return value, or action parameter. | |
| Ericsson NETCONF Interface | A machine to machine interface for configuration management of the ME using the NETCONF protocol over the Secure Shell. | |
| ECLI | Ericsson Command Line Interface. A terminal-based command line interface that is used to monitor and manage the ME. The ECLI is based on industry de facto standard patterns. | |
| ECIM | Ericsson Common Information Model. Controls the MOM structure. ECIM is based on the Common Information Model (CIM) standard. | |
| Event | Occurrence of significance to users, the MEs under surveillance and network management specifications. Events do not have states. | |
| E.164 | ITU-T standard for international public telephone numbering | |
| FQDN | Fully Qualified Domain Name is an unambiguous domain name that specifies the position of a node in the DNS tree hierarchy absolutely. To distinguish an FQDN from a regular domain name, a trailing period is added. ex: "somehost.example.com". | |
| Geographic Redundancy | Geographic redundancy ensures that data is consistent, highly available, and stored in more than one geographic location. | |
| GGSN | Gateway GPRS Support Node. An interface between the GPRS backbone network and the external Public Data Networks (radio and IP networks). It is the gateway between the GPRS network and a public or private PDN such as, an ISP, or a corporate network. | |
| GiG-E | Gigabit Ethernet. A version of Ethernet, which supports data transfer rates of 1 Gigabit (1,000 megabits) per second. | |
| Gi Interface | The Gi interface connects the GGSN to an external PDN and provides the MS access to the requested network and services. Also see SGSN. | |
| Gn Interface | The Gn interface connects SGSNs to SGSNs when the two nodes are in the same PLMN. Also see SGSN. | |
| Gp Interface | The Gp interface connects Public Land Mobile Networks (PLMN) together. | |
| GPRS | General Packet Radio Service. A radio technology based on packet-switching protocol for GSM (Global System for Mobile Communications) network. It provides fast connection setup and data transfer using unused TDMA (Time Division Multiple Access) channels in GSM network. | |
| GP | Granularity Period. The time between the initiation of two successive gatherings of measurement data. | |
| Gr' | Reference point between a pre R6 HSS/HLR and a 3GPP AAA Server. | |
| Gr Interface | The Gr interface is an SS7 signalling network used to connect the Home Location Register (HLR) and SGSNs. Also see SGSN. | |
| GRX | GPRS Roaming Network. A network that connects different PLMNs together. | |
| GTP | GPRS Tunneling Protocol. Data connection established between the MS and a PDN. | |
| GTT | Global Title Translation (GTT) is an SCCP layer capability which translates what is known as a global title (for example, dialed digits for a toll free number) into a signaling point code and a subsystem number so that it can be processed at the correct application. | |
| HA | High Availability. A system or component that is continuously operational for a desirably long length of time. Availability is measured relative to 100% operational status. | |
| Health Check Job | Health Check (HC) job is a collection of categories of rules for execution from one or more rule set files. A HC job can be manually or automatically scheduled. | |
| Health Check Rule |
A Health Check rule is a single
input entity to the health check engine. It contains information about:
| |
| Rule Set File | A Rule Set File (RSF) consists of one or more rules. It contains details about the conditions to be checked and evaluated for a particular rule. | |
| Heartbeats | Used by a Management System to monitor the interface over which the alarms or alerts are to be sent. Heartbeats are needed because a management system cannot assume that a "silent" ME behaves properly. The Heartbeat event is reported as an SNMP notification at regular intervals. | |
| IETF | Internet Engineering Task Force. An international group of network designers, operators, vendors, and researchers responsible for developing internet standards, which are expressed in Requests for comments (RFC) and also for handling internet drafts. | |
| INAP | Intelligent Network Application Protocol. INAP is a signalling protocol used in the intelligent network architecture. It is part of the SS7 protocol suite, typically layered on top of TCAP. It can also be termed as logic for controlling telecommunication services migrated from traditional switching points to computer-based service independent platforms. | |
| Information Model | An abstraction and representation of the entities (or MOs) in a managed environment, their properties, attributes, and operations, as well as the way that they relate to each other. It is independent of any specific repository, software use, protocol, or platform. | |
| Initial system start | The first start of the system when it is initially configured and its default settings are defined. The initial system start is normally performed at the factory, before the delivery of the system. | |
| InnoDB | A disk-based storage engine for MySQL. IPWorks uses this engine to store the persistent master copy of the data. | |
| Integrated Site (IS) |
A framework that hosts several
different independent applications, each having its own independent
release cycle. The IS provides a basic level of support to its applications, such as hardware management, software management, connectivity, and address allocation. | |
| Integrated Site base infrastructure |
As IS with:
| |
| Integrated Site infrastructure | An IS with: | |
| Integrated Site Management system (ISM) |
The central
management system in the Integrated Site, which provides IS internal
services to the blade systems: boot-loading, management support, configuration
support, fault management, Network File System (NFS), and others. The ISM resides on one of the blades in the SIS blade system and is assigned a logical, as well as a physical IP address on the IS Internal OAM Subnet (ISOS). This design makes it easier to move the ISM to another blade in the blade system. The other blades in the blade system have only physical IP addresses. The operator can communicate with the ISM via: | |
| Integrated Site minimum base infrastructure | The minimum infrastructure that makes an Integrated Site runnable, although not necessarily able to communicate with external networks: | |
| Internal OAM basic subnet (ISOB) | A subnet that is logically separated from all other subnets handled by the IS. All communication on the ISOB is confined to the IS domain. Thus, no routing to or from the ISOB is allowed. | |
| Internal OAM supplementary subnet (ISOS) | An extra subnet which exists solely to enable multiblade application blade systems to implement a redundant IP-interface associated to their BSOM function while avoiding so-called weak multihoming. | |
| IPsec | IP Security Protocol. A protocol used to authenticate and encrypt information exchanged over the Internet. | |
| iSCSI | In computing, iSCSI is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers. It is a popular storage area network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure. | |
| IS LAN | The IS-internal LAN over which the IS blade systems exchange data packets. The LAN is physically implemented in the backplane as a Gigabit Ethernet. | |
| Jumpstart |
In IS: A procedure where the operating
system of a computer system, for instance, a SIS blade, is installed
via a network connection. Jumpstart is only used when a reinitialization of the IS software installation is required. During a jumpstart the IS software is transferred from the IS jumpstart server to the IS node. The IS jumpstart server can contain different IS software releases. | |
| Jumpstart server | A computer that has IS software, is connected to an IS system, and from which the (new) software can be loaded into the IS system. | |
| LAN fault management | A function that collects all LAN layer 2 events (uplink and downlink traps) and, based on them, makes a decision about the suspected faulty unit and isolates it. The goal is to isolate the faulty unit within 100 ms. | |
| Link aggregation | The use of two or more links as if they were a single link. | |
| Link aggregation group | A group of two or more data channels which appear as a single logical link between blades. | |
| Link Service Access Point (LSAP) | In IS: A hardware interface between a blade and the backplane. A blade has one or more such interfaces. The interface is automatically created and deleted along with the creation of the blade. | |
| LNP | Local Number Portability. The capability of keeping the same local telephone number when switching carriers. | |
| Load Balancing | The distribution of processing and communications activity evenly across a network so that no single node is overwhelmed. | |
| LOTC | Linux® Open Telecom Cluster. A custom Ericsson operating system distribution based on GNU/Linux. The LOTC provides a Linux cluster with high-availability characteristics. | |
| Locally connected terminal |
A device connected
to a port on the switch hardware equipment directly via a cable, either
of:
Depending on the type of device and port, the locally connected terminal accesses different management functions. For some blade systems, a few commands can only be performed from a locally connected terminal.
| |
| Locking | Manual isolation and preparation for removal of a board belonging to a blade system. When you click a Lock button in the ISM GUI, the Integrated Site system, if possible, isolates the blade system gracefully and then powers down the blade system board. | |
| Locking a blade |
The locking of a blade but not
of a blade system. In blade systems that consist of more than one blade you can lock a blade without locking the blade system. When the blade has been locked, that is, its functions have been disabled and stopped, the board is powered off. | |
| Locking a blade system |
The locking of a blade
system and, as a consequence, of its blades. When you lock a blade system, all blades in the blade system are locked, that is, all functions on the blades are disabled and stopped, and finally the boards are powered off. | |
| Main Switch (MXB) |
The central switching facility
in the Integrated Site (IS). The Main Switch provides Ethernet bridging on the MAC level throughout the IS-internal LAN. The Main Switch is implemented by two MXB blade systems in each subrack. To start up an IS two MXBs are needed, but when the system is operational, you can replace a faulty MXB without switching the system off. | |
| Main Switch Blade | One of two MXB blades in each subrack. Each MXB is a blade system of its own. | |
| Maintenance bus (M-bus) | A serial bus for basic management (board reset, and so on) of boards in a subrack. | |
| ME | Managed Element. A node in the network. ManagedtElement is a single root element object in the MOM, which is the starting point for navigation. | |
| MO | Managed Object. A software object that encapsulates the manageable characteristics and behavior of a particular hardware or software resource. An MO is an instance of a MOC. An MO has normally attributes that provide information used to characterize the MOs that belong to the MOC. An MO can also have actions that allow the user to perform operations on the underlying implementation. | |
| MOC | Managed Object Class. The MOM has one or more defined MOCs. The MOCs are instantiated with real data on a deployed ME. The MOC maintains all characteristics of an MO such as attributes and actions. | |
| Managed Object Management | A folder in Active Library Explorer that contains the MOM. | |
| MOM | Managed Object Model. A structured collection of configuration information that defines the O&M capability on an ME. The MOM is defined as a set of MOCs. The MOCs contain attributes representing the configuration that can be performed by the user, and actions representing the operations that can be invoked by the user. The MOM is a static blueprint for the creation of the actual object model. | |
| Management function area (MFA) |
A distinct area
of related management functions and services in the Integrated Site
(IS). In the IS GUI, the MFAs are on the top level in the Service Frame. Most MFAs are subdivided into services, which in turn contains entry points to management functions. | |
| Management function area guide (MFAG) |
An online
document that is part of the IS help library and describes management
operations in the services of a management function area (MFA). It
also provides recommendations and guidelines regarding the attributes
and parameter settings. In MFAs where the service descriptions are large, these descriptions are in many cases moved to separate service guides (SGs). | |
| MIB | Management Information Base. The collection of MOs, which control the configuration of an ME and its functionality. | |
| MIM | Management Information Model. A view of the MOM, where certain parts of the MOM can be hidden from the user, depending on the use case. The MOM is traditionally stored offline, while a MIM is traditionally stored online for use by tools. Often the MIM is represented in a different language to the MOM, for example, XML. There is normally one file, in whatever modeling format, per MIM. The cardinality between a MOM and a MIM is one to one. | |
| Management Node | Each MySql cluster has a Management Node. The Management Node manages the configuration of the other nodes in the cluster, so user must start it before starting the other nodes and stop it after stopping the other nodes. | |
| Management terminal | A computer with a web browser that provides access to the Integrated Site Management system (ISM). The management terminal accesses the ISM: | |
| MAP | Mobile Application Part. MAP is an SS7 protocol, which provides an application layer for the various nodes in GSM and UMTS mobile core networks and GPRS core networks to communicate with each other to provide services to mobile phone users. The MAP is the application-layer protocol used to access the Home Location Register, Visitor Location Register, Mobile Switching Center, Equipment Identity Register, Authentication Center, Short Message Service Center, and Serving GPRS Support Node. | |
| MNP | Mobile Number Portability. MNP enables mobile telephone users to retain their mobile telephone numbers when changing from one mobile network operator to another. | |
| MNP SRF | Signalling Relay Function for support of MNP. | |
| MPBN | Mobile Packet Backbone Network. Part of Ericsson ENGINE Multi-Service Backbone solutions. It is an internet-class, carrier-class data backbone that enables operators to offer new or expand services over an IP infrastructure in an extremely reliable and ultra-scalable configuration. Mobile System Mobile phone system or network consists of a network of cells. Each cell is served by a radio base station from where calls are forwarded to and received from your mobile phone by wireless radio signals. | |
| MySQL | A third-party relational database management system. MySQL is a trademark of MySQL AB. | |
| MySQL Cluster | The MySQL cluster contains a RAM replica of all the ENUM data. It consists of the following different types of nodes: Management Node, Data Node, SQL Node, and NDB Node. The SQL Node acts as slave to Storage Server’s MySQL to replicate all the provisioned data. The ENUM Server uses the MySQL NDB API interface to access the data from the cluster. | |
| NDB | Network Database. A RAM-based storage engine used by MySQL Cluster. | |
| NDB Cluster HA | The HA is implemented on the management node, sql node, and data node. | |
| Netconf |
A network management protocol developed
in the IETF by the Netconf working group. It was published as RFC
4741. The Netconf protocol provides mechanisms to install, manipulate, and delete the configuration of network devices. It also can perform some monitoring functions. It uses an XML-based data encoding for the configuration data as well as the protocol messages. The Netconf protocol operations are realized on top of a simple Remote Procedure Call (RPC) layer. This in turn is realized on top of the transport protocol. | |
| Northbound | An interface that conceptualizes lower-level details. It interfaces to higher-level layers and is normally drawn at the top of an architectural overview. | |
| NBI | Northbound Interface. The interface to a Management System and a CLI client. The protocols used are ECLI, NETCONF, SFTP, and SNMP. | |
| NETCONF | Network Configuration Protocol. A network management protocol developed in the IETF and published as RFC 4741. | |
| Northbound gateway | A blade system connecting IS to the remote management network. | |
| Notification | A general term for a message that carries an alarm or alert instance. | |
| NP | Number Portability. The capability of keeping the same telephone number when switching carriers or services. | |
| Mobile number portability status | Information indicating the status of number portability for a mobile subscriber. It can be one of the following: own number ported out, own number not ported out, foreign number ported in, foreign number ported to a foreign network, foreign number not known to be ported. | |
| OAM or O&M | Operation, Administration, and Maintenance. A subsystem of an application that permits the user to operate, administer, and maintain an application. OAM gives the operator access to tasks such as, subscriber data, network data, number analysis trees, alarms, and event notification. | |
| PIC | Intelligent Network defines a Basic Call State Model (BCSM), which identifies the various states of call processing. A formal name, which known as a Point In Call (PIC), is assigned by BCSM to each call processing state. | |
| QoS | Quality of Service. The performance properties of a network service, including throughput, transit delay, and priority. QoS properties can provide different service levels for different types of network traffic. For example, streaming video usually has a higher priority than other traffic, since the consequences of interrupting streaming video are immediately apparent to the user. | |
| RADIUS | Remote Authentication Dial In User Service. It is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a network service. | |
| Remote Management | Management from a management terminal that is connected to the IS via ISER or L3X. | |
| report file | The output from the Health Check Management function is a report file. It contains the result of a HC job. | |
| Resource Group | The cluster system enables applications to be run and administered as highly available resources. | |
| Role | Equivalent to the user occupation within an organization, for example, System Administrator. A user can have one or more roles. | |
| Rule | Authorization rules specify the permissions to a set of resources within the ME. The authorization rules are grouped into roles. Authorization rules are defined locally on the ME. | |
| S6b | The interface between the PDN GW and the 3GPP AAA server in EPC network. | |
| SDP | Software Delivery Package. An archive file (TAR file) with RedHat® Package Manager (RPM®) software packages and a file describing the Ericsson product data. A software item can be an SDP. A software item represents any kind of Ericsson software product that is present on the ME. | |
| SGSN | Serving GPRS Support Node. The node through which the Mobile Station (MS) connects to a Public Data Network (PDN) to provide packet routing for a service area. | |
| SNMP | Simple Network Management Protocol. A protocol that uses a management information base (MIB) to monitor and control devices on an IP network. It can also be used to retrieve statistics from IPWorks DNS or DHCP servers. In addition SNMP traps can be generated for significant event and alarms. Also see Management Information Base (MIB). | |
| SNMP Master Agent | A "master" agent that is available on the standard transport address and port, and processes SNMP protocol messages. | |
| SNMP Subagent | A "subagent" that contains management instrumentation, such as a protocol server or element server. It communicates with SNMP Master Agent through the AgentX protocol. | |
| SQL Node | Each MySQLcluster must have at least one SQL Node. Data is replicated from the InnoDB Node to the SQL Node. The SQL Node creates the ENUM-related tables with engine type NDB. Non-ENUM-related tables are stored on the SQL Node and ENUM-related tables are stored on the Data Node. | |
| SS7 | Signalling System #7. An architecture for performing out-of-band signaling in support of the call-establishment, billing, routing, and information-exchange functions of the public switched telephone network (PSTN). It identifies functions to be performed by a signaling-system network and a protocol to enable their performance. IPWorks ERH uses it to communicate with the HLR. | |
| STa | The interface between the trusted non-3GPP IP access network and the 3GPP AAA Server. | |
| Sta+ | The reference point between the IPWorks AAA Server and trusted non-3GPP Access Network. | |
| Subrack | A shelf in a cabinet. A subrack contains slots for boards. | |
| Struct | Handles structured attributes that can contain an arbitrary number of elements of the same or different type. Each struct is defined in the related MOC description. | |
| SWm | The interface between the IPWorks 3GPP AAA Server and ePDG. | |
| SWx | The interface between the 3GPP AAA server and the HSS. | |
| SF | System Functions. Common system functions and resources for the management entity, for example, Fault Management (Fm), Performance Management (Pm), and Security Management (SecM). SystemFunctions is one of the first level branches in the MOM. | |
| SysM | System Management. Represents the system-level functions such as time handling and version handling. | |
| TCAP component | In TCAP, components are a means of invoking an operation at a remote node. A TCAP message can contain several components, invoking several operations simultaneously. | |
| Transaction | Configuration changes are applied through atomic transactions. Thus, it is ensured that all or none of the operations are executed. | |
| Transport Management | Transport-related functions and resources, for example, load sharing between all configured and available blades in the cluster, and distribution of incoming traffic to the system. Transport is one of the first level branches in the MOM. | |
| Trap | An unacknowledged SNMP message that carries a notification or heartbeat. | |
| Upgrade | A product or product version that is created to provide an increased level of functionality or performance to a user. Upgrade is also the operation to replace a previous product or product version with a new product or product version that provides an increased level of functionality. | |
| TSIG | Transaction Signature. TSIG uses shared secrets and a one-way hash function to authenticate DNS messages, particularly responses, and updates. It is mainly for resolvers and name servers to use, and flexible enough to secure DNS messages (including zone transfers) and dynamic updates. | |
| TTL | Time To Live. A field in the IP header that specifies the maximum amount of time that a packet can travel on a network before being discarded. | |
| Toll Free | Toll Free number is a special telephone number, in that the called party is charged the cost of the calls by the telephone carrier, instead of the calling party. The cost of the call to the called party is usually based on factors such as the amount of usage the number experiences, the cost of the trunk lines to the facility, and possibly a monthly flat rate service charge. | |
| Virtual LAN (VLAN or vLAN) |
An emulated, logically
separated LAN on a physical LAN. The physical LAN can host several
VLANs, each of them handling a separate subset of the total traffic.
VLANs are used for traffic separation and efficient decoupling of
broadcast domains. Separation of traffic in a VLAN is based on categorization
of packets. In their headers, the packets on the LAN contain a VLAN
identifier, which is unique to each VLAN. Types of Virtual LANs supported by IS are:
| |
| VPN | Virtual Private Network. A private network such as, a corporate LAN that uses the Internet or other public network to transport the private traffic of the network in encapsulated form. | |
| Wa | The reference point between the WLAN AN and 3GPP AAA Server. | |
| Wm | The reference point between IPWorks AAA server and the PDG node. | |