CN112073295B

CN112073295B - Method and system for providing group service for third-party application

Info

Publication number: CN112073295B
Application number: CN202010841796.9A
Authority: CN
Inventors: 不公告发明人
Original assignee: Individual
Current assignee: Individual
Priority date: 2020-08-20
Filing date: 2020-08-20
Publication date: 2022-06-24
Anticipated expiration: 2040-08-20
Also published as: CN112073295A

Abstract

The invention discloses a method, a client, a server and a system for providing group service for third-party application. The method comprises the following steps: creating a group and setting a third party application identifier to which the group belongs, wherein the third party application identifier indicates a third party application to which the group belongs; determining whether the user is a user on a third-party application server according to a social user account of the user, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier; and if so, adding the user into the group according to the social user account. The method can ensure that the user joining the group is the user of the third-party application to which the group belongs, and can further ensure that the users in the group mutually identify the user identity of the other party on the third-party application.

Description

Method and system for providing group service for third-party application

[ technical field ] A method for producing a semiconductor device

The invention relates to the technical field of internet, in particular to a method, a client, a server and a system for providing group service for third-party application.

[ background of the invention ]

For a third-party application providing services such as games, traveling, shopping, enterprise applications and the like for a user, a group service in the third-party application is sometimes provided for business needs, so that the users in the third-party application can interact based on the group service. For example, a network gaming application, to facilitate interaction between game users, creates groups so that game users can communicate with each other, discuss game play, and the like within the same group.

However, the inventor of the present invention has found that the method has at least the following disadvantages: firstly, the group service is not the core business capability of the third-party application, and if the group service is developed and provided in the third-party application, the development and operation cost of a third-party application service provider can be increased; second, the use frequency of many third-party applications is usually low, and the user is not always on-line on the third-party application, so even if a group session message is generated on the third-party application, the user cannot necessarily receive and view the group session message in time.

In addition, for a third-party application that does not provide group services, a user sometimes spontaneously creates a group on a social network application (e.g., an application such as instant messaging or microblog), and notes information related to the third-party application on the name and introduction of the group (e.g., a certain colony of a certain game, a certain route group of a certain travel website, etc.), and then sends a group number, a group two-dimensional code, a group joining link, etc. to other users, so that other users join the group together; or other users may join the group by themselves searching for the group through the search functionality of the social networking application.

However, the inventor of the present invention found that the method has at least the following disadvantages: firstly, for a user applying for joining a group of social network applications, whether the user belongs to a user on a corresponding third-party application cannot be verified; secondly, for a user who has joined a group, unless the user declares himself (such as modifying a nickname, modifying a signature or sending a group session message and the like, the user is a certain user on a third-party application, and the like), other users in the group can hardly recognize that the user is a certain user on the third-party application; and thirdly, even if the user self-declares that the user is a certain user on the corresponding third-party application, because each user self-declares is needed, the use is complicated, effective constraint is not provided for the user, and whether the user self-declares or not and whether the declaration of the user is real or not cannot be ensured.

It is important to note that the above background information is only used to enhance an understanding of the background of the present invention and, thus, may include prior art information that does not constitute a part of the present disclosure as known to one of ordinary skill in the art.

[ summary of the invention ]

The main objective of the present invention is to provide a method, a client, a server and a system for providing group services for third-party applications, so as to solve at least to some extent one or more problems caused by limitations and disadvantages of the related art, including the following technical solutions:

in a first aspect, a method for providing a group service for a third-party application is provided, and is applied to a social application server, and the method includes:

creating a group and setting a third party application identifier to which the group belongs, wherein the third party application identifier indicates a third party application to which the group belongs;

determining whether the user is a user on a third-party application server according to a social user account of the user, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier;

and if so, adding the user into the group according to the social user account.

Preferably, the setting the identifier of the third-party application to which the group belongs includes:

associating the group identification information of the group with the third-party application identification, and enabling the third-party application identification to be obtained according to the group identification information; and/or the first and/or second light sources,

the attribute information of the group comprises an attribute used for indicating a third-party application, and an attribute value of the attribute is set as the third-party application identification.

Preferably, the associating the group identification information of the group with the third party application identification includes:

the group identification information comprises the third-party application identification, so that the third-party application identification can be acquired from the group identification information; and/or the first and/or second light sources,

and establishing an incidence relation between the group identification information and the third party application identification so that the third party application identification can be obtained in the incidence relation according to the group identification information.

Preferably, when determining whether the user is a user on the third-party application server according to the social user account of the user, the third-party application identifier is acquired according to group identifier information sent by the social application client.

Preferably, the determining whether the user is a user on the third-party application server side according to the social user account of the user includes:

querying the social user account from the third-party application server to determine whether the user is a user on the third-party application server; alternatively, the first and second electrodes may be,

determining an application user account according to the social user account and the third-party application identifier, and inquiring the application user account from the third-party application server to determine whether the user is a user on the third-party application server; alternatively, the first and second liquid crystal display panels may be,

and acquiring a mobile phone number according to the social user account, and inquiring the mobile phone number from the third-party application server to determine whether the user is the user on the third-party application server.

Preferably, the querying the application user account to the third-party application server to determine whether the user is a user on the third-party application server includes:

sending a user query request to the third-party application server, wherein the user query request comprises the application user account;

receiving feedback information of the third-party application server side;

and if the feedback information indicates that the user exists, determining that the user is the user on the third-party application server side.

Preferably, the joining the user to the group according to the social user account includes:

adding the social user account in a group member list of the group; alternatively, the first and second electrodes may be,

and determining a group member account according to the social user account and the third-party application identifier, acquiring the social user account according to the group member account, and adding the group member account into a group member list of the group.

Preferably, the adding the social user account to the group member list of the group further comprises:

and determining a group member account according to the social user account and the third-party application identifier, and acquiring the social user account according to the group member account.

Preferably, the determining the group member account according to the social user account and the third party application identifier includes:

acquiring the group member account in a pre-established corresponding relationship according to the social user account and the third-party application identifier; alternatively, the first and second electrodes may be,

and based on a predetermined encryption mode, encrypting and generating the group member account according to the social user account and the third party application identifier.

Preferably, the obtaining the group member account in the pre-established corresponding relationship according to the social user account and the third party application identifier includes:

acquiring a corresponding group member account according to the social user account and the third-party application identifier;

if the corresponding group member account is obtained, determining the corresponding group member account as the group member account;

if the corresponding group member account is not acquired, generating a unique group member account, determining the unique group member account as the group member account, and establishing a corresponding relationship between the social user account and the third-party application identifier and the unique group member account, so that the unique group member account can be acquired according to the social user account and the third-party application identifier, and the social user account can be acquired according to the unique group member account.

Preferably, the generating the group member account based on the social user account and the third party application identifier by encryption includes:

generating a hash value according to the social user account;

establishing a corresponding relation between the hash value and the social user account so that the social user account can be obtained according to the hash value;

and performing XOR operation on the hash value and the third party application identifier to generate the group member account.

Preferably, the method further comprises:

sending the user attribute information of the user on the third-party application server side to the group members of the group according to the social user account; and/or the first and/or second light sources,

sending the group information of the group to the social user account; or/and (c) the first and/or second,

and sending application information to the social user account, wherein the application information is the application information corresponding to the third-party application identifier.

Preferably, the sending, according to the social user account, the user attribute information of the user on the third-party application server to the group members of the group includes:

acquiring user attribute information of the user on the third-party application server according to the social user account, and forwarding the user attribute information to the group members; alternatively, the first and second electrodes may be,

determining an application user account according to the social user account and the third-party application identifier, and sending the application user account and a request address to the group member so that the group member can request the request address to acquire the user attribute information according to the application user account, wherein the request address is a request address corresponding to the third-party application identifier; alternatively, the first and second electrodes may be,

and sending the social user account and the request address to the group member so that the group member can request the request address to acquire the user attribute information according to the social user account, wherein the request address is the request address corresponding to the third-party application identifier.

Preferably, the obtaining of the user attribute information of the user on the third-party application server side according to the social user account includes:

inquiring the social user account number from the third-party application server to acquire the user attribute information; alternatively, the first and second electrodes may be,

determining an application user account according to the social user account and the third-party application identifier, and inquiring the application user account from the third-party application server to acquire the user attribute information.

Preferably, the user attribute information includes one or more of a user name, a user head portrait, a gender, an age, a birth date, a location, and a personal signature.

Preferably, the determining an application user account according to the social user account and the third-party application identifier includes:

acquiring the application user account in a pre-established corresponding relation according to the social user account and the third-party application identifier; alternatively, the first and second liquid crystal display panels may be,

and based on a predetermined encryption mode, encrypting and generating the application user account according to the social user account and the third-party application identifier.

Preferably, the generating the application user account by encrypting according to the social user account and the third-party application identifier includes:

and generating the application user account after hash calculation according to the social user account and the third-party application identifier.

Preferably, the group information includes a group name or/and a group profile.

Preferably, the application information includes an application name or/and an application icon or/and an application profile.

In a second aspect, a third-party application group creation method is provided, and is applied to a social application server, and the method includes:

receiving a group creation request sent by a sender, wherein the creation request is a request for creating a third-party application group;

acquiring a third party application identifier according to the creation request;

and creating a group, and setting the third party application identifier to which the group belongs as the third party application identifier.

Preferably, the acquiring the identifier of the third-party application according to the creation request includes:

the creating request comprises the third party application identifier, and the third party application identifier is obtained from the creating request; and/or the first and/or second light sources,

the creation request comprises associated information, and the third party application identifier is acquired from a pre-established association relation between the associated information and the third party application identifier according to the associated information; and/or the first and/or second light sources,

the sender is a third-party application server, and the third-party application identifier is obtained according to the identity information of the third-party application server.

Preferably, if the sender is a social application client, after obtaining the third-party application identifier according to the creation request and before creating the group, the method further includes:

determining whether the sender is a user on a third-party application server according to the social user account of the sender, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier;

if yes, executing the step of creating the group.

Preferably, the determining, according to the social user account of the sender, whether the sender is a user on a third-party application server further includes:

inquiring whether the sender allows to create a group or not from the third-party application server according to the social user account;

if yes, executing the step of creating the group.

Preferably, the sender is a social application client, and after creating the group, the method further includes:

and adding the sender into the group according to the social user account of the sender.

Preferably, the creating a group further includes:

and setting group information of the group, wherein the group information is transmitted by the sender.

Preferably, the group information includes a group name or/and a group profile.

In a third aspect, a group session message display method is provided, which is applied to a social application client, and a user has logged in the social application client, and the method includes:

receiving a group session message sent by a social application server, wherein the group session message comprises group identification information and message content, and the group is a group for third-party application;

and acquiring the user attribute information of the message sender on a third-party application server, wherein the third-party application server is the server of the third-party application to which the group indicated by the group identification information belongs.

And displaying the user attribute information and the message content on a group message session interface corresponding to the group identification information.

Preferably, the obtaining of the user attribute information of the message sender on the third-party application server includes:

receiving user attribute information sent by the social application server, wherein the user attribute information is obtained by the social application server from the third-party application server according to a social user account of the message sender; alternatively, the first and second electrodes may be,

receiving a request address sent by the social application server and an application user account of the message sender, and requesting the request address to acquire the user attribute information according to the application user account, wherein the request address is a request address used by the third-party application server for providing the user attribute information; alternatively, the first and second electrodes may be,

receiving a request address sent by the social application server and a social user account of the message sender, and requesting the request address to acquire the user attribute information according to the social user account, wherein the request address is a request address used by the third-party application server for providing the user attribute information; alternatively, the first and second electrodes may be,

and acquiring the group member account of the message sender included in the group session message from the pre-stored corresponding relationship between the group member account and the user attribute information, and acquiring the user attribute information in the corresponding relationship according to the group member account.

Preferably, the user attribute information includes a user name or/and a user avatar.

Preferably, the method further comprises:

acquiring an application name of a third-party application to which the group belongs, indicated by the group identification information, and displaying the application name on the group message session interface; and/or the first and/or second light sources,

and acquiring the group name of the group, and displaying the group name on the group message session interface.

Preferably, the obtaining of the application name of the third-party application to which the group indicated by the group identification information belongs includes:

and inquiring the application name of the third-party application to the social application server according to the group identification information, and receiving and acquiring the application name.

Preferably, the acquiring the group name of the group includes:

receiving and acquiring the group name sent by the social application server; and/or the first and/or second light sources,

the method comprises the steps of obtaining and storing a corresponding relation between group identification information and a group name in advance, and obtaining the group name in the corresponding relation according to the group identification information.

Preferably, the application name and the group name are displayed in a header area of the group message session interface.

In a fourth aspect, a group display method is provided, which is applied to a social application client, and a user has logged in the social application client, and the method includes:

the method comprises the steps that group information of at least one part of third-party application groups to which a user belongs is obtained from a social application server, and application information of third-party applications to which each group in the at least one part of third-party application groups belongs is obtained;

displaying a group display interface, and displaying the group information and the application information on the group display interface.

Preferably, the group information includes a group name or/and a group profile.

Preferably, the method further comprises:

and displaying a title in a title area of the group display interface, wherein the title represents that the group display interface is used for a third-party application group.

Preferably, the displaying the group information and the application information on the group display interface includes:

and displaying the group information and the application information of each group according to groups.

Preferably, the displaying the group information and the application information of each group by group includes:

and generating an area for each group according to each group, and displaying the group information and the application information of the group in the area of each group.

Preferably, the generating the region for each group according to each group further includes:

and dividing each area into two sub-areas, wherein one sub-area displays the application information of the group, and the other sub-area displays the group information of the group.

Preferably, the dividing each region into two sub-regions further comprises:

the left sub-area displays the application information of the group, and the right sub-area displays the group information of the group.

Preferably, the method further comprises:

and receiving group session messages from the social application server, and displaying the last group session message of each group on the group display interface.

Preferably, the last group session message displayed includes a message sender and message content.

Preferably, the message sender is user attribute information of a sender of the last group session message on a third-party application server, and the third-party application server is a server of a third-party application to which the group belongs.

In a fifth aspect, a group detail display method is provided, and is applied to a social application client, where a user has logged in, and the method includes:

acquiring group information of a designated group from a social application server, wherein the designated group is a group for third-party application;

acquiring user attribute information of at least one part of group members in the designated group on a third-party application server, wherein the third-party application server is a server of a third-party application to which the designated group belongs;

displaying a group detail interface, displaying the group information on the group detail interface, and displaying the user attribute information of at least one part of group members.

Preferably, the group information includes a group name or/and a group profile.

Preferably, the method further comprises

And acquiring application information of the third-party application to which the specified group belongs from the social application server.

Preferably, the obtaining of the user attribute information of at least a part of group members in the designated group on the third-party application server includes:

acquiring user attribute information of at least a part of group members from the social application server, wherein the user attribute information of at least a part of group members is acquired from the third-party application server by the social application server according to social user accounts of at least a part of group members; alternatively, the first and second electrodes may be,

acquiring a request address and application user accounts of at least a part of group members from the social application server, and requesting to acquire user attribute information of at least a part of group members from the request address according to the application user accounts, wherein the request address is a request address used by the third-party application server for providing the user attribute information; alternatively, the first and second electrodes may be,

and acquiring a request address and the social user account of at least part of group members from the social application server, and requesting to acquire the user attribute information of at least part of group members from the request address according to the social user account, wherein the request address is a request address used by the third-party application server for providing the user attribute information.

Preferably, the display group detail interface is displayed after responding to the selection operation of the specified group in the group display interface.

In a sixth aspect, a social application server is provided, including: a processor, a memory and a computer program stored on the memory and executable on the processor, characterized in that the computer program implements the method according to the first aspect above or/and implements the method according to the second aspect above when executed by the processor.

There is provided a social application client comprising: a processor, a memory and a computer program stored on the memory and executable on the processor, characterized in that the computer program implements the method according to the third aspect as described above, or/and implements the method according to the fourth aspect as described above, or/and implements the method according to the fifth aspect as described above when executed by the processor.

There is provided a storage medium for a social application server, wherein the storage medium stores a program for implementing the method of the first aspect or/and a program for implementing the method of the second aspect.

There is provided a storage medium for a social application client, wherein the storage medium stores a program for implementing the method according to the third aspect, and/or for implementing the method according to the fourth aspect, or/and for implementing the method according to the fifth aspect.

In a seventh aspect, a social application system is provided, the system including a social application server and a social application client; the social application server comprises the social application server of the sixth aspect; the social application client comprises a social application client as described above in the sixth aspect.

In summary, the technical effects brought by the technical solution provided by the present invention at least include: on the first hand, because the created third-party application group is created and provided with the group service by the social application server, the problems of increased development cost, low use frequency and the like caused by the self-provision of the group service by the third-party application can be avoided; in the second aspect, users joining the third-party application group can be ensured to be users on the same third-party application; in the third aspect, further, the user attribute information of the user on the third-party application server is sent to the group members, so that the users in the third-party application group can mutually identify identities based on the user attribute information of the user on the third-party application server, and the problem that each user needs to self-declare that the user is a certain user on the corresponding third-party application in the group is avoided.

[ description of the drawings ]

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

FIG. 1 is a schematic block diagram of an implementation environment in accordance with the present invention;

FIG. 2 is a flowchart illustrating an embodiment of a method for providing group services to third party applications;

FIG. 3 is a flowchart illustrating an embodiment of a method for creating a group of third-party applications;

FIG. 4 is a flowchart illustrating an embodiment of a group session message display method;

FIG. 5 is a schematic flow chart diagram of an embodiment of a group display method;

FIG. 6 is a schematic flow chart diagram of an embodiment of a group detail display method;

FIG. 7 is a schematic diagram of a group message conversation interface provided in accordance with an embodiment of a group conversation message presentation method;

FIG. 8 is a schematic diagram of a group presentation interface provided in accordance with an embodiment of a group presentation method;

fig. 9 is a schematic diagram of a group detail interface provided according to an embodiment of a group detail display method.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

[ detailed description ] embodiments

In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

First, related noun terms

To facilitate understanding, some terms referred to herein are introduced and described.

The social network application: the network application provides social application services for users, such as instant messaging, microblog, network community, video community, friend-making social application services and the like, and comprises corresponding group services. The social network application comprises a social application server and a social application client, and a user logs in the social application server through a network based on the social application client, so that the social application service provided by the social application server is obtained.

Social user accounts: in social networking applications for identifying a user's account number or identity.

A third party application: applications provided by third party application service providers for providing application services to users, such as application services for games, travel, shopping, enterprise applications, and the like. The third-party application comprises a third-party application server and a third-party application client, and the user accesses the third-party application server through the network based on the third-party application client, so that the business application data and the service provided by the third-party application server are obtained.

Third party application identification: the identification information for uniquely identifying the third party application may be a domain name of the third party application server, or may be a unique character string.

Applying the user account: and the third-party application server is used for identifying an account number or identification of a user.

Group (2): in the social network application, a plurality of users form a group, and the group members can communicate with each other.

Third party application group: a group for a third party application established on a social networking application.

Social application group: a group of users for a social networking application established on the social networking application.

It should be noted that both the social application group and the third-party application group are groups established on the social network application, where the social application group is a group used for interaction between users of the social network application, and it can be understood that, before the application date of the present invention, the social application group is a group form common in the social network application; the third-party application group is a group used for interaction between users of third-party applications, and it can be understood that when a user is a user of both the social network application and a certain third-party application, the user can join the third-party application group used for the third-party application, or when the group used for the third-party application is established, the user of the third-party application can join the group for interaction.

The group member account number: an account number or identification used in the group to identify the group member.

OpenID: in order not to reveal the user's social user account, an identification is generated to replace the social user account. In other words, in order not to directly provide the social user account in the third-party application server, the social user account of the user is identified in the third-party application server by using OpenID.

Group session message: messages that group members interact within the group.

The user name is as follows: the name of the user on the third party application includes the user's real name or/and the user's nickname. For example, in some third party applications (such as some enterprise applications), the username is referred to as the user's real name; in some third party applications (such as some online games), the username is referred to as a nickname for the user; in some third party applications (e.g., some shopping applications), the user is registered with both a nickname and a real name after real-name authentication, and the user name includes the user's real name or/and the user's nickname. Further, if the user is registered with a merchant name, business name, or the like on a third party application, the user name may also include the merchant name, business name, or the like.

Mobile phone number: the number to be dialed for calling a Mobile Subscriber and the receiving number for sending a short message to a Mobile Subscriber, also called MSISDN (Mobile Subscriber ISDN number).

Second, description of the implementation Environment

Referring to fig. 1, a schematic diagram of an implementation environment according to the present invention is shown. The implementation environment comprises a social application server, a social application client, a third-party application server, a third-party application client and a user.

The social application server side: and the server is used for providing the social network application service for the user. The system comprises a third-party application server, a first-party server and a second-party server, wherein the third-party application server is connected with the third-party application server through a network and used for determining whether a user is the user on the third-party application server or not and acquiring user attribute information of the user from the third-party application server; and the social application client is connected with the network and used for providing group service for the user through the social application client.

The social application client: and the client program of the social network application is used for accessing the social application server to obtain the social application service.

The third-party application server side: and the service end is used for providing required third-party application services for the user, such as services of games, travel, shopping, enterprise applications and the like. The system comprises a social application server, a third party application server and a social application server, wherein the social application server is connected with the social application server through a network and used for feeding back whether a user is the user on the third party application server or not to the social application server and providing user attribute information of the user to the social application server; and the third-party application client is connected with the network and used for providing the third-party application service for the user through the third-party application client.

The third party application client: and the client program of the third-party application is used for accessing the third-party application server to obtain the third-party application service.

The user: the user is both a user of the social networking application and a user of a third party application. Namely, the user can access the social application server through the network based on the social application client, so as to obtain the social application service provided by the social application server; the user can also access the third-party application server through the network based on the third-party application client, so that the third-party application service provided by the third-party application server is obtained.

It should be noted that the program types of the social application client and the third-party application client may be a native application client (e.g., a native application program on an operating system), a Web application client (e.g., a Web page program running on a browser), a light application client (e.g., a program based on HTML5 or JavaScript), or a hybrid application client, and the program types of the clients are not limited in the embodiments of the present invention.

It should be noted that the social application server and the social application client in the embodiments of the present invention may be only used to implement the method provided in the embodiments of the present invention, and thus, the social application server may also be referred to as a group server, and the social application client may also be referred to as a group client; in other words, the methods provided by the embodiments of the present invention may be additionally implemented on the basis of not implementing the social network application of the present invention.

It is understood that, in an actual implementation environment, a plurality of or a large number of users may be further included, and a plurality of or a large number of third-party applications provided by different third-party application service providers and used for providing different third-party application services may be further included, where each user accesses the social application service terminal through the network based on the social application client running on the respective user terminal, and each user accesses the corresponding third-party application service terminal through the network based on the third-party application client, respectively, so as to obtain the third-party application service provided by the corresponding third-party application service terminal.

It can be understood that the social application server or the third-party application server may be a single server, a server cluster composed of a plurality of servers, or a cloud server.

It should be noted that the implementation environment configuration shown in fig. 1 is not limited to the implementation environment, and may include more or less components than those shown, or some components may be combined, or a different arrangement of components may be used, as will be appreciated by those skilled in the art. The implementation environment configuration shown in fig. 1 is only for enhancing understanding of the present technology and thus may include prior art information that does not constitute a known art to those of ordinary skill in the art.

Third, a method embodiment for providing group service for third party application

Referring to fig. 2, a flowchart of an embodiment of a method for providing a group service for a third-party application according to the present invention is shown. The embodiment is exemplified by applying the method to the social application server in the implementation environment shown in fig. 1, where the method may include:

step 201, creating a group, and setting a third party application identifier to which the group belongs, wherein the third party application identifier indicates a third party application to which the group belongs.

The method includes the steps of creating a group for the third-party application on a social application server, and setting a third-party application identifier to which the group belongs, wherein the third-party application identifier indicates the third-party application to which the group belongs, and the group can also be understood as a group for providing group service for the third-party application indicated by the third-party application identifier.

The setting of the third-party application identifier to which the group belongs may include the following various embodiments:

in a first embodiment, the group identification information of the group is associated with the third-party application identifier, and the third-party application identifier can be acquired according to the group identification information.

The group is provided with group identification information, and the group identification information is used for uniquely identifying the group, and then a third party application identification to which the group belongs is set, so that the group identification information of the group can be associated with the third party application identification, and the third party application identification can be acquired according to the group identification information.

For example, the third party application identifier is included in the group identification information, so that the third party application identifier can be acquired from the group identification information.

Specifically, the group identification information mainly includes the third-party application identifier and a unique identifier, and the group can be uniquely identified according to the third-party application identifier and the unique identifier.

Since the group identification information mainly includes the third-party application identification and the unique identification, the third-party application identification can be obtained from the group identification information.

For another example, an association relationship between the group identifier information and the third-party application identifier is established, so that the third-party application identifier can be acquired in the association relationship according to the group identifier information.

In a second embodiment, the attribute information of the group includes an attribute indicating a third-party application, and an attribute value of the attribute is set as the third-party application identifier.

And setting an attribute for indicating a third-party application in the attribute information of the group, namely setting the attribute for indicating the third-party application to which the group belongs, and setting an attribute value of the attribute as the identifier of the third-party application.

As can be seen from the above, compared with the existing social application group, in this step, a group for a third-party application is created, and the third-party application identifier to which the group belongs is set to indicate the third-party application to which the group belongs, so that a group service can be provided for the third-party application according to the third-party application identifier, where the third-party application is indicated by the third-party application identifier.

Further, group information such as group name and/or group profile can be set for the group.

It should be noted that, application information may also be set for the third-party application in advance at the social application service end, where the application information includes an application name or/and an application icon or/and an application profile. For example, a corresponding relationship between the third-party application identifier and the application information is established in advance, so that the corresponding application information can be obtained in the corresponding relationship according to the third-party application identifier, specifically, when the third-party application is registered in advance on the social application server, the application information of the third-party application is submitted by the third-party application service provider, and after the social application server passes the auditing, corresponding attribute values are set in attributes such as the third-party application identifier of the third-party application, the application name or/and the application icon or/and the application profile.

Step 202, determining whether the user is a user on a third-party application server according to a social user account of the user, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier; if yes, proceed to step 203.

For a user to be added into the group, determining whether the user is a user on a third-party application server according to the social user account of the user and the third-party application identifier, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier; if the user is determined to be the user on the third-party application server, continuing to execute the following step 203; otherwise, the following step 203 and its subsequent steps are not performed.

Specifically, determining whether the user is the user on the third-party application server according to the social user account of the user may include various embodiments, for example, the embodiments may include:

in a first embodiment, the social user account is queried for the third-party application server to determine whether the user is a user on the third-party application server.

The user on the third-party application server binds a social user account in advance, that is, the user is identified by the social user account on the third-party application server, the social application server may query the social user account to the third-party application server, and if the query result indicates that the user exists, it is determined that the user is the user on the third-party application server. Specifically, the method comprises the following steps:

and the social application server side sends a user query request to the third-party application server side, wherein the user query request comprises the social user account. Specifically, a request address of the third-party application server is preset on the social application server, and the request address is used for inquiring information of a user on the third-party application server, for example, when the third-party application server is registered in advance, the social application server establishes a corresponding relationship between a third-party application identifier and the request address, and the corresponding request address can be obtained according to the third-party application identifier; the social application server side sends a user query request to the request address, wherein the user query request comprises the social user account;

and receiving feedback information of the third-party application server. Specifically, after the third-party application server receives the user query request, the third-party application server obtains the social user account included in the user query request, queries the user bound with the social user account according to the social user account, and feeds back information indicating whether the user exists according to a query result, for example, feeds back information indicating that the user exists, or feeds back user attribute information of the user, and the like, which can indicate that the user exists; correspondingly, the social application server receives feedback information of the third-party application server;

And the social application service side can also synchronize the user data bound with the social user account on the third-party application service side to the social application service side, and the social application service side inquires the social user account in the user data and determines whether the user is the user on the third-party application service side according to an inquiry result. It can be understood that, if there are multiple third-party applications, the social application server may use a third-party application identifier to mark user data synchronized by the corresponding third-party application server, and determine the corresponding user data according to the third-party application identifier when querying the social user account.

In a second implementation manner, an application user account is determined according to the social user account and the third-party application identifier, and the application user account is queried for the third-party application server to determine whether the user is a user on the third-party application server.

Determining an application user account according to the social user account and the third-party application identifier, inquiring the application user account from the third-party application server, and if the inquiry result indicates that the user exists, determining that the user is the user on the third-party application server.

And determining an application user account according to the social user account and the third-party application identifier, wherein the application user account is an account for identifying a user on the third-party application server side. In particular, various embodiments may be included:

in one embodiment, the application user account is obtained in a pre-established correspondence according to the social user account and the third-party application identifier.

The method comprises the steps that the corresponding relation between the social user account and the application user account is pre-established on the social application server side, the corresponding relation between the third-party application identification and the application user account is pre-established, so that the corresponding application user account can be obtained in the corresponding relation according to the social user account and the third-party application identification, and therefore the application user account can be obtained in the corresponding relation according to the social user account and the third-party application identification.

In one embodiment, the application user account is generated by encrypting according to the social user account and the third-party application identifier based on a predetermined encryption mode.

The social application server encrypts the social user account and the third party application identifier to generate an encrypted value based on a predetermined encryption mode, and generates the same encrypted value when the same social user account and the same third party application identifier are used again for encryption. Taking hash algorithm encryption as an example, combining the social user account and the third party application identifier to generate a new character string, encrypting the character string by using a hash algorithm to generate a hash value, and taking the hash value as an application user account; and after the social user account and the third-party application identifier are combined in the same mode and encrypted by the hash algorithm again, generating a hash value with the same value, wherein the hash value is the application user account.

In an actual application scenario, taking an example that a social application server provides an OAuth-like authorization service, the third-party application server integrates the OAuth authorization service, when the third-party application server obtains authorization of a user, the social application server generates an OpenID according to the social user account of the user and the third-party application identifier of the third-party application server, the third-party application server obtains the OpenID fed back by the social application server, and uses the OpenID as an application user account of a newly registered user, or binds the OpenID as an application user account of an existing user, so that the OpenID can be used as an application user account of the user on the third-party application server. Therefore, the social application server uses a manner corresponding to OpenID generation, and can obtain the same OpenID according to the social user account and the third-party application identifier, that is, the social application server can obtain the application user account according to the social user account and the third-party application identifier.

After determining the application user account, the social application service side queries the user by querying the application user account to the third-party application service side, and determines whether the user is a user on the third-party application service side according to a query result, which may specifically include the following multiple steps:

and sending a user query request to the third-party application server, wherein the user query request comprises the application user account. Specifically, a request address of the third-party application server is preset on the social application server, and the request address is used for inquiring information of a user at the third-party application server; for example, when a third-party application is registered in advance on a social application server, a corresponding relation between a third-party application identifier and a request address is established, and the corresponding request address can be obtained according to the third-party application identifier; the social application server side sends a user query request to the request address, wherein the user query request comprises the application user account;

and receiving feedback information of the third-party application server. Specifically, after the third-party application server receives the user query request, the third-party application server obtains the application user account included in the user query request, queries the application user account in a user database according to the application user account, and feeds back information indicating whether the user exists according to a query result, for example, feeds back information indicating that the user exists, or feeds back user attribute information of the user, and the like, which can indicate that the user exists; correspondingly, the social application server receives feedback information of the third-party application server;

And the social application service side inquires the application user account in the user data, and determines whether the user is the user on the third-party application service side according to an inquiry result. It can be understood that, if there are multiple third-party applications, the social application server may use a third-party application identifier to mark user data synchronized by the corresponding third-party application server, and determine the corresponding user data according to the third-party application identifier when querying the application user account.

In a third implementation manner, a mobile phone number is obtained according to the social user account, and the mobile phone number is inquired from the third-party application server to determine whether the user is the user on the third-party application server.

If the user on the third-party application server side binds a mobile phone number in advance, namely the user is identified by the mobile phone number on the third-party application server side, meanwhile, the user on the social application server side binds the mobile phone number, the social application server side obtains the mobile phone number according to the social user account number, inquires the mobile phone number for the third-party application server side, and if the inquiry result indicates that the user exists, the user is determined to be the user on the third-party application server side. The specific implementation manner is similar to the implementation manner in which the social user account is queried for the third-party application server to determine whether the user is a user on the third-party application server in the first implementation manner, wherein the mobile phone number is used for replacing the social user account to perform querying, and the request address is an address capable of querying information of the user on the third-party application server according to the mobile phone number, and is not described herein again.

It should be noted that, when the social application server queries the mobile phone number from the third-party application server, the social application server may first obtain the authorization of the social application client. For example, taking an example that a social application server provides authorization service similar to OAuth, after obtaining authorization agreement of a social application client, the social application server sends the mobile phone number to the third-party application server for query. This embodiment is not limited.

And step 203, adding the user into the group according to the social user account.

On the social application server, the user is identified by the social user account, so that the user can be added to the group according to the social user account.

Specifically, adding the user to the group according to the social user account may include various embodiments, for example, may include:

in a first embodiment, the social user account is added to a group member list of the group.

The social application server side is provided with a corresponding group member list for the group, the group members are identified by the social user accounts in the group member list, and the social user accounts are added into the group member list of the group, so that the user is added into the group.

Further, in order to not send the social user account of the group member to the social application client, and also in order to avoid the same user using the same account or identifier in a third-party application group of different third-party applications, the group member account may be determined according to the social user account and the third-party application identifier, and the social user account may be acquired according to the group member account, so that the same user may use different group member accounts in third-party application groups of different third-party applications. Specifically, determining the group member account according to the social user account and the third-party application identifier may include various embodiments:

for example, the corresponding relationship between the social user account and the group member account and the third-party application identifier is stored in advance on the social application server, that is, the group member account can be found in the corresponding relationship according to the social user account and the third-party application identifier.

Specifically, the social application server searches for a corresponding group member account in the corresponding relationship according to the social user account and the third-party application identifier.

If the corresponding group member account is found, the social application server side is indicated to create a group member account for the user in a corresponding group, the corresponding group is a third party application group corresponding to the third party application identifier, and the social application server side determines that the corresponding group member account is the group member account.

If the corresponding group member account is not found, it indicates that the social application server does not create a group member account for the third-party application identifier for the user, the social application server generates a unique group member account, for example, generates a unique character string as the group member account, determines that the unique group member account is the group member account, and establishes a corresponding relationship between the social user account and the third-party application identifier and the unique group member account, so that the unique group member account can be obtained in the corresponding relationship according to the social user account and the third-party application identifier, and the social user account can be obtained according to the unique group member account.

For another example, the group member account is generated by encrypting according to the social user account and the third party application identifier.

And the social application server side takes the encrypted value generated by encrypting the social user account and the third party application identifier as the group member account, and can acquire the social user account according to the encrypted value.

Specifically, the social user account is encrypted by using a hash algorithm to generate a hash value, and a corresponding relation between the hash value and the social user account is established, so that the social user account can be obtained according to the hash value; and taking the value generated after the XOR operation of the hash value and the third party application identifier as the group member account. Therefore, the hash value can be obtained after XOR operation is carried out according to the group member account and the third party application identifier, and the social user account can be obtained according to the hash value.

It should be noted that, if the second implementation manner is adopted in step 202, since the implementation manner includes determining the application user account according to the social user account and the third-party application identifier, the group member account determined according to the social user account and the third-party application identifier in this step and the application user account determined in step 202 may also be the same account, so that the implementation process of determining the group member account in this step and the implementation process of determining the application user account in step 202 may be combined and implemented in the same process, for example, in the implementation process of the second implementation manner in step 202, the application user account is determined by referring to the implementation manner of determining the group member account in this step, and meanwhile, the application user account serves as the group member account in this step.

In the second embodiment, a group member account is determined according to the social user account and the third-party application identifier, and the group member account is added to a group member list of the group according to the group member account which can be obtained.

The social application server determines the group member account of the user according to the social user account and the third-party application identifier, and enables the social user account to be obtained according to the group member account, so that when the social application server executes corresponding operations (such as sending group session messages) to the group members, the social application server can obtain the social user account of the group members according to the group member account of the group members, and accordingly corresponding operations are executed to the social user account. In a specific embodiment, reference may be made to the embodiment in which the group member account is determined according to the social user account and the third party application identifier in the first embodiment, which is not described herein again.

And adding the group member account in a group member list of the group. Specifically, the social application server sets a corresponding group member list for the group, and if the group member is identified by a group member account in the group member list, the group member account is added to the group member list of the group, thereby indicating that the user is added to the group. It can be understood that, if information (such as group session information, user attribute information, and the like) is to be sent to the group member, the group member account of the group member may be obtained according to the group member list, the social user account of the group member may be obtained according to the group member account, and the information may be sent to the social user account of the group member.

Furthermore, a third-party application group list to which the social user account belongs may be set, and the group is added to the third-party application group list, so that the user can be determined to belong to the group according to the social user account. For example, the group identification information of the group is added to a third-party application group list to which the social user account belongs.

Because the user is added into the group, the group members can interact in the group based on the social application service provided by the social application service side. For example, as an example of exchanging group session messages, a group member sends a group session message to a social application server; the social application server side forwards the group session message to the group members of the group; accordingly, the group members receive the group session message.

Further, the user attribute information of the user on the third-party application server side can be sent to the group members of the group according to the social user account.

After the user is added into the group, the user attribute information of the user on the third-party application server side can be sent to the group members of the group, and the user attribute information comprises one or more items of user name, user head portrait, gender, age, birthday, location and individual signature. Specifically, the user attribute information of the user on the third-party application server may be sent to the group members of the group according to the social user account, for example, the following various embodiments may be included:

in a first implementation manner, the user attribute information of the user on the third-party application server side is acquired according to the social user account, and the user attribute information is forwarded to the group members.

For example, if a user on the third-party application server binds a social user account in advance, the user attribute information may be obtained by querying the social user account from the third-party application server.

For another example, if a user on the third-party application server binds a mobile phone number in advance, the mobile phone number may be obtained according to the social user account, and the user attribute information may be obtained by querying the mobile phone number from the third-party application server.

For example, the social application server determines an application user account according to the social user account and the third-party application identifier, and obtains the user attribute information by querying the application user account from the third-party application server.

Specifically, the social application server determines the application user account according to the social user account and the third-party application identifier, and in the second embodiment of step 202, reference may be made to the embodiment in which the application user account is determined according to the social user account and the third-party application identifier, or the application user account and the third-party application identifier may be combined and implemented in a single process, which is not described herein again.

And the social application server side acquires a corresponding request address according to the third-party application identifier. For example, the social application server presets a request address for querying user information from the third-party application server, that is, a corresponding relationship between the third-party application identifier and the request address is preset, so that the request address can be obtained in the corresponding relationship according to the third-party application identifier, and the request address is an address for querying information of a user on the third-party application server.

And then the social application server sends a user query request to the request address, wherein the user query request comprises the application user account.

After the third-party application server receives the user query request, the application user account in the user query request is obtained, the user attribute information of the user is queried according to the application user account, and the user attribute information is fed back to the social application server.

And the social application server forwards the user attribute information to the group members of the group.

The method and the system for managing the group members in the social network can be used for simultaneously managing the user attribute information of the user, and can be used for simultaneously managing the user attribute information of the user. And will not be described in detail herein.

It should be noted that, this embodiment may also be combined with the process of querying the third-party application server for the user in step 202 and implemented in one process. For example, in step 202, after the third-party application server receives the user query request sent by the social application server, if the user exists on the third-party application server, the feedback information includes the user attribute information of the user; if the feedback information received by the social application service side comprises user attribute information, indicating that the user exists, so that the social application service side determines that the user is the user on the third-party application service side and acquires the user attribute information; after the user is joined to the group in step 203, the user attribute information is sent to the group members of the group.

In a second implementation manner, an application user account is determined according to the social user account and the third-party application identifier, and the application user account and a request address are sent to the group member, so that the group member can request the request address to acquire the user attribute information according to the application user account, and the request address is a request address corresponding to the third-party application identifier.

Specifically, the social application server determines the application user account according to the social user account and the third-party application identifier, and the specific implementation may refer to the implementation that determines the application user account according to the social user account and the third-party application identifier in the second implementation of step 202, or may be implemented in a process by combining the two implementations, and the specific implementation process is not described herein again.

And the social application server acquires a corresponding request address according to the third-party application identifier, wherein the request address is used for inquiring user information from the third-party application server according to an application user account. For example, the social application server presets a request address for querying the third-party application server for the user information, that is, a corresponding relationship between the third-party application identifier and the request address is preset, so that the request address can be obtained in the corresponding relationship according to the third-party application identifier.

And then the social application server sends the request address and the application user account to the group members, so that after the group members receive the request address and the application user account, the group members can request the request address to acquire the user attribute information according to the application user account, for example, a user query request including the application user account is sent to the request address, and the user attribute information fed back by the third-party application server is received and acquired.

In a third implementation manner, the social user account and the request address are sent to the group member, so that the group member can request the request address to acquire the user attribute information according to the social user account, and the request address is a request address corresponding to the third-party application identifier.

If the user on the third-party application server side binds a social user account in advance, the social user account and the request address can be sent to the group member, so that the group member can request the request address to acquire the user attribute information according to the social user account, and the request address is the request address corresponding to the third-party application identifier.

Further, the group is pushed to the user so that the user can view the group and interact in the group, wherein the group information of the group is sent to the social user account, or/and the application information corresponding to the third-party application identifier is sent to the social user account. For example, group information such as a group name and/or a group profile is set for the group in advance, the group information is acquired according to the group identification information, and the group information is sent to the social user account, so that the social user account acquires the group information of the group to which the social user account is added; for another example, application information is set for a third-party application in advance, corresponding application information is obtained according to the third-party application identifier, and the application information is sent to the social user account, so that the social user account obtains the application information of the third-party application to which the social user account is added.

It should be understood that this embodiment is only described by taking one user as an example, if there are multiple users, the step 202 and the subsequent steps may be executed multiple times, so that the multiple users may join the group.

It should be understood that the above steps 202 to 203 may also be understood as a process of adding the user to the third-party application group, and in practical applications, the user may be added to the group in the background of the social application server, or the social application server may add the user to the group by receiving a group addition request of the social application client. Taking the example of adding a user to a group by receiving a group join request of a social application client, the third-party application identifier is obtained according to group identifier information sent by the social application client, and the social user account is a social user account logged in by the social application client, and the specific process may include:

and receiving a group joining request sent by the user through a social application client, wherein the joining request comprises group identification information. For example, a user triggers and sends a group joining request through links, two-dimensional codes and the like shared by other users, and a social application server receives the joining request;

and acquiring the third party application identifier according to the group identifier information. Corresponding to the embodiment of setting the third party application identifier to which the group belongs in step 201, if the group identifier information includes the third party application identifier, the third party application identifier is obtained from the group identifier information; or if the association relationship between the group identification information and the third-party application identification is pre-established, acquiring the third-party application identification in the association relationship according to the group identification information; or if the group is set with the attribute for indicating the third-party application, acquiring the attribute value of the attribute of the group according to the group identification information so as to acquire the third-party application identification;

and acquiring a social user account of the user through the social application client. Specifically, a user logs in a social application server through the social application client, so that a social user account of the user logged in by the social application client can be obtained, that is, the social user account of the user is obtained;

determining whether the user is a user on a third-party application server according to the social user account, where the third-party application server is a third-party application server corresponding to the third-party application identifier, and a specific implementation manner may refer to step 202;

if so, the user is added to the group according to the social user account, and the specific implementation manner may refer to step 203.

In summary, the method provided in this embodiment is mainly conceived to provide group service support for a third-party application on a social application server, create a group for the third-party application, and then join a user who is both the social application server and the third-party application to the group. Compared with the prior art, the main technical effects comprise that: on the first hand, because the created third-party application group is created and provided with the group service by the social application server, the problems of increased development cost, low use frequency and the like caused by the self-provision of the group service by the third-party application can be avoided; in the second aspect, users joining the third-party application group can be ensured to be users on the same third-party application; in the third aspect, further, the user attribute information of the user on the third-party application server is sent to the group members, so that the users in the third-party application group can mutually identify identities based on the user attribute information of the user on the third-party application server, and the problem that each user needs to self-declare that the user is a certain user on the corresponding third-party application in the group is avoided.

Fourth, a third party application group creation method embodiment

The social application server may trigger the creation of the group for the third-party application in various ways, for example, the third-party application group may be created in the background of the social application server, or the social application server may create the third-party application group by receiving an external request.

Referring to fig. 3, a flowchart of an embodiment of a third party application group creation method provided by the present invention is shown. In this embodiment, the method is applied to the social application server in the implementation environment shown in fig. 1, and in this embodiment, the social application server creates a third-party application group by receiving an external request. Specifically, the method may include:

step 301, receiving a group creation request sent by a sender, wherein the creation request is a request for creating a third-party application group.

The social application server receives a group creation request, which is a request for creating a group of third-party applications.

The sender of the group creation request may be a third-party application server. For example, the social application server opens an interface to a third-party application server, and the third-party application server sends a group creation request according to the interface.

The sender of the group creation request may also be a social application client. For example, after a user logs in the social application server through the social application client, a group creation request is sent to the social application server through the social application client.

And 302, acquiring a third party application identifier according to the creation request.

Specifically, the social application server obtains the third-party application identifier according to the creation request, and may include various embodiments, for example:

in one embodiment, the creation request includes a third-party application identifier, and the social application server obtains the third-party application identifier included in the creation request.

In one embodiment, an association relationship between the associated information and the third-party application identifier is pre-established in the social application server, and if the creation request contains the associated information associated with the third-party application identifier, the third-party application identifier is obtained in the association relationship according to the associated information. For example, an association relationship between a unique character string and a third-party application identifier is pre-established in the social application server, and when the social application server receives a creation request including the unique character string, the third-party application identifier is obtained in the association relationship according to the unique character string.

In an embodiment, as described in step 301 above, if the sender of the creation request is a third-party application server, the third-party application identifier may be obtained according to identity information of the third-party application server. Specifically, the method comprises the following steps:

for example, if an application account for performing identity authentication from the third-party application server to the social application server is used as the third-party application identifier, the application account acquired by the social application server after the identity authentication of the third-party application server passes is the third-party application identifier of the third-party application server. It should be noted that the identity authentication here refers to identity authentication from a third-party application server to a social application server, for example, in a verification request sent from the third-party application server to the social application server, identity authentication information of the third-party application server, such as an application account and a password, the application account and an encryption value, a token or a session state, encrypted by a key, and the like, is carried, the social application server authenticates the third-party application server according to the identity authentication information, and after the identity authentication information passes, obtains the application account in the identity authentication information; for another example, a token of the third-party application server or an application account associated with the session state is acquired, and the acquired application account is a third-party application identifier of the third-party application server.

For another example, the domain name is used as identity information of the third-party application server, if the domain name is used as the third-party application identifier, the social application server performs domain name reverse resolution according to the IP address of the third-party application server to obtain the domain name, and then the obtained domain name is used as the third-party application identifier of the third-party application server.

For example, a corresponding relationship between the identity information of the third-party application server and the third-party application identifier is pre-stored in the social application server, and the social application server obtains the identity information of the third-party application server (for example, obtains the identity information of the application account, the IP, or the domain name of the third-party application server), and then searches and obtains the third-party application identifier of the third-party application server in the corresponding relationship according to the obtained identity information.

It can be understood that the social application service side may support for a plurality of third-party applications, that is, support to create different groups for the plurality of third-party applications, and in order to improve the recognition degree of the third-party application group, may also pre-establish a corresponding relationship between a third-party application identifier and application information, where the application information includes an application name or/and an application icon or/and an application profile, so that corresponding application information may be obtained according to the third-party application identifier. For example, when the third-party application is registered in advance on the social application service side, the third-party application service provider submits application information of the third-party application, and after the social application service side passes the audit, the third-party application identifier is generated, and the corresponding relation between the third-party application identifier and the application information is established.

Step 303, optionally, if the sender is a social application client, determining whether the sender is a user on a third-party application server according to a social user account of the sender; if yes, proceed to step 304, which is described below.

As described in step 301, in an embodiment, the creation request is a creation request sent by a user through a social application client, and then, it may be further determined whether the sender is a user on a third-party application server, where the third-party application server is a third-party application server corresponding to the third-party application identifier; if yes, proceed to step 304 to create a group; otherwise, step 304, described below, is not performed. Specifically, the method may include the following steps:

acquiring a social user account of the sender;

and determining whether the sender is a user on a third-party application server according to the social user account, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier. For a specific implementation manner, reference may be made to the implementation manner in step 202 of the above-mentioned method for providing group service for third-party applications, which is not described herein again.

Further, not only whether the sender is a user on a third-party application server side or not is judged, but also whether the sender has the authority of creating a group or not can be further judged.

And the social application server inquires whether the sender allows to create the group or not from the third-party application server according to the social user account, if so, the following step 304 is executed to create the group, and otherwise, the following step 304 is not executed. For example, whether the user has the authority to create the third-party application group is set on the third-party application server side; the social application server side determines an application user account according to the social user account and the third-party application identifier, and sends a query request to the third-party application server side, wherein the query request comprises the application user account; the third-party application server side inquires whether the sender has the authority of creating the group or not according to the application user account, if so, the information indicating that the group is allowed to be created is fed back, otherwise, the information indicating that the group is not allowed to be created is fed back; if the social application server receives the information indicating that the group creation is allowed, the social application server determines that the sender allows the group creation, and then performs the following step 304 to create the group, otherwise, does not perform the following step 304.

And step 304, creating a group, and setting the third party application identifier to which the group belongs as the third party application identifier.

The method comprises the steps of creating a group for the third-party application on a social application server side, and setting a third-party application identifier to which the group belongs as the third-party application identifier, namely the third-party application identifier is used for indicating the third-party application to which the group belongs.

The third-party application identifier to which the group belongs is set as the third-party application identifier, the group identification information of the group can be associated with the third-party application identifier, and the third-party application identifier can be acquired according to the group identification information; the attribute value of the group indicating the attribute of the third-party application may also be set as the identifier of the third-party application. For a specific implementation manner, reference may be made to the implementation manner in step 201 of the above-mentioned method for providing group service for third-party application, which is not described herein again.

Further, in order to make the created group more easily recognizable, group information such as a group name and/or a group profile may be set for the created group, and the group information such as the group name and/or the group profile is transmitted by the sender. For example, in step 301, the creation request further includes group information, the group information is acquired from the creation request, and the acquired group information is set as the group information of the group; for another example, after creating a group, group information sent by the sender is received, and the sent group information is set as group information of the group.

As described above, in an embodiment, the creation request is a creation request sent by a user through a social application client, and further, the sender may be added to the group according to a social user account of the sender. Specifically, the method comprises the steps of adding the social user account in a group member list of the group; or determining a group member account according to the social user account and the third party application identifier, and adding the group member account into a group member list of the group according to the group member account which can be obtained by the social user account; in a specific embodiment, reference may also be made to the embodiment in step 203 of the method for providing a group service for a third-party application, which is not described herein again.

In summary, in the method provided in this embodiment, the social application server obtains the third-party application identifier according to the received group creation request, then creates the group, and associates the group identifier information with the third-party application identifier, so that the created group is a group for the third-party application identifier.

Fifth, an embodiment of a group session message display method

Referring to fig. 4, a flowchart of an embodiment of a group session message displaying method according to the present invention is shown. The embodiment is exemplified by applying the method to the social application client in the implementation environment shown in fig. 1. After a user logs in a social application server through a social application client, when the user interacts with group members in the same third-party application group, in this embodiment, a method for displaying a third-party application group session message is provided, where the method may include:

step 401, receiving a group session message sent by a social application server, where the group session message includes group identification information and message content, and the group is a group for a third-party application.

After a user logs in the social application server through the social application client, a group session message can be sent in a third-party application group, and the group session message can also be received.

For example, a group member (i.e., a message sender of a group session message) sends a group session message to the social application server, where the group session message includes group identification information and message content; the social application server receives the group session message, acquires a group member list of the group according to the group identification information, and forwards the group session message to other group members of the group according to the group member list, wherein the forwarded group session message comprises the group identification information and the message content; accordingly, other group members receive the group session message sent by the social application server.

In this embodiment, the user is taken as a group member in the other group (i.e., a message receiver of the group session message) for example, and the user receives the group session message through the logged-in social application client.

Step 402, obtaining the user attribute information of the message sender on a third-party application server, wherein the third-party application server is the server of the third-party application to which the group indicated by the group identification information belongs.

And the social application client acquires user attribute information of the message sender on a third-party application server, wherein the user attribute information comprises a user name or/and a user head portrait, and the third-party application server is a server of third-party application to which the group indicated by the group identification information belongs.

The third-party application group is a group for providing group services for the third-party applications, and it can be understood that the third-party application server is a server of the third-party application to which the group indicated by the group identification information belongs. Specifically, the social application server may determine the third-party application server according to the group identification information, for example, the social application server obtains the third-party application identifier according to the group identification information, where the obtaining manner corresponds to an implementation manner of setting the third-party application identifier to which the group belongs when the group is created, and reference may be specifically made to the above embodiment of the method for providing the group service for the third-party application, which is not described herein again; and the social application server determines a third-party application server according to the third-party application identifier.

Specifically, the social application client obtains the user attribute information of the message sender on the third-party application server, which may include various implementation manners, and specifically may include:

in a first implementation manner, user attribute information sent by the social application server is received, where the user attribute information is obtained by the social application server from the third-party application server according to a social user account of the message sender.

And the social application server side acquires the user attribute information of the message sender on the third-party application server side according to the social user account of the message sender, and then forwards the user attribute information to the social application client side, and the social application client side receives and acquires the user attribute information.

Specifically, the social application server obtains a social user account of the message sender, and obtains the user attribute information of the message sender on the third-party application server according to the social user account, and a specific implementation manner may refer to an implementation manner in which, in the above method embodiment for providing a group service for a third-party application, the user attribute information of the user on the third-party application server is sent to group members of the group according to the social user account, which is not described herein again; then the social application server side forwards the user attribute information to a social application client side; accordingly, the social application client receives and acquires the user attribute information.

In a second implementation manner, a request address sent by the social application server and an application user account of the message sender are received, and the user attribute information is requested to be acquired from the request address according to the application user account, where the request address is a request address used by the third-party application server to provide the user attribute information.

Specifically, the social application server obtains a social user account of the message sender, determines an application user account according to the social user account and the third-party application identifier, and sends the application user account and a request address to a group member of a group in which the group identifier information is located, so that the group member can request the request address to obtain the user attribute information according to the application user account, wherein the request address is a request address corresponding to the third-party application identifier and is also a request address used by the third-party application server for providing the user attribute information. In a specific embodiment, reference may be made to the embodiment of the method for providing a group service for a third-party application, where the user attribute information of the user on the third-party application service end is sent to group members of the group according to the social user account, which is not described herein again.

Correspondingly, the social application client receives and acquires the request address and the application user account of the message sender; and the social application client requests the request address to acquire the user attribute information of the message sender according to the application user account of the message sender.

In a third implementation manner, a request address sent by the social application server and a social user account of the message sender are received, and the user attribute information is requested to be acquired from the request address according to the social user account, wherein the request address is a request address used by the third-party application server for providing the user attribute information.

If the user on the third-party application server binds the social user account in advance, the social application server can send the social user account and the request address to the group member, so that the group member can request the request address to acquire the user attribute information according to the social user account, and the request address is the request address corresponding to the third-party application identifier and is also the request address used by the third-party application server to provide the user attribute information.

Correspondingly, the social application client receives and acquires the request address and the social user account of the message sender; and the social application client requests the request address to acquire the user attribute information of the message sender according to the social user account of the message sender.

In a fourth embodiment, the user attribute information is obtained from the pre-stored correspondence between the group member account and the user attribute information in the correspondence according to the group member account included in the group session message.

For example, the social application server obtains a corresponding group member list according to the group identification information, and if a social user account is added in the group member list to identify a group member, the social application server obtains the social user account of the group member from the group member list; if the group member account is added to the group member list to identify the group members, the social application server side acquires the group member account of each group member from the group member list, and acquires the corresponding social user account according to the group member account; the social application server side acquires user attribute information corresponding to each group member from the third-party application server side according to each social user account, and sends each group member account and the corresponding user attribute information to the social application client side according to the corresponding relation; the social application client receives and stores the corresponding relation between the group member account and the user attribute information; the group session message received by the social application client also comprises a group member account of the message sender, so that the social application client searches and acquires the user attribute information of the message sender on the third-party application server side in the corresponding relationship according to the group member account of the message sender.

For another example, the social application server determines the application user account of each group member according to the social user account of each group member and the third-party application identifier; the social application server side sends each group member account and the corresponding application user account to a social application client side according to the corresponding relation, and sends a request address to the social application client side, wherein the request address is a request address corresponding to the third-party application identifier; the social application client acquires user attribute information according to the application user account and the request address of each group member, and stores the corresponding relation between the group member account and the user attribute information of each group member; the group session message received by the social application client also comprises a group member account of the message sender, so that the social application client searches and acquires the user attribute information of the message sender on the third-party application server side in the corresponding relationship according to the group member account of the message sender.

For example, in the first or second embodiment, the social application client further includes receiving a group member account of the message sender, acquiring user attribute information of the message sender on a third-party application server, and locally storing a corresponding relationship between the group member account of the message sender and the user attribute information, so that when the group session message is received again, the group session message further includes the group member account of the message sender, and the user attribute information is matched and acquired from the locally stored corresponding relationship according to the group member account of the message sender, thereby avoiding repeated acquisition of the user attribute information from the social application server or the third-party application server.

And 403, displaying the user attribute information and the message content on a group message session interface corresponding to the group identification information.

And displaying the user attribute information and the message content on a group message session interface corresponding to the group identification information, namely displaying the message content by using the user attribute information by using a sender of the message content, thereby not only displaying that the message content is sent by the message sender, but also identifying that the message sender is a certain user on a third-party application server.

It can be understood that when there are a plurality of even a large number of group session messages, the group session messages are usually presented one by one in a session stream form on the group message session interface corresponding to the group identification information, that is, the sender and the message content of each group session message are presented item by item, where the sender of each group session message is presented with the user attribute information of the group session message sender on the third party application server, so that not only the message content sent by each group member can be presented on the group message session interface, but also it can be identified that the group member corresponds to a certain user on the third party application server.

Further, the application name of the third-party application to which the group indicated by the group identification information belongs is acquired, and the application name is displayed on the group message session interface. For example, when the third-party application is registered at the social application server, the social application server establishes a corresponding relationship between the third-party application identifier and the application name, and then the social application server obtains the corresponding application name according to the third-party application identifier and returns the application name to the social application client, and the social application client displays the application name in the group message session interface.

Further, a group name of the group is obtained, and the group name is displayed on the group message session interface. For example, the social application server acquires a group name preset by the group according to the group identification information, and returns the group name to the social application client; after receiving the group name, the social application client displays the group name on the group message session interface; for another example, the social application client obtains group information (including a group name) of a third-party application group to which the login user belongs in advance, the group information returned by the social application server further includes a third-party application identifier, the third-party application identifier is used for indicating a third-party application to which the group belongs, the social application client queries and obtains application information (including the application name) from the social application server according to the third-party application identifier, and further, in order to avoid revealing the third-party application identifier to the social application client, the social application server may also use the mapping identifier instead of the third-party application identifier.

Further, the application name and the group name are displayed in a title area of the group message session interface. For example, the application name and the group name may be separated by a symbol, and the separation symbol may include "space @ # - ()" or the like, and the title may be displayed as "certain game/certain clan" or "certain clan | certain game" in the case where the application name is "certain game" and the group name is "certain clan", for example.

And for the group session message sent by the user in the third-party application group, the group session message can also be displayed in the group message session interface, and the message sender of the group session message is displayed by the user attribute information of the user at the third-party application server. Specifically, a social application server obtains a social user account of the user, obtains user attribute information of the user from the third-party application server according to the social user account, and forwards the user attribute information to a social application client logged in by the user; or, the social application server determines an application user account according to the social user account of the user and the third-party application identifier, and then forwards the application user account and a request address to a social application client which the user logs in, wherein the request address is a request address corresponding to the third-party application identifier, so that the social application client acquires user attribute information of the user according to the application user account and the request address; therefore, the group session message sent by the user at the social application client can be shown as the message sender of the group session message in the group message session interface according to the user attribute information of the user.

It should be noted that the above listed sequence of steps in this embodiment is only one manner of execution sequence of many steps, and does not represent the only execution sequence. In the actual implementation process, the steps may not be implemented in the order of the above steps, and the steps may be selectively re-combined and implemented in the order as required. For example, a group message session interface of a certain group may be displayed first, and when a group session message is received, if the group identification information of the group session message matches the group identification information of the group message session interface, the group session message is displayed on the group message session interface; for another example, the social application client may also obtain group information of an application group of a third party to which the user belongs in advance, where the group information includes a group name and/or a group profile, and then locally store a corresponding relationship between the group identification information and the group information, so that the corresponding group information may be matched and obtained from the locally stored corresponding relationship according to the group identification information.

Referring to fig. 7, it shows a group message session interface 70 of a social application client applied to a mobile terminal, where the group message session interface 70 is implemented according to the method provided in the above-mentioned embodiment of the group session message presentation method.

The "fun game and carefree clan" shown in the title area 71 is a combination of an application name and a group name, wherein the "fun game" is an application name of a third party application to which the group belongs, and the "carefree clan" is a group name of the group, and the application name and the group name are separated by a "·" symbol.

The conversation region 72 shows group conversation messages in the group, and only four group conversation messages are shown as an example, wherein the nickname of the user of the first group conversation message sender is "happy zhang san", the user head is shown as an icon 721, and the message content is text message content; the nickname of the user of the second group session message sender is "happy lie four", the avatar of the user is shown as an icon 722, and the message content is text message content; the nickname of the user of the third group session message sender is 'optimistic king five', the head portrait of the user is shown by an icon 723, and the message content is a picture; the third group session message is sent by the current login user of the social application client, the nickname of the current user is 'active old wind', the head image of the user is shown by an icon 724, and the message content is text message content; the nicknames and user head portraits of the users shown in the four group session messages are the nicknames and the user head portraits of the users on the third-party application 'happy game', namely the displayed nicknames and the user head portraits of the users are the nicknames and the user head portraits of the users registered in the third-party application server by the corresponding group members.

In summary, in the method provided in this embodiment, in the displayed group message session interface, the group members in the displayed group session message are displayed according to the user attribute information of the group members at the third-party application server, so that in the communication process of the group session message, the group members can hide the identity information of the group members in the social network application, and can recognize each other based on the identity information of the group members at the third-party application server, thereby enhancing the support of the social network application on the group session message by the third-party application.

Sixth, a group display method embodiment

The social application service end may provide the social application group service, or may not provide the social application group service, and the embodiments of the present invention are not limited thereto. If the social application server provides the social application group service, since the social application server in the embodiments of the present invention provides the third-party application group service, the group to which the user belongs includes both the social application group and the third-party application group, and if all the groups are displayed on one interface, confusion between the social application group and the third-party application group may be caused, so that the user cannot effectively distinguish the social application group from the third-party application group, and even the experience of the user in using the social application group may be affected by the use of the third-party application group.

Referring to fig. 5, a flowchart of an embodiment of a group display method provided by the present invention is shown. The embodiment is exemplified by applying the method to the social application client in the implementation environment shown in fig. 1, and the method may include:

and 501, acquiring group information of at least one part of third-party application groups to which the user belongs from a social application server side, and acquiring application information of third-party applications to which each group in the at least one part of third-party application groups belongs.

After a user logs in a social application server through a social application client, group information of at least one part of third-party application groups to which the user belongs is obtained from the social application server, and application information of third-party applications to which each group in the third-party application groups belongs is obtained, wherein the third-party application groups are groups for providing group services for the third-party applications.

The at least part of the third-party application group refers to a part of or all of the third-party application group to which the user belongs.

The group information of each group comprises the group name or/and the group profile of the group. For example, the social application server obtains a social user account of the user, obtains group identification information of at least a part of or all groups from a third-party application group list to which the social user account belongs, and then obtains corresponding group information according to each group identification information and returns the corresponding group information to the social application client.

The application information of the third-party application to which each group belongs comprises an application name or/and an application icon or/and an application profile. For example, the social application server side acquires a third-party application identifier according to each group identifier information, acquires corresponding application information according to the third-party application identifier, and returns the application information to the social application client side; for another example, the group information returned by the social application server further includes a third-party application identifier, where the third-party application identifier is used to indicate a third-party application to which the group belongs, and the social application client queries and acquires application information from the social application server according to the third-party application identifier.

And 502, displaying a group display interface, and displaying the group information and the application information on the group display interface.

The social application client displays a group display interface, which is an interface for displaying a third-party application group.

And displaying the group information and the application information on the group display interface, specifically, displaying the group information and the application information of at least one part or all of the at least one part of the third-party application group.

Further, a title area is displayed on the group display interface, and a title is displayed in the title area, wherein the title represents that the group display interface is a group for a third-party application. For example, the title is "third party application group" or "third party service group", etc., which means that the group display interface is a group for third party applications.

Further, the group information and the application information of each group are displayed on the group display interface according to groups. It can be understood that, in an actual application, the social application server may return, to the social application client, information of each group by group, including group information of the group and application information of a third-party application to which the group belongs, and may further include group identification information of the group, and the like, so that the social application client may display the group information and the application information of each group by group. For example, the group information of each group and the application information of the third-party application to which the group belongs are shown in a list form, that is, each list shows the group information and the application information of one group.

Further, on the group display interface, an area for each group is generated, and the group information and the application information of the group are displayed in the area of each group. For example, a first area shows group information and application information for a first group, a second area shows group information and application information for a second group, and so on.

Further, the area of each group is divided into two sub-areas, wherein one sub-area displays the application information of the third-party application to which the group belongs, and the other sub-area displays the group information of the group. For example, the left sub-area displays application information of a third-party application to which the group belongs, and the right sub-area displays group information of the group.

In practical application, the social application client receives the group session messages from the social application server, and the last group session message of each group is displayed on the group display interface. For example, the last group session message of the group may be displayed in the another sub-area, where the group session message includes a message sender and a message content, and the message sender displays user attribute information (e.g., a user name) of the sender of the group session message on the third-party application server. Generally, the last group session message refers to the last group session message in time sequence within the same group.

It should be noted that the above-mentioned sequence of steps is only used for illustration, and in practical applications, the steps may not be executed in the sequence. For example, a group interface may be displayed first, then group information and application information may be acquired, and then the group information and the application information may be displayed on the group interface; for another example, the social application client may periodically obtain group information and application information of a third-party application group to which the user belongs, and when the group information is updated, the group information and the application information of each group are refreshed on the group display interface.

Referring to fig. 8, a group presentation interface of a social application client applied to a mobile terminal is shown according to the method provided in this embodiment, where the group presentation interface 80 is implemented according to the method provided in the above embodiment of the group presentation method.

The title displayed in the title area 81 is "third party application group", which means that the group display interface 80 is a group display interface for displaying the third party application group.

In the group display area 82, at least a part of the third party application groups to which the user belongs are displayed in groups, for example, only seven groups are displayed, and taking the first group as an example, the icon 821 displays application icons of the third party applications to which the first group belongs, "group name one" is the group name of the group, "sender one: the latest message content "shows the last group session message of the group, wherein" sender one "is the user name of the group session message sender at the third party application server, and" the latest message content "is the message content of the group session message. The group display modes of the other six groups are the same or similar, and are not described herein again.

In summary, in the method provided in this embodiment, a dedicated interface is used to display the third-party application group to which the user belongs, so that the user can respectively display the social application group and the third-party application group to which the user belongs on different interfaces, and the experience of the user using the existing social application group is not affected.

Seventh, a group detail display method embodiment

Referring to fig. 6, a flowchart of an embodiment of a group detail display method provided by the present invention is shown. The embodiment is exemplified by applying the method to the social application client in the implementation environment shown in fig. 1, and the method may include:

and 601, acquiring group information of a designated group from the social application server side, wherein the designated group is a group for a third-party application.

After a user logs in the social application server through the social application client, the social application client acquires group information of a designated group from the social application server, wherein the designated group is a group for a third-party application.

Specifically, the social application client sends a request for obtaining group information to the social application server, where the request includes the group identification information of the specified group, and after receiving the request, the social application server obtains the corresponding group information according to the group identification information and returns the group information to the social application client.

The group information may include a group name or/and a group profile.

Further, application information of the third-party application to which the designated group belongs may be acquired, and the application information includes an application name or/and an application icon or/and an application profile. For example, when the third-party application is registered at the social application service side, the social application service side establishes a corresponding relationship between the third-party application identifier of the third-party application and the application information, and the social application service side can acquire the third-party application identifier to which the specified group belongs according to the group identifier information, then acquire the application information corresponding to the third-party application identifier, and return the application information to the social application client side.

And step 602, acquiring user attribute information of at least one part of group members in the specified group on a third-party application server, wherein the third-party application server is a server of a third-party application to which the specified group belongs.

At least a part of the group members in the designated group may be a part of the group members in the designated group, or all the group members in the designated group.

Because the designated group is a group for the third-party application, and the group member of the designated group is also a user of the third-party application, the social application client may obtain user attribute information of the group member on the third-party application server, where the user attribute information may include a user name or/and a user avatar, and the third-party application server is a server of the third-party application to which the designated group belongs.

Specifically, the obtaining, by the social application client, the user attribute information of at least a part of group members in the specified group on the third-party application server may include various embodiments, which specifically include:

in a first embodiment, the user attribute information of at least a part of group members is obtained from the social application server, and the user attribute information of at least a part of group members is obtained from the third-party application server by the social application server according to the social user accounts of at least a part of group members.

If the user is added into the group by adding the social user account in the group member list, the social application server side acquires the social user accounts of at least part of group members from the group member list of the specified group; if the user is added to the group by adding the group member account in the group member list, the social application server side obtains the group member accounts of at least part of group members from the group member list of the specified group, and then obtains the social user accounts of at least part of group members according to the group member accounts of the at least part of group members.

The social application server side obtains the third-party application identification to which the specified group belongs, for example, the third-party application identification is obtained according to the group identification information; and the social application server side determines a third-party application server side according to the third-party application identifier.

And the social application server side acquires the user attribute information of at least part of the group members from the third-party application server side according to the social user accounts of at least part of the group members, and forwards the user attribute information of at least part of the group members to the social application client side.

Accordingly, the social application client receives and obtains user attribute information of the at least a portion of the group members.

In a second embodiment, a request address and the application user accounts of at least a part of group members are obtained from the social application server, and user attribute information of at least a part of group members is obtained according to the application user accounts of at least a part of group members and the request address, where the request address is a request address used by the third-party application server to provide the user attribute information.

If the user is added into the group by adding the social user account in the group member list, the social application server side acquires the social user accounts of at least part of group members from the group member list of the specified group; if the user is added to the group by adding the group member account in the group member list, the social application server side obtains the group member accounts of at least one part of group members from the group member list of the specified group, and then obtains the social user accounts of at least one part of group members according to the group member accounts of at least one part of group members.

And the social application server side acquires the third-party application identifier to which the specified group belongs, for example, the corresponding third-party application identifier is acquired according to the group identifier information.

The social application server side determines the application user accounts of at least part of the group members according to the social user accounts of at least part of the group members and the third-party application identification, and determines a request address of the third-party application server side for requesting to acquire user attribute information according to the third-party application identification.

And the social application server side sends the request address and the application user accounts of at least one part of the group members to the social application client side.

Correspondingly, the social application client receives and acquires the request address and the application user account of at least part of the group members; and the social application client acquires the user attribute information of at least part of the group members from the third-party application server according to the application user accounts of the at least part of the group members and the request address.

It can be understood that, the social application server obtains at least a part of group member accounts of the group members from the group member list of the designated group, may obtain all group member accounts in the group member list of the designated group, or obtain a part of group member accounts in the group member list of the designated group according to a certain condition, for example, obtain the group member accounts of the designated number in the group member list in sequence.

In a third embodiment, a request address and the social user accounts of at least a part of group members are obtained from the social application server, and user attribute information of the at least a part of group members is requested to be obtained from the request address according to the social user accounts, where the request address is a request address used by the third-party application server to provide the user attribute information.

If the user on the third-party application server binds a social user account in advance, the social application client may obtain a request address and the social user accounts of the at least part of group members from the social application server, and request the request address to obtain the user attribute information of the at least part of group members according to the social user accounts, where the request address is a request address for providing the user attribute information by the third-party application server. In a specific implementation manner, reference may be made to the second implementation manner, where the social user account is used to replace the application user account for making a request, and a request address is an address where information of a user on the third-party application server can be queried according to the social user account, which is not described herein again.

And 603, displaying a group detail interface, and displaying the group information and the user attribute information of the at least part of group members on the group detail interface.

Displaying a group detail interface, and displaying the group information and the user attribute information of at least a part of group members on the group detail interface, wherein the displayed user attribute information of at least a part of group members may be the user attribute information of all group members in the at least a part of group members, or may be displayed and viewed on the social application client conveniently, so as to avoid inconvenient viewing due to display of a large number of group members, or may only display the user attribute information of a part of group members in the at least a part of group members, for example, limiting the number of displays to be not more than 10, and omitting the user attribute information of more group members in the form of ellipses.

A group detail display interface which can be triggered and displayed in response to the selection operation of the designated group in the group display interface; or the group search method can be triggered and displayed in response to the selection operation of the searched group when the user searches the group on the social application client.

The above sequence of steps is only for example, and in practical applications, the steps may not be performed in the sequence. For example, step 601 and step 602 may be implemented in the same step, that is, when the social application client obtains group information of a specified group from the social application server, the social application server returns the group information of the specified group, and simultaneously returns user attribute information of at least a part of group members in the specified group on the third-party application server; for another example, the social application client displays a group detail interface, then performs

steps

601 and 602 to obtain the group information and the user attribute information of the at least a part of group members, and then displays the group information and the user attribute information of the at least a part of group members on the group detail interface.

Referring to fig. 9, it shows a group detail interface 90 of a social application client applied to a mobile terminal according to an embodiment of the present invention, where the group detail interface 90 is implemented according to the method described in the above embodiment of the group detail display method.

The title displayed in the title area 91 is "third party application group details", which indicates that the group display interface 90 is a group details interface for displaying a third party application group.

Displaying group members in a group member area 92, wherein each group member displays a user head portrait and a user name of the group member, and the user head portrait and the user name are the user head portrait and the user name of the group member on a third-party application server; the number of displayed group members is limited to be not more than 10 groups, and more group members can be further acquired by 'viewing all group members'.

The group name of the current group is shown in the group name area 93, and the group name is "carefree tribe group".

A group profile for the current group, i.e., for the "wordless groups," is presented in group profile area 94.

The application name of the third party application to which the current group belongs is shown in the belonging application area 95, and the application name is "happy game".

An application profile for the third party application to which the current group belongs, i.e. for the "fun game", is presented in the application profile area 96.

In summary, in the method provided in this embodiment, the group information of the designated third-party application group and the user attribute information of the group member of the group are displayed on the displayed group detail interface, so that the group detail of the designated third-party application group can be obtained in time through the group detail interface, and the user attribute information of the group member in the third-party application is displayed, so that the group member can be identified by the identity information of the group member in the third-party application.

It should be noted that, in this document, the terms "comprises," "comprising," "includes," "passing," "sending," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system.

The terms "first," "second," "third," and the like (if any) are used solely to distinguish one from another and are not used to describe a particular order or sequence. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein.

The numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

The method and client, server and system of the present invention can be implemented in many ways. For example, the method, client, server and system of the present invention can be implemented by software, hardware, firmware or any combination of software, hardware and firmware. The above-described order for the steps of the method is for illustrative purposes only, and the steps of the method of the present invention are not limited to the order specifically described above unless specifically indicated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as a program recorded in a recording medium, the program including machine-readable instructions for implementing a method according to the present invention. Thus, the present invention also covers a recording medium storing a program for executing the method according to the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A method for providing group service for third-party application is applied to a social application server side, and comprises the following steps:

for a user to join the group, acquiring the third-party application identifier according to the group and the setting, and determining whether the user is a user on a third-party application server according to the social user account of the user, wherein the third-party application server is a third-party application server corresponding to the third-party application identifier;

if so, adding the user into the group according to the social user account so that the user can interact in the group through a social application client;

determining whether the user is a user on a third-party application server according to the social user account of the user comprises:

querying the social user account from the third-party application server to determine whether the user is a user on the third-party application server; alternatively, the first and second liquid crystal display panels may be,

2. The method of claim 1, wherein the setting the identifier of the third-party application to which the group belongs comprises:

the attribute information of the group comprises an attribute used for indicating a third-party application, and an attribute value of the attribute is set as the third-party application identifier.

3. The method of claim 2, wherein associating the group identification information for the group with the third party application identification comprises:

4. The method of claim 1, wherein the obtaining the third-party application identifier according to the group and the setting comprises:

and receiving group identification information sent by the user through a social application client, wherein the group identification information indicates that the user is to join the group, and acquiring the third-party application identification according to the group identification information and the setting.

5. The method of claim 1, wherein querying the application user account with the third-party application server to determine whether the user is a user on the third-party application server comprises:

receiving feedback information of the third-party application server side;

6. The method of claim 1, wherein the joining the user to the group according to the social user account comprises:

7. The method of claim 6, wherein adding the social user account to the group member list of the group further comprises:

and determining a group member account according to the social user account and the third party application identifier, and acquiring the social user account according to the group member account.

8. The method of claim 6 or 7, wherein determining group member accounts according to the social user account and the third party application identifier comprises:

acquiring the group member account in a pre-established corresponding relation according to the social user account and the third party application identifier; alternatively, the first and second electrodes may be,

9. The method of claim 8, wherein obtaining the group member account in a pre-established correspondence according to the social user account and the third party application identifier comprises:

10. The method of claim 8, wherein the generating the group member account encrypted according to the social user account and the third party application identifier comprises:

generating a hash value according to the social user account;

11. The method of claim 1, further comprising:

sending the user attribute information of the user on the third-party application server side to group members of the group according to the social user account; and/or the first and/or second light sources,

12. The method of claim 11, wherein sending the user attribute information of the user on the third-party application server to the group members of the group according to the social user account comprises:

13. The method of claim 11, wherein the obtaining user attribute information of the user on the third-party application server according to the social user account comprises:

inquiring the social user account from the third-party application server to acquire the user attribute information; alternatively, the first and second electrodes may be,

and determining an application user account according to the social user account and the third-party application identifier, and inquiring the application user account from the third-party application server to acquire the user attribute information.

14. The method of claim 11, wherein the user attribute information comprises one or more of a user name, a user avatar, a gender, an age, a birthday, a location, and a personality signature.

15. The method of claim 1, 12 or 13, wherein the determining an application user account from the social user account and the third party application identifier comprises:

acquiring the application user account in a pre-established corresponding relation according to the social user account and the third-party application identifier; alternatively, the first and second electrodes may be,

16. The method of claim 15, wherein the generating the application user account based on the social user account and the third party application identification encryption comprises:

17. The method according to claim 11, wherein the group information comprises a group name or/and a group profile.

18. The method according to claim 11, characterized in that the application information comprises an application name or/and an application icon or/and an application profile.

19. The method of claim 1, wherein creating the group further comprises, prior to:

and acquiring the third party application identifier according to the creation request.

20. The method of claim 19, wherein the obtaining the third-party application identifier according to the creation request comprises:

the creation request comprises associated information, and the third-party application identifier is obtained from a pre-established association relationship between the associated information and the third-party application identifier according to the associated information; or/and (c) the first and/or second,

21. The method of claim 19, wherein if the sender is a social application client, then after obtaining the third-party application identifier according to the creation request and before creating the group, further comprising:

if yes, executing the step of creating the group.

22. The method of claim 21, further comprising:

if yes, executing the step of creating the group.

23. The method of claim 20, wherein the sender is a social application client, and wherein the creating a group further comprises:

and adding the sender to the group according to the social user account of the sender.

24. The method of claim 19, wherein the creating a group further comprises:

25. The method of claim 24, wherein the group information comprises a group name and/or a group profile.

26. A group message session display method is applied to a social application client of a message receiver, and comprises the following steps:

receiving a group session message forwarded by a social application server, wherein the group session message comprises group identification information and message content, the group is established on the social application server, the group is used for interaction among users of third-party applications through a social application client, the group session message is a message sent to the social application server by a social application client of a message sender, the message sender and the message receiver are both group members of the group, and the social application client of the message receiver and the social application client of the message sender are both social application clients corresponding to the social application server;

acquiring user attribute information of the message sender on a third-party application server, wherein the third-party application server is a server of third-party application to which the group indicated by the group identification information belongs;

27. The method of claim 26, wherein obtaining the user attribute information of the message sender on the third-party application server comprises:

receiving user attribute information sent by the social application server, wherein the user attribute information is acquired from the third-party application server by the social application server according to a social user account of the message sender; alternatively, the first and second electrodes may be,

receiving a request address sent by the social application server and a social user account of the message sender, and requesting the request address to acquire the user attribute information according to the social user account, wherein the request address is a request address used by the third-party application server for providing the user attribute information; alternatively, the first and second liquid crystal display panels may be,

28. The method according to claim 26, wherein the user attribute information comprises a user name or/and a user avatar.

29. The method of claim 26, further comprising:

acquiring an application name of a third-party application to which the group indicated by the group identification information belongs, and displaying the application name on the group message session interface; or/and (c) the first and/or second,

30. The method of claim 29, wherein the obtaining the application name of the third-party application to which the group indicated by the group identification information belongs comprises:

31. The method of claim 29, wherein the obtaining the group name of the group comprises:

32. The method of claim 29, wherein the application name and the group name are exposed in a header area of the group message session interface.

33. A group display method is applied to a social application client, and a user logs in the social application client, and the method comprises the following steps:

the method comprises the steps that group information of at least one part of third-party application groups to which users belong is obtained from a social application server, and application information of third-party applications to which each group belongs in the at least one part of third-party application groups is obtained, wherein each group is a group established on the social application server, and is a group which is used for interaction between the users of the third-party applications to which each group belongs through a social application client;

displaying a group display interface, and displaying the group information and the application information on the group display interface, wherein the group display interface is used for displaying a third-party application group, and is different from an interface for displaying a social application group.

34. The method according to claim 33, wherein the group information comprises a group name or/and a group profile.

35. The method according to claim 33, wherein the application information comprises an application name or/and an application icon or/and an application profile.

36. The method of claim 33, further comprising:

37. The method of claim 33, wherein the presenting the group information and the application information on the group presentation interface comprises:

38. The method of claim 37, wherein said presenting group information and application information for each group by group comprises:

and generating an area for each group according to each group, and respectively displaying the group information and the application information of each group in the area of each group.

39. The method of claim 38, further comprising:

and dividing the area of each group into two sub-areas, wherein one sub-area displays the application information of the group, and the other sub-area displays the group information of the group.

40. The method of claim 39, further comprising:

41. The method of claim 33, further comprising:

42. The method of claim 41, wherein the last group session message of each group comprises a message sender and a message content.

43. The method of claim 42, wherein the message sender is user attribute information of the sender of the last group session message on a third-party application server, and the third-party application server is a server of a third-party application to which a group of the last group session message belongs.

44. The group detail display method is applied to a social application client, and comprises the following steps:

acquiring group information of a designated group from a social application server, wherein the designated group is a group established on the social application server and is a group used for interaction among users of third-party applications through a social application client;

45. The method of claim 44, wherein the group information comprises a group name and/or a group profile.

46. The method of claim 44, further comprising

And acquiring application information of the third-party application to which the designated group belongs from the social application server, and displaying the application information on the group detail interface.

47. The method according to claim 46, wherein the application information comprises an application name or/and an application icon or/and an application profile.

48. The method of claim 44, wherein the obtaining of the user attribute information of at least a part of the group members in the designated group on the third-party application server side comprises:

49. The method according to claim 44, wherein the user attribute information comprises a user name or/and a user avatar.

50. The method of claim 44, wherein the display group details interface is displayed in response to a selection operation of the specified group in a group presentation interface.

51. A social application server, comprising: processor, memory and a computer program stored on the memory and executable on the processor, characterized in that the computer program realizes the method according to any of claims 1 to 25 when executed by the processor.

52. A social application client, comprising: processor, memory and a computer program stored on the memory and executable on the processor, characterized in that the computer program implements the method according to any of claims 26 to 32 when executed by the processor, or/and the computer program implements the method according to any of claims 33 to 43 when executed by the processor, or/and the computer program implements the method according to any of claims 44 to 50 when executed by the processor.

53. The system is characterized by comprising a social application server and a social application client;

the social application server comprises the social application server of claim 51;

the social application client comprises the social application client of claim 52.

54. A storage medium, characterized in that the storage medium has stored therein a program for implementing a method comprising any one of claims 1 to 25.

55. A storage medium having stored thereon a program for implementing a method comprising any of claims 26 to 32, or/and a program for implementing a method comprising any of claims 33 to 43, or/and a program for implementing a method comprising any of claims 44 to 50.