tailieunhanh - Plug and Play Splitter Architectures Drive Operational Savings

Tham khảo tài liệu 'plug and play splitter architectures drive operational savings', công nghệ thông tin, phần cứng phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Next Gen NEIWORKS Plug and Play Splitter Architectures Drive Operational Savings Plug and Play Splitter Architectures Drive Operational Savings IE After service providers decide to deploy a particular fiber-to-the-premise FTTP architecture they are faced with a number of important decisions. This paper addresses one such decision that will significantly impact the network in terms of time performance flexibility and cost throughout its operational life. Providers must decide how to connect the F1 optical feeder cable inputs to the splitters in the fiber distribution hubs FDHs . There are several methods for making these connections but selecting the best technique will provide benefits in many other areas such as turn-up speed dealing with customer churn and easier maintenance and troubleshooting. Early decisions to splice Many early FTTP deployments sparked concerns about loss budgets. Since the use of connectors resulted in more loss than straight splicing the network architects decided splicing inputs to the splitters was preferable to minimize loss. The feeder cable was brought into the cabinet and prepped into a splice area. New splitters were installed with fiber pigtails that were spliced into one of the F1 fibers. This method resulted in slightly less loss and enabled the addition of more splitters as the network grew. However there were also a few downsides to splicing the F1 cables to the splitters. The first issue is the amount of time required to install each splitter. Splicing obviously takes considerably longer than mating two connectors. Also splicing has an affect on the work force. Each time a new splitter is added it requires technicians with more training and higher skill sets as well as the need to have all the specialized splicing equipment available. Not having one or the other readily available increases the time it takes to perform the task and slows down the overall deployment. Another issue created by splicing is in the initial turn-up of