Apparatus for transmitting additional information for AVDS subscription and method thereof

Abstract

An apparatus for transmitting additional information for an AVDS subscription, comprising: a transceiver; one or more processors configured to execute instructions and control the transceiver to transmit or receive information about an automatic valet driving system AVDS subscription; and a memory storing instructions, execution of the instructions configuring the one or more processors to: transmit an AVDS subscription request to a server via the transceiver; receiving AVDS reservation information from the server, wherein the AVDS reservation information is determined based on the AVDS reservation request; transmitting reservation confirmation information for the AVDS reservation information to the server; and transmitting an additional request related to the AVDS subscription request to the server.

Description

Technical Field

[0001] The present disclosure relates to an apparatus or method for automated valet driving, and more particularly, to an apparatus and method for transmitting additional information for a reservation of an Automated Valet Driving System (AVDS). Background Art

[0002] The AVDS consists of a user, a system, and an autonomous vehicle. The AVDS can perform automated valet driving control using the autonomous driving function.

[0003] When authorizing the AVDS to perform automated valet driving control, additional services may be requested or reserved.

[0004] The present disclosure aims to propose a scheme for transmitting additional information regarding an AVDS reservation. Summary of the Invention

[0005] The present Summary is provided to introduce a series of concepts in a simplified form that will be further described in the Detailed Description below. The present Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to help determine the scope of the claimed subject matter.

[0006] In general aspects, the present disclosure provides an apparatus including: a transceiver; one or more processors configured to execute instructions and control the transceiver to transmit or receive information regarding a reservation of an Automated Valet Driving System (AVDS); and a memory storing instructions, and the execution of the instructions configures the one or more processors to: transmit an AVDS reservation request to a server via the transceiver; receive AVDS reservation information from the server, the AVDS reservation information being determined based on the AVDS reservation request; transmit reservation confirmation information for the AVDS reservation information to the server, and transmit an additional request related to the AVDS reservation request to the server.

[0007] Transmitting the additional request may include sequentially transmitting the additional request to a local server and an additional server providing an additional service, the additional service being the service indicated by the additional request after being transmitted to the server.

[0008] The response to the additional request may be determined by the local server.

[0009] The processor may be configured to control a handover request to be transmitted to the server to transfer the control authority of the vehicle associated with the AVDS to the AVDS.

[0010] After transferring the control authority of the vehicle to the AVDS, an additional request can be transmitted to the server.

[0011] Before the pickup time after the completion of the service reserved according to the AVDS, an additional request can be transmitted.

[0012] The additional request can include one or more of the following: a change or addition of information related to the AVDS reservation included in the reservation confirmation information, a change of information related to the service of the AVDS reservation included in the reservation confirmation information, and information about additional services.

[0013] The additional request can be configured to indicate a change in the service of the AVDS reservation included in the reservation confirmation information.

[0014] The additional request can indicate one or more of the following: the AVDS reservation included in the reservation confirmation information, the service of the AVDS reservation included in the reservation confirmation information, and additional services.

[0015] The additional request can indicate one of the following: a request for a change or addition of details of the AVDS reservation included in the reservation confirmation information, and a cancellation of the AVDS reservation included in the reservation confirmation information.

[0016] The additional request can indicate one or more of the following: a request for a change in the service of the AVDS reservation included in the reservation confirmation information, a change in details of the service of the AVDS reservation included in the reservation confirmation information, and a cancellation of the service of the AVDS reservation included in the reservation confirmation information.

[0017] The additional request can indicate additional services and details of the additional services.

[0018] In general, this document provides a processor-implemented method, including: transmitting an Automated Valet Driving System (AVDS) reservation request to a server; receiving AVDS reservation information determined based on the AVDS reservation request; transmitting reservation confirmation information for the AVDS reservation information to the server; and transmitting an additional request related to the AVDS reservation request to the server.

[0019] The additional request can include one or more of the following: a change or addition of information related to the AVDS reservation included in the reservation confirmation information, a change of information related to the service of the AVDS reservation included in the reservation confirmation information, and information about additional services.

[0020] The additional request can be configured to indicate a change in the service of the AVDS reservation included in the reservation confirmation information. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 shows the basic process of an Automated Valet Driving System (AVDS);

[0022] Figure 2 shows the system structure;

[0023] Figure 3 shows the vehicle control device;

[0024] Figure 4 shows the structure of the vehicle;

[0025] Figure 5 shows the global AVDS server and / or the local AVDS server;

[0026] Figure 6 shows the process related to AVDS reservation;

[0027] Figure 7 shows the process related to AVDS handover;

[0028] Figure 8 shows the process related to AVDS additional request transmission;

[0029] Figure 9 shows the configuration and functions of the AVDS server system; and

[0030] Figure 10 is a flowchart related to the AVDS addition request.

[0031] In the drawings and the detailed description, unless otherwise stated or specified, the same or similar reference numerals can be understood to refer to the same or similar elements, features, and structures. The drawings may not be drawn to scale, and for clarity, illustration, and convenience, the relative dimensions, proportions, and descriptions of the elements in the drawings may be exaggerated. Detailed Description

[0032] The following detailed description is provided to assist the reader in obtaining a comprehensive understanding of the methods, apparatuses, and / or systems described herein. However, after understanding the disclosure of the present application, various variations, modifications, and equivalents of the methods, apparatuses, and / or systems described herein will become apparent. For example, the order of the operations described herein is merely exemplary and is not limited to those set forth herein, but may be changed as will become apparent after understanding the disclosure of the present application, except for those operations that must occur in a specific order.

[0033] The features described herein may be embodied in different forms and should not be construed as limited to the examples described herein. On the contrary, the examples described herein are only used to illustrate some of the many possible ways of implementing the methods, apparatuses, and / or systems described herein, which will become apparent after understanding the disclosure of the present application.

[0034] With reference to the embodiments described in detail below and the accompanying drawings, the advantages and features of the present disclosure and the methods for realizing the advantages and features will become clear. However, the present disclosure is not limited to the embodiments disclosed herein, but will be implemented in various forms. The embodiments of the present disclosure are provided to fully disclose the present disclosure, and those of ordinary skill in the art can fully understand the scope of the present disclosure. The present disclosure will only be limited by the scope of the technical solutions of the present disclosure attached hereto. At the same time, the terms used in this specification are used to explain the embodiments, rather than to limit the present disclosure.

[0035] In the description of the embodiments, in the case where any one element is described as being formed on or under another element, such description includes the case where the two elements are formed in direct contact with each other and the case where the two elements are in indirect contact with each other by means of one or more other elements inserted between the two elements. In addition, when one element is described as being formed on or under another element, such description may include the case where one element is formed on the upper side or the lower side with respect to another element.

[0036] Unless the context clearly indicates otherwise, the singular forms are also used to include the plural forms. It should also be understood that when the terms "comprise" and / or "include" are used herein, they specify the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0037] Figure 1 The basic process of the AVDS according to an embodiment is shown.

[0038] Figure 1 The basic process of the AVDS is shown. The AVDS is an extension of the use case and operational design domain (ODD) of the ISO 23374-1 automated valet parking system (AVPS). This system helps to achieve safe and reliable low-speed Level-4 driverless operation of vehicles and promotes the rapid and smooth introduction of future L4 systems into the market based on the experience obtained from using the AVDS at low speeds in a well-defined ODD.

[0039] AVDS provides low-speed automated valet parking service for vehicle owners. This service is not limited to driverless operation within dedicated parking facilities, but also allows driverless operation in designated outdoor spaces. Basically, both AVPS and AVDS describe a journey from point A to point B.

[0040] An example use case handled by AVDS is valet parking in an airport terminal. AVPS describes the Society of Automotive Engineers (SAE) Level 4 driving in a dedicated parking facility, while AVDS extends the drop-off area to areas outside the parking facility. After the driver leaves the designated local AVDS drop-off area, the system automatically guides the vehicle on public roads to the entrance of the parking facility and, as needed, guides the vehicle from the entrance to an empty parking space or another space. For example, when referring to spaces of interest, other use cases handled by AVDS can include driving scenarios at charging stations or car wash stations or company premises for logistics purposes.

[0041] AVDS is expected to achieve end-user benefits in terms of time savings, stress reduction, and reduced vehicle energy consumption, and to meet users' expectations for many low-speed maneuvering functions. AVDS provides an automatic charging process for electric vehicles without driver input and optimizes the utilization of a limited number of charging stations. AVDS in company premises can reduce labor costs through a driverless vehicle control system.

[0042] To contribute to safe and reliable driverless AVDS operation, the requirements specified in this document are based on the performance of the state-of-the-art technology available at the time of publication. Therefore, this part will be revised in the future as technology advances.

[0043] Due to differences in globally available and commonly used technologies (such as spectrum allocation), the embodiments include specific technical solutions for communication interfaces (such as communication methods and message protocols). Therefore, the embodiments are linked to communication interfaces at the national / regional level to ensure interoperability.

[0044] AVDS performs Level 4 automated driving of single or multiple driverless vehicles at speeds below 30 km / h within a defined operating area.

[0045] The embodiments specify the system framework, the operation sequence and communication interfaces, the performance requirements of the operation and management functions, the environmental conditions within the operation area, and the test procedures for verifying the performance requirements of the AVDS. The AVDS is considered a use case and ODD extension of ISO 23374-1, including indoor and outdoor applications such as unmanned operation in company premises, driving on public roads, and outdoor valet parking (e.g., from the airport terminal to the parking lot). In addition, the AVDS is capable of enabling other services. Further, the AVDS is applied to situations such as driving to an electric vehicle charging station or a car wash.

[0046] The AVDS includes physically independent subsystems distributed among the vehicle, facility equipment, and user domains. The functions of the AVDS are achieved through the cooperation of these subsystems, which in most cases are provided by different organizations. The embodiments include a system architecture that uses communication interfaces between the subsystems at the logical level.

[0047] The AVDS manages system participants (e.g., vehicles, facilities, and users compatible with the AVDS) and provides the necessary interfaces between them. The embodiments include requirements for management functions (e.g., verifying the compatibility between the vehicle and the premises, performing remote assistance and recovery when autonomous driving is not possible, and issuing a shutdown command in response to the actions of other facility users).

[0048] In addition, the AVDS is intended for use by service providers or facility operators who obtain vehicle authorization from individual service recipients.

[0049] The embodiments may refer to the following standard documents.

[0050] ISO 23374-1, Intelligent transport systems - Automated valet parking systems (AVPS) - Part 1: System framework, requirements for automated driving, and communication interfaces

[0051] ISO 20900, Intelligent transport systems - Partially Automated Parking Systems (PAPS) - Performance requirements and test procedures

[0052] ISO 8608 Mechanical vibration - Road surface profiles - Reporting of measured data

[0053] ISO 19206-2, Road vehicles - Test equipment for target vehicles, vulnerable road users, and other objects for the evaluation of active safety functions - Part 2: Requirements for pedestrian targets

[0054] ISO 19206-4 Road vehicles - Test equipment for target vehicles, vulnerable road users, and other objects for the evaluation of active safety functions - Part 4: Requirements for bicycle targets.

[0055] The definitions of the terms according to the embodiments are as follows:

[0056] AVDS Service Provider: An organization that provides AVDS for operating an unmanned vehicle.

[0057] AVDS User: An individual service recipient who transfers rights (3.3) / restores rights (3.3) to / from the service provider through AVDS.

[0058] Permission: The right and ability to perform a specific task in the Subject Vehicle (SV).

[0059] Subject Vehicle (SV): A vehicle equipped with an AVDS vehicle operation subsystem.

[0060] Location: A public or private area where AVDS is available

[0061] Parking Facility: A public or private parking lot with AVDS functionality

[0062] Operation Area: A geographical area within a location that meets the AVDS standard where autonomous driving can be performed

[0063] Drop-off Area: A location within the operation area where the user leaves the SV and transfers the permission to the service provider.

[0064] Pick-up Area: A location within the operation area where the service provider transfers the SV for the user to board and hands over the permission.

[0065] Parking Point: A destination within the operation area where a vehicle can be parked or temporarily stored

[0066] Stop Point: Depending on the use case considered, a destination within the operation area where the SV stops and remains in a specific state condition.

[0067] Parking Area: An area within the operation area that includes multiple parking spaces

[0068] Destination: A location within the operation area for transporting the SV.

[0069] Route: A planned traversal of the SV from a starting point to a destination

[0070] Path: A planned sequence of route points that the SV is to follow

[0071] Trajectory: A planned route that includes time information and the equipment of the automated valet parking facility

[0072] PFE: Physical equipment installed in the parking facility to support AVPS, automated valet driving location equipment

[0073] DPE: Physical device installed in the operation area of an AVDS site to support the AVDS

[0074] Encoded marker: Physical or logical marker installed in an AVDS site that uses a unique ID and can be detected by the SV to support positioning

[0075] Anonymous marker: Physical or logical marker installed in an AVDS site that does not use a unique ID and can be detected by the SV to support positioning

[0076] Designed speed: The situational speed of the SV determined by the AVDS and designed to travel in a given situation (such as traffic conditions, environmental conditions)

[0077] Designed distance: When performing autonomous driving, the situational physical distance designed from the SV to other facilities, road users, objects, or structures maintained by the AVDS in a given situation

[0078] Subsystem: The logical level of an AVDS component that includes one or more functions

[0079] Function: A function of the AVDS that helps process the input of the system and convert the input into an appropriate output

[0080] (Autonomous driving service) Reservation: The basic agreement reached between the user and the service provider regarding the operation and management of the SV within a specific site

[0081] (Automated valet parking) Session: The interaction sequence of a given SV between check-in and check-out

[0082] (Automated valet parking) Duty: A series of interactions where the AVDS automatically operates the SV from a parking position to a destination for a specific purpose

[0083] (Test) Scenario: A description of a complete traversal from a starting point to a destination for performing a test

[0084] (Test) Scene: A description of a specific event where the test is executed, excluding the starting point or the destination

[0085] System Operator (SO): The role of an organization that manages vehicle operations in the operation area of an AVDS site, and this organization includes tasks monitored when performed automatically or manually by individuals at a remote location

[0086] Premises (PM): The role of an organization that maintains the operation area in an operable and safe state according to the AVDS requirements

[0087] Orchestration System (OS): A system that classifies a session or multiple connected sessions into a single task and arranges an executable and optimized sequence of these tasks

[0088] Value added service system (VA): The role of a service system that provides dedicated service management and communication interfaces for the AVDS

[0089] The definitions of the abbreviations according to the embodiments are as follows.

[0090] ADS: Autonomous driving System; DDT: Dynamic Driving Task; OEDR: Object and Event Detection and Response; ODD: Operational Design Domain; SV: Subject Vehicle; FV: Forward Vehicle; PFE: Automated valet Parking Facility Equipment; DPE: Automated valet Driving Premises Equipment; VMC: Vehicle Motion Control; DSRC: Dedicated Short Range Communication; VRU: Vulnerable Road User; RO: Remote vehicle Operation (subsystem); VO: On-board Vehicle Operation (subsystem); UF: User Frontend (subsystem); UB: User Backend (subsystem); VB: Vehicle Backend (subsystem); OB: Operator Backend (subsystem); PM: Automated valet Parking facility Management (subsystem); DM: Automated valet Driving premises Management (subsystem); VA: Value added service system.

[0091] Figure 1 Shows the basic process of the AVDS based on user actions and system responses. Figure 1 Is a representative use case showing the process by which the user initially transfers the permission to the service provider.

[0092] In the AVDS, the user can request additional services to be performed (e.g., electric vehicle (EV) charging or car wash), while the SV's permissions remain with the AVDS service provider. The requested service and the earliest boarding time can be transmitted to the system together with the reservation. Although previously authorized by the AVDS service provider, additional services can be requested based on the remaining time.

[0093] These sessions (including additional services) involve more duties and tasks than AVPS (e.g., in the following order: parking, waiting, charging, parking, waiting, washing, and parking). The orchestration system is responsible for sorting the requested services and organizing the corresponding duties within a given time. The additional services are considered additional duties, the vehicle is driven to the designated location for service execution, and the vehicle is re-parked at the original parking location or another location. After the requested service is completed (e.g., charging completed, car wash completed), automatic re-parking occurs, and there is a parking space available for the next service or a parking space available for re-parking. No user request is required. For each additional service, the compatibility between the vehicle and the service should be checked. This includes geometric (e.g., vehicle height, width, length, and charging plug location, etc.) characteristics, electrical (e.g., plug type, charging power, and required charging level, etc.) characteristics, and other specific service characteristics.

[0094] Refer to Figure 1 , the AVDS service is provided according to <1> user actions and <2> system responses. The autonomous driving method and device according to the embodiment can correspond to the terminal for user actions and / or the system for system responses. For the sake of brevity, the autonomous driving method and device according to the embodiment can be referred to as the automatic valet parking method / device or method / device, etc.

[0095] The method / device according to the embodiment receives a request from the user. The method / device according to the embodiment checks the available space and compatibility for valet parking. The method / device according to the embodiment identifies the SV and activates the registration process. The method / device according to the embodiment receives the autonomous driving authorization from the user. The method / device according to the embodiment performs the autonomous driving vehicle operations. For example, the operations according to the embodiment can include entering, parking, re-parking, and driving to the service location. The method / device according to the embodiment can selectively have a third party perform the service actions. For example, there can be charging, car wash, maintenance, etc. The method / device according to the embodiment can allow the user to request collection. The method / device according to the embodiment can perform the self-controlled vehicle operations. For example, exiting can be performed. The method / device according to the embodiment can activate the checkout process. The method / device according to the embodiment transfers the permissions to the user.

[0096] Figure 2Shows a system structure associated with a method / apparatus according to an embodiment.

[0097] Figure 2 Shows a system structure associated with a method and apparatus for the basic process of an AVDS for performing Figure 1 of.

[0098] Figure 2 Is the logical structure of a subsystem of the AVDS. The implementation of the logical subsystem with respect to physical components may vary depending on the system design. In addition, the subsystem may include multiple physical components. For example, the remote vehicle operation subsystem may include sensors, control devices, and communication devices.

[0099] The system according to an embodiment can execute and include the method / apparatus according to an embodiment. For example, the AVDS device / system of the method / apparatus according to an embodiment may include an operator backend (OB), an orchestrating system (OS), and / or a remote vehicle operation (RO). The AVDS device / system according to an embodiment may correspond to a server. The user terminal of the method / apparatus according to an embodiment may include a user frontend (UF) and / or a user backend (UB). The vehicle of the method / apparatus according to an embodiment may include a vehicle backend (VB) and / or an on-board vehicle operation (VO). The system of the method / apparatus according to an embodiment may further include a service system (value added service system, (VA)) and / or a system operator (SO). The operations according to an embodiment may be performed by Figure 2 each component of the system. Figure 2 Each component of may correspond to hardware, software, a processor, and / or a combination thereof.

[0100] Figure 3 Shows a vehicle control device according to an embodiment.

[0101] The vehicle control device 3000 according to an embodiment is a device that controls the operation of a vehicle according to an embodiment. The vehicle control device may be referred to as an autonomous driving integration controller 600. The vehicle control device may include an interface unit 3001, a processor 3002, and a memory 3003.

[0102] The memory can store instructions, signaling information, data, etc. for performing operations according to the embodiments. The memory can be connected to the interface unit and the processor to transmit and receive necessary signals.

[0103] The interface unit can receive signals, information, data, etc. from the vehicle control device and transmit the signals, information, and data, etc. to the memory and / or the processor. In addition, the signals, information, data, etc. generated from the memory and / or the processor can be transmitted to the vehicle and / or the driver and / or the passengers.

[0104] The processor can perform vehicle control operations according to the embodiments based on the data and / or instructions stored in the memory.

[0105] Figure 3 The vehicle control device can correspond to a device installed in the vehicle or a terminal device that controls the vehicle.

[0106] Figure 4 The structure of a vehicle according to an embodiment is shown.

[0107] A vehicle according to an embodiment can be configured as shown Figure 4 and can perform autonomous driving using an autonomous driving control system. A vehicle according to an embodiment can include an autonomous driving vehicle, a robot, urban air mobility (UAM), an aircraft, an autonomous driving device, and other devices or vehicles that can be controlled by autonomous driving. The scope of rights of the present disclosure is not limited by these names.

[0108] The autonomous driving vehicle 1000 can be implemented around an autonomous driving integrated controller 600, which transmits and receives data required for autonomous driving control of the vehicle through a driving information input interface 101, a driving information input interface 201, a passenger output interface 301, and a vehicle control output interface 401. However, in this specification, the autonomous driving integrated controller can be referred to as a controller, a processor, or simply a controller.

[0109] Through the driving information input interface, the autonomous driving integrated controller can obtain driving information according to the operation of the passenger on the user input unit in the autonomous driving mode or the manual driving mode of the vehicle. The user input unit can include a driving mode switch and a control panel 120 (for example, a navigation terminal installed in the vehicle, a smartphone or a tablet computer carried by the passenger, etc.), and thus, the driving information can include the driving mode information and the navigation information of the vehicle.

[0110] In addition, when it is determined that a warning needs to be issued to the driver in the autonomous driving mode or the manual driving mode of the vehicle, the autonomous driving integrated controller can provide warning information and driving status information to the driver through the passenger output interface. The speaker 310 and the display device 320 can be included to output such driving status information and warning information audibly and visually. In this case, the display device can be implemented as the same device as the above control panel, or can be implemented as a separate and independent device.

[0111] In addition, in the autonomous driving mode or the manual driving mode of the vehicle, the autonomous driving integrated controller can transmit control information for the driving control of the vehicle to the sub-control system applied to the vehicle through the vehicle control output interface. The sub-control system for the driving control of the vehicle can include at least one of a motor control system, an engine control system, a brake control system, or a steering control system, and the autonomous driving integrated controller can transmit at least one of motor control information, engine control information, brake control information, or steering control information as control information to each sub-control system through the vehicle control output interface.

[0112] The autonomous driving integrated controller can obtain driving information according to the driver's operation and driving information indicating the driving status of the vehicle through the driving information input interface and the driving information input interface respectively, and provide driving status information and warning information generated according to the autonomous driving algorithm through the passenger output interface.

[0113] Meanwhile, in order to ensure stable autonomous driving of the vehicle, the autonomous driving device according to an embodiment can include a sensor unit for detecting objects around the vehicle (such as surrounding vehicles, pedestrians, roads, or fixed facilities (such as traffic lights, road signs, traffic signs, construction fences, etc.)).

[0114] The sensor unit can include one or more of a lidar (LiDAR) sensor, a radar sensor, and a camera sensor to detect surrounding objects outside the vehicle. It can include a front lidar sensor 511, a front radar sensor 521, a rear lidar sensor 513, a rear radar sensor 524, a left camera sensor 532, a right camera sensor 533, an internal camera sensor 535, a front camera sensor 531, a rear camera sensor 534, etc. The sensor unit can be connected to microphones 551 and 552.

[0115] An embodiment relates to a method of controlling the driving of an ADS vehicle to an EV charging station through an AVDS.

[0116] The embodiments relate to the international standards ISO 23374-1 (AVPS) and ISO 12768-1 (AVDS). The embodiments relate to an Automated Valet Parking System (hereinafter referred to as "AVPS") or an Automated Valet Driving System (hereinafter simply referred to as "AVDS"). The embodiments provide a method and apparatus in which an ADS vehicle (conceptually the same as the standard "SV") autonomously drives from a parking position to an EV charging station and charges, and then autonomously returns to the parking position or goes to another position after charging is completed.

[0117] The current international standards ISO 23374-1 or ISO 12768-1 only describe a method / apparatus for moving an ADS vehicle to an EV charging station immediately after the EV charging station becomes available in response to the completion of charging of the previous EV when the AVPS or AVDS sends the ADS vehicle to the EV charging station. However, the current international standards do not define a method / apparatus for sending the ADS vehicle to the EV charging station before the completion of charging of the previous EV considering the charging completion time of the previous EV. Therefore, the embodiments describe a method / apparatus for driving the ADS vehicle in advance before the completion of charging of the EV considering the charging completion time of the previous EV to achieve efficient and safe automated valet driving. Therefore, since the return time of the ADS vehicle can be advanced, the embodiments have the effect of improving the efficiency of the charging service provided by the EV charging station.

[0118] The embodiments relate to a method of exchanging data between an AVDS and an EV charging station.

[0119] The embodiments relate to the international standards ISO 23374-1 (AVPS) and ISO 12768-1 (AVDS). The embodiments relate to an Automated Valet Parking System (hereinafter referred to as "AVPS") or an Automated Valet Driving System (hereinafter simply referred to as "AVDS"). The embodiments provide a method and apparatus in which an ADS vehicle (used as the same concept as the standard "host vehicle (SV)") autonomously drives from a parking position to an EV charging station and charges, and then autonomously returns to the parking position or goes to another position after charging is completed.

[0120] The current international standards ISO 23374-1 or ISO 12768-1 fail to define the data exchanged between the AVPS or AVDS and the EV charging station. Therefore, the embodiments provide the data exchanged between the AVPS or AVDS and the EV charging station to achieve efficient and safe automated valet driving. Hereinafter, a description of the data for mutual communication between the AVDS and the EV charging station according to the embodiments will be given. As a result, the embodiments have the effect of providing an efficient communication data protocol between the AVDS and the EV charging station.

[0121] As described above, OB, OS, and VA may correspond to servers. In the description related to the following drawings, note that OB, OS, and VA may respectively refer to or correspond to a server (or a global server), a local server, and an additional service server.

[0122] In addition, it should be noted that UB and VB may respectively refer to or correspond to a user terminal and a vehicle.

[0123] Figure 5 A global AVDS server and / or a local AVDS server according to an embodiment is shown.

[0124] Figure 1 of the AVDS, Figure 2 of the device, Figure 3 of the vehicle control device, Figure 4 of the vehicle, etc. may be connected to Figure 5 the global AVDS server and the local AVDS server to control the vehicle.

[0125] The global AVDS server manages the local AVDS servers in each area and performs the function of directly transmitting and receiving data with the vehicle backend (VB), user backend (UB), etc. The global AVDS server may be referred to as an operator backend (OB). The global AVDS server may be connected to at least one local AVDS server and may manage the local AVDS servers.

[0126] The local AVDS server is a local server set by area and may perform the function of transmitting and receiving data with VA (such as an EV charging station, a car wash, etc.) and the global AVDS server (OB). The local AVDS server may be referred to as an orchestration system (OS).

[0127] A method for the global AVDS server to perform the AVDS duties of SV while transmitting and receiving data with the local AVDS server will be described with reference to the following drawings.

[0128] Figure 6 An operation of an AVDS system related to an AVDS reservation according to an embodiment is shown.

[0129] The AVDS system related to the AVDS reservation is mainly divided into five processes, and the signaling, messages, and data classified in the same process are represented by the same numbers. Each process is represented as a step, and steps 1 to 5 shown in Figure 6 will be described.

[0130] Regarding Figure 6Step 1 of the AVDS reservation method for AVDS access control of a vehicle by an AVDS server (OB) may include the step of requesting availability. For example, the UB may request availability from the OB. The availability may include parking time, services to be used, etc.

[0131] Such an availability request may be transmitted from the OB to the OS, or from the OS to the VA. According to an embodiment, the availability in step 1 may be the same.

[0132] Alternatively, the availability in step 1 may be at least partially different according to an embodiment. In this case, compared with the availability transmitted from the UB to the OB, the availability transmitted from the OB to the OS or from the OS to the VA may further include additional information. For example, the availability transmitted from the OB to the OS may further include information about (i) the ID of the UB and / or (ii) the time point at which the OB has received the availability of step 1.

[0133] Regarding Figure 6 Step 2 of the AVDS reservation method for AVDS access control of a vehicle by an AVDS server may include the step of requesting compatibility data. For example, the VA may request compatibility data from the OS. The compatibility data may be information about the ID, size, and / or fuel type of the vehicle. Therefore, the initial request for compatibility data may be executed by the value-added system (VA). The type of information included in the compatibility data may vary according to the VA. For example, some VAs may request information (such as model information (manufacturer / year), etc. instead of the size and / or fuel type of the vehicle) as compatibility data.

[0134] Such a compatibility data request may be transmitted from the VA to the OS, from the OS to the OB, and from the OB to the VB. According to an embodiment, the compatibility data requests in step 2 may be the same.

[0135] Alternatively, according to an embodiment, the compatibility data requests in step 2 may be at least partially different. For example, the compatibility data request transmitted from the OB to the VB may include information about the VB ID, etc.

[0136] Regarding Figure 6 Step 3 of the AVDS reservation method for AVDS access control of a vehicle by an AVDS server may include the step of receiving compatibility data. For example, the OB may receive compatibility data from the VB. The compatibility data may include information about the ID, size, fuel type, etc. of the vehicle.

[0137] Such compatibility data may be transmitted from the VB to the OB, from the OB to the OS, and from the OS to the VA.

[0138] Regarding Figure 6For step 4 of the AVDS reservation method for AVDS access control of a vehicle by an AVDS server, it may include steps of determining, transmitting, and receiving new reservation information. For example, the VA may determine new reservation information and submit a new reservation to the OS. The new reservation information may include at least one of a reservation ID, an available time period, available services (such as EV charging, car wash, etc.), and / or service fees. The new reservation information may vary depending on the VA. For example, the VA of an EV charging station may configure the available time period in one-hour units, and the VA of a car wash station may configure the available time period in 30-minute units.

[0139] The new reservation information determined by the VA may be transmitted from the VA to the OS, from the OS to the OB, and from the OB to the UB. According to an embodiment, the new reservation information in step 4 may all be the same.

[0140] Alternatively, according to an embodiment, the new reservation information in step 4 may be at least partially different. For example, the new reservation information transmitted from the OS to the OB may include the ID of the OS, and the new reservation information transmitted from the OB to the UB may further include the ID of the UB.

[0141] Regarding Figure 6 For step 5 of the AVDS reservation method for AVDS access control of a vehicle by an AVDS server, it may include steps of transmitting and receiving reservation confirmation information. For example, the UB may transmit reservation confirmation information to the OB, and the UB may transmit the reservation confirmation information to the VB. The reservation confirmation information may include at least one of a reservation ID, a determined time period, and a determined service.

[0142] In addition, as Figure 6 shown, the VB does not receive new reservation information but only receives reservation confirmation information from the UB. However, it is not limited to the embodiment where the VB does not receive new reservation information. That is, the VB may also receive new contract information, and the VB and / or the UB may transmit reservation confirmation information to the OB. In addition, the UB may transmit the reservation confirmation information only to the OB and not to the VB.

[0143] The reservation confirmation information transmitted by the UB may be transmitted from the UB to the OB, from the OB to the OS, and from the OS to the VA.

[0144] According to an embodiment, the reservation confirmation information in step 5 may all be the same.

[0145] Alternatively, according to an embodiment, the reservation confirmation information in step 5 may be at least partially different. For example, the reservation confirmation information transmitted from the OB to the OS may include the ID information of the OB.

[0146] According to Figure 6Perform AVDS reservation through the process shown. AVDS reservation is for additional services (such as EV charging service or car wash service). When providing an automated valet driving service (such as valet parking), AVDS reservation can provide reservation for additional services.

[0147] Figure 7 Shows the operation of AVDS during AVDS handover according to an embodiment.

[0148] AVDS handover can be performed through Figure 7 Steps 11 to 19 as follows.

[0149] Regarding Figure 7 Step 11, the AVDS handover method may include the step of the RO identifying that the SV has reached the drop-off area. The RO can identify that the vehicle (SV) has reached the drop-off area through a sensing module in the drop-off area (such as a camera, ultrasonic sensor, infrared sensor, etc.).

[0150] Regarding Figure 7 Step 12, the AVDS handover method may further include the step of the RO notifying the VO whether the SV has been identified in the drop-off area. The RO can notify the SV that the SV has been identified in the drop-off area.

[0151] Regarding Figure 7 Step 13, the AVDS handover method may further include the step of transmitting information notifying that the handover is ready from the VO to the VB and / or from the VB to the UB. The VO can notify the VB that the AVDS handover is ready, and the VB can notify the UB that the AVDS handover is ready.

[0152] Regarding Figure 7 Step 14, the AVDS handover method may further include the step of allowing the user to leave the SV. The user can leave the SV that has reached the drop-off area.

[0153] Regarding Figure 7 Step 15, the AVDS handover method may further include the step of requesting handover from the UB to the VB and / or OB, from the OB to the RO, and from the VB to the VO. After receiving the handover request input from the UF, the UB transmits the handover request to the VB and / or OB. The OB transmits the handover request to the RO, and the VB transmits the handover request to the VO.

[0154] Regarding Figure 7 Step 16, the AVDS handover method may further include the step of the OB recording the handover request from the user. The OB records that there is already a handover request from the user. If the handover fails once, multiple handover attempts can be recorded.

[0155] Regarding Figure 7In step 17, the AVDS handover method may further include a step of checking for handover availability. For example, it may be finally confirmed whether it is an environment where RO, VO, etc. can perform AVDS control operations. For example, an environment where AVDS control operations can be performed may mean whether it is an environment that supports level 4 autonomous driving.

[0156] Regarding Figure 7 In step 18, the AVDS handover method may further include a step of the OB determining whether the AVDS system has permission. The OB may determine that the AVDS system has permission.

[0157] Regarding Figure 7 In step 19 of the AVDS handover method, the OB may notify VB, RO, UB, and / or OS of the handover of permission from VB to VO. It is notified that the control permission has been handed over to the AVDS system. For example, the OB determines the system permission and transmits the permission handover result to VB, RO, UB, and OS. Here, once the handover result is received, RO starts remote control (automatic parking) of the SV. VB records the permission handover in the AVDS system. Once the handover result is received, UB notifies the user of the permission handover. For example, it may notify the user of the permission handover by displaying it as user interface (UI) / user experience (UX) information on the UF.

[0158] Meanwhile, steps 16 and 18 may be performed by the OS instead of the OB.

[0159] In addition, regarding step 15, a handover from the OB to the OS may be requested. Regarding step 16, the OS may record the existence of a handover request from the user. Regarding step 18, the OS may determine whether the AVDS system has permission.

[0160] Figure 8 The process for transmitting and receiving an AVDS reservation or an additional request for an AVDS service related to the AVDS reservation according to the present disclosure is shown.

[0161] The process for transmitting and receiving an AVDS reservation or an additional request for an AVDS service related to the AVDS reservation is mainly divided into three processes. The signaling, messages, and data classified by the same process are represented by the same numbers. Each process is represented as a step, and steps 6 to 8 shown in Figure 8 will be described.

[0162] Regarding Figure 8 In step 6, the method for issuing an additional request for an AVDS reservation or an AVDS service related to the AVDS reservation may include a step of transmitting an additional request. The UB may transmit an additional request to the OB.

[0163] The additional request may include information changes or information additions included in the reservation confirmation information (i.e., related to a pre-confirmed AVDS reservation) and / or information related to such information changes or information additions.

[0164] Alternatively, the additional request may include information changes included in the reservation confirmation information (i.e., related to the AVDS service related to a pre-confirmed AVDS reservation) and / or information related to such information changes.

[0165] Alternatively, the additional request may include information about additional services. The information about additional services may be unrelated to the AVDS reservation included in the reservation confirmation information (i.e., a pre-confirmed AVDS reservation).

[0166] Alternatively, the additional request may include at least one of the following: an information change or information addition related to a pre-confirmed AVDS reservation, an information change related to the AVDS service related to a pre-confirmed AVDS reservation, or information about additional services.

[0167] Alternatively, the additional request may include at least one of the following: i) an information change or information addition related to a pre-confirmed AVDS reservation and / or information related to such information change or information addition; ii) an information change related to the AVDS service related to a pre-confirmed AVDS reservation and / or information related to such information change; and iii) information about additional services.

[0168] For example, the data detail information about the additional request may be defined in the following table. Referring to Table 1, according to the additional request type, each additional request includes: i) the case of an information change or information addition related to a pre-confirmed AVDS reservation; ii) the case of an information change related to the AVDS service related to a pre-confirmed AVDS reservation; and iii) the case of additional services.

[0169] [Table 1]

[0170]

[0171]

[0172]

[0173] Referring to Table 1, the additional request may indicate at least one of the AVDS reservation included in the reservation confirmation information (a pre-confirmed AVDS reservation or the AVTS service related thereto), the AVDS service related to the AVDS reservation, or the additional services. That is, the value of the additional request type may indicate the AVDS reservation, the AVDS service, or the additional services.

[0174] In addition, if the additional request indicates a pre - confirmed AVDS reservation (the AVDS reservation included in the reservation confirmation information), a request for a change or addition to the details for the AVDS reservation, or a cancellation of the AVDS reservation may be indicated.

[0175] In addition, if the additional request indicates the AVDS service of a pre - confirmed AVDS reservation (the AVDS service included in the reservation confirmation information), a request for a change to the AVDS service, a change to the details of the AVDS service, or a cancellation of the AVDS service may be indicated.

[0176] In addition, if the additional request indicates an additional service, an additional service and details regarding the additional service (e.g., service time information, service type, service cost, etc.) may be indicated.

[0177] Such additional requests may be passed from the UB to the OB, from the OB to the OS, and from the OS to the VA.

[0178] According to an embodiment, the additional requests in step 6 may all be the same.

[0179] Alternatively, according to an embodiment, the additional requests in step 6 may be at least partially different. In this case, compared with the additional request transmitted from the UB to the OB, the additional request transmitted from the OB to the OS or from the OS to the VA may further include additional information. For example, the additional request transmitted from the OB to the OS may further include information regarding (i) the ID of the UB and / or (ii) the time point at which the OB receives the additional information from the UB.

[0180] Regarding Figure 8 step 7, a method for issuing an additional request for an AVDS reservation or an AVDS service related to the AVDS reservation may include steps of determining a response to the additional request and transmitting and receiving the determined response. The VA or the OS may determine a response to the received additional request.

[0181] According to the additional request, the response to the additional request may include different information.

[0182] For example, the response to the additional request may include at least one of an AVDS reservation ID, AVDS reservation change information, AVDS reservation additional information, or AVDS reservation cancellation information.

[0183] For another example, the response to the additional request may include at least one of the following: an AVDS reservation ID, information regarding an AVDS service related to a change in the AVDS reservation, information regarding a change to the AVDS service related to the AVDS reservation (e.g., service cost, service execution time (e.g., available time period), charging status, car wash type, etc.), or AVDS service cancellation information.

[0184] For another example, the response to the additional request includes information about the additional service and may include specific information about the additional service (e.g., in the case of an EV charging service, at least one of charging time, charging status, charging speed, and charging type). In the case of a car wash service, it may include at least one of car wash time, car wash type, and car wash cost.

[0185] Meanwhile, the response to the additional request can be configured to include information indicating acceptance or rejection of the additional request.

[0186] Regarding Figure 8 For step 8, the method of issuing an additional request for an AVDS reservation or an AVDS service related to the AVDS reservation can be the step of transmitting and receiving additional request confirmation information in response to the additional request. The UB can determine the additional request confirmation information in response to the response to the received additional request.

[0187] The additional request confirmation information can include at least one of a reservation ID, time information related to the reservation or service, and the determined service.

[0188] Alternatively, the additional request confirmation information can include information composed of the information included in the response to the received additional request. That is, the response to the additional request can include information related to a change / addition of information about the AVDS reservation determined based on the additional request in step 6, a change / addition of information about the AVDS service, or information related to the additional service. Therefore, the additional request confirmation information provided in response to the response to the additional request can include the information included in the response to the additional request or a part thereof.

[0189] The additional request confirmation information transmitted by the UB can be transmitted from the UB to the OB, from the OB to the OS, and from the OS to the VA.

[0190] According to an embodiment, the additional request confirmation information in step 8 can all be the same.

[0191] Alternatively, according to an embodiment, the additional request confirmation information in step 8 can be at least partially different. For example, the additional request confirmation information transmitted from the OB to the OS can include the ID information of the OB.

[0192] Meanwhile, after the process of combining Figure 5 completes the reservation confirmation (step 5 of Figure 6 ), step 6 of Figure 8 can be executed. In addition, after the process of combining Figure 7 transfers the authority of the vehicle (SV) to the AVDS or the AVDS server (OB), Figure 8Step 6. That is, Figure 8 The process of Figure 6 or Figure 7 can be combined and executed with the process of

[0193] In addition, after the handover is completed, the boarding time can be determined (i.e., the time when the vehicle (SV) is sent to the user after completing Automated Valet Driving (AVD) and AVD service reservations and the AVD service, and the authority of the vehicle (SV) is transferred back to the user). In this case, additional requests can be transmitted before the pick-up time.

[0194] Figure 9 shows the configuration and functions of the system of the AVDS server according to an embodiment.

[0195] Figure 9 shows the main functions of the AVDS of each subsystem of the system of the AVDS server.

[0196] RO (Remote vehicle Operation) has the function of controlling autonomous vehicles. Specifically, for steering, movement, and vehicle dynamics, RO has functions such as SV identification, destination assignment, route planning, Object and Event Detection and Response (OEDR), SV positioning, path determination, trajectory calculation, vehicle motion control, emergency stop, etc.

[0197] Like RO, VO (Vehicle Onboard Operation) has the same role and functions. The function allocation between the RO and VO subsystems can vary depending on the type of vehicle operation.

[0198] UF (User Front End) serves as a user interface. Specifically, it has the function of transmitting user requests and the function of receiving and updating the vehicle status from the user. The UF function can vary depending on the specifications of the provider.

[0199] UB (User Back End), VB (Vehicle Back End), OB (Operator Back End), OS (Orchestration System), and PM (Automated Valet Driving Place Management) are management systems.

[0200] UB (User Back End) processes user requests.

[0201] VB (Vehicle Back End) has the function of remote participation and / or release.

[0202] OB (Operator Back End) 900 has functions related to managing the availability of parking facilities, checking the compatibility of SV and parking facilities, controlling the SV as driverless, performing remote support, etc.

[0203] The OS (orchestration system) 901 has the functions of coordinating and optimizing service tasks at corresponding locations and coordinating various services using automation functions.

[0204] PM (Automated Valet Parking management) has the functions of managing environmental conditions and handling operational incapacitation.

[0205] The back-end subsystems (such as UB (User Back-end), VB (Vehicle Back-end), and OB (Operator Back-end)) work together to respond to user requests (such as vehicle search).

[0206] PM (Automated Valet Parking management) coordinates autonomous driving activities in the facility area.

[0207] The Value Added service system (VA) has an additional service role. VA has functions such as additional services (such as washing and charging). These services can be optional.

[0208] OB corresponds to the (global) AVDS server, and OS corresponds to the local AVDS server.

[0209] In addition, UF or UB can correspond to the device or terminal on the user side.

[0210] Figure 10 A flowchart showing a method for transmitting an AVDS reservation or an additional request related to an AVDS reservation according to the present disclosure is shown. Figure 10 The flowchart of can be executed by Figure 3 the device 3000. The device 3000 can be configured to execute the operations of the flowchart according to while executing the AVDS reservation and AVDS handover described with reference to Figure 6 or Figure 7 . In addition, the content not described with reference to Figure 10 can be referred to the description of Figure 10 . Figure 8 The description of

[0211] The device 3000 includes an interface unit 3001, a processor 3002, and a memory 3003, and the interface unit 3003 can include a wired / wireless transceiver.

[0212] The device 3000 can transmit an AVDS reservation request (S810) to the server. The AVDS reservation request can correspond to Figure 6 the availability request. The server can include OB, but can also include OS, VA, etc. and OB to which the AVDS reservation request is directly transmitted.

[0213] Device 3000 may receive AVDS reservation information determined based on an AVDS reservation request (S820). The AVDS reservation information may correspond to Figure 5 new reservation information.

[0214] Device 3000 may transmit reservation confirmation information regarding the AVDS reservation information to the server (S830).

[0215] Thereafter, device 3000 may transmit an additional request related to the AVDS reservation request to the server (S840).

[0216] Via Figure 10 the process shown, device 3000 may additionally perform: addition, change, or cancellation of a pre - confirmed AVDS reservation; addition, change, or cancellation of services for an AVDS reservation; request for additional services, etc., thereby bringing about technical effects that provide more user convenience (such as saving user time, reducing energy consumption, etc.) through AVDS.

[0217] Meanwhile, a device for transmitting an additional request for an AVDS reservation or a service related to an AVDS reservation will be described with reference to Figure 3 description.

[0218] Device 3000 may include a transceiver 3001 and a processor 3002. The processor 3002 controls the transceiver 3001 to transmit or receive information regarding an AVDS reservation.

[0219] The processor 3002 may control the transceiver 3001 to transmit an AVDS reservation request to the server. In addition, the processor 3002 may control the transceiver 3001 to receive AVDS reservation information determined based on the AVDS reservation request. In addition, the processor 3002 may control the transceiver 3001 to transmit reservation confirmation information for the AVDS reservation information. The processor 3002 may control the transceiver 3001 to transmit an additional request related to the AVDS reservation request to the server.

[0220] Meanwhile, an additional request may be transmitted to the server and then sequentially transmitted to a local server and an additional service - providing server that provides additional services related to the service indicated by the additional request.

[0221] The processor 3002 may control a handover request (which is used to hand over the vehicle's authority to AVDS) to be transmitted to the server. Thus, the additional request may be configured to be transmitted to the server after the vehicle's authority has been handed over to AVDS. In addition, the additional request may be transmitted before the pick - up time after the service according to the AVDS reservation is completed.

[0222] The processor 3002 may receive a response to an additional request and the response to the additional request may be determined by a local server.

[0223] The additional request may include at least one of the following: changing or adding information related to the AVDS reservation included in the reservation confirmation information; changing information related to the service of the AVDS reservation included in the reservation confirmation information; or information about an additional service.

[0224] Alternatively, the additional request may be configured to change the service of the AVDS reservation included in the reservation confirmation information.

[0225] In another aspect, the additional request may indicate at least one of the following: the AVDS reservation included in the reservation confirmation information, the service of the AVDS reservation included in the reservation confirmation information, or an additional service.

[0226] The additional request may indicate a request to change or add details of the AVDS reservation included in the reservation confirmation information, or a request to cancel the AVDS reservation included in the reservation confirmation information.

[0227] The additional request may indicate a request to change the service of the AVDS reservation included in the reservation confirmation information, change details of the service of the AVDS reservation included in the reservation confirmation information, or cancel the service of the AVDS reservation included in the reservation confirmation information.

[0228] The additional request may indicate an additional service and details of the additional service.

[0229] Meanwhile, according to another embodiment of the present disclosure, a vehicle (not shown) is proposed, which includes the above-described device for transmitting an additional request for the above-described AVDS reservation or a service related to the AVDS reservation. The vehicle may include a device 3000, and the device 3000 includes a transceiver 3001 and a processor 3002, and the processor 3002 controls the transceiver 3001 to transmit or receive information about the AVDS reservation. The description of the device 3000 may refer to the previous description.

[0230] In this specification, a "device" or "server" that transmits / receives and processes information related to an AVDS reservation, etc. or a configuration included therein is described as performing operations. However, the "device", "server" and their components are just names, and the scope of rights does not depend on them.

[0231] In other words, the proposed technology may be performed under a name other than a device, and the above methods, solutions, etc. may be performed by vehicle control software or its computer, machine or device-readable code.

[0232] In addition, as another aspect of the present disclosure, the operation of the above-described technology can be provided as code that can be implemented, embodied, or executed by a "computer" (including the general concept of a System-on-Chip (SoC), (micro)processor, etc.), a computer-readable storage medium or a computer program product that stores or includes the code. The scope of the rights of the present disclosure can be extended to the code or the computer-readable storage medium or the computer program product that stores or includes the code.

[0233] The various embodiments of the present disclosure do not list all available combinations, but only describe the representative aspects of the present disclosure, and the descriptions of the various embodiments can be applied independently or can be applied through a combination of two or more.

[0234] Multiple embodiments have been described above. However, it should be understood that various modifications can be made. For example, suitable results can be obtained if the described technology is executed in a different order and / or if the components in the described system, architecture, device, or circuit are combined in a different manner and / or replaced or supplemented by other components or their equivalents. Therefore, other embodiments are within the scope of the technical solutions of the present disclosure attached.

[0235] Although the present disclosure includes specific examples, it will be apparent after understanding the disclosure of the present application that various changes in form and detail can be made in these examples without departing from the spirit and scope of the technical solutions of the present disclosure and their equivalents. The examples described herein are considered only in an illustrative sense and not for the purpose of limitation. The description of the features or aspects in each example will be considered applicable to similar features or aspects in other examples. Suitable results can be obtained if the described technology is executed in a different order, and / or if the components in the described system, architecture, device, or circuit are combined in a different manner and / or replaced or supplemented by other components or their equivalents. Therefore, the scope of the present disclosure is not limited by the specific embodiments, but by the technical solutions of the present disclosure and their equivalent content, and all changes within the scope of the technical solutions of the present disclosure and their equivalent content should be construed as being included in the present disclosure.

Claims

1. A device for transmitting additional information for an automatic valet driving system (AVDS) reservation, the device comprising: Transceiver; one or more processors configured to execute instructions and control the transceiver to transmit or receive information about the AVDS subscription; and a memory storing the instructions, wherein execution of the instructions configures the one or more processors to: transmitting an AVDS subscription request to a server via the transceiver; receiving AVDS subscription information from the server, the AVDS subscription information being determined based on the AVDS subscription request; transmitting subscription confirmation information for the AVDS subscription information to the server; and An additional request related to the AVDS subscription request is transmitted to the server.

2. The device according to claim 1, wherein: Transmitting the additional request further comprises: The additional request is sequentially transmitted to a local server and an additional server that provides an additional service, the additional service being a service indicated by the additional request after being transmitted to the server.

3. The device according to claim 2, wherein: A response to the additional request is determined by the local server.

4. The device according to claim 1, wherein: The processor is further configured to: Controlling a handover request to be transmitted to the server to hand over the control authority of the vehicle associated with the AVDS to the AVDS.

5. The device according to claim 4, wherein: After handing over the control authority of the vehicle to the AVDS, the additional request is transmitted to the server.

6. The device according to claim 1, wherein: The additional request is transmitted before a pick-up time after the service booked according to the AVDS is completed.

7. The device according to claim 1, wherein: The additional request includes one or more of the following: changes or additions to information related to the AVDS reservation included in the reservation confirmation information; changes in information related to services subscribed to the AVDS included in the subscription confirmation information; as well as Information about additional services.

8. The device according to claim 1, wherein: The additional request is configured to indicate a change of a service subscribed by the AVDS included in the subscription confirmation information.

9. The device according to claim 1, wherein: The additional request indicates one or more of the following: the AVDS reservation included in the reservation confirmation; The services subscribed by the AVDS included in the subscription confirmation information; and Additional services.

10. The device according to claim 9, wherein: The additional request indicates one of the following: a request for a change or addition of details of the AVDS subscription included in the subscription confirmation; and Cancellation of the AVDS subscription included in the subscription confirmation information.

11. The device according to claim 9, wherein: The additional request indicates one or more of the following: a request for a change of the service subscribed by the AVDS included in the subscription confirmation; changes to the details of the service subscribed to by the AVDS included in the subscription confirmation; and The cancellation of the service subscribed by the AVDS included in the subscription confirmation information.

12. The device according to claim 9, wherein: The additional request indicates the additional service and details of the additional service.

13. A processor-implemented method, the method comprising: Transmitting an automatic valet driving system (AVDS) reservation request to a server; Receiving AVDS subscription information determined based on the AVDS subscription request; transmitting a subscription confirmation message for the AVDS subscription message to the server; as well as An additional request related to the AVDS subscription request is transmitted to the server.

14. The method according to claim 13, wherein: The additional request includes one or more of the following: changes or additions to information related to the AVDS reservation included in the reservation confirmation information; changes in information related to services subscribed to the AVDS included in the subscription confirmation information; as well as Information about additional services.

15. The method according to claim 13, wherein: The additional request is configured to indicate a change of a service subscribed by the AVDS included in the subscription confirmation information.

Images