mip dt infomodel

Download MIP DT Infomodel

Post on 01-Dec-2014

135 views

Category:

Documents

5 download

Embed Size (px)

TRANSCRIPT

Ericssonwide Internal DT FEATURE DESCRIPTIONPrepared (also subject responsible if other) No.

1 (29)

ETH/GS Irn CsiszrApproved Checked

4/190 46-FAD 104 50Date Rev Reference

ETH\GSC

ETHBYP

2005-10-17

A

MSC in POOLAbstract This document describes FAJ 121 297 R2 - MSC in Pool from a DataTranscript point of view.

Content 1 2 2.1 2.2 2.3 2.4 2.4.1 2.4.2 2.4.3 2.5 2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 2.6 2.6.1 2.6.2 3 3.1 3.2 3.2.1 3.2.2 3.2.3 4 4.1 4.1.1 4.1.2 5

Revision Information............................................................................3 Description ..........................................................................................3 Abbreviations.......................................................................................3 Concepts .............................................................................................4 Concerned Nodes ...............................................................................5 Prerequisites .......................................................................................5 Network ...............................................................................................5 Feature included..................................................................................8 Software level ......................................................................................8 General................................................................................................8 Neighbouring MSC Group ...................................................................9 Network Resource Indicator (NRI):......................................................9 MSC Pool Area..................................................................................10 Overlapping Pool Area ......................................................................11 Proxy MSC ........................................................................................12 Technical Solution .............................................................................13 MSC in Pool function.........................................................................13 Building a pool network: ....................................................................15 Traffic Case .......................................................................................22 Location update in MSC in pool area ................................................22 Handover / SRNS Relocation ............................................................23 Neighboring MSC groups ..................................................................24 Subsequent Handover/SRNS Relocation to Third MSC, Anchor MSC24 Handling of Handover/SRNS Relocation in Non-anchor MSC ..........25 Data Transcript Impacts MSC ........................................................26 AXE Parametrs..................................................................................26 Subfile 10000 Size Alteration APT ....................................................27 Subfile 77200 MSC Pool ...................................................................28 Data Transcript Impacts- HLR ...........................................................28

Ericssonwide Internal DT FEATURE DESCRIPTIONPrepared (also subject responsible if other) No.

2 (29)

ETH/GS Irn CsiszrApproved Checked

4/190 46-FAD 104 50Date Rev Reference

ETH\GSC

ETHBYP

2005-10-17

A

6 7

Miscellaneous information .................................................................28 Class .................................................................................................29

Ericssonwide Internal DT FEATURE DESCRIPTIONPrepared (also subject responsible if other) No.

3 (29)

ETH/GS Irn CsiszrApproved Checked

4/190 46-FAD 104 50Date Rev Reference

ETH\GSC

ETHBYP

2005-10-17

A

1

Revision Information

Revision

Impacts

Prepared

Date

A PA3 PA2 PA1

Release Update after review SIGTRAN added Mixed netw. BSC/RNC added New document

ethcsir ethcsir ethcsir ethcsir

17-10-05 28-09-05 08-07-05 09-05-05

2

Description

2.1

AbbreviationsBSC CDR HLR ISP LA MSC MS MSISDN NRI PLMN RNC SMS TMSI Base station Services Switching Centre Call Data Record Home Location Register In Service Performance Location Area Mobile Services Switching Centre Mobile Subscriber Mobile Station ISDN number Network Resource Indicator Public Land Mobile Network Radio Network Controller Short Message Service Temporary Mobile Station Identity

Ericssonwide Internal DT FEATURE DESCRIPTIONPrepared (also subject responsible if other) No.

4 (29)

ETH/GS Irn CsiszrApproved Checked

4/190 46-FAD 104 50Date Rev Reference

ETH\GSC

ETHBYP

2005-10-17

A

UE VLR

User Equipment Visitor Location Register

2.2

ConceptsA MSC Pool is defined as a pool of MSC nodes linked to a number of BSC and/or RNC nodes. Each BSC/RNC is connected to each MSC node of the pool.

Figure 1: Example of a Configuration of an MSC Pool All MSCs within a pool need to be connected to all BSCs/RNCs, so links need to be set up between the nodes. All MSCs within a pool need to have the same BSC/cell RNC/SAI related settings. An MSC of the pool has no knowledge about the behaviour of the surrounding MSC nodes, whether they belong to the same MSC pool or not. The MSC pool concept is mainly applicable for the BSC/RNC, as the BSC/RNC can see a pool of MSC nodes. Each MSC node in a pool shares the same service area with all other MSCs in the pool. If an MSC is removed from the pool the subscribers of the removed MSC will be distributed to the other MSCs of the pool. This feature provides MSC redundancy and improved network service availability. This feature requires a fully meshed network of A-interfaces / IuCS interfaces between all the BSC / RNC nodes of a pool service area and all the MSC nodes of this pool.

Ericssonwide Internal DT FEATURE DESCRIPTIONPrepared (also subject responsible if other) No.

5 (29)

ETH/GS Irn CsiszrApproved Checked

4/190 46-FAD 104 50Date Rev Reference

ETH\GSC

ETHBYP

2005-10-17

A

This means that all MSC nodes of a pool can have access to a GSM service area and a WCDMA service area at the same time. Note: It has to be noted that all MSCs in the pool should provide the same level of functionality (HW&SW&activation of functions), otherwise the enduser can get different level of service depending on which MSC she/he is connected to. Anchor-MSC Anchor-MSC is the MSC where the transaction is originally established.

2.3

Concerned NodesMSC/VLR MSC/MGW MSC server BSC RNC

2.4

Prerequisites

2.4.1

Network The network service availability is improved for UEs roaming in the WCDMA service area of the MSC pool. This is due to the fact that if an MSC fails its subscribers will be reallocated to another MSC node of the pool. The feature eases a change of the network infrastructure and improves horizontal scalability, availability and in-service performance (ISP). Less relocation and location update cases with registration to the HLR reduce the signalling load. Some assumptions that an operator should take into account for the MSC in pool function are the following: The network topology should be a fully meshed network. This means that each MSC shall be logically connected to all BSCs/RNCs in the MSC pool service area.

Ericssonwide Internal DT FEATURE DESCRIPTIONPrepared (also subject responsible if other) No.

6 (29)

ETH/GS Irn CsiszrApproved Checked

4/190 46-FAD 104 50Date Rev Reference

ETH\GSC

ETHBYP

2005-10-17

A

TMSI allocation shall always be performed even after a reload. All MSCs within a pool need to have the same BSC/cell, RNC, and area cluster related settings. For the MSCs that serve also BSCs/RNCs outside the pool, additional settings are needed. When a new MSC (without connected BSCs/RNCs) is installed in the pool, the data of BSCs/RNCs in the pool should be copied to the new MSC. When a new MSC (with connected BSCs/RNCs) is installed in the pool the cell/RNC and area cluster (if available and used) data needs to be copied from the MSC to all MSCs in order to have the same radio data definition. This copy procedure has to be done following some order and rules that are described reference [3]. If an MSC pool is configured for GSM traffic only and some of the MSCs in the pool also serve for WCDMA traffic, then these MSCs should be offloaded from the GSM traffic distributed in the MSC pool. This means that less subscribers will be routed to this MSC from the BSC, by using the MSC selection function. The opposite case (MSC pool configured for WCDMA only with some MSCs in the pool serving GSM traffic) should be considered in the same way. The NRI length should not change during normal operation because all the previously stored NRI values in the MSC are physically deleted from the MSC immediately. The BSCs/RNCs and the MSCs need to have consistent NRI length.

Physical location MSC pool members can be placed in the same site (centralized configuration) or they can be placed in different physical sites (distributed configuration). When deciding about the physical location of the nodes (centralized/distributed) it is important to take into consideration the security aspects, the network architecture (layered, non-layered), the transmission cost aspects and the operational aspects. For example, an MSC pool where all the MSC pool members and the BSCs are placed in the same site has a low transmissi