Invitation system and inviting method
Through the invitation system and method, the first client generates an application invitation carrying the first role information, and the second client enters the target application and creates a virtual role, solving the problem of lack of interactivity in the existing technology, and improving user experience and online social interaction.
Patent Information
- Application Number
- CN202510683708.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-26
- Publication Date
- 2025-08-15
AI Technical Summary
The application of invitation methods in the prior art lacks online social interaction between the two parties, and cannot improve the interactivity between the inviter and the invited party, resulting in insufficient user experience.
By inviting the first client in the system to generate application invitation information carrying the first role information, the second client enters the target application based on the information and creates a virtual role. The first client synchronizes the second role to enhance online social interaction.
This has achieved close contact between the inviter and the invited party in the target application, and improved user experience and online interactivity.
Smart Images
Figure CN120499147A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of Internet technology, and in particular to an invitation system, an invitation method, a computing device, and a computer-readable storage medium. Background Art
[0002] With the development of internet technology, more and more applications have been developed, and online social interaction based on these applications has become increasingly mature. Currently, online social interaction through applications typically involves one participant generating an application invitation and sending it to friends via instant messaging. This invitation requires participation in the application. This invitation method only rewards both the inviter and the invitee, but does not increase online social interaction between the two parties. The lack of online user connections between the two parties prevents the invitee from interacting with the inviter after entering the application. Therefore, improving the social nature of application invitations, enhancing the interactivity between the inviter and invitee, and enhancing the user experience has become a pressing issue for technical personnel. Summary of the Invention
[0003] In view of this, the embodiments of the present application provide an invitation system. The present application also relates to an invitation method, a computing device, a computer-readable storage medium, and a computer program product to solve the above-mentioned problems existing in the prior art.
[0004] According to a first aspect of an embodiment of the present application, an invitation system is provided, the invitation system including a first client and a second client; The first client is configured to generate application invitation information based on the first role information of the target application, and send the application invitation information to the second client; The second client is configured to enter the target application in response to the first role information in the application invitation information; The first client is further configured to synchronously display the second character in a target application scenario, wherein the second character is a virtual character created by the target application when the user of the second client enters the target application.
[0005] According to a second aspect of an embodiment of the present application, an invitation method is provided, which is applied to an invitation system, wherein the invitation system includes a first client and a second client; The method comprises: The first client generates application invitation information based on the first role information of the target application, and sends the application invitation information to the second client; The second client enters the target application in response to the first role information in the application invitation information; The first client synchronously displays a second character in the target application scenario, wherein the second character is a virtual character created by the target application when the user of the second client enters the target application.
[0006] According to a third aspect of an embodiment of the present application, a computing device is provided, including: memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the above method are implemented.
[0007] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program / instruction, and the computer program / instruction implements the steps of the above method when executed by a processor.
[0008] According to a fifth aspect of an embodiment of the present application, a computer program product is provided, comprising a computer program / instruction, which implements the steps of the above method when executed by a processor.
[0009] In an invitation system provided by one embodiment of the present application, a first client generates an application invitation message containing information about a first role. A user of a second client is directed to a target application based on the first role information, and a second role representing the user of the second client is displayed in the target application scenario on the first client. This friend invitation mode of the system enhances online social interaction between users, closely establishing a connection between the first and second clients and improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 This is a schematic diagram of the structure of an invitation system provided by an embodiment of the present application; Figure 2 1 is a flow chart of an invitation method applied to a first client provided in an embodiment of the present application; Figure 3 This is a schematic diagram of the invitation process of the first client in a game scenario provided by an embodiment of the present application; Figure 4 1 is a flow chart of an invitation method applied to a second client provided in an embodiment of the present application; Figure 5 This is a schematic diagram of the invitation process of the second client in the game scenario provided by an embodiment of the present application; Figure 6 1 is a schematic structural diagram of an invitation device applied to a first client provided in an embodiment of the present application; Figure 71 is a schematic structural diagram of an invitation device applied to a second client provided in an embodiment of the present application; Figure 8 This is a flowchart of an invitation method provided in one embodiment of the present application; Figure 9 This is a structural block diagram of a computing device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0011] The following description sets forth many specific details to facilitate a thorough understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the scope of the present application. Therefore, the present application is not limited to the specific implementations disclosed below.
[0012] The terms used in one or more embodiments of the present application are for the purpose of describing specific embodiments only and are not intended to limit one or more embodiments of the present application. The singular forms "a", "the" and "the" used in one or more embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in one or more embodiments of the present application refers to and includes any or all possible combinations of one or more associated listed items.
[0013] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of the present application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of one or more embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0014] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.
[0015] In the present application, an invitation system is provided. The present application also relates to an invitation method, a computing device, a computer-readable storage medium and a computer program product, which are described in detail one by one in the following embodiments.
[0016] Figure 1FIG2 shows a schematic diagram of the structure of an invitation system provided according to an embodiment of the present application, wherein the invitation system includes a first client 102 and a second client 104; The first client 102 is configured to generate application invitation information based on the first role information of the target application, and send the application invitation information to the second client; The second client 104 is configured to enter the target application in response to the first role information in the application invitation information; The first client 102 is further configured to synchronously display a second character in the target application scenario, wherein the second character is a virtual character created by the target application when the user of the second client enters the target application.
[0017] The first client can be understood as the client for issuing the invitation, and the second client can be understood as the client being invited. In actual applications, when a first user uses the first client to run a target application, the first user can invite a second user to participate in the target application. Based on this, the first user can use the first client to generate an invitation message and send the invitation message to the second client used by the second user, thereby inviting the second user to use the second client to run the target application.
[0018] In actual applications, the target application can be an application running on a client, which can be a computer, smart TV, smart phone, smart wearable device, etc., and this is not limited in the embodiments provided in this application. The target application can be game software, shopping software, video software, etc., and the specific content page of the target application is not limited in the embodiments provided in this application, and the actual application shall prevail. When the first user uses the first client to run the target application, he or she may want to invite other users to experience it together, thereby generating application invitation information.
[0019] To establish a connection between users, the first client also needs the first role information corresponding to the first role when generating the invitation message. The first role information can be understood as information related to the first role required to generate the invitation message, such as the first role identification information and the server identification of the role. The first role information can help the second client establish an association with the first role after entering the target application.
[0020] The application invitation information generated by the first client refers to information used to invite other clients to log in to the target application. In actual applications, the application invitation information can be in the form of links, pictures, QR codes, mini-program codes, etc. In the embodiments provided in this application, there is no limitation on the specific display form of the application invitation information, which is subject to actual application. After the application invitation information is generated, the first client can send the application invitation information to the second client. Specifically, the first client can send the application invitation information to the second client through instant messaging tools, emails, face-to-face sharing, Bluetooth, NFC, etc. In the embodiments provided in this application, there is no limitation on the specific form of sending the application invitation information to the second client, which is subject to actual application.
[0021] The second client, as the invited client, can enter the target application according to the first role information in the application invitation information. The second role is a virtual role created for the second user by the target application after the second user accepts the invitation to join the target application.
[0022] In actual applications, a second user operating a second client can enter the target application based on the application invitation information. Since the second client is the target application opened via the application invitation information, once the second user enters the target application, the target application will create a second character for the second user, and the second character will be displayed synchronously in the target application scene of the first client. The first character information in the application invitation information establishes a connection between the characters in the first and second clients. After entering the target application, the second character can be directly displayed in the target application scene of the first client, facilitating interaction between users in the target application scene.
[0023] The target application scenario is a specific scenario in the target application, such as a game scenario in a game application. In the embodiments provided herein, the target application scenario is not specifically limited; it only requires that the user's virtual character can be embodied in the target application scenario. For example, in a game scenario, a first character controlled by a first user can perform related operations in the target application scenario.
[0024] After the second character enters the target application, the second character will also be synchronously displayed in the target application scene of the first client, so that the two characters can interact in the target application scene, thereby enhancing the user experience.
[0025] In a specific embodiment provided by the present application, the first client is configured to generate application invitation information based on the first role information of the target application, including: The first client is configured to obtain first role information based on a target application, perform encryption processing based on the first role information, obtain invitation encryption parameters, and generate application invitation information according to the invitation encryption parameters.
[0026] In this embodiment, the first client wants to invite the second client to interact, so the first client needs to obtain the first role information in the target application and generate application invitation information according to the first role information.
[0027] In actual applications, during the transmission process, the application invitation information may be maliciously obtained by someone, and malicious information may be added to the application invitation information, thereby causing harm. In order to prevent this from happening, in the process of generating the application invitation information, the first role information can be encrypted to obtain the invitation encryption parameters, and the application invitation information can be generated based on the invitation encryption parameters. In the specific implementation provided in the present application, the encryption process can be implemented by a preset encryption function, such as a hash algorithm, symmetric encryption, asymmetric encryption, etc., and the specific encryption algorithm is not limited in this implementation. Taking the hash algorithm as an example, after obtaining the first role information of the first user, the hash algorithm can be used to calculate the hash value corresponding to the first role information, and the hash value can be added to the application invitation information as the invitation encryption parameter. By encrypting the first role information and adding the encrypted invitation encryption parameters to the application invitation information, the security and non-tamperability of the application invitation information are guaranteed, and the security factor of the application invitation information is improved.
[0028] In another specific embodiment provided in this application, it also includes: The first client is further configured to determine a second role type according to the second role, determine role favorability information according to the second role type, and control the second role to perform a target scenario task in the target application scenario according to the role favorability information.
[0029] In this embodiment, the first client also determines the second role type of the second role. The second role type can be understood as whether the user corresponding to the second role (i.e., the second user) is a new user or an existing user. For example, if the second role type is a new user, it means that the user using the second client has not used the target application. If the second role type is an existing user, it means that the user using the second client has previously logged into the target application and has created a second role in the target application.
[0030] The first client can determine the character affinity information between the first and second characters based on the type of the second character. Character affinity information can be understood as the degree of affinity between the first and second characters, and is used to influence the effectiveness of the interaction between the first and second characters. If the second user is a new user, the character affinity information between the first and second characters can be configured according to preset values, and this character affinity information can be updated during subsequent interactions. If the second user is an existing user, the existing character affinity information between the first and second characters can be retrieved.
[0031] After determining the character favorability information, the first user can control the second character to perform the target scenario task in the target application scenario based on the character favorability information. The target scenario task can be understood as a task performed in the target application scenario. For example, in a strategy game scenario, the first character of the first client works to obtain resources in the target application scenario created by the first client. The first client can invite the second client to participate in the game. When the second user enters the game, the second character is created in the target application scenario and participates in the work in the target application scenario of the first client. The higher the character favorability information, the more resources are obtained through work. The character favorability information can closely connect the first user and the second user, enhancing the online interactive experience between users.
[0032] In another specific embodiment provided in this application, it also includes: The first client is further configured to update the character favorability information according to an interaction event between the first character and the user represented by the second character within the target application.
[0033] In this embodiment, the first client can also interact online with the second client to update character favorability information. For example, in a game scenario, the first user and the second user can update character favorability information through events such as exchanging gifts, increasing chat time, and completing joint tasks. It should be noted that in actual applications, character favorability information can increase or decrease depending on the interaction event. The specific association between interaction events and character favorability information can be based on the actual application configuration and is not limited in this embodiment.
[0034] In another specific embodiment provided by the present application, the invitation system further includes a server; The second client is further configured to obtain first role information in response to the application invitation information, and send verification information to the server based on the first role information; The server is configured to send a verification success message to the second client if it is confirmed that the application invitation information meets the requirements according to the verification information; The second client is further configured to enter the target application upon receiving the verification pass message.
[0035] In the real-time method provided in this application, after a first client sends an application invitation message to a second client, the second client also needs to verify the application invitation message to prevent information tampering. Specifically, the system also includes a server. After receiving the application invitation message, the second client parses the application invitation message and obtains the first role information in the application invitation message. Verification information is generated based on the first role information and sent to the server.
[0036] The server authenticates the first role information based on the verification information. If the verification is successful, it means that the application invitation information has not been tampered with and the application invitation information meets the requirements. In this case, the server sends a verification success message to the second client.
[0037] When the second client receives the verification success message, it can enter the target application for subsequent processing.
[0038] In this embodiment, the first character information is encrypted and transmitted to the second client. The first character information will be restored in the second client through a preset decryption algorithm. The restored first character information will also be synchronized to the server for establishing a relationship between the first user and the second user when the second character is subsequently created, thereby binding the connection between the first user and the second user and realizing subsequent interactive events, friend assistance, invitation rewards, etc.
[0039] In a specific embodiment provided in this application, it also includes: The second client is further configured to determine a second role type of the second role, and if the second role type is an old user, obtain server information corresponding to the second role type, and enter the target application based on the server information; In the case that the second role type is a new user, the first server information in the first role information is obtained, and the server information corresponding to the second role type is determined according to the first server information, and the target application is entered based on the server information.
[0040] In actual applications, the second user using the second client may or may not have used the target application before. If the second user has used the target application before, a corresponding second role already exists in the target application, and the second role type of the second role is "old user". If the second user has not used the target application before, no second role has been created in the target application. When the second role is created, the second role type of the second role is "new user".
[0041] In this embodiment, the processing methods for old users and new users are different. If the second role type is an old user, the second role information corresponding to the second role can be obtained from the server, and the server information corresponding to the second role can be obtained from it, and the target application can be entered based on the server information.
[0042] If the second character is a new user, it is necessary to first register new second character information for it in the server. In this embodiment, it can be registered based on the first character information. Specifically, first obtain the first server information in the first character information. The first server information is the information of the server where the first character server is located. In actual applications, the target application may correspond to multiple servers. If it is a newly registered user, the server information of the second character is determined based on the first server information, so that the server of the second character is closer to the first server, which can better achieve seamless connection of interactive events between the first and second characters, thereby enhancing the user experience.
[0043] In a specific embodiment provided in this application, it also includes: The second client is further configured to, when the second character type is a new user, obtain the first server service time in the first server information; when the first server service time is less than or equal to the preset service time, determine that the first server information is the server information corresponding to the second character type; when the first server service time is greater than the preset service time, determine the server information corresponding to the second character type according to the preset server selection rule.
[0044] In this embodiment, the server information corresponding to the second character type is further determined based on the first server information. Specifically, if the second character type is a new user, the first server's service life is first obtained from the first server information. The first server's service life can be understood as the time from the time the first server was first used to the current time.
[0045] If the first server's service time is less than or equal to the preset service time, it can be determined that the first server corresponding to the first character has a shorter service time, and the second character can be assigned to the server. The first server is then determined to be the server corresponding to the second character, that is, the first server information is determined to be the server information corresponding to the second character type.
[0046] If the service opening time of the first server is longer than the preset service opening time, it means that the first server has been running for a long time and there may be more users in it, which will affect the user's application experience. In this case, the server information corresponding to the second role type can be selected based on the preset server selection rule. The preset server selection rule refers to the rule for selecting a server for the second role from multiple servers. For example, the preset server rule can be to select the server with the shortest service opening time, or to select the server with the geographical location closest to the first server, or to select the server with the least registered users, etc. In the specific implementation method provided in this application, the preset server selection rule is not limited and can be based on actual application.
[0047] In this embodiment, if the second character type is a new user, after determining the server information corresponding to the second character type based on the first server information, the second character can be registered in the server information, thereby facilitating subsequent processing. In this embodiment, after the second client is invited, if the second character type is a new user, the second character's server is determined based on the first server of the first character. This can avoid user isolation caused by multiple servers, ensure smoother interaction between the two characters in the target application scenario, and thus enhance the user's interactive experience.
[0048] In a specific embodiment provided in this application, it also includes: The second client is further configured to play an invitation success animation after entering the target application.
[0049] In this embodiment, in order to further improve the user experience, the second client may play an invitation success animation after entering the target application, thereby improving the user experience.
[0050] In a specific embodiment provided in this application, it also includes: The first client is further configured to control the second role to perform a target scenario task in the target application scenario in response to a control instruction directed to the second role.
[0051] In the real-time method provided by this application, after the second character enters the target application scenario of the first client, the first client can interact with the second character. Specifically, the first client receives a control instruction from the first user directed to the second character, and the control instruction is used to control the second character to perform the corresponding target scenario task in the target application scenario.
[0052] For example, in a game scenario, the target application scenario can be understood as the business scenario of the first character. After the second character enters this business scenario, the first user can control the first client to issue business tasks (such as bartending, chopping wood, cooking, etc.) to the second character. The second character can then perform the corresponding operations in response to these business tasks. This allows the first user to invite the second user to enter the game and interact with them, thereby increasing the positive impression between the first and second characters.
[0053] In the invitation system provided by the embodiments of the present application, when a first client sends an application invitation message to a second client, the first role information is included. This allows the first role information to be used to accurately bind the first and second clients when the second client subsequently accesses the target application. After being invited to the target application, the second client creates a second role, which can then directly access the target application scenario of the first client based on the application invitation information, enhancing the interactive experience between the two parties.
[0054] Secondly, the first character's information is encrypted using an encryption algorithm when it is added to the application invitation message, ensuring the security of the first character's information and preventing it from being tampered with. The first and second characters can then perform interactive events in the target application scenario, thereby updating the character affinity information between the first and second characters, further improving the user experience of online interactions.
[0055] In addition, if the second character is a new user, the server information of the second character can be determined based on the information of the first character, and the friendship relationship between the two parties can be invited simultaneously, avoiding user isolation caused by multiple servers and ensuring seamless connection of online interactive scenes.
[0056] Figure 2 FIG. 1 shows a flow chart of an invitation method applied to a first client according to an embodiment of the present application. Figure 2 As shown, the method includes: Step 202: In response to an invitation instruction for a target application, obtain first role information.
[0057] Step 204: Perform encryption processing according to the first role information to obtain invitation encryption parameters.
[0058] Step 206: Generate application invitation information according to the invitation encryption parameter, and send the application invitation information to the second client.
[0059] In the invitation method applied to a first client provided in an embodiment of the present application, when the first client sends an application invitation message to a second client, the first role information is added. This allows the first role information to be used to accurately bind the first and second clients when the second client subsequently accesses the target application. The first role information is encrypted using an encryption algorithm during the process of adding it to the application invitation message, ensuring the security of the first role information and preventing it from being tampered with. This ensures data security.
[0060] Figure 3 FIG. 1 shows a schematic diagram of an invitation process of a first client in a game scenario provided by an embodiment of the present application, such as Figure 3 As shown, the first client generates a game invitation based on the first character's information and sends it to the second client. After clicking on the game invitation, the second client determines the second user's type. If the second user is a new user, a new user entry is generated for them, followed by a new user favorability score. Based on this, an image of the second character is generated in the first character's city. If the second user is an existing user, the existing user entry and the existing user favorability score are obtained, and based on this, an image of the second character is generated in the first character's city. This completes the user recruitment process.
[0061] Figure 4 FIG. 1 shows a flow chart of an invitation method applied to a second client provided in an embodiment of the present application. Figure 4 As shown, the method includes: Step 402: Determine a second role type of the second role in response to application invitation information of the first client, wherein the application invitation information carries the first role information.
[0062] Step 404: When the second role type is an old user, obtain server information corresponding to the second role type, and enter the target application based on the server information.
[0063] Step 406: When the second role type is a new user, obtain the first server information in the first role information, determine the server information corresponding to the second role type according to the first server information, and enter the target application based on the server information.
[0064] The invitation method applied to the second client provided in the embodiment of the present application determines the server information of the second role according to the second role type of the second role, and enters the target application according to the server information, which can avoid user isolation caused by multiple servers and ensure that the interaction between the two roles in the target application scenario can be smoother.
[0065] Figure 5 FIG. 1 shows a schematic diagram of an invitation process of a second client in a game scenario provided by an embodiment of the present application. Figure 5 As shown, after receiving the game invitation, the second client clicks on it to enter the game. The second client then determines the second user corresponding to the second client. If the second user is an existing user, the default server information for that user is obtained, allowing the user to enter the game. If the second user is a new user, the server determines whether the first character's server has been open for less than seven days. If so, the second character is registered to the first character's server. If not, the second character is registered to the most recently opened server. After registration is complete, the second character enters the game.
[0066] After entering the game, the animation of the second character being recruited is played. After the animation is completed, the second character is displayed in the city of the first character.
[0067] Corresponding to the above method embodiment, the present application also provides an invitation device embodiment applied to the first client. Figure 6 FIG. 1 shows a schematic diagram of a structure of an invitation device applied to a first client provided by an embodiment of the present application. Figure 6 As shown, the device includes: An acquisition module 602 is configured to acquire first role information in response to an invitation instruction for a target application; An encryption module 604 is configured to perform encryption processing according to the first role information to obtain invitation encryption parameters; The sending module 606 is configured to generate application invitation information according to the invitation encryption parameter, and send the application invitation information to the second client.
[0068] In the invitation device for a first client provided in an embodiment of the present application, when the first client sends an application invitation message to a second client, the first role information is added. This allows the first client and the second client to be accurately bound using the first role information when the second client subsequently accesses the target application. The first role information is encrypted using an encryption algorithm during the process of adding it to the application invitation message, ensuring the security of the first role information and preventing it from being tampered with. This ensures data security.
[0069] The above is a schematic diagram of an invitation device for a first client according to this embodiment. It should be noted that the technical solution of the invitation device for the first client and the technical solution of the invitation method for the first client are based on the same concept. For details not described in detail in the technical solution of the invitation device for the first client, please refer to the description of the technical solution of the invitation method for the first client.
[0070] Corresponding to the above method embodiment, the present application also provides an invitation device embodiment applied to the second client. Figure 7 FIG. 1 shows a schematic diagram of a structure of an invitation device applied to a second client provided by an embodiment of the present application. Figure 7 As shown, the device includes: A determination module 702 is configured to determine a second role type of a second role in response to an application invitation message from a first client, wherein the application invitation message carries the first role information; A first acquisition module 704 is configured to, when the second role type is an old user, acquire server information corresponding to the second role type and enter the target application based on the server information; The second acquisition module 706 is configured to, when the second role type is a new user, acquire the first server information in the first role information, determine the server information corresponding to the second role type according to the first server information, and enter the target application based on the server information.
[0071] The invitation device applied to the second client provided in the embodiment of the present application determines the server information of the second role according to the second role type of the second role, and enters the target application according to the server information, which can avoid user isolation caused by multiple servers and ensure that the interaction between the two roles in the target application scenario can be smoother.
[0072] The above is a schematic diagram of an invitation device for a second client according to this embodiment. It should be noted that the technical solution of the invitation device for a second client and the technical solution of the invitation method for a second client described above share the same concept. For details not described in detail in the technical solution of the invitation device for a second client, please refer to the description of the technical solution of the invitation method for a second client described above.
[0073] Figure 8 The following is a flow chart of an invitation method provided in an embodiment of the present application, which is applied to an invitation system including a first client and a second client. The method includes the following steps: Step 802: The first client generates application invitation information based on the first role information of the target application, and sends the application invitation information to the second client.
[0074] Step 804: The second client enters the target application in response to the first role information in the application invitation information.
[0075] Step 806: The first client synchronously displays a second character in the target application scenario, wherein the second character is a virtual character created by the target application when the user of the second client enters the target application.
[0076] Figure 9 The block diagram shows a structure of a computing device 900 according to an embodiment of the present application. The components of the computing device 900 include, but are not limited to, a memory 910 and a processor 920. The processor 920 is connected to the memory 910 via a bus 930, and a database 950 is used to store data.
[0077] The computing device 900 also includes an access device 940 that enables the computing device 900 to communicate via one or more networks 960. Examples of such networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 940 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a Worldwide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.
[0078] In one embodiment of the present application, the above components of the computing device 900 and Figure 9 Other components not shown in the figure may also be connected to each other, for example, via a bus. Figure 9The computing device structure block diagram shown is for illustrative purposes only and is not intended to limit the scope of the present application. Those skilled in the art may add or replace other components as needed.
[0079] Computing device 900 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, personal digital assistant, laptop computer, notebook computer, netbook computer, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or personal computer (PC). Computing device 900 can also be a mobile or stationary server.
[0080] The processor 920 is configured to execute the following computer program / instruction, which implements the steps of the above-mentioned invitation method when executed by the processor.
[0081] The above is a schematic solution of a computing device of this embodiment. It should be noted that the technical solution of the computing device and the technical solution of the invitation method described above are of the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the invitation method described above.
[0082] An embodiment of the present specification further provides a computer-readable storage medium storing a computer program / instruction. When the computer program / instruction is executed by a processor, the steps of the above-mentioned invitation method are implemented.
[0083] The above is a schematic solution of a computer-readable storage medium of this embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the invitation method described above are of the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the invitation method described above.
[0084] An embodiment of the present specification further provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned invitation method when executed by a processor.
[0085] The above is an illustrative solution of a computer program product of this embodiment. It should be noted that the technical solution of this computer program product and the technical solution of the invitation method described above are based on the same concept. For details not described in detail in the technical solution of the computer program product, please refer to the description of the technical solution of the invitation method described above.
[0086] The foregoing description describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0087] The computer instructions include computer program code, which may be in source code form, object code form, executable file, or some intermediate form. The computer-readable medium may include any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal, and software distribution medium. It should be noted that the content of the computer-readable medium may be appropriately increased or decreased based on the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media does not include electric carrier signals and telecommunication signals.
[0088] It should be noted that for the aforementioned method embodiments, for ease of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.
[0089] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.
[0090] The preferred embodiments of the present application disclosed above are intended only to help illustrate the present application. The optional embodiments do not describe all details in detail, nor do they limit the invention to the specific embodiments described. Obviously, many modifications and variations can be made based on the content of this application. This application selects and describes these embodiments in detail in order to better explain the principles and practical applications of this application, so that those skilled in the art can better understand and utilize this application. This application is limited only by the claims and their full scope and equivalents.
Claims
1. An invitation system, characterized in that: The invitation system includes a first client and a second client; The first client is configured to generate application invitation information based on the first role information of the target application, and send the application invitation information to the second client; The second client is configured to enter the target application in response to the first role information in the application invitation information; The first client is further configured to synchronously display a second character in the target application scenario, wherein the second character is a virtual character created by the target application when the user of the second client enters the target application.
2. The system according to claim 1, wherein The first client is configured to generate application invitation information based on the first role information of the target application, including: The first client is configured to obtain first role information based on a target application, perform encryption processing based on the first role information, obtain invitation encryption parameters, and generate application invitation information according to the invitation encryption parameters.
3. The system according to claim 1, wherein: Also includes: The first client is further configured to determine a second role type according to the second role, determine role favorability information according to the second role type, and control the second role to perform a target scenario task in the target application scenario according to the role favorability information.
4. The system according to claim 3, wherein: Also includes: The first client is further configured to update the character favorability information according to an interaction event between the first character and the user represented by the second character within the target application.
5. The system according to claim 1, wherein: The invitation system further includes a server; The second client is further configured to obtain first role information in response to the application invitation information, and send verification information to the server based on the first role information; The server is configured to send a verification success message to the second client if it is confirmed that the application invitation information meets the requirements according to the verification information; The second client is further configured to enter the target application upon receiving the verification pass message.
6. The system according to claim 1, wherein: Also includes: The second client is further configured to determine a second role type of the second role, and if the second role type is an old user, obtain server information corresponding to the second role type, and enter the target application based on the server information; In the case that the second role type is a new user, the first server information in the first role information is obtained, and the server information corresponding to the second role type is determined according to the first server information, and the target application is entered based on the server information.
7. The system according to claim 6, wherein: Also includes: The second client is further configured to, when the second character type is a new user, obtain the first server service time in the first server information; when the first server service time is less than or equal to the preset service time, determine that the first server information is the server information corresponding to the second character type; when the first server service time is greater than the preset service time, determine the server information corresponding to the second character type according to the preset server selection rule.
8. The system according to claim 1, wherein: Also includes: The second client is further configured to play an invitation success animation after entering the target application.
9. The system according to claim 1, wherein: Also includes: The first client is further configured to control the second role to perform a target scenario task in the target application scenario in response to a control instruction directed to the second role.
10. An invitation method, characterized in that: Applied to an invitation system, the invitation system includes a first client and a second client; The method comprises: The first client generates application invitation information based on the first role information of the target application, and sends the application invitation information to the second client; The second client enters the target application in response to the first role information in the application invitation information; The first client synchronously displays a second character in the target application scenario, wherein the second character is a virtual character created by the target application when the user of the second client enters the target application.
11. A computing device, characterized in that include: memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the method according to claim 10 are implemented.
12. A computer-readable storage medium storing a computer program / instruction, characterized in that: When the computer program / instructions are executed by a processor, the steps of the method according to claim 10 are implemented.