Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
A Comprehensive Guide to the Scheduling Function in OSI Systems Management: CAN/CSA-ISO/IEC 10164-15-04 (ISO/IEC 10164-15)
Technical Requirements, Implementation Insights, and Compliance Framework for Network Management Automation Based on International Standards
1. Scope and Purpose
CAN/CSA-ISO/IEC 10164-15-04, which is the Canadian national adoption of the international standard ISO/IEC 10164-15:2002, defines the Scheduling Function (SCHED) for Open Systems Interconnection (OSI) Systems Management. As an integral part of the comprehensive OSI management framework, this standard provides a standardized model, service definition, and protocol specification that allows management applications to plan and automate management operations without continuous human intervention.
The primary goal of this standard is to enable automated network and systems administration. Typical use cases include scheduling automated backups, regulating log file archiving, activating performance monitoring agents during peak business hours, and enforcing security policy updates during specific maintenance windows. The standard defines a robust framework that allows a managing system to specify when operations should be performed, for how long they should remain active, and how often they should recur.
It achieves this by defining three key technical elements: an abstract model for the scheduling service, a robust set of Managed Object (MO) definitions using the Guidelines for the Definition of Managed Objects (GDMO), and the protocol exchanges (Common Management Information Service/Protocol operations) necessary to create, manage, and execute these schedules within a managed network element.
2. Core Technical Requirements and Service Definitions
The Scheduling Function is built upon a highly structured object-oriented model defined in GDMO and encoded via Abstract Syntax Notation One (ASN.1). The standard specifies a set of Managed Objects, packages, attributes, actions, and notifications that must be implemented to claim conformance to the function.
2.1 The Scheduling Service Model
The architecture centers around the scheduler Managed Object, which acts as the factory and management entity for individual schedule Managed Objects. Each schedule MO defines the specific time constraints for a management operation. The model distinguishes between single absolute schedules, recurring schedules (based on intervals or a calendar), and duration-bound schedules.
Key attributes defined in the ASN.1 module include schedulerTimeList (for specifying absolute start times), schedulerRecurringInterval (for periodic execution), and schedulerDuration (for limiting the active lifecycle of a schedule). The standard specifies specific actions for managing the schedule lifecycle, such as activateSchedule, deactivateSchedule, suspendSchedule, and resumeSchedule, which provide fine-grained control over a scheduled task.
2.2 Summary of Key Managed Objects
The following table summarizes the core Managed Objects, their mandatory and conditional packages, and their primary functional roles as defined by the standard.
| Managed Object (MO) | Mandatory Package | Key Conditional Packages | Key Actions / Notifications | Functional Use Case |
|---|---|---|---|---|
| Scheduler | SchedulerPackage | SchedulingManagerPackage | scheduleOperation, scheduleCreation | Manages the overall scheduling subsystem and creates Schedule MOs |
| Schedule | SchedulePackage | RecurringSchedulePackage, DurationSchedulePackage | activateSchedule, deactivateSchedule, suspendSchedule | Defines a specific task to be executed at a defined time |
| Calendar | CalendarPackage | WeekDayCalendarPackage, HolidayCalendarPackage | Structural State Attributes | Defines complex recurrence patterns and exceptions |
| Trigger | TriggerPackage | NotificationTriggerPackage, ActionTriggerPackage | schedulingActionError, schedulingEntryOverflow | Initiates the specific management operation or notification |
3. Implementation Highlights and Best Practices
Implementing the Scheduling Function requires careful attention to state management and time synchronization within the managed system. The following highlights address critical aspects of deployment.
State Management: Schedule MOs follow a strict state transition model. A schedule can be in an active, inactive, suspended, or finished state. Understanding these transitions is critical for correct operation. For example, a recurring schedule reaches the finished state only when explicitly deactivated or when its defined duration expires.
Time Synchronization: The accuracy of the scheduling function is entirely dependent on the accuracy of the managed object’s system clock. Implementers must ensure robust time synchronization, typically via the Network Time Protocol (NTP), to guarantee that scheduled actions trigger precisely at the intended time.
Integration with Other Functions: The SCHED function is designed to work in concert with other OSI management functions. Scheduled actions can directly trigger event reports (ISO/IEC 10164-5), modify log records (ISO/IEC 10164-12), or enforce security alarms (ISO/IEC 10164-7).
Tip: When configuring recurring schedules, leverage the Calendar MO to pre-define standard maintenance windows and holiday exclusions. This centralizes scheduling policy and prevents critical tasks from triggering on non-operational days.
Warning: Granular scheduling at sub-second intervals or managing thousands of schedule MOs on a single agent can lead to CMIP processing bottlenecks and scheduling queue overflows. This triggers
schedulingEntryOverflow notifications, degrading the reliability of the scheduling service.Best Practice: Use the
suspendSchedule and resumeSchedule actions for operational flexibility instead of deleting and recreating schedule MOs. This preserves historical state data and significantly reduces CMIP network traffic during temporary maintenance periods.Critical Note: Implementers must strictly adhere to the specific ASN.1 definitions for time values (GeneralizedTime or UTC Time) as defined in the ASN.1 module of the standard. Using an incorrect time encoding or format is the most common root cause of conformance failure and CMIP parsing errors during interoperability testing.
4. Compliance Notes and Adoption Framework
CAN/CSA-ISO/IEC 10164-15-04 is the identical national adoption of the international standard ISO/IEC 10164-15:2002 by the Canadian Standards Association (CSA). Adopting this standard ensures that Canadian telecommunications and network management solutions achieve full global interoperability with OSI management frameworks.
Conformance Requirements: To claim conformance to the Scheduling Function, an implementation must satisfy both Static and Dynamic conformance requirements:
– Static Conformance: The implementation must claim support for the mandatory packages and specify which conditional packages are implemented.
– Dynamic Conformance: The implementation must correctly execute the management operations and emit the appropriate notifications as defined in the GDMO templates.
Testing: Conformance testing typically involves a protocol analyzer or test harness that validates the CMIP Protocol Data Units (PDUs) against the exact GDMO and ASN.1 modules defined in the standard.
Q: How does CAN/CSA-ISO/IEC 10164-15-04 relate to similar standards in the ITU-T?
A: This standard is technically identical to ITU-T Recommendation X.737. The two bodies (ISO/IEC and ITU-T) jointly developed the text to ensure a single, unified international standard for the Scheduling Function within the OSI management framework.
A: This standard is technically identical to ITU-T Recommendation X.737. The two bodies (ISO/IEC and ITU-T) jointly developed the text to ensure a single, unified international standard for the Scheduling Function within the OSI management framework.
Q: What is the significance of the “04” in the standard number?
A: The “04” identifies this as the 2004 edition of the Canadian adoption. The technical content is strictly identical to the 2002 edition of the international standard ISO/IEC 10164-15. This represents the core definitive text for the OSI Scheduling Function.
A: The “04” identifies this as the 2004 edition of the Canadian adoption. The technical content is strictly identical to the 2002 edition of the international standard ISO/IEC 10164-15. This represents the core definitive text for the OSI Scheduling Function.
Q: What happens if a scheduled action fails to execute correctly?
A: The standard defines the
A: The standard defines the
schedulingEntryActionError notification to report failures. The schedule MO can be configured to either continue retrying the action, suspend itself, or fully deactivate, depending on the specific policy implemented by the managing system.Q: Is this standard relevant outside of pure CMIP/GDMO environments?
A: Yes. While the standard is firmly rooted in the OSI management framework, the abstract model it provides (time-based triggers, calendar objects, recurring interval logic) has heavily influenced design patterns in modern management systems, providing a foundational understanding of management automation logic.
A: Yes. While the standard is firmly rooted in the OSI management framework, the abstract model it provides (time-based triggers, calendar objects, recurring interval logic) has heavily influenced design patterns in modern management systems, providing a foundational understanding of management automation logic.