Subject: [CDNi] explanation on use cases.

From: ZhouZhipeng <[email-masked]>
Date: Tue, 16 Aug 2011 10:40:04 +0000

Dear all,
I have taken a carefully review on the meeting minutes and felt that this meeting is really very practical with many valuable comments and opinions.
Thanks for Manning's presentation on my slides and thanks for all members' feedback on these use cases.
I feel most people esp. the chairs have made consensus that the CDNI is to cooperate multiple CDNs hence the signaling and metadata would be the output of this project.
So for my use case 3 and 4, obviously they are not proposing for operations(such as transcoding) but to describe how such operations may be implemented and controlled/signaled in the CDNI scenario.
Absolutely CDNI will not dive into such basic operations since they have existed and been mature for quite a few years( transcoding belong to ITU/MPEG) while the gap is the interaction between CDNs for the fulfillment of these operations( e.g. how uCDN informs dCDN to support some media adaptation).
Totally, these two cases are to enhance the value of CDN service and in fact as I know are supported in more and more CDN providers.(transcoding has been the popular service by many CDN providers. You may google if you like to learn the names of those CDN providers) Further I think for CDNI to support such functionality would not be complicated since we only need to clarify how to transfer the signaling and the individual CDN may fulfill the functionality internally.
I also notes in Gilles's slide 7 on the "CDN capability use cases", it illustrates that "an end-user switches from her connected TV to her mobile".  Obviously if at first a CDN may support mobile application and another CDN may support TV application. If to connect these two CDNs, they should both support mobile and TV applications.

Besides, for the "differentiated delivery", it is a very popular concept in fact. Many people have already shared the understanding on this use case and feel it is similar to some other concepts such as SLA. While I like to explain that this case is towards the content awareness and the object is the content.

For other technology area the differ service may be towards a link or a transport chain or the type of transferred data. By similar logic for the content delivery, the differentiation may be set towards the specific content.

As for my first two use cases, I think they are relevant to some requirements but:

1)      Those requirements do not have use case to support( for example, the whitelist/blacklist looks relative ( not exactly) but miss the use cases)

2)         The content of these two use case are new. Somehow the Bertrand-usecase has shared the footprint use cases that is to show the requirements of several requirements(geography extension...)

But it has not shown what information would be exchanged and how multiple CDN cooperate for a task.
So, I personally feel these two use cases may be merged under the section of  "Footprint Extension Use Cases".

By the explanation above, I hope it may help you more understand my use cases. For any concern, welcome your more comments.
Thanks.
Zhipeng

-----------------------------------------------------
Huawei Carrier Software Business Unit.
No.101,Software Avenue,Yuhuatai District,Nanjing, P.R.of China
Zipcode:210012
E-Mail: [email-masked]<mailto:[email-masked]>
Phone:(+86) 25-56620690
Fax:(+86) 25-56624081
Mobile:(+86) 13404162849
-----------------------------------------------------