Memory information management method and device

Abstract

A memory information management method and a device. The method comprises: an electronic device detecting a first operation of a user, wherein the first operation is used for instructing to memorize target content described in a natural language; and then obtaining memory information on the basis of the first operation, wherein the memory information comprises the target content carried by structured information. By means of the described method, memory information of a user can be efficiently managed by means of an electronic device, thereby facilitating the user's memorization and utilization.

Description

A method and device for managing memory information

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410801365.8, filed on June 20, 2024, entitled "A Method and Device for Managing Memory Information", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of electronic device technology, and in particular to a method and device for managing memory information. Background Technology

[0004] With the rapid development of society, electronic devices such as mobile phones are becoming increasingly common. These devices not only have communication functions but also powerful processing capabilities, storage capacity, and camera functions. Electronic devices utilize operating systems (such as HarmonyOS). The operating system executes corresponding applications, allowing users to use electronic devices to make calls, send text messages, browse the web, and store information. For example, in the current conversation scenario, to prevent forgetting useful user conversation information (or content), the user needs to memorize (record) and store the received conversation information via their mobile phone for later retrieval and recall.

[0005] However, current implementations typically record and display user-remembered information in natural language (or plain text), lacking efficient management of this information. This hinders user memorization and use (e.g., storing, retrieving, and accessing information). Therefore, achieving efficient management of user-remembered information is a pressing issue that needs to be addressed. Summary of the Invention

[0006] This application provides a method and device for managing memory information. The method is used to achieve efficient management of user memory information, making it easier for users to remember and use.

[0007] In a first aspect, embodiments of this application provide a method for managing memory information, applied to electronic devices (or terminal devices), including but not limited to personal computers, server computers, handheld or laptop devices, mobile devices (such as mobile phones, tablets, etc.), in-vehicle computers, smartwatches, televisions, and other electronic devices with display screens; the method can be executed by the electronic device or by a corresponding component of the electronic device (e.g., a chip, a chip system, or a circuit, etc.). Taking the method being executed by an electronic device as an example, the method may include: the electronic device detecting a first operation by a user, the first operation being used to instruct the memory to store target content described in natural language; and then the electronic device obtaining memory information based on the first operation, the memory information including target content carried by structured information.

[0008] In this embodiment of the application, the target content described in natural language can also be referred to as the user's unstructured memory information. In the above, the memory information obtained by the electronic device based on the first operation includes target content carried by structured information; therefore, this memory information can be referred to as structured memory information.

[0009] In this application, the electronic device detects a first user action, which instructs the user to memorize target content described in natural language. The electronic device then obtains the memorized information based on the first action, which includes the target content carried by structured information. This method allows for efficient management of the user's memorized information through the electronic device, facilitating memorization and use.

[0010] In one possible implementation, the structured information includes multiple tags and multiple sub-contents corresponding to each of the tags.

[0011] In this application embodiment, the plurality of labels may indicate, but are not limited to, indicating at least one of the following:

[0012] Time, place, people, things, actions, states, attributes, and relationships.

[0013] The meanings of the above labels are as follows:

[0014] (1) Time can refer to a specific time point (e.g., 7:00 PM), a date (e.g., May 3), a time period (e.g., 7:00 AM to 8:00 AM), a duration (e.g., from May 3, 2024 to June 3, 2024), a cycle (e.g., once a year), etc.

[0015] (2) Location can refer to geographical location, such as the doorstep of home, restaurant, school, hospital, etc.

[0016] (3) People can refer to related people, participants, etc.

[0017] (4) "Objects" can refer to real objects (such as mobile phones, stools, scenery, etc.) or virtual objects (such as phone numbers, email addresses, etc.).

[0018] (5) Actions can refer to user behavior, such as being in a meeting, running, etc.

[0019] (6) State can refer to the form that a person or thing exhibits (e.g., something is a liquid, something is a rectangle, something is still, etc.), and it can also refer to the progress of something (e.g., work has been completed, work is being carried out, etc.).

[0020] (7) Attributes can refer to the unique or non-unique characteristics or features of a person or thing; the attributes of things include color, shape, weight, etc., and the attributes of people include personality, ability, etc.; attributes can also refer to the general term for the same type of people or things.

[0021] (8) Relationship can refer to the connection or function between any one or more of people, things, or objects. For example, Zhang San and I are relatives, the computer is mine, and the application is installed in electronic devices.

[0022] In this embodiment of the application, the sub-content corresponding to a tag can refer to the specific information or content corresponding to the tag. For example, if the tag is time, then 8:00 AM is the sub-content corresponding to time. As another example, if the tag is a person, then "my mother" is the sub-content corresponding to that tag.

[0023] For example, if the target content based on natural language description is "Please help me remember that my mother's birthday is December 28th", the target content carried by the electronic device based on the first operation and structured information can be "My mother's birthday is December 28th".

[0024] In one possible implementation, the structured information may further include a scene type, which is bound to a set of tags from the plurality of tags. This set of tags may be some or all of the plurality of tags. This implementation allows for scene classification of the memory information, facilitating efficient management of the memory information.

[0025] In the embodiments of this application, the above-mentioned scenario types may be, but are not limited to, important days, cards, frequently used addresses, or events.

[0026] For example, for the "important day" scenario type, a set of tags can be bound to attributes, people, and time. The content corresponding to these tags can be birthday (i.e., the content corresponding to the attribute), "my mother" (i.e., the content corresponding to the person), and "December 28th" (i.e., the content corresponding to the time).

[0027] For example, for the scenario type of "card and certificate", a set of tags can be bound to attributes, people, and time. The content corresponding to these tags are "ID card", "me", and "effective date November 3, 2023, expiration date November 3, 2033".

[0028] For example, for the scenario type of "frequently used address", a set of tags can be bound to attributes, people, and locations, and the content corresponding to these tags are "home address", "my" and "28 Renmin Road", respectively.

[0029] For example, for the scenario type of "event", a set of tags can be bound to action, person, time and location, and the content corresponding to these tags are "going out to eat", "me", "8 o'clock" and "restaurant".

[0030] In one possible implementation, the multiple tags also include a target application or target application type associated with the target content. This approach allows users to more conveniently query and use the information they need by leveraging the association between the target content and the application or application type.

[0031] For example, the target application can be an application program (APP) on an electronic device, such as Taobao, JD.com, etc., and the target application type can be the type of application, such as shopping APP, social APP, etc.

[0032] In this embodiment of the application, the target application may include a first application and a second application, wherein the first application is an application that was previously installed on the electronic device and has now been deleted, and the second application is an application that is currently installed on the electronic device. The first application and the second application are of the same type.

[0033] In one possible implementation, the memory information is displayed to the user in the form of cards. This approach allows the electronic device to intuitively present the memory information to the user in card format, making it more convenient for the user to access and use the information, resulting in a better user experience.

[0034] In one possible implementation, the card includes an entry point for the user to access the target application (e.g., a user-operable button displayed on the card). This implementation allows users to quickly access and use the target application through the entry point on the card, resulting in convenient operation and a better user experience.

[0035] In one possible implementation, at least one of the aforementioned tags, sub-content, and scene types is user-editable or searchable. This implementation allows users to edit or search for content in a more flexible, convenient, and efficient manner.

[0036] In one possible implementation, the electronic device obtains the memory information by: generating the memory information; or receiving the memory information from a server. This implementation enables the electronic device to effectively obtain the memory information.

[0037] Secondly, embodiments of this application provide a device comprising multiple functional modules (e.g., a communication module, a storage module, a display module, a processing module, etc.); the multiple functional modules interact to implement the methods executed by the electronic devices in the first aspect and its various embodiments described above. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations.

[0038] Thirdly, embodiments of this application provide a device including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the device is running, the at least one processor executes the method executed by the electronic device described in the first aspect and its various embodiments.

[0039] Fourthly, embodiments of this application provide a program product that, when run on a device, causes the device to execute the method executed by the electronic device in any of the above aspects and their respective embodiments.

[0040] Fifthly, embodiments of this application provide a readable storage medium storing a program that, when executed by a device, causes the device to perform the method executed by the electronic device in any of the above aspects and embodiments.

[0041] Sixthly, embodiments of this application provide a chip for reading a program stored in a memory and executing the method executed by the electronic device in any of the above aspects and embodiments.

[0042] In a seventh aspect, embodiments of this application provide a chip system including a processor for supporting a device in implementing the methods executed by the electronic devices in any of the above aspects and embodiments. In one possible design, the chip system further includes a memory for storing the necessary programs and data. The chip system may be composed of chips or may include chips and other discrete devices.

[0043] It should be noted that the beneficial effects of the various designs of the electronic devices provided in the second to seventh aspects of the embodiments of this application can be referred to the beneficial effects of any possible implementation of the first aspect, and will not be repeated here. Attached Figure Description

[0044] Figure 1 is a schematic diagram of a user's memory information in a dialogue scenario;

[0045] Figure 2 is a schematic diagram of a possible hardware structure of an electronic device in an embodiment of this application;

[0046] Figure 3 is a schematic diagram of a possible software structure of an electronic device in an embodiment of this application;

[0047] Figure 4A is a schematic diagram of a system architecture that may be applicable to the memory information management method provided in the embodiments of this application;

[0048] Figure 4B is a schematic diagram of another system architecture that may be applicable to the memory information management method provided in the embodiments of this application;

[0049] Figure 4C is a schematic diagram of a system architecture that may also be applicable to the memory information management method provided in the embodiments of this application;

[0050] Figure 5 is a schematic diagram of several possible ways to enter the memory application interface provided in the embodiments of this application;

[0051] Figure 6A is a schematic diagram of memorizing user memory information in an important day scenario provided by an embodiment of this application;

[0052] Figure 6B is a schematic diagram of an important day scenario editing memory service card provided in an embodiment of this application;

[0053] Figure 7A is a schematic diagram of memorizing user information in a card and certificate scenario provided in an embodiment of this application.

[0054] Figure 7B is a schematic diagram of an editable memory service card in a card and certificate scenario provided in an embodiment of this application;

[0055] Figure 8 is a schematic diagram of memorizing and editing user memory information in common address and event scenarios provided in an embodiment of this application;

[0056] Figure 9A is a schematic diagram of an application for associating unstructured memory information of users in an important day scenario provided by an embodiment of this application;

[0057] Figure 9B is a schematic diagram of an application for editing memory service cards and associated applications in an important day scenario provided in an embodiment of this application;

[0058] Figure 10 is a schematic diagram of a method for retrieving relevant memory information based on an application APP, as provided in an embodiment of this application.

[0059] Figure 11 is a flowchart illustrating a method for managing memory information according to an embodiment of this application;

[0060] Figure 12 is a schematic diagram of the application and demonstration process structure provided in the embodiments of this application;

[0061] Figure 13A is a schematic flowchart of a method for managing memory information through collaboration between the terminal and the cloud, as provided in an embodiment of this application.

[0062] Figure 13B is a schematic diagram of the process structure for implementing memory information management through collaboration between the terminal side and the cloud, as provided in an embodiment of this application.

[0063] Figure 14A is a schematic diagram of the structured processing of memory information and its application by the collaboration between the terminal side and the cloud side according to an embodiment of this application;

[0064] Figure 14B is a schematic diagram of information display corresponding to memory scene classification provided in an embodiment of this application;

[0065] Figure 15A is a schematic diagram of the interface effect after the user's memory information is structured and processed in the important daily memory scenario provided in the embodiment of this application;

[0066] Figure 15B is a schematic diagram of the interface effect after the user memory information is structured and processed in the card memory scenario provided in the embodiment of this application.

[0067] Figure 15C is a schematic diagram of the interface effect after the user memory information is structured and processed in the address memory scenario provided in the embodiment of this application.

[0068] Figure 15D is a schematic diagram of the interface effect after the user memory information is structured and processed in the event memory scenario provided in the embodiment of this application.

[0069] Figure 16 is a schematic diagram of the flow structure of a user's memory information association application provided in an embodiment of this application;

[0070] Figure 17 is a schematic diagram of querying relevant memory information based on an application according to an embodiment of this application;

[0071] Figure 18 illustrates a process for intelligent execution control that can be applied to an embodiment of this application. Detailed Implementation

[0072] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0073] The names and related technical features involved in the embodiments of this application will be explained below. It should be noted that these explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0074] 1) Memory information: Memory information can refer to information or content that needs to be memorized, recorded, stored, and can be reproduced, such as user information including but not limited to events, place names, time, concepts, ideas, words, etc.

[0075] In this embodiment of the application, the memory information can be recorded and / or stored in an electronic device and can be provided to the user for viewing and use.

[0076] 2) Unstructured memory information: Unstructured memory information refers to memory information that cannot be logically expressed using a fixed structure. That is, the structure of unstructured memory information is usually irregular or incomplete, without a predefined or standard information model / template, and it is impossible to automatically classify scenarios and / or integrate information for unstructured memory information. For example, unstructured memory information can be information expressed in the user's natural language or information in plain text form.

[0077] 3) Structured memory information: Structured memory information refers to memory information that can be logically expressed using a fixed structure. Usually, the structure of such information is regular or complete, and there are predefined or standard information models / templates. In addition, for structured memory information, scene classification and / or information integration can be performed automatically.

[0078] In the embodiments of this application, structured memory information can also be referred to as formatted memory information, or standardized / unified memory information, etc.

[0079] 4) End-side electronic devices: Electronic devices (also known as terminal devices) can include mobile phones, tablets, laptops, personal digital assistants (PDAs), point of sale (POS) terminals, in-vehicle computers, smartwatches, televisions, and other electronic devices with display screens.

[0080] Typically, electronic devices can support a variety of applications. These may include one or more of the following: travel apps, drawing apps, presentation apps, word processing apps, game apps, phone apps, video player apps, music player apps, email apps, shopping apps, instant messaging apps, photo management apps, camera apps, browser apps, calendar apps, clock apps, payment apps, and health management apps. Instant messaging apps, in particular, can be diverse, including SMS apps, MMS apps, various email apps, WeChat, Tencent QQ, WhatsApp Messenger, Line, Instagram, and DingTalk. Users can use instant messaging apps to send text, voice messages, images, video files, and other files to other contacts.

[0081] The applications supported by the electronic device can be native applications or quick apps; this application embodiment does not impose specific limitations. The electronic device can also support quick service cards corresponding to these applications, such as cards corresponding to order logistics services in shopping applications, and cards corresponding to ticketing information in travel applications. Furthermore, the electronic device can support quick service cards corresponding to both installed and uninstalled applications.

[0082] 5) Desktop: Desktop can refer to the desktop of an electronic device, that is, the interface through which the electronic device interacts with the user when the electronic device is in the foreground and no application is running.

[0083] For example, a mobile phone's home screen typically displays one or more functional icons (i.e., representative graphics that demonstrate their corresponding functions) and icon labels (names of the icon's functions), such as camera, app store, folders, etc. In addition, the home screen may also display service cards, shortcuts, widgets, etc.

[0084] 6) Service Cards (referred to as cards): Service cards, also known as quick service cards, provide a more granular, atomic service capability than applications (apps). They directly display the services or content that users care about most in an interactive card format. Cards can be embedded in various apps or interactive scenarios to better meet user needs. A card is generally a page within a quick app or its corresponding native app. Clicking the card will take the user to a specific service page within the corresponding quick app or app.

[0085] The card generation process is as follows: the application service provider uploads the service content that needs to be pushed to the user to the server. The server generates the corresponding card according to the service content uploaded by the provider and pushes the card to the user's electronic device for display, so that the user's electronic device presents the service pushed by the application service provider to the user in the form of a card.

[0086] Generally, a card corresponds to a portion of the service functions of an application (unless otherwise specified, the "application" referred to in this application can be a quick app or a native app, and this application embodiment does not impose any restrictions). The application provider can split the application's services into multiple service modules, with each service module corresponding to a card, and then push different cards to users according to different service scenarios.

[0087] In the embodiments of this application, the card used to provide memory / record / display memory information services in the interface displayed by the electronic device can be called a "memory card" or a "memory service card".

[0088] 7) Interface: An interface refers to the two-dimensional surface on the display screen of an electronic device that is used to present images, videos, text, information, and other content to the user. The visual style of the interface (such as shape, structure, size, etc.) can usually remain fixed or can be flexibly set by the user.

[0089] Interface resources: These typically indicate the content displayed on the interface, such as images, text, and rich media. Rich media refers to information dissemination methods that include animation, sound, video, and / or interactivity. Rich media can include streaming media, audio, Flash, and one or a combination of programming languages ​​such as Java, Javascript, and DHTML.

[0090] A page typically refers to the content displayed on a screen, and the interface can be presented through a page. In the embodiments of this application, a page can be a desktop; for example, a mobile phone may include at least one page, and each page corresponds to a desktop. A page can also be any one or more interfaces in the lock screen or the negative one screen.

[0091] 8) Visual style: Visual style (abbreviated as "style") can refer to the visual feeling that things present to people, including the shape, structure, size, color, movement and stillness of things.

[0092] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0093] Furthermore, in the description of this application, terms such as "first," "second," or "1," "2," etc. (except in special cases indicating numerical values) are used only for descriptive purposes and should not be construed as indicating or implying relative importance or order. The symbol "***" or similar symbols described in the embodiments of this application are used to represent ambiguous information or content.

[0094] The preceding text introduced some of the terms used in the embodiments of this application. The following text introduces the technical background of the embodiments of this application.

[0095] With the rapid development of society, electronic devices such as mobile phones are becoming increasingly common. These devices not only have communication functions but also powerful processing capabilities, storage capacity, and camera functions. Electronic devices utilize operating systems (such as HarmonyOS). The operating system executes the corresponding applications, allowing users to make calls, send text messages, browse web pages, and store information. As shown in Figure 1, in the current dialogue scenario, to prevent forgetting useful user dialogue information / content (such as Chen's mobile phone number in the dialogue interface shown in Figure 1), the user needs to memorize (record) and store the received dialogue information / content through their mobile phone for easy retrieval and memorization later.

[0096] However, current implementations typically record and display user-remembered information in natural language (or plain text), lacking efficient management and hindering user memorization and use (e.g., storing, retrieving, and accessing information). Therefore, achieving efficient management of user-remembered information is a pressing issue that needs to be addressed.

[0097] In view of the above problems, embodiments of this application provide a method for managing memory information. This method is used to achieve efficient management of user memory information, facilitating user memorization and use.

[0098] The technical solutions in this application embodiment can be applied to electronic devices, which can be any device capable of displaying an interface. For example, electronic devices can be mobile phones, foldable phones, tablets, wearable devices (e.g., watches, bracelets), in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart home devices (e.g., smart TVs), and other electronic devices. It is understood that this application embodiment does not limit the specific type of electronic device. The electronic devices to which this application embodiment can be applied, in exemplary embodiments, include but are not limited to those equipped with… Alternatively, it can be an electronic device running another operating system. For example, the electronic device described in the foregoing embodiments can be used.

[0099] Figure 2 illustrates a possible hardware structure diagram of an electronic device according to an embodiment of this application. Referring to Figure 2, the electronic device 200 includes components such as a power supply 210, a processor 220, a memory 230, an input module 240, a display module 250, an audio circuit 260, and a communication interface 270. Those skilled in the art will understand that the hardware structure of the electronic device 200 shown in Figure 2 does not constitute a limitation on the electronic device 200. The electronic device 200 provided in this application embodiment may include more or fewer components than shown, may combine two or more components, or may have different component configurations. The various components shown in Figure 2 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0100] The following is a detailed description of each component of the electronic device 200, with reference to Figure 2:

[0101] Power supply 210 (such as a battery) is used to power various components. Optionally, power supply 220 can be logically connected to processor 220 through a power management system, thereby enabling the power management system to manage functions such as charging, discharging, and power consumption.

[0102] The processor 220 is the control center of the electronic device 200. It connects various components via various interfaces and lines, and executes software programs and / or modules stored in the memory 230, as well as calling data stored in the memory 230, to perform various functions and process data of the electronic device 200, thereby enabling various services based on the electronic device 200. In this embodiment, the processor 220 can be used to implement a memory information management method provided in this embodiment.

[0103] The memory 230 can be used to store software programs and modules. The processor 220 executes various functional applications and data processing of the electronic device 200 by running the software programs and modules stored in the memory 230. Optionally, the memory 230 may mainly include a program storage area and a data storage area. The program storage area may store the operating system (mainly including the software programs or modules corresponding to the kernel layer, system layer, application framework layer, and application layer). In addition, the memory 230 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, or other volatile solid-state storage device.

[0104] The input module 240 can be used to receive editing operations on various types of data objects, such as numbers or characters, input by the user, and to generate key signal inputs related to user settings and function control of the electronic device 200. Optionally, the input module 240 may include a touch panel 241 and other input devices 242. The touch panel 241, also known as a touchscreen, can collect user touch operations on or near it (e.g., operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 241), and drive corresponding connection devices according to a pre-set program. In this embodiment, the touch panel 241 can collect user operations on it. For example, the user operation may be the operation of entering a search term in the search box, or the operation of clicking on any search result included in the search results interface.

[0105] Optionally, other input devices 242 may include, but are not limited to, one or more of the following: a physical keyboard, an infrared sensor, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick. For example, an infrared sensor can be used to detect the user's air gestures.

[0106] The display module 250 (also referred to as a display screen, display unit, or presentation unit) can be used to display information input by the user or information provided to the user, as well as various menus of the electronic device 200. The display module 250 is the display system of the electronic device 200, used to present the interface and realize human-computer interaction. The display module 250 may include a display panel 251. Optionally, the display panel 251 can be configured using a liquid crystal display (LCD), an organic light-emitting diode (OLED), or other similar forms. In this embodiment, the display module 250 can be used to display a user interface. For example, the user interface can display interfaces corresponding to various possible memory scenarios, such as the homepage interface of a memory app, the memory application interface displayed on the electronic device's desktop interface via a pull-down operation, or a chat interface displayed by waking up a voice assistant. As another example, the user interface can also display an interface showing memory information obtained based on the method provided in this embodiment.

[0107] Audio circuitry 260, microphone 261, and speaker 262 provide an audio interface between the user and electronic device 200. Audio circuitry 260 converts audio data into signals recognizable by speaker 262 and transmits these signals to speaker 262, where they are converted into sound signals for output. Microphone 261 collects external sound signals (such as human speech or other sounds) and converts these signals into signals recognizable by audio circuitry 260, sending them to audio circuitry 260. Audio circuitry 260 can also convert the signals transmitted by microphone 261 into audio data and output the audio data to RF circuitry for transmission to, for example, another electronic device, or output the audio data to memory 230 for further processing.

[0108] The electronic device 200 can physically connect to other devices via the communication interface 270. Optionally, the communication interface 270 can be connected to the communication interfaces of the other devices via a cable to enable data transmission between the electronic device 200 and the other devices.

[0109] In this embodiment, the electronic device 200 is capable of communication services and interacting with other electronic devices. Therefore, the electronic device 200 needs to have data transmission capabilities. The electronic device 200 not only includes the communication interface 270 shown in Figure 2, but may also include other communication modules, which will not be detailed here. Furthermore, the electronic device 200 may also include a camera, at least one sensor, etc., although not shown in Figure 2, and will not be listed here. The at least one sensor may include, but is not limited to, a pressure sensor, a barometric pressure sensor, an accelerometer, a distance sensor, a fingerprint sensor, a touch sensor, a temperature sensor, etc.

[0110] The operating system (OS) involved in this application embodiment is the most basic system software running on the electronic device 200. The software system of the electronic device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment takes an operating system adopting a layered architecture as an example to illustrate the software architecture of the electronic device 200.

[0111] Figure 3 illustrates a possible software architecture block diagram of an electronic device according to an embodiment of this application. Referring to Figure 3, the software architecture of the electronic device can be a layered architecture; for example, the software can be divided into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into five layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the runtime and system libraries, the kernel layer, and the hardware layer.

[0112] The application layer may include a series of application packages. As shown in Figure 3, the application layer may include a user interface (UI), camera, settings, skin modules, third-party applications, etc. Third-party applications may include, for example, wireless local area network (WLAN), music, call, Bluetooth, video, search, etc. In this embodiment, the application layer may also provide applications for implementing desktop-based search functionality and applications for implementing voice assistant-based search functionality.

[0113] In one possible implementation, the application can be developed using Java, by calling the application programming interface (API) provided by the application framework layer. Developers can then interact with the underlying operating system layers (such as the hardware layer and kernel layer) to develop their own applications. This application framework layer primarily consists of a series of services and management systems within the operating system.

[0114] The application framework layer provides application programming interfaces and a programming framework for applications within the application layer. The application framework layer includes some predefined functions. As shown in Figure 3, the application framework layer may include a view system, activity manager, window manager, content provider, phone manager, resource manager, notification manager, etc.

[0115] The Activity Manager manages the lifecycle of each application and provides commonly used navigation and back functions, offering an interactive interface for all program windows.

[0116] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0117] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0118] A view system includes both visual and non-visual controls, such as controls that display text and controls that display images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text message notification icon could include views that display text and views that display images.

[0119] A phone manager is used to provide communication functions for electronic devices. For example, it manages call status (including connection and disconnection).

[0120] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0121] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0122] The runtime includes the core libraries and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0123] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core libraries of the operating system. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0124] A system library can include multiple functional modules. For example: a surface manager, a media framework, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), etc.

[0125] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0126] The media framework supports playback and recording of various commonly used audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0127] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0128] A 2D graphics engine is a drawing engine for 2D drawing. A 2D graphics engine can perform drawing operations, such as drawing on the screen to search, edit, and create interfaces for searching memory information.

[0129] In some embodiments, a 3D graphics processing library can be used to draw 3D motion trajectory images, and a 2D graphics engine can be used to draw 2D motion trajectory images.

[0130] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0131] The hardware layer can include various types of sensors, such as accelerometers, gravity sensors, and touch sensors.

[0132] Typically, an electronic device 200 can run multiple applications simultaneously. In a simpler scenario, one application corresponds to one process; in a more complex scenario, one application can correspond to multiple processes. Each process has a unique process ID.

[0133] It should be understood that the hardware structure of the electronic device can be as shown in Figure 2, and the software system architecture of the electronic device can be as shown in Figure 3. The software programs and / or modules corresponding to the software system architecture in the electronic device can be stored in the memory 230. The processor 220 can run the software programs and applications stored in the memory 230 to execute the flow of a memory information management method provided in the embodiments of this application.

[0134] Figures 4A, 4B, and 4C illustrate several system architecture diagrams that may be applicable to the memory information management method provided in the embodiments of this application.

[0135] In this embodiment, the cloud can refer to various services and resources on the Internet, including but not limited to cloud storage, cloud computing, cloud applications, and cloud databases. These can be accessed and used on the Internet without requiring users to build and maintain their own server infrastructure. The computing resources and data storage provided by the cloud have characteristics such as high reliability, high scalability, and high availability. The edge refers to devices that can connect to the cloud and interact with users to provide computing and information services, such as mobile phones, computers, and other electronic devices.

[0136] System Architecture 1: Referring to the system architecture shown in Figure 4A, this system architecture scenario may include, for example, an electronic device 200, a user 41, and a server 42. The electronic device 200 can connect to and communicate with the server 42 through a communication network. Specifically, the electronic device 200 is used to respond to a first operation by the user, the first operation being used to instruct the user to memorize target content described in natural language; it is also used to send the target content described in natural language to the server 42. The server 42 is used to obtain memorized information based on the target content described in natural language, the memorized information including the target content carried by structured information; the server 42 is also used to send the memorized information to the electronic device 200; correspondingly, the electronic device 200 receives the memorized information from the server 42.

[0137] In one possible implementation, the aforementioned server 42 can serve as an example in the cloud.

[0138] System Architecture Two: Referring to the system architecture shown in Figure 4B, this system architecture differs from the system architecture shown in Figure 4A in that the method provided in this embodiment can also be implemented by the electronic device 200 itself. Specifically, the electronic device 200 detects a first user operation, which instructs the user to memorize target content described in natural language; the electronic device 200 is also used to generate memory information based on the first operation, the memory information including the target content carried by structured information.

[0139] Figures 4A and 4B above are examples of system architectures that can be applied to the embodiments of this application. The embodiments of this application do not limit the specific scenario of the system architecture. For example, server 42 can also connect to and serve more electronic devices.

[0140] System Architecture 3: As shown in Figure 4C, based on the system architecture shown in Figure 4A, electronic device 200 can also collaborate with other devices to transfer some tasks to other devices for processing. Therefore, the system architecture shown in Figure 4C can include electronic device 200, user 41, server 42, and electronic device 201.

[0141] Electronic device 200 can be, for example, a mobile phone, and electronic device 201 can be, for example, a large screen. Multi-device collaboration can be, for example, a scenario where a mobile phone screen is projected onto a large screen. The large screen can act as a transfer device for the mobile phone, receiving media data transferred from the mobile phone and playing and / or displaying it.

[0142] Based on the system architecture diagrams shown above, the following uses a mobile phone as an example to illustrate the application effects achievable by the method provided in this application embodiment from the perspective of its interface display. It should be noted that the screen displayed on the interface of the electronic device described below is merely an exemplary demonstration of the application effects of this application embodiment and does not constitute a limitation on the actual displayed screen and visual style.

[0143] First, Figure 5 shows several examples of how to access the memory application interface according to embodiments of this application.

[0144] Example 1: Referring to Figure 5(a), interface 501a shows a schematic diagram of the mobile phone desktop. In interface 501a, the user's finger operates on the memory APP. The electronic device responds to the user's operation command, opens the memory APP, and displays interface 502 as shown in Figure 5(e).

[0145] Example 2: Referring to Figure 5(b), interface 501b shows a schematic diagram of the mobile phone desktop. In interface 501b, the user's finger can be used to pull down any position on the interface. The electronic device responds to the user's pull-down operation and displays interface 502 as shown in Figure 5(e).

[0146] Example 3: Referring to Figure 5(c), in the scenario where the electronic device displays a desktop interface, the electronic device can detect and respond to voice commands to display interface 501c, which is a chat interface after waking up the voice assistant. As can be seen from interface 501c, the voice command can be "Open Memory APP," and the electronic device responds to this voice command by opening the Memory APP and displaying interface 502 as shown in Figure 5(e).

[0147] It should be noted that the embodiments of this application are not limited to the scenario where the electronic device displays a desktop interface, and voice commands can be detected in any possible scenario where the electronic device displays an interface.

[0148] Example 4: As shown in Figure 5(c), interface 501d shows the SMS chat interface of a mobile phone. In interface 501d, the user can first press and hold the chat box to be remembered to display the function box. Then the user can operate the "memorize" function icon to open the memory APP and display interface 502 as shown in Figure 5(e).

[0149] Referring to Figure 5(e), interface 502 is a possible visualization interface for memory information. Interface 502 displays multiple memory scenarios (e.g., important dates, cards, frequently used addresses, times) and corresponding service cards for each scenario. Within each memory scenario, users can create service cards to record memory information / content. For example, as shown in interface 502, in the important date memory scenario, the user has already created a service card to remember their birthday. The user can click "Edit" to edit or update the memory information, such as the date of the birthday and the name of the associated person. Furthermore, the user can create more service cards related to important dates by clicking the "Create" button at the bottom of interface 502.

[0150] Furthermore, the interface display effects achievable using the method provided in this application are described in conjunction with the accompanying drawings. It should be noted that, for ease of understanding, the following description of providing memory information / content through an interface display is merely an example. In practical applications, this application is not limited to providing memory information / content through an interface display; for example, it may also provide memory information / content through voice broadcasting, and the visual style of the displayed content is not limited.

[0151] In the embodiments of this application, the interface of the electronic device's memory application (APP) can display memory information corresponding to one or more memory scenarios. The following uses important days, cards, frequently used addresses, and events as examples of memory scenarios to introduce the interface display effects that may be achieved by using the method provided in this application.

[0152] Important Day Memory Scenario: See Figure 6A. Interface 601 shows the memory application interface in the important day memory scenario. In interface 601, the memory service card 6011 that has been created is displayed. Users can click the "Go to Create" button to create memory service cards for other important days, which will take them to the dialog interface 602 for creating an important day memory.

[0153] In interface 602, users can input information or content related to important dates using the keyboard or voice commands. Interface 602 shows that the user inputs "Xiaoyi, please remember my uncle's birthday is March 28th" in input box 6021. The electronic device displays the reply "Got it. Next time, just say 'check my uncle's birthday' and it will tell you." Based on the user's input, the device automatically creates and displays a corresponding memory service card 6023. Specifically, the memory service card 6023 displays the date "March 28th," the associated person "uncle," and the repetition period as "repeated annually."

[0154] The memory service card 6023 also displays "Go to Edit" and "View All" buttons. When a user needs to edit, update, or delete the information displayed in the memory service card 6023 (such as date, associated person, and recurring period), they can click the "Go to Edit" button to edit, update, or delete the information displayed in the memory service card 6023. In addition, by clicking the "View All" button, the user can view all the memory service cards created under the memory field of important days, as shown in interface 603 in Figure 6B.

[0155] Referring to Figure 6B, in interface 603, under the memory scenario of important days, memory service cards for Uncle's birthday and My birthday have been created. When the user clicks the "Go to Edit" button in the Uncle's birthday memory service card, the corresponding editing box for that memory service card will be displayed in interface 603, as shown in interface 604. In this editing box, some tags associated with the important day and their corresponding memory information are displayed, such as type and corresponding memory information "birthday", name and corresponding memory information "birthday", associated person and corresponding memory information "uncle", date and corresponding memory information "March 28", and repetition and corresponding memory information "repeated every year". In addition, the memory information corresponding to each tag can also be manually edited, updated, or deleted by the user. For example, if the memory information "March 28" for the date is incorrect, the user can manually enter the correct date "February 29" in the memory information box for the date. The user can also modify the memory information "repeated every year" for repetition, such as entering "repeated every four years" in the memory information box for repetition.

[0156] Card memory scenario: As shown in Figure 7A, interface 701 displays the memory application interface in the card memory scenario. In interface 701, the relevant instructions for card recording and query are displayed. Users can click the "Go to Create" button to create a card memory service card, which will take them to the dialog interface 702 for creating a memory card.

[0157] In interface 702, users can input memorized card information or content via the keyboard or voice. Interface 702 shows that the user inputs the card information "Xiaoyi, please remember my ID number 1305*******18" in input box 7021. The electronic device displays the reply "Written down, next time just say 'Query my ID' and it will tell you" in reply box 7022. Based on the user's input, the device automatically creates and displays the corresponding memory service card 7023. Specifically, the memory service card 7023 displays the ID number "1305*******18" and the associated person and card type "My ID Card".

[0158] The memory service card 7023 also displays "Go to Edit" and "View All" buttons. When a user needs to edit, update, or delete the information displayed in the memory service card 7023 (such as ID card number, associated person, and card type), they can click the "Go to Edit" button to edit, update, or delete the information displayed in the memory service card 7023. In addition, by clicking the "View All" button, the user can view all the memory service cards created under the card's memory field, as shown in interface 703 of Figure 7B.

[0159] Referring to Figure 7B, in interface 703, under the card / certificate memory scenario, a memory service card for my ID card and a service card for Zhang Lan's business card have been created. When the user clicks the "Go to Edit" button in the memory service card for my ID card, the corresponding editing box for that memory service card will be displayed in interface 703, as shown in interface 704a. In this editing box, some tags associated with the card / certificate and their corresponding memory information are displayed, such as the card / certificate type and its corresponding memory information "ID card", the associated person and its corresponding memory information "me", the certificate number and its corresponding memory information "1305*******18", the certificate's effective date and its corresponding memory information, and the certificate's expiration date and its corresponding memory information. In addition, the memory information corresponding to each tag can also be manually edited, updated, or deleted by the user. For example, for the certificate's effective date and expiration date, the user can manually enter the actual date in the memory information boxes corresponding to the certificate's effective date and expiration date.

[0160] When a user clicks the "Edit" button in the memory service card of Zhang Lan's business card, the corresponding editing box for that service card will be displayed, as shown in interface 704b. In this editing box, some tags associated with the card and their corresponding memory information are displayed, such as the card type and its corresponding memory information "business card", the associated person and its corresponding memory information "Zhang Lan", the phone number and its corresponding memory information "182******82", and the email address and its corresponding memory information. In addition, the memory information corresponding to each tag can also be manually edited, updated, or deleted by the user. For example, for the email address, the user can manually enter Zhang Lan's email address in the memory information box corresponding to the email address.

[0161] Memory scenarios for frequently used addresses and events: Referring to the introduction of memory scenarios for important dates and cards above, for memory scenarios for frequently used addresses and events, one or more memory service cards can also be created for the user's memory information or content. Furthermore, the memory information displayed on each memory service card can also be manually edited, updated, or deleted by the user, which will not be detailed here.

[0162] For example, as shown in Figure 8, interface 801 shows an interface where users can edit memory information or content in the memory scenario of frequently used addresses, while interface 802 shows an interface where users can edit the information or content displayed on the first memory service card in the memory scenario of events.

[0163] The above examples use important dates, cards, frequently used addresses, and events as memory scenarios to illustrate the application effects achieved through the methods of this application. This application is not limited to the above-mentioned memory scenarios. In practical applications, electronic devices (such as mobile phones) can classify memory scenarios based on the user's memory information or content. For other memory scenarios, the corresponding interface display effects can also be achieved by referring to the above description, and will not be shown one by one.

[0164] Furthermore, in the method provided in this application embodiment, the user's memory information can be associated with an application (or task). Thus, when using the method, the user can either access and use the associated application while retrieving and using the memory information, or retrieve the memory information through the associated application even without knowing it. It should be noted that the following description of providing memory information and associated applications through an interface display is merely an example. In actual applications, this application does not limit the provision of memory information and associated applications through an interface display; for example, it can also provide it through voice broadcasting, and the visual style of the displayed content is not limited.

[0165] For example, taking the memory scenario of an important day as an example, as shown in Figure 9A, the user can input memory information or content through keyboard input or voice, as can be seen from the input box 9011 shown in interface 901. The memory information input by the user is "Xiaoyi, please remember my uncle's birthday is March 28th". Based on the memory information input by the user, the electronic device displays the reply information "I've remembered it. Next time, just say 'check my uncle's birthday' and I'll tell you" through the reply box 9012. It also automatically creates and displays a memory service card 9013. In the memory service card 9013, not only is the specific date "March 28th" and the associated person and type "uncle's birthday" displayed, but also the associated applications APP1 and APP2 are displayed. APP1 and APP2 can be, for example, applications that the user has used in previous years for their uncle's birthday, or applications that the electronic device automatically pushes that are associated with the birthday scenario. That is, the pushed applications are applications that the electronic device predicts the user may use to celebrate the birthday. In addition, the memory service card 9013 also displays "View All" and "Go to Edit" buttons. When users need to edit, update, or delete the information displayed in the memory service card 9013 (such as date, associated person, and type), they can click the "Go to Edit" button to edit, update, or delete the information displayed in the memory service card 9013. Furthermore, in the memory service card 9013, users can click the "View All" button to view all the memory service cards created under the memory field of important days, as shown in interface 902.

[0166] In interface 902, memory service cards for my uncle's birthday and my birthday have already been created. The uncle's birthday memory service card primarily displays the date "March 28th," the associated person and type "Uncle's Birthday," and the associated applications APP1 and APP2. For my birthday's memory information, since the associated application APP3 has been deleted, the electronic device can automatically recommend APP1, which has a similar purpose or function to APP3, as the associated application. Therefore, my birthday memory service card displays the date "May 28th," the associated person and type "My Birthday," a notification that the associated application APP3 has been deleted, and the recommended application APP1.

[0167] Furthermore, the information displayed in each memory service card can also be manually edited, updated, or deleted by the user. As shown in Figure 9B, in interface 903, when the user clicks the "Go to Edit" button in the Uncle's Birthday memory service card, the corresponding editing box for that memory service card will be displayed, as shown in interface 904. In this editing box, not only are some tags associated with the important date (such as type, name, associated person, date, repetition) and the corresponding memory information automatically displayed, but the tags and application information of the associated applications (such as the icons of APP1 and APP2) are also automatically displayed. Alternatively, the memory information corresponding to each tag can be manually edited or entered by the user. For example, in the information box corresponding to the associated application, the user can manually enter other APP information. Similarly, the information of each tag displayed in my birthday memory service card can also be manually edited, updated, or deleted by the user, which will not be detailed here.

[0168] In this embodiment, after memory information is associated with an application, when a user queries memory information, they can search for associated memory information by entering keywords they want to remember, or they can search for related memory information based on the application (APP). For example, as shown in Figure 10, the content displayed in the input box 1001 and reply box 1002 of the interface 1000 shows that when a user queries memory information related to APP1, the electronic device can automatically display one or more memory information associated with APP1 through memory service cards. For example, memory service card 1003 displays the memory information of my uncle's birthday, and memory service card 1004 displays the memory information of my birthday.

[0169] As can be seen from the above examples, in this application embodiment, after associating the structured memory information with the terminal application (APP), it can meet the user's need to use the associated application when using the memory information. In addition, the user can also retrieve and query related memory information based on the application, increasing the ways for the user to retrieve and query memory information. This not only improves the efficiency of the user in viewing memory information, but also enhances the user experience.

[0170] The above describes the possible application effects of the memory information management method provided by the embodiments of this application from the perspective of electronic device display. The following describes a memory information management method provided by this application from the perspective of technical implementation, that is, how to use the method provided by this application to achieve the interface effect described above, thereby improving the efficiency of users in retrieving and viewing memory information, and also meeting the needs of users to use related applications when using memory information, thus enhancing the user experience.

[0171] Figure 11 shows a flowchart of a memory information management method provided in an embodiment of this application. This method can be applied to electronic devices (or terminal devices), including but not limited to personal computers, server computers, handheld or laptop devices, mobile devices (such as mobile phones, tablets, etc.), in-vehicle computers, smartwatches, televisions, and other electronic devices with display screens. This method can be executed by the electronic device or by a corresponding component of the electronic device (e.g., a chip, a chip system, or a circuit). Taking the execution of this method by an electronic device as an example, referring to Figure 11, the method may include the following steps:

[0172] S1101: The electronic device detects a first operation by the user, the first operation being used to instruct the memory of target content based on a natural language description.

[0173] In the embodiments of this application, the target content described above based on natural language can also be referred to as the user's unstructured memory information.

[0174] In one possible implementation, the structured information includes multiple tags and multiple sub-contents corresponding to each of the tags.

[0175] In this application embodiment, the plurality of labels may indicate, but are not limited to, indicating at least one of the following:

[0176] Time, place, people, things, actions, states, attributes, and relationships.

[0177] The meanings of the above labels are as follows:

[0178] (1) Time can refer to a specific time point (e.g., 7:00 PM), a date (e.g., May 3), a time period (e.g., 7:00 AM to 8:00 AM), a duration (e.g., from May 3, 2024 to June 3, 2024), a cycle (e.g., once a year), etc.

[0179] (2) Location can refer to geographical location, such as the doorstep of home, restaurant, school, hospital, etc.

[0180] (3) People can refer to related people, participants, etc.

[0181] (4) "Objects" can refer to real objects (such as mobile phones, stools, scenery, etc.) or virtual objects (such as phone numbers, email addresses, etc.).

[0182] (5) Actions can refer to user behavior, such as being in a meeting, running, etc.

[0183] (6) State can refer to the form that a person or thing exhibits (e.g., something is a liquid, something is a rectangle, something is still, etc.), and it can also refer to the progress of something (e.g., work has been completed, work is being carried out, etc.).

[0184] (7) Attributes can refer to the unique or non-unique characteristics or features of a person or thing; the attributes of things include color, shape, weight, etc., and the attributes of people include personality, ability, etc.; attributes can also refer to the general term for the same type of people or things.

[0185] (8) Relationship can refer to the connection or function between any one or more of people, things, or objects. For example, Zhang San and I are relatives, the computer is mine, and the application is installed in electronic devices.

[0186] In this embodiment of the application, the sub-content corresponding to a tag can refer to the specific information or content corresponding to the tag. For example, if the tag is time, then 8:00 AM is the sub-content corresponding to time. As another example, if the tag is a person, then "my mother" is the sub-content corresponding to that tag.

[0187] For example, if the target content based on natural language description is "Please help me remember that my mother's birthday is December 28th", the target content carried by the electronic device based on the first operation and structured information can be "My mother's birthday is December 28th".

[0188] In one possible implementation, the structured information may further include a scene type, which is bound to a set of tags from the plurality of tags. This set of tags may be some or all of the plurality of tags. This implementation allows for scene classification of the memory information, facilitating efficient management of the memory information.

[0189] In the embodiments of this application, the above-mentioned scenario types may be, but are not limited to, important days, cards, frequently used addresses, or events.

[0190] For example, for the "Important Day" scenario, the bound set of tags can be attribute, person, and time. For the "Card / ID" scenario, the bound set of tags can be attribute, person, and time. For the "Frequently Used Address" scenario, the bound set of tags can be attribute, person, and location. For the "Event" scenario, the bound set of tags can be action, person, time, and location.

[0191] In one possible implementation, the multiple tags also include a target application or target application type associated with the target content. This approach allows users to more conveniently query and use the information they need by leveraging the association between the target content and the application or application type.

[0192] In this embodiment of the application, the target application may include a first application and a second application, wherein the first application is an application that was previously installed on the electronic device and has now been deleted, and the second application is an application that is currently installed on the electronic device. The first application and the second application are of the same type.

[0193] In one possible implementation, the memory information is displayed to the user in the form of cards. This approach allows the electronic device to intuitively present the memory information to the user in card format, making it more convenient for the user to access and use the information, resulting in a better user experience.

[0194] In one possible implementation, the card includes an entry point for the user to access the target application (e.g., a user-operable button displayed on the card). This implementation allows users to quickly access and use the target application through the entry point on the card, resulting in convenient operation and a better user experience.

[0195] In one possible implementation, at least one of the aforementioned tags, sub-content, and scene types is user-editable or searchable. This implementation allows users to edit or search for content in a more flexible, convenient, and efficient manner.

[0196] S1102: The electronic device obtains memory information based on the first operation, the memory information including target content carried based on structured information.

[0197] In this embodiment of the application, the memory information obtained by the above-mentioned electronic device based on the first operation includes target content carried by structured information, so the memory information can be called structured memory information.

[0198] In one possible implementation, the electronic device obtains the memory information by: generating the memory information; or receiving the memory information from a server. This implementation enables the electronic device to effectively obtain the memory information.

[0199] In summary, this application proposes a method for managing memory information. The method includes: an electronic device detecting a first operation by a user, the first operation indicating the memorization of target content described in natural language; and then, based on the first operation, obtaining memory information, which includes the target content carried by structured information. Through this method, the user's memory information can be efficiently managed through the electronic device, thereby facilitating the user's memorization and use.

[0200] Based on the method shown in Figure 11 above, the method will be described in detail below through several specific implementation methods.

[0201] Implementation Method 1:

[0202] In Implementation Method 1, the flow of the memory information management method of this application embodiment is mainly introduced from the perspective of display and application on the terminal side (such as electronic devices). Referring to the flow structure diagram shown in Figure 12, the flow of this method may include the following:

[0203] S1201: The electronic device receives the user's memory operation command.

[0204] S1202: The electronic device identifies and retrieves the memory information input by the user.

[0205] In one possible implementation, the processor of the electronic device responds to the user's memory operation instructions by recognizing and retrieving the memory information input by the user; since the memory information input by the user can be information expressed in the user's natural language, without fixed rules, it is unstructured memory information.

[0206] S1203: Electronic devices obtain structured memory information based on memory information.

[0207] This application does not specifically limit how an electronic device obtains structured memory information based on memory information. For example, the structured processing of memory information can be performed on the device side (such as an electronic device) or on the cloud (such as a memory retrieval module in the cloud).

[0208] For structured memory information, the following S1204 can be performed for memory storage, and one or more of the following S1205 to S1208 processing steps can also be performed.

[0209] S1204: Electronic devices can store structured memory information.

[0210] For example, the memory (also known as the memory storage module) of an electronic device can store encrypted structured memory information. When the user uses the device, the stored structured memory information can be decrypted and displayed in the form of editable or updatable cards to ensure the security of the stored memory information.

[0211] S1205: Electronic devices classify structured memory information into scenarios.

[0212] In this embodiment of the application, the memory information processed according to S1203 and S1205 can be displayed through the interface of the electronic device's display screen.

[0213] For example, after the memory information is structured in S1203, the structured memory information can be displayed on the screen of the electronic device in the form of, but not limited to, service cards. After the structured memory information is categorized into scenarios in S1205, the categorized memory scenarios and the corresponding structured memory information under each memory scenario can be displayed on the screen of the electronic device. The structured memory information can be displayed in the form of, but not limited to, service cards on the interface.

[0214] S1206: Electronic devices perform memory editing on structured memory information.

[0215] For example, the processor of an electronic device can respond to user actions by editing, updating, or deleting structured memory information displayed in a memory service card on the electronic device.

[0216] S1207: Electronic devices store edited, structured memory information.

[0217] In this embodiment of the application, the structured memory information stored in the memory (or memory storage module) of the electronic device can be displayed through the display screen interface of the electronic device and can be edited, updated or deleted by the user. The memory (or memory storage module) of the electronic device can also store the structured memory information edited or updated by the user.

[0218] S1208: Electronic devices apply and associate structured memory information.

[0219] For example, the processor of an electronic device (also known as a memory association module) can determine the corresponding application (APP) / task based on the user's memory information, the user's historical application usage information (i.e., the user's habits), and the corresponding memory scenario, and associate (or bind) the structured memory information with the corresponding application / task.

[0220] If the corresponding application (APP) / task has been deleted from the electronic device, the electronic device can analyze or determine the similarity between the application (APP) and at least one other existing application / task, and then select one or more applications / tasks with high similarity from the at least one application / task, and associate (or bind) the one or more applications / tasks with high similarity with the structured memory information.

[0221] For example, after receiving unstructured memory information from a user's electronic device on the device side, the cloud-based memory retrieval module can structure this information and return it to the device for display and storage. Furthermore, the cloud-based application recommendation module can automatically associate the structured memory information with corresponding applications (APPs) based on the user's memory information and historical usage data, and return the associated application information to the device for further association processing with the structured memory information.

[0222] If the cloud receives an operation command from the device on the edge, indicating that the associated application has been deleted from the device, the application association module in the cloud can also recommend other similar applications to the device on the edge for association with the structured memory information.

[0223] The associated and / or similar applications (recommended applications) of the aforementioned structured memory information can be displayed on the screen of the electronic device through, but not limited to, memory service cards. In addition, the information of the associated and / or similar applications displayed by the electronic device can also be edited or updated by the user.

[0224] Based on the above S1208, after associating the structured memory information with applications, when a user retrieves and consults memory information, the following can be performed:

[0225] S1209a: Electronic devices determine whether an associated application exists.

[0226] For example, the processor of an electronic device can respond to an operation instruction input by a user, which may be information about an application, and then determine whether the application exists; if it exists, the following S1209b can be executed; if it does not exist, the following S1209c can be executed.

[0227] For example, the processor of an electronic device responds to a memory retrieval operation instruction input by the user, determines the associated application, the memory retrieval operation instruction is used to retrieve the memory information that the user wants to access, and determines whether the application exists; if it exists, S1209b can be executed; if it does not exist, S1209c is executed.

[0228] S1209b: Electronic devices support mutual searching between applications and memory information.

[0229] For example, the processor of an electronic device can retrieve or consult related memory information based on the application indicated by the user's input operation instructions, and can display the corresponding structured memory information through the screen interface.

[0230] For example, the processor of an electronic device can display the corresponding structured memory information and associated applications through the screen interface based on the memory retrieval operation command input by the user, and support the user to use the associated applications.

[0231] S1209c: Electronic devices can automatically associate recommended similar applications with structured information.

[0232] For example, an electronic device can determine the corresponding memory information and associated applications based on the user's input memory retrieval operation command. If the associated application has been deleted from the electronic device, the electronic device can associate recommended similar applications with the memory information and display the corresponding structured memory information and the recommended similar applications through the screen interface.

[0233] The recommended similar applications can be determined in the cloud or by the device itself; this application does not impose any specific limitations on this.

[0234] In Implementation Method 1, on the device side, after obtaining structured memory information based on user-input memory information, the electronic device can encrypt and store it in a memory storage module. It can also automatically categorize scenes based on the structured memory information in the memory storage module and display it to the user. The user can edit / update / delete the structured memory information displayed after scene categorization, and the memory storage module will then encrypt and store the edited / updated / deleted memory information. Furthermore, after obtaining structured memory information, the electronic device can automatically associate the structured memory information with applications (APPs) and display them to the user. The associated applications can be determined or recommended based on one or more of the user's memory information, daily usage patterns, and user intent. This way, when the user subsequently reviews the memory information, the associated applications can be automatically matched for the user to use. It also supports mutual searching / query between memory information and applications, making memory management and use more convenient for the user.

[0235] Implementation Method Two:

[0236] In implementation method two, based on the method shown in Figure 11 and applying the system architecture shown in Figure 4A, a method for managing memory information shown in Figure 11 is introduced, which involves collaborative implementation on the edge and cloud. Referring to Figure 13A, it may include the following:

[0237] S1301A: The user's unstructured memory information is sent from the terminal to the cloud. Correspondingly, the cloud receives the user's unstructured memory information.

[0238] In one possible implementation, Figure 13B shows the overall architecture of collaborative execution between the edge and the cloud. Referring to processes 1 and 2 in Figure 13B, the electronic device on the edge detects the user's operation command. In response to the user's operation command, which can be the user's input memory information or an instruction to remember / record the user's input information, the electronic device on the edge sends the user's unstructured memory information, i.e., the user's natural language memory text, which can also be understood as the user's memory information that has not yet been classified, to the memory retrieval module in the cloud. Subsequently, the memory retrieval module in the cloud converts the user's unstructured memory information into the user's structured memory information.

[0239] S1302A: The cloud converts the user's unstructured memory information into the user's structured memory information.

[0240] In one possible implementation, the memory retrieval module in the cloud performs step S1302A.

[0241] S1303A: The cloud sends the user's structured memory information to the client. Accordingly, the client receives the structured memory information.

[0242] In one possible implementation, referring to process 3 shown in Figure 13B, the cloud-based memory retrieval module returns the user's structured memory information to the memory storage module of the terminal electronic device for storage and display by the terminal electronic device.

[0243] Referring to process 4.1 in Figure 13B, after receiving the structured memory information, the memory storage module of the terminal electronic device will encrypt and store the structured memory information for user use. Furthermore, referring to process 4.2 in Figure 13B, the terminal electronic device can also display the user's structured memory information in a multimodal manner; where multimodal means can refer to displaying information or data using multiple presentation formats, such as images, videos, text, and voice.

[0244] In some embodiments, on the device side, the application association module can receive structured memory information from the memory storage module. It can then analyze this information based on the user's historical data and intent scenarios, automatically associating the structured memory information with the corresponding application (APP). If the corresponding application (APP) has been deleted, the application association module can automatically associate the structured memory information with other similar applications based on the similarity between the application (APP) and other applications. Alternatively, the electronic device can report to the cloud that the corresponding application has been deleted, and the cloud can recommend other similar applications. The application association module then automatically associates the cloud-recommended similar applications with the structured memory information.

[0245] Furthermore, the application association module can return the associated information (such as the association information between the memory information and the application, and the associated application information) to the memory storage module for storage, and the electronic device can also display the structured memory information associated with the application in a multimodal manner.

[0246] In this embodiment, structured memory information can be composed of memory information corresponding to at least one tag, where the at least one tag may include an application (APP) tag. Thus, when an electronic device displays structured memory information, the structured memory information can be displayed through a memory service card.

[0247] In one possible design, the memory service card includes one or more editable display areas. Each editable display area can display memory information corresponding to a tag. Users can quickly edit, update, or delete the information displayed in each display area of ​​the memory service card.

[0248] S1304A: The terminal side responds to user commands to query / edit / delete structured memory information.

[0249] In one possible implementation, as shown in Figure 13B, the memory storage module of the electronic device on the terminal side may include one or more of the following functions / capabilities:

[0250] (1) Encryption and decryption of memory information, (2) Classification of memory information, (3) Editing of memory information, (4) Related applications;

[0251] In addition, the memory storage module of an electronic device may also have the function / capability to interact with the display module (such as display module / screen, voice module, etc.).

[0252] Referring to process 5 shown in Figure 13B, the terminal electronic device can respond to user operation commands to query / edit / delete memory information. For example, if the terminal electronic device receives a user's query operation command for querying memory information, the electronic device responds to the user's query operation command by instructing the memory storage module to decrypt and output the corresponding structured memory information. Then, the corresponding structured memory information can be displayed to the user in a multimodal manner (e.g., displaying text, images, or playing audio).

[0253] If the electronic device receives an editing command from the user, and this command is used to edit the memory information, the electronic device responds to the user's editing command by instructing the memory storage module to edit the corresponding structured memory information and store the edited structured memory information. For example, the electronic device's display screen shows an editable interface for the corresponding structured memory information, which the user edits. The edited structured memory information is then returned to the memory storage module for encryption and storage.

[0254] If the electronic device on the terminal receives a deletion operation command from the user, which is used to delete memory information, the electronic device responds to the user's deletion operation command by instructing the memory storage module to delete the corresponding structured memory information stored therein.

[0255] Furthermore, the terminal electronic device can also respond to user commands to query / edit / delete applications associated with memory information. Specifically, the implementation methods for querying / editing / deleting memory information described above will not be elaborated upon here.

[0256] In some embodiments, referring to processes 6.1 and 6.2 shown in Figure 13B, if the associated application has been deleted from the electronic device on the device side, the electronic device can send an instruction to the application recommendation module in the cloud to indicate the deletion of the application and / or application scenario associated with the memory information. After receiving the instruction, the application recommendation module in the cloud can return the application recommendation results to the device side, that is, the application recommendation module in the cloud can recommend other similar applications to the electronic device on the device side.

[0257] In the second implementation method, it is generally more efficient and effective to process large amounts of data in the cloud. Therefore, in this embodiment, the client (or user) can collaborate efficiently with the cloud (or cloud-side) to manage memory information. Specifically, the client can transmit unstructured memory information input by the user to the cloud, which then assists in converting it into structured memory information. The cloud then sends the structured memory information back to the client for user use. After obtaining the structured memory information, the client can respond to user commands by querying, editing, or deleting the memory information.

[0258] Implementation Method 3:

[0259] In Implementation Method 3, the structured processing process of converting the user's unstructured memory information into structured memory information in S1203 and S1302A will be described in detail.

[0260] In this embodiment, unstructured memory information can be converted into structured memory information by the cloud (or the device), and then classification tags can be obtained from the structured memory information. As shown in Figure 14A, on the device (or user side), unstructured memory information input by the user can be transmitted to the cloud via an electronic device. The memory extraction module on the cloud side extracts and processes the unstructured memory information to obtain structured memory information, and then transmits the structured memory information back to the device (or user side) for the user to use. The device (or user side) obtains structured memory information. Since structured memory information has memory features or memory attributes (e.g., memory information belongs to categories such as time, place, person, or event), memory scenarios can be automatically classified based on the structured memory information, such as family, work, travel, health, etc. After classifying the memory scenarios, the structured memory information can be displayed on the electronic device in a multimodal manner, showing one or more tags of memory information or content. Users can flexibly edit, update, or delete the memory information or content of each tag.

[0261] The process by which the cloud-based memory extraction module extracts and processes unstructured memory information to obtain structured memory information can include: First, classifying the unstructured memory information, for example, within a limited closed domain (i.e., within a pre-defined category range). For multi-category memory information, multiple categories will exist. Then, extracting attribute values ​​for each category from the unstructured memory information. Further, during the extraction process, remembering the attribute values ​​of each category and disambiguating entities / objects based on these attribute values. For example, unstructured memory information may contain different words such as "my mom," "old mom," or "mother," but these words all refer to the same entity / object. Therefore, these words can be grouped into a unified standard term, such as "my mom." As another example, unstructured memory information may contain the word "apple." However, "apple" can refer to Apple Inc. or simply fruit. Therefore, based on the context of the memory, the entity / object can be accurately identified and then grouped into the corresponding category.

[0262] Figure 14B shows a schematic diagram of a memory scene classification in an embodiment of this application. The classified memory scenes can include "important day" memories, "card / certificate" memories, "address" memories, "event" memories, etc. For each memory scene, one or more subcategories can be included. For example, for "important day" memories, subcategories include birthdays, anniversaries, repayment dates, etc.; for "card / certificate" memories, subcategories include business cards, ID cards, etc.; for "address" memories, subcategories include my home, relatives' homes, a family of three's home, etc.; for "event" memories, subcategories include personal events and public events.

[0263] Furthermore, for each subcategory, one or more tags can be further subdivided based on memory attributes. For example, in the "birthday" scenario of important days, the subdivided tags include date (or time), subject (i.e., the object of the statement, such as a person or thing), and associated persons. In the "business card" scenario of cards and certificates, the subdivided tags include phone number, subject (i.e., the object of the statement), and associated persons. In the "my home" scenario of addresses, the subdivided tags include address type, associated persons, and detailed address. In the "personal event" scenario of events, the subdivided tags include time (or date), event content, and participants.

[0264] It should be noted that in the embodiments of this application, the various memory scene types (such as important days, cards, addresses, events, etc.) and their subcategories also belong to the tags described in the method shown in Figure 11.

[0265] Figure 14B shows an example of memory scene classification in an embodiment of this application. In practical applications, more levels (or fewer levels) of classification can be performed with reference to the process shown in Figure 14B. Performing more levels of classification is, for example, performing more detailed classification based on each of the above labels, which will not be described in detail here.

[0266] In one possible implementation, a structured template (also called a standard template or reference module) can be predefined for structuring memory information based on the memory scenario. The structured template can contain at least one tag for the memory, such as type, subtype, associated object / entity, etc. The type can be used to represent the memory scenario. In this embodiment, different structured templates (or information models) can be preset for different memory scenarios (e.g., important dates, cards, addresses, events, etc.).

[0267] In this implementation, the memory scenario of important dates, cards, addresses, and events is used as an example to introduce the corresponding structured template and implementation effect.

[0268] Example 1: For the memory scenario of important days, Table 1-1 shows a structured template that includes type, subtype, date, associated person, and repeating tags.

[0269] Table 1-1

[0270] When a user's unstructured memory information is "Please remember my mother's birthday is December 13th", the unstructured memory information is converted into structured memory information based on the structured template shown in Table 1, as shown in Table 1-2.

[0271] Table 1-2

[0272] For example, the effect displayed on the electronic device can be seen in the interface shown in Figure 15A (1). The user can input the user's unstructured memory information "Please remember my mother's birthday is December 13th", and then a memory service card will be generated in the interface. The memory service card is used to display structured memory information. For example, the memory service card includes multiple user-editable display areas, which display information / content of multiple labels, such as the time "December 13th", the person and type "my mother's birthday", the cycle "repeated every year", and the associated applications "APP1" and "APP2". The memory service card also displays an "Edit" button. The user can enter the state of editing structured memory information by clicking the button, as shown in the interface shown in Figure 15A (2). The interface displays an editing box. In the editing box, the user can edit, update or delete the information / content displayed in each display area of ​​the memory service card.

[0273] Example 2: For the memory scenario of cards and certificates, Table 2-1 shows a structured template, which includes type, subtype, number, associated person, and date tag.

[0274] Table 2-1

[0275] When a user's unstructured memory information is "Please write down my ID number as 1305*******18, effective date as November 25, 2023, and expiration date as November 25, 2033", the unstructured memory information is converted into structured memory information based on the structured template shown in Table 2-1, as shown in Table 2-2.

[0276] Table 2-2

[0277] For example, the effect displayed on the electronic device can be seen in the interface shown in Figure 15B (1). The user can input the user's unstructured memory information "Please write down my ID number as 1305*******18, effective date as November 25, 2023, and expiration date as November 25, 2033". Then, a memory service card is generated in the interface. The memory service card is used to display structured memory information. The service memory card includes multiple user-editable display areas, which display information / content of multiple labels, such as the number "1305*******18", the person and type "my ID card", the date "effective date: November 25, 2023" and "expiration date: November 25, 2033", and the associated application "APP4". The memory service card also displays an "edit" button. The user can enter the state of editing structured memory information by clicking the button, as shown in the interface shown in Figure 15B (2). The interface displays an editing box. In the editing box, the user can edit, update or delete the information / content displayed in each display area of ​​the memory service card.

[0278] Example 3: For address memory scenarios, Table 3-1 shows a structured template that includes type, subtype, associated person, and detailed address label.

[0279] Table 3-1

[0280] When a user's unstructured memory information is "Help me remember that Zhang San lives in Nanjing First People's Hospital, and his detailed address is *******", the unstructured memory information is converted into structured memory information based on the structured template shown in Table 3-1, as shown in Table 3-2.

[0281] Table 3-2

[0282] For example, the effect displayed on the electronic device can be seen in the interface shown in Figure 15C (1). The user can input the user's unstructured memory information "Help me remember that Zhang San lives in Nanjing First People's Hospital, and the detailed address is *******". Then, a memory service card is generated in the interface. The memory service card is used to display structured memory information. The service memory card includes multiple user-editable display areas, which display information / content of multiple labels, such as the type "Nanjing First People's Hospital", the person and type "Zhang San's address", and the associated application "APP5". The memory service card also displays a "Go to Edit" button. The user can enter the state of editing structured memory information by clicking the button, as shown in the interface shown in Figure 15C (2). The interface displays an editing box. In the editing box, the user can edit, update or delete the information / content displayed in each display area of ​​the memory service card.

[0283] Example 4: For memory scenarios of events, Table 4-1 shows a structured template that includes type, event content, participants, location, start time, end time, and repeating tags.

[0284] Table 4-1

[0285] When a user's unstructured memory information is "Help me remember that I went to ******** with Zhang San for dinner at 7 pm and finished at 8:30 pm", the unstructured memory information is converted into structured memory information based on the structured template shown in Table 4-1, as shown in Table 4-2.

[0286] Table 4-2

[0287] For example, the effect displayed on the electronic device can be seen in the interface shown in Figure 15D (1). The user can input the user's unstructured memory information "Help me remember that I went to ******** with Zhang San at 7 pm and finished at 8:30 pm". Then, a memory service card is generated in the interface. The memory service card is used to display structured memory information. The service memory card includes multiple user-editable display areas, which display information / content of multiple labels, such as "going out to eat", "person and type" "my event", "start time: 19:00" and "end time: 20:30", and the associated application "APP6". The memory service card also displays an "edit" button. The user can enter the state of editing structured memory information by clicking the button, as shown in the interface shown in Figure 15D (2). The interface displays an editing box. In the editing box, the user can edit, update or delete the information / content displayed in each display area of ​​the memory service card.

[0288] In Implementation Method 3, the process of structuring user memory information in the embodiments of this application is mainly introduced, which can support the automatic classification of user memory information into different memory scenarios (categories), thereby enabling efficient organization and retrieval of memory information. This not only makes it easier for users to view and manage various types of memory information, but also improves the efficiency of users editing memory information and enhances the user's memory experience.

[0289] Implementation Method Four:

[0290] In Implementation Method 4, the implementation methods of associated memory information and applications in the embodiments of this application will be described in detail.

[0291] In this embodiment, the cloud can possess capabilities such as user intent analysis, application recommendation, and associating user memory information with application apps on the device side. Alternatively, the device-side electronic device can possess capabilities such as user intent analysis, application recommendation, and associating user memory information with application apps. Or, the cloud can possess the capabilities of user intent analysis and application recommendation, while the device-side electronic device possesses the capability of associating user memory information with application apps. Therefore, this embodiment does not specifically limit the objects that perform processes such as user opinion analysis, application recommendation, and associating user memory information with application apps on the device side.

[0292] The following section mainly introduces the implementation method of associating user memory information with the application (APP) on the client side.

[0293] For example, Figure 16 shows a flowchart of an automatic memory association application. The device can provide user information via an application association module (or automatic association module) in the cloud (or on the device itself). This user information may include, but is not limited to, the user's historical data, generated content, application usage patterns, and one or more memory records, such as memory information 1 and memory information 2 shown in Figure 16. Furthermore, the application association module in the cloud (or on the device) can analyze the user's intent based on the user information provided on the device and recommend related applications for each memory record. For example, for memory information 1, the application association module recommends related application APP 2; for memory information 2, if the associated application APP 1 has been deleted, then application APP 2 can be recommended for association.

[0294] In this application embodiment, a possible implementation of associating memory information with an application is provided, including the following steps:

[0295] Step 1: The cloud-based automatic association module receives historical data generated by the user during the use of the terminal device, user-generated content and usage patterns of various applications, as well as one or more memory information of the user stored in the memory storage module.

[0296] Step 2: The cloud-based automatic association module analyzes each piece of memory information to determine the applicable apps that can be associated with it.

[0297] In one possible implementation, the cloud-based automatic association module analyzes the user's intent for each piece of memory information and, based on semantic matching, logical reasoning, and other methods, analyzes a large amount of data to identify the application apps that need to be associated with the memory information.

[0298] Step 3: The cloud-based automatic association module sends the memory analysis results (i.e., the application apps associated with each memory information) to the client side for user use.

[0299] Step 4: If the user has deleted the app associated with the memory information, then indicate this to the cloud.

[0300] Step 5: The cloud-based automatic association module can use an automatic recommendation algorithm to identify new applications and recommend them to the client side.

[0301] In this embodiment, after the terminal-side electronic device associates memory information with an application (APP), it can provide the associated APP to the user when the user retrieves and queries the memory information. Furthermore, the user can also search for associated memory information based on the APP. For example, referring to Figure 17, when a user wants to find associated memory information based on APP 2, the electronic device can respond to the user's search and determine the memory information associated with APP 2, such as the two memory information entries: "Uncle's Birthday" and "My Birthday." These can be displayed to the user through Memory Service Card 1 and Memory Service Card 2 generated on the electronic device's display screen.

[0302] In one possible implementation, users can use intelligent commands to retrieve and query memory information or related applications.

[0303] The following describes a smart execution control process applicable to embodiments of this application. Taking an end-side electronic device executing this process as an example, after obtaining the user's memory information, the electronic device identifies the user's memory information and can convert it into long-term memory information. When the electronic device recognizes the user's intention to initiate smart control execution, it will enter the smart execution control process, as shown in Figure 18, including the following:

[0304] Step 1: Obtain interface integration and understanding information.

[0305] Interface integration and understanding information can also include the intent information entered by the user.

[0306] Step 2: Based on the interface integration understanding information, perform interface integration understanding.

[0307] Step 3: Search for matching memory information.

[0308] Unlike the structured processing of memory information, in the application recommendation process, in multi-turn task scenarios, users can supplement information about their intentions during the execution flow. This supplementary information can be text, voice, images, etc.

[0309] If no matching or relevant memory information is found, proceed to step 4 below; if a matching or relevant memory information is found, proceed to step 5 below.

[0310] Step 4: Automatically execute the control process based on the pre-training content.

[0311] Step 5: Combine the supplementary information of the user's intent to generate an atomic execution sequence for the client side and perceive the execution result.

[0312] In other words, the memory reasoning framework will combine supplementary information about the user's intent (including immediate and non-immediate queries, and can support user interruption) to generate an atomic execution sequence for execution on the client side, and will be aware of the execution results and interface changes.

[0313] Step 6: Determine whether the user's intent has been achieved.

[0314] If the user's intention is achieved, the user can be prompted that the intelligent execution information has been completed; otherwise, return to step 1 above, automatically iterate and trigger the interface fusion understanding again to generate a new round of control sequence until the user's intention is achieved.

[0315] In Implementation Method 4, the implementation method of the association between memory information and application in the embodiments of this application is mainly introduced. When a user uses the memory service card displayed on the electronic device, he / she can view the application APP related to the memory information. Even if the related APP has been deleted or removed from the store, it can be automatically associated with other APPs with similar uses or functions. In this way, the user can not only use the related application when viewing the memory information, but also search for the related memory information based on the APP, thereby bringing a better memory usage experience to the user.

[0316] It should be noted that the memory information management method shown in Figure 11 of this application embodiment can be referred to the above-described embodiments one to four of this application in specific implementation, and repeated parts will not be described again.

[0317] Based on the above embodiments, this application also provides an electronic device, which includes multiple functional modules (e.g., a communication module, a display module, a memory storage module, etc.); the multiple functional modules interact to realize the functions performed by the electronic device in the various methods described in the embodiments and / or implementations of this application. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations. For example, steps 1101 and 1102 performed by the electronic device in the embodiment shown in FIG11; steps S1201 to S1208, and S1209a, S1209b, and S1209c performed by the electronic device in the embodiment shown in FIG12; and steps S1301A, S1303A, and S1304A performed by the electronic device in the embodiment shown in FIG13A.

[0318] Based on the above embodiments, this application also provides an electronic device, which includes at least one processor and at least one memory. The at least one memory stores computer program instructions. When the electronic device is running, the at least one processor executes the functions performed by the electronic device in the various methods described in the embodiments and / or implementations of this application. For example, steps 1101 and 1102 performed by the electronic device in the embodiment shown in FIG11; steps S1201 to S1208, and S1209a, S1209b and S1209c performed by the electronic device in the embodiment shown in FIG12; and steps S1301A, S1303A and S1304A performed by the electronic device in the embodiment shown in FIG13A.

[0319] Based on the above embodiments, this application also provides a system for managing memory information, which may include the electronic devices and servers as described in the foregoing embodiments. In one possible scenario, the system may also include a transfer device for the electronic devices.

[0320] Based on the above embodiments, this application also provides a computer program product, which includes a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in the embodiments and / or implementation methods of this application.

[0321] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods described in the embodiments and / or implementation methods of this application.

[0322] Based on the above embodiments, this application also provides a chip for reading computer programs stored in a memory to implement the methods described in the embodiments and / or implementation methods of this application.

[0323] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the methods described in the embodiments and / or implementations of this application. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete devices. Those skilled in the art will understand that the embodiments and / or implementations of this application can be provided as methods, systems, or computer program products. Therefore, this application can be implemented entirely in hardware, entirely in software, or in a combination of software and hardware aspects. Furthermore, this application can be implemented as a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0324] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0325] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0326] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0327] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A management method of memory information applied to an electronic device, characterized by, Comprising: detecting a first operation of a user, the first operation being used to indicate remembering a target content based on a natural language description; obtaining, based on the first operation, a remembering information, the remembering information comprising the target content carried based on structured information.

2. The method of claim 1, wherein, The structured information comprises a plurality of labels, and a plurality of sub-contents corresponding to the plurality of labels one by one.

3. The method of claim 2, wherein, The plurality of labels are used to indicate at least one of: time, place, person, thing, action, state, attribute, relationship.

4. The method of claim 2 or 3, wherein, The structured information further comprises a scene type, the scene type being bound to a group of labels in the plurality of labels, the group of labels being part or all of the plurality of labels.

5. The method of claim 4, wherein, The scene type is an important day, or a card, or a commonly used address, or an event.

6. The method of any one of claims 2 to 5, wherein, The plurality of labels further comprise a target application or a target application type associated with the target content.

7. The method of claim 6, wherein, The target application comprises a first application and a second application, the first application being an application that the electronic device has once installed and has currently deleted, the second application being an application that the electronic device has currently installed, the first application and the second application being of the same type.

8. The method of any one of claims 1 to 7, wherein, The remembering information is displayed to the user in the form of a card.

9. The method of claim 8, wherein, The card comprises an entrance for the user to enter the target application.

10. The method of any one of claims 2 to 9, wherein, At least one of the labels, the sub-contents, and the scene type is editable or searchable by the user.

11. The method of any one of claims 1 to 10, wherein, The obtaining of the remembering information comprises: The electronic device generates the remembering information; or The electronic device receives the remembering information from a server.

12. An apparatus, comprising: The at least one processor is coupled with the at least one memory, and is used to read a program stored in the at least one memory to execute the method according to any one of claims 1 to 11.

13. A readable storage medium, characterized by, The readable storage medium has instructions stored therein, and when the instructions are executed on the electronic device, the electronic device executes the method according to any one of claims 1 to 11.

14. A chip, characterized by The chip is coupled with the memory, and is used to execute program instructions in the memory to execute the method according to any one of claims 1 to 11.

Images