TS 33108 v6.0.0 (2002-12-18) agreed at SA#18

33108/r6/UmtsHI2Operations.asn

-UmtsHI2Operations {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi2(1) version-1(1)} 
+UmtsHI2Operations {itu-t(0) identified-organization(4) etsi(0) securityDomain(2) lawfulintercept(2) threeGPP(4) hi2(1) version-2(2)} 
 
 DEFINITIONS IMPLICIT TAGS ::=
 
@@ -33,11 +33,11 @@ securityDomain(2) lawfulIntercept(2)}
 
 -- Security Subdomains
 threeGPPSUBDomainId OBJECT IDENTIFIER ::= {lawfulInterceptDomainId threeGPP(4)}
-hi2DomainId OBJECT IDENTIFIER	::= {threeGPPSUBDomainId hi2(1) version-1(1)}
+hi2DomainId OBJECT IDENTIFIER	::= {threeGPPSUBDomainId hi2(1) version-2(2)}
 
 umts-sending-of-IRI  OPERATION ::= 
 {
-	ARGUMENT	UmtsIRIContent
+	ARGUMENT	UmtsIRIFileContent
 	ERRORS		{ OperationErrors }
 	CODE		global:{threeGPPSUBDomainId hi2(1) opcode(1)}
 }
@@ -45,6 +45,24 @@ umts-sending-of-IRI  OPERATION ::=
 -- The timer.default value is 60s.
 -- NOTE:	The same note as for HI management operation applies.
 
+UmtsIRIFileContent		::= CHOICE
+{
+	umtsiRIContent			UmtsIRIContent,
+	umtsIRIFile				UmtsIRIFile
+}
+
+UmtsIRIFile		::= SEQUENCE OF UmtsIRIContent
+
+-- Aggregation of UmtsIRIContent 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 not withheld in the DF or MF in order to
+-- apply aggragation.
+-- When aggregation is not to be applied,  
+-- UmtsIRIContent needs to be chosen.
+
+
 UmtsIRIContent		::= CHOICE 
 {
 	iRI-Begin-record		[1] IRI-Parameters,	-- include at least one optional parameter