SIST EN 301 098 V1.1.1:2003

• Abstract:

  Defines the SOCs using the requirement from customer administration & routeing & digit analysis administration TMN management services.

• Status: Published
• Publication Date: 31-Oct-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Nov-2003
• Due Date: 01-Nov-2003
• Completion Date: 01-Nov-2003
• Ref Project: ETSI EN 301 098 V1.1.1 (1998-08) - Telecommunications Management Network (TMN); Scheduling function; Support object classes

SIST EN 301 098 V1.1.1:2003 is the Slovene adoption of EN 301 098 V1.1.1 from ETSI for Telecommunications Management Network (TMN) scheduling support object classes. It specifies the managed object classes and ASN.1 information model used to support generic scheduling at the Network Element (NE) / Operations System (OS) interface. The standard is aimed at TMN implementations that need scheduling based on time of day, type of day, trigger points, intervals, and multiple states.

What does SIST EN 301 098 V1.1.1:2003 specify?

SIST EN 301 098 V1.1.1:2003 specifies a generic TMN scheduling model for management applications that need time- or type-of-day-dependent control. It defines the support object classes, their attributes, and the information model used to represent scheduled behavior at the NE/OS interface.

The scope focuses on generic scheduling that can be reused by different management applications, including cases where one scheduler controls several objects or one object is controlled by several schedulers. The scope also excludes temporary override and automatic/manual fallback to a previous management schema.

Annex	What it covers
Annex A	Example of how an SMO and an SO relate in the index-based scheduling model
Annex B	Worked examples of schedulingData values, including interval and trigger cases, typeOfDay use, overlapping intervals, monthly periodicity, and mixed scheduler types

What are the key requirements of SIST EN 301 098 V1.1.1:2003?

SIST EN 301 098 V1.1.1:2003 is built around two managed object classes, multiScheduler and typeOfDayController. In practice, this means an implementation must model both the schedule itself and the calendar-like mapping used to classify dates and weekdays.

Core scheduling behavior

The scheduling information communicated to the scheduled object is independent of the action being performed, and the scheduler does not need to know that action. This matters because the same scheduling structure can support different management functions such as charging or routing.

The multiScheduler supports multiple independent schedules and can control several objects, while one Scheduled Managed Object (SMO) can be scheduled by several Scheduler Objects (SO). This makes the model suitable for shared network control rather than one-off automation.

Supported schedule types

SIST EN 301 098 V1.1.1:2003 supports both interval scheduling and trigger-point scheduling. It also allows activities with more than two states, not just simple on/off behavior. That is important where a network function needs to switch among several operating modes.

The standard also supports scheduling by type of day, such as weekend, holiday, or other special day categories. In practice, this lets operators apply different behavior on working days, holidays, or exception dates.

Time patterns and overlap handling

Daily and weekly periodicity are supported, and the model also allows limited-duration repetition. Overlapping intervals are permitted, but precedence rules are needed to decide which interval wins. The schedulingData attribute carries that logic, including optional priority when intervals overlap.

The defaultIndex is used when no defined interval applies or when the scheduler is suspended or deleted. That gives operators a deterministic fallback state.

Type-of-day mapping

The typeOfDayController groups dates and weekdays into typeOfDay values. Specific date mappings take precedence over weekday mappings, and currentTypeOfDay is derived from the translation lists. This matters when a holiday or special date should override the normal weekday classification.

Conformance requires support for the managed object classes defined in clauses 7 and 8. Those clauses are therefore the mandatory technical core of the document.

What terms does SIST EN 301 098 V1.1.1:2003 define?

• ASN.1 - Abstract Syntax Notation One, the notation used for the formal type definitions in the standard.
• NE - Network Element, the managed network node where scheduled behavior may be applied.
• OS - Operations System, the management system that interacts with the NE.
• SMO - Scheduled Managed Object, the managed object whose behavior is controlled by scheduling.
• SO - Scheduler Object, the object that carries the scheduling information.
• OC - Object Class, the managed object class concept used for multiScheduler and typeOfDayController.
• TMN - Telecommunications Management Network, the management framework addressed by the standard.

Who uses SIST EN 301 098 V1.1.1:2003?

SIST EN 301 098 V1.1.1:2003 is used by TMN designers, network management system developers, and telecom equipment vendors that implement scheduled management functions. It is also relevant to operations teams and integrators working on routing, charging, customer administration, or digit analysis administration services that need time-based behavior.

Quality managers and buyers use it to check whether a product’s management interface supports the required scheduling model and object classes.

Which standards are used with SIST EN 301 098 V1.1.1:2003?

• ITU-T Recommendation M.3100 - provides the generic network information model and the managedElement naming context.
• ITU-T Recommendation X.208 - provides the ASN.1 notation used for the formal type definitions.
• ITU-T Recommendation X.721 - provides the management information structure and the top class used by typeOfDayController.
• ITU-T Recommendation X.746 - provides the scheduling function model that multiScheduler extends and the imported schedule-related types.
• ITU-T Recommendation X.720 - provides the management information model used for the object model and set semantics.

What does the SIST EN 301 098 V1.1.1:2003 document contain?

The document contains a functional description of scheduling in clause 4, followed by an information model, object class descriptions, formal object class definitions, name bindings, and ASN.1 type definitions. Clause 6 shows the object model with multiScheduler and typeOfDayController, including inheritance and naming relations.

Clause 8 gives the formal definitions that implementers use for management interfaces, while Annex A illustrates the SMO/SO relationship for index-based scheduling. Annex B gives worked examples for interval and trigger scheduling, typeOfDay-based behavior, overlapping intervals, monthly repetition, and mixed scheduler types.

Figures show the scheduled selection entity-relationship view, naming relations, and the inheritance tree. These parts are mainly used for design and implementation of TMN management software, as well as for conformance checking against the managed object model.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Telecommunications Management Network (TMN); Scheduling function; Support object classes33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 301 098 Version 1.1.1SIST EN 301 098 V1.1.1:2003en01-november-2003SIST EN 301 098 V1.1.1:2003SLOVENSKI
STANDARD
EN 301 098 V1.1.1 (1998-08)European Standard (Telecommunications series)Telecommunications Management Network (TMN);Scheduling function;Support object classesSIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)2ReferenceDEN/TMN-00035 (a6000ico.PDF)Keywordsmanagement, network, schedulingETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/[e-mail]://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)3ContentsIntellectual Property Rights.4Foreword.41Scope.52References.53Abbreviations.54Scheduling function.64.1Functional requirements.64.2References analysis.65Conformance.66Information model.76.1Introduction to the object model.76.2 Functional model.77Information model description.87.1multiScheduler.87.2typeOfDayController.98Object class definitions.108.1Managed object class definition.108.1.1multiScheduler.108.1.2typeOfDayController.118.2Packages.118.3Attributes.118.3.1currentTypeOfDay.118.3.2dateTranslationList.118.3.3defaultIndex.118.3.4schedulingData.128.3.5typeOfDayControllerInstance.128.3.6typeOfDayControllerId.128.3.7weekDayTranslationList.128.4Name bindings.128.4.1multiScheduler-managedElement.128.4.2typeOfDayController-managedElement.128.5ASN.1 Type Definitions.13Annex A (informative):Example of SMO and SO.15Annex B (informative):Example of schedulingData values.16B.1Example 1: Shows several index values use.16B.1.1Interval solution.16B.1.2Trigger solution.17B.2Example 2: Shows typeOfDay use.17B.2.1Interval solution.17B.2.2Trigger solution.18B.3Example 3: Shows overlapping intervals, implicit repetition (months periodicity) and mixedscheduler types.19History.21SIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)4Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical CommitteeTelecommunications Management Network (TMN).National transposition datesDate of adoption of this EN:7 August 1998Date of latest announcement of this EN (doa):30 November 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 May 1999Date of withdrawal of any conflicting National Standard (dow):31 May 1999SIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)51ScopeFor some management applications, activities and/or operations have to be scheduled. This scheduling can be dependentof various factors (e.g. time of day, type of day) and it can be repeated (e.g. daily, weekly, bi-weekly). Schedulingactivities can also require more information than a simple on/off scheduling, if e.g. the scheduling can select one out ofthree or more alternatives.To manage this type of scheduling a generic solution needs to be applied. This solution shall be useful for a number ofdifferent management applications.The scope of the present document is to model the support functions for this generic solution at the NE/OS interface.Requirements for temporary override and automatic/manual fall-back to a previous management schema are outside thescope of the present document.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, subsequent revisions do apply.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]ITU-T Recommendation M.3100 (1995): "Generic network information model".[2]ITU-T Recommendation X.208 (1993): "Specification of Abstract Syntax Notation One (ASN.1)".[3]ITU-T Recommendation X.721 (1992): "Information technology - Open Systems Interconnection -Structure of management information: definition of management information".[4]ITU-T Recommendation X.746 (1995): " Information technology - Open Systems Interconnection -Systems management: scheduling function".[5]ITU-T Recommendation X.720 (1992): "Information technology - Open Systems Interconnection -Structure of management information: management information model".3AbbreviationsFor the purposes of the present document, the following abbreviations apply:ASN.1Abstract Syntax Notation OneNENetwork ElementOCObject ClassOSOperations SystemSMOScheduled Managed ObjectSOScheduler ObjectSIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)64Scheduling function4.1Functional requirementsSome management applications (e.g. charging or routing) need time/type of day dependent scheduling function. Tomanage these dependencies, the functional requirements are the following:R.1Scheduling information that is communicated to the scheduled object shall be independent of the action the scheduled object performs. The scheduler has no knowledge about this action.R.2Several independent schedulers can co-exist.R.3A scheduler can schedule several objects.R.4One SMO can be scheduled by several SO.R.5Scheduler shall be able to handle trigger points.R.6Scheduler shall be able to handle intervals.R.7Scheduler shall be able to schedule activities that have more than two states.R.8Scheduling shall be possible on base of type of day (e.g. weekend, Christmas, bank holiday).R.9At least daily and weekly periodicity shall be possible for the periodicity of trigger points and intervals.R.10It shall be possible to limit the duration of periodical repetitions.R.11Overlapping intervals shall be allowed. Precedence rules are therefore needed in order to decide which interval is active.R.12It shall be possible to retrieve from the scheduler all the objects it is scheduling.Besides these requirements, it is assumed that the relations between the scheduler, the scheduling information and thecorresponding actions to be performed are existing in the scheduled object.4.2References analysisThe scheduling function described in ITU-T Recommendation X.746 [4] provides a function that can schedule a numberof activities within multiple managed objects by a single scheduler and is able to specify the time duration that theschedule is active.This scheduler covers only a part of the functional requirement given in the subclause 4.1 and it is designed for startingand stopping of activities.It could be possible to use it by straining the modelling to the maximum extent. It is not used for the following reasons:· it is not possible to define, for every point in time, different activities for each SMO;· the scheduler schedules activities between two states;· the type of day dependency is not covered;· overlapping intervals are not supported.5ConformanceIn order to claim conformance to this specification, a system needs to support the management functions for all managedobject classes defined in clauses 7 and 8 of the present document. Therefore the clauses 7 and 8 form the mandatory partof the present document.SIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)76Information model6.1Introduction to the object modelThe scheduling function is realised by two entities, the multiScheduler and the typeOfDayController.The OC multiScheduler extends the functionality of the interval scheduling and aperiodic scheduling as described inITU-T Recommendation X.746 [4]. For information, refer to model description in clause 7 of that document.For interval scheduling, the ITU-T scheduler allows the transition of one activity in a SMO between the active andinactive state. The multiScheduler allows the transition of an activity between several (two or more) states. Each suchstate is associated with an index value. The OC multiScheduler also allows overlapping intervals.For aperiodic scheduling, the OC multiScheduler allows the triggering of (possibly different) activities depending on anindex value. Aperiodic scheduling in the OC multiScheduler can also be used for operation scheduling, as described inITU-T Recommendation X.746 [4].For both types of scheduling, the possibility exists to schedule activities depending on the type of day, e.g. holidays,weekdays.The OC typeOfDayController is used to group days into categories according to their type, e.g. 1st January can beclassified as specialDay1.6.2Functional model0,1Npoints totypeOfDayControllermultiSchedulerpoints toSMON0, 110, MFigure 1: Scheduled selection E-R diagramITU-T Rec. M.3100 [1]:managedElementtypeOfDayControllermultiSchedulernamesFigure 2: Naming RelationsSIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)8multiSchedulertypeOfDayController"ITU-T Rec.X.746 [4]": scheduler"ITU-T Rec.X.721 [3]": topFigure 3: Inheritance tree7Information model descriptionThis clause describes the object classes of the information model. For OC's descriptions the following table style is used.Table 1: Generic OC's descriptionObject Class: "Object class name"AttributesM/CValue SetOperationActionsM/CNotificationsM/CThe column M/C indicates whether the information presented by the attributes/actions/notifications is mandatory(M) orconditional(C).The column "Value Set" indicates whether the attribute is single-valued or set-valued (see ITU-T RecommendationX.720 [5], subclause 5.1.2.2).The column "Operation" indicates the operations that are possible on the attribute.7.1multiSchedulerThe OC multiScheduler is inherited from ITU-T Recommendation X.746 [4] scheduler. It provides the ability to controlactivities for which more information is required then a simple on/off scheduling. This OC multiScheduler allows thedefinition of multiple independent schedules, each of which is associated with an activity. These activities are associatedto index values or are triggered by operations. In the case of index values, the association between a particular indexvalue and an activity is defined within the SMO.SIST EN 301 098 V1.1.1:2003

ETSIEN 301 098 V1.1.1 (1998-08)9Table 2: multiScheduler descriptionObject Class: multiSchedulerAttributesM/CValue SetOperationschedulingDataMSetGET-REPLACEADD-REMOVEdefaultIndexCSingleGET-REPLACEREPLACE-WITH-DEFAULTtypeOfDayControllerInstanceCSingleGET-REPLACENotifications"ITU-T Recommendation X.746 [4]":operationNotificationPackageCThe following attributes describe the OC multiScheduler:-schedulingData;This attribute contains a set of schedules and related data controlling the activities;-defaultIndex;This attribute gives the index that is applicable when none of the intervals specified in the attributeschedulingData is valid or when the scheduler is suspended or deleted;-typeOfDayControllerInstance;This attribute identifies the instance of OC typeOfDayController that is relevant for this instance of OCmultiScheduler.7.2typeOfDayControllerThe OC typeOfDayController provides management information needed to map a specific date or a weekday to a typeof day and contains the currently valid typeOfDay.Table 3: typeOfDayControllerObject Class: typeOfDayControllerAttributesM/CValue SetOperationtypeOfDayControllerIdMSingleGETcurrentTypeOfDayMSingleGETdateTranslationListMSetGET-REPLACEREPLACE-WITH-DEFAULTADD-REMOVEweekDayTranslationListMSetGET-REPLACEREPLACE-WITH-DEFAULTNotific
...