Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.7.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.10.4  HR LI Phase 2p. 294

7.10.4.1  Overviewp. 294

The Phase-2 of HR LI that applies to inbound roaming target UEs that use IMS-based services with home-routed roaming or the inbound roaming UEs that use IMS-based services with home-routed roaming to communicate with the target non-local ID include the functions that revolve around the following interfaces.
  • LI_X1: Used by the LIPF to provision the LMISF-IRI, MDF2 and MDF3 with the LI information for a target.
  • LI_T1: Used by the LMISF-IRI to instruct the BBIFF-C/BBIFF that IMS media related user plane packets of target's communication need to be captured and delivered to the LMISF-CC.
  • LI_T3: Used by the BBIFF-C to instruct the BBIFF-U to capture and deliver the IMS media related user plane packets of target's communication to the LMISF-CC.
  • LI_X3_LITE_S: Used by the BBIFF-U/BBIFF to forward the IMS signalling related user plane packets of inbound roaming UEs to the LMISF-IRI.
  • LI_X3_LITE_M: Used by the BBIFF-U/BBIFF to forward the IMS media related user plane packets of target's communication to the LMISF-CC.
The triggering interface LI_T3 is not used in the case of BBIFF in SGW. The LI_X3_LITE_S is also used for HR LI Phase-1.
Up

7.10.4.2  Provisioning over LI_X1p. 294

7.10.4.2.1  Generalp. 294
For Phase-2 of HR LI, the following LI functions are provisioned over LI_X1 by the LIPF using the X1 protocol defined in ETSI TS 103 221-1 [7] with the LIPF playing the role of ADMF and the following LI functions playing the role of NE as per the reference model depicted in ETSI TS 103 221-1 [7].
  • LMISF-IRI.
  • MDF2.
  • MDF3.
As described in clause 7.10.1, the Phase-2 of HR LI applies to inbound roaming target UEs that use IMS-based services with home-routed roaming or the inbound roaming UEs that use IMS-based services with home-routed roaming to communicate with the target non-local ID. The following target identities are used for Phase-2 of HR LI:
  • IMPU.
  • IMPI.
  • PEIIMEI.
  • IMEI.
The target identity in the IMPI format may contain a value derived from a SUPI or an IMSI. The target identity in the IMPU format containing a SIP URI or TEL URI may contain a value derived from a GPSI, MSISDN, an E.164 number, or IMSI. Only IMPU is used for target non-local ID. For triggered LALS, the LTF function associated with LMISF-IRI (see clause 7.3.1 and TR 33.928) is provisioned with the target identity of IMPU.
Up
7.10.4.2.2  Provisioning of LMISF-IRIp. 295
The LMISF-IRI shall be provisioned over LI_X1 by the LIPF for target based interception of IMS services in the VPLMN with home-routed roaming.
The target identities listed in clause 7.10.4.2.1 shall apply for the provisioning of LMISF-IRI with LMISF-IRI playing the combined role of IRI-POI and CC-TF for the interception of IMS-based services in the VPLMN with home-routed roaming.
The LMISF-IRI shall support the following service scoping from the structure defined in ETSI TS 103 221-1 [7]:
  • The enumerated value of "voice" or "messaging" in the service type field.
  • When location reporting is required, one or both of "reportBeginingAndEnd", "reportUponChange".
  • "SuspendOnOutboundInternationalRoaming".
Table 7.10.4.2-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the LMISF-IRI for Phase-2.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID XID assigned by LIPF. The value used here is different from the value used in ActivateTask shown in Table 7.10.3.2-4.M
TargetIdentifiersOne or more of the target identifiers listed in clause 7.10.4.2.1.M
DeliveryType Set to "X2Only", "X3Only" or "X2andX3" as needed to meet the requirements of the warrant. 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
ServiceScoping Using the format defined in ETSI TS 103 221-1 [7] based on the service scoping listed above the table. When multiple intercepts are activated on a target identifier, the service scoping shall be the union of all of them.C
Up
7.10.4.2.3  Provisioning of the MDF2p. 295
The MDF2 listed as the delivery endpoint over LI_X2 for xIRI generated by the LMISF-IRI shall be provisioned over LI_X1 by the LIPF.
The target identities listed in clause 7.10.4.2.1 shall apply for the provisioning of MDF2.
The MDF2 shall support the following service scoping from the structure defined in ETSI TS 103 221-1 [7]:
  • The enumerated value of "voice" or "messaging" in the service type field.
  • When location reporting is required, one or both of "reportBeginingAndEnd", "reportUponChange".
Table 7.10.4.2-2 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.10.4.2.1.M
DeliveryTypeThis value shall be 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.10.4.2-3.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 Using the format defined in ETSI TS 103 221-1 [7] include the service scoping as applicable to this LIID based on the service scoping listed above the table.C
Up
7.10.4.2.4  Provisioning of the MDF3p. 296
The MDF3 listed as the delivery endpoint over LI_X3 for xCC generated by the LMISF-CC shall be provisioned over LI_X1 by the LIPF.
The target identities listed in clause 7.10.4.2.1 shall apply for the provisioning of MDF3.
The MDF3 shall support the following service scoping from the structure defined in ETSI TS 103 221-1 [7]:
  • The enumerated value of "voice" or "messaging" in the service type field.
  • When location reporting is required, one or both of "reportBeginingAndEnd", "reportUponChange".
Table 7.10.4.2-4 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF3.
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.10.4.2.1.M
DeliveryTypeThis value shall be Ignored by the MDF3.M
ListOfDIDs Delivery endpoints of LI_HI3. 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.10.4.2-5.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 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 Using the format defined in ETSI TS 103 221-1 [7] include the service scoping as applicable to this LIID based on the service scoping listed above the table.C
Up

7.10.4.3  Generation of xIRI over LI_X2p. 297

7.10.4.3.1  General conceptsp. 297
The LMISF-IRI extracts the SIP messages that it receives within the xCC from the BBIFF-U/BBIFF over the LI_X3_LITE_S.
On the originating end of a voice session, the LMISF-IRI examines the SIP message, the stored LI_X2_LITE record and the stored LI_X3_LITE_S record to check for the following:
  • Whether the calling party identity is a target.
  • Whether the called party identity is a target non-local ID.
On the terminating end of a voice session, the LMISF-IRI examines the SIP message, the stored LI_X2_LITE record and the stored LI_X3_LITE_S record to check for the following:
  • Whether the called party identity is a target.
  • Whether the calling party identity is a target non-local ID.
  • Whether the redirecting party identity is a target non-local ID.
The SIP headers used for identifying a calling party identity, called party identity, redirecting party identity can be same identities used by the IMS signaling functions with the following additions:
  • P-Preferred Identity as calling party identity.
When any of the conditions listed above are true, the LMISF-IRI concludes that target is involved in an IMS session that shall be intercepted. Accordingly, the LMISF-IRI generates the xIRIs and delivers the same to the MDF2 over the LI_X2.
For IMS-based voice services, if media interception is required, the LMISF-IRI sends a trigger for the same to the BBIFF-C/BBIFF over the LI_T1 interface.
Up
7.10.4.3.2  Target matchp. 297
7.10.4.3.2.1  Generalp. 297
When an IMS UE performs an IMS registration (using SIP REGISTER) request, the LMISF-IRI examines the following for a target match:
  • From header and To header of the SIP REGISTER when the target identity is IMPU.
  • SUPI or IMSI stored in the LI_X2_LITE record when the target identity is IMPI.
  • +sip.instance-id of Contact header of the SIP REGISTER when the target identity is PEIIMEI or IMEI.
The LMISF-IRI shall store the +sip.instance-id in the LI_X2_LITE_S record for later use.
7.10.4.3.2.2  Service type of voicep. 298
When an IMS UE originates an IMS session (using SIP INVITE), the LMISF-IRI examines the following to verify for a target match:
  • P-Preferred Identity header and From header present in the SIP INVITE when the target identity is IMPU.
  • Request URI header and To header present in the SIP INVITE when the target identity is IMPU and target is non-local ID.
  • SUPI or IMSI stored in the LI_X2_LITE record when the target identity is IMPI.
  • +sip.instance-id of Contact header received in the SIP REGISTER request when the target identity is PEIIMEI or IMEI.
When an IMS UE receives an incoming IMS session (using SIP INVITE), the LMISF-IRI examines the following to verify for a target match:
  • Request URI and To header present in the SIP INVITE when the target identity is IMPU.
  • P-Asserted-Id, From header, History Info header and Diversion header present in the SIP header when the target identity is IMPU and target is non-local ID.
  • SUPI or IMSI stored in the LI_X2_LITE record when the target identity is IMPI.
  • +sip.instance-id of Contact header received in the SIP REGISTER request when the target identity is PEIIMEI or IMEI.
LMISF-IRI may use the Via header or the Route header to determine whether the SIP INVITE is for an originating IMS session or a terminating IMS session. LMISF-IRI stores the SIP Call Id to associate the subsequent SIP messages received on the same session for a target match.
For subsequent SIP messages, the LMISF-IRI may use the stored LI_X3_LITE_S record to determine for a target match.
Up
7.10.4.3.2.3  Service type of messagingp. 298
When the Service Type received in the LI_X1 provisioning is "messaging", the LMISF-IRI examines the SIP MESSAGE for a target match as shown below:
  • For MO-SMS over IP, P-Preferred Identity header and From header present in the SIP MESSAGE when the target identity is IMPU.
  • For MO-SMS over IP, TP-DA field of SMS-SUBMIT within the Message-body of SIP MESSAGE when the target identity IMPU for target non-local ID.
  • For MT-SMS over IP, the Request URI and To header present in the SIP MESSAGE when the target identity is IMPU.
  • For MT-SMS over IP, the TP-OA field or TP-RA field of SMS-SUBMIT within the Message-body SIP MESSAGE when the target identity IMPU for target non-local ID.
  • SUPI or IMSI stored in the LI_X2_LITE record when the target identity is IMPI.
  • +sip.instance-id of Contact header received in the SIP REGISTER request when the target identity is PEIIMEI or IMEI.
LMISF-IRI may use the Via header or the Route header to determine whether the SIP MESSAGE is for MO-SMS over IP or MT-SMS over IP.
Up
7.10.4.3.3  xIRIsp. 298
The xIRIs generated at the LMISF-IRI shall be same as the xIRIs generated in the IRI-POIs present in the IMS signaling functions (see clause 7.12.4.12).
As defined in TS 33.127 the LMISF-IRI generates the following xIRIs:
  • Encapsulated SIP message.
  • Start of interception with an established IMS session.
The xIRI CC Unavailable defined in TS 33.127 for IMS-based services is not applicable to N9HR LI and S8HR LI. The encapsulated SIP message is sent using the xIRI IMSMessage record.
Further details of the xIRIs are defined in clause 7.12.4.12.
Up

7.10.4.4  Triggering of BBIFF-C from LMISF over LI_T1p. 299

7.10.4.4.1  Generalp. 299
When the intercepted IMS-session requires the media interception, the LMISF-IRI sends a trigger to the BBIFF-C/BBIFF over to the LI_T1 interface (see TS 33.127) with LMISF-CC as the delivery end point.
The LMISF-IRI upon discovering through the xIRIs received over the LI_X2_LITE interface that a change in SMF or SGW-C/SGW has occurred for an interception involving an IMS-session shall send the trigger to BBFF-C/BBIFF present in the new SMF or SGW-C/SGW over LI_T1 interface with LMISF-CC as the delivery end point to continue the IMS media interception when required.
When the IMS session is completely released (e.g. all session-legs are released), the LMISF-IRI sends a trigger to the BBIFF-C/BBIFF to stop the media intereption. The LMISF-IRI may also send the trigger to stop the media interception when the target information is deprovisioned in the LMISF-IRI by the LIPF.
The present document supports the media interception of IMS voice media.
Up
7.10.4.4.2  N9HR LIp. 299
The LI_T1 trigger that the LMISF-IRI sends to the BBIFF-C present in the SMF shall include at least the following information:
  • The XID that LMISF-IRI receives from the LIPF over LI_X1 for the target related activation.
  • Target identity: SUPI, PDU session ID, IMS voice media.
  • Delivery end point: LMISF-CC.
The details of ActivateTask sent to the BBIFF-C in SMF over LI_T1 are shown in Table 7.10.4.4-1.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID Allocated by the LMISF-IRI as per ETSI TS 103 221-1 [7].M
TargetIdentifiers Information that identifies the need to intercept the IMS voice media. The target identifiers as shown in Table 7.10.4.4-2.M
DeliveryType Set to "X3Only". M
ListOfDIDs Shall give the DID of the LMISF-CC to which the xCC should be delivered. The delivery endpoint is configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
CorrelationIDThis value is set by the LMISF-IRI and shall be same as the value to be used in the xCC generated at the LMISF-CC. The BBIIF-C passes this field to the BBIFF-U over LI_T3.M
ProductIDShall be set to the XID of the Task Object associated with the interception at the LMISF-IRI. This value shall be passed to the BBIFF-U over LI_T3.M
Identifier type ETSI TS 103 221-1 [7] TargetIdentifier type Definition
SUPISUPIETSI TS 103 221-1 [7]
PDUSessionIDTargetIdentifierExtension/PDUSessionIDInteger (see XSD schema)
IMSVoiceMediaTargetIdentifierExtension/IMSVoiceMediaEmpty tag (see XSD schema)
NOTE:
The LMISF-IRI shall use the SUPI and PDU Session ID received over the LI_X2_LITE interface to populate the target identifiers SUPI and PDUSessionID respectively. The SUPI is in either SUPIIMSI or IMSI format (ETSI TS 103-221-1 [7]).
The DeactivateTask message that the LMISF-IRI sends to the BBIFF-C present in the SMF shall include the XID of the Task created by the ActivateTask message (see Table 7.10.4.4-1).
Up
7.10.4.4.3  S8HR LIp. 300
The LI_T1 trigger that the LMISF-IRI sends to the BBIFF-C present in the SGW-C/SGW shall include at least the following information:
  • The XID that LMISF-IRI receives from the LIPF over LI_X1 for the target related activation.
  • Target identity: IMSI, Bearer ID, IMS voice media.
  • Delivery end point: LMISF-CC.
The details of ActivateTask sent to the BBIFF-C in SGW-C over LI_T1 are shown in Table 7.10.4.4-3.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID Allocated by the LMISF-IRI as per ETSI TS 103 221-1 [7].M
TargetIdentifiers Information that identifies the need to intercept the IMS voice media. See Table 7.10.4.4-4.M
DeliveryType Set to "X3Only". M
ListOfDIDs Shall give the DID of the LMISF-CC to which the xCC should be delivered. The delivery endpoint is configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
CorrelationIDThis value is set by the LMISF-IRI and shall be same as the value to be used in the xCC generated at the LMISF-CC. The BBIIF-C in passes this field to the BBIFF-U over LI_T3.M
ProductIDShall be set to the XID of the Task Object associated with the interception at the LMISF-IRI. This value shall be passed to the BBIFF-U over LI_T3.M
Identifier type ETSI TS 103 221-1 [7] TargetIdentifier type Definition
IMSIIMSIETSI TS 103 221-1 [7]
BearerIDTargetIdentifierExtension/BearerIDInteger (see XSD schema)
IMSVoiceMediaTargetIdentifierExtension/IMSVoiceMediaEmpty tag (see XSD schema)
NOTE:
The LMISF-IRI shall use the IMSI and Bearer ID received over the LI_X2_LITE interface to populate the target identifiers IMSI and BearerID respectively.
The DeactivateTask message that the LMISF-IRI sends to the BBIFF-C/BBIFF present in the SGW-C/SGW shall include the XID of the Task created by the ActivateTask message (see Table 7.10.4.4-3).
Up

7.10.4.5  Triggering of BBIFF-U from BBIFF-C over LI_T3p. 300

7.10.4.5.1  Generalp. 300
When the trigger is received over the LI_T1 for activating the media interception, the BBIFF-C present in the SGW-C shall send a trigger over LI_T3 to the BBIFF-U present in the SGW-U when a dedicated bearer for the IMS media is established on the PDN connection.
When the trigger is received over the LI_T1 for activating the media interception, the BBIFF-C present in the SMF shall send a trigger over LI_T3 to the BBIFF-U present in the UPF when the PDU session is modified for adding IMS media related QoS flow.
If the trigger over LI_T1 is received for activating the media interception after the IMS media related changes has happened (i.e. dedicated bearer is established for IMS media, PDU session is modified for adding the IMS media related QoS flow), then the BBIFF-C shall send the trigger to the BBIFF-U over LI_T3 immediately.
The BBIFF-C shall trigger the BBIFF-U to stop the delivery of xCC to the LMISF-CC when it receives the trigger from the LMISF-IRI over LI_T1 for stopping the media interception, independent of whether the IMS media related changes have happened or not.
Up
7.10.4.5.2  N9HR LIp. 301
The LI_T3 trigger that the BBIFF-C in SMF sends to the BBIFF-U present in the UPF shall include at least the following information:
  • XID assigned locally by the BBIFF-C in the SMF.
  • The ProductID that includes the XID it receives from the LMISF-IRI over LI_T1.
  • Target identity: PFCP Session ID, PDR ID with the QFI associated with the IMS voice media (5Q = 1) related QoS flow.
  • Delivery end point: LMISF-CC
The details of ActivateTask sent to the BBIFF-U in UPF over LI_T3 are shown in Table 7.10.4.5-1.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID Allocated by the BBIFF-C as per ETSI TS 103 221-1 [7].M
TargetIdentifiers Packet detection criteria as determined by the BBIFF-C in the SMF, which enables the BBIFF-U to isolate user-plane packets of IMS voice media. The BBIFF-U in the UPF shall support the identifier types given in Table 6.2.3-7. The target identity type of PDR ID shall be mandatory. The BBIFF-C in SMF shall use the QFI associated with the IMS voice media (5QI = 1) related QoS flow to populate the QFI field within the PDI of PDR ID.M
DeliveryType Set to "X3Only". M
ListOfDIDs Shall give the DID of the LMISF-CC to which the xCC should be delivered. The delivery endpoint is configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
CorrelationID Correlation ID to assign to X3 PDUs generated by the BBIFF-U in the UPF. This field is populated with the same CorrelationID received over the LI_T1 interface (see Table 7.10.4.4-1).M
ProductID Shall be set to the XID of the Task Object associated with the interception as received in the ProductID field over LI_T1 interface (see Table 7.10.4.4-1). This value shall be used by the BBIFF-U in the UPF to fill the XID of X3 PDUs.M
The DeactivateTask sent to the BBIFF-U present in the UPF over LI_T3 shall include the XID of the Task created by the ActivateTask message (see Table 7.10.4.5-1).
Up
7.10.4.5.3  S8HR LIp. 301
The LI_T3 trigger that the BBIFF-C in SGW-C sends to the BBIFF-U present in the SGW-U shall include at least the following information:
  • XID assigned locally by the BBIFF-C in the SGW-C.
  • The ProductID that includes the XID it receives from the LMISF-IRI over LI_T1.
  • Target identity: PFCP Session ID, PDR ID with the F-TEID associated with the IMS voice media (QCI = 1) related dedicated bearer.
  • Delivery end point: LMISF-CC.
The details of ActivateTask sent to the BBIFF-U in SGW-U over LI_T3 are shown in Table 7.10.4.5-2.
ETSI TS 103 221-1 [7] field name Description M/C/O
XID Allocated by the BBIFF-C as per ETSI TS 103 221-1 [7].M
TargetIdentifiers Packet detection criteria as determined by the BBIFF-C in the SGW-C, which enables the BBIFF-U in SGW-U to isolate user-plane packets. The BBIFF-U in the SGW-U shall support the identifier types given in Table 6.2.3-7. The target identity type of PDR ID shall be mandatory. The BBIFF-C in SGW-C shall use the F-TEIDs associated with the IMS voice media (QCI = 1) related dedicated bearer to populate the F-TEID field within the PDI of PDR ID.M
DeliveryType Set to "X3Only". M
ListOfDIDs Shall give the DID of the LMISF-CC to which the xCC should be delivered. The delivery endpoint is configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
CorrelationID Correlation ID to assign to X3 PDUs generated by the BBIFF-U in the SGW-U. This field is populated with the same CorrelationID received over the LI_T1 interface (see Table 7.10.4.4-3).M
ProductID Shall be set to the XID of the Task Object associated with the interception as received in the ProductID field over LI_T1 interface (see Table 7.10.4.4-3). This value shall be used by the BBIFF-U in the SGW-U to fill the XID of X3 PDUs.M
The DeactivateTask sent to the BBIFF-U present in the SGW-U over LI_T3 shall include the XID of the Task created by the ActivateTask message (see Table 7.10.4.5-2).
Up

7.10.4.6  Generation of xCC over LI_X3_LITE_Mp. 302

The BBIFF-U in UPF and the BBIFF-U in SGW-U shall send the xCC over LI_X3_LITE_M for each of the packet matching the criteria specified in the Triggering message (i.e. Activate Task message) received over the LI_T3 from the BBIFF-C.
The BBIFF in SGW shall identify the IMS voice media (QCI = 1) related dedicated bearer associated with the IMS signaling related bearer as indicated in the trigger received over the LI_T1 from the LMISF-IRI and then send xCC over LI_X3_LITE_M for each of the packet captured from that dedicated bearer.
The BBIFF-U/BBIFF shall set the payload format to indicate the appropriate payload type (5 for IPv4 Packet, 6 for IPv6 Packet, or 12 for GTP-U Packet as described in ETSI TS 103 221-2 [8] clauses 5.4 and 5.4.13).
Up

7.10.4.7  Generation of xCC over LI_X3p. 302

The xCC generated at the LMISF-CC shall be same as the xCC generated in the CC-POIs present in the IMS media functions. Further details of this are not specified in the present document.
The correlation identifier value included in the xCC of an IMS session can be dependent on the UDP port numbers associated with the voice-media related RTP streams. This is the case when a user is involved in multiple IMS sessions. An illustrated of this is shown in clause 7.10.4.8
Up

7.10.4.8  Correlation identifierp. 302

The xIRIs generated at the LMISF-IRI shall be correlated using the correlation identifier field defined ETSI TS 103 221-2 [8]. This correlation identifier value can be independent of the correlation identifier value received in the xCC from the BBIFF-U/BBIFF over the LI_X3_LITE_S interface.
Furthermore, the xIRIs generated at the LMISF_IRI shall include the correlation identifier value used in the xCC generated at the LMISF-CC. Any intra-LMISF interactions required to associate the correlation identifier values used by the LMISF-IRI and LMISF-CC are outside the scope of the present document.
Each session-leg of an IMS session may have to be correlated separately. This is accomplished using the RTP/RTCP port numbers present in the SDP of IMS signaling message and the UDP port numbers present in the IMS voice media related RTP as illustrated in Figure 7.10.4.8-1 below.
Copy of original 3GPP image for 3GPP TS 33.128, Fig. 7.10.4.8-1: Correlation at the session-leg level (an illustration)
Up
Figure 7.10.4.8-1 illustrates an example where an IMS session includes two session-legs.
Session-leg 1:
  • Source IP address: 192.0.2.10 and source port number: 24000 (RTP), 24001 (RTCP).
  • Destination IP address: 198.51.100.1 and destination port number: 32000 (RTP), 32001 (RTCP).
Session-leg 2:
  • Source IP address: 192.0.2.10 and source port number: 26000 (RTP), 26001 (RTCP).
  • Destination IP address: 198.51.100.1 and destination port number: 36000 (RTP), 36001 (RTCP).
The IP address of the two end-points happen to be the same for the two session legs. The RTP port numbers present in the SDP of IMS signaling message and the UDP port numbers of the associated with the IMS voice-media related RTP happen to be the same for a session-leg.
Therefore, in general, multiple session-legs can be identified using the RTP port numbers present in the SDP of IMS signaling message and the UDP port numbers associated with the IMS voice-media related RTP.
Up

7.10.4.9  Generation of IRI over LI_HI2p. 303

When an xIRI is received over LI_X2 from the LMISF-IRI, 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 IRI messages delivered over the LI_HI2 for HR LI are same as the IRI messages delivered over the LI_HI2 for LI IMS-based voice services. Further details of this are outside the scope of the present document.
Up

7.10.4.10  Generation of CC over LI_HI3p. 303

When the xCC is received over LI_X3 from the LMISF-CC, the MDF3 shall deliver the CC over LI_HI3 without undue delay.
The CC delivered over the LI_HI3 for HR LI is the same as the CC delivered over the LI_HI3 for LI IMS-based voice services. Further details of this are outside the scope of the present document.

Up   Top   ToC