DeIay Controlin Multi-Class Multi –Server RST- based Communication Networks ViaM/K Setting

dc.contributor.authorAmin Babiker A/Nabi Mustafa
dc.contributor.authorMuawia Mohammed Ahmed Mahmoud
dc.contributor.authorIsmail El-Azhary T.
dc.contributor.authorHuda Adibah Mohd Ramli
dc.date.accessioned2018-01-17T12:08:37Z
dc.date.available2018-01-17T12:08:37Z
dc.date.issued2017-01-16
dc.descriptionمؤتمرen_US
dc.description.abstractAbstract In the present work, analysis of non-preemptive priority queues with multiple servers and multiple priority classes, which is based on Residual Service Time (RST) was utilized to calculate the total waiting time for system customers. Definitely, this waiting time is determined by several parameters such as the number of servers, the order of the Priority class to which the customer belongs and the total number of customers in the system.Analysis of the results showed that different Priority class order/Number of Servers combinations could attain the same waiting time. Accordingly, these parameters could be used in determining the desired level of performance expressed in terms of waiting time. The obtained results of waiting times and their relations with priority class orders and Number of Servers could help a lot in justifying and supporting this proposed RST-Based Analysis. Keywords Non-preemptive priority queues, residual service time, total waiting time, RST-based analysis.en_US
dc.identifier.urihttp://hdl.handle.net/123456789/10344
dc.publisherجامعة النيلين - كلية الدراسات العلياen_US
dc.subjectCommunication Networksen_US
dc.subjectCommunications Engineeringen_US
dc.titleDeIay Controlin Multi-Class Multi –Server RST- based Communication Networks ViaM/K Settingen_US
dc.typeWorking Paperen_US

Files

Original bundle

Now showing 1 - 1 of 1
Thumbnail Image
Name:
167.pdf
Size:
99.25 KB
Format:
Adobe Portable Document Format
Description:

License bundle

Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
1.71 KB
Format:
Item-specific license agreed upon to submission
Description: