The documents listed below are not explicitly cited in this specification but are provided for background and for historical information.

This specification is replaced by TS 33.126 from Rel-15 onwards and should only be used as a historical reference to pre Rel-15 LI requirements. Additional Location information can be reported for various instances; the use of services; the use of network and or radio resources, the loss of a service; requested commercial LCS queries by the user, associates, or other application; and or from network and radio functions providing varying degrees of granularity and accuracy. Location Service may provide a higher degree of location granularity and accuracy than the existing network based Lawful Interception location capabilities described in clause 5.11.1. National regulation may impose the following requirements defined in TS 22.071 apply to LCS when invoked as part of LALS (Lawful Access Location Services):

• Any UE (including inbound roamers) served by the PLMN and supported by the serving PLMN LCS (including coverage) shall be targetable by LALS;
• If the location positioning for the target UE has failed, the LCS server shall report the reason for failure, if known;
• For LALS Target UEs may be positioned under all circumstances required by national regulatory requirements;
• The target UE user shall not be notified of any LALS location attempt;
• LALS location information provided should be the most recent if requested and available;
• The invocation, use and collection of LALS location should not cause target User service interruptions except for LCS priority described in clauses  4.5 and 7.3 of TS 22.071. In the case of LCS priority, national regulations may override the definitions in TS 22.071;
• Support for LALS Location shall apply for both active and idle UEs;
• LCS shall support LALS requests for the current (updated), or the last known position of an UE;
• The network should be sufficiently flexible to accommodate evolving LCS enabling mechanisms and LALS service requirements;
• Only authorized LALS network functions, resources and LI-LCS Clients shall provide LALS information;
• LALS shall support location of UEs in either circuit switched and packet switched domains.

National regulations may impose the following requirements in addition to those defined in TS 22.071 to apply to LCS when invoked as part of LALS:

• No LCS subscription is required for any UE within the PLMN for providing LALS location;
• The LALS positioning information shall be provided to the collection functions in a secure and reliable manner, such that the location information is neither lost, corrupted, nor made available to any unauthorized third party;
• The LI-LCS Client shall support periodic target UE location reporting to the LEA;
• LALS shall support different location update periods per target for multiple LEAs;
• LALS shall support identifying a target UE using any one of the following:
  • MSISDN
  • Tel URI/SIP URI
  • IMPI / IMPU
  • IMSI
  • IMEI
• Providing LALS location of an UE attached to a 3GPP network, using an IMEI identifier is required by some national regulations. In such case, IMEI may be mapped dynamically by a suitable identity such as IMSI or MSISDN (but is beyond the scope of this standard). Target identities which may be provided by the LI-LCS client to the LCS server are specified by TS 22.071 and TS 23.271;
• LALS shall re-use LCS supported positioning technologies defined in 3GPP, including positioning technology specific limitations, policies, procedures and operations. The specific positioning technology selected and deployed to support LCS and LALS will vary from operator to operator and even PLMN to PLMN;
• National Regulation may require LALS provide higher accuracy and security than Commercial LCS Services;
• LALS shall support multiple requests and obtain the location of the same target UE at the same time from different LEAs.