ACG Research

ACG Research
We focus on the Why before the What
Showing posts with label Dennis Ward. Show all posts
Showing posts with label Dennis Ward. Show all posts

Friday, June 12, 2015

Five Lessons Equipment Providers Learned from Deploying IoT Solutions

Dennis Ward discusses five lessons the equipment providers have learned form deploying Internet of Things solutions. He talks about horizontal platforms, end-to-end solutions, subscriber-based billing models and security.

Click to read the entire blog.

Click for more information about ACG’s IoT services.

Wednesday, April 29, 2015

Is API Regulation the Future of Information Security?

Recently, I listened in on an IEEE-SA sponsored roundtable at the RSA Conference in San Francisco on April 22, 2015. Karen McCabe, IEEE-SA senior director, Technology Policy and International Affairs, lead a discussion on whether Application Programming Interface (API) regulation is necessary for the future of information security. Participants were Bret Hartman, VP and CTO, Security Business Group, Cisco Systems, Inc.; Cooper Quintin, staff technologist, Electronic Frontier Foundation; Monique Morrow, CTO, evangelist, New Frontiers Development and Engineering, Cisco Systems, Inc.; Hadi Narhari, chief security architect, NVIDIA; Rob Zazueta, Director Platform Strategy, Mashery (Intel); Matt McLarty, VP, The API Academy, CA Technologies; and moderator Kimball Brown, Independent Technology Consultant.

What is an Application Programmable Interface (API)? In its native form, APIs are building blocks for developers to construct programs. APIs often come in the form of a library that includes specifications for routines, data structures, object classes and variables. In other cases an API is simply a specification of remote calls exposed to the API consumers (for example, JSON and REST). These APIs are used primarily for many of the virtualized functions/service programs we are seeing on the market today. Think of a remote controlled robot on a manufacturing floor, a virtual network function in a switch or your favorite application on your cell phone that accesses the sensor on your wrist that monitors your heart or on a macroscopic scale, the billions of devices that are forecasted to exist via the Internet Of Things (IoT) and the programs to control them. All of these programs will rely on APIs in their development. Imagine if a rogue hacker tried to manipulate these programs via accessible APIs to cause harm? There lies the issue. How can this be avoided? What is the state of protection now? And where does this responsibility lie?

The panel agreed that there needs to be more education given to developers on building security into their initial designs, possibly implementing an attack tree or use case security framework from which to build. This framework should be transparent to the consumer because this structure should not impede on the go-to-market strategies that affect the bottom line. Although the panel agreed that this would be a good idea, because there are so many types of APIs, there is no standard way to implement this. As for IoT, the development environment is not like a static information technology environment where the attack points are relatively predictable. IoT environments, in many cases, will be mobile, personal and limited in memory space for which traditional security measures cannot be used. The threat model will have to be redefined, which has yet to happen. Once one is established this model should be communicated to developers as well as consumers.

Panel member also discussed a universal consortium establishing standards and if this would help the problem? The answer was a little but it would not fully address the problem, because the market pace and demand will be too fast for standardization groups to react. One thought was to develop an emerging new API platform with proper hooks and external partners buying into the model. This thought spurred an interesting conversation dealing with the integrity of the partners in the joint venture. How credible are they? This led quickly into the examples of Target, Snapchat and J.P Morgan/Chase where the weak link was the integrity of the partner and not necessarily the flaw of an API, underscoring that business partners having a stake in the level of security that is needed. This led to an interesting discussion concerning Person Area Networks (PAN) where the person becomes the API. Would a developer, consumer or human PAN bill of rights help? Again a “one-size-fits-all” constitution would be tough because every person has his or her own view of what personal security means? It would be hard for a government or business to enforce such a constitution. Businesses do not want regulation to hinder innovation or sales.

The discussion concluded with the final question of how APIs will look in 10 years? All panelists agreed that presently APIs are in a single-user mode and need to move toward a distributed model. Higher levels of SDKs need to be implemented. APIs should have a different paradigm for deployment such that devices, services and systems govern themselves. For example, applications should automatically inform the API what it can and cannot do during processes. For IoT, this method will allow better integration between devices, reduce human regulation policies and thus optimize security.
 
     Dennis Ward
     dward@acgcc.com
     acgcc.com

 

Monday, March 16, 2015

New Entrants into the DCI Small Form Factor Market

Two equipment titans Coriant and Alcatel-Lucent entered the Data Center Interconnect (DCI) small form factor market with targeted packet optical networking products. Coriant added to its 7100 family of products with the 7100 Pico™ Packet Optical Transport Platform and Alcatel-Lucent added to its 1830 Photonic Service Switch (PSS) family of cloud optimized metro products with its 1830 PSS-4, 8, 16 optical transport platforms. Both of these devices integrate cleanly into their respective portfolios and are Software Defined Network (SDN) enabled for dynamic service instantiation.

These products are significant because they validate the need for higher performance in this growing sector of the packet optical market. Bell Labs forecasts an increase of metro traffic by 560 percent by 2017. By 2019 there will be 60 percent more data centers in the world’s metro areas and DCI volumes will increase 400 percent. Why? With cloud-based services, the industry has recognized the need for data center interconnect (DCI). Initially, service providers offering XaaS solutions were connecting customers’ data centers to service providers’ data centers.  New requirements for DCI have grown out of the operators’ needs to deploy very high-capacity, high-speed, low-latency, efficient transport between their own data center sites. In addition, rich data types such as video, multimedia mobile backhaul, cloud and data center traffic are also forcing the need for more intelligent programmability and automation in management of these traffic patterns. However, because of the size and power constraints of the metro data centers to date, platforms need to fit strategically into smaller Point of Demarcation (POD) locations with low power and high cooling requirements. This is where the DCI small form factor market emerges.

Some key specifications and product comparisons for DCI Small FF at-a-glance:

DCI Small FF Requirements
Coriant 7100 Pico
ALU 1830 PSS –4, 8, 16
4 RU Chassis or less
2 RU
PSS-4=(2 RU), PSS-8(3 RU), 16(8 RU)
DWDM w/ Tb/s fiber capacity
88 DWDM @ 10 & 100G
8 CWDM, 32 DWDM (400G – 1.6 Tb/s)
Eth, OTN, SONET
Eth, OTN, SONET
Eth, OTN, SONET
SAN (FICON, etc.)
SAN interfaces
SAN interfaces
Video (DVB, SDI, etc.)
Video interfaces
Video interfaces
40 - 100G+ ntwk interface
40G
10G, 100G, 200G
10GE – 100GE modular I/O
1, 10 , 100 GE (176 GE max)
10 , 40, 100 GE (w/112SDX11 card)
Pwr (AC or DC)
AC/DC (110/220VAC / -48VDC)
AC/DC (110/220VAC / -48VDC)
Open API/SDN mgt
Transend
SDN Enabled

ACG sees a bifurcation of the DCI market between small and multislot form factor devices. The total high-speed DCI market was approximately $400 million in 2013 and is forecasted to grow to $4 billion by 2019. Growth for the DCI small form factor is predicted to be $3 billion by 2019, 97.3 percent CAGR 2014–2019. Growth for the DCI multislot is predicted to be $1 billion by 2019, 27.1 percent CAGR 2014–2019. This market segment is growing because of ADVA, BTI, Ciena, Cisco, Cyan, ECI Telecom, Ekinops, Fujitsu, Huawei, Infinera and ZTE. Who will command the market share? Time will tell but in the meantime ACG is tracking the progress of this exciting market in its new DCI Optical Networking Market Worldwide syndication.


Contact sales@acgcc.com to find out more information or schedule a meeting with Dennis Ward and Paul Parker-Johnson to discuss this research.


Friday, February 20, 2015

Worldwide Optical Market Increases Slightly in 4Q

Demand for rich media and OTT services to the home and mobile devices are market trends that continue to pressure providers to move DCs into the metro and enhance core infrastructures

The Worldwide Optical Networking market rebounded slightly in Q4 2014 to $3.375 billion in revenue, dipping 7.0 percent q-q but increasing 2.7 percent y-y. The year closed with annual revenue of $13.1 billion, 0.9 percent y-y increase. Demand for high-speed optical infrastructure remains steady, driven by increased sales of 100G interfaces in the Metro and LH WDM segments. “The 4Q revenue jump has been observed within the optical market for the last three out of four years. The year-over-year growth indicates a slight increase of spending but not necessarily a bullish market,” stated Dennis Ward, principal optical analyst, ACG.

Regionally, APAC is the top producing region though revenue declined 5.3 percent q-q. North America remained in the 2nd position, increasing 7.8 percent q-q and up 25.4 percent y-y. EMEA remained a strong 3rd at 11.4 percent q-q but showed a dip of 5.2 percent y-y. LAM improved with 6.3 percent q-q and 10.2 percent y-y growth.

The growth rate of 100G optical interfaces remains steady. The trend to support 4G and mobile Internet with its rich services is driving this as well as 400G trials in all regions. But 400G standards are still in flux. Although the Tier 1 communication service providers gear up for 2015, many of the optical equipment providers are finding a real market with the content service providers (CSPs) as they migrate their data centers into the metro closer to their customer bases. Some of these CSPs are looking for simple high- capacity solutions via dark fiber across the metro; others want more sophisticated long-haul solutions into the metro. “We see the demand for DCI bifurcating into two distinct market segments of products, small slot versus multislot solutions,” says Dennis Ward.  

Service provider SDN and NFV in combination with P-OTS/Metro WDM solutions are gaining traction in network infrastructure selection and deployments. P-OTS segment saw a quarterly dip in its revenue contribution but maintained its $.5 billion run rate, decreasing 7.9 percent q-q but increasing an impressive 28.9 percent y-y. The top five worldwide players in 4Q were Huawei, ZTE, Ciena, Infinera and Alcatel-Lucent, respectively.  

Metro WDM maintained its quarterly $1 billion run rate but decreased 0.7 percent q-q and 9.2 percent y-y. Metro traffic is predicted to grow faster than backbone traffic as more regional data centers are located closer to the user community. As much as 70 percent of the traffic is predicted to stay within the metro from which it originated, bolstering east-west traffic between data centers. The increase in DCI supports this trend and will drive the need for additional capacity by the traditional service providers, MSOs, cloud and data center operators.


For more information about ACG's optical services, contact sales@acgcc.com.




Tuesday, February 3, 2015

Internet of Things Makes a Showing at the CES 2015

Invited by the IEEE-SA to participate on a panel called the “IEEE IoT Soiree,” I recently had the pleasure of attending my first CES show. Our panel critiqued a few startups in the IoT space (http://ces.ieeesa-events.org/). A key take-away from this event was that investors are really actively not investing in IoT, but investors seem to be looking for companies that will change the way people do things and enhance their lives. The products must have a strong lifestyle changing effect. The startups that were presented centered on edge devices, but some may be service provider worthy and turned into a viable service business. Cisco panelist Maciej Kranz said that the industrial IoT is where the money is, but enterprises are still fearful of taking the leap because of unknown security issues and unsubstantiated return on investments. Although true, there are sustainable IoT designed to show sustainable IoT scenarios and businesses that service providers can leverage. Another take-away centered on how to stimulate enterprises to embrace IoT and use the solutions for their own benefits.

 

After the event I began my exploration. This was the first time I attended the CES event and it was impressive. However my first impression was “crowded”! Why? This year the convention—the largest CES to date with more exhibition space than last year—hosted 170,000 people and about 3,600 exhibitors. The event was distributed between two convention centers and hotels throughout the Las Vegas strip.  However, it was organized with themed areas, for example, fitness, wearables, privacy, home security, and branded aisles showcasing French, Israeli, Korean and Chinese technology. The exhibit locations were itemized into product categories such as 3D printing, digital Imaging/Photography, online media and wireless devices and services.

There were plenty of commercial products with IoT solutions or marketing touting “connected” devices as well as wearable watches and fitbit-like devices. Mind control products, using the frontal lobe, were quite intriguing.  3D video experiences were also popular (via TV, glasses for gaming, etc.). I was particularly interested in the health, biotech and wearables areas, promising for service providers (thank goodness they were close together!). See forecast (link to press release). One example of cutting-edge connect solution development was exhibited by Jeff Li, vice president of iHealth, http://community.ihealthlabs.com/Protals/Home.aspx, who mentioned that it is now building out a cloud service aimed at service providers . 

The event although overwhelming, it did reinforce that IoT can be a viable service business once providers figure out how to address the market, security issues and prove return on investments. But if you plan to go to CES 2016 my advice is to invest in good, comfortable shoes because you will be walking for miles!

For more information about ACG's IoT services contact sales@acgcc.com.

Wednesday, January 7, 2015

IoT Offers Opportunity for Service Providers and Vendors

The Internet of Things (IoT) market opportunity across the cellular network will be worth $138.4 billion by 2018 with a compound annual growth rate of 33.2 percent. The key service provider verticals are connected car, home, industrial IoT, utilities, and wearable technology. The market is very fragmented with many players from a wide range of industries; however, each has fundamental approaches. Industry standards bodies and consortiums, such as OneM2M, IEEE-SA, ITU-T and IIC, are working on setting a single set of core standards to guide the industry.

All equipment providers are striving to position themselves as key vendors though at present no one has a complete solution. Ericsson, Cisco, ALU and recently Intel have horizontal IoT platform solutions that address early and late SP adopters. Ericsson leads the EP platform sales with total 1Q14 and 2Q14 revenue of $26.7 billion.

Service providers are a key part of the IoT value chain. However, to be successful, ACG recommends that SPs continue building out their core infrastructures by focusing on the common service entity functions: BSS/OSS, provisioning management, policy management, reporting management, data management, security management/governance and diagnostics.

Use cases are the best way to validate IoT implementations. For SPs, use cases that yield the most value have the following attributes: highly managed, mission critical, life dependent, warrant high liability, and regulatory constraints.

Click for more information about Dennis Ward.

For more information about the forecast contact sales@acgcc.com.


Monday, July 7, 2014

IoT B2B Ecosystem: How Can SPs Retain Their Maximum Share?

The OneM2M joint standards groups partition the Internet of Things (IoT) ecosystem by access domain, network domain and application domain. Within these domains the service providers (SP), specifically wireless SPs, are in the network domain and are responsible for the operational and business system services of the devices (OSS/BSS), for example, SIM provisioning, monitoring and management of the device over the “air,” routing traffic from the device to backend systems and applications or to other devices in the network, billing and recording of device activity based on bandwidth usage or further analytics associated with the application deployed. In a legacy machine to machine (M2M) scenario the value chain for the SP was clear; however, with the new IoT ecosystem this and business models have changed. How can SPs obtain the most value and retain reasonable financial margins within today’s IoT ecosystem?

Traditional M2M Business Models
Established M2M business models, which are limited in scope and structured, were quite clear and the revenue share among the domains was evenly distributed and predictable. Leading SP network operation field specialists acknowledge that the device provider, network provider and the application provider each receive one-third of the revenue.  A customer would request a defined service, such as a fleet/asset tracking service, from the service provider who most likely had a purpose-built solution. Depending on the quantity of assets that needed to be tracked, the service provider would know precisely how many unintelligent devices and SIMs to purchase from his device supplier, servers from the network provider and software packages to order from the applications provider. The SP would be responsible for provisioning its custom OSS/BSS systems and application services and provide the management. The customer would pay for the devices and software licenses upfront and either pay the SP per connection or by bandwidth usage. The device and software vendors would require a maintenance fee, which the SP would pass on to the customer. This is now an obsolete business model.

Present M2M/IoT Business Models
In the new M2M/IoT ecosystem SPs’ role and business models have changed. According to Network specialists, the device vendor gets around 20 percent; the network provider gets 15 percent and the application provider gets 65 percent. The new enhanced M2M devices have advanced processors that make them more intelligent, aware and thus more valuable. Because of enhanced hardware and firmware these devices can be embedded with antennas that can speak directly to the internet via 3/4G cellular or via WiFi routers. In most cases the radio access portion of the network domain has not been upgraded (2G or 3G wireless) so the expense is less. SPs use OSS/BSS platform partners because the OSS/BSS layer must be enhanced to accommodate the intelligent access devices. Application layer services are leveraged between application platform providers’ partnerships. These providers employ their own device, storage, cloud suppliers and application designers. To compete SPs have to engage in various business arrangements and complex strategic alliances with equity interests and exclusivity clauses. The negative effect is revenue fragmentation; however, providers can charge the customer more and thus raise the overall average revenue per unit. In this fragmented and crowded environment, how can the SPs continue to earn their full value?

Service Provider-Centric Use Cases
To earn their full value in the M2M/IoT ecosystem, SPs have to select their verticals and use cases very carefully. What are the characteristics of a monetizable use case for SPs? Service providers must adopt use cases that require a highly managed infrastructure and within these verticals should be mission critical and/or life dependent as well as wireless connectivity. These use cases will warrant more liability and require more regulatory demands but will enhance the importance of the SP’s network. The SP will maintain the value in the IoT ecosystem and customers will pay premium for the enhanced quality service. The following are examples of service provider-centric vertical use cases:
  • Healthcare: Remote heart/lung/brain monitoring for patients in transit; remote surgical services (monitoring/surveillance)
  • Transportation: Fleet/Asset tracking services where environmental controls for cargo/livestock need monitoring; telemetry (driverless vehicles); highly critical vehicle diagnostic monitoring and proactive resolution services
  • Manufacturing: Airborne robotic devices; off-shore mobile device control and monitoring services
  • Utilities: SCADA monitoring and proactive purification services for gas, water, soil, etc.
  • Government: Surveillance of mission-critical items; disaster recovery bots
  • Telecommunications: Banking processes and monitoring in remote areas

Tuesday, June 10, 2014

IoT In Perspective, Ready for Reality?

Kevin Ashton, cofounder of the Auto-ID Center at MIT that created the Radio Frequency Identification (RFID) global standard, is credited with the expression “Internet of Things,” envisioning a “system where the internet is connected to the physical world via ubiquitous sensors.” His vision in 1999 is not far from today’s reality. Technology has advanced to a point where almost anything can be “sensor-ized” to collect, store and transfer data. Interestingly enough, RFID tags were designed to categorize, itemize and quantify things. Hence the question, how big is the IoT market today?

Views in the market are that it is difficult to quantify simply because the concept is too broad and connections are hard to evaluate. Clearer explanations as to what a “connection” is within the IoT sector needs to be defined further. Nevertheless, some companies have generated numbers. Cisco made an attempt to embrace the concept within the explanation of the “Internet of Everything”. Using “Value at Stake” the worldwide market size was predicted to be $14.4 trillion in 10 years, where 45% or ~ $6,480 billion was attributed to machine to machine (M2M) connections. This is particularly interesting to service providers (SPs) because they will own these connections. If we analyze this number linearly, then for one year, the expectation for the worldwide M2M market size is about $648 billion.


Source: Cisco IBSG, 2013; Note: To make the numbers work, the actual IoE should be $14.160 trillion.

But what is the potential value per connection in a year? Revenue estimates for SPs and total cost of ownership (TCO) evaluations for customers are definitely of interest. The total number of M2M cellular connections last year was around 132 million. Thus: $648 B/1 yr x 1 yr/132M connections = $4,909/connection in a year (~ $409 per month).

Last year (August 2013) the top number of M2M connections for U.S. companies:

Service Provider
M2M Connections (Millions)
Revenue(M) (Yr: $4909/conn)
AT&T Mobility
14.7
72,162
Verizon
8
39,272
Sprint
3.3
16,199
T-Mobile
3.3
16,199

Therefore, if the potential values are in the correct order of magnitude for M2M, (not considering the CAGR sifts, etc.), then the increase in connections because of IoT will essentially bring increased revenue to SPs. Is that really true? Much of the margin depends on the revenue shared between the SP’s platform partners as well.

IoT Platforms: The M2M/IoT platforms that are being deployed—some have taken several years to develop—have several vendors within their ecosystems. Bigger SPs had to partner with these platform providers to enter the M2M/IoT market quickly. The following are platform providers for the major U.S.:

Service Provider
Platform Provider
Engagement Year
AT&T
Jasper, Axeda
2009, 2012,
Verizon
Zelitron SA, Qualcomm, nPhase, Axeda
2003, 2010, 2010, 2011
Sprint
Axeda
2010
T-Mobile (now part of Sprint)
Raco Wireless
2006

What kinds of business partnerships have the SPs made with these platform providers? What are the present revenue sharing models and who owns the customers in these scenarios? To what key verticals and monetizable use cases do SPs need to turn their solutions to maximize their profits within these partnerships? For example, what percentage of that monthly revenue of $409 actually goes to the SPs? Can a customer transfer between SP/PP solutions and expect a seamless experience? These are not new questions; however, the issues are still here and need to be explored again with fresh eyes since the technology and market landscape is changing.

For example, virtualization within the core of SPs; networks are giving new agility, efficiency and interoperability choices. Equipment providers such as Ericsson, Alcatel-Lucent, Juniper and Cisco are developing innovative software defined networks- and network fabric virtualization-based appliances in software and hardware to assist SPs in revolutionizing their core OSS/BSS delivery platforms and edge Radio Access Network facilities to rapidly and easily create solutions that can propel the managed M2M/IoT industry forward and fight off over-the-top competition.

What’s the bottleneck? It is not the technology but the ability of the industry to cooperate in normalizing the horizontal layer of the network (actually where the platform providers sit) to serve the verticals appropriately. One of the answers is to urge the standards bodies to more aggressively converge ideas toward this end. OneM2M, the Global Partnership developing standards for M2M communications enabling large-scale implementation of IoT, is in the process of spearheading this effort. However how are they doing with the specification normalization?

In reviewing the OneM2M Technical Report Doc # oneM2M-TR-0003-Architecture_Analysis_Part_2 it is clear that the seven Standards Developing Organizations are well on their way toward integrating a basic framework of functional elements that will prove invaluable in normalizing the playing field. These types of specifications will assist the platform and equipment providers technically so they can clearly see how to design solutions to help the SPs deploy more economical and simpler solutions to the market to effect better results or “outcomes.” The OneM2M 10th Technical Plenary committee met in Berlin, Germany, on 4/11/14 and confirmed that it will be releasing its initial complete specifications for IoT in August 2014.  



Dennis Ward