CN117130527A - Schedule management method, electronic device and computer-readable storage medium - Google Patents

Abstract

The application relates to the technical field of electronics, and provides a schedule management method, electronic equipment and a computer readable storage medium. The method comprises the steps of displaying a schedule interface, wherein the schedule interface is an interface of a schedule application program APP, the schedule interface is used for displaying schedule information, the schedule interface comprises at least one action control, each action control corresponds to one interface to be skipped, and the at least one action control is a control generated in response to the operation of adding actions of a user; receiving a selection operation of a user on a target control in the at least one action control; and responding to the selection operation, and jumping from the schedule interface to a target interface to be jumped corresponding to the target control. The method can be convenient for a user to operate, and has flexible application scenes.

Description

Schedule management method, electronic device and computer-readable storage medium

Technical field

This application relates to the field of electronic technology, specifically to a schedule management method, electronic equipment and computer-readable storage media.

Background technique

As the pace of people's production and life becomes faster and faster, more and more daily tasks need to be handled, and the need for effective schedule management becomes more and more urgent. As a common terminal device, smartphones have become an important tool for people to record and manage their schedules.

People often manage schedules through calendar or to-do applications (APPs) installed on terminal devices, for example, recording meeting schedule times through a calendar APP.

In the current calendar APP, the dial-in number and the link to join the online meeting can be provided for the online meeting schedule, and the application scenarios are relatively simple.

Contents of the invention

This application provides a schedule management method, device, chip, electronic device, computer-readable storage medium and computer program product, which can provide rich interactive scenarios and facilitate user use.

In the first aspect, a schedule display interface is provided. The schedule interface is used to display schedule information. The schedule interface includes at least one action control. Each action control corresponds to an interface to be jumped. The at least one action control is in response to the user's A control generated by the operation of adding an action; receiving the user's selection operation on the target control in at least one action control; in response to the selection operation, jumping from the schedule interface to the target to-be-jumped interface corresponding to the target control.

When viewing the schedule, the user can directly select the required shortcut key (action control) on the schedule interface, and then operate the terminal device to directly jump to the target to-be-jumped interface corresponding to the target control, without the need for the user to operate other third-party APPs or Open the corresponding interface, so the operation is more convenient. Moreover, this method enables users to add shortcut keys for different actions according to their own needs, realizes the user's need for customized shortcut keys (action controls), and provides users with a richer and more convenient interactive experience.

In some embodiments, before displaying the schedule interface, the method further includes: displaying an interface for creating a new schedule, which is used by the user to create a new schedule; receiving an operation of adding an action input by the user; and responding to the operation of adding an action. The icon of the target action corresponding to the target control is added to the schedule interface. The target action is the action that jumps to the target interface to be jumped.

Users can actively associate the target action with the schedule through the operation of adding an action in the new schedule interface, so as to associate the target action with the corresponding schedule, thereby adding the icon of the target action corresponding to the target control in the new schedule interface. , making it easier for users to jump directly to the target interface to be jumped through the target control.

In some embodiments, the operation of adding an action is an operation of selecting an icon of a target action in a candidate action list, and the candidate action list at least includes an icon of the target action.

Users can subjectively select the actions required by the current schedule from the list of optional actions formed by multiple actions that can be added, and add them, which can realize customized schedule actions and provide users with a richer and more convenient interactive experience.

In some embodiments, receiving the operation of adding an action input by the user includes: receiving the first operation input by the user in the interface of creating a new schedule, where the first operation is the operation of the user selecting the add action option; in response to the first operation, displaying A list of actions to be selected; receiving a second operation input by the user, where the second operation is a selection operation for an icon of a target action in the action list to be selected; and selecting the target action in response to the second operation.

The user can select the add action option in the interface of creating a new schedule. When the list of actions to be selected is displayed, the user selects the icon of the target action, thereby selecting the target action as the action corresponding to the new schedule, which facilitates the user to jump directly to the target through the target control. The target interface corresponding to the action is to be redirected.

In some embodiments, before displaying the first interface, the method further includes: displaying the target interface to be jumped; receiving a sharing operation input by the user; and in response to the sharing operation, displaying the target control corresponding to the target interface to be jumped in the schedule interface.

When users browse pages or use various APPs, they can display the target control corresponding to the interface to be jumped to in the schedule interface directly through the sharing operation in the interface they are browsing. This method can add actions to jump to the page in different interfaces of different applications through the sharing operation function. The types of actions that can be added are not limited by the list of actions to be selected, making the types of actions that can be added more abundant. , more interactive.

In some embodiments, receiving the sharing operation input by the user includes: receiving a third operation input by the user, where the third operation is the user's operation of selecting the sharing control in the target interface to be jumped; in response to the third operation, displaying at least one Objects to be shared, at least one of the objects to be shared includes a calendar application APP; receiving a fourth operation input by the user, the fourth operation being an operation for the user to select the schedule APP from at least one object to be shared; in response to the fourth operation, displaying There are schedule controls and new schedule controls; the fifth operation of receiving user input, the fifth operation is the operation of the user selecting the target control from the existing schedule control and the new schedule control; displaying the schedule editing interface corresponding to the target control, in the schedule editing interface Includes the icon of the target action corresponding to the target control. The target action is the action to jump to the target interface to be jumped.

By selecting the sharing control (share button) in the currently used interface, the user can continue to select the schedule APP in the pop-up object to be shared, and then select the existing schedule control or create a new schedule control to achieve the currently used interface as the target to be shared. Jump interface, add the action of jumping to the target interface to be jumped to the schedule that needs to be added, so that users can add it at any time when using the terminal device APP or browsing the web. The functions are richer and the interactivity is more powerful.

In some embodiments, before displaying the schedule interface, the method further includes: obtaining a schedule template. The schedule template includes a correspondence relationship between at least one schedule time, at least one schedule identifier, and at least one interface to be jumped. The at least one interface to be jumped includes The target interface to be jumped; according to the schedule template, the target control corresponding to the target interface to be jumped is displayed in the schedule interface.

The terminal device can also obtain a preset schedule template. The schedule template includes multiple existing schedules (schedule groups), and some or all of these existing schedules (schedule groups) have corresponding actions (APPs or links) added to them. . After the terminal device imports the configuration file of the schedule template, the action controls corresponding to the actions in the schedule template can be displayed in the corresponding schedule interface. Using calendar templates to set schedules eliminates the need for users to add corresponding actions for each schedule one by one, making the operation more convenient.

The above-mentioned ways of adding actions are diverse and flexible, can meet the needs of different scenarios and different users, and improve user experience.

In some embodiments, the schedule template is any one or more of a travel planning calendar template, a degree application calendar template, a snap-up event calendar template, and a competition calendar template.

In some embodiments, the number of controls of at least one action control is one; or, at least one action control is a menu control of multiple action controls, and the menu control is used to call out multiple action controls.

When there is one action corresponding to the schedule displayed on the schedule interface, the action control corresponding to the action can be directly displayed; when there are multiple actions corresponding to the schedule displayed on the schedule interface, the menu control can be directly displayed, and the user can Click the menu control to bring up multiple action controls, and then select the required target action among these multiple action controls. This display method can simplify the display interface and facilitate interface layout.

In some embodiments, the schedule interface is an interface of a schedule APP or an interface of a schedule card.

In some embodiments, the target interface to be jumped is the interface or target page of the target APP.

In some embodiments, the target APP is one of a conference APP, a shopping APP and a ticket purchase APP, a travel APP, a taxi APP, a phone call APP, a hotel reservation APP, a ticket reservation APP, a car rental APP, a tour guide reservation APP, a chat APP, and a payment APP. Type; the target page is one of shopping website pages, ticket purchase website pages, travel website pages, entry and exit website pages, embassy website pages, hotel reservation website pages, air ticket reservation website pages, and education bureau website pages.

The above-mentioned various APPs, various pages and various templates can meet the needs of different users. They are comprehensive and practical, fully meet the needs of users, and improve the user experience.

In a second aspect, a schedule management device is provided, including a unit composed of software and/or hardware, and the unit is used to execute any method in the technical solution described in the first aspect.

In a third aspect, an electronic device is provided. The electronic device includes: a processor, a memory, and an interface; the processor, the memory, and the interface cooperate with each other to enable the electronic device to execute any method in the technical solution described in the first aspect.

In a fourth aspect, embodiments of the present application provide a chip including a processor; the processor is configured to read and execute a computer program stored in a memory to execute any method in the technical solution described in the first aspect.

Optionally, the chip further includes a memory, and the memory is connected to the processor through circuits or wires.

Further optionally, the chip further includes a communication interface.

In a fifth aspect, a computer-readable storage medium is provided. A computer program is stored in the computer-readable storage medium. When the computer program is executed by a processor, the processor is caused to execute the technology described in the first aspect. any method in the scheme.

In a sixth aspect, a computer program product is provided. The computer program product includes: computer program code. When the computer program code is run on an electronic device, the electronic device causes the electronic device to execute the technical solution described in the first aspect. Either way.

Description of the drawings

Figure 1 is a schematic structural diagram of an example terminal device 100 provided by an embodiment of the present application;

Figure 2 is a software structure block diagram of the terminal device 100 provided by the embodiment of the present application;

Figure 3 is a schematic interface diagram of an example calendar APP provided by the embodiment of the present application;

Figure 4 is an interface change diagram of an example of creating a new schedule provided by the embodiment of the present application;

Figure 5 is another example of an interface change diagram for creating a new schedule provided by the embodiment of the present application;

Figure 6 is a schematic interface diagram of another calendar APP provided by the embodiment of the present application;

Figure 7 is an interface change diagram of an example of adding actions provided by the embodiment of the present application;

Figure 8 is another example of an interface change diagram for adding actions provided by the embodiment of the present application;

Figure 9 is a schematic interface diagram of another calendar APP provided by the embodiment of the present application;

Figure 10 is a schematic interface diagram of another schedule card provided by an embodiment of the present application;

Figure 11 is a schematic structural diagram of an example schedule management device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Among them, in the description of the embodiments of this application, unless otherwise stated, "/" means or, for example, A/B can mean A or B; "and/or" in this article is only a way to describe related objects. The association relationship means that there can be three relationships. For example, A and/or B can mean: A alone exists, A and B exist simultaneously, and B alone exists. In addition, in the description of the embodiments of this application, "plurality" refers to two or more than two.

Hereinafter, the terms “first”, “second” and “third” are used for descriptive purposes only and shall not be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Thus, features defined as "first", "second", and "third" may explicitly or implicitly include one or more of these features.

The schedule management method provided by the embodiment of the present application can be applied to mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, notebook computers, and super mobile personal computers. On terminal devices such as ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs), the embodiments of the present application do not place any restrictions on the specific types of terminal devices.

For example, FIG. 1 is a schematic structural diagram of an example terminal device 100 provided by an embodiment of the present application. The terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and user Identification module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or less components than shown in the figures, or combine some components, or split some components, or arrange different components. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), an image signal processor ( image signal processor (ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU), etc. . Among them, different processing units can be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the terminal device 100 . The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

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

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can separately couple the touch sensor 180K, charger, flash, camera 193, etc. through different I2C bus interfaces. For example, the processor 110 can be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to implement the touch function of the terminal device 100 .

The I2S interface can be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 can be coupled with the audio module 170 through the I2S bus to implement communication between the processor 110 and the audio module 170 . In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface to implement the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communications to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface to implement the function of answering calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 and the wireless communication module 160 . For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interfaces include camera serial interface (CSI), display serial interface (displayserial interface, DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the terminal device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the terminal device 100.

The GPIO interface can be configured through software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, display screen 194, wireless communication module 160, audio module 170, sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface that complies with USB standard specifications, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the terminal device 100, and can also be used to transmit data between the terminal device 100 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other terminal devices, such as AR devices.

It can be understood that the interface connection relationships between the modules illustrated in the embodiments of the present application are only schematic illustrations and do not constitute a structural limitation on the terminal device 100 . In other embodiments of the present application, the terminal device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through the wireless charging coil of the terminal device 100 . While charging the battery 142, the charging management module 140 can also provide power to the terminal device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, wireless communication module 160, etc. The power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the terminal device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. The structures of antenna 1 and antenna 2 in Figure 1 are only an example. Each antenna in terminal device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

A modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 110 and may be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide information including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), and global navigation satellite systems applied on the terminal device 100 (global navigation satellite system, GNSS), frequency modulation (FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the terminal device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (codedivision multiple access, CDMA), broadband code Wideband code division multiple access (WCDMA), time-division code division multiple access (TD-CDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM , and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou satellite navigation system (Beidounavigation satellite system, BDS), quasi-zenith satellite system (quasi- zenith satellitesystem (QZSS) and/or satellite based augmentation systems (SBAS).

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

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode). (AMOLED), flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diodes (QLED), etc. In some embodiments, the terminal device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The terminal device 100 can implement the shooting function through the ISP, camera 193, video codec, GPU, display screen 194, application processor, etc.

The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera sensor through the lens, the optical signal is converted into an electrical signal, and the camera sensor passes the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the terminal device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital video. The terminal device 100 may support one or more video codecs. In this way, the terminal device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can continuously learn by itself. The NPU can realize intelligent cognitive applications of the terminal device 100, such as image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes instructions stored in the internal memory 121 to execute various functional applications and data processing of the terminal device 100 . The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the terminal device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), etc.

The terminal device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .

Speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. The terminal device 100 can listen to music through the speaker 170A, or listen to hands-free calls.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the terminal device 100 answers a call or a voice message, the voice can be heard by bringing the receiver 170B close to the human ear.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak close to the microphone 170C with the human mouth and input the sound signal to the microphone 170C. The terminal device 100 may be provided with at least one microphone 170C. In other embodiments, the terminal device 100 may be provided with two microphones 170C, which in addition to collecting sound signals, may also implement a noise reduction function. In other embodiments, the terminal device 100 can also be equipped with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions, etc.

The headphone interface 170D is used to connect wired headphones. The headphone interface 170D may be a USB interface 130, or may be a 3.5 mm open mobile terminal platform (OMTP) standard interface or a Cellular Telecommunications Industry Association of the USA (CTIA) standard interface.

The pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor may include at least two parallel plates of conductive material. When a force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The terminal device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is performed on the display screen 194, the terminal device 100 detects the strength of the touch operation according to the pressure sensor 180A. The terminal device 100 may also calculate the touched position based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch location but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold is applied to the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

The gyro sensor 180B may be used to determine the motion posture of the terminal device 100 . In some embodiments, the angular velocity of the terminal device 100 about three axes (ie, x, y, and z axes) may be determined by the gyro sensor 180B. The gyro sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyro sensor 180B detects the angle at which the terminal device 100 shakes, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shake of the terminal device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

Air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

Magnetic sensor 180D includes a Hall sensor. The terminal device 100 can detect the opening and closing of the flip leather case using the magnetic sensor 180D. In some embodiments, when the terminal device 100 is a flip machine, the terminal device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. Then, based on the detected opening and closing status of the leather case or the opening and closing status of the flip cover, features such as automatic unlocking of the flip cover are set.

The acceleration sensor 180E can detect the acceleration of the terminal device 100 in various directions (generally three axes). When the terminal device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of terminal devices and be used in applications such as horizontal and vertical screen switching, pedometers, etc.

Distance sensor 180F for measuring distance. The terminal device 100 can measure distance through infrared or laser. In some embodiments, when shooting a scene, the terminal device 100 can use the distance sensor 180F to measure distance to achieve fast focusing.

Proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal device 100 emits infrared light through a light emitting diode. The terminal device 100 detects infrared reflected light from nearby objects using photodiodes. When sufficient reflected light is detected, it can be determined that there is an object near the terminal device 100 . When insufficient reflected light is detected, the terminal device 100 may determine that there is no object near the terminal device 100 . The terminal device 100 can use the proximity light sensor 180G to detect when the user holds the terminal device 100 close to the ear for talking, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in holster mode, and pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense ambient light brightness. The terminal device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the terminal device 100 is in the pocket to prevent accidental touching.

Fingerprint sensor 180H is used to collect fingerprints. The terminal device 100 can use the collected fingerprint characteristics to realize fingerprint unlocking, access application lock, fingerprint photography, fingerprint answering incoming calls, etc.

Temperature sensor 180J is used to detect temperature. In some embodiments, the terminal device 100 uses the temperature detected by the temperature sensor 180J to execute the temperature processing policy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the terminal device 100 reduces the performance of a processor located near the temperature sensor 180J in order to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the terminal device 100 heats the battery 142 to avoid the low temperature causing the terminal device 100 to shut down abnormally. In some other embodiments, when the temperature is lower than another threshold, the terminal device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

Touch sensor 180K, also called "touch panel". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation on or near the touch sensor 180K. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the terminal device 100 in a position different from that of the display screen 194 .

Bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human body's vocal part. The bone conduction sensor 180M can also contact the human body's pulse and receive blood pressure beating signals. In some embodiments, the bone conduction sensor 180M can also be provided in an earphone and combined into a bone conduction earphone. The audio module 170 can analyze the voice signal based on the vibration signal of the vocal vibrating bone obtained by the bone conduction sensor 180M to implement the voice function. The application processor can analyze the heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M to implement the heart rate detection function.

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The terminal device 100 may receive key input and generate key signal input related to user settings and function control of the terminal device 100 .

The motor 191 can generate vibration prompts. The motor 191 can be used for vibration prompts for incoming calls and can also be used for touch vibration feedback. For example, touch operations for different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The motor 191 can also respond to different vibration feedback effects for touch operations in different areas of the display screen 194 . Different application scenarios (such as time reminders, receiving information, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or separated from the terminal device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The terminal device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the terminal device 100 adopts eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100 .

The software system of the terminal device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of this application takes the Android system with a layered architecture as an example to illustrate the software structure of the terminal device 100 .

Figure 2 is a software structure block diagram of the terminal device 100 according to the embodiment of the present application. The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime (Android runtime) and system libraries, and kernel layer. The application layer can include a series of application packages.

As shown in Figure 2, the application package can include camera, gallery, calendar, calling, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 2, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the terminal device 100 . For example, call status management (including connected, hung up, etc.).

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a prompt sound is emitted, the terminal device vibrates, and the indicator light flashes, etc.

Android runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system.

The core library contains two parts: one part is the functional functions that need to be called by the Java language, and the other part is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

System libraries can include multiple functional modules. For example: surface manager (surface manager), media library (media libraries), 3D graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition, and layer processing.

2D Graphics Engine is a drawing engine for 2D drawing.

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

In order to facilitate understanding, the following embodiments of the present application will take the terminal device with the structure shown in Figure 1 and Figure 2 as an example, and combine the drawings and application scenarios to specifically describe the schedule management method provided by the embodiments of the present application.

As the pace of people's production and life becomes faster and faster, more and more daily tasks need to be handled, and the need for effective schedule management becomes more and more urgent. As a common terminal device, smartphones have become an important tool for people to record and manage their schedules. People often manage their schedules through calendar or to-do apps installed on their terminal devices, for example, using calendar apps to record meeting schedule times. In the current calendar APP, for online meeting schedules, only the dial-in number and meeting link for online meetings can be provided, and the application scenarios are relatively simple. When the user wants to perform more operations on the schedule of the online meeting, for example, when the user wants to access the video resources of the online meeting, the user needs to open the meeting APP to find the video resources or access the URL where the video resources are stored to view, which is relatively complicated to operate. Cumbersome.

In the embodiment of this application, the user can first add the required actions to the corresponding daily growth through the operation of adding actions, so that the terminal device generates corresponding shortcut keys according to different actions and displays them on the interface of the schedule APP. After that, the user can directly select the required shortcut key when viewing the schedule, and then operate the terminal device to jump directly to the corresponding interface, without the user having to operate other third-party apps or open the corresponding link, so the operation is more convenient. Moreover, this method enables users to add shortcut keys for different actions according to their own needs, realizes the user's need to customize shortcut keys, and provides users with a richer and more convenient interactive experience.

First, a detailed description is given of how users generate shortcut keys by adding actions. The above-mentioned schedule APP may be a calendar APP, a to-do APP or an agenda APP.

There are three ways to add actions to the schedule:

Method 1: Taking adding relevant actions to the schedule of the calendar APP as an example, the user can first operate the terminal device to open the calendar APP. At this time, the interface of the terminal device can display the interface of the calendar APP, for example, the month as shown in Figure 3 can be displayed. view. In the Calendar APP interface, users can click on the date to add a schedule and click the Add button "+" in the lower right corner of the screen to start the new schedule interface, or the default is to add the current day's schedule and directly click the Add button "+" to Launch the interface for creating a new schedule. Optionally, the interface of the calendar APP can also be a weekly view, a daily view, etc., which are not limited in the embodiment of the present application, as long as it can display an add button for adding a schedule. For example, if the current date is August 25 as shown in Figure 3, and the user needs to add a schedule for that day, he or she does not need to select a date, but directly clicks the add button "+" in the lower right corner of Figure 3 to enter the new schedule interface.

Figure a in Figure 4 is a schematic diagram of an interface for creating a new schedule provided by the embodiment of the present application. In the current interface, the user can enter the title of the schedule, select or enter the location, set the start time and end time of the schedule, and can also Click the "Add More Items" button to set and enter other schedule-related information, such as setting priorities, setting alarm clocks for reminders, adding note information, setting countdown day cards, etc. In this application, the "Add more items" button may also display an "Add action" button, for example, as shown in Figure b or c in Figure 4. The user can perform the operation shown in Figure b or c in Figure 4, that is, click the "Add Action" button to display the shortcut key "Add Action" for adding the corresponding action.

When the user clicks "Add Action", a list of actions to be selected may pop up on the interface of the terminal device, as shown in figure a in Figure 5, for example. The list of actions to be selected may include icons of multiple actions to be selected, and each icon of the action to be selected may correspond to an application or a link. Figure a in Figure 5 shows an example in which the candidate action list includes icons of four candidate actions: Action 1, Action 2, Action 3 and Action 4. Optionally, when there are more icons of actions to be selected, the user can also switch to display icons of other actions to be selected by sliding up and down the page of the list or the scroll bar of the list, so that the user can choose flexibly. When the user needs to add one of the candidate actions, he can click the icon of the candidate action to complete the operation of adding the action in the schedule. In figure b in Figure 5, the list of actions to be selected includes the following icons: ticket purchase 1, meeting 1, www.123456.com and www.654321.com as an example. For example, when the title of the user's newly created schedule is "Business Trip Tickets" and the location is "None" (not set), you can click the "Add Action" button to select the "Ticket Purchase 1" icon. At this time, "Grab Tickets" The action is added to the schedule named "Business trip ticket purchase", for example, as shown in picture c in Figure 5. The user can click the completion button "√" in the upper right corner on the interface shown in Figure 5 (c) to confirm the completion of the new schedule "Business Trip Ticket Purchase" operation. At this time, the shortcut "ticket grabbing" corresponding to the APP for purchasing ticket 1 can be generated on the interface of the calendar APP, as shown in Figure 6, for example. Users can click the "Grab Tickets" button to directly jump to the terminal device interface display to the ticket purchase 1 APP. Optionally, the user can continue to click the add button "+" in the lower right corner of the screen on the interface shown in Figure 6 to create other schedules. If the user selects the "Meeting 1" icon in the list of actions to be selected as shown in Figure 5 b, the "Join the meeting now" action is added to the schedule named "Test Meeting", for example, in Figure 5 As shown in Figure d. The user can click the completion button "√" in the upper right corner on the interface shown in Figure 5 d to confirm the completion of the operation of creating a new schedule "test meeting". At the same time, the shortcut "Join meeting now" corresponding to meeting 1 can be generated on the calendar APP interface.

Optionally, the above list of actions to be selected may also include options for other more selectable APPs, such as travel APPs, shopping APPs, navigation APPs, payment APPs, and other types of APPs; optionally, for each Different pages or operations of the selectable APP can also correspond to multiple selectable actions. For example, in addition to the actions corresponding to the dial-in number and link to join the meeting, the Conference 1 APP can also include actions corresponding to requesting to host the meeting, meeting online resource address (such as audio address, video address), etc. Among them, the action corresponding to the dial-in number for joining the conference is that the terminal device dials the number to join the online meeting; the action corresponding to the joining link is for the terminal device to open the joining link to access the online meeting; the action corresponding to requesting to host the conference is for the terminal device to initiate hosting to the host Application for permission; the action corresponding to the conference online resource address is for the terminal device to access the address to obtain the corresponding conference audio or video resources, which can include browsing or downloading audio and video resources.

Optionally, the above list of actions to be selected may also include icons of a specific set of shortcut instructions input in advance, and the user can directly select the required set of shortcut instructions and add them to the schedule as actions to be performed by the terminal device. When the user selects the icon corresponding to the shortcut instruction set in the schedule interface, the terminal device can execute the instructions in the shortcut instruction set in sequence, thereby jumping to the interface corresponding to the shortcut instruction set or completing the operation of the shortcut instruction set. Optionally, the above shortcut instruction set can be a downloaded instruction set template, or a shortcut instruction set customized by the user after multiple operations. The embodiments of the present application do not limit this, as long as the shortcut instruction set can instruct The terminal device only needs to display the interface expected by the user or complete the operation expected by the user (such as grabbing tickets and paying).

Method two:

Users can also add the link of the current interface to the schedule as an action through the sharing function while using other APPs. Optionally, it can be added to a newly created schedule or added to an existing schedule.

For example, when the user is browsing the interface of the ticket purchase 1 APP, the terminal device displays the interface shown in figure a in Figure 7. After the user sets the required time, location and ticket type (train ticket, plane ticket or bus ticket) in this interface, they can click the query button "Check Tickets" to query the trains that meet the needs or perform other operations. When the user needs to add a page that jumps to the ticket purchase 1 APP to the corresponding action in the schedule, he can click the more button "..." in the upper right corner of picture a in Figure 7 to bring up the menu window. The menu window may include but is not limited to: sharing, saving, etc. buttons. The composition of these buttons may vary depending on the content and type of the currently displayed page. This is not limited in the embodiment of the present application. When the user performs the operation shown in Figure 7 a and clicks the "Share" button, the terminal device can pop up the sharing window shown in Figure 7 c. The sharing window includes multiple objects to be shared, which can include but are not limited to calendar APP (taking calendar APP as an example), chat software friends (WeChat friends or QQ friends), circle of friends, emails, memos, copy links, and more. Multiple buttons "...". The user clicks the icon of the Calendar APP in the menu window to start the operation of adding the action "jump to the current page" to the schedule in the Calendar APP.

In response to the user's operation of adding an action, the terminal device can pop up a selection interface. The selection interface can be shown in Figure 7 d, including two buttons: "Add to existing schedule" and "New schedule". The user can Make your selection. When the user selects the "Add to existing button", the terminal device can display a list of multiple existing schedules. For example, as shown in figure a in Figure 8, the current existing schedule is "Business trip ticket purchase". Optionally, the schedule may be a schedule to which no action has been added, or a schedule to which other actions have been added. Figure a in Figure 8 shows an example in which the action "contact taxi" has been added. The user can click on the schedule that needs to be added in the list of existing schedules, for example, click on the schedule of "Business Trip Ticket Purchase", and the terminal device displays the editing interface of the schedule, for example, as shown in Figure 8 b. An icon for the action "Grab Tickets" has been added to the editing interface of the "Business Trip Tickets" schedule. If the user selects "New Schedule" in Figure 7d, the interface of the terminal device can display the interface of creating a new schedule as shown in Figure 8c. In the early stage of the display, the interface can display "Grab Tickets" "For this action button, the user also needs to enter the schedule name "Business trip ticket purchase", address (optional), time and other information. After that, the user can click the completion button "√" displayed in the upper right corner of the schedule editing interface to complete the ticket grabbing action and add it to the required schedule "Business Travel Ticket Purchase".

Taking the situation shown in picture b in Figure 8 as an example, after the addition of the ticket grabbing action is completed, the monthly view of the calendar APP can be displayed as shown in picture a in Figure 9, in the "Business Trip Ticket Purchase" column of the schedule Two existing action buttons are displayed: "Contact Taxi" and "Grab Ticket". It should be noted that the above-mentioned adding process of the "contact taxi" action can refer to the adding method of the action in the previous embodiment. The difference is that the "contact taxi" action corresponds to dialing the taxi phone number in the call APP. interface. Optionally, the above information such as the type and name of the button, the name of the schedule, etc. are examples and do not limit the added actions. Optionally, when the same schedule has only one action button, the terminal device can directly display the action button, making the interface display more indirect and direct, making it easier for the user to operate. Optionally, when there are multiple action buttons in the same schedule, such as the two buttons shown in Figure 9 a, the terminal device can also directly display all the action buttons, and can also display a menu entry such as "Operation" buttons to simplify the interface, such as the schematic diagram of the schedule column shown in Figure 9 b. The user can open a list of multiple action buttons by clicking the menu entry button, for example, the schematic diagram of the schedule column shown in Figure 9 (c). Then the user can select the operation that needs to be performed from a list of multiple action buttons. In order to reflect the differences between different display interfaces, Figures b and c in Figure 9 above show schematic diagrams of the schedule columns. Other interfaces of the calendar month view are not shown, but they do not represent what is displayed in other interfaces. The content does not exist.

Optionally, the user can also input multiple consecutive operations to the terminal device so that the terminal device generates a shortcut instruction set for these operations, and then uses "Share" or "Add Action" in the generation interface or storage interface of the shortcut instruction set. Through other operations, the shortcut instruction set is added to an existing schedule or a new schedule to complete the operation of adding the action to the corresponding schedule, which will not be described in detail in the embodiment of this application.

The above method two can add the action of jumping to the page through the sharing function in different interfaces of different applications. The types of actions that can be added are not limited by the list of actions to be selected, making the types of actions that can be added more abundant. More interactive.

It should be noted that after the user adds the corresponding action in the schedule, the corresponding shortcut is generated in the interface of the current calendar APP. At this time, add the corresponding attributes through the format defined by iCalendar. In some embodiments, the attribute may be an ATTEND-ACTION attribute, and the parameters contained in the ATTEND-ACTION attribute may include:

PLATFORM: Indicates the platform type that the current action is adapted to, such as: Windows, Linux, Mac, Android or IOS, etc.;

LANGUAGE: Indicates the language type of the label text corresponding to the added action, such as: zh-CN or en-US, etc., where zh-CN means Simplified Chinese and en-US means English;

LABEL: Indicates the content of the label text corresponding to the added action, such as: grabbing tickets, contacting the host, joining the meeting immediately, and requesting to host the meeting.

The ATTEND-ACTION attribute also includes links corresponding to each action.

Taking the calendar APP as an example, after adding the action corresponding to the schedule, the corresponding ATTEND-ACTION attribute field can be expressed locally as follows:

BEGIN:VCALENDAR

METHOD: xyz

VERSION:2.0

PRODID:-//ABC Corporation//NONSGML My Product//EN

BEGIN:VEVENT

DTSTAMP:19970324T120000Z

...

ATTEND-ACTION; VALUE = URI; PLATFORM = Android; LANGUAGE = zh-CN; LABEL = "Contact the host": tel: +8607000000000;

ATTEND-ACTION;VALUE=URI;PLATFORM=Android;

LANGUAGE=zh-CN; LABEL="Join the meeting now": https://meeting.tt.com/l/ehewFSfengBPae...

ATTEND-ACTION;VALUE=URI;PLATFORM=Android;

LANGUAGE＝zh-CN;LABEL="Request to host":https://meeting.tt.com/l/ehewFSfengBPae...

...

END:VEVENT

END:VCALENDAR

The above fields define the three actions of contacting the host, joining the meeting immediately, and requesting to host (conference). This field contains the parameters and other information corresponding to these actions. The expression form of the above fields may also vary according to different systems, and the embodiments of this application do not limit this. For example, the fields corresponding to the action of contacting the host include the platform type as Android, the language as Simplified Chinese, and the phone number to contact the host as +8607000000000. The fields corresponding to the action of requesting hosting include the platform type being Android, the language being Simplified Chinese, and the link requesting hosting being https://meeting.tt.com/l/ehewFSfengBPae.... The parameters of the above platform type and language type can be added to follow the current system, and the content of the label text can be set by the user.

Optionally, when other actions are added, corresponding attribute parameters will be added to the fields of the corresponding schedule APP, which will not be described again here.

The above ATTEND-ACTION attribute can be added to VEVENT (schedule), VTODO (to-do) or VJOURNAL (agenda) to mark the list of actions to be selected.

This application extends the existing iCalendar specification and adds fields corresponding to different actions in the protocol. This field defines the data format, interaction method and calendar file transmission-independent interoperability protocol (iCalendarTransport-Independent Interoperability Protocol, ITIP) , can support the addition and jump of more user-defined actions, providing users with a richer and more convenient interactive experience.

Method three:

The terminal device can also obtain a preset schedule template. The schedule template includes multiple existing schedules (schedule groups), and some or all of these existing schedules (schedule groups) have corresponding actions (APPs or links) added to them. . After the terminal device imports the configuration file of the schedule template, the action buttons in the schedule template can be displayed in the corresponding schedule interface.

Optionally, the above schedule template can be set according to common schedule types; optionally, the schedule template can also be saved based on a combination of one or more related schedules manually added by the user. In this regard, this application The examples are not limiting.

Optionally, the above schedule template may include but is not limited to travel planning calendar, degree application calendar, rush activity calendar and competition calendar, for example, as shown in Table 1, Table 2, Table 3 and Table 4 below.

Taking the schedule template as a travel planning calendar as an example, see Table 1:

Table 1

Table 1 can include three items: schedule time, matter (schedule name) and action. The schedule in the travel plan calendar shown in Table 1 above spans 12 days, from day-7 to day+4, and each day has a corresponding schedule. Different schedules correspond to different actions. For example, the passport schedule corresponds to the link to the entry-exit website, which means that the action corresponding to the passport schedule is to jump to the entry-exit website for users to operate. For another example, in Table 1, the outbound airport drop-off schedule corresponds to the taxi-hailing APP and the taxi contact. Among them, the taxi-hailing APP corresponds to the action of the terminal device opening the taxi-hailing APP, and the taxi contact corresponds to the terminal device dialing the taxi contact's phone number. Number actions. The other schedules in Table 1 will not be described again.

Taking the calendar template as an application degree calendar as an example, see Table 2:

Table 2

schedule time Event (schedule name) Action/APP March ID photo Chat APP to contact photo studio contacts April Real estate/rental materials University degree inquiry website, Housing Authority website April Application submission Education Bureau website June View Results Education Bureau website

Table 2 above also includes three items: schedule time, event (schedule name) and action as an example. The schedules in the degree application calendar shown in Table 2 above are relatively long, each schedule lasts for one month, and different schedules are arranged for different months. For example, if the ID photo schedule requires contacting the photo studio, and the contact method is to use a chat APP, then the corresponding action for the ID photo schedule is to jump to the chat APP. Optionally, you can also jump directly to the photo studio contact. The chat page facilitates direct contact. For another example, in Table 2, the schedule for viewing the results corresponds to the Education Bureau website, and the action corresponding to the schedule is to open the Education Bureau website or directly access the Education Bureau website and display the results page. The other schedules in Table 2 will not be described again.

Taking the schedule template as a snap-up event calendar as an example, see Table 3:

table 3

schedule time Event (schedule name) Action/APP 11.1 Collect and receive coupons Shopping APP 11.5 Distribute coupons in store Shopping APP 11.10 Confirm shopping cart Shopping APP 11.11 Payment Shopping APP, payment APP

Table 3 above also includes three items: schedule time, event (schedule name) and action as an example. The snap-up activity calendar shown in Table 3 includes multiple schedules and time nodes, such as four schedules and corresponding time nodes for collecting coupons, receiving coupons, confirming shopping carts, and making payments. Each schedule corresponds to the required operations. APP. Actions corresponding to the schedule in the snap-up activity calendar all require the operation of the shopping APP; and in the final payment schedule, the payment APP also needs to be operated. Therefore, the user can add the actions of the shopping APP and/or payment APP to the corresponding payment schedule. to jump to the corresponding APP for operation. For example, the user can add an action button of the shopping APP in the schedule of collecting and sending coupons. The action is to open the shopping APP or directly display the collection page of the shopping APP. For another example, the user can add action buttons for the shopping APP and payment APP in the payment schedule. The corresponding action for the shopping APP is to open the shopping APP or directly display the collection page of the shopping APP. The corresponding action for the payment APP is to open the payment APP or Directly display the payment confirmation page.

Taking the schedule template as the competition calendar as an example, see Table 4:

Table 4

schedule time Event (schedule name) Action/APP day-7 Pre-registration Competition pre-registration website day-5 Team up Chat APP, competition website day-3 Official registration Competition official website day Attend the competition Map APP1 day+1 second round Competition official website, map APP1 day+2 third round Competition official website, map APP1 ... ... ...

Table 4 above also includes three items: schedule time, event (schedule name) and action as an example. The schedule times shown in Table 1 and Table 4 are relative times, not absolute times. Users can calibrate the start time, end time, or the specific time of one of the schedules shown in the schedule template as needed. For example, if the pre-registration schedule requires operations on the competition pre-registration website, then the action corresponding to the pre-registration schedule is to access the page of the competition pre-registration website. For another example, in Table 4, the schedule of the second round of competition corresponds to the official website of the competition and map APP1, then the action corresponding to the official website of the competition is to open the official website of the competition, and the action corresponding to map APP1 is map APP1 and navigate to the entry address. The other schedules in Table 4 will not be described again.

Using calendar templates to set schedules eliminates the need for users to add corresponding actions for each schedule one by one, making the operation more convenient.

Optionally, the above schedule template may contain multiple schedules. These schedules may not be exactly the same as the actual needs of users. Therefore, the user can modify the above schedule template, for example, add or delete schedules in a schedule template, or modify the schedules in the schedule template. The name, time, actions, links of action instructions, etc. of the schedule can be modified, so the application is more flexible.

For example, the user can enter the editing interface of a certain schedule in the above schedule template in the calendar APP, and edit the schedule, such as modifying or deleting it; the user can also create a new schedule and add the new schedule to the existing schedule template. Implement adding schedule to schedule template.

Optionally, the user can also use a special schedule template editing tool to modify, add or delete the information in the list displayed in the above schedule template (for example, Table 1-Table 4), thereby generating a new configuration file, and then The new configuration file is imported into the schedule APP. It should be noted that when the user edits and modifies the schedule template, the corresponding fields will also change accordingly. For example, the user modifies the action of the "Second Round of Competition" in the schedule in Table 4 and changes Map APP1 to Map APP2. Then the action button "Map APP1" displayed in the schedule changes to "Map APP2". When the user enters the schedule interface When the action button "Map APP2" is clicked, the interface of the terminal device opens Map APP2 to display the interface of Map APP2.

The above schedule template can be used by governments, public institutions or businesses for unified release. For example, in order to facilitate students' guidance on applying for a degree, a government department can publish a schedule template called a degree application calendar. Among them, the websites and officially recognized APPs involved in each schedule have been added. Users only need to download the schedule template of the degree application calendar, and then they can complete the degree application under the guidance of the schedule template, avoiding students from consulting various resources. The cumbersome process also prevents government departments from responding too much to problems in the process, saves time for both parties, and thus simplifies the process of applying for a degree.

Optionally, users can also generate calendar templates based on their own schedules for others to use. Users only need to make fine adjustments based on the existing calendar templates.

It should be noted that when a calendar template is imported, the fields corresponding to the actions of each schedule in the calendar template and the action buttons corresponding to the actions in the calendar template will appear in the schedule interface of the schedule APP. Optionally, when importing a calendar template, the terminal device will filter the actions that can be imported according to the platform type parameter in the schedule field in the calendar template, that is, select the platform type that matches the system platform type on the current terminal device. Actions are imported, and those that do not match are not imported.

Optionally, after the terminal device imports the calendar template, the actions corresponding to each schedule in the calendar template can be displayed in the schedule interface in the form of shortcut keys. At the same time, the fields corresponding to each action will also be added to the code snippet of the schedule APP. Optionally, the terminal device can also filter and filter actions corresponding to each schedule in the calendar template. For example, filter out actions whose platform type is different from the current system platform type, and display actions that are the same as the current system platform type to ensure that the action can successfully jump to the corresponding link.

It should be noted that the terminal device can open the link (UniformResource Identifier, URI) of the APP action supported by its own system. For example, Windows supports app URI handlers (UWP) or URL Protocol; Linux supports Desktop Entry; Mac supports Universal Links or App Links; Android supports App Links; and IOS supports Universal Links.

When the terminal device displays operable action buttons in the interface of the schedule APP, and after completing adding the actions of the schedule, the interface shown in Figure 6 or Figure 8 can be displayed, for example. Optionally, schedule-related information can also be displayed on the desktop in the form of cards. At this time, the action button corresponding to the schedule displayed in the card can also be displayed in the card, for example, as shown in pictures a and b in Figure 10. The user can click the action button in the schedule card as needed to jump to the corresponding page or open the corresponding APP. For example, when the user clicks the "Operation" button in Figure 10 a and clicks the pop-up "Contact Host" When the "People" action button is pressed, the terminal device can jump to the call interface and display the host's corresponding phone number in the dial bar. For another example, when the user clicks the "Operation" button in Figure 10 a and clicks the pop-up "Request Host" action button, the terminal device can jump to the conference APP and display a page for requesting support, such as the terminal device display. This method does not require the user to operate a separate conference APP and initiate operations such as requesting hosting on the interface of the conference APP, so it is more convenient.

Optionally, when there are multiple schedules in the schedule card, important or urgent schedules can also be displayed above the schedule card, and non-urgent schedules can be folded. Optionally, when a schedule corresponds to multiple action buttons, a menu button such as "Operation" can be displayed in the schedule card, and optional action buttons can be called up by clicking the menu button to simplify the display of the card interface.

In some embodiments, the schedule management method includes: displaying a schedule interface, the schedule interface is used to display schedule information, the schedule interface includes at least one action control, each action control corresponds to an interface to be jumped, and at least one action control is a response A control generated by the user's operation of adding an action; receiving the user's selection operation on the target control in at least one action control; in response to the selection operation, jumping from the schedule interface to the target to-be-jumped interface corresponding to the target control.

When the terminal device displays action buttons (that is, action controls) that can be operated in the interface of the schedule APP, that is, the schedule interface, and after completing adding the actions to the schedule, the interface shown in Figure 6 or 8 can be displayed, for example. Optionally, schedule-related information can also be displayed on the desktop in the form of cards. At this time, the action button corresponding to the schedule displayed in the schedule interface or schedule card can also be displayed in the schedule interface or schedule card, for example, as shown in Figures a and b in Figures 6 and 10. The user can click the action button in the schedule interface or schedule card as needed to jump to the corresponding page or open the corresponding APP. For example, when the user clicks the "Action" button in Figure 10 a and clicks the pop-up When clicking the "Contact Host" action button, the terminal device can jump to the call interface and display the host's corresponding phone number in the dial bar. For another example, when the user clicks the "Operation" button in Figure 10 a and clicks the pop-up "Request Host" action button, the terminal device can jump to the conference APP and display a page for requesting support, such as the terminal device display. This method does not require the user to operate a separate conference APP and initiate operations such as requesting hosting on the interface of the conference APP, so it is more convenient.

When viewing the schedule, the user can directly select the required shortcut key (target action control) on the schedule interface, and then operate the terminal device to directly jump to the target to-be-jumped interface corresponding to the target control, without the user having to operate other third-party APPs. Or open the corresponding interface, so the operation is more convenient. Moreover, this method enables users to add shortcut keys for different actions according to their own needs, realizes the user's need for customized shortcut keys (action controls), and provides users with a richer and more convenient interactive experience.

Optionally, before displaying the schedule interface, it also includes: displaying a new schedule interface, which is used by the user to create a new schedule; receiving an operation of adding an action input by the user; responding to the operation of adding an action, in the new schedule The icon of the target action corresponding to the target control is added to the interface. The target action is the action to jump to the target interface to be jumped.

Users can actively associate the link of the interface to which the target action is to jump to the schedule through the operation of adding an action in the interface of creating a new schedule, so as to associate the target action to the corresponding schedule, thereby adding goals in the interface of creating a new schedule. The icon of the target action corresponding to the control, such as the operations shown in Figure 4 and Figure 5, facilitates the user to directly jump to the target interface to be jumped through the target control.

Optionally, the operation of adding an action is an operation of selecting an icon of a target action in a list of actions to be selected, and the list of actions to be selected at least includes an icon of the target action.

Users can subjectively select the actions required by the current schedule from the list of optional actions formed by multiple actions that can be added, and add them, which can realize customized schedule actions and provide users with a richer and more convenient interactive experience.

Optionally, receiving the operation of adding an action input by the user includes: receiving the first operation input by the user in the interface of creating a new schedule, where the first operation is the operation of the user selecting the add action option; in response to the first operation, displaying the options to be selected Action list; receiving a second operation input by the user, the second operation being a selection operation for an icon of a target action in the action list to be selected; and selecting the target action in response to the second operation.

The user can select the add action option in the interface of creating a new schedule. When the list of actions to be selected is displayed, the user selects the icon of the target action, thereby selecting the target action as the action corresponding to the new schedule, which facilitates the user to jump directly to the target through the target control. The target interface corresponding to the action is to be redirected.

Optionally, before displaying the first interface, the method further includes: displaying the target interface to be jumped; receiving a sharing operation input by the user; and in response to the sharing operation, displaying the target control corresponding to the target interface to be jumped in the schedule interface.

When users browse pages or use various APPs, they can display the target control corresponding to the interface to be jumped to in the schedule interface directly through the sharing operation in the interface they are browsing. This method can add actions to jump to the page in different interfaces of different applications through the sharing operation function. The types of actions that can be added are not limited by the list of actions to be selected, making the types of actions that can be added more abundant. , more interactive.

Optionally, receiving the sharing operation input by the user includes: receiving a third operation input by the user, where the third operation is the user's operation of selecting the sharing control in the target interface to be jumped; in response to the third operation, displaying at least one to-be-shared operation Object, at least one object to be shared includes a calendar application APP; receiving a fourth operation input by the user, the fourth operation being an operation for the user to select a calendar APP from at least one object to be shared; in response to the fourth operation, displaying the existing schedule control and a new schedule control; receive the fifth operation of user input, the fifth operation is the operation of the user to select the target control from the existing schedule control and the new schedule control; display the schedule editing interface corresponding to the target control, and the schedule editing interface includes the target The icon of the target action corresponding to the control. The target action is the action to jump to the target interface to be jumped.

By selecting the sharing control (share button) in the currently used interface, the user can continue to select the schedule APP in the pop-up object to be shared, and then select the existing schedule control or create a new schedule control to achieve the currently used interface as the target to be shared. Jump interface, add the action of jumping to the target interface to be jumped to the schedule that needs to be added, so that users can add it at any time when using the terminal device APP or browsing the web. The functions are richer and the interactivity is more powerful.

Optionally, before displaying the schedule interface, the method further includes: obtaining a schedule template. The schedule template includes a correspondence relationship between at least one schedule time, at least one schedule identifier, and at least one interface to be jumped. The at least one interface to be jumped includes a target to-be-jumped interface. Jump interface; according to the schedule template, the target control corresponding to the target interface to be jumped is displayed in the schedule interface.

The terminal device can also obtain a preset schedule template. The schedule template includes multiple existing schedules (schedule groups), and some or all of these existing schedules (schedule groups) have corresponding actions (APPs or links) added to them. . After the terminal device imports the configuration file of the schedule template, the action controls corresponding to the actions in the schedule template can be displayed in the corresponding schedule interface. Using calendar templates to set schedules eliminates the need for users to add corresponding actions for each schedule one by one, making the operation more convenient.

The above-mentioned ways of adding actions are diverse and flexible, can meet the needs of different scenarios and different users, and improve user experience.

Optionally, the schedule template is any one or more of a travel planning calendar template, a degree application calendar template, a rush activity calendar template, and a competition calendar template.

Optionally, the number of controls of at least one action control is one; or, at least one action control is a menu control of multiple action controls, and the menu control is used to call out multiple action controls.

When there is one action corresponding to the schedule displayed on the schedule interface, the action control corresponding to the action can be directly displayed; when there are multiple actions corresponding to the schedule displayed on the schedule interface, the menu control can be directly displayed, and the user can Click the menu control to bring up multiple action controls, and then select the required target action among these multiple action controls. This display method can simplify the display interface and facilitate interface layout.

Optionally, the schedule interface is an interface of a schedule APP or an interface of a schedule card.

Optionally, the target interface to be jumped is the interface or target page of the target APP.

Optionally, the target APP is one of a conference APP, a shopping APP and a ticket purchase APP, a travel APP, a taxi APP, a phone call APP, a hotel reservation APP, an air ticket reservation APP, a car rental APP, a tour guide reservation APP, a chat APP, and a payment APP; The target page is one of a shopping website page, a ticket purchase website page, a travel website page, an immigration website page, an embassy website page, a hotel reservation website page, an air ticket reservation website page, or an education bureau website page.

The above-mentioned various APPs, various pages and various templates can meet the needs of different users. They are comprehensive and practical, fully meet the needs of users, and improve the user experience.

It should be noted that the actions described in the embodiments of this application correspond to the links that jump to the corresponding actions. The controls in the embodiments of this application represent buttons on the page that can be used for user touch operations. Other positions in this article will not be mentioned. Repeat.

Examples of the methods provided in this application are detailed above. It can be understood that, in order to implement the above functions, the corresponding device includes corresponding hardware structures and/or software modules for performing each function. Persons skilled in the art should easily realize that, with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

This application can divide the schedule management device into functional modules according to the above method examples. For example, each function can be divided into functional modules, or two or more functions can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in this application is schematic and is only a logical function division. In actual implementation, there may be other division methods.

Figure 11 shows a schematic structural diagram of a schedule management device provided by this application. Device 1100 includes:

The display module 1101 is used to display the schedule interface. The schedule interface is used to display schedule information. The schedule interface includes at least one action control. Each action control corresponds to an interface to be jumped. At least one action control is in response to the user's added action. Controls generated by operations;

The receiving module 1102 is used to receive the user's selection operation on the target control in at least one action control;

The processing module 1103 is configured to jump from the schedule interface to the target to-be-jumped interface corresponding to the target control in response to the selection operation.

In some embodiments, before displaying the schedule interface, the following steps are also included:

The display module 1101 is also used to display the interface for creating a new schedule. The interface for creating a new schedule is used by the user to create a new schedule;

The receiving module 1102 is also used to receive the operation of adding an action input by the user;

The display module 1101 is also configured to, in response to the operation of adding an action, add an icon of the target action corresponding to the target control in the interface of the new schedule, where the target action is an action to jump to the target interface to be jumped.

In some embodiments, the operation of adding an action is an operation of selecting an icon of a target action in a candidate action list, and the candidate action list at least includes an icon of the target action.

In some embodiments, the receiving module 1102 is also configured to receive the first operation input by the user in the interface of creating a new schedule, where the first operation is the user's operation of selecting the add action option;

The display module 1101 is also configured to display a list of actions to be selected in response to the first operation;

The receiving module 1102 is also configured to receive a second operation input by the user, where the second operation is a selection operation for the icon of the target action in the action list to be selected;

The processing module 1103 is also configured to select a target action in response to the second operation.

In some embodiments, the display module 1101 is also used to display the target interface to be jumped;

The receiving module 1102 is also used to receive the sharing operation input by the user;

The display module 1101 is also used to display the target control corresponding to the target interface to be jumped in the schedule interface in response to the sharing operation.

In some embodiments, the receiving module 1102 is also configured to receive a third operation input by the user. The third operation is the user's operation of selecting the sharing control in the target interface to be jumped;

The display module 1101 is also configured to display at least one object to be shared in response to the third operation, and the at least one object to be shared includes a schedule APP;

The receiving module 1102 is also configured to receive a fourth operation input by the user. The fourth operation is the user's operation of selecting the schedule APP from at least one object to be shared;

The display module 1101 is also configured to display existing schedule controls and new schedule controls in response to the fourth operation;

The receiving module 1102 is also used to receive a fifth operation input by the user. The fifth operation is an operation in which the user selects a target control from an existing schedule control and a new schedule control;

The display module 1101 is also used to display the schedule editing interface corresponding to the target control. The schedule editing interface includes an icon of the target action corresponding to the target control, and the target action is an action to jump to the target interface to be jumped.

In some embodiments, the processing module 1103 is also used to obtain a schedule template. The schedule template includes a correspondence relationship between at least one schedule time, at least one schedule identifier, and at least one interface to be jumped. The at least one interface to be jumped includes a target. The interface to be jumped;

The display module 1101 is also used to display the target control corresponding to the target interface to be jumped in the schedule interface according to the schedule template.

In some embodiments, the schedule template is any one or more of a travel planning calendar template, a degree application calendar template, a snap-up event calendar template, and a competition calendar template.

In some embodiments, the number of controls of at least one action control is one; or, at least one action control is a menu control of multiple action controls, and the menu control is used to call out multiple action controls.

In some embodiments, the schedule interface is an interface of a schedule APP or an interface of a schedule card.

In some embodiments, the target interface to be jumped is the interface or target page of the target APP.

In some embodiments, the target APP is one of a conference APP, a shopping APP and a ticket purchase APP, a travel APP, a taxi APP, a phone call APP, a hotel reservation APP, a ticket reservation APP, a car rental APP, a tour guide reservation APP, a chat APP, and a payment APP. Type; the target page is one of shopping website pages, ticket purchase website pages, travel website pages, entry and exit website pages, embassy website pages, hotel reservation website pages, air ticket reservation website pages, and education bureau website pages.

The specific manner in which the device 1100 executes the schedule management method and the beneficial effects produced can be found in the relevant descriptions in the method embodiments, and will not be described again here.

An embodiment of the present application also provides an electronic device, including the above processor. The electronic device provided in this embodiment may be the terminal device 100 shown in FIG. 1, and is used to execute the above schedule management method. In the case of an integrated unit, the terminal device may include a processing module, a storage module and a communication module. The processing module may be used to control and manage the actions of the terminal device. For example, it may be used to support the terminal device in executing steps performed by the display unit, the detection unit and the processing unit. The storage module can be used to support terminal devices to execute stored program codes and data. The communication module can be used to support communication between the terminal device and other devices.

The processing module may be a processor or a controller. It may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with this disclosure. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor (DSP) and a microprocessor, and so on. The storage module may be a memory. The communication module can specifically be a radio frequency circuit, a Bluetooth chip, a Wi-Fi chip and other devices that interact with other terminal devices.

In one embodiment, when the processing module is a processor and the storage module is a memory, the terminal device involved in this embodiment may be a device with the structure shown in Figure 1 .

Embodiments of the present application also provide a computer-readable storage medium. A computer program is stored in the computer-readable storage medium. When the computer program is executed by a processor, it causes the processor to execute any of the above embodiments. schedule management method.

An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, it causes the computer to perform the above related steps to implement the schedule management method in the above embodiment.

Among them, the electronic devices, computer-readable storage media, computer program products or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the above provided The beneficial effects of the corresponding methods will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or can be integrated into another device, or some features can be ignored, or not implemented. Another point is that the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, and the replacement unit may or may not be physically separated, as The component displayed by the unit can be one physical unit or multiple physical units, that is, it can be located in one place, or it can be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

Integrated units may be stored in a readable storage medium if they are implemented in the form of software functional units and sold or used as independent products. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the software product is stored in a storage medium , including several instructions to cause a device (which can be a microcontroller, a chip, etc.) or a processor to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes.

The above contents are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, and should are covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (14)

1. A schedule management method, characterized by including: Display a schedule interface. The schedule interface is used to display schedule information. The schedule interface includes at least one action control. Each of the action controls corresponds to an interface to be jumped. The at least one action control is in response to the user's Add the control generated by the operation of the action; Receive a user's selection operation on a target control in the at least one action control; In response to the selection operation, jump from the schedule interface to the target to-be-jumped interface corresponding to the target control. 2. The method according to claim 1, characterized in that before displaying the schedule interface, it further includes: Display an interface for creating a new schedule. The interface for creating a new schedule is used by the user to create a new schedule; Receive the operation of adding the action input by the user; In response to the operation of adding an action, an icon of a target action corresponding to the target control is added to the interface of the new schedule, and the target action is an action of jumping to the target interface to be jumped. 3. The method according to claim 2, wherein the operation of adding an action is an operation of selecting an icon of the target action in a list of actions to be selected, and the list of actions to be selected at least includes the target Action icon. 4. The method according to claim 3, characterized in that the operation of receiving the adding action input by the user includes: Receive the first operation input by the user in the interface of the new schedule, where the first operation is the user's operation of selecting the add action option; In response to the first operation, display the list of actions to be selected; Receive a second operation input by the user, where the second operation is a selection operation for the icon of the target action in the list of actions to be selected; In response to the second operation, the target action is selected. 5. The method according to claim 1, characterized in that before displaying the first interface, further comprising: Display the target interface to be jumped; Receive sharing operations input by the user; In response to the sharing operation, the target control corresponding to the target interface to be jumped is displayed in the schedule interface. 6. The method according to claim 5, characterized in that the sharing operation of receiving user input includes: Receive a third operation input by the user, where the third operation is the user's operation of selecting a sharing control in the target to-be-jumped interface; In response to the third operation, display at least one object to be shared, where the at least one object to be shared includes a calendar application APP; Receive a fourth operation input by the user, where the fourth operation is the user's operation of selecting the schedule APP from the at least one object to be shared; In response to the fourth operation, display the existing schedule control and the new schedule control; Receive a fifth operation input by the user, where the fifth operation is an operation in which the user selects a target control from the existing schedule control and the new schedule control; The schedule editing interface corresponding to the target control is displayed. The schedule editing interface includes an icon of a target action corresponding to the target control. The target action is an action to jump to the target interface to be jumped. 7. The method according to claim 1, characterized in that before displaying the schedule interface, it further includes: Obtain a schedule template, the schedule template includes a correspondence relationship between at least one schedule time, at least one schedule identifier, and at least one interface to be jumped, and the at least one interface to be jumped includes the target interface to be jumped; According to the schedule template, the target control corresponding to the target interface to be jumped is displayed in the schedule interface. 8. The method according to claim 7, characterized in that the schedule template is any one or more of a travel planning calendar template, a degree application calendar template, a rush activity calendar template, and a competition calendar template. 9. The method according to any one of claims 1 to 8, characterized in that the number of controls of the at least one action control is one; or, The at least one action control is a menu control of multiple action controls, and the menu control is used to call out the multiple action controls. 10. The method according to any one of claims 1 to 9, characterized in that the schedule interface is an interface of the schedule APP or an interface of a schedule card. 11. The method according to any one of claims 1 to 10, characterized in that the target interface to be jumped is the interface or target page of the target APP. 12. The method according to claim 11, characterized in that the target APP is a conference APP, a shopping APP and a ticket purchase APP, a travel APP, a taxi APP, a phone call APP, a hotel reservation APP, an air ticket reservation APP, a car rental APP, and a tour guide. One of booking APP, chat APP and payment APP; The target page is one of a shopping website page, a ticket purchase website page, a travel website page, an immigration website page, an embassy website page, a hotel reservation website page, an air ticket reservation website page, and an education bureau website page. 13. An electronic device, characterized by comprising: a processor, a memory and an interface; The processor, the memory and the interface cooperate with each other so that the electronic device performs the method according to any one of claims 1 to 12. 14. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium. When the computer program is executed by a processor, the processor is caused to execute claims 1 to 12. any of the methods described.