Virtual network function management

By dynamically managing the life cycle of VNF in a cellular communication network and selecting the appropriate mode of VNF processing requests, the problem of resource waste in virtualized network functions in idle mode is solved, and processing efficiency and resource utilization are improved.

CN118900240APending Publication Date: 2024-11-05NOKIA NETWORKS OY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410521923.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-02
Filing Date
2024-04-28
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In cellular communication networks, virtualized network functions (VNFs) remain in idle mode for a long time lead to waste of resources and increased computational complexity, and the prior art is difficult to effectively manage and optimize the life cycle of VNFs, resulting in inefficiency.

Method used

The controller selects VNF in active mode, standby idle mode or initializes idle mode to service requests, dynamically adjusts life cycle extension (LTE) to adapt to changes in demand, optimizes the instantiation and configuration of VNFs, and reduces unnecessary resource consumption and Delay.

Benefits of technology

Effectively control the number of VNFs, avoid resource waste, improve processing efficiency, reduce computing complexity and delays, dynamically respond to traffic changes, and optimize resource usage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118900240A_ABST
    Figure CN118900240A_ABST
Patent Text Reader

Abstract

In accordance with an example aspect of the present disclosure, there is provided an apparatus configured at least to: receive a request for an action handled by a first type of virtualized network function or cloud native network function (C / VNF); selecting a C / VNF from a group of C / VNFs to serve the request, or instantiating and selecting a new C / VNF to serve the request, where each C / VNF in the group is in one of the following three modes: an active mode, a standby idle mode, or an initialized idle mode; and assigning the request to the selected C / VNF.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to managing Virtual Network Functions (VNFs), for example in the context of a cellular communication network. Background Art

[0002] A communication network comprises nodes tasked with different functions. For example, in the case of a cellular communication network, the network comprises a radio access network RAN ​​and a core network CN. The RAN comprises RAN nodes such as base stations, while the CN comprises CN nodes, the tasks of which are to influence the functioning of the network as a whole. Examples of the functions of CN nodes include maintaining subscriber registers, switching connections, controlling the RAN, and enforcing network policies.

[0003] The nodes of a network may be physical nodes, which are computing substrates configured with software to perform one or more functions of the node. For example, such a physical node may be an independent device connected to other physical nodes using a wired connection. On the other hand, the nodes of a network may be virtualized network functions VNFs, which are logical nodes running on a physical computing substrate. A physical substrate may run one or more VNFs, and each VNF performs the functions of the node in a manner similar to a physical node. From the perspective of other network nodes, it makes no difference whether the node is implemented as a VNF or a physical node. Other types of functions of a network may also be virtualized as VNFs, and the VNFs do not need to correspond to logical network nodes.

[0004] The base stations perform various computational processes, such as header and encryption processing, according to the protocols implemented in these base stations. The base stations can be unitary or distributed in nature. Summary of the invention

[0005] According to some aspects, the subject matter of independent claims is provided. Some embodiments are defined in the dependent claims. The scope of protection sought by various embodiments of the present invention is set forth by the independent claims. The embodiments, examples and features (if any) described in this specification that do not fall within the scope of the independent claims should be interpreted as examples that help understand the various embodiments of the present invention.

[0006] According to a first aspect of the present disclosure, a device is provided, which includes at least one processing core and at least one memory for storing instructions. When the instructions are executed by the at least one processing core, the device at least: receives a request for an action processed by a first type of virtualized network function or a cloud native network function C / VNF, selects a C / VNF from a group of C / VNFs to serve the request, wherein a single C / VNF in the group is in one of the following three modes: active mode, retired idle mode, or initialized idle mode, or instantiates and selects a new C / VNF to serve the request, and assigns the request to the selected C / VNF.

[0007] According to a second aspect of the present disclosure, a method is provided, which includes receiving in an apparatus a request for an action handled by a first type of virtualized network function or a cloud native network function C / VNF, selecting a C / VNF from a group of C / VNFs to serve the request, wherein a single C / VNF in the group is in one of three modes: active mode, standby idle mode, or initialized idle mode, instantiating and selecting a new C / VNF to serve the request, and assigning the request to the selected C / VNF.

[0008] According to a third aspect of the present disclosure, a non-transitory computer-readable medium is provided, having a set of computer-readable instructions stored thereon, which, when executed by at least one processor, cause the device to at least: receive a request for an action processed by a first type of virtualized network function or a cloud-native network function C / VNF, select a C / VNF from a group of C / VNFs to serve the request, wherein a single C / VNF in the group is in one of the following three modes: active mode, standby idle mode, or initialized idle mode, or instantiate and select a new C / VNF to serve the request, and assign the request to the selected C / VNF. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 illustrates example systems in accordance with at least some embodiments of the present invention;

[0010] Figure 2A The diagram shows the VNF lifecycle;

[0011] Figure 2B The diagram shows the VNF lifecycle;

[0012] Figure 3 illustrates example devices capable of supporting at least some embodiments of the present invention;

[0013] Figure 4 is a flow chart according to at least some embodiments of the present invention, and

[0014] Figure 5 is a flow chart of a method according to at least some embodiments of the present invention. DETAILED DESCRIPTION

[0015] The method disclosed in this article enables effective control of VNFs in the system so that the total number of active VNFs remains reasonable to avoid wasting energy and computing resources, such as memory, when keeping unnecessary VNFs in idle mode. The standby VNFs remain in idle mode for a period of time before being deleted so that they can be reused when processing incoming requests, so that new VNFs do not need to be frequently instantiated as a response to incoming requests. In addition, only a reasonable number of newly initialized VNFs are kept idle to serve bursts of incoming requests. For example, the VNFs used can run virtualized microservices, such as microservices corresponding to functionality (such as compression and / or encryption processes) performed in a RAN node. Although this article mainly discusses VNFs, the principles of the present disclosure also relate to cloud native network functions CNFs. The acronym C / VNF is used herein to refer to VNFs or CNFs.

[0016] Figure 1 An example system is illustrated that is consistent with at least some embodiments of the present invention. Figure 1 An example is a cellular communication system, but embodiments of the present disclosure are also applicable to different types of networks.

[0017] The controller 110 is configured to process incoming requests in the network. These requests involve functions to be performed by network nodes, where Figure 1 In a system of at least some of these nodes are VNFs. Examples of such nodes include a mobility management entity MME, an access and mobility management entity AMF, and a serving general packet radio service support node SGSN. These requests are served by assigning the requests to the VNF for processing. The request may include an indication of a maximum acceptable waiting time, and when there is a maximum acceptable waiting time, sets the maximum time that the network can use in serving the request.

[0018] The base stations 130 are located in the radio access network RAN ​​of the entire network. The base stations 130 may be single base stations, or at least one of them may be a distributed base station. The distributed base station includes a centralized unit CU and one or more distributed units DU. For example, the DU is equipped with a radio part and may handle radio link control RLC and media access control MAC functions, while the CU may be configured to handle radio resource control RRC and packet data convergence protocol PDCP functions. In an actual physical network, the number of base stations may be hundreds or even thousands, rather than thousands. Figure 1The number shown in the figure. The CU may also have a logical node CU-UP for processing the user plane and a logical node CU-CP for processing the control plane. For example, the CU-UP and the CU-CP may run on the same physical computing substrate, or on separate computing substrates. For example, the CU-CP may be configured to run the control plane portion of the RRC and PDCP protocols, while the CU-UP may be configured to run the service data adaptation protocol SDAP and the user plane portion of the PDCP protocol. The E1 interface may connect the CP-CP to the CP-UP, while the F1-C interface may connect the CP-CP to (multiple) DUs in a network based on the Third Generation Partnership Project 3GPP standard.

[0019] The computing substrate running the functions of the CU can perform functions in the VNF as a virtualized microservice. For example, SDAP and PDCP functional entities can be run as VNFs, where such VNFs themselves can include other VNFs configured to run parts of the corresponding protocols. For example, such parts can include compression, decompression, encryption, and decryption. For example, the transport packet header compression or decompression of a single bearer can be served by a single VNF for uplink and downlink packets respectively.

[0020] The computing substrates 101 and 102 are configured to run multiple VNFs each. The VNFs do not have to be of the same type. Instead, the computing substrates 101 and 102 can be general-purpose computers, such as servers in a server farm or a cloud computing center. For example, at least one of the computing substrates can run in the CU of a base station, in a single base station, or as a core network server. The computing substrate 101 has three groups of VNFs: active mode VNF 101a, standby idle mode VNF 101b, and initialized idle mode VNF 101c. The VNFs in these groups do not need to all be of the same type. For example, there can be multiple types of VNFs in the active mode VNF 101a group. The computing substrate 102 also has three groups of VNFs: active mode VNF 102a, standby idle mode VNF 102b, and initialized idle mode VNF 102c. Groups 101a, 101b, and 101c form a first supergroup, groups 102a, 102b, and 102c form a second supergroup, groups 101a and 102a form a third supergroup, groups 101b and 102b form a fourth supergroup, and groups 101c and 102c form a fifth supergroup. The number of computational bases need not be two, but may be one, or more than two. Also for clarity of illustration, Figure 1 Including two.

[0021] In response to receiving the request, the controller 110 is configured to select a VNF to run the request. In some cases, such as when the request is not urgent, it can be assigned to an active VNF from group 101a, or 102a, or a group including groups 101a and 102a. The advantage of using a standby idle VNF from group 101b or 102b is that such a VNF can immediately begin processing the request. In addition, the standby VNF has been instantiated and configured, so the use of the standby VNF provides an additional benefit compared to a new VNF, namely reducing the rate at which new VNFs need to be instantiated and configured, thereby reducing computational complexity.

[0022] In the case where no suitable idle VNF is available, an idle mode VNF may be selected for initialization from group 101c, or 102c, or a group including groups 101c and 102c. Using an already initialized idle VNF has the advantage of reducing latency compared to responding to an incoming request by instantiating and configuring a new VNF.

[0023] VNFs can be classified into different types based on the type of processing they provide. A request can request a specific single processing type, or a request can be a type that triggers a VNF sequence to be used. A VNF sequence can also be considered as a specific type of aggregated VNF. In general, when an active VNF completes processing, it can transition to a standby idle state and notify the controller 110 of this. The length of time that a VNF remains in a standby idle state is referred to herein as a lifecycle extension (LTE). The LTE can be different for different VNF ​​types. LTE can vary during operation, and the initial value of LTE can be between 5% and 10% of the time it takes for a VNF of the corresponding type to complete processing of its task. How LTE can vary will be discussed in more detail below.

[0024] Changing LTE helps ensure that an excessive number of VNFs do not remain idle for long periods of time, using resources while waiting for new requests. The entire VNF group can dynamically adapt to changing needs. In summary, a VNF can first be instantiated and configured to be held in an initialization idle mode, then it can be assigned a request to serve, causing it to enter active mode, after which the VNF can spend LTE in standby idle mode before being deactivated and removed from memory to free up memory space for other types of VNFs with greater demand.

[0025] The LTE may depend on both the CNF type and the prevailing load state. The LTE of each VNF type may be adapted based at least in part on the average interval between incoming requests of the type served by the corresponding VNF type. Specifically, when the average time interval between arriving requests is greater than the sum of the request service time and the LTE, the LTE may be increased, and when the average time interval between arriving requests is less than the sum of the request service time and the LTE, the LTE may be reduced. In other words, the LTE may be reduced when the frequency of arriving requests decreases, and the LTE may be increased when the frequency of arriving requests of the relevant type increases. The LTE may be reduced and increased in steps of one percent of the request service time, for example, the request service time is the length of time it takes the VNF to service a request. The LTE may be adjusted, and the adjusted LTE may be assigned to the VNF in association with assigning the request to the VNF. In at least some embodiments, a VNF that has already processed a request does not have its LTE adjusted.

[0026] In optimal use, incoming requests can be immediately assigned to standby C / VNFs in idle mode for processing. Now, in a pool with a number of VNFs N, the probability of finding one of the VNFs in idle mode at a point in time increases as its life cycle increases. This becomes clearer by considering two extreme cases: first, when the life cycle extension decreases, that is, LTE approaches zero, then the probability of finding the VNF in standby idle mode decreases. Second, when the life cycle extension increases, that is, LTE approaches infinity, then the probability of finding the VNF in standby idle mode increases. In the case of an increase in the frequency of incoming requests, more requests are assigned to standby C / VNFs in idle mode, thereby reducing their number: N approaches zero. Therefore, the probability of finding a VNF in idle mode decreases. This decrease in probability can be counteracted by increasing the life cycle extension of the VNF: LTE approaches infinity, corresponding to the second case mentioned above.

[0027] In case the frequency of incoming requests decreases, fewer requests are allocated to the inactive VNFs in idle mode. Therefore, the number of VNFs N can be further reduced by shortening the life cycle of the VNFs to zero by extending LTE to reduce their useless stay time in idle mode.

[0028] The number of initialized idle VNFs corresponding to the size of groups 101c and 102c can be kept to the minimum level required to provide acceptable service levels, because idle VNFs consume memory, and in addition configuring new VNFs consumes some computing resources. Therefore, in an ideal state, requests will be mainly assigned to idle VNFs in use, and possibly active VNFs. Initialized idle VNFs can be used to service specific types of burst requests.

[0029] When the controller 110 receives the request, it selects a VNF of the following type from the current list of idle VNFs in standby mode: the type of VNF is configured to serve the incoming request. If no suitable standby VNF is available, the controller 110 can select a VNF from a suitable initialized idle VNF. Once the LTE of the VNF expires, the controller or another node deletes the VNF from the list of available VNF instances. Such a VNF will be deactivated and removed. The controller 110 can be configured to select a standby VNF with the shortest remaining portion of the remaining LTE. Such a selection enhances the availability of this type of standby VNF because other VNFs have more LTE remaining to wait for incoming requests. The number of initialized idle VNFs can also be managed dynamically. If the number drops below a threshold, the pool can be automatically enhanced by instantiating and initializing additional VNFs. In some embodiments, machine learning solutions such as artificial neural networks are used to predict incoming request patterns in advance and increase the number of VNFs in initialized idle mode to anticipate incoming request bursts. Such a machine learning solution can be trained using training data recorded from real-time use in the network, where patterns in the traffic are captured. Dynamic adaptation of LTE minimizes the number of VNFs that are idle for long periods of time, thereby saving computing resources. The length of LTE can also depend on the network operator's policy.

[0030] Once the VNF has completed processing the request, as mentioned above, it may notify the controller 110 by sending a notification. The notification may include, for example, the identity of the VNF sending the notification, and the type of request being served, and / or the type of VNF. The notification may also include the time the VNF took to process the request and the value of LTE. It may also include an indication of a predicted outage time, at which the LTE will expire unless additional requests are provided to the VNF during LTE.

[0031] Regarding the functionality of the controller 110, it receives requests from a client, which may include a core network entity or one of the VNFs in a base station (such as in a CU). The controller may determine the number R of incoming requests for each request type T. T In addition, the controller 110 may be configured to determine an average number of requests of type T.

[0032]

[0033] Where R T is the number of requests received within the time window. The controller 110 may also be configured to determine the number of requests R of type T. T The standard deviation σ R,T . In addition, the controller 110 can be configured to register the processing time from the VNFs, thereby notifying the controller that they have completed processing the requests assigned to them. Similarly, the LTE of the VNFs entering the standby idle mode can be recorded by the controller 110. The controller can also determine the average processing time of requests of type T

[0034] where i is the job index.

[0035] Similarly, the processing time τ for each request of type T is T The standard deviation σ T,T It can be determined by the controller 110.

[0036] When LTE is shorter, the population of idle VNFs is lower than when LTE is longer. With short TLE, more initialized idle VNFs may need to be used to service incoming requests. In the case where initialized idle VNFs are exhausted or close to being exhausted, new VNFs may need to be instantiated and configured to service incoming requests. Longer LTE increases the number of idle VNFs, so that they will consume more resources to maintain in idle mode, but they can serve incoming requests with very short delays.

[0037] In order to achieve an optimized service of incoming requests, the number of idle VNFs of each type available in a time period should be equal to the number of incoming requests of the corresponding type. To achieve this, the controller 110 may continuously monitor the number of incoming requests to obtain a continuously updated average number of incoming requests of each type and each time period Δt. The number of idle VNFs in use is increased or decreased by lengthening or shortening their average LTE so that:

[0038]

[0039]

[0040] Here, represents the average LTE for VNF of type T, represents the average inter-arrival time of requests of type T, and Indicates the average processing time of requests of type T.

[0041] The number of initialized idle VNFs can be chosen to be equal to the number of incoming requests of type T, R T The standard deviation ρσ R,T Here, ρ can be chosen to be two or three, for example.

[0042] Using these principles, most incoming requests can be served by the standby idle NFVs, and the remaining requests can be served by the initialized idle NFVs. Using a smaller p (such as 2) is a resource saving strategy that allows fewer initialized idle NFVs to be ready to serve requests that cannot be served by the standby idle NFVs. Using a higher p (such as 3) is a strategy that emphasizes lower latency by keeping more initialized idle NFVs ready to serve requests, thereby reducing the need to instantiate new NFVs to respond to incoming requests, or assigning requests to active NFVs.

[0043] Figure 2A The VNF life cycle is shown in the figure. Time advances from left to right. The time length 210 corresponds to That is, the average processing time of the request, and the time length 220 corresponds to That is, the average LTE of VNFs of this type. Therefore, the VNF will be in active mode during the time period 210 in which it processes the request, and after this for a time length 220 (LTE), the VNF will be in standby idle mode while it waits for a possible arrival of new requests of the type it is configured to process. New requests arriving during the time length 210 will preferably not be assigned to this VNF, because this VNF is busy processing earlier requests. If a new request arrives during the time length 220 (LTE), then the idle VNF that is in standby will be a good choice to process the new request. On the other hand, if a new request arrives only after the expiration of the time length 220, the VNF will be deactivated and therefore it is no longer available to process the new request.

[0044] Figure 2B The figure shows the VNF life cycle. Similar numbers represent Figure 2A Here is a similar structure. Marks the average time between the arrival of two consecutive requests of the type handled by this VNF. As shown, this time starts at the beginning of the time length 210 and ends halfway through LTE 220. Figure 2B In the case of , plus or minus three standard deviations σ in the time distribution between successive arrivals of requests corresponds to the start and end of LTE.

[0045] In the case of medium traffic, the average number of requests of type T is R T Average inter-arrival time (exist Figure 2Bis marked as ) arrives, which is greater than the average request processing time corresponding to the time length 210 But it is less than the sum of the average request processing time 210 and LTE 220. This medium traffic situation can be expressed as

[0046] In this case, the average number of inactive idle VNFs will remain constant, since incoming requests can be assigned to the group of inactive idle VNFs. The advantage of LTE is that it keeps inactive VNFs active so that they can handle incoming requests, while the variance of the arrival rate is slightly larger.

[0047] Under high traffic conditions, requests of type T are processed faster than the average request processing time. Shorter mean inter-arrival time arrive: In this case, the population of idle VNFs to be used will decrease and eventually be exhausted, and the controller 110 will begin to rely on the initialized idle VNFs to service incoming requests. It may be necessary to expand the initialized idle VNF group by instantiating new VNFs into the initialized idle VNF group to avoid exhausting the available VNFs.

[0048] In low traffic situations, requests of type T are processed faster than the average request processing time. Longer mean inter-arrival time arrive: In this case, the group of idle VNFs to be used will be gradually deactivated, causing the number of their groups to drop. Requests can be assigned to initialized idle VNFs or active VNFs. Since the number of requests is small in low traffic situations, it is not challenging from a resource management perspective.

[0049] Figure 3 The illustrated device 300 may include, for example, Figure 1Controller 110. The device 300 includes a processor 310, which may include, for example, a single-core or multi-core processor, wherein the single-core processor includes one processing core and the multi-core processor includes more than one processing core. In general, the processor 310 may include a control device. The processor 310 may include more than one processor. When the processor 310 includes more than one processor, the device 300 may be a distributed device in which the processing of tasks occurs in more than one physical unit. The processor 310 may be a control device. The processing core may include, for example, a Cortex-A8 processing core manufactured by ARM Holdings or a Zen processing core designed by Advanced Micro Devices Corporation. The processor 310 may include at least one Qualcomm Snapdragon and / or Intel Atom processor. The processor 310 may include at least one application-specific integrated circuit ASIC. The processor 310 may include at least one field programmable gate array FPGA. Processor 310 may be means for performing method steps, such as receiving, selecting, assigning, adjusting, reducing, and initializing, in device 300. Processor 310 may be configured, at least in part, by computer instructions to perform actions.

[0050] The processor may include circuitry, or be constructed as one or more circuitry, configured to perform the stages of the method according to the embodiments described herein. As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) a pure hardware circuit implementation, such as an implementation in analog and / or digital circuitry only, and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) (multiple) hardware processors with any portion of software (including (multiple) digital signal processors), software and (multiple) memories, which work together to enable the device (such as a controller) to perform various functions), and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software (e.g., firmware) to operate, but the software may not be present when not required for operation.

[0051] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. By way of example and where applicable to a particular claim element, the term "circuitry" also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0052] Device 300 may include memory 320. Memory 320 may include random access memory and / or permanent memory. Memory 320 may include at least one RAM chip. For example, memory 320 may include solid-state, magnetic, optical and / or holographic memory. Memory 320 may be at least partially accessible by processor 310. Memory 320 may be at least partially included in processor 310. Memory 320 may be a component for storing information. Memory 320 may include computer instructions that processor 310 is configured to execute. When computer instructions configured to cause processor 310 to perform certain actions are stored in memory 320, and device 300 as a whole is configured to run under the guidance of processor 310 using computer instructions from memory 320, processor 310 and / or at least one of its processing cores may be considered to be configured to perform the certain actions. Memory 320 may be at least partially included in processor 310. Memory 320 may be at least partially external to device 300, but accessible by device 300. Memory 320 may be non-temporary. As used herein, the term "non-transitory" is a restriction on the medium itself (that is, tangible, not a signal), not on the persistence of data storage (eg, RAM versus ROM).

[0053] Device 300 may include a transmitter 330. Device 300 may include a receiver 340. Transmitter 330 and receiver 340 may be configured to transmit and receive information, respectively, according to at least one standard. Transmitter 330 may include more than one transmitter. Receiver 340 may include more than one receiver.

[0054] The device 300 may include a user interface UI 360. The UI 360 may include at least one of a display, a keyboard, a touch screen, a vibrator arranged to signal the user by vibrating the device 300, a speaker, and a microphone. The user may be able to operate the device 300 via the UI 360, for example to configure virtualization parameters.

[0055] The processor 310 may be provided with a transmitter arranged to output information from the processor 310 to other devices included in the device 300 via electrical leads internal to the device 300. Such a transmitter may include a serial bus transmitter arranged to output information to the memory 320 for storage therein, for example, via at least one electrical lead. As an alternative to a serial bus, the transmitter may include a parallel bus transmitter. Likewise, the processor 310 may include a receiver arranged to receive information in the processor 310 from other devices included in the device 300 via electrical leads internal to the device 300. Such a receiver may include a serial bus receiver arranged to receive information from the receiver 340, for example, via at least one electrical lead, for processing in the processor 310. As an alternative to a serial bus, the receiver may include a parallel bus receiver. The device 300 may include Figure 3 Other equipment not shown

[0056] The processor 310, the memory 320, the transmitter 330, the receiver 340 and / or the UI 360 may be interconnected in a variety of different ways via electrical leads within the device 300. For example, each of the above devices may be individually connected to a main bus within the device 300 to allow the devices to exchange information. However, as will be appreciated by those skilled in the art, this is only an example, and various ways of interconnecting at least two of the aforementioned devices may be selected depending on the embodiment without departing from the scope of the present invention.

[0057] Figure 4 is a flow chart according to at least some embodiments of the present invention. A request arrives at the controller in stage 410, and processing proceeds from stage 410 to stage 420, where it is determined whether the number of standby idle VNFs of the type that handles the request is zero. If the number is zero, processing proceeds to stage 430, where an initialized idle VNF is selected to service the request, and in stage 440, the request of stage 410 is assigned to the selected initialized idle VNF. On the other hand, if a standby idle VNF is available, the request of stage 410 will be assigned to the standby idle VNF by proceeding to stage 455.

[0058] In stage 450, a notification has arrived at the controller 110, thereby notifying the controller of at least one of the request processing time τ or the request arrival time λ. The controller responds to the notification by calculating, in stage 455, the current average request inter-arrival time and the average processing time of requests for the request type of stage 410. In some embodiments, in stage 455, the average request inter-arrival time and the average request processing time are calculated for all request types or, for example, all request types that had at least one request during the past 24 hours. Processing proceeds from stage 455 to stage 460.

[0059] In stage 460, it is determined whether the average time λ between request arrivals is greater than the average request processing time τ, but less than the sum of the average request processing time τ and LTE. If this is the case, processing proceeds from stage 460 to stage 470, where the request is assigned to a standby idle VNF.

[0060] On the other hand, if the comparison in stage 460 returns a negative result, the process proceeds to stage 480, where the average time between request arrivals λ is compared to the sum of the average request processing time τ and LTE. If λ is greater, the process proceeds to stage 490, where LTE is increased, whereupon the process proceeds to stage 470 and the request is assigned to a standby idle VNF. If λ is not greater than the sum of τ and LTE, the process proceeds from stage 480 to stage 495, where LTE is decreased, and then proceeds to stage 470 and the request is assigned to a standby idle VNF. The modified LTE can thus be assigned to the VNF in association with the assignment of the request to the VNF for processing.

[0061] In general, by increasing or decreasing LTE, it can mean modifying the LTE for the newly instantiated VNF while leaving the LTE in the VNFs already in the system unchanged. This saves resources in terms of reducing the amount of signaling in the system. In some embodiments, LTE is assigned to the VNF in relation to assigning a request to the VNF. In these cases, increasing or decreasing LTE means increasing or decreasing the LTE assigned to the VNF in relation to assigning a request to the VNF for processing.

[0062] Figure 5 It is a flowchart of a method according to at least some embodiments of the present invention. The stages of the illustrated method can be performed in the controller 110, or in a control device configured to control its functions when installed in the controller 110. Stage 510 includes receiving a request for an action processed by a first type of virtualized network function or cloud native network function C / VNF in the device. Stage 520 includes selecting a C / VNF from a group of C / VNFs to serve the request, wherein a single C / VNF in the group is in one of the following three modes: active mode, standby idle mode, or initialized idle mode, instantiating and selecting a new C / VNF to satisfy the request. Finally, stage 530 includes assigning the request to the selected C / VNF.

[0063] It should be understood that the disclosed embodiments of the present invention are not limited to the specific structures, process steps or materials disclosed herein, but are extended to equivalents thereof that will be recognized by those of ordinary skill in the relevant art. It should also be understood that the terms used herein are only used for the purpose of describing specific embodiments and are not intended to be limiting.

[0064] References to one embodiment or embodiments throughout the specification mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment of the invention. Thus, the phrases "in one embodiment" or "in an embodiment" that appear in various places throughout the specification do not necessarily all refer to the same embodiment. When terms such as, for example, about, or substantially are used to reference values, the exact value is also disclosed.

[0065] As used herein, for convenience, multiple projects, structural elements, constituent elements and / or materials can be presented in a public list. However, these lists should be interpreted as if each member in the list is individually identified as a separate and unique member. Therefore, any individual member in the list should not be interpreted as being in fact equivalent to any other member in the same list based only on its performance in a common group, without contrary instructions. In addition, various embodiments of the present invention and examples together with the alternatives of its various components can be mentioned in this article. It should be understood that such embodiments, examples and alternatives should not be interpreted as equivalents in fact to each other, but should be regarded as separate and autonomous representations of the present invention.

[0066] In addition, the described features, structures or characteristics can be combined in any suitable manner in one or more embodiments. In the foregoing description, many specific details, such as examples of length, width, shape, etc., are provided to provide a thorough understanding of embodiments of the present invention. However, those skilled in the relevant art will recognize that the present invention can be practiced without one or more specific details, or using other methods, components, materials, etc. In other examples, well-known structures, materials or operations are not shown or described in detail to avoid blurring various aspects of the present invention.

[0067] Although the foregoing examples illustrate the principles of the present invention in one or more specific applications, it is obvious to those skilled in the art that various modifications may be made in the details of form, use and implementation without the exercise of inventive ability and without departing from the principles and concepts of the present invention. Therefore, the present invention is not limited except as set forth in the appended claims.

[0068] The verbs "comprise" and "include" are used in this document as open limitations, which neither exclude nor require the existence of unrecited features. Unless explicitly stated otherwise, the features recited in the dependent claims may be freely combined with each other. Furthermore, it should be understood that the use of "a" or "an" throughout this document, i.e. the singular, does not exclude the plural.

[0069] Industrial Applications

[0070] At least some embodiments of the present invention find industrial application in managing virtualization of functions such as microservices.

[0071] List of abbreviations

[0072] CU Centralized Unit

[0073] CNF Cloud Native Network Function

[0074] DU Distributed Unit

[0075] MAC Media Access Control

[0076] PDCP Packet Data Convergence Protocol

[0077] RAN Radio Access Network

[0078] RRC Radio Resource Control

[0079] SDAP Service Data Adaptation Protocol

[0080] VNF virtualized network function.

Claims

1. An apparatus for managing a virtual network function (VNF), comprising at least one processing core and at least one memory storing instructions, wherein the instructions, when executed by the at least one processing core, cause the apparatus to at least: - receiving a request for an action to be processed by a first type of virtualized network function or cloud-native network function C / VNF; - Selecting a C / VNF from a group of C / VNFs to serve the request, or instantiating and selecting a new C / VNF to serve the request, wherein a single C / VNF in the group is in one of the following three modes: active mode, standby idle mode, or initialized idle mode; and - Assign the request to the selected C / VNF.

2. An apparatus according to claim 1, wherein the apparatus is configured to adjust the length of time that the first type of C / VNF remains in the standby idle mode based on the frequency of requests processed by the first type of C / VNF received in the apparatus.

3. An apparatus according to claim 2, wherein the apparatus is configured to: reduce the length of time that the first type of C / VNF remains in the standby idle mode when the frequency of the requests decreases, increase the length of time that the first type of C / VNF remains in the standby idle mode when the frequency of the requests increases, and assign the reduced or increased length of time that the first type of C / VNF remains in the standby idle mode to the selected C / VNF in association with assigning the requests to the selected C / VNF.

4. The apparatus according to any one of claims 1-3, wherein the C / VNF in the initialized idle mode is a C / VNF to which the apparatus has not yet assigned a request to be processed.

5. The device according to any one of claims 1-3, wherein the C / VNF in the standby idle mode is a C / VNF from which the device has received a notification that the C / VNF has completed processing a request.

6. An apparatus according to any one of claims 1-3, wherein the apparatus is configured to: select the number of initialized idle mode C / VNFs of the first type based on the variance of the number of incoming requests per time unit, and the requests are processed by the C / VNFs of the first type.

7. The apparatus of claim 6, wherein the apparatus is configured to select a larger number of the first type of initialized idle mode C / VNFs when the variance is higher, and to select a smaller number of the first type of initialized idle mode C / VNFs when the variance is lower.

8. The apparatus according to claim 6, wherein the apparatus is configured to initialize the C / VNF to the initialization idle mode.

9. The device according to any one of claims 1-3 is also configured to receive a completion notification from a C / VNF, a single completion notification indicating that the C / VNF that has sent the corresponding completion notification has completed processing the request and the C / VNF has entered a standby idle mode.

10. The apparatus according to any one of claims 1-3 is further configured to receive a request for an action processed by a second type of C / VNF to select a C / VNF of the second type from a second group of C / VNFs to serve the request, wherein a single C / VNF of the second type in the second group is in one of the following three modes: the active mode, the standby idle mode, or the initialized idle mode, and assign the request to the selected C / VNF of the second type.

11. A method for managing a virtual network function (VNF), comprising: - receiving in the device a request for an action to be processed by a first type of virtualized network function or cloud-native network function C / VNF; - selecting a C / VNF from a group of C / VNFs to serve the request, or instantiating and selecting a new C / VNF to serve the request, wherein a single C / VNF in the group is in one of the following three modes: active mode, standby idle mode, or initialized idle mode, and - Assign the request to the selected C / VNF.

12. The method according to claim 11, further comprising: Based on the frequency of receiving requests processed by the C / VNF of the first type in the device, the length of time that the C / VNF of the first type remains in the inactive idle mode is adjusted.

13. The method according to claim 12, wherein the method comprises: When the frequency of the requests decreases, the length of time that the first type C / VNF remains in the standby idle mode is reduced, and when the frequency of the requests increases, the length of time that the first type C / VNF remains in the standby idle mode is increased, and in association with assigning the requests to the selected C / VNF, the reduced or increased length of time that the first type C / VNF remains in the standby idle mode is assigned to the selected C / VNF.

14. The method according to any one of claims 11-13, wherein the C / VNF in the initialized idle mode is a C / VNF to which the device has not yet assigned a request to be processed.

15. The method according to any one of claims 11-13, wherein the C / VNF in the inactive idle mode is a C / VNF from which the device has received a notification that the C / VNF has completed processing a request.

16. The method according to any one of claims 11 to 13, further comprising: The number of initialized idle mode C / VNFs of the first type is selected based on the variance of the number of incoming requests per time unit, and the requests are processed by the C / VNFs of the first type.

17. The method of claim 16, wherein when the variance is higher, a greater number of the first type of initialized idle mode C / VNFs are selected, and when the variance is lower, a smaller number of the first type of initialized idle mode C / VNFs are selected.

18. The method according to any one of claims 11 to 13, further comprising: A completion notification is received from the C / VNF, the single completion notification indicating that the C / VNF that has sent the corresponding completion notification has completed processing the request and the C / VNF has entered an idle mode.

19. The method according to any one of claims 11 to 13, further comprising: Receive a request for an action to be processed by a C / VNF of a second type to select a C / VNF of the second type from a second group of C / VNFs to serve the request, wherein a single C / VNF of the second type in the second group is in one of the following three modes: the active mode, the standby idle mode, or the initialized idle mode, and assign the request to the selected C / VNF type of the second type.

20. A computer readable medium having stored thereon a set of computer readable instructions which, when executed by at least one processor, cause an apparatus to at least: - receiving a request for an action to be processed by a first type of virtualized network function or cloud-native network function C / VNF; - selecting a C / VNF from a group of C / VNFs to serve the request, or instantiating and selecting a new C / VNF to serve the request, wherein a single C / VNF in the group is in one of the following three modes: active mode, standby idle mode, or initialized idle mode, and - Assign the request to the selected C / VNF.