02a TR-45 LAES Scope Wording

advertisement
TR45/2003.12.03.16
FYI for TR-45
These wording changes to the scopes for the proposed joint projects approved by TR-45 in June, 2003,
were made during a TR-45 LAES Ad Hoc group conference call on November 14th. This wording will be
included in a letter to T1 coming out of the December Ad Hoc meeting in response to their liaison from
August 2003 posing questions on the two projects.
Scope and Justification for Rev. C Project:
This proposed revision is intended to include standard maintenance following J-STD025-B implementation fixes and improvements from field deployment and possibly CALEA
capabilities resulting from an analysis of Law Enforcements requirements expressed in
various forms (e.g., Electronic Surveillance Needs for Carrier-Grade Voice over
Packet service (CGVoP), IMS/MMD for 3GPP2 systems, support for TIA-835-C Mobile IPv6,
support for Direct Signal Reporting, circuit/packet terminology cleanup, support for
MEID ) and information related to additional Packet Mode technologies.
(Note: A copy of the CGVoP document may be obtained by going to
<http://www.askcalea.net> and clicking on the link in the lower left corner
["askcalea a question"]. When the dialog box comes up, type a request for a copy of
the CGVoP document.)
Neither the requirements, messaging, protocol, or any additional text developed for
the new revision of J-STD-025 is intended to conflict with other lawful intercept
standards for CALEA.
This scope specifically mentions that addition of 3GPP2 IMS/MMD as a new platform we
will be working on. This will also be pointed out in the response letter.
The intended ballot date for this document is Nov 2004 based on earlier input from
the carriers. This will be discussed again at the December meeting.
Scope and Justification for additional LAES capabilities:
Produce a new TIA STD containing the messaging for support of additional LAES
capabilities. Expected sources for contributions on these capabilities include, but
are not limited to, distributed documents from Law Enforcement (e.g., Packet
Surveillance Fundamental Needs Document (PSFND), Electronic Surveillance Needs for
Carrier-Grade Voice over Packet Service (CGVoP)), previous ESTS contributions to the
TR-45 LAES AdHoc Group (e.g., Surveillance Status, Continuity Check Tone, Feature
Status, Non-communication signaling for information services), and carrier and vendor
discussions with LEA (e.g., location tracking, Call Release information, LNP
Considerations). Messages should be able to toggle on/off, as implementations of
these capabilities are optional and to be provided upon request with negotiated
terms. This STD assumes a J-STD-025 embedded architecture, messaging and protocol for
communications surveillance. This standard is not being developed to meet the
requirements of CALEA, and CALEA references are outside the scope.
There is an assumption of covering 3GPP2 IMS systems with this scope.
The intended ballot date for this document is June 2005.
again at the December meeting.
This will be discussed
Call release information is mentioned in this scope. This refers to the direction
the release was initiated, the release cause code, whether the network released the
call, etc.
An example for LNP Considerations would be the port out indicator.
Download