U.S. patent application number 16/513792 was filed with the patent office on 2019-11-07 for schedule management system, non-transitory computer readable medium, and schedule management method.
This patent application is currently assigned to FUJI XEROX CO., LTD.. The applicant listed for this patent is FUJI XEROX CO., LTD.. Invention is credited to Kengo TOKUCHI, Shunichi YASUDA.
Application Number | 20190340582 16/513792 |
Document ID | / |
Family ID | 57325475 |
Filed Date | 2019-11-07 |
![](/patent/app/20190340582/US20190340582A1-20191107-D00000.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00001.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00002.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00003.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00004.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00005.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00006.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00007.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00008.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00009.png)
![](/patent/app/20190340582/US20190340582A1-20191107-D00010.png)
United States Patent
Application |
20190340582 |
Kind Code |
A1 |
YASUDA; Shunichi ; et
al. |
November 7, 2019 |
SCHEDULE MANAGEMENT SYSTEM, NON-TRANSITORY COMPUTER READABLE
MEDIUM, AND SCHEDULE MANAGEMENT METHOD
Abstract
A schedule management apparatus includes a schedule information
receiving unit that receives schedule information generated by one
or more client devices from each of the client devices, the
schedule information including a description of an event, a
location of the event, and a date/time of the event. On the basis
of the schedule information received by the schedule information
receiving unit, information is displayed on each of the client
devices about an event to be newly added that matches the schedule
information without overlapping with a date/time of each of events
scheduled before and after the event, the information representing
at least one of a duration of the event, a location of the event,
and a route to the event.
Inventors: |
YASUDA; Shunichi; (Kanagawa,
JP) ; TOKUCHI; Kengo; (Kanagawa, JP) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
FUJI XEROX CO., LTD. |
Tokyo |
|
JP |
|
|
Assignee: |
FUJI XEROX CO., LTD.
Tokyo
JP
|
Family ID: |
57325475 |
Appl. No.: |
16/513792 |
Filed: |
July 17, 2019 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14919222 |
Oct 21, 2015 |
10423930 |
|
|
16513792 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06Q 10/1095
20130101 |
International
Class: |
G06Q 10/10 20060101
G06Q010/10 |
Foreign Application Data
Date |
Code |
Application Number |
May 21, 2015 |
JP |
2015-103409 |
Claims
1. A schedule management apparatus comprising; a schedule
information receiving unit that receives schedule information
generated by one or more client devices from each of clients, the
schedule information including a desired information of an event, a
desired location of the event, and a desired date and/or time of
the event; an extraction unit that extracts a group of clients with
no overlap of the desired location and the desired date and/or time
of the event, on the bases of the desired information from among
the clients that are event member candidates; a setting unit that
performs mediation between the extracted group of clients and
finally sets the event; a distribution unit that distributes
information about an event date and/or time and an event location
to the extracted clients; and an acquire unit that acquires
information about the event when the user actually participates in
the event that has been automatically set.
2. The schedule management apparatus according to claim 1, wherein
the distribution unit distributes the information location
including an advertisement image and charge.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation application of U.S.
patent application Ser. No. 14/919,222, filed Oct. 21, 2015, which
is based on and claims priority under 35 USC 119 from Japanese
Patent Application No. 2015-103409 filed May 21, 2015. The
disclosures of each of the above are hereby incorporated by
reference in their entireties.
BACKGROUND
Technical Field
[0002] The present invention relates to a schedule management
system, a non-transitory computer readable medium, and a schedule
management method.
SUMMARY
[0003] According to an aspect of the invention, there is provided a
schedule management apparatus including a schedule information
receiving unit that receives schedule information generated by one
or more client devices from each of the client devices, the
schedule information including a description of an event, a
location of the event, and a date/time of the event, in which on
the basis of the schedule information received by the schedule
information receiving unit, information is displayed on each of the
client devices about an event to be newly added that matches the
schedule information without overlapping with a date/time of each
of events scheduled before and after the event, the information
representing at least one of a duration of the event, a location of
the event, and a route to the event.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Exemplary embodiments of the present invention are described
in detail based on the following figures, wherein:
[0005] FIG. 1 illustrates a general configuration of a schedule
management system;
[0006] FIG. 2A is a block diagram illustrating a hardware
configuration of a client device;
[0007] FIG. 2B is a block diagram illustrating a hardware
configuration of a schedule management server apparatus;
[0008] FIG. 3 illustrates a configuration of the functional blocks
of a client device;
[0009] FIG. 4 illustrates a configuration of the functional blocks
of a schedule management server apparatus;
[0010] FIG. 5 is a flowchart illustrating a flow of operation of a
schedule management system;
[0011] FIG. 6 illustrates a configuration of the functional blocks
of a schedule management server apparatus;
[0012] FIG. 7 is a flowchart illustrating a flow of operation of a
schedule management server apparatus;
[0013] FIG. 8 illustrates a configuration of the functional blocks
of a schedule management server apparatus;
[0014] FIG. 9 illustrates a configuration of the functional blocks
of a schedule management server apparatus; and
[0015] FIG. 10 illustrates a configuration of the functional blocks
of a schedule management system in which the function of a schedule
management server apparatus is built in a client device.
DETAILED DESCRIPTION
[0016] Although the present invention is described below by way of
its exemplary embodiments and specific examples with reference to
the figures, the present invention is not limited to these
exemplary embodiments and specific examples.
[0017] It is to be noted that in the following discussion using the
figures, the figures are schematic only, and the relative
proportions of various dimensions may differ from the actuality.
Further, for the ease of understanding, components other than those
necessary for explanation are omitted as appropriate.
[0018] First Exemplary Embodiment
[0019] (1) General Configuration of Schedule Management System
[0020] FIG. 1 illustrates a general configuration of a schedule
management system 1 according to a first exemplary embodiment. FIG.
2A is a block diagram illustrating a hardware configuration of a
client device 100, and FIG. 2B is a block diagram illustrating a
hardware configuration of a schedule management server apparatus
200.
[0021] Hereinafter, a general configuration of the schedule
management system 1 is described with reference to the figures.
[0022] As illustrated in FIG. 1, the schedule management system 1
includes multiple client devices 100, the schedule management
server apparatus 200, a property search server 300, an address
search server 400, and a station-to-station search server 500. The
client devices 100, the schedule management server apparatus 200,
the property search server 300, the address search server 400, and
the station-to-station search server 500 are connected to a network
600 such as the Internet or wide area network (WAN) so as to be
able to communicate with each other.
[0023] As illustrated in FIG. 2A, the client device 100 has
components such as a central processing unit (CPU) 101, a random
access memory (RAM) 102, a read only memory (ROM) 103, an operation
input unit 104, a communication unit 105, and a display 106. The
client device 100 may be, for example, a portable electronic device
such as a cellular phone, a PDA terminal, a smart phone, or a
notebook PC, or a stationary electronic device such as a desktop
PC.
[0024] As illustrated in FIG. 2B, the schedule management server
apparatus 200 has components such as a CPU 201, a RAM 202, a ROM
203, an operation input unit 204, a communication unit 205, and a
hard disk drive (HDD) 206. Although the schedule management server
apparatus 200 is a stationary PC or the like, the schedule
management server apparatus 200 may be another electronic
device.
[0025] (2) Functional Configuration of Schedule Management
System
[0026] FIG. 3 illustrates a configuration of the functional blocks
of the client device 100. FIG. 4 illustrates a configuration of the
functional blocks of the schedule management server apparatus
200.
[0027] Hereinafter, a functional configuration of the schedule
management system 1 is described with reference to the figures.
[0028] (2.1) Client Device
[0029] As illustrated in FIG. 3, each of the client devices 100 has
the following functional blocks: a desired meeting information
transmitting unit 110 that transmits first schedule information
including the location, date/time, and time period of a meeting
that is an example of an event, a set meeting information receiving
unit 120, and a meeting participation history management unit
130.
[0030] Each of the client devices 100 has a schedule management
tool 140 (to be referred to as scheduler 140 hereinafter) as an
application. The scheduler 140 manages schedule information about
the user of the client device 100. The scheduler 140 stores
information including schedule information such as the date/time
and location of an event scheduled for the user of the client
device 100 and positional information of the user's home or
workplace.
[0031] When the desired meeting information transmitting unit 110
receives an input of desired meeting information including a
desired meeting date/time, a desired meeting location range, and
meeting member candidates made from the user by using the operation
input unit 104 of the client device 100, the desired meeting
information transmitting unit 110 transmits the desired meeting
information to the schedule management server apparatus 200.
[0032] The set meeting information receiving unit 120 receives
information about a meeting automatically set by the schedule
management server apparatus 200 (to be referred to as set meeting
information hereinafter). This set meeting information is stored in
a such a state that allows the set meeting information to be viewed
on the scheduler 140.
[0033] The user of the client device 100 views and checks this set
meeting information via the scheduler 140 and the display 106. This
set meeting information may be received and stored as an
e-mail.
[0034] When the user actually participates in a meeting
automatically set by the schedule management server apparatus 200,
the meeting participation history management unit 130 acquires
information about the meeting (date/time, positional information of
the location, positional information of the immediately previous
scheduled activity (a departure point to the meeting), the distance
travelled from the departure point to the meeting to the hosting
place of the meeting, and members of the meeting) while using
information stored on the scheduler 140, and stores the acquired
data into a meeting history database 150.
[0035] (2.2) Schedule Management Server Apparatus
[0036] As illustrated in FIG. 4, the schedule management server
apparatus 200 has the following functional blocks: a client's
desired meeting information storing unit 210, a travel time
calculating unit 220, a client's desired meeting information
matching unit 230, a meeting setting unit 240, a set meeting
information storing unit 250, and a set meeting information
transmitting unit 260.
[0037] The client's desired meeting information storing unit 210
temporarily stores desired meeting information of each of the
client devices 100 transmitted at appropriate times from the
desired meeting information transmitting unit 110 of each of the
client devices 100.
[0038] The travel time calculating unit 220 connects to the
property search server 300, the address search server 400, and the
station-to-station search server 500, and calculates travel time
from positional information, date/time information, and time period
information within the desired meeting information of each of the
client devices 100, and station-to-station information based on
information of a departure point to the meeting.
[0039] The property search server 300 searches for an office, a
meeting room, or another such rental property from positional
information entered in the desired meeting information of each of
the client devices 100.
[0040] The address search server 400 searches for an address from
positional information entered in the desired meeting information
of each of the client devices 100.
[0041] The station-to-station search server 500 extracts the
nearest station to the departure point, the nearest station to the
destination, and the shortest travel route, on the basis of the
desired date/time information and time period information of each
of the client devices 100 and information in the address search
server 400.
[0042] The client's desired meeting information matching unit 230
extracts, on the basis of desired meeting information temporarily
stored in the client's desired meeting information storing unit
210, a group of client devices that match the desired meeting
information with no overlap of desired meeting dates/times and
desired meeting location ranges (to be referred to as matching
client device group hereinafter), from among the client devices 100
that are meeting member candidates in the desired meeting
information.
[0043] For the matching client device group extracted by the
client's desired meeting information matching unit 230, the meeting
setting unit 240 further performs mediation between the pieces of
desired meeting information of multiple client devices 100
belonging to the matching client device group to finally set the
meeting details.
[0044] The set meeting information storing unit 250 stores the
final meeting date/time and location information set by the meeting
setting unit 240 as set meeting information.
[0045] The set meeting information transmitting unit 260 transmits
the set meeting information determined for the matching client
device group to each of the client devices 100 belonging to the
matching client device group.
[0046] (3) Operation of Schedule Management System
[0047] FIG. 5 is a flowchart illustrating a flow of operation of
the schedule management system 1.
[0048] Hereinafter, operation of the schedule management system 1
according to the first exemplary embodiment is described in more
detail.
[0049] The client device 100 transmits desired meeting information
including a desired meeting date/time, a desired meeting location
range, and meeting member candidates input via the operation input
unit 104, to the schedule management server apparatus 200 from the
desired meeting information transmitting unit 110 (S101).
[0050] The schedule management server apparatus 200 receives, by
the communication unit 205, desired meeting information transmitted
from each of the client devices 100 (S102). Then, the schedule
management server apparatus 200 temporarily stores the received
desired meeting information of each of the client devices 100 in
the client's desired meeting information storing unit 210
(S103).
[0051] The schedule management server apparatus 200 transmits
positional information entered in the desired meeting information
of each of the client devices 100 to the property search server
300, and acquires office, meeting room, or other rental property
information from the property search server 300 (S104).
[0052] Further, the schedule management server apparatus 200
transmits the positional information in the desired meeting
information to the address search server 400, and acquires address
information from the address search server 400 (S105).
[0053] The schedule management server apparatus 200 transmits the
acquired address information, desired date/time information, and
time period information to the station-to-station search server
500, and acquires station-to-station information from the
station-to-station search server 500 (S106).
[0054] Then, the travel time calculating unit 220 calculates travel
time on the basis of the acquired information (S107).
[0055] Subsequently, the schedule management server apparatus 200
performs a matching process by the client's desired meeting
information matching unit 230. The matching process extracts a
matching client device group that matches a desired meeting
date/time and a desired meeting location range, from among meeting
member candidates in the desired meeting information of each of the
client devices 100 (S108).
[0056] The matching process is executed as follows. For example,
first, for a given client device 100, other client devices 100 with
the same desired meeting date are extracted. Then, from among these
extracted client devices 100, only those other client devices 100
for which the desired meeting time (time period) overlaps that of
the given client device 100 by a predetermined proportion or more
(for example, 50% or more) are extracted, and further, those other
client devices 100 for which the desired meeting location range
overlaps that of the given client device 100 by a predetermined
proportion or more (for example, 25% or more) are extracted.
[0057] Then, from the group of other client devices thus extracted,
a group of client devices 100 with no overlapping client devices
100 is extracted as a matching client device group.
[0058] Next, for the matching client device group extracted by the
client's desired meeting information matching unit 230, the meeting
setting unit 240 of the schedule management server apparatus 200
further performs mediation between the pieces of desired meeting
information of the client devices 100 belonging to the matching
client device group on the basis of the travel time and route
information calculated by the travel time calculating unit 220 to
thereby finally set the meeting details (S109).
[0059] Then, the schedule management server apparatus 200 transmits
information about the meeting date/time, the meeting location, and
the shortest route finally determined, to each of the client
devices 100 via the set meeting information transmitting unit 260
(S110).
[0060] In each of the client devices 100, the set meeting
information receiving unit 120 receives the set meeting information
automatically set by the schedule management server apparatus 200
(S111). This set meeting information is stored in such a state that
allows the set meeting information to be viewed on the scheduler
140, thus allowing the user of the client device 100 to view and
check the set meeting information via the scheduler 140 and the
display 106.
[0061] When the user actually participates in a meeting that has
been automatically set, the meeting participation history
management unit 130 acquires information about the meeting while
using information stored on the scheduler 140 as appropriate, and
stores the acquired meeting information into the meeting history
database 150 (S112).
[0062] Modifications
[0063] The schedule management server apparatus 200 stores
information about the meeting date/time, the meeting location, and
the shortest route finally determined, in the set meeting
information storing unit 250 as meeting history information.
[0064] Further, the schedule management server apparatus 200
references meeting history information stored in the set meeting
information storing unit 250, and distributes information about the
meeting date/time, the meeting location, and the shortest route
finally determined, to each of the client devices 100.
[0065] Second Exemplary Embodiment
[0066] FIG. 6 illustrates a configuration of the functional blocks
of a schedule management server apparatus 200A. FIG. 7 is a
flowchart illustrating a flow of operation of the schedule
management server apparatus 200A.
[0067] Hereinafter, operation of the schedule management server
apparatus 200A according to a second exemplary embodiment is
described in detail. It is to be noted that components common to
those of the schedule management system 1 according to the first
exemplary embodiment are denoted by the same reference signs, and a
detailed description of those components is omitted.
[0068] The schedule management server apparatus 200A according to
the second exemplary embodiment includes a schedule monitoring unit
270. The schedule monitoring unit 270 detects third schedule
information corresponding to a time period that is on the same day
as received first schedule information and precedes or follows the
first schedule information.
[0069] The schedule management server apparatus 200A receives
desired meeting information transmitted as first schedule
information from each of the client devices 100 (S201), and
temporarily stores the received information in the client's desired
meeting information storing unit 210 (S202).
[0070] Then, the schedule management server apparatus 200A checks
if, as third schedule information, schedule information that
precedes the received desired meeting information in time exists
(S203). If such schedule information exists (Yes at S203), the
schedule management server apparatus 200A transmits positional
information of this schedule information to the address search
server 400, and acquires address information from the address
search server 400 (S204).
[0071] The schedule management server apparatus 200A transmits
positional information of the schedule information immediately
preceding the first schedule information and positional information
of the first schedule information to the station-to-station search
server 500, and acquires station-to-station information from the
station-to-station search server 500 (S205).
[0072] Then, the travel time calculating unit 220 calculates travel
time on the basis of the acquired information (S206). The schedule
monitoring unit 270 determines if the time between the start time
of the first schedule information and the finish time of the
immediately preceding schedule information is greater than or equal
to a required travel time (S207).
[0073] If there is no problem with the travel time (Yes at S207),
the schedule monitoring unit 270 checks if schedule information
that follows the first schedule information in time exists (S208).
If such schedule information exists (Yes at S208), the schedule
management server apparatus 200A transmits positional information
of this schedule information to the address search server 400, and
acquires address information from the address search server 400
(S209).
[0074] The schedule management server apparatus 200A transmits
positional information of the first schedule information and
positional information of the immediately following schedule
information to the station-to-station search server 500, and
acquires station-to-station information from the station-to-station
search server 500 (S210).
[0075] Then, the travel time calculating unit 220 calculates travel
time on the basis of the acquired station-to-station information
(S211).
[0076] The schedule monitoring unit 270 determines if the time
between the start time of the immediately following schedule
information and the finish time of the first schedule information
is greater than or equal to a required travel time (S212). If there
is no problem with the travel time (Yes at S212), the schedule
monitoring unit 270 stores the immediately following schedule
information into the set meeting information storing unit 250, and
transmits information about the meeting date/time, the meeting
location, and the shortest route finally set, to each of the client
devices 100 via the set meeting information transmitting unit 260
(S213).
[0077] If it is determined at step S212 that there is not enough
travel time (No at S212), information to that effect is transmitted
to each of the client devices 100 via the set meeting information
transmitting unit 260 (S214).
[0078] If it is determined at step S207 that there is not enough
travel time (No at S207), information to that effect is transmitted
to each of the client devices 100 via the set meeting information
transmitting unit 260 (S215).
[0079] Third Exemplary Embodiment
[0080] FIG. 8 illustrates a configuration of the functional blocks
of a schedule management server apparatus 200B.
[0081] Hereinafter, operation of the schedule management server
apparatus 200B according to a third exemplary embodiment is
described in detail. It is to be noted that components common to
those of the schedule management system 1 according to the first
exemplary embodiment are denoted by the same reference signs, and a
detailed description of those components is omitted.
[0082] The schedule management server apparatus 200B according to
the third exemplary embodiment includes a content receiving unit
280 and a content providing unit 281. The content receiving unit
280 receives content from a provider that provides information of
the location of a meeting, and content from a provider that
provides information of the nearest station to the departure point,
the nearest station to the destination, and the shortest travel
route. The content providing unit 281 distributes each of these
pieces of content to each of the client devices 100 at a timing
based on a preset schedule.
[0083] Examples of content provided by a provider that provides
information of the location of a meeting include an advertisement
image/picture. The content receiving unit 280 receives an
advertisement image/picture from the property search server 300
that is connected, and saves the advertisement image/picture on the
HDD 206.
[0084] Further, as for an advertisement image/picture as an example
of content provided by a provider that provides information of the
nearest station to the departure point, the nearest station to the
destination, and the shortest travel route, such an advertisement
image/picture is received from the station-to-station search server
500 and saves on the HDD 206.
[0085] The content providing unit 281 determines the content to be
distributed to each of the client devices 100 and its distribution
schedule, on the basis of desired meeting information temporarily
stored in the client's desired meeting information storing unit
210.
[0086] Specifically, for example, the content providing unit 281
selects advertisement information that matches a desired meeting
location range and the shortest route information, and distributes
the selected advertisement information to each of the client
devices 100. Each of the client devices 100 receives an
advertisement distributed from the schedule management server
apparatus 200B via the communication unit 105, and displays the
received advertisement on the display 106.
[0087] Fourth Exemplary Embodiment
[0088] FIG. 9 illustrates a configuration of the functional blocks
of a schedule management server apparatus 200C.
[0089] Hereinafter, operation of the schedule management server
apparatus 200C according to the fourth exemplary embodiment is
described in more detail. It is to be noted that components common
to those of the schedule management system 1 according to the first
exemplary embodiment are denoted by the same reference signs, and a
detailed description of those components is omitted.
[0090] The schedule management server apparatus 200C according to
the fourth exemplary embodiment includes a rental charge
calculating unit 290 that calculates the difference between the
rental charge to be charged for newly renting a set event location
on a single-use basis, and the rental charge to be charged for
continuously renting the very same set event location.
[0091] The rental charge calculating unit 290 calculates the
difference in charge on the basis of usage charge upper limit
information about an event location set for each of the client
devices 100, and the rental charge to be charged for continuously
renting the very same set event location.
[0092] The usage charge upper limit information about an event
location includes information such as equipment, depreciation, and
energy costs for an office or building in which each of the client
devices 100 is installed. The information about the rental charge
for continuously renting the very same set event location is
acquired from the property search server 300.
[0093] The difference in charge calculated by the rental charge
calculating unit 290 transmitted to each of the client devices 100.
Each of the client devices 100 receives the difference in charge
transmitted from the schedule management server apparatus 200C via
the communication unit 105, and displays the difference on the
display 106.
[0094] While the schedule management system 1 is herein implemented
as a system in which the client devices 100 and the schedule
management server apparatus 200 are connected to the network 600
and capable of communicating with each other, the schedule
management system 1 may be implemented as a schedule management
system 1A in which the function of the schedule management server
apparatus 200 is built in each of the client devices 100.
[0095] As illustrated in FIG. 10, when a desired meeting
information input unit 110A receives an input of a desired meeting
date/time, a desired meeting location range, and meeting member
candidates, the schedule management system 1A temporarily stores
desired meeting information of each of the client devices 100 in
the client's desired meeting information storing unit 210.
[0096] Then, a set meeting information display unit 260A displays
set meeting information determined for a matching client device
group, on the display 106 of each of the client devices 100.
[0097] The foregoing description of the exemplary embodiments of
the present invention has been provided for the purposes of
illustration and description. It is not intended to be exhaustive
or to limit the invention to the precise forms disclosed.
Obviously, many modifications and variations will be apparent to
practitioners skilled in the art. The embodiments were chosen and
described in order to best explain the principles of the invention
and its practical applications, thereby enabling others skilled in
the art to understand the invention for various embodiments and
with the various modifications as are suited to the particular use
contemplated. It is intended that the scope of the invention be
defined by the following claims and their equivalents.
* * * * *