1、 TIA-1154-1 February 2010(Addendum to TIA-1154) System Requirements for MSC Pool 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
2、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 of TIA from manufacturing or selling products not conforming t
3、o 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 accordance with the American National Standards Institute (ANSI)
4、 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 problems associated with its use or all applicable regulatory requir
5、ements. 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-0334-AD1, formulated under the cognizance of the TIA TR-45.8Core Networks Com
6、mittee.) 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 ENGINEERING PUBLICATIONS or call IHS, USA and Canada
7、(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 hard copy or soft copy (including posting on the w
8、eb) 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 are located at: http:/www.tiaonline.org/standards/ca
9、talog/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, modified or changed in the standards development or
10、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 for IPR. When IPR consisting of patents and publis
11、hed 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 inquire into, the scope or validity of any claims of
12、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. TIA does not warrant or represent that procedures or
13、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 formulation, development or publication of standards
14、(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 obligation to search or investigate the records of an
15、y 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 shall apply; and (iii) Information as to claims of I
16、PR 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. TIA does not certify, inspect, test or otherwise inv
17、estigate 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, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURP
18、OSE 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 CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RU
19、LE 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 FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAI
20、NED 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, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR
21、 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. 2009 3GPP2 EDITOR 1 2 Zhiming Li, Huawei, 3 Lee Valerius, Huawei,
22、 4 5 REVISION HISTORY 6 7 REVISION HISTORY Version 1.0 Initial publication 30 Oct,2008 Ver sion 2.0 Version update to support Legacy CS in addition to LMSD architecture. 05 November 2009 S.R0136-0 v2.0 System Requirements for MSC Pool 2009 3GPP2 ii Table of Contents 1 2 Table of Contents ii 3 List o
23、f Tables iii 4 List of Figures iv 5 1 INTRODUCTION AND SCOPE .1 6 2 REFERENCES 1 7 2.1 Normative Reference .1 8 2.2 Informative References 1 9 3 DEFINITIONS AND ABBREVIATIONS .1 10 4 GENERAL FEATURE DESCRIPTION .2 11 4.1 Scenarios for MSC Pool .2 12 5 DETAILED REQUIREMENTS 3 13 5.1 System Requiremen
24、ts .3 14 5.2 Operation, Administration, Maintenance and Provisioning 15 Requirements .4 16 5.3 System Design Goals 4 17 18 19 System Requirements for MSC Pool S.R0136-0 v2.0 2009 3GPP2 iii List of Tables 1 None. 2 3 S.R0136-0 v2.0 System Requirements for MSC Pool 2009 3GPP2 iv List of Figures 1 None
25、2 S.R0136-0 v2.0 System Requirements for MSC Pool 2009 3GPP2 Page 1 1 1 INTRODUCTION AND SCOPE 2 This document specifies the requirements necessary to support MSC Pool 3 in the CDMA200017 wireless network. MSC Pool enables signaling 4 connections between one BSC with multiple MSCs, so the MS served
26、by 5 any BSC of that pool area can be served by any MSC in that pool area. 6 The Serving Node Selection Function (SNSF) is the key functionality for 8 the MSC Pool application. The main function of SNSF is selecting a 9 serving MSC within the MSC Pool for a given user, and routing the 10 signaling b
27、etween the MSC and the BSC. 11 12 2 REFERENCES 13 Unless explicitly stated in the reference, references are to the latest 14 revision, addendum, version, or date. The document references which are 15 applicable to this specification include the following: 16 2.1 Normative Reference 17 18 1. 3GPP2 N.
28、S0005-0 v1.0, X.S0004-E v1.0, “Radiotelecommunications 19 intersystem Operations”, July 1997 20 2. 3GPP2: A.S001114-D v1.0, Interoperability Specification (IOS) for 21 cdma2000 Access Network Interfaces, July 2007. 22 23 2.2 Informative References 24 None. 25 3 DEFINITIONS AND ABBREVIATIONS 26 The t
29、erms and abbreviations which are used within this specification are 27 defined as follows: 28 MSC Pool: An MSC Pool is a set of MSCs or a set of MSCes to which a set 29 of BSCs can connect. An MSC Pool cannot contain a mixture of MSCs 30 and MSCes. 31 1cdma2000is the trademark for the technical nome
30、nclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States S.R0136-0 v2.0 System Requirements for
31、 MSC Pool 2009 3GPP2 Page 2 Pool Area: A Pool Area is a geographical area which consists of radio 1 coverage of a set of BSCs connected to an MSC pool. Within the Pool area, 2 an MS does not need to change the serving MSC or MSCe. 3 4 BSC Base Station Controller HRPD High Rate Packet Data LMSD Legac
32、y MS Domain LAC Location Area Code MS Mobile Station MSC Mobile Switching Center MSCe Mobile Switching Center Emulator PA Pool Area SNSF Serving Node Selection Function 5 4 GENERAL FEATURE DESCRIPTION 6 MSC Pool feature uses per-user signaling connections between a BSC 7 and any one MSC or MSCe with
33、in the MSC pool with the aid of SNSF. An 8 MSC pool may contain either MSC(s) or MSCe(s), but not both MSC(s) 9 and MSCe(s), within the same pool. This allows a more flexible network 10 topology, so if an MSC or MSCe goes out of service, it does not cause an 11 entire geographic area assigned to tha
34、t node to be out of service. 12 For an MS which registers in a Pool Area (PA), the SNSF will select a 13 serving MSC or MSCe. The MS is served by this serving MSC or MSCe as 14 long as it is within the PA until load redistribution occurs. When load 15 redistribution is needed (e.g., when an MSC or M
35、SCe is maintained or 16 upgraded by the operator, is overloaded, or breaks down), the load 17 associated with the node will be redistributed to other nodes. All SNSFs 18 in the PA do not assign any load on the MSC or MSCe until it is 19 recovered. The MSC Pool feature is not intended to be supported
36、 20 between and amongst multiple operators. For certain operator scenarios, 21 for the purpose of load re-balance, the re-registration may be required. 22 23 4.1 Scenarios for MSC Pool 24 This section gives some scenarios when a network operator will wish to 25 apply the MSC Pool mechanism. 26 27 S.
37、R0136-0 v2.0 System Requirements for MSC Pool 2009 3GPP2 Page3 Scenario 1: When a Mobile Station (MS) moves within the Pool Area, the 1 serving MSC or MSCe need not change. Hence the signaling traffic of re-2 registration could be reduced. 3 Scenario 2: The Core network can be expanded easier and ca
38、n be scaled 4 between the radio network and core network. For example, the operator 5 could expand Core Network capacity by only introducing a new MSC or 6 MSCe without new BSC(s). Additionally, side benefit is load balance. 7 8 5 DETAILED REQUIREMENTS 9 The requirements contained in this section ma
39、y be implemented in a 10 phased manner during the development of the stage 2 and stage 3 11 specifications. 12 5.1 System Requirements 13 SYS-01: It shall be possible to connect between SNSF and any MSC or 14 MSCe in the Pool. 15 SYS-02: An MSC or MSCe within the MSC pool shall be able to 16 support
40、 both MSC pool configuration and legacy 17 configuration. 18 SYS-03: A BSC within the MSC pool configuration shall be able to 19 support both MSC pool configuration and legacy 20 configuration. 21 SYS-04: SNSF shall be able to select an MSC or MSCe as a serving 22 node for a subscriber within the MS
41、C Pool configuration 23 based on a selection algorithm which includes the load 24 redistribution capability. 25 SYS-05: It shall be possible for the operator to choose the selection 26 algorithm used by SNSFs. 27 SYS-06: An MS shall be served by a selected MSC or MSCe, known as 28 the default MSC/MS
42、Ce, for the life of the registration within 29 the PA even if the MS crosses the BSC boundary within the 30 MSC Pool area. 31 SYS-07: It shall be possible to redistribute the MSs from the current 32 serving node/failure node to a new serving node within the 33 MSC pool, a new serving node provides t
43、he functions decribed 34 in SYS-06. 35 S.R0136-0 v2.0 System Requirements for MSC Pool 2009 3GPP2 Page 4 SYS-08: MSC Pool network entities shall be able to interoperate with 1 non-MSC Pool network entities without any impact on the 2 non-MSC Pool network entities (e.g., trunking group 3 procedures,
44、handoff procedures). 4 SYS-09: This feature shall not create any impacts to deployed non-5 MSC Pool network interfaces or entities that support 1. 6 SYS-10: Deployment of this feature shall be possible such that 7 adjacent non-MSC Pool MSCs or MSCes can interoperate with 8 MSC Pool MSCs or MSCes wit
45、hout modification of procedures 9 of the non-MSC Pool entities. 10 SYS-11: It shall be possible to deploy this feature in such a way that 11 an HRPD system that spans both the MSC Pool Area and 12 non-MSC Pool Area can operate without modification, and 13 without modification to standard procedures
46、for handoff from 14 HRPD to cdma2000 1x. 15 SYS-12: Introduction of MSC pool shall not impact any of the existing 16 Circuit Switched (CS) services supported by current IOS 17 specification2. 18 SYS-13: MSC Pool shall support legacy cdma2000 1x MS. 19 20 5.2 Operation, Administration, Maintenance an
47、d Provisioning 21 Requirements 22 OAM&P-01: The OAM&P system shall be able to trigger load redistribution 23 from one MSC/MSCe to other MSC/MSCe(s) in the MSC Pool. 24 OAM&P-02: It shall be possible to allow the BSC to be configured with a 25 new SNSF when the current SNSF is unavailable. 26 27 5.3
48、System Design Goals 28 GOALS-01: When one MSC or MSCe in an MSC Pool breaks down, the 29 interruption time for users being registered in this node should 30 be minimized. In other words, another MSC or MSCe within 31 the MSC Pool shall take over the communication services (e.g., 32 call origination, call delivery, etc.) from this node as quickly as 33 possible. 34 GOALS-02: The SNSF should consider load balancing when selecting a 35 serving MSC or MSCe. 36
