Skip to main content

Next Generation Networks and Grids

This week I attended a meeting at the ITU in Geneva on the topic of Next Generation Networks (NGNs) and Grids. NGNs are developed by the telco industry to provide a range of services over IP networks. The key to their design is the separation of service provision from transport mechanisms. Traffic may be routed over different types of network, each of which provides a common interface. The same traffic may in turn implement all sorts of services, including voice, television, videoconferencing, data transfer, multiplayer games, and whatever application designers come up with in the future.

So NGNs have a virtualised infrastructure providing a range of user services. They are using Web Services technology and are tackling issues such as security (authentication, authorisation, audit), accounting & billing, service description and deployment. Which all sounds familiar from the Grid world. That's what this workshop was about. In particular, it was to investigate opportunites for the ITU (International Telecommunications Union) and the OGF (Open Grid Forum) to work together. Of necessity, much of the time was spent on mutual education - I certainly knew little about NGNs before (although I knew something of BTs incarnation of NGNs, their "21st Century Network").

I was particularly interested in the presentations about Quality of Service (QoS). This is absolutely crucial to NGNs, because different transport mechanisms have different performance characteristics, while different services have different requirements. For example, data services usually demand zero loss of information, while voice can be more relaxed about packet loss provided that enough arrive in time. IPTV has very stringent requirements on both packet loss and arrival time. So the NGN architecture details how QoS requirements can be passed from services to transport mechanisms via a central abstraction.

QoS hasn't received so much attention in the Grid world, but I believe that it will be vital there. Currently Grids are still being installed by experts and used in circumstances where "best effort" performance is satisfactory. (Within a single organisation, "best effort" may be very good quality). There is research that addresses how to specify and establish service-level agreements, but fpr the most part this hasn't been deployed in production grids or entered the standardisation process.

The workshop finished with a discussion of how the ITU and OGF could co-operate on producing standards that address some well-chosen use cases. This seems a potentially valuable partnership. Certainly the ITU can bring expertise in many areas to the Grid world, including audit and accounting. Perhaps the partnership will also advance the state of QoS specification too.


Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:

I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…