1、ETSI TR 102 053 1.1.1 (2002-03) Technical Repor Telecom m u ni cat ions secu ri ty ; Lawful Interception (LI); Notes on ISDN lawful interception functionality 2 ETSI TR 102 053 VI .I .I (2002-03) Reference DTR/SEC-003016 Keywords ISDN, lawful interception, security ETSI 650 Route des Lucioles F-O692
2、1 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:l/w.etsi
3、 .orq The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on
4、 ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at 3 If you find
5、 errors in the present document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 2002. All rights r
6、eserved. ETSI 3 ETSI TR 102 053 VI . 1 . 1 (2002-03) Contents Intellectual Property Rights 5 Foreword . 5 1 Scope 6 2 References 6 3 Definitions and abbreviations . 6 Definitions 6 3.1 3.2 Abbreviations . 6 4 Introduction 6 5 Typical message sequence diagrams for IR1 7 5.1 5.2 5.3 5.4 5.4.1 5.4.2 5.
7、4.3 5.4.4 5.4.5 5.5 5.5.1 5.5.2 5.5.3 5.6 5.6.1 5.7 5.7.1 5.7.2 5.7.3 5.8 5.8.1 5.8.2 5.9 5.9.1 5.9.2 5.9.3 5.9.4 5.9.5 5.10 5.10.1 5.10.2 5.10.3 5.10.4 5.10.5 5.10.6 5.10.7 5.10.8 5.10.9 5.11 5.12 5.13 5.13.1 5.13.2 5.14 General remarks . 7 Remarks to tables . 8 Remarks to scenarios 8 Originating t
8、arget. basic call . 9 Initial LI procedures 9 Set up of an additional call leg 11 IRI-CONTINUE records (general) . 11 Answer by other party . 11 Call release (originating or terminating target) . 12 Temnating target, basic call . 14 Initial LI procedure . 14 Answer by target . 16 Call release 16 Ori
9、ginating target call, invocation of LI relevant services . 16 Call forwarded by called party 16 18 18 21 21 . Terminating target call. invocation of LI relevant services Terminating call at target is a forwarded call Call forwarded by target 18 Call HOLD by target 22 Call RETRIEVE by targ 22 Target
10、actions during a call in progres Three Party Service (3PTY) 23 Target establishes Three 23 24 Target: Private communication with Active-Held p 24 Release of 3 PTY conference by Active-Held party . 25 Release of 3 PTY conference by Active-Idle party 25 Add on conference (CONF) . 25 Mapping of PartyId
11、ConferenceId to Communication Identifiers 26 Beginning a conference from the Idle call state 26 Beginning a conference from the Active call state . 27 Adding a remote user 28 Splitting a remote user 29 Further actions during a conference 30 Target clears the conference . 31 Option B (CC link only fo
12、r active call) . 31 Add on conference using other protocols . 31 Target exchange receives notification related to other party 32 Service activation (not call related) 32 Service activatiodinvocation during a call 32 ISDN accesses 32 Analogue accesses 33 Unsuccessful calls from target (originating),
13、IRI-BEGIN record sent . 33 ETSI 4 ETSI TR 102 053 VI . 1 . 1 (2002-03) 5.15 6 State model for an ISDN (overview description for CC link and IR1 delivery) . 35 Annex A: Bibliography 38 Unsuccessful calls frodto target. IRI-BEGIN record not sent 34 History 39 ETSI 5 ETSI TR 102 053 VI .I .I (2002-03)
14、Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR O00 314: “Intellectual Property
15、 Rights (7PRs); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried o
16、ut by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee
17、 Security (SEC). ETSI 6 ETSI TR 102 053 VI .I .I (2002-03) 1 Scope The present document republishes information previously available in ES 20 1 671 11 version 1.1.1, which is considered to be valuable, but which it was not appropriate to retain in future versions of ES 20 1 67 1 i. The present docum
18、ent gives detailed guidance on network functionality, beyond that provided in i, on lawful interception as it applies to an ISDN. The handover interface remains as specified in i. The material is expected to be of particular use to: - manufacturers; - network operators; - Law Enforcement Agencies; -
19、 others who are concerned with the specification and implementation of lawful interception as it concerns an ISDN. 2 Re fe re nces For the purposes of this Technical Report (TR) the following references apply: il ETSI ES 201 671 (V2.1.1): “Telecommunications security; Lawful Interception (LI); Hando
20、ver interface for the lawful interception of telecommunications traffic“. 3 Definitions and abbreviations 3.1 De fi nit ions For the purposes of the present document, the terms and definitions given in ES 201 671 i apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations
21、defiied in ES 20 1 67 1 11 apply. 4 I n t rod uct ion The present document supplements ES 201 671 i in its application to an ISDN. ES 201 671 i describes H12: IR1 for circuit switching, H13: CC for circuit switching, general procedures for circuit switched supplementary services and detailed procedu
22、res for circuit switched supplementary services in the annex “Circuit switched handover“. ETSI 7 ETSI TR 102 053 VI .I .I (2002-03) 5 Typical message sequence diagrams for IR1 5.1 General remarks The tables and message sequence diagrams (scenarios) of this clause are typical examples showing which p
23、arameters shall be included in the IRI records, and when the records shall be sent out to the LEA, for different call phases, call configurations and the invocation of supplementary services. The purpose of this clause is to supplement and clarisl the procedures and the use of parameters which are s
24、pecified in the main body and the normative annexes of ES 201 671 i. These normative parts have precedence in case of ambiguities. A general principle for handling complex call configurations is to break down the scenarios for LI related tasks into several sub-scenarios, which are ideally identical
25、for parts of basic calls or other “standard“ call situations. This reduces significantly the complexity of specisling and realizing the LI related tasks. As a consequence, the scenarios below contain in many cases just a remark to another scenario with the applicable sequence, see example below. EXA
26、MPLE: Call Forwarding on No Reply (CFNR) is active for a target (party B). 1) An incoming call is, after a time-out, released at the targets access, but forwarded by the exchange. The sequence up to the release is handled similarly to a call released by B during ringing. 2) The following set up of t
27、he forwarded call to a party C is handled in the same way as for immediate forwarding, for example CFU. Both transactions can be treated independently of each other. A new specific sequence for CFNR is not needed. The tables and scenarios of this clause contain several typical cases. They do not cov
28、er all possible combinations, and are structured into clauses as follows: Basic calls 5.4 Originating target, basic call 5.5 Terminating target, basic call Call with ISDN supplementary services being invoked 5.6 5.7 5.8 5.9 Three Party Service (3PTY) 5.1 O Add on conference (CONF) 5.11 Target exchan
29、ge receives notification related to other party Originating target call, invocation of LI relevant services Terminating target call, invocation of LI relevant services Target actions during a call in progress Subscriber Controlled Input (SCI) 5.12 5.13 Service activation (not call related) Service a
30、ctivatiodinvocation during a call Unsuccessful calls 5.14 5.15 Unsuccessful calls from target (originating), IRI-BEGIN record sent Unsuccessful calls frodto target, IRI-BEGIN record not sent ETSI 8 ETSI TR 102 053 VI .I .I (2002-03) 5.2 Remarks to tables Within the tables, the parameters of an IR1 r
31、ecord which are significant for the specific case are indicated. They depend, except for the mandatory parameters, of the type of a target call. The order of the IR1 parameters is not fixed. The complete set of parameters, which may be part of an IR1 record, is described in ES 201 671 i in annex A “
32、Circuit switched network handover“. The parameter notation uses the ASN.l definitions of ES 201 671 i. Unless otherwise stated, the tables are applicable to all kinds of originating or terminating accesses, such as ISDN and analogue subscribers. Restrictions or differences may be mentioned in the co
33、lumn “remarks“ or within additional text. Mapping of parameters originated from signalling systems other than DSSl or ISUP shall follow existing interworking specifications. Only parameters and signals which are available from the standard signalling procedures shall be included. No additional proce
34、dures need be used for LI to obtain parameters which are not available by default. For example, no request for a missing CLI need be made, even if the signalling system would allow it. Regarding the accuracy of the time stamp value of a record, it may be determined at any point in time during the pe
35、riod between the detection of an event and the sending of the related record. 5.3 Remarks to scenarios The included scenarios are examples. They show successful LI invocations within a local exchange. Exceptional cases are not included. In case of ambiguities, the text of ES 201 671 i shall have pri
36、ority. The indicated call handling messages are, in general, not based on a specific protocol. However, in several cases protocol specific information needs to be mentioned. In these cases, the DSSl functional access protocol is used, because it is a kind of superset standard of protocol features. W
37、ithin the figures such cases are indicated by using DSSl protocol message names in capital letters. Message sequences for other protocols, such as for analogue access, should be derived from the specified sequences. The scenarios do not show all signalling protocol messages. The emphasis is on those
38、 messages which are significant for, or related to, IRI records and CC link events. The IR1 record parameters which are indicated as additional information in the scenarios are limited to significant ones for a given case. For example, parameters which are mandatory such as the LIID, data and time,
39、etc. are not explicitly mentioned. The parameter names use logical names, as described in ES 201 671 i in annex A “Circuit switched network handover“, instead of the exact ASN. 1 notation. It is not required that identical sequences result for the same actions of a target or another party. These seq
40、uences may depend on the actual access or network protocols, and the call configuration, for example purely local calls, or calls via other exchanges. The master configuration chosen for decisions as to which parameters ought to be included in IRI records is transit call switching using ISDN user pa
41、rt signalling. This means, for example, that the information which can be provided by such calls shall also be available in case of purely local calls. As described above, the individual IRI records, which carry certain information, may vary. As a general rule, intercept related information is trans
42、mitted to the LEMF within an IR1 record when it first becomes available. In the scenarios, identical parameters are not repeated in succeeding records, unless their content or value has changed. However, an implementation may decide to repeat information which has already been sent, for example in o
43、rder to avoid the need for a memory of previously sent parameters. With respect to the CC links in case of multi party calls, the option “CC links for active and non-active calls“ is generally shown (option A). In general, the scenario figures contain one or more pictures depicting the actual config
44、uration of the target and the other party, or parties, within a call and the targets call state. ETSI 9 ETSI TR 102 053 VI .I .I (2002-03) Functional entities used within the scenarios: Target terminal: Equipment of the interception subject, which originates or terminates an intercepted call. Orig./
45、tem. SF-T: Switching function of the target, containing the IIF; within these examples, the SF-T is assumed to be a fixed ISDN network local exchange. Orig./tem. SF-P: Switching function of the other party; within these examples, the SF-P is assumed to be a fixed ISDN network local exchange. Other p
46、arty: Equipment of the other party(ies), which originates or terminates a call, in which the target is involved. LEMF HI2 (IRI): LEMF port, receiving IRI. LEMF HI3 (CC): NOTE: LEMF port, receiving the content of communication (CC links). In general an incoming message to any functional entity causes
47、 one or more outgoing messages. In case of several outgoing messages, the order of sending them is purely implementation dependent. The figures do not intend to spec a fixed sequence. 5.4 Originating target, basic call This clause concentrates on the description of basic calls, originated by the tar
48、get. However, the IRI record tables partly depict parameters which can also be used in conjunction with the invocation of supplementary services. 5.4.1 Initial LI procedures This clause includes the procedure until the point in time when the local exchange of the target (SF-T) sends an IRI-BEGIN rec
49、ord, and sets up a CC link. Corresponding transition in state model: Begin, CC Zinkset up (the state model shows the special case of en-bloc signalling). The IRI-BEGIN record constitutes the first record of an originating or terminating call. NOTE: The exact point of sending the IRI-BEGIN record may depend on national regulations, and on the implementation of the IIF. For example, it may be sent immediately when connecting proceed indication (dial tone) or only when starting routing within the SF-T. Irrespective of the point in time of sending the IRI-BEGI
