Predefined Business Objects

Business Objects and Data Sources > Introducing Business Objects and Data Sources > Predefined Business Objects

Predefined Business Objects

JViews TGO provides the following predefined business objects:

Network Elements

Network elements include any kind of shelf-based telecom or data-communications equipment (a switch, a multiplexer, a cross-connect, and so on), outside plant equipment (coax node), and peripheral equipment (terminal or printer).

Network Element Representations

A network element can be represented by a pictorial representation (bitmap image or vector drawing), a symbol, or a shape. Not all physical details of the element are visible in the representation.

Pictorial representation.The network element base is a bitmap image or vector drawing. This drawing is meant to be realistic. Several predefined bases are available for shelf-based equipment, terminals, and mobile phone access network elements. New bases can easily be introduced by providing bitmap images.

Figure 1.1 Pictorial Representations of Shelf-Based Equipment and Terminal

Symbolic representation. The network element base has a square and the network element function is denoted by a symbol containing ITU/ANSI or traditional symbols. The default type corresponding to the default symbolic network element representation is called NE (Network Element). Figure 1.2 illustrates an NE type network element: here, an add-drop multiplexer with a capacity of OC192.

Figure 1.2 Symbolic Representation of NE Type Network Element

Shape representation. The network element base has a geometric shape that symbolizes the network element type (or function class). The center of the base may contain an icon that further refines the network element function. Several predefined shapes are provided as types of the network elements. Figure 1.3 illustrates a Mux shape network element.

Figure 1.3 Shape Representation of Mux Network Element

Partial Network Elements

A partial network element is an abstraction which denotes a network element that is only part of the real-world network element. Partial network elements can be used in several situations, for example:

To represent distributed clusters where parts of a cluster need to be divided accross different subnetworks.
To allow one network element to be used by different service providers. In this case, the network element needs to be divided in several parts. Each part is represented as a partial network element and its state reflects only the elements that are interesting for the service provider that is using it.

Partial network elements are graphically represented by an icon located at the bottom left of the network element base.

Figure 1.4 Partial Network Elements Expanded and Collapsed

Shortcuts

A shortcut network element is an abstraction denoting an object that is only a reference to an existing network element.

Shortcuts can be either standard or dangling. In the first case, the network element is a shortcut to another object that is managed by the system. In the second case, the network element is a shortcut to an object that is currently not available, which means that the shortcut is dangling and needs to be validated by the management system.

Shortcut network elements are graphically represented by an icon located at the bottom left of the network element base.

Figure 1.5 Standard Shortcuts

Figure 1.6 Dangling Shortcuts

For more information about network elements, see section Network Elements.

Links

Links are used to display the transmission elements making up the network lines. Links feature the same dynamic display as network elements. Each type of link has its own graphical representation, and different link states are represented graphically by changes in color or internal pattern design. Links can also carry decorations, in particular to represent alarms. Links can be directional.

Some sample links are shown in Figure 1.7.

	A link in the disabled state.
	A link in the active state.
	A link with secondary states and a label.
	A link with an alarm cluster.

Figure 1.7 Sample Links

The drawing of a link between two nodes is, by default, automatically calculated by JViews TGO. The link calculation is performed using a layout optimizer.

The default layout optimizer provided draws direct links without intermediate points and according to a given angle. The links are attached to nodes using small horizontal or vertical segments.

For more information about links, see section Links.

Links can also be grouped in a link bundle, that is, a set of links that have the same destination node. Links in a bundle can be collapsed to a single overview link.

Groups

Groups are containers that logically group network resources. They are used to display a geographic or a functional region by grouping together either network elements (such as multiplexers, switches, and so on) or links (such as transport, access, and so on).

Groups support the whole set of state and alarm representations: alarm balloons, severity color, primary state representation graphics, status or secondary state icons, and so forth.

Groups have three kinds of visual representations: polygonal, rectangular, and linear.

Polygonal Groups

Polygonal groups are flexible containers that generally represent a group of network elements at a regional level. Polygonal groups usually do not represent a physical object, but rather a user-defined collection of objects that are not necessarily located in the same place. Polygonal groups are represented by a screened transparent polygon with a relief border as shown in Figure 1.8.

Figure 1.8 Polygonal Group with Single Minor Alarm

In this figure the group label, the alarm counter, and the alarm balloon are displayed as a cluster. The drawing of this cluster is organized around a central rectangle called a plinth which is drawn by default at the polygon center.

Rectangular Groups

Rectangular groups hold network elements that are located in the same place such as a site, a building, or a city. They can be resized to create any kind of rectangular container. Rectangular groups look like an opaque relief rectangle, as shown in Figure 1.9.

Figure 1.9 Rectangular Group with Single Warning Alarm

Rectangular groups with alarms contain an information cluster located by default at the center of the rectangle.

Linear Groups

Linear groups are bendable, "pipe-like" containers. They are used to hold a group of network elements and links or they may represent the backbone transport system in the network. The graphical representation of linear groups evokes a linear collection of objects. For example, linear groups can be used to represent all the repeaters between two line termination network elements.

Figure 1.10 shows an example of a linear group on which a critical alarm has been detected.

Figure 1.10 Linear Group with Single Critical Alarm

When an alarm is displayed on a linear group, an information cluster appears at the center of the median segment. The median segment is the segment containing the midpoint of the link.

Shortcuts

A shortcut group is an abstraction denoting an object that is only a reference to an existing group.

Shortcuts can be either standard or dangling. In the first case, the group is a shortcut to another object that is managed by the system. In the second case, the group is a shortcut to an object that is currently not available, which means that the shortcut is dangling and needs to be validated by the management system.

Shortcut groups are graphically represented by an icon located at the bottom left of the group plinth.

Figure 1.11 Standard Shortcut

Figure 1.12 Dangling Shortcut

For more information about groups, see section Groups.

Subnetworks

Subnetworks allow you to create applications that display a network inside another network. They are not pure predefined business objects in the sense that they are created automatically by the JViews TGO network component when you define a containment relationship between objects in the data source.

A subnetwork can be defined as any business object with child objects in the network component. You can display it either collapsed or expanded in the network component.

In the collapsed state, the subnetwork is represented as a single object.

Figure 1.13 Collapsed Subnetwork

In the expanded state, the subnetwork is displayed with all the objects contained in it.

Figure 1.14 Expanded Subnetwork

For more information about subnetworks, see section Subnetworks.

Shelves, Cards, Ports, and LEDs

Shelves are telecom objects that can be made up of a certain number of slots of different widths in which cards can be stored. By default, slot numbers are displayed at the bottom of the slots.

Cards are represented by rectangles that support the same base states as network elements. Like network elements, they can carry alarm and status icons. They are used to display details of modifications that have been made to the states and alarms of an item of equipment at the level of the physical card.

Figure 1.15 shows a shelf with empty slots (the first five) and cards in various states, some of them carrying alarms.

Figure 1.15 Shelf with Cards in Various States

By default, status and secondary state icons are displayed at the bottom of the card, and alarms at the top of the card. Only the letter corresponding to the highest outstanding alarm is displayed. Other counting information such as figures and + signs do not appear.

There are three different types of card:

Standard cards correspond to the description given above. Such cards can take up one or several slots on the shelf and do not necessarily extend across an entire shelf section. You can, for example, place a card starting from slot #3 of the shelf and occupying this slot, the next slot and 50% of slot 5. Each card has its own label.

An example of a set of standard cards in various states (from disabled on the left to busy and shutting down on the right) is provided in Figure 1.16.

Figure 1.16 Standard Cards in Various States

Empty slots correspond to an empty portion of the shelf for which you want to display certain characteristics, either static (a label) or dynamic (statuses and alarms). Figure 1.17 shows a set of empty slots, where the basic design does not vary.

Figure 1.17 Empty Slots

Card-carrier cards hold other cards in a linear arrangement. All cards contained in the card carrier are the same size and can contain states, statuses, and alarms. Figure 1.18 shows a set of five card carriers, each of which carries two cards (in various states). The card carrier itself can carry statuses and alarms. The area at the bottom of the card carrier is used to display a graphic representation of its state.

Figure 1.18 Several Card Carriers with Cards

Cards can contain ports and LEDs, which are called card items.

Ports are the physical interfaces of pieces of equipment and are usually located on cards, Ports can also be connectors.

Figure 1.19 Example of Ports

LEDs (Light Emitting Diode) are used to represent the state of an item of equipment through a color. Most types of equipment use LEDs as interfaces to provide the user with information on hardware and software conditions.

Figure 1.20 Examples of LEDs

For more information about shelves and cards, see section Shelves and Cards.

Base Transceiver Stations (BTS)

Base Transceiver Stations (BTS) are base stations composed of antennas that relay (receive and transmit) radio messages within cells of a cellular phone system. Each antenna has an orientation and a beam width that are graphically represented. Each antenna can have its own state and graphical characteristics.

Figure 1.21 A BTS with Three Antennas

For more information about base tranceiver stations, see section BTS (Base Transceiver Station).

Off-Page Connectors

Off-page connectors can be used in place of nodes (either groups or network elements) and can have links connected to them. They usually come in pairs and are used to show the continuation of a link from one network to another.

Figure 1.22 shows a partial network with three off-page connectors, each with a different graphic representation.

Figure 1.22 Network with Different Representations of Off-Page Connectors

For more information about off-page connectors, see section Off-Page Connectors.

Alarms

The JViews TGO alarm object is based on the alarm object defined by the Java Specification Requests (JSR)-90 workgroup. This alarm object has been designed to be used in the development of OSS/J Quality of Service APIs (telecom management applications).

Alarms are of two kinds: raw and impact.

Figure 1.23 An Alarm Table with Raw (Balloons) and Impact (Clouds) Alarms

A raw alarm is an alarm reported by a network element and carried by this element.

An impact alarm corresponds to a propagated alarm that is reported by a network element but carried by another element.

Alarms can be represented as individual objects in a table and tree. For more information, see section Alarms.

Note

Alarms can also be represented as part of the managed object (in a network or equipment view). In this case, they are considered as part of the object state and not as individual objects. For more information, see Alarm States.

PREVIOUS NEXT