 Core networks as we know are lying on the inside of wireless network because usually we look we think of wireless networks as the Wireless channel based connectivity But at the back end we have the backhaul connectivity to the core or the IP based infrastructure We are going to look at and understand how self-organizing networks based Enablement allows our core networks to perform better and we are going to look at a specific use case of auto configuration First of all, we know wherever we deploy self-organizing network based Framework this results into improved management. So we are going to replicate the same for core networks as well in in 3gpp guidelines particularly 4g and 5g we had the evolved packet core the evolved packet system involving certain entities This is and since we start off with the in order be talking to the Serving gateway the home subscriber station and the PDN gateway We are looking at essentially the radio and the core networks as well So once we talk about the improvement of management functionality Using son's we are actually looking at an end-to-end mechanism involving both wired and wireless so we look at a specific example of Automatic neighbor relationship based functionality that is neighbor discovery reach ability connectivity We are specifically going to look at how the X2 or the wireless mesh links are established between the in order bees in the evolved packet system through the involvement of the mobility management entity which is at the core of the Evolved packet system Let's take the example of Autoconfiguration we know that hundreds of thousands of in order bees Connect to the mobility management entities these MMEs are since on the core side So this involves if we look at it from the Managed management and administrative perspective perspective the configuration is a very laborious task So how could we possibly involve? son in setting up the the star link s1 between the enote bee and The mobility management entity Let's look at the example here the enote bees which are numerous would be Automatically using son providing their information like their own IDs And the coverage in terms of cells that they have the tracking area to the mobility and entity The mobility management entity provides an IP address to the enote bee through which an entire process can be initiated And it is going to return upon successful configuration unique MME ID that is its own ID the PLMNs which are supported through the MME and the Capacity which is being provisioned to this enote bee Relative to the other enote bees. So this is a simple mechanism of auto configuration with the core entity similarly for automatic neighbor relationship, the MME supports or facilitates the configuration of The x2 interface between enote bees This is very important because Any wrong neighbor selection could cause failure of handover and even The call success probability also goes down So MME essentially acts as a transparent relay from the enote bee source enote bee to the target enote bee So let's look at x2 interface establishment scenario We are going to look at the figure, but we can read it for our convenience so that you would be Having those keywords in your mind afresh once you look at the illustration. So enote bee detects that it has a new neighbor to which the x2 interface could be established which initiates the configuration transfer procedure using Mechanism known as the transport network layer so MME Is going to act as a middle man a middle entity middle man to forward the messages to the target enote bee And upon successful acknowledgement from the target enote bee the source enote bee initiates the TNL establishment procedure and x2 interface is established See here. We have the configuration transfer procedure The signaling process involves we have enote bee one Enote bee two mobility management entity the requesting enote bee sends a request Through the MME since we are talking about self organizing network So the encapsulation is going to be such that MME would not need to do deep packet inspection And it could simply relate depending upon the destination enote bee ID And then it is going to receive the reply from the target enote bee with the transport network layer configuration parameters for the source enote bee And depending upon those parameters Finally in we can see in step number five x2 interface that is a mesh interface is established between source and destination enote bees This reference has also been adopted from Sepohamelanin Nice discussion exists if you are interested in further reading you might like to have a look