CN113518198B - Session interface display method, conference interface display method, device and electronic equipment - Google Patents

Abstract

The disclosure relates to a session interface display method, a conference interface display device and electronic equipment, and belongs to the technical field of computers. The method comprises the following steps: a conference interface of a conference is displayed, a first query request is sent to a server in response to a session initiation instruction in the conference interface, and the server is used for returning a first session identifier when the first session identifier corresponding to the conference identifier is queried; receiving a first session identifier returned by the server; and displaying a session interface corresponding to the first session identifier. According to the method provided by the embodiment of the disclosure, under the condition that the first account participates in the conference, the session corresponding to the participating conference can be determined through the corresponding relation between the conference identifier and the session identifier, so that the session interface corresponding to the session is displayed, the account participating in the conference can interact based on the existing session, and a new session does not need to be additionally established, so that session resources are saved.

Description

Session interface display method, conference interface display method, device and electronic equipment

Technical Field

The disclosure relates to the technical field of computers, and in particular relates to a session interface display method, a conference interface display device and electronic equipment.

Background

With the development of computer technology, conference applications are becoming more and more widespread, and online conferences of multiple people can be realized through the conference applications. In general, when multiple persons are involved in an online conference, a session may need to be performed between participants, and how to implement a session between participants in the online conference is a problem that needs to be solved.

Disclosure of Invention

The disclosure provides a session interface display method, a session interface display device and electronic equipment, so that session resources are saved.

According to an aspect of the embodiments of the present disclosure, there is provided a session interface display method, including:

displaying a conference interface of a conference, wherein a participation account list of the conference comprises a first account logged in by a local terminal device;

responding to a session initiation instruction in the conference interface, sending a first query request to a server, wherein the first query request carries a conference identifier of the conference, and the server is used for returning the first session identifier when inquiring the first session identifier corresponding to the conference identifier;

receiving the first session identifier returned by the server;

and displaying a session interface corresponding to the first session identifier, wherein the session interface is a session interface corresponding to the first session indicated by the first session identifier, and the participating account of the first session at least comprises accounts in the participating account list.

In some embodiments, the displaying the conference interface of the conference includes:

under the condition that the session interface is displayed, a first session creation request is sent to the server in response to a session creation instruction in the session interface, the first session creation request carries the first account number and the first session identifier corresponding to the session interface, the server is used for receiving the first session creation request, creating the conference and acquiring the conference identifier, establishing a corresponding relation between the conference identifier and the first session identifier, adding the first account number into the conference, and returning the conference identifier;

receiving the conference identification returned by the server;

and displaying the conference interface corresponding to the conference identifier.

In some embodiments, the first session creation request further carries a second account, the second account being an account in the participating accounts of the first session; the server is further configured to send a first conference participation request to the terminal logged in by the second account, where the first conference participation request is used to request the corresponding second account to participate in the conference, and add the second account that agrees to participate in the conference to the conference.

In some embodiments, before the displaying the conference interface of the conference, the session interface displaying method further includes:

displaying the session interface, and displaying a conference entrance of the conference in the session interface;

the conference interface for displaying the conference comprises:

and responding to the confirmation operation of the conference entrance, and displaying a conference interface of the conference.

In some embodiments, before the displaying the conference interface of the conference, the session interface displaying method further includes:

displaying at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account;

and responding to the triggering operation of the session options corresponding to the first historical conference record, displaying the session interface, wherein the participation account of the first session corresponding to the session interface comprises the participation account contained in the first historical conference record.

In some embodiments, the responding to the triggering operation of the session options corresponding to the first historical conference record displays the session interface, including:

responding to a triggering operation of session options corresponding to the first historical conference record, sending a second query request to the server, wherein the second query request carries a historical conference identifier, the historical conference identifier is used for indicating a conference recorded by the first historical conference record, the server is used for receiving the second query request, and returning to the first session identifier when the session identifier corresponding to the historical conference identifier is inquired as the first session identifier;

Receiving the first session identifier returned by the server;

and displaying the session interface corresponding to the first session identifier.

In some embodiments, after the second query request is sent to the server in response to the triggering operation of the session option corresponding to the first historical conference record, the session interface display method further includes:

receiving a first reminding message returned by the server, wherein the first reminding message is used for indicating that the server does not inquire a session identifier corresponding to the historical conference identifier;

a first session creation request is sent to a server, the first session creation request carries a participation account included in the first history meeting record, the server is used for receiving the first session creation request, creating the first session and acquiring the first session identifier, returning the first session identifier, and the participation account of the first session includes the participation account included in the first history meeting record;

receiving the first session identifier returned by the server;

and displaying the session interface corresponding to the first session identifier.

In some embodiments, before the displaying the conference interface of the conference, the session interface displaying method further includes:

Displaying at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account;

the conference interface for displaying the conference comprises:

responding to triggering operation of meeting options corresponding to a first historical meeting record, sending a second meeting creation request to the server, wherein the second meeting creation request carries the first account and a third account, the third account is a participation account contained in the first historical meeting record, and the server is used for receiving the second meeting creation request, creating the meeting, acquiring the meeting identifier and returning the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

receiving the conference identification returned by the server;

and displaying the conference interface corresponding to the conference identifier.

In some embodiments, the second meeting creation request also carries a historical meeting identification for indicating the meeting recorded by the first historical meeting record; the server is further configured to establish a correspondence between the conference identifier and the first session identifier when it is queried that the session identifier corresponding to the historical conference identifier is the first session identifier.

In some embodiments, after the sending the first query request to the server in response to the session initiation instruction in the conference interface, the session interface display method further includes:

receiving a second reminding message returned by the server, wherein the second reminding message is used for indicating that the server does not inquire a session identifier corresponding to the conference identifier;

a second session creation request is sent to the server, the second session creation request carries an account number included in the participation account number list, the server is used for receiving the second session creation request, creating a second session, acquiring a second session identifier, establishing a corresponding relation between the session identifier and the second session identifier, returning to the second session identifier, and the participation account number of the second session includes the account number included in the participation account number list;

Receiving a second session identifier returned by the server;

and displaying a session interface corresponding to the second session identifier.

In some embodiments, the displaying the session interface corresponding to the session identifier includes:

and displaying the conference interface as the session interface in a switching way.

In some embodiments, after the conference interface is displayed as the session interface, the session interface display method further includes:

and in response to detecting a presentation instruction of the conference interface in the session interface, switching and displaying the session interface as the conference interface.

According to another aspect of the embodiments of the present disclosure, there is provided a session interface display method, including:

displaying at least one history meeting record corresponding to a first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account, and the first account is an account logged in by a local terminal device;

and responding to the triggering operation of the session options corresponding to the first historical conference record, displaying a session interface, wherein the participation accounts of the first session corresponding to the session interface comprise the participation accounts contained in the first historical conference record.

According to still another aspect of the embodiments of the present disclosure, there is provided a conference interface display method including:

displaying at least one history meeting record corresponding to a first account and meeting options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account, and the first account is an account logged in by a local terminal device;

responding to triggering operation of meeting options corresponding to a first historical meeting record, sending a second meeting creation request to a server, wherein the second meeting creation request carries the first account and a third account, the third account is a participation account contained in the first historical meeting record, and the server is used for receiving the second meeting creation request, creating the meeting, acquiring the meeting identifier and returning the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

Receiving the conference identification returned by the server;

and displaying a conference interface corresponding to the conference identifier.

According to still another aspect of the embodiments of the present disclosure, there is provided a session interface display apparatus including:

the conference system comprises a display unit, a display unit and a control unit, wherein the display unit is configured to execute a conference interface for displaying a conference, and a participation account list of the conference comprises a first account logged in by local equipment;

a sending unit, configured to perform a response to a session initiation instruction in the conference interface, and send a first query request to a server, where the first query request carries a conference identifier of the conference, and the server is configured to return a first session identifier corresponding to the conference identifier when querying the first session identifier;

the receiving unit is configured to receive the first session identifier returned by the server;

the display unit is further configured to display a session interface corresponding to the first session identifier, where the session interface is a session interface corresponding to a first session indicated by the first session identifier, and the participating account of the first session at least includes an account in the participating account list.

In some embodiments, the display unit includes:

a sending subunit, configured to perform sending, in response to a meeting creation instruction in the session interface, a first meeting creation request to the server under the condition that the session interface is displayed, where the first meeting creation request carries the first account number and the first session identifier corresponding to the session interface, and the server is configured to receive the first meeting creation request, create the meeting and obtain the meeting identifier, establish a correspondence between the meeting identifier and the first session identifier, add the first account number to the meeting, and return the meeting identifier;

the receiving subunit is configured to receive the meeting identification returned by the server;

and the display subunit is configured to display the conference interface corresponding to the conference identifier.

In some embodiments, the first session creation request further carries a second account, the second account being an account in the participating accounts of the first session; the server is further configured to send a first conference participation request to the terminal logged in by the second account, where the first conference participation request is used to request the corresponding second account to participate in the conference, and add the second account that agrees to participate in the conference to the conference.

In some embodiments, the display unit is further configured to perform displaying the session interface in which the conference entry of the conference is displayed; and responding to the confirmation operation of the conference entrance, and displaying a conference interface of the conference.

In some embodiments, the display unit is further configured to perform displaying at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record, where the history meeting record is used for recording meetings in which the first account participates; and responding to the triggering operation of the session options corresponding to the first historical conference record, displaying the session interface, wherein the participation account of the first session corresponding to the session interface comprises the participation account contained in the first historical conference record.

In some embodiments, the display unit includes:

a sending subunit, configured to perform a triggering operation in response to a session option corresponding to the first historical conference record, and send a second query request to the server, where the second query request carries a historical conference identifier, the historical conference identifier is used to indicate a conference recorded by the first historical conference record, and the server is used to receive the second query request, and return the first session identifier if the session identifier corresponding to the historical conference identifier is queried as the first session identifier;

A receiving subunit configured to perform receiving the first session identifier returned by the server;

and the display subunit is configured to display the session interface corresponding to the first session identifier.

In some embodiments, the receiving subunit is further configured to perform receiving a first alert message returned by the server, where the first alert message is used to indicate that the server does not query the session identifier corresponding to the historical conference identifier;

the sending subunit is further configured to send a first session creation request to a server, where the first session creation request carries a participation account included in the first history conference record, and the server is configured to receive the first session creation request, create the first session, obtain the first session identifier, and return the first session identifier, where the participation account of the first session includes a participation account included in the first history conference record;

the receiving subunit is further configured to perform receiving the first session identifier returned by the server;

the display subunit is further configured to perform displaying the session interface corresponding to the first session identifier.

In some embodiments, the display unit is further configured to perform displaying at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, where the history meeting record is used for recording meetings in which the first account participates;

the display unit includes:

a sending subunit, configured to perform a triggering operation in response to a meeting option corresponding to a first historical meeting record, send a second meeting creation request to the server, where the second meeting creation request carries the first account and a third account, the third account is a participating account included in the first historical meeting record, and the server is configured to receive the second meeting creation request, create the meeting, acquire the meeting identifier, and return the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

the receiving subunit is configured to receive the meeting identification returned by the server;

And the display subunit is configured to display the conference interface corresponding to the conference identifier.

In some embodiments, the second meeting creation request also carries a historical meeting identification for indicating the meeting recorded by the first historical meeting record; the server is further configured to establish a correspondence between the conference identifier and the first session identifier when it is queried that the session identifier corresponding to the historical conference identifier is the first session identifier.

In some embodiments, the receiving unit is further configured to perform receiving a second alert message returned by the server, where the second alert message is used to indicate that the server does not query the session identifier corresponding to the conference identifier;

the sending unit is further configured to send a second session creation request to the server, where the second session creation request carries an account number included in the participating account number list, and the server is configured to receive the second session creation request, create a second session and obtain a second session identifier, establish a correspondence between the conference identifier and the second session identifier, and return the second session identifier, where a participating account number of the second session includes an account number included in the participating account number list;

The receiving unit is further configured to execute receiving a second session identifier returned by the server;

the display unit is further configured to display a session interface corresponding to the second session identifier.

In some embodiments, the display unit is configured to perform the switching display of the conference interface as the session interface.

In some embodiments, the display unit is further configured to perform a display of the session interface as the conference interface in response to detecting a presentation instruction to the conference interface in the session interface.

According to still another aspect of the embodiments of the present disclosure, there is provided a session interface display apparatus including:

the display unit is configured to execute and display at least one history meeting record corresponding to a first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording a meeting in which the first account participates, and the first account is a participating account logged in by a local terminal device;

the display unit is further configured to execute a triggering operation for responding to a session option corresponding to a first historical conference record, and display a session interface, wherein the participation account of the first session corresponding to the session interface comprises the participation account contained in the first historical conference record.

According to still another aspect of the embodiments of the present disclosure, there is provided a conference interface display apparatus including:

the display unit is configured to display at least one history meeting record corresponding to a first account and meeting options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings in which the first account participates, and the first account is an account logged in by a local terminal device;

a sending unit configured to perform a triggering operation in response to a meeting option corresponding to a first historical meeting record, send a second meeting creation request to a server, where the second meeting creation request carries the first account and a third account, the third account is a participating account included in the first historical meeting record, and the server is configured to receive the second meeting creation request, create the meeting, acquire the meeting identifier, and return the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

The receiving unit is configured to receive the meeting identification returned by the server;

the display unit is further configured to display a conference interface corresponding to the conference identifier.

According to still another aspect of the embodiments of the present disclosure, there is provided an electronic device including:

one or more processors;

volatile or non-volatile memory for storing the one or more processor-executable instructions;

wherein the one or more processors are configured to perform the session interface display method or the conference interface display method of the above aspect.

According to still another aspect of the embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the session interface display method or the conference interface display method described in the above aspects.

According to yet another aspect of embodiments of the present disclosure, there is provided a computer program product, which when executed by a processor of an electronic device, causes the electronic device to perform the session interface display method or the conference interface display method of the above aspects.

According to the method, the device and the electronic equipment provided by the embodiment of the disclosure, under the condition that the first account participates in the conference, the session corresponding to the participating conference can be determined through the corresponding relation between the conference identifier and the session identifier, so that the session interface corresponding to the session is displayed, the account participating in the conference can interact based on the existing session, and a new session does not need to be additionally established, so that session resources are saved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a schematic diagram illustrating an implementation environment according to an example embodiment.

Fig. 2 is a flow chart illustrating a method of session interface display according to an exemplary embodiment.

Fig. 3 is a flow chart illustrating a method of session interface display according to an exemplary embodiment.

FIG. 4 is a schematic diagram of a session interface, shown according to an example embodiment.

Fig. 5 is a schematic diagram of a conference interface shown in accordance with an exemplary embodiment.

FIG. 6 is a schematic diagram of a session interface shown according to an example embodiment.

Fig. 7 is a flowchart illustrating a session interface display method according to an exemplary embodiment.

Fig. 8 is a flowchart illustrating a session interface display method according to an exemplary embodiment.

Fig. 9 is a schematic diagram of a recording display interface, according to an example embodiment.

Fig. 10 is a flowchart illustrating a conference interface display method according to an exemplary embodiment.

Fig. 11 is a flowchart illustrating a session interface display method according to an exemplary embodiment.

FIG. 12 is a flowchart illustrating a client-based display of an interface according to an exemplary embodiment.

FIG. 13 is a schematic diagram of a primary interface, according to an example embodiment.

Fig. 14 is a block diagram illustrating a session interface display apparatus according to an exemplary embodiment.

Fig. 15 is a block diagram illustrating a session interface display apparatus according to an exemplary embodiment.

Fig. 16 is a block diagram illustrating a session interface display apparatus according to an exemplary embodiment.

Fig. 17 is a block diagram illustrating a conference interface display device according to an exemplary embodiment.

Fig. 18 is a block diagram of a terminal according to an exemplary embodiment.

Fig. 19 is a block diagram of a server, according to an example embodiment.

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description of the present disclosure and the claims and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

The terms "at least one," "a plurality," "each," "any" as used herein, at least one includes one, two or more, a plurality includes two or more, and each refers to each of a corresponding plurality, any of which refers to any of the plurality. For example, the plurality of accounts includes 3 accounts, and each refers to each of the 3 accounts, and any one refers to any one of the 3 accounts, which can be the first account, or the second account, or the third account.

The user information (including but not limited to user equipment information, user personal information, etc.) related to the present disclosure is information authorized by the user or sufficiently authorized by each party.

The session interface display method and the conference interface display method provided by the embodiments of the present disclosure are executed by an electronic device, and in some embodiments, the electronic device is a terminal, for example, the terminal is a mobile phone, a tablet computer, a computer, or other types of terminals. In some embodiments, the electronic device is a server, for example, the server is a server, or a server cluster composed of several servers, or is a cloud computing service center.

FIG. 1 is a schematic diagram of an implementation environment provided in accordance with an exemplary embodiment, the implementation environment comprising: terminal 101 andserver 102, terminal 101 andserver 102 are connected via a network, and can interact withserver 102.

In some embodiments, a client served by theserver 102 is installed on the terminal 101, and the terminal 101 can implement functions such as online conferences, sessions, and the like through the client. For example, the client is a conference application having a function of an online conference, but of course, the conference application can also have other functions, such as a session function, a shopping function, a navigation function, a game function, and the like. In some embodiments,server 102 is a background server for the client or is a cloud server that provides services such as cloud computing and cloud storage.

In some embodiments, the implementation environment includes a plurality ofterminals 101 and aserver 102, each of the plurality ofterminals 101 having a client installed thereon, theserver 102 for providing services to the client.

The plurality ofterminals 101 log in the client based on the respective account numbers, and can join the conference based on the client so as to enable communication among the plurality of account numbers participating in the conference; or, based on the client being able to join the session, messages can be sent to each other between multiple accounts in the session. Wherein the conference or the session is created by theserver 102.

The method provided by the embodiment of the disclosure can be applied to various scenes.

For example, in an office conference scenario.

In an office scene, a plurality of terminals are corresponding to a plurality of staff, each terminal is provided with a client, each terminal logs in the client based on an account, the plurality of terminals join in a conference based on the client, by adopting the method for displaying the session interface provided by the embodiment of the disclosure, the plurality of accounts logged in by the plurality of terminals participate in the conference, based on the conference interface of the conference, a video conference or a voice conference can be realized among the plurality of accounts, and in the conference process, if a message needs to be sent or checked among the plurality of accounts, a first session identifier corresponding to the conference identifier of the conference is queried, so that a session among staff participating in the conference is realized based on the session interface corresponding to the first session identifier, for example, any participant can send a file or a file message to other participants based on the session interface, or the participant can check a file, a text message and the like sent by other participants based on the session interface.

For another example, in an online lecture scenario.

The teacher terminal logs in the client based on the account number, the student terminal logs in the client based on the account number, the teacher terminal and the plurality of student terminals are added into the conference based on the client, the session interface display method provided by the embodiment of the disclosure is adopted, online communication is carried out between a teacher and students participating in the conference so as to realize online teaching, and in the conference process, if a message needs to be sent or checked among the plurality of account numbers, a first session identifier corresponding to a conference identifier of the conference is queried so as to realize participation in a session between the teacher and the students based on a session interface corresponding to the first session identifier, for example, a teacher can send a message to the students based on the session interface, and the students can check the message sent by the teacher based on the session interface.

Fig. 2 is a flowchart illustrating a session interface display method, see fig. 2, performed by a terminal, according to an exemplary embodiment, comprising the steps of:

201. the terminal displays a conference interface of a conference, and the participation account list of the conference comprises a first account logged in by the local terminal equipment.

In the embodiment of the disclosure, the conference is an online conference, multiple accounts can participate in the conference, and terminals logged in by the multiple accounts can interact based on the conference, for example, an audio conference or a video conference can be performed between the multiple accounts participating in the conference. For example, a terminal that participates in any account login of the conference sends out audio data or video data, and other terminals that participate in other accounts login of the conference can receive the audio data or video data and play the audio data or video data. During the meeting, the account number can participate in the meeting in a plurality of ways, for example, the account number of the meeting is added to the meeting, or the account number participating in the meeting is invited to be added to the meeting, etc. The conference is time-efficient, and if the conference results, the conference cannot be added to the conference, and the conference interface of the conference cannot be displayed. The conference is provided with a participation account list, and accounts participating in the conference are all contained in the participation account list.

The conference interface is used for displaying information in the conference, for example, a plurality of accounts, video data or function options and the like participating in the conference are displayed in the conference interface. For example, the function options include a microphone option, a camera option, etc., and the user can turn off or turn on the microphone, turn off or turn on the camera based on the function options displayed by the terminal.

202. The terminal responds to a session initiation instruction in a conference interface, a first query request is sent to a server, the first query request carries a conference identifier of a conference, and the server is used for returning the first session identifier when the first session identifier corresponding to the conference identifier is queried.

Wherein the meeting identifier is used to characterize the meeting, the meeting identifier is any form of identifier, for example, the meeting identifier is a serial number displayed according to a target format, a meeting name of the meeting, and the like. The first session identifier is used to characterize a first session corresponding to the conference, where the first session identifier is any form of identifier, for example, the first session identifier is a serial number displayed in a target format, a session name of the session, and so on.

In the disclosed embodiments, session identification is used to characterize a session. The participating accounts of the session can comprise a plurality of accounts, the session provides a platform for message interaction for the plurality of accounts, clients logged in by the plurality of accounts can participate in the session, messages can be mutually sent among the plurality of accounts participating in the same session, namely the session is equivalent to a virtual chat room established among the plurality of accounts, and the plurality of accounts participating in the session can chat in the virtual chat room. For example, the terminal with any account number logged in sends a message to the terminal with other account numbers logged in based on the session interface, or displays the message sent by the terminal with other account numbers logged in for the user to view. In addition, the session can be maintained, and if the terminal is closed to display the session interface under the condition that any account logs in, the session interface can be displayed again through the entrance of the session, and the message contained in the session interface can be displayed for the user to view.

In the embodiment of the disclosure, a correspondence between session identifiers and conference identifiers is stored in a server, if any session identifier corresponds to a session identifier, it indicates that a conference corresponding to the session identifier has a corresponding session, and the session corresponding to the conference is a session indicated by the session identifier corresponding to the session identifier. In the process of participating in the conference, if a user wants to initiate a session based on the participating conference, an operation is performed on a conference interface to initiate a session initiation instruction, a terminal responds to the session initiation instruction in the conference interface and interacts with a server, the server inquires the corresponding relation between the conference identification and the session identification so as to determine whether the conference identification of the conference has a corresponding session identification or not, whether the conference has a corresponding session or not is determined, and under the condition that the server inquires a first session identification corresponding to the conference identification of the conference, the inquired first session identification is returned to the terminal so that a subsequent terminal can display the session interface corresponding to the first session identification.

203. The terminal receives a first session identifier returned by the server, and displays a session interface corresponding to the first session identifier, wherein the session interface is a session interface corresponding to the first session indicated by the first session identifier, and the participating account of the first session at least comprises accounts in a participating account list.

After the terminal receives the first session identifier returned by the server, the terminal indicates that the server has queried the first session identifier corresponding to the conference identifier of the conference, i.e. indicates that the conference has a corresponding session. The account numbers of the first session indicated by the first session identification comprise the account numbers of the conference, namely, the first session is established between the account numbers of the conference, so that the session between the account numbers of the conference can be realized through the session interface corresponding to the first session without additionally establishing a new session, thereby saving session resources.

According to the method provided by the embodiment of the disclosure, under the condition that the first account participates in the conference, the session corresponding to the participating conference can be determined through the corresponding relation between the conference identifier and the session identifier, so that the session interface corresponding to the session is displayed, the account participating in the conference can interact based on the existing session, and a new session does not need to be additionally established, so that session resources are saved.

In some embodiments, displaying a conference interface for a conference includes:

under the condition of displaying a session interface, responding to a meeting creation instruction in the session interface, sending a first meeting creation request to a server, wherein the first meeting creation request carries a first account number and a first meeting identifier corresponding to the session interface, and the server is used for receiving the first meeting creation request, creating a meeting, acquiring the meeting identifier, establishing a corresponding relation between the meeting identifier and the first meeting identifier, adding the first account number into the meeting, and returning the meeting identifier;

Receiving a meeting identifier returned by the server;

and displaying a conference interface corresponding to the conference identifier.

Under the condition that a session interface is displayed, a conference is initiated based on the session interface, and a corresponding relation between a conference identifier and the session identifier is established, so that when any account number which subsequently participates in the conference needs to initiate the session, the corresponding session can be determined based on the established corresponding relation, the account number which participates in the conference can interact based on the session which is established before, and a new session does not need to be additionally established, thereby saving session resources.

In some embodiments, the first session creation request further carries a second account, the second account being an account of the participating accounts of the first session; the server is further configured to send a first conference participation request to a terminal logged in by the second account, where the first conference participation request is used to request the corresponding second account to participate in the conference, and add the second account agreeing to participate in the conference.

The server interacts with the terminal logged in by the second account to maintain the conference, and adds the second account which agrees to participate in the conference into the conference, so that management of the created conference is realized.

In some embodiments, before displaying the conference interface of the conference, the session interface display method further includes:

Displaying a session interface, and displaying a conference entrance of a conference in the session interface;

a conference interface for displaying a conference, comprising:

and in response to the confirmation operation of the conference entrance, displaying a conference interface of the conference.

The switching display between the session interface and the conference interface can be realized through the conference portal released in the conference, and the interface switching style is enriched, so that the convenience of interface switching is improved.

In some embodiments, before displaying the conference interface of the conference, the session interface display method further includes:

displaying at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account;

and responding to the triggering operation of the session options corresponding to the first historical conference record, displaying a session interface, wherein the participation accounts of the first session corresponding to the session interface comprise the participation accounts contained in the first historical conference record.

The method provided by the embodiment of the disclosure provides a method for initiating a session by using a history conference record, and a corresponding session interface is displayed by using a displayed history conference record, namely a new session initiation mode is realized, and convenience in session initiation is improved.

In some embodiments, in response to a triggering operation of a session option corresponding to the first historical conference record, displaying a session interface includes:

responding to the triggering operation of the session options corresponding to the first historical conference record, sending a second query request to the server, wherein the second query request carries a historical conference identifier, the historical conference identifier is used for indicating the conference recorded by the first historical conference record, the server is used for receiving the second query request, and returning to the first session identifier when the session identifier corresponding to the historical conference identifier is queried to be the first session identifier;

receiving a first session identifier returned by the server;

and displaying a session interface corresponding to the first session identifier.

By inquiring the session identifier corresponding to the history meeting identifier by the server, whether the history meeting record corresponds to a session or not is determined, and interaction is performed based on the existing session without additionally creating a new session under the condition that the history meeting record is determined to have the corresponding session, so that session resources are saved.

In some embodiments, after sending the second query request to the server in response to a triggering operation of the session option corresponding to the first historical conference record, the session interface display method further includes:

Receiving a first reminding message returned by the server, wherein the first reminding message is used for indicating that the server does not inquire a session identifier corresponding to the history meeting identifier;

the method comprises the steps that a first session creation request is sent to a server, the first session creation request carries a participation account number contained in a first historical conference record, the server is used for receiving the first session creation request, creating a first session, acquiring a first session identifier, returning the first session identifier, and the participation account number of the first session comprises the participation account number contained in the first historical conference record;

receiving a first session identifier returned by the server;

and displaying a session interface corresponding to the first session identifier.

Under the condition that the server does not inquire the session identifier corresponding to the history meeting identifier, namely the history meeting record does not have a corresponding session, the terminal requests the server to create the session through interaction with the server only under the condition that the history meeting record does not have a corresponding session, and displays a session interface corresponding to the session created by the server, so that the created session is prevented from being repeated, session resources are saved, the server is convenient to manage the session, and the server does not need to invite accounts to create the session respectively, so that the convenience of session creation is improved.

In some embodiments, before displaying the conference interface of the conference, the session interface display method further includes:

displaying at least one historical conference record corresponding to the first account and conference options corresponding to each historical conference record, wherein the historical conference records are used for recording conferences participated by the first account;

a conference interface for displaying a conference, comprising:

responding to triggering operation of meeting options corresponding to the first historical meeting record, sending a second meeting creation request to a server, wherein the second meeting creation request carries a first account and a third account, the third account is a participation account contained in the first historical meeting record, and the server is used for receiving the second meeting creation request, creating a meeting, acquiring a meeting identifier and returning the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

receiving a meeting identifier returned by the server;

and displaying a conference interface corresponding to the conference identifier.

The method provided by the embodiment of the disclosure provides a mode of initiating a new conference by using the history conference record, displays the history conference record corresponding to the account number, initiates a new conference by using the displayed history conference record, and displays the conference interface of the conference, thereby improving the convenience of conference initiation.

In some embodiments, the second meeting creation request also carries a historical meeting identification for indicating the meeting recorded by the first historical meeting record; the server is further configured to establish a correspondence between the conference identifier and the first session identifier when the session identifier corresponding to the historical conference identifier is queried as the first session identifier.

By inquiring the first session identifier corresponding to the history session identifier, a corresponding relation between the newly created session identifier corresponding to the conference and the first session identifier is established, so that the corresponding first session is searched through the corresponding relation in the subsequent conference participation process, and a new session is not required to be created, thereby saving session resources.

In some embodiments, after sending the first query request to the server in response to a session initiation instruction in the conference interface, the session interface display method further includes:

receiving a second reminding message returned by the server, wherein the second reminding message is used for indicating that the server does not inquire a session identifier corresponding to the session identifier;

the method comprises the steps that a second session creation request is sent to a server, the second session creation request carries an account number included in a participation account number list, the server is used for receiving the second session creation request, creating a second session and obtaining a second session identifier, a corresponding relation between the session identifier and the second session identifier is established, the second session identifier is returned, and the participation account number of the second session includes the account number included in the participation account number list;

Receiving a second session identifier returned by the server;

and displaying a session interface corresponding to the second session identifier.

Under the condition that the conference does not correspond to the session, a new session is created for the conference, and the session between accounts participating in the conference can be realized through a session interface corresponding to the created session, namely a message container is provided for the conference, so that messages can be sent between the accounts participating in the conference. And the corresponding relation between the conference identifier and the session identifier corresponding to the newly created session is established, namely, the association relation between the conference and the second session is created, so that the existing session interface of the second session is displayed through the corresponding relation later, and the new session is not required to be created, thereby saving session resources.

In some embodiments, displaying a session interface corresponding to the session identifier includes:

and displaying the conference interface as a session interface in a switching way.

The conference interface is switched and displayed as the session interface, so that the free switching from the conference interface to the session interface is realized, and the session function is realized in the process of participating in the conference.

In some embodiments, after the conference interface is displayed as the session interface, the session interface display method further includes:

And in response to detecting a presentation instruction of the conference interface in the session interface, displaying the session interface as the conference interface in a switching manner.

Under the condition of displaying the session interface, when the display instruction of the session interface is detected, the session interface is switched and displayed as the session interface, namely, the effect of randomly switching the interface under the condition of participating in the conference is realized, namely, the session can be carried out at any time under the condition of participating in the conference, and the convenience of the online conference is improved.

Based on the embodiment shown in fig. 2, the terminal can initiate a conference through the session interface under the condition of displaying the session interface, and can realize any switching between the session interface and the session interface in the process of participating in the conference, and the specific process is described in the following embodiments.

Fig. 3 is a flowchart illustrating a session interface display method according to an exemplary embodiment, and referring to fig. 3, an execution body of the method includes a terminal and a server, including the steps of:

301. under the condition that a session interface is displayed, the terminal responds to a meeting creation instruction in the session interface, and sends a first meeting creation request to the server, wherein the first meeting creation request carries a first account number and a first session identifier corresponding to the session interface.

The first account is an account logged in by the terminal. In the embodiment of the present disclosure, the first session identifier is used to characterize the first session, the displayed session interface is a session interface corresponding to the first session, and the participating account number of the first session includes at least the first account number, and may further include other account numbers. Under the condition that the terminal logged in by the first account number displays a session interface, a user can initiate a conference creation process, and the terminal sends a conference creation request to the server so that the server can create a conference later.

In some embodiments, the process of conference creation is initiated by a conference option in the session interface, i.e., 301 includes: under the condition that a session interface is displayed, the terminal responds to the triggering operation of meeting options in the session interface and sends a first meeting creation request to the server, wherein the first meeting creation request carries a first account number and a first session identifier corresponding to the session interface.

Wherein the conference option is used to initiate a conference creation request. In some embodiments, the meeting option is displayed at any location of the session interface, such as in the upper right-hand corner of the session interface or in the lower left-hand corner of the session interface. The process of conference creation is initiated through the session options displayed by the session interface, so that convenience of conference creation can be improved.

In some embodiments, the first session creation request also carries a second account, the second account being an account of the participating accounts of the first session. For example, the second account carried by the first meeting creation request includes one or more.

Under the condition of displaying a session interface, all or part of accounts can be selected from the participating accounts of the first session to initiate the conference, so that any second account inviting to participate in the first session is realized to join the conference, and the flexibility of conference initiation is ensured.

In some embodiments, the conference is initiated by selecting a portion of the account number from the first session through a session option in the session interface, i.e., 301 includes: under the condition that a session interface is displayed, the terminal responds to the triggering operation of meeting options in the session interface, displays the participating account of the first session, selects a second account from the displayed accounts, responds to the confirmation operation of the selected second account, and sends a first meeting creation request to the server, wherein the first meeting creation request carries the first account, the second account and a first session identifier.

When a conference creation request is initiated based on a session interface, the participation accounts of the first session are displayed so as to select any account number from the participation accounts to initiate the conference creation request, namely, the conference can be initiated based on any account number in the participation accounts of the first session, so that the flexibility of conference initiation is improved.

For example, when a meeting creation request is initiated, the participating account number of the first session can also be displayed in a popup window, that is, the process of sending the meeting creation request to the server includes: and under the condition that the session interface is displayed, the terminal responds to the triggering operation of the meeting option in the session interface, displays a popup window and a confirmation option, displays the participating account number of the first session in the popup window, and responds to the triggering operation of the confirmation option when the second account number is selected, and sends a first meeting creation request to the server. The account included in the participating account of the first session is displayed in the popup window mode, so that a user can conveniently select a second account ready for inviting to a meeting from the displayed account, and a first meeting creation request is sent to the server through a confirmation option, and the user operation is facilitated.

In some embodiments, the session interface includes a plurality of regions, for example, the session interface includes a message presentation region for presenting messages sent between the participating accounts of the first session, a message input region for inputting messages, the messages being text messages, picture messages, files, or the like, through which messages can be sent to other accounts in the first session, and the sent messages are presented in the message presentation region.

As shown in the first diagram of fig. 4, asession option 401 is displayed in the upper right corner area of the session interface, in response to a clicking operation on thesession option 401, apopup window 402 and afirst confirmation option 403 are displayed, and in response to a clicking operation on thefirst confirmation option 403, a first session creation request is sent to the server, where the first session creation request carries the first account, the selected second account and the first session identifier, when any number of second accounts is selected, as shown in the second diagram of fig. 4. As shown in the first diagram of fig. 4, the session interface further displays amessage display area 404, amessage input area 405, and asecond confirmation option 406, and in response to clicking thesecond confirmation option 406, the message input in themessage input area 405 is sent to the participating account of the first session, and the input message is displayed in themessage display area 404. The conversation interface also displays expression options, picture options, file options and the like, wherein the expression options are used for sending expressions in the conversation interface, the picture options are used for sending pictures in the conversation interface, and the file options are used for sending files in the conversation interface.

302. The server receives a first meeting creation request, creates a meeting, acquires a meeting identifier of the meeting, establishes a corresponding relation between the meeting identifier and the first meeting identifier, adds a first account number into the meeting, and returns the meeting identifier to the terminal.

In the embodiment of the disclosure, the participating account list of any conference includes accounts participating in the conference, and after the conference is created, adding any account to the account list of the conference is equivalent to adding the account to the conference. After receiving the first meeting creation request, the server creates the meeting, wherein the first account is equivalent to the initiator of the meeting, and the server adds the first account into the participating account list of the meeting, namely, the first account is added into the meeting.

In the embodiment of the disclosure, a correspondence between conference identifiers and session identifiers is stored in a server, and in the correspondence, a conference indicated by any conference identifier is associated with a session indicated by a corresponding session identifier, that is, accounts participating in the conference indicated by the conference identifier are all participating accounts of the session corresponding to the corresponding session identifier. After the meeting identifier of the meeting is acquired, a corresponding relation between the meeting identifier and a first meeting identifier carried by a first meeting creation request is established, so that when any account subsequently participating in the meeting initiates a session, the corresponding session can be determined based on the established corresponding relation, and the accounts participating in the meeting can interact based on the first session which has been created before.

In some embodiments, the process of the server creating the meeting and obtaining the meeting identification of the meeting includes: the method comprises the steps that a conference is established by a server, a conference identifier is randomly generated for the conference, and the first account is added into a participation account list corresponding to the conference; or, a conference identification database is stored in the server, the conference identification database comprises a plurality of conference identifications, the conference identifications do not correspond to the conference, the server creates a conference, selects one conference identification from the conference identification database as the conference identification of the conference, and adds the first account number into a participation account number list corresponding to the conference.

In the embodiment of the disclosure, in the process of creating a conference, a participating account list is generated, and a conference identifier is associated with the participating account list, that is, the created conference has a corresponding participating account list and conference identifier, and adding any account to the participating account list is equivalent to adding the account to the conference.

In addition, the first session creation request also carries a second account, and the second account is an account in the participating accounts of the first session; the server interacts with the terminal logged in by the second account to invite the second account to join in the created conference, that is, the method further includes: the server sends a first participation meeting request to the terminal logged in by the second account, wherein the first participation meeting request is used for requesting the corresponding second account to participate in the meeting, and the second account which agrees to participate in the meeting is added into the meeting.

Because the second account carried by the first meeting creation request is the account selected by the user, the server sends a first meeting participation request to the terminal logged in by the second account, so that whether the second account participates in the meeting or not is confirmed based on the first meeting participation request, the server adds the second account which agrees to participate in the meeting to the meeting, and the second account which agrees to participate in the meeting is added to a participation account list of the meeting.

The server interacts with the terminal logged in by the second account to maintain the conference, and adds the second account which agrees to participate in the conference into the conference, so that management of the created conference is realized.

In some embodiments, the process of the server interacting with the terminal logging into the second account includes: the server sends a first conference participation request to a terminal logging in the second account, the first conference participation request carries a third reminding message, the terminal logging in the second account receives the first conference participation request, the third reminding message is displayed and used for reminding the first account to request to participate in the conference, an approval message is sent to the server in response to confirmation operation of the third reminding message, the server receives the approval message sent by the terminal logging in the second account, the approval message is used for indicating that the corresponding second account approves to participate in the conference, and the server adds the second account corresponding to the approval message into the conference.

For example, after receiving the first conference participation request, the terminal logged in by the second account displays a third reminding message, a confirmation option and a rejection option, and sends an agreement message to the server in response to the triggering operation of the confirmation option; and responding to the triggering operation of the rejection option, sending a rejection message to the server, wherein the rejection message is used for indicating that the corresponding second account number refuses to participate in the conference, and the server does not add the second account number into the conference.

303. And the terminal receives the conference identifier returned by the server and displays a conference interface corresponding to the conference identifier.

And when the terminal receives the conference identification returned by the server and indicates that the server has successfully created the conference, the terminal can display a conference interface corresponding to the conference so as to participate in the online conference based on the conference interface.

In some embodiments, the terminal is capable of displaying a conference interface through interaction with the server, that is, 303 includes: the terminal sends a first display request to the server, the first display request carries the conference identifier, the server receives the first display request, inquires first interface information corresponding to the conference identifier, sends the first interface information to the terminal, receives the first interface information, and renders the conference interface based on the first interface information.

The first interface information is used for describing the conference interface, for example, the first interface information is used for describing a plurality of display areas, a plurality of controls, display styles and the like in the conference interface. The first interface information is acquired in an interactive mode with the server, and the conference interface is rendered, so that the first interface information is not required to be stored in the terminal, and the storage resource of the terminal is saved.

In some embodiments, the accounts participating in the meeting are displayed in the meeting interface.

For example, a list of participating accounts is displayed in the conference interface, the list of participating accounts including accounts participating in the conference. The account numbers participating in the conference are displayed in the conference interface, so that information contained in the conference interface is enriched, and a user can conveniently view the account numbers participating in the conference.

In some embodiments, the conference interface includes a first display area and a second display area, the first display area is used for participating in accounts of the conference and status information of each account, and the second display area is used for displaying a list of participating accounts of the conference. The status information is used to indicate a status of the corresponding account, for example, status information of any account is used to indicate whether the account turns on a microphone, whether speaking is being performed, and so on. Different information is displayed in different display areas so as to enrich the display modes of the conference interface, and therefore the display effect of the conference interface is improved.

For example, if the conference is a video conference, the first display area is used for displaying video images of accounts participating in the conference and status information of each account; or the conference is an audio conference, and the first display area is used for displaying the accounts participating in the conference, the head portrait of each account and the state information.

In some embodiments, the conference interface further includes a plurality of function options for turning on or off different functions during participation in the conference.

For example, the multiple function options include a microphone option, a camera option, a sharing screen option, an invite option, a record option, a session option, a set option and a close option, wherein the microphone option is used for turning on or off a microphone, the camera option is used for turning on or relating to a camera, the sharing screen option is used for sharing content displayed on a screen to other accounts participating in the conference, the invite option is used for inviting the accounts to participate in the conference in the case of participating in the conference, the record option is used for recording content displayed on a conference interface or audio corresponding to the conference, the session option is used for initiating a display instruction of the session, and the set option is used for adjusting sound effects, video effects or settings of other contents of the conference. As shown in fig. 5, the conference interface displays afirst display area 501, asecond display area 502, and a plurality offunction options 503. The conference interface is provided with the function options, so that the conference interface can be used for displaying the function options, and the conference interface can be used for operating in the conference participation process, thereby improving the convenience of operation and improving the online conference effect.

In some embodiments, when the terminal displays the conference interface, responding to any account to join the conference, and displaying a fourth reminding message in the conference interface, wherein the fourth reminding message is used for reminding the account to join the conference. The fourth reminding message is displayed to remind the account to join the conference, so that the display style of the conference interface is enriched, and the display effect of the conference interface is improved.

For example, after joining the account number which agrees to participate in the conference, the server sends a fourth reminding message to the terminal which has participated in the conference, and the terminal receives the fourth reminding message sent by the server under the condition that a conference interface is displayed, and displays the fourth reminding message on the conference interface so as to remind that the account number is joined in the conference.

It should be noted that, in the embodiment of the present disclosure, the conference interface is displayed through the interaction between the terminal and the server, and in another embodiment, the terminal may display the conference interface of the conference in other manners without performing steps 301-303.

In some embodiments, the conference interface is displayed through a conference portal displayed in the session interface, that is, the method includes: the terminal displays a session interface, a conference entrance of the conference is displayed in the session interface, and the conference interface of the conference is displayed in response to the confirmation operation of the conference entrance.

The conference entrance is used for indicating the conference address of the conference, and the conference entrance can be added into the conference indicated by the conference entrance. The conference indicated by the conference entrance is initiated by a first account logging in the terminal or by other accounts participating in the first session corresponding to the session interface. For example, aconference portal 601 is displayed in the session interface, as shown in fig. 6.

In this embodiment of the present disclosure, the session interface is an interface corresponding to a first session, when any account participating in the first session initiates a conference based on the session interface, a conference portal of the conference is published to the first session, so that when a terminal logged in by each account participating in the first session displays the session interface, the published conference portal can be displayed in the session interface, and then any account participating in the first session can be added to the conference indicated by the conference portal based on the displayed conference portal, and the conference interface of the conference is displayed. The switching display between the session interface and the conference interface can be realized through the conference portal released in the conference, and the interface switching style is enriched, so that the convenience of interface switching is improved.

For example, according to steps 301-303, the terminal interacts with the server to initiate a conference, and issues a conference portal to the first session, so that the terminal logged in by each account participating in the first session can display the conference portal when displaying the session interface, and can join the conference based on the session portal displayed by the session interface to display the conference interface of the conference. For another example, the conference portal is initiated by other accounts participating in the first session corresponding to the session interface, and when the session interface is displayed, the terminal receives conference portals issued by other accounts, displays the conference portal in the session interface, and displays the conference interface of the conference based on that the displayed conference portal can be added into the conference indicated by the conference portal.

For example, based on the displayed conference portal, the terminal displays the conference interface through interaction with the server, that is, the process of displaying the conference interface based on the displayed conference portal includes: and the terminal responds to the confirmation operation of the conference entrance and sends an agreement message to the server, wherein the agreement message is used for indicating that the corresponding account agrees to participate in the conference indicated by the conference entrance, the server receives the agreement message sent by the terminal, and the account corresponding to the agreement message is added into the conference.

304. And the terminal responds to a session initiation instruction in the conference interface and sends a first query request to the server, wherein the first query request carries the conference identification of the conference.

The session initiation instruction is used for initiating a session, and the conference identifier is used for representing a conference corresponding to the conference interface. If a user wishes to initiate a session based on a participating conference, an operation is performed at the conference interface to initiate a session initiation instruction, and the terminal sends a first query request to the server in response to the session initiation instruction at the conference interface to determine whether the conference identifier of the conference has a corresponding session identifier, i.e. equivalent to determining whether the conference corresponds to a session, so as to enable a session function in the process of participating in the conference.

In some embodiments, the session is initiated through a session option in the conference interface, i.e., the 304 includes: and the terminal responds to the triggering operation of the session options in the conference interface and sends a first query request to the server, wherein the first query request carries the conference identification of the conference. The session options are displayed in the conference interface, so that the session can be initiated in the process of participating in the conference, and the convenience of session initiation is ensured.

305. And the server receives the first query request, and returns the first session identifier to the terminal when the session identifier corresponding to the conference identifier is queried as the first session identifier.

In the embodiment of the disclosure, after a corresponding relation between a conference identifier and a session identifier is stored in a server, the server queries the corresponding relation between the conference identifier and the session identifier based on the conference identifier after receiving a first query request, if the first session identifier corresponding to the conference identifier is queried, the conference indicated by the conference identifier is indicated to correspond to the first session indicated by the first session identifier, and then the first session identifier is sent to a terminal, so that a subsequent terminal can display a session interface corresponding to the first session identifier.

306. The terminal receives the first session identification returned by the server.

Because the corresponding relation between the conference identifier and the session identifier is stored in the server, the terminal queries the session identifier corresponding to the conference identifier through interaction with the server, so that the accuracy of the queried session identifier is ensured, the session interface corresponding to the existing session can be displayed later, a new session is not required to be created, and session resources are saved.

307. And the terminal switches and displays the conference interface as a session interface corresponding to the first session identifier.

After receiving the first session identifier sent by the server, the terminal indicates that the first session identifier corresponding to the session identifier is queried, and then switches the currently displayed session interface to a session interface corresponding to the first session identifier, so that a session can be performed with an account number participating in the first session based on the displayed session interface. The conference interface is switched and displayed as the session interface, so that the free switching from the conference interface to the session interface is realized, and the session function is realized in the process of participating in the conference. And the session interface is used as a message container of the conference, and can bear the message in the first session, so that the account numbers participating in the conference can send or inquire the message in the session interface.

In the embodiment of the disclosure, the terminal switches the displayed conference interface to the session interface, and at this time, the terminal can play the audio in the conference, that is, the conference interface is switched to the background, and only the conference interface is not displayed any more, but at this time, the terminal can also receive the audio in the conference and play the received audio.

In some embodiments, the terminal displays the session interface through interaction with the server, that is, 307 includes: the terminal sends a second display request to the server, the second display request carries a first session identifier, the server receives the second display request, inquires second interface information corresponding to the first session identifier, sends the second interface information to the terminal, receives the second interface information, renders the session interface based on the second interface information, and switches and displays the session interface as the session interface.

The second interface information is used for describing the session interface, for example, the second interface information is used for describing a plurality of display areas, a plurality of controls, display styles and the like in the session interface. The second interface information is acquired in an interactive mode with the server, and the conference interface is rendered, so that the second interface information is not required to be stored in the terminal, and the storage resource of the terminal is saved.

It should be noted that, in the embodiment of the present disclosure, the first session identifier corresponding to the meeting identifier is taken as an example for illustration, and in another embodiment, the session identifier corresponding to the meeting identifier may not be queried, that is, in the case that the session identifier corresponding to the meeting identifier is not queried, the following manner may be adopted to display the session interface.

In some embodiments, when the session identifier corresponding to the session identifier is not queried, a session is created for the session, and then a session interface corresponding to the created session is displayed, that is, the process of displaying the session interface includes: the terminal receives a second reminding message returned by the server, the second reminding message is used for indicating that the server does not inquire a session identifier corresponding to the conference identifier, a second session creation request is sent to the server, the second session creation request carries an account number included in the participation account number list, the server is used for receiving the second session creation request, creating a second session and acquiring the second session identifier, establishing a corresponding relation between the conference identifier and the second session identifier, returning the second session identifier to the terminal, receiving the second session identifier returned by the server by the terminal, and displaying a session interface corresponding to the second session identifier.

In the embodiment of the disclosure, the session identifier corresponding to the conference identifier is not queried, that is, the conference is not corresponding to a session, so in order to enable a session between accounts participating in the conference, a second session is created based on the accounts included in the conference participation account list, and the newly created second session participation accounts include the accounts included in the conference participation account list, so that the accounts participating in the conference subsequently can be subjected to the session based on the session interface corresponding to the second session. And establishing a corresponding relation between the conference identifier and a second session identifier corresponding to the second session, so that the corresponding relation which can be created later can be used for searching the corresponding session identifier, and a corresponding session interface can be displayed.

Under the condition that the conference does not correspond to the session, a new session is created for the conference, and the session between accounts participating in the conference can be realized through a session interface corresponding to the created session, namely a message container is provided for the conference, so that messages can be sent between the accounts participating in the conference. And the corresponding relation between the conference identifier and the session identifier corresponding to the newly created session is established, namely, the association relation between the conference and the second session is created, so that the existing session interface of the second session is displayed through the corresponding relation later, and the new session is not required to be created, thereby saving session resources.

As can be seen from the foregoing embodiments, when the server queries the session identifier corresponding to the conference identifier based on the first query request, it is possible to query the session identifier corresponding to the conference identifier, or it is also possible to not query the session identifier corresponding to the conference identifier, so after step 304, the terminal displays the session interface in different manners based on different results returned by the server.

In some embodiments, after 304, the method further comprises: the server receives the first inquiry request, inquires a session identifier corresponding to the conference identifier of the conference, when the first session identifier corresponding to the conference identifier is inquired, sends a first inquiry result to the terminal, wherein the first inquiry result carries the first session identifier, when the session identifier corresponding to the conference identifier is not inquired, sends a second inquiry result to the terminal, the second inquiry result is used for indicating that the session identifier corresponding to the conference identifier is not inquired, and the terminal receives the first inquiry result returned by the server and displays a session interface according to the 307; the terminal receives a second query result returned by the server, sends a second session creation request to the server, the second session creation request carries a meeting identifier of the meeting and an account included in a participation account list of the meeting, the server receives the second session creation request, creates a first session and obtains the first session identifier, establishes a corresponding relation between the meeting identifier and the first session identifier, sends the first session identifier to the terminal, and the terminal receives the first session identifier and displays a session interface according to 307.

The terminal and the server interact, a session interface is displayed through a query result sent by the server, the session interface of the session is directly displayed under the condition that the conference has a corresponding session, the corresponding session is firstly established for the conference under the condition that the conference does not have the corresponding session, and then the session interface corresponding to the established session is displayed by the terminal, namely, the scheme of realizing the session under the condition of participating in the online conference can be ensured according to the mode, and the feasibility of realizing the session under the condition of participating in the online conference is ensured.

It should be noted that, in the embodiment of the present disclosure, the conference interface and the session interface are independently displayed as an example, and in another embodiment, the conference interface and the session interface can be displayed simultaneously by displaying the session interface corresponding to the first session identifier by the terminal under the condition that the conference interface is displayed without executing 307.

308. And the terminal responds to the detection of the display instruction of the conference interface in the session interface, and displays the session interface as the conference interface in a switching way.

Under the condition of displaying the session interface, when the display instruction of the session interface is detected, the session interface is switched and displayed as the session interface, namely, the effect of randomly switching the interface under the condition of participating in the conference is realized, namely, the session can be carried out at any time under the condition of participating in the conference, and the convenience of the online conference is improved.

In some embodiments, the displayed interface is switched by the meeting option in the session interface, i.e., 308 includes: and the terminal responds to the triggering operation of the conference options in the session interface, and displays the session interface as the conference interface in a switching manner.

Wherein the meeting option is used to display a meeting interface, in some embodiments, the meeting option is located anywhere in the meeting interface, e.g., the meeting option is located in the upper right corner area, or the lower left corner area, of the meeting interface. The conference options are displayed in the session interface so as to realize interface switching through the conference options, thereby ensuring the convenience of interface switching.

In some embodiments, switching the display interface through the conference portal displayed in the session interface, i.e., 308 includes: and the terminal responds to the triggering operation of the conference entrance displayed in the session interface, and switches and displays the session interface as the conference interface.

Wherein the conference portal is published into the session by the initiator of the conference. For example, the conference indicated by the conference portal is initiated by the first account, that is, after the conference is successfully created, the first account publishes the conference portal of the conference in the first session, so that when any terminal logged in by the account participating in the first session displays the session interface, the conference portal can be displayed. The switching display between the session interface and the conference interface can be realized through the conference portal released in the conference, and the interface switching style is enriched, so that the convenience of interface switching is improved.

It should be noted that, the disclosure is described in terms of the terminal directly displaying the conference interface or the session interface, and in another embodiment, the terminal is installed with a client, where the client includes the conference interface and the session interface, and the server provides services for the client. The terminal logs in the client based on the first account number, and a conference interface or a session interface in the client is displayed based on interaction between the logged-in client and the server. For example, the client is an IM (Instant Messaging ) application client.

It should be noted that, in the embodiment of the present disclosure, the conference interface and the session interface are independently displayed as an example, and in another embodiment, the conference interface and the session interface can be displayed at the same time. In some embodiments, after 306, the method further comprises: and the terminal displays a session interface corresponding to the first session identifier under the condition of displaying the conference interface. By simultaneously displaying the conference interface and the session interface, the display style of the interface is enriched, so that a user can perform a session with other accounts at any time through the session interface under the condition of participating in the conference, and the convenience of the online conference is improved.

According to the method provided by the embodiment of the disclosure, under the condition that the first account participates in the conference, the session corresponding to the participating conference can be determined through the corresponding relation between the conference identifier and the session identifier, so that the session interface corresponding to the session is displayed, the account participating in the conference can interact based on the existing session, and a new session does not need to be additionally established, so that session resources are saved.

Fig. 7 is a flowchart illustrating a session interface display method, see fig. 7, performed by a terminal, according to an exemplary embodiment, comprising the steps of:

701. the terminal displays at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account, and the first account is an account logged in by the local terminal equipment.

The first account is an account logged in by the terminal. Each history meeting record displayed by the terminal is used for recording the history meeting participated by the first account, the session option corresponding to each history meeting record is used for initiating a session, and the initiated session is associated with the history meeting record.

702. And the terminal responds to the triggering operation of the session options corresponding to the first historical conference record, a session interface is displayed, and the participation accounts of the first session corresponding to the session interface comprise the participation accounts contained in the first historical conference record.

The session interface is used for displaying messages sent between accounts in a session, and the first historical conference record is a historical conference record related to the session interface in at least one displayed historical conference record. If the user wants to initiate a session corresponding to the first history meeting record, an operation is performed on the first history meeting record, the terminal responds to a triggering operation of a session option corresponding to the first history meeting record, a session interface corresponding to the session corresponding to the first history meeting record is displayed, the participation account of the first session comprises the participation account contained in the first history meeting record, namely, the first session comprises the account which participates in the history meeting, and based on the displayed session interface, the participation accounts contained in the first history meeting record can mutually send or view messages.

The method provided by the embodiment of the disclosure provides a method for initiating a session by using a history conference record, and a corresponding session interface is displayed by using a displayed history conference record, namely a new session initiation mode is realized, and convenience in session initiation is improved.

On the basis of the embodiment shown in fig. 7, in the process of displaying the session interface through the history meeting record, the server queries the session identifier corresponding to the history meeting identifier, and displays the session interface in different manners based on different query results returned by the server, and specific steps are described in the following embodiments.

Fig. 8 is a flowchart illustrating a session interface display method according to an exemplary embodiment, and referring to fig. 8, an execution subject of the method includes a terminal, including the steps of:

801. and the terminal displays at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record.

The history meeting record is used for recording the meeting in which the first account participates, and in some embodiments, any history meeting record includes a meeting name, a meeting starting time or a meeting ending time, accounts participating in the history meeting, and the like. The participation accounts included in any history meeting record are the accounts of the history meeting recorded by the history meeting record.

In some embodiments, the terminal displays the history meeting record through the record display interface, that is, 801 includes: and the terminal displays the at least one history meeting record and the session options corresponding to each history meeting record in the record display interface. The history meeting record is displayed through the record display interface so that a user can view the history meeting record, and convenience in viewing the history meeting record is improved. As shown in fig. 9, 6 history conferences and session options corresponding to each history conference are displayed in the recording display interface, and the conference name, conference end time, and the like of each history conference are displayed in the recording display interface.

802. And the terminal responds to the triggering operation of the session options corresponding to the first historical conference record, and sends a second query request to the server, wherein the second query request carries a historical conference identifier, and the historical conference identifier is used for indicating the conference recorded by the first historical conference record.

Each history meeting record corresponds to a history meeting identifier, and the history meeting identifier is used for indicating a history meeting recorded by a corresponding first history meeting record. In the embodiment of the disclosure, the corresponding relation between the conference identifier and the session identifier is stored in the server, so that the terminal interacts with the server, and the subsequent server queries the corresponding session identifier based on the history conference identifier carried by the second query request to determine whether the first history conference record has the corresponding session.

803. The server receives a second query request, returns a first session identifier to the terminal when the session identifier corresponding to the historical conference identifier is queried as a first session identifier, and returns a first reminding message to the terminal when the session identifier corresponding to the historical conference identifier is not queried, wherein the first reminding message is used for indicating that the server does not query the session identifier corresponding to the historical conference identifier.

In the embodiment of the disclosure, for the conference recorded in the first historical conference record, if the conference has a corresponding session, a corresponding relationship between the historical conference identifier and the session identifier is created, for example, the conference is initiated from the session, or the session is created based on the account number participating in the conference process, and then the corresponding relationship between the conference identifier and the session identifier is established. After receiving the second query request, the server queries the corresponding relation between the conference identifier and the session identifier based on the history conference identifier, and if the first session identifier corresponding to the history conference identifier is queried, the server indicates that the history conference indicated by the history conference identifier corresponds to a session, and returns the queried first session identifier; if the session identifier corresponding to the history meeting identifier is not queried, and the history meeting indicated by the history meeting identifier does not have a corresponding session, a first reminding message is returned to remind that the session identifier corresponding to the history meeting identifier is not queried.

The session identification corresponding to the history meeting identification is inquired through interaction with the server so as to determine whether the history meeting record corresponds to a session or not, and different inquiry results are used for representing so as to ensure the accuracy of the inquiry results.

After inquiring the session identifier corresponding to the history meeting identifier, the server returns an inquiry result to the terminal, and the terminal can know whether the server inquires the session identifier corresponding to the history meeting identifier or not based on the inquiry result returned by the server, and the terminal executes the following 804 or 805-807 based on different inquiry results returned by the server.

804. And the terminal receives the first session identifier returned by the server and displays a session interface corresponding to the first session identifier.

The session interface is a session interface corresponding to a first session indicated by a first session identifier, and the participating account of the first session includes a participating account included in a history meeting record corresponding to the history meeting identifier. After the first session identifier corresponding to the history meeting identifier is queried, the corresponding first session can be determined based on the first session identifier, and a session interface of the first session is displayed. Based on the displayed session interface, the participating accounts contained in the history meeting record can mutually send or view messages, namely, the account participating in the same history meeting can directly perform a session, so that the convenience of the session is improved.

In some embodiments, the history meeting record and the corresponding session options displayed by the terminal in the record display interface, and the record display interface and the session interface are displayed independently, that is, 804 includes: and after receiving the first session identifier returned by the server, the terminal switches and displays the record display interface as a session interface corresponding to the first session identifier.

The session interface corresponding to the first session identifier is the session interface corresponding to the first session indicated by the first session identifier. And switching and displaying the record display interface as a session interface so as to enrich the display effect of the interface.

805. The terminal receives a first reminding message returned by the server, and sends a first session creation request to the server, wherein the first session creation request carries a participation account number contained in the history meeting record.

When the server does not inquire the session identifier corresponding to the history meeting identifier, the session corresponding to the history meeting is not created in the process of participating in the history meeting, so that a first session needs to be created, and the participation account of the first session comprises the participation account contained in the history meeting record, so that the session among the accounts participating in the history meeting is realized based on the created first session. Thus, a first session creation request is sent to the server requesting the server to create a new session.

806. The server receives a first session creation request, creates a first session, acquires a first session identifier, and returns the first session identifier to the terminal, wherein the participation account of the first session comprises the participation account contained in the first historical conference record.

After receiving a first session creation request sent by a terminal, a server creates a first session, so that a participation account of the first session comprises a participation account contained in a first history conference record, acquires a first session identifier for the created first session, and returns the acquired first session identifier to the terminal, so that the terminal can display a session interface based on the first session identifier later.

In some embodiments, the process of the server creating the first session includes: the server generates an account list based on the first session creation request, acquires a first session identifier for the account list, associates the account list with the first session identifier, and adds the participating account contained in the first history meeting record to the account list to obtain the first session.

In the embodiment of the disclosure, each session corresponds to an account list, and the account added to the account list is the account participating in the session. The server creates an account list and associates the account list with the first session identifier, so that subsequent management of the first session is facilitated.

In some embodiments, the server can determine the first session identification in a number of ways, i.e., the process of obtaining the first session identification includes: the first session identification is an identification that is randomly generated when the first session is created; or, a session identification database is stored in the server, the session identification database comprises a plurality of session identifications, no session is corresponding to the session identifications, and after the first session is created, the server selects one session identification from the session identification database as the first session identification corresponding to the first session.

807. And the terminal receives the first session identifier returned by the server and displays a session interface corresponding to the first session identifier.

After the first session identifier is obtained, a corresponding first session can be determined through the first session identifier, and a session interface of the first session is displayed. Based on the displayed session interface, the first historical conference record can send or view messages to each other among the participating accounts.

Under the condition that the server does not inquire the session identifier corresponding to the history conference identifier, the terminal requests the server to create the session through interaction with the server, and a session interface corresponding to the session created by the server is displayed.

In some embodiments, the terminal displays the session interface through interaction with the server, that is, 8043 includes: the terminal sends a second display request to the server, the second display request carries a first session identifier, the server receives the second display request, inquires second interface information corresponding to the first session identifier, sends the second interface information to the terminal, receives the second interface information, and renders the session interface based on the second interface information.

The second interface information is used for describing the session interface. The second interface information is acquired in an interactive mode with the server, and the session interface is rendered, so that the rendered session interface is matched with the second interface information stored in the server, and the accuracy of the displayed session interface is guaranteed.

It should be noted that, in the embodiment of the present disclosure, the session identifier corresponding to the history meeting identifier is queried first, and then the session interface is displayed based on the queried result, and in another embodiment, steps 802-804 are not required to be executed, other manners can be adopted, and the terminal responds to the triggering operation of the session option corresponding to the first history meeting record, and displays the session interface.

The method provided by the embodiment of the disclosure provides a method for initiating a session by using a history conference record, and a corresponding session interface is displayed by using a displayed history conference record, namely a new session initiation mode is realized, and convenience in session initiation is improved.

And the corresponding session interface is displayed through the history conference record, namely, after the history conference is finished, the method is convenient for viewing the session corresponding to the history conference, so that the message in the session interface can be viewed, and the convenience for viewing the session is improved.

Fig. 10 is a flowchart illustrating a conference interface display method, see fig. 10, performed by a terminal, according to an exemplary embodiment, comprising the steps of:

1001. the terminal displays at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account, and the first account is an account logged in by the local terminal equipment.

The first account is an account logged in by the terminal. Each history meeting record displayed by the terminal is used for recording the history meeting participated by the first account, and meeting options corresponding to each history meeting record are used for initiating one meeting.

1002. The terminal responds to the triggering operation of the meeting options corresponding to the first historical meeting record, a second meeting creation request is sent to the server, the second meeting creation request carries a first account and a third account, the third account is a participation account contained in the first historical meeting record, the server is used for receiving the second meeting creation request, creating a meeting, acquiring a meeting identifier and returning the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference.

In an embodiment of the present disclosure, the participating account included in the first history meeting record is an account of a history meeting recorded in the first history meeting record. When a conference is initiated again through conference options corresponding to the first historical conference record, any third account number can be selected from the first historical conference record, a new conference is created through interaction with the server, and the third account number which agrees to participate in the conference is added to the conference by the server, so that the accounts which agree to participate in the conference can be added to the new conference, and a mode of initiating a new conference by utilizing the historical conference record is realized.

1003. And the terminal receives the conference identifier returned by the server and displays a conference interface corresponding to the conference identifier.

After the terminal determines the conference identification, the conference indicated by the conference identification can be determined, and the online conference can be carried out with the account numbers participating in the conference through the conference interface by displaying the conference interface of the conference.

The method provided by the embodiment of the disclosure provides a mode of initiating a new conference by using the history conference record, displays the history conference record corresponding to the account number, initiates a new conference by using the displayed history conference record, and displays the conference interface of the conference, thereby improving the convenience of conference initiation.

Based on the embodiment shown in fig. 10, the specific steps of displaying the conference interface by using the history conference record corresponding to the first account through the interaction between the terminal and the server are described in the following embodiments.

Fig. 11 is a flowchart illustrating a session interface display method according to an exemplary embodiment, referring to fig. 11, an execution subject of the method includes a terminal and a server, including the steps of:

1101. the terminal displays at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account.

The 1101 is the same as 801, and will not be described again.

1102. The terminal responds to triggering operation of meeting options corresponding to the first historical meeting record, a second meeting creation request is sent to the server, the second meeting creation request carries a first account number and a third account number, and the third account number is a participation account number contained in the first historical meeting record.

The third account number comprises one or more than one, and is selected from the participating accounts contained in the first historical conference record. In some embodiments, the third account is all accounts except the first account in the participating accounts included in the first history meeting record, or the third account is any number of accounts selected by the user from the participating accounts included in the first history meeting record. The conference creation request is initiated by selecting a third account from the participating accounts contained in the history conference record, namely, the conference can be initiated again by selecting any third account from the history conference record, so that convenience in conference initiation is improved.

In some embodiments, the conference creation request is sent in the displayed account by displaying the participating accounts contained in the history meeting record, that is, 1102 includes: the terminal responds to the triggering operation of meeting options corresponding to the first historical meeting record, the participating account contained in the first historical meeting record is displayed, a third account is selected from the displayed accounts, and a second meeting creation request is sent to the server in response to the confirmation operation of the selected third account.

Wherein the conference option is used to initiate a conference creation request. The conference creation request is initiated by selecting any account number from the participating accounts contained in the history conference record, namely, the conference can be initiated based on any account number contained in the history conference record, so that the flexibility of conference initiation is improved.

For example, the terminal responds to the triggering operation of the meeting option corresponding to the first historical meeting record, displays a popup window and a confirmation option, displays the participating account contained in the first historical meeting record in the popup window, and responds to the triggering operation of the confirmation option when the third account is selected, and sends a second meeting creation request to the server. The participation account number contained in the first history conference record is displayed in the popup window mode, so that the display effect of the account number is improved, the third account number is conveniently selected from the account numbers displayed in the popup window and the conference is initiated through the popup window and the confirmation options, and therefore the flexibility and convenience of conference initiation are improved.

1103. The server receives a second session creation request, creates a second session, acquires a second session identifier, establishes a corresponding relation between the conference identifier and the second session identifier, returns the second session identifier, and the participating account of the second session comprises the account included in the participating account list.

The 1103 is the same as 302, and will not be described again.

In some embodiments, the second conference creation request further carries a history conference identifier, where the history conference identifier is used to indicate a conference recorded in the first history conference record, and after the conference is created, the server is further capable of establishing a correspondence between the conference identifier and the session identifier, that is, after the server creates the conference, the method further includes: and when the server inquires that the session identifier corresponding to the historical session identifier is the first session identifier, establishing a corresponding relation between the session identifier and the first session identifier.

If the first history meeting record has a corresponding session, the corresponding relation between the history meeting identification and the session identification is stored in the server, if the first session identification corresponding to the history meeting identification is inquired, the corresponding relation between the meeting identification corresponding to the newly created meeting and the first session identification is established, so that the corresponding session is searched through the corresponding relation in the subsequent meeting participation process, a message container is provided for the meeting, the accounts participating in the meeting can mutually send messages through the session, and the new session does not need to be created again, thereby saving resources.

1104. And the terminal receives the conference identifier returned by the server and displays a conference interface corresponding to the conference identifier.

This 1104 is similar to 303 above and will not be described again here.

It should be noted that the embodiments of the present disclosure create a new meeting with a history of meetings and display the meeting interface, while in another embodiment, meetings can be created in other ways.

In some embodiments, where the terminal is equipped with a client, the process of creating the conference includes: the terminal logs in the client based on the first account number, displays a main interface of the client, responds to the triggering operation of the conference options in the main interface, sends a third conference creation request to the server, the third conference creation request carries the first account number, the server receives the third conference creation request, creates a new conference and obtains a conference identifier of the conference, sends the conference identifier to the terminal, receives the conference identifier, and displays a conference interface corresponding to the conference identifier.

In the embodiment of the disclosure, the client is served by the server, and has an online conference function, so that a conference can be created through conference options. After the terminal creates the conference, other terminals can join the conference based on the conference identification of the conference, so as to realize the effect of the multi-person online conference.

The method provided by the embodiment of the disclosure provides a mode of initiating a new conference by using the history conference record, displays the history conference record corresponding to the account number, initiates a new conference by using the displayed history conference record, and displays the conference interface of the conference, thereby improving the convenience of conference initiation.

It should be noted that the above embodiments may be combined at will, for example, on the basis of the embodiment shown in fig. 7, and the embodiment shown in fig. 3 is combined, that is, the session interface is displayed by using the history conference record, and then, the conference is initiated based on the displayed session interface, the conference interface is displayed, and the switching between the conference interface and the display interface is realized. For another example, based on the embodiment shown in fig. 11, in connection with the embodiment shown in fig. 2, it is achieved to initiate a conference using a history conference record, display a conference interface, and switch a session interface for displaying a session based on the display of the conference interface.

Based on the embodiments shown above, a process of displaying an interface based on a client is provided, as shown in fig. 12, the process includes:

1201. and the terminal logs in the client based on the first account number and displays an interface of the client.

As shown in fig. 13, the interface includes therein aconference recording portal 1301, aconference creation portal 1302, anidentification presentation area 1303, and a session presentation area including amessage presentation area 1304 and amessage input area 1305. The identifier display area is used for displaying session identifiers of a plurality of sessions participated in by a first account logged in the terminal, themessage display area 1304 is used for displaying messages issued in the session corresponding to any selected session identifier, namely, chat records among the plurality of accounts participated in the session, themessage input area 1305 is used for inputting messages, and the messages can be issued to the selected session based on themessage input area 1305. Theconference record entry 1301 is configured to enter a record display interface, and display a history conference record corresponding to a first account logged in the terminal. Theconference creation portal 1302 is operable to create a group conference based on any of the selected session identifications.

And under the condition that the terminal displays the main interface of the client, the user executes different operations, and the interfaces displayed by the terminal are different. If the user clicks on themeeting record entry 1301, the specific steps for subsequently effecting a switch between the meeting interface and the meeting interface are shown at 1202-1206; if the user clicks onconference creation portal 1302, the specific steps followed to effect a switch between conference interfaces and session interfaces are shown as 1207-1208.

1202. The user clicks theconference record entry 1301, and the terminal displays a record display interface, and displays the history conference record corresponding to the first account number and the session option and the conference option corresponding to each history conference record in the record display interface.

If the user clicks on the session option, a session interface can then be displayed and a meeting initiated based on the session interface, as at 1203-1204. If the user clicks on the meeting option, the meeting interface can then be displayed and the meeting interface can be switched to a conversation interface, such as 1205-1206.

1203. And clicking a session option corresponding to the first historical conference record in the record display interface by the user, displaying a session interface corresponding to the historical conference record by the terminal, wherein the participation accounts contained in the historical conference record are all participated in the session corresponding to the session interface.

1204. The terminal displays the conference option in the session interface, the user clicks the conference option, a conference is initiated, and the terminal displays the conference interface. The terminal issues a conference entrance to the session corresponding to the session interface, the terminal participating in the account login of the session displays the conference entrance in the session interface corresponding to the session, if the user clicks the conference entrance, the terminal joins in the conference indicated by the conference entrance, and the corresponding terminal displays the conference interface.

1205. The user clicks a meeting option corresponding to a first historical meeting record in a record display interface, the terminal displays the participating accounts and confirmation options contained in the historical meeting record, the user selects any number of accounts from the displayed accounts, clicks the confirmation options to initiate a meeting, the terminal displays a meeting interface corresponding to the established meeting, and the accounts which agree to participate in the meeting are displayed in the meeting interface.

1206. The terminal displays a session option in the conference interface, the user clicks the session option, the terminal displays the session interface, and the accounts participating in the conference all participate in the session corresponding to the session interface.

1207. Upon selection of any session identification, the user clicks on the conference creation portal 1302 to initiate the conference, the terminal displays a conference interface in which the conference account numbers that agree to participate in the conference are displayed. And, the terminal issues a conference portal to the selected session, the terminal participating in the account login of the selected session displays the conference portal in themessage display area 1304, and if the conference portal is clicked, the terminal joins the conference indicated by the conference portal, and a conference interface is displayed.

1208. The terminal displays the session options in the conference interface, the user clicks the session options, and the terminal switches to display the session interface.

Fig. 14 is a block diagram illustrating a session interface display apparatus according to an exemplary embodiment. Referring to fig. 14, the session interface display apparatus includes:

adisplay unit 1401, configured to execute a conference interface for displaying a conference, where a participating account list of the conference includes a first account logged in by the local terminal device;

a sendingunit 1402 configured to perform sending, in response to a session initiation instruction in the conference interface, a first query request to a server, where the first query request carries a conference identifier of a conference, and the server is configured to return the first session identifier when the first session identifier corresponding to the conference identifier is queried;

areceiving unit 1403 configured to perform receiving the first session identifier returned by the server;

thedisplay unit 1401 is further configured to perform displaying a session interface corresponding to the first session identifier, where the session interface is a session interface corresponding to the first session indicated by the first session identifier, and the participating account of the first session at least includes an account in the participating account list.

In some embodiments, as shown in fig. 15, adisplay unit 1401 includes:

the sending subunit 1411 is configured to perform sending, under the condition that the session interface is displayed, a first session creation request to the server in response to a session creation instruction in the session interface, where the first session creation request carries a first account number and a first session identifier corresponding to the session interface, and the server is configured to receive the first session creation request, create a conference and obtain the conference identifier, establish a correspondence between the conference identifier and the first session identifier, add the first account number to the conference, and return the conference identifier;

A receiving subunit 1412 configured to execute the meeting identifier returned by the receiving server;

a display subunit 1413 configured to perform displaying a conference interface corresponding to the conference identification.

In some embodiments, the first session creation request further carries a second account, the second account being an account of the participating accounts of the first session; the server is further configured to send a first conference participation request to a terminal logged in by the second account, where the first conference participation request is used to request the corresponding second account to participate in the conference, and add the second account agreeing to participate in the conference.

In some embodiments, thedisplay unit 1401 is further configured to perform displaying a session interface in which a conference entry of a conference is displayed; and in response to the confirmation operation of the conference entrance, displaying a conference interface of the conference.

In some embodiments, thedisplay unit 1401 is further configured to display at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record, where the history meeting record is used for recording the meeting in which the first account participates; and responding to the triggering operation of the session options corresponding to the first historical conference record, displaying a session interface, wherein the participation accounts of the first session corresponding to the session interface comprise the participation accounts contained in the first historical conference record.

In some embodiments, as shown in fig. 15, adisplay unit 1401 includes:

a sending subunit 1411, configured to perform a triggering operation in response to the session option corresponding to the first historical conference record, send a second query request to the server, where the second query request carries a historical conference identifier, the historical conference identifier is used to indicate a conference recorded by the first historical conference record, and the server is used to receive the second query request, and return the first session identifier if the session identifier corresponding to the historical conference identifier is queried to be the first session identifier;

a receiving subunit 1412 configured to execute the first session identifier returned by the receiving server;

a display subunit 1413 configured to perform displaying a session interface corresponding to the first session identification.

In some embodiments, the receiving subunit 1412 is further configured to execute a first alert message returned by the receiving server, where the first alert message is used to indicate that the server does not query the session identifier corresponding to the historical conference identifier;

the sending subunit 1411 is further configured to perform sending a first session creation request to a server, where the first session creation request carries a participating account number included in the first history meeting record, and the server is configured to receive the first session creation request, create a first session and obtain a first session identifier, return the first session identifier, and the participating account number of the first session includes a participating account number included in the first history meeting record;

A receiving subunit 1412 further configured to execute the first session identifier returned by the receiving server;

the display subunit 1413 is further configured to perform displaying a session interface corresponding to the first session identification.

In some embodiments, as shown in fig. 15, thedisplay unit 1401 is further configured to perform displaying at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, where the history meeting record is used for recording a meeting in which the first account participates;

adisplay unit 1401, comprising:

a sending subunit 1411, configured to perform a triggering operation in response to a meeting option corresponding to the first historical meeting record, send a second meeting creation request to the server, where the second meeting creation request carries a first account and a third account, the third account is a participating account included in the first historical meeting record, and the server is configured to receive the second meeting creation request, create a meeting, acquire a meeting identifier, and return the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

A receiving subunit 1412 configured to execute the meeting identifier returned by the receiving server;

a display subunit 1413 configured to perform displaying a conference interface corresponding to the conference identification.

In some embodiments, the second meeting creation request also carries a historical meeting identification for indicating the meeting recorded by the first historical meeting record; the server is further configured to establish a correspondence between the conference identifier and the first session identifier when the session identifier corresponding to the historical conference identifier is queried as the first session identifier.

In some embodiments, the session interface display apparatus further comprises:

thereceiving unit 1403 is further configured to execute receiving a second alert message returned by the server, where the second alert message is used to indicate that the server does not query the session identifier corresponding to the session identifier;

the sendingunit 1402 is further configured to perform sending a second session creation request to the server, where the second session creation request carries an account included in the participating account list, and the server is configured to receive the second session creation request, create a second session, obtain a second session identifier, establish a correspondence between the conference identifier and the second session identifier, and return the second session identifier, where the participating account of the second session includes an account included in the participating account list;

The receivingunit 1403 is further configured to perform receiving the second session identifier returned by the server;

thedisplay unit 1401 is further configured to perform displaying a session interface corresponding to the second session identifier.

In some embodiments, thedisplay unit 1401 is configured to perform switching display of the conference interface as a session interface.

In some embodiments, thedisplay unit 1401 is further configured to perform displaying the session interface switch as the conference interface in response to detecting a presentation instruction to the conference interface in the session interface.

Fig. 16 is a block diagram illustrating a session interface display apparatus according to an exemplary embodiment. Referring to fig. 16, the session interface display apparatus includes:

thedisplay unit 1601 is configured to perform displaying at least one history meeting record corresponding to the first account and session options corresponding to each history meeting record, where the history meeting record is used to record a meeting in which the first account participates, and the first account is an account logged in by the local device;

thedisplay unit 1601 is further configured to perform a triggering operation in response to a session option corresponding to the first history meeting record, display a session interface, where the participation account of the first session corresponding to the session interface includes a participation account included in the first history meeting record.

Fig. 17 is a block diagram illustrating a conference interface display device according to an exemplary embodiment. Referring to fig. 17, the conference interface display device includes:

the display unit 1701 is configured to display at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, where the history meeting record is used to record a meeting in which the first account participates, and the first account is an account logged in by the local device;

a sending unit 1702 configured to perform a triggering operation in response to a meeting option corresponding to the first historical meeting record, send a second meeting creation request to a server, where the second meeting creation request carries a first account and a third account, the third account is a participating account included in the first historical meeting record, and the server is configured to receive the second meeting creation request, create a meeting, acquire a meeting identifier, and return the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

areceiving unit 1703 configured to perform receiving the conference identifier returned by the server;

The display unit 1701 is further configured to perform displaying a conference interface corresponding to the conference identifier.

The specific manner in which the individual units perform the operations in relation to the apparatus of the above embodiments has been described in detail in relation to the embodiments of the method and will not be described in detail here.

In an exemplary embodiment, there is also provided an electronic device including:

one or more processors;

volatile or non-volatile memory for storing one or more processor-executable instructions;

wherein the one or more processors are configured to perform the steps performed by the terminal in the session interface display method or the conference interface display method described above.

In some embodiments, the electronic device is provided as a terminal. Fig. 18 is a block diagram illustrating a structure of a terminal 1800, according to an exemplary embodiment. The terminal 1800 may be a portable mobile terminal, such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. The terminal 1800 may also be referred to as a user device, portable terminal, laptop terminal, desktop terminal, or the like.

The terminal 1800 includes: aprocessor 1801 and amemory 1802.

Processor 1801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. Theprocessor 1801 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). Theprocessor 1801 may also include a main processor and a coprocessor, the main processor being a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ); a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, theprocessor 1801 may be integrated with a GPU (Graphics Processing Unit, image processor) for taking care of rendering and rendering of content that the display screen is required to display. In some embodiments, theprocessor 1801 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.

Thememory 1802 may include one or more computer-readable storage media, which may be non-transitory. Thememory 1802 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium inmemory 1802 is used to store at least one program code for execution byprocessor 1801 to implement a conversation interface display method or a conference interface display method provided by a method embodiment in the present disclosure.

In some embodiments, the terminal 1800 may also optionally include: aperipheral interface 1803 and at least one peripheral. Theprocessor 1801,memory 1802, andperipheral interface 1803 may be connected by a bus or signal line. The individual peripheral devices may be connected to theperipheral device interface 1803 by buses, signal lines or circuit boards. Specifically, the peripheral device includes: at least one ofradio frequency circuitry 1804, adisplay screen 1805, acamera assembly 1806, anaudio circuit 1807, apositioning assembly 1808, and apower supply 1809.

Theperipheral interface 1803 may be used to connect I/O (Input/Output) related at least one peripheral device to theprocessor 1801 andmemory 1802. In some embodiments,processor 1801,memory 1802, andperipheral interface 1803 are integrated on the same chip or circuit board; in some other embodiments, either or both of theprocessor 1801,memory 1802, andperipheral interface 1803 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.

TheRadio Frequency circuit 1804 is configured to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. Theradio frequency circuit 1804 communicates with a communication network and other communication devices via electromagnetic signals. Theradio frequency circuit 1804 converts electrical signals to electromagnetic signals for transmission, or converts received electromagnetic signals to electrical signals. Optionally, theradio frequency circuit 1804 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. Theradio frequency circuitry 1804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, theradio frequency circuitry 1804 may also include NFC (Near Field Communication ) related circuitry, which is not limited by this disclosure.

Thedisplay 1805 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When thedisplay 1805 is a touch display, thedisplay 1805 also has the ability to collect touch signals at or above the surface of thedisplay 1805. The touch signal may be input as a control signal to theprocessor 1801 for processing. At this point, thedisplay 1805 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, thedisplay 1805 may be one and disposed on the front panel of the terminal 1800; in other embodiments, thedisplay 1805 may be at least two, disposed on different surfaces of the terminal 1800 or in a folded configuration; in other embodiments, thedisplay 1805 may be a flexible display disposed on a curved surface or a folded surface of theterminal 1800. Even more, thedisplay screen 1805 may be arranged in an irregular pattern other than rectangular, i.e., a shaped screen. Thedisplay 1805 may be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.

Thecamera assembly 1806 is used to capture images or video. Optionally, thecamera assembly 1806 includes a front camera and a rear camera. The front camera is arranged on the front panel of the terminal, and the rear camera is arranged on the back of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, thecamera assembly 1806 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.

Theaudio circuitry 1807 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and the environment, converting the sound waves into electric signals, and inputting the electric signals to theprocessor 1801 for processing, or inputting the electric signals to theradio frequency circuit 1804 for realizing voice communication. For stereo acquisition or noise reduction purposes, the microphone may be multiple, and disposed at different locations of theterminal 1800. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is then used to convert electrical signals from theprocessor 1801 or theradio frequency circuit 1804 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, theaudio circuitry 1807 may also include a headphone jack.

Thelocation component 1808 is utilized to locate a current geographic location of the terminal 1800 to enable navigation or LBS (Location Based Service, location-based services). Thepositioning component 1808 may be a positioning component based on the united states GPS (Global Positioning System ), the beidou system of china, or the galileo system of russia.

Apower supply 1809 is used to power the various components in theterminal 1800. Thepower supply 1809 may be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When thepower supply 1809 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, the terminal 1800 also includes one or more sensors 1810. The one or more sensors 1810 include, but are not limited to: acceleration sensor 1811, gyroscope sensor 1812, pressure sensor 1813, fingerprint sensor 1814, optical sensor 1815, andproximity sensor 1816.

The acceleration sensor 1811 may detect the magnitudes of accelerations on three coordinate axes of a coordinate system established with theterminal 1800. For example, the acceleration sensor 1811 may be used to detect components of gravitational acceleration on three coordinate axes. Theprocessor 1801 may control thedisplay screen 1805 to display a user interface in either a landscape view or a portrait view based on gravitational acceleration signals acquired by the acceleration sensor 1811. The acceleration sensor 1811 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 1812 may detect a body direction and a rotation angle of the terminal 1800, and the gyro sensor 1812 may collect a 3D motion of the user to the terminal 1800 in cooperation with the acceleration sensor 1811. Theprocessor 1801 may implement the following functions based on the data collected by the gyro sensor 1812: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

Pressure sensor 1813 may be disposed on a side frame of terminal 1800 and/or belowdisplay 1805. When the pressure sensor 1813 is disposed at a side frame of the terminal 1800, a grip signal of the terminal 1800 by a user may be detected, and theprocessor 1801 performs a left-right hand recognition or a shortcut operation according to the grip signal collected by the pressure sensor 1813. When the pressure sensor 1813 is disposed at the lower layer of thedisplay 1805, theprocessor 1801 controls the operability control on the UI interface according to the pressure operation of the user on thedisplay 1805. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

The fingerprint sensor 1814 is used to collect a fingerprint of the user, and theprocessor 1801 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 1814, or the fingerprint sensor 1814 identifies the identity of the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, theprocessor 1801 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 1814 may be disposed at the front, back, or side of theterminal 1800. When a physical key or vendor Logo is provided on the terminal 1800, the fingerprint sensor 1814 may be integrated with the physical key or vendor Logo.

The optical sensor 1815 is used to collect the ambient light intensity. In one embodiment, theprocessor 1801 may control the display brightness of thedisplay screen 1805 based on the intensity of ambient light collected by the optical sensor 1815. Specifically, when the intensity of the ambient light is high, the display brightness of thedisplay screen 1805 is turned up; when the ambient light intensity is low, the display brightness of thedisplay screen 1805 is turned down. In another embodiment, theprocessor 1801 may also dynamically adjust the shooting parameters of thecamera assembly 1806 based on the intensity of ambient light collected by the optical sensor 1815.

Aproximity sensor 1816, also known as a distance sensor, is provided on the front panel of theterminal 1800.Proximity sensor 1816 is used to collect the distance between the user and the front face of terminal 1800. In one embodiment, when theproximity sensor 1816 detects that the distance between the user and the front face of the terminal 1800 gradually decreases, theprocessor 1801 controls thedisplay 1805 to switch from the on-screen state to the off-screen state; when theproximity sensor 1816 detects that the distance between the user and the front of the terminal 1800 gradually increases, theprocessor 1801 controls thedisplay 1805 to switch from the off-screen state to the on-screen state.

Those skilled in the art will appreciate that the structure shown in fig. 18 is not limiting and may include more or fewer components than shown, or may combine certain components, or may employ a different arrangement of components.

In some embodiments, the electronic device is provided as a server. Fig. 19 is a schematic diagram of a server according to an exemplary embodiment, where theserver 1900 may have a relatively large difference between configuration and performance, and may include one or more processors (Central Processing Units, CPU) 1901 and one ormore memories 1902, where at least one program code is stored in thememories 1902 and loaded and executed by theprocessors 1901 to implement the methods provided in the respective method embodiments described above. Of course, the server may also have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, which when executed by a processor of an electronic device, causes the electronic device to perform the steps performed by the electronic device in the session interface display method or the conference interface display method described above. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided, which, when executed by a processor of an electronic device, enables the electronic device to perform the steps performed by the electronic device in the session interface display method or the conference interface display method described above.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (22)

1. The session interface display method is characterized by comprising the following steps:

Displaying at least one history meeting record corresponding to a first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account;

responding to triggering operation of session options corresponding to a first historical conference record, displaying a session interface, wherein a participation account of a first session corresponding to the session interface comprises a participation account contained in the first historical conference record;

responding to the triggering operation of the conference options in the session interface, and displaying a conference interface of a conference corresponding to the session to which the session interface belongs; or, in response to a triggering operation of a conference entrance in the session interface, switching and displaying the session interface as the conference interface, wherein the participation account list of the conference comprises a first account logged in by the local terminal equipment;

responding to triggering operation of session options in the conference interface, sending a first query request to a server, wherein the first query request carries conference identifications of the conference, the server is used for returning a first session identification when the first session identification corresponding to the conference identification is queried according to the corresponding relation between the stored conference identifications and the session identifications, and the server is also used for returning a second reminding message when the session identification corresponding to the conference identification is not queried;

If the first session identifier returned by the server is received, displaying a session interface corresponding to the first session identifier, wherein the session interface is a session interface corresponding to a first session indicated by the first session identifier, and the participating account of the first session at least comprises accounts in the participating account list;

if the second reminding message returned by the server is received, a second session is created through the server, and a session interface corresponding to the second session is displayed.

2. The session interface display method according to claim 1, wherein displaying a conference interface of a conference corresponding to a session to which the session interface belongs comprises:

under the condition that the session interface is displayed, a first session creation request is sent to the server in response to a session creation instruction in the session interface, the first session creation request carries the first account number and the first session identifier corresponding to the session interface, the server is used for receiving the first session creation request, creating the conference and acquiring the conference identifier, establishing a corresponding relation between the conference identifier and the first session identifier, adding the first account number into the conference, and returning the conference identifier;

Receiving the conference identification returned by the server;

and displaying the conference interface corresponding to the conference identifier.

3. The method for displaying a session interface according to claim 2, wherein the first session creation request further carries a second account, the second account being an account in the participating accounts of the first session; the server is further configured to send a first conference participation request to the terminal logged in by the second account, where the first conference participation request is used to request the corresponding second account to participate in the conference, and add the second account that agrees to participate in the conference to the conference.

4. The method for displaying a session interface according to claim 1, wherein the displaying the session interface in response to the triggering operation of the session option corresponding to the first history meeting record includes:

responding to a triggering operation of session options corresponding to the first historical conference record, sending a second query request to the server, wherein the second query request carries a historical conference identifier, the historical conference identifier is used for indicating a conference recorded by the first historical conference record, the server is used for receiving the second query request, and returning to the first session identifier when the session identifier corresponding to the historical conference identifier is inquired as the first session identifier;

Receiving the first session identifier returned by the server;

and displaying the session interface corresponding to the first session identifier.

5. The method for displaying a session interface according to claim 4, wherein after the second query request is sent to the server in response to the triggering operation of the session option corresponding to the first history meeting record, the method for displaying a session interface further comprises:

receiving a first reminding message returned by the server, wherein the first reminding message is used for indicating that the server does not inquire a session identifier corresponding to the historical conference identifier;

a first session creation request is sent to the server, the first session creation request carries a participation account contained in the first historical conference record, the server is used for receiving the first session creation request, creating the first session and acquiring the first session identifier, returning the first session identifier, and the participation account of the first session comprises the participation account contained in the first historical conference record;

receiving the first session identifier returned by the server;

and displaying the session interface corresponding to the first session identifier.

6. The session interface display method according to claim 1, characterized in that the session interface display method further comprises:

displaying at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account;

the session interface display method further comprises the following steps:

responding to triggering operation of meeting options corresponding to a first historical meeting record, sending a second meeting creation request to the server, wherein the second meeting creation request carries the first account and a third account, the third account is a participation account contained in the first historical meeting record, and the server is used for receiving the second meeting creation request, creating a meeting, acquiring the meeting identifier and returning the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

Receiving the conference identification returned by the server;

and displaying the conference interface corresponding to the conference identifier.

7. The session interface display method according to claim 6, wherein the second conference creation request further carries a history conference identifier, the history conference identifier being used to indicate a conference recorded by the first history conference record; the server is further configured to establish a correspondence between the conference identifier and the first session identifier when it is queried that the session identifier corresponding to the historical conference identifier is the first session identifier.

8. The method for displaying a session interface according to claim 1, wherein if the second alert message returned by the server is received, creating a second session by the server, and displaying a session interface corresponding to the second session includes:

a second session creation request is sent to the server, the second session creation request carries an account number included in the participation account number list, the server is used for receiving the second session creation request, creating the second session and obtaining a second session identifier, a corresponding relation between the conference identifier and the second session identifier is established, the second session identifier is returned, and the participation account number of the second session includes the account number included in the participation account number list;

Receiving the second session identifier returned by the server;

and displaying a session interface corresponding to the second session identifier.

9. The method for displaying a session interface according to claim 1, wherein after the session interface corresponding to the first session identifier is displayed, the method for displaying a session interface further comprises:

and in response to detecting a presentation instruction of the conference interface in the session interface, switching and displaying the session interface as the conference interface.

10. The session interface display method is characterized by comprising the following steps:

displaying at least one history meeting record corresponding to a first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account, and the first account is an account logged in by a local terminal device;

responding to triggering operation of session options corresponding to a first historical conference record, displaying a session interface, wherein a participation account of a first session corresponding to the session interface comprises a participation account contained in the first historical conference record;

responding to the triggering operation of the conference options in the session interface, and displaying a conference interface of a conference corresponding to the session to which the session interface belongs;

Responding to the triggering operation of session options in the conference interface, and sending a first query request to a server;

when a first session identifier sent by the server according to the first query request is received, displaying a session interface corresponding to the first session identifier, wherein the first session identifier is a session identifier corresponding to the conference identifier of the conference queried by the server;

when a second reminding message sent by the server according to the first query request is received, a second session is created through the server, a session interface corresponding to the second session is displayed, and the second reminding message is used for indicating that the server does not query a session identifier corresponding to the conference identifier.

11. A session interface display device, characterized in that the session interface display device comprises:

the display unit is configured to display at least one history meeting record corresponding to a first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings participated by the first account; responding to triggering operation of session options corresponding to a first historical conference record, displaying a session interface, wherein a participation account of a first session corresponding to the session interface comprises a participation account contained in the first historical conference record;

The display unit is further configured to execute a meeting interface for responding to the triggering operation of the meeting options in the session interface and displaying the meeting corresponding to the session to which the session interface belongs; or, in response to a triggering operation of a conference entrance in the session interface, switching and displaying the session interface as the conference interface, wherein the participation account list of the conference comprises a first account logged in by the local terminal equipment;

the sending unit is configured to execute a triggering operation for responding to a session option in the conference interface, and send a first query request to a server, wherein the first query request carries a conference identifier of the conference, the server is used for returning a first session identifier when the first session identifier corresponding to the conference identifier is queried according to a corresponding relation between stored conference identifiers and session identifiers, and the server is also used for returning a second reminding message when the session identifier corresponding to the conference identifier is not queried;

the receiving unit is configured to receive the first session identifier returned by the server;

the display unit is further configured to display a session interface corresponding to the first session identifier, where the session interface is a session interface corresponding to a first session indicated by the first session identifier, and the participating account of the first session at least includes an account in the participating account list;

The receiving unit is further configured to receive the second reminding message returned by the server;

the sending unit is further configured to perform creation of a second session through the server;

the display unit is further configured to display a session interface corresponding to the second session.

12. The session interface display apparatus according to claim 11, wherein the display unit comprises:

a sending subunit, configured to perform sending, in response to a meeting creation instruction in the session interface, a first meeting creation request to the server under the condition that the session interface is displayed, where the first meeting creation request carries the first account number and the first session identifier corresponding to the session interface, and the server is configured to receive the first meeting creation request, create the meeting and obtain the meeting identifier, establish a correspondence between the meeting identifier and the first session identifier, add the first account number to the meeting, and return the meeting identifier;

the receiving subunit is configured to receive the meeting identification returned by the server;

And the display subunit is configured to display the conference interface corresponding to the conference identifier.

13. The session interface display device according to claim 12, wherein the first session creation request further carries a second account, the second account being an account in the participating accounts of the first session; the server is further configured to send a first conference participation request to the terminal logged in by the second account, where the first conference participation request is used to request the corresponding second account to participate in the conference, and add the second account that agrees to participate in the conference to the conference.

14. The session interface display apparatus according to claim 11, wherein the display unit comprises:

a sending subunit, configured to perform a triggering operation in response to a session option corresponding to the first historical conference record, and send a second query request to the server, where the second query request carries a historical conference identifier, the historical conference identifier is used to indicate a conference recorded by the first historical conference record, and the server is used to receive the second query request, and return the first session identifier when it is queried that the session identifier corresponding to the historical conference identifier is the first session identifier;

A receiving subunit configured to perform receiving the first session identifier returned by the server;

and the display subunit is configured to display the session interface corresponding to the first session identifier.

15. The session interface display apparatus according to claim 14, wherein the receiving subunit is further configured to perform receiving a first alert message returned by the server, where the first alert message is used to indicate that the server does not query a session identifier corresponding to the historical conference identifier;

the sending subunit is further configured to send a first session creation request to the server, where the first session creation request carries a participation account included in the first historical conference record, and the server is configured to receive the first session creation request, create the first session, obtain the first session identifier, and return the first session identifier, where the participation account of the first session includes a participation account included in the first historical conference record;

the receiving subunit is further configured to perform receiving the first session identifier returned by the server;

the display subunit is further configured to perform displaying the session interface corresponding to the first session identifier.

16. The session interface display device according to claim 11, wherein the display unit is further configured to perform displaying at least one history meeting record corresponding to the first account and meeting options corresponding to each history meeting record, where the history meeting record is used for recording a meeting in which the first account participated;

the display unit includes:

a sending subunit, configured to perform a triggering operation in response to a meeting option corresponding to a first historical meeting record, send a second meeting creation request to the server, where the second meeting creation request carries the first account and a third account, the third account is a participating account included in the first historical meeting record, and the server is configured to receive the second meeting creation request, create a meeting, acquire the meeting identifier, and return the meeting identifier; the first account is added into the conference, a second participation conference request is sent to a terminal logged in by the third account, the second participation conference request is used for requesting the corresponding third account to participate in the conference, and the third account which agrees to participate in the conference is added into the conference;

The receiving subunit is configured to receive the meeting identification returned by the server;

and the display subunit is configured to display the conference interface corresponding to the conference identifier.

17. The session interface display apparatus of claim 16, wherein the second meeting creation request further carries a history meeting identification indicating a meeting recorded by the first history meeting record; the server is further configured to establish a correspondence between the conference identifier and the first session identifier when it is queried that the session identifier corresponding to the historical conference identifier is the first session identifier.

18. The session interface display apparatus according to claim 11, wherein the sending unit is further configured to perform sending a second session creation request to the server, where the second session creation request carries an account included in the participating account list, and the server is configured to receive the second session creation request, create the second session and obtain a second session identifier, establish a correspondence between the conference identifier and the second session identifier, return the second session identifier, and the participating account of the second session includes an account included in the participating account list;

The receiving unit is further configured to receive the second session identifier returned by the server;

the display unit is further configured to display a session interface corresponding to the second session identifier.

19. The session interface display apparatus according to claim 11, wherein the display unit is further configured to execute switching display of the session interface as the conference interface in response to detection of a presentation instruction to the conference interface in the session interface.

20. A session interface display device, characterized in that the session interface display device comprises:

the display unit is configured to execute and display at least one history meeting record corresponding to a first account and session options corresponding to each history meeting record, wherein the history meeting record is used for recording meetings in which the first account participates, and the first account is an account logged in by a local terminal device;

the display unit is further configured to execute a triggering operation for responding to a session option corresponding to a first historical conference record, and display a session interface, wherein a participation account of the first session corresponding to the session interface comprises a participation account contained in the first historical conference record;

A module for performing the steps of:

responding to the triggering operation of the conference options in the session interface, and displaying a conference interface of a conference corresponding to the session to which the session interface belongs;

responding to the triggering operation of session options in the conference interface, and sending a first query request to a server;

when a first session identifier sent by the server according to the first query request is received, displaying a session interface corresponding to the first session identifier, wherein the first session identifier is a session identifier corresponding to the conference identifier of the conference queried by the server;

when a second reminding message sent by the server according to the first query request is received, a second session is created through the server, a session interface corresponding to the second session is displayed, and the second reminding message is used for indicating that the server does not query a session identifier corresponding to the conference identifier.

21. An electronic device, the electronic device comprising:

one or more processors;

volatile or non-volatile memory for storing the one or more processor-executable instructions;

wherein the one or more processors are configured to perform the session interface display method of any one of claims 1 to 9; or configured to perform the session interface display method of claim 10.

22. A non-transitory computer readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the session interface display method of any one of claims 1 to 9; or configured to perform the session interface display method of claim 10.

Images