ITU-T M 3660-1992 ISDN Interface Management Services - Maintenance ISDN (Study Group IV) 8 pp《综合业务数字网接口管理服务-维修 综合业务数字网(研究组4)8页》.pdf

《ITU-T M 3660-1992 ISDN Interface Management Services - Maintenance ISDN (Study Group IV) 8 pp《综合业务数字网接口管理服务-维修 综合业务数字网(研究组4)8页》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3660-1992 ISDN Interface Management Services - Maintenance ISDN (Study Group IV) 8 pp《综合业务数字网接口管理服务-维修 综合业务数字网(研究组4)8页》.pdf（8页珍藏版）》请在麦多课文档分享上搜索。

1、CCITT RECMN*Mm3bbO 92 I 4862591 0579151 353 I N T E R NAT I ON AL TE LE CO M M U N I CAT I O N U N I O N CCITT THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE MAINTENANCE: ISDN M.3660 (1 0/92) ISDN INTERFACE MANAGEMENT SERVICES i Recommendation M.3600 CCITT RECHN*H*3bb0 92 II Y86259

2、1 0579152 29T FOREWORD The CCIT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication Union (ITU). CCITT is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to s

3、tandardizing telecommunications on a worldwide basis. The Plenary Assembly of CCIT which meets every four years, establishes the topics for study and approves Recommendations prepared by its Study Groups. The approval of Recommendations by the members of CCITT between Plenary Assemblies is covered b

4、y the procedure laid down in CCIT Resolution No. 2 (Melbourne, 1988). Recommendation M.3660 was prepared by Study Group IV and was approved under the Resolution No. 2 procedure on the 5th of October 1992. CCIT NOTE In this Recommendation, the expression “Administration” is used for conciseness to in

5、dicate both a telecommunication administration and a recognized private operating agency. O ITU 1993 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writi

6、ng from the ITU. CCITT RECMN*N*3bbO 92 D Y862593 0579353 L2b Recommendation M.3660 ISDN INTERFACE MANAGEMENT SERVICES (1 992) Abstract This Recommendation provides Stage 1 descriptions of ISDN interface management services. Keywords - ISDN interface management services; - management of ISDN; - UNI.

7、1 General 1.1 Scope ISDN interface management services are services provided to allow network management capabilities for the ISDN interface, which includes aspects of the subscriber installation (SI) and subscriber access (SA). Communication of management information for ISDN interface management s

8、ervices is across one DSS 1 interface between two peer protocol entities. 1.2 Configuration The reference configuration for ISDN interface management sources may be found in Figure 6M.3600 i. 1.3 Approach 1.3.1 General A three stage approach is used to describe ISDN interface management services. St

9、age 1 is a prose description of the management service. Stage 2 defines the information flow between the network and the customer management entities. In addition for management services the definition of managed objects used to represent the ISDN interface resources and services are defined in Stag

10、e 2. Stage 3 defines the protocols required to implement the particular management service. 1.3.2 Division of work The Stage 1 definition for ISDN interface management services may be found in this Recommendation. 2 ISDN interface services From the following list of ISDN interface management service

11、s, only service profile verification for basic rate (SPV-Basic), service profile verification for primary rate (SPV-Primary), and local loopback management are defined. The remaining services are for further study. - Service profile verification-basic (SPV-Basic); - Local loopback management (LLM);

12、- - Service profile verification - primary (SPV-Primary); Service profile management - basic (SPM-Basic); Recommendation M.3660 (10192) 1 CCITT RECMN*M.3660 92 m 4862591 0579354 Ob2 m - - State change management (SCM). Service profile management - primary (SPM-Primary); 3 Local loopback management (

13、LLM) service This Recommendation identifies an ISDN interface management service to allow either side of an ISDN User-Network Interface to request bearer channels to be looped back. This service is called Local loopback management (LLM), it is optional and is a component of fault management. 3.1 Sta

14、ge I This loopback management service is intended to provide a base capability for other management services. These services would be used in support of the failure detection, fault localization, and fault correction verification maintenance phases. There are a number of potential services this loop

15、back service may form a part of. 1) A “continuity check - a loopback of ISDN user-network interface B-channels, initiated by the customer to test for a B-channel is carried on a facility separate from the D-channel. Additional work is required to define the use of this loopback for a continuity chec

16、k. Remote B-channel termination tests - a remote manager (manager other than the end-user) could use the loopback service from the network to the customer as part of a remote test of an ISDN user-network interface B-channel termination. Such a remote test requires additional work to define the means

17、 of remotely activating the loopback and definition of the tests to be applied. 2) This loopback service may also have applicability to other future services. This Local loopback management service (LLM) provides a means for either side of an ISDN user-network interface to request activation and dea

18、ctivation of loopbacks of the B-channel terminations of the ISDN user-network interface. This service is provided between loopback requesting points that are layer 3 peers of the ISDN user-network in terface. The loopbacks requested by this service are: - - - in the ET toward the user; in the TE or

19、TA toward the network; in the NT2 toward the network; - - in the NT2 toward the user; in the NT1 toward the user (controlled by the ET and requested by the TE or TA) for basic rate access only. Ail loopbacks are on a per channel basis and are under the internal control of the functional group in whi

20、ch they reside (except for loopback C in the NTl, which is under the control of the ET). That is the loopback point and loopback control point are within the same functional group. The loopback requesting point is the other side of the ISDN user-network interface. Any bearer channel termination can

21、be looped by this service. This service is deniable by the loopback control point. Figure l/M.3660 shows the pairs of the loopback control and requesting points involved in this service. 3.2 LLM rules and procedures The following summarizes the Stage 1 description rules and procedures proposed to go

22、vern the LLM messages. These procedures occur between the two-layer-3-peer entities at the two ends of a B-channel. - the service should provide the ability to request activation and deactivation of the loopbacks discussed above; the service should provide positive confmation from the loopback contr

23、ol point to the loopback requesting point that a loopback has been activated or deactivated; - 2 Recommendation M.3660 (10D2) CCITT RECMN*M-3660 92 Li862593 0579355 TT9 Layer 1 control ._._._._ - the service should provide the optional capability to report test results from the loopback requesting p

24、oint to the loopback control point as part of the loopback deactivation; - the service should provide optional reasons why a requested loopback activation or deactivation has not occurred; - the service should provide notification from the loopback control point to the loopback requesting point if t

25、he loopback is deactivated autonomously by the loopback control point; - loopback C may only be invoked with this service when the NT1 is in the same management domain as the ET. TE or TA m-m ControHer/Requester Controller/Requester ControllerIRequester ControIlerlRequester TE or TA p1-61 Controller

26、/Requester Controller/Requester Requester Controller FIGURE 1/M.3660 Loopback controlhequesting points 3.2.1 Relationship to Recommendation Q.931 121 states and procedures When a loopback is active on a channel, the channel should be considered as if a call was ACTIVE. A loopback request on a channe

27、l with an active call or in progress call should be denied with the appropriate reason information. This service does not directly cause call clearing. Active calls should be cleared by Recommen- dation 4.931 2 procedures if necessary. Instead of disrupting an active call, it is preferable to monito

28、r the state of the cal and invoke the loopback after the call has cleared. Recommendation M.3660 (1082) 3 CCITT RECMN*M.3bbO 72 = 4862571 0577156 935 3.2.2 Relationship to management states This service does not directly change ISDN management states. If a B-channel is in the active call state then

29、the loopback request should be denied with the cause of busy traffic, The requesting point can then, at its option, either place the channel in a maintenance state (to keep the channel from being seized if the dl on it clears) and either camp-on to wait for the call to clear or force the cai1 down v

30、ia Recommendation Q.93 1 2 clearing. 4 Service profile verification (SPV) service Service profile verification (SPV) is an optional, interface-specific ISDN management service, which pro- vides the capability to read the service profile information across the ISDN user-network interface. This servic

31、e is a component of configuration management. 4.1 Stage 1 for SPV on basic rate access Successful operation of an ISDN exchangehetwork will require simple and dependable installation and verification of ISDN BRA terminal service profile parameter assignments by both customers and maintenance personn

32、el. To meet this requirement, the ISDN exchange should provide the capability for providing basic service profile data to an ISDN terminal. No requirements are placed on the terminal for processing of the service profile data provided by the ET. However, some potential uses by the terminal (and/or p

33、ersonnel at the terminal) include - terminal initialization, and - verification that - - Feature activators are properly assigned to features; and - correct Terminal endpoint identifier (TEI) or Service profile identifier (SPID) is being used; proper Directory numbers (DNs) and Bearer capabilities (

34、BCs) are registered with the network. 4.1.1 Elements of the service contained in its profe. transfer is for further study. The element of the service is the terminal (TE/TA) requesting from the network that it sends the information The following lists the types of information which are transferred t

35、o the terminal. Additional information - DNs; - bearer capabilities; - - - feature key assignments. number of calls per DN BC pair, feature assigned to DN BC pair; 4.1.2 SPV rules and procedures messages. These procedures occur between the two-layer-3-peer entities at the two ends of an access loop.

36、 The following summarizes the Stage 1 description of the rules and procedures proposed to govern the SPV 1) The terminal should provide the capability to allow the user to start the procedure. (The ability of the network to start the procedure is for further study); The use of SPID is described in R

37、ecommendation 4.932 3. 2, Features may be activated using Feature activators (FAs) using the procedures described in Recommendation Q.932 131. FAs may be mapped to a particular terminal feature key. The services which a particular FA maps to are agreed by the customer and network at subscription tim

38、e. 4 Recommendation M.3660 (10192) CCITT RECNN*N-3660 92 M 4862591 0579157 871 2) 3) SPV may only be invoked when a logical link has been established; in the case of dynamic TEI, the terminai must have completed the terminal initialization procedure, to ailow association to a specific service profil

39、e; SPV will operate when a cai1 is active at a particular terminai; offering calls will not be affected by SPV being in progress. 4) 5) 4.2 Stage I for SPV on primary rate access The complexity of service possible on ISDN primary rate access will require a means for the maintenance personnel to veri

40、fy that the service profiles used by the NT2 and the ET are compatible. This verification may be needed by either customer installation or network maintenance personnel. To meet this need the SPV service on primary rate access should provide for either side of interface to initiate this service. No

41、requirements are placed on either the ET or NT2 for processing the data provided by SPV. However, the “2 may use the service profile data provided by the ET to initialize its side of the interface. 4.2.1 Elements of the service The element of this service is one side of the interface (NT2 or ET) req

42、uesting the other side (ET or NT2) to send the information contained in its profile. The following lists some possible data that may be exchanged. A definitive list is for further study. - Trunk group data: - B-channels in trunk group; - hunt direction; - servicehearer capabilities; - service option

43、s; - billing number (ET provided). - Function group data: - test line numberdcharacteristics. - Routingdata: - ordered list of trunk groups. 4.2.2 Rules and procedures The following summarizes the Stage 1 description of the rules and procedures for SPV on primary rate access. 1) 2) SPV may be invoke

44、d by either the user or the network. SPV may only be invoked when the primary rate access logical link on the D-channel has been established. 3) 4) SPV may be invoked when calls are active on the interface. SPV will not interfere with normal call processing. References u1 CCITT Recommendation M.3600

45、 Principles for the management of ISDNs. PI CCITT Recommendation Q.93 1 ISDN user-network interface layer 3 specjication for basic control. DI CCITT Recommendation Q.932 Generic procedures for the control of ISDN supplementary services. Recommendation M.3660 (10/92) 5 CCITT RECMN*M-3bbO 92 m 4862593 0579358 708 9 Printed in Switzerland Geneva, 1993