# US 12,771,609 B2 · Scaling arrangement and method performed therein > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,771,609 B2 - Document ID: US12771609B2 - Status: Granted - Kind: B2 - Application number: 18/718,323 - Filed: 2021-12-10 - Published: 2025-03-20 - Granted: 2026-10-20 - Earliest claimed: 2021-12-10 - Assignees: Telefonaktiebolaget LM Ericsson (publ) - Applicants: Telefonaktiebolaget LM Ericsson (publ) - Inventors: Xuejun Cai; Jinhua Feng; Selome Kostentinos Tesfatsion - Web page: https://patentgrep.com/patent/US12771609B2 ## CPC - H04L 41/0897: by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities - H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Embodiments herein disclose for example a method performed by a scaling arrangement (13) for managing resources in a communication network associated with a multiple cloud infrastructure, wherein the scaling arrangement comprises a global auto-scaler (131) and one or more local auto-scalers (132). The scaling arrangement determines, at the global auto-scaler (131) of the scaling arrangement (13), to perform one or more actions based on at least resource information stored at the global auto-scaler; wherein the resource information is associated with resources structured in multiple clouds comprising one or more local clusters of resources. The one or more actions comprise modifying a parameter related to at least one of the resources of the multiple clouds. The scaling arrangement sends a modifying request to at least one local auto-scaler out of the one or more local auto-scalers (132), requesting to perform one or more operations related to the modified parameter. ## Claims ### Claim 1 A method performed by a scaling arrangement for managing resources in a communication network associated with a multiple cloud infrastructure, wherein the scaling arrangement comprises a global auto-scaler and one or more local auto-scalers, the method comprising: creating and initiating, by the global auto-scaler, the one or more local auto-scalers in each of the multiple clouds according to global configuration information including global scaling rules and parameters, wherein each local auto-scaler is responsible for local horizontal autoscaling within its respective cluster and is extended to request the global auto-scaler to perform global scaling when local scaling cannot be fulfilled; dynamically modifying, by the global auto-scaler, configuration of the one or more local auto-scalers based on collected performance metrics and information provided by one or more load balancers; determining, at the global auto-scaler of the scaling arrangement, to perform one or more actions based on at least resource information stored at the global auto-scaler; wherein the resource information is associated with resources structured in multiple clouds comprising one or more local clusters of resources; and wherein the one or more actions comprise modifying a parameter related to at least one of the resources of the multiple clouds; and sending a modifying request to at least one local auto-scaler out of the one or more local auto-scalers, requesting to perform one or more operations related to the modified parameter. ### Claim 2 (depends on 1) The method according to claim 1, wherein modifying the parameter comprises at least one of: modifying a number of resources of the multiple clouds; creating an autoscaling rule for the at least one local auto-scaler out of the one or more local auto-scalers; and creating a parameter for the at least one local auto-scaler out of the one or more local auto-scalers. ### Claim 3 (depends on 2) The method according to claim 2, wherein the modifying request requests at least one of: adding a resource; removing the resource; and using at least one of the created autoscaling rule and parameter. ### Claim 4 (depends on 2) The method according to claim 2, further comprising: sending one or more instructions to the one or more load balancers, wherein the one or more instructions are related to at least one of: the created autoscaling rule, the created parameter, and the modified number of resources, wherein the one or more instructions to the one or more load balancers comprise instructions to modify a traffic redirection policy based on the modified number of resources, wherein the modified traffic redirection policy routes user equipment requests to clusters where new resources have been deployed to prevent performance imbalance. ### Claim 5 (depends on 4) The method according to claim 4, wherein the one or more instructions indicate a redirection of requests from one or more user equipments in the communication network. ### Claim 6 (depends on 1) The method according to claim 1, wherein the resource information comprises one or more global performance metrics and the determination is performed periodically and comprises checking the one or more global performance metrics provided from one or more local clusters of resources of respective cloud and based on the checked one or more global performance metrics evaluating if a global scaling is needed. ### Claim 7 (depends on 1) The method according to claim 1, further comprising: determining, by a local auto-scaler of the one or more local auto-scalers managing a local cluster of resources, that global scaling of resources is needed for the local cluster of resources; and sending, by the local auto-scaler, a request to the global auto-scaler, requesting for global scaling; and wherein the one or more actions to be performed are determined based on the request and the resource information stored at the global auto-scaler. ### Claim 8 (depends on 7) The method according to claim 7, wherein the request to the global auto-scaler indicates at least one of a cluster identity, ID, a type of the scaling, and a desired amount of resources. ### Claim 9 (depends on 1) The method according to claim 1, wherein the resource information comprises one or more of: global scaling policy and parameter; geographic information; statistical performance metrics from one or more local clusters of respective cloud; and data collected from one or more load balancers. ### Claim 10 (depends on 1) The method according to claim 1, further comprising performing at the at least one local auto-scaler, an operation based on the modifying request. ### Claim 11 (depends on 1) A non-transitory computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods according to claim 1, as performed by the scaling arrangement. ### Claim 12 A scaling arrangement for managing resources in a communication network associated with a multiple cloud infrastructure, wherein the scaling arrangement comprises a global auto-scaler and one or more local auto-scalers, and processing circuitry, wherein the processing circuitry is configured to: create and initiate, by the global auto-scaler, the one or more local auto-scalers in each of the multiple clouds according to global configuration information including global scaling rules and parameters, wherein each local auto-scaler is responsible for local horizontal autoscaling within its respective cluster and is extended to request the global auto-scaler to perform global scaling when local scaling cannot be fulfilled; dynamically modify, by the global auto-scaler, configuration of the one or more local auto-scalers based on collected performance metrics and information provided by one or more load balancers; determine, at the global auto-scaler of the scaling arrangement, to perform one or more actions based on at least resource information stored at the global auto-scaler; wherein the resource information is associated with resources structured in multiple clouds comprising one or more local clusters of resources; and wherein the one or more actions comprise modifying a parameter related to at least one of the resources of the multiple clouds; and send a modifying request to at least one local auto-scaler out of the one or more local auto-scalers, requesting to perform one or more operations related to the modified parameter. ### Claim 13 (depends on 12) The scaling arrangement according to claim 12, wherein the scaling arrangement is configured to modify the parameter by at least one of: modifying a number of resources of the multiple clouds; creating an autoscaling rule for the at least one local auto-scaler out of the one or more local auto-scalers; and creating a parameter for the at least one local auto-scaler out of the one or more local auto-scalers. ### Claim 14 (depends on 13) The scaling arrangement according to claim 13, wherein the modifying request requests at least one of: adding a resource; removing the resource; and using at least one of the created autoscaling rule and parameter. ### Claim 15 (depends on 13) The scaling arrangement according to claim 13, wherein the scaling arrangement is further configured to send one or more instructions to one or more load balancers, wherein the one or more instructions are related to at least one of: the created autoscaling rule, the created parameter, and the modified number of resources, wherein the one or more instructions to the one or more load balancers comprise instructions to modify a traffic redirection policy based on the modified number of resources, wherein the modified traffic redirection policy routes user equipment requests to clusters where new resources have been deployed to prevent performance imbalance. ### Claim 16 (depends on 15) The scaling arrangement according to claim 15, wherein the one or more instructions indicate a redirection of requests from one or more user equipments in the communication network. ### Claim 17 (depends on 12) The scaling arrangement according to claim 12, wherein the resource information comprises one or more global performance metrics and the scaling arrangement is configured to perform the determination periodically and to check the one or more global performance metrics provided from one or more local clusters of resources of respective cloud and based on the checked one or more global performance metrics evaluate if a global scaling is needed. ### Claim 18 (depends on 12) The scaling arrangement according to claim 12, wherein the scaling arrangement is configured to: determine by a local auto-scaler out the one or more local auto-scaler managing a local cluster of resources, that global scaling of resources is needed for the local cluster of resources; send by the local auto-scaler, a request to the global auto-scaler, requesting for global scaling; and wherein the scaling arrangement is further configured to determine the one or more actions to be performed based on the request and the resource information stored at the global auto-scaler. ### Claim 19 (depends on 18) The scaling arrangement according to claim 18, wherein the request to the global auto-scaler indicates at least one of a cluster identity, ID, a type of the scaling, and a desired amount of resources. ### Claim 20 (depends on 12) The scaling arrangement according to claim 12, wherein the resource information comprises one or more of: global scaling policy and parameter; geographic information; statistical performance metrics from one or more local clusters of respective cloud; and data collected from one or more load balancers.