System and method configuring a slice profile in a fifth generation network
The present disclosure relates to a communication method and system for converging a 5 th -Generation (5G) communication system for supporting higher data rates beyond a 4 th -Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. Embodiments herein disclose a system and method for configuring slice profile in a Fifth Generation (5G) network. The method comprises determining root slice profile from a Service Profile ( 101 ). Further, generating one or more subnet slice profiles ( 102 ) associated with corresponding one or more network domains of the 5G network from the root slice profile. Furthermore, classifying one or more attributes ( 501 ) in each of the one or more subnet slice profiles ( 102 ) as configurable attributes ( 103 ) or as non-configurable attributes for the corresponding one or more network entities ( 105 ) in the corresponding network domain. Thereafter, providing the one or more attributes ( 501 ) categorized as the configurable attributes ( 103 ) to the corresponding one or more network entities ( 105 ) for enforcing the configurable attributes ( 103 ). Finally, providing the one or more attributes ( 501 ) categorized as the non-configurable attributes to the corresponding one or more OAM entities for enforcing the non-configurable attributes.
1. A method performed by a network slice management service (NSMS) producer in a communication system, the method comprising:
identifying a service profile based on a list of one or more generic network slice template (GST) attributes;
identifying a slice profile for a core network (CN) domain and a slice profile for a radio access network (RAN) domain based on the service profile, wherein the slice profile for the CN domain is used to carry one or more CN domain requirements and the slice profile for the RAN domain is used to carry one or more RAN domain requirements;
translating a CN domain requirement among the one or more CN domain requirements into a configurable parameter related to network function behavior in the CN domain; and
translating a RAN domain requirement among the one or more RAN domain requirements into a configurable parameter related to network function behavior in the RAN domain,
wherein a CN domain requirement not translated into a configurable parameter among the one or more CN domain requirements is kept at operations, administration maintenance (OAM) domain and is used for behavior of a network slice, and
wherein a RAN domain requirement not translated into a configurable parameter among the one or more RAN domain requirements is kept at the OAM domain and is used for behavior of a network slice.
2. The method of claim 1 , wherein identifying the slice profile for the CN domain and the slice profile for the RAN domain further comprising:
identifying one or more transport network (TN) requirements based on the service profile.
3. The method of claim 2 , further comprising:
translating one or more requirements in the service profile into one or more requirements in a root slice profile; and
identifying the slice profile for the CN domain, the slice profile for the RAN domain, and the one or more TN requirements based on the root slice profile.
4. The method of claim 1 ,
wherein a maximum number of UEs in the slice profile for the CN domain is identified based on a maximum number of UEs in the service profile, and
wherein the maximum number of UEs in the slice profile for the CN domain is translated into the configurable parameter related to network function behavior in the CN domain.
5. The method of claim 1 ,
wherein a maximum number of UEs in the slice profile for the RAN domain is identified based on a maximum number of UEs in the service profile,
wherein the maximum number of UEs in the slice profile for the RAN domain is translated into the configurable parameter related to network function behavior in the RAN domain.
6. The method of claim 1 ,
wherein a maximum number of protocol data unit (PDU) sessions in the slice profile for the CN domain is identified based on a maximum number of connections in the service profile, and
wherein the maximum number of PDU sessions in the slice profile for the CN domain is translated into the configurable parameter related to network behavior in the CN domain.
7. The method of claim 1 ,
wherein a key performance indicator (KPI) is associated with a maximum number of PDU sessions of the network slice, and
wherein the KPI is obtained based on successful PDU session establishment procedures of session management functions (SMFs) which are associated with the network slice.
8. A network slice management service (NSMS) producer in a communication system, the NSMS producer comprising:
a transceiver; and
a controller configured to:
identify a service profile based on a list of one or more generic network slice template (GST) attributes,
identify a slice profile for a core network (CN) domain and a slice profile for a radio access network (RAN) domain based on the service profile, wherein the slice profile for the CN domain is used to carry one or more CN domain requirements and the slice profile for the RAN domain is used to carry one or more RAN domain requirements,
translate a CN domain requirement among the one or more CN domain requirements into a configurable parameter related to network function behavior in the CN domain, and
translate a RAN domain requirement among the one or more RAN domain requirements into a configurable parameter related to network function behavior in the RAN domain,
wherein a CN domain requirement not translated into a configurable parameter among the one or more CN domain requirements is kept at operations, administration maintenance (OAM) domain and is used for behavior of a network slice, and
wherein a RAN domain requirement not translated into a configurable parameter among the one or more RAN domain requirements is kept at the OAM domain and is used for behavior of a network slice.
9. The NSMS producer of claim 8 , wherein the controller is further configured to:
identify one or more transport network (TN) requirements based on the service profile.
10. The NSMS producer of claim 9 , wherein the controller is further configured to:
translate one or more requirements in the service profile into one or more requirements in a root slice profile, and
identify the slice profile for the CN domain, the slice profile for the RAN domain, and the one or more TN requirements based on the root slice profile.
11. The NSMS producer of claim 8 ,
wherein a maximum number of UEs in the slice profile for the CN domain is identified based on a maximum number of UEs in the service profile, and
wherein the maximum number of UEs in the slice profile for the CN domain is translated into the configurable parameter related to network function behavior in the CN domain.
12. The NSMS producer of claim 8 ,
wherein a maximum number of UEs in the slice profile for the RAN domain is identified based on a maximum number of UEs in the service profile, and
wherein the maximum number of UEs in the slice profile for the RAN domain is translated into the configurable parameter related to network function behavior in the RAN domain.
13. The NSMS producer of claim 8 ,
wherein a maximum number of protocol data unit (PDU) sessions in the slice profile for the CN domain is identified based on a maximum number of connections in the service profile, and
wherein the maximum number of PDU sessions in the slice profile for the CN domain is translated into the configurable parameter related to network behavior in the CN domain.
14. The NSMS producer of claim 8 ,
wherein a key performance indicator (KPI) is associated with a maximum number of PDU sessions of the network slice, and
wherein the KPI is obtained based on successful PDU session establishment procedures of session management functions (SMFs) which are associated with the network slice.