LogicalResource

LogicalResource : public abstract class

Created:	3/12/2005 12:00:00 AM
Modified:	7/30/2007 12:30:04 PM

Project:
Author:	AutoMagic KB LLC
Version:	6.2
Phase:	SID
Status:	Approved
Complexity:	Medium
Advanced:
UUID:	{65265AB9-9555-4dc6-ABF2-6D8CDE274AA8}
Appears In:	ManagedEntity Generalization Tree, Resource Generalization Tree, Protocol Generalization Tree, DeviceInterface Generalization Tree, Figure Pr.02 - Product, Service, Resource Domain Relationships, Product-Service-Resource Relationships, Service Class Diagram, Service-PhysicalResource Interaction, Service-Resource-Product Summary, Simplified Service Class Diagram, Fig 4SO-06 - High Level Product-Service-Resource, Fig 4SO-07, Fig 4SO-16 - Logical Resource and LogicalDeviceRoles , Fig 4SO-19 - VPN Roles, Resource and Role Summary, Resource-Service-PartyRole, ResourceSpec-Resource-ResourceRole, Fig 5LR-05 - Resource split, Fig 5LR-07 - Resource - Product, Fig 5LR-09 - Product - Resource - Service, Fig 5LR-11 - LR Subclasses, Fig 5LR-12 - LogicalDevice Detail, Fig 5LR-13 - Resources and ResourceSpecification Overview, Fig 5LR-19 - LogicalResourceRole, Fig 5LR-20 - PartyRole-ResourceRole, Fig 5LR-21 - ResourceSpec and ResourceSpecChar, Fig 5LR-22 - ResourceSpecCharValue, Fig 5LR-23 - Software, Fig 5LR-28 - DeviceInterface RFSs, Fig 5LR-31 - Protocol Interactions, Fig 5LR-37 - MTE Top-Level Hierarchy, Fig 5LR-32 - CompoundResource Model, Fig 5LR-33 - CompoundResource Instance Example, Fig 5LR-45 - ResourcePort Detail, Fig 5LR-51 - Resource-ResourceRoles, Fig 5LR-52 - LogicalResourceRole Overview, Fig 5LR-75 - ResourceSpecXXXX Biz Model, Fig 5LR-87 - LogicalResourceSpec Detailed Biz Model, Fig 5LR-88 - ResourceCharacteristic Biz Model, Fig 5LR-74- LogicalResourceSpec Biz Model, Fig 5LR-72 - LogicalDevice Biz Model, Fig 5LR-80 - MTE Biz Model, Fig 5LR-61 - CompoundResource Biz Model, Fig 5LR-65 - Pipe SubClasses, Fig 5LR-68 - IPAddress Biz Model, Fig 5LR-77 - LRSpec Subclasses Biz Model, Fig 5LR-78 - LRSpecChar Biz Model, Logical Resource Role Summary, Fig 5PR-05 , Fig 5PR-11 - PhysicalResourceSpec, Fig 5PR-36 - PhysicalResourceSpec Biz Model, Router, Resource Trouble Info, Root Business Entities, AMKB-BusinessInteraction, Fig 35 - DEN-ng Location, Fig 37 - Resource Overview, Fig 38 - Contracts and Resources, Fig 39 - Service Overview, Fig 40 - Contracts and Services, Fig 41 - Contracts and Products-Resources-Services

Copyright TM Forum 2005 This is an abstract base class for describing different logical aspects of devices (e.g., DeviceInterfaces) that constitute a Product. It has two main purposes: (1) to collect common attributes and relationships for all logical entities, and (2) to provide a convenient, single point where relationships with other managed objects can be defined.

Attributes
Associations To
Associations From
Other Links

Attribute

Details

public Integer
lrStatus

Notes:

This is an enumerated integer whose value indicates the current status of the object. The following values are defined: 0: Unknown 1: OK 2: Initializing 3: Starting 4: Paused 5: Stopping 6: Stopped 7: Degraded 8: Stressed 9: Predicted Failure 10: Error - General 11: Error - Non Recoverable 12: Not Installed or Not Present 13: In Maintenance 14: Unable To Contact 15: Lost Communications Stopped indicates that the LogicalResource is known to still exist, but it is no longer operational. However, it has not failed. Stressed indicates that the LogicalResource is functioning, but needs attention (e.g., it may be overheating, or overloaded in some way). This is similar to Predicted Failure, which indicates that this LogicalResource is functioning properly, but is predicting a failure in the near future. In Maintenance indicates that this LogicalResource is being configured, maintained, or otherwise administered and is NOT available for service. Unable To Contact indicates that the monitoring system has knowledge of this LogicalResource but has never been able to establish communications with it. In contrast, Lost Commmunications indicates that the LogicalResource has been contacted successfully in the past and is known to still exist; however, it is currently unreachable. This is an optional attribute.

public Integer
serviceState

Notes:

This is an enumerated integer that defines the availability and usage (i.e., the service state) of this LogicalResource. Its values are: 0: Unknown 1: In Service 2: Out of Service 3: Testing 4: In Maintenance 5: Not Available 6: Not Applicable This is an optional attribute.

public Boolean
isOperational

Notes:

This attribute is used to define the operational status of the object, and is implemented as a Boolean: TRUE means that the object is currently operational, and FALSE means that the object is not currently operational. This is a REQUIRED attribute.

Element	Source Role	Target Role	Details
Network Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of LogicalResources that make up this Network.<br/></p>
Location Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association defines the Location(s) that a particular LogicalResource can be found at. Note that there can be multiple Locations assigned for a particular LogicalResource.<br/></p><p> <br/></p><p>This relationship is semantically different than the PhysicalResourceLocatedAt relationship. This is because LogicalResources do not have physical presences, except through the PhysicalResource that they are bound to. For example, a DeviceInterface is bound to a PhysicalPort. The DeviceInterface doesn't have a location - the PhysicalPort does. Thus, the LogicalResource "location" is really the location of the PhysicalResource that contains, or hosts, the LogicalResource.<br/></p><p><br/></p><p>Please see the DEN-ng Location model for more information.<br/></p>
PhysicalResource Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association represents the binding between a PhysicalResource and a LogicalResource. The semantics of this binding are represented by the LogicalPhysicalResource associationClass.<br/></p><p><br/></p><p>This association defines the set of LogicalResources that a particular PhysicalResource supports.<br/></p><p><br/></p><p>Please see the DEN-ng Resource model for more details.<br/></p>
ResourceFacingService Class	Name:	Name:	<p>Copyright TM Forum 2006<br/></p><p><br/></p><p>This aggregation defines the set of LogicalResources that are required for this particular ResourceFacingService to function correctly. <br/></p><p><br/></p><p>The LogicalResourcesImplementRFS aggregation is active in nature - it signifies an active whole-part relationship between a set of LogicalResources and a ResourceFacingService. Put another way, this latter aggregation is used to identify the LogicalResources that are used so that a ResourceFacingService can function. <br/></p><p><br/></p><p>The cardinality of the LogicalResourcesImplementRFS aggregation is 0..n on the aggregate side, because PhysicalResources can be installed which use LogicalResources before a ResourceFacingService is actually implemented. AResourceFacingService can have zero or more PhysicalResources and LogicalResources for it to be instantiated. Hence, the aggregations has a 1..n cardinality on its component end.<br/></p>

Element	Source Role	Target Role	Details
LogicalResourceRole Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of logical roles that are used to describe an instance of a particular LogicalResource. <br/></p><p><br/></p><p>The difference between this aggregation and the SpecifiesLogicalResourceRoles aggregation is that this aggregation enables instances of a LogicalResource to be described using LogicalResourceRoles. In contrast, the SpecifiesLogicalResourceRoles aggregation defines functionality of a LogicalResource using LogicalResourceRoles. <br/></p><p><br/></p><p>Please see the DEN-ng Resource model for more details<br/></p>

Object	Type	Connection	Notes
Protocol	Class	Tree
LogicalResourceRole	Class	Class	Copyright TM Forum 2005 This aggregation defines the set of logical roles that are used to describe an instance of a particular LogicalResource. The difference between this aggregation and the SpecifiesLogicalResourceRoles aggregation is that this aggregation enables instances of a LogicalResource to be described using LogicalResourceRoles. In contrast, the SpecifiesLogicalResourceRoles aggregation defines functionality of a LogicalResource using LogicalResourceRoles. Please see the DEN-ng Resource model for more details
DeviceInterface	Class	Tree
Software	Class	Tree
OperatingSystem	Class	Tree
ManagedTransmissionEntity	Class	Tree
LogicalDevice	Class	Tree
NetworkAddress	Class	Tree
DeviceRole	Class	Tree
Network	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of LogicalResources that make up this Network.
Location	Class	Class	Copyright TM Forum 2005 This association defines the Location(s) that a particular LogicalResource can be found at. Note that there can be multiple Locations assigned for a particular LogicalResource. This relationship is semantically different than the PhysicalResourceLocatedAt relationship. This is because LogicalResources do not have physical presences, except through the PhysicalResource that they are bound to. For example, a DeviceInterface is bound to a PhysicalPort. The DeviceInterface doesn't have a location - the PhysicalPort does. Thus, the LogicalResource "location" is really the location of the PhysicalResource that contains, or hosts, the LogicalResource. Please see the DEN-ng Location model for more information.
PhysicalResource	Class	Class	Copyright TM Forum 2005 This association represents the binding between a PhysicalResource and a LogicalResource. The semantics of this binding are represented by the LogicalPhysicalResource associationClass. This association defines the set of LogicalResources that a particular PhysicalResource supports. Please see the DEN-ng Resource model for more details.
Resource	Class	Tree
ResourceFacingService	Class	Class	Copyright TM Forum 2006 This aggregation defines the set of LogicalResources that are required for this particular ResourceFacingService to function correctly. The LogicalResourcesImplementRFS aggregation is active in nature - it signifies an active whole-part relationship between a set of LogicalResources and a ResourceFacingService. Put another way, this latter aggregation is used to identify the LogicalResources that are used so that a ResourceFacingService can function. The cardinality of the LogicalResourcesImplementRFS aggregation is 0..n on the aggregate side, because PhysicalResources can be installed which use LogicalResources before a ResourceFacingService is actually implemented. AResourceFacingService can have zero or more PhysicalResources and LogicalResources for it to be instantiated. Hence, the aggregations has a 1..n cardinality on its component end.