Question 25/XI - Protocols for remote operation of specific OAM
applications

Considering

(a) that there is a need for a common approach for remote operation of
specific System Management Applications for switching, transmission, and
customer equipment;

(b) that there is a need to remotely request OAM applications
(e.g., error reports, remote activation of loops, and selftests); which
may be located at the customer premises (or in private networks), in
switching, signalling, and transmission systems, or in Service Control
Centres;

(c) that the requestor of these specific OAM applications may be located
within the customer premises or in one or more OAM centres, or in one or
more Service Control Centres;

(d) that the objects to be managed in various entities will be
identified by other Questions (i.e., service definitions, TMN);

(e) that the convergence with the general OSI concepts and principles is
an objective;

(f) that the selection of a common set of protocol elements is highly
desirable,

What new Recommendation(s) are required for the specific Application
protocols to support OAM System Management Applications controlled from
remote entities?

Study points should include:

1. whether the scope of studies is to be enlarged to include the
following management functions:

- accounting (billing),

- traffic measurements,

- network configuration management: (such as control of dedicated
network resources by a user),

- security management,

- performance management;

2. clarification of the functions and procedures identified as part of
Layer Management;

3. the means of providing a capability for the user to locate faults
between multiple networks (or service providers);

4. the following Questions pertaining to remote loop-back control:

- how are loop-backs identified?

- if a TE performs a loop-back on its B-Channels what cause is to be
specified for the rejection of incoming calls?

- how are channels on which loop-backs are to be performed identified
from a remote location?

- identification of the management information to be exchanged for
maintenance purposes,

- whether the protocol message flows should to be included in the
management application service description andor the protocol
descriptions of these services.

ANNEX 1

(to Question 25/XI)

ISDN user-network interface protocol for
management protocol applications

Annex 1 contains an initial draft Recommendation text defining the
protocol applicable to specific remote user equipment maintenance
applications (e.g., loop-back control, test calls, error or event
reports).

Draft Recommendation Q.942

ISDN USER-NETWORK INTERFACE PROTOCOL FOR MANAGEMENT -
MANAGEMENT PROTOCOL APPLICATIONS

1. General

This.................................

1.1 Scope

Management ................................

2.2 Fault management facilities

2.2.1 Spontaneous error reporting facility

2.2.9 Equipment identification facility

3.1.1.2Maintenance service states of the channels transported by an ST
interface, as seen by the terminal

3.2 Control of selftests

Procedures ..............................

3.3 Control of loop-backs

Procedures for................................

FIGURE 3Q.942

Possible loop-back locations as defined in I.600

Note - .............................................

3.3.2 Loop-back addressing and selection requirements

The .....................................................

3.3.4 Loop-back activation on existing calls

The .........................................................

APPENDIX A

(to draft Recommendation Q.942)

Table A-1Q.942 shows the requirements on Q.942 services from maintenance
operations described in the I.600 Series of Recommendations.

TABLE A-1Q.942

Relationship between maintenance Recommendations in the
I.600 Series and Q.942 services