Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 33.128  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.7…   6…   6.2.2.2A…   6.2.3…   6.2.3.2.7…   6.2.3.3…   6.2.4…   6.3…   6.3.2.2A…   6.3.3…   6.3.3.2…   6.3.3.2.4…   6.3.3.2A…   7…   7.3…   7.3.3…   7.3.3.2.21…   7.3.3.2.42…   7.3.3.2.63…   7.3.4…   7.4…   7.4.3.8…   7.5…   7.6…   7.7…   7.7.4…   7.8…   7.8.4…   7.9…   7.10…   7.10.4…   7.11…   7.12…   7.13…   7.13.3…   7.13.3.4…   7.14…   7.15…   8…   A…   D…   E…   M… 
7.13 RCS  7.13.1 Provisioning over LI_X1  7.13.1.1 General  7.13.1.2 Provisioning of the POIs and TFs in the RCS Server and the POIs in the HTTP Content Server, File Transfer Localization Function and S-CSCF by the LIPF  7.13.1.3 Provisioning of the MDF2  7.13.1.4 Provisioning of the MDF3  7.13.2 Triggering of the IRI-POI and CC-POI in the HTTP Content Server  7.13.2.1 Triggering of the IRI-POI in the HTTP Content Server over LI_T2  7.13.2.1.1 LI_T2 interface Specifics  7.13.2.2 Triggering of the CC-POI in the HTTP Content Server over LI_T3  7.13.2.2.1 LI_T3 interface Specifics 
...

 

7.13  RCS  p. 338

7.13.1  Provisioning over LI_X1  p. 338

7.13.1.1  General  p. 338

If the warrant is for IRI only, the IRI-POI and IRI-TF in the RCS Servers and the IRI-POI in the HTTP Content Server, File Transfer Localization Function and the S-CSCF shall be provisioned in accordance with clause 7.13.1.2.
If the warrant is for IRI and CC, then the IRI-POI, IRI-TF, CC-POI and CC-TF in the RCS Servers defined in clause 7.13.2.1 of TS 33.127 (see RCS definition in GSMA RCC.07 [78]) and the IRI-POI and the CC-POI in the HTTP Content Server, File Transfer Localization Function and S-CSCF shall be provisioned in accordance with clause 7.13.1.2.
In both cases, the MDF2 shall be provisioned in accordance with clause 7.13.1.3, and the MDF3 shall be provisioned in accordance with clause 7.13.1.4.
The POIs in the HTTP Content Server and the File Transfer Localization Function may also be triggered by the TFs in the RCS Server as described in clause 7.13.2.
Up

7.13.1.2  Provisioning of the POIs and TFs in the RCS Server and the POIs in the HTTP Content Server, File Transfer Localization Function and S-CSCF by the LIPF  p. 339

The IRI-POI, CC-POI, IRI-TF and CC-TF present in the RCS Server, the IRI-POI and CC-POI in the HTTP Content Server, and File Transfer Localization Function and the IRI-POI in the S-CSCF, are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POIs and TFs in the RCS Server and the IRI-POIs in the S-CSCF shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used).
  • IMPU.
  • IMPI.
  • IMEI.
  • PEIIMEI.
The POIs in the HTTP Content Server and File Transfer Localization Function shall support the following additional target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used).
  • SIPURI.
  • TELURI.
  • GPSIMSISDN.
  • GPSINAI.
  • IMSI.
  • SUPIIMSI.
  • SUPINAI.
  • Email Address.
Table 7.13.1.2-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI, CC-POI, IRI-TF and CC-TF in the RCS Servers and the IRI-POI and CC-POI in the HTTP Content Server and File Transfer Localization Function and the IRI-POI in S-CSCF.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF. If the CC-TF or IRI-TF is also being tasked for the same interception, the same XID shall be used. The same XID shall be used at the RCS Servers, the S-CSCF and the HTTP Content Server for the same interception.M
TargetIdentifiersOne or more of the target identifiers listed in the paragraphs above.M
DeliveryType Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant. (NOTE: "X2Only" for IRI-POI, IRI-TF and "X3Only" for CC-TF and CC-POI can also be also be used). M
ListOfDIDs Delivery endpoints of LI_X2 or LI_X3. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.M
ListOfServiceTypes Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7] clause 6.2.1.2, Table 4.C
Up

7.13.1.3  Provisioning of the MDF2  p. 339

The MDF2 listed as the delivery endpoint for xIRI generated by the IRI-POI in the RCS Servers, the IRI-POI in the HTTP Content Server, the IRI-POI in the File Transfer Localization Function, or the IRI-POI in the S-CSCF shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 7.13.1.3-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2.
The MDF2 shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • IMPU.
  • IMPI.
  • IMEI.
  • GPSIMSISDN.
  • GPSINAI.
  • IMSI.
  • SUPIIMSI.
  • SUPINAI.
  • Email Address.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDSame XID used by the LIPF for provisioning the LI functions of the RCS Servers, the S-CSCF and the HTTP Content Servers for this intercept.M
TargetIdentifiersOne or more of the target identifiers listed in the paragraph above.M
DeliveryType Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant. (Ignored by the MDF2). M
ListOfDIDs Delivery endpoints of LI_HI2. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.M
ListOfMediationDetails Sequence of Mediation Details, see Table 7.13.1.3-2.M
ETSI TS 103 221-1 [7] field name Description M/C/O
LIIDLawful Intercept ID associated with the task.M
DeliveryType Set to "HI2Only". M
ListOfDIDsDetails of where to send the IRI for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.C
ServiceScoping Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of subparameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7] Annex C Table C.2.C
Up

7.13.1.4  Provisioning of the MDF3  p. 340

The MDF3 listed as the delivery endpoint for the xCC generated by the CC-POI in the RCS Servers, the CC-POI in the HTTP Content Servers and the CC-POI in the File Transfer Localization Function shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 7.13.1.4-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF3.
The MDF3 shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • IMPU.
  • IMPI.
  • IMEI.
  • GPSIMSISDN.
  • GPSINAI.
  • IMSI.
  • SUPIIMSI.
  • SUPINAI.
  • EmailAddress.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDSame XID used by the LIPF for provisioning the POIs, TFs of the RCS Servers and the POIs of the HTTP Content Servers and the S-CSCF.M
TargetIdentifiersOne or more of the target identifiers listed in the paragraph above.M
DeliveryType Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant (Ignored by the MDF3). M
ListOfDIDs Delivery endpoints of LI_HI3 or LI_MDF. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.M
ListOfMediationDetails Sequence of Mediation Details, see Table 7.13.1.4-2.M
ETSI TS 103 221-1 [7] field name Description M/C/O
LIIDLawful Intercept ID associated with the task.M
DeliveryType Set to "HI3Only". M
ListOfDIDsDetails of where to send the CC for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.C
ServiceScoping Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of subparameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7] Annex C Table C.2.C
Up

7.13.2  Triggering of the IRI-POI and CC-POI in the HTTP Content Server  p. 341

7.13.2.1  Triggering of the IRI-POI in the HTTP Content Server over LI_T2  p. 341

7.13.2.1.1  LI_T2 interface Specifics  p. 341
In order to allow the IRI-POI in the HTTP content server to detect all events related to files uploaded or downloaded by a target, the IRI-TF in the RCS Server sends a trigger to the IRI-POI present in the HTTP Content Server with the necessary information over the LI_T2 interface.
When the IRI-TF in the RCS Server detects that a file is being uploaded or downloaded by a target UE it shall send an activation message to the IRI-POI in the HTTP Content Server over the LI_T2 interface. The activation message shall contain the correlation identifiers that the IRI-POI in the HTTP Content Server shall use with the xIRI. This can be achieved by sending an ActivateTask message as defined in ETSI TS 103 221-1 [7] clause 6.2.1 with the following details.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID Allocated by the IRI-TF as per ETSI TS 103 221-1 [7].M
TargetIdentifiers File detection criteria as determined by the IRI-TF in the RCS Server, which enables the IRI-POI in the HTTP Content Server to isolate target files. The IRI-POI in the HTTP Content Server shall support the identifier types given in Table 7.13.2.1-2. M
DeliveryType Set to "X2Only". M
ListOfDIDs Delivery endpoints for LI_X2. These delivery endpoints shall be configured by the IRI-TF in the RCS Server using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.M
CorrelationIDCorrelation ID to assign to xIRI generated by the IRI-POI in the HTTP Content Server. This field is populated with the same CorrelationID the IRI-POI in the RCS Server uses for the associated xIRI.M
ProductIDShall be set to the XID of the Task Object associated with the interception at the IRI-TF. This value shall be used by the IRI-POI in the HTTP Content Server to fill the XID of X2 messages.M
ListOfServiceTypes Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7] clause 6.2.1.2, Table 4.C
Identifier type Owner ETSI TS 103 221-1 [7] TargetIdentifier type Definition
RCS Content URI (See Note)3GPPTargetIdentifierExtension / RCSContentURIRCSContentURI (see XSD schema)
NOTE:
If the TargetIdentifier used is an RCS Content URI, only one RCS Content URI shall beincluded per ActivateTask message.
Up

7.13.2.2  Triggering of the CC-POI in the HTTP Content Server over LI_T3  p. 342

7.13.2.2.1  LI_T3 interface Specifics  p. 342
To support the use-cases where the IRI-POI in the HTTP Content Server does not get the identity of the user involved in the file-transfer (and therefore, the CC-POI in the HTTP Content Server cannot perform the intereption based on the target identity provisioned by the LIPF), the CC-TF present in the RCS Server sends a trigger to the CC-POI present in the HTTP Content Server. When the CC-TF in the RCS Server detects that a file is being uploaded or downloaded by a target UE, it shall send an activation message to the CC-POI in the HTTP Content Server over the LI_T3 interface. The activation message shall contain the correlation identifiers that the CC-POI in the HTTP Content Server shall use with the xCC. This can be achieved by sending an ActivateTask message as defined in ETSI TS 103 221-1 [7] clause 6.2.1 with the following details.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID Allocated by the CC-TF as per ETSI TS 103 221-1 [7].M
TargetIdentifiers File detection criteria as determined by the CC-TF in the RCS Server, which enables the CC-POI in the HTTP Content Server to isolate target files. The CC-POI in the HTTP Content Server shall support the identifier types given in Table 7.13.2.1-2.M
DeliveryType Set to "X3Only". M
ListOfDIDs Delivery endpoints for LI_X3. These delivery endpoints shall be configured by the CC-TF in the RCS Server using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.M
CorrelationIDCorrelation ID to assign to xCC generated by the CC-POI in the HTTP Content Server. This field is populated with the same CorrelationID the IRI-POI in the RCS Server uses for the associated xIRI.M
ProductIDShall be set to the XID of the Task Object associated with the interception at the CC-TF. This value shall be used by the CC-POI in the HTTP Content Server to fill the XID of X3 messages.M
ListOfServiceTypes Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7] clause 6.2.1.2, Table 4.C
Up

Up   Top   ToC