1 module yes-o1-notify-pnf-registration {
3 namespace "urn:o-ran-sc:params:xml:ns:yang:yes-o1-notify-pnf-registration";
6 import yang-based-event-stream {
9 "wiki.opnfv.org/display/ves/VES+goes+YES";
14 "wiki.opnfv.org/display/ves/VES+goes+YES";
16 import ietf-inet-types {
19 "RFC 6991: YANG data types for Internet addresses and related
22 import ietf-yang-types {
25 "RFC 6991: Common YANG Data Types.";
29 "O-RAN Software Community";
33 "This module is inspired by VES 7.1.1 but uses YANG concepts and types to
34 describe the exchanged data format.
35 The module yes-o1-notify-pnf-registration is only required, if the
36 network function does not support NETCONF CALL HOME but RESTCONF
39 Due to the different hardware definitions by 3GPP and by IETF two
40 additional and complimentary yang models are available. It is recommended
41 that the NETCONF-Server offers an implementation at least of one of the
42 following additional yang modules:
44 - yes-o1-notify-pnf-registration-3gpp-hardware
45 - yes-o1-notify-pnf-registration-ietf-hardware
47 Copyright 2022 highstreet technologies GmbH and others.
49 Licensed under the Apache License, Version 2.0 (the 'License');
50 you may not use this file except in compliance with the License.
51 You may obtain a copy of the License at
53 http://www.apache.org/licenses/LICENSE-2.0
55 Unless required by applicable law or agreed to in writing, software
56 distributed under the License is distributed on an 'AS IS' BASIS,
57 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
58 See the License for the specific language governing permissions and
59 limitations under the License.";
64 including feedback from WG4 about the usage of RFC 8348.";
66 "ONAP SDN-R: wiki.onap.org/display/DW/SDN-R
67 VES: wiki.opnfv.org/display/ves/VES+Home
68 docs.onap.org/en/frankfurt/submodules/dcaegen2.git/docs/sections/services/ves-http
69 YES: wiki.opnfv.org/display/ves/VES+goes+YES
70 O-RAN Operations and Maintenance Interface Specification (O-RAN.WG10.O1-Interface.0-v07.00)
71 section 2.7.2.4 Operations and Notifications
72 RFC 8348: A YANG Data Model for Hardware Management";
79 identity o1-notify-pnf-registration {
82 "Indicates, that the event body contains o1-notify-nf-registration
83 asynchronous message context.";
90 grouping o1-notify-pnf-registration-grp {
97 "The name of the object class describing a PNF in the context of
100 leaf object-instance {
104 "Reference to the object representing the PNF.";
106 leaf notification-identifier {
110 "An notification identifier of this event as defined in ITU-T Rec. X.733.";
112 "ITU-T Rec. X.733 - section 8.1.2.8.";
114 leaf notification-type {
118 "Only the domain identity 'o1-notify-pnf-registration' is allowed.";
121 type yang:date-and-time;
124 "The earliest time aka epoch time associated with the event from
127 leaf system-distinguished-name {
131 "Distinguished Name of the management service provider of the notification";
133 leaf o1-specification-version {
139 "The version of the O1 Specification defining the format of this PNF registration notification";
142 case vendor-private-enterprise-number {
146 "Network function vendor IANA private enterprise number.";
150 "The network function vendor can be identified by its name or by its
151 IANA private enterprise number (PEN)";
153 "IANA Private Enterprise Numbers
154 http://www.iana.org/assignments/enterprise-numbers/enterprise-numbers";
160 "The m-plane fully qualified domain name (host) or IP address to
161 be used by the manager to contact the PNF.";
163 "O-RAN Operations and Maintenance Interface Specification (O-RAN.WG10.O1-Interface.0-v07.00)
164 section 2.7.2.4 Operations and Notifications - oamV4IpAddress and oamV6IpAddress";
167 type inet:port-number;
170 "The port number the PNF listens for OAM commands..";
177 "The general type of hardware.";
179 "3GPP TS 28.632 vendorUnitFamilyType";
186 "Vendor name for the network function";
188 "3GPP TS 28.632 vendorUnitTypeNumber";
190 leaf restart-reason {
195 "The reason the network function restarted.";
198 "An object class containing o1-notify-pnf-registration specific parameters.";
202 * Augmentation of YES
205 augment "/yes:event-history/yes:event" {
206 when "derived-from-or-self(/yes:event-history/yes:event/yes:header/yes:domain, 'ypr:o1-notify-pnf-registration')" {
208 "The event header must indicate 'o1-notify-pnf-registration'.";
210 if-feature "yes:event-history";
211 container o1-notify-pnf-registration {
212 uses o1-notify-pnf-registration-grp;
214 "A single object for specific parameters, used for the registration of
215 physical network functions (PNF).";
218 "Adds to YES the specifics of o1-notify-pnf-registration notifications.";
221 augment "/yes:yang-based-event-stream/yes:event" {
222 when "derived-from-or-self(/yes:yang-based-event-stream/yes:event/yes:header/yes:domain, 'ypr:o1-notify-pnf-registration')" {
224 "The event header must indicate 'o1-notify-pnf-registration'.";
226 container o1-notify-pnf-registration {
227 uses o1-notify-pnf-registration-grp;
229 "A single object for specific parameters, used for the registration of
230 physical network functions (PNF).";
233 "Adds to YES the specifics of o1-notify-pnf-registration notifications.";