ATIS 1000042-2012 Support for Lawfully Authorized Electronic Surveillance (LAES) of Advanced Voice over Packet (VoP) Conferencing.pdf

1、 TECHNICAL REPORT ATIS-1000042 SUPPORT FOR LAWFULLY AUTHORIZED ELECTRONIC SURVEILLANCE (LAES) OF ADVANCED VOICE OVER PACKET (VOP) CONFERENCING ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the i

2、nformation, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Servi

3、ces, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North

4、 American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited

5、 by the American National Standards Institute (ANSI). For more information, please visit . Notice of Disclaimer Optional (O) Provided at the discretion of the implementation; or Conditional (C) Required in situations where a condition (defined in the description column of the table) is met. The info

6、rmation to be conveyed by each parameter is identified. Note that both optional and conditional parameters are considered to be OPTIONAL syntactically in the abstract syntax descriptions. The inclusion requirements in this clause take precedence over the abstract syntax definitions. The following ti

7、ming requirements shall apply to the delivery of CII: Each surveillance message shall be sent by the Delivery Function to the Collection Function within eight (8) seconds of receipt by the IAP of the information pertaining to the CII triggering event at least 95% of the time. Each surveillance messa

8、ge shall contain a time-stamp that is within 200 milliseconds from when the CII event triggering the surveillance message was detected. The CaseIdentity and Conference-ID parameters provide correlation of all the CII messages and enable the LEA CF to properly process the encapsulated CC-APDU payload

9、 ATIS-1000042 7 6.1 Conference Focus CII Reporting Capabilities 6.1.1 Conference-Started Message The Conference-Started message reports the start of a Conference. The Conference starts when the first party is joined to the Conference. This event is reported when the first party is joined to the Conf

10、erence. Table 1: Conference-Started Message Parameters Conference-Started Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event. Conference-ID

11、M Identifies the Conference. Used to correlate CII messages for the lawful intercept. Conference-Parties M Identifies parties joined to the Conference. CCAddress C Provide for content interception to identify the delivery address for the Call Content. 6.1.2 Conference-Already-Started Message The Con

12、ference-Already-Started message reports the start of an intercept on an active Conference. A Conference is active if there is at least one party joined to the Conference. This event is reported when an intercept is placed on an active Conference. Table 2: Conference-Already-Started Message Parameter

13、s Conference-Already-Started Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event. Conference-ID M Identifies the Conference. Used to correlat

14、e CII messages for the lawful intercept. Conference-Parties M Identifies parties joined to the Conference. CCAddress C Provide for content interception to identify the delivery address for the Call Content. ATIS-1000042 8 6.1.3 Conference-Stopped Message The Conference-Stopped message reports the en

15、d of a Conference. A Conference ends when the last party leaves the Conference or the Conference is ended by other means (e.g., at the designated stop time of the Conference). This event is reported when the last party leaves a Conference or an active Conference is stopped. Table 3: Conference-Stopp

16、ed Message Parameters Conference-Stopped Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event. Conference-ID M Identifies the Conference. Used

17、 to correlate CII messages for the lawful intercept. 6.1.4 Conference-Party-Invited Message The Conference-Party-Invited message reports when a party (or parties) is invited or referred to the Conference. This event is reported when a party (or parties) is invited or referred to the Conference. Tabl

18、e 4: Conference-Party-Invited Message Parameters Conference-Party-Invited Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event. Conference-ID

19、M Identifies the Conference. Used to correlate CII messages for the lawful intercept. Conference-Parties M Identifies parties invited or referred to the Conference. 6.1.5 Conference-Party-Joined Message The Conference-Party-Joined message reports parties joined to the Conference. It is not necessary

20、 to report parties joined to the Conference if those parties have already been reported by the Conference-Started or Conference-Already-Started message. This event is reported when: A party (or parties) is joined to the Conference; A party drops and rejoins the Conference; A party that was placed on

21、 hold rejoins the Conference (i.e., retrieved from hold); or A party that was not previously reported by the Conference-Started or Conference-Already-Started message joins the Conference. ATIS-1000042 9 Table 5: Conference-Party-Joined Message Parameters Conference-Party-Joined Parameters MOC Descri

22、ptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event. Conference-ID M Identifies the Conference. Used to correlate CII messages for the lawful intercept. Conferenc

23、e-Parties M Identifies parties joined to the Conference. 6.1.6 Conference-Party-Dropped Message The Conference-Party-Dropped message reports parties dropped from the Conference or placed on hold. This event is reported when a party (or parties) is dropped from the Conference, or when a party is plac

24、ed on hold. Table 6: Conference-Party-Dropped Message Parameters Conference-Party-Dropped Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event

25、. Conference-ID M Identifies the Conference. Used to correlate CII messages for the lawful intercept. Conference-Parties-Dropped C Identifies parties dropped from the Conference. Conference-Parties-on-Hold C Identifies parties on hold from the Conference. 6.1.7 Conference-Party-Invitation-Failed Mes

26、sage The Conference-Party-Invitation-Failed message reports when the invitation to a party to the Conference has failed. Table 7: Conference-Party-Invitation-Failed Message Parameters Conference-Party-Dropped Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity

27、 M Identifies the network element containing the IAP. TimeStamp M Identifies the date and time of this Conference event. Conference-ID M Identifies the Conference. Used to correlate CII messages for the lawful intercept. Conference-Party M Identifies the party invited or referred to the Conference.

28、Failure-Reason C Identifies the reason for the failure of the invitation. ATIS-1000042 10 7 LAES Call Content Surveillance Messages While each Conference Party sends the Call Content packets to the Conference Mixer independently, the Telecommunications Service Provider (TSP) shall mix the Call Conte

29、nt of all Conference Parties and send this mixed Call Content to the LEA, when lawfully authorized. The interval to commence transmission of the intercepted Call Content packets from the Conference Mixer IAP towards the CF shall be limited to the computational delay of the IAP. To transfer the inter

30、cepted Call Content packets from the Delivery Function (DF) to the Collection Function (CF), an Application Protocol Data unit (APDU) - called the CCDelivery APDU (CC-APDU) - is used to encapsulate the intercepted Call Content packets. The CC-APDU consists of a CCDelivery Header and a CCDelivery Pay

31、load. The CC Delivery Payload contains the mixed Call Content packet. The CC-APDU is generated when Call Content delivery is authorized and enabled. Delivery of Call Content via CC-APDUs is dependent upon appropriate provisioning of the CC delivery interface. A CC-APDU shall be triggered for each Ca

32、ll Content packet to be delivered. The CC-APDU contains the following parameters: Table 8: CC-APDU Parameters CC-APDU Parameters MOC DescriptionCaseIdentity M Identifies the lawful intercept. IAPSystemIdentity C Identifies the network element containing the IAP. Include when known. Conference-ID M I

33、dentifies the Conference. Used to correlate CC with CII messages for the lawful intercept. Payload M CC-APDU payload (see Figure 3). The CaseIdentity and Conference-ID parameters provide correlation to the CII, enable correlation of the CC-APDUs associated with a media stream, and enable the LEA CF

34、to properly process the encapsulated CC-APDU payload. The CC-APDU payload includes the RTP header and the mixed voice content from all the Conference Parties. The RTP header defines the payload type.55If a non-standard payload type is used, this needs to be negotiated with the LEA. ATIS-1000042 11 F

35、igure 3: CC-APDU Payload 8 Conferencing Abstract Syntax Notation Figure 4: LAES Object Tree 8.1 Conferencing CII Abstract Syntax Module Conferencing-LAES-CII-Abstract-Syntax-Module iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) conferencing(4) cii(0) version-1(0) DEFINITIONS IMPLICIT TAGS :

36、= BEGIN IMPORTS CaseIdentity, TimeStamp FROM Laesp-j-std-025-b iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) j-std-025(0) j-std-025-b(2) version-1(0) - Imports from J-STD-025-B Module CCAddress, IAPSystemIdentity, PartyIdentity FROM T1S1-LAES-VoP-Abstract-Syntax-Module iso(1) member-body

37、(2) us(840) tia(113737) laes(2) t1(1) t1-678(0) cii(0) common (0) version-4(3); - Imports from ATIS-1000678.b.2010 Module conferencing-LAES-CII-Abstract-Syntax-Module-OID OBJECT IDENTIFIER := iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) conferencing(4) cii(0) version-1(0) conferencing-CII

38、-Protocol-Identifier OBJECT IDENTIFIER := conferencing-LAES-CII-Abstract-Syntax-Module-OID ATIS-1000042 12 ConferencingProtocol := SEQUENCE conferencing-CII-Protocol-Identifier 0 OBJECT IDENTIFIER, conferencing-Message 1 Conferencing-Message Conferencing-Message := CHOICE conference-Started 0 Confer

39、ence-Started, conference-Already-Started 1 Conference-Already-Started, conference-Stopped 2 Conference-Stopped, conference-Party-Invited 3 Conference-Party-Invited, conference-Party-Joined 4 Conference-Party-Joined, conference-Party-Dropped 5 Conference-Party-Dropped, conference-Party-Invited-Failed

40、 6 Conference-Party-Invited-Failed, . - Message Definitions Conference-Started := SEQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity, timestamp 2 TimeStamp, conference-ID 3 Conference-ID, conference-Parties 4 SET OF Conference-Party, ccAddress 5 CCAddress OPTIONAL, . Conference-Al

41、ready-Started := SEQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity, timestamp 2 TimeStamp, conference-ID 3 Conference-ID, conference-Parties 4 SET OF Conference-Party, ccAddress 5 CCAddress OPTIONAL, . Conference-Stopped := SEQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPS

42、ystemIdentity, timestamp 2 TimeStamp, conference-ID 3 Conference-ID, . Conference-Party-Invited := SEQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity, timestamp 2 TimeStamp, conference-ID 3 Conference-ID, conference-Parties 4 SET OF Conference-Party, . Conference-Party-Joined := S

43、EQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity, timestamp 2 TimeStamp, conference-ID 3 Conference-ID, conference-Parties 4 SET OF Conference-Party, . ATIS-1000042 13 Conference-Party-Dropped := SEQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity, timestamp 2 T

44、imeStamp, conference-ID 3 Conference-ID, conference-Parties-Dropped 4 SET OF Conference-Party OPTIONAL, conference-Parties-on-Hold 5 SET OF Conference-Party OPTIONAL, . Conference-Party-Invited-Failed := SEQUENCE caseId 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity, timestamp 2 TimeStamp, co

45、nference-ID 3 Conference-ID, conference-Party 4 Conference-Party, failure-reason 5 Failure-Reason OPTIONAL, . - Parameter Definitions Conference-ID := UTF8String Conference-Party := PartyIdentity Failure-Reason := UTF8String END - of Conferencing-LAES-CII-Abstract-Syntax-Module 8.2 Conferencing CC A

46、bstract Syntax Module Conferencing-LAES-CC-Abstract-Syntax-Module iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) conferencing(4) cc(1) version-1(0) DEFINITIONS IMPLICIT TAGS := BEGIN IMPORTS CaseIdentity FROM Laesp-j-std-025-b iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) j-std-

47、025(0) j-std-025-b(2) version-1(0) - Imports from J-STD-025-B Module IAPSystemIdentity FROM T1S1-LAES-VoP-Abstract-Syntax-Module iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) t1-678(0) cii(0) common (0) version-4(3); - Imports from ATIS-1000678.b.2010 Module Conference-ID FROM Conferencing

48、-LAES-CII-Abstract-Syntax-Module iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) conferencing(4) cii(0) version-1(0); conferencing-CC-Protocol-ID OBJECT IDENTIFIER := iso(1) member-body(2) us(840) tia(113737) laes(2) t1(1) conferencing(4) cc(1) version-1(0) Conferencing-CC-APDU := SEQUENCE c

49、onferencing-CC-Protocol-ID 0 OBJECT IDENTIFIER, ATIS-1000042 14 cc-APDU 1 CC-APDU, . CC-APDU := SEQUENCE caseID 0 CaseIdentity, iAPSystemIdentity 1 IAPSystemIdentity OPTIONAL, conference-ID 2 Conference-ID, payload 3 OCTET STRING END - of Conferencing-LAES-CC-Abstract-Syntax-Module ATIS-1000042 15 Annex A (informative) A Conference Manager Reporting o