JP5450673B2 - Electronic device and communication control method - Google Patents

Description

  The present invention relates to an electronic device that performs close proximity wireless communication and a communication control method applied to the device.

  In recent years, wireless communication such as NFC has begun to be used in IC cards, mobile phones and the like. The user can easily perform communication for authentication processing, billing, etc., simply by holding the IC card or mobile phone over the reader / writer unit of the host device.

  Recently, new proximity wireless communication technology capable of high-speed communication has begun to be developed. This new proximity wireless communication technology enables exchange of data files such as document data, image data, and audio data as well as authentication and billing services.

  Patent Document 1 discloses a command for executing transaction processing such as cash deposit and payment by short-range non-contact communication with a mobile terminal, and locking an operation function of the mobile terminal in response to completion of the transaction processing. Is disclosed. This transaction apparatus can prevent the mobile terminal from being illegally used by a third party after transaction processing.

JP 2009-140176 A

  By the way, in order to make close proximity wireless communication between devices useful, only the touch operation of bringing devices close to each other is used as a trigger, and the connection between these devices is automatically established, and data transfer between these devices is performed. Is required to start automatically.

  However, if a device is left in close proximity to another device, for example, each time the data transfer between these devices is completed, the devices are reconnected, resulting in, for example, the transfer of the same data. It is possible that the same service such as will be executed over and over again.

  The present invention has been made in consideration of the above-described circumstances, and an object thereof is to provide an electronic device and a communication control method capable of preventing the same service from being repeatedly executed by close proximity wireless communication.

In order to solve the above-described problem, in order to solve the above-described problem, an electronic device of the present invention includes a communication module that performs close proximity wireless communication, and a connection request signal during a period in which the communication module is not connected. A connection control means for transmitting and establishing a connection between the communication module and the external device in a proximity state; and when the connection is established, executing data transfer between the communication module and the external device When an event of either a communication time-out due to cancellation of the proximity state or reception of a connection release request signal from the external device occurs, a connection between the communication module and the external device is established. ; and a connection release means for releasing, said communication control means, when the connection is established, the connection release request signal causes the previous disconnection The first device connected to the communication module and the external device newly connected to the communication module are the same devices that are received and the connection is established within a predetermined time from the previous connection release. Whether or not the condition is satisfied, and when the condition is satisfied, the data transfer between the communication module and the external device is not executed, and when the condition is not satisfied, It is configured to perform data transfer between a communication module and the external device .

  According to the present invention, it is possible to prevent the same service from being repeatedly executed by close proximity wireless communication.

1 is a block diagram showing a system configuration of an electronic device according to an embodiment of the present invention. 4 is an exemplary block diagram illustrating a configuration of a communication control program used in the electronic apparatus of the embodiment. FIG. The perspective view which shows the external appearance of the electronic device of the embodiment. 2 is an exemplary diagram illustrating an example of close proximity wireless communication performed between the electronic apparatus of the embodiment and an external device. FIG. The figure which shows the example of the software air architecture for controlling proximity | contact wireless communication applied to the electronic device of the embodiment. 6 is an exemplary view for explaining an example of a device mode used in the electronic apparatus of the embodiment. FIG. 6 is an exemplary view showing an example of state transition of a communication control program used in the electronic apparatus of the embodiment. FIG. The figure for demonstrating the example in which the same service is repeatedly performed between two devices. The figure for demonstrating another example in which the same service is repeatedly performed between two devices. 6 is an exemplary view for explaining an example of a communication control operation executed by the electronic apparatus of the embodiment. FIG. 6 is an exemplary flowchart for explaining an example of a procedure of communication control processing executed by the electronic apparatus of the embodiment. 6 is an exemplary view for explaining another example of a communication control operation executed by the electronic apparatus of the embodiment. FIG. 6 is an exemplary flowchart for explaining another example of the procedure of the communication control process executed by the electronic apparatus of the embodiment.

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

  FIG. 1 shows a configuration of an electronic apparatus according to an embodiment of the present invention. The electronic device 10 is realized as, for example, a portable computer, a mobile phone, a PDA, an audio player, a TV, or the like. The electronic apparatus 10 includes a system control unit 11, a memory 12, a storage device 13, an input unit 14, a liquid crystal display (LCD) 15, a sound controller 16, a speaker 17, an indicator 18, a power supply control unit 19, and a proximity wireless communication device. 20.

  The system control unit 11 controls the operation of each unit in the electronic device 10. The system control unit 11 is connected to the memory 12, storage device 13, input unit 14, LCD 15, sound controller 16, indicator 18, power supply control unit 19, and proximity wireless communication device 20. The system control unit 11 includes a CPU 101a.

  The CPU 101a is a processor that executes an operating system and various application programs / utility programs loaded from the storage device 13 to the memory 12. The application program / utility program includes a communication control program 12a for controlling the communication operation of the close proximity wireless transfer device 20.

  The communication control program 12a increases the connection possibility between any electronic device (external device) having a close proximity wireless communication function and the close proximity wireless communication device 20, and the close proximity wireless communication device 20 and the external device are in close proximity. Even if it is left for a relatively long time, it has a communication control function for preventing the same service from being repeatedly executed.

  The storage device 13 is composed of, for example, a hard disk drive or a nonvolatile semiconductor memory. The input unit 14 is an input device for inputting data and instructions to be given to the CPU 111. The input unit 14 is realized by, for example, a keyboard, a plurality of button switches, or a pointing device.

  The LCD 15 is a display device used as a display of the electronic device 10. The sound controller 16 is a sound source circuit for outputting sound corresponding to the audio data transmitted from the CPU 101a. The sound controller 16 converts the audio data transmitted from the CPU 101 a from a digital audio signal to an analog audio signal, and outputs the analog audio signal to the speaker 17. The speaker 17 outputs a sound corresponding to the analog audio signal.

  The indicator 18 presents the status of the close proximity wireless communication executed by the close proximity wireless communication device 20 (data transfer start, data transfer end, etc.). The indicator 18 includes a light emitting unit such as an LED.

  The power supply control unit 19 supplies power to each unit in the electronic device 10 using power supplied from the outside via the AC adapter 30 or power supplied from the battery 19 b provided in the electronic device 10. . In other words, the electronic device 10 is driven by an external power source such as an AC commercial power source or a battery 19b. The AC adapter 30 can also be provided in the electronic device 10. The power control unit 19 powers on or powers off the electronic device 10 according to the operation of the power switch (P-SW) 19a by the user.

  The proximity wireless communication device 20 is a communication module that performs proximity wireless communication. The close proximity wireless transfer device 20 can communicate with another device (external device) having a close proximity wireless communication function that exists within a predetermined communication range from the close proximity wireless transfer device 20. In the wireless communication between the close proximity wireless communication device 20 and the external device, when the close proximity wireless communication device 20 and the external device are in a close proximity state, that is, the distance between the close proximity wireless communication device 20 and the external device is a communication distance ( For example, it is possible only when approaching within 3 cm). When the close proximity wireless communication device 20 and the external device approach within the communication distance, communication between the close proximity wireless communication device 20 and the external device becomes possible. Then, an operation for establishing a connection (wireless connection) between the close proximity wireless transfer device 20 and the external device is started. After the connection (wireless connection) between the devices is established, a service such as data transfer using SCSI, OBEX, or other general-purpose protocol is performed by the proximity wireless communication between the proximity wireless communication device 20 and the external device. Executed.

  In close proximity wireless communication, an induced electric field is used. For example, TransferJet can be used as the close proximity wireless communication system. TransferJet is a close proximity wireless communication method using UWB, and can realize high-speed data transfer.

  The close proximity wireless transfer device 20 is connected to the antenna 20b. The antenna 20b is an electrode called a coupler, and transmits / receives data to / from an external device by a radio signal using an induction electric field. When the external device approaches within a communication distance (for example, 3 cm) from the antenna 20b, the close proximity wireless communication device 20 and the antenna (coupler) of each external device are coupled by an induced electric field, whereby the close proximity wireless communication device 20 is connected. Wireless communication between the external device and the external device becomes possible. The close proximity wireless transfer device 20 and the antenna 20b can be realized as one module.

  Next, the configuration of the communication control program 12a will be described with reference to FIG.

  The communication control program 12a includes a connection control program 121, a connection control driver 122, and the like. The connection control driver 122 is a program for controlling (physical) connection between the close proximity wireless transfer device 20 and an external device. The connection control program 121 manages establishment and release of a connection between the close proximity wireless transfer device 20 and an external device, and controls execution of services such as data transfer between the close proximity wireless transfer device 20 and the external device. To do.

  The connection control program 121 includes a connection control unit 123, a communication control unit 124, a connection release unit 125, a negotiation stop unit 126, and the like. The connection control unit 123 is a program module for establishing a connection between the close proximity wireless transfer device 20 and an external device, for example. The connection control unit 123 detects an external device in proximity to the proximity wireless communication device 20 when the proximity wireless communication device 20 is in a disconnected state. More specifically, the connection control unit 123 transmits a connection request signal via the close proximity wireless communication device 20 while the close proximity wireless communication device 20 is in the disconnected state, and the close proximity wireless communication device 20 in the close proximity state and the external Establish a connection with the device. The communication control unit 124 determines a service to be provided by the close proximity wireless communication between the close proximity wireless communication device 20 and the external device in response to the establishment of the connection between the close proximity wireless communication device 20 and the external device. To negotiate with external devices. Then, the communication control unit 124 executes the determined service by proximity wireless communication. The connection release unit 125, when an event of occurrence of a communication timeout due to the release of the proximity state between devices or reception of a connection release request signal from an external device occurs, the close proximity wireless communication device 20 and the external device Disconnect the connection between. The negotiation stopping unit 126 establishes a connection between the close proximity wireless communication device 20 and the external device after the close connection between the close proximity wireless communication device 20 and the external device is canceled by receiving the connection release request signal from the external device. When re-established, processing for stopping execution of negotiation by the communication control unit 124 is executed.

  Next, an example of the appearance of the electronic device 10 will be described with reference to FIG. 3 assuming that the electronic device 10 is realized as a portable personal computer.

  FIG. 3 is a perspective view showing the external appearance of the electronic device 10. The electronic device 10 includes a main body 41 and a display unit 42. The display unit 42 is attached to the main body 41 so as to be rotatable between an open position where the upper surface of the main body 41 is exposed and a closed position where the upper surface of the main body 41 is covered by the display unit 42. In the display unit 42, the LCD 15 described above is provided.

  The main body 41 has a thin box-shaped housing. On the upper surface of the housing of the main body 41, a keyboard 14a, a touch pad 14b, an indicator 18, a power switch 19a, and the like are arranged.

  An upper surface of the main body 41, specifically, a part of the palm rest rest area 41 a on the upper surface of the main body 41 functions as a communication surface. That is, the proximity wireless communication device 20 and the antenna (coupler) 20 b are provided in the main body 41 so as to face the palm rest rest area 41 a on the upper surface of the main body 41. The antenna (coupler) 20b is arranged to output a radio signal (inductive electric field) to the outside via the upper surface of the main body 41 (specifically, a part of the palm rest rest area 41a on the upper surface of the main body 41). ing. A small area on the upper surface of the main body 41 facing the antenna (coupler) 20b, that is, a small area located above the antenna (coupler) 20b on the upper surface of the main body 41 is used as a communication position.

  For example, the user performs an operation (touch operation) of holding an external device having a proximity wireless communication function over a communication position in the palm rest rest area 41 a of the main body 41, thereby data between the external device and the electronic apparatus 10. A service like forwarding can be started.

  FIG. 4 shows a state of close proximity wireless communication performed between the mobile phone 50 and the electronic device 10. In the case of the mobile phone 50, for example, an antenna (coupler) for close proximity wireless communication is provided facing the back of the case. In this case, the cellular phone 50, the electronic device 10, and the cellular phone 50 are placed by holding the back surface of the casing of the cellular phone 50 over a communication position on the palm rest region of the main body 41 of the electronic device 20 (or placing the cellular phone 5 on the palm rest region). It is possible to start close proximity wireless communication.

  Next, with reference to FIG. 5, a software architecture for controlling close proximity wireless communication executed using the close proximity wireless communication device 20 will be described.

  The software architecture of FIG. 5 shows a hierarchical structure of a protocol stack for controlling close proximity wireless communication. The protocol stack includes a physical layer (PHY), a connection layer (CNL), a protocol conversion layer (PCL), and an application layer.

  The physical layer (PHY) is a layer that controls physical data transfer, and corresponds to the physical layer in the OSI reference model. Some or all of the functions of the physical layer (PHY) can also be realized using hardware in the close proximity wireless transfer device 20.

  The physical layer (PHY) converts data from the connection layer (CNL) into a radio signal. The connection layer (CNL) corresponds to the data link layer and transport layer in the OSI reference model, and controls the physical layer (PHY) to execute data communication. The connection layer (CNL) can be realized by the connection control driver 122 described above.

  The connection layer (CNL) includes a proximity wireless communication device 20 and an external device that are set in a proximity state in response to a connection request received from the protocol conversion layer (PCL) or a connection request received from an external device. A process for establishing a (physical) connection (CNL connection) is executed. Here, an example of a procedure for establishing a CNL connection between two devices (devices 1 and 2) will be described. Of the devices 1 and 2, the device on the communication start side, for example, the device 1, executes processing for wirelessly transmitting a connection request signal (C_Req). This connection request (C_Req) can also include a unique ID (UID) of the device 1. The device 2 periodically executes processing for receiving the connection request signal (C_Req). When the device 1 and the device 2 are in the proximity state, the device 2 can receive the connection request signal (C_Req) transmitted from the device 1. When receiving the connection request signal (C_Req), the device 2 wirelessly transmits to the device 1 a response signal (C_Acc) indicating acceptance of the received connection request signal (C_Req). This response signal (C_Acc) can include the unique ID (UID) of the device 2. The device 1 can receive a response signal (C_Acc) wirelessly transmitted from the device 2. As described above, the connection (CNL connection) between the device 1 and the device 2 is established by transmitting and receiving the connection request signal (C_Req) and the response signal (C_Acc) between the device 1 and the device 2.

  The protocol conversion layer (PCL) corresponds to the session layer and the presentation layer in the OSI reference model, and is located between the application layer and the connection layer (CNL). This protocol conversion layer (PCL) can be realized by the connection control program 121 described above. The protocol conversion layer (PCL) controls each application (communication program) in the application layer and controls the connection layer (CNL) in order to establish a connection between the two devices.

  More specifically, the protocol conversion layer (PCL) includes a plurality of communication adapters (PCL adapters) respectively corresponding to a plurality of types of application protocols (for example, SCSI, OBEX, and other general-purpose protocols), and a protocol conversion layer (PCL). And a PCL controller for controlling the operation. The PCL controller activates one of a plurality of communication adapters (PCL adapters) according to an application protocol (for example, SCSI, OBEX, other general-purpose protocol, etc.) corresponding to the service to be executed. The activated PCL adapter converts application program data (user data) corresponding to the PCL adapter into a specific transmission data format that can be handled by the connection layer (CNL). By this conversion processing, data transmitted / received by any application program is converted into a packet (data in a specific transmission data format) that can be handled by the connection layer (CNL). This protocol conversion layer (PCL) makes it possible to use various application protocols in near field communication.

  In this embodiment, the PCL controller realized by the connection control program 121 supports three device modes (proactive mode, reactive mode, and flexible mode) as shown in FIG. It can operate in one of the three device modes.

  The proactive mode is a mode in which a connection request signal (connection request command) is actively transmitted for the purpose of data transfer between a local device and a communication partner device. The communication partner device may be referred to as a counter device (peer device). For example, when an application program for performing data transfer or the like using near field communication is started, the device mode automatically transitions to the proactive mode. The proactive mode is a device mode that can function as a so-called master, and a device in the proactive mode can control a communication partner device and execute a service such as data transfer between the devices.

  The reactive mode is a mode for waiting for a connection request signal from a communication partner device (a device in a proactive mode or a device in a flexible mode). This reactive mode is a device mode for functioning as a so-called slave, and the device in the reactive mode is data between devices under the control of the communication partner device (proactive mode device or flexible mode device). Services such as forwarding can be performed.

  The default device mode of a mobile device such as a mobile phone that cannot be driven by an external power supply is set to a reactive mode in order to reduce its power consumption. When an application program on the mobile device is activated by a user operation, the mobile device can automatically transition from the reactive mode to the proactive mode.

  The device set to the proactive mode transmits a connection request signal C_Req. On the other hand, the device in the reactive mode receives the connection request signal C_Req from the communication partner device (the device in the proactive mode or the device in the flexible mode), but does not transmit the connection request signal C_Req. Few.

  The flexible mode is a mode in which a connection request signal C_Req is actively transmitted for the purpose of connection between a local device and a communication partner device. This flexible mode is a mode in which the device mode of the local device can be automatically changed to the proactive mode or the reactive mode in accordance with the device mode (proactive mode or reactive mode) of the communication partner device.

  The flexible mode device transitions to the reactive mode if the communication partner device is in the proactive mode, and transitions to the proactive mode if the communication partner device is in the reactive mode. The transition to the proactive mode or the reactive mode is performed, for example, after a CNL connection between devices is established.

  For example, the default device mode of a device such as a personal computer that can be driven by an external power source such as an AC adapter power source is the flexible mode. The device in the flexible mode can transmit the connection request signal C_Req. As a result, for example, even when the user brings the mobile phone close to a personal computer (flexible mode device) without operating the mobile phone application, the connection between the devices can be established. Services such as data transfer between these devices can be executed under the control of the personal computer.

  The combinations between connectable devices are (1) a combination of a proactive mode device and a reactive mode device, (2) a combination of a proactive mode device and a flexible mode device, and (3) a flexible mode device. Only a combination of devices in reactive mode. The default device mode for each device is either reactive mode or flexible mode.

  Next, status transition of the PCL controller realized by the connection control program 121 of this embodiment will be described with reference to FIG.

The PCL controller transitions to one of three states: an unconnected state 61, a connecting state 62, and a connected state 63. The unconnected state 61 is a state before the devices are brought close to each other, in other words, a state in which the connection between the close proximity wireless communication device 20 and any external device is not established. When the close proximity wireless transfer device 20 receives a connection request signal (C_Req) or a response signal (C_Acc) from an external device, the state of the PCL controller transitions to the connecting state (connecting) 62. The connecting state (connecting) 62 is CNL. A state that has established a connection. When the establishment of the CNL connection is completed, the state of the PCL controller transitions to a connected state (connected) 63. In the connected state (connected) 63, the PCL controller starts a control sequence including three phases of authentication, negotiation, and service execution. In other words, the PCL controller first authenticates the communication partner device in the authentication phase, and enters the negotiation phase when the authentication is successful. In the negotiation phase, the PCL controller negotiates with a communication partner device and determines a service to be provided. If the negotiation is successful, the PCL controller enters the service execution phase. The PCL controller executes the service determined by the negotiation in the service execution phase.

  More specifically, the connected state (connected) 63 includes, for example, an authenticating state 71, a negotiating state 72, a service executing state 73, and a no service state (no service). ) 74 sub-states (four phases) are defined.

  An authenticating state 71 corresponds to the authentication phase described above. The authenticating state (authenticating) 71 is a state in which the process of authenticating the connection partner device is being performed. If authentication of the connected device is successful, the state of the PCL controller transitions to a negotiating state 72, while if authentication of the device fails, the state of the PCL controller is no service. Transition to 74.

  A negotiating state 72 corresponds to the above-described negotiation phase. In the negotiating state (negotiating) 72, a process of determining a service (also referred to as an application service) to be provided by close proximity wireless communication between the close proximity wireless communication device 20 and an external device is performed by negotiation with a connection partner device. It is in a state of being broken. During the period of negotiating 72, under the control of the device in proactive mode, for example, information on the service to be executed (for example, the type of PCL adapter to be used, the type of application protocol to be used, Etc.) are exchanged between devices, which determines the services to be performed by proximity wireless communication between the devices. For example, a device in proactive mode can notify a communication partner device (reactive mode device) of information related to a service corresponding to an application program executed on the device, and the communication partner device can notify the communication partner device. The determined service is determined as a service to be executed. In addition, for a device whose default device mode is flexible mode, for example, a service associated in advance with a communication partner device (reactive mode device) is determined as a service to be executed, and information on the determined service is displayed. You may make it notify to the other party's device.

  When the negotiation is successful and the service to be used is determined, the PCL adapter and the application program corresponding to the determined service are started, and the state of the PCL controller transitions to a service executing state 73 (executing service) 73 To do. If the negotiation fails, the state of the PCL controller transitions to a no service 74.

  A service executing state (executing service) 73 corresponds to the service execution phase described above. The service executing state 73 (executing service) 73 is a state in which a determined service such as data transfer is being executed by close proximity wireless communication. When execution of the determined service is complete, the state of the PCL controller transitions to a no service 74.

  When the connection (CNL connection) between devices is released (disconnected), the state of the PCL controller is changed to an unconnected state (unconnected) 61. There are two types of events that cause the connection between devices to be released, for example, (1) the occurrence of a communication timeout due to the release of the proximity state, and (2) the reception of a connection release request signal C-RLS from the communication partner device. is there.

  The communication timeout occurs when communication between devices is interrupted by a predetermined timeout value or more after the distance between the devices is separated from the communication range. During the period of the connected state (connected) 63, the CNL layer can periodically transmit, for example, a command (probe command or the like) for confirming that the communication partner device exists within the communication range ( Polling). If there is no response from the communication partner device for this command for longer than the timeout value after transmitting this command, the CNL layer notifies the PCL layer that a communication timeout has occurred due to the release of the proximity state. The PCL controller executes, for example, a process for stopping a running PCL adapter, a process for stopping a running application, and the like to release a connection between devices and transition to an unconnected state (unconnected) 61. To do.

  The connection release request signal C-RLS is a command that explicitly requests connection release. The device in the connecting state 62 (connecting) 62, for example, during a period in which the state is a no service state 74 (no service) 74, the connection release request signal C-RLS is sent to the communication partner device as necessary. Can be sent.

  Even when the connection release request signal C-RLS is received from the communication partner device, the PCL controller is starting, for example, the process of stopping the active PCL adapter in the same manner as when a communication timeout occurs. A process for stopping the application is executed, the connection between the devices is released, and the state transits to an unconnected state (unconnected) 61.

  The electronic device 10 of this embodiment can operate in the flexible mode. In other words, the default device mode of the electronic device 10 may be a flexible mode. Therefore, during the period of the unconnected state (unconnected) 61, the PCL controller transmits a connection request signal C-Req by controlling the CNL layer in order to establish a connection with the device in the reactive mode. To do.

  In the unconnected state 61, the PCL controller of the electronic device 10 transmits a connection request signal. However, when the state of the PCL controller transitions to an unconnected state 61 due to the release of the connection due to a communication timeout, the communication partner device that was previously connected to the electronic device 10 no longer exists within the communication range. do not do. For this reason, even if the PCL controller transmits a connection request signal, as long as the user does not bring the communication partner device close to the electronic device 10 again, the communication partner device and the electronic device 10 (proximity wireless communication device 20). Will not be re-established.

  On the other hand, when the state of the PCL controller transitions to the unconnected state 61 due to reception of the connection release request signal C-RLS from the communication partner device, the communication partner device is the electronic device 10 ( There is a possibility that the wireless communication device 20 is kept close to the proximity wireless communication device 20). For this reason, there is a possibility that the connection between the communication partner device and the electronic apparatus 10 (proximity wireless communication device 20) is automatically re-established. In this case, there is a possibility that the same service as the service such as data transfer executed at the time of the previous connection is executed again between the communication partner device and the electronic device 10 (close proximity wireless communication device 20). The communication partner device may transmit a connection release request signal C-RLS each time a transition to a no service 74 occurs. In this case, there arises a problem that the same service is repeatedly executed. For example, a situation may occur in which several identical data files are repeatedly transferred between the communication partner device and the electronic device 10 (close proximity wireless communication device 20).

  FIG. 8 shows an example of a sequence in which the same service is repeatedly executed. FIG. 8 assumes close proximity wireless communication between a device A whose default device mode is the flexible mode and a device B whose default device mode is the reactive mode.

(1) After the connection between the device A and the device B is established, the device mode of the device A transitions to the proactive mode. Data transfer is performed between device A and device B under the control of device A. For example, when the data transfer is completed, the device B may transmit a connection release request signal C-RLS (disconnect command).
(2) When the device A receives the connection release request signal C-RLS from the device B, the device A changes the device mode of the local device to the flexible mode that is the default device mode.
(3) The device A transmits a connection request signal C_Req to detect the opposite device. When the device A receives a response signal C_Acc (“OK” in the figure) indicating the acceptance of the connection request signal C_Req from the device B, the device A establishes a connection between the device A and the device B.
(4) The device A determines a service by negotiation with the device B, activates an application such as an application associated with the device B, and changes its own device mode to the proactive mode.
(5) The application started in (4) starts file transfer. When the data transfer is completed, the device B may transmit the connection release request signal C-RLS (disconnect command) again. As a result, the sequence (reconnection, data transfer) surrounded by the dotted line in FIG. 8 is repeated.

  FIG. 9 shows an example of a sequence in which the same service is repeatedly executed. FIG. 9 assumes near field communication between the device A in the flexible mode and the device B set in the proactive mode.

(1) After the connection between the device A and the device B is established, the device mode of the device A transitions to the reactive mode. Data transfer is performed between device A and device B under the control of device B in the proactive mode. For example, when the data transfer is completed, the device B may transmit a connection release request signal C-RLS (disconnect command).
(2) When the device A receives the connection release request signal C-RLS from the device B, the device A changes the device mode of the local device to the flexible mode that is the default device mode. Device B also transitions to the reactive mode, which is its default device mode.

(3) The device A transmits a connection request signal C_Req to detect the opposite device. When the device A receives a response signal C_Acc (“OK” in the figure) indicating the acceptance of the connection request signal C_Req from the device B, the device A establishes a connection between the device A and the device B.
(4) The device A determines a service by negotiation with the device B, activates an application such as an application associated with the device B, and changes its own device mode to the proactive mode.
(5) The application started in (4) starts file transfer. When the data transfer is completed, the device B may transmit the connection release request signal C-RLS (disconnect command) again. As a result, the sequence (reconnection, data transfer) surrounded by the dotted line in FIG. 9 is repeated.

  A flexible mode function (for example, a function of automatically transmitting a connection request signal in a non-connected state) is useful in terms of enhancing connectivity between devices. However, as described above, if devices are left in close proximity, a problem of reconnection and data transfer may occur.

  In order that the connection control program 121 of this embodiment can prevent the occurrence of such reconnection and repeated data transfer, after the CNL connection is released by the connection release request signal from the external device (B1). The identifier of the external device (B2) in which a new connection with the close proximity wireless communication device 20 is established is compared with the identifier of the external device (B1) that has transmitted the connection release request signal, and these identifiers do not match (external The device (B2) is a device different from the external device (B1)), and performs data transfer between the external device (B2) and the close proximity wireless transfer device 20, and when these identifiers match (external device (B2 ) And the external device (B1) are the same device), and between the external device (B2) and the close proximity wireless transfer device 20 It does not execute the data transfer. For example, when these identifiers match, the connection control program 121 detects the external device (B2) in order to prevent the data transfer between the external device (B2) and the close proximity wireless transfer device 20 from being executed again. ) Negotiation with) is stopped.

  The process of stopping the execution of the negotiation is the connection between the local device and the external device after the connection between the local device and the external device is released due to the reception of the connection release request signal from the external device. Is executed on the condition that is re-established. When a connection between devices is established after a communication timeout, a control sequence for data transfer (also referred to as a connection process), that is, authentication, negotiation, and service execution are executed unconditionally.

  As described above, stopping the processing in the negotiation phase can prevent reconnection and data transfer between the flexible mode device and the external device from being repeated.

  Note that, for example, a message for inquiring the user as to whether or not the connection processing operation with the same device may be continued may be displayed on the LCD 15. If the user selects not to continue the connection process, the connection control program 121 stops execution of the connection process (for example, execution of negotiation). On the other hand, if the user selects to continue the connection processing operation, the connection control program 121 continues the connection processing.

  Next, an example of a communication control operation executed by the connection control program 121 of this embodiment will be described with reference to FIG. In FIG. 10, device A is a device whose default device mode is the flexible mode, and device B is a device whose default device mode is the reactive mode. The electronic apparatus 10 of this embodiment corresponds to the device A.

After the connection between device A and device B is established, the device mode of device A transitions to the proactive mode. Data transfer is performed between device A and device B under the control of device A. For example, when the data transfer is completed, the device B may transmit a connection release request signal C-RLS (disconnect command).
When the device A receives the connection release request signal C-RLS from the device B, the device A shifts to the non-connected state and changes the device mode of the device A to the flexible mode that is the default device mode. Device A transmits a connection request signal C_Req in order to detect the opposite device. When the device A receives a response signal C_Acc (“OK” in the figure) indicating the acceptance of the connection request signal C_Req from the device B, the device A establishes a connection between the device A and the device B. Then, the connection control program 121 of the device A transitions from the connected state (connecting) 62 to the connected state (connected) 63.

  In this way, when the connection between the device A and the device B is reestablished after the connection release by the connection release request signal C-RLS, the connection control program 121 determines whether or not to continue the connection process with the same device. A message box 71 for confirming with the user, that is, a message for confirming with the user whether to continue the close proximity wireless communication between the device A and the device B is displayed on the display screen of the LCD 15. The message box 71 is displayed, for example, when the following three conditions are satisfied.

Condition 1: The cause of the previous connection release is reception of the connection release request signal C-RLS from the external device.
Condition 2: A new connection is established within a predetermined time (X seconds) from the reception of the connection release request signal C-RLS.
Condition 3: The identifier (UID) of the external device newly connected to the local device is the same as the identifier (UID) of the external device previously connected to the local device (that is, the connection with the same external device is re-established) Was).

  If the external device that transmitted the connection release request signal C-RLS is left in the state of being close to the local device, the external device that has transmitted the connection release request signal C-RLS within a predetermined time (X seconds). A new connection between the device and the local device is automatically established. Therefore, the condition 2 can be used as a condition for confirming that the external device that has transmitted the connection release request signal C-RLS is left in a state of being close to the local device. If the user once separates the external device that has transmitted the connection release request signal C-RLS from the local device and then touches the external device again, condition 2 often does not hold.

  Note that the message box 71 may be displayed when two conditions of condition 1 and condition 2 are satisfied. Whether or not the UID of the external device newly connected to the local device is the same as the UID of the external device previously connected to the local device is confirmed by, for example, authentication processing in the authenticating state 71. I can do it. That is, when the connection control program 121 of the device A enters the authenticating state 71 in the connected state 63, the UID of the external device newly connected to the local device and the previous connection to the local device are connected. The UIDs of the external devices (external devices that have transmitted the connection release request signal C-RLS immediately before) are compared, and it is determined whether or not these UIDs match.

  If the “Yes” button in the message box 71 is clicked by the user, the connection control program 121 determines the service to be executed in the negotiation phase as usual, and executes the determined service in the service execution phase. . On the other hand, if the “No” button in the message box 71 is clicked by the user, the connection control program 121 stops processing in the negotiation phase. Thereby, the progress of the connection process is stopped, for example, immediately before the negotiation is started (at the beginning of the negotiation phase), or is stopped in the middle of the negotiation. Therefore, no service such as data transfer is executed between the device A and the device B.

  During the period in which the state of the device A is in the connected state (connected) 63, the device A can monitor whether or not a communication timeout has occurred. Therefore, even if the PCL controller of the device A is in a state where the processing is stopped in the negotiation phase, if the device B is separated from the device A by the user, the occurrence of a communication timeout is detected, and thereby the device A (The state of the connection control program 121) is transitioned to an unconnected state 61. Therefore, the device A can establish a connection with a new counter device.

  Next, an example of a communication control processing procedure executed by the communication control program 121 in order to realize the sequence of FIG. 10 will be described with reference to the flowchart of FIG.

  The communication control program 121 releases the connection from the opposite device after notifying the opposite device of the completion of service execution such as data transfer or after the completion of the service execution is notified from the opposite device to the local device (step S11). It is determined whether a request signal C-RLS (disconnect command) has been received (step S12).

  If the connection release request signal C-RLS has not been received (NO in step S12), the state of the communication control program 121 changes to a no service state (no service) 74 (step S13). If a disconnection event due to a communication timeout occurs during the period in which the communication control program 121 is in a no-service state (no service) 74 (YES in step S14), the communication control program 121 executes the local device (proximity wireless communication of the electronic device 10). In order to release the connection between the device 20) and the opposite device, processing such as stopping the active PCL adapter is executed as necessary, and the state of the PCL controller of the local device is set to the disconnected state (disconnected state). ) 61 (step S15). In the unconnected state (disconnected state) 61, the communication control program 121 starts processing for transmitting a connection request signal in cooperation with the CNL layer.

  If the connection release request signal C-RLS is received (YES in step S12), the communication control program 121 executes connection release processing (disconnection processing) for releasing the connection between the local device and the opposite device. Then, the state of the PCL controller of the local device is set to a disconnected state (disconnected state) 61 (step S16). In step S16, for example, a process of stopping an active PCL adapter is executed.

  Then, the communication control program 121 returns the device mode of the local device to the flexible mode that is the default mode (step S17). And the communication control program 121 starts the process which transmits a connection request signal (step S18).

  If the communication control program 121 receives the response signal C_Acc from the opposite device (or the connection request signal C_Req from the opposite device) in the unconnected state (disconnected state) 61 (YES in step S19), the communication control program 121 In cooperation with the CNL layer, a connection is established between the opposite device that has transmitted the response signal C_Acc or the connection request signal C_Req and the local device, and the authenticating state 71 in the connected state 63 is authenticated. Transition to. The communication control program 121 authenticates the opposite device and determines whether or not the above three conditions are satisfied (step S20).

  If the three conditions are satisfied (YES in step S20), the communication control program 121 displays the message box 71 on the LCD 15 and confirms with the user whether or not to continue the connection process with the same device ( Step S21).

  If the user has selected to continue the connection process (YES in step S22), the communication control program 121 prepares for data transfer (step S23). In step S23, the communication control program 121 enters the negotiation phase (negotiating state 72). Then, the communication control program 121 executes negotiation with the opposite device in the negotiation phase in order to determine a service to be provided by close proximity wireless communication between the local device and the opposite device. Then, the communication control program 121 enters the service execution phase (service executing state 73), and executes the determined service (data transfer) in the service execution phase (step S24).

  If the user selects not to continue the connection process (NO in step S22), the communication control program 121 stops the process in the negotiation phase (step S25). As a result, since the negotiation with the opposite device is not executed, the service to be provided by the close proximity wireless communication between the local device and the opposite device is not determined. Therefore, neither the local device nor the opposing device can select and start each of the PCL adapter and the application program. Therefore, the service (data transfer) is not started. If a disconnection event due to a communication timeout occurs during the period when the connection process is stopped (YES in step S26), the communication control program 121 sets the state of the PCL controller of the local device to the disconnected state (disconnected state) 61. (Step S15).

  Next, another example of the communication control operation executed by the connection control program 121 of this embodiment will be described with reference to FIG. In FIG. 12, device A is a device whose default device mode is the flexible mode, and device B is a device whose default device mode is the reactive mode. The electronic apparatus 10 of this embodiment corresponds to the device A.

After the connection between device A and device B is established, the device mode of device A transitions to the proactive mode. Data transfer is performed between device A and device B under the control of device A. For example, when the data transfer is completed, the device B may transmit a connection release request signal C-RLS (disconnect command).
When the device A receives the connection release request signal C-RLS from the device B, the connection control program 121 of the device A displays the message box 72 on the LCD 15 at this time. This message box 72 is used for notifying the user that the device is still touched by the electronic device 10 and for confirming to the user whether or not reconnection (continuation of the connection process) with this device is present. It is done. The message box 72 also displays a message that recommends the user to move the device away from the electronic device 10 if reconnection is not desired.

  Under the control of the connection control program 121, the device A proceeds with processing. That is, the device A changes to the non-connected state and changes the device mode of the device A to the flexible mode that is the default device mode. Device A transmits a connection request signal C_Req in order to detect the opposite device. When the device A receives a response signal C_Acc (“OK” in the figure) indicating the acceptance of the connection request signal C_Req from the device B, the device A establishes a connection between the device A and the device B.

  If the “Yes” button in the message box 72 is clicked by the user, the connection control program 121 determines the service to be executed in the negotiation phase as usual, and executes the determined service in the service execution phase. . On the other hand, if the “No” button in the message box 72 is clicked by the user, the connection control program 121 stops processing in the negotiation phase. Thereby, the progress of the connection process is stopped, for example, immediately before the negotiation is started, or is stopped in the middle of the negotiation. Therefore, no service such as data transfer is executed between the device A and the device B.

  If the device B is separated from the device A by the user, the occurrence of a communication timeout is detected, and the state of the device A (the state of the connection control program 121) is changed to the unconnected state (unconnected) 61. .

  Next, an example of a communication control process executed by the communication control program 121 in order to realize the sequence of FIG. 12 will be described with reference to the flowchart of FIG.

  The communication control program 121 releases the connection from the opposite device after notifying the opposite device of completion of the service execution such as data transfer or after the completion of the service execution is notified from the opposite device to the local device (step S31). It is determined whether a request signal C-RLS (disconnect command) has been received (step S32).

  If the connection release request signal C-RLS has not been received (NO in step S32), the state of the communication control program 121 transitions to a no service state (no service) 74 (step S33). If a disconnection event due to a communication timeout occurs during a period in which the communication control program 121 is in a no-service state (no service) 74 (YES in step S34), the communication control program 121 executes the local device (proximity wireless communication of the electronic device 10). In order to release the connection between the device 20) and the opposite device, processing such as stopping the active PCL adapter is executed as necessary, and the state of the PCL controller of the local device is set to the disconnected state (disconnected state). ) 61 (step S35). In the unconnected state (disconnected state) 61, the communication control program 121 starts processing for transmitting a connection request signal in cooperation with the CNL.

  If the connection release request signal C-RLS is received (YES in step S32), the communication control program 121 first displays the message box 72 on the LCD 15, and the device remains touched by the electronic device 10. To the user and confirms the intention to reconnect to the device (step S36).

  In a state where the message box 72 is displayed, the communication control program 121 executes connection release processing (disconnection processing) for releasing the connection between the local device (electronic device 10) and the opposite device, and the local device The state of the PCL controller is set to a disconnected state (disconnected state) 61 (step S37). Then, the communication control program 121 returns the device mode of the local device to the flexible mode that is the default mode (step S38). And the communication control program 121 starts the process which transmits a connection request signal (step S39).

  If the communication control program 121 receives the response signal C_Acc from the opposite device (or the connection request signal C_Req from the opposite device) in the unconnected state (disconnected state) 61 (YES in step S40), the communication control program 121 In cooperation with the CNL layer, a connection is established between the opposite device that has transmitted the response signal C_Acc or the connection request signal C_Req and the local device, and the authenticating state 71 in the connected state 63 is authenticated. Transition to.

  The communication control program 121 determines which of the “Yes” button or the “No” button in the message box 72 is selected by the user (step S41). If the “Yes” button, that is, the continuation of the connection process is selected by the user (YES in step S41), the communication control program 121 prepares for data transfer (step S42). In step S42, the communication control program 121 enters a negotiation phase (negotiating state 72). Then, the communication control program 121 executes negotiation with the opposite device in the negotiation phase in order to determine a service to be provided by close proximity wireless communication between the local device and the opposite device. Then, the communication control program 121 enters the service execution phase (service executing state 73), and executes the determined service (data transfer) in the service execution phase (step S43).

  If the “No” button, that is, not to continue the connection process is selected by the user, or if neither the “Yes” button or the “No” button is selected by the user (NO in step S41), the communication control The program 121 stops processing in the negotiation phase (step S44). As a result, the service to be provided by the close proximity wireless communication between the local device and the opposite device is not determined. Therefore, the service is not started because neither the local device nor the opposite device can select and start each of the PCL adapter and the application program. If a disconnection event due to a communication timeout occurs during the period when the connection process is stopped (YES in step S45), the communication control program 121 sets the state of the PCL controller of the local device to a disconnected state (disconnected state) 61. (Step S35).

  As described above, according to the present embodiment, even if the connection between the external device and the electronic apparatus 10 is reestablished due to the reception of the connection release request from the external device, It is possible to prevent the same service from being executed again.

  Note that the function of the connection control program of the present embodiment can also be realized by a hardware module.

  Further, the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of components disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

  DESCRIPTION OF SYMBOLS 10 ... Electronic device, 11 ... System control part, 12a ... Communication control program, 101a ... CPU, 20 ... Proximity wireless communication device, 121 ... Connection control program, 123 ... Connection control part, 124 ... Communication control part, 125 ... Connection release Department.

Claims (6)

A communication module for performing close proximity wireless communication;
A connection control means for transmitting a connection request signal during a period in which the communication module is in a non-connected state and establishing a connection between the communication module and an external device in a proximity state;
Communication control means for executing data transfer between the communication module and the external device when the connection is established;
Connection release means for releasing the connection between the communication module and the external device when an event of occurrence of a communication timeout due to the release of the proximity state or reception of a connection release request signal from the external device occurs And
In the communication control means, when the connection is established, the cause of the previous connection release is reception of a connection release request signal, the connection is established within a predetermined time from the previous connection release, and the communication module Whether or not the condition that the first external device connected last time and the external device newly connected to the communication module are the same device is satisfied, and if the condition is satisfied, The data transfer between the communication module and the external device is not executed, and the data transfer between the communication module and the external device is executed when the condition is not satisfied. Electronic equipment. The communication control means displays on the display a message for confirming to the user whether or not to continue proximity wireless communication between the communication module and the external device when the condition is satisfied, and performs the proximity wireless communication. The electronic device according to claim 1, wherein the data transfer is not executed when it is designated by the user not to continue. The communication control means displays on the display a message for confirming to the user whether or not to continue proximity wireless communication between the communication module and the external device when the condition is satisfied, and performs the proximity wireless communication. The data transfer is not performed when the user specifies not to continue, and the data transfer is performed when the user specifies not to continue the close proximity wireless communication. Electronic equipment. A communication control method for controlling proximity wireless communication executed by a communication module provided in an electronic device,
A connection control step of transmitting a connection request signal during a period in which the communication module is in a non-connected state, and establishing a connection between the communication module and an external device in a proximity state;
A communication control step for executing data transfer between the communication module and the external device when the connection is established;
A connection release step for releasing the connection between the communication module and the external device when an event of occurrence of a communication timeout due to the release of the proximity state or reception of a connection release request signal from the external device occurs And
The communication control step includes
When the connection is established, the cause of the previous connection release is reception of a connection release request signal, the connection is established within a predetermined time from the previous connection release, and the communication module is connected to the communication module last time. Determining whether a condition that one external device and the external device newly connected to the communication module are the same device is satisfied,
When the condition is satisfied, data transfer between the communication module and the external device is not executed, and when the condition is not satisfied, data transfer between the communication module and the external device is executed. A communication control method characterized by the above. In the communication control step, when the condition is satisfied, a message for confirming whether or not to continue the proximity wireless communication between the communication module and the external device is displayed on a display, and the proximity wireless communication is performed. 5. The communication control method according to claim 4, wherein when the user designates not to continue, the data transfer is not executed. In the communication control step, when the condition is satisfied, a message for confirming whether or not to continue the proximity wireless communication between the communication module and the external device is displayed on a display, and the proximity wireless communication is performed. 5. The data transfer is not executed when the user designates not to continue, and the data transfer is executed when the user designates that the close proximity wireless communication is continued. Communication control method.

Images