CN109358996B - Processing method and processing system for change request - Google Patents
Processing method and processing system for change request Download PDFInfo
- Publication number
- CN109358996B CN109358996B CN201811168961.8A CN201811168961A CN109358996B CN 109358996 B CN109358996 B CN 109358996B CN 201811168961 A CN201811168961 A CN 201811168961A CN 109358996 B CN109358996 B CN 109358996B
- Authority
- CN
- China
- Prior art keywords
- change request
- change
- hardware
- request
- engine
- 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.)
- Expired - Fee Related
Links
- 238000012508 change request Methods 0.000 title claims abstract description 272
- 238000012545 processing Methods 0.000 title claims abstract description 19
- 238000003672 processing method Methods 0.000 title claims abstract description 9
- 230000004044 response Effects 0.000 claims abstract description 77
- 230000008859 change Effects 0.000 claims abstract description 73
- 238000011156 evaluation Methods 0.000 claims abstract description 50
- 238000000034 method Methods 0.000 claims abstract description 31
- 230000002159 abnormal effect Effects 0.000 claims abstract description 28
- 230000008569 process Effects 0.000 claims abstract description 19
- 230000006870 function Effects 0.000 claims description 58
- 238000004088 simulation Methods 0.000 claims description 10
- 238000004364 calculation method Methods 0.000 claims description 9
- 230000009286 beneficial effect Effects 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 claims description 4
- 239000000872 buffer Substances 0.000 claims description 3
- 230000000977 initiatory effect Effects 0.000 claims description 3
- 230000008263 repair mechanism Effects 0.000 claims description 3
- 230000008439 repair process Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 4
- 238000007792 addition Methods 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2247—Verification or detection of system hardware configuration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
Abstract
The application discloses a processing method and a processing system for a change request, wherein the processing method for the change request comprises the following steps: receiving a request for a hardware change; performing function evaluation of hardware, and judging whether the requirement of executing the change request is met; if the request meets the regulation, judging the rationalization of the change request; if the change request is reasonable, the response time is compared and the change request is executed. The processing method and the processing system for the change request can judge whether the change request can be executed or not and whether an abnormal response exists in the execution process or not, simulate to execute the change request, and improve the safety of hardware when the change request is executed.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and a system for processing a change request.
Background
The hardware facilities in modern networks include one or a combination of components in a chassis, motherboard, CPU, or memory. When an administrator wants to change a hardware facility, manual change may take time or even cause an error, if the change is performed by an automation tool, rationalization of the change and an influence caused by the change cannot be judged, if the change is performed by an automation tool, an unknown risk is brought to the hardware facility, and a change process cannot be monitored in real time.
Disclosure of Invention
When a user or an administrator requests to change a hardware facility, whether the change request can be executed or not and whether an abnormal response exists in the execution process or not can be judged, the change request is simulated to be executed, and the safety of hardware when the change request is executed is improved.
A method of processing a change request, comprising the steps of: receiving a request for a hardware change; performing function evaluation of hardware, and judging whether the requirement of executing the change request is met; if the request meets the regulation, judging the rationalization of the change request; if the change request is reasonable, the response time is compared and the change request is executed.
As above, wherein performing a functional evaluation of the hardware comprises the sub-steps of: function evaluation value A for hardwareiCarrying out initialization; calculating a functional weight value G of hardwarei(ii) a Function evaluation value A of update hardwarei'; wherein: a. thei’＝Ai+Gi；Gi＝S1*(1-Xi)+S2*Mi+S3*Ci(ii) a Wherein XiTo storage space usage, MiFor memory idleness, CiS1, S2, and S3 represent weighting coefficients of the hardware storage space availability, the memory usage, and the CPU usage in the node state, and S1+ S2+ S3 is 1.
As above, wherein the storage space idle rate Xi＝(Ti-Ui)/Ti，TiIs the total memory space of the hardware, UiMemory space is used for hardware.
As above, among others, the function evaluation value A of the hardwareiIf' greater than 1, it means that the specification is satisfied, and the change request is executed.
The above, wherein the judging of rationalization of the change request comprises the sub-steps of: simulating execution of the change request; judging whether the change request is reasonable or not, and if the change request is not reasonable, the process exits; and if so, judging whether the change request has abnormal response in the execution process.
As above, if there is an exception response, an exception handling policy is invoked, an exception handling mechanism is started, and the change request of the exception is repaired.
As above, wherein comparing response times and executing a change request comprises the sub-steps of: calculating a response time t1 of the hardware before the execution of the change request and a response time t2 of the hardware after the execution of the change request; if the response time t1 is less than t2, the change request is not allowed to execute, and if t1 is greater than t2, the change request is allowed.
As above, in response to comparing the response times t1 and t2, the function of the hardware is evaluated again, whether there is a beneficial or abnormal response to the execution of the change request is determined, and if the function evaluation value a after the execution of the change request is determinedi"greater than or equal to the update evaluation value Ai' the change request is again allowed to execute, otherwise the change request denies execution.
A change request processing system includes a change request processor, one or more request buffers, a change engine, a response time calculation unit, and a change store queue; the change request processor comprises a function evaluation module and a function evaluation value updating module;
the change request processor receives the change request, performs function evaluation on hardware facilities, judges whether the hardware meets the regulation for executing the change request, calls a change engine to simulate and execute the change request if the hardware meets the regulation, and stores the reasonably executed change request in a change storage queue; the change engine responds to the hardware to execute the change request and makes rationalization judgment on the change request; the request cache is used for storing the change request received by the change request processor; the response time calculation unit is used for responding to the change request to be executed, calculating the response time t2 of the hardware after the change request is executed, comparing the response time t2 with the response time t1 of the hardware before the change request is executed, and if t1 is larger than t2, the change request processor calls the change request in the change storage queue and executes the change request; the change store queue stores post-execution permission change requests, and the change request handler invokes the change request and executes in response to the change request being permitted.
The method comprises the following steps of (1) enabling a change engine to comprise a simulation execution module and an exception handling starting module; the change engine responds to the hardware capable of executing the change request, calls the simulation execution module to perform simulation execution of the change request, monitors execution of the change request in real time, calls the exception handling starting module when exception handling occurs, and starts the exception repair mechanism to repair the change request.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings.
FIG. 1 is a schematic diagram of an internal structure of a change request processing system according to an embodiment of the present application;
FIG. 2 is a block diagram of a sub-module of a change request processor provided in accordance with an embodiment of the present application;
FIG. 3 is a sub-module diagram of a change request analysis unit provided according to an embodiment of the present application;
FIG. 4 is a flow chart of a method for processing a change request provided according to an embodiment of the present application;
fig. 5 is a flowchart of a hardware function evaluation method provided according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application are clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. 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 application.
The application relates to a method and a system for executing a change request. According to the method and the device, when a user or an administrator requests to change the hardware facility, whether the change request can be executed or not and whether an abnormal response exists in the execution process or not can be judged, the change request is simulated to be executed, and the safety of hardware when the change request is executed is improved.
Fig. 1 is a schematic diagram illustrating an internal structure of a change request processing system provided in the present application.
The change request processing system includes a change request processor 110, one or more request buffers 120, a change engine 130, a response time calculation unit 140, a change store queue 150. As shown in fig. 2, the change request processor 110 includes a function evaluation module 210 and a function evaluation value update module 220. As shown in FIG. 3, change engine 130 includes a simulation execution module 310 and an exception handling initiation module 320.
The change request handler 110 receives the change request, performs a function evaluation of the hardware facility, determines whether the hardware complies with a specification for executing the change request, invokes the change engine 130 to simulate executing the change request if the hardware complies with the specification, and stores the executed change request in the change storage queue 150.
Specifically, the change request processor 110 calls the function evaluation module 210 to evaluate the function of the hardware facility, and calls the function evaluation value update module 220 to update the function evaluation value, and determines whether the hardware can execute the change request.
Specifically, in response to the hardware being able to execute the change request, the change engine 130 invokes the simulation execution module 310 to perform simulation execution of the change request, and monitors execution of the change request in real time, and if an exception occurs, invokes the exception handling initiation module 320 to initiate an exception recovery mechanism to recover the change request.
The request cache 120 is used to store change requests received by the change request handler 110.
Illustratively, the request cache 120 includes a plurality of entries, each for holding an instance of a change request, ordered in the order in which the request cache was added, the change request being added to the request cache 120 from the end of the queue and the change request being fetched from the head of the queue.
Preferably, one or more entries are capable of accommodating instances of one or more change requests.
Periodically, as one embodiment, in response to a change request being added, the change request handler 110 performs execution of the change request according to the order of the change requests in the request cache 120.
Alternatively, the change request handler 110 selects the request cache 120 in a random, round-robin, weighted round-robin manner, and the request cache 120 may be prioritized and adjusted.
The response time calculation unit 140 is executed in response to the change request, calculates the response time t2 of the hardware after the change request is executed, and compares the response time t2 with the response time t1 of the hardware before the change request is executed, and if t1 is greater than t2, the change request processor 110 retrieves and executes the change request in the change store queue 150.
Further, the response time calculation unit 140 sends a signal to the change request processor 110 after comparing the response time, the change request processor 110 evaluates the function of the hardware again, and if the function evaluation value is higher than the original function evaluation value, the execution of the change request is permitted.
The change store queue 150 is executed in response to a change request, storing the change request, and specifically, as opposed to a request cache, the change request stored in the change store queue 150 is eligible for execution by a change request handler invoking the change request.
Preferably, in response to the change request being interrupted, the change request can continue to be sent or the change processor 110 invokes the change request from the change store queue 150.
FIG. 4 is a flow chart of a method of processing a change request provided in accordance with the present application;
in this embodiment, a change request handler is provided to perform the change request, the change request handler being coupled to other units or modules that manage the change request, the change request handler performing the change request when a change is requested by one or more components in the hardware facility.
Step S410: a request for a hardware change is received.
The request for change is targeted to one or a combination of components in the chassis, motherboard, CPU, or memory in the hardware facility, and the change request is executed by change request processor 110.
The change request may be to change the memory of the hardware, and for example, the change request may be to increase the memory. As another example, the change request may make a change to a combination of components in hardware.
Illustratively, the change request may be stored in the request cache 120, and the change request handler 110 retrieves the change request from the request cache 120.
Step S420: and performing function evaluation of the hardware, and judging whether the hardware conforms to the regulation for executing the change request.
The change request processor 110 receives a request for hardware change, acquires function information of current hardware, performs function evaluation on the hardware in combination with the function information, acquires a function evaluation result of the hardware before the change, and determines whether the change request can be executed according to the function evaluation result of the hardware. As shown in fig. 5, wherein the functional evaluation of the hardware comprises the following sub-steps:
step 510: function evaluation value A for hardwareiInitialization is performed.
Wherein 0<Ai<1, if AiIf the number of requests is less than 1, the change request is refused to be executed, if A isiHardware is able to perform change requests greater than 1, where the function evaluates value AiIs changeable according to the functional weight value GiCan realize the function evaluation value A of hardwareiIs changed.
Step 520: calculating a functional weight value G of hardwarei。
The function evaluation criteria of each component in the hardware are different, and the function evaluation criteria of each component form the function evaluation criteria of the hardware, for example, the function evaluation criteria of the hardware is performed according to the storage space of the hardware, and the following data are used for measurement, specifically, the storage space utilization rate X is includediMemory idle rate MiCPU idle rate CiAnd linearly weighting the three parameters to obtain a hardware function weight value Gi＝S1*(1-Xi)+S2*Mi+S3*CiWherein the storage space idle rate Xi＝(Ti-Ui)/Ti，TiIs the total memory space of the hardware, UiS1, S2, and S3 represent weighting coefficients of the hardware storage space availability, the memory usage, and the CPU usage in the node state, preferably, S1+ S2+ S3 is 1, and S1, S2, and S3 may be determined by actual conditions, which is not limited herein.
Illustratively, the node state represents several working states of hardware, such as standby, working or sleeping.
According to the function weight value G of hardwarei＝S1*(1-Xi)+S2*Mi+S3*CiCan derive, the storage space usage rate XiThe smaller, the memory idle rate MiThe greater the CPU idle rate CiThe larger the value, the function weight GiThe larger.
Step 530: and updating the function evaluation value of the hardware.
According to the function weight value GiAnd initialized function evaluation value AiAdding to obtain the function evaluation value Ai', i.e. Ai’＝Ai+GiUntil the function evaluation value A of the hardwarei' greater than 1, a change request of hardware can be performed.
If the hardware does not conform to the specification, the process exits, and if the hardware conforms to the specification, the step S430 is executed: rationalizing the change request is judged.
Specifically, the change engine 130 corresponding to the change request is set in hardware in advance, the change engine 130 can determine whether the change request is reasonable, and the change request processor 110 calls the change engine 130 in real time during the execution of the change request to determine whether the change request can be changed during the execution and whether the change can be continuously executed, and if not, the process exits and the change request is rejected.
Further, the change request is simulated and executed in the simulation execution module 310 in advance, and the change engine 130 is a virtual system (or a copy of hardware) after simulating the hardware system, in order to determine the rationalization of the change request and whether the change request would have an abnormal effect, for example, if the change request is to increase the memory, the change engine 130 can determine whether the frequency of the CPU is sufficient, the hard disk can be matched to the CPU, and the change request can actually increase memory in executing the change request, and if the results envisioned in the change engine are reached, the change request is considered to be reasonable, whether an abnormal response exists in the execution process of the change request is judged, if no abnormal response exists, the step S440 is continuously executed, if the expected result is not reached or the change request is abnormal, and the normal operation of the hardware is influenced, the change engine 130 invokes the abnormal handling strategy in the abnormal handling starting module 320.
Specifically, the exception handling policy can prompt an administrator or a user about exception of a change request, and can also invoke an exception handling mechanism stored in the exception handling policy to analyze and repair the change request of the exception, and further, the repair mechanism is customized by the user and can be modified.
Step S440: the response times are compared and a change request is executed.
Specifically, a change request is executed in hardware, the response time calculation unit 140 calculates the response time t1 before the change request is executed, calculates the response time t2 after the change request is executed, compares the response times t1 and t2, if the response time t1 is less than t2, the change request is not allowed to be executed again, if t1 is greater than t2, the change request is allowed, and by default, the execution can be directly allowed the next time the change request is executed in the hardware.
As another embodiment, in the execution process of the change request, if the change engine 130 does not detect an abnormal response of the change request, the response time calculation unit 140 compares the response times and sends a signal to the change request processor 110, the change request processor 110 re-evaluates the function of the hardware and determines whether there is a beneficial or abnormal response after the execution of the change request, the evaluation method is the same as the principle of steps S510-530, and if a new function evaluation value a is obtainedi"greater than or equal to Ai' then the change request brings a beneficial response to the hardware (or no beneficial or abnormal response to the hardware), then the change request is allowed to execute again in response to the change request, otherwise the change request denies execution.
Further, in response to the change request being executed, the change request is stored in change store queue 150, the change request in change store queue 150 may be submitted by a hardware facility administrator or a component in the hardware facility. The power down prevention policy may be used, for example, when the system is powered down, the execution of the change request is interrupted, and in response to the system being powered up again, the change storage queue 150 continues to send the interrupted change request, so that even when the system is powered down, each change request may be provided to the change request processor 110 to continue executing work, and the change request processor 110 triggers the change engine to simulate the execution of the change request to determine whether the change request is legal and whether there is an abnormal response in the execution, and if so, the step S440 is continued.
The application has the following beneficial effects:
(1) the processing method and the processing system for the change request can judge whether the change request can be executed or not, simulate to execute the change request, and improve the safety of hardware when the change request is executed.
(2) The processing method and the processing system for the change request can monitor and judge whether the change request has abnormal response in the execution process in real time, and reduce risks existing when the hardware facility executes the change request.
Although the present application has been described with reference to examples, which are intended to be illustrative only and not to be limiting of the application, changes, additions and/or deletions may be made to the embodiments without departing from the scope of the application.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (9)
1. A method for processing a change request, comprising the steps of:
receiving a request for a hardware change;
performing function evaluation of hardware, and judging whether the requirement of executing the change request is met;
if the request meets the regulation, judging the rationalization of the change request;
if the change request is reasonable, comparing the response time and executing the change request;
during the execution process of the change request, detecting the exception of the change request; if the abnormal response of the change request is not detected, re-evaluating the function of the hardware after responding to the comparison response time;
wherein, the function evaluation of the hardware comprises the following substeps:
function evaluation value A for hardwareiCarrying out initialization;
calculating a functional weight value G of hardwarei；
Function evaluation value A of update hardwarei’；
Wherein:
Ai’＝Ai+Gi；
Gi＝S1*(1-Xi)+S2*Mi+S3*Ci；
wherein XiTo storage space usage, MiFor memory idleness, CiS1, S2, and S3 represent weighting coefficients of the hardware storage space idle rate, the memory usage rate, and the CPU usage rate in the node state, and S1+ S2+ S3 is 1;
wherein 0< Ai <1, the change request is denied execution if Ai is less than 1, and the change request is executed if Ai is greater than 1;
setting a corresponding change engine for the change request in hardware in advance, and judging whether the change request is reasonable or not by the change engine; simulating and executing a change request in advance, if the change request is to increase the memory, judging whether the frequency of a CPU is enough, whether a hard disk is matched with the CPU and whether the change request really increases the memory in the process of executing the change request by a change engine, if the expected result in the change engine is achieved, judging that the change request is reasonable, judging whether the change request has abnormal response in the executing process, and if the change request has no abnormal response, comparing the response time and executing the change request; if the expected result of the change engine is not reached or the change request is abnormal, the change engine calls an abnormal processing strategy;
wherein the exception handling policy is to prompt an administrator or user for a change request exception.
2. The method of claim 1, wherein the storage space idle rate X isi＝(Ti-Ui)/Ti，TiIs the total memory space of the hardware, UiMemory space is used for hardware.
3. The change request processing method according to any one of claims 1-2, wherein when the function evaluation value a of the hardware is satisfiediIf' greater than 1, it means that the specification is satisfied, and the change request is executed.
4. A method of handling change requests according to claim 1, characterized in that the rationalization of the change request comprises the sub-steps of:
simulating execution of the change request;
judging whether the change request is reasonable or not, and if the change request is not reasonable, the process exits; and if so, judging whether the change request has abnormal response in the execution process.
5. The method of claim 4, wherein if there is an exception response, invoking an exception handling policy, starting an exception handling mechanism, and repairing the exception change request.
6. The change request processing method according to claim 1, wherein comparing response times and executing a change request comprises the sub-steps of:
calculating a response time t1 of the hardware before the execution of the change request and a response time t2 of the hardware after the execution of the change request;
if the response time t1 is less than t2, the change request is not allowed to execute, and if t1 is greater than t2, the change request is allowed.
7. The method as claimed in claim 6, wherein the hardware function is evaluated again in response to comparing the response time t1 with t2, and whether there is a beneficial or abnormal response after the change request is executed is determined, and if the function evaluation value A after the change request is executed is determinedi"greater than or equal to the update evaluation value Ai' the change request is again allowed to execute, otherwise the change request denies execution.
8. A change request processing system includes a change request processor, one or more request buffers, a change engine, a response time calculation unit, and a change store queue; the change request processor comprises a function evaluation module and a function evaluation value updating module;
the change request processor receives the change request, performs function evaluation on hardware facilities, judges whether the hardware meets the regulation for executing the change request, calls a change engine to simulate and execute the change request if the hardware meets the regulation, and stores the reasonably executed change request in a change storage queue;
the change engine responds to the hardware to execute the change request and makes rationalization judgment on the change request;
the request cache is used for storing the change request received by the change request processor;
the response time calculation unit is used for responding to the change request to be executed, calculating the response time t2 of the hardware after the change request is executed, comparing the response time t2 with the response time t1 of the hardware before the change request is executed, and if t1 is larger than t2, the change request processor calls the change request in the change storage queue and executes the change request;
the change storage queue stores a change request after execution is allowed, and the change request processor calls the change request and executes the change request in response to the change request being allowed;
during the execution process of the change request, detecting the exception of the change request; if the abnormal response of the change request is not detected, re-evaluating the function of the hardware after responding to the comparison response time;
wherein the function evaluation of the hardware by the change request processor comprises the following substeps:
function evaluation value A for hardwareiCarrying out initialization;
calculating a functional weight value G of hardwarei；
Function evaluation value A of update hardwarei’；
Wherein:
Ai’＝Ai+Gi；
Gi＝S1*(1-Xi)+S2*Mi+S3*Ci；
wherein XiTo storage space usage, MiFor memory idleness, CiFor CPU idle rate, S1, S2, S3 indicate node statesWeighting coefficients of hardware storage space idle rate, memory utilization rate and CPU utilization rate, wherein S1+ S2+ S3 is 1;
wherein 0< Ai <1, the change request is denied execution if Ai is less than 1, and the change request is executed if Ai is greater than 1;
setting a corresponding change engine for the change request in hardware in advance, and judging whether the change request is reasonable or not by the change engine; simulating and executing a change request in advance, if the change request is to increase the memory, judging whether the frequency of a CPU is enough, whether a hard disk is matched with the CPU and whether the change request really increases the memory in the process of executing the change request by a change engine, if the expected result in the change engine is achieved, judging that the change request is reasonable, judging whether the change request has abnormal response in the executing process, and if the change request has no abnormal response, comparing the response time and executing the change request; if the expected result of the change engine is not reached or the change request is abnormal, the change engine calls an abnormal processing strategy;
wherein the exception handling policy is to prompt an administrator or user for a change request exception.
9. The change request processing system according to claim 8, wherein the change engine includes a simulation execution module and an exception handling initiation module;
the change engine responds to the hardware capable of executing the change request, calls the simulation execution module to perform simulation execution of the change request, monitors execution of the change request in real time, calls the exception handling starting module when exception handling occurs, and starts the exception repair mechanism to repair the change request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811168961.8A CN109358996B (en) | 2018-10-08 | 2018-10-08 | Processing method and processing system for change request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811168961.8A CN109358996B (en) | 2018-10-08 | 2018-10-08 | Processing method and processing system for change request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109358996A CN109358996A (en) | 2019-02-19 |
| CN109358996B true CN109358996B (en) | 2021-09-24 |
Family
ID=65348510
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811168961.8A Expired - Fee Related CN109358996B (en) | 2018-10-08 | 2018-10-08 | Processing method and processing system for change request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109358996B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101605224A (en) * | 2008-06-09 | 2009-12-16 | 汤姆森许可贸易公司 | Be used for handling the method that channel changes request in the IPTV system |
| CN101682355A (en) * | 2007-03-12 | 2010-03-24 | 思科技术公司 | Method and apparatus providing scalability for channel change requests in a switched digital video system |
| CN101686379A (en) * | 2008-09-24 | 2010-03-31 | 阿尔卡特朗讯公司 | Improved device for ip TV channel selection |
| CN104737549A (en) * | 2012-10-18 | 2015-06-24 | Lg电子株式会社 | Apparatus and method for processing an interactive service |
| CN105653338A (en) * | 2015-12-30 | 2016-06-08 | 广东欧珀移动通信有限公司 | Application updating method and device |
| CN106294073A (en) * | 2016-08-15 | 2017-01-04 | 合智能科技（深圳）有限公司 | Service calling method and device |
| CN104023088B (en) * | 2014-06-28 | 2017-04-19 | 山东大学 | Storage server selection method applied to distributed file system |
| CN107872352A (en) * | 2017-11-27 | 2018-04-03 | 瑞斯康达科技发展股份有限公司 | A kind of performance test methods of network management system, apparatus and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7337103B2 (en) * | 2004-01-15 | 2008-02-26 | International Business Machines Corporation | Method and apparatus for the automatic correction of faulty wires in a logic simulation hardware emulator / accelerator |
| US7840397B2 (en) * | 2005-12-02 | 2010-11-23 | Derek Chiou | Simulation method |
| CN100518357C (en) * | 2006-02-14 | 2009-07-22 | 信息产业部电信传输研究所 | System and method of testing effects of interference between mobile communication systems |
| CN103677956B (en) * | 2013-12-06 | 2017-05-31 | 北京奇虎科技有限公司 | A kind of method and apparatus of the application operation of simulation mobile device on the computing device |
-
2018
- 2018-10-08 CN CN201811168961.8A patent/CN109358996B/en not_active Expired - Fee Related
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101682355A (en) * | 2007-03-12 | 2010-03-24 | 思科技术公司 | Method and apparatus providing scalability for channel change requests in a switched digital video system |
| CN101605224A (en) * | 2008-06-09 | 2009-12-16 | 汤姆森许可贸易公司 | Be used for handling the method that channel changes request in the IPTV system |
| CN101686379A (en) * | 2008-09-24 | 2010-03-31 | 阿尔卡特朗讯公司 | Improved device for ip TV channel selection |
| CN104737549A (en) * | 2012-10-18 | 2015-06-24 | Lg电子株式会社 | Apparatus and method for processing an interactive service |
| CN104023088B (en) * | 2014-06-28 | 2017-04-19 | 山东大学 | Storage server selection method applied to distributed file system |
| CN105653338A (en) * | 2015-12-30 | 2016-06-08 | 广东欧珀移动通信有限公司 | Application updating method and device |
| CN106294073A (en) * | 2016-08-15 | 2017-01-04 | 合智能科技（深圳）有限公司 | Service calling method and device |
| CN107872352A (en) * | 2017-11-27 | 2018-04-03 | 瑞斯康达科技发展股份有限公司 | A kind of performance test methods of network management system, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109358996A (en) | 2019-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6689873B2 (en) | Techniques for offloading and onloading data to processor / coprocessor configurations | |
| US9003239B2 (en) | Monitoring and resolving deadlocks, contention, runaway CPU and other virtual machine production issues | |
| US8424007B1 (en) | Prioritizing tasks from virtual machines | |
| US20080104608A1 (en) | Starting up at least one virtual machine in a physical machine by a load balancer | |
| JP5524117B2 (en) | Power management based on automatic load detection | |
| US20090094183A1 (en) | Predictive Monitoring Method and System | |
| CN110928661B (en) | Thread migration method, device, equipment and readable storage medium | |
| WO2012121714A1 (en) | Performing a change process based on a policy | |
| CN109325349A (en) | A kind of method for managing security, terminal device and computer readable storage medium | |
| US20110071811A1 (en) | Using event correlation and simulation in authorization decisions | |
| US10885180B2 (en) | Detection of emulated computer systems using variable difficulty challenges | |
| US20090326869A1 (en) | Performance evaluating apparatus | |
| CN104737134A (en) | System and method for operating system agnostic hardware validation | |
| Sammy et al. | Energy efficient security preserving vm live migration in data centers for cloud computing | |
| CN106951321B (en) | Method and device for managing CPU (Central processing Unit) resources of virtual machine | |
| US10558810B2 (en) | Device monitoring policy | |
| KR102365839B1 (en) | Method and device for monitoring application performance | |
| TW201610672A (en) | Debugging in a data processing apparatus | |
| CN112463367A (en) | Method and system for optimizing performance of storage system, electronic equipment and storage medium | |
| CN109684126B (en) | Memory verification method for ARM equipment and ARM equipment for executing memory verification | |
| CN111083062A (en) | Weight mechanism-based current limiting method and device, computer equipment and storage medium | |
| CN109358996B (en) | Processing method and processing system for change request | |
| CN111159038B (en) | Method for simulating CPU load and electronic equipment | |
| US20110225593A1 (en) | Interface-based environmentally sustainable computing | |
| WO2022161100A1 (en) | Edge computing server resetting method and device |
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 | ||
| CB02 | Change of applicant information |
Address after: 075000, No. three, B District, 04 East Zone, Chahar Century Square, Hebei, Zhangjiakou Applicant after: Zhangjiakou dachengyuan science and Technology Service Co.,Ltd. Address before: 075000, No. three, B District, 04 East Zone, Chahar Century Square, Hebei, Zhangjiakou Applicant before: ZHANGJIAKOU HAOYANG TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201112 Address after: 101300 Beijing Shunyi District Airport Street, No. 1 Anhua Street, 1st Building, 1st Floor, No. 2159 Applicant after: BEIJING LONGPU INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 075000, No. three, B District, 04 East Zone, Chahar Century Square, Hebei, Zhangjiakou Applicant before: Zhangjiakou dachengyuan science and Technology Service Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210906 Address after: 100000 1003, floor 10 (11), building 12, Futong East Street, Chaoyang District, Beijing Applicant after: Beijing Tianhong Ruizhi Technology Co.,Ltd. Address before: 101300 Beijing Shunyi District Airport Street, No. 1 Anhua Street, 1st Building, 1st Floor, No. 2159 Applicant before: BEIJING LONGPU INTELLIGENT TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20210924 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |