1、 J-STD-025-B-2 April 2007 Lawfully Authorized Electronic Surveillance (LAES) Addendum 2-Support for Carrier Identity ANSI/J-STD-025-B-2-2007 APPROVED: APRIL 27, 2007 REAFFIRMATION: APRIL 12, 2012 JOINT STANDARDS Joint Standards and Publications are adopted in accordance with the American National St
2、andards Institute (ANSI) patent policy. By such action, the Telecommunications Industry Association or the Alliance for Telecommunications Industry Solutions does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication.
3、 This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations be
4、fore its use. This standard was developed under Project No. SP-3-4465-UGRV2-RF1, formulated under the cognizance of the TIA TR-45 Committee on Mobile Telephone (703)907-7700; Fax: (703)907-7727 or by email to receptiontiaonline.org. This document was coordinated between ATIS and TIA. A Word from TIA
5、: TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstanding between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the
6、 proper product for his/her particular need. Existence of such Standards and Publications shall not be in any respect preclude any member or nonmember of TIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Public
7、ations preclude their voluntary use by those other than TIA members, whether the standard is to be used either domestically or internationally. TIA Documents contain information deemed to be of technical value to the industry, and are published at the request of the originating Committee without nec
8、essarily following the rigorous public review and resolution of comments which is a procedural part of the development of a American National Standard (ANS). Further details of the development process are available in the TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engin
9、eering_manual.cfm A Word from ATIS: ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More than 200 companies actively formulate standards
10、 in ATIS Forums, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Gro
11、ups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contrib
12、utor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit www.atis.org. NOTICE FROM
13、PATENT HOLDERS The users attention is called to the possibility that compliance with this standard may require use of an invention covered by patent rights. By publication of this standard, no position is taken with respect to the validity of this claim or of any patent rights in connection therewit
14、h. The patent holder has, however, filed a statement of willingness to grant a license under these rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain a license. Details may be obtained from the Telecommunications Industry Association, Alliance for Teleco
15、mmunications Industry Solutions or the American National Standards Institute. Copyright Telecommunications Industry Association 2012 Copyright Alliance for Telecommunications Industry Solutions 2012 All rights reserved This document is subject to change. NOTICE OF COPYRIGHT This document is issued u
16、nder a joint copyright by the Telecommunications Industry Association and the Alliance for Telecommunications Industry Solutions, and may not be reproduced without permission. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyri
17、ght permission. For copyright permission to reproduce portions of this document, please contact TIA Standards Department or go to the TIA website (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/about/faqDetail.cfm?id=18 Organizations may
18、obtain permission to reproduce a limited number of copies by entering into a license agreement. For information, contact: Global Engineering Documents 15 Inverness Way East Englewood, CO 80112-5704 or call U.S.A. and Canada (1-800-854-7179) International (303) 397-7956 OR ATIS Document Center: http:
19、/www.atis.org/docstore/default.aspx Alliance for Telecommunications Industry Solutions 1200 G Street, NW Suite 500 Washington, DC 20005 (202) 628-6380 NOTICE OF DISCLAIMER AND LIABILITY The document to which this Notice is affixed (the “Document”) has been prepared by one or more Engineering Committ
20、ees or Formulating Groups of the Telecommunications Industry Association (“TIA”). In addition, the Document was balloted by ATIS Wireless Technologies and Systems Committee and ATIS Packet Technologies and Systems Committee. TIA is not the author of the Document contents, but publishes and claims co
21、pyright to the Document pursuant to licenses and permission granted by the authors of the contents. TIA Engineering Committees and Formulating Groups are expected to conduct their affairs in accordance with the TIA Engineering Manual (“Manual”), the current and predecessor versions of which are avai
22、lable at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm. The ATIS Wireless Technologies and Systems Committee and ATIS Packet Technologies and Systems Committee is expected to conduct its affairs in accordance with the ATIS Operating Procedures which is available at http:/www.atis.org/
23、legal/op.asp. . TIAs function is to administer the process, but not the content, of document preparation in accordance with the Manual and, when appropriate, the policies and procedures of the American National Standards Institute (“ANSI”). Likewise, ATIS function, and on behalf of its Committees an
24、d Forums, is to administer the process according to its Operating Procedures, but not develop the content of the document. TIA and ATIS do not evaluate, test, verify or investigate the information, accuracy, soundness, or credibility of the contents of the Document. In publishing the Document, TIA a
25、nd ATIS disclaim any undertaking to perform any duty owed to or for anyone. If the Document is identified or marked as a project number (PN) document, or as a standards proposal (SP) document, persons or parties reading or in any way interested in the Document are cautioned that: (a) the Document is
26、 a proposal; (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Docu
27、ment may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. Neither TIA nor ATIS makes any search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and
28、 called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. When IPR consisting of patents are claimed and called to ATISs attention, a statement from the holder thereof is requested, all in accordance with the ATISs Operating Procedures. Neither T
29、IA nor ATIS takes any position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. Neither TIA or ATIS will neither be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved,
30、nor will TIA or ATIS opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its contents. TIA and ATIS d
31、o not enforce or monitor compliance with the contents of the Document. TIA and ATIS do not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOU
32、T LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON-INFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA AND ATIS EXPRESSLY DISCLAIM ANY AND ALL RESPONSIBILITIES FO
33、R THE ACCURACY OF THE CONTENTS AND MAKE NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE
34、 CONTENTS. NEITHER TIA NOR ATIS SHALL BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS,
35、LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS
36、 HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS.ANSI/J-STD-025-B-2 Table of Contents 1. INTRODUCTION.1 2. SCOPE.1 3. SECTION REVISIONS1 Section 5.5.4 - message parameters, cdma2000PacketDataServingSystem message 1 Section 6.5 - module ID and Object Identifier versi
37、on.2 Section 6.5 - message definitions, cdma2000PacketDataServingSystem message 2 Section 6.5 - parameter definitions, CarrierIdentity.2 i ANSI/J-STD-025-B-2 1. Introduction The purpose of this addendum is to add the Carrier Identity information in the cdma2000PacketDataServingSystem message to the
38、ANSI/J-STD-025-B standard to support a subscriber roaming in another network by providing the Carrier Identity. Paragraphs in ANSI/J-STD-025-B that are not shown remain the same. The section numbering in this document aligns with the original sections in ANSI/J-STD-025-B. 2. Scope This addendum only
39、 consists of additions to ANSI/J-STD-025-B adding Carrier Identity information in the cdma2000PacketDataServingSystem message, as follows: a. Page 72, Line 40: Section 5.5.4 cdma2000PacketDataServingSystem message, Table 21 Add CarrierIdentity. b. Page 93, Lines 40 and 52: Section 6.5 Module ID and
40、Object Identifier Update Module ID and Object Identifier. c. Page 95 Line 27: Section 6.5 - message definitions, cdma2000PacketDataServingSystem message - Add CarrierIdentity. d. Page 96 Line 3: Section 6.5 - parameter definitions - Add CarrierIdentity. 3. Section Revisions Text for ANSI/J-STD-025-B
41、 addendum adding Carrier Identity information in the cdma2000PacketDataServingSystem message and parameter definitions: Section 5.5.4 cdma2000PacketDataServingSystem Table 21: cdma2000PacketDataServingSystem Message Parameters Parameter MOC Usage CaseIdentity M Identifies the intercept subject. IAPS
42、ystemIdentity C Include to identify the system containing the IAP when the underlying data carriage does not imply that system. TimeStamp M Time and date that the event was detected. SubjectIPAddress C Provide the IPv4 address assigned for the session: - The Home IPv4 address used for the Mobile IPv
43、4 session; - The Dynamic IPv4 address allocated by the PDSN for Simple IPv4 access, or; - The /64 globally unique prefix assigned to the intercept subject by the PDSN ANSI/J-STD-025-B-2 Parameter MOC Usage for Simple IPv6 access. SubjectIdentity C Observed identity or identities of the subject. Prov
44、ide known identities. ServingSystemIdentity M Identifies the entity that is currently serving the intercept subject. HaIPAddress C IPv4 address of the HA, only provided for Mobile IPv4 access. FaCoA C Foreign Agent provided Care of Address, only provided for Mobile IPv4 access. CarrierIdentity C Pro
45、vide a 5 or 6- byte Identifier of the visited PDSN comprising of a 3 byte Mobile Country Code (MCC) followed by a 2 or 3 byte Mobile Network Code (MNC) of the visited carrier, if known. Section 6.5 cdma2000 Abstract Syntax for Packet Data CII Delivery CDMA2000CIIModule iso(1) member-body(2) us(840)
46、tia(113737) laes(2) tr45(0) cdma2000(1) cii(0) version-2(1) cdma2000CIIModuleID OBJECT IDENTIFIER := iso(1) member-body(2) us(840) tia(113737) laes(2) tr45(0) cdma2000(1) cii(0) version-2(1) cdma2000PacketDataServingSystem := SEQUENCE caseIdentity 0 CaseIdentity, iapSystemIdentity 1 SystemIdentity O
47、PTIONAL, timeStamp 2 TimeStamp, subjectIPaddress 3 IpAddress OPTIONAL, subjectIdentity 4 SubjectId OPTIONAL, servingSystemIdentity 5 SystemIdentity, haIPaddress 6 IpAddress OPTIONAL, faCoA 7 IpAddress OPTIONAL, carrierIdentity 8 CarrierIdentity OPTIONAL - include if known -parameter definitions; CarrierIdentity := Visible String (SIZE (56) -A 5 or 6- byte Identifier of the visited PDSN comprising of a 3 -byte Mobile Country Code (MCC) followed by a 2 or 3 byte -Mobile Network Code (MNC) of the visited carrier. This value is -configured locally in the visited carriers PDSN. 2
