Changed IOCname to PreparedNotifications + smaller others

      Solution Set (SS) definitions

      3GPP TS 28.623";

  revision 2025-01-19 { reference CR-xxxx ; } 

  revision 2025-01-19 { reference CR-0493 ; } 

  revision 2024-05-18 { reference CR-0359 ; } 

  revision 2024-01-18 { reference "CR-0309 CR-0329" ; } 

  revision 2023-09-18 { reference CR-0271 ; } 

      config false;

      description "If a producer knows or suspects that it failed to prepare 

        some notifications, the types of these notifications should be listed 

        here.";

        here. 

        It can be used to detect cases where only some notificationTypes 

        are missing, e.g. only FM is unavailable, but CM notifications 

        are working.";

    }

  }

  grouping SentNotificationsGrp {

   description "Attributes of SentNotifications.";

  grouping PreparedNotificationsGrp {

   description "Attributes of PreparedNotifications.";

    leaf oldestSequenceNo {

      type uint64 ;

    }

    leaf numberOfStoredNotifications {

      type uint32 ;

      type uint64 ;

      config false;

      description "The number of notifications in the sentNotificationList.";

    }

        in the subscription. The base object instance of the scope is the 

        object instance name-containing the NtfSubscriptionControl instance. 

        When the scope attribute is absent, all objects below and including 

        the base object are scoped. The notifications related to the selected 

        managed object instances are candidates to be sent to the address 

        the base object are scoped. 

        For most notification types the scope needs to identify a set of 

        managed object instances, such as for alarm notifications. For some 

        notification types one or more attributes, attribute fields or 

        attribute elements may be specified as well, though, such as for 

        attribute value change notifications. Details on this matter are 

        specified together with the definition of the notification type.

        Note that a scope may also include objects that are not created yet, 

        for example, when a complete subtree is scoped, or when all objects 

        with a specific object class are scoped. Object instances added after 

        creating the subscription are included in the subscription as well 

        if not explicitly exluded.

        The notifications related to the selected 

        data are candidates to be sent to the address 

        specified by the notificationRecipientAddress attribute.

        The notificationTypes attribute and notificationFilter attribute 

        attributes 

        - all notifications carry the sequenceNo and the subscriptionId 

        parameters 

        - the IOC SentNotifications is supported. 

        - the IOC PreparedNotifications is supported. 

        - the notification notifyNotificationError is supported

        If notifications are prepared by the producer but their delivery to 

        the recipient is unsuccessful, the consumer should detect this based 

        on the sequenceNo and the subscriptionId and retrieve the missing 

        notifications from the SentNotifications MOI. 

        notifications from the PreparedNotifications MOI. 

        If MnS producer is not able to prepare notifications this is indicated 

        by the operationalState, availabilityStatus and missedNotificationTypes 

        attributes and the notifyNotificationError notification. The 

        notifyNotificationError notification type notifyNotificationError 

        If the MnS producer is not able to prepare notifications this 

        is indicated by the operationalState, availabilityStatus and 

        missedNotificationTypes attributes and the notifyNotificationError 

        notification. The notificationType notifyNotificationError 

        shall be automatically included in all subscriptions. 

        To fetch the information missed, the consumer should retrieve the 

        data from the relevant managed object instances (e.g. AlarmList, 

        Files etc.). The information needed is dependent on the subscription.

        Creation and deletion of NtfSubscriptionControl instances by MnS 

        consumers is optional; when not supported, the NtfSubscriptionControl 

        }

      }

      list SentNotifications {

      list PreparedNotifications {

        if-feature ReliableNotificationTransfer;

        description "This IOC represents the set of notifications prepared for 

          a specific NtfSubscriptionControl subscription. Notifications are 

        uses top3gpp:Top_Grp;

        container attributes {

          uses SentNotificationsGrp;

          uses PreparedNotificationsGrp;

        }

      }

    }