KR102649690B1 - Electronic apparatus and managing a job schedule method thereof - Google Patents

Abstract

A method for managing a work schedule for an electronic device is disclosed. The work schedule management method includes checking a code including information about a first job and information about a first time set for performing the first job; providing a first work schedule generated based on the information about the first task and the information about the first time set; Based on the information about the first set of times, performing the first task; And it may include providing performance result information of the first task.

Description

Electronic device and its work schedule management method {ELECTRONIC APPARATUS AND MANAGING A JOB SCHEDULE METHOD THEREOF}

This disclosure relates to an electronic device that provides a platform that allows users to more conveniently manage work schedules and a control method thereof.

Before distributing an application, developers must perform various tests on the application to ensure that the application satisfies the required functions, performance, usability, stability, etc. Additionally, since the type and amount of data obtained from customers every day is different, developers must repeatedly perform the same tests based on different data.

However, in order to repeatedly perform the same test based on different data, various parameters must be set, and if a developer manually sets various parameters by directly modifying the code, there is a problem that a lot of time and manpower is wasted.

In this regard, prior literature such as KR 10-1553649 B1 may be referred to.

The disclosed embodiments seek to provide an electronic device and a method for managing its work schedule. More specifically, the object is to provide an electronic device and a control method thereof that provide a platform that allows users to more conveniently manage work schedules.

The technical challenges that this embodiment aims to achieve are not limited to the technical challenges described above, and other technical challenges can be inferred from the following embodiments.

One aspect of the present disclosure includes identifying code that includes information about a first job and information about a first set of times for performing the first job; providing a first work schedule generated based on the information about the first task and the information about the first time set; Based on the information about the first set of times, performing the first task; and providing performance result information of the first task.

Additionally, in one embodiment of the present disclosure, the information about the first time set includes information about a first cycle, and performing the first task includes performing the first task every first cycle. A work schedule management method including: can be provided.

Additionally, in an embodiment of the present disclosure, the work schedule management method may further include providing a list of a plurality of work schedules including the first work schedule.

In addition, in one embodiment of the present disclosure, the work schedule management method includes obtaining a user input for changing information about a second cycle of a second work schedule among the list of the plurality of work schedules; And based on the changed information about the second cycle, performing a second task corresponding to the second work schedule every changed second cycle may be provided.

In addition, in an embodiment of the present disclosure, the work schedule management method further includes providing information about an expected execution time of the second task based on changed information about the second cycle, the work schedule Management methods can be provided.

In addition, in one embodiment of the present disclosure, the information about the first time set further includes information about a first date for performing the first task, and the task schedule management method includes performing the first task. Obtaining user input to: confirming data corresponding to the first date; and performing the first task based on data corresponding to the first date.

Additionally, in one embodiment of the present disclosure, the step of performing the first task on the first date includes, when the first date is not set, a user input regarding a second date for performing the first task. acquiring; confirming data corresponding to the second date; and performing the first task based on data corresponding to the second date.

In addition, in one embodiment of the present disclosure, the code further includes information about at least one user to provide a notification, and the task schedule management method includes, when performance of the first task fails, the first task A work schedule management method may be provided, further comprising providing a notification regarding performance failure to the at least one user.

In addition, in one embodiment of the present disclosure, the code further includes information about at least one port, and performing the first task every first cycle may include performing the first task on the server corresponding to the at least one port. A work schedule management method including the step of performing a first task may be provided.

In addition, in one embodiment of the present disclosure, the work schedule management method includes: obtaining a user input to stop performing a third task corresponding to a third task schedule among the list of the plurality of task schedules; and omitting repeated performance of the third task.

In addition, in an embodiment of the present disclosure, the work schedule management method further includes providing information regarding the status of a fourth work schedule among the list of the plurality of work schedules, and the status of the fourth work schedule is A work schedule management method including at least one of a performable state and a performing state may be provided.

Additionally, in one embodiment of the present disclosure, the work schedule management method may be initiated by obtaining a pull request from a user terminal.

In addition, in one embodiment of the present disclosure, the work schedule management method includes: checking at least one date on which performance of the first task failed, based on performance result information of the first task; confirming data corresponding to the at least one date; and performing the first task based on data corresponding to the at least one date.

In addition, in one embodiment of the present disclosure, the information about the first time set further includes information about an expiration date, and performing the first task includes performing the first task until the expiration date. A work schedule management method including steps performed every cycle may be provided.

Another aspect of the present disclosure includes a communication unit, a memory, and a controller, wherein the controller identifies a code that includes information about a first task and information about a first set of times for performing the first task. and providing a first work schedule created based on the information about the first task and the information about the first time set, and performing the first task based on the information about the first time set. , an electronic device that provides information on the performance result of the first task can be provided.

Another aspect of the present disclosure may provide a computer-readable recording medium on which a program for implementing a method performed by an electronic device is recorded.

Specific details of other embodiments are included in the detailed description and drawings.

If you follow the proposed embodiment, one or more of the following effects can be expected.

According to the embodiments of the present specification, the user can set a cycle or date to perform tasks more conveniently.

Additionally, according to the embodiments of the present specification, when performance of a task fails, the user can more conveniently receive notification that the task has failed.

The effect of the invention is not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

1 shows a system according to one embodiment.
FIG. 2 is a diagram illustrating a process in which an electronic device manages a work schedule according to an embodiment.
3A to 3B illustrate a user interface provided by an electronic device, according to an embodiment.
4A to 4C illustrate a user interface provided by an electronic device, according to an embodiment.
5A to 5E are diagrams for explaining a process in which an electronic device manages a work schedule, according to an embodiment.
FIGS. 6A to 6C are diagrams for explaining a process by which an electronic device manages a work schedule, according to an embodiment.
FIGS. 7A and 7B are diagrams for explaining a process by which an electronic device manages a work schedule, according to an embodiment.
8A to 8B show an example of one or more codes included in code for a schedule task.
Figure 9 shows an example of a notification provided to a user when a task fails to be performed.
Figure 10 shows a flowchart of a method for managing order information for an electronic device according to an embodiment.
Figure 11 shows a block diagram of an electronic device according to an embodiment.

The terms used in the embodiments are general terms that are currently widely used as much as possible while considering the functions in the present disclosure, but this may vary depending on the intention or precedent of a person working in the art, the emergence of new technology, etc. In addition, in certain cases, there are terms arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the relevant description. Therefore, the terms used in this disclosure should be defined based on the meaning of the term and the overall content of this disclosure, rather than simply the name of the term.

When it is said that a part "includes" a certain element throughout the specification, this means that, unless specifically stated to the contrary, it does not exclude other elements but may further include other elements.

The expression “at least one of a, b, and c” used throughout the specification means ‘a alone’, ‘b alone’, ‘c alone’, ‘a and b’, ‘a and c’, ‘b and c ', or 'all of a, b, and c'.

The “terminal” mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal through a network. Here, the computer includes, for example, a laptop, desktop, laptop, etc. equipped with a web browser, and the portable terminal is, for example, a wireless communication device that guarantees portability and mobility. , all types of communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), and LTE (Long Term Evolution), smartphones, tablet PCs, etc. It may include a handheld-based wireless communication device.

Below, with reference to the attached drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings.

1 shows a system according to one embodiment.

Referring to FIG. 1 , the system may include at least one of an electronic device 100, one or more user terminals 120, 140, and 160, and a network 180. Meanwhile, the system shown in FIG. 1 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 1.

The electronic device 100 is a device that configures and provides various information. The electronic device 100 may provide the configured information in the form of a web page or application screen, or may provide information in a form that can be displayed as a web page or application screen on the receiving terminal.

According to one embodiment, the electronic device 100 may perform a task at each set of times set based on code written by the user and provide a performance result. For example, the electronic device 100 identifies a code that includes information about a first task and a first set of times for performing the first task, and A first work schedule created based on information about may be provided. Thereafter, the electronic device 100 may perform the first task based on information about the first time set and provide information on the performance result of the first task.

One or more user terminals 120, 140, and 160 are terminals used by each user, and the users can access services provided by the network 180 using their respective user terminals 120, 140, and 160. You can. For example, the electronic device 100 may provide a platform or application for managing a work schedule according to code written by the user to one or more user terminals 120, 140, and 160. Users can more conveniently manage one or more work schedules and check the results of work using a platform or application installed on their respective user terminals 120, 140, and 160.

One or more user terminals 120, 140, and 160 and the electronic device 100 may communicate with each other within the network 180. The network 180 includes a local area network (LAN), a wide area network (WAN), a value added network (VAN), a mobile radio communication network, a satellite communication network, and their respective networks. It is a comprehensive data communication network that includes a combination and allows each network constituent shown in FIG. 1 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication network. Wireless communications include, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy, ZigBee, WFD (Wi-Fi Direct), UWB (ultra wideband), and infrared communication (IrDA, infrared Data Association). ), NFC (Near Field Communication), etc., but are not limited thereto.

FIG. 2 is a diagram illustrating a process by which the electronic device 100 manages a work schedule according to an embodiment.

According to one embodiment, the electronic device 100 may obtain a pull request 200 from a user terminal. For example, after the user saves the code 210 for a schedule task in a local repository, the user terminal requests to merge the saved code 210 into the master branch or original code stored in the integrated repository. You can enter . The user terminal may transmit a pull request 200 including information about the code 210 related to the stored schedule task to the electronic device 100 based on the user's input.

Meanwhile, the electronic device 100 is a device or worker terminal for merging and managing codes written by multiple users, and can receive the pull request 200 directly from the user terminal, but is a device that exists separately from the worker terminal. It can be. In this case, instead of receiving the pull request 200 directly from the user terminal, the electronic device 100 may obtain information that the user terminal has transmitted the pull request 200 to the worker terminal.

According to one embodiment, as the electronic device 100 obtains the pull request 200, it may check the code 210 related to the schedule task. For example, the electronic device 100 may check a plurality of codes included in the schedule task code 210, each of which includes information about the task and information about the time set for performing the task.

According to one embodiment, the electronic device 100 may create a schedule task 220 based on the code 210 related to the schedule task and add the generated schedule task 220 to the task list 230. . For example, the electronic device 100 may create a schedule task 220 and provide a user interface for managing a plurality of tasks including the created schedule task 220. This will be described in detail with reference to FIGS. 3A and 3B.

According to one embodiment, as the electronic device 100 obtains a user input for distributing the schedule task 220, a plurality of work schedules ( 240) can be generated. For example, the electronic device 100 may obtain a user input for selecting an icon for distributing the schedule task 220 in a user interface for managing a plurality of tasks. Thereafter, the electronic device 100 may generate a plurality of task schedules 240 based on information about the task and information about the time set included in each of the plurality of codes among the codes 210 about the schedule task. there is.

According to one embodiment, the electronic device 100 may store a plurality of generated work schedules 240 in the work schedule database 250. For example, the electronic device 100 may inject information about the plurality of work schedules 240 into the work schedule database 250 and provide a user interface for managing the plurality of work schedules 240. This will be described in detail with reference to FIGS. 4A to 7B.

According to one embodiment, the electronic device 100 may perform a task at each set cycle based on information about the cycle corresponding to each of the plurality of task schedules 240. For example, if the information about the time set includes information about the cycle, the electronic device 100 may perform a task at every set cycle using a task scheduler such as Crontab. Alternatively, the electronic device 100 may obtain a user input for changing the cycle through a user interface for managing the plurality of work schedules 240 and perform a task for each changed cycle.

According to one embodiment, the electronic device 100 may perform a task on a set date based on information about the date corresponding to each of the plurality of task schedules 240. For example, when information about a time set includes information about a date, the electronic device 100 may perform a task based on data corresponding to the set date. Alternatively, the electronic device 100 may obtain a user input for changing the date through a user interface for managing the plurality of work schedules 240 and perform a task based on data corresponding to the changed date.

According to one embodiment, the electronic device 100 may store task performance result information in the task performance result database 260. For example, the electronic device 100 may perform a task at a set cycle or perform a task based on data on a set date, and store task performance result information in the task performance result database 260 .

According to one embodiment, when performance of a task fails, the electronic device 100 may provide a notification 270 regarding the failure of task performance to at least one user. For example, the electronic device 100 may check information about at least one user who will receive a notification included in each of a plurality of codes. Thereafter, when performance of the task fails, the electronic device 100 may provide a notification 270 regarding the failure of task performance to at least one confirmed user using a tool such as VictorOps or Slack.

FIGS. 3A and 3B illustrate a user interface 300 provided by the electronic device 100 according to an embodiment.

Referring to FIGS. 3A and 3B, according to one embodiment, the electronic device 100 may provide a user interface (UI) 300 including a list of one or more tasks to the user through the user's terminal. there is

According to one embodiment, the user interface 300 may include an area for displaying and managing various information about one or more tasks. For example, the user interface 300 may include an area displaying information for identifying one or more tasks, an area displaying icons for distributing one or more tasks, or an area displaying the status of one or more tasks. there is. However, the areas shown in FIGS. 3A and 3B are only an example and may be added, changed, or omitted based on user input.

According to one embodiment, the user interface 300 may include an area 320 for selecting whether to display the status of each of one or more tasks. For example, referring to FIG. 3B, when the user selects the icon corresponding to the schedule task 310 displayed in the area 320, the electronic device 100 compiles the code for the schedule task 310 and then distributes it. Information that this has been done can be displayed in area 325.

According to one embodiment, the user interface 300 may include an area 330 for selecting one or more tasks. For example, the user can manage tasks more conveniently by selecting a check box corresponding to each of one or more tasks included in the area 330.

According to one embodiment, the user interface 300 may include an area 335 that displays information for identifying one or more tasks. For example, 798 may be displayed in the area 335 as information for identifying the schedule task 310.

According to one embodiment, the user interface 300 may include an area 340 that displays the names of one or more tasks. For example, ESP_QA_Platform_scheduler may be displayed as the name of the schedule task 310 in the area 340.

According to one embodiment, the user interface 300 may include an area 345 that displays information about a branch into which code corresponding to each of one or more tasks is merged. For example, master may be displayed in area 345, indicating that code corresponding to schedule task 310 has been merged into the master branch. Additionally, the user is within area 345 ?? By selecting the icon, you can change the branch where the code corresponding to each of one or more tasks is merged.

According to one embodiment, the user interface 300 may include an area 350 for distributing one or more tasks. For example, a Start icon may be displayed in area 350 as an icon for distributing one or more tasks. When the user selects the Start icon corresponding to the schedule task 310, the electronic device 100 may distribute the code corresponding to the schedule task 310.

According to one embodiment, the user interface 300 may include an area 355 that displays the status of one or more tasks. For example, the area 355 may display Passed indicating that the code for the schedule task 310 has been compiled and then distributed.

According to one embodiment, the user interface 300 may include an area 360 that displays information about a server corresponding to each of one or more tasks. For example, service up may be displayed in area 360, indicating that the server corresponding to the schedule task 310 is operating.

According to one embodiment, the user interface 300 may include an area 365 that displays a Post Office Protocol (POP) IP corresponding to one or more tasks. For example, the fourth Pop IP may be displayed in the area 365 as the Pop IP corresponding to the schedule task 310.

According to one embodiment, the user interface 300 may include an area 370 that displays a Host IP corresponding to one or more tasks. For example, the fourth Host IP may be displayed in the area 370 as the Host IP corresponding to the schedule task 310.

According to one embodiment, the user interface 300 may include an area 375 that displays information about at least one user authorized to change settings of one or more tasks. For example, a third user may be displayed in the area 375 as at least one user authorized to change the settings of the schedule task 310.

According to one embodiment, the user interface 300 includes an area 380 that displays information about the coverage of each of one or more tasks, and an icon for checking information about the 7x24 service of each of the one or more tasks. It may include a display area 385 or an area 390 that displays an icon for confirming additional information about each of one or more tasks.

According to one embodiment, the user interface 300 may include an area 395 for searching for a specific task. For example, when the user inputs the name of a task to be searched or an IP corresponding to the task into the area 395, the electronic device 100 may provide a task corresponding to the input search word.

Meanwhile, the number and location of the above-described areas, expressions displayed in the areas, types of user interface components, and specific examples of setting information included in the setting information sets are only examples, and the present disclosure includes examples different from those described above. It is obvious to those skilled in the art that this disclosure can be implemented.

FIGS. 4A to 4C illustrate a user interface 400 provided by the electronic device 100 according to an embodiment.

Referring to FIGS. 4A to 4C , the electronic device 100 may provide a user interface 400 including a list of one or more work schedules to the user through the user's terminal, according to an embodiment. For example, the user can change parameters related to the work schedule or trigger execution of the work schedule by selecting various icons corresponding to the work schedule. Alternatively, the user can stop the execution of the task schedule or check the results of the task by selecting various icons corresponding to the task schedule.

According to one embodiment, the user interface 400 may include an area for displaying and managing various information about one or more work schedules. For example, the user interface 400 may include an area for displaying information for identifying one or more work schedules, an area for displaying icons for triggering performance of one or more work schedules, or an area for displaying the status of one or more work schedules. It may include areas, etc. However, the areas shown in FIGS. 4A to 4C are only an example and may be added, changed, or omitted based on user input.

According to one embodiment, the user interface 400 may include an area 420 for selecting whether to display the performance results of a task corresponding to each of one or more task schedules. For example, referring to FIG. 4B , when the user selects the icon corresponding to the first task schedule 402 displayed in the area 420, the electronic device 100 selects the task corresponding to the first task schedule 402. Among the performance results, the most recently performed performance result can be displayed in area 425.

According to one embodiment, the user interface 400 may include an area 430 that displays an index of one or more work schedules. For example, the electronic device 100 displays one or more work schedules based on the order in which the one or more work schedules are created or the order in which the code corresponding to each of the one or more work schedules in the code for the schedule task is written, etc. An index may be displayed in the area 430 according to the order in which one or more work schedules are displayed.

According to one embodiment, the user interface 400 may include an area 435 for controlling and managing one or more work schedules. For example, a play icon, a stop icon, and a note icon may be displayed in the area 435 as icons for controlling and managing each of one or more work schedules. The user can change information about the time set for performing a task corresponding to each of the one or more task schedules by selecting a play icon, a stop icon, or a note icon corresponding to each of the one or more task schedules. This will be described in detail with reference to FIGS. 5A to 6C.

According to one embodiment, the user interface 400 may include an area 440 that displays the status of one or more work schedules. For example, a Running icon may be displayed in the area 440 indicating that a task corresponding to the fourth task schedule 408 is currently being performed. Alternatively, an Available icon may be displayed in the area 440 to indicate that the task corresponding to the second task schedule 404 can be performed.

According to one embodiment, the user interface 400 may include an area 445 that displays the name of a task corresponding to one or more task schedules. For example, in the area 445, sync_incomplete_ab may be displayed as the name of the task corresponding to the third task schedule 406, and update_ects_bts_stauts may be displayed as the name of the task corresponding to the fifth task schedule 410. You can. At this time, the name of the task corresponding to the work schedule may be determined based on the code for the schedule task written by the user, the task or function corresponding to the task schedule, etc., but is not limited to the above.

According to one embodiment, the user interface 400 may include an area 450 that displays information about a cycle for performing a task corresponding to each of one or more task schedules. For example, in the area 450, 1*/1** mon-fri may be displayed, indicating that the cycle is set so that the task corresponding to the second task schedule 404 is performed at 1 minute every hour from Monday to Friday. You can. Alternatively, */10**** may be displayed in the area 450, indicating that the cycle is set so that the task corresponding to the fifth task schedule 410 is performed every 10 minutes.

According to one embodiment, the user interface 400 may include an area 455 that displays an icon for stopping repeated performance of a task corresponding to each of one or more task schedules. More specifically, the electronic device 100 may display a toggle switch in the area 455 as a user interface component for stopping performance of a task corresponding to each of one or more task schedules.

For example, when the user activates the toggle switch corresponding to the first task schedule 402, repeated performance of the task corresponding to the first task schedule 402 may continue. Alternatively, when the user deactivates the toggle switch corresponding to the third task schedule 406, repeated performance of the task corresponding to the third task schedule 406 may be stopped or omitted.

According to one embodiment, the user interface 400 may include an area 460 that displays information about the port of the server on which a task corresponding to each of one or more task schedules will be performed. For example, 18021 may be displayed in the area 460 as the port number of the server on which the task corresponding to the first task schedule 402 will be performed. Alternatively, 18021 and 23004 may be displayed in the area 460 as port numbers of servers on which tasks corresponding to the second task schedule 404 will be performed.

According to one embodiment, the user interface 400 may include an area 465 that displays information about a user who changed a setting parameter for each of one or more work schedules. For example, the first user may be displayed in the area 465 as a user who changed the setting parameters related to the first work schedule 402. Alternatively, a fourth user may be displayed in the area 465 as a user who changed the setting parameters for the fifth work schedule 410.

According to one embodiment, the user interface 400 may include an area 470 that displays information about the last time a task corresponding to each of one or more task schedules was successfully performed. For example, the area 470 may display 2022-12-21T 09:01:09 as the last time the task corresponding to the second task schedule 404 was successfully performed. Alternatively, the area 470 may display 2022-08-19T 03:56:42 as the last time the task corresponding to the fourth task schedule 408 was successfully performed.

According to one embodiment, the user interface 400 may include an area 475 that displays information about the last time performance of a task corresponding to each of one or more task schedules failed. For example, 2022-11-07T 17:25:45 may be displayed in the area 475 as the last time when performance of the task corresponding to the third task schedule 406 failed. Alternatively, if the performance of the task corresponding to the fourth task schedule 408 has never failed, no information may be displayed in the area corresponding to the fourth task schedule 408 in the area 475.

According to one embodiment, the user interface 400 may include an area 480 that displays an icon for checking the performance result of a task corresponding to each of one or more task schedules. For example, when the user selects the view icon corresponding to the fifth task schedule 410 in the area 480, the electronic device 100 provides information on the performance results of the task corresponding to the fifth task schedule 410. can do. This will be explained with reference to FIGS. 7A to 7B.

According to one embodiment, the user interface 400 may include an area 485 for searching for a specific task. For example, when the user inputs the name of a job to be searched into the area 485, the electronic device 100 may provide a job schedule corresponding to the entered search term. Referring to FIG. 4C, when the user inputs Sync in the area 485, the electronic device 100 provides information about the second task schedule 404 and the third task schedule 406 corresponding to Sync. You can.

Meanwhile, the number and location of the above-mentioned areas, expressions displayed in the areas, types of user interface components, and specific examples of setting information included in the setting information sets are only examples, and the present disclosure includes examples different from those described above. It is obvious to those skilled in the art that this disclosure can be implemented.

FIGS. 5A to 5E are diagrams for explaining a process by which the electronic device 100 manages a work schedule, according to an embodiment. Content that overlaps with FIGS. 4A to 4C will be briefly described or omitted.

Referring to FIGS. 5A to 5E , the electronic device 100 may provide a user interface 500 including a list of one or more work schedules to the user through the user's terminal, according to an embodiment.

According to one embodiment, the user interface 500 may include an area 520 that displays information about a cycle for performing a task corresponding to each of one or more task schedules. For example, 0*/23*** may be displayed in the area 520, indicating that the cycle is set so that the task corresponding to the first task schedule 510 is performed at 0 minutes every 23 hours.

According to one embodiment, the user interface 500 may include an area 530 for controlling and managing one or more work schedules. For example, a note icon for setting a task cycle corresponding to each of one or more task schedules may be displayed in the area 530.

According to one embodiment, the electronic device 100 may obtain a user input for selecting a note icon and display a screen for setting a task cycle corresponding to the selected note icon. For example, referring to FIG. 5B , when the user selects the note icon corresponding to the first task schedule 510 in the area 530, the electronic device 100 selects the task corresponding to the first task schedule 510. A pop-up window 540 may be displayed for setting information about the cycle for performing.

According to one embodiment, the pop-up window 540 may include an area 550 for setting the cycle of the selected work schedule in minutes, hours, days, months, and weeks. At this time, information indicating the cycle in which the task corresponding to the selected task schedule is currently being performed may be displayed in the area 550. For example, referring to FIG. 5B , 0*/23*** indicating the cycle in which the task corresponding to the first task schedule 510 is currently being performed may be displayed in the area 550.

According to one embodiment, the electronic device 100 may obtain a user input that changes the cycle of the selected work schedule. For example, referring to FIG. 5C, the electronic device 100 changes the cycle for performing the task corresponding to the first task schedule 510 from 0*/23*** to 0*/12***. You can obtain user input.

According to one embodiment, the electronic device 100 may provide information about the expected performance time of a task corresponding to the selected task schedule based on changed information about the cycle. For example, referring to FIG. 5D, the electronic device 100 obtains a user input for selecting the validate icon 560, and the task corresponding to the first task schedule 510 is scheduled for Tuesday 12 January 16, 2023. Information indicating that the operation is scheduled to be performed at 0:00 on Wednesday, January 17, 2023 and at 12:00 on Wednesday, January 17, 2023 may be displayed in area 570. However, Figure 5d shows that the electronic device 100 displays information on the three expected times at which the electronic device 100 will perform the task in the area 570, but this is only an example, and the information displayed in the area 570 The number of expected times may be different from what was described above.

According to one embodiment, the electronic device 100 may perform a task corresponding to the selected work schedule at each changed cycle, based on changed information about the cycle. For example, after obtaining a user input for selecting the Save icon 590, the electronic device 100 may store changed information regarding the cycle of the first work schedule 510. Thereafter, the electronic device 100 may perform the task corresponding to the first task schedule 510 at 0 minutes every 12 hours.

According to one embodiment, the pop-up window 540 may include an area 580 for setting the expiration date of the selected work schedule. For example, referring to FIG. 5E, when the user selects the downward icon in area 580 or positions the cursor within area 580, the electronic device 100 displays a date selector for setting the expiration date of the work schedule. (date picker) 585 can be provided. Thereafter, the electronic device 100 may obtain a user's input for selecting a specific date and display the selected date in area 580.

According to one embodiment, the electronic device 100 may perform a task corresponding to a work schedule selected based on changed information about the cycle and information about the expiration date for each changed cycle until the expiration date. For example, after obtaining a user input for selecting the Save icon 590, the electronic device 100 may store changed information about the cycle of the first work schedule 510 and information about the expiration date. Thereafter, the electronic device 100 may perform the task corresponding to the first task schedule 510 at 0 minutes every 12 hours until the expiration date.

Meanwhile, the number and location of the above-described areas, expressions displayed in the areas, types of user interface components, and specific examples of setting information included in the setting information sets are only examples, and the present disclosure includes examples different from those described above. It is obvious to those skilled in the art that this disclosure can be implemented.

FIGS. 6A to 6C are diagrams for explaining a process by which the electronic device 100 manages a work schedule, according to an embodiment. Content that overlaps with FIGS. 4A to 4C will be briefly described or omitted.

Referring to FIGS. 6A to 6C , the electronic device 100 may provide a user interface 600 including a list of one or more work schedules to the user through the user's terminal, according to an embodiment.

According to one embodiment, the user interface 600 may include an area 630 that displays the status of one or more work schedules. For example, an Available icon indicating that tasks corresponding to the first task schedule 610 and the second task schedule 620 can be performed may be displayed in the area 630.

According to one embodiment, the user interface 600 may include an area 640 for controlling and managing one or more work schedules. For example, the area 640 may display a play icon to trigger performance of a task corresponding to each of one or more task schedules or a stop icon to stop performance of a task corresponding to each of one or more task schedules. there is.

According to one embodiment, the electronic device 100 may obtain a user input for selecting a play icon and perform the task based on whether a date for performing the task corresponding to the selected play icon is set.

For example, when a date for performing the first task corresponding to the first work schedule 610 is set, the electronic device 100 receives a user input for selecting a play icon corresponding to the first work schedule 610. As acquired, the first task can be performed based on data corresponding to the set date. Thereafter, referring to FIG. 6B, the electronic device 100 displays a Running icon in the area 630 indicating that a job corresponding to the first work schedule 610 is being performed, and the first work schedule in the area 640 The play icon corresponding to (610) can be changed to a stop icon.

Alternatively, when the date for performing the second task corresponding to the second work schedule 620 is not set, the electronic device 100 receives a user input for selecting the play icon corresponding to the second work schedule 620. As it is acquired, a screen for setting the date to perform the second task can be displayed. Referring to FIG. 6C, the electronic device 100 may display a pop-up window 650 including an area 660 for inputting a date to perform the second task. Thereafter, the electronic device 100 may obtain an input for writing a date in the area 660 and an input for selecting the Save icon 670, and may perform a second task based on the data of the input date.

At this time, setting a date to perform a task may mean that the code corresponding to the task includes a specific date as a field value corresponding to the date variable. Additionally, not having a date set to perform a task may mean that the code corresponding to the task includes None or a null value as a field value corresponding to the date variable. However, this is only an example and is not limited to the above.

Meanwhile, the number and location of the above-described areas, expressions displayed in the areas, types of user interface components, and specific examples of setting information included in the setting information sets are only examples, and the present disclosure includes examples different from those described above. It is obvious to those skilled in the art that this disclosure can be implemented.

FIGS. 7A and 7B are diagrams for explaining a process by which the electronic device 100 manages a work schedule according to an embodiment. Content that overlaps with FIGS. 4A to 4C will be briefly described or omitted.

Referring to FIGS. 7A and 7B , the electronic device 100 may provide a user interface 700 including a list of one or more work schedules to the user through the user's terminal, according to an embodiment.

According to one embodiment, the user interface 700 may include an area 740 that displays an icon for checking the performance result of a task corresponding to each of one or more task schedules. For example, referring to FIG. 7B , as the electronic device 100 obtains a user input for selecting a view icon corresponding to the first task schedule 720, the electronic device 100 selects a view icon corresponding to the first task schedule 720. A pop-up window 760 containing performance result information may be displayed.

According to one embodiment, the electronic device 100 may provide a result of performing a task corresponding to the selected task schedule. For example, referring to FIG. 7B , the electronic device 100 may display a pop-up window 760 containing the performance results of the task corresponding to the first task schedule 720 for the past 10 days.

According to one embodiment, the electronic device 100 may perform a task based on data corresponding to at least one date on which task performance failed. For example, referring to FIG. 7B, the electronic device 100 obtains a user input for selecting the Re-execute icon 780 and, based on the performance result information of the first task, determines that the performance of the first task has failed. At least one date can be identified. Thereafter, the electronic device 100 may check data corresponding to at least one date and perform the first task based on the data corresponding to at least one date.

Meanwhile, the number and location of the above-described areas, expressions displayed in the areas, types of user interface components, and specific examples of setting information included in the setting information sets are only examples, and the present disclosure includes examples different from those described above. It is obvious to those skilled in the art that this disclosure can be implemented.

8A to 8B show an example of one or more codes 800 and 850 included in code for a schedule task.

According to one embodiment, one or more codes 800 and 850 included in the code for the schedule task may include information about the time set for performing the task. For example, referring to Figure 8A, code 800 may include "cron='1*/1*** mon-fri'" 810, as information about the cycle for performing the task. , information about the expiration date may include “expire date=2023-03-22” (815). Or, referring to FIG. 8B, the code 850 may include "cron='023***'" 860 as information about the cycle for performing the task, and the code 850 may include "cron='023***'" 860 on the date to perform the task. As information about this, it may include “date=None” (865).

According to one embodiment, one or more codes 800 and 850 included in the code for the schedule task may include information about the port corresponding to the server that will perform the task. For example, referring to FIG. 8A, the code 800 may include "port='18001'" 820 as information about the port corresponding to the server to perform the task. Alternatively, referring to FIG. 8B, the code 850 may include "port='18001'" 870 as information about the port corresponding to the server to perform the task.

According to one embodiment, one or more codes 800 and 850 included in the code for the schedule task may include information about at least one user to whom a notification is to be provided. For example, referring to FIG. 8A , code 800 may include “notifier: first user” 830 as information about at least one user to be notified when a task is not performed. Alternatively, referring to FIG. 8B, the code 850 may include “notifier: second user” 880 as information about at least one user who will provide a notification when a task fails to be performed.

According to one embodiment, one or more codes 800 and 850 included in the code for the schedule task may include information about the task. For example, referring to FIG. 8A, code 800 may include information 840 regarding specific contents for performing the sync_qa_bts_tasks task. Alternatively, referring to FIG. 8B, the code 850 may include information 890 regarding specific contents for performing the sync_teatrail_qa_data task.

Meanwhile, specific examples of the user to provide the above-described notification, the cycle to perform the task, the name of the task, or the port number corresponding to the server to perform the task are only an example, and the present disclosure is an example different from the above. It is obvious to those skilled in the art that this disclosure can be implemented.

Figure 9 shows an example of a notification 900 provided to a user when a task fails to be performed.

According to one embodiment, when the electronic device 100 fails to perform a task, it may provide a notification 900 regarding the failure of the task to at least one user. For example, referring to FIG. 9, when performance of a task fails, the electronic device 100 provides information about at least one user to provide a notification, information about the time when performance of the task failed, or the name of the task. The notification 900 may be provided to at least one user.

Meanwhile, the specific examples regarding the user to provide the above-mentioned notification, the time at which task performance was failed, or the name of the task are merely examples, and the present disclosure may be implemented with examples different from those described above. It is self-evident to those with ordinary knowledge in the relevant technical field.

Figure 10 shows a flowchart of a method for managing order information for an electronic device according to an embodiment. The foregoing description may apply to overlapping content.

In step S1000, the electronic device may check a code including information about the first task and information about the first time set for performing the first task.

According to one embodiment, the information about the first time set may include information about the first cycle, and the electronic device can perform the first task every first cycle.

According to one embodiment, the information about the first time set may further include information about an expiration date, and the electronic device may perform the first task every first cycle until the expiration date.

According to one embodiment, the code may further include information about at least one user to whom notifications are to be provided. Additionally, when performance of the first task fails, the electronic device may provide a notification regarding the failure of the first task to at least one user.

According to one embodiment, the code may further include information about at least one port. Additionally, the electronic device may perform the first task on a server corresponding to at least one port.

In step S1020, the electronic device may provide a first task schedule generated based on information about the first task and information about the first time set.

According to one embodiment, the electronic device may provide a list of a plurality of work schedules including the first work schedule.

According to one embodiment, the electronic device obtains a user input for changing information about the second cycle of a second work schedule among a list of a plurality of work schedules, and based on the changed information about the second cycle, performs a second task. The second task corresponding to the schedule may be performed every second changed cycle.

According to one embodiment, the electronic device may obtain a user input to stop performing a third task corresponding to a third task schedule among a list of a plurality of task schedules, and may omit repeated performance of the third task.

According to one embodiment, the electronic device may provide information about the status of a fourth work schedule among a list of a plurality of work schedules. At this time, the state of the fourth task schedule may include at least one of a performable state and a performing state.

In step S1040, the electronic device may perform the first task based on information about the first time set.

According to one embodiment, the information about the first time set may further include information about the first date for performing the first task. Additionally, the electronic device may obtain a user input for performing the first task, check data corresponding to the first date, and perform the first task based on the data corresponding to the first date.

According to one embodiment, if the first date is not set, the electronic device obtains user input regarding a second date for performing the first task, verifies data corresponding to the second date, and determines the second date. The first task may be performed based on data corresponding to .

In step S1060, the electronic device may provide information on the performance result of the first task.

According to one embodiment, the electronic device may initiate a work schedule management method as it obtains a pull request from the user terminal.

According to one embodiment, based on information on the performance of the first task, the electronic device determines at least one date on which performance of the first task failed, verifies data corresponding to the at least one date, and determines at least one date on which the first task failed. The first task may be performed based on data corresponding to the date.

FIG. 11 shows a block diagram of an electronic device 100 according to an embodiment.

According to one embodiment, the electronic device 100 may include a communication device 1120, a memory 1140, and a controller 1160. The electronic device 100 shown in FIG. 11 shows only components related to this embodiment. Accordingly, those skilled in the art can understand that other general-purpose components may be included in addition to the components shown in FIG. 11. Since the electronic device 100 may include content related to the above-described server, description of overlapping content will be omitted. In an embodiment, the communication unit may include one or more transceivers. Additionally, in an embodiment, the control unit may include one or more processors.

The communication unit 1120 is a device for performing wired/wireless communication and can communicate with external electronic devices. The external electronic device may be a terminal or server. In addition, communication technologies used by the communication unit 1120 include Global System for Mobile communication (GSM), Code Division Multi Access (CDMA), Long Term Evolution (LTE), 5G, Wireless LAN (WLAN), and Wireless-Fidelity (Wi-Fi). ), Bluetooth??, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), etc.

The control unit 1160 can control the overall operation of the electronic device 100 and process data and signals. The control unit 1160 may be composed of at least one hardware unit. Additionally, the control unit 1160 may operate by one or more software modules generated by executing program codes stored in the memory 1140. The control unit 1160 may include a processor and a memory, and the processor may execute program codes stored in the memory to control the overall operation of the electronic device 100 and process data and signals. Additionally, in an embodiment, the control unit 1160 may include at least one processor.

The control unit 1160 identifies a code containing information about the first task and information about the first set of times for performing the first task, and based on the information about the first task and the information about the first set of times. The generated first work schedule can be provided, the first task can be performed based on information about the first time set, and information on the performance of the first task can be provided.

The electronic device according to the above-described embodiments includes a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, keys, buttons, etc. It may include the same user interface device, etc. Methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program instructions executable on the processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). ), DVD (Digital Versatile Disc), etc. The computer-readable recording medium is distributed among computer systems connected to a network, so that computer-readable code can be stored and executed in a distributed manner. The media may be readable by a computer, stored in memory, and executed by a processor.

This embodiment can be represented by functional block configurations and various processing steps. These functional blocks may be implemented in various numbers of hardware or/and software configurations that execute specific functions. For example, embodiments include integrated circuit configurations such as memory, processing, logic, look-up tables, etc. that can execute various functions under the control of one or more microprocessors or other control devices. can be hired. Similar to how the components can be implemented as software programming or software elements, this embodiment includes various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, Java ( It can be implemented in a programming or scripting language such as Java), assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors. Additionally, this embodiment may employ conventional technologies for electronic environment settings, signal processing, and/or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations. The term may include the meaning of a series of software routines in connection with a processor, etc.

The above-described embodiments are merely examples and other embodiments may be implemented within the scope of the claims described below.

Claims (16)

A method of managing a work schedule for an electronic device, comprising:
Upon obtaining a pull request from a user terminal, a first task including information on a first job corresponding to the pull request and a first set of time information for performing the first job Checking the code for;
generating a first task based on the code for the first task;
providing a first user interface for managing a plurality of tasks to which the first task is added;
confirming a user input for distributing the first task among the plurality of tasks through the first user interface;
generating a first task schedule based on the information about the first task and the first set of time information;
Storing the first work schedule in a database and providing a second user interface for managing a plurality of work schedules to which the first work schedule is added; Based on the first time information set, the first work schedule performing steps; and
Providing performance result information of the first task through the second user interface,
The first user interface includes an area that displays information about a branch into which code corresponding to each of the plurality of tasks is merged, and an area that displays information about whether each of the plurality of tasks has been distributed,
The second user interface includes an area for displaying information about the cycle for performing a task corresponding to each of the plurality of work schedules, and an icon for stopping repeated performance of the task corresponding to each of the plurality of work schedules. A method of managing a work schedule, including an area to display.
According to claim 1,
The first set of time information includes information about a first period,
The performing the first task includes performing the first task every first cycle.
delete The method of claim 1, wherein the work schedule management method includes:
Obtaining a user input for changing information about a second cycle of a second work schedule among the plurality of work schedules through the second user interface; and
Based on the changed information about the second cycle, the work schedule management method further includes performing a second task corresponding to the second work schedule every changed second cycle.
The method of claim 4, wherein the work schedule management method includes:
A work schedule management method further comprising providing information about an expected execution time of the second task based on the changed information about the second cycle.
According to claim 1,
The first set of time information further includes information regarding a first date for performing the first task,
The work schedule management method is,
Obtaining user input for performing the first task;
confirming data corresponding to the first date; and
Work schedule management method further comprising performing the first task based on data corresponding to the first date.
The method of claim 6, wherein performing the first task on the first date comprises:
If the first date is not set, obtaining user input regarding a second date for performing the first task;
confirming data corresponding to the second date; and
A work schedule management method comprising performing the first task based on data corresponding to the second date.
According to claim 1,
The code further includes information about at least one user for whom notification is to be provided,
The work schedule management method further includes, when performance of the first task fails, providing a notification regarding failure of performance of the first task to the at least one user.
According to clause 2,
The code further includes information about at least one port,
The performing the first task every first cycle includes performing the first task on a server corresponding to the at least one port.
The method of claim 1, wherein the work schedule management method includes:
Obtaining a user input to stop performance of a third task corresponding to a third task schedule among the plurality of task schedules through the second user interface; and
A work schedule management method further comprising omitting repeated performance of the third task.
According to claim 1,
The second user interface further includes an area that displays information about the status of each of the plurality of work schedules,
A work schedule management method wherein the state of each of the plurality of work schedules includes at least one of a performable state and a performing state.
delete The method of claim 1, wherein the work schedule management method includes:
Based on performance result information of the first task, confirming at least one date on which performance of the first task failed;
confirming data corresponding to the at least one date; and
A work schedule management method further comprising performing the first task based on data corresponding to the at least one date.
According to clause 2,
The first time information set further includes information regarding an expiration date,
The performing the first task includes performing the first task every first cycle until the expiration date.
A computer-readable recording medium that records a program for executing the method of claim 1 on a computer.
As an electronic device,
Ministry of Communications;
Memory; and
It includes a controller, wherein the controller includes:
Upon obtaining a pull request from a user terminal, a code for a first task, including information on a first task and a first set of time information for performing the first task, corresponding to the pull request Check and
Create a first task based on the code for the first task,
Providing a first user interface for managing a plurality of tasks to which the first task has been added,
Through the first user interface, confirm a user input for distributing the first task among the plurality of tasks,
Generate a first task schedule based on the information about the first task and the first set of time information,
Storing the first work schedule in a database and providing a second user interface for managing a plurality of work schedules to which the first work schedule is added,
Based on the first set of time information, perform the first task,
Providing performance result information of the first task through the second user interface,
The first user interface includes an area that displays information about a branch into which code corresponding to each of the plurality of tasks is merged, and an area that displays information about whether each of the plurality of tasks has been distributed,
The second user interface includes an area for displaying information about the cycle for performing a task corresponding to each of the plurality of work schedules, and an icon for stopping repeated performance of the task corresponding to each of the plurality of work schedules. An electronic device comprising an area for displaying.

Images