CN113824572B

CN113824572B - Conference access method and device

Info

Publication number: CN113824572B
Application number: CN202110513352.7A
Authority: CN
Inventors: 刘镇
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-05-11
Filing date: 2021-05-11
Publication date: 2023-05-12
Anticipated expiration: 2041-05-11
Also published as: WO2022237543A1; CN113824572A

Abstract

A conference access method and apparatus, the method comprising: the terminal equipment receives and acquires at least one group of conference schedules, wherein the conference schedules comprise schedule information of three-party applications, and the conference schedules further comprise conference links and conference content information; the terminal equipment generates a conference list according to the at least one group of conference schedules, wherein the conference list comprises the at least one group of conference summary information, and the conference summary information comprises conference links and at least part of conference contents; the terminal equipment displays the conference list of the at least one group of conference schedules, receives conference link operation of a user on a target conference, and responds to the operation to enter the target conference to realize one-key conference.

Description

Conference access method and device

Technical Field

The embodiment of the application relates to the field of terminals, in particular to a conference access method and device.

Background

The calendar provider (Calendar Provider) is a repository for user calendar events. It allows a user to perform a series of operations on calendar, event, meeting, reminder, etc. content, including for example, query, insert, update, delete operations, etc. A calendar provider in the terminal may control a calendar application APP in the application layer, which is typically preset in the handset, for managing the calendar of the third party platform, such as synchronizing user created calendar data into a repository of the system calendar.

However, the calendar provider does not have the conference system entry and instant messaging (Instant Messaging, IM) functions, so the user applies to third party applications at the terminal, rather than

When IM communication is carried out or a conference or a group chat is carried out, a third party Application (APP) needs to be downloaded in advance, the third party Application APP is clicked and started, a corresponding access window is found, then the conference or the chat group is clicked, the operation process is complex for a user, the time for entering the conference is long, and the user experience is poor.

Disclosure of Invention

The embodiment of the application provides a conference access method and device, so that a conference can be quickly entered, and time consumption is reduced. Specifically, the following technical scheme is disclosed:

in a first aspect, an embodiment of the present application provides a conference access method, which is applied to a terminal device, where the method includes: the terminal equipment acquires at least one group of conference schedules, wherein the conference schedules comprise schedule information of three-party applications, and the conference schedules also comprise conference links and conference content information; the terminal equipment generates a conference list according to the at least one group of conference schedules, wherein the conference list comprises the at least one group of conference summary information, and the conference summary information comprises conference links and at least part of conference contents; the terminal equipment displays a conference list of the at least one group of conference schedules; and receiving conference link operation of a user on a target conference, and entering the target conference in response to the conference link operation.

According to the method provided by the aspect, the conference link function is newly added in the calendar application, when the terminal equipment receives the conference link operation of the user, the target conference access link can be obtained according to the conference link operation, and the target conference can be directly jumped to the target conference of the three-party application through the target conference link, so that one-key conference is realized. The method simplifies the user operation and the waiting time of the operation, and improves the user experience.

With reference to the first aspect, in a possible implementation manner of the first aspect, the generating, by the terminal device, a conference list according to the at least one set of conference schedules includes: the terminal equipment receives at least one group of conference schedules, schedule identifiers are distributed for each conference schedule, and the conference schedules correspond to the schedule identifiers one by one; the terminal equipment acquires the conference summary information according to the at least one group of conference schedules, and the conference summary information corresponds to the schedule identifications one by one; and generating a meeting list of the at least one group of meeting schedules according to the meeting summary information and the schedule identification. According to the method, the schedule identifier is distributed to the conference schedule, so that convenience is provided for searching the conference summary information corresponding to the user link operation subsequently.

With reference to the first aspect, in another possible implementation manner of the first aspect, the obtaining, by the terminal device, the meeting summary information according to the at least one set of meeting schedules includes: the terminal equipment acquires standard format information of the schedule, wherein the standard format information of the schedule comprises the conference link and at least part of conference content.

The standard format information of the schedule also comprises at least one basic field and an expansion field, wherein the basic field records the conference content information, and the expansion field records the conference link. The expansion field also records a schedule detail address, a data source or a group chat address.

Optionally, the standard format information of the schedule is expansion information based on RFC2445 protocol specification.

With reference to the first aspect, in a further possible implementation manner of the first aspect, the displaying, by the terminal device, a meeting list of the at least one set of meeting schedules includes: displaying the conference list on a screen locking interface or an unlocking interface of the terminal equipment in at least one of the following modes; the at least one mode includes: windows or cards.

Wherein, the unlocking interface includes: and the desktop unlocked by the terminal equipment or the application interface of the calendar application unlocked by the terminal equipment.

With reference to the first aspect, in a further possible implementation manner of the first aspect, the displayed conference list of the at least one group of conference schedules further includes: at least one meeting control, each meeting control corresponding to a meeting link. The terminal equipment receives conference link operation of a user on a target conference, and the conference link operation comprises the following steps: and the terminal equipment receives clicking operation of the user on a target meeting control, wherein the target meeting control is one of the at least one meeting control.

With reference to the first aspect, in a further possible implementation manner of the first aspect, the entering, by the terminal device, the target conference in response to the conference link operation includes: and the terminal equipment enters a target conference link according to the click operation of the user on the target conference control, and the target conference link corresponds to the target conference control one by one. And the terminal equipment starts a three-party application corresponding to the target conference link and accesses the conference corresponding to the target conference link.

According to the implementation mode, the conference link function is newly added in the calendar application and is displayed to the user through the conference list, when the terminal equipment receives the conference link operation of the user, the target conference link can be obtained according to the conference link operation, and the target conference link is directly jumped to the conference interface of the three-party application, so that one-key conference is realized. The method simplifies the user operation and the waiting time of the operation, and improves the user experience.

Specifically, the terminal device starts a three-party application corresponding to the target conference link, accesses a conference corresponding to the target conference link, and includes: the three-party application of the terminal equipment receives a meeting request, and the meeting request is triggered by the meeting linking operation; and the three-party application of the terminal equipment jumps to the meeting corresponding to the target meeting link according to the meeting request.

Wherein the at least one conference control is displayed in the conference list by any one of: an "access meeting" control, a "Join meeting" control, or a "Join" control.

Optionally, the conference summary information further includes: meeting time and meeting topic.

Optionally, the conference list includes at least one conference prompt message, and the at least one conference prompt message is arranged according to a time sequence.

In a second aspect, an embodiment of the present application further provides a conference access device, where the device is applied to a terminal device, and the device includes: an acquisition unit, a processing unit, a display unit, a receiving unit, and the like.

The conference schedule comprises schedule information of three-party applications, conference links and conference content information; a processing unit for generating a meeting list according to the at least one set of meeting schedules, the meeting list comprising the at least one set of meeting summary information, the meeting summary information comprising meeting links and at least part of meeting content; a display unit for displaying a meeting list of the at least one group of meeting schedules; the receiving unit is used for receiving conference link operation of a user on a target conference; the processing unit is further configured to enter the target conference in response to the conference link operation.

With reference to the second aspect, in a possible implementation manner of the second aspect, the processing unit is further configured to allocate a schedule identifier to each conference schedule according to the at least one group of conference schedules received by the obtaining unit, where the conference schedules are in one-to-one correspondence with the schedule identifiers; the obtaining unit is further configured to obtain the meeting summary information according to the at least one set of meeting schedules, and generate a meeting list of the at least one set of meeting schedules according to the meeting summary information and the schedule identifier, where the meeting summary information corresponds to the schedule identifier one by one.

With reference to the second aspect, in another possible implementation manner of the second aspect, the obtaining unit is further configured to obtain standard format information of the schedule, where the standard format information of the schedule includes the conference link and the at least part of conference content. The standard format information of the schedule also comprises at least one basic field and an expansion field, wherein the basic field records the conference content information, and the expansion field records the conference link.

Optionally, the display unit is further configured to display the conference list on a screen locking interface or an unlocking interface of the terminal device in at least one of the following manners; the at least one mode includes: windows or cards, etc.

With reference to the second aspect, in a further possible implementation manner of the second aspect, the display unit is further configured to display at least one meeting control in a meeting list of the at least one group of meeting schedules, where each meeting control corresponds to one meeting link. The receiving unit is further configured to receive a click operation of the user on a target meeting control, where the target meeting control is one of the at least one meeting control.

With reference to the second aspect, in a further possible implementation manner of the second aspect, the processing unit is further configured to enter a target conference link according to a click operation of the user on a target conference control, start a three-party application corresponding to the target conference link, and access a conference corresponding to the target conference link. Wherein the target conference links are in one-to-one correspondence with the target conference controls.

Further, the processing unit is further configured to start the three-party application of the terminal device to receive a meeting request, where the meeting request is triggered by the meeting link operation, and control the three-party application of the terminal device to jump to the meeting corresponding to the target meeting link according to the meeting request.

Optionally, the at least one conference control is displayed in the conference list in any one of the following manners: an "access meeting" control, a "Join meeting" control, or a "Join" control.

In a third aspect, embodiments of the present application further provide a terminal device, where the terminal device includes at least one processor and a memory, and further includes: communication module, display screen, at least one sensor etc..

The display screen is a touch display screen. The at least one sensor includes a touch sensor, a pressure sensor, and the like.

Wherein the memory is configured to provide computer program instructions and/or data to the at least one processor; the at least one processor is configured to execute the computer program instructions to implement the methods of the foregoing first aspect and various implementations of the first aspect.

Specifically, the communication module is used for acquiring at least one group of conference schedules, wherein the conference schedules comprise schedule information of three-party applications, and the conference schedules further comprise conference links and conference content information; a processor for generating a meeting list from the at least one set of meeting schedules, the meeting list comprising the at least one set of meeting summary information, the meeting summary information comprising meeting links and at least part of meeting content; the display screen is used for displaying a meeting list of the at least one group of meeting schedules and receiving meeting link operation of a user on a target meeting; the processor is further configured to enter the target meeting in response to the meeting linking operation.

With reference to the third aspect, in a possible implementation manner of the third aspect, the processor is further configured to receive the at least one set of conference schedules, and allocate a schedule identifier to each conference schedule, where the conference schedules are in one-to-one correspondence with the schedule identifiers; and acquiring the conference summary information according to the at least one group of conference schedules, and generating a conference list of the at least one group of conference schedules according to the conference summary information and the schedule identification, wherein the conference summary information corresponds to the schedule identification one by one.

With reference to the third aspect, in another possible implementation manner of the third aspect, the communication module is further configured to obtain standard format information of the schedule, where the standard format information of the schedule includes the conference link and the at least part of conference content.

The standard format information of the schedule also comprises at least one basic field and an expansion field, wherein the basic field records the conference content information, and the expansion field records the conference link. Optionally, the expansion field further records a schedule detail address, a data source or a group chat address.

With reference to the third aspect, in a further possible implementation manner of the third aspect, the display screen is further configured to display the conference list on a screen locking interface or an unlocking interface of the terminal device in at least one of the following manners; the at least one mode includes: windows or cards.

With reference to the third aspect, in a further possible implementation manner of the third aspect, the display screen is further configured to display at least one meeting control in a meeting list of the at least one group of meeting schedules, where each meeting control corresponds to a meeting link; and receiving clicking operation of the user on a target meeting control, wherein the target meeting control is one of the at least one meeting control.

Further, the processor is further configured to enter a target conference link according to a click operation of the user on a target conference control, where the target conference link corresponds to the target conference control one by one; and starting the three-party application corresponding to the target conference link, and accessing the conference corresponding to the target conference link.

With reference to the third aspect, in a further possible implementation manner of the third aspect, the processor is further configured to start a three-party application of the terminal device to receive a meeting request, where the meeting request is triggered by the meeting link operation, and control the three-party application of the terminal device to jump to a meeting corresponding to the target meeting link according to the meeting request.

In the alternative, the at least one processor and the memory may be integrated in one processing chip or chip circuit.

Optionally, the terminal device includes, but is not limited to, a mobile phone, a PC, and a tablet computer.

In a fourth aspect, the present application also provides a computer readable storage medium having instructions stored therein such that when the instructions are run on a computer or processor, they can be used to perform the method of the foregoing first aspect and various implementations of the first aspect.

In addition, embodiments of the present application also provide a computer program product comprising computer instructions which, when executed by a computer or processor, implement the method of the foregoing first aspect and various implementations of the first aspect.

It should be noted that, the beneficial effects corresponding to the technical solutions of the various implementation manners of the second aspect to the fourth aspect are the same as the beneficial effects of the foregoing first aspect and the various implementation manners of the first aspect, and detailed descriptions of the beneficial effects of the foregoing first aspect and the various implementation manners of the first aspect are omitted.

Drawings

Fig. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application;

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

fig. 3 is a schematic diagram of a display interface including a "calendar application" APP on a terminal device provided in an embodiment of the present application;

fig. 4 is a flowchart of a conference access method provided in an embodiment of the present application;

fig. 5 is a flowchart of another conference access method provided in an embodiment of the present application;

FIG. 6a is a schematic diagram of a target meeting control displayed in an "immediate notification bit" according to an embodiment of the present application;

FIG. 6b is a schematic diagram of a target meeting control displayed with a "shallow find bit" according to an embodiment of the present application;

FIG. 6c is a schematic diagram of a target meeting control displayed in a "global archive location" according to an embodiment of the present application;

FIG. 6d is a schematic diagram of a "meeting" control displayed in "calendar details" according to an embodiment of the present application;

FIG. 7 is a schematic diagram of interface interaction of a one-touch conference according to an embodiment of the present application;

fig. 8 is a signaling flow chart of a conference access method provided in an embodiment of the present application;

fig. 9 is a schematic structural diagram of a conference access device according to an embodiment of the present application.

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application, the following describes the technical solutions in the embodiments of the present application in detail with reference to the accompanying drawings.

Before the technical scheme of the embodiment of the application is described, an application scenario of the embodiment of the application is described with reference to the accompanying drawings. The technical solutions of the embodiments of the present application may be applied to various communication systems, such as a wireless local area network (Wireless Local Area Network, WLAN), global system for mobile communications (global system for mobile communications, GSM) system, code division multiple access (code division multiple access, CDA) system, wideband code division multiple access (wide band code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), general mobile communication system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (world wide interoperability for microwave access, wiMAX) communication system, future fifth generation (5th generation,5G) system, new Radio (NR), etc. As shown in fig. 1, in any of the above communication systems, there is included: terminal equipment and network equipment carried by at least one user, etc.

The terminal device may be a portable device, such as an intelligent terminal, a mobile phone, a notebook computer, a tablet computer, a personal computer (personal computer, PC), a personal digital assistant (personal digital assistant, PDA), a foldable terminal, a wearable device (e.g. a smart watch or a bracelet) with a wireless communication function, a user device (UE) or a User Equipment (UE), a game console, and an augmented reality (augmented reality, AR) \virtual reality (VR) device, where the embodiment of the present application does not limit the specific device configuration of the terminal device. In addition, an Android (Android) system is mounted in the various terminal devices.

Fig. 2 is a schematic hardware structure of a terminal device according to an embodiment of the present application. As shown in fig. 2, the terminal device 100 may include a processor 110, a memory 120, a universal serial bus (universal serial bus, USB) interface 130, a radio frequency circuit 140, a mobile communication module 150, a wireless communication module 160, a camera 170, a display 180, a sim card interface 190, a touch sensor 200, a pressure sensor 210, keys 220, and the like.

The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. The different processing units may be separate devices or may be integrated in one or more processors, for example, in a system on a chip (SoC). A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface 190, and/or a USB interface 130, among others.

Memory 120 may be used to store computer-executable program code that includes instructions. The memory 120 may include a stored program area and a stored data area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. The storage data area may store data (e.g., audio data, phonebook) created during use of the terminal device 100, etc. In addition, the memory 120 may include one or more memory units, for example, may include volatile memory (RAM) such as random access memory (dynamic access memory), nonvolatile memory (NVM) such as read-only memory (ROM), flash memory (flash memory), and the like. The processor 110 performs various functional applications of the terminal device 100 and data processing by executing instructions stored in the memory 120 and/or instructions stored in a memory provided in the processor.

The wireless communication function of the terminal device 100 may be implemented by the radio frequency circuit 140, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The radio frequency circuit 140 may include at least one antenna 141 for transmitting and receiving electromagnetic wave signals. Each antenna in the terminal device 100 may be used to cover a single or multiple communication bands. In some embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 141, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 may amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 141 to radiate the electromagnetic waves. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (including but not limited to speakers, receivers, etc.) or displays images or video through the display 180. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

The wireless communication module 160 may include a wireless fidelity (wireless fidelity, wiFi) module, a Bluetooth (BT) module, a GNSS module, a near field communication technology (near field communication, NFC) module, an Infrared (IR) module, and the like. The wireless communication module 160 may be one or more devices integrating at least one of the modules described above. The wireless communication module 160 receives electromagnetic waves via the antenna 141, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 141.

In this embodiment, the wireless communication functions of the terminal device 100 may include, for example, functions of the global system for mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), fifth generation mobile communication technology new air interface (5th generation mobile networks new radio,5G NR), BT, GNSS, WLAN, NFC, FM, and/or IR. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

The camera 170 is used to capture still images or video. The camera 170 includes a lens and a photosensitive element, and an object is projected to the photosensitive element by generating an optical image through the lens. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, RYYB, or the like format. In some embodiments, the terminal device 100 may include 1 or N cameras 170, N being a positive integer greater than 1.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent awareness of the terminal device 100 may be implemented by the NPU, for example: image recognition, face recognition, voice recognition, and the like.

The display 180 is used to display images, videos, and the like. The display 180 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), miniLED, microLED, micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, terminal device 100 may include 1 or N displays 180, N being a positive integer greater than 1.

Touch sensor 200, also referred to as a "touch device". The touch sensor 200 may be disposed on the display screen 180, and the touch sensor 200 and the display screen 180 form a touch screen, which is also referred to as a "touch screen". The touch sensor 200 is used to detect a touch operation acting on or near it. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 180. In other embodiments, the touch sensor 200 may also be disposed on a surface of the terminal device 100 at a different location than the display 180. The pressure sensor 210 is used to measure the pressure value of the user's touch screen. In addition, other sensors such as a gyroscope sensor, an acceleration sensor, a temperature sensor, and the like may also be included.

The keys 220 include a power-on key, a volume key, etc. The key 220 may be a mechanical key. Or may be a touch key. The terminal device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the terminal device 100.

It is to be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the terminal device. In other embodiments of the present application, the terminal device may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

In addition, the network device includes, but is not limited to, a cloud server, a third party platform, a data center, a computing unit, and the like, and the function of the network device may be the same as or different from the structure of the terminal device 100 shown in fig. 2, and the structure and the form of the network device are not specifically limited in this embodiment.

The server, the third party platform, the data center or the computing unit and other various network devices are development platforms, namely all users can access the cloud end through the client.

The application layer of the terminal equipment comprises a plurality of application APP. Among the applications 1 to 8, the application 4 is a three-party application APP, which has a conference video function, such as nailing or flying book.

In addition, optionally, the terminal device further includes a storage application APP, a clock, a gallery, a memo, and other application APPs, which is not limited in this embodiment. It should be noted that, in the display interface shown in fig. 3, the "calendar application" and the storage application (application 7) are two different APPs, and in other embodiments, the "calendar application" and the "storage application" APPs are combined into the same APP. The combined APP can perform data transmission with the three-party application so as to realize the function of one-key meeting in the three-party application.

In addition, in the software architecture of the terminal device, a calendar provider, a content provider, and the like are also included in the application framework layer of the terminal device. Wherein the calendar provider is a repository for user calendar events. The calendar provider allows users to perform queries, inserts, updates, deletes operations regarding calendar, event, meeting, reminder, etc. content. In addition, the calendar provider can also access other applications, synchronization adapters, content providers, etc. using the application program interface (Application Programming Interface, API).

Wherein the content provider is operable to store data and provide access data for APP of the application layer. Typically, the data is provided by an Android platform (including calendar providers) content provider in the form of a collection of tables based on a relational database model, one record per row and one specific type of data per column. Through the calendar provider API, applications and synchronization adapters can obtain read and write access rights to database tables holding user calendar data.

In addition, each content provider provides a common Uri (encapsulated as a Uri object) that uniquely identifies its data set. A content provider controls multiple data sets (multiple tables), each of which is exposed to a separate Uri. In addition, all the Uris of the content provider start with "content//" which is an identification of the data as controlled by the content provider. The calendar provider defines for each class (table) it a Uri constant, one format of Uri being < class >. Content_uri. For example: event.

The method provided in this embodiment will be described in detail.

The conference access method provided in this embodiment is applied to any one of the foregoing terminal devices, and referring to fig. 4, the method includes:

401: the terminal equipment acquires at least one group of conference schedules, wherein the conference schedules comprise schedule information of three-party applications, and the conference schedules further comprise conference links and conference content information.

The conference content information is used for describing basic information of a conference schedule, the conference link is used for describing an address of a conference, and the conference address is an access address of a third application. Further, the address of the meeting includes a uniform resource identifier (Universal Resource Identifier, uri) or a uniform resource locator (Universal Resource Locator, url).

Optionally, the meeting schedule is schedule standard format information, and the schedule standard format information is based on contents on a solicited opinion (Request For Comments, RFC) 2445 protocol version and is used for describing relevant information of the schedule. Further, the schedule standard format information or RFC2445 protocol version includes at least one basic field and an extension field, wherein the basic field records the conference content information, and the extension field records the conference link (meetingInfoUri).

Among them, RFCs are a series of memos issued by the internet engineering task force (The Internet Engineering Task Force, IETF). The memo collects information about the internet and software files of UNIX and internet communities to number the memo. The RFC2445 protocol version mainly describes a standard data format for calendars (Calendar) and defines relevant fields and rules for calendars for implementing functions of creation, reminding, etc. of Calendar applications in an android system. The present embodiment adds an extension field based on RFC2445 protocol version content.

In addition, the expansion field also records schedule detail address (eventInfoUri), data source (dataSource), group chat address and other contents.

It should be noted that, the "conference link" is a wide range of access link addresses, including, but not limited to, a conference access address provided by a three-party application, a chat address provided by a three-party application, a group chat access address, or a live broadcast access address.

Optionally, in step 401, the terminal device may periodically acquire meeting schedule information, or after the server creates a meeting schedule, the meeting schedule is sent to the terminal device, and the manner in which the terminal device acquires the meeting schedule is not limited in this embodiment.

402: the terminal device generates a conference list according to the at least one group of conference schedules, wherein the conference list comprises the at least one group of conference summary information, and the conference summary information comprises conference links and at least part of conference contents.

Specifically, as shown in fig. 5, the step 402 includes:

4021: the terminal equipment receives at least one group of conference schedules, schedule identifiers are distributed for each conference schedule, and the conference schedules correspond to the schedule identifiers one by one.

Wherein the conference schedule can be represented by a schedule (event) table, each event table can be represented by a schedule identification (event ID), and the conference schedule event table has a unique correspondence with the schedule identification event ID. As shown in table 1 below, is a correspondence between an event table and an event ID, and detailed information of a single schedule (or event). The "event table" is all called "CalendarContract. Events".

Alternatively, the schedule event in this embodiment may also be referred to as an "event".

Table 1, correspondence between meeting schedules and schedule identifications

As can be seen from table 1, the correspondence between specific meeting schedule information and EVENT/schedule identification is recorded in table 1, wherein each row has information of a single EVENT, such as a TITLE (time), an EVENT place (event_location), a start time (DTSTART), an end time (DTEND), etc. In addition, the event can occur once or repeatedly. Each event table is associated with an event ID, i.e. a one-to-one correspondence between a calendar identity and a meeting calendar. For example, in table 1, a schedule identifier corresponding to a meeting schedule is event ID 1.

Similarly, if a plurality of conference schedules exist, the corresponding relation between the conference schedules and the schedule identifications is established, and one conference schedule corresponds to one schedule identification.

The method further comprises the following steps: 4022: and the terminal equipment acquires conference summary information according to the at least one group of conference schedules, wherein the conference summary information corresponds to the schedule identifications one by one.

In particular, the meeting summary information includes a meeting link and at least a portion of meeting content. For example, the meeting summary information may be presented in table 2. Referring to table 2, a conference summary information table, which may also be referred to as a relationship (relationship) information table, is shown.

Table 2, conference summary information table

The conference summary information table includes conference links and conference contents, for example, the conference links include: eventInfoUri, meetingInfoUri and dataSource, etc. for recording meeting/calendar access addresses, and data sources, etc. The conference content includes: schedule creation time, schedule update time, schedule identification, id of the schedule, etc.

Alternatively, the above-mentioned association information table may be added to the RFC2445 protocol version by means of at least one field, for example, in a directory of the RFC2445 protocol version, and a new theme is added to record the association information table. It should be appreciated that at least one extended field (extendData) may also be added to the association information table for recording other data.

4023: and the terminal equipment generates a conference list of the at least one group of conference schedules according to the conference summary information and the schedule identification.

In a possible implementation manner, the terminal device generates a meeting list of the at least one group of meeting schedules according to the schedule identifier shown in the table 1 and the meeting summary information shown in the table 2, and binds the schedule identifier (event ID) and the meeting summary information to generate a meeting list of the group of meeting schedules, as shown in the table 3.

Table 3, conference list of a set of conference schedules

In addition, the method further comprises the steps of: the terminal device stores a list of meetings of the at least one set of schedules.

In this embodiment, the terminal device is in a native android system framework, for example

The method comprises the steps that on the basis of a android system framework which is not modified by a third party, a company releases, at least one group of schedule meeting lists are obtained, wherein each group of schedule meeting list comprises an association relationship between a schedule identifier and a meeting link, and convenience is provided for subsequent rapid jump.

Wherein the conference link includes a conference access address and/or a calendar access address. The at least part of the conference content includes part or all of the conference content shown in the foregoing table 2 or table 3.

For example, the meeting summary information further includes: meeting time, meeting topic, and other primary cues. For example, the meeting time is: 8:00 am to 10:00 am, the meeting topic is "office entertainment seminar".

403: the terminal device displays a meeting list of the at least one set of meeting schedules.

Wherein the terminal device displays a meeting list of the at least one group of meeting schedules, including: and displaying the conference list on a screen locking interface or an unlocking interface of the terminal equipment in at least one of the following modes. The at least one mode includes: windows or cards. Wherein, the unlocking interface includes: and the terminal equipment is an unlocked desktop or an unlocked application interface of the calendar application.

In addition, the conference list of the at least one group of conference schedules displayed on the screen locking interface or the screen unlocking interface of the terminal equipment further comprises: at least one meeting control, each meeting control corresponding to a meeting link.

Specifically, a group of conference lists are displayed on a screen locking interface of the terminal equipment when the terminal equipment is in a screen locking state. The conference list comprises conference links and partial conference contents, wherein the partial conference contents comprise: meeting time, meeting theme, meeting personnel. For example, as shown in fig. 6a, a window of a meeting notification is displayed on a screen locking interface of the terminal device, where the window includes a meeting time: 8:00 am to 10:00 am, conference subject: "office entertainment seminar", attendees, and "access conference". The meeting access control is a meeting access control corresponding to the meeting link. In addition, other controls may be included, such as a "meeting details" control, and the like.

Optionally, if the terminal device is in an unlocked state, displaying the conference list on an unlocking interface of the terminal device. For example, as shown in fig. 6b, an unlock interface is provided that includes a window and controls for a plurality of applications, such as an application mall, sports health, weather, email, etc. Wherein, the window comprises a conference list, and the conference list comprises three groups of conference summary information. A meeting control "Join" is included in the first set of meeting summary information, the "Join" control corresponding to a meeting link of the first set of meeting schedules.

Alternatively, another implementation of displaying the conference list on the unlock interface is to display the conference list in a calendar application of the unlock interface, as shown in fig. 6 c. After the user opens the "calendar" application, the meeting list is displayed on the first application interface of the "calendar" application. The conference list includes conference prompt information of three conferences, and the conference prompt information can be arranged according to time sequence. Examples include: meeting reminder 1, "working discussion 1" from 08:30 to 12:00; meeting reminder 2, "working discussion 2" from 13:00 to 18:00; meeting prompt 3, from 19:00 later, "buy birthday cake for daughter". The conference prompt information comprises a conference control "Join" which is presented to the user.

Optionally, when the meeting list is displayed in the calendar application of the unlocking interface, more detailed meeting information may also be displayed. For example, as shown in fig. 6d, the meeting list is displayed on the second application interface of the "calendar" application, where the meeting list includes a set of details of the meeting schedule. Such as information including meeting topic, meeting time, meeting link, meeting ID, chairman password, guest password, participant, location, time zone, etc. In the example of fig. 6d, the conference theme is: UXD design review; meeting time is 10:30 to 12:00 am, and the date is 9 months, 10 days and thursday; the conference control corresponding to the conference link is 'joining xx video conference'; the conference ID is: xxx xxx; the number of participants is 4, the place is located in conference hall 1, and the current time zone is: gtm+8.00, chinese standard time zone, etc.

It should be understood that, in this embodiment, the manner of displaying the conference list on the terminal device includes, but is not limited to, a window or card manner, and other manners, such as a message bar, etc., may also be adopted, and the specific display method is not limited in this embodiment.

404: and the terminal equipment receives the conference link operation of the user on the target conference.

The target conference is a conference which the user desires to access. The conference link of the target conference is accessed through a target conference access control, such as an access conference control or a Join control, and is displayed in a window or a card of the terminal device. In a specific embodiment, the user clicks the meeting control in any one of the meeting lists in fig. 6a to 6d, the meeting control clicked by the user is a target meeting control, the terminal device receives the click operation of the user on the target meeting control, and the target meeting control is one of the at least one meeting control.

405: and the terminal equipment responds to the conference link operation to enter the target conference.

Specifically, the method comprises the following steps: and the terminal equipment enters a target conference link according to the click operation of the user on the target conference control, and the target conference link corresponds to the target conference control one by one. And the terminal equipment starts the three-party application corresponding to the target conference link and accesses the conference corresponding to the target conference link.

For example, taking fig. 6a as an example, when the user clicks the "access meeting" control of the window on the lock screen interface, the terminal device obtains a content uniform resource identifier (contentUri) according to the operation of the user, where the content uniform resource identifier (contentUri) is obtained, the contentUri corresponds to a schedule identifier, in this embodiment, the schedule identifier corresponding to the contentUri is called as a target schedule identifier, for example, the target schedule identifier is called as event ID 1, and because of the corresponding relationship between the established schedule identifier and meeting summary information, according to the event ID 1, meeting summary information having a unique corresponding relationship with the event ID 1 can be found, and according to the corresponding relationship of the table 3, target meeting summary information including a meeting access address (meeting infouri) is determined, where the access address is the target meeting link, and after finding the target meeting link, the target meeting link is directly transferred to the target meeting according to the target meeting link.

As shown in fig. 7, after clicking the "access meeting" control in the meeting list displayed by the terminal device, the user determines the target meeting link according to the above step 405, and directly jumps to the meeting interface corresponding to the target meeting link, so as to implement a typing meeting operation of the user.

According to the method provided by the embodiment, the conference link function is newly added in the calendar application and is displayed to the user through the conference list, when the terminal equipment receives the conference link operation of the user, the target conference access address can be obtained according to the conference link operation, and the conference interface of the three-party application is directly jumped to through the target conference access address, so that one-key conference is realized. The method simplifies the user operation and the waiting time of the operation, and improves the user experience.

Optionally, the terminal device may include a calendar application, a three-party application, and a storage application, as shown in fig. 8, where the foregoing conference access method specifically includes the following steps:

801: the terminal equipment acquires basic data and expansion data of the conference schedule. The expansion data comprises conference links.

Specifically, in the process of communication with the cloud server, the terminal device executes step 801 when the acquisition server creates a meeting schedule message. For example, after determining that the user identity of the client is legal, the server sends the basic data and the expansion data to the terminal device.

The basic data mainly describe basic information of schedules, and comprises time, places, meeting personnel information, number of meeting personnel, description and the like. Optionally, the base data is related data in RFC2445 protocol. The expansion data is an expansion field, the expansion field is based on some newly added fields in the RFC2445 protocol, such as a relation protocol field, and the relation protocol field is used for describing conference addresses, data sources (dataSource) and the like, or the relation protocol field contains an access address which needs to be entered. Such as eventInfoUri and meetingInfoUri.

Specific transmission mode this embodiment is not limited thereto. The sending mode is that the server packages and encapsulates the basic data and the expansion data into an ics file package, and sends the ics file package to the terminal equipment. Wherein the Ics file is an iCalendar format file created by Microsoft Outlook 2002 or higher.

Correspondingly, the terminal equipment receives the ics file packet sent by the server. This step corresponds to step 401 of the previous embodiment.

802: and the terminal equipment creates a relation information table according to the basic data and the expansion data, and inserts a schedule identifier (event ID) into the relation information table to obtain a conference list of at least one group of conference schedules.

Specifically, the calendar application of the terminal device receives an ics file package acquired from an application layer, analyzes the ics file package to obtain the basic data and the expansion data, creates a relation information table according to the basic data and the expansion data, and associates an event ID with the relation information table to obtain a conference list of at least one group of conference schedules, as shown in the foregoing table 3. The specific procedure is the same as step 402 of the previous embodiment.

Optionally, step 802 may also be implemented by a calendar application and a storage application, which may be a calendar provider and/or a content provider of the foregoing embodiments. In one implementation, the calendar application sends the parsed base data and the parsed extension data to the storage application. After the storage application receives the data, a relationship information table and a schedule base data table (event table) are created. The relation information table includes expansion data such as eventInfoUri, meetingInfoUri. The aforementioned basic data is described in the event tables, and each event table can be identified by an event ID, which can be preconfigured by the terminal device. The storage application inserts the event_id into the relationship information table to generate a meeting list of at least one set of meeting schedules, as shown in table 3 above.

The storage application stores a meeting list of the at least one set of meeting schedules.

803: the terminal device obtains a user operation by which the user clicks on the "calendar" application on the display interface, the user operation indicating that the user desires to view the schedule that has been created.

804: and responding to the view operation of the user, displaying a meeting list of the at least one group of meeting schedules, wherein the meeting list comprises a target meeting schedule list. The target meeting calendar is part or all of the meeting list of at least one set of meeting calendars generated in step 802 above.

One possible implementation is when the user clicks on a "calendar" application, the calendar application obtains the ContentUri to which the user operation corresponds. The contentru is understood as a tool class, and is mainly used for processing a Uri object using a content constraint, and the syntax format of the contentru object is as follows: content/(author// path/id), where author is a string that identifies Content provider, all Content Uri begins with this string, which is unique and is commonly identified by a class name. A path may be a table in a database or a field in a table, "/" is used to separate tables and fields; id is a unique identification of each record in the database, i.e., an id number.

The calendar application looks up a target meeting calendar list corresponding to the ContentUri according to the ContentUri, and the list can be also called a target event list, wherein the target event list comprises a target calendar identifier (event ID), and further the target event ID corresponding to the ContentUri is determined. And searching a target conference link corresponding to the event ID in the corresponding relation stored in the step 802 by utilizing the target event ID.

The target conference link corresponds to a target conference access control, such as an "access conference" control or a "Join" control, and as shown in fig. 6a, an "immediate notification bit" window displays the "access conference" control on a screen locking interface of the terminal device. Similarly, as shown in fig. 6b, the target meeting control displayed in a "shallow search bit" manner on the unlocking interface of the terminal device is an example, where the target meeting control is a "Join" icon; FIG. 6c is an example of a target meeting control displayed in a "global archive location," which is also a "Join" icon; fig. 6d is an example of a target meeting control displayed in "calendar details," which is an "join xx video conference" icon.

Optionally, before displaying the target meeting control, the method further includes: judging whether the target meeting schedule list comprises a meeting link, namely a target meeting link, and if so, displaying the target meeting control. If not, the search fails, and the user is prompted to search the conference schedule again.

805: and the terminal equipment receives the operation that the user clicks the target meeting control on the terminal equipment.

806: and the terminal equipment enters the target conference links according to the click operation of the user on the target conference control, the target conference links are in one-to-one correspondence with the target conference control, and the three-party application corresponding to the target conference links is started.

807: and the three-party application starts and accesses the conference corresponding to the target conference link.

Specifically, after receiving the operation that the user clicks the target meeting control, the calendar application sends an meeting request to the three-party application, and after receiving the meeting request, the three-party application directly jumps to a meeting corresponding to the target meeting link according to the meeting request, and enters a meeting by one key, and at the moment, the user enters the target meeting interface. For example, as shown in fig. 7, after the user clicks the target meeting control of "meeting access", the three-party application APP is directly started from the current notification interface, and jumps to the meeting interface of the three-party application APP, for example, jumps to the display interface of the nailed meeting, so as to achieve the effect of one-key meeting.

An embodiment of the apparatus corresponding to the present embodiment of the above-described method is described below.

The present embodiment provides a conference access device, which may be a terminal device, and its structure may refer to the terminal device shown in fig. 2, and includes a processor 110, a memory 120, a mobile communication module 150, a wireless communication module 160, an antenna 141, a radio frequency circuit 140, a display screen 180, a touch sensor 200, and the like.

Alternatively, the number of the processors 110 may be one or more, which is not limited in this embodiment.

Wherein, at least one of the mobile communication module 150, the wireless communication module 160, the antenna 141 and the radio frequency circuit 140 may be collectively referred to as a communication module, and the communication module is configured to obtain at least one set of conference schedules, where the conference schedules include schedule information of three-party applications, and the conference schedules further include conference links and conference content information. Processor 110 is configured to generate a meeting list from the at least one set of meeting schedules, the meeting list including the at least one set of meeting summary information, the meeting summary information including meeting links and at least a portion of meeting content.

The display screen 180 is used for displaying a meeting list of the at least one group of meeting schedules and receiving meeting link operation of a user on a target meeting; the display 180 is connected to the touch sensor 200, and senses a touch operation of a user. The processor 110 is further configured to enter the target meeting in response to the meeting linking operation.

Wherein the meeting summary information further includes: meeting time and meeting topic.

Optionally, in a possible implementation manner of this embodiment, the processor 110 is further configured to receive the at least one set of conference schedules, and allocate a schedule identifier to each of the conference schedules, where the conference schedules are in a one-to-one correspondence with the schedule identifiers; and acquiring the conference summary information according to the at least one group of conference schedules, and generating a conference list of the at least one group of conference schedules according to the conference summary information and the schedule identification, wherein the conference summary information corresponds to the schedule identification one by one.

Optionally, in another possible implementation manner of this embodiment, the communication module is further configured to obtain standard format information of the schedule, where the standard format information of the schedule includes the conference link and the at least part of conference content.

The standard format information of the schedule also comprises at least one basic field and an expansion field, wherein the basic field records the conference content information, and the expansion field records the conference link. Further, the expansion field also records a schedule detail address, a data source and a group chat address.

In addition, the display screen 180 is further configured to display the conference list on a screen locking interface or an unlocking interface of the terminal device in at least one of the following manners; the at least one mode includes: windows or cards. Wherein, the unlocking interface includes: and the desktop unlocked by the terminal equipment or the application interface of the calendar application unlocked by the terminal equipment.

Optionally, the display screen 180 is further configured to display at least one meeting control in the meeting list of the at least one group of meeting schedules, where each meeting control corresponds to a meeting link; and receiving clicking operation of the user on a target meeting control, wherein the target meeting control is one of the at least one meeting control.

Optionally, in another possible implementation manner of this embodiment, the processor 110 is further configured to enter a target conference link according to a click operation of the target conference control by the user, where the target conference link is in one-to-one correspondence with the target conference control; and starting the three-party application corresponding to the target conference link, and accessing the conference corresponding to the target conference link.

Further, the processor is further configured to start the three-party application of the terminal device to receive a meeting request, where the meeting request is triggered by the meeting link operation, and control the three-party application of the terminal device to jump to the meeting corresponding to the target meeting link according to the meeting request.

Optionally, in another possible implementation manner of this embodiment, the memory 120 is configured to store a meeting list of the at least one group of meeting schedules.

In addition, the communication module is further used for receiving data and/or data packets sent by the server or the cloud network device.

It should be noted that the functions of the communication module, the processor 110, the display screen 180, and the memory 120 may also be implemented by software, for example, as shown in fig. 9, which is a schematic structural diagram of a conference access device, where the device includes: the acquisition unit 901, the processing unit 902, the display unit 903, and the receiving unit 904, and may further include other units and modules, such as a storage unit, a transmission unit, and the like, which are not limited in this embodiment.

The acquiring unit 901 is configured to acquire at least one group of conference schedules, where the conference schedules include schedule information of three-party applications, and the conference schedules further include conference links and conference content information; a processing unit 902, configured to generate a meeting list according to the at least one set of meeting schedules, where the meeting list includes the at least one set of meeting summary information, and the meeting summary information includes a meeting link and at least part of meeting content; a display unit 903 for displaying a meeting list of the at least one group of meeting schedules; a receiving unit 904, configured to receive a meeting linking operation of a user on a target meeting; the processing unit 902 is further configured to enter the target conference in response to the conference link operation.

In addition, the acquisition unit 901, the processing unit 902, the display unit 903, and the receiving unit 904 are also used to implement the conference access method shown in fig. 4, 5, and 8 described above.

The embodiment of the application also provides a wireless communication system, which comprises at least one terminal device and a network device, wherein the terminal device is the apparatus shown in fig. 9 or fig. 2, and can be used to implement the methods shown in fig. 4, fig. 5 and fig. 8 in this embodiment. The structure of the network device may be the same as or different from that of the terminal device, which is not limited in this embodiment.

According to the system provided by the embodiment, the conference link function is newly added in the calendar application and is displayed to the user through the conference list, when the terminal equipment receives the conference link operation of the user, the target conference access address can be obtained according to the conference link operation, and the conference interface of the three-party application is directly jumped to through the target conference access address, so that one-key conference is realized. The method simplifies the user operation and the waiting time of the operation, and improves the user experience.

Furthermore, embodiments of the present application provide a computer program product comprising one or more computer program instructions. When loaded and executed by a computer, produces, in whole or in part, a method flow or function as described in the various embodiments above. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus.

Wherein the computer program product may be stored in the memory 120. In addition, the memory 120 is further configured to store information such as at least one set of meeting schedules, a meeting list of at least one set of meeting schedules, and the like in the foregoing embodiments.

Furthermore, in the description of embodiments of the present application, unless otherwise indicated, "at least one" refers to one or more than one. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

The above-described embodiments of the present application are not intended to limit the scope of the present application.

Claims

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

the calendar application of the terminal equipment acquires at least one group of conference schedules from a server, wherein the conference schedules comprise schedule information of a three-party application, the conference schedules further comprise conference links and conference content information, and the server sends the schedule information to the terminal equipment after determining that the user identity of the terminal equipment is legal;

The storage application of the terminal equipment receives at least one group of conference schedules from the calendar application of the terminal equipment, allocates schedule identifiers for each conference schedule, wherein the conference schedules correspond to the schedule identifiers one by one, and each schedule identifier corresponds to a content uniform resource identifier;

the storage application of the terminal equipment acquires conference summary information according to the at least one group of conference schedules, and the conference summary information corresponds to the schedule identifications one by one;

the storage application of the terminal equipment generates a conference list of the at least one group of conference schedules according to the conference summary information and the schedule identifier;

the calendar application of the terminal device obtains the meeting list of the at least one group of meeting schedules from the storage application of the terminal device; the meeting list includes at least one set of the meeting summary information including a meeting link and at least a portion of meeting content;

displaying the conference list of the at least one group of conference schedules in a calendar application of a screen locking interface or an unlocking interface of the terminal equipment, wherein the conference list comprises at least one conference control;

responding to the operation of clicking a target meeting control by a user, acquiring a target content uniform resource identifier corresponding to the target meeting control by a calendar application of the terminal equipment, and determining a target schedule identifier corresponding to the target content uniform resource identifier; determining target conference summary information corresponding to the target schedule identifier, and acquiring a target conference link from the target conference summary information; starting a three-party application corresponding to the target conference link, wherein the three-party application has a conference video function; wherein the target meeting control is one of the at least one meeting control;

And the three-party application of the terminal equipment receives an admission request sent by a calendar application of the terminal equipment and jumps to the target meeting corresponding to the target meeting link according to the admission request.

2. The method of claim 1, wherein the storage application of the terminal device obtains the meeting summary information according to the at least one set of meeting schedules, comprising:

and the storage application of the terminal equipment acquires standard format information of the schedule, wherein the standard format information of the schedule comprises the conference link and at least part of conference content.

3. The method of claim 2, wherein the standard format information of the schedule further comprises at least one base field and an extension field, the base field recording the meeting content information and the extension field recording the meeting link.

4. The method of claim 3, wherein the extension field also records a calendar detail address, a data source, or a group chat address.

5. The method according to any of claims 1-4, wherein displaying the meeting list of the at least one set of meeting schedules in a calendar application of a lock screen interface or an unlock interface of the terminal device comprises:

Displaying the conference list in a calendar application of a screen locking interface or an unlocking interface of the terminal equipment in at least one of the following modes;

the at least one mode includes: windows or cards.

6. The method of claim 5, wherein the unlocking interface comprises:

and the desktop unlocked by the terminal equipment or the application interface of the calendar application unlocked by the terminal equipment.

7. The method of any of claims 1-4, wherein displaying the meeting list for the at least one set of meeting schedules further comprises: displaying at least one conference control in the conference list of the at least one group of conference schedules, wherein each conference control corresponds to one conference link;

the calendar application of the terminal equipment receives meeting linking operation of a user on a target meeting, and the calendar application comprises the following steps:

and the calendar application of the terminal equipment receives clicking operation of the user on a target meeting control, wherein the target meeting control is one of the at least one meeting control.

8. The method as recited in claim 1, further comprising:

the conference call request is triggered by the conference link operation.

9. The method of claim 7, wherein the at least one meeting control is displayed in the meeting list by any one of:

an "access meeting" control, a "Join meeting" control, or a "Join" control.

10. The method of any of claims 1-4, wherein the meeting summary information further comprises: meeting time and meeting topic.

11. A terminal device comprising a memory and at least one processor, wherein,

the memory stores one or more computer programs therein;

the at least one processor, when executing the one or more computer programs, causes the terminal device to implement the method of any of claims 1-10.

12. A computer-readable storage medium, wherein computer program instructions are stored in the computer-readable storage medium,

the method of any one of claims 1 to 10 when executed by the computer program instructions.