ITU-T I 251 7 (REV 1)-1992 Malicious Call Identification (Study Group I) 10 pp《恶意呼叫识别(研究组I)共10页》.pdf

1、CCITT RECMN*I-25L- 7*(REV*L) 92 W 4862591 0573847 855 INTERNATIONAL TELECOMMUNICATION UNION CCITT 1.251.7 (rev.1) THE INTERNATIONAL TELEGRAPH AND TELEPHONE CONSULTATIVE COMMITTEE INTEGRATED SERVICES DIGITAL NETWORK (ISDN) GENERAL STRUCTURE AND SERVICE CA PA B I LITI ES MALICIOUS CALL IDENTIFICATION

2、Recommendation 1.251.7 (rev.1) Geneva, 1992 FOREWORD The CCIlT (the International Telegraph and Telephone Consultative Committee) is a permanent organ of the International Telecommunication. Union (IT). CCIiT is responsible for studying technical, operating and tariff questions and issuing Recommend

3、ations on them with a view to standardizing telecommunications on a worldwide basis. The Plenary Assembly of CCI“T which meets every four years, establishes the topics for study and approves Recommendations prepared by its Stlidy Groups. The approval of Recommendations by the members of CCIlT betwee

4、n Plenary Assemblies is covered by the procedure laid down in CCl“ Resolution No. 2 (Melbourne, 1988). Recommendation 1.251.7 was prepared by Study Group I and was approved under the Resolution No. 2 procedure on the 4th of August 1992. CCITT NOTE In this Recommendation, the expression “Administrati

5、on“ is used for conciseness to indicate both a telecommunication Administration and a recognized private operating agency. O IT 1992 Ail 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 microf

6、ilm, without permission in writing from the ITU. Recommendation 1.251.7 MALICIOUS CALL IDENTIFICATION (revised 1992) 1 Definition Maiicious Call Identification is a Supplementary service offered to the called party which enables the called party to request that the calling party be identified to the

7、 network and be registered in the network. Note - This would be used by the called party on cails considered to be malicious. 2 Description 2.1 General description Malicious Call Identification (MCID) gives an integrated services digital network (ISDN) user the possibility to cause, by an appropriat

8、e request, the registration in the network of the following items: - called party number; - calling party number; - local time and date of the invocation in the network serving the called user; and - as a service provider option: calling party sub-address (if provided by the calling user). In the ca

9、se of interaction with other supplementary services, it may be required to register more information (see 0 6). The location of the registration function in the served users network is a matter of implementation. The information will not be available to the terminal equipment under the control of th

10、e called user nor the calling user. The information will be stored at a location(s) under the control of the network operator. The provision of call information for MCID purposes on calls between different networks is subject to bilateral agreement between the service providers involved. Furthermore

11、, the provision of call information for MCID purposes across international boundaries wiil be subject to bilateral agreement between the legal authorities of the countries involved. The MCID supplementary service can either be invoked during or after the active phase of the call, but before the call

12、ed user has cleared. Other alternatives are for further study (see 0 3.2.2). A network subscription option may be provided which allows automatic invocation of MCID on calls to the served user which are not answered. As a network option, besides the above registration of call information, the connec

13、tion may be held automatically for legal purposes, on invocation of MCID until the intervention of the service provider. This option is beyond the scope of this Recommendation. Recommendation 1.251.7 1 2.2 Specijc terminology Calling party number: This is the public network provided number which ide

14、ntifies either the calling party or at least the access into the public network of the call from the calling party. Served user: A called user to whom the MCID supplementary service has been provided. 2.3 Qualijcation on the applicability to telecommunication services This supplementary service is a

15、pplicable to all telecommunication services. 3 Procedures 3.1 Provisiodwithdrawal This service shall be provided and withdrawn after pre-arrangement with the service provider, in accordance with national legal requirements. A network subscription option may be provided which allows automatic invocat

16、ion of MCID on calls to the served user which are not answered. Note - The purpose of this option is to allow for registration of calls that ring for a short time only. 3.2 Normalprocedures 3.2.1 Activatioddeactivatiodregistration The MCID supplementary service is activated at provision and deactiva

17、ted at withdrawal, under the control of the service provider. 3.2.2 Invocation and operation The served user can invoke the Malicious Call Identification supplementary service by an appropriate procedure in the following cases: - Before answer (as a service provider option). Note - A typical example

18、 is where a called user may have received a Calling Line Identification (CLI), but wishes to “register” the incoming call with the exchange, possibly without answering the call. (This option is for further study.) During the active phase of the call: This is the normal situation. In this instance, t

19、he called user should be able to continue with the call after invocation of MCID. After the calling party has cleared This would be possible during the limited time the network is awaiting the called users reaction to the network disconnect indication, unless MCID has already been invoked for that c

20、all. After called party has cleared (network option): This would be possible during a short time-out period. (This option is for further study.) - - - Successful invocation will result in registration of the call information described in 0 2.1, The served user should be informed by an appropriate ac

21、knowledgement that the registration has been performed, If the option described in 0 3.1 is subscribed to by the served user, MCID will be invoked automatically by the network at the clearance of all or particular calls to the served user which have not been answered. 2 Recommendation 1.251.7 CCITT

22、RECMNaI.251. 7*(REV*3) 92 m 4862591 0573853 286 m Note - Restrictions may be applied to automatic invocation in order to avoid excessive registration of call information on unanswered calls. Such restrictions may consist of, e.g.: - automatic invocation only on “short” unanswered calls, i.e. those w

23、hich are terminated within a certain time interval after presentation (e.g. 10 seconds); automatic invocation only during certain periods of the day (e.g. night hours). - If on an answered call, the calling user disconnects first, the network should allow the served (= called) user to invoke MCID wi

24、thin the normal time-out applied by the network awaiting the called users reaction to the network disconnect indication, unless MCID has already been invoked for that call. 3.3 Exceptional procedures 3.3.1 Activatioddeactivatiodregistration Not applicable. 3.3.2 Invocation and operation If an invoca

25、tion request is received from a user who is not provided with the MCID supplementary service, an invocation request is received from the served user during a phase of the call when MCID is not supported, or if an invocation request is received from a calling user, then the network will not invoke MC

26、ID. In these cases an appropriate indication will be sent to the served user. If a user has already successfully invoked the MCID supplementary service on a call and the information has been registered, then subsequent attempts to invoke the MCID supplementary service should not be acted upon by the

27、 network. The served user should be informed by an appropriate acknowledgement that the registration has been performed (as in the normal procedures). 3.4 3.4.1 3.4.2 4 5 5.1 Alternative procedures Activatioddeactivatiodregistration Not applicable. Invocation and operation Not applicable. Network ca

28、pabilities for charging Charging requirements are beyond the scope of this Recommendation. Interworking requirements Interworking with PSTN When interworking between public switched telephone network (PSTN) and ISDN occurs, the number of the caliing user may not be available; it may, however, be pos

29、sible to register certain information about the routing of the call depending on the capabilities of the PSTN. Where such interworking applies on a national call, the available information shall be registered in the location appropriate for the network. For international cails, the registration of a

30、vailable information is dependent on any agreement between the lega authorities of the countries involved. Recommendation 1.251.7 3 In the case of interworking where: - a call is forwarded or deflected to a PSTN destination; and - the PSTN supports MCID; and - the forwarded-to PSTN user has MCID act

31、ivated, then, at least the registration of the cailing party number and time should be supported. 5.2 Interworking with private networks A served user (i.e. a disturbed party) on a private ISDN shall be able to send an MCID invocation request to the public ISDN in the case of an incoming public to p

32、rivate network cail. Private ISDNs should technically be able to support and complement the public MCID service beyond the public network boundary by identifying a malicious caller on the private ISDN (if requested by the legal authority) on an outgoing private to public network call. This interwork

33、ing case applies only when an appropriate arrangement between the two network operators exists. 5.3 Interworking with data networks Wherever possible the MCID supplementary service should be supported on calls from data networks. 6 Interaction with other supplementary services 6.3 6.4 6.5 4 6.1 Call

34、 Waiting No impact, i.e. neither supplementary service affects the operation of the other supplementary service. 6.2 Call Transfer The transferring user will not be able to invoke MCID on a call after transfer of that call has been invoked. If, after transfer has been completed, the served (transfer

35、red to) user successfuliy invokes MCID, then the network shall register the numbers of the other user in the call and last transferring users. Connected Line Identification Presentation No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Connected

36、Line Identijication Restriction No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Calling Line Ident8cation Presentation No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Recommendation 1.251.

37、7 6.6 6.7 6.8 6.9 CCITT RECMN*I-25L* 7*i(REV*L) 92 = 4862593 0573853 059 Calling Line Identcation Restnction No impact, Le. neither supplementary service affects the operation of the other supplementary service. Closed User Group No impact, i.e. neither supplementary service affects the operation of

38、 the other supplementary service. Conference Calling No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Direct-Dialling-In If Direct-Dialling-In DI) is provided to the served user of MCID, then MCID should be provided either globally for the whole

39、 access or on a per-DDI number basis, according to access arrangements. In both cases, the ISDN number of the called user, including DDI digits, should be registered. 6.10 Call diversion services 6.10.1 Call Forwarding Busy The MCID supplementary service can be invoked for a forwarded call. In addit

40、ion to the normal operation of the MCID supplementary service, the identity of the called user shall be registered and, as a network option, the last diverting user can be registered. Once forwarding has taken place, the forwarding user cannot invoke the MCID supplementary service. 6.10.2 Call Forwa

41、rding No Reply The MCID supplementary service can be invoked for a forwarded call. In addition to the normal operation of the MCID supplementary service, the identity of the called user shall be registered and, as a network option, the last diverting user can be registered. Once forwarding has taken

42、 place, the forwarding user cannot invoke the MCID supplementary service, 6.10.3 Call Forwarding Unconditional The MCID supplementary service can be invoked for a forwarded call. In addition to the normal operation of the MCID supplementary service, the identity of the called user shall be registere

43、d and, as a network option, the last diverting user can be registered. Once forwarding has taken place, the forwarding user cannot invoke the MCID supplementary service. 6.10.4 Call Deflecfion The MCID supplementary service can be invoked for a deflected call. In addition to the normal operation of

44、the MCID supplementary service, the identity of the called user shall be registered and, as a network option, the last diverting user can be registered. Once deflection has taken place, the deflecting user cannot invoke the MCID supplemenary service. 6.1 1 Line Hunting No impact, i.e. neither supple

45、mentary service affects the operation of the other supplementary service. Recommendation 1.251.7 5 6.12 Three-Party Service No impact, i.e neither supplementary service affects the operation of the other supplementary service. 6.13 User-to-User Signalling No impact, i.e. neither supplementary servic

46、e affects the operation of the other supplementary service. 6.14 Multiple Subscriber Number If Multiple Subscriber Number (MSN) is provided to the served user of MCID, then MCID shall be provided either globally for the whole access or on a per MSN number basis, according to access arrangements. 6.1

47、5 6.16 6.17 6.18 6.19 6.20 6.21 6.22 7 6 Call Hold No impact, Le. neither supplementary service affects the operation of the other supplementary service. Advice of Charge No impact, Le. neither supplementary service affects the operation of the other supplementary service. Multi-level Precedence and

48、 Preemption No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Priority Service No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Malicious Call Identification Not applicable. Outgoing Call Bar

49、ring No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Reverse Charging No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Su b-addressing No impact, i.e. neither supplementary service affects the operation of the other supplementary service. Dynamic description See Figure 1i.251.7. Recommendation 1.251.7 CCITT RECMN*I.251. 7*(REV*1) 92 48b259L 0573855 921 = idle 0 Calling active phase request a Calling clears Accept Record call details (Note) (e-) idle Awaiting input re