1、 STD-ITU-T RECMN Q.81-7-ENGL 1797 H 48b2.591 Ob41007 Ob4 = INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU 4.81.7 (06197) SERIES Q: SWITCHING AND SIGNALLING Functions and information flows for services in the ISDN - Supplementary services Stage 2 descripti
2、on for number identification supplementary services: Malicious call identification (MCID) ITU-T Recommendation Q.81.7 (Previously CCITT Recommendation) STD-ITU-T RECMN Q.BL.7-ENGL 1777 LiBb2571 Ob41010 B8b m ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANU
3、AL SERVICE INTERN ATION AL AUTOMATIC AND SEMI -AUTOMATIC WORK1 N G FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.l-Q.3 Q.4-Q.59 Q.60-Q.99 Methodology Q. 60-Q .67 Basic services Q -68-Q.79 (1 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.lOO-Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No
4、. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK I
5、NTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN Q. 120-Q.249 Q.250-Q.309 Q.310-Q.399 Q.400-(2.499 Q.500-Q .599 Q.600-Q.699 Q. 700-Q 349 Q.850-Q.999 Q. I 000-Q. 1 O99 Q.llOO-Q.1199 Q.1200-Q.1999 Q.2000-Q.2999 For further details, please refer to ITU-T List of Recommendati
6、ons. ITU-T RECOMMENDATION Q.81.7 STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES: MALICIOUS CALL IDENTIFICATION (MCID) Summary This Recommendation defines the stage 2 of the Integrated Services Digital Network (ISDN) as provided by telecommunications operators for the Malicious
7、Call Identification (MCID) supplementary service. Stage 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call. The malicious call identification supplem
8、entary service allows the served user to alert the service provider that a malicious call has been received and requests that the service provider retain the calling information for the purpose of identifjkg the caller. The MCID supplementary service is available to all telecommunications services.
9、Source ITU-T Recommendation 4.81.7 was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 5th of June 1997. STD-ITU-T RECMN Q.BL-7-ENGL 1777 9 4662591 Ob41012 b59 W FOREWORD ITU (International Telecommunication Union) is the United Nations
10、Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the IT. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommuni
11、cations on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the I
12、TU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conc
13、iseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU take
14、s no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU hadkad not received notice of intellectual
15、 property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1998 All rights reserved. No part of this publica
16、tion may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation Q.81.7 (06/97) STD-ITU-T RECMN Q-81J-ENGL 1997 48b2591 Ob41013 575 W 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 7.1
17、0 CONTENTS Page Malicious Call Identification (MCID) Scope References Definitions Symbols and abbreviations . Description . Derivation of the functional model . 7.6.1 The functional model description 7.6.2 Description of the functional entities 7.6.3 Information flows . Relationship with a basic ser
18、vice 7.7.1 Information flow diagrams 7.7.2 Definitions of individual information flows SDL diagrams for functional entities . 7.8.1 FE1 7.8.2 FE2 7.8.3 FE3 7.8.4 FE4 Functional Entity Actions (FEAs) 7.9.1 FEAs of FE1 7.9.2 FEAs of FE2 7.9.3 FEAs of FE3 7.9.4 FEAs of FE4 Allocation of functional enti
19、ties to physical localities . Annex A . Procedure to be included in the basic call process (Recommendation Q.71 4) 1 1 1 2 2 4 4 7 8 8 9 11 19 19 19 19 20 20 21 22 Recommendation Q.81.7 (06/97) iii - Recommendation 4.81.7 STAGE 2 DESCRIPTION FOR NUMBER IDENTIFICATION SUPPLEMENTARY SERVICES: MALICIOU
20、S CALL IDENTIFICATION (MCID) (Geneva, 1997) 7 Malicious Call Identification (MCID) 7.1 Scope This Recommendation defines the stage 2 of the Integrated Services Digital Network (ISDN) as provided by telecommunications operators for the Malicious Call Identification supplementary service (MCID). Stage
21、 2 identifies the functional capabilities and the information flows needed to support the service description. The stage 2 description also identifies user operations not directly associated with a call (Recommendation I. 130 i). This Recommendation is specified according to the methodology specifie
22、d in Recommendation 4.65 2. This Recommendation does not formally describe the relationship between this supplementary service and the basic call. Where possible this information is included for guidance however. This Recommendation does not speci all users of this Recommendation are therefore encou
23、raged to investigate the possibility of applying the Recommendation 4.81.7 (06/97) 1 most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. il CCITT Recommendation 1.130 (1988), Method for the characte
24、rization of telecommunication sewices supported by an ISDN and network capabilities of an ISDN. 2 CCITT Recommendation 4.65 (1988), Stage 2 of the method for the characterization of services supported by an ISDN. 3 ITU-T Recommendation 1.1 12 (1993), Vocabulary of terms for ISDNs. 4 ITU-T Recommenda
25、tion 4.7 1 (1 993), ISDN circuit mode switched bearer services. 5 ITU-T Recommendation 2.1 O0 (1 993), CCITT SpeciJication and Description Language (SDL). 6 CCITT Recommendation Q.9 (i 988), Vocabulary of switching and signalling terms. 7 ITU-T Recommendation Z. 120 (1 993), Message sequence chart (
26、MSC). 8 CCITT Recommendation 1.25 1.7 (1 992), Number IdentiJcation supplementary services: Malicious Call Identijkation. 7.3 Definitions This Recommendation defines the following terms: - - Integrated Services Digital Network (ISDN): see 2.3h.112 3, definition 308. Service; telecommunications servi
27、ce: see 2.2/I. 1 12 3, definition 201. 7.4 Symbols and abbreviations This Recommendation uses the following symbols and abbreviations: CC CCA CLI Calling Line Identity FE Functional Entity FEA Functional Entity Action ISDN Integrated Services Digital Network LE Local Exchange MCID Malicious Call Ide
28、ntification PNX Private Network Exchange TE Terminal Equipment Call Control, typically a LE Call Control Agent, typically a TE 7.5 Description Not applicable. 2 Recommendation Q.81.7 (06197) - 7.6 Derivation of the functional model 7.6.1 The functional model description The functional model for the
29、MCID supplementary service is shown in Figure 7-1. T11814-96 NOTE 1 - This model recognizes that a PNX (NK!) will require service control functionality (Le. FE2) to be provided by the PNX. For the case where no PNX is involved, e.g. TE directly connected, generally by basic access, neither FE2 nor r
30、elationship rb exists. NOTE 2 - It is assumed that a PNX uses access link clearing procedures independent of the extension clearing procedures. FE2 shall meet the requirements of the stage 1 service description and shall not delay the access throughput. NOTE 3 - FE4 provides CLI, when requested from
31、 FE3. Figure 7-UQ.81.7 7.6.2 The Functional Entities (FES) required by the MCID supplementary service above those of the basic call are as follows: - - - - Description of the functional entities FE1 : MCID agent of the served user; FE2: MCID control of served PNX user; FE3 : MCID control of served u
32、ser; FE4: MCID control of the call originating network entity. Recommendation 4.81.7 (06/97) 3 7.6.3 The relationship to a basic service is shown in Figure 7-2. NOTE - The basic call model is defined in 2.VQ.71 4 with the exception that rl represents an outgoing call relationship from a CCAA and r3
33、represents an incoming call relationship to a CCA. Relationship with a basic service FE5 7 FE7 FET3 T118149O-96 NOTE 1 - For the case where no PNX is involved, e.g. TE directly connected, generally by basic access, neither FEZ nor relationship rb exists NOTE 2 - Information flows between FE4 and FE5
34、 and infomation flows between FE3, FE6 and FE7 are not shown. Figure 7-2/Q.81.7 7.7 Information flows 7.7.1 Information flow diagrams The initiation of functional entity actions at functional entities and the information flow between FES is shown in the following diagrams. 7.7.1.1 See Figure 7-3. En
35、try into the MCID service at FE3 Il FE3 Il SETUP req. 931 i. b 931a 933 934 T1 I4738092 Figure 7-3/Q.81.7 4 Recommendation 4.81.7 (06/97) - 7.7.1.2 Information request towards FE4 upon detection of incomplete SETUP contents for MCID service at FE3 t. . +I req. See Figure 7-4. 934 b 935 341 DISCONNEC
36、T b. 933 req. ra Fa u SETUP req. 241 I. (no CLI) Il 1938 SETUP req. )I. b T11473SU-92 NOTE -Detection of insufficient contents of SETUP for MCID service will prevent basic call from being established across the access until INFORM 3 resp. received or timer Tmcid.2 expire. Timer Tmcid.2 expiry will r
37、esult in call clearing. Timer Tmcid.2 is equivalent to the appropriate network timer T33. Figure 7-4/Q.81.7 7.7.1.3 Functions of FE3 when calling party clears before the served user invokes the MCID service See Figure 7-5. RELEASE 341 I I I T1147400-92 Figure 7-9Q.81.7 Recommendation 4.81.7 (06/97)
38、5 7.7.1.4 See Figure 7-6. Invocation of the MCID supplementary service (directly connected served user) C 91 1 MCID req. 912 I I I MCID req. 1 F FE3 935 933 939 930 - . I I CC MCiD conf. d I914 I MCIDconf. T1147410-92 II NOTE -Depending upon the implementation and the capabilities of the signalling
39、system used, the MCiD supplementary service information may also be printed out at the originating local exchange. Figure 7-6/Q.81.7 7.7.1.5 See Figure 7-7. Invocation of the MCID supplementary service (served user is PNX extension) rb IFEz(.rl. MCID req. MCiD resp. T1147420-92 NOTE -Depending upon
40、the implementation and the capabilities of the signalling system used, the MCID supplementary service information may also be printed out at the originating local exchange. Figure 7-7/Q.81.7 6 Recommendation Q.81.7 (06197) STD-ITU-T RECMN Q-81-7-ENGL 1997 48b259L Ob41020 725 7.7.1.6 Functions of FE2
41、 when calling party clears before served user (PNX extension) invokes the MCID service See Figure 7-8. 341 DISCONNECT . b req. 926 341 RELEASE 341 I. req. 332 RELEASE - ToMCiDFE MFORM 3 T118159M3 (-) Figure 7-20/Q.81.7 - FE4 7.9 Functional Entity Actions (FEAs) The following functional entity action
42、s shall be associated with each FE. 7.9.1 FEAs of FE1 9 1 1 : 9 12: 913: 914: 9 15 : receive the user MCID invoke instructions and respond 9 12. transmit MCID req. towards network. receive MCID resp. from FE2 or FE3 and respond 914. indicate to the user confirmation of successful MCID invocation. re
43、ceive MCID MCID FAILURE INDICATION req. and indicate rejection to user. 7.9.2 FEAs ofFE2 921 : detect a clearing request from network (e.g. RELEASE request or DISCONNECT request from the network) and respond 922,926. I 922: 923: start timer Tmcid.1 (equivalent to network timer T305 or T306). detecti
44、on of MCID req. fi-om FE1 and respond 924. Recommendation Q.81.7 (06/97) 19 STD-ITU-T RECMN Q-BL.7-ENGL 1997 iBb259L Obll1033 383 = 924: 925: 926: 927: 928: 929: NOTE - FE2 need not be present when this service is provided to a TE connected via the “T“ reference point only (i.e. no NT2 or “S“ refere
45、nce point). transmit MCID req. to FE3. detect called party clear request, respond 929, stop timer Tmcid.1 (if running), basic call FEA 342, i.e. normal clearing. delay response of clearing protocol (e.g. delay RELEASE COMPLETE or RELEASE) respond 923 (until expiry of Tmcid.1 then basic call FEA 341,
46、 i.e. normal clearing) and 925. detect MCID resp. and respond 928. transmit MCID resp. to FEI. transmit Called PARTY CLEAR INF. towards FE3. 7.9.3 FEAs ofFE3 93 1 : detect presence or absence of CLI information (basic call FEA 241a) and respond 93 la or 93 1 b. store CLI information as MCID informat
47、ion and respond 93A, 934,933. transmit INFORM 3 req. towards FE4,937,932 requesting CLI information if MCID is subscribed (optional in every case). receive INFORM 3 resp. from FE4, respond 931a and stop Tmcid.2. detect MCID req. and respond 930 and 939. detect calling party clear before MCID req. re
48、ceived from user and respond 935, optionally: respond 930 (automatic invocation). start timer Tmcid. 1 and retain MCID information within store for time period Tmcid. 1, respond 933 (expiry of Tmcid.1 shall result in 936). start timer Tmcid.2 (expiry of timer Tmcid.2 shall result in call clearing).
49、93 la: 93 1 b: 932: 933: 934: 93 5: 937: 938: stop timer Tmcid.2. 939: stop timer Tmcid.1. 930: 930a: 93A: 93B: printout: all stored MCID information and respond 930a. transmit MCID resp. to FE2 or FE1. receive “Alerting received flag = l“, respond 93B. detect “Calling Party cleared flag = 1“ after “Alerting received flag = l“, respond 934. 7.9.4 FEAs ofFE4 941: 942: 943 : receive INFORM 3 (MCID ENCOUNTERED req.) from FE3 and respond 942. gather (short-term store) all available calling party identity information an
