Application mode control method and device, electronic equipment and storage medium

Abstract

The invention relates to an application mode control method and device, electronic equipment and a storage medium. The application mode control method comprises the following steps: determining whether a trigger event for triggering a login application mode is detected or not; if the trigger event is detected, a user mode identifier is obtained, and the user mode identifier is used for indicating an application mode corresponding to a user who logs in an application currently; and logging in an application mode corresponding to the user mode identifier. According to the embodiment of the application, after the user logs in the application, the application mode corresponding to the user can be automatically entered, manual switching of the application mode is not needed, automatic matching of the user and the application mode is achieved, application use convenience is improved, and then the same user can conveniently log in the same application through different electronic devices.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an application mode control method, device, electronic device and storage medium. Background Art

[0002] With the popularization of smart devices and the aging of users of smart devices, the use of smart devices and applications is increasingly aimed at elderly users. However, due to the limited vision, hearing, and operating ability of elderly users in using smart devices, the conventional UI interface and interaction process are relatively complicated for the elderly. Many apps will develop elderly modes to facilitate use by elderly users.

[0003] However, the current senior mode is limited to a single device and has not yet achieved intelligent automatic matching of multiple devices. It is impossible to automatically log in to the same senior mode on different devices with the same account through a unified account. Summary of the invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, the present application provides an application mode control method, device, electronic device and storage medium.

[0005] In a first aspect, the present application provides an application mode control method, comprising:

[0006] determining whether a triggering event for triggering a login application mode is detected;

[0007] If the trigger event is detected, a user mode identifier is obtained, where the user mode identifier is used to indicate an application mode corresponding to a user currently logging into the application;

[0008] Log in to the application mode corresponding to the user mode identifier.

[0009] Optionally, obtain a user mode identifier, including:

[0010] Obtaining a first verification key corresponding to the login account of the current login application;

[0011] A user mode identifier is obtained according to the first verification key.

[0012] Optionally, obtaining a user mode identifier according to the first verification key includes:

[0013] Obtain a second verification key from the historical record, where the second verification key is recorded when the application was successfully logged in last time;

[0014] determining whether the first verification key is the same as the second verification key;

[0015] If the first verification key is the same as the second verification key, a user mode identifier corresponding to the second verification key is obtained locally.

[0016] Optionally, obtaining a user mode identifier according to the first verification key further includes:

[0017] If the first verification key is different from the second verification key, a user mode identifier corresponding to the first verification key is obtained in the cloud.

[0018] Optionally, the method further comprises:

[0019] If an application mode switching operation for switching an application mode is received, the application mode switching operation is used to control the application from a default mode to a target mode, and obtain a user identifier of a currently logged-in application and a first mode identifier corresponding to the target mode;

[0020] A user mode identifier is determined according to the user identifier and the first mode identifier, and the user mode identifier is stored locally and in the cloud.

[0021] Optionally, obtain the user ID of the currently logged in application, including:

[0022] Get the login account of the current login application;

[0023] A user ID is randomly generated according to the login account.

[0024] Optionally, the method further comprises:

[0025] If no application mode switching operation for switching the application mode is received, obtaining a user identifier of the currently logged-in application and a second mode identifier of the default mode;

[0026] A user mode identifier is determined according to the user identifier and the second mode identifier, and the user mode identifier is stored locally and in the cloud.

[0027] In a second aspect, the present application provides an application mode control device, comprising:

[0028] A detection module, used to determine whether a triggering event for triggering a login application mode is detected;

[0029] A first acquisition module, configured to acquire a user mode identifier if the trigger event is detected, wherein the user mode identifier is used to indicate an application mode corresponding to a user currently logging into the application;

[0030] A login module is used to log in to the application mode corresponding to the user mode identifier.

[0031] Optionally, the first acquisition module includes:

[0032] A first acquisition unit, used to acquire a first verification key corresponding to a login account currently logged into the application;

[0033] The second acquisition unit is used to acquire the user mode identifier according to the first verification key.

[0034] Optionally, the second acquiring unit includes:

[0035] A first acquisition subunit is used to acquire a second verification key of the historical record, where the second verification key is recorded when the application is successfully logged in last time;

[0036] A first determining subunit, configured to determine whether the first verification key is the same as the second verification key;

[0037] The second acquisition subunit is configured to locally acquire a user mode identifier corresponding to the second verification key if the first verification key is the same as the second verification key.

[0038] Optionally, the second acquiring unit further includes:

[0039] The third acquisition subunit is configured to acquire, in the cloud, a user mode identifier corresponding to the first verification key if the first verification key is different from the second verification key.

[0040] Optionally, the device further comprises:

[0041] A second acquisition module is configured to, upon receiving an application mode switching operation for switching an application mode, obtain a user identifier of a currently logged-in application and a first mode identifier corresponding to the target mode;

[0042] The first storage module is used to determine a user mode identifier according to the user identifier and the first mode identifier, and store the user mode identifier locally and in the cloud.

[0043] Optionally, the second acquisition module includes:

[0044] The third acquisition unit is used to obtain the login account of the current login application;

[0045] A generating unit is used to randomly generate a user identifier according to the login account.

[0046] Optionally, the device further comprises:

[0047] A third acquisition module is used to acquire the user identifier of the currently logged-in application and the second mode identifier of the default mode if no application mode switching operation for switching the application mode is received;

[0048] A determination module is used to determine a user mode identifier according to the user identifier and the second mode identifier, and store the user mode identifier locally and in the cloud.

[0049] In a third aspect, the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0050] Memory, used to store computer programs;

[0051] The processor is used to implement any application mode control method described in the first aspect when executing a program stored in the memory.

[0052] In a fourth aspect, the present application provides a computer-readable storage medium, on which a program of an application mode control method is stored, and when the program of the application mode control method is executed by a processor, the steps of the application mode control method described in any one of the first aspects are implemented.

[0053] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0054] The embodiment of the present application can automatically enter the application mode corresponding to the user after the user logs into the application, without the need to manually switch the application mode, thereby achieving automatic matching of users and application modes, improving the convenience of application use, and further, making it convenient for the same user to log in to the same application through different electronic devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0056] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0057] Figure 1 A flowchart of an application mode control method provided in an embodiment of the present application;

[0058] Figure 2 A flowchart of an application mode control method in a practical application provided by an embodiment of the present application;

[0059] Figure 3 A structural diagram of an application mode control device provided in an embodiment of the present application;

[0060] Figure 4 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0062] Since the current elderly mode is limited to a single device, multiple devices have not yet been intelligently matched automatically, and it is impossible to automatically log in to the same elderly mode on different devices with the same account through a unified account. To this end, the embodiments of the present application provide an application mode control method, device, electronic device and storage medium.

[0063] The present application embodiment provides an application mode control method, which can be applied to electronic devices running applications, such as mobile phones, tablet computers, etc. Figure 1 As shown, including:

[0064] Step S101, determining whether a triggering event for triggering a login application mode is detected;

[0065] In the embodiment of the present application, when the user exits the APP to the background and then returns to the foreground, or kills the APP in the background and re-enters the APP, a trigger event for triggering the login application mode will be triggered.

[0066] The application mode can be an elderly mode, a child mode, an entertainment mode, or any other application mode different from the default mode.

[0067] Step S102: if the trigger event is detected, a user mode identifier is obtained, where the user mode identifier is used to indicate an application mode corresponding to the user currently logging into the application;

[0068] In this step, the application mode to be used by the user currently logging into the application can be determined, and the identifier of the application mode is the user mode identifier.

[0069] Step S103: Log in to the application mode corresponding to the user mode identifier.

[0070] In this step, an application mode corresponding to the user mode identifier may be entered, and a series of processes corresponding to the application mode may be executed.

[0071] The embodiment of the present application can automatically enter the application mode corresponding to the user after the user logs into the application, without the need to manually switch the application mode, thereby achieving automatic matching of users and application modes, improving the convenience of application use, and further, making it convenient for the same user to log in to the same application through different electronic devices.

[0072] In another embodiment of the present application, step S102 of obtaining a user mode identifier includes:

[0073] Step S201, obtaining a first verification key corresponding to the login account of the current login application;

[0074] In this embodiment of the present application, the first verification key may be a token value of a login account.

[0075] Step S202: Obtain a user mode identifier according to the first verification key.

[0076] In one implementation of the present application, step S202 of obtaining a user mode identifier according to the first verification key includes:

[0077] Step S301, obtaining a second verification key of the history record, wherein the second verification key is recorded when the application was successfully logged in last time, that is, the second verification key corresponds to the login account of the application that was successfully logged in last time, that is, the second verification key is the token value of the login account that was successfully logged in last time;

[0078] Step S302, determining whether the first verification key is the same as the second verification key;

[0079] Step S303: If the first verification key is the same as the second verification key, locally obtain a user mode identifier corresponding to the second verification key.

[0080] When the first verification key is the same as the second verification key, it indicates that the user who logged into the application last time and the user who logged into the application this time are the same user and the application mode to be used is the same, so the user mode identifier corresponding to the second verification key can be directly obtained.

[0081] Step S304: If the first verification key is different from the second verification key, a user mode identifier corresponding to the first verification key is obtained in the cloud.

[0082] When the first verification key is different from the second verification key, it indicates that the user who logged into the application last time and the user who logged into the application this time are different, and the application modes to be used may be different. Therefore, the user mode identifier corresponding to the first verification key can be obtained in the cloud.

[0083] The embodiment of the present application compares the first verification key with the second verification key recorded when the application was successfully logged in last time. If the two are the same, the user mode information of the application mode used for the last login can be directly obtained. Otherwise, the user mode identifier of the application mode to be used by the user currently logging into the application can be obtained from the cloud. This ensures that regardless of whether the user using the electronic device to log in to the application is the same as the user who successfully logged in to the application last time, the application mode required by the user currently logging in to the application can be provided to match the personalized needs of different users. There is no need to manually switch the application mode, thereby achieving automatic matching of users and application modes, improving the convenience of application use, and thus making it convenient for different users to log in to the same application through the same electronic device.

[0084] In another embodiment of the present application, the method further includes:

[0085] Step S401, if an application mode switching operation for switching an application mode is received, the application mode switching operation is used to control the application from a default mode to a target mode;

[0086] Step S402, obtaining a user identifier of the currently logged-in application and a first mode identifier corresponding to the target mode;

[0087] Obtaining a user identification of a currently logged-in application includes: obtaining a login account of the currently logged-in application; and randomly generating a user identification according to the login account.

[0088] Step S403: determine a user mode identifier according to the user identifier and the first mode identifier, and store the user mode identifier locally and in the cloud.

[0089] When receiving an application mode switching operation, the embodiment of the present application can automatically determine the user mode identifier based on the user identifier of the currently logged-in application and the first mode identifier of the target mode switched to by the application mode switching operation, and save it locally and in the cloud, so that the user can automatically enter the application mode he prefers the next time he logs in to the application through the local computer and through other devices.

[0090] In another embodiment of the present application, the method further includes:

[0091] Step S501, if the application mode switching operation for switching the application mode is not received;

[0092] Step S502, obtaining the user identifier of the currently logged-in application and the second mode identifier of the default mode;

[0093] Step S503: determine a user mode identifier according to the user identifier and the second mode identifier, and store the user mode identifier locally and in the cloud.

[0094] The embodiment of the present application can automatically determine the user mode identifier based on the user identifier of the currently logged-in application and the second mode identifier of the default mode when no application mode switching operation is received, and store it locally and in the cloud, so that it can be used to determine the application mode to be logged in the next time the same or different user logs in to the application through the local device, and it can also be used to determine the application mode to be logged in the next time the same user logs in to the application through other devices.

[0095] For ease of understanding, the present application also provides an embodiment in practical application, such as Figure 2 As shown below:

[0096] The default mode is normal mode when the user logs in or registers for the first time. After a successful login, the token value corresponding to the account is obtained. The token is used as the key for identity authentication. The token value is obtained through the account and then concatenated with appStyle to create a dictionary. The concatenated field "appStyle+token" is the key, and the corresponding value is recorded as the default normal mode "normal". The created dictionary is stored locally and uploaded to the cloud server for unified management, so that the corresponding mode status can be obtained when the account switches the device to log in. If during use, the elderly user manually switches the account to the elderly mode, the corresponding value is recorded as "elder" after the switch to the elderly mode is successful. At this time, the value corresponding to the key of the dictionary value should be stored locally and uploaded to the cloud to overwrite the original information.

[0097] When the user exits the app to the background and then returns to the foreground, or kills the app in the background and reenters the app, the token value is compared locally to see if it has changed. If the token has not changed, the locally stored value is used as the current mode. If the token changes, it means that the user changes the account to log in from another device, and the corresponding key value cannot be obtained from the local storage. At this time, the value corresponding to the token is retrieved from the cloud server. If the value obtained is "normal", the user logs in to the normal mode normally. If the corresponding value is "elder", the user logs in to the elderly mode. In this way, even if the account switches devices to log in, the cloud service can record the mode status at the time of the last login, so that the matching login is consistent with the last login mode.

[0098] Through the present invention, a unified elderly user account can enjoy a consistent elderly mode experience on different smart devices, reducing tedious and repeated mode switching actions, improving convenience and satisfaction, and simplifying the operation process for elderly users.

[0099] In another embodiment of the present application, an application mode control device is also provided, such as Figure 3 As shown, including:

[0100] A detection module 11, used to determine whether a triggering event for triggering a login application mode is detected;

[0101] A first acquisition module 12 is used to acquire a user mode identifier if the trigger event is detected, where the user mode identifier is used to indicate an application mode corresponding to a user currently logging into the application;

[0102] The login module 13 is used to log in the application mode corresponding to the user mode identifier.

[0103] The embodiment of the present application can automatically enter the application mode corresponding to the user after the user logs into the application, without the need to manually switch the application mode, thereby achieving automatic matching of users and application modes, improving the convenience of application use, and further, making it convenient for the same user to log in to the same application through different electronic devices.

[0104] Optionally, the first acquisition module includes:

[0105] A first acquisition unit, used to acquire a first verification key corresponding to a login account currently logged into the application;

[0106] The second acquisition unit is used to acquire the user mode identifier according to the first verification key.

[0107] Optionally, the second acquiring unit includes:

[0108] A first acquisition subunit is used to acquire a second verification key of the historical record, where the second verification key is recorded when the application is successfully logged in last time;

[0109] A first determining subunit, configured to determine whether the first verification key is the same as the second verification key;

[0110] The second acquisition subunit is configured to locally acquire a user mode identifier corresponding to the second verification key if the first verification key is the same as the second verification key.

[0111] Optionally, the second acquiring unit further includes:

[0112] The third acquisition subunit is configured to acquire, in the cloud, a user mode identifier corresponding to the first verification key if the first verification key is different from the second verification key.

[0113] The embodiment of the present application compares the first verification key with the second verification key recorded when the application was successfully logged in last time. If the two are the same, the user mode information of the application mode used for the last login can be directly obtained. Otherwise, the user mode identifier of the application mode to be used by the user currently logging into the application can be obtained from the cloud. This ensures that regardless of whether the user using the electronic device to log in to the application is the same as the user who successfully logged in to the application last time, the application mode required by the user currently logging in to the application can be provided to match the personalized needs of different users. There is no need to manually switch the application mode, thereby achieving automatic matching of users and application modes, improving the convenience of application use, and thus making it convenient for different users to log in to the same application through the same electronic device.

[0114] Optionally, the device further comprises:

[0115] A second acquisition module is configured to, upon receiving an application mode switching operation for switching an application mode, obtain a user identifier of a currently logged-in application and a first mode identifier corresponding to the target mode;

[0116] The first storage module is used to determine a user mode identifier according to the user identifier and the first mode identifier, and store the user mode identifier locally and in the cloud.

[0117] Optionally, the second acquisition module includes:

[0118] The third acquisition unit is used to obtain the login account of the current login application;

[0119] A generating unit is used to randomly generate a user identifier according to the login account.

[0120] When receiving an application mode switching operation, the embodiment of the present application can automatically determine the user mode identifier based on the user identifier of the currently logged-in application and the first mode identifier of the target mode switched to by the application mode switching operation, and save it locally and in the cloud, so that the user can automatically enter the application mode he prefers the next time he logs in to the application through the local computer and through other devices.

[0121] Optionally, the device further comprises:

[0122] A third acquisition module is used to acquire the user identifier of the currently logged-in application and the second mode identifier of the default mode if no application mode switching operation for switching the application mode is received;

[0123] A determination module is used to determine a user mode identifier according to the user identifier and the second mode identifier, and store the user mode identifier locally and in the cloud.

[0124] The embodiment of the present application can automatically determine the user mode identifier based on the user identifier of the currently logged-in application and the second mode identifier of the default mode when no application mode switching operation is received, and store it locally and in the cloud, so that it can be used to determine the application mode to be logged in the next time the same or different user logs in to the application through the local device, and it can also be used to determine the application mode to be logged in the next time the same user logs in to the application through other devices.

[0125] In another embodiment of the present application, an electronic device is provided, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;

[0126] Memory, used to store computer programs;

[0127] The processor is used to implement the application mode control method described in any of the above method embodiments when executing the program stored in the memory.

[0128] In the electronic device provided by the embodiment of the present invention, the processor executes the program stored in the memory to automatically enter the application mode corresponding to the user after the user logs in to the application, without the need to manually switch the application mode, thereby achieving automatic matching between the user and the application mode, improving the convenience of using the application, and further, making it convenient for the same user to log in to the same application through different electronic devices.

[0129] The communication bus 1140 mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 1140 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0130] The communication interface 1120 is used for communication between the electronic device and other devices.

[0131] The memory 1130 may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0132] The above-mentioned processor 1110 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0133] In another embodiment of the present application, a computer-readable storage medium is provided, on which a program of the application mode control method is stored. When the program of the application mode control method is executed by a processor, the steps of the application mode control method described in any of the aforementioned method embodiments are implemented.

[0134] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0135] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. An application mode control method, characterized in that: include: determining whether a triggering event for triggering a login application mode is detected; If the trigger event is detected, a user mode identifier is obtained, where the user mode identifier is used to indicate an application mode corresponding to a user currently logging into the application; Log in to the application mode corresponding to the user mode identifier.

2. The application mode control method according to claim 1, characterized in that: Get user mode flags, including: Obtaining a first verification key corresponding to the login account of the current login application; A user mode identifier is obtained according to the first verification key.

3. The application mode control method according to claim 2, characterized in that: Acquiring a user mode identifier according to the first verification key includes: Obtain a second verification key from the historical record, where the second verification key is recorded when the application was successfully logged in last time; determining whether the first verification key is the same as the second verification key; If the first verification key is the same as the second verification key, a user mode identifier corresponding to the second verification key is obtained locally.

4. The application mode control method according to claim 3, characterized in that: Acquiring a user mode identifier according to the first verification key also includes: If the first verification key is different from the second verification key, a user mode identifier corresponding to the first verification key is obtained in the cloud.

5. The application mode control method according to claim 1, characterized in that: The method further comprises: If an application mode switching operation for switching an application mode is received, the application mode switching operation is used to control the application from a default mode to a target mode, and obtain a user identifier of the currently logged-in application and a first mode identifier corresponding to the target mode; A user mode identifier is determined according to the user identifier and the first mode identifier, and the user mode identifier is stored locally and in the cloud.

6. The application mode control method according to claim 5, characterized in that: Get the user ID of the currently logged in application, including: Get the login account of the current login application; A user ID is randomly generated according to the login account.

7. The application mode control method according to claim 5, characterized in that: The method further comprises: If no application mode switching operation for switching the application mode is received, obtaining a user identifier of the currently logged-in application and a second mode identifier of the default mode; A user mode identifier is determined according to the user identifier and the second mode identifier, and the user mode identifier is stored locally and in the cloud.

8. An application mode control device, characterized in that: include: A detection module, used to determine whether a triggering event for triggering a login application mode is detected; A first acquisition module, configured to acquire a user mode identifier if the trigger event is detected, wherein the user mode identifier is used to indicate an application mode corresponding to a user currently logging into the application; A login module is used to log in to the application mode corresponding to the user mode identifier.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to implement the application mode control method described in any one of claims 1 to 7 when executing the program stored in the memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program of the application mode control method, and when the program of the application mode control method is executed by a processor, the steps of the application mode control method described in any one of claims 1 to 7 are implemented.

Images