SIST I-ETS 300 291 E1:2003

• Abstract:

  Will contain the functional definitions and managed object definitions for customer administration aspects of ISDN, POTS and digital lines including PABX and CENTREX bearing in mind that the model must be extendable for mobile, ATM and UPT

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI I-ETS 300 291 ed.1 (1995-01) - Network Aspects (NA); Functional specification of Customer Administration (CA) on the Operations System/Network Element (OS/NE) interface

SIST I-ETS 300 291 E1:2003 is the Slovenian adoption of ETSI I-ETS 300 291 Edition 1. It specifies the Customer Administration (CA) information model on the Operations System/Network Element (OS/NE) interface for Public Switched Telephone Network (PSTN) and public Integrated Services Digital Network (ISDN) service provisioning and service configuration. The model is intended for network management engineers, operators, and equipment suppliers that need a common way to represent subscriber lines, numbers, profiles and services.

What does SIST I-ETS 300 291 E1:2003 specify?

SIST I-ETS 300 291 E1:2003 specifies the management aspects of Customer Administration (CA) on the OS/NE interface. It focuses on semi-permanent subscriber data for service provisioning and service configuration, not on call processing.

The scope includes centrex subscribers and Private Automatic Branch Exchanges (PABX) treated as terminal equipment. It does not cover PABX extensions. The model is designed to be extendible to mobile, Asynchronous Transfer Mode (ATM), cordless and Universal Personal Telecommunications (UPT) subscribers.

The document is organized as follows:

• Clause 1 states the scope.
• Clause 2 lists the normative references used by the model.
• Clause 3 gives the core definitions and abbreviations.
• Clause 4 shows information model diagrams.
• Clause 5 describes the information model informally.
• Clause 6 gives the formal managed object definitions and the ASN.1 module.
• Annex A gives name translations used in clauses 5 and 6.
• Annex B lists supplementary service candidates for standardization.
• Annex C gives examples of how to apply the model.

Annex	What it covers
Annex A	Reference list for used names, with translation tables for object classes and attributes
Annex B	Candidates for standardization, including supplementary services, attributes, behaviours and an ASN.1 module
Annex C	Examples of use of the customer administration model

What are the key requirements of SIST I-ETS 300 291 E1:2003?

SIST I-ETS 300 291 E1:2003 defines a managed-object model for customer administration on the OS/NE interface. In practice, this means the standard tells implementers how to structure subscriber data so that an operations system and a network element can share the same view of lines, numbers, profiles and services.

The model is built around a small set of core object classes

Clause 5 describes the main object classes used in the model: Managed Element, access port, access channel, directory number, customer profile, customized resources, customized service and group dial plan. These objects are the building blocks for modelling analogue, digital and ISDN subscribers, including Centrex and PABX use cases.

This matters because an operator or supplier can represent a customer subscription as linked managed objects rather than as ad hoc database fields. That makes provisioning, changes and fault analysis more consistent across systems.

The diagrams show how the objects relate to each other

Clause 4 presents entity-relationship models, inheritance hierarchies and naming hierarchies. The document says these diagrams are for clarification, while the formal GDMO templates and ASN.1 type definitions are the relevant implementation references.

That means implementers should use the diagrams to understand the structure, but rely on Clause 6 for the actual machine-readable definitions. The hierarchy also shows how the model is intended to be extended by subclassing.

The model separates common attributes from object-specific ones

Clause 5.2 identifies generic attributes used across the model:

• relative distinguished name
• operational state
• administrative state
• owner object classes
• association attributes

In practice, these attributes let systems name objects, show whether they are active or locked, and express how customers, ports, numbers and services are linked. That is important when an administrator needs to trace which service belongs to which line or number.

The standard uses standard management notifications

Clause 5.3 identifies no specific CA actions. Clause 5.4 says the model uses generic notifications for object creation, object deletion, attribute value change, state change and relationship change.

This is important for operations systems because it means CA events can be handled with the standard management event types already used in telecommunications management. Systems can therefore react to object lifecycle and relationship changes without inventing special event formats.

Clause 6 gives the formal definitions needed for implementation

Clause 6 defines the managed object classes, packages, behaviours, attributes, name bindings and the ASN.1 module. The formal definitions cover the service and access objects needed for analogue access, basic access, primary rate access, digital access, directory numbers, Centrex profiles, customized services, telephony, Teletex, Telefax group 4, terminal portability, three party and Multiple Subscriber Number (MSN).

For implementers, this is the part that turns the conceptual model into something that can be coded, tested and exchanged. It also defines how services such as CLIP, CLIR, Call Forwarding and Call Waiting are represented as managed objects.

The attribute set includes service parameters that operators must provision

Clause 6.4 defines attributes such as access channel and rate, acting role, advice of charge activation, call forwarding notifications, channel rate, channel type, line characteristics, line signalling, line test capability, maximum number of information channels, maximum number of total calls, maximum number of waiting calls, closed user group parameters and translation table.

These are the kinds of values an operator must enter when turning a customer request into a working line configuration. They also show which technical constraints are part of the customer record, such as signalling type, channel limits and closed user group settings.

Name bindings define where objects sit in the management tree

Clause 6.5 defines name bindings for access channels, access ports, customer profiles, Centrex profiles, customized resources, customized service, E.164 directory numbers and group dial plan. That tells the system how objects are named and contained under the Managed Element.

This matters because naming and containment determine how an OS locates a specific subscriber object, how it groups related objects, and how it builds valid instances of the model.

Annex C shows how the model is used in real subscription cases

Annex C gives four worked examples, from a simple single-line configuration to multi-line cases with MSN and customised resources. These examples show when a Customized Resources object is needed and how services are associated with directory numbers and access ports.

For a buyer or integrator, Annex C is useful because it shows the practical shape of the object model in realistic provisioning scenarios.

What terms does SIST I-ETS 300 291 E1:2003 define?

SIST I-ETS 300 291 E1:2003 defines several core terms that describe the management model.

• Customer Administration (CA) - the function of managing customer service provisioning information on a switch.
• Operations System (OS) - the management system that controls and configures network elements.
• Network Element (NE) - the managed network equipment that holds the customer service data.
• access port - the logical termination point of the customer service access within the switch.
• access channel - the logical termination of an ISDN B-channel or D-channel, or an individual channel of a digital access port.
• customer profile - the object class that relates the resources used by a customer and contains the services provisioned for that customer.
• customized resources - the object class that links the subset of a customer's services and resources that do not apply to every access port, access channel or Directory Number (DN).
• centrex - the functional equivalent of a Private Branch Exchange (PBX) realized in a single local exchange.

Who uses SIST I-ETS 300 291 E1:2003?

SIST I-ETS 300 291 E1:2003 is used by people who design, implement and operate telecommunications management systems. Network management and Telecommunications Management Network (TMN) engineers use it to model subscriber administration data at the OS/NE interface.

Switch and operations-system suppliers use it when defining managed objects, packages, behaviours and ASN.1 types for subscriber provisioning. Telecom operators use it when configuring PSTN and ISDN subscriptions, Centrex arrangements, directory numbers and supplementary services.

It is also relevant to integration, testing and acceptance teams that need a common object model for service provisioning and service configuration. Buyers and quality managers can use it to check whether a supplier's management interface supports the same customer administration structure.

Which standards are used with SIST I-ETS 300 291 E1:2003?

SIST I-ETS 300 291 E1:2003 relies on several related ETSI and CCITT publications for numbering, service descriptions and the management information model.

• ETR 047 - gives the TMN management services context that the CA model follows.
• ETR 046 - provides modelling guidelines for Telecommunications Management Networks.
• ETR 010 - supplies the ISDN service selection background used to choose teleservices, bearer services and supplementary services.
• ETS 300 050 - provides the Multiple Subscriber Number (MSN) supplementary service description.
• CCITT Recommendation E.164 - supplies the ISDN-era numbering plan used for directory numbers.
• CCITT Recommendations F.200 and F.184 - provide the Teletex and group 4 telefax service descriptions.
• CCITT Recommendations I.210, I.230, I.231, I.241 and I.254 - define service principles, bearer service categories, circuit-mode bearer services, teleservices and multiparty supplementary services.
• CCITT Recommendation M.3100 - provides the generic network information model.
• CCITT Recommendations X.720, X.721, X.722, X.730, X.731 and X.732 - provide the OSI management information model, managed object definition guidelines and state and relationship management functions.
• CCITT Recommendation X.25 - gives the packet-mode interface reference used as background for data-network aspects.
• CEPT Handbook on services and facilities offered to the subscribers in telephone system - provides the service context for telephone-network facilities.

What does the SIST I-ETS 300 291 E1:2003 document contain?

SIST I-ETS 300 291 E1:2003 contains an informal model description, formal managed-object definitions, package definitions, behaviour definitions, attribute definitions, name bindings and an ASN.1 module. The main body covers the managed objects for access, directory numbers, customer profiles, customized resources and customized services, plus the service objects used for ISDN and Centrex provisioning.

It also contains translation tables in Annex A that map descriptive names to formal object and attribute names, which is useful when implementing or reading the ASN.1 model. Annex B adds candidate supplementary services and their associated attributes and behaviours. Annex C gives worked examples that show how the object model is instantiated for different customer configurations, including single-line and multi-line cases.

SLOVENSKI STANDARD
01-december-2003
Omrežni vidiki (NA) – Funkcijska specifikacija za strankino administracijo (CA) na
vmesniku operacijski sistem/omrežni element (OS/NE)
Network Aspects (NA); Functional specification of Customer Administration (CA) on the
Operations System/Network Element (OS/NE) interface
Ta slovenski standard je istoveten z: I-ETS 300 291 Edition 1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

INTERIM
EUROPEAN I-ETS 300 291
TELECOMMUNICATION January 1995
STANDARD
Source: ETSI TC-NA Reference: DI/NA-043309
ICS: 33.080
Network, interfaces
Key words:
Network Aspects (NA);
Functional specification of Customer Administration (CA)
on the Operations System/Network Element (OS/NE) interface
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
Copyright Notification: No 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 1995. All rights reserved.
New presentation - see History box

Page 2
I-ETS 300 291: January 1995
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
I-ETS 300 291: January 1995
Contents
Foreword .11
Introduction.11
1 Scope .13
2 Normative references.13
3 Definitions and abbreviations .14
3.1 Definitions .14
3.2 Abbreviations .15
4 Information model diagrams.15
4.1 Entity-relationship models.16
5 Information model description.23
5.1 Object class description.23
5.1.1 Managed element object class.23
5.1.2 Access port object classes.23
5.1.2.1 Access port.23
5.1.2.2 Basic access.24
5.1.2.3 Primary rate access.24
5.1.2.4 Digital access.25
5.1.2.5 Analogue access .25
5.1.3 Access channel object class .25
5.1.4 Directory number object classes .26
5.1.4.1 Directory number .26
5.1.4.2 CCITT Recommendation E.164 directory number .27
5.1.5 Customer profile object classes .27
5.1.5.1 Customer profile .27
5.1.5.2 Analogue/ISDN customer profile .28
5.1.5.3 Centrex group profile .28
5.1.5.4 Centrex user profile .28
5.1.5.5 Centrex console profile.29
5.1.6 Customized resources object class.29
5.1.7 Customized service object classes .30
5.1.7.1 Customized service object class .30
5.1.7.2 Customized bearer service.30
5.1.7.2.1 Circuit mode 64 kbit/s customized bearer service.30
5.1.7.2.2 Circuit mode 3,1 kHz audio customized bearer service .30
5.1.7.3 Customized teleservice.31
5.1.7.3.1 Teletex teleservice.31
5.1.7.3.2 Telefax group 4 teleservice .31
5.1.7.3.3 Telephony 3,1 kHz teleservice object class.31
5.1.7.4 Customized supplementary service object class.31
5.1.7.4.1 Calling line identification presentation supplementary
service .32
5.1.7.4.2 Calling line identification restriction supplementary service.32
5.1.7.4.3 Direct dialling in supplementary service .32
5.1.7.4.4 Multiple subscriber number supplementary service .32
5.1.7.4.5 Terminal portability supplementary service .33
5.1.7.4.6 Advice of charge: charging information during the call
supplementary service.33
5.1.7.4.7 Advice of charge: charging information at the end of the
call supplementary service .33
5.1.7.4.8 Advice of charge: charging information at call set-up time
supplementary service.33

Page 4
I-ETS 300 291: January 1995
5.1.7.4.9 Call hold supplementary service . 34
5.1.7.4.10 Call waiting supplementary service. 34
5.1.7.4.11 Three party supplementary service. 34
5.1.7.4.12 Completion of calls to busy subscriber supplementary
service. 34
5.1.7.4.13 Call forwarding busy supplementary service. 34
5.1.7.4.14 Call forwarding no reply supplementary service . 35
5.1.7.4.15 Call forwarding unconditional supplementary service. 35
5.1.7.4.16 Closed user group supplementary service. 35
5.1.7.4.17 Closed user group supplementary service subscription
option . 36
5.1.8 Group dial plan . 36
5.2 Definition of attributes. 37
5.2.1 Relative distinguished name. 37
5.2.2 State attributes. 37
5.2.2.1 Operational state. 37
5.2.2.2 Administrative state. 37
5.2.3 Relationship attributes . 37
5.2.3.1 Owner object classes. 38
5.2.3.1.1 Customer profile. 38
5.2.3.1.2 Customized resources . 38
5.2.3.1.3 Customized services. 38
5.2.3.2 Association attributes. 39
5.2.3.2.1 Associated DN . 39
5.2.3.2.2 Associated access ports . 39
5.2.3.2.3 Associated access channels. 39
5.2.3.2.4 Associated customer profile. 39
5.2.3.2.5 Associated customized resources . 40
5.2.3.2.6 Associated customized services. 40
5.2.3.2.7 Associated customized supplementary services . 40
5.3 Actions description . 41
5.4 Notifications description . 41
6 Formal definitions . 41
6.1 Definition of managed object classes. 41
6.1.1 Access channel. 41
6.1.2 Access port. 41
6.1.3 Advice of charge: charging information during the call. 42
6.1.4 Advice of charge: charging information at the end of the call. 42
6.1.5 Advice of charge: charging information at call set-up time. 42
6.1.6 Analogue access . 42
6.1.7 Analogue ISDN customer profile . 43
6.1.8 Basic access. 43
6.1.9 Completion of calls to busy subscribers . 43
6.1.10 Call forwarding busy . 43
6.1.11 Call forwarding, no reply . 44
6.1.12 Call forwarding unconditional. 44
6.1.13 Call hold. 44
6.1.14 Call waiting. 44
6.1.15 Centrex console profile. 45
6.1.16 Centrex group profile . 45
6.1.17 Centrex user profile . 45
6.1.18 Circuit mode 3,1 kHz audio. 45
6.1.19 Circuit mode 64 kbit/s . 45
6.1.20 Calling line identification presentation. 46
6.1.21 Calling line identification restriction. 46
6.1.22 Closed user group . 46
6.1.23 Closed user group subscription options. 46
6.1.24 Customer profile . 47
6.1.25 Customized bearer service. 47
6.1.26 Customized resources. 47
6.1.27 Customized service . 48
6.1.28 Customized supplementary service. 48

Page 5
I-ETS 300 291: January 1995
6.1.29 Customized teleservice .48
6.1.30 Direct dialling in .48
6.1.31 Digital access .49
6.1.32 Directory number.49
6.1.33 CCITT Recommendation E.164 DN.49
6.1.34 Group dial plan .49
6.1.35 Multiple subscriber number .50
6.1.36 Primary rate access.50
6.1.37 Telefax group 4 .50
6.1.38 Telephony.50
6.1.39 Teletex.51
6.1.40 Terminal portability supplementary service .51
6.1.41 Three party .51
6.2 Definition of packages .51
6.2.1 Acting role package.51
6.2.2 Administrative state package .51
6.2.3 Associated consoles package.51
6.2.4 Line test capability package .52
6.2.5 Subscriber characteristics package .52
6.3 Definition of behaviours .53
6.3.1 Access channel common behaviour .53
6.3.2 Access channel create behaviour .53
6.3.3 Access channel delete behaviour.53
6.3.4 Access channel for customer administration behaviour.53
6.3.5 Access channel relation behaviour.53
6.3.6 Access channel state behaviour.54
6.3.7 Access port common behaviour.54
6.3.8 Access port relations behaviour .54
6.3.9 Access port state behaviour.54
6.3.10 Advice of charge: charging information during the call, common behaviour.54
6.3.11 Advice of charge: charging information at the end of the call, common
behaviour.54
6.3.12 Advice of charge: charging information at call set-up time, common
behaviour.55
6.3.13 Analogue access common behaviour .55
6.3.14 Analogue access delete behaviour .55
6.3.15 Analogue access for customer administration behaviour.55
6.3.16 Analogue ISDN profile common behaviour .55
6.3.17 Analogue ISDN profile relations behaviour .55
6.3.18 Basic access common behaviour.55
6.3.19 Basic access delete behaviour.55
6.3.20 Basic access for customer administration behaviour.56
6.3.21 Completion of calls to busy subscriber, common behaviour.56
6.3.22 Call forwarding busy, common behaviour .56
6.3.23 Call forwarding no reply, common behaviour.56
6.3.24 Call forwarding unconditional, common behaviour.56
6.3.25 Call hold common behaviour.56
6.3.26 Call waiting common behaviour .56
6.3.27 Centrex console profile common behaviour.56
6.3.28 Centrex console profile delete behaviour.56
6.3.29 Centrex group profile common behaviour.56
6.3.30 Centrex user profile common behaviour .57
6.3.31 Circuit mode 3,1 kHz audio common behaviour .57
6.3.32 Circuit mode 3,1 kHz audio create behaviour .57
6.3.33 Circuit mode 3,1 kHz audio delete behaviour.57
6.3.34 Circuit mode 64 kbit/s common behaviour.57
6.3.35 Circuit mode 64 kbit/s create behaviour.57
6.3.36 Circuit mode 64 kbit/s delete behaviour .57
6.3.37 Calling line identification presentation supplementary service common
behaviour.57
6.3.38 Calling line identification restriction supplementary service common
behaviour.58
6.3.39 Closed user group common behaviour .58

Page 6
I-ETS 300 291: January 1995
6.3.40 Closed user group create behaviour. 58
6.3.41 Closed user group delete behaviour. 58
6.3.42 Closed user group subscription option common behaviour. 58
6.3.43 Closed user group subscription option create behaviour. 58
6.3.44 Closed user group subscription option delete behaviour. 59
6.3.45 Customer profile common behaviour. 59
6.3.46 Customer profile create behaviour . 59
6.3.47 Customer profile delete behaviour. 59
6.3.48 Customer profile state behaviour. 59
6.3.49 Customized bearer service common behaviour . 60
6.3.50 Customized bearer service relations behaviour. 60
6.3.51 Customized resources common behaviour . 60
6.3.52 Customized resources create behaviour . 60
6.3.53 Customized resources delete behaviour . 61
6.3.54 Customized resources relations behaviour. 61
6.3.55 Customized resources state behaviour . 61
6.3.56 Customized services common behaviour. 61
6.3.57 Customized service relations behaviour. 62
6.3.58 Customized service state behaviour. 62
6.3.59 Customized supplementary service common behaviour. 62
6.3.60 Customized supplementary service relations behaviour . 62
6.3.61 Customized teleservice relations behaviour . 63
6.3.62 Customized teleservice common behaviour. 63
6.3.63 Direct dialling in supplementary service common behaviour. 63
6.3.64 Digital access common behaviour. 63
6.3.65 Digital access delete behaviour . 63
6.3.66 Directory number common behaviour . 63
6.3.67 Directory number relation behaviour. 64
6.3.68 Directory number state behaviour. 64
6.3.69 CCITT Recommendation E.164 DN common behaviour . 64
6.3.70 CCITT Recommendation E.164 DN delete behaviour. 64
6.3.71 Group dial plan common behaviour. 64
6.3.72 Group dial plan create behaviour. 65
6.3.73 Group dial plan delete behaviour. 65
6.3.74 Multiple subscriber number supplementary service common behaviour. 65
6.3.75 Multiple subscriber number supplementary service create behaviour. 65
6.3.76 Multiple subscriber number supplementary service delete behaviour. 65
6.3.77 Primary rate access common behaviour . 65
6.3.78 Primary rate access for customer administration behaviour . 65
6.3.79 Supplementary service create behaviour . 65
6.3.80 Supplementary service delete behaviour. 65
6.3.81 Telephony common behaviour . 65
6.3.82 Telephony create behaviour . 66
6.3.83 Telephony delete behaviour. 66
6.3.84 Teletex common behaviour . 66
6.3.85 Teletex create behaviour . 66
6.3.86 Teletex delete behaviour . 66
6.3.87 Telefax group 4 common behaviour. 66
6.3.88 Telefax group 4 create behaviour. 66
6.3.89 Telefax group 4 delete behaviour . 66
6.3.90 Terminal portability supplementary service common behaviour. 66
6.3.91 Three party supplementary service common behaviour. 67
6.4 Definition of attributes. 67
6.4.1 Access channel and rate . 67
6.4.2 Acting role. 67
6.4.3 Advice of charge activation. 67
6.4.4 Announcement. 67
6.4.5 Associated default DN . 67
6.4.6 Associated consoles. 67
6.4.7 Associated member access channels . 67
6.4.8 Associated member access ports . 68
6.4.9 Associated member customized services . 68
6.4.10 Associated member CCITT Recommendation E.164 directory numbers . 68

Page 7
I-ETS 300 291: January 1995
6.4.11 Associated member supplementary services.68
6.4.12 Associated owner customer profiles .68
6.4.13 Associated owner customized resources.68
6.4.14 Associated owner customized services.69
6.4.15 Completion of calls to busy subscriber recall mode .69
6.4.16 Call forwarding active notification.69
6.4.17 Call forwarding calling notification .69
6.4.18 Call forwarding release information.69
6.4.19 Call forwarding served notification .69
6.4.20 Call ID restriction options .69
6.4.21 Call waiting calling notification.70
6.4.22 Channel rate.70
6.4.23 Channel type .70
6.4.24 Configuration .70
6.4.25 Closed user group barring.70
6.4.26 Closed user group data network ID.70
6.4.27 Closed user group index .70
6.4.28 Closed user group interlock code.70
6.4.29 Closed user group network authorisation.70
6.4.30 Customer profile ID .70
6.4.31 Customized resources ID.71
6.4.32 Customized service ID .71
6.4.33 D-channel layer 1 activation .71
6.4.34 D-channel layer 2 activation .71
6.4.35 Dialled codes list .71
6.4.36 CCITT Recommendation E.164 directory number.71
6.4.37 CCITT Recommendation E.164 directory number ID .71
6.4.38 Establishment.71
6.4.39 Group dial plan ID .72
6.4.40 Identifying name .72
6.4.41 Line characteristics.72
6.4.42 Line signalling.72
6.4.43 Line test capability.72
6.4.44 Maximum number of information channels.72
6.4.45 Maximum number of total calls .72
6.4.46 Maximum number of waiting calls.72
6.4.47 Number of digits for call ID.72
6.4.48 No screening option .72
6.4.49 Number of digits for terminal ID .73
6.4.50 Number of digits not to transmit .73
6.4.51 Preferred closed user group identifier .73
6.4.52 Screen originating DN .73
6.4.53 Subscriber category .73
6.4.54 Subscriber type.73
6.4.55 Symmetry .73
6.4.56 Telefax group 4 class .73
6.4.57 Teletex mode.73
6.4.58 Third wire equipment.73
6.4.59 Translation table.74
6.5 Name bindings.74
6.5.1 Access channel basic access .74
6.5.2 Access channel digital access.74
6.5.3 Access channel primary rate access.74
6.5.4 Access port managed element.74
6.5.5 Customer profile managed element.74
6.5.6 Centrex group profile centrex user profile .74
6.5.7 Centrex group profile centrex console profile.75
6.5.8 Customized resources customer profile.75
6.5.9 Customized service customer profile .75
6.5.10 CCITT Recommendation E.164 directory number managed element.75
6.5.11 Group dial plan .75
6.6 ASN.1 defined types module .75

Page 8
I-ETS 300 291: January 1995
Annex A (informative): Reference list for used names. 79
A.1 Translation table for object classes (clauses 5 and 6) . 79
A.2 Translation table for attribute names (clauses 5 and 6) . 80
Annex B (informative): Candidates for standardization . 82
B.1 Supplementary services managed object classes. 82
B.1.1 Automatic line. 82
B.1.2 Automatic recall. 82
B.1.3 Call pickup. 82
B.1.4 Call transfer. 82
B.1.5 Changed destination . 83
B.1.6 Code calling. 83
B.1.7 Incoming call barring . 83
B.1.8 Malicious call indication. 83
B.1.9 Message waiting. 83
B.1.10 Outgoing call barring . 84
B.1.11 Reminder call . 84
B.1.12 Repeat call . 84
B.2 Attribute descriptions . 84
B.2.1 Auto line destination DN. 84
B.2.2 Auto line timeout. 84
B.2.3 Change destination treatment . 84
B.2.4 Change DN. 85
B.2.5 Code call list size. 85
B.2.6 Code call pairs. 85
B.2.7 Call pickup identifier . 85
B.2.8 Call pickup type . 85
B.2.9 ICB category list . 85
B.2.10 ICB treatment . 85
B.2.11 Message indicate . 85
B.2.12 Message type . 86
B.2.13 OCB category. 86
B.2.14 OCB treatment . 86
B.2.15 Reminder program . 86
B.2.16 Reminder time. 86
B.2.17 Secondary number triplet . 86
B.3 Behaviour definitions . 86
B.3.1 Automatic line behaviour. 86
B.3.2 Auto recall behaviour. 86
B.3.3 Call pickup behaviour. 87
B.3.4 Call transfer behaviour . 87
B.3.5 Change destination behaviour. 87
B.3.6 Code call behaviour. 87
B.3.7 Incoming call barring behaviour . 87
B.3.8 Malicious call indication behaviour . 87
B.3.9 Message waiting behaviour. 87
B.3.10 Outgoing call barring behaviour . 87
B.3.11 Reminder call behaviour. 87
B.3.12 Repeat call behaviour. 87
B.4 ASN.1 defined types module . 87
Annex C (informative): Examples of use of the customer administration model. 89
C.1 Example 1. 89
C.2 Example 2. 89

Page 9
I-ETS 300 291: January 1995
C.3 Example 3 .90
C.4 Example 4 .91
History.93

Page 10
I-ETS 300 291: January 1995
Blank page
Page 11
I-ETS 300 291: January 1995
Foreword
This Interim European Telecommunication Standard (I-ETS) has been produced by the Network Aspects
(NA) Technical Committee of the European Telecommunications Standards Institute (ETSI).
An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution ahead
of a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETS
is limited to three years after which it can be converted into an ETS, have it's life extended for a further
two years, be replaced by a new version, or be withdrawn.
This I-ETS identifies, in general, the managed objects to be used when performing Customer
Administration (CA) on the Operations System to Network Element (OS/NE) interface.
The practical realization of an OS/NE interface based on this I-ETS has to be supported by a profile which
specifies and delimits in more detail the application of this I-ETS.
Annex C contains examples on how to apply this I-ETS for customer administration purposes.
Proposed announcement date
Date of latest announcement of this I-ETS (doa): 30 April 1995
Introduction
For this I-ETS, the following priorities were assigned for the scope of the CA model:
- modelling of analogue, digital and Integrated Services Digital Network (ISDN) subscribers and
Private Branch Exchanges (PBXs);
- modelling of the priority 1 ETSI ISDN teleservices, bearer services and supplementary services,
including centrex.
Extendibility to cover priority 2 ETSI ISDN teleservices, bearer services and supplementary services,
mobile subscribers, ATM, cordless and Universal Personal Telecommunication (UPT) subscribers, packet
switching, the full range of CEPT services and non-standardized services (e.g. hunting, etc.) is foreseen
via subclassing (see entity-relationship diagram subclause 4.1, and descriptions in subclause 5.1).
For this edition of this I-ETS, the CA model is restricted to modelling of semi-permanent subscriber data.
Call processing and dynamic (state) information are currently not covered.

Page 12
I-ETS 300 291: January 1995
Blank page
Page 13
I-ETS 300 291: January 1995
1 Scope
This Interim European Telecommunication Standard (I-ETS) specifies the management aspects of
Customer Administration (CA) for Public Switched Telephone Network (PSTN), and public Integrated
Services Digital Network (ISDN), in line with descriptions in ETR 047 [4], and restricted to service
provisioning and serv
...