A method, apparatus, device, and readable storage medium for verifying non-empty data.

Abstract

The present invention provides a data non-empty check method, device, equipment and readable storage medium, which relates to the field of computer technology, including obtaining first information, wherein the first information includes at least one parameter entity information filled in on a terminal, and the parameter entity information includes at least two field names and a value attribute corresponding to the field name; traversing the annotations of all the field names according to a first preset annotation to obtain the existence status of the first preset annotation, and the existence status includes existence or non-existence; when the existence status is existence, the existence status triggers calling a non-empty check interceptor to perform a non-empty check on the first information. The present invention implements non-empty check by means of interceptor + annotation, improves development efficiency, reduces the amount of code, and distinguishes scenarios according to the parameter value to implement a flexible non-empty check method.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a data non-null check method, device, equipment and readable storage medium. Background Art

[0002] Spring group verification technology: first define multiple group interfaces, then add NotNull annotations to the fields that need to be non-null checked, and use the groups parameter to specify in which groups the field cannot be empty. Finally, set the @Validated annotation in the method signature that uses the parameter, and use the parameter to specify which group the current interface belongs to. The above non-null verification method cannot achieve the purpose of scenario-based verification during code development. Summary of the invention

[0003] The purpose of the present invention is to provide a data non-empty check method, device, equipment and readable storage medium to improve the above-mentioned problem. In order to achieve the above-mentioned purpose, the technical solution adopted by the present invention is as follows:

[0004] In a first aspect, the present application provides a method for checking data is not empty, comprising: obtaining first information, the first information comprising at least one filled-in parameter entity information, the parameter entity information comprising at least one field name and a value attribute corresponding to the field name; traversing all annotations of the field name according to a first preset annotation to obtain an existence status of the first preset annotation, the existence status comprising existence or non-existence; when the existence status is existence, the existence status triggers a call to a non-empty check interceptor to perform a non-empty check on the first information.

[0005] Furthermore, the existence status triggers the calling of a non-empty check interceptor to perform a non-empty check on the first information, including: calculating the second information based on the first information, the second information including the first verification scenario; traversing the value attributes corresponding to each of the field names in the first information, and performing a non-empty check based on the second information to obtain the third information, the third information including the field name that failed the check, the field name that failed the check being the field name that failed the check.

[0006] Furthermore, the second information is calculated based on the first information, and the second information includes a first verification scenario, including: obtaining and parsing a first preset scenario calculation function to obtain a function variable set, and the function variable set includes at least one parameter name; extracting fourth information from the first information according to the parameter name, and the fourth information includes a value attribute corresponding to the parameter name; and calculating the first verification scenario according to the first preset scenario calculation function and the fourth information.

[0007] Further, the traversal of the value attribute corresponding to each field name in the first information, and performing non-empty check based on the second information to obtain at least one field name that failed, includes: judging the annotation content of the field name, if the field name is not annotated by the first preset annotation, judging the annotation content of the next field name; if the field name is annotated by the first preset annotation, judging whether the value attribute corresponding to the field name is empty, if the value attribute corresponding to the field name is not empty, judging the annotation content of the next field name; if the value attribute corresponding to the field name is empty, judging whether the value attribute corresponding to the first preset annotation is empty, if the value attribute corresponding to the first preset annotation is empty, then recording the field name as a failed field name; if the value attribute corresponding to the first preset annotation is not empty, judging whether the value attribute corresponding to the first preset annotation contains a first verification scenario, if the value attribute corresponding to the first preset annotation contains the first verification scenario, then recording the field name as a failed field name.

[0008] Furthermore, the recording of the field name as a failed field name also includes: if there is a failed field name, sending a first control command and re-acquiring the first information, the first control command includes a command to control the display to display that the failed field name cannot be empty.

[0009] In the second aspect, the present application also provides a data non-empty verification device, including: a first acquisition unit, used to obtain first information, the first information includes at least one filled-in parameter entity information, the parameter entity information includes at least one field name and a value attribute corresponding to the field name; a first identification unit, used to traverse all annotations of the field name according to a first preset annotation to obtain the existence status of the first preset annotation, the existence status includes existence or non-existence; a trigger execution unit, used for when the existence status is existence, the existence status triggers the call of a non-empty verification interceptor to perform a non-empty verification on the first information.

[0010] Furthermore, the trigger execution unit includes: a first calculation unit, used to calculate second information based on the first information, the second information including a first verification scenario; a verification unit, used to traverse the value attributes corresponding to each of the field names in the first information, and perform non-empty verification based on the second information to obtain third information, the third information including failed field names, and the failed field names are the field names that failed the verification.

[0011] Furthermore, the first calculation unit includes: a parsing unit, used to obtain and parse the first preset scenario calculation function to obtain a function variable set, wherein the function variable set includes at least one parameter name; an extraction unit, used to extract fourth information from the first information according to the parameter name, wherein the fourth information includes a value attribute corresponding to the parameter name; and a second calculation unit, used to calculate the first verification scenario according to the first preset scenario calculation function and the fourth information.

[0012] Further, the verification unit includes: a first logic unit, used to determine the annotation content of the field name, if the field name is not annotated by the first preset annotation, then determine the annotation content of the next field name; a second logic unit, used to determine whether the value attribute corresponding to the field name is empty if the field name is annotated by the first preset annotation, if the value attribute corresponding to the field name is not empty, then determine the annotation content of the next field name; a third logic unit, used to determine whether the value attribute corresponding to the first preset annotation is empty if the value attribute corresponding to the field name is empty, if the value attribute corresponding to the first preset annotation is empty, then record the field name as a failed field name; a fourth logic unit, used to determine whether the value attribute corresponding to the first preset annotation contains a first verification scenario if the value attribute corresponding to the first preset annotation is not empty, if the value attribute corresponding to the first preset annotation contains the first verification scenario, then record the field name as a failed field name.

[0013] Furthermore, the verification unit also includes: a sixth logic unit, which is used to send a first control command and re-acquire the first information if there is a failed field name, and the first control command includes a command to control the display to display that the failed field name cannot be empty.

[0014] In a third aspect, the present application also provides a data non-empty check device, including:

[0015] Memory for storing computer programs;

[0016] A processor is used to implement the steps of the data non-empty verification method when executing the computer program.

[0017] In a fourth aspect, the present application further provides a readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned data non-empty check method are implemented.

[0018] The beneficial effects of the present invention are:

[0019] The present invention implements non-null check by means of interceptor + annotation, improves development efficiency, reduces the amount of code, and distinguishes scenarios according to parameter values ​​to implement a flexible non-null check method.

[0020] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or be understood by implementing the embodiments of the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 This is a flow chart of the data non-empty verification method described in Embodiment 1 of the present invention;

[0023] Figure 2 This is a schematic diagram of the structure of the data non-empty verification device described in Example 2 of the present invention;

[0024] Figure 3 This is a schematic diagram of the structure of the data non-empty verification device described in Example 3 of the present invention. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all of the embodiments. The components of the embodiments of the present invention generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed invention, but merely represents selected embodiments of the present invention. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0026] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0027] Embodiment 1:

[0028] This embodiment provides a method for checking whether data is not empty.

[0029] See also Figure 1 , the figure shows that the method includes step S100, step S200 and step S300.

[0030] S100. Acquire first information, where the first information includes at least one filled-in parameter entity information, and the parameter entity information includes at least one field name and a value attribute corresponding to the field name.

[0031] It should be noted that in this application, the first information source can be information transmitted from a terminal through an interface, or information transmitted from another server through an interface. The terminal can be a mobile phone, a personal computer, or other counter service terminal, and this application does not make specific restrictions.

[0032] S200. Traverse the annotations of all field names according to the first preset annotation to obtain the existence status of the first preset annotation, where the existence status includes existence or non-existence.

[0033] S300: When the existence status is existence, the existence status triggers calling a non-empty check interceptor to perform a non-empty check on the first information.

[0034] In this method, the verification is enabled by the existence of the first preset annotation, which is different from the prior art that relies on dividing the scenarios according to the interface used by the parameter object. It is more convenient in the code development stage and effectively reduces the amount of code.

[0035] It should be noted that in this method, SceneAbleNotNull is used as the first preset annotation, and the non-null check interceptor can be implemented through springAOP.

[0036] Furthermore, in some specific embodiments, step S300 includes step S310 and step S320.

[0037] S310. Calculate and obtain second information according to the first information, where the second information includes a first verification scenario.

[0038] S320, traverse the value attribute corresponding to each field name in the first information, and perform non-empty check based on the second information to obtain third information, the third information includes the failed field name, and the failed field name is the field name that failed the check.

[0039] In the present application, after checking the SceneAbleNotNull annotation, the first verification scene is calculated by the first verification scene calculation method defined on the interface, so as to achieve the purpose of distinguishing the verification scenes according to the parameter values.

[0040] In some specific embodiments, step S310 includes step S311, step S312 and step S313 to implement the first verification scenario verification.

[0041] S311, acquiring and parsing a first preset scenario computing function to obtain a function variable set, where the function variable set includes at least one parameter name;

[0042] S312: extract the fourth information from the first information according to the parameter name, where the fourth information includes a value attribute corresponding to the parameter name;

[0043] S313: Calculate a first verification scenario according to the first preset scenario calculation function and the third information.

[0044] For the sake of convenience, an example is given in this application. First, a getScene method is defined. The definition of the method is common knowledge in the field and will not be repeated in this application.

[0045] In the defined getScene method, the specific function is: {if (age! = null && age> = 18) return "adult"; else return "minor"}, where age is the parameter name mentioned above, and the current scene can be calculated by calling the value attribute corresponding to age in the getScene method. At the same time, it should be noted that for technical personnel in this field, multiple verification scenes can also be set at the same code layer to complete the data verification requirements.

[0046] In some specific embodiments, step S320 includes step S321, step S322, step S313 and step S314 to implement data verification in the first verification scenario.

[0047] S321. Determine the annotation content of the field name. If the field name is not annotated by the first preset annotation, determine the annotation content of the next field name.

[0048] S322. If the field name is annotated by the first preset annotation, determine whether the value attribute corresponding to the field name is empty; if the value attribute corresponding to the field name is not empty, determine the annotation content of the next field name.

[0049] S323. If the value attribute corresponding to the field name is empty, determine whether the value attribute corresponding to the first preset annotation is empty. If the value attribute corresponding to the first preset annotation is empty, record the field name as a failed field name. S324. If the value attribute corresponding to the first preset annotation is not empty, determine whether the value attribute corresponding to the first preset annotation includes a first validation scenario. If the value attribute corresponding to the first preset annotation includes the first validation scenario, record the field name as a failed field name.

[0050] In this method, first traverse each field name to see which one is marked by SceneAbleNotNull, and then determine whether SceneAbleNotNull is empty. If SceneAbleNotNull is empty, it means that no matter what verification scene it is, it needs to be checked for non-empty. When there is a specific verification scene in SceneAbleNotNull, call SceneAbleNotNull to see if the verification scene is included in the second information. If the value attribute of the field name is empty and the verification scene is in the second information, the non-empty check is hit. For example: ID@SceneAbleNotNull ("Adult", "Chinese"), it needs to be checked when the current scene is adult or Chinese.

[0051] In this step, when the above method is used, non-empty checks can be performed on multiple scenes at the same time, and when non-empty checks are performed in the above manner, the amount of code development can be effectively reduced.

[0052] Meanwhile, in some specific embodiments, step S320 also includes step S329.

[0053] S329: If there is a failed field name, send a first control command and reacquire the first information, the first control command including a command to control the display to display that the failed field name cannot be empty.

[0054] In this method, for those field names that are checked to be empty, the terminal user is prompted to fill in the relevant information to complete the data entry.

[0055] Embodiment 2:

[0056] like Figure 2 As shown, this embodiment provides a data non-empty verification device, the device comprising:

[0057] The first acquisition unit 1 is used to acquire first information, where the first information includes at least one filled-in parameter entity information, and the parameter entity information includes at least one field name and a value attribute corresponding to the field name.

[0058] The first identification unit 2 is used to traverse the annotations of all field names according to the first preset annotation to obtain the existence status of the first preset annotation, where the existence status includes existence or non-existence.

[0059] The trigger execution unit 3 is used for triggering the calling of the non-empty check interceptor to perform a non-empty check on the first information when the existence state is existence.

[0060] In some specific embodiments, the trigger execution unit 3 includes:

[0061] The first calculation unit 31 is used to calculate and obtain second information according to the first information, where the second information includes a first verification scenario.

[0062] The verification unit 32 is used to traverse the value attribute corresponding to each field name in the first information, and perform non-empty verification based on the second information to obtain third information, where the third information includes the failed field name, and the failed field name is the field name that failed the verification.

[0063] In some specific embodiments, the first calculation unit 31 includes:

[0064] The parsing unit 311 is used to obtain and parse the first preset scenario computing function to obtain a function variable set, where the function variable set includes at least one parameter name.

[0065] The extraction unit 312 is used to extract fourth information from the first information according to the parameter name, where the fourth information includes a value attribute corresponding to the parameter name.

[0066] The second calculation unit 313 is used to calculate the first verification scene according to the first preset scene calculation function and the fourth information.

[0067] In some specific embodiments, the verification unit 32 includes:

[0068] The first logic unit 321 is used to determine the annotation content of the field name, and if the field name is not annotated by the first preset annotation, determine the annotation content of the next field name.

[0069] The second logic unit 322 is used to determine whether the value attribute corresponding to the field name is empty if the field name is annotated by the first preset annotation, and if the value attribute corresponding to the field name is not empty, determine the annotation content of the next field name.

[0070] The third logic unit 323 is used to determine whether the value attribute corresponding to the first preset annotation is empty if the value attribute corresponding to the field name is empty. If the value attribute corresponding to the first preset annotation is empty, the field name is recorded as a failed field name.

[0071] The fourth logic unit 324 is used to determine whether the value attribute corresponding to the first preset annotation contains the first verification scenario if the value attribute corresponding to the first preset annotation is not empty, and if the value attribute corresponding to the first preset annotation contains the first verification scenario, record the field name as the failed field name.

[0072] In some specific embodiments, the verification unit 32 further includes:

[0073] The sixth logic unit 325 is used to send a first control command and reacquire the first information if there is a failed field name, and the first control command includes a command to control the display to display that the failed field name cannot be empty.

[0074] It should be noted that, regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated here.

[0075] Embodiment 3:

[0076] Corresponding to the above method embodiment, this embodiment further provides a data non-empty verification device, and the data non-empty verification device described below and the data non-empty verification method described above can refer to each other.

[0077] Figure 3 FIG. 8 is a block diagram of a data non-empty check device 800 according to an exemplary embodiment. Figure 3 As shown, the data non-empty check device 800 may include: a processor 801 and a memory 802. The data non-empty check device 800 may also include one or more of a multimedia component 803, an I / O interface 804, and a communication component 805.

[0078] The processor 801 is used to control the overall operation of the data non-empty verification device 800 to complete all or part of the steps in the above-mentioned data non-empty verification method. The memory 802 is used to store various types of data to support the operation of the data non-empty verification device 800, and these data may include, for example, instructions for any application or method operating on the data non-empty verification device 800, and application-related data, such as contact data, sent and received messages, pictures, audio, video, etc. The memory 802 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, disk or optical disk. The multimedia component 803 may include a screen and an audio component. The screen may be, for example, a touch screen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 802 or sent via the communication component 805. The audio component also includes at least one speaker for outputting audio signals. The I / O interface 804 provides an interface between the processor 801 and other interface modules, and the above-mentioned other interface modules can be keyboards, mice, buttons, etc. These buttons can be virtual buttons or physical buttons. The communication component 805 is used for wired or wireless communication between the data non-empty check device 800 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 805 can include: Wi-Fi module, Bluetooth module, NFC module.

[0079] In an exemplary embodiment, the data non-empty check device 800 can be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, referred to as ASIC), digital signal processors (Digital Signal Processor, referred to as DSP), digital signal processing devices (Digital Signal Processing Device, referred to as DSPD), programmable logic devices (Programmable Logic Device, referred to as PLD), field programmable gate arrays (Field Programmable Gate Array, referred to as FPGA), controllers, microcontrollers, microprocessors or other electronic components to execute the above-mentioned data non-empty check method.

[0080] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, and when the program instructions are executed by a processor, the steps of the above-mentioned data non-empty check method are implemented. For example, the computer-readable storage medium can be the above-mentioned memory 802 including program instructions, and the above-mentioned program instructions can be executed by the processor 801 of the data non-empty check device 800 to complete the above-mentioned data non-empty check method.

[0081] Embodiment 4:

[0082] Corresponding to the above method embodiment, a readable storage medium is also provided in this embodiment. The readable storage medium described below and the data non-empty verification method described above can refer to each other.

[0083] A readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data non-empty check method of the above method embodiment are implemented.

[0084] The readable storage medium may specifically be a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or other readable storage medium that can store program codes.

[0085] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

[0086] The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A data non-empty verification method, characterized in that: include: Acquire first information, where the first information includes at least one filled-in parameter entity information, where the parameter entity information includes at least one field name and a value attribute corresponding to the field name; Traversing all annotations of the field name according to the first preset annotation to obtain the existence status of the first preset annotation, wherein the existence status includes existence or non-existence; When the existence status is existence, the existence status triggers calling a non-empty check interceptor to perform a non-empty check on the first information; The existence status triggers calling a non-null check interceptor to perform a non-null check on the first information, including: Calculate second information according to the first information, where the second information includes a first verification scenario; Traversing the value attribute corresponding to each field name in the first information, and performing non-empty check based on the second information to obtain third information, wherein the third information includes a failed field name, and the failed field name is the field name that failed the check; The second information is obtained by calculating according to the first information, wherein the second information includes a first verification scenario, including: Acquire and parse a first preset scenario computing function to obtain a function variable set, wherein the function variable set includes at least one parameter name; Extracting fourth information from the first information according to the parameter name, the fourth information including a value attribute corresponding to the parameter name; A first verification scenario is calculated based on the first preset scenario calculation function and the fourth information.

2. The data non-empty verification method according to claim 1 is characterized in that , the traversing of the value attribute corresponding to each field name in the first information, and performing non-empty check based on the second information to obtain the third information, includes: Determine the annotation content of the field name, and if the field name is not annotated by the first preset annotation, determine the annotation content of the next field name; If the field name is annotated by the first preset annotation, then determine whether the value attribute corresponding to the field name is empty; if the value attribute corresponding to the field name is not empty, then determine the annotation content of the next field name; If the value attribute corresponding to the field name is empty, then determine whether the value attribute corresponding to the first preset annotation is empty. If the value attribute corresponding to the first preset annotation is empty, then record the field name as a failed field name. If the value attribute corresponding to the first preset annotation is not empty, determine whether the value attribute corresponding to the first preset annotation includes a first verification scenario; if the value attribute corresponding to the first preset annotation includes the first verification scenario, record the field name as a failed field name.

3. The data non-empty verification method according to claim 2 is characterized in that , the field name is recorded as the failed field name, and then includes: If there is a failed field name, a first control command is sent and the first information is acquired again, wherein the first control command includes a command to control the display to display that the failed field name cannot be empty.

4. A data non-empty verification device, characterized in that: include: A first acquisition unit is used to acquire first information, where the first information includes at least one filled-in parameter entity information, where the parameter entity information includes at least one field name and a value attribute corresponding to the field name; A first identification unit, configured to traverse the annotations of all the field names according to a first preset annotation, and obtain an existence status of the first preset annotation, wherein the existence status includes existence or non-existence; a triggering execution unit, configured to trigger, when the existence state is existence, calling a non-null check interceptor to perform a non-null check on the first information; The trigger execution unit comprises: A first calculation unit, configured to calculate second information according to the first information, where the second information includes a first verification scenario; A verification unit, configured to traverse the value attribute corresponding to each of the field names in the first information, and perform a non-empty check based on the second information to obtain third information, wherein the third information includes a failed field name, and the failed field name is the field name that failed the check; The first computing unit comprises: A parsing unit, configured to acquire and parse a first preset scenario computing function to obtain a function variable set, wherein the function variable set includes at least one parameter name; an extraction unit, configured to extract fourth information from the first information according to the parameter name, wherein the fourth information includes a value attribute corresponding to the parameter name; The second calculation unit is used to calculate a first verification scenario according to the first preset scenario calculation function and the fourth information.

5. The data non-empty verification device according to claim 4, characterized in that: The verification unit comprises: A first logic unit, configured to determine the annotation content of the field name, and if the field name is not annotated by the first preset annotation, determine the annotation content of the next field name; A second logic unit is used to determine whether the value attribute corresponding to the field name is empty if the field name is annotated by the first preset annotation, and if the value attribute corresponding to the field name is not empty, determine the annotation content of the next field name; A third logic unit is used for, if the value attribute corresponding to the field name is empty, determining whether the value attribute corresponding to the first preset annotation is empty, and if the value attribute corresponding to the first preset annotation is empty, recording the field name as a failed field name; The fourth logic unit is used to determine whether the value attribute corresponding to the first preset annotation contains a first verification scenario if the value attribute corresponding to the first preset annotation is not empty; if the value attribute corresponding to the first preset annotation contains the first verification scenario, the field name is recorded as a failed field name.

6. The data non-empty verification device according to claim 5, characterized in that: The verification unit also includes: The sixth logic unit is used to send a first control command and reacquire the first information if there is a failed field name, wherein the first control command includes a command to control the display to display that the failed field name cannot be empty.

7. A data non-empty check device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the data non-empty verification method as claimed in any one of claims 1 to 3 when executing the computer program.

8. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data non-empty verification method according to any one of claims 1 to 3 are implemented.

Images