0% found this document useful (0 votes)
64 views5 pages

Sources of Revenue To Deliver ROI

The document discusses sources of revenue for telecom companies from subscribers and third parties including voice, data, app purchases, and advertising. It also covers network design methodologies like bottom-up and top-down approaches and types of network designs including mesh and rings networks. Key aspects of network design are identified like customer requirements, sites, costs, equipment, and reliability. Quality of service factors for networks like latency, jitter, packet loss, bandwidth, and errors are defined. Documentation for network designs should include executive summary, requirements, current/new designs, testing results, implementation plan, and detailed maps/configurations.

Uploaded by

Anil Shirsat
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
Download as doc, pdf, or txt
0% found this document useful (0 votes)
64 views5 pages

Sources of Revenue To Deliver ROI

The document discusses sources of revenue for telecom companies from subscribers and third parties including voice, data, app purchases, and advertising. It also covers network design methodologies like bottom-up and top-down approaches and types of network designs including mesh and rings networks. Key aspects of network design are identified like customer requirements, sites, costs, equipment, and reliability. Quality of service factors for networks like latency, jitter, packet loss, bandwidth, and errors are defined. Documentation for network designs should include executive summary, requirements, current/new designs, testing results, implementation plan, and detailed maps/configurations.

Uploaded by

Anil Shirsat
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1/ 5

Sources of revenue to deliver ROI

• Subscriber revenue

Voice & Data revenue directly from subscribers


Data bits (charges to user based on bits of downloads)
Services (charges to user for data services – SMS, remote data storage/sync/backup, etc)
Apps purchases (charges to user for mobile app purchases)
Products purchases (charges to user for product purchases, such as ring tones, songs, etc.)

• Non-subscriber revenue

Revenue share for third party services


Revenue share from mobile apps purchases
Revenue share from product purchases
Revenue from advertising to subscribers by third parties

Design Methodology

• A bottom-up approach is the piecing together of systems to give rise to grander


systems, thus making the original systems sub-systems of the emergent system.
• A top-down approach (is also known as step-wise design) is essentially the
breaking down of a system to gain insight into its compositional sub-systems.

3. Network Model

The essential inputs to the design process are:


• customer traffic requirements;
• sites for nodes;
• equipment (link and node) costs;
• available duct network;
• Reliability requirements.

Design Types

Mesh Network.
Shared restoration mesh networks minimise the link cost by achieving direct routings for
working paths and the highest possible degree of sharing for protection paths. This effect
is most significant when links are long (because the savings are proportionately greater),
and when the connectivity of the network nodes is high (because a greater degree of
sharing of restoration capacity is possible). The traffic pattern is particularly important
for ring networks where it is advantageous to be able to fill rings evenly
Rings Network

Rings are the most common architecture found in metropolitan areas and span a large
distances. The fiber ring might contain as few as four wavelength channels, and
typically fewer nodes than channels. Bit rate is in the range of 622 Mbps to 10 Gbps
per channel.

Ring configurations can be deployed with one or more DWDM systems, supporting
any-to-any traffic, or they can have a hub station and one or more OADM nodes, or
satellites
Design Review of network design model

Design review is a tool that can be used to help companies improve the quality of the
services, reduce the time to market for a service and reduce the development and
scrap/rework costs of the project. It is a general activity that can be applied readily to
any industry, and can be used to improve the quality of services as well as products.

Quality of Service

Quality of Service (QoS) is the collective measure of the level of service to a subscriber
Quality of service is the ability to provide different priority to different applications,
users, or data flows, or to guarantee a certain level of performance to a data flow. For
example, a required bit rate, delay, jitter, packet dropping probability and/or bit error rate
may be guaranteed. Quality of service guarantees are important if the network capacity is
insufficient, especially for real-time streaming multimedia applications such as voice
over IP, online games and IP-TV, since these often require fixed bit rate and are delay
sensitive, and in networks where the capacity is a limited resource, for example in
cellular data communication.

A network or protocol that supports QoS may agree on a traffic contract with the
application software and reserve capacity in the network nodes.

A best-effort network or service does not support quality of service.

Performance criteria for QoS

• Latency/Packet delay (or delay in general)


It might take a long time for each packet to reach its destination, because it gets held up
in long queues, or takes a less direct route to avoid congestion. This is different from
throughput, as the delay can build up over time, even if the throughput is almost normal.
In some cases, excessive latency can render an application such as VoIP or online gaming
unusable.

• Jitter (delay variations)


Packets from the source will reach the destination with different delays. A packet's delay
varies with its position in the queues of the routers along the path between source and
destination and this position can vary unpredictably. This variation in delay is known as
jitter and can seriously affect the quality of streaming audio and/or video.

• Packet loss
The routers might fail to deliver (drop) some packets if their data is corrupted or they
arrive when their buffers are already full. The receiving application may ask for this
information to be retransmitted, possibly causing severe delays in the overall
transmission.

• Bandwidth or throughput
Due to varying load from other users sharing the same network resources, the bit-rate (the
maximum throughput) that can be provided to a certain data stream may be too low for
realtime multimedia services if all data streams get the same scheduling priority.

• Errors or bit error rate


Sometimes packets are corrupted due to bit errors caused by noise and interference,
especially in wireless communications and long copper wires. The receiver has to detect
this and, just as if the packet was dropped, may ask for this information to be
retransmitted

Documenting Your Network Design

In engineering, technical documentation refers to any type of documentation that


describes handling, functionality and architecture of a technical product or a product
under development or use.
Technical documentation aims at providing enough information for a user to
understand inner and outer dependencies of the product at hand.

Contents of a Network Design Document

• Executive summary
• Project goal
• Project scope
• Design requirements
• Current state of the network
• New logical and physical design
• Results of network design testing
• Implementation plan
• Project budget
AND
• Detailed topology maps
• Device configurations
• Addressing and naming details
• Network design testing results
• Contact information
• Pricing and payment options
• More information about the company that is presenting the design
– Annual reports, product catalogs, press releases
• Legal contractual terms and conditions

You might also like