KR102518415B1 - Method and apparatus of providing interface for driver - Google Patents

Abstract

The present invention relates to a method and a device for providing an interface for a driver. According to one embodiment of the present disclosure, the method for providing an interface comprises: a step of determining a main interface displaying information related to a vehicle driving service based on a state of a vehicle; and a step of generating the determined main interface. The step of determining the main interface comprises: a step of determining the main interface by an interface before going to work; a step of determining the main interface by a workplace movement interface by responding to switching of the state of the vehicle to a workplace movement state; and a step of determining the main interface by an allocation standby interface by responding to switching of the state of the vehicle to the allocation standby state.

Description

Method and device for providing interface for engineer {METHOD AND APPARATUS OF PROVIDING INTERFACE FOR DRIVER}

The present invention relates to a method and apparatus for providing an interface for an article.

Conventional means of transportation include buses, subways, and taxis. Buses and subways are inexpensive, but have the inconvenience of having to go directly to a designated area at a set time and take a taxi. However, there is a disadvantage that the cost is high.

In general cities, you can freely use transportation such as buses, subways, and taxis. It falls.

Demand Responsive Transportation (DRT) transportation is emerging as a transportation method that compensates for the advantages and disadvantages of these conventional transportation means. Demand-response transportation means a transportation method that can flexibly operate the service section, service frequency, and service time according to the user's demand without a fixed route.

Recently, research on how to operate a demand-responsive transportation system more efficiently is required.

The foregoing background art is technical information that the inventor possessed for derivation of the present invention or acquired during the derivation process of the present invention, and cannot necessarily be said to be known art disclosed to the general public prior to filing the present invention.

An object of the present disclosure is to provide a method and apparatus for providing an interface for an article. The problems to be solved by the present disclosure are not limited to the above-mentioned problems, and other problems and advantages of the present disclosure that are not mentioned can be understood by the following description and more clearly understood by the embodiments of the present disclosure. It will be. In addition, it will be appreciated that the problems and advantages to be solved by the present disclosure can be realized by the means and combinations indicated in the claims.

According to a first aspect of the present disclosure, based on a state of a vehicle, determining a main interface displaying information about a vehicle driving service; and generating the determined main interface, wherein the determining of the main interface comprises: determining the main interface as an interface prior to going to work; determining the main interface as a workplace movement interface in response to the state of the vehicle being switched to the workplace movement state; and determining the main interface as the dispatch waiting interface in response to the state of the vehicle being switched to the dispatch standby state.

A second aspect of the present disclosure is a memory in which at least one program is stored; and a processor that operates by executing the at least one program; wherein the processor determines a main interface for displaying information on a vehicle driving service based on a state of the vehicle, and generates the determined main interface; Determining the main interface may include determining the main interface as an interface before going to work, determining the main interface as a work place movement interface in response to the state of the vehicle being switched to the work place movement state, and determining the main interface as the work place movement state, An apparatus for providing an interface for a driver may be provided, which determines the main interface as an dispatch standby interface in response to a transition to a dispatch wait state.

A third aspect of the present disclosure may provide a computer-readable recording medium recording a program for executing the method according to the first aspect in a computer.

According to the above-described problem solving means of the present disclosure, a demand response type system can be effectively operated.

In addition, since an interface that is appropriately switched according to the state of the vehicle can be displayed, it is possible to provide a pleasant and efficient work and demand-responsive vehicle service to the driver.

1 is a diagram for explaining an autonomous driving method according to an exemplary embodiment.
2 is a block diagram illustrating hardware included in an autonomous driving device according to an exemplary embodiment.
3 is a diagram for explaining a demand-responsive transportation system according to an exemplary embodiment.
4 is a state diagram illustrating a process of providing operation of a demand-responsive vehicle and a change in a state of a demand-responsive vehicle in a demand-responsive transportation system according to an exemplary embodiment.
5 is a diagram illustrating an access process for driving a vehicle according to an exemplary embodiment.
6A and 6B are exemplary diagrams illustrating interfaces that may be displayed in an access process for driving a vehicle according to an exemplary embodiment.
7 is an exemplary diagram illustrating a travel route interface according to an embodiment.
8 is an exemplary diagram illustrating an interface before going to work created according to an embodiment.
9 is an exemplary diagram illustrating a workplace movement interface created according to an embodiment.
10 is an exemplary diagram illustrating an dispatch standby interface generated according to an exemplary embodiment.
11 is an exemplary diagram illustrating a boarding point movement interface generated according to an embodiment.
12 is an exemplary diagram illustrating a seat information interface generated according to an embodiment.
13 is an exemplary diagram for explaining an operation of an external display device according to an exemplary embodiment.
14 is a flowchart of a method for providing an interface for an article according to an exemplary embodiment.
15 is a block diagram of a device for providing an interface for a driver according to an exemplary embodiment.

Advantages and features of the present invention, and methods for achieving them will become clear with reference to the detailed description of embodiments in conjunction with the accompanying drawings. However, it should be understood that the present invention is not limited to the embodiments presented below, but may be implemented in a variety of different forms, and includes all conversions, equivalents, and substitutes included in the spirit and scope of the present invention. . The embodiments presented below are provided to complete the disclosure of the present invention and to fully inform those skilled in the art of the scope of the invention to which the present invention belongs. In describing the present invention, if it is determined that a detailed description of related known technologies may obscure the gist of the present invention, the detailed description will be omitted.

Terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, the terms "include" or "have" are intended to designate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, but one or more other features It should be understood that the presence or addition of numbers, steps, operations, components, parts, or combinations thereof is not precluded.

Some embodiments of the present disclosure may be represented as functional block structures and various processing steps. Some or all of these functional blocks may be implemented as a varying number of hardware and/or software components that perform specific functions. For example, functional blocks of the present disclosure may be implemented by one or more microprocessors or circuit configurations for a predetermined function. Also, for example, the functional blocks of this disclosure may be implemented in various programming or scripting languages. Functional blocks may be implemented as an algorithm running on one or more processors. In addition, the present disclosure may employ prior art for electronic environment setup, signal processing, and/or data processing, etc. Terms such as “mechanism,” “element,” “means,” and “composition” will be used broadly. It can be, and is not limited to mechanical and physical configurations.

In addition, connecting lines or connecting members between components shown in the drawings are only examples of functional connections and/or physical or circuit connections. In an actual device, connections between components may be represented by various functional connections, physical connections, or circuit connections that can be replaced or added.

Vehicles may include all types of transportation means used to move people or objects with engines, such as cars, buses, motorcycles, kickboards, or trucks.

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

1 is a diagram for explaining an autonomous driving method according to an exemplary embodiment.

Referring to FIG. 1 , an autonomous driving device according to an embodiment of the present invention may be mounted on a vehicle to implement an autonomous vehicle 10 . An 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 the preceding vehicle 20 running in front through an image sensor and/or an event sensor mounted on the front of the autonomous vehicle 10 . The self-driving device may further include sensors for detecting the front side of the self-driving vehicle 10, another driving vehicle 30 operating in a side road, and pedestrians around the self-driving vehicle 10.

At least one of the sensors for collecting situational information around the self-driving vehicle may have a predetermined field of view (FoV) as shown in FIG. 1 . For example, when a sensor mounted on the front of the autonomous vehicle 10 has an angle of view (FoV) as shown in FIG. 1 , information detected in the center of the sensor may have a relatively high importance. This may be because most of the information corresponding to the motion of the preceding vehicle 20 is included in the information detected from the center of the sensor.

The self-driving device controls the movement of the self-driving vehicle 10 by processing information collected by sensors of the self-driving vehicle 10 in real time, while storing at least some of the information collected by the sensors in a memory device. .

2 is a block diagram illustrating hardware included in an autonomous driving device according to an exemplary embodiment.

Referring to FIG. 2 , an autonomous driving device 40 may include a sensor unit 41 , a processor 46 , a memory system 47 , a vehicle body control module 48 , and the like. The sensor unit 41 includes a plurality of sensors 42-45, and the plurality of sensors 42-45 may include an image sensor, an event sensor, an illuminance sensor, a GPS device, an acceleration sensor, and the like.

Data collected by sensors 42-45 may be passed to processor 46. The processor 46 stores the data collected by the sensors 42-45 in the memory system 47, and controls the body control module 48 based on the data collected by the sensors 42-45 to control the vehicle movement can be determined. 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 as a single semiconductor chip.

In addition to the system controller of the memory system 47, each of the memory devices included in the memory system 47 may include a memory controller, and the memory controller may include an artificial intelligence (AI) operation circuit such as a neural network. The memory controller may generate calculation data by assigning a predetermined weight to data received from the sensors 42 to 45 or the processor 46 and store the calculation data in a memory chip.

The autonomous driving device 40 may be mounted on a demand response type vehicle described below.

3 is a diagram for explaining a demand-responsive transportation system according to an exemplary embodiment.

Demand Responsive Transportation (DRT) transportation means a transportation method that can flexibly operate the operation section, number of trips, and operation hours according to user demand without a fixed route.

Demand-response transportation can be classified into various types according to the route operation method. For example, the fixed route type is a type in which the operation time, stop, and origin/end point are all fixed. The off-route type is a type in which the operation time, starting point, and ending point are fixed, but in the case of a stop, a new stop can be set in addition to the fixed stop according to the user's reservation. In the quasi-dynamic type, the starting and ending points are fixed, but only the departure and arrival times are fixed for the operation time, and the stops other than the starting and ending points can be set freely. The dynamic type is a type in which the operation time, stop, and start/end point are not fixed.

In addition, demand response traffic can be classified into various types according to the number of starting and ending points. For example, a one-to-one type is a type that starts at one point and moves to another point. In addition, the one-to-many type is a type that moves from one source to multiple destinations, and the many-to-one type is a type that moves from multiple sources to one destination. In addition, the many-to-many type has no start and end points, and can be changed according to circumstances or needs.

Referring to FIG. 3 , the demand response type transportation system 300 may include a user terminal 310 , a control server 320 and a demand response type vehicle 330 .

The user terminal 310 may refer to a terminal of a user who wants to use the demand-responsive transportation system 300 (hereinafter referred to as 'service user'). In the present disclosure, the user terminal 310 may have the same meaning as a device for a service user. An application for a service user configured to transmit/receive various information and provide an interface for a service user to use the demand-responsive 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 an application for a service user is installed.

A service user may be provided with a vehicle dispatch service in which a boarding and alighting location is determined through the user terminal 310 and a vehicle is allocated based on the boarding and alighting location. In addition, the service user may be provided with dispatch information through the user terminal 310 until riding the dispatched vehicle. In addition, the service user may be provided with driving information about the vehicle he/she has boarded through the user terminal 310 .

The user terminal 310 receives a service user's input through an application, transmits data to the control server 320 or the demand response type vehicle 330 based on the received input, and transmits data to the control server 320 or the demand response type vehicle 330. Data may be received from the vehicle 330 and provided to a service user through an application based on the received data.

The user terminal 310 includes a smart phone, a tablet PC, a PC, a smart TV, a mobile phone, a personal digital assistant (PDA), a laptop, a media player, a micro server, a global positioning system (GPS) device, an e-book reader, and a digital broadcasting terminal. , navigation, kiosks, MP3 players, digital cameras, consumer electronics, devices with cameras, and other mobile or non-mobile computing devices, but are not limited thereto. In addition, the user terminal 310 may be a wearable device having a communication function and data processing function, such as a watch, glasses, a hair band, and a ring, but is not limited thereto.

The control server 320 refers to a server that performs a control function for operating demand response type traffic. The control server 320 may transmit and receive data with the user terminal 310 to provide service users with the use of the demand response type transportation system 300 . In addition, the control server 320 may maintain, repair, manage, or control the demand-responsive transportation system 300 by transmitting and receiving data to and from the demand-responsive vehicle 330 .

The control server 320 provides information on service users, information on vehicle service providers (e.g., vehicle operating corporations) that operate demand-response traffic, information on drivers belonging to vehicle service providers, and information on the driver's work. Information or data necessary to implement the demand-responsive transportation system 300 including information on demand-response vehicles and information on demand-response vehicles may be stored.

In order to perform the functions of the control server 320, an information providing device for control that can be used by an administrator of the control server 320, is part of the control server 320, or connected to the control server 320 may be provided. . The device for providing information for control may provide an interface for control through which the manager of the control server 320 may interact.

The demand response type vehicle 330 refers to a vehicle that provides transportation to service users according to the demand response type traffic operation method under the control of the control server 320 . The demand response type vehicle 330 may be a vehicle that is dispatched according to a user's demand and whose operation section, number of times of operation, operation time, etc. are determined according to the operation method of demand response type traffic.

The demand response type vehicle 330 may include an information providing device for drivers, an information providing device for passengers, or a display device outside the vehicle.

The driver's information providing device is a part of the demand response vehicle 330 that can be used by a driver who gets on the demand response vehicle 330 and directly drives the demand response vehicle 330 or assists autonomous driving, or It may refer to a device connected to the demand response type vehicle 330 . Alternatively, the driver's information providing device may be a part of an autonomous driving device installed in the demand response type vehicle 330 or a device connected to the autonomous driving device. The device for providing information for drivers may provide the driver with information about the boarded driver and transmit data to the control server 320 in response to an interaction with the driver.

The device for providing information for passengers is a part of the demand response vehicle 330 that can be used by a service user (hereinafter referred to as 'passenger') riding on the demand response vehicle 330 or connected to the demand response vehicle 330. can mean a device. Alternatively, the device for providing information for passengers may be a part of an autonomous driving device installed in the demand response type vehicle 330 or a device connected to the autonomous driving device. The device for providing information for passengers may be configured to provide passengers with information about the demand-responsive vehicle they have boarded and to interact with the passengers.

The external display device may refer to a device connected to the demand responsive vehicle 330 or a part of the demand responsive vehicle 330 capable of displaying information toward the outside of the demand responsive vehicle 330 . Alternatively, the external display device may be a part of an autonomous driving device installed in the demand response type vehicle 330 or a device connected to the autonomous driving device. The external display device may be associated with an information providing device for drivers or an information providing device for passengers, and may be configured to display various types of information on the outside of the demand response type vehicle 330 .

The user terminal 310, the control server 320, and the demand response type vehicle 330 may perform communication using a network. For example, the network may include a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and any of these It is a comprehensive data communication network that includes mutual combinations and enables each network constituent entity shown in FIG. 3 to communicate smoothly with each other, and may include wired Internet, wireless Internet, and mobile wireless communication network. In addition, wireless communication, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth low energy (Bluetooth low energy), Zigbee, WFD (Wi-Fi Direct), UWB (ultra wideband), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), etc. may be included, but are not limited thereto.

4 is a state diagram illustrating a process of providing operation of a demand-responsive vehicle and a change in a state of a demand-responsive vehicle in a demand-responsive transportation system according to an exemplary embodiment.

Each state shown in FIG. 4 means one of states that a demand-responsive vehicle may have while it is being operated in the demand-responsive transportation system. Hereinafter, the term 'vehicle' may be interpreted as meaning including a demand response type vehicle.

In this disclosure, the state of the vehicle may be automatically switched based on specific conditions such as the location of the vehicle.

In the present disclosure, the state before going to work ( S1 ) may refer to a state of the vehicle before the driver gets on the vehicle and authenticates going to work. The boarding driver may work according to a work plan corresponding to work related information stored in the control server. In one embodiment, the state of the vehicle may be set or initialized to a state before going to work (S1) in response to remaining as much as a threshold time or less until the shift start time included in the information about shifts stored in the control server.

In the present disclosure, the work place movement state S2 may refer to a vehicle state when a vehicle that does not exist at the work place is moving to the work place. In one embodiment, the work place movement state S2 may refer to a state of a vehicle that is switched when the driver of the vehicle completes attendance certification in the state before going to work S1. In one embodiment, a place of work may refer to any point on an autonomous driving route.

In the present disclosure, the waiting for dispatch state ( S3 ) may refer to a state of a vehicle when the vehicle exists on an autonomous driving route and can be assigned to travel, but has not yet been assigned.

In the present disclosure, the boarding location movement state (S4) may refer to a state of the vehicle when the vehicle is assigned to travel and moves to a boarding location, which is a place where passengers plan to board. In the present disclosure, the assignment of vehicle operation may correspond to the completion of assignment to a service user. In the present disclosure, even if a vehicle is allocated for operation, the operation may be canceled by a driver, a control server, or a passenger who decides to board.

In the present disclosure, the drop-off location moving state S5 may refer to a state of the vehicle when a passenger gets on the vehicle and moves to a drop-off location, which is a place where the passenger decides to get off.

In one embodiment, when the state of the vehicle is in the drop-off location moving state (S5), the state of the vehicle may be switched to the dispatch standby state (S3) in response to the passenger getting off at the drop-off point.

In the present disclosure, the resting place moving state S6 may refer to a state of the vehicle when the driver drives the vehicle and moves to the resting place for the driver to rest. In one embodiment, the state of the vehicle may be switched to a rest area movement state S6 based on a rest plan included in a work plan corresponding to work related information stored in the control server.

In the present disclosure, the rest state S7 may refer to a state of the vehicle when the vehicle moves to a rest area and the driver is taking a break.

In one embodiment, when the state of the vehicle is in the rest state (S7), the state of the vehicle may be switched to the work place movement state (S2) in response to the end of the driver's rest time.

In the present disclosure, the moving state S8 may refer to a state of a vehicle when a vehicle that does not exist at the work place is moving to the work place. In one embodiment, based on the work plan corresponding to the work information stored in the control server, the state of the vehicle may be switched to the work place movement state (S8).

In the present disclosure, the duty end state ( S9 ) may refer to a state of the vehicle when the driver ends his duty and moves to the place of work. In one embodiment, when the vehicle is in the work place moving state (S8), when the vehicle arrives at the work place, the state of the vehicle may be switched to the work end state (S9).

Each state shown in FIG. 4 is provided as an example, and the state of the demand response vehicle may be arbitrarily appropriately configured according to the type of the demand response vehicle, the nature of the route, and the driving method, in addition to those shown. Some of each state may be omitted. As an example, when the demand response type vehicle is a van, the dispatch waiting state S3 may not exist, and the boarding location moving state S4 and the drop off location moving state S5 may be in the same state. As another example, when a break plan is not included in the driver's work plan, the resting place movement state (S6) and the resting state (S7) may not exist.

Also, switching between vehicle states, indicated by arrows in FIG. 4 , may be performed differently from those shown. As an example, when the operation assignment is canceled in the boarding location moving state (S4), it may be directly switched to the dispatch waiting state (S3) instead of being switched to the dropping off location moving state (S5).

Hereinafter, a connection process for driving a vehicle will be described as a preliminary work to be performed by a driver to drive a vehicle.

In the present disclosure, the connection process for driving a vehicle may be performed through a connection device for driving a vehicle, and the connection device for driving a vehicle may refer to a device in which software for a driver is installed.

In the present disclosure, an access process for driving a vehicle may refer to a process in which a driver connects a device he or she has with a vehicle so that the vehicle can be used to provide a demand-responsive transportation service. The connection process for vehicle operation is to verify or register whether a demand-responsive vehicle or a driver riding the vehicle is suitable for providing demand-responsive transportation service or whether it is scheduled to provide demand-responsive transportation service. process may be included.

According to the connection process for driving a vehicle according to an embodiment of the present disclosure, a device connected to or mounted on a demand response vehicle does not necessarily need to be a device verified or distributed by a control server, and a driver uses software for a driver. The installed device can be connected to a demand responsive vehicle and the vehicle can be used for demand responsive transportation service. In addition, when a device previously connected to a demand response type vehicle (or a device as part of a demand response type vehicle) fails, an emergency situation can be flexibly handled if there is a device installed with software for a driver.

5 is a diagram illustrating an access process for driving a vehicle according to an exemplary embodiment.

Referring to FIG. 5 , in the present disclosure, the connection process for driving a vehicle includes a boarding entity 510, a connection device for driving a vehicle 520, a vehicle management system 530 for business operators, a control server 540, or vehicle management. The process may be performed by transmitting/receiving signals or data between the servers 550 .

The boarding entity 510 of FIG. 5 may correspond to the boarding driver of the present disclosure.

In FIG. 5 , the vehicle management system 530 for operators is a device used by a vehicle service providing entity (eg, a vehicle operating corporation) operating demand response type transportation or a vehicle service providing entity operating demand response type transportation, or a demand response system. It may be a digital interface provided for management purposes such as a web page or a mobile app used by a vehicle service provider operating type transportation.

In FIG. 5 , the vehicle management server 550 may serve as a server that manages fleets including vehicles, and includes pure data of the fleet, eg, vehicle ID, vehicle manufacturer, and number of passengers. Data such as number, vehicle type, etc. can be managed. Meanwhile, the control server 540 of FIG. 5 may be a server that controls the operation of the fleet. The control server 540 may manage data such as vehicle dispatch, service users (customers), and vehicle driving conditions. That is, the vehicle management server 550 may play a role of managing mobility services, and the control server 540 may play a role of operating mobility services.

In one embodiment, the vehicle management server 550 may be the same as the control server 540 or may be configured as a part of the control server 540 .

The connection process for driving a vehicle according to an embodiment may be performed after the boarding entity 510 connects the connection device 520 for driving the vehicle to the vehicle.

Referring to FIG. 5 , in step 5001, the connection device 520 for vehicle driving requests the boarding entity 510 to input a first identifier in response to the connection device 520 for vehicle driving being connected to the vehicle. can

Referring to FIG. 5 , in step 5002, the boarding entity 510 may input a first identifier to the connection device 520 for driving the vehicle.

In the present disclosure, the first identifier may correspond to vehicle service provider information. That is, the first identifier may be an identifier capable of identifying a company, corporation, or company that provides or operates a vehicle service, such as a corporate ID or business registration number.

Referring to FIG. 5 , in step 5003, in response to the input of the first identifier of the vehicle driving entity 510, the vehicle management server 550 verifies and reserves the first identifier. Access device registration may be requested.

Referring to FIG. 5 , in step 5004, the vehicle management server 550 may transmit a verification completion signal for the first identifier and a preliminary connection device registration completion signal to the access device 520 for driving the vehicle.

Referring to FIG. 5 , in step 5005, the connection device 520 for vehicle driving determines that the verification of the first identifier is completed in response to receiving a signal indicating completion of verification of the first identifier and completion of registration of the preliminary access device. And, the boarding entity 510 may be requested to input the second identifier.

Referring to FIG. 5 , in step 5006, the vehicle management system for business operators 530 may request a first identifier preliminary access device list from the control server 540. In step 5007, the control server 540 may transmit the first identifier preliminary connected device list request to the vehicle management server 550 in response to receiving the first identifier preliminary connected device list request.

Referring to FIG. 5 , in step 5008, the vehicle management server 550 may return the first identifier preliminary connected device list to the control server 540 in response to the request for the first identifier preliminary connected device list. In step 5009, the control server 540 may transmit the first identifier preliminary access device list to the vehicle management system 530 for operators in response to receiving the first identifier preliminary access device list. The vehicle management system 530 for business operators may match an access device to a pre-registered vehicle in response to receiving the first identifier preliminary access device list.

Referring to FIG. 5 , in step 5010, the vehicle management system for business operators 530 may match an access device with a previously registered vehicle, and then request registration of the access device with the previously registered vehicle. The control server 540 may verify the previously registered vehicle in response to receiving a request to register a connection device to the previously registered vehicle.

Referring to FIG. 5 , in step 5011, the control server 540 verifies the previously registered vehicle, and then requests the vehicle management server 550 to register an access device to the previously registered vehicle. The vehicle management server 550 may generate a second identifier in response to receiving a request for registering a connection device with a previously registered vehicle.

In the present disclosure, the second identifier may correspond to equipment specific information. Through verification of the second identifier, it is possible to determine whether or not a device that is intended to connect to the demand-responsive transportation system and provide travel is a suitable device, and which functions and interfaces to activate.

Also, in the present disclosure, the second identifier may correspond to service specific information. Software (eg, an application) for a driver installed in a connection device for driving a vehicle may include various functions or services. The second identifier determines which service to provide among various types of services, and provides It may be an identifier that is a basis for determining a function corresponding to a service.

Referring to FIG. 5 , in step 5012, the vehicle management server 550 may generate a second identifier and then return the second identifier to the control server 540. In step 5013, the control server 540 may deliver the second identifier to the vehicle management system 530 for operators in response to receiving the second identifier. In step 5014, the vehicle management system 530 for business operators may transmit the second identifier to the boarding entity 510 in response to receiving the second identifier.

In one embodiment, steps 5006 to 5014 may be performed independently of or concurrently with step 5005.

Referring to FIG. 5 , in step 5015, a second identifier input request is received, and the boarding entity 510 receiving the second identifier may input the second identifier into the vehicle driving connection device 520. For example, the boarding entity 510 may check the second identifier received through the personal terminal and input the second identifier to the connection device 520 for vehicle operation.

Referring to FIG. 5 , in step 5016, the vehicle driving access device 520 may request the vehicle management server 550 to verify the second identifier and complete vehicle registration in response to receiving the input of the second identifier. . The vehicle management server 550 may register a device in a pre-registered vehicle in response to receiving the second identifier verification and vehicle registration completion request.

Referring to FIG. 5 , in step 5017, the vehicle management server 550 registers the equipment in the previously registered vehicle, and then transmits a signal for completion of verification of the second identifier and registration of spare equipment to the connection device 520 for vehicle operation. can transmit In one embodiment, the verification completion signal for the second identifier and the preliminary equipment registration completion signal may include an access token for communication. The access token for communication may refer to authority for the access device 520 for vehicle operation to access the demand-responsive transportation system to provide services.

Referring to FIG. 5 , the connection device 520 for driving a vehicle activates an interface corresponding to the first identifier and the second identifier in response to receiving a signal for completion of verification of the second identifier and registration of spare equipment. can The connection device 520 for driving a vehicle may provide an activated interface to the boarding entity 510 .

In an embodiment, when receiving a verification failure signal for the first identifier, the connection device 520 for driving the vehicle may re-request input of the first identifier to the boarding entity 510 .

In an embodiment, when receiving a verification failure signal for the second identifier, the connection device 520 for driving the vehicle may re-request input of the second identifier to the boarding entity 510 . In another embodiment, when receiving a verification failure signal for the second identifier, the connection device 520 for vehicle operation may re-request input of the first identifier to the boarding entity 510 .

Software for a boarding driver is installed in the connection device 520 for vehicle operation, and the installed software for a boarding driver is not different depending on the boarding driver, vehicle service provider, and type of service, and all included in the demand-responsive transportation system. It may be implemented for a driver, vehicle service provider, and service type. However, for efficient and effective demand-response vehicle operation, it may be desirable to provide a function or interface suitable for a driver, vehicle service provider, and service type. Accordingly, through a process of activating a corresponding interface, only appropriate functions or interfaces in software including various functions or interfaces may be activated and provided.

In one embodiment, the interface activated and provided by the connection device 520 for driving a vehicle may be the interface displayed in the aforementioned state before going to work.

6A and 6B are exemplary diagrams illustrating interfaces that may be displayed in an access process for driving a vehicle according to an exemplary embodiment.

As shown in FIGS. 6A and 6B , in the connection process for driving the vehicle described with reference to FIG. 5 , an interface suitable for requesting an input from the driver and allowing the driver to input data is provided by the connection device for driving the vehicle. can be provided.

Referring to FIG. 6A , in an embodiment, a first identifier input interface 610 may be displayed while a vehicle driving connection device receives a first identifier input from a driver. 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 .

In the present disclosure, the first message display area 601 may refer to an area for displaying various messages including a message for informing a boarding driver what action to take. In particular, the first message display area 601 may be an area for displaying a message necessary for a driver in the process of inputting and verifying the first identifier.

In the present disclosure, the first input data display area 602 may refer to an area configured to check data input by a driver. In particular, the first input data display area 602 may be a means by which a boarding driver who inputs the first identifier can check whether or not he or she is correctly inputting the first identifier.

In the present disclosure, the first data input interface 603 may refer to an interface including an object for a driver to input data. In one embodiment, the first data input interface 603 may be configured to include only necessary objects according to the configuration method of the first identifier (eg, Korean only, English only, English and numbers, etc.).

In one embodiment, the connection device for driving a vehicle comprises a first message display area 601, a first input data display area 602, and a first data input interface 603, respectively, and configured first message display area 601 , the first input data display area 602 and the first data input interface 603 may be included to create the first identifier input interface 610 . In one embodiment, the connection device for driving a vehicle may display the generated first identifier input interface 610 to be provided to a driver.

6A illustrates a process in which a driver inputs a first identifier through the first identifier input interface 610 . As shown, interfaces suitable for various situations that may occur in the process of verifying the first identifier may be displayed.

Specifically, while the vehicle driving connection device receives the first identifier from the driver, the vehicle driving connection device may display a message waiting for input of the first identifier in the first message display area 601 . For example, the first identifier input waiting message may include messages waiting for completion of inputting the first identifier, such as “Please input business registration number” or “Enter corporate ID”.

Correspondingly, the driver may input the first identifier by interacting with the first data input interface 603, and the connection device for vehicle driving displays input data related to the input first identifier as the first input data. area 602 can be displayed.

The first data input interface 603 may include an object that completes an input (eg, an object in the shape of an Enter key), and the driver interacts with the object that completes the input to generate a first identifier input completion signal. can do.

In response to receiving the first identifier input completion signal, the connection device for driving the vehicle may transmit input data related to the input first identifier to the control server until the first identifier input completion signal is received. In addition, the connection device for vehicle operation may transmit driver information or vehicle information along with input data related to the first identifier, and may request verification of the first identifier based on the transmission.

In one embodiment, the verification result is largely verification failure or verification success, and the connection device for vehicle driving may generate the first identifier input interface 610 according to a signal according to the verification result.

For example, if the transmitted input data for the first identifier is not included in the data list stored in the control server or vehicle management server, that is, if it is not vehicle service provider information registered in the control server, access for vehicle operation The device may display an unregistered corporation message in the first message display area 601 . For example, the unregistered corporation message may include a message indicating that the vehicle service provider is not registered, such as "This is an unregistered business operator" or "This is an unregistered corporation".

For example, when the vehicle driving connection device is successfully verified by the control server, the vehicle driving connection device 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 messages indicating that the first identifier verification has been successfully completed, such as "verification has been completed" and "proceed to the next step".

Referring to FIG. 6B , in an embodiment, a second identifier input interface 620 may be displayed while a vehicle driving connection device receives a second identifier input from a driver. 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 .

In the present disclosure, the second message display area 604, similar to the first message display area 601, may refer to an area for displaying various messages including a message for informing the driver what action to take. can In particular, the second message display area 604 may be an area for displaying a message necessary for a driver in the process of inputting and verifying the second identifier.

In the present disclosure, the second input data display area 604 may refer to an area configured to check data input by a driver, similar to the first input data display area 602 . In particular, the second input data display area 604 may be a means for self-confirming whether or not the driver inputting the second identifier is correctly inputting it.

In the present disclosure, the second data input interface 606, similar to the first data input interface 603, may refer to an interface including an object for a driver to input data. In one embodiment, the second data input interface 606 may be configured to include only necessary objects according to the configuration method of the second identifier (eg, Korean only, English only, English and numbers, etc.).

In one embodiment, the connection device for driving a vehicle comprises a second message display area 604, a second input data display area 605, and a second data input interface 606, respectively, and configured second message display area 604 , the second input data display area 605 , and the second data input interface 606 may be included to create the second identifier input interface 620 . In one embodiment, the connection device for driving a vehicle may display the generated second identifier input interface 620 to be provided to a driver.

6B illustrates a process in which the driver inputs the second identifier through the second identifier input interface 620. As shown, interfaces suitable for various situations that may occur in the process of verifying the second identifier may be displayed.

Specifically, while the vehicle driving connection device receives the second identifier from the driver, the vehicle driving connection device may display a message waiting for input of the second identifier in the second message display area 604 . For example, the second identifier input waiting message may include messages waiting for completion of inputting the second identifier, such as “Please input a secret code” or “Enter an authentication number”.

Correspondingly, the driver may input the second identifier by interacting with the second data input interface 606, and the connection device for driving the vehicle displays input data related to the input second identifier as the second input data. area 605 can be displayed.

The second data input interface 606 may include an object for completing input (eg, an object in the shape of an Enter key), and the driver interacts with the object for completing input to generate a second identifier input completion signal. can do.

The connection device for driving a vehicle may transmit input data related to the input second identifier to the control server until the second identifier input completion signal is received in response to receiving the second identifier input completion signal. The access device for driving the vehicle may request verification of the second identifier based on this transmission.

In one embodiment, the verification result can be largely verification failure or verification success. The connection device for driving the vehicle may generate the second identifier input interface 620 according to the signal according to the verification result.

For example, if input data about the transmitted second identifier does not match the generated second identifier, the connection device for driving a vehicle may display a unique code mismatch message in the second message display area 604. . For example, the unique code mismatch message may include messages indicating that the second identifier has been entered incorrectly, such as "incorrect secret code" or "incorrect authentication number".

For example, when the transmitted input data on the second identifier matches the unique code, the connection device for driving a vehicle may display a second identifier verification completion message on the second message display area 604 . For example, the verification completion message may include messages indicating that the second identifier verification has been successfully completed, such as "verification has been completed" and "equipment access has been completed".

Hereinafter, a process of providing driving of a demand response type vehicle after connection for vehicle driving is completed will be described.

As described above, the demand response type vehicle may include an information providing device for a driver, an information providing device for passengers, or a display device outside the vehicle. The device for providing information for drivers may be the same as or correspond to the aforementioned device for driving a vehicle.

In the present disclosure, in a process of providing driving of a demand-responsive vehicle, an information providing device for a driver may perform a process of determining a main interface displaying information on a vehicle driving service and generating the determined main interface.

First, until driving is assigned to a demand response type vehicle, the main interface may be largely determined as an interface before going to work, an interface for moving to work, or an interface waiting for dispatch.

In one embodiment, the interface before going to work, the interface for moving to work, and the interface waiting for dispatch may include a driving route interface. A driving route interface may also be created by the driver's information providing device, and the driver's information providing device may create a driving route interface based on received or collected information.

7 is an exemplary diagram illustrating a travel route interface according to an embodiment.

In the present disclosure, the driving route interface 700 may refer to an interface displaying the surrounding environment of a vehicle equipped with an information providing device for drivers (hereinafter, the term 'own vehicle' is used for drivers, unlike other vehicles). Refers to a vehicle equipped with an information providing device).

In one embodiment, the driving route interface 700 may include an icon corresponding to the own vehicle. An icon corresponding to the own vehicle may be based on vehicle information. For example, when the own vehicle is a car, the icon corresponding to the own vehicle may be a car-shaped icon, and when the own vehicle is a van, the icon corresponding to the own vehicle may be a van-shaped icon.

In one embodiment, the driving route interface 700 may include lanes. In one embodiment, the lane may be generated based on road information received based on location information of the own vehicle. In an embodiment, the lane may be generated based on information on lanes around the host vehicle recognized by a sensor mounted in the vehicle.

In one embodiment, the driving route interface 700 may include icons corresponding to other vehicles around the own vehicle. In one embodiment, a shape of an icon corresponding to another vehicle may be determined based on information of the other vehicle. In one embodiment, the location of the icon corresponding to the other vehicle may be determined based on location information of the other vehicle relative to the own vehicle. In one embodiment, information of other vehicles or location information of other vehicles may be recognized from a sensor mounted in the own vehicle. The information providing device for drivers may place an icon corresponding to another vehicle in a relative position of the other vehicle based on the own vehicle.

In one embodiment, the driving route interface 700 may include icons corresponding to pedestrians around the own vehicle. In one embodiment, the location information of the pedestrian may be recognized from a sensor mounted on the vehicle. The information providing device for drivers may place an icon corresponding to a pedestrian at a position relative to another vehicle based on the own vehicle.

The driver's information providing device generates an icon corresponding to the own vehicle, a lane, an icon corresponding to another vehicle, or an icon corresponding to a pedestrian, and based on the received or collected information, the icon corresponding to the own vehicle is centered on the lane, An icon corresponding to another vehicle or an icon corresponding to a pedestrian may be placed to create the driving route interface 700 .

In one embodiment, the driving route interface 700 may be generated so that vehicles that may affect driving are displayed differently than other vehicles. For example, an icon corresponding to a vehicle located in front of the host vehicle may be displayed in red. For example, when the host vehicle needs to change lanes to an outside lane to stop at a stop located on the roadside, an icon corresponding to a vehicle adjacent to the right side of the host vehicle may be displayed in red.

In an embodiment, the information providing device for drivers may set a threshold distance, and generate an icon corresponding only to other vehicles or pedestrians within the threshold distance range based on the own vehicle, thereby generating the driving route interface 700. . For example, the information providing device for drivers may generate the driving route interface 700 only with icons corresponding to other vehicles or pedestrians within a range of 10 m from the own vehicle. For example, this threshold distance may be set by a control server or a boarding driver.

FIG. 7 illustrates an exemplary driving route interface 700 in which icons of lanes, a plurality of other vehicles, and pedestrians around the own vehicle 710 are arranged around the icon corresponding to the own vehicle 710 .

As described above, the interface before going to work, the interface for moving to work, and the waiting for dispatch interface may include a driving route interface.

8 is an exemplary diagram illustrating an interface before going to work created according to an embodiment.

In the present disclosure, the driver information providing device may determine the main interface as the interface before going to work in response to the state of the vehicle being the state before going to work. Alternatively, since the state of the vehicle before going to work is an initial stage after completing the connection process for driving the vehicle, the driver information providing device may determine the main interface as the interface before going to work as an initial stage. The apparatus for providing information for drivers may generate an interface before going to work in response to determining the main interface as the interface before going to work.

Referring to FIG. 8 , an interface before going to work created according to an embodiment is shown.

In one embodiment, the interface before going to work 800 is the aforementioned driving route interface 810, the interface 820 including driver information or vehicle information, the attendance authentication interface 830, or the autonomous driving function status interface. (840).

In an embodiment, the interface 820 including driver information or vehicle information may be generated based on driver information and vehicle information included in the driver information providing device.

In one embodiment, the attendance authentication interface 830 may include an object with which a driver may interact. When the boarding driver interacts with an object included in the attendance authentication interface 830, an attendance authentication signal may be generated. In one embodiment, the generated attendance authentication signal may be transmitted to the control server.

In the present disclosure, the autonomous driving function state interface 840 may refer to an interface displaying operating states of one or more devices, functions, etc. related to autonomous driving mounted to implement autonomous driving of a vehicle. Referring to FIG. 8 , the autonomous driving function state interface 840 may display whether one or more devices, functions, etc. related to autonomous driving are normally operating through indicators for each of one or more devices, functions, etc. related to autonomous driving. there is. This is provided as a simple example, and any suitable manner capable of indicating the operational status of a device, function, etc. may be applied.

In one embodiment, the interface 800 before going to work may further include an attendance authentication guide message. For example, the attendance authentication guide message may include a message suggesting that the driver perform attendance authentication, such as "Please press the attendance button."

In one embodiment, in response to the attendance authentication signal being received, the state of the vehicle may be switched to a work place movement state.

9 is an exemplary diagram illustrating a workplace movement interface created according to an embodiment.

In the present disclosure, the driver's information providing device may determine the main interface as the workplace movement interface in response to the vehicle state being switched to the workplace movement state. The apparatus for providing information for an engineer may generate a workplace movement interface in response to determining the main interface as the workplace movement interface.

Referring to FIG. 9 , a workplace movement interface created according to an exemplary embodiment is illustrated.

In one embodiment, the workplace movement interface 900 includes the above-described driving route interface 910, a route guidance interface 920 configured to include destination information, a navigation map, and driving method guidance, or an autonomous driving function status interface. (930).

In one embodiment, the route guidance interface 920 may be generated based on destination information, vehicle location information, road information based on vehicle location information, traffic information, and the like.

In one embodiment, the destination may be set automatically. For example, an information providing device for a driver may set an arbitrary point in the workplace as a destination. For example, the driver's information providing device may set a point closest to the location of the vehicle among points on a predefined autonomous driving route as a destination. In this way, a boarding driver who has completed attendance verification can immediately drive a vehicle to a place of work or an autonomous driving route.

In one embodiment, the information about the destination may include a name, estimated time of arrival, or remaining distance.

In one embodiment, in response to the location of the vehicle reaching the destination, that is, entering the autonomous driving route from the general driving route, the state of the vehicle may be switched to a dispatch waiting state.

In one embodiment, the driving mode of the vehicle may be switched to the autonomous driving mode in response to the location of the vehicle reaching the destination, that is, entering the autonomous driving route from the normal driving route.

10 is an exemplary diagram illustrating an dispatch standby interface generated according to an exemplary embodiment.

In the present disclosure, the driver's information providing device may determine the main interface as the dispatch standby interface in response to the change of the vehicle status to the dispatch standby status. The driver's information providing device may generate the dispatch waiting interface in response to determining the main interface as the dispatch waiting interface.

Referring to FIG. 10 , an dispatch standby interface generated according to an exemplary embodiment is illustrated.

In one embodiment, the dispatch waiting interface 1000 may include the aforementioned driving route interface 1010 , route guidance interface 1020 , notification interface 1030 , or autonomous driving function status interface 1040 .

In one embodiment, route guidance interface 1020 may include a navigation map. In one embodiment, route guidance provided by the route guidance interface 1020 may be guidance on a predefined route. For example, a predefined route may be a work place or an autonomous driving route. Also, the predefined route may be a circuit route having the same origin and destination. In this case, if the vehicle is not assigned a trip, the vehicle will continue to travel on the circuit route.

In one embodiment, the notification interface 1030 may include various notifications related to vehicle trip assignments. For example, as shown, the notification interface 1030 may include a message indicating that a vehicle is waiting for dispatch. For example, the notification interface 1030 may include information on the nearest boarding point on a circuit route. For example, the notification interface may include a message indicating that autonomous driving is in progress.

In one embodiment, the process of determining and displaying the main interface as the workplace movement interface by the driver's information providing device may be omitted. For example, when a driver authenticates attendance at a work place or on an autonomous driving route, the vehicle state may skip the work place travel state and switch to a waiting for dispatch state. In this case, a process related to the work place movement interface may be omitted. can

In one embodiment, the main interface to be displayed on the information providing device for articles may include a condition activation object. A conditional activation object refers to an object that is activated only when a predefined condition is met and the driver can interact with it. When a condition activation object does not meet a predefined condition, it may be deactivated and displayed on the main interface.

The predefined condition may relate to a condition in which the vehicle does not become dangerous even when the driver interacts with an object included in the driver's information providing device. For example, the predefined condition may be a condition related to vehicle speed. For example, the conditional activation object may be activated only when the value of the current speed of the vehicle is 0. For example, the predefined condition may be a condition related to the state of the vehicle. For example, the conditional activation object may be activated only when the state of the vehicle is a waiting state for dispatch, a rest state, or a state before going to work.

In one embodiment, the driver's information providing device may display the driver's menu interface when the driver interacts with the condition activation object.

In one embodiment, the driver menu interface may include one or more objects that the driver can interact with, and the driver interacts with the corresponding object to obtain driver information, vehicle information, driving history, and driver information. Work history, work plan of the driver, notices received from the control server (or vehicle management server), information such as settings of the driver's information providing device, terms and conditions, policies, driver's manual, etc. may be provided. For example, the boarding driver may interact with an object corresponding to the notice to check the notice received from the control server.

Demand response type vehicles are in a state in which they can be allocated for operation only when the state of the vehicle is in a standby state for dispatch. A process of providing driving of a demand response type vehicle after being allocated driving will be described later with reference to FIGS. 11 and 12 .

As described above, various vehicle states may include states related to rest.

While the demand response type vehicle is in operation, when it is not long before the scheduled break time, the driver information providing device may inform the driver that the scheduled break time is short and provide information related to the break.

In the present disclosure, when the remaining time until the scheduled break time reaches the first hour, the driver's information providing device may display a break guidance interface.

In one embodiment, the first time may be any suitable time such as 5 minutes, 10 minutes, 20 minutes, etc. In one embodiment, the first time is a boarding driver and a corporation to which the boarding driver belongs (subject to provide vehicle service) Alternatively, it may be the time set by the control server.

In one embodiment, the break guidance interface is an interface notifying the boarding driver that the scheduled break time is short, and may include a message such as "It is the scheduled break time in 10 minutes."

In the present disclosure, after the driver's information providing device displays the rest guidance interface, if the vehicle status is a vehicle dispatch standby status, the vehicle status may be immediately switched to a rest area movement status. On the other hand, if the vehicle's state is the driving state, after receiving the driving end signal, the vehicle's state may be switched to the resting place moving state. In one embodiment, when the remaining time until the scheduled break time is equal to or less than the first hour, and the vehicle is in a running state, the vehicle may be switched to a state in which additional dispatch is not received.

In the present disclosure, the driver's information providing device may determine the main interface as the resting place moving interface in response to the vehicle state being switched to the resting place moving state. The device for providing information for drivers may generate a resting place moving interface in response to determining the main interface as the resting place moving interface.

In the present disclosure, the rest area movement interface may be similar to the work place movement interface 900 described above with reference to FIG. 9 . That is, the rest area movement interface may include a driving route interface and a route guidance interface configured to include destination information, a navigation map, and driving method guidance. However, the destination in the embodiment of the resting place movement interface will be set to the resting place.

In one embodiment, when the location of the vehicle reaches a destination, that is, a resting place, the state of the vehicle may be switched to a resting state.

In the present disclosure, when the vehicle is in a rest state and the time remaining until the scheduled work time after the break reaches the second hour, the driver's information providing device may display a break end guidance interface.

In one embodiment, the second time may be any suitable time such as 5 minutes, 10 minutes, 20 minutes, etc. In one embodiment, the second time is a boarding driver and a corporation to which the boarding driver belongs (subject to provide vehicle service) Alternatively, it may be the time set by the control server.

In one embodiment, the break end guide interface is an interface notifying the boarding driver that the break end time is about to end, and may include a message such as “The break is scheduled to end in 10 minutes.”

In the present disclosure, when the time remaining until the scheduled work time after the break reaches 0, the state of the vehicle may be switched to a waiting state for dispatch. Similarly, the device for providing driver information may determine the main interface as the waiting interface for dispatching in response to the state of the vehicle being switched to the waiting for dispatching state.

In the present disclosure, when the time remaining until the shift end time reaches the third hour, the driver's information providing device may display a shift end guide interface.

In one embodiment, the third time may be any suitable time such as 5 minutes, 10 minutes, 20 minutes, etc. In one embodiment, the third time is a boarding driver and a corporation to which the boarding driver belongs (subject to provide vehicle service) Alternatively, it may be the time set by the control server.

In one embodiment, the shift end guide interface is an interface for notifying the boarding driver that the scheduled shift end time is about to end, and may include a message such as “The shift end is scheduled to end in 10 minutes.”

In the present disclosure, after the driver's information providing device displays the duty end guidance interface, if the vehicle status is in the waiting for dispatch status, the status of the vehicle may be immediately switched to the scheduled departure status. On the other hand, if the vehicle is in a driving state, after receiving the driving end signal, the vehicle state may be switched to an leaving work state. In one embodiment, when the remaining time until the end of the shift is equal to or less than the third hour and the vehicle is in a running state, the vehicle may be switched to a state in which additional dispatch is not received.

In the present disclosure, in response to the time remaining until the end of the shift time reaching 0, the state of the vehicle may be switched to a state of moving to work.

In one embodiment, the driver's information providing device may determine the main interface as an interface for moving to work in response to the state of the vehicle being switched to the moving to work state. The driver's information providing device may generate the home office mobile interface in response to determining the main interface as the home office mobile interface.

In the present disclosure, the work place movement interface may be similar to the work place movement interface 900 described above with reference to FIG. 9 . That is, the homecoming movement interface may include a driving route interface and a route guidance interface configured to include destination information, a navigation map, and driving method guidance. However, the destination in the embodiment of the mobile interface for leaving work will be set to the place of work.

In one embodiment, when the location of the vehicle reaches a destination, that is, the place of work, the state of the vehicle may be switched to an end-of-work state.

Hereinafter, a process of providing service of a demand response type vehicle in relation to passengers getting on and off after the vehicle is allocated will be described.

In the present disclosure, when the state of the vehicle is in the dispatch waiting state, the vehicle may be assigned to drive. That is, when the vehicle is in an dispatch waiting state, an dispatch request signal may be received.

In one embodiment, in response to the dispatch request signal being received, the state of the vehicle may be switched to a boarding location moving state.

11 is an exemplary diagram illustrating a boarding point movement interface generated according to an embodiment.

In the present disclosure, the driver's information providing device may determine the main interface as the boarding location moving interface in response to the vehicle state being switched to the boarding location moving state. The device for providing information for drivers may generate a boarding location moving interface in response to determining the main interface as the boarding location moving interface.

Referring to FIG. 11 , a boarding point movement interface created according to an exemplary embodiment is illustrated.

In one embodiment, the boarding point movement interface 1100 is the above-described driving route interface 1110, a route guidance interface 1120 configured to include information about a destination, a navigation map, and driving method guidance, or an autonomous driving function state. interface 1130.

In one embodiment, the destination is a boarding location and may be automatically set based on information included in the dispatch request signal.

In one embodiment, the information about the destination may include a name, estimated time of arrival, or remaining distance.

In one embodiment, the dispatch request signal may be received even when the vehicle is not in the dispatch waiting state. For example, when the vehicle is a vehicle capable of driving only 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 may be received. In this embodiment, when a new destination included in a new dispatch request signal arrives earlier than an existing destination on a predetermined route, it may be referred to as a stopover addition situation. On the other hand, when the new destination included in the new dispatch request signal arrives later than the existing destination on a predetermined route, it may be referred to as a dispatch addition situation. In both cases, if a new destination is added by a new dispatch request signal, each destination may be referred to as a passing destination.

In one embodiment, when a new dispatch request signal is received, information on the destination may be updated based on information on the existing destination and information on the new destination included in the new dispatch request signal. In one embodiment, the device for providing information for drivers may display an update-related notification message in response to information on the destination being updated.

In one embodiment, when the destination includes a plurality of transit destinations, information about the destination included in the route guidance interface 1120 includes information about the transit destination that arrives first among the plurality of transit destinations and which arrives next. Information on transit destinations may be displayed while being switched according to a predetermined cycle. For example, the driver's information providing device may display the first transit destination for 4 seconds and then display the second transit destination for 2 seconds.

When the state of the vehicle is in the boarding point movement state, when the vehicle arrives at the boarding point and boards passengers, the state of the vehicle may be switched to the drop off point movement state. In the process of switching the state of the vehicle from the boarding point moving state to the dropping point moving state, there may be several embodiments.

In one embodiment, when the distance between the vehicle and the destination (boarding location) is equal to or less than the first threshold distance, the driver's information providing device may display an arrival notification message. In one embodiment, in response to the fact that the distance between the vehicle and the destination (boarding location) is equal to or less than the first threshold distance, the driver information providing device may display a boarding point arrival completion object. The boarding point arrival completion object may refer to an object for generating a boarding point arrival completion signal through interaction with the boarding driver. The first threshold distance may be arbitrarily set to a value suitable for notifying that the destination is almost reached, such as 50m, 100m, or 150m.

In one embodiment, in response to the interaction with the boarding point arrival completion object, the driver's information providing device may display the boarding completion object. The boarding completion object may refer to an object for generating a boarding completion signal through interaction with the boarding driver. In one embodiment, in response to interacting with the ride complete object, a ride complete signal may be generated, and in response to receiving the ride complete signal, the state of the vehicle may be transitioned to a drop-off moving state.

In one embodiment, in response to interaction with the boarding point arrival completion object, the driver's information providing device may display a timer. A timer may count down a predetermined amount of time. In the present disclosure, a vehicle does not wait at the boarding point until a passenger gets on, but when a predetermined time elapses without a passenger boarding the vehicle, the vehicle is canceled so that a smooth demand response type transportation system can be provided. there is. That is, when the boarding completion signal is not received until a predetermined time elapses, the state of the vehicle may be switched to a waiting state for dispatching. The predetermined time may be arbitrarily set to a value suitable for providing a smooth demand-responsive transportation system, such as 3 minutes or 5 minutes.

In the present disclosure, the driver's information providing device may determine the main interface as the drop-off location movement interface in response to the vehicle state being switched to the drop-off location movement state. The device for providing information for drivers may generate a drop-off point move interface in response to determining the main interface as the drop-off point move interface.

In the present disclosure, the drop-off point movement interface may be similar to the pick-up point movement interface 1100 described above with reference to FIG. 11 . That is, the drop-off location movement interface may include a driving route interface or a route guidance interface 1120 configured to include information about a destination, a navigation map, and driving method guidance. In this case, the destination may be a destination that is automatically set based on information included in the dispatch request signal. In addition, embodiments related to the boarding point movement interface described above may be equally applied.

When the vehicle is in the drop-off point moving state, when the vehicle arrives at the drop-off point and drops passengers off, the vehicle state may be switched to a dispatch waiting state. In the process of changing the state of the vehicle from the moving state to the dispatching state, there may be various embodiments.

In one embodiment, when the distance from the destination (drop-off point) of the vehicle is equal to or less than the second threshold distance, the driver's information providing device may display an arrival notification message. In one embodiment, in response to the fact that the distance between the vehicle and the destination (drop-off point) is equal to or less than the second threshold distance, the driver information providing device may display a drop-off point arrival completion object. The drop-off point arrival completion object may refer to an object for generating a drop-off point arrival completion signal through interaction with the boarding driver. The second threshold distance may be arbitrarily set to a value suitable for notifying that the destination is almost reached, such as 50m, 100m, or 150m. The second threshold distance may be the same as or different from the first threshold distance.

In one embodiment, in response to an interaction with the drop-off arrival completion object, the driver information providing device may display the drop-off completion object. The getting off completion object may refer to an object for generating a getting off completion signal through interaction with the driver. In one embodiment, in response to the interaction with the getting off completion object, a getting off completion signal may be generated, and in response to receiving the getting off completion signal, the state of the vehicle may be switched to a dispatch waiting state.

In one embodiment, there may be multiple 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 an autonomous driving mode by a driver's manipulation. In one embodiment, the vehicle may be switched to an autonomous driving mode in an autonomous driving route that is an autonomous driving route.

In one embodiment, when the vehicle enters a compulsory manual driving area in which driving in the demand response autonomous driving mode is not possible, the driver's information providing device may display a manual driving mode switching request message. The manual driving mode switching request message may include a message requesting the driver to switch to the manual driving mode, such as “Please switch to the manual driving mode”.

In one embodiment, the forced manual driving area may include a child protection area.

In one embodiment, when the vehicle belongs to the compulsory manual driving zone, the vehicle cannot be switched to autonomous driving mode by the driver.

In one embodiment, when the driving mode of the vehicle is switched, the driver's information providing device may display a driving mode switching message. The driving mode switching message may include a message indicating that the driving mode has been switched, such as "Converted to manual driving mode" or "Converted to autonomous driving mode".

12 is an exemplary diagram illustrating a seat information interface generated according to an embodiment.

In one embodiment, the boarding point movement interface may further include a seat information interface 1200 . For example, if the vehicle is a van, passengers may also be assigned a seat to be seated in the vehicle, and the seat information interface 1200 may be an interface for displaying information about the assigned seat accordingly.

Referring to FIG. 12 , a seat information interface 1200 including objects corresponding to a plurality of seats 1C, 2A, 3A, 3C, 4A, 4B, and 4C including a driver's seat 1210 is shown.

In one embodiment, the seat information interface may be created based on vehicle seat information. The seat information of the vehicle may be information transmitted from the control server or stored in an information providing device for drivers. The information providing device for drivers may generate a seat layout displaying the arrangement of a plurality of seats based on seat information of the vehicle.

In one embodiment, each of the plurality of seats may be differently displayed according to the seat state of each of the plurality of seats in the generated seat layout. In one embodiment, the seat state may be, for example, any one of a boarding completion state, a boarding scheduled state, and a remaining state. The boarding complete state may refer to a state in which a passenger has boarded at a boarding location and is seated in a corresponding seat, and a boarding scheduled state may refer to a state in which a passenger who is scheduled to board is scheduled to be seated even though the passenger has not yet boarded at the boarding location. The remaining state may refer to a state in which there is no passenger scheduled to sit in the seat because no seat is assigned.

Plan to Board Referring to FIG. 12 , objects corresponding to seats 2A and 3A in the seat layout are colored dark, which may indicate a boarding completion state. Referring to FIG. 12 , objects corresponding to seats 4A, 4B, and 4C in the seat layout are processed as stripes, which may indicate a scheduled boarding state. Referring to FIG. 12 , objects corresponding to seats 1C and 3C are not processed in any way, which may indicate a residual state. This is provided as a simple example, and any suitable manner of indicating seat conditions may be applied.

In one embodiment, the seat information interface 1200 generated by the information providing device for drivers may be based on seat information data. The seat information data may be transmitted from the 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 created in conjunction with a control server or a user terminal.

In an embodiment, in a process of distributing a user, when there are a plurality of passengers, seats in which the passengers are seated as well as the dispatched vehicles may be determined. Information on the boarding location and expected seat of the determined passenger may be transmitted to the demand response type vehicle, and the driver's information providing device determines the status of the scheduled seat based on the transmitted information until reaching the corresponding boarding location. A boarding scheduled state may be determined, and a seat information interface 1200 may be generated.

In one embodiment, various schemes may be applied to assign seats to passengers. For example, when one user terminal requests boarding for a plurality of people, adjacent seats may be assigned to the plurality of people. For example, when one user terminal requests boarding for one person, a seat that has no left and right adjacent seats may be preferentially assigned. For example, a seat in an adjacent boarding state or a seat with the smallest number of adjacent seats in a scheduled boarding state may be preferentially assigned. In addition, any suitable manner of assigning seats may be applied.

Meanwhile, the seat information data may be modified by the driver information providing device, and the corrected seat information data may be transmitted to the control server. In one embodiment, the driver may modify or transmit the seat information data by interacting with the seat information interface displayed on the driver information providing device.

For example, a vehicle may leave a boarding point without a passenger who has decided to board at a specific boarding point. In this case, the seat in the scheduled boarding state while leaving the boarding area should be changed to the remaining seat, not converted to the boarding completed state.

Accordingly, in one embodiment, an object corresponding to each of a plurality of seats displayed on the seat layout may be created so that the driver can interact with them. In one embodiment, when a boarding driver interacts with an object corresponding to a seat in which a boarding state is to be boarded or a seat in which boarding is complete, the seat state of the corresponding seat may be changed to a remaining seat. When a seat state of a corresponding seat is changed to a remaining seat, the device for providing information for a driver may change an object corresponding to the corresponding seat in the seat layout to a remaining seat and display the changed object. The device for providing information for drivers may modify or transmit seat information data based on the changed seat condition. In this way, the boarding driver can forcibly change the seat state to the remaining seat state.

In one embodiment, the main interface generated by the driver's information providing device may further include a driving control interface. The operation control interface may refer to an interface configured to allow a driver to manually or forcibly cancel the assignment of a vehicle or stop the assignment of a vehicle through interaction. In one embodiment, the operation control interface may include a operation cancellation object or a dispatch stop object. The operation cancellation object may be an object through which the driver interacts to cancel the vehicle assignment, and the dispatch stop object may be an object through which the driver interacts to stop dispatching. In one embodiment, the operation cancellation object may be activated only in a boarding point moving state.

In one embodiment, when the driver interacts with the service cancellation object or the dispatch stop object, the driver information providing device may generate a reason input interface capable of inputting a reason. In one embodiment, an interface capable of inputting a reason may be generated to select one of a plurality of predetermined reasons. For example, the plurality of pre-determined reasons may include a driver reason, a passenger reason, and an accident.

In one embodiment, when the reason input by the driver through the reason input interface corresponds to 'occurrence of an accident', the state of the vehicle may be switched to an accident occurrence state. In the present disclosure, an accident occurrence state may refer to a state in which operation is stopped and vehicle assignment is stopped until the accident is dealt with.

In one embodiment, in response to the state of the vehicle being converted to an accident occurrence state, the driver's information providing device may generate an accident occurrence interface. The accident occurrence interface may include an object through which the driver interacts to generate an accident handling completion signal. In response to the reception of the accident processing completion signal, the state of the vehicle may be switched to a waiting state for dispatch.

In addition to the above-described interfaces, interfaces that may be generated by the information providing device for drivers for display may include any appropriate interfaces required for vehicle driving. For example, an interface indicating the driving state of the vehicle may be included. For example, an interface indicating whether sensors or functions of the vehicle are operating may be included.

In the present disclosure, a device for providing information for passengers may generate an interface (hereinafter referred to as 'interface for passengers') to be displayed on the device for providing information for passengers. The passenger interface may be configured to display necessary information to passengers aboard the demand response vehicle.

In one embodiment, the passenger interface may be configured to include part or all of the interface displayed on the driver information providing device.

In one embodiment, the passenger interface may include a travel route interface. In one embodiment, the driving route interface included in the passenger interface may be one in which some information (eg, an icon corresponding to a pedestrian) is omitted from the driving route interface included in interfaces displayed on the driver information providing device.

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 one in which some information (eg, driving method guidance) is omitted from route guidance interfaces included in interfaces displayed on the driver information providing device.

In one embodiment, the passenger interface may include a seat information interface. In one embodiment, the seat information interface included in the passenger interface may be a seat information interface included in interfaces displayed on the driver information providing device, and some information (eg, current seat position) may be added.

In one embodiment, the passenger interface may include a stop information interface. The stop information interface may be configured to display information about a stop at which the demand-responsive vehicle stops for getting on and off passengers. The stop information interface may include information about the first stop, and may further include information about the next stop. In one embodiment, information about the first stop to be reached and information about the next stop to be reached may be alternately displayed at a predefined period.

In one embodiment, the passenger interface may include a guide message interface. A guide message that may be included in the guide message interface may include, for example, a message to fasten a seat belt and a message to prepare to get off. In one embodiment, in response to the driving mode of the vehicle being switched from the autonomous driving mode to the manual driving mode, the guidance message may include a message indicating that the driving mode has been switched.

In addition to the aforementioned interface, the passenger interface that the device for providing information for passengers can generate for display may include any suitable interface necessary for providing information to passengers.

Hereinafter, an operation of an external display device in a process of providing driving of a demand response type vehicle will be described.

13 is an exemplary diagram for explaining an operation of an external display device according to an exemplary embodiment.

In one embodiment, the external display device may collect data including vehicle information, vehicle status, vehicle location information, destination information, or signals generated by a device mounted on the vehicle.

In one embodiment, the external display device may generate an external display interface based on the collected data, and may be associated with an information providing device for drivers or an information providing device for passengers. In particular, an external display interface may be created based on interfaces included in various interfaces generated by the above-described information providing device for articles. In one embodiment, the external display device and the information providing device for articles may be substantially the same device including a common processor.

In one embodiment, the external display device may include a plurality of 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 on the front of the vehicle, and the rear display may be a display installed on the rear of the vehicle.

Referring to (a) of FIG. 13 , a front display 1310 and a rear display 1320 are shown. As shown, the front display 1310 may be installed on the front of the vehicle, and the rear display 1320 may be installed on the rear of the vehicle. In (a) of FIG. 13 , external display interfaces displayed on the front display 1310 and the rear display 1320 are different, but may be created identically. That is, the external display device may create a front external display interface and a rear external display interface.

In an embodiment, the external display device may differently generate a front external display interface and a rear external display interface based on the collected data. For example, a subject viewing the front external display and a subject mainly viewing the rear external display may be different, and accordingly, content suitable for display on each external display may be different. For example, when the vehicle state is in a boarding point moving state or a dropping point moving state, as shown in (a) of FIG. In 1320, only a message indicating that the vehicle is in operation may be displayed. For example, when a vehicle enters a child protection area, the front display 1310 displays the name of the vehicle and the tour route name as shown in FIG. 13(b), and the rear display 1320 displays the As shown in (d), only a message indicating that it is a child protection area may be displayed. For example, when the vehicle is stopped at a pick-up point (or drop-off point) for passengers to get on (or get off) (e.g., after the driver interacts with the pick-up point arrival completion object and before inputting a pick-up completion signal) ), the front display 1310 displays the vehicle name and tour route name as shown in FIG. 13(b), and the rear display 1320 displays passengers getting on and off as shown in FIG. Only a message notifying you can be displayed.

In one embodiment, the front display interface and the rear display interface for various situations may be as shown in Table 1 below, but are not limited thereto.

In one embodiment, the external display interface may be generated based on vehicle information. For example, an external display interface may be created to display the name of the vehicle. The name of the vehicle may refer to a name capable of identifying which vehicle among a plurality of vehicles in the demand-responsive transportation system. For example, if the vehicle is a vehicle that runs along a circuit route, an external display interface may be created to display the circuit route name. Referring to (b) of FIG. 13 , the name of the vehicle and the tour route name may be displayed on the external display interface.

In one embodiment, the external display interface may be generated based on the state of the vehicle. For example, if the state of the vehicle is not in operation, that is, any one of the state before going to work, moving to work place, moving to resting place, resting state, scheduled to leave work, moving to work state, and end of work state, the vehicle is not running An external display interface can be created to display messages. As an example, a message indicating that the vehicle is not in operation may include a message such as “preparing for operation”.

As another example, when the state of the vehicle is a moving state to a resting place, the message may include a message “to stand by”. As another example, when the state of the vehicle is a moving state from work, the message may include a message such as “go to the garage”.

For example, when the state of the vehicle is in an accident state, the external display interface may include a vehicle inspection message “inspecting the vehicle” as shown in (c) of FIG. 13 .

In one embodiment, the external display interface may be generated based on vehicle location information. For example, the external display device may receive the location of the vehicle, and in response to the received location of the vehicle entering a specific area, an external display interface may be generated to include a specific message. As an example, the specific message may be a message informing that a specific area has been entered. As a specific example, the specific area may be a special driving road, such as a child protection area or an automobile exclusive road, instead of a general driving road. For example, when a vehicle enters a child protection area, a message indicating that the vehicle enters a child protection area may be displayed as shown in (d) of FIG. 13 . As another specific example, when the vehicle enters a compulsory manual driving area where the vehicle cannot operate in the autonomous driving mode and the driving mode of the vehicle is switched to the manual driving mode, an external display interface is generated to display a notification message for switching to the manual driving mode. can For example, the manual driving mode switching notification message may include a message indicating that the driving mode has been switched, such as “I drive in the manual driving mode”. For example, the compulsory manual operation area may include a child protection area.

In this embodiment, the location information of the vehicle is independently received by the external display device separately from other devices such as the driver information providing device, and accordingly, the external display device independently of the driver information providing device based on the location information interfaces can be created.

In one embodiment, the external display interface may be created based on information about the destination. For example, the name of the destination may be periodically displayed on the external display interface according to a predetermined cycle.

In one embodiment, the external display interface may be generated based on a signal generated by a vehicle-mounted device. For example, in response to interacting with the boarding point arrival completion object, an external display interface may be generated to include a message indicating that a passenger is boarding. A message indicating that a passenger is boarding may be maintained until a boarding completion signal is received. For example, in response to interaction with the drop-off arrival completion object, an external display interface may be generated to include a message indicating that a passenger is getting off. A message indicating that the passenger is getting off may be maintained until a getting off completion signal is received. For example, as shown in (e) of FIG. 13 , a message indicating that a passenger is boarding or alighting may include a message “a passenger is getting on or off”.

In one embodiment, the external display interface may be created based on functions operated in the vehicle. For example, when the vehicle makes a right turn, an external display interface may be generated to display a message or an object indicating that the vehicle will make a right turn in response to a right turn signal being turned on.

14 is a flowchart of a method for providing an interface for an article according to an exemplary embodiment.

The operations shown in FIG. 14 can be executed by the aforementioned information providing device for articles. Specifically, the operations shown in FIG. 14 may be executed by a processor included in the aforementioned information providing device for articles.

In operation 1410, the processor may determine a main interface displaying vehicle driving service information based on the state of the vehicle.

In one embodiment, step 1410 includes determining the main interface as the pre-work interface, determining the main interface as the workplace travel interface in response to the state of the vehicle being switched to the workplace travel state, and the vehicle state being ready for dispatch. In response to the transition to the state, determining a main interface as an dispatch standby interface.

In one embodiment, when the state of the vehicle is in the state before going to work, in response to receiving the attendance authentication signal, the state of the vehicle may be switched to the work place movement state.

In one embodiment, the state of the vehicle may be switched to a waiting state for dispatch in response to the location of the vehicle entering an autonomous driving route when the vehicle is in a work place movement state.

In an embodiment, the interface before going to work may include a driving route interface, an interface including driver information and vehicle information, an attendance authentication interface, and an autonomous driving function status interface.

In one embodiment, the workplace movement interface may include a driving route interface, a route guidance interface including destination information, a navigation map, and driving method guidance, and an autonomous driving function status interface.

In step 1420, the processor may generate the determined main interface.

In one embodiment, after step 1420, the processor activates and displays a first interactable object in response to meeting a predefined condition, and in response to not meeting a predefined condition, the processor activates and displays the first object. The object may be deactivated and displayed, and an article menu interface may be displayed in response to receiving an input for interacting with the activated first object.

In one embodiment, the processor displays a break 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 the first time, and the state of the vehicle is a dispatch waiting state. , the vehicle state is switched to the resting place moving state, and when the vehicle state is the driving state, the vehicle state is switched to the resting place moving state in response to receiving the operation end signal, and the vehicle state is the resting place moving state. In response to switching to , the main interface may be determined as the rest area movement interface.

In one embodiment, the processor displays 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 reaches the second time, and the schedule for work after the break In response to the remaining time reaching 0, the state of the vehicle may be switched to a waiting state for dispatch.

In one embodiment, the processor displays an end-of-shift guidance interface in response to the time remaining until the end of shift time included in the shift setting data included in the driver's information reaches a third time, and the state of the vehicle is the running state. In this case, in response to receiving the operation end signal, the state of the vehicle is switched to the leaving scheduled state. In response to the time reaching 0, the state of the vehicle is switched to the movement to work state, and in response to the state of the vehicle to be switched to the movement to work state, the main interface may be determined as the movement to work interface.

15 is a block diagram of a device for providing an interface for a driver according to an exemplary embodiment.

The device for providing an interface for articles in FIG. 15 may correspond to the above-described device for providing information for articles.

Referring to FIG. 15 , an apparatus for providing an interface for a driver 1500 may include a communication unit 1510, a processor 1520, and a DB 1530. In the interface providing device 1500 for engineers in FIG. 15 , only components related to the embodiment are shown. Accordingly, those skilled in the art can understand that other general-purpose components may be further included in addition to the components shown in FIG. 15 .

The communication unit 1510 may include one or more components that enable wired/wireless communication with an external server or external device. For example, the communication unit 1510 may include at least one of a short-range communication unit (not shown), a mobile communication unit (not shown), and a broadcast reception unit (not shown).

The DB 1530 is hardware that stores various data processed in the device for providing an interface for drivers 1500, and may store programs for processing and controlling the processor 1520. The DB 1530 may store payment information, user information, and the like.

The DB 1530 includes random access memory (RAM) such as dynamic random access memory (DRAM) and static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and CD-ROM. ROM, Blu-ray or other optical disk storage, hard disk drive (HDD), solid state drive (SSD), or flash memory.

The processor 1520 controls overall operations of the driver interface providing device 1500 . For example, the processor 1520 may generally control an input unit (not shown), a display (not shown), a communication unit 1510, and the DB 1530 by executing programs stored in the DB 1530. The processor 1520 may control the operation of the article interface providing device 1500 by executing programs stored in the DB 1530 .

The processor 1520 may control at least some of the operations of the device for providing an interface for articles 1500 described above with reference to FIGS. 1 to 14 .

The processor 1520 includes application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, and microcontrollers. It may be implemented using at least one of micro-controllers, microprocessors, and electrical units for performing other functions.

As an embodiment, the driver interface providing device 1500 may be a mobile electronic device. For example, the driver interface providing device 1500 is implemented as a smart phone, tablet PC, PC, smart TV, PDA (personal digital assistant), laptop, media player, navigation device, camera-equipped device, and other mobile electronic devices. It can be. In addition, the driver interface providing device 1500 may be implemented as a wearable device having a communication function and a data processing function, such as a watch, glasses, a hair band, and a ring.

As another embodiment, the driver interface providing device 1500 may be an electronic device embedded in a vehicle. For example, the driver interface providing device 1500 may be an electronic device inserted into a vehicle through tuning after production.

As another embodiment, the driver interface providing device 1500 may be a server located outside the vehicle. A server may be implemented as a computer device or a plurality of computer devices that communicate over a network to provide commands, codes, files, content, services, and the like. The server may receive data necessary for determining a moving path of the vehicle from devices mounted on the vehicle, and determine the moving path of the vehicle based on the received data.

As another embodiment, a process performed by the driver interface providing device 1500 may be performed by at least some of a mobile electronic device, an electronic device embedded in a vehicle, and a server located outside the vehicle.

Embodiments according to the present invention may be implemented in the form of a computer program that can be executed on a computer through various components, and such a computer program may be recorded on a computer-readable medium. At this time, the medium is a magnetic medium such as a hard disk, a floppy disk and a magnetic tape, an optical recording medium such as a CD-ROM and a DVD, a magneto-optical medium such as a floptical disk, and a ROM hardware devices specially configured to store and execute program instructions, such as RAM, flash memory, and the like.

Meanwhile, the computer program may be specially designed and configured for the present invention, or may be known and usable to those skilled in the art of computer software. An example of a computer program may include not only machine language code generated by a compiler but also high-level language code that can be executed by a computer using an interpreter or the like.

According to one embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. Computer program products may be traded between sellers and buyers as commodities. A computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or through an application store (eg Play Store™) or between two user devices. It can be distributed (e.g., downloaded or uploaded) directly or online. In the case of online distribution, at least part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a manufacturer's server, an application store server, or a relay server's memory.

The steps constituting the method according to the present invention may be performed in any suitable order unless an order is explicitly stated or stated to the contrary. The present invention is not necessarily limited according to the order of description of the steps. The use of all examples or exemplary terms (eg, etc.) in the present invention is simply to explain the present invention in detail, and the scope of the present invention is limited due to the examples or exemplary terms unless limited by the claims. it is not going to be In addition, those skilled in the art can appreciate that various modifications, combinations and changes can be made according to design conditions and factors within the scope of the appended claims or equivalents thereof.

Therefore, the spirit of the present invention should not be limited to the above-described embodiments and should not be determined, and all scopes equivalent to or equivalently changed from the claims as well as the claims described below are within the scope of the spirit of the present invention. will be said to belong to

Claims (9)

In the method of providing an interface for articles,
determining a main interface displaying vehicle operation service information based on a vehicle state; and
Generating the determined main interface; including,
Determining the main interface,
determining the main interface as an interface before going to work;
determining the main interface as a workplace movement interface in response to the state of the vehicle being switched to the workplace movement state; and
determining the main interface as an dispatch standby interface in response to the state of the vehicle being switched to the dispatch wait state;
Including,
When the state of the vehicle is the state before going to work, in response to receiving the attendance authentication signal, the state of the vehicle is switched to the work place travel state, and the destination is the closest to the location of the vehicle among points on a predefined autonomous driving route. set to the nearest point,
When the state of the vehicle is in the work place movement state, the vehicle is switched to a waiting state for dispatch in response to the vehicle's location entering the autonomous driving route;
The workplace movement interface,
Including a route guidance interface including information about the destination, a navigation map and driving method guidance,
method.
delete According to claim 1,
The interface before going to work,
driving route interface;
an interface including driver information and vehicle information;
attendance authentication interface; and
autonomous driving function status interface;
including,
method.
According to claim 1,
The workplace movement interface,
driving route interface; and
autonomous driving function status interface;
Including more,
method.
According to claim 1,
The method,
in response to meeting a predefined condition, activating and displaying a first object capable of interaction;
in response to not satisfying the predefined condition, inactivating and displaying the first object; and
displaying an article menu interface in response to receiving an input for interacting with the activated first object;
Including more,
method.
According to claim 1,
The method,
displaying a break guide interface in response to the remaining time until the scheduled break time included in the duty setting data included in the driver's information reaching a first time;
switching the vehicle state to a rest area movement state when the state of the vehicle is a vehicle dispatch waiting state;
switching the state of the vehicle to a resting place moving state in response to receiving a driving end signal when the state of the vehicle is a driving state; and
determining the main interface as a resting place moving interface in response to the state of the vehicle being switched to a resting place moving state;
including,
method.
According to claim 6,
displaying a break end guide interface in response to a time remaining until a scheduled work time after a break included in the work setting data included in the information of the driver reaching a second time; and
In response to the time remaining until the scheduled work time after the break reaches 0, switching the state of the vehicle to a waiting state for dispatching;
including,
method.
In the device for providing an interface for drivers,
a memory in which at least one program is stored; and
A processor operating by executing the at least one program; including,
the processor,
determine a main interface displaying information about vehicle driving services based on the state of the vehicle;
Create the determined main interface,
Determining the main interface,
Determining the main interface as the interface before going to work, and responding to the state of the vehicle being switched to the work place movement state, determining the main interface as the work place movement interface, and responding to the state of the vehicle being switched to the dispatch waiting state and determining the main interface as an dispatch standby interface,
When the state of the vehicle is the state before going to work, in response to receiving the attendance authentication signal, the state of the vehicle is switched to the work place travel state, and the destination is the closest to the location of the vehicle among points on a predefined autonomous driving route. set to the nearest point,
When the state of the vehicle is in the work place movement state, the vehicle is switched to a waiting state for dispatch in response to the vehicle's location entering the autonomous driving route;
The workplace movement interface,
Including a route guidance interface including information about the destination, a navigation map and driving method guidance,
Device.
A computer-readable recording medium on which a program for executing the method according to claim 1 is recorded on a computer.

Images