CN113824572A

CN113824572A - Conference access method and device

Info

Publication number: CN113824572A
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: 2021-12-21
Anticipated expiration: 2041-05-11
Also published as: CN113824572B; WO2022237543A1

Abstract

A conference access method and device, the method comprising: the method comprises the steps that terminal equipment receives and acquires at least one group of meeting schedules, wherein the meeting schedules comprise schedule information of three-party application, and the meeting schedules also comprise meeting links and meeting content information; the terminal equipment generates a meeting list according to the at least one group of meeting schedules, the meeting list comprises the at least one group of meeting summary information, and the meeting summary information comprises meeting links and at least part of meeting content; the terminal equipment displays the conference list of the at least one group of conference schedules, receives the conference link operation of the user to the target conference, responds to the operation to enter the target conference, and realizes one-touch 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 the user to perform a series of operations on the contents of calendars, events, meetings, reminders, etc., including, for example, query, insert, update, delete operations, etc. The calendar provider in the terminal may control a calendar application APP in the application layer, which is usually preset in the mobile phone for managing the schedule of the third-party platform, such as synchronizing schedule data created by the user into a resource library of the system calendar.

However, the calendar provider does not have the functions of conference system entry and Instant Messaging (IM), so the user has a third party application at the terminal, such as

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 APP is clicked and started, a corresponding access window is found, and then the APP is clicked to enter the conference or the chat group.

Disclosure of Invention

The embodiment of the application provides a conference access method and a conference access device, so that a conference can be rapidly accessed, 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 method comprises the steps that terminal equipment obtains at least one group of meeting schedules, wherein the meeting schedules comprise schedule information of three-party application, and the meeting schedules further comprise meeting links and meeting content information; the terminal equipment generates a conference list according to the at least one group of conference schedule information, 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 a conference link operation of a user on a target conference, and entering the target conference in response to the conference link operation.

The method provided by the aspect adds a conference link function in the calendar application, and when the terminal equipment receives the conference link operation of the user, the terminal equipment can obtain the target conference access link according to the conference link operation and directly skips to the target conference of the three-party application through the target conference link, thereby realizing one-touch conference. 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 meeting list according to the at least one group of meeting schedules includes: the terminal equipment receives the at least one group of meeting schedules and allocates schedule identification to each meeting schedule, and the meeting schedules correspond to the schedule identification 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 identification one by one; and generating a conference list of the at least one group of conference schedules according to the conference summary information and the schedule identification. According to the implementation mode, the schedule identification is distributed for the conference schedule, so that convenience and rapidness are provided for searching the conference summary information corresponding to the user link operation in the follow-up process.

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

The standard format information of the schedule further 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 extension field also records a schedule detail address, a data source or a group chat address.

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

With reference to the first aspect, in yet another possible implementation manner of the first aspect, the displaying, by the terminal device, a meeting list of the at least one group 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 comprises the following steps: a window or a card.

Wherein the unlocking interface comprises: the desktop after the terminal equipment is unlocked, or an application interface of the calendar application after the terminal equipment is unlocked.

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

With reference to the first aspect, in yet another possible implementation manner of the first aspect, the entering, by the terminal device, the target conference in response to the conference linking operation includes: and the terminal equipment enters a target conference link according to the clicking operation of the user on the target conference entering control, wherein the target conference link corresponds to the target conference entering 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.

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

Specifically, the starting, by the terminal device, a three-party application corresponding to the target conference link, and accessing the conference corresponding to the target conference link includes: receiving a conference joining request by a three-party application of the terminal equipment, wherein the conference joining request is triggered by the conference linking operation; and the three-party application of the terminal equipment skips to the conference corresponding to the target conference link according to the conference entering request.

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

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

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 apparatus, where the apparatus is applied to a terminal device, and the apparatus includes: the device comprises an acquisition unit, a processing unit, a display unit, a receiving unit and the like.

The system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring at least one group of meeting schedules, the meeting schedules comprise schedule information of three-party application, and the meeting schedules further comprise meeting links and meeting content information; the processing unit is used for generating 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 content; the display unit is used for displaying a conference list of the at least one group of conference schedule information; the receiving unit is used for receiving the conference link operation of a user on the target conference; the processing unit is further configured to enter the target conference in response to the conference linking 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 correspond to the schedule identifiers one to one; the obtaining unit is further configured to obtain the meeting summary information according to the at least one group of meeting schedules, and generate a meeting list of the at least one group of meeting schedules according to the meeting summary information and the schedule identifiers, where the meeting summary information corresponds to the schedule identifiers one to 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 the conference content. The standard format information of the schedule further 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 comprises the following steps: windows or cards, etc.

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

With reference to the second aspect, in yet another 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 entry control, start a three-party application corresponding to the target conference link, and access a conference corresponding to the target conference link. And the target conference links correspond to the target conference access controls one by one.

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

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

In a third aspect, an embodiment of the present application further provides a terminal device, where the terminal device includes at least one processor and a memory, and in addition, the terminal device further includes: the device comprises a communication module, a display screen, at least one sensor and the like.

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 the at least one processor with computer program instructions and/or data; the at least one processor is configured to execute the computer program instructions to implement the methods in the foregoing first aspect and various implementation manners of the first aspect.

Specifically, the communication module is configured to obtain at least one group of meeting schedules, where the meeting schedules include schedule information of a three-party application, and the meeting schedules further include meeting links and meeting content information; a processor 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 meeting links and at least part of meeting content; the display screen is used for displaying a conference list of the at least one group of conference schedules and receiving conference link operation of a user on a target conference; the processor is further configured to enter the target conference in response to the conference 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 group of meeting schedules, and allocate a schedule identifier to each meeting schedule, where the meeting schedules correspond to the schedule identifiers one to one; 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 to 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 the conference content.

The standard format information of the schedule further 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 extension field further records a schedule detail address, a data source or a group chat address.

With reference to the third aspect, in yet another possible implementation manner of the third aspect, the display screen is further configured to display the meeting 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 comprises the following steps: a window or a card.

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

Further, the processor is further configured to enter a target conference link according to the click operation of the user on a target conference entering control, where the target conference link corresponds to the target conference entering control one to 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 yet another 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 conference joining request, where the conference joining request is triggered by the conference link operation, and control the three-party application of the terminal device to jump to a conference corresponding to the target conference link according to the conference joining request.

Alternatively, 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, which stores instructions such that when the instructions are executed on a computer or a processor, the instructions can be used to execute the method in the foregoing first aspect and various implementation manners of the first aspect.

In addition, the present application also provides a computer program product, which includes computer instructions, and when the instructions are executed by a computer or a processor, the method in the foregoing first aspect and various implementation manners of the first aspect may be implemented.

It should be noted that, 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 first aspect and the various implementation manners of the first aspect, and for specific reference, the description of the beneficial effects in the various implementation manners of the first aspect and the first aspect is not repeated.

Drawings

Fig. 1 is an architecture 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 according to 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 according to an embodiment of the present application;

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

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

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

fig. 6b is a schematic diagram of a target conference control displayed by a "shallow search bit" according to an embodiment of the present application;

FIG. 6c is a schematic diagram of a target conference control displayed in a "global gear position" according to an embodiment of the present application;

fig. 6d is a schematic diagram of a "conference entry" control displayed as "schedule details" according to an embodiment of the present application;

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

fig. 8 is a signaling flowchart of a conference access method according to an embodiment of the present application;

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

Detailed Description

In order to make the technical solutions in the embodiments of the present application better understood by those skilled in the art, the technical solutions in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

Before describing the technical solution of the embodiment of the present application, an application scenario of the embodiment of the present application is first described with reference to the drawings. The technical solution of the embodiment of the present application may be applied to various communication systems, such as Wireless Local Area Network (WLAN), global system for mobile communications (GSM) systems, code division multiple access (CDA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), universal mobile communication system (universal mobile telecommunication system, UMTS), universal microwave access (WiMAX), future radio Network (NR 5, WiMAX) systems, and so on. As shown in fig. 1, any of the above communication systems includes: terminal equipment and network equipment carried by at least one user, and the like.

The terminal device may be a portable device, such as a smart terminal, a mobile phone, a notebook computer, a tablet computer, a Personal Computer (PC), a Personal Digital Assistant (PDA), a foldable terminal, a wearable device with a wireless communication function (e.g., a smart watch or a bracelet), a user equipment (user device) or a User Equipment (UE), a game machine, and an Augmented Reality (AR) \\ Virtual Reality (VR) device, and the like. In addition, an Android (Android) system is installed in the various terminal devices.

Fig. 2 is a schematic diagram of a 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 (USB) interface 130, a radio frequency circuit 140, a mobile communication module 150, a wireless communication module 160, a camera 170, a display screen 180, a SIM card interface 190, a touch sensor 200, a pressure sensor 210, keys 220, and the like.

Among other things, processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural Network Processor (NPU), among others. The different processing units may be independent devices, or may be integrated into one or more processors, for example, a system on a chip (SoC). A memory may also be provided in 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 have just been used or recycled by the processor 110.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface 190 and/or a USB interface 130, and the like.

The memory 120 may be used to store computer-executable program code, which includes instructions. The memory 120 may include a program storage area and a data storage 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 by at least one function, and the like. The storage data area may store data (e.g., audio data, a phonebook) created during use of the terminal device 100, and the like. Furthermore, the memory 120 may include one or more memory units, for example, a volatile memory (volatile memory), such as a Random Access Memory (RAM), and a non-volatile memory (NVM), such as a read-only memory (ROM), a flash memory (flash memory), and the like. The processor 110 executes 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 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 on the terminal device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive electromagnetic waves from the antenna 141, filter, amplify, etc. the received electromagnetic waves, and transmit the electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 141 to radiate the electromagnetic wave. 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 disposed 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 a 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 passes the demodulated low frequency baseband signal to a 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 audio devices (including but not limited to speakers, headphones, etc.) or displays images or video through the display screen 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 modules, independent of the processor 110.

The wireless communication module 160 may include a wireless fidelity (WiFi) module, a Bluetooth (BT) module, a GNSS module, a 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, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 can also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves via the antenna 141 to radiate it.

In the embodiment of the present application, the wireless communication function of the terminal device 100 may include, for example, global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), new radio interface (5G NR), GNSS, WLAN, FM, BT, and/or NFC IR. GNSS may include Global Positioning System (GPS), global navigation satellite system (GLONASS), beidou satellite navigation system (BDS), quasi-zenith satellite system (QZSS), and/or Satellite Based Augmentation System (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 generates an optical image through the lens and is projected onto the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signals into image signals in standard RGB, YUV, RYYB and other formats. 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 that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. The NPU can implement applications such as intelligent recognition of the terminal device 100, for example: image recognition, face recognition, voice recognition, and the like.

The display screen 180 is used to display images, videos, and the like. The display screen 180 includes a display panel. The display panel may be a 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 (active-matrix organic light-emitting diode), a flexible light-emitting diode (FLED), a MiniLED, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the terminal device 100 may include 1 or N display screens 180, N being a positive integer greater than 1.

Touch sensor 200 is 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 called a "touch screen". The touch sensor 200 is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 180. In other embodiments, the touch sensor 200 may be disposed on the surface of the terminal device 100 at a different position than the display screen 180. The pressure sensor 210 is used to measure the pressure value of the user's touch screen. In addition, other sensors may also be included, such as a gyroscope sensor, an acceleration sensor, a temperature sensor, and the like.

The keys 220 include a power-on key, a volume key, and the like. The keys 220 may be mechanical keys. Or may be touch keys. The terminal device 100 may receive a key input, and generate a key signal input related to user setting and function control of the terminal device 100.

It is to be understood that the illustrated structure of the embodiments of the present application does not constitute a specific limitation to the terminal device. In other embodiments of the present application, a terminal device may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components may be used. 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 particularly limited in this embodiment.

Various network devices such as the server, the third-party platform, the data center or the computing unit are development platforms, that is, all users can access the cloud through the client.

The application layer of the terminal equipment comprises a plurality of application APPs. Among the applications APP, at least a calendar application and a three-party application are included, as shown in fig. 3, among the applications 1 to 8, the application 4 is a three-party application APP having a conference video function, such as stapling or flybook.

In addition, optionally, the terminal device further includes a storage application APP, a clock, a gallery, a memo, and other applications APP, 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 merged into one APP. The merged APP can be in data transmission with the three-party application, so that the function of entering the three-party conference by one key is realized.

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 a user to perform query, insert, update, delete operations regarding the contents of a calendar, event, meeting, reminder, etc. Further, the calendar provider can also access other applications, synchronization adapters, content providers, and the like using an Application Programming Interface (API).

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

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

The method provided in this example is explained in detail below.

A 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 method comprises the steps that terminal equipment obtains at least one group of meeting schedules, wherein the meeting schedules comprise schedule information of three-party application, and the meeting schedules further comprise meeting links and meeting 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 for entering a third application. Further, the address of the conference includes a uniform Resource Identifier (Uri) or a uniform Resource Locator (Url).

Optionally, the meeting schedule is schedule standard format information, and the schedule standard format information is based on content in a Request For Comments (RFC) 2445 protocol version and is used to describe related information of the schedule. Further, the schedule standard format information or RFC2445 protocol version includes at least one basic field and an extension field, where the basic field records the conference content information, and the extension field records the conference link (meetingInfoUri).

The RFC is a series of memos issued by The Internet Engineering Task Force (IETF). The memo collects information about the internet, and software files of UNIX and internet communities, which are numbered. The RFC2445 protocol version mainly describes a standard data format of a Calendar (Calendar), and defines relevant fields and rules of the Calendar, so as to realize functions of creating, reminding and the like of the Calendar application in an android system. The embodiment adds an extension field based on the RFC2445 protocol version content.

In addition, the extension field records contents such as a schedule detail address (eventInfoUri), a data source (dataSource), a group chat address, and the like.

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

Optionally, in step 401, the terminal device may periodically obtain meeting schedule information, or send the meeting schedule to the terminal device after the server creates a meeting schedule, where this embodiment does not limit a manner in which the terminal device obtains the meeting schedule.

402: and 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.

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

4021: the terminal equipment receives at least one group of meeting schedules and allocates schedule identification for each meeting schedule, and the meeting schedules correspond to the schedule identification one by one.

The meeting schedule can be represented by schedule (event) tables, each event table can be represented by a schedule identification (event ID), and the meeting schedule event tables and the schedule identification event IDs have unique corresponding relations. As shown in table 1 below, a correspondence between an event table and an event ID, and detailed information of a single schedule (or event). The "event tables" are collectively referred to as "calendarcract.

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

TABLE 1 correspondence between meeting Schedule and Schedule identification

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

Similarly, if there are multiple meeting schedules, a corresponding relationship between the multiple meeting schedules and multiple schedule identifiers is established, and one meeting schedule corresponds to one schedule identifier.

The method further comprises the following steps: 4022: and the terminal equipment acquires the conference summary information according to the at least one group of conference schedules, wherein the conference summary information corresponds to the schedule identification 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 the form of table 2. Referring to table 2, it is a conference summary information table, which may be called a relation information table.

Table 2, summary information table of conference

The conference summary information table includes a conference link and conference content, for example, the conference link includes: eventInfoUri, meetingInfoUri, dataSource, etc., for recording conference/calendar access addresses, and data sources, etc. The conference content comprises: schedule creation time, schedule update time, schedule identification, Id of schedule, etc.

Optionally, the association information table may be added to the RFC2445 protocol version by means of at least one field, for example, added to a directory of the RFC2445 protocol version, and a new theme is added to record the association information table. It should be understood that at least one extension 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 table 1 and the meeting summary information shown in table 2, and binds a schedule identifier (event ID) with the meeting summary information to generate a meeting list of a group of meeting schedules, as shown in table 3.

TABLE 3 meeting List of a set of meeting schedules

In addition, still include: and the terminal equipment stores the meeting list of the at least one group of schedules.

In this embodiment, the terminal device is in a native android system framework, such as

The method comprises the steps that a company issues, and on the basis of an android system frame which is not modified by a third party, a conference list of at least one group of schedules is obtained, wherein the conference list of each group of schedules comprises an incidence relation between schedule identification and a conference link, and convenience is brought to subsequent rapid conference jumping.

Wherein the conference link comprises a conference access address and/or a schedule 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 subject, and other primary reminder content. For example, the meeting time is: 8:00 to 10:00 am, the subject of the conference is "office entertainment seminar".

403: and the terminal equipment displays a conference list of the at least one group of conference 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 comprises the following steps: a window or a card. Wherein the unlocking interface comprises: and the terminal equipment unlocks the desktop or the application interface of the calendar application after unlocking.

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

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

Optionally, if the terminal device is in the unlocked state, the conference list is displayed on an unlocking interface of the terminal device. For example, as shown in fig. 6b, the unlocking interface includes a window and controls of a plurality of applications, such as an application mall, sports health, weather, email, and the like. The window comprises a meeting list, and the meeting list comprises three groups of meeting summary information. The first group of meeting summary information comprises a meeting entering control "Join", and the "Join" control corresponds to a meeting link of the first group of meeting schedules.

Optionally, another implementation manner of displaying the meeting list on the unlocking interface is to display the meeting list in a calendar application of the unlocking interface as shown in fig. 6 c. After the user opens the "calendar" application, the meeting list is displayed on a first application interface of the "calendar" application. The meeting list includes meeting reminder information for three meetings, and the meeting reminder information can be arranged in time sequence. Examples include: meeting prompt information 1, "job conference 1" from 08:30 to 12: 00; meeting reminder information 2, "job conference 2" from 13:00 to 18: 00; meeting prompt information 3, "buy birthday cake for daughter" from 19:00 onward. And each meeting prompt message comprises a meeting entrance control 'Join', and the meeting entrance control 'Join' 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 be displayed. For example, as shown in fig. 6d, the meeting list is displayed on the second application interface of the "calendar" application, and the meeting list includes detailed information of a set of meeting schedules. Such as information including meeting subject, meeting time, meeting link, meeting ID, chairman password, guest password, participants, location, time zone, etc. In the example of fig. 6d, the conference topic is: UXD design review; the meeting time is 10:30 to 12:00 am, the date is 9 months, 10 days and thursday; the conference control corresponding to the conference link is 'join xx video conference'; the conference ID is: xxx xxx xxx; the number of participants is 4, the location is in conference room number 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 meeting list on the terminal device includes, but is not limited to, a window or card manner, and other manners, such as a message bar manner, an information bar manner, and the like, 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.

And the target conference is a conference which a user desires to access. The conference link of the target conference is accessed through a target conference joining control, such as an "access conference" control or a "Join" control, which is displayed in a window or a card of the terminal device. A specific implementation manner is that a user clicks a conference entry control in any one of the conference lists in fig. 6a to 6d, the conference entry control clicked by the user is a target conference entry control, the terminal device receives a click operation of the user on the target conference entry control, and the target conference entry control is one of the at least one conference entry 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 clicking operation of the user on the target conference entering control, wherein the target conference link corresponds to the target conference entering 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 a user clicks an "access conference" control of a window on a lock screen interface, a terminal device obtains a content uniform resource identifier (contentUri) according to an operation of the user, the obtained content uniform resource identifier (contentUri) corresponds to a schedule identifier, in this embodiment, a schedule identifier corresponding to the contentUri is referred to as a target schedule identifier, for example, the target schedule identifier is event ID 1, and due to a correspondence between the established schedule identifier and conference summary information, conference summary information having a unique correspondence with event ID 1 can be found according to event ID 1, and target conference summary information is determined according to a correspondence of table 3, the target conference summary information includes a conference access address (meetingInfoUri), the access address is the target conference link, and directly jumping to the target conference according to the target conference link after finding the target conference link.

As shown in fig. 7, after the user clicks the "access conference" control in the conference list displayed by the terminal device, the target conference link is determined according to the step 405, and the user directly jumps to the conference interface corresponding to the target conference link, thereby implementing the one-click conference operation of the user.

According to the method provided by the embodiment, a conference link function is 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 terminal equipment can obtain the target conference access address according to the conference link operation and directly jumps to the conference interface of the three-party application through the target conference access address, so that one-click 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, the conference access method specifically includes the following steps:

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

Specifically, in the communication process between the terminal device and the cloud server, when the terminal device acquires a conference schedule message created by the server, step 801 is executed. For example, after determining that the user identity of the client is legal, the server sends the basic data and the extension data to the terminal device.

The basic data mainly describes basic information of the schedule, such as time, location, information of participants, number of participants, description, and the like. Optionally, the basic data is related data in RFC2445 protocol. The extension data is an extension field, the extension field is a field added newly based on the protocol of RFC2445, such as a relation protocol field, and the relation protocol field is used for describing a conference address, a data source (dataSource), and the like, or the relation protocol field includes an access address to be joined. Such as eventInfoUri and meetingInfoUri.

The present embodiment does not limit this. One sending mode is that the server packages the basic data and the expansion data into an ics file packet, and sends the ics file packet to the terminal device. 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 identification (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 obtained from the application layer, analyzes the ics file package to obtain the basic data and the extension data, creates a relationship information table according to the basic data and the extension data, and associates the event ID with the relationship information table to obtain a meeting list of at least one group of meeting schedules, as shown in table 3. The specific process 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 the calendar provider and/or the content provider of the previous embodiments. In one implementation, the calendar application sends the parsed basic data and the parsed extension data to the storage application. After the storage application receives the data, a relationship information table and a schedule basic data table (event table) are created. The relationship information table includes development data such as eventInfoUri and meetingInfoUri. The aforementioned basic data are described in 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 acquires a user operation of clicking a 'calendar' application on a display interface by a user, the user operation indicating that the user desires to view a schedule that has been created.

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

One possible implementation is that when the user clicks on the "calendar" application, the calendar application obtains the ContentUri corresponding to the user operation. Among them, ContentUri can be understood as a tool class, which is mainly used for processing Uri objects using "content" constraints, and the syntax format of ContentUri objects is: content:// authority// path/id, where authority is a string that identifies the contentprovider, all Content Uri starts with this string, which has uniqueness and is generally 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 the unique identification, i.e., id number, of each record in the database.

And the calendar application searches a target meeting schedule list corresponding to the ContentUri according to the ContentUri, wherein the list can be called a target event list, the target event list comprises a target schedule identifier (event ID), and then the target event ID corresponding to the ContentUri is determined. And then using the target event ID to search for the target conference link corresponding to the event ID in the correspondence stored in the foregoing step 802.

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

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

805: and the terminal equipment receives the operation of clicking the target conference entering control on the terminal equipment by the user.

806: and the terminal equipment enters a target conference link according to the clicking operation of a user on a target conference entering control, the target conference link corresponds to the target conference entering control one by one, and the three-party application corresponding to the target conference link is started.

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

Specifically, after receiving an operation of clicking a target conference entering control by a user, the calendar application sends a conference entering request to the three-party application, and after receiving the conference entering request, the three-party application directly skips to a conference corresponding to a target conference link according to the conference entering request, enters a conference by one touch, and then the user enters a target conference interface. For example, as shown in fig. 7, after the user clicks a target conference entry control of "access to a conference", the three-party APP is directly started from the current notification bit interface, and jumps to a conference interface of the three-party APP, for example, jumps to a display interface of a nailed conference, so as to achieve an effect of one-click conference entry.

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

The embodiment provides a conference access device, which can be a terminal device, and the structure of the device can be seen from the terminal device shown in fig. 2, which 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.

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

The mobile communication module 150, the wireless communication module 160, and at least one of 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 meeting schedules, where the meeting schedules include schedule information of a three-party application, and the meeting schedules further include meeting links and meeting content information. The processor 110 is 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 meeting links and at least part of meeting content.

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

Wherein the meeting summary information further comprises: meeting time and meeting subject.

Optionally, in a possible implementation manner of this embodiment, the processor 110 is further configured to receive the at least one group of meeting schedules, and allocate a schedule identifier to each meeting schedule, where the meeting schedules correspond to the schedule identifiers one to one; 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 to 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 the conference content.

The standard format information of the schedule further 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 extension 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 meeting 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 comprises the following steps: a window or a card. Wherein the unlocking interface comprises: the desktop after the terminal equipment is unlocked, or an application interface of the calendar application after the terminal equipment is unlocked.

Optionally, the display screen 180 is further configured to display at least one conference entry control in the conference list of the at least one group of conference schedules, where each conference entry control corresponds to one conference link; and receiving the clicking operation of the user on a target conference control, wherein the target conference control is one of the at least one conference 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 user on a target conference entry control, where the target conference link corresponds to the target conference entry control one to one; 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 a three-party application of the terminal device to receive a conference joining request, where the conference joining request is triggered by the conference link operation, and control the three-party application of the terminal device to jump to a conference corresponding to the target conference link according to the conference joining 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 can also be implemented by software, for example, as shown in fig. 9, which is a schematic structural diagram of a conference access apparatus, the apparatus includes: the acquiring unit 901, the processing unit 902, the displaying unit 903, and the receiving unit 904 may further include other units and modules, such as a storage unit, a sending unit, and the like, which is not limited in this embodiment.

The acquiring unit 901 is configured to acquire at least one group of meeting schedules, where the meeting schedules include schedule information of a three-party application, and the meeting schedules further include meeting links and meeting content information; a processing unit 902, configured to generate a meeting list according to the at least one set of meeting schedule information, 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, configured to display a meeting list of the at least one set of meeting schedule information; a receiving unit 904, configured to receive a conference link operation of a user on a target conference; the processing unit 902 is further configured to enter the target conference in response to the conference linking operation.

In addition, the acquiring unit 901, the processing unit 902, the display unit 903 and the receiving unit 904 are further configured to implement the conference access method shown in fig. 4, fig. 5 and fig. 8.

An embodiment of the present application further provides a wireless communication system, including at least one terminal device and a network device, where the terminal device is the apparatus shown in fig. 9 or fig. 2, and may 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.

The system provided by the embodiment adds a conference linking function in the calendar application, displays the conference linking function to the user through the conference list, and when the terminal device receives the conference linking operation of the user, can obtain the target conference access address according to the conference linking operation, and directly jumps to the conference interface of the three-party application through the target conference access address to realize one-touch conference. The method simplifies the user operation and the waiting time of the operation, and improves the user experience.

Furthermore, embodiments of the present application also provide a computer program product, which includes one or more computer program instructions. When loaded and executed by a computer, cause the method flows or functions described in the various embodiments above, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device.

Wherein the computer program product may be stored in the memory 120. In addition, the memory 120 is also used to store at least one group of meeting schedules, a meeting list of at least one group of meeting schedules, and other information in the foregoing embodiments.

In addition, in the description of the embodiments of the present application, "at least one" means one or more than one unless otherwise specified. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

The above-described embodiments of the present application do not limit the scope of the present application.

Claims

1. A conference access method is applied to a terminal device, and the method comprises the following steps:

the terminal equipment acquires at least one group of meeting schedules, wherein the meeting schedules comprise schedule information of three-party application, and the meeting schedules also comprise meeting links and meeting content information;

the terminal equipment generates a meeting list according to the at least one group of meeting schedules, the meeting list comprises the at least one group of meeting summary information, and the meeting summary information comprises meeting links and at least part of meeting content;

the terminal equipment displays a conference list of the at least one group of conference schedules;

the terminal equipment receives a conference link operation of a user on a target conference;

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

2. The method of claim 1, wherein the terminal device generates a meeting list according to the at least one set of meeting schedules, comprising:

the terminal equipment receives the at least one group of meeting schedules and allocates schedule identification to each meeting schedule, and the meeting schedules correspond to the schedule identification 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 identification one by one;

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.

3. The method of claim 2, wherein the obtaining, by the terminal device, the meeting summary information according to the at least one set of meeting schedules comprises:

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

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

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

6. The method of any of claims 1-5, wherein the terminal device displays a meeting list of the at least one set of meeting schedules, comprising:

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 comprises the following steps: a window or a card.

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

the desktop after the terminal equipment is unlocked, or an application interface of the calendar application after the terminal equipment is unlocked.

8. The method of any of claims 1-7, wherein the displayed meeting list of the at least one set of meeting schedules further comprises: at least one conference joining control, wherein each conference joining control corresponds to one conference link;

the method for receiving the conference link operation of the target conference by the user through the terminal equipment comprises the following steps:

and the terminal equipment receives the click operation of the user on a target conference entering control, wherein the target conference entering control is one of the at least one conference entering control.

9. The method of claim 8, wherein the terminal device enters the target conference in response to the conference linking operation, comprising:

the terminal equipment enters a target conference link according to the clicking operation of the user on a target conference entering control, and the target conference link corresponds to the target conference entering 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.

10. The method of claim 9, wherein the terminal device starts a three-party application corresponding to the target conference link, and accesses the conference corresponding to the target conference link, including:

receiving a conference joining request by a three-party application of the terminal equipment, wherein the conference joining request is triggered by the conference linking operation;

and the three-party application of the terminal equipment skips to the conference corresponding to the target conference link according to the conference entering request.

11. The method of any of claims 8-10, wherein the at least one meeting control is displayed in the meeting list by any of:

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

12. The method of any of claims 1-11, wherein the meeting summary information further comprises: meeting time and meeting subject.

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

one or more computer programs stored in the memory;

the one or more computer programs, when executed by the at least one processor, cause the terminal device to implement the method of any one of claims 1 to 12.

14. A computer-readable storage medium having computer program instructions stored therein,

the computer program instructions, when executed, implement the method of any of claims 1 to 12.