Your business intends to create in depth use of video conferencing and multi-media applications. How do you identify what bandwidth resolution (T1, DS3, OCx/Sonet, etc.) would best meet your desires and incorporate that call into your network cowl these applications?
I'd say that it depends on what sort of service and QoS you are looking at. For example, after you say "video" you mean video conferencing and not one thing like VoD. The Bandwidth necessities can vary in step with your service requirements.
As an example: For IPTV services, the image quality depends on the encoding deployed: MPEG-2 consumes approx. 3.75 Mbps, whereas MPEG-four needs approx. a pair of Mbps for the same high-quality image production. Conjointly broadcast TV is delivered using IP Multicast that makes the bandwidth required smitten by the number of channels offered and the encoding rate. 200 channels of MPEG-two in commonplace definition will take approx. 750 Mbps of bandwidth. VoD, on the other hand, may be a unicast per-viewer channel. one thousand normal definition VoD users can would like appro. 3.75 Mbps.
The QoS needs for video conferencing using H.323 (SIP could be completely different once more) will be planned on the "Rule of seventy five" as follows: Calculate the minimum bandwidth needed by every of your applications ( e.g., video, voice, information). The full of this bandwidth is that the minimum demand for any given link and it should consume NO MORE than 75% of the full obtainable bandwidth on the link. The seventy five% rule makes allowances for bandwidth required for over head traffic, like routing, Layer 2 keepalives and different applications, like, email, HTTP etc.
Thus, Capacity coming up with for H.323, should seem like one thing as follows:
Video knowledge + 20% = bandwidth required.
Example:
Video data rate: Bandwidth Required:
512 kbps = 614 kbps
1.5Mbps = 1.eight Mbps ...
For issues like number of concurent users and more stuff on video conferencing you'll be able to perhaps take into account trying into Cisco's solutions offered and also TANDBERG boxes.
Cisco considers anything 766Kb to be a "slow link" for VOIP. Additionally you would like to contemplate the criticality of the sites thus you will would like 2 separate connections. All multi-media applications run on prime of your other applications so QoS only permits a preference of who goes first.
You wish a sensible baseline of non-multi-media applications (VOIP). Therefore bandwidth desires to be in a position to handle all necessary applications within the network.
Conjointly, you will would like to remember that the bandwidth aggregation at the Data Center needs to fulfill or exceed all inbound remote web site traffic. In different words, if I have three remote sites all with T1s. I am going to need additional than one T1 at the Data Center to manage the traffic. Remember unless this is often a greenfield then baseline, baseline, baseline!
When it involves streaming video, bi-directional - you're going to have to consider the quality of the compression you're planning to use. If you are planning on using high definition video 1 direction it's counseled to possess a minimum of 2MB within the direction of the video being accessed.
Therefore if you are streaming video to your laptop then you wish to make positive that you just get 2MB download capacity. Additionally, another issue to stay in mind is latency and loss of packets. I might advocate staying away from wireless for this sort of application as it will add latency and cause problems later. DS3 bandwidth and anything higher may be over kill, but would simply be ready to handle your demands.
Without knowing specifics, it's hard to provide an explicit answer, however, one will still specify a systematic method for calculating required bandwidth. Once you know the bandwidth requirement, then it's all about negotiating the foremost economical means to order that bandwidth from a network provider in the area.
Here is what I might suggest:
1. Calculate the height external link bandwidth requirements (inter-office data transfer, video conferencing, email transfers. With attachments running in tens of megabytes, email traffic cannot be ignored these days.).
2. Real time applications being mostly jitter and delay sensitive - so you have to make sure that you may have enough bandwidth when they need it. The bandwidth of video depends on the mpeg profiles used (while not going into specific, typically 1.five Mbps will offer you terribly sensible video on a PC (equal to VCD quality). HDTV pictures will take concerning twenty Mbps - however that is domain more reserved for IP TV service suppliers). Most current users of interactive video communications will be happy with the photographs coded and transmitted @ 512 Kbps. This includes audio and video plus management signaling. Therefore, one ought to provision a minimum of 512 Kbps per video stream, and a lot of the better (I would say 1.five Mbps is the great if you are a huge organization and use a massive TV for video conferences)). Therefore, multiply bandwidth for a single stream by the amount of parallel streams required. Now that determines the full peak real time usage.
3. There's no specific rule - but wise men with expertise advise to keep the height real time among 60 to seventy five% of network bandwidth out there leaving the remaining capacity for background traffic. In an exceedingly small organization of 5 people - it is straightforward to inform people not to download gigabyte attachments when video conferencing goes on , however in larger organizations it's arduous to enforce such things except with router policies (assuming they have QoS support), and you'll be able to deal with occasional unhappy users.
4. Currently, once you recognize your bandwidth requirements, it is time to talk to the network operator how they will offer that bandwidth in the most price effective way.
I'd say that it depends on what sort of service and QoS you are looking at. For example, after you say "video" you mean video conferencing and not one thing like VoD. The Bandwidth necessities can vary in step with your service requirements.
As an example: For IPTV services, the image quality depends on the encoding deployed: MPEG-2 consumes approx. 3.75 Mbps, whereas MPEG-four needs approx. a pair of Mbps for the same high-quality image production. Conjointly broadcast TV is delivered using IP Multicast that makes the bandwidth required smitten by the number of channels offered and the encoding rate. 200 channels of MPEG-two in commonplace definition will take approx. 750 Mbps of bandwidth. VoD, on the other hand, may be a unicast per-viewer channel. one thousand normal definition VoD users can would like appro. 3.75 Mbps.
The QoS needs for video conferencing using H.323 (SIP could be completely different once more) will be planned on the "Rule of seventy five" as follows: Calculate the minimum bandwidth needed by every of your applications ( e.g., video, voice, information). The full of this bandwidth is that the minimum demand for any given link and it should consume NO MORE than 75% of the full obtainable bandwidth on the link. The seventy five% rule makes allowances for bandwidth required for over head traffic, like routing, Layer 2 keepalives and different applications, like, email, HTTP etc.
Thus, Capacity coming up with for H.323, should seem like one thing as follows:
Video knowledge + 20% = bandwidth required.
Example:
Video data rate: Bandwidth Required:
512 kbps = 614 kbps
1.5Mbps = 1.eight Mbps ...
For issues like number of concurent users and more stuff on video conferencing you'll be able to perhaps take into account trying into Cisco's solutions offered and also TANDBERG boxes.
Cisco considers anything 766Kb to be a "slow link" for VOIP. Additionally you would like to contemplate the criticality of the sites thus you will would like 2 separate connections. All multi-media applications run on prime of your other applications so QoS only permits a preference of who goes first.
You wish a sensible baseline of non-multi-media applications (VOIP). Therefore bandwidth desires to be in a position to handle all necessary applications within the network.
Conjointly, you will would like to remember that the bandwidth aggregation at the Data Center needs to fulfill or exceed all inbound remote web site traffic. In different words, if I have three remote sites all with T1s. I am going to need additional than one T1 at the Data Center to manage the traffic. Remember unless this is often a greenfield then baseline, baseline, baseline!
When it involves streaming video, bi-directional - you're going to have to consider the quality of the compression you're planning to use. If you are planning on using high definition video 1 direction it's counseled to possess a minimum of 2MB within the direction of the video being accessed.
Therefore if you are streaming video to your laptop then you wish to make positive that you just get 2MB download capacity. Additionally, another issue to stay in mind is latency and loss of packets. I might advocate staying away from wireless for this sort of application as it will add latency and cause problems later. DS3 bandwidth and anything higher may be over kill, but would simply be ready to handle your demands.
Without knowing specifics, it's hard to provide an explicit answer, however, one will still specify a systematic method for calculating required bandwidth. Once you know the bandwidth requirement, then it's all about negotiating the foremost economical means to order that bandwidth from a network provider in the area.
Here is what I might suggest:
1. Calculate the height external link bandwidth requirements (inter-office data transfer, video conferencing, email transfers. With attachments running in tens of megabytes, email traffic cannot be ignored these days.).
2. Real time applications being mostly jitter and delay sensitive - so you have to make sure that you may have enough bandwidth when they need it. The bandwidth of video depends on the mpeg profiles used (while not going into specific, typically 1.five Mbps will offer you terribly sensible video on a PC (equal to VCD quality). HDTV pictures will take concerning twenty Mbps - however that is domain more reserved for IP TV service suppliers). Most current users of interactive video communications will be happy with the photographs coded and transmitted @ 512 Kbps. This includes audio and video plus management signaling. Therefore, one ought to provision a minimum of 512 Kbps per video stream, and a lot of the better (I would say 1.five Mbps is the great if you are a huge organization and use a massive TV for video conferences)). Therefore, multiply bandwidth for a single stream by the amount of parallel streams required. Now that determines the full peak real time usage.
3. There's no specific rule - but wise men with expertise advise to keep the height real time among 60 to seventy five% of network bandwidth out there leaving the remaining capacity for background traffic. In an exceedingly small organization of 5 people - it is straightforward to inform people not to download gigabyte attachments when video conferencing goes on , however in larger organizations it's arduous to enforce such things except with router policies (assuming they have QoS support), and you'll be able to deal with occasional unhappy users.
4. Currently, once you recognize your bandwidth requirements, it is time to talk to the network operator how they will offer that bandwidth in the most price effective way.
