WO2014021747A1

WO2014021747A1 - Flexible payment in pricing system

Info

Publication number: WO2014021747A1
Application number: PCT/SE2012/050857
Authority: WO
Inventors: Shinta Shinta SUGIMOTO; Shingo Murakami; Takeshi Matsumura; Toshikane Oda
Original assignee: Telefonaktiebolaget L M Ericsson (Publ)
Priority date: 2012-08-03
Filing date: 2012-08-03
Publication date: 2014-02-06

Abstract

A mobile device, which makes payment flexible in a pricing system, is provided. The mobile device includes a storage unit configured to store user identification information of a first user; first communication unit configured to communicate with a terminal having account information of a second user, the account information being transmitted to a pricing system by the terminal for a transaction; a second communication unit configured to communicate with the pricing system via a network; and a control unit configured to obtain terminal identification information of the terminal from the terminal, wherein the control unit is further configured to transmit the user identification information of the first user and the terminal identification information of the terminal to the pricing system such that the first user makes payment for the transaction instead of the second user.

Description

DESCRIPTION

FREXIBLE PAYMENT IN PRICING SYSTEM

TECHNICAL FIELD

[0001] The present invention relates to an

electronic pricing system.

BACKGROUND

[0002] Recently, an electronic pricing system such as an Electronic Road Pricing (ERP) system has been widely deployed. The ERP system allows drivers to pay a toll fare automatically. In the ERP system, an On- Board Unit (OBU) provided in a car transmits user account information to a roadside terminal attached on a toll gate using a short range radio communication link, which is also referred to as Dedicated Short Range Communications (DSRC) link when the car passes through the toll gate. The user account information is normally issued by a credit card company.

[0003] Then, the toll way operator charges the credit card company for the toll fare by providing the user account information used at the toll gate, and the credit card company charges person specified by the user account information for the toll fare. Usually, the user account information is stored in a smartcard. For instance, in the case of the ERP system in Japan, a user needs to obtain a smartcard from a credit card company in advance, and the user needs to insert the smartcard into the OBU.

[0004] In the current ERP system, if a fellow passenger also has his/her smartcard, the fellow passenger can pay the toll fare instead of the driver by inserting the smartcard of the fellow passenger into the OBU. Further, the OBU is recently provided in a rental car. Thus the user of the rental car can use the ERP system by inserting his/her smartcard into the OBU in the rental car.

[0005] Thus, the user account information is not stored in the OBU, but in the smartcard detachable from the OBU, the person who pays the toll fare can be easily changed by replacing the smartcard.

[0006] However, there are some advantages of OBUs having the embedded memory, which stores the user account information and is not detachable from the OBU, over the traditional OBU, which has a slot for

inserting the smartcard. For example, the size and the cost of the OBU having the embedded memory can be reduced compared to the OBU having the slot for the smartcard. Further, the OBU having the embedded memory is more resistant to shocks and vibration than the OBU having the slot for the smartcard, because it requires physical contact between the smartcard and the OBU.

Taking the requirements from the automotive industry, European Telecommunication Standards Institute (ETSI) defines physical characteristics of embedded UICC as shown in ETSI TS 102 671.

[0007] If the user account information is stored in the memory which cannot detach from the OBU, the user cannot change the user account information in the OBU. This is inconvenient if the person other than the owner of the OBU needs or wants to make a payment.

SUMMARY

[0008] The present invention provides a mobile device, a terminal and a server used in a pricing system or a charging system, which makes payment flexible .

[0009] In accordance with a first aspect of the present invention, a mobile device includes a storage unit configured to store user identification

information of a first user; a first communication unit configured to communicate with a terminal having account information of a second user, where the account information is transmitted to a pricing system by the terminal for a transaction; a second communication unit configured to communicate with the pricing system via a network; and a control unit configured to obtain terminal identification information of the terminal from the terminal using the first communication unit. The control unit is further configured to transmit the user identification information of the first user and the terminal identification information of the terminal to the pricing system using the second communication unit such that the first user makes payment for the transaction on behalf of the second user.

[0010] The control unit may be further configured to prompt the first user to enter an amount of money that the first user makes payment, and to transmit the amount of money to the pricing system. The control unit may be further configured to prompt the first user to enter a sub ect for the transaction that the first user makes payment, and to transmit the sub ect to the pricing system.

[0011] The user identification information of the first user and the terminal identification information may be transmitted to the pricing system so that the pricing system changes the account information of the second user stored in the terminal to account

information of the first user. The control unit may be further configured to receive the account information of the first user from the pricing system using the second communication unit, and to transmit the account information of the first user to the terminal using the first communication unit. Further, the control unit may be further configured to transmit the user

identification information of the first user and the terminal identification information to the pricing system if the first user enters an input indicating an approval of payment on behalf of the second user. The account information of the first user may have a validity period or a number of times that the terminal can use the account information of the first user.

[0012] In accordance with a second aspect of the present invention, a terminal using account information of the terminal for a transaction with a pricing system includes a storage unit configured to store terminal identification information of the terminal and first account information; and a control unit configured to transmit the terminal identification information to a mobile device, and to change the account information of the terminal from the first account information to second account information received from the mobile device or the pricing system.

[0013] The control unit may be further configured to change the account information of the terminal from the second account information to the first account information when one transaction with the pricing system using the second account information is

completed. The second account information may have a validly period or a number of transactions, and the control unit may be further configured to change the account information of the terminal from the second account information to the first account information when the validity period of the second account

information is expired or the terminal uses the second account information by times equal to the number of transactions .

[0014] In accordance with a third aspect of the present invention, a server used in a pricing system includes a storage unit configured to store a relation of user identification information and account

information for each user; and a control unit

configured to receive user identification information of a first user, terminal identification information of a terminal having account information of a second user and a payment condition by the first user from a mobile device. The control unit is further configured to charge the first user instead of the second user for a transaction performed using the account information of the second user between the terminal and the pricing system based on the payment condition.

[0015] In accordance with a fourth aspect of the present invention, a server used in a pricing system includes a storage unit configured to store a relation of user identification information and account

information for each user; and a control unit

configured to receive user identification information of a first user, terminal identification information of a terminal having account information of a second user and a payment condition by the first user from a mobile device, and to transmit account information of the first user, the terminal identification information of the terminal and the payment condition by the first user to another server in the pricing system such that the pricing system charges the first user instead of the second user for a transaction performed using the account information of the second user between the terminal and the pricing system based on the payment condition.

[0016] In accordance with a fifth aspect of the present invention, a server used in a pricing system includes a storage unit configured to store a relation of user identification information and account

information for each user; a control unit configured to receive user identification information of a first user and terminal identification information of a terminal having account information of a second user from a mobile device, and to generate temporary user account information of the first user to set the temporary user account information to the terminal in response to a reception of the user identification information of the first user.

[0017] In accordance with a sixth aspect of the present invention, a method performed by a mobile device having user identification information of a first user is provided. The method includes the steps of obtaining terminal identification information of a terminal from the terminal using a first communication unit, where the terminal has account information of a second user and the account information is transmitted to a pricing system by the terminal for a transaction; and transmitting the user identification information of the first user and the terminal identification

information of the terminal to the pricing system using a second communication unit such that the first user makes payment for the transaction on behalf of the second user.

[0018] In accordance with a seventh aspect of the present invention, a method performed by a terminal using account information of the terminal for a

transaction with a pricing system, where the terminal stores terminal identification information of the terminal and first account information as the account information of the terminal, is provided. The method includes the steps of transmitting the terminal

identification information to a mobile device;

receiving second account information from the mobile device or the pricing system; and changing the account information of the terminal from the first account information to the second account information; and transmitting the second account information to the pricing system for a transaction.

[0019] In accordance with an eighth aspect of the present invention, a method performed by a server in a pricing system is provided. The method includes the steps of receiving user identification information of a first user and terminal identification information of a terminal having account information of a second user from a mobile device, and generating temporary user account information of the first user to set the temporally user account information to the terminal.

[0020] Further objects and advantages of the present invention will be apparent from the following description of the exemplary embodiments of the

invention as illustrated in the accompanying drawings.

BRIEF DESCRIPTION OF DRAWINGS

[0021] Fig. 1 shows an exemplary system according to an embodiment of the present invention;

[0022] Fig. 2 shows an exemplary sequence diagram according to an embodiment of the present invention;

[0023] Fig. 3 shows an exemplary sequence diagram according to another embodiment of the present

invention;

[0024] Fig. 4 is an exemplary sequence diagram according to still another embodiment of the present invention;

[0025] Fig. 5 shows an exemplary block diagram of a mobile device according to an embodiment of the present invention;

[0026] Fig. 6 shows an exemplary block diagram of an on-board unit according to an embodiment of the present invention; and [0027] Fig. 7 shows an exemplary block diagram of a credit server according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] Fig. 1 shows an exemplary system according to an embodiment. The embodiment uses an Electronic Road Pricing (ERP) system as an example of pricing systems or charging systems, however; the invention is not limited to the ERP system, but can be applied to other pricing systems or charging systems.

[0029] In Fig. 1, an on-board unit (OBU) 2 is a terminal used for transactions with a pricing system 8. According to the present embodiment, the OBU 2 is provided in a car 100. The OBU 2 stores user account information (UAI) of a driver, who is an owner of the car 100 and the OBU 2, and terminal identification information (OBU-ID) , which is used to identify the OBU 2. The user account information is issued by a credit card company, and is stored in an embedded memory of the OBU 2, and the driver cannot replace the embedded memory of the OBU 2 with other memory.

[0030] The OBU 2 has a first short range wireless interface such as near field communication (NFC) , and can communicate with a mobile device 1 using the NFC interface. Further, the OBU 2 has a second short range wireless interface such as a dedicated short range communication (DSRC) , and can communicate with an ERP device 3 installed at a toll gate of the toll way using the DSRC interface. In one embodiment, the OBU 2 has a mobile communication interface according to a standard defined by, for example, the third generation

partnership project (3GPP), and can communicate with servers connected to a network 7 using the mobile communication interface. In other embodiments, the mobile communication interface is not required for the OBU2.

[0031] The mobile device 1 of a fellow passenger has a mobile communication interface according to a standard defined by, for example, 3GPP, and can

communicate with servers connected to the network 7 using the mobile communication interface. Further, the mobile device 1 has a short range wireless interface such as near field communication (NFC) , and can

communicate with the OBU 2 using the NFC interface.

The mobile device 1 stores user identification

information (U-ID) of the fellow passenger. The fellow passenger also has user account information (UAI) issued by the credit card company.

[0032] In the present embodiment, the network 7 includes a mobile communication network in accordance with 3GPP standards and/or data network such as the

Internet. However, the network 7 may be a data network, which can be accessed via a wireless local area network (W-LAN) access point. In this case, the mobile device 1 and the OBU 2 have a W-LAN interface instead of the mobile communication interface.

[0033] A credit server 5 is operated by the credit card company, which issues UAIs and stores a relation of UAI to U-ID for each user based on contracts in advance. The UAI is like a credit card number, and is used for each transaction with the pricing system 8, and the credit card company issues bills to a user identified by the UAI used in the transactions.

[0034] The ERP device 3 is a device installed at a toll gate, and obtains the UAI stored in the OBU 2 using a DSRC link when the car 100 passes through the toll gate, and transmits the UAI to an ERP server 4. The ERP server 4 calculates the toll fare charged to a person identified by the UAI and stores the toll fare and the UAI . The ERP device 3 and the ERP server 4 are operated by the toll way operator, and the toll way operator informs the credit card company of the toll fare and the UAI, and issues a bill of the toll fare to the credit card company based on information stored in the ERP server 4. The credit card company issues a bill of the toll fare to a user identified by the UAI.

[0035] In one embodiment, a management server 6 is used. The management server 6 can communicate with the OBU 2 via the network 7, and can change the UAI stored in the OBU 2 into temporary user account information ( T-UAI ) . In Fig. 1, the pricing system 8 includes the ERP device 3, the ERP server 4, the credit server 5 and the management server 6. The management server 6 may be operated by the toll way operator, the credit card company or a third-party company.

[0036] Fig. 2 is an exemplary sequence diagram according to an embodiment of the present invention. In the present embodiment, the mobile communication interface of the OBU 2 and the management server 6 are not required.

[0037] If the fellow passenger makes payment of all or part of toll fare of the journey, the fellow passenger makes device pairing in step SI 00. The device pairing is performed by placing the mobile device 1 within the communication range of NFC with the OBU 2. By the pairing, the mobile device 1 obtains terminal identification information (OBU-ID) of the OBU 2 in step S101. In step S102, the mobile device 1 displays a screen to prompt the fellow passenger to enter an amount of money that the fellow passenger pays, and the fellow passenger enters the amount of money. In step S103, the mobile device 1 transmits a request message including the U-ID of the fellow passenger, the OBU-ID of the OBU 2 and the amount of money entered by the fellow passenger to the credit server 5 via the network 7. In step SI 04, the credit server 5 transmits a response message including a random value to the mobile device 1 via the network 7 for the authentication, and the mobile device 1 transmits a request message including a signature to the credit server 5 via the network 7 in step SI 05. The signature is computed by the private key of the fellow passenger stored in the mobile device 1, and a set of parameters including the U-ID of the fellow passenger, the OBU-ID of the OBU 2, the random value, and optionally more parameters are provided as an input for the signature computation. The credit server 5 verifies the

signature transmitted in the step SI 05 using the public key of the fellow passenger. The person skilled in the art would understand that other authentication methods may be applied.

[ 0038 ] If the authentication of the mobile device

1 is successful, the credit server 5 identifies the UAI of the fellow passenger from the U-ID of the fellow passenger, and transmits a request message including the UAI of the fellow passenger, the OBU-ID of the OBU 2 and the amount of money paid by the fellow passenger to the ERP sever 4 in step SI 06. The ERP sever 4 stores the UAI of the fellow passenger, the OBU-ID of the OBU 2 and the amount of money paid by the fellow passenger in step S107, and transmits an

acknowledgement message to the credit server 5 in step SI 08. The credit sever 5 transmits an acknowledgement message to the mobile device 1 in response to a reception of the acknowledgement message from the ERP server 4 in step S109.

[ 0039 ] In step S110, the car 100 passes through one or more toll gates, and the ERP device 3 installed on each toll gate that the car 100 passes through obtains the UAI of the driver and OBU-ID of the OBU 2. In step Sill, the ERP device 3 reports the obtained UAI and the OBU-ID to the ERP server 4. The ERP sever 4 calculates the total fare charged to the UAI of the driver obtained from the ERP device 3. Since the OBU- ID received from the ERP device 3 is stored in the ERP server 4 related to the UAI of the fellow passenger, the ERP server 4 compares the total fare charged to the UAI of the driver and the amount of money paid by the fellow passenger in step S112. If the total fare is less than or equal to the amount of money paid by the fellow passenger, the toll way operator charges the fellow passenger for the total fare. If the total fare is more than the amount of money paid by the fellow passenger, the toll way operator charges the amount of money paid by the fellow passenger stored in the step SI 07 to the fellow passenger, and charges the

difference between the total fare and the amount of money paid by the fellow passenger to the driver of the car 100. In step S113, settlement of payment is made by the toll way operator and the credit card company, and the credit card company charges the fellow passenger and the driver accordingly.

[ 0040 ] According to the present embodiment, the fellow passenger can decide the amount of money he/she owes, even though the UAI in the OBU 2 has not changed. In the embodiment, the fellow passenger can specify the amount of money, which the fellow passenger makes payment. Alternatively, the fellow passenger can specify the section of the toll way, which the fellow passenger owes. In other words, the fellow passenger can specify subjects of payment instead of the amount of money. In this case, the pricing system 8 may charge the fellow passenger for subjects that the fellow passenger has specified, and the pricing system 8 may charge the driver for subjects that the fellow passenger has not specified. In the case of ERP system, the fellow passenger may enter a road section from A to B to the mobile device 1. In this case, the pricing system 8 may charge the fellow passenger for the toll fare of the section from A to B if the driver enters the toll way at A and exits the toll way at B, and the pricing system 8 may charge the driver for the toll fare if the driver did not enter the toll way at A or did not exit the toll way at B. Or, the pricing system 8 may charge the fellow passenger for the toll fare if both the entry point and exit points are within the section from A to B, and the pricing system 8 may charge the driver for the toll fare if the one of the entry point or exit point is outside the section from A to B. Further, the fellow passenger may enter a date of transaction in addition to the subjects for

transactions to the mobile device 1. The information specifying the payment condition, i.e. the amount of money, subjects, date and so on, entered by the fellow passenger in the step 102 are transmitted to the credit server 5 in the step SI 03 and to the ERP server 4 in the step S106.

[0041] Further, the ERP server 4 can send a message obtaining an approval from the fellow passenger before the step S113. For example, assume that the fellow passenger enters a date without specifying the amount of money or subjects for payment in the step S102. In this case the ERP sever 4 may charge the fellow passenger for all toll fares of the date.

However, the ERP server 4 may communicate with the mobile device 1, and receive a reply indicting an approval or subjects that the fellow passenger makes payment from the mobile device 1. Then, the ERP server 4 may charge the fellow passenger and drivers

accordingly.

[0042] Fig. 3 is a sequence diagram according to another embodiment of the present invention. In the present embodiment, the OBU 2 has a mobile

communication interface, and the management server 6 is required. [0043] If the fellow passenger makes a payment for a toll fare at upcoming toll gate, the fellow passenger makes a device pairing in step S200, and the mobile device 1 obtains the OBU-ID of the OBU 2 in step S201. In step S202, the mobile device 1 displays a screen for asking the approval by the fellow passenger, and if the fellow passenger approves the payment at the upcoming toll gate, the mobile device 1 transmits a request message including the U-ID of the fellow passenger and the OBU-ID of the OBU 2 to the credit server 5 via the network 7 in step S203. In step S204, the credit server 5 transmits a response message including a random value to the mobile device 1 via the network 7 for the authentication, and the mobile device 1 transmits a request message including a signature to the credit server 5 via the network 7 in step S205. The signature is computed by the private key of the fellow passenger stored in the mobile device 1, and a set of parameters including the U-ID of the fellow passenger, the OBU-ID of the OBU 2, the random value, and optionally more parameters are provided as an input for the signature computation. The credit server 5 verifies the signature transmitted in the step S205 using the public key of the fellow passenger.

[0044] If the authentication is successful, the credit server 5 transmits an acknowledgement message to the mobile device 1 in step S206, and generates temporary user account information ( T-UAI ) of the fellow passenger in step S207. The T-UAI is basically the same as the UAI . However, the T-UAI is just used for a short time period, i.e. temporary. Then the credit server 5 transmits a request message including the T-UAI of the fellow passenger and the OBU-ID of the OBU 2 to the ERP server 4 in step S208. The ERP sever 4 transmits an acknowledgement message to the credit server 5 in step S209, and transmits a request message including the T-UAI of the fellow passenger and the

OBU-ID of the OBU 2 to the management server 6 in step S210. The management server 6 transmits an

acknowledgement message to the ERP server 4 in step S211.

[ 0045 ] Upon reception of the request message from the ERP server 4 in the step S210, the management server 6 transmits a change request message including the T-UAI of the fellow passenger to the OBU 2 via the network 7 in step S212. Upon a reception of the change request message from the management server 6, the OBU 2 sets the T-UAI of the fellow passenger to the OBU 2 as its user account information in step S213. In step S214, the car 100 passes through the toll gate, and the ERP device 3 installed on the toll gate that the car 100 passes through obtains the T-UAI of the fellow passenger stored in the OBU 2. The ERP device reports the obtained T-UAI to the ERP server 4 in step S215. In step S217, the settlement is performed between the toll way operator and the credit card company. Since the T-UAI is used for the transaction at the step S214, the toll fare is charged to the fellow passenger.

Since the OBU 2 has used the T-UAI of the fellow passenger for the transaction in the step S214, the OBU 2 restores the original user account information, i.e. the UAI of the driver, to the OBU 2 as its user account information, and erases the T-UAI of the fellow

passenger in step S216.

[0046] According to the present embodiment, the fellow passenger can decide whether to pay or not for the next toll way by just placing his/her mobile device 1 near the OBU 2. In the embodiment, the T-UAI is erased and the UAI of the OBU 2 is restored when the car 100 passes through the toll gate. However, the fellow passenger can enter a validity period or date in the step S202. In this case, the validity period is transmitted to the credit server 5 in the step S203, and transmitted to the ERP server 4 in the step S208, and transmitted to the management server 6 in the step S210, and transmitted to the OBU 2 in the step S212, and OBU 2 restores the UAI of the driver and erases the T-UAI when the validity period is expired.

[0047] Further, the fellow passenger may enter the number of transactions using the T-UAI of the fellow passenger. In this case, the OBU 2 restores the UAI of the driver and erases the T-UAI of the fellow passenger when the T-UAI is used for transaction by the time equal to the number of transaction entered by the fellow passenger.

[0048] Further, the fellow passenger can select toll ways, and enter the selected toll ways and the validity period in the step S202. The selected toll ways are informed to the EPR server 4, and the validity period is set to the OBU 2. In this case, the ERP server 4 charges the fellow passenger for toll fare regarding the selected toll ways by the fellow

passenger, and charges the driver for other toll fares.

[0049] In the embodiment, the T-UAI of the fellow passenger, not the actual user account information of the fellow passenger, is transmitted to the OBU 2.

With the configuration, sensitive information, i.e. user account information of the fellow passenger, can be kept secret .

[0050] Fig. 4 is a sequence diagram according to still another embodiment of the present invention. In the present embodiment, the OBU 2 has no mobile communication interface, and the management server 6 is not required.

[0051] If the fellow passenger makes payment for a toll fare, the fellow passenger makes device pairing in step S300, and the mobile device 1 obtains the OBU-ID of the OBU 2 in step S301. In step S302, the mobile device 1 displays a screen for asking the approval by the fellow passengers, and if the fellow passenger enters an input indicating approval of the payment at the upcoming toll gate, the mobile device 1 transmits a request message including the U-ID of the fellow

passenger and the OBU-ID of the OBU 2 to the credit server 5 via the network 7 in step S303. In step S 304, the credit server 5 transmits a response message

including a random value to the mobile device 1 via the network 7 for the authentication, and the mobile device 1 transmits a request message including a signature to the credit server 5 via the network 7 in step S305.

The signature is computed by the private key of the fellow passenger stored in the mobile device 1, and a set of parameters including the U-ID of the fellow passenger, the OBU-ID of the OBU 2, the random value, and optionally more parameters are provided as an input for the signature computation. The credit server 5 verifies the signature transmitted in the step S305 using the public key of the fellow passenger.

[ 0052 ] If the authentication is successful, the credit server 5 generates temporary user account

information ( T-UAI ) of the fellow passenger in step S306, and transmits an acknowledgement message

including the T-UAI of the fellow passenger to the mobile device 1 in step S307. In response to a

reception of the acknowledgement message from the credit server 5, the mobile device 1 instructs the fellow passenger to place the mobile device 1 near the OBU 2. By placing the mobile device 1 within the communication range with the OBU 2, the mobile device 1 transmits a change request message including the T-UAI of the fellow passenger to the OBU 2 in step S308.

[0053] Upon a reception of the change request message from the mobile device 1, the OBU 2 set the T- UAI of the fellow passenger to the OBU 2 as its user account information in step S309. In step S310, the car 100 passes through the toll gate, and the ERP device 3 installed on the toll gate that the car 100 passes through obtains the T-UAI of the fellow

passenger stored in the OBU 2. Then ERP device 3 reports the obtained T-UAI to the ERP server 4 in step S311. In step S313, the settlement is performed between the toll way operator and the credit card company. Since the T-UAI is used for the transaction at the step S310, the toll fare is charged to the fellow passenger. Since the OBU 2 has used the T-UAI of the fellow passenger for the transaction in the step S310, the OBU 2 restores the original user account information, i.e. the UAI of the driver, to the OBU 2 as its user account information, and erases the T-UAI of the fellow passenger in step S312.

[0054] According to the present embodiment, the fellow passenger can decide whether to pay or not for the next toll way by just placing his/her mobile device 1 near the OBU 2. In this embodiment, the mobile communication interface is not required for the OBU 2, and the management server 4 is not required. The same modification described in reference to Fig. 3 can be applied to the present embodiment.

[0055] Fig. 5 is an exemplary block diagram of a mobile device according to an embodiment of the present invention.

[0056] A storage unit 11 stores the U-ID of the fellow passenger and a private key of the fellow passenger. A NFC unit 12 is a communication unit according to a near field communication technique, and can communicate with the OBU 2. A mobile communication unit 13 is a communication unit according to, for example, 3GPP standard, and can communicate with servers in the pricing system 8 via the network 7.

[0057] The control unit 14 controls the mobile device 1, and performs communications described using Figs. 2 to 4.

[0058] The storage unit 11 may include a non^¬ volatile memory such as a flash-memory. The NFC unit 12 and the mobile communication unit 13 may include an ASIC (Application Specific Integrated Circuits), a DSP (Digital Signal Processor) and/or a CPU (Central

Processing Unit) with program for DSP/CPU. Further the NFC unit 12 and the mobile communication unit 13 may include transceiver and antenna for transmitting and receiving wireless signals. The control unit 14 may include a CPU and/or DSP with program for CPU/DSP. The control unit 14 may further include peripheral circuits.

[0059] Fig. 6 is an exemplary block diagram of an on-board unit according to an embodiment of the present invention.

[0060] A storage unit 21, which is embedded into the OBU 2 stores the UAI of the driver and the OBU-ID of the OBU 2. A NFC unit 22 is a communication unit according to a near field communication technique, and can communicate with the mobile device 1. A mobile communication unit 23 is a communication unit according to, for example, 3GPP standard, and can communicate with servers in the pricing system 8 via the network 7. The DSRC unit 25 is a communication unit according to a dedicated short range communication technique, and can communicate with the ERP device 3 in the pricing system 8.

[0061] The control unit 24 controls the OBU 2, and performs communications described using Figs. 2 to 4.

[0062] The storage unit 21 may include a non^¬ volatile memory and be tamper-resistant to protect the secure information such as the user account information and the private key. The NFC unit 22, the mobile communication unit 23 and the DSRC unit 25 may include an ASIC (Application Specific Integrated Circuits), a DSP (Digital Signal Processor) and/or a CPU (Central Processing Unit) with program for DSP/CPU. Further the NFC unit 22, the mobile communication unit 23 and the DSRC unit 25 may include transceiver and antenna for transmitting and receiving wireless signals. The control unit 24 may include a CPU and/or DSP with program for CPU/DSP. The control unit 14 may further include peripheral circuits.

[0063] Fig. 7 is an exemplary block diagram of a credit server according to an embodiment of the present invention.

[0064] A storage unit 31 stores a relation of user identification information (U-ID) and user account information (UAI) for each user. A control unit 32 performs communications described using Figs. 2 to 4.

[0065] In the embodiment, the ERP server 4, the credit server 5 and the management server 6 are

different. However, two or all servers function may be implemented in one server. Further, each server can be realized by a plurality of servers.

[0066] Many modifications and variations will be apparent to those of ordinary skilled in the art. The present embodiments were chosen and described in order to best explain the principles of the invention. It should be understood that the present invention is not limited to the specific embodiments described in the specification, except as defined in the appended claims .

[0067] Further, the invention may be achieved by a program, which realizes the functions of the above embodiments. Programs defining functions on the invention can be delivered to servers 4, 5 and 6, the mobile device 1 and/or the OBU 2 using non-transitory computer-readable storage media or via a network. It should be understood that the invention may be

implemented by software, hardware or a combination of software and hardware.

Claims

1. A mobile device (1) comprising:

a storage unit (11) configured to store user identification information of a first user;

a first communication unit (12) configured to communicate with a terminal (2) having account

information of a second user, the account information being transmitted to a pricing system (8) by the terminal (2) for a transaction;

a second communication unit (13) configured to communicate with the pricing system (8) via a network ( 7 ) ; and

a control unit (14) configured to obtain terminal identification information of the terminal (2) from the terminal (2) using the first communication unit (12), wherein the control unit (14) is further

configured to transmit the user identification

information of the first user and the terminal

identification information of the terminal (2) to the pricing system (8) using the second communication unit (13) such that the first user makes payment for the transaction on behalf of the second user.

2. The mobile device (1) according to claim 1, wherein the control unit (14) is further configured to prompt the first user to enter an amount of money that the first user makes payment, and to transmit the amount of money to the pricing system (8) .

3. The mobile device (1) according to claim 1 or 2, wherein the control unit (14) is further configured to prompt the first user to enter a sub ect for the transaction that the first user makes payment, and to transmit the sub ect to the pricing system (8) .

4. The mobile device (1) according to claim 1, wherein the user identification information of the first user and the terminal identification information are transmitted to the pricing system (8) so that the pricing system (8) changes the account information of the second user stored in the terminal (2) to account information of the first user.

5. The mobile device (1) according to claim 4, wherein the control unit (14) is further configured to receive the account information of the first user from the pricing system (8) using the second communication unit (13), and to transmit the account information of the first user to the terminal (2) using the first communication unit (12).

6. The mobile device (1) according to claim 4 or 5, wherein the control unit (14) is further configured to transmit the user identification information of the first user and the terminal identification information to the pricing system (8) if the first user enters an input indicating an approval of payment on behalf of the second user.

7. The mobile device (1) according to any one of claims 4 to 6, wherein the account information of the first user has a validity period or a number of times that the terminal (2) can use the account information of the first user.

8. A terminal (2) using account information of the terminal (2) for a transaction with a pricing system (8), comprising:

a storage unit (21) configured to store terminal identification information of the terminal (2) and first account information; and

a control unit (24) configured to transmit the terminal identification information to a mobile device (1), and to change the account information of the terminal (2) from the first account information to second account information received from the mobile device (1) or the pricing system (8) .

9. The terminal (2) according to claim 8, wherein the control unit (24) is further configured to change the account information of the terminal (2) from the second account information to the first account

information when one transaction with the pricing system (8) using the second account information is completed.

10. The terminal (2) according to claim 8, wherein the second account information has a validly period or a number of transactions, and wherein the control unit (24) is further configured to change the account information of the terminal (2) from the second account information to the first account information when the validity period of the second account information is expired or the terminal (2) uses the second account information by times equal to the number of

transactions .

11. A server (5) used in a pricing system (8) comprising:

a storage unit (51) configured to store a

relation of user identification information and account information for each user; and

a control unit (52) configured to receive user identification information of a first user, terminal identification information of a terminal (2) having account information of a second user and a payment condition by the first user from a mobile device (1), wherein the control unit (52) is further configured to charge the first user instead of the second user for a transaction performed using the account information of the second user between the terminal (2) and the pricing system (8) based on the payment condition.

12. A server (5) used in a pricing system (8) comprising:

a storage unit (51) configured to store a

a control unit (52) configured to receive user identification information of a first user, terminal identification information of a terminal (2) having account information of a second user and a payment condition by the first user from a mobile device (1), and to transmit account information of the first user, the terminal identification information of the terminal (2) and the payment condition by the first user to another server (4) in the pricing system (8) such that the pricing system (8) charges the first user instead of the second user for a transaction performed using the account information of the second user between the terminal (2) and the pricing system (8) based on the payment condition.

13. A server (5) used in a pricing system (8) comprising:

a storage unit (51) configured to store a

relation of user identification information and account information for each user;

a control unit (52) configured to receive user identification information of a first user and terminal identification information of a terminal (2) having account information of a second user from a mobile device (1), and to generate temporary user account information of the first user to set the temporary user account information to the terminal (2) in response to a reception of the user identification information of the first user.

14. A method performed by a mobile device (1) having user identification information of a first user, the method comprising the steps of:

obtaining (S101, S201, S301) terminal

identification information of a terminal (2) from the terminal (2) using a first communication unit (12), the terminal (2) having account information of a second user, the account information being transmitted to a pricing system (8) by the terminal (2) for a

transaction; and

transmitting (S103, S203, S303) the user

identification information of the first user and the terminal identification information of the terminal (2) to the pricing system (8) using a second communication unit (13) such that the first user makes payment for the transaction on behalf of the second user.

15. The method according to claim 14, further

comprising the steps of:

prompting (SI 02) the first user to enter an amount of money or a sub ect for the transaction that the first user makes payment; and

transmitting (S103) the amount of money or the sub ect to the pricing system (8).

16. The method according to claim 14, further

comprising the steps of:

receiving (S307) account information of the first user from the pricing system (8) using the second communication unit (13); and

transmitting (S308) the account information of the first user to the terminal (2) using the first communication unit (12) .

17. A method performed by a terminal (2) using account information of the terminal (2) for a

transaction with a pricing system (8), the terminal (2) storing terminal identification information of the terminal (2) and first account information as the account information of the terminal (2), the method comprising the steps of:

transmitting (S200, S300) the terminal

identification information to a mobile device ( 1 ) ;

receiving (S212, S308) second account information from the mobile device (1) or the pricing system (8); and

changing (S213, S309) the account information of the terminal (2) from the first account information to the second account information; and

transmitting (S214, S310) the second account information to the pricing system (8) for a transaction.

18. The method according to claim 17, further

comprising the step of changing (S216, S312) the

account information of the terminal (2) from the second account information to the first account information when one transaction with the pricing system (8) using the second account information is completed.

19. The method according to claim 17, wherein the second account information has a validly period or a number of transactions, and the method further

comprising the step of changing the account information of the terminal (2) from the second account information to the first account information when the validity period of the second account information is expired or the terminal (2) uses the second account information by times equal to the number of transactions.

20. A method performed by a server (5) in a pricing system (8) comprising the steps of:

receiving (S207) user identification information of a first user and terminal identification information of a terminal (2) having account information of a second user from a mobile device (1), and

generating temporary user account information of the first user to set the temporally user account information to the terminal (2).