Managed end identification method, management system, computer and storage medium

Abstract

The invention provides a managed end identification method, a management system, a computer and a storage medium. The method comprises the following steps: analyzing a screen image of a user by utilizing a pre-training model, and identifying image content; performing region division on the screen image according to the analysis result and the recognized image content to obtain a plurality of image regions; predicting an optimal quantization parameter of each image region according to a preset rule; and compressing the corresponding image according to the optimal quantization parameter of each image area, and transmitting the compressed screen image to a user managed end. According to the method for identifying the managed end, the unified unique identifier can be provided to identify the managed end, and the identifier can be used as the unique identifier of the managed end equipment in a general service scene.

Description

Technical Field

[0001] This disclosure relates to the field of identification managed end technology, specifically to an identification managed end method, management system, computer, and storage medium. Background Technology

[0002] For managed devices or software registered with the management system, a unique ID is required for identification as a unique identifier for the management system. This unique identifier is named End ID, or EID for short. Regarding the uniqueness of the End ID, due to the wide variety of managed devices or software types and the lack of a unified unique identifier for customer scenarios, it is difficult to find a hardware or system identifier to serve as the unique identifier for managed devices in typical business scenarios. Summary of the Invention

[0003] The purpose of this disclosure is to overcome the shortcomings of the prior art and provide a method, management system, computer and storage medium for identifying a managed device. This method for identifying a managed device can provide a unified and unique identifier to identify the managed device, which can be used as a unique identifier for the managed device in general business scenarios.

[0004] According to a first aspect of the present disclosure, a method for identifying a managed endpoint is provided, applied to a management system, comprising the following steps: Receive reporting information sent by the managed terminal, wherein the reporting information carries the characteristic information of the managed terminal; When the reported information carries the managed terminal EID information, the system queries whether there is preset EID information corresponding to the managed terminal EID information in the management system based on the managed terminal EID information. If there is no preset EID information corresponding to the managed terminal EID information in the management system, the managed terminal ID rule is obtained by querying the managed terminal identification configuration table according to the type and feature information of the managed terminal. The managed terminal EID information is generated based on the managed terminal feature information and the managed terminal ID rules, and the managed terminal EID information is returned to the managed terminal.

[0005] In one embodiment, the method further includes: If the management system contains preset EID information corresponding to the managed terminal's EID information, then the registration status of the managed terminal is updated.

[0006] In one embodiment, before updating the registration status of the managed terminal, the method further includes: Detect whether the managed terminal feature information is consistent with the managed terminal EID information; If the managed terminal feature information is consistent with the managed terminal EID information, then update the registration status of the managed terminal; If the managed terminal's feature information is inconsistent with the managed terminal's EID information, registration will fail and an error message will be returned to the managed terminal.

[0007] In one embodiment, the method further includes: The system detects whether at least two managed endpoints have the same EID information. If at least two managed terminals have the same EID information in the management system, then update the registration status of the first registered managed terminal. Modify the managed terminal ID rules for the remaining managed terminals and re-register them.

[0008] In one embodiment, the method further includes: Receive change information sent by the managed terminal; Determine whether the managed EID information needs to be updated based on the content of the change information.

[0009] In one embodiment, the method includes: If the content of the change information is a hardware change that is unrelated to the managed terminal ID rule, then the hardware feature information of the managed terminal will only be updated in the managed terminal identification configuration table.

[0010] In one embodiment, the method includes: If the content of the change information is a hardware change related to the managed terminal ID rule, then modify the managed terminal ID rule of the managed terminal. The managed terminal EID information is regenerated based on the modified managed terminal ID rules and the updated hardware feature information of the managed terminal device; The regenerated EID information of the managed end is returned to the managed end.

[0011] According to a second aspect of the present disclosure, a management system is provided, the management system comprising: a receiving module, a querying module, an acquiring module, and a generating module; wherein... The receiving module is used to receive reporting information sent by the managed terminal, and the reporting information carries the characteristic information of the managed terminal; The query module is used to query whether there is a preset EID information in the management system that corresponds to the managed terminal EID information when the reported information carries the managed terminal EID information. The acquisition module is used to query the managed terminal identification configuration table to obtain the managed terminal ID rule if there is no preset EID information in the management system that corresponds to the managed terminal EID information. The generation module is used to generate managed terminal EID information based on the managed terminal feature information and managed terminal ID rules, and return the managed terminal EID information to the managed terminal.

[0012] According to a third aspect of the present disclosure, a computer is provided, comprising: a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of any of the above methods.

[0013] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, characterized in that the computer program, when executed by a processor, implements the steps of the method as described in any of the above.

[0014] This disclosure provides a method for identifying a managed device. When a managed device registers with a management system, it reports corresponding feature information. The management system determines the corresponding feature information based on different device types in the managed device ID rule configuration table. If the feature information reported by the corresponding device type is incorrect, registration is rejected, and an error message indicating that the corresponding feature information is missing is displayed. If the feature information is normal, a device ID is generated according to the device ID generation rules configured in the management system and returned to the managed device. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0016] Figure 1 This is a flowchart illustrating a method for identifying a managed endpoint, as provided in an embodiment of this disclosure.

[0017] Figure 2 This is a flowchart illustrating a method for identifying a managed endpoint, as provided in an embodiment of this disclosure.

[0018] Figure 3 This is a flowchart illustrating a method for identifying a managed endpoint, as provided in an embodiment of this disclosure.

[0019] Figure 4 This is a logic diagram of a method for identifying a managed endpoint, provided in an embodiment of the present disclosure.

[0020] Figure 5 This is an architecture diagram of a management system provided in an embodiment of the present disclosure.

[0021] Figure 6This is an architectural diagram of a computer provided for an embodiment of the present disclosure. Detailed Implementation

[0022] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0023] The overall design concept of the identification method disclosed herein is as follows: Because different terminal types have different identification characteristics, different terminal IDs can be generated from the characteristic information of different terminal types (such as MAC address). At the same time, terminal IDs can also be generated from multiple characteristic information of the terminal type (such as MAC address + BIOS UUID). If problems occur in the management system when terminal IDs are not unique in customer scenarios, the system can add combination of characteristic information (such as adding the characteristic ID of BIOS UUID to the MAC address) to the original managed terminal ID rules through system configuration.

[0024] The management system generates a string-type EID based on the managed device ID rules and returns it to the end device or software. The end device or software needs to save the EID and ensure that it is not deleted after software updates, upgrades, or system restarts. If the EID is accidentally corrupted, the end device or software will be treated as a new device on the CAM side when it registers without the EID.

[0025] When end devices register in a scenario with EID, there are two scenarios on the CAM side: If the EID has already been saved on the management system side, the CAM will directly update the registration status and the registration will be successful.

[0026] The management system has not yet saved the EID (in the case where the end device has registered in the management system 1 environment and generated an EID, and then brought it to the management system 2 environment). The management system 2 regenerates the EID based on the registered feature information and returns it to the end device, which then updates the new EID.

[0027] End device registration without EID: The management system registers it as a new device. First, it generates an EID based on the feature information. Then, it checks whether the EID exists in the CAM. If it already exists in the management system, the registration is rejected. If it does not exist, the device registration is successful.

[0028] The specific steps are as follows: Create a new table: vca_endpoint_rule, with fields including: endpoint type, reported feature information, features required to generate the managed endpoint ID rule, and whether it is effective.

[0029] The management system exposes entry points for feature information corresponding to different terminal types on the interface, and supports modifying the feature information required to generate the corresponding terminal ID. An editing interface for terminal ID generation rules is added to the management system. Clicking the "Terminal ID Generation Rules" tab displays a table with four columns, the last of which is the operation column. These four columns are: Terminal Type, Reported Feature Information, Features Required to Generate Managed Terminal ID Rules, and Operation Column. The Operation Column displays a "Modify Rule" button. Clicking the "Modify" button pops up a dropdown list of features required to generate managed terminal ID rules for the current row. The dropdown list contains all the reported feature information for the current row, and also displays the selected features.

[0030] In this embodiment, the management system needs to initialize a default value in advance according to the predetermined rules during initialization.

[0031] It should be noted that the managed end in this embodiment is a terminal device or software.

[0032] Figure 1 This is a schematic diagram illustrating the workflow of an identifier managed terminal system provided in an embodiment of this disclosure. Figure 1 As shown, this method is applied to a management system, which includes: Step 101: Receive the reporting information sent by the managed terminal, wherein the reporting information carries the characteristic information of the managed terminal; In this step, when the terminal device or software registers for the first time or restarts registration, it obtains all the characteristic information of the device or software, and reports the characteristic information required by the terminal type according to the requirements of the terminal characteristic reporting form. The management system will obtain the managed terminal characteristic information from the reported information.

[0033] Step 102: When the reported information carries the managed terminal EID information, query the management system to see if there is any preset EID information corresponding to the managed terminal EID information. In this step, when the reported information includes the managed terminal's EID information, the management system queries the management system to see if there is any preset EID information corresponding to the EID information.

[0034] Step 103: If there is no preset EID information corresponding to the managed terminal EID information in the management system, then query the managed terminal identification configuration table according to the type and characteristic information of the managed terminal to obtain the managed terminal ID rule; wherein, the managed terminal identification configuration table is shown in Table 1.

[0035] Table 1 is the configuration table for the managed terminal. It should be noted that in the managed terminal information identification configuration table, the controlled terminal ID rule is a string, and is separated by commas (English).

[0036] In this step, if there is no preset EID information corresponding to the ID information in the management system, the management system queries the managed end identification configuration table to obtain the managed end ID rule based on the type and characteristic information of the managed end.

[0037] Step 104: Generate managed terminal EID information based on the managed terminal feature information and managed terminal ID rules, and return the managed terminal EID information to the managed terminal.

[0038] In this step, the management system generates the managed terminal EID information based on the managed terminal's characteristic information and the managed terminal ID rule, and returns this managed terminal EID information to the terminal device or software. The terminal device or software needs to save the managed terminal EID information. For example, if the managed terminal ID rule is the MAC address, then the management system only needs to generate the managed ID based on the MAC address; if the managed terminal ID rule is MAC address + BIOS UUID, then the management system needs to generate the managed terminal EID by combining the MAC address and BIOS UUID.

[0039] Optionally, the method further includes: If the management system contains preset EID information corresponding to the managed terminal's EID information, then the registration status of the managed terminal is updated.

[0040] In this embodiment, when there is preset EID information in the management system that corresponds to the EID information of the managed terminal, it is only necessary to update the registration status of the managed terminal.

[0041] In one embodiment, before updating the registration status of the managed terminal, the method further includes: Detect whether the managed terminal feature information is consistent with the managed terminal EID information; If the managed terminal feature information is consistent with the managed terminal EID information, then update the registration status of the managed terminal; If the managed terminal's feature information is inconsistent with the managed terminal's EID information, registration will fail and an error message will be returned to the managed terminal.

[0042] In this embodiment, the management system detects whether the characteristic information of the managed end is consistent with the EID information of the management end. When the characteristic information of the management end is consistent with the EID information of the managed end, the registration status of the managed end is updated. When the characteristic information of the management end is inconsistent with the EID information of the managed end, the registration fails and an error message is returned to the terminal device software.

[0043] Optionally, such as Figure 2 As shown, the method further includes: Step 201: Detect whether there are at least two managed terminals with the same EID information in the management system; Step 202: If at least two managed terminals have the same EID information in the management system, update the registration status of the first registered managed terminal. Step 203: Modify the managed terminal ID rules for the remaining managed terminals and re-register.

[0044] It should be noted that if the operating system of a previously registered client software (such as Windows software) is reinstalled, the original stored EID is deleted. However, the management system already contains information about this client software, so registration fails even though the device already exists. In this scenario, it is impossible to distinguish from a MAC address conflict scenario, so registration failure can only be returned. The administrator can manually delete the original resources from the management system and then re-register.

[0045] In one embodiment, the method further includes: The system detects whether at least two managed endpoints have the same EID information. If at least two managed terminals have the same EID information in the management system, then update the registration status of the first registered managed terminal. Modify the managed terminal ID rules for the remaining managed terminals and re-register them.

[0046] In this embodiment, when two managed terminals have the same EID information, the first managed terminal registers successfully, while the others fail to register. The management system modifies the management terminal ID rules for the failed managed terminals and then re-registers them. The re-registration process is the same as described above, and will not be repeated in this embodiment.

[0047] It should be noted that the EID and resource ID managed internally by the management system do not need to be changed, thus ensuring the consistency of the original registered terminal devices or software resources.

[0048] Optionally, the method further includes: Receive change information sent by the managed terminal; Determine whether the managed EID information needs to be updated based on the content of the change information.

[0049] In one embodiment, the method includes: If the content of the change information is a hardware change that is unrelated to the managed terminal ID rule, then the hardware feature information of the managed terminal will only be updated in the managed terminal identification configuration table.

[0050] In this embodiment, if the change information is a hardware change unrelated to the managed terminal ID rule, such as the managed terminal ID rule being the MAC address and other hardware of the managed terminal changing, the registration process will not be affected. The management system only needs to update the relevant hardware feature information of the managed terminal, and the original EID and resource ID of the managed terminal do not need to be changed.

[0051] In one implementation, such as Figure 3 As shown, the method includes: Step 301: If the content of the change information is a hardware change related to the managed terminal ID rule, then modify the managed terminal ID rule of the managed terminal. Step 302: Regenerate the managed terminal EID information according to the modified managed terminal ID rules and the updated hardware feature information of the managed terminal device; Step 303: Return the regenerated managed terminal EID information to the managed terminal.

[0052] In this embodiment, if the change information is a hardware change related to this type of managed terminal ID rule, such as the managed terminal ID rule being a MAC address, and the managed terminal's network card being replaced, resulting in a change in the MAC address; in this case, after the managed terminal is registered, it will become a new resource according to the current managed terminal ID rule, so it is necessary to register a new managed terminal EID and resource ID in the management system.

[0053] Figure 4 This disclosure provides a logic diagram for identifying a managed endpoint method.

[0054] This disclosure provides a method for identifying a managed device. When a managed device registers with a management system, it reports corresponding feature information. The management system determines the corresponding feature information based on different device types in the managed device ID rule configuration table. If the feature information reported by the corresponding device type is incorrect, registration is rejected, and an error message indicating that the corresponding feature information is missing is displayed. If the feature information is normal, a device ID is generated according to the device ID generation rules configured in the management system and returned to the managed device.

[0055] Figure 5 This is a structural diagram of a management system provided in an embodiment of this disclosure. Figure 5 As shown, the management system includes: a receiving module 501, a querying module 502, an acquiring module 503, and a generating module 504; wherein, the receiving module 501 is used to receive reporting information sent by the managed terminal, the reporting information carrying the characteristic information of the managed terminal; the querying module 502 is used to query whether there is preset EID information corresponding to the managed terminal EID information in the management system when the reported information carries the managed terminal EID information; the acquiring module 503 is used to query the managed terminal identification configuration table to obtain the managed terminal ID rule according to the type and characteristic information of the managed terminal when there is no preset EID information corresponding to the managed terminal EID information in the management system; the generating module 504 is used to generate managed terminal EID information according to the managed terminal characteristic information and the managed terminal ID rule, and return the managed terminal EID information to the managed terminal.

[0056] In one embodiment, a computer is provided, the internal structure of which can be as follows: Figure 6 As shown. The computer includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and the database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores data. The network interface communicates with external managed devices via a network connection. When the computer program is executed by the processor, it implements the above-described method for implementing a VR game based on emotion analysis. It includes: memory and a processor; the memory stores the computer program; and the processor executes the computer program to implement any step in the above-described method for implementing a VR game based on emotion analysis.

[0057] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, can perform any of the steps in the above-described method for implementing a VR game based on emotion analysis.

[0058] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can 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, etc.) containing computer-usable program code.

[0059] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing processor to produce a machine, such that the instructions, which execute via the computer or other programmable data processing processor, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0060] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0061] These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device to implement the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0062] Although preferred embodiments of this disclosure have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this disclosure.

[0063] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A method for identifying a managed endpoint, characterized in that, Applied to a management system, the method includes: Receive reporting information sent by the managed terminal, wherein the reporting information carries the characteristic information of the managed terminal; When the reported information carries the managed terminal EID information, the system queries whether there is preset EID information corresponding to the managed terminal EID information in the management system based on the managed terminal EID information. If there is no preset EID information corresponding to the managed terminal EID information in the management system, the managed terminal ID rule is obtained by querying the managed terminal identification configuration table according to the type and feature information of the managed terminal. The managed terminal EID information is generated based on the managed terminal feature information and the managed terminal ID rules, and the managed terminal EID information is returned to the managed terminal.

2. The method according to claim 1, characterized in that, The method further includes: If the management system contains preset EID information corresponding to the managed terminal's EID information, then the registration status of the managed terminal is updated.

3. The method according to claim 2, characterized in that, Before updating the registration status of the managed terminal, the method further includes: Detect whether the managed terminal feature information is consistent with the managed terminal EID information; If the managed terminal feature information is consistent with the managed terminal EID information, then update the registration status of the managed terminal; If the managed terminal's feature information is inconsistent with the managed terminal's EID information, registration will fail and an error message will be returned to the managed terminal.

4. The method according to claim 1, characterized in that, The method further includes: The system detects whether at least two managed endpoints have the same EID information. If at least two managed terminals have the same EID information in the management system, then update the registration status of the first registered managed terminal. Modify the managed terminal ID rules for the remaining managed terminals and re-register them.

5. The method according to claim 1, characterized in that, The method further includes: Receive change information sent by the managed terminal; Determine whether the managed EID information needs to be updated based on the content of the change information.

6. The method according to claim 5, characterized in that, The method includes: If the content of the change information is a hardware change that is unrelated to the managed terminal ID rule, then the hardware feature information of the managed terminal will only be updated in the managed terminal identification configuration table.

7. The method according to claim 1, characterized in that, The method includes: If the content of the change information is a hardware change related to the managed terminal ID rule, then modify the managed terminal ID rule of the managed terminal. The managed terminal EID information is regenerated based on the modified managed terminal ID rules and the updated hardware feature information of the managed terminal device; The regenerated EID information of the managed end is returned to the managed end.

8. A management system, characterized in that, The management system includes: a receiving module, a query module, an acquisition module, and a generation module; wherein, The receiving module is used to receive reporting information sent by the managed terminal, and the reporting information carries the characteristic information of the managed terminal; The query module is used to query whether there is a preset EID information in the management system that corresponds to the managed terminal EID information when the reported information carries the managed terminal EID information. The acquisition module is used to query the managed terminal identification configuration table to obtain the managed terminal ID rule if there is no preset EID information in the management system that corresponds to the managed terminal EID information. The generation module is used to generate managed terminal EID information based on the managed terminal feature information and managed terminal ID rules, and return the managed terminal EID information to the managed terminal.

9. A computer, comprising: A memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images