CN107545198B - Key management method and device - Google Patents
Key management method and device Download PDFInfo
- Publication number
- CN107545198B CN107545198B CN201710351987.5A CN201710351987A CN107545198B CN 107545198 B CN107545198 B CN 107545198B CN 201710351987 A CN201710351987 A CN 201710351987A CN 107545198 B CN107545198 B CN 107545198B
- Authority
- CN
- China
- Prior art keywords
- client
- key information
- kvm
- monitoring
- application
- 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.)
- Active
Links
Images
Abstract
The application provides a key management method and a key management device, wherein the method comprises the following steps: after the KVM client obtains a focus, blocking communication between key information and the application client through the monitoring client, so that the application client cannot obtain the key information; and providing the key information to the KVM client so that the KVM client operates a server corresponding to the KVM client by using the key information. Through the technical scheme, the KVM client can operate the remote server based on the key information of the host, so that the remote server is conveniently operated, and the user experience is improved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a key management method and apparatus.
Background
The effective management of the server is an inevitable problem for managers, and the current implementation method is as follows: the manager manages the server through a KVM (Keyboard Video Mouse, display terminal, and Mouse). As shown in fig. 1, a schematic diagram of a manager managing a server through a KVM client is shown, where the KVM client for managing the server is configured on a PC (Personal Computer), and the manager may operate a remote server through the KVM client on the PC.
Disclosure of Invention
The application provides a key management method, which is applied to a host comprising an application client, a KVM client and a monitoring client, and comprises the following steps:
after the KVM client obtains a focus, blocking communication between key information and the application client through the monitoring client, so that the application client cannot obtain the key information;
and providing the key information to the KVM client so that the KVM client operates a server corresponding to the KVM client by using the key information.
The application provides a button management device, is applied to the host computer including application client, KVM client and monitoring client, the device specifically includes:
the processing module is used for blocking the communication between the key information and the application client side through the monitoring client side after the KVM client side obtains the focus, so that the application client side cannot obtain the key information;
and the sending module is used for providing the key information to the KVM client so that the KVM client operates the server corresponding to the KVM client by using the key information.
Based on the above technical solution, in the embodiment of the present application, after the key information is monitored, communication between the key information and the application client may be blocked, so that the application client cannot obtain the key information, and the key information is provided to the KVM client, so that the KVM client may operate the server corresponding to the KVM client by using the key information. Therefore, based on the key information of the host, the KVM client can operate a remote server, the remote server is convenient to operate, and the user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIG. 1 is a schematic diagram of server management by a KVM client;
FIG. 2 is a schematic diagram of an application scenario in an embodiment of the present application;
FIG. 3 is a flow chart of a key management method according to an embodiment of the present application;
fig. 4 is a block diagram of a key management device according to an embodiment of the present application;
fig. 5 is a hardware configuration diagram of a host according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" and the like, as used herein, is intended to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" is used may be interpreted as "at … …," or "when … …," or "in response to a determination.
An embodiment of the present application provides a key management method, which may be applied to a host (i.e., a PC) including an operating system, an application client, a KVM client, and a monitoring client, and is shown in fig. 2, which is an application scenario diagram of the key management method. The operating system is a computer program for managing and controlling hardware resources and software resources of the host, is basic system software, and other application programs can run only under the support of the operating system. The KVM client is an application installed on the host for managing the server. The monitoring client is an application program installed on the host and used for monitoring the key information and blocking communication between the monitored key information and the application client, so that the application client cannot acquire the key information, the KVM client can acquire the key information, and the server is managed by using the key information. The application client is a client other than the KVM client local to the host, and is configured to implement a corresponding function, for example, the application client may be a word, a pdf, a browser, a QQ, or the like.
In one example, great convenience may be provided to the user by configuring the key for the KVM client such that the KVM client operates the server through the key. However, if the key configured for the KVM client is the same as the key of the application client, the application client may respond to the key preferentially, and the KVM client may also respond to the key preferentially.
In view of the above discovery, the key management method provided in the embodiment of the present application may monitor the key information through the monitoring client, and block communication between the key information and the application client, so that the application client cannot acquire the key information, and the KVM client can acquire the key information.
In an example, the operating system may include, but is not limited to, a Windows operating system, a Linux operating system, an iOS operating system, an android operating system, and the like, for convenience of description, the Windows operating system is taken as an example for illustration, and for other operating systems such as the Linux operating system, the iOS operating system, and the android operating system, a processing manner of the operating system is similar to that of the Windows operating system, and details are not described later.
On a host installed with a Windows operating system, a listening client may be implemented by a HOOK program (also referred to as a HOOK function). The nature of the HOOK program is a function for processing messages, the HOOK program is hung in the Windows operating system by calling an API (Application Programming Interface) of the Windows operating system, when a specific message (such as a message carrying key information) is sent out, the HOOK program can capture the specific message before the specific message reaches a destination window (such as an Application client), that is, the HOOK program obtains control right first.
Certainly, in practical applications, the listening client may also be implemented by using other functions (e.g., a blocking function), the blocking function may be suspended in an operating system (e.g., a Windows operating system, a Linux operating system, etc.), and when a specific message (e.g., a message carrying key information) is sent out, before the specific message does not reach a destination window (e.g., an application client), the blocking function may capture the specific message first, that is, the blocking function obtains a control right first. The implementation manner of the monitoring client is not limited as long as the functions can be realized.
In the application scenario, referring to fig. 3, a schematic flow chart of the key management method is shown.
In one example, after the KVM client obtains focus, the key information may be listened to by the listening client. After the key information is monitored, the communication between the key information and the application client can be blocked by the monitoring client, so that the application client cannot acquire the key information.
In one example, the monitoring client is in the off state before the KVM client obtains focus, and key information is not monitored by the monitoring client. In addition, after the KVM client obtains the focus, the monitoring client may be started, and then the key information is monitored by the monitoring client. In addition, after the KVM client loses focus, the monitoring client may be turned off, and key information is no longer monitored by the monitoring client. The monitoring client is a client for monitoring key information.
When the host display window is the window of the KVM client, it indicates that the KVM client has currently obtained the focus, and at this time, the operation of the user for the host is the operation for the KVM client. Additionally, when the host display window is no longer the window of the KVM client, it indicates that the KVM client has currently lost focus, at which point the user is operating on the host, not the KVM client.
In one example, the listening client can listen to the message carrying the key information, i.e., the listening client can listen to the key information. Specifically, after monitoring the message carrying the key information, the operating system sends the message carrying the key information to the monitoring client, and the monitoring client can monitor the key information.
In one example, the key information monitored by the monitoring client may be key information that the application client has a priority usage right, or key information that the application client does not have a priority usage right. Based on the key information, after the key information is monitored, whether the application client has the priority using right of the key information can be judged through the monitoring client; if yes, the communication between the key information and the application client side can be blocked through the monitoring client side, so that the application client side cannot acquire the key information; if not, the key information may be provided directly to the KVM client that has obtained the focus without performing a blocking operation.
In one example, in order to enable the listening client to know the key information that the application client does not have the priority usage right and the key information that the application client has the priority usage right, an information table for recording the key information that the application client does not have the priority usage right and/or the key information that the application client has the priority usage right may be further configured for the listening client. Based on the information table, after the monitoring client monitors the key information, whether the application client has the priority of using the key information can be judged by inquiring the information table.
For example, if the information table is configured with key information without priority usage right, after the key information is monitored, if the key information exists in the information table, it indicates that the application client does not have the priority usage right of the key information, and if the key information does not exist in the information table, it indicates that the application client has the priority usage right of the key information. For another example, if the information table is configured with key information with priority usage right, after the key information is monitored, if the key information exists in the information table, it indicates that the application client has the priority usage right of the key information, and if the key information does not exist in the information table, it indicates that the application client does not have the priority usage right of the key information. For example, if the information table is configured with key information without priority usage right and key information with priority usage right, after the key information is monitored, the information table can be queried to directly determine whether the application client has the priority usage right of the key information.
In one example, the key information of the application client with the priority usage right refers to: after obtaining the key information, the operating system does not provide the key information to the KVM client that has obtained the focus, but provides the key information to the application client, so that the application client performs an operation based on the key information, for example, after obtaining the key information corresponding to the key (Alt + Tab), the operating system provides the key information to the application client, and the application client performs a screen-switching operation based on the key information. The key information that the application client has no priority usage right refers to: after obtaining the key information, the operating system provides the key information to the KVM client that has obtained the focus, and performs an operation based on the key information by the KVM client, where ctrl + c, ctrl + v, and so on are key information for which the application client does not have the priority right.
In one example, information generated when a user operates a keyboard may be used as the key information, and the key information may be general key information (e.g., a, b, c, etc.) and shortcut key information (e.g., ctrl + c, ctrl + v, etc.). The shortcut key information is information generated by a user operating a shortcut key, the shortcut key can be called a shortcut key or a hot key, the operation is completed through certain specific keys, key sequences or key combinations, and the shortcut key can be used for replacing a mouse to complete some work, for example, ctrl + c represents copying, and ctrl + v represents pasting.
In one example, the process for "providing key information to KVM client" may include, but is not limited to: the method I is that the key information is sent to the KVM client by the monitoring client; or, in the second mode, the adjustment parameter corresponding to the key information is determined by monitoring the client, and the configuration file is modified according to the adjustment parameter; then, the configuration file is monitored through the KVM client, the adjusting parameters are analyzed from the configuration file, and the key information corresponding to the adjusting parameters is determined. The format of the configuration file specifically includes but is not limited to: txt format, xml format, json format, word format or PDF format, etc., without limitation to the file format; in addition, the adjustment parameters specifically include but are not limited to: identification information and execution times corresponding to the key information.
For the first method, when the communication between the key information and the application client is blocked, the application client cannot acquire the key information, and the KVM client cannot acquire the key information. In order to enable the KVM client to obtain the key information, the following functions may also be configured for the monitoring client: the key information is sent to the KVM client, based on which the listening client may send the key information to the KVM client.
For the second method, when the communication between the key information and the application client is blocked, the application client cannot acquire the key information, and the KVM client cannot acquire the key information. In order to make the KVM client obtain the key information, the following functions may also be configured for the monitoring client: and modifying the configuration file through the adjustment parameters corresponding to the key information. Based on this, after the monitoring client monitors the key information, the monitoring client determines the adjustment parameters (such as identification information and execution times corresponding to Alt + Tab) corresponding to the key information, and records the adjustment parameters in the configuration file. In addition, the KVM client may periodically monitor the configuration file, and when the configuration file changes, the adjustment parameter may be parsed from the configuration file, and the key information corresponding to the adjustment parameter may be determined, so that the KVM client may obtain the key information.
The identification information corresponding to the key information may include but is not limited to: the name of the key information (e.g., Alt + Tab key), and the unique string corresponding to the key information (e.g., Alt + Tab key string 123123), are not limited to this identification information, as long as the key information can be distinguished.
Because the configuration file records the identification information and the execution times corresponding to the key information, the KVM client can analyze the identification information and the execution times from the configuration file to obtain the key information. For example, in the last period, the configuration file records the Alt + Tab key and the execution time 1, while in the current period, the configuration file records the Alt + Tab key and the execution time 2, so that the KVM client may know that the key information is the Alt + Tab key. For another example, in the last period, the ctrl + c button and the execution count 1 are recorded in the configuration file, and in the current period, the Alt + Tab button and the execution count 1 are recorded in the configuration file, so that the KVM client may know that the button information is the Alt + Tab button.
Based on the above technical solution, in the embodiment of the present application, after the key information is monitored, communication between the key information and the application client may be blocked, so that the application client cannot obtain the key information, and the key information is provided to the KVM client, so that the KVM client may operate the server corresponding to the KVM client by using the key information. Therefore, based on the key information of the PC, the KVM client can operate a remote server, the remote server is convenient to operate, and the user experience is improved.
Based on the same application concept as the method, an embodiment of the present application further provides a key management device, which is applied to a host including an application client, a KVM client, and a monitoring client, as shown in fig. 4, and is a structural diagram of the key management device provided by the present application, where the key management device specifically includes:
a processing module 401, configured to block, by the monitoring client, communication between the key information and the application client after the KVM client obtains a focus, so that the application client cannot obtain the key information;
a sending module 402, configured to provide the key information to the KVM client, so that the KVM client operates a server corresponding to the KVM client by using the key information.
The processing module 401 is further configured to start the monitoring client after the KVM client obtains a focus; after the KVM client loses focus, closing the monitoring client;
the monitoring client is used for monitoring key information.
The sending module 402 is specifically configured to send the key information to the KVM client through the monitoring client in a process of providing the key information to the KVM client; alternatively, the first and second electrodes may be,
determining an adjusting parameter corresponding to the key information through the monitoring client, and modifying a configuration file according to the adjusting parameter; and monitoring the configuration file through the KVM client, analyzing the adjustment parameters from the configuration file, and determining the key information corresponding to the adjustment parameters.
The format of the configuration file modified by the sending module 402 according to the adjustment parameter is specifically: txt format, or xml format, or json format; the adjusting parameters determined by the sending module 402 specifically include: and identification information and execution times corresponding to the key information.
The processing module 401 is specifically configured to determine, by the monitoring client, whether the application client has a priority usage right of the key information in a process of blocking communication between the key information and the application client by the monitoring client; if yes, the communication between the key information and the application client side is blocked through the monitoring client side.
In the host provided in the embodiment of the present application, from a hardware level, a schematic diagram of a hardware architecture of the host may specifically refer to fig. 5. The method comprises the following steps: a machine-readable storage medium and a processor, wherein:
a machine-readable storage medium: the instruction code is stored.
A processor: the instruction codes stored in the machine readable storage medium are read and executed by communicating with the machine readable storage medium, so as to realize the key management operation disclosed by the above example of the application.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: a RAM (random access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (which may include, but is not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A key management method is applied to a host comprising an application client, a KVM client and a monitoring client, and comprises the following steps:
after the KVM client obtains a focus, blocking communication between key information and the application client through the monitoring client, so that the application client cannot obtain the key information;
and providing the key information to the KVM client so that the KVM client operates a server corresponding to the KVM client by using the key information.
2. The method of claim 1, further comprising:
after the KVM client obtains a focus, starting the monitoring client;
after the KVM client loses focus, closing the monitoring client;
the monitoring client is used for monitoring key information.
3. The method of claim 1,
the process of providing the key information to the KVM client specifically includes:
sending the key information to the KVM client through the monitoring client; alternatively, the first and second electrodes may be,
determining an adjusting parameter corresponding to the key information through the monitoring client, and modifying a configuration file according to the adjusting parameter; and monitoring the configuration file through the KVM client, analyzing the adjustment parameters from the configuration file, and determining the key information corresponding to the adjustment parameters.
4. The method of claim 3,
the format of the configuration file is specifically as follows: txt format, or xml format, or json format;
the adjusting parameters specifically include: and identification information and execution times corresponding to the key information.
5. The method according to claim 1, wherein the process of blocking communication between the key information and the application client by the listening client specifically includes:
judging whether the application client has the priority using right of the key information or not through the monitoring client; if yes, the communication between the key information and the application client side is blocked through the monitoring client side.
6. A key management device is applied to a host comprising an application client, a KVM client and a monitoring client, and specifically comprises:
the processing module is used for blocking the communication between the key information and the application client side through the monitoring client side after the KVM client side obtains the focus, so that the application client side cannot obtain the key information;
and the sending module is used for providing the key information to the KVM client so that the KVM client operates the server corresponding to the KVM client by using the key information.
7. The apparatus of claim 6,
the processing module is further configured to start the monitoring client after the KVM client obtains the focus; after the KVM client loses focus, closing the monitoring client;
the monitoring client is used for monitoring key information.
8. The apparatus of claim 6,
the sending module is specifically configured to send the key information to the KVM client through the monitoring client in a process of providing the key information to the KVM client; alternatively, the first and second electrodes may be,
determining an adjusting parameter corresponding to the key information through the monitoring client, and modifying a configuration file according to the adjusting parameter; and monitoring the configuration file through the KVM client, analyzing the adjustment parameters from the configuration file, and determining the key information corresponding to the adjustment parameters.
9. The apparatus of claim 8,
the format of the configuration file modified by the sending module according to the adjustment parameter is specifically as follows: txt format, or xml format, or json format; the adjusting parameters determined by the sending module specifically include: and identification information and execution times corresponding to the key information.
10. The apparatus according to claim 6, wherein the processing module is specifically configured to determine, by the monitoring client, whether the application client has a priority right to use the key information during the process of blocking the communication between the key information and the application client by the monitoring client; if yes, the communication between the key information and the application client side is blocked through the monitoring client side.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710351987.5A CN107545198B (en) | 2017-05-18 | 2017-05-18 | Key management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710351987.5A CN107545198B (en) | 2017-05-18 | 2017-05-18 | Key management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107545198A CN107545198A (en) | 2018-01-05 |
| CN107545198B true CN107545198B (en) | 2020-02-11 |
Family
ID=60966819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710351987.5A Active CN107545198B (en) | 2017-05-18 | 2017-05-18 | Key management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107545198B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101452376A (en) * | 2007-12-06 | 2009-06-10 | 宏正自动科技股份有限公司 | Methods and systems for client computer managing multiple servers |
| CN101819468A (en) * | 2009-02-26 | 2010-09-01 | 国际商业机器公司 | Method and device for accessing input fields in form |
| CN104636103A (en) * | 2014-12-31 | 2015-05-20 | 华为技术有限公司 | Keyboard data transmission method and device |
| CN105051713A (en) * | 2013-03-15 | 2015-11-11 | 安迈科技股份有限公司 | System and method of web-based keyboard, video and mouse (kvm) redirection and application of the same |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060143473A1 (en) * | 2004-12-29 | 2006-06-29 | Kumar Mohan J | Software key implementation using system management firmware |
| CN101072381B (en) * | 2007-06-14 | 2015-04-15 | 华为技术有限公司 | Terminal control message processing method and message processor and media server |
| CN101127784B (en) * | 2007-09-29 | 2011-08-03 | 网秦无限（北京）科技有限公司 | Method and system for quickly obtaining network information service at mobile terminal |
| CN103020526B (en) * | 2012-12-21 | 2016-04-13 | 北京奇虎科技有限公司 | Rogue program active interception method and apparatus and client device |
| CN103067176A (en) * | 2013-01-11 | 2013-04-24 | 浪潮集团有限公司 | Safety authentication method applied to multi-unit server management |
| CN103888296A (en) * | 2014-03-21 | 2014-06-25 | 浪潮电子信息产业股份有限公司 | Blade server KVM switching technology |
-
2017
- 2017-05-18 CN CN201710351987.5A patent/CN107545198B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101452376A (en) * | 2007-12-06 | 2009-06-10 | 宏正自动科技股份有限公司 | Methods and systems for client computer managing multiple servers |
| CN101819468A (en) * | 2009-02-26 | 2010-09-01 | 国际商业机器公司 | Method and device for accessing input fields in form |
| CN105051713A (en) * | 2013-03-15 | 2015-11-11 | 安迈科技股份有限公司 | System and method of web-based keyboard, video and mouse (kvm) redirection and application of the same |
| CN104636103A (en) * | 2014-12-31 | 2015-05-20 | 华为技术有限公司 | Keyboard data transmission method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107545198A (en) | 2018-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9935847B2 (en) | Dynamic grouping of managed devices | |
| US9781542B2 (en) | Techniques for predictive power management of a mobile device | |
| US9659066B2 (en) | Dynamic interest-based notifications | |
| US9836346B2 (en) | Error troubleshooting using a correlated knowledge base | |
| US10530716B2 (en) | Voice chat mode self-adapting method and apparatus | |
| US10885218B2 (en) | Privacy protection method and terminal device | |
| US20190146830A1 (en) | Template-driven multi-tenant workflow processing | |
| CN106445292B (en) | Method and system for managing application programs in different body modes | |
| US9454375B2 (en) | Parallel program analysis and branch prediction | |
| JP2015529913A (en) | Information backup method and apparatus | |
| KR20160145116A (en) | Battery efficient synchronization of communications using a token bucket | |
| US10897512B2 (en) | Generating push notifications | |
| CN115001967B (en) | Data acquisition method and device, electronic equipment and storage medium | |
| US8855599B2 (en) | Method and apparatus for auxiliary communications with mobile communications device | |
| CN113590017B (en) | Method, electronic device and computer program product for processing data | |
| CN110868347A (en) | Message prompting method, device and system | |
| CN107545198B (en) | Key management method and device | |
| CN107154971A (en) | One kind application method for down loading and device | |
| KR102428002B1 (en) | Electronic device for installing a profile and method for the same | |
| US20220046093A1 (en) | Planned message notification for iot device based on activity | |
| US20180321970A1 (en) | Controlling Background Activity of an Application Using a Policy | |
| CN106776057B (en) | Event processing method and device | |
| CN110928630A (en) | Activation control method, device and equipment for application program window and storage medium | |
| CN112446984A (en) | Intelligent door lock control method and device | |
| US11683348B2 (en) | Bypassing security vulnerable and anomalous devices in multi-device workflow |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant after: Xinhua Sanxin Information Technology Co., Ltd. Address before: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Applicant before: Huashan Information Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |