Rządowy projekt ustawy o zmianie ustawy - Prawo telekomunikacyjne oraz niektórych innych ustaw

...
-- In case a given country wants to use additional national parameters according to its
law,
-- these national parameters should be defined using the ASN.1 syntax and added after
the
-- extension marker (...).
-- It is recommended that "version parameter" and "vendor identification parameter" are
-- included in the national parameters definition. Vendor identifications can be
-- retrieved from the IANA web site (see annex H). Besides, it is recommended to avoid
-- using tags from 240 to 255 in a formal type definition.
}

UmtsQos ::= CHOICE
{
qosMobileRadio [1] OCTET STRING,
-- The qosMobileRadio parameter shall be coded in accordance with the § 10.5.6.5 of
-- document [9] without the Quality of service IEI and Length of
-- quality of service IE (. That is, first
-- two octets carrying 'Quality of service IEI' and 'Length of quality of service
-- IE' shall be excluded).

qosGn [2] OCTET STRING
-- qosGn parameter shall be coded in accordance with § 7.7.34 of document [17]
}

IMSevent ::= ENUMERATED
{
unfilteredSIPmessage (1),
-- This value indicates to LEMF that the whole SIP message is sent.
...,
sIPheaderOnly (2)
-- If warrant requires only IRI then specific content in a 'sIPMessage'
-- (e.g. 'Message', etc.) has been deleted before sending it to LEMF.
}

LDIevent ::= ENUMERATED
{
targetEntersIA (1),
targetLeavesIA (2),
...
}

CorrelationValues ::= CHOICE
{
iri-to-CC [0] IRI-to-CC-Correlation,
-- correlates IRI to Content(s)

2
7
iri-to-iri [1] IRI-to-IRI-Correlation,
-- correlates IRI to IRI
both-IRI-CC [2] SEQUENCE
{
-- correlates IRI to IRI and IRI to Content(s)
iri-CC [0] IRI-to-CC-Correlation,
iri-IRI [1] IRI-to-IRI-Correlation
}
}

IRI-to-CC-Correlation ::= SEQUENCE
{
-- correlates IRI to Content
cc [0] SET OF OCTET STRING,
-- correlates IRI to multiple CCs


iri [1] OCTET STRING OPTIONAL
-- correlates IRI to CC with signaling
}

IRI-to-IRI-Correlation ::= OCTET STRING
-- correlates IRI to IRI


END -- of HI2Operations
CS, PS


HI2Operations {itu-t(0) identified-organization(4) etsi(0) securityDomain(2)
lawfulIntercept(2) hi2(1) version9(9)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN

-- =============================
-- Object Identifier Definitions
-- =============================

-- LawfulIntercept DomainId
lawfulInterceptDomainId OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4)
etsi(0)
securityDomain(2) lawfulIntercept(2)}

-- Security Subdomains
hi2DomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId hi2(1)}

2
8
hi2OperationId OBJECT IDENTIFIER ::= {hi2DomainId version9(9)}

IRIsContent ::= CHOICE
{
iRIContent IRIContent,
iRISequence IRISequence -- NOT USED
}

IRISequence ::= SEQUENCE OF IRIContent -- NOT USED
-- Aggregation of IRIContent is an optional feature.
-- It may be applied in cases when at a given point in time several IRI records are
-- available for delivery to the same LEA destination.
-- As a general rule, records created at any event shall be sent immediately and shall
-- not held in the DF or MF in order to apply aggregation.
-- When aggregation is not to be applied, IRIContent needs to be chosen.

IRIContent ::= CHOICE
{
iRI-Begin-record [1] IRI-Parameters,
-- At least one optional parameter must be included within the iRI-Begin-Record.
iRI-End-record [2] IRI-Parameters,
iRI-Continue-record [3] IRI-Parameters,
-- At least one optional parameter must be included within the iRI-Continue-Record.
iRI-Report-record [4] IRI-Parameters,
-- At least one optional parameter must be included within the iRI-Report-Record.
...
}

IRI-Parameters ::= SEQUENCE
{
domainID [0] OBJECT IDENTIFIER (hi2OperationId) OPTIONAL,
-- for the sending entity the inclusion of the Object Identifier is mandatory
iRIversion [23] ENUMERATED
{
version2(2),
...,
version3(3),
version4(4),
version5(5),
version6(6),
version7(7),
lastVersion(8)
} OPTIONAL,
-- Optional parameter "iRIversion" (tag 23) is redundant starting from TS 101 671
v2.4.1
-- where to the object identifier "domainID" was introduced into IRI-Parameters.

2
9
-- In order to keep backward compatibility, even when the version of the "domainID"
-- parameter will be incremented it is recommended to always send to LEMF the same:
-- enumeration value "lastVersion(8)".
-- if not present, it means version 1 is handled

lawfulInterceptionIdentifier [1] LawfulInterceptionIdentifier,
-- This identifier is associated to the target.

communicationIdentifier [2] CommunicationIdentifier,
-- used to uniquely identify an intercepted call.
-- Called "callIdentifier" in Edition 1 of ES 201 671.

timeStamp [3] TimeStamp,
-- date and time of the event triggering the report.

intercepted-Call-Direct [4] ENUMERATED
{
not-Available(0),
originating-Target(1),
-- In case of GPRS, this indicates that the PDP context activation, modification
-- or deactivation is MS requested.
terminating-Target(2),
-- In case of GPRS, this indicates that the PDP context activation, modification
-- or deactivation is network initiated.
...
} OPTIONAL,

intercepted-Call-State [5] Intercepted-Call-State OPTIONAL,

ringingDuration [6] OCTET STRING (SIZE (3)) OPTIONAL, -- NOT USED
-- Duration in seconds. BCD coded : HHMMSS

conversationDuration [7] OCTET STRING (SIZE (3)) OPTIONAL, -- NOT USED
-- Duration in seconds. BCD coded : HHMMSS

locationOfTheTarget [8] Location OPTIONAL,
-- location of the target subscriber

partyInformation [9] SET SIZE (1..10) OF PartyInformation OPTIONAL,
-- This parameter provides the concerned party (Originating, Terminating or forwarded
-- party), the identity(ies) of the party and all the information provided by the
party.

callContentLinkInformation [10] SEQUENCE
{
cCLink1Characteristics [1] CallContentLinkCharacteristics OPTIONAL,

3
0
-- Information concerning the Content of Communication Link Tx channel established
-- toward the LEMF (or the sum signal channel, in case of mono mode).

cCLink2Characteristics [2] CallContentLinkCharacteristics OPTIONAL,
-- Information concerning the Content of Communication Link Rx channel established
-- toward the LEMF.
...
} OPTIONAL, -- NOT USED

release-Reason-Of-Intercepted-Call [11] OCTET STRING (SIZE (2)) OPTIONAL,
-- Release cause coded in ITU-T Q.850 [31] format.
-- This parameter indicates the reason why the intercepted call cannot be established
or
-- why the intercepted call has been released after the active phase.

nature-Of-The-intercepted-call [12] ENUMERATED
{
-- Nature of the intercepted "call":
gSM-ISDN-PSTN-circuit-call(0),
-- the possible UUS content is sent through the HI2 or HI3 "data" interface
-- the possible call content call is established through the HI3 "circuit" interface
gSM-SMS-Message(1),
-- the SMS content is sent through the HI2 or HI3 "data" interface
uUS4-Messages(2),
-- the UUS content is sent through the HI2 or HI3 "data" interface
tETRA-circuit-call(3),
-- the possible call content call is established through the HI3 "circuit" interface
-- the possible data are sent through the HI3 "data" interface
teTRA-Packet-Data(4),
-- the data are sent through the HI3 "data" interface
gPRS-Packet-Data(5),
-- the data are sent through the HI3 "data" interface
...,
uMTS-circuit-call(6)
-- the possible call content call is established through the HI3 "circuit" interface
-- the possible data are sent through the HI3 "data" interface
} OPTIONAL,

serverCenterAddress [13] PartyInformation OPTIONAL,
-- e.g. in case of SMS message this parameter provides the address of the relevant
-- server within the calling (if server is originating) or called
-- (if server is terminating) party address parameters

sMS [14] SMS-report OPTIONAL,
-- this parameter provides the SMS content and associated information


3
1