Method and apparatus for providing a driver interface - Patents.com
The interface for drivers in demand-based transportation systems addresses inefficiencies in conventional methods by managing vehicle operations through identifier verification and state-based interface activation, improving driver comfort and service efficiency.
Patent Information
- Application Number
- JP2023113289
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-07-08
- Filing Date
- 2023-07-10
- Publication Date
- 2024-11-27
- Estimated Expiration
- 2043-07-10
AI Technical Summary
Conventional transportation methods such as buses and taxis face inefficiencies in rural areas due to limited availability and high costs, while demand-based transportation systems lack effective interfaces for drivers to manage operations efficiently.
A method and apparatus providing an interface for drivers, including steps for identifier verification, registration, and activation of interfaces based on vehicle state, to manage demand-based transportation services effectively.
Enables comfortable and efficient operation of demand-based transportation systems by adapting interfaces to vehicle states, enhancing driver experience and service provision.
Smart Images

Figure 0007591104000002 
Figure 0007591104000003 
Figure 0007591104000004
Abstract
Description
[Technical field]
[0001] The present invention relates to a method and apparatus for providing a driver interface. [Background technology]
[0002] Traditional means of transportation include buses, subways, and taxis. Buses and subways are inexpensive but have the inconvenience of requiring passengers to go directly to a designated area at a designated time to board. Taxis allow passengers to board and disembark wherever they want, but have the disadvantage of being expensive.
[0003] In ordinary cities, people can freely use public transportation such as buses, subways, and taxis, but in remote areas such as the countryside, taxis may not operate and buses may only operate three or four times a day, making access to traditional public transportation less convenient.
[0004] Demand-responsive transport (DRT) is emerging as a transportation method that can make up for the advantages and disadvantages of conventional transportation methods. Demand-responsive transport is a transportation method that does not have fixed routes and can flexibly operate operation sections, frequency of operation, and operation times according to user demand.
[0005] In recent years, there has been a demand for research into methods for operating demand-based transportation systems more efficiently.
[0006] The above-mentioned background art is technical information that the inventor possessed for the purpose of deriving the present invention or that he / she acquired in the process of deriving the present invention, and is not necessarily publicly known art that was disclosed to the general public prior to the filing of the application of the present invention. Summary of the Invention [Problem to be solved by the invention]
[0007] An object of the present disclosure is to provide a method and device for providing a driver interface. The problems to be solved by the present disclosure are not limited to the problems mentioned above, and other problems and advantages of the present disclosure not mentioned can be understood from the following description and will be more clearly understood by the embodiments of the present disclosure. It will be understood that the problems and advantages to be solved by the present disclosure can be realized by the means and combinations thereof set forth in the claims. Means for achieving the problems
[0008] A first aspect of the present disclosure may provide a connection method for vehicle operation services, including a step of receiving an input of a first identifier corresponding to vehicle service provider information, a step of requesting verification of the first identifier and registration of a backup connection device, a step of receiving an input of a second identifier corresponding to device identification information in response to completion of verification of the first identifier, a step of requesting completion of verification of the second identifier and vehicle registration, and a step of activating an interface corresponding to the vehicle service provider information and the device identification information in response to completion of verification of the second identifier.
[0009] A second aspect of the present disclosure may provide a connection device for vehicle operation services, including a memory having at least one program stored therein, and a processor operating by executing the at least one program, wherein the processor receives an input of a first identifier corresponding to vehicle service provider information, requests verification of the first identifier and registration of a backup connection device, and in response to completion of verification of the first identifier, receives an input of a second identifier corresponding to device identification information, requests verification of the second identifier and completion of vehicle registration, and in response to completion of verification of the second identifier, activates an interface corresponding to the vehicle service provider information and the device identification information.
[0010] A third aspect of the present disclosure can provide a method for providing an interface for a driver, which includes a step of determining a main interface that displays information about vehicle operation services based on a state of the vehicle, and a step of generating the determined main interface, wherein the step of determining the main interface includes a step of determining the main interface in a pre-work interface, a step of determining the main interface in a workplace transfer interface in response to the state of the vehicle switching to a workplace transfer state, and a step of determining the main interface in a vehicle dispatch waiting interface in response to the state of the vehicle switching to a vehicle dispatch waiting state.
[0011] A fourth aspect of the present disclosure can provide a driver interface providing device that includes a memory having at least one program stored therein, and a processor that operates by executing the at least one program, wherein the processor determines a main interface that displays information related to vehicle operation services based on a vehicle state, and generates a determined main interface, wherein determining the main interface includes determining the main interface with a pre-work interface, determining the main interface with a workplace transfer interface in response to the vehicle state switching to a workplace transfer state, and determining the main interface with a vehicle dispatch waiting interface in response to the vehicle state switching to a vehicle dispatch waiting state.
[0012] A fifth aspect of the present disclosure may provide a method for providing a vehicle operation information interface, the method including: determining a main interface that displays information related to vehicle operation services based on a vehicle state; and generating the determined main interface, wherein the determining the main interface includes determining the main interface in a vehicle dispatch waiting interface; and determining the main interface in a boarding location moving interface in response to the vehicle state switching to a boarding location moving state, the vehicle dispatch waiting interface including a driving route interface configured to display an environment surrounding the vehicle, a route guidance interface including a navigation map, a notification interface that displays notifications related to the vehicle's operation allocation, and an autonomous driving function status interface.
[0013] A sixth aspect of the present disclosure can provide a vehicle operation information interface providing device including a memory having at least one program stored therein, and a processor operating by executing the at least one program, wherein the processor determines a main interface, which is an interface that displays information related to vehicle operation services based on a state of a vehicle, and generates the determined main interface, wherein determining the main interface includes determining the main interface in a vehicle dispatch waiting interface, and determining the main interface in a boarding location moving interface in response to the state of the vehicle switching to a boarding location moving state, wherein the vehicle dispatch waiting interface includes a driving route interface configured to display the environment around the vehicle, a route guidance interface including a navigation map, a notification interface that displays notifications related to the vehicle's operation allocation, and an autonomous driving function status interface.
[0014] A seventh aspect of the present disclosure may provide a method for providing an interface for vehicle operation, including a step of collecting data including information about a vehicle, a state of the vehicle, location information of the vehicle, information about a destination, or a signal generated by a device installed in the vehicle, and a step of generating a driver interface to be displayed on a driver information providing device and an external display interface to be displayed on an external display device based on the collected data.
[0015] An eighth aspect of the present disclosure includes a memory having at least one program stored therein, and a processor operating by executing the at least one program, wherein the processor is capable of providing an interface providing device for vehicle operation that collects data including vehicle information, a state of the vehicle, location information of the vehicle, information regarding the destination, or a signal generated by a device mounted on the vehicle, and generates a driver interface to be displayed on a driver information providing device and an external display interface to be displayed on an external display device based on the collected data.
[0016] A ninth aspect of the present disclosure may provide a computer-readable recording medium having recorded thereon a program for causing a computer to execute a method according to the first, third, fifth, or seventh aspect. Effect of the Invention
[0017] According to the above-mentioned means for solving the problems disclosed herein, a demand-based transportation system can be operated effectively.
[0018] In addition, an interface that switches appropriately depending on the vehicle's condition can be displayed, enabling comfortable and efficient work for the driver and the provision of on-demand vehicle services. [Brief description of the drawings]
[0019] [Figure 1]FIG. 1 is a diagram for explaining an automatic driving method according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing hardware included in an automatic driving device according to one embodiment. [Diagram 3] FIG. 1 is a diagram for explaining a demand-based transportation system according to an embodiment. [Figure 4] 1 is a state diagram illustrating a process in which a demand-based vehicle is operated in a demand-based transportation system according to an embodiment and a change in the state of the demand-based vehicle. [Diagram 5] 1 is a diagram illustrating a connection process for operating a vehicle according to an embodiment; [Figure 6A] 11 is an exemplary diagram illustrating an interface that may be displayed during a connection process for vehicle operation according to an embodiment. FIG. [Figure 6B] 11 is an exemplary diagram illustrating an interface that may be displayed during a connection process for vehicle operation according to an embodiment. FIG. [Figure 7] FIG. 13 is an exemplary diagram illustrating a driving route interface according to one embodiment. [Figure 8] FIG. 13 is an exemplary diagram illustrating a pre-work interface generated according to one embodiment. [Figure 9] FIG. 13 is an exemplary diagram illustrating a work location mobility interface generated according to one embodiment. [Figure 10] FIG. 13 is an exemplary diagram illustrating a ride waiting interface generated according to one embodiment. [Figure 11] FIG. 13 is an exemplary diagram illustrating a ride location transfer interface generated according to one embodiment. [Figure 12] FIG. 13 is an exemplary diagram illustrating a seat information interface generated according to one embodiment. [Figure 13] 1 is an exemplary diagram illustrating an operation of an external display device according to an embodiment; [Figure 14] 4 is a flow chart of a connection method for vehicle navigation services according to one embodiment. [Figure 15]1 is a flow chart of a method for providing a driver interface according to one embodiment. [Figure 16] 1 is a flowchart of a method for providing a vehicle operational information interface according to one embodiment. [Figure 17] 1 is a flowchart of a method for providing an interface for vehicle navigation according to one embodiment. [Figure 18] FIG. 2 is a block diagram of an apparatus according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0020] The advantages and features of the present invention, as well as the methods for achieving them, will become apparent from the embodiments described in detail with the accompanying drawings. However, the present invention is not limited to the embodiments presented below, and may be realized in various different forms, and it should be understood that the present invention includes all modifications, equivalents, and alternatives within the spirit and technical scope of the present invention. The embodiments presented below are provided to ensure that the disclosure of the present invention is complete, and to fully convey the scope of the invention to those skilled in the art to which the present invention pertains. In the description of the present invention, if a detailed description of a related known technology is deemed to obscure the gist of the present invention, the detailed description will be omitted.
[0021] The terms used in this application are merely used to describe certain embodiments and are not intended to limit the present invention. A singular expression includes a plural expression unless the context clearly indicates otherwise. In this application, terms such as "include" or "have" are intended to specify the presence of features, numbers, steps, operations, components, parts, or combinations thereof described herein, and should be understood not to preclude the presence or additional possibility of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0022] Some embodiments of the present disclosure may be illustrated in functional block configurations and various processing steps. Some or all of these functional blocks may be implemented in various hardware and / or software configurations that perform specific functions. For example, the functional blocks of the present disclosure may be implemented by one or more microprocessors or by circuit configurations for a given function. Also, for example, the functional blocks of the present disclosure may be implemented in various programming or scripting languages. The functional blocks may be implemented by algorithms executed by one or more processors. Furthermore, the present disclosure may employ conventional techniques for electronic configuration, signal processing, and / or data processing, etc. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical and physical configurations.
[0023] Furthermore, the connecting lines or connecting members between components shown in the figures are merely exemplary of functional and / or physical or circuit connections, and in an actual device the connections between components may be represented by various interchangeable or additional functional, physical or circuit connections.
[0024] A vehicle may include any type of transportation means used to move people or goods with a vehicle, such as a car, bus, motorcycle, scooter, or truck.
[0025] The present disclosure will now be described in detail with reference to the accompanying drawings.
[0026] FIG. 1 is a diagram for explaining an automatic driving method according to an embodiment.
[0027] Referring to FIG. 1, an autonomous driving device according to an embodiment of the present invention may be mounted on a vehicle to realize an autonomous vehicle 10. The autonomous driving device mounted on the autonomous vehicle 10 may include various sensors for collecting surrounding situation information. As an example, the autonomous driving device may detect the movement of a leading vehicle 20 traveling ahead through an image sensor and / or an event sensor mounted on the front of the autonomous vehicle 10. The autonomous driving device may further include sensors for detecting other vehicles 30 traveling in adjacent lanes as well as the front of the autonomous vehicle 10, and pedestrians around the autonomous vehicle 10.
[0028] At least one of the sensors for collecting situation information around the autonomous vehicle may have a predetermined field of view (FoV) as shown in Fig. 1. As an example, when a sensor mounted on the front of the autonomous vehicle 10 has a field of view (FoV) as shown in Fig. 1, information detected at the center of the sensor may have a relatively high importance. This is because the information detected at the center of the sensor contains most of the information corresponding to the movement of the leading vehicle 20.
[0029] The autonomous driving device processes information collected by sensors of the autonomous vehicle 10 in real time to control the movement of the autonomous vehicle 10, while at least a portion of the information collected by the sensors can be stored in a memory device.
[0030] FIG. 2 is a block diagram showing hardware included in an automatic driving device according to one embodiment.
[0031] 2, the autonomous driving device 40 may include a sensor unit 41, a processor 46, a memory system 47, and a vehicle control module 48. The sensor unit 41 includes a plurality of sensors 42-45, which may include an image sensor, an event sensor, an illuminance sensor, a GPS device, an acceleration sensor, and the like.
[0032] The data collected by the sensors 42-45 may be transferred to the processor 46. The processor 46 may store the data collected by the sensors 42-45 in a memory system 47 and control a body control module 48 to determine the movement of the vehicle based on the data collected by the sensors 42-45. The memory system 47 may include two or more memory devices and a system controller for controlling the memory devices. Each of the memory devices may be provided on a single semiconductor chip.
[0033] In addition to the system controller of memory system 47, each memory device included in memory system 47 may include a memory controller, and the memory controller may include an artificial intelligence (AI) calculation circuit such as a neural network. The memory controller can generate calculation data by applying a predetermined weight to data received from sensors 42 to 45 or processor 46, and store the calculation data in a memory chip.
[0034] The automatic driving device 40 may be installed in a demand-based vehicle described below.
[0035] FIG. 3 is a diagram for explaining a demand-based transportation system according to an embodiment.
[0036] Demand-responsive transport (DRT) refers to a transportation method that does not have fixed routes and can flexibly operate operation sections, frequency of operation, and operation times according to user demand.
[0037] Demand-based transportation can be divided into various types depending on the route operation method. For example, the fixed route type is a type in which the operating time, stops, and starting and ending points are all fixed. The route deviation type is a type in which the operating time and starting and ending points are fixed, but in the case of stops, new stops can be set in addition to the fixed stops according to user reservations. The semi-dynamic type is a type in which the starting and ending points are fixed, but only the departure and arrival times are fixed for the operating time, and stops can be freely set in addition to the starting and ending points. The dynamic type is a type in which the operating time, stops, and starting and ending points are not fixed.
[0038] Demand-based transportation can also be divided into various types depending on the number of origins and destinations. For example, the one-to-one type is a type that departs from one point and travels to another. The one-to-many type is a type that travels from one origin to multiple destinations, while the many-to-one type is a type that travels from multiple origins to one destination. The many-to-many type has no origin and destination and can be changed according to circumstances and demands.
[0039] Referring to FIG. 3, a demand-based transportation system 300 may include a user terminal 310, a control server 320, and a demand-based vehicle 330.
[0040] The user terminal 310 may refer to a terminal of a user (hereinafter, "service user") who intends to use the demand-based transportation system 300. In the present disclosure, the user terminal 310 may have the same meaning as a device for a service user. A service user application configured to transmit and receive various information and provide an interface for the service user to use the demand-based transportation system 300 may be installed in the user terminal 310. In other words, the user terminal 310 may refer to a terminal in which a service user application is installed.
[0041] A service user can receive a vehicle dispatch service that determines a boarding location and a disembarking location via the user terminal 310 and dispatches a vehicle based on the boarding location and a disembarking location. The service user can also receive vehicle dispatch information via the user terminal 310 until boarding the dispatched vehicle. The service user can also receive operation information regarding the vehicle that the service user boarded via the user terminal 310.
[0042] The user terminal 310 can receive input from a service user via an application, transmit data to the control server 320 or the demand-type vehicle 330 based on the received input, receive data from the control server 320 or the demand-type vehicle 330, and provide a service to the service user via the application based on the received data.
[0043] The user terminal 310 may be, but is not limited to, a smartphone, a tablet PC, a PC, a smart TV, a mobile phone, a PDA (personal digital assistant), a laptop, a media player, a microserver, a GPS (global positioning system) device, an e-book reader, a digital broadcasting terminal, a navigation system, a kiosk, an MP3 player, a digital camera, a home appliance, a device equipped with a camera, and other mobile or non-mobile computing devices. Alternatively, the user terminal 310 may be, but is not limited to, a wearable device such as a watch, glasses, a headband, and a ring with communication and data processing capabilities.
[0044] The control server 320 refers to a server that performs a control function for operating a demand-based transportation system. The control server 320 can transmit and receive data to and from the user terminal 310 to provide the service user with the use of the demand-based transportation system 300. In addition, the control server 320 can transmit and receive data to and from the demand-based vehicle 330 to maintain, repair, manage, or control the demand-based transportation system 300.
[0045] The control server 320 can store information or data necessary to realize the demand-based transportation system 300, including information about service users, information about the vehicle service provider (e.g., the vehicle operating corporation) that operates the demand-based transportation, information about the drivers belonging to the vehicle service provider, information about the drivers' work status, information about the demand-based vehicles, etc.
[0046] A control information providing device may be provided that is part of the control server 320 or is connected to the control server 320 and can be used by an administrator of the control server 320 to perform the functions of the control server 320. The control information providing device may provide a control interface with which the administrator of the control server 320 can interact.
[0047] The on-demand vehicle 330 refers to a vehicle that provides transportation to a service user according to a demand-based transportation operation method under the control of the control server 320. The on-demand vehicle 330 may be a vehicle that is dispatched according to a user's demand, and the operation route, number of operations, operation time, etc. are determined according to the operation method of the demand-based transportation.
[0048] The demand vehicle 330 may include a driver information device, a passenger information device, or a vehicle exterior display device.
[0049] The driver information providing device may refer to a part of the demand vehicle 330 or a device connected to the demand vehicle 330 that can be used by an on-board driver who is on board the demand vehicle 330 and drives the demand vehicle 330 directly or assists in automatic driving. Alternatively, the driver information providing device may be a part of an automatic driving device mounted on the demand vehicle 330 or a device connected to the automatic driving device. The driver information providing device may provide information about the on-board demand vehicle to the on-board driver and transmit data to the control server 320 in response to an interaction with the on-board driver.
[0050] The passenger information providing device may refer to a device that is a part of the demand-type vehicle 330 or is connected to the demand-type vehicle 330 and can be used by a service user (hereinafter, "passenger") aboard the demand-type vehicle 330. Alternatively, the passenger information providing device may be a part of an automatic driving device mounted on the demand-type vehicle 330 or a device connected to the automatic driving device. The passenger information providing device may be configured to provide information about the demand-type vehicle aboard the passenger and to be able to interact with the passenger.
[0051] The external display device may refer to a part of the demand-type vehicle 330 or a device connected to the demand-type vehicle 330 that can display information toward the outside of the demand-type vehicle 330. Alternatively, the external display device may be a part of an automatic driving device mounted on the demand-type vehicle 330 or a device connected to the automatic driving device. The external display device may be linked to a driver information providing device or a passenger information providing device, and may be configured to display various information outside the demand-type vehicle 330.
[0052] The user terminal 310, the control server 320, and the demand-type vehicle 330 can communicate using a network. For example, the network includes a local area network (LAC), a wide area network (WAN), a value-added network (VAL), a mobile radio communication network, a satellite communication network, and a combination thereof, and is a comprehensive data communication network that enables each network component shown in FIG. 3 to smoothly communicate with each other, and can include a wired Internet, a wireless Internet, and a mobile wireless communication network. In addition, the wireless communication can include, for example, a wireless LAN (Wi-Fi), Bluetooth (registered trademark), Bluetooth low energy, ZigBee, Wi-Fi Direct (WFD), ultra wideband (UWB), infrared data association (IrDA), near field communication (NFC), and the like, but is not limited thereto.
[0053] FIG. 4 is a state diagram illustrating a process in which a demand-based vehicle is operated in a demand-based transportation system according to an embodiment and a change in the state of the demand-based vehicle.
[0054] Each state shown in Fig. 4 means one of the states that a demand-based vehicle may have in the process of operating the demand-based vehicle in a demand-based transportation system. In the following, the term "vehicle" may be interpreted as including a demand-based vehicle.
[0055] In the present disclosure, the vehicle state can be automatically switched based on certain conditions, such as the location of the vehicle.
[0056] In the present disclosure, the pre-work state S1 may refer to the state of the vehicle before the driver boards the vehicle and performs work authentication. The driver can work according to a work plan corresponding to the work information stored in the control server. In one embodiment, the state of the vehicle may be set or initialized to the pre-work state S1 in response to the remaining time until the work start time included in the work information stored in the control server being less than or equal to a critical time.
[0057] In the present disclosure, the workplace moving state S2 may refer to the state of a vehicle that is not at the workplace and is moving to the workplace. In one embodiment, the workplace moving state S2 may refer to the state of a vehicle that is switched to when the driver of the vehicle completes attendance authentication in the pre-work state S1. In one embodiment, the workplace may refer to any point on the autonomous driving route.
[0058] In this disclosure, the dispatch waiting state S3 may refer to the state of the vehicle when it is on an autonomous driving route and can be assigned to operate, but has not yet been assigned.
[0059] In the present disclosure, the boarding location movement state S4 may refer to the state of the vehicle when the vehicle is assigned to operate and moves to the boarding location where the passenger has decided to board. In the present disclosure, the vehicle being assigned to operate may correspond to the completion of dispatch to the service user. In the present disclosure, even if the vehicle is assigned to operate, the operation may be canceled by the on-board driver, the control server, or the passenger who has decided to board.
[0060] In this disclosure, drop-off location travel state S5 may refer to the state of the vehicle when a passenger boards the vehicle and travels to a drop-off location where the passenger chooses to get off.
[0061] In one embodiment, when the state of the vehicle is in the drop-off moving state S5, in response to a passenger dropping off at the drop-off location, the state of the vehicle may switch to the waiting for dispatch state S3.
[0062] In the present disclosure, the rest area moving state S6 may refer to a state of the vehicle when the driver moves the vehicle to a rest area for the driver's rest. In one embodiment, the state of the vehicle can be switched to the rest area moving state S6 based on a rest plan included in a work plan corresponding to information about work stored in the control server.
[0063] In this disclosure, rest state S7 may refer to the state of the vehicle when the vehicle has moved to a rest area and the driver on board is taking a rest.
[0064] In one embodiment, when the state of the vehicle is in the rest state S7, in response to the driver's rest period expiring, the state of the vehicle may switch to the work location transfer state S2.
[0065] In the present disclosure, the leaving location moving state S8 may refer to the state of a vehicle when a vehicle that is not at the leaving location is moving to the leaving location. In one embodiment, the state of the vehicle can be switched to the leaving location moving state S8 based on a work plan corresponding to the work information stored in the control server.
[0066] In the present disclosure, the end-of-duty state S9 may refer to the state of the vehicle when the driver ends his / her work and moves to the work location. In one embodiment, when the vehicle is in the work location moving state S8, if the vehicle reaches the work location, the state of the vehicle can switch to the end-of-duty state S9.
[0067] Each state shown in FIG. 4 is provided as an example, and the state of the demand-type vehicle may be arbitrarily and appropriately configured according to the type of the demand-type vehicle, the characteristics of the route, and the operation method other than those shown, and some of the states shown may be omitted. As an example, if the demand-type vehicle is a public bus, the dispatch waiting state S3 may not exist, and the boarding location moving state S4 and the disembarking location moving state S5 may be the same state. As another example, if the driver's work plan does not include a rest plan, the rest location moving state S6 and the rest state S7 may not exist.
[0068] Also, the transitions between vehicle states, depicted as arrows in Figure 4, may occur differently than shown. As an example, if a trip assignment is canceled in the boarding location moving state S4, the vehicle may immediately switch to the waiting for dispatch state S3 rather than switching to the disembarking location moving state S5.
[0069] The following describes the connection process for vehicle operation as a preparatory task that the driver must perform before operating the vehicle.
[0070] In the present disclosure, the connection process for vehicle operation may be performed via a connection device for vehicle operation, and the connection device for vehicle operation may refer to a device in which onboard driver software is installed.
[0071] In the present disclosure, a connection process for vehicle operation may refer to a process in which a driver connects his / her own device to a vehicle so that the vehicle can be used to provide a demand-based transportation service. The connection process for vehicle operation may include a process for verifying or registering whether a demand-based vehicle or a driver who rides in the vehicle is suitable to provide a demand-based transportation service, whether the vehicle was scheduled to provide a demand-based transportation service, etc.
[0072] According to a connection process for vehicle operation according to an embodiment of the present disclosure, the device connected to or installed in the demand-type vehicle does not necessarily have to be a device verified or distributed by the control server, and the on-board driver can connect a device in which the on-board driver software is installed to the demand-type vehicle and use the vehicle for on-demand transportation services. In addition, when a device already connected to the demand-type vehicle (or a part of the device of the demand-type vehicle) breaks down, an emergency situation can be flexibly dealt with as long as there is a device in which the on-board driver software is installed.
[0073] FIG. 5 is a diagram illustrating a connection process for vehicle operation according to an embodiment.
[0074] Referring to FIG. 5, in the present disclosure, the connection process for vehicle operation may proceed by transmitting and receiving signals or data between a passenger entity 510, a connection device for vehicle operation 520, a vehicle management system for an operator 530, a control server 540, or a vehicle management server 550.
[0075] The on-board entity 510 in FIG. 5 may correspond to the on-board driver of the present disclosure.
[0076] In FIG. 5, the operator vehicle management system 530 may be a vehicle service provider (e.g., a vehicle operating corporation) that operates demand-based transportation, a device used by the vehicle service provider that operates demand-based transportation, or a digital interface provided for management purposes such as a web page or mobile app used by the vehicle service provider that operates demand-based transportation.
[0077] In FIG. 5, the vehicle management server 550 can play a role of managing a fleet including vehicles, and can manage pure data of the fleet, such as vehicle ID, vehicle manufacturer, number of passengers, vehicle type, etc. Meanwhile, the control server 540 in FIG. 5 can be a server that controls the operation of the fleet. The control server 540 can manage data such as vehicle dispatch, service users (customers), and vehicle operation status. That is, the vehicle management server 550 can play a role of managing mobility services, and the control server 540 can play a role of operating the mobility services.
[0078] In one embodiment, the vehicle management server 550 may be the same as the control server 540 or may be configured as part of the control server 540 .
[0079] According to an embodiment, the connection process for driving a vehicle may be performed after a passenger 510 connects a connection device 520 for driving a vehicle to the vehicle.
[0080] Referring to FIG. 5, in step 5001, the connection device 520 for vehicle operation may request the onboard entity 510 to input a first identifier in response to the connection device 520 for vehicle operation being connected to the vehicle.
[0081] Referring to FIG. 5, in step 5002, a passenger entity 510 may input a first identifier into a connection device 520 for vehicle operation.
[0082] In the present disclosure, the first identifier may correspond to vehicle service provider information. That is, the first identifier may be an identifier that can identify a company, corporation, business, etc. that provides or operates a vehicle service, such as a corporate ID or a business registration number.
[0083] Referring to FIG. 5, in step 5003, the connection device 520 for vehicle operation may request the vehicle management server 550 to verify the first identifier and register the backup connection device in response to the input of the first identifier by the onboard entity 510.
[0084] Referring to FIG. 5, in step 5004, the vehicle management server 550 may transmit a signal indicating completion of verification of the first identifier and completion of registration of the backup connection device to the connection device 520 for vehicle operation.
[0085] Referring to FIG. 5, in step 5005, in response to receiving a signal indicating completion of verification for the first identifier and completion of registration of the backup connection device, the connection device 520 for vehicle operation may determine that verification for the first identifier is completed and may request the onboard entity 510 to input a second identifier.
[0086] 5, in step 5006, the business operator's vehicle management system 530 can request the first identifier backup device list from the control server 540. In step 5007, the control server 540 can forward the request for the first identifier backup device list to the vehicle management server 550 in response to receiving the request for the first identifier backup device list.
[0087] 5, in step 5008, the vehicle management server 550 can return the first identifier backup connection device list to the control server 540 in response to the request for the first identifier backup connection device list. In step 5009, the control server 540 can transfer the first identifier backup connection device list to the operator's vehicle management system 530 in response to receiving the first identifier backup connection device list. The operator's vehicle management system 530 can match a connection device to a registered vehicle in response to receiving the first identifier backup connection device list.
[0088] 5, in step 5010, the business vehicle management system 530 can match the connection device with the registered vehicle and then request the registered vehicle to register the connection device. In response to receiving the connection device registration request from the registered vehicle, the control server 540 can verify the registered vehicle.
[0089] 5, in step 5011, after verifying the registered vehicle, the control server 540 can request the registered vehicle to register a connection device. In response to receiving the connection device registration request from the registered vehicle, the vehicle management server 550 can generate a second identifier.
[0090] In the present disclosure, the second identifier may correspond to device identification information. Through verification of the second identifier, it can be determined whether the device that is attempting to connect to the demand-based transportation system and provide service is a compatible device, and it can also be determined which functions and interfaces to activate.
[0091] In addition, in the present disclosure, the second identifier may correspond to service-specific information. The on-board driver software (e.g., application) installed in the connection device for driving the vehicle may include various functions or services, and the second identifier may be a basis for determining which of various types of services to provide and for determining the function corresponding to the service to be provided.
[0092] 5, in step 5012, after generating the second identifier, the vehicle management server 550 can return the second identifier to the control server 540. In step 5013, in response to receiving the second identifier, the control server 540 can forward the second identifier to the operator's vehicle management system 530. In step 5014, in response to receiving the second identifier, the operator's vehicle management system 530 can forward the second identifier to the boarding entity 510.
[0093] In one embodiment, steps 5006 through 5014 may be performed independently or simultaneously with step 5005.
[0094] 5, in step 5015, the boarding entity 510 that receives the second identifier by receiving the second identifier input request may input the second identifier into the connection device 520 for vehicle operation. For example, the boarding entity 510 may check the second identifier received via a personal terminal and input the second identifier into the connection device 520 for vehicle operation.
[0095] 5, in step 5016, the connection device 520 for vehicle operation may request the vehicle management server 550 to verify the second identifier and complete the vehicle registration in response to receiving the second identifier input. The vehicle management server 550 may register the device to the already registered vehicle in response to receiving the request to verify the second identifier and complete the vehicle registration.
[0096] 5, in step 5017, the vehicle management server 550 may transmit a signal indicating completion of verification of the second identifier and completion of backup device registration to the connection device 520 for vehicle operation after registering the device to the already registered vehicle. In one embodiment, the signal indicating completion of verification of the second identifier and completion of backup device registration may include an access token for communication. The access token for communication may mean authority for the connection device 520 for vehicle operation to access the demand-based transportation system to provide a service.
[0097] 5, the connection device 520 for vehicle operation may activate interfaces corresponding to the first identifier and the second identifier in response to receiving a signal indicating completion of verification of the second identifier and completion of backup device registration. The connection device 520 for vehicle operation may provide the activated interfaces to the boarding entity 510.
[0098] In one embodiment, the connection device 520 for vehicle operation may request the onboard entity 510 to re-enter the first identifier if it receives a signal indicating a failure in verification of the first identifier.
[0099] In one embodiment, the connection device 520 for vehicle operation may request the onboard entity 510 to input the second identifier again when the connection device 520 for vehicle operation receives a signal indicating that the verification of the second identifier has failed. In another embodiment, the connection device 520 for vehicle operation may request the onboard entity 510 to input the first identifier again when the connection device 520 for vehicle operation receives a signal indicating that the verification of the second identifier has failed.
[0100] The connection device 520 for vehicle operation has on-board driver software installed, and the installed on-board driver software may be implemented for all on-board drivers, vehicle service providers, and service types included in the on-demand transportation system, without differing depending on on-board drivers, vehicle service providers, and service types. However, for efficient and effective on-demand vehicle operation, it may be desirable to provide functions or interfaces that are suitable for on-board drivers, vehicle service providers, and service types. Thus, through a process of activating a corresponding interface, only the suitable functions or interfaces may be activated and provided in the software including various functions or interfaces.
[0101] In one embodiment, the interface activated and provided by the connection device 520 for vehicle operation may be the interface displayed in the pre-work state described above.
[0102] 6A and 6B are exemplary diagrams illustrating interfaces that may be displayed during a connection process for vehicle operation according to an embodiment.
[0103] As shown in Figures 6A and 6B, in the connection process for vehicle operation described with reference to Figure 5, an interface suitable for requesting input from the on-board driver and for the on-board driver to input data may be provided by the connection device for vehicle operation.
[0104] 6A , in one embodiment, in the process of receiving an input of a first identifier from a driver, a connection device for vehicle operation may display a first identifier input interface 610. As shown, the first identifier input interface 610 may include a first message display area 601, a first input data display area 602, and a first data input interface 603.
[0105] In the present disclosure, the first message display area 601 may refer to an area for displaying various messages including a message for informing the driver of what action to take. In particular, the first message display area 601 may be an area for displaying a message required for the driver during the input and verification process of the first identifier.
[0106] In the present disclosure, the first input data display area 602 may refer to an area configured to allow the on-board driver to check the data entered. In particular, the first input data display area 602 may be a means by which the on-board driver who enters the first identifier can check for himself or herself whether the input is correct.
[0107] In the present disclosure, the first data input interface 603 may refer to an interface including objects for the on-board driver to input data. In one embodiment, the first data input interface 603 may be configured to include only objects required according to the configuration method of the first identifier (e.g., configured with Hangul only, configured with English only, configured with English and numbers, etc.).
[0108] In one embodiment, the connection device for vehicle operation may configure a first message display area 601, a first input data display area 602, and a first data input interface 603, respectively, and generate a first identifier input interface 610 including the configured first message display area 601, the first input data display area 602, and the first data input interface 603. In one embodiment, the connection device for vehicle operation may display the generated first identifier input interface 610 to provide it to a driver on board.
[0109] 6A is a diagram showing a process in which a driver inputs a first identifier through a first identifier input interface 610. As shown, interfaces suitable for various situations that may occur in the process of verifying the first identifier can be displayed.
[0110] Specifically, in a process in which the connection device for vehicle operation receives an input of the first identifier from the onboard driver, the connection device for vehicle operation may display a first identifier input waiting message in the first message display area 601. For example, the first identifier input waiting message may include a message waiting for completion of input of the first identifier, such as "Please enter your business registration number" or "Please enter your corporate ID."
[0111] In response to this, the on-board driver can interact with the first data input interface 603 to input the first identifier, and the connection device for vehicle operation can display input data related to the input first identifier in the first input data display area 602.
[0112] The first data input interface 603 may include an object for completing the input (e.g., an Enter key type object), and the on-board driver may interact with the object for completing the input to generate a first identifier input completion signal.
[0113] In response to receiving the first identifier input completion signal, the connection device for vehicle operation may transmit input data related to the first identifier inputted until the first identifier input completion signal is received to the control server. Also, the connection device for vehicle operation may transmit information of a driver on board or information of a vehicle together with the input data related to the first identifier, and may request verification of the first identifier based on the transmission.
[0114] In one embodiment, the verification result is generally verification failure or verification success, and the connection device for vehicle operation can generate the first identifier input interface 610 according to a signal according to the verification result.
[0115] For example, if the transmitted input data related to the first identifier is not included in the data list stored in the control server or the vehicle management server, i.e., if the data is not vehicle service provider information registered in the control server, the connection device for vehicle operation may display an unregistered corporation message in the first message display area 601. For example, the unregistered corporation message may include a message such as "unregistered business" or "unregistered corporation" to indicate that the vehicle service provider is not a registered vehicle service provider.
[0116] For example, if the connection device for vehicle operation from the control server is successful in the verification, the connection device for vehicle operation may display a first identifier verification completion message in the first message display area 601. For example, the first identifier verification completion message may include a message indicating that the verification of the first identifier has been successfully completed, such as "Verification is completed" or "Proceed to the next step."
[0117] 6B , in one embodiment, in the process in which the connection device for vehicle operation receives the input of the second identifier from the onboard driver, a second identifier input interface 620 may be displayed. As shown, the second identifier input interface 620 may include a second message display area 604, a second input data display area 605, and a second data input interface 606.
[0118] In the present disclosure, the second message display area 604 may refer to an area for displaying various messages including messages for informing the on-board driver of what action to take, similar to the first message display area 601. In particular, the second message display area 604 may be an area for displaying messages required for the on-board driver during the process of inputting and verifying the second identifier.
[0119] In the present disclosure, the second input data display area 605 may refer to an area configured to allow the on-board driver to check the data entered, similar to the first input data display area 602. In particular, the second input data display area 605 may be a means by which the on-board driver who enters the second identifier can check for himself or herself whether the input has been made correctly.
[0120] In this disclosure, the second data input interface 606 may refer to an interface including objects for the on-board driver to input data, similar to the first data input interface 603. In one embodiment, the second data input interface 606 may be configured to include only objects required according to the configuration method of the second identifier (e.g., configured with Hangul only, configured with English only, configured with English and numbers, etc.).
[0121] In one embodiment, the connection device for vehicle operation may configure a second message display area 604, a second input data display area 605, and a second data input interface 606, respectively, and generate a second identifier input interface 620 including the configured second message display area 604, the second input data display area 605, and the second data input interface 606. In one embodiment, the connection device for vehicle operation may display the generated second identifier input interface 620 to provide it to a driver on board.
[0122] 6B is a diagram showing a process in which the driver inputs the second identifier via the second identifier input interface 620. As shown, interfaces suitable for various situations that may occur in the process of verifying the second identifier can be displayed.
[0123] Specifically, in a process in which the connection device for vehicle operation receives an input of the second identifier from the on-board driver, the connection device for vehicle operation may display a second identifier input waiting message in the second message display area 604. For example, the second identifier input waiting message may include a message waiting for completion of the input of the second identifier, such as "Please enter the secret code" or "Please enter the authentication number."
[0124] Correspondingly, the on-board driver can interact with the second data input interface 606 to input the second identifier, and the connection device for vehicle operation can display input data related to the input second identifier in the second input data display area 605.
[0125] The second data input interface 606 may include an object for completing the input (e.g., an Enter key type object), and the on-board driver may interact with the object for completing the input to generate a second identifier input completion signal.
[0126] In response to receiving the second identifier input completion signal, the connection device for vehicle operation may transmit input data related to the second identifier inputted until the second identifier input completion signal is received to the control server. The connection device for vehicle operation may request verification of the second identifier based on the transmission.
[0127] In one embodiment, the verification result may be largely a verification failure or a verification success. The connection device for vehicle operation may generate a second identifier input interface 620 according to a signal according to the verification result.
[0128] For example, if the input data related to the transmitted second identifier does not match the generated second identifier, the connection device for vehicle operation may display a unique code mismatch message in the second message display area 604. For example, the unique code mismatch message may include a message indicating that the second identifier has been entered incorrectly, such as "The secret code is incorrect" or "The authentication number is incorrect."
[0129] For example, if the input data related to the transmitted second identifier matches the unique code, the connection device for vehicle operation may display a verification completion message of the second identifier in the second message display area 604. For example, the verification completion message of the second identifier may include a message indicating that the verification of the second identifier has been successfully completed, such as "Verification completed" or "Device connection completed."
[0130] The process of providing a demand-based vehicle operation after a connection for vehicle operation is completed will be described below.
[0131] As described above, the demand-based vehicle may include a driver information providing device, a passenger information providing device, a vehicle exterior display device, etc. The driver information providing device may be the same as or a corresponding device to the connection device for vehicle operation described above.
[0132] In the present disclosure, in the process of providing operation of a demand-based vehicle, the information providing device for drivers may perform a process of determining a main interface for displaying information related to the vehicle operation service and generating the determined main interface.
[0133] First, until a trip is assigned to a demand-based vehicle, the main interface can be broadly determined as a pre-work interface, a work location transfer interface, or a vehicle dispatch waiting interface.
[0134] In one embodiment, the pre-work interface, the work location moving interface, and the vehicle dispatch waiting interface may include a driving route interface. The driving route interface may also be generated by a driver information providing device, and the driver information providing device may generate the driving route interface based on received or collected information.
[0135] FIG. 7 is an example diagram illustrating a driving route interface according to one embodiment.
[0136] In this disclosure, the driving route interface 700 may refer to an interface that displays the environment around the vehicle in which the driver information device is installed (hereinafter, the term "own vehicle" refers to the vehicle in which the driver information device is installed, as opposed to other vehicles).
[0137] In one embodiment, the driving route interface 700 may include an icon corresponding to the host vehicle. The icon corresponding to the host vehicle may be based on information of the vehicle. For example, if the host vehicle is a passenger car, the icon corresponding to the host vehicle may be a passenger car type icon, and if the host vehicle is a bus, the icon corresponding to the host vehicle may be a bus type icon.
[0138] In one embodiment, the driving route interface 700 may include lanes. In one embodiment, the lanes may be generated based on road information received based on the position information of the host vehicle. In one embodiment, the lanes may be generated based on lane information around the host vehicle recognized from a sensor mounted on the host vehicle.
[0139] In one embodiment, the driving route interface 700 may include icons corresponding to other vehicles around the host vehicle. In one embodiment, the shape of the icon corresponding to the other vehicle may be determined based on information of the other vehicle. In one embodiment, the position of the icon corresponding to the other vehicle may be determined based on position information of the other vehicle relative to the host vehicle. In one embodiment, the information of the other vehicle or the position information of the other vehicle may be recognized from a sensor mounted on the host vehicle. The driver information providing device may place the icon corresponding to the other vehicle at a relative position of the other vehicle relative to the host vehicle.
[0140] In one embodiment, the driving route interface 700 may include an icon corresponding to a pedestrian around the host vehicle. In one embodiment, the position information of the pedestrian can be recognized from a sensor mounted on the host vehicle. The driver information providing device can place the icon corresponding to the pedestrian at a relative position of another vehicle with respect to the host vehicle.
[0141] The driver information providing device can generate an icon corresponding to the host vehicle, an icon corresponding to a lane, an icon corresponding to another vehicle, or an icon corresponding to a pedestrian, and can generate a driving route interface 700 by arranging the icon corresponding to the host vehicle, the icon corresponding to the lane, the icon corresponding to another vehicle, or the icon corresponding to a pedestrian at the center based on the received or collected information.
[0142] In one embodiment, the driving route interface 700 may display vehicles that may affect driving in a different way from other vehicles. For example, an icon corresponding to a vehicle located in front of the vehicle may be displayed in red. For example, if the vehicle needs to change lanes to the outside lane to stop at a bus stop along the road, an icon corresponding to a vehicle close to the left side of the vehicle may be displayed in red.
[0143] In one embodiment, the information providing device for driver may set a critical distance and generate icons corresponding to only other vehicles or pedestrians within the critical distance range based on the own vehicle to generate the driving route interface 700. For example, the information providing device for driver may generate the driving route interface 700 only with icons corresponding to other vehicles or pedestrians within a range of 10 m based on the own vehicle. For example, the critical distance may be set by a control server or a driver on board.
[0144] FIG. 7 illustrates an example driving route interface 700 in which an icon corresponding to the host vehicle 710 is centered around icons of the lanes surrounding the host vehicle 710, several other vehicles, and pedestrians.
[0145] As described above, the pre-work interface, the work location transfer interface, and the vehicle dispatch waiting interface may include a driving route interface.
[0146] FIG. 8 is an exemplary diagram illustrating a before-work interface generated according to one embodiment.
[0147] In the present disclosure, the information providing device for driver may determine the main interface as a pre-work interface in response to the state of the vehicle being a pre-work state. Alternatively, since the state of the vehicle being a pre-work state is an initial stage after completing a connection process for vehicle operation, the information providing device for driver may determine the main interface as a pre-work interface as an initial stage. The information providing device for driver may generate a pre-work interface in response to determining the main interface as the pre-work interface.
[0148] Referring to FIG. 8, a pre-work interface 800 generated according to one embodiment is shown.
[0149] In one embodiment, the pre-attend interface 800 may include the driving route interface 810 described above, an interface 820 including on-board driver information or vehicle information, an attendance authentication interface 830, or an autonomous driving function status interface 840.
[0150] In one embodiment, the interface 820 including on-board driver information or vehicle information may be generated based on on-board driver information and vehicle information included in the driver information device.
[0151] In one embodiment, the clock-in authentication interface 830 may include objects with which the on-board driver may interact. When the on-board driver interacts with an object included in the clock-in authentication interface 830, a clock-in authentication signal may be generated. In one embodiment, the generated clock-in authentication signal may be transmitted to a control server.
[0152] In the present disclosure, autonomous driving function status interface 840 may refer to an interface that displays the operation status of one or more devices, functions, etc. related to autonomous driving that are installed to realize autonomous driving of a vehicle. Referring to FIG. 8, autonomous driving function status interface 840 can display whether one or more devices, functions, etc. related to autonomous driving are operating normally via indicator lights for each of the one or more devices, functions, etc. related to autonomous driving. This is provided merely as an example, and any suitable manner capable of displaying the operation status of a device, function, etc. may be applied.
[0153] In one embodiment, the pre-attend interface 800 may further include an attendance authentication guidance message. For example, the attendance authentication guidance message may include a message such as "Press the attendance button" to suggest to the driver to perform attendance authentication.
[0154] In one embodiment, in response to a clock-in authorization signal being received, the state of the vehicle may switch to a work location transfer state.
[0155] FIG. 9 is an exemplary diagram illustrating a work location mobility interface generated according to one embodiment.
[0156] In the present disclosure, the driver information providing device can determine a main interface in the workplace moving interface in response to the state of the vehicle switching to the workplace moving state. The driver information providing device can generate a workplace moving interface in response to determining the main interface in the workplace moving interface.
[0157] Referring to FIG. 9, a work location mobility interface 900 generated according to one embodiment is shown.
[0158] In one embodiment, the workplace mobility interface 900 may include the driving route interface 910 described above, a route guidance interface 920 configured to include information about the destination, a navigation map, and driving directions, or an automated driving functionality status interface 930.
[0159] In one embodiment, the route guidance interface 920 may be generated based on information about the destination, vehicle position information, road information based on the vehicle position information, information about traffic volume, and the like.
[0160] In one embodiment, the destination may be set automatically. For example, the driver information providing device may set an arbitrary point of a workplace as the destination. For example, the driver information providing device may set a point on a predefined automated driving route that is closest to the vehicle's location as the destination. In this way, a driver who has completed attendance authentication can immediately operate the vehicle at the workplace or on the automated driving route.
[0161] In one embodiment, information about a destination may include a name, an estimated time of arrival, or a remaining distance.
[0162] In one embodiment, in response to the vehicle's position reaching a destination, i.e., entering an automated driving route from a general driving route, the vehicle's state may be switched to a dispatch waiting state.
[0163] In one embodiment, in response to the vehicle's position reaching a destination, i.e., entering an autonomous driving route from a general driving route, the vehicle's driving mode may be switched to an autonomous driving mode.
[0164] FIG. 10 is an exemplary diagram illustrating a ride waiting interface generated according to one embodiment.
[0165] In the present disclosure, the information providing device for driver can determine a main interface in the vehicle dispatch standby interface in response to the state of the vehicle switching to a vehicle dispatch standby state, and can generate a vehicle dispatch standby interface in response to determining the main interface in the vehicle dispatch standby interface.
[0166] Referring to FIG. 10, a vehicle waiting interface 1000 generated according to one embodiment is shown.
[0167] In one embodiment, the vehicle dispatch waiting interface 1000 may include the driving route interface 1010, the route guidance interface 1020, the notification interface 1030, or the automated driving feature status interface 1040 described above.
[0168] In one embodiment, the route guidance interface 1020 may include a navigation map. In one embodiment, the route guidance provided to the route guidance interface 1020 may be guidance for a predefined route. For example, the predefined route may be a work location or an automated driving route. Additionally, the predefined route may be a circular route with the same start and end location. In such a case, if the vehicle is not assigned to a trip, the vehicle will be operated on the circular route.
[0169] In one embodiment, the notification interface 1030 may include various notifications related to the vehicle's trip assignment. For example, as shown, the notification interface 1030 may include a message that the vehicle is waiting for dispatch. For example, the notification interface 1030 may include the nearest pickup location on the route. For example, the notification interface may include a message that the vehicle is self-driving.
[0170] In one embodiment, the process of the driver information providing device determining and displaying the main interface as the workplace movement interface may be omitted. For example, when the driver on board performs attendance authentication at the workplace or on the automatic driving route, the vehicle state may be switched to a dispatch standby state by skipping the workplace movement state, and in this case, the process related to the workplace movement interface may be omitted.
[0171] In one embodiment, the main interface displayed on the driver information providing device may include a conditionally activated object. The conditionally activated object refers to an object that is activated only when a predefined condition is met and that the on-board driver can interact with. The conditionally activated object may be displayed in a non-activated main interface when the predefined condition is not met.
[0172] The predefined condition may relate to a condition under which the vehicle will not be endangered if the on-board driver interacts with an object included in the driver information providing device. For example, the predefined condition may be a condition related to the speed of the vehicle. For example, the condition activation object may be activated only if the current speed value of the vehicle is zero. For example, the predefined condition may be a condition related to the state of the vehicle. For example, the condition activation object may be activated only if the state of the vehicle is a waiting state, a resting state, or a pre-work state.
[0173] In one embodiment, the driver information system may display a driver menu interface when the on-board driver interacts with a condition activation object.
[0174] In one embodiment, the driver menu interface may include one or more objects with which the on-board driver can interact, and the on-board driver may interact with the corresponding objects to receive on-board driver information, vehicle information, driving history, on-board driver work history, on-board driver work plan, notices received from the control server (or vehicle management server), information such as settings of the driver information providing device, terms and conditions and policies, on-board driver manual, etc. For example, the on-board driver may interact with an object corresponding to notices to check notices received from the control server.
[0175] A demand-based vehicle is not eligible for service assignment until the vehicle is in a dispatch standby state. A process of providing service to a demand-based vehicle after the vehicle is assigned will be described later with reference to FIGS. 11 and 12.
[0176] As mentioned above, various vehicle conditions may include rest-related conditions.
[0177] When the demand vehicle is in operation and there is little time left until the scheduled rest time, the driver information providing device can inform the driver that there is not much time left until the scheduled rest time and provide information related to the rest.
[0178] In the present disclosure, when the remaining time until the scheduled rest time reaches a first hour, the driver information providing device can display a rest guidance interface.
[0179] In one embodiment, the first time may be any suitable time such as 5 minutes, 10 minutes, 20 minutes, etc., and in one embodiment, the first time may be a time set by the on-board driver, the corporation to which the on-board driver belongs (vehicle service provider), or the control server.
[0180] In one embodiment, the break guidance interface is an interface that informs the driver that there is little time left for a scheduled break, and may include a message such as "Your break is scheduled in 10 minutes."
[0181] In the present disclosure, after the driver information providing device displays the rest guide interface, if the vehicle state is a dispatch waiting state, the vehicle state may immediately switch to a rest location movement state. On the other hand, if the vehicle state is a driving state, the vehicle state may switch to a rest location movement state after receiving a driving end signal. In one embodiment, if the remaining time until the scheduled rest time is less than or equal to the first hour but the vehicle state is a driving state, the vehicle may switch to a state not receiving additional dispatch.
[0182] In the present disclosure, the information providing device for driver may determine a main interface in the rest area movement interface in response to the state of the vehicle switching to the rest area movement state, and may generate a rest area movement interface in response to determining the main interface in the rest area movement interface.
[0183] In the present disclosure, the rest location moving interface may be similar to the work location moving interface 900 described above with reference to Figure 9. That is, the rest location moving interface may include a driving route interface and a route guidance interface configured to include information about a destination, a navigation map, and driving method guidance, except that the destination in the embodiment of the rest location moving interface may be set to a rest location.
[0184] In one embodiment, when the vehicle's position reaches a destination, i.e., a rest stop, the vehicle's state may switch to a rest state.
[0185] In the present disclosure, when the vehicle state is in a rest state, if the remaining time until the scheduled post-break work time reaches a second hour, the driver information providing device can display a rest end guidance interface.
[0186] In one embodiment, the second time may be any suitable time such as 5 minutes, 10 minutes, 20 minutes, etc., and in one embodiment, the second time may be a time set by the on-board driver, the corporation to which the on-board driver belongs (vehicle service provider), or the control server.
[0187] In one embodiment, the break end notification interface is an interface that notifies the driver that there is not much time left to end the break, and may include a message such as "The break is scheduled to end in 10 minutes."
[0188] In the present disclosure, when the remaining time until the scheduled post-break work time reaches zero, the vehicle state can be switched to a vehicle dispatch waiting state. Similarly, the driver information providing device can determine a main interface at the vehicle dispatch waiting interface in response to the vehicle state switching to the vehicle dispatch waiting state.
[0189] In the present disclosure, when the remaining time until the end of shift reaches a third hour, the driver information providing device can display an end of shift guidance interface.
[0190] In one embodiment, the third time may be any suitable time such as 5 minutes, 10 minutes, 20 minutes, etc., and in one embodiment, the third time may be a time set by the on-board driver, the corporation to which the on-board driver belongs (vehicle service provider), or the control server.
[0191] In one embodiment, the end-of-shift notification interface is an interface that notifies the driver that there is not much time left until the end of the shift, and may include a message such as "Your shift is scheduled to end in 10 minutes."
[0192] In the present disclosure, after the driver information providing device displays the end-of-shift guidance interface, if the vehicle state is in a dispatch waiting state, the vehicle state may immediately switch to a scheduled clock-out state. Meanwhile, if the vehicle state is in a running state, the vehicle state may switch to a scheduled clock-out state after receiving an operation end signal. In one embodiment, if the remaining time until the end of shift is less than or equal to a third hour but the vehicle state is in a running state, the vehicle may switch to a state in which it does not receive additional dispatches.
[0193] In the present disclosure, in response to the time remaining until the end of the shift reaching zero, the state of the vehicle may switch to a work stop state.
[0194] In one embodiment, the driver information providing device may determine a main interface in the leave location moving interface in response to the state of the vehicle switching to the leave location moving state. The driver information providing device may generate a leave location moving interface in response to determining the main interface in the leave location moving interface.
[0195] In the present disclosure, the leave location transfer interface may be similar to the work location transfer interface 900 described above with reference to Figure 9. That is, the leave location transfer interface may include a driving route interface and a route guidance interface configured to include information about a destination, a navigation map, and driving method guidance, except that the destination in the leave location transfer interface embodiment may be set to a leave location.
[0196] In one embodiment, when the vehicle location reaches the destination, i.e., the off-duty location, the vehicle state may switch to an off-duty state.
[0197] The following describes a process in which a demand-based vehicle is provided with respect to passenger boarding and disembarking after a vehicle is assigned to operate.
[0198] In the present disclosure, when the vehicle's status is awaiting dispatch, the vehicle may be assigned to operate, i.e., when the vehicle's status is awaiting dispatch, the vehicle may receive a dispatch request signal.
[0199] In one embodiment, in response to a ride request signal being received, the state of the vehicle may switch to a pick-up transfer state.
[0200] FIG. 11 is an exemplary diagram illustrating a ride location transfer interface generated according to one embodiment.
[0201] In the present disclosure, the driver information providing device can determine a main interface in the boarding location movement interface in response to the state of the vehicle switching to the boarding location movement state. The driver information providing device can generate a boarding location movement interface in response to determining the main interface in the boarding location movement interface.
[0202] Referring to FIG. 11, a pickup location transfer interface generated according to one embodiment is shown.
[0203] In one embodiment, the pickup location movement interface 1100 may include the driving route interface 1110 described above, a route guidance interface 1120 configured to include information about the destination, a navigation map, and driving directions, or an automated driving function status interface 1130.
[0204] In one embodiment, the destination may be a pickup location that is automatically set based on information included in the ride request signal.
[0205] In one embodiment, information about a destination may include a name, an estimated time of arrival, or a remaining distance.
[0206] In one embodiment, even if the vehicle is not in a dispatch standby state, the dispatch request signal can be received. For example, if the vehicle is a vehicle that can only travel on a predetermined route and the new destination included in the new dispatch request signal is on the predetermined route, the new dispatch request signal can be received. In this embodiment, when the new destination included in the new dispatch request signal arrives before the existing destinations on the predetermined route, this can be called a waypoint addition situation. On the other hand, when the new destination included in the new dispatch request signal arrives after the existing destinations on the predetermined route, this can be called a waypoint addition situation. In either case, if a new destination is added by the new dispatch request signal, each destination can be called a waypoint destination.
[0207] In one embodiment, when a new dispatch request signal is received, the information on the destination can be updated based on the information on the existing destination and the information on the new destination included in the new dispatch request signal. In one embodiment, in response to the information on the destination being updated, the driver information providing device can display a notification message regarding the update.
[0208] In one embodiment, when a destination includes multiple intermediate destinations, the information on the destination included in the route guidance interface 1120 can be displayed by switching between information on the first intermediate destination among the multiple intermediate destinations and information on the next intermediate destination according to a predetermined cycle. For example, the driver information providing device can display information on the first intermediate destination for four seconds, and then display information on the next intermediate destination for two seconds.
[0209] When the state of the vehicle is a boarding location moving state, the state of the vehicle can be switched to a disembarking location moving state when the vehicle arrives at the boarding location and boards the passenger. There are several possible embodiments in the process of the state of the vehicle switching from the boarding location moving state to the disembarking location moving state.
[0210] In one embodiment, when the distance between the vehicle and the destination (boarding location) is equal to or less than the first critical distance, the driver information device may display an arrival notification message. In one embodiment, in response to the distance between the vehicle and the destination (boarding location) being equal to or less than the first critical distance, the driver information device may display a boarding location arrival completion object. The boarding location arrival completion object may refer to an object with which the boarding driver interacts to generate a boarding location arrival completion signal. The first critical distance may be arbitrarily set to a value suitable for notifying that the destination has almost been reached, such as 50 m, 100 m, or 150 m.
[0211] In one embodiment, in response to interacting with the boarding arrival completion object, the driver information providing device can display a ride completion object. The ride completion object can refer to an object for the boarding driver to interact with to generate a ride completion signal. In one embodiment, in response to interacting with the ride completion object, a ride completion signal can be generated, and in response to receiving the ride completion signal, the state of the vehicle can switch to a drop-off transfer state.
[0212] In one embodiment, in response to interacting with the boarding location arrival completion object, the driver information providing device may display a timer. The timer may countdown a predetermined time. In the present disclosure, the vehicle may provide a smooth on-demand transportation system by canceling dispatch when a predetermined time has elapsed without a passenger boarding the vehicle, rather than waiting at the boarding location until the passenger boards. That is, if a boarding completion signal is not received until the predetermined time has elapsed, the state of the vehicle may switch to a dispatch waiting state. The predetermined time may be arbitrarily set to a value suitable for providing a smooth on-demand transportation system, such as, for example, 3 minutes, 5 minutes, or the like.
[0213] In the present disclosure, the driver information providing device can determine a main interface in the drop-off location movement interface in response to the state of the vehicle switching to the drop-off location movement state. The driver information providing device can generate a drop-off location movement interface in response to determining the main interface in the drop-off location movement interface.
[0214] In the present disclosure, the drop-off location movement interface may be the same as the boarding location movement interface 1100 described above with reference to FIG. 11. That is, the drop-off location movement interface may include a route guidance interface 1120 configured to include information on a driving route interface or a destination, a navigation map, and a driving method guide. In this case, the destination may be automatically set as a drop-off location based on information included in the dispatch request signal. Other than this, the embodiments related to the boarding location movement interface described above may be applied in the same manner.
[0215] When the vehicle state is in the drop-off location moving state, the vehicle state can be switched to the dispatch waiting state when the vehicle arrives at the drop-off location and drops off the passengers. There are several possible embodiments in the process of the vehicle state switching from the drop-off location moving state to the dispatch waiting state.
[0216] In one embodiment, when the distance between the vehicle and the destination (drop-off location) is equal to or less than the second critical distance, the driver information providing device may display an arrival notification message. In one embodiment, in response to the distance between the vehicle and the destination (drop-off location) being equal to or less than the second critical distance, the driver information providing device may display a drop-off location arrival completion object. The drop-off location arrival completion object may refer to an object for the on-board driver to interact with to generate a drop-off location arrival completion signal. The second critical distance may be arbitrarily set to a value suitable for notifying that the destination has almost been reached, such as 50m, 100m, 150m, etc. The second critical distance may be the same as or different from the first critical distance.
[0217] In one embodiment, in response to interacting with the drop-off arrival completion object, the driver information providing device may display a drop-off completion object. The drop-off completion object may refer to an object for the on-board driver to interact with to generate a drop-off completion signal. In one embodiment, in response to interacting with the drop-off completion object, a drop-off completion signal may be generated, and in response to receiving the drop-off completion signal, the state of the vehicle may switch to a waiting state.
[0218] In one embodiment, there may be a plurality of driving modes. The plurality of driving modes may include an autonomous driving mode and a manual driving mode. In one embodiment, the vehicle may be switched to the autonomous driving mode by an operation of an on-board driver. In one embodiment, the vehicle may be switched to the autonomous driving mode on an autonomous driving route, which is a route where autonomous driving is possible.
[0219] In one embodiment, when the vehicle enters a compulsory manual driving area where the vehicle cannot be driven in the demand-type autonomous driving mode, the driver information providing device may display a message requesting switching to the manual driving mode. The message requesting switching to the manual driving mode may include a message requesting the onboard driver to switch to the manual driving mode, such as "Please switch to the manual driving mode."
[0220] In one embodiment, the mandatory manual driving zone may include a child protection zone.
[0221] In one embodiment, if the vehicle is in a mandatory manual driving zone, the vehicle cannot be switched to autonomous driving mode by the on-board driver.
[0222] In one embodiment, when the driving mode of the vehicle is switched, the driver information providing device may display a driving mode switching message. The driving mode switching message may include a message that the driving mode has been switched, such as "Switched to manual driving mode" or "Switched to automatic driving mode."
[0223] FIG. 12 is an exemplary diagram illustrating a seat information interface generated according to one embodiment.
[0224] In one embodiment, the boarding location transfer interface may further include a seat information interface 1200. For example, if the vehicle is a jitney, the passengers are also assigned seats to sit in the vehicle, and the seat information interface 1200 may be an interface for displaying information regarding the assigned seats accordingly.
[0225] Referring to FIG. 12, a seat information interface 1200 is shown that includes objects corresponding to a number of seats 1C, 2A, 3A, 3C, 4A, 4B, and 4C, including an onboard driver seat 1210.
[0226] In one embodiment, the seat information interface 1200 may be generated based on seat information of a vehicle. The seat information of the vehicle may be information transmitted from a control server or stored in the driver information providing device. The driver information providing device may generate a seat layout that displays the arrangement of multiple seats based on the seat information of the vehicle.
[0227] In one embodiment, the generated seating layout may display each of the plurality of seats differently depending on the seating status of each of the plurality of seats. In one embodiment, the seating status may be, for example, one of a boarding completed state, a boarding planned state, and a remaining seat state. The boarding completed state may refer to a state in which a passenger has boarded at a boarding location and is seated in the seat, the boarding planned state may refer to a state in which a passenger has not boarded at a boarding location yet but a passenger who is scheduled to board is scheduled to be seated, and the remaining seat state may refer to a state in which a seat has not been assigned and therefore there is no passenger scheduled to be seated in the seat.
[0228] Referring to Figure 12, the objects corresponding to seats 2A and 3A in the seating layout are processed with a dark color, which may indicate a boarded-out state. Referring to Figure 12, the objects corresponding to seats 4A, 4B, and 4C in the seating layout are processed with stripes, which may indicate a boarding-to-be state. Referring to Figure 12, the objects corresponding to seats 1C and 3C are not processed at all, which may indicate an open seat state. This is provided by way of example only, and any suitable manner of indicating seat status may be applied.
[0229] In one embodiment, the seat information interface 1200 generated by the driver information providing device may be based on seat information data. The seat information data may be transmitted from a control server, and the seat information data transmitted by the control server may be generated by a request from a user terminal used by a service user. That is, the seat information interface 1200 may be generated in cooperation with the control server or the user terminal.
[0230] In one embodiment, in the process of dispatching a vehicle to a user, if there are multiple passengers, not only the dispatched vehicle but also the seats in which the passengers will sit may be determined. Information regarding the determined boarding location and the seat to be sat in can be transmitted to the demand-type vehicle, and the driver information providing device can determine the state of the seat to be sat in the boarding state until the boarding location is reached based on the transmitted information, and generate the seat information interface 1200.
[0231] In one embodiment, various methods may be applied to assign seats to passengers. For example, when one user terminal requests boarding for multiple personnel, adjacent seats may be assigned to the multiple personnel. For example, when one user terminal requests boarding for one personnel, a seat without adjacent seats on the left and right may be preferentially assigned. For example, a seat with the fewest adjacent seats in a boarding-completed state or adjacent seats in a boarding-scheduled state may be preferentially assigned. Any other suitable method of assigning seats may be applied.
[0232] Meanwhile, the seat information data may be modified by the driver information device, and the modified seat information data may be transmitted to the control server. In one embodiment, the driver on board may interact with a seat information interface displayed on the driver information device to modify or transmit the seat information data.
[0233] For example, a vehicle may leave a specific boarding location without a passenger boarding the vehicle. In this case, the seats that were scheduled to be boarded while the vehicle was leaving the boarding location should be changed to remaining seats, rather than being switched to a boarding completed state.
[0234] As a result, in one embodiment, an object corresponding to each of the multiple seats displayed in the seat layout can be generated so that the on-board driver can interact with it. In one embodiment, when the on-board driver interacts with an object corresponding to a seat that is scheduled to be boarded or a seat that is completely boarded, the seat status of the seat can be changed to a remaining seat. When the seat status of the seat is changed to a remaining seat, the driver information device can change the object corresponding to the seat in the seat layout to a remaining seat and display it. The driver information device can modify or transmit seat information data based on the changed seat status. As a result, the on-board driver can forcibly change the seat status to a remaining seat status.
[0235] In one embodiment, the main interface that can be generated by the information providing device for drivers may further include a driving control interface. The driving control interface may refer to an interface configured to allow an on-board driver to interact with the vehicle to manually or forcibly cancel or stop the vehicle allocation. In one embodiment, the driving control interface may include a driving cancellation object or a vehicle dispatch stop object. The driving cancellation object may be an object that an on-board driver interacts with to cancel the vehicle allocation, and the vehicle dispatch stop object may be an object that an on-board driver interacts with to stop the vehicle dispatch. In one embodiment, the driving cancellation object may be activated only in a boarding location transfer state.
[0236] In one embodiment, when a driver interacts with a trip cancellation object or a dispatch stop object, the driver information providing device can generate a reason input interface that allows the driver to input a reason. In one embodiment, the interface that allows the driver to input a reason can be generated to select one of a plurality of predetermined reasons. For example, the plurality of predetermined reasons can be a driver's reason, a passenger's reason, and an accident.
[0237] In one embodiment, if the reason input by the on-board driver through the reason input interface corresponds to "accident occurred", the state of the vehicle may switch to an accident occurred state. In the present disclosure, the accident occurred state may refer to a state in which operation is suspended and vehicle allocation is suspended until the accident is handled.
[0238] In one embodiment, in response to the state of the vehicle being switched to the accident occurrence state, the driver information providing device may generate an accident occurrence interface. The accident occurrence interface may include an object with which the on-board driver can interact to generate an accident processing completion signal. In response to the accident processing completion signal being received, the state of the vehicle may be switched to a dispatch waiting state.
[0239] In addition to the above-mentioned interfaces, the driver information device may generate interfaces for displaying the driver information device may include any suitable interface required for driving the vehicle. For example, the driver information device may include an interface indicating the vehicle's driving status. For example, the driver information device may include an interface indicating whether a sensor or function of the vehicle is operational.
[0240] In the present disclosure, the passenger information providing device can generate an interface for displaying on the passenger information providing device (hereinafter, "passenger interface") The passenger interface can be configured to display information required by a passenger aboard a demand-type vehicle.
[0241] In one embodiment, the passenger interface may be configured to include some or all of the interface displayed on the driver information device.
[0242] In one embodiment, the passenger interface may include a driving route interface. In one embodiment, the driving route interface included in the passenger interface may be a driving route interface included in the interface displayed on the driver information providing device with some information (e.g., an icon corresponding to a pedestrian) omitted.
[0243] In one embodiment, the passenger interface may include a route guidance interface. In one embodiment, the route guidance interface included in the passenger interface may be a route guidance interface included in the interface displayed on the driver information providing device with some information (e.g., driving method guidance) omitted.
[0244] In one embodiment, the passenger interface may include a seat information interface, which may include some information (e.g., current seat position) added to the seat information interface included in the interface displayed on the driver information device.
[0245] In one embodiment, the passenger interface may include a bus stop information interface. The bus stop information interface may be configured to display information about a bus stop where the demand vehicle stops to pick up or drop off passengers. The bus stop information interface may include information about a first bus stop to be reached and may further include information about a second bus stop to be reached. In one embodiment, the information about the first bus stop to be reached and the information about the second bus stop to be reached may be displayed alternately at a predefined cycle.
[0246] In one embodiment, the passenger interface may include a guidance message interface. Guidance messages that may be included in the guidance message interface may include, for example, a message to fasten a seat belt, a message to prepare to exit the vehicle, etc. In one embodiment, in response to the vehicle's driving mode switching from the autonomous driving mode to the manual driving mode, the guidance message may include a message that the driving mode has been switched.
[0247] In addition to the interfaces discussed above, passenger interfaces that the passenger information system may generate for display may include any suitable interface necessary to provide information to a passenger.
[0248] Hereinafter, the operation of the external display device during the process of providing service of a demand-responsive vehicle will be described.
[0249] FIG. 13 is an exemplary diagram illustrating the operation of an external display device according to an embodiment.
[0250] In one embodiment, the external display device can collect data including vehicle information, vehicle status, vehicle location information, destination information, or signals generated by devices onboard the vehicle.
[0251] In one embodiment, the external display device may generate an external display interface based on the collected data and may also cooperate with the driver information device or the passenger information device. In particular, the external display interface may be generated based on an interface included in the various interfaces generated by the driver information device described above. In one embodiment, the external display device and the driver information device may include a common processor, i.e., may be substantially the same device.
[0252] In one embodiment, the external display device may include multiple external displays. For example, the external display device may include a front display and a rear display. The front display may be a display installed at the front of the vehicle, and the rear display may be a display installed at the rear of the vehicle.
[0253] Referring to Fig. 13(a), a front display 1310 and a rear display 1320 are shown. As shown, the front display 1310 may be installed at the front of the vehicle, and the rear display 1320 may be installed at the rear of the vehicle. In Fig. 13(a), the external display interfaces displayed on the front display 1310 and the rear display 1320 are different, but may be generated in the same way. That is, the external display device may generate a front external display interface and a rear external display interface.
[0254] In one embodiment, the external display device may generate a front external display interface and a rear external display interface differently based on the collected data. For example, the subject who watches the front external display may be different from the subject who mainly watches the rear external display, and therefore the content suitable for displaying on each external display may also be different. For example, when the vehicle is in a pick-up location moving state or a drop-off location moving state, as shown in FIG. 13(a), the front display 1310 may display the name of the vehicle and the name of the route, and the rear display 1320 may display only a message that the vehicle is in operation. For example, when the vehicle enters a child protection area, the front display 1310 may display the name of the vehicle and the name of the route, as shown in FIG. 13(b), and the rear display 1320 may display only a message informing that the area is a child protection area, as shown in FIG. 13(d). For example, when a vehicle is stopped at a pick-up location (or disembarkation location) to allow a passenger to board (or disembark) (e.g., after the on-board driver interacts with the pick-up location arrival completion object and before inputting a boarding completion signal), the front display 1310 may display the vehicle name and route name as shown in FIG. 13(b), and the rear display 1320 may display only a message informing passengers that they are boarding, as shown in FIG. 13(e).
[0255] In one embodiment, the front and back display interfaces for different situations may be as follows, but are not limited to, Table 1 below.
[0256] [Table 1] In one embodiment, the external display interface may be generated based on the information of the vehicle. For example, the external display interface may be generated to display the name of the vehicle. The name of the vehicle may refer to a name that can identify which vehicle among a plurality of vehicles in the demand-based transportation system. For example, if the vehicle is a vehicle that travels along a circular route, the external display interface may be generated to display the name of the circular route. Referring to FIG. 13(b), the name of the vehicle and the name of the circular route may be displayed on the external display interface.
[0257] In one embodiment, the external display interface may be generated based on the state of the vehicle. For example, if the vehicle is not in motion, i.e., a pre-work state, a work location moving state, a rest location moving state, a rest state, a scheduled work stop state, a work stop location moving state, or a work stop end state, the external display interface may be generated to display a vehicle not in motion message. For example, the message that the vehicle is not in motion may include a message such as "preparing to move."
[0258] As another example, if the vehicle state is a rest area moving state, the message may include a message such as "Go to waiting area." As yet another example, if the vehicle state is a work area moving state, the message may include a message such as "Go to garage."
[0259] For example, if the vehicle state is an accident state, the external display interface may include a vehicle inspection message "vehicle inspection in progress," as shown in FIG. 13(c).
[0260] In one embodiment, the external display interface may be generated based on the position information of the vehicle. For example, the external display device may receive the position of the vehicle, and generate the external display interface to include a specific message in response to the received position of the vehicle entering a specific area. As an example, the specific message may be a message notifying the entry into a specific area. As a specific example, the specific area may not be a general driving road, but a special driving road such as a child protection area or a motorway. For example, when the vehicle enters a child protection area, a message notifying the entry of the vehicle into the child protection area may be displayed as shown in FIG. 13(d). As another specific example, when the vehicle enters a forced manual driving area in which the vehicle cannot be driven in the autonomous driving mode and the driving mode of the vehicle is switched to the manual driving mode, the external display interface may be generated so that a notification message of switching to the manual driving mode is displayed. For example, the notification message of switching to the manual driving mode may include a message that the driving mode has been switched, such as "driving in manual driving mode". For example, the forced manual driving area may include a child protection area.
[0261] In this embodiment, vehicle location information is received independently by the external display device separately from other devices such as the driver information device, thereby enabling the external display device to generate an interface based on the location information independently of the driver information device.
[0262] In one embodiment, the external display interface may be generated based on information about the destination, for example, the name of the destination may be displayed periodically according to a predetermined period on the external display interface.
[0263] In one embodiment, the external display interface may be generated based on a signal generated by a device onboard the vehicle. For example, in response to interacting with a boarding destination arrival complete object, the external display interface may be generated to include a message that a passenger is boarding. The message that a passenger is boarding may be maintained until a boarding complete signal is received. For example, in response to interacting with a drop-off destination arrival complete object, the external display interface may be generated to include a message that a passenger is disembarking. The message that a passenger is disembarking may be maintained until a disembarking complete signal is received. As an example, as shown in FIG. 13(e), the message that a passenger is boarding or disembarking may include a message that "passengers are boarding or disembarking."
[0264] In one embodiment, the external display interface may be generated based on a function operated on the vehicle, for example, if the vehicle is turning right, the external display interface may be generated to display a message or object indicating a right turn in response to the right turn signal being illuminated.
[0265] FIG. 14 is a flow chart of a connection method for vehicle navigation services according to one embodiment.
[0266] The operations shown in Fig. 14 can be executed by the above-mentioned connection device for vehicle operation. Specifically, the operations shown in Fig. 14 can be executed by a processor included in the above-mentioned connection device for vehicle operation.
[0267] In step 1410, the processor may receive an input of a first identifier corresponding to vehicle service provider information.
[0268] In one embodiment, Step 1410 may include displaying a first identifier input interface including a first message display area, a first input data display area, and a first data input interface.
[0269] In one embodiment, step 1410 may further include the steps of displaying a first identifier input waiting message in the first message display area, displaying input data related to the entered first identifier in the first input data display area, and, in response to receiving a first identifier input completion signal, transmitting the input data related to the entered first identifier until the first identifier input completion signal is received.
[0270] In step 1420, the processor may request verification and registration of the pre-connected device for the first identifier.
[0271] In step 1430, the processor may receive input of a second identifier corresponding to the device identification information in response to completing the verification for the first identifier.
[0272] In one embodiment, step 1430 may include displaying a second identifier input interface including a second message display area, a second input data display area, and a second data input interface.
[0273] In one embodiment, step 1430 may further include the steps of displaying a second identifier input waiting message in the second message display area, displaying input data related to the entered second identifier in the second input data display area, and, in response to receiving a second identifier input completion signal, transmitting the input data related to the entered second identifier until the second identifier input completion signal is received.
[0274] In one embodiment, the processor may display a message of an unregistered legal entity in the first message display area in response to verification failing on the first identifier.
[0275] In step 1440, the processor may request verification of the second identifier and completion of vehicle registration.
[0276] At step 1450, the processor may activate an interface corresponding to the vehicle service provider information and the equipment identification information in response to the verification of the second identifier being completed.
[0277] In one embodiment, the processor may determine that verification for the second identifier is complete if it receives a verification completion signal for the second identifier, and the verification completion signal for the second identifier may include an access token for communication.
[0278] In one embodiment, the processor may switch the state of the vehicle to a pre-work state in response to verification being completed for the second identifier.
[0279] In one embodiment, the processor may display a unique code mismatch message in the second message display area in response to the verification failing for the second identifier.
[0280] FIG. 15 is a flow chart of a method for providing a driver interface according to one embodiment.
[0281] The operation shown in Fig. 15 can be executed by the above-mentioned information providing device for driver. Specifically, the operation shown in Fig. 15 can be executed by a processor included in the above-mentioned information providing device for driver.
[0282] In step 1510, the processor may determine a main interface that displays information about vehicle operation services based on the state of the vehicle.
[0283] In one embodiment, step 1510 may include determining a main interface at a pre-departure interface, determining a main interface at a work location transfer interface in response to the vehicle state switching to a work location transfer state, and determining a main interface at a vehicle dispatch waiting interface in response to the vehicle state switching to a vehicle dispatch waiting state.
[0284] In one embodiment, if the vehicle state is a pre-work state, it may switch to a work location transfer state in response to receiving a work authorization signal.
[0285] In one embodiment, if the vehicle's state is a work location moving state, it may switch to a dispatch waiting state in response to the vehicle's position entering an automated driving route.
[0286] In one embodiment, the pre-attend interface may include a driving route interface, an interface including on-board driver information and vehicle information, an attendance authentication interface, and an autonomous driving function status interface.
[0287] In one embodiment, the work location mobility interface may include a driving route interface, a route guidance interface including information about the destination, a navigation map and driving directions, and an automated driving feature status interface.
[0288] In step 1520, the processor may generate the determined main interface.
[0289] In one embodiment, after step 1520, the processor may activate and display a first object that can be interacted with in response to satisfying a predefined condition, deactivate and display the first object in response to not satisfying the predefined condition, and display a driver menu interface in response to receiving input to interact with the activated first object.
[0290] In one embodiment, the processor displays a rest guidance interface in response to the remaining time until the scheduled break time included in the work setting data included in the driver's information reaching a first hour, switches the vehicle state to a rest location movement state when the vehicle state is in a waiting state, switches the vehicle state to a rest location movement state in response to receiving an end of operation signal when the vehicle state is in an operating state, and determines a main interface in the rest location movement interface in response to the vehicle state switching to the rest location movement state.
[0291] In one embodiment, the processor can display a break end guidance interface in response to the remaining time until the scheduled work time after the break included in the work setting data included in the driver's information reaching a second hour, and can switch the vehicle's state to a standby state in response to the remaining time until the scheduled work time after the break reaching zero.
[0292] In one embodiment, the processor can display an end-of-work guidance interface in response to the remaining time until the end of work included in the work setting data included in the driver's information reaching a third hour, switch the vehicle state to a scheduled clock-out state in response to receiving an operation end signal if the vehicle state is in an operating state, switch the vehicle state to a scheduled clock-out state if the vehicle state is in a waiting state, switch the vehicle state to a clock-out location moving state in response to the remaining time until the end of work reaching zero, and determine the main interface in the clock-out location moving interface in response to the vehicle state switching to the clock-out location moving state.
[0293] FIG. 16 is a flow chart of a method for providing a vehicle operational information interface according to one embodiment.
[0294] The operation shown in Fig. 16 can be executed by the above-mentioned information providing device for driver. Specifically, the operation shown in Fig. 16 can be executed by a processor included in the above-mentioned information providing device for driver.
[0295] In step 1610, the processor may determine a main interface that displays information about vehicle operation services based on the state of the vehicle.
[0296] In one embodiment, step 1610 may include determining the main interface at a dispatch waiting interface, and determining the main interface at a pick-up location transfer interface in response to the vehicle state switching to a pick-up location transfer state.
[0297] In one embodiment, the dispatch waiting interface may include a driving route interface configured to display an environment surrounding the vehicle, a route guidance interface including a navigation map, a notification interface that presents notifications related to the vehicle's operational assignments, and an autonomous driving function status interface.
[0298] In one embodiment, if the vehicle's state is awaiting dispatch, it may switch to a pick-up location moving state in response to receiving a dispatch request signal.
[0299] In one embodiment, the pickup location travel interface may include a driving route interface configured to display the vehicle's surrounding environment and a route guidance interface including information about the destination, a navigation map, and driving directions.
[0300] In one embodiment, the driving route interface may include an icon corresponding to the vehicle based on information about the vehicle, lanes generated based on road information received based on position information of the vehicle and lane information around the vehicle recognized from a sensor mounted on the vehicle, icons corresponding to other vehicles generated by arranging them in relative positions of the other vehicles based on information of other vehicles around the vehicle recognized from a sensor mounted on the vehicle and position information of the other vehicles, and icons corresponding to pedestrians generated by arranging them in relative positions of the pedestrians based on position information of pedestrians around the vehicle recognized from a sensor mounted on the vehicle.
[0301] In one embodiment, in response to receiving a dispatch request signal, if the vehicle's state is a dispatch waiting state, the processor can switch the vehicle's state to a pickup location moving state and set a destination based on information included in the dispatch request signal.
[0302] In step 1620, the processor may generate the determined main interface.
[0303] After step 1620, the processor may display a seat information interface.
[0304] In one embodiment, the seat information interface may include a seat layout displaying an arrangement of a plurality of seats and an indication of the seat status of each of the plurality of seats.
[0305] In one embodiment, the seat status may be one of an available seat status, a scheduled boarding status, and a completed boarding status.
[0306] After step 1620, in response to interacting with an object of a first seat among the multiple seats displayed in the seat layout, whose seat status is a scheduled boarding status or a boarding completed status, the processor can change the seat status of the first seat to a remaining seat, and in response to a change in the status of the first seat to a remaining seat, change and display the object of the first seat to a remaining seat.
[0307] From step 1620 onwards, the processor can display an arrival notification message and a boarding location arrival completion object on the main interface in response to the distance between the vehicle and the destination being less than or equal to a first critical distance, display a boarding completion object and a timer counting down a predetermined time on the main interface in response to interacting with the boarding location arrival completion object, switch the vehicle's state to a disembarking location movement state in response to receiving a boarding completion signal, and switch the vehicle's state to a dispatch waiting state in response to not receiving a boarding completion signal until the predetermined time has elapsed.
[0308] FIG. 17 is a flow chart of a connection method for vehicle navigation services according to one embodiment.
[0309] The operation shown in Fig. 17 can be executed by the driver information providing device or the external display device described above. Specifically, the operation shown in Fig. 17 can be executed by a processor included in the driver information providing device or the external display device described above.
[0310] In step 1710, data may be collected including vehicle information, vehicle status, vehicle location information, destination information, or signals generated by devices onboard the vehicle.
[0311] At step 1720, a driver interface for display on the driver information device and an external display interface for display on the external display device may be generated based on the collected data.
[0312] In one embodiment, after step 1720, a step may be performed in which vehicle location information is received by an external display device, the received vehicle location information is determined to have entered a specific area, and a step of generating a message in response to the determination indicating that the specific area has been entered, and the step of generating an external display interface may include a step of generating an external display interface such that the generated message is displayed.
[0313] In one embodiment, the specific area is a child protection area, and in response to the vehicle's driving mode switching to the manual driving mode, an external display interface can be generated to include a manual driving mode switching notification message.
[0314] In one embodiment, the external display device may include a front external display device and a rear external display device, and the external display interface may include a front external display interface and a rear external display interface.
[0315] In one embodiment, in response to the vehicle being in a waiting state for dispatch or a moving state for a pickup location, the front external display interface may display the vehicle name and the route name, and the rear external display interface may display a message during driving.
[0316] In one embodiment, in response to interacting with the boarding destination arrival completion object, the rear external display interface may display a passenger boarding message, and in response to a boarding completion signal being received, the rear external display interface may display an in-service message.
[0317] In one embodiment, in response to the vehicle entering the child protection area, a child protection area entry notification message may be displayed on the rear exterior display interface.
[0318] FIG. 18 is a block diagram of an apparatus according to one embodiment.
[0319] The device in FIG. 18 may correspond to the above-mentioned connection device for vehicle operation services, a device for providing an interface for a driver, a device for providing an interface for vehicle operation information, or a device for providing an interface for vehicle operation.
[0320] Referring to Fig. 18, the device 1800 may include a communication unit 1810, a processor 1820, and a DB 1830. Only components related to the embodiment are shown in the device 1800 in Fig. 18. Therefore, a person skilled in the art can understand that the device 1800 may further include other general components in addition to the components shown in Fig. 18.
[0321] The communication unit 1810 may include one or more components that enable wired / wireless communication with an external server or an external device. For example, the communication unit 1810 may include at least one of a short-range communication unit (not shown), a mobile communication unit (not shown), and a broadcast receiving unit (not shown).
[0322] The DB 1830 is hardware that stores various data processed in the device 1800, and may store programs for processing and controlling the processor 1820. The DB 1830 may store payment information, user information, and the like.
[0323] DB1830 may include dynamic random access memory (DRAM), random access memory (RAM), such as static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM, Blu-ray or other optical disk storage, hard disk drive (HDD), solid state drive (SSD), or flash memory.
[0324] The processor 1820 controls the overall operation of the device 1800. For example, the processor 1820 may execute a program stored in the DB 1830 to overall control an input unit (not shown), a display (not shown), a communication unit 1810, the DB 1830, etc. The processor 1820 may control the operation of the device 1800 by executing a program stored in the DB 1830.
[0325] The processor 1820 may control at least a portion of the operation of the apparatus 1800 described above in FIGS.
[0326] The processor 1820 may be implemented using at least one of ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, micro-controllers, microprocessors, and other electrical units for performing other functions.
[0327] In one embodiment, the device 1800 may be a mobile electronic device. For example, the device 1800 may be implemented as a smartphone, tablet PC, PC, smart TV, PDA (personal digital assistant), laptop, media player, navigation, camera-equipped device, and other mobile electronic devices. Furthermore, the device 1800 may be implemented as a wearable device such as a watch, glasses, headband, and ring with communication and data processing capabilities.
[0328] In another embodiment, device 1800 may be an electronic device that is installed in a vehicle. For example, device 1800 may be an electronic device that is inserted into a vehicle after the production process through tuning.
[0329] In yet another embodiment, the device 1800 may be a server located outside the vehicle. The server may be realized by a computer device or multiple computer devices that communicate over a network to provide instructions, code, files, content, services, etc. The server may receive data required to determine the vehicle's travel route from a device installed in the vehicle, and may determine the vehicle's travel route based on the received data.
[0330] In yet another embodiment, the processes performed by device 1800 may be performed by at least a portion of a mobile electronic device, an electronic device integrated within a vehicle, and a server located outside the vehicle.
[0331] The embodiments according to the present invention may be realized in the form of a computer program that can be executed by various components on a computer, and such a computer program may be recorded on a computer-readable medium, which may include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program instructions, such as ROMs, RAMs, and flash memories.
[0332] On the other hand, the computer programs may be those specially designed and constructed for the present invention, or they may be well known and available to those skilled in the art of computer software. Examples of computer programs include not only machine code, such as produced by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc.
[0333] According to one embodiment, the methods according to various embodiments of the present disclosure may be provided in a computer program product. The computer program product may be traded between sellers and buyers as a commodity. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)) or may be distributed through an application store (e.g., Play Store, etc.). TM The computer program product may be distributed online (e.g., downloaded or uploaded) via a web browser, a mobile device, or directly between two user devices. In the case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated on a machine-readable storage medium, such as a memory of a manufacturer's server, an application store's server, or an intermediary server.
[0334] Unless otherwise clearly stated or contrary to the order of steps constituting the method according to the present invention, the steps may be performed in any suitable order. The order of steps described above is not necessarily intended to limit the present invention. The use of all examples or exemplary terms (such as, for example, etc.) in the present invention is merely for the purpose of explaining the present invention in detail, and the scope of the present invention is not limited by the above examples or exemplary terms unless limited by the claims. Furthermore, those skilled in the art will recognize that various modifications, combinations, and changes can be made according to design conditions and factors within the scope of the appended claims or their equivalents.
[0335] Therefore, the spirit of the present invention should not be limited to the above-described embodiments, and all scopes equivalent to or modified equivalently to the claims below, as well as the scope of the claims, belong to the spirit of the present invention.
Claims
1. 1. A method for providing an interface for a driver, comprising: determining a main interface for displaying information related to vehicle operation services based on the vehicle status; and generating the determined main interface, The step of determining a main interface includes: determining a pre-work interface as the main interface; determining a workplace transfer interface as the main interface in response to the state of the vehicle switching to a workplace transfer state; and determining a vehicle dispatch waiting interface as the main interface in response to the state of the vehicle switching to a vehicle dispatch waiting state; Including, The state of the vehicle is When in a pre-work state, in response to receiving a work authentication signal, switching to a work location moving state; If in a work location transfer state, in response to the vehicle's position entering an automated driving route, the method switches to a dispatch waiting state.
2. A method for providing a driver interface, comprising: determining a main interface for displaying information related to vehicle operation services based on the vehicle status; and generating the determined main interface, The step of determining a main interface includes: determining a pre-work interface as the main interface; determining a workplace transfer interface as the main interface in response to the state of the vehicle switching to a workplace transfer state; and determining a vehicle dispatch waiting interface as the main interface in response to the state of the vehicle switching to a vehicle dispatch waiting state; Including, The pre-work interface includes: Driving route interface, an interface including information about the driver on board and information about the vehicle; Attendance authentication interface, and A method including an autonomous driving function status interface.
3. The workplace mobility interface includes: Driving route interface, A route guidance interface that includes destination information, navigation maps, and driving directions; and Autonomous Driving Function Status Interface The method of claim 1 , comprising:
4. The method comprises: activating and displaying a first interactable object in response to satisfying a predefined condition; in response to the predefined condition not being satisfied, deactivating and displaying the first object; and displaying a driver menu interface in response to receiving an input interacting with the activated first object. The method of claim 1 further comprising:
5. A method for providing a driver interface, comprising: determining a main interface for displaying information related to vehicle operation services based on the vehicle status; and generating the determined main interface, The step of determining a main interface includes: determining a pre-work interface as the main interface; determining a workplace transfer interface as the main interface in response to the state of the vehicle switching to a workplace transfer state; and determining a vehicle dispatch waiting interface as the main interface in response to the state of the vehicle switching to a vehicle dispatch waiting state; Including, The method comprises: displaying a rest guidance interface in response to a remaining time until a scheduled rest time included in work setting data included in the driver information reaching a first hour; When the state of the vehicle is a dispatch waiting state, switching the state of the vehicle to a rest area moving state; switching the state of the vehicle to a rest area moving state in response to receiving an end-of-travel signal when the state of the vehicle is a moving state; and determining a main interface at a rest area movement interface in response to the state of the vehicle switching to a rest area movement state; A method comprising:
6. displaying a break end guidance interface in response to a remaining time until a scheduled work time after the break, which is included in the work setting data included in the driver information, reaching a second hour; and switching the state of the vehicle to a dispatch standby state in response to the remaining time until the scheduled work time after the break reaching zero; The method of claim 5 , comprising:
7. In the driver interface providing device, a memory having at least one program stored therein; and a processor that operates by executing said at least one program, The processor, determining a main interface for displaying information about the vehicle operation service based on the vehicle status; Generate the determined main interface, Determining the main interface includes: determining a pre-work interface as the main interface, determining a workplace transfer interface as the main interface in response to the state of the vehicle switching to a workplace transfer state, and determining a vehicle dispatch waiting interface as the main interface in response to the state of the vehicle switching to a vehicle dispatch waiting state; The state of the vehicle is When in a pre-work state, in response to receiving a work authentication signal, switching to a work location moving state; When in a work location moving state, the device switches to a dispatch waiting state in response to the vehicle's position entering an automated driving route.
8. A computer-readable recording medium having recorded thereon a program for causing a computer to execute the method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Vehicle allocation management system
JP1999283191A
