An interface control method and device, electronic equipment and storage medium
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- CHINA FAW CO LTD
- Filing Date
- 2023-06-21
- Publication Date
- 2026-06-12
AI Technical Summary
Traditional JTAG interfaces have security issues during hardware debugging. Unauthorized users can easily repair fuses or rewiring by using simple methods, leading to security vulnerabilities in interface calls.
By obtaining the target user's information, user authentication and interface usage status are determined. Based on the authentication and usage status, the interface control method is determined. If the user is successfully authenticated and the interface is available, the interface is started; otherwise, a locking mechanism is implemented.
It improves the security of JTAG interface calls, prevents unauthorized users from calling the interface, and enhances the security of hardware debugging.
Smart Images
Figure CN116738394B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, and in particular to an interface control method, apparatus, electronic device, and storage medium. Background Technology
[0002] JTAG (Joint Test Action Group) is a universal international standard debugging protocol that is widely used in chip testing and system debugging.
[0003] Traditional manufacturers need to perform return component analysis, and typically retain the JTAG port after mass production to locate faults. Common protection methods include obfuscating JTAG traces on the circuit board or blowing fuses within the JTAG routing. However, for an unauthorized user with extensive hardware knowledge, these intentionally hidden vulnerabilities can often be fixed with a soldering iron, leading to significant security issues with the JTAG interface.
[0004] To solve the above problems, the interface control method of JTAG needs to be improved. Summary of the Invention
[0005] This invention provides an interface control method, device, electronic device, and storage medium to solve the problem of interface call security risks that exist in hardware interface repair methods.
[0006] In a first aspect, embodiments of the present invention provide an interface control method, including:
[0007] Upon receiving an interface call request, obtain the information to be used corresponding to the target user; wherein, the information to be used includes the user association information of the target user and the interface to be called corresponding to the target user;
[0008] The user authentication status of the target user is determined based on the user association information;
[0009] Based on the interface association information corresponding to the interface to be called, determine the usage status of the interface corresponding to the interface to be called;
[0010] Based on the user authentication status and the interface usage status, determine the interface control method corresponding to the interface to be called.
[0011] Secondly, embodiments of the present invention also provide an interface control device, comprising:
[0012] The information acquisition module is used to acquire, upon receiving an interface call request, the information to be used corresponding to the target user; wherein, the information to be used includes the user association information of the target user and the interface to be called corresponding to the target user;
[0013] The authentication status determination module is used to determine the user authentication status of the target user based on the user association information.
[0014] The usage status determination module is used to determine the usage status of the interface corresponding to the interface to be called based on the interface association information corresponding to the interface to be called.
[0015] The control mode determination module is used to determine the interface control mode corresponding to the interface to be called based on the user authentication status and the interface usage status.
[0016] Thirdly, embodiments of the present invention also provide an electronic device, comprising:
[0017] At least one processor; and
[0018] A memory communicatively connected to the at least one processor; wherein,
[0019] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the interface control method according to any embodiment of the present invention.
[0020] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions that are used to cause a processor to execute and implement the interface control method described in any embodiment of the present invention.
[0021] The technical solution of this invention, upon receiving an interface call request, obtains the user-related information corresponding to the target user, authenticates the target user based on the user association information in the user-related information, and determines the interface usage status of the interface to be called based on the interface association information in the user-related information. The user authentication status of the target user is determined based on the user association information; the interface usage status corresponding to the interface to be called is determined based on the interface association information; and the interface control method corresponding to the interface to be called is determined based on the user authentication status and the interface usage status. If the user authentication status is authenticated and the interface usage status is available, the interface to be called is started for interface debugging; if the user authentication status is unauthenticated or the interface usage status is unavailable, the interface to be called is locked. This solves the security risks of interface calls inherent in hardware-based interface repair methods. By authenticating the user and determining the interface usage status, the security of interface calls to the interface to be called is improved.
[0022] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description
[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0024] Figure 1 This is a flowchart of an interface control method provided according to Embodiment 1 of the present invention;
[0025] Figure 2 This is a flowchart of an interface control method provided according to Embodiment 2 of the present invention;
[0026] Figure 3 This is a schematic diagram of the structure of an interface control device according to Embodiment 3 of the present invention;
[0027] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the interface control method of the present invention. Detailed Implementation
[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0029] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in sequences other than those illustrated or described herein.
[0030] Before elaborating on this technical solution, a brief introduction to its application scenarios is provided to facilitate a clearer understanding. JTAG is a universal international standard debugging protocol widely used in chip testing and system debugging. JTAG has three main functions: first, as a programmer, it can download software to the memory chip; second, as a debugging tool, it is used to debug the Electronic Control Unit (ECU) to locate problems when they occur; and finally, it has a boundary scan function, which can be used to access the internal signal logic state of the chip and probe the state of the chip pins. Therefore, JTAG plays a very important role in the ECU development process. If debugging access to JTAG were granted to all users, it would inevitably create serious security risks.
[0031] In practical applications, traditional manufacturers, due to the need for return component analysis, typically retain the JTAG interface for location tracking after mass production. Currently, common methods for interface security protection include obfuscating JTAG traces on the circuit board or blowing fuses in the JTAG routing. However, users familiar with hardware operations can access the JTAG interface by repairing the traces or fuses, thus posing a significant security risk.
[0032] Example 1
[0033] Figure 1 The present invention provides a flowchart of an interface control method according to an embodiment of the present invention. This embodiment is applicable to situations where, based on the user's authentication status and interface usage status, it is determined whether an interface call can be made to the JTAG interface, and then the return item analysis is performed based on the JTAG interface. This method can be executed by an interface control device, which can be implemented in hardware and / or software, and can be configured in a computing device capable of executing the interface control method.
[0034] like Figure 1 As shown, the method includes:
[0035] S110. Upon receiving an interface call request, obtain the information to be used corresponding to the target user.
[0036] In this context, an interface call request can be understood as a request sent by a terminal device to invoke a JTAG interface when a target user needs to do so. The target user refers to the user who needs to invoke the JTAG interface. The information to be used includes the target user's user association information and the corresponding interface to be invoked, where the interface to be invoked can be understood as the JTAG interface to be called.
[0037] It should be noted that the target user may be an authorized user or an unauthorized user. However, in order to ensure the security of JTAG interface calls, the identity of the target user needs to be authenticated. Only when the target user is confirmed to be an authorized user can the target user be allowed to make interface calls.
[0038] Specifically, during response analysis, the target user needs to call the JTAG interface to locate problems in the response. In practice, the target user needs to initiate an interface call request through the terminal device. When the terminal device receives the interface call request, it can obtain the corresponding information for the target user based on the login information entered by the target user on the terminal device's login page, such as user association information and the interface to be called.
[0039] Optionally, obtaining the information to be used corresponding to the target user includes: parsing the interface call request according to the request application format corresponding to the interface call request to obtain the information to be used corresponding to the target user.
[0040] The request format can be understood as the data format corresponding to the interface call request. For example, the request format can be a message format.
[0041] Upon receiving an API call request, the request format is parsed using the corresponding parsing method to obtain the usage information for the target user. In other words, different parsing methods are required for API call requests with different request formats.
[0042] S120. Determine the user authentication status of the target user based on the user association information.
[0043] User-related information refers to the identity information associated with the target user, such as basic user attribute information. User authentication status can be used to indicate whether the target user is an authorized user. If the user authentication status is authenticated, it indicates that the target user is an authorized user and can call the interface to be called. If the user authentication status is unauthorized, it indicates that the target user is an unauthorized user and cannot call the interface to be called.
[0044] Optionally, the user authentication status of the target user is determined based on the user association information, including: generating authentication information based on the user association information and sending the authentication information to the target authentication system; receiving the authentication result from the target authentication system and determining the user authentication status of the target user based on the authentication result.
[0045] The information to be authenticated refers to the information used to authenticate the authorization status of the target user. For example, the information to be authenticated could be the target user's username, unique identification code, and contact information provided by the target user. The target authentication information can be understood as the system that authenticates the information to be authenticated; for example, the target authentication system includes a password authentication system and / or a key authentication system.
[0046] In practical applications, when a target user calls an API, the target authentication system needs to authenticate the target user's identity information to determine the user's authentication status. Specifically, the system obtains the information to be authenticated based on the target user's associated information and sends this information to the target authentication system. If the information to be authenticated matches the user verification information pre-stored in the target authentication system, the target user's authentication status is determined to be authenticated; otherwise, the target user's authentication status is determined to be unauthenticated.
[0047] S130. Determine the usage status of the interface corresponding to the interface to be called based on the interface association information.
[0048] The interface association information can be understood as information associated with the interface to be called, such as interface operation information, number of times the interface has been used, and duration of interface usage. The interface usage status can be used to characterize whether the interface to be called can be invoked. Interface usage status includes an available status and an unavailable status.
[0049] Specifically, the usage status of the interface to be called can be determined based on the interface association information. If the interface usage status is "available," it means that the interface to be called can be invoked by the target user, and thus, response analysis can be performed based on the interface to be called. Conversely, if the interface usage status is "unavailable," it means that the interface to be called cannot be invoked at the moment and cannot be accessed temporarily; consequently, response analysis cannot be performed based on the interface to be called.
[0050] S140. Based on the user authentication status and interface usage status, determine the interface control method corresponding to the interface to be called.
[0051] Specifically, based on the user authentication status and the interface usage status, the corresponding interface control method is determined, including: if the user authentication status is authenticated and the interface usage status is available, the interface to be called is started to perform interface debugging; if the user authentication status is unauthenticated or the interface usage status is unavailable, the interface to be called is locked.
[0052] In a specific example, during mass production, all JTAG interfaces related to the product are locked, for instance, with appropriate access permissions set. Further, the software flashing station requests a password from the product server and writes it to the storage area of the hardware secure storage module. The password is then backed up to the target authentication system of the product purchaser (i.e., the target user). This target authentication system can be a password authentication system and / or a key authentication system. When return file analysis is required, the target user can authenticate themselves by logging into the target authentication system. After successful authentication, the target authentication system authenticates the interface to be called. Further, if the user's authentication status is authenticated and the interface usage status is usable, the interface to be called can be invoked, and interface debugging can then be performed based on the interface. If the user's authentication status is unauthenticated or the interface usage status is unusable, the interface to be called is locked to ensure its security.
[0053] The technical solution of this invention, upon receiving an interface call request, obtains the user-related information corresponding to the target user, authenticates the target user based on the user association information in the user-related information, and determines the interface usage status of the interface to be called based on the interface association information in the user-related information. The user authentication status of the target user is determined based on the user association information; the interface usage status corresponding to the interface to be called is determined based on the interface association information; and the interface control method corresponding to the interface to be called is determined based on the user authentication status and the interface usage status. If the user authentication status is authenticated and the interface usage status is available, the interface to be called is started for interface debugging; if the user authentication status is unauthenticated or the interface usage status is unavailable, the interface to be called is locked. This solves the security risks of interface calls inherent in hardware-based interface repair methods. By authenticating the user and determining the interface usage status, the security of interface calls to the interface to be called is improved.
[0054] Example 2
[0055] Figure 2 The flowchart of an interface control method provided in Embodiment 2 of the present invention is shown. Optionally, the determination of the interface usage status corresponding to the interface to be called based on the interface association information corresponding to the interface to be called is further refined.
[0056] like Figure 2 As shown, the method includes:
[0057] S210. Upon receiving an interface call request, obtain the information to be used corresponding to the target user.
[0058] S220. Determine the user authentication status of the target user based on the user association information.
[0059] S230. Obtain the interface running information corresponding to the interface to be called, and determine the interface running status corresponding to the interface to be called based on the interface running information.
[0060] The interface's running status includes either an idle state or a busy state.
[0061] Optionally, if the interface is in an idle state, the interface to be called is determined to be in an available state; if the interface is in a busy state, the interface to be called is determined to be in an unavailable state.
[0062] In practical applications, to avoid excessive access to the interface to be called at the same time, the corresponding interface running status can be determined based on the interface's running information. If the interface to be called is currently being called by other users, or if the current access volume of the interface to be called is less than the preset access volume, then the interface running status is determined to be idle; otherwise, the interface running status is determined to be busy. If the interface running status is idle, the interface usage status of the interface to be called is determined to be available; if the interface running status is busy, the interface usage status of the interface to be called is determined to be unavailable.
[0063] Optionally, the interface association information is the number of times the interface is used. Based on the interface association information corresponding to the interface to be called, the usage status of the interface to be called is determined, including: obtaining the number of times the interface to be called is used; if the number of times the interface is used is less than the upper limit of the number of times the interface is used, the usage status of the interface is determined to be usable; if the number of times the interface is used is greater than or equal to the upper limit of the number of times the interface is used, the usage status of the interface is determined to be unusable.
[0064] Optionally, the interface association information is the interface usage duration. Based on the interface association information corresponding to the interface to be called, the usage status of the interface to be called is determined, including: obtaining the interface usage duration corresponding to the interface to be called; if the interface usage duration is less than the upper limit of interface usage duration, the interface usage status is determined to be usable; if the interface usage duration is greater than or equal to the upper limit of interface usage duration, the interface usage status is determined to be unusable.
[0065] S240. Based on the user authentication status and interface usage status, determine the interface control method corresponding to the interface to be called.
[0066] The technical solution of this invention, upon receiving an interface call request, obtains the user-related information corresponding to the target user, authenticates the target user based on the user association information in the user-related information, and determines the interface usage status of the interface to be called based on the interface association information in the user-related information. The user authentication status of the target user is determined based on the user association information; the interface usage status corresponding to the interface to be called is determined based on the interface association information; and the interface control method corresponding to the interface to be called is determined based on the user authentication status and the interface usage status. If the user authentication status is authenticated and the interface usage status is available, the interface to be called is started for interface debugging; if the user authentication status is unauthenticated or the interface usage status is unavailable, the interface to be called is locked. This solves the security risks of interface calls inherent in hardware-based interface repair methods. By authenticating the user and determining the interface usage status, the security of interface calls to the interface to be called is improved.
[0067] Example 3
[0068] Figure 3 This is a schematic diagram of an interface control device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: an information acquisition module 310, an authentication status determination module 320, a usage status determination module 330, and a control mode determination module 340.
[0069] The information acquisition module 310 is used to acquire the information to be used corresponding to the target user when receiving an interface call request; the information to be used includes the user association information of the target user and the interface to be called corresponding to the target user.
[0070] The authentication status determination module 320 is used to determine the user authentication status of the target user based on the user association information.
[0071] The usage status determination module 330 is used to determine the usage status of the interface corresponding to the interface to be called based on the interface association information corresponding to the interface to be called.
[0072] The control mode determination module 340 is used to determine the interface control mode corresponding to the interface to be called based on the user authentication status and interface usage status.
[0073] The technical solution of this invention, upon receiving an interface call request, obtains the user-related information corresponding to the target user, authenticates the target user based on the user association information in the user-related information, and determines the interface usage status of the interface to be called based on the interface association information in the user-related information. The user authentication status of the target user is determined based on the user association information; the interface usage status corresponding to the interface to be called is determined based on the interface association information; and the interface control method corresponding to the interface to be called is determined based on the user authentication status and the interface usage status. If the user authentication status is authenticated and the interface usage status is available, the interface to be called is started for interface debugging; if the user authentication status is unauthenticated or the interface usage status is unavailable, the interface to be called is locked. This solves the security risks of interface calls inherent in hardware-based interface repair methods. By authenticating the user and determining the interface usage status, the security of interface calls to the interface to be called is improved.
[0074] Optionally, an information acquisition module is used to parse the interface call request according to the request application format corresponding to the interface call request, and obtain the information to be used by the target user.
[0075] Optionally, the authentication status determination module includes: an information sending unit, used to generate authentication information based on user association information and send the authentication information to the target authentication system; wherein, the target authentication system includes a password authentication system and / or a key authentication system;
[0076] The authentication status determination unit is used to receive the information authentication result fed back by the target authentication system and determine the user authentication status of the target user based on the information authentication result.
[0077] Optionally, the usage status determination module includes: a running status determination unit, used to obtain the interface running information corresponding to the interface to be called, and determine the running status of the interface to be called based on the interface running information; wherein, the interface running status includes idle status or busy status;
[0078] The first state determination unit is used to determine that the interface to be called is in an available state if the interface running state is an idle state.
[0079] The second state determination unit is used to determine that the interface to be called is in an unusable state if the interface is in a busy state.
[0080] Optionally, the usage status determination module includes: a usage count determination unit, used to obtain the usage count of the interface corresponding to the interface to be called, where the interface association information is the number of times the interface is used;
[0081] The third state determination unit is used to determine the interface usage state as usable if the number of times the interface is used is less than the upper limit of the number of times the interface is used.
[0082] The fourth state determination unit is used to determine the interface usage state as unusable if the number of times the interface is used is greater than or equal to the upper limit of the number of times the interface can be used.
[0083] Optionally, the usage status determination module includes: a duration determination unit, used to obtain the usage duration of the interface corresponding to the interface to be called;
[0084] The fifth state determination unit is used to determine the interface usage state as usable if the interface usage time is less than the upper limit of interface usage time.
[0085] The sixth state determination unit is used to determine the interface usage state as unusable if the interface usage duration is greater than or equal to the upper limit of interface usage duration.
[0086] Optionally, the control method determination module includes: a startup unit, used to start the interface to be called if the user authentication status is authenticated and the interface usage status is available, so as to perform interface debugging on the interface to be called;
[0087] The locking unit is used to lock the interface to be called if the user authentication status is unauthenticated or the interface usage status is unusable.
[0088] The interface control device provided in the embodiments of the present invention can execute the interface control method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.
[0089] Example 4
[0090] Figure 4 A schematic diagram of the structure of an electronic device 10 according to an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0091] like Figure 4As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0092] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0093] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as interface control methods.
[0094] In some embodiments, the interface control method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the interface control method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the interface control method by any other suitable means (e.g., by means of firmware).
[0095] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0096] Computer programs used to implement the interface control method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.
[0097] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0098] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0099] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0100] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.
[0101] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.
[0102] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. An interface control method, characterized in that, include: Upon receiving an interface call request, obtain the information to be used corresponding to the target user; wherein, the information to be used includes the user association information of the target user and the interface to be called corresponding to the target user; The user authentication status of the target user is determined based on the user association information; Based on the interface association information corresponding to the interface to be called, determine the usage status of the interface corresponding to the interface to be called; Based on the user authentication status and the interface usage status, determine the interface control method corresponding to the interface to be called; Wherein, the interface association information is interface operation information. Determining the interface usage status corresponding to the interface to be called based on the interface association information includes: obtaining the interface operation information corresponding to the interface to be called, and determining the interface operation status corresponding to the interface to be called based on the interface operation information; wherein, the interface operation status includes an idle state or a busy state; if the interface operation status is the idle state, then the interface usage status of the interface to be called is determined to be an available state; if the interface operation status is the busy state, then the interface usage status of the interface to be called is determined to be an unavailable state; or Wherein, the interface association information is the number of times the interface is used. Determining the interface usage status based on the interface association information includes: obtaining the number of times the interface is used; if the number of times the interface is used is less than the upper limit of the number of times the interface can be used, then the interface usage status is determined to be usable; if the number of times the interface is used is greater than or equal to the upper limit of the number of times the interface can be used, then the interface usage status is determined to be unusable; or Wherein, the interface association information is the interface usage duration. The step of determining the interface usage status corresponding to the interface to be called based on the interface association information includes: obtaining the interface usage duration corresponding to the interface to be called; if the interface usage duration is less than the upper limit of interface usage duration, then the interface usage status is determined to be usable; if the interface usage duration is greater than or equal to the upper limit of interface usage duration, then the interface usage status is determined to be unusable. The step of determining the interface control method corresponding to the interface to be called based on the user authentication status and the interface usage status includes: if the user authentication status is authenticated and the interface usage status is available, then the interface to be called is started to perform interface debugging; if the user authentication status is unauthenticated or the interface usage status is unavailable, then the interface to be called is locked.
2. The method according to claim 1, characterized in that, The acquisition of the information to be used corresponding to the target user includes: Based on the request format corresponding to the interface call request, the interface call request is parsed to obtain the information to be used by the target user.
3. The method according to claim 1, characterized in that, Determining the user authentication status of the target user based on the user association information includes: Authentication information is generated based on the user association information, and the authentication information is sent to the target authentication system; wherein, the target authentication system includes a password authentication system and / or a key authentication system; Receive the authentication result from the target authentication system and determine the user authentication status of the target user based on the authentication result.
4. An interface control device, characterized in that, include: The information acquisition module is used to acquire, upon receiving an interface call request, the information to be used corresponding to the target user; wherein, the information to be used includes the user association information of the target user and the interface to be called corresponding to the target user; The authentication status determination module is used to determine the user authentication status of the target user based on the user association information. The usage status determination module is used to determine the usage status of the interface corresponding to the interface to be called based on the interface association information corresponding to the interface to be called. The control method determination module is used to determine the interface control method corresponding to the interface to be called based on the user authentication status and the interface usage status. The usage status determination module includes: a running status determination unit, used to obtain the interface running information corresponding to the interface to be called if the interface association information is interface running information, and determine the interface running status corresponding to the interface to be called based on the interface running information; wherein the interface running status includes an idle state or a busy state; a first status determination unit, used to determine that the interface usage status of the interface to be called is an available state if the interface running status is the idle state; and a second status determination unit, used to determine that the interface usage status of the interface to be called is an unavailable state if the interface running status is the busy state; or The usage status determination module includes: a usage count determination unit, used to obtain the usage count of the interface corresponding to the interface to be called, where the interface association information is the number of times the interface is used; a third status determination unit, used to determine that the interface usage status is usable if the number of times the interface is used is less than the upper limit of the number of times the interface is used; and a fourth status determination unit, used to determine that the interface usage status is unusable if the number of times the interface is used is greater than or equal to the upper limit of the number of times the interface is used; or The usage status determination module includes: a duration determination unit, used to obtain the interface usage duration corresponding to the interface to be called, where the interface association information is the interface usage duration; a fifth status determination unit, used to determine that the interface usage status is usable if the interface usage duration is less than the upper limit of interface usage duration; and a sixth status determination unit, used to determine that the interface usage status is unusable if the interface usage duration is greater than or equal to the upper limit of interface usage duration. The control method determination module includes: a startup unit, used to start the interface to be called for debugging if the user authentication status is authenticated and the interface usage status is available; and a locking unit, used to lock the interface to be called if the user authentication status is unauthenticated or the interface usage status is unusable.
5. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the interface control method according to any one of claims 1-3.
6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the interface control method according to any one of claims 1-3.