JP6282859B2 - Schedule management system and program for schedule management - Google Patents

Schedule management system and program for schedule management Download PDF

Info

Publication number
JP6282859B2
JP6282859B2 JP2013260488A JP2013260488A JP6282859B2 JP 6282859 B2 JP6282859 B2 JP 6282859B2 JP 2013260488 A JP2013260488 A JP 2013260488A JP 2013260488 A JP2013260488 A JP 2013260488A JP 6282859 B2 JP6282859 B2 JP 6282859B2
Authority
JP
Japan
Prior art keywords
schedule
calendar
application
url scheme
calendar application
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
JP2013260488A
Other languages
Japanese (ja)
Other versions
JP2015118465A (en
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 JP2013260488A priority Critical patent/JP6282859B2/en
Publication of JP2015118465A publication Critical patent/JP2015118465A/en
Application granted granted Critical
Publication of JP6282859B2 publication Critical patent/JP6282859B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to a schedule management system and a schedule management program, and more particularly, to a schedule management system for registering a schedule including one or more events to a calendar application, which is an application capable of managing a schedule in a calendar format. It is suitable for use in.

  Conventionally, an application that can manage a schedule in a calendar format (hereinafter referred to as a calendar application) has been provided. Most calendar apps have a schedule management function that registers and manages various events. An interface for registering events is generally one in which events are registered one by one by specifying a date.

  By the way, there is a case where it is desired to register a schedule in which the same event is repeatedly performed on a fixed day of the week or date, such as garbage collection, in the calendar application. In addition, there may be a case where it is desired to register a schedule in which a similar event is repeatedly performed on a known date in advance, such as the annual game schedule of a professional baseball team, in the calendar application.

  It is quite troublesome to register the same type of events over multiple days one by one. In view of this, a technique has been proposed in which a plurality of events of the same type that are performed regularly or irregularly can be efficiently registered (see, for example, Patent Documents 1 and 2).

  The scheduling apparatus described in Patent Document 1 stores input information for collectively inputting work contents and work schedules of a plurality of regular tasks, and calendar information related to a calendar including a calendar date and scheduled work contents. Calendar information storage means, and calendar information update means for reflecting the work contents to the work schedule contents with respect to the calendar date stored in the calendar information storage means corresponding to the work schedule collectively input by the input means. Yes.

  Further, the schedule management device described in Patent Document 2 is configured so that when a repetitive schedule is set, by directly touching and specifying each date on the schedule displayed on the schedule input calendar screen, the repetitive regularity Regardless of the date, it is possible to easily specify and set all dates regardless of the repetitive schedule of any date setting.

JP 2010-152594 A JP 2003-288330 A

  However, any of the conventional schedule management apparatuses described in Patent Documents 1 and 2 registers a schedule in a calendar as a mechanism in one calendar application, and schedules events set by another application. Could not be registered directly in the calendar app. Some recent calendar apps have a synchronization function with an online calendar on a website. However, this is just synchronization, and a new schedule that is not registered in the online calendar cannot be registered in the calendar application.

  An event schedule set by another application may be provided by an event information provider. In that case, instead of directly registering the schedule from another application to the calendar application, the calendar application schedule registration screen is displayed with the schedule contents and explanation reflected, and the user is notified of the details of the schedule. It is also desirable to prompt confirmation. However, it has not been possible to make a transition directly from another application to the calendar application schedule registration screen.

  The present invention has been made to solve such a problem, and it is possible to efficiently register a schedule of one or more events designated by another application in a calendar application. Objective.

  In order to solve the above-described problems, in the present invention, in another application that is an application different from the calendar application, the calendar application to be registered in the schedule, the command to be executed on the calendar application, and the contents of the schedule A URL scheme including parameters for specifying is generated and notified to the calendar application. Then, based on the notified URL scheme, the calendar application is activated and processing specified by the command is executed.

  According to the present invention configured as described above, a schedule of one or more events specified by another application can be generated by generating and executing a URL scheme specifying a parameter for specifying the contents of the schedule and an execution command. Can be directly registered in the calendar application, or the schedule registration screen of the calendar application can be directly displayed in a state in which the contents of the schedule or information related to the schedule is reflected. Thereby, the schedule of the 1 or more event designated with another application can be efficiently registered into a calendar application.

It is a figure which shows the hardware structural example of the schedule management system by this embodiment. It is a block diagram which shows the function structural example of the user terminal by this embodiment. It is a figure which shows an example of the input screen provided to a web browser. It is a figure which shows an example of the URL scheme of the character string form by this embodiment. It is a figure which shows an example of the schedule registration screen of the event by this embodiment. It is a figure which shows an example of the schedule registration screen of the event calendar by this embodiment. It is a figure which shows an example of the calendar screen of the calendar application with which the event calendar was registered.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a hardware configuration example of the schedule management system according to the present embodiment. As shown in FIG. 1, the schedule management system according to the present embodiment includes a user terminal 10, an event information providing server 20, and a Web server 30, which are configured to be connectable via a communication network 40 such as the Internet. Yes. The user terminal 10 is, for example, a mobile terminal such as a smartphone or a tablet, or a personal computer.

  The user terminal 10 includes a CPU 11, a ROM 12, a RAM 13, a hard disk 14, a display unit 15, an operation unit 16, and a communication I / F unit 17 as hardware configurations. The CPU 11 controls the operation of the user terminal 10 according to a schedule management program stored in the ROM 12, RAM 13, or hard disk 14. The display unit 15 and the operation unit 16 are configured by a display with a touch panel, for example. The communication I / F unit 17 performs communication between the event information providing server 20 and the Web server 30 via the communication network 40.

  The hard disk 14 stores a calendar application 101 that is an application whose schedule can be managed in a calendar format, and another application 102 that is an application different from the calendar application 101. Both the calendar application 101 and the separate application 102 include the schedule management program of the present invention. The schedule management system of this embodiment provides a function for registering a schedule including one or more events from another application 102 to the calendar application 101.

  The schedule management system of the present embodiment has a function for registering a schedule for one event in the calendar application 101 (event registration function) and a function for collectively registering a schedule for an event calendar including a plurality of events in the calendar application 101 (event calendar). Registration function). The different application 102 only needs to be different from the calendar application 101, and the content of the application does not matter. For example, the separate application 102 is an application having a function of inputting event schedule information. Alternatively, the separate application 102 may be a web browser that can access the web server 30.

  The event information providing server 20 includes a database 20A that stores schedule data related to an event calendar. The schedule data regarding each event calendar is stored in association with the event calendar ID. The schedule data is irregular, such as those related to a regular schedule where the same event is repeated every day, such as garbage collection, or the annual game schedule of a favorite baseball team Is related to an irregular schedule in which the same type of event is repeated on a date that is known in advance. This schedule data indicates the contents and explanation of the schedule, and includes information such as the implementation date, implementation contents, and detailed explanation of the events of a plurality of events.

  FIG. 2 is a block diagram illustrating an example of a functional configuration realized by executing a schedule management program included in the calendar application 101 and another application 102 stored in the user terminal 10. As shown in FIG. 2, the user terminal 10 includes a URL scheme generation unit 21, a URL scheme notification unit 22, and a URL scheme execution unit 23 as functional configurations. The URL scheme generation unit 21 and the URL scheme notification unit 22 are realized by a schedule management program included in another application 102. On the other hand, the URL scheme execution unit 23 is realized by a schedule management program included in the calendar application 101.

  The URL scheme generation unit 21 generates a URL scheme including a calendar application 101 to be registered in a schedule, a command to be executed for the calendar application 101, and a parameter for specifying the contents of the schedule in another application 102. . The URL scheme generation unit 21 provides a function of generating a URL scheme as an internal process of the user terminal 10 and a function of accessing a website provided by the Web server 30 and generating a URL scheme.

  FIG. 3 is a diagram illustrating an example of an input screen that is provided to a web browser by accessing a website provided by the web server 30 when the different application 102 is a web browser. FIG. 3A shows an input screen used when registering one event in the calendar application 101, and FIG. 3B shows an input screen used when registering an event calendar in the calendar application 101.

  When registering one event, as shown in FIG. 3A, schedule information such as an event title, start date / time, end date / time, location, and contents is input. On the other hand, when registering an event calendar, a desired event calendar ID is input as shown in FIG. Up to five event calendar IDs can be input in this example.

  When the “Create URL” or “Create QR code” button (existing in the screen scrolled in FIG. 3A) is pressed, the URL scheme generation unit 21 executes the URL based on the input information. Generate a scheme. Here, when the “Create URL” button is pressed, the URL scheme generation unit 21 generates the URL scheme in the form of a character string. On the other hand, when the “Create QR code” button is pressed, the URL scheme generation unit 21 generates a URL scheme in the form of a QR code.

  Note that the URL scheme generated when the “Create URL” or “Create QR Code” button is pressed is for calling the schedule registration screen of the calendar application 101. On the other hand, when the “event calendar registration” button shown in FIG. 3B (in the case of FIG. 3A, the “event registration” button that exists after scrolling the screen) is pressed, the URL scheme generation unit 21 generates a URL scheme for directly registering a schedule in the calendar application 101 according to the input information.

  When another application 102 is an application that is not a web browser and generates a URL scheme as an internal process of the user terminal 10, the user inputs schedule information related to one event using a function of the other application 102. The URL scheme generation unit 21 generates a URL scheme based on the information input in this way. Note that the input screen in this case depends on the implementation of the separate application 102, but there may be input items and buttons similar to those shown in FIG.

  FIG. 4 is a diagram illustrating an example of a URL scheme in the form of a character string generated by the URL scheme generation unit 21. In FIG. 4, the part denoted by reference numeral 41 indicates the URL of the Web server 30. This URL is information generated when another application 102 is a web browser, that is, when a URL scheme is generated through the input screen of FIG. 3 provided from the Web server 30 and the calendar application 101 is called through the Web server 30. It is.

  On the other hand, when the separate application 102 is an application that is not a web browser and generates a URL scheme as an internal process of the user terminal 10, the calendar application 101 is directly called from the separate application 102 without using the Web server 30. In this case, the URL of the Web server 30 indicated by reference numeral 41 is not necessary.

The part shown by the code | symbol 42 shows the name of the calendar application 101 made into the registration object of a schedule. Here, the scheme is such that the calendar application 101 whose name is described can be activated. A portion denoted by reference numeral 43 indicates a command to be executed for the calendar application 101. Examples of commands include the following.
app Launch Calendar App 101
deliverEventRegister Register events directly to the Calendar app 101
scheduleRegister Direct registration of event calendar to calendar app 101
deliverEventDetail Call schedule registration screen (detailed event information)

A portion denoted by reference numeral 44 indicates a parameter for specifying the contents of the schedule. The example of FIG. 4 shows parameters for registering an event calendar in the calendar application 101. That is, the parameter in this case is an event calendar ID with “cid = 201024”. On the other hand, the parameters for registering one event in the calendar application 101 include schedule information input through the input screen of FIG. 3A, and are specified by the following character string, for example.
"Title = Alumni Association Schedule & dtstart = 20131130163000 & dtend = 20131130183000 & allDay = 0 & eventLocation = Roppongi, Minato-ku, Tokyo & description = Alumni Association will be held. Membership fee 4,500 yen Secretary: Hirata (080-5555-5555)"

  The URL scheme notification unit 22 notifies the calendar application 101 of the URL scheme generated by the URL scheme generation unit 21. As described above, there are two notification methods. That is, when another application 102 is an application that is not a web browser and the URL scheme generation unit 21 generates a URL scheme as an internal process of the user terminal 10, the URL scheme notification unit 22 directly notifies the calendar application 101 of the URL scheme. To do.

  On the other hand, when another application 102 is a web browser and the URL scheme generation unit 21 generates a URL scheme through an input screen provided from the Web server 30, the URL scheme notification unit 22 is shown at the top of the URL scheme. The URL scheme is notified to the calendar application 101 via the Web server 30 according to the URL.

  Based on the URL scheme notified by the URL scheme notification unit 22, the URL scheme execution unit 23 activates the calendar application 101 and executes processing specified by the command. For example, when a command for calling the schedule registration screen is specified by the URL scheme, the URL scheme execution unit 23 calls the schedule registration screen of the calendar application 101 and relates to the schedule content or schedule specified by the parameter. The schedule registration screen is displayed on the display unit 15 with the information reflected.

  Here, when the content of the schedule related to one event is specified by the parameter, the URL scheme execution unit 23 calls the schedule registration screen of the calendar application 101, and the content of the schedule specified by the parameter (schedule information of the event) Is input to each input item, and the schedule registration screen is displayed on the display unit 15.

  FIG. 5 is a diagram illustrating an example of an event schedule registration screen. As shown in FIG. 5, the schedule registration screen for one event is displayed in a state where the schedule information input through the input screen of FIG. 3A is input to each input item. The user confirms the contents displayed on the schedule registration screen, and presses the “Register” button if there is no problem. As a result, a schedule related to one event is registered in the calendar application 101.

  When the schedule content (event calendar ID) relating to the event calendar is specified by the parameter, the URL scheme execution unit 23 accesses the event information providing server 20 and obtains schedule data corresponding to the event calendar ID from the database 20A. get. Then, the schedule registration screen of the calendar application 101 is called, and the schedule registration screen is displayed on the display unit 15 in a state in which the description included in the schedule data acquired from the database 20A is included.

  FIG. 6 is a diagram illustrating an example of an event calendar schedule registration screen. FIG. 6A shows a schedule registration screen for an event calendar related to garbage collection. In the example shown in FIG. 6A, an explanation of an event calendar related to garbage collection is displayed, and an introduction of an additional function is displayed. The additional function is a function for purchasing an icon to be displayed on the calendar of the calendar application 101, for example. When the user wishes to purchase an icon, the user can transition to an icon purchase site by pressing the “Store” button and purchase the desired icon. When the purchase of the icon is finished, the screen returns to the screen of FIG.

  FIG. 6B shows an event calendar schedule registration screen regarding the annual game schedule of a favorite baseball team of professional baseball. In the example shown in FIG. 6B, an explanation of an event calendar related to the annual game schedule is displayed, and an introduction of additional functions is displayed. The additional function is, for example, a function for purchasing a scoreboard that informs the game breaking news. In the example of FIG. 6 (b), “Purchased” is displayed. If you have not purchased the scoreboard and wish to purchase the scoreboard, you can switch to the purchase site by pressing the “Store” button. It is possible to purchase a scoreboard. When the purchase of the scoreboard is finished, the screen returns to the screen of FIG.

  When a plurality of event calendar IDs are input on the input screen of FIG. 3B, information on the plurality of event calendars is displayed on the schedule registration screen. For example, when an event calendar ID related to garbage collection and an event calendar ID related to an annual game schedule are input, the information shown in FIG. 6A and the information shown in FIG. 6B are arranged in order on the schedule registration screen. Is displayed.

  The user confirms the explanation content displayed on the schedule registration screen as shown in FIG. 6 and presses an “add” button if there is no problem. As a result, schedules related to a plurality of events included in the event calendar are collectively registered in the calendar application 101.

  FIG. 7 is a diagram illustrating an example of a calendar screen of the calendar application 101 in which an event calendar is registered. FIG. 7A shows a calendar screen displayed when an event calendar related to garbage collection is registered. As shown in FIG. 7A, an icon representing garbage collection is displayed on the date cell corresponding to the garbage collection date. FIG. 7B shows a calendar screen displayed when an event calendar related to the annual game schedule is registered. As shown in FIG. 7B, an icon representing the opponent is displayed on the date cell corresponding to the game day. A purchased scoreboard is displayed below the calendar.

  As described above in detail, in this embodiment, in another application 102, a calendar application 101 to be registered as a schedule, a command to be executed for the calendar application 101, and a parameter for specifying the content of the schedule are included. A URL scheme is generated and notified to the calendar application 101. Then, based on the URL scheme notified from the other application 102, the calendar application 101 is activated and processing specified by the command is executed.

  According to the schedule management system of the present embodiment configured as described above, an event specified by another application 102 can be generated by generating and executing a URL scheme specifying a parameter for specifying the schedule contents and an execution command. In addition, the schedule of the event calendar can be directly registered in the calendar application 101, or the schedule registration screen of the calendar application 101 can be directly displayed in a state where the contents of the schedule or information such as an explanation or an additional function is reflected. As a result, an event designated by another application 102 or an event calendar schedule can be efficiently registered in the calendar application 102.

  In addition, when registering an event calendar from another application 102 to the calendar application 101, it is possible to provide information useful to the user such as explanation information of the event calendar by displaying a schedule registration screen related to the event calendar. In addition, since it is possible to provide an interface of an additional function for the user to purchase contents and items related to the event calendar, it is possible to bring about an advertising effect as seen from the event information provider.

  In the above embodiment, the case where the calendar application 101 and the separate application 102 exist in the same user terminal 10 has been described, but the present invention is not limited to this. For example, when the URL scheme is notified from the different application 102 to the calendar application 101 via the Web server 30, the calendar application 101 and the different application 102 may exist in different user terminals 10. However, in this case, it is necessary to include the address of the user terminal 10 as the destination in the URL scheme.

  Moreover, although the said embodiment demonstrated the example which inputs an event calendar ID directly like FIG.3 (b), this invention is not limited to this. For example, a list of event calendars may be displayed, and when the user selects a desired event calendar from the list, the corresponding event calendar ID may be automatically input.

  In the above embodiment, when the event calendar schedule data stored in the database 20A of the event information providing server 20 is updated, the event calendar schedule registered in the calendar application 101 of the user terminal 10 is automatically set. You may make it update automatically. For example, the calendar application 101 of the user terminal 10 periodically accesses the event information providing server 20 to notify the event calendar ID and confirms whether or not the corresponding schedule data has been updated. When the update is confirmed, the schedule data of the event calendar is acquired from the event information providing server 20 and the schedule of the calendar application 101 is updated.

  Alternatively, when the user terminal 10 obtains event calendar schedule data from the event information providing server 20, the address of the user terminal 10 is associated with the event calendar ID and stored in the event information providing server 20. Then, when the event calendar schedule data in the database 20A is updated, the calendar application 101 of the user terminal 10 is called from the event information providing server 20 by the URL scheme, and the event calendar schedule of the calendar application 101 is automatically updated. It may be.

  In addition, each of the above-described embodiments is merely an example of implementation in carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner. That is, the present invention can be implemented in various forms without departing from the gist or the main features thereof.

DESCRIPTION OF SYMBOLS 10 User terminal 20 Event information provision server 30 Web server 21 URL scheme production | generation part 22 URL scheme notification part 23 URL scheme execution part 101 Calendar application 102 Another application

Claims (6)

  1. A schedule management system for registering a schedule including one or more events for a calendar application, which is an application capable of managing a schedule in a calendar format,
    In another application which is an application different from the calendar application, a URL including the calendar application to be registered in the schedule, a command to be executed for the calendar application, and a parameter for specifying the content of the schedule A URL scheme generation unit for generating a scheme;
    A URL scheme notifying unit for notifying the calendar application of the URL scheme generated by the URL scheme generating unit;
    A schedule management system comprising: a URL scheme execution unit that activates the calendar application and executes a process specified by the command based on the URL scheme notified by the URL scheme notification unit.
  2. The above command is a command for calling the schedule registration screen.
    The URL scheme execution unit calls the schedule registration screen of the calendar application and displays the schedule registration screen in a state reflecting the contents of the schedule specified by the parameters or information related to the schedule. The schedule management system according to claim 1.
  3.   When the content of the schedule related to one event is specified by the parameter, the URL scheme execution unit calls the schedule registration screen of the calendar application, and inputs the content of the schedule specified by the parameter as an input item. The schedule management system according to claim 2, wherein the schedule registration screen is displayed in a state in which the schedule is displayed.
  4.   When the contents of a schedule related to an event calendar including a plurality of events are specified by the parameters, the URL scheme execution unit acquires the schedule contents and description information specified by the parameters from the server, and the calendar 3. The schedule management system according to claim 2, wherein the schedule registration screen is displayed by calling the schedule registration screen of the app and including at least the information described above.
  5. A schedule management program for registering a schedule including one or more events for a calendar application, which is an application capable of managing a schedule in a calendar format,
    In another application which is an application different from the calendar application, a URL including the calendar application to be registered in the schedule, a command to be executed for the calendar application, and a parameter for specifying the content of the schedule A URL scheme generating means for generating a scheme, and a schedule management program for causing a computer to function as a URL scheme notifying means for notifying the calendar application of the URL scheme generated by the URL scheme generating means.
  6.   Claim 5 for further causing the computer to function as URL scheme execution means for starting the calendar application and executing processing specified by the command based on the URL scheme notified by the URL scheme notification means. Program for schedule management described.
JP2013260488A 2013-12-17 2013-12-17 Schedule management system and program for schedule management Active JP6282859B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2013260488A JP6282859B2 (en) 2013-12-17 2013-12-17 Schedule management system and program for schedule management

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2013260488A JP6282859B2 (en) 2013-12-17 2013-12-17 Schedule management system and program for schedule management

Publications (2)

Publication Number Publication Date
JP2015118465A JP2015118465A (en) 2015-06-25
JP6282859B2 true JP6282859B2 (en) 2018-02-21

Family

ID=53531150

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2013260488A Active JP6282859B2 (en) 2013-12-17 2013-12-17 Schedule management system and program for schedule management

Country Status (1)

Country Link
JP (1) JP6282859B2 (en)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI102869B (en) * 1996-02-26 1999-02-26 Nokia Mobile Phones Ltd The device, method, and system ähettämiseksi and receiving information relating to the various applications l
CN100485603C (en) * 2003-04-04 2009-05-06 雅虎公司 Systems and methods for generating concept units from search queries
JP2006178940A (en) * 2004-11-25 2006-07-06 Towa Kagaku Kk Refuse collection calendar creation device, refuse collection calendar creation software, refuse collection calendar information creation system and information terminal device
US20060277087A1 (en) * 2005-06-06 2006-12-07 Error Brett M User interface for web analytics tools and method for automatic generation of calendar notes, targets,and alerts
JP2013168733A (en) * 2012-02-14 2013-08-29 Toshiba Corp Electronic device and method of controlling the same

Also Published As

Publication number Publication date
JP2015118465A (en) 2015-06-25

Similar Documents

Publication Publication Date Title
AU2009322760B2 (en) Isolating received information on a locked device
EP2353344B1 (en) Providing selected data through a locked display
US20140189541A1 (en) Content sharing interface for sharing content in social networks
US20130227476A1 (en) Method, apparatus and computer program product for management of information on a graphic user interface
EP2843612A1 (en) Electronic device, social tile displaying method, and tile connection method
US20150058821A1 (en) Mobile design patterns
US10088973B2 (en) Event scheduling presentation in a graphical user interface environment
US7721210B2 (en) Electronic calendar system
CN103927074B (en) Configure the device for mobile communication and its usability methods of the key frame of device for mobile communication
US8577960B2 (en) Providing status information for components in a distributed landscape
US20130246111A1 (en) Use of touch and gestures related to tasks and business workflow
TWI564734B (en) Method and computing device for providing dynamic navigation bar for expanded communication service
CN104081382B (en) Establish the method and system for the user interface that can dynamically specify
TWI569198B (en) Dynamic minimized navigation bar for expanded communication service
CN104838353A (en) Coordination contextual display data on a display screen
CA2473643A1 (en) Calendar overlays
US20180307382A1 (en) Event listening integration in a collaborative electronic information system
JP2014516180A (en) Social information management method and system adapted thereto
CN102939583B (en) Creation task session
US20120216146A1 (en) Method, apparatus and computer program product for integrated application and task manager display
US9977800B2 (en) Systems and methods for enabling a user to operate on displayed web content via a web browser plug-in
JP2011066850A (en) Information communication terminal
TWI564782B (en) Docking and undocking dynamic navigation bar for expanded communication service
TWI459293B (en) Hand-held electronic device, operation method applicable thereto and computer-readable recording media
CN102662649A (en) Method and apparatus for customizing function menu of application programs

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20161205

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20171220

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20171226

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20180125

R150 Certificate of patent or registration of utility model

Ref document number: 6282859

Country of ref document: JP

Free format text: JAPANESE INTERMEDIATE CODE: R150