Documente Academic
Documente Profesional
Documente Cultură
Issue 01
Date 2010-02-15
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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.
Contents
1 Feature Definition......................................................................................................................1-1
1.1 Definition........................................................................................................................................................1-2
4 Feature Configurations.............................................................................................................4-1
4.1 Configurations on the USDP...........................................................................................................................4-2
4.2 Configurations on the RBT Portal...................................................................................................................4-2
5 Commissioning...........................................................................................................................5-1
6 FAQ...............................................................................................................................................6-1
Figures
Tables
1 Feature Definition
1.1 Definition
An advertisement RBT is an RBT whose content is an advertisement. Advertisement RBT
feature will be used by different companies to promote their advertisements.
1.1 Definition
An advertisement RBT is an RBT whose content is an advertisement. Advertisement RBT
feature will be used by different companies to promote their advertisements.
The advertisement RBT system is set up based on the existing ring back tone (RBT) platform
and wise advertisement (WAD) platform. The advertisement RBT service is implementation
based on the Corp. RBT service. A special Corp. is created on the universal service development
platform (USDP) and this account is used to manage the advertisement RBT service.
NOTE
This feature is supported in RBT from RBTV600R001C01B033CP0003 and USDP from
USDPV100R002C01B044CP0053.
Prerequisite Implementati
Feature Use Role on Way
Create an AD Corp:
A new configuration is added for the AD Corp’s corp code. A corp whose corpcode is set to
sys_ad_sys is created and the information about the corp is preset. Create the new corp admin.
The corp admin should be able to invoke the adminDelTone function without any approval and
admin can modify or delete tone without approval. USDP should synchronize corpid and
corpcode fields to Call node.
Privileges of an AD Corp:
The privileges of an AD corp as follows:
l Allows the maximum member and maximum ring are set to 9999999999 and the maximum
depart number is set to -1 (means do not restrict), for the AD corp.
l Restrict the setting times for the corp.
l Restrict the group number and group member number restrict of the AD corp.
l Allow the corp admin to invoke the adminDelTone function.
The following figure shows corp create an advertising department or advertisement RBT
Channels
Procedure
Step 1 The Portal invoke the CorpManage.addCorpDept() SOAP Interface to create an advertisement
RBT channel.
l CorpManage.editCorpDept() SOAP Interface to edit an advertisement RBT channel.
l CorpManage. queryCorpDep() SOAP Interface to query an advertisement RBT channel.
l CorpManage.delCorpDept() SOAP Interface to delete an advertisement RBT channel.
NOTE
Along with the department information, the Corp. administrator can upload an IVR prompt file. This file is
stored in the path configured in path_file_root\ivr_ad_prompt_file_path\path_work_cue_tone\deptid. The files
can be uploaded for multiple languages and are stored in the folder, deptid.
----End
The following figure shows corp set RBTs to advertisement RBT Channels
4. The system prompts a success or failure message after set RBTs to advertisement RBT
channels.
Context
Support advertisement RBT feature in Web portal, WAP and SMS to browse advertisement RBT
is depends on the configurations, support_advertisement_rbt Only if this flag is enabled, AD
RBT link will be visible.
For SMS commands flow browsead and browsemyad refer RBT Ring Back Tone Service Short
Message Reference Guide SM commands are updated in RBT table,T_SMCOMMANDS and
SM operations are updated in RBT table, T_SMOPERATIONS.
l For browsemyad: An AD RBT user wants to browse different advertising channels to
which he is already subscribed refer browse an my advertisement RBT channels.
The number of entries to be returned in the query must be controlled by configuration,
sm_query_tone_max_num
The following figure shows browse an advertisement RBT Channels. Where browse an
advertisement RBT channels can be view by Ad RBT user and non Ad RBT user.
1. The Portal invoke the query SOAP Interface to check where user is advertisement RBT
user.
The procedure for to query all the departments in the special corp admin as follows:
Procedure
Step 1 The Portal invoke the CorpManage.queryCorpDept() SOAP Interface to query all the
departments in the special corp admin.
l UserToneManage.querySetting() SOAP Interface to query all settings in a department.
l UserToneManage.queryTbTone() SOAP Interface to query songs in a setting.
----End
Context
Whether the RBT user can use the advertisement RBT feature through Web Portal, WAP and
SM, is decided by the configurations in RBT portal as follows:
l support_advertisement_rbt can decide whether support the advertisement RBT in Web
portal, WAP and SMS.
l support_nonrbt_adrbt_subscription can decide whether support the advertisement RBT
for Non RBT user.
NOTE
l Whenever a user becomes a special corp user at the subscribing time, no SMS will be send to him.
l Subscription of a non RBT user to AD RBT is supported only in real time mode. If you configure this in
non real time, RBT will just accept the subscription request to subscribe to personal RBT service. User will
not be subscribed to AD RBT. He will have to subscribe to AD RBT, again after subscription to personal
RBT service is successful.
Procedure
Step 1 The Portal invoke the UserManage.subscribe() SOAP Interface to subscribing to the RBT
service.
Step 2 The details is updated in the USDP tables, t_userinfo and t_userserviceinfo.
----End
Context
Whether the RBT user can use the advertisement RBT feature through Web Portal, WAP is
decided by the configurations in RBT portal support_advertisement_rbt.
An advertisement RBT subscriber wants to modify advertisement RBT channel to which he is
subscribed.
Modify has 2 WAD calls. First it calls WAD to query the user subscribed AD channel. Then
after user makes a new selection, it calls the WAD again.
The following figure shows modify an advertisement RBT channel.
Procedure
Step 1 The Portal invoke the UserManage.query() SOAP Interface to check where user is
advertisement RBT user.
Step 2 The RBT calls HTTP interface WAD API http[https]://WAD URL/rbtorderquery.do of
WAD external system to query the advertisement RBT channels which are subscribed by the
advertisement RBT user.
Step 3 The RBT calls HTTP interface WAD API http[https]://WAD URL/rbtorder.do of WAD
external system to unsubscribing to the advertisement RBT service.
Step 4 RBT user modify the channel information.
Step 5 The WAD system modify from advertising channels for that user.
Step 6 WAD sends this result to the web portal.
Step 7 The system prompts a success or failure message after modifying an advertisement RBT channel.
----End
l When a subscriber becomes the advertisement RBT subscriber, the personal RBT also remains but the
subscriber can choose whether to cancel Personal RBT or not based on the RBT configuration,
user_destroy_config. The Personal RBT remains even after the Ad RBT is unsubscribed for the user.
l whenever a user becomes a special corp user at the Unsubscribing time, no SMS will be send to him.
l Unsubscription is optional, after unsubscribe from advertisement RBT, user can unsubscribe or can remain
as Normal RBT user.
For SMS commands flow cancelad and cancelad all refer RBT Ring Back Tone Service Short
Message Reference Guide SM commands are updated in RBT table, T_SMCOMMANDS and
SM operations are updated in RBT table, T_SMOPERATIONS.
Procedure
Step 1 The RBT calls HTTP interface WAD API http[https]://WAD URL/rbtorder.do of WAD
external system to unsubscribing to the advertisement RBT service.
Step 2 The WAD system unsubscribe from advertising channels for that user
Step 3 WAD sends this result to the web portal.
Step 4 The Portal invoke the CorpUserManage.delCorpUser() SOAP Interface to unsubscribing to
the corp RBT service.
Step 5 The details is updated in the USDP table, t_corpuserinfo.
Step 6 WAD sends this result to the web portal.
Step 7 The system prompts a success or failure message after unsubscribing an advertisement RBT
service.
Step 8 USDP sends this result to the web portal.
Step 9 The system prompts a success or failure message after unsubscribing an RBT service.
----End
4 Feature Configurations
Context
When USDP portal is upgraded to USDP V100R002C01B044CP0051 patch, then system is
updating the adcorp_special_corpcode configuration in t_config table in USDP database.
path_ivr_adch_tone: Indicates the directory for storing the IVR advertisement channel
announcements.
NOTE
The directory for storing IVR advertisement channel announcements is a relative path to the root directory
that stores all the RBT files (path_file_root). This configuration is not available for modification through
EAS.
Procedure
Step 1 Run the HUAWEI EAS Operation & Maintenance System.
Step 3 Choose $RBT_EAS_HOME > RBT portal Configurations > Service Feature
Configuration > Advanced Configurations > Advertising RBTs
[ADVETISEMENT_RBT] .
Configure the following parameters, for detail description please refer the description in EAS.
Parameter Usage
Parameter Usage
----End
5 Commissioning
Make sure you have finished configuring the system function service, then you can start
commissioning the feature, here we only provide how to commission the subscribing advertising
RBT channels as an example. For other features as create, set, browse, modify and unsubscribe
advertising RBT channels, please refer to related section in implementation by the whole RBT
system.
Scenario
Subscribing advertising RBT channels: Suppose RBT user wants to subscribe the advertising
RBT channels.
l The RBT portal support the RBT presentation feature.
l A special Corp has to create the advertising RBT Channels
l The status of RBT user is normal.
NOTE
Non RBT users has to subscribe RBT service first then proceed for subscribing advertising RBT channels.
Procedure
Step 1 RBT user login to the web portal.
Step 2 Click AD RBT in the menu area.
Step 3 Click Subscribe AD RBT in the navigation area.
Step 4 Enter your phone number in the text box.
Step 5 Click confirm. Then Obtain verification window is displayed.
Step 6 Enter the Verification code. Click get verification code, then the verification code will be send
to your handset.
Step 7 Click Register. Then AD Channel window is displayed.
Step 8 Select any or all check box of AD Channel, which you want to be subscribed.
Step 9 Click Register to subscribe the AD RBT service. The system will prompt a success or failure
message.
NOTE
If you have not selected a presentation date, the RBT is immediately presented to the presentee.
If the system displays a success message , you need to confirm an subscribing to the corp RBT
service has been written into USDP table, t_corpuserinfo is updated.
If the system displays a failure message, you need to handle according the failure message, the
failure message are provided by USDP soap interface, you can get the return code from $USDP
\usdplogs\worklog\common\common.log
The following failures are just for example:
The system is busy. You can try accessing the system later.
The database operation is abnormal. Check whether the USDP DB works properly
and the connection between the USDP and
USDP DB is normal. If it is abnormal, check
the connection and handle the problem
immediately.
----End
6 FAQ
This section will list the FAQs about the RBT presentation.
How to support registration of Non RBT user while subscribing advertising RBT
channels?
Set support_nonrbt_adrbt_subscription to 1 in RBT side.
1. Subscribe to RBT service
Subscription is required only for Non RBT users. If user is already RBT user, then directly
subscribe to corp service with a special Corp.
2. Subscribe to corp service with a special Corp account, which is used to manage the
advertising RBT service.
3. Subscribe to advertising RBT service.
For more details refer 3.6 Subscribing to the advertisement RBT Service