1、 TIA/EIA-828-2001 APPROVED: NOVEMBER 20, 2001 REAFFIRMED: APRIL 16, 2012 TIA/EIA-828 November 2001BTS-BSC Inter- Operability (Abis Interface) NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and pu
2、rchasers, 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-member o
3、f 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 in acc
4、ordance 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 problem
5、s 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. 3-4604-A, formulated under th
6、e 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 use or practice
7、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 applications are claim
8、ed 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 party to discu
9、ssions 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 provided in the Ma
10、nual 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 standard, specif
11、ication, 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 letters of assuran
12、ce 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 publications of the
13、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 or services or
14、 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 MERCHANTABILITY AND ITS N
15、ONINFRINGEMENT 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 SAFETY OR HEALTH
16、 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 WITHOUT LIMITATION
17、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 ADVISED OF THE POSSIB
18、ILITY 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. BTS-BSC Inter-operability (Abis Interface) TIA/EIA-828 Table of Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
19、 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 1. Introduction 1 2. Objectives . 1 2.1 Scope of the document . 1 2.2 References 1 2.2.1 Telecommunications Industry Association (TIA) / Electronics Industry Association (EIA) 1 2.2.2 Standards Committee T1 . 2 2.2.
20、3 International Telecommunications Union - Telecommunications Sector (ITU-T). 2 2.2.4 Other . 2 Terminology 3 2.3 Acronyms. 3 2.4 Others. 4 3. Network Reference Model and Interfaces . 5 3.1 Support of user traffic connections to a frame selector function 8 3.2 Support of paging channel messaging 8 3
21、.3 Support of Access channel messaging 9 3.4 Support of broadcast system information functions. 9 3.5 Layers 1 Inter-operability Specification (IOS) for CDMA 2000 Access Network Interfaces (also referenced as 3GPP2 TSG-As A.S0001); December, 2000. TIA/EIA/IS-95B; Mobile Station - Base Station Compat
22、ibility Standard for Dual-Mode Wideband Spread Spectrum Cellular Systems; March, 1999 1TIA/EIA-828 BTS-BSC Inter-operability (Abis Interface) 1.2.2 Standards Committee T1 1 2 3 ANSI T1.627 - 1993, B-ISDN - ATM Layer Functionality and Specification, 1993. 1.2.3 International Telecommunications Union
23、- Telecommunications Sector (ITU-T) 4 5 6 7 8 9 10 11 12 13 ITU-T Recommendation I.363.2, B-ISDN ATM Adaptation layer specification: Type 2 AAL; September, 1997. ITU-T Recommendation I.363.5, B-ISDN ATM Adaptation Layer specification: Type 5 AAL; August, 1996. ITU-T Recommendation I.366.1; Segmentat
24、ion and Reassembly Service Specific Con-vergence Sublayer for the AAL type 2; June, 1998. ITU-T Recommendation Q.2931, Broadband-Integrated Services Digital Network (B-ISDN) Digital Subscriber Signalling No. 2 (DSS2) User-Network Interface Layer 3 Specification for Basic Call/Connection Control, 199
25、5. 1.2.4 Other 14 15 16 17 18 Internet Engineering Task Force, RFC 791 - Internet Protocol (IP), 1981. Internet Engineering Task Force, RFC 793 - Transmission Control Protocol (TCP), 1981. 2 BTS-BSC Inter-operability (Abis Interface) TIA/EIA-828 Terminology 1 2 1.3 Acronyms 3 4 5 6 7 8 9 10 11 12 13
26、 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 The following is a list of acronyms that are used in this specification text. AAL2 ATM Adaptation Layer type 2 AAL5 ATM Adaptation Layer type 5 ADDS Application Data Delivery Service ANSI American National Standards Insti
27、tute ARFCN Absolute Radio Frequency Channel Number ATM Asynchromous Transfer Mode BSC Base Station Controller BSMAP Base Station Management Application Part BTS Base Transceiver System CC Conference Calling CCITT International Telegraph and Telephone Consultative Committee (See ITU) CDMA Code Divisi
28、on Multiple Access CID Circuit IDentifier (used with reference to AAL2) CM Connection Management cUDP compressed IP/UDP FCH Fundamental Channel IETF Internet Engineering Task Force IMSI International Mobile Subscriber Identity IOS Interoperability Specification IP Internet Protocol ISDN Integrated S
29、ervices Digital Network ISLP Intersystem Link Protocol ITU International Telecommunications Union kb kilo bits LAC Location Area Code LSB Least Significant Bit MAC Medium Access Control MIN Mobile Identification Number MS Mobile Station MSB Most Significant Bit MSC Mobile Switching Center OAM&P Oper
30、ations, Administration, Maintenance, and Provisioning OTD Orthogonal Transmit Diversity PACA Priority Access and Channel Assignment 3TIA/EIA-828 BTS-BSC Inter-operability (Abis Interface) PATE Packet Arrival Time Error 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 PCF Packet Control
31、 Function PCM Pulse Code Modulation PN Pilot Number PPP Point to Point Protocol PSPDN Packet Switched Public Data Network PSTN Public Switched Telephone Network QoS Quality of Service RAND Random Variable RFC Request for Comment RLP Radio Link Protocol SCH Supplemental Channel SCM Service Connect Me
32、ssage SCTP Stream Control Transmission Protocol SDU Selection/Distribution Unit function SMS Short Message Service SMS-MO SMS Mobile Originated SMS-MT SMS Mobile Terminated SSCS Service Specific Convergence Sublayer SSD Shared Secret Data SSSAR Service Specific Segmentation and Reassembly TCP Transm
33、ission Control Protocol UDP User Datagram Protocol 1.4 Others 25 26 27 28 1) In this document the term “cell” is used to refer to a sector with in a cell. 2) The messages indicated with solid lines flow over the Abis interface and the messages indicated with dashed lines flow over interfaces other t
34、han the Abis interface. 4 BTS-BSC Inter-operability (Abis Interface) TIA/EIA-828 2. Network Reference Model and Interfaces 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Figure 4-1 shows the network reference model that is referred to in this specification. Abis Signaling Abis
35、TrafficAbis Signaling Abis Traffic BTS BTS B S Abis Interface BSC SDU FunctionCH element CH elementFigure 4-1 Reference Model a) Abis interface = Abis signaling + Abis traffic b) A Selection Distribution Unit (SDU) function is located in the BSC c) A channel element is located in the BTS Notes: The
36、handoff procedure between BTSs within a BSC is defined in this document. The handoff procedure between the BSs has been defined in TIA/EIA/IS-2001. There are 2 architecture for the L2 terminations were considered. They are shown in the following Table 4-1. L r-csch(*1) f-csch(*2) Type A Type BL3 L3
37、L3Authentication BSC ARQ ARQAddressing Addressing Utility UtilityLAC SAR SAR L2 MAC MAC MACBSC L1 L1 L1 BTS BTS Table 4-1 Layer 2 termination type 27 28 29 30 31 (*1) r-csch (reverse common signaling logical channel) This logical channel is applied for the case that MS sends message on the ACH and B
38、TS replies on the PCH. In r-csch, LAC sub-layer is composed by Authentication sub-layer, ARQ sub-layer, Addressing sub-layer, Utility sub-layer and SAR sub-layer. 5TIA/EIA-828 BTS-BSC Inter-operability (Abis Interface) (*2) f-csch (forward common signaling logical channel) 1 2 3 4 5 6 7 8 9 10 11 12
39、 13 14 15 16 This logical channel is applied for the case that BTS sends message on the PCH and MS replies on the ACH. In f-csch, LAC sub-layer is composed ARQ sub-layer, Addressing sub-layer, Utility sub-layer and SAR sub-layer. In this specification type A is introduced as architecture for initial
40、 phase. However we are also introducing type B for the next release. In this release of the Abis specification L2 termination is mandatory to be supported by the BTS. To allow for a migration to new architectures, a mechanism is provided on the Abis interface whereby the BTS can specify if L2 termin
41、ation function will be supported. If the BTS indicates that it does not support L2 termination, then the BSC shall support L2 termination. In this release of the Abis specification the BTS shall specify to the BSC that it terminates L2 termination. 6 BTS-BSC Inter-operability (Abis Interface) TIA/EI
42、A-828 1 2 3 4 5 6 7 8 BSCBTSAbis SignalingOAM SignalingMSFCH (f/r-dsch, f/r-dtch)SCH (f/r-dtch)DCCH (f/r-dsch, f/r-dtch)ACH (r-csch)PCH (f-csch)Abis InterfaceDCCH (Abis-IS-2000 DCCH Fwd/Rvs)FCH (Abis-IS-2000 FCH Fwd/Rvs)SCH (Abis-IS-2000 SCH Fwd/Rvs)PCH (Abis-PCH Msg Transfer)ACH (Abis-ACH Msg Trans
43、fer)Air Interface(FFS)BSAbis SignalingAbis trafficFigure 4-2 shows the relationship between logical air interface channels and Abis interface signal Note: This figure is informative. In this figure, some signals defined in the air interface are omitted for clarity. Figure 4-2 Relationship between Ai
44、r interface and Abis interface (Intra-BS Model) 7TIA/EIA-828 BTS-BSC Inter-operability (Abis Interface) Table 4-2 summaries the details of the Abis interface 1 2 3 Table 4-2 Abis interface description Abis function Transaction Abis Message (A7/A3 message related to Abis) Abis connection establish (B
45、SC invoke) - call setup - Handoff - Abis-BTS Setup - Abis-BTS Setup Ack - Abis-Connect - Abis-Connect Ack (A7-HO Req.) (A7-HO Req. Ack) (A3-Connect) (A3-Connect Ack) Abis connection release (BSC invoke) - call release - Handoff - Abis-BTS Release - Abis-BTS Release Ack - Abis-Remove - Abis-Remove Ac
46、k (A7-Drop) (A7-Drop Ack) (A3-Remove) (A3-Remove Ack) Abis connection release (BTS invoke) - Abis-BTS Release Request - Abis-BTS Release - Abis-BTS Release Ack - Abis-Remove - Abis-Remove Ack (A7-Tgt rm. req.) (A7-Drop) (A7-Drop Ack) (A3-Remove) (A3-Remove Ack) PCH transfer - Abis-PCH Msg Transfer -
47、 Abis-PCH Msg Transfer Ack (A7-PCH .) (A7-PCH . Ack) ACH transfer - Abis-ACH Msg Transfer (A7-ACH .) SCH transfer and establish - SCH setup - Abis-Burst Request - Abis-Burst Response -Abis-Burst Commit (A7-Burst Req.) (A7-Burst Rsp.) (A7-Burst Commit) 4 2.1 Support of user traffic connections to a f
48、rame selector function 5 6 7 8 9 10 11 12 13 In a CDMA system, the user traffic (voice, data, etc.) of a Mobile Station (MS) may be connected to the network using one or more connections from MS to BTS(s). If multiple connections are used for a single flow of user information, the user traffic conne
49、ction is said to be in soft handoff. The first step within the network is to carry these multiple connections back to a single point from which a selection is made of the “best” frame received over the radio connections. This implies a connection from each involved BTS back to a central point where frame selection occurs. This central point is referred to as the “SDU function.” 2.2 Support of paging channel messaging 14 15 16 17 18 19 20 21 When an MS is to be sent a message on a paging channel, the BSC typically formats the majority of the message and forwards it to the BTS along with va
