Question: In S8HR Lawful Interception (LI) for roaming cases, how does the Local Mobility and Interception Function (LMISF) verify the target identity for an incoming call to an inbound roaming user from a Non-Local-ID as the target?
Option 1: Using the called party identity (e.g., SIP headers: Request URI, P-Called-Party-Id, To)
Option 2: Based solely on the UE location received from the Serving Gateway/BBIFF
Option 3: Utilizing the tunnel endpoint IDs to determine call direction and then applying a fixed rule
Option 4: Using calling party identity (P-Asserted-Id, From) or redirecting party identity (History-Info, Diversion)
Explanation: For incoming calls to an inbound roaming user from a Non-Local-ID as the target, the LMISF uses either the calling party's asserted identity (through headers like P-Asserted-Id, From) or the redirecting party's identity (obtained from History-Info, Diversion headers) to verify the target identity. This approach is necessary for accurately identifying and intercepting communications involving non-local targets in roaming scenarios.