Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

MSC Server/MSC with Integrated MGCF (MSCF)

IP.com Disclosure Number: IPCOM000028360D
Original Publication Date: 2004-Jun-25
Included in the Prior Art Database: 2004-Jun-25
Document File: 2 page(s) / 371K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

In the standard architecture of the Internet Multimedia Subsystem (IMS) and the CS (Circuit Switched) domain, as defined in the 3GPP standardization, the Media Gateway Control Function (MGCF) in the IMS and the MSC (Mobile Switching Center) Server in the CS domain perform similar tasks (cf. Figure 1). Both control the MGWs (Media Gateways) and handle the communication between their respective domain and the PSTN/PLMN. Furthermore, the MGCF provides the SIP support, which is often also implemented in the MSC Server as a function called SIP-T (Session Initiation Protocol for Telephony). Because of this analogy, the MGCF functionality can easily be integrated in the MSC Server. Similarly, the MGCF functionality can also be integrated in a MSC so that this MSC serves as a Gateway MSC for both the CS domain and the IMS. A possible implementation of this MSC Server Control Function (MSCF) is shown in Figure 2. The MSCF already includes both the MGW controlling and all ISUP/BICC protocol variants necessary for the interworking with the different PSTN/PLMNs. Also, the interrogation procedure for identifying the called IMS subscriber via the HSS (Home Subscriber Server) is available by using the existing MSC Server respectively MSC features. If the MSC Server already offers a SIP stack, due to a possible SIP-T support, then only an appropriate SIP protocol conversion and the communication with the CSCF/BGCF (Call State Control Function/Breakout Gateway Control Function) has to be added to the MSC Server respectively MSC functionality, which then can be used for other future applications, too. To support PS (Packet Switched) traffic, a Gi interface can be implemented in the MSC. The MSCF and its interfaces is schematically illustrated in Figure 3.

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 98% of the total text.

Page 1 of 2

S

MSC Server/MSC with Integrated MGCF (MSCF)

Idea: Andreas Trapp, DE-Munich

In the standard architecture of the Internet Multimedia Subsystem (IMS) and the CS (Circuit Switched) domain, as defined in the 3GPP standardization, the Media Gateway Control Function (MGCF) in the IMS and the MSC (Mobile Switching Center) Server in the CS domain perform similar tasks (cf. Figure 1). Both control the MGWs (Media Gateways) and handle the communication between their respective domain and the PSTN/PLMN. Furthermore, the MGCF provides the SIP support, which is often also implemented in the MSC Server as a function called SIP-T (Session Initiation Protocol for Telephony). Because of this analogy, the MGCF functionality can easily be integrated in the MSC Server. Similarly, the MGCF functionality can also be integrated in a MSC so that this MSC serves as a Gateway MSC for both the CS domain and the IMS. A possible implementation of this MSC Server Control Function (MSCF) is shown in Figure 2.

The MSCF already includes both the MGW controlling and all ISUP/BICC protocol variants necessary for the interworking with the different PSTN/PLMNs. Also, the interrogation procedure for identifying the called IMS subscriber via the HSS (Home Subscriber Server) is available by using the existing MSC Server respectively MSC features. If the MSC Server already offers a SIP stack, due to a possible SIP-T support, then only an appropriate SIP protocol conversion and the communication with the CSCF/BGCF (Call State Control Function/Breakout Gateway Control Function) has to be added to the MSC Server respectively MSC functionality, which then can be used for other future applications, too. To support PS (Packet Switched) traffic, a Gi interface can be implemented in the MSC. The MSCF and its interfaces is schematically illustrated in Figure 3.

Figure 1: 3GPP Standard Network (simplified)

Multimedia IP Networks

HSS/ AS

SIP

T-PSI,CBICSG W

MSC MSC

H.248 H.248

   CS IMS/PS

CSCF/ BGCF

MGCF

SGW

SGSN

GGSN

MGW

MGW

MGW

MSC Ser ver

MSC Server

HLR/SCP HSS/AS

  Radio Network/ Mobile Subscriber

A/Iu(cs) Iu(ps)

ISUP,B ICC ISUP,B ICC

PSTN/ PLMN

© SIEMENS AG 2004 file: 2004J04126.doc page: 1

[This page contains 3 pictures or other non-text objects]

Page 2 of 2

S

Figure 2: Network with integrated MSCF (simplified)

Multimedia IP Networks

HSS/AS

CSCF/ BGCF

   CS IMS/PS

SGSN

GGSN

MGW

MSC MSC SIP BICC,SIP-T

H.248

MGW

SGW

FMSCMSC Ser ver

HL R/ SCP

 Radio Network/ Mobile Subscriber

SIP Iu(ps) A/Iu(ps)

PSTN/ PLMN

ISUP, BICC

Figure 3: MSCF Definition and Interfaces

MAP,CAP Nc(BICC,SIP-T)

Mj(SIP)

Mn(H.248)

MSCS

MGCF

Iu(ctrl)

Mg(SIP) mgcf

A(ctrl) mscs

ISUP,BICC

Iu(ctrl)

A(ctrl)

ISUP,BICC

Mc(H.248)

MSCF

MAP,CAP Nc(BICC,SIP-T)

Mg,Mj (SIP)

mscf

=

ISUP,BICC

Mc,Mn (H.248)

© SIEMENS...