| |
|
The prevention of unauthorized use of a resource, including the prevention of use of a resource in an unauthorized manner. |
|
|
|
For LCS an access group represents one or more access points of the same service characteristic in the same location. |
|
|
|
For LCS an access point represents an end point of the LCS. Each LCS is bound by two access points. Note that access point may not be available to the SP |
|
|
|
The characteristics of a valid transaction. Atomicity: The changes effected by a transaction on the physical and logical state (hereafter simply the state) of an application are atomic. Within the bounds of a transaction, either all the changes occur, or none of them occur. Consistency: A transaction is a correct transformation of the state. The operations executed within the bounds of a transaction do not violate any of the integrity constraints associated with the state. This requires that the transaction be a correct program. Isolation: Even though transactions execute concurrently, it appears to each transaction T, that other transactions executing concurrently with T are executed either before T or after T. Durability: Once a transaction T completes successfully (commits), the changes made to the state by T survive failures. |
|
|
|
Condition (e.g. alarm) not cleared (ITU-T Rec. M.2140). |
|
|
|
An abstraction for entities outside a system, subsystem, or class that interacts with the system, subsystem, or class. |
|
|
|
The novel reuse of an entity in a manner beyond that conceived by the originator of the entity. |
|
|
|
Mechanism to convert one entity that has a particular syntactic representation to another entity that has a different syntactic representation in order to enable interoperation of the two. The entity may range from a simple system interface to an information or data model (or fragment thereof). Effective interoperation may still require the application of a mediation layer. |
|
|
|
When 2 entities have incompatible interfaces, an adapter converts the interface of one entity to enable it to interoperate with the other entity. |
|
|
|
A collection of systems and sub-networks operated by a single organization or administrative authority. It may be subdivided into a number of routing domains. |
|
|
|
As defined in Recommendation X.701, the Systems Management Overview (SMO), but with the following restriction. With respect to a particular telecommunications service (or resource) instance, it shall be possible to manage the service with one system playing the manager role, and the other playing the agent role |
|
|
|
A role taken by an MIS-User in which it is capable of performing management operations on managed objects and of emitting notifications on behalf of managed objects. |
|
|
|
A well-defined set of information and operations that characterize a highly cohesive, loosely coupled set of business entities. ABEs are used in the SID Business Framework to represent business concepts. |
|
|
|
A set of system objects (i.e., classes, along with their attributes and methods, as well as constraints and relationships) that collectively model a well-defined set of information. The name ASE was deliberately chosen to emphasize the linkage between the business view and the system view. ASEs are not invented from first principles; rather, they arise to add detail to ABEs. |
|
|
|
An alerting indication of a condition that may have immediate or potential negative impact on the state of service resources, e.g. network element, application, system, etc. |
|
|
|
Another name, besides the object identifier, by which a trouble report may be known, referenced or identified (usually by the customer). |
|
|
|
An interaction – the invocation – initiated by a client component instance, resulting in the conveyance of information from that client component instance to a server component instance, requesting a function to be performed by that server component instance. |
|
|
|
An definition of the name of the invocation and the number, names and types of its parameters. |
|
|
|
An architecture that provides a common design scheme for applications to support operability, interoperability, packaging and deployment issues. |
|
|
|
A co-operative relationship between two application entities, formed by their exchange of application protocol control information through their use of presentation services. |
|
|
|
A component that conforms to the NGOSS Specification, provides a unit of application capability, and can be supported by the NGOSS Infrastructure and Communication services. |
|
|
|
An explicitly identified set of application service elements, related options, and any other necessary information for the interworking of application entities on an application association. |
|
|
|
The aspects of an application process pertinent to OSI |
|
|
|
Architecture is the description of a system and its parts. This description includes a specification of the elements that compose the system, the interactio | |