![]() Keywords: service selection, streaming, UPnP Some delay grew higher, which could be affected by the increase of service providers’ load. There were anomalies at some scenarios though. Experiments prove that the optimization reduces average end-to-end delay between clients and multimedia streaming service providers at the rate of 35.343%. In this study, a method of optimizing the UPnP-based service selection of multimedia streaming for dynamic condition is proposed. Implementations of multimedia streaming applications in dynamic environment, where there might be changes on delay, packet loss, and the availability of services at service providers, causes the urgency of optimization in existing service selection mechanism. ![]() Client applications just fetch a service from a number of service providers in the network, even randomly. On existing multimedia streaming applications, service selection is done without any prioritizing. Service selection will be held based on current condition of the network, such as delay and packet loss. The selection of the most appropriate service is to be done automatically by UPnP clients. In a condition where some hosts run same services, how clients select them becomes one interesting issue. The process of service discovery in dynamic environment should reduce manual configuration, enable automatic discovery and optimal service selection, and also offer up-to-date services available. It arranges addressing, discovery, description, and also device and service selection. UPnP works at a network supporting multicast messages. Universal Plug and Play (UPnP) enables networking without manual configuration and administration. Kata kunci: pemilihan layanan, streaming, UPnP Dari hasil percobaan, terbukti bahwa optimasi tersebut menurunkan end-to-end delay rata-rata antara klien dengan penyedia layanan streaming multimedia sebesar 35,343%, meski terdapat anomali pada beberapa skenario, yaitu naiknya end-to-end delay rata-rata, yang bisa jadi dipengaruhi oleh peningkatan beban kerja penyedia layanan. Pada penelitian ini diusulkan metode dalam melakukan optimasi pada pemilihan layanan streaming multimedia berbasis UPnP untuk kondisi dinamis, yaitu kondisi di mana dapat terjadi perubahan pada delay, packet loss, dan ketersediaan layanan. Implementasi aplikasi streaming multimedia di lingkungan dinamis menyebabkan perlunya optimasi terhadap mekanisme pemilihan layanan yang sudah ada. ![]() Aplikasi klien mengambil begitu saja salah satu layanan streaming multimedia dari sejumlah perangkat penyedia layanan di jaringan, bahkan secara acak. Pada aplikasi-aplikasi streaming multimedia berbasis UPnP yang ada, pemilihan layanan dilakukan tanpa penentuan prioritas sama sekali. Pemilihan layanan dilaksanakan berdasarkan parameter yang mencerminkan kondisi jaringan saat itu, seperti delay dan packet loss. Pemilihan layanan yang paling sesuai dapat dilakukan secara otomatis oleh klien UPnP. Pada kondisi di mana beberapa host menyediakan layanan yang sama, bagaimana klien memilih layanan menjadi permasalahan tersendiri. Proses penemuan layanan dalam lingkungan dinamis harus mengurangi konfigurasi manual, memungkinkan penemuan otomatis dan pemilihan layanan yang optimal, serta menawarkan secara terkini layanan-layanan yang tersedia. Ia mengatur pengalamatan, penemuan, deskripsi, serta pemilihan perangkat dan layanan. UPnP bekerja pada jaringan yang mendukung pesan multicast. So, you could implement as much or little of the UPnP specs as is convenient.Universal Plug and Play (UPnP) memungkinkan adanya jaringan tanpa konfigurasi dan administrasi manual. If you don't care about third party use of server or renderer, you're free to do whatever works for your product. Its also what I do in the UPnP stack I maintain and I haven't found this to cause any problems.Īll that said, you'll only really need to worry about any of this if you want other programs to use your server or renderer as a standard UPnP device, independently of your combined server + renderer + control point. I can't find a definitive reference for this but it seems to be strongly implied in section 2.3 (device description) of the v1.1 architecture document. If you decide to use embedded devices, I believe that each device should have its own UUID. Section 2.2 (Device Model) of each of the above docs says that renderer and server devices respectively can be either root or embedded. I think you can however embed one (either) device in the other. UPnP-av-MediaRenderer-v3-Device-20101231.pdf & UPnP-av-MediaServer-v4-Device-20101231.pdf define specific device types for server and renderer (see section 3 of each doc) so you'll need separate UPnP devices. ![]() You can't combine your media server and renderer into a single UPnP device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |