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.

Comments

Popular posts from this blog

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…