CN114006902A - Cloud mobile phone restarting method, device, equipment and storage medium - Google Patents
Cloud mobile phone restarting method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114006902A CN114006902A CN202111257772.XA CN202111257772A CN114006902A CN 114006902 A CN114006902 A CN 114006902A CN 202111257772 A CN202111257772 A CN 202111257772A CN 114006902 A CN114006902 A CN 114006902A
- Authority
- CN
- China
- Prior art keywords
- mobile phone
- cloud mobile
- restart
- restarting
- target cloud
- 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 53
- 238000004590 computer program Methods 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 10
- 230000010365 information processing Effects 0.000 claims 1
- 238000005516 engineering process Methods 0.000 description 19
- 238000004891 communication Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000013473 artificial intelligence Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000010801 machine learning Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000903 blocking effect 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
- 238000013135 deep learning Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003924 mental process Effects 0.000 description 1
- 238000003058 natural language processing Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011160 research Methods 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
- 238000012549 training Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
- H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephone Function (AREA)
Abstract
The disclosure provides a cloud mobile phone restarting method, device, equipment and storage medium, and relates to the technical field of cloud computing, in particular to the technical field of cloud mobile phones. The specific implementation scheme is as follows: responding to a cloud mobile phone restarting request, and determining whether a target cloud mobile phone to be restarted meets a deep restarting condition; and if so, sending a restart instruction to the physical machine to which the target cloud mobile phone belongs so as to enable the physical machine to execute restart operation. According to the scheme, when the cloud mobile phone meets the deep restart condition, the physical machine to which the cloud mobile phone belongs is restarted, and compared with the restarting of the cloud mobile phone, the smoothness of cloud mobile phone control is better improved.
Description
Technical Field
The present disclosure relates to the field of cloud computing technologies, and in particular, to a cloud mobile phone restarting method, apparatus, device, and storage medium.
Background
With the development of cloud computing technology, cloud mobile phone (i.e., Cloudphone) technology is gradually emerging, and a cloud mobile phone applies the cloud computing technology to network terminal services and realizes cloud services through a cloud server. With the increase of the operation duration of the cloud mobile phone, how to ensure the smoothness of the operation of the cloud mobile phone is important.
Disclosure of Invention
The disclosure provides a method, a device, equipment and a storage medium for restarting a cloud mobile phone.
According to an aspect of the present disclosure, a cloud mobile phone restarting method is provided, which includes:
responding to a cloud mobile phone restarting request, and determining whether a target cloud mobile phone to be restarted meets a deep restarting condition;
and if so, sending a restart instruction to the physical machine to which the target cloud mobile phone belongs so as to enable the physical machine to execute restart operation.
According to another aspect of the present disclosure, there is provided an electronic device including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the cloud handset restart method provided by the present disclosure.
According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the cloud handset restart method provided by the present disclosure.
According to the technology disclosed by the invention, when the cloud mobile phone meets the deep restart condition, the physical machine to which the cloud mobile phone belongs can be restarted, and compared with the restarting of the cloud mobile phone, the smoothness of cloud mobile phone control is better improved.
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
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
fig. 1 is a flowchart of a cloud handset restart method according to an embodiment of the present disclosure;
fig. 2 is a flow chart of another cloud handset restart method according to an embodiment of the present disclosure;
fig. 3 is a flowchart of yet another cloud-phone reboot method according to an embodiment of the present disclosure;
fig. 4A is a flowchart of yet another cloud-enabled handset rebooting method, according to an embodiment of the present disclosure;
fig. 4B is a schematic diagram of a cloud handset restart method according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a cloud mobile phone restarting device according to an embodiment of the present disclosure;
fig. 6 is a block diagram of an electronic device for implementing a cloud handset restart 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.
With the development of cloud computing technology, cloud mobile phone (i.e., Cloudphone) technology is gradually emerging, and a cloud mobile phone applies the cloud computing technology to network terminal services and realizes cloud services through a cloud server. At present, a physical machine virtualizes a plurality of cloud mobile phones according to hardware information and performance of the physical machine. The user can install different applications to the cloud mobile phone in the process of using the virtual cloud mobile phone, and the cloud mobile phone occupies a Central Processing Unit (CPU) of a physical machine and an operating memory along with the increase of the operation duration of the cloud mobile phone, so that the phenomenon of blocking of the cloud mobile phone due to the fact that much cache rubbish and dirty data exist is caused. The embodiment provides a scheme for effectively relieving the cloud mobile phone stuck phenomenon.
Fig. 1 is a flowchart of a cloud mobile phone restarting method according to an embodiment of the present disclosure, which is applicable to a case of restarting a cloud mobile phone. The method can be executed by a cloud mobile phone restarting device, the device can be realized by software and/or hardware, and the device can be integrated in electronic equipment bearing a cloud mobile phone restarting function, such as a cloud server.
As shown in fig. 1, the method may specifically include:
s101, responding to a cloud mobile phone restarting request, and determining whether a target cloud mobile phone to be restarted meets a deep restarting condition.
In this embodiment, the cloud mobile phone restart request is a request for instructing the cloud mobile phone to restart. The target cloud mobile phone to be restarted is the cloud mobile phone which needs to be restarted. The cloud mobile phone refers to a mobile phone in which a cloud computing technology is applied to network terminal services, and cloud services are realized through a cloud service terminal, and can also be understood as a mobile phone virtualized in a physical machine in a software manner. The physical machine is a name for a physical computer as compared with a virtual machine (cloud handset), and the physical machine provides a hardware environment for the virtual handset (cloud handset). It should be noted that at least one cloud mobile phone may be deployed on one physical machine. The deep restart condition is a condition for instructing a physical machine to which the cloud mobile phone belongs to perform deep restart.
In this embodiment, in response to a cloud mobile phone restart request, the essence of determining whether a target cloud mobile phone to be restarted meets a deep restart condition is to determine whether a physical machine to which the target cloud mobile phone belongs is restarted and normal operation of a process or software in the physical machine is affected. Optionally, one implementation manner is: and judging whether other software or processes are operated on the physical machine to which the target cloud mobile phone to be restarted belongs, and if not, determining that the target cloud mobile phone to be restarted meets the deep restarting condition. The other realization mode is as follows: and judging whether important data are cached in the physical machine to which the target cloud mobile phone to be restarted belongs, and if not, determining that the target cloud mobile phone to be restarted meets the deep restarting condition. The determination may also be made based on the deployment situation of other cloud handsets in the physical machine, which is not limited in this embodiment.
And S102, if yes, sending a restart instruction to a physical machine to which the target cloud mobile phone belongs so that the physical machine executes restart operation.
In this embodiment, if the deep restart condition is met, the cloud server may generate an instruction for instructing the physical machine to restart, and then send the restart instruction to the physical machine to which the target cloud mobile phone belongs, so that the physical machine responds to the restart instruction to execute a restart operation.
Optionally, the restart instruction may be that the cloud service generates a restart message according to an identifier of a device to be restarted (such as a physical machine) and a restart parameter, further analyzes the restart message, determines a type of the restart device (such as a physical machine type), and generates a restart instruction corresponding to the type. The restart parameter refers to a parameter required by restarting the device. The restart instruction may also be a locally stored instruction, in which case the restart instruction is called directly from the local.
According to the technical scheme provided by the embodiment of the disclosure, whether a target cloud mobile phone to be restarted meets a deep restarting condition is determined by responding to a cloud mobile phone restarting request, and if yes, a restarting instruction is sent to a physical machine to which the target cloud mobile phone belongs, so that the physical machine executes restarting operation. According to the technical scheme, when the cloud mobile phone meets the deep restart condition, the physical machine to which the cloud mobile phone belongs is restarted, and compared with the direct restart of the cloud mobile phone, the occupied data and dirty data of the internal memory in the physical machine are effectively eliminated, the phenomenon that the cloud mobile phone is stuck or crashed is relieved, and the control smoothness of the cloud mobile phone is better improved.
On the basis of the above embodiment, as an optional mode of the present disclosure, it is determined that the cloud mobile phone restart request may be a cloud mobile phone restart request sent by a client of a target cloud mobile phone; and/or generating a cloud mobile phone restarting request of the target cloud mobile phone when the current moment is detected to reach the target cloud mobile phone restarting period.
Optionally, it is determined that the cloud mobile phone restart request may be a cloud mobile phone restart request sent by a client of a target cloud mobile phone received by a cloud server. Specifically, when the client of the target cloud mobile phone detects that the cloud mobile phone is stuck or crashed, the client of the target cloud mobile phone sends a cloud mobile phone restart request to the cloud server; correspondingly, the cloud server receives a cloud mobile phone restart request. The cloud mobile phone restart method can also be used for manually triggering a corresponding control at a client of the target cloud mobile phone by a user so as to instruct the cloud mobile phone to send a cloud mobile phone restart request to the cloud server.
Optionally, it is determined that the cloud mobile phone restart request may be a cloud mobile phone restart request generated when it is detected that the current time reaches the restart period of the target cloud mobile phone. The restarting period refers to a time period for restarting the cloud mobile phone; the restart period may be set by a person skilled in the art according to practical circumstances. Specifically, the cloud server side detects that a time period between the current time and the last time when the target cloud mobile phone is restarted reaches a restart period of the target cloud mobile phone, and then generates a cloud mobile phone restart request of the target cloud mobile phone.
Optionally, it is determined that the cloud mobile phone restart request may be a cloud mobile phone restart request sent by a client of a target cloud mobile phone; and generating a cloud mobile phone restarting request of the target cloud mobile phone when detecting that the current time reaches the restarting period of the target cloud mobile phone.
The cloud mobile phone restarting request is sent by the client or generated at regular time, so that the determined diversity and flexibility of the cloud mobile phone restarting request are improved, and the cloud mobile phone can be well ensured to be in a relatively smooth state.
Fig. 2 is a flowchart of another cloud phone restarting method according to an embodiment of the present disclosure, and on the basis of the above embodiment, an optional implementation scheme is provided for further optimizing "determining whether a target cloud phone to be restarted satisfies a deep restart condition".
As shown in fig. 2, the method may specifically include:
s201, responding to a cloud mobile phone restarting request, and determining a physical machine to which a target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine according to a deployment relationship between the cloud mobile phone and the physical machine and a binding relationship between the cloud mobile phone and a user.
In this embodiment, the deployment relationship refers to a relationship between the cloud mobile phones and the physical machines, that is, which cloud mobile phone is deployed on which physical machine; optionally, the deployment relationship may be stored locally at the cloud server, and further, the deployment relationship may also be stored in a physical machine deployed by the cloud mobile phone, and the cloud server interacts with the physical machine and is acquired from the physical machine.
In this embodiment, the binding relationship refers to a relationship between the cloud mobile phones and the users, that is, which cloud mobile phone is used by which user; the optional binding relationship can be stored locally at the cloud server, further, the binding relationship can be stored in a physical machine deployed in the cloud mobile phone, and the cloud server interacts with the physical machine and is acquired from the physical machine.
In this embodiment, the available cloud mobile phone refers to a cloud mobile phone that is deployed on a physical machine and is available for at least one user to use. Further, the available cloud handsets include at least a target cloud handset. Namely, at least one cloud mobile phone, namely a target cloud mobile phone, is deployed in the physical machine. When a plurality of cloud mobile phones are deployed in the physical machine, at least a target cloud mobile phone is bound with a user.
In this embodiment, the user binding information set refers to a set of user information of at least one available cloud mobile phone deployed on a physical machine. That is, for each available cloud mobile phone, if the user is bound, the user binding information set includes the user binding information of the user.
In this embodiment, the cloud server, in response to the cloud mobile phone restart request, determines the physical machine to which the target cloud mobile phone to be restarted belongs according to the deployment relationship between the cloud mobile phone and the physical machine, and determines the user binding information set of the available cloud mobile phone deployed on the physical machine according to the binding relationship between the cloud mobile phone and the user.
S202, determining whether the target cloud mobile phone meets deep restart conditions or not according to the user binding information set.
For example, if only one available cloud mobile phone is provided, that is, only the target cloud mobile phone is deployed in the physical machine, at this time, it may be directly determined that the target cloud mobile phone meets the deep restart condition.
For example, if there are a plurality of available cloud mobile phones, that is, the target cloud mobile phone and other cloud mobile phones are deployed in the physical machine, it is determined that the target cloud mobile phone meets the deep restart condition if the user binding information set only includes the user binding information of the target cloud mobile phone.
And S203, if so, sending a restart instruction to the physical machine to which the target cloud mobile phone belongs so that the physical machine executes restart operation.
According to the technical scheme of the embodiment, a physical machine to which a target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine are determined according to a deployment relationship between the cloud mobile phone and the physical machine and a binding relationship between the cloud mobile phone and a user in response to a cloud mobile phone restarting request; the available cloud mobile phones at least comprise a target cloud mobile phone, whether the target cloud mobile phone meets a deep restarting condition is determined according to the user binding information set, and if yes, a restarting instruction is sent to a physical machine to which the target cloud mobile phone belongs, so that the physical machine executes restarting operation. According to the technical scheme, the physical machine to which the target cloud mobile phone belongs is restarted under the condition that only the target cloud mobile phone is bound with the user in the physical machine, so that the loss of user data of other cloud mobile phones in the physical machine due to the restart of the physical machine is avoided, the smoothness of the target cloud mobile phone is improved, and meanwhile, the data safety of other cloud mobile phones is guaranteed.
On the basis of the foregoing embodiment, as an optional manner of the present disclosure, it may be determined that the target cloud mobile phone meets the deep restart condition, or if the user binding information set only includes the user binding information of the target cloud mobile phone, it may be determined that the target cloud mobile phone meets the deep restart condition, if the user binding information set only includes the user binding information of the target cloud mobile phone, and the physical machine has not been restarted within a preset time period, it is determined that the target cloud mobile phone meets the deep restart condition.
Specifically, if the user information set only contains user binding information of the target cloud mobile phone, and if the physical machine is identified not to be restarted within a preset time period, it is determined that the target cloud mobile phone meets the deep restart condition. The preset time period can be set by a person skilled in the art according to actual conditions.
It can be understood that the frequent restart of the physical machine can be effectively avoided by introducing the deep restart condition that the set time period is not restarted.
Fig. 3 is a flowchart of another cloud mobile phone restart method according to an embodiment of the present disclosure, and on the basis of the above embodiment, an optional implementation is provided for further optimizing "determining whether a target cloud mobile phone meets a deep restart condition according to a user binding information set".
As shown in fig. 3, the method may specifically include:
s301, responding to a cloud mobile phone restarting request, and determining a physical machine to which a target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine according to a deployment relationship between the cloud mobile phone and the physical machine and a binding relationship between the cloud mobile phone and a user; the available cloud handsets include at least a target cloud handset.
And S302, if the user binding information of other cloud mobile phones except the target cloud mobile phone in the available cloud mobile phones exists in the user binding information set, determining whether the target cloud mobile phone meets the deep restart condition or not according to historical login information of other cloud mobile phones.
In this embodiment, the historical login information refers to the login situation before the current time, and may be obtained locally at the cloud server, or may be obtained from a physical machine through physical machine interaction.
One possible implementation manner of this embodiment is: if the user binding information of other cloud mobile phones except the target cloud mobile phone in the available cloud mobile phones exists in the user binding information set, but the other cloud mobile phones do not log in within a certain time, it is determined that the target cloud mobile phone meets the deep restart condition.
Another possible implementation manner of this embodiment is: if the user binding information of other cloud mobile phones except for the target cloud mobile phone in the available cloud mobile phones exists in the user binding information set, whether other users (users bound by non-target cloud mobile phones) bound by other cloud mobile phones (other cloud mobile phones deployed on the physical machine to which the target cloud mobile phone belongs) bind cloud mobile phones on other physical machines (physical machines to which the non-target cloud mobile phones belong) is determined, and if yes, whether the target cloud mobile phones meet the deep restart condition is determined according to the frequency of the other users (users bound by the non-target cloud mobile phones) using the cloud mobile phones on the other physical machines (physical machines to which the non-target cloud mobile phones belong) and the other cloud mobile phones (other cloud mobile phones deployed on the physical machine to which the target cloud mobile phones belong). For example, if the frequency of using the cloud mobile phone on the other physical machine (the physical machine to which the non-target cloud mobile phone belongs) by the other user (the user to which the non-target cloud mobile phone is bound) is much higher than that of using the other cloud mobile phone (the other cloud mobile phone deployed on the physical machine to which the target cloud mobile phone belongs), it is determined that the target cloud mobile phone meets the deep restart condition.
And S303, if so, sending a restart instruction to the physical machine to which the target cloud mobile phone belongs so as to enable the physical machine to execute a restart operation.
According to the technical scheme of the embodiment, a physical machine to which a target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine are determined according to a deployment relationship between the cloud mobile phone and the physical machine and a binding relationship between the cloud mobile phone and a user in response to a cloud mobile phone restarting request; the available cloud mobile phones at least comprise target cloud mobile phones, and further, if the user binding information of other cloud mobile phones except the target cloud mobile phones in the available cloud mobile phones is concentrated in the user binding information, whether the target cloud mobile phones meet deep restart conditions is determined according to historical login information of the other cloud mobile phones. According to the technical scheme, the historical login information of other cloud mobile phones is combined, so that occupied memory data and dirty data in the physical machine are deleted on the premise of avoiding deleting important data in other cloud mobile phones, occupied memory is released, the dirty data are cleared, and the phenomenon of cloud mobile phone blockage is greatly avoided.
Fig. 4A is a flowchart of another cloud mobile phone restarting method according to an embodiment of the present disclosure, which is further optimized and provides an optional preferred scheme based on the above embodiment.
As shown in fig. 4A, the method may specifically include:
s401, a cloud mobile phone restarting request is obtained.
S402, responding to the cloud mobile phone restarting request, and determining whether a target cloud mobile phone to be restarted meets a deep restarting condition. If yes, S403 is executed, and if no, S404 is executed.
And S403, if yes, sending a restart instruction to the physical machine to which the target cloud mobile phone belongs so that the physical machine executes restart operation.
And S404, if the target cloud mobile phone is not satisfied, sending a restart instruction to the target cloud mobile phone so that the target cloud mobile phone executes a restart operation.
In the embodiment, if the deep restart condition is not met, the cloud server sends a restart instruction to the target cloud mobile phone; correspondingly, the target cloud mobile phone executes restarting operation.
A specific example is provided in the present disclosure, and fig. 4B is a schematic diagram of a cloud handset restart method according to an embodiment of the present disclosure. The embodiment provides the preferable examples of the method for realizing the cloud mobile phone restart through the interaction of the user client, the cloud server and the cloud mobile phone or the physical machine.
The interface service, the timing service, the message queue and the management service belong to sub-services in the cloud service side.
For example, as shown in fig. 4B, if the user client initiates a restart request to the interface service; correspondingly, the interface service responds to the restart request, performs service logic judgment (namely, judges whether a target cloud mobile phone to be restarted meets a deep restart condition), generates a restart message according to a judgment result, and sends the restart message to the message queue. The management service (manager-server) acquires and analyzes the restart message from the message queue, specifically, the management service analyzes the restart message, judges whether the cloud mobile phone (virtual cloud mobile phone) is restarted or the physical machine (physical machine to which the cloud mobile phone belongs) is restarted, and further generates a restart instruction corresponding to the physical machine or the cloud mobile phone. And sending the corresponding restart instruction to the cloud mobile phone or the physical machine so as to enable the cloud mobile phone or the physical machine to execute the restart operation.
For example, as shown in fig. 4B, if the user client sets a restart task to the interface service; correspondingly, the interface service stores the task information according to the task parameters in the set restart task. The task information may include a cloud mobile phone identifier corresponding to the user client, a restart period corresponding to the cloud mobile phone identifier, and the like; the timing service scans the restart task at regular time, performs service logic judgment according to the task information, generates a restart message, and sends the restart message to a message queue. And the management service (manager-server) acquires and analyzes the restart message from the message queue, judges whether the cloud mobile phone (virtual cloud mobile phone) is restarted or the physical machine (physical machine to which the cloud mobile phone belongs) is restarted, and further generates a restart instruction corresponding to the physical machine or the cloud mobile phone. And sending the corresponding restart instruction to the cloud mobile phone or the physical machine so as to enable the cloud mobile phone or the physical machine to execute the restart operation.
According to the technical scheme of the embodiment, whether a target cloud mobile phone to be restarted meets a deep restarting condition is determined by responding to a cloud mobile phone restarting request, and if yes, a restarting instruction is sent to a physical machine to which the target cloud mobile phone belongs, so that the physical machine executes restarting operation; and if not, sending a restart instruction to the target cloud mobile phone so that the target cloud mobile phone executes restart operation. According to the technical scheme, whether the physical machine is restarted or the cloud mobile phone is restarted can be determined according to the actual deployment condition of the physical machine to which the cloud mobile phone belongs, the memory occupation and dirty data in the physical machine can be more flexibly cleared, and the phenomenon that the cloud mobile phone is stuck or crashed is relieved.
Fig. 5 is a schematic structural diagram of a cloud mobile phone restart apparatus according to an embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a case of restarting a cloud mobile phone. The method can be executed by a cloud mobile phone restarting device, the device can be realized by software and/or hardware, and the device can be integrated in electronic equipment bearing a cloud mobile phone restarting function, such as a cloud server.
As shown in fig. 5, the cloud mobile phone restarting apparatus 500 may specifically include:
a restart condition determining module 501, configured to respond to a cloud cell phone restart request, and determine whether a target cloud cell phone to be restarted meets a deep restart condition;
and a restart instruction sending module 502, configured to send a restart instruction to a physical machine to which the target cloud mobile phone belongs if the physical machine meets the requirement, so that the physical machine executes a restart operation.
According to the technical scheme provided by the embodiment of the disclosure, whether a target cloud mobile phone to be restarted meets a deep restarting condition is determined by responding to a cloud mobile phone restarting request, and if yes, a restarting instruction is sent to a physical machine to which the target cloud mobile phone belongs, so that the physical machine executes restarting operation. According to the technical scheme, when the cloud mobile phone meets the deep restart condition, the physical machine to which the cloud mobile phone belongs is restarted, and compared with the direct restart of the cloud mobile phone, the occupied data and dirty data of the internal memory in the physical machine are effectively eliminated, the phenomenon that the cloud mobile phone is stuck or crashed is relieved, and the control smoothness of the cloud mobile phone is better improved.
Further, the restart condition determining module 501 includes:
the user information determining unit is used for determining a physical machine to which the target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine according to the deployment relationship between the cloud mobile phone and the physical machine and the binding relationship between the cloud mobile phone and the user; the available cloud mobile phones at least comprise target cloud mobile phones;
and the restarting condition determining unit is used for determining whether the target cloud mobile phone meets the deep restarting condition or not according to the user binding information set.
Further, the restart condition determining unit includes:
and the restarting condition determining subunit is used for determining that the target cloud mobile phone meets the deep restarting condition if the user binding information set only contains the user binding information of the target cloud mobile phone.
Further, the restart condition determining subunit is specifically configured to:
and if the user binding information set only contains the user binding information of the target cloud mobile phone and the physical machine is not restarted within a preset time period, determining that the target cloud mobile phone meets the deep restart condition.
Further, the restart condition determining unit includes:
the restarting condition determining subunit is further configured to determine whether the target cloud mobile phone meets the deep restarting condition according to historical login information of other cloud mobile phones if the user binding information of other cloud mobile phones than the target cloud mobile phone in the available cloud mobile phones exists in the user binding information set.
Further, the restart instruction sending module 502 is further configured to:
and if not, sending a restart instruction to the target cloud mobile phone so that the target cloud mobile phone executes restart operation.
Further, the apparatus further includes a restart request determining module, which is specifically configured to:
receiving a cloud mobile phone restarting request sent by a client of a target cloud mobile phone; and/or the presence of a gas in the gas,
and generating a cloud mobile phone restarting request of the target cloud mobile phone when the current moment is detected to reach the target cloud mobile phone restarting period.
The cloud mobile phone restarting device can execute the cloud mobile phone restarting method provided by any embodiment of the disclosure, and has the corresponding functional modules and beneficial effects of the execution method.
In the technical scheme of the disclosure, the acquisition, storage, application and the like of the related user information data and the like all accord with the regulations of related laws and regulations, and do not violate the good customs of the public order.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
FIG. 6 illustrates a schematic block diagram of an example electronic device 600 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 assistants, cellular telephones, 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. 6, the apparatus 600 includes a computing unit 601, which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM)602 or a computer program loaded from a storage unit 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the device 600 can also be stored. The calculation unit 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, a mouse, or the like; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The computing unit 601 performs the various methods and processes described above, such as a cloud handset restart method. For example, in some embodiments, the cloud handset reboot method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the cloud handset restart method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform the cloud handset restart method by any other suitable means (e.g., by means of firmware).
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), blockchain networks, 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 can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome. The server may also be a server of a distributed system, or a server incorporating a blockchain.
Artificial intelligence is the subject of research that makes computers simulate some human mental processes and intelligent behaviors (such as learning, reasoning, thinking, planning, etc.), both at the hardware level and at the software level. Artificial intelligence hardware technologies generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing, and the like; the artificial intelligence software technology mainly comprises a computer vision technology, a voice recognition technology, a natural language processing technology, a machine learning/deep learning technology, a big data processing technology, a knowledge map technology and the like.
Cloud computing (cloud computing) refers to a technology system that accesses a flexibly extensible shared physical or virtual resource pool through a network, where resources may include servers, operating systems, networks, software, applications, storage devices, and the like, and may be deployed and managed in a self-service manner as needed. Through the cloud computing technology, high-efficiency and strong data processing capacity can be provided for technical application and model training of artificial intelligence, block chains and the like.
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 or sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.
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 restarting method comprises the following steps:
responding to a cloud mobile phone restarting request, and determining whether a target cloud mobile phone to be restarted meets a deep restarting condition;
and if so, sending a restart instruction to the physical machine to which the target cloud mobile phone belongs so as to enable the physical machine to execute restart operation.
2. The method of claim 1, wherein the determining whether the target cloud handset to be restarted satisfies a deep restart condition comprises:
determining a physical machine to which a target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine according to a deployment relationship between the cloud mobile phone and the physical machine and a binding relationship between the cloud mobile phone and a user; the available cloud mobile phones at least comprise target cloud mobile phones;
and determining whether the target cloud mobile phone meets a deep restart condition or not according to the user binding information set.
3. The method of claim 2, wherein determining whether the target cloud handset meets a deep restart condition according to the user binding information set comprises:
and if the user binding information set only contains the user binding information of the target cloud mobile phone, determining that the target cloud mobile phone meets the deep restart condition.
4. The method of claim 3, wherein the determining that the target cloud mobile phone meets the deep restart condition if the set of user binding information only includes user binding information of the target cloud mobile phone comprises:
and if the user binding information set only contains the user binding information of the target cloud mobile phone and the physical machine is not restarted within a preset time period, determining that the target cloud mobile phone meets a deep restart condition.
5. The method of claim 2, wherein the determining whether the target cloud handset meets a deep restart condition according to the user binding information set comprises:
and if the user binding information of other cloud mobile phones except the target cloud mobile phone in the available cloud mobile phones exists in the user binding information set, determining whether the target cloud mobile phone meets a deep restart condition or not according to historical login information of the other cloud mobile phones.
6. The method of claim 1, further comprising:
and if not, sending a restart instruction to the target cloud mobile phone so as to enable the target cloud mobile phone to execute a restart operation.
7. The method of claim 1, further comprising:
receiving a cloud mobile phone restarting request sent by a client of the target cloud mobile phone; and/or the presence of a gas in the gas,
and generating a cloud mobile phone restarting request of the target cloud mobile phone when the current moment is detected to reach the target cloud mobile phone restarting period.
8. A cloud cell-phone restarts the device, includes:
the cloud mobile phone restarting request processing module is used for responding to a cloud mobile phone restarting request and determining whether a target cloud mobile phone to be restarted meets a deep restarting condition;
and the restarting instruction sending module is used for sending a restarting instruction to the physical machine to which the target cloud mobile phone belongs if the restarting instruction is met, so that the physical machine executes restarting operation.
9. The apparatus of claim 8, wherein the restart condition determination module comprises:
the system comprises a user information determining unit, a target cloud mobile phone restarting unit and a user information processing unit, wherein the user information determining unit is used for determining a physical machine to which the target cloud mobile phone to be restarted belongs and a user binding information set of an available cloud mobile phone deployed on the physical machine according to a deployment relationship between the cloud mobile phone and the physical machine and a binding relationship between the cloud mobile phone and a user; the available cloud mobile phones at least comprise target cloud mobile phones;
and the restarting condition determining unit is used for determining whether the target cloud mobile phone meets a deep restarting condition according to the user binding information set.
10. The apparatus of claim 9, wherein the restart condition determining unit comprises:
and the restarting condition determining subunit is used for determining that the target cloud mobile phone meets the deep restarting condition if the user binding information set only contains the user binding information of the target cloud mobile phone.
11. The apparatus of claim 10, wherein the restart condition determining subunit is specifically configured to:
and if the user binding information set only contains the user binding information of the target cloud mobile phone and the physical machine is not restarted within a preset time period, determining that the target cloud mobile phone meets a deep restart condition.
12. The apparatus of claim 9, wherein the restart condition determining unit comprises:
and the restarting condition determining subunit is further configured to determine whether the target cloud mobile phone meets a deep restarting condition according to historical login information of other cloud mobile phones if the user binding information of other cloud mobile phones except the target cloud mobile phone in the available cloud mobile phones is concentrated in the user binding information.
13. The apparatus of claim 8, the restart instruction sending module further configured to:
and if not, sending a restart instruction to the target cloud mobile phone so as to enable the target cloud mobile phone to execute a restart operation.
14. The apparatus of claim 8, further comprising a restart request determination module, the module specifically configured to:
receiving a cloud mobile phone restarting request sent by a client of the target cloud mobile phone; and/or the presence of a gas in the gas,
and generating a cloud mobile phone restarting request of the target cloud mobile phone when the current moment is detected to reach the target cloud mobile phone restarting period.
15. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the cloud handset restart method of any of claims 1-7.
16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the cloud handset restart method of any of claims 1-7.
17. A computer program product comprising a computer program which, when executed by a processor, implements a cloud handset restart method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111257772.XA CN114006902B (en) | 2021-10-27 | 2021-10-27 | Cloud mobile phone restarting method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111257772.XA CN114006902B (en) | 2021-10-27 | 2021-10-27 | Cloud mobile phone restarting method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114006902A true CN114006902A (en) | 2022-02-01 |
| CN114006902B CN114006902B (en) | 2023-08-11 |
Family
ID=79924359
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111257772.XA Active CN114006902B (en) | 2021-10-27 | 2021-10-27 | Cloud mobile phone restarting method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114006902B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120110313A1 (en) * | 2010-11-01 | 2012-05-03 | Red Hat Israel, Ltd. | Enhanced reboot command |
| CN104461757A (en) * | 2014-11-03 | 2015-03-25 | 中国联合网络通信集团有限公司 | Method and device for restoring virtual machines |
| US20170264768A1 (en) * | 2014-11-28 | 2017-09-14 | Katsumi Sayama | Information processing apparatus and restart executing method |
| CN107741877A (en) * | 2017-11-06 | 2018-02-27 | 湖南红手指信息技术有限公司 | A kind of method, storage medium and the processor of cloud handset starting virtual opetrating system |
| CN107943270A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Control method, device and the storage medium and mobile terminal of application service |
| CN109005245A (en) * | 2018-09-07 | 2018-12-14 | 广州微算互联信息技术有限公司 | The use management method and system of cloud mobile phone |
| CN109992343A (en) * | 2019-03-27 | 2019-07-09 | 上海达龙信息科技有限公司 | Control method, control system and the electronic equipment of virtual cloud desktop server |
| CN110502324A (en) * | 2019-07-31 | 2019-11-26 | 湖南微算互联信息技术有限公司 | The processing method, system and storage medium for restarting data of cloud mobile phone games |
| CN111143170A (en) * | 2019-12-31 | 2020-05-12 | 北京云派网络科技有限公司 | Cloud mobile phone monitoring system and method |
| CN113472956A (en) * | 2021-09-03 | 2021-10-01 | 北京健康之家科技有限公司 | Cloud mobile phone management method and device |
-
2021
- 2021-10-27 CN CN202111257772.XA patent/CN114006902B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120110313A1 (en) * | 2010-11-01 | 2012-05-03 | Red Hat Israel, Ltd. | Enhanced reboot command |
| CN104461757A (en) * | 2014-11-03 | 2015-03-25 | 中国联合网络通信集团有限公司 | Method and device for restoring virtual machines |
| US20170264768A1 (en) * | 2014-11-28 | 2017-09-14 | Katsumi Sayama | Information processing apparatus and restart executing method |
| CN107741877A (en) * | 2017-11-06 | 2018-02-27 | 湖南红手指信息技术有限公司 | A kind of method, storage medium and the processor of cloud handset starting virtual opetrating system |
| CN107943270A (en) * | 2017-11-21 | 2018-04-20 | 广东欧珀移动通信有限公司 | Control method, device and the storage medium and mobile terminal of application service |
| CN109005245A (en) * | 2018-09-07 | 2018-12-14 | 广州微算互联信息技术有限公司 | The use management method and system of cloud mobile phone |
| CN109992343A (en) * | 2019-03-27 | 2019-07-09 | 上海达龙信息科技有限公司 | Control method, control system and the electronic equipment of virtual cloud desktop server |
| CN110502324A (en) * | 2019-07-31 | 2019-11-26 | 湖南微算互联信息技术有限公司 | The processing method, system and storage medium for restarting data of cloud mobile phone games |
| CN111143170A (en) * | 2019-12-31 | 2020-05-12 | 北京云派网络科技有限公司 | Cloud mobile phone monitoring system and method |
| CN113472956A (en) * | 2021-09-03 | 2021-10-01 | 北京健康之家科技有限公司 | Cloud mobile phone management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114006902B (en) | 2023-08-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113766487B (en) | Cloud mobile phone information acquisition method, device, equipment and medium | |
| CN114356547B (en) | Low-priority blocking method and device based on processor virtualization environment | |
| CN115659039A (en) | Information recommendation method, information recommendation device, information display method, information recommendation equipment, information display medium and program product | |
| CN117742959A (en) | Training method and device based on clusters, electronic equipment and storage medium | |
| CN114936173B (en) | Read-write method, device, equipment and storage medium of eMMC device | |
| US9436505B2 (en) | Power management for host with devices assigned to virtual machines | |
| CN113225265B (en) | Flow control method, device, equipment and computer storage medium | |
| CN114025037B (en) | Cloud mobile phone overhaul method and device, electronic equipment and storage medium | |
| CN113961289A (en) | Data processing method, device, equipment and storage medium | |
| CN113608765A (en) | Data processing method, device, equipment and storage medium | |
| CN113419865A (en) | Cloud resource processing method, related device and computer program product | |
| CN112965799A (en) | Task state prompting method and device, electronic equipment and medium | |
| CN114006902A (en) | Cloud mobile phone restarting method, device, equipment and storage medium | |
| CN113703793B (en) | Application installation method, device, equipment and medium for cloud mobile phone | |
| CN114398150A (en) | Application running method, device, equipment and storage medium | |
| CN115953771A (en) | Text image processing method, device, equipment and medium | |
| CN114051057A (en) | Method and device for determining queuing time of cloud equipment, electronic equipment and medium | |
| CN114443439A (en) | Control method, device and equipment based on ARM server and storage medium | |
| CN113760431A (en) | Application program control method and device, electronic equipment and readable storage medium | |
| CN114090118A (en) | Method, device and equipment for starting small program and storage medium | |
| CN112882711A (en) | Rendering method, device, equipment and storage medium | |
| CN114082174A (en) | Control method and device of cloud game, electronic equipment and storage medium | |
| CN114217837A (en) | Software updating method, device, equipment and medium for cloud mobile phone | |
| CN118170324B (en) | Cloud hard disk migration method and device, electronic equipment and storage medium | |
| CN114003367B (en) | Risk monitoring method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |