Server and vehicle communicating therewith

Abstract

According to the present disclosure, a server may include: a communication device configured to communicate with a vehicle; and a processor configured to determine usage pattern information of the vehicle based on first traffic information associated with the toll station, where the first traffic information is received from the vehicle at a first time. The server may also include a memory configured to store usage pattern information of the determined vehicle. The processor may be further configured to: determine whether use of the vehicle coincides with the stored use pattern information based on second traffic information received from the vehicle at a second time after the first time; and transmitting a request for confirming the use of the vehicle to the vehicle based on determining that the use of the vehicle does not coincide with the stored use pattern information.

Description

Technical Field

[0001] The present disclosure relates to a server for collecting tolls using an Electronic Toll Collection System (ETCS), and a vehicle communicating therewith. Background Art

[0002] Electronic Toll Collection Systems (ETCS), such as the HI-PASS device used on highways in Korea, automatically collect tolls from users through a standardized application interface using the Dedicated Short Range Communication (DSRC) protocol.

[0003] ETCS is a system capable of automatically transmitting and receiving toll information between a roadside device and a terminal of a vehicle (eg, an onboard device or an ETCS terminal) based on the DSRC protocol.

[0004] When a vehicle enters a toll booth, ETCS can identify the type of vehicle using a vehicle classification device, communicate with a vehicle terminal device using an antenna, and send fee information corresponding to the vehicle type to the vehicle terminal device based on the communication with the vehicle terminal device.

[0005] In addition to using a vehicle category classification device to identify the vehicle category and using an antenna to communicate with a vehicle terminal device, ETCS can also identify road information used by the vehicle based on communication with the vehicle terminal device, obtain fee information based on the identified road information and vehicle category, and send the obtained fee information to the vehicle terminal device.

[0006] In some implementations, the fee is paid using a postpaid card or prepaid card inserted into a slot in the vehicle terminal device, which causes inconveniences: a postpaid card or prepaid card must be obtained from a credit card company to automatically pay the fee, and the user himself must insert the prepaid card or postpaid card into the vehicle terminal device. In the case of a prepaid card, the user must recharge in advance. In addition, there may be a risk of losing the postpaid card or prepaid card inserted into the vehicle terminal device.

[0007] Thus, in some implementations, the vehicle terminal device may use an embedded integrated circuit (IC) chip to pay for the fee. Summary of the invention

[0008] One aspect of the present disclosure provides: a server that can determine whether usage information of a first terminal device deviates from pre-stored usage pattern information to identify whether the first terminal device is being used normally, and in response to abnormal use of the first terminal device, delete payment registration information stored in the first terminal device; and a vehicle that communicates with the server.

[0009] Another aspect of the present disclosure provides: a server, which can determine whether a vehicle user has changed when no confirmation information about whether the first terminal device is used normally is received, and delete the payment registration information stored in the first terminal device in response to the change of the vehicle user; and a vehicle communicating with the server.

[0010] Part of other embodiments of the present disclosure will be set forth in the following description, and part of the embodiments will be obvious from the description, or the embodiments may be learned by practice of the present disclosure.

[0011] According to one or more example embodiments of the present disclosure, a server may include: a communication device configured to communicate with a vehicle; and a processor configured to: determine usage pattern information of the vehicle based on first pass information associated with a toll booth. The first pass information may be received from the vehicle at a first time. The server may also include a memory configured to: store the determined usage pattern information of the vehicle. The processor may also be configured to: determine whether the use of the vehicle is consistent with the stored usage pattern information based on second pass information received from the vehicle at a second time after the first time, and send a request to the vehicle to confirm the use of the vehicle based on determining that the use of the vehicle is inconsistent with the stored usage pattern information.

[0012] The processor may be configured to determine the usage pattern information of the vehicle by: collecting first passage information associated with a toll booth within a predetermined time period; and determining the usage pattern information of the vehicle based on the first passage information collected within the predetermined time period.

[0013] The processor may be configured to determine whether the usage of the vehicle is consistent with the stored usage pattern information by comparing the stored usage pattern information with a portion of the second traffic information recorded after the vehicle received a last start command of the vehicle.

[0014] The processor may be configured to determine whether the use of the vehicle is consistent with the stored use pattern information by: obtaining use information of the vehicle based on the second passage information. The use information may include: identification information associated with the toll booth and passage time information associated with the toll booth; comparing the use information with the stored use pattern information of the vehicle to determine whether the use of the vehicle deviates from the stored use pattern information of the vehicle; and determining that the use of the vehicle is inconsistent with the stored use pattern information based on determining that the use of the vehicle deviates from the stored use pattern information of the vehicle.

[0015] The processor can also be configured to: based on confirmation of use of the vehicle received from the vehicle, determine whether the received confirmation indicates that a first user associated with the second pass information is different from a second user associated with the stored vehicle usage pattern information; and based on determining that the received confirmation indicates that the first user is different from the second user, send a request to the vehicle to delete the payment registration information stored in the vehicle.

[0016] The processor can also be configured to: obtain first identification information associated with a user of the vehicle based on not receiving confirmation of use of the vehicle from the vehicle; and send a request to the vehicle to delete payment registration information stored in the vehicle based on the first identification information being different from second identification information associated with a second user associated with the first pass information.

[0017] The server may be a first server. The communication device may be configured to communicate with a second server. The processor may also be configured to: based on receiving a request from the second server to delete the payment registration information stored in the vehicle, send the received request to the vehicle.

[0018] The stored usage pattern information of the vehicle may include usage pattern information of a terminal device provided in the vehicle. The terminal device may include an integrated circuit (IC) chip for performing toll payment at a toll booth.

[0019] According to one or more example embodiments of the present disclosure, a vehicle may include a first terminal device including an integrated circuit (IC) chip. The IC chip may be configured to store payment registration information for toll payment. The vehicle may also include: a communication device configured to communicate with a server; and a processor configured to: based on paying a fee at a toll station via the first terminal device, send to the server passage information associated with the toll station; and based on receiving a request for deleting the payment registration information from the server, delete the payment registration information stored in the IC chip.

[0020] The vehicle may further include: a second terminal device including a user interface. The processor may also be configured to: based on receiving an indication of abnormal use of the first terminal device from the server, cause the second terminal device to display a message associated with the received indication; and based on receiving user information from the second terminal device, send user information to the server.

[0021] The second terminal device may be configured to: identify a user; perform user authentication on the identified user; and send one of a user authentication success indication or a user authentication failure indication to the first terminal device based on a result of the user authentication. The first terminal device may be configured to: activate the IC chip based on receiving the user authentication success indication.

[0022] The second terminal device may be configured to identify the user by: receiving identification information of the user; and identifying the user based on the received identification information.

[0023] The second terminal device may be configured to perform user authentication by: receiving authentication information of the identified user; and comparing the received authentication information with pre-stored user authentication information associated with the user.

[0024] The vehicle may further include an authentication device configured to perform user authentication. The processor may further be configured to send to the first terminal device one of the following: a user authentication success indication received from the authentication device, or a user authentication failure indication received from the authentication device. The first terminal device may be configured to activate the IC chip based on receiving the user authentication success indication.

[0025] The vehicle may further include: a second terminal device including a user interface. The second terminal device may be configured to: store an application for the CarPay service; output an image corresponding to executing the stored application; and send payment registration information received through the application to the first terminal device. The first terminal device may also be configured to: issue a card through an IC chip based on the payment registration information.

[0026] The communication device may also be configured to communicate with the mobile device. The processor may also be configured to: receive payment registration information registered to an application executable on the mobile device; and send the received payment registration information to the first terminal device. The first terminal device may also be configured to: issue a card through the IC chip based on the payment registration information.

[0027] The server may be a first server. The communication device may be configured to communicate with a second server. The processor may also be configured to: based on receiving a request for deleting the payment registration information from the second server, send the received request to the first terminal device. The first terminal device may be configured to: based on receiving the sent request, delete the payment registration information stored in the IC chip.

[0028] The processor may be further configured to send a request to the first terminal device to delete the payment registration information based on receiving a user change indication associated with the vehicle from the server. The first terminal device may be configured to delete the payment registration information stored in the IC chip based on receiving the request.

[0029] The processor can also be configured to: obtain and store usage pattern information associated with the first terminal device based on historical traffic information associated with the toll station and collected within a predetermined time period; and determine whether the use of the first terminal device is consistent with the stored usage pattern information based on the portion of the traffic information recorded after the vehicle received the last start command.

[0030] The vehicle may further include a second terminal device including a user interface. The processor may be further configured to, in response to determining that usage of the first terminal device is inconsistent with the stored usage pattern information, cause the second terminal device to output a message indicating a request for confirming usage of the first terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] These and / or other embodiments of the present disclosure will become apparent and more easily understood by describing the following embodiments in conjunction with the accompanying drawings:

[0032] Figure 1 is a diagram showing a configuration of an electronic toll collection system (ETCS) including a vehicle according to an embodiment;

[0033] Figure 2 is a diagram showing an example of communication of a vehicle according to an embodiment;

[0034] Figure 3 is a control block diagram showing a vehicle according to an embodiment;

[0035] Figure 4 is a control block diagram showing a first terminal device provided in a vehicle according to an embodiment;

[0036] Figure 5 is a control block diagram showing a second terminal device provided in a vehicle according to an embodiment;

[0037] Figure 6 is a control block diagram showing a first server according to an embodiment;

[0038] Figure 7 is a diagram showing an example of a usage pattern of a first terminal device obtained by a first server according to an embodiment;

[0039] Fig. 8A and Figure 8B is a flowchart illustrating a control operation between a first server, a second server, and a vehicle according to an embodiment; and

[0040] Fig. 9 is a diagram illustrating an exemplary display of a second terminal device of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0041] The same figure numbers throughout the specification represent the same elements. In addition, this specification does not describe all the elements according to the embodiments of the present disclosure, and omits the well-known descriptions or overlapping parts in the art to which the present disclosure relates. Terms such as "~component", "~member", "~module", "~block", etc. may refer to at least one process processed by at least one hardware or software. According to the embodiment, multiple "~components", "~members", "~modules", "~blocks" may be embodied as a single element, or multiple "~components", "~members", "~modules", "~blocks" may include multiple elements.

[0042] It should be understood that when an element is mentioned as being “connected” to another element, it may be directly or indirectly connected to the other element, wherein the indirect connection includes “connection” via a wireless communication network.

[0043] It should be understood that the term “comprising” when used in this specification specifies the presence of features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of at least one other feature, integer, step, operation, element, component and / or groups thereof.

[0044] It should be understood that when it is described in this specification that a member is “on” another member, the member may not only be in contact with the other member but also another member may exist between the two members.

[0045] It will be understood that, although the terms first, second, etc. may be used to describe various elements, these elements should not be limited by these terms.

[0046] It will be understood that the singular forms also include the plural forms unless the context clearly dictates otherwise.

[0047] The reference numerals used for the method steps are only for convenience of explanation and are not intended to limit the order of the steps. Therefore, unless the context clearly requires otherwise, the described order may be performed in other ways.

[0048] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0049] Figure 1 is a configuration diagram of an electronic toll collection system (ETCS) including a vehicle according to an embodiment.

[0050] refer to Figure 1 , the ETCS according to the embodiment may include a roadside equipment (RSE, S2) provided at one side of a toll station S1 and a vehicle 1 passing through the toll station S1.

[0051] ETCS is a system capable of automatically transmitting and receiving toll information between the RSE S2 and the vehicle 1 based on a dedicated short-range communication technology.

[0052] The RSE S2 may include a transmitting and receiving antenna for communicating with the vehicle 1. The RSE S2 may automatically request fee payment from the vehicle 1 through communication with the vehicle 1.

[0053] The RSE S2 may identify the category of the vehicle 1 passing through the toll booth S1 through communication with the vehicle 1 , and may request the vehicle to pay a fee corresponding to the identified vehicle category.

[0054] Vehicle class refers to the size of the vehicle, such as light vehicle, medium vehicle, and large vehicle.

[0055] The RSE S2 may communicate with a server (not shown) of a toll road manager.

[0056] The RSE S2 may transmit identification information of the toll station S1 (toll station identification information), passing time information, identification information of the vehicle, and fee information to a server (not shown).

[0057] The vehicle 1 may radiate electromagnetic waves to the outside through an antenna (not shown).

[0058] The vehicle 1 may receive electromagnetic waves transmitted from at least one of the RSE S2 or a server (not shown) through an antenna (not shown), and may convert the received electromagnetic waves into electric signals.

[0059] The vehicle 1 may demodulate the electromagnetic wave received through an antenna (not shown) to convert into an electric signal, may obtain a control signal corresponding to the converted electric signal, and use the obtained control signal to control the vehicle 1 .

[0060] The vehicle 1 may receive the passing information from the RSE S2. The passing information may include toll booth identification information, passing time information and fee information.

[0061] The vehicle 1 can automatically pay the fee based on the received passage information.

[0062] Figure 2 is a diagram showing an example of communication of a vehicle according to an embodiment.

[0063] The vehicle 1 may communicate with the mobile device 2 , the first server 3 , and the second server 4 .

[0064] The vehicle 1 can receive and store the user's identification information. The vehicle 1 can receive information from the mobile device 2 by linking to the mobile device 2, process the received information from the mobile device 2, and display the received or processed information from the mobile device 2 (e.g., display a message associated with an abnormal use indication). The vehicle 1 can send information stored in the vehicle and the vehicle's operating information to the mobile device 2.

[0065] The vehicle 1 may process the information received from the first server 3 , and may display the information received from the first server 3 .

[0066] The vehicle 1 may transmit information stored in the vehicle 1 and operation information of the vehicle 1 to the first server 3 .

[0067] The vehicle 1 may process the information received from the second server 4 , and may display the information received from the second server 4 .

[0068] The vehicle 1 may transmit information stored in the vehicle 1 and operation information of the vehicle 1 to the second server 4 .

[0069] The mobile device 2 may communicate with the vehicle 1 through at least one of a Bluetooth Low Energy (BLE) module, an Ultra Wideband (UWB) module, or a Near Field Communication (NFC) module.

[0070] The mobile device 2 can remotely control the vehicle 1 , and can perform payment for services used by the user or goods purchased by the user.

[0071] A first application for the CarPay service and a second application for the remote control service of the vehicle 1 may be set on the mobile device 2 .

[0072] The second application may be an application for a digital key service.

[0073] The first application and the second application can also be implemented as one application. In this case, the second application can also perform the CarPay service.

[0074] The user's identification information, the mobile device's identification information, the vehicle's identification information, and payment registration information may be registered and stored through the first application and the second application set on the mobile device 2 .

[0075] The identification information of the mobile device 2 is unique identification information of the mobile device 2 , and may include at least one of a phone number, a Wi-Fi MAC address, a serial number, or an International Mobile Equipment Identity (IMEI) of the mobile device 2 .

[0076] The identification information of the mobile device 2 may include Bluetooth identification information (BTID).

[0077] The user's identification information (user identification information) may include information about at least one of the following: the user's name, the user's date of birth, the user's social security number, the user's gender, the user's telephone number, the user's home address, the user's work address, the user's driver's license information, or the user's email address.

[0078] The identification information of vehicle 1 (vehicle identification information) may include information about at least one of the following: vehicle category, vehicle model, serial number, vehicle identification number, vehicle license plate, and power generation method (e.g., hybrid, electric, internal combustion engine, hydrogen, etc.).

[0079] The vehicle category can be classified based on at least one of engine displacement, vehicle length, vehicle width or vehicle height. In this case, the vehicle can be divided into light vehicles, small vehicles, medium vehicles and large vehicles.

[0080] Payment registration information may include card information and account information.

[0081] The card information may include information on at least one of: a card company, a card number, an expiration date, a password, or a security code (eg, a card verification code (CVC)).

[0082] Account information may include information about bank type, account number, account password, and account holder name.

[0083] The payment registration information may also include information on the following items: daily payment limit, maximum payment amount per transaction, and maximum number of transactions per day.

[0084] The mobile device 2 can perform membership registration (subscription) for the digital key service through the second application. In this case, the mobile device 2 can receive and store the digital key (or electronic key) of the vehicle from the server (not shown) of the vehicle manufacturer. Here, the digital key may include identification information and authentication information of the mobile device 2 and vehicle control right information.

[0085] The mobile device 2 may transmit the digital key stored in response to completion of the subscription to the digital key service to the vehicle 1 .

[0086] The mobile device 2 may receive a user input for controlling the vehicle through the second application, and may display operation information of the vehicle.

[0087] The mobile device 2 may attempt to establish communication with the vehicle 1 in response to the command to execute the digital key service. In this case, the mobile device 2 may send the digital key to the vehicle 1.

[0088] The digital key may include identification information and authentication information of the mobile device 2 and vehicle control right information, and may also include vehicle identification information.

[0089] The mobile device 2 may perform member registration for the CarPay service through the first application.

[0090] The mobile device 2 may receive payment registration information of a vehicle user who uses the vehicle through the first application, and register and store the received payment registration information of the user.

[0091] The mobile device 2 may execute the first application in response to completing the registration of the payment registration information. In this case, the mobile device 2 may link the digital key service and the CarPay service.

[0092] The mobile device 2 may be implemented as a computer or a portable terminal that can be connected to the vehicle 1 via a network.

[0093] The computer may include, for example, a notebook computer equipped with a web browser, a desktop computer, a tablet personal computer (PC), a tablet computer, etc. The portable terminal may include, for example, various handheld-based wireless communication devices that ensure portability and mobility, such as a personal communication system (PCS), a global system for mobile communications (GSM), a personal digital cellular (PDC), a personal handyphone system (PHS), a personal digital assistant (PDA), an international mobile communication (IMT)-2000, a code division multiple access (CDMA)-2000, a wideband CDMA (WCDMA), a wireless broadband Internet (WiBro) terminal, and a smart phone, as well as a wearable device such as a watch, a ring, a bracelet, an anklet, a necklace, glasses, contact lenses, or a head mounted device (HMD).

[0094] The first server 3 may be a server of a company that issues and manages a credit card (ie, HI-PASS card) used for fee payment.

[0095] The first server 3 may be a server of a company that issues and manages credit cards, or a server of an organization that collects and manages fees.

[0096] The first server 3 can store the user's payment registration information.

[0097] In response to receiving the traffic information from the vehicle, the first server 3 may store the received traffic information, and may obtain the usage pattern (e.g., toll usage pattern, toll booth usage pattern, etc.) information of the user vehicle based on the traffic information stored in the predetermined time period. Here, the predetermined time period may be a preset time period.

[0098] The first server 3 may store the obtained usage pattern information of the user's vehicle.

[0099] The first server 3 may determine whether the vehicle 1 is used normally (eg, within a predetermined range, such as consistent with a historical usage pattern) or abnormally (eg, outside a predetermined range, such as inconsistent with a historical usage pattern) based on the usage pattern information.

[0100] In response to abnormal use of the vehicle 1 , the first server 3 may request confirmation of use of the vehicle 1 from the vehicle 1 or the mobile device 2 .

[0101] In response to abnormal use of the vehicle 1 , the first server 3 may request the vehicle 1 to delete the payment registration information.

[0102] In response to the use confirmation of the vehicle 1 , the first server 3 may request the vehicle 1 to delete the payment registration information.

[0103] In response to abnormal use of the vehicle 1 , the first server 3 may also determine from a server (not shown) of the toll road manager whether the user of the vehicle has changed.

[0104] The server of the toll road manager may store the identification information of the vehicle user and the identification information of the vehicle.

[0105] In response to a change in the vehicle user, the first server 3 may request the vehicle 1 to delete the payment registration information.

[0106] In response to the change of the vehicle user, the first server 3 may request the mobile device 2 to delete the payment registration information.

[0107] In response to the request to delete the payment registration information of the second server, the first server 3 may delete the stored payment registration information of the vehicle, and may request the vehicle 1 to delete the payment registration information.

[0108] The second server 4 may be a server of a company that provides and manages the first application.

[0109] The second server 4 may be a server of a company that provides and manages the second application.

[0110] The second server 4 may be a server provided at a service center, a vehicle manufacturer, a repair center, etc. that manages the vehicle 1. In addition, the second server 4 may be a server of an application (ie, app) that provides services associated with the vehicle 1, and may be a telematics server or a platform server.

[0111] The second server 4 may store identification information of a user who has registered as a member through the first application, identification information of a vehicle, identification information of a mobile device, and payment registration information.

[0112] In response to receiving a command to delete the payment registration information through the first application, the second server 4 may send a command to delete the payment registration information to the first server 3 .

[0113] The second server 4 may send at least one of the vehicle identification information or the user identification information to the first server 3 to allow the first server 3 to delete the payment registration information.

[0114] The second server 4 may store identification information of a user registered as a member through the second application, identification information of a vehicle, and identification information of a mobile device.

[0115] Figure 3 is a diagram showing a reference according to an embodiment Figure 4 and Figure 5 A control block diagram of a vehicle is described.

[0116] Figure 4 is a control block diagram showing a first terminal device provided in a vehicle according to an embodiment, and Figure 5 is a control block diagram illustrating a second terminal device provided in a vehicle according to an embodiment.

[0117] The vehicle 1 may include a first terminal device 110 , a second terminal device 120 , an authentication device 130 , a first communication device 140 , a first processor 150 , and a first memory 151 .

[0118] In order to distinguish the components of the vehicle 1 from the components of the first server 3 , the components of the vehicle 1 are referred to as “first” components, and the components of the first server 3 are referred to as “second” components.

[0119] The first terminal device 110 may be installed on or embedded in the dashboard.

[0120] The first terminal device 110 may be installed on a rearview mirror or a front windshield.

[0121] In response to receiving the payment registration information from the first server 3 or the first processor 150 , the first terminal device 110 may store the received payment registration information.

[0122] The first terminal device 110 may match and store the payment registration information with the user identification information.

[0123] When entering the toll station S1 , the first terminal device 110 may communicate with the RSE S2 .

[0124] The first terminal device 110 may receive the passage information from the RSE S2 and pay the fee in response to receiving the passage information.

[0125] When paying the fee, the first terminal device 110 may send the passage information to the first server 3. The passage information may include fee information, toll booth identification information, passage date information, passage day information, and passage time information, and may also include toll booth location information.

[0126] When entering a toll booth, the first terminal device 110 may receive toll booth identification information from at least one of the second terminal device 120 or the first communication device.

[0127] When sending the pass information to the first server 3 , the first terminal device 110 may send the user identification information and the payment registration information to the first server 3 or the second server 4 .

[0128] The first terminal device 110 may store the pass information. The first terminal device 110 may match the pass information with the user identification information and store them.

[0129] like Figure 4 As shown, the first terminal device 110 may include at least one integrated circuit (IC) chip 111 , 112 , and 113 , a socket 114 , a first communication unit 115 , a first controller 116 , and a storage 117 .

[0130] The IC chip may be an integrated circuit chip made of semiconductors and may not be affected by magnetic materials. Each IC chip may be in the form of an embedded IC card in which card information is stored in the IC chip, rather than a physical card inserted into a slot.

[0131] The card information may include information about at least one of a card company, a card number, an expiration date, a password, or a security code (eg, CVC).

[0132] The IC chip may be an embedded card in which the account information is stored.

[0133] Account information may include information about bank type, account number, account password, and account holder name.

[0134] Here, the card information and account information may be payment registration information.

[0135] The payment registration information may also include information about the daily payment limit, the maximum payment amount per transaction, and the maximum number of transactions per day.

[0136] The IC chip can encrypt and store information. The IC chip can include a security processor.

[0137] The IC chip may store a certificate corresponding to a secret key of the public key infrastructure.

[0138] The IC chip may include a power supply terminal, a data transmission / reception terminal, and a clock transmission / reception terminal.

[0139] The following description is made on the assumption that the number of IC chips is three.

[0140] Each of the IC chips 111 , 112 , and 113 may include an issuer security domain (ISD) originally permanently installed by a vehicle manufacturer and a supplementary security domain (SSD) installed by a card company providing payment services.

[0141] A security domain (SD) structure including an ISD and an SSD may comply with a global platform (GP) card specification.

[0142] Deleting and changing the information of each IC chip can be performed only by the ISD.

[0143] Each of the IC chips 111 , 112 , and 113 can perform payment based on payment registration information registered through the first server 3 or the second server 4 .

[0144] When the vehicle passes through the toll booth S1 , each of the IC chips 111 , 112 , and 113 can perform payment based on the fee information received from the RSE S2 .

[0145] The physical card is inserted into the slot 114. The slot 114 can read information about the physical card and send the read information to the first controller 116.

[0146] The first communication unit 115 may transmit and receive information between constituent components of the first terminal device 110 .

[0147] The first communication part 115 may be connected to a vehicle network (NT) to perform communication.

[0148] The first communication unit 115 may transmit information to the first processor 150 and receive information from the first processor 150 .

[0149] The first communication unit 115 may communicate with an external electronic device (eg, the RSE S2 , the first server 3 , the second server 4 , etc.) through wireless communication.

[0150] The first controller 116 can communicate with the first communication device 140 to identify the vehicle 1, identify the user, and determine whether the identified user is the same as the user of the identified vehicle. When the user of the identified vehicle is the same as the identified user and user authentication success information is received from at least one of the second terminal device 120 or the authentication device 130, the first controller 116 can control the IC chip corresponding to the identified user to be activated.

[0151] The first controller 116 may confirm the identification information of the user logged in through the second terminal device 120, and confirm the payment registration information corresponding to the confirmed identification information. The first controller 116 may control the activation of the IC chip based on the confirmed payment registration information and the payment registration information stored in the first storage 117. That is, the first controller 116 may control the IC chip corresponding to the user identification information to be activated.

[0152] When storing the payment registration information in at least one IC chip, the first controller 116 may store the payment registration information by encrypting a unique number assigned to the vehicle instead of the vehicle license plate in order to ensure security against theft, forgery, and tampering.

[0153] In response to receiving the first card issuance request, the security key, and the payment registration information through the first processor 150, the first controller 116 can store the payment registration information in the first IC chip 111 among the multiple IC chips by using the received security key. Specifically, by using the security key, the SSD and applet corresponding to the payment registration information are obtained in the first IC chip 111, and the first controller 116 can issue the first IC chip 111 as a newly issued first card (e.g., a first virtual card). Here, the first card can be a card under the name of the first user.

[0154] Here, the acquisition of the SSD and the applet may be performed by the ISD.

[0155] The security key corresponds to a key with authority to issue new cards and can be issued by a Personal Security Application Module (PerSAM).

[0156] PerSAM is a card type security device that is required to be used only according to a specified procedure in order to securely transfer keys for issuing cards (electronic money). PerSAM can be a module with key information required for issuance and can be provided by the toll road management party that supervises ETCS.

[0157] When the first IC chip 111 is issued as a first card, the first controller 116 may obtain initialization interdepartmental electronic wallet (IEP) data of the first card. That is, the first controller 116 may obtain and store initialization IEP data to be transmitted when entering the toll station S1 in advance.

[0158] The initialized IEP data of the first card may include the transaction serial number of the first card, a random number obtained from the first card, an identifier (ID) of the issuer of the first card, the ID of the first card, the balance of the first card, the ID of the toll road manager, the ID of the card service, and a signature value obtained by the first card.

[0159] The first controller 116 may obtain the session key by encrypting the transaction serial number of the first card, the random number obtained from the first card, and the key stored in the first card.

[0160] The first controller 116 may obtain the signature value by encrypting the ID of the issuer of the first card, the ID of the first card, the balance of the first card, and the session key.

[0161] When the vehicle 1 enters the toll station S1 , the first controller 116 may identify the entrance of the toll station based on the identification information received from the RSE S2 , and identify the identification information of the toll station S1 .

[0162] When the entrance of the toll booth is identified, the first controller 116 may control the first communication part 115 to transmit the initialization IEP data of the first card to the RSE S2.

[0163] In response to the identified and authenticated user being the first user, the first controller 116 may select the first card as an example, and may perform charging communication for fee payment with the selected first card, thereby allowing payment of the fee.

[0164] In response to receiving the card deletion request and the authority key through the first processor 150 , the first controller 116 may delete the payment registration information stored in the first IC chip 111 using the authority key.

[0165] When the payment registration information registered in any one IC chip is deleted, the first controller 116 may delete the SSD and the applet.

[0166] The authority key corresponds to a key having authority to delete the card and may be issued by PerSAM. In addition, the card deletion request may include an SSD deletion command and an applet deletion command.

[0167] In response to receiving the second card issuance request, the security key and the payment registration information through the first processor 150, the first controller 116 can store the payment registration information in the second IC chip 112 by using the received security key, and the second IC chip 112 is an unissued IC chip among the multiple IC chips. Specifically, by using the security key to obtain the SSD and applet corresponding to the payment registration information in the second IC chip 112, the first controller 116 can issue the second IC chip 112 as a newly issued second card. Here, the second card can be a card under the second user name.

[0168] After completing the fee payment, the first controller 116 may send the pass information to the first processor 150 , the first server 3 or the second server 4 .

[0169] The first controller 116 may include at least one memory storing a program for performing the above-mentioned operations and the following operations, and at least one processor for implementing the stored program. When multiple memories and processors are provided, the multiple memories and processors may be integrated into one chip, or provided in physically separate locations.

[0170] The first storage 117 may store a program for performing the above-described operations of the first controller 116. The first controller 116 may execute the program stored in the first storage 117.

[0171] The first storage 117 can be implemented by at least one of the following, but is not limited to: a volatile memory, such as a random access memory (RAM); a non-volatile memory, such as a cache, a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc.; or a recording medium, such as a hard disk drive (HDD) or a compact disk read-only memory (CD-ROM).

[0172] The second terminal device 120 may be installed on or embedded in the dashboard.

[0173] The second terminal device 120 may be a device for a user interface, that is, the second terminal device 120 may receive a user input and output information corresponding to the user input.

[0174] The second terminal device 120 may output information on various functions performed in the vehicle 1 and information on various functions for user convenience.

[0175] The second terminal device 120 may be a device that executes an audio, video, and navigation mode. The second terminal device 120 may be an audio, video, navigation (AVN) device.

[0176] The second terminal device 120 may output navigation information in response to the navigation mode, output audio information in response to the audio mode, or output video information in response to the video mode.

[0177] The second terminal device 120 may be linked to the mobile device 2 , and may receive and output information about the mobile device 2 .

[0178] For example, the second terminal device 120 may display user schedule information stored in the mobile device 2 , output audio information stored in the mobile device 2 , or receive destination information stored in the mobile device 2 .

[0179] The second terminal device 120 may include an application for linking to the mobile device 2 .

[0180] The second terminal device 120 may output an image for linking to the mobile device 2 .

[0181] The second terminal device 120 may perform user authentication by linking to the mobile device 2 .

[0182] The second terminal device 120 may perform a remote service for user convenience and may perform a CarPay service.

[0183] The second terminal device 120 may include a first application for the CarPay service and a second application for the remote control service.

[0184] The second terminal device 120 may perform user authentication.

[0185] The second terminal device 120 may send user identification information, user authentication success information, or user authentication failure information to at least one of the first terminal device 110 or the first processor 150 .

[0186] The second terminal device 120 may output an image for the CarPay service and an image for guiding user authentication.

[0187] The second terminal device 120 may send at least one of navigation information, vehicle current location information, or toll booth identification information to the first terminal device 110 .

[0188] The second terminal device 120 may transmit the user input to at least one of the first terminal device 110 or the first processor 150 .

[0189] like Figure 5 As shown, the second terminal device 120 may include an input unit 121 , a display 122 , a speaker 123 , a second communication unit 124 , a second controller 125 , and a second storage 126 .

[0190] The input unit 121 may receive user input.

[0191] The user input may include navigation mode selection information, destination information, route selection information, and CarPay service selection information, and may also include a user authentication command.

[0192] The user input may include user identification information.

[0193] The user input may include a command to link to the mobile device 2 .

[0194] The input part 121 may receive a user registration command for registering a user of the vehicle, and may receive a user deletion command for deleting some registered users.

[0195] The input part 121 may receive a user registration command for the CarPay service and a user deletion command for deleting some registered users.

[0196] The input unit 121 may also receive user identification information, card information, account information, and identification information of at least one mobile device as subscription information for user registration of the CarPay service.

[0197] User identification information may include information about at least one of: the user's name, the user's date of birth, the user's social security number, the user's gender, the user's telephone number, the user's home address, the user's work address, the user's driver's license information, or the user's email address.

[0198] The card information may include information about at least one of a card company, a card number, an expiration date, a password, and a security code (eg, CVC).

[0199] The identification information of the mobile device is unique identification information of the mobile device, and may include at least one of a phone number, a Wi-Fi MAC address, a serial number, or an IMEI of the mobile device.

[0200] The identification information of the mobile device 2 may be Bluetooth identification information (BTID).

[0201] The input portion 121 may be implemented as at least one of a physical button, a key, or a switch.

[0202] The input unit 121 may include hardware devices, such as various buttons or switches, pedals, keyboards, mice, trackballs, various control rods, handles, joysticks, etc.

[0203] The input unit 121 may further include a graphical user interface (GUI), such as a touch panel, that is, a software device. The touch panel may be implemented as a touch screen panel (TSP) and form an interlayer structure with the display panel of the display 122 .

[0204] The input part 121 may receive identification information of a mobile device requesting sharing of the CarPay service, and may receive a command for approving or canceling the sharing.

[0205] In addition, the input unit 121 may receive a command for starting to register the biometric information of the user, a command for ending to register the biometric information, and a command for deleting the biometric information.

[0206] The display 122 may display information about a function being executed by the vehicle 1 or the second end device 120 .

[0207] For example, the display 122 may display navigation information, information related to a phone call, information on contents outputted through the mobile device 2, information related to music playing, or external broadcast information.

[0208] The display 122 may display a subscription image for user registration of the CarPay service.

[0209] The display 122 may display an image of the CarPay service in response to execution of the CarPay service, and may also display payment completion information and payment failure information as images.

[0210] The display 122 may display identification information of the mobile device requesting to share the CarPay service, and may display consent information about the CarPay service of completing consent or rejecting consent.

[0211] When passing through a toll booth, the display 122 may display the passing information. The passing information may include toll booth identification information, fee information, passing date information, passing time information, and may also include toll booth location information.

[0212] The display 122 may display user identification information, and may also display user authentication success information or user authentication failure information.

[0213] Furthermore, the display 122 may display an authentication request button image for requesting user authentication, and an authentication confirmation button image for notifying the user to confirm authentication.

[0214] The display 122 may display a button image for linking to the mobile device 2 and a button image for cancelling the link with the mobile device 2 .

[0215] The display 122 may display identification information of the mobile device 2 .

[0216] When the remote service function is executed, the display 122 may display remote service information.

[0217] The display 122 may also display communication status information with the mobile device 2. That is, the display 122 may display information on whether communication with the mobile device 2 can be performed.

[0218] The display 122 may be provided as a cathode ray tube (CRT), a digital light processing (DLP) panel, a plasma display panel (PDP), a liquid crystal display (LCD) panel, an electroluminescent (EL) panel, an electrophoretic display (EPD) panel, an electrochromic display (ECD) panel, a light emitting diode (LED) panel, an organic light emitting diode (OLED) panel, etc., but is not limited thereto.

[0219] The second terminal device 120 may include only the display 122. In this case, the input portion may be an input device provided on a head unit, a center box of an instrument, a steering wheel, or the like.

[0220] The speaker 123 may output a sound corresponding to an output of the vehicle or the second terminal device 120 .

[0221] The speaker 123 may output guidance information about entering a toll booth, and may output passage information as sound or voice.

[0222] The speaker 123 may output the navigation information as sound or voice.

[0223] The speaker 123 may output user authentication success information or user authentication failure information as voice.

[0224] At least one speaker 123 may be provided. The speaker 123 may be disposed within the vehicle.

[0225] The second communication unit 124 may transmit and receive information between components of the second terminal device 120 .

[0226] The second communication part 124 may be connected to the vehicle network (NT) to perform communication.

[0227] The second communication part 124 may transmit and receive information to and from the first processor 150 .

[0228] The second communication unit 124 may transmit and receive information to and from the first terminal device 120 .

[0229] The second communication unit 124 may communicate with an external electronic device (eg, RSE S2, etc.) through wireless communication.

[0230] The second communication unit 124 may include a global positioning system (GPS) receiver for identifying current location information of the vehicle.

[0231] The second controller 125 may control execution of the navigation mode in response to selection information of the navigation mode.

[0232] In response to receiving destination information through the input unit 121, the second controller 125 can identify the current position information of the vehicle, obtain a route from the current position to the destination based on the identified current position information and the destination information of the vehicle, and control the display 122 to display route information about the obtained route.

[0233] When multiple routes are obtained, the second controller 125 can confirm the route information corresponding to the route selection information selected through the input unit 121, obtain navigation information based on the confirmed route information, map information and current location information, and control the display 122 and the speaker 123 to output the obtained navigation information.

[0234] The second controller 125 may request input of login information in response to receiving an ON command (eg, engine ignition start, motor start, vehicle start, etc.) In this case, the second controller 125 may control the display 122 to display a window for login input.

[0235] The second controller 125 may perform user authentication based on login information input to the login input window.

[0236] The second controller 125 may request input of user identification information in response to receiving the start boot command, and may request user authentication in response to receiving the user identification information through the input portion 121 .

[0237] The second controller 125 may perform user authentication based on the user identification information received in the input portion 121 and the user authentication information received in the input portion 121. For example, the user authentication information may include a password or an authentication pattern.

[0238] In response to receiving a password through the input unit 121, the second controller 125 may determine whether the received password is the same as a pre-stored password. Based on the determination that the received password is the same as the pre-stored password, the second controller 125 may send user authentication success information to the first terminal device 110, and based on the determination that the received password is different from the pre-stored password, the second controller 125 may send user authentication failure information to the first terminal device 110.

[0239] In response to receiving the authentication pattern information through the input unit 121, the second controller 125 may determine whether the received authentication pattern information is the same as the pre-stored authentication pattern information. Based on the determination that the received authentication pattern information is the same as the pre-stored authentication pattern information, the second controller 125 may send user authentication success information to the first terminal device 110, and based on the determination that the received authentication pattern information is different from the pre-stored authentication pattern information, the second controller 125 may send user authentication failure information to the first terminal device 110.

[0240] The second controller 125 may control at least one of the display 122 or the speaker 123 to output user authentication success information or user authentication failure information.

[0241] In response to receiving the start boot command, the second controller 125 may obtain biometric information of the user (user biometric information), and may automatically perform user authentication based on the obtained user biometric information.

[0242] The second controller 125 may also receive user authentication success information and user authentication failure information from the authentication device 130 .

[0243] Based on the success of the user authentication, the second controller 125 may control the activation of the first terminal device 110 , and based on the failure of the user authentication, the second controller 125 may control the deactivation of the first terminal device 110 .

[0244] In addition, when entering a toll booth, the second controller 125 may transmit identification information of the toll booth to the first terminal device 110 .

[0245] In response to receiving the information confirmation command of the first terminal device through the input unit 121, the second controller 125 can control the communication with the first terminal device and control the display 122 to display the identification information of the first terminal device obtained by communicating with the first terminal device. The second controller 125 can also control the display 122 to display the user identification information of each IC chip registered in the first terminal device, and control the display 122 to display the payment history information of the successfully authenticated user.

[0246] The payment history information may be CarPay information. That is, in response to receiving a command for requesting confirmation of CarPay information through the input unit 121, the second controller 125 may receive the payment history information from the first terminal device and control the display 122 to display the received payment history information as CarPay information.

[0247] The second controller 125 may control the display 122 to display payment history information of the successfully authenticated user.

[0248] The second controller 125 may control the display 122 to display the usage pattern information of the vehicle of the successfully authenticated user. The usage pattern information of the vehicle may correspond to the usage pattern information of the first terminal device and may correspond to the usage pattern information of the IC chip corresponding to the user identification information.

[0249] The second controller 125 may execute a program stored in the second storage 126 .

[0250] The second controller 125 may execute a program corresponding to the application of the CarPay service and control at least one of the display or the speaker to output an image corresponding to the executed program. While executing the program, the second controller 125 may send payment registration information received through the first application to the first terminal device.

[0251] The second storage 126 may store a program for executing the above-described operations of the second controller.

[0252] The second storage 126 may store user identification information and user authentication information.

[0253] In the case where there are multiple vehicle users, the second storage 126 may store user identification information of each user and user authentication information of each user.

[0254] The second storage 126 may store identification information of the mobile device for linking to the CarPay service.

[0255] The second storage 126 may store user biometric information for user authentication.

[0256] User biometric information may include the user's facial information, voice information, fingerprint information, vein information, iris information, etc.

[0257] The second storage 126 can be implemented by at least one of the following, but is not limited to: a volatile memory, such as a random access memory (RAM); a non-volatile memory, such as a cache, a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc.; or a recording medium, such as a hard disk drive (HDD) or a compact disk read-only memory (CD-ROM).

[0258] The authentication device 130 may include an input device (not shown) for receiving user identification information. Here, the user identification information may include information on at least one of a user's name, ID, or phone number.

[0259] The authentication device 130 may include a sensor that detects biometric information for user authentication.

[0260] The sensor may include an image sensor that obtains an image of a user's face or gestures.

[0261] The sensor may include a complementary metal oxide semiconductor (CMOS) image sensor or a charge coupled device (CCD) image sensor, and a three-dimensional (3D) spatial recognition sensor, such as a KINECT (RGB-D sensor), a time-of-flight (TOF) camera, a stereo camera, etc.

[0262] The image sensor may include a camera that detects information of objects around the vehicle and converts it into electronic image signals.

[0263] A sensor (not shown) may detect user biometric information.

[0264] The user biometric information may include fingerprint information. In this case, the sensor may be a fingerprint sensor. Here, the fingerprint sensor may be a CCD camera or a CCD scanner. The fingerprint sensor may include one of an electrostatic sensor, a thermal sensor, or an ultrasonic image sensor.

[0265] The user biometric information may include voice information, iris information, or vein information.

[0266] In the case where the biometric information is voice information, the sensor may include a microphone.

[0267] In the case where the biometric information is iris information, the sensor may include a camera or an infrared camera.

[0268] In the case where the biometric information is vein information, the sensor may include a vein scanner or a CCD camera.

[0269] In response to a command for starting registration of user biometric information, the sensor may wake up.

[0270] The authentication device 130 may perform user authentication to authenticate the user of the vehicle.

[0271] The authentication device 130 can obtain user biometric information for user authentication, and can obtain biometric identification information that can identify the user from the obtained user biometric information.

[0272] The authentication device 130 may register the obtained biometric information and store it together with the user identification information as information for user authentication of the vehicle.

[0273] In the case where the information used for user authentication is face information, the authentication device 130 can recognize the user's face based on image information obtained by the sensor, and can perform user authentication based on face identification information about the recognized face and pre-registered face recognition information.

[0274] In addition to user authentication based on face recognition, the authentication device 130 may also perform user authentication based on at least one of fingerprint recognition information, voice recognition information, vein recognition information, or iris recognition information.

[0275] In response to receiving biometric information from the mobile device 2 , the authentication device 130 may obtain similarity between the biometric information received from the mobile device 2 and the pre-registered biometric information, and may control updating of the pre-registered biometric information based on the obtained similarity.

[0276] In addition, the authentication device 130 may control at least one of the display 122 or the speaker 123 of the second terminal device 120 to output guide information prompting to update the pre-stored biometric information based on the similarity between the pre-registered biometric information and the received biometric information.

[0277] Based on the user authentication success, the authentication device 130 may send user authentication success information and user identification information to the first terminal device 110 and the first processor 150 .

[0278] Based on the user authentication failure, the authentication device 130 may send user authentication failure information to the first terminal device 110 and the first processor 150 .

[0279] In response to receiving a command for registering biometric information through the input unit 121 of the second terminal device 120 or an input device (not shown) provided in the vehicle 1, the authentication device 130 may activate a sensor of the authentication device, obtain user biometric information based on the biometric information obtained through the activated sensor, obtain biometric information serving as characteristic information of the user from the obtained biometric information, and store the obtained biometric information.

[0280] In addition, the authentication device 130 may control the output of the guide information regarding the registration process of the biometric information. When controlling the output of the guide information, the authentication device 130 may control the operation of the display 122 and the speaker 123 of the second terminal device.

[0281] In response to receiving biometric information from the mobile device 2 in a state where the biometric information is not registered, the authentication device 130 may register the received biometric information as biometric information for user authentication.

[0282] The authentication device 130 may register and store the user identification information together with the biometric information.

[0283] In response to receiving a command for deleting the biometric information, the authentication device 130 may control deletion of the biometric information of the registered user.

[0284] The authentication device 130 may be provided in a head unit of the vehicle.

[0285] The authentication device 130 may also be provided in the second terminal device 120 .

[0286] The first communication device 140 can communicate with the mobile device 2 , the first server 3 , the second server 4 , and the RSE S2 .

[0287] The first communication device 140 may transmit information received from at least one of the mobile device 2, the first server 3, the second server 4, or the RSE S2 to the first processor 150. The first communication device 140 may transmit various information to at least one of the mobile device 2, the first server 3, the second server 4, or the RSE S2 based on a control command of the first processor 150.

[0288] The first communication device 140 may include at least one component that enables communication between various external devices and components of the vehicle 1 , for example, at least one of a short-range communication module, a wireless communication module, or a wired communication module.

[0289] The short-range communication module may include various short-range communication modules that use a wireless communication network to send and receive signals within a short distance, such as a Bluetooth module, an infrared communication module, a radio frequency identification (RFID) communication module, a wireless local area network (WLAN) communication module, a near field communication (NFC) communication module, a Zigbee communication module, etc.

[0290] The wired communication module may include various wired communication modules, such as a controller area network (CAN) communication module, a local area network (LAN) module, a wide area network (WAN) module, a value-added network (VAN) module, etc., and also include various cable communication modules, such as a universal serial bus (USB), a high-definition multimedia interface (HDMI), a digital video interface (DVI), recommended standard 232 (RS-232), power line communication, plain old telephone service (POTS), etc.

[0291] The wired communication module may also include a Local Interconnect Network (LIN).

[0292] In addition to the Wi-fi module and the Wibro module, the wireless communication module may also include the following wireless communication module: the module supports various wireless communication methods, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), Universal Mobile Telecommunications System (UMTS), Time Division Multiple Access (TDMA), Long Term Evolution (LTE), etc.

[0293] The first processor 150 may transmit and receive information with the first terminal device 110 , the second terminal device 120 , and the authentication device 130 .

[0294] The first processor 150 may control a connected car service (CCS).

[0295] The first processor 150 can store member registration information of the connected car service and can control the first communication device 140 based on the member registration information of the connected car service. The first processor 150 can control the first communication device 140 to send and receive information with the mobile device 2, the first server 3 and the second server 4.

[0296] Member registration (subscription) for the connected car service may be performed through the second terminal device of the vehicle or the mobile device.

[0297] Connected car services use a network or Internet connection in or around the vehicle to provide services such as remote starting and diagnosing the vehicle, making and receiving calls, messages and emails, providing real-time traffic information, emergency assistance, etc.

[0298] The connected car service implements vehicle control, vehicle management, etc. by using applications on a mobile device, a first terminal device, and a second terminal device in a vehicle.

[0299] The first processor 150 may control at least one of the remote control service or the CarPay service through the connected car service.

[0300] The first processor 150 may also perform user authentication through the connected car service.

[0301] The first processor 150 may also control the CarPay service through the digital key registered in the mobile device 2 .

[0302] In response to being communicatively connected to the mobile device 2 through the first communication means, the first processor 150 may control the CarPay service by linking to the first application of the mobile device 2 .

[0303] When communicatively connected with the mobile device 2 , the first processor 150 may receive CarPay information regarding the CarPay service, and may control the second terminal device 120 to display the received CarPay information.

[0304] The CarPay information may include member registration information for the CarPay service, CarPay use history information, payment registration information for using the CarPay service, and authentication information for executing the CarPay service.

[0305] CarPay information may include payment information using an IC chip.

[0306] The first processor 150 may receive a card issuance request or a card deletion request from the first server 3 , and may transfer the card issuance command or the card deletion command received from the first server 3 to the first terminal device 110 .

[0307] The first processor 150 may transfer user authentication success information or user authentication failure information received from the authentication device 130 or the second terminal device 120 to the first terminal device 110 .

[0308] The first processor 150 may control activation and standby states of the first terminal device 110 to pay for a service received by a user or a product purchased by the user.

[0309] For example, when the vehicle approaches a toll station, the first processor 150 can determine whether the vehicle is before entering the toll station based on the navigation information of the second terminal device. Based on the determination that the vehicle is before entering the toll station, the first processor 150 can automatically activate the CarPay application set on the second terminal device, control the first terminal device 110 to be in a payment standby state, and automatically pay the fee through the first terminal device 110 when the vehicle passes through the toll station.

[0310] When determining whether the vehicle is before entering a toll station, the first processor 150 can determine whether the distance from the current position of the vehicle to the toll station is a preset distance based on the current position information and the toll station position information, and when it is determined that the distance from the current position to the toll station is the preset distance, the first processor 150 can determine that the vehicle is before entering the toll station.

[0311] In response to receiving confirmation request information from the first server 3 regarding whether the first terminal device is used normally (for example, within a predetermined range, such as consistent with a historical usage pattern), the first processor 150 can control the second terminal device 120 to display guidance information requesting confirmation whether the first terminal device is used normally.

[0312] In response to receiving the confirmation information through the input unit 121 of the second terminal device, the first processor 150 may send the received confirmation information to the first server 3. Here, the confirmation information may include normal use information of the first terminal device and abnormal use information of the first terminal device.

[0313] In response to receiving the user identification information and the IC chip deletion request information from the first server 3, the first processor 150 may send the user identification information and the IC chip deletion request information to the first terminal device. The IC chip deletion request information may be deletion request information of the payment registration information stored in the IC chip.

[0314] In response to not receiving the confirmation information through the input unit 121 of the second terminal device, the first processor 150 may transmit information regarding non-reception of the confirmation information to the first server 3 .

[0315] The first processor 150 may obtain and store the usage pattern information of the first terminal device based on the toll booth passage information collected within a predetermined time period, and may determine whether the first terminal device is being used normally (e.g., outside a predetermined range, such as inconsistent with a historical usage pattern) based on the usage pattern information of the first terminal device stored after (e.g., the vehicle) received the last start command (e.g., recorded by the vehicle) and the toll booth passage information received. In response to determining that the first terminal device is being used abnormally, the first processor 150 may control the second terminal device to output confirmation information requesting confirmation of the abnormal use of the first terminal device.

[0316] The first processor 150 may perform overall control of driving the vehicle.

[0317] The first processor 150 may be implemented as a memory (not shown) storing an algorithm for controlling the operation of components of the vehicle or data on a program for reproducing the algorithm, and a processor (not shown) performing the above-mentioned operation using the data stored in the memory.

[0318] The first memory 151 may store vehicle identification information and user identification information.

[0319] The identification information of the vehicle 1 may include information on the vehicle category, vehicle model, vehicle identification number (vehicle license plate), power generation method (eg, hybrid, electric, internal combustion engine, hydrogen, etc.), and the like.

[0320] The first memory 151 may store identification information of a mobile device that executes a digital key service, authentication information of the mobile device, and a digital key.

[0321] The first memory 151 may store identification information, payment registration information, and user authentication information (eg, password) of the mobile device 2 for executing the CarPay service.

[0322] In the case where there are multiple users, the first memory 151 may store user identification information of each user, mobile device identification information of each user, payment registration information of each user, and user authentication information of each user.

[0323] In the case where there are multiple users, the first memory 151 may also store biometric information of each user.

[0324] Payment registration information may include card information and account information.

[0325] The card information may include information about at least one of a card company, a card number, an expiration date, a password, and a security code (eg, CVC).

[0326] Account information may include information about bank type, account number, account password, and account holder name.

[0327] The identification information of the mobile device is unique identification information of the mobile device, and may include at least one of a phone number, a Wi-Fi MAC address, a serial number, or an International Mobile Equipment Identity (IMEI) of the mobile device 2 .

[0328] The identification information of the mobile device 2 may be Bluetooth identification information (BTID).

[0329] The first memory 151 may store user authentication information and biometric information corresponding to the user identification information.

[0330] The user identification information may include the user's account information.

[0331] The user's account information may include the user's phone number, name, email address, and photo that the user enters when ordering a vehicle.

[0332] The user's account information may be the same as the user's account information registered through the application set on the mobile device 2 .

[0333] The biometric information may include at least one of the following: facial recognition information, fingerprint recognition information, iris recognition information, vein recognition information, or voice recognition information.

[0334] The first memory 151 may delete the user identification information and the biometric information in response to a control command of the first processor 150 .

[0335] The first memory 151 can be implemented by at least one of the following, but is not limited to: a volatile memory, such as a random access memory (RAM); a non-volatile memory, such as a cache, a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc.; or a recording medium, such as a hard disk drive (HDD) or a compact disk read-only memory (CD-ROM).

[0336] The first memory 151 and the first processor 150 may be integrated into one chip, or provided at physically separate locations.

[0337] At least one component may be added or omitted to correspond Figure 3 The components of the vehicle shown, Figure 4 The first terminal device and Figure 5 The performance of the second terminal device shown. In addition, those skilled in the art will readily appreciate that the mutual positions of the constituent components may be modified according to the performance or structure of the vehicle.

[0338] on the other hand, Figure 3 , Figure 4 and Figure 5 Each of the constituent components shown refers to a software and / or hardware component (eg, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC)).

[0339] Figure 6 is a control block diagram showing a first server according to an embodiment.

[0340] The first server 3 may be a server of the vehicle manufacturer, or may be a server provided at a service center that manages the vehicle 1. The first server 3 may also be a server of an application (i.e., an app) that provides services associated with the vehicle 1, a telematics server, or a platform server. In addition, the first server 3 may be a server used in the vehicle development stage.

[0341] The first server 3 may be any one of the following: a card company server, a simple payment service provider (eg, smart payment service) server, a vehicle manufacturer server, a digital key service provider server, or a vehicle management server.

[0342] like Figure 6 As shown, the first server 3 may include a second communication device 310 , a second processor 320 and a second memory 330 .

[0343] The second communication device 310 can communicate with the vehicle 1 , the mobile device 2 , and the second server 4 .

[0344] The second communication device 310 may include at least one component that enables communication with various external devices and components of the first server 3, such as at least one of the following: a short-range communication module, a wireless communication module, or a wired communication module.

[0345] Specific examples of the short-range communication module, the wired communication module, and the wireless communication module are the same as those of the first communication device, and thus descriptions thereof are omitted.

[0346] The second processor 320 may allow payment services through CarPay based on the payment registration information and authentication success information received from the mobile device 2 .

[0347] The second processor 320 may allow payment through the CarPay service based on the payment registration information and the user authentication success information received from the second terminal device 120 .

[0348] The second processor 320 may receive passage information from the first communication device 140 of the vehicle or the first terminal device 110 of the vehicle during a predetermined period of time, obtain a usage pattern based on the received passage information, and store usage pattern information about the obtained usage pattern in the second memory 330. The usage pattern may be a usage pattern of the vehicle, a usage pattern of the first terminal device, or a usage pattern of the IC chip.

[0349] The predetermined time period may be from a time point before the start command is input to a predetermined time point in the past. For example, the predetermined time period may be a time period from yesterday to one month ago.

[0350] The predetermined time period may include a time period from the member registration time for the CarPay service through the first application to a preset time. For example, the predetermined time period may be a one-month period from the member registration time through the first application.

[0351] like Figure 7 As shown, the second processor 320 may obtain and store usage pattern information of the first terminal device for each user.

[0352] The usage pattern information of the first terminal device is based on the passage information, and may include identification information and passage time information of the toll booth, and may also include location information of the toll booth.

[0353] The second processor 320 may also obtain a usage pattern based on the traffic information received during the predetermined number of driving times from the member registration time.

[0354] The second processor 320 may obtain usage information based on the currently received traffic information, and determine whether the use of the first terminal device deviates from the pre-stored usage pattern based on the obtained usage information and the pre-stored usage pattern information. Based on the determination that the use of the first terminal device deviates from the pre-stored usage pattern, it may be determined that the first terminal device is being used abnormally (e.g., outside a predetermined range, such as inconsistent with a historical usage pattern), and based on the determination that the use of the first terminal device is within the pre-stored usage pattern, it may be determined that the first terminal device is being used normally.

[0355] The currently received traffic information may include traffic information received after the last start command of the vehicle was input.

[0356] After obtaining the usage pattern information of the first terminal device, the second processor 320 may determine whether the usage of the first terminal device deviates from a pre-stored usage pattern.

[0357] The usage pattern information of the first terminal device may correspond to the usage pattern information of the vehicle.

[0358] When determining whether the use of the first terminal device deviates from the pre-stored usage pattern information based on the obtained usage information and the pre-stored usage pattern information, the second processor 320 can confirm the toll station identification information (first toll station identification information) and the passage time information of the toll station (first passage time information) based on the pre-stored usage pattern information, and can confirm the toll station identification information (second toll station identification information) and the passage time information of the toll station (second passage time information) based on the received passage information.

[0359] In addition, the second processor 320 may determine whether the first toll station identification information and the second toll station identification information are the same. Based on the determination that the first toll station identification information and the second toll station identification information are the same, the second processor 320 may determine whether the first passage time information and the second passage time information are the same or similar to each other. Based on the determination that the first passage time information and the second passage time information are the same or similar to each other, the second processor 320 may determine that the use of the first terminal device is within the pre-stored use pattern.

[0360] Based on determining that the first toll booth identification information and the second toll booth identification information are different from each other or the first passage time information and the second passage time information are different from each other, the second processor 320 may determine that the use of the first terminal device deviates from a pre-stored use pattern.

[0361] The second processor 320 may determine that the use of the first terminal device deviates from the pre-stored use pattern based on the travel time information and toll booth identification information included in the pre-stored use pattern information and the travel time information and toll booth identification information included in the received travel information.

[0362] When determining whether the use of the first terminal device deviates from the pre-stored usage pattern information based on the obtained usage information and the pre-stored usage pattern information, the second processor 320 can confirm the toll station location information (first toll station location information) based on the pre-stored usage pattern information, confirm the toll station location information (second toll station location information) based on the received passage information, and determine whether the first toll station location information is the same as the second toll station location information.

[0363] Based on determining that the first terminal device is being used abnormally, the second processor 320 may send confirmation request information to the vehicle 1 requesting confirmation of whether the first terminal device is being used normally.

[0364] Here, the abnormal use of the first terminal device may include abnormal use of the vehicle and abnormal use of the IC chip.

[0365] In response to receiving confirmation information from the vehicle 1, the second processor 320 may determine whether the received confirmation information is the same user information or different user information (e.g., the received confirmation information is information about whether the user is different, or information about whether the user has changed). Based on determining that the received confirmation information is the same user information, the second processor 320 may maintain the IC chip of the first terminal device in the issued state, and based on determining that the received confirmation information is different user information (e.g., an indication that the user associated with the last toll booth pass is different from the user associated with the stored usage pattern), the second processor 320 may send a deletion request message of the payment registration information of the IC chip of the first terminal device to the vehicle 1.

[0366] The second processor 320 may also receive information regarding the failure to receive confirmation information from the vehicle 1 .

[0367] In response to not receiving the confirmation information from the vehicle 1 , the second processor 320 may request identification information of the vehicle user from a server (not shown) of the toll road manager.

[0368] In response to receiving the identification information of the vehicle user from the server (not shown) of the toll road management party, the second processor 320 may compare the received identification information of the vehicle user with the user identification information included in the received passage information. Based on determining that the identification information of the vehicle user is different from the user identification information included in the received passage information, the second processor 320 may determine that the user of the vehicle has changed, and based on determining that the identification information of the vehicle user is the same as the user identification information included in the received passage information, the second processor 320 may determine that the user of the vehicle has not changed.

[0369] Based on determining that the user of the vehicle has changed, the second processor 320 may send deletion request information of the payment registration information of the IC chip of the first terminal device to the vehicle 1 .

[0370] In response to receiving the deletion request information of the user identification information and the payment registration information from the second server 4 , the second processor 320 may send the deletion request information of the user identification information and the payment registration information to the vehicle 1 .

[0371] A single second processor 320 or a plurality of second processors 320 may be provided.

[0372] The second processor 320 may be implemented as a memory (not shown) and a processor (not shown), the memory storing an algorithm for controlling the operation of the components of the first server 3 or data about a program for reproducing the algorithm, and the processor performing the above-mentioned operation using the data stored in the memory. In this case, the memory and the processor may be implemented as separate chips. Alternatively, the memory and the processor may be implemented as a single chip.

[0373] The second memory 330 may store identification information of a user who uses the vehicle 1 (user identification information), vehicle identification information, and identification information of a mobile device.

[0374] The user identification information, the vehicle identification information, and the identification information of at least one mobile device 2 stored in the first server 3 may be information registered through an application provided on the mobile device 2 of the vehicle or the second terminal device 120 .

[0375] The second memory 330 may store payment registration information matched with the vehicle identification information and the user identification information.

[0376] The second memory 330 may store vehicle usage pattern information corresponding to the user identification information. The vehicle usage pattern information may be usage pattern information of the first terminal device.

[0377] The usage pattern information of the vehicle may be usage pattern information of the vehicle or the first terminal device within a predetermined period of time.

[0378] The second memory 330 can be implemented by at least one of the following, but is not limited to: a volatile memory, such as a random access memory (RAM); a non-volatile memory, such as a cache, a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPOM), etc.; or a recording medium, such as a hard disk drive (HDD) or a compact disk read-only memory (CD-ROM).

[0379] on the other hand, Figure 6 Each constituent component shown refers to a software and / or hardware component (eg, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC)).

[0380] Corresponds to Figure 6 The performance of the components of the first server 3 shown in FIG. 1 may add or omit at least one component. In addition, those skilled in the art will readily appreciate that the relative positions of the components may be modified according to the performance or structure of the system.

[0381] Fig. 8A and Figure 8Bis a flowchart illustrating a control operation between a first server, a second server, and a vehicle according to an embodiment.

[0382] In response to completing the membership registration for the connected car service and receiving user identification information and payment registration information (501) through the input unit 121 of the second terminal device 120, the vehicle can match and store the received user identification information with the payment registration information, and based on the user identification information and payment registration information, issue a card (e.g., a virtual card) for fee payment through the IC chip of the first terminal device (502).

[0383] The second server 4 may receive user identification information and payment registration information from a user who has completed membership registration through an application for the CarPay service.

[0384] The second server 4 may send the received user identification information and payment registration information to the vehicle 1 ( 503 ).

[0385] In response to receiving the user identification information and payment registration information from the second server 4, the vehicle can also issue a card (e.g., a virtual card) (505) for fee payment through the IC chip of the first terminal device based on the user identification information and payment registration information (504).

[0386] The vehicle may display information related to fee payment using the second terminal device 120. The information related to fee payment may be HI-PASS information.

[0387] like Fig. 9 As shown, the vehicle can use the second terminal device 120 to display a payment history button for requesting display of fee payment history, a HI-PASS card button for selecting a card for paying fees, and a first terminal device information button for requesting display of information about the first terminal device.

[0388] When the HI-PASS card button displayed on the second terminal device 120 is selected, the vehicle may display a card that can be used for toll payment when passing through a toll booth.

[0389] The vehicle can set a card selected from the displayed cards as a card for fee payment through the input unit 121 .

[0390] Additionally, the vehicle may automatically set one of a plurality of cards to pay the fee in response to user identification and user authentication.

[0391] In response to payment of a fee by the first terminal device when passing through a toll booth, the vehicle may transmit passage information (eg, first passage information received at a first time or historical passage information) to the first server 3 (506).

[0392] In response to receiving the passage information from the vehicle 1 , the first server 3 may store the received passage information.

[0393] The first server 3 may collect the stored traffic information within a predetermined period of time (507), obtain (eg, determine) usage pattern information of the first terminal device based on the collected traffic information, and store the obtained usage pattern information of the first terminal device (508).

[0394] The first server 3 may match and store the usage pattern information of the first terminal device with the user identification information.

[0395] The first server 3 may also match and store the usage pattern information of the first terminal device with the user identification information and the payment registration information.

[0396] In response to payment of a fee by the first terminal device when passing through a toll booth, the vehicle 1 may send passage information (e.g., second passage information sent at a second time after the first time) to the first server 3 (509). Here, the passage information may include toll booth identification information, passage time information, and may also include toll booth location information, passage day information, and passage date information.

[0397] In response to receiving the pass information, the first server 3 may determine whether the first terminal device is used normally based on the received pass information and pre-stored usage pattern information (510).

[0398] More specifically, the first server 3 can obtain usage information based on the received traffic information, and determine whether the use of the first terminal device deviates from the pre-stored usage pattern based on the obtained usage information and the pre-stored usage pattern information. Based on the determination that the use of the first terminal device deviates from the pre-stored usage pattern, it can be determined that the first terminal device is being used abnormally, and based on the determination that the use of the first terminal device is within the pre-stored usage pattern, it can be determined that the first terminal device is being used normally.

[0399] Determining whether the use of the first terminal device deviates from the pre-stored usage pattern based on the obtained usage information and the pre-stored usage pattern information may include: confirming the toll station identification information (first toll station identification information) and the passage time information (first passage time information) based on the pre-stored usage pattern information; confirming the toll station identification information (second toll station identification information) and the passage time information (second passage time information) based on the received passage information; determining whether the first toll station identification information is the same as the second toll station identification information; based on determining that the first toll station identification information is the same as the second toll station identification information, determining whether the first passage time information and the second passage time information are the same or similar to each other; and determining that the use of the first terminal device is within the pre-stored usage pattern based on the first passage time information and the second passage time information being the same or similar to each other.

[0400] The first server 3 may determine that the use of the first terminal device deviates from a pre-stored use pattern based on determining that the first toll booth identification information and the second toll booth identification information are different from each other or the first passage time information and the second passage time information are different from each other.

[0401] The first server 3 may determine that the use of the first terminal device deviates from the pre-stored use pattern based on the passage time information and toll booth identification information included in the pre-stored use pattern information and the passage time information and toll booth identification information included in the received passage information.

[0402] When determining whether the use of the first terminal device deviates from the pre-stored usage pattern information based on the obtained usage information and the pre-stored usage pattern information, the first server 3 can also confirm the toll station location information (first toll station location information) based on the pre-stored usage pattern information, confirm the toll station location information (second toll station location information) based on the received passage information, and determine whether the first toll station location information is the same as the second toll station location information.

[0403] Based on the determination that the first terminal device is being used abnormally, the first server 3 may send confirmation request information to the vehicle 1 requesting confirmation of whether the first terminal device is being used normally ( 511 ).

[0404] Here, abnormal use of the first terminal device may include abnormal use of the vehicle (eg, use of the vehicle is inconsistent with a historical use pattern of the vehicle) and abnormal use of the IC chip (eg, use of the IC chip is inconsistent with a historical use pattern of the IC chip).

[0405] In response to receiving the confirmation request information from the first server, the vehicle 1 may control at least one of a display or a speaker of the second terminal device to output the confirmation request information ( 512 ).

[0406] In response to receiving the confirmation information through the input section of the second terminal device (513), the vehicle 1 may transmit the received confirmation information to the first server 3 (514).

[0407] In response to receiving confirmation information from vehicle 1, first server 3 can determine whether the received confirmation information is the same user information or different user information, that is, whether the received confirmation information is information about different users. Based on determining that the received confirmation information is the same user information, first server 3 can keep the IC chip of the first terminal device in the issued state.

[0408] Based on determining that the received confirmation information is different user information (for example, the user associated with the last toll payment or the last received (for example, second) pass information is different from the user associated with the vehicle's historical usage pattern), the first server 3 can send a deletion request message (515) for the payment registration information of the IC chip of the first terminal device to the vehicle 1.

[0409] In this case, the vehicle 1 may confirm the payment registration information corresponding to the user identification information, and may delete the confirmed payment registration information among the payment registration information stored in the first terminal device 110 (516).

[0410] The vehicle 1 may also allow information on the deletion of the payment registration information to be displayed through the display of the second terminal device.

[0411] Based on determining that the confirmation information is not received from the vehicle 1 (517), the first server 3 may request the vehicle user's identification information and the vehicle identification information from a server (not shown) of the toll road manager (518).

[0412] In response to receiving information about non-receipt of confirmation information from the vehicle 1 , the first server 3 may also request the vehicle identification information and the identification information of the vehicle user from a server (not shown) of the toll road manager.

[0413] In response to receiving identification information of a vehicle user from a server (not shown) of a toll road manager, the first server 3 may compare the received user identification information with user identification information corresponding to the received traffic information to determine whether the user of the vehicle has changed (519).

[0414] Based on determining that the received user identification information and the user identification information corresponding to the received pass information are different from each other, the first server 3 can determine that the user of the vehicle has changed, and based on determining that the received user identification information and the user identification information corresponding to the received pass information are the same, the first server 3 can determine that the user of the vehicle has not changed.

[0415] Based on the determination that the user of the vehicle has changed (520), the first server 3 may send a deletion request message (521) of the user identification information and the payment registration information to the vehicle 1. In this case, the vehicle 1 may confirm the payment registration information corresponding to the user identification information, and delete the confirmed payment registration information from the payment registration information stored in the first terminal device 110 (522).

[0416] In response to receiving the deletion request information of the user identification information and the payment registration information (523), the second server 4 may send the deletion request information of the payment registration information to the first server 3 (524).

[0417] In this case, in response to receiving deletion request information of user identification information and payment registration information (for example, received by the first server 3 from the second server 4), the first server 3 can send deletion request information of user identification information and payment registration information to the vehicle 1 (525).

[0418] The second server 4 may also send a deletion request message of the payment registration information to the vehicle 1 .

[0419] In response to receiving the deletion request information of the user identification information and the payment registration information, the vehicle may confirm the payment registration information corresponding to the user identification information and delete the confirmed payment registration information from among the payment registration information stored in the first terminal device 110 (526).

[0420] As can be seen from the above, according to the embodiments of the present disclosure, in the case where the usage information of the first terminal device (terminal device for HI-PASS) deviates from the pre-stored usage pattern information, the user can confirm that the user of the vehicle or the user of the first terminal device has changed, and the payment registration information stored in the first terminal device can be deleted in response to the user's change, thereby preventing the first terminal device from being misused. That is, the misuse of the payment IC chip embedded in the first terminal device can be prevented.

[0421] According to an embodiment of the present disclosure, it may be determined whether a vehicle is stolen based on the user's confirmation information regarding whether the user has changed.

[0422] According to an embodiment of the present disclosure, by paying a fee using a payment IC chip embedded in the first terminal device, the inconvenience of having to physically insert a credit card into the first terminal device can be eliminated, and the risk of losing the inserted credit card can be prevented.

[0423] According to the embodiments of the present disclosure, the amount of plastic used in manufacturing credit cards can be reduced, thereby being beneficial to environmental protection.

[0424] According to an embodiment of the present disclosure, payment registration information may be easily input and stored through an application for the CarPay service set on a mobile device.

[0425] According to an embodiment of the present disclosure, through communication between a mobile device and a vehicle, the payment details of CarPay (date, time, amount, company paid to) and the payment details of the first terminal device can be displayed on the second terminal device (AVN terminal device), thereby allowing the user to quickly and conveniently view the payment details of CarPay and the payment details of the first terminal device.

[0426] According to the embodiments of the present disclosure, only software needs to be changed, thereby eliminating the cost of adding and manufacturing hardware.

[0427] According to the embodiments of the present disclosure, the marketability of the vehicle and the first terminal device can be improved, the user satisfaction and the user trust can be improved, and the competitiveness of the vehicle and the first terminal device can be ensured.

[0428] On the other hand, the above embodiments can be stored in the form of a recording medium storing computer executable instructions. The instructions can be stored in the form of program code, and when executed by a processor, the instructions can perform the operations of the disclosed embodiments. The recording medium can be implemented as a computer-readable recording medium.

[0429] The computer-readable recording medium includes various recording media in which instructions decoded by a computer are stored in, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic tape, a magnetic disk, a flash memory, an optical recording medium, or the like.

[0430] Although the embodiments have been described for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the present disclosure. Accordingly, the embodiments are not described in a limiting sense.

Claims

1. A server, comprising: A communication device configured to: communicate with the vehicle; a processor configured to: determine usage pattern information of the vehicle based on first pass information associated with a toll booth, wherein the first pass information is received from the vehicle at a first time; and A memory configured to: store the determined vehicle usage pattern information; Wherein, the processor is further configured to: determining whether usage of the vehicle is consistent with stored usage pattern information based on second traffic information received from the vehicle at a second time after the first time; and Based on determining that the usage of the vehicle is inconsistent with the stored usage pattern information, a request for confirming the usage of the vehicle is sent to the vehicle.

2. The server according to claim 1, wherein: The processor is configured to determine the usage pattern information of the vehicle by: collecting first pass information associated with a toll booth within a predetermined time period; as well as Based on the first traffic information collected within the predetermined period of time, usage pattern information of the vehicle is determined.

3. The server according to claim 1, wherein: The processor is configured to determine whether the usage of the vehicle is consistent with the stored usage pattern information by: The stored usage pattern information is compared with a portion of the second traffic information recorded after the vehicle received a last start command of the vehicle.

4. The server according to claim 1, wherein: The processor is configured to determine whether the usage of the vehicle is consistent with the stored usage pattern information by: Based on the second traffic information, use information of the vehicle is obtained, wherein the use information includes: identification information associated with the toll booth; and travel time information associated with the toll booth; comparing the usage information with stored usage pattern information of the vehicle to determine whether the usage of the vehicle deviates from the stored usage pattern information of the vehicle; and Based on determining that usage of the vehicle deviates from stored usage pattern information of the vehicle, it is determined that usage of the vehicle is inconsistent with the stored usage pattern information.

5. The server according to claim 1, wherein: The processor is further configured to: determining, based on receiving a confirmation of use of the vehicle from the vehicle, whether the received confirmation indicates that a first user associated with the second pass information is different from a second user associated with the stored usage pattern information of the vehicle; as well as Based on determining that the received confirmation indicates that the first user is different from the second user, a request is sent to the vehicle to delete the payment registration information stored in the vehicle.

6. The server according to claim 1, wherein: The processor is further configured to: Based on not receiving confirmation of use of the vehicle from the vehicle, obtaining first identification information associated with a user of the vehicle; and Based on the first identification information being different from second identification information associated with a second user associated with the first pass information, a request for deleting payment registration information stored in the vehicle is sent to the vehicle.

7. The server according to claim 1, wherein: The server is a first server, wherein the communication device is configured to communicate with the second server, and The processor is further configured to: based on receiving a request from the second server for deleting the payment registration information stored in the vehicle, send the received request to the vehicle.

8. The server according to claim 1, wherein: The stored usage pattern information of the vehicle includes usage pattern information of a terminal device provided in the vehicle, and Wherein, the terminal device includes an integrated circuit (IC) chip for paying fees at the toll station.

9. A vehicle comprising: a first terminal device including an integrated circuit (IC) chip, wherein the IC chip is configured to store payment registration information for fee payment; a communication device configured to: communicate with a server; and The processor is configured as: transmitting, to the server, passage information associated with the toll booth based on payment of a fee at the toll booth via the first terminal device; and The payment registration information stored in the IC chip is deleted based on receiving a request for deleting the payment registration information from the server.

10. The vehicle of claim 9, further comprising: a second terminal device including a user interface, Wherein, the processor is further configured to: upon receiving from the server an indication of abnormal use of the first terminal device, causing the second terminal device to display a message associated with the received indication; and Based on receiving the user information from the second terminal device, the user information is transmitted to the server.

11. The vehicle according to claim 10, wherein: The second terminal device is configured as follows: Identify users; performing user authentication on the identified user; and Based on the result of the user authentication, one of a user authentication success indication or a user authentication failure indication is sent to the first terminal device, and The first terminal device is configured to activate the IC chip based on receiving a user authentication success indication.

12. The vehicle according to claim 11, wherein: The second terminal device is configured to identify the user in the following manner: receiving identification information of the user; and The user is identified based on the received identification information.

13. The vehicle according to claim 11, wherein: The second terminal device is configured to perform user authentication in the following manner: receiving authentication information of the identified user; and The received authentication information is compared with pre-stored user authentication information associated with the user.

14. The vehicle of claim 9, further comprising: The authentication device is configured to: perform user authentication, The processor is further configured to: send one of the following to the first terminal device: a user authentication success indication received from the authentication device, or a user authentication failure indication received from the authentication device, and The first terminal device is configured to activate the IC chip based on receiving a user authentication success indication.

15. The vehicle of claim 9, further comprising: a second terminal device including a user interface, Wherein, the second terminal device is configured as: Stores applications used for the CarPay service; outputting an image corresponding to executing the stored application; and sending the payment registration information received through the application to the first terminal device, and The first terminal device is further configured to issue a card through the IC chip based on the payment registration information.

16. The vehicle of claim 9, wherein: The communication device is further configured to communicate with the mobile device, Wherein, the processor is further configured to: receiving payment registration information registered to an application executable on the mobile device; and sending the received payment registration information to the first terminal device, and The first terminal device is further configured to issue a card through the IC chip based on the payment registration information.

17. The vehicle according to claim 9, wherein: The server is a first server, wherein the communication device is configured to communicate with a second server, The processor is further configured to: based on receiving a request for deleting payment registration information from the second server, send the received request to the first terminal device, and The first terminal device is configured to delete the payment registration information stored in the IC chip based on receiving the sent request.

18. The vehicle of claim 9, wherein: The processor is further configured to: based on receiving a user change indication associated with the vehicle from the server, send a request to the first terminal device for deleting payment registration information, and The first terminal device is configured to delete the payment registration information stored in the IC chip based on receiving the request.

19. The vehicle of claim 9, wherein: The processor is further configured to: obtaining and storing usage pattern information associated with the first terminal device based on historical traffic information associated with a toll booth and collected within a predetermined time period; and Based on a portion of the traffic information recorded after the vehicle received the last start command, it is determined whether the use of the first terminal device is consistent with the stored use pattern information.

20. The vehicle of claim 19, further comprising: a second terminal device including a user interface, The processor is further configured to: in response to determining that the use of the first terminal device is inconsistent with the stored use pattern information, cause the second terminal device to output a message indicating a request for confirming the use of the first terminal device.

Images