JP2015225395A - Electronic apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow an electronic apparatus to be recognized as a device that has requested a particular service even if the residual quantity of a battery in the electronic apparatus has dropped after requesting the particular service.SOLUTION: An electronic apparatus powered by a battery includes: proximity wireless communication means comprising storage means enabling read-out from the outside; communication means for communicating with a communication device and transmitting an authentication code for prescribed communication contents to the communication device; and means for storing the authentication code in the storage means in response to the residual quantity of the battery being a prescribed quantity or less.

Description

  The present invention relates to an electronic device.

  In recent years, it has become possible to place a system for ordering articles via a wireless local area network (LAN) using a mobile terminal such as a smartphone. In addition, it has become possible to authenticate with NFC (Near Field Communication) when purchasing goods.

  For example, when a mobile terminal receives a specific service such as when an article is ordered by a wireless LAN or the like after requesting a specific service such as ordering an article, the mobile terminal uses NFC to receive a specific service. A system that authenticates that a device that requested a specific service is considered. Patent Document 1 discloses a method of transmitting fixed identification information and document data to a server via a wireless LAN or the like, and later authenticating the device by another communication means.

JP 2012-138074 A

  However, in the conventional method, when the mobile terminal places an order for the article, the remaining battery level of the mobile terminal remains. However, when the article is taken to the ordering party and authenticated by NFC, the remaining battery capacity of the mobile terminal is exceeded. A situation where authentication by NFC cannot be performed may occur due to the decrease. In this case, for example, when the article is taken to the ordering party, it cannot be recognized that the mobile terminal is an apparatus used for ordering the article. For this reason, the user may not be able to receive the article even though the order of the article has been completed using the mobile terminal.

  Accordingly, an object of the present invention is to make it possible to recognize that an electronic device is a device that has requested a specific service even if the remaining battery level of the electronic device has decreased after requesting a specific service. To do.

  An electronic device according to the present invention is an electronic device operated by a battery, and communicates with a proximity wireless communication unit having a storage unit readable from the outside, a communication device, and an authentication code for predetermined communication. Communication means for transmitting to the communication device, and means for storing the authentication code in the storage means in response to the remaining amount of the battery being below a predetermined amount.

  According to the present invention, it is possible to recognize that an electronic device is a device that has requested a specific service even if the remaining battery level of the electronic device has decreased after requesting a specific service. is there.

It is a schematic block diagram of the system to which a present Example is applied. It is a schematic block diagram of an embodiment of an electronic device according to the present invention. It is a schematic block diagram of the communication apparatus of the system shown in FIG. It is a schematic diagram which shows the data structural example of the authentication code in a present Example. It is explanatory drawing of the data reading / writing of a NFC tag. It is a flowchart which shows an example of the radio | wireless communication process of the electronic device in a present Example. It is a flowchart of the process example of the server in a present Example. It is a flowchart of an example of the radio | wireless communication process of the communication apparatus in a present Example. It is a flowchart which shows an example of the near field communication process of the communication apparatus in a present Example. It is a flowchart which shows an example of the near field communication process of the electronic device in a present Example. It is a flowchart which shows another example of the radio | wireless communication process of an electronic device.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a configuration diagram showing an environment in which an electronic device is used in an embodiment of the present invention. In addition, the portable terminal 100 is mentioned and demonstrated below as an example of the electronic device in an Example. The portable terminal 100 can communicate with the server 300 via a wireless communication path (001) such as a wireless LAN or Bluetooth (registered trademark), and can communicate with the communication device 200 via a close proximity wireless communication path (003) such as NFC. The communication device 200 can communicate with the server 300 via a communication path (002) of wireless communication such as wireless LAN or Bluetooth, or wired communication such as wired LAN. As for NFC, the mobile terminal 100 includes an NFC-compatible wirelessly readable / writable tag (NFC tag), and the communication device 200 includes a reader / writer device that can read and write data of the NFC tag of the mobile terminal 100.

  The portable terminal 100 can receive a predetermined service by communicating with the server 300 through the wireless communication path (001). The server 300 stores data sent from the mobile terminal 100 and the communication device 200 in an internal storage and responds in response to various inquiries. In response, the server 300 transmits the requested data to the device designated by the requester.

  FIG. 2 is a schematic configuration block diagram of the mobile terminal 100. With reference to FIG. 2, the structure of the portable terminal 100 is demonstrated.

  Reference numeral 101 denotes a control unit. The control unit 101 is configured by a CPU, for example, and controls each unit of the mobile terminal 100. The ROM for storing the program belongs to the control unit 101, and is omitted in FIG.

  Reference numeral 102 denotes a RAM, which is a memory mainly used as a work area for the control unit 101 and a temporary buffer area for data. Programs such as an OS (Operation System) and applications are expanded on the RAM 102 and executed by the control unit 101.

  Reference numeral 103 denotes an imaging unit. The imaging unit 103 includes an optical lens, a CMOS image sensor, a digital image processing unit, and the like, and includes means for generating image data corresponding to an optical image generated on the CMOS image sensor by the optical lens. Image data acquired by the imaging unit 103 is temporarily stored in the RAM 102 and processed based on the control of the control unit 101. The processed image data is recorded on a recording medium by the recording unit 106 and transmitted to an external device by the wireless communication unit 107, for example. The imaging unit 103 also includes a lens control unit, and the lens control unit controls zoom, focus, aperture adjustment, and the like of the optical lens based on a command from the control unit 101.

  Reference numeral 104 denotes a display unit. The display unit 104 is configured by a liquid crystal panel, an organic EL panel, or the like, and displays an operation screen, image data generated by the imaging unit 103, and the like based on an instruction from the control unit 101.

  Reference numeral 105 denotes an operation unit. The operation unit 105 is configured by a button, a cross key, a touch panel, a remote controller, or the like, and accepts a user operation instruction. The operation information input from the operation unit 105 is transmitted to the control unit 101, and the control unit 101 controls each unit of the mobile terminal 100 based on the operation information.

  Reference numeral 106 denotes a recording unit. The recording unit 106 stores data in a recording medium or reads data from the recording medium based on an instruction from the control unit 101. The recording medium is composed of, for example, a built-in flash memory, a built-in hard disk, or a memory card that can be attached to and detached from the portable terminal 100.

  Reference numeral 107 denotes a wireless communication unit. The wireless communication unit 107 includes processing hardware and the like for performing communication such as an antenna and a wireless LAN, and performs, for example, IEEE 802.11n / a / g / b wireless LAN communication. The communication unit 207 is connected to an external access point via a wireless LAN, and can communicate with other communication devices via the access point.

  Reference numeral 108 denotes an internal bus. The internal bus 108 is a bus for connecting each part in the mobile terminal 100 to each other.

  Reference numeral 109 denotes an NFC communication unit. The NFC communication unit 109 includes an NFC tag and an antenna for NFC communication. The NFC communication unit 109 has a communication function in each mode of a reader / writer mode, a peer mode, and a card emulation mode (tag mode).

  When the NFC communication unit 109 is an initiator in the reader / writer mode or the peer mode, the NFC communication unit 109 performs near field communication with an NFC tag or the like by outputting an RF signal from the antenna, and the NFC tag ( Read / write data to / from memory.

  When the NFC communication unit 109 is in the peer mode target or in the card emulation mode (tag mode), the NFC communication unit 109 receives signals from other NFC-compatible devices via an antenna and stores them in the RAM 102. Return the necessary response signal.

  110 is a battery. Using the power of the battery 110, the control unit 101 can control each unit of the mobile terminal 100. Further, even when the remaining amount of the battery 110 is reduced to such an extent that it cannot be supplied to either the imaging unit 103 or the wireless communication unit 107, the NFC communication unit 109 can operate in the card emulation mode (tag mode). That is, the NFC reader / writer can access the NFC tag built in the NFC communication unit 109 by proximity wireless communication, reads data from the NFC tag (memory built in), and reads data from the NFC tag (memory built in). Can write.

  FIG. 3 is a block diagram of a schematic configuration of the communication apparatus 200. The configuration of the communication apparatus 200 will be described with reference to FIG.

  Reference numeral 201 denotes a control unit. The control unit 201 is configured by a CPU, for example, and controls each unit of the communication device 200. Further, the ROM for storing the program belongs to the control unit 201 and is omitted in FIG.

  A RAM 202 is a memory mainly used as a work area for the control unit 201 and a temporary buffer area for data.

  Reference numeral 203 denotes a display unit. The display unit 203 is configured by a liquid crystal panel, an organic EL panel, or the like, and displays an operation screen or the like based on an instruction from the control unit 201.

  Reference numeral 204 denotes an internal bus. The internal bus 204 is a bus for connecting each part in the communication device 200 to each other.

  Reference numeral 205 denotes an operation unit. The operation unit 205 includes a button, a cross key, a touch panel, a remote control, and the like, and accepts user operation instructions. The operation information input from the operation unit 205 is transmitted to the control unit 201, and the control unit 201 executes control of each unit based on the operation information.

  Reference numeral 206 denotes a recording unit. The recording unit 206 reads data from the recording medium or writes data to the recording medium based on an instruction from the control unit 201. The recording medium is composed of, for example, a built-in flash memory, a built-in hard disk, or a removable memory card.

  Reference numeral 207 denotes a communication unit. The communication unit 207 includes hardware for performing at least one communication of a wireless LAN and a wired LAN. The wireless LAN corresponds to, for example, the IEEE 802.11n / a / g / b system. The communication unit 207 is connected to an external access point via a wireless LAN, and can communicate with other communication devices via the access point. In addition, the communication unit 207 performs communication via an external router or a switching hub using an Ethernet (registered trademark) cable in a wired LAN.

  Reference numeral 208 denotes an NFC communication unit. The NFC communication unit 208 includes an NFC tag and an antenna and a resonance circuit for NFC communication. The NFC communication unit 208 has a communication function in each operation mode of a reader / writer mode, a peer mode, and a card emulation mode (tag mode).

  When the NFC communication unit 208 is an initiator in the reader / writer mode or the peer mode, the NFC communication unit 208 performs near field communication with an NFC tag or the like by outputting an RF signal from the antenna, and the NFC tag ( Data can be read and written to the memory.

  When the NFC communication unit 208 is in the peer mode target or card emulation mode (tag mode), the NFC communication unit 208 receives a signal from another NFC device by the antenna and stores it in the RAM 202, and a necessary response. Reply signal.

  FIG. 4 shows a data configuration example of the authentication code 401. An authentication code 401 used in wireless communication or proximity wireless communication is composed of a device identification ID 402, a request ID 403, and a manufacturer ID 404, and serves as identification information that identifies the content of communication with the communication device 200 and the portable terminal 100. The device identification ID 402 is ID information for identifying the mobile terminal 100, and may be a randomly generated value or a unique identification value. The request ID 403 is identification information for identifying a request for a specific service. The manufacturer ID 404 is a unique identifier that identifies the manufacturer of the mobile terminal 100. The authentication code 401 is a code generated using the terminal ID and the request ID, and may be a code unique to the terminal ID and the request ID.

  FIG. 5 shows a configuration example of the NFC tag of the mobile terminal 100. At least one of the control unit 101 and the NFC communication unit 109 can read / write data from / to the NFC tag. Even when the remaining amount of the battery 110 is empty, both the control unit 101 and the NFC communication unit 109 can read and write the data of the NFC tag using the carrier power supplied from the NFC reader / writer. The authentication code 401 shown in FIG. 4 is written at a predetermined address of the NFC tag by the control unit 101 and read from the predetermined address by the NFC communication unit 109.

  FIG. 6 shows an example of wireless communication processing in the mobile terminal 100. With reference to FIG. 6, the ordering process in the portable terminal 100 will be described. The control unit 101 executes a control program for realizing the flowchart illustrated in FIG. 6 in a state where the power of the mobile terminal 100 is on.

  In step S <b> 601, the control unit 101 determines whether a processing command that requires communication using the wireless communication unit 107 has been received. The processing command includes a user input to the control unit 101 by the operation unit 105 and an instruction from an external device via the wireless communication unit 107. For example, there may be a case where order processing is performed via wireless communication. When the control unit 101 receives a processing command that requires communication using the wireless communication unit 107 (Yes in S601), the control unit 101 proceeds to S602. If the processing command that requires communication is not received using the wireless communication unit 107 (No in S601), the control unit 101 repeatedly performs S601.

  In step S <b> 602, the control unit 101 determines whether the processing instruction received in step S <b> 601 is processing that requires authentication by the NFC communication unit 109. For example, the process that requires authentication by the NFC communication unit 109 is a request for a specific service in the NFC communication unit 109 when a service is actually received after a request for the specific service is made via the wireless communication unit 107. It is assumed that the user has been authenticated. When the process is a process that requires authentication by the NFC communication unit 109 (Yes in S602), the control unit 101 proceeds to S611. If the process does not require authentication by the NFC communication unit 109 (No in S602), the control unit 101 proceeds to S603.

  In step S <b> 603, the control unit 101 controls the wireless communication unit 107 to perform a predetermined wireless communication process, and ends the process illustrated in the flowchart in FIG. 6.

  In step S611, the control unit 101 causes the NFC communication unit 109 to operate in the P2P mode, and proceeds to step S604.

  In step S604, as illustrated in FIG. 4, the control unit 101 generates the authentication code 401 based on the terminal ID (device identification ID 402 and manufacturer ID 404) and the request ID 403, and proceeds to step S606.

  In step S606, the control unit 101 transmits the generated authentication code 401 to the server 300 via the wireless communication unit 107, and the process proceeds to step S607.

  In step S <b> 607, the control unit 101 determines whether a response to the transmission of the authentication code has been received via the wireless communication unit 107. When the control unit 101 receives a response to the transmission of the authentication code 401 within a predetermined time (Yes in S607), the control unit 101 proceeds to S610. When the control unit 101 does not receive a response to the transmission of the authentication code 401 within a predetermined time (No in S607), the control unit 101 ends the processing illustrated in the flowchart in FIG.

  In step S610, the control unit 101 determines whether the remaining amount of the battery 110 is equal to or less than a predetermined amount. The predetermined value may be, for example, a remaining amount value corresponding to 1/10 or less of the total capacity of the battery 110. The predetermined value may be a value corresponding to the remaining amount of the battery 110 that can supply power necessary for the operation of the wireless communication unit 107, for example.

  In S610, when the control unit 101 determines that the remaining amount of the battery 110 is equal to or less than the predetermined amount (Yes in S610), the control unit 101 proceeds to S608. When the control unit 101 determines that the remaining amount of the battery 110 is not less than or equal to the predetermined amount (No in S610), the process illustrated in the flowchart in FIG.

  In step S608, the control unit 101 stores the authentication code 401 generated in step S604 in the NFC tag described with reference to FIG. 5, and proceeds to step S609.

  In step S609, the control unit 101 changes the NFC communication unit 109 to the card emulation mode (tag mode), and ends the processing illustrated in the flowchart in FIG.

  FIG. 7 is a flowchart illustrating an example of communication processing in the server 300.

  In step S <b> 701, the server 300 determines whether the authentication code 401 from the mobile terminal 100 has been received. When the server 300 receives the authentication code 401 (Yes in S701), the server 300 proceeds to S702. If the server 300 has not received the authentication code 401 (No in S701), the server 300 waits for reception.

  In S <b> 702, the server 300 transmits a response indicating that the reception of the authentication code 401 is completed to the mobile terminal 100, and ends the processing illustrated in the flowchart illustrated in FIG. 7.

  FIG. 8 shows a flowchart of an example of reception processing of the authentication code 401 in the communication apparatus 200. The control unit 201 executes a control program corresponding to the flowchart shown in FIG. 8 when the communication device 200 is in the power-on state.

  In step S <b> 801, the control unit 201 determines whether the authentication code 401 has been received from the server 300 via the communication unit 207. When the control unit 201 receives the authentication code 401 (Yes in S801), the control unit 201 proceeds to S802. When the control unit 201 has not received the authentication code 401 (No in S801), the control unit 201 waits for reception.

  In step S802, the control unit 201 stores the authentication code 401 received in step S801 in the recording unit 206, and ends the processing illustrated in the flowchart in FIG.

  FIG. 9 shows a flowchart of an example of NFC authentication processing in the communication apparatus 200. With reference to FIG. 9, an authentication processing operation when the communication apparatus 200 operates as a reader / writer will be described. The control unit 201 executes a control program corresponding to the flowchart shown in FIG. 9 when the communication apparatus 200 is in a power-on state. The process shown in the flowchart in FIG. 9 is executed in parallel with the process shown in the flowchart in FIG.

  In step S <b> 901, the control unit 201 determines whether an authentication code has been received via the communication unit 207. When the control unit 201 receives the authentication code (Yes in S901), the control unit 201 proceeds to S902. When the control unit 201 has not received the authentication code (No in S901), the control unit 201 repeatedly performs S901.

  In step S902, the control unit 201 controls the NFC communication unit 208 to make an inquiry as to whether an NFC-compatible device exists. For example, the NFC communication unit 208 transmits a SENSB_REQ command for Type B, and a SENSF_REQ command for Type F. If there is an NFC-compatible device, the NFC communication unit 208 receives a SENSB_RES response if it is Type B, and transfers it to the control unit 201 if it is Type F. If there is an NFC-compatible device (Yes in S902), the control unit 201 proceeds to S911. When there is no NFC-compatible device (No in S902), the control unit 201 repeatedly performs S902.

  In S911, when the control unit 201 determines from the command response in S902 that the NFC-compatible device found in S902 is in the card emulation (tag) mode (Yes in S911), the control unit 201 proceeds to S903. If the control unit 201 determines from the command response in S902 that the NFC-compatible device found in S902 is not in the card emulation (tag) mode (No in S911), the process proceeds to S912.

  In step S903, the control unit 201 transmits a read command to the address of the authentication code in order to control the NFC communication unit 208 and acquire the authentication code 401. Thereafter, the control unit 201 receives a read command response via the NFC communication unit 208 and stores the authentication code in the RAM 202. The control unit 201 proceeds to S904.

  In step S <b> 913, the control unit 201 transmits a command corresponding to the P2P mode for acquiring the authentication code 401 by controlling the NFC communication unit 208. Thereafter, the control unit 201 receives a response to the command corresponding to the P2P mode via the NFC communication unit 208 and stores the authentication code in the RAM 202. The control unit 201 proceeds to S904.

  In step S <b> 904, the control unit 201 determines whether the authentication code stored in the RAM 202 matches the authentication code 401 of the mobile terminal 100 stored in the recording unit 206. If the control unit 201 determines that the authentication code stored in the RAM 202 is the registered authentication code 401 (Yes in S904), the control unit 201 completes the authentication and proceeds to S905. When the control unit 201 determines that the authentication code stored in the RAM 202 is not the registered authentication code 401 (No in S904), the control unit 201 returns to S902.

  In step S <b> 905, since the control unit 201 has confirmed the registered authentication code, the control unit 201 deletes or invalidates the authentication code of the NFC tag of the mobile terminal 100 via the NFC communication unit 208. The control unit 201 proceeds to S906.

  In step S906, the control unit 201 exchanges NFC application layer communication using an NDEF (NFC Data Exchange Format) data method in accordance with a desired application. For example, if the service requested by the mobile terminal 100 is an order for an article, the settlement of the order for the article is performed. After the processing of S906, the control unit 201 ends the processing shown in the flowchart in FIG.

  FIG. 10 shows a flowchart of an example of the authentication process of the mobile terminal 100 as the NFC card emulation mode (tag mode). Is stored in the recording unit 106. When the power of the mobile terminal 100 is on, or when the control unit 101 receives NFC carrier power transmitted from the communication device 200 via the NFC communication unit 109 of the mobile terminal 100, the control unit 101 performs the flowchart illustrated in FIG. The control program to be realized is executed.

  In step S <b> 1001, the control unit 101 determines whether a read command for the authentication code on the NFC tag has been received via the NFC communication unit 109. When the control unit 101 determines that a read command for the authentication code on the NFC tag has been received (Yes in S1002), the process proceeds to S1002. When the control unit 101 does not receive a read command for the authentication code on the NFC tag (No in S1002), the control unit 101 repeatedly performs S1002.

  In S1002, the control unit 101 returns the authentication code 401 on the NFC tag as a response to the authentication code read command via the NFC communication unit 109, completes the authentication, and proceeds to S1003.

  In S1003, the communication apparatus 200 invalidates the authentication code 401 on the NFC tag of the NFC communication unit 109, and the control unit 101 proceeds to S1004.

  In step S1004, the control unit 101 exchanges NFC application layer communication using an NDEF (NFC Data Exchange Format) data method in accordance with a desired application. For example, if the service requested by the mobile terminal 100 is an order for an article, settlement of the order for the article is performed. After the process of S1004, the control unit 101 ends the process shown in the flowchart in FIG.

  As described above, the NFC communication unit 109 of the mobile terminal 100 initially operates in the NFC P2P mode, thereby enabling P2P communication with other NFC devices. On the other hand, even if the remaining amount of the battery 110 of the mobile terminal 100 is empty, the NFC communication unit 109 of the mobile terminal 100 operates as an NFC card emulation mode (tag mode). Accordingly, the control unit 101 of the mobile terminal 100 can receive the NFC carrier power transmitted from the communication device 200 (NFC reader / writer) and execute the process illustrated in FIG. That is, the authentication code 401 can be used as an NFC card emulation mode (tag mode) even when the remaining battery 110 of the mobile terminal 100 is empty. As a result, it is possible to authenticate that the mobile device 100 and the communication device 200 are the same device by associating the wireless communication processing with the proximity wireless communication processing such as NFC.

  Although the communication configuration via the server 300 has been described here, various data may be exchanged directly between the mobile terminal 100 and the communication device 200 without going through the server 300.

  FIG. 11 shows a flowchart of an example of another wireless communication process of the mobile terminal 100. The control unit 101 executes a control program that realizes the flowchart illustrated in FIG. 11 in a state where the power of the mobile terminal 100 is on.

  In the second embodiment, S1101 to S1107 and S1103 in FIG. 11 are the same processes as S601 to S607 and S603 in FIG.

  In S1107, when the control unit 101 receives a response to the transmission of the authentication code 401 within a predetermined time (Yes in S1107), the control unit 101 proceeds to S1110.

  In S1110, the control unit 101 determines whether or not the remaining amount of the battery 110 is equal to or less than a predetermined amount, similar to S610.

  In S1110, when the control unit 101 determines that the remaining amount of the battery 110 is equal to or less than the predetermined amount (Yes in S1110), the control unit 101 proceeds to S1108. If the control unit 101 determines that the remaining amount of the battery 110 is not less than or equal to the predetermined amount (No in S1110), the control unit 101 proceeds to S1112.

  In step S1108, the control unit 101 stores the authentication code 401 generated in step S1104 in the NFC tag described with reference to FIG. 5, and proceeds to step S1109.

  In step S1109, the control unit 101 changes the NFC communication unit 109 to the card emulation mode (tag mode), and proceeds to step S1113.

  In step S1112, the control unit 101 causes the NFC communication unit 109 to operate in the P2P mode, and proceeds to step S1113.

  In step S <b> 1113, the control unit 101 transmits the mode of the NFC communication unit 109 to the server 300 via the wireless communication unit 107. When the process proceeds to S1113 via the process of S1112, the NFC communication unit 109 notifies the server 300 that it is in the P2P mode. On the other hand, when the process proceeds to S1113 via the process of S1109, the NFC communication unit 109 notifies the server 300 that the card emulation mode (tag mode) is set. Through the process of S1113, the server 300 can know the NFC mode of the mobile terminal 100 in advance.

  After the process of S1113, the control unit 101 returns to S1110.

  As described above, in the process shown in FIG. 11, the control unit 101 periodically checks the remaining amount of the battery 110, and sets the mode of the NFC communication unit 109 between the P2P mode and the card emulation mode according to the remaining amount of the battery 110. Switch with.

  The portable terminal 100 can initially perform P2P communication with other NFC devices by operating in the P2P mode.

  Even when the battery 110 of the mobile terminal 100 is empty, the NFC carrier power is received from the communication device 200 (NFC reader / writer) by operating as the card emulation mode (tag mode), and the control unit 101 can execute the processing shown in FIG. That is, even if the remaining battery 110 of the mobile terminal 100 is empty, the authentication code can be used as an NFC card emulation mode (tag mode). Thereby, it can authenticate that it is the same apparatus by associating the wireless communication processing and the proximity wireless communication processing such as NFC between the mobile terminal 100 and the communication device 200.

  (Other Embodiments) The portable terminal 100 and the communication device 200 described above are only one embodiment for explaining the present invention. For example, each of the mobile terminal 100 and the communication device 200 may be configured by a combination of a plurality of individual devices. When the operation mode of the NFC communication unit 109 is changed, the portable terminal 100 may notify the communication device 200 of the operation mode change or the changed operation mode each time or when necessary.

  The processes and functions of the above-described embodiments can also be realized by a computer program. In this case, the computer program according to the present invention can be executed by a computer (including a CPU and the like), and realizes various functions described in the embodiments.

  It goes without saying that the computer program according to the present invention may realize various processes and functions described in the embodiments using an OS (Operating System) running on the computer.

  The computer program according to the present invention is read from a computer-readable recording medium and executed by the computer. As the computer-readable recording medium, a hard disk device, an optical disk, a CD-ROM, a CD-R, a memory card, a ROM, or the like can be used. The computer program according to the present invention may be provided from an external device to a computer via a communication interface and executed by the computer.

Claims (9)

An electronic device powered by a battery,
Proximity wireless communication means comprising externally readable storage means;
Communication means for communicating with a communication device and transmitting an authentication code to the communication device for predetermined communication content;
An electronic apparatus comprising: means for storing the authentication code in the storage means when the remaining amount of the battery becomes equal to or less than a predetermined amount.   The electronic device according to claim 1, wherein the proximity wireless communication unit is a non-contact communication unit compatible with NFC.   The electronic device according to claim 1, wherein the proximity wireless communication unit operates in an NFC P2P mode in the initial stage.   4. The electronic device according to claim 1, wherein the proximity wireless communication unit operates in a card emulation mode by storing the authentication code in the storage unit. 5.   The electronic device according to claim 4, wherein the proximity wireless communication unit switches to a P2P mode when the remaining amount of the battery exceeds a predetermined amount.   5. The electronic apparatus according to claim 4, wherein the close proximity wireless transfer means is operable with carrier power of an external reader / writer in the card emulation mode.   The electronic device according to claim 1, wherein the authentication code includes a terminal ID and identification information for identifying the predetermined communication content.   The electronic device according to claim 1, wherein the authentication code includes a code generated from a terminal ID and identification information for identifying the predetermined communication content.   9. The electronic apparatus according to claim 1, further comprising means for notifying the communication device of a change in operation mode of the close proximity wireless communication means via the communication means.

Images