Software authorization detection method, equipment production method, chip and storage medium

Abstract

The present application discloses a software authorization detection method, a device production method, a chip, and a storage medium. The software authorization detection method includes: a target chip obtains authorization condition information and a non-unique identification attribute of the target chip, and the target chip is used to run the target software; the non-unique identification attribute is compared with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software. The above scheme can realize the authorization detection of the target software.

Description

Technical Field

[0001] The present application relates to the field of software technology, and in particular to a software authorization detection method, a device production method, a chip, and a storage medium. Background Art

[0002] It costs a lot for software developers to develop a software. As an important technical resource, software can be authorized for use to protect the rights and interests of software developers and prevent the software from being illegally copied or abused. However, how to implement software authorization detection has become an urgent problem to be solved. Summary of the invention

[0003] The present application at least provides a software authorization detection method, a device production method, a chip and a storage medium, which can detect whether the target software is authorized.

[0004] The present application provides a software authorization detection method, which is applied in the production process of a device provided with a target chip, and the method includes: the target chip obtains authorization condition information and a non-unique identification attribute of the target chip, and the target chip is used to run the target software; the non-unique identification attribute is compared with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software.

[0005] Among them, the authorization condition information includes an authorization time range, and the non-unique identification attribute includes time information of the target chip; comparing the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software includes: judging whether the time information of the target chip is within the authorization time range; in response to the time information being within the authorization time range, determining that the target chip meets the software authorization condition; in response to the time information not being within the authorization time range, determining that the target chip does not meet the software authorization condition.

[0006] The time information of the target chip is the manufacturing time of the target chip.

[0007] Wherein, obtaining the non-unique identification attribute of the target chip includes: reading the identification information of the target chip; and extracting the time information of the target chip from the identification information.

[0008] Among them, after comparing the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization conditions of the target software, the method also includes: in response to the target chip not meeting the software authorization conditions, after a preset time interval, restricting the target chip and / or restricting the target software running on the target chip.

[0009] The restricting of the target chip includes: controlling the target chip to enter a locked state.

[0010] The limiting of the target software running on the target chip includes at least one of the following: controlling the performance of the target software to be lower than the preset performance; disabling some functions of the target software; and limiting the running of the target software.

[0011] The limiting of the operation of the target software includes: in response to satisfying a trigger condition, controlling the target software to shut down or restart.

[0012] Wherein, obtaining the authorization condition information includes: reading the authorization condition information from the program file of the target software.

[0013] Wherein, the target chip is a microcontroller or a digital signal processing chip.

[0014] Among them, the target chip is used to be set on the air-conditioning circuit board, and the target software is the compressor driving software.

[0015] The present application provides a method for producing a device, on which a target chip is provided. The method comprises: writing a program file of a target software into the target chip; after the target chip is powered on, executing a software authorization detection method as described in any of the above items to implement authorization detection of the target software.

[0016] The present application provides a chip, including a memory and a processor, wherein the processor is used to execute program instructions stored in the memory to implement any of the above-mentioned software authorization detection methods.

[0017] The present application provides a computer-readable storage medium having program instructions stored thereon, and when the program instructions are executed by a processor, any of the above-mentioned software authorization detection methods is implemented.

[0018] In the above scheme, by comparing the non-unique identification attribute of the target chip with the authorization condition information, the authorization condition information can represent the software authorization condition, so as to determine whether the target chip meets the software authorization condition of the target software, thereby realizing authorization detection of the target software.

[0019] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.

[0021] Figure 1 This is a flowchart of an embodiment of the software authorization detection method of the present application;

[0022] Figure 2 It is a flowchart of another embodiment of the software authorization detection method of the present application;

[0023] Figure 3 It is a schematic diagram of a process of an embodiment of a method for producing the device of the present application;

[0024] Figure 4 It is a schematic diagram of the framework of a chip embodiment of the present application;

[0025] Figure 5 It is a schematic diagram of a framework of an embodiment of a computer-readable storage medium of the present application. DETAILED DESCRIPTION

[0026] The scheme of the embodiment of the present application is described in detail below in conjunction with the drawings of the specification.

[0027] In the following description, for the purpose of explanation rather than limitation, specific details such as specific subsystem structures, interfaces, and technologies are provided to facilitate a thorough understanding of the present application.

[0028] The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there may be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. In addition, "many" in this article means two or more than two. In addition, the term "at least one" in this article means any combination of at least two of any one or more of a plurality of, for example, including at least one of A, B, and C, can mean including any one or more elements selected from the set consisting of A, B, and C.

[0029] See also Figure 1 , Figure 1 It is a flowchart of an embodiment of the software authorization detection method of the present application. It should be noted that the software authorization detection method provided by the present application can be executed by the target chip, the target chip can be used to run the target software, and the software authorization detection method can be used to determine whether the target software is authorized. Specifically, the software authorization detection method provided by the present application can be used in the production process of a device provided with a target chip, and before the device leaves the factory, the target chip used to run the target software set in the device is subjected to authorization detection.

[0030] Specifically, the method may include:

[0031] Step S110: Obtain authorization condition information.

[0032] Step S120: Acquire the non-unique identification attribute of the target chip.

[0033] It should be noted that the execution order of step S110 and step S120 is not limited and can be set according to actual application needs.

[0034] The non-unique identification attribute may be an attribute of the target chip related to the authorization of the target software, and the attribute is not used to uniquely identify the chip, and different chips may have the same non-unique identification attribute. The authorization condition information may indicate the authorization condition of the target software, and may be pre-set.

[0035] It should be noted that the software authorization conditions of the target software may be restriction conditions on non-unique identification attributes, so that the authorization condition information is compared with the non-unique identification attributes of the target chip to determine whether the target chip meets the software authorization conditions of the target software.

[0036] Step S130: Compare the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software.

[0037] The authorization condition information may indicate the authorization condition of the target software, and the non-unique identification attribute is an attribute of the target chip that is related to the authorization of the target software. By comparing the non-unique identification attribute with the authorization condition information, it can be determined whether the target chip meets the software authorization condition of the target software or does not meet the software authorization condition. Meeting the software authorization condition may indicate that the software has valid authorization, and not meeting the software authorization condition may indicate that the software does not have valid authorization.

[0038] In the above method, by comparing the non-unique identification attribute of the target chip with the authorization condition information, the authorization condition information can represent the software authorization condition, so as to determine whether the target chip meets the software authorization condition of the target software, thereby realizing the detection of software authorization in the target chip.

[0039] Furthermore, the method can be applied to the production process of a device provided with a target chip. The non-unique identification attribute of the chip is used to determine whether the software authorization conditions are met. Since there is no need to use the unique identification information of the chip as a judgment standard, there is no need to obtain the unique identification information of each chip one by one during the production stage, and determine the judgment standard for each chip one by one, which greatly simplifies the production process and reduces production costs.

[0040] In some embodiments, if the target chip meets the software authorization conditions of the target software, indicating that it has valid authorization, the target chip can subsequently run the target software normally.

[0041] In some embodiments, if the target chip does not meet the software authorization conditions of the target software, it means that the target software on this target chip does not have valid authorization, and corresponding restriction measures can be executed to limit the operation of the target software, thereby protecting the software from unauthorized abuse.

[0042] It is understandable that the authorization condition information is information corresponding to the non-unique attribute of the chip. In some embodiments, the authorization condition information includes the authorization time range. The non-unique identification attribute includes the time information of the target chip.

[0043] Further, comparing the two to determine whether the target chip meets the software authorization conditions of the target software may include: judging whether the time information of the target chip is within the authorized time range, and in response to the time information being within the authorized time range, determining that the target chip meets the software authorization conditions; and in response to the time information not being within the authorized time range, determining that the target chip does not meet the software authorization conditions.

[0044] It should be noted that there may be a corresponding relationship between the authorization condition information and the non-unique identification attribute used to determine whether the software is effectively authorized. For example, in the previous example, both are related to time. The authorization condition information and the non-unique identification attribute can be set according to actual application needs, and may not be limited to the information related to time mentioned in the above embodiment, for example, it may also be information related to the chip model, etc.

[0045] In a specific application scenario, the time information of the target chip may be the manufacturing time of the target chip.

[0046] In some embodiments, the non-unique identification attribute of the target chip can be obtained by reading.

[0047] In an implementation scenario, the non-unique identification attribute of the target chip can be obtained through the following steps: reading the identification information of the target chip, and extracting the time information of the target chip from the identification information.

[0048] In a specific application scenario, a universally unique identifier (UUID) of a target chip is read, and the manufacturing time of the target chip, specifically the manufacturing date, is extracted from the universally unique identifier.

[0049] It can be understood that the above method of obtaining the non-unique identification attribute is only an example, and can be specifically set according to actual application needs.

[0050] In a specific application scenario, the manufacturing time of the target chip is obtained, and the preset authorization time range is obtained to determine whether the manufacturing time is within the authorization time range, so as to determine whether the target chip meets the software authorization conditions of the target software.

[0051] Exemplarily, the authorization time range may be up to December 31, 2024, so chips manufactured on or before December 31, 2024 meet the software authorization conditions.

[0052] In some embodiments, the authorization condition information may include other information in addition to the authorization time range. Accordingly, the corresponding information of the target chip may be obtained to determine whether the software authorization condition is met.

[0053] See also Figure 2 , Figure 2 This is a flow chart of another embodiment of the software authorization detection method of the present application. Specifically, the method may include:

[0054] Step S210: Acquire the non-unique identification attribute of the target chip.

[0055] Step S220: Obtain authorization condition information.

[0056] The authorization condition information may be preset. In some embodiments, the authorization condition information may be fixed in the program file of the target software, and the authorization condition information may be read from the program file of the target software.

[0057] In a specific application scenario, the program file of the target software may include an authorization detection module and a software module, wherein the software module may correspond to the target software, and the authorization detection module may be used to implement the software authorization detection method provided in this application.

[0058] Since the authorization condition information is solidified in the program file of the target software, the target chip can read the authorization condition information and non-unique identification attributes by itself after it is powered on, and this acquisition process does not involve other devices. During the equipment production process, the user does not need to perform additional steps for software authorization detection, and the authorization detection can be achieved without the user's perception, thereby reducing the risk of the software being cracked. For example, in some prior arts, during the production process, it is necessary to write the authorization judgment information into other storage devices outside the target chip. In this application, there is no need to use other storage devices, nor is there any need to write the authorization condition information into other storage devices, which simplifies the production steps and reduces production costs.

[0059] In some embodiments, the software authorization conditions of the target software can be changed. For example, the authorization deadline is changed from 2024 to 2025. The authorization condition information can represent the software authorization condition. By changing the authorization condition information, the updated software authorization condition can be used to perform software authorization detection. For example, the authorization condition information includes December 31, 2024, and December 31, 2025 is used to replace December 31, 2024, thereby achieving an extension of the authorization.

[0060] In some embodiments, the target chip may be a microcontroller unit (MCU). In some embodiments, the target chip may be a digital signal processing (DSP) chip.

[0061] In a specific application scenario, the target chip is used to be set on an air conditioner circuit board, which can be used to run the compressor driver software as the target software. Of course, the target software is not limited to the above examples, and can be set according to the actual application needs. The target chip can also be set on other devices, including but not limited to power supplies, inverters, etc., and can be set according to the actual application needs.

[0062] Step S230: Compare the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software.

[0063] For the related description of step S210 to step S230, reference may be made to the related contents in the aforementioned embodiments.

[0064] In some cases, if the target chip meets the software authorization conditions of the target software, no restrictions will be imposed on the target software of the target chip, and the operation of the target software will not be affected during subsequent use. In some cases, if the target chip does not meet the software authorization conditions of the target software, indicating that it does not have a valid authorization, restrictions may be imposed on the target chip and / or the target software running on the target chip may be restricted.

[0065] Step S240: In response to the target chip not satisfying the software authorization condition, after a preset time interval, executing restriction measures for the target chip and / or restriction measures for the target software running on the target chip.

[0066] The restriction measures may be executed after a preset time interval. For target software without valid authorization, restrictions may still be implemented even after a certain period of time.

[0067] If the target chip does not meet the software authorization conditions, the target software does not have a valid authorization, and the target software can be restricted. Specifically, the restriction on the target software can be achieved by restricting the target software itself and / or the hardware where the target software is located.

[0068] The restriction on the target software by restricting the hardware where the target software is located may be to restrict the target chip.

[0069] The target chip may be arranged on a circuit board, which may be a circuit board of an electronic device. The operation performed by the target chip may affect the operation of the circuit board and even the electronic device.

[0070] The measures to restrict the target chip can be set according to the actual application needs. The specific restrictive measures can be diversified, and the corresponding restriction results can also be diversified. For example, the scope of influence brought by the restrictive measures can be set according to the needs, which can affect the work of the target chip, the work of the circuit board where it is located, or the work of the device where it is located. For another example, the degree of influence brought by the restrictive measures can also be diversified, which can be to weaken the performance, affect some functions, or restrict the use, etc.

[0071] In some embodiments, restricting the target chip may include: controlling the target chip to enter a locked state.

[0072] In some cases, after the target chip enters the locked state, it needs to be re-burned. In some cases, after the target chip enters the locked state, the chip can no longer be used and needs to be replaced with a new chip.

[0073] In a specific application scenario, the target chip can be controlled to enter a secure locking state.

[0074] In a specific application scenario, the target chip can be encrypted and locked.

[0075] In some embodiments, limiting the target software running on the target chip may include at least one of the following: controlling the performance of the target software to be lower than a preset performance, disabling some functions of the target software, and limiting the operation of the target software.

[0076] It is understandable that the software can be restricted from three aspects: software performance, software functions and software operation. For example, the software can be restricted by reducing the performance of the software, or by disabling some functions of the software.

[0077] In some embodiments, limiting the operation of the target software may include: controlling the target software to shut down or restart.

[0078] In a specific application scenario, the target software is compressor driver software, and the target chip is used to be set on an air-conditioning circuit board. Shutting down or restarting the target software will cause the air-conditioning to shut down or restart.

[0079] In some embodiments, after a preset time interval, the step of restricting the target chip or restricting the target software may be further subject to a trigger condition. Exemplarily, the trigger condition may be related to the running time of the target software. In some cases, the trigger condition may be randomly generated, for example, after the running time of the target software reaches a randomly generated time, the execution of the restriction measure is triggered. In some cases, some restriction measures may be repeatedly executed, so multiple trigger conditions may be set for the restriction measures that can be repeatedly executed. Exemplarily, the trigger condition may include multiple successively increasing running times, etc.

[0080] In a specific application scenario, limiting the operation of the target software may include, in response to satisfying a trigger condition, controlling the target software to shut down or restart.

[0081] It should be noted that the software authorization detection method provided in this application can be executed each time the target chip is powered on. In one implementation scenario, during the device production process, the device needs to be tested, at which time the target chip is powered on and the relevant steps of the software authorization detection method can be executed.

[0082] In some embodiments, the target software is in the form of a software library.

[0083] In a specific application scenario, after the target chip is powered on and the software library is loaded, the relevant steps of the software authorization detection method can be executed.

[0084] See also Figure 3 , Figure 3 1 is a flow chart of an embodiment of the device production method of the present application. A target chip is provided on the device. Specifically, the method may include:

[0085] Step S310: Write the program file of the target software into the target chip.

[0086] During the device production process, the program file of the target software needs to be written into the target chip, wherein the program file of the target software may include an authorization detection module and a software module, wherein the software module may correspond to the target software, and the authorization detection module may be used to implement the software authorization detection method provided in this application. Thus, the target chip can implement software authorization detection and run the target software.

[0087] During the device production process, the target chip is powered on. After powering on, the target chip can execute the steps of the software authorization detection method to implement authorization detection of the target software. Specifically, the target chip can execute steps S320-S340. The relevant description of steps S320-S340 can refer to the relevant content in the above embodiment.

[0088] In a specific application scenario, during the equipment production process, a test will be carried out before leaving the factory. During the test, the target chip will be powered on and the software authorization detection method will be executed to determine whether the target software has valid authorization.

[0089] It should be noted that the program file of the target software has been written into the target chip. In the subsequent use process, the software authorization detection can be performed each time the target chip is powered on.

[0090] In some embodiments, the target chip may be a microcontroller unit (MCU). In some embodiments, the target chip may be a digital signal processing (DSP) chip.

[0091] After the target chip is powered on, steps S320 to S340 are executed. The execution order of steps S320 and S330 is not limited and can be set according to actual needs.

[0092] Step S320: The target chip obtains a non-unique identification attribute of the target chip.

[0093] Step S330: The target chip obtains authorization condition information.

[0094] Step S340: The target chip compares the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software.

[0095] In a specific application scenario, the UUID of the MCU is read from the register or specific storage area inside the MCU, and then the manufacturing date information of the MCU is analyzed. The authorized date information can be set by the software provider when the software library is released and stored inside the software library. The manufacturing date information is compared with the authorized date information to determine whether the target chip meets the software authorization conditions of the target software.

[0096] In some embodiments, if the target chip does not meet the software authorization conditions of the target software, then the target chip and / or the target software running on the target chip may be restricted. Furthermore, the restriction measures may be executed after a preset time interval.

[0097] In a specific application scenario, the device provided with the target chip may be an air conditioner electronic control board.

[0098] In a specific application scenario, the device provided with the target chip may be an air conditioner, and the target software may be compressor driver software.

[0099] In some existing embedded software authorization detection schemes, the unique identification information of the chip is used as information for authorization judgment in the process of determining whether it is authorized. During the device production process, since the unique identification information of each chip is different, it is necessary to first obtain the unique identification information of the chip, and then determine the authorization condition information of each chip one by one according to the unique identification information, so as to be used for the subsequent software authorization detection.

[0100] In the above scheme, whether the software has valid authorization is determined based on the authorization condition information, which is related to the non-unique identification attribute. Compared with the unique identification attribute, the use of non-unique identification attributes to participate in authorization detection does not require the acquisition of the unique identification information of each chip, and the generation of authorization condition information one by one, which greatly simplifies the device production process and reduces production costs.

[0101] In some embodiments, the authorization condition information may be pre-written into a program file of the target software and may be directly read.

[0102] During the device production process, users do not need to perform additional steps for software authorization detection. After the program file of the target software is written into the chip, the chip can automatically complete the authorization detection when it is powered on, and the authorization detection can be realized without the user's perception. For example, in some prior arts, during the production process, it is necessary to write the information for determining authorization into other storage devices other than the target chip. In this application, there is no need to use other storage devices, nor is there any need to write the authorization condition information into other storage devices, which simplifies the production steps and reduces the production cost.

[0103] See also Figure 4 , Figure 4 It is a schematic diagram of the framework of a chip embodiment of the present application.

[0104] In this embodiment, the chip 40 includes a memory 41 and a processor 42. The processor 42 is used to execute program instructions stored in the memory 41 to implement any of the above-mentioned software authorization detection methods.

[0105] Specifically, the processor 42 is used to control itself and the memory 41 to implement any of the above-mentioned software authorization detection methods.

[0106] See also Figure 5 , Figure 5 It is a schematic diagram of a framework of an embodiment of a computer-readable storage medium of the present application.

[0107] The computer-readable storage medium 50 provided in this embodiment stores program instructions 51 that can be executed by a processor. When the program instructions 51 are executed by the processor, they are used to implement any of the above-mentioned software authorization detection methods.

[0108] The description of each embodiment above tends to emphasize the differences between the embodiments, and the same or similar aspects can be referenced to each other. For the sake of brevity, this article will not repeat them. Different embodiments can be combined with each other on the basis of no contradiction or conflict.

[0109] In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only schematic. For example, the division of modules or units is only a logical function division. There may be other division methods in actual implementation, such as units or components can be combined or integrated into another subsystem, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0110] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

Claims

1. A software authorization detection method, characterized in that: The method is applied in a production process of a device provided with a target chip, and the method comprises: The target chip reads authorization condition information from a program file of the target software, and obtains a non-unique identification attribute of the target chip, the target chip is used to run the target software, the authorization condition information indicates a software authorization condition of the target software, and the authorization condition information is a restriction condition on the non-unique identification attribute; Compare the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software, if the software authorization condition is met, the target chip is authorized, and if the software authorization condition is not met, the target chip is not authorized; In response to the target chip not satisfying the software authorization condition, after a preset time interval, restricting the target software running on the target chip; wherein, restricting the target software running on the target chip includes controlling the target software to be shut down or restarted in response to satisfying a trigger condition, wherein the trigger condition includes the target software running for a preset time period, and the number of the preset time periods is one or more; The new authorization condition information is obtained, and the current authorization condition information in the program file is updated using the new authorization condition information.

2. The method according to claim 1, characterized in that The authorization condition information includes an authorization time range, and the non-unique identification attribute includes time information of the target chip; and comparing the non-unique identification attribute with the authorization condition information to determine whether the target chip satisfies the software authorization condition of the target software includes: Determining whether the time information of the target chip is within the authorized time range; In response to the time information being within the authorization time range, determining that the target chip meets the software authorization condition; In response to the time information not being within the authorization time range, it is determined that the target chip does not satisfy the software authorization condition.

3. The method according to claim 2, characterized in that The time information of the target chip is the manufacturing time of the target chip; and / or, The obtaining of the non-unique identification attribute of the target chip comprises: Reading identification information of the target chip; The time information of the target chip is extracted from the identification information.

4. The method according to claim 1, characterized in that: After comparing the non-unique identification attribute with the authorization condition information to determine whether the target chip meets the software authorization condition of the target software, the method further includes: In response to the target chip not satisfying the software authorization condition, the target chip is restricted after the preset time interval.

5. The method according to claim 4, characterized in that The limiting the target chip comprises: Controlling the target chip to enter a locked state; The limiting of the target software running on the target chip also includes at least one of the following: Controlling the performance of the target software to be lower than a preset performance; Disable some functions of the target software.

6. The method according to claim 1, characterized in that The target chip is a microcontroller or a digital signal processing chip; and / or, The target chip is used to be arranged on an air conditioner circuit board, and the target software is compressor driving software.

7. A method for producing a device, characterized in that: The device is provided with a target chip, and the method comprises: Writing the program file of the target software into the target chip; After the target chip is powered on, the software authorization detection method according to any one of claims 1 to 6 is executed to implement authorization detection of the target software.

8. A chip, characterized in that: The method comprises a memory and a processor, wherein the memory stores program instructions, and when the program instructions are executed by the processor, the method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium having program instructions stored thereon, characterized in that: When the program instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images