Account identifier changing method and device, storage medium and electronic equipment

Abstract

The invention discloses an account identifier changing method and device, a storage medium and electronic equipment. The method comprises the steps that under the condition that both a first account and a second account log in a target application, a first account identifier and a second account identifier are displayed, the ownership of each account identifier in the target application belongs to a corresponding unique account, the account identifiers are different, the ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account. The ownership of the second account identifier belongs to the second account; and in response to a first identification request sent by the first account number to the second account number, displaying a first event, and under the condition that the first event is completed, replacing the account number identification of the first account number with the second account number identification from the first account number identification, and changing the ownership of the second account number identification to be belonging to the first account number. According to the method and the device, the technical problem that the user cannot use the favorite account identifier due to the fact that the account identifiers cannot be repeated is solved.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a method and apparatus for changing account identifiers, a storage medium, and an electronic device. Background Technology

[0002] In recent years, various internet applications have flourished, allowing users to express their personality, values, social attitudes, and identity through account identifiers (nicknames). Since user nicknames serve as unique identifiers for accounts within applications, they are typically set to prevent duplication. That is, different accounts generally cannot use the same nickname. In other words, users choose their own nicknames and can only choose those that are unique to each other. Therefore, if a highly valuable nickname has already been registered by another user, the user will be unable to use their preferred nickname.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a method, apparatus, storage medium, and electronic device for changing account identifiers, so as to at least solve the technical problem that account identifiers cannot be duplicated, causing users to be unable to use their preferred account identifiers.

[0005] According to one aspect of the embodiments of this application, a method for changing an account identifier is provided, comprising: when both a first account and a second account are logged into a target application, displaying a first account identifier and a second account identifier, wherein the ownership of each account identifier in the target application belongs to a corresponding unique account, and each account identifier is different, the ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account; in response to the first account sending a first identifier request to the second account, displaying a first event, wherein the first identifier request is used to indicate that the first account requests the second account to acquire ownership of the second account identifier; and when the first event has been completed, replacing the first account identifier of the first account with the second account identifier, wherein the ownership of the second account identifier is changed to belong to the first account.

[0006] According to another aspect of the embodiments of this application, an account identifier changing device is also provided, comprising: a first display module, configured to display a first account identifier and a second account identifier when both a first account and a second account are logged into a target application, wherein the ownership of each account identifier in the target application belongs to the corresponding unique account, and each account identifier is different, the ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account; a second display module, configured to display a first event in response to the first account sending a first identifier request to the second account, wherein the first identifier request indicates that the first account requests the second account to acquire ownership of the second account identifier; and a replacement module, configured to replace the account identifier of the first account with the second account identifier when the first event has been completed, wherein the ownership of the second account identifier is changed to belong to the first account.

[0007] Optionally, the device is configured to display a first event in response to the first account sending a first identifier request to the second account in the following manner: in response to the first account sending the first identifier request to the second account, a request prompt message is displayed on the application interface of the second account, wherein the request prompt message is used to inform the second account that the first account is requesting to acquire ownership of the second account identifier; in response to the second account performing a first interactive operation on the request prompt message, the first event is displayed on the application interface of the first account, wherein the first interactive operation is used to indicate that the second account allows the first account to initiate the process of acquiring the second account identifier.

[0008] Optionally, the device is configured to respond to the second account's response to the request prompt message by performing a first interactive operation, and display the first event on the application interface of the first account in at least one of the following ways: responding to the second account's response to the request prompt message by performing the first interactive operation, displaying a first resource transfer event on the application interface of the first account, wherein the first resource transfer event indicates that the first account needs to transfer virtual resources to the second account; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying a second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to help the second account transfer virtual resources to a third account; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying a relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to change social relationships.

[0009] Optionally, the device is configured to respond to the second account's response to the request prompt message by performing a first interactive operation, and display a second resource transfer event on the application interface of the first account in at least one of the following ways: responding to the second account's response to the request prompt message by performing the first interactive operation, displaying the second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to transfer a first number of virtual resources to the third account to upgrade the virtual level of the target virtual item owned by the second account to a preset level; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying the second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to transfer a second number of virtual resources to the third account to extend the duration of the target permission owned by the second account by a first preset duration; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying the second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to transfer a third number of virtual resources to the third account to transfer ownership of the preset virtual item to the second account.

[0010] Optionally, the device is configured to respond to the second account's response to the request prompt message by performing a first interactive operation, displaying a relationship establishment event on the application interface of the first account in at least one of the following ways: responding to the second account's response to the request prompt message by performing a first interactive operation, displaying the relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to add the second account as a friend account; responding to the second account's response to the request prompt message by performing a first interactive operation, displaying the relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to join a first preset group, the first preset group indicating a group that the first account has not joined but the second account has already joined; responding to the second account's response to the request prompt message by performing a first interactive operation, displaying the relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to leave a second preset group and join the first preset group, the second preset group indicating a group that the first account has already joined.

[0011] Optionally, the device is configured to respond to the second account's request prompt message by performing a first interactive operation and displaying the first event on the application interface of the first account in the following manner: responding to the second account's request prompt message by performing the first interactive operation, displaying an event set component on the application interface of the first account, wherein the event set component corresponds to a set of events, the set of events including the first event; responding to the first account's event set component by performing a second interactive operation, displaying the first event on the application interface of the first account, wherein the second interactive operation is used to select the first event from the set of events.

[0012] Optionally, the device is configured to replace the account identifier of the first account with the second account identifier in the event that the first event has been completed by at least one of the following methods: when the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event has been completed, replace the account identifier of the first account with the second account identifier, and transfer the virtual resources from the first account to the second account according to the number of virtual resources transferred as indicated by the first event; when the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event has not been completed, transfer the virtual resources from the first account to the system account according to the number of virtual resources transferred as indicated by the first event; when the first event has been completed for a second preset time, replace the account identifier of the first account with the second account identifier, and transfer the virtual resources from the system account to the second account according to the number of virtual resources transferred as indicated by the first event; when the first event has not been completed for the second preset time, send a change failure message to the first account, and cancel the ownership of the virtual resources transferred from the first account to the system account by the first account.

[0013] Optionally, the device is further configured to: when both the first account and the second account are logged into the target application, in response to a third interactive operation performed by the second account, display the second account identifier in a preset area, wherein the preset area represents a display area for an account identifier that allows changes in ownership; and in response to the first account performing a fourth interactive operation on the second account identifier in the preset area, send the first identifier request to the second account and display the first event.

[0014] Optionally, the device is further configured to perform at least one of the following steps: when the first event has been completed, replacing the account identifier of the second account with a third account identifier pre-set by the second account; when the first event has been completed, replacing the account identifier of the second account with a random account identifier automatically generated by the target application; when the first event has been completed, replacing the account identifier of the second account with the first account identifier.

[0015] Optionally, the device is further configured to: display the first account identifier and the live stream identifier when both the first account and the streamer account are logged into the virtual live stream room, wherein the target application includes the virtual live stream room, and the live stream identifier represents the identifier set by the streamer account for the virtual live stream room; display a second event in response to the first account sending a second identifier request to the streamer account, wherein the second identifier request is used to indicate that the first account requests the streamer account to obtain the right to use the live stream identifier; and replace the first account identifier with the live stream account identifier when the second event has been completed, wherein the ownership of the live stream account identifier belongs to the first account, and the live stream account identifier includes the first account identifier and the live stream identifier.

[0016] Optionally, the device is configured to respond to the first account sending a second identifier request to the broadcaster account and display a second event in the following manner: responding to the identifier promotion request sent by the broadcaster account, publishing an event notification message in the virtual live broadcast room; responding to the first account performing a fifth interactive operation on the event notification message, sending the second identifier request to the broadcaster account and displaying the second event on the application interface of the first account.

[0017] Optionally, the device is configured to replace the account identifier of the first account with the live room account identifier when the second event has been completed in the following manner: when the second event has been completed, synthesize the live room account identifier based on the first account identifier and the live room identifier; replace the account identifier of the first account with the live room account identifier, and assign corresponding permissions to the first account, wherein an account with the live room identifier in the virtual live room is allowed to participate in the promotional activities published by the virtual live room, and when an account with the live room account identifier leaves the virtual live room, the account identifier used is the live room account identifier.

[0018] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the above-mentioned account identifier change method when running.

[0019] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the account identifier change method as described above.

[0020] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-described method for changing the account identifier through the computer program.

[0021] In this embodiment, when both the first account and the second account are logged into the target application, a first account identifier and a second account identifier are displayed. Ownership of each account identifier in the target application belongs to its corresponding unique account, and each account identifier is distinct. Ownership of the first account identifier belongs to the first account, and ownership of the second account identifier belongs to the second account. In response to the first account sending a first identifier request to the second account, a first event is displayed. The first identifier request indicates that the first account is requesting ownership of the second account identifier from the second account. Once the first event is completed, the first account identifier is replaced with the second account identifier, and ownership of the second account identifier changes to belong to the first account. This allows, for example, in a social application, when both the first and second accounts are logged into the target application simultaneously, the application interface will display two different account identifiers, representing the first account and the second account respectively. These identifiers are unique, and the ownership of each identifier strictly corresponds to its registered account. When the first account requests the right to use the identifier of the second account, the target application triggers a request event. This signifies that the first account has formally requested the second account to acquire ownership of its identifier. Once the identifier request event is processed and the second account agrees to transfer ownership of the identifier to the first account, the target application updates the first account's identifier to the second account's identifier and formally transfers ownership of the second account's identifier to the first account. This achieves the goal of ensuring that the transfer of ownership of the account identifier is both secure and efficient, thereby providing users with a smooth interactive experience. It enables account identifiers to be changed between different accounts, allowing users to use their desired account identifiers. This solves the technical problem that account identifiers cannot be duplicated, preventing users from using their preferred account identifiers.

[0022] Furthermore, in the virtual live streaming scenario, when both the viewer (first account) and the streamer log in simultaneously, the application interface displays two unique identifiers: the viewer's personal account identifier and the live streaming room's exclusive identifier. The live streaming room identifier is specially set by the streamer to represent the live streaming room's brand or theme. When viewers wish to use the live streaming room identifier, they can send a request to the streamer. This request (second identifier request) will trigger an event (second event), displayed on the interface. Once the viewer completes this event, their account identifier will be replaced with the live streaming room account identifier. This allows viewers, regardless of whether they are actually in the virtual live streaming room, to use the live streaming room account identifier to help the streamer with promotional activities and brand marketing, providing users with a more personalized and interactive experience in the virtual live streaming room. Attached Figure Description

[0023] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0024] Figure 1 This is a schematic diagram illustrating the application environment of an optional method for changing account identifiers according to an embodiment of this application;

[0025] Figure 2 This is a flowchart illustrating an optional method for changing an account identifier according to an embodiment of this application;

[0026] Figure 3 This is a schematic diagram of an optional method for changing an account identifier according to an embodiment of this application;

[0027] Figure 4 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0028] Figure 5 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0029] Figure 6 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0030] Figure 7 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0031] Figure 8 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0032] Figure 9This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0033] Figure 10 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0034] Figure 11 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0035] Figure 12 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0036] Figure 13 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0037] Figure 14 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0038] Figure 15 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0039] Figure 16 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0040] Figure 17 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application;

[0041] Figure 18 This is a schematic diagram of an optional account identifier changing device according to an embodiment of this application;

[0042] Figure 19 This is a structural diagram of an optional account identifier change product according to an embodiment of this application;

[0043] Figure 20 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

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

[0045] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application 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 application 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.

[0046] First, some nouns or terms that appear in the description of the embodiments of this application shall be interpreted as follows:

[0047] An account identifier is a unique identifier used to identify and distinguish different user accounts. In the digital age, account identifiers are essential on social media, online games, email services, and any other platform that requires user registration. Each account identifier should be unique to ensure that each user can be accurately identified.

[0048] A live streaming room refers to an online live streaming program opened by an individual or organization in the internet age. It is not only a place for broadcasters to broadcast programs to viewers, but also a platform for social and commercial activities. Broadcasters can simultaneously stream their activities via computer or mobile phone, while viewers can watch through websites or apps.

[0049] Bullet comments are text messages, emojis, and gifts sent by users after watching the streamer's exciting content. These messages can be seen by other users in the live stream. There are different types of bullet comments, including text bullet comments, emoji bullet comments, and special effects bullet comments.

[0050] The present application will be described below with reference to embodiments:

[0051] According to one aspect of the embodiments of this application, a method for changing an account identifier is provided. Optionally, in this embodiment, the above-mentioned method for changing an account identifier can be applied to, for example... Figure 1 The hardware environment shown consists of server 101 and terminal device 103. For example... Figure 1As shown, server 101 is connected to terminal 103 via a network and can be used to provide services to terminal devices or applications installed on terminal devices. The applications can be video applications, instant messaging applications, browser applications, educational applications, game applications, etc. Database 105 can be set up on the server or independently of the server to provide data storage services for server 101, such as a game data storage server. The network mentioned above can include, but is not limited to, wired networks and wireless networks. The wired network includes local area networks, metropolitan area networks, and wide area networks. The wireless network includes Bluetooth, WIFI, and other networks that enable wireless communication. Terminal device 103 can be a terminal configured with an application, and can include, but is not limited to, at least one of the following: mobile phones (such as Android phones, iOS phones, etc.), laptops, tablets, handheld computers, MID (Mobile Internet Devices), PADs, desktop computers, smart TVs, smart voice interaction devices, smart home appliances, vehicle terminals, aircraft, virtual reality (VR) terminals, augmented reality (AR) terminals, mixed reality (MR) terminals, and other computer devices. The server mentioned above can be a single server, a server cluster composed of multiple servers, or a cloud server.

[0052] Combination Figure 1 As shown, the above-mentioned method for changing the account identifier can be executed by an electronic device, which can be a terminal device or a server. The above-mentioned method for changing the account identifier can be implemented by the terminal device or the server respectively, or by the terminal device and the server together.

[0053] The above is merely an example, and this embodiment does not impose any specific limitations.

[0054] Alternatively, as an alternative implementation method, such as Figure 2 As shown, the methods for changing the account identifier mentioned above include:

[0055] S202, when both the first account and the second account are logged into the target application, the first account identifier and the second account identifier are displayed. The ownership of each account identifier in the target application belongs to the corresponding unique account, and each account identifier is different. The ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account.

[0056] Optionally, in this embodiment, the first account and the second account can be understood as user accounts registered and logged in to the target application. The second account is different from the first account, representing different users. The target application can include, but is not limited to, the specific application or game that the user logs in and uses; in this case, it is a platform that provides account services.

[0057] Optionally, in this embodiment, the aforementioned account identifier is a symbol or name used to identify and distinguish different accounts, and is typically composed of numbers, letters, or combinations thereof. For example, in a certain game application, user A's account identifier is "Little Grass," while user B's account identifier might be "Washing Machine."

[0058] It should be noted that the ownership of the aforementioned account identifiers refers to the binding relationship between the account identifier and a specific account, indicating that the identifier belongs exclusively to that account and cannot be used by other accounts. For example, the ownership of "Little Grass" belongs to user A's account, while the ownership of "Washing Machine" belongs to user B's account. The uniqueness of the account identifier means that each account identifier is unique and not duplicated, ensuring that each user's identity can be accurately identified. For example, in the aforementioned game application, no third account will have the same identifier as "Little Grass" or "Washing Machine".

[0059] In gaming applications, these terms collectively form the foundation for user identification and account management, ensuring order in the gaming environment and personalization of the user experience.

[0060] Optionally, in this embodiment, the aforementioned first account is the user's master account, and the account identifier is a personalized account identifier for the first account. The account identifier is unique; that is, if the account identifier is already occupied by another account, it cannot be set for the first account simultaneously, and it cannot be obtained through any purchase method. Illustratively, the account identifier can be the object name (or object nickname) corresponding to the first account, object identity identifier, object title, object honor, etc., and this embodiment does not limit the scope of the account identifier. Optionally, the account identifier can also be the user's username (user nickname) or user identity identifier in the game.

[0061] Optionally, in this embodiment, the account identifier is used as an example to illustrate the concept. For users participating in the game, a user nickname is generally used instead of their real name. The user nickname (or object nickname) is an important identity credential for users participating in the game. For game platforms, in order to strengthen the management of users participating in the game, corresponding user nickname management mechanisms are in place. For example, the length of user nicknames is limited (generally 6-8 characters); users can set a user nickname once when creating a game character; and different users cannot have the same user nickname. Therefore, user nicknames (game character nicknames) are unique in the game.

[0062] Optionally, in this embodiment, the timing of setting the account identifier can be: when the user initially creates a game character, the account identifier corresponding to the first account can be set; or it can be modified during the game. In one possible implementation, an account identifier modification interface for setting the account identifier corresponding to the first account is provided, whereby the user can set the account identifier for the first account, and the terminal can obtain the account identifier set by the user.

[0063] Specifically, if a user sets an account identifier when initially creating their first account, the corresponding account identifier modification interface can be the game entry interface or the game initial interface; if a user modifies the account identifier during the game, the account identifier modification interface can be the user character attribute interface.

[0064] It should be noted that the account identifier modification interface may display an account identifier input box. The account identifier modification operation can be an input operation in the account identifier input box. For example, users can enter the account identifier in the account identifier input box, and the corresponding terminal receives the input operation and obtains the account identifier entered in the account identifier input box.

[0065] In addition, the account identifier modification interface can also display prompts indicating the requirements for setting the account identifier, such as the number of characters and the character type requirements. Based on the account identifier management mechanism, the account identifier can be set when: when a user initially creates a game character (or the first account), the account identifier corresponding to the first account can be set; or it can be modified during gameplay. In one possible implementation, an account identifier modification interface is provided for setting the account identifier corresponding to the first account. Users can set the account identifier for the first account through the account identifier modification operation on the account identifier modification interface, and the terminal can obtain the account identifier set by the user. If the user sets the account identifier when initially creating the first account, the corresponding account identifier modification interface can be the game entry interface or the game initial interface; if the user modifies the account identifier during gameplay, the attribute setting interface can be the user character attribute interface.

[0066] Furthermore, the account identifier modification interface can display an account identifier input box. The account identifier modification operation can be an input operation into the attribute value input box. For example, users can enter their account identifier into this input box, and the corresponding terminal receives and retrieves the entered account identifier. The account identifier modification interface can also display prompts indicating the requirements for account identifier settings, such as the number of characters in the account identifier and the required character type.

[0067] In one exemplary embodiment, Figure 3 This is a schematic diagram of an optional method for changing an account identifier according to an embodiment of this application, such as... Figure 3 As shown, taking a massively multiplayer online role-playing game (MMORPG) application as an example, the steps include, but are not limited to, the following:

[0068] S302, Account Login: Player A logs in to the game using the first account "Warrior123", and Player B logs in to the same game using the second account "Mage456".

[0069] S304, Identification display: On the game interface, player A's character has the identifier "Warrior 123" displayed above their head, and player B's character has the identifier "Mage 456" displayed above their head.

[0070] S306, Ownership Confirmation: The game server records and confirms that "Warrior 123" and "Mage 456" belong to player A and player B respectively, ensuring the uniqueness and ownership of the identifiers.

[0071] S308, Interaction Recognition: When player A and player B interact in the game, the system uses account identifiers to identify and process their social, team-up, and other requests.

[0072] Therefore, through account identifiers, the system can quickly verify user identity, ensuring the security of transactions and interactions. Each user's account identifier is unique, enhancing the personalized user experience. The server can detect user's gaming behavior based on the account identifier for data analysis and optimization of the gaming experience.

[0073] In an exemplary embodiment, taking an online battle arena (MOBA) application as an example, the steps include, but are not limited to, the following:

[0074] S1, Account Login: User C logs into the MOBA game using the first account "Assassin7", and User D logs in using the second account "Sniper8".

[0075] S2, the identifier shows: In the game's matchmaking queue and loading screen, "Assassin 7" is displayed next to user C's character, and "Sniper 8" is displayed next to user D's character.

[0076] S3, Ownership Confirmation: When a user logs in, the game server verifies the ownership of the account identifier to ensure that "Assassin 7" and "Sniper 8" are associated with user C and user D respectively.

[0077] S4, In-game Interaction: In the game, users can click on another user's account icon to view their profile, send friend requests, or report them.

[0078] Therefore, account identifiers not only serve as identifiers of user identity, but also involve the technical aspects of the game, such as identity verification, data detection, and social functions, all of which are achieved through the uniqueness and ownership of account identifiers.

[0079] S204, in response to the first account sending a first identifier request to the second account, display a first event, wherein the first identifier request is used to indicate that the first account requests the second account to acquire ownership of the identifier of the second account;

[0080] Optionally, in this embodiment, the aforementioned first identifier request represents a request sent by the first account to the second account, with the purpose of acquiring ownership of the second account's identifier. For example, in a game application, user "Xiaocao" wants to obtain the nickname of user "Xihaiji" and therefore sends an identifier request. In a social application, the account registered and logged in by user "@Sunshine" can be referred to as the first account, and user "@Sunshine" wants to obtain the identifier of user "@Moonlight" and therefore sends an identifier request.

[0081] Optionally, in this embodiment, the aforementioned first event may include, but is not limited to, an event displayed on the game interface after the first account sends the first identifier request, indicating that the first account has pending tasks. For example, in a game application, when user "Little Grass" sends an identifier request to user "Washing Machine," the system will display a request box on user "Little Grass's" game interface to instruct user "Little Grass" on how to obtain the identifier "Washing Machine." In a social application, when "@Sunshine" sends an identifier request to "@Moonlight," the system will display a request box on "@Sunshine's" interface to instruct user "@Sunshine" on how to obtain the identifier "@Moonlight."

[0082] In one exemplary embodiment, Figure 4 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application, including but not limited to the following steps:

[0083] S1, User A and User B log in to the target application. User A's account nickname is "Warrior123" and User B's account nickname is "Mage456".

[0084] S2, responding to user A's request for... Figure 4 On the application interface shown, user B's nickname "Mage456" performs an interactive operation, displaying a drop-down menu. This drop-down menu includes operations that user A can perform, including but not limited to "trade nickname" and "evaluate nickname". "Trade nickname" is used to initiate a nickname claim request to user B, while "evaluate nickname" is used to inform user B of user A's evaluation of the nickname "Mage456".

[0085] S3, responding to user A's request for... Figure 4 The application interface shown shows that the "Trade Nickname" interaction operation displays the first event, which includes the task that user A needs to perform to obtain the nickname "Mage456" through trading. This includes, but is not limited to, random tasks, upgrading user B's mount, recharging user B's membership, and gifting virtual resources such as diamonds to user B. Alternatively, it may include, but is not limited to, application services that user A and user B can participate in together, such as playing a game, having a live PK between user A and user B, or completing a task together.

[0086] S4, responding to user A's request for... Figure 4 The interaction with the "Give User B 500 Diamonds" option on the application interface shown completes the first event mentioned above.

[0087] S206, In the event that the event has been completed, the account identifier of the first account is replaced with the second account identifier, wherein the ownership of the second account identifier is transferred to the first account.

[0088] Optionally, in this embodiment, the aforementioned event completion can be understood as the identification request sent by the first account to the second account being accepted, and the first account having completed the task indicated by the first event. For example, in a game application, user A (the first account) requests user B's (the second account) team identification. After user B agrees, a first event is generated. Once the task corresponding to the first event is executed by user A, the first event is considered complete. In a social application, user A requests to use user B's specific topic hashtag. After user B agrees, a first event is generated. Once the task corresponding to the first event is executed by user A, the first event is considered complete.

[0089] Optionally, in this embodiment, the aforementioned change of ownership means that the ownership of the second account identifier is transferred from the second account to the first account. For example, in a game application, after user A successfully receives user B's identifier, the ownership of the identifier "Little Grass" is transferred from user B to user A. In a social application, after user A successfully receives user B's hashtag, the ownership of the identifier "#GlobalTravel" is transferred from user B to user A.

[0090] It should be noted that the above-mentioned ownership transfer can be subject to a corresponding time limit. That is, when the ownership transfer reaches a certain time limit, the ownership will be transferred back from user A to user B. The above-mentioned time limit can be related to the above-mentioned event. For example, different time limits can be set according to the number of diamonds given away.

[0091] In both scenarios described above, the change of ownership means that the first account can now legally use the identifier that originally belonged to the second account, and this identifier is unique on the platform and will not conflict with the identifiers of other accounts. This change is achieved through an update of the backend database to ensure that the transfer of identifier ownership is accurate.

[0092] In one exemplary embodiment, Figure 5 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application, including but not limited to the following steps:

[0093] S1, User A regarding such Figure 4 The application interface shown prompts you to perform an interactive operation to "Give User B 500 Diamonds".

[0094] S2, User A transferred 500 virtual diamonds to User B;

[0095] S3, in response to the transfer of 500 virtual diamonds, confirming the completion of the first event mentioned above, user A's account identifier has changed from "Warrior123" to "Mage456", and user B's account identifier is no longer displayed as "Mage456".

[0096] The above is merely an example, and this application does not impose any specific limitations.

[0097] It should be noted that after the second account transfers ownership of the second account identifier to the first account, the second account identifier can be flexibly set. It can be an account identifier pre-stored by the second account, or it can be an account identifier randomly set by the system for the second account. The identifier reset by the second account is different from the account identifiers of other accounts in the target application and is also a unique account identifier.

[0098] It should also be noted that the aforementioned first event can also be an event displayed on the application interface corresponding to the second account and completed by the second account, such as an event that asks the second account for consent, or an event in which the second account issues exchange conditions, etc.

[0099] In this embodiment, when the first account and the second account log in to the target application simultaneously, the application interface will display two different account identifiers, representing the first account and the second account respectively. These identifiers are unique, and the ownership of each identifier strictly corresponds to its registered account. When the first account wishes to acquire the identifier of the second account, the target application will trigger a request event, signifying that the first account has formally requested the second account to acquire ownership of its identifier. Once the identifier request event is processed and the second account agrees to transfer the identifier ownership to the first account, the target application updates the first account's identifier to the second account's identifier and formally transfers the ownership of the second account's identifier to the first account. This achieves the goal of ensuring that the transfer of ownership of the account identifier is both secure and efficient, thereby providing users with a smooth interactive experience. It allows account identifiers to be changed between different accounts, enabling users to use their desired account identifiers. This solves the technical problem of duplicate account identifiers, which prevents users from using their preferred account identifiers.

[0100] As an optional approach, in response to the first account sending a first identifier request to the second account, the first event is displayed, including:

[0101] In response to the first account sending a first identifier request to the second account, a request prompt message is displayed on the application interface of the second account. The request prompt message is used to inform the second account that the first account is requesting the second account to acquire ownership of the second account's identifier.

[0102] In response to the second account performing a first interactive operation on the request prompt message, a first event is displayed on the application interface of the first account, wherein the first interactive operation is used to indicate that the second account allows the first account to initiate the process of obtaining the second account's identifier.

[0103] Optionally, in this embodiment, the aforementioned request notification message can be understood as informing the second account that the first account is requesting ownership of the second account identifier from the second account. That is, it can inform the second account that the first account is currently requesting ownership of the second account identifier. The aforementioned first interactive operation and the other interactive operations described below can be understood as a series of actions performed between the user and the system to achieve a specific function or task, such as clicking, dragging and dropping, scrolling, swiping, long pressing, and zooming.

[0104] In one exemplary embodiment, taking a massively multiplayer online role-playing game (MMORPG) as an example, Figure 6 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, which may include, but is not limited to, the following steps:

[0105] S1, Sending an identifier request: User A (first account) discovers a rare identifier belonging to User B (second account) in the game and wants to acquire ownership of it. User A sends an identifier request to User B through the in-game trading system.

[0106] S2, display request prompts: such as Figure 6 As shown, a system notification message pops up on User B's game interface, informing User A that User A is requesting to acquire ownership of User B's identifier.

[0107] S3, perform interactive operations: such as Figure 6 As shown, User B views the request and decides to accept it. He performs a confirmation action in the game, such as clicking the "yes" button.

[0108] S4, displays the first event: such as Figure 6 As shown, an event notification appears on User A's game interface, indicating that User B has allowed him to initiate the process of obtaining the identifier. At this time, User A can initiate the process of obtaining the second account identifier as needed.

[0109] This embodiment enhances the user experience through intuitive prompts and event notifications, enabling users to easily understand and respond to complex interaction processes. Formal request and confirmation processes ensure transaction security and transparency, preventing fraud and misunderstandings. Users receive prompt feedback, accelerating the pace of in-game social interaction and transactions. Simplified operation processes allow users to make quick decisions, enhancing game interactivity. Clear request and response processes provide users with a clear transaction path, reducing uncertainty during transactions.

[0110] In an exemplary embodiment, taking a social media platform as an example, the steps may include, but are not limited to, the following:

[0111] S1, Sending an identifier request: User E (first account) sees a popular hashtag belonging to User F (second account) in a social application and wants to use this hashtag. User E sends a request to User F via a message.

[0112] S2, Display request prompt: User F's notification center displays a message from User E requesting ownership of the tag.

[0113] S3, Perform interactive operation: After reading the information, user F decides to agree and replies with an "agree" message.

[0114] S4, First event displayed: A notification is displayed on user E's application interface, indicating that user F has allowed him to start using the tag. At this time, the ownership of the tag is transferred from user F to user E, that is, user E is prohibited from using the tag anymore.

[0115] In this embodiment, the social media platform enhances user experience by providing a clear notification system that allows users to easily manage and respond to incoming requests. Allowing users to use popular hashtags increases content visibility and engagement. Formal request and confirmation processes enable users to build and maintain professional networks, enhancing the platform's commercial value. Simplified request and response mechanisms allow users to quickly process professional requests, improving efficiency. Clear communication and agreement processes help build trust among users, laying the foundation for future collaborations.

[0116] As an optional approach, in response to the second account performing a first interactive operation on the request prompt message, a first event is displayed on the application interface of the first account, including at least one of the following:

[0117] In response to the second account performing the first interactive operation on the request prompt message, a first resource transfer event is displayed on the application interface of the first account, wherein the first resource transfer event indicates that the first account needs to transfer virtual resources to the second account;

[0118] In response to the second account performing the first interactive operation on the request prompt message, a second resource transfer event is displayed on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to help the second account transfer virtual resources to the third account;

[0119] In response to the second account performing the first interactive operation on the request prompt message, a relationship establishment event is displayed on the application interface of the first account, whereby the relationship establishment event indicates that the first account needs to change social relationships.

[0120] Optionally, in this embodiment, in a game scenario, the aforementioned first resource transfer event includes, but is not limited to, an event indicating that the first account needs to transfer virtual resources to the second account. For example, in a game scenario, user A (the first account) requests to obtain the account identifier of user B (the second account). After user B agrees, the game interface displays that user A needs to transfer a certain amount of gold coins (virtual resources) to user B. In a social scenario, user A (the first account) requests to obtain the user identifier of user B (the second account) and needs to send virtual gifts to user B (the second account).

[0121] In one exemplary embodiment, Figure 7 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application. The above-mentioned response to the second account performing a first interactive operation on the request prompt message, displaying the first resource transfer event on the application interface of the first account, can be as follows: Figure 7 As shown, User A gives User B 500 diamonds in order to obtain User B's account identifier "Mage456".

[0122] Optionally, in this embodiment, in a game scenario, the aforementioned second resource transfer event includes, but is not limited to, an event indicating that the first account needs to help the second account transfer virtual resources to the third account. For example, in a game scenario, user A (the first account) helps user B (the second account) transfer in-game items (virtual resources) to user C or a system account (the third account) to obtain user B's (the second account's) account identifier. In a social scenario, user A (the first account) helps user B (the second account) forward a tweet containing points rewards to user C (the third account) to request user B's (the second account's) user identifier.

[0123] In one exemplary embodiment, Figure 8 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application. The above-mentioned response to the second account performing a first interactive operation on the request prompt message, and displaying the second resource transfer event on the application interface of the first account, can be as follows: Figure 8As shown, user A pays a certain amount of virtual resources to the system account (third account) in order to enable the system account to add "Monthly Noble" privileges to the second account, and then obtain user B's account identifier "Mage456".

[0124] Optionally, in this embodiment, in a game scenario, the aforementioned relationship establishment event includes, but is not limited to, indicating that the first account needs to change its social relationship with the second account, such as adding friends or establishing a guild relationship. For example, if user A (the first account) sends a friend request to user B (the second account), and user B agrees, the game interface displays that a friend relationship has been established between user A and user B. In a social scenario, if user A (the first account) receives a friend request from user B (the second account), and user B agrees, the application interface displays that a friend relationship has been established between user A and user B.

[0125] In one exemplary embodiment, Figure 9 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application. The above-mentioned response to the second account performing a first interactive operation on the request prompt message, displaying a relationship establishment event on the application interface of the first account, can be as follows: Figure 9 As shown, user A sends a close friend request to user B, thereby obtaining user B's account identifier "mage456".

[0126] As an optional approach, in response to the second account performing a first interactive operation on the request prompt message, a second resource transfer event is displayed on the application interface of the first account, including at least one of the following:

[0127] In response to the second account performing the first interactive operation on the request prompt message, a second resource transfer event is displayed on the application interface of the first account. The second resource transfer event indicates that the first account needs to transfer a first amount of virtual resources to the third account in order to upgrade the virtual level of the target virtual item owned by the second account to a preset level.

[0128] In response to the second account performing the first interactive operation on the request prompt message, a second resource transfer event is displayed on the application interface of the first account. The second resource transfer event indicates that the first account needs to transfer a second number of virtual resources to the third account in order to extend the duration of the target permission held by the second account by a first preset duration.

[0129] In response to the second account performing the first interactive operation on the request prompt message, a second resource transfer event is displayed on the application interface of the first account. The second resource transfer event indicates that the first account needs to transfer a third number of virtual resources to the third account in order to transfer the ownership of the preset virtual items to the second account.

[0130] Optionally, in this embodiment, the first account needs to transfer a first amount of virtual resources to the third account to upgrade the virtual level of the target virtual item owned by the second account to a preset level. This can be understood as user A (first account) needing to pay a certain amount of virtual resources to the in-game store (third account) to help user B (second account) upgrade the level of the virtual item they own to a preset level.

[0131] Optionally, in this embodiment, the first account needs to transfer a second amount of virtual resources to the third account in order to extend the duration of the target permissions held by the second account. The first preset duration can be understood as, in the game application, user A needs to pay a certain amount of virtual resources (the second amount of virtual resources) to the game company (the third account) in order to extend user B's VIP membership permissions by one month.

[0132] Optionally, in this embodiment, the first account needs to transfer a third amount of virtual resources to the third account in order to transfer the ownership of the preset virtual item to the second account. This can be understood as, in the game application, user A needs to pay a certain amount of virtual resources (the third amount of virtual resources) to the system account (the third account) in order to purchase a virtual item and transfer its ownership to user B.

[0133] As an optional approach, in response to the second account performing a first interactive operation on the request prompt message, a relationship establishment event is displayed on the application interface of the first account, including at least one of the following:

[0134] In response to the second account performing the first interactive operation on the request prompt message, a relationship establishment event is displayed on the application interface of the first account, whereby the relationship establishment event indicates that the first account needs to add the second account as a friend account;

[0135] In response to the second account performing the first interactive operation on the request prompt message, a relationship establishment event is displayed on the application interface of the first account. The relationship establishment event indicates that the first account needs to join the first preset group. The first preset group indicates the group that the first account has not joined, but the second account has joined.

[0136] In response to the second account performing the first interactive operation on the request prompt message, a relationship establishment event is displayed on the application interface of the first account. The relationship establishment event indicates that the first account needs to leave the second preset group and join the first preset group. The second preset group indicates the group that the first account has already joined.

[0137] Optionally, in this embodiment, the aforementioned relationship establishment event can be understood as the first account needing to establish a certain social relationship with the second account, such as adding friends or joining a group.

[0138] For example, user A (first account) receives a friend request from user B (second account). After user B accepts, the game interface displays a message indicating that user A needs to add user B as a friend. These friend accounts represent a friendly relationship between users; they can be accounts that have added each other as friends. When user A and user B are mutual friends, user A allows access to user B's account identifier.

[0139] Optionally, in this embodiment, the aforementioned first preset group refers to a specific group within the game, to which the first account has not yet joined, while the second account is already a member. For example, in a game application, user B is a member of the "Explorers" guild, and user A (the first account) has not yet joined any guild. User B invites user A to join the "Explorers" guild, which constitutes the first preset group. When user A joins the "Explorers" guild, user A allows access to user B's account identifier.

[0140] It should be noted that joining a group as mentioned above refers to a user accepting an invitation or application to become a member of a game group.

[0141] Optionally, in this embodiment, the aforementioned second preset group refers to a specific group within the game, and the first account is already a member of that group. Leaving the group refers to a user actively leaving or being removed from a game group. For example, if user A decides to leave the "Explorers" team to join user B's "Conquerors" team, user A needs to first leave the second preset group. When user A leaves the "Explorers" team, user A allows access to user B's account identifier.

[0142] In this embodiment, relationship-establishing events typically involve social interactions between users, such as adding friends, joining or leaving groups, etc. These events are implemented through in-game interactions and will display corresponding prompts on the user's application interface to notify the user of the event's occurrence and the required action. Once the user takes the appropriate action, the other user's account identifier can be obtained.

[0143] As an optional solution, in response to the second account performing a first interactive operation on the request prompt message, a first event is displayed on the application interface of the first account, including:

[0144] In response to the second account performing the first interactive operation on the request prompt message, an event collection component is displayed on the application interface of the first account, wherein the event collection component corresponds to a set of events, and the set of events includes the first event;

[0145] In response to the first account performing a second interactive operation on the event collection component, the first event is displayed on the application interface of the first account, wherein the second interactive operation is used to select the first event from a set of events.

[0146] Optionally, in this embodiment, the aforementioned event set component refers to a UI element within the game that contains a set of related events, which users can view and manage through this component. For example, Figure 10 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, such as... Figure 10 As shown, user A's (first account) game interface has a "Random Task" component. This component contains all current task events, i.e., an event collection component. By performing a first interactive operation on the request prompt message through the second account, the event collection component can be displayed on the first account's application interface. Then, the first account performs a second interactive operation on this event collection component to select the first event to be executed.

[0147] As an optional solution, if the first event has been completed, the account identifier of the first account can be replaced with the second account identifier, including at least one of the following:

[0148] If the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event has been completed, the account identifier of the first account will be replaced with the identifier of the second account, and the virtual resources will be transferred from the first account to the second account according to the number of virtual resources to be transferred as indicated by the first event.

[0149] If the first event instructs the first account to transfer virtual resources to the second account, and the first event is not yet completed, the virtual resources will be transferred from the first account to the system account according to the number of virtual resources to be transferred as indicated by the first event; if the first event has been completed for a second preset period, the account identifier of the first account will be replaced with the identifier of the second account, and the virtual resources will be transferred from the system account to the second account according to the number of virtual resources to be transferred as indicated by the first event; if the first event is not completed for a second preset period, a change failure message will be sent to the first account, and the ownership of the virtual resources transferred from the first account to the system account will be revoked.

[0150] Optionally, in this embodiment, replacing the account identifier of the first account with the second account identifier can be understood as directly replacing the displayed first account identifier corresponding to the first account with the second account identifier and canceling the display of the second account identifier corresponding to the second account. It can also be understood as canceling the display of the second account identifier corresponding to the second account and configuring the second account identifier to be allowed to be set as the account identifier of the first account.

[0151] In one exemplary embodiment, such as Figure 10As shown, User A's profile page displays the first account identifier (Warrior 123). After User A completes the first event mentioned above (for example, transferring a certain amount of virtual resources to User B), User A's profile page displays the second account identifier (Mage 456).

[0152] Optionally, in this embodiment, the aforementioned second preset duration can be set according to actual needs; it can be the system default duration or set by the second account. Whether the first event is completed within the second preset duration is determined by the system. If the first event is not completed within the second preset duration, a change failure message is sent to the first account, and the ownership of the virtual resources transferred from the first account to the system account is revoked.

[0153] For example, taking a second preset duration of 3 minutes as an example, the timer starts after the first account initiates a request and the second account responds with permission to start the transfer process. If the first account does not complete the first event within 3 minutes, the virtual resources prepaid by the first account will be deducted, and its ownership of the virtual resources will be canceled. If the first account completes the first event within 3 minutes, the virtual resources prepaid by the first account will be deducted, its ownership of the virtual resources will be canceled, and the virtual resources will be transferred to the second account.

[0154] It should be noted that the aforementioned cancellation of the ownership of virtual resources transferred from the first account to the system account may include, but is not limited to, all or part of the ownership of such virtual resources. If the first account fails to complete the first event, part of such resources may be transferred to the second account, or may not be transferred to the second account.

[0155] In this embodiment, the completion status of the first event determines the flow of virtual resources and the change of account identifier. If the first event is completed, the resources are directly transferred from the first account to the second account, and the account identifier is changed accordingly. If the first event is not completed, the resources are transferred to the system account, and the final destination of the resources is determined based on the completion status of the event after a preset time. If the first event is not completed within the preset time, the system will notify the first account of the change failure and cancel the ownership of the resources previously transferred to the system account. These mechanisms ensure the logic and fairness of in-game transactions and event handling.

[0156] As an optional approach, the above method also includes:

[0157] When both the first account and the second account are logged into the target application, in response to the third interactive operation performed by the second account, the second account identifier is displayed in a preset area, where the preset area represents the display area of ​​the account identifier that allows changes in ownership;

[0158] In response to the first account performing a fourth interactive operation on the second account identifier in the preset area, a first identifier request is sent to the second account, and a first event is displayed.

[0159] Optionally, in this embodiment, the aforementioned preset area can be understood as a pre-defined transaction display area. Accounts wishing to sell their account identifiers can post promotional messages in this area to improve the transaction efficiency of account identifiers. For example, in a game application, the aforementioned preset area may, but is not limited to, a pre-defined area in the game interface used to display specific information or perform specific interactions. The player's transaction interface has a dedicated area for displaying the account identifier of the transaction object; this area is the preset area. The identifier of the second account is displayed in the preset area for other players to identify and interact with.

[0160] In one exemplary embodiment, Figure 11 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application, including but not limited to the following steps:

[0161] S1, User Y (second account) logs into the game and performs a specific action (third interaction), such as clicking the trade button, e.g. Figure 11 As shown, after logging into the game, user Y clicked the "Account Identification Trading" button on the interface.

[0162] S2, in response to user Y's action, the game displays user Y's account identifier in a preset area, such as... Figure 11 As shown, user Y's account identifier "Mage456" is displayed at the top of the transaction window.

[0163] S3, after user X (first account) sees user Y's identifier, they perform an operation on the identifier in the preset area (fourth interaction operation), such as clicking user Y's identifier. Figure 11 As shown, user X clicked on user Y's account identifier "Mage456" in the trading interface.

[0164] S4, the game sends an identifier request (first identifier request) from user X to user Y, and displays an event (first event) on user X's interface. For example... Figure 11 As shown, user X received an event that says "500 diamonds need to be transferred to user Y", which is the first event.

[0165] The above is merely an example, and this application does not impose any specific limitations.

[0166] As an optional approach, the above method also includes at least one of the following:

[0167] If the first event has been completed, the account identifier of the second account will be replaced with the third account identifier that was pre-set for the second account;

[0168] If the first event has been completed, replace the second account's account identifier with a random account identifier automatically generated by the target application;

[0169] If the first event has been completed, the account identifier of the second account will be replaced with the first account identifier.

[0170] Optionally, in this embodiment, the aforementioned third account identifier may include, but is not limited to, another account identifier pre-set by the player, used to replace the current account identifier under specific circumstances. For example, player Y pre-sets a third account identifier "Y_ShadowWalker" in the game application, which is used to replace the second account identifier after it is obtained by another account.

[0171] Optionally, in this embodiment, the random account identifier automatically generated by the target application may include, but is not limited to, the account identifier automatically generated by the game system for the player. It is usually random to maintain the anonymity or novelty of the player's identity.

[0172] Optionally, in this embodiment, replacing the account identifier of the second account with the first account identifier can be understood as the first account relinquishing ownership of the first account identifier after the first account obtains the account identifier of the second account. At this time, the first account identifier is regarded as an unclaimed account identifier, and the second account can first replace it with the account identifier, and then obtain the account identifier of other accounts or modify it manually.

[0173] In one exemplary embodiment, Figure 12 This is a schematic diagram of another optional method for changing an account identifier according to an embodiment of this application. After the first event is completed, the account identifier of the second account is replaced with a pre-set third account identifier, for example, such as... Figure 12 As shown, after user A completes the first event, user B's account identifier "Mage456" is automatically changed to the pre-set "Hunter789". After the first event is completed, the account identifier of the second account is replaced with a random account identifier automatically generated by the target application, for example, as shown below. Figure 12 As shown, user A completes the first event, and user B's account identifier is automatically changed by the system to a randomly generated identifier, such as "New User 1". After the first event is completed, the account identifier of the second account is replaced with the first account identifier, for example, as shown. Figure 12 As shown, user A completed the first event, and user B's account identifier was changed to the identifier of the opponent user A, "Warrior123".

[0174] This example demonstrates the diversity of account identity changes, which can be used to increase interactivity, reward mechanisms, or provide users with a new identity experience.

[0175] As an optional approach, the above method also includes:

[0176] When both the primary account and the streamer account are logged into the virtual live streaming room, the primary account identifier and the live streaming room identifier are displayed. The target application includes the virtual live streaming room, and the live streaming room identifier indicates the identifier set by the streamer account for the virtual live streaming room.

[0177] In response to the first account sending a second identifier request to the streamer account, a second event is displayed, wherein the second identifier request is used to indicate that the first account is requesting the streamer account to obtain the right to use the live broadcast room identifier;

[0178] If the second event has been completed, the account identifier of the first account will be replaced with the live room account identifier. The ownership of the live room account identifier belongs to the first account, and the live room account identifier includes the first account identifier and the live room identifier.

[0179] Optionally, in this embodiment, the display of the first account identifier and the live stream identifier can be interpreted as follows: in the virtual live stream room, when both the first account (viewer) and the streamer's account are logged in, the system will display a special identifier set by the streamer for the live stream room on the interface. By displaying two different account identifiers, the personalization and recognizability of the live stream room are enhanced, while providing viewers with an identity identifier for interacting with the streamer.

[0180] For example, in a virtual live streaming room, both player A (the first account) and virtual streamer B (the streamer account) are logged in, and the interface displays player A's game nickname and streamer B's exclusive live streaming room identifier.

[0181] It should be noted that the aforementioned response to the first account sending a second identifier request to the streamer's account can be understood as the first account (viewer) sending a request to the streamer in the live stream, hoping to obtain the right to use the live stream identifier. This request mechanism allows interaction between the viewer and the streamer, increasing the sense of participation and interactivity in the live stream. For example, in some social applications, viewer C clicks the "Request to Join" button in the live stream, sending a request to streamer D, hoping to obtain a membership identifier for streamer D's live stream.

[0182] On the other hand, the aforementioned display of the second event can be understood as follows: after the first account sends an identifier request to the streamer account, the system will display an event (the second event) on the application interface of the first account, prompting the first account on how to obtain the live stream identifier.

[0183] Furthermore, replacing the first account's identifier with the livestream room's identifier can be understood as follows: after the first event is completed, the first account's identifier is replaced with a new identifier that includes the livestream room identifier, and the ownership of this new identifier belongs to the first account. This identifier change increases the sense of belonging and honor within the livestream room, while also facilitating the management and identification of the livestream room. In the virtual livestream room, player G completes the challenge set by streamer H (the first event is complete), and his account identifier is changed to "H Livestream Room Member - G".

[0184] In one exemplary embodiment, Figure 13 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, such as... Figure 13 As shown, "host nickname" is the live stream identifier mentioned above. This live stream identifier can be configured for the first account that has completed the second event, that is, mimie1_host nickname, mimie2_host nickname, mimie3_host nickname.

[0185] As an optional solution, in response to the first account sending a second identifier request to the streamer account, a second event is displayed, including:

[0186] In response to a promotional request sent by the streamer's account, an event notification message is published in the virtual live stream room;

[0187] In response to the first account performing the fifth interactive operation on the event notification message, a second identifier request is sent to the broadcaster account, and the second event is displayed on the application interface of the first account.

[0188] Optionally, in this embodiment, the aforementioned response to a streamer's account sending a promotional request for their livestream identifier, and the subsequent publication of an event notification message in the virtual livestream room, can be understood as follows: when a streamer sends a request in the game to promote or share their livestream identifier, the system will publish an event notification message in the livestream room to notify the audience of this request. For example, in the virtual livestream room, virtual streamer K sends a request, hoping that viewers will use a specific livestream identifier. The system then publishes an event notification message in the livestream room. This real-time event notification message enhances the interaction between the streamer and the audience, enabling viewers to understand and participate in the streamer's activities, thereby increasing the activity and engagement of the livestream room.

[0189] For example, the aforementioned response to the first account performing the fifth interactive operation on the event notification message, sending a second identifier request to the broadcaster's account, can be understood as the viewer (first account) seeing the identifier promotion request sent by the broadcaster, and then performing a specific interactive operation (such as clicking the notification message) to send a request to the broadcaster, hoping to obtain the right to use the live broadcast room identifier. For instance, after viewer L sees the identifier promotion request of broadcaster K in the virtual live broadcast room, clicks the notification message, and sends a request to broadcaster K, hoping to use broadcaster K's live broadcast room identifier. By allowing viewers to interact with the event notification message, the system can collect viewer feedback and participation intentions, providing broadcasters with a channel to interact with viewers, and also providing viewers with a way to express support and participation.

[0190] It should be noted that the aforementioned display of the second event on the application interface of the first account can be understood as the system displaying a new event (the second event) on its application interface after the viewer (the first account) performs the fifth interactive operation. This event may be a response to the viewer's request or a further instruction. In an exemplary embodiment, Figure 14 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, such as... Figure 14 As shown, streamer K announces via advertisement that this live stream has a unique nickname. After viewer L sends a request, a new event appears on their interface, prompting them to choose whether to obtain the nickname. If L chooses to obtain the nickname, a task is initiated to transfer virtual resources to the streamer's account or to acquire the virtual live stream. When L confirms the transfer or task, a component triggers the request. Once the transfer or task is completed, the request is considered successfully sent, and the viewer awaits streamer K's response. This second event provides immediate feedback on the viewer's actions, enhancing user experience consistency and satisfaction. It also provides viewers with clear expectations and anticipation, increasing the transparency of the interaction.

[0191] This embodiment demonstrates the interaction process between the host and the audience in a virtual live streaming room. Through event notification messages and interactive operations, the interactivity and participation of the live streaming room are enhanced, thereby improving the user experience.

[0192] As an optional solution, if the second event has been completed, the account identifier of the first account will be replaced with the live stream account identifier, including:

[0193] If the second event has been completed, synthesize the live stream account identifier based on the first account identifier and the live stream identifier;

[0194] The account identifier of the first account will be replaced with the live room account identifier, and corresponding permissions will be assigned to the first account. Accounts with the live room identifier in the virtual live room are allowed to participate in promotional activities released by the virtual live room. When an account with the live room account identifier leaves the virtual live room, the account identifier used will be the live room account identifier.

[0195] Optionally, in this embodiment, the above-mentioned synthesis of a live stream account identifier based on the first account identifier and the live stream identifier when the second event has been completed can be understood as follows: when a specific second event (e.g., a viewer completes a task or meets a certain condition) is completed, the system combines the viewer's personal account identifier with the live stream identifier to generate a new live stream account identifier. For example, in a live stream, if viewer Z (first account) completes the challenge set by the streamer (the second event has been completed), the system combines Z's game nickname with the live stream's exclusive identifier to generate a new live stream account identifier, "Z Live Stream Warrior". This synthesized identifier enhances the viewer's sense of belonging and the team spirit of the live stream, while also providing a way for the live stream to identify and reward active viewers.

[0196] For example, replacing the first account's identifier with the live stream account identifier and assigning corresponding permissions to the first account can be understood as replacing the viewer's original account identifier with a new live stream account identifier, and the system granting this new identifier specific permissions, such as participating in live stream promotional activities. For instance, in a live stream, viewer A's account identifier is replaced with "Live Stream VIP-A," and they gain the right to participate in exclusive live stream activities. This replacement and permission allocation not only increases viewer participation but also facilitates live stream management, enabling viewers with specific identifiers to enjoy more interaction and privileges.

[0197] Furthermore, the provision that accounts with the livestream icon in the aforementioned virtual livestream room are allowed to participate in promotional activities launched by the virtual livestream room can be understood as meaning that only accounts with the livestream icon in their account identifiers are eligible to participate in promotional activities organized by the livestream room. For example, in a virtual livestream concert, only viewers whose account identifiers have been updated to include the "Concert Exclusive" icon, such as "User X - Concert Exclusive," can participate in the livestream room's lucky draw. This method can effectively identify and attract viewers with high engagement and loyalty to the livestream room, while also providing a target audience for the livestream room's promotional activities.

[0198] It's important to note that the account identifier used by the aforementioned accounts with the livestream room identifier even after leaving the virtual livestream room can be understood as the same identifier acquired during the livestream, still containing the livestream room identifier. For example, after leaving the livestream room, viewer B's account identifier remains "B-Livestream Room Exclusive," which may appear in other contexts as proof of their participation in a specific livestream activity. This continuous identifier display enhances the sustained impact of the livestream activity and provides viewers with a form of social currency, increasing their social interaction and sense of belonging.

[0199] In one exemplary embodiment, Figure 15 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, such as... Figure 15 As shown, a user enters live room 1 with the nickname mimie1. After completing the second event, the user obtains the nickname XX of live room 1 and automatically changes their own nickname to mimie1_XX. Afterwards, the user enters live room 2, whose nickname is AA. The user has not yet completed the second event set in live room 2, so the user's nickname is still mimie1_XX.

[0200] The following specific examples will further explain this application:

[0201] For example, firstly, a user's profile page includes information such as the user's avatar, nickname, birthday, and nationality. When a new user registers, they choose a name, which is deduplicated. If a user already has that name, a notification will be displayed. Similarly, when editing and changing the name on the profile page later, the deduplication check will be performed, indicating that the name is already taken. A catchy nickname often attracts more attention. For instance, in live stream challenges, users can obtain a nickname for a lucky draw designated by the streamer; or they can challenge other users to obtain a nickname, with the user who loses the nickname receiving a satisfactory reward.

[0202] In one exemplary embodiment, in some live streaming rooms, in order to promote their brand, the streamer will require users to have a specific streamer nickname to be eligible for a prize draw. For example, the message may be: "The prize draw in this live streaming room is only valid for people whose nicknames contain 'xxx'." This nickname can be obtained by participating in live streaming room activities (users cannot change this nickname through their profile page, and therefore are not eligible for the prize draw; it's like completing a task will give the user a tag, which is necessary to qualify for the live streaming room prize draw). In this case, users can pay to purchase the live streaming room nickname to keep it permanently active, or they can obtain it by participating in live streaming room tasks.

[0203] It should be noted that if users do not wish to pay for the service, they can click "Complete Task" to see the corresponding tasks on the nickname acquisition task page, including completed and incomplete tasks. Clicking on a task will take them to the corresponding task page, such as the game sharing task. Once the sharing is completed, the task is finished, and the user will receive a permanent nickname for the live stream, along with a pop-up notification. The user can then participate in the streamer's subsequent giveaways. Furthermore, when sending comments in the live stream, the usernames will be displayed with the specific streamer's nickname, allowing the streamer to identify their close fans. The streamer's nickname can also be changed to promote a brand, similar to an advertisement.

[0204] In another exemplary embodiment, user A can initiate a username challenge to user B. When user A initiates the username challenge, user B receives a pop-up notification. User B can click "decline" and will not receive challenge invitations from user A again. If user B clicks "agree," user A enters the challenge task page. Within 5 minutes of the countdown, user A must complete the tasks in the task box to obtain the username.

[0205] It should be noted that after user A completes the task, a congratulatory pop-up will be received saying, "You have completed all the task challenges and you will have B's user nickname." At this time, user B will randomly generate a user nickname, while user A will get the user nickname they want.

[0206] In one exemplary embodiment, Figure 16 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, such as... Figure 16 As shown, user A enters a live stream. The streamer, to promote a brand, launches a prize draw. However, only users whose nicknames contain information about the live stream's brand are eligible to participate. The backend identifies eligible users and adds them to the prize pool. Uneligible users can choose to purchase a special nickname to gain entry into the draw, or they can obtain the nickname by completing tasks. By linking user nicknames with the brand promoted by the streamer, the streamer gains brand promotion, users receive prizes, and users participate in the streamer's activities to earn nicknames, thus increasing the interaction between users and the streamer. In one exemplary embodiment... Figure 17 This is a schematic diagram illustrating another optional method for changing an account identifier according to an embodiment of this application, such as... Figure 17 As shown, user A can challenge user B to a task. After user B agrees, user A completes the corresponding task. When the backend records that all the corresponding tasks have been completed, user A gains a nickname, user B loses the nickname, and user B gains a reward.

[0207] It should be noted that when the task list is empty, it means that user A has completed all tasks, at which point user A receives a nickname. Whenever user A completes a task in the task list, a reward is sent to user B. If user A abandons completing other tasks within the specified time, the reward will not be refunded. This application involves a reward distribution system, a task completion statistics system, a nickname distribution channel, and a lottery eligibility determination system. The logic is clear, the system is highly versatile, and it integrates user nicknames with commercial features, promoting the streamer's brand and bringing additional revenue to users.

[0208] In this embodiment, user A takes on user B's nickname through a challenge. User A obtains a satisfactory nickname, which has high recognizability and attracts more attention and likes. User B then receives nickname benefits. The streamer can link brand information to user nicknames to gain brand promotion. Users can continuously gain eligibility to participate in lucky draws. Users can obtain the nickname for free by completing tasks in the live stream, which increases interaction between users and the streamer in the live stream.

[0209] In addition, User A can add User B as a friend to initiate a nickname exchange; User A can list their nickname for sale, and User B can directly purchase it; the streamer's brand information lottery event can be launched periodically, continuously allowing users to earn benefits and rewarding users whose nicknames contain brand information.

[0210] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0211] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0212] According to another aspect of the embodiments of this application, an account identifier changing apparatus for implementing the above-described account identifier changing method is also provided. For example... Figure 18 As shown, the device includes:

[0213] The first display module 1802 is used to display a first account identifier and a second account identifier when both the first account and the second account are logged into the target application. The ownership of each account identifier in the target application belongs to the corresponding unique account, and each account identifier is different. The ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account.

[0214] The second display module 1804 is used to display a first event in response to the first account sending a first identifier request to the second account, wherein the first identifier request is used to indicate that the first account requests the second account to acquire ownership of the identifier of the second account;

[0215] The replacement module 1806 is used to replace the account identifier of the first account with the second account identifier when the first event has been completed, wherein the ownership of the second account identifier is changed to belong to the first account.

[0216] As an optional solution, the device is configured to respond to the first account sending a first identifier request to the second account by displaying a first event in the following manner: In response to the first account sending the first identifier request to the second account, a request prompt message is displayed on the application interface of the second account, wherein the request prompt message is used to inform the second account that the first account is requesting ownership of the second account identifier from the second account; In response to the second account performing a first interactive operation on the request prompt message, the first event is displayed on the application interface of the first account, wherein the first interactive operation is used to indicate that the second account allows the first account to initiate the process of acquiring the second account identifier.

[0217] As an optional solution, the device is configured to respond to the second account's response to the request prompt message by performing a first interactive operation, and display the first event on the application interface of the first account in at least one of the following ways: responding to the second account's response to the request prompt message by performing the first interactive operation, displaying a first resource transfer event on the application interface of the first account, wherein the first resource transfer event indicates that the first account needs to transfer virtual resources to the second account; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying a second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to help the second account transfer virtual resources to a third account; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying a relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to change social relationships.

[0218] As an optional solution, the device is configured to respond to the second account's response to the request prompt message by performing a first interactive operation, and display a second resource transfer event on the application interface of the first account in at least one of the following ways: responding to the second account's response to the request prompt message by performing the first interactive operation, displaying the second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to transfer a first number of virtual resources to the third account to upgrade the virtual level of the target virtual item owned by the second account to a preset level; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying the second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to transfer a second number of virtual resources to the third account to extend the duration of the target permission owned by the second account by a first preset duration; responding to the second account's response to the request prompt message by performing the first interactive operation, displaying the second resource transfer event on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to transfer a third number of virtual resources to the third account to transfer ownership of the preset virtual item to the second account.

[0219] As an optional solution, the device is configured to respond to the second account's request prompt message by performing a first interactive operation, displaying a relationship establishment event on the application interface of the first account in at least one of the following ways: responding to the second account's request prompt message by performing a first interactive operation, displaying the relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to add the second account as a friend account; responding to the second account's request prompt message by performing a first interactive operation, displaying the relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to join a first preset group, the first preset group indicating a group that the first account has not joined but the second account has already joined; responding to the second account's request prompt message by performing a first interactive operation, displaying the relationship establishment event on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to leave a second preset group and join the first preset group, the second preset group indicating a group that the first account has already joined.

[0220] As an optional solution, the device is configured to respond to the second account's request prompt message by performing a first interactive operation, displaying the first event on the application interface of the first account in the following manner: responding to the second account's request prompt message by performing the first interactive operation, displaying an event set component on the application interface of the first account, wherein the event set component corresponds to a set of events, the set of events including the first event; responding to the first account's event set component by performing a second interactive operation, displaying the first event on the application interface of the first account, wherein the second interactive operation is used to select the first event from the set of events.

[0221] As an optional solution, the device is configured to replace the account identifier of the first account with the second account identifier in the event that the first event has been completed by at least one of the following methods: when the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event has been completed, replace the account identifier of the first account with the second account identifier, and transfer the virtual resources from the first account to the second account according to the number of virtual resources transferred as indicated by the first event; when the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event has not been completed, transfer the virtual resources from the first account to the system account according to the number of virtual resources transferred as indicated by the first event; when the first event has been completed for a second preset duration, replace the account identifier of the first account with the second account identifier, and transfer the virtual resources from the system account to the second account according to the number of virtual resources transferred as indicated by the first event; when the first event has not been completed for the second preset duration, send a change failure message to the first account, and cancel the ownership of the virtual resources transferred from the first account to the system account by the first account.

[0222] As an optional solution, the device is further configured to: when both the first account and the second account are logged into the target application, in response to a third interactive operation performed by the second account, display the second account identifier in a preset area, wherein the preset area represents a display area for an account identifier that allows changes in ownership; in response to the first account performing a fourth interactive operation on the second account identifier in the preset area, send the first identifier request to the second account and display the first event.

[0223] As an optional solution, the device is further configured to perform at least one of the following steps: when the first event has been completed, replacing the account identifier of the second account with a third account identifier pre-set by the second account; when the first event has been completed, replacing the account identifier of the second account with a random account identifier automatically generated by the target application; when the first event has been completed, replacing the account identifier of the second account with the first account identifier.

[0224] As an optional solution, the device is further configured to: display the first account identifier and the live stream identifier when both the first account and the streamer account are logged into the virtual live stream room, wherein the target application includes the virtual live stream room, and the live stream identifier represents the identifier set by the streamer account for the virtual live stream room; display a second event in response to the first account sending a second identifier request to the streamer account, wherein the second identifier request indicates that the first account is requesting the streamer account to obtain the right to use the live stream identifier; and, if the second event has been completed, replace the first account identifier with the live stream account identifier, wherein the ownership of the live stream account identifier belongs to the first account, and the live stream account identifier includes the first account identifier and the live stream identifier.

[0225] As an optional solution, the device is configured to respond to the first account sending a second identifier request to the broadcaster account and display a second event in the following manner: in response to the identifier promotion request sent by the broadcaster account, publish an event notification message in the virtual live broadcast room; in response to the first account performing a fifth interactive operation on the event notification message, send the second identifier request to the broadcaster account and display the second event on the application interface of the first account.

[0226] As an optional solution, the device is used to replace the account identifier of the first account with the live room account identifier when the second event has been completed in the following manner: when the second event has been completed, synthesize the live room account identifier based on the first account identifier and the live room identifier; replace the account identifier of the first account with the live room account identifier, and assign corresponding permissions to the first account, wherein an account with the live room identifier in the virtual live room is allowed to participate in the promotional activities published by the virtual live room, and when an account with the live room account identifier leaves the virtual live room, the account identifier used is the live room account identifier.

[0227] In this application embodiment, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0228] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0229] According to one aspect of this application, a computer program product is provided, the computer program product comprising a computer program.

[0230] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0231] Figure 19 A schematic block diagram of a computer system architecture for implementing an electronic device according to embodiments of the present application is shown.

[0232] It should be noted that, Figure 19 The computer system 1900 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0233] like Figure 19 As shown, the computer system 1900 includes a central processing unit (CPU) 1901, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1902 or programs loaded from storage section 1908 into random access memory (RAM) 1903. The RAM 1903 also stores various programs and data required for system operation. The CPU 1901, ROM 1902, and RAM 1903 are interconnected via a bus 1904. An input / output interface 1905 (I / O interface) is also connected to the bus 1904.

[0234] The following components are connected to the input / output interface 1905: an input section 1906 including a keyboard, mouse, etc.; an output section 1907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1908 including a hard disk, etc.; and a communication section 1909 including a network interface card such as a local area network card, modem, etc. The communication section 1909 performs communication processing via a network such as the Internet. A drive 1910 is also connected to the input / output interface 1905 as needed. Removable media 1911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on the drive 1910 as needed so that computer programs read from them can be installed into the storage section 1908 as needed.

[0235] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1909, and / or installed from removable medium 1911. When the computer program is executed by central processing unit 1901, it performs various functions defined in the system of this application.

[0236] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1909, and / or installed from removable media 1911. When the computer program is executed by the central processing unit 1901, it performs various functions provided in the embodiments of this application.

[0237] According to another aspect of the embodiments of this application, an electronic device for implementing the above-described method for changing the account identifier is also provided. This electronic device may be... Figure 1 The terminal device or server shown. This embodiment uses this electronic device as an example for illustration. Figure 20 As shown, the electronic device includes a memory 2002 and a processor 2004. The memory 2002 stores a computer program, and the processor 2004 is configured to execute the steps in any of the above method embodiments via the computer program.

[0238] Optionally, in this embodiment, the aforementioned electronic device may be located in at least one of a plurality of network devices in a computer network.

[0239] Optionally, in this embodiment, the processor may be configured to execute the methods in the embodiments of this application via a computer program.

[0240] Alternatively, as those skilled in the art will understand, Figure 20 The structure shown is for illustrative purposes only. Figure 20 This does not limit the structure of the aforementioned electronic devices. For example, the electronic device may also include components that are more... Figure 20 The more or fewer components shown (such as network interfaces, etc.), or having the same Figure 20 The different configurations shown.

[0241] The memory 2002 can be used to store software programs and modules, such as the program instructions / modules corresponding to the account identifier change method and apparatus in this embodiment. The processor 2004 executes various functional applications and data processing by running the software programs and modules stored in the memory 2002, thereby implementing the aforementioned account identifier change method. The memory 2002 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 2002 may further include memory remotely located relative to the processor 2004, and these remote memories can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. Specifically, the memory 2002 may be used, but is not limited to, to store information such as account identifiers. As an example, such as... Figure 20 As shown, the memory 2002 may include, but is not limited to, the first display module 1602, the second display module 1604, and the replacement module 1606 in the account identifier changing device. Furthermore, it may include, but is not limited to, other module units in the account identifier changing device, which will not be described in detail in this example.

[0242] Optionally, the aforementioned transmission device 2006 is used to receive or send data via a network. Specific examples of the network may include wired and wireless networks. In one example, the transmission device 2006 includes a Network Interface Controller (NIC), which can be connected to other network devices and a router via a network cable to communicate with the Internet or a local area network. In another example, the transmission device 2006 is a Radio Frequency (RF) module used for wireless communication with the Internet.

[0243] In addition, the aforementioned electronic device also includes: a display 2008 for displaying the account identifier; and a connection bus 2010 for connecting the various module components in the aforementioned electronic device.

[0244] In other embodiments, the aforementioned terminal device or server can be a node in a distributed system, wherein the distributed system can be a blockchain system, which is a distributed system formed by connecting multiple nodes through network communication. The nodes can form a peer-to-peer network, and any form of computing device, such as a server, terminal, or other electronic device, can become a node in the blockchain system by joining this peer-to-peer network.

[0245] According to one aspect of this application, a computer-readable storage medium is provided, wherein a processor of an electronic device reads computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the electronic device to perform the account identifier change method provided in various alternative implementations of the above-described account identifier change aspect.

[0246] Optionally, in this embodiment, the computer-readable storage medium described above may be configured to store methods for performing the embodiments of this application.

[0247] Optionally, in this embodiment, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0248] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0249] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part 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 one or more electronic devices to execute all or part of the steps of the methods described in the various embodiments of this application.

[0250] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0251] In the several embodiments provided in this application, it should be understood that the disclosed application can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0252] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0253] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0254] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for changing an account identifier, characterized in that, include: When both the first account and the second account are logged into the target application, the first account identifier and the second account identifier are displayed. The ownership of each account identifier in the target application belongs to the corresponding unique account, and each account identifier is different. The ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account. In response to the first account sending a first identifier request to the second account, a first event is displayed, wherein the first identifier request is used to indicate that the first account is requesting the second account to acquire ownership of the identifier of the second account; If the first event has been completed, the account identifier of the first account will be replaced with the second account identifier, wherein the ownership of the second account identifier will be transferred to the first account.

2. The method according to claim 1, characterized in that, The response to the first account sending a first identifier request to the second account, displaying the first event, includes: In response to the first account sending the first identifier request to the second account, a request prompt message is displayed on the application interface of the second account, wherein the request prompt message is used to inform the second account that the first account is requesting the second account to acquire ownership of the second account identifier; In response to the second account performing a first interactive operation on the request prompt message, the first event is displayed on the application interface of the first account, wherein the first interactive operation is used to indicate that the second account allows the first account to initiate the process of obtaining the second account identifier.

3. The method according to claim 2, characterized in that, The response of the second account performing a first interactive operation on the request prompt message, and displaying the first event on the application interface of the first account, includes at least one of the following: In response to the second account performing a first interactive operation on the request prompt message, a first resource transfer event is displayed on the application interface of the first account, wherein the first resource transfer event indicates that the first account needs to transfer virtual resources to the second account; In response to the second account performing the first interactive operation on the request prompt message, a second resource transfer event is displayed on the application interface of the first account, wherein the second resource transfer event indicates that the first account needs to help the second account transfer virtual resources to the third account; In response to the second account performing the first interactive operation on the request prompt message, a relationship establishment event is displayed on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to change social relationships.

4. The method according to claim 3, characterized in that, The response of the second account performing a first interactive operation on the request prompt message, and displaying a second resource transfer event on the application interface of the first account, includes at least one of the following: In response to the second account performing the first interactive operation on the request prompt message, the second resource transfer event is displayed on the application interface of the first account. The second resource transfer event indicates that the first account needs to transfer a first number of virtual resources to the third account in order to upgrade the virtual level of the target virtual item owned by the second account to a preset level. In response to the second account performing the first interactive operation on the request prompt message, the second resource transfer event is displayed on the application interface of the first account. The second resource transfer event indicates that the first account needs to transfer a second number of virtual resources to the third account in order to extend the duration of the target permission held by the second account by a first preset duration. In response to the second account performing the first interactive operation on the request prompt message, the second resource transfer event is displayed on the application interface of the first account. The second resource transfer event indicates that the first account needs to transfer a third number of virtual resources to the third account in order to transfer the ownership of the preset virtual items to the second account.

5. The method according to claim 3, characterized in that, The response to the second account performing a first interactive operation on the request prompt message, displaying a relationship establishment event on the application interface of the first account, includes at least one of the following: In response to the second account performing a first interactive operation on the request prompt message, the relationship establishment event is displayed on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to add the second account as a friend account; In response to the second account performing a first interactive operation on the request prompt message, the relationship establishment event is displayed on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to join a first preset group, and the first preset group indicates a group that the first account has not joined but the second account has joined; In response to the second account performing a first interactive operation on the request prompt message, the relationship establishment event is displayed on the application interface of the first account, wherein the relationship establishment event indicates that the first account needs to leave the second preset group and join the first preset group, and the second preset group indicates the group that the first account has already joined.

6. The method according to claim 2, characterized in that, The response to the second account performing a first interactive operation on the request prompt message, displaying the first event on the application interface of the first account, includes: In response to the second account performing the first interactive operation on the request prompt message, an event collection component is displayed on the application interface of the first account, wherein the event collection component corresponds to a set of events, and the set of events includes the first event; In response to the first account performing a second interactive operation on the event set component, the first event is displayed on the application interface of the first account, wherein the second interactive operation is used to select the first event from the set of events.

7. The method according to claim 1, characterized in that, The step of replacing the account identifier of the first account with the second account identifier after the first event has been completed includes at least one of the following: If the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event has been completed, the account identifier of the first account is replaced with the second account identifier, and the virtual resources are transferred from the first account to the second account according to the number of virtual resources to be transferred as indicated by the first event. If the first event indicates that the first account needs to transfer virtual resources to the second account, and the first event is not yet completed, the virtual resources are transferred from the first account to the system account according to the number of virtual resources to be transferred as indicated by the first event; if the first event has been completed for a second preset period, the account identifier of the first account is replaced with the second account identifier, and the virtual resources are transferred from the system account to the second account according to the number of virtual resources to be transferred as indicated by the first event; if the first event is not completed for the second preset period, a change failure message is sent to the first account, and the ownership of the virtual resources transferred from the first account to the system account is revoked.

8. The method according to claim 1, characterized in that, The method further includes: When both the first account and the second account are logged into the target application, in response to the third interactive operation performed by the second account, the second account identifier is displayed in a preset area, wherein the preset area represents the display area of ​​the account identifier that allows changes in ownership; In response to the first account performing a fourth interactive operation on the second account identifier in the preset area, the first identifier request is sent to the second account, and the first event is displayed.

9. The method according to claim 1, characterized in that, The method further includes at least one of the following: If the first event has been completed, the account identifier of the second account will be replaced with a third account identifier pre-set by the second account; If the first event has been completed, the account identifier of the second account will be replaced with a random account identifier automatically generated by the target application; If the first event has been completed, the account identifier of the second account will be replaced with the first account identifier.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: When both the first account and the streamer account are logged into the virtual live streaming room, the first account identifier and the live streaming room identifier are displayed. The target application includes the virtual live streaming room, and the live streaming room identifier represents the identifier set by the streamer account for the virtual live streaming room. In response to the first account sending a second identifier request to the streamer account, a second event is displayed, wherein the second identifier request is used to indicate that the first account is requesting the streamer account to obtain the right to use the live room identifier; If the second event has been completed, the account identifier of the first account will be replaced with the live room account identifier, wherein the ownership of the live room account identifier belongs to the first account, and the live room account identifier includes the first account identifier and the live room identifier.

11. The method according to claim 10, characterized in that, The response to the first account sending a second identifier request to the broadcaster account, displaying a second event, includes: In response to the identification promotion request sent by the broadcaster account, an event notification message is published in the virtual live broadcast room; In response to the first account performing the fifth interactive operation on the event notification message, the second identifier request is sent to the broadcaster account, and the second event is displayed on the application interface of the first account.

12. The method according to claim 10, characterized in that, The step of replacing the account identifier of the first account with the live stream account identifier after the second event has been completed includes: If the second event has been completed, the live stream account identifier is synthesized based on the first account identifier and the live stream identifier; The account identifier of the first account is replaced with the live room account identifier, and corresponding permissions are assigned to the first account. Accounts with the live room identifier in the virtual live room are allowed to participate in promotional activities published by the virtual live room. When an account with the live room account identifier leaves the virtual live room, the account identifier used is the live room account identifier.

13. A device for changing an account identifier, characterized in that, include: The first display module is used to display a first account identifier and a second account identifier when both the first account and the second account are logged into the target application. The ownership of each account identifier in the target application belongs to the corresponding unique account, and each account identifier is different. The ownership of the first account identifier belongs to the first account, and the ownership of the second account identifier belongs to the second account. The second display module is used to display a first event in response to the first account sending a first identifier request to the second account, wherein the first identifier request is used to indicate that the first account requests the second account to acquire ownership of the identifier of the second account; The replacement module is used to replace the account identifier of the first account with the second account identifier when the first event has been completed, wherein the ownership of the second account identifier is changed to belong to the first account.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored computer program, wherein the computer program can be executed by an electronic device to perform the method described in any one of claims 1 to 13.

15. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program performs the steps of the method described in any one of claims 1 to 13.

16. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method described in any one of claims 1 to 13 through the computer program.

Images