Ars and qr linked vehicle owner call system
Patent Information
- Application Number
- KR1020250096190
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2025-07-16
- Publication Date
- 2026-09-23
- Estimated Expiration
- 2045-07-16
Smart Images

Figure 112025080596267-PAT00006_ABST
Abstract
Description
Technology Field
[0001] The present disclosure relates to a system and method for facilitating communication between the owner of a parked vehicle and an external caller, and specifically, to an ARS and QR-based vehicle calling system and method that enables a caller to connect directly with the vehicle owner through a QR code or ARS number attached to the vehicle. Background Technology
[0002] Unless otherwise indicated in this specification, the contents described in this section are not prior art for the claims of this application, and are not to be recognized as prior art simply because they are included in this section.
[0003] Recently, situations where temporarily parked vehicles cause inconvenience to traffic have been occurring frequently in densely populated residential and commercial areas, as well as in hospitals and schools within cities. In such cases, outsiders need to contact the vehicle owner to request the vehicle's relocation; however, contact information is generally not displayed on the exterior of the vehicle, or its exposure is often restricted for reasons such as privacy protection.
[0004] Accordingly, parking call systems capable of contacting owners via QR codes or ARS phone numbers attached to the vehicle have been proposed. Most conventional systems utilize a method where users simply enter the license plate number after scanning a QR code or connecting to an ARS phone number, and then either connect directly to a pre-registered contact or send a text message (including a URL).
[0005] However, existing ARS-based systems provide only single-step procedures, such as "enter license plate number -> connect to phone" or "transmit URL," which results in an inconvenient user experience (UX) for the caller or raises concerns about misconnections. Additionally, there is inadequate handling of duplicate license plate numbers: although multiple vehicles may share the same last four digits based on only a partial license plate number, conventional systems do not provide selection logic for such duplicate entries, leading to the possibility of misconnections. Furthermore, when connected to a standard phone number, the vehicle owner's actual contact information may be exposed, posing a vulnerability to personal information protection issues. Moreover, the lack of scenario-specific guidance within the ARS flow regarding license plate number validation, notification of duplication, and connection to a secure number results in low practical usability for the caller. Prior art literature
[0006] 1. Korean Patent Registration No. 10-2458958 (October 20, 2022) 2. Korean Patent Registration No. 10-1263199 (May 6, 2013) The problem to be solved
[0007] The purpose of the embodiments disclosed in this disclosure is to provide an ARS and QR-based vehicle calling system and a method thereof, wherein when a caller inputs a portion of a vehicle number via an ARS number or QR code attached to a vehicle, the system determines the validity and duplication of the input value, provides guidance on multiple items if necessary, and connects to the vehicle owner via a pre-registered virtual number (safe number) according to the caller's selection.
[0008] In addition, the embodiments disclosed in this disclosure aim to provide a vehicle calling system that improves user satisfaction and reduces the possibility of malfunction and misidentification by improving a simple ARS input procedure and providing a sophisticated call UX scenario that includes checking for duplication, user selection, and guidance flow control even after the vehicle identification information is entered.
[0009] In addition, the embodiment disclosed in this disclosure aims to provide a vehicle calling method that enables accurate identification and connection by including an interface that lists duplicate items and guides the caller to select them, even if the caller inputs only a part of the vehicle number (e.g., the last four digits of the vehicle number) through an ARS system, in cases where there are multiple vehicles sharing the same information.
[0010] In addition, the embodiment disclosed in this disclosure aims to implement a system capable of preventing unnecessary connection attempts and malfunctions by configuring a flow that immediately determines when a caller's input value is invalid, notifies of the error through ARS guidance, and induces re-input.
[0011] In addition, the embodiments disclosed in this disclosure aim to provide a vehicle calling system capable of ensuring privacy protection and call traceability by connecting a call with a caller using a pre-mapped virtual safe number (e.g., 050x number, etc.) instead of the vehicle owner's actual contact information.
[0012] In addition, the embodiments disclosed in this disclosure aim to realize a parking call platform capable of responding to various call situations, such as smartphone users or general mobile phone users, by integrating and providing a hybrid communication path of QR codes and ARS numbers.
[0013] Meanwhile, the technical problems of the present invention are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem
[0014] A vehicle calling system according to the present disclosure for achieving the technical problem described above, which performs a call connection with a vehicle owner based on input from a caller terminal, comprises: a parking number plate providing number and QR code information for ARS connection; and an application installed on a caller terminal that recognizes a number or QR code from the parking number plate and connects to a vehicle owner; wherein the application may include: an ARS receiving module that receives vehicle identification information within a voice call made by a caller to an ARS number attached to a vehicle; a validity verification module that determines the validity of the vehicle identification information and provides an error guidance if it is invalid; a duplicate item selection module that, if there are multiple vehicles corresponding to the vehicle identification information, guides the caller to the information of the multiple vehicles and receives a selection input; a virtual number connection module that connects the virtual phone number of the owner corresponding to the vehicle selected by the caller to the caller terminal; and a call history management module that records and manages call connection information on a server.
[0015] In addition, the above ARS receiving module can receive a portion of the vehicle number according to the caller's input order, verify the input value, provide a selection request or error guidance, and provide voice guidance for connecting with the vehicle owner.
[0016] In addition, the above validation module verifies the validity of vehicle identification information by comparing it with a pre-registered vehicle number database, and can output a voice guidance prompting the caller to re-enter the information if an unregistered number is entered.
[0017] In addition, the duplicate item selection module can list the entire number of each vehicle by item and provide voice guidance to the caller when there are multiple vehicles corresponding to the input vehicle identification information, and can receive the caller's input for selecting numbers.
[0018] In addition, the virtual number connection module performs a call connection between the caller and the vehicle owner using a virtual safe number of a predetermined format instead of an actual phone number, and can temporarily deactivate the safe number after the connection is terminated.
[0019] In addition, the virtual number connection module can perform vehicle identification information input and selection without ARS calling on a web page accessed by a caller via a QR code attached to the vehicle, and then proceed with a QR linkage mode in which the same virtual number call connection is performed.
[0020] In addition, the above call history management module can store call records on a server, including the time of the ARS call, entered vehicle identification information, caller selection information, and connected virtual number information, and allow them to be viewed through an administrator page.
[0021] In addition, the virtual number connection module can perform a waiting notice, a retry request, or send a voice message to the caller depending on the reception status, including whether the vehicle owner is on a call or has rejected the call, and can provide guidance on the vehicle owner's call status. Effects of the invention
[0022] According to the aforementioned means for solving the problem of the present disclosure, vehicle identification and owner connection can be made possible using only a part of the vehicle number (e.g., the last four digits), thereby reducing the input burden on the caller while providing intuitive usability.
[0023] In addition, according to the aforementioned means for solving the problem of the present disclosure, the possibility of a mistaken connection can be effectively prevented by determining whether there are duplicate vehicle numbers within the ARS flow, and configuring the system to guide the caller to select one if multiple items exist.
[0024] In addition, according to the aforementioned means for solving the problem of the present disclosure, by providing a call flow scenario that subdivides the ARS user experience (UX), flexible and intuitive responses to various situations such as caller input errors, duplicate selections, and call connection failures are possible, thereby maximizing user convenience.
[0025] In addition, according to the aforementioned means for solving the problem of the present disclosure, by providing a connection function through a virtual safe number (e.g., 050x number), the actual contact information of the vehicle owner is not exposed to the outside, and a safe calling environment is provided that allows for the protection of personal information and the tracking of call history.
[0026] In addition, according to the aforementioned means for solving the problem of the present disclosure, by providing a dual access method of QR code and ARS number, it is possible to encompass both a QR access environment using a smartphone and an ARS access environment using a regular mobile phone, thereby ensuring compatibility and accessibility capable of responding to various caller usage environments.
[0027] In addition, according to the aforementioned means for solving the problem of the present disclosure, by including a validation of the validity of the input number and a guidance flow, unnecessary connection attempts caused by incorrect number input or system malfunction can be prevented, and the reliability and efficiency of system operation are improved.
[0028] Furthermore, according to the aforementioned means for solving the problem of the present disclosure, the vehicle call system can be flexibly designed using a pre-registration method or a dynamic mapping method, and thus has great potential for utilization in various application fields, such as not only personal vehicles but also delivery vehicles and commercial vehicles.
[0029] The effects obtainable from the exemplary embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art to which the exemplary embodiments of the present disclosure belong from the description below. That is, unintended effects resulting from the implementation of the exemplary embodiments of the present disclosure can also be derived by those skilled in the art from the exemplary embodiments of the present disclosure. Brief explanation of the drawing
[0030] FIG. 1 is a diagram showing an ARS and QR-linked vehicle owner call system according to an embodiment. Figure 2 is a diagram showing the data processing configuration of a terminal according to an embodiment. FIG. 3 is a diagram showing the processor configuration according to an embodiment. FIGS. 4 to 6 are drawings showing example screens of a QR-based vehicle call interface according to an embodiment. FIG. 7 is a diagram illustrating a vehicle owner call process according to an embodiment. Specific details for implementing the invention
[0031] Hereinafter, various embodiments of the present disclosure are described in conjunction with the accompanying drawings. As various embodiments of the present disclosure may be subject to various modifications and may have various forms, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the various embodiments of the present disclosure to specific forms, and it should be understood that they include all modifications and / or equivalents and substitutions that fall within the spirit and scope of the various embodiments of the present disclosure. In relation to the description of the drawings, similar reference numerals have been used for similar components.
[0032] In various embodiments of the present disclosure, terms such as “comprising” or “having” are intended to indicate the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.
[0033] In various embodiments of the present disclosure, expressions such as “or” include any and all combinations of the words listed together. For example, “A or B” may include A, may include B, or may include both A and B.
[0034] Expressions such as "first," "second," "first," or "second" used in various embodiments of the present disclosure may modify various components of the various embodiments, but do not limit such components. For example, such expressions do not limit the order and / or importance of such components and may be used to distinguish one component from another.
[0035] When it is mentioned that a component is "connected" or "joined" to another component, it should be understood that the component may be directly connected or joined to the other component, but that a new component may also exist between the component and the other component.
[0036] In the embodiments of the present disclosure, terms such as "module," "unit," "part," etc. are used to refer to a component that performs at least one function or operation, and such component may be implemented in hardware or software, or in a combination of hardware and software. Additionally, a plurality of "modules," "units," "parts," etc. may be integrated into at least one module or chip and implemented as at least one processor, except where each needs to be implemented in specific individual hardware.
[0037] Terms such as those defined in commonly used dictionaries should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in the various embodiments of the present disclosure.
[0038] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0039] FIG. 1 is a diagram showing an ARS and QR-linked vehicle owner call system according to an embodiment.
[0040] Referring to FIG. 1, the ARS and QR-linked vehicle owner call system according to the embodiment may be configured to include a parking number plate (200), an application (100) installed on a caller terminal, and a server (300).
[0041] The parking number plate (200) provides number and QR code information for ARS connection to the vehicle owner's terminal. In the embodiment, the application (100) is installed on the caller and vehicle owner's terminals and recognizes the number or QR code from the parking number plate to connect the caller and the vehicle owner. In the embodiment, the parking number plate (200) is attached to the exterior of the vehicle and visually provides phone number and QR code information for ARS connection to induce a call with the vehicle owner. In the embodiment, the ARS number is configured so that the caller can call the vehicle owner based on voice call using a standard telephone, and the QR code is configured to connect to a web-based call interface or application by scanning it through a camera such as a smartphone.
[0042] Additionally, the parking number plate (200) may be registered with the server (300) in advance to be linked to an ARS system or QR path mapped to part of the vehicle number or a unique identifier.
[0043] The server (300) performs the role of searching for corresponding vehicle information based on vehicle identification information entered by the caller, transmitting the virtual number of the vehicle owner to the caller's terminal, relaying a call connection request, or storing and managing connection history. Additionally, if there are multiple vehicles corresponding to the same identification information, the server (300) can perform the function of generating a duplicate item list to guide the caller to the candidate information and designating the final connection target according to the caller's selection.
[0044] Additionally, the application (100) may be installed on the caller's terminal or the vehicle owner's terminal, respectively, and performs the role of recognizing the number or QR code displayed on the parking number plate (200) to transmit vehicle identification information to the server (300), and controlling a series of call procedures such as ARS flow guidance, vehicle number input, duplicate selection, and virtual number call connection. Furthermore, the application (100) may provide additional functions such as reception settings, connection time control, automatic response function, and call history check on the vehicle owner's terminal, and provide user convenience functions such as easy connection and recent call history lookup on the caller's terminal.
[0045] Figure 2 is a diagram showing the data processing configuration of a terminal according to an embodiment.
[0046] In an embodiment, the caller terminal (100) may be implemented as a computer capable of connecting to a remote server or terminal via a network. Here, the computer may include, for example, a laptop, desktop, or laptop equipped with a navigation system or a web browser. At this time, at least one terminal (100) is a network
[0047] It can be implemented as a terminal capable of connecting to a remote server or terminal. At least one terminal (100) may include all kinds of handheld-based wireless communication devices, such as navigation, PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), Wibro (Wireless Broadband Internet) terminal, smartphone, smartpad, tablet PC, etc., as a wireless communication device that ensures portability and mobility.
[0048] The configuration of the terminal (100) shown in FIG. 2 is merely a simplified example.
[0049] The communication module (110) can be configured regardless of the mode of communication, such as wired or wireless, and can be configured with various communication networks, such as a Personal Area Network (PAN) or a Wide Area Network (WAN). Additionally, the communication module (110) can operate based on the known World Wide Web (WWW) and may utilize wireless transmission technologies used for short-range communication, such as Infrared Data Association (IrDA) or Bluetooth. For example, the communication module (110) may be responsible for transmitting and receiving data necessary to perform a technique according to one embodiment of the present disclosure.
[0050] Memory (120) may refer to any type of storage medium. For example, memory (120) may include at least one type of storage medium among flash memory type, hard disk type, multimedia card micro type, card type memory (e.g., SD or XD memory, etc.), RAM (Random Access Memory), SRAM (Static Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), PROM (Programmable Read-Only Memory), magnetic memory, magnetic disk, and optical disk. Such memory (120) may also constitute the database shown in FIG. 1.
[0051] The memory (120) can store at least one instruction that can be executed by the processor (130). Additionally, the memory (120) can store any form of information generated or determined by the processor (130) and any form of information received by the server (200). Additionally, the memory (120) stores various types of modules, instruction sets, or models.
[0052] The processor (130) can perform technical features according to embodiments of the present disclosure to be described below by executing at least one instruction stored in memory (120). In one embodiment, the processor (130) may be composed of at least one core and may include a processor for data analysis and / or processing, such as a central processing unit (CPU) of a computer device, a general purpose graphics processing unit (GPGPU), or a tensor processing unit (TPU).
[0053] This processor (130) can train a neural network or model designed in a machine learning or deep learning manner. To this end, the processor (130) can perform calculations for training the neural network, such as processing input data for training, extracting features from input data, calculating errors, and updating the weights of the neural network using backpropagation. Additionally, the processor (130) can perform inference for a specific purpose using a model implemented in an artificial neural network manner.
[0054] FIG. 3 is a diagram showing the processor configuration according to an embodiment.
[0055] Referring to FIG. 3, the instruction set according to the embodiment may be configured to include an ARS receiving module (131), a validation module (132), a duplicate item selection module (133), a virtual number connection module (134), a call history management module (135), a call status tracking module (136), an update management module (137), a rate policy control module (138), a revenue linkage module (130), and a response evaluation module (1311). The term "module" as used herein should be interpreted to include software, hardware, or a combination thereof, depending on the context in which the term is used. For example, software may be machine language, firmware, embedded code, and application software. As another example, hardware may be a circuit, a processor, a computer, an integrated circuit, an integrated circuit core, a sensor, a MEMS (Micro-Electro-Mechanical System), a passive device, or a combination thereof.
[0056] The ARS receiving module (131) receives vehicle identification information within a voice call made by a caller to an ARS number attached to a vehicle. In the embodiment, the ARS receiving module (131) receives a user input value in which vehicle identification information (e.g., the last four digits of a vehicle number) is entered in a DTMF (Dual Tone Multi Frequency) manner according to voice guidance after the caller connects to the system through a voice call path made by a caller to an ARS number attached to the outside of the vehicle, and decodes the input value. In the embodiment, the ARS receiving module (131) detects and collects the input DTMF signal in real time and transmits it to a server (300) or an upper control module so that it can be used in subsequent validation and vehicle owner identification processes, and may also include error detection and re-input induction procedures for exception situations such as input delay, incorrect format, or no response.
[0057] The validation module (132) determines the validity of the vehicle identification information and provides an error notification if it is invalid. In the embodiment, the validation module (132) determines the validity of the input value by comparing the vehicle identification information entered through the ARS receiving module (131) with the identification information records stored in the vehicle database or server (300) that were previously registered. To this end, the validation module (132) determines whether a part of the entered vehicle number (e.g., the last four digits) matches one of the valid vehicle identification information registered in the system, and if the result is incorrect or unregistered, it outputs an error voice notification to the caller, such as "Invalid number" or "Unregistered vehicle," and controls the flow of the process to induce re-entry or end the call.
[0058] In addition, the validation module (132) can determine that an input error or timeout has occurred and perform a separate exception notification procedure even if input is not made within a certain period of time or if the input format differs from the system standard.
[0059] Additionally, the duplicate item selection module (133) guides the caller to the information of multiple vehicles and receives a selection input when there are multiple vehicles corresponding to the vehicle identification information. In an embodiment, when the vehicle identification information received through the ARS receiving module (131) overlaps with the information of multiple vehicles stored in the server (300), the duplicate item selection module (133) guides the caller to the list of all vehicles corresponding to the identification information through a voice or visual interface and receives a selection input from the caller. Through this, when a part of the entered vehicle number (e.g., "1234") matches the identification information of multiple vehicles, the duplicate item selection module (133) guides the caller to the full vehicle number or key distinguishing information of multiple items in the form of, for example, "123ga1234 is number 1, 345na1234 is number 2, and 567da1234 is number 3," and induces the caller to select which vehicle among the items to select using a number key input or other designated method.
[0060] In the embodiment, when a selected input value is received, the duplicate item selection module (133) identifies the vehicle owner information (e.g., virtual number) mapped to the item and transmits the control flow to a subsequent call connection step. Additionally, if the caller enters an invalid number or the input time is exceeded, an exception handling flow including a request for re-entry or a connection termination notice may also be supported.
[0061] The virtual number connection module (134) connects the owner's virtual phone number corresponding to the vehicle selected by the caller to the caller's terminal. In an embodiment, the virtual number connection module (134) performs the function of connecting the owner's contact information corresponding to the finally identified vehicle to the caller's terminal according to the processing result of the duplicate item selection module (133) or the validity verification module (132). At this time, control is provided so that a call connection is made through a pre-mapped virtual phone number (e.g., a secure number in the 050x format) instead of an actual contact. To this end, the virtual number connection module (134) refers to the vehicle identification information and the owner's virtual number mapping table stored in the server (300) to extract a virtual number corresponding to the vehicle selected or entered by the caller, and controls the system to connect the virtual number to the caller's terminal. At this time, the virtual number may be automatically discarded or deactivated after a certain period of time has elapsed since the call connection, and provides a secure connection path for protecting the privacy of both users and for recording call history on the server.
[0062] Additionally, the virtual number connection module (134) may include subsequent flow control functions, such as a waiting notice, a retry request, or a voice message recording notice, when a caller attempts to connect but the receiving terminal is busy or does not respond.
[0063] The call history management module (135) records and manages call connection information on a server. In an embodiment, the call history management module (135) records various information generated during the call connection process between a caller and a vehicle owner on the server (300) and manages it in an integrated manner. To this end, the call history management module (135) collects call-related data in real time, such as the caller's ARS call time, entered vehicle identification information, validity judgment results, duplicate item selection history, virtual number mapping information, call connection status, and duration, stores it on a server, and manages it in a log format so that it can be preserved for a certain period. Additionally, the call history management module (135) can provide an interface that allows an administrator or system operator to perform call history inquiry, abnormal connection detection, call statistics analysis, etc., based on the collected data, and is linked with an API or administrator portal so that it can be utilized for purposes such as handling user complaints, detecting malfunction history, and securing security audit history as needed. In this way, the call history management module (135) can improve the stability and operational efficiency of the system by ensuring transparency and reliability of the call system and realizing post-call tracking and management functions for the call history between the vehicle owner and the caller.
[0064] In the embodiment, the ARS receiving module (131) receives a portion of the vehicle number (e.g., the last four digits) according to the caller's input order, checks the input value, provides a selection request or error guidance, and provides voice guidance for connecting with the vehicle owner. Additionally, within a voice call made by the caller to an ARS number attached to the outside of the vehicle, the ARS receiving module (131) receives a portion of the vehicle number according to a predefined order, determines the validity of the input value, provides a selection request or error guidance, and provides voice guidance for the procedure to connect with the vehicle owner. To this end, the ARS receiving module (131) induces the input of a portion of the vehicle number. In the embodiment, when the caller is connected to the system, the ARS receiving module (131) induces the caller's input by outputting a vehicle identification information input request message, such as "Please enter the last four digits of the vehicle number and press the asterisk (*)," through voice guidance.
[0065] Afterward, when the caller enters part of the vehicle number using the DTMF method, the ARS receiving module (131) receives the input value and verifies whether the number of digits and format of the input value match the system's standards. At this time, if the input value is appropriate, it provides an input value confirmation voice message such as "The number you entered is XXXX. If correct, press 1, and press 2 to enter again." so that the caller can confirm it.
[0066] In the embodiment, if the input value is invalid or is a number not registered in the system, an error voice guidance such as "The number you entered is invalid" is output, and the caller is prompted to re-enter or the call is terminated. Conversely, if there are multiple vehicles corresponding to the input value, an item-specific guidance voice such as "123-ga-1234 is number 1, and 234-na-1234 is number 2" is output in conjunction with the duplicate item selection module (133), and the caller is prompted to select an input.
[0067] In the embodiment, when the finally selected vehicle information is confirmed, the ARS receiving module (131) outputs a call connection guidance voice such as "Connecting with the vehicle owner based on the information you entered. Please wait a moment," and proceeds with the call connection procedure through the subsequent virtual number connection module (134).
[0068] In the embodiment, the ARS receiving module (131) can minimize input errors, information duplication, abnormal connections, etc. that may occur during the connection process between the caller and the vehicle owner, and can ensure a consistent user experience (UX) and a stable connection flow.
[0069] The validation module (132) verifies the validity of vehicle identification information by comparing it with a pre-registered vehicle number database, and outputs a voice guidance to induce the caller to re-enter the information if an unregistered number is entered. The validation module (132) determines the validity of the vehicle identification information received through the ARS receiving module (131) by comparing it with a pre-registered vehicle number database, and provides appropriate voice guidance to the caller based on the result. In an embodiment, when a caller enters a part of the vehicle number (e.g., the last four digits) in the DTMF format, the corresponding input value is received through the ARS receiving module (131) and transmitted to the validation module (132). Subsequently, the validation module (132) refers to a pre-registered vehicle number list from the server (300) or the linked database and compares whether the entered vehicle identification information matches one of the registered items. This comparison is performed including character matching, digit count verification, and registration status check, and if an item that exactly matches exists, it is determined to be valid information.
[0070] Subsequently, if one or more of the entered vehicle identification information matches, the system forwards the information to the duplicate determination and connection processing flow, and if it is invalid or does not match the registered information, it performs an error handling procedure.
[0071] In addition, in the embodiment, if the input value is not registered in the system, the validation module (132) outputs a voice guidance message to the caller, such as "The number you entered is invalid. Please press 1 to enter again," or "There are no registered vehicles. Please check the number again," and prompts for re-entry. In the embodiment, if the caller selects to re-enter, the system enters the input loop again, and if the error is repeated more than a certain number of times, the call may be terminated or switched to an exception flow such as a guide to connect to an agent.
[0072] In addition, the validation module (132) can detect exceptional situations such as insufficient digits in the input value, non-numeric signals, or timeouts, and in such cases, it can be configured to minimize user errors through guidance messages such as "Input timed out. Please try again from the beginning." Such procedures of the validation module (132) provide effects such as preventing input errors, blocking abnormal connections, improving user satisfaction, and ensuring system reliability, and contribute to simultaneously ensuring accuracy and efficiency of the call flow.
[0073] Additionally, if there are multiple vehicles corresponding to the input vehicle identification information, the duplicate item selection module (133) lists the entire number of each vehicle by item and provides voice guidance to the caller, and receives the caller's number selection input. The duplicate item selection module (133) lists the entire number of each vehicle by item and provides voice guidance to the caller, and receives the caller's selection input, in accordance with the input vehicle identification information confirmed through the validity verification module (132), if there are multiple vehicles. To do this, the duplicate item selection module (133) first searches for and obtains a list of all vehicles that match the identification information entered by the caller (e.g., the last four digits of the vehicle number) in the registered vehicle number database when the vehicle identification information entered by the caller (e.g., the last four digits of the vehicle number) matches multiple vehicles.
[0074] Subsequently, when multiple vehicle numbers are searched, the module separates each vehicle number into a unique item and maps it to sequential numbers (e.g., 1, 2, 3...) to form an item-specific index. For example, it forms voice guidance items that can be intuitively selected by the caller, such as "123ga1234 is number 1, 234na1234 is number 2, and 345da1234 is number 3."
[0075] Subsequently, the mapped vehicle number list is output as voice to the caller via Text-to-Speech (TTS) conversion or a pre-registered voice file, and the caller is guided to select the desired item after listening to the number of each item through voice guidance. Additionally, the caller inputs a number (e.g., one of 1, 2, or 3) corresponding to the desired vehicle number among the guided items using the DTMF method, and the duplicate item selection module (133) receives and reads the input value to identify the finally selected vehicle. Furthermore, in the embodiment, if the caller enters an invalid number or there is no input within a certain period of time, an exception guidance voice such as "Selection timed out. Please press 1 to try again" or "Invalid input. Starting over from the beginning" is output, and a loop re-entry or call termination procedure can be performed.
[0076] Additionally, the virtual number connection module (134) performs a call connection between the caller and the vehicle owner using a virtual safe number of a predetermined format instead of an actual phone number, and temporarily deactivates the safe number after the connection is terminated. In an embodiment, the virtual number connection module (134) performs a call connection using a pre-mapped virtual safe number (e.g., 050x format) to prevent the actual phone number from being exposed to the outside during the process of connecting the contact information of the vehicle owner corresponding to the vehicle selected by the caller to the caller's terminal, and temporarily deactivates the safe number after the connection is terminated. To this end, when the caller first selects a specific vehicle through the duplicate item selection module (133) or a single vehicle is identified through the validity verification module (132), the virtual number connection module (134) looks up a virtual safe number corresponding to the actual phone number by referring to a virtual number mapping table stored in the server (300) based on the identification information of the vehicle.
[0077] Subsequently, the virtual number connection module (134) establishes a call path to connect a call request from a caller terminal to the vehicle owner's actual terminal by utilizing the retrieved virtual safe number as a relay number. At this time, the caller does not know the vehicle owner's actual phone number, and the call is made internally through a relay server or communication gateway within the system. This virtual number connection method enables smooth communication without direct exchange of personal information between the caller and the vehicle owner, thereby providing the effect of protecting personal information and guaranteeing anonymity for both parties. In addition, history such as the time of the call, virtual number usage history, and call duration can be recorded on the server.
[0078] Subsequently, when a call ends, the virtual number connection module (134) switches the virtual safe number to a temporarily deactivated or unusable state immediately or after a certain period of time, thereby blocking unauthorized communication attempts to the same virtual number thereafter and enhancing security by maintaining a one-time connection structure. Additionally, in the embodiment, the virtual number may be set to have a certain validity period, or a reply blocking policy may be applied to prevent the caller from calling the vehicle owner again, and such settings are predefined by the vehicle owner or administrator.
[0079] In addition, in the embodiment, the virtual number connection module (134) can perform a QR linkage mode in which vehicle identification information can be entered and selected without an ARS call on a web page accessed by a caller via a QR code attached to the vehicle, and subsequently a call connection to the same virtual number is performed. In the embodiment, the virtual number connection module (134) performs a QR linkage mode configured to allow vehicle identification information to be entered and selected without an ARS call on a web page accessed by a caller via scanning a QR code attached to the vehicle, and performs a call connection through a virtual safe number based on the entered identification information.
[0080] To this end, the virtual number linkage module (134) allows the caller to scan a QR code attached to the outside of the vehicle with a terminal such as a smartphone and automatically access a web-based call page (URL) linked thereto. The QR code may contain information for vehicle identification (e.g., vehicle ID, connection token, etc.) or may serve as an identification key for loading the call page on the server (300). In the embodiment, the web page accessed by the caller requests the input of a part of the vehicle number (e.g., the last four digits) or automatically retrieves information on multiple candidate vehicles based on the vehicle ID included in the QR code.
[0081] In the embodiment, when multiple vehicles are searched, the full number of each vehicle is displayed by item on the web screen, and the caller can select the desired item by touch or click. This is a user interface configuration that provides the same selection process as a voice-based ARS flow in a GUI environment.
[0082] Afterward, when the caller completes the selection, the virtual number connection module (134) looks up the virtual safe number (e.g., in the 050x format) mapped to the vehicle and provides a callable call link (e.g., tel: / / 050xxxxxxx) or an immediate connection button so that the caller can request a call with the vehicle owner directly from the caller's terminal. This allows the caller to perform a call connection based on the same virtual number without going through a separate ARS system.
[0083] Additionally, in the embodiment, when a call is established, the caller and the vehicle owner do not know each other's actual phone numbers, and the call is made through a virtual number relay server or a SIP gateway. At this time, the connection history is recorded in the server (300), and the virtual number may be temporarily deactivated when the connection is terminated.
[0084] In addition, on the web page, functions such as text message requests, photo transmission, and voice message leaving can be extended in addition to calls, and such configurations can be implemented through a web app (App-less environment) or a dedicated application depending on the caller's terminal environment. In this way, the virtual number connection module (134) can provide the same call function even in user environments where access to ARS is difficult by additionally performing a call connection scenario (QR linkage mode) through a QR-based connection path, and can significantly improve the accessibility of the system and user convenience.
[0085] In addition, by utilizing the same virtual number mapping system in common, consistency in security and call history management can also be maintained.
[0086] Subsequently, a call connection is established with the vehicle owner's terminal via the 050x virtual number registered to the selected vehicle. If the vehicle owner is currently on a call, a voice message such as "Currently on a call. Please try again later" is provided, and if there is no response, a function to leave a voice message is provided. This embodiment incorporates duplicate selection and exception handling logic into a traditional ARS-based call flow to prevent misconnection and improve the user experience (UX).
[0087] Additionally, the call history management module (135) stores call records on a server, including the time of the ARS call, entered vehicle identification information, caller selection information, and connected virtual number information, and makes them viewable through an administrator page. When a caller attempts to connect with a vehicle owner or a connection is established, the call history management module (135) records various information generated during the call process on the server (300) and provides the recorded information so that a system administrator or operator can subsequently view and manage it. To this end, at the time when a caller attempts to connect with a vehicle owner by making a call to an ARS number attached to the vehicle or by accessing a call web page via a QR code, the call history management module (135) includes (a) the time of the ARS call or the time of QR access, and (b) vehicle identification information entered by the caller (e.g., the last digits of the vehicle number). (c) if duplicate items exist, information on the vehicle item selected by the caller, (d) a virtual safe number (050x number, etc.) assigned by the server, and (e) call-related data including the call connection result (e.g., connection successful, in progress, no response, etc.) are collected.
[0088] In the embodiment, the collected call history information is stored in real time in the history storage or log database of the server (300), and each history item is indexed based on a unique identifier (UUID) or timestamp and systematically managed. Additionally, for the protection of personal information, the caller's phone number or the actual number of the vehicle owner is not stored and may be recorded in a virtual number and masked form. Subsequently, the call history management module (135) is linked with a separate web-based administrator interface or an integrated operating system so that an administrator can subsequently view or search for specific history. In the embodiment, the administrator page may provide sorting, filtering, and search functions based on fields such as the call date, part of the vehicle number, selected item, virtual number, connection status, and call duration.
[0089] The call history stored in this manner can be utilized for various operational purposes, such as system maintenance, responding to user inquiries, detecting abnormal connections, traffic analysis, and improving connection success rates. Additionally, an administrator or server can perform functions such as automatically generating statistical reports, backing up history, or providing notifications for abnormal usage detection. In the embodiment, the call history management module (135) stores all inputs and processing results of ARS and QR-based call flows as structured history data on the server, thereby realizing various effects such as ensuring operational reliability, protecting users, and improving the efficiency of system maintenance.
[0090] Additionally, the virtual number connection module (134) performs a waiting notice, a retry request, or a voice message transmission to the caller according to the vehicle owner's reception status (e.g., whether the call is in progress, rejection of reception, etc.), and provides guidance on the vehicle owner's call status. In the embodiment, the virtual number connection module (134) determines the vehicle owner's reception status (e.g., in progress, rejection of reception, no response, etc.) in real time while attempting to connect a call with the vehicle owner selected by the caller, performs a waiting notice, a retry request, or a voice message transmission function to the caller according to the status, and provides the reason for the inability to make a call as a voice notice.
[0091] To this end, when a call connection request is made from the caller's terminal to the vehicle owner's virtual safe number (e.g., 050x number), the virtual number connection module (134) attempts to connect to the actual phone number mapped to the virtual number through a relay server or SIP gateway. After the connection request, it receives a reception response signal from the vehicle owner's terminal and determines the call status in real time, such as (a) a normal connection possible state, (b) a busy state, (c) a call rejection state, or (d) a no answer state. Subsequently, depending on the reception status, the virtual number connection module (134) may provide the caller with a voice guidance flow or an alternative path as follows.
[0092] In the embodiment, if a call is in progress, "The other party is currently on another call. Please try again later." is displayed to provide guidance on waiting or choosing to retry, and if the call is rejected, a retry request guidance after the call ends is provided, such as "The other party is unable to answer the call. Please try again later."
[0093] In addition, in the case of no response, the caller is prompted to select whether to send a voice message via DTMF input, such as "The other party is not responding. Please press 1 to leave a voice message or 2 to end."
[0094] In addition, in the embodiment, if the caller selects to leave a voice message, the virtual number connection module (134) switches to a message recording interface, records the caller's voice for a certain period of time, and then saves the voice file to a server or delivers it to the vehicle owner's terminal via a push notification, MMS, or a dedicated app. In the embodiment, the caller is clearly guided on the vehicle owner's current call status and available action options, and the system can prevent misconnection, minimize unnecessary repeated calls, and improve the caller's user experience (UX) through this guidance flow. Furthermore, the virtual number connection module (134) includes sophisticated guidance and response procedures based on the reception status in addition to a simple connection attempt, thereby increasing the reliability and efficiency of the vehicle call system and enabling user-friendly functions.
[0095] In addition, in the embodiment, the call status tracking module (136) detects call connection failure events (e.g., call rejection, no answer, etc.) that occur repeatedly to the vehicle owner, and if the cumulative number of such events reaches a preset threshold, it sends a notification to the vehicle owner or automatically imposes a penalty such as restricting the call function, deducting the internal system evaluation score, or outputting a warning message. In the embodiment, the server (300) records the call status for each call attempt, and if a Call Rejected or No Answer status occurs consecutively for the same vehicle for a predetermined number of times (e.g., 3 times) or more, it sends a push notification or text message to the vehicle owner's terminal stating, "Consecutive call rejections have been detected. Restrictions on the use of the call system may occur." It then restricts the call connection for a certain period of time or outputs a guidance message to the caller stating, "The connection has been restricted because the other party has not responded for a long time," and lowers the trust index or response rating for the vehicle owner within the system, thereby inducing the user to improve their own response rate. In addition, these response rate-based control policies can be checked in real time on the vehicle owner's app screen or administrator interface, thereby enhancing the transparency of the system and the user's awareness of responsibility.
[0096] In the embodiment, the call status tracking module (136) can calculate a penalty score P based on the ratio and continuity of call rejection or no answer statuses among call attempts that occurred for a single vehicle owner over a certain period, as shown in Equation 1.
[0097] Mathematical formula 1
[0098]
[0099] In Equation 1, Nfail is the number of calls determined to be rejected or unanswered within the observation period, Ntotal is the total number of call attempts, Lconsec is the maximum length of consecutive failure events (rejection / unanswered), and α and is a weighting coefficient based on system settings. Mathematical Equation 1 enables response attitude analysis that reflects not only simple failure rates but also continuity patterns, thereby allowing the provision of behavior-based control logic.
[0100] In the embodiment, the call status tracking module (136) performs management procedures, such as restricting calls to the vehicle owner, lowering the reliability score within the system, or providing feedback to induce a response, based on a penalty score P calculated by analyzing the history of call connection failures for the vehicle owner. To this end, the call status tracking module (136) calculates a penalty score reflecting the rate and continuity of call rejection or non-response events based on call logs over a certain period, and if the score is above a preset threshold, it enables the execution of one or more control procedures including restricting the call function, lowering the system reliability score, transmitting automatic feedback, recording statistics, and notifying an administrator. In the embodiment, restricting the call function involves automatically disabling the virtual number connection function for the vehicle owner for a certain period of time or restricting the same caller from attempting repeated calls.
[0101] Lowering the system reliability score is a setting that reduces the internally defined Response Score (RS) for a vehicle owner account or registered vehicle to affect the recommendation ranking or display priority provided to callers in the future.
[0102] Automated feedback transmission encourages improved user response behavior by automatically sending warning messages, push notifications, or emails to vehicle owners, such as "Call connections have repeatedly failed recently. Please improve your call response rate." Regarding statistical recording and administrator notifications, information on users whose penalty scores consistently exceed a threshold is accumulated in the history management module of the operations server, allowing them to be marked as warning targets or enabling additional actions via the administrator page.
[0103] Additionally, in the embodiment, the call status tracking module (136) measures the elapsed time from when the call connection between the caller and the vehicle owner is completed until the vehicle owner's actual parking location is modified or movement is detected, and if the elapsed time exceeds a preset reference time, the vehicle owner's penalty score is deducted. To this end, the virtual number connection module (134) calculates the elapsed time through the difference between the time when the call between the caller and the vehicle owner ends and the time when the vehicle's parking location is modified or movement is detected based on GPS or sensors after the end time. In the embodiment, if the elapsed time exceeds a reference time (e.g., 5 minutes), the system can adjust the penalty score of the vehicle owner.
[0104] For example, the call status tracking module (136) can increase the penalty score P of the vehicle owner according to a predetermined weight. The new penalty can be calculated through Equation 2.
[0105] Mathematical formula 2
[0106]
[0107] In Equation 2, S_penalty is the cumulative penalty score of the vehicle owner, γ is the penalty weighting factor for timeout, Tres is the elapsed time from the end of the call until the vehicle location is actually corrected, and Tth is the maximum allowable response time defined by the system (e.g., 300 seconds). This formula can evaluate the behavior of the vehicle owner by accumulating penalty points based on the delayed response time.
[0108] In addition, in the embodiment, if the elapsed time exceeds a threshold, a push notification or SMS message such as "Parking location action was delayed after the call. This may affect call response quality" is sent to the vehicle owner's terminal to induce behavioral improvement.
[0109] In addition, in the embodiment, if a delay in elapsed time exceeding a threshold occurs more than the cumulative count threshold, the system may be configured to restrict the call connection function for the vehicle owner for a certain period of time or to exclude them from priority call targets. Furthermore, whether the vehicle's location has changed can be automatically detected through a dedicated application running on the owner's terminal via GPS location information, BLE tag movement detection, or integration with a parking control system, and can be recognized in the same way even if the vehicle owner manually registers a change in location.
[0110] In the embodiment, the renewal management module (137) ensures that the call function is valid for a predefined validity period from the vehicle registration date or the first call date, and if the validity period is exceeded, provides a call restriction notice message to the caller and sends a notice message to the vehicle owner regarding service extension or conversion to a paid service. In the embodiment, the renewal management module (137) calculates a predefined validity period (T_valid) based on the earlier of the vehicle identification information registration date or the first call date, periodically checks whether the validity period has expired, and if the validity period is exceeded, outputs a notice message regarding the restriction of the call function to the caller terminal. At the same time, it performs the function of sending a notice message to the vehicle owner terminal regarding the fact that the service validity period has expired and regarding extension or conversion to a paid service. In the embodiment, the renewal management module (137) can simultaneously secure operational efficiency of the service and flexibility in applying the billing policy by dynamically controlling whether the call function is continuously provided.
[0111] Additionally, when the rate policy control module (138) receives a rate plan for the use of the call function from the vehicle owner, usage conditions such as the number of possible calls, connection time, and message transmission function are determined according to the selected rate plan, and the call function is restricted or expanded according to the said conditions. In an embodiment, the rate policy control module (138) receives a rate plan type for the use of the call function from the vehicle owner terminal, and dynamically determines one or more usage conditions such as the number of possible calls, single call connection time, whether to include a text message transmission function, and the call record retention period according to the received rate plan, and operates in a manner that restricts or expands the provision of the call function or the function range based on the determined usage conditions. In an embodiment, the rate plan types may be classified, for example, into a basic type, a premium type, and an event type; in the case of the basic type, the number of monthly calls and call time are limited, while in the premium type, the call function is provided without restriction and may include text transmission and call log storage functions. In this way, the rate policy control module (138) enables the implementation of a revenue model through inducing access to paid services and differentiating functions by controlling the usage range of the call function within the system according to the selected rate plan.
[0112] In addition, in the embodiment, the QR code-based web page includes a third-party advertising area, and the revenue linkage module (130) records advertising revenue information on the server when a caller clicks on an advertisement or displays it for a certain period of time or longer, and sets up the distribution of a portion of the revenue to the vehicle owner account or the system administrator account. The revenue linkage module (130) includes an advertising area containing third-party advertising content on the web-based call interface screen accessed by a caller scanning a QR code attached to the vehicle, and when it detects a click event by a caller or a viewing exposure event for a certain period of time or longer regarding the content within the advertising area, it records the details of advertising revenue generation on the server based on the event information. Furthermore, the revenue linkage module (130) refers to the advertising revenue information recorded on the server and processes the distribution of a portion or all of the advertising revenue to the vehicle owner account, the system administrator account, or an external affiliate account according to a pre-set revenue distribution policy. Through this, the QR-based call system goes beyond a simple means of connecting calls and internalizes revenue generation functions based on advertising exposure and clicks, thereby providing substantial incentives to the vehicle owner and simultaneously enabling the implementation of a sustainable revenue model for the system operator.
[0113] Additionally, the response evaluation module (1311) calculates a response reliability score based on the vehicle owner's call reception history, and if the score is below a preset threshold, it temporarily restricts the call connection to the vehicle or provides a notice to the caller stating, "This is a vehicle with restricted connections," and the score can be checked in real time on the administrator page. In the embodiment, the response evaluation module (1311) calculates the vehicle owner's response reliability score by evaluating factors such as whether a response was given, the waiting time for reception, the number of rejections, and the frequency of non-response based on past call history data received by the vehicle owner's terminal.
[0114] The above response reliability score can be calculated by a quantitative evaluation formula that combines, for example, the response rate among the last N calls, the average connection waiting time, the rejection rate, etc., and if the calculated score is below a preset threshold, the system performs one or more control procedures. In the embodiment, the control procedures include temporarily restricting the call function for the vehicle and outputting a guidance message to the caller, but are not limited thereto.
[0115] The temporary restriction of the call function for the vehicle in question is to automatically block the connection or handle a connection failure response when a caller attempts to make a call.
[0116] The output of an informational message to the caller is to provide, for example, a voice or screen announcement stating, "Calls are currently restricted for this vehicle due to a low response rate."
[0117] In addition, the above response reliability score can be viewed in real time through a dedicated page for system administrators or an integrated control interface, allowing the administrator to systematically assess the vehicle owner's service usage integrity or call response quality. In the embodiment, the response evaluation module (1311) quantitatively evaluates the response quality of the vehicle call service and autonomously restricts the use of non-responding users, thereby realizing technical effects such as improved caller satisfaction, enhanced system operation efficiency, and strengthened control functions against unfaithful users.
[0118] In addition, in the embodiment, the call history management module (135) links the call history data, which includes the time of the call, vehicle number, response status, and location information of the caller, to an external server or affiliated organization, and allows it to be utilized for commercial data analysis or customer service improvement with the user's consent. In the embodiment, the call history management module (135) is configured to store and transmit call history data generated during the vehicle calling process, and the call history data includes the time of the call, vehicle number (or vehicle identification information), whether the call was answered, whether the call was successful, and the caller's location information (GPS coordinates or cell-based location information). The call history management module (135) links the stored call history data to an external linked server, affiliated organization, or statistical analysis platform only when the user's prior consent is secured, and the linked data can be utilized for the following purposes. For example, it can be analyzed as data for commercial purposes. Specifically, it can be analyzed for vehicle call density analysis by time of day, statistics on parking inconvenience by region, and vehicle classification based on user response rates.
[0119] Furthermore, it can be used for quality analysis to improve customer service. Specifically, it can be analyzed for tracking call failure patterns, automating lists of non-responding vehicles, and generating location-based response quality maps. Additionally, within the scope of user consent, this embodiment may transmit collected historical data after de-identifying it into a form that makes personal identification impossible, or apply encryption or anonymization methods that comply with privacy policies. By providing advanced analysis functions based on call records, the call history management module configured in this manner can realize technical effects such as improving the operational quality of the vehicle hailing system, expanding partnership services, and developing data-driven commercial models.
[0120] FIG. 4 is a diagram showing an example screen of a QR-based vehicle call interface according to an embodiment. Referring to FIG. 4, the vehicle call system according to the embodiment provides a web-based call page that is automatically accessed when a caller scans a QR code attached to a vehicle. The page includes a GUI (Graphic User Interface) based call interface that links vehicle identification information with call / text functions. The top of the screen includes the QR code scanned by the caller or an identification image that visually displays it. This facilitates mapping between the vehicle and the corresponding call page and serves as a standard for authentication and unique connection. In the embodiment, the full vehicle number (e.g., "123ga1234") is displayed in text form at the bottom of the QR code, allowing the caller to visually identify the vehicle. Additionally, a fixed phrase pre-entered by the vehicle owner or an automatically generated status message (e.g., "Please wait a moment, I will move the car") is displayed, and this message serves as a means to convey the vehicle owner's intent or intention to the caller. The message may be placed within a rectangular frame or a speech bubble-shaped visual container on the screen. As illustrated in FIG. 4, the call interface can implement a QR-based non-face-to-face call flow without an ARS, and by integrally providing vehicle identification, communication means connection, and user guidance functions, it can simultaneously satisfy the convenience of the caller and the protection of the vehicle owner's personal information.
[0121] FIG. 5 is a diagram showing an example screen of a vehicle number plate registration and QR device linkage interface according to an embodiment.
[0122] Referring to FIG. 5, a dedicated application or administrator system used by the vehicle owner includes a user interface for registering a vehicle number, linking devices, and adding a calling device via QR scanning. In the embodiment, a QR code and contact information corresponding to a vehicle number plate registered by the vehicle owner (e.g., "123-ga 1234") are displayed, and a "+" button is provided for registering a new number plate.
[0123] As illustrated in FIG. 5, the initial screen, which indicates the absence of a linked call device (e.g., a QR pager or BLE tag), includes an entry button "+" for adding a new device. Additionally, a QR code scanning screen for registering a new device is provided, where recognition is performed automatically when the device is placed in the scanning area in the center of the screen. If recognition fails, a manual registration guide ("Can't scan?") and a button to proceed to the next step are provided. This configuration allows the vehicle owner to directly register, link, and manage a QR call device or a safe number device, and improves the maintenance efficiency of the call system through a user-friendly and intuitive GUI configuration.
[0124] Figure 6 is a diagram showing a vehicle information registration and manager interface according to an embodiment.
[0125] As illustrated in FIG. 6, a vehicle registration UI is shown in which a vehicle owner registers a QR parking number plate by entering the vehicle number, representative contact information, status message, etc. A device management screen is shown that displays information such as the representative number, status message, and vehicle number for the registered parking number plate, and provides functions such as vehicle management, member management, preview, and de-registration. Additionally, a member management interface is shown that provides functions such as a list of members linked to the vehicle call system, administrator accounts, issuance of invitation links, and checking application status. The above configuration is implemented so that the vehicle owner can systematically register and manage multiple users and vehicles, and easily perform connection settings for the call system, operational authority, and distributed user management through an intuitive UI.
[0126] Hereinafter, we will look at FIG. 7. The vehicle owner call method illustrated in FIG. 7 can be performed by a vehicle owner call terminal (100) including a processor (130).
[0127] Meanwhile, FIG. 7 is merely illustrative, and the concept of the present invention is not to be interpreted as being limited to that depicted in FIG. 7. For example, each step may be configured in a different order than that depicted in FIG. 7, at least one of the steps depicted in FIG. 7 may not be performed, or one or more steps not depicted in FIG. 7 may be additionally performed. Below, a vehicle owner calling method will be described in order. Since the operation (function) of the vehicle owner calling method according to the embodiment is essentially the same as the function of the vehicle owner calling system, descriptions that overlap with FIG. 1 to 6 will be omitted.
[0128] FIG. 7 is a diagram illustrating a vehicle owner call process according to an embodiment.
[0129] Referring to FIG. 7, in step S110, vehicle identification information is received within a voice call made by the caller to the ARS number attached to the vehicle. In step S120, the validity of the vehicle identification information is determined, and if it is invalid, the process proceeds to step S130 to provide an error notification. In step S140, the number of vehicles corresponding to the vehicle identification information is checked, and if multiple vehicles corresponding to the vehicle identification information exist, the process proceeds to step S150 to provide the caller with information on the multiple vehicles, and in step S160, a selection input is received. In step S170, the virtual phone number of the owner corresponding to the vehicle selected by the caller is connected to the caller's terminal. In step S180, the call connection information is recorded and managed on a server.
[0130] Meanwhile, the methods according to the various embodiments of the present invention described above can be implemented in the form of an application or software program that can be installed on an existing electronic device.
[0131] In addition, the whole or part of the method may be composed of multiple software function modules and implemented on an operating system (OS). Alternatively, each step may be composed of a single software function module, or each step may be combined to form a single software function module and implemented on an operating system. Therefore, even if all of the embodiments of the present disclosure are not implemented as a single software function module, if multiple software function modules implement each step of the present disclosure and multiple software function modules are implemented on a single operating system, it can be understood that the method of the present disclosure has been implemented.
[0132] In addition, the methods according to the various embodiments of the present invention described above can be implemented solely through software upgrades or hardware upgrades of existing electronic devices. Furthermore, the various embodiments of the present invention described above can also be performed through an embedded server equipped in an electronic device or an external server of the electronic device.
[0133] Meanwhile, according to one embodiment of the present invention, the various embodiments described above may be implemented as software comprising instructions stored on a computer-readable recording medium using software, hardware, or a combination thereof. In some cases, the embodiments described herein may be implemented as the processor itself. According to the software implementation, embodiments such as the procedures and functions described herein may be implemented as separate software modules. Each of the software modules may perform one or more functions and operations described herein.
[0134] Meanwhile, a computer or a similar device may include a device according to the disclosed embodiments, which is capable of calling instructions stored from a storage medium and operating according to the called instructions. When said instructions are executed by a processor, the processor may perform a function corresponding to said instructions directly or by using other components under the control of said processor. The instructions may include code generated or executed by a compiler or an interpreter.
[0135] A computer-readable recording medium may be provided in the form of a non-transitory computer-readable recording medium. Here, "non-transitory" simply means that the storage medium does not contain a signal and is tangible, without distinguishing whether data is stored semi-permanently or temporarily on the storage medium. In this context, a non-transitory computer-readable medium refers to a medium that stores data semi-permanently and is readable by a device, rather than a medium that stores data for a short moment, such as registers, caches, or memory. Specific examples of non-transitory computer-readable media may include CDs, DVDs, hard disks, Blu-ray discs, USBs, memory cards, and ROMs.
[0136] As described above, exemplary embodiments have been disclosed in the drawings and specification. Although specific terms have been used to describe the embodiments in this specification, they are used only for the purpose of explaining the technical concept of this disclosure and are not intended to limit the meaning or the scope of this disclosure as defined in the claims. Therefore, those skilled in the art will understand that various modifications and equivalent alternative embodiments are possible therefrom. Accordingly, the true technical scope of protection of this disclosure should be determined by the technical concept of the appended claims.
Claims
Claim 1 A vehicle calling system that performs a call connection with a vehicle owner based on input from a caller terminal comprises: a parking number plate providing number and QR code information for ARS connection; and an application installed on the caller terminal that recognizes the number or QR code from the parking number plate and connects to the vehicle owner; wherein the application comprises: an ARS receiving module that receives vehicle identification information within a voice call initiated by the caller to an ARS number attached to the vehicle; a validity verification module that determines the validity of the vehicle identification information and provides an error notification if it is invalid; a duplicate item selection module that, if multiple vehicles corresponding to the vehicle identification information exist, provides the multiple vehicle information to the caller and receives a selection input; a virtual number connection module that connects the virtual phone number of the owner corresponding to the vehicle selected by the caller to the caller terminal; a call history management module that records and manages call connection information on a server; and a response evaluation module that calculates a response reliability score based on the vehicle owner's call reception history, and if the score is below a preset threshold, temporarily restricts the call connection to the vehicle or provides the caller with a notification stating "This is a vehicle with restricted connection," and makes the score available for real-time verification on an administrator page. and a call status tracking module that detects call connection failure events occurring repeatedly to a vehicle owner; wherein the call status tracking module calculates a penalty score P for a single vehicle owner based on the following Equation 1, and based on the penalty score P, performs at least one management procedure among call restriction, system reliability reduction, and response-inducing feedback for the vehicle owner, and if the penalty score for a specific vehicle over a certain period exceeds a preset threshold, executes at least one control procedure among call function restriction, system reliability reduction, automatic feedback transmission, statistical recording, and administrator notification, [Equation 1] (Nfail is the number of calls determined to be rejected or unanswered within the observation period, Ntotal is the total number of call attempts, Lconsec is the maximum length of consecutive failure events (rejection / unanswered), α and β are weighting coefficients according to system settings) Vehicle owner call system. Claim 2 In claim 1, the ARS receiving module is a vehicle owner calling system that receives a portion of a vehicle number according to the input order of the caller, verifies the input value, provides a selection request or error guidance, and voice-guides a connection with the vehicle owner. Claim 3 In claim 1, the validation module validates the validity of the vehicle identification information by comparing it with a pre-registered vehicle number database, and outputs a voice guidance to induce the caller to re-enter the information if an unregistered number is entered, in a vehicle owner call system. Claim 4 In claim 1, the duplicate item selection module lists the entire number of each vehicle by item and provides voice guidance to the caller when there are multiple vehicles corresponding to the input vehicle identification information, and receives the caller's number selection input, a vehicle owner call system. Claim 5 In claim 1, the virtual number connection module performs a call connection between a caller and a vehicle owner through a virtual safe number of a predetermined format instead of an actual phone number, and a vehicle owner call system that temporarily deactivates the safe number after the connection is terminated. Claim 6 A vehicle owner call system according to claim 1, characterized in that the system includes a QR linkage mode in which vehicle identification information can be entered and selected without ARS calling on a web page accessed by a caller via a QR code attached to a vehicle, and subsequently a call connection to the same virtual number is performed. Claim 7 In claim 1, the call history management module stores a call record on a server including the time of the ARS call, input vehicle identification information, caller selection information, and connected virtual number information, and allows it to be viewed through an administrator page, thereby making it a vehicle owner call system. Claim 8 In claim 1, the virtual number connection module performs a waiting guidance, a retry request, or the transmission of a voice message to a caller according to a reception status including the vehicle owner's call in progress and reception rejection, and provides guidance on the vehicle owner's call status, a vehicle owner call system. Claim 9 The vehicle owner call system according to claim 1, comprising: a renewal management module in which the call function is valid for a predefined validity period from the vehicle registration date or the first call date, and when the validity period is exceeded, provides a call restriction notice message to the caller and sends a notice message regarding service extension or paid conversion to the vehicle owner. Claim 10 The vehicle owner call system according to claim 1, wherein the vehicle owner call system includes a rate policy control module that, when a rate plan for the use of a call function is selected by a vehicle owner, usage conditions such as the number of possible calls, connection time, and message transmission function are determined according to the selected rate plan, and the call function is restricted or expanded according to the conditions. Claim 11 A vehicle owner call system according to claim 6, wherein the QR code-based web page includes a third-party advertising area, and the vehicle owner call system includes a revenue linkage module configured to record advertising revenue information on a server and distribute a portion of the revenue to a vehicle owner account or a system administrator account when a caller clicks on an advertisement or is exposed for a certain period of time or longer. Claim 12 delete Claim 13 In claim 7, the above call history management module links the above call history data, including the time of call, vehicle number, response status, and location information of the caller, to an external server or affiliated organization, and allows it to be utilized for commercial data analysis or customer service improvement with the user's consent, a vehicle owner call system.
Citation Information
Patent Citations
Reliable parking service system and method thereof
KR101263199B1
Method for providing safety car parking service
KR101389506B1
Method and system for notifying of business using the safety telephone number
KR1020100085636A
Method and system for providing parking security number service
KR1020230055480A
Methods and systems for safe contact service provision
KR102616461B1