CN112260966A - Flow distribution control method, device and storage medium - Google Patents
Flow distribution control method, device and storage medium Download PDFInfo
- Publication number
- CN112260966A CN112260966A CN202011113864.6A CN202011113864A CN112260966A CN 112260966 A CN112260966 A CN 112260966A CN 202011113864 A CN202011113864 A CN 202011113864A CN 112260966 A CN112260966 A CN 112260966A
- Authority
- CN
- China
- Prior art keywords
- service instance
- service
- weight
- preheating
- started
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 3
- 239000000243 solution Substances 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000006583 body weight regulation Effects 0.000 description 1
- 201000010099 disease Diseases 0.000 description 1
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000012088 reference solution Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/805—QOS or priority aware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
- H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/78—Architectures of resource allocation
- H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/801—Real time traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/82—Miscellaneous aspects
- H04L47/826—Involving periods of time
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to the technical field of communication networks, in particular to a traffic distribution control method, a traffic distribution control device and a storage medium. The method comprises the following steps: when a newly added started target service instance exists, calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance for each service instance in the service to which the target service instance belongs; the preheating parameters comprise a preheating period and a preheating step length; issuing the weight of each service instance to an Istio agent, and performing flow distribution through the Istio agent according to the weight of each service instance; and when the starting condition of the timing task is met, after the preheating step length is separated, the step of calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance is executed again. The method and the device achieve the effects that the weight of the newly started service instance can be continuously increased in the preheating period, so that the service instance can gradually enter a full state, the high load when the service instance is just started is avoided, and the service stability is improved.
Description
Technical Field
The present application relates to the field of communications network technologies, and in particular, to a method, an apparatus, and a storage medium for controlling traffic distribution.
Background
In the service network environment based on the Istio, after a class of service instances are started, the class of service instances need to enter a full-service state according to the service starting time asymptotically, and the request traffic of the class of service instances also needs to be increased asymptotically according to the service starting time and gradually reaches a full-service state. The issue does not currently provide a corresponding mechanism, nor a reference solution to the corresponding problem.
Any service instance has the same weight as other instances after the completion of the initiation, resulting in the service entering a full service state immediately after initiation. The service instance does not enter a full service state after being started, and instantaneous full access can cause the service instance to work badly with diseases on one hand, and on the other hand, a large number of user requests fail within a period of time after being started due to the limitation of service capacity, so that the service stability is influenced.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, an apparatus, and a storage medium for controlling traffic distribution, so as to solve the problems in the prior art.
According to a first aspect, an embodiment of the present application provides a traffic distribution control method, including:
when a newly added started target service instance exists, calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance for each service instance in the service to which the target service instance belongs; the preheating parameters comprise a preheating period and a preheating step length;
issuing the weight of each service instance to an Istio agent, and performing flow distribution through the Istio agent according to the weight of each service instance;
and when the starting condition of the timing task is met, after the preheating step length is separated, the step of calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance is executed again.
Optionally, the calculating the weight of the service instance according to the start time and the preheating parameter of the service instance includes:
the weight of the service instance is min (current time-start time of the service instance, warm-up period).
Optionally, the step of detecting whether the timing task starting condition is met includes:
detecting whether the weight reaches the preheating period;
and if the weight does not reach the preheating period, determining that the starting condition of the timing task is met.
Optionally, the method further includes:
and if the weight reaches the preheating period, ending the process.
Optionally, if the target service corresponding to the target service instance includes at least two service instances and the at least two service instances are continuously started within a time less than a preset interval, the method further includes:
acquiring the actual last starting time of each started service instance in the target service at the current moment;
acquiring the last starting time of the association of the target service when the weight is issued last time;
and if the associated last starting time is earlier than the actual last starting time, determining that the timed task starting condition is not met.
Optionally, the method further includes:
and if the associated last starting time is not earlier than the actual last starting time, determining that the starting condition of the timing task is met.
Optionally, the step of determining whether the target service instance exists includes:
monitoring a service data center, wherein the service data center comprises registration information registered after a service instance is started;
and determining whether a newly added started service instance exists according to the monitored service data center.
In a second aspect, there is provided a traffic distribution control apparatus, the apparatus comprising a memory and a processor, the memory having at least one program instruction stored therein, and the processor implementing the method according to the first aspect by loading and executing the at least one program instruction.
In a third aspect, there is provided a computer storage medium having stored therein at least one program instruction for loading and execution by a processor to implement the method of the first aspect.
Calculating the weight of each service instance in the service to which the target service instance belongs according to the starting time and the preheating parameter of the service instance when a newly-added started target service instance exists; the preheating parameters comprise a preheating period and a preheating step length; issuing the weight of each service instance to an Istio agent, and performing flow distribution through the Istio agent according to the weight of each service instance; and when the starting condition of the timing task is met, after the preheating step length is separated, the step of calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance is executed again. The problems that the service instance load is high and the service stability is poor when the service instance enters a full service state immediately after being started in the prior art are solved; the method and the device achieve the effects that the weight of the newly started service instance can be continuously increased in the preheating period, so that the service instance can gradually enter a full state, the high load when the service instance is just started is avoided, and the service stability is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood and to implement them in accordance with the contents of the description, the following detailed description is given with reference to the preferred embodiments of the present invention and the accompanying drawings.
Drawings
Fig. 1 is a flowchart of a method of controlling traffic distribution according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In addition, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
Referring to fig. 1, a flowchart of a method for controlling traffic distribution according to an embodiment of the present application is shown, where the method is used in the isio, and as shown in fig. 1, the method includes:
In general, one service may include a plurality of service instances, and the present embodiment may preset a warm-up parameter for each service instance, where the preset parameter may include whether to warm up (enableWarmUp), a warm-up period (warmpupurzation), and a warm-up step size (warmpinnterval). The preheating period and the preheating step length are both preset values, for example, the preheating period may be 90s, and the preheating step length may be 5 s. To customize the attach for warm-up, i' o/eableWarmUp is supported to control at the service granularity whether warm-up is to be turned on for a particular service/instance.
In actual implementation, the preheating periods and preheating step lengths corresponding to different types of service instances may be the same or different, and this embodiment does not limit this. In addition, during actual implementation, the preheating parameters and the preheating step length of each service instance can be dynamically adjusted according to historical statistical data of each service instance in the cluster, so that the elasticity of the whole cluster and the service is improved.
After the service instance starts, the service instance may register a start state with a service data center, which may be a K8S API Server. Correspondingly, the step of determining whether the target service instance exists in this step may include:
(1) monitoring a service data center, wherein the service data center comprises registration information registered after the service instance is started;
(2) and determining whether a newly added started service instance exists according to the monitored service data center.
When a new target service instance exists in the service data center, the subsequent steps can be executed.
In addition, in this embodiment, after the target service instance is monitored, the target service instance and the starting time of the target service instance may be recorded. That is, for each service instance that has been started, the Istio may obtain the start time for each service instance.
Then, for each service instance in the target service, the isitio may calculate the weight of each service instance according to the start time and the preheating parameter of the service instance, where the weight of each service instance is: min (current time-start time of service instance, warm-up period).
102, issuing the weight of each service instance to an Istio agent, and distributing flow according to the weight of each service instance through the Istio agent;
after the Istio calculates the weight of each service instance, the Istio may issue the calculated weight to the Istio-Proxy. Alternatively, it may be issued to all Istio-Proxy agents within the cluster. The Istio-Proxy distributes traffic among the service instances according to the weight of each service instance.
And 103, when the starting condition of the timing task is met, after the preheating step length is separated, the step of calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance is executed again.
After the weight of each service instance is issued, it can be determined whether the timed task starting condition is satisfied, and when the timed task starting condition is satisfied, after the preheating step length is spaced, step 101 is executed again.
The step of judging whether the timing task starting condition is met may include:
(1) detecting whether the weight reaches the preheating period;
(2) and if the weight does not reach the preheating period, determining that the starting condition of the timing task is met.
When the preheating period is not reached, the weight of the service instance can be continuously increased, and at the moment, the weight of the service instance needs to be updated, so that the condition that the starting condition of the timing task is met can be determined; on the contrary, when the weight reaches the preheating period, the weight reaches the maximum value, and at this time, the weight of the service instance does not need to be calculated again, so that the timed task starting condition can be judged not to be met.
In a possible embodiment, assuming that there are 3 service instances of B1, B2 and B3 in the target service, the method includes (1) service instance starting; (2) the service instance registers a starting state in a K8S API Server; (3) the Istio acquires a newly started service instance by monitoring the K8S API Server; (4) calculating the weight of each service instance; (5) issuing the calculated weight to the Istio-Proxy, and distributing the flow according to each weight by the Istio-Proxy through a route; (6) and when the timing starting condition is met, periodically triggering and calculating the weight according to the preheating step length, and executing issuing.
In summary, when a newly-added started target service instance exists, for each service instance in the service to which the target service instance belongs, calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance; the preheating parameters comprise a preheating period and a preheating step length; issuing the weight of each service instance to an Istio agent, and performing flow distribution through the Istio agent according to the weight of each service instance; and when the starting condition of the timing task is met, after the preheating step length is separated, the step of calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance is executed again. The problems that the service instance load is high and the service stability is poor when the service instance enters a full service state immediately after being started in the prior art are solved; the method and the device achieve the effects that the weight of the newly started service instance can be continuously increased in the preheating period, so that the service instance can gradually enter a full state, the high load when the service instance is just started is avoided, and the service stability is improved.
In a possible implementation manner of the foregoing embodiment, if the target service corresponding to the target service instance includes at least two service instances and the at least two service instances are continuously started within a time less than a preset interval, according to the method described in the foregoing embodiment, the weight needs to be frequently calculated and issued, for example, in a start period including 30 service instances, a preheating period of 90s, and a preheating step size of 5s, and in an extreme case, up to 540 times of calculation and issue may be performed within 90 s. Therefore, in order to reduce the processing complexity caused by calculation and issue, the step of determining whether the timing task start condition is satisfied in the above embodiment may further include:
(1) acquiring the actual final starting time of each started service instance in the target service at the current moment;
the actual last start time is the start time of the latest started service instance in the target service at the current time, that is, the actual last start time is max (service instance start time).
(2) Acquiring the last starting time of the association of the target service when the weight is issued last time;
when the Istio issues the weight to the Istio agent each time, the issued task is associated to the current service last starting time, namely as the associated last starting time.
(3) And if the associated last starting time is earlier than the actual last starting time, determining that the timed task starting condition is not met.
If the associated last starting time is earlier than the actual last starting time, it is indicated that a new service instance is started again, that is, the weight is updated again, and at this time, even if the weight obtained by judgment in the above embodiment does not reach the preheating period, it is still determined that the timed task starting condition is not satisfied; on the contrary, if the associated last starting time is not earlier than the actual last starting time, the timed task starting condition is judged to be met for real-time weight regulation and control.
By the method, the times of updating the weight and issuing the weight can be reduced, the configuration is issued once at the same time for the same service regardless of the change of the service instances, the issuing interval is not less than the preheating step length in the calculation, and the processing complexity of the Istio is reduced.
The present embodiment also provides a flow distribution control apparatus, which includes a memory and a processor, where the memory stores at least one program instruction, and the processor implements the method according to the foregoing embodiment by loading and executing the at least one program instruction.
The present embodiment also provides a computer storage medium, in which at least one program instruction is stored, and the at least one program instruction is used for being loaded and executed by a processor to implement the method of the above embodiment.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (9)
1. A traffic distribution control method, for use in the isio, the method comprising:
when a newly added started target service instance exists, calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance for each service instance in the service to which the target service instance belongs; the preheating parameters comprise a preheating period and a preheating step length;
issuing the weight of each service instance to an Istio agent, and performing flow distribution through the Istio agent according to the weight of each service instance;
and when the starting condition of the timing task is met, after the preheating step length is separated, the step of calculating the weight of the service instance according to the starting time and the preheating parameter of the service instance is executed again.
2. The method of claim 1, wherein the calculating the weight of the service instance according to the start-up time and the warm-up parameter of the service instance comprises:
the weight of the service instance is min (current time-start time of the service instance, warm-up period).
3. The method of claim 1, wherein detecting whether the timed task start condition is met comprises:
detecting whether the weight reaches the preheating period;
and if the weight does not reach the preheating period, determining that the starting condition of the timing task is met.
4. The method of claim 3, further comprising:
and if the weight reaches the preheating period, ending the process.
5. The method according to any one of claims 1 to 4, wherein if the target service corresponding to the target service instance comprises at least two service instances and the at least two service instances are started consecutively within a time less than a preset interval, the method further comprises:
acquiring the actual last starting time of each started service instance in the target service at the current moment;
acquiring the last starting time of the association of the target service when the weight is issued last time;
and if the associated last starting time is earlier than the actual last starting time, determining that the timed task starting condition is not met.
6. The method of claim 5, further comprising:
and if the associated last starting time is not earlier than the actual last starting time, determining that the starting condition of the timing task is met.
7. The method of any of claims 1 to 4, wherein the step of determining whether the target service instance exists comprises:
monitoring a service data center, wherein the service data center comprises registration information registered after a service instance is started;
and determining whether a newly added started service instance exists according to the monitored service data center.
8. A traffic distribution control apparatus, comprising a memory having stored therein at least one program instruction, and a processor for loading and executing the at least one program instruction to implement the method of any one of claims 1 to 7.
9. A computer storage medium having stored therein at least one program instruction for loading and execution by a processor to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113864.6A CN112260966B (en) | 2020-10-18 | 2020-10-18 | Traffic distribution control method, apparatus and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113864.6A CN112260966B (en) | 2020-10-18 | 2020-10-18 | Traffic distribution control method, apparatus and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112260966A true CN112260966A (en) | 2021-01-22 |
| CN112260966B CN112260966B (en) | 2024-01-12 |
Family
ID=74244658
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011113864.6A Active CN112260966B (en) | 2020-10-18 | 2020-10-18 | Traffic distribution control method, apparatus and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112260966B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040167980A1 (en) * | 2003-02-20 | 2004-08-26 | International Business Machines Corporation | Grid service scheduling of related services using heuristics |
| US20170289307A1 (en) * | 2016-03-29 | 2017-10-05 | Amazon Technologies, Inc. | System Interaction Monitoring And Component Scaling |
| CN108845876A (en) * | 2018-04-09 | 2018-11-20 | 阿里巴巴集团控股有限公司 | A kind of method and device of traffic assignments |
| CN108881367A (en) * | 2018-04-09 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of service request processing method, device and equipment |
| CN109726043A (en) * | 2018-09-07 | 2019-05-07 | 网联清算有限公司 | Application service control method and device |
| CN111597048A (en) * | 2020-05-15 | 2020-08-28 | 上海交通大学 | Micro-service scheduling method and system based on service quality and electronic equipment |
-
2020
- 2020-10-18 CN CN202011113864.6A patent/CN112260966B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040167980A1 (en) * | 2003-02-20 | 2004-08-26 | International Business Machines Corporation | Grid service scheduling of related services using heuristics |
| US20170289307A1 (en) * | 2016-03-29 | 2017-10-05 | Amazon Technologies, Inc. | System Interaction Monitoring And Component Scaling |
| CN108845876A (en) * | 2018-04-09 | 2018-11-20 | 阿里巴巴集团控股有限公司 | A kind of method and device of traffic assignments |
| CN108881367A (en) * | 2018-04-09 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of service request processing method, device and equipment |
| CN109726043A (en) * | 2018-09-07 | 2019-05-07 | 网联清算有限公司 | Application service control method and device |
| CN111597048A (en) * | 2020-05-15 | 2020-08-28 | 上海交通大学 | Micro-service scheduling method and system based on service quality and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| 郝庭毅;吴恒;吴国全;张文博;: "面向微服务架构的容器级弹性资源供给方法", 计算机研究与发展, no. 03, pages 144 - 155 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112260966B (en) | 2024-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10361928B2 (en) | Cluster instance management system | |
| CN109889999B (en) | Flow pool management method, system and terminal of Internet of things card | |
| CN110673948A (en) | Cloud game resource scheduling method, server and storage medium | |
| JP2009244945A (en) | Load distribution program, load distribution method, load distribution device and system including the same | |
| CN106464733A (en) | Method and device for adjusting virtual resources in cloud computing | |
| CN111277640B (en) | User request processing method, device, system, computer equipment and storage medium | |
| CN111585824B (en) | Resource distribution method, device and system and electronic equipment | |
| CN110677459A (en) | Resource adjusting method and device, computer equipment and computer storage medium | |
| CN111918314A (en) | Mobile network optimization method and system based on distributed SDN | |
| CN112068934A (en) | Control system and method for container cloud service instance contraction | |
| CN109151070A (en) | Service scheduling method, the electronic device of point-to-point CDN based on block chain | |
| CN112689007A (en) | Resource allocation method, device, computer equipment and storage medium | |
| CN102413514A (en) | Data distribution device and data distribution system | |
| CN111796933A (en) | Resource scheduling method, device, storage medium and electronic equipment | |
| CN112260966A (en) | Flow distribution control method, device and storage medium | |
| WO2021083196A1 (en) | Network traffic migration method and apparatus | |
| CN107346308B (en) | Method and device for calling data in cluster system | |
| CN116455830A (en) | Method for realizing high-availability distributed QOS of storage gateway | |
| CN114791818B (en) | Storage controller system update method, system, computer device and storage medium | |
| CN106980545B (en) | Remote calling method and device | |
| CN112311599B (en) | Cloud resource allowance alarm method and device and server | |
| CN111190728B (en) | Resource adjustment method and device | |
| CN114124763A (en) | Method and system for measuring broadband access rate | |
| CN107786614B (en) | TMS application downloading self-adaptive strategy method | |
| CN112084089A (en) | Method, device and equipment for determining upper limit of power consumption of data center node and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240515 Address after: 510000 No. 106 Fengze East Road, Nansha District, Guangzhou City, Guangdong Province Patentee after: Guangzhou dinghang Information Technology Service Co.,Ltd. Country or region after: China Address before: 215000 Room 101, 5 building, 78 Ling Ling Road, hi tech Zone, Suzhou, Jiangsu. Patentee before: SUZHOU SIMAWEI TECHNOLOGY Co.,Ltd. Country or region before: China |