KR20210128150A - A mobile lounge providing system and method thereof - Google Patents

Abstract

A method for scheduling a vehicle according to one embodiment comprises: a step of collecting the service area information; a step of predicting a call demand of a service area based on the service area information; a step of generating the dispatch information based on the predicted call demand; and a step of transmitting the dispatch information to at least one vehicle. Therefore, the present invention is capable of improving user convenience.

Description

Vehicle scheduling method and server {A MOBILE LOUNGE PROVIDING SYSTEM AND METHOD THEREOF}

The disclosed invention relates to a vehicle scheduling method and server related to vehicle dispatch.

In general, the operation plan of public transportation is established according to the demand of the user, and has a characteristic in that a predetermined route, first train time, last train time, and dispatch interval are determined. The existing public transportation operation plan was established in such a way that a certain number of vehicles and drivers were dispatched for each route allocated by the transportation company.

However, since the existing public transportation operation plan cannot be flexibly modified or changed according to the fluctuating user demand, it does not meet the user's demand, resulting in a problem of lowering the quality of the service. In addition, since the operation plan of the existing public transportation is based on a predetermined route, the user has the inconvenience of being unable to board at a desired time at a desired place.

Provided are a vehicle scheduling method and a server capable of flexibly controlling the dispatch of vehicles according to the demand of users for each service area.

A vehicle scheduling method according to an embodiment includes: collecting service area information; predicting a call demand in a service area based on the service area information; generating dispatch information based on the predicted call demand; and transmitting the dispatch information to at least one vehicle.

The service area information may include existing call data, public transportation information, traffic volume information, and population data.

The generating of the dispatch information may include: checking the number of vehicles in a first area of the service area and a call demand in the first area; and when the number of vehicles in the first area is greater than or equal to the call demand in the first area, generating the dispatch information based on the number of vehicles in the first area.

The generating of the dispatch information may include: when the number of vehicles in the first area is less than the call demand of the first area, obtaining supportable vehicle information from a second area; and generating the vehicle dispatch information based on the number of vehicles in the first area and vehicle information supportable from the second area.

The call demand may include a call demand by day of the week and a call demand by time.

The dispatch information may include a stop position and a stop time at which the at least one vehicle is disposed.

The transmitting of the vehicle dispatch information may include transmitting a vehicle control signal so that the at least one vehicle moves to the stopped position.

A vehicle scheduling method according to an embodiment includes: generating vehicle matching information based on a call message received from a user terminal and the dispatch information; and transmitting the vehicle matching information to a matched vehicle among the user terminal and the at least one vehicle.

The call message may include a boarding location and destination.

The vehicle matching information may include a driving route, riding time, and seat information.

The transmitting of the vehicle matching information may include transmitting a vehicle control signal so that the matched vehicle moves to the riding position.

A vehicle scheduling method according to an embodiment includes, when a new call message is received from another user terminal, determining whether sharing is possible; and when sharing is possible, correcting the vehicle matching information based on the paging message and the new paging message.

Whether the sharing is possible may be determined based on a boarding position and destination included in each of the paging message and the new paging message.

A server according to an embodiment includes a communication unit; and collecting service area information from an external device through the communication unit, predicting a call demand of a service area based on the service area information, generating dispatch information based on the predicted call demand, and sending the information to at least one vehicle. and a control unit controlling the communication unit to transmit the dispatch information.

The controller may collect the service area information including existing call data, public transportation information, traffic volume information, and population data.

The control unit checks the number of vehicles in the first area of the service area and the call demand of the first area, and when the number of vehicles in the first area is greater than or equal to the call demand of the first area, the number of vehicles in the first area Based on this, the dispatch information may be generated.

When the number of vehicles in the first area is less than the call demand of the first area, the control unit obtains supportable vehicle information from a second area, and includes the number of vehicles in the first area and supportable vehicle information from the second area. Based on this, the dispatch information may be generated.

The controller may predict the call demand for each day of the week and the call demand for each time of the service area.

The controller may generate the vehicle dispatch information including a stop position and a stop time at which the at least one vehicle is disposed.

The controller may transmit a vehicle control signal so that the at least one vehicle moves to the stopped position.

The control unit may generate vehicle matching information based on a call message received from the user terminal and the vehicle dispatch information, and transmit the vehicle matching information to a matched vehicle among the user terminal and the at least one vehicle.

The call message may include a boarding location and destination.

The vehicle matching information may include a driving route, riding time, and seat information.

The controller may transmit a vehicle control signal so that the matched vehicle moves to the riding position.

When a new call message is received from another user terminal, the control unit may determine whether sharing is possible, and when sharing is possible, the controller may modify the vehicle matching information based on the call message and the new call message.

The controller may determine whether the sharing is possible based on a boarding position and a destination included in each of the paging message and the new paging message.

A vehicle scheduling system according to an embodiment includes a user terminal; at least one vehicle; and collecting service area information from an external device, predicting a call demand of a service area based on the service area information, generating dispatch information based on the predicted call demand, and providing the dispatch information to the at least one vehicle a server that transmits, generates vehicle matching information based on the call message received from the user terminal and the dispatch information, and transmits the vehicle matching information to a vehicle matched among the user terminal and the at least one vehicle; may include

According to the disclosed vehicle scheduling method and server, it is possible to flexibly adjust the vehicle dispatch according to the demand of the user for each service area. Accordingly, it is possible to improve the convenience of the user who wants to use the vehicle, and it is possible to satisfy the user's demand even though the number of operable vehicles is limited.

1 is a diagram illustrating a vehicle scheduling system according to an exemplary embodiment.
2 shows a configuration of a server according to an embodiment.
3 is a diagram for explaining a service area.
4 is a flowchart illustrating a vehicle scheduling method according to an exemplary embodiment.
5 is a flowchart specifically explaining a vehicle dispatch method among a vehicle scheduling method according to an exemplary embodiment.
6 is a flowchart illustrating a method of matching a user with a vehicle in a vehicle scheduling method according to an exemplary embodiment.

Like reference numerals refer to like elements throughout. This specification does not describe all elements of the embodiments, and general content in the technical field to which the present invention pertains or content that overlaps among the embodiments is omitted.

Throughout the specification, when a part is "connected" with another part, it includes not only direct connection but also indirect connection, and indirect connection includes connection through a wireless communication network. do.

In addition, when a part "includes" a certain component, this means that other components may be further included, rather than excluding other components, unless otherwise stated.

The singular expression includes the plural expression unless the context clearly dictates otherwise.

In addition, terms such as "~ part", "~ group", "~ block", "~ member", and "~ module" may mean a unit for processing at least one function or operation. For example, the terms may refer to at least one process processed by at least one hardware such as a field-programmable gate array (FPGA)/application specific integrated circuit (ASIC), at least one software stored in a memory, or a processor. have.

The signs attached to each step are used to identify each step, and these signs do not indicate the order between the steps, and each step is performed differently from the stated order unless the context clearly indicates a specific order. can be

Hereinafter, an embodiment of a mobile lounge providing system and a method thereof will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a vehicle scheduling system according to an exemplary embodiment.

Referring to FIG. 1 , a vehicle scheduling system 1 according to an embodiment may include a server 10 , a user terminal 20 , and a vehicle 30 . A plurality of vehicles 30 may exist. The vehicle 30 may be referred to as a service vehicle. Also, the vehicle 30 is a multi-seater vehicle, and may be, for example, an 11-seater van.

The server 10 may communicate with the user terminal 20 and the vehicle 30 through the network 40 . The server 10 may be connected to the network 40 using wireless communication or wired communication, and may communicate directly with the user terminal 20 and the vehicle 30 .

Wireless communication, 5 ^th Generation (5G), LTE, LTE Advance (LTE-A), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), UMTS (Universal Mobile Telecommunications System), WiBro (wireless broadband), or cellular communications using Global System for Mobile communications (GSM).

Wireless communication includes wireless fidelity (WiFi), Bluetooth, Bluetooth low energy (BLE), zigbee, near field communication (NFC), magnetic secure transmission, radio frequency (RF), or body area network (BAN). ) may be included. In addition, the wireless communication may include GNSS. The GNSS may be a Global Positioning System (GPS), a global navigation satellite system (Glonass), a beidou navigation satellite system (hereinafter, “Beidou”) or galileo, the european global satellite-based navigation system.

Wired communication may include Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), Recommended Standard-232 (RS-232), power line communication, or Plain Old Telephone Service (POTS).

The network 40 may include a telecommunications network, a computer network (eg, a LAN or WAN), the Internet, or a telephone network.

The user terminal 20 may include a mobile terminal or a fixed terminal owned by the user. A mobile terminal is an electronic device that can be easily carried and moved. Personal Digital Assistant), PMP (Portable Multimedia Player), DMB (Digital Multimedia Broadcasting) user terminal device, E-Book, portable computer (Notebook, Tablet, etc.) or digital camera (Digital Camera) may be included. A fixed terminal is an electronic device that can be used fixedly at a specific location, and may include a desktop personal computer, a smart TV, and the like.

A plurality of user terminals 20 may also exist. That is, each of the plurality of users may have the user terminal 20 .

2 shows the configuration of the server 10 according to an embodiment.

Referring to FIG. 2 , the server 10 may include a communication unit 100 and a control unit 200 . The communication unit 100 may communicate with the user terminal 20 and the vehicle 30 under the control of the control unit 200 . The communication unit 100 may use the various communication methods described above.

The control unit 200 may include at least one memory 220 in which a program, algorithm, and/or application for executing a vehicle scheduling method is stored, and at least one processor 210 for executing the stored program, algorithm and/or application. have. When the memory 220 and the processor 210 are plural, they may be integrated on one chip or may be provided in physically separate locations.

The memory 220 may include a non-volatile memory device such as a cache, a read only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), and a flash memory. can In addition, the memory 220 may include a volatile memory device such as a random access memory (RAM), and may include a storage medium such as a hard disk drive (HDD) or a CD-ROM. The type of the memory 220 is not limited to the exemplified one.

Meanwhile, although not shown, the user terminal 20 and the vehicle 30 may also include a communication unit and a control unit, respectively.

Hereinafter, a vehicle scheduling method according to an embodiment will be described in detail.

3 is a diagram for explaining a service area. 4 is a flowchart illustrating a vehicle scheduling method according to an exemplary embodiment.

Referring to FIG. 3 , the service area is an area within a predetermined radius from the stopping position of the vehicle 30 , and may include a first area, a second area, and a third area. Since the service area shown in FIG. 3 is exemplary, the service area may be set in various ways.

A stop is a place where the vehicle 30 can stop. For example, the stop may be a parking lot. A first stop, a second stop, and a third stop may exist in each of the first area, the second area, and the third area. However, the stop is not limited to that illustrated in FIG. 3 . There can be multiple stops in each area.

Referring to FIG. 4 , the control unit 200 of the server 10 may collect service area information from an external device through the communication unit 100 ( 301 ). The service area information may include existing call data, public transportation information, traffic volume information, and population data. The external device may mean another server or database.

The controller 200 of the server 10 may predict a call demand based on the service area information ( 302 ). The call demand refers to the user's demand for the vehicle 30 . In other words, the call demand may mean the number of calls by users who want to use the vehicle 30 . For example, when there is a large population or heavy traffic in the service area, the call demand may be high. In addition, there may be high demand for calls even when public transportation within the service area is insufficient. The public transport information may refer to the number of public transport routes.

The control unit 200 of the server 10 may predict the call demand based on the existing call data of the service area. The existing call data may include a call message received from the user terminal 20 for a predetermined period in the service area. The control unit 200 of the server 10 may predict the call demand based on the number of call messages received during a predetermined period. Also, the control unit 200 of the server 10 may predict the call demand by day of the week and the call demand by time of the service area. For example, the control unit 200 of the server 10 may predict the call demand with respect to the Thursday afternoon time of this week or the Thursday afternoon time of the following week based on the number of calls that occurred during the Thursday afternoon time for the past several weeks.

The control unit 200 of the server 10 may predict the call demand based on the hourly traffic volume of the service area. For example, the traffic volume during commuting hours in the service area may be greater than the traffic volume at other times. The server 10 may calculate an average traffic volume for time other than commuting time. The server 10 may predict the call demand during commuting time as high as the difference between the traffic volume at the commute time and the average traffic volume at other times.

In addition, if there is no existing call data of the second area, and the population data of the first area and the population data of the second area are similar, the control unit 200 of the server 10 provides the predicted call demand for the first area 2 It can be predicted by local call demand. When the population data of the first region and the population data of the second region are similar, the public transport information of the first region and the public transport information of the second region may be similar.

The controller 200 of the server 10 may generate dispatch information based on the predicted call demand ( 303 ). The control unit 200 of the server 10 may generate dispatch information for disposing the vehicle 30 in each region in proportion to the call demand in each region. By disposing the vehicle 30 in the service area in advance before the user's service request is made, the user's accessibility can be improved. The server 10 may transmit the generated vehicle dispatch information to the vehicle 30 ( 304 ). Also, the control unit 200 of the server 10 may generate dispatch information for each day of the week and dispatch information for each time based on the call demand for each day of the week and the call demand for each time.

The dispatch information may include a stop position and a stop time at which the at least one vehicle 30 is to be disposed. The vehicle 30 that has received the dispatch information may move to a stop position included in the dispatch information, and wait at the stop position for a stop time ( 305 ). The stopping position corresponds to the stopping position described in FIG. 3 .

In addition, the vehicle dispatch information may include driver assignment information. When the vehicle 30 is not an autonomous vehicle, a driver is required. The controller 200 of the server 10 may generate driver assignment information using the total number of drivers and the working hours of each driver.

The user terminal 20 may transmit a paging message to the server 10 (306). The call message may include the ride location and destination.

The controller 200 of the server 10 may generate vehicle matching information based on the call message and dispatch information received from the user terminal 20 ( 307 ). The vehicle matching information may include a driving route to a destination, riding time, and seat information.

For example, the controller 200 of the server 10 may match the vehicle 30 within a predetermined distance from the boarding position included in the call message. The control unit 200 of the server 10 may match the vehicle 30 existing in the closest stop position from the boarding position included in the call message. In addition, the controller 200 of the server 10 may obtain the current location information of the vehicle 30 and match the vehicle 30 that is closest to the boarding location included in the call message.

The server 10 may transmit vehicle matching information to a matched vehicle among the user terminal 20 and the at least one vehicle 30 ( 308 ). Also, the control unit 200 of the server 10 may transmit a vehicle control signal so that the matched vehicle moves to the riding position.

The user terminal 20 may display a map of a service area in which an icon of a matched vehicle is displayed on the screen based on the vehicle matching information received from the server 10 . In addition, the user terminal 20 may display a screen including at least one of a riding position, a riding time, seat information, a moving state of the vehicle, or a driving route to a destination.

5 is a flowchart specifically explaining a vehicle dispatch method among a vehicle scheduling method according to an exemplary embodiment.

Referring to FIG. 5 , the controller 200 of the server 10 may check the number of vehicles 30 in the first area among the service areas ( 501 ) and check the call demand in the first area ( 502 ). When the number of vehicles in the first region is equal to or greater than the call demand in the first region, the controller 200 of the server 10 may generate dispatch information based on the number of vehicles in the first region ( 503 and 504 ).

For example, when the number of vehicles 30 existing in the first area is greater than the call demand, the call demand may be satisfied. That is, the addition of the vehicle 30 is not required. By appropriately arranging the vehicles 30 existing in the first area at the stops in the first area, efficient vehicle operation is possible.

Meanwhile, when the number of vehicles in the first area is less than the call demand in the first area, the controller 200 of the server 10 may obtain supportable vehicle information from the second area among the service areas ( 503 and 505 ). Also, the controller 200 of the server 10 may generate vehicle dispatch information based on the number of vehicles in the first area and vehicle information supportable from the second area ( 506 ).

For example, the number of vehicles 30 disposed in the first area may be less than the call demand in the first area. In this case, the server 10 may extract a supportable vehicle from among the vehicles 30 existing in the second area. A vehicle waiting at the second stop in the second area may be extracted as a supportable vehicle. More specifically, when the number of vehicles existing in the second region exceeds the current call demand, the number of vehicles exceeding the current call demand may be determined as supportable vehicles.

In this way, the server 10 may calculate the gap between the call demand and the vehicle supply for each service area, and arrange the vehicle so that the sum of the gaps in the plurality of service areas is minimized. Also, the server 10 may generate dispatch information by reflecting the time and cost required for the vehicle 30 to move to another service area.

As another example, when the number of vehicles 30 disposed in the first area is smaller than the call demand in the first area, additional vehicles may be dispatched from the garage. The garage is a place located outside the service area, and may be a place where vehicle inspection or maintenance is performed.

The server 10 may transmit the generated vehicle dispatch information to each vehicle 30 ( S507 ).

6 is a flowchart illustrating a method of matching a user with a vehicle in a vehicle scheduling method according to an exemplary embodiment.

Referring to FIG. 6 , the controller 200 of the server 10 may generate vehicle matching information based on a call message and dispatch information received from the user terminal 20 ( 601 ). The vehicle matching information may include a driving route to a destination, riding time, and seat information.

The server 10 may transmit vehicle matching information to a matched vehicle among the user terminal 20 and the at least one vehicle 30 ( 602 ). Also, the control unit 200 of the server 10 may transmit a vehicle control signal so that the matched vehicle moves to the riding position.

When a new call message is received from another user terminal, the controller 200 of the server 10 may determine whether sharing is possible (603, 604). The control unit 200 of the server 10 may determine whether a ride is possible based on the boarding position and destination included in each of the call message and the new call message.

For example, a driving route may be generated using a call message first received from the first user terminal. Thereafter, a new call message may be received from the second user terminal. When the user's location included in the new call message is on the driving route, and the second destination of the new call message is adjacent to the first destination of the first call message, it may be determined that sharing is possible. Whether sharing is possible may be determined according to the execution result of the sharing algorithm pre-stored in the memory 220 .

The controller 200 of the server 10 may correct vehicle matching information based on the call message and the new call message when sharing is possible ( 605 ). For example, driving route and seat information among vehicle matching information may be modified.

The server 10 may transmit the corrected vehicle matching information to the user terminal 20 and the matched vehicle 30 ( 606 ).

As described above, according to the disclosed vehicle scheduling method and server, it is possible to flexibly control vehicle dispatch according to the user's demand for each service area. Accordingly, it is possible to improve the convenience of the user who wants to use the vehicle, and it is possible to satisfy the user's demand even though the number of operable vehicles is limited.

Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium storing instructions executable by a computer. Instructions may be stored in the form of program code, and when executed by a processor, may generate program modules to perform operations of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.

The computer-readable recording medium includes any type of recording medium in which instructions readable by the computer are stored. For example, there may be a read only memory (ROM), a random access memory (RAM), a magnetic tape, a magnetic disk, a flash memory, an optical data storage device, and the like.

The disclosed embodiments have been described with reference to the accompanying drawings as described above. Those of ordinary skill in the art to which the present invention pertains will understand that the present invention may be practiced in other forms than the disclosed embodiments without changing the technical spirit or essential features of the present invention. The disclosed embodiments are illustrative and should not be construed as limiting.

10: server 20: user terminal
30: vehicle 40: network
100: communication unit 200: control unit

Claims (27)

collecting service area information;
predicting a call demand in a service area based on the service area information;
generating dispatch information based on the predicted call demand; and
and transmitting the dispatch information to at least one vehicle. According to claim 1,
The step of collecting the service area information includes:
Collecting existing call data, public transportation information, traffic volume information, and population data of the service area; Vehicle scheduling method comprising a. 3. The method of claim 2,
The step of generating the dispatch information includes:
checking the number of vehicles in a first area of the service area and a call demand in the first area; and
and generating the dispatch information based on the number of vehicles in the first region when the number of vehicles in the first region is greater than or equal to the call demand in the first region. 4. The method of claim 3,
The step of generating the dispatch information includes:
obtaining supportable vehicle information from a second area when the number of vehicles in the first area is less than the call demand of the first area; and
and generating the dispatch information based on the number of vehicles in the first region and vehicle information supportable from the second region. According to claim 1,
The call demand is
A vehicle scheduling method including call demand by day of the week and call demand by hour. According to claim 1,
The dispatch information is
A vehicle scheduling method comprising a stop position and a stop time at which the at least one vehicle is disposed. 7. The method of claim 6,
The step of transmitting the dispatch information is
and transmitting a vehicle control signal so that the at least one vehicle moves to the stopped position. According to claim 1,
generating vehicle matching information based on a call message received from a user terminal and the vehicle dispatch information; and
and transmitting the vehicle matching information to a matched vehicle among the user terminal and the at least one vehicle. 9. The method of claim 8,
The call message is
A method of scheduling a vehicle including ride location and destination. 9. The method of claim 8,
The vehicle matching information is
A method of scheduling a vehicle including travel route, ride time and seat information. 9. The method of claim 8,
Transmitting the vehicle matching information comprises:
and transmitting a vehicle control signal so that the matched vehicle moves to the riding position. 9. The method of claim 8,
when a new call message is received from another user terminal, determining whether a ride is possible; and
When sharing is possible, modifying the vehicle matching information based on the paging message and the new paging message; vehicle scheduling method further comprising a. 13. The method of claim 12,
Whether it is possible to share
A vehicle scheduling method determined based on a boarding position and a destination included in each of the paging message and the new paging message. communication department; and
Collect service area information from an external device through the communication unit, predict a call demand of a service area based on the service area information, generate dispatch information based on the predicted call demand, and send the information to at least one vehicle. A server comprising a; a control unit for controlling the communication unit to transmit the dispatch information. 15. The method of claim 14,
the control unit
A server that collects the service area information including existing call data, public transportation information, traffic volume information, and population data. 16. The method of claim 15,
the control unit
Check the number of vehicles in the first area of the service area and the call demand of the first area,
When the number of vehicles in the first area is greater than or equal to the call demand in the first area, the server generates the dispatch information based on the number of vehicles in the first area. 17. The method of claim 16,
the control unit
If the number of vehicles in the first area is less than the call demand of the first area, obtain supportable vehicle information from a second area;
A server generating the vehicle dispatch information based on the number of vehicles in the first area and vehicle information supportable from the second area. 15. The method of claim 14,
the control unit
A server that predicts the call demand by day of the week and the call demand by time of the service area. 15. The method of claim 14,
the control unit
A server generating the vehicle dispatch information including a stop position and a stop time at which the at least one vehicle is disposed. 20. The method of claim 19,
the control unit
A server that transmits a vehicle control signal so that the at least one vehicle moves to the stopped position. 15. The method of claim 14,
the control unit
generating vehicle matching information based on the call message received from the user terminal and the vehicle dispatch information;
A server that transmits the vehicle matching information to a matched vehicle among the user terminal and the at least one vehicle. 22. The method of claim 21,
The call message is
A server containing the ride location and destination. 22. The method of claim 21,
The vehicle matching information is
Server containing travel route, ride time and seat information. 22. The method of claim 21,
the control unit
A server that transmits a vehicle control signal so that the matched vehicle moves to the riding position. 22. The method of claim 21,
the control unit
When a new call message is received from another user terminal, it is determined whether sharing is possible,
When sharing is possible, the server corrects the vehicle matching information based on the call message and the new call message. 26. The method of claim 25,
the control unit
A server for determining whether the ride is possible based on the boarding location and destination included in each of the paging message and the new paging message. user terminal;
at least one vehicle; and
Collect service area information from an external device, predict call demand of a service area based on the service area information, generate dispatch information based on the predicted call demand, and provide the dispatch information to the at least one vehicle a server that transmits, generates vehicle matching information based on the call message received from the user terminal and the vehicle dispatch information, and transmits the vehicle matching information to the user terminal and a vehicle matched among the at least one vehicle; vehicle scheduling system.

Images