WO2018018361A1

WO2018018361A1 - Calendar event creating method and device

Info

Publication number: WO2018018361A1
Application number: PCT/CN2016/091544
Authority: WO
Inventors: 伍亮雄; 刘海涛; 骆艳飞
Original assignee: 北京小米移动软件有限公司
Priority date: 2016-07-25
Filing date: 2016-07-25
Publication date: 2018-02-01
Also published as: CN106462835A

Abstract

Provided are a calendar event creating method and device, relating to the field of mobile terminals. The method comprises: receiving a first trigger operation performed on a calendar event creating control provided by a third-party application, the third-party application being an application other than a calendar application (101); creating a calendar event according to the first trigger operation (102); and importing parameters extracted from the third-party application to the calendar event by using an intent approach, the parameters at least comprising reminder content, a start time, and an end time (103). The method solves the problem that a user needs to manually input calendar event creating parameters when creating a calendar event associated with a third-party application. The third-party application can automatically create a calendar event, thus reducing user inputs, and improving the calendar event creating efficiency.

Description

Calendar event creation method and device

Technical field

The embodiments of the present disclosure relate to the field of mobile terminals, and in particular, to a calendar event creation method and apparatus.

Background technique

The calendar software installed in the mobile terminal is a schedule management software that is highly time-correlated, and the user can manage the schedule by creating a calendar event.

In the related art, after the user opens the calendar application, click to create a calendar event control, and manually input calendar event parameters such as reminder content, start time, end time, reminder time, reminder number in the calendar event creation interface, and the calendar application according to the calendar event The parameter generates a calendar event.

Public content

In order to solve the problem that a user needs to manually input a calendar event creation parameter when creating a calendar event related to a third-party application, the present disclosure provides a calendar event creation method and apparatus. The technical solution is as follows:

In a first aspect, an embodiment of the present disclosure provides a method for creating a calendar event, the method comprising:

Receiving a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application;

Creating a calendar event according to the first triggering operation;

The parameters extracted from the third-party application are imported into the calendar event by the intent method, and the parameters include at least the reminder content, the start time, and the end time.

Optionally, import the parameters for creating calendar events in the third-party application into the calendar event creation interface, including:

After the parameters extracted from the third-party application are imported into the calendar event by the intent method, the display interface of the third-party application is switched to the calendar event creation interface, and the imported parameters are displayed in the calendar event creation interface;

Receiving a modification operation on the imported parameters;

Modify the imported parameters in the calendar event creation interface according to the modification operation.

Optionally, the parameter further includes a jump interface parameter, and the jump interface parameter is used to indicate a predetermined display interface that jumps when viewing the calendar event; the method further includes:

After the reminder time of the calendar event is reached, the calendar event prompt control is displayed, and the reminding time of the calendar event is before the end time of the calendar event;

Receiving a second triggering operation acting on the calendar event prompt control;

The predetermined display interface is displayed according to the second triggering operation.

Optionally, the method further includes:

Before receiving the first triggering operation,

Creating an activation event in the calendar application that is used to provide an interface for creating a calendar event for a third party application;

Creating a calendar event according to the first triggering operation includes: invoking an activation event according to the first triggering operation, and creating a calendar event by activating the event.

Optionally, create an activation event in the calendar app, including:

Register the interface activity component in the profile of the calendar application;

Create calendar events by activating events, including:

Create calendar events through the interface activity component.

In a second aspect, an embodiment of the present disclosure provides a calendar event creation device, where the device includes:

a first receiving module configured to receive a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application;

Creating a module configured to create a calendar event according to the first triggering operation;

The import module is configured to import the parameters extracted from the third-party application into the calendar event by intent.

Optionally, the device further includes:

The switching module is configured to, after importing the parameters extracted from the third-party application into the calendar event by using the intent method, switch the display interface of the third-party application to the calendar event creation interface, and display the imported parameters in the calendar event creation interface;

a second receiving module configured to receive a modification operation on the imported parameter;

The modification module is configured to modify the imported parameters in the calendar event creation interface according to the modification operation.

Optionally, the parameter further includes a jump interface parameter, and the jump interface parameter is used to indicate that the calendar is being viewed. a predetermined display interface for jumping when the device is in use; the device further includes:

The first display module is configured to display a calendar event prompt control after the prompt time of the calendar event is reached, and the reminding time of the calendar event is before the end time of the calendar event;

a third receiving module configured to receive a second triggering operation that is applied to the calendar event prompting control;

The display module is configured to display the predetermined display interface according to the second triggering operation.

Optionally, the device further includes:

a control creation module configured to create an activation event in the calendar application before receiving the first triggering operation, the activation event being used to provide an interface for creating a calendar event for the third party application;

Create modules, including:

A sub-module is created that is configured to invoke an activation event based on the first triggering operation to create a calendar event by activating the event.

Optionally, the control creation module is further configured to: register the interface activity component in a configuration file of the calendar application.

A submodule is created that is also configured to create calendar events through the interface activity component.

In a third aspect, an embodiment of the present disclosure provides a calendar event creation device, where the device includes:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

Creating a calendar event according to the first triggering operation;

The parameters extracted from the third-party application are imported into the calendar event by an intent method, and the parameters include at least a reminder content, a start time, and an end time.

After the control event is created by triggering the calendar event on the display interface of the third-party application, the parameters for creating the calendar event are extracted from the third-party application, and the intent is used to import the parameter into the calendar event to automatically create the calendar event, which is solved in the creation and The problem of manually inputting calendar event parameters when the third-party application related calendar events reaches the third-party application to automatically create calendar events, reduce user input, and improve the efficiency of calendar event creation.

In addition, by inserting the jump interface parameter, when the reminder time of the calendar event is reached, the calendar event prompt control is displayed, and when the calendar event prompt control is triggered, jumping to the predetermined display interface, Reduce user operations and conveniently switch to the display interface corresponding to the content indicated by the calendar event.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present disclosure. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

FIG. 1 is a flowchart of a method for creating a calendar event according to an embodiment of the present disclosure;

2 is a flowchart of a method for providing a calendar event creation method according to another embodiment of the present disclosure;

3 is a schematic diagram of an interface of a display interface of a third-party application according to an embodiment of the present disclosure;

4 is a schematic diagram of an interface for creating a calendar event according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of an implementation of a calendar event creation method according to an embodiment of the present disclosure; FIG.

6 is a flowchart of a method for creating a calendar event according to another embodiment of the present disclosure;

FIG. 7 is a schematic diagram of an implementation of a calendar event creation method according to another embodiment of the present disclosure; FIG.

FIG. 8 is a structural block diagram of a calendar event creation apparatus according to an embodiment of the present disclosure;

FIG. 9 is a structural block diagram of a calendar event creation apparatus according to another embodiment of the present disclosure;

FIG. 10 is a structural block diagram of a calendar event creation apparatus according to another embodiment of the present disclosure.

detailed description

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with aspects of the present disclosure as detailed in the appended claims.

The calendar event creation method provided by various embodiments of the present disclosure may be implemented by a smart terminal adopting an Android (Android) operating system, and the smart terminal may be an electronic device such as a smart phone, a smart TV, a tablet computer.

Please refer to FIG. 1 , which shows a flowchart of a calendar event creation method provided by an exemplary embodiment of the present disclosure. This calendar event creation method is suitable for use in a terminal where a calendar application is installed. As shown in Figure 1, The calendar event creation method can include the following steps.

In step 101, a first triggering operation is applied to a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application.

In step 102, a calendar event is created in accordance with the first triggering operation.

In step 103, the parameters extracted from the third-party application are imported into the calendar event by the intent method, and the parameters include at least the reminder content, the start time, and the end time.

In this embodiment, the parameters for importing the calendar event include at least the reminder content, the start time, and the end time. Optionally, the parameter may further include at least one of a prompt time, a reminder count, a calendar account, an account status, an activity nature, a location, and a note.

In Android, an intent is an abstract description of an operation. The intent is responsible for describing the actions of an operation in an application, the data involved in the action, and the additional data. An intent is a runtime binding mechanism that connects two components while the program is running, causing one component to transfer data to another component via an intent.

The operating system of the terminal imports the calendar event from the parameters extracted from the third-party application through the intent method. It can be understood that the operating system of the terminal establishes a communication connection with the calendar application through the intent in the third-party application, so that the parameters in the third-party application can be transmitted. Apply to the calendar.

In summary, the calendar event creation method provided by the embodiment of the present disclosure extracts a parameter for creating a calendar event from a third-party application by triggering a calendar event creation control on a display interface of a third-party application, and uses an intent. The method of importing parameters into calendar events to automatically create calendar events solves the problem of manually inputting calendar event parameters when creating calendar events related to third-party applications, so that third-party applications can automatically create calendar events, reduce user input, and improve The effect of calendar event creation efficiency.

Please refer to FIG. 2 , which shows a flowchart of a calendar event creation method provided by another exemplary embodiment of the present disclosure. This calendar event creation method is suitable for use in a terminal where a calendar application is installed. As shown in FIG. 2, the calendar event creation method may include the following steps.

In step 201, an activation event is created in the calendar application, the activation event being used to provide an interface for creating a calendar event for the third party application.

Among them, the third-party application is an application other than the calendar application.

Creating an activation event in the calendar application is accomplished by registering the interface activity component in the calendar application's configuration file.

The configuration file of the calendar application may be an AndroidManifest.xml file of the calendar application in the Android system. In the Android system, an application corresponds to an AndroidManifest.xml file, and all interfaces need to be declared in the AndroidManifest.xml file, that is, the interface activity component needs to be registered in the AndroidManifest.xml file.

If the terminal wants to directly create a calendar event by a third-party application, the interface activity component for creating a calendar event for the third-party application needs to be registered in the AndroidManifest.xml file corresponding to the calendar application, that is, the AndroidManifest.xml file corresponding to the calendar application. Register an Activity for creating calendar events for third-party applications. The interface activity component is the Activity, and an Activity is applicable to all third applications that need to create calendar events.

Optionally, after the interface activity component activity is registered in the AndroidManifest.xml file corresponding to the calendar application, the third-party application may also jump from the display interface of the third-party application to the calendar application according to the interface activity component Activity when creating the calendar event. The calendar event creates an interface.

Optionally, registering an interface activity component activity for creating a calendar event for a third-party application in a configuration file of the calendar application may be implemented as follows:

Add the following code to the AndroidManifest.xml file corresponding to the calendar app:

In step 202, a first triggering operation is applied to a calendar event creation control provided by a third party application.

Optionally, the third-party applications are a short message application, a broadcast application, a social application, a shopping application, a reading application, and the like.

A calendar event creation control is displayed on the display interface of the third-party application, and the operating system of the terminal receives a trigger operation acting on the calendar event creation control.

For example, as shown in FIG. 3, the display interface in the current terminal is the display interface 31 of a broadcast application. When the user clicks on the calendar event creation control 32, the operating system of the terminal receives the first triggering action acting on the calendar creation control 32.

In step 203, an activation event is invoked according to the first triggering operation, and a calendar event is created by the activation event.

The interface activity component is invoked according to the first triggering operation, and the calendar event is created by the interface activity component.

Optionally, the third-party application creates a calendar event in the background, and the current display interface of the terminal is still a display interface of the third-party application.

Optionally, the third party application creates a calendar event in the foreground, and the current display interface of the terminal can be switched from the display interface of the third application to the calendar event creation interface in the calendar application.

In step 204, the parameters extracted from the third-party application are imported into the calendar event by the intent method, and the parameters include at least the reminder content, the start time, and the end time.

Optionally, the parameters for importing calendar events include at least reminder content, start time, and end time. Optionally, the parameter may further include at least one of a prompt time, a reminder count, a calendar account, an account status, an activity nature, a location, and a note.

The operating system of the terminal analyzes the parameters in the display interface of the third-party application, and uses the parameters that can be used to create the calendar event as parameters of the import calendar event, and imports the parameters into the corresponding positions of the various parameters in the calendar event by means of an intent.

For example, in the display interface of the third-party application shown in FIG. 3, the parameter corresponding to the broadcast program "Water Margin 20th" is used as the parameter corresponding to the reminder content in the calendar event, and the corresponding parameter "June" is predicted from the play time. On the 17th, from 19:30 to 20:30, the parameters corresponding to the start time and the end time in the calendar event are extracted, and the calendar event of June 17 is created. When the parameter is imported by the intent method, the "Water Margin 20th" is Import the reminder content in the calendar event, import "19:30" into the start time in the calendar event, and import "20:30" into the end time in the calendar event.

Optionally, the parameter is imported into the corresponding position of each parameter in the calendar event by means of an intent, and may be implemented by a third party application by calling the following code:

Intent intent=new Intent("miui.intent.action.INSERT_CALENDAR");

intent.putExtra("content","Reminder content");

intent.putExtra("start_time","start time");

intent.putExtra("end_time","end time");

.......

startActivity(intent);

For example, after the user clicks the calendar event creation control 32 in the display interface 31 in FIG. 3, the third application creates a calendar event in the background. After the user opens the calendar application, clicking the calendar event can view the details of the calendar event, and the third party application creates The calendar event is shown in Figure 4.

In step 205, the calendar event prompt control is displayed when the reminder time of the calendar event is reached.

The reminder time for a calendar event is before the end time of the calendar event. Optionally, the reminder time of the calendar event is before the start time of the calendar event, or the reminder time of the calendar event is between the start time and the end time of the calendar event.

Optionally, if the third-party application does not import the prompt time parameter into the calendar event, the prompt time of the calendar event is a prompt time determined according to a default setting of the calendar event, for example, the prompt time is a calendar event in the default setting of the calendar event. The first 5 minutes of the start time, or, the reminder time is the start time of the calendar event.

The calendar event reminder control is used to prompt the user when the calendar event occurred. Optionally, the calendar event prompt control is displayed in a drop-down notification bar, or the calendar event prompt control is displayed as a floating window in the display interface of the terminal.

Optionally, the parameter inserted into the calendar event by the third party application further includes a jump interface parameter, and the jump interface parameter is used to indicate a predetermined display interface that jumps when viewing the calendar event. At this time, the jump interface parameter is a link corresponding to the predetermined display interface.

Optionally, the predetermined display interface is a display interface of a third-party application that imports the parameter into the calendar event, or the predetermined display interface is a display interface of the third-party application manually added by the user, or the predetermined display interface is a third-party application that imports the parameter. The display interface of the specified third-party application other than the third-party application that imports the parameters.

For example, the user creates a calendar event through a shopping application, and when the calendar event is created, the shopping application uses the snapping interface of an item as a predetermined display interface; or the user creates a calendar event through the short message application, and when the calendar event is created, A dialing interface corresponding to a contact is used as a predetermined display interface.

Optionally, if the parameter of the third party application importing the calendar event does not include the jump interface parameter, the calendar prompt control is used to display the reminder content and the start time of the calendar event.

In step 206, a second triggering action is applied to the calendar event prompt control.

In step 207, a predetermined display interface is displayed according to the second triggering operation.

According to the second triggering operation, the terminal switches to the predetermined display interface at the display interface of the reminder time of the calendar event.

For example, the reminder time of a calendar event is 19:30, and the content of the calendar event is listening to the broadcast program. At 19:30, the display interface of the terminal is the display interface of a shopping application, and the calendar is displayed at 19:30. The event prompt control, after the user clicks the calendar event prompt control, switches from the current shopping application interface to the broadcast listening interface, as shown in FIG. 5 .

Optionally, if the parameter inserted in the calendar event creation interface of the third-party application does not include the jump interface parameter, according to the second triggering operation, the terminal is switched to the calendar application in the display interface of the reminding time of the calendar event for displaying the The display interface of the detailed information of the calendar event; or, according to the second triggering operation, the calendar display control is hidden, and does not switch to any other display interface.

In addition, by inserting the jump interface parameter, when the reminder time of the calendar event is reached, the calendar event prompt control is displayed, and when the calendar event prompt control is triggered, jumping to the predetermined display interface can reduce the user operation and conveniently switch to The display interface corresponding to the content indicated by the calendar event.

In an alternative embodiment based on the embodiment shown in FIG. 2, the third party application creates a calendar event in the foreground, the terminal operating system switches the display interface of the third application to the calendar event creation interface in the calendar application, and creates the calendar event The interface displays the imported parameters, and the user can also manually change the parameters on the calendar event creation interface, that is, after step 204, step 204a, step 204b, and step 204c are further included, as shown in FIG. 6.

In step 204a, the display interface of the third party application is switched to the calendar event creation interface, and the imported parameters are displayed in the calendar event creation interface.

The third party application creates a calendar event in the foreground, and the terminal's operating system switches the display interface of the third application to the calendar event creation interface in the calendar application. The implementation process of the step may be: the operating system of the terminal invokes the action action in the interface activity component according to the first triggering operation, switches the display interface of the third-party application to the calendar event creation interface, and displays the imported event in the calendar event creation interface. parameter.

Optionally, the user sets in a third-party application when the third-party application automatically creates a calendar event, Whether to switch the display interface of the third-party application to the calendar event creation interface. If the user sets a third-party application to automatically create a calendar event in a third-party application, and switches the display interface of the third-party application to a calendar event creation interface, the third-party application automatically creates a calendar event each time a third party application The application's display interface switches to the calendar event creation interface.

Optionally, the third-party application determines whether to switch the display interface of the third-party application to the calendar event creation interface according to the parameter in the display interface currently used to create the calendar event, for example, the user purchases a certain product by using a shopping application. At the time, the shopping application is used to create a calendar event about the purchase of the item. At this time, the shopping application determines that the user has the need to change the reminder time of the calendar event according to the parameter in the snap-up notice interface of the item, and then determines the third-party application. The display interface switches to the calendar event creation interface.

In step 204b, a modification operation on the imported parameters is received.

When the imported parameters displayed in the calendar event creation interface do not meet the actual needs of the user, the user can manually change the parameters in the calendar event creation interface.

Optionally, after the user selects the corresponding position of the parameter, the corresponding parameter is changed or added to generate a modification operation, and the operating system of the terminal receives the modification operation.

Optionally, when the calendar event creation interface is displayed, and the imported parameters are displayed in the calendar event creation interface, the user can also manually set parameters that are not imported by the third-party application in the calendar event creation interface, for example, the third-party application is not imported. The calendar event priority parameter, the user can manually set the priority of the calendar event in the calendar creation interface.

In step 204c, the imported parameters in the calendar event creation interface are modified according to the modification operation.

For example, as shown in FIG. 7, the number of reminders in the calendar event creation interface 33 is originally 1, the user clicks the reminder number parameter 35, and the number 1 is modified to the number 3, and the modification operation is generated, and the terminal's operating system receives the parameter modification operation, and the reminder is given. The number of times is changed to 3.

Optionally, the calendar event creation interface provides a confirmation control, and the user triggers the confirmation control to save the modified parameters. Optionally, the confirmation control is a save option in the calendar event creation interface. For example, as shown in Figure 7, the user clicks save option 37 to save the modified parameters.

In addition, by displaying the calendar event creation interface, receiving the modification operation of the imported parameters, modifying the parameters imported in the calendar event creation interface according to the modification operation, thereby being able to generate calendar events according to the actual needs of the user, and improving the flexibility of creating calendar events. .

Please refer to FIG. 8 , which shows a structure of a calendar event creation apparatus provided by an embodiment of the present disclosure. Block diagram. The calendar event creating means may be implemented by software, hardware or a combination of both as all or part of the above-described terminal capable of providing a calendar event creating method. The device includes:

The first receiving module 810 is configured to receive a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application.

A creation module 820 is configured to create a calendar event in accordance with the first triggering operation.

The import module 830 is configured to import the parameters extracted from the third party application into the calendar event by the intent method.

In summary, the calendar event creation apparatus provided by the embodiment of the present disclosure extracts a parameter for creating a calendar event from a third-party application by triggering a calendar event creation control on a display interface of a third-party application, and uses an intent. The method of importing parameters into calendar events to automatically create calendar events solves the problem of manually inputting calendar event parameters when creating calendar events related to third-party applications, and automatically creates calendar events through third-party applications, reducing user input and improving The effect of calendar event creation efficiency.

Please refer to FIG. 9 , which is a structural block diagram of a calendar event creation apparatus according to another embodiment of the present disclosure. The calendar event creating means may be implemented by software, hardware or a combination of both as all or part of the above-described terminal capable of providing a calendar event creating method. The device includes:

The first receiving module 910 is configured to receive a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application.

A creation module 920 is configured to create a calendar event in accordance with the first triggering operation.

The import module 930 is configured to import the parameters extracted from the third party application into the calendar event by the intent method.

Optionally, the device further includes:

The switching module 940 is configured to: after importing the parameters extracted from the third-party application into the calendar event by using the intent method, switch the display interface of the third-party application to the calendar event creation interface, and display the imported parameters in the calendar event creation interface;

The second receiving module 950 is configured to receive a modification operation on the imported parameter;

The modification module 960 is configured to modify the imported parameters in the calendar event creation interface according to the modification operation.

Optionally, the parameter further includes a jump interface parameter, and the jump interface parameter is used to indicate a predetermined display interface that jumps when viewing the calendar event; the device further includes:

The first display module 970 is configured to display a calendar event prompt control after the prompt time of the calendar event is reached, and the reminding time of the calendar event is before the end time of the calendar event;

The third receiving module 980 is configured to receive a second triggering operation that is applied to the calendar event prompting control;

The display module 990 is configured to display a predetermined display interface according to the second triggering operation.

Optionally, the device further includes:

a control creation module 991 configured to create an activation event in the calendar application for providing an interface for creating a calendar event for the third party application before receiving the first triggering operation;

The creating module 920 includes a creating submodule 921 configured to invoke an activation event according to the first triggering operation to create a calendar event by the activation event.

The control creation module 991 is also configured to register the interface activity component in a configuration file of the calendar application.

A sub-module 921 is created that is also configured to create calendar events through the interface activity component.

In summary, the calendar event creation apparatus provided by the embodiment of the present disclosure extracts a parameter for creating a calendar event from a third-party application by triggering a calendar event creation control on a display interface of a third-party application, and uses an intent. The method of importing parameters into calendar events to automatically create calendar events solves the problem of manually inputting calendar event parameters when creating calendar events related to third-party applications, so that third-party applications can automatically create calendar events, reduce user input, and improve The effect of calendar event creation efficiency.

In addition, by inserting the jump interface parameter, when the reminder time of the calendar event is reached, the calendar event prompt control is displayed, and when the calendar event prompt control is triggered, jumping to the predetermined display interface can reduce the user operation and conveniently switch to The corresponding display interface of the content prompted by the calendar event.

An exemplary embodiment of the present disclosure provides a calendar event creation apparatus, the apparatus comprising:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

Receiving a first trigger action on a calendar event creation control provided by a third party application, third party The app is an app other than the calendar app;

Creating a calendar event according to the first triggering operation;

FIG. 10 is a block diagram of a calendar event creation apparatus, according to an exemplary embodiment. For example, device 1000 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.

Referring to FIG. 10, apparatus 1000 can include one or more of the following components: processing component 1002, memory 1004, power component 1006, multimedia component 1008, audio component 1010, input/output (I/O) interface 1012, sensor component 1014, and Communication component 1016.

Processing component 1002 typically controls the overall operation of device 1000, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. Processing component 1002 can include one or more processors 1018 to execute instructions to perform all or part of the steps of the above described methods. Moreover, processing component 1002 can include one or more modules to facilitate interaction between component 1002 and other components. For example, processing component 1002 can include a multimedia module to facilitate interaction between multimedia component 1008 and processing component 1002.

The memory 1004 is configured to store various types of data to support operation at the device 1000. Examples of such data include instructions for any application or method operating on device 1000, contact data, phone book data, messages, pictures, videos, and the like. The memory 1004 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable. Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.

Power component 1006 provides power to various components of device 1000. Power component 1006 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1000.

The multimedia component 1008 includes a screen between the device 1000 and the user that provides an output interface. In some embodiments, the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and hand on the touch panel Potential. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1008 includes a front camera and/or a rear camera. When the device 1000 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 1010 is configured to output and/or input an audio signal. For example, the audio component 1010 includes a microphone (MIC) that is configured to receive an external audio signal when the device 1000 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in memory 1004 or transmitted via communication component 1016. In some embodiments, the audio component 1010 also includes a speaker for outputting an audio signal.

The I/O interface 1012 provides an interface between the processing component 1002 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.

Sensor assembly 1014 includes one or more sensors for providing device 1000 with various aspects of state assessment. For example, the sensor assembly 1014 can detect an open/closed state of the device 1000, the relative positioning of the components, such as a display and a keypad of the device 1000, and the sensor assembly 1014 can also detect a change in position of a component of the device 1000 or device 1000, the user The presence or absence of contact with device 1000, device 1000 orientation or acceleration/deceleration and temperature variation of device 1000. Sensor assembly 1014 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1014 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1014 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communication component 1016 is configured to facilitate wired or wireless communication between device 1000 and other devices. The device 1000 can access a wireless network based on a communication standard, such as Wi-Fi, 2G or 3G, or a combination thereof. In an exemplary embodiment, communication component 1016 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, communication component 1016 also includes a near field communication (NFC) module to facilitate short range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, apparatus 1000 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the calendar event creation method described above.

In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium comprising instructions, such as a memory 1004 comprising instructions executable by processor 1018 of apparatus 1000 to perform the calendar event creation method described above. For example, the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.

Other embodiments of the present disclosure will be apparent to those skilled in the <RTIgt; The present application is intended to cover any variations, uses, or adaptations of the present disclosure, which are in accordance with the general principles of the disclosure and include common general knowledge or common technical means in the art that are not disclosed in the present disclosure. . The specification and examples are to be regarded as illustrative only,

It is to be understood that the invention is not limited to the details of the details and The scope of the disclosure is to be limited only by the appended claims.

Claims

A calendar event creation method, the method comprising:

Receiving a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application;

Creating a calendar event according to the first triggering operation;

The parameters extracted from the third-party application are imported into the calendar event by an intent method, and the parameters include at least a reminder content, a start time, and an end time.
The method of claim 1 further comprising:

After importing the parameters extracted from the third-party application into the calendar event by intent manner, switching the display interface of the third-party application to a calendar event creation interface, and displaying the imported parameters in the calendar event creation interface. ;

Receiving a modification operation on the imported parameter;

Modifying the imported parameters in the calendar event creation interface according to the modification operation.
The method according to claim 1 or 2, wherein the parameter further comprises a jump interface parameter, the jump interface parameter being used to indicate a predetermined display interface that jumps when viewing the calendar event; The method also includes:

After the reminding time of the calendar event is reached, a calendar event prompt control is displayed, and the reminding time of the calendar event is before the end time of the calendar event;

Receiving a second triggering operation acting on the calendar event prompt control;

Displaying the predetermined display interface according to the second triggering operation.
A method according to any one of claims 1 to 3, characterized in that

The method also includes creating an activation event in the calendar application, the activation event for providing an interface for creating the calendar event for the third party application, prior to receiving the first triggering operation;

The creating a calendar event according to the first triggering operation includes: invoking the activation event according to the first triggering operation, and creating the calendar event by using the activation event.
The method of claim 4 wherein said creating in said calendar application Activation events, including:

Registering an interface activity component in a configuration file of the calendar application;

The creating the calendar event by the activation event includes:

The calendar event is created by the interface activity component.
A calendar event creating device, the device comprising:

a first receiving module configured to receive a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application;

a creating module configured to create a calendar event according to the first triggering operation;

And an import module configured to import the parameters extracted from the third-party application into the calendar event by an intent manner.
The device according to claim 6, wherein the device further comprises:

a switching module, configured to switch the display interface of the third-party application to a calendar event creation interface after the parameter extracted from the third-party application is imported into the calendar event by an intent manner, and create the calendar event creation interface The imported parameters are displayed in the interface;

a second receiving module configured to receive a modification operation on the imported parameter;

And a modification module configured to modify the imported parameter in the calendar event creation interface according to the modification operation.
The apparatus according to claim 6 or 7, wherein the parameter further comprises a jump interface parameter, the jump interface parameter being used to indicate a predetermined display interface that jumps when viewing the calendar event; The device also includes:

a first display module, configured to display a calendar event prompt control after the prompt time of the calendar event is reached, the prompt time of the calendar event being before an end time of the calendar event;

a third receiving module configured to receive a second triggering operation that is applied to the calendar event prompting control;

And a display module configured to display the predetermined display interface according to the second triggering operation.
The device according to any one of claims 7 to 8, wherein the device further comprises:

a control creation module configured to apply to the calendar application before receiving the first triggering operation Creating an activation event for providing the third party application with an interface to create the calendar event;

The creating module includes:

A sub-module is created, configured to invoke the activation event in accordance with the first triggering operation, the calendar event being created by the activation event.
The apparatus of claim 9, wherein the control creation module is further configured to register an interface activity component in a configuration file of the calendar application.

The creating sub-module is further configured to create the calendar event by the interface activity component.
A calendar event creating device, the device comprising:

processor;

a memory for storing the processor executable instructions;

Wherein the processor is configured to:

Receiving a first triggering operation of a calendar event creation control provided by a third party application, the third party application being an application other than the calendar application;

Creating a calendar event according to the first triggering operation;

The parameters extracted from the third-party application are imported into the calendar event by an intent method, and the parameters include at least a reminder content, a start time, and an end time.