WIRELESS NETWORK AND METHODS FOR HANDLING PDU SESSION HANDOVER ADMISSION CONTROL IN WIRELESS NETWORK

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose methods for handling a network slice admission control (NSAC) performed by a Network Function (NF) service consumer (200) in a wireless network (1000). The method includes determining that an existing Protocol Data Unit (PDU) session has been handed over from a source access to a target access. Further, the method includes performing a network slice admission control for the PDU session, based on the determination, by interacting the NF service consumer with a Network Slice Admission Control Function (NSACF) entity (300).

Claims

1. A method for handling a network slice admission control (NSAC) performed by a Network Function (NF) service consumer (200) in a wireless network (100), comprising: determining that an existing Protocol Data Unit (PDU) session has been handed over from a source access to a target access; and performing a network slice admission control for the PDU session, based on the determination, by interacting the NF service consumer with a Network Slice Admission Control Function (NSACF) entity (300).

2. The method as claimed in claim 1, wherein performing the network slice admission control for the PDU session comprises: increasing a number of PDU session for the target access, and in case that the increasing the number of PDU session for the target access is successful, decreasing a number of PDU sessions for the source access.

3. The method as claimed in claim 1, wherein the source access is a 3rd Generation Partnership Project (3GPP) and the target access is a non-3GPP access.

4. The method as claimed in claim 1, wherein the source access is a non-3GPP access and the target access is a 3GPP access.

5. The method as claimed in claim 1, wherein the NF service consumer comprises (200) one of a Session Management Function (SMF) entity (200b) or a combined SMF and Packet Data Network Gateway (PGW-C) (200a).

6. A Network Function (NF) service consumer (200) for handling a network slice admission control (NSAC) in a wireless network, comprising: a processor; a memory; and a NSAC controller, coupled with the processor and the memory, configured to: determine that an existing Protocol Data Unit (PDU) session has been handed over from a source access to a target access; and perform a network slice admission control for the PDU session, based on the determination, by interacting the NF service consumer with a Network Slice Admission Control Function (NSACF) entity (300).

7. The NF service consumer (200) as claimed in claim 6, wherein perform the network slice admission control for the PDU session comprises: increasing a number of PDU session for the target access, and in case that the increasing the number of PDU session for the target access is successful, decreasing a number of PDU sessions for the source access.

8. The NF service consumer (200) as claimed in claim 6, wherein the source access is a 3rd Generation Partnership Project (3GPP) access and the target access is a non-3GPP access.

9. The NF service consumer (200) as claimed in claim 6, wherein the source access is a non-3GPP access and the target access is a 3GPP access.

10. The NF service consumer (200) as claimed in claim 6, wherein the NF service consumer (200) comprises one of a Session Management Function (SMF) entity (200b) or a combined SMF and Packet Data Network Gateway (PGW-C) (200a).

Description

BRIEF DESCRIPTION OF DRAWINGS

[0044] The embodiments disclosed herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:

[0045] FIG. 1 depicts an example scenario in which a UE registers on a 3GPP and a non-3GPP, according to prior arts;

[0046] FIG. 2 depicts a method for handling PDU and PDN session handovers in wireless communication networks, according to embodiments as disclosed herein;

[0047] FIG. 3 depicts a scenario in which a handover of the PDU session occurs between a 3GPP to a non-3GPP, according to embodiments as disclosed herein;

[0048] FIG. 4 depicts a scenario in which a handover of the PDU session occurs between a non-3GPP to an EPC, according to embodiments as disclosed herein;

[0049] FIG. 5 depicts a scenario in which a handover of the PDN connection occurs from an EPC to a 5GC (non-3GPP), according to embodiments as disclosed herein;

[0050] FIG. 6 depicts a dual-registration case in which the UE is simultaneously registered on the EPC and the 5GC, according to embodiments as disclosed herein;

[0051] FIG. 7 shows various hardware components of a NF service consumer, according to the embodiments as disclosed herein; and

[0052] FIG. 8 is a flow chart illustrating a method for handling the NSAC in a wireless network, according to the embodiments as disclosed herein.

MODE FOR THE INVENTION

[0053] Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms include and comprise, as well as derivatives thereof, mean inclusion without limitation; the term or, is inclusive, meaning and/or; the phrases associated with and associated therewith, as well as derivatives thereof, may mean 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, or the like; and the term controller means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0054] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms application and program refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase computer readable program code includes any type of computer code, including source code, object code, and executable code. The phrase computer readable medium includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A non-transitory computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0055] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0056] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0057] The embodiments herein achieve methods for handling a NSAC in a wireless network. The method includes determining, by a NF service consumer, that an existing PDU session has been handed over from a source access to a target access. Further, the method includes updating, by the NF service consumer, a count at the source access and a count at the target access, based on the determination, by interacting the NF service consumer with a NSACF entity.

[0058] In an embodiment, if a request type is existing PDU session, a SMF entity shall not perform network slice admission control for the PDU session, except for the following cases such as handover of an existing PDU session between a 3GPP access and a non-3GPP access is performed. In an embodiment, the NF service consumer (e.g. SMF, combined SMF+PGW-C or the like) shall invoke a NumOfPDUsUpdate service operation to request the NSACF entity to perform network slice admission control procedure related to a number of PDU sessions by using HTTP POST techniques.

[0059] The following abbreviations have been used herein: [0060] a) NSAC: Network Slice Admission Control, [0061] b) NSACF: Network Slice Admission Control Function, [0062] c) AMF: Access and Mobility Management Function, [0063] d) NEF: Network Exposure Function, [0064] e) NF: Network Function, [0065] f) NSSAI: Network Slice Selection Assistance Information, [0066] g) NSSF: Network Slice Selection Function, [0067] h) S-NSSAI: Single Network Slice Selection Assistance Information, [0068] i) SMF: Session Management Function, [0069] j) UPF: User Plane Function, [0070] k) EPC: Evolved Packet Core Network, [0071] l) EPS: Evolved Packet System, [0072] m) MME: Mobility Management Entity, [0073] n) PGW-C: Packet Data Network Gateway,

[0074] The prior art does not disclose the point that the NSACF maintains the PDU session count per access type. Thus, if the PDU session is handed over from one access type (e.g., 3GPP access type) to another access type (e.g., non-3GPP access) if there is no interaction with the NSACF then the NSACF will maintain the wrong count of PDU sessions per access type and will lead to unintended consequences. For example consider below example,

[0075] 1. Suppose PDU session count in the NSACF for S-NSSAI X for 3GPP access and non-3GPP access respectively are P0-3GPP and P0-non-3GPP.

[0076] 2. UE on 3GPP access established new PDU session with S-NSSAI-x. NSACF updated with PDU session count as P0-3GPP+1, Po-non-3GPP

[0077] 3. UE handover PDU session of S-NSSAI from 3GPP to non-3GPP as per the prior art, SMF doesn't perform interaction with NSACF so PDU session count in the NSACFF is not update and it remains P0-3GPP+1, Po-non-3GPP

[0078] As the count is not update for 3GPP and non-3GPP access. Other UE will face admission control. For an example, another UE try to establish PDU session with S-NSSAI-x, it may not be admitted if maximum allowed PDU session for S-NSSAI is set to P0-3GPP+1. Similar issue can be inferred when UE handover PDU session from non-3GPP access to 3GPP access. The current arts does not handle above scenarios. The proposed method overcomes the problem of the current arts.

[0079] Referring now to the drawings, and more particularly to FIGS. 2 through 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0080] FIG. 2 depicts a method for handling PDU and PDN session handovers in the wireless communication networks (1000), according to the embodiments as disclosed herein. The SMF+PGW-C (200a) takes the below action, in case of PDU session/PDN connection is handover over from one access to other access:

[0081] Case1: The source access is the non-3GPP and the target access is the 3GPP (5GC)

[0082] A) The SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of PDU session per network slice for the non-3GPP access.

[0083] B) The SMF (200b) or the SMF+PGW-C (200a) interact with the NSACF (300) to increase number of PDU session per network slice for the 3GPP access.

[0084] Case2: The source access is 3GPP (5GC) and the target access is the non-3GPP.

[0085] A) The SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of PDU session per network slice for the 3GPP access.

[0086] B) The SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number of PDU session per network slice for the non-3GPP access.

[0087] For case 1 and case 2, if the SMF (200b) or the SMF+PGW-C (200a) identified the PDU session transfer between the 3GPP and the non-3GPP (based on the saved access information in step A and/or B), it interacts with the NSACF (300) to decrease the number of PDU sessions per network slice on the source access and increase the number of PDU session per network slice on the target access.

[0088] Case3: Source access is an EPC and the target access is the non-3GPP.

[0089] If the SMF+PGW-C (200a) is configured with EPC counting required,

[0090] A) the SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of PDU session per network slice for the 3GPP access.

[0091] B) the SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number of PDU session per network slice for the non-3GPP access.

[0092] C) The SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of registered UE(s) per network slice for the 3GPP access.

[0093] Case 4: The source access is non-3GPP and the target access is EPC

[0094] if the EPC counting is required,

[0095] A) the SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of the PDU session per network slice for the non-3GPP access.

[0096] B) The SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number of PDU session per network slice for the 3GPP access.

[0097] C) the SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number of registered UE(s) per network slice for the 3GPP access if the EPC counting is not required,

[0098] A) the SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of the PDU session per network slice for the non-3GPP access

[0099] Case 5: the source access is the EPC and the target access is 5GC (3GPP)

[0100] If the EPC counting is required,

[0101] A) the SMF (200b) or the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease number of registered UE(s) per network slice for the 3GPP access or

[0102] B) If the SMF+PG-C (200a) identified that PDN connection with PDU session ID is completely moved to other access (in this case 3GPP access), interact with NSACF (300) to decrease number of registered UE(s) per network slice for the 3GPP access.

[0103] Case 6: the source access is the EPC and the target access is 5GC (3GPP)

[0104] if EPC counting is not required,

[0105] A) SMF (200b) or SMF+PGW-C (200a) interact with NSACF (300) to decrease number of PDU session per network slice for the 3GPP access if EPC counting is required,

[0106] A) SMF (200b) or SMF+PGW-C (200a) interact with NSACF (300) to decrease number of registered UE(s) per network slice for the 3GPP access

[0107] For all solutions, if the PDN connection is successfully handover to other access (e.g., 5GC or non-3GPP), SMF+PGW-C (200a) which is configured with EPC Counting required, interact with NSACF (300) to decreases the number of registered UEs per network slice for the S-NSSAI which is handed over to the other access.

[0108] When the PDN connection is handed over/reselected to target access (e.g., 5GC or non-3GPP) or the target RAT (EPS or 5GS), if the SMF+PGW-C (200a) is configured with EPC counting required, the source SMF+PGW-C (200a) interact with NSACF (300) to decreases the number of registered UEs per network slice/number of PDU sessions for the S-NSSAI, which is handed over to target access or target RAT.

[0109] When the PDN connection is handed over/reselected to the target access (e.g., 5GC or non-3GPP) or the target RAT EPS or 5GS), if the SMF+PGW-C (200a) is configured with EPC Counting required, the target SMF+PGW-C (200a) interact with NSACF (300) to increases the number of registered UEs per network slice/number of PDU sessions for the S-NSSAI which is handed over to target access or target RAT.

[0110] When the PDN connection is handed over/reselected to target access (e.g., 5GC or non-3GPP) or the target RAT (EPS or 5GS), if the SMF+PGW-C (200a) is configured with EPC Counting is not required, the source SMF+PGW-C (200a) interacts with the NSACF (300) to decreases the number of registered UEs per network slice/number of PDU sessions for the S-NSSAI,s which is handed over to target access or target RAT

[0111] When the PDN connection is handed over/reselected to the target access (e.g., 5GC or non-3GPP) or target RAT (EPS or 5GS), if the SMF+PGW-C (200a) is configured with EPC Counting is not required, the target SMF+PGW-C (200a) interact with the NSACF (300) to increases the number of registered UEs per network slice/number of PDU sessions for the S-NSSAI which is handed over to target access. The source and target in above embodiments can be the same node, but they act as two different virtual nodes from the protocol perspective.

[0112] As shown in the FIG. 2, at step 1, the UE (100) have the PDU session or the PDN connection on the source access. At step 2, the SMF+PGW-C (200a) stores the (radio) access information (e.g. EPC, 5GC, non-3GPP, ePDG etc.). At 3, the PDU session or the PDN connection is handed over to the target access. At 4, the SMF+PGW-C (200a) stores the (radio) access information (e.g. EPC, 5GC, non-3GPP, ePDG etc.) after the HO.

[0113] FIG. 3 depicts an example scenario in which the handover of the PDU session occurs between the 3GPP to the non-3GPP, according to the embodiments as disclosed herein.

[0114] At step 1, the UE (100) registers in the 5GS (i.e., non-3GPP). At step 2, the AMF (500) interacts with the NSACF (300) to increase number of registered UE(s) per network slice. At step 3, the UE (100) registers in the 5GS (3GPP). At step 4, the AMF (500) interacts with the NSACF (300) to increase number of registered UE(s) per network slice. At step 5, the PDU session establishment procedure is done between the UE (100) and the AMF (500). At step 6, the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number of PDU session per network slice. At step 7, the PDU session establishment procedure is done between the UE (100) and the AMF (500) the HO of existing PDU session to the non-3GPP. At step 8, if the SMF (200b) or the SMF+PGW-C (200a) determines that the PDU session is handed over from non-3GPP to 3GPP or 3GPP to non-3GPP (HO between 3GPP and non-3GPP with both the source and target access is on 5GS). The SMF (200b) or SMF+PGW-C (200a) interacts with the NSACF (300) to increases the number of PDU sessions per network slice for current access (target access) where PDU session is handover successfully. The SMF+PGW-C (200a) interacts with the NSACF (300) to decreases the number of PDU sessions per network slice for the access from where PDU session is handed over (source access). The SMF (200b) or SMF+P-GW stores the (Radio) access, where the PDU session is established. At the time of PDU session, the HO from one access to another access, the SMF (200b) or the SMF+PGW-C (200a) uses the stored information to determine source and target access.

[0115] FIG. 4 depicts a scenario in which the handover of the PDU session occurs between the non-3GPP and the EPC, according to the embodiments as disclosed herein. At step 1, the UE (100) registers in the 5GS (i.e., non-3GPP). At step 2, the AMF (500) interacts with the NSACF (300) to increase number of registered UE(s) per network slice. At step 3, the UE registers in the EPC. At step 4, the PDU session establishment procedure is performed between the UE (100) and the AMF (500). At step 5, the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number of PDU session per network slice. At step 6, the PDN connection establishment procedure is performed between the UE (100) and the AMF (500) after the HO PDU session to the EPC.

[0116] At step 7, if the SMF (200b) or the SMF+PGW-C (200a) determines that the PDN connection is handed over to non-3GPP from the EPC. The SMF+PGW-C (200a) interacts with the NSACF (300) to update the number of PDU sessions and/or number of registered UE(s) per network slice as:

[0117] Case 1: if SMF+PGW-C (200a) is configured with EPC Count not required.

[0118] 1. The SMF+PGW-C (200a) interacts with the NSACF (300) to decrease the number of PDU sessions per network slice on the non-3GPP access.

[0119] Case 2: EPC count required:

[0120] 1. The SMF+PGW-C (200a) interacts with the NSACF (300) to decrease the number of PDU sessions per network slice on non-3GPP access.

[0121] 2. The SMF+PGW-C (200a) interacts with the NSACF (300) to increase the number of PDU session per network slice on 3GPP access.

[0122] 3. The SMF+PGW-C (200a) interacts with the NSACF (300) to increase the number of registered UEs per network slice on 3GPP access.

[0123] The SMF (200b) or the SMF+P-GW (200a) stores the (Radio) access, where the PDU session is established. At the time of PDN connection HO from one access to another access, the SMF (200b) or the SMF+PGW-C (200a) uses the stored information to determine the source and target access (e.g., SMF store the (radio) access information as EPC,5GS 3GPP, 5GS non-3GPP).

[0124] FIG. 5 depicts a scenario in which the handover of the PDN session occurs from the EPC to the 5GC (non-3GPP), according to the embodiments as disclosed herein. At step 1, the UE (100) registers in the 5GS. At step 2, the AMF (500) interacts with the NSACF (300) to increase number of registered UE(s) per network slice. At step 3, the PDN connection establishment procedure is performed between the UE (100) and the SMF+PGW-C (200a). At step 4, the SMF+PGW-C (200a) interacts with the NSACF (300) to increase number registered UE(s) per network slice. At step 5, the SMF+PGW-C (200a) interact with the NSACF (300) to increase number of PDU session per network slice. At step 6, the PDU session establishment on the 5GS is performed between the UE (100) and the AMF (500).

[0125] If the SMF (200b) or the SMF+PGW-C (200a) determines that the PDN connection is handed over to the non-3GPP from the EPC, the SMF+PGW-C (200a) configured with the EPC Counting required interacts with the NSAC as below: [0126] a. Decrease the number of PDU sessions per network slice on the 3GPP access. [0127] b. Increase the number of PDU session per network slice on the non-3GPP access. Decrease the number of registered UE per network slice on the GPP access.

[0128] FIG. 6 depicts a dual-registration case in which the UE (100) is simultaneously registered on the EPC and the 5GC, according to the embodiments as disclosed herein. At step 1, the UE (100) registers in the 5GS. At step 2, the AMF (500) interacts with the NSACF (300) to increase a number of registered UE(s) per network slice. At step 3, the PDN connection establishment procedure is performed between the UE (100) and the SMF+PGW-C (200a). At step 4, the SMF+PGW-C (200a) interact with the NSACF (300) to increase the number registered UE(s) per network slice. At step 5, the SMF+PGW-C (200a) interact with the NSACF (300) to increase the number of PDU session per network slice. At step 6, the PDU session establishment, on the 5GS, is performed between the UE (100) and the AMF (500). In step 7, if the EPC counting is required, the SMF+PGW-C (200a) interacts with the NSACF (300) to decrease the number of registered UE(s) per network slice or after step 6, if the SMF+PGW-C (200a) determined that the PDN connection is successfully handover to the 5GC (3GPP or non-3GPP), i.e., PDN connection with associated PDU session ID (PID1) is moved to other access, interact with NSACF (300) to decrease the number of registered UE(s) for the S-NSSAI (S-NSSAI1 in this case).

[0129] As per the proposed solution, the network slice admission control for the maximum number of UEs (100) and/or for maximum number of PDU sessions per network slice may not be performed at the time of PDN connection establishment for UE (100) not supporting N1 mode. The SMF+P-GWC (200a) can reject the PDN connection request, if the associated Access Point Name (APN) provided in the PDN connection request belongs to the network slice and the UE (100) has the N1 mode disabled. The SMF+PGW-C (200a) may identify the UE (100) not having N1 mode support either from the PDU session ID IE or 5QI IE value or any other N1 mode relevant IEs included during connection establishment request from UE (100).

[0130] FIG. 7 shows various hardware components of the NF service consumer (200), according to the embodiments as disclosed herein. The NF service consumer (200) can be, for example, but not limited to the SMF entity (200b) and the combined SMF and PGW-C (200a). In an embodiment, the NF service consumer (200) includes a processor (210), a communicator (220), a memory (230) and a NSAC controller (240). The processor (210) is coupled with the communicator (220), the memory (230) and the NSAC controller (240).

[0131] The NSAC controller (240) determines that the existing PDU session has been handed over from the source access to the target access. Further, the NSAC controller (240) updates the count at the source access and a count at the target access, based on the determination, by interacting the NF service consumer (200) with the NSACF entity (300). In an embodiment, the NSAC controller (240) decreases the number of PDU sessions per network slice at the source access and increases the number of PDU sessions per network slice at the target access upon determining the existing PDU session is handover from the source access to the target access. The source access and the target access is on a 5GS.

[0132] In an embodiment, the source access is the 3GPP access and the target access is the non-3GPP access. In another embodiment, the source access is the non-3GPP access and the target access is the 3GPP access.

[0133] The NSAC controller (240) is physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0134] Further, the processor (210) is configured to execute instructions stored in the memory (230) and to perform various processes. The communicator (220) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (230) may, in some examples, be considered a non-transitory storage medium. The term non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term non-transitory should not be interpreted that the memory (230) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0135] Although the FIG. 7 shows various hardware components of the NF service consumer (200) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the NF service consumer (200) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention. One or more components can be combined together to perform same or substantially similar function in the NF service consumer (200).

[0136] FIG. 8 is a flow chart (800) illustrating a method for handling the NSAC in the wireless network (1000), according to the embodiments as disclosed herein. The operations (802 and 804) are handled by the NSAC controller (240). At step 802, the method includes determining that the existing PDU session has been handed over from the source access to the target access. At step 804, the method includes updating the count at the source access and the count at the target access, based on the determination, by interacting the NF service consumer with the NSACF entity (300).

[0137] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device, or a combination of hardware device and software module.

[0138] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.