CN112235229A - Method for inviting user, related device, server and storage medium - Google Patents

Method for inviting user, related device, server and storage medium Download PDF

Info

Publication number
CN112235229A
CN112235229A CN201910579509.9A CN201910579509A CN112235229A CN 112235229 A CN112235229 A CN 112235229A CN 201910579509 A CN201910579509 A CN 201910579509A CN 112235229 A CN112235229 A CN 112235229A
Authority
CN
China
Prior art keywords
user
server
application
request
invitation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201910579509.9A
Other languages
Chinese (zh)
Other versions
CN112235229B (en
Inventor
胡腾
杨培艺
侯帅
赵东
李斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201910579509.9A priority Critical patent/CN112235229B/en
Publication of CN112235229A publication Critical patent/CN112235229A/en
Application granted granted Critical
Publication of CN112235229B publication Critical patent/CN112235229B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/26—Devices for calling a subscriber
    • H04M1/27—Devices whereby a plurality of signals may be stored simultaneously
    • H04M1/274—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc
    • H04M1/2745—Devices whereby a plurality of signals may be stored simultaneously with provision for storing more than one subscriber number at a time, e.g. using toothed disc using static electronic memories, e.g. chips
    • H04M1/27467—Methods of retrieving data
    • H04M1/27475—Methods of retrieving data using interactive graphical means or pictorial representations

Abstract

The embodiment of the invention discloses a method for inviting users, a related device, a server and a storage medium, wherein the method comprises the following steps: the first server receiving a first invitation request from a first application; when the first server determines that the first invitation request is a valid request based on the user information of the first user and the user information of the second user, the first server generates a second invitation request based on the first invitation request; the first server sends a second invitation request to a second server, and a second user is triggered by the second server to respond to the second invitation request based on a second application; when the first server receives the request confirmation message from the second server, the first server triggers the second user to log in the first application. By adopting the embodiment of the invention, the quick invitation to the user can be realized, the invited user can join the new application without a registration process, the invitation efficiency can be improved, and the applicability is high.

Description

Method for inviting user, related device, server and storage medium
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, a related apparatus, a server, and a storage medium for inviting a user.
Background
With the continuous development of computer technology and terminal applications, diversified terminal applications have become an essential part of users' leisure, entertainment and work. When using a certain application, a user may wish to invite his friends to experience and use the application together.
However, in the current application product, the friend invitation is mainly realized by sending an invitation link and an invitation mail. The invitation link mode mainly sends an invitation link for recommending an experience associated product to the invited friend, the invited friend needs to install and jump to another client, the operation is complicated, and the user experience is not good enough. The invitation mail mode mainly sends mails containing the information related to the experience products to the invited friends, so that real-time communication cannot be carried out, and real-time response is poor
Disclosure of Invention
Embodiments of the present invention provide a method, a related apparatus, a server, and a storage medium for inviting a user, which can skip a registration process to invite the user to join an application where an inviter is located, simplify an invitation process, improve user invitation efficiency, and have high applicability.
In a first aspect, an embodiment of the present invention provides a method for inviting a user, where the method includes:
a first server receives a first invitation request from a first application, wherein the first invitation request is a request which is triggered by a first user based on the first application and is used for inviting a second user corresponding to a second application to log in the first application, and the first invitation request comprises user information of the first user and the second user in the first application;
when the first server determines that the first invitation request is a valid request based on the user information of the first user and the user information of the second user, the first server generates a second invitation request based on the first invitation request;
the first server sends the second invitation request to a second server, and the second server triggers the second user to respond to the second invitation request based on the second application;
when the first server receives a request confirmation message from the second server, the first server triggers the second user to log in the first application, and the request confirmation message is generated by the second server when the second user responds to the second invitation request based on the second application.
With reference to the first aspect, in a possible implementation manner, the first server stores a user relationship set of the first user in the first application, where the user relationship set includes a plurality of user relationships, and a user relationship is used to represent an association relationship between the first user and a contact of the first user; the method further comprises the following steps:
the first server determines whether the contact of the first user comprises the second user;
when the contact of the first user comprises the second user, the first server determines a first user relationship between the first user and the second user from the user relationship set;
the first server determines whether the association relationship between the first user and the second user is the first user relationship according to the user information of the first user and the user information of the second user included in the first invitation request;
if the association relationship between the first user and the second user is the first user relationship, the first server determines that the first invitation request is a valid request.
With reference to the first aspect, in a possible implementation manner, the generating, by the first server, a second invitation request based on the first invitation request includes:
the first server acquires a server identifier of a second server;
the first server generates a second invitation request based on the server identifier of the second server, the user information of the first user and the user information of the second user;
wherein the server identifier of the second server is used to trigger the second server to identify the second invitation request.
With reference to the first aspect, in one possible implementation, the method further includes:
the first server generates a target account based on the user information of the second user, where the target account is used to trigger the second user to log in the first application through the target account when the first server confirms the request confirmation message of the second user.
With reference to the first aspect, in a possible implementation manner, the triggering, by the first server, the second user to log in the first application includes:
the first server confirms whether the request confirmation message includes the user information of the second user and the application identifier of the second application;
and if the request confirmation message comprises the user information of the second user and the application identifier of the second application, the first server confirms the request confirmation message to trigger the second user to log in the first application.
In a second aspect, an embodiment of the present invention provides a method for inviting a user, where the method includes:
a second server receives a second invitation request from a first server, wherein the second invitation request is used for inviting a second user corresponding to a second application to log in the first application, and the second invitation request comprises a first user and user information of the second user in the first application;
when the second server determines that the second invitation request is a valid request based on the user information of the first user and the user information of the second user, the second server generates an invitation message based on the second invitation request;
the second server sends the invitation message to the second application to trigger the second user to respond to the second invitation request;
when the second user confirms the invitation message based on the second application, the second server generates a request confirmation message based on user information of the second user and an application identifier of the second application, and sends the request confirmation message to the first server.
With reference to the second aspect, in a possible implementation manner, the second server stores a user relationship set of the second user in the second application, where the user relationship set includes a plurality of user relationships, and one user relationship is used to represent an association relationship between the second user and one contact of the second user; the method further comprises the following steps:
the second server determines whether the contact of the second user comprises the first user;
when the contact of the second user comprises the first user, the second server determines a second user relationship between the second user and the first user from the user relationship set;
the second server determines whether the association relationship between the second user and the first user is the second user relationship according to the user information of the second user and the user information of the first user included in the second invitation request;
if the association relationship between the second user and the first user is the second user relationship, the second server determines that the second invitation request is a valid request.
In a third aspect, an embodiment of the present invention provides an apparatus for inviting a user, where the apparatus includes:
a first receiving module, configured to receive a first invitation request from a first application, where the first invitation request is a request, triggered by a first user based on the first application, for inviting a second user corresponding to a second application to log in the first application, and the first invitation request includes user information of the first user and the second user in the first application;
a first generating module, configured to generate a second invitation request based on the first invitation request when the first server determines that the first invitation request is a valid request based on the user information of the first user and the user information of the second user;
a first sending module, configured to send the second invitation request to a second server, and trigger, by the second server, the second user to respond to the second invitation request based on the second application;
and a login triggering module, configured to trigger the second user to log in the first application when the first server receives a request confirmation message from the second server, where the request confirmation message is a message generated by the second server when the second user responds to the second invitation request based on the second application.
With reference to the third aspect, in a possible implementation manner, the first server stores a user relationship set of the first user in the first application, where the user relationship set includes a plurality of user relationships, and one user relationship is used to represent an association relationship between the first user and one contact of the first user; the apparatus further comprises a first determining module, the first determining module further comprising a plurality of determining units:
the first determining unit is further used for determining whether the contact of the first user comprises the second user;
a second determining unit, configured to determine, when the contact of the first user includes the second user, a first user relationship between the first user and the second user from the user relationship set;
a third determining unit, configured to determine whether an association relationship between the first user and the second user is the first user relationship according to the user information of the first user and the user information of the second user included in the first invitation request;
a fourth determining unit, configured to determine that the first invitation request is a valid request when the association relationship between the first user and the second user is the first user relationship.
With reference to the third aspect, in one possible implementation, the first generating module includes:
an obtaining unit, configured to obtain a server identifier of a second server;
a generating unit, configured to generate a second invitation request based on the server identifier of the second server, the user information of the first user, and the user information of the second user;
wherein the server identifier of the second server is used to trigger the second server to identify the second invitation request.
With reference to the third aspect, in a possible implementation manner, the apparatus further includes:
and an account generation module, configured to generate a target account based on the user information of the second user, where the target account is used to trigger the second user to log in the first application through the target account when the first server confirms the request confirmation message of the second user.
With reference to the third aspect, in a possible implementation manner, the login triggering module includes:
a fifth determining unit, configured to determine whether the request confirmation message includes the user information of the second user and the application identifier of the second application;
a sixth determining unit, configured to, when the request confirmation message includes the user information of the second user and the application identifier of the second application, confirm the request confirmation message to trigger the second user to log in the first application.
In a fourth aspect, an embodiment of the present invention provides an apparatus for inviting a user, where the apparatus includes:
a second receiving module, configured to receive a second invitation request from a first server, where the second invitation request is used to invite a second user corresponding to a second application to log in the first application, and the second invitation request includes a first user and user information of the second user in the first application;
a second generating module, configured to generate an invitation message based on the second invitation request when the second server determines that the second invitation request is a valid request based on the user information of the first user and the user information of the second user;
a second sending module, configured to send the invitation message to the second application to trigger the second user to respond to the second invitation request;
a third generating module, configured to generate a request confirmation message based on the user information of the second user and the application identifier of the second application when the second user confirms the invitation message based on the second application, and send the request confirmation message to the first server.
With reference to the fourth aspect, in a possible implementation manner, the second server stores a user relationship set of the second user in the second application, where the user relationship set includes a plurality of user relationships, and one user relationship is used to represent an association relationship between the second user and one contact of the second user; the apparatus further comprises a second determining module, the second determining module further comprising a plurality of determining units:
a seventh determining unit, configured to determine whether the contact of the second user includes the first user;
an eighth determining unit, configured to determine, when the contact of the second user includes the first user, a second user relationship between the second user and the first user from the user relationship set;
a ninth determining unit, configured to determine whether an association relationship between the second user and the first user is the second user relationship according to the user information of the second user and the user information of the first user included in the second invitation request;
a tenth determining unit, further configured to determine that the second invitation request is a valid request when the association relationship between the second user and the first user is the second user relationship.
In a fifth aspect, an embodiment of the present invention provides a server, where the server includes a processor, a memory, a transceiver, and a network interface; the processor is connected to the memory and the network interface, respectively, where the network interface is used to connect to a server, the memory is used to store a program code, and the processor and the transceiver are used to call the program code.
In a sixth aspect, an embodiment of the present invention provides a server, where the server includes a processor, a memory, a transceiver, and a network interface; the processor is connected to the memory and the network interface, respectively, where the network interface is used to connect to a server, the memory is used to store a program code, and the processor and the transceiver are used to call the program code.
In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored, and the computer program is executed by a processor to implement the method provided in the first and second aspects and/or any possible implementation manner of the first and second aspects.
In the embodiment of the invention, through the verification of the first server on the first invitation request, the validity of the first invitation request can be confirmed before the invitation request is sent out, and the first user and the second user are ensured to have a user relationship meeting the conditions for sending the invitation request. The user relationship between the first user and the second user is confirmed again by the second server for the received second invitation request, so that it can be confirmed that the second application can receive the second invitation request. In addition, the first server allocates an account number and binds the identity to the second user, so that no user registration process exists in the process of joining the second user into the first application, the efficiency of user invitation is improved, and the user experience is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention;
FIG. 2a is a schematic diagram of an architecture of a method for inviting users according to an embodiment of the present invention; .
FIG. 2b is another schematic diagram of an architecture of a method for inviting users according to an embodiment of the present invention;
FIG. 3 is a timing diagram illustrating a method for inviting users according to an embodiment of the present invention;
FIG. 4a is a schematic diagram of an invitation interface of a first application according to an embodiment of the present invention;
FIG. 4b is a schematic diagram of another invitation interface of the first application according to an embodiment of the invention;
FIG. 5 is a flowchart illustrating a process of determining that a first invite request is a valid request according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating a process of determining that a second invite request is a valid request according to an embodiment of the present invention;
FIG. 7a is a schematic diagram of an interface for displaying an invitation message according to an embodiment of the present invention;
FIG. 7b is a schematic diagram of an interface for acknowledging the invite message according to an embodiment of the present invention;
FIG. 7c is a schematic diagram of another interface for acknowledging the invite message provided by an embodiment of the present invention;
FIG. 7d is a schematic diagram of an interface for responding to a second invite request according to an embodiment of the present invention;
FIG. 8 is a block diagram of an apparatus for inviting users according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of another structure of an apparatus for inviting users according to an embodiment of the present invention;
FIG. 10 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 11 is another schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention. As shown in fig. 1, the network architecture diagram may include a server 300, a server 400, a terminal 200 and a terminal 500, where the terminal 200 corresponds to a user 100, the terminal 500 corresponds to a user 600, and both the terminal 200 and the terminal 500 may install a communication application, and each terminal may communicate with a background server corresponding to the communication application through the communication application in the terminal. The server 300 is a background server corresponding to the communication application in the terminal 200, and the server 400 is a background server corresponding to the communication application in the terminal 500. For example, when the user 100 corresponding to the terminal 200 is an inviter and the user 600 is an invitee, the user 100 may invite the user 600 to log in the communication application in the terminal 200 through the server 300 corresponding to the communication application in the terminal 200. The invitation information triggered by the user 100 based on the communication application in the terminal 200 may be sent to the server 400 by communicating between the server 300 and the server 400, and the server 400 sends the invitation information to the communication application in the terminal 500, so as to reach the purpose of sending the invitation information of the user 100 to the user 600. Conversely, when the user 600 is an inviter, the invitation information triggered by the user 600 based on the communication application in the terminal 500 may be sent to the server 400 based on the terminal 500, forwarded to the server 300 by the server 400, and sent to the communication application in the terminal 200 by the server 300 so as to convey the invitation information to the user 100. The terminal may include a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), and the like, which is not limited herein.
In order to better explain the method for inviting the user provided by the embodiment of the present invention, the method for inviting the user provided by the embodiment of the present invention is further explained with reference to fig. 2a and fig. 2 b. Fig. 2a is an architecture diagram of a method for inviting users according to an embodiment of the present invention. As shown in fig. 2a, when an inviter needs to invite a user to join an application where the inviter is located, the inviter may perform an operation of inviting an invitee based on the application where the inviter is located so as to trigger the application where the inviter is located to send an invitation request to a server corresponding to the application where the inviter is located. When the server corresponding to the application where the inviter is located receives the invitation request, the server may send the invitation request to the server corresponding to the application where the invitee is located. At this time, after receiving the invitation request, the server corresponding to the application where the invitee is located may send an invitation notification to the application where the invitee is located based on the invitation request, so as to notify the invitee that the invitee is inviting the invitee to join the application where the invitee is located at this time. Fig. 2b is another schematic architecture diagram of a method for inviting users according to an embodiment of the present invention. As shown in fig. 2b, the invitee may check the invitation message in the invitation notification based on the application where the invitee is located, and confirm the invitation message when the invitee agrees to accept the invitation to trigger the application where the invitee is located to confirm the invitation request received by the server corresponding to the application where the invitee is located. At this time, the server may send a request confirmation message to a server corresponding to the application where the inviter is located after the invitee confirms the invitation request, so that the server where the inviter is located binds the identity information of the invitee with the account number of the invitee, and thus, the invitee may be triggered to log in the application where the inviter is located, and the purpose of inviting the user to join the application where the inviter is located is achieved.
For convenience of description, the first user, the first application and the first server respectively represent an inviter, an application where the inviter is located and a server corresponding to the application where the inviter is located, and the second user, the second application and the second server respectively represent an invitee, an application where the invitee is located and a server corresponding to the application where the invitee is located, and thus, the method for inviting a user, the server and the related device provided in the embodiments of the present invention are described below. Wherein the first application and the second application are different communication applications, respectively.
Referring to fig. 3, fig. 3 is a timing diagram illustrating a method for inviting a user according to an embodiment of the present invention. The method for inviting the user provided by the embodiment of the invention can comprise the following steps S101-S111:
s101, receiving a first invitation request.
Specifically, the first invitation request is a request triggered by the first user based on the first application and used for inviting the second user corresponding to the second application to log in the first application. When the first user performs an invitation operation through an operation indicated by the first application, the first application may be triggered to send a first invitation request to the first server. It should be noted that the first application and the second application are two completely different but associated applications. When registering the first application, the first user may establish an application association relationship between the first application and the second application based on relevant information (including, but not limited to, a user name of the second application, identity information of the first user, a mobile phone number, and the like, which is not limited herein) of the first user on the second application. For example, a first user may input a user name of the first user in a second application during registration of the first application, so that the first application may establish an application association relationship between the first application and the second application based on the user name of the first user in the second application. The establishment and expression form of the application association relationship may be determined based on an association mechanism of a specific application and an actual application scenario, which is not limited herein. When the first application and the second application have an application association relationship, the first server corresponding to the first application and the second server corresponding to the second application can implement server data sharing transmission based on the application association relationship. That is to say, the second server may send the buddy list and the terminal address book of the first user in the second application to the first server, so that the first server may store the buddy list and the terminal address book of the first user in the second application, or the first application may call the buddy list and the terminal address book of the first user in the second application, which are stored in the second server, based on the first server, so as to display the buddy list and the terminal address book of the first user in the second application to the first user through the first application. Accordingly, the first user may trigger a first invitation request based on the first application to invite the first user to log in to the first application at a corresponding second user of the second applications. For convenience of description, the buddy list of the first user in the second application is referred to as the buddy list of the first user, and the buddy in the buddy list is referred to as the buddy of the first user.
In some possible embodiments, the specific operation process of the first user triggering the first invitation request based on the first application may be as shown in fig. 4 a. Fig. 4a is a schematic diagram of an invitation interface of a first application according to an embodiment of the present invention. As shown in fig. 4a, fig. 4a illustrates one way in which the first user triggers the first invite request based on the first application. In the interface diagram in fig. 4a, the first user may select "app buddy" to enter the first user's buddy list interface at an invite user interface provided by the first application. At this time, the first user may select any one friend in the friend list to invite, where the specific selection manner may be implemented in a touch manner (clicking any position in the list row where any one friend is located), a voice control manner (inputting a name of any one friend by voice, a name of a friend, etc.), and the like, which is not limited herein. For example, when a first user wants to invite a user named "xiao ming" (at this time, the user is a second user) in a buddy list to join a first application, the first user may trigger the first application to generate a first invitation request by clicking a "invite" button corresponding to the "xiao ming" in the buddy list, or invite the "xiao ming" by clicking an avatar of the "xiao ming", sliding the avatar of the "xiao ming", or the like, and a specific invitation mode may be implemented based on an invitation mode provided by the first application, which is not limited herein.
In some possible embodiments, the second user may be a terminal address book contact of the first user in the second application, where the first user logs in the first application and the second application based on the same terminal, and a specific operation process of the first user triggering the first invitation request based on the first application may be shown in fig. 4 b. Fig. 4b is a schematic diagram of another invitation interface of the first application according to the embodiment of the present invention. Fig. 4b illustrates another way in which the first user triggers the first invite request based on the first application. In the interface diagram in fig. 4b, the first user may select, on the invitation user joining interface provided by the first application, to invite the terminal address book to enter the address book list interface of the first user in the terminal where the second application is located. At this time, the first user may select any one contact person in the address list for invitation, where a specific selection manner may be implemented in a touch manner (clicking any position in a list row where any one contact person is located), a voice control manner (inputting a name of any one contact person, a contact way, and the like by voice), and the like, which is not limited herein. For example, when a first user wants to invite a user named "lie four" in the address list (at this time, the user is a second user) to join the first application, the first user may trigger the first application to generate the first invitation request by clicking a position of the "lie four" in the address list, sliding an area where the "lie four" is located, and the like, so as to invite the "lie four", and a specific invitation manner may be implemented based on an invitation manner provided by the first application, which is not limited herein. Optionally, when the first user accesses the address list in the terminal where the first application is located, the access right of the terminal address list needs to be acquired, so that the first application is used for accessing the address list of the terminal where the first application is located, and a specific right verification process is not described here.
In some possible implementations, when the first user forms the invitation operation based on the first application, the first application may be triggered to generate the first invitation request at this time. The first application can acquire the user information of the first user in the first application when the user completes the invitation operation. Meanwhile, the user information of the second user can be obtained when the second user is used as a friend of the first user in the second application. When the second user is the terminal address book contact of the first user, the first application acquires the information stored in the terminal address book of the second user and uses the information as the user information of the second user. The user information of the first user and the user information of the second user include, but are not limited to, a name, an identification number, a phone number, a birth date, a mailbox, a fingerprint, face recognition information, and other information that can distinguish user characteristics, and is not limited herein. After the first application acquires the user information of the first user and the user information of the second user, the first application generates a first invitation request based on the invitation operation of the first user and carries the user information of the first user and the user information of the second user in the first invitation request, so that the first invitation request is sent to a server corresponding to the first application, namely the first server.
S102, whether the first invitation request is a valid request is determined.
In some possible embodiments, after the first server receives the first invitation request sent by the first application, in order to ensure that the first application can successfully send the first invitation request to the second server, the first application may verify whether the first invitation request is a valid request after receiving the first invitation request. For a specific verification process, refer to fig. 5, and fig. 5 is a flowchart illustrating determining that the first invite request is a valid request according to an embodiment of the present invention. The method for determining that the first invitation request is the valid request provided by the embodiment of the invention may include the following steps S1021 to S1024:
s1021, whether the contact of the first user comprises the second user is determined.
In some possible embodiments, since the first server is a background server corresponding to the first application, the first server stores a user relationship set of the first user in the first application (or a terminal where the first user is based on the first application). The user relationship set comprises a plurality of user relationships, and each user relationship user represents an association relationship between the first user and one contact of the first user. The association relationship may be a real friend relationship (e.g., a normal friend, but not a blacklist friend, an unmasked friend, etc.) between the first user and each friend in the first application, or may be one or more association relationships used for indicating that the first user and the second user are associated with each other, such as a contact relationship having a real communication method in an address list of a terminal where the first application is located, and a specific representation form is not limited herein. Optionally, after the first server receives the first invitation request, the first server may first determine whether all users in the user relationship set of the first user (i.e., contacts of the first user) include the second user. If the contact of the first user does not include the second user, the first server may determine that the user information of the second user acquired by the first application is invalid information, that is, the second user is not a valid user, that is, the first user cannot successfully invite the second user at this time. If the contact of the first user includes the second user, the first server may perform the next verification on the first invitation request.
S1022, when the contact of the first user includes the second user, the first server determines the first user relationship between the first user and the second user from the user relationship set.
In some possible embodiments, when the contact of the first user includes the second user, the first server may determine a user relationship (for convenience, hereinafter referred to as a first user relationship) between the first user and the second user from the user relationship set, that is, the first server may determine the first user relationship between the first user and the second user stored in the first server. For example, the first user relationship in the user relationship set may be a normal friend contact (that is, the second user is not blacklisted, not masked, or the like by the first user), or the second user establishes an association with the contact address of the first user based on a correct and valid contact address, or the like, which is not limited herein.
S1023, determining whether the association relationship between the first user and the second user is the first user relationship according to the user information of the first user and the user information of the second user included in the first invitation request.
In some feasible embodiments, since the first invitation request carries the user information of the first user and the user information of the second user, at this time, the first server may determine whether the relationship between the first user and the second user is the first user relationship based on the user information of the first user and the user information of the second user. Specifically, the first server may determine, based on a basis of establishment of an association between the first user and each user in the user relationship set, judgment basis information used for establishing the user association, so as to determine corresponding judgment basis information from the user information of the first user and the user information of the second user. The first server may determine whether the association relationship between the first user and the second user is the first user relationship based on determination criterion information in the user information of the first user and determination criterion information in the user information of the second user. For example, when the user relationship set is a correct contact information association relationship for indicating each contact of the first user and each contact of the first user, the first server may obtain the contact information of the first user and the contact information of the second user from the user information of the first user and the user information of the second user, so as to determine the user relationship between the first user and the second user in the first application based on the contact information of the first user and the contact information of the second user, and further determine whether the user relationship in the first application is the first user relationship in the user relationship set.
S1024, if the association relationship between the first user and the second user is the first user relationship, determining that the first invitation request is an effective request
In some possible embodiments, when the association relationship between the first user and the second user is not the first user relationship, the first server may determine that the first invitation request is an invalid request, and the first server may not send the first invitation request to any server. If the association between the first user and the second user is the first user relationship, the first server may determine that the first invite request is a valid request. For example, if the user relationship in the user relationship set is established based on identity information (identification number, name, etc.), at this time, the first server is correct based on the identity information in the user information of the first user and the user information of the second user, and the first server may determine that the association relationship between the first user and the second user is the first user relationship. The specific determination manner may be determined according to the set of user relationships actually stored in the first server, which is not limited herein. In this case, the second server may determine that the first invite request is a valid request when the association between the first user and the second user is the first user relationship.
In the embodiment of the invention, whether the first invitation request is a valid request is determined by the first server checking the user relationship between the first user and the second user in the first invitation request sent by the first application, so as to determine whether to send the first invitation request to the second server. Through the operation, the request which cannot be used for inviting the second user to log in the first application can be filtered out in advance based on the first server, so that the long-time waiting caused by triggering an invalid invitation request by the first user is reduced, and the user experience can be further improved.
S103, generating a second invitation request.
In some possible embodiments, since the invitation object of the first invitation request is a second user, and the second user is a friend of the first user in the second application or a terminal address book contact, after determining that the first invitation request is a valid request, the first server may send the first invitation request to a second server corresponding to the second application based on an application association relationship between the first application and the second application. In order to ensure that the first invitation request can be recognized and received by the second server, the first server needs to perform information processing on the first invitation request so as to accurately send the invitation request of the first user inviting the second user to the second server. Specifically, the first server re-extracts the user information of the first user and the user information of the second user, which are carried in the first invitation request, and simultaneously acquires the server identifier of the second server, so that a second invitation request can be generated based on the user information of the first user, the user information of the second user, and the server identifier of the second server. Since the second invite request carries the server identifier of the second server, when the first server sends the second invite request to the second server, the second server can identify and receive the second invite request. The second server identifier is only used for enabling the second server to identify and receive the second invitation request, and may be a message that satisfies a communication protocol for communication between the first server and the second server, or may be an identifier for identifying a source and a destination of the second invitation request, and the specific representation form is not limited herein.
And S104, receiving a second invitation request.
In some possible embodiments, after the first server sends the second invitation request to the second server, the second server may identify whether the second invitation request includes a server identifier of the second server. If the second invitation request includes the server identifier of the second server, the second server may receive the second invitation request. Optionally, the second server may further determine whether the second invitation request has data missing during the request sending process, or whether the second invitation request has a potential safety hazard, and the like, and the specific determination manner may be determined based on an actual application scenario, which is not limited herein.
S105, determining whether the second invite request is a valid request.
In some possible embodiments, after the second server receives the second invitation request sent by the first server, the second server may verify whether the second invitation request is a valid request after receiving the first invitation request. For a specific verification process, refer to fig. 6, and fig. 6 is a flowchart illustrating determining that the second invite request is a valid request according to an embodiment of the present invention. The method for determining that the second invite request is an effective request according to the embodiment of the present invention may include the following steps S1051 to S1054:
s1051, determining whether the contact of the second user contains the first user.
In some possible embodiments, since the second server is a background server corresponding to the second application, the second server stores a user relationship set of the second user in the second application (or the second user is based on a terminal where the second application is located). The user relationship set comprises a plurality of user relationships, and each user relationship user represents the association relationship between the second user and one contact of the second user. The association relationship may be a real friend relationship (e.g., a normal friend, but not a blacklist friend, an unmasked friend, etc.) between the second user and each friend in the second application, or may be one or more association relationships indicating that the second user and the first user are associated with each other, such as a contact relationship having a real communication manner in an address book of a terminal where the second application is located, and a specific representation form is not limited herein. Optionally, after the second server receives the second invitation request, the user information of the first user and the user information of the second user included in the second invitation request may be acquired. The second server may determine whether all users in the user relationship set of the second user (i.e., contacts of the second user) include the first user. If the contact of the second user does not include the first user, the second server does not perform any processing on the second invitation request. If the contact of the second user includes the first user, the second server may perform the next verification on the second invitation request.
S1052, when the contact of the second user includes the first user, the second server determines the second user relationship between the second user and the first user from the user relationship set.
In some possible embodiments, when the contact of the second user includes the first user, the second server may determine the user relationship between the second user and the first user (for convenience of description, hereinafter referred to as a second user relationship) from the user relationship set, that is, the second server may determine the second user relationship between the second user and the first user stored in the second server. For example, the second user relationship in the user relationship set may be a normal friend contact (that is, the first user is not blacklisted, not masked, or the like by the second user), or the first user establishes an association with the contact address of the second user based on a correct and valid contact address, or the like, which is not limited herein.
And S1053, determining whether the association relationship between the second user and the first user is the second user relationship according to the user information of the second user and the user information of the first user included in the second invitation request.
In some feasible embodiments, since the second invitation request carries the user information of the first user and the user information of the second user, at this time, the second server may determine whether the relationship between the first user and the second user is the second user relationship based on the user information of the second user and the user information of the first user. Specifically, the second server may determine, based on a basis of establishment of an association between the second user and each user in the user relationship set, judgment basis information used for establishing the user association, so as to determine corresponding judgment basis information from the user information of the first user and the user information of the second user. The second server may determine whether the association relationship between the second user and the first user is the second user relationship based on the determination criterion information in the user information of the first user and the determination criterion information in the user information of the second user. For a specific implementation, reference may be made to the implementation shown in step S1023 in fig. 5, which is not described herein again.
S1054, if the association relationship between the second user and the first user is the second user relationship, determining that the second invitation request is an effective request
In some possible embodiments, when the association relationship between the second user and the first user is not the second user relationship, the second server may determine that the second invite request is an invalid request, and the first server may not send the second invite request to the second application. If the association between the second user and the first user is the second user relationship, the second server may determine that the second invite request is a valid request. For a specific determination manner, reference may be made to the implementation manner shown in step S1024 in fig. 5, which is not described herein again.
In the embodiment of the invention, the second server checks whether the user relationship between the first user and the second user in the second invitation request meets the user relationship pre-stored by the second server, so as to determine whether the second invitation request is a valid request. Therefore, whether the invitation message is sent to the second user through the second application or not can be determined based on the second server, the user experience of the user is further improved, and the user invitation efficiency is improved.
And S106, generating an invitation message.
In some possible embodiments, after determining that the second invitation request is a valid request, the second server may generate an invitation message according to the second invitation request. Wherein the invitation message is used for prompting the second user to complete the confirmation operation of the invitation message. It should be particularly noted that, the specific process of the second server generating the invitation message based on the second invitation request may be determined according to the operation mode of the actual server and the actual requirement of the second application on the output content of the application, and is not limited herein.
S107, sending an invitation message.
In some possible embodiments, after generating the invitation message, the second server may send the invitation message to the second application based on an application association relationship between the first application and the second application. And sending the invitation message to a designated position of the second application based on the user information of the second user in the second invitation request and the message push rule of the second application, so that the invitation message is displayed to the second user based on the second application, and the invitation message is prevented from being sent to other users in the second application. For example, the second application may send the invitation message to a "service notification" message of the second application, and remind the second user to view the invitation message based on the second application in the form of a service notification. The designated location includes, but is not limited to, any push manner (system notification, message popup, etc.) of the display message in the second application, which is not limited herein.
And S108, triggering the second user to respond to the second invitation request.
Specifically, after the second server sends the invitation message to the second application, the user may be prompted to view and confirm the invitation message to complete a response to a second invitation request sent by the first server to the second server. A specific manner of the second user confirming the invitation message may be described in step S109, which is not described herein.
S109, confirming the invitation message.
In some possible embodiments, after the second server sends the invitation message to the second application, the user needs to be reminded to view the invitation message. For example, when the second server reminds the second user to view the invitation message based on the second application in the form of a service notification, refer to fig. 7a, where fig. 7a is an interface diagram for displaying the invitation message according to an embodiment of the present invention. In fig. 7a, the invitation message is displayed on the application interface of the second application in the form of "service notification", and is notified to the second user in a manner of new message notification that the second user receives a new message, so as to remind the second user to click "service notification" to view the invitation message in the service notification. For a specific reminding manner of the other invitation messages, reference may be made to the description in step S107, and details are not described herein again.
In some possible embodiments, the second user may confirm the invitation message by clicking and viewing the invitation message. For example, please refer to fig. 7b, fig. 7b is a schematic diagram of an interface for confirming an invitation message according to an embodiment of the present invention. As shown in fig. 7b, the second user can see the invitation content of the invitation message after clicking the "service notification". Based on the content of the invite message, the second user can know that the source of the invite message is "certain" in the first application, and the sending time (or receiving time) of the invite message. The second user may click on "details" to view more information of the invitation message, such as identity information of "a certain" of the first user, application profile of the first application, and reward information for joining the first application, etc., without limitation. And if the second user clicks the invitation message, the second user confirms the invitation message and selects to join the first application. For another example, please refer to fig. 7c, fig. 7c is a schematic diagram of another interface for confirming the invitation message according to the embodiment of the present invention. As shown in fig. 7c, the second user may not only know that the source of the invitation message is "some" in the first application and the sending time (or receiving time) of the invitation message, but also confirm the invitation message and choose to join the first application by scanning the two-dimensional code in the invitation message.
In some possible embodiments, in order to further ensure that the invitation message is successfully sent to the second application, and that the invitation message is viewed or confirmed by the second user but not by other users, the second application may further validate the operation instruction for confirming the invitation message after the user confirms the invitation message. Specifically, after receiving an operation instruction for confirming the invitation message by the user, the second application may verify whether the operation instruction includes an application identifier of the second application and user information of the second user. When the operation command includes the application identifier of the second application, the second application confirms that the invitation message is successfully sent to the second application, and the invitation message is confirmed (operation for confirming the invitation message is completed) by the user based on the second application. When the operation command includes the user information of the second user, the second application may confirm that the invitation message is confirmed by the second user and not that the other users complete the confirmation. For example, when the invitation message is displayed on the message card shown in the display interface shown in fig. 7b, the message card may acquire the user information and the second application identifier of the user when the user clicks the invitation message, so as to determine that the invitation message is not forwarded to another user by the second user through the second application. Thereby avoiding the situation that the first inviting user invites other users except the second user because the second user forwards the inviting message to other users. For another example, when the invitation message is displayed on a message card shown in the display interface shown in fig. 7c, if the second user scans the two-dimensional code in the invitation message through the second application to complete the confirmation operation, at this time, the message card may obtain the user information of the second user and the application identifier of the second application, so as to determine that the invitation message is the invitation message confirmation operation completed by the second user based on the second application. It should be particularly noted that the confirmation operation of the invitation message may also be that the second user instructs to complete based on the operation prompted by the invitation message after clicking the invitation message, as shown in fig. 7d, where fig. 7d is an interface diagram for responding to the second invitation request provided by the embodiment of the present invention. When the second user clicks "download first application", it means that the second user completes the invitation message confirmation operation, that is, the second user has responded to the second invitation request received by the second server. The "downloading the first application" may also be replaced by other operation prompt modules, such as a verification information filling prompt module, a personal identity information filling prompt module, and the like, and the specific implementation manner may be determined based on an actual application scenario, which is not limited herein.
S110, generating and sending a request confirmation message.
In some possible embodiments, after the second user completes the confirmation operation of the invitation message based on the second application, the second application confirms that the second user completes the response to the second invitation request sent by the first application. In this case, the second application may generate a request acknowledgement message and forward the request acknowledgement message to the first server through the second server. Alternatively, the second application may notify the second server that the second user has responded to the second invitation request to trigger the second server to generate a request confirmation message and send the request confirmation message to the first server. The request confirmation message may include the user information of the second user and the application identifier of the second application, or may include an invitation confirmation identifier generated by the second application when the second user completes an operation of confirming the invitation message, so as to prompt the second server and/or the second server that the second user has responded to the second invitation request.
And S111, triggering a second user to log in the first application.
In some possible embodiments, when the first server receives the request confirmation message sent by the second server, the first server may perform message verification on the request confirmation message. That is, the first server may further verify whether the request confirmation message includes the user information of the second user and the application identifier of the second application, so as to determine that the second invitation request sent by the first server is responded by the second user based on the second application. In addition, it may also be verified whether the request confirmation message includes an invitation confirmation identifier generated by the second application when the second user completes the confirmation of the invitation message operation, so as to confirm whether the second application completes all confirmation operations in the invitation message.
In some feasible embodiments, after receiving the request confirmation message sent by the second server, the first server may generate a target account for the second user to log in the first application according to the user information of the second user carried in the request confirmation message, and bind the target account and the user information of the second user, so as to ensure that the target account can only be logged in by the second user. After the first server binds the user information of the second user with the target account, the first server may send an invitation success notification to the second server so that the second user logs in the first application based on the target account to invite the second user to join the first application. Or, after binding the user information of the second user with the target account, the first server may perform real-time monitoring on the target account, and allow the second user to enter the first application when it is monitored that the second user logs in the first application based on the target account. Specifically, in order to quickly trigger the second user to log in the first application after the first server receives the request confirmation message sent by the second server, the first server may generate a target account for the second user based on the user information of the second user in the received first invitation request at any time between the time when the first server receives the first invitation request and the time when the second server sends the request confirmation message to the first server, so as to reduce the waiting time of the second application after responding to the second invitation request due to the uncertain factors caused by network transmission, and the applicability is high.
In the embodiment of the invention, through the verification of the first server on the first invitation request, the validity of the first invitation request can be confirmed before the invitation request is sent out, and the first user and the second user are ensured to have a user relationship meeting the conditions for sending the invitation request. The user relationship between the first user and the second user is confirmed again by the second server for the received second invitation request, so that it can be confirmed that the second application can receive the second invitation request. In addition, an account can be allocated for the second user and the identity can be bound for the second user through the first server based on the user information of the second user, so that the second user only needs to finish responding to the second invitation request by confirming the invitation request, a complicated registration process is avoided, the user invitation efficiency is improved, and the user experience is improved.
Referring to fig. 8, fig. 8 is a schematic structural diagram of an inviting user device according to an embodiment of the present invention. The user invitation device 1 provided by the embodiment of the invention comprises:
a first receiving module 11, configured to receive a first invitation request from a first application, where the first invitation request is a request that is triggered by a first user based on the first application and is used for inviting a second user corresponding to a second application to log in the first application, and the first invitation request includes user information of the first user and the second user in the first application;
a first generating module 12, configured to generate a second invitation request based on the first invitation request when the first server determines that the first invitation request is a valid request based on the user information of the first user and the user information of the second user;
a first sending module 14, configured to send the second invitation request to a second server, and trigger, by the second server, the second user to respond to the second invitation request based on the second application;
a login triggering module 15, configured to trigger the second user to log in the first application when the first server receives a request confirmation message from the second server, where the request confirmation message is a message generated by the second server when the second user responds to the second invitation request based on the second application.
In some possible embodiments, the first server stores a user relationship set of the first user in the first application, where the user relationship set includes a plurality of user relationships, and a user relationship is used to represent an association relationship between the first user and a contact of the first user; the user invitation device 1 further comprises a first determination module, and the first determination module further comprises a plurality of determination units:
a first determining unit 131, configured to determine whether the contact of the first user includes the second user;
a second determining unit 132, configured to determine, when the contact of the first user includes the second user, a first user relationship between the first user and the second user from the user relationship set;
a third determining unit 133, configured to determine whether an association relationship between the first user and the second user is the first user relationship according to the user information of the first user and the user information of the second user included in the first invitation request;
the fourth determining unit 134 is further configured to determine that the first invitation request is a valid request when the association relationship between the first user and the second user is the first user relationship.
In some possible embodiments, the first generating module 12 includes:
an obtaining unit 121, configured to obtain a server identifier of the second server;
a generating unit 122, configured to generate a second invitation request based on the server identifier of the second server, the user information of the first user, and the user information of the second user;
wherein the server identifier of the second server is used to trigger the second server to identify the second invitation request.
In some possible embodiments, the user invitation device 1 further includes:
the account generation module 16 is further configured to generate a target account based on the user information of the second user, where the target account is used to trigger the second user to log in the first application through the target account when the first server confirms the request confirmation message of the second user.
In some possible embodiments, the login triggering module 15 includes:
a fifth determining unit 151, configured to determine whether the request confirmation message includes the user information of the second user and the application identifier of the second application;
a sixth determining unit 152, configured to, when the request confirmation message includes the user information of the second user and the application identifier of the second application, confirm the request confirmation message to trigger the second user to log in the first application.
Referring to fig. 9, fig. 9 is a schematic structural diagram of an inviting user device according to an embodiment of the present invention. The user invitation device 2 includes:
a second receiving module 21, configured to receive a second invitation request from a first server, where the second invitation request is used to invite a second user corresponding to a second application to log in a first application, and the second invitation request includes a first user and user information of the second user in the first application;
a second generating module 23, configured to generate an invitation message based on the second invitation request when the second server determines that the second invitation request is a valid request based on the user information of the first user and the user information of the second user;
a second sending module 24, configured to send the invitation message to the second application to trigger the second user to respond to the second invitation request;
a third generating module 25, configured to, when the second user confirms the invitation message based on the second application, generate a request confirmation message based on user information of the second user and an application identifier of the second application, and send the request confirmation message to the first server.
In some possible embodiments, the second server stores a user relationship set of the second user in the second application, where the user relationship set includes a plurality of user relationships, and a user relationship is used to represent an association relationship between the second user and a contact of the second user; the user invitation device 2 further includes a second determination module 22, and the second determination module 22 further includes a plurality of determination units:
a seventh determining unit 221, configured to determine whether the contact of the second user includes the first user;
an eighth determining unit 222, configured to determine, when the contact of the second user includes the first user, a second user relationship between the second user and the first user from the user relationship set;
a ninth determining unit 223, configured to determine whether the association relationship between the second user and the first user is the second user relationship according to the user information of the second user and the user information of the first user included in the second invitation request;
the tenth determining unit 224 is further configured to determine that the second invitation request is a valid request when the association relationship between the second user and the first user is the second user relationship.
In a specific implementation, the device for inviting the user may execute, through each built-in module and/or unit thereof, the implementation manner provided in each step in fig. 1 to fig. 7d, which is not described herein again.
In the embodiment of the invention, through the verification of the first server on the first invitation request, the validity of the first invitation request can be confirmed before the invitation request is sent out, and the first user and the second user are ensured to have a user relationship meeting the conditions for sending the invitation request. The user relationship between the first user and the second user is confirmed again by the second server for the received second invitation request, so that it can be confirmed that the second application can receive the second invitation request. In addition, the first server allocates an account number for the second user and binds the identity, so that a user registration process does not exist when the user invitation between the applications is completed, the efficiency of the user invitation is improved, and the user experience is improved.
Referring to fig. 10, fig. 10 is a schematic structural diagram of a server according to an embodiment of the present invention, and as shown in fig. 10, a server 1000 in this embodiment may include: the processor 1001, the transceiver 1002, the network interface 1005 and the memory 1006, and the server 1000 may further include: a user interface 1004, and at least one communication bus 1003. The communication bus 1003 is used to implement connection communication among these components. The user interface 1004 may include a Display (Display) and a Keyboard (Keyboard), and the optional user interface 1004 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1006 may be a high-speed RAM memory or a non-volatile memory (e.g., at least one disk memory). The memory 1006 may optionally be at least one memory device located remotely from the processor 1001 and the transceiver 1002. As shown in fig. 10, the memory 1004, which is a type of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.
In the server 1000 shown in fig. 10, a network interface 1005 may provide a network communication function to enable communication between the servers; and the user interface 1004 is primarily an interface for providing input to a user; and the processor 1001 and transceiver 1002 may be configured to invoke a device control application stored in the memory 1006 to perform the following operations:
the transceiver 1002 is configured to receive a first invitation request from a first application, where the first invitation request is a request, triggered by the first application, of a first user to invite a second user corresponding to a second application to log in the first application, and the first invitation request includes user information of the first user and the second user in the first application;
the processor 1001 is configured to generate a second invitation request based on the first invitation request when the first server determines that the first invitation request is a valid request based on the user information of the first user and the user information of the second user;
the transceiver 1002 is configured to send the second invitation request to a second server, and trigger the second user to respond to the second invitation request based on the second application through the second server;
the processor 1001 is configured to trigger the second user to log in the first application when the first server receives a request confirmation message from the second server, where the request confirmation message is a message generated by the second server when the second user responds to the second invitation request based on the second application.
In some possible embodiments, the first server stores a user relationship set of the first user in the first application, where the user relationship set includes a plurality of user relationships, and a user relationship is used to represent an association relationship between the first user and a contact of the first user; the processor 1001 is further configured to:
determining whether the contact of the first user comprises the second user;
when the contact of the first user comprises the second user, determining a first user relationship between the first user and the second user from the user relationship set;
determining whether the association relationship between the first user and the second user is the first user relationship according to the user information of the first user and the user information of the second user included in the first invitation request;
and when the association relationship between the first user and the second user is the first user relationship, determining that the first invitation request is a valid request.
In some possible embodiments, the processor 1001 is configured to:
acquiring a server identifier of a second server;
generating a second invitation request based on the server identifier of the second server, the user information of the first user and the user information of the second user;
wherein the server identifier of the second server is used to trigger the second server to identify the second invitation request.
In some possible embodiments, the processor 1001 is further configured to:
and generating a target account based on the user information of the second user, wherein the target account is used for triggering the second user to log in the first application through the target account when the first server confirms the request confirmation message of the second user.
In some possible embodiments, the processor 1001 is configured to:
confirming whether the request confirmation message comprises the user information of the second user and the application identifier of the second application;
and when the request confirmation message comprises the user information of the second user and the application identifier of the second application, confirming the request confirmation message to trigger the second user to log in the first application.
It should be understood that, in some possible embodiments, the processor 1001 may be a Central Processing Unit (CPU), and the processor 1001 may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and so on. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 1006 may include both read-only memory and random access memory, and provides instructions and data to the processor. A portion of the memory 1006 may also include non-volatile random access memory.
In a specific implementation, the server 1001 may execute, through each built-in functional module, the implementation manners provided in the steps in fig. 1 to fig. 7d, which may be specifically referred to the implementation manners provided in the steps, and are not described herein again.
Referring to fig. 11, fig. 11 is another schematic structural diagram of a server according to an embodiment of the present invention, and as shown in fig. 11, a server 1100 in this embodiment may include: a processor 1101, a transceiver 1102, a network interface 1105, and a memory 1106. In addition, the server 1100 may further include: a user interface 1104, and at least one communication bus 1103. The communication bus 1103 is used to realize connection communication among these components. The user interface 1104 may include a Display (Display) and a Keyboard (Keyboard), and the optional user interface 1104 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1006 may be a high-speed RAM memory or a non-volatile memory (e.g., at least one disk memory). The memory 1106 may optionally be at least one storage device located remotely from the processor 1101 and the transceiver 1102. As shown in fig. 11, the memory 1104, which is a type of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.
In the server 1100 shown in FIG. 11, the network interface 1105 may provide network communication functions for communication between servers; while user interface 1104 is primarily an interface for providing input to a user; and the processor 1101 and transceiver 1102 may be configured to invoke a device control application stored in the memory 1106 to perform the following operations:
the transceiver 1102 is configured to receive a second invitation request from a first server, where the second invitation request is used to invite a second user corresponding to a second application to log in a first application, and the second invitation request includes user information of the first user and the second user in the first application;
the processor 1101 is configured to generate an invitation message based on the second invitation request when the second server determines that the second invitation request is a valid request based on the user information of the first user and the user information of the second user;
the transceiver 1102 is configured to send the invite message to the second application to trigger the second user to respond to the second invite request;
the processor 1101 is configured to, when the second user confirms the invitation message based on the second application, generate a request confirmation message based on user information of the second user and an application identifier of the second application, and send the request confirmation message to the first server.
In some possible embodiments, the second server stores a user relationship set of the second user in the second application, where the user relationship set includes a plurality of user relationships, and a user relationship is used to represent an association relationship between the second user and a contact of the second user; the processor 1101 is further configured to:
determining whether the contact of the second user comprises the first user;
when the contact of the second user comprises the first user, determining a second user relationship between the second user and the first user from the user relationship set;
determining whether the association relationship between the second user and the first user is the second user relationship according to the user information of the second user and the user information of the first user included in the second invitation request;
and when the association relationship between the second user and the first user is the second user relationship, determining that the second invitation request is a valid request.
It should be appreciated that in some possible implementations, the processor 1101 may be a Central Processing Unit (CPU), and the processor 1101 may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 1106 may include both read-only memory and random access memory and provides instructions and data to the processor. A portion of the memory 1106 may also include non-volatile random access memory.
In a specific implementation, the server 1100 may execute the implementation manners provided in the steps in fig. 1 to fig. 7d through the built-in functional modules, which may specifically refer to the implementation manners provided in the steps, and are not described herein again.
In the embodiment of the invention, through the verification of the first server on the first invitation request, the validity of the first invitation request can be confirmed before the invitation request is sent out, and the first user and the second user are ensured to have a user relationship meeting the conditions for sending the invitation request. The user relationship between the first user and the second user is confirmed again by the second server for the received second invitation request, so that it can be confirmed that the second application can receive the second invitation request. In addition, the first server allocates an account number and binds the identity to the second user, so that no user registration process exists in the process of joining the second user into the first application, the efficiency of user invitation is improved, and the user experience is improved.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and is executed by a processor to implement the method provided in each step in fig. 1 to 7d, which may specifically refer to the implementation manner provided in each step, and is not described herein again.
The computer readable storage medium may be the task processing device provided in any of the foregoing embodiments or an internal storage unit of the terminal, such as a hard disk or a memory of an electronic device. The computer readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash card (flash card), and the like, which are provided on the electronic device. The computer readable storage medium may further include a magnetic disk, an optical disk, a read-only memory (ROM), a Random Access Memory (RAM), and the like. Further, the computer readable storage medium may also include both an internal storage unit and an external storage device of the electronic device. The computer-readable storage medium is used for storing the computer program and other programs and data required by the electronic device. The computer readable storage medium may also be used to temporarily store data that has been output or is to be output.
The terms "first", "second", and the like in the claims, in the description and in the drawings of the present invention are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments. The term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.

Claims (10)

1. A method of inviting users, the method comprising:
the method includes that a first server receives a first invitation request from a first application, the first invitation request is a request, triggered by the first application, of a first user for inviting a second user corresponding to a second application to log in the first application, and the first invitation request comprises user information of the first user and the second user in the first application;
when the first server determines that the first invitation request is a valid request based on the user information of the first user and the user information of the second user, the first server generates a second invitation request based on the first invitation request;
the first server sends the second invitation request to a second server, and the second server triggers the second user to respond to the second invitation request based on the second application;
when the first server receives a request confirmation message from the second server, the first server triggers the second user to log in the first application, and the request confirmation message is generated by the second server when the second user responds to the second invitation request based on the second application.
2. The method according to claim 1, wherein the first server stores a user relationship set of the first user in the first application, the user relationship set includes a plurality of user relationships, one user relationship is used to represent an association relationship between the first user and one contact of the first user; the method further comprises the following steps:
the first server determining whether the second user is included in the first user's contacts;
when the contact of the first user comprises the second user, the first server determines a first user relationship between the first user and the second user from the user relationship set;
the first server determines whether the association relationship between the first user and the second user is the first user relationship according to the user information of the first user and the user information of the second user included in the first invitation request;
and if the association relationship between the first user and the second user is the first user relationship, the first server determines that the first invitation request is a valid request.
3. The method of claim 1 or 2, wherein generating, by the first server, a second invitation request based on the first invitation request comprises:
the first server acquires a server identifier of a second server;
the first server generates a second invitation request based on the server identification of the second server, the user information of the first user and the user information of the second user;
wherein the server identification of the second server is used to trigger the second server to recognize the second invitation request.
4. The method according to any one of claims 1 to 3, further comprising:
the first server generates a target account based on the user information of the second user, and the target account is used for triggering the second user to log in the first application through the target account when the first server confirms the request confirmation message of the second user.
5. The method of any of claims 1 to 4, wherein the first server triggering the second user to log into the first application comprises:
the first server confirms whether the request confirmation message comprises the user information of the second user and the application identification of the second application;
and if the request confirmation message comprises the user information of the second user and the application identifier of the second application, the first server confirms the request confirmation message to trigger the second user to log in the first application.
6. A method of inviting users, the method comprising:
the second server receives a second invitation request from the first server, wherein the second invitation request is used for inviting a second user corresponding to a second application to log in the first application, and the second invitation request comprises a first user and user information of the second user in the first application;
when the second server determines that the second invitation request is a valid request based on the user information of the first user and the user information of the second user, the second server generates an invitation message based on the second invitation request;
the second server sends the invitation message to the second application to trigger the second user to respond to the second invitation request;
and when the second user confirms the invitation message based on the second application, the second server generates a request confirmation message based on the user information of the second user and the application identifier of the second application, and sends the request confirmation message to the first server.
7. The method according to claim 6, wherein the second server stores a user relationship set of the second user in the second application, the user relationship set includes a plurality of user relationships, one user relationship is used to represent an association relationship between the second user and one contact of the second user; the method further comprises the following steps:
the second server determining whether the first user is included in the second user's contacts;
when the contact of the second user comprises the first user, the second server determines a second user relationship between the second user and the first user from the user relationship set;
the second server determines whether the association relationship between the second user and the first user is the second user relationship according to the user information of the second user and the user information of the first user included in the second invitation request;
and if the association relationship between the second user and the first user is the second user relationship, the second server determines that the second invitation request is an effective request.
8. A server, comprising: a processor, a memory, a transceiver, and a network interface;
the processor is connected to the memory and the network interface, respectively, wherein the network interface is used for connecting to a server, the memory is used for storing program codes, and the processor and the transceiver are used for calling the program codes to execute the method according to claims 1 to 5.
9. A server, comprising: a processor, a memory, a transceiver, and a network interface;
the processor is connected to the memory and the network interface, respectively, wherein the network interface is used for connecting to a server, the memory is used for storing program codes, and the processor and the transceiver are used for calling the program codes to execute the method according to claims 6 to 7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which is executed by a processor to implement the method of any one of claims 1 to 7.
CN201910579509.9A 2019-06-28 2019-06-28 Method for inviting user, related device, server and storage medium Active CN112235229B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910579509.9A CN112235229B (en) 2019-06-28 2019-06-28 Method for inviting user, related device, server and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910579509.9A CN112235229B (en) 2019-06-28 2019-06-28 Method for inviting user, related device, server and storage medium

Publications (2)

Publication Number Publication Date
CN112235229A true CN112235229A (en) 2021-01-15
CN112235229B CN112235229B (en) 2022-09-27

Family

ID=74110908

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910579509.9A Active CN112235229B (en) 2019-06-28 2019-06-28 Method for inviting user, related device, server and storage medium

Country Status (1)

Country Link
CN (1) CN112235229B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080243853A1 (en) * 2007-03-30 2008-10-02 Verizon Services Corp. Method and system for notifying an invitee user when an inviting user accesses a social networking application
CN102334316A (en) * 2009-02-27 2012-01-25 索尼爱立信移动通讯有限公司 Methods and arrangements for creating a virtual relationship between communication devices for publishing personal data
CN106101194A (en) * 2016-05-31 2016-11-09 腾讯科技（深圳）有限公司 A kind of method adding group and server
CN106075904A (en) * 2016-06-07 2016-11-09 腾讯科技（深圳）有限公司 The method and device of cross-platform game fighting, terminal, system
CN107485859A (en) * 2017-09-21 2017-12-19 广州四三九九信息科技有限公司 Game invitation method, device and electronic equipment
CN108525293A (en) * 2018-02-08 2018-09-14 腾讯科技（深圳）有限公司 A kind of information processing method, device and storage medium
CN108965107A (en) * 2018-06-22 2018-12-07 腾讯科技（深圳）有限公司 Good friend's adding method, device, system, client and server
WO2019084875A1 (en) * 2017-11-02 2019-05-09 腾讯科技（深圳）有限公司 Information processing method and apparatus, server, and storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080243853A1 (en) * 2007-03-30 2008-10-02 Verizon Services Corp. Method and system for notifying an invitee user when an inviting user accesses a social networking application
CN102334316A (en) * 2009-02-27 2012-01-25 索尼爱立信移动通讯有限公司 Methods and arrangements for creating a virtual relationship between communication devices for publishing personal data
CN106101194A (en) * 2016-05-31 2016-11-09 腾讯科技（深圳）有限公司 A kind of method adding group and server
CN106075904A (en) * 2016-06-07 2016-11-09 腾讯科技（深圳）有限公司 The method and device of cross-platform game fighting, terminal, system
CN107485859A (en) * 2017-09-21 2017-12-19 广州四三九九信息科技有限公司 Game invitation method, device and electronic equipment
WO2019084875A1 (en) * 2017-11-02 2019-05-09 腾讯科技（深圳）有限公司 Information processing method and apparatus, server, and storage medium
CN108525293A (en) * 2018-02-08 2018-09-14 腾讯科技（深圳）有限公司 A kind of information processing method, device and storage medium
CN108965107A (en) * 2018-06-22 2018-12-07 腾讯科技（深圳）有限公司 Good friend's adding method, device, system, client and server

Also Published As

Publication number Publication date
CN112235229B (en) 2022-09-27

Similar Documents

Publication Publication Date Title
CN105530175B (en) Message processing method, device and system
US10063547B2 (en) Authorization authentication method and apparatus
CN109587044B (en) Group creation and message interaction method and device
JP5759564B2 (en) Coupon notification and provision system using SNS information and method thereof
CN105407086B (en) Temporary authorization method, client and server
CN107347054B (en) Identity verification method and device
US11457045B2 (en) Methods and user equipment for exchanging service capabilities
WO2015067017A1 (en) Method,system and server system of payment based on a conversation group
CN105704002A (en) Instant messaging method and instant messaging device
CN104935500B (en) Friend recommendation method and device based on network call
CN101217506B (en) Message processing method, system and client
CN112260929B (en) Content sharing method and device, terminal and storage medium
CN114726947B (en) Message display method, device, user terminal and readable storage medium
CN103916400A (en) User account management method and system
CN105404800B (en) Account information authorization method, terminal and server
CN106357684B (en) Game application program login method and device
JP6843106B2 (en) Communication equipment, communication methods and communication systems
CN108288152B (en) Interaction method, terminal and storage medium for sharing information
US10778434B2 (en) Smart login method using messenger service and apparatus thereof
US20150085855A1 (en) Method and system for managing the communication between two users
CN105634882B (en) Network access equipment sharing method, device and system
CN113518028A (en) Group chat method and device based on distinguishing group owner and group member
CN112235229B (en) Method for inviting user, related device, server and storage medium
CN103532832A (en) Method for transmitting telephone number
CN111193655B (en) Information processing method, information processing apparatus, server, and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40037815

Country of ref document: HK

SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant