1、 4 TIA-1154 March 2010System 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 products, and assisting th
2、e 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 such Standards and Publi
3、cations. 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) patent policy. By such ac
4、tion, 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 requirements. It is the responsi
5、bility 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, formulated under the cognizance of the TIA TR-45.8 -Core Networks - Mobile and Personal Communica
6、tions 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 ENGINEERING PUBLICATIONS or call IHS, USA and
7、 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 hard copy or soft copy (including posting
8、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 are located at: http:/www.tiaonline.org/stan
9、dards/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, modified or changed in the standards develop
10、ment 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 for IPR. When IPR consisting of patents an
11、d 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 inquire into, the scope or validity of any cl
12、aims 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. TIA does not warrant or represent that proced
13、ures 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 formulation, development or publication of st
14、andards (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 recor
15、ds 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 shall apply; and (iii) Information as to cla
16、ims 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. TIA does not certify, inspect, test or other
17、wise 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, ITS FITNESS OR APPROPRIATENESS FOR A PARTICU
18、LAR 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 CONTENTS COMPLIANCE WITH ANY APPLICABLE STA
19、TUTE, 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 FROM OR RELATING TO ANY USE OF THE CONTENT
20、S 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, TORT (INCLUDING NEGLIGENCE), PRODUCT LIAB
21、ILITY 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. S.R0136-0 v1.0 System Requirements for MSC Pool EDITOR 1 2
22、3 4 5 Zhiming Li, Huawei, REVISION HISTORY 6 REVISION HISTORY Version 1.0 Initial publication 30 Oct,2008 2008 3GPP2 ii System Requirements for MSC Pool S.R0136-0 v1.0 Table of Contents 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Table of Contents . iii List of Tables iv List of Figures . v 1 I
23、NTRODUCTION AND SCOPE .1 2 REFERENCES 1 2.1 Normative Reference .1 2.2 Informative References 1 3 DEFINITIONS AND ABBREVIATIONS 1 4 GENERAL FEATURE DESCRIPTION .2 4.1 Scenarios for MSC Pool .2 5 DETAILED REQUIREMENTS 3 5.1 System Requirements .3 5.2 Operation, Administration, Maintenance and Provisi
24、oning Requirements .4 5.3 System Design Goals 4 2008 3GPP2 iii S.R0136-0 v1.0 System Requirements for MSC Pool List of Tables 1 2 3 None. 2008 3GPP2 iv System Requirements for MSC Pool S.R0136-0 v1.0 2008 3GPP2 v 1 2 List of Figures NoneS.R0136-0 v1.0 System Requirements for MSC Pool 1 3 4 5 6 7 8 9
25、 10 11 12 13 15 16 17 19 20 21 22 23 24 26 28 29 30 31 1 INTRODUCTION AND SCOPE 2 This document specifies the requirements necessary to support MSC Pool in the CDMA20001wireless network. MSC Pool enables signaling connections between one BSC with multiple MSCs, so the MS served by any BSC of that po
26、ol area can be served by any MSC in that pool area MSC Pool is built upon to the Legacy Mobile Station Domain architecture. Serving Node Selection Function (SNSF) is the key functionality for MSC Pool application. The main function of SNSF is selecting a serving MSC within MSC Pool for a given user,
27、 and routing the signaling between the MSC and the BSC. 2 REFERENCES 14 Unless explicitly stated in the reference, references are to the latest revision, addendum, version, or date. The document references which are applicable to this specification include the following: 2.1 Normative Reference 18 1
28、. 3GPP2 N.S0005-0 v1.0, X.S0004-E v1.0, “Radiotelecommunications intersystem Operations”, July 1997 2. 3GPP2: A.S001114-D v1.0, Interoperability Specification (IOS) for cdma2000 Access Network Interfaces, July 2007. 2.2 Informative References 25 None. 3 DEFINITIONS AND ABBREVIATIONS 27 The terms and
29、 abbreviations which are used within this specification are defined as follows: MSC pool: An MSC Pool is a set of MSCes to which a set of BSCs can connect. 1cdma2000is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2.
30、 Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States 2008 3GPP2 Page 1 S.R0136-0 v1.0 System Requirements for MSC Pool Pool Area: A Pool Area is a geographical area which consists of radi
31、o coverage of a set of BSCs connected to an MSC pool. Within the Pool area, an MS does not need to change the serving MSCe. 1 2 3 4 5 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 24 25 26 BSC Base Station Controller HRPD High Rate Packet Data LMSD Legacy MS Domain LAC Location Area Code MS Mobile St
32、ation MSC Mobile Switching Center MSCe Mobile Switching Center Emulator PA Pool Area SNSF Serving Node Selection Function 4 GENERAL FEATURE DESCRIPTION 6 MSC Pool feature uses per-user signaling connections between a BSC and any one MSCe within the MSC pool with the aid of SNSF. This allows a more f
33、lexible network topology, so if an MSCe goes out of service, it does not cause an entire geographic area assigned to that MSCe to be out of service. For an MS which registers in a Pool Area (PA), the SNSF will select a serving MSCe. The MS is served by this serving MSCe as long as it is within the P
34、A until load redistribution occurs. When load redistribution is needed (e.g., when a MSCe is maintained or upgraded by the operator, is overloaded, or breaks down), the load associated with the MSCe will be redistributed to other MSCes. All SNSFs in the PA do not assign any load on the MSCe until it
35、 is recovered. MSC Pool feature is not intended to be supported between and amongst multiple operators. For certain operator scenarios, for the purpose of load re-balance, the re-registration may be required. 4.1 Scenarios for MSC Pool 23 This section gives some scenarios when a network operator wil
36、l wish to apply the MSC Pool mechanism. 2008 3GPP2 Page 2 S.R0136-0 v1.0 System Requirements for MSC Pool Scenario 1: When a Mobile Station (MS) moves within the Pool Area, the serving MSCe need not change. Hence the signaling traffic of re-registration could be reduced. 1 2 3 4 5 6 7 8 10 11 12 14
37、15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 Scenario 2: Core network can be expanded easier and can be scaled between the radio network and core network. For example, operator could expand Core Network capacity by only introducing a new MSCe without new BSC(s). Additional
38、ly, side benefit is load balance. 5 DETAILED REQUIREMENTS 9 The requirements contained in this section may be implemented in a phased manner during the development of the stage 2 and stage 3 specifications. 5.1 System Requirements 13 SYS-01: It shall be possible to connect between SNSF and any MSCe
39、in the Pool SYS-02: An MSCe within the MSC pool shall be able to support both MSC pool configuration and legacy configuration. SYS-03: A BSC within the MSC pool configuration shall be able to support both MSC pool configuration and legacy configuration. SYS-04: SNSF shall be able to select an MSCe a
40、s a serving MSCe for a subscriber within the MSC Pool configuration based on a selection algorithm which include the load redistribution capability. SYS-05: It shall be possible for the operator to choose the selection algorithm used by SNSFs. SYS-06: An MS shall be served by a selected MSCe, known
41、as the default MSCe, for the life of the registration within the PA even if the MS crosses the BSC boundary within the MSC Pool area. SYS-07: it shall be possible to redistribute the MSs from the current serving MSCe/failure MSCe to a new serving MSCe within the MSC pool, a new serving MSCe provides
42、 the functions decribed in SYS-06. SYS-08: MSC Pool network entities shall be able to interoperate with non-MSC Pool network entities without any impact on the non-MSC Pool network entities (e.g., trunking group procedures, handoff procedures). 2008 3GPP2 Page3 S.R0136-0 v1.0 System Requirements for
43、 MSC Pool 2008 3GPP2 Page 4 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 18 19 20 21 22 23 25 26 27 28 29 30 31 32 SYS-09: This feature shall not create any impacts to deployed non-MSC Pool network interfaces or entities that support 1. SYS-10: Deployment of this feature shall be possible such that adjace
44、nt non-MSC Pool MSCs can interoperate with MSC Pool MSCes without modification of procedures of the non-MSC Pool entities. SYS-11: It shall be possible to deploy this feature in such a way that an HRPD system that spans both the MSC Pool Area and non-MSC Pool Area can operate without modification, a
45、nd without modification to standard procedures for handoff from HRPD to cdma2000 1x. SYS-12: Introduction of MSC pool shall not impact any of the existing Circuit Switched (CS) services supported by current IOS specification2 SYS-13: MSC Pool shall support legacy cdma2000 1x MS. 5.2 Operation, Admin
46、istration, Maintenance and Provisioning 17 Requirements OAM&P-01: The OAM&P system shall be able to trigger load redistribution from one MSCe to other MSCe(s) in the MSC Pool. OAM&P-02: It shall be possible to allow the BSC to be configured with a new SNSF when the current SNSF is unavailable. 5.3 S
47、ystem Design Goals 24 GOALS-01: When one MSCe in an MSC Pool breaks down, the interruption time for users being registered in this MSCe should be minimized. In other words, other MSCe within the MSC Pool shall take over the communication services (e.g., call origination, call delivery, etc.) from this MSCe as quickly as possible. GOALS-02: The SNSF should consider load balancing when selecting a serving MSCe.
