TIA-1180-2010 Interoperability Specification (IOS) for MSC Pool Network《MSC Pool网络的互操作性规范(IOS)》.pdf

1、 TIA-1180 March 2010Interoperability Specification (IOS) for MSC Pool Network NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of pro

2、ducts, 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 of TIA from manufacturing or selling products not conforming to s

3、uch 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 accordance with the American National Standards Institute (ANSI) pa

4、tent 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 problems associated with its use or all applicable regulatory requireme

5、nts. 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 Standards Proposal No. 3-0355.200, formulated under the cognizance of the TIA TR-45.4 -Radio to Switching

6、 Technology - Mobile and Personal Communications Standards) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND EN

7、GINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document is copyrighted by the TIA. Reproduction of these documents either in

8、 hard copy or soft copy (including posting on the web) is prohibited without copyright 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 a

9、re located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright OR Telecommunications Industry Association Standards (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, m

10、odified or changed in the standards development or any editing process. The use 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

11、 for IPR. When IPR consisting of patents and published pending patent applications 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 in

12、quire into, the scope or validity of any claims of IPR. TIA will neither be a 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. TI

13、A 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. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the fo

14、rmulation, development or publication of standards (whether designated as a standard, 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 ob

15、ligation to search or investigate the records of any other SSO for IPR or letters 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 s

16、hall apply; and (iii) Information as to claims of IPR in the records or publications 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. T

17、IA does 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 WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, I

18、TS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY 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

19、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 CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING

20、 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, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY

21、, 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 HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. Revision History

22、 Date Publication Description December 2009 A.S0018-0 v1.0 Initial revision. For features supported, refer to section 1.1. 1 2 3 4 (This page intentionally left blank) TIA-1180 i 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 27 28 29 30 31 32 33 34 35 36 Table of Contents Fore

23、word. v 1 Introduction.1-1 1.1 Overview.1-1 1.1.1 Purpose1-1 1.1.2 Scope.1-1 1.1.3 Document Convention 1-1 1.2 References.1-1 1.2.1 Normative References.1-1 1.2.2 Informative References.1-2 1.3 Terminology1-2 1.3.1 Acronyms1-2 1.3.2 Definitions 1-3 1.4 MSC Pool Network IOS Architecture Reference Mod

24、el1-3 1.4.1 Protocol-based MSC Pool Network IOS Architecture Reference Model.1-3 1.4.1.1 Protocol-based MSC Pool Interfaces 1-4 1.4.1.2 Protocol-based MSC Pool Architectural Principles1-5 1.4.2 OA that a certain course of action is preferred but not necessarily required; or (in the negative form) th

25、at a certain possibility or course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the standard. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical, or causal. 22 23 24 25

26、 26 27 28 1.2 References 29 References are either normative or informative. A normative reference is used to include another doc-ument as a mandatory part of a 3GPP2 specification. Documents that provide additional non-essential in-formation are included in the informative references section. 30 31

27、32 1.2.1 Normative References 33 The following standards contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based upon this d

28、ocument are encouraged to investigate the possibility of applying the most recent editions published by them. ANSI and TIA maintain registers of currently valid national standards published by them. 34 35 36 37 38 TIA-1180 1-2 2 6 1 3GPP2: A.S0014-D v2.0, Interoperability Specification (IOS) for cdm

29、a2000 Access Network 1 Interfaces Part 4 (A1, A1p, A2, and A5 Interfaces), August 2009. 2 3GPP2: X.S0012-0 v2.0, Legacy MS Domain Step 1, March 2004. 3 3 3GPP2: X.S0025-0 v1.0, Legacy MS Domain Step 2, February 2006. 4 4 ITU-T: H.248.1, Gateway Control Protocol: Version 3, September 2005. 5 1.2.2 In

30、formative References 7 None. 8 9 1.3 Terminology 10 This section contains definitions, symbols and abbreviations that are used throughout the document. 11 1.3.1 Acronyms 12 3GPP2 3rdGeneration Partnership Project 2 BS Base Station BSC Base Station Controller BSMAP Base Station Management Application

31、 Part CIC Circuit Identity Code CN Core Network DTAP Direct Transfer Application Part HLR Home Location Register IE Information Element IMSI International Mobile Subscriber Identity IOS Interoperability Specification LMSD Legacy MS Domain MGW Media Gateway MS Mobile Station MSC Mobile Switching Cent

32、er MSCe Mobile Switching Center Emulator NRI Network Reference Identifier OA and 2) discards connection-oriented messages that are received from the BSC. If the SNSF is co-located with the BSC, the SNSF shall pass the message to the BSC via internal interfaces. Regarding the Reset message sent by th

33、e BSC, the SNSF shall send the message to each MSCe in the PA. 5. For facility management messages other than Reset, the SNSF obtains the network address of the 24 BSC and the circuit identifier from the received A1 message. The SNSF shall then route the message to the Selected Serving MSCe accordin

34、g to a configured mapping between the obtained information and the MSCe address. The SNSF shall await the arrival of the associated acknowledgement from the MSCe or the BSC prior to sending an acknowledgement to the corresponding BSC or MSCe. This is to ensure that the received acknowledgement is an

35、 indication that the MSCe or BSC responded to the original message and not that the SNSF received the message. 6. The optional capability of the BS to request a preferred terrestrial circuit in the CM Service Request 31 message is not supported by the MSC Pool feature. In any case of uplink message

36、handling, the SNSF shall assert the network address (e.g., SS7 signaling point code) of the source BSC as the source network address of the message that is transmitted to the selected MSCe. In the event of complete SNSF node failure, all of the BSs connected to the SNSF will be unable to support tra

37、ffic. In such an event, message type-specific recovery procedures currently specified in A.S0014 1 for timer expiration are invoked at the MSCe or BSC as appropriate. Table 1.6.2-1 identifies the source of the NRI for each uplink A1p message, based on message characteristics and SNSF routing behavio

38、r. Table 1.6.2-1 NRI Source for A1p Uplink Messages Message Name SUA Message Source of the NRI Message Discriminator Additional Service Request CODT SUA LR DTAP ADDS Deliver CODT SUA LR DTAP ADDS Deliver Ack CODT SUA LR DTAP ADDS Page Ack CLDT TAG BSMAP TIA-1180 1-8 Message Name SUA Message Source o

39、f the NRI Message Discriminator ADDS Transfer CLDT IMSI BSMAP Assignment Complete CODT SUA LR BSMAP Assignment Failure CODT SUA LR BSMAP Authentication Report CODT SUA LR DTAP CODT SUA LR DTAP Authentication Response CLDT TAG BSMAP Base Station Challenge CODT SUA LR DTAP Bearer Update Required CODT

40、SUA LR BSMAP Bearer Update Response CODT SUA LR BSMAP BS Authentication Request CODT SUA LR BSMAP BS Security Mode Request CLDT IMSI BSMAP BS Service Request CLDT IMSI BSMAP Clear Complete CODT SUA LR BSMAP Clear Request CODT SUA LR BSMAP CM Service Request CORE IMSI DTAP CM Service Request Continua

41、tion CODT SUA LR DTAP Connect CODT SUA LR DTAP Event Notification Ack CLDT IMSI BSMAP Feature Notification Ack CLDT TAG BSMAP Flash with Information CODT SUA LR DTAP Flash with Information Ack CODT SUA LR DTAP Handoff Commenced CODT SUA LR BSMAP Handoff Complete CODT SUA LR BSMAP Handoff Failure COR

42、EF SUA LR BSMAP Handoff Performed CODT SUA LR BSMAP Handoff Request Acknowledge COAK SUA LR BSMAP Handoff Required CODT SUA LR BSMAP Location Updating Request CORE IMSI DTAP PACA Command Ack CODT SUA LR BSMAP PACA Update CLDT IMSI BSMAP PACA Update Ack CLDT IMSI BSMAP Paging Response CORE TAG DTAP P

43、arameter Update Confirm CODT SUA LR DTAP Privacy Mode Complete CODT SUA LR BSMAP Radio Measurements for Position Response CODT SUA LR BSMAP CODT SUA LR DTAP Rejection CLDT TAG BSMAP Reset CLDT 1BSMAP Reset Ack CLDT BSMAP TIA-1180 1-9 Message Name SUA Message Source of the NRI Message Discriminator C

44、ODT SUA LR DTAP Security Mode Response CLDT TAG BSMAP Service Release CODT SUA LR DTAP Service Release Complete CODT SUA LR DTAP SSD Update Response CODT SUA LR DTAP CODT SUA LR DTAP Status Response CLDT TAG BSMAP User Zone Update Request CODT SUA LR DTAP Note 1: The NRI concept does not apply for t

45、he Reset message. 1 1.6.3 Network Reference Identifier 2 This section specifies the format of the Network Reference Identifier (NRI) when placed within the Tag IE and when placed within the Local Reference. The NRI is used for target node identification by the SNSF when handling Direct Transfer Appl

46、ication Part (DTAP) or Base Station Management Application Part (BSMAP) messages traveling in the uplink (BS-to-MSC) direction. 3 4 5 6 7 8 9 The NRI bits may be placed within the Tag IE as illustrated in Figure 1.6.3-1. Actual placement of the NRI within the Tag IE is an operator concern. 7 6 5 4 3

47、 2 1 0 Octet Tag: A1 Element Identifier 1 NRI 2 3 4 5 Figure 1.6.3-1 Identification of NRI within Tag IE 10 11 12 13 The NRI bits may be placed within the Local Reference as illustrated in Figure 1.6.3-2. Actual placement of the NRI within the Local Reference is an operator concern. 23 22 21 20 19 1

48、8 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 NRI Figure 1.6.3-2 Identification of NRI within Local Reference 14 1.6.4 Load Redistribution 15 There are situations where an MSCe in a PA may be out of service (e.g., when an MSCe is maintained or upgraded by the operator). This entity is known as the f

49、ailure MSCe. The re-distribution procedure can be used to redistribute the load from the failure MSCe to other MSCe nodes in the PA in an orderly manner. Load re-distribution does not require any specific functionality in the MS. 16 17 18 19 20 21 22 Re-distribution of MSs is initiated by the OM&P system. The OM&P system shall notify all SNSFs in the PA which MSCe is going to be off-loaded and trigger all SNSFs to update configuration information. The SNSF shall distribute the load based on the updated configuration thereafter. TIA-1180 1-10 1 2 3 4 Eventually, mo