resource control unit

Abstract

This resolves the issue of pods not being able to be placed depending on resource usage. [Solution] The system includes a determination unit 542 that determines, from among multiple pods, a target pod for which resources for executing an application will be secured based on attributes corresponding to the pod, which is the smallest execution unit of an application, and a reservation unit 544 that reserves resources to provide an execution environment for the target pod according to the attributes of the target pod before starting the target pod.

Description

[Technical Field]

[0001] The present disclosure relates to, for example, a resource control device. [Background technology]

[0002] A known resource allocation method for network slicing is to maintain a table that links slice IDs with container orchestrator labels, and to start a container with a label corresponding to the slice ID when a connection is established (see, for example, non-patent document 1). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] Yuta Tanaka and Kenzo Okuda, "Resource allocation method in cooperation with a container orchestrator in network slicing," 2023 Institute of Electronics, Information and Communication Engineers, Society Conference, B-6-52, Sep. 2023. Summary of the Invention [Problem to be solved by the invention]

[0004] However, with the above technology, when resources are not sufficiently secured and some pods have already been deployed, there is a problem that when starting a pod that consumes a large amount of resources or a pod that requires distributed deployment, the pod may not be able to be deployed depending on the resource usage situation. [Means for solving the problem]

[0005] In order to solve the above problem, a resource control device according to one aspect of the present disclosure includes a determination unit that determines, among multiple pods, a target pod for which resources for executing an application will be secured based on attributes corresponding to the pod, which is the smallest execution unit of the application, and a reservation unit that reserves resources to provide an execution environment for the target pod based on the attributes of the target pod before starting the target pod. [Brief explanation of the drawings]

[0006] [Figure 1] 1 is a block diagram showing a configuration of a system to which a resource control device according to an embodiment is applied; [Figure 2] FIG. 10 is an operational sequence diagram illustrating resource control in the system. [Figure 3] FIG. 10 is a diagram illustrating an example of input parameters. [Figure 4] FIG. 10 is a diagram illustrating an example of a destination resource in a target pod. [Figure 5] FIG. 10 is a diagram illustrating an example of AZs and worker nodes. [Figure 6] FIG. 10 is a diagram illustrating an example of a reservation in a target pod. [Figure 7] FIG. 10 is a diagram illustrating an example of deployment in a target pod. [Figure 8] FIG. 10 is a diagram illustrating an example of deployment in a target pod. [Figure 9] FIG. 10 is a diagram illustrating an example of an additional deployment in a target pod. [Figure 10] FIG. 10 is a diagram illustrating an example of deployment in a non-target pod. [Figure 11] FIG. 10 is a diagram illustrating an example in which parameters are corrected. [Figure 12] FIG. 10 is a diagram illustrating an example of a destination resource in a target pod when the resource is corrected. [Figure 13] FIG. 10 is a diagram illustrating an example of a reservation in a target pod. [Figure 14] FIG. 10 is a diagram illustrating an example of scaling out a non-target pod. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that in each drawing, the dimensions and scale of each part are appropriately different from those of the actual parts. Furthermore, the embodiments described below are preferred examples of the present invention, and therefore various technically preferable limitations are applied. However, the scope of the present invention is not limited to these embodiments unless otherwise specified in the following description to the effect that the present invention is limited.

[0008] FIG. 1 is a block diagram showing the configuration of a system 1 to which a resource control device 42 according to an embodiment is applied. The system 1 shown in this figure is, for example, a 5G mobile communication system, and includes a terminal 10, a base station 20, a core network 30, an input device 40, and an infrastructure device 50.

[0009] The terminal 10 is, for example, a smartphone operated by a user. The base station 20 is a station that transmits and receives radio waves necessary for wireless communication with the terminal 10. For simplicity, only one terminal 10 and one base station 20 are shown in the figure, but in reality there are multiple terminals 10 and base stations 20.

[0010] The core network 30 connects the base station 20 to the Internet, and includes a communication control unit 32 and a traffic control unit 34 . The communication control unit 32 is a functional unit called a control plane that manages communication sessions and controls communications. The traffic control unit 34 is a functional unit called a User Plane that controls communication traffic. The device in the traffic control unit 34 has a function of passing a label corresponding to the slice ID to the infrastructure device 50. A slice ID is an identifier used to distinguish between logical networks (slices) that are virtually divided from a physical network. A label is used to separate each resource and to specify the pod that corresponds to the label.

[0011] The input device 40 is an information input device operated by an operator such as a system administrator of a telecommunications carrier. Specifically, parameters such as NF instances and resources required for pods are input by the operator to the input device 40 and are supplied to the infrastructure device 50. Examples of the parameters will be described later.

[0012] The infrastructure device 50 includes a container orchestrator 52 and a resource control device 54 . The container orchestrator 52 is a functional entity that performs deployment, scaling, management, etc. of pods made up of containers when executing containerized applications. A container is a packaged application and middleware. A pod is made up of one or more containers and is the smallest execution unit of an application. Deployment refers to placing and deploying pods etc. in an execution environment, and will be referred to simply as "deploy" hereafter. Scaling can be done by scaling out, which increases the number of containers according to the required traffic volume, or by scaling in, which reduces the number of containers.

[0013] The resource control device 54 responds with the placement destination of the pod when the container orchestrator 52 requests the placement destination of the pod, and includes a determination unit 542 and a reservation unit 544. The determination unit 542 determines whether or not a pod is a target pod with stricter placement requirements, based on the parameters input by the input device 40. Note that, among the pods, a pod determined not to be a target pod is referred to as a non-target pod. The reservation unit 544 reserves in advance the resources to which the target pod is to be placed. "In advance" means before actually starting or deploying the target pod, and "reserving" is performed by creating a table indicating that the target pod has been reserved on a worker node. A worker node is a node that provides the execution environment for pods, including containers. In this embodiment, the container orchestrator 52 and the resource control device 54 cooperate to control the deployment of pods, etc.

[0014] Next, the operation of resource control in the system 1 will be described.

[0015] FIG. 2 is an operational sequence diagram showing resource control in the system 1. As shown in FIG. First, the operator inputs various parameters by operating the input device 40 (step Sc1). When the parameters are input, the input device 40 transmits the parameters to the resource control device .

[0016] FIG. 3 is a diagram illustrating an example of parameters. As shown in this figure, each pod is associated with information indicating elements such as an NF instance, a minimum number of replicas, a maximum number of replicas, resources, placement constraints, and slices. In the example of FIG. 3, the pods are assigned symbols such as #A, #B, . . . to distinguish them from one another.

[0017] An NF instance corresponds to a unit in a core network. For example, #upf1 in pods #A and #B indicates the first unit of the UPF (User Plane Function). Also, #smf1 in pods #C and #D indicates the first unit of the SMF (Session Management Function). The minimum replica count is the minimum set number of replicas for a pod. The maximum number of replicas is the maximum set number of replicas that can be created for a pod. Here, the resource indicates the amount of resource consumed by the pod, and in this embodiment, to simplify the indication of the amount of resource, it is expressed as either "large," "medium," or "small." Placement constraints indicate the placement conditions for pods. Specifically, they specify whether the AZs that provide the execution environment for pods must be distributed across multiple locations (distribution required) or not (distribution preferred). An AZ (Availability Zone) is an operational unit for multiple server devices, and generally refers to a group of server devices configured with the same power supply. Processing pods (containers) across multiple AZs improves fault tolerance.

[0018] A slice here refers to a logical network that provides an execution environment for a pod, and in this embodiment, the following three types are shown: "High-speed, high-capacity" that processes data at high speed and in large volumes, "Ultra-large-volume terminal" that processes large-scale machine-type communications, and "Low-latency, high-reliability" that processes data with low latency and extremely high reliability.

[0019] In the input device 40, for example, a plurality of parameter elements are displayed on the screen in a pull-down menu, and one of these elements is designated by the operator's selection.

[0020] In the resource control device 54 that has received the parameters from the input device 40, the determining unit 542 determines that the pods included in the parameters are either target pods with strict placement requirements or non-target pods with loose placement requirements (step Sc2). 3, the determination unit 542 determines pod #A, whose placement constraint is "distribution required," as the target pod. Also, the determination unit 542 determines pod #D, whose placement constraint is "distribution preferred," but whose slice requires "low latency and high reliability," as the target pod. On the other hand, the determining unit 542 determines pods #B and #C, which have the placement constraint of "distribution priority", as non-target pods.

[0021] Here, the determination unit 542 determines either the target pod or the target pod mainly based on the placement constraint and the slice, but in reality, the determination is made taking into consideration other factors such as resources. The decision unit 542 may weight each element and decide to make a pod a target pod if the weighted total is equal to or greater than a threshold, and decide to make a pod a non-target pod if the total is less than the threshold. The minimum number of replicas, the maximum number of replicas, the resource, the placement constraint, and the slice are examples of "attributes of the target pod." The determination unit 542 transmits the determination result to the reservation unit 544 .

[0022] The reservation unit 544 receives the determination result from the determination unit 542 and determines the placement resource for the target pod by calculation or the like, and reserves it (step Sc3).

[0023] Here, as shown in FIG. 5, it is assumed that worker nodes Wrk#1 to #3, Wrk#4 to #6, and Wrk#7 to #9 are operated in different AZs. FIG. 4 is a diagram showing an example of a destination resource for a pod reserved by the reservation unit 544, and FIG. 6 is a diagram showing an example of a pod reserved in the destination resource as shown in FIG.

[0024] 3, the placement constraint for Pod #A is "Distribution Required," so the worker nodes that provide the execution environment for Pod #A must be distributed across multiple AZs. Therefore, the reservation unit 544 reserves worker nodes Wrk #1, Wrk #4, and Wrk #7 as placement resources for Pod #A. In other words, the worker nodes that provide the execution environment for Pod #A are reserved and distributed across three AZs. In FIG. 6 and subsequent figures, the amount of resources consumed by pods in a worker node (consumed resources) does not necessarily reflect the resources (amounts) shown in FIG. 3 (FIG. 11).

[0025] The placement constraint of pod #D is not "distribution required" but "distribution preferred", but the slice is "low latency and high reliability", so the reservation unit 544 reserves more worker nodes as placement resources for pod #D, distributing them across more worker nodes than for pod #A. Specifically, the reservation unit 544 reserves worker nodes Wrk #2, Wrk #5, Wrk #8, and Wrk #9 as placement resources for pod #D. In Figure 3, the maximum number of replicas for Pod #D is "3," whereas in Figure 4, the number of worker nodes on which Pod #D is placed is "4," which is greater than the maximum number of replicas. The reason for this is that the slice for Pod #D is set to "low latency and high reliability." For example, if Pod #D is provided by a worker node with the maximum number of replicas, and one of the worker nodes goes down due to some kind of failure, this allows for a quick switchover to the reserved (remaining) worker nodes.

[0026] The reservation unit 544 holds, for example, a table showing the relationship between the target pod and the reserved destination resource, as shown in Fig. 4. Note that no destination resource is allocated to the non-target pod.

[0027] Furthermore, even if a pod is reserved for one worker node, the worker node may have vacant space depending on the amount of resources consumed by the pod. In the vacant space, the container orchestrator 52 may deploy a non-target pod, as described below. In addition, if a target pod is reserved on a worker node and an untargeted pod temporarily requests a large number of resources, the worker node may be released from reservation to provide the untargeted pod, and the untargeted pod may be deployed on the released worker node.

[0028] Next, the cooperative operation between the container orchestrator 52 and the resource control device 54 when an NF instance is generated, in other words, when a unit is constructed, will be described.

[0029] When an NF instance is created, a request to deploy a pod required for the NF instance is generated in the container orchestrator 52 (step Sc11). The container orchestrator 52 requests the resource control device 54 whether the pod required for the NF instance is a target pod, and if it is a target pod, the container orchestrator 52 requests the placement destination of the pod (step Sc12).

[0030] In the resource control device 54, the reservation unit 544 determines whether the requested pod is a target pod, and if it is a target pod, determines the destination resource reserved for the target pod by referring to a table it holds (see FIG. 4). Specifically, if the table contains a description of the destination resource corresponding to the requested pod, it is a target pod, and if not, it is a non-target pod.

[0031] If the requested pod is the target pod, the reservation unit 544 responds to the container orchestrator 52 with the placement resource reserved for the target pod (step Sc13). Furthermore, if the requested pod is a non-target pod, the reservation unit 544 responds to that effect to the container orchestrator 52.

[0032] If the requested pod is the target pod, the container orchestrator 52 deploys the pod to the destination resource indicated in the response (step Sc14). For example, if the requested pod is pod #D of the target pods, the reservation unit 544 responds that pod #D is the target pod and that the resources to which it is to be deployed are worker nodes Wrk #2, Wrk #5, Wrk #8, and Wrk #9. The container orchestrator 52 deploys pod #D to two worker nodes, which is the minimum number of replicas of pod #D, among the (reserved) worker nodes Wrk #2, Wrk #5, Wrk #8, and Wrk #9 in the response.

[0033] Figure 7 shows an example in which pod #D is deployed to the two worker nodes Wrk#2 and Wrk#5, which have the smallest number of replicas, out of the reserved worker nodes Wrk#2, Wrk#5, Wrk#8, and Wrk#9.

[0034] When a request to deploy pod #A occurs while pod #D is deployed, the container orchestrator 52 will go through the above steps Sc11 to Sc14 to deploy pod #A with the minimum number of replicas of pod #A among the reserved worker nodes Wrk#1, Wrk#4, and Wrk#7. FIG. 8 is a diagram illustrating an example in which pod #A is deployed to one worker node Wrk#1, which has the smallest number of replicas, among reserved worker nodes Wrk#1, Wrk#4, and Wrk#7.

[0035] If the requested pod is a non-target pod, the container orchestrator 52 deploys the pod to an unreserved worker node that satisfies the placement requirements of the pod.

[0036] After commercial communication is established with the NF instance, pods are deployed to resources according to slice IDs. 2, when a session establishment request is made from the terminal 10 or the base station 20 (step Sc20), the traffic control unit 34 in the core network 30 requests the container orchestrator 52 to secure resources for the pod (step Sc21). That is, a label corresponding to the slice ID is passed to the container orchestrator 52. The container orchestrator 52 requests the resource control device 54 to indicate which pod in the table held in the reservation unit 544 the pod corresponding to the label corresponds to, and if the corresponding pod is the target pod, to indicate where the pod should be placed (step Sc22).

[0037] If the pod is the target pod, the reservation unit 544 responds to the container orchestrator 52 with the placement resource reserved for the target pod (step Sc23). Furthermore, if the pod is an untargeted pod, the reservation unit 544 responds to that effect to the container orchestrator 52.

[0038] If the requested pod is the target pod, the container orchestrator 52 deploys the pod to the destination resource included in the response (step Sc24).

[0039] For example, if slice iD is "low latency and high reliability," the pod corresponding to the label corresponds to pod #D, which is the target pod. Therefore, the reservation unit 544 responds that the pod corresponding to the label corresponds to pod #D, which is the target pod, and that the worker nodes Wrk #2, Wrk #5, Wrk #8, and Wrk #9 are the resources to which it is to be placed. The container orchestrator 52 deploys pod #D. Here, in the first NF instance generation, if pods #A and #D have already been deployed as shown in Fig. 8, the container orchestrator 52 deploys pod #D to the worker node Wrk#8 reserved for pod #D as shown in Fig. 9.

[0040] After the pod is deployed, the container orchestrator 52 responds to the core network 30 that resources for the pod have been secured (step Sc25), and the core network 30 responds to the base station 20 that a session has been established (step Sc26).

[0041] 10 is a diagram illustrating an example in which an out-of-target pod is deployed. In detail, the example illustrates an example in which pods #A and #D are deployed to each worker node as shown in FIG. 9 or reserved as destination resources, and pod #B, which is an out-of-target pod, is newly deployed. Pod #D has already been reserved for worker node Wrk9, but not all of worker node Wrk9 is reserved for Pod #D, leaving some remaining. Figure 10 shows an example in which Pod #D, with a "small" amount of resources, is deployed on the remaining resources of worker node Wrk9.

[0042] Next, the operation when the parameters input by the input device 40 are corrected will be described. As described above, the parameters shown in Fig. 3 are used to reserve placement resources for the target pods, pods #A and #D, as shown in Fig. 6. Pods #A and #D are deployed by generating NF instances as shown in Fig. 8, and pod #D is additionally deployed on worker node Wrk#8 by establishing a session as shown in Fig. 9.

[0043] In this state, it is assumed that pod #E as shown in FIG. 11 is added to the parameters shown in FIG. In detail, assume that for pod #E, whose NF instance is upf#2, the minimum number of replicas is "2", the maximum number of replicas is "4", the resource is "large", the placement constraint is "distribution priority", and the slice is "low latency, high reliability".

[0044] In the resource control device 54, which has received the parameters to which pod #E has been added from the input device 40, the determination unit 542 determines whether or not to make pod #E the target pod. In this example, pod #E is the same as pod #D except for the minimum number of replicas and the maximum number of replicas, so the determination unit 542 determines pod #E to be the target pod for the same reasons as for pod #D. The result of this determination is sent to the reservation unit 544.

[0045] The reservation unit 544 receives the determination result and reserves the destination resources for pod #E. The reservation unit 524 reserves the number of worker nodes to be used as the destination resources for pod #E to be "4." It is also assumed that the amount of resources consumed by pod #D on one worker node is greater than the amount of resources consumed by pod #D. At this point, as shown in Figure 9, pods #A and #D are deployed to each worker node or reserved as destination resources, so it is not possible to secure destination resources for pod #E.

[0046] For this reason, the reservation unit 544, for example, creates new worker nodes wrk#10 to #12, and reserves worker nodes wrk#10 and Wrk#11 and the free worker nodes Wrk#3 and Wrk#6 in FIG. 9 as placement resources for pod#E. That is, as shown in FIGS. 12 and 13, the reservation unit 544 reserves the worker nodes Wrk#3, Wrk#6, wrk#10, and Wrk#11 as placement resources for pod#E.

[0047] In this way, even if there are not enough resources to place the target pod, parameters can be added sequentially by creating new worker nodes.

[0048] Next, an operation will be described when a non-target pod temporarily requests a large number of resources due to an increase in load such as burst traffic. Here, assuming a state as shown in FIG. 10, it is assumed that the non-target pod requesting many resources is pod #B. In detail, the state shown in Figure 10 is as follows: first, of the worker nodes Wrk#1, Wrk#4, and Wrk#7 reserved as destination resources for pod #A, pod #A is deployed to worker node Wrk#1; second, of the worker nodes Wrk#2, Wrk#5, Wrk#8, and Wrk#9 reserved as destination resources for pod #D, pod #D is deployed to worker nodes Wrk#2, Wrk#5, and Wrk#8; and third, of the worker nodes Wrk#3 and Wrk#6 and worker node Wrk#8, pod #B, a non-target pod, is deployed to areas other than the areas reserved as destination resources for pod #D. In this state, Pod #B is already deployed to three worker nodes. Since the maximum number of replicas of Pod #B is 5, Pod #B can be deployed to two additional worker nodes.

[0049] Here, pod #A is deployed to worker node Wrk#1, but worker nodes Wrk#4 and Wrk#7 are only reserved and not actually deployed. Therefore, as shown in FIG. 14, the container orchestrator 52 issues a scale-out command to release the reservation of worker nodes Wrk#4 and Wrk#7, and deploys pod #B to the worker nodes Wrk#4 and Wrk#7 that have become vacant due to the release. By releasing the reservation in this way, it is possible to deal with cases where a large number of resources are temporarily requested. It is also possible to configure the resource, for which the reservation was cancelled and the pod was deployed, to be re-reserved as the placement destination for the original target pod once the temporary increase in load has been resolved.

[0050] Next, in order to explain the advantages of the system 1 according to this embodiment, a system according to a comparative example will be described. In the comparative example, the resource control device 54 in the embodiment does not exist, and resources are secured by cooperation between the core network 30 and the container orchestrator 52.

[0051] Specifically, in the comparative example, a table linking slice IDs and labels is maintained, and when a connection request occurs, a pod corresponding to the slice ID is deployed. In other words, in the comparative example, resources are secured on demand.

[0052] In the comparative example, if the resources in the base device are limited and surplus resources cannot be secured, the following inconveniences are expected to occur. In detail, in the comparative example, when a new pod that consumes a large amount of resources is to be deployed, if all the worker nodes are deployed to other pods, there will be no worker node to provide an execution environment for the new pod, and therefore the new pod cannot be deployed. Also, when scaling out a pod that must be distributed, if there are no available worker nodes in the AZ where you are trying to distribute and provide an execution environment, you will not be able to deploy the pod you are trying to increase.

[0053] In contrast, in this embodiment, the destination resources for the target pod are reserved before the target pod is started, so the inconvenience of not being able to deploy it by other pods can be resolved. Also, in this embodiment, the inconvenience of not being able to deploy the pod to be augmented when scaling out can be resolved because the destination resources are reserved. Furthermore, in this embodiment, even if a resource is reserved, if it is not deployed, the reservation for that resource is cancelled and an untargeted pod is added or newly deployed to that resource, making it possible to deal with cases where a large number of resources are temporarily requested.

[0054] <Other> The block diagrams used to explain the above embodiments illustrate functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., via wire, wireless, etc.) and these multiple devices. The functional blocks may be realized by combining the single device or multiple devices with software. Functions include, but are not limited to, judgment, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (component) that performs transmission is called a transmitting unit or a transmitter. As described above, there are no particular limitations on how each of these is implemented.

[0055] The notification of information is not limited to the aspects / embodiments described in the present disclosure and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0056] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xG (x is, for example, an integer or a decimal point)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or any other suitable system, and next generation systems extended, modified, created, or defined based on these. In addition, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may be applied.

[0057] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0058] In the present disclosure, a specific operation performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network worker nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network worker node other than the base station (for example, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network worker node other than the base station, a combination of multiple other network worker nodes (for example, an MME and an S-GW) may also be used.

[0059] Information (described later) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network worker nodes.

[0060] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0061] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0062] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0063] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0064] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0065] Information, signals, and the like described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, and the like that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. Terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). A signal may also be a message. A component carrier (CC) may also be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

[0066] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0067] Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, radio resources may be indicated by indexes. The names used for the above-described parameters are not limiting in any way. Furthermore, mathematical formulas using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0068] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. A base station may also be referred to by terms such as a macrocell, small cell, femtocell, picocell, etc. A base station can accommodate one or multiple (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​at least one of the base station and base station subsystem that provides communication services within this coverage. In this disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control and operate based on the information.

[0069] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably. A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0070] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on operational commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device, such as a sensor. Furthermore, the base station in the present disclosure may be interpreted as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be referred to as, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal may be configured to have the functions possessed by the above-mentioned base station. Furthermore, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be interpreted as a side channel. Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the base station may be configured to have the functions possessed by the above-mentioned user terminal.

[0071] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0072] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0073] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0074] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0075] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0076] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0077] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0078] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0079] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0080] It is clear to those skilled in the art that the present invention is not limited to the embodiments described in this specification. The present invention can be implemented in modified and altered forms without departing from the spirit and scope of the present invention as defined by the claims. Therefore, the description in this specification is intended to be illustrative and does not have any limiting meaning on the present invention. Furthermore, multiple aspects selected from the aspects exemplified in this specification may be combined. [Explanation of symbols]

[0081] 30...core network, 50...infrastructure device, 52...container orchestrator, 54...resource control device, 542...decision unit, 544...reservation unit.

Claims

1. A determination unit that determines, from among a plurality of pods, a target pod for which resources for executing the application are to be secured based on attributes corresponding to the pod, which is the smallest execution unit of the application; A reservation unit that reserves resources that provide an execution environment for the target pod according to attributes of the target pod before starting the target pod; Resource control unit including:

2. The resource is a worker node that provides an execution environment for a pod, The reservation unit reserves a worker node on which the target pod is to be placed, The attributes include a minimum number of replicas; When starting the target pod, The pod is placed on the worker nodes of the number specified by the minimum replica number among the worker nodes reserved by the reservation unit. The resource control device of claim 1 .

3. After the number of target pods specified by the minimum replica number is placed on the worker node, The target pod is additionally placed on a worker node on which the target pod has not yet been placed, among the worker nodes reserved by the reservation unit. The resource control device according to claim 2 .

4. Among the plurality of pods, non-target pods other than the target pod are The non-target pod is placed on a worker node that is not reserved by the reservation unit or a worker node on which the target pod is placed and on which the non-target pod can be placed. The resource control device according to claim 3 .

5. The non-target pod is placed on a worker node on which the target pod has not been placed, among the worker nodes reserved by the reservation unit. The resource control device according to claim 4 .

Images