CN111522604A - Application data processing method and device and computer readable storage medium - Google Patents

Abstract

The application discloses an application data processing method, an application data processing device and a computer readable storage medium, wherein the method comprises the following steps: responding to conference entering operation aiming at a target conference in the first application, and acquiring an application installation state of the second application; the target conference is initiated through the second application; when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation; in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation; and entering the target conference in the second application according to the conference detail information. By the adoption of the method and the device, the entering efficiency aiming at the target conference can be improved.

Description

Application data processing method and device and computer readable storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing application data, and a computer-readable storage medium.

Background

With the continuous development of computer networks, users can also participate in conferences in a cloud conference mode.

In the prior art, when terminal z1 creates a conference in application y1, terminal z1 may recommend the created conference to terminal z2 through application y2, for example, send a link of the conference to application y2 in terminal z 2. The terminal device z2 can copy the link of the conference in the application y2, open the application y1 again, and paste the copied link of the conference into the started application y1 to enter the conference.

However, in the above process, since the terminal device z2 needs to copy the link of the meeting to the system clipboard before opening the application y1, if the terminal device z2 copies another text message to the system clipboard at this time, this text message will overwrite the link of the meeting originally existing in the system clipboard. Thus, when terminal device z2 reopens application y1, no link to the meeting has been found in the system clipboard. The terminal device z2 again needs to reopen the application y2, copy the conference link again in application y2 and paste into application y1 to enter the conference.

Therefore, in the prior art, the process of entering the conference in the application y2 through the third-party application (the application y1) is complicated, and the entering efficiency of the conference is low.

Disclosure of Invention

The application provides an application data processing method, an application data processing device and a computer readable storage medium, which can improve the entrance efficiency aiming at a target conference.

One aspect of the present application provides an application data processing method, including:

responding to conference entering operation aiming at a target conference in the first application, and acquiring an application installation state of the second application; the target conference is initiated through the second application;

when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation;

in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation;

and entering the target conference in the second application according to the conference detail information.

One aspect of the present application provides an application data processing apparatus, including:

the conference joining response module is used for responding to conference joining operation aiming at the target conference in the first application and acquiring the application installation state of the second application; the target conference is initiated through the second application;

the installation module is used for installing the second application when the application installation state is the application uninstallation state and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation;

the detail obtaining module is used for obtaining meeting detail information corresponding to the meeting identification according to the identification mapping relation in the second logged application;

and the conference entering module is used for entering the target conference in the second application according to the conference detail information.

An aspect of the application provides a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform a method as in an aspect of the application.

An aspect of the application provides a computer-readable storage medium having stored thereon a computer program comprising program instructions which, when executed by a processor, cause the processor to perform the method of the above-mentioned aspect.

The method and the device can respond to conference joining operation aiming at the target conference in the first application, and obtain the application installation state of the second application; the target conference is initiated through the second application; when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation; in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation; and entering the target conference in the second application according to the conference detail information. Therefore, the method provided by the application can automatically acquire the conference detail information aiming at the target conference after the second application is installed and logged in, and quickly enter the target conference according to the conference detail information, so that the entry efficiency aiming at the target conference after the second application is logged in is improved.

Drawings

In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings needed for the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of a system architecture provided herein;

fig. 2a is a schematic page diagram of a terminal device provided in the present application;

fig. 2b is a schematic page diagram of a terminal device provided in the present application;

FIG. 3 is a flow chart illustrating an application data processing method provided herein;

fig. 4 is a schematic page diagram of a terminal device provided in the present application;

fig. 5 is a schematic page diagram of a terminal device provided in the present application;

FIG. 6 is a flow chart illustrating an application data processing method provided herein;

FIG. 7 is a flow chart illustrating an application data processing method provided herein;

FIG. 8 is a schematic diagram of a scenario of application data processing provided herein;

FIG. 9 is a schematic diagram of an application data processing apparatus provided in the present application;

fig. 10 is a schematic structural diagram of a computer device provided in the present application.

Detailed Description

The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings in the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Please refer to fig. 1, which is a schematic diagram of a system architecture provided in the present application. As shown in fig. 1, the system architecture diagram may include a plurality of terminal devices including aterminal device 200a, aterminal device 200b, and aterminal device 200c, and a plurality of servers. The plurality of servers includesserver 100,server 200, andserver 300. Theterminal device 200a, theterminal device 200b and theterminal device 200c can communicate with each server, and the servers can communicate with each other. The terminal device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable device (e.g., a smart watch, a smart bracelet, etc.), and the like. Here, the communication between theterminal device 200a, theterminal device 200b, and the plurality of servers is taken as an example for explanation, and please refer to the following procedure.

Please refer to fig. 2a, which is a schematic page diagram of a terminal device provided in the present application. As shown in fig. 2a, theterminal device 200a is a terminal device held by a user bean, and an application Y1 may be installed in theterminal device 200a, where the application Y1 may be any communication type application, and the application Y1 has a function of creating a conference, where the conference may be a video conference or a voice conference. Theterminal page 100a of theterminal device 200a is a page of a conference created by the user kidney bean through the application Y1 in theterminal device 200a, and as seen from theterminal page 100a, the users currently participating in the conference include the user kidney bean and the user music. Theterminal device 200a further supports that the user beans can invite other users to participate in the conference, where the inviting mode may be a two-dimensional code inviting mode, and may be: theterminal device 200a may jump to thedisplay terminal page 101a in response to a click operation of the user bean on the "invite to participate"button 100b in theterminal page 100 a. Alternatively, theterminal page 101a may be a sub-page independently displayed on theterminal page 100 a.

Theterminal page 101a includes aninvitation picture 101b of the meeting, and theinvitation picture 101b includes details of the meeting (i.e., "bean-initiated meeting starts at 9: 00") and a two-dimensional code 104b of the meeting. The two-dimensional code 104b includes a web address for entering the conference. Also included interminal page 101a are a "forward to chat"button 120b, a "share to application Y2" button, and a "save as picture"button 121 b. Theterminal device 200a may share theinvitation picture 101b in theterminal page 101a to a friend in the address book of the user kidney bean in the application Y1 in response to a click operation of the user kidney bean on the "forward to chat"button 120b in theterminal page 101 a. Theterminal device 200a may also output theinvitation picture 104b in theterminal page 101a in response to a click operation of the user bean on the "save as picture"button 121b in theterminal page 101a, and store it in the local album of theterminal device 200 a.

Theterminal device 200a may further include an application Y2, the application Y2 may be any communication application, the application Y1 is a different application from the application Y2, and the application Y2 has functions of receiving and transmitting a message. Here, in response to the click operation of the user bean on the "share to application Y2" button in theterminal page 101a, theterminal apparatus 200a starts the application Y2 in theterminal apparatus 200 a. Theterminal apparatus 200a supports the user bean to select a friend who wants to invite to participate in the conference in the address book of the launched application Y2, here, it is assumed that the user bean selects much friends in the address book of the application Y2. Theterminal device 200a may send theinvitation picture 101b in theterminal page 101a to the user in the application Y2, and jump to display theterminal page 102 a. Theterminal page 102a is a chat page of how many friends the user bean has with in the application Y2 in theterminal device 200a, as shown by theterminal page 102a, how many friends the user bean has successfully sent amessage 103b containing theinvitation picture 101b to. It is also the main description of the present application that how many users participate in a conference through a third party application, here application Y2, is described below.

Please refer to fig. 2b together, which is a schematic page diagram of a terminal device provided in the present application. As shown in fig. 2b, theterminal device 200b is a terminal device that is owned by many users (i.e., many friends in the address book of the application Y2 of the above-mentioned user bean). Theterminal device 200b may also have an application Y2 installed therein, aterminal page 103a of theterminal device 200b is a chat page where the user mostly chats with his friend bean in the application Y2 (i.e., the user bean), as shown by theterminal page 103a, the user mostly receives amessage 103b sent by his friend bean, themessage 103b includes aninvitation picture 101b of the meeting, and theinvitation picture 101b includes a two-dimensional code 104b of the meeting. Theterminal device 200b may respond to a long-press operation of the two-dimensional code of the conference in themessage 103b in theterminal page 103a, which is more specific to the user, identify a website included in the two-dimensional code of the conference, and jump to and display theterminal page 104a, which is equivalent to that theterminal device 200b opens a link, and the link is the website obtained by identifying the two-dimensional code of the conference. The operation of theterminal device 200b to open the website included in the two-dimensional code of the conference may be implemented by accessing a page server, where the page server may be an h5 server, and the page server may be theserver 200. Aconference portal page 106b is included in theterminal page 104 a. Meeting details for the meeting (i.e., "bean initiated meeting the meeting starts meeting presenter: music at 9: 00") and "open application Y1, join meeting"button 107b are included in meetingentry page 106 b.

Theterminal apparatus 200b may start the application Y1 by calling the external application interface registered by the application Y1 in theterminal apparatus 200b by the application Y2 in response to a click operation of the user with respect to thebutton 107b in theconference portal page 106b more. When the launch of the application Y1 fails, indicating that the application Y1 is not installed in theterminal apparatus 200b, theterminal apparatus 200b may jump to display to theterminal page 105 a. Theterminal device 200b may further obtain a conference identifier of the conference from the website obtained by identifying the two-dimensional code 104b of the conference, where the conference identifier is an ID (identity) for uniquely identifying one conference. Therefore, when theterminal device 200b detects that the application Y1 is not installed, in addition to jumping to theterminal page 105a, it may synchronize the account id (here, account id 1) of the user account registered in the application Y2 by the user and the conference id of the conference acquired from the web address included in the two-dimensional code of the conference to theserver 100. Here, theserver 100 is used as a background server of the application Y1, that is, when theterminal device 200b detects that the application Y1 is not installed, theterminal device 200b may synchronize the account identifier 1 and the session identifier to theserver 100. Theserver 100 may store the acquired account id 1 and the conference id in association, which may be understood as storing a mapping relationship between the account id 1 and the conference id. Theterminal device 200b transmits the account id 1 and the meeting identifier to theserver 100, so that theserver 100 can associate the process of storing the account id 1 and the meeting identifier without sensing how many users are.

More, aprompt box 108b is displayed in theterminal page 105a, and theprompt box 108b includes a prompt message "prompt: you do not install application Y1! "," click download "button 109b, and" cancel "button. Theterminal device 200b may display theterminal page 106a in response to a click operation of the user with respect to the "click download"button 109b in theterminal page 105 a. Theterminal page 106a is a download page for the application Y1, and the operation of theterminal device 200b jumping to display to theterminal page 106a may be implemented by a software server, which may be theserver 300 described above, being a server that provides the user with an installation package service of the downloaded application. Theterminal apparatus 200b can download the application installation package of the application Y1 in response to a click operation of the user with respect to the "click download install"button 110b in theterminal page 106a, and theterminal apparatus 200b can install the application Y1 by the downloaded application installation package.

When the installation of the application Y1 by theterminal apparatus 200b is completed, the application Y1 may be launched and theterminal page 107a may be displayed. Theterminal page 107a is a page for registering or logging in the application Y1, and supports a user to log in by inputting an account and a password registered in the application Y1 or by a third-party application in theterminal page 107 a. Here, the third party application for the application Y1 may refer to the application Y2 and the application Y3, login or registration of the application Y1 through the application Y2 may be achieved through thebutton 111b in theterminal page 107a, and login or registration of the application Y1 through the application Y3 may be achieved through thebutton 122b in theterminal page 107 a. Here, theterminal apparatus 200b can log in or register the application Y1 using the application Y2 in response to a click operation of the user with respect to thebutton 111b in theterminal page 107a more.

If the application Y1 is logged in through the application Y2, it indicates that the application Y1 has been registered in advance through the user account which is registered in the application Y2 by the majority of users. When the application Y1 is registered through the application Y2, a mapping account id corresponding to the account id 1 is obtained through account ids of user accounts (that is, the account id 1) obtained by registering a large number of users in the application Y2, where the mapping account id is an account id of a user account obtained by registering a large number of users in the application Y1 through the application Y2, in other words, the mapping account id is an account id of a user account registered in the application Y1 a large number of users. Therefore, if the user mostly registers the application Y1 through the application Y2, theserver 100 inevitably stores the mapping relationship between the account id 1 and the corresponding mapping account id. Therefore, theterminal device 200b can log in to the application Y1 using the account id of the user account registered by the application Y2 (i.e., the above-described mapped account id) and jump to theterminal page 108a in response to a click operation of the user with respect to thebutton 111b in theterminal page 107 a. Theterminal page 108a is an application home page after logging in the application Y1.

The application home page of the application Y1 is displayed to indicate that login to the application Y1 is successful, and when theterminal device 200b detects that login to the application Y1 is successful through the mapping account identifier, the application Y1 may be triggered to generate the conference entering notification information. Theterminal device 200b may send the conference notification information generated by the application Y1 to theserver 100, where the conference notification information is generated by the application Y1 that is logged in through the mapping account id, and therefore the mapping account id is carried by the conference notification information. After acquiring the conference entrance notification information sent by theterminal device 200b, theserver 100 may find the account id 1 having a mapping relationship with the mapping account id through the mapping account id carried in the conference entrance notification information, and then, theserver 100 may also find the conference id having a mapping relationship with the account id 1, and finally, theserver 100 may acquire the conference detail information of the corresponding conference through the conference id. Theserver 100 may send the acquired meeting detail information to theterminal device 200b, and theterminal device 200b may display a full-screen meeting notification page according to the acquired meeting detail information, where the meeting notification page is theterminal page 109 a. The conference detail information "bean invites you to enter the conference host initiated by the conference bean" acquired by theterminal device 200b is displayed in theterminal page 109 a: happy participant: 2 people ",slider 112b and" enter temporarily "button 123 b. Through the above process, it can be known that, under the perception of the user being many, that is, shortly after the login to the application Y1 is successful and the application home page of the application Y1 in theterminal page 108a is displayed (for example, 0.1 second, 0.5 second, 1 second, or the like is separated), theterminal device 200b automatically displays theterminal page 109a in full screen in the application Y1.

Theterminal device 200b may respond to the operation that the user mostly drags theslider 112b in theterminal page 109a to the right, enter the meeting created by the user bean, and jump to display theterminal page 110a, where theterminal page 110a is a page of the ongoing meeting. As can be seen from the terminal page 11a, the users participating in the conference at this time include the user beans, the user abundance, and the user music. Theterminal device 200b can also return to theterminal page 108a in response to a click operation of the user with respect to the "enter temporarily"button 123b in theterminal page 109 a.

By the method provided by the application, when a certain conference (for example, conference 1) in the application Y1 is entered through a third-party application (for example, the application Y2 described above), and it is found that the application Y1 is not installed, the conference entrance notification page for the conference 1 can be automatically displayed immediately after the application Y1 is installed and the application Y1 is logged in subsequently, so that the user can quickly enter the conference 1 through the conference entrance notification page without searching a conference entrance for the conference 1 again, for example, without searching a two-dimensional code in an invitation picture of the conference 1 again (the two-dimensional code can be understood as a conference entrance of the conference), and then enter the corresponding conference through the searched conference entrance. Therefore, by the method, when the user reinstalls and logs in the application to which the conference belongs, the efficiency of the user entering the conference is improved, full-automatic notification of the conference is realized, and the conference entering experience of the user is improved.

Please refer to fig. 3, which is a schematic flowchart of an application data processing method provided in the present application, and as shown in fig. 3, the method may include:

step S101, responding to conference joining operation aiming at a target conference in a first application, and acquiring an application installation state of a second application; the target conference is initiated through the second application;

optionally, the execution main body in this embodiment may be any terminal device, and in this embodiment, the terminal device x is taken as an example for description. The terminal device x has a first application installed therein, where the first application may be any application that can receive a message, for example, the first application may be a communication type application (i.e., app), and the communication type application may refer to an application with a chat function. The second application may be any application that can initiate an online conference, where the online conference may be called a cloud conference or a conference for short, and the conference may be a video conference or a voice conference. The target conference is a conference created in the second application, and the target conference is created for another terminal device (assumed to be terminal device y) different from terminal device x. The terminal device y may have a second application installed therein, and the target conference may be created by the terminal device y through the installed second application. The terminal device x may obtain a conference entrance for the target conference sent by the terminal device y, where the conference entrance may be a jump website for the target conference or a two-dimensional code including the jump website for the target conference. The terminal device y sends a conference portal of the target conference created in the second application to the terminal device x through a third-party application (here, the third-party application is the first application), and this application also mainly describes a process how to enter the target conference created in the second application through the third-party application, please refer to the following process.

The following describes the procedure how terminal device y sends a conference portal for the target conference to terminal device x:

it is assumed that the terminal device y is a terminal device owned by the user y, and what is logged in the second application in the terminal device y is a user account registered by the user y in the second application. The terminal device y may create the target conference in the second application in response to a user operation of the user y. For example, a button or a function key for creating a conference may be provided in the second application, and the terminal device y may respond to a click operation of the user y on the button or the function key, so that the target conference may be created. And the terminal device y can respond to the clicking operation of the user y on the button to generate the invitation picture of the target conference. The invitation picture may include an identification code of a jumping website of the target conference and conference detail information of the target conference, and the invitation picture may be used as a conference entrance of the target conference. The identification code of the jumping website containing the target conference can be a two-dimensional code of the jumping website containing the target conference. The conference detail information of the target conference may include a conference name of the target conference, a creator of the target conference, a creation time of the target conference, a host of the target conference, and the like.

The process of generating the invitation picture of the target conference may be:

the background server of the second application may be referred to as the application server. First, the terminal device y may transmit a creation request for a target conference to the application server in response to a user operation of the user y. After acquiring the creation request for the target conference, the application server may generate a conference identifier of the target conference. The conference identifier of the target conference is a conference ID of the target conference, and is an identifier generated by the application server and used for uniquely identifying the target conference, where the conference identifier may be a character string, for example, the conference identifier may be 123, or the conference identifier may also be h12, and so on. The application server may send the generated conference identifier of the target conference to the terminal device y to notify the terminal device y that the target conference creation is successful, and the terminal device y may display a conference in-progress page for the target conference in the second application.

The in-progress conference page is a conference page of the target conference, the in-progress conference page may include a generation button of an invitation picture for the target conference, the terminal device y may respond to a click operation of the user y on the generation button, and send a generation request of the invitation picture for the target conference to a background server of the second application, and the generation request may carry a conference identifier of the target conference. After the application server obtains the request for generating the invitation picture for the target conference, the application server can generate a jumping website for the target conference according to the conference identifier of the target conference, and then the application server can generate the identification code of the target conference according to the jumping website. The identification code of the target conference can be a two-dimensional code, the two-dimensional code can be image data, the two-dimensional code comprises a jump website related to the target conference, and the jump website comprises a conference identification of the target conference.

After generating the identification code of the target conference, the application server may transmit the generated identification code of the target conference and the conference detail information of the target conference to the terminal device y. After acquiring the identification code of the target conference and the conference detail information of the target conference sent by the application server, the terminal device y may generate an invitation picture of the target conference according to the acquired identification code of the target conference and the conference detail information of the target conference, where the invitation picture includes both the identification code of the target conference and the conference detail information, for example, the invitation picture of the target conference may be theinvitation picture 101b in fig. 2 a.

Optionally, the invitation picture of the target conference may also be generated by the application server directly according to the identification code of the target conference and the conference detail information, in other words, the application server may directly send the invitation picture of the target conference to the terminal device y instead of sending the identification code of the target conference and the conference detail information.

It is assumed that the terminal device x is a terminal device held by the user x, and what is logged in the first application in the terminal device x is a user account registered by the user x in the first application. The terminal device y may respond to the user operation of the user y, and send the generated invitation picture of the target conference to the terminal device x through the first application. For example, a "share to first application" button may be provided in a generation page of an invitation picture in a second application of the terminal device y, and the terminal device y may respond to a click operation of the user y on the "share to first application" button and start a first application in the terminal device y through an application external interface of the first application in the terminal device y. And the user y is supported to find the user x in the address list in the started first application, and the user x is selected as a sending object of the invitation picture. Then, the terminal device y may send the invitation picture to the first application in the terminal device x held by the user x.

For another example, a "save to album" button may be provided in the generated page where the invitation picture in the second application of the terminal device y is located, and the terminal device y may derive the invitation picture of the target conference in response to the click operation of the user y on the "save to album" button, and save the derived invitation picture of the target conference to the local album of the terminal device y. After that, the terminal device y may start the first application in response to a start operation of the user y for the first application. And the user y is supported to expand a chat page with the user x in the started first application, select the saved invitation picture of the target conference from the local album of the terminal device y in the expanded chat page with the user x, and send the selected invitation picture to the user x as a chat message.

The application external interface (i.e., urlschema) of the first application in the terminal device y is obtained by being registered in the terminal device y when the first application is installed. It can be understood that each application installed in the terminal device may be correspondingly registered with an application external interface, and the application external interface is used for realizing mutual access between different applications in the terminal device. In other words, between different applications in the terminal device, the corresponding application can be accessed through the application external interface corresponding to each application.

Responding to the identification operation of the identification code aiming at the target conference in the first application to obtain a website identification result; acquiring meeting invitation information of a target meeting according to a meeting identifier in the website identification result; outputting a conference entrance page aiming at the target conference according to the conference invitation information; responding to the conference entrance page entrance operation, and acquiring the application installation state of the second application:

furthermore, the first application has a function of identifying a website address in an identification code (for example, a two-dimensional code), and after the terminal device x acquires the invitation picture sent by the terminal device y, the terminal device x may respond to a long-press operation of the user x on the identification code in the invitation picture in the first application to identify a jumping website address of the target conference included in the identification code. The identified jumping website of the target conference can be called a website identification result, and the website identification result includes a conference identifier of the target conference. The terminal device x can access a page server according to the jump website, where the page server can be an h5 server, where h5 is a set of technologies for creating a web page interaction effect, in other words, h5 is a web page of the mobile terminal. The h5 server may recognize the meeting identifier of the target meeting according to the jumping website, and request the meeting invitation information of the target meeting from the application server of the second application according to the meeting identifier, where the meeting invitation information may be the same as or different from the meeting detail information of the target meeting, and the meeting invitation information may include a creator, a creation time, a host, and the like of the target meeting.

The application server may transmit the conference invitation information of the target conference to the h5 server, and the h5 server may transmit the acquired conference invitation information of the target conference to the terminal device x. After acquiring the meeting invitation information of the target meeting, the terminal device x may display a meeting entry page for the target meeting to the invitation information according to the meeting, where the meeting entry page is an h5 page. The meeting entry page may include the meeting invitation information and may also include a portal for entering the target meeting, which may be a "start second application, enter target meeting" button, for example, the meeting entry page may be meetingentry page 106b in fig. 2 a.

Responding to conference entering operation aiming at a target conference in the first application, and starting the second application based on an application external interface of the second application; when the second application is failed to be started, acquiring an uninstalled state of the application; when the second application is started successfully, acquiring the installed state of the application:

the terminal device x may respond to a click operation of a button "start second application and enter target conference" in the conference entry page by the user x, and acquire an installation state of the second application in the terminal device x. The click operation of the button for "starting the second application and entering the target conference" in the conference entry page may be referred to as a conference entering operation for the target conference. The installation state of the second application includes an application installed state and an application uninstalled state, and the process of acquiring the installation state of the second application in the terminal device x may be:

the terminal device x may respond to the conference entering operation of the user x for the target conference in the first application, and start the second application through the external application interface registered in the terminal device x by the second application. When the second application is failed to be started in the terminal device x, it indicates that the second application is not installed in the terminal device x, and an application uninstalled state of the second application is obtained. And when the second application is successfully started in the terminal device x, indicating that the second application is installed in the terminal device x, and obtaining the application installation state of the second application.

Step S102, when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation;

optionally, when the installation state of the second application in the terminal device x is an application uninstallation state, the terminal device x may display an application download page in a terminal page. The application download page is a page of an application installation package for downloading the second application, and may also be an h5 page, and the application download page is displayed by accessing a software server, which is a server for downloading the installation package of the application. And after the application installation data package supporting the user x to download the second application in the application download page is obtained, the terminal device x can install the second application through the downloaded application installation data package. Furthermore, when the installed state of the second application in the terminal device x is an application uninstalled state, the terminal device x may further synchronize the conference identifier of the target conference and the application account identifier for the second application with an application server of the second application, and the following explanation on the application account identifier is provided.

Synchronizing the conference identifier and the application account identifier of the target conference to an application server of a second application, so that the application server stores an identifier mapping relationship between the conference identifier and the application account identifier:

the synchronization of the conference identifier of the target conference and the application account identifier for the second application from the application server by the terminal device x is realized by the h5 server, and may be: when detecting the application uninstalled state of the second application, the terminal device x may send, to the h5 server, a prompt for the installation state of the second application, where the prompt is used to notify the h5 server that the second application is not installed in the terminal device x. After the h5 server obtains the prompt information, the conference identifier of the target conference and the application account identifier for the second application may be sent to the application server of the second application, so that the application server may store the acquired conference identifier and application account identifier of the target conference in an associated manner. It can be understood that the application server needs to store a mapping relationship between the acquired conference identifier of the target conference and the application account identifier for the second application, and the mapping relationship between the conference identifier and the application account identifier may be referred to as an identifier mapping relationship.

The application account id for the second application refers to an account id of a user account used for logging in the second application after the subsequent user x installs the second application and logs in the second application. For example, subsequently, when the user x is a second application logged in through a mobile phone number, the application account id is the mobile phone number; for another example, subsequently, when the user x is a second application logged in through a certain mailbox, the application account id is the mailbox; for example, when the user x logs in the second application through the account registered in the first application, the application account id is the account id of the user account registered in the first application by the user x (referred to as OpenId of the first application).

Wherein, a login selection page is output; the login selection page comprises a first application login control and an external account login control; when the selection operation aiming at a first application login control in a login selection page is responded, taking an account identification of a first application as an application account identification, and synchronizing the conference identification and the application account identification to an application server; when the selection operation of an external account login control in a login selection page is responded, an account identification acquisition page is output, an entered account character string is acquired in the account identification acquisition page and is used as an application account identification, and the agenda identification and the application account identification are synchronized to an application server:

therefore, before the terminal device x transmits the aforementioned prompt information on the installation state of the second application to the h5 server, a login selection page may be output on the terminal page, and this login selection page may be displayed before the application download page. In other words, when the terminal device x detects the application uninstalled state of the second application, display can be skipped from the above-described conference entry page as the login selection page. For example, the application download page may be theterminal page 106a in fig. 2a, and the login selection page may be displayed after theterminal page 105a in fig. 2a and before theterminal page 106 a. The login selection page comprises a first application login control and an external account login control, the first application login control and the external account login control can be buttons, and the first application login control and the external account login control can be controlled through voice. The login selection page is used for determining the application account identification for the second application, the first application login control in the login selection page is used for taking the account identification of a user account obtained by registering the user x in the first application as the application account identification, the external account login control in the login selection page is used for taking an account character string recorded by the user x as the application account identification, and the account character string can be a mobile phone number or a mailbox and the like.

Wherein the second application is installed; logging in a second application based on the first application when the application account identification is the account identification of the first application; when the application account is identified as the account character string, logging in a second application based on the account character string:

the terminal device x may respond to a selection operation of the user x for a first application login control in the login selection page, for example, respond to a click operation of a button corresponding to the first application login control or a voice selection operation for the first application login control, take an account id of the first application (i.e., an account id of a user account registered by the user x in the first application) as an application account id for the second application, and synchronize the application account id and a conference id of the target conference to the application server. In this case, it is indicated that the user x needs to use the first application to log in the second application after installing the second application in the terminal device x.

Or, the terminal device x may also output an identifier obtaining page in the terminal page in response to a selection operation of the user x for the external account login control in the login selection page. The terminal device x may obtain an account character string entered by the user x in the identifier obtaining page, and the terminal device x may use the obtained account character string as an application account identifier for the second application and synchronize the application account identifier and the conference identifier of the target conference to the application server. In this case, it indicates that the user needs to log in the second application by using the account character string entered by the user after installing the second application in the terminal device.

More specifically, after the terminal device x installs the second application, if the application account id is the account id of the first application, the first application may be used to register and log in the second application or directly log in the second application. The first application is used for logging in the second application, which indicates that a user account is registered in the second application through the user account of the first application by the user x, and during the process, an application server (namely, a background server of the second application) generates an account identifier of the second application through account identifier mapping of the first application. The account id of the second application is the account id of the user account registered in the second application by the user x using the user account in the first application, and may be referred to as a mapping account id. The mapping account id and the application account id in this case (i.e. the account id of the first application) have a mapping relationship therebetween, and the application server also stores the mapping relationship.

Or, after the terminal device x installs the second application, if the application account id is an account character string entered by the user, the application may register and log in the second application using the account character string or directly log in the second application. If the user account is directly logged in the second application, the user account is registered in the second application by using the account character string, and the account identifier of the second application is the account character string.

Please refer to fig. 4, which is a schematic page diagram of a terminal device provided in the present application. As shown in fig. 4, the terminal device x is taken as theterminal device 200b, the first application is the application Y2, and the second application is the application Y1. Theterminal page 105a is theterminal page 105a in fig. 2a, and theterminal page 106a is theterminal page 106a in fig. 2 a. The terminal device x may jump to theterminal page 100c in response to a click operation of the user x on the "click download"button 109b in theterminal page 105a, where theterminal page 100c is the login selection page. The login selection page includes alogin selection box 102c, and thelogin selection box 102c includes a "current application login"button 103c and an "other account login"button 104c, where the "current application login"button 103c is the first application login control, and the "other account login"button 104c is the external account login control. The terminal device x may respond to a click operation of the user x on thebutton 103c in theterminal page 100c, use the application identifier of the first application as the application account identifier, and jump to theterminal page 106 a.

Or, the terminal device x may also respond to a click operation of the user x on thebutton 104c in theterminal page 100c, and jump to and display theterminal page 101c, where theterminal page 101c is the identifier obtaining page. Theterminal page 101c includes aninput box 105c, and supports the user x to enter an account character string in theinput box 105c, where the account character string entered in theinput box 105c by the user x is "12345678", and the 12345678 may be a mobile phone number. The terminal device x may respond to a click operation of the user x on the "ok"button 106c in theinput box 105c, acquire an account character string entered by the user x in theterminal page 101c, use the account character string as the application account identifier, and jump to and display the application account identifier on theterminal page 106 a. The above process describes how to determine the application account identification for the second application.

Alternatively, in theterminal page 100c in the embodiment described in fig. 4, in addition to the "current application login" button and the "other account login" button, a "login with application Y3" button, a "login with application Y4" button, and the like may be provided in theterminal page 100 c. Both the application Y3 and the application Y4 may be any other application different from the first application and the second application, a user account registered by the user x in the application Y3 is registered in the application Y3 in the terminal device x, and a user account registered by the user x in the application Y4 is also registered in the application Y4.

Further, the terminal device x may respond to a click operation of the user x on the "login using application Y3" button, and obtain, from the application Y3 in the terminal device x, the account id of the application Y3 as the application account id for the second application through the application external interface registered by the application Y3 in the terminal device x. The account id of the application Y3 is the account id of the user account of the user x logged in the application Y3. Alternatively, the terminal device x may respond to a click operation of the user x on the "login using the application Y4" button, and obtain the account id of the application Y4 from the application Y4 in the terminal device x through the application external interface registered by the application Y4 in the terminal device x, as the application account id for the second application. The account id of the application Y4 is the account id of the user account of the user x logged in the application Y4. After responding to the click operation of the user x on the "login with application Y3" button or responding to the click operation of the user x on the "login with application Y4" button, the terminal device x can jump to the application download page for the second application, namely, theterminal page 106a in fig. 4.

Optionally, the obtaining manner of the application account identifier for the second application and the login manner for the second application may also be:

the user account of the user x in the first application may be referred to as a first account, and the user account of the user x in the second application may be referred to as a second account. The user x may bind a second account of the user x in the second application in the first application, after the binding, the first account in the first application has a binding relationship with the second account, and the binding relationship may be stored in a background server of the first application. The background server of the first application may store not only the binding relationship between the first account and the second account, but also an account and a password of the second account entered by the user x.

Therefore, when the application installation state of the second application acquired by the terminal device x is an application uninstallation state, the account id of the second account having a binding relationship with the first account may be acquired from the background server of the first application through the first application, and the account id of the second account may be an account (e.g., a mobile phone number or a mailbox, etc.) of the second account. The terminal device x may use the acquired account id of the second account as the application account id for the second application. The terminal device x may send the account id of the second account and the conference id of the target conference to the application server, and the application server may store an id mapping relationship between the account id of the second account and the conference id.

In addition, when the application installation state of the second application acquired by the terminal device x is the application uninstallation state, the second application may also be automatically downloaded and installed. After the second application is installed, the terminal device x may further obtain the account and the password of the second account from the background server of the first application through the first application. The terminal device x can directly use the acquired account and password of the second account to log in the second application without performing other user operations by the user.

When the background server of the first application stores the binding relationship between the first account and the second account, only the account identifier of the second account may be stored, and the account identifier of the second account may be an account (e.g., a mobile phone number or a mailbox) of the second account. The terminal device x can acquire an account identifier of a second account having a binding relationship with the first account from a background server of the first application through the first application, use the account identifier of the second account as an application account identifier for the second application, and send the account identifier of the second account and a conference identifier of a target conference to the application server, so that the application server can store an identifier mapping relationship between the account identifier of the second account and the conference identifier.

In addition, after the terminal device x acquires the application uninstalled state of the second application, and downloads and installs the second application, the installed second application may be automatically started. After the second application is started, the first application in the terminal device x may acquire the account id of the second account from the background server of the first application, and give the account id of the second account to the started second application. The started second application can acquire the account and the password of the second account from the application server of the second application according to the acquired account identifier of the second account (to implement the process, the user x is required to authorize the first application in the second application, that is, the second application is authorized to acquire the account and the password of the second account through the account identifier of the second account acquired from the first application), and then the second application can successfully log in the second application according to the account and the password of the second account sent by the application server.

Under the circumstance, the terminal device x can respond to the conference entering operation (for example, the operation of identifying the identification code of the target conference) of the user x for the target conference, namely, the second application can be installed and logged in by itself under the circumstance that the second application is not installed, and meanwhile, the user x is not required to execute any user operation, so that the full-automatic installation and login process of the terminal device x for the second application is realized, the login efficiency of the terminal device x for the second application is improved, the user operation is simplified, and the user experience is improved.

Step S103, in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation;

optionally, when the terminal device x successfully logs in the second application through the application account identifier and enters an application home page of the second application, the second application is triggered to spontaneously generate meeting entry request information, and the meeting entry request information is used for acquiring meeting detail information of the target meeting from the application server. Terminal device x may send the generated conference entry request information to the application server.

When the successful login of the second application based on the first application is detected, conference entrance request information is generated; the conference joining request information carries a mapping account identifier corresponding to the application account identifier; the account identification is mapped to be the account identification obtained by registering the first application in the second application; sending the conference joining request information to an application server so that the application server can acquire conference detail information of the target conference according to the mapping account identification and the identification mapping relation carried by the conference joining request information; the conference detail information is acquired by the application server according to the conference identifier; the conference identifier is acquired by the application server according to the identifier mapping relation and the application account identifier; the application account identification is obtained by the application server according to the mapping account identification carried by the conference joining request information:

if the second application is logged in by using the first application, the conference entry request information generated by the second application in the terminal device x carries the mapping account identifier, and the mapping account identifier and the account identifier of the first application have a mapping relationship. After the application server obtains the conference entry request information, an application account identifier (here, an account identifier of the first application) having a mapping relationship with the mapping account identifier may be obtained according to the mapping account identifier carried by the conference entry request information. Then, the application server may obtain a pre-stored conference identifier having a mapping relationship with the acquired application account identifier according to the acquired application account identifier. After the application server obtains the conference identifier, the application server can obtain the conference detail information of the target conference according to the conference identifier. The application server may transmit the acquired meeting detail information to the terminal device x.

When the successful login of the second application based on the account character string is detected, conference joining request information is generated; the conference joining request information carries an account character string; sending the conference joining request information to an application server so that the application server can acquire conference detail information of the target conference according to the account character string and the identification mapping relation carried by the conference joining request information; the conference detail information is acquired by the application server according to the conference identifier; the conference identifier is obtained by the application server according to the account character string carried by the conference joining request information and the identifier mapping relationship:

if the second application is logged in by using the account character string, the conference entry request information generated by the second application in the terminal device x carries the application account identifier (i.e., the account character string). After the application server obtains the conference joining request information, the application server can obtain a conference identifier having a mapping relation with the conference joining request information according to the application account identifier carried by the conference joining request information, and after the application server obtains the conference identifier, the application server can obtain conference detail information of the target conference according to the conference identifier. The application server may transmit the acquired meeting detail information to the terminal device x.

If the second application is logged in by using the second account, the conference entry request information generated by the second application in the terminal device x may carry an account id of the second account. After the application server obtains the conference joining request information, the application server can obtain a conference identifier having an identifier mapping relationship with the conference identifier according to the account identifier of the second account carried by the conference joining request information. Furthermore, the application server may obtain the meeting detail information of the corresponding target meeting according to the obtained meeting identifier, and the application server may send the obtained meeting detail information to the second application in the terminal device x.

Through the above process, the second application in the terminal device x can obtain the meeting detail information of the target meeting sent to the second application by the application server.

Step S104, entering a target conference in a second application according to the conference detail information;

optionally, the conference detail information of the target conference may include a conference identifier of the target conference, the terminal device x may directly enter a page where the target conference is located in the second logged-in application according to the acquired conference identifier in the conference detail information of the target conference, and the page where the target conference is located may refer to a page where the target conference is in progress. The conference detail information of the target conference may further include information such as conference creation time, a conference creator, a conference host, and a conference name of the target conference, and the terminal device x may further display information such as the conference creation time, the conference creator, the conference host, and the conference name included in the conference detail information in a page in which the target conference is in progress. In other words, in the view of the user x, after the second application is installed and logged in the terminal device x, the target conference can be entered in the logged-in second application immediately without performing other user operations.

Therefore, it can be understood that, when the application account id is an account id of a second account having a binding relationship with a first account in a first application, after the terminal device x responds to a conference entering operation of the user x for the target conference (for example, a clicking operation on thebutton 107b in fig. 2b) in the step S101, a series of actions of installing the second application, logging in the installed second application through the second account, and directly entering the target conference in the logged-in second application may be automatically performed. In this case, in the view angle of the user x, that is, after the conference entering operation for the target conference is performed, even if the terminal device x does not have the second application installed therein, the user can directly enter the target conference without performing any other user operation in the middle. Therefore, further, the operation difficulty of the user is reduced, and the entry efficiency for the target conference is improved.

Optionally, the terminal device x may also output, in the second application, a conference entry notification page for the target conference according to the acquired conference detail information, where the conference entry notification page may be referred to as an incoming call notification of the target conference, the conference entry notification page may be displayed in full screen in the terminal device x, and the conference entry notification page may include the conference detail information. For example, the conference notification page may be theterminal page 109a of fig. 2a described above. The meeting detail information may include meeting identification, creator, creation time, host, current number of participants, etc. of the target meeting.

The conference notification page may further include a confirmation control and a cancellation control, where the confirmation control and the cancellation may be both buttons and may also be voice controls. In response to the selection operation of the user x on the confirmation control in the conference entry notification page, the terminal device x may jump to a conference in-progress page (e.g., theterminal page 110a in fig. 2 a) displayed in the target conference and enter the target conference, that is, an application account of the user x in the second application participates in the target conference. The selection operation of the user x for the confirmation control can be referred to as a confirmation operation for the conference entry notification page. The terminal device x can also respond to the selection operation of the user x for the cancel control in the conference entrance notification page, close the conference entrance notification page, abandon the entrance of the target conference, and return to the application home page of the second application. The selection operation of the user x for the cancel control can be referred to as a cancel operation for the conference entry notification page.

More specifically, when the application server detects that the target conference has ended, for example, the target conference has been cancelled, the application server may delete the identifier mapping relationship between the stored application account identifier and the conference identifier of the target conference, so that when the terminal device x installs and logs in the second application, if the target conference has ended, the conference entry notification page for the target conference is not displayed when the terminal device x successfully logs in the second application.

In addition, when the terminal device x successfully enters the target conference through the conference entry notification page, the terminal device x may send conference entry prompt information to the application server, where the conference entry prompt information is used to prompt the application server that the second application in the terminal device x has successfully entered the target conference. When the application server obtains the conference entering prompt information, the identifier mapping relationship between the stored application account identifier and the conference identifier of the target conference can be deleted.

Further, even when the user x logs in the second application through another terminal device other than the terminal device x, the conference entrance notification information for the target conference can be displayed in the terminal device that logs in the second application through the above-described procedure. For example, assuming that the user x logs in the second application at the terminal device z through the application account id, when the terminal device z successfully logs in the second application, the second application in the terminal device z may send conference entry request information to the application server, where the conference entry request information may carry the application account id. When the application server acquires the conference joining request information, the application server can search the conference identifier having an identifier mapping relationship with the conference identifier according to the application account identifier carried by the conference joining request information, and then find the conference detail information of the corresponding target conference through the searched conference identifier. Then, the application server may send the found meeting detail information of the target meeting to the terminal device z, so that the terminal device z may enter the target meeting according to the meeting detail information.

And when the application server detects that other terminal devices except the terminal device x log in the second application, the stored identifier mapping relationship between the application account identifier and the conference identifier of the target conference can be deleted. In other words, when the application server detects that the user account corresponding to the application account identifier in the stored identifier mapping relationship enters the target conference, the application server may delete the stored identifier mapping relationship between the application account identifier and the conference identifier of the target conference.

Further, when the application installation state of the second application acquired in step S101 is the application installed state, the terminal device x may start the second application through the application external interface of the second application, and enter the home page of the second application. The terminal device x may directly enter the target conference in the started second application, or may display the conference entrance notification page for the target conference in the started second application, in which case, the conference detail information in the conference entrance notification page may be the conference invitation information of the target conference acquired by the terminal device. After that, the terminal device x may select to enter the target conference or select not to enter the target conference through the conference entering notification page.

Please refer to fig. 5, which is a schematic page diagram of a terminal device provided in the present application. Here, the terminal device x is theterminal device 200b, the first application is the application Y2, the second application is the application Y1, the number of users x is large, and the user Y is the user bean. Theterminal page 104a is theterminal page 104a in fig. 2a, the terminal device x may respond to a click operation of a user on thebutton 107a in theterminal page 104a, successfully start the second application through an application external interface of the second application, and directly display the terminal page 100d in the started second application, where the terminal page 100d is the conference notification page. The terminal page 100d includes aslider 101d and abutton 102d, where theslider 101d is the above-mentioned confirmation control, and thebutton 102d is the above-mentioned cancellation control. The terminal device x may enter the target conference in response to a right-sliding operation (i.e., the above-mentioned confirmation operation) of the user x on theslider 101d, and jump to and display on theterminal page 104d, and it can be known through theterminal page 104d that the users currently participating in the target conference include the user beans, the user music, and how many users are. The terminal device x may also respond to a click operation of the user x on thebutton 102d, abandon entry into the target conference, and jump to and display theterminal page 103d, where theterminal page 103d is an application home page of the second application.

The method and the device can respond to conference joining operation aiming at the target conference in the first application, and obtain the application installation state of the second application; the target conference is initiated through the second application; when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation; in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation; and entering the target conference in the second application according to the conference detail information. Therefore, the method provided by the application can automatically acquire the conference detail information aiming at the target conference and quickly enter the target conference according to the conference detail information after the second application is installed and logged in, so that the entry efficiency aiming at the target conference after the second application is logged in is improved.

Please refer to fig. 6, which is a flowchart illustrating an application data processing method according to the present application. As shown in fig. 3, the method may include:

step S201, the second application of the inviter requests the server f1 to generate a two-dimensional code and generate a conference identifier;

optionally, the inviter may refer to the user y, the second application of the inviter may refer to the second application installed in the terminal device y, and the user account of the inviter is logged in the second application installed in the terminal device y. The second application of the inviter may request the creation of the target conference from the server f1 through the terminal device y to request the generation of the conference identification of the target conference and the two-dimensional code of the target conference. The server f1 is a background server of the second application, i.e. the application server.

Step S202, the server f1 sends the two-dimensional code picture data and the meeting details to a second application of the inviter;

optionally, the server f1 may generate a conference identifier of the target conference after acquiring the creation request for the target conference sent by the second application in the terminal device y, and generate a jump website for the target conference according to the conference identifier of the target conference, where the jump website includes the conference identifier. Then, the server f1 may generate two-dimensional code picture data according to the jump website, where the two-dimensional code picture data includes the jump website for the target conference. The server f1 may send the generated two-dimensional code picture data containing the jump website of the target conference and the conference details of the target conference to the second application in the terminal device y. The conference details of the target conference may refer to conference detail information of the target conference, and the conference details may include information such as a creator of the target conference, a creation time of the target conference, a host of the target conference, and a conference name of the target conference.

Step S203, the second application of the inviter generates a sharing picture according to the two-dimensional code and the meeting details;

optionally, the second application in the terminal device y may generate a sharing picture for the target conference (the sharing picture is equal to the invitation picture) according to the acquired two-dimensional code picture data and the conference details of the target conference, which are sent by the server f1, where the sharing picture includes the conference details and the two-dimensional code picture data of the target conference.

Step S204, the second application of the inviter sends the sharing picture to the first application of the inviter;

optionally, the first application of the inviter refers to a first application installed in the terminal device y, and the first application in the terminal device y is logged in by a user account of the inviter. A button of "share to first application" may be provided in the second application of the terminal device y, and the terminal device y may start the first application in response to a click operation of the inviter with respect to the button of "share to first application". And the user is supported to select an invitee in the address book of the started first application, and the generated sharing picture is sent to the invitee through the started first application. Here, the invitee may refer to the user x described above.

Optionally, the terminal device y may also export the generated sharing picture of the target conference to a local album of the terminal device y for storage. And the support inviter opens a first application in the terminal device y, selects an invitee in the opened first application, and expands a chat page with the selected invitee. And supporting the inviter to open the local album of the terminal device y in the chat page, selecting the stored sharing picture in the local album, and sending the sharing picture to the invitee as a chat message.

Step S205, the first application of the inviter selects the invitee to go to the message channel;

optionally, after the first application in the terminal device y selects the invitee in the first application, the shared picture is sent to the invitee through the background server of the first application, so that the first application in the terminal device y may send the shared picture to the server f2, where the server f2 is the background server of the first application.

Step S206, the server f2 sends the shared picture to the first application of the invitee;

optionally, the first application of the invitee may refer to a first application installed in the terminal device x, and the first application installed in the terminal device x logs in a user account registered by the invitee. The server f2 may send the obtained shared picture sent to the first application in the terminal device y to the first application in the terminal device x, so as to achieve the purpose of sending the shared picture to the invitee, and the invitee may also view the shared picture for the target conference in the first application in the terminal device x.

Through the process, the process that the inviter sends the sharing picture to the invitee is realized. The following describes how an invitee enters a target conference through a third-party application (here, the first application in terminal device x) in an embodiment corresponding to fig. 7.

Please refer to fig. 7, which is a flowchart illustrating an application data processing method according to the present application. The embodiment depicted in fig. 7 is a step subsequent to the embodiment depicted in fig. 6 described above. As shown in fig. 7, the method may include:

step S301, a first application of an invitee analyzes a two-dimensional code;

alternatively, the invitee may refer to the user x, and the first application of the invitee may be the first application installed in the terminal device x. The first application in the terminal device x may obtain the shared picture sent to the first application in the terminal device y. The first application in the terminal device x can analyze the two-dimensional code in the shared picture to obtain the website included in the two-dimensional code. For example, the first application in the terminal device x may respond to a long-time pressing operation of the user x on the two-dimensional code in the shared picture, and the website included in the two-dimensional code may be resolved.

Step S302, a first application of an invitee opens a website contained in the two-dimensional code;

optionally, the first application in the terminal device x may open the website included in the two-dimensional code obtained by the analysis by accessing the page server. The page server may be an h5 server, and the h5 server may be used to provide a web service for the first application in the terminal device x.

Step S303, the page server acquires meeting detail information according to the meeting identification;

optionally, the page server may obtain a conference identifier of the target conference in the website included in the analyzed two-dimensional code, and send the conference identifier to the server of the second application, so as to request the server of the second application to obtain conference detail information of the target conference. And the server of the second application is the application server.

Step S304, the server of the second application sends the meeting detail information to the page server;

optionally, the server of the second application may obtain a conference identifier of the target conference sent by the page server, and the server of the second application may correspondingly obtain conference detail information of the target conference according to the conference identifier. The meeting detail information may include the creator, creation time, meeting name, meeting supporter, etc. of the target meeting. The server of the second application may send the acquired meeting detail information of the target meeting to the page server.

Step S305, the page server sends meeting detail information to a first application of an invitee;

optionally, the page server may obtain the meeting detail information of the target meeting sent by the server of the second application, and the page server may send the obtained meeting detail information to the first application in the terminal device x.

Step S306, the first application of the inviter prompts the page server that the first application is not installed;

optionally, the first application in the terminal device x may obtain the meeting detail information of the target meeting sent by the page server. The first application in the terminal device x may output the conference entry page for the target conference in the terminal page according to the acquired conference detail information. Terminal device x may launch the second application in response to a conference entry operation by user x for the conference entry page. For example, a button "open second application and enter target meeting" may be provided in the meeting entry page, and the first application in the terminal device x may respond to a click operation of the button "open second application and enter target meeting" by the user x, and start the second application through the external application interface registered in the terminal device x by the second application. When the terminal device x finds that the second application is not started successfully, indicating that the second application is not installed in the terminal device x, the terminal device x may prompt the page server that the second application is not installed. For example, the terminal device x may send a prompt message to the page server, so as to prompt the page server that the second application is not installed in the terminal device x through the prompt message.

Step S307, when the page server detects that the first application is not installed, the page server sends pre-conference information to an application server of a second application;

optionally, the page server may obtain a prompt message sent by the terminal device x, and learn that the second application is not installed in the terminal device x according to the prompt message. When the page server detects that the second application is not installed in the terminal device x, the pre-conference information may be sent to the server of the second application. The pre-conference information is used for automatically displaying an incoming call notification for the target conference in the second application after the second application is installed and logged in the subsequent terminal device x, which is specifically referred to below. The conference pre-entry information may include a conference identifier of the target conference and an account identifier of a first application in the terminal device x, where the account identifier of the first application is an account identifier of a user account logged in the first application in the terminal device x, and the account identifier of the first application is used as an application account identifier for the second application.

After the server of the second application acquires the conference identifier of the target conference and the account identifier of the first application, which are sent to the server of the page server, the server of the second application may perform associated storage on the acquired conference identifier and the account identifier of the first application, that is, store a mapping relationship between the acquired conference identifier and the account identifier of the first application.

Step S308, the page server guides the terminal device x held by the invitee to jump to a software downloading page for guiding downloading;

alternatively, the page server may access the software server so that the software server may provide the terminal device x with software download-related information, which is information for downloading the second application. The terminal device x may output an application download page for the second application in the terminal page according to the software download related information, for example, the application download page may be theterminal page 106a in fig. 4 described above.

Step S309, the terminal device of the invitee may download and install the second application from the software server;

optionally, the terminal device x may download the application installation data package of the second application in the output software download page in response to a user operation of the user x. For example, a "download second application" button may be provided in the software download page, and the terminal device x may access the software server from which an application installation package for downloading the second application is requested in response to a click operation of the user x on the "download second application" button. Then, the terminal device x may install the second application through the downloaded application installation data package of the second application. After the terminal device x successfully installs the second application, the application installation data packet of the second application may be automatically deleted. Through the above-described procedure, the second application of the invitee in fig. 7 exists in the terminal device x.

Step S310, a second application of the invitee logs in the second application through the first application;

optionally, the second application in the terminal device x may log in the second application through the first application, that is, log in the second application through the user account in the first application. The second application in the terminal device x may request the first application in the terminal device x to acquire the account id of the user account bound in the first application, that is, the account id of the first application.

Step S311, the first application of the invitee sends the account identifier of the first application to the second application of the invitee;

optionally, when receiving an acquisition request for an account identifier of a first application sent by a second application in the terminal device x, a first application in the terminal device x may send the application identifier of the first application to the second application in the terminal device x.

Step S312, the second application of the invitee uses the account identifier of the first application to log in or register;

optionally, the second application in the terminal device x may obtain, according to the account id of the first application, the account id of the second application from a server of the second application. If the user x has previously registered the second application through the account id of the first application, it indicates that the user x has a user account of the second application, and the user account of the second application is obtained by registering the user account of the first application. Therefore, a mapping relationship exists between the account id of the user account of the second application and the account id of the first application, and the server of the second application necessarily stores the mapping relationship, and the account id of the second application may be referred to as a mapping account id. Therefore, the server of the second application may directly obtain the corresponding mapping account id according to the account id of the first application sent by the second application in the terminal device x.

Or, if the user x does not register the second application with the account id of the first application before, the second application may be registered with the account id of the first application, and during registration, the server of the second application also generates the account id of the second application (i.e., maps the account id) according to the account id of the first application. After the registration is completed, the server of the second application also stores the mapping relationship between the account id of the first application and the mapping account id. Therefore, the server of the second application may obtain the mapping account id corresponding to the account id of the first application generated at this time.

Step 313, the server of the second application sends the mapping application identifier corresponding to the account identifier of the first application to the second application of the invitee;

optionally, the server of the second application may send the obtained mapping application identifier having a mapping relationship with the account identifier of the first application to the second application in the terminal device x.

Step S314, the second application of the invitee enters an application home page and activates the pre-conference information;

optionally, the second application in the terminal device x may log in the second application according to the obtained mapping account identifier, and enter an application home page of the second application. When the second application in the terminal device x enters the application home page of the second application, the second application can be activated, so that the second application sends activation information to the server of the second application. The activation information is used to activate pre-session information, the activation information is equal to the session request information, and the activation information may carry the mapping account id.

Step S315, the server of the second application inquires corresponding meeting detail information;

optionally, after acquiring the activation information sent by the second application in the terminal device x, the server of the second application may acquire the account id of the first application having a mapping relationship with the account id according to the mapping account id carried in the activation information, and then may find the conference id of the target conference having a mapping relationship with the account id of the first application through the acquired account id of the first application. And then, the server of the second application can obtain the conference detail information of the target conference according to the searched conference identifier of the target conference. The meeting detail information may include the meeting name of the target meeting, the meeting start time, the meeting progress state (e.g., in-progress state or end state), the meeting creator, the meeting moderator, and the like.

Step S316, the server of the second application sends the meeting detail information to the second application of the invitee;

optionally, the server of the second application may send the acquired meeting detail information to the second application in the terminal device x.

Step S317, the second application of the invitee displays a meeting notification page;

optionally, the second application in the terminal device x may acquire the meeting detail information of the target meeting, which is sent to the second application by the server of the second application, and the second application in the terminal device x may output an incoming call notification for the target meeting in the terminal page according to the acquired meeting detail information of the target meeting, where the incoming call notification is the meeting notification page for the target meeting. Meeting detail information of the target meeting can be included in the meeting notification page, and the meeting notification page is used for enabling the second application in the terminal device to enter the target meeting.

The incoming call notification of the target conference may be a full-screen incoming call notification output in the terminal device x, and the incoming call notification may include a "enter conference" button (the function is equivalent to theslider 112b in fig. 2b) and a "temporarily not enter conference" button (the function is equivalent to thebutton 123b in fig. 2 b). The terminal device x can respond to the click operation of the user x on the "enter conference" button in the terminal page where the incoming call notification is located, and enter the target conference. Or, the terminal device x may also give up entering the target conference in response to the click operation of the "temporarily not entering the conference" button in the terminal page where the incoming call notification is located by the user x, and return to the application home page of the second application in the terminal device x.

The method and the device can respond to conference joining operation aiming at the target conference in the first application, and obtain the application installation state of the second application; the target conference is initiated through the second application; when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation; in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation; and entering the target conference in the second application according to the conference detail information. Therefore, the method provided by the application can automatically acquire the conference detail information aiming at the target conference and quickly enter the target conference according to the conference detail information after the second application is installed and logged in, so that the entry efficiency aiming at the target conference after the second application is logged in is improved.

Please refer to fig. 8, which is a schematic view of a scenario for applying data processing according to the present application. As shown in fig. 8, theterminal device 100e may be the terminal device y, theterminal device 102e may be the terminal device x, and theserver 103e may be an application server of the second application. The second application may be installed in theterminal device 100e, and the second application in theterminal device 100e may create the target conference.

After the target conference is created, theterminal device 100e may further generate aninvitation picture 101e for the target conference, where theinvitation picture 101e may include an identification code (e.g., a two-dimensional code, etc.) of the target conference and conference detail information of the target conference. Theterminal device 100e may further include a first application, and theterminal device 100e may start the first application in the generation page of theinvitation picture 101e of the second application, search and select the user x in the address list of the first application, and send theinvitation picture 101e to the user x. The sending of theinvitation picture 101e to the user x is to send theinvitation picture 101e to a terminal device where a user account of the user x in the first application is located, where the terminal device where the user account of the user x in the first application is located is theterminal device 102 e. In other words, theterminal device 100e may send the above-describedinvitation picture 101e to the second application in theterminal device 102 e.

When the first application in theterminal device 102e acquires theinvitation picture 101e sent by theterminal device 100e, the identification code in theinvitation picture 101e in the first application may be identified through a function of identifying the identification code in the first application. After theterminal device 102e recognizes the identification code in theinvitation picture 101e, the second application may be launched. When theterminal device 102e detects that the second application is not started successfully, which indicates that the second application is not installed in theterminal device 102e, theterminal device 102e may synchronize thepre-conference information 104e for the target conference to theapplication server 103e of the second application. The synchronization of thepre-conference information 104e of the target conference to theserver 103e by theterminal device 102e is realized by the h5 server. Thepre-conference information 104e of the target conference may include a conference identifier of the target conference and an application account identifier for the second application (the application account identifier may be an account identifier of a user account of the user x in the first application), and the pre-conference information is used to enable theterminal device 102e to quickly enter the target conference after the second application is installed.

Next, theterminal device 102e may install the second application and log in the second application using the application account identification. When the application account identification is the account identification of the user account of the user x in the first application, the second application can be logged in through the user account of the user x in the first application.

When theterminal device 102e successfully logs in the second application and enters the application home page of the second application, the second application may be triggered to autonomously send conference entry request information to theapplication server 103 e. The conference joining request information may carry an application account id, for example, if the second application logs in through a user account of the user x in the first application, the conference joining request information may carry a mapping account id corresponding to the account id of the user account of the user x in the first application (which may be referred to as the account id of the first application for short), the mapping account id is an account id of the user account obtained by registering the user account of the user x in the first application in the second application, a mapping relationship is provided between the account id of the first application corresponding to the user x and the mapping account id, and a mapping relationship between the account id of the first application and the mapping account id corresponding to the user x is also stored in theapplication server 103 e.

After theapplication server 103e acquires the conference entry request information sent by theterminal device 102e, theapplication server 103e may acquire an account id of the first application having a mapping relationship with the mapping account id according to the mapping account id carried by the conference entry request information. Since theapplication server 103e stores thepre-conference information 104e for the target conference before, thepre-conference information 104e may include a conference identifier of the target conference and an application account identifier, which may be an account identifier of the first application. Therefore, theapplication server 103e may find, according to the account identifier of the first application obtained by mapping the account identifier, a conference identifier having a mapping relationship with the account identifier of the first application (find according to thepre-conference information 104 e). Further, theapplication server 103e may find the meeting detail information of the corresponding target meeting according to the meeting identifier.

More, theapplication server 103e may send the acquired meeting detail information of the target meeting to theterminal device 102e, and theterminal device 102e may display a meeting notification page for the target meeting according to the meeting detail information, and further, theterminal device 102e may respond to a meeting operation of the user x for the meeting notification page to enter the target meeting. Alternatively, theterminal device 102e may also directly enter the target meeting according to the acquired meeting detail information of the target meeting without the user x performing other user operations.

By adopting the method provided by the application, when the target conference in the second application is entered through the third-party application (here, the first application), under the condition that the second application where the target conference is located is not installed, theterminal device 103e is supported, after the second application is installed, the user x does not need to find the conference entrance of the target conference again (for example, the identification code corresponding to the target conference), and thus the user x can quickly enter the target conference, the user operation of the user x when entering the target conference is simplified, and therefore, the conference entering efficiency of the user x for the target conference in the second application is improved, and the conference entering experience of the user x for the cross-application entering of the target conference is improved.

Fig. 9 is a schematic structural diagram of an application data processing apparatus according to the present application. The application data processing apparatus may be a computer program (including program code) running in a computer device, for example, the application data processing apparatus is an application software, and the application data processing apparatus may be configured to execute corresponding steps in the method provided by the embodiment of the present application. As shown in fig. 9, the application data processing apparatus 1 may include: aconference response module 101, aninstallation module 102, adetail acquisition module 103 and anotification module 104;

the conference joiningresponse module 101 is configured to respond to a conference joining operation for the target conference in the first application and acquire an application installation state of the second application; the target conference is initiated through the second application;

theinstallation module 102 is configured to install a second application when the application installation state is an application uninstallation state, and log in the second application according to the application account identifier; the application account number identification and the conference identification of the target conference have an identification mapping relation;

thedetail acquiring module 103 is configured to acquire, in the logged-in second application, meeting detail information corresponding to the meeting identifier according to the identifier mapping relationship;

and aconference entering module 104, configured to enter the target conference in the second application according to the conference detail information.

For specific functional implementation manners of theconference response module 101, theinstallation module 102, thedetail obtaining module 103, and thenotification module 104, please refer to steps S101 to S104 in the embodiment corresponding to fig. 3, which is not described herein again.

The application installation state comprises an application uninstalled state and an application installed state;

theconference response module 101 includes: astart unit 1011, astart failure unit 1012, and astart success unit 1013;

astarting unit 1011, configured to start a second application based on an application external interface of the second application in response to a conference entering operation for a target conference in the first application;

a failedstart unit 1012, configured to acquire an uninstalled application state when starting of the second application fails;

astart success unit 1013 configured to acquire the application installed state when the second application is successfully started.

For a specific function implementation manner of thestart unit 1011, thestart failure unit 1012, and thestart success unit 1013, please refer to step S101 in the corresponding embodiment of fig. 3, which is not described herein again.

Theconference response module 101 includes: anidentification unit 1014, an invitationinformation acquisition unit 1015, an entrypage output unit 1016, and anenrollment response unit 1017;

theidentification unit 1014 is used for responding to the identification operation of the identification code of the target conference in the first application to obtain a website identification result;

an invitationinformation obtaining unit 1015, configured to obtain conference invitation information of the target conference according to the conference identifier in the website identification result;

an entrypage output unit 1016 configured to output a conference entry page for the target conference according to the conference invitation information;

and anenrollment response unit 1017, configured to obtain an application installation state of the second application in response to the enrollment operation for the conference portal page.

For specific functional implementation manners of the identifyingunit 1014, the invitationinformation obtaining unit 1015, the entrypage output unit 1016, and the conference enteringresponse unit 1017, please refer to step S101 in the corresponding embodiment of fig. 3, which is not described herein again.

Wherein the application data processing apparatus 1 is configured to:

synchronizing the conference identifier and the application account identifier of the target conference to an application server of a second application, so that the application server stores an identifier mapping relationship between the conference identifier and the application account identifier;

thedetail acquiring module 103 includes: aninformation transmitting unit 1031 and an information acquiring unit 1032;

aninformation sending unit 1031, configured to send conference entry request information to the application server based on the logged second application, so that the application server obtains conference detail information of the target conference according to the conference entry request information and the identifier mapping relationship;

an information obtaining unit 1032, configured to obtain the meeting detail information sent by the application server.

For specific implementation of functions of theinformation sending unit 1031 and the information obtaining unit 1032, please refer to steps S102 to S103 in the embodiment corresponding to fig. 3, which is not described herein again.

The application data processing device 1 includes: a selectedpage output module 105, a firstcontrol response module 106 and a secondcontrol response module 107;

a selectedpage output module 105 for outputting a login selected page; the login selection page comprises a first application login control and an external account login control;

a firstcontrol response module 106, configured to, when a selection operation for a first application login control in a login selection page is responded, use an account id of a first application as an application account id, and synchronize an negotiation id and the application account id to an application server;

a secondcontrol response module 107, configured to output an account id obtaining page when a selection operation for an external account login control in the login selection page is responded, obtain an entered account character string in the account id obtaining page, serve as an application account id, and synchronize the session id and the application account id to the application server.

For a specific implementation manner of the function of the pageselection output module 105, the firstcontrol response module 106, and the secondcontrol response module 107, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.

Wherein, theinstallation module 102 includes: aninstallation unit 1021, anapplication login unit 1022, and a characterstring login unit 1023;

aninstallation unit 1021 for installing a second application;

anapplication login unit 1022, configured to log in a second application based on the first application when the application account id is an account id of the first application;

a characterstring login unit 1023, configured to log in the second application based on the account character string when the application account is identified as the account character string.

For a specific implementation manner of the functions of theinstallation unit 1021, theapplication login unit 1022, and thestring login unit 1023, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.

Theinformation sending unit 1031 includes: afirst generation sub-unit 10311 and a firstinformation transmission sub-unit 10312;

afirst generation subunit 10311, configured to generate meeting entry request information when detecting that the second application is successfully logged in based on the first application; the conference joining request information carries a mapping account identifier corresponding to the application account identifier; the account identification is mapped to be the account identification obtained by registering the first application in the second application;

a firstinformation sending subunit 10312, configured to send the conference joining request information to the application server, so that the application server obtains conference detail information of the target conference according to the mapping account id and the id mapping relationship carried in the conference joining request information; the conference detail information is acquired by the application server according to the conference identifier; the conference identifier is acquired by the application server according to the identifier mapping relation and the application account identifier; the application account identification is obtained by the application server according to the mapping account identification carried by the conference joining request information.

For specific implementation of functions of thefirst generating subunit 10311 and the firstinformation sending subunit 10312, please refer to steps S102 to S103 in the embodiment corresponding to fig. 3, which is not described herein again.

Theinformation sending unit 1031 includes: asecond generating sub-unit 10313 and a secondinformation transmitting sub-unit 10314;

asecond generation subunit 10313, configured to generate conference entry request information when detecting that the second application is successfully logged in based on the account character string; the conference joining request information carries an account character string;

a secondinformation sending subunit 10314, configured to send the conference joining request information to the application server, so that the application server obtains conference detail information of the target conference according to the account character string and the identifier mapping relationship carried in the conference joining request information; the conference detail information is acquired by the application server according to the conference identifier; the conference identifier is obtained by the application server according to the account character string carried by the conference joining request information and the identifier mapping relation.

For specific implementation manners of functions of thesecond generating subunit 10313 and the secondinformation sending subunit 10314, please refer to steps S102 to S103 in the embodiment corresponding to fig. 3, which is not described herein again.

The application data processing apparatus 1 further includes: a downloadpage output module 108 and a datapacket download module 109;

a downloadpage output module 108, configured to output an application download page;

a datapackage downloading module 109, configured to download an application installation data package of the second application in the application downloading page;

a mountingmodule 102 for:

the second application is installed based on the application installation package.

For a specific implementation manner of the functions of the downloadpage output module 108 and the datapacket download module 109, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.

The application data processing device 1 includes: a bindingaccount acquisition module 110 and a binding identifier synchronization module 111;

a binding accountnumber obtaining module 110, configured to obtain an account number identifier of a second account number having a binding relationship with the first account number, as an application account number identifier; the first account is a user account of the first application; the second account is a user account of a second application;

a binding identifier synchronization module 111, configured to synchronize the session identifier and the application account identifier to the application server;

a mountingmodule 102 for:

and installing the second application, and logging in the second application according to the second account.

For a specific implementation manner of the functions of the bindingaccount obtaining module 110 and the binding identifier synchronizing module 111, please refer to step S102 in the embodiment corresponding to fig. 3, which is not described herein again.

The application data processing apparatus 1 further includes: a promptmessage generation module 112 and adeletion module 113;

a promptinformation generating module 112, configured to generate a conference entering prompt information when it is detected that the target conference is successfully entered through the conference detail information;

a deletingmodule 113, configured to send the conference entering prompt message to the application server, so that the application server deletes the identifier mapping relationship between the stored application account identifier and the conference identifier.

For a specific implementation manner of the functions of the promptinformation generating module 112 and the deletingmodule 113, please refer to step S104 in the embodiment corresponding to fig. 3, which is not described herein again.

Theconference entry module 104 includes: a notificationpage output unit 1041 and aconfirmation response unit 1042;

a notificationpage output unit 1041, configured to output a conference entrance notification page for the target conference in the second application according to the conference detail information;

aconfirmation responding unit 1042, configured to enter the target conference in response to a confirmation operation for the conference entry notification page.

For a specific implementation manner of the functions of the notificationpage output unit 1041 and theconfirmation response unit 1042, please refer to step S104 in the corresponding embodiment of fig. 3, which is not described herein again.

The application data processing apparatus 1 further includes: anapplication launch module 114 and anapplication entry module 115;

anapplication starting module 114, configured to start the second application based on the application external interface of the second application when the application installation state is the application installed state;

and anapplication entering module 115, configured to enter the target conference in the started second application.

For a specific implementation manner of the functions of theapplication starting module 114 and theapplication entering module 115, please refer to step S104 in the embodiment corresponding to fig. 3, which is not described herein again.

The method and the device can respond to conference joining operation aiming at the target conference in the first application, and obtain the application installation state of the second application; the target conference is initiated through the second application; when the application installation state is the application uninstallation state, installing a second application, and logging in the second application according to the application account identification; the application account number identification and the conference identification of the target conference have an identification mapping relation; in the second logged application, meeting detail information corresponding to the meeting identification is obtained according to the identification mapping relation; and entering the target conference in the second application according to the conference detail information. Therefore, the method provided by the application can automatically acquire the conference detail information aiming at the target conference and quickly enter the target conference according to the conference detail information after the second application is installed and logged in, so that the entry efficiency aiming at the target conference after the second application is logged in is improved.

Please refer to fig. 10, which is a schematic structural diagram of a computer device provided in the present application. As shown in fig. 10, thecomputer device 1000 may include: theprocessor 1001, thenetwork interface 1004, and thememory 1005, and thecomputer device 1000 may further include: auser interface 1003, and at least onecommunication bus 1002. Wherein acommunication bus 1002 is used to enable connective communication between these components. Theuser interface 1003 may include a Display screen (Display) and a Keyboard (Keyboard), and theoptional user interface 1003 may also include a standard wired interface and a standard wireless interface. Thenetwork interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). Thememory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. Thememory 1005 may optionally be at least one memory device located remotely from theprocessor 1001. As shown in fig. 10, amemory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a device control application program.

In thecomputer device 1000 shown in fig. 10, thenetwork interface 1004 may provide a network communication function; theuser interface 1003 is an interface for providing a user with input; and theprocessor 1001 may be configured to invoke a device control application stored in thememory 1005 to implement the description of the application data processing method in any of the embodiments previously described. It should be understood that thecomputer device 1000 described in this application can also perform the description of the application data processing apparatus 1 in the embodiment corresponding to fig. 9, which is not described herein again. In addition, the beneficial effects of the same method are not described in detail.

Further, here, it is to be noted that: the present application further provides a computer-readable storage medium, and the computer-readable storage medium stores the computer program executed by the application data processing apparatus 1 mentioned above, and the computer program includes program instructions, and when the processor executes the program instructions, the description of the application data processing method in any of the embodiments can be performed, and therefore, details will not be described here again. In addition, the beneficial effects of the same method are not described in detail. For technical details not disclosed in the embodiments of the computer storage medium referred to in the present application, reference is made to the description of the embodiments of the method of the present application. As an example, program instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network, which may comprise a block chain system.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

The above disclosure is only for the purpose of illustrating the preferred embodiments of the present application and is not to be construed as limiting the scope of the present application, so that the present application is not limited thereto but rather by the claims appended hereto.

Claims (15)

1. An application data processing method, comprising:

responding to conference entering operation aiming at a target conference in the first application, and acquiring an application installation state of the second application; the target meeting is initiated by the second application;

when the application installation state is an application uninstallation state, installing the second application, and logging in the second application according to an application account identifier; the application account identification and the conference identification of the target conference have an identification mapping relation;

in the second logged application, acquiring meeting detail information corresponding to the meeting identification according to the identification mapping relation;

and entering the target conference in the second application according to the conference detail information.

2. The method of claim 1, wherein the application installation state comprises an application uninstalled state and an application installed state;

the step of responding to the conference joining operation aiming at the target conference in the first application and acquiring the application installation state of the second application comprises the following steps:

responding to the conference entering operation aiming at the target conference in the first application, and starting the second application based on an application external interface of the second application;

when the second application is failed to be started, acquiring the uninstalled state of the application;

and when the second application is successfully started, acquiring the installed state of the application.

3. The method of claim 1, wherein the obtaining the application installation state of the second application in response to the conference joining operation of the first application for the target conference comprises:

responding to the identification operation of the identification code of the target conference in the first application to obtain a website identification result;

acquiring meeting invitation information of the target meeting according to the meeting identification in the website identification result;

outputting a conference entrance page aiming at the target conference according to the conference invitation information;

and responding to the conference entering operation aiming at the conference entrance page, and acquiring the application installation state of the second application.

4. The method of claim 1, further comprising:

synchronizing the conference identifier and the application account identifier of the target conference to an application server of the second application, so that the application server stores the identifier mapping relationship between the conference identifier and the application account identifier;

in the second logged application, obtaining meeting detail information corresponding to the meeting identifier according to the identifier mapping relationship, including:

sending conference entering request information to the application server based on the second logged application, so that the application server obtains the conference detail information of the target conference according to the conference entering request information and the identification mapping relation;

and acquiring the meeting detail information sent by the application server.

5. The method of claim 4, wherein synchronizing the meeting identification and the application account identification of the target meeting to an application server of the second application comprises:

outputting a login selection page; the login selection page comprises a first application login control and an external account login control;

when the selection operation aiming at the first application login control in the login selection page is responded, taking the account identification of the first application as the application account identification, and synchronizing the conference identification and the application account identification to the application server;

when the selection operation aiming at the external account login control in the login selection page is responded, an account identification acquisition page is output, an input account character string is acquired in the account identification acquisition page and is used as the application account identification, and the conference identification and the application account identification are synchronized to the application server.

6. The method of claim 5, wherein installing the second application and logging in the second application according to an application account identifier comprises:

installing the second application;

logging in the second application based on the first application when the application account identification is the account identification of the first application;

and when the application account identification is the account character string, logging in the second application based on the account character string.

7. The method of claim 6, wherein the sending conference request information to the application server based on the logged second application, so that the application server obtains the conference detail information of the target conference according to the conference request information and the identifier mapping relationship, comprises:

when successful login of the second application based on the first application is detected, generating meeting entrance request information; the conference joining request information carries a mapping account identifier corresponding to the application account identifier; the mapping account identification is obtained by registering the first application in the second application;

sending the conference joining request information to the application server, so that the application server obtains the conference detail information of the target conference according to the mapping account identification and the identification mapping relation carried by the conference joining request information; the conference detail information is acquired by the application server according to the conference identifier; the conference identifier is acquired by the application server according to the identifier mapping relation and the application account identifier; the application account identification is obtained by the application server according to the mapping account identification carried by the conference joining request information.

8. The method of claim 6, wherein the sending conference request information to the application server based on the logged second application, so that the application server obtains the conference detail information of the target conference according to the conference request information and the identifier mapping relationship, comprises:

when the second application is detected to be successfully logged in based on the account character string, generating meeting entering request information; the conference joining request information carries the account character string;

sending the conference joining request information to the application server, so that the application server obtains the conference detail information of the target conference according to the account character string carried by the conference joining request information and the identifier mapping relation; the conference detail information is acquired by the application server according to the conference identifier; the conference identifier is obtained by the application server according to the account character string carried by the conference joining request information and the identifier mapping relation.

9. The method of claim 4, wherein synchronizing the meeting identification and the application account identification of the target meeting to an application server of the second application comprises:

acquiring an account identifier of a second account having a binding relationship with the first account, and taking the account identifier as the application account identifier; the first account is a user account of the first application; the second account is a user account of the second application;

synchronizing the conference identifier and the application account identifier to the application server;

the installing the second application and logging in the second application according to the application account identification comprises the following steps:

and installing the second application, and logging in the second application according to the second account.

10. The method of claim 4, further comprising:

when the conference detail information is detected to successfully enter the target conference, generating conference entering prompt information;

and sending the conference entering prompt information to the application server so that the application server deletes the identifier mapping relation between the stored application account identifier and the conference identifier.

11. The method of claim 1, further comprising:

outputting an application download page;

downloading an application installation data package of the second application in the application download page;

the installing the second application comprises:

installing the second application based on the application installation data package.

12. The method of claim 1, wherein entering the target meeting in the second application according to the meeting detail information comprises:

outputting a conference entrance notification page aiming at the target conference in the second application according to the conference detail information;

and responding to the confirmation operation aiming at the conference entrance notification page, and entering the target conference.

13. The method of claim 1, further comprising:

when the application installation state is an application installation state, starting the second application based on an application external interface of the second application;

entering the target conference in the initiated second application.

14. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1-13.

15. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method according to any one of claims 1-13.

Images