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.15 LI at 5GMS AF  7.15.1 Provisioning over LI_X1  7.15.1.1 Provisioning of IRI-POI in 5GMS AF  7.15.1.2 Provisioning of the MDF2  7.15.2 Generation of xIRI over LI_X2  7.15.2.1 General  7.15.2.2 Service access information  7.15.2.3 Consumption reporting  7.15.2.4 Dynamic policy invocation  7.15.2.5 Metrics reporting  7.15.2.6 Network assistance  7.15.2.7 Unsuccessful procedure  7.15.2.8 Start of interception with already configured UE  7.15.3 Generation of IRI over LI_HI2 
...

 

7.15  LI at 5GMS AF  p. 364

7.15.1  Provisioning over LI_X1  p. 364

7.15.1.1  Provisioning of IRI-POI in 5GMS AF  p. 364

The IRI-POI present in the 5GMS AF is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI in the 5GMS AF shall support the target identifier types given in Table 7.15.1.1-1.
Identifier Owner ETSI TS 103 221-1 [7] TargetIdentifier type Definition
gPSIMSISDNETSIGPSIMSISDN See ETSI TS 103 221-1 [7]
gPSINAIETSIGPSINAI See ETSI TS 103 221-1 [7]
Table 7.15.1.1-2 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI in the 5GMS AF.
If the IRI-POI in the 5GMS AF receives an ActivateTask message and the ListOfServiceTypes parameter contains a ServiceType that is not supported, the IRI-POI in the 5GMS AF shall reject the task with an appropriate error as described in ETSI TS 103 221-1 [7] clause 6.2.1.2.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiersOne of the target identifiers listed in the paragraph above.M
DeliveryType Set to "X2Only". M
ListOfDIDs Delivery endpoints for LI_X2 for the IRI-POI in the 5GMS AF. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
ListOfServiceTypes Shall be included when the explicit identification of specific CSP service types to be intercepted by the task as described in clause 5.2.4 is required. This parameter is defined in ETSI TS 103 221-1 [7] clause 6.2.1.2, Table 4.M
Up

7.15.1.2  Provisioning of the MDF2  p. 364

The MDF2 listed as the delivery endpoint over LI_X2 for xIRI generated by the 5GMS AF shall be provisioned over LI_X1 by the LIPF.
The target identities listed in clause 7.15.1.1 shall apply for the provisioning of MDF2.
Table 7.15.1.2-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiersOne or more of the target identifiers listed in clause 7.15.1.1.M
DeliveryType Set to "X2Only". (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.15.1.2-2M
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 Service type set to "Data". Other fields are dependent on the warrant. M
Up

7.15.2  Generation of xIRI over LI_X2  p. 365

7.15.2.1  General  p. 365

The IRI-POI present in the 5GMS AF shall send the xIRIs over LI_X2 for each of the events listed in clause 7.15.4 of TS 33.127, the details of which are described in the following clauses.

7.15.2.2  Service access information  p. 365

The IRI-POI in the 5GMS AF shall generate an xIRI containing an 5GMSAFServiceAccessInformation record when the IRI-POI present in the 5GMS AF detects that an 5GMS AF has sent the service access information to the Media Session Handler in the target UE. The IRI-POI present in the 5GMS AF shall generate the xIRI for the following event (as specified in clause 11.2 of TS 26.512):
  • 5GMS AF returns retrieveServiceAccessInformation response (i.e. 200 OK) in response to retrieveServiceAccessInformation request (i.e. GET) received from the Media Session Handler in the target UE which requests Service Access Information.
Field Name Description M/C/O
gPSIGPSI of the target UE.M
serviceAccessInformationResource Includes service access information resource data encoded according to clause 11.2.3 of TS 26.512. The SBIReference for this parameter shall be populated with 'TS26512_M5_ServiceAccessInformation.yaml#/­components/schemas/­ServiceAccessInformationResource' M
Up

7.15.2.3  Consumption reporting  p. 365

The IRI-POI in the 5GMS AF shall generate an xIRI containing an 5GMSAFConsumptionReporting record when the IRI-POI present in the 5GMS AF detects that an 5GMS AF has received a consumption report from the target UE. The IRI-POI present in the 5GMS AF shall generate the xIRI for the following event (as specified in clause 11.3 of TS 26.512):
  • 5GMS AF returns submitConsumptionReport Response (i.e. 204 No Content) in response to a submitConsumptionReport Request (i.e. POST) from the Media Session Handler in the target UE which submits a consumption report.
Field Name Description M/C/O
gPSIgPSI of the target UE.M
consumptionReport Includes a consumption report according to clause 11.3.3 of TS 26.512. The SBIReference for this parameter shall be populated with 'TS26512_M5_ ConsumptionReporting.yaml#/components/schemas/ConsumptionReport'. M
Up

7.15.2.4  Dynamic policy invocation  p. 366

The IRI-POI in the 5GMS AF shall generate an xIRI containing an 5GMSAFDynamicPolicyInvocation record when the IRI-POI present in the 5GMS AF detects that an 5GMS AF has received a dynamic policy from the target UE. The IRI-POI present in the 5GMS AF shall generate the xIRI for the following events (as specified in clause 11.5 of TS 26.512):
  • 5GMS AF returns a createDynamicPolicy Response (i.e. 201 Created) in response to a createDynamicPolicy Request (i.e. POST) from the Media Session Handler in the target UE which creates a dynamic policy resource.
  • 5GMS AF returns a retrieveDynamicPolicy Response (i.e. 20O OK) in response to a retrieveDynamicPolicy Request (i.e. GET) from the Media Session Handler in the target UE which retrieves the dynamic policy resource.
  • 5GMS AF returns an updateDynamicPolicy Response (i.e. 20O OK or 204 No Content) in response to an updateDynamicPolicy Request (i.e. PUT) from the Media Session Handler in the target UE which replaces the dynamic policy resource.
  • 5GMS AF returns a patchDynamicPolicy Response (i.e. 20O OK or 204 No Content) in response to a patchDynamicPolicy Request (i.e. PATCH) from the Media Session Handler in the target UE which modifies the dynamic policy resource.
  • 5GMS AF returns a destroyDynamicPolicy Response (i.e. 204 No Content) in response to a destroyDynamicPolicy Request (i.e. DELETE) from the Media Session Handler of the target UE which deletes the dynamic policy resource.
Field Name Description M/C/O
gPSIGPSI of the target UE.M
dynamicPolicyResource Includes a dynamic policy resource according to clause 11.5.3 of TS 26.512. The SBIReference for this parameter shall be populated with 'TS26512_M5_ DynamicPolicies.yaml#/components/schemas/DynamicPolicy'. M
dPIOperationTypeType of operation applied to the dynamic policy resource, i.e. createDynamicPolicy, retrieveDynamicPolicy, updateDynamicPolicy, patchDynamicPolicy, destroyDynamicPolicy.M
Up

7.15.2.5  Metrics reporting  p. 366

The IRI-POI in the 5GMS AF shall generate an xIRI containing an 5GMSAFMetricsReporting record when the IRI-POI present in the 5GMS AF detects that an 5GMS AF has received a metrics report from the target UE. The IRI-POI present in the 5GMS AF shall generate the xIRI for the following event (as specified in clause 11.4 of TS 26.512):
  • 5GMS AF returns submitMetricsReport Response (i.e. 204 No Content) in response to a submitMetricsReport Request (i.e. POST) from the Media Session Handler in the target UE which submits a metrics report.
Field Name Description M/C/O
gPSIGPSI of the target UE.M
metricsReport Includes a metrics report according to clause 11.4.3 of TS 26.512. Encoded according to clause C.4.3 of TS 26.512 and TS 26.247. The XMLNamespace for this parameter shall be set to 'urn:3gpp:metadata:2011:HSD:receptionreport'. M
Up

7.15.2.6  Network assistance  p. 366

The IRI-POI in the 5GMS AF shall generate an xIRI containing an FiveGMSAFNetworkAssistance record when the IRI-POI present in the 5GMS AF detects that an 5GMS AF has received a network assistance from the target UE. The IRI-POI present in the 5GMS AF shall generate the xIRI for the following events (as specified in clause 11.6 of TS 26.512):
  • 5GMS AF returns a createNetworkAssistanceSession Response (i.e. 201 Created) in response to a createNetworkAssistanceSession Request (i.e. POST) from the Media Session Handler in the target UE which creates a network assistance session resource.
  • 5GMS AF returns a retrieveNetworkAssistanceSession Response (i.e. 200 OK) in response to a retrieveNetworkAssistanceSession Request (i.e. GET) from the Media Session Handler in the target UE which retrieves an existing network assistance session resource.
  • 5GMS AF returns an updateNetworkAssistanceSession Response (i.e. 200 OK or 204 No Content) in response to an updateNetworkAssistanceSession Request (i.e. PUT) from the Media Session Handler in the target UE which replaces an existing network assistance session resource.
  • 5GMS AF returns a patchNetworkAssistanceSession Response (i.e. 200 OK or 204 No Content) in response to a patchNetworkAssistanceSession Request (i.e. PATCH) from the Media Session Handler in the target UE which modifies the network assistance session resource.
  • 5GMS AF returns a destroyNetworkAssistanceSession Response (i.e. 204 No Content) in response to a destroyNetworkAssistanceSession Request (i.e. DELETE) from the Media Session Handler in the target UE which deletes the network assistance session resource.
  • 5GMS AF returns a requestBitRateRecommendation Response (i.e. 200 OK) in response to a requestBitRateRecommendation Request (i.e. GET) from the Media Session Handler in the target UE which requests a bit rate recommendation for the next recommendation window.
  • 5GMS AF returns a requestDeliveryBoost Response (i.e. 200 OK) in response to a requestDeliveryBoost Request (i.e. POST) from the Media Session Handler in the target UE which requests a delivery boost.
Field Name Description M/C/O
gPSIGPSI of the target UE.M
networkAssistanceSessionResource Includes a network assistance session resource according to clause 11.6.3 of TS 26.512. The SBIReference for this parameter shall be populated with 'TS26512_M5_ NetworkAssistance.yaml#/components/schemas/ NetworkAssistanceSession'. M
nAOperationTypeType of operation applied to the network assistance resource, i.e. createNetworkAssistanceSession, retrieveNetworkAssistanceSession, updateNetworkAssistanceSession, patchNetworkAssistanceSession, destroyNetworkAssistanceSession, requestBitRateRecommendation and requestDeliveryBoost.M
Up

7.15.2.7  Unsuccessful procedure  p. 367

The IRI-POI in the 5GMS AF shall generate an xIRI containing a FiveGMSAFUnsuccessfulProcedure record when the IRI-POI present in the 5GMS AF detects an unsuccessful procedure or error condition for a target UE. Accordingly, the IRI-POI in the 5GMS AF generates the xIRI when any of the following events are detected:
  • 5GMS AF returns retrieveServiceAccessInformation response (i.e. 404 Not Found) in response to retrieveServiceAccessInformation request (i.e. GET) from the target UE.
  • 5GMS AF returns submitConsumptionReport Response (i.e. 400 Bad Request or 415 Unsupported Media Type) in response to a submitConsumptionReport Request (i.e. POST) from the target UE.
  • 5GMS AF returns submitMetricsReport Response (i.e. 400 Bad Request or 415 Unsupported Media Type) in response to a submitMetricsReport Request (i.e. POST) from the target UE.
  • 5GMS AF returns a createDynamicPolicy Response (i.e. 400 Bad Request or 401 Unauthorized) in response to a createDynamicPolicy Request (i.e. POST) from the target UE.
  • 5GMS AF returns a retrieveDynamicPolicy Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a retrieveDynamicPolicy Request (i.e. GET) from the target UE.
  • 5GMS AF returns an updateDynamicPolicy Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to an updateDynamicPolicy Request (i.e. PUT) from the target UE.
  • 5GMS AF returns a patchDynamicPolicy Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a patchDynamicPolicy Request (i.e. PATCH) from the target UE.
  • 5GMS AF returns a destroyDynamicPolicy Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a destroyDynamicPolicy Request (i.e. DELETE) from the target UE.
  • 5GMS AF returns a createNetworkAssistanceSession Response (i.e. 400 Bad Request or 401 Unauthorized) in response to a createNetworkAssistanceSession Request (i.e. POST) from the target UE.
  • 5GMS AF returns a retrieveNetworkAssistanceSession Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a retrieveNetworkAssistanceSession Request (i.e. GET) from the target UE.
  • 5GMS AF returns an updateNetworkAssistanceSession Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to an updateNetworkAssistanceSession Request (i.e. PUT) from the target UE.
  • 5GMS AF returns a patchNetworkAssistanceSession Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a patchNetworkAssistanceSession Request (i.e. PATCH) from the target UE.
  • 5GMS AF returns a destroyNetworkAssistanceSession Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a destroyNetworkAssistanceSession Request (i.e. DELETE) from the target UE.
  • 5GMS AF returns a requestBitRateRecommendation Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a requestBitRateRecommendation Request (i.e. GET) from the target UE.
  • 5GMS AF returns a requestDeliveryBoost Response (i.e. Either 400 Bad Request or 401 Unauthorized or 404 Not Found) in response to a requestDeliveryBoost Request (i.e. POST) from the target UE.
Field Name Description M/C/O
gPSIGPSI of the target UE.M
fiveGMSAFUnsuccessfulOperationType of unsuccessful operation.M
fiveGMSAFErrorCodeError code returned for the unsuccessful operation.M
Up

7.15.2.8  Start of interception with already configured UE  p. 368

The IRI-POI in the 5GMS AF shall generate an xIRI containing an FiveGMSAFStartOfInterceptionWithAlreadyConfiguredUE record when the IRI-POI present in the 5GMS AF detects that interception is activated for a target UE which Media Session Handler has already been configured with the service access information.
Field Name Description M/C/O
gPSIGPSI of the target UE.M
serviceAccessInformationResource Includes service access information resource data encoded according to clause 11.2.3 of TS 26.512. The SBIReference for this parameter shall be populated with 'TS26512_M5_ServiceAccessInformation.yaml#/­components/­schemas/­ServiceAccessInformationResource'. M
Up

7.15.3  Generation of IRI over LI_HI2  p. 368

When an xIRI is received over LI_X2 from the IRI-POI in the 5GMS AF, the MDF2 shall send the IRI message over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received from LI_X2. The record may be enriched by other information available at the MDF (e.g. additional location information).
The timestamp field of the ETSI TS 102 232-1 [9] PSHeader structure shall be set to the time at which the 5GMS AF event was observed (i.e. the timestamp field of the xIRI).
The IRI type parameter shall be included and coded according to Table 7.14.2-19 (see ETSI TS 102 232-1 [9] clause 5.2.10).
IRI message Record type
FiveGMSAFServiceAccessInformationREPORT
FiveGMSAFConsumptionReportingREPORT
FiveGMSAFDynamicPolicyInvocationREPORT
FiveGMSAFMetricsReportingREPORT
FiveGMSAFNetworkAssistanceREPORT
FiveGMSAFUnsuccessfulProcedureREPORT
FiveGMSAFStartOfInterceptionWithAlreadyConfiguredUEREPORT
The threeGPP33128DefinedIRI field (see ETSI TS 102 232-7 [10] clause 15) shall be populated with the BER-encoded IRIPayload.
MDF2 delivers the IRI to the LEMF with GPSI as the target identity if and only if GPSI is present in the xIRI.
Up

Up   Top   ToC