ITU-T Z 334-1988 SUBSCRIBER ADMINISTRATION《用户管理》.pdf

上传人:twoload295 文档编号:806681 上传时间:2019-02-04 格式:PDF 页数:22 大小:299.42KB
下载 相关 举报
ITU-T Z 334-1988 SUBSCRIBER ADMINISTRATION《用户管理》.pdf_第1页
第1页 / 共22页
ITU-T Z 334-1988 SUBSCRIBER ADMINISTRATION《用户管理》.pdf_第2页
第2页 / 共22页
ITU-T Z 334-1988 SUBSCRIBER ADMINISTRATION《用户管理》.pdf_第3页
第3页 / 共22页
ITU-T Z 334-1988 SUBSCRIBER ADMINISTRATION《用户管理》.pdf_第4页
第4页 / 共22页
ITU-T Z 334-1988 SUBSCRIBER ADMINISTRATION《用户管理》.pdf_第5页
第5页 / 共22页
点击查看更多>>
资源描述

1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 : TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU-!.G13-!#().%G0G0,!.5!%35“3#2)“%2G0G0!$-).)342!4)/.)45G134G0G0RecommendationG0G0: (Extract from the “LUEG0“OOK)NOTES1 ITU-T Recommendation Z.334 was published in Fascicle X.7 of the Blue Book. This file is an

2、 extract from theBlue Book. While the presentation and layout of the text might be slightly different from the Blue Book version, thecontents of the file are identical to the Blue Book version and copyright conditions remain unchanged (see below).2 In this Recommendation, the expression “Administrat

3、ion” is used for conciseness to indicate both atelecommunication administration and a recognized operating agency. ITU 1988, 1993All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic ormechanical, including photocopying and microfilm,

4、without permission in writing from the ITU.Fascicle X.7 - Rec. Z.334 1Recommendation Z.334Fascicle X.7 - Rec. Z.334SUBSCRIBER ADMINISTRATION1. GeneralThis Recommendation has been developed in accordance with the methodology defined in RecommendationsZ.332 and Z.333.The main part of this Recommendati

5、on deals with the model of the subscriber Administration. A glossary of theterms used is also included. The list of functions to be controlled by means of MML is contained in Annex A. For eachof these functions one or more MML functions can be derived and each of them can be described using themetal

6、anguage defined in Recommendation Z.333 in order to detail the relevant information structure.Annex B contains a list of MML functions and the information structure diagrams associated to each of them tobe used as guidelines.2 IntroductionThe scope of this Recommendation is the operational aspect of

7、 the functional area of subscriber administration.It has been recognized that subscriber Administration is related to various administrative procedures, belongingto other functional areas, which have to be carried out prior to or in functional relationship to the jobs to be controlledby MML.Such adm

8、inistrative procedures are Administration dependent with different degrees of data processing support.They can be considered as the administrative environment.3 Subscriber administration model3.1 IntroductionThe model is applicable to subscribers to whom normal telephone services (POTS: Plan of Tele

9、phone Services)are offered.For the representation of the model the metalanguage defined in Recommendation Z.333 has been used.For the purposes of this Recommendation subscribers have been divided into the following two classes (seeFigures B-1/Z.334, B-2/Z.334 and B-3/Z.334: single-line subscribers,

10、comprising single-party and multi-party lines; multi-line subscribers, comprising PBX (without direct inward dialling), PABX (with direct inwarddialling) and subscriber line groups.Both single-line and multi-line subscribers are embedded in an administrative environment. This environmentmay comprise

11、 all data relevant for administering the various types of subscribers. Examples for such data are addressesof subscribers and subscribers features. The administrative environment aspects are not considered in detail in thismodel.3.2 Description of model3.2.1 GeneralSubscribers are distinguished by t

12、he data describing the way in which they are connected to and managed bythe public exchange, including data related to the associated hardware equipment in the exchange. Examples are twoparty lines, ordinary subscriber lines, PABXs multi-party lines.From the Administration view every subscriber fall

13、s into one of the two main types identified in the model,single- or multi-line subscribers. Due to the different association of information entities needed for the representationof these two main types, two different sets of MML functions are felt to be appropriate. The relevant informationentities

14、defined in the model are described in the following sections.3.2.2 Line characteristicsLine characteristics are described by their attributes which may include information about class of line, kind of2 Fascicle X.7 - Rec. Z.334signalling, attenuation equalization, traffic directions, etc.3.2.3 Line

15、group characteristicsLine group characteristics are described by their attributes which may include information about kind ofsignalling, class of line, traffic directions etc., associated to all lines forming the group.3.2.4 Facility characteristicsFacility characteristics are described by their att

16、ributes. They include all information about supplementaryservices which can be assigned to a given subscriber. Examples are abbreviated dialling, do not disturb service, wake-up service, charging information like normal charging or free of charge.There are attributes which can only be controlled by

17、the Administration while others are primarily controlled bythe subscribers themselves. However, it has been recognized that in the latter case these attributes can also becontrolled by the Administration.3.2.5 Restriction characteristicsRestriction characteristics include information which indicate

18、the limitations on the regular operational mode,e.g., traffic restrictions for originating calls.3.2.6 Monitoring characteristicsMonitoring characteristics are related to particular monitoring actions, which are carried out by the system. Themonitoring actions are mainly of a temporary nature and co

19、mprise subscriber Administration functions carried out toobtain data related to calls. Examples are malicious call tracing and charging observation. Monitoring actions areactivated on subscribers or Administrations request and are described by their attributes, e.g. duration of monitoring,starting t

20、ime.3.2.7 Single-line subscriber identitySingle-line subscriber identity allows the unambiguous identification of a single-line subscriber, normally by itsdirectory number.3.2.8 Multi-line subscriber identityMulti-line subscriber identity allows the unambiguous identification of a multi-line subscri

21、ber, normally by itsdirectory numbers.3.2.9 Equipment identityEquipment identity allows the unambiguous identification of the device to which a subscriber line is connected.3.2.10 Line numberA line number allows the unambiguous identification of a line within a line group.3.2.11 Associated directory

22、 numberAn associated directory number may be entered for lines that are members of a multi-line subscriber and thatneed to have associated with them a directory number other than the multi-line subscriber identity. Examples includethe night service number for a member of a PBX or the directory numbe

23、r of a directly dialable member of a multi-linehunt group.3.2.12 StateThe state of a subscriber line identifies the current operational mode in an unique way. It may be possible tointerrogate the state of a subscriber line.4 Glossary of termssingle-line subscriber lineA line between a public exchang

24、e and a subscriber set.multi-line subscriber lineA line between a public exchange and a P(A)BX or a line between a public exchange and a subscriber setFascicle X.7 - Rec. Z.334 3belonging to a subscriber line group.line groupA line group is a group of lines of a multi-line subscriber with some commo

25、n line characteristics, e.g.incoming, outgoing, bothway.subscriber line groupA group of line groups which are recognized and managed by a public exchange as a logical group.ANNEX A(to Recommendation Z.334)List of system functions to be controlled by MML and list of jobsA.1 List of functions to be co

26、ntrolled by MML1) administering subscriber lines and related data;2) tracing malicious calls;3) retrieving subscriber charging information;4) observing subscriber charging.A.2 List of jobsA.2.1 GeneralThe jobs considered hereafter can be performed either at the exchange level or at Operation and Mai

27、ntenanceCentre (OMC) level, or both.The description of each job should include the following general characteristics. The operator is supposed to input all data relevant for the job to be performed. The system is supposed to check the input data for formal correctness and logical plausibility and to

28、 outputan error message in the case of syntax/semantic errors and incomplete insertions, and to prompt for furtherinput. The system should update the data in its database according to the requirements of the performed job, e.g.to store, to delete data in its database.A.2.2 List of jobsA.2.2.1 To cre

29、ate a single-line subscriber The purpose of the job is to define an association between an equipment identity, subscriber identity, line,facility, restriction and monitoring characteristics. The complexity of the job is medium. The frequency of the job is high. In local exchanges the job expected to

30、 be one of the most frequent. The job is performed at the request of the subscriber, in accordance with the availability of requiredequipment, directory numbers, etc.A.2.2.2 To create a multi-line subscriber, a new line group of a multi-line subscriber, or a new line of a multi-linesubscriber The pu

31、rpose of the job is to create a multi-line subscriber, a new line group of a multi-line subscriber, or anew line of a multi-line subscriber, and to define an association between multi-line subscriber identity, linegroup identity, line numbers, equipment identities, line, facility, restriction and mo

32、nitoring characteristics. The complexity of the job is medium. The frequency of the job is low.4 Fascicle X.7 - Rec. Z.334 The job is performed at the request of the subscriber, in accordance with the availability of requiredequipment, directory numbers, etc.A.2.2.3 To change single-line subscriber

33、related data The purpose of this job is to change single-line subscriber related data, i.e. the line and/or facility and/orthe restriction and/or the monitoring characteristics. The complexity of the job depends on the number of the changes and assignments. The frequency of the job is medium. The jo

34、b is performed at the request of the subscriber or of the Administration.A.2.2.4 To change multi-line subscriber related data The purpose of the job is to change multi-line subscriber related data, i.e. the facility and/or line and/orrestriction and/or monitoring characteristics and/or associated di

35、rectory number. The complexity of the job depends on the number of the changes and assignments. The frequency of the job is low; The job is performed at the request of the subscriber or of the Administration.A.2.2.5 To delete a single-line subscriber The purpose of the job is to delete all data, i.e

36、., equipment identity, subscriber identity and characteristics,related to a certain single-line subscriber. The complexity of the job is low depending on system checks. The frequency of the job is medium. The job is performed on request of the subscriber or of the Administration.A.2.2.6 To delete a

37、multi-line subscriber, line groups of a multi-line subscriber, or lines of a multi-line subscriber The purpose of the job is to delete a multi-line subscriber, line groups of a multi-line subscriber or lines ofa multi-line subscriber. The complexity of the job is medium depending on system checks. T

38、he frequency of the job is low. The job is performed at the request of the subscriber or of the Administration.A.2.2.7 To interrogate single-line or multi-line subscriber related data The purpose of the job is to interrogate single-line or multi-line subscriber, line related data, according toselect

39、ion criteria, e.g. single-line/multi-line subscriber identity, all charge free lines. The system is supposed to display the desired data on an output device at the operators request. The complexity of the job is low. The frequency of the job is high when the selection criterion is subscriber identit

40、y and low when otherselection criteria are used. The job is performed at the request of the Administration.A.2.2.8 To retrieve charging information for a single-line or a multi-line subscriber The purpose of the job is to retrieve charging information for a single-line or a multi-line subscriber in

41、caseof the pulse metering. The system is supposed to provide subscribers charging information on an output device at the operatorsrequest. The complexity of the job is low. The frequency of the job is low. The job is performed for administrative reasons.A.2.2.9 To block/unblock a single-line subscri

42、ber The purpose of the job is to make a single-line subscriber unavailable/available to traffic.Fascicle X.7 - Rec. Z.334 5 The system is supposed to block/unblock a single-line subscriber to originating and/or terminating traffic. The complexity of the job is low. The frequency of the job is medium

43、. The job is performed for administrative reasons.A.2.2.10 To block/unblock a multi-line subscriber The purpose of the job is to make a multi-line subscriber, line groups of a multi-line subscriber or lines of amulti-line subscriber unavailable/available to traffic. The system is supposed to block/u

44、nblock a multi-line subscriber, line groups of a multi-line subscriber orlines of a multi-line subscriber to originating and/or terminating traffic. The complexity of the job is low. The frequency of the job is low. The job is performed for administrative reasons.A.2.2.11 To activate/deactivate mali

45、cious call tracing for a single-line or a multi-line subscriber The purpose of the job is to enable/disable malicious call tracing for a single-line subscriber, a multi-linesubscriber, or line groups of a multi-line subscriber. The system is supposed to collect the malicious call tracing data, to st

46、ore it and to display it on operatorsrequest. The complexity of the job is low. The frequency of the job is low. The job is performed at the request of the subscriber.A.2.2.12 To activate/deactivate a single-line or a multi-line subscriber The purpose of the job is to put into or to take out of serv

47、ice a single-line subscriber, a multi-linesubscriber, line groups of a multi-line subscriber or lines of a multi-line subscriber previously defined inthe system. The activation function may be implied in the corresponding creation function. The complexity of the job is low. The frequency of the job

48、is high. The job is performed at the request of the subscriber.A.2.2.13 To activate/deactivate single-line or multi-line subscriber charging observation The purpose of the job is to start/stop charging observation for a single-line or a multi-line subscriber for astated duration. The system is suppo

49、sed to collect the charging information data, to store it and to output it on operatorsrequest. The complexity of the job is low. The frequency of the job is low. The job is performed at the request of the Administration.ANNEX B(to Recommendation Z.334)Guidelines for the list of MML functionsand associated information structure diagramsB.1 IntroductionThis annex contains guidelines for the list of MML functions and associated information structure diagramsrelated to the subscriber administration model defined in this R

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 标准规范 > 国际标准 > 其他

copyright@ 2008-2019 麦多课文库(www.mydoc123.com)网站版权所有
备案/许可证编号:苏ICP备17064731号-1