Plans to generate and demonstrate methods, apparatus, computing devices, and storage media
By fixing the calendar component in the chat page, the problem of separating the plan generation and viewing process is solved, realizing the continuous visibility of plan content and the continuity of chat interaction, thus improving the user's plan viewing efficiency and interaction efficiency.
Patent Information
- Application Number
- CN202611262620.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-19
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, separating the plan generation and viewing processes onto different pages results in lengthy operation paths, low interaction efficiency, and users need to frequently switch pages to complete plan creation and viewing.
A calendar component is permanently displayed on the dialogue page between the user and the target agent, allowing users to view the planned items for each date in the target plan. The calendar component is linked with the dialogue page to ensure that it is always visible, eliminating the need for users to switch between different pages.
It achieves continuous visibility of plan content and continuity of dialogue interaction, allowing users to check the plan schedule at any time during the conversation, improving the efficiency of plan information acquisition and interaction, and reducing information search costs and operation path length.
Smart Images

Figure CN123114609A_ABST
Abstract
Description
Technical Field
[0001] This specification relates to the field of computer technology, and in particular to methods, apparatus, computing devices, and storage media for generating and displaying plans. Background Technology
[0002] With the rapid development of artificial intelligence technology, intelligent dialogue systems have been widely applied in the fields of schedule management and planning. Users can interact with intelligent agents through natural language, which assist in the generation and management of various plans. After the plan is generated, clearly presenting the plan content to the user so that they can easily view the specific arrangements for each time point is one of the key aspects of improving the user experience. Summary of the Invention
[0003] In view of the above, embodiments of this specification provide a plan generation method. One or more embodiments of this specification also relate to a plan display method, a plan generation apparatus, a plan display apparatus, a computing device, a computer-readable storage medium, and a computer program product, to address the technical deficiencies existing in the prior art.
[0004] According to a first aspect of the embodiments of this specification, a plan generation method is provided, comprising: Displays the dialogue page with the target intelligent agent; In response to the completion of the creation of the target plan on the dialogue page, a calendar component is permanently displayed on the dialogue page; wherein, the target plan is created by the target agent based on the plan generation request received on the dialogue page; the calendar component is used to view the planned items corresponding to each date in the target plan.
[0005] According to a second aspect of the embodiments of this specification, a plan display method is provided, comprising: In response to entering a dialogue page with the target agent, the dialogue page displays target items matching the current date; wherein, the dialogue page includes a fixed-display calendar component, the target items belong to a target plan, the target plan is created by the target agent based on a plan generation request received on the dialogue page, and the calendar component is used to view the planned items corresponding to each date in the target plan; In response to a viewing action of the target item, the plan details page of the target plan is displayed.
[0006] According to a third aspect of the embodiments of this specification, a plan generation apparatus is provided, comprising: The dialogue module is configured to display a dialogue page with the target intelligent agent; The plan creation module is configured to display a calendar component on the dialogue page in response to the completion of the creation of a target plan on the dialogue page; wherein the target plan is created by the target agent based on a plan generation request received on the dialogue page; the calendar component is used to view the planned items corresponding to each date in the target plan.
[0007] According to a fourth aspect of the embodiments of this specification, a plan display device is provided, comprising: The dialogue module is configured to respond to entering a dialogue page with a target agent, and to display target items matching the current date on the dialogue page; wherein, the dialogue page includes a fixed-display calendar component, the target items belong to a target plan, the target plan is created by the target agent based on a plan generation request received on the dialogue page, and the calendar component is used to view the plan items corresponding to each date in the target plan; The plan display module is configured to display the plan details page of the target plan in response to a viewing operation of the target item.
[0008] According to a fifth aspect of the embodiments of this specification, a computing device is provided, comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the above-described plan generation method or the steps of the above-described plan display method.
[0009] According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, implement the steps of the above-described plan generation method or the steps of the above-described plan presentation method.
[0010] According to a seventh aspect of the embodiments of this specification, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the above-described plan generation method or the steps of the above-described plan presentation method.
[0011] This specification provides a plan generation method. After a user completes the creation of a target plan on a dialogue page with a target agent, a calendar component is fixedly displayed on the dialogue page, allowing the user to view the planned items corresponding to each date in the target plan through the calendar component. In this scheme, the fixed display ensures that the calendar component remains continuously visible on the dialogue page and does not disappear or collapse as the dialogue content scrolls. Since the calendar component is fixedly displayed on the dialogue page after the target agent completes plan creation, and the planned items corresponding to each date in the target plan are mapped to the date nodes of the calendar component, the calendar component becomes a continuously visible information anchor point on the dialogue page. Users do not need to switch between the dialogue page and an external calendar, nor do they need to browse historical message records. They can check the plan arrangements at any time while continuing subsequent dialogue with the target agent, thus achieving a unity of continuous visibility of plan content and coherence of dialogue interaction, simplifying the user's operation path between plan viewing and dialogue communication. Meanwhile, because the calendar component organizes and presents planned items by date in a visual way, users can more intuitively grasp the time distribution and schedule of the plan compared to plain text output, further improving the efficiency of obtaining plan information.
[0012] This specification provides a method for displaying plans. When entering a dialogue page with a target intelligent agent, a calendar component is always displayed on the dialogue page, and the system automatically filters the corresponding target items from the target plans according to the current date and displays them on the dialogue page; when the user performs a view operation on the target item, the system further displays the plan details page of the target plan. Based on the above solution, since the calendar component is permanently displayed on the chat page, and the system automatically matches and displays the corresponding target items from the target plan based on the current date when entering the page, a linkage is formed between the calendar component and the current date. The calendar component provides a visual framework for the time dimension, and the current date serves as the positioning anchor point within this framework. The combination of the two allows users to directly know the items that need to be performed on the current date on the chat page without having to manually browse the calendar to find the arrangements for the day, reducing the user's information search cost and improving information acquisition efficiency. At the same time, since the calendar component is permanently displayed on the chat page, and the display of target items works collaboratively with the calendar component based on the same time base (the current date), even if the user scrolls through the chat content or performs other operations, the association between the calendar component and the target items corresponding to the current date remains consistent. This ensures that the user can continuously obtain clear guidance on the day's plan without leaving the chat page, avoiding the loss of time anchor points and context fragmentation caused by page jumps or information scrolling in traditional solutions. Furthermore, after a user views the target item, the system displays a plan details page containing the complete plan content. The target item serves as the entry point from the overview to the details, forming a coherent navigation path with the plan details page. Users naturally transition from the overview information (target item) on the dialog page to the complete information on the details page without having to manually locate the current date in the calendar or search day by day. This achieves a seamless connection from the target item matched to the current date to the complete plan content, further improving the user's operational efficiency from plan overview to details. Attached Figure Description
[0013] Figure 1 A flowchart of a plan generation method according to an embodiment of this specification is shown; Figure 2 This is a schematic diagram illustrating a specific implementation of a method for fixing the calendar component on the dialog page, as provided in one embodiment of this specification. Figure 3 This is a schematic diagram illustrating a specific implementation method for the process of moving from the planned startup page to the return dialog page, as provided in one embodiment of this specification. Figure 4 A schematic diagram illustrating a specific implementation of creating a target plan according to an embodiment of this specification; Figure 5 This diagram illustrates the selection of a target and setting of a training frequency when creating a target plan, as provided in one embodiment of this specification. Figure 6 This is a schematic diagram illustrating a method for acquiring user motion data according to an embodiment of this specification; Figure 7 A flowchart illustrating a plan presentation method according to one embodiment of this specification is shown; Figure 8 A schematic diagram of a dialog page and a plan details page provided for one embodiment of this specification; Figure 9 A schematic diagram illustrating the display status of a plan details page provided in one embodiment of this specification; Figure 10 A schematic diagram illustrating the switching between weekly and monthly views in a plan details page provided in one embodiment of this specification; Figure 11 This is a schematic diagram illustrating the display status of an evaluation card provided in one embodiment of this specification. Figure 12 A flowchart of a plan generation method provided as an embodiment of this specification; Figure 13 A flowchart of a method for displaying planned data, provided as an embodiment of this specification; Figure 14 A schematic diagram of a plan generation device provided in one embodiment of this specification; Figure 15 A schematic diagram of a plan demonstration device provided in one embodiment of this specification; Figure 16 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation
[0014] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.
[0015] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.
[0016] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."
[0017] Furthermore, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of this specification are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.
[0018] First, the terms and concepts used in one or more embodiments of this specification will be explained.
[0019] An event is a specific action or change that occurs in a system or application. It can be triggered by the user (such as clicking a button or typing on the keyboard) or by the system (such as a timer expiring or a file download completing). Programs typically listen for these events and execute corresponding code when a specific event occurs.
[0020] A component is a simple encapsulation of data and methods, typically referring to a reusable software module. It can consist of multiple elements and possesses interactivity and independence. Components can be custom-defined or framework-based, used to build different parts of an application. Components are commonly used to construct different functional modules of an application, offering high reusability and flexibility. Components can encapsulate complex business logic and data management functions, reducing repetitive development work and improving development efficiency. Components can exist independently of the user interface, handling backend logic and data management.
[0021] Controls: In a computer user interface, a "control" is any element that a user can directly interact with. These elements allow users to input data, select options, or trigger certain actions. Controls can be graphical (such as buttons, text boxes, checkboxes, etc.) or more abstract (such as voice commands). Buttons are typically used to perform an action or open a new interface; text boxes allow users to input or edit text information; checkboxes represent a Boolean value (yes / no), which users can select or deselect; dropdown lists provide a list of options for users to choose from, usually displaying only one selected value; list boxes display multiple options, allowing users to select one or more items; labels display static text, usually used to explain the function of other controls, and can also be used as buttons; scrollbars allow users to navigate large datasets, such as browsing long documents or lists; images display static pictures and can sometimes be used as buttons; combo boxes combine the functionality of text boxes and dropdown lists, allowing users to both input text and select from a list. These controls are typically provided with standard styles by the operating system or development kit. Developers can customize their appearance and behavior as needed. Different operating systems and programming languages (such as Java, C#, Python, etc.) have their own set of controls and provide corresponding APIs to create and manage these controls.
[0022] "In response to" indicates the state in which a corresponding event occurs or a condition is met. The timing of subsequent actions performed in response to this event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is met. For example, in some cases, subsequent actions may be performed immediately when the event occurs or the condition is met; while in other cases, subsequent actions may be performed some time after the event occurs or the condition is met.
[0023] Triggered actions refer to actions or responses that are automatically executed when specific conditions or events occur. Triggered actions for controls mainly refer to events and behaviors triggered after a user interacts with UI controls (such as buttons, text boxes, drop-down menus, etc.). These triggered actions can include the following types: 1. Click event: The user clicks a button, link, or icon. 2. Mouse Over / Mouse Enter event: The mouse pointer moves over the control and hovers. 3. Input event: The user enters or modifies text in a text box. 4. Change event: The user changes the options in a drop-down menu or selection box. 5. Focus event: The control gains or loses input focus, etc.
[0024] This specification provides a plan generation method. One or more embodiments of this specification also relate to a plan display method, a plan generation apparatus, a plan display apparatus, a computing device, a computer-readable storage medium, and a computer program product, which will be described in detail in the following embodiments.
[0025] In existing plan generation solutions, users typically need to create a plan on a dedicated plan editing page, and then return to the homepage or list page to view the plan details. Because the plan creation process and the plan viewing process are separated into different pages, users need to frequently switch between multiple pages to complete the entire process of "creating a plan - viewing the plan's time distribution - starting execution," resulting in a lengthy operation path and low interaction efficiency.
[0026] This specification provides an embodiment of a plan generation method that can be applied to terminal devices (such as mobile phones, tablets, etc.). Through conversational interaction between a target intelligent agent (such as an AI assistant based on a large language model) and the user, it generates periodic plans such as training plans and displays a calendar component in a fixed position on the dialogue page, allowing the user to intuitively view the planned events for each date in the dialogue scenario, thereby improving interaction efficiency.
[0027] See Figure 1 , Figure 1 A flowchart of a plan generation method according to an embodiment of this specification is shown, which may specifically include the following steps.
[0028] Step 102: Display the dialogue page with the target agent.
[0029] The target intelligent agent can refer to a dialogue system built on artificial intelligence technology, which can understand the user's natural language input and respond accordingly, assisting the user in completing operations such as information retrieval, task execution, and plan generation. This target intelligent agent can be implemented using a large language model, or it can be implemented using a rule-based or retrieval-based dialogue system.
[0030] A dialogue page refers to the interface used to present the dialogue interactions between a user and a target intelligent agent. This page can display dialogue messages sent by the user, replies from the target intelligent agent, and various interactive cards or controls provided by the target intelligent agent. Users can enter text, voice, or perform clicks on this page to engage in multi-turn dialogues with the target intelligent agent.
[0031] In some embodiments, a user can launch an application via a terminal device (such as a mobile phone, tablet, wearable device, etc.) to enter a dialogue page with the target intelligent agent. This dialogue page can be presented as a conversation window between the user and the target intelligent agent, where the user can enter messages, and the target intelligent agent can reply based on the user's input.
[0032] In practical applications, when a user first enters the dialogue page, the target agent can proactively send a welcome message and guide the user to input a plan generation request. The user can initiate the plan generation request by entering a text message (such as "Generate a running plan for me") in the input box on the dialogue page.
[0033] Step 104: In response to the completion of the creation of the target plan on the dialogue page, a calendar component is fixedly displayed on the dialogue page; wherein, the target plan is created by the target agent based on the plan generation request received on the dialogue page; the calendar component is used to view the planned items corresponding to each date in the target plan.
[0034] The calendar component refers to an interface element that displays planned tasks in a calendar format. This component can display a date grid, with each date's corresponding cell showing whether a planned task is scheduled for that date, or displaying a brief identifier for the planned task (such as a training intensity icon, task type icon, etc.). Users can quickly understand the overall distribution of their target plans on the timeline using this calendar component.
[0035] Fixed display refers to the state in which the calendar component remains visible within the chat page. In this state, the calendar component will not move out of the visible area or collapse as the user scrolls within the chat page; even if the chat content increases or the user scrolls up to view historical messages, the calendar component remains visible.
[0036] Planned items can refer to the specific arrangements corresponding to each date in the target plan. Taking a training plan as an example, planned items can include information such as training type (e.g., easy run, tempo run, long-distance run), training distance, training duration, and training intensity.
[0037] In practical applications, the calendar component is permanently displayed on the dialogue page, meaning it remains visible within the page's view area. As the user continues other dialogue operations with the target agent (such as sending messages, receiving replies, scrolling up to view historical messages), the calendar component remains at the top of the page or in another preset position, without disappearing or collapsing due to increased dialogue content or page scrolling. Users can view the overall schedule of the target plan at any time through this calendar component.
[0038] In some embodiments, the calendar component can also support interactive operations. For example, a user can click on a date in the calendar component to display details of planned activities for that date in a dialog page, or jump to a plan details page to view more complete plan content.
[0039] Based on some embodiments of this specification, since the calendar component is permanently displayed on the dialogue page after the target plan is created, it becomes a continuously visible information anchor point on the dialogue page. During subsequent use, users do not need to switch between the dialogue page and an external calendar application, nor do they need to browse historical message records. They can continue the dialogue with the target agent while simultaneously checking the planned items corresponding to each date in the target plan, thus balancing the continuous visibility of the plan content with the continuity of dialogue interaction. Furthermore, because the calendar component visually organizes and presents planned items by date, compared to plain text output, users can more intuitively grasp the overall distribution and progress of the target plan on the timeline, further improving the efficiency of obtaining plan information.
[0040] Some embodiments of this specification can be applied to scenarios requiring intelligent agents to assist in generating plans, such as sports training, learning plans, and work tasks. For example, users can use a dialogue page to interact with the target intelligent agent in natural language, allowing the target intelligent agent to guide the user in creating a training plan. After the plan is created, an overview tool of the plan's content is continuously displayed on the dialogue page, so that the user can review the plan at any time during subsequent conversations with the target intelligent agent.
[0041] In one optional implementation of this embodiment, the step of displaying the calendar component on the dialog page includes: in response to completing the creation of a target plan on the dialog page, displaying a plan overview card on the dialog page; in response to a trigger operation on the plan overview card, jumping to a plan launch page, the plan launch page displaying the planned items corresponding to each date in the target plan and including a plan activation control; in response to a trigger operation on the plan activation control, returning from the plan launch page to the dialog page, and displaying the calendar component on the dialog page.
[0042] The plan overview card refers to the interactive card displayed on the dialog page after the target plan is created. The plan overview card can contain core summary information of the target plan (such as total training volume, total training cycles, total number of training sessions, etc.), or it can include the name and brief description of the target plan, so that users can quickly understand the basic information of the plan before starting the plan.
[0043] In some embodiments, in addition to displaying the total training volume, total training cycles, and total number of training sessions, the plan overview card may also display information such as the plan's objective description, the user level to which the plan is applicable, and the plan's difficulty level. In other embodiments, the plan overview card may also include functional controls such as "Share Plan" and "Save Plan" to facilitate users in sharing the plan with other users or saving it locally.
[0044] A launch page can be a standalone page that appears after a user triggers the plan overview card. This launch page can be displayed above the dialog page (e.g., as a full-screen overlay or a half-screen pop-up) or it can redirect to a new page independent of the dialog page. The launch page can display detailed arrangements of the planned tasks for each date in the target plan, helping users fully understand the plan's content before officially launching it. The launch page also includes a plan activation control, which users can use to confirm the launch of the plan.
[0045] In some embodiments, the launch page can display the planned items corresponding to each date of the target plan in chronological order, with each date's planned items arranged in an itemized manner. Users can scroll to view all planned items. In other embodiments, the launch page can also display the planned items in groups according to the plan's phases. Planned items within the same phase are grouped together, and each group is separated by a phase title, allowing users to more clearly understand the structure of the plan.
[0046] A plan launch control refers to an operable control set in the plan launch page. User interaction with this control indicates confirmation of launching the target plan. In response to this interaction, the system can associate the target plan with the in-app calendar, and after the association is complete, return from the plan launch page to the dialog page, where the calendar component is permanently displayed.
[0047] In some embodiments, the calendar component can display a weekly calendar view of the week containing the current date, with each date's corresponding cell displaying a brief identifier of the planned activity for that date (such as training distance, training type, etc.). For example, if training is scheduled for a certain date, the corresponding training distance value (such as "3km") will be displayed in that date's cell; if a date is a rest day, the training identifier may not be displayed in that date's cell, or it may be identified as a rest day in a specific style.
[0048] In practical applications, when the calendar component is first displayed on the dialog page, it can default to the week containing the planned start date and distinguish between the current date and the planned start date (e.g., highlighting). In other embodiments, when the calendar component is first displayed, if the current date is within the planned time frame, the calendar component can default to the week containing the current date and display a specific visual identifier (e.g., highlighting or circle) on the current date to help users quickly locate their plans for the day.
[0049] In this embodiment, a step-by-step guidance chain between the plan overview card, the plan launch page, and the calendar component allows users to progress sequentially from browsing the plan overview, confirming details, to continuous review during the plan initiation process. This reduces the length of the user's operation path while ensuring the completeness of information presentation. Specifically, users can first quickly understand the core summary information of the plan through the plan overview card, then view the details of the planned items and the plan stages for each date through the plan launch page, and finally obtain a continuously visible plan overview tool through the calendar component in the dialog page. This achieves a smooth transition from information viewing and confirmation to continuous use during the plan initiation process.
[0050] The following description, in conjunction with the accompanying drawings, illustrates a specific implementation of the plan generation method provided in this specification, which involves the fixed display of a calendar component on a dialog page.
[0051] Figure 2 This is a schematic diagram illustrating a specific implementation method for fixing the calendar component on the dialog page, as provided in one embodiment of this specification.
[0052] In some embodiments, after the target agent completes the creation of the target plan on the dialog page, a plan overview card can be displayed on the dialog page. The plan overview card may include core summary information such as the name of the target plan, total training amount, total training period, and total number of training iterations, enabling users to quickly understand the basic information of the plan.
[0053] by Figure 2 For example, Figure 2 The left-hand page is the "Dialogue Page," where the target agent sends a message: "A personalized plan has been generated! You have some running experience. This plan won't push you too hard; instead, it will guide you step-by-step, based on your current running level. Click to see how to schedule your days." Below this message is a plan overview card titled "3km Introductory Plan," containing three core metrics: "25 Total Kilometers," "3 Training Weeks," and "12 Training Sessions." This plan overview card can be presented as a standalone card on the dialogue page, and users can click on it to view more detailed plan content. In some embodiments, the plan overview card may also include time information (such as start and end dates, plan phase divisions, etc.) or a description of the plan's goals (such as guiding text like "Build running awareness and establish a solid physical foundation").
[0054] In some embodiments, before sending the plan overview card, the target agent may also display a confirmation message about plan creation on the dialog page, informing the user that the plan has been created and prompting the user to view details or start the plan by clicking the plan overview card.
[0055] In some embodiments, a user can perform a trigger action on the plan overview card (such as clicking any area of the card), and the system responds to the trigger action by navigating to the plan launch page. This launch page can be displayed over the dialog page (such as popping up from the bottom of the page as a full-screen overlay), or it can navigate from the dialog page to a separate new page.
[0056] by Figure 2 For example, Figure 2 The top right page is the "Plan Launch Page," which displays the detailed arrangements of the planned items for each date in the target plan.
[0057] Specifically, the program's launch page may include the following functional modules: a program overview information area, a training type description card, a program preview area, and a program activation control.
[0058] Plan summary information area such as Figure 2As shown on the program's launch page, the top of the page displays the program name "3km Introductory Program," the overall program intensity information "Just Right," and the program's core metrics such as "25 Total Kilometers," "3 Training Weeks," and "12 Training Sessions."
[0059] Training type description card, such as Figure 2 As shown, this section displays descriptions of the different training types involved in the plan. For example, the page uses cards to illustrate four training types: "Easy Run," "Tempo Run," "Interval Run," and "Long Distance Run," explaining the intensity and heart rate zones for each type. These training type description cards help users understand the differences between the various training types before starting the plan, thus gaining a more comprehensive understanding of the plan's content. In some embodiments, the training type description cards can display more training types, or visual distinguishing elements such as difficulty indicators and color codes for each type, allowing users to quickly identify different types of training when executing the plan.
[0060] The plan preview area can include information on the plan's phase divisions and plan-related items. For example... Figure 2 As shown, the plan's phase division information includes descriptions displayed on the page such as "Phase 1: Running Recovery Week: Starting with a run-walk combination, the goal is to complete a 2km easy run...", "Phase 2: ...", "Phase 3: ...", etc., helping users understand the overall structure of the plan and the goals of each phase. Regarding plan items, for example, the page shows that the plan item for "March 9th / Monday" is "2km easy run, 26-minute pace 6'30"-6'50". Through the plan preview area, users can preview the overall plan and the specific arrangements for each date within the plan to determine if the plan meets their expectations.
[0061] Plan to enable controls such as Figure 2 As shown, a "Start Plan" control is located at the bottom of the page. Users can click this control to confirm the start of the target plan. In some embodiments, this control may also be displayed as "Confirm Start," "Start Plan," or other similar formats.
[0062] In some embodiments, after a user performs a trigger operation on the schedule start control in the schedule launch page, the system can close the schedule launch page, return to the dialog page from the schedule launch page, and display the calendar component in the dialog page.
[0063] by Figure 2For example, the bottom right page of the attached image is the "dialogue page" after returning, and a calendar component is always displayed at the top of this page. This calendar component can display a weekly calendar view of the week containing the current date, and the corresponding cells for each date can display a brief label of the planned tasks for that date. For example, in the attached image, the training distance information such as "2 km", "2.5 km", and "3 km" is marked below each date, allowing users to intuitively understand the training schedule for each day of the week.
[0064] Within this dialogue page, the target agent can also send messages to inform the user that the calendar component is now permanently displayed on the dialogue page, prompting the user to check their plans at any time using this calendar component, or guiding the user to the next step (such as "Would you like to try running 1 kilometer first? I'll adjust the plan for you more precisely based on the test data"). Users can continue their conversation with the target agent on this page, while simultaneously viewing the planned events for each date in the target plan through the permanently displayed calendar component at the top.
[0065] In some embodiments, the plan launch page may also include interactive functionality. For example, a user can click on a plan item for a specific date on the plan launch page, and the page can expand to display more details of that plan item (such as a detailed description of the training content, suggested pace range, precautions, etc.). As another example, a user can adjust a plan item on the plan launch page (such as modifying the training distance or training type for a specific date). After making the adjustment, clicking the activation control will allow the system to generate the final target plan based on the adjusted content.
[0066] Based on some embodiments of this specification, since the plan overview card is displayed on the dialog page immediately after the target plan is created, users can quickly understand the core summary information of the target plan through this card and make a preliminary judgment on whether the plan meets their needs without entering other pages; since the user jumps to the plan launch page after performing a trigger operation on the plan overview card, the plan launch page displays the detailed arrangement of the plan items corresponding to each date in the target plan and the plan stage division information, so that the user can fully understand the time distribution and stage arrangement of the plan before starting the plan, effectively reducing the risk of plan misjudgment due to information opacity; since the plan launch page also includes a training type description card, which displays the characteristic information such as exercise intensity and heart rate zone corresponding to different training types, users can understand the different training types involved in the plan in advance through this card, so as to more accurately understand the purpose and requirements of each training arrangement when executing the plan; since the user returns to the dialog page after performing a trigger operation on the plan start control, and the calendar component is fixedly displayed on the dialog page, the calendar component becomes a continuously visible time anchor point on the dialog page, and the user can check the overall time arrangement of the target plan at any time on the dialog page from the first moment of starting the plan. Overall, the progressively deeper, chain-like design, from the plan overview card (overview) to the plan launch page (details and confirmation) and then to the calendar component (fixed display), allows users to gradually understand, confirm, and use the plan during the plan launch process. This achieves a smooth transition from information viewing and plan confirmation to continuous review, improving the completeness of the plan launch process and the user experience.
[0067] In an optional implementation of this embodiment, the plan generation method further includes: in response to a trigger operation on the plan activation control, displaying a calendar synchronization request interface, the calendar synchronization request interface being used to request access permissions to an external calendar; and in response to an authorization operation on the calendar synchronization request interface, adding the planned items corresponding to each date in the target plan to the external calendar.
[0068] The calendar synchronization request interface refers to the interactive interface used to request access to an external calendar after the user confirms the start of a target plan. This interface can display explanatory information about the permission request (such as the benefits of synchronizing planned items to an external calendar, the scope of required permissions, etc.), and may also include entry points for granting and denying permissions. Users can understand this interface as a bridge between the system and the external calendar; through this interface, users can authorize the synchronization of planned items to the external calendar or choose to skip the synchronization.
[0069] An external calendar can refer to a calendar service or application that is independent of the current application, such as the calendar app that comes pre-installed on a mobile phone or a third-party calendar service. External calendars typically have functions such as schedule management and reminder notifications, and users may have already recorded work arrangements, life events, and other schedule information in the external calendar.
[0070] The authorization operation refers to the user's confirmation of permission to access the external calendar in the calendar synchronization request interface. After the user performs the authorization operation, the system obtains the corresponding permissions, thereby adding the planned items corresponding to each date in the target plan to the external calendar. In some embodiments, the user can grant "full access" permissions or "add only" permissions, and the scope of system operations corresponding to different permission levels may be different.
[0071] In some embodiments, after a user performs a trigger operation on the plan start control in the plan launch page, the system can first display the calendar synchronization request interface, and then determine the subsequent process based on the user's operation in the calendar synchronization request interface.
[0072] Figure 3 This is a schematic diagram illustrating a specific implementation method for the process of moving from the planned startup page to the return dialog page, as provided in one embodiment of this specification.
[0073] by Figure 3 Let's take an example to illustrate. Figure 3 The top-left page is the plan launch page. On this page, users can view the division and specific arrangements of each stage of the plan (e.g., "Stage 1: Running Recovery Week: Starting with a run-walk combination, aiming to complete a 2km easy run," "Stage 2: ...", "Stage 3: ...", etc.), confirm the details of the plan (e.g., "March 9th / Monday: 2km easy run, 26-minute pace 6'30"-6'50"), and after reading the training type description card, click the "Start Plan" control at the bottom of the page. In response to the "Start Plan" control, the system can display the calendar synchronization request interface.
[0074] like Figure 3 As shown in the upper right corner, the calendar synchronization request interface displays a "Sync to My Schedule" control. Users can use this control to trigger the synchronization process, adding planned events for each date in the target schedule to the external calendar. After the user clicks "Sync to My Schedule," the system can further display a permission request pop-up or a permission request page. Figure 3As shown in the lower left corner of the page, the pop-up window displays information about the permission request (e.g., "'APP X' needs full access to your calendar. It needs access to your calendar to synchronize your running training plan and intelligently recommend the best exercise time based on your available schedule," where "APP X" is the name of the current application), and displays permission options for the user to choose from. For example, the user can choose "Keep 'Add Only'" or "Allow Full Access." If the user chooses "Allow Full Access," the system will have full access to the external calendar, allowing it to add planned items for each date in the target plan to the external calendar and read existing schedule information in the user's external calendar for conflict detection and plan adjustments. If the user chooses "Keep 'Add Only'," the system will only have permission to add items to the external calendar and will not read existing schedule information.
[0075] After the user completes the authorization process, the system can add the scheduled items corresponding to each date in the target plan to an external calendar. In some embodiments, the specific implementation of adding scheduled items to the external calendar may include: the system calling the application programming interface of the external calendar to write each scheduled item into the external calendar as a schedule entry. Taking a training plan as an example, if a "2km easy run" is scheduled for a certain date in the target plan, the system can create a schedule entry for the corresponding date in the external calendar. The title of this schedule entry can be "2km easy run", the time period can be set to the planned execution time (such as "9:00-10:00"), and the reminder time can be set to a preset time earlier than the planned execution time (such as 30 minutes in advance). The system can set a reminder time for each scheduled item corresponding to each date. This reminder time can be earlier than the planned execution time of the scheduled item so that the user receives a ringing reminder before the schedule node. For example, if the planned execution time of a scheduled item is "9:00", the reminder time can be set to "8:30" or "8:45".
[0076] After the user completes the authorization process and returns to the chat page, as follows Figure 3 As shown in the lower right corner of the page, the calendar component is permanently displayed on the dialogue page. The target agent can send a message to inform the user that the calendar component is now permanently displayed on the dialogue page and prompt the user to check their schedules at any time using this calendar component. The specific display method of the calendar component can be found in the description of the preceding embodiments, and will not be repeated here. If the user refuses authorization or skips synchronization in the calendar synchronization request interface, the system can also directly return to the dialogue page and permanently display the calendar component, but will not perform the external calendar addition operation for planned items.
[0077] In some embodiments, after a user authorizes the calendar synchronization request interface, the system can first return to the dialog page and display the calendar component, while simultaneously performing the external calendar addition operation for the planned event asynchronously in the background. In other embodiments, the system can first complete the external calendar addition operation, confirm successful addition, and then return to the dialog page and display the calendar component.
[0078] In some embodiments, the calendar synchronization request interface may provide two options, "Allow" and "Deny," without distinguishing between "Full Access" and "Add Only." In other embodiments, the calendar synchronization request interface may provide multiple authorization levels for the user to choose from, such as "Full Access" (can read and write external calendars), "Add Only" (can only write events, cannot read existing schedules), and "Read Only" (can only read schedules, cannot write events). Different authorization levels correspond to different system operation scopes.
[0079] In some embodiments, the permission request pop-up may display a sample of the planned event (e.g., "Add the planned event to an external calendar, example: 'March 9th 2km easy run, 26-minute pace 6'30"-6'50"') to help users understand the specific content to be synced to the external calendar before making an authorization decision. In other embodiments, the permission request pop-up may not display a sample, but only inform the user of the purpose and scope of the permission request through text description.
[0080] Based on some embodiments of this specification, after the user clicks the plan start control on the plan launch page, the system displays a calendar synchronization request interface requesting access to an external calendar. This allows the user to select to synchronize the planned items to an external calendar while confirming the plan launch, achieving seamless integration of plan launch and calendar synchronization within the same process. This avoids the tedious operation of manually adding planned items one by one to the external calendar after the plan is launched. After the user grants authorization, the system automatically adds the planned items corresponding to each date in the target plan to the external calendar, allowing the user to view the plan simultaneously in the external calendar application they use daily, without having to switch repeatedly between multiple applications. While adding each planned item to the external calendar, the system can set a reminder time earlier than the planned execution time for each planned item, allowing the user to be informed of the day's arrangements in time through the reminder function of the external calendar before the planned items are executed, reducing the risk of missed plan execution due to forgetting or time conflicts.
[0081] In an optional implementation of this embodiment, the plan generation method further includes: obtaining the set schedule information from the external calendar; when the corresponding date of the schedule information arrives, if the execution period of the schedule information conflicts with the execution period of the planned item on the corresponding date, displaying plan confirmation information on the dialog page, the plan confirmation information being used to ask the user whether to execute or adjust the target planned item on the corresponding date in the target plan as scheduled.
[0082] The schedule information refers to schedules that users create themselves or that already exist in an external calendar. This schedule information can include the date, time, title, location, notes, and other details of the schedule.
[0083] Plan confirmation messages refer to interactive information displayed on the dialog page when external schedule information and target planned items are related in time. These messages can be used to ask users whether they want to execute the target planned item as originally planned, or whether adjustments to the plan are needed.
[0084] For example, after the system reads other schedule information created by the user in the external calendar through the application programming interface (API), if it detects a schedule that conflicts with the planned event on a certain day (e.g., a "9:00-10:00 AM meeting" is scheduled in the user's external calendar, while the target plan has a "9:00-10:00 AM 2km easy run" scheduled for that day), it displays a plan confirmation message on the dialog page. This message can inform the user that there is a time conflict between the planned event and the external schedule, and ask the user whether to adjust the execution time of the planned event. The user can directly reply with a confirmation message on the dialog page (e.g., "Execute as scheduled" or "Reschedule to the afternoon"), and the system determines whether to adjust the planned event for that date in the target plan based on the user's reply.
[0085] In some embodiments, when the system obtains the schedule information created by the user in the external calendar, if it detects that the user has other scheduled activities on a certain date, it can set the reminder time for the target planned event on that date to be earlier, so that the user has sufficient time to make arrangements. For example, if the user has multiple scheduled events in the external calendar on a certain day, the system can automatically adjust the reminder time for the planned events on that day from the usual 30 minutes in advance to 60 minutes in advance.
[0086] In some embodiments, when setting reminder times for planned events corresponding to each date, the system can use a default reminder time (e.g., 30 minutes in advance), or users can customize the reminder time advance in the plan launch page or plan details page. In other embodiments, users can set different reminder times for different types of planned events; for example, setting a reminder 60 minutes in advance for a long-distance run and a reminder 20 minutes in advance for an easy run.
[0087] In some embodiments, if the user's authorization level is "Full Access," the system can read existing schedule information in the user's external calendar and display a comparison view of the day's planned activities and the external schedule in the dialog page (e.g., displaying "Today's Plan: 5km Easy Run; Today's Schedule: 9:00-10:00 Meeting"). This allows the user to decide whether to execute the planned activities based on a full understanding of the day's arrangements, or to adjust the time and pace themselves when executing the plans. If the user's authorization level is "Add Only," the system may not perform the external calendar read operation. Accordingly, the plan confirmation information may not be automatically triggered by the system, or may be presented in other ways (e.g., manually confirmed by the user).
[0088] In some embodiments, after obtaining pre-set schedule information from an external calendar, the system may not display plan confirmation information but instead automatically adjust the scheduled items for the corresponding date in the target plan based on the schedule information. For example, if there are many scheduled events on a certain day in the external calendar, the system can automatically adjust the execution time of the scheduled items for that day to a free period and notify the user of the adjustment result in the dialog page. In other embodiments, the system only displays plan confirmation information when there is a time conflict between the scheduled item and the external schedule; if there is no conflict on that day, no additional information is displayed in the dialog page.
[0089] Based on some embodiments of this specification, since the system obtains the schedule information created by the user in the external calendar and displays the plan confirmation information on the dialog page when the corresponding date of the schedule information arrives, the target plan can be associated and linked with the existing schedules in the user's external calendar. The user does not need to manually compare the conflict relationship between the planned items and the external schedule. By establishing a correspondence between the external schedule and the planned items in the time dimension, the system can provide timely prompts when the user's plan execution may be affected by the external schedule, thereby improving the certainty of plan execution and the user's time management efficiency. At the same time, since the system only triggers the plan confirmation information on the date corresponding to the existing schedule in the external calendar, rather than uniformly querying all dates, the display of this information has a clear time trigger condition—that is, it is only triggered on the date when the user has arranged other things through the external calendar, avoiding unnecessary prompts on the date when there are no external schedules, and reducing information interference for the user. In addition, since the acquisition of schedule information and the display of plan confirmation information are based on the user's authorization operation through the calendar synchronization request interface, this dual authorization mechanism (first authorizing synchronization to the external calendar, and then controlling the reading scope through the authorization level when acquiring schedule information) can ensure the user's control over personal schedule data.
[0090] In one optional implementation of this embodiment, the step of creating the target plan on the dialog page includes: In response to receiving the plan generation request in the dialog page, a data collection card is displayed in the dialog page, and the data collection card displays a first data collection question and a first set of options corresponding to the first data collection question; In response to a selection operation for a first target option in the first set of options, a second data collection question and a second set of options corresponding to the second data collection question are displayed on the dialog page, the second data collection question being determined based on the first target option; In response to the completion of the data collection card, the creation of the target plan is completed based on the selection results of each data collection question within the data collection card.
[0091] The data collection card refers to an interactive card displayed on the dialog page used to collect user information. This card can sequentially display multiple data collection questions, each with several options for the user to choose from. By selecting options for each data collection question, the user provides the system with the basic data needed to generate the target plan.
[0092] In some embodiments, after a user initiates a plan generation request on the dialogue page, the target agent can guide the user to complete data collection through multi-turn dialogue.
[0093] Figure 4 This is a schematic diagram illustrating a specific implementation of the creation of a target plan according to an embodiment of this specification.
[0094] like Figure 4 As shown, Figure 4 The dialog page displays data collection cards. In some embodiments, the data collection cards may be displayed as individual cards on the dialog page, each card sequentially showing a data collection question and a set of options for each question. Figure 4 As shown, the data collection card can display the first data collection question (e.g., "When it comes to a single run, which sentence best describes you?"), and below this question, a set of corresponding options (e.g., "Run-walk combination, maximum 3 km", "Easy jogging, 3-5 km", "Advanced running, daily 5-10 km", etc.). Users can select a target option from the set of options. In response to a selection of the first target option from the first set of options, the data collection card can display a second data collection question and its corresponding second set of options. The second data collection question can be determined based on the first target option (e.g., if the user selected "Run-walk combination, maximum 3 km" for the first question, the second question could ask about the user's running mileage over the past month). Only one data collection question can be displayed at a time on the data collection card. After the user completes the selection for the current question, the card can dynamically update to display the next question. This continues until all data collection questions have been answered. Selected answers for each question can be displayed visually (e.g., highlighted or circled). After completing the selection of all questions, users can click the "Complete Filling" control at the bottom of the data collection card. In response to this operation, the system will complete the creation of the target plan based on the selection results of each data collection question in the data collection card.
[0095] In some embodiments, the display order of the data collection questions within the data collection card can be dynamically adjusted based on the user's selections. For example, if the user selects a higher-level option in the first question, the basic questions can be skipped, and the advanced questions can be presented directly. In other embodiments, the data collection card may also display progress indicators (such as "3 / 5 complete") to help the user understand the progress of data collection. In still other embodiments, the data collection questions are not limited to multiple-choice questions and may include input box questions (such as "Please fill in your best 5km time"), where users can answer by entering numerical values or text.
[0096] In some embodiments, the second evaluation question is generated based on the answer content corresponding to the first target option using a preset evaluation question determination strategy; the evaluation question determination strategy includes: generating the second evaluation question in real time based on the answer content; or, determining the second evaluation question by matching from a preset evaluation question path based on the answer content.
[0097] The evaluation question determination strategy can refer to the decision rules or decision model used to determine the next data collection question. This strategy determines the specific content of the next data collection question based on the user's selection of the current data collection question. This strategy can be implemented in different ways, such as real-time generation based on an inference model or matching based on a preset path. The inference model can refer to a trained or configured artificial intelligence model that can infer and generate a context-appropriate next data collection question based on the user's input. This inference model can be implemented using a large language model or a rule-based natural language generation model.
[0098] In some embodiments, the assessment question determination strategy may include: generating a second assessment question in real time based on the user's answer. Specifically, the system can input the user's selection result for the first data collection question (i.e., the answer content corresponding to the first target option) into the inference model. This inference model can perform semantic understanding of the user's answer content, identify the user's current exercise level, exercise habits, or exercise goals, and generate the next data collection question matching the user's situation based on the identification results. The inference model can identify key information (such as "run-walk combination" or "maximum 3 kilometers") by performing semantic analysis on the user's answer content, and determine the topic and specific wording of the next data collection question accordingly. Taking a training plan scenario as an example, if the user answers "run-walk combination, maximum 3 kilometers," the inference model can identify that the user is currently at a beginner level, thereby generating a question about the user's recent running volume (such as "How many kilometers have you run in the past month?"). If the user answers "advanced running, 5-10 kilometers daily," the inference model can generate a question about the user's training intensity or training frequency (such as "How many times a week do you run?"). Because the inference model can flexibly generate questions based on the user's answers without relying on a preset question path, it can still generate matching follow-up questions even when the user's answers are unusual or exceed the usual preset range, thereby improving the adaptability and flexibility of the data collection process.
[0099] In some embodiments, the system can provide constraints to the inference model before it generates questions (such as "Please generate data collection questions related to the running plan" or "Please ensure the questions are multiple-choice with 3-4 options") to ensure that the generated questions meet the requirements of the data collection cards. These constraints can be pre-set by the system to standardize the question format output by the inference model. In other embodiments, the inference model can generate the next question based on all currently collected user responses (including the selection results of the first data collection question and other completed answers), allowing the next question to comprehensively reflect the user's situation across multiple dimensions, rather than just based on a single selection result from the previous question, thereby improving the contextual coherence of the questions.
[0100] In some embodiments, the evaluation question determination strategy may include: matching and determining a second evaluation question from a preset evaluation question path based on the user's answer. Specifically, the system may pre-build an evaluation question path library containing multiple branch paths, each corresponding to a combination of user answers and associated with a corresponding next data collection question. After the user completes the selection of the first data collection question, the system can match the user's selection result (i.e., the answer content corresponding to the first target option) in the evaluation question path library, find the branch path corresponding to the answer content, and determine the next data collection question associated with the branch path as the second evaluation question. Taking a training plan scenario as an example, multiple branch paths can be set in the preset path library. For example, if the user answers "run-walk combination, maximum 3 kilometers", the system will match the branch path "ask the user about recent running volume"; if the user answers "advanced running, daily 5-10 kilometers", the system will match the branch path "ask the user about weekly running frequency". A branch path can contain a complete question-and-answer sequence (i.e., an ordered arrangement of multiple subsequent questions). When a user enters a branch path, the data collection questions are displayed sequentially according to the preset question order within that branch path, until all questions in that path have been collected. The preset path matching method has the advantages of fast response speed and controllable question content, and is suitable for scenarios where data collection questions are relatively standardized.
[0101] In some embodiments, the system can combine the two methods described above to determine the second evaluation question. For example, the system can first attempt to match and determine the second evaluation question from a preset evaluation question path. If the matching fails (e.g., there is no branch path corresponding to the user's answer in the preset path library), the system switches to using an inference model to generate the second evaluation question in real time. This hybrid strategy can ensure rapid response in common scenarios while providing fallback question generation capabilities through the inference model in special scenarios. In some embodiments, after generating the question using the inference model, the system can feed the generated question and the corresponding user answer back into the evaluation question path library as new preset paths, thereby continuously enriching the coverage of the preset path library.
[0102] Based on some embodiments of this specification, since the second evaluation question can be generated using a preset evaluation question determination strategy based on the answer content corresponding to the first target option, the data collection questions can be adapted to the user's individual circumstances, rather than using a fixed questionnaire template for all users. This avoids presenting users with irrelevant questions during the data collection process and reduces the user's answering burden. When using the real-time generation method with an inference model, since the inference model can flexibly infer and generate subsequent questions based on the user's answer content, the data collection questions are not limited by the number of preset paths and can adapt to a wider range of user answers. When using the preset path matching method, since the questions and their jump relationships are pre-configured in the path library, the data collection process can be completed quickly without calling the inference model, which is suitable for scenarios with relatively fixed question structures. The above two methods can be flexibly selected or combined according to the application scenario, thereby balancing the flexibility and response efficiency of data collection.
[0103] In one optional implementation of this embodiment, the step of creating the target plan in response to the completion of the data collection card and based on the selection results of each data collection question within the data collection card includes: in response to the completion of the data collection card, displaying a plan target recommendation card on the dialog page, the plan target recommendation card including at least one candidate plan target, the candidate plan target being determined based on the selection results; and generating the target plan in response to the selection operation of selecting a plan target from the at least one candidate plan target.
[0104] Among them, the plan target recommendation card can refer to the recommendation card displayed on the dialog page after the data collection is completed, which is used to recommend one or more candidate plan targets to the user based on the selection results.
[0105] In some embodiments, after the user completes the data collection card, the system determines the user's fitness data based on the selection results of each data collection question, and generates candidate program goals based on the fitness data.
[0106] Figure 5 This diagram illustrates the selection of a target and setting of a training frequency when creating a target plan, as provided in one embodiment of this specification.
[0107] like Figure 5 As shown, Figure 5 The dialog page is displayed in the middle. For example... Figure 5 On the page, the target agent sends a message: "Understood! You've been practicing a combination of running and walking daily, with a maximum distance of 3 kilometers. In the past month, you've completed 1-5 kilometers of running practice, and your longest continuous run is 10 minutes. I guess you might want to achieve one of these three goals. Click the card to adjust the weekly training frequency~." Below this message is a recommended plan goal card. This recommended plan goal card can include multiple candidate plan goals (such as "Running Basics," "Endurance Improvement," and "Habit Formation"). Each candidate plan goal is determined based on the user's selection of the data collection question (for example, if the user selected "Running and Walking, Maximum 3 kilometers," then a beginner-level goal can be prioritized; if the user selected "Advanced Running, 5-10 kilometers daily," then an advanced goal can be prioritized). Each candidate plan goal can display corresponding descriptive information (such as "Establish Running Awareness & Build a Solid Foundation," "Build an Aerobic Base & Enhance Physical Reserves," and "Fix Running Frequency & Cultivate a Long-Term Habit"). The system can determine a recommended goal based on the user's exercise ability data, and this recommended goal can be visually highlighted. Users can select a goal from the recommended goal cards (such as clicking the "Running for Beginners" card).
[0108] In some embodiments, the recommended planning goals card may also include an "Adjust Goals" control, which allows users to view other unrecommended but available planning goals.
[0109] In an optional implementation of this embodiment, generating the target plan in response to a selection operation for a selected plan target among the at least one candidate plan targets includes: displaying a training frequency setting area corresponding to the selected plan target in response to a selection operation for a selected plan target among the at least one candidate plan targets, the training frequency setting area including at least one week selection control, the week selection control being used to determine at least one target week for executing the above target plan from a set of weeks in response to a user operation; and generating the target plan in response to a week selection operation for the week selection control.
[0110] The training frequency setting area refers to the interactive area displayed after the user selects a plan target, used to configure the execution time distribution of the plan within a week. The weekday selection control refers to the operable control set in the training frequency setting area, which allows the user to select one or more days of the week as the plan execution days.
[0111] In some embodiments, after the user selects a planning goal, the system can display a training frequency setting area on the dialog page.
[0112] like Figure 5 On the upper right side of the page, in response to the user's selection of the "Running for Beginners" plan goal from the candidate plan goals, the plan goal recommendation card on the dialog page switches to the training frequency setting area. This training frequency setting area can contain weekday selection controls (such as rounded rectangle buttons for Monday to Sunday) for each day of the week. Each weekday selection control is used to select or deselect the corresponding weekday in response to user actions. For example, the user can click the weekday selection controls corresponding to "Wednesday" and "Friday" to select them as training days. The training frequency setting area can also display suggested information (such as "Recommended 3-4 times per week") and statistics on the number of days selected (such as "4 days selected / week"). After the user completes the weekday selection, they can click the "That's it!" or "Confirm" control in the training frequency setting area. In response to this action, the system generates a target plan based on the user's selected plan goal, the selected weekday, and the selection results of each data collection question in the data collection card.
[0113] In some embodiments, the training frequency setting area may also include a "reset" control, which allows users to cancel all selected days of the week with a single click and reselect. In other embodiments, the day-of-the-week selection control may support batch selection operations (e.g., providing shortcut options such as "select all," "select weekdays," and "select weekends"). In still other embodiments, the training frequency setting area may also provide an option to select training times by specific dates (e.g., selecting a month and day via a calendar control) to accommodate scenarios where plans need to be executed by specific dates rather than by weekday intervals.
[0114] Based on some embodiments of this specification, since the data collection cards sequentially display data collection questions on the dialog page, with only one question displayed at a time, and subsequent questions dynamically determined based on the user's selection of previous questions, users do not need to face a complete questionnaire; they only need to answer each question to complete the data provision. This reduces the cognitive burden and resistance users experience from filling in a large amount of information at once. Furthermore, the personalized adaptability of the question progression improves the efficiency and accuracy of data collection. The plan goal recommendation card displays multiple candidate plan goals determined based on the user's selection results, allowing users to independently choose a goal plan based on a full understanding of the system's recommendation criteria, balancing intelligent system recommendation with user autonomy. The weekday selection control in the training frequency setting area allows users to flexibly configure training execution days on a weekly basis, enabling users to customize the plan rhythm according to their own work and rest patterns, improving the plan's adaptability to the user's daily habits. Overall, the progressively guiding link from data collection to goal recommendation to frequency setting balances user convenience and the personalization of the final generated plan during the user information collection process.
[0115] In one optional implementation of this embodiment, the step of creating the target plan on the dialog page includes: in response to receiving the plan generation request on the dialog page, displaying a device binding card on the dialog page, the device binding card including a device data import option and a confirm no device option, the device data import option being used to trigger the import of the user's historical exercise data from the wearable device; in response to the selection operation of the device data import option, importing the user's historical exercise data from the wearable device, and displaying a user profile card on the dialog page, the user profile card including basic user information and at least one exercise data item determined based on the historical exercise data.
[0116] The device binding card refers to an interactive card displayed on the dialog page that guides users to bind their sports data collection device. This card may include options to import device data and confirm no device. The device data import option triggers the import of the user's historical sports data from wearable devices (such as smartwatches, fitness trackers, etc.) or sports data platforms (such as health apps, sports communities, etc.). The user profile card refers to a card generated based on the imported historical sports data, displaying basic information about the user's athletic abilities. It may include basic user information (such as nickname, gender, age, exercise frequency, and exercise level tags) as well as sports data items determined based on historical sports data (such as longest exercise distance, best performance, and maximum heart rate).
[0117] In some embodiments, after a user initiates a plan generation request, the system may first display a device binding card to guide the user to import historical exercise data through the device.
[0118] Figure 6 This is a schematic diagram illustrating a method for acquiring user motion data according to an embodiment of this specification.
[0119] like Figure 6 As shown in the top left corner of the page, in response to the user's request to "provide a running plan," the target agent in the dialogue page sends a message: "Great! Before starting to create a plan, I'd like to import your exercise data first. This will help with plan creation. If you don't have past data, you can bind it first for easier analysis later." Below this message is a device binding card. The device binding card can display supported device channels or data sources (such as "Supports data from Apple Health, Garmin, Gooch, Huawei, Yuewo, vivo, Honor, and OPPO channels"), as well as two options: "No device in my system" and "One-click import." Users can choose "One-click import" to import historical exercise data from a bound wearable device, or choose "No device in my system" to skip device binding and proceed to the data collection card link.
[0120] In response to the selection of the "No My Device" option, the system can display as follows: Figure 6 After the transition page shown in the upper right corner, you will enter a page like... Figure 4 The data collection card link is shown. See the description above for details; it will not be repeated here.
[0121] In response to the selection of the "One-Click Import" option, the system can import the user's historical activity data from the wearable device and display the user profile card after the import is complete, such as... Figure 6 As shown in the lower left corner of the page, the user profile card can contain basic user information (such as avatar, nickname "Tom", gender "male", age "31 years old", exercise frequency "2-3 times per week", level label "aerobic jogger") and multiple exercise data items determined based on historical exercise data (such as "longest exercise distance 5.1km", "3km BP 16′12″", "maximum heart rate 178 bpm", etc.). Each exercise data item can have an edit icon to allow users to check and correct the data. The user profile card can serve as a confirmation interface after data import, allowing users to confirm the accuracy of the data obtained from the device before proceeding to the subsequent plan generation process. The target agent can send messages above the user profile card, informing the user of the data import source, cumulative running distance, total exercise duration, and prompting the user to check the profile information.
[0122] In some embodiments, the device binding card may display icons or names of multiple device channels, allowing users to initiate the data import process for the corresponding channel by clicking its icon. In other embodiments, the device binding card may also include a "skip" control, allowing users to directly access the data collection card link without displaying the profile card. In still other embodiments, if the system detects insufficient data after importing historical exercise data (e.g., the user only has 1-2 exercise records), it can automatically enter the data collection card link to supplement the required data through a dialog box, ensuring a more sufficient foundation for subsequent planned data generation.
[0123] Based on some embodiments of this specification, by providing a device binding card in the dialog page, users can authorize the import of historical exercise data from wearable devices with a single click via the device data import option. This eliminates the tedious manual entry of exercise data, reduces data entry time, and minimizes errors that may occur during manual input. Furthermore, by displaying a user profile card containing basic user information and exercise data items, users can verify the accuracy of the imported data before plan generation, enhancing data reliability. The combination of device import and profile verification allows users with device data to quickly complete data entry through import, while simultaneously verifying the completeness of the data through the profile card, thus balancing data entry efficiency and accuracy.
[0124] In an optional implementation of this embodiment, the plan generation method further includes: in response to an edit trigger operation on a target motion data item in the user profile card, displaying an editable overlay corresponding to the target motion data item, wherein the editable overlay displays an editable current value of the target motion data item and a save control; the current value is determined based on the user's historical motion data; in response to a trigger operation on the save control, updating the user profile card based on the edited current value; and generating the target plan based on the updated user profile card.
[0125] The editing overlay refers to the interactive layer displayed on the dialog page when a user performs an editing operation on a data item in a file card, allowing the user to modify the corresponding data value.
[0126] In some embodiments, users can edit and modify the motion data items in their user profile cards. For example... Figure 6As shown on the lower left and lower right pages, each exercise data item in the user profile card (such as "5.1km", "16′12″", "178bpm") can be associated with an edit control. After the user performs an edit trigger operation on the target exercise data item (such as clicking the edit icon corresponding to the data item), the system can display the corresponding edit overlay. This edit overlay can be displayed above the dialog page and can contain a title (such as "Tom's Profile Filling"), a subtitle (such as "Longest Running Distance in km"), a large numerical display of the current value, and a numeric keypad or step adjustment control. The user can enter precise values via the numeric keypad or adjust values via the step adjustment control. The bottom of the edit overlay can contain a save control. After the user clicks the save control, the system can update the user profile card based on the edited current value.
[0127] In some embodiments, after a user completes the editing and updating of a profile card, the system can generate a target plan based on the updated user profile card, for example, redirecting to a page such as... Figure 2 The left-hand page. In some embodiments, generating a target plan based on the updated user profile card may include: the system may redirect to a plan target recommendation card flow, for example, redirecting to... Figure 5 On the top left side of the page, a dialog box displays a plan target recommendation card. This card contains candidate plan targets determined based on updated profile data. Users can select one and continue to complete the training frequency settings, ultimately generating the target plan. Because users re-enter the plan target recommendation process after editing their profile card, the recommended plan targets are based on the latest user data, avoiding inaccuracies caused by untimely data correction.
[0128] In some embodiments, when a user edits the current value in the editing overlay, the system can display a unit prompt for the current value (such as "km" or "min / km") to help the user input accurately. In other embodiments, after a user performs an edit trigger operation on a certain exercise data item, the system may not display the editing overlay, but instead directly switch the data item to an editable state in the user profile card (such as displaying an input box). The user can then modify the value in the input box and click save or click on other areas of the card to complete the update. In still other embodiments, after a user edits and saves a certain exercise data item, the system can automatically identify whether other data items associated with that data item need to be updated accordingly (for example, if the user modifies the "longest exercise distance," the system can prompt the user whether to update the "best performance" accordingly), and perform the corresponding update after obtaining user confirmation.
[0129] Based on some embodiments of this specification, the device binding card provides an option to import historical exercise data from wearable devices. This eliminates the need for users with existing exercise records to manually fill in various exercise data; data import can be completed with a one-time authorization, simplifying the data entry process and reducing the user's input burden. Simultaneously, since the user profile card is displayed immediately after data import, users can confirm the accuracy of the imported data before plan generation and correct individual data items by editing the overlay, ensuring both convenience and accuracy in data entry. Furthermore, because users re-enter the plan goal recommendation process after editing their profile card, the system can re-determine candidate plan goals based on the latest corrected data, avoiding discrepancies between plan goals and the user's actual situation due to data deviations, thus improving the accuracy of plan recommendations. The coexistence of device import and dialogue-based data collection paths allows users with device data to quickly complete data entry through import, while users without device data can complete data collection through dialogue. These two methods adapt to different user scenarios, improving the applicability of the solution to different user groups.
[0130] See Figure 7 , Figure 7 A flowchart of a plan presentation method according to an embodiment of this specification is shown, which may specifically include the following steps.
[0131] Step 702: In response to entering a dialogue page with the target agent, the dialogue page displays target items matching the current date; wherein, the dialogue page includes a fixed-display calendar component, the target items belong to a target plan, the target plan is created by the target agent based on a plan generation request received on the dialogue page, and the calendar component is used to view the planned items corresponding to each date in the target plan.
[0132] The target item can refer to the planned items in the target plan that match the current date. When a user enters the chat page, the system can filter the planned items corresponding to that date from the target plan based on the current system date and display them on the chat page.
[0133] In some embodiments, the target item and the calendar component that is permanently displayed in the chat page can work together based on the same time base (i.e., the current date)—the calendar component provides a visual framework for the time dimension, and the target item serves as a positioning anchor point under this framework, so that users can directly know the day's plans without having to manually search in the calendar when they enter the chat page.
[0134] In some embodiments, users can access a dialogue page with the target intelligent agent via a terminal device. This dialogue page consistently displays a calendar component, which has been described in detail in the above embodiments and will not be repeated here. After entering the dialogue page, the system can filter the planned items (i.e., target items) corresponding to the current system date from the target plan and display them on the dialogue page.
[0135] Figure 8 This is a schematic diagram of a dialog page and a plan details page provided in one embodiment of this specification.
[0136] like Figure 8 As shown on the left side of the page, a calendar component is permanently displayed at the top of the chat window. The current date (e.g., March 20th) can be marked with specific visual identifiers (such as underline, highlight, or circle). Below the calendar component are the target tasks. These tasks can include the following information: a greeting (e.g., "Hello Tom, today is your 7th training day"), weather information (e.g., "Today's weather in Nanshan District, Shenzhen is sunny, 18-22℃, and the air quality is very good (AQI 23)"), physical condition information (e.g., "You slept for 8 hours and 42 minutes last night, and this morning your HRV is basically consistent with the normal level of the past 7 days. Your overall recovery is good, and you are well-suited for running"), plan execution suggestions (e.g., "We suggest you complete today's training as planned: a 3km long-distance run, estimated time approximately 22 minutes"), and a detailed card for the day's planned tasks (e.g., "3km long-distance run, 33 minutes, pace 6'30"-6'50", cloudy, 22℃, excellent air quality, physical readiness 70%).
[0137] In some embodiments, the target item may include detailed parameters of the planned activity for the day, such as training distance (e.g., "3 km"), training type (e.g., "long distance run"), estimated time (e.g., "33 minutes"), pace zone (e.g., "6'30"-6'50"), weather conditions (e.g., "cloudy, 22°C"), air quality (e.g., "excellent air quality"), and physical readiness index (e.g., "70% physical readiness"). This information helps users fully understand the day's training schedule and external conditions before executing the plan.
[0138] In some embodiments, if the current date is within the time frame of the target plan, the target item can be the planned item corresponding to that date; if the current date is not within the time frame of the target plan (e.g., the plan has not yet started or has already ended), the target item can be the planned item closest to the current date, or the system can display a prompt message to inform the user that the current date is not within the planned period.
[0139] Step 704: In response to the viewing operation of the target item, display the plan details page of the target plan.
[0140] The plan details page can refer to a separate page that displays complete information about the target plan. This page may include the overall progress of the plan, cumulative data, calendar view, and details of the planned items for each date.
[0141] In some embodiments, users can perform viewing operations on a target item (such as clicking any area in the target item card, or clicking controls such as "View All"), and the system responds to this operation by displaying the plan details page of the target plan.
[0142] In some embodiments, the target item may also include a "Start Training" control, which allows the user to directly begin the day's training record (e.g., start timing, record GPS trajectory, etc.) without entering the plan details page. In other embodiments, the target item may also include an "Adjust Plan" control, which, when clicked by the user, displays plan adjustment options (e.g., "Adjust Training Distance," "Adjust Training Time," "Adjust Training Type," etc.). After the user selects an option, the target agent can make corresponding adjustments to the target plan, and the calendar component and target item can be updated synchronously after the adjustment is completed.
[0143] Based on some embodiments of this specification, since the system automatically matches and displays the corresponding target items from the target plan according to the current date when the user enters the dialog page, a linkage is formed between the calendar component and the current date. The calendar component provides a visual framework in the time dimension, and the current date serves as the positioning anchor point within this framework. The cooperation between the two allows users to directly know the items that need to be performed on the current date in the dialog page without manually browsing the calendar to find the arrangements for the day, reducing the user's information search cost. At the same time, since the calendar component is fixedly displayed in the dialog page, and the display of target items works collaboratively with the calendar component based on the same time base, even if the user scrolls through the dialog content... Whether performing other operations or not, the association between the calendar component and the target item corresponding to the current date remains consistent, ensuring that users can continue to receive clear guidance on the day's plan without leaving the chat page. In addition, after the user performs a view operation on the target item, the system further displays a plan details page containing the complete plan content, and the date corresponding to the current date is displayed in a highlighted manner in the plan calendar, and the plan card corresponding to the current date is placed in a preset position in the visible area. This allows users to directly view the complete plan content of the day without having to relocate in the plan details page, achieving a seamless transition from the overview of the day's items in the chat page to the complete plan in the plan details page.
[0144] In one optional implementation of this embodiment, the plan details page includes basic plan information, a statistical data display area, and a plan details display area; the statistical data display area includes at least one data indicator card, each data indicator card is used to display a data chart corresponding to a statistical data indicator of the target plan; the plan details display area is used to display a plan calendar and plan cards, the plan calendar is used to display the distribution of planned items of the target plan on each date, and the plan cards are used to display the details of planned items corresponding to each date in the target plan.
[0145] The basic plan information, displayed at the top of the plan details page, may include the plan name, plan progress, and an overall plan overview (such as total training volume, total training cycles, and total number of training sessions). The statistics display area, on the plan details page, refers to the area displaying statistical charts related to the target plan; this area may contain one or more data indicator cards. The plan details display area, on the plan details page, refers to the area displaying the plan calendar and plan cards.
[0146] Figure 9 This is a schematic diagram illustrating the display status of a plan details page provided in one embodiment of this specification.
[0147] like Figure 8 The right side of the page and Figure 9 As shown, the plan details page can include basic plan information, a statistics display area, and a plan details display area. Basic plan information can be displayed at the top of the plan details page, including the plan name (e.g., "3km Introductory Plan"), plan progress (e.g., "58% Progress"), and an overall plan overview (e.g., "Plan totals 25km, 12 training sessions, 3 weeks of training"), indicating the progress and overall scale of the target plan. The statistics display area can be located below the basic plan information, and can include at least one data indicator card. Each data indicator card displays a data graph corresponding to a statistical indicator of the target plan (e.g., a cumulative running progress bar showing the comparison between the current cumulative value "14.5km" and the target value). The plan details display area can be located below the statistics display area, displaying the plan calendar and plan cards. The plan calendar shows the distribution of planned activities across different dates, with each date's corresponding cell displaying the training volume label for that date (e.g., "3km", "2.5km", etc.), allowing users to intuitively understand the overall distribution of the plan over time. The plan card can display details of the planned items for each date in the target plan (e.g., "March 20th / Friday: 3km long run, 33 minutes, pace 6'30"-6'50", cloudy, 22℃, good air quality").
[0148] In some embodiments, the plan cards can be displayed differently based on the execution status of the target items for the corresponding dates: for dates that have been completed, the plan card can display actual execution data (such as performance score, actual time, actual pace, etc.); for dates that have not started or are in progress, the plan card can display pre-planned plan information (such as target distance, target pace, etc.). By displaying the plan cards in conjunction with the plan calendar, users can obtain the overall time distribution of the plan from the calendar and the specific arrangements for each date from the cards.
[0149] Based on some embodiments of this specification, the plan details page uses a three-area structure—basic plan information, statistical data display area, and plan details display area—to provide users with plan information at different granularities on the same page. Specifically, basic plan information is displayed at the top of the page, presenting an overview of the overall progress and scale of the plan; the statistical data display area is located in the middle, displaying statistical charts related to the target plan through data indicator cards; the plan details display area uses a combination of a plan calendar and plan cards—the calendar provides a macro-level distribution of the plan on a timeline, and the cards provide specific arrangements for each date—allowing users to quickly switch between information granularity between the overview and details. Through the vertical arrangement of these three areas, users can obtain information from three different dimensions—an overview of plan progress, statistical data trends, and specific date arrangements—at once, completing the information retrieval from macro to micro without switching between different pages, reducing the operational cost for users to jump between multiple pages or functional modules to find information.
[0150] In an optional implementation of this embodiment, displaying the plan details page of the target plan includes: positioning the plan details display area to the position corresponding to the current date in the plan details page, wherein the current date in the plan calendar is presented in a display mode different from other dates, and the plan card corresponding to the current date is placed in a preset position within the visible area.
[0151] In some embodiments, when a user navigates from a chat page to a plan details page, the plan details page may be displayed with the current date as the anchor point.
[0152] Specifically, in response to a user's action of viewing a target item, the system can position the plan details display area to the location corresponding to the current date when displaying the plan details page. The current date in the plan calendar can be displayed in a way that distinguishes it from other dates (such as highlighting, selecting, or marking with a specific color), and the plan card corresponding to the current date can be placed in a preset position within the visible area (such as at the top of the visible area). Figure 8As shown, the current date "20" in the plan calendar can be displayed differently from other dates. The plan card corresponding to "March 20th / Friday" in the plan card list can be placed at the top of the visible area, so that users can quickly locate the plan for the day without having to manually search for it in the plan card list.
[0153] In some embodiments, the anchoring action may include the synchronized positioning of the schedule calendar and schedule cards—that is, the schedule calendar scrolls to the week of the current date, while the schedule card list scrolls to the card corresponding to the current date, both focusing on the same date in the view, allowing the user to see the current date's schedule from two dimensions simultaneously without having to repeatedly navigate between the calendar and the card list. In some embodiments, if the current date is not in the visible area when the schedule details page is first displayed, the system can automatically scroll the page to bring both the calendar position and the card position corresponding to the current date into the visible area. In other embodiments, when the schedule details page is first displayed, only the schedule card is positioned to the card corresponding to the current date, while the current date in the schedule calendar is highlighted in the calendar's visible area without additional scrolling.
[0154] In some embodiments, the anchoring behavior in the plan details page can be triggered only when the user first enters the plan details page. When the user returns to the plan details page later, the system can maintain the user's browsing position when they last left, instead of automatically anchoring to the current date.
[0155] Based on some embodiments of this specification, when a user enters the plan details page from the dialog page, the current date in the plan calendar is highlighted, and the plan card corresponding to the current date is placed in a preset position in the visible area. This allows the user to directly locate the plan for the current date without having to manually search or scroll through the plan details page, reducing the user's repeated operations between calendar location and card search, and lowering the cost of information acquisition.
[0156] In an optional implementation of this embodiment, the plan display method further includes: hiding the statistical data display area in response to a first-direction swipe operation on the plan details display area; and expanding the display of the statistical data display area in response to a second-direction swipe operation on the plan details display area.
[0157] In some embodiments, users can control the display status of the statistics display area by performing a swipe operation on the plan details display area within the plan details page.
[0158] like Figure 9As shown, you can perform a first-direction swipe or a second-direction swipe on the plan details page. In response to a first-direction swipe (e.g., swiping up) on the plan details display area, the statistics display area can be hidden, allowing the plan details display area to occupy a larger display area on the page, making it easier for users to focus on viewing the plan calendar and plan cards. In response to a second-direction swipe (the opposite direction of the first direction, such as swiping down) on the plan details display area, the statistics display area can be expanded, allowing it to reappear on the page, and multiple data indicator cards can be displayed simultaneously, such as... Figure 9 The data shown includes cumulative running distance, average cadence, and cumulative calorie consumption.
[0159] Understandable, Figure 8 and Figure 9 The data indicator cards shown are for illustrative purposes only. In practical applications, the statistical data display area can contain many different types of data indicator cards to present the user's training results from multiple dimensions. For example, data indicator cards can also include distance breakthrough prediction charts, aerobic percentage charts, etc. Furthermore, users can customize the data indicator cards displayed in the statistical data display area according to their own focus. For example, by long-pressing a data indicator card or clicking the edit control, users can select the desired data indicator from the candidate data indicator list to replace the currently displayed data indicator card. These different types of data indicator cards can be presented individually or in combination in the statistical data display area. Users can switch between different data indicator cards and their corresponding data charts by swiping horizontally or vertically within the statistical data display area.
[0160] In some embodiments, the statistics display area can be completely hidden (i.e., the statistics display area is not visible on the page) or collapsed into a thumbnail state (such as displaying only a title bar or an expand tooltip), which the user can expand by swiping again. In some embodiments, the hiding or expanding of the statistics display area can be triggered by the user performing a swipe operation in any area within the plan details page, and is not limited to swiping operations targeting the plan details display area.
[0161] In some embodiments, the display ratio between the statistics display area and the plan details display area on the plan details page can change continuously in response to a swipe operation (e.g., the statistics display area gradually shrinks and the plan details display area gradually expands as the user swipes), rather than jumping between hidden and fully displayed. In other embodiments, the user can adjust the relative size between the statistics display area and the plan details display area by long-pressing and dragging the edge of the plan details display area. In other embodiments, the plan details page may also include a toggle control that allows the user to switch between "show statistics display area" and "hide statistics display area" states. In other embodiments, when the statistics display area is hidden, an operable prompt area (such as "swipe up to view statistics") can be retained at the top of the plan details page, which the user can click or swipe to re-expand the display of the statistics display area.
[0162] Based on some embodiments of this specification, since the plan details page includes basic plan information, statistical data display area, and plan details display area, users can simultaneously obtain three different levels of information—plan progress overview, data statistics, and specific plan arrangements—on the same page without switching between different pages. Furthermore, since the plan details display area includes a plan calendar and plan cards, with the calendar providing a macro-level distribution on a timeline and the cards providing specific content for each date, both present plan information from different dimensions. Users can quickly switch between viewing overview and details within the same area.
[0163] Based on some embodiments of this specification, since users can hide or expand the statistical data display area by performing swipe operations in different directions in the plan details display area, users can flexibly adjust the information layout of the page according to their current focus. When they need to focus on specific plan arrangements, they can hide the statistical data display area by swiping in the first direction to free up more display space. When they need to view data statistics, they can expand the display area again by swiping in the second direction. Users can switch between different granular information viewing modes on the same page without jumping to another page.
[0164] In one optional implementation of this embodiment, the planning calendar supports view switching; the method further includes: in response to a view switching operation on the planning calendar, switching between a weekly view and a monthly view, wherein the weekly view displays the calendar for the current week and the monthly view displays the calendar for the current month.
[0165] The view switching operation refers to the interactive action performed by the user on the planning calendar to switch the display granularity. Users can use this operation to switch between weekly and monthly views to select different time scales to view the distribution of planned tasks. The weekly view is a calendar display mode with a one-week time range, showing the distribution of planned tasks for each date within the current week, allowing users to focus on specific arrangements in the short term. The monthly view is a calendar display mode with a one-month time range, showing the distribution of planned tasks for each date within the current month, allowing users to grasp the overall planning rhythm for the entire month.
[0166] Figure 10 This is a schematic diagram illustrating the switching between weekly and monthly views in a plan details page provided in one embodiment of this specification.
[0167] like Figure 10 As shown, the plan calendar on the plan details page supports view switching. The plan calendar can include view switching controls (such as a "week / month" toggle button), which users can click to switch views. In response to view switching operations on the plan calendar, it can switch between weekly and monthly views. In weekly view, the plan calendar displays the calendar for the current week, with each date's corresponding cell displaying the training volume label or training type identifier, allowing users to focus on specific training arrangements in the short term. For example, Figure 10 The left-hand page displays a weekly view, showing the calendar from March 16th to March 22nd. Below each date, you can label training distance information such as "3 km" or "2.5 km". In the monthly view, the plan calendar displays the current month's calendar, with each date's corresponding cell displaying a brief plan indicator, allowing users to grasp the overall plan distribution for the month. For example, Figure 10 The right-hand page displays a monthly view, showing the complete calendar for March 2026. Training volume labels can be displayed in the date cells corresponding to each training day. Users can quickly understand which dates in the month are scheduled for training, which dates are rest days, and the distribution density of training dates throughout the month through the monthly view.
[0168] In some embodiments, when a user enters the plan details page from the dialog page, the plan calendar can display a weekly view by default to help the user quickly focus on the specific training schedule for the current week. Users can switch to a monthly view to view the entire month's plan as needed. In some embodiments, when switching between the weekly and monthly views, the training volume labels or plan identifiers corresponding to each date can be adjusted in their display position and size within the date grid to adapt to the size changes of the date grid in different views. For example, in the weekly view, the date grid is larger and can display more detailed plan identifiers (such as training distance values plus training type names), while in the monthly view, the date grid is smaller and can only display training distance values or intensity icons.
[0169] In some embodiments, after a user switches from a weekly view to a monthly view by clicking the "Week / Month" toggle control, the statistics display area can synchronously update the content of the data statistics indicators (e.g., the monthly view displays the cumulative running volume for the current month, and the weekly view displays the cumulative running volume for the current week) to maintain consistency in data display after the view switch. In other embodiments, the view switching operation can be achieved through a pinch or spread gesture on the calendar (pinch to switch from the monthly view to the weekly view, spread to switch from the weekly view to the monthly view). In still other embodiments, the calendar can also support more granular view switching (e.g., a daily view), allowing users to switch between daily, weekly, and monthly views using the view switching control.
[0170] Based on some embodiments of this specification, since the planning calendar supports switching between weekly and monthly views, users can select different time granularities to view the plan according to their current information needs: the weekly view focuses on recent specific arrangements, making it easy to quickly view the training tasks for the week on the execution date; the monthly view provides an overview of the entire month's plan distribution, making it easy to grasp the overall training rhythm, and users can view information at different granularities from macro to micro without switching between different pages.
[0171] In one optional implementation of this embodiment, the planned items corresponding to each date displayed in the planning calendar are presented in the form of icons, and the display style of the icons corresponding to planned items with different training intensities is different; the display style includes at least one of icon color, icon shape or icon size.
[0172] Intensity icons can refer to graphic symbols used in the planning calendar to represent different training intensities. Planning items with different training intensities can display intensity icons with different styles, such as differences in icon color, icon shape, or icon size.
[0173] In some embodiments, the planned items corresponding to each date displayed in the planning calendar can be presented in the form of icons, and the display style of the icons corresponding to planned items with different training intensities can be different.
[0174] Specifically, the planned activities for each date in the calendar are presented as icons, with different icon styles for planned activities of different training intensities. Specifically, for dates requiring a training plan, the calendar displays an intensity icon matching the corresponding training intensity; for dates not requiring a training plan (such as rest days), no intensity icon is displayed. Planned activities of different training intensities can be distinguished by different icon styles. For example, the intensity icon for an easy run might be a green circle, for a tempo run a yellow triangle, and for an interval run a red square. In addition to shape, icons for different training intensities can also differ in color (e.g., low-intensity training icons might be blue or green, medium-intensity training icons might be yellow or orange, and high-intensity training icons might be red or purple) to allow users to quickly identify the daily training intensity level by color. Icon styles can include at least one of icon color, icon shape, or icon size. These different styles can be used individually or in combination (e.g., icons for different training intensities can differ in both color and shape to provide richer visual distinctions).
[0175] In some embodiments, when the target plan includes multiple training phases, the icon shapes for planned items corresponding to different training phases in the plan calendar can be different to help users visually identify the current training phase in the calendar. For example, the icon for the first training day can be a circle, the icon for the second training day can be a triangle, and the icon for the third training day can be a parallelogram. In the month view, due to the limited space in the date grid, using icons of different shapes to distinguish phases saves more space than text labels, and users can quickly locate the current phase through graphics without reading the phase number. Color coding for different training intensities and shape coding for different training phases can be used simultaneously (i.e., the same icon has both color and shape attributes, with color indicating intensity and shape indicating phase) to convey more dimensions of information within a limited space.
[0176] In some embodiments, users can click on the intensity icon in the plan calendar to view a detailed description of the training intensity corresponding to that icon (such as training type name, intensity zone, heart rate suggestion, etc.), helping users understand the specific meaning of different training intensities while viewing the plan. In other embodiments, the legend area of the plan calendar can display all icon styles used in the current view and their corresponding training intensities or training phases, allowing users to quickly understand the meaning of different icons. In still other embodiments, users can customize the icon styles corresponding to different training intensities or training phases in the settings of the plan details page (for example, users can adjust the color or shape of the "Easy Run" icon according to their personal preferences).
[0177] Based on some embodiments of this specification, since the planned items corresponding to each date are presented in the form of icons, and the display style of the icons corresponding to planned items with different training intensities is different, users can quickly identify the daily training intensity distribution in the calendar view without clicking to enter the details, improving the overview efficiency of the calendar and the user experience. Because the icons for different training intensities differ in color, and color, as one of the most sensitive visual attributes of the human visual system, can be perceived and distinguished faster than shape or size, users can quickly judge the intensity change pattern throughout the entire planning period by the color distribution when browsing the monthly view. When the target plan contains multiple training phases, since the icon shapes of the planned items corresponding to different training phases are different, and shape encoding and intensity encoding can be used simultaneously (color is used to convey intensity information, and shape is used to convey phase information), users can simultaneously perceive information in both training intensity and training phase dimensions without adding extra interaction steps, reducing the time cost for users to identify training phases. Furthermore, color encoding and shape encoding convey information in different dimensions, and they are independent and do not interfere with each other, allowing users to simultaneously obtain the distribution pattern of training intensity and the rhythm of training phase division in the monthly view, comprehensively grasping the overall structure of the plan without switching between multiple views or pages.
[0178] In an optional implementation of this embodiment, the plan display method further includes: in response to the completion event of the target item corresponding to the current date, displaying an evaluation card on the dialog page; the evaluation card includes at least one evaluation dimension card, each evaluation dimension card being used to display evaluation information corresponding to one evaluation dimension of the target item; the evaluation dimension includes at least one of training performance score, running posture analysis, pace analysis, heart rate analysis, and cadence analysis.
[0179] The evaluation card refers to an interactive card proactively pushed to the dialogue page by the target agent after the user completes the daily goal. This evaluation card can contain evaluation information and data feedback regarding the completion status. Evaluation dimension cards refer to sub-cards within the evaluation card used to display information for specific evaluation dimensions; each evaluation dimension card corresponds to one evaluation dimension (such as training performance score, running posture analysis, pace analysis, heart rate analysis, cadence analysis, etc.).
[0180] Figure 11 This diagram illustrates the display state of an evaluation card provided in one embodiment of this specification. The application scenario shown is as follows: On a certain day after the target plan begins execution, after the user completes the training tasks for the day, the target agent proactively sends a message on the dialogue page, pushing evaluation information based on the training statistics for that day to the user.
[0181] like Figure 11 As shown, a calendar component (illustrated as date numbers in the image) is permanently displayed at the top of the dialogue page, allowing users to quickly view the planned tasks for each date in their target plan. The current date in the calendar component can be marked with a specific visual identifier (such as underlined or highlighted) to indicate the user's current time. Below the calendar component, messages pushed by the target agent are displayed. These messages may include greetings (e.g., "Hello Tom, today is your 7th training day"), weather information (e.g., "Today's weather in Nanshan District, Shenzhen is sunny, 18~22℃, and the air quality is very good (AQI 23)"), and training completion evaluations (e.g., "Today's 3km long-distance run performance was excellent, reaching 98 points"), allowing users to receive overall training feedback before viewing the evaluation cards.
[0182] In response to the completion event of the target task corresponding to the current date, the system can display an evaluation card on the dialog page. This evaluation card can include at least one evaluation dimension card (such as...). Figure 11 The "Long Distance Run Summary" or "Running Analysis" cards (within the framework) display assessment information for each assessment dimension corresponding to a specific objective. Assessment dimensions may include at least one of the following: training performance score (e.g., the number "98"), running form analysis, pace analysis, heart rate analysis, and cadence analysis.
[0183] In some embodiments, when a user returns to the chat page after completing a target task on the plan details page, the system may also display an evaluation card on the chat page. In other embodiments, the system directly displays the evaluation card on the chat page after the user completes a target task. The evaluation card can be triggered automatically after the user completes the task, without relying on the user's active request.
[0184] In one optional embodiment of this example, the evaluation card includes a first evaluation dimension card and a second evaluation dimension card; the plan display method further includes: in response to a card switching operation on the evaluation card, switching from displaying the first evaluation dimension card to displaying the second evaluation dimension card, or switching from displaying the second evaluation dimension card to displaying the first evaluation dimension card; the card switching operation includes a horizontal swipe operation on the evaluation card or a click operation on a switching control on the evaluation card.
[0185] Among them, the card switching operation can refer to the interactive operation performed by the user on the evaluation card to switch between cards of different evaluation dimensions.
[0186] In some embodiments, the evaluation card may include a first evaluation dimension card and a second evaluation dimension card, and the user can switch between different evaluation dimension cards through a card switching operation. The card switching operation may include a horizontal swipe operation on the evaluation card (such as the user swiping left or right in the evaluation card area) or a click operation on the switching control on the evaluation card (such as clicking the label control such as "Running Analysis" or "Running Form Analysis" on the evaluation card).
[0187] For example, Figure 11 The top-left and bottom-left pages can be viewed as a process of switching from the "Long Distance Run Summary" assessment dimension card to the "Running Analysis" assessment dimension card by swiping horizontally. Furthermore, for example, Figure 11 The evaluation dimension card "Long Distance Run Summary" in the upper left corner of the page displays the training performance with a score of "98" and shows an overall evaluation summary for this training (such as "Identified that your [3km long distance run] had a long ground contact time and running form efficiency that needs improvement"). Figure 11 The "Running Analysis" card in the lower left corner of the page displays summary information about the run during this training session (such as "Today's running pace was very stable, with an average cadence of 167 spm. Combined with the pace, the running form was smooth and efficient").
[0188] In one optional implementation of this embodiment, the evaluation dimension card displays partial evaluation information for the corresponding evaluation dimension in a default state and includes an information expansion control. The plan display method further includes: in response to a trigger operation on the information expansion control, expanding and displaying the remaining evaluation information for the corresponding evaluation dimension in the evaluation dimension card.
[0189] Among them, the information expansion control can refer to the control set in the evaluation dimension card, which allows users to view the remaining evaluation information of the corresponding evaluation dimension.
[0190] In some embodiments, the evaluation dimension card can display partial evaluation information for the corresponding evaluation dimension by default (e.g., only the evaluation title and a summary sentence), and includes an information expansion control (as shown in the figure, "Expand All" and the icon on the right). Users can trigger this control to expand and display the remaining evaluation information for the corresponding evaluation dimension within the evaluation dimension card. For example, in... Figure 11 On the left side of the page, the evaluation dimension card displays by default "Identified that your [3km long-distance run] had a long ground contact time and running form efficiency needs improvement." After the user clicks "Expand All" or the icon to its right, the card can be expanded to... Figure 11 The status displayed on the right-hand page shows more complete analysis information (including more specific analysis such as "The ground contact time of 356 milliseconds is relatively long (efficiency range recommended <250ms), indicating that the connection of the push-off force is not smooth enough. However, the symmetry of the movement is very good, with almost no deviation between the left and right feet").
[0191] In some embodiments, the evaluation card may also include a sharing control, allowing users to share the day's training evaluation results to other platforms. In other embodiments, the evaluation dimension cards within the evaluation card may include progress indicators (e.g., "2 / 4 of the evaluation dimensions have been displayed") to help users understand the current card's position among all evaluation dimensions. In other embodiments, users can click the "View All Dimensions" control within the evaluation card to expand and display a thumbnail list of all evaluation dimension cards on the dialog page. In still other embodiments, after a user closes an evaluation card (e.g., by clicking the close button in the upper right corner of the card), the evaluation card may collapse into a notification bar (e.g., "Today's training evaluation is complete, click to view details") to minimize interference with subsequent conversations.
[0192] Based on some embodiments of this specification, since the evaluation cards are proactively pushed to the dialogue page by the target agent after the user completes the daily target tasks, the user can immediately obtain the evaluation feedback for this training without actively initiating a query, shortening the time interval between completing training and obtaining evaluation feedback, and improving the timeliness of feedback. Because the evaluation cards use a card switching operation to switch between different evaluation dimension cards, each evaluation dimension is displayed independently. Users can choose to view detailed evaluation information for a specific dimension based on their focus, without having to read all dimensions at once, reducing the possibility of information overload. Simultaneously, since the evaluation dimension cards only display partial evaluation information by default, users can use the information expansion control to view the remaining evaluation information as needed, balancing the simplicity and completeness of information presentation. Overall, the evaluation card push mechanism, together with the aforementioned plan display scheme, forms a complete closed loop of "plan display → execution tasks → completion feedback," enabling users to complete the entire process from viewing the daily schedule to executing the plan and obtaining training feedback within the same dialogue page, without switching between different pages or applications, improving the continuity of training management and user experience.
[0193] See Figure 12 , Figure 12 A flowchart of a plan generation method provided in one embodiment of this specification is shown below. Figure 12 As shown, the client is mainly responsible for displaying the dialog page, receiving and responding to user interactions, and displaying the calendar component and various cards, while the server is located on a remote server or cloud service provider and is responsible for data processing, storage, and interaction with external systems (such as databases, third-party services, etc.).
[0194] On the user's end, a dialogue page with the target intelligent agent is displayed.
[0195] On the user side, in response to the plan generation request obtained from the dialog page, a plan generation request is sent to the server.
[0196] On the server side, in response to the plan generation request, a device binding card is sent back to the user. The device binding card includes a device data import option and a confirmation no device option. The device data import option is used to trigger the import of the user's historical exercise data from the wearable device.
[0197] The first scenario (where the user selects the device data import option): On the user side, in response to the selection operation for the device data import option, a device data import request is sent to the server.
[0198] On the server side, the user's historical exercise data is imported from the wearable device, and a user profile card is sent back to the user. The user profile card includes basic user information and at least one exercise data item determined based on the historical exercise data.
[0199] On the user side, in response to an edit trigger operation on a target motion data item in the user profile card, an editing overlay corresponding to the target motion data item is displayed. The editing overlay displays the editable current value of the target motion data item and a save control.
[0200] On the user side, in response to a triggered operation on the save control, the user profile card is updated based on the edited current value, and the updated profile data is sent to the server.
[0201] On the server side, the target plan is generated based on the updated user profile card.
[0202] The second scenario (where the user selects "Confirm" and there is no device option): On the user side, in response to the selection operation of the "confirm no device" option, a "no device" confirmation message is sent to the server.
[0203] On the server side, in response to the no-device confirmation information, a data collection card is sent back to the user terminal. The data collection card displays a first data collection question and a first set of options corresponding to the first data collection question.
[0204] On the user side, in response to the selection operation for the first target option in the first option set, the user sends the first selection result to the server.
[0205] The server determines a second data collection problem based on the first selection result and feeds back the second data collection problem and the second set of options corresponding to the second data collection problem to the user.
[0206] On the user side, in response to the selection operation for the second target option in the second option set, the user sends the second selection result to the server. This process continues until all data collection questions have been answered.
[0207] On the user side, in response to the completion of the data collection card filling operation, a data collection completion message is sent to the server.
[0208] On the server side, based on the updated archive data (first case) or the selection results for each data collection question in the data collection card (second case), a plan target recommendation card is fed back to the user. The plan target recommendation card includes at least one candidate plan target, which is determined based on the selection results.
[0209] On the user side, in response to the selection operation of the selected plan target among the at least one candidate plan targets, the target selection information is sent to the server.
[0210] On the server side, in response to the target selection information, a training frequency setting area is fed back to the user side. The training frequency setting area contains at least one week selection control. The week selection control is used to respond to user operations and determine at least one target week from the week set for executing the target plan.
[0211] On the user side, in response to the week selection operation and plan confirmation operation of the week selection control, a plan confirmation message is sent to the server.
[0212] On the server side, in response to the plan confirmation information, the target plan is generated, and a plan overview card is fed back to the user. The plan overview card includes the total training amount, total training period, and total number of training sessions for the target plan.
[0213] On the user side, in response to a triggered operation on the plan overview card, a plan launch page display request is sent to the server.
[0214] On the server side, in response to the request to display the plan launch page, the plan launch page data is fed back to the client. The plan launch page displays the planned items corresponding to each date in the target plan and includes a plan start control.
[0215] On the user side, in response to the trigger operation of the plan start control, a plan start confirmation message is sent to the server.
[0216] On the server side, in response to the plan start confirmation information, the server sends back calendar synchronization request interface data to the user. The calendar synchronization request interface is used to request access permissions to external calendars.
[0217] On the user side, in response to the authorization operation on the calendar synchronization request interface, authorization information is sent to the server.
[0218] On the server side, the planned items corresponding to each date in the target plan are added to the external calendar, and the calendar component data is fed back to the user.
[0219] On the user's end, a calendar component is permanently displayed on the dialog page. The calendar component is used to view the planned items corresponding to each date in the target plan.
[0220] Understandable, Figure 12Some operations performed by the server in the illustrated embodiments can also be performed locally by the user in some implementations, which can be flexibly configured according to the user's computing power and application scenario. For example, the dynamic determination of subsequent data collection questions in the data collection card (i.e., generating the next question based on the user's selection result of the previous question) can be completed by the inference model executed locally on the user, without relying on the server's computing resources, thus ensuring the smooth progress of the data collection process even when the network connection is unstable; as another example, the generation operation of the target plan can also be directly generated locally by the user based on the user's selection result, thereby reducing the number of interactions with the server, improving the response speed of plan generation, and reducing privacy concerns during user data transmission. In addition, the determination or generation of device binding cards, user profile cards, data collection cards and their contained data collection questions and option results, training frequency setting area, plan launch page data, calendar synchronization request interface data, etc., can also be implemented at least partially by the user based on locally preloaded data, thereby reducing the number of interactions with the server and improving the response speed of plan generation. Figure 12 The division of labor between the server and the user in the illustrated embodiment is merely an example and does not constitute a limitation on the executing entity.
[0221] In an optional embodiment, Figure 12 At least some of the operations performed by the server can be performed by the user, for example, by the target agent calling other functional modules in the user.
[0222] This specification provides a plan generation method applied to a user terminal, displaying a dialogue page with a target agent. In response to the creation of a target plan on the dialogue page, a calendar component is permanently displayed on the dialogue page. The target plan is created by the target agent based on a plan generation request received on the dialogue page. The calendar component is used to view the planned items corresponding to each date in the target plan. Because the calendar component is permanently displayed on the dialogue page, the user can continuously view the planned items corresponding to each date in the target plan without leaving the dialogue context, thus balancing the continuous visibility of the plan content with the continuity of the dialogue interaction.
[0223] See Figure 13 , Figure 13 A flowchart of a method for displaying planned data, provided as an embodiment of this specification, is shown below. Figure 13 As shown, the client is mainly responsible for displaying the chat page and plan details page, receiving and responding to user interactions, while the server is located on a remote server or cloud service provider and is responsible for data processing and storage.
[0224] On the user side, in response to entering the dialogue page with the target intelligent agent, a page entry information is sent to the server.
[0225] On the server side, the current system date is obtained, target items matching the current date are filtered from the target plans, and the target items and calendar component data are fed back to the user.
[0226] On the user's end, a calendar component is permanently displayed on the dialogue page, showing the target item. The target item belongs to a target plan, which is created by the target agent based on a plan generation request received on the dialogue page. The calendar component is used to view the planned items corresponding to each date in the target plan.
[0227] On the user's end, in response to the viewing operation of the target item, a request to display the plan details page is sent to the server.
[0228] On the server side, in response to the request to display the plan details page, the plan details page data is fed back to the user.
[0229] On the user's end, a plan details page is displayed. The plan details page includes basic plan information, a statistical data display area, and a plan details display area. The statistical data display area includes at least one data indicator card, each data indicator card displaying a data chart corresponding to a statistical data indicator of the target plan. The plan details display area displays a plan calendar and plan cards. The plan calendar shows the distribution of planned items for the target plan on each date, and the plan cards display the details of planned items corresponding to each date in the target plan. When the plan details page is displayed, it uses the current date as the anchor point: the current date in the plan calendar is presented in a way that distinguishes it from other dates, and the plan card corresponding to the current date is placed in a preset position within the visible area.
[0230] On the user's end, in response to a first-direction swipe operation on the plan details display area within the plan details page, the statistics display area is hidden.
[0231] On the user's end, in response to a second-direction swipe operation within the plan details display area on the plan details page, the statistical data display area is expanded. The first and second directions can be swipe operations in opposite directions.
[0232] On the user side, in response to the view switching operation of the planning calendar, the display switches between weekly and monthly views. The planned tasks corresponding to each date in the planning calendar are presented as icons, with different display styles for icons corresponding to planned tasks of different training intensities.
[0233] On the user's end, in response to the target task completion event corresponding to the current date, a training completion confirmation message is sent to the server. The target task completion event can be triggered on the user's end after detecting that the user has completed the training for the day, for example, by the user clicking the "End Training" control or by the system automatically detecting training completion through exercise data.
[0234] On the server side, in response to the training completion confirmation information, the server retrieves the training data for the current date and sends the evaluation card data back to the user. The evaluation card includes at least one evaluation dimension card, each evaluation dimension card displaying evaluation information corresponding to one evaluation dimension of the target item; the evaluation dimension includes at least one of training performance score, running posture analysis, pace analysis, heart rate analysis, and cadence analysis.
[0235] On the user's end, the evaluation card is displayed on the dialog page.
[0236] On the user side, in response to a card switching operation for the evaluation card, the display switches between the first evaluation dimension card and the second evaluation dimension card. The card switching operation includes a horizontal swipe operation on the evaluation card or a click operation on a switching control on the evaluation card.
[0237] On the user side, in response to a trigger operation that expands the control for the information in the evaluation dimension card, the remaining evaluation information for the corresponding evaluation dimension is displayed in the evaluation dimension card. The evaluation dimension card displays a portion of the evaluation information for the corresponding evaluation dimension by default.
[0238] Understandable, Figure 13 Some operations performed by the server in the illustrated embodiments can also be performed locally by the user in some implementations, which can be flexibly configured according to the user's computing power and application scenario. For example, the target item matching operation (i.e., filtering the corresponding target item from the target plan based on the current system date) can be completed locally by the user, thus eliminating the need to send a request to the server every time the user enters the dialog page, reducing network interaction latency and improving page loading speed. As another example, the operation of generating plan details page data can be completed locally by the user based on locally stored plan and training data, thus eliminating the need to send a request to the server every time the user jumps to the plan details page, reducing network interaction latency and improving page loading speed. Furthermore, the evaluation information generation operation of the evaluation card can also be completed locally by the user based on locally stored plan and training data, allowing the user to receive evaluation feedback immediately after training without waiting for server processing and response. Figure 13 The division of labor between the server and the user in the illustrated embodiment is merely an illustrative example and does not constitute a limitation on the executing entity. In optional embodiments, Figure 13At least some of the operations performed by the server can be performed by the user, for example, by the target agent calling other functional modules in the user.
[0239] This specification provides a method for displaying planned data, applied to a user terminal. In response to entering a dialogue page with a target agent, the method displays target items matching the current date on the dialogue page. The dialogue page includes a fixed-display calendar component. In response to a viewing operation of the target item, a plan details page for the target plan is displayed. Because the calendar component is fixedly displayed on the dialogue page, and the system automatically matches and displays the corresponding target item from the target plan based on the current date upon entering the page, a linkage is established between the calendar component and the current date. Users do not need to manually browse the calendar to find their daily schedule; they can directly learn about the tasks that need to be performed on the current date from the dialogue page. Furthermore, after the user performs a viewing operation on the target item, the system further displays the plan details page, allowing the user to naturally transition from the overview information on the dialogue page to the complete information on the details page, achieving a seamless connection from the target item matching the current date to the complete plan content. Meanwhile, after users complete their daily goals, the target agent proactively pushes evaluation cards to the dialogue page. These evaluation cards can be switched between different evaluation dimensions using a card switching operation, and users can view the complete evaluation information as needed through the information expansion control. This allows users to complete the entire process from viewing the daily schedule and execution plan to obtaining training feedback on the same dialogue page, further improving the continuity of training management and user experience.
[0240] Corresponding to the above method embodiments, this specification also provides embodiments of a planning and generation apparatus. Figure 14 This is a schematic diagram illustrating the structure of a plan generation device according to one embodiment of this specification. This plan generation device can be applied to a user terminal, such as... Figure 14 As shown, the device includes: Dialogue module 1402 is configured to display a dialogue page with the target intelligent agent; The plan creation module 1404 is configured to display a calendar component on the dialogue page in response to the completion of the creation of the target plan on the dialogue page; wherein the target plan is created by the target agent based on the plan generation request received on the dialogue page; the calendar component is used to view the planned items corresponding to each date in the target plan.
[0241] Optionally, the plan creation module 1404 is further configured to: in response to completing the creation of the target plan on the dialog page, display a plan overview card on the dialog page; in response to a trigger operation on the plan overview card, jump to a plan launch page, the plan launch page displays the plan items corresponding to each date in the target plan and includes a plan start control; in response to a trigger operation on the plan start control, return from the plan launch page to the dialog page, and display the calendar component on the dialog page.
[0242] Optionally, the plan creation module 1404 is further configured to: in response to a trigger operation on the plan activation control, display a calendar synchronization request interface, the calendar synchronization request interface being used to request access permissions to an external calendar; and in response to an authorization operation on the calendar synchronization request interface, add the planned items corresponding to each date in the target plan to the external calendar.
[0243] Optionally, the plan creation module 1404 is further configured to: obtain the set schedule information from the external calendar; when the corresponding date of the schedule information arrives, if the execution period of the schedule information conflicts with the execution period of the planned item on the corresponding date, display plan confirmation information on the dialog page, the plan confirmation information being used to ask the user whether to execute or adjust the target planned item on the corresponding date in the target plan as scheduled.
[0244] Optionally, the plan creation module 1404 is further configured to: in response to receiving the plan generation request in the dialog page, display a data collection card in the dialog page, the data collection card displaying a first data collection question and a first set of options corresponding to the first data collection question; in response to a selection operation for a first target option in the first set of options, display a second data collection question and a second set of options corresponding to the second data collection question in the dialog page, the second data collection question being determined based on the first target option; and in response to a completion operation for the data collection card, complete the creation of the target plan based on the selection results for each data collection question in the data collection card.
[0245] Optionally, the plan creation module 1404 is further configured to: in response to a completion operation for the data collection card, display a plan target recommendation card in the dialog page, the plan target recommendation card including at least one candidate plan target, the candidate plan target being determined based on the selection result; and in response to a selection operation for a selected plan target among the at least one candidate plan target, generate the target plan.
[0246] Optionally, the plan creation module 1404 is further configured to: in response to a selection operation for a selected plan target among the at least one candidate plan targets, display a training frequency setting area corresponding to the selected plan target, the training frequency setting area including at least one week selection control, the week selection control being used to determine at least one target week for executing the above-mentioned target plan from a set of weeks in response to a user operation; and generate the target plan in response to a week selection operation for the week selection control.
[0247] Optionally, the plan creation module 1404 is further configured to: in response to receiving the plan generation request in the dialog page, display a device binding card in the dialog page, the device binding card including a device data import option and a confirm no device option, the device data import option being used to trigger the import of the user's historical exercise data from the wearable device; in response to a selection operation for the device data import option, import the user's historical exercise data from the wearable device, and display a user profile card in the dialog page, the user profile card including basic user information and at least one exercise data item determined based on the historical exercise data.
[0248] Optionally, the plan creation module 1404 is further configured to: in response to an edit trigger operation on a target motion data item in the user profile card, display an editable overlay corresponding to the target motion data item, the editable overlay displaying the editable current value of the target motion data item and a save control; the current value is determined based on the user's historical motion data; in response to a trigger operation on the save control, update the user profile card based on the edited current value; and generate the target plan based on the updated user profile card.
[0249] This specification provides a plan generation device, including a dialogue module and a plan creation module. Through the interaction and cooperation between these modules, a dialogue page with a target agent is displayed. In response to the creation of a target plan on the dialogue page, a calendar component is permanently displayed on the dialogue page. The target plan is created by the target agent based on a plan generation request received on the dialogue page. The calendar component is used to view the planned items corresponding to each date in the target plan. Because the calendar component is permanently displayed on the dialogue page, users can continuously view the planned items corresponding to each date in the target plan without leaving the dialogue context. This balances the continuous visibility of plan content with the continuity of dialogue interaction, simplifies the user's operation path between plan viewing and dialogue communication, and improves the efficiency of obtaining plan information.
[0250] The above is an illustrative scheme of a plan generation apparatus according to this embodiment. It should be noted that the technical solution of the plan generation apparatus and the technical solution of the plan generation method described above belong to the same concept. For details not described in detail in the technical solution of the plan generation apparatus, please refer to the description of the technical solution of the plan generation method described above.
[0251] Corresponding to the above method embodiments, this specification also provides an embodiment of a plan display device. Figure 15 This is a schematic diagram illustrating the structure of a planning display device according to one embodiment of this specification. The planning display device can be applied to a broadcaster's end, such as... Figure 15 As shown, the device includes: The dialogue module 1502 is configured to respond to entering a dialogue page with a target agent, and to display target items matching the current date on the dialogue page; wherein, the dialogue page includes a fixedly displayed calendar component, the target items belong to a target plan, the target plan is created by the target agent based on a plan generation request received on the dialogue page, and the calendar component is used to view the plan items corresponding to each date in the target plan; The plan display module 1504 is configured to display the plan details page of the target plan in response to a viewing operation of the target item.
[0252] Optionally, the plan details page includes basic plan information, a statistical data display area, and a plan details display area; the statistical data display area includes at least one data indicator card, each data indicator card is used to display a data chart corresponding to a statistical data indicator of the target plan; the plan details display area is used to display a plan calendar and plan cards, the plan calendar is used to display the distribution of planned items of the target plan on each date, and the plan cards are used to display the details of planned items corresponding to each date in the target plan.
[0253] Optionally, the plan display module 1504 is further configured to: hide the statistical data display area in response to a first-direction sliding operation on the plan details display area; and expand the display of the statistical data display area in response to a second-direction sliding operation on the plan details display area.
[0254] Optionally, the plan display module 1504 is further configured to: in the plan details page, position the plan details display area to the position corresponding to the current date, wherein the current date in the plan calendar is presented in a display mode different from other dates, and the plan card corresponding to the current date is placed in a preset position within the visible area.
[0255] Optionally, the planning calendar supports view switching; the planning display module 1504 is further configured to: switch between a weekly view and a monthly view in response to a view switching operation on the planning calendar, wherein the weekly view displays the calendar for the current week and the monthly view displays the calendar for the current month.
[0256] Optionally, the planned items corresponding to each date displayed in the planning calendar are presented in the form of icons, and the display style of the icons corresponding to planned items with different training intensities is different; the display style includes at least one of icon color, icon shape or icon size.
[0257] Optionally, the plan display module 1504 is further configured to: in response to the completion event of the target item corresponding to the current date, display an evaluation card in the dialog page; the evaluation card includes at least one evaluation dimension card, each evaluation dimension card is used to display evaluation information corresponding to one evaluation dimension of the target item; the evaluation dimension includes at least one of training performance score, running posture analysis, pace analysis, heart rate analysis, and cadence analysis.
[0258] Optionally, the evaluation card includes a first evaluation dimension card and a second evaluation dimension card; the plan display module 1504 is further configured to: in response to a card switching operation on the evaluation card, switch from displaying the first evaluation dimension card to displaying the second evaluation dimension card, or switch from displaying the second evaluation dimension card to displaying the first evaluation dimension card; the card switching operation includes a horizontal swipe operation on the evaluation card or a click operation on a switching control on the evaluation card.
[0259] Optionally, the evaluation dimension card displays partial evaluation information for the corresponding evaluation dimension in the default state and includes an information expansion control. The plan display module 1504 is further configured to: in response to a trigger operation on the information expansion control, expand and display the remaining evaluation information for the corresponding evaluation dimension in the evaluation dimension card.
[0260] This specification provides a plan display device, including a dialogue module and a plan display module. Through the interaction and cooperation between the modules, in response to entering a dialogue page with a target intelligent agent, the target item matching the current date is displayed on the dialogue page. The dialogue page includes a fixed-display calendar component, and the target item belongs to the target plan. In response to a viewing operation of the target item, a plan details page of the target plan is displayed. Because the calendar component is fixedly displayed on the dialogue page, and the system automatically matches and displays the corresponding target item from the target plan based on the current date when entering the page, a linkage is formed between the calendar component and the current date. Users do not need to manually browse the calendar to find the arrangements for the day; they can directly know the items that need to be performed on the current date on the dialogue page. Since the system further displays the plan details page after the user performs a viewing operation on the target item, the user can naturally transition from the overview information on the dialogue page to the complete information on the details page, achieving a seamless connection from the target item matching the current date to the complete plan content, further improving the user's operational efficiency from plan overview to detailed viewing.
[0261] The above is an illustrative scheme of a planning display device according to this embodiment. It should be noted that the technical solution of this planning display device and the technical solution of the planning display method described above belong to the same concept. For details not described in detail in the technical solution of the planning display device, please refer to the description of the technical solution of the planning display method described above.
[0262] Figure 16 A structural block diagram of a computing device according to one embodiment of this specification is shown. The components of the computing device 1600 include, but are not limited to, a memory 1610 and a processor 1620. The processor 1620 is connected to the memory 1610 via a bus 1630, and a database 1650 is used to store data.
[0263] The computing device 1600 also includes an access device 1640, which enables the computing device 1600 to communicate via one or more networks 1660. Examples of such networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 1640 may include one or more of any type of wired or wireless network interface (e.g., a network interface card (NIC)), such as an IEEE 802.18 Wireless Local Area Network (WLAN) wireless interface, a Wi-MAX (Worldwide Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, or a Near Field Communication (NFC) interface.
[0264] In one embodiment of this specification, the above-described components of the computing device 1600 and Figure 16 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 16 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.
[0265] The computing device 1600 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or personal computers (PCs). The computing device 1600 can also be a mobile or stationary server.
[0266] The processor 1620 is configured to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the above-described plan generation method or the steps of the above-described plan display method.
[0267] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the map display method described above belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the plan generation method or plan display method described above.
[0268] An embodiment of this specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the above-described plan generation method or the steps of the above-described plan presentation method.
[0269] The above is an illustrative embodiment of a computer-readable storage medium. It should be noted that the technical solution of this storage medium belongs to the same concept as the technical solution of the aforementioned plan generation method or plan display method. Details not described in detail in the technical solution of the storage medium can be found in the description of the technical solution of the aforementioned plan generation method or plan display method.
[0270] An embodiment of this specification also provides a computer program, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the above-described plan generation method or implement the steps of the above-described plan display method.
[0271] The above is an illustrative example of a computer program according to this embodiment. It should be noted that the technical solution of this computer program belongs to the same concept as the technical solution of the map display method described above. Details not described in detail in the technical solution of the computer program can be found in the descriptions of the technical solutions of the plan generation method or plan display method described above.
[0272] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0273] Computer instructions include computer program code, which can be in the form of source code, object order code, executable files, or certain intermediate forms. Computer-readable media can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in computer-readable media can be appropriately added or removed according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.
[0274] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.
[0275] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0276] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.
Claims
1. A method for generating plans, characterized in that, include: Displays the dialogue page with the target intelligent agent; In response to the completion of the creation of the target plan on the dialogue page, a calendar component is permanently displayed on the dialogue page; wherein, the target plan is created by the target agent based on the plan generation request received on the dialogue page; the calendar component is used to view the planned items corresponding to each date in the target plan.
2. The method according to claim 1, characterized in that, The method of fixing the calendar component on the dialog page includes: In response to the completion of the creation of the target plan on the dialog page, a plan overview card is displayed on the dialog page; In response to a trigger operation on the plan overview card, the system jumps to the plan launch page, which displays the plan items corresponding to each date in the target plan and includes a plan start control; In response to a triggering operation on the schedule start control, the system returns from the schedule start page to the dialog page and displays the calendar component on the dialog page.
3. The method according to claim 2, characterized in that, Also includes: In response to the triggering operation of the plan start control, a calendar synchronization request interface is displayed, which is used to request access to an external calendar; In response to the authorization operation on the calendar synchronization request interface, the planned items corresponding to each date in the target plan are added to the external calendar.
4. The method according to claim 3, characterized in that, Also includes: Retrieve the set schedule information from the external calendar; When the corresponding date of the schedule information arrives, if the execution period of the schedule information conflicts with the execution period of the planned items on the corresponding date, a plan confirmation message is displayed on the dialog page. The plan confirmation message is used to ask the user whether to execute or adjust the target planned items on the corresponding date in the target plan as scheduled.
5. The method according to claim 1, characterized in that, The process of creating the target plan on the dialog page includes: In response to receiving the plan generation request in the dialog page, a data collection card is displayed in the dialog page, and the data collection card displays a first data collection question and a first set of options corresponding to the first data collection question; In response to a selection operation for a first target option in the first set of options, a second data collection question and a second set of options corresponding to the second data collection question are displayed on the dialog page, the second data collection question being determined based on the first target option; In response to the completion of the data collection card, the creation of the target plan is completed based on the selection results of each data collection question within the data collection card.
6. The method according to claim 5, characterized in that, In response to the completion of the data collection card, the creation of the target plan is completed based on the selection results of each data collection question within the data collection card, including: In response to the completion of the data collection card, a plan target recommendation card is displayed on the dialog page. The plan target recommendation card includes at least one candidate plan target, which is determined based on the selection result. In response to a selection operation for a selected planning target among the at least one candidate planning targets, the target plan is generated.
7. The method according to claim 6, characterized in that, The step of generating the target plan in response to a selection operation for a selected plan target among the at least one candidate plan targets includes: In response to a selection operation for a selected plan target among the at least one candidate plan targets, a training frequency setting area corresponding to the selected plan target is displayed. The training frequency setting area includes at least one week selection control. The week selection control is used to determine at least one target week for executing the above-mentioned target plan from the set of weeks in response to a user operation. The target schedule is generated in response to a week selection operation on the week selection control.
8. The method according to claim 1, characterized in that, The process of creating the target plan on the dialog page includes: In response to receiving the plan generation request on the dialog page, a device binding card is displayed on the dialog page. The device binding card includes a device data import option and a confirm no device option. The device data import option is used to trigger the import of the user's historical exercise data from the wearable device. In response to the selection of the device data import option, the user's historical exercise data is imported from the wearable device, and a user profile card is displayed on the dialog page. The user profile card includes basic user information and at least one exercise data item determined based on the historical exercise data.
9. The method according to claim 8, characterized in that, The method further includes: In response to an edit trigger operation on a target motion data item in the user profile card, an edit overlay corresponding to the target motion data item is displayed. The edit overlay displays the editable current value of the target motion data item and a save control. The current value is determined based on the user's historical motion data. In response to a trigger operation on the save control, the user profile card is updated based on the edited current value; The target plan is generated based on the updated user profile card.
10. A method for presenting a plan, characterized in that, include: In response to entering a dialogue page with the target agent, the dialogue page displays target items matching the current date; wherein, the dialogue page includes a fixed-display calendar component, the target items belong to a target plan, the target plan is created by the target agent based on a plan generation request received on the dialogue page, and the calendar component is used to view the planned items corresponding to each date in the target plan; In response to a viewing action of the target item, the plan details page of the target plan is displayed.
11. The method according to claim 10, characterized in that, The plan details page includes basic plan information, a statistical data display area, and a plan details display area. The statistical data display area includes at least one data indicator card, each data indicator card is used to display a data chart corresponding to a statistical data indicator of the target plan. The plan details display area is used to display a plan calendar and plan cards. The plan calendar is used to display the distribution of planned items of the target plan on each date, and the plan cards are used to display the details of planned items corresponding to each date in the target plan.
12. The method according to claim 11, characterized in that, Also includes: In response to a first-direction swipe operation on the plan details display area, the statistics display area is hidden; In response to a second-direction swipe operation on the plan details display area, the statistical data display area is expanded.
13. The method according to claim 11, characterized in that, The plan details page displaying the target plan includes: In the plan details page, the plan details display area is positioned at the location corresponding to the current date. The current date in the plan calendar is presented in a display method that is different from other dates, and the plan card corresponding to the current date is placed in a preset position within the visible area.
14. The method according to claim 11, characterized in that, The schedule calendar supports view switching; the method also includes: In response to a view switching operation for the planned calendar, the display is switched between a weekly view and a monthly view, wherein the weekly view displays the calendar for the current week and the monthly view displays the calendar for the current month.
15. The method according to claim 11, characterized in that, The planned items corresponding to each date displayed in the plan calendar are presented in the form of icons. The display style of the icons corresponding to planned items with different training intensities is different; the display style includes at least one of icon color, icon shape or icon size.
16. The method according to claim 10, characterized in that, Also includes: In response to the completion event of the target item corresponding to the current date, an evaluation card is displayed on the dialog page; the evaluation card includes at least one evaluation dimension card, and each evaluation dimension card is used to display evaluation information corresponding to one evaluation dimension of the target item; the evaluation dimension includes at least one of training performance score, running posture analysis, pace analysis, heart rate analysis, and cadence analysis.
17. The method according to claim 16, characterized in that, The evaluation card includes a first evaluation dimension card and a second evaluation dimension card; the method further includes: In response to a card switching operation on the evaluation card, the display can switch from showing the first evaluation dimension card to showing the second evaluation dimension card, or from showing the second evaluation dimension card to showing the first evaluation dimension card; the card switching operation includes a horizontal swipe operation on the evaluation card or a click operation on a switching control on the evaluation card.
18. The method according to claim 16, characterized in that, The evaluation dimension card displays partial evaluation information for the corresponding evaluation dimension by default and includes information expansion controls. The method further includes: In response to the triggering operation of the information expansion control, the remaining evaluation information for the corresponding evaluation dimension is expanded and displayed in the evaluation dimension card.
19. A plan generation device, characterized in that, include: The dialogue module is configured to display a dialogue page with the target intelligent agent; The plan creation module is configured to display a calendar component on the dialogue page in response to the completion of the creation of a target plan on the dialogue page; wherein the target plan is created by the target agent based on a plan generation request received on the dialogue page; the calendar component is used to view the planned items corresponding to each date in the target plan.
20. A planning display device, characterized in that, include: The dialogue module is configured to respond to entering a dialogue page with a target agent, and to display target items matching the current date on the dialogue page; wherein, the dialogue page includes a fixed-display calendar component, the target items belong to a target plan, the target plan is created by the target agent based on a plan generation request received on the dialogue page, and the calendar component is used to view the plan items corresponding to each date in the target plan; The plan display module is configured to display the plan details page of the target plan in response to a viewing operation of the target item.
21. A computing device, characterized in that, include: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the plan generation method according to any one of claims 1-9, or the steps of the plan presentation method according to any one of claims 10-18.
22. A computer-readable storage medium, characterized in that, It stores computer-executable instructions that, when executed by a processor, implement the steps of the plan generation method according to any one of claims 1-9, or the steps of the plan presentation method according to any one of claims 10-18.
23. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the steps of the plan generation method according to any one of claims 1-9, or the steps of the plan presentation method according to any one of claims 10-18.
