Meeting recording method, related device and system

Abstract

Disclosed in the embodiments of the present application are a meeting recording method, a related device and a system. The method comprises: establishing an association relationship between a meeting record 1 generated on an application 1 and a schedule 1 on an application 2; and then, on the basis of the association relationship, providing to a user a viewing entry of the meeting record 1 on the application 2, and / or providing to the user a viewing entry of the schedule 1 on the application 1. By means of the method provided in the embodiments of the present application, a meeting record on an application 1 can be associated with a schedule on an application 2, such that meeting records from different channels are integrated by means of schedules, and thus a user can intuitively view and manage the meeting records from different channels in the schedules, thereby improving the user experience.

Description

Meeting minutes methods, related equipment and systems

[0001] This application claims priority to Chinese Patent Application No. 202510476318.5, filed with the State Intellectual Property Office of China on April 15, 2025, entitled "Meeting Minutes Method, Related Equipment and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of electronic technology, and in particular to meeting recording methods, related equipment and systems. Background Technology

[0003] Meeting minutes are a document or collection of information that records and organizes the proceedings of a meeting. They are an important tool for meeting management, ensuring not only the accurate recording and communication of meeting content but also supporting decision-making, task execution, and subsequent evaluation. Users can access these minutes through meeting applications (such as Tencent Meeting). TM DingTalk TM WeMeeting TM Meeting minutes can be recorded via audio, screen recording, or video recording. Currently, users cannot easily view and manage meeting minutes from different channels, causing inconvenience and a poor user experience. For example, when a user has participated in meetings through multiple meeting applications, they need to search for the corresponding meeting minutes in each application separately. Similarly, when a user has participated in an offline meeting, it is difficult to access the meeting minutes on their electronic device. Summary of the Invention

[0004] This application provides a meeting recording method, related equipment, and system. The method includes: establishing an association between meeting minutes 1 generated on application 1 and schedule 1 on application 2; then, based on this association, providing a viewing entry point for meeting minutes 1 to the user on application 2, and / or providing a viewing entry point for schedule 1 to the user on application 1. Through the method provided by this application embodiment, meeting minutes on application 1 and schedules on application 2 can be linked, thereby enabling the integration of meeting minutes from different channels through the schedule, facilitating users to intuitively view and manage meeting minutes from different channels within the schedule, and improving the user experience.

[0005] In a first aspect, this application provides a meeting recording method, the method comprising: obtaining first attribute information of a first meeting record from a first application, the first meeting record being used to record first content of a first meeting, the first attribute information being used to indicate the time or identifier of the first meeting; establishing an association between the first meeting record and a first schedule on a second application based on the first attribute information, the second application being used to manage the schedule; and providing a viewing entry point for the first meeting record to a user on the second application based on the association, and / or providing a viewing entry point for the first schedule to a user on the first application.

[0006] The first application, also referred to as application 1, is an application used to generate meeting minutes by recording the content of a meeting (e.g., a meeting application, or an application with text recording, speech recognition, recording, or video recording functions). This first application can be an application built into the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this. In some embodiments, the first application may include an Artificial Intelligence (AI) model. For example, the first application can be a voice assistant, a software application that enables human-computer interaction based on AI technology. The voice assistant can recognize the user's voice commands, understand their intentions, and use technologies such as natural language processing and speech synthesis to provide users with various services and assistance, such as information query, schedule management, reminder settings, and device control. The second application, also referred to as application 2, is an application with schedule management functions. The second application can be an application built into the operating system (e.g., a calendar) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this.

[0007] The first meeting record, also referred to as meeting record 1, may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recordings, meeting audio files, meeting video files, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this. The first schedule, also referred to as schedule 1, may be a task that needs to be completed within a preset time period (such as 1 hour). Its name may also be a reminder, event, task, important day, important thing, etc. This application embodiment does not limit its name.

[0008] The first attribute information can be used to indicate the time or identifier of the first meeting, so that the second application can subsequently establish a relationship between the first meeting record and the first schedule on the second application based on the first attribute information. The first meeting can be any meeting that the user participates in. The first content can include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recordings, meeting audio files, meeting video files, etc.), and can also include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this.

[0009] In the embodiments of this application, the executing entity can be a second application, an electronic device with the second application installed, or the operating system of the aforementioned electronic device. The embodiments of this application do not limit this.

[0010] By using the method provided in the first aspect, the second application can link meeting records on the first application with the schedule on the second application, thereby integrating meeting records from different channels through the schedule. This allows the corresponding meeting records to be updated in the schedule after the meeting ends, making it easier for users to view and manage meeting records from different channels intuitively in the schedule, thus improving the user experience.

[0011] In conjunction with the first aspect, in some embodiments, providing a user with an entry point to view the first meeting minutes on the second application specifically includes: obtaining the first content of the first meeting minutes on the first application; and displaying the first content to the user on the second application.

[0012] The first content may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recording files, meeting audio files, meeting video files, etc.), and may also include the integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this.

[0013] In conjunction with the first aspect, in some embodiments, providing a user with an entry point to view the first meeting minutes on the second application specifically includes: displaying a first link on the second application to the user, the first link being used to open an interface in the first application to view the first meeting minutes.

[0014] The first link is an application jump entry (e.g., an application jump entry from a second application to a first application), and its name can also be a control, etc. The embodiments of this application do not limit its name.

[0015] Optionally, when the entry point for viewing the first meeting record in the second application is a first link, in response to the operation of opening the first schedule in the second application, the first link can be displayed in the first schedule in the second application. This first link can be used to open the interface (e.g., user interface 720) in the first application to view the first meeting record. In response to the operation on the first link, the display can be switched from displaying the first schedule in the second application to displaying the first meeting record in the first application. For example, as shown in Figures 6A-6C, in response to the operation of opening the first schedule in the calendar (e.g., clicking on schedule 431 in user interface 430), the first link can be displayed in the first schedule in the calendar. This first link can be used to open the interface (e.g., user interface 720) in the voice assistant to view the first meeting record. In response to the operation on the first link, the display can be switched from displaying the first schedule in the calendar to displaying the first meeting record in the voice assistant.

[0016] In conjunction with the first aspect, in some embodiments, providing a user with an entry point to view the first schedule on the first application specifically includes: obtaining the content information of the first schedule on the second application; and displaying the content information of the first schedule to the user on the first application.

[0017] The information in the first agenda may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants.

[0018] In conjunction with the first aspect, in some embodiments, providing a user with an entry point to view the first schedule on the first application specifically includes: displaying a second link to the user on the first application, the second link being used to open an interface in the second application to view the first schedule.

[0019] The second link is an application jump entry (e.g., an application jump entry from the first application to the second application), and its name can also be a control, etc. The embodiments of this application do not limit its name.

[0020] In conjunction with the first aspect, in some embodiments, the first schedule is a schedule created on a second application based on the first attribute information.

[0021] Among them, a newly created schedule refers to a schedule created on the second application at a time later than the time the first meeting record was generated on the first application.

[0022] In conjunction with the first aspect, in some embodiments, the first schedule is selected from existing schedules created on the second application based on first attribute information.

[0023] Here, "created" means that the creation time of the schedule is earlier than the generation time of the first meeting record. Among the created schedules, the schedule time of the first schedule is closest to the generation time of the first meeting record, or the time difference between the schedule time of the first schedule and the generation time of the first meeting record is less than a first threshold (e.g., 0.5 hours).

[0024] In some embodiments, the first schedule associated with the first meeting record may be a schedule actively selected by the user from a list of created schedules on a second application. In other embodiments, the first schedule associated with the first meeting record may be a schedule automatically matched by the second application from a list of created schedules.

[0025] In conjunction with the first aspect, in some embodiments, the first meeting record includes meeting records generated from online audio captured via a network, and / or, the first meeting record includes meeting records generated from audio captured via a microphone.

[0026] Currently, meeting applications can only record online meetings, not offline meetings. Therefore, users often cannot access the meeting minutes of offline meetings on their electronic devices. However, the meeting recording method provided in this application can generate offline meeting minutes using a microphone and save them to a schedule management application. This allows for the integration of meeting minutes from different formats (online and offline), making it easier for users to view and manage meeting minutes from different channels intuitively within their schedules, thus improving the user experience.

[0027] Specifically, if the meeting is an offline meeting, users can choose a microphone as the audio source, and the meeting record can include the meeting record generated from the sound captured by the microphone. If the meeting is an online meeting, users can choose internal system audio as the audio source, and the meeting record can include the meeting record generated from online audio captured via the network. If the meeting is a combination of online and offline, users can choose both a microphone and internal system audio as audio sources, and the meeting record can include the meeting record generated from the sound captured by the microphone and the meeting record generated from online audio captured via the network. A meeting combining online and offline elements could be, for example, an online meeting in which multiple offline users participate.

[0028] In conjunction with the first aspect, in some embodiments, the first meeting record contains the text of the speeches made by each speaker in the meeting.

[0029] If the first application includes an AI model, the first meeting record may contain the text of the speeches delivered by each speaker in the meeting. For example, the first application may be a voice assistant, which can use the AI ​​model to convert the spoken content of each speaker in the meeting into text content.

[0030] Secondly, this application provides a meeting recording method, which includes: obtaining schedule information from a second application, the schedule information including content information of a first schedule managed by the second application; establishing an association between a first meeting record and a first schedule on the first application based on the schedule information, the first application being used to generate the first meeting record by recording the first content of the first meeting; and providing a viewing entry point for the first meeting record to a user on the second application based on the association, and / or providing a viewing entry point for the first schedule to a user on the first application.

[0031] The first application, also referred to as application 1, is an application used to generate meeting minutes by recording the content of a meeting (e.g., a meeting application, or an application with text recording, speech recognition, recording, or video recording functions). This first application can be an application built into the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this. In some embodiments, the first application may include an Artificial Intelligence (AI) model. For example, the first application can be a voice assistant, a software application that enables human-computer interaction based on AI technology. The voice assistant can recognize the user's voice commands, understand their intentions, and use technologies such as natural language processing and speech synthesis to provide users with various services and assistance, such as information query, schedule management, reminder settings, and device control. The second application, also referred to as application 2, is an application with schedule management functions. The second application can be an application built into the operating system (e.g., a calendar) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this.

[0032] The first meeting record, also referred to as meeting record 1, may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recordings, meeting audio files, meeting video files, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this. The first schedule, also referred to as schedule 1, may be a task that needs to be completed within a preset time period (such as 1 hour). Its name may also be a reminder, event, task, important day, important thing, etc. This application embodiment does not limit its name.

[0033] The first meeting can be any meeting in which the user participates. The first content can include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recordings, meeting audio files, meeting video files, etc.), and can also include integrated meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this.

[0034] The schedule information can be the content information of one or more schedules managed by the second application, which may include, but is not limited to, one or more of the following: event name, schedule time. The schedule information may also include the content information of a first schedule managed by the second application, which may include, but is not limited to, one or more of the following: meeting name, meeting time, participants.

[0035] In the embodiments of this application, the executing entity can be a first application, an electronic device with the first application installed, or the operating system of the aforementioned electronic device. The embodiments of this application do not limit this.

[0036] By using the method provided in the second aspect, the first application can associate meeting records on the first application with schedules created on the second application, thereby integrating meeting records from different channels through schedules. This allows the corresponding meeting records to be updated in the schedule after the meeting ends, making it easier for users to view and manage meeting records from different channels intuitively in the schedule, thus improving the user experience.

[0037] In conjunction with the second aspect, in some embodiments, establishing an association between a first meeting record and a first schedule on a first application based on schedule information specifically includes: providing a schedule to be selected to a user on the first application based on schedule information, the schedule to be selected including the first schedule; and establishing an association between the first meeting record and the first schedule on the first application in response to the user's selection of the first schedule.

[0038] The schedule to be selected can be one or more schedules managed by the second application. It is understood that the schedules to be selected are schedules already created on the second application.

[0039] For example, as shown in Figure 2D, in response to a user's action of selecting a first event from an existing schedule (e.g., Meeting 1, Meeting 2, Meeting 3), the first application can establish an association between a first meeting record on the first application and a first event on the second application.

[0040] In other embodiments, the first application can select a first schedule from the existing schedules on the second application based on the first meeting record, and establish an association between the first meeting record on the first application and the first schedule on the second application. For example, among the existing schedules, the schedule time of the first schedule is closest to the generation time of the first meeting record, or the time difference between the schedule time of the first schedule and the generation time of the first meeting record is less than a first threshold (e.g., 0.5 hours). It should be noted that "existing schedule" refers to a schedule whose creation time is earlier than the generation time of the first meeting record.

[0041] In conjunction with the second aspect, in some embodiments, providing a user with an entry point to view the first meeting minutes on the second application specifically includes: obtaining the first content of the first meeting minutes on the first application; and displaying the first content to the user on the second application.

[0042] The first content may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recording files, meeting audio files, meeting video files, etc.), and may also include the integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this.

[0043] In conjunction with the second aspect, in some embodiments, providing a user with an entry point to view the first meeting minutes on the second application specifically includes: displaying a first link on the second application to the user, the first link being used to open an interface in the first application to view the first meeting minutes.

[0044] The first link is an application jump entry (e.g., an application jump entry from a second application to a first application), and its name can also be a control, etc. The embodiments of this application do not limit its name.

[0045] Optionally, when the entry point for viewing the first meeting record in the second application is a first link, in response to the operation of opening the first schedule in the second application, the first link can be displayed in the first schedule in the second application. This first link can be used to open the interface (e.g., user interface 720) in the first application to view the first meeting record. In response to the operation on the first link, the display can be switched from displaying the first schedule in the second application to displaying the first meeting record in the first application. For example, as shown in Figures 6A-6C, in response to the operation of opening the first schedule in the calendar (e.g., clicking on schedule 431 in user interface 430), the first link can be displayed in the first schedule in the calendar. This first link can be used to open the interface (e.g., user interface 720) in the voice assistant to view the first meeting record. In response to the operation on the first link, the display can be switched from displaying the first schedule in the calendar to displaying the first meeting record in the voice assistant.

[0046] In conjunction with the second aspect, in some embodiments, providing a user with an entry point to view the first schedule on the first application specifically includes: obtaining the content information of the first schedule on the second application; and displaying the content information of the first schedule to the user on the first application.

[0047] The information in the first agenda may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants.

[0048] In conjunction with the second aspect, in some embodiments, providing a user with an entry point to view the first schedule on the first application specifically includes: displaying a second link on the first application to the user, the second link being used to open an interface in the second application to view the first schedule.

[0049] The second link is an application jump entry (e.g., an application jump entry from the first application to the second application), and its name can also be a control, etc. The embodiments of this application do not limit its name.

[0050] In conjunction with the second aspect, in some embodiments, the first meeting record includes meeting records generated from online audio captured via a network, and / or the first meeting record includes meeting records generated from audio captured via a microphone.

[0051] Currently, meeting applications can only record online meetings, not offline meetings. Therefore, users often cannot access the meeting minutes of offline meetings on their electronic devices. However, the meeting recording method provided in this application can generate offline meeting minutes using a microphone and save them to a schedule management application. This allows for the integration of meeting minutes from different formats (online and offline), making it easier for users to view and manage meeting minutes from different channels intuitively within their schedules, thus improving the user experience.

[0052] Specifically, if the meeting is an offline meeting, users can choose a microphone as the audio source, and the meeting record can include the meeting record generated from the sound captured by the microphone. If the meeting is an online meeting, users can choose internal system audio as the audio source, and the meeting record can include the meeting record generated from online audio captured via the network. If the meeting is a combination of online and offline, users can choose both a microphone and internal system audio as audio sources, and the meeting record can include the meeting record generated from the sound captured by the microphone and the meeting record generated from online audio captured via the network. A meeting combining online and offline elements could be, for example, an online meeting in which multiple offline users participate.

[0053] In conjunction with the second aspect, in some embodiments, the first meeting record contains the text of the speeches made by each speaker in the meeting.

[0054] If the first application includes an AI model, the first meeting record may contain the text of the speeches delivered by each speaker in the meeting. For example, the first application may be a voice assistant, which can use the AI ​​model to convert the spoken content of each speaker in the meeting into text content.

[0055] Thirdly, this application provides a meeting recording method, which includes: after a first application generates a first meeting record by recording the first content of a first meeting, establishing an association between the first meeting record and a first schedule on a second application, wherein the first schedule is a schedule created on the second application based on the first meeting record; and according to the association, providing a viewing entry point for the first meeting record to a user on the second application, and / or providing a viewing entry point for the first schedule to a user on the first application.

[0056] The first application, also referred to as application 1, is an application used to generate meeting minutes by recording the content of a meeting (e.g., a meeting application, or an application with text recording, speech recognition, recording, or video recording functions). This first application can be an application built into the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this. In some embodiments, the first application may include an Artificial Intelligence (AI) model. For example, the first application can be a voice assistant, a software application that enables human-computer interaction based on AI technology. The voice assistant can recognize the user's voice commands, understand their intentions, and use technologies such as natural language processing and speech synthesis to provide users with various services and assistance, such as information query, schedule management, reminder settings, and device control. The second application, also referred to as application 2, is an application with schedule management functions. The second application can be an application built into the operating system (e.g., a calendar) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this.

[0057] The first meeting record, also referred to as meeting record 1, may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recordings, meeting audio files, meeting video files, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this. The first schedule, also referred to as schedule 1, may be a task that needs to be completed within a preset time period (such as 1 hour). Its name may also be a reminder, event, task, important day, important thing, etc. This application embodiment does not limit its name.

[0058] The first meeting can be any meeting in which the user participates. The first content can include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recordings, meeting audio files, meeting video files, etc.), and can also include integrated meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this.

[0059] In the embodiments of this application, the executing entity can be a first application, an electronic device with the first application installed, or the operating system of the aforementioned electronic device. The embodiments of this application do not limit this.

[0060] By using the method provided by the third party, the first application can link meeting records on the first application with newly created schedules on the second application, thereby integrating meeting records from different channels through the schedule. This allows the corresponding meeting records to be updated in the schedule after the meeting ends, making it easier for users to view and manage meeting records from different channels intuitively in the schedule, thus improving the user experience.

[0061] In conjunction with the third aspect, in some embodiments, establishing an association between a first meeting record and a first schedule on a second application specifically includes: in response to a first operation by a user on the first application, establishing an association between the first meeting record and the first schedule on the second application, wherein the first operation is further used to trigger the creation of a new first schedule on the second application.

[0062] The first schedule can be a schedule created on the second application based on the first meeting record. The newly created schedule refers to a schedule created on the second application at a time later than the time the first meeting record was generated on the first application.

[0063] In other embodiments, the first application may create a new first schedule on the second application based on the first meeting record, and establish an association between the first meeting record on the first application and the first schedule on the second application. For example, the schedule time of the newly created first schedule is closest to the generation time of the first meeting record, or the time difference between the schedule time of the newly created first schedule and the generation time of the first meeting record is less than a first threshold (e.g., 0.5 hours).

[0064] In conjunction with the third aspect, in some embodiments, providing a user with an entry point to view the first meeting minutes on the second application specifically includes: obtaining the first content of the first meeting minutes on the first application; and displaying the first content to the user on the second application.

[0065] The first content may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recording files, meeting audio files, meeting video files, etc.), and may also include the integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the first application. This application embodiment does not limit this.

[0066] In conjunction with the third aspect, in some embodiments, providing a user with an entry point to view the first meeting minutes on the second application specifically includes: displaying a first link to the user on the second application, the first link being used to open an interface in the first application to view the first meeting minutes.

[0067] The first link is an application jump entry (e.g., an application jump entry from a second application to a first application), and its name can also be a control, etc. The embodiments of this application do not limit its name.

[0068] Optionally, when the entry point for viewing the first meeting record in the second application is a first link, in response to the operation of opening the first schedule in the second application, the first link can be displayed in the first schedule in the second application. This first link can be used to open the interface (e.g., user interface 720) in the first application to view the first meeting record. In response to the operation on the first link, the display can be switched from displaying the first schedule in the second application to displaying the first meeting record in the first application. For example, as shown in Figures 6A-6C, in response to the operation of opening the first schedule in the calendar (e.g., clicking on schedule 431 in user interface 430), the first link can be displayed in the first schedule in the calendar. This first link can be used to open the interface (e.g., user interface 720) in the voice assistant to view the first meeting record. In response to the operation on the first link, the display can be switched from displaying the first schedule in the calendar to displaying the first meeting record in the voice assistant.

[0069] In conjunction with the third aspect, in some embodiments, providing a user with an entry point to view the first schedule on the first application specifically includes: obtaining the content information of the first schedule on the second application; and displaying the content information of the first schedule to the user on the first application.

[0070] The information in the first agenda may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants.

[0071] In conjunction with the third aspect, in some embodiments, providing a user with an entry point to view the first schedule on the first application specifically includes: displaying a second link to the user on the first application, the second link being used to open an interface in the second application to view the first schedule.

[0072] The second link is an application jump entry (e.g., an application jump entry from the first application to the second application), and its name can also be a control, etc. The embodiments of this application do not limit its name.

[0073] In conjunction with the third aspect, in some embodiments, the first meeting record includes meeting records generated from online audio captured via a network, and / or the first meeting record includes meeting records generated from audio captured via a microphone.

[0074] Currently, meeting applications can only record online meetings, not offline meetings. Therefore, users often cannot access the meeting minutes of offline meetings on their electronic devices. However, the meeting recording method provided in this application can generate offline meeting minutes using a microphone and save them to a schedule management application. This allows for the integration of meeting minutes from different formats (online and offline), making it easier for users to view and manage meeting minutes from different channels intuitively within their schedules, thus improving the user experience.

[0075] Specifically, if the meeting is an offline meeting, users can choose a microphone as the audio source, and the meeting record can include the meeting record generated from the sound captured by the microphone. If the meeting is an online meeting, users can choose internal system audio as the audio source, and the meeting record can include the meeting record generated from online audio captured via the network. If the meeting is a combination of online and offline, users can choose both a microphone and internal system audio as audio sources, and the meeting record can include the meeting record generated from the sound captured by the microphone and the meeting record generated from online audio captured via the network. A meeting combining online and offline elements could be, for example, an online meeting in which multiple offline users participate.

[0076] In conjunction with the third aspect, in some embodiments, the first meeting record contains the text of the speeches made by each speaker in the meeting.

[0077] If the first application includes an AI model, the first meeting record may contain the text of the speeches delivered by each speaker in the meeting. For example, the first application may be a voice assistant, which can use the AI ​​model to convert the spoken content of each speaker in the meeting into text content.

[0078] Fourthly, this application provides a meeting recording method applied to a first electronic device, the first electronic device having a first application installed, the first application being logged in with a first account, the method comprising: receiving an association instruction message, the association instruction message being used to instruct a second electronic device to establish an association between a first schedule and a first meeting record when logging in with the first account; saving the association on the first application; and providing a viewing entry point for the first meeting record to the user on the first application based on the association.

[0079] The first electronic device and the second electronic device can be the electronic device 100 shown in Figure 12. The first electronic device can be the device being synchronized, and the second electronic device can be the device synchronizing. The first account can be the account used by the first electronic device and the second electronic device to log in to the system.

[0080] The first application, also known as application 2, is a built-in application (such as a calendar) of an operating system that has a schedule management function.

[0081] The first meeting record, also known as meeting record 2, can include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video files, etc.), or it can include integrated meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using an AI model. This application embodiment does not limit this. It should be noted that the first meeting record is recorded by the second electronic device while logged into the first account. The first schedule, also known as schedule 2, can be a task that needs to be completed within a preset time period (e.g., within 1 hour). Its name can also be a reminder, event, task, important day, important thing, etc. This application embodiment does not limit its naming.

[0082] Currently, users cannot intuitively view and manage meeting records from different channels. For example, when a user participates in multiple meetings using multiple electronic devices, they need to search for the corresponding meeting records on each device, which is inconvenient and results in a poor user experience.

[0083] By using the method provided in the fourth aspect, based on the association between meeting minutes and schedules, and assuming that the application with schedule management function is a built-in application of the operating system (such as a calendar), the first electronic device can synchronize the association between meeting minutes and schedules across different electronic devices logged into the same account. This allows users to quickly view meeting minutes associated with schedules on all their electronic devices, eliminating the need for users to search for the corresponding meeting minutes on each device when participating in multiple meetings using multiple electronic devices. This makes it convenient for users to manage all the meetings they have attended without worrying about missing any.

[0084] In conjunction with the fourth aspect, in some embodiments, the first electronic device is also equipped with a second application. After receiving the association instruction message, the method further includes: saving the association relationship on the second application; and providing the user with an entry point to view the first schedule on the second application based on the association relationship.

[0085] The second application, also referred to as application 1, is an application used to save meeting minutes (e.g., a meeting application, or an application with text recording, speech recognition, recording, or video recording functions). This second application can be a built-in application of the operating system (e.g., a voice assistant, a memo app), or a third-party application (i.e., an application not included in the operating system's core functionality); this embodiment of the application does not impose any limitations on this.

[0086] Fifthly, this application provides a meeting recording method applied to a second electronic device. The method includes: establishing an association between a first schedule on a first application and a first meeting record on a second application, wherein the first application is logged in with a first account; and sending an association instruction message to the first electronic device, wherein the association instruction message is used to instruct the second electronic device to establish an association between the first schedule and the first meeting record when logged in with the first account.

[0087] In a sixth aspect, this application provides an electronic device, which includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program, and when the processor executes the computer program, the electronic device performs the method of any one of the first to fifth aspects described above.

[0088] In a seventh aspect, this application provides a communication system, comprising: a first electronic device and a second electronic device; wherein: the second electronic device is used to establish an association between a first schedule on a first application and a first meeting record on the second application, the first application being logged in with a first account; sending an association instruction message to the first electronic device, the association instruction message being used to instruct the second electronic device to establish an association between the first schedule and the first meeting record when logging in with the first account; the first electronic device is also used to send an association instruction message to the first electronic device, the association instruction message being used to instruct the second electronic device to establish an association between the first schedule and the first meeting record when logging in with the first account; the first electronic device has a first application installed, the first application being logged in with the first account; the first electronic device is used to receive the association instruction message, the association instruction message being used to instruct the second electronic device to establish an association between the first schedule and the first meeting record when logging in with the first account; the first electronic device is also used to save the association on the first application; the first electronic device is also used to provide a viewing entry for the first meeting record to the user on the first application based on the association.

[0089] Eighthly, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the method described in any one of the first to seventh aspects.

[0090] Ninthly, this application provides a computer program product that, when executed by a processor, implements the method described in any one of the first to seventh aspects.

[0091] In a tenth aspect, this application provides a chip including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, causing the chip to perform the method described in any one of the first to seventh aspects.

[0092] The solutions provided in aspects five through ten above are used to implement or cooperate with the methods provided in aspects one through four above, and therefore can achieve the same or corresponding beneficial effects as the methods in aspects one through four, which will not be elaborated here. Attached Figure Description

[0093] Figure 1A is a flowchart illustrating a meeting recording method for establishing a relationship between meeting minutes and schedules on application 2, as provided in an embodiment of this application.

[0094] Figure 1B is a flowchart illustrating a meeting recording method for establishing a relationship between meeting minutes and schedules on application 1, as provided in an embodiment of this application.

[0095] Figure 1C is another flowchart illustrating a meeting recording method for establishing a relationship between meeting minutes and schedules on application 1, as provided in an embodiment of this application.

[0096] Figures 2A-2F are a set of interface diagrams provided in the embodiments of this application;

[0097] Figures 3A-3C are another set of interface schematic diagrams provided in the embodiments of this application;

[0098] Figures 4A-4E are another set of interface diagrams provided in the embodiments of this application;

[0099] Figures 5A and 5B are another set of interface diagrams provided in the embodiments of this application;

[0100] Figures 6A-6C are another set of interface schematic diagrams provided in the embodiments of this application;

[0101] Figures 7A-7E are another set of interface diagrams provided in the embodiments of this application;

[0102] Figure 8 is a flowchart illustrating a meeting recording synchronization method provided in an embodiment of this application;

[0103] Figure 9 is a flowchart illustrating a meeting record sharing method provided in an embodiment of this application;

[0104] Figure 10 is a schematic diagram of a communication system 10 provided in an embodiment of this application;

[0105] Figure 11 is a schematic diagram of a communication system 20 provided in an embodiment of this application;

[0106] Figure 12 is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application. Detailed Implementation

[0107] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0108] Meeting minutes are a document or collection of information that records and organizes the proceedings of a meeting. They are an important tool for meeting management, ensuring not only the accurate recording and communication of meeting content but also supporting decision-making, task execution, and subsequent evaluation. Users can access these minutes through meeting applications (such as Tencent Meeting). TM DingTalk TM WeMeeting TM Meeting records can be taken using various methods such as audio recording, screen recording, and video recording. Meeting applications can leverage software or artificial intelligence to assist users in managing the entire meeting process, encompassing pre-meeting preparation, in-meeting recording and collaboration, and post-meeting summaries. In office settings, meeting applications can assist users in conducting meetings through hardware and software collaboration, audio optimization, and large-scale model summarization overlay. Users can also use tools beyond meeting applications to record meetings; for example, they can use applications with text recording, speech recognition, audio recording, or video recording capabilities to record the content of online or offline meetings, thus obtaining meeting minutes.

[0109] Currently, users cannot intuitively view and manage meeting records from different channels, causing inconvenience and a poor user experience. For example, when a user has participated in meetings across multiple meeting applications, they need to search for the corresponding meeting records in each application separately. Similarly, when a user has participated in an offline meeting, it is difficult to access the meeting records on their electronic device.

[0110] To address the aforementioned issues, this application provides a meeting recording method. In this method, meeting records generated on application 1 can be linked to a schedule on application 2. This allows the user to access the meeting records on application 2 and / or access the schedule on application 1 based on this link. This enables the integration of meeting records from different channels through the schedule, facilitating intuitive viewing and management of meeting records from various channels within the schedule, thus enhancing the user experience.

[0111] In this embodiment, application 1 can be an application for generating meeting minutes by recording the content of a meeting (e.g., a meeting application, or an application with text recording, speech recognition, recording, or video recording functions). Application 1 can be a built-in application of the operating system (e.g., a voice assistant), or a third-party application (i.e., an application not included in the operating system's core functionality); this embodiment does not impose any limitations on this. In some embodiments, application 1 can include an artificial intelligence (AI) model. For example, application 1 can be a voice assistant, a software application that enables human-computer interaction based on AI technology. The voice assistant can recognize the user's voice commands, understand their intentions, and utilize technologies such as natural language processing and speech synthesis to provide users with various services and assistance, such as information retrieval, schedule management, reminder settings, and device control.

[0112] In this embodiment of the application, meeting minutes may include records of the meeting process that have not been processed by the AI ​​model (such as meeting screen recording files, meeting audio files, meeting video files, etc.), and may also include integrated meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in application 1. This embodiment of the application does not limit this.

[0113] In this embodiment of the application, application 2 can be an application with a schedule management function. Application 2 can be an application that comes with the operating system (such as a calendar) or a third-party application (i.e., an application that does not come with the operating system). This embodiment of the application does not limit this.

[0114] In this embodiment of the application, a schedule is a task that needs to be completed within a preset time period (e.g., within 1 hour). Its name can also be a reminder, event, task, important day, important thing, etc. This embodiment of the application does not limit its name.

[0115] In this embodiment of the application, the association between meeting minutes and schedule can be established on application 2 or application 1, and this embodiment of the application does not limit this.

[0116] Figure 1A illustrates the overall flow of a meeting record method for establishing a relationship between meeting minutes and schedules on application 2, as provided in an embodiment of this application.

[0117] As shown in Figure 1A, the method may include:

[0118] S101. Obtain the first attribute information of meeting record 1 from application 1.

[0119] In this embodiment, application 2 can obtain first attribute information of meeting record 1 from application 1. This first attribute information can be used to indicate the time or identifier of the first meeting, so that application 2 can subsequently establish a relationship between meeting record 1 and schedule 1 on application 2 based on the first attribute information. The meeting record 1 can be used to record the first content of the first meeting. This first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video files, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This embodiment does not limit this. Application 1 can be a built-in application of the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system). This embodiment does not limit this.

[0120] S102. Establish the association between meeting minutes 1 and schedule 1 on application 2 based on the first attribute information.

[0121] In this embodiment, after obtaining the first attribute information of meeting record 1 from application 1, application 2 can establish an association between meeting record 1 on application 1 and schedule 1 on application 2 based on the first attribute information. Application 2 can be an application with schedule management functionality; it can be a built-in application of the operating system (e.g., a calendar) or a third-party application (i.e., an application not built into the operating system). This embodiment does not impose any limitations on this. In some embodiments, schedule 1 can be a newly created schedule on application 2 based on the first attribute information, where a newly created schedule refers to a schedule whose creation time on application 2 is later than the generation time of meeting record 1 on application 1. It should be noted that before establishing the association between meeting record 1 on application 1 and schedule 1 on application 2, the user can manually adjust or directly confirm the association between meeting record 1 and schedule 1. For example, the user can manually modify the schedule time of schedule 1. In other embodiments, schedule 1 can be a schedule selected from existing schedules on application 2 based on the first attribute information, where "existing" means the schedule's creation time is earlier than the generation time of meeting record 1. Among the created schedules, the schedule time of schedule 1 is closest to the generation time of meeting record 1, or the time difference between the schedule time of schedule 1 and the generation time of meeting record 1 is less than a first threshold (e.g., 0.5 hours). In some embodiments, schedule 1 associated with meeting record 1 may be a schedule actively selected by the user from the created schedules on application 2. In other embodiments, schedule 1 associated with meeting record 1 may be a schedule automatically matched by application 2 from the created schedules. It should be noted that schedule 1 may be created by application 1 on application 2, or it may be created by application 2 on application 2; this application embodiment does not limit this.

[0122] S103. Based on the association, provide users with an entry point to view meeting minutes 1 on application 2, and / or provide users with an entry point to view schedule 1 on application 1.

[0123] In this embodiment of the application, based on the association between meeting minutes 1 and schedule 1, the application 2 can provide users with an entry point to view meeting minutes 1, and / or the application 1 can provide users with an entry point to view schedule 1.

[0124] In some embodiments, providing a viewing entry point for meeting minutes 1 to the user on application 2 may specifically include: first obtaining the first content of meeting minutes 1 on application 1, and then displaying the first content to the user on application 2. The first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video recordings, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This application embodiment does not limit this. In other embodiments, providing a viewing entry point for meeting minutes 1 to the user on application 2 may specifically include: displaying a first link to the user on application 2. This first link can be used to open the interface for viewing meeting minutes 1 in application 1 (e.g., user interface 720). It should be noted that the first link is an application jump entry point (e.g., an application jump entry point from application 2 to application 1), and its name may also be a control, etc. This application embodiment does not limit its naming.

[0125] In some embodiments, providing a viewing entry point for Schedule 1 to the user on application 1 may specifically include: first obtaining the content information of Schedule 1 on application 2, and then displaying the content information of Schedule 1 to the user on application 1. The content information of Schedule 1 may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants. In other embodiments, providing a viewing entry point for Schedule 1 to the user on application 1 may specifically include: displaying a second link to the user on application 1, which can be used to open the interface for viewing Schedule 1 in application 2 (e.g., user interface 710). It should be noted that the second link is an application jump entry point (e.g., an application jump entry point from application 1 to application 2), and its name may also be a control, etc. The naming of this application embodiment is not limited.

[0126] Optionally, when the entry point for viewing meeting minutes 1 on application 2 is the first link, in response to the operation of opening schedule 1 in application 2, the first link can be displayed in schedule 1 on application 2. This first link can be used to open the interface for viewing meeting minutes 1 in application 1 (e.g., user interface 720). In response to the operation on the first link, the display can be switched from schedule 1 in application 2 to meeting minutes 1 in application 1. For example, as shown in Figures 6A-6C, in response to the operation of opening schedule 1 in the calendar (e.g., clicking schedule 431 in user interface 430), the first link can be displayed in schedule 1 on the calendar. This first link can be used to open the interface for viewing meeting minutes 1 in the voice assistant (e.g., user interface 720). In response to the operation on the first link, the display can be switched from schedule 1 in the calendar to meeting minutes 1 in the voice assistant.

[0127] In some embodiments, Meeting Record 1 contains multiple meeting records, and Schedule 1 also contains multiple schedules. These multiple meeting records in Meeting Record 1 can correspond one-to-one with the multiple schedules in Schedule 1. Application 2 can establish the association between these multiple meeting records in Meeting Record 1 and the multiple schedules in Schedule 1. Access to Meeting Record 1 can be provided to the user in multiple schedules on Application 2, and / or access to multiple schedules can be provided to the user in Meeting Record 1 on Application 1. For example, a user may attend multiple meetings consecutively over a period of time, and the meeting records of these multiple meetings collectively constitute Meeting Record 1. Application 2 can automatically associate these multiple meeting records with multiple schedules based on one or more of the meeting information such as topic semantics, time period, and speakers. The user can manually adjust or directly confirm the association between multiple meeting records and multiple schedules. Then, access to Meeting Record 1 can be provided to the user in multiple schedules on Application 2, and / or access to multiple schedules can be provided to the user in Meeting Record 1 on Application 1.

[0128] In the embodiments of this application, the executing entity of the above process can be application 2, an electronic device with application 2 installed, or the operating system of the above electronic device. The embodiments of this application do not limit this.

[0129] The method provided in this application embodiment allows application 2 to associate meeting records on application 1 with the schedule on application 2, thereby integrating meeting records from different channels through the schedule. This allows the corresponding meeting records to be updated in the schedule after the meeting ends, making it easier for users to view and manage meeting records from different channels intuitively in the schedule, thus improving the user experience.

[0130] Figure 1B illustrates an overall flow of a meeting recording method for establishing a relationship between meeting minutes and schedules on application 1, as provided in an embodiment of this application.

[0131] As shown in Figure 1B, the method may include:

[0132] S201. Obtain schedule information from application 2.

[0133] In this embodiment, application 1 can obtain schedule information from application 2. This schedule information can be the content information of one or more schedules managed by application 2, and may include, but is not limited to, one or more of the following: event name, schedule time. The schedule information may include the content information of schedule 1 managed by application 2, which may include, but is not limited to, one or more of the following: meeting name, meeting time, participants. Application 2 can be a built-in application of the operating system (e.g., a calendar) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this.

[0134] S202. Establish the association between meeting minutes 1 and schedule 1 on application 1 based on the schedule information.

[0135] In this embodiment, after obtaining schedule information from application 2, application 1 can establish a relationship between meeting record 1 on application 1 and schedule 1 on application 2 based on the schedule information. Application 1 can be used to generate meeting record 1 by recording the first content of the first meeting. Application 1 can be a built-in application of the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any limitations on this. It should be noted that the first content can include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video files, etc.), and can also include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1; this embodiment does not impose any limitations on this.

[0136] In some embodiments, based on schedule information obtained from application 2, application 1 may provide a user with a list of schedules to select. These schedules can be one or more schedules managed by application 2, and may include schedule 1. It is understood that the schedules to select are schedules already created on application 2. Then, in response to the user's selection of schedule 1, application 1 can establish an association between meeting record 1 on application 1 and schedule 1 on application 2. For example, as shown in FIG2D, in response to the user's selection of schedule 1 from created schedules (e.g., meeting 1, meeting 2, meeting 3), application 1 can establish an association between meeting record 1 on application 1 and schedule 1 on application 2. In other embodiments, application 1 can select schedule 1 from created schedules on application 2 based on meeting record 1 and establish an association between meeting record 1 on application 1 and schedule 1 on application 2. For example, among the created schedules, the schedule time of schedule 1 is closest to the generation time of meeting record 1, or the time difference between the schedule time of schedule 1 and the generation time of meeting record 1 is less than a first threshold (e.g., 0.5 hours). It should be noted that "created" as mentioned above refers to the schedule's creation time being earlier than the generation time of meeting record 1. It should also be noted that before establishing the association between meeting record 1 on application 1 and schedule 1 on application 2, the user can manually adjust or directly confirm the association between meeting record 1 and schedule 1; for example, the user can manually modify the schedule time of schedule 1. Furthermore, schedule 1 can be created by application 1 on application 2, or it can be created by application 2 on application 2; this embodiment of the application does not impose any limitations on this.

[0137] In some embodiments, application 1 can generate meeting record 1. For example, application 1 can be a voice assistant. The voice assistant can be turned on before generating meeting record 1. In some embodiments, the voice assistant can be turned on based on user input, which may include, but is not limited to, voice input, gesture input, key input, and touch input. Touch input may be, for example, a click on the voice assistant application icon in the control center, a click on the voice assistant application icon on the desktop, or a click on the voice assistant option in the settings application; this embodiment does not limit this. After the voice assistant is turned on, it can record the meeting and generate meeting record 1. In some embodiments, application 1 can start recording the meeting in response to a user actively initiating meeting recording. For example, application 1 can start recording the meeting in response to a user clicking the start control (e.g., control 363 in user interface 360) in the meeting information settings interface. In other embodiments, application 1 can automatically record the meeting. For example, application 1 can start recording the meeting when the current time is detected to have reached the meeting time set by the user.

[0138] In some embodiments, meeting record 1 is generated in real time during the meeting. In other embodiments, meeting record 1 is generated after the meeting ends. It is understood that the embodiments of this application do not limit the generation time of meeting record 1.

[0139] It should be noted that the embodiments of this application do not limit the method of ending the recording meeting. In some embodiments, application 1 can end the recording meeting in response to the user's active action to end the recording meeting. For example, in response to the user clicking the end control (e.g., control 552 in user interface 550) in the meeting recording interface, application 1 can end the recording meeting. In other embodiments, application 1 can automatically end the recording meeting. For example, application 1 can end the recording meeting if it is detected that the duration of the meeting recording has reached a preset duration (e.g., 1 hour).

[0140] It should be noted that the embodiments of this application do not restrict the order in which the schedule information is obtained from application 2 and the meeting record 1 is generated on application 1. For example, application 1 can first obtain the schedule information from application 2 and then generate meeting record 1. Alternatively, application 1 can first generate meeting record 1 and then obtain the schedule information from application 2. Yet another example is that application 1 can simultaneously generate meeting record 1 and obtain the schedule information from application 2.

[0141] S203. Based on the association, provide users with an entry point to view meeting minutes 1 on application 2, and / or provide users with an entry point to view schedule 1 on application 1.

[0142] In this embodiment of the application, based on the association between meeting minutes 1 and schedule 1, the application 2 can provide users with an entry point to view meeting minutes 1, and / or the application 1 can provide users with an entry point to view schedule 1.

[0143] In some embodiments, providing a viewing entry point for meeting minutes 1 to the user on application 2 may specifically include: first obtaining the first content of meeting minutes 1 on application 1, and then displaying the first content to the user on application 2. The first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video recordings, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This application embodiment does not limit this. In other embodiments, providing a viewing entry point for meeting minutes 1 to the user on application 2 may specifically include: displaying a first link to the user on application 2. This first link can be used to open the interface for viewing meeting minutes 1 in application 1 (e.g., user interface 720). It should be noted that the first link is an application jump entry point (e.g., an application jump entry point from application 2 to application 1), and its name may also be a control, etc. This application embodiment does not limit its naming.

[0144] In some embodiments, providing a viewing entry point for Schedule 1 to the user on application 1 may specifically include: first obtaining the content information of Schedule 1 on application 2, and then displaying the content information of Schedule 1 to the user on application 1. The content information of Schedule 1 may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants. In other embodiments, providing a viewing entry point for Schedule 1 to the user on application 1 may specifically include: displaying a second link to the user on application 1, which can be used to open the interface for viewing Schedule 1 in application 2 (e.g., user interface 710). It should be noted that the second link is an application jump entry point (e.g., an application jump entry point from application 1 to application 2), and its name may also be a control, etc. The naming of this application embodiment is not limited.

[0145] Optionally, when the entry point for viewing meeting minutes 1 on application 2 is the first link, in response to the operation of opening schedule 1 in application 2, the first link can be displayed in schedule 1 on application 2. This first link can be used to open the interface for viewing meeting minutes 1 in application 1 (e.g., user interface 720). In response to the operation on the first link, the display can be switched from schedule 1 in application 2 to meeting minutes 1 in application 1. For example, as shown in Figures 6A-6C, in response to the operation of opening schedule 1 in the calendar (e.g., clicking schedule 431 in user interface 430), the first link can be displayed in schedule 1 on the calendar. This first link can be used to open the interface for viewing meeting minutes 1 in the voice assistant (e.g., user interface 720). In response to the operation on the first link, the display can be switched from schedule 1 in the calendar to meeting minutes 1 in the voice assistant.

[0146] In some embodiments, Meeting Record 1 contains multiple meeting records, and Schedule 1 also contains multiple schedules. These multiple meeting records in Meeting Record 1 can correspond one-to-one with the multiple schedules in Schedule 1. Application 1 can establish the association between these multiple meeting records in Meeting Record 1 and these multiple schedules in Schedule 1. Access to Meeting Record 1 can be provided to the user in multiple schedules on Application 2, and / or access to multiple schedules can be provided to the user in Meeting Record 1 on Application 1. For example, within a certain period, a user continuously attends multiple meetings, and the meeting records of these multiple meetings collectively constitute Meeting Record 1. Application 1 can automatically associate these multiple meeting records with multiple schedules based on one or more of the meeting information such as topic semantics, time period, and speakers. The user can manually adjust or directly confirm the association between multiple meeting records and multiple schedules. Then, access to Meeting Record 1 can be provided to the user in multiple schedules on Application 2, and / or access to multiple schedules can be provided to the user in Meeting Record 1 on Application 1.

[0147] In the embodiments of this application, the executing entity of the above process can be application 1, an electronic device with application 1 installed, or the operating system of the electronic device. The embodiments of this application do not limit this.

[0148] The method provided in this application embodiment allows application 1 to associate meeting records on application 1 with schedules created on application 2, thereby integrating meeting records from different channels through schedules. This enables the corresponding meeting records to be updated in the schedule after the meeting ends, facilitating users to intuitively view and manage meeting records from different channels in the schedule, thus improving the user experience.

[0149] Figure 1C illustrates another general flow of the meeting record method for establishing the association between meeting minutes and schedule on application 1, as provided in an embodiment of this application.

[0150] As shown in Figure 1C, the method may include:

[0151] S301. After Application 1 generates Meeting Record 1 by recording the first content of the first meeting, the association between Meeting Record 1 and Schedule 1 on Application 2 is established. Schedule 1 is a new schedule created on Application 2 based on Meeting Record 1.

[0152] In this embodiment, application 1 can generate meeting minutes 1 by recording the first content of the first meeting. It should be noted that the first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video files, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This embodiment does not limit this. Application 1 can be a built-in application of the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system). This embodiment does not limit this. For example, application 1 can be a voice assistant. Before generating meeting minutes 1, the voice assistant can be turned on. In some embodiments, the voice assistant can be turned on based on user input, which may include, but is not limited to, voice input, gesture input, key input, and touch input. Touch input may be, for example, clicking the voice assistant application icon in the control center, clicking the voice assistant application icon on the desktop, or clicking the voice assistant option in the settings application. This embodiment does not limit this. After the voice assistant is activated, it can record the meeting and generate meeting record 1. In some embodiments, application 1 can start recording the meeting in response to the user actively initiating the recording. For example, application 1 can start recording the meeting in response to the user clicking the start control (e.g., control 363 in user interface 360) in the meeting information settings interface. In other embodiments, application 1 can record the meeting automatically. For example, application 1 can start recording the meeting when the current time detects that the user-set meeting time has arrived.

[0153] In some embodiments, meeting record 1 is generated in real time during the meeting. In other embodiments, meeting record 1 is generated after the meeting ends. It is understood that the embodiments of this application do not limit the generation time of meeting record 1.

[0154] It should be noted that the embodiments of this application do not limit the method of ending the recording meeting. In some embodiments, application 1 can end the recording meeting in response to the user's active action to end the recording meeting. For example, in response to the user clicking the end control (e.g., control 552 in user interface 550) in the meeting recording interface, application 1 can end the recording meeting. In other embodiments, application 1 can automatically end the recording meeting. For example, application 1 can end the recording meeting if it is detected that the duration of the meeting recording has reached a preset duration (e.g., 1 hour).

[0155] In this embodiment, after application 1 generates meeting record 1 by recording the first content of the first meeting, application 1 can establish an association between meeting record 1 on application 1 and schedule 1 on application 2. Application 2 can be a built-in application of the operating system (e.g., a calendar) or a third-party application (i.e., an application not built into the operating system); this embodiment does not impose any restrictions on this. Schedule 1 can be a newly created schedule on application 2 based on meeting record 1. This newly created schedule refers to a schedule on application 2 whose creation time is later than the generation time of meeting record 1 on application 1. It should be noted that schedule 1 can be created by application 1 on application 2, or it can be created by application 2 on application 2; this embodiment does not impose any restrictions on this.

[0156] In some embodiments, in response to a user's first operation on application 1, application 1 can establish an association between meeting record 1 on application 1 and schedule 1 on application 2. The first operation can also be used to trigger the creation of a new schedule 1 on application 2. In other embodiments, application 1 can create a new schedule 1 on application 2 based on meeting record 1 and establish an association between meeting record 1 on application 1 and schedule 1 on application 2. For example, the schedule time of the newly created schedule 1 is closest to the generation time of meeting record 1, or the time difference between the schedule time of the newly created schedule 1 and the generation time of meeting record 1 is less than a first threshold (e.g., 0.5 hours). It should be noted that before establishing the association between meeting record 1 on application 1 and schedule 1 on application 2, the user can manually adjust or directly confirm the association between meeting record 1 and schedule 1; for example, the user can manually modify the schedule time of schedule 1.

[0157] S302. Based on the association, provide users with an entry point to view meeting minutes 1 on application 2, and / or provide users with an entry point to view schedule 1 on application 1.

[0158] In this embodiment of the application, based on the association between meeting minutes 1 and schedule 1, the application 2 can provide users with an entry point to view meeting minutes 1, and / or the application 1 can provide users with an entry point to view schedule 1.

[0159] In some embodiments, providing a viewing entry point for meeting minutes 1 to the user on application 2 may specifically include: first obtaining the first content of meeting minutes 1 on application 1, and then displaying the first content to the user on application 2. The first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video recordings, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This application embodiment does not limit this. In other embodiments, providing a viewing entry point for meeting minutes 1 to the user on application 2 may specifically include: displaying a first link to the user on application 2. This first link can be used to open the interface for viewing meeting minutes 1 in application 1 (e.g., user interface 720). It should be noted that the first link is an application jump entry point (e.g., an application jump entry point from application 2 to application 1), and its name may also be a control, etc. This application embodiment does not limit its naming.

[0160] In some embodiments, providing a viewing entry point for Schedule 1 to the user on application 1 may specifically include: first obtaining the content information of Schedule 1 on application 2, and then displaying the content information of Schedule 1 to the user on application 1. The content information of Schedule 1 may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants. In other embodiments, providing a viewing entry point for Schedule 1 to the user on application 1 may specifically include: displaying a second link to the user on application 1, which can be used to open the interface for viewing Schedule 1 in application 2 (e.g., user interface 710). It should be noted that the second link is an application jump entry point (e.g., an application jump entry point from application 1 to application 2), and its name may also be a control, etc. The naming of this application embodiment is not limited.

[0161] Optionally, when the entry point for viewing meeting minutes 1 on application 2 is the first link, in response to the operation of opening schedule 1 in application 2, the first link can be displayed in schedule 1 on application 2. This first link can be used to open the interface for viewing meeting minutes 1 in application 1 (e.g., user interface 720). In response to the operation on the first link, the display can be switched from schedule 1 in application 2 to meeting minutes 1 in application 1. For example, as shown in Figures 6A-6C, in response to the operation of opening schedule 1 in the calendar (e.g., clicking schedule 431 in user interface 430), the first link can be displayed in schedule 1 on the calendar. This first link can be used to open the interface for viewing meeting minutes 1 in the voice assistant (e.g., user interface 720). In response to the operation on the first link, the display can be switched from schedule 1 in the calendar to meeting minutes 1 in the voice assistant.

[0162] In some embodiments, Meeting Record 1 contains multiple meeting records, and Schedule 1 also contains multiple schedules. These multiple meeting records in Meeting Record 1 can correspond one-to-one with the multiple schedules in Schedule 1. Application 1 can establish the association between these multiple meeting records in Meeting Record 1 and these multiple schedules in Schedule 1. Access to Meeting Record 1 can be provided to the user in multiple schedules on Application 2, and / or access to multiple schedules can be provided to the user in Meeting Record 1 on Application 1. For example, within a certain period, a user continuously attends multiple meetings, and the meeting records of these multiple meetings collectively constitute Meeting Record 1. Application 1 can automatically associate these multiple meeting records with multiple schedules based on one or more of the meeting information such as topic semantics, time period, and speakers. The user can manually adjust or directly confirm the association between multiple meeting records and multiple schedules. Then, access to Meeting Record 1 can be provided to the user in multiple schedules on Application 2, and / or access to multiple schedules can be provided to the user in Meeting Record 1 on Application 1.

[0163] In the embodiments of this application, the executing entity of the above process can be application 1, an electronic device with application 1 installed, or the operating system of the electronic device. The embodiments of this application do not limit this.

[0164] The method provided in this application embodiment allows application 1 to associate meeting records on application 1 with newly created schedules on application 2, thereby integrating meeting records from different channels through the schedule. This enables the corresponding meeting records to be updated in the schedule after the meeting ends, facilitating users to intuitively view and manage meeting records from different channels in the schedule, thus improving the user experience.

[0165] It should be noted that in the embodiments of Figures 1A, 1B, and 1C, after generating meeting record 1, application 1 can save meeting record 1 in application 1, so that schedule 1 on application 2 can be associated with meeting record 1 on application 1. Application 1 can be used to generate meeting record 1 by recording the first content of the first meeting and save meeting record 1 in application 1. In some embodiments of this application, after application 1 generates meeting record 1, the meeting record 1 can be saved to application 3, so that schedule 1 on application 2 can be associated with meeting record 1 on application 3. Application 1 can be used to generate meeting record 1 by recording the first content of the first meeting. Application 1 can be a built-in application of the operating system (e.g., a voice assistant) or a third-party application (i.e., an application not built into the operating system). This application embodiment does not limit this. Application 3 can be used to save meeting record 1 generated by application 1. Application 3 can be a built-in application of the operating system (e.g., a memo app) or a third-party application (i.e., an application not built into the operating system). This application embodiment does not limit this.

[0166] When meeting record 1 generated by application 1 is saved to application 3: In some embodiments, application 2 can establish an association between meeting record 1 on application 3 and schedule 1 on application 2. Specifically, application 2 can first obtain the first attribute information of meeting record 1 from application 3, then establish an association between meeting record 1 on application 3 and schedule 1 on application 2 based on the first attribute information, and finally provide the user with an entry point to view meeting record 1 on application 2, and / or provide the user with an entry point to view schedule 1 on application 3 based on the association. In other embodiments, application 3 can establish an association between meeting record 1 on application 3 and schedule 1 on application 2. For example, application 3 can first obtain schedule information from application 2, then establish an association between meeting record 1 on application 3 and schedule 1 on application 2 based on the schedule information, and finally provide the user with an entry point to view meeting record 1 on application 2, and / or provide the user with an entry point to view schedule 1 on application 3 based on the association. For example, after meeting record 1 is generated in application 1, application 3 can save meeting record 1 to application 3 and establish a relationship between meeting record 1 in application 3 and schedule 1 in application 2. Schedule 1 is a new schedule created in application 2 based on meeting record 1. Finally, based on the relationship, application 2 provides users with an entry point to view meeting record 1, and / or application 3 provides users with an entry point to view schedule 1. In this way, meeting records from different channels are integrated through the schedule, so that the corresponding meeting records can be updated in the schedule after the meeting ends. This makes it easier for users to intuitively view and manage meeting records from different channels in the schedule, improving the user experience.

[0167] For example, as shown in Figures 7A-7E, after saving meeting minutes 1 to a memo, in response to an operation to open schedule 1 in the calendar (e.g., clicking schedule 431 in user interface 430), a viewing entry for meeting minutes 1 can be displayed in schedule 1 on the calendar. This viewing entry for meeting minutes 1 can be used to open the interface for viewing meeting minutes 1 in the memo (e.g., user interface 810). In response to an operation on the viewing entry for meeting minutes 1, the display can be switched from schedule 1 in the calendar to meeting minutes 1 in the memo, which may have a viewing entry for schedule 1. This viewing entry for schedule 1 can be used to open the interface for viewing schedule 1 in the calendar (e.g., user interface 710). In response to an operation on the viewing entry for schedule 1, the display can be switched from displaying meeting minutes 1 saved in the memo to displaying schedule 1 in the calendar.

[0168] It should be noted that Schedule 1 on Application 2 can be associated only with Meeting Record 1 on Application 3, and Schedule 1 on Application 2 can also be associated only with Meeting Record 1 on Application 1. Schedule 1 on Application 2 can also be associated with both Meeting Record 1 on Application 3 and Meeting Record 1 on Application 1 simultaneously. This application embodiment does not impose any limitations on this. It is understood that this application embodiment does not limit the number of viewing entry points for Meeting Record 1 in Schedule 1. In some embodiments, only the viewing entry point for Meeting Record 1 on Application 1 can be displayed in Schedule 1, such as entry point 712 in the user interface 710 shown in FIG. 6B. In other embodiments, only the viewing entry point for Meeting Record 1 on Application 3 can be displayed in Schedule 1, such as entry point 713 in the user interface 710 shown in FIG. 7B. In other embodiments, both the viewing entry points for Meeting Record 1 on Application 1 and Meeting Record 1 on Application 3 can be displayed in Schedule 1 simultaneously.

[0169] It is understandable that the storage format of meeting record 1 may differ across different applications. For example, meeting record 1 may be stored in different formats in application 1, application 2, and application 3. For instance, meeting record 1 may be stored as an audio file in application 1, as a hyperlink in the calendar of application 2, and as a document file in the default folder of application 3.

[0170] Currently, when users hold meetings through multiple meeting applications, these applications create corresponding meeting schedules in the calendar. However, the meeting records for these schedules are isolated from each other, making it inconvenient for users to view and search meeting records. The meeting recording method provided in this application can intelligently integrate meeting records generated by multiple meeting applications into a schedule management application (e.g., a calendar). This allows users to quickly view and search all meeting schedules and corresponding meeting records, and also facilitates navigation to specific schedules via meeting records.

[0171] Based on the above overall method flow, taking application 1 as a voice assistant, application 2 as a calendar, and application 3 as a memo as examples, the following will describe in detail a series of graphical user interfaces provided by the embodiments of this application.

[0172] In some embodiments, as shown in Figures 2A-2F, before the voice assistant opens and starts recording the meeting, the voice assistant can set meeting information based on user input. This meeting information may include, but is not limited to, one or more of the following: meeting name, audio source (i.e., meeting audio recording method), microphone range, meeting location, meeting time, participants, associated schedule (i.e., the schedule for saving meeting records), and meeting topic area.

[0173] For example, as shown in FIG2A, after the voice assistant is turned on, a user interface 310 may be displayed in the voice assistant, which can be a meeting information settings interface. The meeting information settings interface may include a sound source input box (e.g., input box 311), which can be used to receive input from the user to select the meeting sound recording method (e.g., microphone and system sound). Optionally, the sound source input box displays default options for the sound source (e.g., "microphone and system sound" option). The sound source input box may contain a trigger control (e.g., control 312), which can be used to trigger the display of one or more sound source options. In some embodiments, in response to a user input operation (e.g., a click) on the sound source input box (e.g., input box 311) or the trigger control (e.g., control 312), the voice assistant may display a user interface 320 as shown in FIG2B.

[0174] For example, as shown in Figure 2B, the voice assistant may display a user interface 320. This user interface 320 may include a sound source selection box (e.g., selection box 321), which may include one or more sound source options. These options may include, but are not limited to, a "microphone" option (e.g., option 322), a "system sound" option (e.g., option 323), and a "microphone and system sound" option (e.g., option 324). A microphone as a sound source can be used to record real-world ambient sound, system sound as a sound source can be used to record online audio, and a microphone and system sound as a sound source can be used to record online audio. Furthermore, the sound source selection box may also include a confirmation control (e.g., control 325) and a cancellation control, wherein the confirmation control can be used to select the meeting audio recording method. In some embodiments, in response to a user’s sequential action on a sound source option (e.g., “microphone and system sound”) and an input operation (e.g., a click) of a confirmation control (e.g., control 325), the voice assistant may display a user interface 330 as shown in FIG2C, in which a sound source input box (e.g., input box 331) displays the sound source (e.g., microphone and system sound) selected by the user.

[0175] Currently, meeting applications can only record online meetings, not offline meetings. Therefore, users often cannot access the meeting minutes of offline meetings on their electronic devices. However, the meeting recording method provided in this application can generate offline meeting minutes using a microphone and save them to a schedule management application. This allows for the integration of meeting minutes from different formats (online and offline), making it easier for users to view and manage meeting minutes from different channels intuitively within their schedules, thus improving the user experience.

[0176] Specifically, if the meeting is an offline meeting, users can choose a microphone as the audio source, and the meeting record can include the meeting record generated from the sound captured by the microphone. If the meeting is an online meeting, users can choose internal system audio as the audio source, and the meeting record can include the meeting record generated from online audio captured via the network. If the meeting is a combination of online and offline, users can choose both a microphone and internal system audio as audio sources, and the meeting record can include the meeting record generated from the sound captured by the microphone and the meeting record generated from online audio captured via the network. A meeting combining online and offline elements could be, for example, an online meeting in which multiple offline users participate.

[0177] For example, as shown in FIG2C, the voice assistant may display a user interface 330, which can be a meeting information settings interface. The meeting information settings interface may include an associated schedule input box (e.g., input box 332), which can be used to receive input from the user selecting a schedule to save meeting records (e.g., creating a new schedule). Optionally, the associated schedule input box displays default options for associated schedules (e.g., the "create a new schedule" option). The associated schedule input box may contain a trigger control (e.g., control 333), which can be used to trigger the display of one or more associated schedule options. In some embodiments, in response to a user input operation (e.g., a click) on the associated schedule input box (e.g., input box 332) or the trigger control (e.g., control 333), the voice assistant may display a user interface 340 as shown in FIG2D.

[0178] For example, as shown in FIG2D, the voice assistant may display a user interface 340, which may include an associated schedule selection box (e.g., selection box 341), and the associated schedule selection box may include one or more associated schedule options. Optionally, the one or more associated schedule options may include created schedule options (e.g., option combination 342). The created schedule in the associated schedule may refer to the schedule whose schedule time is closest to the meeting time entered by the user among the schedules whose creation time is earlier than the meeting start recording time, or the schedule whose schedule time is less than a first threshold (e.g., 0.5 hours) from the meeting time entered by the user. For example, if the user has not yet entered a meeting time, the default meeting time in the voice assistant is the current time displayed in the associated schedule selection box, which is 08:08 on October 31, 2024. The created schedule associated with the current time can be schedule combination 411 in the user interface 410 shown in Figure 3A. Schedule combination 411 indicates three schedules: Meeting 1, Meeting 2, and Meeting 3. These three schedules are also the schedules indicated by option combination 342 in the user interface 340. The associated schedule option may also include a "Create New Schedule" option (e.g., option 343). The newly created schedule can refer to a schedule created in the calendar after the voice assistant generates Meeting Record 1. This newly created schedule refers to a schedule whose creation time is later than the generation time of Meeting Record 1. In addition, the associated schedule selection box may also include a confirmation control (e.g., control 344) and a cancel control, wherein the confirmation control can be used to select the schedule to save the meeting record. In some embodiments, in response to a user’s input operation (e.g., clicking) on ​​an associated schedule option (e.g., “Create new schedule”) and a confirmation control (e.g., control 344), the voice assistant may display a user interface 350 as shown in FIG2E, in which an associated schedule input box (e.g., input box 351) displays the associated schedule (e.g., create new schedule) selected by the user.

[0179] For example, as shown in Figure 2E, the voice assistant may display a user interface 350, which can be a meeting information settings interface. The meeting information settings interface may include a meeting name input box (e.g., input box 352), which can be used to receive user input for the meeting name. Optionally, the meeting name input box may display a prompt message, such as "Please enter the scene name (optional, maximum 50 characters)". The meeting information settings interface may also include a microphone pickup range input box (e.g., input box 353), which can be used to receive user input for selecting the microphone pickup range. The microphone pickup range input box displays default options for the microphone pickup range (e.g., "wide range" option). The microphone pickup range input box may contain a trigger control, which can be used to trigger the display of one or more microphone pickup range options. It is understood that the microphone pickup range input box can only receive user input when the sound source includes a microphone (the sound source is a microphone, or a microphone and system sound). The meeting information settings interface may also include a combined input box (e.g., input box 354), which can be used to receive one or more inputs from the user regarding the meeting location, meeting time, and participants. Besides meeting location, meeting time, and participants, the combined input box can also be used to receive inputs from the user regarding other meeting information; this embodiment does not limit this. The meeting information settings interface may also include a topic area input box (e.g., input box 355), which can be used to receive input from the user selecting a meeting topic area. Optionally, the topic area input box displays default options for meeting topic areas (e.g., "General Topic Area" option 356). Besides general topic areas, the topic area input box can also display options for other topic areas, such as science and technology, economics, etc.; this embodiment does not limit this.

[0180] In some embodiments, in response to a user's input operation on a meeting information input box (e.g., entering "Audio Conference 01" in input box 352, entering "Meeting Room 1" in the location input box 354, or selecting "2024 / 10 / 31 16:10" in the time input box 354), the voice assistant can display a user interface 360 ​​as shown in FIG2F. The user interface 360 ​​displays the meeting name input box (e.g., input box 361) with the user-entered meeting name (e.g., "Audio Conference 01"), and the combined input box (e.g., input box 362) with the user-entered meeting location (e.g., "Meeting Room 1") and meeting time (e.g., "2024 / 10 / 31 16:10"). Furthermore, the meeting information settings interface may also include a start control (e.g., control 363), which can be used to trigger the voice assistant to start recording the meeting.

[0181] In some embodiments, as shown in Figures 4A-4E, meeting information can be modified in the voice assistant after the meeting recording begins.

[0182] It should be noted that, as mentioned above, the user selected "Create New Schedule" in the associated schedule input box of the meeting information settings interface. Therefore, after starting to record the meeting, a new schedule with the meeting time entered by the user is created in the calendar. For example, as shown in Figure 3B, compared with the user interface 410 shown in Figure 3A, the schedule for October 31st displayed in the user interface 420 has added a new schedule 421. This schedule 421 is the schedule for the meeting named "Audio Conference 01," which is the meeting name entered by the user in the meeting information settings interface.

[0183] For example, as shown in Figure 4A, after the meeting recording begins, a user interface 510 can be displayed in the voice assistant. This user interface 510 can be a meeting recording interface. The meeting recording interface can include a meeting name (e.g., meeting name 511 indicates the meeting name "Voice Meeting 01"), which corresponds to the meeting name entered by the user in the meeting information settings interface. The meeting recording interface can also include a meeting recording component (e.g., component 512), which can be used to indicate the duration of the meeting recording. For example, component 512 indicates that the meeting recording duration is 0 hours, 0 minutes, and 0 seconds, and that the meeting has just started recording.

[0184] For example, as shown in Figure 4B, during meeting recording, a user interface 520 can be displayed in the voice assistant. This user interface 520 can be a meeting recording interface. The meeting recording interface can include setting controls (e.g., control 521), which can be used to trigger the display of a meeting information setting box. The meeting recording interface can also include a meeting recording component (e.g., component 522), which can be used to indicate the duration of the meeting recording. For example, component 522 indicates that the duration of the meeting recording is 0 hours, 15 minutes, and 8 seconds. In addition, after the duration of the meeting recording exceeds a preset duration (e.g., 1 minute), the meeting recording interface can also include text content converted from the meeting audio. This text content can include, but is not limited to, the speech content of each speaker in the meeting (e.g., instruction information 525), the speaker's name (e.g., instruction information 523), and the speaking time of each speaker (e.g., instruction information 524), wherein the speaker's name can be recognized by the voice assistant. It should be noted that the meeting can be a video conference, an audio conference, or a text conference; this embodiment does not limit this. The speaker's input during the meeting can be text input, voice input, or image input. Image input can include picture input and / or video input, and this application embodiment does not limit this.

[0185] In some embodiments, in response to a user input action (e.g., a click) on a setting control (e.g., control 521), the voice assistant may display a user interface 530 as shown in FIG4C.

[0186] For example, as shown in FIG4C, the voice assistant may display a user interface 530, which may include a meeting information setting box (e.g., setting box 531) and a meeting name input box (e.g., input box 532), which can be used to receive user input for the meeting name. In some embodiments, in response to a user's input operation on the meeting information setting box (e.g., changing "Voice Meeting 01" in input box 532 of setting box 531 to "Meeting 4"), the voice assistant may display a user interface 540 as shown in FIG4D, in which the meeting name input box (e.g., input box 542) of the meeting information setting box (e.g., setting box 541) displays the meeting name (e.g., "Meeting 4") modified by the user. In addition, the user interface 540 may also include a confirmation control (e.g., control 543), which can be used to save the meeting information modified by the user in the meeting information setting box. In some embodiments, in response to a user's input operation on the confirmation control (e.g., clicking control 543), the voice assistant may display a user interface 550 as shown in FIG4E.

[0187] For example, as shown in Figure 4E, after modifying the meeting information, the voice assistant may display a user interface 550, which may include the modified meeting name (e.g., meeting name 551 indicates that the user has modified the meeting name to "Meeting 4"). Furthermore, the user interface 550 may also include an end control (e.g., control 552), which can be used to trigger the end of the meeting recording. At this time, the meeting name of the schedule in the calendar that saves the meeting recording is also modified. For example, as shown in Figure 3C, compared to the user interface 420 shown in Figure 3B, the meeting name of schedule 431 displayed in user interface 430 has been changed from "Voice Meeting 01" to "Meeting 4," which is the meeting name modified by the user in the meeting information settings box.

[0188] In some embodiments, in response to a user's input action on the end control (e.g., clicking control 552), the voice assistant may display the user interface 610 as shown in FIG5A.

[0189] In some embodiments, as shown in Figures 5A-5B, after the voice assistant generates meeting record 1, meeting record 1 can be saved to a memo. Exemplarily, as shown in Figure 5A, the voice assistant may display a user interface 610, which may include a prompt box (e.g., prompt box 611) containing information prompting the user whether to save meeting record 1, such as "Meeting ended, save the current meeting record?". In some examples, the prompt information may not be conveyed to the user through a user interface, but rather through other means, such as through voice announcement. Furthermore, the user interface 610 may also include a confirm control (e.g., control 612) and a cancel control, wherein the confirm control can be used to save meeting record 1. In some embodiments, in response to the user clicking the confirm control (e.g., control 612) in the user interface 610, the meeting record 1 generated by the voice assistant can be saved to a memo (e.g., meeting record 1 is saved to the default folder in the memo), and the voice assistant may display a user interface 620 as shown in Figure 5B. For example, as shown in FIG5B, the voice assistant can display a user interface 620, which may include a prompt box (e.g., prompt box 621) containing information prompting the user whether to open the memo after the meeting minutes 1 have been successfully saved, such as "Saved successfully, open memo?". In some examples, the above prompt information may not be conveyed to the user through a display interface, but through other means, such as through voice announcement. Furthermore, the user interface 620 may also include a confirm control (e.g., control 622) and a cancel control, wherein the confirm control can be used to trigger the user to navigate from the voice assistant to the memo.

[0190] In some embodiments, as shown in Figures 6A-6C, in response to the operation of opening Schedule 1 in the calendar (e.g., clicking Schedule 431 in user interface 430), an entry point for viewing Meeting Record 1 on the voice assistant can be displayed in Schedule 1. This entry point can be used to open the interface for viewing Meeting Record 1 in the voice assistant. In response to the operation on the entry point for viewing Meeting Record 1, the display can be switched from Schedule 1 in the calendar to Meeting Record 1 in the voice assistant.

[0191] For example, as shown in Figure 6A, when the calendar is opened, a user interface 430 can be displayed in the calendar. The user interface 430 can be referred to in Figure 3C above, and will not be described again here.

[0192] For example, as shown in Figure 6B, after opening Schedule 1 in the calendar, a user interface 710 can be displayed in the calendar. This user interface 710 can be the interface for Schedule 1, which may contain Schedule 1 (e.g., Schedule 711). Schedule 1 may also contain an entry point for viewing Meeting Record 1 on the voice assistant (e.g., entry point 712), which can be used to open the interface for viewing Meeting Record 1 in the voice assistant. In some embodiments, Schedule 1 may contain schedule information, which may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants. For example, the schedule information for Schedule 711 includes the meeting name "Meeting 4," the meeting time "16:10-17:10," and "Thursday, October 31st." In some embodiments, Schedule 1 may also contain a summary of Meeting Record 1, which is a brief overview of Meeting Record 1 provided by an AI model.

[0193] In some embodiments, in response to a user's input operation on the first entry point (e.g., clicking entry point 712), the voice assistant may display the user interface 720 as shown in FIG6C.

[0194] For example, as shown in FIG6C, the voice assistant may display a user interface 720, which can be the interface of the voice assistant storing meeting records 1. It should be noted that the meeting records 1 stored in the voice assistant may include records of the meeting process that have not been processed by the AI ​​model, such as meeting audio files in the user interface 720, and may also include integrated meeting content processed by the AI ​​model, such as the text of the speeches of each speaker in the user interface 720. This application embodiment does not limit this.

[0195] In some embodiments, as shown in Figures 7A-7E, after meeting record 1 is saved to the memo, in response to an operation to open schedule 1 in the calendar (e.g., clicking schedule 431 in user interface 430), a viewing entry for meeting record 1 in the memo can be displayed in schedule 1. This viewing entry for meeting record 1 in the memo can be used to open an interface for viewing meeting record 1 in the memo. In response to an operation to the viewing entry for meeting record 1 in the memo, the display can be switched from schedule 1 in the calendar to meeting record 1 saved in the memo. Then, in response to an operation to the viewing entry for schedule 1 in the memo, the display can be switched from meeting record 1 saved in the memo to schedule 1 in the calendar.

[0196] For example, as shown in Figure 7A, when the calendar is opened, a user interface 430 can be displayed in the calendar. The user interface 430 can be referred to in Figure 3C above, and will not be described again here.

[0197] For example, as shown in FIG7B, after opening Schedule 1 in the calendar, a user interface 710 can be displayed in the calendar. The user interface 710 can be the interface of Schedule 1. The interface of Schedule 1 can include an entry point for viewing Meeting Minutes 1 in the memo (e.g., entry point 713). The entry point for viewing Meeting Minutes 1 in the memo can be used to open the interface for viewing Meeting Minutes 1 in the memo.

[0198] In some embodiments, in response to a user's input operation on the viewing entry point of meeting record 1 on the memo (e.g., clicking entry point 713), the memo may display the user interface 810 as shown in FIG7C. In other embodiments, in response to a user's input operation on a control (e.g., control 622) in the user interface 620 (e.g., clicking), the memo may display the user interface 810 as shown in FIG7C. In other embodiments, in response to a user's input operation on the memo application icon on the desktop (e.g., clicking), the memo may display the user interface 810 as shown in FIG7C. It is understood that the embodiments of this application do not limit the type of operation for opening the memo.

[0199] For example, as shown in FIG7C, the memo may display a user interface 810, which may be a memo interface storing meeting record 1. Optionally, meeting record 1 may be saved to a default folder in the memo (e.g., the "Voice Assistant" folder 811). Optionally, the user interface 810 may include an identifier of the voice assistant (e.g., identifier 812), which can be used to indicate that meeting record 1 was generated by the voice assistant. The identifier of the voice assistant may include an expansion control (e.g., control 813), which can be used to expand the full content of the meeting record. In some embodiments of this application, the meeting record 1 stored in the memo has a viewing entry for schedule 1 (e.g., entry 814), which can be used to open the interface for viewing schedule 1 in the calendar. It should be noted that the viewing entry for schedule 1 may be, for example, a link or a control, and this embodiment of the application does not limit this. In addition, the user interface 810 may also include part of the content of the meeting record (e.g., text 815). It should be noted that the presentation of Meeting Record 1 in the memo can be a record of the meeting process without AI model processing (such as a screen recording, audio file, video file, etc.), or an integration of meeting content processed by AI model processing, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in the voice assistant, or other formats. This application embodiment does not limit this. It is understood that this application embodiment does not limit the presentation format of Meeting Record 1 in the memo. Optionally, Meeting Record 1 saved in the memo can also have a viewing entry point on the voice assistant. This viewing entry point on the voice assistant is the application jump entry point, which can be used by the user to jump from the memo to the voice assistant. It should be noted that the viewing entry point on the voice assistant can be, for example, a link or a control; this application embodiment does not limit this.

[0200] In some embodiments, in response to a user input operation on an expanded control (e.g., clicking control 813), the memo may display a user interface 820 as shown in FIG7D.

[0201] For example, as shown in Figure 7D, the memo may display a user interface 820, which may include an outline of meeting minutes 1. For example, outline 821 may include meeting information, meeting summary, to-do information, audio transcription, speaking notes, screenshots, and meeting attachments. Furthermore, the user interface 820 may also include the full content of the meeting minutes (e.g., text 822) and an entry point for viewing schedule 1 (e.g., entry point 823), which can be used to open the calendar interface for viewing schedule 1. Optionally, meeting minutes 1 saved in the memo may also have an entry point for viewing meeting minutes 1 on a voice assistant. This entry point on the voice assistant serves as an application jump entry point, allowing users to jump from the memo to the voice assistant.

[0202] In some embodiments, in response to a user's input operation on the viewing entry of Schedule 1 (e.g., clicking entry 823), the calendar can display a user interface 710 as shown in FIG7E, which can be the interface of Schedule 1.

[0203] Currently, users cannot intuitively view and manage meeting records from different channels. For example, when a user participates in multiple meetings using multiple electronic devices, they need to search for the corresponding meeting records on each device, which is inconvenient and results in a poor user experience.

[0204] In some embodiments of this application, based on the association of meeting records and schedules, when the application (application 2) with schedule management function is a built-in application of the operating system (e.g., calendar), the first electronic device can synchronize the association between meeting records and schedules between different electronic devices logged into the same account. This allows users to quickly view meeting records associated with schedules on their various electronic devices, eliminating the need for users to search for the corresponding meeting records on each electronic device when they participate in multiple meetings using their multiple electronic devices. This makes it convenient for users to manage all the meetings they have attended at any time without worrying about missing any.

[0205] The following is a detailed flowchart illustrating a meeting record synchronization method provided in an embodiment of this application.

[0206] Figure 8 exemplarily illustrates the specific flow of a meeting record synchronization method provided in an embodiment of this application. This method can be applied to a first electronic device, which has application 2 installed and is logged in with a first account. Application 2 can be a system application with schedule management functions (i.e., an application that comes with the operating system), such as a calendar.

[0207] As shown in Figure 8, the method may include:

[0208] S401. During the login with the first account, the second electronic device sends an association instruction message to the first electronic device. The association instruction message is used to instruct the second electronic device to establish an association between schedule 2 and meeting record 2 when logging in with the first account.

[0209] In some embodiments, the second electronic device can establish an association between meeting record 2 on application 1 and schedule 2 on application 2. Optionally, to establish the association between meeting record 2 on application 1 and schedule 2 on application 2, application 2 can first obtain first attribute information of meeting record 2 from application 1, and then establish the association between meeting record 2 and schedule 2 on application 2 based on the first attribute information. Optionally, to establish the association between meeting record 2 on application 1 and schedule 2 on application 2, application 1 can first obtain schedule information from application 2, and then establish the association between meeting record 2 on application 1 and schedule 2 based on the schedule information. Optionally, to establish the association between meeting record 2 on application 1 and schedule 2 on application 2, after application 1 generates meeting record 2 by recording the first content of the second meeting, application 1 can establish the association between meeting record 2 and schedule 2 on application 2, where schedule 2 is a new schedule created on application 2 based on meeting record 2. It should be noted that Application 1 is an application in the second electronic device used to generate meeting minutes 2 by recording the first content of the second meeting. Application 1 can be an application built into the operating system of the second electronic device (e.g., a voice assistant), or a third-party application (i.e., an application not built into the operating system of the second electronic device). This application embodiment does not impose any restrictions on this. Application 2 is an application in the second electronic device used to manage schedules. Application 2 can be an application built into the operating system of the second electronic device (e.g., a calendar). The first content can include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video files, etc.), and can also include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in Application 1. This application embodiment does not impose any restrictions on this. Among them, meeting minutes 2 are recorded by the second electronic device during the period when Application 2 is logged in with the first account. After establishing the association between Meeting Record 2 on Application 1 and Schedule 2 on Application 2, during the login period of Application 2 with the first account, the second electronic device can send an association instruction message to the first electronic device. This association instruction message can be used to instruct the second electronic device to establish an association between Schedule 2 and Meeting Record 2 when logging in with the first account. Optionally, the second electronic device can forward the association instruction message to the first electronic device through a server. The server can be a system cloud server, which can be used to receive the association instruction message sent by the second electronic device during login with the first account, and to send the association instruction message to the first electronic device during login with the first account; the first account can be the account used by both the first and second electronic devices to log in to the system.

[0210] It should be noted that the embodiments of this application do not restrict the order in which the first electronic device and the second electronic device log in to the first account. In some embodiments, the first electronic device can log in to the first account simultaneously with the second electronic device. In other embodiments, the first electronic device can log in to the first account first, and the second electronic device can log in to the first account later. In still other embodiments, the second electronic device can log in to the first account first, and the first electronic device can log in to the first account later.

[0211] S402, Upon receiving the association instruction message sent by the second electronic device, the first electronic device saves the association relationship on application 2.

[0212] In some embodiments, after receiving the association instruction message sent by the second electronic device, the first electronic device can save the association between schedule 2 and meeting minutes 2 on application 2. It should be noted that before the first electronic device saves the association between schedule 2 and meeting minutes 2 on application 2, the user can manually adjust or directly confirm the association between meeting minutes 2 and schedule 2; for example, the user can manually modify the schedule time of schedule 2. It should also be noted that application 2 is a built-in application (e.g., a calendar) in the operating system of the first electronic device used for managing schedules.

[0213] S403. Based on the association, provide users with an entry point to view meeting minutes 2 on application 2.

[0214] In some embodiments, after the association between meeting minutes 2 and schedule 2 is saved on application 2, the first electronic device can provide users with an access point to view meeting minutes 2 on application 2 based on the association between meeting minutes 2 and schedule 2.

[0215] Optionally, the first electronic device may also have application 1 installed. In this case, after receiving the association instruction message sent by the second electronic device, the first electronic device can save the association between meeting minutes 2 and schedule 2 on application 1. After saving the association between meeting minutes 2 and schedule 2 on application 1, the first electronic device can provide the user with an entry point to view schedule 2 on application 1 according to the association. It should be noted that the above-mentioned application 1 is an application in the first electronic device used to save meeting minutes 2. This application 1 can be an application that comes with the operating system of the first electronic device (such as a voice assistant or memo), or it can be a third-party application (i.e., an application that does not come with the operating system of the first electronic device). This application embodiment does not limit this.

[0216] It should be noted that the embodiments of this application do not restrict the order in which meeting minutes 2 are saved on application 1 and schedule 2 is saved on application 2. For example, application 1 can save meeting minutes 2 on application 1 first, and then save schedule 2 on application 2. Alternatively, application 1 can save schedule 2 on application 2 first, and then save meeting minutes 2 on application 1. Yet another example is that application 1 can save meeting minutes 2 on application 1 and schedule 2 on application 2 simultaneously.

[0217] In some embodiments, providing a viewing entry point for meeting minutes 2 on application 2 may specifically include: first obtaining the first content of meeting minutes 2 on application 1, and then displaying the first content to the user on application 2. The first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video recordings, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This application embodiment does not limit this. In other embodiments, providing a viewing entry point for meeting minutes 2 on application 2 may specifically include: displaying a first link to the user on application 2. This first link can be used to open the interface for viewing meeting minutes 2 in application 1 (e.g., user interface 720). It should be noted that the first link is an application jump entry point (e.g., an application jump entry point from application 2 to application 1), and its name may also be a control, etc. This application embodiment does not limit its naming.

[0218] In some embodiments, providing a viewing entry point for Schedule 2 to the user on application 1 may specifically include: first obtaining the content information of Schedule 2 on application 2, and then displaying the content information of Schedule 2 to the user on application 1. The content information of Schedule 2 may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants. In other embodiments, providing a viewing entry point for Schedule 2 to the user on application 1 may specifically include: displaying a second link to the user on application 1, which can be used to open the interface for viewing Schedule 2 in application 2 (e.g., user interface 710). It should be noted that the second link is an application jump entry point (e.g., an application jump entry point from application 1 to application 2), and its name may also be a control, etc. The naming of this application embodiment is not limited.

[0219] In this way, based on the association between meeting minutes and schedules, and assuming that the application with schedule management function (application 2) is a built-in application of the operating system (such as a calendar), the first electronic device can synchronize the association between meeting minutes and schedules across different electronic devices logged into the same account. This allows users to quickly view meeting minutes associated with schedules on all their electronic devices, eliminating the need for users to search for the corresponding meeting minutes on each device when participating in multiple meetings using multiple electronic devices. This makes it convenient for users to manage all the meetings they have attended without worrying about missing any.

[0220] In some embodiments of this application, based on the association between meeting minutes and schedules, the first electronic device can share the association between meeting minutes and schedules among different electronic devices. This allows participants to quickly share meeting information without needing to use different meeting applications, thus improving the user experience.

[0221] The following is a detailed flowchart illustrating a meeting record sharing method provided in an embodiment of this application.

[0222] Figure 9 illustrates, for example, the specific flow of a meeting record sharing method provided in an embodiment of this application.

[0223] As shown in Figure 9, the method may include:

[0224] S501, the first electronic device receives the schedule 3 shared by the third electronic device and the meeting minutes 3 associated with the schedule 3.

[0225] In some embodiments, the third electronic device can establish an association between meeting record 3 on application 1 and schedule 3 on application 2. Optionally, to establish an association between meeting record 3 on application 1 and schedule 3 on application 2, application 2 can first obtain first attribute information of meeting record 3 from application 1, and then establish an association between meeting record 3 and schedule 3 on application 2 based on the first attribute information. Optionally, to establish an association between meeting record 3 on application 1 and schedule 3 on application 2, application 1 can first obtain schedule information from application 2, and then establish an association between meeting record 3 on application 1 and schedule 3 based on the schedule information. Optionally, to establish an association between meeting record 3 on application 1 and schedule 3 on application 2, after application 1 generates meeting record 3 by recording the first content of the third meeting, application 1 can establish an association between meeting record 3 and schedule 3 on application 2, where schedule 3 is a new schedule created on application 2 based on meeting record 3. It should be noted that Application 1 mentioned above is an application in the third electronic device used to generate meeting minutes 3 by recording the first content of the third meeting. Application 1 can be an application built into the operating system of the third electronic device (e.g., a voice assistant), or a third-party application (i.e., an application not built into the operating system of the third electronic device). This application embodiment does not limit this. Application 2 mentioned above is an application in the third electronic device used to manage schedules. Application 2 can be an application built into the operating system of the third electronic device (e.g., a calendar), or a third-party application (i.e., an application not built into the operating system of the third electronic device). This application embodiment does not limit this. The first content can include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video files, etc.), and can also include the integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting through the AI ​​model in Application 1. This application embodiment does not limit this. After establishing the association between meeting minutes 3 on application 1 and schedule 3 on application 2, the third electronic device can share schedule 3 and meeting minutes 3 associated with schedule 3 with the first electronic device, or the third electronic device can share meeting minutes 3 and schedule 3 associated with meeting minutes 3 with the first electronic device. Accordingly, the first electronic device can receive schedule 3 and meeting minutes 3 associated with schedule 3 shared by the third electronic device. It should be noted that the association between schedule 3 and meeting minutes 3 can be established by the third electronic device in applications 2 and 1, or it can be shared by other electronic devices to the third electronic device; this embodiment does not limit this. For example, the third electronic device can share the association between meeting minutes 3 and schedule 3 with the first electronic device.In response to the operation of receiving the association between meeting minutes 3 and schedule 3, the first electronic device can receive the association between meeting minutes 3 and schedule 3. It should be noted that the first electronic device can log in to the same account as the third electronic device, or the first electronic device can log in to different accounts than the third electronic device; this embodiment does not impose any limitations on this. It should also be noted that the first electronic device can perform long-distance communication with the third electronic device (e.g., communication via cellular mobile communication, satellite communication, etc.), and the first electronic device can also perform short-distance communication with the third electronic device (e.g., communication via Bluetooth, near field communication (NFC), wireless local area network (WLAN, etc.); this embodiment does not impose any limitations on this.

[0226] S502a, The first electronic device saves meeting minutes 3 on application 1.

[0227] S502b, The first electronic device saves schedule 3 on application 2.

[0228] In some embodiments, after receiving the schedule 3 shared by the third electronic device and the meeting minutes 3 associated with the schedule 3, the first electronic device can save the meeting minutes 3 on application 1 and the schedule 3 on application 2. It should be noted that before the first electronic device saves the meeting minutes 3 on application 1 and the schedule 3 on application 2 (i.e., saves the association between the schedule 3 and the meeting minutes 3), the user can manually adjust or directly confirm the association between the meeting minutes 3 and the schedule 3. For example, the user can manually modify the schedule time of the schedule 3. It should be noted that application 1 is the application in the first electronic device used to save the meeting minutes 3. This application 1 can be an application built into the operating system of the first electronic device (e.g., a voice assistant, memo), or it can be a third-party application (i.e., an application not built into the operating system of the first electronic device). This application embodiment does not impose any limitations on this. Application 2 is the application in the first electronic device used to manage schedules. This application 2 can be an application built into the operating system of the first electronic device (e.g., a calendar), or it can be a third-party application (i.e., an application not built into the operating system of the first electronic device). This application embodiment does not impose any limitations on this.

[0229] It should be noted that the embodiments of this application do not restrict the order in which the meeting minutes 3 are saved on application 1 and the schedule 3 is saved on application 2. For example, application 1 can save the meeting minutes 3 on application 1 first, and then save the schedule 3 on application 2. Alternatively, application 1 can save the schedule 3 on application 2 first, and then save the meeting minutes 3 on application 1. Yet another example is that application 1 can simultaneously save the meeting minutes 3 on application 1 and the schedule 3 on application 2.

[0230] S503. Based on the association, provide the user with an entry point to view meeting minutes 3 on application 2, and / or provide the user with an entry point to view schedule 3 on application 1.

[0231] In some embodiments, after saving meeting minutes 3 on application 1 and schedule 3 on application 2, the first electronic device may provide users with an access point to view meeting minutes 3 on application 2 and / or provide users with an access point to view schedule 3 on application 1, depending on the association between meeting minutes 3 and schedule 3.

[0232] In some embodiments, providing a viewing entry point for meeting minutes 3 to the user on application 2 may specifically include: first obtaining the first content of meeting minutes 3 on application 1, and then displaying the first content to the user on application 2. The first content may include records of the meeting process that have not been processed by the AI ​​model (e.g., meeting screen recordings, meeting audio files, meeting video recordings, etc.), or it may include an integration of meeting content processed by the AI ​​model, such as meeting minutes obtained by organizing the speeches of multiple speakers in the meeting using the AI ​​model in application 1. This application embodiment does not limit this. In other embodiments, providing a viewing entry point for meeting minutes 3 to the user on application 2 may specifically include: displaying a first link to the user on application 2. This first link can be used to open the interface for viewing meeting minutes 3 in application 1 (e.g., user interface 720). It should be noted that the first link is an application jump entry point (e.g., an application jump entry point from application 2 to application 1), and its name may also be a control, etc. This application embodiment does not limit its naming.

[0233] In some embodiments, providing a viewing entry point for Schedule 3 to the user on application 1 may specifically include: first obtaining the content information of Schedule 3 on application 2, and then displaying the content information of Schedule 3 to the user on application 1. The content information of Schedule 3 may include, but is not limited to, one or more of the following: meeting name, meeting time, and participants. In other embodiments, providing a viewing entry point for Schedule 3 to the user on application 1 may specifically include: displaying a second link to the user on application 1, which can be used to open the interface for viewing Schedule 3 in application 2 (e.g., user interface 710). It should be noted that the second link is an application jump entry point (e.g., an application jump entry point from application 1 to application 2), and its name may also be a control, etc. The naming of this application embodiment is not limited.

[0234] In this way, by linking meeting minutes and schedules, the first electronic device can share the association between meeting minutes and schedules across different electronic devices. This allows participants to quickly share meeting information without needing to use separate meeting applications, thus improving the user experience.

[0235] Figure 10 illustrates an exemplary communication system 10 provided in an embodiment of this application.

[0236] As shown in Figure 10, the communication system 10 may include: a first electronic device and a second electronic device. A conference record synchronization method shown in Figure 8 can be applied to the communication system 10.

[0237] The second electronic device can be used to establish a link between meeting minutes 2 on application 1 and schedule 2 on application 2, where application 2 is logged in with the first account. The second electronic device can also be used to send a linking instruction message to the first electronic device, instructing the second electronic device to establish a link between schedule 2 and meeting minutes 2 when logging in with the first account. Application 2 is used to manage schedules and is a built-in application of the operating system; meeting minutes 2 are recorded by the second electronic device during its login with the first account; the first account can be the account used by both the first and second electronic devices to log in to the system. Optionally, the second electronic device can forward the linking instruction message to the first electronic device via a server. The server can be a system cloud server, which can receive the linking instruction message sent by the second electronic device during its login with the first account and send the linking instruction message back to the first electronic device during its login with the first account.

[0238] In this embodiment, the first electronic device has application 2 installed, which is logged into using a first account. The first electronic device can receive association instruction messages sent by the second electronic device, which instruct the second electronic device to establish an association between schedule 2 and meeting minutes 2 when logged in with the first account. The first electronic device can also save the association on application 2. The first electronic device can also provide a viewing entry for meeting minutes 2 to the user on application 2 based on the association. Optionally, the first electronic device can also have application 1 installed. In this case, after receiving the association instruction message sent by the second electronic device, the first electronic device can save the association between meeting minutes 2 and schedule 2 on application 1. After saving the association between meeting minutes 2 and schedule 2 on application 1, the first electronic device can also provide a viewing entry for schedule 2 to the user on application 1 based on the association. It should be noted that application 1 can be used to save meeting minutes 2. Application 1 can be a built-in application of the operating system of the first electronic device (e.g., a voice assistant, memo), or a third-party application (i.e., an application not built into the operating system of the first electronic device). This embodiment does not limit this.

[0239] In this embodiment, a communication connection can be established between the first electronic device and the second electronic device. Based on this communication connection, the second electronic device can synchronize the association between schedule 2 and meeting minutes 2 with the first electronic device. The communication connection established between the first and second electronic devices can include, but is not limited to, wired connections (e.g., a wired connection established via a data cable connected through a Type-C interface), wireless connections such as Bluetooth (BT) and Wireless Fidelity (WiFi), etc. Furthermore, the first and second electronic devices in the communication system 10 can also connect and communicate using any combination of the above methods; this embodiment does not impose any limitations on this. That is to say, the first and second electronic devices in the communication system 10 can form a network (i.e., a network) according to a certain communication protocol and networking strategy, enabling mutual communication between the first and second electronic devices.

[0240] Figure 11 illustrates an exemplary communication system 20 provided in an embodiment of this application.

[0241] As shown in Figure 11, the communication system 20 may include a first electronic device and a third electronic device. A meeting record sharing method shown in Figure 9 can be applied to the communication system 20.

[0242] The third electronic device can be used to establish a relationship between meeting minutes 3 on application 1 and schedule 3 on application 2, and share schedule 3 and meeting minutes 3 associated with schedule 3 with the first electronic device. Application 1 can be used to generate meeting minutes 3 by recording the first content of the third meeting, and application 2 can be used to manage the schedule. It should be noted that the relationship between schedule 3 and meeting minutes 3 can be established by the third electronic device in applications 2 and 1, or it can be shared by other electronic devices to the third electronic device; this embodiment does not impose any limitations on this.

[0243] The first electronic device can be used to receive the schedule 3 shared by the third electronic device and the meeting minutes 3 associated with the schedule 3. The first electronic device can also be used to save the schedule 3 on application 2 and save the meeting minutes 3 on application 1. The first electronic device can also be used to provide users with an access point to view the meeting minutes 3 on application 2 based on the association, and / or provide users with an access point to view the schedule 3 on application 1.

[0244] In this embodiment, a communication connection can be established between the first electronic device and the third electronic device. Based on this communication connection, the third electronic device can share the association between schedule 3 and meeting minutes 3 with the first electronic device. This communication connection can include, but is not limited to, wired connections (e.g., a wired connection established via a data cable connected through a Type-C interface), wireless connections such as WLAN communication connections, cellular mobile communication connections, etc. If it is a WLAN communication connection or a cellular mobile communication connection, then the communication connection between the first electronic device and the server can be an indirect communication connection, i.e., a communication connection established through an access point (AP), which can include, but is not limited to, base stations and routers. Furthermore, the first electronic device and the server in the communication system 20 can also connect and communicate using any combination of the above methods; this embodiment does not impose any limitations on this. That is to say, the first electronic device and the server in the communication system 20 can form a network (i.e., a network) according to a certain communication protocol and networking strategy, enabling mutual communication between the first electronic device and the server.

[0245] Figure 12 illustrates an electronic device 100 provided in an embodiment of this application.

[0246] In this embodiment, the first electronic device, the second electronic device, and the third electronic device can be electronic device 100. Electronic device 100 can be various types of smart terminal devices including a screen, and this embodiment does not limit the specific type of electronic device 100. For example, electronic device 100 can be a mobile phone, or it can be a mobile tablet computer, an in-vehicle tablet computer, a desktop computer, a laptop computer, a handheld computer, a smartwatch, etc.

[0247] As shown in Figure 12, the electronic device 100 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, antenna 1, antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, a display screen 294, and a subscriber identity module (SIM) card interface 295, etc. The sensor module 280 may include at least one of a pressure sensor 280A, a touch sensor 280K, etc.

[0248] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0249] Processor 210 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0250] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0251] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0252] The external storage interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 210 through the external storage interface 220 to perform data storage functions. For example, music, photos, videos, and other data can be stored on the external memory card.

[0253] Internal memory 221 can be used to store one or more computer programs, which include instructions. Processor 210 can execute the aforementioned instructions stored in internal memory 221, thereby causing electronic device 100 to perform the meeting recording method provided in some embodiments of this application, as well as various functional applications and data processing. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system; it may also store one or more application programs (such as a gallery, contacts, calendar, memos, etc.). The data storage area may store data created during the use of electronic device 100 (such as photos, contacts, meeting minutes, etc.). Furthermore, internal memory 221 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0254] USB interface 230 is an interface that conforms to the USB standard specification, specifically it can be a Mini USB interface, Micro USB interface, USB Type-C interface, etc.

[0255] The charging management module 240 receives charging input from the charger. While charging the battery 242, the charging management module 240 can also supply power to the electronic device 100 through the power management module 241.

[0256] The power management module 241 connects the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240, supplying power to the processor 210, internal memory 221, external memory, display 294, and wireless communication module 260, etc. The power management module 241 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 241 may also be located within the processor 210. In other embodiments, the power management module 241 and the charging management module 240 may be located in the same device.

[0257] The wireless communication function of electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. In some embodiments of this application, as the recipient, electronic device 100 can receive schedule 3 and meeting minutes 3 associated with schedule 3 shared by other electronic devices through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor; as the sharer, after establishing the association between meeting minutes 3 and schedule 3, electronic device 100 can share schedule 3 and meeting minutes 3 associated with schedule 3 with other electronic devices through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. In other embodiments of this application, as the synchronized party, electronic device 100 has application 2 installed, which is logged in with a first account. During the login of the first account, electronic device 100 can receive association instruction messages sent by other electronic devices that are also logged into the first account through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. These association instruction messages can be used to instruct other electronic devices to establish an association between schedule 2 and meeting minutes 2 when logging in with the first account. As a synchronizing party, after establishing the association between meeting minutes 2 and schedule 2, electronic device 100 can send association instruction messages to other electronic devices through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor during the login of application 2 with the first account. These association instruction messages can be used to instruct electronic device 100 to establish an association between schedule 2 and meeting minutes 2 when logging in with the first account.

[0258] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0259] The mobile communication module 250 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 250 may include at least one filter, switch, power amplifier, low-noise amplifier, etc. The mobile communication module 250 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna. In some embodiments, at least some functional modules of the mobile communication module 250 may be housed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 and at least some modules of the processor 210 may be housed in the same device.

[0260] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates 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. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor displays images or videos via the display screen 294. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and may be housed within the same device as the mobile communication module 250 or other functional modules.

[0261] The wireless communication module 260 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (WiFi) networks), Bluetooth (BT), global navigation satellite systems, frequency modulation, near field communication (NFC), infrared technology, ultra-wideband (UWB), and SparkLink. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via an antenna, frequency-modulates and filters the electromagnetic wave signals, and sends the processed signal to the processor 210. The wireless communication module 260 can also receive signals to be transmitted from the processor 210, frequency-modulate and amplify them, and then convert them into electromagnetic waves for radiation via the antenna. For example, the wireless communication module 260 may include a Bluetooth module, a WiFi module, etc.

[0262] In some embodiments, a portion of the antenna of the electronic device 100 is coupled to the mobile communication module 250, and another portion of the antenna is coupled to the wireless communication module 260, enabling the electronic device 100 to communicate with networks and other devices via wireless communication technology.

[0263] The electronic device 100 can implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, and an application processor. Examples include music playback and recording. In some embodiments, the electronic device 100 can activate a voice assistant through the audio module 270 to generate meeting minutes 1 via the voice assistant.

[0264] The audio module 270 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 270 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 270 may be located in the processor 210, or some functional modules of the audio module 270 may be located in the processor 210.

[0265] The speaker 270A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 270A.

[0266] The receiver 270B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 270B can be brought close to the ear to listen to the voice.

[0267] Microphone 270C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 270C, inputting the sound signal into microphone 270C. Electronic device 100 may be equipped with at least one microphone 270C.

[0268] In some embodiments of this application, the electronic device 100 can generate meeting minutes 1 by collecting sound through the microphone 270C.

[0269] The 270D headphone jack is used to connect wired headphones.

[0270] Pressure sensor 280A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 280A may be disposed on display screen 294. When a touch operation is applied to display screen 294, electronic device 100 detects the intensity of the touch operation based on pressure sensor 280A. Electronic device 100 may also calculate the touch position based on the detection signal from pressure sensor 280A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities may correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS message is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS message is executed.

[0271] Touch sensor 280K, also known as a touch panel or touch-sensitive surface, can be located on display screen 294. The touch sensor 280K and display screen 294 together form a touchscreen, also called a "touchscreen." Touch sensor 280K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 294. In other embodiments, touch sensor 280K may also be located on the surface of electronic device 100, in a different position than display screen 294.

[0272] In some embodiments of this application, the electronic device 100 can detect operations such as opening a voice assistant, opening schedule 1 in application 2, opening application 3, user selecting schedule 1 in application 1, and user's first operation in application 1 through pressure sensor 280A and touch sensor 280K.

[0273] Electronic device 100 can perform display functions through GPU, display screen 294, and application processor, such as displaying the user interface of application 2 containing a view entry for meeting minutes, the user interface of application 1 containing a view entry for schedules, the user interface of application 3 containing a view entry for schedules, and so on. The GPU is a microprocessor for image processing, connected to display screen 294 and application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 210 may include one or more GPUs, which execute instructions to generate or modify display information.

[0274] The display screen 294 is used to display images, videos, etc. In some embodiments, the electronic device 100 may include one or N display screens 294, where N is a positive integer greater than 1.

[0275] The SIM card interface 295 is used to connect a SIM card. The electronic device 100 interacts with the network through the SIM card to achieve functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from it.

[0276] It should be noted that the application jump entry points (including but not limited to the entry point for viewing meeting minutes and the entry point for viewing the schedule) in the embodiments of this application can be, for example, a link or a control. The embodiments of this application do not limit the display form of the entry points.

[0277] Based on the embodiments of this application, electronic devices can jump between meeting minutes and schedules, with each schedule containing an entry point to view the meeting minutes. Furthermore, the synchronization of the association between meeting minutes and schedules across multiple devices logged into the same account, as well as the sharing of this association between different devices, can be detected through decompilation and end-to-end message processing. In addition, a meeting minute can be associated with multiple schedules, each of which provides an entry point to jump to that single meeting minute.

[0278] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps performed by the electronic device in the above method embodiments, or the steps performed by the human-computer interaction module and the computing module.

[0279] This application also provides a computer program product that, when run on a terminal device, enables the terminal device to perform the steps executed by the electronic device in the above method embodiments.

[0280] This application also provides a chip system, which includes a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the steps performed by the electronic device in any of the method embodiments of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0281] The term "user interface (UI)," or simply "interface," used in the specification and accompanying drawings of this application, refers to the medium through which an application or operating system interacts and exchanges information with the user. It facilitates the conversion between the internal form of information and a form acceptable to the user. The user interface of an application is written in source code using specific computer languages ​​such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the terminal device, ultimately presenting user-recognizable content, such as images, text, and buttons. Controls, also known as widgets, are the basic elements of the user interface. Typical controls include toolbars, menu bars, text boxes, buttons, scroll bars, images, and text. The attributes and content of controls in the interface are defined using tags or nodes, such as XML tags. <textview> 、 <imgview> 、 <videoview>Nodes define the controls contained in the interface. A node corresponds to a control or property in the interface, and after parsing and rendering, the node is presented as the content visible to the user. In addition, many applications, such as hybrid applications, often contain web pages within their interfaces. A web page, also known as a webpage, can be understood as a special control embedded in the application interface. Web pages are source code written in a specific computer language, such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript (JS), etc. Web page source code can be loaded and displayed as user-readable content by a browser or a web page display component with browser-like functionality. The specific content contained in a webpage is also defined through tags or nodes in the webpage source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>To define the elements and attributes of a webpage.

[0282] The most common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0283] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

[0284] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0285] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if..." or "after..." or "in response to determining..." or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is detected" can be interpreted as meaning "if determining..." or "in response to determining..." or "when (the stated condition or event) is detected" or "in response to detecting (the stated condition or event)".

[0286] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0287] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A method for taking meeting minutes, characterized in that, The method includes: First attribute information of a first meeting record is obtained from a first application. The first meeting record is used to record the first content of the first meeting. The first attribute information is used to indicate the time or identifier of the first meeting. Based on the first attribute information, an association is established between the first meeting record and the first schedule on the second application, which is used to manage the schedule; Based on the aforementioned association, the user is provided with an access point to view the first meeting minutes on the second application, and / or provided with an access point to view the first schedule on the first application.

2. The method according to claim 1, characterized in that, The first schedule is a schedule created on the second application based on the first attribute information.

3. The method according to claim 1, characterized in that, The first schedule is selected from the schedules already created on the second application based on the first attribute information.

4. A method for taking meeting minutes, characterized in that, The method includes: Obtain schedule information from a second application, the schedule information including content information of a first schedule managed by the second application; Based on the schedule information, an association is established between the first meeting record on the first application and the first schedule. The first application is used to generate the first meeting record by recording the first content of the first meeting. Based on the aforementioned association, the user is provided with an access point to view the first meeting minutes on the second application, and / or provided with an access point to view the first schedule on the first application.

5. The method according to claim 4, characterized in that, The step of establishing the association between the first meeting record on the first application and the first schedule based on the schedule information specifically includes: Based on the schedule information, the user is provided with a schedule to be selected on the first application, the schedule to be selected including the first schedule; In response to the user's selection of the first schedule on the first application, an association is established between the first meeting record on the first application and the first schedule.

6. A method for taking meeting minutes, characterized in that, The method includes: After the first application generates a first meeting record by recording the first content of the first meeting, an association is established between the first meeting record and a first schedule on the second application, wherein the first schedule is a new schedule created on the second application based on the first meeting record; Based on the aforementioned association, the user is provided with an access point to view the first meeting minutes on the second application, and / or provided with an access point to view the first schedule on the first application.

7. The method according to claim 6, characterized in that, The process of establishing the association between the first meeting record and the first schedule on the second application specifically includes: In response to a first action by the user on the first application, an association is established between the first meeting record and the first schedule on the second application, wherein the first action is further used to trigger the creation of the first schedule on the second application.

8. The method according to any one of claims 1-7, characterized in that, Providing the user with an access point to view the first meeting minutes on the second application specifically includes: Obtain the first content of the first meeting record on the first application; The first content is displayed to the user on the second application.

9. The method according to any one of claims 1-7, characterized in that, Providing the user with an access point to view the first meeting minutes on the second application specifically includes: On the second application, a first link is displayed to the user, which is used to open an interface in the first application to view the first meeting record.

10. The method according to any one of claims 1-9, characterized in that, Providing the user with an entry point to view the first schedule on the first application specifically includes: Obtain the content information of the first schedule on the second application; The content information of the first schedule is displayed to the user on the first application.

11. The method according to any one of claims 1-9, characterized in that, Providing the user with an entry point to view the first schedule on the first application specifically includes: A second link is displayed to the user on the first application, the second link being used to open an interface in the second application to view the first schedule.

12. A meeting recording method, applied to a first electronic device, characterized in that, The first electronic device has a first application installed, and the first application logs in with a first account. The method includes: Receive an association instruction message, the association instruction message being used to instruct the second electronic device to establish an association between the first schedule and the first meeting record when logging in with the first account; The association is stored in the first application; Based on the aforementioned relationship, the user is provided with an entry point to view the first meeting minutes on the first application.

13. The method according to claim 12, characterized in that, The first electronic device is also equipped with a second application, and after receiving the association indication message, the method further includes: The association is stored in the second application; Based on the aforementioned relationship, the user is provided with an entry point to view the first schedule on the second application.

14. An electronic device, characterized in that, The electronic device includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program that, when executed by the processor, causes the electronic device to perform the method as described in any one of claims 1-13.

15. A computer storage medium, characterized in that, The computer storage medium stores a computer program that, when executed by a processor, causes the electronic device to perform the method as described in any one of claims 1-13.

16. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it causes the electronic device to perform the method as described in any one of claims 1-13.

Images