3G Video Call Data Rates

3G Video
MSOFTX3000
V200R008C03
Issue 1.00
Date 2009-04-06
INTERNAL
Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, 518129, People’s Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
MSOFTX3000
3G Video Call About This Document
About This Document
Author
Prepared by Liu Shiyue Date 2009-4-6
Tested by Date
Reviewed by Date
Approved by Date
Organization
This document is organized as follows:
Section Describes
1.1 Feature Description The function code, definition, and benefits of the 3G Video
feature.
1.2 Availability The licensing requirements and NE requirements (including the
minimum software versions and provided functions) of 3G
Video feature.
1.3 Service Flow The flow of 3G Video feature.
1.4 Table Query for 3G The table query procedure of 3G Video feature.
Video
1.5 Charging and CDR The procedure for performing charging and generating CDRs
when 3G Video feature is provided.
1.6 Performance The impact of the service on performance measurement and the
Measurement performance measurement entities specific to the 3G Video
feature.
1.7 Operation and The MML commands and alarm information related to the 3G
Maintenance Video feature.
1.8 Reference The standards and specifications with which the 3G Video
feature complies and the glossary, abbreviations, and acronyms
used in this document.
Huawei Proprietary and Confidential

Issue 01 (2009-04-06)
Copyright © Huawei Technologies Co., Ltd.
MSOFTX3000
About This Document 3G Video Call
Update History
Issue Details Date Author Approved by
V1.00 Initial release Liu Shiyue

Issue 01 (2009-04-06)
MSOFTX3000
3G Video Call Contents
Contents
1 3G Video .........................................................................................................................................1
1.1 Feature Description .......................................................................................................................................... 1
1.1.1 Function Code......................................................................................................................................... 1
1.1.2 Definition ................................................................................................................................................ 1
1.1.3 Application Scenario ............................................................................................................................... 2
1.1.4 External Interfaces .................................................................................................................................. 2
1.1.5 Compliance Standards............................................................................................................................. 5
1.1.6 Constraints and Limitations .................................................................................................................... 5
1.1.7 Benefits ................................................................................................................................................... 5
1.1.8 Release History ....................................................................................................................................... 6
1.2 Availability ....................................................................................................................................................... 6
1.2.1 Involved NEs .......................................................................................................................................... 6
1.2.2 Functions of the NEs............................................................................................................................... 6
1.2.3 Requirements for License ....................................................................................................................... 7
1.2.4 Hardware Compatibility.......................................................................................................................... 7
1.2.5 Supporting Versions ................................................................................................................................ 7
1.3 Service Flow..................................................................................................................................................... 7
1.3.1 Scenario Description............................................................................................................................... 7
1.3.2 H.245 Negotiation................................................................................................................................... 8
1.3.3 Intra-MSC 3G Video Calls.................................................................................................................... 10
1.3.4 Inter-ISUP-MSC 3G Video Calls .......................................................................................................... 23
1.3.5 Inter-BICC-MSC 3G Video Calls ......................................................................................................... 28
1.3.6 Inter-SIP-MSC 3G Video Calls............................................................................................................. 36
1.3.7 Video Call Announcement Flow (Local Announcement Notification ) ................................................ 43
1.3.8 Interaction Between the 3G Video Call Service and the Supplementary Service ................................. 48
1.3.9 Interaction Between the 3G Video Call Service and the DTMF ........................................................... 57
1.3.10 Interaction Between the 3G Video Call Service and the Intelligent Network (IN) Service ................ 59
1.3.11 3G Video Call Fallback ....................................................................................................................... 69
1.3.12 3G Video Call Failure ......................................................................................................................... 80
1.4 Table Query for 3G Video .............................................................................................................................. 94
1.5 Charging and CDR ......................................................................................................................................... 95
1.6 Performance Measurement............................................................................................................................. 96
1.7 Operation and Maintenance ........................................................................................................................... 98

Issue 01 (2009-04-06) i
MSOFTX3000
Contents 3G Video Call
1.7.1 Related MML Commands..................................................................................................................... 98

1.7.2 Related Alarms...................................................................................................................................... 98
1.8 Reference ....................................................................................................................................................... 99
1.8.1 Acronyms and Abbreviations ................................................................................................................ 99

ii Issue 01 (2009-04-06)
MSOFTX3000
3G Video Call Figures
Figures
Figure 1-1 Framework of circuit switched multimedia in 3GPP (Items in square brackets are optional) ............. 3
Figure 1-2 H.245 negotiation flow ........................................................................................................................ 9
Figure 1-3 Intra-MSC 3G video call flow ........................................................................................................... 11
Figure 1-4 Procedure of an inter-ISUP-MSC video call between 3G subscribers............................................... 23

Figure 1-5 Procedure of an inter-BICC-MSC video call between 3G subscribers .............................................. 28
Figure 1-6 Procedure of an inter-SIP-MSC video call between 3G subscribers.................................................. 36
Figure 1-7 Announcement notification upon an intra-MSC 3G video call failure .............................................. 44
Figure 1-8 Announcement notification upon an inter-MSC 3G video call failure............................................... 45
Figure 1-9 USSD notification upon a 3G video call failure ................................................................................ 46
Figure 1-10 Interaction between the 3G video call service and the CFU service................................................ 50
Figure 1-11 Interaction between the 3G video call service and the CFB (user-determined busy/CFNRy (no
answering) service................................................................................................................................................ 52
Figure 1-12 Interaction between the 3G video call service and the CFB (video call forwarding)/ or CFNRc-2
(unreachable) service ........................................................................................................................................... 54
Figure 1-13 Interaction between the 3G video call service and the CFB service (NDB network-determined busy)
.............................................................................................................................................................................. 56
Figure 1-14 VP IN service triggered for the caller and the callee ....................................................................... 59
Figure 1-15 VP IN service triggered for the caller .............................................................................................. 63
Figure 1-16 VP IN service triggered for the callee.............................................................................................. 66

Figure 1-17 Multimedia fallback when the caller does not subscribe to the multimedia service ........................ 69
Figure 1-18 Multimedia fallback when the callee does not subscribe to the multimedia fallback service.......... 70
Figure 1-19 Multimedia fallback when the callee is in the 2G network.............................................................. 71
Figure 1-20 Multimedia fallback when the called UE does not support the multimedia call fallback ................ 72
Figure 1-21 Multimedia fallback when the called UE does not support Repeat Indicator .................................. 74
Figure 1-22 Multimedia fallback triggered by handover from 3G video calls to 2G video calls ........................ 75
Figure 1-23 Multimedia fallback triggered when the RNC sends the bearer modification request..................... 77
Figure 1-24 Single BC video fallback (requiring the support of the UE)............................................................ 79

Issue 01 (2009-04-06) iii
MSOFTX3000
Figures 3G Video Call
Figure 1-25 3G video call failed because the network serving the callee does not support the 3G video call
service .................................................................................................................................................................. 81
Figure 1-26 3G video call failed because the callee does not subscribe to the 3G video call service ................. 82
Figure 1-27 3G video call failed because the callee is located in a 2G access network (sub-scenario a)............ 83
Figure 1-28 3G video call failed because the callee is located in a 2G access network (sub-scenario b)............ 84
Figure 1-29 3G video call failed because the called UE does not support the video call service........................ 85
Figure 1-30 3G video call failed because the radio coverage area where the callee is located does not support
the video call service............................................................................................................................................ 87
Figure 1-31 3G video call failed because the callee answers the video call as a voice call................................. 88
Figure 1-32 3G video call failed because the caller who has subscribed to the video call service is located in a
2G access network................................................................................................................................................ 90
Figure 1-33 3G video call failed because the resources in the 3G radio coverage area where the caller is located
are insufficient...................................................................................................................................................... 91
Figure 1-34 3G video call failed because the caller does not subscribe to the video call service........................ 92
Figure 1-35 General table query flow of the 3G video call ................................................................................. 95

iv Issue 01 (2009-04-06)
MSOFTX3000
3G Video Call Tables
Tables
Table 1-1 H.324M protocol frame ......................................................................................................................... 3

Table 1-2 NEs involved in the 3G video feature.................................................................................................... 6
Table 1-3 Versions of the Huawei products that support the 3G video service...................................................... 7
Table 1-4 Key measurement units related to the 3G video service...................................................................... 96

Issue 01 (2009-04-06) v
MSOFTX3000
3G Video Call 1 3G Video
1 3G Video
1.1 Feature Description

1.1.1 Function Code
Function Code
3G video WMFD-040100
1.1.2 Definition
Function Definition
3G video call This feature provides an end-to-end synchronous video and

audio transmission service that enables the subscribers to
communicate with each other through video and voice on a
real time basis. With this feature, subscribers can perceive the
change in the video and audio information of the peer end,
and thus can communicate with each other more easily.
3G video call fallback This feature enables the system to roll back a 3G video call to
a 2G voice call through cooperation between the network and
the UE when a 3G video call fails because of a network fault
or terminal fault. The process is transparent to subscribers and
thus helps maintain the service experience of subscribers.
Performance measurement This feature enables the system to implement the performance
upon 3G video call measurement upon 3G video call failures. Based on the
failures performance measurement results, carriers can analyze the
operation status of the video call service. This feature is
applicable only when the subscribers have 3G video call
service registered.

Issue 01 (2009-04-06) 1
MSOFTX3000
1 3G Video 3G Video Call
1.1.3 Application Scenario

This feature is applicable to the UMTS network.
1.1.4 External Interfaces

The interfaces between the MSC server and all network entities (NEs) must be compliant with
3GPP.
The 3G video terminal must be compliant with the H.324M standard.
H.324 is a low bit-rate multimedia communication standard developed for real-time
transmission of voice, video, or their combination.
The 3G video call service is a data service. It differs from the traditional voice call service in
the following aspects:
1. The 3G video call service is a data service.
2. The 3G video call service does not support most of inband operations of the voice service,
for example, inband announcement (including the ringback tone and call failure tone).
3. The 3G video call service does not support the supplementary services that require
movement of terminations, such as CALL HOLD, MPTY, and ECT.
The H.324M standard is an extension of "mobile part" in the ITUT H.324 standard. It defines
the wireless access-related information (see Appendix C Multimedia Telephone Terminals
Over Error Prone Channels and Appendix H Mobile Multilink Operation) and is applied to the
WCDMA and CDMA networks for video communication.
H.324 is originally used to implement POTS-based multimedia communication through the
V.34 modem in synchronization mode. As defined in the generic H.324 protocol, the control
protocol is H.245, multiplexing protocol is H.223, video codec protocol is H.261 or H.263,
text protocol is T.140, and audio codec protocol is G.723.1.
To expand this standard in the wireless or mobile industry, Appendix C (Multimedia
Telephone Terminals Over Error Prone Channels) and Appendix H (Mobile Multilink
Operation) of H.324, and Appendixes A, B, C, and D of H.323 add related descriptions about
H.324. In addition, the H.323 mobile specific appendix defines certain functions about
protection and control of errors, and thus improves the anti-error capabilities of multiplexing
for data communication in the wireless network.H.245 provides supplementary commands
and control flows for the mobile part of H.223.These functions added for mobile applications
are defined in the H.324M standards. The terminals compliant with the H.324 standards are
called H.324M terminals.
H.324M terminal: The H.324M terminal complies with the ITU-T H.324 protocol and
includes the terminals described in Appendix C (Multimedia Telephone Terminals Over Error
Prone Channelss).
3G-324M terminal: The 3GPP adopts H.324 as the standard for video communication in the
circuit domain and provides supplementary regulations in 3GPP TS 26.110 and 3GPP TS
26.111. The terminals that are compliant with these specifications are called 3G-324M
terminals.

2 Issue 01 (2009-04-06)
MSOFTX3000
Table 1-1 H.324M protocol frame
Framework H.324M
protocol
Video protocol H.261

H.263
MPEG-4
Audio protocol G.723.1
3GPP AMR
Multiplexing H.223
protocol
Control protocol H.245
Figure 1-1 Framework of circuit switched multimedia in 3GPP (Items in square brackets are
optional)
Networking for video calls in fixed and mobile networks

Issue 01 (2009-04-06) 3
MSOFTX3000
There are two types of 3G video terminals: circuit-based low bit rate H.324 terminal and packet-based
SIP or H.323 compatible terminal.
The interworking between the video services in the mobile and fixed networks includes:
z Video call interworking between different 3G video terminals of different modes
z Video call interworking between 3G video terminal and H.323 video terminal
z Video call interworking between 3G video terminal and SIP video terminal
z Mixed video conference with 3G video terminal, H.323 terminal, and SIP terminal
The video interworking between the WCDMA/TD-SCDMA and CDMA2000 networks is
called homogeneous interworking because the terminals involved use the same protocol
H.324M. Other interworking is called heterogeneous interworking.

4 Issue 01 (2009-04-06)
MSOFTX3000
1.1.5 Compliance Standards

Protocol Number Name Organization
TS 24.008 Mobile radio interface Layer 3 3GPP

specification, Core network
protocols; Stage 3
Q.931 3G security; Security threats and ITUT
requirements
TR 27.001 Specification drafting rules 3GPP
TR 29.007 Technical Specification Group 3GPP
working methods
3GPP 26.110 Codec for circuit switched 3GPP
multimedia telephony service,
General description
3GPP 26.111 Codec for circuit switched 3GPP
multimedia telephony service,
Modifications to H.324
1.1.6 Constraints and Limitations

Feature Specifications
Specification Measurement Entities
- -
Application Limitations
None.
Impact on the System

None.
1.1.7 Benefits
Beneficiary Description
Carriers The 3G video service enables carriers to provide the video telephony
service to improve the customers' satisfaction.
Subscribers The 3G video service enables subscribers to enjoy a new 3G video
telephony service and helps to enrich people's life through convenient
communication.

Issue 01 (2009-04-06) 5
MSOFTX3000
1.1.8 Release History

History Date Version Details Release Plan
Initial release 2009-4-20 V200R008C02 -

Second release 2009-7-27 V200R008C03 Added the video
call failure
scenario.
1.2 Availability
1.2.1 Involved NEs
The 3G video service requires the cooperation of the UE, MSC server, RNC, MGW, and HLR.
Table 1-2 lists the NEs involved in the 3G Video feature.
Table 1-2 NEs involved in the 3G video feature

UE Node B RNC MSC MGW SGSN GGSN HLR VIG
√ √ √ √ √ √
The symbol "√" indicates that the NE is required.
1.2.2 Functions of the NEs

z MSC
Mobile Services Switching Centre (MSC) controls the video calls of the mobile terminals in
its control area.
z MGW
The Media Gateway (MGW) is connected to the MSC. It implements interaction of video
calls under the control of the MSC. It is responsible for the establishment and connection of
bearers in a specific media path.
z RNC
Radio Network Controller (RNC) is responsible for establishment, release of video calls,
handover, macrodiversity combination, and radio resource management control.
z HLR
Home Location Register (HLR) is a database used to manage mobile subscribers. Each
mobile subscriber must register with the home HLR for successful service implementation.
For example, subscribers can use the 3G voice call service only after they register with the
home HLR.
z UE

6 Issue 01 (2009-04-06)
MSOFTX3000
User Equipment (UE) is the mobile terminal used by a subscriber to originate video calls. It
provides the terminal adaptation function and operation interface for subscribers to use video
services conveniently.
z VIG
The Video Interworking Gateway (VIG) is used for video interworking of different networks,
for example, the video interworking between the WCDMA/TD-SCDMA, CDMA2000, and
other networks (H.323, SIP, and Internet).
1.2.3 Requirements for License

z The 3G Video Call feature is optional. You must apply for a license to use this feature.
z The multimedia fallback is optional. You must apply for a license to use this feature.
1.2.4 Hardware Compatibility

None.
1.2.5 Supporting Versions

Table 1-3 lists the versions of the Huawei products that support the 3G video service.
Table 1-3 Versions of the Huawei products that support the 3G video service
NE Product Supporting Version
MSC MSOFTX3000 V200R008C02

MGW UMG8900 V200R008C02
1.3 Service Flow

z Unless otherwise stated, all the video telephony terminals described in this section support
3G-324M.
z The service flow described in this section is the basic service flow and does not represent all
scenarios.
1.3.1 Scenario Description

Based on the features of the 3G video call, this document describes the service flow from
seven scenarios:
z H.245 negotiation
z 3G video call announcement flow (Notification of local terminal)
z Intra-MSC 3G video call
z Inter-MSC 3G video call, which is classified into the following scenarios according to
the signaling exchanged between MSCs:
− Inter-MSC ISUP video call

Issue 01 (2009-04-06) 7
MSOFTX3000
− Inter-MSC BICC video call

− Inter-MSC SIP video call
The TUP signaling cannot transmit bearer-related information between MSCs, and therefore the TUP
signaling does not support video calls.
z Interaction between the 3G video call service and the supplementary service
z Interaction between the 3G video call service and the intelligent network (IN) service
z Video call fallback scenario which is classified into the following sub-scenarios based on
the fallback reasons.
− Callers not provided with the multimedia fallback service
− Callees not provided with the multimedia fallback service.
− Multimedia fallback of the callee in a 2G network
− Multimedia call fallback not supported by the callee
− Repeat Indicator-based multimedia call fallback not supported by the callee
− Multimedia fallback due to handover from 3G to 2G network
− Multimedia fallback due to the bearer modification request of the RNC
− Single BC video fallback (requiring the support of the UE)
1.3.2 H.245 Negotiation

Flow Description
1. H.245 negotiation

8 Issue 01 (2009-04-06)
MSOFTX3000
Figure 1-2 H.245 negotiation flow
The H.245 negotiation is implemented by two H.245 terminals. The negotiation procedure can
be classified into master/slave determination (MasterSlaveDetermination/Ack/Reject/Release),
terminal capability negotiation (TerminalCapabilitySet/Ack/Reject/Release), enable multiple
multiplexing entry (MultiplexEntrySend/Ack/Reject/Release), open logical channel

Issue 01 (2009-04-06) 9
MSOFTX3000
(OpenLogicalChannel/Ack/Reject/Release), close logical channel

(CloseLogicalChannel/Ack/Reject/Release), and H.245 management (EndSessionCommand).
2. Message flow
1) Establish an H.245 channel:
a) Master/slave determination (MasterSlaveDetermination/Ack/Reject/Release): This
procedure and the terminal capability negotiation procedure
(TerminalCapabilitySet/Ack/Reject/Release) can be implemented at the same time.
b) Terminal capability negotiation (TerminalCapabilitySet/Ack/Reject/Release): This
procedure and the master/slave determination procedure
(MasterSlaveDetermination/Ack/Reject/Release) can be implemented at the same time.
c) Open the logical channel (OpenLogicalChannel/Ack/Reject/Release)
d) Enable multiplexing entry (MultiplexEntrySend/Ack/Reject/Release): Interaction with
the TD phones is mandatory. For H323 or SIP video calls, this procedure is not required.
2) Close the H.245 channel:
a) Close logical channel (CloseLogicalChannel/Ack/Reject/Release)
b) Close the H.245 channel (EndSessionCommand)
Key Message and Information Element

There are no special messages and key information elements.
Configuration Impact
None.
Constraints
None.
1.3.3 Intra-MSC 3G Video Calls

Flow Description
In an intra-MSC 3G video call, the called party is paged in the same way as in the scenario of normal
voice call. Therefore, paging is not described separately in this section.

10 Issue 01 (2009-04-06)
MSOFTX3000
Figure 1-3 Intra-MSC 3G video call flow
The procedure of an intra-MSC 3G video call is as follows:

Issue 01 (2009-04-06) 11
MSOFTX3000
1. UE A sends a SETUP message to the MSC, carrying the Bearer Capability IE where ITC
is UDI and ORA is H.223&H.245.
2. The MSC sends an SRI request to the HLR, carrying the ISDN BC converted from the
PLMN BC.
3. The HLR obtains the roaming number that the MSC allocates for the callee, and then
sends a SRI ACK message carrying the obtained roaming number to the MSC.
4. The MSC sends a SETUP message to UE B, carrying the BC_IE of which ITC is UDI
and ORA is H.223&H.245.
5. UE B sends a CALL CONFFIRM message to the MSC.
6. The MSC sends an ADD REQ message carrying the PLMN BC IE to the MGW, in an
attempt to prepare bearer resources for the caller.
7. The MSC sends a CALL PROCEEDING message to UE A.
8. The MGW sends an ADD REPLY message carrying the applied resource ID applied to
the MSC.
9. The MSC sends RNC A an RAB Assignment message where both the maximum bit rate
and the guaranteed bit rate are 64000 bit/s.
10. The RNC A returns an RAB assignment message to the MSC.
11. The MSC sends an ADD REQ message carrying the PLMN BC IE to the MGW, in an
attempt to prepare resources for bearer resources for the callee.
12. The MGW sends an ADD REPLY message carrying the applied resource ID to the
MSC.
13. The MSC sends RNC B an RAB Assignment message where both the maximum bit rate
14. The RNC B returns an RAB assignment message to the MSC.
15. UE B reports an ALERTING message to the network side. The ALERTING message is
transparently transmitted to UE A through the MSC and RNC A.
16. UE B reports a CONNECT message to the network side. The ALERTING message is
transparently transmitted to UE A through the MSC and RNC A.
17. UE A reports a CONNECT ACK message to the network side. The CONNECT ACK
message is transparently transmitted to UE B through the MSC and RNC A.
18. H.245 channel establishment: UE A negotiates with UE B through
TerminalCapabilitySet/Ack/Reject/Release,
MasterSlaveDetermination/Ack/Reject/Release, MultiplexEntrySend/Ack/Reject/Release,
and OpenLogicalChannel/Ack/Reject/Release (for opening H.245 audio and video
channels).After the negotiation is complete and the H.245 channel is established, UE A
communicates with UE B through video.
19. H.245 channel release: Between UE A and UE B, the H.245 audio and video logical
channels are closed (CloseLogicalChannel/Ack/Reject/Release), the H.245 sessions are
terminated (EndSessionCommand), and the resources on the caller and callee planes are
released.
20. (Assume that UE A terminates the call first.) UE A sends a DISCONNECT message to
the MSC.
21. The MSC sends a DISCONNECT message to UE B.
22. The MSC sends a RELEASE request to UE A.
23. UE B sends a RELEASE request to the MSC.
24. UE A sends a RELEASE COMPLETE message to the MSC.
25. The MSC sends a RELEASE COMPLETE message to UE B.

12 Issue 01 (2009-04-06)
MSOFTX3000
Key Message and Information Element
z UE A sends a SETUP message to the MSC ( ). Among the information elements of

the SETUP message, only the following information element varies with the call type
(voice call or 3G video call):
a) For the 3G video calls, the IE Bearer Capability contains the following fields:
i. ITC: Unrestricted Digital Information (UDI)
ii. Duplex mode: Full duplex.
iii. Synchronous/asynchronous: Synchronous
iv. Connect element: transparent.
v. Fixed network user rate (FNUR): 64K bit/s.
vi. Rate adaption: For details, see Other Rate adaption.

Issue 01 (2009-04-06) 13
MSOFTX3000
vii. Other rate adaption (ORA): H.223 & H.245
z The MSC sends an SRI message to the HLR ( ). Among the information elements
of the SRI message, only the following information element varies with the call type
a) For 3G video calls, the Network Signal Info IE contains ISDN BC, LLC, and HLC.
i. Constitution of IEs
ISDN BC TAG
LENGTH
CONTENT
HLC TAG
LENGTH
CONTENT
LLC TAG
LENGTH
CONTENT
ISDN BC TAG:04
HLC TAG:7D
LLC TAG:7C
ii. Information element instance:

14 Issue 01 (2009-04-06)
MSOFTX3000
This IE is optional. That is, when the ISDN BC, LLC, and HLC are unavailable, this IE cannot be
included.
The description of each byte of this IE is as follows:

ISDN BC TAG: 04
ISDN BC LENGTH: 03
ISDN BC: 88 90 A6
LLC TG: 7C
LLC LENGTH: 03
LLC: 88 90 A6
According to 3GPP 29007, the mapping of key bytes between the PLMN BC and ISDN BC in
a video call is listed as follows (blue bold characters against grey background):
Octet PLMN BC parameter value Octet ISDN BC parameter value
1 Bearer Capability IEI 1 Bearer Capability IEI

2 Length of BC contents 2 Length of BC contents
3 Radio channel requirement No comparable field
#7.6 half rate channel
full rate channel
dual and full, rate preferred
dual and half rate preferred
3 Coding Standard 3 Coding Standard
#5 GSM standard coding #7.6 CCITT standardized coding
3 Transfer mode 4 Transfer mode
#4 circuit mode #7.6 circuit mode
packet mode (note7) packet mode
3 Information transfer capability 3 Information transfer capability
#3.1 speech #5.1 speech
unrestricted digital unrestricted digital
3,1 kHz audio ex PLMN 3,1 kHz audio
facsimile group 3 (note 1) 3,1 kHz audio
other ITC (see octet 5a) no comparable value
5a Other ITC
#7.6 restricted digital (note 18)
4 Compression (note 14) No comparable field
#7 data compression allowed
data compression not allowed
4 Structure 4a Structure (note 4)
#6.5 SDU integrity #7.5
unstructured

Issue 01 (2009-04-06) 15
MSOFTX3000
4 Duplex mode 5d Duplex mode

#4 half duplex #7 half duplex
full duplex full duplex
4 Configuration 4a Configuration (note 4)
#3 point to point #4.3
4 Establishment 4a Establishment (note 4)
#1 demand #2.1
4 NIRR (note 12)
no meaning No comparable field
Data ≤ 4.8kbit/s, FR nt,
6kbit/s radio interface is requested
5 Rate adaptation 5 User information layer 1 protocol
#5.4 no rate adaptation (note 2) #5.1 no comparable value
V.110, I.460/X.30 rate adaptation CCITT standardized rate adaption
V.110, I.460/X.30
CCITT X.31 flag stuffing (note 25) (note 25)
Recommendation G.711 µ-law
No comparable value (note 11) Recommendation G.711 A-law (note
No comparable value (note 11) 3)
Recommendation G.721 32 kbit/s
No comparable value (note 11) ADPCM and I.460
No comparable value
other rate adaptation (see octet 5a)
5a Other rate adaptation
#5.4 V.120 (note 17) No comparable value
PIAFS (note 27)
H.223 & H.245 H.223 & H.245 (note 26)
5 Signalling access protocol No comparable field
#3.1 I.440/I.450
X.21 (note 24)
X.28, ded.PAD, indiv.NUI (note 24)
X.28, ded PAD, univ.NUI (note 24)
X.28, non-ded PAD (note 24)
X.32 (note 24)
6 Synchronous/asynchronous 5a Synchronous/asynchronous
#1 synchronous #7 synchronous
asynchronous asynchronous
6 User info. layer 1 protocol 5 User info. layer 1 protocol
#5.2 default layer 1 protocol #5.1 see section under rate adaptation for
3GPP TS 24.008 above
6a Number of stop bits 5c Number of stop bits
#7 1 bit #7.6 1 bit
2 bits 2 bits

16 Issue 01 (2009-04-06)
MSOFTX3000
6a Negotiation 5a Negotiation
#6 In band neg. not possible #6 In band neg. not possible
no comparable value In band neg. possible (note 10)
6a Number of data bits 5c Number of data bits excluding
#5 #5.4 parity if present
7 bits 7 bits
8 bits 8 bits
6a User rate 5a User rate
#4.1 0.3 kbit/s #5.1 0.3 kbit/s
1.2 kbit/s 1.2 kbit/s
12 kbit/s (note 7) 12 kbit/s
1.2 kbit/s / 75 bit/s (note 24) 75 bit/s / 1.2 kbit/s
any value 19.2 kbit/s (note 14)
no comparable value Ebits or inband negotiation
(note 10)
6b Intermediate rate 5b Intermediate rate (note 13)
#7.6 8 kbit/s #7.6 8 kbit/s or not used
16 kbit/s 16 kbit/s or not used
any value 32 kbit/s or not used (note 14)
6b NIC on Tx 5b NIC on Tx
#5 does not require #5b does not require
requires (note7) requires (note 8)
6b NIC on Rx 5b NIC on Rx
#4 cannot accept #4 cannot accept
can accept (note 7) can accept (note 8)
6b Parity information 5c Parity information
#3.1 odd #3.1 odd
even even
none none
forced to 0 forced to 0
forced to 1 forced to 1
6c Connection element No comparable field
#7.6 transparent
non-transparent (RLP)
both, transp. preferred
both, non-transp. preferred

Issue 01 (2009-04-06) 17
MSOFTX3000
6c Modem type 5d Modem type

#5.1 none #6.1 no comparable value (note 5)
V.21 V.21
V.22 V.22
V.22bis V.22bis
V.23 (note 24) V.23
V.26ter V.26ter
V.32 V.32
modem for undef. interface No comparable value (note 5)
autobauding type 1 No comparable value (note 5, note 10)
7 User info. layer 2 protocol 6 User info.layer 2 prot. (note 6)
#5.1 X.25 link level (note 24) X.25 link level
ISO 6429, codeset 0 no comparable value
COPnoFlCt no comparable value
videotex profile 1 (note 7) no comparable value
X.75 layer 2 modified (CAPI) (note 24) X.25 link level
6d Fixed network user rate (note 15) 5a User rate
#5.1 FNUR not applicable (note 7) #5.1 no comparable value
9,6 kbit/s 9,6 kbit/s
12 kbit/s (note 7) 12 kbit/s
33.6 kbit/s no comparable value
64,0 kbit/s no comparable value (note 16)
6e Maximum number of traffic channels No comparable field
#3.1 1 TCH
2 TCH
3 TCH
4 TCH
5 TCH
6 TCH
7 TCH (note 7)
8 TCH (note 7)

18 Issue 01 (2009-04-06)
MSOFTX3000
6f Wanted air interface user rate (note 23) No comparable field

#4.1 air interface user rate not applicable (note
7)
9,6 kbit/s
14,4 kbit/s
19,2 kbit/s
28,8 kbit/s
38,4 kbit/s
43,2 kbit/s
57,6 kbit/s
interpreted by the network as 38.4 kbit/s
(note 7)
6d Other modem type (note 15) 5d Modem type
#7.6 No other modem type #6.1 no comparable value
V.34 V.34
6e Acceptable channel coding(s) No comparable field
#7.4 TCH/F4.8 acceptable (note 19)
TCH/F9.6 acceptable
TCH/F14.4 acceptable
6f User initiated modification indicator No comparable field
#7.5 (note 23)
User initiated modification not
required
User initiated modification upto 1
TCH/F may be requested
6g Acceptable channel coding(s) (note 20) No comparable field
#7.5 TCH/F28.8 acceptable
TCH/F32.0 acceptable
TCH/F43.2 acceptable (note 22)
6g Asymmetry preference indication (Note No comparable field
#4.3 23)
no preference
up link biased asymmetry preference
down link biased asymmetry preference

Issue 01 (2009-04-06) 19
MSOFTX3000
z The MSC sends an ADD REQ message to the MGW to connect to the termination of the
RNC ( ). Among the information elements of the ADD REQ message, only
the following information element varies with the call type (voice call or 3G video call):
a) For 3G video calls, the LocalControlDescriptor IE contains the following fields:

i. PLMN BC
ii. UP mode: Transparent
iii. DelErrSDU: No

20 Issue 01 (2009-04-06)
MSOFTX3000
iv. UP version: version1
z MSC sends an RAB assignment message to the RNC A ( ). Among the

information elements of the RAB message, only the following information element
varies with the call type (voice call or 3G video call):
a) For 3G video calls, the RAB IE contains the following fields:

i. trafficClass: conversational
ii. maxBitrate: 64 Kbit/s

Issue 01 (2009-04-06) 21
MSOFTX3000
iii. GuaranteedBitrate: 64 Kbit/s
iv. MaxSDU Size: 640
v. userPlaneInformation: transparent mode; uP ModeVersions: version1
z The MSC sends a SETUP message to UE B. The difference of the IEs between the 3G
video calls and voice calls is the same as the difference described in the previous
procedure where UE A sends a SETUP message to the MSC.
Impact
None.
Constraints
None.

22 Issue 01 (2009-04-06)
MSOFTX3000
1.3.4 Inter-ISUP-MSC 3G Video Calls

Flow Description
z In an inter-ISUP-MSC video call, the called party is paged in the same way as in the scenario of
normal voice call. Therefore, paging is not described separately in this section.
z In an inter-ISUP-MSC video call, the SRI procedure proceeds in the same ways as in the scenario of
intra-MSC 3G video call. For details about the SRI procedure, see the Intra-MSC 3G video calls.
Figure 1-4 Procedure of an inter-ISUP-MSC video call between 3G subscribers

Issue 01 (2009-04-06) 23
MSOFTX3000
The procedure of an inter-ISUP-MSC video call between 3G subscribers is as follows:

2. MSC A sends a CALL PROCEEDING message to UE A.
3. MSC A sends an ADD REQ message to MGW A, instructing MGW A to prepare
resources required for the termination connecting with RNC A.
4. MGW A returns an ADD REPLY message to MSC A.
5. MSC A sends an ADD REQ message to MGW A, to prepare gateway resources for
outgoing ISUP termination.
7. MSC A sends RNC A an RAB Assignment message where both the maximum bit rate
8. RNC A returns an RAB assignment response to MSC A.
9. MSC A sends an ISUP IAM message carrying User Service Information to MSC B.
10. MSC B sends a SETUP message to UE B, carrying the Bearer Capability IE where ITC
11. UE B returns a CALL CONFIRMED message. If the message does not carry a new
Bearer Capability IE, it indicates that the called UE supports the video call.
12. MSC B sends an ISUP ACM message to MSC A.
13. MSC B sends an ADD REQ message to MGW B, to prepare gateway resources for the
incoming ISUP termination.
14. MGW B returns an ADD REPLY message to MSC B.
15. MSC B sends an ADD REQ message to MGW B, to prepare gateway resources for
connecting to the termination of RNC B.
17. MSC B sends RNC B an RAB Assignment message where both the maximum bit rate
18. RNC B returns an RAB assignment response to MSC B.
19. UE B sends an ALERTING message to MSC B.
20. MSC B sends an ISUP CPG message to MSC A.
21. MSC A sends an ALERTING message to UE A.
22. UE B sends a CONNECT message to MSC B.
23. MSC B sends a CONNECT ACK message to UE B.
24. MSC B sends an ISUP ANM message to MSC A.
25. MSC A sends a CONNECT message to UE A.
26. UE A sends a CONNECT ACK message to MSC A.
27. H.245 channel establishment: UE A negotiates with UE B about the end-to-end H.245
terminal capability set (TerminalCapabilitySet/Ack/Reject/Release), H.245 master/slave
determination (MasterSlaveDetermination/Ack/Reject/Release), whether to send the
multiplex entry (MultiplexEntrySend/Ack/Reject/Release), and whether to open the
logical audio and video channels (OpenLogicalChannel/Ack/Reject/Release).After the
negotiation is complete and the H.245 channel is established, UE A communicates with
UE B through video.

24 Issue 01 (2009-04-06)
MSOFTX3000
released.
MSC A.
30. MSC A sends a RELEASE request to UE A.
31. MSC A sends an ISUP REL message to MSC B.
32. MSC B sends a DISCONNECT message to UE B.
33. UE A sends a RELEASE COMPLETE message to MSC A.
34. UE B sends a RELEASE request to MSC B.
35. MSC B sends an ISUP RLC message to MSC A.
36. MSC B sends a RELEASE COMPLETE message to UE B.
Key Messages and Information Elements
Only the ISUP-specific messages and IEs that vary from 3G video calls to normal voice calls are
described in this section. For details about other messages that vary with the call type, see the Intra-MS
3G Video Calls.
z The MSC sends an ADD REQ message to the MGW ( ) , to prepare resources
for incoming/outgoing ISUP terminations. Among the information elements of the ADD
REQ message, only the following information element varies with the call type (voice
call or 3G video call):
Local Descriptor
For 3G video calls, this information element contains the following property parameters:
i. SDP-a: It conveys the USI information element.
ii. SDP-b : It indicates the bandwidth is 64 kbit/s.

Issue 01 (2009-04-06) 25
MSOFTX3000
iii. SDP-m: It indicates that the service is data service (Note that other data services
also require this parameter).
z MSC A sends an ISUP IAM message to MSC B . Among the information elements
of the ISUP IAM message, only the following information element varies with the call
type (voice call or 3G video call):
a) Transmission medium requirement (TMR) information element: For 3G video calls,
this information element is set to 64 kbit/s unrestricted.
b) USI information element

For 3G video calls, the related fields of USI are as follows:
i. Information transfer Capability: unrestricted digital information
ii. Coding standard: ITUT
iii. Information transfer rate: 64 kbit/s
iv. transfer mode: circuit mode
v. User information layer-1 –protocol: H.223 &H.245

26 Issue 01 (2009-04-06)
MSOFTX3000
c) Access transport: The content of this information element is the same as that of the
LLC information element sent from the UE.
None.
Constraint
None.

Issue 01 (2009-04-06) 27
MSOFTX3000
1.3.5 Inter-BICC-MSC 3G Video Calls

Flow Description
z In an inter-BICC-MSC call, the called party is paged in the same way as in the scenario of normal
z In an inter-BICC-MSC video call, the SRI procedure proceeds in the same ways as in the scenario of
intra-MSC 3G video call. For details about the SRI procedure, see Intra-MSC 3G video calls.
z This scenario takes an inter-BICC-MSC video call (in fast forward setup mode) between 3G
subscribers as an example.
Figure 1-5 Procedure of an inter-BICC-MSC video call between 3G subscribers

28 Issue 01 (2009-04-06)
MSOFTX3000
The procedure of an inter-BICC-MSC video call between 3G subscribers is as follows:


Issue 01 (2009-04-06) 29
MSOFTX3000

BICC outgoing termination.
7. MGW A sends a NOTIFY REQ message to MSC A, carrying the tunnel packet.
8. MSC A returns a NOTIFY REPLY message to MGW A.
11. MSC A sends a BICC IAM message carrying User Service Information to MSC B.
Bearer Capability information element, it indicates that the called UE supports the video
call.
incoming BICC termination.
18. MGW B sends a NOTIFY REQ message to MSC B, carrying the tunnel packet.
19. MSC B returns a NOTIFY REPLY message to MSC B.
20. MSC B sends a BICC APM message to MSC A.
24. MSC B sends a BICC ACM message to MSC A.
28. MSC B sends a BICC ANM message to MSC A.
determination (MasterSlaveDetermination/Ack/Reject/Release), whether to the multiplex
entry (MultiplexEntrySend/Ack/Reject/Release), and whether to open the logical audio
and video channels (OpenLogicalChannel/Ack/Reject/Release).After the negotiation is
complete and the H.245 channel is established, UE A communicates with UE B through
video.
released.

30 Issue 01 (2009-04-06)
MSOFTX3000
33. (Assume that UE A terminates the call first) UE A sends a DISCONNECT message to
MSC A.
34. MSC A sends a RELEASE message to UE A.
35. MSC A sends a BICC REL message to MSC B.
39. MSC B sends a BICC RLC message to MSC A.
Only the BICC-specific messages and IEs that vary from 3G video calls to normal voice calls are
3G Video Calls.
z The MSC sends an ADD REQ message to the MGW ( ) , to prepare

resources for incoming/outgoing BICC terminations. Among the information elements of
the ADD REQ message, only the following information element varies with the call type
a) Local Descriptor: For 3G video calls, this information element contains the
following property parameters:
i. SDP-m: It indicates that the service is a data service.
ii. SDP-b: It indicates that the bandwidth is 64 KB.

Issue 01 (2009-04-06) 31
MSOFTX3000
iii. SDP-a: This information element contains the packaged USI information
element.
b) LocalControlDescriptor: For 3G video calls, this information element contains the

following fields:
i. UP mode: support
ii. UP error frame check mode(DelErrSDU): yes

32 Issue 01 (2009-04-06)
MSOFTX3000
iii. UP interface: cn
iv. UP direction: out
v. UP version: version 1 and version 2

Issue 01 (2009-04-06) 33
MSOFTX3000
z MSC A sends a BICC IAM message to MSC B ( ). Among the information

elements of the BICC IAM message, only the following information element varies with
the call type (voice call or 3G video call):
d) TMR information element: For 3G video calls, this information element is 64 kbit/s
unrestricted.
e) USI information element. For 3G video calls, this information element contains the
following fields:
iii. Information transfer rate: 64 Kbit/s
iv. Transfer mode: circuit mode
f) Access transport: The content of this information element is the same as that of the
LLC information element from the user side.

34 Issue 01 (2009-04-06)
MSOFTX3000
MUME (MUME) codec must be configured by running ADD MGW; otherwise, the
inter-BICC video calls cannot be connected.
Constraints
None.

Issue 01 (2009-04-06) 35
MSOFTX3000
1.3.6 Inter-SIP-MSC 3G Video Calls

Flow Description
z In an inter-SIP-MSC call, the called party is paged in the same way as in the scenario of normal
z In an inter-SIP-MSC video call, the SRI procedure proceeds in the same ways as in the scenario of
intra-MSC 3G video call. For details about the SRI procedure, see Intra-MSC 3G video calls.
z This scenario takes SIP-I call mode as an example.
Figure 1-6 Procedure of an inter-SIP-MSC video call between 3G subscribers

36 Issue 01 (2009-04-06)
MSOFTX3000
The procedure of an inter-SIP-MSC video call between 3G subscribers is as follows:

outgoing SIP termination.
7. MGW A sends a NOTIFY REQ message to MSC A.
8. MSC A returns a NOTIFY REPLY message to MGW A.
11. MSC A sends a SIP INVITE message to MSC B, carrying the SDP information and
packaged ISUP IAM message.
12. MSC B sends a 100 message to MSC A.
call.
incoming SIP termination.
19. MGW B sends a NOTIFY REQ message to MSC B.
20. MSC B returns a NOTIFY REPLY message to MSC B.
21. MSC B sends a SIP 183 message carrying the SDP information to MSC A.
22. MSC A sends a PRACK message to MSC B.
23. MSC A checks whether the codec information changes. If yes, MSC A sends a MOD
REQ message to MGW A to modify the bearer information of MGW A. After the
modification is successful, MGW A sends a MOD REPLY message to MSC A.
27. MSC B sends a SIP 180 message to MSC A.
28. MSC A sends a PRACK message to MSC B.

Issue 01 (2009-04-06) 37
MSOFTX3000

34. MSC A sends an ACK message to MSC B.
UE B through video.
37. H.245 channel disconnection: Between UE A and UE B, the H.245 audio and video
logical channels are closed (CloseLogicalChannel/Ack/Reject/Release), the H.245
sessions are terminated (EndSessionCommand), and the resources on the caller and
callee planes are released.
MSC A.
39. MSC A sends a RELEASE request to UE A.
40. MSC A sends a SIP BYE message to MSC B.
Only the SIP-specific messages and IEs that vary from 3G video calls to normal voice calls are
3G Video Calls.
z The MSC sends an ADD REQ message to the MGW ( ), to prepare

resources for incoming/outgoing SIP terminations. Among the information elements of
the ADD REQ message, only the following information element varies with the call type
c) LocalControlDescriptor: For 3G video calls, this information element contains the
i. UP mode: transparent

38 Issue 01 (2009-04-06)
MSOFTX3000
ii. UP error frame check mode (UP DelErrSDU): yes
iii. UP version: version 1 and version 2
d) Local Descriptor. For 3G video calls, this information element contains the
i. SDP-m: audio $ RTP/AVP 121

Issue 01 (2009-04-06) 39
MSOFTX3000
ii. SDP-a:rtpmap:121 CLEARMODE/8000
iii. SDP-a: 10 (packaging duration)
z MSC A sends a SIP INVITE message to MSC B ( ). The difference of the

information elements (contained in the INVITE message) between video calls and voice
calls is as follows:
a) The SIP INVITE message carries the SDP information of the outgoing SIP
termination.

40 Issue 01 (2009-04-06)
MSOFTX3000
b) The SIP INVITE message carries the packaged ISUP IAM message, in which the
3G related video information elements are encapsulated in code streams as shown in
the following figure. You can check the encapsulated ISUP IAM message through
code streams.
Click Show ISUP Body to obtain the complete encapsulated ISUP IAM message, in
which the information elements of 3G video calls are completely the same as those
of inter-ISUP-MSC 3G video calls.

Issue 01 (2009-04-06) 41
MSOFTX3000
TMR information element: For 3G video calls, this information element is 64 kbit/s
unrestricted.
USI information element:

For 3G video calls, this information element contains the following fields:
iii. Information transfer rate: 64 kbit/s

42 Issue 01 (2009-04-06)
MSOFTX3000
iv. Transfer mode: circuit mode

Access transport: The content of this information element is the same as that of
the LLC information element from the user side.
None.
Constraints
None.
1.3.7 Video Call Announcement Flow (Local Announcement

Notification )
Description
The 3G video call service is a data service and does not support inband announcement.
Therefore, announcement is implemented by the UE. For details, see the 3GPP 22.001
Appendix F 2.4.
Applicability
This method will apply in all cases where signaling is capable of indicating the supervisory
tone required. However, for connection to certain fixed networks where this signaling is not
possible, fixed network tones will be carried over the traffic channel.
User equipment may employ any suitable technique to indicate supervisory information.
However, if tones are employed, they should be in accordance with the present document. The
use of these tones in the MSC is preferred.

Issue 01 (2009-04-06) 43
MSOFTX3000
The tones and/or announcement to the calling party should not be provided if Information transfer
capability is set to UDI. The announcement, including ringback tone and call failure tone are played by
the UE. The following section describes the announcement notification upon a 3G video call failure.
Announcement Notification Upon An Intra-MSC 3G Video Call Failure
Figure 1-7 Announcement notification upon an intra-MSC 3G video call failure
The procedure of an announcement notification upon an intra-MSC 3G video call failure is as

follows:
1. UE A sends a SETUP message to MSC A, carrying the Bearer Capability IE where ITC
2. The call fails. MSC A sends a RELEASE message carrying the failure cause code to UE
A.
3. Based on the failure cause, UE A plays a call failure announcement to the subscriber.

None.
Impact
None.
Constraints
None.

44 Issue 01 (2009-04-06)
MSOFTX3000
Announcement Notification Upon An Inter-MSC 3G Video Call Failure
Figure 1-8 Announcement notification upon an inter-MSC 3G video call failure
The procedure of an announcement notification upon an inter-MSC 3G video call failure is as

follows:
2. MSC A sends an IAM message to MSC B, carrying the USI specific to video bearer
capability.
3. MSC B sends PAGING messages to UE B for multiple times (in a specified time) but
does not receive any responses. MSC B then determines that the video call does not
require VMSC announcement and sends a REL message to MSC A, carrying the failure
cause (Cause = No User Responding).
4. MSC A releases the video call and forwards the REL message with the failure cause "No
User Responding" to UE A.
5. Based on the failure cause, UE A plays the corresponding announcement to the
subscriber, informing that the callee does not respond and the video call fails.

None.
Impact
None.
Constraints
None.

Issue 01 (2009-04-06) 45
MSOFTX3000
USSD Notification Upon a 3G Video Call Failure

USSD announcement upon a video call failure:
When a video call fails, the caller terminal displays a call failed alert, but it does not provide
more details about the cause of the call failure. Without knowledge of the call failure cause,
the caller is likely to make retries before giving up the hope of reaching the callee. This
increases the rate of unsuccessful call attempts especially when the call failure is due to
invalid number, wrong dialing, or unreachable callee.
To address this problem, the network sends a USSD notification about the call failure cause to
the caller. This reduces the number of unnecessary call retries and improves the call complete
rate. Before the USSD notification upon a call failure feature is ready for use, you must run
the ADD VPCFN command to correlate a USSD string with each failure cause code.
The USSD notification upon a call failure feature is configured only on the originating MSC;
other tandem or terminating MSCs do not support this feature.
Figure 1-9 USSD notification upon a 3G video call failure
The procedure of the USSD notification upon a 3G video call failure is as follows:
2. MSC A sends an outgoing IAM message to MSC B, carrying the USI specific to video
bearer capability.
3. MSC B sends PAGING messages to UE B for multiple times (in a specified time) but
does not receive any responses. MSC B then determines that the video call does not

46 Issue 01 (2009-04-06)
MSOFTX3000
require VMSC announcement and sends a REL message with the failure cause "No User
Responding" to MSC A.
4. MSC A activates the USSD notification function and queries the VP Call Failure
Processing table by the failure cause code "No User Responding" to find out the
correlated USSD string.
5. MSC A sends a REGISTER message with the code stream of the USSD string "No User
Responding" to UE A.
6. Based on the sting "No User Responding" contained in the REGISTER message, UE A
displays the string to subscriber A.
7. UE A sends a FACILITY message to MSC A, indicating that the USSD operation is
successful.
8. MSC A continues the call release processing.
z MSC A sends an RRGISTER message to UE A .

The RRGISTER message includes the facility information element that contains the code
streams of "No User Responding".

Issue 01 (2009-04-06) 47
MSOFTX3000
None.
Constraints
None.
1.3.8 Interaction Between the 3G Video Call Service and the

Supplementary Service
The 3G video call service is a BS30 service. According to the 3GPP 22.004 protocol, the 3G
video call service is compliant with the following supplementary services:
a) Number display supplementary services: The 3G video service supports the number
display supplementary services. The implementation procedure of this type of
supplementary service is the same as that of a common voice call.
b) Call forwarding supplementary services: The 3G video service supports the call
forwarding supplementary services. The implementation procedure of this type of
supplementary service is the same as that of a common voice call.
c) Call waiting (CW) supplementary service: The 3G video service supports the CW
supplementary service. At present, the MSOFTX3000 supports only the scenario in
which the 3G video call waits the voice call.
Specific application scenario: Subscriber B originates a voice call to CW subscriber A who is
engaged in a video call. If subscriber A chooses to connect to subscriber B, the MSC releases
the connected video call and connects the incoming voice call.
At present, only the 3G terminals such as NOKIA 6680 and NOKIA7600 support the CW
supplementary service.
d) HOLD supplementary service: The 3G video service does not support the HOLD
e) MPTY supplementary service: The 3G video service does not support the MPTY
f) ECT supplementary service: The 3G video service does not support the ECT
SS Telephony Emergency SMS PTP SMS-CB Fax cct Data

Call
TS11 TS12 TS21 TS22 TS 23 TS 6x BS2x,

BS3x
eMLPP Yes Yes9 Yes Yes
CD Yes Yes Yes
CLIP Yes Yes Yes
CLIR Yes Yes Yes
COLP Yes Yes Yes

48 Issue 01 (2009-04-06)
MSOFTX3000
SS Telephony Emergency SMS PTP SMS-CB Fax cct Data

Call
COLR Yes Yes Yes

CFU Yes Yes Yes
CFB Yes Yes Yes
CFNRy Yes Yes Yes
CFNRc Yes Yes Yes
CW1 Yes Yes Yes
HOLD2 Yes
MPTY Yes
ECT Yes
z The 3G video call service is a data service. After the bearer negotiation is complete, all data
transmission parameter attributes are configured. Therefore, the supplementary services that require
the movement of terminations, such as MPTY, CALL HOLD, and ECT are not supported.
z The number display supplementary service is always bundled with specific service codes. Therefore,
ensure that each service code of the video service maps a supplementary service (such as CLIP,
CLIR, COLP, and COLR). Otherwise, the number display service is unavailable.
Interaction Between the 3G Video Call Service and the CFU Service
The bearer establishment process is generally the same, and therefore is not included in this scenario.
This section takes the BICC signaling as an example to describe the interaction between the 3G video
call service and the CFU service.

Issue 01 (2009-04-06) 49
MSOFTX3000
Figure 1-10 Interaction between the 3G video call service and the CFU service
The procedure for interaction between the 3G video call service and the CFU service is as
follows:
1. (G)MSC B receives a BICC IAM message, carrying the BC_IE of which ITC is UDI and
ORA is H.223&H.245.
2. (G)MSC B sends a Send Routing Info (SRI) message with the ISDN BC information
element to the HLR.
3. The HLR returns a SRI ACK message carrying the forwarding number to (G)MSC B.
4. (G)MSC B sends a SRI message to the HLR.
5. The HLR sends a PRN message to the VLR.
6. The VLR returns a PRN ACK message carrying the MSRN to the HLR.
7. The HLR returns a SRI ACK message carrying the forwarding number to (G)MSC B.
8. (G)MSC B sends an IAM message to the terminating MSC C of the forwarded-to UE.
9. MSC C sends a PAGING message to the forwarded-to UE.
10. UE C sends a PAGING RSP message to MSC C.

50 Issue 01 (2009-04-06)
MSOFTX3000
11. MSC C sends a SETUP message carrying the multimedia BC to the UE.
12. The UE (if supports the multimedia BC) returns the CALL CONFIRMED message to
MSC C.
13. MSC C sends an RAB ASSIGNMENT REQ message to the RNC.
14. The RNC returns an RAB ASSIGNMENT RSP message to MSC C. Upon receiving the
RAB ASSIGNMENT RSP message, the RNC establishes the air interface bearer.
15. After alerted, the UE sends an ALERTING message to MSC C.
16. MSC C receives an ALERTING message and sends an ACM message to (G)MSC B.
17. (G)MSC B sends the ACM message to the peer office.
18. After the callee answers the phone, the UE sends a CONNECT message to MSC C.
19. MSC C sends an ANM message carrying CONNECT NUMBER to (G)MSC B,
informing the peer end of the forwarded-to number.
20. (G)MSC B sends an ANM message to the peer office.
21. MSC C sends a CONNECT ACK message to the UE, informing the UE that the call
connection is established and the video call begins.

None.
Constraints
None.
Interaction Between the 3G Video Call Service and the CFB (User-Determined
Busy) or CFNRy (No Answering) Service
call service and the CFB (user-determined busy) or CFNRY (no answering) service.

Issue 01 (2009-04-06) 51
MSOFTX3000
Figure 1-11 Interaction between the 3G video call service and the CFB (user-determined
busy/CFNRy (no answering) service
The procedure for interaction between the 3G video call service and the CFB
(user-determined busy) or CFNRy service (no answering) is as follows:
1. (G)MSC A receives a BICC IAM message.

52 Issue 01 (2009-04-06)
MSOFTX3000
2. (G)MSC A sends a SRI message to the HLR, carrying the ISDN BC information
element.
3. The HLR sends a Proving Roaming Number (PRN) message to the VLR.
5. The HLR returns a SRI ACK message to (G)MSC A.
6. (G)MSC A sends an IAM message to MSC C.
7. MSC C sends a PAGING message to the UE.
8. The UE returns a PAGING RSP to MSC C.
9. MSC C sends a SETUP message carrying the multimedia BC to the UE.
10. The UE (if supports the multimedia BC) returns a CALL CONFIRMED message to
MSC C.
RAB ASSIGNMENT RSP message, the MSC C establishes the air interface bearer.
13. After alerted, the UE sends an ALERTING message to MSC C.
14. Upon receiving the ALERTING message, MSC C sends an ACM message to the peer
office.
15. The callee is busy or does not answer the call. UE B then sends a DISCONNECT
message to MSC C.
16. MSC C sends a RELEASE message to UE B to release the connection with UE B.
17. The call is forwarded to UE C. MSC C then sends a PAGING message to UE C.
18. UE C returns a PAGING RSP message to MSC C.
19. MSC C receives a RELEASE COMPLETE message from UE B. The connection
between MSC C and UE B is released.
20. MSC C sends a SETUP message carrying the multimedia BC to UE C.
21. The UE (if supports the multimedia BC) returns a CALL CONFIRMED message to
MSC C.
RAB ASSIGNMENT RSP message, MSC C establishes the air interface bearer.
24. UE C is alerted and sends an ALERTING message to MSC C.
25. MSC C sends a CPG message to (G)MSC A, informing (G)MSC A that the call is being
established.
26. MSC C receives a CONNECT message carrying CONNECT NUMBER from UE C,
informing MSC C of the forwarded-to number and the call answered.
27. MSC C sends an ANM message to (G)MSC A, informing (G)MSC A that the call
forwarded to UEC is answered.
28. MSC C sends a CONNECT_ACK message to UE C. The video call is connected.

None.

Issue 01 (2009-04-06) 53
MSOFTX3000
Constraints
None.
Interaction Between the 3G Video Call Service and the CFB (Video Call
Forwarding)/ or CFNRc-2 (Unreachable) Service
call service and the CFB (video call forwarding)/ or CFNRc-2 (unreachable) service.
Figure 1-12 Interaction between the 3G video call service and the CFB (video call forwarding)/ or
CFNRc-2 (unreachable) service

54 Issue 01 (2009-04-06)
MSOFTX3000
The procedure for interaction between the 3G video call service and the CFB (video call
forwarding)/ or CFNRc-2 (unreachable) service is as follows:
2. (G)MSC A sends a SRI message carrying the ISDN BC information element to the HLR.
7. MSC C sends a PAGING message to UE B.
8. After the paging times out, MSC C continues to send the PAGING message to UE B (the
number of times the MSC sends the PAGING message is determined by the MSC).
9. After several paging failures, MSC C queries HLR C for the roaming number of UE C if
UE B subscribes to the CFB service and the call must be forwarded to UE C.
10. MSC C sends a PAGING message to UE C.
11. MSC C receives a PAGING ACK message from UE C.
12. MSC C sends a SETUP message carrying the multimedia BC to UE C.
13. UE C (if supports the multimedia BC) returns a CALL CONFIRMED message to MSC
C.
RAB ASSIGNMENT RSP response, the MSC C establishes the air interface bearer.
17. Upon receiving the ALERTING message from UE C, MSC C sends an ACM message to
the peer office.
18. (G)MSC A sends an ACM message to UE A.
19. After the callee answers the phone, UE C sends a CONNECT message to MSC C.
20. MSC C sends an ANM message carrying CONNECT NUMBER to the peer office,
informing the peer office of the forwarded-to number.
21. MSC C sends a CONNECT ACK message to UE C, informing UE C that the call
22. (G)MSC A sends an ANM message to UE A.
23. The caller and the callee start the video conversation.

None.
Constraints
None.

Issue 01 (2009-04-06) 55
MSOFTX3000
Interaction Between the 3G Video Call Service and the CFB Service (NDB
Network-Determined Busy)
call service and the CFB service (NDB network-determined busy).
Figure 1-13 Interaction between the 3G video call service and the CFB service (NDB
network-determined busy)

56 Issue 01 (2009-04-06)
MSOFTX3000
The procedure for interaction between the 3G video call service and the CFB service (NDB
network-determined busy) is as follows:
2. (G)MSC A sends a SRI message carrying the ISDN BC information element to the HLR.
7. MSC C knows that UE B is busy and the call must be forwarded to UE C, and then sends
a PAGING request to UE C.
8. UE C returns a PAGING ACK message to MSC C.
9. Upon receiving the PAGING ACK message, the MSC sends a SETUP message carrying
the multimedia BC (BCm) to UE C.
10. UE C (if supports the multimedia BC) returns a CALL CONFIRMED message to MSC
C.
RAB ASSIGNMENT RSP message, the MSC C establishes the air interface bearer.
14. MSC C receives an ALERTING message from UE C and sends an ACM message to
(G)MSC A.
15. (G)MSC A sends the ACM message to the peer office.
16. After the callee answers the phone, UE C sends a CONNECT message to MSC C.
17. MSC C sends an ANM message carrying CONNECT NUMBER to (G)MSC A,
informing the peer office of the forwarded-to number.
18. (G)MSC A sends an ANM message carrying CONNECT NUMBER to the peer office.
19. MSC C sends a CONNECT ACK message to UE C, informing UE C that the call

None.
Constraints
None.

DTMF
Based on the 3GPP 23.014 protocol, the 3G video call service is a data service and does not
support the DTMF. Therefore, the protocol compliance check must be implemented by the
UE.

Issue 01 (2009-04-06) 57
MSOFTX3000
The use of DTMF is permitted only when the speech teleservice is being used or during the
speech phase of alternate speech/data and alternate speech/facsimile teleservices. This
permission of using the DTMF is checked in the UE.

58 Issue 01 (2009-04-06)
MSOFTX3000

Intelligent Network (IN) Service
VP IN Service Triggered for the Caller and the Callee
Figure 1-14 VP IN service triggered for the caller and the callee

Issue 01 (2009-04-06) 59
MSOFTX3000
z In the preceding flow chart, HLR A/B functions as the originating and terminating HLRs and the
SCP A/B functions as the originating and terminating SCPs.
z The MSC server receives a SETUP message from the calling UE. Based on the OCSI and the
triggering criteria (if an OCSI is available and the BS30 service is allowed to be triggered), the MSC
server determines that the IN procedure must be triggered. Then, the MSC server sends an IDP
request that includes the BS30 to the originating SCP.
z If the SCP detects that the BC parameter contained in the IDP request indicates the BS30 service, the
call is charged at the rate of video calls.
z The MSC server sends the SRI message that includes the called number and the BC parameter of
BS30 to HLR B. Based on the TCSI and the triggering criteria (if a TCSI is available and the BS30
service is allowed to be triggered), HLR B determines that the called IN procedure must be triggered
and sends a SRI-ACK response that includes the TCSI to the MSC server.
The procedure for triggering the VP IN service for the caller and the callee is as follows:
1. UE A sends a SETUP message to MSC server A, carrying the Bearer Capability IE
where ITC is UDI and ORA is H.223&H.245.
2. MSC server A obtains the called MSRN and sends a Call_Proceeding message to UE A
(the caller).
3. MSC server A continues to process the call and triggers the IN service based on the
caller service profile OCSI. Then, the MSC server sends an IDP message to SCP A. The
bearer type in the IDP message is set to BS30.
4. Step 4/5/6 Upon receiving the IDP message, SCP A determines that the caller must be
charged at the rate of video calls and sends the RRBE, AC, and Continue messages (and
FCI signaling if required) to MSC server A.
5. MSC server A sends an SRI request to HLR B.
6. HLR B returns the SRI_ACK message that includes the TCSI to MSC server A.
7. Upon receiving the SRI_ACK, MSC SERVER A sends an IDP request that includes the
parameter BS30 to SCP B.
8. Step 10/11/12 SCP B receives the IDP message and determines that the callee must be
charged at the rate of video calls. Then, SCP B sends the RRBE, AC, and Continue
messages to MSC server A.
9. MSC server A receives the Continue message and sends the SRI message to HLR B to
obtain the routing information of UE B.
10. HLR B queries MSC server B attached by the callee for the roaming number.
11. MSC server B returns the roaming number to HLR B. If MSC server B supports
pre-paging, it originates a paging procedure before sending the roaming number to HLR
B.
12. HLR B returns the routing information of UE B to MSC server A.
13. MSC server A sends a BICC IAM message to MSC server B. If the callee has subscribed
to the CLIP service, the BICC IAM message must include the calling number.
14. If pre-paging is not initiated in step 12, MSC server B sends a PAGING request to UE B.
15. UE B returns a PAGING ACK message to MSC server B.
16. MSC server B sends a SETUP message to UE B, carrying the Bearer Capability IE
call.

60 Issue 01 (2009-04-06)
MSOFTX3000
18. UE B is alerted and sends an ALERTING message to MSC server B.

19. MSC server B sends a BICC ACM message to MSC server A.
20. MSC server A sends an ALERTING message to UE A. The VP service is also a data
bearer service, but 3GPP does not define how to play a ringback tone for a video call.
Therefore, during a video call, MSC server A and MSC server B do not play the
ringback tone for the caller.
21. The callee answers the call, and UE B sends a CONNECT message to MSC server B.
22. MSC server B sends a BICC ANM message to MSC server A.
23. MSC server B sends a CONNECT ACK message to UE B.
24. MSC server A sends a CONNECT message to UE A.
25. UE A returns a CONNECT ACK message to MSC server A.
logical audio and video channels (OpenLogicalChannel/Ack/Reject/Release). After the
UE B through video.
27. H.245 channel disconnection: The H.245 audio and video logical channels between UE
A and UE B are closed (CloseLogicalChannel/Ack/Reject/Release), the H.245 sessions
are terminated (EndSessionCommand), and the resources on the caller and callee planes
are released.
MSC server A.
29. MSC server A sends a BICC REL message to MSC server B, to request it (MSC server
B) to release the call on the terminating side.
30. MSC server B sends a DISCONNECT message to UE B.
31. MSC server B sends a BICC RELEASE COMPLETE message to MSC server A.
32. MSC server A sends a RELEASE message to UE A.
33. UE A sends a RELEASE COMPLETE message to MSC server A.
34. UE B sends a RELEASE request to MSC server B.
35. MSC server B sends a RELEASE COMPLETE message to UE B.
36. MSC server A sends an ACR message to SCP A. The ACR contains the session
duration.
37. MSC server A sends an ERB(o_Disconnect) message to SCP A.
38. SCP A sends an RC message to MSC server A.
39. MSC server A reports an ACR message to SCP B. The ACR contains the session
duration.
40. MSC server A sends an ERB(t_Disconnect) message to SCP B.
41. SCP B sends an RC message to MSC server A.


Issue 01 (2009-04-06) 61
MSOFTX3000
For interaction between the 3G video call service and the IN service, the data configuration of
the 3G video call service must be consistent with the IN call configuration.
Constraints
None.

62 Issue 01 (2009-04-06)
MSOFTX3000
VP IN Service Triggered for the Caller
Figure 1-15 VP IN service triggered for the caller

Issue 01 (2009-04-06) 63
MSOFTX3000
triggering criteria (if an OCSI is available and the BS30 service is allowed to be triggered), the MSC
server determines that the IN procedure must be triggered . Then, the MSC server sends an IDP
request that includes the BS30 to the originating SCP.
BS30 to HLR B. Based on the TCSI and the triggering criteria (if a TCSI is unavailable and the
BS30 service is not allowed to be triggered), HLR B determines that the called IN procedure need
not be triggered. Then, HLR B sends a SRI-ACK response that includes the MSRN instead of the
TCSI to the MSC server.
The procedure for triggering the VP IN service for the caller is as follows:
2. MSC server A obtains the called MSRN and sends a Call_Proceeding message to UE A
(the caller).
3. MSC server A receives the call request and triggers the IN service based on the OCSI
contained in the caller service profile. Then, MSC server A sends an IDP message to
SCP A. The bearer type in the IDP message is set to BS30.
4. Step 4/Step 5/Step 6 SCP A receives the IDP message and determines that the caller
must be charged at the rate of video calls. Then, SCP A sends RRBE, AC, and Continue
5. MSC server A sends a SRI message to HLR B to obtain the routing information of UE B.
6. HLR B queries MSC server B serving the callee for the roaming number.
B.
9. MSC server A sends a BICC IAM message to MSC server B. If the callee has subscribed
to the calling line identification display (CLIP) service, the BICC IAM message must
include the calling number.
10. If pre-paging is not initiated, MSC server B sends a PAGING request to UE B.
13. UE B returns a CALL CONFIRMED message to MSC server B. If the message does not
contain a new Bearer Capability information element, it indicates that the called UE
supports the video call.

64 Issue 01 (2009-04-06)
MSOFTX3000

logical audio and video channels (OpenLogicalChannel/Ack/Reject/Release). After the
UE B through video.
23. H.245 channel disconnection: Between UE A and UE B, the H.245 audio and video
logical channels are closed (CloseLogicalChannel/Ack/Reject/Release), the H.245
sessions are terminated (EndSessionCommand), and the resources on the caller and
callee planes are released.
MSC server A.
25. MSC server A sends a BICC REL message to MSC server B, to request it (MSC server
B) to release the call on the terminating side.
32. MSC server A sends an ACR message to SCP A. The ACR contains the session
duration.
33. MSC server A sends an ERB(o_Disconnect) message to SCP A.
34. SCP A sends an RC message to MSC server A.

The interaction between the 3G video call service and the IN service is compliant with the IN
call configurations.
Constraints
None.

Issue 01 (2009-04-06) 65
MSOFTX3000
VP IN Service Triggered for the Callee
Figure 1-16 VP IN service triggered for the callee

66 Issue 01 (2009-04-06)
MSOFTX3000
triggering criteria (if there is no OCSI and the triggering criteria forbids the triggering of the BS30
service), the MSC server determines that the IN procedure need not be triggered. Then, the MSC
server initiates an SRI instead of an IDP request to the HLR.
BS30 to HLR B. Based on the TCSI and the triggering criteria (if a TCSI is available and the BS30
service is allowed to be triggered), HLR B determines that the called IN procedure must be triggered
and sends a SRI-ACK response that includes the TCSI to the MSC server.
The procedure for triggering the VP IN service for the callee is as follows:
2. MSC server A obtains the called MSRN and sends a Call_Proceeding message to UE A.
3. MSC server A sends an SRI request to HLR B.
4. HLR B returns a SRI_ACK that includes the TCSI to MSC server A.
5. Upon receiving the SRI_ACK, MSC SERVER A sends an IDP request carrying the
parameter BS30 to SCP B.
6. Step 6/7/8 SCP B receives the IDP message and determines that the callee must be
charged at the rate of video calls. Then, SCP B sends the RRBE, AC, and Continue
7. MSC server A receives the Continue message and sends the SRI message to HLR B to
obtain the routing information of UE B.
8. HLR B queries MSC server B serving the callee for the roaming number.
B.
11. MSC server A sends a BICC IAM message to MSC server B. If the callee subscribes to
the caller identification display service, the BICC IAM message must include the caller
number.
12. If pre-paging is not initiated in step 10, MSC server B sends a PAGING request to UE B.
15. UE B returns a CALL CONFIRMED message to MSC server B. If the message does not
carry a new Bearer Capability information element, it indicates that the called UE
supports the video call.

Issue 01 (2009-04-06) 67
MSOFTX3000

UE B through video.
25. H.245 channel disconnection: The H.245 audio and video logical channels between UE
A and UE B are closed (CloseLogicalChannel/Ack/Reject/Release), the H.245 sessions
are terminated (EndSessionCommand), and the resources on the caller and callee planes
are released.
MSC server A.
27. MSC server A sends a BICC REL message to MSC server B, to request MSC server B to
release the call on the terminating side.
34. MSC server A reports an ACR message to SCP B. The ACR contains the session
duration.
35. MSC server A sends an ERB(t_Disconnect) message to SCP B.
36. SCP B sends an RC message to MSC server A.

The interaction between the 3G video call service and the IN service is compliant with the IN
call configurations.
Constraints
None.

68 Issue 01 (2009-04-06)
MSOFTX3000
1.3.11 3G Video Call Fallback

Multimedia Fallback When the Caller Does Not Subscribe to the Multimedia
Service
Figure 1-17 Multimedia fallback when the caller does not subscribe to the multimedia service
The procedure of a 3G video call fallback when the caller does not subscribe to the
multimedia service is as follows:
1. UE A sends a SETUP message to MSC A. In the SETUP message, the Repeat Indicator
information element is set to support of service change and fallback; the first BC
(BCm) indicates the multimedia BC and the second BC (BCsp) indicates the voice BC.
2. MSC A receives the SETUP message and determines that the caller does not subscribe to
the multimedia call service. MSC A then sends a Call Proceeding message that includes
only the voice BC to UE A.
3. The system continues to connect the call as a voice call.

None.
Constraints
None.

Issue 01 (2009-04-06) 69
MSOFTX3000
Multimedia Fallback When the Callee Does Not Subscribe to the Multimedia
Fallback Service
Figure 1-18 Multimedia fallback when the callee does not subscribe to the multimedia fallback
service
The procedure of a 3G video call fallback when the callee does not subscribe to the
multimedia fallback service is as follows:
1. UE A sends a SETUP message to MSC A. In the SETUP message, the information
element Repeat Indicator is set to support of service change and fallback; the first BC
2. Upon receiving the SETUP message, MSC A sends a Send Routing Info Req message
that includes the multimedia bearer information to the HLR serving the callee.
3. The HLR determines that the called subscriber does not subscribe to the multimedia
service and sends a Send Routing Info Ack message that includes BEARER SERVICE
NOT SUPPORTED to the MSC.
4. Upon receiving the Send Routing Info Ack message, MSC A finds that the cause value is
Bearer Service Not Supported and the current call is a 3G video call. MSC A then
triggers the multimedia fallback procedure and sends a Send Routing Info Req message
that includes the voice bearer information to the HLR serving the callee.
5. The HLR returns a Send Routing Info Ack message that includes the roaming number to
MSC A.
6. MSC A sends a Call Proceeding message that includes only the voice BC to UE A.
7. MSC A sends an outgoing IAM message that includes only the voice BC to MSC B.

70 Issue 01 (2009-04-06)
MSOFTX3000

None.
Constraints
None.
Multimedia Fallback When the Callee Is in the 2G Network
Figure 1-19 Multimedia fallback when the callee is in the 2G network
The procedure of a 3G video call fallback when the callee is in the 2G network is as follows:
1. UE A sends a SETUP message to MSC A. In the SETUP message, the information
2. Upon receiving the SETUP message, MSC A sends a Send Routing Info Req message
that includes the multimedia bearer information to the HLR serving the callee.
3. The HLR sends a PRN message to MSC B serving the callee to request for the roaming
number.

Issue 01 (2009-04-06) 71
MSOFTX3000
4. MSC B determines that the callee is in the 2G network and sends a response that
includes the cause value FACILITY NOT SUPPORTED to the HLR serving the callee.
5. The home HLR sends a Send Routing Info Req Ack message that includes the cause
value FACILITY NOT SUPPORTED to MSC A.
6. MSC A determines that the current call is a 3G video call, and the cause value contained
in the Send Routing Info Req Ack message is FACILITY NOT SUPPORTED. MSC A
then triggers the multimedia fallback procedure and sends the Send Routing Info Req
message that includes the voice bearer information to the HLR serving the callee.
7. The HLR sends a PRN message to the terminating MSC B to request for the roaming
number.
8. MSC B returns a response to the HLR that includes the assigned roaming number.
9. The HLR returns a Send Routing Info Req Ack message that includes the assigned
roaming number to MSC A.
10. MSC A sends a Call Proceeding message that includes only the voice BC to UE A.
11. MSC A sends an outgoing IAM message that includes only the voice BC to MSC B.
Multimedia Fallback When the Called UE Does Not Support the Multimedia
Call Fallback
Figure 1-20 Multimedia fallback when the called UE does not support the multimedia call
fallback
The procedure of a 3G video call fallback when the called UE does not support the
multimedia call fallback is as follows:
2. UE A sends a SETUP message to the MSC. In the SETUP message, the information
3. Upon receiving the SETUP message, the MSC sends the SETUP message to UE B (the
called UE). In the SETUP message, the information element Repeat Indicator is set to

72 Issue 01 (2009-04-06)
MSOFTX3000
support of service change and fallback; the first BC (BCm) indicates the multimedia
BC and the second BC (BCsp) indicates the voice BC.
4. UE B does not support the 3G video call and sends a CALL CONFIRM message that
includes only the voice BC to the MSC.
5. The MSC sends a Call Proceeding message that includes only the voice BC to UE A.

None.
Constraints
None.

Issue 01 (2009-04-06) 73
MSOFTX3000
Multimedia Fallback When the Called UE Does Not Support Repeat Indicator
Figure 1-21 Multimedia fallback when the called UE does not support Repeat Indicator
2. The procedure of a 3G video call fallback when the called UE does not support Repeat
Indicator is as follows:
1. UE A sends a SETUP message to the MSC. In the SETUP message, the information
2. Upon receiving the SETUP message, the MSC sends the SETUP message to UE B (the
called UE). In the SETUP message, the information element Repeat Indicator is set to
support of service change and fallback; the first BC (BCm) indicates the multimedia
BC and the second BC (BCsp) indicates the voice BC.
3. UE B does not support the Repeat Indicator that is set to support of service change and
fallback and sends a STATUS message that includes the cause value Conditional IE
error to the MSC.
4. If bit 1 of P1000 is set to 1, the MSC sends another SETUP message containing BCm to
UE B. If bit 1 of P1000 is set to 0, the MSC sends another SETUP message containing
BCsp to UE B. The default value of bit 1 of P1000 is 1.
5. UE B sends a CALL CONFIRM message to the MSC.
6. If the MSC sends another SETUP message containing BCsp to UE B in step 4, the MSC
sends a CALL PROCEEDING message containing BCsp and sets up a voice call. If the

74 Issue 01 (2009-04-06)
MSOFTX3000
MSC sends another SETUP message containing BCm to UE B in step 4, the MSC sends
a CALL PROCEEDING message containing BCm and sets up a multimedia call.

If bit 1 of P1000 is set to 1, the MSC sends another SETUP message containing BCm to UE B.
If bit 1 of P1000 is set to 0, the MSC sends another SETUP message containing BCsp to UE
B.
Constraints
None.
Multimedia Fallback Triggered by Handover from 3G Video Calls to 2G Video

Calls
Figure 1-22 Multimedia fallback triggered by handover from 3G video calls to 2G video calls
The procedure of a 3G video call fallback triggered by handover from 3G video calls to 2G
video calls is as follows:

Issue 01 (2009-04-06) 75
MSOFTX3000
1. The RNC serving UE A sends a RELOCATION REQUIRED message to the MSC. The
target cell is a 2G cell.
2. The MSC receives the RELOCATION REQUIRED message and determines that the call
is a multimedia call and refuses to perform the handover.
3. The MSC sends a MODIFY message containing the BCsp to UE A that initiates the
handover.
4. UE A sends a MODIFY COMPLETE message to the MSC.
5. The MSC sends a MODIFY message containing the BCsp to UE B.
6. UE B sends a MODIFY COMPLETE message to the MSC.
7. The MSC sends a MOD REQ to the MGW to request the MGW to change the attributes
of the called termination.
8. The MGW returns a MOD REPLY message to the MSC.
9. The MSC sends a RAB ASSIGN MODIFY message to RNC B to request RNC B to
modify the air interface resources.
10. RNC B returns a RAB ASSIGN MODIFY RSP message to the MSC.
11. The MSC sends a MOD REQ to the MGW to request the MGW to change the attributes
of the calling termination.
12. The MGW returns a MOD REPLY message to the MSC.
13. The MSC sends a RAB ASSIGN MODIFY message to RNC A to request RNC B to
14. RNC A returns a RAB ASSIGN MODIFY RSP message to the MSC. The call becomes
stable, and the system connects the call as a voice call.

None.
Constraints
None.

76 Issue 01 (2009-04-06)
MSOFTX3000
Multimedia Fallback Triggered When the RNC Sends the Bearer Modification
Request
Figure 1-23 Multimedia fallback triggered when the RNC sends the bearer modification request
The procedure of a 3G video call fallback triggered when the RNC sends the bearer
modification request is as follows:
1. RNC A sends a RAB MODIFY REQ message to the MSC when a multimedia call is
active.
2. The MSC receives the RAB MODIFY REQ message and determines that the call is a
multimedia call. Then, the MSC sends a MODIFY message containing the BCsp to UE
A.
3. UE A sends a MODIFY COMPLETE message to the MSC.
4. The MSC sends a MODIFY message containing the BCsp to UE B.
5. UE B sends a MODIFY COMPLETE message to the MSC.
6. The MSC sends a MOD REQ to the UMG to request the UMG to modify the attributes
of the called termination.
7. The UMG returns a MOD REPLY message to the MSC.
8. The MSC sends a RAB ASSIGN MODIFY message to RNC B to request RNC B to
9. RNC B returns a RAB ASSIGN MODIFY RSP message to the MSC.

Issue 01 (2009-04-06) 77
MSOFTX3000
10. The MSC sends a MOD REQ to the UMG to request the UMG to modify the attributes
of the calling termination.
11. The UMG returns a MOD REPLY message to the MSC.
12. The MSC sends a RAB ASSIGN MODIFY message to RNC A to request RNC A to
13. RNC A returns a RAB ASSIGN MODIFY RSP message to the MSC. The call becomes
stable, and the video call changes to a voice call.

None.
Constraints
None.

78 Issue 01 (2009-04-06)
MSOFTX3000
Single BC Video Fallback (Requiring the Support of the UE)
z The single BC fallback mode requires support of the UE. Upon receiving a call release message
containing the cause value #58, #47, #57, or #88 from the network, the calling UE offers a
subscriber two operation options through the man-machine interface: a) initiate another voice call; b)
abandon the call. The caller can choose an operation according to the message that is displayed
through the man-machine interface or allow the UE to automatically initiate another voice call. If the
caller chooses option a), the UE initiates another voice call using the last dialed video call number. If
the subscriber has subscribed to the automatic fallback service, the calling UE automatically initiate
a voice call without displaying the message for the subscriber.
z At present, China Mobile and China Unicom adopt this single BC fallback mode.
Figure 1-24 Single BC video fallback (requiring the support of the UE)
The procedure of the single BC video fallback (requiring the support of the UE) is as follows:
1. The fallback mode of the UE is configured to automatic fallback.
2. The UE sends a SETUP message containing the BCm and Called num to the MSC.
3. The MSC releases the video call and sends an RLEASE message containing the cause
value #58, #47, #57, or #88 to the UE.
4. Based on the cause value #58, #47, #57, or #88, the UE initiates another voice all
addressed to the same called UE.
5. The voice call continues to be connected.
Explanation of cause values:
#47“Resources unavailable, unspecified”

Issue 01 (2009-04-06) 79
MSOFTX3000
#57“Bearer capability not authorized”

#58“Bearer capability not presently available”
#88“Incompatible destination”

None.
Constraints
None.
Interaction Between the 3G Video Fallback and the IN Service

When a video call falls back, the current call is released and the caller chooses whether to
initiate a new voice call, based on the mobile specifications.
When the video call falls back and the current call is released, the MSC reports the four cause
values #47, #57, #58, and #88.For the SCP, the original video call is released and another new
voice call is established. The SCP cannot modify the four cause values #47, #57, #58, and #88
reported from the MSC, and the MSC delivers the RC based on these four cause values.

None.
Constraints
None.
1.3.12 3G Video Call Failure

Callee Served by a Network That Does Not Support the 3G Video Call Service
Upon receiving a video call addressed to a PSTN or PLMN subscriber, the originating MSC
performs the following judgments:
z Whether the callee is a subscriber of another network
z Whether the network supports the video call service if the callee is the subscriber of
another network
If the originating MSC finds that the callee is served by a network that does not support the
video call service, the MSC releases the video call. The cause value included in the
RELEASE message is "Bearer capability not presently available".

80 Issue 01 (2009-04-06)
MSOFTX3000
In this case, the value of the measurement entity VP Call Failures due to Bearer capability not
presently available (available in the measurement unit UTRAN VP Subscriber Originated
Calls) increases by one.
Figure 1-25 3G video call failed because the network serving the callee does not support the 3G
video call service
The message flow is as follows:

1. The MSC receives a SETUP message carrying the BCm from a 3G video call subscriber.
2. The MSC analyzes the called number and determines that the callee is a subscriber
served by a network that does not support the 3G video call service.
3. The MSC sends a RELEASE message to the caller. The cause value included in the
RELEASE message is "Bearer capability not presently available".

The scenario, where the callee is served by a network that does not support the video call
service, needs to be created. For details, see the description of ADD INTWORKCTRL.
Constraints
None.
Callee Not Subscribing to the Video Call Service

Upon receiving a video call request, the 3G network notifies the caller to release the call if it
detects that the callee does not subscribe to the video call service in the CS domain. The cause
value included in the RELEASE message is "Bearer capability not presently available".

Issue 01 (2009-04-06) 81
MSOFTX3000
This scenario occurs only when the multimedia fallback service is not triggered. In this case,
the value of the measurement entity VP Call Failures due to Bearer capability not presently
available (available in the measurement unit UTRAN VP Subscriber Originated Calls)
increases by one.
Figure 1-26 3G video call failed because the callee does not subscribe to the 3G video call service

2. The MSC sends an SRI request carrying the BCm to the terminating HLR.
3. The terminating HLR checks the service profile of the callee. If the callee does not
subscribe to the video call service, the HLR sends an SRI Rsp message to the MSC. The
cause value included in the SRI Rsp is "Bearer Service Not Provisioned".
4. Upon receiving the SRI Rsp from the HLR, the originating MSC sends a RELEASE
message to the calling UE. The cause value included in the RELEASE message is
"Bearer capability not presently available".

The scenario, where the subscriber does not subscribe to the video call service, needs to be
created by deregistering the BS30 service on the HLR. For details, see the description of
MOD BS30.
Constraints
None.

82 Issue 01 (2009-04-06)
MSOFTX3000
Callee Subscribing to the Video Call Service But Located in a 2G Access

Network
Upon receiving a video call request, the 3G network notifies the caller to release the call if it
detects that the callee has subscribed to the video call service but is located in a 2G access
network. The cause value included in the RELEASE message is "Bearer capability not
presently available". This scenario is classified into two sub-scenarios:
z Sub-scenario a: Based on the called MSC ID, the terminating HLR determines that the
callee is located in a 2G network and thus denies the establishment of the video call.
z Sub-scenario b: When the 2G network and the 3G network share an LAI, the terminating
HLR fails to detect the exact location of the callee. In this case, the terminating MSC
rejects the video call from the 2G access network.
These two sub-scenarios occur only when the multimedia fallback service is not triggered. In
Sub-scenario a, the value of the measurement entity VP Call Failures due to Bearer capability
not presently available (available in the measurement unit UTRAN VP Subscriber Originated
Calls) increases by one. In Sub-scenario b, the value of the measurement entity VP Call
Failures due to Bearer capability not presently available (available in the measurement unit
UTRAN VP Subscriber Originated Calls) and the value of the measurement entity VP Call
Failures due to Bearer capability not presently available (available in the measurement unit
UTRAN VP Subscriber Terminated Calls) increase by one.
Figure 1-27 3G video call failed because the callee is located in a 2G access network
(sub-scenario a)

Issue 01 (2009-04-06) 83
MSOFTX3000
Figure 1-28 3G video call failed because the callee is located in a 2G access network
(sub-scenario b)
The message flow of sub-scenario a is as follows:

1. The MSC receives a SETUP message carrying the BCm from a 3G video call
subscriber.
2. The MSC sends an SRI request carrying the BCm to the terminating HLR.
3. Based on the called MSC ID, the terminating HLR determines that the callee is located
in a 2G network. Then, the HLR sends an SRI Rsp message to the MSC. The cause value
included in the SRI Rsp message is "Bearer Service Not Provisioned".
4. Upon receiving the SRI Rsp from the terminating HLR, the originating MSC sends a
RELEASE message to the calling UE. The cause value included in the RELEASE
message is "Bearer capability not presently available".
The message flow of sub-scenario b is as follows:
When the originating MSC queries the terminating HLR for routing information, the
terminating HLR cannot identify whether the callee is located in a 2G network because
the 2G network and the 3G network share an LAI. Therefore, the originating MSC
successfully obtains the routing information, and the terminating MSC sends the SETUP
message to the callee.
2. Upon receiving a Call Confirmed message from the callee, the terminating MSC
determines that the message includes the BCm and the callee is located in the 2G access
network.
3. The terminating MSC sends a RELEASE message to the caller and the callee
respectively. The cause value included in the RELEASE message is "Bearer capability
not presently available".


84 Issue 01 (2009-04-06)
MSOFTX3000
For details about how to configure the 2G network and the 3G network to share an LAI, see
ADD SHARELAI.
Constraints
None.
Callee Subscribing to the Video Call Service But the Video Call Service not
Supported by Called UE
During a video call, if the callee has subscribed to the video call service but the called UE
does not support the video call service, the called UE then releases the call. The cause value
included in the RELEASE message sent from the called UE to the terminating MSC is
"Incompatible Destination". Upon receiving the RELEASE message, the terminating MSC
instructs the originating MSC to release the call.
the value of the measurement entity VP Call Failures due to Incompatible destination
(available in the measurement unit UTRAN VP Subscriber Terminated Calls) and the value of
the measurement entity VP Call Failures due to Incompatible destination (available in the
measurement unit UTRAN VP Subscriber Originated Calls) increase by one separately.
Figure 1-29 3G video call failed because the called UE does not support the video call service

2. The originating MSC sends a Call_Proceeding message to the calling UE.
3. The originating MSC sends an SRI request carrying the BCm to the terminating HLR.

Issue 01 (2009-04-06) 85
MSOFTX3000
4. The terminating HLR checks the service profile of the callee. If the callee has subscribed
to the video call service, the terminating HLR sends a PRN message carrying the BCm to
the MSC.
5. The terminating MSC checks the bearer parameter included in the PRN message. If the
network supports the multimedia service, the terminating MSC sends a PRN Rsp
message to the HLR, carrying the roaming number of the callee.
6. The terminating HLR sends an SRI Rsp message to the originating MSC, carrying the
roaming number of the callee.
7. On receiving the roaming number of the callee, the originating MSC sends an IAM
message to the terminating MSC. In the IAM message, the parameter TMR is set to 64
kbit/s preferred, indicating that the multimedia bearer service is preferred.
8. The terminating MSC sends a SETUP message to the called UE.
9. The called UE does not support the video call, and thus sends a RELEASE message to
the terminating MSC. The cause value included in the RELEASE message is
"Incompatible Destination".
10. The terminating MSC sends a REL message to the originating MSC. The cause value
included in the REL message is "Incompatible Destination".
11. The originating MSC sends a RELEASE message to the calling UE. The cause value
included in the REL message is "Incompatible Destination".

None.
Constraints
None.
Radio Coverage Area Where the Callee Is Located Not Supporting the Video Call
Service
In a video call, the callee in a 3G network has subscribed to the video call service and the
called UE supports the video call service, but the corresponding radio coverage area does not
support the video call service. In this scenario, the RNC in the 3G network serving the callee
then sends a RAB Assignment Response message to the terminating MSC. Upon receiving the
message, the terminating MSC instructs the calling UE and the called UE to release the call.
the value of the measurement entity VP Call Failures due to Resources unavailable (available
in the measurement unit UTRAN VP Subscriber Originated Calls) and the value of the
measurement entity VP Call Failures due to Resources unavailable (available in the
measurement unit UTRAN VP Subscriber Terminated Calls) increase by one separately.

86 Issue 01 (2009-04-06)
MSOFTX3000
Figure 1-30 3G video call failed because the radio coverage area where the callee is located does
not support the video call service

3. The originating MSC sends an SRI request carrying BCm to the terminating HLR.
the terminating MSC.
5. The terminating MSC checks the BCm included in the PRN message. If the network
supports the multimedia service, the terminating MSC sends a PRN Rsp message to the
HLR, carrying the roaming number of the callee.
7. Upon receiving the roaming number of the callee, the originating MSC sends an IAM
message carrying the BCm to the terminating MSC.
8. The terminating MSC sends a SETUP message carrying the BCm to the called UE.
9. The terminating MSC sends a RAB Assignment Req message to the RNC.
10. If the video call fails for the radio reason (for example, the radio resources are
insufficient) of the callee's location, the RNC directly sends a RAB Assignment Rsp
message to the MSC without implementing the RAB assignment. The cause value
included in the RAB Assignment Rsp message is "Release Due To UTRAN Generated
Reason."
11. The terminating MSC sends a RELEASE message to the originating MSC. The cause
value included in the RELEASE message is "Resources unavailable, unspecified".
12. The originating MSC sends a RELEASE message to the calling UE. The cause value
included in the RELEASE message is "Resources unavailable, unspecified".

Issue 01 (2009-04-06) 87
MSOFTX3000

None.
Constraints
None.
Callee Answered the Video Call As a Voice Call

In a video call, the callee in a 3G network has subscribed to the video call service and the
called UE supports the video call service, but the callee chooses to answer the call as a voice
call (for certain reasons such as payment). In this scenario, the called UE sends a RELEASE
message to the network. The cause value included in the RELEASE message is "Incompatible
destination".
the value of the measurement entity VP Call Failures due to Incompatible destination
(available in the measurement unit UTRAN VP Subscriber Terminated Calls) and the value of
the measurement entity VP Call Failures due to Incompatible destination (available in the
measurement unit UTRAN VP Subscriber Originated Calls) increase by one separately.
Figure 1-31 3G video call failed because the callee answers the video call as a voice call

88 Issue 01 (2009-04-06)
MSOFTX3000

3. The originating MSC sends an SRI request carrying BCm to the terminating HLR.
the terminating MSC.
5. The terminating MSC checks the BCm included in the PRN message. If the network
supports the multimedia service, the terminating MSC sends a PRN Rsp message to the
HLR, carrying the roaming number of the callee.
7. Upon receiving the roaming number of the callee, the originating MSC sends an IAM
message carrying the BCm to the terminating MSC.
8. If pre-paging is not initiated, the terminating MSC sends a PAGING request to the
callee.
9. The called UE returns a PAGING ACK message to the terminating MSC.
10. The terminating MSC sends a SETUP message carrying the BCm to the called UE.
11. The called UE returns a CALL CONFIRMED message. If the message does not carry a
new Bearer Capability information element, it indicates that the called UE supports the
video call.
12. The called UE is alerted, and the called UE sends an ALERTING message to the
terminating MSC.
13. The terminating MSC sends an ACM message to the originating MSC.
14. The originating MSC sends an ALERTING message to the calling UE.
15. If the callee chooses to answer the video call as a voice call, the called UE sends a
RELEASE message to the network. The cause value included in the RELEASE message
is "Incompatible destination".
16. Upon receiving the RELEASE message from the called UE, the terminating MSC sends
a RELEASE message to the originating MSC.
17. The originating MSC sends a RELEASE message to the calling UE.

None.
Constraints
None.

Issue 01 (2009-04-06) 89
MSOFTX3000
Caller Who Has Subscribed to the Video Call Service Located in a 2G Access
Network
Upon receiving a video call, if the MSC determines that the caller is located in a 2G network,
it releases the call directly. The cause value included in the RELEASE message is "Resources
unavailable, unspecified".
in the measurement unit UTRAN VP Subscriber Originated Calls) increases by one.
Figure 1-32 3G video call failed because the caller who has subscribed to the video call service is
located in a 2G access network

2. The originating MSC determines that the caller is located in a 2G access network and
returns a RELEASE message to the calling UE. The cause value included in the
RELEASE message is "Resources unavailable, unspecified".

None.
Constraints
None.

90 Issue 01 (2009-04-06)
MSOFTX3000
Resources in the 3G Radio Coverage Area Where the Caller Is Located Are
Insufficient
During a video call, if the caller in a 3G network has subscribed to the video call service but
the radio coverage area where the caller is located does not support the video call service, the
originating RNC then returns a RAB Assignment Rsp message that includes the cause value
"Release Due To UTRAN Generated Reason" to the originating MSC. Upon receiving the
message, the originating MSC releases the call. The cause value included in the RELEASE
message is "Resources unavailable, unspecified".
in the measurement unit UTRAN VP Subscriber Originated Calls) and the value of the
measurement entity VP Call Failures due to Resources unavailable (available in the
measurement unit UTRAN VP Subscriber Terminated Calls) increase by one.
Figure 1-33 3G video call failed because the resources in the 3G radio coverage area where the
caller is located are insufficient

3. The originating MSC sends a RAB Assignment Req message to the RNC.
4. If the video call fails for the radio environment or radio resources reason of the caller's
location, the RNC directly sends a RAB Assignment Rsp message to the MSC without
implementing the RAB assignment. The cause value included in the RAB Assignment
Rsp message is "Release Due To UTRAN Generated Reason."

Issue 01 (2009-04-06) 91
MSOFTX3000
5. Upon receiving the RAB Assignment Rsp message, the originating MSC sends a
RELEASE message to the calling UE. The cause value included in the RELEASE
message is "Resources unavailable, unspecified".

None.
Constraints
None.
Caller Not Subscribing to the Video Call Service

Upon receiving a call from a subscriber who does not subscribe to the video call service, the
originating MSC directly releases the call. The cause value included in the RELEASE
message is "Bearer capability not authorized".
the value of the measurement entity VP Call Failures due to No Support from Bearer
Capability (available in the measurement unit UTRAN VP Subscriber Originated Calls)
increases by one.
Figure 1-34 3G video call failed because the caller does not subscribe to the video call service

2. The MSC checks the service profile of the caller and determines that the caller does not
subscribe to the video call service. Then, the MSC returns a RELEASE message to the

92 Issue 01 (2009-04-06)
MSOFTX3000
calling UE. The cause value included in the RELEASE message is "Bearer capability not
authorized".

None.
Constraints
None.
Operation and Maintenance Scenario

Generally, the feature of the performance measurement upon video call failures is applied in
the following scenarios for operation and maintenance (O&M):
z Delivery and installation (network design)
z Commissioning configuration (deployment)
z Upgrade
z Routing maintenance (preventive maintenance) and troubleshooting
z Others
Delivery and Installation (Network Design)

None.
Commissioning Configuration (Deployment)

z Background and objective
For a new 3G network that provides the video call service, you can observe the operation
of the video call service through the performance measurement entities added for the
feature of the performance measurement upon call failures.
z Application scenario
The new 3G network requires the registration of the video call service and
commissioning of the video call service.
z Preset conditions
To implement the performance measurement upon call failures, you must first register
the video call service.
z Major operations
Create performance measurement tasks with the measurement units UTRAN VP
Subscriber Originated Calls and UTRAN VP Subscriber Terminated Calls. These two
measurement units include the measurement entities of VP Call Failures due to No
Support from Bearer Capability, VP Call Failures due to Resources unavailable, VP Call
Failures due to Bearer capability not presently available, and VP Call Failures due to
Incompatible destination.
z Subsequent processing

Issue 01 (2009-04-06) 93
MSOFTX3000
Analyze the causes of the video call failures based on the performance measurement
results.
If the callee does not subscribe to the video call service, the callee is located in a 2G
network, or the peer office does not support the video call service, the failure cause may
be "VP Call Failures due to Bearer capability not presently available".
If the caller is located in a 2G network and the corresponding radio resources are
insufficient, the failure cause may be "VP Call Failures due to Resources unavailable".
If the caller does not subscribe to the video call service, the failure cause may be "VP
Call Failures due to No Support from Bearer Capability".
If the called UE does not support the video call service, or the callee chooses to answer
the call as a voice call, the failure cause may be "VP Call Failures due to Incompatible
destination".
z Possible fault:
After a license file is loaded, run DSP LICENSE to check whether H324M Function is
set to 0. If yes, it indicates that the license is invalid or unavailable. In this case, contact
related personnel to modify the license file or apply for a new license file.
Upgrade
None.
Routing Maintenance (Preventive Maintenance) and Troubleshooting

See the descriptions of the deployment.
Others
None.
1.4 Table Query for 3G Video

Figure 1-35 shows the general table query flow of the 3G video call.

94 Issue 01 (2009-04-06)
MSOFTX3000
Figure 1-35 General table query flow of the 3G video call
Determine that the

call is a video call.
Query the GSM service

configuration table for data records of No
the BS30 UDI service.
Yes
Connect the video

Reject the call.
call.
Table Involved in the 3G Video Feature

Table Function MML Command
GSM service This command is used to add a GSM service ADD GSMSRV
configuration configuration data record to the configuration
table database.
1.5 Charging and CDR

The CDR generation principles of the 3G video calls are similar to those of basic calls. They
are different only in the CDR contents. As a data bearer service, the CDRs of the 3G video
call differ from others in service codes and the following aspects:
z 1. rate Indication: It is valid and the code is H.223 & H.245.
z 2. basicService: It is set to bearerService and the bearer service code is 0x1F.
z 3. Generally, Fnur is valid in the CDR of video calls. Generally, the 3G video call rate is
64 Kbit/s.
Key Field Value Remarks
Basic service: 0x1F Video call service code

RateIndication H.223 & H.245 Indicator of the video call rate adaptation

Issue 01 (2009-04-06) 95
MSOFTX3000
Key Field Value Remarks
Fix Network User Rate 64k Fixed network user rate
For detailed CDR generation principles and CDR formats, see the 3G Charging.
According to GSM 02.04 , the BS30 service is defined as a general synchronization bearer service;
according to 3GPP 22.004, the 3G video call service is a type of the BS30 service. The service code of
the general synchronization bearer service is defined to 00011111(1f) in 3GPP 29002, and therefore, the
value of the mapping service code is If.
1.6 Performance Measurement

Related Measurement Units
Table 1-4 Key measurement units related to the 3G video service
Measurement Unit Description
UTRAN VP Subscriber Originated This measurement unit is aimed at measuring video

Calls call traffic originated by 3G subscribers. It includes
the following measurement entities: VP Call
Attempts, VP Call Completion Times, VP Call
Answer Times, VP Call Failures due to No Support
from Bearer Capability, VP Call Seizure Traffic, VP
Call Completion Traffic, VP Call Answer Traffic,
VP Call Completion Rate, VP Call Answer Rate, VP
Call Wrong Dialing Num Times, VP Call Released
Before Ringing, VP Call Released After Ringing, VP
Call Ringed No Answer, VP Call Callee Busy, VP
Call Barring, VP Call Callee Not Reachable, VP Call
Callee Absent, VP Call Network Error, and VP Call
Temporary Error, VP Call Failures due to Resources
unavailable, VP Call Failures due to Bearer
capability not presently available, and VP Call
Failures due to Incompatible destination.

96 Issue 01 (2009-04-06)
MSOFTX3000
UTRAN VP Subscriber This measurement unit is aimed at collecting

Terminated Calls statistics about video calls to local 3G subscribers. It
includes the following measurement entities: VP Call
Attempts, VP Call Completion Times, VP Call
Answer Times, VP Call Failures due to No Support
from Bearer Capability, VP Call Seizure Traffic, VP
Call Completion Traffic, VP Call Answer Traffic,
VP Call Completion Rate, VP Call Answer Rate, VP
Call Released Before Ringing, VP Call Ringed No
Answer, VP Call Callee Determined busy, VP Call
Released Before Ringing, VP Call Network Error,
and VP Call Temporary Error, VP Call Failures due
to Resources unavailable, VP Call Failures due to
Bearer capability not presently available, and VP
Call Failures due to Incompatible destination.
VP Incoming Traffic in Mobile This measurement unit is aimed at obtaining
Office Directions information about the traffic of video phone (VP)
calls and running states of circuits carrying the video
calls in the RNC office direction. It includes the
following measurement entities: Seizure Times, Call
Completion Times, Answer Times, Call Completion
Rate, Seizure Traffic, Call Completion Traffic,
Answer Traffic, Callee Determined Busy Times,
Releases After Ringing, No Answer After Ringing,
3G to 2G Handover Rejected Times, Call Dropped
Times at the RAN Side, Call Drop Rate at the RAN
Side, Wrong Dialing Times, Call Barring, Release
Before Ringing, Callee Not Reachable, Network
Error, Temporary Error, User initiate service change
from VP to voice times, User initiate service change
from VP to voice success times, User initiate service
change from voice to VP times, User initiate service
change from voice to VP success times, Network
initiate service change from VP to voice times,
Network initiate service change from VP to voice
success times, Network initiate service change from
voice to VP times, Network initiate service change
from voice to VP success times and VP Call fallback
times.

Issue 01 (2009-04-06) 97
MSOFTX3000
VP Outgoing Traffic in Mobile This measurement unit is aimed at obtaining

Office Directions information about the traffic of video phone (VP)
calls and running states of circuits carrying the video
calls in the RNC office direction. It includes the
following measurement entities: Seizure Attempts,
Seizure Times, Call Completion Times, Answer
Times, Call Completion Rate, Answer Rate, Seizure
Traffic, Call Completion Traffic, Answer Traffic,
Callee Determined Busy Times, Releases After
Ringing, No Answer After Ringing, 3G to 2G
Handover Rejected Times, Call Dropped Times at
the RAN Side, Call Drop Rate at the RAN Side,
Release Before Ringing, Network Error, Temporary
Error, User initiate service change from VP to voice
times, User initiate service change from VP to voice
success times, User initiate service change from
voice to VP times, User initiate service change from
voice to VP success times, Network initiate service
change from VP to voice times, Network initiate
service change from VP to voice success times,
Network initiate service change from voice to VP
times, Network initiate service change from voice to
VP success times and VP Call fallback times.
KPI Specifications
For details about the KPI specifications, see the Maintenance Manual.
1.7 Operation and Maintenance

1.7.1 Related MML Commands
The key MML commands related to the video call service are listed as follows:
z ADD GSMSR: It is used to configure the MSC to support the BS30 service.
z ADD VPCFN: It is used to configure the MSC to support the USSD notification feature
upon a video call failure.
1.7.2 Related Alarms

None.

98 Issue 01 (2009-04-06)
MSOFTX3000
1.8 Reference
1.8.1 Acronyms and Abbreviations
Acronyms/Abbreviations Full Name
3GPP The 3rd Generation Partnership Project

3G-324M The 3rd Generation-324Mobile
AAA Authorization, Authentication, and Accounting
ACM Address Complete Message
ANM Answer Message
BC Bearer Capability
BC1 First Bearer Capability in a message (preferred service)
BC2 Second Bearer Capability in a message (less preferred
service)
BCa Bearer Capability of the currently selected service
BCb Bearer Capability of the service to switch to
BCm Bearer Capability multimedia
BCsp Bearer Capability speech
BC_IE Bearer Capacity Identity Element
CFU Call Forwarding Unconditional
CFNRc Call Forwarding on mobile subscriber Not Reachable
CFNRy Call Forwarding on mobile subscriber No Reply
CFB Call Forwarding on mobile subscriber Busy
GK GateKeeper
IAM Initial Address Message
ISDN Integrated Services Digital Network
ISUP Integrated Services Digital Network (ISDN) User Part
(ISUP)
ITC Information Transform Capability
MCU Mutilpoint Control Unit
MG Media Gateway
MGC Gateway Control
MMI Man-Machine Interface
MSC Mobile Switching Centre

Issue 01 (2009-04-06) 99
MSOFTX3000
Acronyms/Abbreviations Full Name
MSRN Mobile Station Roaming Number

NDB Network Determined Busy
O-MSC Originating MSC
ORA Other Rate Adaptation
O-UE Originating UE
PRI Primary Rate Interface
Radius Remote Authentication Dial In User Service
RI Repeat Indicator
SCUDIF Service Change and UDI/RDI Fallback
SRI Send Routing Info
SS SoftSwitch
TMR Transmission Medium Requirement
T-MSC Terminating MSC
TMU Transmission Medium Used
T-UE Terminating UE
TD-SCDMA Time Division-Synchronous Code Division Multiple
Access
UDB User Determined Busy
UDI Unrestricted Digital Information
VIG Video Interactive Gateway
VMSC Visited Mobile Services switching Centre

100 Issue 01 (2009-04-06)

3G Video Call Data Rates

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

3G Video Call Data Rates

Transféré par

Droits d'auteur :

Formats disponibles

3G Video

Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

About This Document

Huawei Proprietary and Confidential

V1.00 Initial release Liu Shiyue

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1.7.1 Related MML Commands..................................................................................................................... 98

Huawei Proprietary and Confidential

Figure 1-4 Procedure of an inter-ISUP-MSC video call between 3G subscribers............................................... 23

Figure 1-16 VP IN service triggered for the callee.............................................................................................. 66

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Table 1-1 H.324M protocol frame ......................................................................................................................... 3

Table 1-4 Key measurement units related to the 3G video service...................................................................... 96

Huawei Proprietary and Confidential

1.1 Feature Description

3G video call This feature provides an end-to-end synchronous video and

Huawei Proprietary and Confidential

1.1.3 Application Scenario

1.1.4 External Interfaces

Huawei Proprietary and Confidential

Table 1-1 H.324M protocol frame

Video protocol H.261

Networking for video calls in fixed and mobile networks

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1.1.5 Compliance Standards

TS 24.008 Mobile radio interface Layer 3 3GPP

1.1.6 Constraints and Limitations

Impact on the System

Huawei Proprietary and Confidential

1.1.8 Release History

Initial release 2009-4-20 V200R008C02 -

Table 1-2 NEs involved in the 3G video feature

The symbol "√" indicates that the NE is required.

1.2.2 Functions of the NEs

Huawei Proprietary and Confidential

1.2.3 Requirements for License

1.2.4 Hardware Compatibility

1.2.5 Supporting Versions

MSC MSOFTX3000 V200R008C02

1.3 Service Flow

1.3.1 Scenario Description

Huawei Proprietary and Confidential

− Inter-MSC BICC video call

1.3.2 H.245 Negotiation

Huawei Proprietary and Confidential

Figure 1-2 H.245 negotiation flow

Huawei Proprietary and Confidential

(OpenLogicalChannel/Ack/Reject/Release), close logical channel

Key Message and Information Element

1.3.3 Intra-MSC 3G Video Calls

Huawei Proprietary and Confidential

Figure 1-3 Intra-MSC 3G video call flow

The procedure of an intra-MSC 3G video call is as follows:

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Key Message and Information Element

z UE A sends a SETUP message to the MSC ( ). Among the information elements of