Commit f65fca54 authored by canterburym's avatar canterburym
Browse files

TS 33108 v7.3.0 (2005-12-19) agreed at SA#30

parent ac1dd6a6
UMTS-HI3CircuitLIOperations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3CS(4) r6(6) version2(2)}
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3CS(4) r7(7) version0(0)}
DEFINITIONS IMPLICIT TAGS ::=
......@@ -23,12 +22,12 @@ IMPORTS OPERATION,
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2)
lawfulIntercept(2) hi2(1) version7(7)} -- Imported from TS 101 671v2.11.1
lawfulIntercept(2) hi2(1) version9(9)} -- Imported from TS 101 671v2.13.1
SMS-report
FROM UmtsHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2)
threeGPP(4) hi2(1) version-2(2)};
threeGPP(4) hi2(1) r7(7) version-2(2)};
-- Object Identifier Definitions
......@@ -38,7 +37,7 @@ lawfulInterceptDomainId OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(
-- Security Subdomains
threeGPPSUBDomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId threeGPP(4)}
hi3CSDomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi3CS(4) r6(6) version-2(2)}
hi3CSDomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi3CS(4) r7(7) version-0(0)}
uMTS-circuit-Call-related-Services OPERATION ::=
{
......@@ -69,8 +68,15 @@ UMTS-Content-Report ::= SEQUENCE
version [23] ENUMERATED
{
version1(1),
...
... ,
-- versions 2-7 were omitted to align with UmtsHI2Operations.
version8(8)
} OPTIONAL,
-- Optional parameter "version" (tag 23) became redundant starting from
-- 33.108v6.8.0, where the object identifier "hi3CSDomainId" was introduced into
-- "UMTS-Content-Report". In order to keep backward compatibility, even when the
-- version of the "hi3CSDomainId" parameter will be incremented it is recommended to
-- always send to LEMF the same: enumeration value "lastVersion(8)".
lawfulInterceptionIdentifier [6] LawfulInterceptionIdentifier OPTIONAL,
communicationIdentifier [1] CommunicationIdentifier,
-- Used to uniquely identify an intercepted call: the same as used for the relevant IRI.
......
Umts-HI3-PS {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3(2) r6(6) version-3(3)}
Umts-HI3-PS {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi3(2) r7(7) version-0(0)}
DEFINITIONS IMPLICIT TAGS ::=
......@@ -8,13 +8,13 @@ IMPORTS
GPRSCorrelationNumber
FROM UmtsHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi2(1) r6(6) version-6(6)} -- Imported from TS 33.108v6.8.0
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi2(1) r7(7) version-2(2)} -- Imported from TS 33.108v7.2.0
LawfulInterceptionIdentifier,
TimeStamp
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version7(7)}; -- from ETSI HI2Operations TS 101 671v2.11.1
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulIntercept(2) hi2(1) version9(9)}; -- from ETSI HI2Operations TS 101 671v2.13.1
-- Object Identifier Definitions
......@@ -24,7 +24,7 @@ securityDomain(2) lawfulIntercept(2)}
-- Security Subdomains
threeGPPSUBDomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId threeGPP(4)}
hi3DomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi3(2) r6(6) version-3(3)}
hi3DomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi3(2) r7(7) version-0(0)}
CC-PDU ::= SEQUENCE
{
......@@ -53,7 +53,14 @@ Version ::= ENUMERATED
{
version1(1),
...,
version3(3)
version3(3) ,
-- versions 4-7 were omitted to align with UmtsHI2Operations.
lastVersion(8)
-- Mandatory parameter "version" (tag 1) was always redundant in 33.108, because
-- the object identifier "hi3DomainId" was introduced into "ULIC-headerV in the initial
-- version of 33.108v5.0.0 In order to keep backward compatibility, even when the
-- version of the "hi3DomainId" parameter will be incremented it is recommended to
-- always send to LEMF the same: enumeration value "lastVersion(8)".
}
TPDU-direction ::= ENUMERATED
......
UmtsCS-HI2Operations
{ itu-t (0) identified-organization (4) etsi (0) securityDomain (2) lawfulIntercept (2) threeGPP(4) hi2CS (3) r6(6) version-3 (3)}
{itu-t (0) identified-organization (4) etsi (0) securityDomain (2) lawfulIntercept (2) threeGPP(4) hi2CS (3) r7(7) version-0 (0)}
DEFINITIONS IMPLICIT TAGS ::=
......@@ -18,19 +18,19 @@ IMPORTS OPERATION,
CommunicationIdentifier,
CC-Link-Identifier,
National-Parameters,
National-HI2-ASN1parameters,
National-HI2-ASN1parameters
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2)
lawfulIntercept(2) hi2(1) version7(7)} -- Imported from TS 101 671v2.11.1
lawfulIntercept(2) hi2(1) version9(9)} -- Imported from TS 101 671v2.13.1
Location,
SMS-report
FROM UmtsHI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2)
lawfulintercept(2) threeGPP(4) hi2(1) r6(6) version-6(6)};
-- Imported from TS 33.108v6.8.0
lawfulintercept(2) threeGPP(4) hi2(1) r7(7) version-2(2)};
-- Imported from TS 33.108v7.2.0
-- Object Identifier Definitions
......@@ -41,14 +41,14 @@ securityDomain(2) lawfulIntercept(2)}
-- Security Subdomains
threeGPPSUBDomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId threeGPP(4)}
hi2CSDomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi2CS(3) r6(6) version-3(3)}
hi2CSDomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi2CS(3) r7(7) version-0(0)}
umtsCS-sending-of-IRI OPERATION ::=
{
ARGUMENT UmtsCS-IRIsContent
ERRORS { OperationErrors }
CODE global:{ threeGPPSUBDomainID hi2CS(3) opcode(1)}
CODE global:{ threeGPPSUBDomainId hi2CS(3) opcode(1)}
}
-- Class 2 operation. The timer shall be set to a value between 3 s and 240 s.
-- The timer.default value is 60s.
......@@ -103,8 +103,15 @@ IRI-Parameters ::= SEQUENCE
version1(1),
...,
version2(2),
version3(3)
version3(3),
-- versions 4-7 were ommited to align with UmtsHI2Operations.
lastVersion(8)
} OPTIONAL,
-- Optional parameter "iRIversion" (tag 23) was always redundant in 33.108, because
-- the object identifier "hi2CSDomainId" was introduced into "IRI Parameters" with the
-- initial HI2 CS domain module in 33.108v6.1.0. In order to keep backward compatibility,
-- even when the version of the "hi2CSDomainId" 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.
......@@ -177,7 +184,7 @@ IRI-Parameters ::= SEQUENCE
-- in case of multiparty calls.
national-Parameters [16] National-Parameters OPTIONAL,
...,
umts-Cs-Event [33] Umts-Cs-Event OPTIONAL
umts-Cs-Event [33] Umts-Cs-Event OPTIONAL,
-- Care should be taken to ensure additional parameter numbering does not conflict with
-- ETSI TS 101 671 or Annex B.3 of this document (PS HI2).
national-HI2-ASN1parameters [255] National-HI2-ASN1parameters OPTIONAL
......
UmtsHI2Operations {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi2(1) r7(7) version-1(1)}
UmtsHI2Operations {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi2(1) r7(7) version-2(2)}
DEFINITIONS IMPLICIT TAGS ::=
......@@ -23,7 +23,7 @@ IMPORTS
FROM HI2Operations
{itu-t(0) identified-organization(4) etsi(0) securityDomain(2)
lawfulIntercept(2) hi2(1) version5(5)}; -- Imported from TS 101 671
lawfulIntercept(2) hi2(1) version9(9)}; -- Imported from TS 101 671v2.13.1
-- Object Identifier Definitions
......@@ -34,7 +34,7 @@ securityDomain(2) lawfulIntercept(2)}
-- Security Subdomains
threeGPPSUBDomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId threeGPP(4)}
hi2DomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi2(1) r7(7) version-1(1)}
hi2DomainId OBJECT IDENTIFIER ::= {threeGPPSUBDomainId hi2(1) r7(7) version-2(2)}
umts-sending-of-IRI OPERATION ::=
{
......@@ -86,7 +86,7 @@ OperationErrors ERROR ::=
}
-- This values may be sent by the LEMF, when an operation or a parameter is misunderstood.
-- Parameters having the same tag numbers must be identical in Rel-5 and Rel-6 modules.
-- Parameters having the same tag numbers must be identical in Rel-5 and onwards modules.
IRI-Parameters ::= SEQUENCE
{
hi2DomainId [0] OBJECT IDENTIFIER, -- 3GPP HI2 domain
......@@ -98,8 +98,14 @@ IRI-Parameters ::= SEQUENCE
version4 (4),
-- note that version5 (5) cannot be used as it was missed in the version 5 of this
-- ASN.1 module.
version6 (6)
} OPTIONAL,
version6 (6),
-- vesion7(7) was ommited to align with ETSI TS 101 671.
lastVersion (8) } OPTIONAL,
-- Optional parameter "iRIversion" (tag 23) was always redundant in 33.108, because
-- the object identifier "hi2DomainId" was introduced into "IRI Parameters" in the
-- initial version of 33.108v5.0.0. In order to keep backward compatibility, even when
-- the version of the "hi2DomainId" 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.
......@@ -148,13 +154,13 @@ IRI-Parameters ::= SEQUENCE
servingSGSN-address [32] OCTET STRING (SIZE (5..17)) OPTIONAL,
-- Octets are coded according to 3GPP TS 23.003 [25]
...,
-- Tag [33] was taken into use by ETSI module in TS 101 671v2.12.1
-- Tag [33] was taken into use by ETSI module in TS 101 671v2.13.1
ldiEvent [34] LDIevent OPTIONAL,
correlation [35] CorrelationValues OPTIONAL,
national-HI2-ASN1parameters [255] National-HI2-ASN1parameters OPTIONAL
}
-- Parameters having the same tag numbers must be identical in Rel-5 and Rel-6 modules
-- Parameters having the same tag numbers must be identical in Rel-5 and onwards modules
-- PARAMETERS FORMATS
......@@ -369,7 +375,8 @@ GPRSEvent ::= ENUMERATED
sMS (11),
pDPContextModification (13),
servingSystem (14),
...
... ,
startOfInterceptionWithMSAttached (15)
}
-- see [19]
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment