Terminal software management platform and method, electronic equipment and storage medium

By providing a terminal software management platform, including software management modules and certification management modules, the problems of terminal software difficulty in managing and information security risks are solved, and unified management and high security are achieved.

CN119939552APending Publication Date: 2025-05-06CHONGQING SELIS PHOENIX INTELLIGENT INNOVATION TECH CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202510043259.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-01-10
Publication Date
2025-05-06

AI Technical Summary

Technical Problem

Since each terminal software is independently developed and deployed by multiple departments, it is difficult to manage and maintain, and there are large information security risks.

Method used

Provides a terminal software management platform, including software management module and certification management module. The software management module is used to visually display and manage multiple terminal software, and the authentication management module is used to receive software access requests from terminal devices, perform permission verification, and ensure the security of data transmission through encryption protocols.

Benefits of technology

It realizes unified management of terminal software, facilitates unified maintenance of multiple terminal software, and improves information security through strict authentication mechanisms, reduces information security risks, and is low in cost.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119939552A_ABST
    Figure CN119939552A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of computers, in particular to a terminal software management platform and method, electronic equipment and a storage medium, and the platform comprises a software management module which is used for carrying out visual display and management on multiple pieces of terminal software; the authentication management module is used for receiving a software access request transmitted by the terminal equipment, the software access request comprises equipment authentication information, account authentication information and a target key, and the target key is generated when the terminal software management platform establishes a communication channel with the current terminal equipment for the first time; based on the equipment authentication information, the account authentication information and the target secret key, performing permission verification on the terminal equipment; if the permission verification is passed, allowing the terminal device to access one or more terminal software in the software management module; according to the platform, unified management and maintenance of the terminal software can be realized, and in addition, through the authentication mode, the software information security degree can be better improved, and the information security risk can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a terminal software management platform, method, electronic device and storage medium. Background Art

[0002] With the advancement of digital transformation, enterprises have gradually introduced and developed a large number of terminal software in various business areas. These terminal software usually cover different systems, devices, applications and services, and are used in various business processes of enterprises. The functions of terminal software are constantly expanding, covering multiple fields from automated testing, performance monitoring, data collection to system security.

[0003] However, since each terminal software is often independently developed and deployed by multiple departments, it is difficult to manage and maintain, and there are also great risks in information security. For example, separately deployed terminal software may cause sensitive data to be leaked during the flow between different systems, and decentralized terminal software may have more security vulnerabilities. Summary of the invention

[0004] The present application provides a terminal software management platform, method, electronic device and storage medium to solve the problem in the related art that each terminal software is often independently developed and deployed by multiple departments, resulting in difficulty in management and maintenance, and also posing a great risk in terms of information security.

[0005] The present application provides a terminal software management platform, the platform comprising: a software management module for visually displaying and managing multiple terminal software;

[0006] An authentication management module, configured to receive a software access request transmitted by a terminal device, wherein the software access request includes: device authentication information, account authentication information, and a target key, wherein the target key is generated when the terminal software management platform and the current terminal device establish a communication channel for the first time;

[0007] Based on the device authentication information, the account authentication information, and the target key, the terminal device is authenticated; if the authentication passes, the terminal device is allowed to access one or more terminal software in the software management module.

[0008] In one embodiment of the present application, the authentication management module is further used to receive an authentication request sent by a terminal device, wherein the authentication request includes the device authentication information and the account authentication information;

[0009] Based on the device authentication information and the account authentication information, the terminal device is authenticated; if the identity authentication is successful, the target key is generated and fed back to the terminal device.

[0010] In one embodiment of the present application, the authentication management module is further used to periodically send a callback request to the terminal device according to a preset authentication information refresh frequency, and the callback request is used to instruct the terminal device to re-authenticate the identity;

[0011] Receive the device authentication information and the account authentication information returned by the terminal device; and re-perform identity authentication based on the device authentication information and the account authentication information.

[0012] In one embodiment of the present application, it further includes: a terminal management module, the terminal management module includes:

[0013] The device registration unit is used to store the device information of the terminal device that has completed registration, wherein the device information includes: a unique identifier of the terminal device, a device type, an operating system, and network information;

[0014] A device deregistration unit, configured to deregister the corresponding terminal device upon receiving a device deregistration instruction, wherein the triggering mode of the device deregistration instruction includes: a preset device deregistration button is triggered, and the terminal device has not communicated with the terminal software management platform for a long time;

[0015] The device status monitoring unit is used to monitor the status of each terminal device.

[0016] In one embodiment of the present application, it further includes:

[0017] The user management module is used to create accounts and assign and manage permissions for the created accounts, wherein permission management includes: adding, deleting, and disabling permissions for the created accounts.

[0018] In one embodiment of the present application, it also includes: a data recording module, which is used to store the software usage record of the terminal device and store the terminal device record accessing the terminal software management platform.

[0019] In one embodiment of the present application, during the data transmission process, the authentication management module uses a preset encryption protocol to encrypt the data to be transmitted, and sends the encrypted data to the target end.

[0020] The present application also provides a terminal software management method based on the terminal software management platform as described in any one of the above, the method comprising:

[0021] Receiving a software access request transmitted by a terminal device, the software access request including: device authentication information, account authentication information, and a target key, wherein the target key is generated when a terminal software management platform and a current terminal device establish a communication channel for the first time;

[0022] Based on the device authentication information, the account authentication information, and the target key, verify the authority of the terminal device;

[0023] If the permission verification is passed, the terminal device is allowed to access one or more of the terminal software in the software management module.

[0024] The present application also provides an electronic device, comprising a processor, a memory and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute a computer program stored in the memory to implement a terminal software management method as provided in any of the above embodiments.

[0025] The present application also provides a computer-readable storage medium on which a computer program is stored, wherein the computer program is used to enable a computer to execute the terminal software management method provided in any of the above embodiments.

[0026] Beneficial effects of the embodiments of the present application: The terminal software management platform, method, electronic device and storage medium provided by the embodiments of the present application, the platform is used to visually display and manage multiple terminal software by setting up a software management module; and setting up an authentication management module, which is used to receive software access requests transmitted by terminal devices, the software access requests include: device authentication information, account authentication information, and target key, wherein the target key is generated when the terminal software management platform and the current terminal device first establish a communication channel; based on the device authentication information, account authentication information, and target key, the terminal device is authenticated; if the authority verification is passed, the terminal device is allowed to access one or more terminal software in the software management module. The platform can better realize the unified management of terminal software, facilitate the unified maintenance of multiple terminal software, and, through the above-mentioned authentication method, can better improve the software information security, reduce information security risks, and have low cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A schematic diagram of the structure of a terminal software management platform provided in one embodiment of the present application;

[0028] Figure 2 Another structural diagram of the terminal software management platform provided in one embodiment of the present application;

[0029] Figure 3A schematic diagram of the interaction logic of a terminal software management platform provided in one embodiment of the present application;

[0030] Figure 4 A schematic diagram of a user management interface of a terminal software management platform provided in an embodiment of the present application;

[0031] Figure 5 A schematic diagram of an organization management interface of a terminal software management platform provided in an embodiment of the present application;

[0032] Figure 6 A schematic diagram of a platform (software) management interface of a terminal software management platform provided in one embodiment of the present application;

[0033] Figure 7 A flowchart of a terminal software management method provided in one embodiment of the present application;

[0034] Figure 8 A schematic diagram of the structure of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0035] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0036] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.

[0037] In the following description, a large number of details are discussed to provide a more thorough explanation of the embodiments of the present application. However, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details. In other embodiments, well-known structures and devices are shown in the form of block diagrams rather than in detail to avoid making the embodiments of the present application difficult to understand.

[0038] Combine the following Figures 1 to 8 , the terminal software management platform, method, electronic device and storage medium provided by this application are explained.

[0039] See also Figure 1 , Figure 1 A schematic diagram of the structure of a terminal software management platform provided in an embodiment of the present application is shown in FIG. Figure 1 As shown, the platform includes:

[0040] The software management module 110 is used to visualize and manage multiple terminal software;

[0041] The authentication management module 120 is used to receive a software access request transmitted by a terminal device, wherein the software access request includes: device authentication information, account authentication information, and a target key, wherein the target key is generated when the terminal software management platform and the current terminal device establish a communication channel for the first time;

[0042] Based on the device authentication information, the account authentication information, and the target key, the terminal device is authenticated; if the authentication passes, the terminal device is allowed to access one or more terminal software in the software management module.

[0043] In some examples of this embodiment, the software management module 110 is used to visually display multiple terminal software in a preset visual operation interface. The visual operation interface has corresponding software management and operation buttons, such as software addition, software update, and deletion, etc., which facilitates administrators and users to manage multiple terminal software through the visual operation interface.

[0044] The above embodiment can improve the security of software access and reduce information security risks by setting the above authentication method in the authentication management module 120. It can be understood that the security of access to terminal software, that is, software resources, can be effectively improved through multi-factor authentication. Specifically, if any of the device authentication information, account authentication information, and target key fails to be verified, the terminal device is not qualified to access the software resources, thereby effectively improving the security of software access.

[0045] In some examples of this embodiment, the device authentication information includes a unique identifier of the terminal device, a certificate, and a device status, etc. The unique identifier of the terminal device is such as a MAC (physical) address, an IP (Internet Protocol Address, Internet Protocol) address, and a device serial number, etc. The account authentication information includes: information such as a user name and password.

[0046] In some examples of this embodiment, the authentication management module 120 can determine the legitimacy of this access based on the target key, that is, compare the target key in the access request with the pre-stored key to determine whether the terminal device and the user are allowed to access the software. In addition, based on the device authentication information, account authentication information, and preset permission records, the permissions of the current terminal device and user are determined to complete the permission verification. The permission record records the current terminal device and user's operating permissions for the software.

[0047] In addition, if the terminal device authority verification is passed, the user can view the list of available software in the terminal device and download the required terminal software to the local according to actual needs.

[0048] In some embodiments, the authentication management module 120 is further used to receive an authentication request sent by a terminal device, wherein the authentication request includes the device authentication information and the account authentication information;

[0049] Based on the device authentication information and the account authentication information, the terminal device is authenticated; if the identity authentication is successful, the target key is generated and fed back to the terminal device.

[0050] In some examples of this embodiment, the above identity authentication step can be applied to the authentication process when the terminal software management platform establishes a communication channel with the terminal device for the first time. By performing the above identity authentication, the security of the user accessing the terminal software can be improved to a certain extent.

[0051] In some embodiments, the authentication management module is further used to periodically send a callback request to the terminal device according to a preset authentication information refresh frequency, and the callback request is used to instruct the terminal device to re-authenticate the identity;

[0052] Receive the device authentication information and the account authentication information returned by the terminal device; and re-perform identity authentication based on the device authentication information and the account authentication information.

[0053] In some examples of this embodiment, the authentication information refresh frequency can be set according to actual needs. By regularly performing identity authentication and refreshing authentication information, information security can be effectively enhanced.

[0054] Figure 2 This is another structural diagram of the terminal software management platform provided in one embodiment of the present application. Please refer to Figure 2 In some embodiments, the platform further includes: a terminal management module 130, wherein the terminal management module 130 includes:

[0055] The device registration unit is used to store the device information of the terminal device that has completed registration, wherein the device information includes: a unique identifier of the terminal device, a device type, an operating system, and network information;

[0056] A device deregistration unit, configured to deregister the corresponding terminal device upon receiving a device deregistration instruction, wherein the triggering mode of the device deregistration instruction includes: a preset device deregistration button is triggered, and the terminal device has not communicated with the terminal software management platform for a long time;

[0057] The device status monitoring unit is used to monitor the status of each terminal device.

[0058] It can be understood that by setting the above-mentioned device registration unit, device deregistration unit, and device status monitoring unit, the registration, deregistration, and status monitoring of multiple terminal devices can be better realized, which facilitates the unified management of multiple terminal devices.

[0059] In some examples of this embodiment, the terminal device may be a test terminal device, etc.

[0060] In some embodiments, the platform further comprises:

[0061] The user management module 140 is used to create accounts and assign and manage permissions for the created accounts, wherein permission management includes: adding, deleting, and disabling permissions for the created accounts.

[0062] It can be understood that by setting up the user management module 140, it is possible to facilitate unified management of multiple users and organizations, greatly improving the convenience of user management.

[0063] In some embodiments, the platform further includes: a data recording module for storing software usage records of terminal devices and storing records of terminal devices accessing the terminal software management platform.

[0064] In some examples of this embodiment, the terminal software management platform includes a central database, a management server, and multiple client interfaces. The central database is used for data storage. The software management module 110, the authentication management module 120, the terminal management module 130, and the user management module 140 in the above embodiments are all integrated in the management server. The client interface is used to access external devices. The terminal software management platform can be deployed in a cloud server (such as a public cloud server or a private cloud server of an enterprise). In some embodiments, the above software usage records and terminal device records can be synchronized to the cloud server by data synchronization to facilitate subsequent query and management.

[0065] In some embodiments, during the data transmission process, the authentication management module uses a preset encryption protocol to encrypt the data to be transmitted, and sends the encrypted data to the target end.

[0066] In some examples of this embodiment, the encryption protocol may be a TLS (Transport Layer Security) protocol and a Kerberos protocol, etc.

[0067] It can be understood that by encrypting the data to be transmitted during the data transmission process, data leakage can be effectively prevented and the security of data transmission can be enhanced.

[0068] Figure 3 For an interactive logic diagram of a terminal software management platform provided in an embodiment of the present application, please refer to Figure 3 , Figure 3 The interactive relationship between the terminal software management platform, administrator, and user is demonstrated in an exemplary manner. Figure 3 User 1, user 2, and user 3 in the example above can use the corresponding terminal device (such as Figure 3 The administrator can manage multiple terminal devices, terminal software (multiple software included in the terminal software store), and users through the visual operation interface of the terminal software management platform (such as the web (network) interface). The terminal software management platform can authenticate and authorize each terminal device. Figure 3 The callback in it means callback, that is, sending a callback request, and return means return, that is, the terminal device returns the corresponding information based on the callback request to complete the identity authentication.

[0069] Figure 4 For a user management interface diagram of a terminal software management platform provided in an embodiment of the present application, please refer to Figure 4 In the user management interface, multiple search boxes can be set, such as user name, organization, authorization status, encryption options, and authorization time, etc., to facilitate user search. In addition, the user management interface can also visualize the corresponding information of each user, namely user name, organization, authorization status, encryption options, and authorization time. In addition, corresponding operation buttons can also be set in the user management interface, such as a configuration button (for configuring or modifying user information), a new authorization button, and an enable / disable button, etc., to facilitate the management of user permissions. Figure 4 The "User Management", "Organization Management", "Platform Management", and "Resource Management" on the left side represent the various visual management modules. It is worth mentioning that Figure 4 The detailed information shown in the above, such as Username21, first-level organization name / second-level organization name, encrypted CPU, and encrypted hard disk, are all exemplary information and have no actual meaning, so they will not be repeated here.

[0070] Figure 5 This is a schematic diagram of the organization management interface of the terminal software management platform provided in one embodiment of the present application. It can be understood that an organization may include multiple users. Figure 5 In the organization management interface, you can display relevant information about the organization (work set), such as the work set name, work set ID, work set creator, creation time, and work set status. The work set status can be normal or abnormal. In addition, you can set corresponding search boxes in the organization management interface, such as the work set name search box and status search box, to facilitate work set search. It should be mentioned that Figure 5 The detailed information shown in the article, such as the specific creation time, is only exemplary information and has no actual meaning, so it will not be repeated here.

[0071] Figure 6 For a schematic diagram of the platform (software) management interface of the terminal software management platform provided in one embodiment of the present application, please refer to Figure 6 , Figure 6 The platform name in refers to the software name. In the platform management interface, you can visualize information such as the platform name, platform number, version number, description information, status, and status update time. In addition, you can also configure corresponding operation buttons, such as configuration buttons, delete buttons, etc., to facilitate software configuration and deletion. In addition, you can also set corresponding search boxes in the platform management interface, such as platform name search box, status search box, etc., to facilitate software search. At the same time, you can also add a platform entry button to add new software. It should be mentioned that Figure 6 The detailed information shown in the figure, such as software 21 and the specific status update time, are all exemplary information and have no actual meaning, and will not be repeated here.

[0072] By setting up the terminal software management platform in the above embodiment, it is possible to better achieve unified management of multiple terminal software, better simplify the management process and difficulty, reduce management workload, and improve management efficiency. In addition, since the software, terminal, and users are integrated on the same platform for management, maintenance costs can be reduced. It is understandable that compared with maintaining multiple independent systems, the above-mentioned method of integrating software, terminals, and users on the same platform can greatly reduce maintenance costs. In addition, by setting up the above-mentioned visual operation interface, users can easily access and manage software, effectively improving user experience.

[0073] By adopting the above authentication mechanism, the information security of the platform can be greatly improved, and the risk of data leakage and illegal access can be reduced. By adopting the data synchronization mechanism, it is convenient for enterprises to conduct data analysis in a timely manner and provide decision support for enterprises. By deploying terminal software on the cloud platform, the high availability and scalability of the platform can be guaranteed, the stable operation of the platform can be ensured, and the risk of platform failure can be reduced.

[0074] By setting up the above-mentioned unified terminal software management platform, different departments and teams within the enterprise can facilitate software resource sharing and data sharing, which helps promote business collaboration and teamwork.

[0075] The terminal software management method provided by the present application is described below. The terminal software management method described below and the terminal software management platform described above can be referenced to each other.

[0076] Please refer to Figure 7 The terminal software management method provided in this embodiment includes:

[0077] S710: receiving a software access request transmitted by a terminal device, wherein the software access request includes: device authentication information, account authentication information, and a target key, wherein the target key is generated when a communication channel is first established between the terminal software management platform and the current terminal device;

[0078] S720: Performing authority verification on the terminal device based on the device authentication information, the account authentication information, and the target key;

[0079] S730: If the authority verification is passed, the terminal device is allowed to access one or more of the terminal software in the software management module. The terminal software management method in this embodiment can better realize the unified management of terminal software, facilitate the unified maintenance of multiple terminal software, and through the above authentication method, it can better improve the software information security, reduce information security risks, have low cost, and strong real-time performance.

[0080] It should be mentioned that the terminal software management method provided in the above embodiment is based on the terminal software management platform. Therefore, the specific manner in which each module and unit in the terminal software management platform performs operations belongs to the scope of the present method and will not be described in detail here. In addition, in actual application, the terminal software management platform provided in the above embodiment can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the system into different functional modules to complete all or part of the functions described above, and this is not limited here.

[0081] In some embodiments, an electronic device is also provided, which may be a server, and its internal structure is shown in FIG. Figure 8 As shown. The electronic device includes a processor, a memory, a network interface and a database connected via a system bus. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external client via a network connection. When the computer program is executed by the processor, the functions or steps on the server side of the above method are implemented.

[0082] In some embodiments, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program: receiving a software access request transmitted by a terminal device, the software access request comprising: device authentication information, account authentication information, and a target key, wherein the target key is generated when a terminal software management platform and a current terminal device establish a communication channel for the first time; performing authority verification on the terminal device based on the device authentication information, the account authentication information, and the target key; if the authority verification passes, allowing the terminal device to access one or more of the terminal software in the software management module.

[0083] In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: receiving a software access request transmitted by a terminal device, the software access request including: device authentication information, account authentication information, and a target key, wherein the target key is generated when a terminal software management platform and a current terminal device first establish a communication channel; based on the device authentication information, the account authentication information, and the target key, performing authority verification on the terminal device; if the authority verification passes, allowing the terminal device to access one or more of the terminal software in the software management module.

[0084] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or electronic device can refer to the relevant descriptions on the server side and the client side in the aforementioned method embodiment. To avoid repetition, they will not be described one by one here.

[0085] The flow chart and block diagram in the accompanying drawings illustrate the possible implementation architecture, function and operation of the method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0086] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A terminal software management platform, characterized in that: include: Software management module, used for visual display and management of multiple terminal software; An authentication management module, configured to receive a software access request transmitted by a terminal device, wherein the software access request includes: device authentication information, account authentication information, and a target key, wherein the target key is generated when the terminal software management platform and the current terminal device establish a communication channel for the first time; Based on the device authentication information, the account authentication information, and the target key, the terminal device is authenticated; if the authentication passes, the terminal device is allowed to access one or more terminal software in the software management module.

2. The terminal software management platform according to claim 1, characterized in that: The authentication management module is further used to receive an authentication request sent by a terminal device, wherein the authentication request includes the device authentication information and the account authentication information; Based on the device authentication information and the account authentication information, the terminal device is authenticated; if the identity authentication is successful, the target key is generated and fed back to the terminal device.

3. The terminal software management platform according to claim 2, characterized in that: The authentication management module is also used to periodically send a callback request to the terminal device according to a preset authentication information refresh frequency, wherein the callback request is used to instruct the terminal device to re-authenticate the identity; Receiving the device authentication information and the account authentication information returned by the terminal device; Identity authentication is re-performed based on the device authentication information and the account authentication information.

4. The terminal software management platform according to claim 1, characterized in that: Also includes: A terminal management module, the terminal management module comprising: The device registration unit is used to store the device information of the terminal device that has completed registration, wherein the device information includes: a unique identifier of the terminal device, a device type, an operating system, and network information; A device deregistration unit, configured to deregister the corresponding terminal device upon receiving a device deregistration instruction, wherein the triggering mode of the device deregistration instruction includes: a preset device deregistration button is triggered, and the terminal device has not communicated with the terminal software management platform for a long time; The device status monitoring unit is used to monitor the status of each terminal device.

5. The terminal software management platform according to any one of claims 1 to 4, characterized in that: Also includes: The user management module is used to create accounts and assign and manage permissions for the created accounts, wherein permission management includes: adding, deleting, and disabling permissions for the created accounts.

6. The terminal software management platform according to claim 1, characterized in that: Also includes: The data recording module is used to store the software usage records of the terminal equipment and to store the terminal equipment records accessing the terminal software management platform.

7. The terminal software management platform according to claim 1, characterized in that: During the data transmission process, the authentication management module adopts a preset encryption protocol to encrypt the data to be transmitted, and sends the encrypted data to the target end.

8. A terminal software management method based on the terminal software management platform according to any one of claims 1 to 7, characterized in that: include: Receiving a software access request transmitted by a terminal device, the software access request including: device authentication information, account authentication information, and a target key, wherein the target key is generated when a terminal software management platform and a current terminal device establish a communication channel for the first time; Based on the device authentication information, the account authentication information, and the target key, verify the authority of the terminal device; If the permission verification is passed, the terminal device is allowed to access one or more of the terminal software in the software management module.

9. An electronic device, characterized in that: It comprises a processor, a memory and a communication bus; the communication bus is used to connect the processor and the memory; the processor is used to execute the computer program stored in the memory to implement the terminal software management method as claimed in claim 8.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and the computer program is used to enable a computer to execute the terminal software management method as claimed in claim 8.

Citation Information

Patent Citations

  • File use processing method, terminal and server

    CN107979571A

  • Server access method and device, equipment and storage medium

    CN112822217A

  • Interface protection method and device, nonvolatile storage medium and computer equipment

    CN117473466A

  • Integrated portal software management system and method for construction project

    CN118552147A