SERVER AND CONTROL METHOD THEREOF

Abstract

A server includes a communicator; and a controller configured to control the communicator. The controller is configured to: in response to receiving a card issuance request from a user terminal through the communicator, control the communicator to request a card company server corresponding to the card issuance request for card information; and in response to receiving the card information from the card company server through the communicator, control the communicator to transmit a card issuance command including a security key and the card information to an electronic toll collection system (ETCS) terminal of a vehicle.

Claims

1. A server, comprising: a communicator; and a controller configured to control the communicator, wherein the controller is configured to: in response to receiving a card issuance request from a user terminal through the communicator, control the communicator to request a card company server corresponding to the card issuance request for card information; and in response to receiving the card information from the card company server through the communicator, control the communicator to transmit a card issuance command including a security key and the card information to an electronic toll collection system (ETCS) terminal of a vehicle.

2. The server of claim 1, wherein the card issuance command includes a supplementary security domain (SSD) creation command and an applet creation command.

3. The server of claim 1, wherein, in response to receiving a card issuance success confirmation message from the vehicle, the controller is configured to match and store customer information and the card information issued to the vehicle.

4. The server of claim 3, wherein the controller is configured to: in response to receiving the card issuance request from the user terminal through the communicator, determine whether a previously issued card exists in the ETCS terminal, and in response to the previously issued card being existent, control the communicator to transmit, to the user terminal, a message confirming whether to delete the previously issued card.

5. The server of claim 4, wherein, in response to receiving a deletion command for the previously issued card from the user terminal through the communicator, the controller is configured to control the communicator to transmit a card deletion command including an authorization key to the ETCS terminal of the vehicle.

6. The server of claim 5, wherein the card deletion command includes a supplementary security domain (SSD) deletion command and an applet deletion command.

7. The server of claim 5, wherein, in response to receiving a card deletion success confirmation message from the vehicle, the controller is configured to control the communicator to transmit the card issuance command to the ETCS terminal of the vehicle.

8. The server of claim 7, wherein, in response to receiving the card issuance success confirmation message from the vehicle, the controller is configured to update the pre-stored card information issued to the vehicle.

9. The server of claim 3, wherein, in response to receiving a card deletion request from the card company server, the controller is configured to: identify customer information corresponding to customer information of the card deletion request from among pre-stored customer information and control the communicator to transmit a card deletion command comprising an authorization key to a vehicle corresponding to the identified customer information.

10. The server of claim 9, wherein, in response to receiving a card deletion success confirmation message from the vehicle, the controller is configured to update the pre-stored card information issued to the vehicle.

11. A control method of a server comprising a communicator, the control method comprising: in response to receiving a card issuance request from a user terminal through the communicator, controlling the communicator to request a card company server corresponding to the card issuance request for card information; and in response to receiving the card information from the card company server through the communicator, controlling the communicator to transmit a card issuance command including a security key and the card information to an electronic toll collection system (ETCS) terminal of a vehicle.

12. The control method of claim 11, wherein the card issuance command includes a supplementary security domain (SSD) creation command and an applet creation command.

13. The control method of claim 11, further comprising: in response to receiving a card issuance success confirmation message from the vehicle, matching and storing customer information and the card information issued to the vehicle.

14. The control method of claim 13, further comprising: in response to receiving the card issuance request from the user terminal through the communicator, determining whether a previously issued card exists in the ETCS terminal; and in response to the previously issued card being existent, controlling the communicator to transmit, to the user terminal, a message confirming whether to delete the previously issued card.

15. The control method of claim 14, further comprising: in response to receiving a deletion command for the previously issued card from the user terminal through the communicator, controlling the communicator to transmit a card deletion command including an authorization key to the ETCS terminal of the vehicle.

16. The control method of claim 15, wherein the card deletion command includes an SSD deletion command and an applet deletion command.

17. The control method of claim 15, further comprising: in response to receiving a card deletion success confirmation message from the vehicle, controlling the communicator to transmit the card issuance command to the ETCS terminal of the vehicle.

18. The control method of claim 17, further comprising: in response to receiving the card issuance success confirmation message from the vehicle, updating the pre-stored card information issued to the vehicle.

19. The control method of claim 13, further comprising: in response to receiving a card deletion request from the card company server, identifying customer information corresponding to customer information of the card deletion request from among pre-stored customer information; and controlling the communicator to transmit a card deletion command comprising an authorization key to a vehicle corresponding to the identified customer information.

20. The control method of claim 19, further comprising: in response to receiving a card deletion success confirmation message from the vehicle, updating the pre-stored card information issued to the vehicle.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0029] These and/or other aspects of the disclosure should become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:

[0030] FIG. 1 illustrates an electronic toll collection system (ETCS) card management system according to an embodiment;

[0031] FIG. 2 is a control block diagram illustrating a server according to an embodiment;

[0032] FIG. 3 is a control block diagram illustrating a vehicle according to an embodiment;

[0033] FIG. 4 is a signal flow graph when a server according to an embodiment receives a card issuance request from a user;

[0034] FIG. 5 is a diagram illustrating an example where a card is issued to a card integrated circuit (IC) chip of an ETCS terminal according to an embodiment;

[0035] FIG. 6 is a signal flow graph when a server according to an embodiment receives a card issuance request from a user in a state where a previously issued card exists;

[0036] FIG. 7 is a diagram illustrating an example where a new card is issued in a state where a card has been issued to a card IC chip of an ETCS terminal according to an embodiment;

[0037] FIG. 8 is a signal flow graph when a server according to an embodiment receives a card deletion request from a card company;

[0038] FIG. 9 is a flowchart illustrating operations of managing card issuance in a control method of a server according to an embodiment; and

[0039] FIG. 10 is a flowchart illustrating operations of receiving a card deletion request from a card company in a control method of a server according to an embodiment.

DETAILED DESCRIPTION

[0040] Like reference numerals throughout the specification denote like elements. Also, this specification does not describe all the elements according to embodiments of the disclosure, and descriptions well-known in the art to which the disclosure pertains or overlapped portions are omitted.

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

[0042] It should be understood that the term “include” when used in this specification specifies the presence of stated features, integers, steps, operations, elements, and/or components. However, the term “include” does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0043] It should be understood that the singular forms are intended to include the plural forms as well, unless the context clearly dictates otherwise.

[0044] The terms such as “˜part”, “˜device”, “˜member”, “˜module”, “˜block”, and the like may refer to a unit for processing at least one function or act. For example, the terms may refer to at least process processed by at least one hardware, such as field-programmable gate array (FPGA)/application specific integrated circuit (ASIC), software stored in memories or processors. When a part, device, member, module, block, or the like of the present disclosure is described as having a purpose or performing an operation, function, or the like, the part, device, member, module, block, or the like should be considered herein as being “configured to” meet that purpose or to perform that operation or function.

[0045] Reference numerals used for method steps are just used for convenience of explanation but are not used to limit an order of the steps. Thus, unless the context clearly dictates otherwise, the written order may be practiced otherwise.

[0046] Hereinafter, a server and a control method thereof according to embodiments of the disclosure are described in detail with reference to the accompanying drawings.

[0047] FIG. 1 illustrates an electronic toll collection system (ETCS) card management system according to an embodiment.

[0048] Referring to FIG. 1, an ETCS card management system 1 according to an embodiment includes a server 10 providing a connected car service (CCS) for a vehicle 20, the vehicle 20 including an ETCS terminal, a user terminal 30, and a card company server 40 issuing a card to the ETCS terminal.

[0049] Each of the server 10, the vehicle 20, the user terminal 30, and the card company server 40 may be connected to a network 50 by wire or wirelessly and transmit and receive data with each other through the network 50.

[0050] According to an embodiment, when receiving a card issuance request from the user terminal 30, the server 10 may deliver the card issuance request to the card company server 40, receive card information from the card company server 40, and transmit a card issuance command including a security key and the card information to the vehicle 20.

[0051] Also, according to an embodiment, when receiving a card deletion command from the card company server 40, the server 10 may transmit the card deletion command including an authorization key to the vehicle 20.

[0052] Also, according to an embodiment, by matching and storing customer information and card information about a card issued to the vehicle, the server 10 may manage the customer information and the card information. In this instance, the server 10 may update the customer information and the card information, when a change in card (issuance of a new card or a deletion of card) occurs.

[0053] According to an embodiment, when receiving the card issuance command or the card deletion command from the server 10, the vehicle 20 may deliver the card issuance command or the card deletion command to the ETCS terminal.

[0054] The ETCS terminal of the vehicle 20 may create or delete a supplementary security domain (SSD) and an applet based on the card issuance command or the card deletion command. Thus, a card to a card integrated circuit (IC) chip may be issued or the card issued to the card IC chip may be deleted.

[0055] According to an embodiment, the user terminal 30 may receive an input from a driver of the vehicle 20. For example, the user terminal 30 may receive an input for issuance of a new card and transmit a card issuance request to the server 10 based on the input.

[0056] According to an embodiment, the card company server 40 may generate card information about a card to be issued to the card IC chip of the ETCS terminal and transmit to the server 10. Also, when a card has expired or a payment is outstanding, the card company server 40 may transmit the card deletion request to the server 10.

[0057] As such, the server 10 controls the issuance of the card to the card IC chip of the ETCS terminal or deletion of the issued card, and thus the card of the ETCS terminal may be managed.

[0058] The constituent components of the ETCS card management system 1 and the relationships thereof have been described above. Hereinafter, the constituent components are described in greater detail.

[0059] FIG. 2 is a control block diagram illustrating the server 10 according to an embodiment.

[0060] Referring to FIG. 2, the server 10 according to an embodiment includes a communicator 110, a controller 120, and a storage 130. Here, the controller 120 controls transmission of a signal for issuing or deleting a card of an ETCS terminal to the ETCS terminal, and the storage 130 stores various information required for control.

[0061] According to an embodiment, the communicator 110 is connected to the network 50 to transmit and receive data with the vehicle 20, the user terminal 30, and the card company server 40. To this end, the communicator 110 may be provided as a known type of communication module.

[0062] According to an embodiment, when receiving a card issuance request from the user terminal 30 through the communicator 110, the controller 120 may control the communicator 110 to request the card company server 40 corresponding to the card issuance request for card information.

[0063] According to an embodiment, when receiving the card information from the card company server 40 through the communicator 110, the controller 120 may control the communicator 110 to transmit a card issuance command including a security key and the card information to the ETCS terminal of the vehicle 20.

[0064] In this instance, the security key corresponds to a key with an authority of issuance of card and may be issued by a personal secure application module (PerSAM). The PerSAM is a card-type security device that is required to be used only according to a specified procedure in order to securely deliver a key for issuing a card (electronic currency). In other words, the PerSAM is a module having key information required for issuance and may be provided by the Korea Expressway Corporation in charge of ETCS.

[0065] Also, the card information may include an expiration date, card serial number, issuance-eligible customer information, issuance-eligible vehicle information, and the like.

[0066] Also, the card issuance command may include an SSD creation command and an applet creation command.

[0067] According to an embodiment, when receiving a card issuance success confirmation message from the vehicle 20, the controller 120 may match and store customer information and the card information issued to the vehicle 20 and thus manage the customer information and the card information.

[0068] According to an embodiment, when receiving the card issuance request from the user terminal 30 through the communicator 110, the controller 120 may determine whether a previously issued card exists in the ETCS terminal. In other words, the controller 120 may determine whether a card issued to a user of the user terminal 30 exists based on the pre-stored customer information and card information.

[0069] According to an embodiment, when the previously issued card does not exist in the ETCS terminal, the controller 120 may control the communicator 110 to transmit the card issuance command to the vehicle 20 based on the card information received from the card company server 40, as described above.

[0070] Also, according to an embodiment, when the previously issued card exists in the ETCS terminal, the controller 120 may control the communicator 110 to transmit a message confirming whether to delete the issued card to the user terminal 30.

[0071] When receiving a deletion command for the issued card from the user terminal 30 through the communicator 110, the controller 120 may control the communicator 110 to transmit a card deletion command including an authorization key to the ETCS terminal of the vehicle 20. In this instance, the authorization key corresponds to a key with an authority to delete the card and may be issued by the PerSAM.

[0072] Also, the card deletion command may include an SSD deletion command and an applet deletion command.

[0073] When receiving a card deletion success confirmation message from the vehicle 20 through the communicator 110, the controller 120 may control the communicator 110 to transmit the card issuance command to the ETCS terminal of the vehicle 20.

[0074] Also, when receiving the card issuance success confirmation message from the vehicle 20 through the communicator 110, the controller 120 may update the pre-stored card information issued to the vehicle 20 and thus manage the customer information and the card information.

[0075] According to an embodiment, when receiving a card deletion request from the card company server 40 through the communicator 110, the controller 120 may identify customer information corresponding to customer information of the card deletion request from among the pre-stored customer information and control the communicator 110 to transmit the card deletion command including the authorization key to a vehicle corresponding to the identified customer information.

[0076] Also, when receiving the card deletion success confirmation message from the vehicle 20, the controller 120 updates the pre-stored card information issued to the vehicle 20 and thus manages the customer information and the card information.

[0077] The controller 120 may include at least one memory storing a program for performing the aforementioned operations and operations described below and include at least one processor for implementing a stored program. When a plurality of memories and processors are provided, the plurality of memories and processors may be integrated into one chip or provided in physically separated locations.

[0078] According to an embodiment, the storage 130 may store a variety of modules (e.g., PerSAM) required for deleting or issuing the card and match and store card information corresponding to an issued card and customer information corresponding to the card information. To this end, the storage 130 may be provided as a known type of storage medium.

[0079] FIG. 3 is a control block diagram illustrating the vehicle 20 according to an embodiment.

[0080] Referring to FIG. 3, the vehicle 20 according to an embodiment includes a communicator 210, an ETCS terminal 220 including a card IC chip 223, and a head unit 230 controlling a CCS.

[0081] Each of the communicator 210, the ETCS terminal 220, and the head unit 230 is connected to a vehicle network (NT) and may transmit and receive data with each other.

[0082] According to an embodiment, the communicator 210 is wirelessly connected to the network 50 to perform communication with the server 10. To this end, the communicator 210 may be a known type of wireless communication module.

[0083] According to an embodiment, the ETCS terminal 220 may include a communication interface 221 connected to the vehicle network (NT) to perform communication, a controller 222 controlling issuance and deletion of card, and the card IC chip 223 in which card information of an issued card is input and which performs payment.

[0084] According to an embodiment, the communication interface 221 is connected to the vehicle network (NT) to perform communication. To this end, the communication interface 221 may be provided as a known type of communication module.

[0085] According to an embodiment, when receiving a card issuance command including a security key and card information through the head unit 230, the controller 222 may issue a card to the card IC chip 223 using the security key. Specifically, by generating an SSD and an applet corresponding to the card information in the card IC chip 223 by using the security key, the controller 222 may issue the card.

[0086] Also, when issuing the card to the card IC chip 223 is completed, the controller 222 may allow a card issuance success confirmation message to be transmitted to the server 10 through the head unit 230.

[0087] According to an embodiment, when receiving a card deletion command including an authorization key from the head unit 230 through the communication interface 221, the controller 222 may delete the card issued to the card IC chip using the authorization key. In this instance, deleting the card issued to the card IC chip may be deleting an applet and a SSD corresponding to the card.

[0088] Also, when deleting the card from the card IC chip 223 is completed, the controller 222 may allow a card deletion success confirmation message to be transmitted to the server 10 through the head unit 230.

[0089] The controller 222 may include at least one memory storing a program for performing the aforementioned operations and operations described below and include at least one processor for implementing a stored program. When a plurality of memories and processors are provided, the plurality of memories and processors may be integrated into one chip or provided in physically separated locations.

[0090] According to an embodiment, the card IC chip 223 may perform payment based on the card information of the issued card. In other words, the card IC chip 223 may perform payment based on fee information received from roadside equipment.

[0091] To this end, the card IC chip 223 may include an issuer security domain (ISD), which is initially permanently installed in the card IC chip 223 by an initial card issuer (e.g., a manufacturer of the vehicle 20), and an SSD, which is installed by a service provider (card company) providing a payment service and requires to manage a separate key. In this instance, deletion and change of the card information may be performed only by the ISD and a structure of a security domain (SD) including the ISD and the SSD may comply with a GlobalPlatform (GP) card specification.

[0092] According to an embodiment, the head unit 230 may control the CCS. In other words, the head unit 230 may store CCS subscription information and transmit and receive data with the server 10 through the communicator 210 based on the CCS subscription information.

[0093] For example, the head unit 230 may receive the card issuance command or card deletion command from the server 10 through the communicator 210 and deliver the card issuance command or card deletion command, received from the server 10 through the communicator 210, to the ETCS terminal 220.

[0094] The constituent components of the server 10 and the vehicle 20 have been described above. Hereinafter, the server 10 that generates and transmits a signal for issuing or deleting a card is described in detail.

[0095] FIG. 4 is a signal flow graph when the server 10 according to an embodiment receives a card issuance request from a user. FIG. 5 is a diagram illustrating an example where a card is issued to a card IC chip of an ETCS terminal according to an embodiment.

[0096] Referring to FIG. 4, the user terminal 30 according to an embodiment may request the server 10 for card issuance based on a user input (401).

[0097] According to an embodiment, when receiving the card issuance request from the user terminal 30, the server 10 may deliver the card issuance request to the card company server 40 corresponding to the card issuance request (402).

[0098] In this instance, the card company server 40 may generate card information based on the card issuance request (403) and transmit the card information to the server 10 (404). In this instance, the card information may include an expiration date, card serial number, issuance-eligible customer information, issuance-eligible vehicle information, and the like.

[0099] When receiving the card information from the card company server 40, the server 10 may transmit a card issuance command including a security key and the card information to the vehicle 20 (405).

[0100] In this instance, the security key corresponds to a key with an authority of issuance of card, and may be issued by a PerSAM. The PerSAM is a card-type security device that is required to be used only according to a specified procedure in order to securely deliver a key for issuing a card (electronic currency). In other words, the PerSAM is a module having key information required for issuance and may be provided by the Korea Expressway Corporation in charge of ETCS.

[0101] Also, the card issuance command may include an SSD creation command and an applet creation command.

[0102] According to an embodiment, when receiving the card issuance command from the server 10, the head unit 230 may transmit the card issuance command to the ETCS terminal 220 (406), and the ETCS terminal 220 may generate an SSD and an applet in the card IC chip 223 and issue a card (407).

[0103] Specifically, as shown in FIG. 5, by generating an SSD 223b and an applet 223c corresponding to the card information in the card IC chip 223 by using the security key, the ETCS terminal 220 may issue the card. In this instance, generation of the SSD 223b and the applet 223c may be performed by an ISD 223a.

[0104] Afterwards, the ETCS terminal 220 may transmit whether the issuance is successful to the head unit 230 (408), and the head unit 230 may transmit whether the issuance is successful to the server 10 (409). In other words, when issuing the card to the card IC chip 223 is completed, the ETCS terminal 220 may transmit a card issuance success confirmation message to the server 10 through the head unit 230.

[0105] According to an embodiment, when receiving the card issuance success confirmation message from the vehicle 20, the server 10 may match and store customer information and the card information issued to the vehicle 20 and thus manage the customer information and the card information issued to the vehicle 20 (410).

[0106] FIG. 6 is a signal flow graph when the server 10 according to an embodiment receives a card issuance request from a user in a state where a previously issued card exists. FIG. 7 is a diagram illustrating an example where a new card is issued in a state where a card has been issued to the card IC chip 223 of the ETCS terminal 220 according to an embodiment.

[0107] Referring to FIG. 6, the user terminal 30 according to an embodiment may transmit a card issuance request to the server 10 according to a user input (601).

[0108] According to an embodiment, when a previously issued card exists in the ETCS terminal 220, the server 10 may control the communicator 110 to transmit a message confirming whether to delete the previously issued card to the user terminal 30 (602).

[0109] In this case, the user terminal 30 may transmit the message confirming whether to delete the previously issued card (a deletion command for the previously issued card) to the server 10, based on a user input (603).

[0110] According to an embodiment, when receiving the deletion command for the previously issued card from the user terminal 30 through the communicator 110, the server 10 may transmit a card deletion command including an authorization key to the vehicle 20 (604). In this instance, the authorization key corresponds to a key with an authority to delete the card and may be issued by the PerSAM. Also, the card deletion command may include a SSD deletion command and an applet deletion command.

[0111] In this case, the head unit 230 receiving the card deletion command may deliver the card deletion command to the ETCS terminal 220 (605).

[0112] When receiving the card deletion command including the authorization key from the head unit 230 through the communication interface 221, the ETCS terminal 220 may delete the card issued to the card IC chip by using the authorization key (606).

[0113] In this instance, deleting the card issued to the card IC chip may be deleting an SSD 223b-1 and an applet 223c-1 corresponding to the card, as shown in FIG. 7.

[0114] Also, the ETCS terminal 220 may transmit whether the deletion of the card issued to the card IC chip 223 is successful to the head unit 230 (607), and the head unit 230 may transmit whether the card deletion is successful to the server 10 (608).

[0115] In other words, when deleting the card from the card IC chip 223 is completed, the ETCS terminal 220 may transmit a card deletion success confirmation message to the server 10 through the head unit 230.

[0116] Also, according to an embodiment, the server 10 may transmit a card issuance request to the card company server 40 corresponding to the card issuance request (609).

[0117] In this case, the card company server 40 may generate card information based on the card issuance request (610) and transmit the card information to the server 10 (611). In this instance, the card information may include an expiration date, card serial number, issuance-eligible customer information, issuance-eligible vehicle information, and the like.

[0118] When receiving the card information from the card company server 40, the server 10 may transmit a card issuance command including a security key and the card information to the vehicle 20 (612).

[0119] According to an embodiment, when receiving the card issuance command from the server 10, the head unit 230 may transmit the card issuance command to the ETCS terminal 220 (613), and the ETCS terminal 220 may generate an SSD and an applet in the card IC chip 223 and issue a card (614).

[0120] Specifically, as shown in FIG. 7, by generating a SSD 223b-2 and an applet 223c-2 corresponding to the card information in the card IC chip 223 by using the security key, the ETCS terminal 220 may issue the card. In this instance, generation of the SSD 223b-2 and the applet 223c-2 may be performed by the ISD 223a.

[0121] Afterwards, the ETCS terminal 220 may transmit whether the issuance is successful to the head unit 230, and the head unit 230 may transmit whether the issuance is successful to the server 10. In other words, when issuing the card to the card IC chip 223 is completed, the ETCS terminal 220 may transmit a card issuance success confirmation message to the server 10 through the head unit 230.

[0122] According to an embodiment, when receiving the card issuance success confirmation message from the vehicle 20, the server 10 may match and update customer information and the card information issued to the vehicle 20 and thus manage the customer information and the card information issued to the vehicle 20.

[0123] FIG. 8 is a signal flow graph when the server 10 according to an embodiment receives a card deletion request from a card company.

[0124] Referring to FIG. 8, the card company server 40 according to an embodiment may transmit a card deletion request to the server 10 (801). In other words, the card company server 40 may transmit the card deletion request to the server 10, when a card has expired or payment is outstanding.

[0125] According to an embodiment, when receiving the card deletion request from the card company server 40 through the communicator 110, the server 10 may identify customer information corresponding to customer information of the card deletion request from among pre-stored customer information (802) and control the communicator to transmit a card deletion command including an authorization key to a vehicle corresponding to the identified customer information (803).

[0126] In this case, the head unit 230 may transmit the card deletion command, received from the server 10, to the ETCS terminal 220 (804).

[0127] When receiving the card deletion command including the authorization key from the head unit 230 through the communication interface 221, the ETCS terminal 220 may delete a card issued to the card IC chip using the authorization key (805). In this instance, deleting the card issued to the card IC chip may be deleting an SSD and an applet corresponding to the card.

[0128] Also, the ETCS terminal 220 may transmit whether the deletion of the card issued to the card IC chip 223 is successful to the head unit 230 (806), and the head unit 230 may transmit whether the card deletion is successful to the server 10 (807).

[0129] In other words, when deleting the card from the card IC chip 223 is completed, the ETCS terminal 220 may transmit a card deletion success confirmation message to the server 10 through the head unit 230.

[0130] According to an embodiment, when receiving the card deletion success confirmation message from the vehicle 20, the server 10 may update pre-stored card information issued to the vehicle 20 and thus update the customer information and the card information (808).

[0131] Hereinafter, embodiments of a control method of the server 10 according to an aspect of the disclosure are described. The server 10 according to the above-described embodiment may be used in the control method of the server 10. Accordingly, the above description with reference to FIGS. 1-8 may be equally applied to the control method of the server 10.

[0132] FIG. 9 is a flowchart illustrating operations of managing card issuance in a control method of the server 10 according to an embodiment.

[0133] Referring to FIG. 9, according to an embodiment, when a card issuance request is received from the user terminal 30 (Yes in operation 910), the server 10 may determine whether a previously issued card exists in the ETCS terminal 220 (920). In other words, the controller 120 may determine whether a card issued to a user of the user terminal 30 exists based on pre-stored customer information and card information,

[0134] According to an embodiment, when the previously issued card exists (Yes in operation 920), the server 10 may transmit a request for confirming whether to delete the previously issued card to the user terminal 30 (930). When a message confirming the deletion of the previously issued card is received (Yes in operation 940), the server 10 may transmit a card deletion command including an authorization key to the vehicle 20 (950). In this instance, the authorization key corresponds to a key with an authority to delete the card and may be issued by the PerSAM. Also, the card deletion command may include an SSD deletion command and an applet deletion command.

[0135] According to an embodiment, the server 10 may transmit the card issuance request to the card company server 40 (960), and when card information is received (Yes in operation 970), transmit a card issuance command including a security key and the card information to the vehicle 20 (980).

[0136] In this instance, transmitting the card issuance request to the card company server 40 may be performed regardless of transmitting the card deletion command to the vehicle 20 and also be performed before or simultaneously with transmission of the card deletion command.

[0137] However, transmitting the card issuance command to the vehicle 20 may be performed after transmitting the card deletion command, for example, may be performed in response to receiving a card deletion success confirmation message from the vehicle 20.

[0138] Also, according to an embodiment, when the previously issued card does not exist (No in operation 920), the server 10 may transmit the card issuance request to the card company server 40 (960). Also, when the card information is received (Yes in operation 970), the server 10 may transmit the card issuance command including the security key and the card information to the vehicle 20 (980).

[0139] FIG. 10 is a flowchart illustrating operations of receiving a card deletion request from a card company in a control method of the server 10 according to an embodiment.

[0140] Referring to FIG. 10, according to an embodiment, when a card deletion request is received from the card company server 40 (Yes in operation 1010), the server 10 may identify customer information corresponding to requested information (1020).

[0141] Specifically, when the card deletion request is received from the card company server 40 through the communicator 110, the server 10 may identify customer information corresponding to customer information of the card deletion request from among pre-stored customer information.

[0142] According to an embodiment, the server 10 may transmit a card deletion command including an authorization key to a vehicle corresponding to the identified customer information (1030), and when receiving a card deletion success confirmation message from the vehicle 20 (Yes in operation 1040), update the customer information and card information issued to the vehicle (1050).

[0143] In other words, when receiving the card deletion success confirmation message from the vehicle 20, the server 10 updates the pre-stored card information issued to the vehicle 20 and thus updates the customer information and the card information.

[0144] As is apparent from the above, according to the embodiments of the disclosure, the server and the control method thereof can manage a card performing payment in an ETCS terminal through issuance or deletion of the card and thus allow a card of a card company to be issued to a card IC chip of the ETCS terminal manufactured by a vehicle manufacturer.

[0145] Embodiments can thus be implemented in the form of a recording medium storing computer-executable instructions that are executable by a processor. The instructions may be stored in the form of a program code, and when executed by a processor, the instructions may generate a program module to perform operations of the disclosed embodiments. The recording medium may be implemented non-transitory as a computer-readable recording medium.

[0146] The computer-readable code can be recorded on a medium or transmitted through the Internet. The medium may include read only memory (ROM), random access memory (RAM), magnetic tapes, magnetic disks, flash memories, and optical recording medium.

[0147] Although embodiments have been described for illustrative purposes, those having ordinary skill in the art should appreciate that various modifications, additions, and substitutions are possible, without departing from the scope and spirit of the disclosure. Therefore, embodiments have not been described for limiting purposes.