Subscribers pay for the music download one time, for a flat fee. In some
cases, you may want to issue a license where the subscriber pays for a period of time.
At the end of that period of time, the subscriber has to pay another cycle.
Your legacy systems do not support this model, and hence the need to add new systems
that do not integrate very well with the legacy systems. You end up managing
these separately.
You now have the billing taken care of, but you have no means of auditing the transactions
between the subscriber and your content delivery platform. Worse, the content
is owned by another content provider, so you must interface to its server to purchase
the content, and then deliver the content to your subscriber. The content provider must
be paid at the time of your transaction, but the subscriber is not going to pay before
receiving a bill from you at the end of the month.
When the subscriber finally receives their bill, that subscriber refuses to pay, because
he or she never received the content. You do not have the tools to see the transaction
when it took place because your existing monitoring system does not support IP networks
and does not provide visibility to the IP transactions with the content provider.
You have to purchase yet another system to monitor the IP portion of your network.
And of course, we haven??™t talked about the network requirements to provide the
transport of music to your subscriber.
Pages:
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100