WO2018018361A1 - Procédé et dispositif de création d'événement dans un calendrier - Google Patents

Procédé et dispositif de création d'événement dans un calendrier Download PDF

Info

Publication number
WO2018018361A1
WO2018018361A1 PCT/CN2016/091544 CN2016091544W WO2018018361A1 WO 2018018361 A1 WO2018018361 A1 WO 2018018361A1 CN 2016091544 W CN2016091544 W CN 2016091544W WO 2018018361 A1 WO2018018361 A1 WO 2018018361A1
Authority
WO
WIPO (PCT)
Prior art keywords
calendar event
calendar
interface
application
party application
Prior art date
Application number
PCT/CN2016/091544
Other languages
English (en)
Chinese (zh)
Inventor
伍亮雄
刘海涛
骆艳飞
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN201680000812.3A priority Critical patent/CN106462835A/zh
Priority to PCT/CN2016/091544 priority patent/WO2018018361A1/fr
Publication of WO2018018361A1 publication Critical patent/WO2018018361A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system

Definitions

  • the embodiments of the present disclosure relate to the field of mobile terminals, and in particular, to a calendar event creation method and apparatus.
  • 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.
  • the present disclosure provides a calendar event creation method and apparatus.
  • the technical solution is as follows:
  • an embodiment of the present disclosure provides a method for creating a calendar event, the method comprising:
  • 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.
  • import the parameters for creating calendar events in the third-party application into the calendar event creation interface including:
  • 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 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:
  • the calendar event prompt control is displayed, and the reminding time of the calendar event is before the end time of the calendar event;
  • the predetermined display interface is displayed according to the second triggering operation.
  • the method further includes:
  • 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.
  • create an activation event in the calendar app including:
  • 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.
  • 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.
  • 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.
  • the device further includes:
  • 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.
  • 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.
  • an embodiment of the present disclosure provides a calendar event creation device, where the device includes:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • 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 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.
  • 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.
  • FIG. 1 is a flowchart of a method for creating a calendar event according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for providing a calendar event creation method according to another embodiment of the present disclosure
  • FIG. 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
  • FIG. 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. 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.
  • 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.
  • Android Android
  • FIG. 1 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.
  • the calendar event creation method can include the following steps.
  • 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.
  • step 102 a calendar event is created in accordance with the first triggering operation.
  • 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.
  • the parameters for importing the calendar event include at least the reminder content, the start time, and the end time.
  • 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.
  • 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.
  • the calendar event creation method 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.
  • FIG. 2 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.
  • the calendar event creation method may include the following steps.
  • 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.
  • 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.
  • 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.
  • 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.
  • the interface activity component is the Activity, and an Activity is applicable to all third applications that need to create calendar events.
  • 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.
  • 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:
  • step 202 a first triggering operation is applied to a calendar event creation control provided by a third party application.
  • 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.
  • the display interface in the current terminal is the display interface 31 of a broadcast application.
  • the operating system of the terminal receives the first triggering action acting on the calendar creation control 32.
  • 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.
  • 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.
  • 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.
  • 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.
  • the parameters for importing calendar events include at least reminder content, start time, and end time.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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");
  • the third application creates a calendar event in the background.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the jump interface parameter is a link corresponding to the predetermined display interface.
  • 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 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.
  • the calendar prompt control is used to display the reminder content and the start time of the calendar event.
  • step 206 a second triggering action is applied to the calendar event prompt control.
  • step 207 a predetermined display interface is displayed 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.
  • the reminder time of a calendar event is 19:30, and the content of the calendar event is listening to the broadcast program.
  • 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 .
  • 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.
  • the calendar event creation method 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the shopping application is used to create a calendar event about the purchase of the item.
  • 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.
  • step 204b a modification operation on the imported parameters is received.
  • the corresponding parameter is changed or added to generate a modification operation, and the operating system of the terminal receives the modification operation.
  • 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.
  • step 204c the imported parameters in the calendar event creation interface are modified according to the modification operation.
  • 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.
  • the calendar event creation interface provides a confirmation control, and the user triggers the confirmation control to save the modified parameters.
  • 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.
  • FIG. 8 shows a structure of a calendar event creation apparatus provided by an 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 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.
  • the calendar event creation apparatus 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.
  • FIG. 9 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.
  • 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.
  • 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.
  • the device further includes:
  • 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.
  • the calendar event creation apparatus 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.
  • 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:
  • a memory for storing processor executable instructions
  • processor is configured to:
  • third party 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;
  • 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.
  • FIG. 10 is a block diagram of a calendar event creation apparatus, according to an exemplary embodiment.
  • 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.
  • 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.
  • processing component 1002 can include one or more modules to facilitate interaction between component 1002 and other components.
  • 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.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Disk Disk
  • Optical Disk 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • communication component 1016 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
  • communication component 1016 also includes a near field communication (NFC) module to facilitate short range communication.
  • NFC near field communication
  • 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.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • 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.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the calendar event creation method described above.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Human Computer Interaction (AREA)
  • User Interface Of Digital Computer (AREA)
  • Telephone Function (AREA)

Abstract

La présente invention concerne un procédé et un dispositif de création d'événement dans un calendrier, dans le domaine des terminaux mobiles. Le procédé consiste : à recevoir une première opération de déclenchement effectuée sur un événement dans un calendrier créant une commande fournie par une application tierce, l'application tierce étant une application autre qu'une application dans un calendrier (101) ; à créer un événement dans un calendrier selon la première opération de déclenchement (102) ; et à importer des paramètres extraits de l'application tierce vers l'événement dans un calendrier en utilisant une approche d'intention, les paramètres comprenant au moins un contenu de rappel, un temps de départ et un temps de fin (103). Le procédé résout le problème selon lequel un utilisateur a besoin d'entrer manuellement des paramètres de création d'événement dans un calendrier lors de la création d'un événement dans un calendrier associé à une application tierce. L'application tierce peut automatiquement créer un événement dans un calendrier, en réduisant ainsi les saisies d'utilisateur et en améliorant l'efficacité de création d'événement dans un calendrier.
PCT/CN2016/091544 2016-07-25 2016-07-25 Procédé et dispositif de création d'événement dans un calendrier WO2018018361A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201680000812.3A CN106462835A (zh) 2016-07-25 2016-07-25 日历事件创建方法及装置
PCT/CN2016/091544 WO2018018361A1 (fr) 2016-07-25 2016-07-25 Procédé et dispositif de création d'événement dans un calendrier

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/091544 WO2018018361A1 (fr) 2016-07-25 2016-07-25 Procédé et dispositif de création d'événement dans un calendrier

Publications (1)

Publication Number Publication Date
WO2018018361A1 true WO2018018361A1 (fr) 2018-02-01

Family

ID=58215594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/091544 WO2018018361A1 (fr) 2016-07-25 2016-07-25 Procédé et dispositif de création d'événement dans un calendrier

Country Status (2)

Country Link
CN (1) CN106462835A (fr)
WO (1) WO2018018361A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107613090A (zh) * 2017-08-04 2018-01-19 捷开通讯(深圳)有限公司 一种提醒事项的记录方法、移动终端以及存储设备
CN107809531A (zh) * 2017-10-18 2018-03-16 维沃移动通信有限公司 一种日程创建方法、移动终端
CN109032453A (zh) * 2018-08-24 2018-12-18 北京新界教育科技有限公司 显示方法及装置
CN110286976B (zh) * 2019-05-24 2021-10-01 华为技术有限公司 界面显示方法、装置、终端及存储介质
CN112162786A (zh) * 2020-09-02 2021-01-01 北京小米移动软件有限公司 信息展示方法、装置及计算机可读存储介质
CN115225758B (zh) * 2021-04-19 2024-06-25 华为技术有限公司 通知方法、相关装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001089206A2 (fr) * 2000-05-12 2001-11-22 At & T Corp. Procede et systeme de presentation d'un guide de programmation electronique
CN1600021A (zh) * 2001-11-07 2005-03-23 诺基亚公司 从远程源将内容自动记录到pc的电子日历中的方法
CN103369113A (zh) * 2012-03-30 2013-10-23 厦门毅想通信研发中心有限公司 一种处理来电信息的方法和移动终端
CN103986836A (zh) * 2014-05-28 2014-08-13 小米科技有限责任公司 日历提醒的方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9547846B2 (en) * 2011-02-24 2017-01-17 Good Technology Holdings Limited Method and apparatus for the processing of data relating to calendar entries
CN103780740A (zh) * 2012-10-17 2014-05-07 汉峰世纪科技(北京)有限公司 一种日历与电话信息交互处理的方法
CN104240067A (zh) * 2013-06-24 2014-12-24 腾讯科技（深圳）有限公司 提醒设置方法、装置及电子设备
CN103632253A (zh) * 2013-10-28 2014-03-12 金蝶软件（中国）有限公司 一种创建日历的方法和装置
CN104657846A (zh) * 2015-03-19 2015-05-27 上海斐讯数据通信技术有限公司 一种移动终端的日历事件提醒方法及其系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001089206A2 (fr) * 2000-05-12 2001-11-22 At & T Corp. Procede et systeme de presentation d'un guide de programmation electronique
CN1600021A (zh) * 2001-11-07 2005-03-23 诺基亚公司 从远程源将内容自动记录到pc的电子日历中的方法
CN103369113A (zh) * 2012-03-30 2013-10-23 厦门毅想通信研发中心有限公司 一种处理来电信息的方法和移动终端
CN103986836A (zh) * 2014-05-28 2014-08-13 小米科技有限责任公司 日历提醒的方法及装置

Also Published As

Publication number Publication date
CN106462835A (zh) 2017-02-22

Similar Documents

Publication Publication Date Title
US10264085B2 (en) Method and device for presenting push notifications
WO2018018361A1 (fr) Procédé et dispositif de création d'événement dans un calendrier
US11204779B2 (en) Terminal control method and apparatus, terminal and storage medium
WO2017114457A1 (fr) Procédé et dispositif de traitement de messages instantanés
WO2017201860A1 (fr) Procédé et dispositif de diffusion vidéo en direct en continu
CN105306718B (zh) 事件提示方法及装置
US9800666B2 (en) Method and client terminal for remote assistance
EP3232340A1 (fr) Procédé de fonctionnement d'un afficheur et afficheur permettant d'afficher des pages d'un programme d'application
WO2017113666A1 (fr) Procédé et dispositif de commutation d'interface d'application
EP3104587B1 (fr) Procédé et appareil pour l'affichage d'une interface de conversation
WO2017084183A1 (fr) Procédé et dispositif de traitement d'informations
KR20160077011A (ko) 스마트 홈 디바이스의 운전상태 조절 방법, 장치, 프로그램 및 기록매체
JP6145221B2 (ja) スケジュール管理方法、装置、プログラム、及び記録媒体
CN109669730B (zh) 一种进程保活方法、装置、电子设备及介质
CN106528273B (zh) 应用程序管理方法及装置
JP2016533110A5 (fr)
CN105260247A (zh) 一种控制终端应用的方法及装置
US20170308397A1 (en) Method and apparatus for managing task of instant messaging application
CN111552426B (zh) 智能设备的操作方法、装置及存储介质
CN106547462B (zh) 拍照控制方法、装置及移动终端
CN109521923B (zh) 悬浮窗控制方法、装置及存储介质
CN108984098B (zh) 基于社交软件的信息显示的控制方法及装置
CN105704286A (zh) 一种通讯信息的展示方法及装置
US11397596B2 (en) Method and device for controlling pop-up window, electronic device, and storage medium
WO2019051836A1 (fr) Procédé et appareil de réponse à des informations

Legal Events

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

Ref document number: 16909942

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16909942

Country of ref document: EP

Kind code of ref document: A1