ДСТУ 4071-2001
Кратко
ДСТУ 4071-2001 визначає архітектурні засади відкритого розподіленого керування (ODMA) та використання брокера об’єктних запитів (CORBA). Документ регулює взаємодію об'єктів у складних ІТ-системах та мережах управління, забезпечуючи їх сумісність.
Что сделать
При аудиті надійності автоматизованих систем управління охороною праці перевіряйте відповідність архітектури обміну даними стандартам відкритих систем для уникнення збоїв.
Темы
Касается профессий
Скачать документ
Формат .docx · доступно зарегистрированным пользователям
Текст документа
(ISO/IEC 13244:1998, Amd/1;1999, MOD)
1 2 4 1 2 2.1 2.2 2.3 З? 3.1 ODP-RM 3.2 3.3 4 5 6 6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 . 6.2.5 6.3 7 7.1 7.1.1 7.1.2 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 7.2.10 7.2.11 8 CORBA - 8.1 8.1.1 CORBA - 8.1.2 8.1.3 8.1.4 8.1.5 8.2 8.2.1 8.2.2 8.2.3 8.2.4 CORBA - В?.1 В?.1.1 В?.1.2 В?.2 В?.2.1 В?.2.2 В?.З? В?.3.1 В?.3.2 D.1 D.2 D.3 D.4 D.5 D.6 D.7 Е?.1 Е?.2 F.1 ODP - F.2 F.2.1 F.2.2 —? —? —?
INFORMATION TECHNOLOGY
OPEN DISTRIBUTED MANAGEMENT ARCHITECTUREAND SUPPORT USING COMMON OBJECT REQUEST BROKERARCHITECTURE (CORBA)
1 —? —? —? ODMA —? —? —? ODMA - — 1) 2)
2 2.1 —? ITU-T Recommendation —? ITU-T Recommendation X.701 (1997) | ISO/IEC 10040:1998 Information technology — Open Systems Interconnection — Systems management overview ( —? ITU-T Recommendation —? ITU-T Recommendation —? —? —? —? ITU-T Recommendation —? —? —? ITU-T Recommendation —? ITU-T Recommendation —? ITU-T Recommendation — ITU-T Recommendation
—? ITU-T Recommendation X.902 (1995) | ISO/IEC 10746-2:1996 Information technology — Open Distributed Processing — Reference model: Foundations ( —? ITU-T Recommendation —? ITU-T Recommendation —? ITU-T Recommendation —? ITU-T Recommendation 2.2 —? ITU-T Recommendation G.805 (1995) Generic functional architecture of transport networks ( —? ITU-T Recommendation G. 851.1 (1996) Management of the transport network— Application of the RM-ODP framework ( —? ITU-T Recommendation G.852.1 (1996) Management of the transport network— Enterprise viewpoint for simple subnetwork connection management ( —? ITU-T Recommendation G.853.2 (1996) Subnetwork connection management information viewpoint ( —? ITU-T Recommendation —? ITU-T Recommendation Q.821 (1993) Stage 2 and stage 3 description/or the Q3 interface — Alarm surveillance ( 2.3 CORBA: The Common Object Request Broker: Architecture and Specification ( —? CORBA Services; Common Object Services Specification, Object Management Group ( —? CORBA Facilities: Common Object Facilities Specification, Object Management Group ( 3.1 ODP-RM Abstraction — Action — Activity — Architecture — Behaviour — Binding — —? —? —? —? —? — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — ODP - — — — — — — — — — — — — — — — Announcement — basic engineering object — Binder — 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 3.3.7 3.3.8 3.3.9 3.3.10 3.3.11 3.3.12 3.3.13 4 ACID (Atomic Consistent Isolated Durable) — ACSE (Association Control Service Element) — API (Application Programming Interface) — ASN.1 (Abstract Syntax Notation. 1) — bmos (base management-operation server) — CMIS (Common Management Information Service) — CMISE (Common Management Information Service Entity) — CORBA (Common Object Request Broker Architecture) — Dll (Dynamic Invocation Interface) — GDMO (Guidelines for the Definition of Managed Objects) — GIOP (General Inter Orb Protocol) — GRM (General Relationship Model) — IDL (Interface Definition Language) — IR (Interface Repository) — Ir (linked reply) — Ire (linked reply client) — Irs (linked reply server) — JIDM (X/Open-NMF Joint Inter-Domain Management) — X/Open-NMF MOC (Managed Object Class) — moc (management-operation client) — mos (management-operation server) — nc (notification client) — ns (notification server) — ODMA (Open Distributed Management Architecture) — ODP (Open Distributed Processing) — ODP-RM (Reference Model for Open Distributed Processing) — OMG (Object Management Group) — ORB (Object Request Broker) — OSI-SM (OSI Systems Management) — Qo (Quality of Service) — RC (Relationship Class) — RPC (Remote Procedure Call) — SMA (Systems Management Architecture) — SMASE (Systems Management Application Service Element) — SNC (Subnetwork Connection) — SNMP (Simple Network Management Protocol) — TP (Transaction Processing) — 5 —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? 6 6.1 —? —? —? —? —? —? —? —? 6.2 6.2.1 ODMA - —? —? —? —? —? —? 6.2.2 ODMA - 6.2.3 6.2.3.1 —? —? 6.2.3.2 —? —? —? —? —? —? —? —? —? —? —?
6.2.3.2.1
6.2.3.3
—? —?
6.2.3.4 6.2.4
6.2.4.1 —? —? 6.2.5 ODMA 6.3 ODP -
7 7.1 MIS -
1
7.1.1 7.1.2 —? —? —? —?
7.2 —? —? —? —? —?
7.2.1 1. 2. 3. 4.
7.2.2 7.2.3
7.2.4 ODMA
7.2.5 7.2.6 —? —?
7.2.7 OSI -
7.2.8 —? —? 7.2.9 7.2.10 7.2.11 8 CORBA - —? —? —? —? 8.1 8.1.1 CORBA - ODP IDL 8.1.2 —? —? 8.1.3 8.1.4 8.1.5 8.2.1 8.2.2
—? stub —? stub —? 8.2.3 CORBA - 8.2.4 CORBA -
( 1. ( 2. ( —? —? —? —? —?
а?) ( Ь?) ( —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? —? ODP MIS - MIS - MIS - ( В?.1 В?.1.1 а?) Ь?) с?) d) е?) f) В?.1.2 В?.1.2.1 —? —?
В?.1.2.3 В?.2 В?.2.1 а?) Ь?) с?) d) е?) f) В?.2.2
В?.2.2.1 —? —? В?.2.2.2 В?.2.2.3 В?.З? В?.3.1 а?) Ь?) В?.3.2 —? —?
В?.3.2.1 —? —? В?.3.2.2 —? —? В?.3.2.3 —? —? а?) Ь?) с?) d) е?) f) —? —?
CHARACTERIZED BY
— log Package PACKAGE BEHAVIOUR logBehaviour BEHAVIOUR
DEFINED AS "This managed object is used to store incoming event reports and local system notifications. Additional details are defined in ATTRIBUTES logld GET, discriminatorConstruct GET-REPLACE,
administrativeState GET-REPLACE,
operationalState GET,
availabilityStatus PERMITTED VALUES Attribute-ASN1 Module.LogAvailability REQUIRED VALUES Attribute-ASN1 Module.UnscheduledLogAvailability GET, logFullAction GET-REPLACE;
NOTIFICATIONS
objectcreation, objectDeletion, attributeValueChange, statechange, processingErrorAlarm;;; REGISTERED AS smi2MObjectClass 6;
(
D.1 —? —? —? —?
D.2 meanMonitorMetric RELATIONSHIP CLASS
BEHAVIOUR meanMonitorMetricBhv BEHAVIOUR DEFINED AS
ROLE meanMonitorControlServer COMPATIBLE WITH meanMonitorControl;
ROLE observedObjectlnstanceClient COMPATIBLE WITH scanObservedObjectValue;
ROLE quaiityOfServiceAlarmClient COMPATIBLE WITH qualityOfServiceAlarm;
REGISTERED AS ;
D.3 meanMonitorControl MANAGED OBJECT CLASS
DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2”:top;
CHARACTERIZED BY meanMonitorControlPkg PACKAGE
BEHAVIOUR meanMonitorControIBhv BEHAVIOUR DEFINED AS
ATTRIBUTES
observedObjectlnstance GET-REPLACE,
observedAttributeld GET-REPLACE,
granularityPeriod GET-REPLACE.
movingTimePeriod GET-REPLACE,
derivedGauge GET-REPLACE
notificationTriggerThreshold GET-REPLACE,
re-armThreshold GET-REPLACE,
operationalState GET-REPLACE;;
REGISTERED AS ;
scanObservedObjectValue MANAGED OBJECT CLASS
DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top;
CHARACTERIZED BY scanObservedObjectValuePkg PACKAGE
BEHAVIOUR scanObservedObjectValueBhv BEHAVIOUR DEFINED AS
REGISTERED AS ;
qualityOfServiceAlarm MANAGED OBJECT CLASS
DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top;
CHARACTERIZED BY qualityOfServiceAlarmPkg PACKAGE
BEHAVIOUR qualityOfServiceAlarmBhv BEHAVIOUR DEFINED AS
NOTIFICATION
"ISO/IEC 10164-4":qua!ityOfServiceAlarmNotification;;;
REGISTERED AS ;
D.4 —? —? —? —? —? —? —? —? quality of observed observed
Service Object Object
Alarm Instance Instance
Client Server —.
observed /observed
I Object J I Object I Interface 1 vExample
Example
Control Server
D.5 ROLE observedObjectinstanceServer COMPATIBLE WITH observedObjectlnterfaceExample; REGISTERED AS ;
D.6 RELATIONSHIP OBJECT fullMeanMonitorControl;
ROLE meanMonitoi-ControlServer RELATED CLASSES fullMeanMonitorControl;
ROLE observedObjectlnstanceClient RELATED CLASSES observedObjectlnterfaceExample REPRESENTED BY RELATIONSHIP-OBJECT-USING-POINTER observedObjectlnstance;
ROLE qualityOfServiceAlarmClient RELATED CLASSES fullMeanMonitorControl; REGISTERED AS ;
D.7 observedObjectlnterfaceExample MANAGED OBJECT CLASS
DERIVED FROM "CCITT Rec. X.721 | ISO/IEC 10165-2":top;
CHARACTERIZED BY observedObjectlnterfaceExamplePkg PACKAGE
BEHAVIOUR observedObjectlnterfaceExampleBhv;
ATTRIBUTES
observedValue GET-REPLACE;;
REGISTERED AS ;
( Е?.1 —? —? —? —? —? —? —? Е?.2
" UserLabel3) <"Rec. G. 852.1", COMMUNITY:sscc, ACTION:scccl > ,
<"Rec. G.852.1", COMMUNITYzsscc. ACTION:sccc2 > .
COMPUTATIONAL-INTERFACE simpleSncPerformerlfce
OPERATIONS <setupSubnetworkConnection>;
<releaseSubnetworkConnection>;
BEHAVIOUR
setupSubnetworkConnection operation
OPERATION setupSubnetworkConnection
INPUT-PARAMETERS
subnetwork : Subnetworkid ::= REF(snQuerylfce);
snpa : SnTPId ::= REF(snTPQuerylfce);
snpz : SnTPId ::= REF(snTPQuerylfce);
dir : Directionality;
suppliedUserLabel: UserLabel;
-- - OUTPUT_PARAMETERS
newSNC : SNCId ::= REF(sncQuerylfce) ;
agreedUserLabel: UserLabel;
RAISED EXCEPTIONS
incorrectSubnetworkTerminationPoints : SnTPId; subnetworkTerminationPointDisabled : SnTPId;
subnetworkDisabled : NULL;
subnetworkTerminationPointConnected : SnTPId;
operation Fails : NULL;
wrongDirectionality : Directionality;
userLabellnUse : UserLabel;
BEHAVIOUR
PARAMETERMATCHING
subnetwork: < ssccNotConnected , ROLE:involvedSubnetwork > AND < ssccConnected , ROLEiinvolvedSubnetwork > ;
snpa : < ssccNotConnected , ROLE:potentialAEnd > AND
< scmConnected , ROLE:connectedAEnd > ;
snpz : < ssccNotConnected , ROLE. potentialZEnd > AND
< ssccConnected , ROLE:connectedZEnd > ;
dir : < ssccConnected, ROLE: involvedSubnetwork , ATTRIBUTE: directionality > ; newSNC : <ssccConnected, ROLE: involvedSubnetwork> ;
suppliedUserLabel: <ssccConnected, ROLEiinvolvedSubnetwork, ATTRIBUTE: userLabel >
OR <>; - serviceCharacteristics:<ssccConnected,ROLE: involvedServiceCharacteristics >;
PRE-CONDITIONS < ssccNotConnected> ;
- - - - networkTP - - POST CONDITIONS < ssccConnected> ;
- - - - EXCEPTIONS
IF PRECONDITION <inv 1> NOT.VERIFIED RAISE_EXCEPTION IncorrectSubnetworkTerinination Points ;
IF PRECONDITION <inv_2> NOT.VERIFIED RAISE_EXCEPTION subnetworkTerminationPointConnected ;
IF PRE CONDITION <inv_3> NOT.VERIFIED RAISE_EXCEPTION subnetworkTerminationPointConnected ;
IF POST_CONDITION <inv_l> NOT.VERIFIED RAISE EXCEPTION operationFails ;
IF POST.CONDIT10N <inv 2>NOT.VERIFIED RAISE EXCEPTION operationFails ;
IF POST.CONDITION <inv_3> NOT.VERIFIED RAISE EXCEPTION operationFails ;
IF POST CONDITION <inv_4> NOT.VERIFIED RAISE_EXCEPTION userLabell