Method for displaying context and sequence of events, and device and storage medium

Abstract

The present application relates to the technical field of big data. Disclosed are a method for displaying the context and sequence of events, and a device and a storage medium. The method for displaying the context and sequence of events comprises: when a time range selected by a user has been detected by a client, sending the time range to a server side; on the basis of the time range, the server side acquiring an event set and a preset number of events within a corresponding time period; and on the basis of the obtained event set and the obtained preset number of events, re-generating a result of the context and sequence of events within the corresponding time range, and returning the result of the context and sequence of events to the client for display. On the basis of the method, a user can make custom adjustments on a time window of the context and sequence of events, and can acquire a result of the context and sequence of events within a corresponding time range, such that the user can quickly and accurately understand the situation of events occurring within a specific time period, thereby improving the efficiency of the user acquiring event development information.

Description

Event context display method, device and storage medium

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on October 20, 2023, with application number 202311369074.8 and application name “A method, device and storage medium for displaying event context”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of big data technology, and in particular to an event context display method, device, and storage medium. Background Art

[0003] Currently, news websites can chronologically organize the development of the same news event at different points in time, providing users with a clear context for the news event. For example, as shown in Figure 1, users can use the event context function to view the schedule of an international sports competition.

[0004] However, when users use the event context function to understand the development of an event, they can only view a list of all events within the start and end time of the event, making it impossible for users to quickly and accurately understand the circumstances of the event within a specific time period, reducing the efficiency of users in obtaining event progress information.

[0005] Summary of the Invention

[0006] To solve the above problems, the present application provides an event context display method, device and storage medium.

[0007] In a first aspect, the present application provides an event context display method, the method comprising: a client displays a first event context result corresponding to a first time period; the client detects a first instruction from a user, wherein the first instruction is used to instruct the display of a second event context result corresponding to a second time period in the first time period; the client displays the second event context result corresponding to the second time period in response to the first instruction from the user, the number of events displayed in the second event context result being greater than the number of events displayed in a third event context result, wherein the third event context result is the event context within the second time period in the first event context result.

[0008] In the present application, the client may be a terminal device such as a mobile phone, computer, virtual reality device, augmented reality (AR) device, laptop computer, etc. mentioned in the present application; the first time period may be the time range from the beginning to the latest development stage of the target event mentioned in the present application; the first event context result may be the initial complete event context result of the target event mentioned in the present application; the first instruction may be the interaction between the user and the terminal device for adjusting the time window range mentioned in the present application; the second time period may be the user-customized time window range mentioned in the present application; the second event context result may be the event context result within the corresponding time range generated based on user interaction information mentioned in the present application; the third event context result may be the event context corresponding to the second time period directly intercepted in the initial complete context result.

[0009] It can be understood that in this application, when the client detects that the user opens a third-party application such as Tencent NewsTM and enters the target event to be queried, the client can display the initial complete event context of the target event from the beginning of the event to the latest development stage of the event on the display interface; next, the user can customize the time window of the event context through any interactive method on the display interface, and the client will display the event context results of the corresponding time range on the display interface.

[0010] In some embodiments, the event granularity in the second event context result regenerated based on the user interaction information is finer, resulting in the number of events in the second event context result being different from the number of event contexts corresponding to the second time period directly intercepted from the initial complete first event context result.

[0011] Based on the above method, users can customize the time window of the event context and obtain the event context results within the corresponding time range. They can also change the content and number of event contexts, allowing users to quickly and accurately understand the occurrence of events within a specific time period, thereby improving the efficiency of users in obtaining event progress information.

[0012] In one possible implementation, the client displays a second event context result corresponding to a second time period in response to a first instruction from a user, including: the client sends the second time period corresponding to the first instruction to a server; the server generates a second event context result corresponding to the second time period based on the second time period, and sends the second event context result to the client; and the client displays the second event context result corresponding to the second time period.

[0013] It can be understood that in this application, after the client detects the user's first instruction, the time window range parameters corresponding to the first instruction will be sent to the server, and the server will execute the event context generation algorithm to generate the event context results within the corresponding time period, and return the event context results to the client for display through the client's display interface.

[0014] In one possible implementation, generating a second event context result corresponding to the second time period based on the second time period includes: obtaining an event set corresponding to the second time period based on the second time period; determining the number of events displayed; and generating a second event context result corresponding to the second time period based on the event set and the number of events displayed corresponding to the second time period.

[0015] In this application, the event set corresponding to the second time period can be the related event set E of the target event within the user-defined time window mentioned in this application; the number of events displayed can be the event cluster number parameter K in the generated event context result mentioned in this application.

[0016] It can be understood that in this application, the server side can obtain the relevant event set E of the target event within the corresponding time period based on the time window parameter, and then generate the event context results within the corresponding time range based on the obtained relevant event set E and the preset number of events.

[0017] In a possible implementation, the above-mentioned obtaining of an event set corresponding to the second time period based on the second time period includes: extracting a document set corresponding to the second time period; obtaining an associated event set corresponding to the second time period based on the document set corresponding to the second time period; and performing timing adjustment on each associated event in the associated event set corresponding to the second time period to obtain an event set corresponding to the second time period.

[0018] It can be understood that in the present application, the event set can be a list of events of different granularities (i.e., the degree of event details) within the time window. When generating the event list, it is necessary to perform event structuring processing on the document collection of the target event in the second time period through the natural language processing model, for example, extracting event related information such as event participants, event location, event keywords, and event time; then perform event association on the obtained event related information, for example, obtain the associated event: event participant A has event C at location B; finally, all associated events are obtained and time-series processing is performed to obtain the related event set of the target event in the second time period.

[0019] In a possible implementation, the above-mentioned document set corresponding to the second time period is based on the document set corresponding to the second time period to obtain the associated event set corresponding to the second time period, including: extracting event-related information from the document set corresponding to the second time period, the event-related information including at least one of: event participants, event location, event keywords and event time; and performing event association on the event-related information to obtain the associated event set corresponding to the second time period.

[0020] It can be understood that in the present application, when generating a set of associated events corresponding to the second time period, the document collection of the target event within the second time range can be subjected to event structuring processing through a natural language processing model, for example, extracting event-related information such as event participants, event location, event keywords, and event time; then performing event association on the obtained event-related information, for example, obtaining an associated event: event C occurred at location B for event participant A; finally, obtaining a list of all associated events and removing identical events, thereby obtaining a set E of associated events for the target event within the time range T.

[0021] In one possible implementation, the above-mentioned timing adjustment of each associated event in the associated event set corresponding to the second time period to obtain the event set corresponding to the second time period includes: adjusting the order of each associated event based on the timing relationship of each associated event in the associated event set corresponding to the second time period to obtain the event set corresponding to the second time period; wherein the timing relationship includes: at least one of: time sequence and event causal relationship.

[0022] It is understood that in the embodiments of the present application, it is also necessary to perform event temporal relationship processing on the associated events in the set of related events of the target event within the second time range. That is, based on the time information of the events, as well as the causal relationship and contextual information between the events, according to the specific scenario and task requirements, appropriate methods and models are selected to process and analyze the temporal relationship of the events. For example, based on the date information in the events, a timeline is constructed to represent the sequence of events, and the associated events are arranged according to their positions on the timeline to complete the event temporal relationship processing.

[0023] In a possible implementation, the determining of the number of events to be displayed includes: determining the number of events to be displayed corresponding to the second event context result based on the duration of the second time period.

[0024] It can be understood that in this application, the number of events displayed corresponding to the second event context result can be determined based on the time range parameter T. For example, when the preset time range is less than 30 days, the preset number of events displayed is 10, and when the preset time range is greater than 30 days, the preset number of events displayed is 15, etc.

[0025] In a possible implementation, the determining of the number of event displays further includes: using a preset number of event displays as the number of events displayed corresponding to the second event context result.

[0026] It can be understood that in the present application, the number of events displayed corresponding to the second event context result can be a preset fixed value. For example, the event context result can be fixed to 10 related events.

[0027] In one possible implementation, the above-mentioned generating a second event context result corresponding to the second time period based on the event set corresponding to the second time period and the number of event displays includes: clustering the event set corresponding to the second time period based on the number of event displays to generate the second event context result, wherein the number of clusters in the clustering processing is the same as the number of event displays.

[0028] It can be understood that in the present application, the server side can obtain the event context result through the clustering algorithm based on the determined related event set E of the target event in the second time period and the event cluster number parameter K, wherein the clustering algorithm can represent obtaining an associated event in each cluster to represent the associated events of the entire cluster.

[0029] In some embodiments, the clustering algorithm may refer to clustering the related events in the event set E into K groups, summarizing a characteristic related event in each group to represent all the related events in the group, and using the summarized characteristic related events as a generated event context result, and finally selecting K events to form an event context result within the time range of T.

[0030] In one possible implementation, the above-mentioned clustering processing of the event set corresponding to the second time period based on the number of event displays to generate the second event context result includes: determining the number of clusters based on the number of event displays; clustering the event set corresponding to the second time period based on the number of clusters to obtain multiple cluster sets; determining each feature-related event in each of the cluster sets; and determining the second event context result based on the each feature-related event.

[0031] In the present application, the server may obtain the second event context result according to the determined set of related events and the number of event clusters of the target event within the second time range.

[0032] In some embodiments, a clustering algorithm may involve dividing the associated events in event set E into K groups, i.e., K cluster sets, summarizing a characteristic associated event in each group to represent all associated events in that group, and using the summarized characteristic associated events as a generated event context result. Ultimately, K events are selected to form an event context result within a time range of T. The value of K is the same as the number of events displayed. The second event context result determined based on the clustering algorithm can better reflect the characteristics of each cluster set, thereby improving the accuracy of event context results such as news.

[0033] In a possible implementation, the first instruction includes: one or more of a voice instruction and adjusting a display control of a display interface of the client.

[0034] It is understood that in this application, the user can directly input the start and end range of the time window by voice, and can also adjust the time window range by adjusting the display controls of the interactive interface.

[0035] In a possible implementation, the display controls include: a quick time period button, a time slider, a start and end calendar box, and one or more display controls of a date input box.

[0036] It can be understood that in the present application, the display controls of the interactive interface can include various forms, such as quick time periods (for example, shortcut buttons such as "last three days" and "last week"); a time slider, in which the left end of the slider represents the start date of the time window and the right end of the slider represents the end date of the time window; a start and end calendar box, in which two dates are selected to represent the start date and end date of the time window respectively; and a date input box, in which the start date and end date of the time window can be directly entered.

[0037] In a possible implementation, the method further includes: the server extracting a document set corresponding to the first time period; the server generating a first event context result corresponding to the first time period based on the document set corresponding to the first time period, and sending the first event context result to the client.

[0038] It can be understood that in this application, when the client detects that the user opens a third-party application such as Tencent NewsTM and enters the target event to be queried, the client can send the target event to the server. The server extracts the file collection of the target event from the beginning of the event to the latest development stage, and generates the initial complete event context result and returns it to the client.

[0039] In a second aspect, the present application provides an electronic device comprising: a memory and a processor, the memory being used to store instructions executed by one or more processors of the electronic device, and the processor being one of the one or more processors of the electronic device, and being used to execute the event context display method mentioned in the present application.

[0040] In a third aspect, the present application provides a readable storage medium, wherein the readable storage medium stores instructions, which, when executed on an electronic device, enable the electronic device to execute the event context display method mentioned in the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] FIG1 shows a schematic diagram of a usage scenario of an event context function according to some embodiments of the present application;

[0042] FIG2 shows a schematic diagram of a system architecture according to some embodiments of the present application;

[0043] FIG3 shows a schematic diagram of a device architecture according to some embodiments of the present application;

[0044] FIG4A is a schematic diagram showing a first scenario of obtaining an event context result by adjusting the time window by dragging a time slider according to some embodiments of the present application;

[0045] FIG4B is a schematic diagram showing a second scenario of obtaining an event context result by adjusting the time window by dragging a time slider according to some embodiments of the present application;

[0046] FIG4C is a schematic diagram showing a third scenario of obtaining an event context result by adjusting the time window by dragging a time slider according to some embodiments of the present application;

[0047] FIG4D is a schematic diagram showing a fourth scenario of obtaining an event context result by adjusting the time window by dragging a time slider according to some embodiments of the present application;

[0048] FIG5A is a schematic diagram showing a first scenario of adjusting a time window through a date input box to obtain an event context result according to some embodiments of the present application;

[0049] FIG5B is a schematic diagram showing a second scenario of adjusting the time window through the date input box to obtain event context results according to some embodiments of the present application;

[0050] FIG6A is a schematic diagram showing a first scenario of obtaining event context results by adjusting the time window through a quick time period according to some embodiments of the present application;

[0051] FIG6B is a schematic diagram showing a second scenario of obtaining event context results by adjusting the time window through a quick time period according to some embodiments of the present application;

[0052] FIG7A is a schematic diagram showing a first scenario of obtaining an event context result by adjusting a time window through a start and end calendar frame according to some embodiments of the present application;

[0053] FIG7B is a schematic diagram showing a second scenario of obtaining an event context result by adjusting the time window through the start and end calendar frames according to some embodiments of the present application;

[0054] FIG8 is a schematic diagram showing an interaction process between a client and a server of an event context display method according to some embodiments of the present application;

[0055] FIG9 shows a schematic diagram of a hardware structure of a server according to some embodiments of the present application;

[0056] FIG10 shows a schematic diagram of a hardware structure of a client according to some embodiments of the present application. DETAILED DESCRIPTION

[0057] The illustrative embodiments of the present application include, but are not limited to, an event context display method, device, and storage medium.

[0058] The following first briefly describes the background of the method provided in the embodiments of the present application.

[0059] As mentioned earlier, news websites can chronologically organize the development of the same news event at different points in time, providing users with a clear context for the news event. For example, as shown in Figure 1, users can use the event context function to view the schedule for an international sports competition. For example, the schedule may include: a swimming competition at 10:00 on May 20, a diving competition at 10:00 on May 22, and a table tennis competition at 10:00 on May 24.

[0060] In some embodiments, event context can be generated by identifying and extracting text fragments related to the target content from pre-stored events (e.g., articles, news reports, etc.) as a first event; then extracting relevant text content from the first event as a second event, wherein the second event can be a summary, title, etc., which is used to summarize the main information of the first event and is directly related to the target content; finally, the second event is used as a context node to construct a coherent and orderly event context related to the target content.

[0061] In some embodiments, event context can also be generated by collecting documents related to the target event (for example, news reports, forum discussions, etc.), and grouping the documents in chronological order according to the timeline information corresponding to the documents to form multiple time windows, where the time window can be a fixed time interval (for example, one day, one week, etc.); then, for the documents in each time window, text analysis and keyword extraction are performed to understand the changes and evolution trends of event public opinion between different time windows; next, based on the obtained keywords and other information, n event states reflecting the development stage of the target event are determined, where the event state can be a keyword or phrase that describes the characteristics, progress or important turning points of the event; finally, the n event states are formed into an orderly and coherent event context in chronological order to show the development process and evolution of the target event.

[0062] However, the above-mentioned methods of generating event context are all based on a complete event list within the start and end time range of the document-generated event, so that when users use the event context function to understand the development of a certain event, they can only view the pre-generated complete event list within the time range from the start of the event to the latest development of the event. This makes it impossible for users to quickly and accurately understand the circumstances of the event within a specific time period, reducing the efficiency of users in obtaining event progress information.

[0063] In order to solve the above problems, an embodiment of the present application provides an event context display method. In the method of the present application, the user can adjust the time range parameter T of the event context time window on the client through any interactive method (for example, a time slider, a start and end calendar box, etc.); then, the server can obtain the relevant event set E of the target event within the T time window range based on the time range parameter T sent by the client; based on the obtained relevant event set E of the target event within the T time window range and the preset number of events, generate the event context result within the corresponding time range, and return the event context result to the client for display on the display interface. In this way, it is possible to support users in freely adjusting the event context time window, and to obtain the event context result within the corresponding time range based on user interaction information, thereby improving the personalized user experience of users in understanding the progress of events within a specific time range in the event context function.

[0064] In some embodiments, the preset number of events can be determined based on the above-mentioned time range parameter T. For example, when the preset time range T is less than 30 days, the preset number of events is 10; when the preset time range T is greater than 30 days, the preset number of events is 15, etc.

[0065] In some embodiments, the preset number of events may be a preset fixed value. For example, the number of related events in the event context result may be fixed to 10.

[0066] In some embodiments, the user can customize the time window of the event context through a variety of interactive methods, wherein the interactive methods can include directly inputting the start and end range of the time window by voice, and can also include adjusting the time window range by adjusting the display controls of the interactive interface. Among them, the display controls can include various forms, such as quick time periods (for example, shortcut buttons such as "last three days" and "last week"); a time slider, wherein the left end of the slider represents the start date of the time window, and the right end of the slider represents the end date of the time window; a start and end calendar box, in which two dates are selected in the calendar box to represent the start date and end date of the time window respectively; and a date input box, in which the start date and end date of the time window can be directly entered. The user can adjust the time window range through different adjustment methods in the interactive interface, and the embodiments of the present application are not limited to this.

[0067] In some embodiments, after the user adjusts the time window range in the interactive interface, the client can receive the user's interactive information and then adjust the time range parameter T based on the interactive information. For example, if the user specifies the time range as February 5, 2023 to February 15, 2023 through the "date input box", the client determines the input start and end timestamps based on the interactive information and updates the time range parameter T from the default value (event from start to end) to the timestamp "20230205_20230215".

[0068] In some embodiments, the server can obtain a set of related events E of the target event within the time period based on the time range parameter T, wherein the event set E can be a list of events of different granularities (i.e., event details) within the time window. When generating an event list, it is necessary to perform event structuring processing on the document collection of the target event within the time range of T through a natural language processing model, for example, extracting event related information such as event participants, event location, event keywords, and event time; then perform event association on the obtained event related information, for example, obtain an associated event: event participant A experienced event C at location B; finally, obtain a list of all associated events and remove identical events to obtain a set of related events E of the target event within the time range of T.

[0069] In some embodiments, it is necessary to perform event temporal relationship processing on the associated events in the set E of related events related to the target event within the time range T. This involves selecting appropriate methods and models to process and analyze the temporal relationships of events based on the event time information, or the causal relationships and contextual information between events, according to the specific scenario and task requirements. For example, based on the date information in the events, a timeline can be constructed to represent the sequence of events, and the associated events can be arranged according to their position on the timeline to complete event temporal relationship processing.

[0070] In some embodiments, before generating an event context result, it is also necessary to determine a parameter K for the number of event clusters in the generated event context result. The number of event contexts in the final event context result is determined based on the parameter K. The parameter K can be a fixed value or a piecewise function. A fixed value represents a fixed value for any time range parameter T selected by the user. For example, K can be set to a default value of 10, indicating that the event context structure is fixed to 10 related events. The parameter K can also be set to a piecewise function, i.e., it can be assigned different values ​​based on the range of the time range parameter T. For example, when the range of T is less than or equal to 7 days, K is assigned to 3; when the range of T is greater than 7 days and less than or equal to 30 days, K is assigned to 10; and when the range of T is greater than 30 days, K is assigned to 15. This means that when generating an event context result, if the user selects a time range parameter T within 7 days, 3 event context results will be generated; if the time range parameter T is between 7 and 30 days, 10 event context results will be generated; and if the time range parameter T exceeds 30 days, 15 event context results will be generated. In addition, the K value can be adjusted in any manner, and the embodiments of the present application do not limit this.

[0071] In some embodiments, the server can obtain the event context result through a clustering algorithm based on the determined related event set E of the target event within the time range T and the event cluster number parameter K. Among them, the clustering algorithm can refer to dividing the related events in the event set E into K groups, summarizing a feature-related event in each group to represent all the related events of the group, and using the summarized feature-related events as a generated event context result, and finally selecting K events to form the event context result within the time range T. For example, if the user queries the event context results within the six days from April 1 to April 6, and determines that the K value is 2, it is necessary to sort the related events in the event set E by time, and divide the related events of the first three days into the first group, and divide the related events of the last three days into the second group; next, it can be summarized that the first feature-related event represents the first group, and the second feature-related event represents the second group; finally, based on the first feature-related event and the second feature-related event, the event context result within the time range T is formed. In addition, the clustering algorithm can be any clustering algorithm such as K-means clustering, hierarchical clustering, etc., and the embodiments of the present application are not limited to this.

[0072] In some embodiments, the initial complete event context list typically only displays event context results from a macro perspective and overall trends, resulting in a small number of event context results; however, when the user customizes the time window range, a larger number of event context details can be generated by determining the K value. For example, the complete event context list displays only one event that occurred from April 4th to April 5th (for example, Group A won the football match); after the user customizes the time window from April 4th to April 5th, if the K value is determined to be 2, the number of event context events generated in real time becomes 2 and the granularity is more detailed (for example, Group A lost 1 point in the first half of the football match, and Group A won 3 points in the second half of the football match). By customizing the time window by the user, the content and number of event contexts can be changed, thereby improving the user's understanding of the target event.

[0073] It can be understood that the client mentioned above in this application may include terminal devices such as mobile phones, computers, virtual reality (VR) devices, tablets, augmented reality (AR) devices, laptops, etc. In addition, the client may include third-party applications such as Tencent News™ and NetEase News™, but the embodiments of this application do not limit this.

[0074] The following is a brief description of the system architecture of the embodiment of the present application. Figure 2 is a structural diagram of a system architecture provided by the embodiment of the present application, wherein 201 is a user; 202 is a terminal device, which can be used to implement interaction with the user, for example, the user can customize the time window size of the event context in the interactive interface of the terminal device, and the user can see the displayed event context results in the display interface of the terminal device; 203 is a server, which can provide the hardware equipment and software environment for program execution for executing the event context display method mentioned in this application. In addition, the server is also used to receive and process user interaction information from the terminal device and run the event context generation algorithm, and can return the generated event context results to the terminal device; 204 is a storage device, such as a hard disk or other storage device, which is used to store the original text content of the event and can provide the server with a collection of related documents of the target event.

[0075] Based on the above system architecture, the event context display method mentioned in this application can be executed through interaction between users and terminal devices, server processing algorithm logic, and data storage via storage devices. In this way, through interaction between users and terminal devices, users can understand the development of an event within a specific time period.

[0076] Correspondingly, an embodiment of the present application also provides a device for executing an event context display method. The device includes a real-time user interaction module, configured to complete interaction with the user and process changes in time window parameters based on real-time interaction information; a real-time event context generation module, configured to generate different event context results under different time windows in real time based on user interaction information; and a display module, configured to update and display the results generated by the real-time event context generation module. Through the above-mentioned device, a user can customize the time window of the event context in the device, and generate the corresponding event context in real time and return it to the user.

[0077] The following briefly describes the structure of the device for generating event context mentioned in this application based on Figure 3. Figure 3 shows a schematic diagram of the structure of a device according to an embodiment of the present application. Specifically, the device includes the following modules:

[0078] Event context real-time generation module.

[0079] In some embodiments, the real-time event context generation module needs to perform the following two tasks: Task 1: Process the acquired news data of the target event and generate an initial event context result under the initial default parameters (from the start of the event to the latest development time) through the event context generation algorithm; Task 2: Generate event context results within the corresponding time range based on user interaction information. Specifically, when a user enters a news topic page through any window, for example, by searching for news topic keywords through a search engine, the real-time event context generation module will first perform Task 1 and return the complete event context result corresponding to the news to the user; then, the real-time event context generation module will repeatedly perform Task 2 based on the user's interactive behavior, generating different event context results within different time ranges.

[0080] In some embodiments, when the event context real-time generation module performs the above-mentioned task 1, it needs to obtain a set of relevant documents of the target event; then extract event-related information such as event participants, event location, event keywords, and event time from the document collection; then associate the obtained event-related information with events, for example, obtain an associated event: event participant A experienced event C at location B; finally, process the obtained associated events in an event temporal relationship, for example, based on the date information in the associated events, construct a timeline to represent the sequence of associated events, and arrange the associated events according to their positions on the timeline, so as to obtain the initial event context results of the target event from the beginning to the latest development time.

[0081] In some embodiments, when the event context real-time generation module performs the above-mentioned task 2, the event context real-time generation module will receive the time range parameter T returned by the user real-time interaction module (i.e., module 3 mentioned later); then the event context generation algorithm obtains the relevant event set E of the target event within the time period based on the time range parameter T; next, it is necessary to determine the value of the event cluster number parameter K in the generated event context result; finally, based on the relevant event set E and the event cluster number parameter K, the event context result within the time range T is obtained through the clustering algorithm.

[0082] Display module.

[0083] In some embodiments, the display module is mainly responsible for updating and displaying the results generated by the event context real-time generation module. Users can see the event context results generated in real time under different time windows in the display module.

[0084] User real-time interaction module.

[0085] In some embodiments, the user real-time interaction module is mainly used to complete the interaction with the user and process the change of the time range parameter T according to the real-time interaction information.

[0086] In some embodiments, the user will give an input, namely user interaction information, where the interaction information indicates that the user can freely adjust the time window range in real time through any interactive method in the interactive interface; after the user performs the interactive operation, the user real-time interaction module will obtain the information about the time window change; next, the user real-time interaction module will adjust the time range parameter T based on the time window change information. For example, the user specifies the time range from February 5, 2023 to February 15, 2023 through the "date input box". The user real-time interaction module determines the incoming start and end timestamps based on the interaction information, and updates the time range parameter T from the default value (event from start to end) to the timestamp "20230205_20230215".

[0087] In some embodiments, the real-time user interaction module will pass the adjusted time range parameter T to the real-time event context generation module, and generate the event context results within the time range T through the event context generation algorithm. The real-time event context generation module will then pass the generated event context results to the display module for display. The user can see the event context results within the time range T on the display interface and can continue to customize the time window range.

[0088] Based on the above-mentioned device for generating event context, the user can customize the time window of the event context in the device, and the corresponding event context is generated in real time and returned to the user.

[0089] The following briefly describes the scenario in which the user obtains the event context result by adjusting the time window by dragging the time “slider bar” with reference to FIG. 4A to FIG. 4D .

[0090] In some embodiments, when a user accesses a news topic page through any window, for example, by searching for news topic keywords through a search engine, the display interface will display the initial complete event context results under the initial default parameters corresponding to the news (from the start of the event to the latest development time). For example, as shown in Figure 4A, the user can view the complete 34 event contexts of event A from the start to the end of the event on the event context display interface 401. For example, the approximate schedule of an international competition can be seen: the opening ceremony will be held at 10:00 on February 1, the diving competition will be held at 10:00 on February 2, the shooting competition will be held at 9:00 on March 25, the gymnastics competition will be held at 10:00 on March 26, the swimming competition will be held at 10:00 on March 28, and the football match will be held at 10:00 on April 1, etc. 34 event context results.

[0091] Among them, a time slider 4011 will be displayed on the display interface 401 of Figure 4A. The user can adjust the time window range by dragging the left slider 4012 or the right slider 4013 on the time slider 4011. The position of the left slider 4012 on the slider 4011 represents the start date of the time window, and the position of the right slider 4013 on the slider 4011 represents the end date of the time window.

[0092] In some embodiments, as shown in Figure 4A, when the initial complete event context is generated, the left slider 4012 is at the leftmost end of the slider bar 4011 (i.e., the event start date February 1, 2023), and the right slider 4013 is at the rightmost end of the slider bar 4011 (i.e., the event end date April 1, 2023), indicating that the event context result is the entire event context of event A from the start of the event to the end of the event.

[0093] In some embodiments, the user can change the start date of the time window by dragging the left slider on the time slider. For example, as shown in FIG4B , the user can drag left slider 4012 to the position on slider 4011 on March 28, 2023, while right slider 4013 remains at the rightmost end of slider 4011. At this point, the client will update to display interface 402, indicating that the event context results are the event context results for Event A from March 28, 2023, to April 1, 2023. At this point, a more detailed schedule can be viewed, for example: swimming preliminaries at 10:00 AM on March 28, swimming semifinals at 2:00 PM on March 28, swimming finals at 9:00 AM on March 29, football preliminaries at 9:00 AM on March 30, football semifinals at 3:00 PM on March 30, and football finals at 10:00 AM on April 1. Compared with the event context results shown in Figure 4A, Figure 4B shows a more detailed event context results within a specific time range (March 28 to April 1).

[0094] In some embodiments, the user can also change the end date of the time window by dragging the right slider on the time slider. For example, as shown in FIG4C , the user can drag right slider 4013 to the position on slider 4011 on February 2, 2023, while left slider 4012 remains at the far left end of slider 4011. At this point, the client will update to display interface 403, indicating that the event context results are the event context results for Event A from February 1 to February 2, 2023. At this point, more detailed event schedules can be seen, such as: opening ceremony at 10:00 on February 1, fireworks display at 19:00 on February 1, diving competition preliminaries at 10:00 on February 2, and diving competition rematches at 15:00 on February 2. Compared to the event context results shown in FIG4A , FIG4C shows a more detailed event context results for the specific time range (February 1 to February 2).

[0095] In some embodiments, the user can also change the start and end dates of the time window by simultaneously dragging the left and right sliders on the time slider. For example, as shown in FIG4D , the user can simultaneously change the positions of the left slider 4012 and the right slider 4013 on the slider 4011. At this time, the client will update to display interface 404, indicating that the event context result is the event context result of event A from March 25, 2023 to March 26, 2023. At this time, a more detailed schedule can be seen, for example: the shooting competition semi-finals will be held at 9:00 on March 25, the shooting competition finals will be held at 14:00 on March 25, the gymnastics competition preliminaries will be held at 10:00 on March 26, and the gymnastics competition semi-finals will be held at 15:00 on March 26. Compared with the event context result shown in FIG4A , FIG4D shows a more detailed event context result within the specific time range (March 25 to March 26).

[0096] It can be understood that in the embodiment of the present application, the user can interact with the client by dragging the time slider at will, and the server will generate event interaction results within different time ranges based on the interaction information and return them to the user.

[0097] The following briefly describes the scenario in which the user adjusts the time window through the "date input box" to obtain the event context result with reference to FIG. 5A and FIG. 5B .

[0098] In some embodiments, when a user enters a news topic page through any window, for example, by searching for news topic keywords through a search engine, the display interface will display the initial complete event context results under the initial default parameters corresponding to the news (from the start of the event to the latest development time). For example, as shown in Figure 5A, the user can view the complete 34 event contexts of event A from the start to the end of the event on the event context display interface 501. Among them, the display interface 501 will display a date input box 5011 and a date input box 5012. The date input box 5011 on the left indicates the start date of the time window, and the date input box 5012 on the right indicates the end date of the time window. The user can select any date as the start date of the time window through the date selector 5011A in the date input box 5011, and select any date as the end date of the time window through the date selector 5012A in the date input box 5012. Among them, the date selector indicates that the user can expand the calendar interface by clicking a button, and the user can select a specific date on the calendar interface.

[0099] In some embodiments, as shown in FIG5A , when generating an initial complete event context, date input box 5011 displays the initial occurrence date of Event A, February 1, 2023, and date input box 5012 displays the end date of Event A, April 1, 2023, indicating that the event context result represents the entire event context from the start to the end of Event A. For example, a general schedule of events for an international competition can be displayed: the opening ceremony at 10:00 AM on February 1, the shooting competition at 9:00 AM on March 25, the gymnastics competition at 10:00 AM on March 26, the football match at 10:00 AM on April 1, and so on, totaling 34 event context results.

[0100] In some embodiments, the user can select any date in the date input box as the start date or end date of the time window. For example, as shown in Figure 5B, the user selects March 25, 2023, in the date input box 5011 through the date selector 5011A, and selects March 26, 2023, in the date input box 5012 through the date selector 5012A. At this time, the client will update to the display interface 502, indicating that the event context result is the event context result of event A from March 25, 2023 to March 26, 2023. At this time, more detailed schedule arrangements can be seen, for example: the shooting competition semi-finals will be held at 9:00 on March 25, the shooting competition finals will be held at 14:00 on March 25, the gymnastics competition preliminaries will be held at 10:00 on March 26, and the gymnastics competition semi-finals will be held at 15:00 on March 26. Compared with the event context results shown in Figure 5A, Figure 5B shows a more detailed event context results within a specific time range (March 25 to March 26).

[0101] It can be understood that in the embodiment of the present application, the user can interact with the client by selecting any time in the date input box, and the server will generate event interaction results within different time ranges based on the interaction information and return them to the user.

[0102] The following briefly describes the scenario in which the user adjusts the time window through the “Quick Time Period” to obtain the event context result with reference to FIG. 6A and FIG. 6B .

[0103] In some embodiments, when a user accesses a news topic page through any window, for example, by searching for a news topic keyword through a search engine, the display interface will display the initial complete event context results corresponding to the news under the initial default parameters (from the start of the event to the latest development time). For example, as shown in Figure 6A, the user can view the complete 34 event contexts of event A from the start to the end of the event on the event context display interface 601. For example, the approximate schedule of an international competition can be seen: the opening ceremony will be held at 10:00 on February 1, the diving competition will be held at 10:00 on February 2, the shooting competition will be held at 9:00 on March 25, the gymnastics competition will be held at 10:00 on March 26, the swimming competition will be held at 10:00 on March 28, and the football match will be held at 10:00 on April 1, etc. 34 event context results.

[0104] Among them, the quick time periods of "last three days", "last week", "last month" and "last three months" will be displayed on the display interface 601 of Figure 6A. The user can select any quick time period button to view the event context results of the corresponding time range.

[0105] In some embodiments, as shown in FIG6B , a user can click the "Last Three Days" shortcut time button to view the progress of Event A over the three days preceding the event's end date. At this point, the client will update to display interface 602, indicating that the event context results are for Event A from March 30th to April 1st. At this point, a more detailed schedule can be seen: the preliminary round of the football match will be held at 9:00 AM on March 30th, the semi-final round will be held at 3:00 PM on March 30th, the final round will be held at 2:00 PM on March 31st, and the final round will be held at 10:00 AM on April 1st. Compared to the event context results shown in FIG6A , FIG6B shows a more detailed event context results within a specific time range (March 30th to April 1st).

[0106] In some embodiments, the quick time period can be set arbitrarily, for example, it can be set to "last 15 days", "last 30 days", etc., and this embodiment of the present application does not limit this.

[0107] It can be understood that in the embodiment of the present application, the user can interact with the client by selecting a quick time period, and the server will generate event interaction results within different time ranges based on the interaction information and return them to the user.

[0108] The following briefly describes the scenario in which the user adjusts the time window through the "start and end calendar box" to obtain the event context result with reference to FIG. 7A and FIG. 7B .

[0109] In some embodiments, when a user enters a news topic page through any window, for example, by searching for news topic keywords through a search engine, the display interface will display the initial complete event context results under the initial default parameters corresponding to the news (from the start of the event to the latest development time). For example, as shown in Figure 7A, the user can view the complete 34 event contexts of event A from the start to the end of the event on the event context display interface 701.

[0110] Among them, the start and end calendar frame icon 7011 will be displayed on the display interface 701 of Figure 7. The user can enter the date selection interface 7012 by clicking the start and end calendar frame 7011, and select any two times in the calendar 7013 of the date selection interface 7012 as the start time and end time of the time window.

[0111] In some embodiments, as shown in FIG7A , when generating an initial complete event context, clicking on the start and end calendar frame 7011 enters the date selection interface 7012, which displays the start and end times of Event A, indicating that the event context result is the entire event context from the start to the end of Event A. For example, the approximate schedule of an international competition can be viewed: the opening ceremony at 10:00 AM on February 1st, the diving competition at 10:00 AM on February 2nd, the shooting competition at 9:00 AM on March 25th, the gymnastics competition at 10:00 AM on March 26th, the swimming competition at 10:00 AM on March 28th, and the football match at 10:00 AM on April 1st, among other 34 event context results.

[0112] In some embodiments, as shown in FIG7B , the user enters a date selection interface 7012 by clicking on the start and end calendar frame 7011. In the calendar 7013 of the date selection interface 7012, the user selects a time window from February 1, 2023, to February 3, 2023. Then, by clicking on the run button (i.e., the GO button), the event context results for the corresponding time range are obtained. The client is then updated to display interface 702, indicating that the event context results are the event context results for Event A from February 1 to February 3. At this point, more detailed event schedules can be viewed, for example: the opening ceremony will be held at 10:00 on February 1, the fireworks display will be held at 19:00 on February 1, the diving competition preliminaries will be held at 10:00 on February 2, the diving competition semi-finals will be held at 15:00 on February 2, and the diving competition finals will be held at 10:00 on February 3. Compared to the event context results shown in FIG7A , FIG7B displays more detailed event context results within the specific time range (February 1 to February 3).

[0113] It can be understood that in the embodiment of the present application, the user can arbitrarily select a time window range through the start and end calendar boxes to interact with the client, and the server will generate event interaction results within different time ranges based on the interaction information and return them to the user.

[0114] The following describes the interaction process between the client and the server when executing the event context display method in an embodiment of the present application based on the interaction process diagram shown in Figure 8. The event context display method can be executed by the client and the server. As shown in Figure 8, the interaction process specifically includes the following steps:

[0115] 801: The client receives first interaction information from the user.

[0116] It can be understood that in the embodiment of the present application, the first interaction information is query information input by the user. For example, the first interaction information may be a keyword of a target event to be queried input by the user.

[0117] In some embodiments, when a user enters a news topic page through any window, for example, by searching for news topic keywords through a search engine, the client receives the first interaction information.

[0118] 802: The client sends first interaction information to the server.

[0119] It can be understood that in the embodiment of the present application, after the client receives the first interaction information of the user, it will send the first interaction information to the server, and the server will receive the first interaction information and perform corresponding processing.

[0120] 803: The server generates a first event context result.

[0121] It can be understood that in an embodiment of the present application, after the server receives the first interaction information sent by the client, the server will first generate the initial complete event context of the target event queried by the user from the beginning of the event (or the initial record of the event) to the latest development stage of the event.

[0122] In some embodiments, when generating the first event context result (i.e., the initial event context result), it is first necessary to extract the document collection of the target event queried by the user; then, it is necessary to perform event structuring processing on the document collection of the target event through a natural language processing model, for example, extracting event related information such as event participants, event location, event keywords, and event time; then, the obtained event related information is associated with events, for example, an associated event is obtained: event participant A has event C at location B, a list of all associated events is obtained and the same events are removed; finally, the associated events are processed according to the event time sequence relationship, that is, the associated events are sorted according to the order of the events, and the initial complete event context result can be obtained.

[0123] In some embodiments, when generating the first event context result, the time window range parameter T is a default value "DEFAULT", which indicates that the time range of the initial event context result is from the earliest event occurrence time to the latest event occurrence time.

[0124] 804: The server sends the first event context result to the client.

[0125] It can be understood that in the embodiment of the present application, after the server generates the first event context result of the target event, the server will send the first event context result to the client.

[0126] 805: The client displays the result of the first event context.

[0127] It can be understood that in the embodiment of the present application, after the client receives the first event context result sent by the server, the client will display the first event context result on the display interface.

[0128] 806: The client receives the second interaction information from the user.

[0129] It is understood that in the embodiment of the present application, the second interaction information may be related information of a time range selected by the user. The client may receive the second interaction information between the user and the client in any manner.

[0130] In some embodiments, the interaction between the user and the client can be in various ways. For example, for the time slider shown in Figures 4A to 4D, the second interaction information may refer to the user being able to adjust the time range by dragging the slider; for the date input box shown in Figures 5A and 5B, the second interaction information may refer to the user directly entering the time range in the date input box; for the quick time period shown in Figures 6A and 6B (for example, shortcut buttons such as "last three days" and "last week"), the second interaction information may refer to any shortcut button selected by the user; for the start and end calendar boxes shown in Figures 7A and 7B, the second interaction information may refer to the user selecting two dates in the calendar box to represent the start date and end date of the time window, respectively. The user can interact with the client in different ways in the interactive interface, and the embodiments of the present application are not limited to this.

[0131] 807: The client adjusts the time window parameters.

[0132] It can be understood that in the embodiment of the present application, after the client receives the second interaction information of the user, the client will adjust the time window range T based on the second interaction information.

[0133] In some embodiments, for example, the user specifies the time range from February 5, 2023 to February 15, 2023 through the "date input box", and the client determines the incoming start and end timestamps based on the second interaction information, and updates the time window range T from the default value (event from start to end) to the timestamp "20230205_20230215".

[0134] 808: The client sends the time window parameters to the server.

[0135] It can be understood that in the embodiment of the present application, after the client adjusts the time window range T based on the user's second interaction information, the client will send the time window range T to the server.

[0136] 809: The server obtains a set of related events within the time window.

[0137] It is understood that in the embodiment of the present application, after the server obtains the time window parameter T, it is necessary to extract the relevant event set E of the target event within the time range T based on the time window parameter. The event set E can be a list of events of different granularities (i.e., event details) within the time window.

[0138] In some embodiments, in some embodiments, when generating an event list in a related event set E, it is necessary to perform event structuring processing on the document collection of the target event within the time range of T through a natural language processing model, for example, extracting event related information such as event participants, event location, event keywords, and event time; then perform event association on the obtained event related information, for example, obtain the associated event: event C occurred at location B for event participant A; finally, obtain a list of all associated events and remove the same events to obtain the related event set E of the target event within the time range of T.

[0139] In some embodiments, it is also necessary to perform event temporal relationship processing on the associated events in the set E of related events related to the target event within the time range T. This involves selecting appropriate methods and models to process and analyze the temporal relationships of events based on the event time information, the causal relationships between events, and the contextual information, according to the specific scenario and task requirements. For example, based on the date information in the events, a timeline can be constructed to represent the sequence of events, and the associated events can be arranged according to their position on the timeline to complete event temporal relationship processing.

[0140] 810: The server determines the number of events preset in the second event context result.

[0141] It can be understood that in the embodiment of the present application, before generating the second event context result, the server also needs to determine the event cluster quantity parameter K in the generated second event context result.

[0142] In some embodiments, parameter K can be a fixed value or a piecewise function. The fixed value means that the user selects any time range parameter T, and the K value remains unchanged. For example, K can be set to a default value of 10, indicating that the event context structure is fixed to 10 related events.

[0143] In some embodiments, the value of parameter K can also be set as a piecewise function, that is, it can be assigned different values ​​according to the different ranges of the time range parameter T. For example, when the range of T is less than or equal to 7 days, K is assigned to 3; when the range of T is greater than 7 days and less than or equal to 30 days, K is assigned to 10; when the range of T is greater than 30 days, K is assigned to 15. This means that when generating event context results, if the user selects the time range parameter T to be within 7 days, 3 event context results will be generated; if the time range parameter T is between 7 and 30 days, 10 event context results will be generated; and if the time range parameter T exceeds 30 days, 15 event context results will be generated. In addition, the value of K can be adjusted in any manner, and this embodiment of the application is not limited to this.

[0144] 811: The server generates a second event context result.

[0145] It can be understood that in the embodiment of the present application, the server can generate a second event context result within the corresponding time range through a clustering algorithm based on the determined related event set E of the target event within the time range T and the event cluster quantity parameter K.

[0146] In some embodiments, the clustering algorithm may refer to dividing the related events in the event set E into K groups, summarizing a characteristic related event in each group to represent all the related events in the group, and using the summarized characteristic related events as a generated event context result, and finally selecting K events to form the event context result within the time range of T. For example, if the user queries the event context results within the six days from April 1 to April 6, and determines that the K value is 2, it is necessary to sort the related events in the event set E by time, and divide the related events of the first three days into the first group, and the related events of the last three days into the second group; next, it can be summarized that the first characteristic related event represents the first group, and the second related event represents the second group; finally, based on the first characteristic related event and the second characteristic related event, a second event context result (i.e., the event context result corresponding to the time range of T) is formed.

[0147] 812: The server sends the second event context result to the client.

[0148] It can be understood that in the embodiment of the present application, after the server generates the event context result within the corresponding time range, the server will send the second event context result to the client.

[0149] 813: The client displays the result of the second event context.

[0150] It can be understood that in the embodiment of the present application, after the client receives the second event context result sent by the server, the client will display the second event context result on the display interface.

[0151] Based on this method, users can customize the time window of an event context through any interactive method. Adjusting the event context time window parameters is determined by the user's own behavior. After the interaction is completed, the client and server process the time window parameter changes based on this interaction information and generate different event context results in real time and return them to the user, greatly improving the user experience of understanding the event context within a specific time range. Furthermore, user-defined time window adjustment can also change the content and number of event context items, improving the user's understanding of the target event.

[0152] The event context display method described above can be executed by electronic devices, which can be server-side or client-side. The client can be a mobile phone, computer, virtual reality (VR) device, tablet computer, augmented reality (AR) device, laptop computer, or other terminal device. Furthermore, the client can include third-party applications such as Tencent News™ and NetEase News™, but this embodiment of the application does not limit this.

[0153] The following is an example of the hardware structure diagram of the server side in the embodiment of the present application, taking the electronic device 1100 shown in Figure 9 as an example. As shown in Figure 9, the electronic device 1100 may include one or more processors 1102, a system control logic 1101 connected to at least one of the processors 1102, a system memory 1105 connected to the system control logic 1101, a storage 1103 connected to the system control logic 1101, and a network interface 1108 connected to the system control logic 1101.

[0154] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute the only possible implementation of the electronic device 1100. In other embodiments of the present application, the electronic device 1100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0155] Processor 1102 may include one or more single-core or multi-core processors. In some embodiments, processor 1102 may include any combination of general-purpose processors and specialized processors (e.g., application processors, baseband processors, etc.). It will be understood that in embodiments of the present application, processor 1102 may be configured to execute executable instructions 1104 stored in memory 1103 to implement the method steps executed by the server in the event context display method of the present application.

[0156] The system control logic 1101 may include any suitable interface controller to provide any suitable interface to at least one of the processors 1102 and / or any suitable device or component in communication with the system control logic 1101. The system control logic 1101 may include one or more memory controllers to provide an interface to the system memory 1105. The system memory 1105 may be used to load and store data and / or instructions. In some embodiments, the system memory 1105 of the electronic device 1100 may include any suitable volatile memory, such as a suitable dynamic random access memory.

[0157] The memory 1103 may include one or more tangible, non-transitory computer-readable media for storing data and / or instructions. In some embodiments, the memory 1103 may include any suitable volatile memory and / or any suitable non-volatile storage device. For example, the memory 1103 may include a random access memory (RAM) and / or a cache memory, and may further include a read-only memory (ROM).

[0158] The memory 1103 may include a portion of storage resources on a device on which the electronic device 1100 is installed, or it may be accessible to the device but not necessarily a portion of the device. For example, the memory 1103 may be accessed via a network via the network interface 1108 .

[0159] Specifically, system memory 1105 and storage 1103 may respectively include a temporary copy and a permanent copy of instructions 1106, and a temporary copy and a permanent copy of instructions 1104. Instructions 1106 may include instructions that, when executed by at least one of processors 1102, cause electronic device 1100 to implement the event context display method according to an embodiment of the present invention. In some embodiments, instructions 1106, hardware, firmware, and / or software components thereof may additionally or alternatively be located in system control logic 1101, network interface 1108, and / or processor 1102.

[0160] The network interface 1108 may include a transceiver for providing a radio interface for the electronic device 1100, thereby enabling communication with any other suitable device (such as a front-end module, an antenna, etc.) via one or more networks. In some embodiments, the network interface 1108 may be integrated with other components of the electronic device 1100. For example, the network interface 1108 may be integrated with at least one of the processor 1102, the system memory 1105, the storage 1103, and a firmware device (not shown) having instructions. When at least one of the processors 1102 executes the instructions, the electronic device 1100 implements the method steps executed by the server side in the event context display method according to an embodiment of the present invention.

[0161] The network interface 1108 may further include any suitable hardware and / or firmware to provide a multiple-input multiple-output radio interface. For example, the network interface 1108 may be a network adapter, a wireless network adapter, a telephone modem, and / or a wireless modem.

[0162] The electronic device 1100 may further include an input / output (I / O) device 1107. In some embodiments, the electronic device 1100 further includes a sensor for determining at least one of an environmental condition and location information related to the electronic device 1100.

[0163] In some embodiments, the peripheral component interface may include, but is not limited to, a non-volatile memory port, an audio jack, and a power interface.

[0164] In some embodiments, the sensors may include, but are not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with the network interface 1108 to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites).

[0165] The following is an example of the hardware structure diagram of the client in the embodiment of the present application, taking the electronic device 1200 shown in Figure 10 as an example. As shown in Figure 10, the electronic device 1200 may include a processor 110, a power module 140, a memory 180, a mobile communication module 130, a wireless communication module 120, a sensor module 190, an audio module 150, a camera 170, an interface module 160, a button 101, a display screen 102, and a touch screen 103.

[0166] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute the only possible implementation of the electronic device 1200. In other embodiments of the present application, the electronic device 1200 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0167] The processor 110 may include one or more processing units, for example, a processing module or processing circuit such as a central processing unit, an image processor, a digital signal processor, a microprocessor or a programmable logic device. Different processing units may be independent devices or integrated into one or more processors. A storage unit may also be provided in the processor 110 for storing instructions and data. In some embodiments, the storage unit in the processor 110 is a cache memory 180, which may store instructions or data that the processor 110 has just used or is cyclically using. If the processor 110 needs to use the instruction or data again, it may be directly called from the storage unit, thereby avoiding repeated access, reducing the waiting time of the processor 110, and thus improving the efficiency of the system.

[0168] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0169] It can be understood that in the embodiment of the present application, the processor can be used to execute the method steps executed by the client in the event context display method of the present application.

[0170] The power module 140 may include a power supply, a power management component, and the like. The power supply may be a battery. The power management component manages the charging of the power supply and the supply of power to other modules. In some embodiments, the power management component includes a charging management module and a power management module. The charging management module receives charging input from a charger; the power management module connects to a power supply and is connected to the processor 110. The power management module receives input from the power supply and / or the charging management module and provides power to the processor 110, the display 102, the camera 170, and the wireless communication module 120.

[0171] The mobile communication module 130 may include but is not limited to an antenna, a power amplifier, a filter, etc. The mobile communication module 130 may provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 1200. The mobile communication module 130 may receive electromagnetic waves through the antenna, filter, amplify, and perform other processing on the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 130 may also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna. In some embodiments, at least some of the functional modules of the mobile communication module 130 may be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 130 may be set in the same device as at least some of the modules of the processor 110.

[0172] The wireless communication module 120 may include an antenna and transmit and receive electromagnetic waves via the antenna. The wireless communication module 120 may provide wireless communication solutions for the electronic device 1200, including wireless local area networks, Bluetooth, global navigation satellite systems, frequency modulation (FM), near field communication (NFC), infrared (IR), and other wireless communication technologies. The electronic device 1200 may communicate with the network and other devices using wireless communication technologies.

[0173] In some embodiments, the mobile communication module 130 and the wireless communication module 120 of the electronic device 1200 may also be located in the same module.

[0174] Display screen 102 is used to display human-computer interaction interfaces, images, videos, etc. Display screen 102 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light emitting diode (OLED), or an active-matrix organic light emitting diode (AMOLED).

[0175] The sensor module 190 may include a proximity sensor, a pressure sensor, a gyro sensor, an acceleration sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, an electromagnetic wave absorption rate sensor, a sound sensor, and the like.

[0176] The audio module 150 is used to convert digital audio signals into analog audio signals for output, or to convert analog audio input into digital audio signals. The audio module 150 can also be used to encode and decode audio signals. In some embodiments, the audio module 150 can be provided in the processor 110, or some functional modules of the audio module 150 can be provided in the processor 110. In some embodiments, the audio module 150 can include a speaker, an earpiece, a microphone, and a headphone jack.

[0177] Camera 170 is used to capture still images or video. The lens generates an optical image of an object and projects it onto a photosensitive element. The photosensitive element converts the optical signal into an electrical signal, which is then passed to image signal processing for conversion into a digital image signal. Electronic device 1200 implements its camera function through an ISP, camera 170, video codec, graphics processor, display 102, and application processor.

[0178] The interface module 160 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 1200, or to enable the electronic device 1200 to communicate with other electronic devices.

[0179] In some embodiments, the electronic device 1200 further includes a button 101, a motor, and an indicator. The button 101 may include a volume button, an on / off button, and the like. The motor is used to vibrate the electronic device 1200. Different vibration feedback effects may correspond to different application scenarios (e.g., time reminders, etc.). The indicator may include a laser pointer, an LED indicator, and the like.

[0180] The various embodiments disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0181] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor, a microcontroller, an application specific integrated circuit, or a microprocessor.

[0182] Program code can be implemented with a high-level programming language or an object-oriented programming language to communicate with the processing system. Where necessary, program code can also be implemented in assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0183] In some cases, the disclosed embodiments can be implemented in hardware, firmware, software or any combination thereof. The disclosed embodiments can also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which can be read and executed by one or more processors. For example, instructions can be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, including but not limited to, a floppy disk, an optical disk, an optical disk, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), a magnetic card or an optical card, an erasable programmable read-only memory (EPROM), a flash memory, an electrically erasable programmable read-only memory (EEPROM), or a tangible machine-readable memory for transmitting information (e.g., a carrier wave, an infrared signal digital signal, etc.) using the Internet in an electrical, optical, acoustic or other form of propagation signal. Accordingly, machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, a computer).

[0184] In the accompanying drawings, some structural or method features may be shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or order may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of a structural or method feature in a particular figure does not imply that such a feature is required in all embodiments, and in some embodiments, such features may not be included or may be combined with other features.

[0185] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems raised by this application. In addition, in order to highlight the innovative part of this application, the above-mentioned device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems raised by this application. This does not mean that other units / modules do not exist in the above-mentioned device embodiments.

[0186] It should be noted that in the examples and description of this patent, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "including a" does not exclude the presence of other identical elements in the process, method, article or device that includes the element.

[0187] While the present application has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the present application.

Claims

1. A method for displaying event context, characterized in that: The method comprises: The client displays the first event context result corresponding to the first time period; The client detects a first instruction from the user, where the first instruction is used to instruct display of a second event context result corresponding to a second time period in the first time period; The client displays a second event context result corresponding to the second time period in response to the first instruction of the user, wherein the number of events displayed in the second event context result is greater than the number of events displayed in the third event context result, wherein the third event context result is the event context within the second time period in the first event context result.

2. The method according to claim 1, characterized in that The client displays, in response to the first instruction of the user, a second event context result corresponding to the second time period, including: The client sends a second time period corresponding to the first instruction to the server; The server generates a second event context result corresponding to the second time period based on the second time period, and sends the second event context result to the client; The client displays a second event context result corresponding to the second time period.

3. The method according to claim 2, characterized in that The generating a second event context result corresponding to the second time period based on the second time period includes: Acquire an event set corresponding to the second time period based on the second time period; Determine the number of events to display; Based on the event set corresponding to the second time period and the event display quantity, a second event context result corresponding to the second time period is generated.

4. The method according to claim 3, characterized in that The acquiring, based on the second time period, a set of events corresponding to the second time period includes: Extracting a document set corresponding to the second time period; Based on the document set corresponding to the second time period, obtaining a set of associated events corresponding to the second time period; Performing timing adjustment on each associated event in the associated event set corresponding to the second time period to obtain an event set corresponding to the second time period.

5. The method according to claim 4, characterized in that The obtaining, based on the document set corresponding to the second time period, a set of associated events corresponding to the second time period, includes: Extracting event related information from the document set corresponding to the second time period, the event related information including: at least one of event participants, event location, event keywords, and event time; Perform event association on the event-related information to obtain a set of associated events corresponding to the second time period.

6. The method according to claim 4, characterized in that The step of adjusting the timing of each associated event in the associated event set corresponding to the second time period to obtain the event set corresponding to the second time period includes: Adjusting the order of the associated events in the associated event set corresponding to the second time period based on the temporal relationship of the associated events, to obtain an event set corresponding to the second time period; The temporal relationship includes at least one of time sequence and event causal relationship.

7. The method according to claim 3, characterized in that The determining of the number of event displays includes: The number of events to be displayed corresponding to the second event context result is determined based on the length of the second time period.

8. The method according to claim 3, characterized in that The determining of the event display quantity includes: using a preset event display quantity as the event display quantity corresponding to the second event context result.

9. The method according to claim 3, characterized in that: The generating, based on the event set corresponding to the second time period and the number of event displays, a second event context result corresponding to the second time period includes: Based on the number of displayed events, clustering processing is performed on the event set corresponding to the second time period to generate a second event context result, wherein the number of clusters in the clustering processing is the same as the number of displayed events.

10. The method according to claim 9, characterized in that The clustering of the event set corresponding to the second time period based on the number of event displays to generate a second event context result includes: determining a number of clusters based on the number of event displays; Performing clustering processing on the event set corresponding to the second time period based on the number of clusters to obtain multiple cluster sets; Determining each feature-related event in each of the cluster sets; The second event context result is determined based on the feature-related events.

11. The method according to any one of claims 1 to 10, characterized in that The first instruction includes: one or more of a voice instruction and a display control for adjusting a display interface of the client.

12. The method according to claim 11, characterized in that The display controls include: a quick time period key, a time slide bar, a start and end calendar box, and one or more display controls in a date input box.

13. The method according to claim 1, characterized in that The method further comprises: The server side extracts the document set corresponding to the first time period; The server generates a first event context result corresponding to the first time period based on the document set corresponding to the first time period, and sends the first event context result to the client.

14. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store instructions executed by one or more processors of the electronic device, and the processor is one of the one or more processors of the electronic device, and is used to execute the event context display method described in any one of claims 1-13.

15. A readable storage medium, characterized in that: The readable storage medium stores instructions, and when the instructions are executed on an electronic device, the electronic device executes the event context display method according to any one of claims 1 to 13.

Images