Monday, 6 November 2017

Network slicing: everybody has its own view.

It's been a while. I have been reading and trying to grasp the concept of network slicing. Each SDO has its own vision of it and tries to profile the vision according to its interests and expertise.

I think all starts with the NGMN whitepaper that describes the design considerations for 5G networks, having network slicing as a key enabler to make it happen.


It describes the content of the slices, its purpose and the desire that the configuration matches a business purpose. This is very interesting: previous developments in telecommunications had an inverse approach: create something and then find the application, or tweak it for a desired necessity. In here, the business need is established before the creation of a service. This calls for the creation of a flexible enough system that covers the worst case scenario of applicability of the technology, in this case, 5G.

NGMN provides a wishlist of desired capabilities of Network Slicing in order to fulfill the needs of the main use cases proposed for 5G. Establishes the proper definitions to concepts so SDOs, manufacturers and developers can talk in the same language. Doesn't say how, does not specify the technologies or their interaction. It is just a wishlist.

The architectural view is simple:



These three layers resemble the division that most proponents have for their systems: a business entity; an instantiation of that business requirement; and a "place" where everything happens.

In ETSI point of view, they want to leverage on their NFV architectural framework and its management and orchestration scheme, which is pretty solid.
The strong quality of ETSI is that controls the life-cycle of VNF: from the management of the order from the business/operation entity, down to the instantiation in the infrastructure. And these VNFs are constituent parts of the services implemented in a Network Slice. Having control of the life-cycle of the VNFs guarantees a great interaction with ONF’s SDN architecture. A good document to check out is this one.

Now, regarding ONF, their vision on Network Slicing goes along with SDN and its application to 5G. ONF leverages in that relationship to power the association between NFV and SDN to make the slicing concept come to reality. Even though ONF does not talk about slicing inside its definition of the SDN paradigm, the way an SDN controller presents the resources to applications (via NBI) complies with the definition and concept of network slicing. That resource representation that is inside a client context (inside the SDN controller) is similar to the notion of Network Slice depicted by NGMN. Since the network view is focused in the controller, ONF points out that they rely on the APIs exposed to applications and resources in order to receive/deliver orders and commands. A great document that shows this point of view is the TR-526. It would be great to have a standard way to express the requirements to the resource context. Also I think it is necessary to establish a way to perform the segmentation of the resources from the Infrastructure Provider point of view. A standardized way to express those requirements is also desirable. ONF states that they can define and instantiate an end to end slice, but since there is no way (at the moment) to have a full data plane segmentation, this is not entirely true.

3GPP's view is more elaborate: this because it takes possible scenarios, establishes interfaces and entities that would handle the message call flows among them. It is great that leverage on well known procedures such as Attachment request messages to illustrate how an UE would suggest the core network which resources are needed and which network slice is desired. They have the power to talk in those terms since they have been standardizing the way mobile networks operate. Since an UE has requirements to choose a service to connect to, a more elaborate way to express those parameters is needed. This involves more signaling exchange with new entities inside the core network and interactions (not mentioned) with OSS/BSS and MANO entities that would administer the infrastructure and the proper way to deploy the network functions as desired by the business entities. The specification that describes the whole process is 28.801.

I expect that as I continue reading and advancing in the next topics (5G architecture and security) it could be possible to understand the relationship between these three building blocks of my research. This way, I can begin to assess the architecture, spot weaknesses and propose a complete architecture that provides a secure environment to deploy services using network slices in 5G networks. Also I would like to improve my writing style... and there is only one way to do it.

Comments are welcome.

Thursday, 12 October 2017

How to begin?

In order to begin... I got to understand the title of the thesis. Obvious, but got to express it! So, I got to have an understanding of some key concepts:
  • Network Slicing
  • 5G
  • Security
These concepts seem very broad, but by exploring the literature during the State of the Art (SOTA) review, I think I can narrow down the meaning of all of this under the scope of mobile networks. According to my experience and precious reading, I think I would have to revisit concepts from NFV and SDN, as cornerstone for and automatized network.

And well, where to search for information about those concepts? My advisers recommended me to check the main standard development organization (SDO) documents that talk about the subject. Since all of this is under construction, I am sure I will have fun reading all these documentation.

I will focus on 3 SDOs:
  • 3GPP
  • ETSI
  • 5GMN
There is other from 5G Americas, but it will be a bonus "just in case".

As the reading and analysis advances, I will be posting a summary and my point of view on the key concepts.

Tuesday, 10 October 2017

New challenge! Ph.D.

Well, it is time to revisit my blog and start writing again. I think this will be a good exercise, because it will help to relieve from stress, have a way to "talk to myself" and express ideas about the current challenge I am facing. 
As I read somewhere: "if you can't explain it, you don't understand it". So this will be a way to test myself if I am improving the understanding of the topics.

The new challenge refers to my doctoral study about securization of network slices for 5G. The topic is brand-new, with a lot of subtopics to consider. There can be several approaches depending on the background expertise: the radio access network (RAN), the core network (user plane? control plane?) access to services and applications... I think my focus would be in the core network regarding the way in which the network slices are created and the life-cycle management. 

The idea is to begin exploring and start to get a better understanding of the concepts and try to build a road-map in order to not get lost in this quest.

Wednesday, 30 March 2016

Service Availability and Reliability in NFV

Last semester I wrote an interesting article about the problem with service availability and reliability in NFV implementations, with special remark in LTE/EPC environments. It involved a lot of research, and describes the problem that at the moment NFV experiences when dealing with services that need "five nines" availability. The idea is that NFV is not a technology that will solve all the issues about this matter, but needs the help of other protocols, such ans SDN. At the end of the article, I state my point of view about this topic. I hope you enjoy the read.

Sunday, 20 December 2015

Wireless Sensor Networks - intro

Long time, no see.
I am posting the Mind Maps I have made in order to prepare for my exam of Ad-hoc and Sensor Networks. I hope you find it useful.introduction to WSN

Monday, 12 December 2011

My favorite Android Applications

Its been a month I have used my Galaxy S phone. I have installed several Android apps that have helped me with IT related issues. I would like to share this list with you and also have you feedback... maybe you have other useful apps. The list goes as follows:

  1. ConnectBot
  2. CIDR Calculator
  3. Fing
  4. KeePassDroid
  5. SpeedTest.net
  6. rsync
  7. WiEye

What's your favourite app?

Wednesday, 19 October 2011

CCNP-SWITCH: GLBP cheat sheet

This is other layer 3 redundancy protocol, developed by Cisco. This cheat sheet has no commands, it's purpose is to get an understanding of concepts. I hope you all find it useful.


GLBP