Memory pattern display method and electronic equipment

Abstract

The invention provides a memory pattern display method and electronic equipment, and relates to the technical field of terminals. The method is applied to the electronic equipment and comprises the steps that in response to a first operation, a first interface is displayed, the first interface is used for displaying a memory pattern of a user, the memory pattern is used for indicating memory information of the user, the memory information is expressed through a plurality of node identifications and the relation among the node identifications, and the node identifications are used for indicating entities or events. When the memory graph is applied to the LLM, the LLM is helped to be effectively associated with other node identifications and relationships corresponding to the other node identifications through a plurality of node identifications in the memory graph and relationships among the node identifications, richer context information is obtained, understanding of the LLM on a user is deepened, and therefore in practical application, the user experience is improved. The LLM can provide personalized services for the user by using the acquired context information, so that the personalized requirements of the user are met, and the user experience is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a memory map display method and electronic device. Background Technology

[0002] With the rapid development of artificial intelligence technology, large language models (LLMs) have become a new hot topic in research and application. LLMs, with their massive parameter scale and powerful representation capabilities, have achieved remarkable success in many fields such as natural language processing, computer vision, and speech recognition. However, despite the impressive capabilities of LLMs in handling complex tasks, existing large model techniques still face numerous challenges in practical applications, especially in providing personalized services to users. Summary of the Invention

[0003] This application provides a memory map display method and electronic device, which solves the problem that LLM cannot provide personalized services to users in the prior art.

[0004] To achieve the above objectives, this application adopts the following technical solution:

[0005] In a first aspect, embodiments of this application provide a memory map display method, applied to an electronic device, the method comprising:

[0006] In response to the first operation, a first interface is displayed. The first interface is used to display the user's memory map, which is used to indicate the user's memory information. The memory information is represented by multiple node identifiers and the relationships between the multiple node identifiers. The node identifiers are used to indicate entities or events.

[0007] Based on the memory graph display method provided in this application, the associations between entities and / or events in a user's memory information can be intuitively displayed through multiple node identifiers and the relationships between them. This display method is closer to how humans store and use memory information, making it easier for users to understand and accept, and improving the user experience. When memory graphs are applied to LLM (Low-Level Management), they help LLM effectively connect multiple node identifiers and their relationships to other node identifiers and their corresponding relationships, thereby obtaining richer contextual information and deepening the LLM's understanding of the user. In practical applications, LLM can use the richer contextual information to provide personalized services to users, meet their individual needs, and improve the user experience.

[0008] Furthermore, compared to storing memory information in tensor or text form, the method of directly displaying the memory map on the first interface allows users to quickly find memory information related to entities or events according to their actual needs by using node identifiers. This effectively avoids the tedious steps of searching through the user's memory information (or memory pool list) in tensor or text form to see if it is related to a certain entity or event, simplifying the search steps for a certain entity or event and making it easier for users to quickly view their memory information.

[0009] Optionally, the electronic device may display a first interface in response to a first operation on a first application, wherein the first application may be any APP installed on the electronic device.

[0010] Optionally, the electronic device may also display a first interface in response to a first operation on the first service, wherein the first service may be any system service provided by the operating system.

[0011] In some embodiments, the method further includes: in response to a triggering operation on a first node identifier in the memory map, displaying memory information corresponding to a first event in chronological order, wherein the first event is an event indicated by the first node identifier.

[0012] It should be understood that displaying the memory information corresponding to the first event in chronological order means connecting the memory information corresponding to the first event through a timeline. This makes it easier for users to view the memory information corresponding to the first event comprehensively and clearly, and also makes it easier for users to recall and find all or part of the memory information related to the first event.

[0013] In some embodiments, the method further includes:

[0014] In response to a trigger operation on a second node identifier in the memory graph, the first graph content associated with a first entity in the memory graph is displayed, wherein the first entity is the entity indicated by the second node identifier.

[0015] In some embodiments, the first interface further includes a search control, and the method further includes:

[0016] In response to a triggering operation of the search control, a second interface is displayed, which is used to receive a third node identifier input by the user;

[0017] In response to a second operation detected on the second interface, the second graph content corresponding to the third node identifier in the memory graph is displayed.

[0018] Based on the above possible implementation methods, by entering the third node identifier in the search control, the relevant memory information of the entity or event corresponding to the third node representation can be quickly obtained.

[0019] In some embodiments, the method further includes:

[0020] In response to a third operation on the fourth node identifier in the memory graph, the fourth node identifier and the relationship corresponding to the fourth node identifier are removed from the memory graph.

[0021] Based on the above possible implementation methods, user memory information is represented visually, facilitating direct control and management of the information (e.g., filtering, editing, or deleting). Visualization can also effectively improve the efficiency of user operations on memory information.

[0022] In some embodiments, the method further includes:

[0023] The memory map displays a fifth node identifier, which is obtained based on the memory information of the logged-in user of the electronic device;

[0024] In response to the fourth operation on the fifth node identifier, the fifth node identifier and the relationship with the fifth node identifier are added to the memory graph.

[0025] In some embodiments, the method further includes:

[0026] In response to the fifth operation on the fifth node identifier, the node name of the fifth node identifier in the memory graph is modified.

[0027] In some embodiments, the method further includes:

[0028] In response to the sixth operation on the first relation in the relations, the name of the first relation is updated.

[0029] It should be understood that in practical applications, the relationships between events or entities are not static. Users can proactively manage the relationships between entities or events based on changes in the relationships between them, thereby improving the operability of events or entities.

[0030] In some embodiments, the first interface includes a display switching control, and the method further includes: in response to a triggering operation on the display switching control, displaying memory information in a list display manner.

[0031] Based on the above possible implementation methods, the display methods of memory information can be enriched, further meeting the operational needs of memory information under different practical application requirements. For example, a list can be used to view the memory information that is closest to or furthest from the current event; or a graph can be used to more intuitively view the relationship between a certain entity (and / or a certain event) and other entities (and / or other events).

[0032] Alternatively, the memory information can be displayed in a list or a graphical format.

[0033] In some embodiments, the user logged in on the electronic device is a first user, and the method further includes:

[0034] The synchronization device settings interface is displayed, indicating that the login user of the second device is also the first user;

[0035] In response to a seventh operation detected on the synchronization device settings interface, the memory information is synchronized between the electronic device and the second device.

[0036] Based on the above possible implementation methods, memory information from multiple devices belonging to the same user can be merged (or synchronized) based on the user's action of opening at least one second device, enabling the sharing of personal memory data among multiple devices. This allows for a consistent user experience even when using the same application on different devices.

[0037] In some embodiments, the method further includes: displaying an application settings interface, wherein the application settings interface displays a first application;

[0038] In response to an eighth operation detected on the application settings interface, the source of the memory information is set to include the first application.

[0039] Based on the above possible implementation methods, it is possible to achieve the fusion of personal memory data among multiple applications installed on electronic devices. Data from different applications can be integrated through memory maps. After the integrated data is applied to LLM, LLM can better understand users, thereby providing personalized services to users more accurately and efficiently.

[0040] Optionally, a user's memory information and / or memory map can be stored on the user's electronic device. This reduces the risk of memory information leakage due to network transmission and effectively protects user privacy information (such as interests and habits). In the absence of a network or with an unstable network, users can quickly access their personal memory data without waiting for a network response or connecting to a server. Furthermore, based on the memory information stored on the user's electronic device, applications or LLMs can provide users with more personalized services, such as recommending food based on the user's personal dietary habits.

[0041] Optionally, the user's memory information and / or memory map can also be stored in a cloud server. Storing the user's memory information in a cloud server can effectively prevent the risk of data loss due to hardware failure or software errors in electronic devices. Compared to the user's electronic device, the backup and recovery strategies of the cloud server are more comprehensive, ensuring rapid recovery in the event of data loss or damage. In addition, storing the user's memory information in a cloud server can also effectively reduce the load and storage pressure on electronic devices.

[0042] Optionally, the storage locations of a user's memory information and memory map can be the same or different.

[0043] Secondly, embodiments of this application provide a memory map display device, the memory map display device comprising:

[0044] A first display module is used to display a first interface in response to a first operation. The first interface is used to display the user's memory map, which is used to indicate the user's memory information. The memory information is represented by multiple node identifiers and the relationships between the multiple node identifiers. The node identifiers are used to indicate entities or events.

[0045] In some embodiments, the memory map display device further includes:

[0046] The second display module is used to respond to the trigger operation of the first node identifier in the memory map and display the memory information corresponding to the first event in chronological order. The first event is the event indicated by the first node identifier.

[0047] In some embodiments, the memory map display device further includes:

[0048] The third display module is used to display the first graph content associated with the first entity in the memory graph in response to a trigger operation on the second node identifier in the memory graph. The first entity is the entity indicated by the second node identifier.

[0049] In some embodiments, the first interface further includes a search control, and the memory map display device further includes:

[0050] The fourth display module is used to display a second interface in response to the triggering operation of the search control. The second interface is used to receive the third node identifier input by the user. In response to the second operation detected on the second interface, the second map content corresponding to the third node identifier in the memory map is displayed.

[0051] In some embodiments, the memory map display device further includes:

[0052] The removal module is used to remove the fourth node identifier and the corresponding relationship from the memory graph in response to a third operation on the fourth node identifier in the memory graph.

[0053] In some embodiments, the memory map display device further includes:

[0054] The fifth display module is used to display the fifth node identifier in the memory map. The fifth node identifier is obtained based on the memory information of the logged-in user of the electronic device.

[0055] The determination module is used to add the fifth node identifier and the relationship between the fifth node identifier and the memory graph in response to the fourth operation on the fifth node identifier.

[0056] In some embodiments, the memory map display device further includes:

[0057] The modification module is used to modify the name of the node identified by the fifth node in the memory graph in response to the fifth operation on the fifth node identifier.

[0058] In some embodiments, the memory map display device further includes:

[0059] The update module is used to update the name of the first relation in response to the sixth operation on the first relation in the relation.

[0060] In some embodiments, the first interface includes a display switching control, and the memory map display device further includes:

[0061] The switching module is used to display the remembered information in a list format in response to the trigger operation of the display switching control.

[0062] In some embodiments, the user logged in on the electronic device is the first user, and the memory map display device further includes:

[0063] The sixth display module is used to display the synchronization device settings interface, which indicates that the logged-in user of the second device is also the first user;

[0064] The synchronization module is used to synchronize memory information between the electronic device and the second device in response to the seventh operation detected on the synchronization device settings interface.

[0065] In some embodiments, the memory map display device further includes:

[0066] The seventh display module is used to display the application settings interface, which shows the first application.

[0067] The settings module is used to respond to the eighth operation detected on the application settings interface, and the source of the settings memory information includes the first application.

[0068] Thirdly, embodiments of this application provide an electronic device comprising: one or more processors; one or more memories; and one or more computer programs; wherein the one or more computer programs are stored in the one or more memories, and the one or more computer programs include instructions that, when executed by the electronic device, cause the electronic device to perform the method as described in any possible implementation of the first aspect above.

[0069] Fourthly, embodiments of this application provide a memory map display system, which includes at least one electronic device provided in the third aspect.

[0070] Fifthly, a computer-readable storage medium is provided, the computer-readable medium storing a computer program (also referred to as code or instructions) that, when the computer program code is run on a computer, causes the computer to perform the methods of any of the above aspects or any possible implementations of any of the above aspects.

[0071] In a sixth aspect, a computer program product comprising instructions is provided, the computer program product including: a computer program (also referred to as code or instructions) that, when the computer program is run on a computer, causes the computer to perform the method in any of the above aspects or any possible implementation of any of the above aspects.

[0072] It should be noted that the above-mentioned computer program code can be stored in whole or in part on the first storage medium, wherein the first storage medium can be packaged together with the processor or packaged separately from the processor, and this application does not make specific limitations in this regard.

[0073] In a seventh aspect, a chip system is provided, comprising: a processor and a memory, the memory for storing a computer program (also referred to as code or instructions), the processor for calling and running the computer program stored in the memory, such that a device or apparatus equipped with the chip system performs the method in any of the above aspects or any possible implementations of any of the above aspects.

[0074] It is understood that the beneficial effects of the second to seventh aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0075] Figure 1 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0076] Figure 2 This is a software structure block diagram of an electronic device provided in an embodiment of this application.

[0077] Figure 3 This is a flowchart illustrating a memory map construction method provided in an embodiment of this application.

[0078] Figure 4 This is a flowchart illustrating the construction of a tag library as provided in an embodiment of this application.

[0079] Figure 5 This is a schematic diagram of the structure of a constructed tag library provided in an embodiment of this application.

[0080] Figure 6 This is a schematic diagram illustrating the definition of relationships between nodes in a schema modeling method provided in an embodiment of this application.

[0081] Figure 7 This is a schematic diagram illustrating the use of event-based memory to link entity-based memory in an embodiment of this application.

[0082] Figure 8 The diagram shown is a flowchart of a memory map display method provided in an embodiment of this application.

[0083] Figures 9 to 42 This is a schematic diagram of a scenario related to memory map display provided in an embodiment of this application.

[0084] Figure 43 This is a schematic diagram of the structure of a memory map display device provided in an embodiment of this application. Detailed Implementation

[0085] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings and related embodiments. In the description of the embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between different embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. 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 association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. In the textual description of the embodiments of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship; for example, A / B can represent A or B. In this application, "first," "second," and various numerical designations are only for ease of description and are not used to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, rather than to describe a specific order or sequence.

[0086] With the rapid development of artificial intelligence technology, LLM has become a new hotspot in research and application. LLM, with its massive parameter scale and powerful representation capabilities, has achieved remarkable success in many fields such as natural language processing, computer vision, and speech recognition. However, despite the astonishing capabilities of large model techniques in handling complex tasks, existing large model techniques still face many challenges in practical applications, especially in providing personalized services to users.

[0087] For example, existing LLMs often can only respond independently to a single user input question, and cannot effectively correlate contextual or historical information from consecutive user questions to predict or recommend points of interest (POIs) that the user may be interested in. This limitation prevents LLMs from meeting users' personalized needs.

[0088] A knowledge graph is a structured representation of knowledge that graphically displays entities, concepts, and the relationships between them. If a knowledge graph can be built based on information such as users' interests, dietary preferences, experiences, and habits, then applying this knowledge graph to an LLM (Lifecycle Management) system can enable the LLM to provide more accurate and personalized service responses and more closely align with users' daily planning and decision-making processes, based on their individual needs.

[0089] Therefore, this application provides a memory graph display method. By using multiple node identifiers and the relationships between them, the method can intuitively display the associations between entities and / or events in a user's memory information, effectively using a memory graph to indicate the user's memory information. When a memory graph is applied to an LLM (Lifecycle Management System), it helps the LLM effectively associate multiple node identifiers and their corresponding relationships with other node identifiers, obtaining richer contextual information and deepening the LLM's understanding of the user. In practical applications, the LLM can utilize this acquired contextual information to provide personalized services, meeting users' individual needs and improving the user experience.

[0090] It should be understood that the memory information in this application embodiment is related information generated based on the user's historical operations on the electronic device. Different users have different memory information, and the same user may have the same or different memory information on different electronic devices. Memory information can indicate events, people, objects, times, and locations, and may involve various aspects of an individual's life, work, and studies. In this application embodiment, a user's memory information could be, for example, "Last Wednesday I had hot pot with XXX" or "This Friday I'm going to Shanghai on a business trip with my colleague Xiao Wang to sign a contract with client B," etc.

[0091] A memory graph, as the name suggests, is a graph-based data structure that can be used to represent and store a user's memory information. It is a relational network formed by connecting different entities and / or events, and the relationships between them.

[0092] Furthermore, a memory graph can be composed of nodes and edges.

[0093] Each node (or node identifier) ​​can represent an entity or an event. An entity can refer to an object with at least one attribute, i.e., a real-world transaction. For example, entities can include people, place names, companies, telephone numbers, pets, books, devices, etc.

[0094] An event can refer to a specific matter in one's studies, life, or work, such as marriage, travel, movie performance, business trip, meeting, working overtime, shopping, exercise, training, etc.

[0095] Each edge can represent a relationship between entities and / or events. Specifically, an edge can represent a relationship between entities, between events, between entities and events, or between events and entities. For example, relationships can include: friendship, teacher-student, classmate, colleague, business partner, family, marital, romantic, etc.

[0096] It should be understood that memory maps can represent a user's memory information in a structured form, making it easier for machines (such as computers) to understand and process this information. Furthermore, memory maps can be visualized using a graphical interface, allowing users to intuitively understand different entities and / or events and the relationships between them.

[0097] Memory maps can be applied to AI agents or LLMs. For example, when a memory map is applied to an AI agent, the AI ​​agent can simulate the role of a user's personal assistant, helping the user manage personal affairs (such as scheduling, reminders, weather forecasts, ordering takeout, etc.). For instance, in a practical application, when a user asks the AI ​​agent, "What are my plans for tomorrow?", the AI ​​agent can access memory information from the memory map to view the user's calendar and answer the question.

[0098] Memory graphs can also be applied to scenarios such as personal affairs management (e.g., information recording, task progress tracking, daily planning or decision-making), intelligent search, dialogue questioning, text analysis, sentiment analysis, and data management. This application does not limit these applications in any way.

[0099] The memory map display method provided in this application can be applied to electronic devices. For example, electronic devices may include, but are not limited to, personal computers (PCs), mobile phones, tablets, wearable devices (e.g., watches, bracelets, helmets, smart glasses, etc.), augmented reality (AR) / virtual reality (VR) devices, mixed reality (MR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), in-vehicle devices, smart screens, smart home devices (e.g., smart TVs, smart speakers, smart cameras, and electronic door locks), servers, and motion-sensing game consoles in human-computer interaction scenarios, etc. This application does not impose any limitations on the specific type of electronic device.

[0100] See Figure 1This is a schematic diagram of the hardware structure of an electronic device 100 provided in this application. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 131, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

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

[0102] For example, when the electronic device 100 is a mobile phone or a tablet computer, it may include all the components shown in the figure, or it may include only some of the components shown in the figure.

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

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

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

[0106] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0107] In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface. Both the I2S interface and the PCM interface can be used for audio communication.

[0108] In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be located in the same device.

[0109] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

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

[0111] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1.

[0112] In some embodiments, at least some functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be disposed in the same device.

[0113] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0114] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. Wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. GNSS can include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0115] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0116] The display screen 194 is used to display images, videos, etc., such as various display interfaces in the embodiments of this application. The display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0117] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0118] Electronic device 100 can implement audio functions through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0119] The audio module 170 is used to convert digital audio signals into analog audio signals for output, and also to convert analog audio inputs into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0120] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or hands-free calls through the speaker 170A. For example, the speaker can play the comparison analysis results provided in the embodiments of this application.

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

[0122] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 100 may have at least one microphone 170C. In some embodiments, electronic device 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0123] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

[0124] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0125] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0126] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0127] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0128] See Figure 2 This is a schematic diagram of the software structure of an electronic device according to an embodiment of this application. The operating system in the electronic device can be... or Operating systems such as OS. Here, we will take HarmonyOS, the operating system for electronic devices, as an example for explanation.

[0129] In some embodiments, the HarmonyOS system can be divided into four layers, including the kernel layer, system service layer, framework layer, and application layer, with the layers communicating with each other through software interfaces.

[0130] like Figure 2 As shown, the kernel layer includes the kernel abstract layer (KAL) and the driver subsystem. The KAL contains multiple kernels, such as the Linux Kernel for Linux systems and the LiteOS kernel for lightweight IoT systems. The driver subsystem can include a hardware driver foundation (HDF). The hardware driver foundation provides unified peripheral access capabilities and a framework for driver development and management. A multi-kernel kernel layer can select the appropriate kernel for processing based on system requirements.

[0131] The system service layer is the core capability set of the HarmonyOS system. It provides services to applications through the framework layer. This layer may include a set of basic system capability subsystems, a set of basic software service subsystems, a set of enhanced software service subsystems, and a set of hardware service subsystems.

[0132] The system's basic capability subsystems provide foundational capabilities for the operation, scheduling, and migration of distributed applications on HarmonyOS devices. These may include subsystems such as distributed soft bus, distributed data management, distributed task scheduling, Ark multi-language runtime, common base libraries, multi-modal input, graphics, security, artificial intelligence (AI), and user program frameworks. Among these, the Ark multi-language runtime provides runtime environments for C, C++, or JavaScript (JS) languages ​​and basic system class libraries. It can also provide a runtime environment for Java programs statically generated using the Ark compiler (i.e., the parts of the application or framework layer developed using the Java language).

[0133] The basic software service subsystem provides common and general software services for the HarmonyOS system. These may include subsystems such as event notification, telephony, multimedia, design for X (DFX), and MSDP & DV.

[0134] The enhanced software service subsystem provides HarmonyOS with differentiated enhanced software services for different devices. It may include dedicated subsystems for smart screens, wearables, and the Internet of Things (IoT).

[0135] The hardware service subsystem provides hardware services for the HarmonyOS system. This may include subsystems such as location services, biometric recognition, wearable hardware services, and IoT hardware services.

[0136] The framework layer provides HarmonyOS application development with user program frameworks and capability frameworks in multiple languages, including Java, C, C++, and JS; two user interface (UI) frameworks (JavaUI framework for Java and JS UI framework for JS); and various multi-language framework application programming interfaces (APIs) for exposing software and hardware services. The APIs supported by HarmonyOS devices will vary depending on the degree of system componentization.

[0137] The application layer includes system applications and third-party applications (or extended applications). System applications can include applications that are installed by default on electronic devices, such as the desktop, control bar, settings, and phone. Extended applications can be non-essential applications developed and designed by the electronic device manufacturer, such as applications for managing electronic devices, migrating between devices, note-taking, and weather. Third-party non-system applications can be applications developed by other manufacturers that can run on the HarmonyOS system, such as games, navigation, social networking, or shopping applications.

[0138] It provides the ability to run background tasks and a unified data access abstraction. The process area (PA) primarily supports functional applications (FAs), such as providing computing power as a background service or providing data access capabilities as a data warehouse. Applications developed based on FAs or PAs can implement specific business functions, support cross-device scheduling and distribution, and provide users with a consistent and efficient application experience.

[0139] Multiple electronic devices running the HarmonyOS system can achieve hardware cooperation and resource sharing through distributed soft bus, distributed device virtualization, distributed data management, and distributed task scheduling.

[0140] It should be noted that, Figure 2 The software structure of the electronic device shown is merely an illustrative example and does not limit the specific structure of the electronic device.

[0141] The following is combined with Figure 1 The electronic device shown illustrates the memory map display method provided in the embodiments of this application.

[0142] In this embodiment of the application, before a user can quickly open a memory map using an electronic device, a memory map corresponding to the user's memory information can be constructed first. For example... Figure 3 The diagram shown is a flowchart of the memory map construction method 300 provided in an embodiment of this application. The execution subject of this method 300 can be an electronic device. See also... Figure 3 The memory map construction method 300 may include the following steps S301 to S304.

[0143] Step S301: The electronic device acquires the user's multimodal data.

[0144] It should be understood that a user's multimodal data can refer to various types of data used to construct a memory graph, including but not limited to one or more types of data such as text data, image data, audio data, or video data. In the embodiments of this application, multimodal data can be data generated by users of electronic devices on platforms such as social media, shopping platforms, and online forums.

[0145] Multimodal data can also include diverse data such as SMS messages, contact information, visual data from photo libraries, and health and behavior data detected by smart wearable devices.

[0146] Multimodal data can also be obtained from log information formed by human-computer interaction between users and electronic devices (such as mobile phones, computers, etc.). These log information records users' conversation content, shopping records, ticket booking records, browsing records, search history, etc.

[0147] Multimodal data can also be obtained from photos, videos, text, and other content posted by users on social media platforms, as well as information from interactions with other users (such as chat logs).

[0148] Multimodal data can also be obtained from personal files and data (such as documents, photos, music, videos, etc.) stored on storage devices such as cloud storage, hard drives, and USB flash drives. This application does not limit the method of obtaining multimodal data or the specific content obtained.

[0149] It should be noted that the multimodal data acquired by the electronic device in step S301 can also come from other devices besides the electronic device itself.

[0150] For example, assuming the electronic device in this embodiment is a mobile terminal, the user can log in to the same account information on the mobile terminal and other devices (such as tablets, smartwatches, etc.) to achieve cross-device data sharing and integration. Based on this, the mobile terminal can not only process the multimodal data it collects, but also access and integrate multimodal data obtained from other devices that have logged in with the same account, thereby obtaining richer and more comprehensive data.

[0151] In step S302, the electronic device performs recognition processing on the multimodal data to obtain memory information.

[0152] It should be understood that memory information identified from multimodal data may include one or more modalities such as text data, image data, audio data, or video data.

[0153] The multimodal data acquired by electronic devices may not include memory information. In order to avoid processing irrelevant data, reduce the consumption of computing resources, and improve data processing efficiency, the multimodal data can be identified and processed after the electronic device acquires the user's multimodal data to obtain memory information.

[0154] For example, suppose the multimodal data of a user acquired by an electronic device is "The scenery here is so beautiful". Since there is no specific event, person or other related information in "The scenery here is so beautiful", the above information does not belong to memory information.

[0155] It should be noted that, in this embodiment, the memory information may remain unchanged in terms of events, relationships, or attributes for a relatively long period of time. The memory information may have the characteristic of long-term (or permanent) storage, facilitating subsequent data utilization (e.g., analysis and decision-making, business optimization, etc.). In other words, if the relevant information changes in terms of events, relationships, or attributes after a preset time, it can be determined that the relevant information does not belong to the memory information. The electronic device can determine the preset time from the acquired multimodal data.

[0156] As an example, and not a limitation, a one-time triggered memory may not be considered memory information. For example, the message "Set an alarm for me in 30 minutes" becomes invalid after 30 minutes. This memory cannot be used for subsequent data processing and does not have the characteristic of long-term storage. Therefore, this information may not be considered memory information.

[0157] Short-term sustained memory or short-duration sustained memory may not be considered memory information. For example, the information "Please remember that my parking space in the mall is A507" may not be considered memory information if, after a preset time, my car is no longer parked in the parking space corresponding to A507 after I leave the mall. The relationship between my car and the parking space A507 changes, and this information becomes unusable. Therefore, there is no need to store this information for a long time, and it may not be considered memory information. This application does not impose any limitations on this.

[0158] In some embodiments, supervised fine-tuning (SFT) or prompt methods can be used to determine memory information from multimodal data; alternatively, any algorithm from long short-term memory (LSTM), elastic weight consolidation (EWC), attention mechanism, etc., can be used to determine memory information from multimodal data.

[0159] In some embodiments, memory information can be stored in the electronic device, which reduces the risk of memory information leakage due to network transmission and effectively protects user privacy information (such as interests, habits, etc.). This allows users to quickly access their personal memory data without waiting for a network response or connecting to a server, even in the absence of a network or with an unstable network. Furthermore, based on the memory information stored on the electronic device, applications or LLMs can provide users with more personalized services, such as recommending food based on the user's personal dietary habits.

[0160] In some embodiments, memory information may also be stored in a cloud server. Storing user memory information in a cloud server can effectively prevent the risk of data loss due to hardware failure or software errors in electronic devices. Compared to user electronic devices, cloud servers have more robust backup and recovery strategies, ensuring rapid recovery in the event of data loss or corruption. Furthermore, storing user memory information in a cloud server can effectively reduce the load and storage pressure on electronic devices.

[0161] In step S303, the electronic device classifies the memory information to obtain the category label to which the memory information belongs.

[0162] It should be understood that after the memory information is obtained by recognizing and processing multimodal data, a pre-configured tag library (also known as a tag system) can be used to classify the memory information, further determine the category to which the memory information belongs, and obtain the category tag to which the memory information belongs.

[0163] In this embodiment, the tags in the tag library originate from diverse sources. The tag library can include not only tags formed based on big data analysis and processing, but also tags derived from the memory information of logged-in users on electronic devices. In other words, the tags in the tag library can be further enriched and refined based on basic tags and each user's unique memory information, thus constructing a more comprehensive tag system. Furthermore, the above method can effectively expand the tags in the tag information library, allowing different users' memory maps to include node identifiers based on user feedback, further satisfying users' personalized display needs for their memory maps.

[0164] In some embodiments, such as Figure 4 The diagram shown is a flowchart of a tag library construction method provided in an embodiment of this application. See also... Figure 4 The process of building a tag library may include: acquiring memory information; determining a first tag based on the memory information; determining whether the first tag meets preset conditions; if the first tag meets preset conditions, then storing the first tag; otherwise, if the first tag does not meet preset conditions, then in response to user operation, determining whether to store the first tag.

[0165] It should be understood that the user's memory information can be obtained from the multimodal data based on the aforementioned steps S301 and S302. The specific content of the memory information can be understood by referring to the aforementioned content, and will not be repeated here.

[0166] In some embodiments, the first label can be determined based on the memory information using any of the following algorithms: rule matching and keyword extraction algorithms, machine learning algorithms (e.g., Naive Bayes, Support Vector Machine, Deep Learning, etc.), clustering analysis algorithms, and social attribute and behavioral feature inference algorithms. It is easy to understand that in practical applications, the number of first labels determined by the electronic device based on the memory information can include at least one.

[0167] In some embodiments, the preset conditions can be determined based on the frequency of the first tag appearing in the user's memory information.

[0168] It should be understood that the first tag that meets the preset conditions can be stored in the tag library to build a tag library corresponding to the user's memory information, so that the memory information can be classified and extracted by using the tags in the tag library to obtain the user's memory map.

[0169] For example, if the frequency of the first tag in the user's memory information is greater than the preset frequency, the first tag can be stored directly. The preset frequency can be pre-configured or custom-defined. In other words, if the memory information determines that the first tag is a high-frequency tag, then the first tag is stored directly.

[0170] Correspondingly, if the frequency of the first tag in the user's memory is less than or equal to a preset frequency, the system can respond to the user's action and determine whether to store the first tag. In other words, if the memory information indicates that the first tag is a low-frequency tag, then the system can use human-computer interaction to determine whether to store the first tag through user action.

[0171] The user operation can be an operation to store the first tag. For example, the operation to store the first tag can be a confirmation operation on the first tag; it can also be a modification operation on the first tag followed by a confirmation operation.

[0172] Specifically, when the operation of storing the first tag is a confirmation operation of the first tag, the electronic device can detect the confirmation operation and directly store the first tag.

[0173] When the operation of storing the first tag is a modification operation and a confirmation operation of the first tag, after the electronic device detects the modification operation, the user can modify the first tag (specifically, the name of the first tag). Afterwards, after the electronic device detects the confirmation operation, it stores the modified first tag.

[0174] Furthermore, user actions can also include actions that do not store the first tag. For example, actions that do not store the first tag could be an ignore action or a delete action. For instance, if an electronic device detects an ignore action, it may choose not to store the first tag.

[0175] like Figure 5 The diagram shown is a structural schematic of a tag library provided in an embodiment of this application. (See also...) Figure 5 The tag library can include at least one first-level tag such as event tags, relationship tags, and attribute tags. Each first-level tag can include at least one second-level tag. For example, the event tag can include at least one second-level tag such as marriage, travel, dining, performances / movies, work, cars, shopping, medical care, sports and fitness, and learning / training; the relationship tag can include at least one second-level tag such as friends, teachers, students, classmates, colleagues, partners, family, marital relationships, legal relationships, and romantic relationships; and the attribute tag can include at least one second-level tag such as people and pets. Each second-level tag can further include at least one third-level tag. For example, the work tag can include at least one third-level tag such as business trips, meetings, and overtime; the family tag can include at least one third-level tag such as father, mother, and wife; the people tag can include at least one third-level tag such as name, age, place of origin, gender, and occupation; and the pet tag can include at least one third-level tag such as name, species, and age.

[0176] It's easy to understand that in a tag library, tags can be structured hierarchically. Each tag can include one or more major category tags, each major category tag can further include one or more sub-category tags, each sub-category tag can further include one or more child tags, and so on. This clear hierarchical relationship allows electronic devices or systems (such as an LLM that calls the tag library) to accurately understand and process the tags in the tag library, improving data processing efficiency.

[0177] Furthermore, compared to storing tags as tensors or text lists, the above... Figure 5 The tag storage method shown also facilitates operations on each tag in the tag library (such as filtering operations).

[0178] Based on the above Figure 4 The method shown can be used to build a tag library. Then, the built tag library can be used to classify the user's memory information and obtain category tags corresponding to the memory information.

[0179] It should be understood that the category labels after classification can be... Figure 5 The tags shown are from the tag library. As an example and not a limitation, suppose an electronic device receives a text message: "You have successfully booked an appointment with Dr. Li in Department A of XYZ Hospital at 10:00 AM on XX / XX / XX, with appointment number 123456." The above text message can be identified and classified to obtain a memory message, and the category tag corresponding to this memory message is "medical".

[0180] In some embodiments, the SFT method or the prompt method can also be used to determine the category label corresponding to the memory information. Furthermore, methods for determining the category label corresponding to the memory information may include, but are not limited to, Naive Bayes Classifier, Support Vector Machine (SVM), Decision Tree, Random Forest, Neural Network, K-means Clustering, Hierarchical Clustering, Association Rule Mining, and Topic Model algorithms.

[0181] In step S304, the electronic device extracts information from the memory information according to the category label, obtains multiple node identifiers and the relationship between the multiple node identifiers, and constructs a memory map based on the multiple node identifiers and the relationship between the multiple node identifiers.

[0182] It should be understood that node identifiers are used to indicate entities or events. Correspondingly, the relationships between multiple node identifiers can include relationships between entities, relationships between entities and events, and relationships between events.

[0183] In some embodiments, during the process of extracting information from memory based on category labels, the specific information extracted for each label can be determined according to a predefined ontology (schema) modeling method corresponding to that label. In other words, different labels extract different information, and different memory information can be characterized by the different information extracted.

[0184] In the embodiments of this application, the predefined schema modeling method can follow the property graph modeling method, specifically including five types of nodes: concept nodes, entity nodes, abstract event nodes, concrete event nodes, and memory information nodes.

[0185] The specific type of a concept node can be a concept type; the tag corresponding to a concept node can be a tag from a tag library, such as "travel"; the name corresponding to a concept node can be the same as the tag, such as "travel"; concept nodes are mainly used for classification, and concept nodes do not need to be instantiated during the construction of the memory graph.

[0186] The specific type of an entity node can be an entity type; the tag corresponding to an entity node can correspond to an entity tag in a tag library, such as "person"; the name corresponding to an entity node can be the name of the entity, such as "Zhang San"; the attribute corresponding to an entity node can be the attribute that the entity has, such as a person having attributes like name, gender, and age; entity nodes can be used to instantiate specific entity objects. In the process of constructing a memory graph, entity nodes are usually a type of node that needs to be instantiated.

[0187] Abstract event nodes correspond to abstract event types. The tags within an abstract event node can be derived from the event types under event tags in the tag library; for example, the tag could be "travel event." The name of an abstract event node can be the name of a specific event node, such as "Thailand travel." An abstract event node can represent an event. The attributes of an abstract event node can be attributes of a specific event, such as event trigger words or time. During memory graph construction, abstract event nodes are optional; that is, they may or may not exist for specific memory information. Abstract event nodes are typically a type of node that needs to be instantiated.

[0188] Specific event nodes correspond to specific event types. The tags within specific event nodes can be derived from the tags of abstract event nodes. For example, if the tag for an abstract event node is "Business Trip to Shanghai," then the tag for a specific event node could be "Business Trip to Shanghai on [Date]." The name of a specific event node can be the same as its tag name, such as "Business Trip to Shanghai on [Date]." Specific event nodes can represent a specific event. The attributes of specific event nodes can also be attributes of the specific event, such as event trigger words or time. During the memory graph construction process, specific event nodes are obtained by instantiating abstract event nodes.

[0189] Memory information nodes can be of various types, including those representing memory content. Their labels can be based on event type tags to determine the memory type, such as "travel memory." Memory information nodes can indicate specific memory content (i.e., the user's memory information). Their attributes can correspond to the attributes of the memory content, such as the time or location of the memory. Memory information nodes can also represent specific event-related memory content. During the construction of a memory graph, memory information nodes are typically the type of nodes that need to be instantiated.

[0190] like Figure 6 The diagram shown is a related schematic of a predefined schema modeling method provided in an embodiment of this application. See also... Figure 6Concept nodes can be represented using abstract event nodes, concrete event nodes, and entity nodes. There can be ownership relationships between concept nodes and abstract event nodes, between concept nodes and concrete event nodes, between abstract event nodes and concrete event nodes, and between concept nodes and entity nodes. Concept nodes can also have hierarchical relationships, causal relationships, correlation relationships, etc.

[0191] There can be relationships such as description and details between memory information nodes and specific event nodes, and there can be relationships such as involvement between memory information nodes and entity nodes.

[0192] Entity nodes can be represented using tags of entity types. The attributes of the entity corresponding to each entity node can be used to define the relationships between entity nodes (corresponding to...). Figure 6 The entity relationships in the memory map are used to describe entity-based memories. Furthermore, in the memory map, specific event nodes can be used to connect entity-based memories. That is, there can be relationships such as event arguments and involvement between entity nodes and specific event nodes. Among them, event arguments, also known as event elements, are the components that describe the specific occurrence of an event, and can usually include the time, place, subject, and object of the event.

[0193] based on Figure 6 This allows for information extraction from memory information based on the category labels to which the memory information belongs, resulting in multiple node identifiers and the relationships between them. Subsequently, a user's memory graph can be constructed based on these node identifiers and their relationships.

[0194] As an example, not a limitation, such as Figure 7 The diagram shown is a schematic representation of using event-based memory to link entity-based memory according to an embodiment of this application. See also... Figure 7 Suppose that the electronic device receives two pieces of user memory information. One piece of memory information is "I am going to Shanghai on Friday with my colleague Xiao Wang to sign a contract with client B", and the other piece of memory information is "I had hot pot with Xiao Li last Wednesday".

[0195] First, it can be based on Figure 5 The tag library shown classifies the aforementioned two pieces of memory information to obtain the category tag to which each piece of memory information belongs. For example, see [link to example]. Figure 7We can obtain the first-level label corresponding to the two memory information above as "event label". Further, the second-level label corresponding to "I am going to Shanghai on Friday with my colleague Xiao Wang to sign a contract with client B" is "work", and the second-level label corresponding to "I had hot pot with Xiao Li last Wednesday" is "catering". Furthermore, the third-level label corresponding to "I am going to Shanghai on Friday with my colleague Xiao Wang to sign a contract with client B" can be "business trip".

[0196] Secondly, based on Figure 6 Information is extracted from each memory information according to the schema modeling method corresponding to different predefined category labels, so as to obtain multiple node identifiers in each memory information and the relationships between multiple node identifiers. Based on the above example, multiple entities involved in the above two memory information and the relationships between multiple entities can be extracted to obtain multiple entity node identifiers and the relationships between multiple entity node identifiers.

[0197] In the example above, it is assumed that the schema modeling methods corresponding to the predefined different category labels specifically include: “event label”, “work”, “food” and “business trip” can correspond to concept nodes. Under the concept node “business trip”, there can also be an abstract event node “business trip to Shanghai”. Under the abstract event node “business trip to Shanghai”, there can be a specific event node “business trip to Shanghai on June 14, 2024”. Furthermore, under the specific event node “business trip to Shanghai on June 14, 2024”, there can be complete memory information “I am going to Shanghai on Friday with my colleague Xiao Wang to sign a contract with client B”.

[0198] Similarly, based on another memory information, "I had hot pot with Xiao Li last Wednesday," the concept node of "catering" can include the abstract event node of "eating hot pot." Furthermore, the abstract event node of "eating hot pot" can include the specific event node of "eating hot pot on June 5, 2024." The specific event node of "eating hot pot on June 5, 2024" can also include the complete memory information "I had hot pot with Xiao Li last Wednesday."

[0199] Based on the aforementioned predefined schema modeling method, information extraction is performed on the memory information "I'm going to Shanghai on Friday with my colleague Xiao Wang to sign a contract with client B." This yields three entity node identifiers: "I," "Company B," and "Xiao Wang." Figure 6It can be concluded that there is an "involvement" relationship between the aforementioned memory information nodes and the aforementioned three entity node identifiers; there can be a "colleague" relationship between the two entity nodes "I" and "Xiao Wang"; based on the "employment" attribute value of the entity node "I", an "employment" relationship can be established between "I" and "Company A"; furthermore, there is a "customer" relationship between the two entity nodes "Company A" and "Company B"; based on the "colleague" relationship between the two entity nodes "I" and "Xiao Wang", it can be further determined that there is also an "employment" relationship between "Xiao Wang" and "Company A".

[0200] Similarly, by extracting information from another memory message, "I had hot pot with Xiao Li last Wednesday," we can obtain two entity node identifiers, "I" and "Xiao Li." There is an "involvement" relationship between these two entity node identifiers and the corresponding memory information nodes. The entity node identifiers "I" and "Xiao Li" can have a "classmate" relationship.

[0201] Finally, based on the obtained entity node identifiers and the relationships between them, a corresponding memory graph can be constructed. This can be achieved by constructing the memory graph based on the two sets of memory information mentioned above. Figure 7 The memory map shown in the dashed box.

[0202] It should be noted that during program implementation, triples can be used to represent multiple extracted node identifiers (or nodes) and the relationships between them. Specifically, a triple can be represented as:<head,relation,tail> In this context, head can represent an entity or an event; tail can also represent an entity or an event; and relation can represent the relationship between head and tail, that is, at least one relationship between entities, between entities and events, or between events.

[0203] In some embodiments, the memory map may be stored in the user's electronic device. In other embodiments, the memory map may also be stored in a cloud server. This application does not limit this aspect.

[0204] Optionally, the user's memory information and memory map can be stored in the same location. For example, both the user's memory information and memory map can be stored in the user's electronic device. Alternatively, the user's memory information and memory map can be stored in different locations. For instance, the user's memory information can be stored on a cloud server, and the memory map can be stored in the user's electronic device. In practical applications, the electronic device can access the memory information stored on the cloud server to construct or modify the memory map.

[0205] It is easy to understand that, based on the steps S301 to S304 above, a corresponding memory map can be constructed based on the user's memory information. The human brain remembers information by establishing connections between memories through the dendrites and axons of neurons. Based on the above method, the associations between entities and / or events in the user's memory information are intuitively displayed through multiple node identifiers and the relationships between multiple node identifiers. This makes the constructed memory map closer to the way the human brain remembers information, easier for users to understand and accept, and improves the efficiency of memory information aggregation.

[0206] The following describes a memory map display method provided by an embodiment of this application, such as... Figure 8 The diagram shown is a flowchart illustrating a memory map display method according to an embodiment of this application. This memory map display method 800 can be applied to electronic devices. See also... Figure 8 The memory map display method 800 may include step S801.

[0207] In step S801, the electronic device responds to the first operation by displaying a first interface. The first interface is used to display the user's memory map. The memory map is used to indicate the user's memory information. The memory information is represented by multiple node identifiers and the relationships between the multiple node identifiers. The node identifiers are used to indicate entities or events.

[0208] It should be understood that the first operation can refer to the triggering operation that displays the first interface. This triggering operation can be a click operation, a long press operation, a long press and click operation, a double click operation, a touch operation, or a swipe operation, etc.; the triggering operation can also be a selection operation entered by the user through a physical button on the electronic device; the triggering operation can also be an air gesture operation, a face recognition operation, a voice command operation, etc., detected by the user through the camera, microphone, or other sensors of the electronic device.

[0209] In some embodiments, the electronic device may display a first interface in response to a first operation on a first application, wherein the first application may be any application (APP) installed on the electronic device. For example, any APP may be a "personal assistant" APP.

[0210] In some embodiments, the electronic device may also display a first interface in response to a first operation on a first service, wherein the first service may be any system service provided by the operating system. For example, any system service may be a memory information management service. In practical applications, the memory information management service may be initiated through an app such as a smart assistant.

[0211] The following will take an electronic device as a mobile phone terminal as an example, and combine the above two display methods of the first interface to provide an exemplary description of the memory map display method provided in the embodiments of this application.

[0212] In some embodiments, see Figure 9 The mobile terminal's desktop (900) can display multiple pre-installed apps, including a clock app, calendar app, gallery app, memo app, file manager app, email app, music app, calculator app, video player app, fitness and health app, weather app, browser app, smart living app, settings app, voice recorder app, app store app, personal assistant app (901), camera app, contacts app, phone app, and messaging app, etc. Of course, in... Figure 9 The mobile terminal shown may also have other apps pre-installed, such as mobile management apps, but this application does not limit this.

[0213] The first method involves the mobile terminal displaying a first interface in response to a first operation on a first application.

[0214] For example, see Figure 9 Assuming the first application is Personal Assistant APP 901, which corresponds to the user's memory map, the user can tap the application icon corresponding to Personal Assistant APP 901 on the user's mobile terminal desktop 900 to select and launch Personal Assistant APP 901. After launching, Personal Assistant APP 901 can directly display... Figure 10 The display interface shown is 1000, in Figure 10 The user's memory map can be displayed in a list format in the shown display interface 1000.

[0215] In some embodiments, after the personal assistant APP 901 is launched, it can also directly display something like this. Figure 11 The memory map display interface shown is 1100. Figure 11 The memory map display interface 1100 shown can display the user's memory map in a graphical display manner.

[0216] The second type involves the mobile terminal responding to the first operation of the first service by displaying the first interface.

[0217] For example, assuming the first service is a memory information management service, and the smart assistant that activates the aforementioned memory information management service is specifically a voice assistant, where the voice wake-up command for this voice assistant is "Xiao A", then the user can send the voice wake-up command "Xiao A" to the mobile terminal. After receiving the voice wake-up command "Xiao A", the mobile terminal can activate the voice assistant, and after the voice assistant is activated, it can display something like... Figure 12 The voice wake-up interface 1200 is shown. Next, the user can send the voice command "Open Memory Information Management" to the activated voice assistant, see [link to relevant documentation]. Figure 13 When the voice assistant recognizes the voice command "Open Memory Information Management," it can display the corresponding voice recognition interface 1300. After the voice assistant recognizes the voice command "Open Memory Information Management," it can jump to display as follows: Figure 10 The display interface shown is 1000 or as follows Figure 11 The memory map display interface shown is 1100.

[0218] In this embodiment of the application, the first interface may refer to, for example: Figure 11 The memory map display interface 1100 is shown. This first interface can display a display switching control. The mobile terminal can switch the display mode of the memory information in response to the trigger operation of the display switching control.

[0219] For example, in response to a trigger operation on the display switching control, the mobile terminal can switch the display method of the remembered information from a graphical display to a list display. Alternatively, in response to a trigger operation on the display switching control, the mobile terminal can switch the display method of the remembered information from a list display to a graphical display.

[0220] It should be understood that the number of display toggle controls can correspond to the number of display modes. For example, display modes may include list display and graph display, so see [link to relevant documentation]. Figure 11 In the memory graph display interface 1100, there can be two corresponding display switching controls: a "list display" control 1101 and a "graphological display" control 1102. The "list display" control 1101 displays memory information in a list format, while the "graphological display" control 1102 displays memory information in a graph format. When the mobile terminal detects user interaction with the "list display" control 1101, it can display the memory information in a list format. When the mobile terminal detects user interaction with the "graphological display" control 1102, it can display the memory information in a graph format.

[0221] Of course, the number of display switching controls can also be one. For example, the display method of the memory information can be pre-configured according to a preset order. Assuming the preset order is list display and graph display, a display switching control can be set in the first interface. When the mobile terminal detects the user's first operation of the display switching control, the memory information is displayed in a list format; when the mobile terminal detects the user's second operation of the display switching control, the memory information is displayed in a graph format. This application embodiment does not limit the specific setting form of the display switching control.

[0222] It should be noted that if the above two possible examples are displayed as follows: Figure 10After the display interface 1000 is shown, a "list display" control 1001 and a "graphical display" control 1002 can be set in the display interface 1000. The mobile terminal can display the first interface after detecting the user's operation of the "graphical display" control 1002.

[0223] In this embodiment, the display methods of memory information include, but are not limited to, list display and graph display. Based on the display switching control set in the first interface, not only can the display methods of memory information be enriched, but the operational needs of memory information under different practical application requirements can also be further met. For example, a list can be used to view the memory information closest to or furthest from the current event; similarly, a graph display can provide a more intuitive view of the association between a certain entity (and / or event) and other entities (and / or other events).

[0224] It's easy to understand that in the first interface, the user's memory information can be represented through multiple node identifiers (or nodes) and the relationships between these node identifiers. Each node identifier can be used to indicate an entity or an event. Figure 11 The memory map display interface 1100 shown is the first interface as an example. Figure 11 The memory map display interface 1100 shown may include six node identifiers. Five node identifiers are used to indicate the corresponding entities, and one node identifier is used to indicate the event. Specifically, the five node identifiers used to indicate entities are "I", "Zhang San", "Li Si", "Wang Wu" and "Zhao Liu", and the node identifier used to indicate the event is "going on a trip".

[0225] In the memory map display interface 1100, the correspondence between six node identifiers clearly shows the memory information of "I". Here, "I" can refer to the user corresponding to the mobile terminal. The relationships between the six node identifiers can include: a "boss" relationship between "I" and "Zhang San", a "girlfriend" relationship between "I" and "Li Si", a "classmate" relationship between "I" and "Wang Wu", a "friend" relationship between "I" and "Zhao Liu", a "traveler" relationship between "I" and "going on a trip", a "boss" relationship between "Zhang San" and "Li Si", a "father" relationship between "Zhang San" and "Wang Wu", and a "traveler" relationship between "Li Si" and "going on a trip".

[0226] It is worth noting that in the memory graph display interface 1100, at least one entity and / or at least one event that are related to "me" can be displayed, centered on "me", according to preset rules, as well as the relationship between at least one entity and / or at least one event.

[0227] For example, based on the weight of the relationship between other entities or events and the entity "I", the system can display at least one entity and / or at least one event that are related to "I", as well as the relationship between at least one entity and / or at least one event, with "I" as the center.

[0228] Alternatively, you can center on "me" and display a preset number of other entities and / or events that are related to "me", as well as the preset number of relationships between entities or events.

[0229] Alternatively, based on the screen size of the mobile terminal, the system can display a corresponding number of entities and / or events related to "me," centered on "me," as well as the relationships between these entities and / or events.

[0230] In some embodiments, the mobile terminal may respond to a trigger operation on the second node identifier in the memory graph to display the first graph content associated with the first entity in the memory graph, wherein the first entity is the entity indicated by the second node identifier, and the second node identifier is one of a plurality of node identifiers in the memory graph.

[0231] It should be understood that the content of the first atlas can be a part (or a partial) of the atlas that is associated with the first entity.

[0232] As mentioned above Figure 11 Taking the memory map in the memory map display interface 1100 as an example, assuming the second node identifier is the node identifier corresponding to "Li Si", then the mobile terminal can display the following after detecting the user's operation "Li Si": Figure 14 The display interface 1400 shown can display other entities associated with "Li Si", as well as the relationships between "Li Si" and other entities, with "Li Si" as the center.

[0233] For example, in the display interface 2000, five entities that are related to "Li Si" can be displayed. These five entities can specifically include "Old Li", "Xiao Zhang", "Xiao Yang", "Xiao Wang", and "X". There is a "father" relationship between "Li Si" and "Old Li"; there is a "father" relationship between "Li Si" and "Xiao Zhang"; there is a "friend" relationship between "Li Si" and "Xiao Yang"; there is a "colleague" relationship between "Li Si" and "Xiao Wang"; there is a "company" relationship between "Li Si" and "X"; there is a "husband and wife" relationship between "Old Li" and "Xiao Zhang"; and there is a "company" relationship between "Xiao Wang" and "X".

[0234] In the example above, the first entity indicated by the second node is Li Si; the trigger operation is the user's operation of "Li Si" to display the operation of the display interface 1400. The content of the first graph corresponds to the memory graph displayed within the dotted line in the display interface 1400, which may include "Li Si", five entities associated with "Li Si", the relationship between "Li Si" and the five entities, and the relationship between the five entities.

[0235] In addition to displaying the memory map of the first entity corresponding to the second node identifier in the manner described above, in other possible implementations, a search control can also be set in the first interface so that the mobile terminal responds to the triggering operation of the search control and displays the second interface, which is used to receive the third node identifier input by the user; then, the mobile terminal can respond to the second operation detected on the second interface and display the second map content in the memory map corresponding to the third node identifier.

[0236] It should be understood that the third node identifier can be used to indicate a certain entity or a certain event. Correspondingly, if the third node identifier indicates a certain entity, the content of the second graph can be a portion of the memory graph associated with the aforementioned entity; if the third node identifier indicates a certain event, the content of the second graph can be a portion of the memory graph associated with the aforementioned event.

[0237] As an example, not a limitation, in Figure 11 The memory map display interface 1100 shown can also display a "search" control 1103. After the mobile terminal detects the user's operation of the "search" control 1103, it can display the following: Figure 15 The search interface 1500 shown can display a search box 1501 and a "cancel" button 1502. After the mobile terminal detects the user's operation and enters the corresponding search information (i.e., the third node identifier) ​​in the search box 1501, it can display the memory map interface corresponding to the search information.

[0238] Assuming a user enters the search term "Xiaoming" into search box 1501, when the mobile terminal detects that the user has entered "Xiaoming" into search box 1501, it can display the following: Figure 16 The memory map display interface 1600 shown can display at least one entity and / or at least one event that is related to "Xiaoming", with "Xiaoming" as the center, as well as the relationship between at least one entity and / or at least one event.

[0239] For example, the memory graph display interface 1600 can display four entities related to "Xiaoming" and one event. The four entities can include "Xiao Zhang", "Xiao Chen", "Xiao Bao", and "Xiao Sun", and the event can include "going on a trip". Specifically, "Xiaoming" and "Xiao Zhang" can have a "husband and wife" relationship, "Xiaoming" and "Xiao Chen" can have a "brother" relationship, "Xiaoming" and "Xiao Bao" can have a "child" relationship, "Xiaoming" and "Xiao Sun" can have a "friend" relationship, "Xiaoming" and "going on a trip" can have a "traveler" relationship, and "Xiao Zhang" and "Xiao Sun" can have a "friend" relationship, etc.

[0240] It's easy to understand that in the example above, the third node identifier is used to indicate the entity "Xiaoming". The triggering operation is the user's operation of pressing the "Search" button 1103 to activate the search interface 1500; the second graph content is... Figure 16 The memory map displayed within the dotted line in the memory map display interface 1600 can specifically include: "Xiaoming", four entities associated with "Xiaoming" and an event, the relationship between "Xiaoming" and the four entities and the event, and the relationship between the four entities and the event.

[0241] In this embodiment, in addition to displaying the memory map corresponding to the first entity, memory information corresponding to the first event can also be displayed. Furthermore, the mobile terminal can respond to a trigger operation on the first node identifier in the memory map, displaying the memory information corresponding to the first event in chronological order, where the first event is the event indicated by the first node identifier.

[0242] As mentioned above Figure 11 Taking the memory graph in the memory graph display interface 1100 as an example, in the memory graph display interface 1100, assuming that the first event indicated by the first node identifier is "traveling", the mobile terminal can also detect that after the user operates "traveling", it displays as follows. Figure 17 The travel display interface 1700 shown can display "memory theme" display information 1701 and timeline 1702, etc. The "memory theme" display information 1701 can correspond to the first event indicated by the first node identifier, such as "travel".

[0243] Timeline 1702 can be used to display memory information corresponding to "travel" in chronological order. Timeline 1702 can include buttons for "Year," "Month," the specific content of the "Memory Information," the "Recording Time" display, and the memory theme information.

[0244] In practical applications, users can swipe up and down (or flip pages left and right) on the travel display interface 1700 to view memory information related to the memory theme of "travel".

[0245] In some embodiments, the mobile terminal may also respond to a third operation on the fourth node identifier in the memory graph by removing the fourth node identifier and the relationship corresponding to the fourth node identifier from the memory graph.

[0246] It should be understood that the third operation can refer to the removal of the fourth node identifier from the memory graph. The fourth node identifier can be used to indicate an entity or event.

[0247] As mentioned above Figure 11 Taking the memory graph in the memory graph display interface 1100 as an example, in the memory graph display interface 1100, assuming that the entity indicated by the fourth node is Li Si, the mobile terminal can detect the user's operation "Li Si" and display as follows. Figure 18 The operation window 1800 shown may include a "Delete" button 1801, a "Modify" button 1802, and an "Add" button 1803. The "Delete" button 1801 can be used to delete the node identifier corresponding to "Li Si" in the memory map and the relationship corresponding to that node identifier. The "Modify" button 1802 can be used to modify the node name of the node identifier corresponding to "Li Si" in the memory map. The "Add" button 1803 can be used to add other node identifiers associated with the node identifier corresponding to "Li Si" based on the node identifier corresponding to "Li Si", as well as the relationship between the other node identifiers and the node identifier corresponding to "Li Si".

[0248] Assuming the mobile terminal detects the user's action of pressing the "Delete" button (1801), it can display something like this: Figure 19 The display interface 1900 shown has removed the node identifier corresponding to "Li Si", as well as the relationships between other entities or events and the entity "Li Si". In this example, the third operation may specifically include the user's operation of "Li Si" to display the operation window 1800 and the user's triggering operation of the "Delete" button 1801.

[0249] Of course, the third operation can also include display. Figure 11 The memory map display interface 1100 shown includes a series of operations prior to the memory map, such as the user's operation on the first application, or the user's operation on the first application and the operation on the display switch button, etc.

[0250] It should be understood that the display is as follows Figure 18 The user operation and display of the operation window 1800 shown are as follows: Figure 14The user operations shown in the display interface 1400 can be different.

[0251] In another example, in Figure 11 The memory map display interface 1100 shown can also display a "Modification Mode" button 1104. After the mobile terminal detects the user's operation of the "Modification Mode" button 1104, it can enter the modification state and display as shown below. Figure 20 The modified interface shown is from version 2000. After detecting the user's action "Li Si," the mobile terminal can display something like this. Figure 21 The operation window 2100 shown may also include a "Delete" button 2101, a "Modify" button 2102, and an "Add" button 2103.

[0252] The functions of each button in operation window 2100 can be compared with... Figure 18 The buttons in the operation window 1800 shown have the same function, so they will not be described again here. Of course, operation window 2100 can display more... Figure 18 The number of buttons in the operation window 1800 shown is not limited in this embodiment.

[0253] For example, after the mobile terminal detects the user's operation of the "modify" button 2102, it can enter the modification state. Then, in response to the user's modification operation of changing "Li Si" to "Sun Qi", it can change the node name corresponding to the node identifier from "Li Si" to "Sun Qi".

[0254] It is easy to understand that in practical applications, after modifying the node name, the relationship between the modified node identifier and other node identifiers can be updated based on the relationship between the entity corresponding to the modified node identifier and the entity or event corresponding to other node identifiers.

[0255] Similarly, in some embodiments, the mobile terminal may also update the name of the first relationship in response to a sixth operation on the relationship between multiple node identifiers.

[0256] It should be understood that the first relationship can be the relationship between any entity (or event) and another entity (or event) in the memory graph. The sixth operation can refer to a modification operation on any relationship among multiple node identifiers.

[0257] As mentioned above Figure 11 Taking the memory map in the memory map display interface 1100 as an example, after the mobile terminal detects the user's operation on the "girlfriend" between "I" and "Li Si", it can display the following: Figure 22The operation window 2200 shown may also include a "Delete" button 2201, a "Modify" button 2202, and an "Add" button 2203. The "Delete" button 2201 can be used to delete the "girlfriend" relationship between "me" and "Li Si", that is, to delete the "girlfriend" relationship between the node identifier corresponding to "me" and the node identifier corresponding to "Li Si" in the memory graph. The "Modify" button 2202 can be used to modify the "girlfriend" relationship between "me" and "Li Si", that is, to change the "girlfriend" relationship between the node identifier corresponding to "me" and the node identifier corresponding to "Li Si" in the memory graph to another relationship. The "Add" button 2203 can be used to add a relationship between "me" and "Li Si", that is, there can be two or more relationships between "me" and "Li Si", for example, there can be a "girlfriend" relationship and a "manager" relationship between "me" and "Li Si".

[0258] For example, see Figure 22 After the mobile terminal detects the user's operation of the "Add" button 2203, it can enter the editing state. The mobile terminal responds to the operation of adding a "Manager" relationship and displays the "Girlfriend" relationship and "Manager" relationship between "I" and "Li Si".

[0259] It should be understood that in actual design, in addition to manipulating the first relationship among multiple node identifiers in the above ways to update the name of the first relationship, users can also manipulate the connecting lines corresponding to the first relationship to use arrows with different directions to represent the correspondence between two node identifiers, where the two node identifiers are the node identifiers corresponding to the first relationship.

[0260] For example, after the mobile terminal detects that the user has triggered the connection, it can display something like this. Figure 22 The operation window 2200 shown may include a "Delete" button 2201, a "Modify" button 2202, and an "Add" button 2203. Afterwards, when the mobile terminal detects the user's operation of the "Add" button 2203, it can enter the editing state. In response to the operation of adding a "Manager" relationship, the mobile terminal displays as shown... Figure 23 The display interface 2300 shown can display the "girlfriend" relationship and "manager" relationship between "I" and "Li Si". In this interface, "I" am "Li Si's" "manager" and "Li Si" is "my" "girlfriend".

[0261] In addition, the aforementioned Figure 18 The operation window shown is 1800. Figure 21 The operation window 2100 shown and Figure 22The number and position of buttons displayed in any two or three of the operation windows 2200 shown may be the same or different. This application embodiment does not limit this.

[0262] In other possible implementations, the mobile terminal may also automatically perform editing operations on the node identifiers or the relationships corresponding to the node identifiers in the memory graph after obtaining the memory information to be edited.

[0263] It should be understood that editing operations can include any of the following: adding, updating, deleting, and searching.

[0264] Specifically, after obtaining the memory information to be modified, the mobile terminal can determine the first node identifier (or node) corresponding to the memory information to be edited from the memory graph. Then, based on the first node identifier and the memory information to be edited, the second node identifier to be edited and the relationship between the second node identifier and the memory information to be edited are determined. Finally, the edited memory graph is generated based on the second node identifier and the relationship between the second node identifier and the memory information to be edited.

[0265] In some embodiments, the method for determining the first node identifier (or node) corresponding to the memory information to be edited from the memory graph may include at least one of LLM and retrieval augmented generation (RAG) model.

[0266] As an example, not a limitation, such as Figure 24 The diagram shown is a schematic representation of a memory map of user Joey provided in an embodiment of this application. See also... Figure 24 Joey's memory graph can include tags such as "Relationships," "Preferences," "Events," and "Attributes." Under the "Relationships" tag, there's a "Colleagues" tag; under the "Events" tag, there's an "Arrangements" tag; under the "Colleagues" tag, there's a "Boss" node; and under the "Arrangements" tag, there's an "Amsterdam" node. "Boss" and "Amsterdam" have a "Travel Destination" relationship. Related to the "Amsterdam" node are also the "EK349" and "CP" nodes. Specifically, "Amsterdam" and "EK349" have a "Booked Flight" relationship, and "Amsterdam" and "CP" have a "Booked Hotel" relationship.

[0267] Furthermore, the node identifier "EK349" can also be associated with the node identifier "01:30 2024-05-13", which has a "departure time" relationship with "EK349"; the node identifier "CP" can also be associated with the node identifier "voucher $20", the node identifier "CS", the node identifier "2024-05-18", and the node identifier "2024-05-13". "CP" and "voucher $20" have an "expiration date 2024-05-14", "CP" and "CS" have a "nearby location" relationship, "CP" and "2024-05-18" have a "check-out time" relationship, and "CP" and "2024-05-13" have a "check-in time" relationship, etc. Of course, in Figure 24 The memory map shown may also include other node identifiers and corresponding relationships. For example, under the "Event" label, there may be "Shanghai" node identifier and "D1234" node identifier. There may be a "reserved train number" relationship between "Shanghai" and "D1234". This application does not limit this.

[0268] In one example, suppose the memory information to be edited received by the mobile terminal is "the reserved seat for flight EK349 is 32D", based on Figure 24 After receiving the aforementioned memory information to be edited, the mobile terminal can determine the first node identifier as "EK349" based on the memory information to be edited. Based on the aforementioned "the reserved seat for flight EK349 is 32D", it can determine the second node identifier to be edited as "32D". Furthermore, there can be a "reserved seat" relationship between "EK349" and "32D". Based on this, it can... Figure 24 The memory map shown has a newly added node identifier "32D", and the "reserved seat" relationship between "EK349" and "32D" has been added, resulting in the following: Figure 25 The edited memory map shown.

[0269] In another example, suppose the mobile terminal receives the memory information to be edited as "a $20 hotel voucher will expire on May 14, 2024," and the system time obtained by the mobile terminal is "May 15, 2024." Figure 24 After receiving the aforementioned memory information to be edited, the mobile terminal can determine that the first node identifier is "voucher $20" based on the memory information to be edited. Based on the aforementioned "$20 hotel voucher will expire on May 14, 2024", it can determine that the second node identifier to be edited is "voucher $20", and there is an "expiration time 2024-05-14" relationship between "voucher $20" and "CP". Based on this, it can... Figure 24Removing the node identifier "Voucher $20" and its "Expiration Time 2024-05-14" relationship with "CP" from the memory graph shown yields the following result: Figure 26 The edited memory map shown.

[0270] In yet another example, suppose the mobile terminal receives the memory information to be edited as "Flight EK349 has been rescheduled to May 14, 2024, at 01:40, bound for Amsterdam," based on... Figure 24 After receiving the aforementioned memory information to be edited, the mobile terminal can determine the first node identifier as "EK349" based on the memory information to be edited. Based on the aforementioned "EK349 flight has been rescheduled to fly to Amsterdam on May 14, 2024 at 01:40", it can determine the second node identifier to be edited as "01:30 2024-05-13". Furthermore, there is a "departure time" relationship between "EK349" and "01:30 2024-05-13". Based on this, it can... Figure 24 In the memory map shown, the name corresponding to the node identifier "01:30 2024-05-13" is changed to "01:40 2024-05-14", resulting in the following: Figure 27 The edited memory map shown.

[0271] In other examples, with Figure 12 Taking the voice recognition interface 1200 as an example, a user can input the voice command "What time does my boss's flight depart from Amsterdam?" and the interface will display something like this. Figure 28 The voice dialogue interface 2800 is shown. After the voice assistant recognizes the aforementioned voice dialogue command, it can... Figure 24 In the memory map shown, the first node is identified as "Amsterdam". Based on the "scheduled flight" relationship between "Amsterdam" and "EK349" in the voice dialogue command, the second node can be further identified as "EK349". Combining the "departure time" relationship between "EK349" and "01:30 2024-05-13" in the memory map, the departure time of flight "EK349" from "Amsterdam" is "01:30 2024-05-13". Based on this, the following can be displayed: Figure 29 The dialogue display interface 2900 shown can display the dialogue information "Your boss's flight EK349 departure time is 2024-05-13 01:30" on the mobile terminal.

[0272] It is not difficult to understand, in the above Figure 28 and Figure 29 In the example described, it is also possible to Figure 24The memory graph shown serves as the LLM's memory bank, allowing users to initiate dialogue questions to the LLM. Upon receiving a dialogue question, the LLM displays the corresponding dialogue information to the user based on the node identifiers corresponding to "Amsterdam", "EK349", and "01:30 2024-05-13" and the relationships between the node identifiers.

[0273] In some embodiments, the mobile terminal may also display an application settings interface, in which a first application is displayed; the mobile terminal may respond to an eighth operation detected on the application settings interface and set the source of the memory information to include the first application.

[0274] It should be understood that one or more primary applications can be displayed in the application settings interface. The eighth operation can be used to designate one or more primary applications as the source of memory information.

[0275] In some embodiments, at least one application displayed in the application settings interface may have the same application category. For example, the application settings interface may display at least one app belonging to the category of utilities, specifically, such as a memo app, a voice recorder app, a browser app, a smart assistant app, and a clock app, etc.

[0276] Additionally, at least one application displayed in the application settings interface can also be of a different application category. For example, the application settings interface may display all the apps pre-installed on the mobile device.

[0277] Based on the foregoing Figures 9 to 11 The example described above, after the personal assistant APP901 is launched, can display as follows: Figure 30 The application settings interface 3000 shown can display at least one APP. Based on the user's settings operation on at least one APP, the mobile terminal can obtain memory information from the APP corresponding to the settings operation.

[0278] Assumptions see Figure 30 The application settings interface 3000 can display the following options: "Auto-authorize all" option 3001, settings options for the "Messages" app 3002, settings options for the "Phone" app 3003, settings options for the "Smart Life" app 3004, settings options for the "Video Playback" app 3005, settings options for the "Sports" app 3006, settings options for the "Browser" app 3007, "Cancel" button, and "Confirm" button.

[0279] It's easy to understand that the above settings allow users to choose whether to set data from the corresponding app as the source of their memory information. If the mobile terminal detects that the user has selected the "Auto-authorize All" option 3001 and clicked the "Confirm" button, it can obtain the user's memory information from the log data or interaction data generated by all apps installed on the mobile terminal, thereby constructing the user's memory map.

[0280] In this example, after the mobile terminal obtains the user's memory information from all the log data or interaction data generated by the apps, it can display, as shown below. Figure 10 The display interface shown is 1000 or as follows Figure 11 The memory map display interface shown is 1100.

[0281] If the mobile terminal detects that the user has operated on at least one of the following apps: the settings option 3002 of the "Messages" app, the settings option 3003 of the "Phone" app, the settings option 3004 of the "Smart Life" app, the settings option 3005 of the "Video Playback" app, the settings option 3006 of the "Sports" app, and the settings option 3007 of the "Browser" app, as well as the "Confirm" button, then the user's memory information can be obtained from the log data or interaction data generated with the above-mentioned at least one app, thereby constructing the corresponding memory map.

[0282] Similarly, after obtaining the user's memory information from the log data or interaction data generated by the app corresponding to at least one of the above options, the mobile terminal can also display, as shown below. Figure 10 The display interface shown is 1000 or as follows Figure 11 The memory map display interface shown is 1100.

[0283] based on Figure 12 and Figure 13 The example described can also display, after the voice assistant recognizes the voice command "Open memory information management", the following display: Figure 30 The example shown is application settings interface 3000. The specific content of application settings interface 3000 in this example can be understood by referring to the previous examples, and will not be repeated here.

[0284] Based on the above possible implementation methods, it is possible to achieve the fusion of memory data among multiple applications installed on electronic devices. When data from different applications is integrated and applied to LLM, LLM can better understand users, thereby providing personalized services to users more accurately and efficiently.

[0285] In one possible implementation, the user logged in on the mobile terminal is the first user, and a synchronization device settings interface can also be displayed on the mobile terminal. The synchronization device settings interface can indicate that the user logged in on the second device is also the first user. The mobile terminal can respond to the seventh operation detected on the synchronization device settings interface to synchronize the memory information between the mobile terminal and the second device.

[0286] It should be understood that the second device can be a device with the same logged-in user as the mobile terminal. In practical applications, the login information of the second device can be the same as the login information on the mobile terminal, which may include a mobile phone number, email address, identification code, etc. The seventh operation can be an operation to synchronize the memory information between the second device and the mobile terminal.

[0287] In some embodiments, the second device may include one or more devices, and the logged-in user on the one or more second devices is the same user as the logged-in user on the mobile terminal, both of whom are the first user.

[0288] In one example, the mobile terminal can display something like this: Figure 31 The synchronization device settings interface 3100 shown may include a "Device 1" option 3101, a "WATCH" option 3102, a "Confirm" button, and a "Skip" button. The "Device 1" option 3101 and "WATCH" option 3102 allow the user to choose whether to synchronize the memory information in the corresponding device to the mobile terminal. If the mobile terminal detects that the user has selected at least one of the "Device 1" option 3101 or the "WATCH" option 3102, and clicked the "Confirm" button, then the memory information stored in "Device 1" and / or the "WATCH" device can be shared to the mobile terminal.

[0289] In practical design, the mobile terminal can display the above information after responding to the user's login operation. Figure 31 The synchronization device settings interface 3100 shown is shown. Figure 9 Taking the example given above, after the personal assistant APP901 is launched, it can also display... Figure 32 The login interface 3200 shown may include an "Account" option 3201, a "Password" option 3202, a "Login" button 3203, and a "Register" button 3204. Users can enter login information in the "Account" option 3201 and the "Password" option 3202, and press the "Login" button 3203. When the mobile terminal detects that the user has pressed the "Login" button 3203, it can display the following: Figure 31The synchronization device settings interface 3100 shown includes login information that the user can enter, such as: "Account" option 3201: 123xxxx4567; "Password" option 3202: ABCXXXXYZ.

[0290] In some embodiments, the mobile terminal displays as follows: Figure 31 After the synchronization device settings interface 3100 shown, when the mobile terminal detects the user's operation of the "Confirm" or "Skip" button, it can also display... Figure 10 The displayed interface is 1000 or Figure 11 The memory map display interface shown is 1100.

[0291] It should be noted that if the mobile terminal is the device where the user logs in to the electronic device for the first time with the aforementioned login information, the synchronization device settings interface can be displayed on the third device. This third device is not the first time the same login information has been used to log in to the electronic device, and the login information is: "Account" option 3201: 123xxxx4567; "Password" option 3202: ABCXXXXYZ.

[0292] For example, suppose the third device is a tablet computer, such as Figure 33 As shown, the desktop 3300 of the tablet can display multiple pre-installed apps, including a music app, a weather app, a theme app, an app download app, a payment app, a contacts app, a my device app, a photo album app, a camera app, a contacts app, a phone app, a settings app 301, and a personal assistant app 3301, etc. Of course, in... Figure 27 The tablet computer shown may also have other apps pre-installed, such as video playback apps, but this application does not limit this.

[0293] For example, see Figure 33 Users can tap the application icon corresponding to the personal assistant APP 3301 on the desktop 3300 of the tablet to select and launch the personal assistant APP 3301. After the personal assistant APP 3301 is launched, it can display the following: Figure 34 The login screen shown is 3400. Figure 34 The login interface 3400 shown may include an "Account" option 3401, a "Password" option 3402, a "Login" button 3403, and a "Register" button 3404. Users can enter login information in the "Account" option 3401 and the "Password" option 3402: "Account" option 3201: 123xxxx4567; "Password" option 3202: ABCXXXXYZ, and press the "Login" button 3403. When the mobile terminal detects the user's press of the "Login" button 3403, it can display the following: Figure 35The synchronization device settings interface shown is 3500.

[0294] Assuming the synchronization device settings interface 3500 displays a "Device 1" option 3501, a "WATCH" option 3502, a "Confirm" button 3503, and a "Skip" button 3504, the user can operate the "Device 1" option 3501 and / or the "WATCH" option 3502 to share (or synchronize) the memory information stored in Device 1 and / or WATCH to a tablet computer. It is easy to understand that in this example, Device 1 can correspond to the mobile phone terminal in the aforementioned embodiments.

[0295] Conversely, when the tablet detects that the user has pressed the "Skip" button 3504, it may not share (or synchronize) the memory information stored in Device 1 and / or WATCH to the tablet.

[0296] Of course, in Figure 35 In the synchronization device settings interface 3500 shown, when the tablet computer detects that the user has pressed the "Confirm" or "Skip" button, it can also display... Figure 10 The displayed interface is 1000 or Figure 11 The memory map display interface shown is 1100.

[0297] Based on the above possible implementation methods, memory information between multiple devices of the same user can be fused based on the second device selected by the user, so as to realize the sharing of memory information between multiple devices and maintain a consistent user experience even when using the same application on different devices.

[0298] In other possible implementations, the mobile terminal may also display a to-do list prompt interface, which may display a first tag; the mobile terminal may determine whether to store the first tag in response to a user operation detected on the to-do list prompt interface.

[0299] It's not hard to understand that the first label corresponds to the aforementioned Figure 4 The first label in the described embodiment.

[0300] In this embodiment, the first tag is obtained based on the memory information of the logged-in user (i.e., the first user) on the mobile terminal. Since each mobile terminal typically corresponds to a different logged-in user, and each user's memory information (such as browsing history, preference settings, etc.) is unique (i.e., different users have different memory information), the generated tag information also varies. This differentiation not only enhances the targeting and effectiveness of the service but also ensures that each user can enjoy customized services that match their personal preferences, thereby satisfying diverse personalized needs.

[0301] For example, assuming the currently logged-in user on the mobile terminal is A, then based on A's relevant memory information on the mobile terminal, algorithms such as cluster analysis can be used to cluster the memory information to obtain a first label corresponding to A. The first label corresponding to A can reflect A's specific needs and interests.

[0302] In other possible implementations, the first tag may also be obtained based on the user's multimodal data acquired by the mobile terminal. This application does not limit this aspect.

[0303] In the embodiments of this application, the user operation can be a user's confirmation operation on the first tag; the user operation can also be a confirmation operation performed after the user has modified the first tag; or it can be a user's operation such as ignoring or deleting the first tag.

[0304] In one example, the to-do list notification interface may include a confirm control and an ignore control. The mobile terminal can respond to a triggering action on the confirm control by directly storing the first label. Alternatively, the mobile terminal can respond to a triggering action on the ignore control without storing the first label.

[0305] In some embodiments, the first tag can be directly stored in the constructed tag library for use in classifying memory information and determining the category tag corresponding to the memory information, and then extracting information from the memory information based on the category tag, so as to further enrich the node identifiers in the memory graph and the relationships between node identifiers.

[0306] In other embodiments, the first tag can also be directly stored in the user's memory graph. It should be noted that if the first tag is stored in the user's memory graph, it can be directly displayed in the user's memory graph.

[0307] Based on the above possible implementation methods, users can also provide feedback on node identifiers in the tag library or memory graph, further increasing the interactivity and operability of node identifiers and improving user participation.

[0308] In one example, the to-do list prompt interface may include a modification control and a confirmation control. The corresponding user operations may include triggering the modification control and triggering the confirmation control. The mobile terminal may respond to the triggering operation of the modification control by modifying the first label. Afterward, the mobile terminal may respond to the triggering operation of the confirmation control by storing the modified first label.

[0309] It should be understood that the modified first tag can also be stored in the constructed tag library, used to build a tag library corresponding to the user's memory information. This allows for information extraction based on the category tags of the memory information after those tags are determined, enabling the addition of node identifiers and relationships between them in the memory graph. The modified first tag can also be stored directly in the user's memory graph. Similarly, if the modified first tag is stored in the user's memory graph, it can also be displayed in the user's memory graph.

[0310] Based on the aforementioned example, see Figure 32 After the mobile terminal detects that the user has pressed the "Login" button (3203), it can also display something like this: Figure 36 The interface 3600 shown is included. Interface 3600 may include a "Memory Information Display" option 3601 and a "To-Do" option 3602, etc. After the mobile terminal detects the user's operation of the "To-Do" option 3602, it can display the following... Figure 37 The to-do list prompt interface 3700 is shown. The to-do list prompt interface 3700 may display a "Add Tag" prompt message 3701, a "Confirm" button 3702, a "Modify" button 3703, and an "Ignore" button 3704. The tag corresponding to the "Add Tag" prompt message 3701 is the first tag obtained based on the logged-in user's information on the mobile terminal.

[0311] For example, assuming that the "Add New Tag" prompt message 3701 displayed in the to-do list prompt interface 3700 is "Travel", the mobile terminal can directly save "Travel" after detecting the user's operation of the "Confirm" button 3702.

[0312] Alternatively, the mobile terminal can display the following after detecting the user's operation of the "Modify" button 3703: Figure 38 The modification interface 3800 shown can include "Add Tag" modification information 3801, "Confirm" button 3802 and "Cancel" button. Assuming that the user changes the "Add Tag" modification information 3801 to "Travel", the mobile terminal can directly save "Travel" after detecting the user's operation of the "Confirm" button 3802.

[0313] It should be understood that, Figure 37 In the to-do list prompt interface 3700 shown, after the mobile terminal detects the user's operation of the "ignore" button 3704, it can modify... Figure 36 The display information corresponding to the "To-Do" option 3602 in the interface 3600 shown. For example, the number of to-do items displayed for the "To-Do" option 3602 can be reduced by one. Specifically, the display information corresponding to the "To-Do" option 3602 can be displayed as "0 to-do items".

[0314] In some embodiments, such as Figure 36 In the interface 3600 shown, after the mobile terminal detects the user's operation of the "Memory Information Display" option 3601, it can display as follows: Figure 10 The display interface shown is 1000 or as follows Figure 11 The memory map display interface shown is 1100.

[0315] As an example, and not a limitation, assuming the mobile terminal detects that the user has selected the "Memory Information Display" option 3601, it may display something like this: Figure 10 The display interface 1000 shown includes a "List Display" button 1001 and a "Graphical Display" button 1002. When the mobile terminal detects that the user has pressed the "Graphical Display" button 1002, it can display the following... Figure 11 The memory map display interface shown is 1100.

[0316] Correspondingly, the memory graph display interface 1100 can also display a "List Display" button 1101 and a "Graphical Display" button 1102. After the mobile terminal detects the user's operation of the "Memory Information Display" option 3001, it can display the following: Figure 11 The memory map display interface 1100 shown below, after the mobile terminal detects the user's operation of the "List Display" button 1101, can display as follows: Figure 10 The display interface 1000 is shown. In this case, the "List Display" button 1101 is a display switching control used to switch the display mode of the memory map.

[0317] In some embodiments, a fifth node identifier may also be displayed in the memory graph; in response to a fourth operation on the fifth node identifier, a fifth node identifier and the relationship between the fifth node identifier and the memory graph are added.

[0318] In one example, the fifth node identifier could be the first tag obtained from the logged-in user's memory information on the mobile terminal. Based on this, the relevant content of the fifth node identifier can be understood by referring to the corresponding content of the aforementioned first tag, and will not be repeated here.

[0319] In another example, the fifth node identifier could also be... Figure 3 The memory graph construction method described above yields a node identifier.

[0320] It should be understood that the fourth operation can be a trigger operation on the fifth node identifier in the memory graph, so that the mobile terminal can respond to the trigger operation to add a fifth node identifier in the memory graph and the relationship between the fifth node identifier and the fifth node identifier.

[0321] It should be noted that before the fourth operation, the fifth node identifier can be displayed differently from other node identifiers in the memory graph. For example, the fifth node identifier can differ from other node identifiers in terms of color, animation effects, shape, etc. After the fourth operation, the fifth node identifier is displayed in the same way as other node identifiers.

[0322] In this embodiment, the memory graph can be the graph content corresponding to the second subject associated with the fifth node identifier. The second subject can include the logged-in user on the mobile terminal, for example... Figure 11 The memory graph is shown as "Me" in the memory graph display interface 1100. In other possible embodiments, the memory graph can also be the graph content corresponding to a third subject or event that satisfies a preset relationship with the fifth node identifier. For example, the preset relationship may include the interaction frequency between the entity or event indicated by the fifth node identifier and the third subject or event being greater than a preset threshold, etc.

[0323] As an example, and not a limitation, let's assume the fifth node is labeled "basketball" to represent the memory graph. Figure 11 For example, see the memory map display interface 1100 shown below. Figure 39 The fifth node identifier corresponding to "basketball" can be displayed in a thicker color on the memory map display interface 1100. The mobile terminal can respond to the fourth operation on the fifth node identifier corresponding to "basketball" (e.g., double-clicking the fifth node identifier corresponding to "basketball") to display the display interface 3900.

[0324] Compared to Figure 11 The memory map display interface shown is 1100. Figure 39 The displayed interface 3900 has added a "basketball" node and an "interest" relationship between "me" and "basketball".

[0325] In other embodiments, the mobile terminal may also respond to a fifth operation on the fifth node identifier by modifying the node name corresponding to the fifth node identifier in the memory graph.

[0326] It should be understood that the fifth operation can be a modification operation on the name of the node identified by the fifth node.

[0327] by Figure 39 Taking the display interface 3900 as an example, suppose a user wants to change the name of the fifth node identifier of "basketball" to "sports". The user can perform a modification operation on the fifth node identifier of "basketball" in the display interface 3900 (for example, long press the node identifier corresponding to "basketball"). After that, the node name will be changed from "basketball" to "sports". The mobile terminal can respond to the user's long press, modification and other operations on the fifth node identifier corresponding to "basketball" and display the display interface 4000.

[0328] It should be noted that... Figure 39 In the example shown, after modifying the node name of the fifth node identifier, the relationship between the entity (or event) indicated by the fifth node identifier and the entities (or events) indicated by other node identifiers can remain unchanged.

[0329] Compared to the above Figures 18 to 23 In the example described above, the method of modifying the node name corresponding to any node identifier in the memory graph by using the "Modify" button is as follows: Figure 40 The method shown can speed up the modification of the node name of the fifth node identifier.

[0330] In other embodiments, the mobile terminal may also delete the fifth node identifier in the memory graph in response to the deletion operation of the fifth node identifier.

[0331] For example, based on the aforementioned example, see Figure 41 The mobile terminal can respond to the user's operation of long-pressing the fifth node icon corresponding to "basketball" and dragging the fifth node icon corresponding to "basketball" to the right boundary of the mobile terminal screen display area, and display interface 4100 is displayed, in which the fifth node icon corresponding to "basketball" is deleted.

[0332] It should be understood that in the above example, the deletion operation can be the user long-pressing the fifth node icon corresponding to "basketball" and dragging the fifth node icon to the right boundary of the mobile terminal screen display area.

[0333] In the above embodiments, the fifth node identifier can be... Figure 11 The memory map is displayed in the interface 1100 shown. In some other embodiments, the fifth node identifier may also be displayed in the to-do list prompt interface.

[0334] As an example and not a limitation, the mobile terminal may display a to-do list prompt interface, which includes a fifth node identifier; the mobile terminal may, in response to user actions detected on the to-do list prompt interface, add a fifth node identifier and the relationship between the fifth node identifier and the memory graph.

[0335] It is easy to understand that the user operations in this embodiment may also include a confirmation operation for the fifth node identifier, or a modification operation and confirmation operation for the fifth node identifier. For details on user operations and related content regarding the fifth node identifier, please refer to... Figures 39 to 41 The corresponding content in the embodiments described herein will not be repeated here.

[0336] In one possible example, the to-do list prompt interface may also include a confirm button and a modify button.

[0337] For example, suppose that... Figure 11 The memory map displayed on the memory map display interface 1100 shown is a memory map. For example, the content corresponding to the fifth node is "basketball". The to-do list prompt interface displayed on the mobile terminal can be found here. Figure 42 The display interface 4200 is shown. This display interface 4200 may include the graph content displayed in the memory graph display interface 1100, the node name "basketball" corresponding to the fifth node identifier, a confirmation button 4201, and a modification button 4202. The confirmation button 4201 can be used to directly add the node identifier corresponding to "basketball" to the memory graph; the modification button 4202 can be used to modify the node name corresponding to "basketball".

[0338] In other words, the mobile terminal can respond to the user's trigger operation on the confirmation button 4201 by adding the fifth node identifier corresponding to "basketball" and the relationships between other node identifiers and the fifth node identifier in the memory graph. The mobile terminal can also respond to the user's trigger operation on the modify button 4202, allowing the user to modify the node name corresponding to the fifth node identifier from "basketball" (e.g., to "ball sports"). After the modification is completed, in response to the user's trigger operation on the confirmation button 4201, the node name corresponding to the fifth node identifier is changed from "basketball" to "ball sports", and the fifth node identifier corresponding to "ball sports" and the relationships between other node identifiers and the fifth node identifier are added to the memory graph.

[0339] Of course, the display interface 4200 may include an ignore button 4203, which can directly delete the fifth node identifier corresponding to "basketball" displayed on the display interface 4200. Correspondingly, the mobile terminal can directly respond to the user's trigger operation of the ignore button 4203 and delete the fifth node identifier corresponding to "basketball" on the display interface 4200.

[0340] In the above possible embodiments, the mobile terminal can also automatically delete (or add) the fifth node identifier and the relationship between the fifth node identifier and the memory graph after the fifth node identifier has been displayed for a preset time.

[0341] Based on the above possible implementation methods, adding node identifiers and their corresponding relationships to the corresponding memory graph according to user operations enables users to clearly see the changes in the memory graph. This avoids the problem of users having to switch back and forth between different pages or complex operation processes to understand relevant information when they do not know the relevant information, thus improving the convenience and smoothness of operation and further enhancing the user experience.

[0342] It should be noted that, in the foregoing embodiments of this application, the user operations, trigger operations, first operations, second operations, third operations, fourth operations, fifth operations, sixth operations, seventh operations, and eighth operations detected by the mobile terminal may include, but are not limited to, pressing, clicking, double-clicking, touching, long-pressing, and long-pressing and clicking. This application does not impose any limitations on these operations.

[0343] It is understood that, in this embodiment, the associations between entities and / or events in a user's memory information are displayed intuitively through multiple node identifiers and the relationships between them. This display method is closer to how humans store and use memory information, making it easier for users to understand and accept, and improving the user experience. When memory maps are applied to LLM, they help LLM effectively associate multiple node identifiers and their relationships with other node identifiers, obtaining richer contextual information and deepening the LLM's understanding of the user. In practical applications, LLM can use the obtained contextual information to provide personalized services to users, meet their individual needs, and improve the user experience.

[0344] Furthermore, compared to storing memory information in tensor or text form, the method of directly displaying the memory map on the first interface allows users to quickly find memory information related to entities or events according to their actual needs by using node identifiers. This effectively avoids the tedious steps of searching through the user's memory information (or memory pool list) in tensor or text form to see if it is related to a certain entity or event, simplifying the search steps for a certain entity or event and making it easier for users to quickly view their memory information.

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

[0346] Figure 43 This is a schematic diagram of a memory map display device provided in one embodiment of this application. The memory map display device 4300 can be deployed in the electronic device of the aforementioned embodiment. See also... Figure 43 The memory map display device 4300 may include a first display module 4301.

[0347] The first display module 4301 is used to display a first interface in response to a first operation. The first interface is used to display the user's memory map. The memory map is used to indicate the user's memory information. The memory information is represented by multiple node identifiers and the relationship between the multiple node identifiers. The node identifiers are used to indicate entities or events.

[0348] In some embodiments, the memory map display device 4300 further includes: a second display module, configured to display memory information corresponding to a first event in chronological order in response to a trigger operation on a first node identifier in the memory map, wherein the first event is an event indicated by the first node identifier.

[0349] In some embodiments, the memory map display device 4300 further includes a third display module, configured to display first map content associated with a first entity in the memory map in response to a trigger operation on a second node identifier in the memory map, wherein the first entity is the entity indicated by the second node identifier.

[0350] In some embodiments, the first interface further includes a search control, and the memory map display device 4300 further includes: a fourth display module, configured to display a second interface in response to a trigger operation of the search control, the second interface being configured to receive a third node identifier input by the user; and to display second map content in the memory map corresponding to the third node identifier in response to a second operation detected on the second interface.

[0351] In some embodiments, the memory map display device 4300 further includes a removal module, configured to remove the fourth node identifier and the relationship corresponding to the fourth node identifier from the memory map in response to a third operation on the fourth node identifier in the memory map.

[0352] In some embodiments, the memory map display device 4300 further includes:

[0353] The fifth display module is used to display the fifth node identifier in the memory map. The fifth node identifier is obtained based on the memory information of the logged-in user of the electronic device.

[0354] The determination module is used to add the fifth node identifier and the relationship between the fifth node identifier and the memory graph in response to the fourth operation on the fifth node identifier.

[0355] In some embodiments, the memory map display device 4300 further includes:

[0356] The modification module is used to modify the name of the node identified by the fifth node in the memory graph in response to the fifth operation on the fifth node identifier.

[0357] In some embodiments, the memory map display device 4300 further includes:

[0358] The update module is used to update the name of the first relation in response to the sixth operation on the first relation in the relation.

[0359] In some embodiments, the first interface includes a display switching control, and the memory map display device 4300 further includes:

[0360] The switching module is used to display the remembered information in a list format in response to the trigger operation of the display switching control.

[0361] In some embodiments, the user logged in on the electronic device is the first user, and the memory map display device 4300 further includes:

[0362] The sixth display module is used to display the synchronization device settings interface, which indicates that the logged-in user of the second device is also the first user;

[0363] The synchronization module is used to synchronize memory information between the electronic device and the second device in response to the seventh operation detected on the synchronization device settings interface.

[0364] In some embodiments, the memory map display device 4300 further includes:

[0365] The seventh display module is used to display the application settings interface, which shows the first application.

[0366] The settings module is used to respond to the eighth operation detected on the application settings interface, and the source of the settings memory information includes the first application.

[0367] It should be noted that the module division in the memory map display device provided in the above embodiments is illustrative and only represents one logical functional division. In actual implementation, other division methods are also possible. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0368] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device or processor to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0369] Furthermore, the memory map display device and the memory map display method provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments. For ease of reading, this device embodiment will not repeat the details of the foregoing method embodiments one by one, but it should be clear that the device in this embodiment can correspondingly implement all the contents of the foregoing method embodiments.

[0370] Based on the same inventive concept, embodiments of this application also provide an electronic device, including one or more processors; one or more memories and one or more computer programs; wherein the one or more computer programs are stored in one or more memories, and the one or more computer programs include instructions that, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0371] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods shown in the above embodiments.

[0372] This application also provides a computer program product storing a computer program that, when run by an electronic device, enables the electronic device to perform the methods shown in the above embodiments.

[0373] This application also provides a chip system including a processor and a memory, wherein the memory stores a computer program that, when executed by the processor, implements the methods shown in the above embodiments.

[0374] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0375] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be RAM, which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0376] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

[0378] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0379] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0380] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

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

Claims

1. A memory map display method characterized by comprising: The method is applied to an electronic device, and the method comprises: in response to a first operation, displaying a first interface, the first interface being used to display a memory graph of a user, the memory graph being used to indicate memory information of the user, the memory information being represented by a plurality of node identifiers and relationships between the plurality of node identifiers, the node identifiers being used to indicate entities or events.

2. The memory map display method according to claim 1, characterized by, The method further comprises: in response to a triggering operation on a first node identifier in the memory graph, displaying memory information corresponding to a first event in a time sequence, the first event being an event indicated by the first node identifier.

3. The memory map display method according to claim 1 or 2, characterized by, The method further comprises: in response to a triggering operation on a second node identifier in the memory graph, displaying first graph content associated with a first entity in the memory graph, the first entity being an entity indicated by the second node identifier.

4. The memory map display method according to any one of claims 1 to 3, characterized by, The first interface further comprises a search control, and the method further comprises: in response to a triggering operation on the search control, displaying a second interface, the second interface being used to receive a third node identifier input by the user; in response to a second operation detected on the second interface, displaying second graph content corresponding to the third node identifier in the memory graph.

5. The memory map display method according to any one of claims 1 to 4, characterized by, The method further comprises: in response to a third operation on a fourth node identifier in the memory graph, removing the fourth node identifier and relationships corresponding to the fourth node identifier from the memory graph.

6. The memory map display method according to any one of claims 1 to 5, characterized by, The method further comprises: displaying a fifth node identifier in the memory graph, the fifth node identifier being obtained according to memory information of a login user of the electronic device; in response to a fourth operation on the fifth node identifier, adding the fifth node identifier and relationships between the fifth node identifier in the memory graph.

7. The memory map display method according to claim 6, characterized by, The method further comprises: in response to a fifth operation on the fifth node identifier, modifying a node name of the fifth node identifier in the memory graph.

8. The memory map display method according to any one of claims 1 to 7, characterized by, The method further comprises: in response to a sixth operation on a first relationship in the relationships, updating a name of the first relationship.

9. The memory map display method according to any one of claims 1 to 8, characterized by, The first interface comprises a display switching control, and the method further comprises: in response to a triggering operation on the display switching control, displaying the memory information in a list display manner.

10. The memory map display method according to any one of claims 1 to 9, characterized by, A user logged in on the electronic device is a first user, and the method further comprises: displaying a synchronization device setting interface, the synchronization device setting interface indicating that a login user of a second device is also the first user; in response to a seventh operation detected on the synchronization device setting interface, synchronizing the memory information between the electronic device and the second device.

11. The memory map display method according to any one of claims 1 to 10, characterized by, The method further comprises: displaying an application setting interface, the application setting interface displaying a first application; in response to an eighth operation detected on the application setting interface, setting a source of the memory information to include the first application.

12. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor implements the method in any one of claims 1 to 11 when executing the computer program.

13. A computer-readable storage medium, characterized in that, The computer program is stored on the computer-readable storage medium and, when executed on a computer, causes the computer to perform the method in any one of claims 1 to 11.

14. A chip system, characterized by comprises: a processor and a memory for storing a computer program, the processor being configured to invoke and run the computer program stored in the memory, so that a device or apparatus in which the chip system is installed performs the method according to any one of claims 1 to 11.

Images