CN113419880A - Cloud mobile phone root authority acquisition method, related device and computer program product - Google Patents
Cloud mobile phone root authority acquisition method, related device and computer program product Download PDFInfo
- Publication number
- CN113419880A CN113419880A CN202110812432.2A CN202110812432A CN113419880A CN 113419880 A CN113419880 A CN 113419880A CN 202110812432 A CN202110812432 A CN 202110812432A CN 113419880 A CN113419880 A CN 113419880A
- Authority
- CN
- China
- Prior art keywords
- root
- request
- mobile phone
- service
- controlling
- 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 62
- 238000004590 computer program Methods 0.000 title claims abstract description 17
- 238000012545 processing Methods 0.000 claims abstract description 90
- 238000004891 communication Methods 0.000 claims description 15
- 230000008859 change Effects 0.000 claims description 11
- 230000008569 process Effects 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 8
- 238000006243 chemical reaction Methods 0.000 claims description 2
- 239000000126 substance Substances 0.000 claims 1
- 239000002699 waste material Substances 0.000 abstract description 4
- 238000013473 artificial intelligence Methods 0.000 abstract description 3
- 238000001514 detection method Methods 0.000 description 18
- 239000003795 chemical substances by application Substances 0.000 description 12
- 238000010586 diagram Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Abstract
The invention provides a method and a device for acquiring cloud mobile phone root authority, electronic equipment, a computer readable storage medium and a computer program product, and relates to the technical field of artificial intelligence such as cloud service, a cloud platform and cloud resources. One embodiment of the method comprises: storing the obtained root request of the cloud mobile phone into a message queue; controlling a preset execution service to take out a root request to be processed from a message queue; and controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed. According to the implementation mode, the full-automatic root processing of the cloud mobile phone is realized through the provided message queue and the execution service, manual intervention by management personnel is not needed, precious labor force waste is avoided, the efficiency of root operation is improved, and the probability of operation errors is reduced.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to the field of artificial intelligence technologies such as cloud services, cloud platforms, and cloud resources, and in particular, to a method and an apparatus for acquiring a root authority of a cloud mobile phone, an electronic device, a computer-readable storage medium, and a computer program product.
Background
With the development of cloud services, more and more applications or services are moved from the user side to the cloud side locally, and the cloud application, the cloud desktop and the cloud mobile phone give the calculation result of the cloud side to the user side in a picture projection mode, so that the cost of the user side can be reduced as much as possible.
Different from local root operation directly performed by a user for obtaining the root authority of the intelligent mobile terminal, the user of the cloud mobile phone also needs to perform the root operation on the cloud mobile phone in certain scenes.
Disclosure of Invention
The embodiment of the disclosure provides a method and a device for acquiring cloud mobile phone root authority, electronic equipment, a computer readable storage medium and a computer program product.
In a first aspect, an embodiment of the present disclosure provides a method for acquiring a root authority of a cloud mobile phone, including: storing the obtained root request of the cloud mobile phone into a message queue; controlling a preset execution service to take out a root request to be processed from a message queue; and controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
In a second aspect, an embodiment of the present disclosure provides a cloud mobile phone root authority acquiring apparatus, including: the request storing unit is configured to store the acquired root request of the cloud mobile phone into a message queue; the request extracting unit is configured to control a preset execution service to extract the root request to be processed from the message queue; and the root execution unit is configured to control the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can implement the cloud mobile root authority obtaining method as described in any implementation manner of the first aspect.
In a fourth aspect, the present disclosure provides a non-transitory computer-readable storage medium storing computer instructions for enabling a computer to implement the cloud mobile phone root authority acquiring method as described in any implementation manner of the first aspect when executed.
In a fifth aspect, the present disclosure provides a computer program product including a computer program, where the computer program is capable of implementing the cloud cell phone root authority acquiring method as described in any implementation manner of the first aspect when executed by a processor.
The method for acquiring the cloud mobile phone root authority provided by the embodiment of the disclosure comprises the following steps of firstly, storing an acquired cloud mobile phone root request into a message queue; then, controlling a preset execution service to take out the root request to be processed from the message queue; and finally, controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
According to the cloud mobile phone root request processing method and the cloud mobile phone root request processing system, the full-automatic processing of the root of the cloud mobile phone is achieved through the message queue and the execution service provided in the technical scheme, namely, the message is forwarded between the user side and the cloud mobile phone resource providing side through the message queue, the cloud mobile phone root request taken out from the message queue can be executed through the execution service deployed at the cloud mobile phone resource providing side, the cloud mobile phone root request is automatically processed through the matching of the message queue and the cloud mobile phone resource providing side, manual intervention of management personnel is not needed, the waste of precious labor force in monotonous repeated work is avoided, the root operation efficiency is improved, and the probability of operation errors is reduced.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
Other features, objects and advantages of the disclosure will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture to which the present disclosure may be applied;
fig. 2 is a flowchart of a method for acquiring a cloud mobile phone root authority according to an embodiment of the present disclosure;
fig. 3 is a flowchart of another method for acquiring a cloud mobile phone root authority according to the embodiment of the present disclosure;
fig. 4 is a flowchart of controlling an execution service to complete a root operation in the method for acquiring a root authority of a cloud mobile phone according to the embodiment of the present disclosure;
fig. 5 is a schematic flow chart of a method for acquiring a cloud mobile phone root permission in an application scenario according to an embodiment of the present disclosure;
fig. 6 is a block diagram of a structure of a cloud mobile phone root authority acquiring apparatus according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of an electronic device adapted to execute a cloud mobile phone root authority obtaining method according to an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness. It should be noted that, in the present disclosure, the embodiments and features of the embodiments may be combined with each other without conflict.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the personal information of the related user all accord with the regulations of related laws and regulations, necessary security measures are taken, and the customs of the public order is not violated.
Fig. 1 illustrates an exemplary system architecture 100 to which embodiments of the cloud mobile root permission acquisition method, apparatus, electronic device, and computer-readable storage medium of the present disclosure may be applied.
As shown in fig. 1, the system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 101, 102, 103 to interact with the server 105 over the network 104 to enable cloud handset resources or the like provided by the server 105. Various applications for realizing information communication between the terminal devices 101, 102, and 103 and the server 105 may be installed on the terminal devices 101, 102, and 103, for example, a cloud mobile phone control application, a cloud mobile phone management application, an instant messaging application, and the like.
The terminal apparatuses 101, 102, 103 and the server 105 may be hardware or software. When the terminal devices 101, 102, 103 are hardware, they may be various electronic devices with display screens, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like; when the terminal devices 101, 102, and 103 are software, they may be installed in the electronic devices listed above, and they may be implemented as multiple software or software modules, or may be implemented as a single software or software module, and are not limited in this respect. When the server 105 is hardware, it may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server; when the server is software, the server may be implemented as a plurality of software or software modules, or may be implemented as a single software or software module, which is not limited herein.
The server 105 may provide various services through various built-in applications, for example, a cloud mobile phone control application that can provide various controls for cloud mobile phone resources, and when the server 105 runs the cloud mobile phone control application, the following effects may be achieved: firstly, acquiring a cloud mobile root request from terminal equipment 101, 102 and 103 through a network 104; then, storing the obtained cloud mobile phone root request into a message queue; next, controlling a preset execution service to take out the root request to be processed from the message queue; and finally, controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
Further, the server 105 may also perform feedback to the terminal devices 101, 102, and 103 according to the root result.
It should be noted that the cloud cell phone root request may be acquired from the terminal devices 101, 102, and 103 through the network 104, or may be pre-stored in a message queue provided locally in the server 105 or a message queue local to the non-server 105 in various manners. Thus, when the server 105 can detect a cloud root request directly from the message queue, the request can be taken directly from the message queue and started to execute. In this case, the exemplary system architecture 100 may also not include the terminal devices 101, 102, 103 and the network 104.
The method for acquiring the cloud mobile phone root authority provided in the subsequent embodiments of the present disclosure is generally executed by the server 105 that carries or provides the cloud mobile phone resources, and accordingly, the cloud mobile phone root authority acquiring apparatus is also generally disposed in the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring to fig. 2, fig. 2 is a flowchart of a method for acquiring a root authority of a cloud mobile phone according to an embodiment of the present disclosure, where the process 200 includes the following steps:
step 201: storing the obtained root request of the cloud mobile phone into a message queue;
this step is intended to store the acquired cloud handset root request into a message queue by an executing agent of the cloud handset root method (e.g., the server 105 shown in fig. 1). The cloud mobile phone root request represents the requirement of a user using a cloud mobile phone for performing root operation on a cloud mobile phone resource with a use permission, and the user usually uses a local terminal device owned by the user to send the cloud mobile phone root request to the execution main body, so that the execution main body can respond to the cloud mobile phone root request to meet the requirement.
The message queue is used for temporarily storing incoming cloud mobile phone root requests in the disclosure, and allowing subsequent execution services to take out the stored cloud mobile phone root requests from the message queue for execution. In some scenarios, the message queue may also be independently deployed outside the execution subject, and only the execution subject may take out the stored cloud mobile root request from the execution subject. In addition, according to the requirements of the practical application scene, the message queue or the message middleware can be selected from various specific message queues or message middleware such as ActiveMQ, RabbitMQ, ZeroMQ, Kafka, RocktetMQ and the like for use.
It should be noted that, in general, cloud mobile phone root requests stored in a message queue are distributed from different cloud mobile phone users, and also include enterprise users who use the messages in batches, and particularly when an enterprise user needs to batch root a plurality of cloud mobile phones which have usage rights, the enterprise user may occupy too many positions in the message queue in a short time, and further affect processing of the root requests of individual users, so how to perform better processing on batch operations performed by the enterprise user is also a problem considered by the present disclosure.
Step 202: controlling a preset execution service to take out a root request to be processed from a message queue;
on the basis of step 201, this step is intended to fetch the root request to be processed from the message queue by the execution service preset by the execution subject. The execution service is a single service or a set of a plurality of services which are deployed on the execution main body in advance and used for processing the root request of the cloud mobile phone and completing the root operation on the corresponding cloud mobile phone.
In order to increase the unit processing speed of the to-be-processed cloud mobile phone root requests (hereinafter referred to as the to-be-processed root requests) as much as possible, when the execution service has parallel processing, the execution service can be controlled to take out the to-be-processed root requests with the maximum parallel processing number from the message queue each time, and then the parallel processing capacity of the execution service is fully utilized to increase the unit processing efficiency.
Furthermore, considering that the resources that can be allocated to the execution service to implement parallel processing may change according to the change of the running state of the execution main body, the processing error frequency may be increased according to the fixed maximum parallel processing parameter, so the maximum parallel processing number may be adjusted according to the network communication quality between the execution service and the execution service, or the maximum parallel processing number may be adjusted according to the remaining load of the server where the execution service is located, and the maximum parallel processing number may be adjusted according to the two parameters by combining the actual situation as much as possible according to the xor, thereby ensuring that each request of the parallel processing can be successfully completed.
Step 203: and controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
On the basis of step 202, in this step, the executing agent controls the executing service to perform root on the target cloud mobile phone corresponding to the root request to be processed, that is, the executing agent needs to determine the target cloud mobile phone to be subjected to root operation by the user according to the root request to be processed, and then the executing agent completes root on the target cloud mobile phone under the condition that the operation object is determined.
Considering that whether a target cloud mobile phone has already acquired root permission (that is, whether the root operation has been successfully performed before) or not may not be clear when a user initiates a cloud mobile phone root request, and then directly issuing the cloud mobile phone root request, in order to avoid doing useless work, the method can also be used for controlling the execution service to inquire the permission acquisition state of the target cloud mobile phone corresponding to the root request to be processed, and when the permission acquisition state is not root, controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed. And if the permission acquisition state is root or root is not allowed, directly returning corresponding notification information.
According to the cloud mobile phone root authority obtaining method provided by the embodiment of the disclosure, full-automatic root processing of a cloud mobile phone is realized through the provided message queue and the provided execution service, namely, message forwarding is performed between the user side and the cloud mobile phone resource providing side by means of the message queue, the cloud mobile phone root request taken out from the message queue can be executed by the execution service deployed at the cloud mobile phone resource providing side, and then automatic processing of the cloud mobile phone root request is realized through matching of the message queue and the cloud mobile phone resource providing side, manual intervention by a manager is not needed, so that while precious labor force is prevented from being wasted in monotonous repeated work, the root operation efficiency is improved, and the probability of occurrence of operation errors is reduced.
Referring to fig. 3, fig. 3 is a flowchart of another method for acquiring root rights of a cloud mobile phone according to an embodiment of the present disclosure, where the process 300 includes the following steps:
step 301: storing the obtained root request of the cloud mobile phone into a message queue;
step 302: responding to batch root requests to be processed, the number of which exceeds the maximum parallel processing number, continuously stored in the message queue, and controlling the message queue to convert the batch root requests into a single batch processing instruction;
the present embodiment is directed to the following cases in this step: the cloud mobile phone root requests stored in the message queue comprise batch root requests which are continuously stored by enterprise users at one time and the quantity of which exceeds the maximum parallel processing quantity, for example, an enterprise user generates a request for root operation on 100 cloud handsets at a time, namely, the maximum parallel processing number of the executed services is assumed to be 10 for 100 cloud mobile phone root requests, that is, according to the conventional processing mode, the executed services need to be divided into at least 10 batches to complete the root operation of the 100 cloud mobile phones, these batch-performed operations may affect different batches of cloud phone root conditions due to the burst of intermediate factors, therefore, in order to process the 100 cloud mobile phone root requests as uniformly as possible, the embodiment controls the message queue to convert the batch root requests into a single batch processing instruction in this step, i.e. a root request that originally had only one processing object per thread is converted into a single batch instruction with 100 processing objects.
Generally, since the 100 cloud handsets have similarity in object numbers and are generally consecutive in numbers, a batch processing instruction having 100 processing objects does not usually list numbers or identity information of 100 complete processing objects, but usually adopts a number segment or a code segment or plays the same effect based on common characteristics (such as identification of a certain enterprise). Therefore, the problem that the maximum parallel capability cannot be completely processed at one time can be avoided through the operation of the step, and the processing of the cloud mobile phone root request of the individual user can be carried out as far as possible.
Step 303: controlling a preset execution service to take out a batch processing instruction from a message queue;
step 304: the control execution service analyzes a processing object set corresponding to the batch processing instruction;
step 305: the control execution service performs root on each processing object in the processing object set.
In step 302, in steps 303 to 305, after the execution subject control execution service fetches the batch processing instruction from the message queue, a processing object set corresponding to the batch processing instruction is first parsed, and then a root operation is performed on each processing object in the processing object set.
Different from the embodiment shown in the process 200, the present embodiment mainly provides a way of converting multiple batch root requests into a single batch processing instruction for a case where batch root requests with a number exceeding the maximum parallel processing number are continuously stored in a message queue, so as to avoid potential problems caused by batch processing of batch requests of the same enterprise user as much as possible, and better provide processing of cloud mobile phone root requests of individual users.
On the basis of any of the above embodiments, in view of the complexity in a practical application scenario, that is, in addition to meeting the root request of the user, the execution subject actually providing the cloud mobile phone resource generally needs to provide other services in order to meet other requirements, an implementation manner is further specifically provided herein, in which the execution service is formed by multiple subdivided services: referring to fig. 4, fig. 4 is a flowchart illustrating a method for controlling an execution service to complete a root operation in a cloud mobile phone root authority obtaining method according to an embodiment of the present disclosure, where the process 400 includes the following steps:
step 401: controlling the comprehensive management service to monitor the message change condition of the message queue;
step 402: responding to the message change condition as a newly increased request, and controlling the comprehensive management service to take out the newly increased root request to be processed from the message queue;
step 403: responding to the root request to be processed belonging to the root operation request, and controlling the comprehensive management service to issue the newly increased root request to the root management service;
the comprehensive management service is used as the most superior management service for monitoring the message change condition of the message queue, and when a newly added request needing to be processed by the comprehensive management service is detected, the comprehensive management service is taken out from the message queue and judges the service type of the specific request, and then is issued to the lower management service responsible for executing the corresponding type of service. In this embodiment, after taking out a new root operation request, the integrated management service determines that the request is a root operation, and therefore issues the root operation request to the root management service specially responsible for the root operation.
Besides root management service, the comprehensive management service can also be administered expansion/contraction capacity management service, abnormal repair service, cancellation reconstruction service and the like.
Step 404: controlling the root management service to determine a target cloud mobile phone corresponding to the newly added root request;
step 405: the root management service is controlled to issue a root request to a root execution service arranged on the target cloud mobile phone;
the root management service is responsible for determining the target cloud mobile phone corresponding to the newly added root request, and issuing an instruction of performing root operation on the determined target cloud mobile phone to the root execution service on the lower layer, namely, each cloud mobile phone is deployed with respective root execution service.
Step 406: and controlling the root execution service to perform root on the cloud mobile phone.
It should be noted that the service classification method provided in this embodiment is only an example, and in other application scenarios, other classification methods may also be used.
On the basis of any embodiment, the following steps can be added to improve the completeness of the scheme after root operation is performed on the target cloud mobile phone:
receiving an execution result of the root operation returned by the execution service;
adjusting root state information of the corresponding cloud mobile phone in a preset authority state table according to an execution result;
and sending feedback information to a sending end of the cloud mobile phone root request according to the adjusted authority state table.
Namely, the authority state table is used for recording the current authority state including the root authority of each cloud mobile phone, and the authority state table is used as an information source for feeding back the execution result of the request to the user.
Of course, the idea reflected by the above steps may be adaptively adjusted according to different practical application scenarios to achieve the same or similar technical effects, which are not listed here.
For further understanding, the present disclosure also provides a specific implementation scheme in conjunction with a specific application scenario, please refer to a timing diagram shown in fig. 5:
1. a user firstly initiates a request for detecting whether the equipment has performed root operation to a business service;
2. the service stores the received detection request into a message queue (rocktmq) by monitoring the transmission of a root instruction detection/execution result;
3. the management service in the execution service reads a newly stored detection request from the rocktmq by monitoring the sending of the root instruction in the rocktmq;
4. the management service judges that the detection object of the detection request is in a root state, and therefore the management service issues the detection object to the root management service (namely, management-proxy) related to the root;
the management-proxy service transparently transmits the content of the detection instruction to a root execution service (namely, a management-agent) deployed on the detection object;
the management-agent service transparently transmits the detection instruction to a target cloud mobile phone (namely virtual equipment);
7. the virtual equipment calls an internal detection command to detect the root state of the virtual equipment according to the received root detection instruction;
8. the virtual equipment returns the root detection result to the management-agent service;
transmitting the detection result to the management-proxy service through the management-agent service;
the management-proxy service transparently transmits the detection result to the management service;
11. the management service stores the detection result into the rocktmq;
the message queue for taking out the request to be processed by the management service and the message queue for feeding back the processing result of the request to the user can be different message queues or different parts in the same large message queue, so as to be used for isolating different types of messages.
12. The business service takes out the detection result from the rocktmq;
13. the business service displays the extracted detection result to the user;
14. the user sends an execution request to the service according to the seen detection result of the root;
15. the business service stores the received execution request into a rocktmq;
16. the management service in the execution service reads a newly stored execution request from the rocktmq;
17. the management service judges that the execution object of the execution request is the root authority, and therefore the management service issues the root authority to the management-proxy service related to the root;
the management-proxy service transparently transmits the content of the execution instruction to the management-agent service deployed on the execution object;
the management-agent service transparently transmits an execution instruction to the virtual equipment;
20. the virtual equipment calls an internal execution command to perform root operation according to the received root execution instruction;
21. the virtual equipment returns the root execution result to the management-agent service;
the management-agent service transparently transmits the execution result to the management-proxy service;
the management-proxy service transparently transmits the execution result to the management service;
24. the management service stores the execution result into the rocktmq;
25. the business service takes out an execution result from the rocktmq;
26. and the business service displays the extracted execution result to the user.
With further reference to fig. 6, as an implementation of the methods shown in the above diagrams, the present disclosure provides an embodiment of a cloud mobile phone root authority acquiring apparatus, where the embodiment of the apparatus corresponds to the embodiment of the method shown in fig. 2, and the apparatus may be specifically applied to various electronic devices.
As shown in fig. 6, the cloud cell phone root authority acquiring apparatus 600 of the present embodiment may include: a request storing unit 601, a request extracting unit 602, and a root executing unit 603. The request storing unit 601 is configured to store the acquired root request of the cloud mobile phone into a message queue; a request extracting unit 602 configured to control a preset execution service to extract a root request to be processed from a message queue; a root execution unit 603 configured to control the execution service to perform root on the target cloud handset corresponding to the root request to be processed.
In this embodiment, in the cloud mobile phone root authority obtaining apparatus 600: the detailed processing of the request storing unit 601, the request retrieving unit 602, and the root executing unit 603 and the technical effects thereof can refer to the related descriptions of step 201 and step 203 in the corresponding embodiment of fig. 2, which are not described herein again.
In some optional implementations of this embodiment, in response to the execution service having parallel processing capability, the request fetching unit 602 may include:
and the maximum parallel number taking-out subunit is configured to control a preset execution service to take out the number of the root requests to be processed, which is the maximum parallel processing number, from the message queue.
In some optional implementation manners of this embodiment, the cloud mobile phone root authority obtaining apparatus 600 may further include:
a first adjusting unit configured to adjust a maximum parallel processing number according to a network communication quality with an execution service;
or
And a second adjusting unit configured to adjust the maximum parallel processing number according to the remaining load amount of the server where the execution service is located.
In some optional implementation manners of this embodiment, in response to that the batch root requests to be processed whose number exceeds the maximum parallel processing number are continuously stored in the message queue, the cloud cell root authority obtaining apparatus 600 may further include:
the batch instruction conversion unit is configured to control the message queue to convert the batch root requests into a single batch processing instruction;
correspondingly, the maximum parallel number fetching subunit may be further configured to:
controlling a preset execution service to take out a batch processing instruction from a message queue;
correspondingly, the root execution unit 603 may be further configured to:
the control execution service analyzes a processing object set corresponding to the batch processing instruction;
the control execution service performs root on each processing object in the processing object set.
In some optional implementations of this embodiment, the execution service includes an integrated management service, a root management service, and a root execution service, and the request fetching unit 602 may be further configured to:
controlling the comprehensive management service to monitor the message change condition of the message queue;
responding to the message change condition as a newly increased request, and controlling the comprehensive management service to take out the newly increased root request to be processed from the message queue;
correspondingly, the root execution unit 603 may be further configured to:
responding to the root request to be processed belonging to the root operation request, and controlling the comprehensive management service to issue the newly increased root request to the root management service;
controlling the root management service to determine a target cloud mobile phone corresponding to the newly added root request;
the root management service is controlled to issue a root request to a root execution service arranged on the target cloud mobile phone;
and controlling the root execution service to perform root on the cloud mobile phone.
In some optional implementations of this embodiment, the root execution unit 603 may be further configured to:
controlling an execution service to inquire the authority obtaining state of the target cloud mobile phone corresponding to the root request to be processed;
and responding to the condition that the permission obtaining state is not root, and controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
In some optional implementation manners of this embodiment, the cloud mobile phone root authority obtaining apparatus 600 may further include:
an execution result receiving unit configured to receive an execution result of the root operation returned by the execution service;
the authority state table adjusting unit is configured to adjust root state information of the corresponding cloud mobile phone in a preset authority state table according to an execution result;
and the feedback information sending unit is configured to send feedback information to a sending end of the cloud mobile phone root request according to the adjusted authority state table.
The cloud mobile phone root device provided by the embodiment is used as an embodiment of the device corresponding to the method embodiment, the cloud mobile phone root device provided by the embodiment realizes full-automatic root processing on the cloud mobile phone through the provided message queue and the execution service, namely, the message is forwarded between the user side and the cloud mobile phone resource providing side by means of the message queue, the execution service deployed at the cloud mobile phone resource providing side can execute the cloud mobile phone root request taken out from the message queue, and further, the cloud mobile phone root request is automatically processed through the matching of the message queue and the execution service, the precious cloud mobile phone root request does not need to be manually intervened by a manager, the waste of labor force is avoided in monotonous repeated work, the root operation efficiency is improved, and the probability of operation errors is reduced.
According to an embodiment of the present disclosure, the present disclosure also provides an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; the storage stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can implement the cloud mobile phone root authority obtaining method described in any of the above embodiments when executing the instructions.
According to an embodiment of the present disclosure, a readable storage medium is further provided, where the readable storage medium stores computer instructions, and the computer instructions are configured to, when executed by a computer, enable the cloud mobile phone root authority obtaining method described in any of the above embodiments to be implemented.
The embodiment of the present disclosure provides a computer program product, which when executed by a processor, can implement the method for acquiring the root authority of the cloud mobile phone described in any of the above embodiments.
FIG. 7 illustrates a schematic block diagram of an example electronic device 700 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 7, the device 700 comprises a computing unit 701, which may perform various suitable actions and processes according to a computer program stored in a Read Only Memory (ROM)702 or a computer program loaded from a storage unit 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the device 700 can also be stored. The computing unit 701, the ROM 702, and the RAM 703 are connected to each other by a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
Various components in the device 700 are connected to the I/O interface 705, including: an input unit 706 such as a keyboard, a mouse, or the like; an output unit 707 such as various types of displays, speakers, and the like; a storage unit 708 such as a magnetic disk, optical disk, or the like; and a communication unit 709 such as a network card, modem, wireless communication transceiver, etc. The communication unit 709 allows the device 700 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The Server may be a cloud Server, which is also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in the conventional physical host and Virtual Private Server (VPS) service.
According to the technical scheme of the embodiment of the disclosure, the full-automatic processing of the root of the cloud mobile phone is realized through the provided message queue and the execution service, namely, the message is forwarded between the user side and the cloud mobile phone resource providing side by means of the message queue, the execution service deployed at the cloud mobile phone resource providing side can execute the cloud mobile phone root request taken out from the message queue, and further, the automatic processing of the cloud mobile phone root request is realized through the matching of the message queue and the execution service, manual intervention by a manager is not needed, the waste of precious labor force in monotonous repeated work is avoided, meanwhile, the efficiency of the root operation is improved, and the probability of operation errors is reduced.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, and the present disclosure is not limited herein.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.
Claims (17)
1. A cloud mobile phone root authority obtaining method comprises the following steps:
storing the obtained root request of the cloud mobile phone into a message queue;
controlling a preset execution service to take out a root request to be processed from the message queue;
and controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
2. The method of claim 1, wherein in response to the execution service having parallel processing capabilities, the controlling the pre-provisioned execution service to fetch a pending root request from the message queue comprises:
and controlling a preset execution service to take out the root requests to be processed with the maximum parallel processing number from the message queue.
3. The method of claim 2, further comprising:
adjusting the maximum parallel processing number according to the network communication quality between the execution service and the maximum parallel processing number;
or
And adjusting the maximum parallel processing number according to the residual load of the server where the execution service is located.
4. The method of claim 2, wherein in response to a number of pending batch root requests continuously stored in the message queue exceeding the maximum number of parallel processes, further comprising:
controlling the message queue to convert the batch root requests into a single batch processing instruction;
the method for controlling the preset execution service to take out the root requests to be processed with the maximum parallel processing number from the message queue comprises the following steps:
controlling a preset execution service to take out the batch processing instruction from the message queue;
the controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed includes:
controlling the execution service to analyze a processing object set corresponding to the batch processing instruction;
and controlling the execution service to respectively perform root on each processing object in the processing object set.
5. The method of claim 1, wherein the executive services comprise an integrated management service, a root management service, and a root executive service, and the controlling the preset executive service to fetch the root requests to be processed from the message queue comprises:
controlling the comprehensive management service to monitor the message change condition of the message queue;
responding to the message change condition as a new request, and controlling the comprehensive management service to take out the new root request to be processed from the message queue;
the controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed includes:
responding to the root request to be processed belonging to the root operation request, and controlling the comprehensive management service to issue a new root request to the root management service;
controlling the root management service to determine a target cloud mobile phone corresponding to the newly added root request;
controlling the root management service to issue the new root request to a root execution service arranged on the target cloud mobile phone;
and controlling the root execution service to perform root on the cloud mobile phone.
6. The method of claim 1, wherein the controlling the executive service to root a target cloud handset corresponding to the to-be-processed root request comprises:
controlling the execution service to inquire the authority obtaining state of the target cloud mobile phone corresponding to the root request to be processed;
and in response to the permission obtaining state being no root, controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
7. The method of any of claims 1-6, further comprising:
receiving an execution result of the root operation returned by the execution service;
adjusting root state information of the corresponding cloud mobile phone in a preset authority state table according to the execution result;
and sending feedback information to the sending end of the cloud mobile phone root request according to the adjusted authority state table.
8. A cloud mobile phone root authority acquisition device comprises:
the request storing unit is configured to store the acquired root request of the cloud mobile phone into a message queue;
the request taking-out unit is configured to control a preset execution service to take out the root request to be processed from the message queue;
and the root execution unit is configured to control the execution service to perform root on the target cloud mobile phone corresponding to the to-be-processed root request.
9. The apparatus of claim 8, wherein in response to the execution service having parallel processing capabilities, the request fetch unit comprises:
and the maximum parallel number taking-out subunit is configured to control a preset execution service to take out the number of the root requests to be processed, which is the maximum parallel processing number, from the message queue.
10. The apparatus of claim 9, further comprising:
a first adjusting unit configured to adjust the maximum parallel processing number according to a network communication quality with the execution service;
or
A second adjusting unit configured to adjust the maximum parallel processing number according to a remaining load amount of a server where the execution service is located.
11. The apparatus of claim 9, wherein in response to a number of pending batch root requests continuously stored in the message queue exceeding the maximum number of parallel processes, further comprising:
a batch instruction conversion unit configured to control the message queue to convert the batch root request into a single batch processing instruction;
the maximum parallel number fetch subunit is further configured to:
controlling a preset execution service to take out the batch processing instruction from the message queue;
the root execution unit is further configured to:
controlling the execution service to analyze a processing object set corresponding to the batch processing instruction;
and controlling the execution service to respectively perform root on each processing object in the processing object set.
12. The apparatus of claim 8, wherein the execution service comprises an integrated management service, a root execution service, the request fetch unit is further configured to:
controlling the comprehensive management service to monitor the message change condition of the message queue;
responding to the message change condition as a new request, and controlling the comprehensive management service to take out the new root request to be processed from the message queue;
the root execution unit is further configured to:
responding to the root request to be processed belonging to the root operation request, and controlling the comprehensive management service to issue a new root request to the root management service;
controlling the root management service to determine a target cloud mobile phone corresponding to the newly added root request;
controlling the root management service to issue the new root request to a root execution service arranged on the target cloud mobile phone;
and controlling the root execution service to perform root on the cloud mobile phone.
13. The apparatus of claim 8, wherein the root execution unit is further configured to:
controlling the execution service to inquire the authority obtaining state of the target cloud mobile phone corresponding to the root request to be processed;
and in response to the permission obtaining state being no root, controlling the execution service to perform root on the target cloud mobile phone corresponding to the root request to be processed.
14. The apparatus of any of claims 8-13, further comprising:
an execution result receiving unit configured to receive an execution result of the root operation returned by the execution service;
the authority state table adjusting unit is configured to adjust root state information of the corresponding cloud mobile phone in a preset authority state table according to the execution result;
and the feedback information sending unit is configured to send feedback information to the sending end of the cloud mobile phone root request according to the adjusted authority state table.
15. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the cloud cell phone root rights acquisition method of any of claims 1-7.
16. A non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the cloud cell root authority acquisition method of any one of claims 1-7.
17. A computer program product comprising a computer program which, when executed by a processor, implements the cloud cell root rights acquisition method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110812432.2A CN113419880B (en) | 2021-07-19 | 2021-07-19 | Cloud mobile phone root authority acquisition method, related device and computer program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110812432.2A CN113419880B (en) | 2021-07-19 | 2021-07-19 | Cloud mobile phone root authority acquisition method, related device and computer program product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113419880A true CN113419880A (en) | 2021-09-21 |
| CN113419880B CN113419880B (en) | 2024-04-09 |
Family
ID=77721279
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110812432.2A Active CN113419880B (en) | 2021-07-19 | 2021-07-19 | Cloud mobile phone root authority acquisition method, related device and computer program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113419880B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115793575A (en) * | 2022-10-27 | 2023-03-14 | 东莞市新佰人机器人科技有限责任公司 | Business mode of robot dispatch |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103747433A (en) * | 2013-12-02 | 2014-04-23 | 上海斐讯数据通信技术有限公司 | Method and mobile terminal for realizing root request management through manufacturer server |
| KR20170072552A (en) * | 2015-12-17 | 2017-06-27 | 에스케이텔레콤 주식회사 | Method and apparatus for servicing container in cloud development |
| KR20180058158A (en) * | 2016-11-23 | 2018-05-31 | 숭실대학교산학협력단 | Method for detecting rooting apps in google play store, recording medium, cloud server and system for performing the method |
| CN111600753A (en) * | 2020-05-13 | 2020-08-28 | 山东汇贸电子口岸有限公司 | Intelligent agent management system in cloud computing environment |
| CN113127203A (en) * | 2021-04-25 | 2021-07-16 | 华南理工大学 | Deep learning distributed compiler for cloud edge computing and construction method |
-
2021
- 2021-07-19 CN CN202110812432.2A patent/CN113419880B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103747433A (en) * | 2013-12-02 | 2014-04-23 | 上海斐讯数据通信技术有限公司 | Method and mobile terminal for realizing root request management through manufacturer server |
| KR20170072552A (en) * | 2015-12-17 | 2017-06-27 | 에스케이텔레콤 주식회사 | Method and apparatus for servicing container in cloud development |
| KR20180058158A (en) * | 2016-11-23 | 2018-05-31 | 숭실대학교산학협력단 | Method for detecting rooting apps in google play store, recording medium, cloud server and system for performing the method |
| CN111600753A (en) * | 2020-05-13 | 2020-08-28 | 山东汇贸电子口岸有限公司 | Intelligent agent management system in cloud computing environment |
| CN113127203A (en) * | 2021-04-25 | 2021-07-16 | 华南理工大学 | Deep learning distributed compiler for cloud edge computing and construction method |
Non-Patent Citations (2)
| Title |
|---|
| 孙海滨;张敬超;: "基于MQTT协议的跨平台工业级物联网消息传输系统实现与设计", 软件, no. 08 * |
| 林闯;苏文博;孟坤;刘渠;刘卫东;: "云计算安全:架构、机制与模型评价", 计算机学报, no. 09 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115793575A (en) * | 2022-10-27 | 2023-03-14 | 东莞市新佰人机器人科技有限责任公司 | Business mode of robot dispatch |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113419880B (en) | 2024-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10417062B2 (en) | Method and apparatus of unloading out of memory processing flow to user space | |
| CN112911013B (en) | Cloud application processing method and device, computer equipment and storage medium | |
| CN113766487B (en) | Cloud mobile phone information acquisition method, device, equipment and medium | |
| CN113795039A (en) | Operator network switching method, device, equipment and computer readable storage medium | |
| CN114025037B (en) | Cloud mobile phone overhaul method and device, electronic equipment and storage medium | |
| CN113419880A (en) | Cloud mobile phone root authority acquisition method, related device and computer program product | |
| CN113608765A (en) | Data processing method, device, equipment and storage medium | |
| CN113609027A (en) | ARM cloud server testing method and device, electronic equipment and storage medium | |
| CN116661960A (en) | Batch task processing method, device, equipment and storage medium | |
| CN113420275B (en) | Data connection processing method, related device and computer program product | |
| CN115514718A (en) | Data interaction method, control layer and equipment based on data transmission system | |
| CN113641688B (en) | Node updating method, related device and computer program product | |
| CN115543416A (en) | Configuration updating method and device, electronic equipment and storage medium | |
| CN114283808A (en) | Multi-path outbound system, method, apparatus, medium, and product | |
| CN112925623A (en) | Task processing method and device, electronic equipment and medium | |
| CN114070889A (en) | Configuration method, traffic forwarding method, device, storage medium, and program product | |
| CN113641388A (en) | Cloud mobile phone updating method, related device and computer program product | |
| CN113419865A (en) | Cloud resource processing method, related device and computer program product | |
| CN112714420A (en) | Network access method and device of wifi hotspot providing equipment and electronic equipment | |
| CN112306371A (en) | Method, apparatus and computer program product for storage management | |
| CN114006902B (en) | Cloud mobile phone restarting method, device, equipment and storage medium | |
| CN113726883B (en) | Cloud data processing method, related device and computer program product | |
| CN115061817A (en) | Operation and maintenance method, device, system and computer program product | |
| CN114286343B (en) | Multi-way outbound system, risk identification method, equipment, medium and product | |
| CN114095758B (en) | Cloud image intercepting method and related 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |