Method and system for dynamic call admission capacity management in a communication network

Abstract

The present disclosure relates to a method performed by the NWDAF. The method comprises determining a capacity recommendation in response to an initial capacity allocation request from one or more consumer network entities, sending, to the one or more consumer network entities, the capacity recommendation, receiving a capacity re-allocation request from the one or more consumer network entities, when the capacity recommendation does not meet defined criteria, performing dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request, and sending, to the one or more consumer network entities, an updated capacity recommendation for performing call admission and congestion control based on the updated capacity recommendation from the NWDAF entity.

Description

METHOD AND SYSTEM FOR DYNAMIC CALL ADMISSION CAPACITY MANAGEMENT IN A COMMUNICATION NETWORK

[0001] The present subject matter is related in general to telecommunication network, more particularly, but not exclusively, the present subject matter relates to a method and system for dynamic call admission capacity management in a communication network.

[0002] With the introduction of non-third Generation Partnership Project (non-3GPP) interworking nodes like Non-3GPP　Interworking Function　(N3IWF), Trusted Non-3GPP　Gateway Function (TNGF), Wireline Access Gateway Function (WAGF) and rusted Wireless Interworking Function (TWIF), the number of non-3GPP connections have increased. Systems and use cases such as smart homes, Industrial Internet of Things (IIoT), health care systems, smart factories etc require device connection from Fifth Generation (5G) networks which are primarily based on non-3GPP access types.

[0003] However, currently there is no provision for bandwidth distinction between 3GPP and non-3GPP access types in 5G core. This results in all types of connections being admitted based on a first come first served algorithm. As there is a monopoly of 3GPP access connections (e.g. using New Radio (NR), there is a possibility of resource starvation to non-3GPP connections because of difference in call rates of 3GPP and non-3GPP connections. 5G Core congestion control is currently access medium agnostic, i.e., it does not differentiate between 3GPP access connections and non-3GPP access connections and applies the same policy of congestion control, irrespective of the access medium.

[0004] Further, existing call admission capacity management in 5G Core is statically maintained, with limited scope of considering the dynamics of the volume of calls at different times. This type of dimensioning results in system resources being pre-allocated at full capacity. Also, existing congestion control methodologies do not involve congestion control based on the access type of the call which leads to resource deprivation to new connection requests coming from non-3GPP access during congestion time.

[0005] Thus, there is a need to distinguish bandwidth between 3GPP and Non-3GPP calls and to manage call admission based on distinction.

[0006] The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0007] In an embodiment, the present disclosure relates to a method dynamic call admission capacity management in a communication network. The method comprises of determining a capacity recommendation in response to an initial capacity allocation request from one or more consumer network entities. The capacity recommendation comprising a guaranteed admissible call capacity bandwidth per access type among a plurality of access types and a guaranteed free-pool bandwidth, based on call data and network related data. The plurality of access types comprises of 3GPP access and Non-3GPP (N3GPP) access. The method further comprises of sending to the one or more consumer network entities the capacity recommendation. The method further comprises of receiving a capacity re-allocation request from the one or more consumer network entities, when the capacity recommendation does not meet defined criteria. The method further comprises of performing dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request. The method finally comprises sending to one or more consumer network entities an updated capacity recommendation for performing call admission and congestion control based on the recommendation from the NWDAF entity.

[0008] The present disclosure further relates to Network Data Analytics Function (NWDAF) entity for dynamic call admission capacity management in a communication network. The NWDAF entity comprises of a processor and a memory. The processor is configured to determine a capacity recommendation in response to an initial capacity allocation request from one or more consumer network entities. The capacity recommendation comprising a guaranteed admissible call capacity bandwidth per access type among a plurality of access types and a guaranteed free-pool bandwidth, based on call data and network related data. The plurality of access types comprises of 3GPP access and Non-3GPP (N3GPP) access. The processor is further configured to send to the one or more consumer network entities the capacity recommendation.

[0009] The processor is further configured to receive a capacity re-allocation request from the one or more consumer network entities, when the capacity recommendation does not meet defined criteria. The processor is further configured to perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request. The processor is finally configured to send to one or more consumer network entities an updated capacity recommendation for performing call admission and congestion control based on the capacity recommendation from the NWDAF entity.

[0010] In another embodiment, the present disclosure relates to a method for dynamic call admission capacity management in a communication network. The method comprises of sending to a Network Data Analytics Function (NWDAF) entity, an initial capacity allocation request. The method further comprises of receiving from the NWDAF entity, a capacity recommendation in response to the initial capacity allocation request, comprising a guaranteed admissible call capacity bandwidth per access type among a plurality of access types and a guaranteed free-pool bandwidth, based on call data and network related data. The plurality of access types comprises of 3GPP access and Non-3GPP (N3GPP) access. The method comprises of sending a capacity re-allocation request, when the capacity recommendation does not meet defined criteria. The method comprises of receiving an updated capacity recommendation for performing call admission and congestion control based on the capacity recommendation from the NWDAF entity, wherein the updated capacity recommendation is received based on the NWDAF entity performing dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request. The method finally comprises of dropping incoming calls of an access type of the plurality of access types when the updated capacity recommendation on bandwidth allocated for each of the plurality of access types has exceeded.

[0011] The present disclosure further relates to a consumer network entity for dynamic call admission capacity management in a communication network. The consumer network entity comprises of a processor and a memory. The processor is configured to send to a Network Data Analytics Function (NWDAF) entity, an initial capacity allocation request. The processor is further configured to receive from the NWDAF entity, a capacity recommendation in response to the initial capacity allocation request, comprising a guaranteed admissible call capacity bandwidth per access type among a plurality of access types and a guaranteed free-pool bandwidth, based on call data and network related data. The plurality of access types comprises of 3GPP access and Non-3GPP (N3GPP) access. The processor is further configured to send to the NWDAF entity, a capacity re-allocation request, when the capacity recommendation does not meet defined criteria. The processor is further configured to receive from the NWDAF entity, an updated capacity recommendation for performing call admission and congestion control based on the capacity recommendation from the NWDAF entity, wherein the updated capacity recommendation is received based on the NWDAF entity performing dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request. The processor is finally configured to drop incoming calls of an access type of the plurality of access types when the updated capacity recommendation on bandwidth allocated for each of the plurality of access types has exceeded.

[0012] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.

[0013] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, serve to explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference features and components. Some embodiments of system and / or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and regarding the accompanying figures, in which:

[0014] Fig. 1A illustrates call capacity management as per existing methodologies;

[0015] Fig. 1B illustrates an environment for dynamic call admission capacity management in a communication network, in accordance with some embodiments of the present disclosure;

[0016] Fig. 2 illustrates access aware dynamic call admission capacity management in a communication network, in accordance with some embodiments of the present disclosure;

[0017] Fig. 3 illustrates a detailed a block diagram of a consumer network entity, in accordance with some embodiments of the present disclosure;

[0018] Fig. 4 illustrates a detailed a block diagram of a Network Data Analytics Function (NWDAF) entity, in accordance with some embodiments of the present disclosure;

[0019] Fig. 5A depicts a message flow diagram of an exemplary method for dynamic call admission capacity management between an AMF and a NWDAF, in accordance with some embodiments of the present disclosure;

[0020] Fig. 5B depicts another message flow diagram of an exemplary method for dynamic call admission capacity management between an AMF and a NWDAF, in accordance with some embodiments of the present disclosure;

[0021] Fig. 5C depicts a message flow diagram of an exemplary method for dynamic call admission capacity management between consumer network entities, NWDAF and OAM, in accordance with some embodiments of the present disclosure;

[0022] Figs. 6 and 7 depict a flow diagram of an exemplary method for dynamic call admission capacity management in a communication network, in accordance with some embodiments of the present disclosure;

[0023] Fig. 8 illustrates a block diagram of an exemplary computer system, for executing embodiments consistent with the present disclosure, in accordance with some embodiments of the present disclosure.

[0024] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether such computer or processor is explicitly shown.

[0025] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

[0026] While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the spirit and the scope of the disclosure.

[0027] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a device or system or apparatus proceeded by "comprises… a" does not, without more constraints, preclude the existence of other elements or additional elements in the device or system or apparatus.

[0028] The terms "includes", "including", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that includes a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by "includes… a" does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.

[0029] The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.

[0030] The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly specified otherwise.

[0031] As used herein, the terms "communication" and "communicate" may refer to the reception, receipt, transmission, transfer, provision, and / or the like of information (e.g., data, signals, messages, instructions, commands, and / or the like). For one unit (e.g., a device, a system, a component of a device or system, combinations thereof, and / or the like) to be in communication with another unit means that the one unit is able to directly or indirectly receive information from and / or transmit information to the other unit. This may refer to a direct or indirect connection (e.g., a direct communication connection, an indirect communication connection, and / or the like) that is wired and / or wireless in nature. Additionally, two units may be in communication with each other even though the information transmitted may be modified, processed, relayed, and / or routed between the first and second unit. For example, a first unit may be in communication with a second unit even though the first unit passively receives information and does not actively transmit information to the second unit. As another example, a first unit may be in communication with a second unit if at least one intermediary unit (e.g., a third unit located between the first unit and the second unit) processes information received from the first unit and communicates the processed information to the second unit. In some non-limiting embodiments, a message may refer to a network packet (e.g., a data packet and / or the like) that includes data. It will be appreciated that numerous other arrangements are possible.

[0032] As used herein, the term "processor" may refer to any suitable data computation device or devices. A processor may comprise one or more microprocessors working together to accomplish a desired function. The processor may include CPU comprises at least one high-speed data processor adequate to execute program components for executing user and / or system-generated requests. The CPU may be a microprocessor such as AMD's Athlon, Duron and / or Opteron; IBM and / or Motorola's PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Itanium, Pentium, Xeon, and / or XScale; and / or the like processor(s).

[0033] As used herein, the term "memory" may be any suitable device or devices that can store electronic data. A suitable memory may comprise a non-transitory computer readable medium that stores instructions that can be executed by a processor to implement a desired method. Examples of memories may comprise one or more memory chips, disk drives, etc. Such memories may operate using any suitable electrical, optical, and / or magnetic mode of operation.

[0034] In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0035] Fig. 1A illustrates call capacity management as per existing methodologies. In existing methodologies deployment of 3GPP devices (such as UE 103 in Fig. 1A) are much higher compared deployment of N3GPP devices (such as UE 104 in Fig. 1A). As illustrated in Fig. 1A, incoming call rate of 3GPP devices (X%) is much greater when compared with incoming call rate of N3GPP devices (Y%). In existing methodologies, there is a common call admission policy which is access medium agnostic, which results in incoming calls being admitted based on the order of arrival. This is disadvantageous to N3GPP devices, as the system resources are consumed more by the access type whose call initiation rate is higher, which in this case is 3GPP devices. This leads to resource deprivation for connection arising from N3GPP access type, as the call generation rate of N3GPP access type is lesser than 3GPP access type. Further, in existing systems there is no resource optimization during underutilization period and the existing methodologies also do not support dynamic capacity allocation.

[0036] Fig. 1B illustrates an environment 100 for dynamic call admission capacity management in a communication network. The environment 100 may comprise of consumer network entities 101 and a Network Data Analytics Function (NWDAF) entity 102. The consumer network entities 101 may further comprise of an Access and Mobility Management Function (AMF) 101a and a Session Management Function (SMF) 101b. The various components such as the consumer network entities 101 including the AMF 101a and the SMF 101b and the NWDAF entity 102 belong to a communication network and may be implemented as software or hardware components. The system for dynamic call admission capacity management in the communication network may comprise of the consumer network entities 101 including the AMF 101a and the SMF 101b and the NWDAF entity 102. The NWDAF entity (102) and the consumer network entities 101 including the AMF 101a and the SMF 101b may be implemented as network functions and may be hosted on network server as a Cloud-native Network Function (CNF) or a Virtual Network Function (VNF).

[0037] In an embodiment, the consumer network entities 101 may send to the NWDAF entity 102 an initial capacity allocation request for both 3GPP and N3GPP access types.

[0038] In an embodiment the NWDAF entity 102 may determine a capacity recommendation in response to the initial capacity allocation request. The capacity recommendation may be determined based on call data and network related data. The NWDAF entity 102 may determine the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from Operations, Administration and Maintenance　(OAM), using an Artificial Intelligence (AI) model. The AI model may use real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized.

[0039] In an embodiment the NWDAF entity 102 may send the capacity recommendation to the one or more consumer network entities 101. For example, the NWDAF entity 102 may assign 40% of the bandwidth for the 3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_3GPP as 40%. The NWDAF entity 102 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_N3GPP as 20%. For example, the NWDAF entity 102 may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP). Therefore, guaranteed free-pool bandwidth may be assigned as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0040] In an embodiment, sending by the one or more consumer network entities 101 to the NWDAF entity 102, a capacity re-allocation request, when the capacity recommendation does not meet defined criteria. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example when a current call rate of a given access types exceeds that of its assigned guaranteed bandwidth, the consumer network entities 101 may locally balance the load by borrowing bandwidth from the guaranteed free-pool bandwidth. For example, if the current call rate of 3GPP access type is 80%, of the bandwidth, and the guaranteed bandwidth for 3GPP access type is 40%, then the consumer network entities 101 may re-assign 40% AvailableBWInFreePool to the GuaranteedBW_3GPP. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of the available free pool bandwidth combined (i.e., if CurrentCallRate >= (GuaranteedBW+ AvailableBWInFreePool)), for example, if the current call rate of 3GPP access type exceeds 80% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102.

[0041] In an embodiment the NWDAF entity 102 performs dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101. Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, if consumer network entities 101 has requested for capacity re-allocation as the current call rate of 3GPP access type: CurrCallRate_3GPP >= (guaranteedBW_3GPP+AvailableBWInFreePool)], the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 45% of the bandwidth being reserved for 3GPP access type and 15% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0042] 3GPP = guaranteedBW_3GPP 45;

[0043] N3GPP = guaranteedBW_3GPP 15.

[0044] In an embodiment the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0045] In another embodiment, when the current call rate of the both the access types of the plurality of access types exceed their respective guaranteed admissible call capacity bandwidth allocated (for example, without limiting to, when the guaranteedBW_3GPP is 40% and guaranteedBW_N3GPP is 20%, and the (CurrCallRate_3GPP >= guaranteedBW_3GPP) && (CurrCallRate_3GPP >=guaranteedBW_N3GPP)), the one or more consumer network entities 101 may perform local load balancing from the guaranteed free-pool bandwidth and based on the current call rate of both the 3GPP access type and the 3GPP access type, an a pro-rata basis. For example, without limiting to, based on local load balancing, the capacity of 3GPP access type may be updated to 60% and the capacity of N3GPP access type may be updated to 40%.

[0046] Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of re-allocated bandwidth (by the one or more consumer entities 101) from the guaranteed free-pool bandwidth based on the current call rate of the access type combined (i.e., for example, when [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))]), for example, when the current call rate of 3GPP access type exceeds 60% and when the current call rate of N3GPP access type exceeds 40% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102. In an embodiment the NWDAF entity 102 performs dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101.

[0047] Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, when the consumer network entities 101 have requested for capacity re-allocation as the current call rate of 3GPP and N3GPP access type have exceeded that of the guaranteed bandwidth allocated to 3GPP and N3GPP access type respectively, and that of re-allocated bandwidth from the guaranteed free-pool bandwidth based on the current call rate of the access type, combined, (i.e., [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))] and [CurrCallRate_N3GPP >= (guaranteedBW_N3GPP+(AvailableBWInFreePool % CurrCallRate_N3GPP))]), the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 60% of the bandwidth being reserved for 3GPP access type and 40% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0048] 3GPP = guaranteedBW_3GPP 60;

[0049] N3GPP = guaranteedBW_3GPP 40.

[0050] In an embodiment the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0051] In an embodiment, when the current call rate of a given access type of the plurality of access types exceeds that of the updated capacity recommendation value, and the guaranteed free-pool bandwidth in unavailable and when the other access type of the plurality of access types also do not have unused resources, the one or more consumer network entities 101, may drop incoming calls.

[0052] In another embodiment, the NWDAF entity 102 may determine that the one or more consumer network entities 101 under-utilize the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. In this case, the NWDAF entity 102 may send updated guaranteed bandwidths for at least one of the plurality of access types. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then the NWDAF entity 102 may send an updated capacity recommendation to the one or more consumer network entities 101 as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0053] Fig. 2 illustrates access aware dynamic call admission capacity management in a communication network, in accordance with some embodiments of the present disclosure.

[0054] The method of the present disclosure performs dynamic call admission capacity management by performing bandwidth distinction between 3GPP and N3GPP calls, based on capacity utilization analytical data derived by the NWDAF entity 102. The NWDAF entity 102 may provide a capacity recommendation for 3GPP and N3GPP capacity utilization. The method of the present disclosure performs dynamic load balancing of call capacity across 3GPP and N3GPP access types for better resource utilization. The NWDAF entity 102 provides a capacity recommendation to the one or more consumer network entities 101 (AMF 101a / SMF 101b) 101 comprising guaranteed admissible call capacity bandwidth per access type and a guaranteed free-pool bandwidth. The one or more consumer network entities 101 admit calls based on the capacity recommendation sent by the NWDAF entity 102. GuaranteedBW AvailableBWInFreePool is the available capacity in free pool which can be loaned to any access type if their call BW is over-utilized.

[0055] Fig. 3 illustrates a detailed a block diagram of a consumer network entity 101. The consumer network entities 101 may comprise of a processor 303, an input / output (I / O) interface 302, a memory 304 and modules 306. The memory 304 may further comprise of data 305. The modules 306 may further comprise of modules such as without limitation to, a transceiver module 307, a re-allocation request module 308, a load balancing module 309, and other modules 310.

[0056] In an embodiment, the data 305 may include various temporary data and files generated by the modules 306.

[0057] As used herein, the term module may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a hardware processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable components that provide the described functionality. In an implementation, each of the modules 306 may be configured as stand-alone hardware computing units. In an embodiment, the other modules 310 may be used to perform various miscellaneous functionalities of the consumer network entities 101. It will be appreciated that such the modules 306 may be represented as a single module or a combination of different modules.

[0058] In an embodiment, the transceiver module 307 may be configured to send to the NWDAF entity 102 an initial capacity allocation request for both 3GPP and N3GPP access types.

[0059] In an embodiment, the transceiver module 307 may be configured to receive a capacity recommendation in response to the initial capacity allocation request. The capacity recommendation may be determined based on call data and network related data. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized. For example, the NWDAF entity 102 may assign 40% of the bandwidth for the 3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_3GPP as 40%. The NWDAF entity 102 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_N3GPP as 20%. For example, the NWDAF entity may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP). Therefore, guaranteed free-pool bandwidth may be assigned as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0060] In an embodiment, the re-allocation request module 308 may send to the NWDAF entity 102, a capacity re-allocation request, when the capacity recommendation does not meet defined criteria. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example when a current call rate of a given access types exceeds that of its assigned guaranteed bandwidth, the load balancing module 309 may locally balance the load by borrowing bandwidth from the guaranteed free-pool bandwidth. For example, if the current call rate of 3GPP access type is 80%, of the bandwidth, and the guaranteed bandwidth for 3GPP access type is 40%, then the load balancing module 309 may re-assign 40% AvailableBWInFreePool to the GuaranteedBW_3GPP. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of the available free pool bandwidth combined (i.e., if CurrentCallRate >= (GuaranteedBW+ AvailableBWInFreePool)), for example, if the current call rate of 3GPP access type exceeds 80% in the above example, this may act as the trigger for the re-allocation request module 308 to send the capacity re-allocation request the NWDAF entity 102.

[0061] The updated capacity recommendation may be provided as CAPAUpdateResponse

[0062] 3GPP = guaranteedBW_3GPP 45;

[0063] N3GPP = guaranteedBW_3GPP 15.

[0064] In an embodiment the transceiver module 307 may receive from the NWDAF entity 102 an updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources based on dynamic load balancing performed by the NWDAF entity 102. The transceiver module 307 may use the updated capacity recommendation for performing call admission and congestion control.

[0065] In another embodiment, when the current call rate of the both the access types of the plurality of access types exceed their respective guaranteed admissible call capacity bandwidth allocated (for example, without limiting to, when the guaranteedBW_3GPP is 40% and guaranteedBW_N3GPP is 20%, and the (CurrCallRate_3GPP >= guaranteedBW_3GPP) && (CurrCallRate_3GPP >=guaranteedBW_N3GPP)), the load balancing module 309 may perform local load balancing from the guaranteed free-pool bandwidth and based on the current call rate of both the 3GPP access type and the 3GPP access type, an a pro-rata basis. For example, without limiting to, based on local load balancing, the capacity of 3GPP access type may be updated to 60% and the capacity of N3GPP access type may be updated to 40%.

[0066] Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of re-allocated bandwidth (by the load balancing module 309) from the guaranteed free-pool bandwidth based on the current call rate of the access type combined (i.e., for example, when [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))]), for example, when the current call rate of 3GPP access type exceeds 60% and when the current call rate of N3GPP access type exceeds 40% in the above example, this may act as the trigger for the re-allocation request module 308 to send the capacity re-allocation request the NWDAF entity 102.

[0067] In an embodiment the NWDAF entity 102 may perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101 and the updated capacity recommendation may be provided as CAPAUpdateResponse

[0068] 3GPP = guaranteedBW_3GPP 60;

[0069] N3GPP = guaranteedBW_3GPP 40.

[0070] In an embodiment the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the transceiver module 307. The transceiver module 307 may use the updated capacity recommendation for performing call admission and congestion control.

[0071] In an embodiment, when the current call rate of a given access type of the plurality of access types exceeds that of the updated capacity recommendation value, and the guaranteed free-pool bandwidth in unavailable and when the other access type of the plurality of access types also do not have unused resources, the transceiver module 307, may drop incoming calls.

[0072] In another embodiment, the transceiver module 307 may receive an updated guaranteed bandwidths for at least one of the plurality of access types when the NWDAF entity 102 determines that the transceiver module 307 under-utilizes the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then the NWDAF entity 102 may send an updated capacity recommendation to the transceiver module 308 as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0073] Fig. 4 illustrates a detailed a block diagram of the NWDAF entity 102. The NWDAF entity 102 may comprise of a processor 403, an input / output (I / O) interface 402, a memory 404 and modules 406. The memory 404 may further comprise of data 405. The modules 406 may further comprise of modules such as without limitation to, a transceiver module 407, a capacity recommendation module 408, a load balancing module 409, and other modules 410.

[0074] In an embodiment, the data / 405 may include various temporary data and files generated by the modules 406.

[0075] As used herein, the term module may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a hardware processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable components that provide the described functionality. In an implementation, each of the modules 406 may be configured as stand-alone hardware computing units. In an embodiment, the other modules 409 may be used to perform various miscellaneous functionalities of the NWDAF entity 102. It will be appreciated that such the modules 406 may be represented as a single module or a combination of different modules.

[0076] In an embodiment, the transceiver module 407 may receive an initial capacity allocation request for both 3GPP and N3GPP access types from one or more consumer network entities 101.

[0077] In an embodiment the capacity recommendation module 408 may be configured to determine a capacity recommendation in response to the initial capacity allocation request. The capacity recommendation may be determined based on call data and network related data. The capacity recommendation module 408 may determine the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from Operations, Administration and Maintenance　(OAM), using an Artificial Intelligence (AI) model. The AI model may use real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized.

[0078] In an embodiment the transceiver module 407 may send the capacity recommendation to the one or more consumer network entities 101. For example, the capacity recommendation module 408 may assign 40% of the bandwidth for the 3GPP access type, i.e., the capacity recommendation module 408 may assign: guaranteedBW_3GPP as 40%. The capacity recommendation module 408 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the capacity recommendation module 408 may assign: guaranteedBW_N3GPP as 20%. For example, the capacity recommendation module 408 may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP). Therefore, guaranteed free-pool bandwidth may be assigned as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0079] In an embodiment, the transceiver module 407 may receive a capacity re-allocation request from the one or more consumer network entities 101, when the capacity recommendation does not meet defined criteria. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example when a current call rate of a given access types exceeds that of its assigned guaranteed bandwidth, the consumer network entities 101 may locally balance the load by borrowing bandwidth from the guaranteed free-pool bandwidth. For example, if the current call rate of 3GPP access type is 80%, of the bandwidth, and the guaranteed bandwidth for 3GPP access type is 40%, then the consumer network entities 101 may re-assign 40% AvailableBWInFreePool to the GuaranteedBW_3GPP. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of the available free pool bandwidth combined (i.e., if CurrentCallRate >= (GuaranteedBW+ AvailableBWInFreePool)), for example, if the current call rate of 3GPP access type exceeds 80% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the transceiver module 407.

[0080] In an embodiment the load balancing module 409 performs dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101. Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, if consumer network entities 101 has requested for capacity re-allocation as the current call rate of 3GPP access type: CurrCallRate_3GPP >= (guaranteedBW_3GPP+AvailableBWInFreePool)], the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 45% of the bandwidth being reserved for 3GPP access type and 15% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0081] 3GPP = guaranteedBW_3GPP 45;

[0082] N3GPP = guaranteedBW_3GPP 15.

[0083] In an embodiment the transceiver module 407 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0084] In another embodiment, when the current call rate of the both the access types of the plurality of access types exceed their respective guaranteed admissible call capacity bandwidth allocated (for example, without limiting to, when the guaranteedBW_3GPP is 40% and guaranteedBW_N3GPP is 20%, and the (CurrCallRate_3GPP >= guaranteedBW_3GPP) && (CurrCallRate_3GPP >=guaranteedBW_N3GPP)), the one or more consumer network entities 101 may perform local load balancing from the guaranteed free-pool bandwidth and based on the current call rate of both the 3GPP access type and the 3GPP access type, an a pro-rata basis. For example, without limiting to, based on local load balancing, the capacity of 3GPP access type may be updated to 60% and the capacity of N3GPP access type may be updated to 40%. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of re-allocated bandwidth (by the one or more consumer entities 101) from the guaranteed free-pool bandwidth based on the current call rate of the access type combined (i.e., for example, when [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))]), for example, when the current call rate of 3GPP access type exceeds 60% and when the current call rate of N3GPP access type exceeds 40% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the transceiver module 407. In an embodiment the load balancing module 409 may perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101.

[0085] Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, when the consumer network entities 101 have requested for capacity re-allocation as the current call rate of 3GPP and N3GPP access type have exceeded that of the guaranteed bandwidth allocated to 3GPP and N3GPP access type respectively, and that of re-allocated bandwidth from the guaranteed free-pool bandwidth based on the current call rate of the access type, combined, (i.e., [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))] and [CurrCallRate_N3GPP >= (guaranteedBW_N3GPP+(AvailableBWInFreePool % CurrCallRate_N3GPP))]), the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 60% of the bandwidth being reserved for 3GPP access type and 40% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0086] 3GPP = guaranteedBW_3GPP 60;

[0087] N3GPP = guaranteedBW_3GPP 40.

[0088] In an embodiment the transceiver module 407 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0089] In another embodiment, the capacity recommendation module 408 may determine that the one or more consumer network entities 101 under-utilize the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. In this case, the capacity recommendation module 408 may send updated guaranteed bandwidths for at least one of the plurality of access types. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then the capacity recommendation module 408 may send an updated capacity recommendation to the one or more consumer network entities 101 as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0090] Fig. 5A depicts a message flow diagram of an exemplary method for dynamic call admission capacity management between the AMF 101a and the NWDAF entity 102.

[0091] At step 1 of Fig. 5A, the AMF 101a may send the initial capacity to the NWDAF entity 102.

[0092] At step 2 of Fig. 5A, the NWDAF entity 102 may determine and send a capacity recommendation in response to the initial capacity allocation to the AMF 101a. The capacity recommendation may be determined based on call data and network related data. The NWDAF entity 102 may determine the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from Operations, Administration and Maintenance　(OAM), using an Artificial Intelligence (AI) model. The AI model may use real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized. For example, the NWDAF entity 102 may assign 40% of the bandwidth for the 3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_3GPP as 40%. The NWDAF entity 102 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_N3GPP as 20%. For example, the NWDAF entity 102 may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP).

[0093] At step 3 of Fig. 5A the guaranteed free-pool bandwidth may be determined as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0094] At step 4 of Fig. 5A when a current call rate of a given access types exceeds that of its assigned guaranteed bandwidth, the AMF 101a may locally balance the load by borrowing bandwidth from the guaranteed free-pool bandwidth. For example, if the current call rate of 3GPP access type is 80%, of the bandwidth, and the guaranteed bandwidth for 3GPP access type is 40%, then the AMF 101a may re-assign 40% AvailableBWInFreePool to the GuaranteedBW_3GPP.

[0095] At step 5 of Fig. 5A, when the capacity recommendation does not meet defined criteria, at step 6 of Fig. 5A, the AMF 101a may send a capacity re-allocation request to the NWDAF entity 102. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of the available free pool bandwidth combined (i.e., if CurrentCallRate >= (GuaranteedBW+ AvailableBWInFreePool)), for example, if the current call rate of 3GPP access type exceeds 80% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102.

[0096] At step 7 of Fig 5A, the NWDAF entity 102 performs dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the AMF 101a. Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, if the AMF 101a has requested for capacity re-allocation as the current call rate of 3GPP access type: CurrCallRate_3GPP >= (guaranteedBW_3GPP+AvailableBWInFreePool)], the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 45% of the bandwidth being reserved for 3GPP access type and 15% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0097] 3GPP = guaranteedBW_3GPP 45;

[0098] N3GPP = guaranteedBW_3GPP 15.

[0099] At step 8 of Fig 5A, the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the AMF 101a. The AMF 101a may use the updated capacity recommendation for performing call admission and congestion control.

[0100] At step 9 of Fig 5A, the NWDAF entity 102 may determine that AMF 101a under-utilizes the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. In this case, the NWDAF entity 102 may send updated guaranteed bandwidths for at least one of the plurality of access types. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then the NWDAF entity 102 may send an updated capacity recommendation to the AMF 101a as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0101] Fig. 5B depicts another message flow diagram of an exemplary method for dynamic call admission capacity management between the AMF 101a and the NWDAF entity 102.

[0102] At step 1 of Fig. 5B, the AMF 101a may send the initial capacity to the NWDAF entity 102.

[0103] At step 2 of Fig. 5B, the NWDAF entity 102 may determine and send a capacity recommendation in response to the initial capacity allocation to the AMF 101a. The capacity recommendation may be determined based on call data and network related data. The NWDAF entity 102 may determine the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from Operations, Administration and Maintenance　(OAM), using an Artificial Intelligence (AI) model. The AI model may use real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized. For example, the NWDAF entity 102 may assign 40% of the bandwidth for the 3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_3GPP as 40%. The NWDAF entity 102 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_N3GPP as 20%. For example, the NWDAF entity 102 may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP).

[0104] At step 3 of Fig. 5B the guaranteed free-pool bandwidth may be determined as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0105] At step 4 of Fig. 5B when the current call rate of the both the access types of the plurality of access types exceed their respective guaranteed admissible call capacity bandwidth allocated (for example, without limiting to, when the guaranteedBW_3GPP is 40% and guaranteedBW_N3GPP is 20%, and the (CurrCallRate_3GPP >= guaranteedBW_3GPP) && (CurrCallRate_3GPP >=guaranteedBW_N3GPP)), the AMF 101a may may perform local load balancing from the guaranteed free-pool bandwidth and based on the current call rate of both the 3GPP access type and the 3GPP access type, an a pro-rata basis. For example, without limiting to, based on local load balancing, then the AMF 101a may may update the capacity of 3GPP to 60% and the capacity of N3GPP access type may be updated to 40%.

[0106] At step 5 of Fig. 5B, when the capacity recommendation does not meet defined criteria, at step 6 of Fig. 5A, the AMF 101a may send a capacity re-allocation request to the NWDAF entity 102. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of re-allocated bandwidth (by the AMF 101a) from the guaranteed free-pool bandwidth based on the current call rate of the access type combined (i.e., for example, when [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))]), for example, when the current call rate of 3GPP access type exceeds 60% and when the current call rate of N3GPP access type exceeds 40% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102. In an embodiment the NWDAF entity 102 performs dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the AMF 101a.

[0107] At step 7 of Fig 5B, the NWDAF entity 102 performs dynamic load balancing by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, when the AMF 101a has requested for capacity re-allocation as the current call rate of 3GPP and N3GPP access type have exceeded that of the guaranteed bandwidth allocated to 3GPP and N3GPP access type respectively, and that of re-allocated bandwidth from the guaranteed free-pool bandwidth based on the current call rate of the access type, combined, (i.e., [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))] and [CurrCallRate_N3GPP >= (guaranteedBW_N3GPP+(AvailableBWInFreePool % CurrCallRate_N3GPP))]), the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 60% of the bandwidth being reserved for 3GPP access type and 40% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0108] 3GPP = guaranteedBW_3GPP 60;

[0109] N3GPP = guaranteedBW_3GPP 40.

[0110] At step 8 of Fig 5B, the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the AMF 101a. The AMF 101a may use the updated capacity recommendation for performing call admission and congestion control.

[0111] At step 9 of Fig 5B, when the current call rate of a given access type drops below that of the updated guaranteed bandwidth of that access type (i.e., for example, when CurrUsage_3GPP + 30, CurrUsage_N3GPP = 10), the the AMF 101a may send a capacity re-allocation request to the NWDAF entity 102.

[0112] At step 10 of Fig. 5B, the NWDAF entity 102 in response to receiving the capacity re-allocation request from the AMF 101a performs dynamic load balancing between the plurality of access types based on real time call utilization data, current load, and analytical call utilization data. The NWDAF entity 102 may determine that the AMF 101a under-utilizes the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. In this case, the NWDAF entity 102 may send updated guaranteed bandwidths for at least one of the plurality of access types. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then at step 11 of Fig. 5B, the NWDAF entity 102 may send an updated capacity recommendation to the AMF 101a as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0113] Fig. 5C depicts a message flow diagram of an exemplary method for dynamic call admission capacity management between consumer network entities 101, NWDAF 102 and OAM 501, in accordance with some embodiments of the present disclosure;

[0114] At step 1 of Fig. 5C, the NWDAF entity 102 collects call statistics data, configuration data, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types data from the OAM 501.

[0115] At step 2 of Fig. 5C, the NWDAF entity 102 generates the call capacity utilization factor for 3GPP and N3GPP access types based on the AI model. The AI model considers statistical Network Function (NF), Key Performance Indicators (KPI's), Call KPIs, load, alarms data, faults data.

[0116] At step 3 of Fig. 5C, the AMF 101a sends a Nnwdaf_AnalyticsInfo_Request to the NWDAF entity 102, based on expiry of the configurable NWDAF_Query_Timer. The Event ID may be set to "Call CAPA" and Snssais. Access type parameters may also be specified.

[0117] At step 4 of Fig. 5C, the NWDAF entity 102 may send to the AMF 101a Nnwdaf_AnalyticsInfo_Request response, which may comprise of requested Call CAPA analytics (GuaranteedBW for 3GPP / N3GPP)

[0118] At step 5 of Fig. 5C, the AMF 101a may send to the NWDAF entity 102, Nnwdaf_EventSubscription_Subscribe, which may allow the AMF 101a to subscribe to "Call CAPA" analytics with the NWDAF entity 102 on a periodic basis.

[0119] At step 6 of Fig. 5C, the NWDAF entity 102 collects call utilization statistics per access type, configuration data, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types data from the OAM 501.

[0120] At step 7 of Fig. 5C, the NWDAF entity 102 generates call capacity utilization analytics for the plurality of access types based on AI model that may consider, without limitation to, statistical NF KPIs, Call KPIs, load, Alarm, Faults etc.

[0121] At step 8 of Fig. 5C, the NWDAF entity 102 may send to the AMF 101a Nnwdaf_EventSubscription_Notify, which may include requested call CAPA analytics (GuaranteedBW for 3GPP / N3GPP) to AMF 101a.

[0122] At step 9 of Fig. 5C, when CAPA may be fully utilized due to congestion, the AMF 101a may start rejecting incoming calls. Alternatively, it can send CAPA update request to the NWDAF 102 for additional capacity allocation.

[0123] At step 10 of Fig. 5C, the AMF 101a may send to the NWDAF entity 102 Nnwdaf_AnalyticsInfo_Request, whilst setting Event ID to "Call CAPA" along with current call usage of each of the plurality of access types.

[0124] At step 11 of Fig. 5C, the NWDAF 102 may recommend an updated call CAPA value based on the received current usage of calls and the AI model result. In another embodiment, the NWDAF entity 102 may also reject this request, or send previous GuaranteedBW values.

[0125] At step 12 of Fig. 5C, the NWDAF entity 102 may send to the AMF 101a Nnwdaf_AnalyticsInfo_RequestResponse. The NWDAF entity 102 may provide requested updated call CAPA analytics (GuaranteedBW for 3GPP / N3GPP) to the AMF 101a.

[0126] At step 13 of Fig. 5C the NWDAF entity 102 may send to the AMF 101a Nnwdaf_EventSubscription_Notify. The NWDAF entity 102 may recommend an updated call CAPA value on its own based on latest call utilization data and results of the AI model.

[0127] Fig. 6 depicts a flow diagram of an exemplary method 600 for dynamic call admission capacity management in the communication network.

[0128] At step 601, the NWDAF entity 102 may be configured to determine a capacity recommendation in response to an initial capacity allocation request (for both 3GPP and N3GPP access types) received from one or more consumer network entities 101. The capacity recommendation may be determined based on call data and network related data. The NWDAF entity 102 may determine the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from Operations, Administration and Maintenance　(OAM), using an Artificial Intelligence (AI) model. The AI model may use real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized.

[0129] At step 602, the NWDAF entity 102 may send the capacity recommendation to the one or more consumer network entities 101. For example, the NWDAF entity 102 may assign 40% of the bandwidth for the 3GPP access type, i.e., the capacity recommendation module 408 may assign: guaranteedBW_3GPP as 40%. The NWDAF entity 102 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the capacity recommendation module 408 may assign: guaranteedBW_N3GPP as 20%. For example, the NWDAF entity 102 may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP). Therefore, guaranteed free-pool bandwidth may be assigned as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0130] At step 603, the NWDAF entity 102 may receive a capacity re-allocation request from the one or more consumer network entities 101, when the capacity recommendation does not meet defined criteria. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example when a current call rate of a given access types exceeds that of its assigned guaranteed bandwidth, the consumer network entities 101 may locally balance the load by borrowing bandwidth from the guaranteed free-pool bandwidth. For example, if the current call rate of 3GPP access type is 80%, of the bandwidth, and the guaranteed bandwidth for 3GPP access type is 40%, then the consumer network entities 101 may re-assign 40% AvailableBWInFreePool to the GuaranteedBW_3GPP. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of the available free pool bandwidth combined (i.e., if CurrentCallRate >= (GuaranteedBW+ AvailableBWInFreePool)), for example, if the current call rate of 3GPP access type exceeds 80% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102.

[0131] At step 604, the NWDAF entity 102 may perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101. Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, if consumer network entities 101 has requested for capacity re-allocation as the current call rate of 3GPP access type: CurrCallRate_3GPP >= (guaranteedBW_3GPP+AvailableBWInFreePool)], the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 45% of the bandwidth being reserved for 3GPP access type and 15% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0132] 3GPP = guaranteedBW_3GPP 45;

[0133] N3GPP = guaranteedBW_3GPP 15.

[0134] At step 605, the NWDAF entity 102 may may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0135] In another embodiment, when the current call rate of the both the access types of the plurality of access types exceed their respective guaranteed admissible call capacity bandwidth allocated (for example, without limiting to, when the guaranteedBW_3GPP is 40% and guaranteedBW_N3GPP is 20%, and the (CurrCallRate_3GPP >= guaranteedBW_3GPP) && (CurrCallRate_3GPP >=guaranteedBW_N3GPP)), the one or more consumer network entities 101 may perform local load balancing from the guaranteed free-pool bandwidth and based on the current call rate of both the 3GPP access type and the 3GPP access type, an a pro-rata basis. For example, without limiting to, based on local load balancing, the capacity of 3GPP access type may be updated to 60% and the capacity of N3GPP access type may be updated to 40%. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of re-allocated bandwidth (by the one or more consumer entities 101) from the guaranteed free-pool bandwidth based on the current call rate of the access type combined (i.e., for example, when [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))]), for example, when the current call rate of 3GPP access type exceeds 60% and when the current call rate of N3GPP access type exceeds 40% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102. In an embodiment the NWDAF entity 102 may perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101.

[0136] Dynamic load balancing may be performed by determining if there are unused network resources of the one or more consumer network entities 101 of at least one of the plurality of access types. For example, when the consumer network entities 101 have requested for capacity re-allocation as the current call rate of 3GPP and N3GPP access type have exceeded that of the guaranteed bandwidth allocated to 3GPP and N3GPP access type respectively, and that of re-allocated bandwidth from the guaranteed free-pool bandwidth based on the current call rate of the access type, combined, (i.e., [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))] and [CurrCallRate_N3GPP >= (guaranteedBW_N3GPP+(AvailableBWInFreePool % CurrCallRate_N3GPP))]), the NWDAF entity 102 may perform load balancing between the 3GPP access type and the N3GPP access type based on current load, analytical call utilization data etc., and provide the updated capacity recommendation as 60% of the bandwidth being reserved for 3GPP access type and 40% of the bandwidth being reserved for N3GPP access. The updated capacity recommendation may be provided as CAPAUpdateResponse

[0137] 3GPP = guaranteedBW_3GPP 60;

[0138] N3GPP = guaranteedBW_3GPP 40.

[0139] In an embodiment the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0140] In another embodiment, the NWDAF entity 102 may determine that the one or more consumer network entities 101 under-utilize the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. In this case, the NWDAF entity 102 may send updated guaranteed bandwidths for at least one of the plurality of access types. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then the NWDAF entity 102 may send an updated capacity recommendation to the one or more consumer network entities 101 as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0141] Fig. 7, depicts a flow diagram of an exemplary method 700 for dynamic call admission capacity management in a communication network.

[0142] At step 701, the one or more consumer network entities 101 may be configured to send to the NWDAF 102 entity an initial capacity allocation request for both 3GPP and N3GPP access types.

[0143] At step 702, the one or more consumer network entities 101 may be configured to receive a capacity recommendation in response to the initial capacity allocation request. The capacity recommendation may be determined (by the NWDAF entity 102) based on call data and network related data. The capacity recommendation may comprise a guaranteed free-pool bandwidth and a guaranteed admissible call capacity bandwidth per access type among a plurality of access types such as, without limitation to, 3GPP access and Non-3GPP (N3GPP) access. The guaranteed admissible call capacity bandwidth may refer to minimum percentage of bandwidth that may be allocated to each of the access types. The guaranteed free-pool bandwidth may refer to unused bandwidth that may not have been assigned to any of the access types. The guaranteed free-pool bandwidth may be used when the guaranteed bandwidths of any of the access types are fully utilized. For example, the NWDAF entity 102 may assign 40% of the bandwidth for the 3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_3GPP as 40%. The NWDAF entity 102 may assign 20% of the bandwidth for the non-3GPP access type, i.e., the NWDAF entity 102 may assign: guaranteedBW_N3GPP as 20%. For example, the NWDAF entity 102 may assign guaranteed free-pool bandwidth as: AvailableBWInFreePool = TotalBW - (GuaranteedBW_3GPP +GuaranteedBW_N3GPP). Therefore, guaranteed free-pool bandwidth may be assigned as: AvailableBWInFreePool = 100 - (40+20) = 40%.

[0144] At step 703, the one or more consumer network entities 101 may send to the NWDAF entity 102, a capacity re-allocation request, when the capacity recommendation does not meet defined criteria. The defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth. For example when a current call rate of a given access types exceeds that of its assigned guaranteed bandwidth, the one or more consumer network entities 101 may locally balance the load by borrowing bandwidth from the guaranteed free-pool bandwidth. For example, if the current call rate of 3GPP access type is 80%, of the bandwidth, and the guaranteed bandwidth for 3GPP access type is 40%, then one or more consumer network entities 101 may re-assign 40% AvailableBWInFreePool to the GuaranteedBW_3GPP. Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of the available free pool bandwidth combined (i.e., if CurrentCallRate >= (GuaranteedBW+ AvailableBWInFreePool)), for example, if the current call rate of 3GPP access type exceeds 80% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102.

[0145] The updated capacity recommendation may be provided as CAPAUpdateResponse

[0146] 3GPP = guaranteedBW_3GPP 45;

[0147] N3GPP = guaranteedBW_3GPP 15.

[0148] At step 704, the one or more consumer network entities 101 may receive from the NWDAF entity 102 an updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources based on dynamic load balancing performed by the NWDAF entity 102. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0149] In another embodiment, when the current call rate of the both the access types of the plurality of access types exceed their respective guaranteed admissible call capacity bandwidth allocated (for example, without limiting to, when the guaranteedBW_3GPP is 40% and guaranteedBW_N3GPP is 20%, and the (CurrCallRate_3GPP >= guaranteedBW_3GPP) && (CurrCallRate_3GPP >=guaranteedBW_N3GPP)), the one or more consumer network entities 101 may perform local load balancing from the guaranteed free-pool bandwidth and based on the current call rate of both the 3GPP access type and the 3GPP access type, an a pro-rata basis. For example, without limiting to, based on local load balancing, the capacity of 3GPP access type may be updated to 60% and the capacity of N3GPP access type may be updated to 40%.

[0150] Further, when the current call rate of a given access type exceeds that of the guaranteed bandwidth of that access type and that of re-allocated bandwidth (by the load balancing module 309) from the guaranteed free-pool bandwidth based on the current call rate of the access type combined (i.e., for example, when [CurrCallRate_3GPP >= (guaranteedBW_3GPP+(AvailableBWInFreePool % CurrCallRate_3GPP))]), for example, when the current call rate of 3GPP access type exceeds 60% and when the current call rate of N3GPP access type exceeds 40% in the above example, this may act as the trigger for the one or more consumer network entities 101 to send the capacity re-allocation request the NWDAF entity 102.

[0151] In an embodiment the NWDAF entity 102 may perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request from the one or more consumer network entities 101 and the updated capacity recommendation may be provided as CAPAUpdateResponse

[0152] 3GPP = guaranteedBW_3GPP 60;

[0153] N3GPP = guaranteedBW_3GPP 40.

[0154] In an embodiment the NWDAF entity 102 may send to the updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources to the one or more consumer network entities 101. The one or more consumer network entities 101 may use the updated capacity recommendation for performing call admission and congestion control.

[0155] At step 705, when the current call rate of a given access type of the plurality of access types exceeds that of the updated capacity recommendation value, and the guaranteed free-pool bandwidth in unavailable and when the other access type of the plurality of access types also do not have unused resources, the one or more consumer network entities 101 may drop incoming calls.

[0156] In another embodiment, the one or more consumer network entities 101 may receive an updated guaranteed bandwidths for at least one of the plurality of access types when the NWDAF entity 102 determines that the one or more consumer network entities 101 under-utilize the guaranteed bandwidth for at least one of the plurality of access types, based on load analytics. For example, when the guaranteed bandwidth for each of the plurality of access types are 3GPP = guaranteedBW_3GPP 60 and N3GPP = guaranteedBW_3GPP 40, and the current call rate of the plurality of access types is: CurrUsage_3GPP = 30 and CurrUsage_N3GPP = 10, then the NWDAF entity 102 may send an updated capacity recommendation to the one or more consumer network entities 101 as: 3GPP = guaranteedBW_3GPP 40% and N3GPP = guaranteedBW_3GPP 20%.

[0157] Fig. 8 illustrates a block diagram of an exemplary computer system 800 for implementing embodiments consistent with the present disclosure. The computer system may be, without limitation to, the NWDAF entity 102, the one or more consumer network entities 101 (including but not limited to AMF 101a, SMF 101b), the UE 201 (3GPP access) the UE 202 (N3GPP access). The computer system 800 may include a central processing unit ("CPU" or "processor") 801. The processor 801 may include at least one data processor for executing processes. The processor 801 may include specialized processing units such as, integrated system (bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.

[0158] The processor 801 may be disposed in communication with one or more input / output (I / O) devices 808 and 809 via I / O interface 807. The I / O interface 807 may employ communication protocols / methods such as, without limitation, audio, analog, digital, monaural, RCA, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), RF antennas, S-Video, VGA, IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc.

[0159] Using the I / O interface 807, the computer system 800 may communicate with one or more I / O devices 808 and 809. For example, the input devices 808 may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, stylus, scanner, storage device, transceiver, video device / source, etc. The output devices 809 may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, Plasma display panel (PDP), Organic light-emitting diode display (OLED) or the like), audio speaker, etc.

[0160] In some embodiments, the processor 801 may be disposed in communication with external elements such as external computer systems, servers, network elements. The network interface 810 may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), transmission control protocol / internet protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc.

[0161] In some embodiments, the processor 801 may be disposed in communication with a memory 803 (e.g., RAM, ROM, etc.) via a storage interface 802. The storage interface 802 may connect to memory 803 including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as, serial advanced technology attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fibre channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.

[0162] The memory 803 may store a collection of program or database components, including, without limitation, user interface 804, an operating system 805, a web browser 806 etc. In some embodiments, computer system 800 may store user / application data, such as, the data, variables, records, etc., as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle® or Sybase®

[0163] The operating system 805 may facilitate resource management and operation of the computer system 600. Examples of operating systems include, without limitation, APPLE MACINTOSH® OS X, UNIX®, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTION™ (BSD), FREEBSD™, NETBSD™, OPENBSD™, etc.), LINUX DISTRIBUTIONS™ (E.G., RED HAT™, UBUNTU™, KUBUNTU™, etc.), IBM™ OS / 2, MICROSOFT™ WINDOWS™ (XP™, VISTA™ / 7 / 8, 10 etc.), APPLE® IOS™, GOOGLE® ANDROID™, BLACKBERRY® OS, or the like.

[0164] In some embodiments, the computer system 800 may implement the web browser 806 stored program components. The web browser 806 may be a hypertext viewing application, such as MICROSOFT® INTERNET EXPLORER®, GOOGLE™ CHROME™, MOZILLA® FIREFOX®, APPLE® SAFARI®, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers 806 may utilize facilities such as AJAX, DHTML, ADOBE® FLASH®, JAVASCRIPT®, JAVA®, Application Programming Interfaces (APIs), etc. In some embodiments, the computer system 800 may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as Active Server Pages (ASP), ACTIVEX®, ANSI® C++ / C#, MICROSOFT®, .NET, CGI SCRIPTS, JAVA®, JAVASCRIPT®, PERL®, PHP, PYTHON®, WEBOBJECTS®, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT® exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system 800 may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLE® MAIL, MICROSOFT® ENTOURAGE®, MICROSOFT® OUTLOOK®, MOZILLA® THUNDERBIRD®, etc.

[0165] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media.

[0166] The described operations may be implemented as a method, system or article of manufacture using standard programming and / or engineering techniques to produce software, firmware, hardware, or any combination thereof.　The described operations may be implemented as code maintained in a "non-transitory computer readable medium", where a processor may read and execute the code from the computer readable medium. The processor is at least one of a microprocessor and a processor capable of processing and executing the queries. A non-transitory computer readable medium may include media such as magnetic storage medium (e.g., hard disk drives, floppy disks, tape, etc.), optical storage (CD-ROMs, DVDs, optical disks, etc.), volatile and non-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs, SRAMs, Flash Memory, firmware, programmable logic, etc.), etc. Further, non-transitory computer-readable media may include all computer-readable media except for a transitory. The code implementing the described operations may further be implemented in hardware logic (e.g., an integrated circuit chip, Programmable Gate Array (PGA), Application Specific Integrated Circuit (ASIC), etc.).

[0167] An "article of manufacture" includes non-transitory computer readable medium, and / or hardware logic, in which code may be implemented.　A device in which the code implementing the described embodiments of operations is encoded may include a computer readable medium or hardware logic. Of course, those skilled in the art will recognize that many modifications may be made to this configuration without departing from the scope of the invention, and that the article of manufacture may include suitable information bearing medium known in the art.

[0168] The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.

[0169] The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly specified otherwise.

[0170] The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

[0171] The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.

[0172] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.

[0173] When a single device or article is described herein, it will be readily apparent that more than one device / article (whether or not they cooperate) may be used in place of a single device / article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device / article may be used in place of the more than one device or article, or a different number of devices / articles may be used instead of the shown number of devices or programs. The functionality and / or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality / features. Thus, other embodiments of the invention need not include the device itself.

[0174] The above described one or more embodiments, may have the advantageous effect that, they provide a framework for providing uninterrupted resources to N3GPP devices (UE 202) and promotes N3GPP use cases of 5G. The above described one or more embodiments reduces the connection time for each user registration and each bearer establishment. The above described one or more embodiments aids the network in maintaining Service Level Agreement (SLA) during congestion and provides enhanced resource utilization by dynamic load balancing of resources between 3GPP and N3GPP access types. Further, the above described one or more embodiments may have that the effect that there is a faster recovery from congestion state at 5G Core as congestion control is performed considering traffic generation rate per access type. They also allow for a better chance of connection for calls originating from a access medium type, during congestion state. They also increase the system capacity by re-using the unused system bandwidth.

[0175] The illustrated operations of figures 5A, 5B, 5C, 7 and 8 show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified, or removed. Moreover, steps may be added to the above-described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel.　Yet further, operations may be performed by a single processing unit or by distributed processing units.

[0176] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

[0177] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

1.A method performed by a network data analytics function (NWDAF) entity for dynamic call admission capacity management in a communication network, comprising:determining a capacity recommendation in response to an initial capacity allocation request from one or more consumer network entities, the capacity recommendation indicating at least a guaranteed admissible call capacity bandwidth for a plurality of access types;sending, to the one or more consumer network entities, the capacity recommendation;receiving a capacity re-allocation request from the one or more consumer network entities, when the capacity recommendation does not meet defined criteria;performing dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request; andsending, to the one or more consumer network entities, an updated capacity recommendation for performing call admission and congestion control based on the updated capacity recommendation from the NWDAF entity.2.The method of claim 1,wherein the capacity recommendation is based on call data and network related data,wherein the capacity recommendation comprises at least one of: a guaranteed admissible call capacity bandwidth per access type among a plurality of access types and a guaranteed free-pool bandwidth, andwherein the plurality of access types comprises of 3GPP access and non-3GPP (N3GPP) access.3.The method of claim 1, wherein the NWDAF entity determines the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from an OAM using an artificial intelligence (AI) model, wherein the AI model uses real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output.4.The method of claim 1, wherein performing dynamic load balancing further comprises of:determining if there are unused network resources of the one or more consumer network entities of at least one of the plurality of access types;dynamically allocating unused network resources of the one or more consumer network entities of at least one of the plurality of access types to at least one other access type of the plurality of access types; andsending, to one or more consumer network entities, an updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources.5.The method of claim 4, wherein dynamically allocating unused network resources of the one or more consumer network entities, of at least one of the plurality of access types to at least one other access type of the plurality of access types comprises of: the NWDAF entity data determining based on the capacity recommendation, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from OAM using an artificial intelligence (AI) model, wherein the AI model uses the capacity recommendation, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the updated capacity recommendation as an output.6.The method of claim 1, wherein the call data and the network related data comprises at least one of, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from operations, administration, maintenance (OAM), wherein the plurality of access types comprises of 3GPP access and non-3GPP (N3GPP) access.7.The method of claim 1, wherein the defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth.8.A network data analytics function (NWDAF) entity for dynamic call admission capacity management in a communication network, comprising:a processor; anda memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:determine a capacity recommendation in response to an initial capacity allocation request from one or more consumer network entities, the capacity recommendation indicating at least a guaranteed admissible call capacity bandwidth for a plurality of access types;send, to the one or more consumer network entities, the capacity recommendation;receive a capacity re-allocation request from the one or more consumer network entities, when the capacity recommendation does not meet defined criteria;perform dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request; andsend, to one or more consumer network entities, an updated capacity recommendation for performing call admission and congestion control based on the updated capacity recommendation from the NWDAF entity.9.The NWDAF entity of claim 8,wherein the capacity recommendation is based on call data and network related data,wherein the capacity recommendation comprises at least one of: a guaranteed admissible call capacity bandwidth per access type among a plurality of access types and a guaranteed free-pool bandwidth, andwherein the plurality of access types comprises of 3GPP access and non-3GPP (N3GPP) access.10.The NWDAF entity of claim 8, wherein the processor is configured to determine the capacity recommendation based on real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from OAM using an artificial intelligence (AI) model, wherein the AI model uses real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the capacity recommendation as an output.11.The NWDAF entity of claim 8, wherein the processor configured to perform the dynamic load balancing is further configured to:determine if there are unused network resources of the one or more consumer network entities of at least one of the plurality of access types;dynamically allocate unused network resources of the one or more consumer network entities, of at least one of the plurality of access types to at least one other access type of the plurality of access types; andsend, to one or more consumer network entities, an updated capacity recommendation on bandwidth to be allocated for each of the plurality of access types based on the dynamic allocation of the unused network resources.12.The NWDAF entity of claim 11, wherein the processor configured to dynamically allocate unused network resources of the one or more consumer network entities, of at least one of the plurality of access types to at least one other access type of the plurality of access types, is configured to:determine based on the capacity recommendation, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from OAM using an artificial intelligence (AI) model, wherein the AI model uses the capacity recommendation, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types as an input and gives the updated capacity recommendation as an output.13.The NWDAF entity of claim 8, wherein the call data and the network related data comprises at least one of, real time call pattern data, network configuration data, historic call pattern data and dimensioning of the plurality of access types fetched from operations, administration, maintenance (OAM), wherein the plurality of access types comprises of 3GPP access and non-3GPP (N3GPP) access.14.The NWDAF entity of claim 8, wherein the defined criteria comprises at least one of: the guaranteed admissible call capacity bandwidth for a access type of the plurality of access types exceeding a threshold and non-availability of guaranteed free-pool bandwidth or when the guaranteed admissible call capacity bandwidth for all the access types of the plurality of access types has exceeded and there is no availability of guaranteed free-pool bandwidth.15.A consumer network entity for dynamic call admission capacity management in a communication network, comprising:a processor; anda memory, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:send, to a network data analytics function (NWDAF) entity, an initial capacity allocation request;receive, from the NWDAF entity, a capacity recommendation in response to the initial capacity allocation request, the capacity recommendation indicating at least a guaranteed admissible call capacity bandwidth for a plurality of access types;send, to the NWDAF entity, a capacity re-allocation request, when the capacity recommendation does not meet defined criteria;receive, from the NWDAF entity, an updated capacity recommendation for performing call admission and congestion control based on the capacity recommendation from the NWDAF entity, wherein the updated capacity recommendation is received based on the NWDAF entity performing dynamic load balancing between the plurality of access types based on real time call utilization data in response to receiving the capacity re-allocation request; anddrop incoming calls of an access type of the plurality of access types when the updated capacity recommendation on bandwidth allocated for each of the plurality of access types has exceeded.

Images