Вы находитесь на странице: 1из 2

Siemens AG MO USSD 01/28/2011

Mobile Originated USSD/SCI

MS <-> SCP

1. HLR 1. MAP: USSD_REQUEST (VLR - HLR)


MSC/VLR 4. (USSD 2. CAP: USSD_REQUEST (HLR - SCP)
Handler) 3. CAP: USSD_RESPONSE (SCP - HLR)
3. 4. MAP: USSD_RESPONSE (HLR - VLR)

Remark: The CAMEL messages are transported


transparently through MSC/VLR and HLR.
2.
The USSD-RESPONSE can initate another
SCP USSD-REQUEST message. The number of sequences
depends on the implemented service.

MS <-> HLR The messages between MSC and VLR are the
same as between VLR and HLR
1. HLR
MSC/VLR 2. (USSD 1. MAP: USSD_REQUEST (VLR - HLR)
Handler) 2. MAP: USSD_RESPONSE (HLR - VLR)

MS <-> VLR
Remark: No #7 messages are visible in the
core network.
MSC/VLR
The messages between MSC and VLR are the
same as between VLR and HLR

MS <-> MSC
Remark: No #7 messages are visible in the
core network.
MSC/VLR

Company confidential - for internal use only 50414654.xls Thomas Scholle, ICM N PG NM NE P 3
Siemens AG MT USSD 01/28/2011

Mobile Termininated/ Network Initiated USSD

MS <-> SCP

2. HLR 1. CAP: USSD_REQUEST (SCP - HLR)


MSC/VLR 3. (USSD 2. MAP: USSD_REQUEST (HLR - VLR)
Handler) 3. MAP: USSD_RESPONSE (VLR - HLR)
4. 4. CAP: USSD_RESPONSE (HLR - SCP)

Remark: In case of CAMEL the messages are


transparently routed through MSC and HLR.
1.
The USSD-RESPONSE can initate another
SCP USSD-REQUEST message. The number of sequences
depends on the implemented service.

MS <-> HLR

1. HLR 1. MAP: USSD_REQUEST (VLR - HLR)


MSC/VLR 2. (USSD 2. MAP: USSD_RESPONSE (HLR - VLR)
Handler)

MS <-> VLR
Remark: No #7 messages are visible in the
core network.
MSC/VLR
The messages between MSC and VLR are the
same as between VLR and HLR

MS <-> MSC
Remark: No #7 messages are visible in the
core network.
MSC/VLR

Company confidential - for internal use only 50414654.xls Thomas Scholle, ICM N PG NM NE P 3