The security aspects of each slice can be managed separately, since all slices are logically separate to one another. Some slices may have more stringent security requirements, in which case complete slice isolation may be required in which the slice has exclusive use of dedicated network functions. Any specific security requirements would be use case dependent.
Very good presentation. I have one basic question Does a single UPF instance support multiple network slice or is it dedicated to only one slice(S-NSSAI)?
Just to confirm, a single UPF instance can be part of multiple separate network slice instances and hence supports multiple S-NSSAI. We have several courses on our website, including one on 5G Network Slicing, that provides insight on this topic, if you would like to learn more: www.mpirical.com/courses/5g-network-slicing-updated-2022
@@Mpirical Thank you for the response. If a single UPF instance can be part of multiple Network Slices(S-NSSAI), How does UPF communicates the Slices it supports to SMF or how SMF gets to know the UPF supporting the requested slices? How does UPF manages the QoS requirement per Slices? Are there any parameter which controls the PDRs, FARs per slices(there is optional IE N-SSAI in Session Estab/Modification)? Waiting for your response. Thank you
@@illayarajam900 The UPF is able to register its supported network slices at the NRF, which the SMF can query as part of the UPF discovery process. Alternatively, the SMF can be locally configured with this information. If you would like to know more, you can view and download the covered topic areas in our 5G Network Slicing course here: www.mpirical.com/courses/5g-network-slicing-updated-2022
Cloud is fundamental to the operation of network slicing, since the majority of the 5G Core and elements of the NG-RAN will all be based on cloud technology. This also includes the transport network, which is based on SDN. Cloud provides the flexibility and scalability to handle multiple instances of network slices, all of which can change on a relatively dynamic basis in line with network slice customer requirements.
When network slicing is in operation in the network, PDU sessions are established across them. As such, all the QoS characteristics of a PDU session such as 5QI, ARP, AMBR, GFBR etc all apply within the network slice. It’s worth pointing out that the network slice is established before the PDU sessions start to be established, so the exact QoS profile permissible will also be predefined within the SLA associated with the slice. Moreover, the slice may also support additional aspects of QoS such as high reliability mechanisms for the user and control plane.
Great Presentation! Thank you so much for sharing your valuable knowledge and experience
Thanks for your comment!
Very informative presentation... Good job... Keep up the good work.
Great knowledge. Many thanks
Excellent Presentation! Thank you!
Very good and comprehensive explanation.
Good One..
Succinct and to the point!
Hello thank you for the insight,
my question is how the security is managed between the slices if each have to be isolated?
The security aspects of each slice can be managed separately, since all slices are logically separate to one another. Some slices may have more stringent security requirements, in which case complete slice isolation may be required in which the slice has exclusive use of dedicated network functions. Any specific security requirements would be use case dependent.
@@Mpirical nice! Thank you. Now it's clear 🙏🏿
Very good presentation. I have one basic question Does a single UPF instance support multiple network slice or is it dedicated to only one slice(S-NSSAI)?
Just to confirm, a single UPF instance can be part of multiple separate network slice instances and hence supports multiple S-NSSAI. We have several courses on our website, including one on 5G Network Slicing, that provides insight on this topic, if you would like to learn more: www.mpirical.com/courses/5g-network-slicing-updated-2022
@@Mpirical Thank you for the response. If a single UPF instance can be part of multiple Network Slices(S-NSSAI),
How does UPF communicates the Slices it supports to SMF or how SMF gets to know the UPF supporting the requested slices?
How does UPF manages the QoS requirement per Slices?
Are there any parameter which controls the PDRs, FARs per slices(there is optional IE N-SSAI in Session Estab/Modification)?
Waiting for your response. Thank you
@@illayarajam900 The UPF is able to register its supported network slices at the NRF, which the SMF can query as part of the UPF discovery process. Alternatively, the SMF can be locally configured with this information. If you would like to know more, you can view and download the covered topic areas in our 5G Network Slicing course here: www.mpirical.com/courses/5g-network-slicing-updated-2022
Great presentation 👌
What is or is there any part of cloud in this concept?
Cloud is fundamental to the operation of network slicing, since the majority of the 5G Core and elements of the NG-RAN will all be based on cloud technology. This also includes the transport network, which is based on SDN. Cloud provides the flexibility and scalability to handle multiple instances of network slices, all of which can change on a relatively dynamic basis in line with network slice customer requirements.
Good introduction, thanks!
How is network slicing related to QoS?
When network slicing is in operation in the network, PDU sessions are established across them. As such, all the QoS characteristics of a PDU session such as 5QI, ARP, AMBR, GFBR etc all apply within the network slice. It’s worth pointing out that the network slice is established before the PDU sessions start to be established, so the exact QoS profile permissible will also be predefined within the SLA associated with the slice. Moreover, the slice may also support additional aspects of QoS such as high reliability mechanisms for the user and control plane.
Is there anyway I can contact you. I have series of questions on networking
@@kenzysensei6434 yes, you can contact us via email: enquiries@mpirical.com
Very interesting and well explained