Information processing methods, devices, equipment and storage media

By automatically setting application reminders through receiving voice messages, the problem of cumbersome reminder message settings in existing technologies is solved, achieving efficient reminder message generation and task execution, and improving user experience.

CN117472459BActive Publication Date: 2026-11-17TENCENT CLOUD COMPUTING (BEIJING) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210861587.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-07-20
Publication Date
2026-11-17
Estimated Expiration
2042-07-20

AI Technical Summary

Technical Problem

The existing technology for setting application notification messages is cumbersome, consumes a lot of manual time, and has a poor user experience.

Method used

By receiving voice information, converting it into intent information, determining shortcut commands and launching corresponding applications, generating and pushing reminder messages, and automatically performing the target task.

Benefits of technology

It improves the efficiency of reminder message scheduling, especially for end users with visual impairments, thus enhancing the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117472459B_ABST
    Figure CN117472459B_ABST
Patent Text Reader

Abstract

This application discloses an information processing method, apparatus, device, and storage medium, applicable to fields such as cloud technology, computer technology, and blockchain technology. The method includes: in response to receiving voice information indicating the execution of a target task, converting the voice information into intent information; determining a shortcut command corresponding to the intent information and a first application corresponding to the shortcut command; launching the first application and converting the intent information into a reminder event through the first application, and transmitting the reminder event to a second application, so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target task, the reminder message being used to remind the user to execute the target task; and in response to the second application pushing the reminder message, executing the target task based on the first application. Using this application embodiment, reminder messages can be set for target tasks to remind the user to execute the target task at the corresponding reminder time, offering high applicability.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an information processing method, apparatus, device, and storage medium. Background Technology

[0002] With the widespread use of apps, they have become an indispensable part of people's lives. Using apps for entertainment, work, and communication has become a daily habit.

[0003] With the increasing popularity of applications, people often want to set reminders within these applications to remind them of important tasks. Current technology typically involves manually opening the calendar application and setting reminders for specific tasks at corresponding times. For example, setting a reminder to buy train tickets at 8:00 AM on June 20th in a calendar application. This method is cumbersome, consumes a significant amount of manual time, and provides a poor user experience. Summary of the Invention

[0004] This application provides an information processing method, apparatus, device, and storage medium that can efficiently set reminder messages for target matters to remind the execution of the target matters at the corresponding reminder time, and has high applicability.

[0005] On one hand, embodiments of this application provide an information processing method, the method comprising:

[0006] In response to receiving voice information indicating the execution of a target action, the voice information is converted into intent information;

[0007] Determine the shortcut command corresponding to the above intent information and the first application corresponding to the above shortcut command;

[0008] The first application is launched and the intent information is converted into a reminder event through the first application. The reminder event is then passed to the second application so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target matter. The reminder message is used to remind the execution of the target matter.

[0009] In response to the notification message pushed by the second application, the aforementioned target action is performed based on the first application.

[0010] On the other hand, embodiments of this application provide an information processing apparatus, which includes:

[0011] The information processing module is used to convert the received voice information, which is used to instruct the execution of a target matter, into intent information in response to receiving such voice information.

[0012] The program determination module is used to determine the shortcut command corresponding to the above intent information and the first application corresponding to the above shortcut command.

[0013] An event handling module is used to launch the first application and convert the intent information into a reminder event through the first application, and pass the reminder event to the second application, so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target matter. The reminder message is used to remind the execution of the target matter.

[0014] The task execution module is used to respond to the reminder message pushed by the second application and execute the target task based on the first application.

[0015] On the other hand, embodiments of this application provide an electronic device, including a processor and a memory, which are interconnected;

[0016] The aforementioned memory is used to store computer programs;

[0017] The processor described above is configured to execute the information processing method provided in the embodiments of this application when the computer program described above is invoked.

[0018] On the other hand, embodiments of this application provide a computer-readable storage medium storing a computer program that is executed by a processor to implement the information processing method provided in embodiments of this application.

[0019] On the other hand, embodiments of this application provide a computer program product, which includes a computer program that, when executed by a processor, implements the information processing method provided in embodiments of this application.

[0020] In this embodiment, a corresponding reminder message can be set in the second application by receiving voice information indicating the execution of a target task. After the second application pushes the reminder message, the target task is executed based on the first application. This improves the scheduling efficiency of reminder messages and provides a highly effective user experience for users with visual impairments. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating the information processing method provided in an embodiment of this application;

[0023] Figure 2 This is a schematic diagram of the interactive interface provided in the embodiments of this application;

[0024] Figure 3 This is a schematic diagram of a scenario for the appointment reminder interface provided in an embodiment of this application;

[0025] Figure 4 This is a schematic diagram of a scenario for the permission reminder interface provided in an embodiment of this application;

[0026] Figure 5 This is a schematic diagram of a scenario for displaying reminder messages provided in an embodiment of this application;

[0027] Figure 6 This is another scenario illustration of displaying reminder messages provided in the embodiments of this application;

[0028] Figure 7 This is a schematic flowchart of the information processing method provided in the embodiments of this application;

[0029] Figure 8 This is a schematic diagram of the structure of the information processing device provided in the embodiments of this application;

[0030] Figure 9 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0031] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0032] The information processing method provided in this application is applicable to any device capable of running applications, such as smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, and in-vehicle terminals. The specific application can be determined based on actual application scenario requirements and is not limited thereto. For example, the information processing method provided in this application can be applied to in-vehicle terminals in Intelligent Traffic Systems (ITS) or Intelligent Vehicle Infrastructure Cooperative Systems (IVICS) to enable applications in the in-vehicle terminal to remind and execute actions such as playing music, turning on the air conditioning, and starting navigation.

[0033] Intelligent Transportation Systems (ITS), also known as Intelligent Transportation Systems, effectively integrate advanced science and technology (information technology, computer technology, data communication technology, sensor technology, electronic control technology, automatic control theory, operations research, artificial intelligence, etc.) into transportation, service control, and vehicle manufacturing. This strengthens the connection between vehicles, roads, and users, thereby forming a comprehensive transportation system that ensures safety, improves efficiency, enhances the environment, and saves energy.

[0034] Intelligent vehicle-road cooperative systems, or vehicle-road cooperative systems for short, represent a development direction for Intelligent Transportation Systems (ITS). These systems utilize advanced wireless communication and next-generation internet technologies to implement comprehensive, real-time dynamic information exchange between vehicles and infrastructure. Based on the collection and fusion of dynamic traffic information across all times and spaces, they enable proactive vehicle safety control and collaborative road management, fully realizing effective coordination between people, vehicles, and roads. This ensures traffic safety, improves traffic efficiency, and ultimately forms a safe, efficient, and environmentally friendly road traffic system.

[0035] See Figure 1 , Figure 1 This is a flowchart illustrating the information processing method provided in an embodiment of this application. Figure 1 As shown, the information processing method provided in this application embodiment may specifically include the following steps:

[0036] Step S11: In response to receiving voice information for instructing the execution of a target task, the voice information is converted into intent information and the shortcut instruction corresponding to the intent information is determined.

[0037] In some feasible implementations, the voice information input by the target object is used to instruct the execution of a target task, such as downloading movie A, playing song B, or purchasing a mobile phone. The specific task can be determined based on the actual application scenario requirements and is not limited here.

[0038] Among these features, voice information input by the target object can be received through a smart voice assistant. For example, in response to receiving a wake-up message from the target object for the smart voice assistant, the smart voice assistant can be activated, and then the voice information input by the target object to instruct the execution of the target matter can be received through the smart voice assistant.

[0039] In some feasible implementations, after receiving voice information indicating the execution of a target task, the voice information can be converted into intent information, that is, the voice information can be converted into relevant data forms that can be used to represent the execution of the target task. For example, the voice information input by the target object can be parsed into IntentItem data, and the target task can be described based on the IntentItem data.

[0040] The process of converting voice information into intent information can also be implemented based on a smart voice assistant. For example, in response to receiving a wake-up message from the target object for the smart voice assistant, the smart voice assistant is launched, and then the voice information input by the target object is received through the smart voice assistant and converted into intent information.

[0041] In converting speech information into intent information, speech information can first be converted into text information based on natural language processing technology, and then the text information can be further converted into specific data language to obtain the corresponding intent information.

[0042] Step S12: Determine the shortcut corresponding to the intent information and the first application corresponding to the shortcut.

[0043] In some feasible implementations, after converting voice information into intent information, the shortcut command corresponding to the intent information can be determined.

[0044] Specifically, a target intent that matches the intent information can be determined from the intent set, and then the preset instruction corresponding to the target intent can be determined as the shortcut instruction corresponding to the intent information.

[0045] The intent set includes multiple intents, each corresponding to a specific task. For example, downloading a movie, playing music, and buying coffee each correspond to different intents, and each intent corresponds to a different preset instruction. Different tasks can be distinguished based on these preset instructions.

[0046] In this way, the intents supported by each application and the preset instructions corresponding to each intent can be preset. After determining the shortcut instructions corresponding to the intent information, the first application corresponding to the shortcut instructions can be determined, that is, the first application used to perform the target task can be determined.

[0047] The preset commands mentioned above include, but are not limited to, single-click, double-click, single-finger swipe, two-finger swipe, and custom gestures, etc. The specific commands can be determined based on the actual application scenario requirements and are not restricted here.

[0048] In determining the aforementioned shortcut commands, a target intent matching the intent information can be identified from the intent set based on a pre-created AccessibilityElement, and then the preset command corresponding to the target intent can be determined as the shortcut command corresponding to the intent information. Alternatively, it can be implemented based on other functional components, programs, etc., without limitation.

[0049] In some feasible implementations, for each application, at least one intent object can be pre-created for that application. Each intent object corresponds to an intent, that is, a task. Furthermore, each intent object is an entity object of the LoadCalendarIntent class, representing that the task corresponding to each intent object can have a corresponding reminder message set in the second application. For example, if the second application is a calendar application, then each intent object is an entity object of the LoadCalendarIntent class.

[0050] When creating an intent object, you can first create an intent file and configure relevant field information for the intent file, such as the business type of the corresponding matter, the title information of the reminder message, the content of the corresponding matter, and the reminder time of the reminder message. Then, you can compile the intent file with the configured field information to obtain the intent class for loading the second application.

[0051] The classification of business types can be determined based on the actual application scenario requirements and is not restricted here. Examples include ordering goods, downloading data, or categories such as movies, TV series, and novels.

[0052] The corresponding implementation content is used to describe the specific details of the matter. For example, if the matter is downloading a TV series, the content can be the name of the TV series, the conditions for downloading the TV series, or when to download it, etc. There are no restrictions here.

[0053] Furthermore, the `donateInteraction` method can be overridden to create an intent object corresponding to the intent file within the method, and initial values ​​can be set for the properties of the intent object so that the intent object corresponds to a certain matter, such as downloading a movie. The intent object can also be identified as an entity object of the intent class for loading the second application, thereby establishing an association between the intent object and the intent class for loading the second application, indicating that the matter corresponding to the intent object can be set with a corresponding reminder message in the second application.

[0054] In some feasible implementations, for each application, after creating the intent object corresponding to that application, the intent objects can be associated with the application so that the application supports each intent object.

[0055] Specifically, you can create an intent app extension for the application using the target option in Xcode, and then configure each intent object in the application's application configuration file (such as info.plist) to associate the intent objects created for the application with the application, thereby enabling the intent app extension for the application to support each intent object created for the application.

[0056] In this case, after determining the first application corresponding to the shortcut, if the intent program extension corresponding to the first application supports the intent corresponding to the shortcut, the first application can be launched based on the intent program extension corresponding to the first application.

[0057] Xcode is an integrated development environment (IDE) that runs on a specific operating system and is the fastest way to develop applications. Xcode has a unified interface design, and application coding, testing, and debugging can all be completed within a simple window. The corresponding source code of the application can be understood as the application's configuration file.

[0058] In some feasible implementations, when the first application is launched, if the extension UI component corresponding to the first application detects the interactive interface corresponding to the above intent information, the interactive interface is displayed.

[0059] The interactive interface includes prompts that remind users to schedule the desired action.

[0060] The interactive interface may also include relevant information about the first application, such as the name and icon of the first application, to prompt the first application to perform the target task.

[0061] like Figure 2 As shown, Figure 2 This is a schematic diagram of an interactive interface provided in an embodiment of this application. After receiving voice information input by the target object for downloading movie A, the voice information can be converted into intent information, and the shortcut command corresponding to the intent information and the first application corresponding to the shortcut command can be determined. After the extended interactive interface component corresponding to the first application detects the interactive interface corresponding to downloading movie A, the interactive interface is displayed.

[0062] The interactive interface displays the name of the first application, "Ai Movie," along with a prompt message. The prompt message and the name of the first application prompt the user to schedule an appointment to download movie A using the "Ai Movie" application.

[0063] If the above intent information is used to instruct the download of movie A, then this prompt information is used to prompt the user to schedule a download of movie A.

[0064] Furthermore, upon receiving a confirmation action for the prompt message, the first application can be launched based on the extended interactive interface component.

[0065] The extended interactive interface components corresponding to the first application can be pre-configured.

[0066] Specifically, you can create an extended interactive interface component for the application using the `target` option in Xcode, and then associate each intent object of the first application with this extended interactive interface component. You can also pre-configure the corresponding interactive interface for each intent object to provide reminders for different intents.

[0067] If the interactive interface corresponding to each intent is not pre-configured for the first application, the first application can be launched directly based on the intent program extension corresponding to the first application.

[0068] Step S13: Launch the first application, convert the intent information into a reminder event through the first application, and pass the reminder event to the second application.

[0069] In some feasible implementations, after launching the first application, the intent information can be converted into event data in a data structure supported by the second application, and then an alert event can be constructed based on the converted event data.

[0070] Specifically, the intent information can be parsed into event data in a data structure supported by the second application based on the msgSendCenter function unit in the first application.

[0071] Furthermore, through the message sending center functional unit, an INShort object can be created by calling the initWithIntent method based on the intent object corresponding to the intent information (i.e., the intent object corresponding to the intent that matches the intent information). The intent information is then passed to the message sending center functional unit through the INShort object, and the intent information is converted into event data in a data structure supported by the second application.

[0072] The INshort object is used to convey intent information.

[0073] In the case where the second application is a calendar application, the aforementioned data structure can be an EKEvent data structure.

[0074] Before converting intent information into event data, a reminder interface can be displayed to further prompt the user to set up a reminder in the second application to perform the target task. Upon receiving confirmation from the target user regarding the reminder interface, the process of converting intent information into event data can be executed.

[0075] like Figure 3 As shown, Figure 3 This is a schematic diagram of a scenario for the appointment reminder interface provided in an embodiment of this application. For example... Figure 3 As shown, if the intent information corresponding to the target object is to download a movie, after launching an application that supports downloading movies, a reminder interface can be displayed to prompt the target object whether to add a reminder message in the calendar (the second application). Then, if the target object confirms that a reminder message has been added to the calendar, the target object's intent information is converted into event data.

[0076] The appointment reminder interface can be loaded through the INUIAddVoiceShortcutViewController interface controller, and the currently displayed interface will be overwritten during the loading process.

[0077] Specifically, if the first application is launched via a cold start, the overwritten interface is the interface displayed after the first application starts. If the first application is launched via a warm start, the overwritten interface is the interface displayed before the first application starts.

[0078] When displaying the appointment reminder interface, the processes and tasks being performed on the terminal where the first application is located can be paused or interrupted through relevant protocol methods, such as stopping audio and video playback, pausing data downloads, etc. The specific method can be determined based on the actual application scenario requirements and is not limited here.

[0079] Furthermore, after converting intent information into event data and constructing an alert event based on that data, a permission reminder interface can be displayed. This interface prompts the user to obtain settings permissions for the second application. Once settings permissions for the second application are obtained, an alert event can be constructed based on the event data.

[0080] After receiving a reminder event, the reminder event can be passed to a second application, so that the second application can generate a reminder message based on the reminder event to remind the target task to be performed, and push the reminder message at the reminder time of the target task.

[0081] When creating a notification event, a permission reminder interface can be displayed. This permission reminder interface is used to prompt for permission to grant settings permissions to the second application, that is, permission to add notification messages to the second application.

[0082] The permission reminder interface is pre-configured in the program configuration file (such as info.plist) of the first application, and can be displayed through the relevant configuration information when the permission reminder interface needs to be displayed.

[0083] For example, if the second application is a calendar application, when creating a reminder event, an EKEventStore object can be created first, and the permission reminder interface can be displayed through the EKEventStore object to obtain the calendar application's settings permissions.

[0084] Once you've determined that you need to obtain settings permissions from the calendar application, you can call the `requestAccessToEntityType` method to request these permissions. If the calendar application returns a `YES` field in the granted field and no `error` field is returned, it means the calendar application has agreed to grant settings permissions. You can then call the `eventWithEventStore` method to pass the intent information to an `EKEventStore` to create an `EKEvent` object, which will become the reminder event.

[0085] See Figure 4 , Figure 4 This is a schematic diagram of a permission reminder interface provided in an embodiment of this application. For example... Figure 4 As shown, when the second application is a calendar application, a permission reminder interface can be displayed before constructing the reminder event to prompt for obtaining settings permissions from the calendar application. Upon receiving confirmation from the permission reminder interface (such as clicking the "Yes" button), the relevant methods are invoked to obtain settings permissions from the calendar application.

[0086] In some feasible implementations, the aforementioned reminder event includes one or more of the following: the content of the target matter, the title information of the reminder message, the execution method of the target matter, the display position of the reminder message, the display time range of the reminder message, the reminder time of the reminder message, or the business type of the target matter.

[0087] The content of the target item is used to describe the specific details of the item. For example, if the item is to download a TV series, the content can be the name of the TV series, the conditions for downloading the TV series, or when to download it, etc. There are no restrictions here.

[0088] The title of the reminder message indicates the specific matter of the target task, such as downloading a TV series or opening a presentation; there are no restrictions on this. The title of the reminder message can be determined based on the intent information corresponding to the voice message.

[0089] The execution methods for the target task include, but are not limited to, downloading, opening, and displaying, etc., and can be determined based on the actual application scenario requirements, without any restrictions here. The execution method for the target task can be determined based on the intent information corresponding to the voice information.

[0090] The display position of the reminder message refers to the specific location on the terminal where the second application is located when it pushes the reminder message. This could be the top or center of the terminal's display screen, etc., and there are no restrictions. Different applications used to perform different tasks can correspond to different display positions, or the display position of the reminder message can be a preset display position of the second application. The specific location can be determined based on the actual application scenario requirements, and there are no restrictions here.

[0091] The display time range of the reminder message indicates the duration for which the reminder message will be displayed on the terminal, such as 10 minutes. The display time range can be determined by the intent information corresponding to the voice message, or it can be set by the target object during the creation of the reminder event, or it can be the default display time range of the second application. The specific time range can be determined based on the actual application scenario requirements, and there are no restrictions here.

[0092] The classification of business types can be determined based on the actual application scenario requirements and is not limited here. Examples include ordering goods, downloading data, or categories such as movie genres, TV series genres, and novels. Business types can be determined through the intent information corresponding to the voice information. The business type and execution method of the target matter can be used to characterize the specific operation of the target matter. For example, if the business type is "movie" and the execution method is "download," then the specific operation of the target matter can be determined as downloading a movie.

[0093] The reminder time is the time when the second application pushes the reminder message, and the reminder time can be determined based on the intent information corresponding to the voice information.

[0094] If the intent information corresponding to the voice message does not indicate a reminder time, meaning the target object has not indicated a reminder time via voice message, the reminder event may not include a reminder time or the relevant fields for the reminder time may be set to empty. In this case, after launching the first application, the target reminder service module corresponding to the intent information can be identified, such as a reminder service module for downloading a new movie, downloading a TV series, or reserving concert tickets, and this target service module can be registered with the message sending center functional unit. This allows the first application to instruct the second application to generate and push a reminder message based on the reminder event when the target item meets the reminder conditions. For example, if the intent information corresponding to the voice message is to download singer C's new album, then the first application will instruct the second application to generate and push a reminder message based on the reminder event when singer C's new album becomes available for download.

[0095] After creating a reminder event, you can call the saveEvent:span method to save the reminder event and set a label for it. This label is used to indicate the corresponding target item, that is, the target item that the reminder event is used to remind can be determined based on the label.

[0096] After creating a notification event, the notification event can be saved to the storage space of the terminal where the first application and the second application are located, or to a blockchain, database, distributed version control system (Git) data warehouse, cloud storage, or relational storage server that can be directly accessed by the terminal. The specific method can be determined based on the actual application scenario requirements and is not restricted here.

[0097] Specifically, the second application can generate reminder messages in advance based on reminder events, and then store the reminder messages. When a reminder message needs to be pushed, it can be directly retrieved and pushed, thus improving the efficiency of message push.

[0098] In short, a database can be viewed as an electronic filing cabinet—a place to store electronic documents. In this application, it can be used to store reminder events and / or reminder messages. Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. In this application, each data block in the blockchain can store reminder events and / or reminder messages. Cloud storage is a new concept that extends and develops from cloud computing. It refers to the collaborative storage of reminder events and / or reminder messages by using cluster applications, grid technology, and distributed storage file systems to aggregate a large number of various types of storage devices (also called storage nodes) in a network through application software or application interfaces.

[0099] The data processing procedures involved in the embodiments of this application, such as converting voice information into intent information, converting intent information into event data, and constructing reminder events, can be performed based on cloud computing and other methods. Cloud computing is a product of the integration and development of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing. Cloud computing can improve data processing efficiency.

[0100] Step S14: In response to the push notification message from the second application, perform the target task based on the first application.

[0101] In some feasible implementations, the second application can generate and push a reminder message at the reminder time of the reminder event, such as displaying the reminder message at the corresponding display position on the terminal based on the display position in the reminder event, or the second application can generate a reminder message at the reminder time of the reminder event and convert the reminder message into a reminder voice for prompting via voice. The specific implementation can be determined based on the actual application scenario requirements and is not limited here.

[0102] Furthermore, after the second application pushes a notification message, the first application can be triggered to perform the target task.

[0103] Alternatively, after the second application pushes a notification message, the target task can be performed based on the first application in response to a confirmation action on the notification message.

[0104] like Figure 5 As shown, Figure 5 This is a schematic diagram of a scenario for displaying a reminder message provided in an embodiment of this application. When the target task is to download movie A, a reminder message "Start downloading movie A?" pushed by a second application can be used to confirm with the target whether to perform the target task. After receiving confirmation from the target, the download of movie A can begin using the first application.

[0105] When the first application executes the target task, it can also call the setCalendar method to obtain the corresponding reminder information, thereby enabling the first application to execute the target task based on the reminder information.

[0106] In some feasible implementations, when creating a reminder event for the second application, a pending event corresponding to the target matter can also be created for the first application. Then, after the second application pushes the reminder message, the first application executes the pending event to complete the target matter.

[0107] Specifically, when creating an event to be executed for the first application, the intent information corresponding to the voice information can be converted into event data in a data structure supported by the first application, and then the event to be executed can be constructed based on the event data.

[0108] Alternatively, the event to be executed can be constructed based on the intent object corresponding to the above intent information. The specific details can be determined based on the actual application scenario requirements, and there are no restrictions here.

[0109] The pending events may include information such as the content of the target event, the execution method of the target event, the business type of the target event, and the execution time of the target event, so that the first application can execute the pending events at the same time as the second application pushes a reminder message.

[0110] Specifically, for any event among the pending events of the first application and the corresponding reminder events of the second application, after the event is constructed, the fields of the event can be transformed by classification, so that the corresponding application can recognize the event and have the ability to execute the event.

[0111] In some feasible implementations, in response to the query operation of the target object, the various reminder messages stored in the second application can be determined, and then each reminder message and its corresponding reminder time can be displayed, thereby facilitating the query of each reminded item.

[0112] The above query operation can be triggered by voice query of the target object, or by preset shortcut command, or by the target object after searching for a second application. The specific method can be determined based on the actual application scenario requirements and is not limited here.

[0113] like Figure 6 As shown, Figure 6 This is another scenario illustration of displaying reminder messages provided in the embodiments of this application. When the second application is a calendar, when a search operation on the calendar by the target object is detected, reminder messages for various items corresponding to the second application can be obtained, and then each reminder message can be displayed to the target object. Each reminder message may include information such as the corresponding reminder time and the content of the item, which is not limited here.

[0114] In some feasible implementations, after creating a reminder event for the second application, an update operation can be performed in response to the reminder event, and the update information corresponding to the update operation can be determined.

[0115] The updated information can be input by the target object through a second application or by the target object through voice input. The specific method can be determined based on the actual application scenario requirements and is not limited here.

[0116] The aforementioned update information is used to indicate the items that need to be updated, such as one or more of the following: the content of the target item, the title information of the reminder message, the execution method of the target item, the display position of the reminder message, the display time range of the reminder message, the reminder time of the reminder message, or the business type of the target item.

[0117] For example, if the update information above indicates that the display time interval needs to be changed to 5 minutes, then the field corresponding to the execution method in the corresponding reminder event can be adjusted to change it to 5 minutes.

[0118] In this embodiment of the application, the first application and the second application run on the same terminal, and the second application can be an application with message push function, such as a calendar application, a memo application, etc. The specific application can be determined based on the actual application scenario requirements, and there are no restrictions here.

[0119] The following is combined with Figure 7 The information processing method provided in the embodiments of this application is illustrated by example. Figure 7 This is a schematic diagram of the flow framework of the information processing method provided in the embodiments of this application. For example... Figure 7As shown, for each application, at least one intent object can be pre-created for that application. Each intent object corresponds to an intent, that is, a task. Furthermore, each intent object is an entity object of the calendar application's intent class, used to indicate that the task corresponding to each intent object can have a corresponding reminder message set in the calendar application.

[0120] For each application, after creating the intent objects corresponding to that application, you can associate each intent object with the application to make the application support each intent object. Specifically, you can create an intent app extension for that application through the target option in Xcode, and then configure each intent object in the application's application configuration file (such as info.plist) to associate the intent objects created for that application with that application, thereby enabling the intent app extension for that application to support each intent object created for that application.

[0121] Simultaneously, an extended interactive interface component is created for each application, and each intent object corresponding to the application is associated with this extended interactive interface component. A corresponding interactive interface is pre-configured for each intent object to provide appointment prompts for different intents. Additionally, a message sending center functional unit is created for each application to parse the corresponding intent information into event data.

[0122] After receiving target voice information instructing the execution of a certain task, the voice information can be converted into target intent information, such as parsing the voice information input by the target object into IntentItem data. After converting the target voice information into target intent information, the corresponding shortcut command can be determined.

[0123] If the extended UI component of the target application corresponding to the shortcut detects the UI corresponding to the target intent information, the UI is displayed to prompt the user to schedule the task. The target application is launched after a confirmation action is detected for this UI. If the extended UI component of the target application corresponding to the shortcut detects the UI corresponding to the target intent information, the target application is launched directly.

[0124] After the first application is launched, the message sending center functional unit can call the initWithIntent method to create an INShort object based on the target intent information. The target intent information is then passed to the message sending center functional unit through the INShort object, and then the target intent information is converted into event data EKEvent, a data structure supported by the calendar application. Thus, reminder events can be built based on the event data.

[0125] After receiving the target reminder event, the target reminder event can be passed to the calendar application, so that the calendar application can generate a target reminder message to remind the user to perform the task based on the target reminder event, push the target reminder message at the reminder time of the task, and perform the task based on the target application.

[0126] In this embodiment, a corresponding reminder message can be set in the second application by receiving voice information instructing the execution of a target task. After the second application pushes the reminder message, the target task is executed based on the first application. This improves the efficiency of reminder message scheduling and provides a superior user experience for users with visual impairments. Furthermore, by storing reminder events or messages in storage space associated with the terminal (such as local storage), reminder events or messages can be retrieved promptly to ensure the accuracy of the pushed reminder messages.

[0127] See Figure 8 , Figure 8 This is a schematic diagram of the structure of the information processing apparatus provided in the embodiments of this application. The information processing provided in the embodiments of this application includes:

[0128] The information processing module 81 is used to convert the received voice information, which is used to instruct the execution of a target matter, into intent information in response to receiving the voice information.

[0129] The program determination module 82 is used to determine the shortcut command corresponding to the above intent information and the first application corresponding to the above shortcut command.

[0130] Event processing module 83 is used to start the first application and convert the intent information into a reminder event through the first application, and pass the reminder event to the second application, so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target matter, and the reminder message is used to remind the execution of the target matter;

[0131] The task execution module 84 is used to execute the target task based on the first application in response to the reminder message pushed by the second application.

[0132] In some feasible implementations, the above-described procedure determining module 82 is used for:

[0133] The target intent that matches the above intent information is determined from the intent set, which includes multiple intents, each of which corresponds to a matter;

[0134] The preset command corresponding to the above target intent is determined as the shortcut command corresponding to the above intent information.

[0135] In some feasible implementations, the event handling module 83 described above is used for:

[0136] In response to the extended interactive interface component corresponding to the first application detecting the interactive interface corresponding to the intent information, the interactive interface is displayed. The interactive interface includes prompt information, which is used to prompt the scheduled execution of the target matter.

[0137] In response to the confirmation action for the above prompt, the first application is launched.

[0138] In some feasible implementations, the event handling module 83 described above is used for:

[0139] The intent information is converted into event data using the first application and the data structure supported by the second application.

[0140] The alert event is constructed based on the above event data.

[0141] In some feasible implementations, the event handling module 83 described above is used for:

[0142] The permission reminder interface is displayed to prompt for obtaining setting permissions from the second application.

[0143] In response to obtaining the settings permissions of the aforementioned second application, an alert event is constructed based on the aforementioned event data.

[0144] In some feasible implementations, the aforementioned reminder event includes at least one of the following: the content of the target matter, the execution method of the target matter, the title information of the reminder message, the display position of the reminder message, the display time interval of the reminder message, the reminder time of the reminder message, or the business type of the target matter.

[0145] In some feasible implementations, the event handling module 83 described above is used for:

[0146] In response to the update operation for the above-mentioned reminder event in the second application, determine the update information corresponding to the update operation;

[0147] The above-mentioned reminder event has been updated based on the updated information.

[0148] In specific implementation, the above-mentioned device can perform the above-described actions through its built-in functional modules. Figure 1 The implementation methods provided for each step are detailed in the above-mentioned implementation methods, and will not be repeated here.

[0149] See Figure 9 , Figure 9 This is a schematic diagram of the structure of the electronic device provided in an embodiment of this application. For example... Figure 9 As shown, the electronic device 900 in this embodiment may include: a processor 901, a network interface 904, and a memory 905. Furthermore, the electronic device 900 may also include: an object interface 903, and at least one communication bus 902. The communication bus 902 is used to implement communication between these components. The object interface 903 may include a display screen and a keyboard; optionally, the object interface 903 may also include a standard wired interface or a wireless interface. The network interface 904 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 905 may be a high-speed RAM or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory 905 may also be at least one storage device located remotely from the aforementioned processor 901. Figure 9 As shown, the memory 905, which is a computer-readable storage medium, may include an operating system, a network communication module, an object interface module, and a device control application.

[0150] exist Figure 9 In the illustrated electronic device 900, the network interface 904 provides network communication functionality; the object interface 903 is primarily used to provide an input interface for objects; and the processor 901 can be used to call the device control application program stored in the memory 905 to achieve:

[0151] In response to receiving voice information indicating the execution of a target action, the voice information is converted into intent information;

[0152] Determine the shortcut command corresponding to the above intent information and the first application corresponding to the above shortcut command;

[0153] The first application is launched and the intent information is converted into a reminder event through the first application. The reminder event is then passed to the second application so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target matter. The reminder message is used to remind the execution of the target matter.

[0154] In response to the notification message pushed by the second application, the aforementioned target action is performed based on the first application.

[0155] In some feasible implementations, the processor 901 described above is used for:

[0156] The target intent that matches the above intent information is determined from the intent set, which includes multiple intents, each of which corresponds to a matter;

[0157] The preset command corresponding to the above target intent is determined as the shortcut command corresponding to the above intent information.

[0158] In some feasible implementations, the processor 901 described above is used for:

[0159] In response to the extended interactive interface component corresponding to the first application detecting the interactive interface corresponding to the intent information, the interactive interface is displayed. The interactive interface includes prompt information, which is used to prompt the scheduled execution of the target matter.

[0160] In response to the confirmation action for the above prompt, the first application is launched.

[0161] In some feasible implementations, the processor 901 described above is used for:

[0162] The intent information is converted into event data using the first application and the data structure supported by the second application.

[0163] The alert event is constructed based on the above event data.

[0164] In some feasible implementations, the processor 901 described above is used for:

[0165] The permission reminder interface is displayed to prompt for obtaining setting permissions from the second application.

[0166] In response to obtaining the settings permissions of the aforementioned second application, an alert event is constructed based on the aforementioned event data.

[0167] In some feasible implementations, the aforementioned reminder event includes at least one of the following: the content of the target matter, the execution method of the target matter, the title information of the reminder message, the display position of the reminder message, the display time interval of the reminder message, the reminder time of the reminder message, or the business type of the target matter.

[0168] In some feasible implementations, the processor 901 described above is used for:

[0169] In response to the update operation for the above-mentioned reminder event in the second application, determine the update information corresponding to the update operation;

[0170] The above-mentioned reminder event has been updated based on the updated information.

[0171] It should be understood that in some feasible implementations, the processor 901 described above may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. The memory may include read-only memory and random access memory, and provides instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information.

[0172] In specific implementation, the aforementioned electronic device 900 can perform the above-described actions through its built-in functional modules. Figure 1 The implementation methods provided for each step are detailed in the above-mentioned implementation methods and will not be repeated here.

[0173] This application also provides a computer-readable storage medium storing a computer program that is executed by a processor to implement... Figure 1 The methods provided in each step are detailed in the implementation methods provided in the above steps, and will not be repeated here.

[0174] The aforementioned computer-readable storage medium can be an internal storage unit of the apparatus or electronic device provided in any of the foregoing embodiments, such as a hard disk or memory of the electronic device. The computer-readable storage medium can also be an external storage device of the electronic device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device. The aforementioned computer-readable storage medium can also include magnetic disks, optical disks, read-only memory (ROM), or random access memory (RAM), etc. Furthermore, the computer-readable storage medium can include both internal storage units and external storage devices of the electronic device. The computer-readable storage medium is used to store the computer program and other programs and data required by the electronic device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0175] This application provides a computer program product, which includes a computer program that is executed by a processor. Figure 1 The methods provided for each step in the process.

[0176] The terms "first," "second," etc., used in the claims, description, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or electronic device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or electronic devices. References to "embodiment" herein mean that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The presentation of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments. The term "and / or" as used in the description and appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0177] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Those skilled in the art can implement the described functions using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

[0178] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. An information processing method characterized by comprising: The method includes: In response to receiving voice information indicating the execution of a target task, the voice information is converted into intent information, wherein the intent information is a data format representing the execution of the target task; Determine the shortcut command corresponding to the intent information and the first application corresponding to the shortcut command; In response to the extended interactive interface component corresponding to the first application detecting the interactive interface corresponding to the intent information, the interactive interface is displayed. The interactive interface includes prompt information, which is used to prompt the scheduled execution of the target matter. In response to a confirmation operation on the prompt message, the first application is launched; The appointment reminder interface is displayed, which is used to prompt the user to set a reminder message in the second application to remind them to perform the target task. In response to the confirmation operation on the appointment reminder interface, the intent information is converted into event data in a data structure supported by the second application through the first application. A reminder event is constructed based on the event data and transmitted to the second application so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target matter. The reminder message is used to remind the execution of the target matter. In response to the notification message pushed by the second application, the target action is performed based on the first application.

2. The method of claim 1, wherein, The method for determining the shortcut command corresponding to the intent information includes: The target intent that matches the intent information is determined from the intent set, the intent set including multiple intents, each intent corresponding to a matter; The preset command corresponding to the target intent is determined as the shortcut command corresponding to the intent information.

3. The method according to claim 1, characterized in that, The method further includes: When creating a reminder event for the second application, an event to be executed corresponding to the target item is also created for the first application; The step of executing the target matter based on the first application includes: executing the event to be executed to complete the target matter.

4. The method according to claim 1, characterized in that, The construction of the reminder event based on the event data includes: The permission reminder interface is used to prompt for obtaining setting permissions for the second application; In response to obtaining the settings permission of the second application, a reminder event is constructed based on the event data.

5. The method according to claim 1, characterized in that, The reminder event includes at least one of the following: the content of the target matter, the execution method of the target matter, the title information of the reminder message, the display position of the reminder message, the display time range of the reminder message, the reminder time of the reminder message, or the business type of the target matter.

6. The method according to claim 1, characterized in that, The method further includes: In response to an update operation for the reminder event in the second application, determine the update information corresponding to the update operation; The reminder event is updated based on the updated information.

7. An information processing device, characterized in that, The device includes: The information processing module is configured to, in response to receiving voice information indicating the execution of a target matter, convert the voice information into intent information, wherein the intent information is a data format representing the execution of the target matter; A program determination module is used to determine the shortcut command corresponding to the intent information and the first application corresponding to the shortcut command; An event handling module is configured to: respond to the extended interactive interface component corresponding to the first application detecting the interactive interface corresponding to the intent information; display the interactive interface, which includes prompt information for reminding the user to schedule the execution of the target matter; launch the first application in response to a confirmation operation on the prompt information; display a scheduling reminder interface for prompting the user to set a reminder message in a second application to remind the user to execute the target matter; and, in response to a confirmation operation on the scheduling reminder interface, convert the intent information into event data supported by the second application through the first application, construct a reminder event based on the event data, and transmit the reminder event to the second application so that the second application generates a reminder message based on the reminder event and pushes the reminder message at the reminder time of the target matter, the reminder message being used to remind the user to execute the target matter. The task execution module is used to execute the target task based on the first application in response to the reminder message pushed by the second application.

8. The apparatus according to claim 7, characterized in that, The program determination module is used for: The target intent that matches the intent information is determined from the intent set, the intent set including multiple intents, each intent corresponding to a matter; The preset command corresponding to the target intent is determined as the shortcut command corresponding to the intent information.

9. The apparatus according to claim 7, characterized in that, The event handling module is also used for: When creating a reminder event for the second application, an event to be executed corresponding to the target item is also created for the first application; The step of executing the target matter based on the first application includes: executing the event to be executed to complete the target matter.

10. The apparatus according to claim 7, characterized in that, The event handling module is used for: The permission reminder interface is used to prompt for obtaining setting permissions for the second application; In response to obtaining the settings permission of the second application, a reminder event is constructed based on the event data.

11. The apparatus according to claim 7, characterized in that, The reminder event includes at least one of the following: the content of the target matter, the execution method of the target matter, the title information of the reminder message, the display position of the reminder message, the display time range of the reminder message, the reminder time of the reminder message, or the business type of the target matter.

12. The apparatus according to claim 7, characterized in that, The event handling module is used for: In response to an update operation for the reminder event in the second application, determine the update information corresponding to the update operation; The reminder event is updated based on the updated information.

13. An electronic device, characterized in that, It includes a processor and a memory, which are interconnected; The memory is used to store computer programs; The processor is configured to perform the method as described in any one of claims 1 to 6 when the computer program is invoked.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is executed by a processor to implement the method of any one of claims 1 to 6.

15. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Reminding method and device of automatic generation of event

    CN106022725A

  • Message reminding method and device

    CN108737636A