Loading yang-models/_3gpp-common-management-node.yang 0 → 100644 +90 −0 Original line number Diff line number Diff line module _3gpp-common-management-node { yang-version 1.1; namespace urn:3gpp:sa5:_3gpp-common-management-node; prefix "mmgmtnode3gpp"; import _3gpp-common-top { prefix top3gpp; } import _3gpp-common-yang-types { prefix types3gpp ; } import _3gpp-common-subnetwork { prefix subnet3gpp ; } organization "3GPP SA5"; contact "https://www.3gpp.org/DynaReport/TSG-WG--S5--officials.htm?Itemid=464"; description "Defines ManagementNode IOCs"; reference "3GPP TS 28.623 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions 3GPP TS 28.622 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) 3GPP TS 28.620 Umbrella Information Model (UIM)"; revision 2023-02-14 { reference "CR-0234"; } grouping ManagementSystem_Grp { description "Represents the ManagementSystem_ IOC."; leaf userLabel { type string; description "A user-friendly (and user assignable) name of this object."; } leaf-list managedElements { type types3gpp:DistinguishedName; config false; description "Contains a list of the DN(s) of the related subclasses of ManagedElement_ instance(s)."; } } grouping ManagementNodeGrp { uses ManagementSystem_Grp; leaf vendorName { type string; config false; } leaf userDefinedState { type string; description "An operator defined state for operator specific usage"; } leaf locationName { type string; config false; description "The physical location of this entity (e.g. an address)."; } leaf swVersion { type string; config false; } } augment /subnet3gpp:SubNetwork { list ManagementNode { description "Represents a telecommunications management system (EM) within the TMN that contains functionality for managing a number of ManagedElements (MEs). The management system communicates with the MEs directly or indirectly over one or more interfaces for the purpose of monitoring and/or controlling these MEs. This class has similar characteristics as the ManagedElement. The main difference between these two classes is that the ManagementNode has a special association to the managed elements that it is responsible for managing."; key id; uses top3gpp:Top_Grp; container attributes { uses ManagementNodeGrp; } } } } No newline at end of file yang-models/_3gpp-common-mnsagent.yang 0 → 100644 +91 −0 Original line number Diff line number Diff line module _3gpp-common-mnsagent { yang-version 1.1; namespace urn:3gpp:sa5:_3gpp-common-mnsagent; prefix "magent3gpp"; import _3gpp-common-top { prefix top3gpp; } import _3gpp-common-yang-types { prefix types3gpp ; } import _3gpp-common-managed-element { prefix me3gpp ; } import _3gpp-common-subnetwork { prefix subnet3gpp ; } import _3gpp-common-management-node { prefix mmgmtnode3gpp ; } organization "3GPP SA5"; contact "https://www.3gpp.org/DynaReport/TSG-WG--S5--officials.htm?Itemid=464"; description "Defines MnsAgent IOCs"; reference "3GPP TS 28.623 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions 3GPP TS 28.622 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) 3GPP TS 28.620 Umbrella Information Model (UIM)"; revision 2023-02-14 { reference "CR-0234"; } feature MnsAgentUnderManagedElement { description "MnsAgent shall be contained under ManagedElement."; } feature MnsAgentUnderSubNetwork { description "MnsAgent shall be contained under SubNetwork."; } feature MnsAgentUnderManagedNode { description "MnsAgent shall be contained under ManagedNode."; } grouping MnsAgentGrp { description "Represents the MnsAgentGrp IOC."; leaf systemDN { type types3gpp:DistinguishedName; config false; description "Distinguished Name (DN) of a IRPAgent or a MnSAgent."; } } grouping MnsAgentSubtree { list MnsAgent { description "The MnsAgent represents the MnS producers, incl. the supporting hardware and software, available for a certain management scope that is related to the object name-containing the MnS Agent. The MnSAgent can be name-contained under an IOC as follows: 1) ManagementNode; 2) SubNetwork, if the SubNetwork does not contain a ManagementNode; 3) ManagedElement, if it is the root element. In case the MnsAgent is name-contained under a ManagementNode, the management scope is the complete management scope of the ManagementNode or a subset thereof. In case the MnsAgent is name-contained under a SubNetwork, the management scope is the complete SubNetwork or a subset thereof. In case the MnsAgent is name-contained under a ManagedElement, the management scope is the complete ManagedElement or a subset thereof."; key id; uses top3gpp:Top_Grp; container attributes { uses MnsAgentGrp; } } } augment /me3gpp:ManagedElement { if-feature MnsAgentUnderManagedElement; uses MnsAgentSubtree; } augment /subnet3gpp:SubNetwork { if-feature MnsAgentUnderSubNetwork; uses MnsAgentSubtree; } augment /subnet3gpp:SubNetwork/mmgmtnode3gpp:ManagementNode { if-feature MnsAgentUnderManagedNode; uses MnsAgentSubtree; } } No newline at end of file Loading
yang-models/_3gpp-common-management-node.yang 0 → 100644 +90 −0 Original line number Diff line number Diff line module _3gpp-common-management-node { yang-version 1.1; namespace urn:3gpp:sa5:_3gpp-common-management-node; prefix "mmgmtnode3gpp"; import _3gpp-common-top { prefix top3gpp; } import _3gpp-common-yang-types { prefix types3gpp ; } import _3gpp-common-subnetwork { prefix subnet3gpp ; } organization "3GPP SA5"; contact "https://www.3gpp.org/DynaReport/TSG-WG--S5--officials.htm?Itemid=464"; description "Defines ManagementNode IOCs"; reference "3GPP TS 28.623 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions 3GPP TS 28.622 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) 3GPP TS 28.620 Umbrella Information Model (UIM)"; revision 2023-02-14 { reference "CR-0234"; } grouping ManagementSystem_Grp { description "Represents the ManagementSystem_ IOC."; leaf userLabel { type string; description "A user-friendly (and user assignable) name of this object."; } leaf-list managedElements { type types3gpp:DistinguishedName; config false; description "Contains a list of the DN(s) of the related subclasses of ManagedElement_ instance(s)."; } } grouping ManagementNodeGrp { uses ManagementSystem_Grp; leaf vendorName { type string; config false; } leaf userDefinedState { type string; description "An operator defined state for operator specific usage"; } leaf locationName { type string; config false; description "The physical location of this entity (e.g. an address)."; } leaf swVersion { type string; config false; } } augment /subnet3gpp:SubNetwork { list ManagementNode { description "Represents a telecommunications management system (EM) within the TMN that contains functionality for managing a number of ManagedElements (MEs). The management system communicates with the MEs directly or indirectly over one or more interfaces for the purpose of monitoring and/or controlling these MEs. This class has similar characteristics as the ManagedElement. The main difference between these two classes is that the ManagementNode has a special association to the managed elements that it is responsible for managing."; key id; uses top3gpp:Top_Grp; container attributes { uses ManagementNodeGrp; } } } } No newline at end of file
yang-models/_3gpp-common-mnsagent.yang 0 → 100644 +91 −0 Original line number Diff line number Diff line module _3gpp-common-mnsagent { yang-version 1.1; namespace urn:3gpp:sa5:_3gpp-common-mnsagent; prefix "magent3gpp"; import _3gpp-common-top { prefix top3gpp; } import _3gpp-common-yang-types { prefix types3gpp ; } import _3gpp-common-managed-element { prefix me3gpp ; } import _3gpp-common-subnetwork { prefix subnet3gpp ; } import _3gpp-common-management-node { prefix mmgmtnode3gpp ; } organization "3GPP SA5"; contact "https://www.3gpp.org/DynaReport/TSG-WG--S5--officials.htm?Itemid=464"; description "Defines MnsAgent IOCs"; reference "3GPP TS 28.623 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions 3GPP TS 28.622 Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) 3GPP TS 28.620 Umbrella Information Model (UIM)"; revision 2023-02-14 { reference "CR-0234"; } feature MnsAgentUnderManagedElement { description "MnsAgent shall be contained under ManagedElement."; } feature MnsAgentUnderSubNetwork { description "MnsAgent shall be contained under SubNetwork."; } feature MnsAgentUnderManagedNode { description "MnsAgent shall be contained under ManagedNode."; } grouping MnsAgentGrp { description "Represents the MnsAgentGrp IOC."; leaf systemDN { type types3gpp:DistinguishedName; config false; description "Distinguished Name (DN) of a IRPAgent or a MnSAgent."; } } grouping MnsAgentSubtree { list MnsAgent { description "The MnsAgent represents the MnS producers, incl. the supporting hardware and software, available for a certain management scope that is related to the object name-containing the MnS Agent. The MnSAgent can be name-contained under an IOC as follows: 1) ManagementNode; 2) SubNetwork, if the SubNetwork does not contain a ManagementNode; 3) ManagedElement, if it is the root element. In case the MnsAgent is name-contained under a ManagementNode, the management scope is the complete management scope of the ManagementNode or a subset thereof. In case the MnsAgent is name-contained under a SubNetwork, the management scope is the complete SubNetwork or a subset thereof. In case the MnsAgent is name-contained under a ManagedElement, the management scope is the complete ManagedElement or a subset thereof."; key id; uses top3gpp:Top_Grp; container attributes { uses MnsAgentGrp; } } } augment /me3gpp:ManagedElement { if-feature MnsAgentUnderManagedElement; uses MnsAgentSubtree; } augment /subnet3gpp:SubNetwork { if-feature MnsAgentUnderSubNetwork; uses MnsAgentSubtree; } augment /subnet3gpp:SubNetwork/mmgmtnode3gpp:ManagementNode { if-feature MnsAgentUnderManagedNode; uses MnsAgentSubtree; } } No newline at end of file