Endoscope account management method and system, endoscope and storage medium
By obtaining and verifying account operation files, creating and managing account storage files, the management difficulties and resource occupation problems caused by account accumulation are solved, and efficient management and operation of accounts are achieved.
Patent Information
- Application Number
- CN202411998822.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-31
- Publication Date
- 2025-05-06
AI Technical Summary
Due to the accumulation of accounts, it is difficult to manage accounts, too much resource occupies, and the processing speed is reduced.
By obtaining the account operation file, creating the account storage file, and verifying the login information when the account is logged in. If the account does not exist, register an account. If it exists, verify the login information to achieve effective management and operation of the account.
It effectively improves the processing efficiency of the account, simplifies the account management process, and avoids the problems of resource occupation and processing speed reduction caused by account accumulation.
Smart Images
Figure CN119943307A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to electronic medical equipment, and in particular to an endoscope account management method, system, endoscope and storage medium. Background Art
[0002] With the increasing use of endoscopes in the medical industry at home and abroad, the management of related software programs also needs to be updated and developed. Since the software requires a simpler method to manage various functions, the development and upgrading of software is also becoming more and more important in the field of medical devices. As the first link for users to use the instrument, account management requires a more efficient, scientific and rapid method.
[0003] The lack of an administrator account makes product operation and maintenance difficult. During use, the accumulation of accounts makes it difficult to manage accounts, and the operation becomes increasingly complicated, occupying more and more resources, resulting in a decrease in processing speed. Summary of the invention
[0004] In view of this, the present invention provides an endoscope account management method, system, endoscope and storage medium to solve the problem that account management is difficult due to account accumulation, excessive resources are occupied, and the processing speed is reduced.
[0005] In a first aspect, the present invention provides an endoscope account management method, the method comprising:
[0006] Get account operation files;
[0007] Creating an account storage file based on the account operation file;
[0008] In response to opening the account storage file, performing account login;
[0009] If the account does not exist, registering the account based on the account operation file;
[0010] In response to the successful registration of the account, storing the successfully registered account in the account storage file, and logging in the account;
[0011] If the account exists, verify whether the login information of the account is correct;
[0012] In response to the login information being correct, the account login is successful, and the endoscope is allowed to be operated.
[0013] Beneficial effects: After obtaining the account operation file, create an account storage file according to the account operation file. When logging in, the account storage file needs to be in an open state. If the account to be logged in does not exist, the account can be registered according to the account operation file; when registering an account, the account storage file also needs to be in an open state. After the account registration is successful, it is convenient to store the successfully registered account in the account storage file, which is convenient for subsequent account management; after the account registration is successful, you can log in. If the account to be logged in exists, the login information of the account is verified. When the login information is verified correctly, the account login is successful, allowing the user to operate the endoscope. By setting up an administrator account, the manufacturer has an independent account for development and operation, which makes it easier to deal with problems with the instrument during the period from research and development to later maintenance. The account is registered and logged in through the account operation file, and the account is stored through the account storage file, so that the account storage and account operation are handled separately, the accuracy of each account operation is guaranteed, the account management is more convenient, and the account processing efficiency is effectively improved.
[0014] In an optional implementation manner, before creating the account storage file based on the account operation file, the process further includes:
[0015] Determine whether the account storage file exists in the account operation file;
[0016] In response to the account storage file not existing, creating the account storage file;
[0017] In response to the existence of the account storage file, the account storage file is opened and account login is performed.
[0018] Beneficial effect: When creating an account storage file, first determine whether the account storage file exists. If the account storage file does not exist, create the account storage file. When the account storage file exists, open the account storage file and log in to the account without creating a new account storage file, avoiding account storage confusion due to repeated creation.
[0019] In an optional implementation manner, in response to opening the account storage file, before performing account login, the process further includes:
[0020] Determine the account type of the account, where the account type includes an administrator account and a common user account;
[0021] In response to the account type being a common user account, logging in to the account on a common user account login interface;
[0022] In response to the account type being an administrator account, account login is performed on an administrator account login interface.
[0023] Beneficial effect: By checking the specific attributes of the account to determine the account type, ordinary user accounts and administrator accounts can log in from different account login interfaces. After successful login, different endoscope operation permissions can be granted according to the accounts logged in from different account login interfaces, thereby improving the operability of the endoscope.
[0024] In an optional implementation manner, verifying whether the login information of the account is correct includes:
[0025] Verify whether the login password of the account is correct;
[0026] If the login password verification fails, a reminder of incorrect password is generated, and the account login is performed again.
[0027] Beneficial effects: The password entered by the user is compared with the correct password of the account stored in advance to determine whether the password provided by the user is accurate; if it is verified that the password entered by the user does not match the actual password, a password error reminder is generated to inform the user that the password is incorrect, so that the user can enter the account and password again to try to log in until the correct password is entered and the login is successful; it can give users a certain fault tolerance space and improve the convenience of user use.
[0028] In an optional implementation, the account operation file further includes at least one of an account registration operation, an account login operation, an account deregistration operation, and a password modification operation.
[0029] Beneficial effects: By storing different operation instructions in the account operation file, different operations can be performed on the account according to different operation instructions, providing a comprehensive account management approach, allowing users to operate flexibly according to their own circumstances, and facilitating better management of user accounts.
[0030] In a second aspect, the present invention further provides an endoscope account management system, comprising:
[0031] The first acquisition module is used to acquire the account operation file;
[0032] A first creation module, used to create an account storage file based on the account operation file;
[0033] A first login module, configured to perform account login in response to opening the account storage file;
[0034] A registration module, configured to register the account based on the account operation file if the account does not exist;
[0035] A storage module, configured to store the successfully registered account in the account storage file in response to the successful registration of the account, and log in the account;
[0036] A verification module, used to verify whether the login information of the account is correct if the account exists;
[0037] The operation module is used to allow the endoscope to be operated in response to the login information being correct and the account login being successful.
[0038] Beneficial effect: Because the endoscope account management system is used for the endoscope account management method, it has the same effect as the endoscope account management method and will not be repeated here.
[0039] In an optional implementation, it also includes:
[0040] A first judgment module, used for judging whether the account storage file exists in the account operation file;
[0041] A second creation module, configured to create the account storage file in response to the absence of the account storage file;
[0042] The second login module is used to open the account storage file and perform account login in response to the existence of the account storage file.
[0043] In an optional implementation, it also includes:
[0044] A second determination module is used to determine the account type of the account, where the account type includes an administrator account and a common user account;
[0045] A second acquisition module is used for, in response to the account type being a common user account, performing account login on a common user account login interface;
[0046] The third acquisition module is used to log in the account in the administrator account login interface in response to the account type being an administrator account.
[0047] In a third aspect, the present invention further provides an endoscope, comprising: a memory, a processor, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;
[0048] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the above-mentioned endoscope account management method.
[0049] In a fourth aspect, the present invention further provides a computer-readable storage medium, wherein at least one executable instruction is stored in the storage medium. When the executable instruction is run on an endoscope / endoscope account management system, the endoscope / endoscope account management system enables the endoscope / endoscope account management system to execute the above-mentioned endoscope account management method.
[0050] The above description is only an overview of the technical solution of the embodiment of the present invention. In order to more clearly understand the technical means of the embodiment of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0052] Figure 1 It is a flowchart of an endoscope account management method provided by an embodiment of the present invention;
[0053] Figure 2 It is a structural diagram of an endoscope account management system provided by an embodiment of the present invention;
[0054] Figure 3 It is a schematic diagram of the structure of an endoscope provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0055] Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0056] The following describes a specific embodiment of an endoscope account management method of the present invention. Figure 1 It is a flowchart of an endoscope account management method provided by an embodiment of the present invention. This specification provides method operation steps such as the embodiment or flowchart, but may include more or fewer operation steps based on conventional or non-creative labor. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only execution order. When the actual system or server product is executed, it can be executed in the order shown in the embodiment or the drawings or in parallel (for example, in a parallel processor or multi-threaded processing environment). Specifically, Figure 1 As shown, the method may include the following steps:
[0057] Step S100, obtaining an account operation file;
[0058] Step S200: creating an account storage file based on the account operation file;
[0059] Step S300, in response to opening the account storage file, performing account login;
[0060] Step S400: if the account does not exist, register the account based on the account operation file;
[0061] Step S500: In response to successful account registration, the successfully registered account is stored in an account storage file, and the account is logged in;
[0062] Step S600: If the account exists, verify whether the login information of the account is correct;
[0063] Step S700: In response to the login information being correct, the account login is successful, and the endoscope is allowed to be operated.
[0064] In this embodiment, the user creates an account operation file, and creates an account storage file according to the account operation file. When logging in, the account storage file needs to be in an open state. If the account to be logged in does not exist, the account can be registered according to the account operation file; when registering an account, the account storage file also needs to be in an open state. After the account registration is successful, it is convenient to store the successfully registered account in the account storage file, which is convenient for subsequent management of the account; after the account registration is successful, the login can be performed. If the logged-in account exists, the login information of the account is verified. When the login information is verified correctly, the account login is successful, allowing the user to operate the endoscope. By setting up an administrator account, the manufacturer has an independent account for development and operation, which is more convenient to handle problems with the instrument during the period from research and development to later maintenance. The account is registered and logged in through the account operation file, and the account is stored through the account storage file, so that the account storage and account operation are processed separately, the accuracy of each operation of the account is guaranteed, the management of the account is more convenient, and the processing efficiency of the account is effectively improved.
[0065] In one embodiment, before step S200, the method further includes:
[0066] Determine whether there is an account storage file in the account operation file;
[0067] In response to the account storage file not existing, creating an account storage file;
[0068] In response to the existence of the account storage file, the account storage file is opened and account login is performed.
[0069] In this embodiment, when creating an account storage file, it is first determined whether the account storage file exists. When the account storage file does not exist, the account storage file needs to be created; when the account storage file exists, the account storage file is opened and the account is logged in. There is no need to create a new account storage file, thereby avoiding the situation where account storage confusion occurs due to repeated creation. By putting the endoscope account into the account storage file for unified storage, it can effectively avoid the situation where the account is difficult to manage due to account accumulation during use.
[0070] In one embodiment, before step S300, the method further includes:
[0071] Determine the account type of the account, which includes administrator account and ordinary user account;
[0072] In response to the account type being a common user account, logging in to the account on a common user account login interface;
[0073] In response to the account type being an administrator account, account login is performed on the administrator account login interface.
[0074] In this embodiment, the administrator account is stored in the account operation file, and the ordinary user account is stored in the account storage file, so that the administrator account and the ordinary user account are distinguished, so as to facilitate the granting of different operation permissions to different accounts. Among them, the administrator account can view and manage system logs, configure user permissions, etc., and the administrator account cannot modify passwords and cancel accounts through the account operation file, so as to further ensure the security of the administrator account and the system. By checking the specific attributes of the account to determine the account type, the ordinary user account and the administrator account can log in from different account login interfaces; when the account type is determined to be an ordinary user account, the user is guided to a login interface specially designed for ordinary users according to the account type; similarly, when the account type is determined to be an administrator account, a login interface specially customized for administrators, which is different from the ordinary user login interface, will be presented; different login interfaces have different functions. After successful login, different endoscope operation permissions can be granted according to the accounts logged in from different account login interfaces, so as to improve the operability of the endoscope.
[0075] In other implementations, you can manually choose to log in to an account in a common user account login interface or in an administrator account login interface; when judging the account type, you can determine the account type through identification fields, permission lists, and database records. For example, set a special identification field in the account data to clearly mark whether it is a common user account or an administrator account; or judge based on a specific permission list of the account, for example, an administrator has specific advanced permissions that a common user does not have; or directly read the relevant records of the account type from the database that stores the account information.
[0076] In one embodiment, step S600 includes:
[0077] Verify that the account login password is correct;
[0078] If the login password verification fails, a reminder of incorrect password will be generated and the account login will be performed again.
[0079] In this embodiment, the password entered by the user is compared with the correct password of the account stored in advance to determine whether the password provided by the user is accurate; if it is found after verification that the password entered by the user does not match the actual password, a password error reminder is generated to inform the user that the password is incorrect; for example, a prompt box is popped up and text information is displayed, etc.; the user is prompted to enter the account and password again to try to log in until the correct password is entered and the login is successful; this can give the user a certain amount of fault tolerance and improve the convenience of user use.
[0080] In one embodiment, the account operation file also includes account registration operation, account login operation, account deregistration operation and password modification operation.
[0081] In this embodiment, the account registration operation is a way to create a new account; the account login operation is the process of a registered user verifying his identity to enter the endoscope and obtain corresponding permissions and functions; the account cancellation operation provides a way for the user to actively end the current account usage status; the password modification operation allows the user to update the password according to their own needs to enhance security or solve problems such as forgotten passwords. By storing different operation instructions in the account operation file, different operations can be performed on the account according to different operation instructions, providing a comprehensive account management approach, allowing users to flexibly operate according to their own circumstances, and facilitating better management of user accounts. By putting the endoscope account into the account storage file for unified storage, and then performing operations such as account registration, modification, login and logout through the account operation file, the storage and operation of the account are handled separately, making the account management more convenient.
[0082] Second, as Figure 2 As shown, the present invention also provides an endoscope account management system, including:
[0083] The first acquisition module 100 is used to acquire an account operation file; the account operation file also includes an account registration operation, an account login operation, an account cancellation operation, and a password modification operation, etc.;
[0084] A first creation module 200, used to create an account storage file based on the account operation file;
[0085] A first login module 300, for performing account login in response to opening an account storage file;
[0086] A registration module 400, for registering an account based on an account operation file if the account does not exist;
[0087] The storage module 500 is used to store the successfully registered account to the account storage file in response to the successful account registration, and perform account login;
[0088] Verification module 600, used to verify whether the login information of the account is correct if the account exists;
[0089] The operation module 700 is used to allow the endoscope to be operated in response to the login information being correct and the account login being successful.
[0090] In one embodiment, it also includes:
[0091] The first judgment module is used to judge whether there is an account storage file in the account operation file;
[0092] A second creation module, configured to create an account storage file in response to the absence of the account storage file;
[0093] The second login module is used to open the account storage file and perform account login in response to the existence of the account storage file.
[0094] In one embodiment, it also includes:
[0095] The second judgment module is used to judge the account type of the account, and the account type includes an administrator account and a common user account;
[0096] A second acquisition module is used to log in to the account on the ordinary user account login interface in response to the account type being an ordinary user account;
[0097] The third acquisition module is used to log in the account in the administrator account login interface in response to the account type being an administrator account.
[0098] In one embodiment, the verification module 600 includes:
[0099] Verification unit, used to verify whether the login password of the account is correct;
[0100] The reminder unit is used to generate a reminder of incorrect password if the login password verification fails, and re-login the account.
[0101] The system and method embodiments in the embodiments of the present application are based on the same application concept.
[0102] In a third aspect, the present invention also provides an endoscope, comprising: a memory, a processor, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the above-mentioned endoscope account management method.
[0103] like Figure 3 As shown, the endoscope may include: a processor 502 , a communications interface 504 , a memory 506 , and a communications bus 508 .
[0104] The processor 502, the communication interface 504, and the memory 506 communicate with each other via the communication bus 508. The communication interface 504 is used to communicate with other devices such as a client or other server network elements. The processor 502 is used to execute the program 510, which can specifically execute the relevant steps in the above-mentioned embodiment of the endoscope account management method.
[0105] Specifically, the program 510 may include program code including computer-executable instructions.
[0106] The processor 502 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. The one or more processors included in the endoscope may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs.
[0107] The memory 506 is used to store the program 510. The memory 506 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.
[0108] The program 510 can be specifically called by the processor 502 to enable the endoscope to execute the relevant steps in the above-mentioned embodiment of the endoscope account management method.
[0109] It can be understood by those skilled in the art that Figure 3The structure shown is for illustration only and does not limit the structure of the above-mentioned device. Figure 3 More or fewer components as shown, or with Figure 3 Different configurations shown.
[0110] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, in which at least one executable instruction is stored. When the executable instruction is run on an endoscope / endoscope account management system, the endoscope / endoscope account management system executes the above-mentioned endoscope account management method.
[0111] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system or other device. In addition, the embodiments of the present invention are not directed to any particular programming language.
[0112] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. Similarly, in order to simplify the present invention and help understand one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. Wherein, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself is a separate embodiment of the present invention.
[0113] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and further may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive.
[0114] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim enumerating a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.
Claims
1. An endoscope account management method, characterized in that: include: Get account operation files; Creating an account storage file based on the account operation file; In response to opening the account storage file, performing account login; If the account does not exist, registering the account based on the account operation file; In response to the successful registration of the account, the successfully registered account is stored in the account storage file, and the account is logged in; If the account exists, verify whether the login information of the account is correct; In response to the login information being correct, the account login is successful, and the endoscope is allowed to be operated.
2. The endoscope account management method according to claim 1, characterized in that: Before creating the account storage file based on the account operation file, the method further includes: Determine whether the account storage file exists in the account operation file; In response to the account storage file not existing, creating the account storage file; In response to the existence of the account storage file, the account storage file is opened and account login is performed.
3. The endoscope account management method according to claim 1, characterized in that: In response to opening the account storage file, before performing account login, the method further includes: Determine the account type of the account, where the account type includes an administrator account and a common user account; In response to the account type being a common user account, logging in to the account on a common user account login interface; In response to the account type being an administrator account, account login is performed on an administrator account login interface.
4. The endoscope account management method according to claim 1, characterized in that: The verifying whether the login information of the account is correct includes: Verify whether the login password of the account is correct; If the login password verification fails, a reminder of incorrect password is generated, and the account login is performed again.
5. The endoscope account management method according to claim 1, characterized in that: The account operation file also includes at least one of an account registration operation, an account login operation, an account deregistration operation, and a password modification operation.
6. An endoscope account management system, characterized in that: include: The first acquisition module is used to acquire the account operation file; A first creation module, used to create an account storage file based on the account operation file; A first login module, configured to perform account login in response to opening the account storage file; A registration module, configured to register the account based on the account operation file if the account does not exist; A storage module, configured to store the successfully registered account in the account storage file in response to the successful registration of the account, and log in the account; A verification module, used to verify whether the login information of the account is correct if the account exists; The operation module is used to allow the endoscope to be operated in response to the login information being correct and the account login being successful.
7. The endoscope account management system according to claim 6, characterized in that: Also includes: A first judgment module, used for judging whether the account storage file exists in the account operation file; A second creation module, configured to create the account storage file in response to the absence of the account storage file; The second login module is used to open the account storage file and perform account login in response to the existence of the account storage file.
8. The endoscope account management system according to claim 6, characterized in that: Also includes: A second determination module is used to determine the account type of the account, where the account type includes an administrator account and a common user account; A second acquisition module is used for, in response to the account type being a common user account, performing account login on a common user account login interface; The third acquisition module is used to log in the account in the administrator account login interface in response to the account type being an administrator account.
9. An endoscope, characterized in that: include: A memory, a processor, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute the endoscope account management method as described in any one of claims 1-5.
10. A computer-readable storage medium, characterized in that: The storage medium stores at least one executable instruction, and when the executable instruction is executed on the endoscope / endoscope account management system, the endoscope / endoscope account management system executes the endoscope account management method as described in any one of claims 1-5.