Methods and systems for selection of network slice and network function in wireless communication network

Abstract

The present disclosure provides techniques for selection of a network slice (NS) and a network function (NS) in a wireless communication network. The method comprises receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices. The method further comprises analysing a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices. The method also comprises transmitting the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.

Description

METHODS AND SYSTEMS FOR SELECTION OF NETWORK SLICE AND NETWORK FUNCTION IN WIRELESS COMMUNICATION NETWORK

[0001] The present disclosure generally relates to the field of wireless communication networks, and more particularly, relates to methods and systems for selection of network slice (NS) and network function (NF) in a wireless communication network.

[0002] Communication networks enabled by technologies such as network function virtualization (NFV), and software-defined networking (SDN) may be flexibly organized to serve various customer demands. In building advanced networks, network slicing provides the ability to create isolated virtual networks over which different traffic flows can travel. The network slicing provides flexibility and adaptability in the characteristics of each slice. This allows the network slices (NSs) to each have characteristics tailored to the specific needs of different services. This allows a plurality of different services to be supported by a single pool of network infrastructure. Fig. 1 illustrates a process of a NS selection, in accordance with prior art. As shown in Fig. 1, a consumer NF (e.g. Access and Mobility Management Function (AMF)) 101 sends an NS query request 105 to a Network Slice Selection Function (NSSF) 103. Accordingly, the consumer NF 101 receives a response message (msg) 107 from the NSSF 103. The response msg 107 includes a list of one or more candidate NSs. The consumer NF 101 selects the candidate NS, i.e., NS1 from the candidate list, for example, in a round-robin fashion. However, the consumer NF 101 relies on local implementation to select a slice from the candidate list, such as using a round-robin method, without taking into account key performance indicators (KPIs) of the corresponding network slice (NS). This can lead to the selection of an NS with a poor KPI. For example, the selected candidate NS1 has a call success rate of 80% whereas another NS, i.e., NS3 has a higher call success rate of 99%. As a consequence, there may be multiple NSs with similar KPIs and a few with lower ones. However, a lower KPI NS could still be selected, potentially disrupting incoming calls. This selection could cause the already declining service level agreement (SLA) to deteriorate even further.

[0003] Further, the 3rd Generation Partnership Project (3GPP) has defined a 5G core architecture that allows for automated network function (NF) and service discovery and selection. A consumer NF can query a Network Repository Function (NRF) using the NRF discovery service, where the query can include various attribute-value pairs that the NRF uses to find and filter matching database entries related to the network functions. Fig. 2 illustrates a process of network function selection, in accordance with prior art. As shown in Fig. 2, the consumer NF, such as Session Management Function (SMF) 201, sends a discovery query 205 to the NRF 203 and receives a discovery response 207 from the NRF 203. The discovery response includes a list of one or more candidate NFs. The NRF 203 selects the candidate NFs, e.g., NF1, based on a round-robin fashion. However, the consumer NF 201 relies on local implementation to select an NF from the candidate list, such as using a round-robin method, without taking into account key performance indicators (KPIs) of the corresponding NF. This can lead to the selection of an NF with a poor KPI. For example, the selected candidate NF1 has a throughput of 80% whereas another NF, i.e., NF3 has a higher throughput of 99%. As a consequence, there may be multiple NFs with similar KPIs and a few with lower ones. However, a lower KPI NF could still be selected, resulting in the selection of an erroneous NF and a reduction in NF / service downtime due to the continuous inflow of calls to the erroneous NF. This selection could cause the already declining SLA to deteriorate even further.

[0004] Hence, existing NF and NS selection techniques fail to consider the performance of the NFs and NSs before making a selection. This can result in the selection of suboptimal NFs or less efficient NSs, leading to KPI degradation across the system and a poorer user experience.

[0005] Therefore, there is a requirement to provide improved techniques that can overcome the above-mentioned problems and limitations associated with the selection of the network slice and network function.

[0006] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the invention. This summary is neither intended to identify key or essential inventive concepts of the invention nor is it intended for determining the scope of the invention.

[0007] According to one embodiment of the present disclosure, a method for selection of a network slice is disclosed. The method comprises receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices. The method further comprises analysing, by a first network function, a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices. The method also comprises transmitting, by the first network function, the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.

[0008] According to another embodiment of the present disclosure, a method for selection of a network slice is disclosed. The method comprises transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network slices. The method further comprises receiving, by a second network function, the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices. The method also comprises comparing, by the second network function, each of the performance metric with other remaining performance metrics and selecting, by the second network function, the network slice from the plurality of network slices based on the comparison.

[0009] According to one embodiment of the present disclosure, a method for selection of a network function is disclosed. The method comprises receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network functions. The method further comprises analysing, by a first network function, a plurality of parameters associated with each of the plurality of network functions to determine the performance metric corresponding to each of the plurality of network functions. The method also comprises transmitting, by the first network function, the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions.

[0010] According to another embodiment of the present disclosure, a method for selection of a network function is disclosed. The method comprises transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network functions. The method further comprises receiving, by a second network function, the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions. The method also comprises comparing, by the second network function, each of the performance metric with other remaining performance metrics and selecting, by the second network function, the network function from the plurality of network functions based on the comparison.

[0011] According to another embodiment of the present disclosure, a system for selection of a network slice is disclosed. The system comprises a memory and a processor coupled to the memory. The processor is configured to receive, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices. The processor is further configured to analyse a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices. The processor is furthermore configured to transmit the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.

[0012] According to another embodiment of the present disclosure, a system for selection of a network slice is disclosed. The system comprises a memory and a processor coupled to the memory. The processor is configured to transmit, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network slices. The processor is further configured to receive the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices. The processor is furthermore configured to compare each of the performance metric with other remaining performance metrics and select the network slice from the plurality of network slices based on the comparison.

[0013] According to another embodiment of the present disclosure, a system for selection of a network function is disclosed. The system comprises a memory and a processor coupled to the memory. The processor is configured to receive, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network functions. The processor is further configured to analyse a plurality of parameters associated with each of the plurality of network functions to determine the performance metric corresponding to each of the plurality of network functions. The processor is furthermore configured to transmit the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions.

[0014] According to another embodiment of the present disclosure, a system for selection of a network function is disclosed. The system comprises a memory and a processor coupled to the memory. The processor is configured to transmit, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network functions. The processor is further configured to receive the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions. The processor is furthermore configured to compare each of the performance metric with other remaining performance metrics and select the network function from the plurality of network functions based on the comparison.

[0015] To further clarify the advantages and features of the present invention, a more particular description of the invention will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail in the accompanying drawings.

[0016] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:

[0017] Fig. 1 illustrates a process of a network slice (NS) selection, in accordance with prior art;

[0018] Fig. 2 illustrates a process of network function (NF) selection, in accordance with prior art;

[0019] Fig. 3 illustrates an exemplary architecture of a wireless communication network, in accordance with an embodiment of the present disclosure;

[0020] Fig. 4a illustrates a flow diagram depicting a method for selection of the network slice , in accordance with an embodiment of the present disclosure;

[0021] Fig. 4b illustrates a signal flow diagram depicting a selection of the network slice, in accordance with an embodiment of the present disclosure;

[0022] Fig. 5 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for NS selection, in accordance with a first embodiment of the present disclosure;

[0023] Fig. 6 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for NS selection, in accordance with a second embodiment of the present disclosure;

[0024] Fig. 7a illustrates a flow diagram depicting a method for selection of the network slice, in accordance with an embodiment of the present disclosure;

[0025] Fig. 7b illustrates a signal flow diagram depicting a selection of the network slice, in accordance with an embodiment of the present disclosure;

[0026] Fig. 8 illustrates a signal flow diagram depicting communication between an AMF and a NSSF for NS selection, in accordance with an embodiment of the present disclosure;

[0027] Fig. 9a illustrates a flow diagram depicting a method for the selection of the network function, in accordance with an embodiment of the present disclosure;

[0028] Fig. 9b illustrates a signal flow diagram depicting a selection of the network function, in accordance with an embodiment of the present disclosure;

[0029] Fig. 10 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for selection of the NF, in accordance with a first embodiment of the present disclosure;

[0030] Fig. 11 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for NF selection, in accordance with a second embodiment of the present disclosure;

[0031] Fig. 12a illustrates a flow diagram depicting a method for the selection of the network function, in accordance with an embodiment of the present disclosure;

[0032] Fig. 12b illustrates a signal flow diagram depicting a selection of the network function, in accordance with an embodiment of the present disclosure;

[0033] Fig. 13 illustrates a signal flow diagram depicting communication between an SMF and a NRF for NF selection, in accordance with an embodiment of the present disclosure; and

[0034] Fig. 14 illustrates a block diagram of a system for selection of the network slice and the network function in the wireless communication network, in accordance with an embodiment of the present disclosure.

[0035] Further, skilled artisans will appreciate that elements in the drawings are illustrated for simplicity and may not have necessarily been drawn to scale. For example, the flow charts illustrate the method in terms of the most prominent steps involved to help to improve understanding of aspects of the present invention. Furthermore, in terms of the construction of the system, one or more components of the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0036] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to the embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated system, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur to one skilled in the art to which the invention relates.

[0037] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are explanatory of the invention and are not intended to be restrictive thereof.

[0038] Reference throughout this specification to "an aspect", "another aspect" or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0039] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such process or method. Similarly, one or more devices or sub-systems or elements or structures or components proceeded by "comprises... a" does not, without more constraints, preclude the existence of other devices or other sub-systems or other elements or other structures or other components or additional devices or additional sub-systems or additional elements or additional structures or additional components.

[0040] The term "couple" and the derivatives thereof refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms "transmit", "receive", and "communicate" as well as the derivatives thereof encompass both direct and indirect communication. The term "or" is an inclusive term meaning "and / or". The phrase "associated with," as well as derivatives thereof, refer to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term "controller" refers to any device, system, or part thereof that controls at least one operation. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C, and any variations thereof. As an additional example, the expression "at least one of a, b, or c" may indicate only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof. Similarly, the term "set" means one or more. Accordingly, the set of items may be a single item or a collection of two or more items.

[0041] The present disclosure discloses techniques for selecting a network slice (NS) and a network function (NF) in a wireless communication network, such as 5G, 6G networks. In an embodiment, performance parameters of the NS and NF are considered in NS and NF selection, respectively. Fig. 3 illustrates an exemplary architecture of a wireless communication network, in accordance with an embodiment of the present disclosure. As shown in Fig. 3, in an exemplary embodiment, the wireless communication network 300 may comprise a plurality of network functions (NFs), such as a Network Data Analytics Function (NWDAF) 301a, a NSSF 301b, and a NRF 301c, which are connected to an Access and Mobility Management Function (AMF) 303 and a Session Management Function (SMF) 305. The AMF 303 is in communication with a user equipment (UE) 307 via an N1 interface. The AMF 303 is also in communication with an access network (AN) 309 via an N2 interface. The AN 309 is in communication with a user plane function (UPF) 311 via an N3 interface and the UPF 311 is in communication with the SMF 305 via an N5 interface. The SMF 305 is also in communication with a data network (DN) 313 via an N6 interface. In an embodiment, the AMF 303 may select a network slice (NS) among a plurality of NSs based on a performance metric corresponding to each of the plurality of NSs received from the NWDAF 301a. Similarly, the SMF 305 may select a network function (NF) among a plurality of NFs based on a performance metric corresponding to each of the plurality of NFs received from the NWDAF 301a. The disclosed techniques are further explained in detail with respect to Figs. 3-14.

[0042] Exiting Slice and NF selection methodologies does not involve checking of the performance of the Slice / NF before selecting them. This may lead into a erroneous NF or a sub-optimal / less-KPI Slice being selected, which results KPI degradation of overall system and poor experience to the users. The disclosure describes introduction of performance parameters in Slice and NF selection in 5GC. This shall improve the overall quality of experience to the UE and also the better the system performance in long run. Based on consideration of the performance factor of the Slice and NF while already considering other factors before selecting it, the system performance may be improved.

[0043] Fig. 4a illustrates a flow diagram depicting a method 400 for the selection of the network slice, in accordance with an embodiment of the present disclosure. Fig. 4b illustrates a signal flow diagram depicting a selection of the network slice, in accordance with an embodiment of the present disclosure. Figs. 4a and 4b have been explained in conjunction with each other.

[0044] In an embodiment, the method as described in reference to Fig. 4a may be performed by a first network function. As shown in Fig. 4a, at step 401, the method 400 may include receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices. In an embodiment, the first network function is a Network Data Analytics Function (NWDAF), such as NWDAF 301a and the second network function is one of an Access and Mobility Management Function (AMF), such as AMF 303, and a Network Slice Selection Function (NSSF) 301b. Accordingly, in an embodiment, the NWDAF 301a may receive the request from the AMF 303 or the NSSF 301b.

[0045] Fig. 5 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for NS selection, in accordance with a first embodiment of the present disclosure. For example, the first network function corresponds to a NF service consumer (e.g., AMF 303) and the second network function corresponds to a NWDAF 301a. Hereinafter, the NF service consumer is described as an AMF, but the embodiments of the present disclosure are not limited thereto. Features regarding Query API (e.g., NWDAF AnalyticsInfo_Request Service API) call for new analytics "Slice Performance" are described as the following descriptions.

[0046] In a first embodiment, the NWDAF 301a may receive the request in a request message, i.e., Nwdaf_AnalyticsInfo_Request message, after expiry of a predefined timer, i.e., NWDAF_Query_Timer, as shown in Fig. 5. The predefined timer is associated with the request in the second network function, i.e., the AMF 303 or the NSSF 301b. Accordingly, the AMF 303 or the NSSF 301b may request the NWDAF 301a after the expiry of the NWDAF_Query_Timer, as shown at operation 404 of Fig. 4b. In an embodiment, the predefined timer may be configured by the second network function. As shown in Fig. 5, the request message may include a query, i.e., Slice performance. Accordingly, a parameter EventID of the request may be set to "slice performance". Accordingly, in an embodiment, the NWDAF 301a supports a new EventID (SLICE_PERFORMACE) in "EventId" in the Nnwdaf_AnalyticsInfo request body, as shown in Table 1:

[0047] EnumerationDescriptionApplicability...SLICE_PERFORMANCERepresents the analytics of network slice performance informationSlice_Performance

[0048] An exemplary format of the new EventID is shown in Table 2:

[0049] Enumeration valueDescriptionNF_LOADIndicates that the event subscribed is NF Load.SLICE_PERFORMANCEIndicates the KPI of the network sliceQOS_SUSTAINABILITYIndicates that the event subscribed is QoS sustainability.SLICE_LOAD_LEVELIndicates that the event subscribed is load level information of Network SliceSERVICE_EXPERIENCEIndicates that the event subscribed is a service experience.UE_MOBILITYIndicates that the event subscribed is UE mobility information.UE_COMMIndicates that the event subscribed is UE communication information....SM_CONGESTIONIndicates the Session Management Congestion Control Experience information for specific DNN and / or S-NSSAI.

[0050] Accordingly, in an embodiment, the request includes a plurality of slice attributes indicating information related to the plurality of network slices and the plurality of slice attributes include SLICE_PERFORMANCE. For the table 1 and the table 2, "3GPP TS 29.520 Table 5.1.6.3.4-1: Enumeration EventId" may be referred.

[0051] As shown in Fig. 5, the NWDAF 301a may transmit response messages, i.e. "Nwdaf_AnalyticsInfo_Request response" or "no content" response to the AMF 303 or the NSSF 301b in response to the Nwdaf_AnalyticsInfo_Request message, as shown at operation 406 of Fig. 4b. If no slice instances can be found for the requested slice selection information, then the NWDAF 301a returns a "204 no content" response. However, if the slice instances for the requested slice selection information have been found then the NWDAF 301a returns a "Nwdaf_AnalyticsInfo_Request response" message. In an embodiment, the response message "Nwdaf_AnalyticsInfo_Request response" may include the requested performance metric. The response message "Nwdaf_AnalyticsInfo_Request response" is further discussed in detail in response to step 403.

[0052] Fig. 6 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for NS selection, in accordance with a second embodiment of the present disclosure. For example, the first network function corresponds to a NF service consumer (e.g., AMF 303) and the second network function corresponds to a NWDAF 301a. Hereinafter, the NF service consumer is described as an AMF, but the embodiments of the present disclosure are not limited thereto. Features regarding subscription and notification API (e.g., NWDAF EventsSubscription_Subscribe and Notify Service API) for new analytics "NF Performance" are described as the following descriptions.

[0053] In a second embodiment, the NWDAF 301a may receive the request in a subscription message in an event of subscription of the performance metric by the second network function, as shown in Fig. 6. Particularly, if the AMF 303 or the NSSF 301b has subscribed with the NWDAF 301a to receive the performance metric, then the NWDAF 301a may transmit the performance metric periodically based on the subscription. In an exemplary embodiment, the NWDAF 301a may receive such a request in a Nnwdaf_EventsSubscription message, as shown at operation 408 of Fig. 4b. As shown in Fig. 6, the request message may include a query, i.e., Slice performance. Accordingly, a parameter EventID of the request may be set to "slice performance". Accordingly, in an embodiment, the NWDAF 301a supports a new Event (SLICE_PERFORMACE) in "NwdafEvent" in the Nwdaf_EventSubscription_Subscribe message body, as shown in Table 1. An exemplary format of the new EventID is shown in Table 2. Further, in an embodiment, the NWDAF 301a supports reporting of the new attribute (NssType) in "EventSubscription" in the Nnwdaf_EventsSubscription_Subscribe message body. Further, as shown in Fig. 6, the NWDAF 301a may transmit a response message, i.e. "Nnwdaf_EventsSubscription Notify" or "no content" response to the AMF 303 or the NSSF 301b in response to the Nnwdaf_EventsSubscription message, as shown at operation 410 of Fig. 4b. If no slice instances can be found for the requested slice selection information, then the NWDAF 301a returns a "204 no content" response. However, if the slice instances for the requested slice selection information have been found then the NWDAF 301a returns a "Nnwdaf_EventsSubscription Notify" response message. In an embodiment, the response message "Nnwdaf_EventsSubscription Notify" may include the requested performance metric. The response message "Nnwdaf_EventsSubscription Notify" is further discussed in detail in response to step 403.

[0054] In a further embodiment, the second network function, i.e., the AMF 303 or the NSSF 301b may unsubscribe from event notifications using a Nnwdaf_EventsSubscription_Unsubscribe service message. Accordingly, in an embodiment, the NWDAF 301a supports a new Event (SLICE_PERFORMACE) in "NwdafEvent" in the Nwdaf_EventSubscription_Unsubscribe message body, as shown in Table 1.

[0055] Referring back to Fig. 4a, at step 403, the method 400 may include analysing a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices. In an embodiment, the NWDAF 301a may receive the plurality of parameters associated with each of the plurality of network slices from an Operations Administration and Maintenance (OAM) sub-system, as shown at operation 402 of Fig. 4b. Thereafter, the NWDAF 301a may analyse the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network slices. In an exemplary embodiment, the NWDAF 301a may analyse the received plurality of parameters using an artificial intelligence (AI) model. In an embodiment, the plurality of parameters may include a success ratio of a plurality of call processing procedures, a load parameter, a fault parameter, a transaction rate, a throughput, a call drop rate, an alarm parameter, and a call fail parameter. The success ratio of a plurality of call processing procedures refers to a ratio of attempt to completion counts of a call processing procedure, e.g.., Registration, Packet Data Unit (PDU) Session Establishment, etc., of the NS. The load parameter refers to a dynamic load of the NS e.g., CPU load, Memory load, etc. The fault parameter refers to faults generated on the NS, e.g. Disk Fail, NS out of Service, etc. The transaction rate refers to a rate of call, i.e., transaction in units of time per NS considering the total number of UEs, and PDU Sessions. The call drop rate refers to the measurement of call drops, i.e., the number of call drops over a period of predefined time period. The predefined time period may be configured by the NWDAF 301a. The alarm parameter refers to real-time or non-real-time events, e.g., congestion or load crossing set threshold, etc. The call fail parameter refers to the reason for the call fail, e.g., timeouts of diameter, SBI interface, etc.

[0056] In an embodiment, the performance metric may include a plurality of performance attributes indicating a key performance indicator (KPI) value of a corresponding network slice among the plurality of network slices, a time stamp associated with the KPI value, a confidence score associated with the KPI value, and status information of the corresponding network slice. Further, the plurality of performance attributes may include an identification of single network slice selection assistance information (Snssai), information related to the network slice instance, identification of the network slice instance, availability status of the network slice, dynamic slice performance information, time stamp of calculation of the KPI, and confidence. In an embodiment, the performance metric may be included in the "Nwdaf_AnalyticsInfo_Request response" message. An exemplary format of the "Nwdaf_AnalyticsInfo_Request response" message is shown in Table 3:

[0057]

[0058] For the table 3 of the first embodiment in FIG. 5, "3GPP TS 29.520 Table 5.2.6.2.2-1: Definition of type AnalyticsData" may be referred. For the table 3 of the second embodiment in FIG. 6, "3GPP TS 29.520 Table 5.1.6.2.5-1: Definition of type EventNotification" may be referred.

[0059] For example, the Attributes of the parameter "nsiPerformanceInfos" of the "Nwdaf_AnalyticsInfo_Request response" message is shown in Table 4:

[0060]

[0061] In another embodiment, the performance metric may be included in the "Nnwdaf_EventsSubscription Notify" message. An exemplary format of the "Nnwdaf_EventsSubscription Notify" message is shown in Table 5.

[0062]

[0063] The parameter "nsiPerformanceInfos" of the "Nnwdaf_EventsSubscription Notify" message is the same as shown above in Table 4.

[0064] Referring to Fig. 4a, at step 405, the method 400 may include transmitting the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices. As discussed above, the NWDAF 301a may transmit the performance metric corresponding to each of the plurality of network slices in a response message corresponding to the request message. The selection of the network slice is further explained in reference to Figs. 7a and 7b, which have been explained in conjunction with each other.

[0065] Fig. 7a illustrates a flow diagram depicting a method for the selection of the network slice, in accordance with an embodiment of the present disclosure. In an embodiment, the method as described in reference to Fig. 7a may be performed by a second network function. As shown in Fig. 7a, at step 701, the method 700 may include transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network slices, as shown at operations 704, 708 of Fig. 7b. It should be noted that the first network function may receive the request in accordance with techniques as discussed in reference to Fig. 4a. As discussed in reference to Fig. 4a, the first network function may be the NWDAF 301a, and the second network function may be one of the AMF 303 and the NSSF 301b. Then, at step 703, the method 700 may include receiving the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices, as shown at operations 706, 710 of Fig. 7b. In an embodiment, the NWDAF 301a may receive the plurality of parameters associated with each of the plurality of network functions from an Operations Administration and Maintenance (OAM) sub-system, as shown at operation 702 of Fig. 7b. Thereafter, the NWDAF 301a may analyse the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network functions. In an embodiment, the AMF 303 or the NSSF 301b may receive the performance metric from the NWDAF 301a in accordance with techniques discussed in reference to Fig. 4a, the description of which is not repeated for the sake of brevity of the disclosure. Thereafter, at step 705, the method 700 may include comparing each of the performance metrics with other remaining performance metrics. Then, at step 707, the method 700 may include selecting the network slice from the plurality of network slices based on the comparison. In an exemplary embodiment, let us assume that the AMF 303 or the NSSF 301b has received the performance metric for three NSs, i.e., NS1, NS2, and NS3. The performance metrics of NS1, NS2, and NS3 indicate a KPI value of 8 with a confidence of 90, a KPI value of 9 with a confidence of 60, and a KPI value of 70 with a confidence of 75, respectively. Accordingly, in an exemplary embodiment, the AMF 303 or the NSSF 301b may compare the performance metrics of NS1, NS2, and NS3 and may select the NS1 due to higher confidence. In another exemplary embodiment, the AMF 303 or the NSSF 301b may select the NS2 due to higher KPI value. Hence, the AMF 303 or the NSSF 301b considers the performance metric of the NS during the selection process. It should be noted that the discussed embodiments are exemplary embodiments only and the AMF 303 or the NSSF 301b may select the NS based on other parameters of the performance metric.

[0066] In an embodiment, the NSSF 301b may also transmit the request to the NWDAF 301a. However, in such a scenario, the NSSF 301b first receives the request from the AMF 303 and then transmits the received request to the NWDAF 301a, as shown in Fig. 8. Fig. 8 illustrates a signal flow diagram depicting communication between an NF service consumer (e.g., AMF) and a NSSF for NS selection, in accordance with an embodiment of the present disclosure. As shown in Fig. 8, at operation 1, the AMF sends a GET request, i.e., Nssf_NSSelection_GET message, to the NSSF, as shown at operation 712 of Fig. 7b. The AMF may send the GET request along with query parameters: Requested NSSAI, Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID. At operation 2b, if no slice instances can be found for the requested slice selection information, then the NSSF returns a 403 Forbidden response with the "ProblemDetails" IE containing the Application Error "SNSSAI_NOT_SUPPORTED". However, if the slice instance has been found, then at operation 2a (200 OK), the NSSF returns a response message, i.e., a "Nssf_NSSelection_GET response message", as shown at operation 714 of Fig. 7b. The response body shall contain 'allowed NSSAI' and 'target AMF set or the list of candidate AMF(s)'. In an example, the response message includes an authorized network slice information, i.e., "AuthorizedNetworkSliceInfo" that has 'allowedNssaiList' IE. The allowedNssaiList IE includes 'allowedSnssaiList' IE. Each 'AllowedSnssai' has Attributes including 'allowedSnssai', 'nsiInformationList', and 'mappedHomeSnssai'. In an embodiment, for the 'nsiInformationList' the table 4 may be referred. The AllowedNssai IE is enhanced to include new IEs (e.g., nsKeyPerformanceInd, kpiTimeStamp, confidence) in the table 4. In another example, the response message includes a performance attribute, i.e., "NsiInformation" indicating the performance metric of the NS. In an embodiment, the response message may include the performance metric as shown in Table 4.

[0067] For example, Consumer NF (e.g. AMF) doesn't have intelligence to select the higher KPI slice. It relies on local implementation to select a slice from candidate list e.g. round robin. NSSF returns a list of allowed slices when consumer NF (e.g. AMF) performs NS Selection procedure. It doesn't provide any data on which one to choose. There can be many network slices with the similar KPIs, and a few with less-KPI value, the less-KPI slice may get selected impacting the incoming calls. By selecting a less-KPI slice, the reducing SLA will further get reduced, until the Slice Orchestrator takes corrective action. To address the problems, NWDAF implements new analytics "Slice Performance" for AnalyticsRequest service. NSSF modifies the NS Selection service to provide the "Slice KPI" for the candidate slices / slice instances to consumer NF e.g. AMF. Consumer NF (e.g. AMF) can utilize the slice KPI factor to select the higher KPI slice among the candidate list.

[0068] Fig. 9a illustrates a flow diagram depicting a method 900 for the selection of the network function, in accordance with an embodiment of the present disclosure. Fig. 9b illustrates a signal flow diagram depicting a selection of the network function, in accordance with an embodiment of the present disclosure. Fig. 10 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for selection of the NF, in accordance with a first embodiment of the present disclosure.

[0069] In an embodiment, the method as described in reference to Fig. 9a may be performed by a first network function. As shown in Fig. 9a, at step 901, the method 900 may include receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network functions. In an embodiment, the first network function is a Network Data Analytics Function (NWDAF), such as NWDAF 301a and the second network function is one of a Session Management Function (SMF), such as SMF 305, and a Network Repository Function (NRF) 301c. Accordingly, in an embodiment, the NWDAF 301a may receive the request from the SMF 305 or the NRF 301c.

[0070] In a first embodiment, the NWDAF 301a may receive the request in a request message, i.e., Nwdaf_AnalyticsInfo_Request message, after expiry of a predefined timer, i.e., NWDAF_Query_Timer, as shown in Fig. 10. The predefined timer is associated with the request in the second network function, i.e., the SMF 305 or the NRF 301c. Accordingly, the SMF 393 or the NRF 301c may request the NWDAF 301a after the expiry of the NWDAF_Query_Timer, as shown at operation 904 of Fig. 9b. In an embodiment, the predefined timer may be configured by the second network function. As shown in Fig. 10, the request message may include a query, i.e., NF performance. Accordingly, a parameter EventID of the request may be set to "NF performance" and the parameter event filter of the request may be set to "NF type". Accordingly, in an embodiment, the NWDAF 301a supports a new EventID (NF_PERFORMACE) in "EventId" in the Nnwdaf_AnalyticsInfo request body, as shown in Table 6:

[0071] EnumerationDescriptionApplicability...NF_PERFORMANCERepresents the analytics of network function performance informationNF_Performance

[0072] An exemplary format of the new EventID is shown in Table 7 which lists the existing event IDs support by NWDAF:

[0073] Enumeration valueDescriptionNF_LOADIndicates that the event subscribed is NF Load.NF_PERFORMANCEIndicates the KPI of an NFQOS_SUSTAINABILITYIndicates that the event subscribed is QoS sustainability.SLICE_LOAD_LEVELIndicates that the event subscribed is load level information of Network SliceSERVICE_EXPERIENCEIndicates that the event subscribed is a service experience.UE_MOBILITYIndicates that the event subscribed is UE mobility information.UE_COMMIndicates that the event subscribed is UE communication information....SM_CONGESTIONIndicates the Session Management Congestion Control Experience information for specific DNN and / or S-NSSAI.

[0074] Accordingly, in an embodiment, the request includes a performance attribute, i.e., NF_PERFORMANCE, indicating KPI of the network function.

[0075] As shown in Fig. 10, the NWDAF 301a may transmit response messages, i.e. "Nwdaf_AnalyticsInfo_Request response" or "no content" response to the SMF 305 or the NRF 301c in response to the Nwdaf_AnalyticsInfo_Request message, as shown at operation 906 of Fig. 9b. If no NF instances can be found for the requested NF selection information, then the NWDAF 301a returns a "204 no content" response. However, if the NF instances for the requested NF selection information have been found then the NWDAF 301a returns a "Nwdaf_AnalyticsInfo_Request response" message. In an embodiment, the response message "Nwdaf_AnalyticsInfo_Request response" may include the requested performance metric. The response message "Nwdaf_AnalyticsInfo_Request response" is further discussed in detail in response to step 903.

[0076] Fig. 11 illustrates a signal flow diagram depicting a communication between the first network function and a second network function for NF selection, in accordance with a second embodiment of the present disclosure. In a second embodiment, the NWDAF 301a may receive the request in a subscription message in an event of subscription of the performance metric by the second network function, as shown in Fig. 11. Particularly, if the SMF 305 or the NRF 301c has subscribed with the NWDAF 301a to receive the performance metric, then the NWDAF 301a may transmit the performance metric periodically based on the subscription. In an exemplary embodiment, the NWDAF 301a may receive such a request in a Nnwdaf_EventsSubscription message, as shown at operation 908 of Fig. 9b. As shown in Fig. 11, the request message may include a query, i.e., NF performance. Accordingly, a parameter EventID of the request may be set to "NF performance" and the parameter event filter of the request may be set to "NF type". Accordingly, in an embodiment, the NWDAF 301a supports a new Event (NF_PERFORMACE) in "NwdafEvent" in the Nnwdaf_EventSubscription_Subscribe message body, as shown in Table 6. Further, as shown in Fig. 11, the NWDAF 301a may transmit a response message, i.e. "Nnwdaf_EventsSubscription Notify" or "no content" response to the SMF 305 or the NRF 301c in response to the Nnwdaf_EventsSubscription message. If no NF instances can be found for the requested NF selection information, then the NWDAF 301a returns a "204 no content" response. However, if the NF instances for the requested NF selection information have been found then the NWDAF 301a returns a "Nnwdaf_EventsSubscription_Notify" response message, as shown at operation 910 of Fig. 9b. In an embodiment, the response message "Nnwdaf_EventsSubscription_Notify" may include the requested performance metric. The response message "Nnwdaf_EventsSubscription_Notify" is further discussed in detail in response to step 903.

[0077] In a further embodiment, the second network function, i.e., the SMF 303 or the NRF 301c may unsubscribe from event notifications using a Nnwdaf_EventsSubscription_Unsubscribe service message. Accordingly, in an embodiment, the NWDAF 301a supports a new Event (NF_PERFORMACE) in "NwdafEvent" in the Nwdaf_EventSubscription_Unsubscribe message body, as shown in Table 6.

[0078] Referring back to Fig. 9a, at step 903, the method 900 may include analysing a plurality of parameters associated with each of the plurality of network functions to determine the performance metric corresponding to each of the plurality of network functions. In an embodiment, the NWDAF 301a may receive the plurality of parameters associated with each of the plurality of network functions from an Operations Administration and Maintenance (OAM) sub-system, as shown at operation 902 of Fig. 9b. Thereafter, the NWDAF 301a may analyse the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network functions. In an exemplary embodiment, the NWDAF 301a may analyse the received plurality of parameters using an artificial intelligence (AI) model. In an embodiment, the plurality of parameters may include a success ratio of a plurality of call processing procedures, a load parameter, a fault parameter, a transaction rate, a throughput, a call drop rate, an alarm parameter, and a call fail parameter. The success ratio of a plurality of call processing procedures refers to a ratio of attempt to completion counts of a call processing procedure, e.g.., Registration, Packet Data Unit (PDU) Session Establishment, etc., of the NF. The load parameter refers to a dynamic load of the NF e.g., CPU load, Memory load, etc. The fault parameter refers to faults generated on the NS, e.g. Disk Fail, NF out of Service, etc. The transaction rate refers to a rate of call, i.e., transaction in units of time per NF considering the total number of UEs, and PDU Sessions. The call drop rate refers to the measurement of call drops, i.e., the number of call drops over a period of predefined time period. The predefined time period may be configured by the NWDAF 301a. The alarm parameter refers to real-time or non-real-time events, e.g., congestion or load crossing set threshold, etc. The call fail parameter refers to the reason for the call fail, e.g., timeouts of diameter interface orSBI interface, etc.

[0079] In an embodiment, the performance metric may include a plurality of performance attributes indicating a key performance indicator (KPI) value of a corresponding network function among the plurality of network functions, a time stamp associated with the KPI value, a confidence score associated with the KPI value, and status information of the corresponding network function. Further, the plurality of performance attributes may include an identification of single network function selection assistance information (Snssai), information related to the network function instance, identification of the network function instance, availability status of the network function, dynamic NF performance information, time stamp of calculation of the KPI, and confidence. In an embodiment, the performance metric may be included in the "Nwdaf_AnalyticsInfo_Request response" message. An exemplary format of the "Nwdaf_AnalyticsInfo_Request response" message is shown in Table 8

[0080]

[0081] The parameter "nfPerformanceInfos" of the "Nwdaf_AnalyticsInfo_Request response" message is shown in Table 9:

[0082]

[0083] In another embodiment, the performance metric may be included in the "Nnwdaf_EventsSubscription Notify" message. An exemplary format of the "Nnwdaf_EventsSubscription Notify" message is shown in Table 10:

[0084]

[0085] The parameter "nfPerformanceInfos" of the "Nnwdaf_EventsSubscription Notify" message is the same as shown above in Table 9.

[0086] Referring to Fig. 9a, at step 905, the method 900 may include transmitting the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions. As discussed above, the NWDAF 301a may transmit the performance metric corresponding to each of the plurality of network functions in a response message corresponding to the request message. The selection of the network function is further explained in reference to Figs. 12a and 12b, which have been explained in conjunction with each other.

[0087] Fig. 12a illustrates a flow diagram depicting a method for the selection of the network function in the second network function, in accordance with an embodiment of the present disclosure. Fig. 12b illustrates a signal flow diagram depicting a selection of the network function, in accordance with an embodiment of the present disclosure. In an embodiment, the method as described in reference to Fig. 12a may be performed by a second network function. As shown in Fig. 12a, at step 1201, the method 1200 may include transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network functions, as shown at operations 1204, 1208 of Fig. 12b. It should be noted that the first network function may receive the request in accordance with techniques as discussed in reference to Fig. 9a. As discussed in reference to Fig. 9a, the first network function may be the NWDAF 301a, and the second network function may be one of the SMF 305 and the NRF 301c. Then, at step 903, the method 900 may include receiving the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions, as shown at operations 1206, 1210 of Fig. 12b. In an embodiment, the NWDAF 301a may receive the plurality of parameters associated with each of the plurality of network functions from an Operations Administration and Maintenance (OAM) sub-system, as shown at operation 1202 of Fig. 12b. Thereafter, the NWDAF 301a may analyse the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network functions. In an embodiment, the SMF 305 or the NRF 301c may receive the performance metric from the NWDAF 301a in accordance with techniques discussed in reference to Fig. 9a, the description of which is not repeated for the sake of brevity of the disclosure. Thereafter, at step 905, the method 900 may include comparing each of the performance metrics with other remaining performance metrics. Then, at step 907, the method 900 may include selecting the network function from the plurality of network functions based on the comparison. In an exemplary embodiment, let us assume that the SMF 305 or the NRF 301c has received the performance metric for three NFs, i.e., NF1, NF2, and NF3. The performance metrics of NF1, NF2, and NF3 indicate a KPI value of 8 with a confidence of 90, a KPI value of 9 with a confidence of 60, and a KPI value of 70 with a confidence of 75, respectively. Accordingly, in an exemplary embodiment, the SMF 305 or the NRF 301c may compare the performance metrics of NF1, NF2, and NF3 and may select the NF1 due to higher confidence. In another exemplary embodiment, the SMF 305 or the NRF 301c may select the NF2 due to higher KPI value. Hence, the SMF 305 or the NRF 301c considers the performance metric of the NF during the selection process. It should be noted that the discussed embodiments are exemplary embodiments only and the SMF 305 or the NRF 301c may select the NF based on other parameters of the performance metric.

[0088] In an embodiment, the NRF 301c may also transmit the request to the NWDAF 301a. However, in such a scenario, the NRF first receives the request from the SMF 305 and then transmits the received request to the NWDAF 301a, as shown in Fig. 13. Fig. 13 illustrates a signal flow diagram depicting communication between an SMF and a NRF for NF selection, in accordance with an embodiment of the present disclosure. As shown in Fig. 13, at operation 1302, the SMF 1301 sends a discovery message, i.e., Nrf_NFDiscovery message, to the NRF 1303, as shown at operation 1212 of Fig. 12b. The discovery message may include query parameters of NF selection. At operation 1304a, if no NF instances can be found for the requested NF selection information, then the NRF 1303 returns a response with the "ProblemDetails" IE. However, if the NF instance has been found, then at operation 1304b, the NRF 1303 returns a discovery response message, i.e., a "Nrf_NFDiscovery response message", as shown at operation 1214 of Fig. 12b. The discovery response message includes a NF Profile attribute indicating the performance metric of the NF. In an embodiment, the discovery response message may include the performance metric as shown in Table 9.

[0089] Consumer NF (e.g. AMF, SMF) doesn't have intelligence to select the higher KPI target NF (e.g. SMF, UPF) . It relies on local implementation to select a NF from the candidate list. NRF returns a list of candidate target NFs when consumer NF (e.g. AMF) performs NF Discovery procedure. In such cases, there are problems like Selection of erroneous Network Function, NF / Service Downtime due to continuous inflow of calls to erroneous NF, and Reduced SLA until the management functions takes corrective action. To address the problems, NWDAF implements new analytics "NF Performance" for AnalyticsRequest service. NRF modifies the NF Discovery service to provide the "NF KPI" for the candidate NFs to consumer NF e.g. AMF. Consumer NF (e.g. AMF) can utilize the NF KPI factor to select the higher KPI NF (e.g. SMF) among the candidate list.

[0090] Fig. 14 illustrates a block diagram of a system for selection of the network slice and the network function in the wireless communication network, in accordance with an embodiment of the present disclosure.

[0091] The configuration of Fig. 14 may be understood as a part of the configuration of the first network function and the second network function. Further, the methods 400, 700, 900, and 1200 as disclosed above may be implemented in the system 1400 according to a further embodiment. Accordingly, in a non-limiting exemplary embodiment, the system 1400 may be implemented in at least one of the NWDAF 301a, the AMF 303, the SMF 305, the NSSF 301b, and the NRF 301c.

[0092] Referring to Fig. 14, the system 1400 may include "processor(s)" which is a processor 1401, a communication circuit 1403 (e.g., communicator or communication interface), and a memory 1405.

[0093] As an example, the processor 1401 may be a single processor or a number of processors, all of which could include multiple computing circuits. The processor 1401 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and / or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 1401 is configured to fetch and execute computer-readable instructions and data stored in the memory 1405. The processor 1401 may include one or a plurality of processors. At this time, one or a plurality of processors 1401 may be a general-purpose processor, such as a Central Processing Unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU), and / or an AI-dedicated processor such as a Neural Processing Unit (NPU). The one or a plurality of processors 1401 may control the processing of the input data in accordance with a predefined operating rule or Artificial Intelligence (AI) model stored in the non-volatile memory and the volatile memory, i.e., the memory 1405. The predefined operating rule or AI model is provided through training or learning. In an embodiment, the processor 1401 may be configured to perform methods 400, 700, 900, and 1200 of Figs. 4, 7, 9, and 12, respectively.

[0094] The communication circuit 1403 may perform functions for transmitting and receiving signals via a wireless channel. In an embodiment, the communication circuit 1403 may receive the request from the second network function, in accordance with techniques disclosed in the disclosure. In a further embodiment, the communication circuit 1403 may also transmit the performance metric to the second network function, in accordance with techniques disclosed in the disclosure. In a further embodiment, the communication circuit 1403 may transmit the request to the first network function, in accordance with techniques disclosed in the disclosure. In a further embodiment, the communication circuit 1403 may also receive the performance metric from the first network function, in accordance with techniques disclosed in the disclosure. In another embodiment, the processor 1401 may perform methods 400, 700, 900, and 1200 of Figs. 4, 7, 9, and 12, respectively via the communication circuit 1403.

[0095] The memory 1405 may include any non-transitory computer-readable medium known in the art including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM), and / or non-volatile memory, such as Read-Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 1405 may also store the one or more reports in accordance with techniques disclosed in the disclosure.

[0096] Embodiments are exemplary in nature, and the system 1400 may include additional components required to implement the desired functionality of the system 1400 in accordance with the requirements of the disclosure.

[0097] According to an embodiment, a method for selection of a network slice is provided. The method comprises receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices; analysing, by a first network function, a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices; and transmitting, by the first network function, the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.

[0098] For example, the receiving the request comprises receiving the request in a request message after expiry of a predefined timer associated with the request in the second network function.

[0099] For example, the receiving the request comprises receiving the request in a subscription message in an event of subscription of the performance metric by the second network function.

[0100] For example, the request includes a plurality of slice attributes indicating information related to the plurality of network slices and the plurality of slice attributes include performance of the network slice.

[0101] For example, the performance metric includes a plurality of performance attributes indicating a key performance indicator (KPI) value of a corresponding network slice among the plurality of network slices, a time stamp associated with the KPI value, a confidence score associated with the KPI value, and status information of the corresponding network slice.

[0102] For example, the plurality of performance attributes include an identification of single network slice selection assistance information (Snssai), information related to network slice instance, identification of the network slice instance, availability status of the network slice, dynamic slice performance information, time stamp of calculation of the KPI, and confidence.

[0103] For example, the plurality of parameters include a success ratio of a plurality of call processing procedures, a load parameter, a fault parameter, a transaction rate, a throughput, a call drop rate, an alarm parameter, and a call fail parameter.

[0104] For example, the first network function is a Network Data Analytics Function (NWDAF) and the second network function is one of an Access and Mobility Management Function (AMF) and a Network Slice Selection Function (NSSF).

[0105] For example, the analysing the plurality of parameters comprises receiving the plurality of parameters associated with each of the plurality of network slices from an Operations Administration and Maintenance (OAM)　sub-system; and analysing the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network slices.

[0106] For example, a method for selection of a network slice is provided. The method comprises transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network slices; receiving, by a second network function, the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices; comparing, by the second network function, each of the performance metric with other remaining performance metrics; and selecting, by the second network function, the network slice from the plurality of network slices based on the comparison.

[0107] For example, the second network function is one of an Access and Mobility Management Function (AMF) and a Network Slice Selection Function (NSSF).

[0108] For example, the transmitting the request comprises transmitting the request from an Access and Mobility Management Function (AMF) to a Network Slice Selection Function (NSSF); and transmitting the request from the NSSF to the first network function.

[0109] For example, the receiving the performance metric comprises receiving the performance metric at a Network Slice Selection Function (NSSF) from the first network function; and receiving the performance metric by an Access and Mobility Management Function (AMF) from the NSSF in a response message.

[0110] For example, the response message includes a performance attribute indicating the performance metric of the network slice.

[0111] According to an embodiment, a method for selection of a network function (NF) is provided. The method comprises receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network functions; analysing, by a first network function, a plurality of parameters associated with each of the plurality of network functions to determine the performance metric corresponding to each of the plurality of network functions; and transmitting, by the first network function, the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions.

[0112] For example, the receiving the request comprises receiving the request in a request message after expiry of a predefined timer associated with the request in the second network function.

[0113] For example, the receiving the request comprises receiving the request in a subscription message in an event of subscription of the performance metric by the second network function.

[0114] For example, the request includes a performance attribute indicating KPI of the network function.

[0115] For example, the transmitting the performance metric comprises transmitting the performance metric in one of a request response message and a subscription response message.

[0116] For example, the performance metric includes a plurality of performance attributes indicating a KPI value of a corresponding network function among the plurality of network functions, a time stamp associated with the KPI value, a confidence score associated with the KPI value, and information related to the corresponding network function.

[0117] For example, the plurality of performance attributes include a type of the NF, an identification of the NF instance, an identification of the NF instance set, availability status of the NF, performance of the NF, time stamp of reception of the KPI, an identification of Snssai and confidence.

[0118] For example, the plurality of parameters include a success ratio of a plurality of call processing procedures, a load parameter, a fault parameter, a transaction rate, a throughput, a call drop rate, an alarm parameter, and a call fail parameter.

[0119] For example, the first network function is a Network Data Analytics Function (NWDAF) and the second network function is one of a Session Management Function (SMF) and a Network Repository Function (NRF).

[0120] For example, the analysing the plurality of parameters comprises receiving the plurality of parameters associated with each of the plurality of network functions from an Operations Administration and Maintenance (OAM)　sub-system; and analysing the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network functions.

[0121] According to an embodiment, a method for selection of a network function is provided. The method comprises transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network functions; receiving, by a second network function, the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions; comparing, by the second network function, each of the performance metric with other remaining performance metrics; and selecting, by the second network function, the network function from the plurality of network functions based on the comparison.

[0122] For example, the second network function is one of a Session Management Function (SMF) and a Network Repository Function (NRF).

[0123] For example, the transmitting the request comprises transmitting the request from a Session Management Function (SMF) to a Network Repository Function (NRF) in a discovery message; and transmitting the request from the NRF to the first network function.

[0124] For example, the receiving the performance metric comprises receiving the performance metric at a Network Repository Function (NRF) from the first network function; and receiving the performance metric by an SMF from the NRF in a discovery response message.

[0125] For example, the discovery response message includes a NF Profile attribute indicating the performance metric of the network function.

[0126] According to an embodiment, a system for selection of a network slice is provided. The system comprises a memory; and a processor coupled to the memory, the processor is configured to receive, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices; analyse a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices; and transmit the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.

[0127] According to an embodiment, a system for selection of a network slice is provided. The system comprises a memory; and a processor coupled to the memory, the processor is configured to transmit, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network slices; receive the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices; compare each of the performance metric with other remaining performance metrics; and select the network slice from the plurality of network slices based on the comparison.

[0128] According to an embodiment, a system for selection of a network function is provided. The system comprises a memory; and a processor coupled to the memory, the processor is configured to receive, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network functions; analyse a plurality of parameters associated with each of the plurality of network functions to determine the performance metric corresponding to each of the plurality of network functions; and transmit the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions.

[0129] According to an embodiment, a system for selection of a network function is provided. The system comprises a memory; and a processor coupled to the memory, the processor is configured to transmit, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network functions; receive the performance metric corresponding to each of the plurality of network functions to the second network function for the selection of the network function from the plurality of network functions; compare each of the performance metric with other remaining performance metrics; and select the network function from the plurality of network functions based on the comparison.

[0130] Accordingly, the present disclosure offers several advantages. For instance, the disclosed techniques take into account performance parameters of the NF during NF selection and those of the NS during NS selection, thereby enhancing overall system performance and user experience. The disclosed techniques provide real-time feedback on the performance of both NS and NF to the network, enabling the selection of optimized NS and NF. Additionally, the disclosed techniques improve the efficiency of the NF and NS selection process. The disclosed techniques also prevent new calls from being attached to slices or slice instances with declining SLAs. Moreover, the disclosed techniques help maintain SLA levels even when there is a downward trend in Call Success Rates, throughput, and other metrics.

[0131] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skilled in the art to which this invention belongs. The system, methods, and examples provided herein are illustrative only and not intended to be limiting.

[0132] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

[0133] While specific language has been used to describe the present subject matter, any limitations arising on account thereto, are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The drawings and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment.

Claims

1.A method for selection of a network slice, the method comprising:receiving, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices;analysing, by a first network function, a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices; andtransmitting, by the first network function, the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.2.The method as claimed in claim 1, wherein receiving the request comprises:receiving the request in a request message after expiry of a predefined timer associated with the request in the second network function.3.The method as claimed in claim 1, wherein receiving the request comprises:receiving the request in a subscription message in an event of subscription of the performance metric by the second network function.4.The method as claimed in claim 1, wherein the request includes a plurality of slice attributes indicating information related to the plurality of network slices and the plurality of slice attributes include performance of the network slice.5.The method as claimed in claim 1, wherein the performance metric includes a plurality of performance attributes indicating a key performance indicator (KPI) value of a corresponding network slice among the plurality of network slices, a time stamp associated with the KPI value, a confidence score associated with the KPI value, and status information of the corresponding network slice.6.The method as claimed in claim 5, wherein the plurality of performance attributes include an identification of single network slice selection assistance information (Snssai), information related to network slice instance, identification of the network slice instance, availability status of the network slice, dynamic slice performance information, time stamp of calculation of the KPI, and confidence.7.The method as claimed in claim 1, wherein the plurality of parameters include a success ratio of a plurality of call processing procedures, a load parameter, a fault parameter, a transaction rate, a throughput, a call drop rate, an alarm parameter, and a call fail parameter.8.The method as claimed in claim 1, wherein the first network function is a Network Data Analytics Function (NWDAF) and the second network function is one of an Access and Mobility Management Function (AMF) and a Network Slice Selection Function (NSSF).9.The method as claimed in claim 1, wherein analysing the plurality of parameters comprises:receiving the plurality of parameters associated with each of the plurality of network slices from an Operations Administration and Maintenance (OAM)　sub-system; andanalysing the received plurality of parameters to determine the performance metric corresponding to each of the plurality of network slices.10.A method for selection of a network slice, the method comprising:transmitting, to a first network function, a request for providing a performance metric corresponding to each of a plurality of network slices;receiving, by a second network function, the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices;comparing, by the second network function, each of the performance metric with other remaining performance metrics; andselecting, by the second network function, the network slice from the plurality of network slices based on the comparison.11.The method as claimed in claim 10, wherein the second network function is one of an Access and Mobility Management Function (AMF) and a Network Slice Selection Function (NSSF).12.The method as claimed in claim 10, wherein transmitting the request comprises:transmitting the request from an Access and Mobility Management Function (AMF) to a Network Slice Selection Function (NSSF); andtransmitting the request from the NSSF to the first network function.13.The method as claimed in claim 10, wherein receiving the performance metric comprises:receiving the performance metric at a Network Slice Selection Function (NSSF) from the first network function; andreceiving the performance metric by an Access and Mobility Management Function (AMF) from the NSSF in a response message.14.The method as claimed in claim 13, wherein the response message includes a performance attribute indicating the performance metric of the network slice.15.An apparatus for selection of a network slice, the system comprising:a memory; anda processor coupled to the memory, the processor is configured to:receive, from a second network function, a request for providing a performance metric corresponding to each of a plurality of network slices;analyse a plurality of parameters associated with each of the plurality of network slices to determine the performance metric corresponding to each of the plurality of network slices; andtransmit the performance metric corresponding to each of the plurality of network slices to the second network function for the selection of the network slice from the plurality of network slices.

Images