It is vital to Understand how the technology landscape has changed, how it evolved retrospectively, and how technology is moving forward.
In a cloud environment, there is no single way LI capability is provided. It is sometimes necessary that multiple parties not only to gain access to the “as a Service” data stream but to also correlate location services for the Intercept Services (LBS or E911 prevailing).
G2K Labs’s LIMA LI 5G Platform rises to this “Mediation” challenge by proving a cloud, rather than core environment, that is modular and customizable to address direct interface / mediation with the Intercept Subject’s current access service (ISaaS).
In cloud language, the services are referred to as “Something as a Service”. For example, they can be:
· Communication as a Service (CaaS)
· Data as a Service (DaaS)
· Infrastructure as a Service (IaaS)
· Network as a Service (NaaS)
· Platform as a Service (PaaS)
· Software as a Service (SaaS)
· Virtual Desktop as a Service (VaaS), etc.
To Intercept a Subject In a non-cloud environment, an Intercept Subject is identified in several ways, for example:
· Telephone Number.
· SIP/TEL Uniform Resource Identifier (URI).
· Media Access Control (MAC) Address, International Mobile Station Equipment Identity (IMEI).
· International Mobile Subscriber Identity (IMSI).
· Static IP Address.
For some LI cases, even a network resource may be identified as the Intercept Subject (e.g., Conference URI).
In a cloud environment, an Intercept Subject may have to be identified for lawful interception purposes through the identities used by the Intercept subject to log in to the cloud-based service. In most situations, this could be a user ID. In some situations, it can also be the telephone number or SIP/TEL URI or even the IP address.