WO2023246314A1 - 信息处理方法、信息处理系统、电子设备及存储介质 - Google Patents

信息处理方法、信息处理系统、电子设备及存储介质 Download PDF

Info

Publication number
WO2023246314A1
WO2023246314A1 PCT/CN2023/091593 CN2023091593W WO2023246314A1 WO 2023246314 A1 WO2023246314 A1 WO 2023246314A1 CN 2023091593 W CN2023091593 W CN 2023091593W WO 2023246314 A1 WO2023246314 A1 WO 2023246314A1
Authority
WO
WIPO (PCT)
Prior art keywords
template
list
information
scheduled task
item
Prior art date
Application number
PCT/CN2023/091593
Other languages
English (en)
French (fr)
Other versions
WO2023246314A9 (zh
Inventor
李晢曦
毛宗鑫
李铃
郭充
Original Assignee
京东方科技集团股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司 filed Critical 京东方科技集团股份有限公司
Publication of WO2023246314A1 publication Critical patent/WO2023246314A1/zh
Publication of WO2023246314A9 publication Critical patent/WO2023246314A9/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/186—Templates

Definitions

  • the present disclosure relates to the field of display technology, and in particular, to an information processing method, an information processing system, an electronic device, and a storage medium.
  • the event information of some events In the field of information display technology, it is generally necessary to display the event information of some events on the terminal in the form of an event list. During the display, it is also necessary to continuously update the event list displayed on the terminal according to the order of the occurrence period of the events, so as to Let users know what is happening and what will happen. For example, the schedule information of each flight is displayed on a large screen, or the meeting reservation list of a physical conference room is displayed on a smaller flat screen. The meeting reservation list can help users know what time periods the physical conference room is. What meetings are scheduled?
  • the server is required to update the event list displayed on the terminal according to the occurrence time of each event information.
  • the server will frequently update the list of items displayed on the terminal.
  • intensive update events there will be intensive update events that are very close in time between the server and the terminal.
  • intensive update events will cause thread crashes, causing the update Failure.
  • intensive update events will cause problems such as network congestion and delay, resulting in inaccurate updates.
  • the present disclosure provides an information processing method, which includes:
  • Each item of information includes the occurrence period of the event and the corresponding scheduled task; the scheduled task is used to trigger the server to update the terminal at the trigger time point.
  • a list of events displayed on the website which includes information on events that are currently occurring and/or are yet to occur;
  • a target timing task is determined from the current timing task to be triggered and the next timing task to be triggered, and when the target timing task is triggered, Click to update the list of items displayed on the terminal.
  • a target scheduled task is determined from the current scheduled task to be triggered and the next scheduled task to be triggered, include:
  • the trigger time interval is greater than the first preset threshold, it is determined that the current scheduled task to be triggered and the next scheduled task to be triggered are both the target scheduled tasks;
  • the trigger time interval is not greater than the first preset threshold, it is determined that among the current scheduled task to be triggered and the next scheduled task to be triggered, the one with a later occurrence period is the target scheduled task. .
  • the method further includes:
  • the interval length between the first occurrence period and the second occurrence period is determined; the first occurrence period is the period corresponding to the currently to-be-triggered scheduled task.
  • the occurrence period of the event, the second occurrence period is the occurrence period of the event corresponding to the next scheduled task to be triggered;
  • event idle information is generated based on the first occurrence period and the second occurrence period; the matter idle information is used to indicate that during the first occurrence period
  • the period between the second occurrence period and the second occurrence period can be reserved;
  • the item availability information is added to the item list displayed on the terminal, so as to display the time period that can be reserved in the item list.
  • the item list is generated through the following steps:
  • the event list is generated based on the event list template and the event information of the events that are occurring and/or are to occur.
  • the step of updating the item list displayed on the terminal at the trigger time of the target scheduled task includes:
  • the target scheduled task obtain the first item information corresponding to the target scheduled task and the second item information, wherein the occurrence period of the second item information is located in the item corresponding to the target scheduled task after the occurrence period;
  • the new item list is sent to the terminal to update the item list displayed on the terminal.
  • the method further includes:
  • the updated item list is sent to the terminal, so that the terminal refreshes the displayed item list.
  • the triggering time point of the scheduled task corresponding to each item of information is determined based on the occurrence period of the item of information; the method further includes:
  • the trigger time point of the scheduled task corresponding to the second item information is updated according to the updated occurrence period.
  • the method further includes:
  • the event information corresponding to the target scheduled task is sent to the display device, so that the display device refreshes the displayed event information.
  • the method further includes:
  • the step of updating the list of items displayed on the terminal at the trigger time of the target scheduled task includes:
  • the list of items currently displayed on the target terminal is updated; wherein the current performance parameter of the target terminal is greater than or equal to the target performance parameter.
  • Embodiments of the present disclosure also provide an information processing method, applied to the client.
  • the method includes:
  • the entered matter information is obtained; wherein the matter information includes the occurrence period of the matter and the corresponding scheduled task; the scheduled task is used to trigger the server to update the terminal at the trigger time point Displayed event list, the event list includes event information of events that are currently occurring and/or are to occur;
  • the server determines the trigger time interval between the current scheduled task to be triggered and the next scheduled task to be triggered before triggering the current scheduled task to be triggered; and based on The trigger time interval and the sequence of the occurrence periods are determined from the current scheduled task to be triggered and the next scheduled task to be triggered, and the target scheduled task is determined at the trigger time point of the target scheduled task. , updating the list of items displayed on the terminal.
  • the method before the step of sending the matter information to the server, the method further includes:
  • the matter list template is exported as object-notation JSON type data, it is uploaded to the server, so that the server is based on the obtained matter list template and the matter information of the matters that are occurring and/or are to occur. , generate a list of said matters.
  • the template setting interface includes table configuration items
  • the step of obtaining the drawn item list template in response to the drawing operation of the item list template on the template setting interface includes:
  • table attribute parameters include at least one of table size, number of rows, and number of columns;
  • the corresponding text is added to the cell as the header to obtain the matter list template.
  • the method further includes:
  • the corresponding text is added to the cell as the header to obtain the matter list template, including:
  • the corresponding text is added to the cell as the header, and the table body text attribute is bound to the corresponding cell to obtain the matter list template.
  • the step of generating a table in response to the table attribute parameters entered in the table configuration item includes:
  • the table is generated based on the position coordinates of each cell in the table coordinate system.
  • uploading the matter list template to the server includes:
  • the template setting interface includes a drawing canvas, and before the step of obtaining the drawn matter list template in response to the drawing completion operation of the matter list template performed on the template setting interface, The method also includes:
  • the template elements generated under the drawing operation are recorded, and one template element represents a modified item list template;
  • the drawing operations include but are not limited to any of the following : Drawing operations of graphics in the item list template and editing operations of table attribute parameters;
  • the target template element corresponding to the undo/redo operation is rendered to the drawing canvas.
  • the template elements generated under the drawing operation are recorded, including:
  • the step of rendering the target template element corresponding to the undo/restore operation among the recorded template elements to the drawing canvas includes:
  • the operation step Based on the operation step, search for the target template element corresponding to the operation step starting from the last recorded template element, and render the target template element to the drawing canvas; wherein the operation step includes undo The step size of the type and the step size of the recovery type.
  • the method further includes:
  • the template element and the number of operation steps corresponding to the template element are recorded in the global state object; the number of operation steps represents the drawing operation corresponding to the template element;
  • search for the template element corresponding to the operation step starting from the last recorded template element including:
  • a template element whose operation step number corresponds to the operation step size is searched from the global state object.
  • each of the template elements in the global state object is arranged in the order of operation steps, and the method further includes:
  • the target template element is not the last template element of the record, delete the template elements after the target template element; and/or when the number of template elements of the global state object exceeds the target number, Delete the previously arranged template element;
  • the template element and the number of operation steps corresponding to the template element are recorded into the global state object, including:
  • the template element is appended to the end of the queue of the template element, and the number of operation steps of the template element is updated.
  • the present disclosure also provides an information processing system, including:
  • the client is used to send multiple item information to the server; each item information includes the occurrence period of the item and the corresponding scheduled task; the scheduled task is used to trigger the server to update the item list displayed on the terminal, A list of events that includes events that are currently occurring and/or are yet to occur information;
  • the server is configured to determine the next second scheduled task to be triggered before triggering the current first scheduled task to be triggered; and based on the sequence of the occurrence periods, and the first scheduled task and the second scheduled task The time interval between the triggering time points of the tasks.
  • determine the target scheduled task determine the target scheduled task, and update the items displayed on the terminal at the triggering time point of the target scheduled task. list;
  • the terminal is configured to refresh the currently displayed item list based on the item list sent by the server.
  • the present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When executed by the processor, the information processing method is implemented.
  • the present disclosure also provides a non-transitory computer-readable storage medium, which stores a computer program that causes a processor to execute the information processing method.
  • Figure 1 schematically provides an implementation environment diagram of an information processing method in this disclosure
  • Figure 2 schematically shows a step flow chart of an information processing method in an embodiment provided by the present disclosure
  • Figure 3 schematically shows a step flow chart of an information processing method provided by the present disclosure
  • Figure 4 schematically shows an item list template in a meeting reservation scenario provided by the present disclosure.
  • Figure 5 schematically illustrates a step of obtaining a drawn matter list template provided by the present disclosure. step flow chart
  • Figure 6 schematically shows a schematic diagram of calculating the position coordinates of each cell based on a table coordinate system provided by the present disclosure
  • Figure 7 schematically shows the overall flow chart of how to obtain a meeting list template in a meeting reservation scenario provided by the present disclosure
  • FIG. 8 schematically shows a framework diagram of the information processing system provided by the present disclosure.
  • the meeting reservation scenario Taking the display of a meeting reservation list of a physical conference room on a small flat panel display (hereinafter referred to as the meeting reservation scenario) as an example, the problems existing in the related technology are explained as follows:
  • the reservation information for the physical conference room can include the meeting time, host, participating departments, participants and other information.
  • One physical conference room may correspond to multiple reservation information.
  • the problem of conflicting meeting reservation time periods is that the time periods in the reservation information do not overlap with each other.
  • the meeting reservation information of a physical conference room will be displayed on the electronic door plate of the physical conference room.
  • the electronic door plate is a small display screen, and a meeting list is displayed on it.
  • the meeting list lists the physical meeting rooms.
  • Meeting reservation information Among them, corporate employees generally need to use electronic door tags to determine at what time there are meetings in the physical conference room, as well as unconvened meetings and ongoing meetings.
  • the meeting list on the electronic door plate needs to be updated in real time according to the reservation period corresponding to the meeting reservation information.
  • two scheduled tasks are bound to each meeting reservation information.
  • One is a scheduled task before the meeting, which is used to trigger the update of the meeting list at the moment before the meeting, and the other is a scheduled task during the meeting.
  • a scheduled task near the end time used to trigger the update of the meeting list when the meeting is about to end.
  • the present disclosure proposes a technical concept to solve the above problems, specifically: before each scheduled task is triggered, determine the next scheduled task to be triggered, and based on the order of the occurrence periods of the two scheduled tasks, and The time interval of the trigger time point (hereinafter referred to as the trigger time point interval) selects the target scheduled task to be triggered, thereby updating the event list on the terminal at the trigger time point of the target scheduled task.
  • the trigger time point interval selects the target scheduled task to be triggered, thereby updating the event list on the terminal at the trigger time point of the target scheduled task.
  • FIG. 1 an implementation environment diagram of the information processing method of the present disclosure is shown.
  • the server communicates with multiple terminals and multiple display devices; specifically, multiple terminals are connected to the server through the HTTP protocol, and multiple display devices communicate with the server through near-network protocols such as Bluetooth.
  • the display devices can communicate with the server through Bluetooth.
  • the gateway communicates with the server.
  • the terminal can communicate with the server through the router. When the terminal is scanned by the router, the router reports the basic information of the terminal to the server. When the display device is scanned by the Bluetooth gateway, the Bluetooth gateway reports the basic information of the display device to the server. information.
  • the basic information can include remaining power, logo, signal strength, etc.
  • the client is used to reserve a meeting and upload the reservation information obtained by the reservation to the server.
  • the server is used to generate a meeting list based on the reservation information, and when the scheduled task bound to the reservation information is triggered,
  • the conference list generated based on the corresponding reservation information is sent to the terminal.
  • the terminal can be the electronic door plate mentioned above, used to display the conference list sent by the server.
  • the server may need to initiate conference list update events to multiple terminals in a short period of time.
  • Such frequent and large number of update events in the network will cause network congestion, and the probability of errors in conference list update will greatly increase.
  • a large number of update events It can easily cause the thread to crash and cause the list update to fail.
  • Step S201 Receive multiple pieces of event information sent by the client. Each piece of event information includes the occurrence period of the event and the corresponding scheduled task.
  • the scheduled task is used to trigger the server to update the event list displayed on the terminal at the triggering time point, and the event list displays event information of events that are currently occurring and/or are to occur.
  • the client can be a Web client, and the user can log in to the client in a browser, enter the matter information of the matter to be reserved in the matter reservation interface provided by the client, and then upload the matter information to server.
  • each event information includes the occurrence period of the event.
  • the occurrence period refers to the period during which the event is carried out.
  • the scheduled task can be carried in the event information, or the scheduled task can be bound to the event information and separated from the event information. send.
  • the binding can be to associate the identifier of the specified time task with the identifier of the item information, as long as the association relationship between the item information and the scheduled task is determined.
  • the terminal is used to display a list of matters, and the list of matters includes matter information of matters that are currently occurring and/or are to occur.
  • the list of matters may include matters that are currently occurring, and the matters that are currently occurring refer to: Events that occur at the current time.
  • the list of items may include items to happen.
  • the items to happen refer to items whose occurrence period has not started after the current time.
  • the list of items may include items to happen and items that are currently happening.
  • the scheduled task corresponding to each item information will have its own trigger time.
  • the trigger time can be set according to the occurrence period.
  • the trigger time can be set in the occurrence period. Before, it can also be set at the end of the occurrence period, or it can be set in the occurrence period, or all of the above three situations. Specifically, it can be done according to user needs.
  • different item information is allowed to set different triggering time points of scheduled tasks. For example, the triggering time point of scheduled tasks for some item information is set at the end of the occurrence period, while the triggering time point of scheduled tasks for other item information is set at the end of the occurrence period. The point is set before the occurrence period.
  • one item information can also be allowed to correspond to one scheduled task or multiple scheduled tasks.
  • the scheduled task can be triggered at its own trigger time point.
  • the scheduled task When the scheduled task is triggered at the trigger time point, it means that the item information corresponding to the scheduled task needs to be displayed on the terminal, or the item list needs to be displayed on the terminal. Clear; thus, the server will respond to the trigger, determine the item information that currently needs to be displayed on the terminal, and then update the item list displayed on the terminal based on the item information that currently needs to be displayed on the terminal, so that the item list displayed on the terminal
  • the list of events includes only events that are happening, only events that are about to happen, or both events that are about to happen and things that are happening.
  • the matter information when applied to the application scenario of meeting reservation, may be the meeting reservation information, and the meeting reservation information includes the reservation period.
  • the reservation period is the occurrence period, which can be understood as the time period of the meeting.
  • the scheduled task can be used to trigger the server to update the conference list on the terminal to display the conference reservation information currently being carried out and to be carried out in the future.
  • the event information can be shift information.
  • the shift information includes departure time and arrival time. The period between departure time and arrival time is called the occurrence period, and scheduled tasks can be used to trigger
  • the server updates the flight information list (ie, the event list) displayed on the large screen to display the flight information that has not yet departed.
  • Step S202 Before triggering the current scheduled task to be triggered, determine the trigger time interval between the current scheduled task to be triggered and the next scheduled task to be triggered.
  • each scheduled task since each scheduled task has its own trigger time point, before each scheduled task is triggered at its corresponding trigger time point, the current scheduled task to be triggered and the next scheduled task to be triggered can be determined.
  • the trigger time interval between scheduled tasks since each scheduled task has its own trigger time point, before each scheduled task is triggered at its corresponding trigger time point, the current scheduled task to be triggered and the next scheduled task to be triggered can be determined.
  • the trigger time interval between scheduled tasks since each scheduled task has its own trigger time point, before each scheduled task is triggered at its corresponding trigger time point, the current scheduled task to be triggered and the next scheduled task to be triggered can be determined.
  • the trigger time interval between scheduled tasks since each scheduled task has its own trigger time point, before each scheduled task is triggered at its corresponding trigger time point, the current scheduled task to be triggered and the next scheduled task to be triggered can be determined. The trigger time interval between scheduled tasks.
  • Example # item information 1 corresponds to scheduled task 1, item information 2 corresponds to scheduled task 2, and item information 3 corresponds to scheduled task 3.
  • the trigger time point of scheduled task 1 is 12:55
  • the trigger time point of scheduled task 2 is 12 :50
  • the trigger time point of scheduled task 3 is 13:01
  • scheduled task 2 is triggered at 12:50, which is before the trigger time point of scheduled task 2, that is, before 12:50, for example, At 12:49, the next scheduled task to be triggered, namely scheduled task 1, can be determined. Then, the trigger time interval between the two adjacent triggered timing tasks can be determined.
  • the interval between triggering time points is small, for example, 1 minute apart, then when there is a large amount of transaction information in the server, multiple update events will be generated intensively. If the interval between triggering time points is large, for example, 10 minutes apart, then Generally, intensive multiple update events will not be generated.
  • the item information corresponding to the current scheduled task to be triggered and the item information corresponding to the next scheduled task to be triggered need to belong to the same project.
  • the current scheduled task to be triggered and the next scheduled task to be triggered need to belong to the same project.
  • the scheduled task to be triggered needs to correspond to a physical conference room.
  • the current scheduled task to be triggered and the next scheduled task to be triggered need to correspond to the same line, or the same route, or the same Waiting room.
  • Step S203 Based on the trigger time interval and the sequence of the occurrence periods, determine a target timing task from the current timing task to be triggered and the next timing task to be triggered, and determine the target timing task in the target timing task At the trigger time point, the list of items displayed on the terminal is updated.
  • the trigger time interval and the sequence of occurrence periods can be combined to determine which scheduled tasks to retain among the current scheduled tasks to be triggered and the next scheduled tasks to be triggered.
  • the retained scheduled tasks are called targets. Scheduled tasks.
  • the trigger time interval when the trigger time interval is small, you can choose to retain the current scheduled task to be triggered or the next scheduled task to be triggered.
  • the timing can be personalized Different triggering time points of tasks, so that the occurrence period of the event corresponding to the scheduled task with an earlier triggering time point is not necessarily earlier than the occurrence period of the event corresponding to the scheduled task with a later triggering time point. Therefore, when the interval between trigger time points is small, which scheduled tasks to retain can be determined based on the order of occurrence periods. For example, in some scenarios, scheduled tasks with a later occurrence period are retained, and in other scenarios, scheduled tasks with an earlier occurrence period are retained.
  • the server can update the list of items displayed on the terminal. As a result, no scheduled tasks will be triggered at 12:55, thus preventing intensive update events from breaking out.
  • the triggering of scheduled tasks one of them can be retained based on the trigger time interval between each two adjacent triggered scheduled tasks and the sequence between the corresponding occurrence periods.
  • the scheduled task is used as the target scheduled task, and at the trigger time of the target scheduled task, the list of items displayed on the terminal is updated.
  • the server by reducing the number of update events, thread crashes can be avoided and the success rate of updating the item list can be improved.
  • reducing update events in a short period of time can avoid network congestion, reduce update delays, and ensure update accuracy.
  • the process of determining the target scheduled task is shown:
  • the scheduled task with a later occurrence period can be selected as the target scheduled task, and when the interval between trigger time points is large, the currently to-be-triggered task The scheduled task and the next scheduled task to be triggered are both retained as target scheduled tasks.
  • the trigger time interval is greater than the first preset threshold, it is determined that the current scheduled task to be triggered and the next scheduled task to be triggered are both target scheduled tasks; if the time interval is not greater than the first preset threshold, threshold, then it is determined that among the current scheduled task to be triggered and the next scheduled task to be triggered, the one with a later occurrence period is the target scheduled task.
  • the first preset threshold can be determined according to the performance of the server and the network environment. For example, it can be determined as 10 minutes, or as a shorter 5 minutes.
  • the trigger time interval is greater than the first preset threshold, it indicates that the interval between update events sent by the server is longer and will not cause the occurrence of intensive update events. Therefore, both scheduled tasks can be retained as target scheduled tasks.
  • the interval between triggering points is not greater than the first preset threshold, it means that the interval between update events sent by the server is short, which will lead to the occurrence of intensive update events. Therefore, the later of the two scheduled tasks can be used as the target. Scheduled tasks. Among them, the target timing task with a later occurrence period can prompt the server to update the event information of the events to be happened to the terminal list, which can meet the requirements of conference planning, etc. User needs in appointment scenarios.
  • the case where the trigger time interval is not greater than the first preset threshold may include the case where the trigger time points of the two scheduled tasks are different, or may include the case where the trigger time points of the two scheduled tasks are the same. situation; when the trigger time point is the same, among the two scheduled tasks with the same trigger time point, the scheduled task corresponding to the event information that occurs later can be canceled.
  • Table 1 is the meeting list corresponding to the physical conference room 1.
  • the triggering times were: 12:55 and 13:55.
  • the triggering time points of the two scheduled tasks of meeting 2 are as follows: 13:50 and 14:50. Among them, the 13:50 scheduled task of meeting 2 is triggered first, and the next triggered is the 13:55 scheduled task of meeting 1.
  • the trigger time interval is small, and the meeting time corresponding to the 13:50 scheduled task (meeting 2 ) After the meeting time (meeting 1) corresponding to the 13:55 scheduled task, in this case, the 13:55 scheduled task will be automatically canceled, and the server will update the conference list at 13:50. When updating, the conference will not be issued directly.
  • the conference reservation information of Room 1 is uploaded to the terminal. After the update, the conference list displayed on the terminal includes the conference reservation information of Conference 2 to Conference 4.
  • Table 2 is the meeting list corresponding to the physical conference room 2.
  • the triggering time points of the two scheduled tasks of meeting 2 are: 13:55 and 14:55 respectively.
  • the scheduled task at 13:50 is about to be triggered, it can be determined that the scheduled task at 13:55 will be triggered next.
  • the trigger time points are very close to each other.
  • the meeting time (Meeting 2) corresponding to the 13:55 scheduled task is at 13: 50
  • the server will update the meeting list at 13:55, update
  • the conference list displayed on the rear terminal includes the conference reservation information of conference 2 to conference 4.
  • Table 3 is the list of meetings corresponding to the physical conference room 3.
  • the trigger time interval when determining the target scheduled task, can be In larger cases, it is determined whether the trigger time interval is sufficient for the occurrence of an event. If so, the terminal can be instructed to display idle time information within the interval to inform the user that events can be reserved during this period.
  • the interval length between the first occurrence period and the second occurrence period is determined; the first occurrence period is the period corresponding to the scheduled task currently to be triggered.
  • the second occurrence period is the occurrence period of the event corresponding to the next scheduled task to be triggered.
  • the matter idle information is sent to the terminal and/or the client; the matter idle information is used to indicate that between the first occurrence period and the second occurrence period Periods between occurrence periods can be reserved.
  • the event availability information can be added to the event list displayed on the terminal to display the time periods that can be reserved in the event list.
  • the item idle information can be added to the implementation list at a position between the item information corresponding to the current scheduled task to be triggered and the item information corresponding to the next scheduled task to be triggered.
  • the interval between triggering time points is large and greater than the second preset threshold, it means that there is a long interval between the occurrence periods of the events corresponding to the two scheduled tasks.
  • the duration of the interval between the first occurrence period of the event corresponding to the current scheduled task to be triggered and the second occurrence period of the event corresponding to the next scheduled task to be triggered can be determined.
  • the second preset threshold is greater than the first preset threshold.
  • the interval duration may refer to the interval time between the end moment of the first occurrence period and the start moment of the second occurrence period; when the first occurrence period occurs later, the interval duration may It may refer to the interval time between the end time of the second occurrence period and the start time of the first occurrence period.
  • the matter idle information can be sent to the terminal and/or the client, and the matter idle information can be generated based on the period between the first occurrence period and the second occurrence period.
  • the period between the first occurrence period and the second occurrence period may be called an idle period, and the event idle information is mainly used to represent that the idle period can be reserved.
  • the item availability information may also include a conference room identifier to identify which period of time in a certain physical conference room can be reserved for meetings.
  • the target interval length can be set according to actual needs, for example, set to a length greater than 30 minutes.
  • Table 4 is the meeting list corresponding to the physical conference room 4.
  • the next scheduled task is the 16:50 scheduled task at meeting 3.
  • Two scheduled tasks The trigger time interval is 1 hour and 50 minutes, which is large enough. Therefore, the interval between meeting 2 and meeting 3 can be further determined. It can be seen that the interval is 2 hours, which can be reserved for one or more meetings. Therefore, , can generate idle information for matters between 15:00-17:00, indicating that this period can be reserved. Specifically, you can insert a piece of idle information between meeting 2 and meeting 3 in Table 4, and mark "idle" in the meeting name column, so that in the meeting list on the terminal, "idle" will be displayed before meeting 3 .
  • the update process of the item list is shown:
  • updating the matter list includes: updating the matter list based on scheduled tasks, and updating the matter list based on modified matter information or newly added matter information.
  • the process of updating the item list based on scheduled tasks is as follows:
  • the event list may be generated by the server based on the event information of the currently pending events.
  • the event information of the currently pending events may be determined based on the triggering of the corresponding scheduled tasks, that is, it may include the event information corresponding to the triggered scheduled tasks. Information corresponding to the scheduled task to be triggered.
  • the matter list template sent by the client can be received; and the matter list can be generated based on the matter list template and matter information of matters that are currently occurring and/or are to occur.
  • the item list template can be prepared by the client and then uploaded to the server.
  • the details of the item list template can be made as described in the embodiments on the client side later, and will not be described in detail here.
  • the event list template can stipulate that event information of events that are currently occurring and/or are yet to occur be displayed in the form of a list.
  • the matter list template can be understood as a table type template, including rows and columns, in which the name of the table as the header, for example, the first row of the table can be preset, and each item The item information is used as the body content in the form.
  • the item list template can be understood as a table that does not contain meeting reservation information in the table itself.
  • the event information of events that are currently occurring and/or are to occur can be displayed in the event list as required. Therefore, when updating the event list displayed on the terminal, the event information corresponding to the currently triggered scheduled task can be added.
  • the matter list template taking specific example 1 as an example, the matter information of meeting 2 can be added to the matter list template at 13:50.
  • the event information of meeting 3 and meeting 4 can be added to the event list at 13:50. template.
  • the meeting can be scheduled at 13:50 2.
  • the item information of Meeting 3 and Meeting 4 is added to the item list template.
  • the process of updating the display list on the terminal is shown.
  • the first item information corresponding to the target scheduled task can be obtained at the triggering time of the target scheduled task.
  • the second matter information generate a new matter list based on the first matter information and the second matter information; and send the new matter list to the terminal to update the matter list displayed on the terminal.
  • the occurrence period of the second event information is located after the occurrence period of the event corresponding to the target timing task.
  • the first item information can be understood as information about items that are about to happen
  • the second item information can be understood as information about items that are about to happen, where the first item information and the second item information can be arranged line by line.
  • the first matter information and the second matter information can be added to the matter list in the order of occurrence periods, thereby obtaining a new matter list, and sending the new matter list
  • the terminal after receiving the new item list, the terminal can refresh the displayed item list, thereby realizing the update of the display list on the terminal.
  • the current status of each item information may be included in the item list.
  • the status of each item information in the item list to be displayed may be updated together.
  • the status of the first item information and the status of the second item information may be updated, and a new item list may be generated based on the first item information and the second item information and their respective updated states. list of matters. Among them, the status includes the occurring status and the not-occurring status.
  • the status of the first event information can be determined according to the occurrence period of the event corresponding to the target scheduled task. If the occurrence period is after the current time and very close to the current time, it means that the event is about to happen, so its status can never have happened. The status is changed to the occurring status, and the status of the second event information can remain as the non-occurring status.
  • the status of each matter information can be identified in the list.
  • a new column can be added to identify the status of each conference.
  • the status of the conference can include the starting status and the pending status.
  • the status of each item information in the item list can be updated and identified to help the user obtain which items are happening and which items are waiting to happen, thereby optimizing the user experience.
  • the process of updating the matter list based on the modified matter information or the newly added matter information is as follows:
  • a corresponding updated item list is generated based on the updated first item information and the item list currently displayed on the terminal; and the updated item list is Sent to the terminal so that the terminal refreshes the displayed item list.
  • the item list displayed on the terminal can be updated in real time based on the updated third item information.
  • an updated matter list can be generated based on the updated third matter information and each matter information in the matter list currently displayed on the terminal, and the updated matter list can be sent to the terminal.
  • the terminal receives the new matter list.
  • the displayed item list can be refreshed, thereby realizing real-time updating of the display list on the terminal.
  • the update of the event information may include the update of the occurrence period and the update of other attributes.
  • the update of the reserved conference room may include the update of the reserved conference room.
  • the trigger time point of the corresponding scheduled task can also be updated.
  • the triggering time point of the timing task corresponding to the fourth item information can be updated based on the updated occurrence period.
  • a new trigger time point can be obtained based on the updated occurrence period and the trigger time point setting strategy of the fourth item information, and then the scheduled task of the fourth item information can be triggered at the new trigger time point.
  • the item list will be updated, and when the occurrence period is updated, the scheduled task corresponding to the item information can also be updated. Trigger time point to ensure the accuracy of the list of items displayed on the terminal.
  • multiple terminals may include ticket type terminals and electronic table card type display devices; wherein, the ticket type terminal is used to display information of the entire conference room. Conference list, and the electronic table card type display device is used to display the conference reservation information of the currently ongoing conference.
  • the server can also update the matter information displayed on the electronic table card type display device, so that the electronic table card type display device displays ongoing matters. Matter information.
  • the event information corresponding to the target scheduled task can be sent to multiple display devices, so that the display device refreshes the displayed event information.
  • the occurrence period of the event corresponding to the target scheduled task may mean: in the occurrence period of the event corresponding to the target scheduled task, specifically it may be the start time of the occurrence period, or any time after the start time, to the display
  • the device sends the event information corresponding to the target scheduled task.
  • the display device receives the event information sent by the server, it can refresh the displayed event information.
  • the implementation environment shown in Figure 1 such as MAC address, remaining battery, signal strength, etc.
  • the server stores this information in the database and displays it on the Web page. Users can choose to reserve a meeting in a certain conference room and a certain time period through the Web page (the minimum meeting duration is thirty minutes). After the meeting reservation is successful, the meeting reservation information is transmitted to the server.
  • the event information corresponding to the target scheduled task can be sent to the display device after a preset time period after the start time of the occurrence period of the event corresponding to the target scheduled task. This is because the event can be sent after a period of time after the trigger time point. information to avoid triggering time points, thereby preventing the event of sending update item information from being sent very close to the event of updating the item list, thereby further reducing network congestion.
  • the user of the client can decide whether to bind it based on various information of the terminal (such as power, signal strength, etc.).
  • the meaning of the binding operation is: the bound terminal and display device can be used by the conference system. Meeting reservation information will be issued and the meeting list will be updated.
  • the matter list on the terminal with better current performance can be updated.
  • current performance parameters sent by multiple terminals are received.
  • the current performance parameters include at least one of remaining power and signal strength.
  • the list of items currently displayed on the target terminal can be updated; wherein, the target terminal's The current performance parameters are greater than or equal to the target performance parameters.
  • the target terminal may be a terminal with a remaining power greater than the target remaining power, or the target terminal may be a terminal with a signal strength greater than the target signal strength, or the target terminal may have a remaining power greater than the target remaining power, and the signal strength is greater than Target signal strength for the terminal.
  • the solution based on the current performance parameters is also applicable to updating the event information on the display device.
  • the display devices whose current performance parameters are greater than or equal to the target performance parameters in multiple display devices can be The device sends the event information corresponding to the target scheduled task to refresh the displayed event information.
  • the display device is an electronic table sign.
  • the display device is an electronic table sign.
  • the number of electronic table signs is more than the number of electronic door signs. Therefore, when choosing to update the one with high signal strength and large remaining power, When sending the event information of the electronic table card, the update events of sending the event information can be reduced, thereby further reducing the occupation of network bandwidth by the information.
  • the number of update events sent by the server to the terminal can be reduced, thereby further avoiding network congestion and improving the accuracy of the item list for the target terminal.
  • the router After the terminal is scanned by the router through the protocol, the router reports the basic information of the terminal to the server. After the display device is scanned by the Bluetooth gateway through the Bluetooth protocol, the Bluetooth gateway reports the basic information of the display device to the server.
  • the basic information includes MAC address and battery level. , signal strength, etc.
  • the server stores the basic information of each terminal and display device in the database and displays it through the Web page.
  • Client users can decide whether to bind them based on the basic information of the terminal and display device.
  • the bound terminal can be issued a conference list by the server, and the bound display device can be issued conference reservation information by the server. .
  • S3 The client user reserves a meeting in the conference room and binds some terminals to display the conference list and conference reservation information in this conference room.
  • the electronic door plate displays the conference list and the electronic table plate displays the conference reservation information.
  • the server receives the conference reservation information sent by the client, and generates a scheduled task corresponding to the conference reservation information based on the occurrence period of the conference reservation information and the preset trigger time setting strategy.
  • a meeting reservation information includes two scheduled tasks, namely the scheduled task before the start of the meeting and the scheduled task when the meeting is about to end.
  • Each meeting reservation information and the corresponding scheduled task are stored in the database waiting to be triggered.
  • step S5 Before each scheduled task to be triggered is triggered, determine the trigger time interval between the scheduled task and the next scheduled task to be triggered. If the trigger time interval is greater than 5 minutes, execute step S6; otherwise, execute step S7.
  • S6 Reserve the scheduled task corresponding to the meeting reservation information that occurs later in the two scheduled tasks, cancel the other scheduled task, and send the reserved scheduled task to the terminal at the trigger time of the reserved scheduled task.
  • the conference list generated by the conference reservation information corresponding to the task and the conference reservation information to be occurred. After receiving the conference list, the terminal refreshes the displayed conference list.
  • the conference reservation information corresponding to the reserved scheduled task is sent to the bound display device, which may specifically include participants, moderators, and Conference topics and other information.
  • S7 Reserve the two scheduled tasks.
  • a conference list is generated based on the conference reservation information corresponding to the triggered scheduled task and the conference reservation information to be occurred.
  • the terminal receives the conference list. Afterwards, refresh the displayed meeting list.
  • step S8 is executed; otherwise, step S9 is executed.
  • S8 The client sends event idle information, and sends an event list containing the event idle information to the terminal to indicate that the time period between the two conferences can be reserved.
  • the above-mentioned item list and item information can be encapsulated by the server through the HTTP protocol and then delivered to the terminal.
  • the time interval of the interval can be actively displayed in the terminal's event list, thereby enriching the update mechanism of the event list, making Users can directly check the time slots that can be reserved from the list of items displayed on the terminal, which optimizes the user experience.
  • the event information of the ongoing events can be displayed on the display device. This can realize the display of event information in two dimensions, enrich the information display scenario, and optimize user experience.
  • the trigger time point of the corresponding scheduled task can be updated, thereby ensuring the accuracy of updating the terminal's event list.
  • the inventor conceived and proposed an improvement of the client.
  • the matter information and the scheduled tasks corresponding to the matter information can be provided to the server, so that the server can be based on the triggering time and timing of the scheduled tasks.
  • the triggering of a scheduled task can avoid intensive update events in a short period of time, avoid network congestion and thread crashes, thereby improving the update accuracy and update success rate of the list of items displayed on the terminal.
  • an information processing method in an embodiment of the present disclosure is introduced. This method can be applied to the client side.
  • a step flow chart of an information processing method in an embodiment is shown. As shown in Figure 3, it may specifically include the following steps:
  • Step S301 In response to the event entry on the event reservation interface, obtain the entered event information.
  • the event information includes the occurrence period of the event and the corresponding scheduled task; the scheduled task is used to trigger the server to update the event list displayed on the terminal at the trigger time point, and the event list includes events that are currently occurring and/or are to occur. Information about the matter.
  • Step S302 Send the matter information to the server, so that the server determines the trigger time interval between the current scheduled task to be triggered and the next scheduled task to be triggered before triggering the current scheduled task to be triggered. ; And based on the trigger time interval and the sequence of the occurrence periods, determine the target timing task from the current timing task to be triggered and the next timing task to be triggered, and determine the target timing task at the end of the target timing task At the triggering point, the list of items displayed on the terminal is updated.
  • the matter reservation interface can be understood as a Web page provided by the client for users to reserve matters.
  • the matter reservation interface can include basic information reported by the terminal to the server, and the user can On the reservation interface, select the terminal to display the item list and enter the item information.
  • the trigger time point of the scheduled task when entering the matter information, can be set at the same time.
  • the client can generate a scheduled task corresponding to the matter information.
  • you can also set the trigger time setting policy for the scheduled task for example, set it five minutes before the occurrence period and/or set it five minutes before the end of the occurrence period.
  • several different trigger time point setting strategies can be provided for users to choose from in the matter reservation interface. In this case, the server can generate corresponding scheduled tasks based on the matter information and trigger time point setting strategies.
  • the matter list is generated based on the matter information of the matters that are happening and/or to happen, and the matter list template, where the client side can provide the matter list.
  • To-do list template is generated based on the matter information of the matters that are happening and/or to happen.
  • the client side before uploading the matter information, can obtain the drawn matter list template in response to the drawing completion operation of the matter list template on the template setting interface; upload the matter list template to the server, so that the server can draw the matter list template based on the matter
  • the list template and the event information of the events that are happening and/or to be happened generate the event list.
  • the item list template is a template that contains a table.
  • the template includes a table header and a table body, which is composed of rows and columns. It also includes other information, such as attribute information of the conference room.
  • the item list template is generally drawn in the drawing interface provided by Canvas.
  • Canvas is a method provided by HTML5 to use scripts to draw graphics on web pages.
  • the native Canvas has some shortcomings, such as the lack of interactive object models and graphics. Combination, drag and zoom of objects, etc.
  • drawing the task list template only one cell can be drawn. That is, the user needs to draw multiple cells separately and then combine the multiple cells.
  • the table can only be formed after the process. This method takes a long time, resulting in low efficiency in drawing the item list template.
  • the inventor conceived a technical solution to solve the above technical problems, he regarded the table graphics as a combination of multiple cells, and the cells as a combination of rectangles and text. Based on this idea, he customized a drawing matter List template methods.
  • the specific implementation goal is: a table graphic can be drawn in batches at one time in the canvas, and each cell in the table can be individually configured with text style.
  • this implementation is adopted, the user only needs to set the table attribute parameters to generate multiple cells in batches to obtain a table.
  • SVG is a language that uses XML to describe 2D graphics. Its biggest advantages over Canvas are: first, each drawn graphic is regarded as an object, and related event handlers can be added to it; second, , the graphic quality of SVG images will not be lost when they are enlarged or resized.
  • FIG. 5 a flow chart of steps for obtaining a drawn item list template is shown. As shown in Figure 5, it may specifically include the following steps:
  • Step S501 Generate a table in response to the table attribute parameters entered in the table configuration item.
  • the table attribute parameters include at least one of table size, number of rows and number of columns.
  • the table configuration item can be used to receive the table attribute parameters input by the user.
  • the table configuration item can include the height parameter and width parameter of the table. Then, according to the table coordinate system, it can be calculated under the table attribute parameters, as follows: How many cells are there, and the coordinate value of each cell is calculated, thereby cyclically generating multiple cells based on the coordinate value of each cell, and then obtaining a table.
  • step S501 when implementing step S501, the following process may be adopted:
  • the table attribute parameters include the table size, the number of rows, and the number of columns.
  • the table size includes the length and width of the table.
  • the table coordinate system can be based on the display coordinate system of the display screen, the number of rows, and the number of columns. It can be used to determine the number of cells under the table size, and then determine the coordinates of each cell based on the display coordinate system. Referring to FIG. 6 , a schematic diagram for calculating the position coordinates of each cell based on a table coordinate system is shown.
  • the table width is width
  • the height is height
  • the number of table columns is n
  • the cell width is tw
  • the cell height is th
  • index is the i-th column
  • rowIndex is the i-th row.
  • the maximum number of display rows of the item list template is calculated dynamically.
  • the height of the entire canvas is taken, and the number of rows is calculated based on the row height.
  • the position of each cell in the table coordinate system that is, the length and width of each cell, can be obtained, and the corresponding cells can be generated in a loop at each corresponding position, thereby obtaining the table.
  • Step S502 Receive the text input to the cell as the header in the table configuration item, and the header text attribute of the text.
  • the header text attributes include one or more attributes such as font size, color, and position of the text.
  • the header text attribute can be entered or selected in the table configuration item. For details, you can refer to the similar implementation process of selecting font styles in related technologies.
  • the configured text For the cells of the header, the configured text can be entered.
  • Step S503 Based on the header text attribute, add the corresponding text to the unit as the header grid to get the item list template.
  • the corresponding text in the generated table, can be added to the cell of the header according to the header text attribute, thereby obtaining an item list template as shown in Figure 4.
  • a step flow chart of drawing an item list template is also proposed.
  • a process of setting text attributes in the table body may also be included.
  • the table configuration item may be received.
  • the table body text attribute may also include one or more attributes such as the font size, color, and position of the text.
  • the table body text attribute is used to specify the text style configured in the cells of the table body. Since the text in the cells of the table body is added by the server later based on the event information, the text attribute of the table body can be carried in the event list template and bound to the corresponding cells.
  • the position attribute can indicate whether the text is centered, left, right, top, or bottom in the cell. Therefore, in an optional example, the position coordinates of the text in each cell can also be determined based on the position attribute.
  • the position coordinates of the cell can be used as the criterion. Based on the position attribute of the cell, the position of the text in the cell can be calculated. Position coordinates, which are used as a parameter of the cell.
  • the item list template can be exported as JSON (JavaScript Object Notation, JS object notation) type data and then uploaded to the server. Therefore, the server can add each item information to the corresponding location of the JSON type data when generating the item list, thereby obtaining the JSON type data to be rendered, and then send the JSON type data to be rendered to the server, and in the terminal
  • a list of items can be rendered based on the JSON type data to be rendered.
  • FIG. 7 there is an overall flow diagram showing how to obtain a meeting list template (corresponding matter list template) in a meeting reservation scenario.
  • the specific process may include the following:
  • the Canvas-based drawing interface when drawing an item list template in the drawing interface provided by Canvas, the Canvas-based drawing interface does not have high support for undo/restore.
  • the inventor ported the fabric.js open source library to the Canvas-based drawing library to utilize its export and import methods of content on the canvas to implement the "undo/revert" function.
  • the overall implementation idea is as follows: first, maintain an undo recovery data set and a pointer indicating the current index; when the data on the canvas and the editing area in the canvas are modified, export its data content, and when the undo recovery operation is performed, it can Detect changes in the data object and import the data to restore the content on the canvas.
  • the template elements generated under the drawing operation can be recorded, and in response to the triggered Undo/redo operation: render the target template element corresponding to the undo/redo operation among the recorded template elements to the drawing canvas.
  • one template element represents a modified item list template
  • drawing operations include but are not limited to any of the following: drawing operations on graphics in the item list template and editing operations of table attribute parameters.
  • each drawing operation can be understood as a data modification operation, which includes a drawing operation of graphics on the canvas and an editing operation of text in the editing area.
  • the editing operation of table attribute parameters may include: table configuration The modification operation of the table attribute parameters in the item, the modification operation of the table header text attribute and the table body text attribute, and the modification operation of the table header text.
  • graphic The drawing operation may refer to: drawing of the cell component, such as selection operation of the style of the cell component, scaling operation of the cell component, etc.
  • the content on the canvas when the drawing operation is completed can be exported as a template element.
  • This template element can be roughly understood as an unfinished item list template, that is, as long as the user does not click to upload the item list template, each previous drawing
  • Each operation corresponds to a version of the item list template, and each version of the item list template is called a template element.
  • a drawing operation is: modify the height of the table from 220mm (millimeters) to 210mm in the table attribute parameters.
  • the exported data content can be an item list template.
  • the height of the item list template is 210mm
  • the height of the table in the template element exported before modification is 210mm.
  • the corresponding target template element can be selected from multiple stored template elements and rendered to the drawing canvas.
  • the undo in undo/restore can mean that the user wants to restore the data state before modification, and the restore can mean that after the user returns to the data state of a certain modification, he wants to restore the data state of the next modification. .
  • the cancellation can be It means that the user wants to restore to the state of the nth modification when the user makes the n+2nd modification. Restoration can mean: when the user returns to the state of the nth modification, he wants to restore to the n+1st modification or the nth modification. +2 modified status. It can also be seen that the recovery operation is performed on the basis of the undo operation.
  • the target template element when rendering the target template element corresponding to the undo/redo operation among the recorded template elements to the drawing canvas, the target template element can be determined based on the operation step size. Specifically, the operation step of the undo/restore operation can be determined; based on the operation step, the target template element corresponding to the operation step is searched starting from the last recorded template element, and the target template element is rendered to the drawing canvas; where , the operation step size includes a step size of undo type and a step size of undo type.
  • the operation step size may include a undo type step size and a recovery type step size, where the undo type step size is aimed at the undo operation, It can also be understood as the step size of the backward type.
  • the step size of the recovery type is aimed at the recovery operation, and it can also be understood as the step size of the forward type.
  • the target template element corresponding to the undo operation and the last recorded template element can be determined based on the operation step of the restore operation, such as clicking on the forward type undo control.
  • the number of times determines the final target template element.
  • a global state object can be maintained, thereby saving template elements into the global state object.
  • a global state object corresponding to the drawing canvas can be created; and each time a template element is recorded, the template element and the number of operation steps corresponding to the template element are recorded into the global state object; the number of operation steps represents The drawing operation corresponding to this template element.
  • the template element whose operation step number corresponds to the operation step can be found from the global state object based on the operation step.
  • the global state object includes the array StepArr used to record template elements; and the Current that records the number of operation steps.
  • the number of operation steps can represent how many drawing operations the template element is obtained and is used to represent the total number of drawing operations;
  • the CanvasData used to record the data on the current drawing canvas which refers to the page data to be updated and is a string in JSON format; each time the undo/restore operation is performed , the corresponding template element will be taken out from the StepArr array and the data object will be updated.
  • the template element corresponding to the drawing operation can be recorded into the array of the global state object.
  • each template element in the global state object can be arranged in the order of operation steps. In this way, in order to improve the accuracy of finding the target template element from the array, in each undo/restore operation, When the target template element is determined, if the target template element is not the last template element recorded, the template elements after the target template element are deleted. Correspondingly, each time a template element is recorded, the template element and the number of operation steps corresponding to the template element can be recorded. In the process of recording into the global state object, the template element can be appended to the end of the queue of the template element and the number of operation steps of the template element can be updated.
  • the user changes the height of the table from 220mm to 210mm.
  • it is modified from 210mm to 200mm.
  • the height is modified from 210mm to 215mm.
  • Undo the operation Indicates that when the n+2nd modification is made, the state of the nth modification is restored, and when save is clicked (indicating that the n+1st modification and the n+2nd modification are not wanted), the nth modification is deleted from the global state object. +1st modification and n+2nd modification.
  • the height of the table is modified to 208mm, and then the data after the n+3rd modification is added to the data after the nth modification.
  • the number of operation steps of the drawing operation in the global state object is modified from the n+3th time to the n+1th time.
  • the undo operation step size is 1, and in the global state object from the last A template element counts forward by 1, that is, the data corresponding to the nth operation step is obtained, that is, the height of the table is 210mm.
  • Update can ensure that the operation steps of subsequent undo/restore operations correctly correspond to the operation steps of each template element maintained in the global state object, and improve the accuracy of the found target template elements.
  • the top template elements can be deleted.
  • the first element needs to be deleted in order, that is, according to the first-in, first-out principle. , delete the template element in the global state object.
  • the item list template can be exported as object-numbered JSON type data and then uploaded to the server.
  • the corresponding template elements can be snapshotted.
  • the corresponding snapshot can be extracted, and then the template elements can be restored based on the snapshot.
  • the current content on the drawing canvas can be exported as data in JSON format; and the exported data in JSON format can be snapshotted as a record. template element.
  • the JSON format data of the corresponding target template element can be imported to the drawing canvas, so that the item list template corresponding to the template element can be displayed on the drawing canvas.
  • a set of template elements for undo and recovery and a pointer indicating the number of current operation steps can be maintained to help locate the corresponding template element; for each drawing operation, you can Export the content on the drawing canvas as data in JSON format; when performing an undo/redo operation, import the corresponding JSON format data to restore the content on the canvas. Since the JSON format data is used as a snapshot, the content on the drawing canvas can be restored. , therefore, the convenience of undo/restore can be improved.
  • FIG. 8 a schematic framework diagram of the information processing system is shown. As shown in Figure 8, it includes:
  • the client is used to send multiple item information to the server; each item information includes the occurrence period of the item and the corresponding scheduled task; the scheduled task is used to trigger the server to update the item list displayed on the terminal,
  • the event list includes event information about events that are currently occurring and/or are to occur;
  • the server is configured to determine the next second scheduled task to be triggered before triggering the current first scheduled task to be triggered; and based on the sequence of the occurrence periods, and the first scheduled task and the second scheduled task The time interval between the triggering time points of the tasks.
  • determine the target scheduled task determine the target scheduled task, and update the items displayed on the terminal at the triggering time point of the target scheduled task. list;
  • the terminal is configured to refresh the currently displayed item list based on the item list sent by the server.
  • the server can be used to execute the information processing method described in the above server-side embodiment
  • the client can be used to execute the information processing method described in the above client-side embodiment.
  • It may include multiple terminals and multiple display devices.
  • the display device may be an electronic table sign
  • the terminal may be an electronic house sign. Of course, it may also include other types of terminals, such as large-size display screens.
  • Step 1 Template design
  • the user logs in to the client and uses the Canvas-based drawing library provided by the client to design the item list template.
  • the Canvas drawing library uses the fabric.js open source library.
  • Step 2 The template design user selects the meeting list component on the template setting interface, selects a cell component of a style and drags it to the drawing canvas, and then enters the table attribute parameters, header text, and header text attributes in the configuration bar. And the table body text attribute;
  • Step 3 The client responds to the user's dragging and moving operation of the cell component on the drawing canvas, based on the user's selected cell component, table attribute parameters, header text, header text attribute and table body text attribute, Generate multiple cells in batches to get a table.
  • the client will record each step of the user's drawing operation, and snapshot the template elements under each step of drawing.
  • the saved Determine the target snapshot from the snapshot, and then import the target snapshot to the drawing canvas to facilitate the user to edit the involved meeting list template.
  • Step 4 In response to the user's confirmation operation, the client exports the data on the current drawing canvas into list data in JSON format, and then uploads it to the server.
  • the list data in JSON format is the meeting list template.
  • the template design user can draw a variety of different styles of meeting list templates based on the process from the first to the fourth step for the meeting reservation user to select and use.
  • the conference reservation user logs in to the client, enters the conference reservation interface, enters the conference reservation information, selects the trigger time point setting strategy, and selects a conference list template among the several drawn conference list templates provided; the client will The entered meeting reservation information, selected trigger time point setting policy, and meeting list template are sent to the server.
  • the server In the sixth step, the server generates a scheduled task for the conference reservation information based on the conference reservation information and the selected trigger time point setting policy, thereby determining the trigger time point of the scheduled task.
  • Step 7 The server updates the conference list displayed on the terminal based on the triggering time of the scheduled task.
  • the specific process can be seen in the above exemplary description on the server side, and will not be described again here.
  • This embodiment also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes, the information processing method is implemented.
  • the present disclosure also provides a non-transitory computer-readable storage medium, which stores a computer program that causes a processor to execute the information processing method.
  • this application proposes an information processing device applied on the server side.
  • the device includes the following modules:
  • the information receiving module is used to receive multiple pieces of event information sent by the client.
  • Each item information includes the occurrence period of the event and the corresponding scheduled task; the scheduled task is used to trigger the server to update the information displayed on the terminal at the trigger time point.
  • a list of matters which includes information on matters that are currently occurring and/or are yet to occur;
  • the timing trigger module is used to determine the trigger time interval between the current timing task to be triggered and the next timing task to be triggered before triggering the current timing task to be triggered;
  • a list update module configured to determine a target timing task from the current timing task to be triggered and the next timing task to be triggered based on the trigger time interval and the sequence of the occurrence periods, and determine the target timing task in the At the triggering point of the target scheduled task, the list of items displayed on the terminal is updated.
  • list update modules include:
  • a first determination unit configured to determine that the current scheduled task to be triggered and the next scheduled task to be triggered are both the target scheduled tasks if the trigger time interval is greater than a first preset threshold
  • a second determination unit configured to determine, if the trigger time interval is not greater than the first preset threshold, that the occurrence period is later among the current scheduled task to be triggered and the next scheduled task to be triggered. of scheduled tasks for the stated goal.
  • the device also includes:
  • An interval length determination module configured to determine the interval length between the first occurrence period and the second occurrence period if the trigger time interval is greater than or equal to the second preset threshold; the first occurrence period is the current The occurrence period of the event corresponding to the scheduled task to be triggered, and the second occurrence period is the occurrence period of the event corresponding to the next scheduled task to be triggered;
  • An idle information generation module configured to generate event idle information based on the first occurrence period and the second occurrence period when the interval duration is greater than or equal to the target interval duration;
  • the event idle information is used to indicate that the period between the first occurrence period and the second occurrence period can be reserved;
  • the idle information sending module is configured to add the item idle information to the item list displayed on the terminal, so as to display the time period that can be reserved in the item list.
  • the event list is generated based on the event list template and the event information of the events that are occurring and/or are to occur.
  • the list update module includes:
  • An information acquisition unit configured to acquire the first event information corresponding to the target scheduled task and the second event information at the triggering time point of the target scheduled task, wherein the occurrence period of the second event information is located in the After the occurrence period of the event information corresponding to the target scheduled task;
  • a status update unit configured to update the status of the first item information and the status of the second item information, wherein the status includes an ongoing state and a non-occurring state;
  • a list generating unit configured to generate a new matter list based on the first matter information and the second matter information, and their respective updated states
  • a list sending unit is configured to send the new item list to the terminal to update the item list displayed on the terminal.
  • the device also includes:
  • An information update detection module configured to, when detecting that any third item information among the plurality of item information is updated, generate a corresponding item based on the updated third item information and the item list currently displayed on the terminal. Updated matter list;
  • An information update sending module is configured to send the updated item list to the terminal, so that the terminal refreshes the displayed item list.
  • the triggering time point of the scheduled task corresponding to each item of information is determined based on the occurrence period of the item of information; the device further includes:
  • the trigger time point update module is configured to, when it is detected that the occurrence period of any fourth item information in the plurality of item information is updated, based on the updated occurrence period, update the scheduled task corresponding to the fourth item information according to the updated occurrence period. Updated at the trigger time.
  • the device further includes:
  • a performance parameter acquisition module configured to receive current performance parameters sent by multiple terminals respectively, where the current performance parameters include but are not limited to at least one of remaining power and signal strength;
  • the list update module is specifically configured to update the list of items displayed on the target terminal at the trigger time of the target scheduled task; wherein the current performance parameter of the target terminal is greater than or equal to the target performance parameter.
  • this application proposes an information processing device applied to the client side.
  • the device includes the following modules:
  • the event information receiving module is used to obtain the entered event information in response to the event entry on the event reservation interface; wherein the event information includes the occurrence period of the event and the corresponding scheduled task; the scheduled task is used to trigger The time point triggers the server to update the event list displayed on the terminal, and the event list includes event information of events that are currently occurring and/or are to occur;
  • An information sending module configured to send the event information to the server, so that the server determines the trigger between the current scheduled task to be triggered and the next scheduled task to be triggered before triggering the current scheduled task to be triggered. time point interval; and based on the trigger time point interval and the sequence of the occurrence periods, determine the target timing task from the current timing task to be triggered and the next timing task to be triggered, and determine the target timing task in the target When the scheduled task is triggered, the list of items displayed on the terminal is updated.
  • the device also includes:
  • the item list acquisition module is used to obtain the drawn item list template in response to the drawing completion operation of the item list template performed on the template setting interface;
  • An export module configured to export the matter list template into object-notation JSON type data and then upload it to the server, so that the server can base it on the matter list template and the matters that are happening and/or are about to happen.
  • the item information is generated to generate the item list.
  • the template setting interface includes table configuration items
  • the item list acquisition module includes:
  • a table generation unit configured to generate a table in response to table attribute parameters input in the table configuration item, where the table attribute parameters include at least one of table size, number of rows, and number of columns;
  • a first text attribute acquisition unit configured to receive the text input to the cell as the header in the table configuration item, and the header text attribute of the text
  • a template generation unit configured to add corresponding text to the header text attribute based on the header text attribute. As the header cell, the item list template is obtained.
  • the device also includes:
  • the second text attribute acquisition unit is used to receive the table body text attribute input to the non-header cell in the table configuration item;
  • the template generation unit is specifically configured to add corresponding text to the cell as the header based on the header text attribute, and bind the table body text attribute to the corresponding cell, to obtain The to-do list template.
  • the table generating unit includes:
  • the coordinate system acquisition subunit is used to acquire the table coordinate system of the display screen to be displayed in response to the table attribute parameters input in the table configuration item;
  • a position coordinate determination subunit used to determine the position coordinates of each cell in the table coordinate system based on the table attribute parameters and the table coordinate system;
  • a table generation subunit is used to generate the table based on the position coordinates of each cell in the table coordinate system.
  • the template setting interface includes a drawing canvas
  • the device further includes:
  • the data recording module is used to record the template elements generated under the drawing operation for each drawing operation that occurs on the template setting interface.
  • One template element represents a modified item list template;
  • the drawing operations include but are not limited to Any of the following: drawing operations on graphics in the item list template and editing operations on table attribute parameters;
  • a data recovery module configured to respond to the triggered undo/restore operation and render the target template element corresponding to the undo/restore operation among the recorded template elements to the drawing canvas.
  • the data recording module includes:
  • An export unit configured to export the current content on the drawing canvas into data in JSON format for each drawing operation that occurs on the template setting interface
  • the snapshot unit is used to snapshot the exported data in JSON format as the template element of the record.
  • the data recovery module includes:
  • An operation step determination unit used to determine the operation step of the undo/restore operation
  • An element search unit configured to search for a target template element corresponding to the operation step starting from the last recorded template element based on the operation step, and render the target template element to the The drawing canvas; wherein, the operation step size includes an undo type step size and a recovery type step size.
  • the device also includes:
  • An object creation module used to create a global state object corresponding to the drawing canvas
  • a recording module configured to record the template element and the number of operation steps corresponding to the template element into the global state object each time one of the template elements is recorded; the number of operation steps is used to indicate the number of operation steps corresponding to the template element. drawing operations;
  • the element search unit is specifically configured to search for a template element whose operation step number corresponds to the operation step from the global state object based on the operation step.
  • the device further includes:
  • a deletion module configured to delete the template elements after the target template element if the target template element is not the last template element recorded; and/or the number of template elements in the global state object When the target number is exceeded, delete the template elements ranked first;
  • the recording module is specifically configured to append the template element to the end of the queue of the template element each time a template element is recorded, and update the number of operation steps of the template element.
  • the specific implementation process of the information processing device embodiment is similar to that of the information processing method embodiment. It is sufficient to refer to the process of the above information processing method embodiment and will not be described again here.
  • any reference signs placed between parentheses shall not be construed as limiting the claim.
  • the word “comprising” does not exclude the presence of elements or steps not listed in a claim.
  • the word “a” or “an” preceding an element does not exclude the presence of a plurality of such elements.
  • the present disclosure may be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the element claim enumerating several means, several of these means may be embodied by the same item of hardware.
  • the use of the words first, second, third, etc. does not indicate any order. These words can be interpreted as names.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开涉及一种信息处理方法、信息处理系统、电子设备及存储介质，所述信息处理方法应用于服务器，所述方法包括：接收客户端发送的多条事项信息，每条事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发所述服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。

Description

信息处理方法、信息处理系统、电子设备及存储介质
本申请要求在2022年6月21日提交中国专利局、申请号为202210708156.X、发明名称为“信息处理方法、信息处理系统、电子设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及显示技术领域，特别是涉及一种信息处理方法、信息处理系统、电子设备及存储介质。
背景技术
在信息显示技术领域，一般需要将一些事项的事项信息以事项列表的形式显示在终端上，在显示时，还需要按照事项的发生时段的先后顺序，不断更新终端上所显示的事项列表，以让用户知晓正在发生哪些事项以及将要发生哪些事项。例如，在大屏上显示各个航班的班次信息，又例如，在尺寸较小的平板显示屏上显示某个实体会议室的会议预约列表，通过会议预约列表可以帮助用户知晓实体会议室在哪些时段预约有哪些会议。
相关技术中，由于需要对终端上所显示的事项列表进行适时更新，便需要服务器根据每个事项信息的发生时间去更新终端所显示的事项列表，然而，在事项的发生时间很近的情况下，服务器会频繁更新终端所显示的事项列表，此种情况下，在服务器和终端之间会有时间相隔很近的密集的更新事件，密集的更新事件一方面会造成线程崩溃的问题，致使更新失败，另一方面密集的更新事件会带来网络拥堵和时延等问题，致使更新不准确。
概述
本公开提供了一种信息处理方法，所述信息处理方法包括：
接收客户端发送的多条事项信息，每条事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发所述服务器更新终端 上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；
在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；
基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
在一种可选的实施例中，基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，包括：
若所述触发时点间隔大于第一预设阈值，则确定所述当前待触发的定时任务和所述下一个待触发的定时任务均为所述目标定时任务；
若所述触发时点间隔不大于所述第一预设阈值，则确定所述当前待触发的定时任务和所述下一个待触发的定时任务中，发生时段较晚的为所述目标定时任务。
在一种可选的实施例中，所述方法还包括：
若所述触发时点间隔大于或等于第二预设阈值，则确定第一发生时段和第二发生时段之间的间隔时长；所述第一发生时段为所述当前待触发的定时任务对应的事项的发生时段，所述第二发生时段为所述下一个待触发的定时任务对应的事项的发生时段；
在所述间隔时长大于或等于目标间隔时长的情况下，基于所述第一发生时段和所述第二发生时段，生成事项空闲信息；所述事项空闲信息用于指示在所述第一发生时段与所述第二发生时段之间的时段可被预约；
将所述事项空闲信息添加至所述终端上显示的事项列表中，以在所述事项列表中展示可被预约的时段。
在一种可选的实施例中，所述事项列表是通过以下步骤生成的：
接收所述客户端发送的事项列表模板；
基于所述事项列表模板、所述正发生和/或待发生的事项的事项信息，生成所述事项列表。
在一种可选的实施例中，所述在所述目标定时任务的触发时点，更新所述终端上显示的事项列表的步骤，包括：
在所述目标定时任务的触发时点，获取所述目标定时任务对应的第一事项信息，以及第二事项信息，其中，所述第二事项信息的发生时段位于所述目标定时任务对应的事项的发生时段之后；
对所述第一事项信息的状态和所述第二事项信息的状态进行更新，其中，所述状态包括正发生状态、未发生状态；
基于所述第一事项信息和所述第二事项信息，以及各自更新后的状态，生成新的事项列表；
将所述新的事项列表发送给所述终端，以更新所述终端上显示的事项列表。
在一种可选的实施例中，在所述目标定时任务的触发时点，更新所述终端上当前显示的事项列表的步骤之后，所述方法还包括：
在检测到多个所述事项信息中的任一第三事项信息被更新时，基于更新后的第一事项信息和所述终端上当前显示的事项列表，生成对应的更新后事项列表；
将所述更新后事项列表发送给所述终端，以使所述终端对所显示的事项列表进行刷新。
在一种可选的实施例中，每条事项信息对应的定时任务的触发时点是依据该条事项信息的发生时段确定的；所述方法还包括：
在检测到多个所述事项信息中的任一第四事项信息的发生时段被更新时，依据更新后的发生时段，对所述第二事项信息对应的定时任务的触发时点进行更新。
在一种可选的实施例中，在所述确定目标定时任务的步骤之后，所述方法还包括：
在所述目标定时任务对应的事项的发生时段到来时，向显示设备发送所述目标定时任务对应的事项信息，以使所述显示设备刷新所显示的事项信息。
在一种可选的实施例中，包括多个所述终端，所述方法还包括：
接收多个所述终端各自发送的当前性能参数，所述当前性能参数包括但不限于剩余电量、信号强度中的至少一者；
所述在所述目标定时任务的触发时点，更新所述终端上显示的事项列表的步骤，包括：
在所述目标定时任务的触发时点，更新目标终端上当前所显示的事项列表；其中，所述目标终端的当前性能参数大于或等于目标性能参数。
本公开实施例还提供了一种信息处理方法，应用于客户端，所述方法包括：
响应于在事项预约界面上进行的事项录入，获取录入的事项信息；其中，所述事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；
向所述服务器发送所述事项信息，以使所述服务器在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；并基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
在一种可选的实施例中，在所述向所述服务器发送所述事项信息的步骤之前，所述方法还包括：
响应于在模板设置界面上进行的事项列表模板的绘制完成操作，获取所绘制的事项列表模板；
将所述事项列表模板导出为对象简谱JSON类型的数据后，上传至所述服务器，使所述服务器基于获取的所述事项列表模板、以及所述正发生和/或待发生的事项的事项信息，生成所述事项列表。
在一种可选的实施例中，所述模板设置界面包括表格配置项，所述响应于在模板设置界面上进行的事项列表模板的绘制操作，获取所绘制的事项列表模板的步骤，包括：
响应于在所述表格配置项中输入的表格属性参数，生成表格，所述表格属性参数包括表格尺寸、行数和列数的至少一种；
接收在所述表格配置项中对作为表头的单元格输入的文本，以及所述文本的表头文本属性；
基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，得到所述事项列表模板。
在一种可选的实施例中，在所述基于所述表头文本属性，将对应的文本 添加至所述作为表头的单元格，得到所述事项列表模板的步骤之前，所述方法还包括：
接收在所述表格配置项中对非表头的单元格输入的表身文本属性；
基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，得到所述事项列表模板，包括：
基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，并将所述表身文本属性与对应的单元格进行绑定，得到所述事项列表模板。
在一种可选的实施例中，所述响应于在所述表格配置项中输入的表格属性参数，生成表格的步骤，包括：
响应于在所述表格配置项中输入的表格属性参数，获取待显示的显示屏的表格坐标系；
基于所述表格属性参数和所述表格坐标系，确定每个单元格在所述表格坐标系中的位置坐标；
基于每个单元格在所述表格坐标系中的位置坐标，生成所述表格。
在一种可选的实施例中，向所述服务器上传所述事项列表模板，包括：
将所述事项列表模板导出为对象简谱JSON类型的数据后，上传至所述服务器。
在一种可选的实施例中，所述模板设置界面包括绘图画布，在所述响应于在模板设置界面上进行的事项列表模板的绘制完成操作，获取所绘制的事项列表模板的步骤之前，所述方法还包括：
对所述模板设置界面上发生的每个所述绘制操作，记录该绘制操作下产生的模板元素，一个模板元素表征一次修改后的事项列表模板；所述绘制操作包括但不限于以下任一者：对所述事项列表模板中的图形的绘制操作、表格属性参数的编辑操作；
响应于触发的撤销/恢复操作，将记录的各个模板元素中，与所述撤销/恢复操作对应的目标模板元素渲染至绘图画布。
在一种可选的实施例中，对所述模板设置界面上发生的每个所述绘制操作，记录该绘制操作下产生的模板元素，包括：
对所述模板设置界面上发生的每个所述绘制操作，将所述绘图画布上的当前内容导出为JSON格式的数据；
将所导出的JSON格式的数据进行快照，以作为记录的所述模板元素。
在一种可选的实施例中，所述响应于触发的撤销/恢复操作，将记录的各个模板元素中，与所述撤销/恢复操作对应的目标模板元素渲染至绘图画布的步骤，包括：
确定所述撤销/恢复操作的操作步长；
基于所述操作步长，自最后一次记录的模板元素开始查找与所述操作步长对应的目标模板元素，并将该目标模板元素渲染至所述绘图画布；其中，所述操作步长包括撤销类型的步长和恢复类型的步长。
在一种可选的实施例中，所述方法还包括：
创建与所述绘图画布对应的全局状态对象；
在每记录一个所述模板元素时，将该模板元素以及该模板元素对应的操作步数记录到所述全局状态对象中；所述操作步数表征该模板元素对应的绘制操作；
基于所述操作步长，自最后一次记录的模板元素开始查找与所述操作步长对应的模板元素，包括：
基于所述操作步长，从所述全局状态对象中查找操作步数与所述操作步长相对应的模板元素。
在一种可选的实施例中，在所述全局状态对象中各个所述模板元素按照操作步数的顺序排列，所述方法还包括：
在所述目标模板元素不为记录的最后一个模板元素的情况下，删除中自所述目标模板元素之后的模板元素；和/或在所述全局状态对象的模板元素的数量超过目标数量时，删除排列在前的模板元素；
在每记录一个所述模板元素时，将该模板元素以及该模板元素对应的操作步数记录到所述全局状态对象中，包括：
在每记录到一个模板元素时，将该模板元素追加至所述模板元素的队列尾部中，并更新该模板元素的操作步数。
本公开还提供了一种信息处理系统，包括：
客户端，用于向服务器发送多个事项信息；每个所述事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于触发所述服务器更新终端上显示的事项列表，所述事项列表中包括正发生和/或待发生的事项的事项 信息；
服务器，用于在触发当前待触发的第一定时任务之前，确定下一个待触发的第二定时任务；并基于所述发生时段的先后顺序，以及所述第一定时任务与所述第二定时任务的触发时点的时间间隔，在所述第一定时任务和所述第二定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表；
终端，用于基于所述服务器发送的事项列表，对当前显示的事项列表进行刷新。
本公开还提供了一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行时实现如所述的信息处理方法。
本公开还提供了一种非瞬态计算机可读存储介质，其存储的计算机程序使得处理器执行所述的信息处理方法。
上述说明仅是本公开技术方案的概述，为了能够更清楚了解本公开的技术手段，而可依照说明书的内容予以实施，并且为了让本公开的上述和其它目的、特征和优点能够更明显易懂，以下特举本公开的具体实施方式。
附图简述
为了更清楚地说明本公开实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。需要说明的是，附图中的比例仅作为示意并不代表实际比例。
图1示意性地本公开提供出一种信息处理方法的实施环境图；
图2示意性地示出了本公开提供的一种实施例中的信息处理方法的步骤流程图；
图3示意性地示出了本公开提供的一种信息处理方法的步骤流程图；
图4示意性地示出了本公开提供的一种会议预约场景下的事项列表模板的示意
图5示意性地示出了本公开提供的一种获取所绘制的事项列表模板的步 骤流程图；
图6示意性地示出了本公开提供的一种基于表格坐标系计算每个单元格的位置坐标的示意图；
图7示意性地示出了本公开提供的在会议预约场景下如何得到会议列表模板的整体流程示意图；
图8示意性地示出了本公开提供的信息处理系统的框架示意图。
详细描述
为使本公开实施例的目的、技术方案和优点更加清楚，下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
以在尺寸较小的平板显示屏上显示某个实体会议室的会议预约列表(一下称会议预约场景)为例，对相关技术中存在的问题进行说明如下：
一般在企业中，会设置多个实体会议室用于线下会议的召开，一般企业中各个业务部门可以共用实体会议室，当业务部门较多时，会议也可能较多，因此需要提前对实体会议室进行预约，为此，会提供会议系统以满足企业中对实体会议室的预约服务。其中，对实体会议室的预约信息可以包括会议的召开时段、主持人、参会部门、参会人等信息，一个实体会议室可能对应多个预约信息，当然，为了不产生同一实体会议室的会议预约时段的冲突的问题，预约信息中的时段是互不重合的。
实际场景中，一个实体会议室的会议预约信息会显示在实体会议室的电子门牌上，该电子门牌是一个小型显示屏，其上显示的是会议列表，会议列表中便罗列有实体会议室的会议预约信息。其中，一般需要企业员工通过电子门牌，便可以确定实体会议室的哪些时间有会议，以及未召开的会议和正在召开的会议。
由此，需要对电子门牌上的会议列表按照会议预约信息对应的预约时段，进行实时更新。相关技术中，会为每个会议预约信息绑定两个定时任务，一个是会前的定时任务，用于在会前的时刻触发更新会议列表，另一个是会中 靠近结束时刻的定时任务，用于在快要结束会议时触发更新会议列表。如此，当两个会议预约信息的预约时段距离很近时，便会在相隔很短的时间内，产生多个会议列表的更新事件，如此密集的更新事件一方面会造成线程崩溃的问题，致使更新失败，另一方面密集的更新事件会带来网络拥堵和更新延时等问题，致使更新不准确。
当然，以上仅为示例性说明相关技术所产生的技术问题，实际中，在其他应用场景中，也存在相似的技术问题，例如，在航班或列车的班次信息的展示中也会导致同样的问题。
有鉴于此，本公开提出了解决上述问题的技术构思，具体为：在每个定时任务触发之前，确定下一待触发的定时任务，并根据该两个定时任务的发生时段的先后顺序，和触发时点的时间间隔(后文称触发时点间隔)，选取要触发的目标定时任务，从而在目标定时任务的触发时点，更新终端上的事项列表。这样，若两个相邻触发的定时任务的触发时点的时间间隔较短，则可以从两个相邻触发的定时任务中，根据发生时段的先后顺序选取其中一个定时任务触发，则另一定时任务可以不用触发，由此，可以避免相隔很近的定时任务均触发所导致的网络中频繁大量的更新事件，进而减少更新事件，避免线程崩溃，从而提高事项列表更新的成功率。再者，更新事件的减少可以避免网络带宽的拥堵，降低更新时延，从而提高事项列表更新的成功率和准确性。
参照图1所示，示出了本公开的信息处理方法的一种实施环境图，如图1所示，包括服务器、客户端、多个终端和多个显示设备，其中，客户端与服务器通信链接，服务器与多个终端和多个显示设备通信链接；具体地，多个终端通过HTTP协议与服务器连接，多个显示设备通过蓝牙等近网协议与服务器通信，其中，显示设备可以借由蓝牙网关与服务器通信，终端可以借由路由器与服务器通信，当终端被路由器扫描到后，路由器向服务器上报终端的基本信息，当显示设备被蓝牙网关扫描到后，蓝牙网关向服务器上报显示设备的基本信息。其中，基本信息可以包括剩余电量、标识、信号强度等。在会议预约的场景中，客户端用于预约会议，并将预约得到的预约信息上传给服务器，服务器用于基于预约信息生成会议列表，并在预约信息绑定的定时任务的触发时点，将基于对应的预约信息生成的会议列表发送给终端，终 端可以是上述所述的电子门牌，用于显示服务器发送的会议列表。
由图1也可知，服务器可能需要在短时间内向多个终端发起会议列表的更新事件，如此网络中频繁大量的更新事件会导致网络拥堵，会议列表更新出错的概率大大增加，而大量的更新事件又容易导致线程崩溃，导致列表更新失败。
结合图1所示的实施环境，以会议预约的应用场景为例，对本公开的信息处理方法进行介绍，参照图2所示，示出了一种实施例中的信息处理方法的步骤流程图，在该实施例中，从服务器侧阐述如何执行信息处理方法，当然，本实施例仅示例性地以会议预约的应用场景为例说明，对于其他类似的场景，如班次信息展示场景中，仍然可以适用。如图2所示，具体可以包括以下步骤：
步骤S201：接收客户端发送的多条事项信息，每条事项信息包括事项的发生时段以及对应的定时任务。
其中，所述定时任务用于在触发时点触发所述服务器更新终端上显示的事项列表，所述事项列表展示有正发生和/或待发生的事项的事项信息。
本实施例中，客户端可以是Web客户端，用户可以在浏览器中登录该客户端，从而在客户端所提供的事项预约界面中录入要预约的事项的事项信息，从而将事项信息上传至服务器。其中，每个事项信息中包括事项的发生时段，该发生时段是指事项在哪一时段开展，定时任务可以携带在事项信息中，或者，定时任务可以与事项信息绑定后，与事项信息单独发送。其中，绑定可以是指定时任务的标识与事项信息的标识进行关联，只要确定个事项信息与定时任务的关联关系即可。
其中，终端用于显示事项列表，事项列表包括正发生和/或待发生的事项的事项信息，具体而言，在一些场景中，事项列表可以包括正发生的事项，正发生的事项是指：发生时段在当前时间的事项。在又一些场景中，事项列表可以包括待发生的事项，待发生的事项是指：发生时段在当前时间之后还未开始的事项。在另一些场景中，事项列表可以包括待发生的事项和正发生的事项。
本实施例中，每个事项信息对应的定时任务会具有自身的触发时点，该触发时点可以根据发生时段设置，一般而言，触发时点可以设置在发生时段 之前、也可以设置在发生时段的结束时刻、或者可以设置在发生时段中，或者上述三种情况都有，具体地，可以根据用户需求进行。其中，允许不同的事项信息可以个性化设置定时任务的不同触发时点，例如，一些事项信息的定时任务的触发时点设置在发生时段的结束时刻，而另一些事项信息的定时任务的触发时点设置在发生时段之前。其中，也可以允许一个事项信息对应一个定时任务或对应多个定时任务。
具体实施时，定时任务可以在自身的触发时点被触发，当定时任务在触发时点被触发时，表征该定时任务对应的事项信息需要显示到终端上，或需要从终端上显示的事项列表中清除；由此，服务器便会响应于该触发，确定当前需要在终端上显示的事项信息，进而根据当前需要在终端上显示的事项信息，更新终端上显示的事项列表，以使终端上显示的事项列表仅包括正发生的事项，或仅包括待发生的事项，或同时包括待发生的事项和正发生的事项。
在一种可选的示例中，在应用于会议预约的应用场景中时，事项信息可以是会议预约信息，会议预约信息中包括预约时段，该预约时段即是发生时段，可以理解为是会议的召开时段，此种情况下，定时任务可以用于触发服务器更新终端上的会议列表，以展示当前正开展和后续待开展的会议预约信息。在应用于班次信息展示的应用场景中时，事项信息可以是班次信息，班次信息中包括发车时间和到达时间，发车时间和到达时间之间的时段称为发生时段，而定时任务可以用于触发服务器更新显示大屏上显示的班次信息列表(即事项列表)，以展示还未发车的班次信息。
步骤S202：在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔。
本实施例中，由于每个定时任务都有自身的触发时点，因此，可以在每个定时任务在其对应的触发时点被触发之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔。
示例#，事项信息1对应定时任务1，事项信息2对应定时任务2，事项信息3对应定时任务3，其中，定时任务1的触发时点是12:55，定时任务2的触发时点是12:50，定时任务3的触发时点是13:01，则定时任务2在12:50被触发，其中，在定时任务2的触发时点之前，即12:50之前，例如， 12:49便可以确定下一个待触发的定时任务，即定时任务1。进而可以确定该两个相邻触发的定时任务之间的触发时点间隔。
其中，触发时点间隔较小，例如相隔1分钟，则在服务器中存在大量事项信息的情况下，会产生密集型的多个更新事件，触发时点间隔较大，例如，相隔10分钟，则一般不会产生密集型的多个更新事件。
当然，在一些场景中，当前待触发的定时任务对应的事项信息和下一个待触发的定时任务对应的事项信息需要同属一个项目，如在会议预约场景中，当前待触发的定时任务和下一个待触发的定时任务需要对应一个实体会议室，又例如在班次信息展示场景中，当前待触发的定时任务和下一个待触发的定时任务需要对应同一条线路，或同一条航线，或者，同一个候车室。
步骤S203：基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
本实施例中，可以结合触发时点间隔和发生时段的先后顺序，在当前待触发的定时任务和下一个待触发的定时任务中，确定保留哪一定时任务，被保留的定时任务称为目标定时任务。
具体而言，当触发时点间隔较小的情况下，则可以选择保留当前待触发的定时任务或下一个待触发的定时任务，需要说明的是，由于允许不同的事项信息可以个性化设置定时任务的不同触发时点，这样，触发时点较早的定时任务对应的事项的发生时段，不一定早于触发时点较晚的定时任务对应的事项的发生时段。因此，在触发时点间隔较小的情况下，具体保留哪一定时任务，可以依据发生时段的先后顺序确定。例如，在一些场景中，保留发生时段较晚的定时任务，在又一些场景中，保留发生时段较早的定时任务。
其中，当触发时点间隔较大的情况下，一般不会产生密集型的多个更新事件，因此，可以保留当前待触发的定时任务和下一个待触发的定时任务，当然，在一些其他有需求的场景中，也可以在此种情况下，依据发生时段的先后顺序，保留其中一个定时任务。
以上述示例#为例，定时任务2在12:50被触发之前，确定下一触发的是定时任务1，二者之前的触发时点间隔是5分钟，触发时点间隔较小，因此，可以将发生时段较晚的定时任务保留。其中，定时任务1对应的发生时段是 12:00-13:00，定时任务2对应的发生时段是13:00-14:00，可见，定时任务1的发生时段较早，由此，取消定时任务1，保留定时任务2，定时任务2作为目标定时任务。在12:50触发定时任务2时，服务器便可以更新终端上显示的事项列表。由此，在12:55便不再有定时任务触发，从而不会导致密集的更新事件爆发。
采用本公开实施例的技术方案，由于对于定时任务的触发，可以基于每相邻两个触发的定时任务之间的触发时点间隔，和各自对应的发生时段之间的先后顺序，保留其中一个定时任务作为目标定时任务，并在目标定时任务的触发时点，再更新终端上显示的事项列表。由此，可以避免相隔很近的定时任务均触发所产生的频繁大量的更新事件，对服务器而言，减少更新事件的情况下，可以避免线程崩溃，提高事项列表更新的成功率；而对于服务器与终端所处的网络环境而言，减少短时间内的更新事件，可以避免网络拥堵，降低更新时延，保证更新的准确性。
在一种可选的实施例中，示出了确定目标定时任务的过程：
其中，在确定目标定时任务时，可以在触发时点间隔较小的情况下，选取发生时段较晚的定时任务作为目标定时任务，而在触发时点间隔较大的情况下，将当前待触发的定时任务和下一个待触发的定时任务均保留为目标定时任务。
具体地，若触发时点间隔大于第一预设阈值，则确定当前待触发的定时任务和所述下一个待触发的定时任务均为目标定时任务；若所述时间间隔不大于第一预设阈值，则确定当前待触发的定时任务和所述下一个待触发的定时任务中，发生时段较晚的为目标定时任务。
本实施例中，第一预设阈值可以根据服务器的性能以及网络环境所确定，例如，可以确定为10分钟，或者确定为更短的5分钟。当触发时点间隔大于第一预设阈值，表征服务器发出的更新事件的间隔时长较长，不会导致密集更新事件的发生，由此，可以将两个定时任务均保留为目标定时任务。
当触发时点间隔不大于第一预设阈值，表征服务器发出的更新事件的间隔时长较短，会导致密集更新事件的发生，由此，可以将两个定时任务中发生时段较晚的作为目标定时任务。其中，发生时段较晚的作为目标定时任务可以促使服务器将待发生的事项的事项信息更新至终端列表，满足如会议预 约场景下的用户需求。在一种可选的示例中，触发时点间隔不大于第一预设阈值的情况中，可以包括两个定时任务的触发时点不同的情况，也可以包括两个定时任务的触发时点相同的情况；在触发时点相同的情况下，可以将两个触发时点相同的定时任务中，发生时段较晚的事项信息对应的定时任务取消。
下面，结合会议预约场景的三个具体事例，对本公开如何确定目标定时任务的过程进行示例性说明。
具体示例1：某年某月某日，实体会议室1当天下午预约了四场会议，如下表1所示，表1为实体会议室1对应的会议列表。
表1实体会议室1对应的会议列表
如表1所示，当天下午有四场会议，会议1有两个定时任务，触发时点分别为：12：55和13：55。会议2的两个定时任务的触发时点分别为如下时点：13：50和14：50。其中，会议2的13:50的定时任务先触发，下一个触发的是会议1的13：55的定时任务，触发时点间隔较小，且13：50这个定时任务对应的会议时间(会议2)在13：55定时任务对应的会议时间(会议1)之后，此种情况下，13：55的定时任务将自动取消，服务器在13:50更新会议列表，更新时，直接不再下发会议室1的会议预约信息到终端上，更新后终端显示的会议列表包括会议2-会议4的会议预约信息。
具体示例2：某年某月某日，实体会议室2当天下午预约了四场会议，如下表2所示，表2为实体会议室2对应的会议列表。
如表2所示，当天下午会议室2有四场会议，会议1有两个定时任务，触发时点分别为：12：50和13：50。
表2实体会议室2对应的会议列表
其中，会议2的两个定时任务的触发时点分别为：13：55和14：55。当将要触发13：50的定时任务时，可以确定下一个触发的是13：55的定时任务，触发时点相隔很近，再者13：55定时任务对应的会议时间(会议2)在13：50定时任务对应的会议时间(会议1)之后，此种情况下，13：50的定时任务将不触发，自动取消，等待13：55的定时任务触发，服务器在13:55更新会议列表，更新后终端显示的会议列表包括会议2-会议4的会议预约信息。
具体示例3：某年某月某日，实体会议室3当天下午预约了四场会议，如下表3所示，表3为实体会议室3对应的会议列表。
表3实体会议室3对应的会议列表
如表3所示，当天下午会议室3有四场会议，会议1有两个定时任务，触发时点分别为：12：55和13：55。会议2的两个定时任务的触发时点分别为：13：55和14：55。当将要触发13：55的定时任务时，可以确定同时有另一13：55的定时任务，触发时点相同，此种情况下，会议1的发生时段较早，则取消会议1对应的定时任务，并依据会议2的定时任务的触发，更新会议列表，更新后终端显示的会议列表包括会议2-会议4的会议预约信息。
在一种可选的实施例中，在确定目标定时任务时，可以在触发时点间隔 较大的情况下，确定触发时点间隔是否足以满足一个事项的发生，若是则可以指示终端展示该间隔时长内的时间空闲的信息，以告知用户该时段可以被预约事项。
具体实施时，若触发时点间隔大于或等于第二预设阈值，则确定第一发生时段和第二发生时段之间的间隔时长；第一发生时段为当前待触发的定时任务对应的事项的发生时段，第二发生时段为下一个待触发的定时任务对应的事项的发生时段。
在间隔时长大于或等于目标间隔时长的情况下，基于第一发生时段和第二发生时段，向终端和/或客户端发送事项空闲信息；事项空闲信息用于指示在第一发生时段与第二发生时段之间的时段可被预约。
当然，在具体实施时，可以将事项空闲信息添加至终端上显示的事项列表中，以在事项列表中展示可被预约的时段。此种情况下，事项空闲信息可以添加到实现列表中，位于当前待触发的定时任务对应的事项信息与下一个待触发的定时任务对应的事项信息之间的位置。
本实施例中，若触发时点间隔较大，且大于第二预设阈值，表征在两个定时任务各自所对应的事项的发生时段之间具有较长的间隔时长。此种情况下，可以确定为当前待触发的定时任务对应的事项的第一发生时段，与下一个待触发的定时任务对应的事项的第二发生时段之间的间隔时长。其中，第二预设阈值大于第一预设阈值。
其中，在第一发生时段较早发生时，间隔时长可以是指第一发生时段的结束时刻与第二发生时段的开始时刻之间的间隔时间，在第一发生时段较晚发生时，间隔时长可以是指第二发生时段的结束时刻与第一发生时段的开始时刻之间的间隔时间。
其中，在间隔时长大于或等于目标间隔时长的情况下，可以向终端和/或客户端发送事项空闲信息，该事项空闲信息可以是基于第一发生时段和第二发生时段之间的时段所生成的，该第一发生时段和第二发生时段之间的时段可以被称为空闲时段，事项空闲信息主要用于表征该空闲时段可被预约。
其中，在会议预约场景中，事项空闲信息还可以包括会议室标识，以标识某个实体会议室的哪一时段还可以被预约会议。其中，目标间隔时长可以根据实际需求设置，例如，设置为大于30分钟的时长。
具体示例4：某年某月某日，实体会议室4当天下午预约了四场会议，如下表4所示，表4为实体会议室4对应的会议列表。
表4实体会议室4对应的会议列表
如表4所示，此时以会议2和会议3为例，当会议2结束的14：55的定时任务触发时，下一定时任务是会议3的16:50的定时任务，两个定时任务的触发时点间隔为1小时50分钟，足够大，因此，可以进一步确定会议2和会议3之间的间隔时长，可知，间隔时长是2小时，可以供一个或多个会议的预约，由此，可以生成15:00-17:00之间的事项空闲信息，指示该时段可以被预约。具体而言，可以在表4中的会议2和会议3之间插入一条事项空闲信息，在会议名称一列标记“空闲”，这样在终端上的会议列表中，在会议3之前会显示“空闲”。
在一种可选的实施例中，示出了对事项列表的更新过程：
其中，对事项列表的更新包括：依据定时任务对事项列表的更新，以及依据被修改的事项信息或被新增的事项信息对事项列表的更新。其中，依据定时任务对事项列表的更新的过程如下：
其中，事项列表可以是服务器根据当前待发生的事项的事项信息生成的，当前待发生的事项的事项信息可以是基于对应的定时任务的触发确定的，即可以包括触发的定时任务对应的事项信息和待触发的定时任务对应的事项信息。
在一种具体示例中，可以接收客户端发送的事项列表模板；基于事项列表模板、正发生和/或待发生的事项的事项信息，生成事项列表。
具体实施时，事项列表模板可以是客户端制作好后上传到服务器，事项列表模板的制作可以详见后面客户端侧的实施例所述，在此先不赘述。其中， 事项列表模板可以规定正发生和/或待发生的事项的事项信息以列表的形式显示。在一种可选的示例中，事项列表模板可以理解为是一种表格类型的模板，包括行和列，其中，作为表头的表格，例如第一行的表格的名称可以预先设置，每条事项信息作为表格中的表身内容。如上述表1-表4所示，事项列表模板可以理解为是不含表身中会议预约信息的表。
如上所述，可以根据需求，在事项列表中显示正发生和/或待发生的事项的事项信息，因此，在更新终端上显示的事项列表时，可以将当前触发的定时任务对应的事项信息添加至事项列表模板，以具体示例1为例，可以在13:50，将会议2的事项信息添加至事项列表模板。
或者，将发生时段位于当前触发的定时任务对应的事项之后的事项信息添加至事项列表模板，以具体示例1为例，可以在13:50，将会议3和会议4的事项信息添加至事项列表模板。
或者，将当前触发的定时任务对应的事项信息，以及发生时段位于当前触发的定时任务对应的事项之后的事项信息添加至事项列表模板，以具体示例1为例，可以在13:50，将会议2、会议3和会议4的事项信息添加至事项列表模板。
具体实施时，在一种可选的示例中，示出了对终端上的显示列表进行更新的过程，具体地，可以在目标定时任务的触发时点，获取目标定时任务对应的第一事项信息，以及第二事项信息，基于第一事项信息和第二事项信息，生成新的事项列表；并将新的事项列表发送给终端，以更新终端上显示的事项列表。
其中，第二事项信息的发生时段位于目标定时任务对应的事项的发生时段之后。
本可选的示例中，第一事项信息可以理解为是正要发生的事项信息，第二事项信息可以理解为是待发生的事项信息，其中，可以将第一事项信息和第二事项信息逐行添加至事项列表模板中，在逐行添加时，可以按照第一事项信息和第二事项信息的发生时段的先后顺序添加到事项列表中，从而得到新的事项列表，将该新的事项列表发送给终端，终端在接收到新的事项列表后，可以对所显示的事项列表进行刷新，从而实现了对终端上的显示列表的更新。
当然，在又一种实施例中，事项列表中可以包括各个事项信息的当前状态，在更新事项列表时，可以一并更新要显示的事项列表中各个事项信息的状态。
具体实施时，在生成新的事项列表时，可以对第一事项信息的状态和第二事项信息的状态进行更新，基于第一事项信息和第二事项信息，以及各自更新后的状态，生成新的事项列表。其中，状态包括正发生状态、未发生状态。
其中，第一事项信息的状态可以根据目标定时任务对应的事项的发生时段确定，若发生时段在当前时刻之后且距离当前时刻很近，则表示该事项正要发生，因此其状态可以从未发生状态变更为正发生状态，第二事项信息的状态可以保持为未发生状态。相应地，在生成新的事项列表时，可以将各个事项信息的状态标识在列表中。
以上述表1-表4为例，可以新增一列，用于标识各个会议的状态，当然，在会议预约场景中，会议的状态可以包括正开始状态和待召开状态。
采用此种实施方式时，可以对事项列表中每个事项信息的状态进行更新和标识，以帮助用户获取哪些事项正在发生而哪些事项待发生，从而优化用户体验。
其中，依据被修改的事项信息或被新增的事项信息对事项列表的更新的过程如下：
在检测到多个事项信息中的任一第三事项信息被更新时，基于更新后的第一事项信息和终端上当前显示的事项列表，生成对应的更新后事项列表；并将更新后事项列表发送给终端，以使终端对所显示的事项列表进行刷新。
本实施例中，若客户端对其中一个第三事项信息进行了更新，则可以基于更新后的第三事项信息，对终端上显示的事项列表进行实时更新。具体地，可以根据更新后的第三事项信息和终端上当前显示的事项列表中的各个事项信息，生成更新后事项列表，并将更新后事项列表发送给终端，终端在接收到新的事项列表后，可以对所显示的事项列表进行刷新，从而实现了对终端上的显示列表的实时更新。
其中，事项信息的更新可以包括发生时段的更新以及其他属性的更新，如在会议预约场景中，还可以包括预约的会议室的更新。
其中，在触发时点是基于事项信息的发生时段生成的情况下，在检测到某一事项信息的发生时段更新时，还可以更新对应的定时任务的触发时点。
具体实施时，可以在检测到多个事项信息中的任一第四事项信息的发生时段被更新时，依据更新后的发生时段，对第四事项信息对应的定时任务的触发时点进行更新。
其中，可以依据更新后的发生时段，以及第四事项信息的触发时点设置策略，得到新的触发时点，进而在新的触发时点触发第四事项信息的定时任务。
具体示例5：当会议3的时间由16：00-17：00改为17：00-17：30时，一方面，会基于新的会议3和原本显示的会议1、会议2和会议4，生成新的会议列表，然后显示到终端上。另一方面，会议3的两个定时任务由原先的15：50和16：50更新为16:50和17:20。
采用本公开实施例的技术方案，只要检测到事项信息被更新，或者事项信息的发生时段被更新，都会更新事项列表，且在发生时段被更新时，还可以更新该事项信息对应的定时任务的触发时点，从而保证终端显示事项列表的准确性。
在一种实施例中，如图1所示的实施环境中，多个终端中可以包括门票类型的终端和电子桌牌类型的显示设备；其中，对于门票类型的终端用于显示整个会议室的会议列表，而电子桌牌类型的显示设备用于显示当前进行的会议的会议预约信息。则服务器除可以对终端上的事项列表进行更新外，还可以对电子桌牌类型的显示设备上显示的事项信息进行更新，以使电子桌牌类型的显示设备上显示的是正在进行的事项的事项信息。
具体实施时，可以在确定目标定时任务之后，在目标定时任务对应的事项的发生时段到来时，向多个显示设备发送目标定时任务对应的事项信息，以使显示设备刷新所显示的事项信息。
其中，在目标定时任务对应的事项的发生时段到来时可以是指：在目标定时任务对应的事项的发生时段中，具体可以是发生时段的开始时刻，或开始时刻之后的任一时刻，向显示设备发送目标定时任务对应的事项信息，显示设备在接收到服务器发送的事项信息时，可以对显示的事项信息进行刷新。
在一种可选的实施例中，如图1所示的实施环境，如MAC地址、剩余 电量、信号强度等。服务器将这些信息存到数据库里并显示在Web页面上。用户通过Web页面可以选择在某个会议室，某个时间段预约会议(会议最短时长三十分钟)，会议预约成功后，会议预约信息传到服务器。
其中，可以在目标定时任务对应的事项的发生时段的开始时刻之后的预设时长后，向显示设备发送目标定时任务对应的事项信息，这是因为可以在触发时点之后的一段时间后发送事项信息，以避开触发时点，从而避免发送更新事项信息的事件与更新事项列表的事件相隔很近发送，从而进一步减少网络拥堵的情况。
其中，客户端的用户可基于终端的各种信息(如电量，信号强度等)决定是否对其进行绑定操作，绑定操作的意义是：绑定后的终端和显示设备可以被会议系统使用，将被下发会议预约信息，更新会议列表。
其中，为进一步减少更新事件的密集性，可以在更新事项列表时，对当前性能较好的终端上的事项列表进行更新。具体实施时，接收多个终端各自发送的当前性能参数，当前性能参数至少包括剩余电量、信号强度中的至少一者，接着，可以更新目标终端上当前所显示的事项列表；其中，目标终端的当前性能参数大于或等于目标性能参数。
本实施例中，目标终端可以是剩余电量大于目标剩余电量的终端，或者，目标终端可以是信号强度大于目标信号强度的终端，或者，目标终端可以是剩余电量大于目标剩余电量、且信号强度大于目标信号强度的终端。
在一种可选的示例中，依据当前性能参数的方案也适用于对显示设备上的事项信息的更新，则相应地，可以向多个显示设备中当前性能参数大于或等于目标性能参数的显示设备发送目标定时任务对应的事项信息，以刷新所显示的事项信息。
在会议预约场景中，该显示设备是电子桌牌，一般一个会议室有多个电子桌牌，电子桌牌的数量多于电子门牌的数量，因此，当选择更新信号强度高和剩余电量多的电子桌牌的事项信息时，可以减小发送事项信息的更新事件，从而进一步降低信息对网络带宽的占用。
采用本实施方式的技术方案，可以减少服务器向终端发送的更新事件，从而进一步避免对网络的拥堵，提高对目标终端的事项列表的准确性。
下面，结合会议预约场景下的一个具体示例，如图1所示的实施环境， 对本公开实施例的信息处理方法进行介绍：
S1：终端通过协议被路由器扫描到后，路由器向服务器上报终端的基本信息，显示设备通过蓝牙协议被蓝牙网关扫描到后，蓝牙网关向服务器上报显示设备的基本信息，基本信息包括MAC地址、电量、信号强度等。服务器将各个终端和显示设备的基本信息会存到数据库里，并通过Web页面展示。
S2：客户端的用户可依据终端和显示设备的基本信息决定是否对其进行绑定操作，绑定后的终端可以被服务器下发会议列表，绑定后的显示设备可以被服务器下发会议预约信息。
S3：客户端的用户在会议室中预约会议，并绑定一些终端来显示此会议室下的会议列表和会议预约信息，其中，电子门牌显示会议列表，电子桌牌显示会议预约信息。
S4：服务器接收到客户端发送的会议预约信息，基于会议预约信息的发生时段，和预设的触发时点设置策略，生成会议预约信息对应的定时任务。
其中，一个会议预约信息包括两个定时任务，分别为会议开始前的定时任务，和会议快要结束时的定时任务，每个会议预约信息和对应的定时任务都存在数据库里等待被触发。
S5：在每个待触发的定时任务触发之前，确定该定时任务与下一个待触发的定时任务之间的触发时点间隔。若触发时点间隔大于5分钟，则执行步骤S6，否则，执行步骤S7。
S6：将该两个定时任务中，发生时段较晚的会议预约信息对应的定时任务保留，而取消另一定时任务，并在该保留的定时任务的触发时点，向终端发送该保留的定时任务对应的会议预约信息和待发生的会议预约信息所生成的会议列表，终端接收到会议列表后，刷新所显示的会议列表。
在更新所显示的会议列表之后，该保留的定时任务对应的会议开始后一段时间，向绑定的显示设备发送该保留的定时任务对应的会议预约信息，具体可以包括参会人、主持人和会议主题等信息。
S7：将该两个定时任务都保留，在每个定时任务的触发时点，均基于触发的定时任务对应的会议预约信息和待发生的会议预约信息所生成的会议列表，终端接收到会议列表后，刷新所显示的会议列表。
其中，可以判断两个定时任务对应的事项的发生时段之间的间隔时长， 若间隔时长大于目标间隔时长，则执行步骤S8，否则，则执行步骤S9。
S8：客户端发送事项空闲信息，向终端发生包含事项空闲信息的事项列表，以指示在该两个会议之间的时段可被预约。
其中，上述所述的事项列表、事项信息都可以由服务器通过HTTP协议封装好后下发到终端。
采用本公开实施的信息处理方法，具有以下优点：
第一方面，避免更新事件在短时间内的密集发生，避免了对网络带宽的拥堵、降低线程发生崩溃的概率，从而提高了更新事项列表的准确性和成功率。
第二方面，可以在两个相邻发生的事项之间的间隔时长超过一定时长时，主动将该间隔时长所在的时间区间显示在终端的事项列表中，从而丰富了事项列表的更新机制，使得用户可以直接从终端显示的事项列表查看可以预约的时段，优化了用户体验。
第三方面，可以在更新终端显示的事项列表的同时，将正在发生的事项的事项信息显示到显示设备中，由此可以实现对事项信息的两种维度的展示，丰富了信息显示场景，优化了用户体验。
第四方面，可以在事项信息的发生时段被更新时，对对应的定时任务的触发时点进行更新，从而保证了对终端的事项列表的更新准确性。
基于相同的发明构思，发明人构思了提出了一种客户端的改进，在该客户端上，可以向服务器提供事项信息和事项信息对应的定时任务，以使服务器可以依据定时任务的触发时点和事项信息中包括的发生时段，在每一个待触发的定时任务触发之前，从该定时任务和下一个待触发的定时任务中选取目标定时任务，以在触发时点间隔较小的情况下，取消一个定时任务的触发，以避免短时间内密集的更新事件发生，避免网络拥堵和线程崩溃，从而提高对终端上显示的事项列表的更新准确率和更新成功率。
仍然结合图1所示的实施环境，对本公开的一种实施例中的信息处理方法进行介绍，该方法可以应用于客户端侧。参照图3所示，示出了一种实施例中的信息处理方法的步骤流程图，如图3所示，具体可以包括以下步骤：
步骤S301：响应于在事项预约界面上进行的事项录入，获取录入的事项信息。
其中，所述事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息。
步骤S302：向所述服务器发送所述事项信息，以使所述服务器在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；并基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
本实施例中，事项预约界面可以理解为客户端提供的供用户预约事项的Web页面，如上述服务器侧实施例所述，事项预约界面可以包括终端上报到服务端的基本信息，用户可以在该事项预约界面选择要显示事项列表的终端，以及录入事项信息。
在一种可选的示例中，在录入事项信息时，可以同时设置定时任务的触发时点，在设置有定时任务的触发时点时，客户端可以生成事项信息对应的定时任务。在又一种可选的示例中，在录入事项信息时，可以同时设置定时任务的触发时点设置策略，例如，设置在发生时段之前的五分钟和/或设置在发生时段结束前的五分钟。其中，可以为在事项预约界面提供几种不同的触发时点设置策略供用户选择，此种情况下，服务器可以根据事项信息和触发时点设置策略，生成对应的定时任务。
其中，服务器如何根据各个事项信息的定时任务，更新终端上显示的事项列表的过程可以参照上述服务器侧的实施例所述，在此不再赘述。
相应地，如上述服务器侧的信息处理方法的实施例所述，事项列表是依据正发生和/或待发生的事项的事项信息，以及事项列表模板生成的，其中，在客户端侧可以提供该事项列表模板。
具体实施时，在上传事项信息之前，客户端侧可以响应于在模板设置界面上进行的事项列表模板的绘制完成操作，获取所绘制的事项列表模板；向服务器上传事项列表模板，使服务器基于事项列表模板、以及正发生和/或待发生的事项的事项信息，生成事项列表。
参照图4所示，示出了一种会议预约场景下的事项列表模板的示意图， 下面，结合图4所示的事项列表模板，对本公开如何得到事项列表模板的过程进行说明。
其中，如图4所示，事项列表模板是包含表格的模板，在该模板中包括表头和表身，由行和列构成，还包括其他信息，如会议室的属性信息等。相关技术中，一般是在Canvas提供的绘图界面中绘制事项列表模板，其中，Canvas是HTML5提供的在网页上利用脚本绘制图形的方法，但是原生Canvas存在一些不足，如缺少交互式对象模型、图形组合、对象的拖拽缩放等，此种情况下，在绘制事项列表模板时，仅能一个单元格一个单元格的绘制，即用户需要分别绘制出多个单元格后，将多个单元格组合后才能形成表格，此种方式耗时较长，导致绘制事项列表模板的效率很低。
因此，发明人在构思解决以上技术问题的技术方案时，将表格图形看做多个单元格的组合图形，单元格看做矩形与文本的组合图形，根据这个思路，自定义了一种绘制事项列表模板的方法。具体实现目标是：在画布中可以一次性批量绘制一个表格图形，并且表格中的每个单元格可单独配置文本样式。采用该实施方式时，用户只需设置表格属性参数，即可批量生成多个单元格，从而得到表格。
为事项上述目标，一种方式是使用fabric.js开源库，将该fabric.js开源库移植到基于Canvas的绘图库，来实现对窗口图形的各种可视化操作，其优势在于图形组合的整体操作。如果不使用fabric.js，在网页上实现2D平面图形的绘制和交互也可以使用原生的Canvas和SVG(Scalable Vector Graphics，可缩放的矢量图形)技术。
其中，SVG是一种使用XML描述2D图形的语言，它相比Canvas最大的优势是：第一，每个被绘制的图形都被视为对象，可以为其添加相关的事件处理器；第二，SVG图像在放大或改变尺寸的情况下其图形质量不会有所损失。
参照图5所示，示出了一种获取所绘制的事项列表模板的步骤流程图，如图5所示，具体可以包括以下步骤：
步骤S501：响应于在所述表格配置项中输入的表格属性参数，生成表格。
其中，所述表格属性参数包括表格尺寸、行数和列数的至少一种。
其中，表格配置项可以用于接收用户输入的表格属性参数，具体而言，表格配置项可以包括表格的高度参数和宽度参数，接着，可以根据根据表格坐标系，计算在表格属性参数下，有多少个单元格，并计算每个单元格的坐标值，从而根据每个单元格的坐标值循环生成多个单元格，进而得到表格。
具体实施时，在实施该步骤S501时，可以采用以下过程：
首先，响应于在表格配置项中输入的表格属性参数，获取待显示的显示屏的表格坐标系；之后，基于表格属性参数和表格坐标系，确定每个单元格在表格坐标系中的位置坐标，并基于每个单元格在表格坐标系中的位置坐标，生成表格。
在一种可选的实施例中，表格属性参数包括表格尺寸、行数和列数，表格尺寸包括表格的长度和宽度，表格坐标系可以是依据显示屏的显示坐标系，行数和列数可以用于在表格尺寸下，确定单元格的数量，进而基于显示坐标系，确定出每个单元格的坐标。参照图6所示，示出了一种基于表格坐标系计算每个单元格的位置坐标的示意图。
其中，表格宽度为width，高度为height，表格列数是n，单元格宽度为tw、单元格高度为th，index为第i列，rowIndex为第i行。
其中，tw＝width/n；
left＝width/2+tw*(index-1)，表头的高度计算如下：th＝-height/2，表身的th＝-height/2+th*(rowIndex+1)；
其中，事项列表模板的最大展示行数是动态计算出的，在表格行数计算时，会取到整个画布的高度，根据行高计算出行数。
由此，可以得到每个单元格在表格坐标系中的位置，即每个单元格的长度和宽度，从而循环在每个对应位置生成对应的单元格，进而得到了表格。
步骤S502：接收在表格配置项中对作为表头的单元格输入的文本，以及文本的表头文本属性。
其中，表头文本属性包括文本的字体大小、颜色、位置等一个或多个属性。实际中，表头文本属性可以在表格配置项中录入或选择，具体可以参照相关技术中选择字体样式的类似实现过程，而针对表头的单元格，可以录入配置的文本。
步骤S503：基于表头文本属性，将对应的文本添加至作为表头的单元 格，得到所述事项列表模板。
本实施例中，可以在生成的表格中，将表头的单元格中按照表头文本属性将对应的文本添加至该表头的单元格中，从而得到如图4所示的事项列表模板。
相应地，还提出了一种绘制的事项列表模板的步骤流程图，在该实施方式中，在步骤S503之前，还可以包括设置表身中文本属性的过程，具体地，可以接收在表格配置项中对非表头的单元格输入的表身文本属性；相应地，在步骤S503中，可以基于表头文本属性，将对应的文本添加至作为表头的单元格，并将表身文本属性与对应的单元格进行绑定，得到事项列表模板。
其中，表身文本属性也可以包括文本的字体大小、颜色、位置等一个或多个属性，表身文本属性用于规定配置到表身的单元格中的文本样式。由于表身的单元格中的文本是后期由服务器根据事项信息添加进的，因此，表身文本属性可以携带在事项列表模板中，并与应的单元格进行绑定。
其中，无论是表身文本属性还是表头文本属性，都可以包括文本的位置属性，位置属性可以指示文本在单元格中是居中、居左、居右、居上、居下等属性。由此，在一种可选的示例中，还可以基于位置属性，确定每个单元格中文本的位置坐标。
具体而言，对每个单元格而言，由于得到每个单元格的位置坐标，因此可以以单元格的位置坐标为准，基于该单元格的位置属性，计算该单元格中文本所在位置的位置坐标，该位置坐标作为单元格的一种参数。
当事项列表模板绘制完成后，可以将事项列表模板导出为对象简谱JSON(JavaScript Object Notation，JS对象简谱)类型的数据后，上传至服务器。由此，服务器可以在生成事项列表时，将各个事项信息添加到JSON类型的数据的对应位置中，从而得到JSON类型的待渲染数据，进而将该JSON类型的待渲染数据发送给服务器，在终端侧，可以基于JSON类型的待渲染数据，渲染出事项列表。
参照图7所示，示出了在会议预约场景下如何得到会议列表模板(对应事项列表模板)的整体流程示意图，如图7所示，具体可以包括以下流程：
首先，在模板设置界面上选中会议列表组件，若已经绘图画布，则直接拖拽单元格组件到绘图画布，若没有绘图画布，则需要新建绘图画布。
接着，在表格配置项中输入表格属性参数和表头文本属性(图7中的配置信息)，根据表格属性参数计算表格的行数、列数和字体样式。
之后，将鼠标点击单元格组件并在绘图画布上拖拽，松开单元格组件从而渲染出表格。
接着，完成对表头文本属性、表身文本属性和表头的文本的输入，从而完成对表格组件样式的配置。
最后，点击导出控件，导出为JSON格式的会议列表模板，同步到后端(服务器)，最终由服务器下发给终端。
其中，在一种实施例中，在绘制得到事项列表模板的过程中，可能需要频繁的修改和编辑，这时，撤销/恢复便显得尤为必要，以方便用户进行事项列表模板的修改。
相关技术中，在Canvas提供的绘图界面中绘制事项列表模板时，基于Canvas的绘图界面对撤销/恢复的支持度不高。有鉴于此，发明人将fabric.js开源库移植到基于Canvas的绘图库中，以利用其画布上内容的导出和导入方法，实现“撤销/恢复”功能。
其总体实现思路如下：首先，维护一个撤销恢复的数据集和表示当前所在索引的指针；当画布上以及画布中的编辑区域的数据修改之后，导出其数据内容，当执行撤销恢复操作时，能够监听到数据对象发生变化，导入数据恢复画布上的内容。
具体地，在一种实施例中，在获取所绘制的事项列表模板的步骤之前，可以对模板设置界面上发生的每个绘制操作，记录该绘制操作下产生的模板元素，并响应于触发的撤销/恢复操作，将记录的各个模板元素中，与撤销/恢复操作对应的目标模板元素渲染至绘图画布。
其中，一个模板元素表征一次修改后的事项列表模板；绘制操作包括但不限于以下任一者：对事项列表模板中的图形的绘制操作、表格属性参数的编辑操作。
本实施例中，每一个绘制操作都可以理解为一个数据修改操作，其包括了对画布上的图形的绘制操作，以及编辑区域的文本的编辑操作，表格属性参数的编辑操作可以包括：表格配置项中的表格属性参数的修改操作、表头文本属性和表身文本属性的修改操作、表头文本的修改操作。其中，图形的 绘制操作可以是指：单元格组件的绘制，如对单元格组件的样式的选择操作、单元格组件的缩放操作等。
本实施例中，当编辑区内(包括绘图画布和表格配置项等配置栏)的元素发生变化，比如用户新增一个图形控件、移动图形位置、修改图形的属性，便会针对每个绘制操作，可以将绘制操作完成时画布上的内容导出，作为一个模板元素，该模板元素可以近似理解为是一个未完成的事项列表模板，即只要用户未点击上传事项列表模板，则之前的每次绘制操作都对应一个版本的事项列表模板，每个版本的事项列表模板称为一个模板元素。
示例地，一次绘制操作是：表格属性参数中将表格的高度由220mm(毫米)修改为210mm，则针对该次修改，会导出画布上的全部数据内容，导出的数据内容可以为一个事项列表模板，该事项列表模板的高度为210mm，而修改之前导出的模板元数中表格的高度为210mm。
当模板设置界面上触发了撤销/恢复操作时，可以从存储的多个模板元素中，选取出对应的目标模板元素渲染至绘图画布。具体而言，可以使用fabric.js提供的导入画布内容的方法，如Canvas.loadFromJSON(CanvasData)，即可恢复绘图画布的内容。
其中，撤销/恢复中的撤销可以是指：用户想要恢复到修改前的数据状态，恢复可以是指：用户返回到某一次修改的数据状态后，又要恢复到再下一次修改的数据状态。
例如，第n次修改时，用户将表格的高度由220mm修改为210mm，第n+1次修改时，由210mm修改到200mm，第n+2次修改时，由210mm修改到215mm，则撤销可以是指用户在第n+2次修改时，想恢复到第n次修改的状态，恢复可以是指：用户返回到第n次修改的状态时，想恢复到第n+1次修改或第n+2次修改的状态。也可以看出，恢复操作是在撤销操作的基础上进行的。
其中，在将记录的各个模板元素中，与撤销/恢复操作对应的目标模板元素渲染至绘图画布时，可以基于操作步长确定目标模板元素。具体地，可以确定撤销/恢复操作的操作步长；基于操作步长，自最后一次记录的模板元素开始查找与操作步长对应的目标模板元素，并将该目标模板元素渲染至绘图画布；其中，所述操作步长包括撤销类型的步长和撤销类型的步长。
如上实施例所述，恢复操作是在撤销操作的基础上进行的，因此，操作步长可以包括撤销类型的步长和恢复类型的步长，其中，撤销类型的步长针对的是撤销操作，又可以理解为是后退类型的步长，恢复类型的步长针对的是恢复操作，又可以理解为是前进类型的步长。
在一种可选的实施例中，当执行撤销操作时，可以从最后一次记录的模板元素开始，根据撤销操作的操作步长，例如点击后退类型的撤销控件的次数(后退类型的操作步长)，确定出目标模板元素；当用户执行恢复操作时，可以从撤销操作对应的目标模板元素与最后一次记录的模板元素之间，根据恢复操作的操作步长，例如点击前进类型的撤销控件的次数(前景类型的操作步长)确定出最终的目标模板元素。
在一种可选的实施例中，可以维护一个全局状态对象，从而将模板元素保存至全局状态对象中。具体实施时，可以创建与绘图画布对应的全局状态对象；并在每记录一个模板元素时，将该模板元素以及该模板元素对应的操作步数记录到所述全局状态对象中；操作步数表征该模板元素对应的绘制操作。
当然，若在维护有全局状态对象的情况下，可以基于操作步长，从全局状态对象中查找操作步数与操作步长相对应的模板元素。
其中，全局状态对象包括用于记录模板元素的数组StepArr；以及记录操作步数的Current，操作步数可以表征模板元素是在第几次绘制操作下得到的，用于表征绘制操作的总次数；用于记录撤销/恢复操作的操作步长的stepLength；用于记录当前绘图画布上的数据的CanvasData，其是指待更新的页面数据，是一个JSON格式的字符串；每次执行撤销/恢复操作，会从数组中StepArr取出相应模板元素，更新该数据对象。
其中，当检测到每一个绘制操作时，可以将该绘制操作对应的模板元素记录到全局状态对象的数组中。
在一种实施例中，在全局状态对象中各个模板元素可以按照操作步数的顺序排列，如此，为提高从数组中查找出目标模板元素的准确性，可以在每一次撤销/恢复操作中，确定出目标模板元素时，若目标模板元素不为记录的最后一个模板元素，则删除自目标模板元素之后的模板元素。相应地，在每记录一个模板元素时，可以将该模板元素以及该模板元素对应的操作步数记 录到全局状态对象中的过程中，可以将该模板元素追加至模板元素的队列尾部中，并更新该模板元素的操作步数。
示例地，第n次修改时，用户将表格的高度由220mm修改为210mm，第n+1次修改时，由210mm修改到200mm，第n+2次修改时，由210mm修改到215mm，撤销操作指示在第n+2次修改时，恢复到第n次修改的状态，并点击保存时(表示不想要第n+1次修改和第n+2次修改)，则全局状态对象中删除第n+1次修改和第n+2次修改，在第n+3次修改时，将表格的高度修改为208mm，再将第n+3次修改后的数据添加到第n次修改的数据之后，作为新的第n+1次的模板元素，则全局状态对象中绘制操作的操作步数由第n+3次修改为第n+1。
此种情况下，若用户在第n+3次修改后，希望恢复到表格高度210mm的时候，即第n次修改的数据，则撤销的操作步长是1，而在全局状态对象中从最后一个模板元素向前数1个，即得到操作步数是第n次对应的数据，即表格的高度为210mm。
采用此种实施方式时，由于将撤销/恢复操作所定位的目标模板元素之后的数据删除，这样，可以及时删除数据，释放全局状态对象的存储空间，同时，对全局状态对象的操作步数进行更新，可以保证后续的撤销/恢复操作的操作步长，与全局状态对象中维护的每个模板元素的操作步数的正确对应，提高查找出的目标模板元素的准确性。
相应地，在有一种可选的实施例中，可以在全局状态对象的模板元素的数量超过目标数量时，删除排列在前的模板元素。
具体实施时，追加全局状态对象的模板元素后，如果追加模板元素之后的数组大小已经超出了最大步数，即目标数量，则需要排列在删除最前面的一个元素，即按照先入先出的原则，删除全局状态对象中的模板元素。
当然，针对恢复操作，若恢复操作的操作步长已经指向最后一个模板元素，则不再移动，并在绘图画布上提示已经是最后一步。
如上所述，可以将事项列表模板导出为对象简谱JSON类型的数据后，上传至服务器，其中，可以在对模板设置界面上发生的每个绘制操作进行记录时，将对应的模板元素进行快照。在撤销/恢复时，可以提取出对应的快照，进而基于该快照，进行模板元素的恢复。
具体实施时，可以对所述模板设置界面上发生的每个所述绘制操作，将绘图画布上的当前内容导出为JSON格式的数据；并将所导出的JSON格式的数据进行快照，以作为记录的模板元素。
如此，在将目标模板元素渲染至绘图画布时，可以将对应的目标模板元素的JSON格式的数据导入到绘图画布上，以在绘图画布上显示该模板元素对应的事项列表模板。
采用本客户端的实施方式，使用数据快照式的实现思想，可以维护一个撤销恢复的模板元素集和表示当前所在操作步数的指针，以帮助定位到对应的模板元素；针对每个绘制操作，可以导出绘图画布上的内容为一个JSON格式的数据；当执行撤销/恢复操作时，导入对应的JSON格式的数据恢复画布上的内容，由于以JSON格式的数据作为快照，以恢复绘图画布上的内容，因此，可以提高撤销/恢复的便捷性。
基于相同的发明构思，本公开还提供了一种信息处理系统，参照图8所示，示出了信息处理系统的框架示意图，如图8所示，包括：
客户端，用于向服务器发送多个事项信息；每个所述事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于触发所述服务器更新终端上显示的事项列表，所述事项列表中包括正发生和/或待发生的事项的事项信息；
服务器，用于在触发当前待触发的第一定时任务之前，确定下一个待触发的第二定时任务；并基于所述发生时段的先后顺序，以及所述第一定时任务与所述第二定时任务的触发时点的时间间隔，在所述第一定时任务和所述第二定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表；
终端，用于基于所述服务器发送的事项列表，对当前显示的事项列表进行刷新。
其中，服务器可以用于执行上述服务器侧实施例所述的信息处理方法，客户端可以用于执行上述客户端侧实施例所述的信息处理方法。其中，可以包括多个终端和多个显示设备，显示设备可以是电子桌牌，终端可以是电子门牌，当然，还可以包括其他类型的终端，如大尺寸显示屏等。
下面，对信息处理系统的实际应用过程进行说明：
第一步：模板设计用户登录客户端，使用客户端提供的基于Canvas的绘图库进行事项列表模板的设计，Canvas的绘图库采用fabric.js开源库。
第二步：模板设计用户在模板设置界面上选中会议列表组件，选中一种样式的单元格组件拖拽到绘图画布中，然后在配置栏中录入表格属性参数、表头文本、表头文本属性以及表身文本属性；
第三步：客户端响应于用户在绘图画布上对单元格组件的拖住移动的操作，基于用户选中的单元格组件、表格属性参数、表头文本、表头文本属性以及表身文本属性，批量生成多个单元格，从而得到表格。
在第二步和第三步的过程中，客户端会记录用户的每一步绘制操作，将每一步绘制绘制下的模板元素进行快照保存，当检测到用户的撤销/恢复操作中，从保存的快照中确定出目标快照，然后将目标快照导入到绘图画布上，以方便用户对涉及的会议列表模板的编辑。
第四步：客户端响应于用户的确定操作，将当前绘图画布上的数据导出为JSON格式的列表数据，然后上传到服务器。JSON格式的列表数据即为会议列表模板。
其中，模板设计用户可以基于第一步至第四步的过程，绘制多种不同样式的会议列表模板，供会议预约用户选择和使用。
第五步，会议预约用户登录客户端，进入会议预约界面，录入会议预约信息、选择触发时点设置策略以及在提供的几种已绘制的会议列表模板中选择一个会议列表模板；客户端将用户输入的会议预约信息、选中的触发时点设置策略和会议列表模板发送到服务器。
第六步，服务器根据议预约信息、选中的触发时点设置策略，生成会议预约信息的定时任务，从而确定了定时任务的触发时点。
第七步：服务器基于定时任务的触发时点，对终端上显示的会议列表进行更新，其具体过程可以详见上述服务器侧的示例性说明，在此不再赘述。
本实施例还提供了一种电子设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行时实现所述的信息处理方法。
本公开还提供了一种非瞬态计算机可读存储介质，其存储的计算机程序使得处理器执行所述的信息处理方法。
对于信息处理系统实施例而言，由于其与信息处理方法实施例基本相似，所以描述的比较简单，相关之处参见信息处理方法实施例的部分说明即可。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
基于相同的发明构思，本申请是提出了一种应用于服务器侧的信息处理装置，所述装置包括以下模块：
信息接收模块，用于接收客户端发送的多条事项信息，每条事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发所述服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；
定时触发模块，用于在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；
列表更新模块，用于基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
可选地，列表更新模块，包括：
第一确定单元，用于若所述触发时点间隔大于第一预设阈值，则确定所述当前待触发的定时任务和所述下一个待触发的定时任务均为所述目标定时任务；
第二确定单元，用于若所述触发时点间隔不大于所述第一预设阈值，则确定所述当前待触发的定时任务和所述下一个待触发的定时任务中，发生时段较晚的为所述目标定时任务。
可选地，所述装置还包括：
间隔时长确定模块，用于若所述触发时点间隔大于或等于第二预设阈值，则确定第一发生时段和第二发生时段之间的间隔时长；所述第一发生时段为所述当前待触发的定时任务对应的事项的发生时段，所述第二发生时段为所述下一个待触发的定时任务对应的事项的发生时段；
空闲信息生成模块，用于在所述间隔时长大于或等于目标间隔时长的情况下，基于所述第一发生时段和所述第二发生时段，生成事项空闲信息；所 述事项空闲信息用于指示所述第一发生时段与所述第二发生时段之间的时段可被预约；
空闲信息发送模块，用于将所述事项空闲信息添加至所述终端上显示的事项列表中，以在所述事项列表中展示可被预约的时段。
可选地，所述事项列表是通过以下步骤生成的：
接收所述客户端发送的事项列表模板；
基于所述事项列表模板、所述正发生和/或待发生的事项的事项信息，生成所述事项列表。
可选地，所述列表更新模块，包括：
信息获取单元，用于在所述目标定时任务的触发时点，获取所述目标定时任务对应的第一事项信息，以及第二事项信息，其中，所述第二事项信息的发生时段位于所述目标定时任务对应的事项信息的发生时段之后；
状态更新单元，用于对所述第一事项信息的状态和所述第二事项信息的状态进行更新，其中，所述状态包括正发生状态、未发生状态；
列表生成单元，用于基于所述第一事项信息和所述第二事项信息，以及各自更新后的状态，生成新的事项列表；
列表发送单元，用于将所述新的事项列表发送给所述终端，以更新所述终端上显示的事项列表。
可选地，所述装置还包括：
信息更新检测模块，用于在检测到多个所述事项信息中的任一第三事项信息被更新时，基于更新后的第三事项信息和所述终端上当前显示的事项列表，生成对应的更新后事项列表；
信息更新发送模块，用于将所述更新后事项列表发送给所述终端，以使所述终端对所显示的事项列表进行刷新。
可选地，每条事项信息对应的定时任务的触发时点是依据该条事项信息的发生时段确定的；所述装置还包括：
触发时点更新模块，用于在检测到多个所述事项信息中的任一第四事项信息的发生时段被更新时，依据更新后的发生时段，对所述第四事项信息对应的定时任务的触发时点进行更新。
可选地，包括多个所述终端，所述装置还包括：
性能参数获取模块，用于接收多个所述终端各自发送的当前性能参数，所述当前性能参数包括但不限于剩余电量、信号强度中的至少一者；
列表更新模块，具体用于在所述目标定时任务的触发时点，更新目标终端上所显示的事项列表；其中，所述目标终端的当前性能参数大于或等于目标性能参数。
基于相同的发明构思，本申请是提出了一种应用于客户端侧的信息处理装置，所述装置包括以下模块：
事项信息接收模块，用于响应于在事项预约界面上进行的事项录入，获取录入的事项信息；其中，所述事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；
信息发送模块，用于向所述服务器发送所述事项信息，以使所述服务器在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；并基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
可选地，所述装置还包括：
事项列表获取模块，用于响应于在模板设置界面上进行的事项列表模板的绘制完成操作，获取所绘制的事项列表模板；
导出模块，用于将所述事项列表模板导出为对象简谱JSON类型的数据后，上传至所述服务器，使所述服务器基于所述事项列表模板、以及所述正发生和/或待发生的事项的事项信息，生成所述事项列表。
可选地，所述模板设置界面包括表格配置项，所述事项列表获取模块，包括：
表格生成单元，用于响应于在所述表格配置项中输入的表格属性参数，生成表格，所述表格属性参数包括表格尺寸、行数和列数的至少一种；
第一文本属性获取单元，用于接收在所述表格配置项中对作为表头的单元格输入的文本，以及所述文本的表头文本属性；
模板生成单元，用于基于所述表头文本属性，将对应的文本添加至所述 作为表头的单元格，得到所述事项列表模板。
可选地，所述装置还包括：
第二文本属性获取单元，用于接收在所述表格配置项中对非表头的单元格输入的表身文本属性；
所述模板生成单元，具体用于基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，并将所述表身文本属性与对应的单元格进行绑定，得到所述事项列表模板。
可选地，所述表格生成单元包括：
坐标系获取子单元，用于响应于在所述表格配置项中输入的表格属性参数，获取待显示的显示屏的表格坐标系；
位置坐标确定子单元，用于基于所述表格属性参数和所述表格坐标系，确定每个单元格在所述表格坐标系中的位置坐标；
表格生成子单元，用于基于每个单元格在所述表格坐标系中的位置坐标，生成所述表格。
可选地，所述模板设置界面包括绘图画布，所述装置还包括：
数据记录模块，用于对所述模板设置界面上发生的每个绘制操作，记录该绘制操作下产生的模板元素，一个模板元素表征一次修改后的事项列表模板；所述绘制操作包括但不限于以下任一者：对所述事项列表模板中的图形的绘制操作、表格属性参数的编辑操作；
数据恢复模块，用于响应于触发的撤销/恢复操作，将记录的各个模板元素中，与所述撤销/恢复操作对应的目标模板元素渲染至所述绘图画布。
可选地，所述数据记录模块，包括：
导出单元，用于对所述模板设置界面上发生的每个所述绘制操作，将所述绘图画布上的当前内容导出为JSON格式的数据；
快照单元，用于将所导出的JSON格式的数据进行快照，以作为记录的所述模板元素。
可选地，所述数据恢复模块，包括：
操作步长确定单元，用于确定所述撤销/恢复操作的操作步长；
元素查找单元，用于基于所述操作步长，自最后一次记录的模板元素开始查找与所述操作步长对应的目标模板元素，并将该目标模板元素渲染至所 述绘图画布；其中，所述操作步长包括撤销类型的步长和恢复类型的步长。
可选地，所述装置还包括：
对象创建模块，用于创建与所述绘图画布对应的全局状态对象；
记录模块，用于在每记录一个所述模板元素时，将该模板元素以及该模板元素对应的操作步数记录到所述全局状态对象中；所述操作步数用于指示该模板元素对应的绘制操作；
所述元素查找单元，具体用于基于所述操作步长，从所述全局状态对象中查找操作步数与所述操作步长相对应的模板元素。
可选对，所述装置还包括：
删除模块，用于在所述目标模板元素不为记录的最后一个模板元素的情况下，删除中自所述目标模板元素之后的模板元素；和/或在所述全局状态对象的模板元素的数量超过目标数量时，删除排列在前的模板元素；
记录模块，具体用于在每记录到一个模板元素时，将该模板元素追加至所述模板元素的队列尾部中，并更新该模板元素的操作步数。
其中，信息处理装置实施例与信息处理方法实施例的具体实现过程类似，其参照上述信息处理方法实施例的过程即可，在此不再赘述。
最后，还需要说明的是，除非另外定义，在本文中使用的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。
以上对本公开所提供的一种信息处理方法、信息处理系统及电子设备进行了详细介绍，本文中应用了具体个例对本公开的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本公开的方法及其核心思想；同时，对于本领域的一般技术人员，依据本公开的思想，在具体实施方式及应用范 围上均会有改变之处，综上所述，本说明书内容不应理解为对本公开的限制。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。
本文中所称的“一个实施例”、“实施例”或者“一个或者多个实施例”意味着，结合实施例描述的特定特征、结构或者特性包括在本公开的至少一个实施例中。此外，请注意，这里“在一个实施例中”的词语例子不一定全指同一个实施例。
在此处所提供的说明书中，说明了大量具体细节。然而，能够理解，本公开的实施例可以在没有这些具体细节的情况下被实践。在一些实例中，并未详细示出公知的方法、结构和技术，以便不模糊对本说明书的理解。
在权利要求中，不应将位于括号之间的任何参考符号构造成对权利要求的限制。单词“包含”不排除存在未列在权利要求中的元件或步骤。位于元件之前的单词“一”或“一个”不排除存在多个这样的元件。本公开可以借助于包括有若干不同元件的硬件以及借助于适当编程的计算机来实现。在列举了若干装置的单元权利要求中，这些装置中的若干个可以是通过同一个硬件项来具体体现。单词第一、第二、以及第三等的使用不表示任何顺序。可将这些单词解释为名称。
最后应说明的是：以上实施例仅用以说明本公开的技术方案，而非对其限制；尽管参照前述实施例对本公开进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本公开各实施例技术方案的精神和范围。

Claims (21)

  1. 一种信息处理方法，其特征在于，应用于服务器，所述方法包括：
    接收客户端发送的多条事项信息，每条事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发所述服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；
    在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；
    基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
  2. 根据权利要求1所述的方法，其特征在于，基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，包括：
    若所述触发时点间隔大于第一预设阈值，则确定所述当前待触发的定时任务和所述下一个待触发的定时任务均为所述目标定时任务；
    若所述触发时点间隔不大于所述第一预设阈值，则确定所述当前待触发的定时任务和所述下一个待触发的定时任务中，发生时段较晚的为所述目标定时任务。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    若所述触发时点间隔大于或等于第二预设阈值，则确定第一发生时段和第二发生时段之间的间隔时长；所述第一发生时段为所述当前待触发的定时任务对应的事项的发生时段，所述第二发生时段为所述下一个待触发的定时任务对应的事项的发生时段；
    在所述间隔时长大于或等于目标间隔时长的情况下，基于所述第一发生时段和所述第二发生时段，生成事项空闲信息；所述事项空闲信息用于指示所述第一发生时段与所述第二发生时段之间的时段可被预约；
    将所述事项空闲信息添加至所述终端上显示的事项列表中，以在所述事项列表中展示可被预约的时段。
  4. 根据权利要求1所述的方法，其特征在于，所述事项列表是通过以下步骤生成的：
    接收所述客户端发送的事项列表模板；
    基于所述事项列表模板、所述正发生和/或待发生的事项的事项信息，生成所述事项列表。
  5. 根据权利要求1-4任一所述的方法，其特征在于，所述在所述目标定时任务的触发时点，更新所述终端上显示的事项列表的步骤，包括：
    在所述目标定时任务的触发时点，获取所述目标定时任务对应的第一事项信息，以及第二事项信息，其中，所述第二事项信息的发生时段位于所述目标定时任务对应的事项信息的发生时段之后；
    对所述第一事项信息的状态和所述第二事项信息的状态进行更新，其中，所述状态包括正发生状态、未发生状态；
    基于所述第一事项信息和所述第二事项信息，以及各自更新后的状态，生成新的事项列表；
    将所述新的事项列表发送给所述终端，以更新所述终端上显示的事项列表。
  6. 根据权利要求1所述的方法，其特征在于，在所述目标定时任务的触发时点，更新所述终端上当前显示的事项列表的步骤之后，所述方法还包括：
    在检测到多个所述事项信息中的任一第三事项信息被更新时，基于更新后的第三事项信息和所述终端上当前显示的事项列表，生成对应的更新后事项列表；
    将所述更新后事项列表发送给所述终端，以使所述终端对所显示的事项列表进行刷新。
  7. 根据权利要求1所述的方法，其特征在于，每条事项信息对应的定时任务的触发时点是依据该条事项信息的发生时段确定的；所述方法还包括：
    在检测到多个所述事项信息中的任一第四事项信息的发生时段被更新时，依据更新后的发生时段，对所述第四事项信息对应的定时任务的触发时点进行更新。
  8. 根据权利要求1所述的方法，其特征在于，包括多个所述终端，所 述方法还包括：
    接收多个所述终端各自发送的当前性能参数，所述当前性能参数包括但不限于剩余电量、信号强度中的至少一者；
    所述在所述目标定时任务的触发时点，更新所述终端上显示的事项列表的步骤，包括：
    在所述目标定时任务的触发时点，更新目标终端上所显示的事项列表；其中，所述目标终端的当前性能参数大于或等于目标性能参数。
  9. 一种信息处理方法，其特征在于，应用于客户端，所述方法包括：
    响应于在事项预约界面上进行的事项录入，获取录入的事项信息；其中，所述事项信息包括事项的发生时段以及对应的定时任务；所述定时任务用于在触发时点触发服务器更新终端上显示的事项列表，所述事项列表包括正发生和/或待发生的事项的事项信息；
    向所述服务器发送所述事项信息，以使所述服务器在触发当前待触发的定时任务之前，确定当前待触发的定时任务与下一个待触发的定时任务之间的触发时点间隔；并基于所述触发时点间隔和所述发生时段的先后顺序，从当前待触发的定时任务和所述下一个待触发的定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表。
  10. 根据权利要求9所述的方法，其特征在于，在所述向所述服务器发送所述事项信息的步骤之前，所述方法还包括：
    响应于在模板设置界面上进行的事项列表模板的绘制完成操作，获取所绘制的事项列表模板；
    将所述事项列表模板导出为对象简谱JSON类型的数据后，上传至所述服务器，使所述服务器基于获取的所述事项列表模板、以及所述正发生和/或待发生的事项的事项信息，生成所述事项列表。
  11. 根据权利要求10所述的方法，其特征在于，所述模板设置界面包括表格配置项，所述响应于在模板设置界面上进行的事项列表模板的绘制操作，获取所绘制的事项列表模板的步骤，包括：
    响应于在所述表格配置项中输入的表格属性参数，生成表格，所述表格属性参数包括表格尺寸、行数和列数的至少一种；
    接收在所述表格配置项中对作为表头的单元格输入的文本，以及所述文 本的表头文本属性；
    基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，得到所述事项列表模板。
  12. 根据权利要求11所述的方法，其特征在于，在所述基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，得到所述事项列表模板的步骤之前，所述方法还包括：
    接收在所述表格配置项中对非表头的单元格输入的表身文本属性；
    基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，得到所述事项列表模板，包括：
    基于所述表头文本属性，将对应的文本添加至所述作为表头的单元格，并将所述表身文本属性与对应的单元格进行绑定，得到所述事项列表模板。
  13. 根据权利要求11所述的方法，其特征在于，所述响应于在所述表格配置项中输入的表格属性参数，生成表格的步骤，包括：
    响应于在所述表格配置项中输入的表格属性参数，获取待显示的显示屏的表格坐标系；
    基于所述表格属性参数和所述表格坐标系，确定每个单元格在所述表格坐标系中的位置坐标；
    基于每个单元格在所述表格坐标系中的位置坐标，生成所述表格。
  14. 根据权利要求10-13任一所述的方法，其特征在于，所述模板设置界面包括绘图画布，在所述响应于在模板设置界面上进行的事项列表模板的绘制完成操作，获取所绘制的事项列表模板的步骤之前，所述方法还包括：
    对所述模板设置界面上发生的每个绘制操作，记录该绘制操作下产生的模板元素，一个模板元素表征一次修改后的事项列表模板；所述绘制操作包括但不限于以下任一者：对所述事项列表模板中的图形的绘制操作、表格属性参数的编辑操作；
    响应于触发的撤销/恢复操作，将记录的各个模板元素中，与所述撤销/恢复操作对应的目标模板元素渲染至所述绘图画布。
  15. 根据权利要求14所述的方法，其特征在于，所述对所述模板设置界面上发生的每个所述绘制操作，记录该绘制操作下产生的模板元素的步骤，包括：
    对所述模板设置界面上发生的每个所述绘制操作，将所述绘图画布上的当前内容导出为JSON格式的数据；
    将所导出的JSON格式的数据进行快照，以作为记录的所述模板元素。
  16. 根据权利要求14或15所述的方法，其特征在于，所述响应于触发的撤销/恢复操作，将记录的各个模板元素中，与所述撤销/恢复操作对应的目标模板元素渲染至所述绘图画布的步骤，包括：
    确定所述撤销/恢复操作的操作步长；
    基于所述操作步长，自最后一次记录的模板元素开始查找与所述操作步长对应的目标模板元素，并将该目标模板元素渲染至所述绘图画布；其中，所述操作步长包括撤销类型的步长和恢复类型的步长。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    创建与所述绘图画布对应的全局状态对象；
    在每记录一个所述模板元素时，将该模板元素以及该模板元素对应的操作步数记录到所述全局状态对象中；所述操作步数用于指示该模板元素对应的绘制操作；
    基于所述操作步长，自最后一次记录的模板元素开始查找与所述操作步长对应的模板元素，包括：
    基于所述操作步长，从所述全局状态对象中查找操作步数与所述操作步长相对应的模板元素。
  18. 根据权利要求17所述的方法，其特征在于，在所述全局状态对象中各个所述模板元素按照操作步数的顺序排列，所述方法还包括：
    在所述目标模板元素不为记录的最后一个模板元素的情况下，删除中自所述目标模板元素之后的模板元素；和/或在所述全局状态对象的模板元素的数量超过目标数量时，删除排列在前的模板元素；
    在每记录一个所述模板元素时，将该模板元素以及该模板元素对应的操作步数记录到所述全局状态对象中，包括：
    在每记录到一个模板元素时，将该模板元素追加至所述模板元素的队列尾部中，并更新该模板元素的操作步数。
  19. 一种信息处理系统，其特征在于，包括：
    客户端，用于向服务器发送多个事项信息；每个所述事项信息包括事项 的发生时段以及对应的定时任务；所述定时任务用于触发所述服务器更新终端上显示的事项列表，所述事项列表中包括正发生和/或待发生的事项的事项信息；
    服务器，用于在触发当前待触发的第一定时任务之前，确定下一个待触发的第二定时任务；并基于所述发生时段的先后顺序，以及所述第一定时任务与所述第二定时任务的触发时点的时间间隔，在所述第一定时任务和所述第二定时任务中，确定目标定时任务，并在所述目标定时任务的触发时点，更新所述终端上显示的事项列表；
    终端，用于基于所述服务器发送的事项列表，对当前显示的事项列表进行刷新。
  20. 一种电子设备，其特征在于，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行时实现如权利要求1-8任一所述的信息处理方法或9-18任一所述的信息处理方法。
  21. 一种非瞬态计算机可读存储介质，其特征在于，其存储的计算机程序使得处理器执行如权利要求1-8任一所述的信息处理方法或9-18任一所述的信息处理方法。
PCT/CN2023/091593 2022-06-21 2023-04-28 信息处理方法、信息处理系统、电子设备及存储介质 WO2023246314A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210708156.XA CN115081419A (zh) 2022-06-21 2022-06-21 信息处理方法、信息处理系统、电子设备及存储介质
CN202210708156.X 2022-06-21

Publications (2)

Publication Number Publication Date
WO2023246314A1 true WO2023246314A1 (zh) 2023-12-28
WO2023246314A9 WO2023246314A9 (zh) 2024-03-28

Family

ID=83252569

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/091593 WO2023246314A1 (zh) 2022-06-21 2023-04-28 信息处理方法、信息处理系统、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN115081419A (zh)
WO (1) WO2023246314A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115081419A (zh) * 2022-06-21 2022-09-20 京东方科技集团股份有限公司 信息处理方法、信息处理系统、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140310045A1 (en) * 2013-04-16 2014-10-16 Go Daddy Operating Company, LLC Generating and Displaying a Calendar Event Recurrence Preview
CN107015849A (zh) * 2017-04-07 2017-08-04 北京奇虎科技有限公司 定时任务的提醒方法及装置
CN110532081A (zh) * 2019-09-02 2019-12-03 政采云有限公司 一种定时任务处理方法及装置
CN111080229A (zh) * 2019-11-07 2020-04-28 视联动力信息技术股份有限公司 事项处理方法、装置、服务器、设备及可读存储介质
CN111290728A (zh) * 2020-01-21 2020-06-16 京东方科技集团股份有限公司 一种会议门牌管理系统和电子墨水屏会议门牌
CN115081419A (zh) * 2022-06-21 2022-09-20 京东方科技集团股份有限公司 信息处理方法、信息处理系统、电子设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140310045A1 (en) * 2013-04-16 2014-10-16 Go Daddy Operating Company, LLC Generating and Displaying a Calendar Event Recurrence Preview
CN107015849A (zh) * 2017-04-07 2017-08-04 北京奇虎科技有限公司 定时任务的提醒方法及装置
CN110532081A (zh) * 2019-09-02 2019-12-03 政采云有限公司 一种定时任务处理方法及装置
CN111080229A (zh) * 2019-11-07 2020-04-28 视联动力信息技术股份有限公司 事项处理方法、装置、服务器、设备及可读存储介质
CN111290728A (zh) * 2020-01-21 2020-06-16 京东方科技集团股份有限公司 一种会议门牌管理系统和电子墨水屏会议门牌
CN115081419A (zh) * 2022-06-21 2022-09-20 京东方科技集团股份有限公司 信息处理方法、信息处理系统、电子设备及存储介质

Also Published As

Publication number Publication date
CN115081419A (zh) 2022-09-20
WO2023246314A9 (zh) 2024-03-28

Similar Documents

Publication Publication Date Title
US9026935B1 (en) Application user interface with an interactive overlay
US8473571B2 (en) Synchronizing presentation states between multiple applications
US7987160B2 (en) Status tool to expose metadata read and write queues
US20220392365A1 (en) Interactive Oral Presentation Display System
US8527602B1 (en) Content upload system with preview and user demand based upload prioritization
JP6961993B2 (ja) デバイス上でのメッセージ管理とドキュメント生成のためのシステムと方法、メッセージの管理プログラム、モバイルデバイス
EP2741216A1 (en) Document collaboration method
US20150058053A1 (en) Shifting a group of tasks along a timeline
US10838972B2 (en) Storing service items in association with views
US11237848B2 (en) View playback to enhance collaboration and comments
CN111045999A (zh) 文档展示方法、装置、计算机设备及存储介质
US20140156597A1 (en) Recurring calendar item master and instance synchronization
WO2023246314A1 (zh) 信息处理方法、信息处理系统、电子设备及存储介质
DE202010018484U1 (de) System für die Bearbeitung eines Gesprächs in einem gehosteten Gesprächssystem
US9892105B2 (en) Systems and methods for annotating messages with reminders
US20140149896A1 (en) For-your-information events
US11875081B2 (en) Shared screen tools for collaboration
CN117149182B (zh) 一种前端页面的低耦合配置方法、介质及设备
WO2020000812A1 (zh) Ppt文档的生成方法及装置、存储介质、计算机设备
US20170237787A1 (en) Data system configurations for generating pages
US9942287B2 (en) Information processing system, terminal device, and method
US20180098031A1 (en) Video conferencing computer systems
US20220318755A1 (en) Systems and methods for adaptive curation of rendered digital assets within a virtual workspace in a collaboration system
US20240036927A1 (en) Method for processing workflow in combination with task, task processing method, and related device
US20230333962A1 (en) User feedback mechanism for software applications

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23825967

Country of ref document: EP

Kind code of ref document: A1