ATIS 0300250-2011 Operations Administration Management & Provisioning - Extension to Generic Network Model for Interfaces Between Operations Systems and Network Elements to Support.pdf

1、 ATIS-0300250 ATIS Standard on - OPERATIONS, ADMINISTRATION, MANAGEMENT in the case of Plain Old Telephone Service (POTS) and ISDN, this equipment is connected to the customers telephone equipment via the distribution plant facilities. Calls from the network to this customer are routed to the direct

2、ory number (which is logically connected to the office equipment). Calls initiated by the customer (from this point of access) are originated from the point of access or office equipment domain. A relationship exists between the point of access and the directory number. Thus, there should be a refer

3、ence (pointer) from the directory number to the service view of the point of access and vice versa. 5.2 Many directory number object instances can be associated with one point of access to the switch. For example, in teen services, members of a family are assigned different directory numbers and rin

4、ging codes but share the same office equipment. Another example is an ISDN Basic Rate interface in which several terminals, each supporting several directory numbers, may share the same office equipment. Also, a further example is a POTS party line, where multiple customers share the same point of a

5、ccess but have different directory numbers. This modifies requirement 5.1 in that the point of access should have a reference (pointer) to each of the related directory numbers. 5.3 In some cases, many points of access can be associated with one directory number. This is applicable to Electronic Key

6、 Telephone Service (EKTS) in which a given directory number may appear on many different ISDN Basic Rate access points. Thus, this modifies requirement 5.1 in that the directory number should have a reference (pointer) to each of the related point of access. 5.4 Different points of access may be abl

7、e to support different types of services and options. The point of access should have a reference to a profile that contains information that can be used to determine whether the point of access is able to support the services that the subscriber requires. 5.5 Moreover, for directory numbers associa

8、ted with a subscriber group, there may be options that are available to a whole group. Therefore, it would be useful to be able to also have a service profile associated with groups instead of only with a single directory number. This would mean that adding options to a group would provision the ser

9、vice options for all the members of the group at once. Then, for those members who dont have certain features in their personal profile (the profile associated with the directory number), the presence of a feature in the groups profile would make it available to them. 5.6 Support for high level mana

10、gement operations such as establishing new services, terminating services, configuring and rearranging subscriber groups is required. 5.7 Support for defining and modifying “service packages” that completely defines a given service, including its associated service features and options is required.

11、5.8 For ISDN primary rate service, multiple facilities should be supported with or without D-Channel backup. There is also an objective for the ability to assign B-Channels to an additional DS1 facility even if all of the DS0 slots associated with other DS1 facilities on the interface have yet to be

12、 allocated as B-Channel or a D-Channel. ATIS-0300250 6 5.9 Call-by-Call Service Selection ISDN Call-by-Call Service Selection is a method of providing services on an ISDN PRI as an alternative to providing services on a dedicated interface, a dedicated B-Channel, or a dedicated group of B-Channels.

13、It provides the ability to limit the number of calls for each service type that is carried over the NT2, the service types being Foreign Exchange service, INWATS service, OUTWATS service, Tie Trunk service, and Circuit-mode Public Network service. 5.10 Service Dedicated B-Channels When Call-by-Call

14、Service Selection is not chosen by the customer, an interface, a B-Channel, or a group of B-Channels may be dedicated to a service. It is also possible that a customer may choose to use both Call-by-Call Service Selection and dedicated B-Channels over the same interface. 5.11 Backup D-Channel When a

15、 Primary Rate Interface (PRI) consists of more than one DS1 facility, the failure of the controlling D-Channel could result in the loss of a large number of B-Channels. The D-Channel back-up capability provides a mechanism to switch over to a standby D-Channel when the active D-Channel fails. For ma

16、ximum reliability, the active D-Channel and the backup D-Channel are on different DS1 facilities. 5.12 A customer group or subgroup can contain zero, one, or more members. 5.13 A line without any association to a customer group is considered to be an ordinary Business or Residence service. 5.14 A cu

17、stomer group can be deleted only if it has no members. 5.15 A member of a customer group can be a Directory Number/ISDN Bearer Service (Directory Number/Bearer Service) pair or an Analog Circuit Switch Service. A Directory Number can be member of multiple customer groups, one for each of the Bearer

18、Services with which the Directory Number has a relationship. 5.16 A given subscriber can have multiple customer groups in a given Switching Network Element, each with its own set of members, dialing plans, and group parameters. 5.17 For operational reasons, it is essential that the relationship of c

19、ustomer groups and their members be easy and efficient to rearrange. It should therefore be possible for a customer group member to change from one customer group to another without having to delete and re-create the member. 5.18 To support the use of the SPV and SPM service on ISDN Primary Rate int

20、erfaces, it is necessary to provide the ability to group different service characteristics together. Customer Profile is used to achieve this grouping. This grouping includes objects that are related by the primary rate service configuration and may span multiple D channel to B channel signaling rel

21、ationships. The Customer Profile defines the extent of control of the SPV/SPM password. 6 Object model definitions 6.1 Object classes inheritance Some of the object classes in clause 6 are defined as “subclasses of another object”. A subclass is said to inherit the properties (attributes, events, ac

22、tions, and behaviours) of the superclass from which it is refined. In other words, the subclass is an extension of the superclass in the sense that it has all properties of the superclass plus some additional ones. The concept of inheritance is fundamental to the creation of a generic model. Generic

23、 objects (such as accessPortProfile) can be subclassed to define new objects (such as accessPortProfileAnalog) based upon a configuration management service provisioning modelling concept. Subclassing can also be used to cover specific requirements, such as service-specific needs (e.g., POTS, ISDN)

24、or equipment-specific needs (e.g., Analog Access Port). ATIS-0300250 7 The succession of inheritance relationships (from generic to specific) can be represented by an inheritance hierarchy. Higher levels in this hierarchy contain more generic object classes that are refined to more specific ones loc

25、ated at lower levels of the hierarchy. The inheritance hierarchy of this standard is illustrated in Figure 1. The lines represent the subclassing relationships and the vertices represent the managed objects defined in this standard. The object class “Top” is at the apex of the classification hierarc

26、hy. The “Object Class” attribute is used to indicate the class of the object. Top is the superclass of all other objects, therefore all managed objects contain the attribute “Object Class”. See also Figures 2 through 8. The reader of this standard is encouraged to review Annex A which provides one p

27、ossible application of the model described below. Annexes in this standard provide relationships among managed objects defined in this model. Figure 1 - Model fragments Figure 2 - Common service configuration and analog fragments ATIS-0300250 8 Figure 3 - General ISDN fragment Figure 4 - EKTS fragme

28、nt ATIS-0300250 9 Figure 5 - ISDN Circuit Switched Services Fragment ATIS-0300250 10 TopServiceManagerQ.824.0ServiceManagerAnalogServiceManagerRetrieveServiceQ.824.1ServicePackageQ.824.0ServiceManagerISDNQ.824.1Figure 6 -Support fragment Figure 7 - Supplementary services fragment ATIS-0300250 11 Fig

29、ure 8 - Resource fragment Conventions used in this standard: Throughout this standard, the following conventions are used: The name of an attribute that is intended to point to a specific object class is composed of the name of that object class followed by the string “Ptr”; If an attribute value is

30、 intended to identify different object classes, a descriptive name is given to that attribute and a description is provided in the attribute behaviour; The naming attribute for a managed object is composed of the name of the object class followed by the string “Id”; and The use of “NA” as part of an

31、 object class name is intended to identify this object class as a North American extention to the ITU object class. ATIS-0300250 12 6.2 Referenced objects from ITU-Q.824 series standards Table 1 - Object classes from ITU-T Recommendation Q.824.0 Managed objects Access Channel Access Port Access Port

32、 Profile Administered Circuit Endpoint Subgroup Bearer Service CataloguedSupplementaryService Customer Profile Directory Number Directory Number E164 Directory Number X121 Layer Entity Routing Block Customized Resource Supplementary Service Service Dependent ServiceManager ServicePackage Corrections

33、 to ITU-T Recommendation Q.824.0: When using the managed object classes from Table 1 incorporate the following corrections: Section 3.1, AccessChannel, the CCITT X.721 alarmStatus attribute should be CCITT M.3100 alarmStatus; Section 3.5, BearerServicePkg, add objectCreation and objectDeletion notif

34、ications from ITU-T Recommendation X.721; Section 3.6, CustomerProfile, add objectCreation, objectDeletion, and attributeValueChange notifications from ITU-T Recommendation X.721; Section 6.7, NumberOfBChannelPkg, the numberOfBChannel attribute must include GET-REPLACE and default value -1; Section

35、4.4, CustomizedResource, delete attribute numberOfBChannels. This is not required in the super-class. Note its use in EKTS object defined in this standard; When using the customizedResourcePtrList attribute, add to the attribute behaviour in Section 7.2.0 “.instances of Customized Resources object c

36、lass and/or its subclasses.”; When using the OfficeEquipmentPkg, delete attribute OfficeEquipmentList.and replace with attribute officeEquipment; and When using InterceptTreatmentOriginTypes change the name of the last identifier to “softDTEEmergencyServiceOrBusinessOffice (4).” ATIS-0300250 13 Tabl

37、e 2 - Object classes from ITU-T Recommendation Q.824.1 Managed objects Access Channel B-Channel Access Channel D-Channel Access Port ISDN Basic Rate Access Port ISDN Primary Rate Access Port Profile ISDN Access Port Profile ISDN Basic Rate Access Port Profile ISDN Primary Rate CallingNumberScreening

38、 Bearer Service For 1536 kbps Data Bearer Service For 1920 kbps Data Bearer Service For 384 kbps Data Bearer Service For Multiple Rate Data Catalogued Layer Entity DSS1 Catalogued Layer Entity LAPD Circuit 3.1kHz Circuit MultiUse Circuit Speech Circuit Unrestricted Digital Data Circuit Unrestricted

39、Digital Data Rate Adapted From 56kbps Layer Entity LAPD Service Manager ISDN Service Manager Retrieve Service Terminal Configuration Terminal Service Profile Corrections to ITU-T Recommendation Q.824.1 When using the managed object classes from table 2 incorporate the following corrections: Section

40、6.1.7, delete the first sentence in the behaviour after the bullets; Change syntax of dChannelT3XX := REAL (10,10,-1 . 4200,10,-1); Replace behaviour for attribute directoryNumberAppearanceIdentifierList with “This attribute is used to associate a directoryNumber with a particular key on a terminal,

41、 along with the default bearerService for that key. This information is used to support the service profile verification (M.3660) feature, including the ability to download key assignments to a terminal”; Replace the following ASN.1 production in Q.824-1 with: ServicePackageISDNDescription SERVICE-P

42、ACKAGE-SPECIFIC-DATA: PossibleServicePackages:= SEQUENCE servicePackageName ObjectInstance, ATIS-0300250 14 accessPortName ObjectInstance, serviceDescription SET OF SEQUENCE templateDirectoryNumberName ObjectInstance, directoryNumberName ObjectInstance, serviceRequestInfo SET OF SERVICE-PACKAGE-SPEC

43、IFIC-DATA CHARACTERIZED BY customerGroupPkg PACKAGE BEHAVIOUR customerGroupBehaviour; ATTRIBUTES customerGroupId GET-REPLACE, description GET-REPLACE; REGISTERED AS caObjectClass 1; customerGroupBehaviour BEHAVIOUR DEFINED AS “The customerGroup managed object represents a grouping of subscriber line

44、s to provide origination and termination services and features in common to the members of the group. A customer group may be either a business or non-business grouping of subscriber services. It is not necessary for all members of a customer group to belong to the same organizational entity.”; 6.3.

45、2 Directory number profile directoryNumberProfile MANAGED OBJECT CLASS ATIS-0300250 15 DERIVED FROM “ITU-T Rec. Q.824.0”: customerProfile; CHARACTERIZED BY directoryNumberProfilePkg PACKAGE BEHAVIOUR directoryNumberProfileBehaviour; ATTRIBUTES “Rec. X.721 | ISO/IEC 10165-2 : 1992“: administrativeSta

46、te GET-REPLACE; CONDITIONAL PACKAGES numberOfBChannelsPkg PACKAGE BEHAVIOUR numberOfBChannnelsPkgBehaviour; ATTRIBUTES “ITU-T Rec. Q.824.0“: numberOfBChannels REPLACE-WITH-DEFAULT DEFAULT VALUE GNMSP.minusOne GET-REPLACE; REGISTERED AS caOptionalPkg 1; PRESENT IF “used in ISDN service.”; REGISTERED

47、AS caObjectClass 2; directoryNumberProfileBehaviour BEHAVIOUR DEFINED AS “The Directory Number Profile object class is a subclass of Customer Profile managed object and represents the characteristics of the Directory Number assigned to individual subscribers, independent of the access type and beare

48、r service. Each instance of the Directory Number Profile object class inherits a pointing attribute to the Directory Number object class instance that represents the unique Directory Number assigned for this object. Therefore, the directoryNumberPtrList attribute is restricted to a list of one. When

49、 the accessPortProfilePtrList attribute points to an ISDN Basic Rate access port profile, the Directory Number attribute value of the Directory Number object pointed to from this object is added to the list of Calling Party Valid Directory Number attribute values in the associated Access Port ISDN Basic Rate object.”; numberOfBChannnelsPkgBehaviour BEHAVIOUR DEFINED AS “This package is applicable for ISDN services. The numberOfBChannels attribute limits the B-Channel resources that the directoryNumberProfile can us