CN118509272A - Conference access method, device, equipment and storage medium - Google Patents

Abstract

The embodiment of the present application provides a conference access method, device, equipment and storage medium, which relates to the field of communication technology. The method includes: the conference server generates a conference identifier and a first access address of the target conference based on the received conference creation request; the conference creation request carries a first object identifier; determines the office identification information associated with the first object identifier, and determines the office application corresponding to the office identification information; adopts the transmission protocol between the office server and the conference server corresponding to the office application, generates a first conference link based on the conference identifier and the first access address, and sends it to the office application for presentation through the office server; the office application determines that the first conference link is triggered, generates a notification and sends it, and the conference application generates a conference access request in response to the confirmation operation triggered by the notification, and sends it to the conference server, so that it connects the conference application to the target conference. The above method is used to improve office efficiency and facilitate conference entry.

Description

Conference access method, device, equipment and storage medium

Technical Field

The present application relates to the field of communication technology, and in particular to a conference access method, apparatus, device and storage medium.

Background Art

With the continuous development of network technology, the application of network conferencing is becoming more and more widespread. Network conferencing can realize document sharing, presentation and collaboration with multiple people based on the network. Network conferencing can be held anytime and anywhere, greatly improving office efficiency.

In actual applications, online conferences can be initiated and accessed through conference applications (such as online conference applications or instant messaging applications that support online conferences). Generally, conference applications include a scheduled meeting function. Users can schedule meetings in conference applications and can also set meeting reminders for scheduled meetings to remind users to access the meeting when the scheduled meeting starts. However, when users are working based on office applications, they need to exit the office application before the scheduled meeting starts, log in to the conference application, and perform a series of operations to access the meeting. If the user forgets to set a meeting reminder, the user may miss the scheduled meeting when working based on the office application, causing inconvenience to the user's work.

For example, Zhang San sets up a scheduled meeting in advance in the conference application with a start time of 10:00 on Tuesday and sets a meeting reminder. If Zhang San uses the office application to write a project plan, he needs to save the current project plan information before 10:00, exit the office application, and log in to the conference application, find the conference workbench of the conference application, find the meeting-related information, determine the meeting number 101, return to the conference workbench, click "Join Meeting" to jump to the meeting number input page, and enter the meeting number to join the meeting, making the meeting access operation more cumbersome. If Zhang San forgets to set a meeting reminder, he is likely to forget to schedule a meeting when using the office application to write a project plan, causing a greater workload.

Obviously, during the conference access process of the above method, a series of cumbersome operations need to be performed, which makes office efficiency low and inconvenient.

Therefore, it is now urgent to redesign a conference access method and overcome the above-mentioned defects.

Summary of the invention

The embodiments of the present application provide a conference access method, device, electronic device and storage medium to improve office efficiency and facilitate conference entry.

In a first aspect, an embodiment of the present application provides a conference access method, which is applied to a conference server, and the method includes:

Based on the received conference creation request, generating a conference identifier and a first access address of the target conference; the conference creation request carries the first object identifier;

Determining office identification information associated with the first object identification, and determining an office application corresponding to the office identification information;

Generate a corresponding first conference link based on the conference identifier and the first access address by using a transmission protocol between the office server corresponding to the office application and the conference server;

sending, by the office server, the first conference link to the office application for presentation, so that the office application sends a notification to the conference application when the first conference link is triggered;

A conference access request sent by the conference application based on the notification is received, and based on the first access address carried in the conference access request, the conference application is connected to the target conference.

In a second aspect, an embodiment of the present application provides a conference access method, which is applied to a client that carries a conference application, and the method includes:

Receive and present a notification sent by a conference server; wherein the notification is generated by the office application and sent to the conference application when the first conference link is triggered, and the first conference link is presented by the conference server sending the first conference link to the office application through the office server; the first conference link is generated based on the conference identifier and the first access address of the target conference using a transmission protocol between the office server and the conference server;

In response to a confirmation operation triggered by the notification, a conference interface of the target conference is presented.

In a third aspect, an embodiment of the present application provides a conference access device, which is applied to a conference server. The method includes:

A first processing unit, configured to generate a conference identifier and a first access address of a target conference based on a received conference creation request; the conference creation request carries a first object identifier;

A second processing unit, configured to determine the office identification information associated with the first object identification, and determine the office application corresponding to the office identification information;

The second processing unit is further configured to generate a corresponding first conference link based on the conference identifier and the first access address by using a transmission protocol between the office server corresponding to the office application and the conference server;

a transceiver unit, configured to send the first conference link to the office application for presentation through the office server, so that the office application sends a notification to the conference application when the first conference link is triggered;

A conference access request sent by the conference application based on the notification is received, and based on the first access address carried in the conference access request, the conference application is connected to the target conference.

Optionally, the conference creation request further carries first conference description information; then the second processing unit is further configured to:

Based on the transmission protocol, the first conference description information is intercepted according to a set length, and the intercepted first conference description information is used as the first conference remark information;

The transceiver unit is specifically configured to send the first meeting link and the first meeting note information to the office application for presentation via the office server.

Optionally, the conference server records an association relationship between the first conference description information and the first conference note information; the transceiver unit is further used to receive a modification instruction sent by the office server, where the modification instruction is generated by the office application in response to a modification operation triggered by the first conference note information and sent to the office server;

The second processing unit is further configured to determine the first conference description information by using the association relationship based on the modified first conference remark information carried in the modification indication, and modify the first conference description information to obtain the modified first conference description information;

The transceiver unit is further configured to send the modified first conference description information to the conference application for presentation.

Optionally, the transceiver unit is also used to receive a schedule creation request sent by the conference application, the schedule creation request carrying conference schedule information; and send the conference schedule information to the office application for presentation through the office server, the conference schedule information including at least one of the schedule of the conference application, the first meeting link and the first meeting notes information.

Optionally, the transceiver unit is further used to receive office schedule information sent by the office server, where the office schedule information is sent by the office application to the office server;

The second processing unit is further configured to determine, based on the second conference link carried by the office schedule information, a second access address in the second conference link, wherein the second conference link is obtained by the office application in response to a storage operation triggered for the second conference link and is generated when the conference server creates a conference for the second object identifier; based on the second access address, determine the second conference description information by using an association relationship between the second access address and the second conference description information;

The transceiver unit is further configured to send the second conference description information to the conference application for presentation.

In a fourth aspect, an embodiment of the present application provides a conference access device, which is applied to a client that carries a conference application, and the device includes:

A first presentation unit receives and presents a notification sent by a conference server; wherein the notification is generated by an office application and sent to the conference application when a first conference link is triggered, and the first conference link is presented by the conference server sending the first conference link to the office application through the office server; the first conference link is generated based on a conference identifier and a first access address of a target conference using a transmission protocol between the office server and the conference server;

The conference unit presents a conference interface of the target conference in response to a confirmation operation triggered by the notification.

Optionally, the second presentation unit is used to:

Presenting a conference creation interface, wherein the conference creation interface includes at least one input item;

In response to an input operation triggered by the at least one input item, presenting first conference description information on the conference creation interface;

In response to the creation operation triggered by the first conference description information, the target conference task is created based on the first conference description information, and the interface is redirected to the conference directory interface, where the target conference task is displayed.

Optionally, the first presentation unit is further configured to:

receiving and presenting an information change prompt sent by the conference server; the information change prompt is used to indicate that the first conference description information has changed;

In response to the viewing operation triggered by the information change prompt, presenting the modified first conference description information,

The modified first conference description information is obtained by the conference server receiving a modification instruction sent by the office server, and determining the first conference description information by using an association relationship based on the modified first conference remark information carried in the modification instruction, and then modifying the first conference description information;

The association relationship is an association relationship between the first meeting description information and the first meeting notes information.

Optionally, the first presentation unit is further configured to:

receiving and presenting a reminder to add a meeting, wherein the reminder is used to indicate that a new meeting has been added,

In response to the viewing operation triggered by the adding of the conference reminder, presenting the second conference description information,

The second conference description information is determined by the conference server receiving the office schedule information sent by the office server, and determining the second access address in the second conference link based on the second conference link carried in the office schedule information, and then determining the second access address based on the second access address and the association relationship between the second access address and the second conference description information, and the office schedule information is sent by the office application to the office server;

The second conference link is obtained by the office application in response to a storage operation triggered on the second conference link, and is generated by the conference server when creating a conference for the second object identifier.

In a fifth aspect, an embodiment of the present application provides a computer device, comprising a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes any one of the conference access methods in the first aspect above.

In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes a computer program. When the computer program is executed on a computer device, the computer program is used to enable the computer device to execute any one of the conference access methods in the first aspect above.

In the seventh aspect, an embodiment of the present application provides a computer program product, which includes a computer program stored in a computer-readable storage medium; when a processor of a computer device reads the computer program from the computer-readable storage medium, the processor executes the computer program, so that the computer device executes any one of the conference access methods in the above-mentioned first aspect.

The beneficial effects of this application are as follows:

The conference access method, apparatus, computer equipment and storage medium provided in the embodiments of the present application are applied to a conference server. In the method, after the conference server generates a conference identifier and a first access address of the target conference for a conference creation request, the conference server determines the office application associated with the first object identifier according to the first object identifier carried in the conference creation request, and uses the transmission protocol between the office server corresponding to the office application and the conference server to generate a corresponding first conference link based on the conference identifier and the first access address. In this way, the first conference link can be transmitted to the office server based on the transmission protocol, so that the first conference link can be sent to the office application for presentation through the office server. Then, the user can trigger the first conference link presented by the office application when using the office application and when the conference target starts. , directly open the target conference, wherein, since the first conference link is generated according to the conference identifier and the first access address, when the first conference link is triggered, the conference application can obtain the first access address, thereby sending the first access address to the conference server, so that the conference server can accurately and quickly connect the conference application to the conference based on the first access address, instead of exiting the office application and logging into the conference application when the target conference arrives, and then performing a series of operations to access the conference. Accordingly, the conference access method in the present application can prevent the occurrence of cumbersome conference access operations in related technologies, resulting in slow access to the conference by the user and missing key conference information, thereby ensuring the accuracy of the user's work, improving the user's good experience, and optimizing the quality of conference access services, thereby effectively improving office efficiency and facilitating conference entry.

Other features and advantages of the present application will be described in the subsequent description, and partly become apparent from the description, or understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

FIG1 is an optional schematic diagram of an application scenario provided in an embodiment of the present application;

FIG2 is a flow chart of a conference access method provided in an embodiment of the present application;

FIG3 is a flow chart of a method for accessing a conference when a first conference link is triggered, provided in an embodiment of the present application;

FIG4 is a schematic diagram of an interface presenting a first conference link provided in an embodiment of the present application;

FIG5 is a schematic diagram of a to-do message interface presenting to-do tasks linked to a first conference provided in an embodiment of the present application;

FIG6 is a flow chart of a conference creation method provided in an embodiment of the present application;

FIG7 is a schematic diagram of an interface of a conference workbench provided in an embodiment of the present application;

FIG8 is a schematic diagram of a conference type option provided in an embodiment of the present application;

FIG9 is a schematic diagram of a conference creation interface provided in an embodiment of the present application;

FIG10 is a schematic diagram of an interface of a schedule workbench and a conference workbench provided in an embodiment of the present application;

FIG11 is a schematic diagram of a conference type option provided in an embodiment of the present application;

FIG12 is a schematic diagram of a conference creation interface presenting first conference description information provided in an embodiment of the present application;

FIG13 is a schematic diagram of a conference directory interface provided in an embodiment of the present application;

FIG14 is a schematic diagram of a conference directory interface provided in an embodiment of the present application;

FIG15 is a schematic diagram of a conference creation method provided in an embodiment of the present application;

FIG16 is a schematic diagram of a notification interface provided in an embodiment of the present application;

FIG17 is a schematic diagram of a target conference interface of an unopened video conference provided in an embodiment of the present application;

FIG18 is a schematic diagram of a video conference interface for starting a video conference provided in an embodiment of the present application;

FIG19 is a flow chart of a conference access method provided in an embodiment of the present application;

FIG20 is a schematic diagram of an interface presenting a first meeting link and first meeting notes information provided in an embodiment of the present application;

FIG21 is a schematic diagram of an interface presenting a first meeting link and first meeting notes information provided in an embodiment of the present application;

FIG22 is a schematic diagram of an interface presenting a first meeting link, first meeting notes information, and meeting invitation information provided by an embodiment of the present application;

FIG23 is a schematic diagram of a conference directory interface presenting modified first conference description information provided in an embodiment of the present application;

FIG24 is a schematic diagram of presenting an information change prompt provided in an embodiment of the present application;

FIG25 is a schematic diagram of presenting an information change prompt provided in an embodiment of the present application;

FIG26 is a schematic diagram of an interface for adding a meeting reminder provided in an embodiment of the present application;

FIG27 is a flow chart of a conference access method provided in an embodiment of the present application;

FIG28 is a schematic diagram of a conference access device provided in an embodiment of the present application;

FIG29 is a schematic diagram of a conference access device provided in an embodiment of the present application;

FIG30 is a schematic diagram of a hardware structure of a computer device using an embodiment of the present application;

FIG31 is a schematic diagram of a hardware composition structure of another computer device using an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

It is understandable that in the following specific implementations of the present application, the first meeting description information, the second meeting description information, the first object identifier, the second object identifier and other related data are involved. When the various embodiments of the present application are applied to specific products or technologies, relevant licenses or consents need to be obtained, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions. For example, when it is necessary to obtain relevant data, relevant volunteers can be recruited and relevant agreements for volunteer authorization data can be signed, and then the data of these volunteers can be used for implementation; or, by implementing within the scope of the authorized organization, the following implementation methods are implemented by using the data of internal members of the organization to make relevant recommendations to internal members; or, the relevant data used in the specific implementation are all simulated data, such as simulated data generated in a virtual scene.

To facilitate understanding of the technical solutions provided in the embodiments of the present application, some key terms used in the embodiments of the present application are explained here:

EAS (Exchange ActiveSync): An enterprise email synchronization protocol that allows mobile device users to access their email, calendar, etc.

CGI (Common Gateway Interface) is a standard interface for external extension applications to interact with website servers. It enables external programs to process form data sent by clients on the World Wide Web and respond to it. This response can be files, pictures, sounds, videos, and any data that appears on the browser form. There are many common ways for the server to interact with the client, and CGI technology is one of them. According to the CGI standard, external extension applications can be written to process the data input by the client browser and complete the interaction between the client and the server.

Uniform Resource Locator (URL) is a method for specifying the location of information on the World Wide Web service program of the Internet. URL locates resources by providing an abstract identifier of the resource location. After the system locates a resource, it may perform various operations on it, which can be abstracted into the following words: access, update, replace, and discover attributes.

The technical scheme of the embodiment of the present application involves communication technology and computer technology. Communication technology, also known as communication engineering (also known as information engineering, telecommunication engineering, formerly known as long-distance communication engineering, weak current engineering) is an important branch of electronic engineering. The focus is on information transmission and signal processing in the communication process. Communication engineering studies the transmission of information from the sending end (source) to one or more receiving ends (destination) through electric pulses in the form of electromagnetic waves, sound waves or light waves. Whether the receiving end can correctly identify the information depends on the power loss during transmission. Signal processing is an important link in communication engineering, which includes filtering, encoding and decoding. Among them, computer technology can be roughly divided into several aspects such as computer system technology, computer device technology, computer component technology and computer assembly technology. The development of computer system technology in operating systems and programming languages has a significant impact on computer system technology. For example, various communication applications supported by computer system technology and communication technology can send and receive information anytime and anywhere. In this solution, conference application is a kind of communication application. The powerful data sharing function supports voice conferencing, video conferencing program sharing, speech synchronization, virtual printing, file transfer, etc., which greatly facilitates office and life.

The following is a brief introduction to the design concept of the embodiment of the present application:

Online conferencing, also known as remote collaborative office work, can use the Internet to achieve data sharing among multiple participants in different locations. In actual applications, online conferencing can be initiated and accessed through conference applications (such as online conferencing applications or instant messaging applications that support online conferencing). Generally, in order to facilitate the user to arrange work, a meeting schedule module is also designed in the conference application. Through the meeting schedule module, the user's newly created meeting description information can be added to the schedule, and reminders can be set on the corresponding date.

Correspondingly, for the sake of convenient office work, office schedule modules will also be designed in other office applications. Through the office schedule module, effective coordination of office content can also be achieved.

However, at present, only schedule information can be synchronized between conference applications and other office applications, while conference-related information cannot be synchronized. As a result, users need to repeatedly perform a series of operations such as logging in and viewing between conference applications and other office applications to obtain all work-related information, which makes it impossible to carry out overall planning and processing of work related to conference-related information and schedule information, causing inconvenience to users' work.

For example, Zhang San's office application has one schedule information for Tuesday's schedule, and there is one schedule information in the conference application. This schedule information of the conference application contains meeting-related information. The conference application can synchronize the schedule information of the schedule in the office application, but the office application cannot synchronize the meeting-related information in the schedule information in the conference application. When Zhang San uses the office application and receives a meeting reminder from the conference application, he needs to exit the office application and log in to the conference application. After a series of operations, he needs to view the meeting-related information, find the meeting function, and access the meeting. It can be seen that the operation of accessing a meeting in the related technology is complicated and redundant, and the office efficiency is low. If you forget to set a meeting reminder in the conference application, you may also forget the meeting, causing work errors.

In view of this, an embodiment of the present application provides a conference access method, apparatus, computer equipment and storage medium. The method is applied to a conference server. After receiving a conference creation request sent by a conference application, the conference server generates a conference identifier and a first access address of the target conference for the conference creation request. The conference identifier and the first access address can be stored in a private protocol to facilitate subsequent access to the target conference for the conference application based on the conference identifier and the first access address of the target conference. Furthermore, according to the first object identifier carried in the conference creation request, the office identification information associated with the first object identifier is determined, and the office application corresponding to the office identification information is further determined. The transmission protocol between the office server corresponding to the office application and the conference server is used. Based on the conference identifier and the first access address, a corresponding first conference link is generated, and the association relationship between the first conference link, the conference identifier and the first access address is recorded, so that the first conference link can be transmitted to the office server based on the transmission protocol, and the first conference link is sent to the office application for presentation through the office server. Further, when the user object can perform a trigger operation on the first conference link presented by the office application, according to the first conference link, the relevant information of the first conference link is sent to the conference application, and the conference application sends the relevant information of the first conference link to the conference server. Then, the conference server can determine the target conference corresponding to the first access address according to the relevant information of the first conference link and the above-mentioned association relationship, and connect the conference application to the conference. Compared with exiting the office application and logging into the conference application when the target meeting arrives, and performing a series of operations to access the conference, the office efficiency is effectively improved and the conference is convenient to join.

The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

As shown in Fig. 1, it is a schematic diagram of an application scenario of an embodiment of the present application, which includes any terminal device 110 among multiple terminal devices and any conference server 120 among multiple servers, as well as any terminal device 130 among multiple terminal devices and any office server 140 among multiple servers.

In the embodiment of the present application, the terminal device 110 and the terminal device 130 include but are not limited to mobile phones, tablet computers, laptop computers, desktop computers, e-book readers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals and other devices; the terminal device 110 may be installed with a client related to the conference access service, and may also be installed with a client related to the office service. These two types of clients may be software (such as browsers, communication software, etc.), or web pages, applets, etc. The terminal device 130 may be installed with a client related to the conference access service, and may also be installed with a client related to the office service. These two types of clients may be software (such as browsers, communication software, etc.), or web pages, applets, etc. The terminal device 110 and the terminal device 130 may be the same terminal device or different terminal devices.

The conference server 120 is a background server corresponding to the client (software or web page, applet, etc.) related to the conference access service, or a background server specifically used to provide conference-related functions to the client, which is not specifically limited in this application. The office server 140 is a background server corresponding to the client (software or web page, applet, etc.) related to the office service, or a background server specifically used to provide office-related functions to the client, which is not specifically limited in this application. The conference server 120 and the office server 140 can be independent physical servers, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

It should be noted that the conference access method in the embodiment of the present application can be executed by a computer device, which can be a conference server 120 and a terminal device 110, that is, the method can be jointly executed by the server 120 and the terminal device 110. For example, when the method is jointly executed by the terminal device 110 and the conference server 120, when the client in the terminal device 110 (a client conference application is running in the terminal device 110) inputs the first conference description information for the target conference, a conference creation request is generated according to the input first conference description information, and the conference creation request is sent to the conference server 120. The conference server 120 receives the conference creation request, generates a conference identifier and a first access address of the target conference for the first object identifier according to the first object identifier in the conference creation request, stores the conference identifier and the first access address in a private protocol, and determines an office application (installed and running on a terminal device 130, wherein the terminal device 130 of the office application and the terminal device 110 of the conference application may be the same terminal device or different terminal devices) according to the first object identifier, generates a first conference link according to the conference identifier and the first access address according to a transmission protocol between the conference server 120 and the office server 140, and sends the first conference link to the office application through the office server 140 for presentation. The office application sends the first conference link related information to the conference application in response to an operation triggered on the first conference link. The conference application extracts the first access address from the first conference link related information, and then sends the first access address to the conference server 120. The conference server 120 connects the conference application to the conference according to the first access address. In this way, even if the user creates a target meeting in the conference application, the first conference link of the target meeting will be sent to the office application. When using the office application, the user can directly click the first conference link at the meeting start time of the target meeting to directly enter the target meeting without having to exit the office application, log in to the conference application, and go through a series of operations to find the conference function, enter the meeting number, etc., to access the meeting, thereby achieving convenient meeting entry and effectively improving office efficiency.

It should be noted that what is shown in FIG. 1 is only an example. In fact, the number and communication mode of terminal devices and servers are not limited and are not specifically limited in the embodiments of the present application.

The following describes the conference access method provided by the exemplary embodiment of the present application in combination with the application scenarios described above and with reference to the accompanying drawings. It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of the present application, and the implementation of the present application is not limited in this respect.

2 is a flow chart of a conference access method provided in an embodiment of the present application. Here, a conference server is used as an example for illustration. The specific implementation process of the method is as follows:

Step 201: Generate a conference identifier and a first access address of a target conference based on a received conference creation request; the conference creation request carries a first object identifier;

In one embodiment, a meeting creation request may be generated when a user selects meeting description information in a meeting application, inputs some meeting description information, and determines a scheduled meeting. The meeting creation request may include a first object identifier and first meeting description information, wherein the first object identifier may be the account, name, personal communication number and other related information registered by the user in the meeting application, and the first meeting description information may include: meeting topic, meeting time, meeting duration, participants and other related information. The first meeting description information may also include attachments related to the target meeting.

In one embodiment, the conference server generates a conference identifier of the target conference and a first access address assigned to the target conference in response to a conference creation request, wherein the conference identifier of the target conference can be a unique conference identifier assigned by the conference server to the target conference, which can be composed of a string of random numbers, or can be composed of the object name + conference time, or can be the number of conferences currently created by the conference server, such as the conference identifier is a random number 1282, or is composed of the object name + conference time ZS20230206, or is the number of conferences currently created by the conference server 1090, etc., and there is no specific restriction on the generation of the conference identifier. The first access address can be a URL (Uniform Resource Locator), which locates resources by providing an abstract identifier of the resource location.

Step 202: determining the office identification information associated with the first object identification, and determining the office application corresponding to the office identification information;

In one embodiment, the office identification information may be information related to an office application including the first object identification, such as an application name, an IP address, a personal communication number, etc. of the office application.

In one embodiment, the office application may be an application with an email sending and receiving function, an application with a chat, a file sending function, a tool application software, a management application software, etc. It should be noted that the functions and types of office applications are not specifically limited here and can be set as needed.

Step 203: using a transmission protocol between the office server corresponding to the office application and the conference server, and generating a corresponding first conference link based on the conference identifier and the first access address;

In one embodiment, the transmission protocol between the office server and the conference server corresponding to the office application may be a protocol for transmitting office schedule information of the office application to the conference application, and transmitting conference schedule information in the conference application to the office application. The office application and the conference application may have a schedule information synchronization function.

In one embodiment, the transmission protocol is a protocol for data transmission between the conference server and the office server. For example, if the office application is an application with an email transmission function, the transmission protocol between the conference server and the office server may be the EAS (Exchange ActiveSync) protocol.

In one embodiment, the conference server stores relevant information of the conference application associated with the first object identifier and office identification information of the office application associated with the first object identifier. After receiving the conference creation request, the conference server can determine the office identification information associated with the first object identifier based on the first object identifier carried in the conference creation request, so that the first conference link can be sent to the office server through the transmission protocol, so that the first conference link can be presented in the office application through the office server.

In one embodiment, if the transmission protocol between the conference server and the office server can be the EAS (Exchange ActiveSync) protocol, the conference server can include an 11-bit random character short link generator, which is used to generate a first conference link with a length of 11 characters from the conference identifier and the first access address, and record the mapping relationship between the conference identifier and the first access address and the first conference link.

In one embodiment, a bidirectional mapping table may be provided in the conference server for storing each conference identifier and the corresponding access address, as well as each conference identifier and the respective conference link.

In one embodiment, the conference server has its own private protocol. After generating the conference identifier and the first access address, the conference identifier and the first access address can be written into the corresponding location field of its own private protocol. After generating the first conference link, the first conference link can also be written into the location field of the transmission protocol between the conference application and the office application, so that the first conference link can be accurately obtained based on the transmission protocol and sent to the office server.

In one embodiment, if the conference creation request includes conference location information, the first conference link can be generated not only according to the conference identifier and the first access address, but also according to the conference identifier, the first access address and the conference location information.

In one embodiment, the meeting location information may be a meeting location input by the user, the location of a conference access device for a network conference, or the meeting location after or during a network conference. For example, the meeting location may be an office name or a conference room name of an enterprise.

Step 204: sending the first conference link to the office application for presentation through the office server, so that the office application sends a notification to the conference application when the first conference link is triggered;

In one embodiment, if the office application is an instant messaging application, the conference server can send the first conference link to the office server through the transmission protocol between the conference server and the office server, and the office server sends the first conference link to the office application for presentation. The user can click or long press the first conference link, and the office application can generate a notification containing conference-related information based on the first conference link and send it to the conference application, so that the conference application confirms that the first conference link is triggered and connects the conference application to the target conference.

In one embodiment, if the office application is an application with an email function, the conference server can send the first conference link to the office server through the EAS protocol, and the office server presents the first conference link in the office application. After the first conference link is triggered by the usage object, the office application will send a notification carrying relevant information of the first conference link to the conference application, so that the conference application confirms that the first conference link is triggered and connects the conference application to the target conference.

In one embodiment, the notification sent by the office application to the conference application may include relevant information such as the first object identifier and the first conference link/first access address, so that the conference server corresponding to the conference application can accurately determine the target conference.

Step 205: receiving a conference access request sent by the conference application based on the notification, and connecting the conference application to the target conference based on the first access address carried in the conference access request.

In one embodiment, after the conference application receives the notification sent by the office application, it can be displayed on the screen of the terminal device where the conference application is located. After the confirmation operation triggered by the user object, an access conference request containing the first access address carried in the notification is generated. The conference application sends the access conference request to the conference server, and the conference server connects the conference application to the conference according to the first access address in the access conference request. During the process, the conference application and the office application can communicate. For ease of understanding, a conference access method flow is given here. After the first conference link is sent to the office application for presentation through the office server, the access conference process steps triggered by the first conference link, as shown in Figure 3, can include the following steps:

Step 301: After the conference server sends the first conference link to the office application through the office server and presents it, the office application generates a notification based on the first access address included in the first conference link in response to a click operation triggered on the first conference link;

Step 302: The office application sends the notification to the conference application based on the communication with the conference application;

Step 303: The conference application displays the notification to remind the user, and the user triggers a confirmation operation on the notification to generate an access conference request according to the first access address carried in the notification, and sends the access conference request to the conference server based on CGI;

Step 304: The conference server receives the conference access request and connects the conference application to the target conference corresponding to the first conference address according to the first access address.

The above process steps are not unique. For example, in step 302, when the office application sends the notification to the conference application based on the communication with the conference application, if the conference application is not logged in, the conference application can be automatically logged in based on the operating system of the terminal device, so that the notification is displayed in the conference application. In step 304, after receiving the access conference request, the conference server verifies the validity of the target conference according to the first access address, and after confirming that the target conference is valid, connects the conference application to the target conference corresponding to the first conference address according to the first access address.

In one embodiment, if the office application is an application with an email function, the conference server may send the first conference link to the office server through the EAS protocol.

In one embodiment, the office application may be an office application with an email function. As shown in FIG. 4 , the first conference link is presented on a corresponding interface, which may include corresponding information such as the recipient: Zhang San, the receipt time, and the first conference link.

In one embodiment, the office application may also be an instant messaging application, as shown in FIG5, and the to-do task of the first conference link is presented in the corresponding to-do message interface. It should be noted that the office application may be any application that can receive and display the first conference link, and accordingly, the interface for displaying the first conference link may be any interface that matches the specific functions of the office application and the corresponding interface design. The interface for presenting the first conference link given in FIG4 and FIG5 is only used to clearly illustrate this solution, and does not limit the specific implementation of this solution.

In the above method, after receiving the conference creation request sent by the conference application, the conference server will generate the conference identifier and the first access address of the target conference for the conference creation request, so as to facilitate the subsequent access to the target conference for the conference application according to the conference identifier and the first access address of the target conference. In addition, according to the first object identifier carried in the conference creation request, the office identification information associated with the first object identifier is determined, and the office application corresponding to the office identification information is further determined. The transmission protocol between the office server corresponding to the office application and the conference server is adopted. Based on the conference identifier and the first access address, a corresponding first conference link is generated, so that the first conference link can be transmitted to the office server based on the transmission protocol, so that the first conference link can be sent to the office application for presentation through the office server. Then, the user object can trigger the first conference link presented by the office application to directly open the target conference. Compared with the need to exit the office application and log in to the conference application when the target conference arrives, and then go through a series of operations to access the conference, it effectively improves office efficiency and facilitates meeting entry.

Based on the method flow in FIG. 2 and FIG. 3 above, an embodiment of the present application provides a conference creation method, which is applied to a client that carries a conference application. Before presenting the notification, as shown in FIG. 6, the method further includes:

Step 601: presenting a conference creation interface, wherein the conference creation interface includes at least one input item;

In one embodiment, the at least one input item included in the conference creation interface may be conference theme, participants, conference start time, conference end time, conference location, conference-related attachments, and the like.

In one embodiment, the user can log in to the conference application and find the conference workbench, open the conference workbench, as shown in Figure 7, which is an interface for opening the conference workbench provided in an embodiment of the present application, and then click the cross symbol to present the conference type options shown in Figure 8. The conference types include "quick meeting" and "scheduled meeting". You can click the meeting type of "scheduled meeting" to enter the meeting creation interface, as shown in Figure 9. The meeting creation interface may include an input box for the meeting theme. The user can enter the meeting theme in the input box of the meeting theme. The meeting creation interface may include an option to add participants. The user can add participants at the corresponding location. The meeting creation interface may include the meeting start time, conference room, add location (which can be a location that needs to be moved to the meeting location during the meeting), add meeting attachments, etc. The user can add relevant information such as the meeting start time, conference room, meeting location and meeting attachments at the corresponding location. It should be noted that the meeting creation interface here is only used to more clearly explain the present scheme, and does not limit the specific implementation of the present scheme. For example, the meeting creation interface may also include relevant meeting description information such as meeting duration and meeting creator. Among them, the meeting workbench interface and meeting type selection interface may also be designed and changed accordingly as needed. The meeting workbench interface and meeting type selection interface here are also only used to clearly explain the present scheme, and do not limit the meeting workbench interface and meeting type selection interface of this scheme.

In one embodiment, the user can log in to the conference application and find the schedule workbench, open the schedule workbench, the conference application can include a conference function module and a schedule function module, and the conference schedule function module and the conference function module are coupled, then it can be shown in Figure 10, which is an interface for opening the schedule workbench and the conference workbench provided in an embodiment of the present application. When opening the schedule workbench, the conference workbench is also opened at the same time, then you can click "meeting" to present the meeting type options shown in Figure 11, the meeting types include "quick meeting" and "scheduled meeting", then you can click the meeting type of "scheduled meeting" to enter the meeting creation interface shown in Figure 9.

Step 602: In response to an input operation triggered by the at least one input item, present first conference description information on the conference creation interface;

In one embodiment, as shown in FIG9 , the corresponding meeting theme can be entered in the input box of the meeting theme input item in the meeting creation interface: About AA product design, in the add option for adding participants, select the participants: Participant 1, Participant 2, Participant 3, in the start input item, enter the corresponding meeting start time: January 28, 6:30 p.m., in the conference room input item, enter the corresponding conference room number: 101, and the first meeting description information will be presented in the meeting creation interface, and the first meeting description information will correspondingly include: Meeting theme: About AA product design, Participants: Participant 1, Participant 2, Participant 3, Meeting start time: Saturday, January 28 (tomorrow), 6:30 p.m., Conference room number: 101, as shown in FIG12 , which is a meeting creation interface presenting the first meeting description information.

In one embodiment, meeting attachments and locations may be selectively added in the meeting creation interface. Accordingly, the first meeting description information also includes meeting attachments and locations. It should be noted that at least one input item in the meeting creation interface may be one or more of the above-mentioned meeting topic, meeting start time, participants, conference room, etc., or may also include other information. The specific information of the first meeting description information is not limited here and can be set as needed.

Step 603: In response to the creation operation triggered by the first conference description information, the target conference task is created based on the first conference description information, and the interface of the conference directory is jumped to, and the target conference task is displayed on the conference directory interface.

In one embodiment, based on the meeting creation interface presenting the first meeting description information as shown in Figure 12, when the user clicks Save, it can create a target meeting task in response to the creation operation triggered by the presentation of the first meeting description information, jump to the meeting directory interface as shown in Figure 13, and display the target meeting task in the meeting directory interface.

In one embodiment, based on a meeting creation interface presenting the first meeting description information as shown in FIG12, when a button such as confirm/submit that triggers a creation operation is clicked using an object, a target meeting task can be created in response to the creation operation triggered by the presentation of the first meeting description information, and the interface can be jumped to the meeting directory interface as shown in FIG14. The target meeting task is displayed in the meeting directory interface. The meeting directory interface may not only include one meeting task, but all meeting tasks created using the object can be presented in the meeting directory interface.

Based on the method flow in FIG. 2 and FIG. 3 above, an embodiment of the present application provides a conference creation method, which is applied to a client that carries a conference application, and the method includes:

Step 1501 receives and presents a notification sent by a conference server; wherein the notification is generated by the office application and sent to the conference application when the first conference link is triggered, and the first conference link is sent by the conference server to the office application through the office server for presentation; the first conference link is generated based on the conference identifier and the first access address of the target conference using a transmission protocol between the office server and the conference server;

In one embodiment, when the office application responds to the triggering operation of the first conference link, a notification including information related to the first conference link is generated, wherein the notification may include the first conference link, may also include the first access address, may also include relevant information such as the office application identifier, and the information included in the notification is not specifically limited here.

In one embodiment, the notification interface for displaying the notification by the conference application may be as shown in FIG. 16 , and may be displayed in the form of a message notification on the terminal device where the conference application is located.

Step 1502: In response to a confirmation operation triggered by the notification, present a conference interface of the target conference.

In one embodiment, the conference application accesses the target conference in response to a viewing operation/conference access operation on the notification in the notification interface as shown in FIG. 16 , as shown in FIG. 17 .

In one embodiment, the conference application responds to the viewing operation/conference access operation of the notification in the notification interface as shown in Figure 16, accesses the target conference, and can also directly enter the video conferencing interface as shown in Figure 18. It should be noted that the notification interface shown in Figure 16, the target conference interface without video conferencing as shown in Figure 17, the video conferencing interface with video conferencing turned on as shown in Figure 18, etc. are only used to clearly illustrate the present solution and do not limit the specific implementation of the present solution. For example, for the notification interface, it can also be set to display the notification in a drop-down message box after unlocking, and a common dialog box can be added to the target conference interface without video conferencing and the video conferencing interface with video conferencing turned on, which can be used to transmit or display presentations, meeting attachments and other related files.

Based on the method flow in FIG. 2 above, an embodiment of the present application provides a conference access method, wherein the conference creation request further carries first conference description information;

Then, in step 204, before the office server sends the first conference link to the office application for presentation, as shown in FIG. 19, the method further includes:

Step 1901: Based on the transmission protocol, the first conference description information is intercepted according to a set length, and the intercepted first conference description information is used as the first conference remark information;

In one embodiment, the first conference description information of the target conference may also be stored in the transmission protocol between the conference server and the office server. If the transmission protocol sets a fixed length for the remark field in which the first conference description information is written, in order to smoothly write the first conference description information into the remark field of the transmission protocol, the first conference description information may be intercepted according to the set length, and the intercepted first conference description information may be written into the remark field as the first conference remark information, so that the first conference remark information may be transmitted to the office application.

In one embodiment, the interception method of intercepting the first meeting description information according to the set length may be: taking the set length of characters from the front to the back according to the first meeting description information to obtain the first meeting notes information, or, the interception method of intercepting the first meeting description information according to the set length may be: intercepting according to the preset description items in the first meeting description information to obtain the first meeting notes information. The specific interception method of the first meeting description information is not limited here.

Then, in step 204, the first conference link is sent to the office application for presentation through the office server, and the method includes:

Step 1902: Send the first meeting link and the first meeting note information to the office application through the office server for presentation.

In one embodiment, not only the first meeting link can be sent to the office application for presentation, but also the first meeting notes information can be sent to the office application for presentation, so that the user can obtain more descriptive information about the target meeting, facilitating the user to better arrange work.

In one embodiment, based on the interface of the office application presenting the first meeting link in Figure 4, as shown in Figure 20, the office application presents the interface of the first meeting link and the first meeting notes information, which includes the first meeting notes information: Saturday, January 28 (tomorrow) at 6:30 p.m., Zhang*’s themed meeting on AA product design.

In one embodiment, based on the interface of the office application presenting the first meeting link in Figure 5, as shown in Figure 21, the office application presents the interface of the first meeting link and the first meeting notes information, which includes the first meeting notes information: Saturday, January 28 (tomorrow) at 6:30 p.m., Zhang*’s meeting on the topic of AA product design.

In one embodiment, the office application presents an interface of the first conference link, which may not only include the first conference note information, but also the conference invitation information for the conference participants added according to the conference creation object, such as the conference application conference number: 672-***9-**4

One-touch dialing to join the meeting

+867******3388,86666**********6503893#(Z Country D District)

+852******00,2,86666**********503893#(Z Country H District)

+165******00,86666**********503893#(Country P)

Dial based on your location

+86*******3388 ext. 8***6 (Z country D area)

+85*******00 transfer 2,8***6 (Z country H area)

+16*******00 to 8***6 (Country P)

H.3*3/SIP device dials IP access:

42.1*7.***.2(EJ City)

1.13.1*6.***.2 (HH City)

1*6.1*6.***.2(CQ City)

1*6.1*7.***.2(GA City)

12*.1*7.***.2(EJ City)

Conference Access Guide:

https://work.***.***.com/***/IPPORT/ep***Xed0

As shown in FIG. 22 , an office application provided in an embodiment of the present application presents an interface of a first meeting link, first meeting notes information, and meeting invitation information.

Based on the method flow in FIGS. 2 and 19 above, an embodiment of the present application provides a conference access method, wherein the conference server records an association relationship between the first conference description information and the first conference note information;

Then, after the first meeting link and the first meeting note information are sent to the office application for presentation through the office server in step 204, the method further includes:

Step 1: receiving a modification instruction sent by the office server, where the modification instruction is generated by the office application in response to a modification operation triggered by the first meeting note information and sent to the office server;

In one embodiment, a user may modify the first meeting notes information in an interface in which the office application presents the first meeting notes information. The office application generates a modification indication in response to the modification operation triggered on the first meeting notes information. The modification indication may include the modified first notes information. The office application sends the modification indication to the office server, which sends the modification indication to the conference server via the office server to modify the corresponding first meeting description information in the conference server.

In an embodiment, the modification indication may include relevant information such as a conference identifier or a first object identifier of the target conference, so as to facilitate determination of the first conference description information corresponding to the modified first conference notes information.

Step 2: Based on the modified first conference remark information carried in the modification indication, the first conference description information is determined using the association relationship, and the first conference description information is modified to obtain the modified first conference description information;

In one embodiment, if the first meeting note information is: 6:30 p.m., Saturday, January 28 (tomorrow), Zhang*'s meeting on the theme of AA product design. The modified first meeting note information is: 8:30 a.m., Sunday, January 29 (the day after tomorrow), Zhang*'s meeting on the theme of AA product design. Accordingly, the conference server can modify the modified information in the first meeting note information in the corresponding first meeting description information to 8:30 a.m., Sunday, January 29 (the day after tomorrow).

In one embodiment, the association relationship may be recorded by the conference server when obtaining the first conference notes information, and is the association relationship between the first conference description information and the first conference notes information. This association relationship may be the association relationship between the identifier of the first conference description information and the identifier of the first conference notes information generated for the first conference description information and the first conference notes information. The modified first conference notes information and the identifier of the first conference notes information may be carried in the modification indication, thereby determining the identifier of the first conference description information based on the association relationship and the identifier of the first conference notes information. Finally, the first conference description information is determined, and the first conference description information is modified accordingly to obtain the modified first conference description information.

In one embodiment, the association relationship can be determined based on the first object identifier/the conference identifier of the target meeting, and the association relationship records the first meeting description information and the first object identifier/target meeting, and the association relationship between the first meeting notes information and the first object identifier/target meeting, and the modified first meeting notes information and the first object identifier/target meeting can be carried in the modification indication, thereby determining the corresponding first object identifier/target meeting and the first meeting description information, so as to modify the first meeting description information accordingly and obtain the modified first meeting description information. It should be noted that the specific form of the association relationship is not limited here, and can be determined according to specific needs and designs.

Step 3: Send the modified first conference description information to the conference application for presentation.

In one embodiment, after modifying the first conference description information and obtaining the modified first conference description information, the conference server sends the modified first conference description information to the conference application and displays it on the conference application.

In one embodiment, based on the conference directory interface shown in FIG. 14 , the modified first conference description information may be displayed, as shown in FIG. 23 , where the modified first conference description information is displayed at the corresponding target conference task.

In one embodiment, if the first meeting note information is: 6:30 p.m. on Saturday, January 28 (tomorrow), Zhang*'s meeting on the theme of AA product design, the meeting place is Conference Room 101. The modified first meeting note information is: 6:30 p.m. on Saturday, January 28 (tomorrow), Zhang*'s meeting on the theme of AA product design, the meeting place is Conference Room 102. Accordingly, the conference server can modify the modified information in the first meeting note information in the corresponding first meeting description information to the meeting place is Conference Room 102.

Based on the method flow shown in FIG. 15 , the present embodiment provides a method for presenting change information, and the method further includes:

Step 1: Receive and present an information change prompt sent by the conference server; the information change prompt is used to indicate that the first conference description information has changed;

In one embodiment, as shown in FIG. 24 , an information change prompt may be presented in a terminal device of a conference application.

In one embodiment, the modification information of the first meeting description information can be directly presented in the information change prompt. For example, if the meeting start time in the first meeting description information is changed, the change information can be directly presented in the information change prompt presented by the terminal device of the conference application. As shown in Figure 25, the meeting information change prompt: Saturday, January 28 (tomorrow) 6:30 p.m. is changed to: Sunday, January 29 (the day after tomorrow) 8:30 a.m.

Step 2: In response to the viewing operation triggered by the information change prompt, present the modified first conference description information.

The modified first conference description information is obtained by the conference server receiving a modification instruction sent by the office server, and determining the first conference description information by using an association relationship based on the modified first conference remark information carried in the modification instruction, and then modifying the first conference description information;

The association relationship is an association relationship between the first meeting description information and the first meeting notes information.

In one embodiment, as shown in FIG. 23 , in response to a viewing operation triggered by the information change prompt in FIG. 24 or FIG. 25 , the modified first conference description information is presented.

In one embodiment, the modified first conference description information may also be presented in the schedule of the conference application. It should be noted that the specific presentation interface of the modified first conference description information is not limited here.

Based on the method flow in FIG. 2 and FIG. 19 above, an embodiment of the present application provides a data transmission method, and the method further includes:

Receiving a schedule creation request sent by the conference application, wherein the schedule creation request carries conference schedule information;

The meeting schedule information is sent to the office application for presentation through the office server, wherein the meeting schedule information includes at least one of the schedule of the conference application, the first meeting link and the first meeting notes information.

In one embodiment, the conference application may include a schedule function module and a conference function module, and these two functions are coupled. As shown in FIG10, the conference workbench or the schedule workbench can be entered from the schedule workbench or the conference workbench. When creating a meeting, the conference schedule can also be created for the first conference description information presented in FIG11, the first conference description information is written into the corresponding field of the schedule, and the conference schedule information is obtained based on the first conference description information (which may include the first conference note information obtained by intercepting the first conference description information), so as to send the conference schedule information to the office application for presentation. In addition, the conference schedule information may also include schedule information about work arrangements added by the user in the schedule of the conference application. In this way, the meeting schedule information can be synchronized between the conference server and the office server, that is, the first meeting notes information and work arrangements can be synchronized to the office server and displayed in the office application. When the user plans work based on the schedule in the office application, he can obtain comprehensive work-related information including the first meeting notes information, thereby improving the accuracy of the user's work planning. And since there is no need to log in to the conference application to view the first meeting description information for work planning as in the related technology, the operational complexity of the work session is effectively reduced, and the efficiency of work planning is improved.

In one embodiment, the schedule creation request and the meeting creation request are the same request, which carries a first object identifier, so that a meeting identifier and a first access address of the target meeting are also generated for the meeting creation request, and the office identification information associated with the first object identifier is determined, thereby determining the office application, and using the transmission protocol between the office server and the conference server corresponding to the office application, a corresponding first conference link is generated based on the conference identifier and the first access address, and the first conference link and the conference schedule information are sent to the office application for presentation through the office server, and when the first conference link in the office application is triggered, the conference application accesses the target meeting.

In one embodiment, the meeting schedule information can also be intercepted and processed according to the maximum set length of the transmission protocol, so that at least one of the meeting application schedule, the first meeting link and the first meeting notes information contained in the meeting schedule information can be successfully sent to the office server, thereby sending the meeting schedule information to the office application for presentation, and when the first meeting link in the office application is triggered, the meeting application accesses the target meeting.

Based on the method flow involved in the above flowcharts, the embodiment of the present application also provides a method for adding a conference, and the method further includes:

Step 1: receiving office schedule information sent by the office server, where the office schedule information is sent by the office application to the office server;

In one embodiment, as a participant of the meeting but not the creator of the meeting, the participant can obtain office schedule information in the office application by pasting, copying or receiving messages.

In one embodiment, the office schedule information may include a second conference link generated by a conference server in response to a conference creation request or a schedule creation request for a conference creation object. The second conference link may be generated by a conference identifier and a second access address of the conference server. The conference identifier and the second access address are determined by the conference server in response to the conference creation request or the schedule creation request.

In one embodiment, the conference creation request or schedule creation request of the conference creation object may also carry second conference description information, and the conference server may record the second access address, the conference identifier of the conference, and the association relationship with the second conference description information, as well as the second access address, the conference identifier of the conference, and the association relationship with the second conference link.

In one embodiment, when a participant in a conference who is not a creator obtains office schedule information in an office application by pasting, copying, or receiving a message and saves the information, the office schedule information can be sent to a conference server via an office server.

Step 2: determining a second access address in the second conference link based on the second conference link carried by the office schedule information, wherein the second conference link is obtained by the office application in response to a storage operation triggered for the second conference link and is generated when the conference server creates a meeting for the second object identifier;

In one embodiment, when the conference server generates the second conference link for a conference creation request or a schedule creation request of a conference creation object, the conference server records the correspondence between the second conference link, the conference identifier of the conference, and the second access address. After the conference server receives the office schedule information, the second access address in the second conference link can be determined based on the second conference link and the association relationship carried in the office schedule information.

Step 3: Based on the second access address, determine the second conference description information by using the association relationship between the second access address and the second conference description information;

In one embodiment, the conference server may determine the second conference description information corresponding to the second access address based on the pre-stored association between the second access address and the second conference description information. The second conference description information may include the meeting start time, meeting topic, and participants input by the conference creation object, and may also include meeting invitation information. It should be noted that there is no specific restriction on the second conference description information in the office schedule.

Step 4: Send the second conference description information to the conference application for presentation.

In one embodiment, a conference application that is a participant but not a conference creator receives the second conference description information sent by the conference server and can display the conference description information in the conference application schedule or conference directory interface as a conference task.

In one embodiment, in a conference application of a participant object but not a conference creation object, the display mode of the conference tasks can be set in advance, and the conference tasks can be presented only in the conference directory interface of the conference workbench.

Based on the method flow in FIG. 15 and the method for adding a conference, an embodiment of the present application provides a method for adding a conference, and the method further includes:

receiving and presenting a reminder to add a meeting, wherein the reminder is used to indicate that a new meeting has been added,

In response to the viewing operation triggered by the adding of the conference reminder, presenting the second conference description information,

The second conference description information is determined by the conference server receiving the office schedule information sent by the office server, and determining the second access address in the second conference link based on the second conference link carried in the office schedule information, and then determining the second access address based on the second access address and the association relationship between the second access address and the second conference description information, and the office schedule information is sent by the office application to the office server;

The second conference link is generated when the conference server creates a conference for the second object identifier, and is obtained by the office application in response to a storage operation triggered for the second conference link, and is generated when the conference server creates a conference for the second object identifier.

In one embodiment, the interface for adding a meeting reminder may be as shown in FIG. 26 .

In one embodiment, based on the adding meeting reminder interface shown in FIG26, adding a meeting reminder can also present part or all of the second meeting description information. Presenting part or all of the second meeting description information can be determined by the character length that can be presented in the message. If the character length of the second meeting description information exceeds the character length that can be presented in the message, only part of the second meeting description information is presented. Otherwise, all of the second meeting description information is presented.

In one embodiment, in response to a participant object and a non-conference creation object, for a view operation triggered by adding a conference reminder, the second conference description information or the conference task of the second conference description information is presented on a schedule interface or a conference directory interface.

Based on the above embodiments, further, an embodiment of accessing a conference as a video conference is also provided. Specifically, when the conference server accesses the conference application to the conference, the conference server obtains the voice information of each participant in the video conference and converts the voice information of each participant into text information. The name of the participant, voice time and other conference-related information can be marked in front of the text information corresponding to each participant. Based on the text information marked with the name of the participant, voice time and other conference-related information, a meeting record is generated and recorded in the meeting record of the conference work module, so that when the participant needs to watch the meeting record, it can be displayed at the bottom of the video of the video conference during the meeting, or the participant can download the meeting record in any document format for viewing after the video conference.

Based on the above-mentioned embodiment of accessing the conference as a video conference, another embodiment is provided. Specifically, if there are multiple participants in a conference account of the video conference, such as multiple people appear in the conference video of a logged-in conference account, then when the conference server connects the conference application to the conference, the conference server identifies each participant in the video conference, obtains facial recognition information of each participant, and matches the facial recognition information of each participant with the identity image in the basic object information of each participant in their respective affiliated enterprises, so as to determine the corporate identity information of each participant (if there are one or more participants whose affiliated enterprises cannot be obtained, or their affiliated enterprises are obtained but there is no corresponding object basic information, their facial images can be screenshotted and the screenshot can be used as the name of the participant). The conference server also converts the voice information of each participant into text information, and can mark the text information corresponding to each participant with the name of the participant, corporate identity information, voice time and other conference-related information, and record it in the meeting minutes of the conference work module, so that when the participants need to watch the meeting minutes, they can be displayed at the bottom of the video of the video conference during the meeting, or after the video conference, the participants can download the meeting minutes in any document format for viewing. Based on the above method flows, the present application embodiment provides a conference access method, as shown in FIG27 , including:

Step 2701: The conference application obtains corresponding conference description information in response to an input operation of a user object on at least one input item in the conference creation interface, presents first conference description information, generates a conference creation request in response to operations such as confirmation or saving on the first conference description information, and sends the conference creation request to the conference server.

Step 2702: The conference server receives the conference creation request, and generates a conference identifier and a first access address of the target conference for the conference creation request, stores the conference identifier and the first access address of the target conference in the corresponding fields of the private protocol of the conference application, and stores the first conference description information carried in the conference creation request in the corresponding fields of the private protocol.

Step 2703: The conference server determines the office identification information for the first object identifier carried in the conference creation request, determines the office application corresponding to the office identification information, uses the transmission protocol between the office server corresponding to the office application and the conference server, generates a corresponding first conference link based on the conference identifier and the first access address, and based on the transmission protocol, intercepts the first conference description information carried in the conference creation request according to the set length to obtain the first conference note information, and sends the first conference link and the first conference note information to the office server.

Step 2704: The office server receives and sends the first meeting link and the first meeting note information to the office application.

Step 2705: The office application presents the received first meeting link and first meeting note information.

Step 2706: The office application generates modified first meeting note information in response to the modification operation and confirmation operation on the presented first meeting note information, generates a modification indication according to the modified first meeting note information, and sends it to the office server.

Step 2707: The office server sends the modification instruction to the conference server.

Step 2708: The conference server determines the first conference description information of the target conference corresponding to the modified first conference notes information based on the modified first conference notes information in the modification indication, modifies the first conference description information of the target conference based on the modified first conference notes information, obtains the modified first conference description information, and sends the modified first conference description information to the conference application.

Step 2709: The conference application receives the modified first conference description information and presents it.

Step 2710: The office application obtains office schedule information in response to the paste operation or the received message, and sends the office schedule information to the office server.

Step 2711: The office server receives the office schedule information and sends the office schedule information to the conference server.

Step 2712: The conference server may determine the second access address in the second conference link based on the second conference link carried in the office schedule information, determine the second conference description information based on the second access address and using the association between the second access address and the second conference description information, and send the second conference description information to the conference application.

Step 2713: The conference application receives and presents the second conference description information.

It should be noted that the above method flow is not unique. For example, the process steps of presenting the second conference description information in the conference application based on the second conference description information created by other creation objects in steps 2710 to 2713 can be executed before step 2701.

Based on the same concept, an embodiment of the present application provides a conference access device 2800, which is applied to a conference server. As shown in FIG. 28 , the method includes:

The first processing unit 2801 is used to generate a conference identifier and a first access address of a target conference based on a received conference creation request; the conference creation request carries a first object identifier;

The second processing unit 2802 is configured to determine the office identification information associated with the first object identification, and determine the office application corresponding to the office identification information;

The second processing unit 2802 is further configured to generate a corresponding first conference link based on the conference identifier and the first access address by using a transmission protocol between the office server corresponding to the office application and the conference server;

The transceiver unit 2803 is configured to send the first conference link to the office application for presentation through the office server, so that the office application sends a notification to the conference application when the first conference link is triggered;

The transceiver unit 2803 is further configured to receive a conference access request sent by the conference application based on the notification, and connect the conference application to the target conference through the first processing unit 2801 based on the first access address carried in the conference access request.

Optionally, the conference creation request further carries first conference description information; then the second processing unit 2802 is further configured to:

Based on the transmission protocol, the first conference description information is intercepted according to a set length, and the intercepted first conference description information is used as the first conference remark information;

The transceiver unit 2803 is specifically configured to send the first meeting link and the first meeting note information to the office application for presentation via the office server.

Optionally, the conference server records an association relationship between the first conference description information and the first conference note information; the transceiver unit 2803 is further used to receive a modification instruction sent by the office server, where the modification instruction is generated by the office application in response to a modification operation triggered by the first conference note information and sent to the office server;

The second processing unit 2802 is further configured to determine the first conference description information based on the modified first conference remark information carried in the modification indication by using the association relationship, and modify the first conference description information to obtain the modified first conference description information;

The transceiver unit 2803 is further configured to send the modified first conference description information to the conference application for presentation.

Optionally, the transceiver unit 2803 is also used to receive a schedule creation request sent by the conference application, the schedule creation request carrying conference schedule information; and send the conference schedule information to the office application for presentation through the office server, the conference schedule information including at least one of the schedule of the conference application, the first meeting link and the first meeting notes information.

Optionally, the transceiver unit 2803 is further configured to receive office schedule information sent by the office server, where the office schedule information is sent by the office application to the office server;

The second processing unit 2802 is further configured to determine, based on the second conference link carried by the office schedule information, a second access address in the second conference link, wherein the second conference link is obtained by the office application in response to a storage operation triggered for the second conference link and is generated when the conference server creates a conference for the second object identifier; based on the second access address, determine the second conference description information by using an association relationship between the second access address and the second conference description information;

The transceiver unit 2803 is further configured to send the second conference description information to the conference application for presentation.

Based on the same concept, an embodiment of the present application provides a conference access device 2900, which is applied to a client that carries a conference application. As shown in FIG. 29 , the device includes:

The first presentation unit 2901 receives and presents a notification sent by the conference server; wherein the notification is generated by the office application and sent to the conference application when the first conference link is triggered, and the first conference link is sent by the conference server to the office application through the office server for presentation; the first conference link is generated based on the conference identifier and the first access address of the target conference using the transmission protocol between the office server and the conference server;

The conference unit 2902 presents a conference interface of the target conference in response to a confirmation operation triggered by the notification.

Optionally, the second presentation unit 2903 is used to:

Presenting a conference creation interface, wherein the conference creation interface includes at least one input item;

In response to an input operation triggered by the at least one input item, presenting first conference description information on the conference creation interface;

In response to the creation operation triggered by the first conference description information, the target conference task is created based on the first conference description information, and the interface is redirected to the conference directory interface, where the target conference task is displayed.

Optionally, the first presenting unit 2901 is further configured to:

receiving and presenting an information change prompt sent by the conference server; the information change prompt is used to indicate that the first conference description information has changed;

In response to the viewing operation triggered by the information change prompt, presenting the modified first conference description information,

The modified first conference description information is obtained by the conference server receiving a modification instruction sent by the office server, and determining the first conference description information by using an association relationship based on the modified first conference remark information carried in the modification instruction, and then modifying the first conference description information;

The association relationship is an association relationship between the first meeting description information and the first meeting notes information.

Optionally, the first presenting unit 2901 is further configured to:

receiving and presenting a reminder to add a meeting, wherein the reminder is used to indicate that a new meeting has been added,

In response to the viewing operation triggered by the adding of the conference reminder, presenting the second conference description information,

The second conference description information is determined by the conference server receiving the office schedule information sent by the office server, and determining the second access address in the second conference link based on the second conference link carried in the office schedule information, and then determining the second access address based on the second access address and the association relationship between the second access address and the second conference description information, and the office schedule information is sent by the office application to the office server;

The second conference link is obtained by the office application in response to a storage operation triggered on the second conference link, and is generated by the conference server when creating a conference for the second object identifier.

Based on the same inventive concept as the above method embodiment, a computer device is also provided in the embodiment of the present application. In one embodiment, the computer device may be a server, such as the server 120 shown in FIG. 1 . In this embodiment, the structure of the computer device may be as shown in FIG. 30 , including a memory 3001 , a communication module 3003 and one or more processors 3002 .

The memory 3001 is used to store computer programs executed by the processor 3002. The memory 3001 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and programs required for running the instant messaging function, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.

The memory 3001 may be a volatile memory, such as a random-access memory (RAM); the memory 3001 may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); or the memory 3001 may be any other medium that can be used to carry or store a desired computer program in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 3001 may be a combination of the above memories.

The processor 3002 may include one or more central processing units (CPU) or a digital processing unit, etc. The processor 3002 is configured to implement the above conference access method when calling the computer program stored in the memory 3001 .

The communication module 3003 is used to communicate with terminal devices and other servers.

The specific connection medium between the above-mentioned memory 3001, the communication module 3003 and the processor 3002 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 3001 and the processor 3002 are connected through the bus 3004 in Figure 30, and the bus 3004 is described with a thick line in Figure 30. The connection mode between other components is only for schematic illustration and is not limited. The bus 3004 can be divided into an address bus, a data bus, a control bus, etc. For ease of description, only one thick line is used in Figure 30, but it does not describe only one bus or one type of bus.

The memory 3001 stores a computer storage medium, and the computer storage medium stores computer executable instructions, and the computer executable instructions are used to implement the conference access method of the embodiment of the present application. The processor 3002 is used to execute the above conference access method, as shown in Figure 2 or Figure 3 or Figure 6 or Figure 15 or Figure 19 or Figure 27.

In another embodiment, the computer device may also be other computer devices, such as the terminal device 110 shown in Figure 1. In this embodiment, the structure of the computer device may be as shown in Figure 31, including: a communication component 3110, a memory 3120, a display unit 3130, a camera 3140, a sensor 3150, an audio circuit 3160, a Bluetooth module 3170, a processor 3180 and other components.

The communication component 3110 is used to communicate with the server. In some embodiments, a wireless fidelity (WiFi) module may be included. The WiFi module belongs to a short-range wireless transmission technology. The computer device can help the user to send and receive information through the WiFi module.

The memory 3120 can be used to store software programs and data. The processor 3180 executes various functions and data processing of the terminal device 110 by running the software programs or data stored in the memory 3120. The memory 3120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. The memory 3120 stores an operating system that enables the terminal device 110 to run. In the present application, the memory 3120 can store an operating system and various application programs, and can also store a computer program for executing the conference access method in the embodiment of the present application.

The display unit 3130 can also be used to display information input by the user or information provided to the user and a graphical user interface (GUI) of various menus of the terminal device 110. Specifically, the display unit 3130 may include a display screen 3132 disposed on the front of the terminal device 110. The display screen 3132 may be configured in the form of a liquid crystal display, a light emitting diode, etc. The display unit 3130 may be used to display the conference access user interface in the embodiment of the present application, etc.

The display unit 3130 can also be used to receive input digital or character information, and generate signal input related to user settings and function control of the terminal device 110. Specifically, the display unit 3130 may include a touch screen 3131 arranged on the front of the terminal device 110, which can collect user touch operations on or near it, such as clicking a button, dragging a scroll box, etc.

The touch screen 3131 may be covered on the display screen 3132, or the touch screen 3131 and the display screen 3132 may be integrated to realize the input and output functions of the terminal device 110, and the integrated touch screen may be referred to as a touch display screen. In the present application, the display unit 3130 may display the application and the corresponding operation steps.

Camera 3140 can be used to capture still images, and users can post comments on images taken by camera 3140 through the application. Camera 3140 can be one or more. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the processor 3180 to convert it into a digital image signal.

The terminal device may also include at least one sensor 3150, such as an acceleration sensor 3151, a distance sensor 3152, a fingerprint sensor 3153, and a temperature sensor 3154. The terminal device may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, and a motion sensor.

The audio circuit 3160, the speaker 3161, and the microphone 3162 can provide an audio interface between the user and the terminal device 110. The audio circuit 3160 can transmit the electrical signal converted from the received audio data to the speaker 3161, which is converted into a sound signal for output. The terminal device 110 can also be configured with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 3162 converts the collected sound signal into an electrical signal, which is received by the audio circuit 3160 and converted into audio data, and then the audio data is output to the communication component 3110 to be sent to, for example, another terminal device 110, or the audio data is output to the memory 3120 for further processing.

The Bluetooth module 3170 is used to exchange information with other Bluetooth devices having Bluetooth modules through the Bluetooth protocol. For example, the terminal device can establish a Bluetooth connection with a wearable computer device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 3170 to exchange data.

The processor 3180 is the control center of the terminal device. It uses various interfaces and lines to connect various parts of the entire terminal. It executes various functions of the terminal device and processes data by running or executing software programs stored in the memory 3120 and calling data stored in the memory 3120. In some embodiments, the processor 3180 may include one or more processing units; the processor 3180 may also integrate an application processor and a baseband processor, wherein the application processor mainly processes an operating system, a user interface, and an application program, and the baseband processor mainly processes wireless communications. It is understandable that the above-mentioned baseband processor may not be integrated into the processor 3180. In the present application, the processor 3180 can run an operating system, an application program, a user interface display and a touch response, as well as a conference access method of an embodiment of the present application. In addition, the processor 3180 is coupled to the display unit 3130.

In some possible implementations, various aspects of the conference access method provided by the present application may also be implemented in the form of a program product, which includes a computer program. When the program product is run on a computer device, the computer program is used to enable the computer device to execute the steps of the conference access method according to various exemplary implementations of the present application described above in this specification. For example, the computer device may execute the steps shown in Figure 2 or Figure 3 or Figure 6 or Figure 15 or Figure 19 or Figure 27.

The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

The program product of the embodiment of the present application may adopt a portable compact disk read-only memory (CD-ROM) and include a computer program, and can be run on a computer device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with a command execution system, apparatus, or device.

A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with a command execution system, apparatus, or device.

The computer program embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The computer program for performing the operations of the present application may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and conventional procedural programming languages such as "C" or similar programming languages. The computer program may be executed entirely on the user's computer device, partially on the user's device, as a separate software package, partially on the user's computer device and partially on a remote computer device, or entirely on a remote computer device or server. In the case of a remote computer device, the remote computer device may be connected to the user's computer device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer device (e.g., via the Internet using an Internet service provider).

It should be noted that, although several units or subunits of the device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided into multiple units to be embodied.

In addition, although the operations of the method of the present application are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and/or one step may be decomposed into multiple steps.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (15)

1. A conference access method, applied to a conference server, the method comprising:

Based on the received meeting creation request, generating a meeting identifier and a first access address of the target meeting; the conference creation request carries a first object identifier;

Determining office identification information associated with the first object identification and determining office application corresponding to the office identification information;

Adopting a transmission protocol between an office server corresponding to the office application and the conference server, and generating a corresponding first conference link based on the conference identifier and the first access address;

sending, by the office server, the first meeting link to the office application for presentation, so that the office application sends a notification to the meeting application when the first meeting link is triggered;

and receiving an access conference request sent by the conference application based on the notification, and accessing the conference application into the target conference based on the first access address carried by the access conference request.

2. The method of claim 1, wherein the meeting creation request further carries first meeting description information;

The method further comprises, before the first meeting link is sent to the office application for presentation by the office server:

based on the transmission protocol, intercepting the first meeting description information according to a set length, and taking the intercepted first meeting description information as first meeting remark information;

The first meeting link is sent to the office application for presentation by the office server, and the method comprises the following steps:

and sending the first meeting link and the first meeting remark information to the office application for presentation through the office server.

3. The method of claim 2, wherein the association relationship between the first meeting description information and the first meeting remark information is recorded in the meeting server;

the method further comprises, after the sending, by the office server, the first meeting link and the first meeting remark information to the office application for presentation:

Receiving a modification instruction sent by the office server, wherein the modification instruction is generated by the office application in response to a modification operation triggered by the first meeting remark information and is sent to the office server;

based on the modified first meeting remark information carried in the modification instruction, determining the first meeting description information by adopting the association relation, and modifying the first meeting description information to obtain modified first meeting description information;

and sending the modified first meeting description information to the meeting application for presentation.

4. A method according to claim 2 or 3, wherein the method further comprises:

Receiving a schedule creation request sent by the conference application, wherein the schedule creation request carries conference schedule information;

And sending the conference schedule information to the office application for presentation through the office server, wherein the conference schedule information comprises at least one of schedule of the conference application, the first conference link and the first conference remark information.

5. A method according to any one of claims 1-3, wherein the method further comprises:

receiving office schedule information sent by the office server, wherein the office schedule information is sent to the office server by the office application;

Determining a second access address in a second conference link based on the second conference link carried by the office schedule information, wherein the second conference link is obtained by the office application in response to a storage operation triggered for the second conference link and is generated when the conference server creates a conference for a second object identifier;

based on the second access address, determining second meeting description information by adopting an association relation between the second access address and the second meeting description information;

and sending the second meeting description information to the meeting application for presentation.

6. A conference access method, applied to a client carrying a conference application, comprising:

Receiving and presenting a notification sent by a conference server; the notification is generated and sent to the conference application when a first conference link is triggered by the office application, wherein the first conference link is presented by the conference server through the office server and sent to the office application; the first conference link is generated based on a conference identifier and a first access address of a target conference by adopting a transmission protocol between the office server and the conference server;

and responding to a confirmation operation triggered by the notification, and presenting a meeting interface of the target meeting.

7. The method of claim 6, wherein prior to the presenting the notification, the method further comprises:

Presenting a meeting creation interface, the meeting creation interface comprising at least one input item;

Presenting first meeting description information at the meeting creation interface in response to an input operation triggered for the at least one input item;

And responding to the creation operation triggered by the first meeting description information, creating the target meeting task based on the first meeting description information, jumping to a meeting catalog interface, and displaying the target meeting task on the meeting catalog interface.

8. The method of claim 6, wherein the method further comprises:

receiving and presenting an information change prompt sent by the conference server; the information change prompt is used for indicating the first meeting description information to be changed;

In response to a view operation triggered for the information change prompt, presenting modified first meeting description information,

The method comprises the steps that a conference server receives a modification instruction sent by an office server, and based on modified first conference remark information carried in the modification instruction, the first conference description information is obtained by modifying the first conference description information after the first conference description information is determined by adopting a correlation relation;

The association relationship is the association relationship between the first meeting description information and the first meeting remark information.

9. The method of claim 6, wherein the method further comprises:

receiving and presenting an add meeting prompt, the add meeting prompt indicating that a new meeting has been added,

In response to a view operation triggered for the add-on meeting prompt, second meeting description information is presented,

The second conference description information is determined by adopting an association relation between the second access address and second conference description information based on the second access address after the conference server receives office schedule information sent by the office server and determines a second access address in the second conference link based on a second conference link carried by the office schedule information, wherein the office schedule information is sent by the office application to the office server;

The second conference link is derived by the office application in response to a storage operation triggered for the second conference link, and the conference server is generated when creating a conference for a second object identification.

10. A conference access device for use with a conference server, the device comprising:

The first processing unit is used for generating a meeting identifier and a first access address of the target meeting based on the received meeting creation request; the conference creation request carries a first object identifier;

the second processing unit is used for determining office identification information associated with the first object identification and determining office applications corresponding to the office identification information;

The second processing unit is further configured to generate a corresponding first conference link based on the conference identifier and the first access address by adopting a transmission protocol between the office server corresponding to the office application and the conference server;

The receiving and transmitting unit is used for sending the first meeting link to the office application for presentation through the office server so that the office application sends a notification to the meeting application when the first meeting link is triggered;

and receiving an access conference request sent by the conference application based on the notification, and accessing the conference application into the target conference based on the first access address carried by the access conference request.

11. The apparatus of claim 10, wherein the association of the first meeting description information and the first meeting remark information is recorded in the meeting server;

The receiving and transmitting unit is further configured to receive a modification instruction sent by the office server, where the modification instruction is generated by the office application in response to a modification operation triggered by the first meeting remark information, and send the modification instruction to the office server;

The second processing unit is further configured to determine the first session description information by using the association relationship based on the modified first session remark information carried in the modification instruction, and modify the first session description information to obtain modified first session description information;

the receiving and transmitting unit is further used for sending the modified first meeting description information to the meeting application for presentation.

12. A conference access device for use with a client carrying a conference application, the device comprising:

The first presentation unit receives and presents the notification sent by the conference server; the notification is generated and sent to the conference application when a first conference link of the office application is triggered, wherein the first conference link is presented by the conference server through the office server, and the first conference link is sent to the office application; the first conference link is generated based on a conference identifier and a first access address of a target conference by adopting a transmission protocol between the office server and the conference server;

and the conference unit responds to the confirmation operation triggered by the notification and presents a conference interface of the target conference.

13. A computer readable non-volatile storage medium, characterized in that the computer readable non-volatile storage medium stores a program which, when run on a computer, causes the computer to implement the method of any one of claims 1 to 5, 6-9.

14. A computer device, comprising:

A memory for storing a computer program;

a processor for invoking a computer program stored in said memory, performing the method according to any of claims 1 to 5, 6-9 in accordance with the obtained program.

15. A computer program product comprising a computer program, the computer program being stored on a computer readable storage medium; when a processor of a computer device reads the computer program from the computer readable storage medium, the processor executes the computer program, causing the computer device to perform the method of any one of claims 1 to 5, 6-9.