Browse Prior Art Database

MSC/MSC Server Resources Function (MSRF)

IP.com Disclosure Number: IPCOM000028564D
Published in the IP.com Journal: Volume 4 Issue 6 (2004-06-25)
Included in the Prior Art Database: 2004-Jun-25
Document File: 3 page(s) / 51K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

The 3GPP Release 4 standardization for the CS (Circuit Switched) domain points out that the provision of specific equipment for announcements, tones, multiparty conferences, CS data services and all IN (Intelligent Network) functions within a separate architecture should be located in the MGWs (Media Gateways). Optionally, this can also be implemented in one specialized MGW, which then provides these resources (cf. Figure 1). Therefore, incumbent operators who want to extend a 3GPP R'99 mobile core network with a separate 3GPP Release 4 architecture have to supply the new MGWs with a multitude of resources and equipment although these already exist in (almost) every MSC (Mobile Switching Center) respectively MSC Server. Hence, it is proposed to add a MSC Server Resources Function (MSRF) to the MSC respectively MSC Server. This Function can either be included in every MSC (cf. Figure 2) or only in one specialized MSC, which then provides the resources at one location (Figure 3). The MSC/MSC Server identifies the call scenarios or service scenarios, for which specific equipment is needed, and inserts and controls the resources either itself or provides access to the dedicated MSC, in both cases using well known equipment and procedures.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 3

S

MSC/MSC Server Resources Function (MSRF)

Idea: Andreas Trapp, DE-Munich; Bernd Langen, DE-Munich; Hans-Juergen Hanisch, DE-Munich

The 3GPP Release 4 standardization for the CS (Circuit Switched) domain points out that the provision of specific equipment for announcements, tones, multiparty conferences, CS data services and all IN (Intelligent Network) functions within a separate architecture should be located in the MGWs (Media Gateways). Optionally, this can also be implemented in one specialized MGW, which then provides these resources (cf. Figure 1). Therefore, incumbent operators who want to extend a 3GPP R'99 mobile core network with a separate 3GPP Release 4 architecture have to supply the new MGWs with a multitude of resources and equipment although these already exist in (almost) every MSC (Mobile Switching Center) respectively MSC Server.

Hence, it is proposed to add a MSC Server Resources Function (MSRF) to the MSC respectively MSC Server. This Function can either be included in every MSC (cf. Figure 2) or only in one specialized MSC, which then provides the resources at one location (Figure 3). The MSC/MSC Server identifies the call scenarios or service scenarios, for which specific equipment is needed, and inserts and controls the resources either itself or provides access to the dedicated MSC, in both cases using well known equipment and procedures.

The MSRF equipment consists of hardware/firmware parts that are already available within an existing mobile core network. These are:

- Announcement Machines

- Tone Generators

- Conferencing Units for Multiparty

- Interworking Equipment for CS Data Services

- Special IN Equipment for UI- (User Interface-) Dialogues

Likewise, the MSRF controlling consists of software parts that are also already available within an existing mobile core network:

- Announcement Handling

- Tone Handling

- Multiparty Handling

- Inte...