Unified account management method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention relates to a unified account management method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining the pre-stored sub-account encryption information of a target sub-account in response to the triggering of the management operation of the target sub-account on a unified account platform after a user logs in; obtaining a pre-established unified account key; decrypting the sub-account encryption information by using the unified account key to obtain a sub-account name and a sub-account password of the target sub-account; and based on the sub-account name and the sub-account password, sending operation information to the target sub-platform through a sub-platform interface corresponding to the target sub-account. According to the embodiment of the invention, the sub-accounts of a plurality of sub-platforms can be managed on the unified account platform, the unified account key is established, and the information of each sub-account is protected, so that a user can conveniently perform unified management on the accounts of a plurality of different platforms, and the security of the account information can be ensured.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a unified account management method, device, electronic device and read storage medium. Background Art

[0002] Currently, various applications (Apps) and websites and other platforms usually require logging in to the corresponding platform account to use the corresponding functions. However, the various platforms are usually not interoperable, and operations on the account information of each platform require logging in to the corresponding platform. This causes inconvenience to users, especially in scenarios where it is necessary to log in to multiple platforms at the same time and modify account information, the efficiency of account management is low. Therefore, how to improve the efficiency of managing multiple accounts and reduce the difficulty of managing multiple accounts is a problem that needs to be solved. Summary of the invention

[0003] In view of this, in order to solve some or all of the above technical problems, the embodiments of the present application provide a unified account management method, device, electronic device and computer-readable storage medium.

[0004] In a first aspect, an embodiment of the present application provides a unified account management method, the method comprising: on a unified account platform after a user logs in, in response to triggering a management operation on a target sub-account, obtaining pre-stored sub-account encryption information of a target sub-account; obtaining a pre-established unified account key; using the unified account key, decrypting the sub-account encryption information to obtain the sub-account name and sub-account password of the target sub-account; based on the sub-account name and sub-account password, sending operation information to the target sub-platform through the sub-platform interface corresponding to the target sub-account.

[0005] In one possible implementation, after the user logs in, in response to triggering a management operation on the target sub-account, the unified account platform obtains the pre-stored sub-account encryption information of the target sub-account, including: after the user logs in, the unified account platform sends the target plug-in corresponding to the target sub-account to the terminal device used by the user, so that the terminal device displays the target plug-in; in response to using the target plug-in to perform the management operation on the target sub-account, obtains the pre-stored sub-account encryption information of the target sub-account.

[0006] In a possible implementation, obtaining the pre-established unified account key includes: obtaining the pre-established unified account key from a terminal device used by the user.

[0007] In one possible implementation, after the user logs in, on the unified account platform, in response to triggering a management operation on the target sub-account, before obtaining the pre-stored sub-account encryption information of the target sub-account, the method also includes: obtaining the unified account name and unified password of the unified account platform; generating a unified account key based on the unified account name and unified password; saving the unified account key to a terminal device used by the user; and using the unified account key to encrypt the unified account name and unified password to obtain unified encrypted account information.

[0008] In a possible implementation, generating a unified account key based on a unified account name and a unified password includes: extracting a password fragment from the unified password according to a pre-specified character position; and merging the unified account name and the password fragment to obtain the unified account key.

[0009] In one possible implementation, after using the unified account key to encrypt the unified account name and the unified password to obtain the unified encrypted account information, the method also includes: in response to triggering a login operation to the unified account platform, obtaining the unified account key from the terminal device; using the unified account key, decrypting the unified encrypted account information to obtain the unified account name and the unified password; and using the unified account name and the unified password to log in to the unified account platform.

[0010] In one possible implementation, on the unified account platform after the user logs in, in response to triggering a management operation on the target sub-account, before obtaining the pre-stored sub-account encryption information of the target sub-account, the method also includes: obtaining the sub-account name and sub-password of the target sub-platform input by the user; using the unified account key, encrypting the sub-account name and sub-password to obtain the sub-account encryption information; and binding the correspondence between the sub-account encryption information and the user's unified account name.

[0011] In a second aspect, an embodiment of the present application provides a unified account management device, which includes: a first acquisition module, which is used to obtain pre-stored sub-account encryption information of a target sub-account on a unified account platform after a user logs in, in response to triggering a management operation on a target sub-account; a second acquisition module, which is used to obtain a pre-established unified account key; a first decryption module, which is used to use the unified account key to decrypt the sub-account encryption information to obtain the sub-account name and sub-account password of the target sub-account; and a first sending module, which is used to send operation information to the target sub-platform through the sub-platform interface corresponding to the target sub-account based on the sub-account name and sub-account password.

[0012] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory for storing a computer program; a processor for executing the computer program stored in the memory, and when the computer program is executed, the method of any embodiment of the unified account management method of the first aspect of the present application is implemented.

[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, a method as in any embodiment of the unified account management method of the first aspect described above is implemented.

[0014] In a fifth aspect, an embodiment of the present application provides a computer program, which includes a computer-readable code. When the computer-readable code runs on a device, the processor in the device implements a method as in any embodiment of the unified account management method of the first aspect above.

[0015] The unified account management method, device, electronic device and computer-readable storage medium provided in the embodiments of the present application set up a unified account platform, and the user logs in to the unified account platform. When managing the target sub-account, the sub-account encryption information of the pre-stored target sub-account and the pre-established unified account key are obtained, and the sub-account encryption information is decrypted using the unified account key to obtain the sub-account name and sub-account password of the target sub-account. Based on the sub-account name and sub-account password, the operation information is sent to the target sub-platform through the sub-platform interface corresponding to the target sub-account. The embodiments of the present application realize the binding of multiple sub-platforms to the unified account platform, and the sub-accounts of multiple sub-platforms can be managed on the unified account platform, and a unified account key is established to protect the information of each sub-account, so that it is convenient for users to uniformly manage accounts of multiple different platforms and ensure the security of account information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] In order to more clearly illustrate the embodiments of the present application 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.

[0018] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0019] Figure 1 A flowchart of a unified account management method provided in an embodiment of the present application;

[0020] Figure 2A flowchart of another unified account management method provided in an embodiment of the present application;

[0021] Figure 3 A flowchart of another unified account management method provided in an embodiment of the present application;

[0022] Figure 4 A flowchart of another unified account management method provided in an embodiment of the present application;

[0023] Figure 5 A flowchart of another unified account management method provided in an embodiment of the present application;

[0024] Figure 6 A flowchart of another unified account management method provided in an embodiment of the present application;

[0025] Figure 7 A schematic diagram of the structure of a unified account management device provided in an embodiment of the present application;

[0026] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. It should be noted that unless otherwise specifically stated, the relative arrangement of the components and steps, the numerical expressions and the numerical values ​​described in these embodiments do not limit the scope of the present application.

[0028] Those skilled in the art will understand that the terms "first" and "second" in the embodiments of the present application are only used to distinguish between different steps, devices, modules and other objects, and do not represent any specific technical meanings, nor do they indicate the logical order between them.

[0029] It should also be understood that in this embodiment, “plurality” may refer to two or more than two, and “at least one” may refer to one, two or more than two.

[0030] It should also be understood that any component, data or structure mentioned in the embodiments of the present application can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

[0031] In addition, the term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0032] It should also be understood that the description of the various embodiments in this application focuses on the differences between the various embodiments, and the same or similar aspects thereof can be referenced to each other, and for the sake of brevity, they will not be described one by one.

[0033] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present application, its application, or uses.

[0034] Technologies, circuits, and devices known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the above-mentioned technologies, circuits, and devices should be considered as part of the specification.

[0035] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0036] It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other. To facilitate the understanding of the embodiments of the present application, the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0037] In order to solve the technical problem of inconvenient multi-platform account management in the prior art, the present application provides a unified account management method, which can use a unified account platform to manage the account information of multiple bound sub-accounts at the same time, thereby improving the efficiency of multi-platform account management.

[0038] Figure 1 A flow chart of a unified account management method provided for an embodiment of the present application. This method can be applied to a server, where the server is connected to a terminal device used by a user, and the user uses the terminal device to log in to a unified account platform running on the server to manage multiple sub-accounts. In addition, the execution subject of this method can be hardware or software. When the above-mentioned execution subject is hardware, the execution subject can be one or more of the above-mentioned servers. For example, a single server can execute this method, or multiple servers can cooperate with each other to execute this method. When the above-mentioned execution subject is software, this method can be implemented as multiple software or software modules, or as a single software or software module. No specific limitation is made here.

[0039] like Figure 1 As shown, the method specifically includes:

[0040] Step 101, after the user logs in, in response to triggering a management operation on a target sub-account, the unified account platform obtains the pre-stored sub-account encryption information of the target sub-account.

[0041] In some embodiments, the unified account management platform can be run on a server, and the user logs in to the unified account platform by using an application or web browser installed on a terminal device. The unified account platform is provided with sub-account encryption information of multiple sub-accounts. The user can use the terminal device to operate a certain target sub-account, and the unified account platform obtains the sub-account encryption information of the target sub-account according to the operation instruction input by the user. The sub-account encryption information is the information that is pre-encrypted for the sub-account name and sub-account password of the target sub-platform.

[0042] Step 102: Obtain a pre-established unified account key.

[0043] In some embodiments, the unified account key is pre-established information for decrypting each sub-account. The unified account key can be stored on a server or on a terminal device. The unified account key can be obtained by encrypting the confidential information input by the user using a preset encryption rule.

[0044] Step 103: Decrypt the sub-account encrypted information using the unified account key to obtain the sub-account name and sub-account password of the target sub-account.

[0045] In some embodiments, the unified account key and sub-account encryption information may be decrypted using preset decryption rules to restore the sub-account name and sub-account password of the target sub-account.

[0046] Step 104: Based on the sub-account name and the sub-account password, the operation information is sent to the target sub-platform through the sub-platform interface corresponding to the target sub-account.

[0047] In some embodiments, after obtaining the sub-account name and sub-account password, the sub-account name and sub-account password can be used to log in to the target sub-platform. The user can use the terminal device to forward the operation information from the unified account platform to the target sub-platform through the interface of the target sub-platform on the interface of the unified account platform, and perform various operations on the target sub-platform. For example, the sub-account name and sub-account password of the target sub-platform can be modified, or the target sub-platform can be logged in to operate the functions provided by the target sub-platform.

[0048] The unified account management method provided in the embodiment of the present application sets up a unified account platform, and the user logs in to the unified account platform. When managing the target sub-account, the pre-stored sub-account encryption information of the target sub-account and the pre-established unified account key are obtained, and the sub-account encryption information is decrypted using the unified account key to obtain the sub-account name and sub-account password of the target sub-account. Based on the sub-account name and sub-account password, the operation information is sent to the target sub-platform through the sub-platform interface corresponding to the target sub-account. The embodiment of the present application realizes the binding of multiple sub-platforms to the unified account platform, and the sub-accounts of multiple sub-platforms can be managed on the unified account platform, and a unified account key is established to protect the information of each sub-account, so that it is convenient for users to uniformly manage accounts of multiple different platforms and ensure the security of account information.

[0049] In some optional implementations, such as Figure 2 As shown, step 101 includes:

[0050] Step 1011, after the user logs in, the unified account platform sends the target plug-in corresponding to the target sub-account to the terminal device used by the user, so that the terminal device displays the target plug-in.

[0051] Specifically, the server may store plug-ins corresponding to multiple sub-platforms, issue these plug-ins to the terminal devices used by users, and display the plug-ins after the users log in to the unified account platform using the terminal devices. Users can log in to the target sub-platform and perform various operations on the target sub-platform by operating the target plug-in.

[0052] Step 1012: In response to using the target plug-in to perform a management operation on the target sub-account, obtain the pre-stored sub-account encryption information of the target sub-account.

[0053] Specifically, the server may store encrypted sub-account information of the target sub-account. When the user uses the target plug-in to perform management operations on the target sub-account (for example, using the target sub-account to log in to the target sub-platform, modifying the target sub-account, etc.), the encrypted sub-account information that establishes a corresponding relationship with the target plug-in can be obtained.

[0054] In this embodiment, by setting a plug-in corresponding to the target sub-platform, the user uses the plug-in to manage the account of the target sub-platform, thereby helping the user to manage the target sub-account more conveniently and improving the efficiency of unified account management.

[0055] In some optional implementations, step 102 includes:

[0056] Obtain a pre-established unified account key from the terminal device used by the user.

[0057] That is, the unified account key is stored on the terminal device. When the user uses the terminal device to manage the target sub-account, the unified account key can be sent to the server, and the server uses the unified account key for decryption.

[0058] By storing the unified account key on the terminal device, the security risks caused by storing the unified account key on the server can be avoided, thereby improving the security of account information.

[0059] In some optional implementations, such as Figure 3 As shown, before step 101, the method further includes:

[0060] Step 105: Obtain a unified account name and a unified password of the unified account platform.

[0061] Among them, the unified account name and unified password are the account name and password registered by the user on the unified account platform. The user can log in to the unified account platform using the unified account name and unified password.

[0062] Step 106: Generate a unified account key based on the unified account name and the unified password.

[0063] Specifically, the unified account name and the unified password may be combined or converted according to a preset rule to obtain a unified account key. For example, the unified account name and the unified password may be directly combined into a unified account key, or the combined unified account name and the unified password may be processed according to a preset algorithm to obtain a unified account key.

[0064] Step 107: Save the unified account key to the terminal device used by the user.

[0065] After the unified account key is generated, the unified account key can be fed back to the terminal device and stored by the terminal device.

[0066] Step 108, using the unified account key, encrypt the unified account name and unified password to obtain unified encrypted account information.

[0067] Specifically, a related encryption algorithm (such as AES128 algorithm) can be used to encrypt the unified account name and the unified password based on the unified account key to obtain the unified encrypted account information, which can be stored on the server. The unified encrypted account information can include the encrypted user name and the encrypted password. In this embodiment, the server does not store the unified account key to improve account security.

[0068] This embodiment uses the unified account name and unified password registered by the user to generate a unified account key, and uses the unified account key to encrypt the unified account name and unified password, thereby protecting the unified account name and unified password and improving account security.

[0069] In some optional implementations, such as Figure 4 As shown, step 106 includes:

[0070] Step 1061, extracting password fragments from the unified password according to pre-specified character positions.

[0071] As an example, the unified password is: testAnd78, the pre-specified character positions are the first three digits and the last three digits of the password, and the password fragment is: tesd78.

[0072] Step 1062, combine the unified account name and the password fragment to obtain a unified account key.

[0073] When merging the unified account name and the password fragment, the merging may be performed according to a preset rule, such as directly merging or merging by adjusting the order of characters. For example, assuming that the unified account name is testAccount, after merging the account name with the above password fragment, the obtained unified account key is testAccounttesd78.

[0074] This embodiment obtains a unified account key by extracting a password fragment from the unified password and merging it with the unified account name, thereby establishing a corresponding relationship between the unified account name, the unified password and the unified account key, which helps to improve the efficiency of key generation and the security of account management.

[0075] In some optional implementations, such as Figure 5 As shown, after step 108, the method further includes:

[0076] Step 109 , in response to triggering a login operation to the unified account platform, obtaining a unified account key from the terminal device.

[0077] The user can use the terminal device to log in to the unified account platform, and can enter the unified account name and unified password when logging in. The server receives the input unified account name and unified password, and receives the unified account key.

[0078] Step 110, using the unified account key, decrypt the unified encrypted account information to obtain the unified account name and unified password.

[0079] The server can decrypt the stored unified encrypted account information using the decryption algorithm corresponding to the above encryption algorithm, thereby restoring the unified account name and unified password.

[0080] Step 111, log in to the unified account platform using the unified account name and unified password.

[0081] Specifically, if the restored unified account name and unified password are consistent with the received unified account name and unified password, it is determined that the unified account name and unified password entered by the current user are correct, and the terminal device is allowed to log in to the unified account platform.

[0082] This embodiment can effectively prevent the leakage of the user's unified account information and improve account security by using the unified account key stored in the terminal device and the unified encrypted account information stored in the server to decrypt when the user logs in to the unified account platform.

[0083] In some optional implementations, such as Figure 6 As shown, before step 101, the method further includes:

[0084] Step 112: Obtain the sub-account name and sub-password of the target sub-platform input by the user.

[0085] The user can log in to the unified account platform, use the plug-in corresponding to the target sub-platform, enter the sub-account name and sub-password, and add the account information of the target sub-platform on the unified account platform.

[0086] Step 113, using the unified account key, encrypt the sub-account name and sub-password to obtain sub-account encryption information.

[0087] The encryption rules are the same as the rules for encrypting the unified account name and the unified password in the above embodiment.

[0088] Step 114, binding the correspondence between the sub-account encryption information and the user's unified account name.

[0089] Specifically, the sub-account encryption signal can be recorded on the unified account platform to establish a corresponding relationship between it and the unified account name. When managing the sub-accounts later, you only need to log in to the unified account platform using the unified account name, enter the sub-account name and sub-account password, and use the interface of the target sub-account platform to log in to the target sub-account platform.

[0090] This embodiment uses the above-mentioned unified account key to encrypt the sub-account name and sub-password, so that unified encryption and decryption of accounts of multiple sub-platforms can be achieved on a unified account platform, thereby facilitating unified management of multiple sub-platform accounts on a unified account platform and improving the security of sub-platform account information.

[0091] Figure 7 A schematic diagram of the structure of a unified account management device provided in an embodiment of the present application. Specifically comprising:

[0092] The first acquisition module 701 is used to acquire the pre-stored sub-account encryption information of the target sub-account in response to triggering a management operation on the target sub-account on the unified account platform after the user logs in;

[0093] The second acquisition module 702 is used to acquire a pre-established unified account key;

[0094] The first decryption module 703 is used to decrypt the sub-account encrypted information using the unified account key to obtain the sub-account name and sub-account password of the target sub-account;

[0095] The first sending module 704 is used to send operation information to the target sub-platform through the sub-platform interface corresponding to the target sub-account based on the sub-account name and the sub-account password.

[0096] In some optional implementations, the first acquisition module includes:

[0097] The second sending module is used to send the target plug-in corresponding to the target sub-account to the terminal device used by the user on the unified account platform after the user logs in, so that the terminal device displays the target plug-in;

[0098] The third acquisition module is used to acquire the pre-stored sub-account encryption information of the target sub-account in response to executing the management operation on the target sub-account by using the target plug-in.

[0099] In some optional implementations, the second acquisition module is further used to:

[0100] Obtain a pre-established unified account key from the terminal device used by the user.

[0101] In some optional implementations, the device further includes:

[0102] The fourth acquisition module is used to obtain the unified account name and unified password of the unified account platform;

[0103] A generation module, used to generate a unified account key based on a unified account name and a unified password;

[0104] A saving module, used to save the unified account key to a terminal device used by the user;

[0105] The first encryption module is used to encrypt the unified account name and the unified password using the unified account key to obtain unified encrypted account information.

[0106] In some optional implementations, the generating module includes:

[0107] An extraction unit, used for extracting a password fragment from the unified password according to a pre-specified character position;

[0108] The merging unit is used to merge the unified account name and the password fragment to obtain a unified account key.

[0109] In some optional implementations, the device further includes:

[0110] a fifth acquisition module, configured to acquire a unified account key from a terminal device in response to triggering a login operation to the unified account platform;

[0111] The second decryption module is used to decrypt the unified encrypted account information using the unified account key to obtain the unified account name and unified password;

[0112] The login module is used to log in to the unified account platform using a unified account name and a unified password.

[0113] In some optional implementations, the device further includes:

[0114] The sixth acquisition module is used to obtain the sub-account name and sub-password of the target sub-platform input by the user;

[0115] The second encryption module is used to encrypt the sub-account name and sub-password using the unified account key to obtain sub-account encrypted information;

[0116] The binding module is used to bind the correspondence between the sub-account encryption information and the user's unified account name.

[0117] The unified account management device provided in this embodiment may be as follows Figure 7 The unified account management device shown in can execute all steps of the above unified account management methods, thereby achieving the technical effects of the above unified account management methods. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0118] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, Figure 8 The electronic device 800 shown includes: at least one processor 801, a memory 802, at least one network interface 804 and other user interfaces 803. The various components in the electronic device 800 are coupled together via a bus system 805. It is understood that the bus system 805 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 805 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 805 is not described in detail. Figure 8 Various buses are labeled as bus system 805 .

[0119] The user interface 803 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).

[0120] It can be understood that the memory 802 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 802 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0121] In some implementations, the memory 802 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 8021 and an application program 8022 .

[0122] The operating system 8021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 8022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present application can be included in the application 8022.

[0123] In this embodiment, by calling the program or instruction stored in the memory 802, specifically, the program or instruction stored in the application 8022, the processor 801 is used to execute the method steps provided by each method embodiment, for example, including:

[0124] On the unified account platform after the user logs in, in response to triggering a management operation on the target sub-account, obtain the pre-stored sub-account encryption information of the target sub-account; obtain the pre-established unified account key; use the unified account key to decrypt the sub-account encryption information to obtain the sub-account name and sub-account password of the target sub-account; based on the sub-account name and sub-account password, send operation information to the target sub-platform through the sub-platform interface corresponding to the target sub-account.

[0125] The method disclosed in the above embodiment of the present application can be applied to the processor 801, or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 801. The above processor 801 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software units in the decoding processor can be executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 802, and the processor 801 reads the information in the memory 802 and completes the steps of the above method in combination with its hardware.

[0126] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above functions of the present application, or a combination thereof.

[0127] For software implementation, the technology described above in this article can be implemented by a unit that performs the functions described above in this article. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0128] The electronic device provided in this embodiment may be Figure 8 The electronic device shown in can execute all the steps of the unified account management methods described above, thereby achieving the technical effects of the unified account management methods described above. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0129] The embodiment of the present application also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above-mentioned types of memory.

[0130] When one or more programs in the storage medium can be executed by one or more processors, the unified account management method executed on the electronic device side can be implemented.

[0131] The processor is used to execute the program stored in the memory to implement the following steps of the unified account management method performed on the electronic device side:

[0132] On the unified account platform after the user logs in, in response to triggering a management operation on the target sub-account, obtain the pre-stored sub-account encryption information of the target sub-account; obtain the pre-established unified account key; use the unified account key to decrypt the sub-account encryption information to obtain the sub-account name and sub-account password of the target sub-account; based on the sub-account name and sub-account password, send operation information to the target sub-platform through the sub-platform interface corresponding to the target sub-account.

[0133] The professionals should further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different circuits to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0134] The steps of the circuits or algorithms described in conjunction with the embodiments disclosed herein may be implemented using hardware, software modules executed by a processor, or a combination of the two. The software modules may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0135] It should be understood that the terms used in the text are only for the purpose of describing specific example embodiments, and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used in the text may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The steps, processes, and operations described in the text are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0136] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A unified account management method, characterized in that: The method comprises: On the unified account platform after the user logs in, in response to triggering a management operation on a target sub-account, obtaining pre-stored sub-account encryption information of the target sub-account; Obtain a pre-established unified account key; Using the unified account key, decrypt the sub-account encrypted information to obtain the sub-account name and sub-account password of the target sub-account; Based on the sub-account name and the sub-account password, the operation information is sent to the target sub-platform through the sub-platform interface corresponding to the target sub-account.

2. The method according to claim 1, characterized in that The unified account platform after the user logs in, in response to triggering a management operation on a target sub-account, obtains the pre-stored sub-account encryption information of the target sub-account, including: After the user logs in, the unified account platform sends the target plug-in corresponding to the target sub-account to the terminal device used by the user, so that the terminal device displays the target plug-in; In response to using the target plug-in to perform a management operation on a target sub-account, pre-stored sub-account encryption information of the target sub-account is obtained.

3. The method according to claim 1, characterized in that The obtaining of the pre-established unified account key includes: A pre-established unified account key is obtained from a terminal device used by the user.

4. The method according to claim 3, characterized in that Before the unified account platform after the user logs in, in response to triggering a management operation on a target sub-account, obtains the pre-stored sub-account encryption information of the target sub-account, the method further includes: Obtaining a unified account name and a unified password of the unified account platform; Generate a unified account key based on the unified account name and the unified password; Saving the unified account key to a terminal device used by the user; The unified account name and the unified password are encrypted using the unified account key to obtain unified encrypted account information.

5. The method according to claim 4, characterized in that The generating a unified account key based on the unified account name and the unified password includes: Extracting password fragments from the unified password according to pre-specified character positions; The unified account name and the password fragment are combined to obtain the unified account key.

6. The method according to claim 4, characterized in that After the unified account name and the unified password are encrypted using the unified account key to obtain unified encrypted account information, the method further includes: In response to triggering a login operation to the unified account platform, obtaining the unified account key from the terminal device; Decrypting the unified encrypted account information using the unified account key to obtain the unified account name and the unified password; Use the unified account name and the unified password to log in to the unified account platform.

7. The method according to claim 1, characterized in that Before the unified account platform after the user logs in, in response to triggering a management operation on a target sub-account, obtains the pre-stored sub-account encryption information of the target sub-account, the method further includes: Obtaining the sub-account name and sub-password of the target sub-platform input by the user; Using the unified account key, encrypting the sub-account name and the sub-password to obtain the sub-account encrypted information; Bind the correspondence between the sub-account encryption information and the user's unified account name.

8. A unified account management device, characterized in that: The device comprises: A first acquisition module is used to acquire the pre-stored sub-account encryption information of the target sub-account in response to triggering a management operation on the target sub-account on the unified account platform after the user logs in; A second acquisition module is used to acquire a pre-established unified account key; A first decryption module, configured to use the unified account key to decrypt the sub-account encrypted information to obtain the sub-account name and sub-account password of the target sub-account; The first sending module is used to send operation information to the target sub-platform through the sub-platform interface corresponding to the target sub-account based on the sub-account name and the sub-account password.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor is used to execute the computer program stored in the memory, and when the computer program is executed, the unified account management method described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the unified account management method described in any one of claims 1 to 7 is implemented.

Images