Welcome!

Microservices Expo Authors: Pat Romanski, VictorOps Blog, Derek Weeks, Jason Bloomberg, AppDynamics Blog

Blog Feed Post

Will the Concept of Next Generation of Service Composition Networks Revolutionize Telco Market? (Disponible en Español)

NGSON: An Interesting Standardization Effort


When user generated content began to populate the Internet, and to generate the revolution of content related services, researches understood that user generated services could be the next step to continue such service evolution. Over the last decade standardization efforts have emerge to provide answers and architectural models; efforts like TMF SDF, OMA OSE, ATIS SON, ITU NGN SIDE, OPUCE, SOA and SPICE, can be considered as the more relevant. Recently the IEEE WG P1903 was created to develop the concept of NGSON (Next Generation of Service Overlay Networks), a previous concept, SON (Service Overlay Network), was formulated with the intention to integrate service aware1 technologies created by SOA and delivered over multiple networks using SDP, but the concept lacked some critical features like continuity of the service over multiple networks, or the presentation of content over different devices, considering multiple and diverse contexts of environments. NGSON promises that these features are going to be included, so is natural to think that this new architectural model can revolutionize the way that today the industry develops and delivers the service over Telecommunications networks, this concept can be conceived as a big umbrella that not only integrates service aware models but also will allow the Telcos through the use of a powerful network scheme to provide the first truly pervasive service. The convergence of services, models and technologies in Telecommunications has been well criticized in the past, is obvious that adoption of convergence models hasn’t been massive or enthusiastic; can this new concept become the answer for Telcos seeking to keep services converging over their roof?

 

NGSON Brings To the Table…

10-9-12 image.jpg

Image courtesy of Paola Buelvas ([email protected])


This concept can be thought as extra layer between the service and the network that today Telcos use to deliver service. What really calls the attention is that it allows the service provider to extend beyond its own network infrastructure to reach different networks, contents and even users. NGSON also includes three advance functionalities; Context Awareness, Dynamic Adaptation and Self-Organization. Context Awareness is a key tool for the service realization, it allows the network to evaluate the situational context of the user in multiple dimensions these being: the service, the user, the device and the network. The Dynamic Adaptation will allow the service to transcend beyond networks and devices (Total mobility) ensuring continuity. Self-Organization ensures that internal resources configuration of this new layer can adapt autonomously imitating the proved principle of resilience from the Internet. But what can you do with it? This architectural concept is divided in several layers and functions, investigation efforts and proof of concepts so far have focused on: User created service; the user choses from a list of services, those he wishes to be combined and delivered without having deep SW or telecommunication knowledge. As an option to provide temporal content storage and optimization functions providing core traffic offloading capabilities through its specialized layer that interfaces with the traditional transport networks. It also has been conceived as an option to aggregate Cloud computational resources. Finally, what I consider the one that generates more expectative is the possibility to provide a truly pervasive service; your identity, applications, contacts and preferences everywhere, in all your devices and without interruption.

 

The Technical Challenges Today

 

This effort is just starting and a lot remain to be done, given the current state of the art, the following challenges and work ahead needs to be considered to count with a complete technical proposal:

 

  1. Context Awareness feature must be used for traffic optimization delivery, P2P concepts can be integrated to optimize traffic movement through the network.
  2. The protocols to be executed in the different interfaces still unknown, but have to be compatible with the current service technologies in place.
  3. The layer that interfaces with the current Telco networks called the Delivery control plane hasn’t been completely developed; several issues and complexity definitions remain to be known.
  4. QoS transparently support is required throughout the different interfaces and layers of the model, needless to say how challenging this might be in some networks.
  5. Easy integration with Telco networks; the interconnection not only has to be possible, but has to be simple and very fast to deploy.

 

The Problems of the Past Could be Problems of Today

 

The industry has tried through different approaches to regain the user attention lost against the Internet content providers, the barriers of adoption faced by those different approaches are well known, let me summarize those barriers that I can recognize for NGSON and contrast it against its objectives and architecture definition:

 

  1. Failure to attract critical mass of applications developers for the Telecom service: The NGSON through its Service control layer that includes discovery, integration composition and routing seem to address this issue, but again without knowing the complexity definitions and compatibility with existing service platforms it’s difficult to forecast the success.
  2. Complexity of the model or service architecture: there are several dimensions of complexity to consider; for the model itself, for application developers, for integration with the existent service technologies, complexity to commercialize the model and to integrate it to the network of Telcos. Although the model seems to be realizable and simple enough at a high level to provide planning for growing and maintenance activities, the current information makes it hard to conclude if complexity will ruin the party.
  3. Compatibility: The dimensions to be compatible with are; current content providers and service platforms. Control protocols and signaling schemes both for user content delivery and control of resources and coordination among functional entities. Within current transport networks, again the communication protocols play a key role; it must also consider the negotiation of capabilities and resources for all possible transport networks. For this consideration NGSON implements in a separate way, a control plane for the service, another plane for unified signaling control and a different one for control of the media bearers, this is definitely one of the strongest points of this functional architecture.
  4. Time to market: When talking about adoption of new network infrastructure for service delivery (e.g WCDMA or LTE) is quite understandable that Telcos take their time, and even desirable that standardization bodies also pace their work. But when talking about the service creation infrastructure, time is a critical factor, if there isn’t a quick path of release and availability, the whole concept can be invalidated by a new service paradigm developed by industries less bound by convergence and complexity. NGSON doesn’t count with any advantages here.
  5. Services/Applications/Hooks: It has been proved that Telcos normally do not “nailed it”, when it comes to service creation, so this time around collaborative efforts must be convened, Internet innovators, young developers, content giants and groups of users must be called to make part of the service layer planning department. As usual, it seems very hard to find real collaborative efforts for NGSON, and no initiative is well known and strong enough to be taken into account for existing service aware technologies.

 

One of the main objectives of NGSON is to beneficiate, Content providers, Service Providers and users, the problem is that there seems to be a gap between the concept development and the communication of value to the possible key stakeholders, someone in the industry should bridge this gap.

 

What should the Industry do  to Ensure Success?

 

Considering the huge potential this concept holds to provide the jump towards a new type of service for Telecommunication companies, and as a fan of technology, a professional of the industry and as a plain user, in my opinion this should the action plan for the industry:

 

  • Take full advantage of advance features, this means in the short term, integrating under the technical functional concepts of EPC 4G, the various access technologies available, considering that one access technology would not reach as many users as all of them combined.
  • Cannot be timid when it comes to displaying the capabilities of the architecture, in other words Telcos must give away the power of service creation to those who can execute it to the best this concept can provide.
  • Industry must take the risk, different economy indicators are not favorable for Telcos anymore, ARPU continue to decline, and network usage spikes beyond reasonable network growing, It’s time!
  • I’m not sure if everyone is convinced about services created by the user, but if the industry really believes that this could be the evolution path of the service, we need to start generating information about it, to explain it in a different way, the commercial conditions must be properly set.

 

I see this concept as an interesting opportunity that will provide the Telcos enough arguments for the first time to give away the control of service offering, ensuring economic survival and at the same time evolving towards the next phase of services.

 

Final Remarks


So rephrasing the question that frames this blog: Would the new concept of service creation really revolutionize the industry? To the best of my understanding the NGSON is a well-conceived technical concept that overcomes several flaws of early approximations, has all the necessary components to be innovative and to become successful.

 

But, the cold truth is that still a lot of work to be done, various barriers faced by unified frameworks in the past still present today, industry leaders remain distant to the need of a new approach to the service, in other words innovators roles that could take us the next level remain vacant. In conclusion is a very interesting concept with huge potential, which has to overcome several non-trivial challenges but still have some time to accomplish its objective. As a user and fan of Telecommunications I really would like to see the realization of the service as promised by this interesting effort.

 

For more, follow me, @jomaguo

 

Read this post in Spanish

 

  1. The concept of service awareness is a paradigm that conceives the service composition through high level functional blocks that abstract the complexity of lower transport and delivery layers

 

Read the original blog entry...

More Stories By Deborah Strickland

The articles presented here are blog posts from members of our Service Provider Mobility community. Deborah Strickland is a Web and Social Media Program Manager at Cisco. Follow us on Twitter @CiscoSPMobility.

@MicroservicesExpo Stories
Much of the value of DevOps comes from a (renewed) focus on measurement, sharing, and continuous feedback loops. In increasingly complex DevOps workflows and environments, and especially in larger, regulated, or more crystallized organizations, these core concepts become even more critical. In his session at @DevOpsSummit at 18th Cloud Expo, Andi Mann, Chief Technology Advocate at Splunk, will show how, by focusing on 'metrics that matter,' you can provide objective, transparent, and meaningfu...
Last week I had the pleasure of speaking on a panel at Sapphire Ventures Next-Gen Tech Stack Forum in San Francisco. Obviously, I was excited to join the discussion, but as a participant the event crystallized not only where the larger software development market is relative to microservices, container technologies (like Docker), continuous integration and deployment; but also provided insight into where DevOps is heading in the coming years.
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
In a crowded world of popular computer languages, platforms and ecosystems, Node.js is one of the hottest. According to w3techs.com, Node.js usage has gone up 241 percent in the last year alone. Retailers have taken notice and are implementing it on many levels. I am going to share the basics of Node.js, and discuss why retailers are using it to reduce page load times and improve server efficiency. I’ll talk about similar developments such as Docker and microservices, and look at several compani...
Admittedly, two years ago I was a bulk contributor to the DevOps noise with conversations rooted in the movement around culture, principles, and goals. And while all of these elements of DevOps environments are important, I’ve found that the biggest challenge now is a lack of understanding as to why DevOps is beneficial. It’s getting the wheels going, or just taking the next step. The best way to start on the road to change is to take a look at the companies that have already made great headway ...
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
From the conception of Docker containers to the unfolding microservices revolution we see today, here is a brief history of what I like to call 'containerology'. In 2013, we were solidly in the monolithic application era. I had noticed that a growing amount of effort was going into deploying and configuring applications. As applications had grown in complexity and interdependency over the years, the effort to install and configure them was becoming significant. But the road did not end with a ...
I have an article in the recently released “DZone Guide to Building and Deploying Applications on the Cloud” entitled “Fullstack Engineering in the Age of Hybrid Cloud”. In this article I discuss the need and skills of a Fullstack Engineer with relation to troubleshooting and repairing complex, distributed hybrid cloud applications. My recent experiences with troubleshooting issues with my Docker WordPress container only reinforce the details I wrote about in this piece. Without my comprehensive...
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
Small teams are more effective. The general agreement is that anything from 5 to 12 is the 'right' small. But of course small teams will also have 'small' throughput - relatively speaking. So if your demand is X and the throughput of a small team is X/10, you probably need 10 teams to meet that demand. But more teams also mean more effort to coordinate and align their efforts in the same direction. So, the challenge is how to harness the power of small teams and yet orchestrate multiples of them...
Many private cloud projects were built to deliver self-service access to development and test resources. While those clouds delivered faster access to resources, they lacked visibility, control and security needed for production deployments. In their session at 18th Cloud Expo, Steve Anderson, Product Manager at BMC Software, and Rick Lefort, Principal Technical Marketing Consultant at BMC Software, will discuss how a cloud designed for production operations not only helps accelerate developer...
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
In the world of DevOps there are ‘known good practices’ – aka ‘patterns’ – and ‘known bad practices’ – aka ‘anti-patterns.' Many of these patterns and anti-patterns have been developed from real world experience, especially by the early adopters of DevOps theory; but many are more feasible in theory than in practice, especially for more recent entrants to the DevOps scene. In this power panel at @DevOpsSummit at 18th Cloud Expo, moderated by DevOps Conference Chair Andi Mann, panelists will dis...
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.