Network slices are mentioned in almost every line that appears in 5G, but in general their definition is ambiguous. What is the network slicing, and how is it different from the quality of service (QoS) that has existed for many years?
Network slicing is a specific form of virtualization that allows multiple logical networks to run on top of a shared physical network infrastructure. A key advantage of the network slicing concept is that it provides an end-to-end virtual network that includes not only the network but also computing and storage capabilities. The goal is to allow physical mobile network operators to partition their network resources to allow different users (so-called tenants) to reuse a single physical infrastructure. The most frequently cited example in the 5G discussion is sharing a given physical network to run both Internet of Things (IoT), Mobile Broadband (MBB) and very low latency (eg vehicle communication) applications. These applications obviously have very different transmission characteristics. For example, the Internet of Things usually has a lot of devices, but the throughput of each device can be very low. MBB has almost the opposite characteristics because it will have far fewer devices, but each device will send or receive very high bandwidth content. The purpose of network slicing is to be able to partition the physical network at the end-to-end level to achieve optimal traffic grouping, isolate other tenants, and configure resources at the macro level.
The natural question that often arises in technical discussions about network slicing is why existing Internet technologies cannot handle this task? For example, the widely deployed Quality of Service (QoS) architecture is called DiffServ, which is designed to classify and manage different types of IP traffic (eg, voice, video, text) flowing on a given network. There are other well-known technologies, such as virtual private networks (VPNs), which use technologies such as IP tunnels to separate and isolate traffic on the Internet. Moreover, new approaches such as Network Function Virtualization (NFV) are designed to virtualize part of the mobile network. Each of these features obviously overlaps somewhat with the functionality of the 5G network segmentation. So why do we need to introduce network slicing as another way? The answer is twofold. One reason is based on technical issues, and another more important reason is business drivers.
Network sliced ​​commercial driveThe 5G network is expected to bring lucrative new business opportunities to mobile operators and other new entrants. For example, a mobile operator will be able to split its physical network resources into multiple logical slices and lease those fragments to interested parties. Power companies may want to lease network chips for long periods of time to connect smart grids consisting of sensors, meters and controllers, and optimize the slicing of IoT devices. Alternatively, concert promoters may wish to rent network slices for a short period of time, conduct a one-week music festival, and optimize slices for streaming HD music and VoIP connections.
Network slicing will also allow new business models to evolve in the mobile market. For example, existing cloud and data center providers (such as Amazon and Google) may discover new ways to enter mobile network space through network slicing. This will also allow existing mobile operators (such as AT&T, Orange) to lease network slicing and focus on their core strengths, including providing a high quality network experience. This is completely different from today because the current infrastructure cannot be fine-grained and optimized for different MVNOs (tenants). The current MVNO has purely business and billing relationships with network owners and runs their MVNO services through a regular network with unique coverage. Network slicing will allow network owners to customize the computing, storage, and networking capabilities of the infrastructure for a given virtual network operator's traffic characteristics.
Network slicer technology pusherThe key difference in the network slicing approach is that it provides a comprehensive end-to-end virtual network for a given tenant. No existing QoS-based solution can provide such a thing. For example, DiffServ, the most widely deployed QoS solution, can distinguish VoIP traffic from other types of traffic, such as HD video and web browsing. However, differentiated services cannot distinguish and differentiate between the same types of services (eg, VoIP traffic) from different tenants. In addition, DiffServ is unable to perform traffic isolation at all. For example, IoT traffic from health monitoring networks (eg, connecting hospitals and outpatients) often has strict privacy and security requirements, including where data can be stored and who can access it. This cannot be done by DiffServ because it does not have any functionality for handling network computing and storage. All of these discovered DiffServ deficiencies will be handled by the functionality being developed for network slicing.
What happened in the standard?As network slicing will provide exciting business opportunities, standards organizations are working on a number of related technologies. For example, 3GPP is designating an entire Operations and Management (OAM) framework to determine how the owner of the physical network will manage slices as part of its virtualized NFV network. The 3GPP also specifies the signaling and procedures required between the network components and the UE to assign the devices to a given slice.
The Internet Engineering Task Force (IETF) has begun to study how the underlying IP network implements network slicing. As mentioned earlier, there are now protocols like DiffServ and VPN that support network slicing. The IETF is still arguing about what existing or new protocols will be developed for network slicing. The new OAM feature will allow for the definition, creation, deletion, etc. of slices. These slices can extend between management boundaries, which means that slices can span multiple carriers or countries. New traffic engineering features under consideration include possible updates to the underlying network infrastructure such as MPLS, SDN, etc. to allow control signaling for network slicing purposes.
to sum upNetwork slicing is very different from QoS because it enables end-to-end virtual networks with compute, storage, and networking capabilities. Existing QoS methods are point solutions that provide at most a portion of functionality compared to network slicing. Network slicing has generated a lot of interest in the 5G discussion, mainly because it will open many new business opportunities. Network slicing is part of a general trend to make web services more virtual, benefiting from the lower cost and more innovation that the IT industry has turned to the cloud and “everything as a serviceâ€. Network slicing is unlikely to require revolutionary new technology standards. Instead, the required technological changes will be applied to a variety of technologies and standards, all of which focus on improved network intelligence, system integration, key areas of OAM and traffic engineering.
High Frequency Inverter,High Frequency Power Inverter,High Voltage Boost Converter ,Box Inverter
SUZHOU DEVELPOWER ENERGY EQUIPMENT CO.,LTD , https://www.fisoph-power.com