1、 TIA-2001.1-E-3 (Addendum to TIA-2001.1-E) November 2012Interoperability Specification (IOS) for cdma2000Access Network Interfaces- Part 1 Overview NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers
2、and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-me
3、mber of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA
4、in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety p
5、roblems 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 before its use. (From Project No. TIA-PN-2001.1-E-3, form
6、ulated under the cognizance of the TIA TR-45 Mobile (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 u
7、se or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applica
8、tions are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a
9、 party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA 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 pro
10、vided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a s
11、tandard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or let
12、ters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publi
13、cations of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs
14、 or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTAB
15、ILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE S
16、AFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITH
17、OUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, 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 ADVISE
18、D OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-2001.1-E-3 Revision History Date Publication Description June 2007 A.S0011-D v1.0 For fea
19、tures supported, refer to section 1.1. August 2009 A.S0011-D v2.0 Updates to support 1x air interface enhancements, EVRC-WB on A2p, EVRC-NW on A2 and A2p and bug fixes. May 2011 A.S0011-D v3.0 Support for callback of an emergency call origination, EVRC-NW capacity operating point 0, and bug fixes. A
20、ugust 2012 A.S0011-D v4.0 Support for EVRC-B, EVRC-W B, EVRC-NW, EVRC-NW2K, USSD, MSC-BS indication of Device Type and bug fix. TIA-2001.1-E-3 (This page intentionally left blank.) TIA-2001.1-E-3 i Table of Contents 1 2 Foreword iv 3 1.0 Introduction. 1 4 1.1 Overview . 1 5 1.1.1 Purpose 2 6 1.1.2 S
21、cope 3 7 1.2 References . 4 8 1.2.1 Normative References. 4 9 1.2.2 Informative References. 5 10 1.3 Terminology . 5 11 1.3.1 Acronyms 5 12 1.3.2 Definitions. 6 13 1.4 Organization . 10 14 1.4.1 Overall IOS Specifications. 10 15 1.5 Document Layout 11 16 1.6 Documentation Conventions 12 17 1.6.1 Pro
22、cedural Descriptions 13 18 2.0 Interface Model 15 19 2.1 Reference Points A, Ater, Aquinter, Aquater, 48 and 27 15 20 2.2 Interface Reference Model . 15 21 3.0 Information Flows . 19 22 4.0 MS Mobility for Packet Data Service 21 23 24 25 26 TIA-2001.1-E-3 ii List of Figures 1 2 Figure 1.6-1 Document
23、 Convention Example . 13 3 Figure 2.2-1 Reference Model for Circuit-Switched cdma2000 Access Network Interfaces . 16 4 Figure 2.2-2 Reference Model for Packet-based cdma2000 Access Network Interfaces 17 5 Figure 4-1 Levels of Packet Data Mobility . 21 6 7 8 TIA-2001.1-E-3 iii List of Tables 1 2 Tabl
24、e 1.4.1-1 IOS Cross References . 10 3 4 5 TIA-2001.1-E-3 iv Foreword 1 2 The foreword is not part of this document. 3 4 This document was produced by TSG-A of the Third Generation Partnership Project 2. This document was 5 developed in accordance with the procedural guidelines of 3GPP2 and its Organ
25、izational Partners, and 6 represents the consensus position of these groups. 7 8 TIA-2001.1-E-3 1 Section 1 1.0 Introduction 1 2 1.1 Overview 3 This standard describes the overall system functions, including services and features re-4 quired for interfacing a base station (BS) to a Mobile Switching
26、Center (MSC), Mobile 5 Switching Center Emulation (MSCe), Media Gateway (MGW), other BSs, and a Packet 6 Control Function (PCF). It further describes the interface between a PCF and a Packet 7 Data Service Node (PDSN). These interfaces are based on interoperation with the 8 cdma20001 air interface 1
27、6, the wireless IP network 8 and the ANSI-41 core net-9 work 9. 10 This standard is intended to provide sufficient specification of a set of interfaces to 11 support the interoperability of one vendors equipment with that of another. Which 12 interface(s) a vendor chooses to implement is dependent o
28、n business decisions, and is up 13 to each vendor. However conformance to any given interface specified within this 14 standard requires all of the messages and procedures for supported features on that 15 interface to be supported as specified within this standard. Establishing standard 16 interfac
29、es allows the BS, MSC MSCe, MGW , PCF, and PDSN equipment to evolve 17 independently and to be provided by multiple vendors. 18 The following features have been added to this revision of the standard: 19 1x Enhancement support for: 20 Additional geographical location information 21 Flex-duplex chann
30、el 22 A11 Capabilities indication 23 Advanced Encryption Standard, Authentication and Key Agreement 25 makes maximum use of existing standards from the TIA and other sources; 26 promotes reliability enhancement, technical innovation, network product availability, 27 and economic competition; 28 allo
31、ws connection of various manufacturers BSs to the same MSC; 29 supports future MSC and BS implementations; 30 allows the separate evolution of MSC and BS technology. 31 The BS-MGW interface provides a bearer for traffic between a BS and an MGW. The BS 32 and MGW interface, defined as the A2p interfa
32、ce (Reference Point 27), is shown in 33 Figure 2.2-2. 34 The source BS - target BS interface provides for inter-BS soft/softer handoffs. It 35 specifically represents the demarcation point between two BSs which coincides with the 36 Reference Point “Ater”. This point establishes the technical interf
33、ace and designates the 37 test points and operational division of responsibility between the source BS and target 38 BS. The source BS and target BS interface is defined as the A3/A7 interface shown in 39 Figure 2.2-1 and Figure 2.2-2. 40 The BS-PCF interface provides access between the BS and the P
34、acket Control Function 41 for high speed packet data services. It specifically represents the demarcation point 42 TIA-2001.1-E-3 3 Section 1 between the BS and the PCF which coincides with the Reference Point “Aquinter”. This 1 point establishes the technical interface and designates the test point
35、s and operational 2 division of responsibility between the BS and the PCF. The BS -PCF interface is defined 3 as the A8/A9 interface shown in Figure 2.2-1 and Figure 2.2-2. 4 The PCF-PDSN interface provides access between a Packet Control Function and a 5 Packet Data Serving Node for high speed pack
36、et data services. It specifically represents 6 the demarcation point between the PCF and the PDSN which coincides with the 7 Reference Point “Aquater”. This point establishes the technical interface and designates 8 the test points and operational division of responsibility between the PCF and the P
37、DSN. 9 The PCF-PDSN interface is defined as the A10/A11 interface shown in Figure 2.2-1 and 10 Figure 2.2-2. 11 The PCF-PDSN interface definition fulfills the following criteria: 12 allows connection of various manufacturers PCFs to the same PDSN and vice versa; 13 makes maximum use of existing stan
38、dards from the Internet Engineering Task Force 14 (IETF) and other sources; 15 promotes quality of service and accounting information exchange between the PCFs 16 and the PDSNs; 17 promotes reliability enhancement, technical innovation, network product availability, 18 and economic competition; 19 s
39、upports future PCF and PDSN implementations; 20 allows the separate evolution of PCF and PDSN technologies. 21 1.1.2 Scope 22 This standard provides the specification for the interfaces which coincide with the 23 Reference Points “A”, “Ater”, “Aquater”, and “Aquinter” defined in the 3GPP2 Wireless 2
40、4 Network Reference Model shown in I-1 and Reference Points 27 and 48 for Legacy MS 25 Domain Step 1 18 and Reference Points A1, A1p, A2 and A2p for Legacy MS Domain 26 Step 2 19. 27 The scope of this standard includes the following topics: 28 MSC-BS and BS-BS interfaces: 29 descriptions of the spec
41、ified functional capabilities that provide wireless 30 telecommunications services across the MSC-BS and BS-BS interfaces as 31 defined in the 3GPP2 Wireless Network Reference Model; 32 descriptions of the specified functional capabilities that provide wireless tele-33 communications services across
42、 the MSCe-BS and the MGW-BS interfaces; 34 descriptions of the division of responsibility of the functions provided between 35 the BS and the MSC, and between the source BS and the target BS, without 36 prescribing specific implementations; 37 descriptions of the MSC-BS interface and the BS-BS inter
43、face standards that 38 support DS-41 and cdma2000 systems. 39 BS-PCF interfaces: 40 descriptions of the specified functional capabilities that provide packet data 41 services across the BS-PCF interface; 42 TIA-2001.1-E-3 Section 1 4 descriptions of the division of responsibility of the functions pr
44、ovided between 1 the BS and the PCF without prescribing specific implementations. 2 PCF-PDSN interfaces: 3 descriptions of the specified functional capabilities that provide packet data 4 services across the PCF-PDSN interface; 5 descriptions of the division of responsibility of the functions provid
45、ed between 6 the PCF and the PDSN without prescribing specific implementations. 7 The interfaces defined in this standard are specified by a set of characteristics , including: 8 physical and electromagnetic parameters; 9 channel structures; 10 message types and contents; 11 network operating proced
46、ures; 12 user data framing and transport. 13 14 1.2 References 15 References are either normative or informative. A normative reference is used to include 16 another document as a mandatory part of a 3rd Generation Partnership Project 2 (3GPP2) 17 specification. Documents that provide additional non
47、-essential information are included 18 in the informative references section. For consistency within IOS parts, the most 19 commonly referenced documents 117 shall be the same as they appear here in this 20 part, or left as “Reserved” if not used in a particular IOS part. 21 1.2.1 Normative Referenc
48、es 22 The following standards contain provisions which, through reference in this text, 23 constitute provisions of this standard. At the time of publication, the editions indicated 24 were valid. All standards are subject to revision, and parties to agreements based upon 25 this standard are encour
49、aged to investigate the possibility of applying the most recent 26 editions of the standards indicated below. ANSI and TIA maintain registers of currently 27 valid national standards published by them. 28 1 3GPP2 C.S0001-E v3.0, Introduction to cdma2000 Standards for Spread 29 Spectrum Systems, June 2011. 30 2 3GPP2 C.S0002-E v3.0, Physical Layer Standard for cdma2000 Spread 31 Spectrum Systems, June 2011. 32 3 3GPP2 C.S0003-E v3.0, Medium Access Control (MAC) Standard for cdma2000 33 Spread Spec
