Information processing method and device, electronic equipment and storage medium

Abstract

Embodiments of the present invention provide an information processing method, apparatus, electronic device, and storage medium. The method includes: acquiring available function entry information for multiple login accounts, the login accounts including a currently controlling account and non-controlling accounts; displaying a set of available function entry points in a first graphical user interface corresponding to the currently controlling account based on the available function entry information; responding to a trigger operation targeting a target function entry point in the function entry point set, displaying a first function interface corresponding to the target function entry point in the first graphical user interface, the first function interface being generated based on game data of the currently controlling account; responding to an account selection instruction, selecting a target account from non-controlling accounts; and displaying a second function interface corresponding to the target function entry point in the first graphical user interface, the second function interface being generated based on game data of the target account. By aggregating and displaying the available function entry points of all login accounts in the interface of the currently controlling account, when a user triggers a function entry point, the system can directly generate the corresponding interface based on the game data of the target account, thus completing multi-account operations without switching accounts, reducing operation steps, and lowering resource consumption caused by frequent account switching on the terminal.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer user interface interaction, and more specifically, the embodiments of the present invention relate to an information processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] This section is intended to provide background or context for embodiments of the invention as set forth in the claims. The description herein is not intended to imply that it is prior art simply because it is included in this section.

[0003] As application functions become more abundant and user needs become more diverse, it is becoming increasingly common for users to log in to multiple accounts simultaneously on the same terminal device.

[0004] In related technologies, when a user needs to perform functional operations on multiple logged-in accounts, they usually need to complete the operation in the interface of the currently controlled account first, then switch to another account, re-enter the same functional interface, and perform the operation again, and so on, until all accounts have completed the corresponding operation. Summary of the Invention

[0005] In scenarios involving multiple account logins, different accounts typically have independent function entry points and corresponding function interfaces. Users need to access the corresponding function interface and perform operations for each account separately. Under the aforementioned related technologies, switching accounts is required before performing any operation. Each account switch involves a complete reloading and rendering of the interface, which not only increases the data processing burden and graphics rendering resource consumption of the terminal device, but also forces users to perform a large number of repetitive interface navigation and operation steps, resulting in low operational efficiency. Furthermore, frequent interface switching can easily lead to operational confusion for users and increase the risk of misoperation.

[0006] In this context, embodiments of the present invention aim to provide an information processing method, apparatus, electronic device, and storage medium to at least partially solve the aforementioned problems existing in the related art.

[0007] In a first aspect of the present invention, an information processing method is provided, the method comprising: acquiring available function entry information of multiple login accounts, the login accounts including a currently controlled account and non-controlled accounts; displaying a set of available function entry points in a first graphical user interface corresponding to the currently controlled account according to the available function entry information; responding to a trigger operation for a target function entry point in the set of function entry points, displaying a first function interface corresponding to the target function entry point in the first graphical user interface, the first function interface being generated based on game data of the currently controlled account; responding to an account selection instruction, selecting a target account from the non-controlled accounts; and displaying a second function interface corresponding to the target function entry point in the first graphical user interface, the second function interface being generated based on game data of the target account.

[0008] In a second aspect of the present invention, an information processing apparatus is provided, comprising: an acquisition module for acquiring available function entry information of multiple login accounts, the login accounts including a currently controlled account and non-controlled accounts; a function entry display module for displaying a set of available function entry points in a first graphical user interface corresponding to the currently controlled account based on the available function entry information; a function interface display module for displaying a first function interface corresponding to the target function entry point in the first graphical user interface in response to a trigger operation on a target function entry point in the function entry set, the first function interface being generated based on game data of the currently controlled account; an account selection module for selecting a target account from non-controlled accounts in response to an account selection instruction; and the function interface display module further for displaying a second function interface corresponding to the target function entry point in the first graphical user interface, the second function interface being generated based on game data of the target account.

[0009] In a third aspect of the present invention, an electronic device is provided, comprising: a memory storing computer-executable instructions executable by a processor; and a processor for executing the computer-executable instructions to perform the steps of any of the above-described information processing methods.

[0010] In a fourth aspect of the present invention, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of any of the above-described information processing methods.

[0011] The technical solution provided in this disclosure aggregates and displays the available function entry points of all logged-in accounts in the interface of the currently controlled account. When a user triggers a function entry point, the system can directly generate the corresponding interface based on the game data of the target account. This allows for multi-account operations to be completed without switching accounts, reducing operation steps and lowering resource consumption caused by frequent account switching on the terminal. Attached Figure Description

[0012] The above and other objects, features, and advantages of exemplary embodiments of the present invention will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings. Several embodiments of the invention are illustrated in the drawings by way of example and not limitation, wherein: Figure 1 This is a schematic diagram illustrating the implementation environment of an information processing method provided in this embodiment of the disclosure. Figure 2 A flowchart of an information processing method provided in an embodiment of this disclosure; Figure 3 A schematic diagram of an interface for displaying a set of function entry points, provided as an embodiment of this disclosure; Figure 4This is a schematic diagram illustrating a functional interface switching display provided in an embodiment of this disclosure; Figure 5 A schematic diagram of another set of display function entry points provided in an embodiment of this disclosure; Figure 6 This is a schematic diagram illustrating an account switching process provided in an embodiment of this disclosure; Figure 7 A schematic diagram of an interface for displaying an account switching control provided in an embodiment of this disclosure; Figure 8 This is a schematic diagram illustrating the settings for enabling a multi-account compatibility mode according to an embodiment of the present disclosure. Figure 9 This is a schematic diagram of the structure of an information processing device provided in an embodiment of the present disclosure; Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure.

[0013] In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present disclosure, the technical solutions of the present disclosure will be clearly and completely described below with reference to the accompanying drawings of the embodiments. Obviously, the described embodiments are only some embodiments of the present disclosure, and not all embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present disclosure.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] The accompanying drawings are schematic illustrations of this disclosure and are not necessarily drawn to scale. Some block diagrams shown in the drawings may be functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in hardware modules or integrated circuits, or in networks, processors, or microcontrollers. Implementations can be carried out in various forms and should not be construed as limited to the examples set forth herein. The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough description of embodiments of this disclosure. However, those skilled in the art will recognize that one or more specific details may be omitted when implementing the technical solutions of this disclosure, or other methods, components, apparatuses, steps, etc., may be used to replace one or more specific details.

[0017] Figure 1 A system architecture diagram of the operating environment of this exemplary embodiment is shown. This system architecture may include a terminal device 110 and a server 120. The terminal device 110 may be a mobile phone, tablet computer, personal computer, smart wearable device, game console, etc., and has a display function capable of displaying a graphical user interface, which may include the operating system interface or the application interface. An application, such as a game program, is installed on the terminal device 110. The server 120 generally refers to the backend system providing application services in this exemplary embodiment; it may be a single server or a cluster of multiple servers. For example, a game server program is deployed on the server 120 to perform server-side game data processing. The terminal device 110 and the server 120 can be connected via a wired or wireless communication link for data transmission. The method in one exemplary embodiment of this disclosure can be executed by any one or more of the terminal device 110 and the server 120.

[0018] In one implementation, the above method can be implemented and executed based on a cloud interaction system. The cloud interaction system can be the system architecture described above. Various cloud applications, such as cloud gaming, can run under the cloud interaction system. Taking cloud gaming as an example, cloud gaming can be a game mode based on cloud computing. In the cloud gaming operation mode, the game program's execution entity and the game screen presentation entity are separated. The storage and execution of the game's control and interaction methods are completed on the cloud gaming server (such as the aforementioned server 120). The cloud gaming client (such as the aforementioned terminal device 110) is responsible for receiving and sending data and presenting the game screen. For example, the cloud gaming client can be a display device with data transmission capabilities located close to the user, such as a mobile terminal, television, computer, or PDA; while the cloud gaming server in the cloud performs information processing. When playing the game, the user operates the cloud gaming client to send operation commands to the cloud gaming server. The cloud gaming server runs the game according to the operation commands, encodes and compresses the game screen and other data, returns it to the cloud gaming client via the network, and finally, the cloud gaming client decodes and outputs the game screen.

[0019] In one implementation, the method described above can be implemented by the terminal device 110 alone. For example, without deploying the server 120, the terminal device 110 can run the application in a standalone environment to implement the game function and execute the method described above.

[0020] This embodiment provides an information processing method. Figure 2 This is a flowchart of an information processing method according to an embodiment of the present disclosure, such as... Figure 2 As shown, the process includes the following steps: Step S110: Obtain available function entry information for multiple login accounts, including the currently controlling account and non-controlling accounts.

[0021] Step S120: Based on the available function entry information, display the set of available function entry points in the first graphical user interface corresponding to the current control account.

[0022] Step S130: In response to the trigger operation for the target function entry in the function entry set, display the first function interface corresponding to the target function entry in the first graphical user interface. The first function interface is generated based on the game data of the current control account.

[0023] Step S140: In response to the account selection instruction, select the target account from the non-controlled accounts.

[0024] Step S150: Display the second function interface corresponding to the target function entry in the first graphical user interface. The second function interface is generated based on the game data of the target account.

[0025] In scenarios involving multiple account logins, related technologies provide the ability to switch between accounts to access different user interfaces. However, each account switch requires reloading application data and re-rendering the interface, which is not only cumbersome but also increases the consumption of computing resources and data processing pressure on the terminal device, as well as the waiting time. The method provided in this embodiment enables users to view and trigger function entry points for multiple accounts simultaneously in scenarios where multiple accounts are logged in. By acquiring the available function entry information for multiple logged-in accounts and displaying the set of available function entry points uniformly in the first graphical user interface of the currently controlled account, users can centrally view and trigger function entry points for multiple accounts in a single interface. This avoids the tedious operation of repeatedly locating the same function entry point after switching accounts one by one, and reduces the risk of operation confusion and misoperation caused by frequent interface switching. At the same time, after responding to the trigger operation and displaying the first function interface generated based on the game data of the currently controlled account in the first graphical user interface, the method further responds to the account selection command to select the target account from the non-controlled accounts and directly displays the second function interface generated based on the game data of the target account in the first graphical user interface. This allows users to access and operate the function interfaces of different accounts in the same interface without switching the current controlled account, thereby improving the smoothness and efficiency of multi-account management and optimizing the interactive experience. In addition, the entire process is always completed in the first graphical user interface of the currently controlled account, without triggering the overall reconstruction of the interface, data reloading, and graphics re-rendering due to account switching, effectively reducing the consumption of computing resources and data processing pressure on the terminal device.

[0026] The steps described above are explained in detail below.

[0027] In step S110, the available function entry information of multiple login accounts is obtained. The login accounts include the current control account and non-control accounts.

[0028] Optionally, a login account refers to multiple user accounts that have been successfully logged in on the same terminal device or application client. These accounts can be running in the background or active in the foreground. An account is an independent login credential within the same application, and each account corresponds to independent user-related data. Taking a game application as an example, each account represents an independent game character, and each account corresponds to independent game data (character level, equipment, items, etc.), independent game progress (task completion status, activity participation status, etc.), and independent functional permissions (unlocking different functions based on level, recharge status, etc.).

[0029] Optionally, the currently controlling account refers to the account that the user is currently directly interacting with and controlling. The interface currently displayed on the client is the interface corresponding to this currently controlling account. Taking a game as an example, the currently controlling account is the game account that the player is currently controlling, and the interface displayed on the client includes the game screen corresponding to the currently controlling account (such as game scenes, game characters, character control controls, etc.).

[0030] Optionally, non-controlled accounts refer to accounts that are logged in but not under foreground control, other than the currently controlled account. These accounts can maintain a data connection in the background. The main interface will not render or display the game screen of non-controlled accounts, and players cannot perform certain game operations on those non-controlled accounts.

[0031] Optionally, available function entry information represents the specific functions or task interfaces that each account can access under the current login status, such as check-in, store, or event entry. Different accounts may have different available function entry points due to differences in user status. For example, game accounts at different game progress or level statuses may have different available function modules.

[0032] In step S120, based on the available function entry information, the set of available function entry points is displayed in the first graphical user interface corresponding to the current control account.

[0033] Optionally, the first graphical user interface (GUI) is the front-end interactive interface corresponding to the currently controlling account, used to display the game screen content and various function entry points for the currently controlling account. The first GUI is rendered and generated based on the application's basic resource data and the user data of the currently controlling account.

[0034] Optionally, the set of available function entry points is the union of all available function entry points for all logged-in accounts, presented as a unified view element in the first graphical user interface, allowing users to access multiple account-related function entry points in a single interface.

[0035] In step S130, in response to a trigger operation targeting a target function entry in the function entry set, a first function interface corresponding to the target function entry is displayed in the first graphical user interface. The first function interface is generated based on the game data of the current control account.

[0036] Optionally, the triggering operation is an interactive command such as clicking or touching the target function entry in the graphical interface, which is used to initiate a request to open the corresponding function interface.

[0037] Optionally, the first functional interface is a display of specific content and an operation panel associated with the target function entry, and its data content comes from the current control account.

[0038] Optionally, game data refers to the status, resources, and progress information bound to a specific account, which is used to generate and populate the specific content of the function interface.

[0039] In step S140, in response to the account selection instruction, the target account is selected from the non-control accounts.

[0040] Optionally, the account selection command is an operation command issued by the user after the first functional interface is displayed to select a non-controlled account, used to specify the target account whose functional interface needs to be viewed or operated.

[0041] Optionally, the target account is one or more accounts selected from non-controlled accounts, and the user intends to view or operate the interface corresponding to the target function of these accounts.

[0042] In step S150, a second function interface corresponding to the target function entry is displayed in the first graphical user interface. The second function interface is generated based on the game data of the target account.

[0043] Optionally, the second functional interface is the functional interface displayed in the first graphical user interface that corresponds to the target functional entry. The second functional interface is of the same type as the first functional interface but has a different data source. Its content is dynamically generated based on the game data of the selected target account. Related technologies require an account switching operation to display the functional interfaces of different accounts. This requires obtaining complete data of different accounts from the server and then re-rendering and generating the main interface of the switched account on the terminal before selecting the functional interface corresponding to the functional entry. However, this implementation does not require switching the current control account. It only needs to obtain the user data related to the functional entry under the target account and directly generate the functional interface of the target account in the main interface of the current account (first graphical user interface), thereby improving the operation efficiency and reducing the data transmission and processing pressure on the terminal.

[0044] In a specific application of this embodiment, see Figure 3 and Figure 4 The player simultaneously logged into three game accounts on a mobile device. Account A is the currently controlling account, while accounts B and C are non-controlling accounts. The terminal device obtains the available function access information for each of the three logged-in accounts, such as... Figure 3 As shown in (a), all entry points are centrally displayed on the main interface of account A, such as Figure 3 As shown in (b). When a player clicks on the "Benefits" entry, the terminal device responds to the trigger operation and displays the first functional interface corresponding to the benefits entry in the first graphical user interface. This first functional interface displays content generated based on account A's game data, such as the benefits claiming status of account A and the available benefits. Figure 4As shown in (a). The user then issues an account selection command, choosing account B as the target account from the non-controlled accounts. The terminal device displays a second functional interface corresponding to the welfare entry in the first graphical user interface. This second functional interface displays content generated based on account B's game data, such as the welfare claiming status of account B and the available welfare items. Figure 4 As shown in (b). Throughout the process, account A remains the currently controlling account, and the first graphical user interface does not switch over. The user can view the benefits interface of account B from the interface of account A.

[0045] In an optional implementation, the set of available function entry points includes the union of the available function entry points for all logged-in accounts. This way, by unifying the function entry points of multiple accounts into a complete view, users can intuitively grasp the available operation options for all accounts without having to switch between them individually, significantly reducing the risk of information omission and improving operational efficiency.

[0046] For example, see Figure 3 The user logged into three game accounts simultaneously on the same terminal device: Account A, Account B, and Account C, with Account A being the currently controlling account. Figure 3 (a) Displays the available function entry points for accounts A, B, and C. After obtaining the available function entry point information for each of the three accounts, the system takes the union of the available function entry points for all logged-in accounts and displays this set completely in the first graphical user interface corresponding to account A, such as... Figure 3 As shown in (b), the two function entrances, "Growth Gift" and "First Recharge Gift Pack", which are available for account C, were not originally available in account A. After being merged, they are displayed in the function entrance collection window on the current homepage of account A, so that users can see the function entrances that were not originally displayed separately in the account A interface without switching to account B or account C.

[0047] Optionally, the union refers to the set obtained by combining and summarizing the available function entry points of multiple login accounts and removing duplicates. Specifically, in scenarios where multiple accounts are logged in simultaneously, each login account may have different available function entry points due to differences in their game progress, character level, completed tasks, or unlocked content. For example, one account may have unlocked the advanced event entry point because of its higher character level, while another account, although at a lower level, has a dedicated reward claim entry point because it has completed a specific task. Taking the union of these function entry points means collecting all the function entry points owned by each account, and retaining only one instance of the same function entry point shared by multiple accounts, ultimately forming a complete set that covers all available function entry points of all accounts. Taking three accounts as an example, if account A has access to sign-in and email, account B has access to sign-in and events, and account C has access to email, events, and the store, then the union of these three is the four function entry points: sign-in, email, events, and the store. Although sign-in and email are shared by multiple accounts, each appears only once in the union.

[0048] Optionally, a mapping relationship exists between the function entry points in the union and each login account. While constructing the union, the system can maintain a mapping record that records which login accounts possess each function entry point. For example, the mapping record for the check-in entry point includes accounts A, B, and C, indicating that all three accounts can use the check-in entry point; while the mapping record for the e-commerce entry point only includes account C, indicating that only account C can use the e-commerce entry point. This mapping record can be invoked in subsequent interaction flows. For instance, when a user triggers a function entry point, the system can determine which accounts can use that entry point based on the mapping record, thus providing data support for subsequent account selection.

[0049] Optionally, when the available function entry points for one of the multiple logged-in accounts change, the system can dynamically update the union of the available function entry points. Situations where available function entry points change include, but are not limited to: an account gaining a new available function entry point by completing a specific game task, an account losing an available function entry point due to the expiration of an event, or an account unlocking a new function entry point due to a character level increase. In these cases, the system can re-obtain the available function entry point information for the account whose information has changed and recalculate the union of available function entry points for all logged-in accounts based on the updated information.

[0050] In an optional implementation, based on the available function entry information, a set of available function entry points is displayed in the first graphical user interface corresponding to the current control account. This includes: determining, based on the available function entry information, a first type of function entry point available to the current control account and a second type of function entry point that is unavailable, wherein the second type of function entry point is available to at least one non-control account; and visually differentiating the first type of function entry point and the second type of function entry point within the set of available function entry points. This visual differentiation mechanism allows users to intuitively identify currently operable function entry points and those requiring account switching, reducing the risk of accidental touches and improving the accuracy of information delivery through the interface.

[0051] For example, see Figure 5 In a game application that supports simultaneous login of multiple accounts, a user simultaneously logs in with account A, account B, and account C on the same terminal device, with account A being the currently controlling account. After the system obtains the available function access information for each of the three accounts, such as... Figure 5 As shown in (a); simultaneously, it is determined that account A is unavailable but account C is available, including the "Growth Gift" entry and the "First Recharge Gift Pack" entry. These two entries are classified as the second type of function entry. Subsequently, the system displays the set of available function entry points containing the above five function entry points in the first graphical user interface corresponding to account A. The "Growth Gift" entry and the "First Recharge Gift Pack" entry are displayed with a semi-transparent visual effect, while other function entry points are displayed with normal icon brightness and color, as shown in (a). Figure 5 As shown in (b), this allows users to clearly distinguish between function entries that can be directly used by the current control account and function entries that require other accounts to use.

[0052] Optionally, the first type of function entry point refers to those function entry points within the set of available function entry points that the currently controlling account has the permission to use. Specifically, due to differences in the current controlling account's game character level, completed task progress, unlocked game content, or specific conditions, a subset of function entry points can be used to access the corresponding function interface and perform operations. The second type of function entry point refers to those function entry points within the set of available function entry points that the current controlling account does not have the permission to use, but at least one non-controlling account does. In other words, the second type of function entry point is not a member of the currently controlling account's list of available function entry points, but rather originates from the list of available function entry points of one or more non-controlling accounts. In scenarios involving multiple accounts logging in concurrently, although the currently controlling account cannot directly use the second type of function entry point, it still has the potential to be accessed and operated within the overall multi-account operation process.

[0053] Optionally, visual differentiation refers to using different visual representations for the first and second types of functional entry points in the interface presentation of the available functional entry point set, making them visually distinct. Specific implementations of visual differentiation can include various forms. For example, rendering the second type of functional entry point with a semi-transparent effect, making its icon and text opacity lower than that of the first type of functional entry point, thus presenting a faded or weakened visual impression; another example is overlaying a gray mask on the icon of the second type of functional entry point, making its overall tone darker, contrasting with the normal color of the first type of functional entry point; yet another example is adding a specific identifier (such as a small lock icon or a badge indicating that other accounts are available) to the corner of the icon of the second type of functional entry point to distinguish it from the unmarked state of the first type of functional entry point. Furthermore, visual differentiation can also be achieved by adjusting the border style of the icons, for example, using a solid border for the icon of the first type of functional entry point and a dashed border for the icon of the second type of functional entry point. This disclosure does not limit this aspect.

[0054] In an optional implementation, responding to a trigger operation targeting a target function entry in the set of function entry points, displaying a first function interface corresponding to the target function entry in the first graphical user interface includes: responding to a trigger operation targeting a target function entry in the first type of function entry points, and displaying the first function interface corresponding to the target function entry in the first graphical user interface. This way, by limiting the trigger response to only the first type of entry points available to the current account, interface confusion caused by accidental unavailability of entry points is avoided, improving operational accuracy.

[0055] Optionally, in scenarios where both the first and second types of function entry points coexist in the set of available function entry points, the generation of the first function interface is limited to being triggered by the first type of function entry point, creating a differentiated response path from the processing flow when the second type of function entry point is triggered. When the triggered target function entry point belongs to the first type of function entry point, the system directly generates and displays the first function interface based on the game data of the currently controlling account in the first graphical user interface. This process does not involve changes or switching of account identity, and the currently controlling account always maintains its control state. In the specific implementation, after receiving the trigger operation, the system can first verify the current controlling account's usage permissions for the target function entry point. After confirming that the current controlling account does indeed have access permissions for the function entry point, it will then perform the query of game data and the rendering of the interface.

[0056] In an optional implementation, responding to an account selection instruction and selecting a target account from non-controlled accounts includes: displaying an account switching control in a first functional interface, the account switching control being used to display non-controlled accounts; and responding to a selection operation on the account switching control and selecting the target account from the non-controlled accounts. This allows users to conveniently select other accounts directly from the first functional interface using the account switching control, without leaving the current interface or performing complex navigation operations, thus simplifying the process of cross-account function access.

[0057] For example, see Figure 4 In a game application that supports simultaneous login of multiple accounts, a user simultaneously logs in with accounts A, B, and C on the same terminal device, with account A being the currently controlling account. The user triggers the check-in entry in the first graphical user interface corresponding to account A. The system then displays the first functional interface corresponding to the check-in entry in the first graphical user interface, such as... Figure 4 As shown in (a), the system displays an account switching control in the upper left corner of the first functional interface. This control lists the account identifiers (virtual character avatars) for accounts A, B, and C. When the user clicks the identifier corresponding to account B in the account switching control, the system responds to the selection operation, identifies account B as the target account, and then displays the second functional interface corresponding to the check-in entry, generated based on the game data of account B, in the first graphical user interface. Figure 4 As shown in (b).

[0058] Optionally, the account switching control is an interactive component embedded in the first functional interface. Its main function is to provide users with an intuitive and convenient channel to access or manipulate the data or status of other logged-in accounts within the same functional module. The presentation of this control can be arbitrarily set as needed, such as an expandable list, a set of side-by-side icons, or a drop-down menu. Its content can include the currently controlling account and other logged-in accounts. In its design and implementation, this control needs to accurately obtain and display the identification information of all currently logged-in accounts, such as account avatars, nicknames, or specific identifiers, ensuring that users can clearly distinguish between different accounts.

[0059] Optionally, the timing of the account switching control's display in the first functional interface can be coordinated with the loading process of the first functional interface. In one implementation, when the system responds to a user's trigger operation targeting the target functional entry point and begins generating and displaying the first functional interface, the system simultaneously loads the non-control account data required by the account switching control, and displays the account switching control synchronously in the first functional interface after the first functional interface is rendered, so that the user can see the account switching control at the same time as seeing the first functional interface. In another implementation, the system first completes the rendering and display of the first functional interface, and then, when multiple logged-in accounts are detected, slides or fades the account switching control from the edge of the first functional interface with an animation transition. In yet another implementation, the account switching control is hidden by default, and only appears after the user performs a specific trigger operation in the first functional interface (such as clicking an account management button). The specific display timing can be flexibly determined based on the number of logged-in accounts, the complexity of the first functional interface, and the performance of the terminal device.

[0060] In an optional implementation, the method further includes: responding to a trigger operation targeting a target function entry in the second type of function entry, displaying an account switching prompt message, the prompt message indicating the availability of a first type of non-controlled account for the target function entry; responding to an account switching confirmation command, switching the target non-controlled account selected from the first type of non-controlled accounts to the current controlled account and switching the current controlled account to a non-controlled account; switching the first graphical user interface to display a second graphical user interface corresponding to the target non-controlled account; and displaying a third function interface corresponding to the target function entry in the second graphical user interface, the third function interface being generated based on the game data of the target non-controlled account. Thus, when a user unintentionally or intentionally triggers a function entry that is unavailable to the current account but available to other accounts, a clear prompt and confirmation mechanism guides the user to complete the automatic account switching, and the function is directly displayed in the new main account interface after the switch, enabling the user to access and operate functions that were previously unavailable due to permission restrictions, thereby improving the continuity and efficiency of the operation.

[0061] For example, see Figure 6 In a game application that supports simultaneous login of multiple accounts, a user simultaneously logs in to account A, account B, and account C on the same terminal device, with account A being the currently controlling account. Based on available function entry information, the system determines that the second type of function entry points unavailable for account A include the growth gift entry and the first recharge gift pack entry, and visually differentiates these two types of function entry points within the set of available function entry points, such as... Figure 6As shown in (a), when a user clicks on the semi-transparent "Growth Ceremony" entry, the system responds to this trigger by displaying an account switching prompt window. The pop-up window states that the current account cannot use the Growth Ceremony feature and lists account C as the first category of non-controlled accounts that can use this feature. It also provides confirmation and cancellation buttons. Figure 6 As shown in (b). When the user clicks the confirmation button, the system responds to the account switch confirmation command, switching account C to the currently controlled account and account A to the non-controlled account. Subsequently, the first graphical user interface switches to the second graphical user interface corresponding to account C, and displays the third functional interface corresponding to the growth gift entry within the second graphical user interface. This third functional interface is generated based on the game data of account C, displaying the growth gift claim status and reward content for account C, such as... Figure 6 As shown in (c).

[0062] Optionally, the account switching notification can be displayed as a pop-up window in the first graphical user interface, containing the notification text, a list of available accounts, and confirmation and cancellation buttons. In another implementation, the account switching notification can also be presented as a bottom sliding panel, with the panel displaying the identifiers and brief information of each type of non-control account in a card-style layout.

[0063] Optionally, the first type of non-controlled account refers to those non-controlled accounts that have permission to use the target function entry point among all non-controlled accounts. After a user triggers the second type of function entry point, the system needs to filter out a subset of accounts from the non-controlled accounts that can use the function entry point; this subset is the first type of non-controlled account.

[0064] Optionally, the account switching confirmation command is generated when the user confirms the account switching prompt after viewing the information. This command carries the identifier information of the target non-controlled account selected by the user. In one specific implementation, when there are multiple first-category non-controlled accounts, the account switching prompt can provide a radio button list or clickable account cards for the user to select a target non-controlled account before performing the confirmation operation. When there is only one first-category non-controlled account, the account switching prompt can directly display the information of that unique first-category non-controlled account, and the user only needs to perform a confirmation or cancellation operation.

[0065] Optionally, the second graphical user interface (GUI) is the main game interface corresponding to the target non-controlling account after it switches to the current controlling account. The third functional interface is the functional interface displayed in the second GUI that corresponds to the target functional entry. After the account identity switch is completed, the system switches the first GUI to the second GUI. This switching process involves a complete replacement of the interface rendering content, including switching the game scene from the current controlling account's scene to the target non-controlling account's scene, updating the character information bar at the top of the interface from the original account's character information to the target non-controlling account's character information, and recalculating and displaying the set of available functional entries based on the new current controlling account. After the second GUI completes rendering and display, the system further automatically opens the third functional interface corresponding to the target functional entry in the second GUI. The content of the third functional interface is generated based on the game data of the target non-controlling account (which is now the current controlling account). It can be seen that when an account switch is required, the terminal needs to obtain all the game data of the account being switched and reprocess and render it on the terminal. In some cases, it is necessary to remodel and render the virtual character and game scene, which increases the terminal's resource consumption and waiting time.

[0066] In an optional implementation, an account switching control is displayed in the first functional interface, including: determining a first type of non-controlled account for the available target functional entry based on the available functional entry information; and displaying the account identifier corresponding to the first type of non-controlled account in the account switching control. This allows users to directly identify which non-controlled accounts are available for the current functional operation in the account switching control, avoiding the tedious process of blindly selecting from all logged-in accounts and improving the accuracy and efficiency of cross-account operations.

[0067] For example, in a game application that supports simultaneous login of multiple accounts, a user logs in to account A, account B, and account C simultaneously on the same terminal device, with account A being the currently controlling account. The user triggers the "Holiday Event" entry in the first graphical user interface corresponding to account A, and the system displays the first functional interface corresponding to the check-in entry in the first graphical user interface. Subsequently, the system checks the available functional entry lists of each non-controlling account based on the available functional entry information. It finds that account B's available functional entry list includes the "Holiday Event" entry while account C's does not, thus identifying account B as the first type of non-controlling account. The account switching control displayed in the first functional interface shows the account identifiers of account A and account B, each containing a thumbnail of their respective character avatar, while account C is not displayed in the account switching control.

[0068] Optionally, determining the first category of non-controlled accounts for available target function entry points based on available function entry point information refers to the system using the target function entry point as a filtering condition to search for a subset of non-controlled accounts with permission to use that target function entry point. Specifically, the system extracts the identifier information of the target function entry point from the available function entry point information, and then checks the available function entry point list of each non-controlled account one by one to determine whether the list of each non-controlled account contains an entry that matches the identifier of the target function entry point. For non-controlled accounts whose lists contain such entries, the system classifies them as first category non-controlled accounts.

[0069] Optionally, the number of Category 1 non-controlled accounts depends on the individual game status of each non-controlled account and the access conditions of the target function entry. Under different function entry points, the members belonging to Category 1 non-controlled accounts in the same batch of non-controlled accounts may be completely different. In extreme cases, if all non-controlled accounts cannot access the target function entry point, then Category 1 non-controlled accounts will be an empty set. In this case, the account switching control can only display the identifier of the currently controlled account, or display a message that no accounts are available.

[0070] Optionally, account identifiers can take various forms to present the identity information of non-controlled accounts. From a textual perspective, account identifiers can include the non-controlled account's nickname or character name. From a graphical perspective, account identifiers can include a thumbnail of the non-controlled account's currently used game character's avatar or a small icon of the character's portrait, allowing users to quickly identify the account through visual appeal.

[0071] Optionally, the entire process of identifying the first type of non-controlled accounts and displaying their account identifiers in the account switching control is integrated with the generation and display process of the first functional interface. Simultaneously or subsequently, when the system responds to a user's trigger operation targeting the target functional entry and begins generating the first functional interface, the system initiates the process of identifying the first type of non-controlled accounts, querying and filtering available non-controlled accounts for the target functional entry from the available functional entry information. After identifying the first type of non-controlled accounts, the system obtains the account identifier data (including avatar image resources, nickname text, etc.) for each first type of non-controlled account, passes this data to the rendering module of the account switching control, and the rendering module generates the display content of the account switching control based on a preset control layout template and the account identifier data, embedding the generated account switching control into a specified position in the first functional interface for display.

[0072] In an optional implementation, responding to a selection operation on the account switching control and selecting a target account from non-controlled accounts includes: responding to a selection operation on an account identifier in the account switching control and determining the non-controlled account corresponding to the selected account identifier as the target account. This simplifies the user's selection process in a multi-account environment by directly associating the account identifier with the target account, improving the intuitiveness and accuracy of the operation.

[0073] For example, such as Figure 4 As shown in (a), account A is the currently controlling account. The "Benefits" function interface for account A displays an account switching control, which shows identifiers for accounts A, B, and C that are currently available for the function entry point. Figure 4 As shown in (b), after the user selects the identifier of account B, the system immediately confirms that the non-control account B corresponding to the identifier is the target account and loads the corresponding welfare interface data on the current interface.

[0074] Optionally, the selection operation for an account identifier in the account switching control refers to the interactive behavior of a user selecting a specific account identifier within the control. On touchscreen devices, users can directly tap the display area occupied by an account identifier in the account switching control with their finger to perform the selection operation. On devices using a mouse, users can hover the mouse cursor over the display area of ​​the target account identifier, at which point the account identifier will be highlighted visually, and the user can then complete the selection by clicking the mouse. On devices using a gamepad, users can use the arrow keys to move the focus among multiple account identifiers in the account switching control, and press the confirmation button when the focus is on the target account identifier to complete the selection operation.

[0075] Optionally, when the account switching control displays multiple account identifiers for the first type of non-controlled accounts, the user can switch between different account identifiers. For example, if the user first clicks on the account identifier for account B, the system will identify account B as the target account and generate a second functional interface based on account B's game data. Subsequently, the user can click on the account identifier for account D again in the account switching control. The system will respond to this new selection, identify account D as the new target account, and update the currently displayed second functional interface with the interface content generated based on account D's game data.

[0076] In an optional implementation, an account switching control is displayed in the first functional interface, including: determining a first type of non-controlled account for available target functional entry points and a second type of non-controlled account for unavailable target functional entry points based on available functional entry information; and visually differentiating the account identifiers corresponding to the first type of non-controlled accounts and the second type of non-controlled accounts in the account switching control. In this way, by distinguishing between the account identifiers that support and do not support the current functional entry point, users can intuitively identify the available accounts for the operable target, reducing unnecessary operations and improving the accuracy of information conveyed through the interface.

[0077] For example, see Figure 7 When a user enters the "Benefits Claim" function interface for account A, the account switching control in the upper left corner displays the avatars of all currently logged-in accounts (account A, account B, and account C). Account B, having access to this function, is displayed in the same normal color and brightness as account A, while account C, lacking access, is displayed as a gray, semi-transparent icon. Users can quickly identify available accounts supporting this function through visual differences.

[0078] Optionally, the second category of non-controlled accounts refers to those non-controlled accounts that do not have permission to access the target function entry point. While identifying the first category of non-controlled accounts, the system will also classify other non-controlled accounts not classified as first category into the second category.

[0079] Optionally, visually differentiating the account identifiers for the first type of non-controlled accounts and the second type of non-controlled accounts in the account switching control means that the system uses different visual representations for the account identifiers of the two types of non-controlled accounts, making the two types of account identifiers visually distinct and perceptible to the user. Common differentiation methods include, but are not limited to, adjusting color brightness and saturation, and may also involve whether the identifier itself has visual embellishments indicating an interactive state, such as highlighted borders, corner marks, or micro-animations. This disclosure does not limit this aspect.

[0080] Optionally, the visual differentiation display status in the account switching control can be dynamically updated as the game data of each non-controlled account changes. When a second-category non-controlled account completes a specific game progress update in the background, such as raising its character level to the unlock level of the target function entry, the target function entry's identifier information is added to the list of available function entries for that non-controlled account. At this time, the system can reclassify the non-controlled account based on the latest available function entry information in real time or periodically, reclassifying the non-controlled account from the second-category non-controlled account back to the first-category non-controlled account, and updating the visual presentation of the account identifier in the account switching control from a differentiated state (such as semi-transparent, grayscale) to a normal state consistent with the first-category non-controlled account (such as completely opaque, full color). Conversely, if a first-category non-controlled account loses its access to the target function entry due to changes in game data (such as the function expiring and being closed), the system can also reclassify it back to the second-category non-controlled account and update the visual presentation of its account identifier. In one specific implementation, while the account switching control remains displayed, the system polls the latest available function entry information for each non-control account at fixed time intervals, and automatically refreshes the visual differentiation display status in the control when a change is detected.

[0081] In an optional implementation, after displaying the second functional interface corresponding to the target functional entry in the first graphical user interface, the method further includes: obtaining operation instructions for the second functional interface; and updating the game data corresponding to the target account according to the operation instructions. This allows users to directly operate the functional interface of a non-controlling account without switching the current controlling account, and to update the game data of the corresponding account in real time. This improves operational efficiency in a multi-account environment, reduces the operational burden caused by repetitive operations and account switching, and also reduces the overhead of interface reloading and data reloading caused by account switching.

[0082] For example, in a game application that supports simultaneous login of multiple accounts, a user logs in to account A, account B, and account C simultaneously on the same terminal device, with account A being the currently controlling account. The user triggers the check-in entry in the first graphical user interface corresponding to account A, and the system displays a first functional interface generated based on the game data of account A. The user selects account B as the target account via an account selection command, and the system displays a second functional interface generated based on the game data of account B in the first graphical user interface. This interface displays account B's check-in records and the available check-in status for the day. The user clicks the check-in button in the second functional interface, and the system receives the operation command for that interface, updates the game data corresponding to account B according to the command, updates account B's check-in status to "checked in," writes the check-in rewards into account B's item data, and refreshes the updated check-in status in the second functional interface. Throughout this process, the user remains in the first graphical user interface corresponding to account A and does not perform an account switching operation.

[0083] Optionally, the operation instructions for the second functional interface refer to the instruction information generated by various interactive operations performed by the user in the second functional interface. Since the second functional interface is generated based on the game data of the target account, the operations performed by the user in the second functional interface are essentially operations on the functions of the target account.

[0084] Optionally, updating the game data corresponding to the target account according to the operation instruction means that after receiving the operation instruction, the system applies the operation content contained in the operation instruction to the game data of the target account stored on the server or local side, causing corresponding changes to the game data of the target account. After updating the game data corresponding to the target account according to the operation instruction, the display content in the second function interface can be refreshed synchronously to reflect the data update result. From the data update path, in one implementation, the system sends the operation instruction along with the target account's identification information to the game server. The server verifies the legality of the operation (e.g., verifies whether the target account meets the sign-in conditions), executes the corresponding data modification operation, and returns the updated game data to the terminal device. After receiving the updated data, the terminal device refreshes the display in the second function interface. In another implementation, the system temporarily updates the game data locally and reflects the update result in real time in the second function interface, while asynchronously uploading the operation instruction to the server for persistent storage and verification. The specific data update content depends on the type of operation instruction. For example, the data update corresponding to the sign-in operation instruction includes setting the target account's sign-in mark for the day to complete and adding sign-in reward items and quantities to the target account's item list.

[0085] Optionally, during the execution of operation commands and updating of game data on the target account within the first graphical user interface of the currently controlled account, the login status and game data of the currently controlled account remain unaffected. When processing operation commands for the second functional interface, the system strictly limits the scope of the operation commands to the game data of the target account; the game data of the currently controlled account remains unchanged. In the underlying data processing logic, the system uses the target account identifier information carried in the operation command to locate the data record that needs to be updated, ensuring that the data update operation points to the correct account data storage space.

[0086] In an optional implementation, the method further includes: responding to an account selection command and reselecting a target account from the non-controlling accounts; switching the second functional interface to display a fourth functional interface corresponding to the target functional entry, the fourth functional interface being generated based on the game data of the reselected target account. In this way, users can conveniently switch between multiple non-controlling accounts and view their respective target functional interface data without leaving the current graphical user interface or switching the controlling account, achieving rapid comparison and continuous operation of cross-account data.

[0087] For example, in a game application that supports simultaneous login of multiple accounts, a user logs in to accounts A, B, C, and D on the same terminal device, with account A being the currently controlling account. The user triggers the check-in entry in the first graphical user interface corresponding to account A, and the system displays a first functional interface generated based on account A's game data. The user then selects account B as the target account via the account selection command, and the system displays a second functional interface generated based on account B's game data in the first graphical user interface. This interface displays account B's check-in calendar and daily check-in status. After viewing account B's check-in interface, the user again selects account C from the non-controlling accounts as the target account via the account selection command. The system then switches the currently displayed second functional interface to a fourth functional interface generated based on account C's game data, displaying account C's check-in calendar and daily check-in status. The user can then continue to select account D via the account selection command, and the system again switches the interface to a functional interface generated based on account D's game data. Throughout this process, the user remains within the functional interface level corresponding to the check-in entry, without needing to return to the first graphical user interface to re-trigger the check-in entry.

[0088] Optionally, the fourth functional interface is a functional interface that corresponds to the same target functional entry point as the second functional interface but is generated based on game data from a different non-controlled account. The fourth functional interface and the second functional interface can maintain the same interface structure and layout, as both correspond to the same target functional entry point. For example, both are check-in functional interfaces, possessing the same interface template, control layout, and interaction logic. The difference lies in the game data content filled and displayed in the interface. The second functional interface displays the game data of the previously selected target account, while the fourth functional interface displays the game data of the reselected target account. For example, the second functional interface displays the check-in calendar for account B, showing that account B has checked in for five consecutive days, while the fourth functional interface displays the check-in calendar for account C, showing that account C has checked in for two consecutive days. From a data generation perspective, after determining the reselected target account, the system extracts data fields related to the target functional entry point from the account's game data, renders these data fields according to the interface template corresponding to the target functional entry point, and generates the display content of the fourth functional interface.

[0089] Optionally, during the process of reselecting the target account and switching the display of the fourth function interface, the currently controlling account remains unchanged. When the system performs the reselection and interface switching operations, it does not change the identity of the currently controlling account; the first graphical user interface still belongs to the current controlling account. Only the game data displayed in the function interface's display area switches from one non-controlling account to another. Furthermore, during the display switching process, only the data fields related to the target account and the target function entry point need to be retrieved, significantly reducing data transmission and processing pressure compared to the account switching method.

[0090] In an optional implementation, responding to an account selection instruction and selecting a target account from non-controlled accounts includes: responding to an account selection instruction and selecting multiple target accounts from non-controlled accounts; displaying a second functional interface corresponding to the target functional entry in a first graphical user interface, the second functional interface being generated based on the game data of the target account, including: simultaneously displaying multiple second functional interfaces in the first graphical user interface, wherein each second functional interface is generated based on the game data of its corresponding target account. Thus, by supporting users to select multiple target accounts from non-controlled accounts at once and simultaneously displaying multiple second functional interfaces in the first graphical user interface, with each second functional interface generated based on its corresponding target account's game data, users can simultaneously view and process game data and operation tasks of multiple non-controlled accounts under the same functional entry in the same interface view. This transforms the original serial operation of switching accounts one by one into a parallel presentation, reducing the time overhead of repeatedly switching between multiple accounts and waiting for the interface to load. Simultaneously, it allows users to intuitively compare the game data status of different accounts in the same view, improving the batch processing efficiency of similar interface tasks in multi-account scenarios.

[0091] For example, in a game application that supports simultaneous login of multiple accounts, a user logs in to accounts A, B, C, and D on the same terminal device, with account A as the currently controlling account. The user triggers the check-in entry in the first graphical user interface corresponding to account A, and the system displays a first functional interface generated based on the game data of account A. The user then selects accounts B, C, and D as multiple target accounts using the account selection command. The system simultaneously displays three second functional interfaces in the first graphical user interface. The first second functional interface generates and displays the check-in calendar and daily check-in status of account B based on the game data of account B; the second second functional interface generates and displays the check-in calendar and daily check-in status of account C based on the game data of account C; and the third second functional interface generates and displays the check-in calendar and daily check-in status of account D based on the game data of account D. These three second functional interfaces are presented simultaneously in the first graphical user interface in a side-by-side or tabbed format, allowing the user to perform check-in operations for each account sequentially within the same view.

[0092] Optionally, selecting multiple target accounts from non-controlled accounts means that after receiving an account selection instruction, the system simultaneously identifies multiple non-controlled accounts as target accounts, rather than selecting only one. In specific implementations, the account selection instruction can specify multiple target accounts in several ways. In one way, the user completes the multi-selection operation by clicking the account icons of multiple non-controlled accounts one by one in the account switching control. Each clicked account icon displays a visual feedback of being selected (e.g., a highlighted border or a checkmark). In another way, the account switching control provides a "Select All" button, allowing the user to select multiple non-controlled accounts as target accounts in batches. In yet another way, after selecting multiple target accounts, the user clicks a "Confirm" button to submit the multi-selection results.

[0093] Optionally, when multiple second functional interfaces are displayed simultaneously in the first graphical user interface, the arrangement and layout of the multiple second functional interfaces can be adapted according to the number of target accounts and the available display area of ​​the first graphical user interface. For example, they can be displayed simultaneously in a horizontal or vertical arrangement in the first graphical user interface, or arranged in a grid, such as a two-row, two-column layout, with each functional interface occupying a quarter of the display area. On terminals with limited display space, such as mobile devices, multiple second functional interfaces can also exist simultaneously in the interface as stacked tabs, with each tab corresponding to a second functional interface of a target account. Users can switch between viewing the functional interfaces of different accounts by clicking different tabs. In another layout method, multiple second functional interfaces are arranged in the form of a horizontally scrollable list, and users can browse the functional interfaces of different target accounts by swiping left and right.

[0094] Optionally, in scenarios where multiple secondary functional interfaces are displayed simultaneously, each secondary functional interface can independently receive user operation commands. Users can perform operations (e.g., clicking a check-in button) on a specific secondary functional interface. This operation command will affect the game data of the target account corresponding to that secondary functional interface, without affecting the target accounts corresponding to other secondary functional interfaces. In one implementation, the system can also provide a batch operation function. Users can click a batch check-in button or a batch claim button to perform the same operation on all target accounts displayed simultaneously on all secondary functional interfaces. The system sends the corresponding operation commands to each target account sequentially or in parallel and updates their respective game data. After the batch operation is completed, each secondary functional interface refreshes synchronously to reflect the data update results of its respective target account. Each secondary functional interface can display the account identification information of the corresponding target account, such as displaying the target account's character avatar and nickname at the top or corner of the interface, helping users distinguish which target account each interface corresponds to among multiple parallel functional interfaces.

[0095] In an optional implementation, obtaining available function entry information for multiple login accounts includes: responding to a multi-account compatibility mode activation command and obtaining available function entry information for multiple login accounts. In this way, by actively triggering the compatibility mode activation command, users can flexibly choose whether to enable multi-account compatibility mode according to their needs to trigger subsequent multi-account function entry aggregation and cross-account interface operation processes.

[0096] For example, see Figure 8 In the game settings interface, users can select whether to enable multi-account compatibility mode via a multi-account compatibility mode enable button. After enabling it, the user closes the settings interface and returns to the main interface (first graphical user interface) of the currently controlled account A. The system responds to this multi-account compatibility mode enable command by requesting and retrieving the available function entry information for each of the three logged-in accounts: account A, account B, and account C. Once retrieved, the system displays the union of the available function entry points for the three accounts in the first graphical user interface corresponding to account A.

[0097] Optionally, upon responding to the multi-account compatibility mode activation command, the system can retrieve available function entry information for multiple logged-in accounts. There are several implementations regarding the timing and method of retrieval. In terms of timing, the system can execute the retrieval operation immediately upon receiving the activation command, or it can execute it during the next interface refresh cycle after the activation command triggers a mode switch. Regarding the method, in one implementation, the system sends a batch query request containing all logged-in account identifiers to the game server. Upon receiving the request, the server returns a list of available function entry points for each logged-in account at once. The system then parses the returned data and stores it in a local cache of available function entry information. In another implementation, the system sends independent available function entry query requests for each logged-in account. These requests can be executed in parallel to shorten the overall retrieval time. After all requests have returned responses, the system aggregates and integrates the available function entry data for each account. In yet another implementation, if the basic game data for each logged-in account already exists in the local cache, the system can directly calculate the list of available function entry points for each account locally based on the locally cached game data and the function entry point opening rules, without sending additional query requests to the server. For example, the system determines locally whether each function entry is available to each account based on the character level and completed task list recorded in the local cache for each account, combined with the level requirements and prerequisite task requirements of each function entry.

[0098] Optionally, after enabling multi-account compatibility mode and acquiring available function entry information, the system can dynamically update the available function entry information during operation. In one approach, the system re-acquires the available function entry information for all logged-in accounts at fixed time intervals (e.g., every five minutes) and synchronizes the updated information to the function entry set display in the first graphical user interface. In another approach, the system triggers the update of available function entry information after detecting a specific event (e.g., a logged-in account completing a status upgrade in the background or receiving a data change notification pushed by the server).

[0099] In an optional implementation, the available function entry point is the interface operation task entry point.

[0100] Optionally, a UI operation task entry point refers to a functional entry point associated with a specific UI operation task. When a user triggers this entry point, the system opens the corresponding functional interface, where the user completes the task by performing interactive operations. From the perspective of task type, UI operation tasks can cover various categories, such as daily check-in tasks, email attachment retrieval tasks, activity reward retrieval tasks, daily welfare retrieval tasks, and limited-time gift pack retrieval tasks. These tasks share the common characteristic that they all require the user to actively open the corresponding functional interface and perform at least one interactive operation (such as clicking a button, swiping to confirm, etc.) to complete. From the perspective of the entry point's presentation, UI operation task entry points in the first graphical user interface are typically presented as icon buttons, text links, or combined text and image controls. Users can trigger the entry point and enter the corresponding functional interface by clicking or touching these controls. For example, the check-in entry point is displayed as a calendar icon in a specific area of ​​the interface, the email retrieval entry point is displayed as an envelope icon, and the daily reward retrieval entry point is displayed as a gift box icon.

[0101] Interface operation tasks in multi-account scenarios are characterized by high-frequency repetition. Furthermore, task execution and functional interface rendering rely on relatively little user attribute data, requiring minimal modeling and scene rendering calculations, and do not involve complex interaction logic. If these tasks must be executed by switching accounts each time, it would incur significant unnecessary resource consumption and interrupt the user's execution of other tasks for the currently controlled account. Therefore, this embodiment addresses this type of task by acquiring functional entry information for available interface operation tasks from multiple logged-in accounts, including the current controlling account and non-controlling accounts. Based on this, the set of available functional entry points is uniformly displayed in the first graphical user interface corresponding to the current controlling account. This allows users to centrally access the functional entry points of multiple accounts within a single interface, eliminating the need to switch accounts individually to view available functions, thereby reducing the overhead of repetitive rendering and data loading caused by repeated interface switching. Based on this, when a user triggers the target function entry, the first function interface generated based on the game data of the current controlling account is first displayed in the first graphical user interface. Then, in response to the account selection command, the target account is selected from the non-controlling account, and the second function interface generated based on the game data of the target account is directly displayed in the first graphical user interface. The entire process is always completed in the first graphical user interface of the current controlling account. There is no need to switch the current controlling account to the target account and reload the complete user interface. This avoids the overall reconstruction of the interface and the reallocation of resources caused by account switching, effectively reducing the data processing pressure and graphics rendering resource consumption of the terminal device. At the same time, it significantly reduces the repetitive operation steps when users perform the same operation between multiple accounts, improves the operation efficiency in multi-account scenarios, and reduces the risk of operation confusion and misoperation caused by frequent account switching.

[0102] Corresponding to the above method embodiments, this invention provides an information processing device, see [link to previous document]. Figure 9 The device includes: an acquisition module for acquiring available function entry information for multiple login accounts, including a currently controlled account and non-controlled accounts; a function entry display module for displaying a set of available function entry points in a first graphical user interface corresponding to the currently controlled account based on the available function entry information; a function interface display module for responding to a trigger operation on a target function entry point in the function entry entry set and displaying a first function interface corresponding to the target function entry point in the first graphical user interface, the first function interface being generated based on the game data of the currently controlled account; an account selection module for responding to an account selection command and selecting a target account from the non-controlled accounts; and the function interface display module is also used to display a second function interface corresponding to the target function entry point in the first graphical user interface, the second function interface being generated based on the game data of the target account.

[0103] In an optional implementation, the set of available function entry points includes the union of the available function entry points for all logged-in accounts.

[0104] In an optional implementation, the function entry display module is specifically used to: determine, based on the available function entry information, a first type of function entry that is available to the current control account and a second type of function entry that is unavailable, wherein the second type of function entry is available to at least one non-control account; and to visually differentiate the first type of function entry and the second type of function entry in the set of available function entries.

[0105] In an optional implementation, the function interface display module is specifically used to: respond to a trigger operation for a target function entry in the first type of function entry, and display the first function interface corresponding to the target function entry in the first graphical user interface.

[0106] In an optional implementation, the account selection module includes: a control display unit for displaying an account switching control in a first functional interface, the account switching control being used to display non-controlled accounts; and a selection unit for responding to a selection operation on the account switching control and selecting a target account from the non-controlled accounts.

[0107] In an optional embodiment, the device further includes: a switching prompt module, configured to respond to a trigger operation on a target function entry in the second type of function entry and display account switching prompt information, the prompt information being used to indicate the first type of non-controlled account for the available target function entry; an account switching module, configured to respond to an account switching confirmation command and switch the target non-controlled account selected from the first type of non-controlled accounts to the current controlled account and switch the current controlled account to a non-controlled account; an interface switching module, configured to switch the first graphical user interface to a second graphical user interface corresponding to the target non-controlled account; and a function interface display module, further configured to display a third function interface corresponding to the target function entry in the second graphical user interface, the third function interface being generated based on the game data of the target non-controlled account.

[0108] In an optional implementation, the control display unit includes: an account determination subunit, used to determine a first type of non-controlled account for the available target function entry based on the available function entry information; and an account identifier display subunit, used to display the account identifier corresponding to the first type of non-controlled account in the account switching control.

[0109] In an optional implementation, the selection unit is specifically configured to: respond to a selection operation on an account identifier in the account switching control, and determine the non-controlled account corresponding to the selected account identifier as the target account.

[0110] In an optional implementation, the account determination subunit is specifically used to determine the first type of non-controlled account for available target function entry and the second type of non-controlled account for unavailable target function entry based on the available function entry information; the account identifier display subunit is specifically used to visually differentiate the account identifiers corresponding to the first type of non-controlled account and the second type of non-controlled account in the account switching control.

[0111] In an optional implementation, the device further includes: an instruction acquisition module, which is also used to acquire operation instructions for the second functional interface; and a data update module, which is used to update the game data corresponding to the target account according to the operation instructions.

[0112] In an optional implementation, the account selection module is further configured to respond to an account selection instruction and reselect a target account from non-controlled accounts; the function interface display module is further configured to switch the second function interface to a fourth function interface corresponding to the target function entry, the fourth function interface being generated based on the game data of the reselected target account.

[0113] In an optional implementation, the account selection module is further configured to respond to an account selection instruction and select multiple target accounts from non-controlled accounts; the function interface display module is further configured to simultaneously display multiple second function interfaces in the first graphical user interface, wherein each second function interface is generated based on the game data of the corresponding target account.

[0114] In an optional implementation, the acquisition module is specifically used to: respond to the multi-account compatibility mode activation command and acquire the available function entry information for multiple login accounts.

[0115] In an optional implementation, the available function entry point is the interface operation task entry point.

[0116] The information processing apparatus provided in this disclosure has the same implementation principle and technical effects as the aforementioned method embodiments. For the sake of brevity, any parts not mentioned in the apparatus embodiments can be referred to the corresponding content in the aforementioned method embodiments.

[0117] It should be noted that although several units / modules or sub-units / modules of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of the present invention, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0118] This invention also provides an electronic device, such as... Figure 10As shown, the electronic device includes a processor and a memory. The memory stores computer-executable instructions that can be executed by the processor. The processor executes the computer-executable instructions to implement any information processing method of the embodiments of this disclosure. For specific implementation methods and the resulting technical effects, please refer to the method embodiments, which will not be repeated here.

[0119] Figure 10 This is a schematic diagram of the structure of an electronic device. The electronic device 1100 includes a processor 1101 with one or more processing cores, a memory 1102 with one or more computer-readable storage media, and a computer program stored in the memory 1102 and executable on the processor. The processor 1101 and the memory 1102 are electrically connected. Those skilled in the art will understand that the electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0120] The processor 1101 is the control center of the electronic device 1100. It connects various parts of the electronic device 1100 through various interfaces and lines. By running or loading software programs and / or modules stored in the memory 1102, and calling data stored in the memory 1102, it executes various functions of the electronic device 1100 and processes data, thereby performing overall monitoring of the electronic device 1100.

[0121] Optionally, the electronic device 1100 further includes: a touch display screen 1103, a radio frequency circuit 1104, an audio circuit 1105, an input unit 1106, and a power supply 1107. The processor 1101 is electrically connected to the touch display screen 1103, the radio frequency circuit 1104, the audio circuit 1105, the input unit 1106, and the power supply 1107. Those skilled in the art will understand that... Figure 10 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0122] This invention also provides a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute any information processing method of this disclosure embodiment when run by a processor. For specific implementation methods and the resulting technical effects, please refer to the method embodiments, which will not be repeated here.

[0123] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal device, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0124] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0125] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. An information processing method, characterized in that, The method includes: Obtain available function entry information for multiple login accounts, including the currently controlled account and non-controlled accounts; Based on the available function entry information, the set of available function entry points is displayed in the first graphical user interface corresponding to the current control account; In response to a trigger operation targeting a target function entry in the set of function entry points, a first function interface corresponding to the target function entry point is displayed in the first graphical user interface. The first function interface is generated based on the game data of the currently controlled account. In response to the account selection instruction, select the target account from the non-controlled accounts; The second function interface corresponding to the target function entry is displayed in the first graphical user interface. The second function interface is generated based on the game data of the target account.

2. The information processing method according to claim 1, characterized in that, The set of available function entry points includes the union of the available function entry points for all logged-in accounts.

3. The information processing method according to claim 1, characterized in that, The step of displaying the set of available function entry points in the first graphical user interface corresponding to the current control account based on the available function entry information includes: Based on the available function entry information, a first type of function entry that is available to the current control account and a second type of function entry that is unavailable are determined. The second type of function entry is available to at least one of the non-control accounts. In the set of available function entry points, the first type of function entry point and the second type of function entry point are displayed with visual differentiation.

4. The information processing method according to claim 3, characterized in that, The response is a trigger operation on a target function entry in the set of function entry points, and displays a first function interface corresponding to the target function entry point in the first graphical user interface, including: In response to a trigger operation targeting a specific function entry in the first type of function entry, the first function interface corresponding to the target function entry is displayed in the first graphical user interface.

5. The information processing method according to claim 1, characterized in that, The response account selection instruction, which selects a target account from the non-controlled accounts, includes: An account switching control is displayed in the first functional interface, and the account switching control is used to display the non-controlled account; In response to a selection operation on the account switching control, the target account is selected from the non-controlled accounts.

6. The information processing method according to claim 3, characterized in that, The method further includes: In response to a trigger operation targeting a target function entry in the second type of function entry, an account switching prompt message is displayed, which is used to indicate that a first type of non-controlled account is available for the target function entry; In response to the account switching confirmation command, the target non-control account selected from the first type of non-control account is switched to the current control account, and the current control account is switched to a non-control account; Switch the first graphical user interface to display the second graphical user interface corresponding to the target non-control account; The third function interface corresponding to the target function entry is displayed in the second graphical user interface. The third function interface is generated based on the game data of the target non-control account.

7. The information processing method according to claim 5, characterized in that, The step of displaying the account switching control in the first functional interface includes: Based on the available function entry information, determine the first type of non-controlled account that can access the target function entry; The account identifier corresponding to the first type of non-controlled account is displayed in the account switching control.

8. The information processing method according to claim 5, characterized in that, The response to the selection operation of the account switching control, selecting the target account from the non-controlled accounts, includes: In response to the selection operation of the account identifier in the account switching control, the non-controlled account corresponding to the selected account identifier is determined as the target account.

9. The information processing method according to claim 5, characterized in that, The step of displaying the account switching control in the first functional interface includes: Based on the available function entry information, determine the first type of non-controlled account that can use the target function entry and the second type of non-controlled account that cannot use the target function entry; The account switching control displays the account identifiers corresponding to the first type of non-controlled accounts and the account identifiers corresponding to the second type of non-controlled accounts in a visually differentiated manner.

10. The information processing method according to claim 1, characterized in that, After displaying the second functional interface corresponding to the target functional entry in the first graphical user interface, the method further includes: Obtain operation instructions for the second functional interface; Update the game data corresponding to the target account according to the operation instructions.

11. The information processing method according to claim 1, characterized in that, The method further includes: In response to the account selection instruction, a new target account is selected from the non-controlled accounts; The second function interface is switched to the fourth function interface corresponding to the target function entry, and the fourth function interface is generated based on the game data of the reselected target account.

12. The information processing method according to claim 1, characterized in that, The response account selection instruction, which selects a target account from the non-controlled accounts, includes: In response to the account selection instruction, select multiple target accounts from the non-controlled accounts; The step of displaying a second functional interface corresponding to the target functional entry point in the first graphical user interface, wherein the second functional interface is generated based on the game data of the target account, includes: Multiple second functional interfaces are simultaneously displayed in the first graphical user interface, each of which is generated based on the game data of the corresponding target account.

13. The information processing method according to claim 1, characterized in that, The available entry points for obtaining multiple login accounts include: In response to the command to enable multi-account compatibility mode, obtain the available function entry information for multiple login accounts.

14. The information processing method according to any one of claims 1-13, characterized in that, The available function entry points are the interface operation task entry points.

15. An information processing device, characterized in that, The device includes: The acquisition module is used to acquire available function entry information for multiple login accounts, including the currently controlled account and non-controlled accounts; The function entry display module is used to display the set of available function entries in the first graphical user interface corresponding to the current control account according to the available function entry information; The function interface display module is used to respond to a trigger operation on a target function entry in the set of function entry points, and to display a first function interface corresponding to the target function entry point in the first graphical user interface. The first function interface is generated based on the game data of the current control account. The account selection module is used to respond to account selection instructions and select a target account from the non-controlled accounts; The function interface display module is also used to display a second function interface corresponding to the target function entry in the first graphical user interface, the second function interface being generated based on the game data of the target account.

16. An electronic device, characterized in that, include: Memory stores computer-executable instructions that can be executed by a processor; A processor for executing the computer-executable instructions to implement the method as claimed in any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, The device contains a computer program that, when executed by a processor, implements the method as described in any one of claims 1-14.

Images