JP4856270B2 - Electronic device and communication control method - Google Patents

Description

  The present invention relates to an electronic device that performs communication using a proximity wireless communication method 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. only by holding the IC card or mobile phone over the reader / writer unit of the host device.

  In Patent Document 1, when a plurality of applications that use short-range wireless are simultaneously executed, each application can use the short-range wireless without performing an operation of terminating the application and releasing communication resources. Discloses a wireless communication apparatus for performing communication management.

JP 2008-104088 A

  By the way, in the close proximity wireless communication system, there is a demand for starting execution of a service automatically only by bringing devices close to each other. When starting service execution automatically by bringing devices close to each other, for example, by simply bringing the mobile phone closer to the personal computer, the data stored in the mobile phone is synchronized with the backup of the data stored in the personal computer. It is possible to realize a function such as That is, when a proximity state between devices is detected, service provision can be automatically started via negotiation.

  However, if service provision is automatically started again when devices are left in close proximity after service provision is completed, provision of services that the user does not want may start. There is. In addition, when provision of an undesired service is started, the user needs to perform an operation for stopping the service, which can be said to be a complicated operation for the user.

  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 that can suppress provision of unnecessary services.

  In order to solve the above-described problem, an electronic device according to the present invention is provided between a communication module that performs close proximity wireless communication, and between the communication module and the external device when the communication module and the external device are in close proximity. The communication module set in the second mode for receiving a service start request from the communication partner device when the connection establishment means for establishing the connection and the application program using the proximity wireless communication are selected. Mode control means for setting a first mode for transmitting a service start request to the device, and when the communication module is set to the first mode, a service start request is transmitted to the external device, The communication module is negotiated between the communication module and the external device. Characterized by comprising the negotiating means for determining a service to be executed between the external device, and a service execution unit configured to execute the determined service.

  Further, the communication control method of the present invention is a communication control method for controlling communication between an electronic device including a communication module that performs close proximity wireless communication and an external device, wherein the communication module and the external device are close to each other. When a connection establishment step for establishing a connection between the communication module and the external device and an application program using close proximity wireless communication are selected, a service start request is received from the communication partner device. A mode control step for setting the communication module set to the second mode to a first mode for transmitting a service start request to a communication partner device; and the communication module is set to the first mode. A service start request is transmitted to the external device, and the communication module and the external device are transmitted. A negotiation step for determining a service to be executed between the communication module and the external device, and a service execution step for executing the determined service. .

  According to the present invention, provision of unnecessary services can be suppressed.

It is a block diagram which shows the system configuration | structure of the electronic device which concerns on one Embodiment of this invention. 2 is an exemplary diagram illustrating an example of a software architecture for controlling close proximity wireless communication, which is applied to the electronic apparatus of the embodiment. FIG. 3 is a block diagram illustrating a configuration example of a PCL included in the software architecture of FIG. 2. 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 sequence diagram which shows the example of the near field communication between devices. The sequence diagram which shows another example of the near field communication between devices. FIG. 5 is a sequence diagram illustrating an example of close proximity wireless communication performed between the electronic apparatus of the embodiment and an external device. FIG. 11 is a sequence diagram showing another example of close proximity wireless communication performed between the electronic apparatus of the embodiment and an external device. FIG. 11 is a sequence diagram showing another example of close proximity wireless communication performed between the electronic apparatus of the embodiment and an external device. FIG. 9 is a sequence diagram showing still another example of close proximity wireless communication performed between the electronic apparatus of the embodiment and an external device. The state transition diagram which shows the example of the state transition of the near field communication by the electronic device of the embodiment. FIG. 6 is a diagram illustrating a service provided between the electronic apparatus and the external device of the embodiment. The flowchart which shows the procedure of the near field communication process by the device which communicates by a near field communication system. 6 is an exemplary flowchart illustrating a procedure of close proximity wireless transfer processing 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 mobile device (for example, a mobile phone, a PDA, an audio player, etc.), a personal computer, or a consumer device (for example, a TV, a video recorder, etc.). The electronic device 10 includes a system control unit 101, ROM 102, RAM 103, proximity wireless communication device 104, power supply control unit 105, AC adapter 106, and battery 107.

  The system control unit 101 controls the operation of each unit in the electronic device 10. The system control unit 101 includes a CPU 101 a and is connected to the ROM 102, the RAM 103, the close proximity wireless transfer device 104, and the power supply control unit 105.

  The CPU 101a is a processor that loads a command group and data stored in the ROM 102 into the RAM 103 and executes necessary processing. The RAM 103 is loaded with a proximity wireless communication control program 103a for controlling the proximity wireless communication. The CPU 101 a controls the near field communication device 104 by executing the near field communication control program 103 a loaded in the RAM 103.

  The close proximity wireless transfer device 104 is a communication module that executes close proximity wireless transfer. The close proximity wireless transfer device 104 establishes a wireless connection with another device (external device) having a close proximity wireless communication function that exists within a predetermined distance from the close proximity wireless communication device 104, and transmits data such as a file. To start. Proximity wireless communication between the proximity wireless communication device 104 and the external device is performed in a peer-to-peer manner. The communicable distance is 3 cm, for example. The wireless connection between the close proximity wireless communication device 104 and the external device is such that the close proximity wireless communication device 104 and the external device are in close proximity, that is, the distance between the close proximity wireless communication device 104 and the external device is a communicable distance. Only possible when approaching within (for example, 3 cm). When the close proximity wireless communication device 104 and the external device approach within a communicable distance, a wireless connection is established between the close proximity wireless communication device 104 and the external device. For example, data transmission such as a data file explicitly designated by the user or a predetermined synchronization target data file is executed between the close proximity wireless transfer device 104 and the external device.

  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 104 is connected to the antenna 104a. The antenna 104a is an electrode called a coupler, and transmits / receives data to / from an external device by a wireless signal using an induced electric field. When the external device approaches within a communicable distance (for example, 3 cm) from the antenna 104a, the close proximity wireless communication device 104 and the antenna (coupler) of each external device are coupled by an inductive electric field, whereby the close proximity wireless communication device Wireless communication between the external device 104 and the external device can be executed. The close proximity wireless transfer device 104 and the antenna 104a can be realized as one module.

  The power control unit 105 supplies power to each unit in the electronic device 10 using power supplied from the outside via the AC adapter 106 or power supplied from the battery 107. In other words, the electronic device 10 is driven by an external power source such as an AC commercial power source or the battery 107. The AC adapter 106 can also be provided in the electronic device 10.

  Next, with reference to FIG. 2, a software architecture for controlling close proximity wireless communication performed using the close proximity wireless communication device 104 will be described.

  The software architecture of FIG. 2 shows a hierarchical structure of a protocol stack for controlling close proximity wireless communication. The protocol stack includes a physical layer (PHY) 20, a connection layer (CNL) 30, a protocol conversion layer (PCL) 40, and an application layer 50. For example, the connection layer (CNL) 30, the protocol conversion layer (PCL) 40, and the application layer 50 can be realized by the communication control program 103a.

  The physical layer (PHY) 20 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) 20 may be realized using hardware in the close proximity wireless transfer device 104.

  The physical layer (PHY) 20 converts data from the connection layer (CNL) 30 into a radio signal. The connection layer (CNL) 30 corresponds to the data link layer and the transport layer in the OSI reference model, and controls the physical layer (PHY) 20 to execute data communication. In response to a connection request from the protocol conversion layer (PCL) 40 or a connection request from an external device, the connection layer (CNL) 30 is connected between the close proximity wireless communication device 104 and the external device set in the proximity state. A process of establishing a connection (CNL connection) is executed.

  The protocol conversion layer (PCL) 40 corresponds to the session layer and the presentation layer in the OSI reference model, and a connection layer (CNL) for controlling the establishment and release of the connection between the application layer 50 and the devices A and B. ) 30. The protocol conversion layer (PCL) 40 controls each application (communication program) in the application layer 50 and controls the connection layer (CNL) 30.

  More specifically, the protocol conversion layer (PCL) 40 specifies data (user data) corresponding to an application protocol (for example, SCSI, OBEX, other general-purpose protocol) handled by each communication program of the application layer 50. Execute conversion processing to convert to the transmission data format. By this conversion processing, data transmitted / received by any communication program can be converted into a packet (data in a specific transmission data format) that can be handled by the connection layer (CNL) 30. The protocol conversion layer (PCL) 40 enables various application protocols to be used in close proximity wireless communication.

  In addition, the protocol conversion layer (PCL) 40 exchanges service information (information indicating services that can be provided by each device) and session information (information on a session to be established / disconnected) with a communication partner device. In addition, application activation, connection management, session management, and the like are performed.

  The application layer 50 includes a plurality of communication programs (applications) respectively corresponding to several application protocols such as SCSI, OBEX, and other general-purpose protocols. Each application executes processing for requesting the protocol conversion layer (PCL) 40 to start / end a session, and processing for transmitting and receiving data via the protocol conversion layer (PCL) 40.

  The protocol conversion layer (PCL) 40 includes, for example, a mode monitoring unit 41, a connection monitoring unit 42, a mode monitoring database 43, and a connection monitoring database 44.

  The connection monitoring unit 42 monitors the connection (CNL connection) between the electronic device 10 set in the proximity state and the external device. As described above, in the CNL 30, in response to a connection request from the PCL 40 or a connection request from an external device, processing for establishing a connection between the electronic device 10 set in the proximity state and the external device is executed. The Further, the connection between the electronic device 10 and the external device is released in response to a connection release request by the user or a release of the proximity state due to the separation of the electronic device 10 and the external device. The connection monitoring unit 42 monitors the establishment and release of these connections, and displays information indicating that the connection has been established between the electronic device 10 and the external device or that the connection has been released. To store.

  The mode monitoring unit 41 monitors the mode set in the PCL 40. In the PCL 40, any one of a proactive mode, a reactive mode, and a flexible mode is set.

  The proactive mode is a mode for transmitting a service start request from the electronic device 10 to an external device. The device set to the proactive mode functions as a so-called master, and can control a communication partner device to execute a service such as data transfer between the devices. The reactive mode is a mode in which the electronic apparatus 10 receives a service start request transmitted from an external device. The device set in the reactive mode functions as a so-called slave, and can execute services such as data transfer between devices under the control of the communication partner device.

  The default mode of a portable device such as a mobile phone that cannot be driven by an external power supply is set to reactive mode to reduce its power consumption. When the user operates an application on the portable device, the portable device automatically transitions from the reactive mode to the proactive mode.

  The device set to the proactive mode transmits a connection request signal. On the other hand, since the device in the reactive mode does not transmit a connection request signal, power consumption is relatively small.

  The flexible mode is a mode in which a transition is made between the proactive mode and the reactive mode in accordance with the mode (proactive mode or reactive mode) set in the external device set in the proximity state. The electronic device 10 set in the flexible mode transitions to the reactive mode when the external device is in the proactive mode by negotiation with the external device set in the proximity state, and the external device is in the reactive mode. In the case of, transition to the proactive mode. That is, the electronic device 10 set in the flexible mode switches between functioning as a master and functioning as a slave depending on the mode set in the communication partner device. The transition to the proactive mode or the reactive mode is performed, for example, after a connection between devices is established.

  A default mode set in a device such as a personal computer that can be driven by an external power source such as an AC adapter power source is a flexible mode. The device set to the flexible mode transmits a connection request signal. Thus, even when the user brings the mobile phone close to the personal computer (flexible mode device) without operating the mobile phone application, the connection between the devices can be established. Services such as data file transfer can be provided to the user.

  When a service is executed between a device set to proactive mode (device that has transitioned to proactive mode) and a device that has been set to reactive mode (device that has transitioned to reactive mode), The service specified by the configured device is executed between these two devices. When service execution is completed, the device that has transitioned from the reactive mode to the proactive mode returns to the reactive mode, the device that has transitioned from the flexible mode to the proactive mode, or the device that has transitioned from the flexible mode to the reactive mode. Returns to flexible mode.

  The mode monitoring unit 41 stores information indicating the current mode of the PCL 40 in the mode monitoring database 43. Therefore, when the PCL 40 of the electronic device 10 transitions from the flexible mode to the proactive mode or the reactive mode by negotiation with the external device set in the proximity state, the information indicating one of the transitioned modes is used. The mode monitoring database 43 is rewritten.

  The PCL 40 monitors the connection between the electronic device 10 and an external device (CNL connection) and the mode set in the PCL 40, and controls each application (communication program) in the application layer 50 and CNL 30. Is called.

  FIG. 3 is a block diagram illustrating an example of a functional configuration of the close proximity wireless transfer control program 103a that realizes the functions of the PCL 40 described above.

  As illustrated in FIG. 3, the close proximity wireless transfer control program 103 a includes a control unit 401, a CNL connection monitoring unit 402, a negotiation processing unit 403, a mode control unit 404, a service processing unit 405, and a standby processing unit 406. The close proximity wireless transfer control program 103a is connected to the database 410. The database 410 includes a CNL connection state 410a which is information indicating a connection state between the electronic device 10 and an external device, a connection mode set in the PCL 40 of the electronic device 10, and a connection mode set in the PCL of the external device. This is a storage device that stores the connection mode 410b, which is information indicating.

  The control unit 401 controls a communication sequence between the electronic device 10 and an external device. That is, the control unit 401 responds to a request or notification from the application unit 501 corresponding to the application layer 50 and the data communication unit 201 corresponding to the CNL 30 and the physical layer (PHY) 20 in the proximity wireless communication control program 103a. Control each part.

  The CNL connection monitoring unit 402 monitors the connection (CNL connection) between the electronic device 10 and the external device by the CNL 30. When the connection between the proximity wireless communication device 104 and the external device by the CNL 30 is established, the CNL connection monitoring unit 402 stores information indicating that the CNL connection is established in the CNL connection state 410a of the database 410. To do. When the connection between the electronic device 10 and the external device by the CNL 30 is released, the CNL connection monitoring unit 402 stores information indicating that the CNL connection is released in the CNL connection state 410a of the database 410. To do.

  The CNL connection monitoring unit 402 notifies each unit of the close proximity wireless transfer control program 103a of the establishment or release of the CNL connection. When notified that the CNL connection has been released, the negotiation processing unit 403, the mode control unit 404, the service processing unit 405, and the standby processing unit 406 interrupt the process being executed. In other words, the processes by the negotiation processing unit 403, the mode control unit 404, the service processing unit 405, and the standby processing unit 406 are executed during the period when the CNL connection is established.

  When the negotiation processing unit 403 receives a notification indicating that the CNL connection has been established from the CNL connection monitoring unit 402, the negotiation processing unit 403 performs the negotiation processing. The negotiation processing unit 403 executes arbitration of a mode set in the PCL 40, determination of a service executed between devices, service synchronization, and the like as negotiation processing.

  In arbitration of the mode set in the PCL 40, the negotiation processing unit 403 determines the mode set in the PCL 40 of the electronic device 10 according to the mode set in the communication partner device. As described above, one of the proactive mode, the reactive mode, and the flexible mode is set in the PCL 40. When a service is executed between two devices, one device is set to a proactive mode that transmits a service start request to a communication partner device, and the other device receives and responds to the service start request. Must be set to reactive mode.

  When own PCL 40 is set to proactive mode and PCL 40 of the communication partner device is set to reactive mode, or its own PCL 40 is set to reactive mode and PCL 40 of the communication partner device is set to pro When the active mode is set, the negotiation processing unit 403 does not perform processing for changing the mode set in the PCL 40.

  When its own PCL 40 is set to the flexible mode, the negotiation processing unit 403 selects either the proactive mode or the reactive mode according to the mode set to the PCL 40 of the communication partner device. That is, when the PCL 40 of the communication partner device is set to the proactive mode, the negotiation processing unit 403 selects the reactive mode as the mode to be set for the own PCL 40. Further, when the PCL 40 of the communication partner device is set to the reactive mode, the negotiation processing unit 403 selects the proactive mode as the mode to be set for the own PCL 40. Then, the negotiation processing unit 403 notifies the mode control unit 404 of the selected mode.

  The mode control unit 404 controls the mode set in the PCL 40 in cooperation with the negotiation processing unit 403. The mode control unit 404 sets the mode determined by the negotiation processing unit 403 in the PCL 40.

  Information indicating the mode set in the own PCL 40 and the mode set in the PCL 40 of the communication partner device is stored in the connection mode 410 b of the database 410.

  In determining a service to be executed between devices, the negotiation processing unit 403 determines a service specified by the device on the side where the PCL 40 is set to the proactive mode as a service to be executed between the devices. Therefore, when the communication partner device is set to the proactive mode, the negotiation processing unit 403 determines a service designated by the communication partner device as a service to be executed between the devices. In addition, when the PCL 40 is set to the proactive mode, the negotiation processing unit 403 determines a service corresponding to an application designated by the user or a predetermined service as a service to be executed between devices. .

  In the service synchronization, the negotiation processing unit 403 executes a synchronization process for starting execution of the service between devices.

  The service processing unit 405 executes a process according to the service determined by the negotiation processing unit 403 after the service is synchronized (started) by the negotiation processing unit 403. The service processing unit 405 executes processing by appropriately controlling the data communication unit 201 and the application unit 501.

  The standby processing unit 406 executes standby processing for a period from when the processing by the service processing unit 405 is completed until a new service start request is received. The standby processing unit 406 ends the standby process when a service start request is received from a communication partner device or when a service start request is input by a user. In response to the completion of the standby processing by the standby processing unit 406, the negotiation processing by the negotiation processing unit 403 is started again. That is, the standby processing unit 406 performs a service from the completion of the processing by the service processing unit 405 to the reception of a service start request from the communication partner device, or by the user after the processing by the service processing unit 405 is completed. During the period until the start request is input, the negotiation processing unit 403 is not requested to start the negotiation process.

  The application unit 501 manages a plurality of applications (communication programs) that execute data transmission / reception using proximity wireless communication. The application unit 501 executes processing for notifying the close proximity wireless communication control program 103a of a session start / end request from the application, and processing for controlling the close proximity wireless communication control program 103a. The application is a communication program corresponding to several application protocols such as SCSI, OBEX, and other general-purpose protocols.

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

  FIG. 4 is a perspective view showing an external appearance of the electronic device 10.

  The electronic device 10 includes a main body 11 and a display unit 12. The display unit 12 is attached to the main body 11 so as to be rotatable between an open position where the upper surface of the main body 11 is exposed and a closed position where the upper surface of the main body 11 is covered by the display unit 12. In the display unit 12, the above-described LCD 15 is provided.

  The main body 11 has a thin box-shaped housing. A keyboard, a touch pad, a speaker, a power switch, and the like are arranged on the upper surface of the housing of the main body 11.

  The upper surface of the main body 11, specifically, a part of the palm rest area on the upper surface of the main body 11 functions as a communication surface. That is, the close proximity wireless transfer device 104 and the antenna (coupler) 104 a are provided in the main body 11 so as to face the upper surface of the main body 11. The antenna (coupler) 104a is arranged to output a radio signal (inductive electric field) to the outside via the upper surface of the main body 11 (specifically, a part of the palm rest area on the upper surface of the main body 11). . A small area on the upper surface of the main body 11 facing the antenna (coupler) 104a, that is, a small area located above the antenna (coupler) 104a on the upper surface of the main body 11 is used as a communication position. The close proximity wireless communication device 104 performs close proximity wireless communication with an external device existing within a predetermined wireless communication possible distance (for example, 3 cm) from the communication position on the upper surface of the main body 11 via the upper surface of the main body 11.

  For example, the user performs an operation (also referred to as a touch operation) of holding an external device having a proximity wireless communication function over a communication position on the upper surface of the main body 11 to transfer data between the external device and the electronic apparatus 10. Can be started.

  FIG. 5 shows a state of close proximity wireless communication performed between the mobile phone 70 and the electronic device 10. An antenna (coupler) 70a for close proximity wireless communication is provided in the housing of the mobile phone 70 so as to face the back surface of the housing. In this case, an operation (also referred to as a touch operation) of holding the back surface of the casing of the mobile phone 70 over a communication position on the upper surface of the main body 11 of the electronic device 10, that is, bringing the mobile phone 70 close to the electronic device 10. By doing so, the connection between the mobile phone 70 and the electronic device 10 can be started. The connection between the mobile phone 70 and the electronic device 10 is triggered by the proximity of the mobile phone 70 and the electronic device 10 to each other.

  FIG. 6 is a sequence diagram illustrating an example of close proximity wireless communication between devices. Here, it is assumed that a service start request is transmitted from device A set to proactive mode to device B set to flexible mode. In the initial state, device A is set to the reactive mode, and device B is set to the flexible mode.

  First, the user selects an application program for performing close proximity wireless communication on the device A, brings the device A and the device B close to each other (touch operation), and sets the close state (S101). The device A for which the application program has been selected transitions from the reactive mode in which the service start request is received from the external device to the proactive mode in which the service start request is transmitted to the external device.

  Next, the device A and the device B execute a process (authentication process) for establishing a connection (CNL connection) between the device A and the device B (S102). For example, device A transmits a connection request. Upon receiving this connection request, device B transmits a response to the connection request to device A. With the above processing, a connection is established between device A and device B.

  The devices A and B that have established the connection execute a negotiation process (S103). As the negotiation process, device A and device B perform mode arbitration (S103a), service negotiation (S103b), and service synchronization (S103c).

  Specifically, the device B set to the flexible mode executes mode arbitration that changes its mode according to the mode set to the device A that is the communication partner device (S103a). Here, since the device A is set to the proactive mode, the device B changes its mode from the flexible mode to the reactive mode. Then, the device A and the device B execute service negotiation for determining a service to be executed between the device A and the device B (S103b). Here, the service designated by the device A set to the proactive mode, that is, the service corresponding to the application program selected by the user is determined as the service executed between the device A and the device B. . Device A and device B perform service synchronization for executing the determined service (S103c). Thereby, the execution of the service is started between the device A and the device B.

  When the above negotiation process is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S104). When the execution of the service is completed, the device A transitions from the proactive mode to the reactive mode, and the device B transitions from the reactive mode to the flexible mode. Further, the connection between the device A and the device B is released.

  After the connection between the device A and the device B is released, when the device A and the device B are maintained in the proximity state, the device A and the device B execute the authentication process again (S105). When the connection between the device A and the device B is established by the authentication process, the device A and the device B execute a negotiation process (S106). In this negotiation processing, processing similar to the processing from S103a to S103c is executed.

  First, the device B set to the flexible mode changes its own mode from the flexible mode to the proactive mode because the device A is set to the reactive mode. Next, the device A and the device B execute a service negotiation for determining a service to be executed between the device A and the device B. Specifically, the device B receives information indicating a service group that can be provided by the device A from the device A, and presents a list that lists each service included in the received service group to the user. The user selects a service to be used from the list of services presented on the device B. Device B notifies device A of information indicating the selected service. As a result, the service selected by the user is determined as a service to be executed between the device A and the device B. The service executed between device A and device B may be a predetermined service. Device A and device B execute service synchronization and start execution of the determined service. Then, the device A and the device B execute processing according to the determined service (S107).

  As described above, when one of the connected devices is set to the flexible mode, the service determined by the negotiation is executed, the execution of the service is completed, and the connection between the devices is released. After the period elapses, the connection between the devices is established again. The negotiation process is also executed again, and the provision of a new service is started without the user instructing the start of the new service.

  FIG. 7 is a sequence diagram illustrating another example of close proximity wireless communication between devices. Here, it is assumed that a service start request is transmitted from device B set to flexible mode to device A set to reactive mode. In the initial state, device A is set to the reactive mode, and device B is set to the flexible mode.

  First, the user brings device A and device B close to each other (touch operation) and sets them in a close state (S201). Next, the device A and the device B execute processing (authentication processing) for establishing a connection (CNL connection) between the device A and the device B (S202). For example, device B transmits a connection request. Receiving this connection request, device A transmits a response to the connection request to device B. With the above processing, a connection is established between device A and device B.

  The devices A and B that have established the connection execute a negotiation process (S203). As negotiation processing, device A and device B execute mode arbitration (S203a), service negotiation (S203b), and service synchronization (S203c).

  Specifically, the device B set to the flexible mode executes mode arbitration for changing its own mode according to the mode set to the device A that is the communication partner device (S203a). Here, since device A is set to the reactive mode, device B transitions its own mode from the flexible mode to the proactive mode. Then, the device A and the device B execute service negotiation for determining a service to be executed between the device A and the device B (S203b). Specifically, the device B requests the device A for information indicating a service group that the device A can provide. When the device B receives information on the service group that the device A can provide from the device A, the device B presents a list listing each service included in the service group to the user. Then, the user selects a service to be used from the list of presented services. As a result, the service selected by the user is determined as a service to be executed between the device A and the device B. The service executed between device A and device B may be a predetermined service. Next, the device A and the device B execute service synchronization for executing the determined service (S203c). Thereby, the execution of the service is started between the device A and the device B.

  When the above-described negotiation process is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S204). When the execution of the service is completed, device B transitions from the proactive mode to the flexible mode. Further, the connection between the device A and the device B is released.

  After the connection between the device A and the device B is released, when the device A and the device B are maintained in the proximity state, the device A and the device B execute the authentication process again (S205). When the connection between the device A and the device B is established by the authentication process, the device A and the device B execute a negotiation process (S206). In this negotiation processing, processing similar to the processing from S203a to S203c is executed. Then, the service determined by the negotiation process is executed between the device A and the device B (S207).

  Similar to the sequence diagram shown in FIG. 6, when one of the connected devices is set to the flexible mode, the service determined by the negotiation is executed, the service execution is completed, and the connection between the devices is released. In this case, for example, after a predetermined period elapses, the connection between the devices is established again. The negotiation process is also executed again, and the provision of a new service is started without the user instructing the start of the new service.

  In the sequence diagrams shown in FIGS. 6 and 7, when one of the connected devices is set to the flexible mode, the user starts providing the service between the devices only by bringing the device A and the device B close to each other. be able to. That is, when the device A and the device B are set in the proximity state, the authentication process and the negotiation process between the devices are automatically executed, and the provision of services can be started between the devices.

  However, in the case where service provision is automatically started as described above, it is possible to save the user's operation, while service provision is also started between devices that are simply left in proximity. There is a possibility that a service not desired by the user is executed. For example, after a service corresponding to an application designated by the user is executed between devices set in the proximity state, provision of a new service is started between devices left in the proximity state, or a new service is started. There is a possibility that a list of services for prompting the start of various services is presented to the user. In this case, the user needs to perform an operation for stopping the provision of a new service that has been started, which can be said to be a complicated operation for the user. For this reason, it is necessary to control the device so that the provision of the service is started only when there is a service start request from the user.

  8 to 11 are sequence diagrams illustrating an example of close proximity wireless communication performed between the electronic apparatus 10 and an external device. The electronic device 10 according to the present embodiment controls the close proximity wireless transfer device 104 so as to start providing a service when a user requests to start a service.

  FIG. 8 shows a sequence diagram when communication is disconnected after provision of one service is completed between devices. Here, it is assumed that a service start request is transmitted from device A set to proactive mode to device B set to flexible mode. In the initial state, device A is set to the reactive mode, and device B is set to the flexible mode. Further, in the device B, the communication completion flag indicating that the provision of the service between the devices is completed is set to a state (reset state).

  First, the user selects an application program for performing proximity wireless communication on the device A, brings the device A and the device B close to each other (touch operation), and sets the proximity state (S301). The device A for which the application program has been selected transitions from the reactive mode in which the service start request is received from the external device to the proactive mode in which the service start request is transmitted to the external device.

  Next, device A and device B execute processing (authentication processing) for establishing a connection (CNL connection) between device A and device B (S302). For example, device A transmits a connection request. Upon receiving this connection request, device B transmits a response to the connection request to device A. With the above processing, a connection is established between device A and device B.

  The devices A and B that have established the connection execute a negotiation process (S303). In the negotiation process, similarly to the processes from S103a to S103c in FIG. 6, the devices A and B execute mode arbitration, service negotiation, and service synchronization.

  Specifically, the device B set to the flexible mode executes mode arbitration that changes its mode according to the mode set to the device A that is the communication partner device. Here, since the device A is set to the proactive mode, the device B changes its mode from the flexible mode to the reactive mode. Device A and device B execute service negotiation for determining a service to be executed between device A and device B. Here, the service designated by the device A set to the proactive mode, that is, the service corresponding to the application program selected by the user is determined as the service executed between the device A and the device B. . Device A and device B execute service synchronization for executing the determined service. Thereby, the execution of the service is started between the device A and the device B.

  When the negotiation process described above is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S304). When the execution of the service is completed, the device A transitions from the proactive mode to the reactive mode, and the device B transitions from the reactive mode to the flexible mode. In addition, the device B sets a communication completion flag indicating that the execution of the service is completed (flag set). Note that the connection between the device A and the device B (CNL connection) is maintained.

  During the period when the communication completion flag is set, the device B executes standby processing for waiting for processing for starting provision of a new service. In other words, the device B is set to a wait state that waits for the start of provision of a new service during the period when the communication completion flag is set.

  Then, when the device A and the device B are separated and the proximity state is released, the connection between the device A and the device B is disconnected. In response to the disconnection between device A and device B, device B clears the communication completion flag.

  With the above processing, provision of unnecessary services can be started after the execution of services between devices is completed until the devices are separated (the proximity state between devices is released). Can be suppressed.

  FIG. 9 shows another sequence diagram when communication is disconnected after provision of one service is completed between devices. Here, it is assumed that a service start request is transmitted from device B set to flexible mode to device A set to reactive mode. In the initial state, device A is set to the reactive mode, and device B is set to the flexible mode. Further, in the device B, the communication completion flag indicating that the provision of the service between the devices is completed is set in a state where it is cleared.

  First, the user brings device A and device B close to each other (touch operation) and sets them in a close state (S401). Next, the device A and the device B execute processing (authentication processing) for establishing a connection (CNL connection) between the device A and the device B (S402). Specifically, device B transmits a connection request. Receiving this connection request, device A transmits a response to the connection request to device B. With the above processing, a connection is established between device A and device B.

  The devices A and B that have established the connection execute a negotiation process (S403). In the negotiation process, as in the processes from S203a to S203c in FIG. 7, the device A and the device B execute mode arbitration, service negotiation, and service synchronization.

  Specifically, the device B set to the flexible mode executes mode arbitration that changes its mode according to the mode set to the device A that is the communication partner device. Here, since device A is set to the reactive mode, device B transitions its own mode from the flexible mode to the proactive mode. Device A and device B execute service negotiation for determining a service to be executed between device A and device B. Specifically, the device B requests the device A for information indicating a service group that the device A can provide. When the device B receives information on the service group that the device A can provide from the device A, the device B presents a list listing each service included in the service group to the user. Then, the user selects a service to be used from the list of presented services. Thereby, a service to be executed between the device A and the device B is determined. The service executed between device A and device B may be a predetermined service. Device A and device B then perform service synchronization to execute the determined service. Thereby, the execution of the service is started between the device A and the device B.

  When the negotiation process described above is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S404). When the execution of the service is completed, device B transitions from the proactive mode to the flexible mode. In addition, the device B sets a communication completion flag indicating that the execution of the service is completed. Note that the connection between the device A and the device B (CNL connection) is maintained.

  During the period when the communication completion flag is set, the device B executes standby processing for waiting for processing for starting provision of a new service. In other words, the device B is set to a wait state that waits for the start of provision of a new service during the period when the communication completion flag is set.

  Then, when the device A and the device B are separated and the proximity state is released, the connection between the device A and the device B is disconnected. In response to the disconnection between device A and device B, device B clears the communication completion flag.

  With the above processing, provision of unnecessary services can be started after the execution of services between devices is completed until the devices are separated (the proximity state between devices is released). Can be suppressed.

  FIG. 10 is a sequence diagram when a new service is provided in response to a request from the user after the provision of one service is completed between devices. Here, it is assumed that a service start request is transmitted from device B set to flexible mode to device A set to reactive mode. In the initial state, device A is set to the reactive mode, and device B is set to the flexible mode. Further, in the device B, the communication completion flag indicating that the provision of the service between the devices is completed is set in a state where it is cleared.

  First, the user brings the device A and the device B close to each other (touch operation), and sets the proximity state (S501). Next, the device A and the device B execute an authentication process for establishing a connection (CNL connection) between the device A and the device B (S502). For example, device B transmits a connection request. Receiving this connection request, device A transmits a response to the connection request to device B. With the above processing, a connection is established between device A and device B.

  The devices A and B that have established the connection execute a negotiation process (S503). In the negotiation process, as in the processes from S203a to S203c in FIG. 7, the device A and the device B execute mode arbitration, service negotiation, and service synchronization.

  Specifically, the device B set to the flexible mode executes mode arbitration that changes its mode according to the mode set to the device A that is the communication partner device. Here, since device A is set to the reactive mode, device B transitions its own mode from the flexible mode to the proactive mode. Device A and device B execute service negotiation for determining a service to be executed between device A and device B. Specifically, the device B requests the device A for information indicating a service group that the device A can provide. When the device B receives information on the service group that the device A can provide from the device A, the device B presents a list listing each service included in the service group to the user. Then, the user selects a service to be used from the list of presented services. Thereby, a service to be executed between the device A and the device B is determined. The service executed between device A and device B may be a predetermined service determined in advance. Device A and device B then perform service synchronization to execute the determined service. Thereby, the execution of the service is started between the device A and the device B.

  When the negotiation process described above is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S504). When the execution of the service is completed, device B transitions from the proactive mode to the flexible mode. In addition, the device B sets a communication completion flag indicating that the execution of the service is completed. Note that the connection between the device A and the device B (CNL connection) is maintained.

  During the period when the communication completion flag is set, the device B executes standby processing for waiting for processing for starting provision of a new service. In other words, the device B is set to a wait state that waits for the start of provision of a new service during the period when the communication completion flag is set.

  If a wait cancel request is input by the user during the period when the communication completion flag is set, the device B cancels the wait state of the device B in response to the wait cancel request (S505). Device B clears the communication completion flag. The wait cancellation request is input by the user selecting an application, for example.

  Then, device A and device B execute the negotiation process again (S506). In this negotiation process, the same process as the negotiation process in S503 is executed. Therefore, the device A and the device B execute mode arbitration, service negotiation, and service synchronization processing.

  When the negotiation process is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S507). When the execution of the service is completed, device B transitions from the proactive mode to the flexible mode. In addition, the device B sets a communication completion flag indicating that the execution of the service is completed. Note that the connection between the device A and the device B (CNL connection) is maintained.

  With the above processing, it is possible to prevent the provision of unnecessary services from the time when the execution of the service between the devices is completed until the user inputs a wait release request on the device B. it can. In other words, after the execution of the service between the devices is completed, the provision of the service can be started in response to the user inputting the service start request.

  FIG. 11 shows another sequence diagram in the case where a new service is provided in response to a user request after the provision of one service is completed between devices. Here, it is assumed that a service start request is transmitted from device A set to proactive mode to device B set to flexible mode. In the initial state, device A is set to the reactive mode, and device B is set to the flexible mode. Further, in the device B, the communication completion flag indicating that the provision of the service between the devices is completed is set in a state where it is cleared.

  First, the user selects an application program for performing close proximity wireless communication on the device A, brings the device A and the device B close to each other (touch operation), and sets the close state (S601). The device A for which the application program has been selected transitions from the reactive mode in which the service start request is received from the external device to the proactive mode in which the service start request is transmitted to the external device.

  Next, the device A and the device B execute processing (authentication processing) for establishing a connection (CNL connection) between the device A and the device B (S602). For example, device A transmits a connection request. Upon receiving this connection request, device B transmits a response to the connection request to device A. With the above processing, a connection is established between device A and device B.

  The devices A and B that have established the connection execute a negotiation process (S603). In the negotiation process, similarly to the processes from S103a to S103c in FIG. 6, the devices A and B execute mode arbitration, service negotiation, and service synchronization.

  Specifically, the device B set to the flexible mode executes mode arbitration that changes its mode according to the mode set to the device A that is the communication partner device. Here, since the device A is set to the proactive mode, the device B changes its mode from the flexible mode to the reactive mode. Device A and device B execute service negotiation for determining a service to be executed between device A and device B. Here, the service designated by the device A set to the proactive mode, that is, the service corresponding to the application program selected by the user is determined as the service executed between the device A and the device B. . Device A and device B execute service synchronization for executing the determined service. Thereby, the execution of the service is started between the device A and the device B.

  When the above-described negotiation process is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S604). When the execution of the service is completed, the device A transitions from the proactive mode to the reactive mode, and the device B transitions from the reactive mode to the flexible mode. In addition, the device B sets a communication completion flag indicating that the execution of the service is completed. Note that the connection between the device A and the device B (CNL connection) is maintained.

  During the period when the communication completion flag is set, the device B executes standby processing for waiting for processing for starting provision of a new service. In other words, the device B is set to a wait state that waits for the start of provision of a new service during the period when the communication completion flag is set.

  When the user selects an application program for performing close proximity wireless communication on the device A during the communication completion flag is set, the device A transmits a service start request to the device B (S605). In response to the service start request received from device A, device B cancels the wait state of device B. Device B clears the communication completion flag. Then, device A and device B execute the negotiation process again (S606). In this negotiation process, the same process as the negotiation process in S603 is executed. Therefore, the device A and the device B execute mode arbitration, service negotiation, and service synchronization processing.

  When the negotiation process is completed, a service is executed between the device A and the device B, and communication such as data transmission / reception is performed (S607). Device A transitions from proactive mode to reactive mode, and device B transitions from reactive mode to flexible mode. In addition, the device B sets a communication completion flag indicating that the execution of the service is completed. Note that the connection between the device A and the device B (CNL connection) is maintained.

  With the above processing, it is possible to prevent unnecessary services from being started after device B completes service execution and until device B receives a service start request from device A. Can do. In other words, after the execution of the service between the devices is completed, the provision of the service can be started in response to the user inputting the service start request.

  FIG. 12 is a state transition diagram illustrating an example of state transition of the proximity wireless communication by the electronic device 10.

  When the electronic device 10 is set in the proximity state with the external device, the electronic device 10 transitions from the disconnected state 60 in which the CNL connection is disconnected to the CNL connection established state 61 in which the CNL connection is established. The CNL connection establishment state 61 is further defined as one of a negotiation state 611, a service execution state 612, and a wait state 613. That is, while in the CNL connection establishment state 61, the electronic device 10 transitions to the negotiation state 611, the service execution state 612, and the wait state 613.

  When the state transitions from the disconnected state 60 to the CNL connection established state 61, the electronic device 10 first enters the negotiation state 611. In the negotiation state 611, as described above, negotiation processing such as mode identification, service negotiation, and service synchronization is executed. In response to the completion of the negotiation process, the electronic device 10 transitions from the negotiation state 611 to the service execution state 612.

  In the service execution state 612, processing corresponding to the service determined in the negotiation processing is executed. In response to the completion of execution of the service, the electronic device 10 transitions from the service execution state 612 to the wait state 613.

  In the wait state 613, a waiting process for waiting for the start of the service is performed until an event such as input of a service start request (wait release request) by the user (request from a higher-level application) or reception of a service start request from an external device occurs. Executed. Therefore, in response to the service start request being input by the user or the service start request being received from the external device, the electronic device 10 transitions from the wait state 613 to the negotiation state 611.

  Note that the proximity of the electronic device 10 and the external device during the period in which the electronic device 10 is in the CNL connection establishment state 61, that is, in the period in which the electronic device 10 is in the negotiation state 611, the service execution state 612, or the wait state 613. When the state is released, the connection between the electronic device 10 and the external device is released, and the electronic device 10 transitions to the disconnected state 60.

  As described above, after executing the service specified in the service execution state 612, the electronic device 10 transitions to the wait state 613. In this wait state 613, the electronic device 10 waits to execute a negotiation process for starting a new service until there is a service start request from a user or an external device. Thereby, it is possible to suppress the start of unnecessary service execution between devices set in the proximity state. Note that the standby processing based on the communication completion flag described with reference to FIGS. 8 to 11 may be performed based on the state transition as shown in FIG. In that case, the electronic device 10 manages the transition of the state of the close proximity wireless communication with the communication partner device, and executes processing according to each state. When the state transitions to the wait state 613, as described above, the standby process that waits for the process for starting a new service is executed, which is the same as the case where the standby process based on the communication completion flag is executed. An effect can be obtained.

  Next, the relationship between the mode set in the PCL 40 of each device and the service executed between the devices will be described with reference to FIG. Here, it is assumed that a service is executed between device A and device B. The protocol conversion layer 40 of the device A and the protocol conversion layer 40 of the device B are set to any one of a proactive mode, a flexible mode, and a reactive mode, respectively.

  First, description will be given focusing on the case where the device A is set to the proactive mode.

  When device A is set to proactive mode and device B is set to proactive mode, both device A and device B transmit a service start request to the communication partner device. It does not respond to service start requests by other devices. For this reason, the service is not started between the device A and the device B, and an error occurs.

  When the device A is set to the proactive mode and the device B is set to the flexible mode, both the device A and the device B transmit a service start request to the communication partner device. The device B set in the flexible mode receives the service start request from the device A, transitions from the flexible mode to the reactive mode, and returns a response to the service start request to the device A. Therefore, the service designated by the device A set to the proactive mode is executed between the device A and the device B.

  When device A is set to the proactive mode and device B is set to the reactive mode, device A transmits a service start request to the communication partner device. The device B set to the reactive mode receives this service start request and returns a response to the service start request to the device A. Therefore, the service designated by the device A set to the proactive mode is executed between the device A and the device B.

  Next, the case where the device A is set to the flexible mode will be described.

  When the device A is set to the flexible mode and the device B is set to the proactive mode, both the device A and the device B transmit a service start request to the communication partner device. The device A set in the flexible mode receives the service start request from the device B, transits from the flexible mode to the reactive mode, and returns a response to the service start request to the device B. Therefore, the service designated by the device B set to the proactive mode is executed between the device A and the device B.

  When the device A is set to the flexible mode and the device B is set to the flexible mode, both the device A and the device B transmit a service start request to the communication partner device. However, since the own mode is set to the flexible mode and the mode of the communication partner device is also set to the flexible mode, the service is not started between the device A and the device B, and an error occurs.

  When device A is set in the flexible mode and device B is set in the reactive mode, device A transmits a service start request to the communication partner device. The device B set to the reactive mode receives the service start request from the device A and returns a response to the service start request to the device A. The device A transitions from the flexible mode to the proactive mode. Between the device A and the device B, a service designated in advance by the device A set in the proactive mode is executed. Note that a list of services that can be executed by the device B can be presented to the user on the device A, and the user can select a service to be executed between devices.

  Finally, a case where the device A is set to the reactive mode will be described.

  When device A is set to the reactive mode and device B is set to the proactive mode, device B transmits a service start request to the communication partner device. The device A set to the reactive mode receives the service start request from the device B and returns a response to the service start request to the device B. Therefore, the service designated by the device B set to the proactive mode is executed between the device A and the device B.

  When device A is set in the reactive mode and device B is set in the flexible mode, device B transmits a service start request to the communication partner device. The device A set in the reactive mode receives the service start request from the device B and returns a response to the service start request to the device B. Device B then transitions from the flexible mode to the proactive mode. Between the device A and the device B, a service designated in advance by the device B set to the proactive mode is executed. It is also possible to present a list of services that can be executed by device A to the user on device B, and the user can select a service to be executed between the devices.

  When device A is set to reactive mode and device B is set to reactive mode, neither device A nor device B transmits a service start request to the communication partner device. . For this reason, the service is not executed between the device A and the device B.

  Next, an example of a communication processing procedure according to the proximity wireless communication method will be described with reference to the flowchart of FIG.

  First, the electronic device 10 determines whether or not a touch operation for bringing the electronic device 10 and an external device closer is performed (step S701). Specifically, the electronic device 10 transmits a connection request to the external device, and determines whether a response to the connection request has been received from the external device or whether a connection request has been received from the external device.

  When a touch operation that allows the electronic device 10 and the external device to approach each other is performed (YES in step S701), the electronic device 10 executes an authentication process with the external device (step S702). The electronic device 10 identifies an external device that is a communication partner device. Then, the electronic device 10 executes a negotiation process with the external device (step S703). In the negotiation process, the electronic device 10 executes a mode arbitration process, a service negotiation process, and a service synchronization process. Specifically, the electronic device 10 controls the mode set in the PCL 40 by mode arbitration. In addition, the electronic device 10 determines a service to be executed between the electronic device 10 and the external device, and starts the service.

  When the negotiation process is completed, the electronic device 10 executes the service determined by the negotiation process (step S704).

  Next, the electronic device 10 determines whether the service executed with the external device is completed (step S705). When the service executed with the external device is completed (YES in step S705), the electronic device 10 repeats the processes in and after step S702 again. That is, while the electronic device 10 and the external device are set in the proximity state, the provision of services is repeated between the electronic device 10 and the external device.

  With the above processing, it is possible to repeatedly provide a service between devices set in the proximity state. However, when the provision of a new service is automatically started after one service is completed, it is possible to save the user from having to perform the operation, while the service can be performed even between devices that are simply left in proximity. There is a possibility that the service is started and an unexpected service is executed. FIG. 15 is a flowchart illustrating an example of a communication processing procedure when the close proximity wireless transfer device 104 is controlled to start providing a service only when a service start request is received.

  First, the electronic device 10 determines whether or not a touch operation for bringing the electronic device 10 and an external device closer is performed (step S801). Specifically, the electronic device 10 transmits a connection request to the external device, and determines whether a response to the connection request has been received from the external device or whether a connection request has been received from the external device.

  When a touch operation that allows the electronic device 10 and the external device to approach each other is performed (YES in step S801), the electronic device 10 executes an authentication process with the external device (step S802). The electronic device 10 identifies an external device that is a communication partner device. Then, the electronic device 10 executes a negotiation process with the external device (step S803). In the negotiation process, the electronic device 10 executes a mode arbitration process, a service negotiation process, and a service synchronization process. Specifically, the electronic device 10 controls the mode set in the PCL 40 by mode arbitration. In addition, the electronic device 10 determines a service to be executed between the electronic device 10 and the external device, and starts the service.

  When the negotiation process is completed, the electronic device 10 executes the service determined by the negotiation process (step S804).

  Next, the electronic device 10 determines whether the service executed with the external device is completed (step S805). When the service executed with the external device is completed (YES in step S805), the electronic device 10 sets a flag indicating the completion of the service (step S806). That is, the electronic device 10 shifts to a wait state waiting for processing for starting a new service.

  After shifting to the wait state, the electronic device 10 determines whether or not a service start request event for requesting the start of a new service has occurred (step S807). The service start request event occurs, for example, when a service start request is input by a user or when a service start request is received from an external device.

  If a service start request event has occurred (YES in step S807), the electronic device 10 clears the flag (step S808). Then, the electronic device 10 cancels the wait state and executes a process for starting a new service. That is, the electronic device 10 executes the processes after step S803 again.

  When the service start request event has not occurred (NO in step S807), the electronic device 10 determines whether or not the proximity state with the communication partner device has been released (step S809). Specifically, the electronic device 10 determines whether the CNL connection established with the communication partner device has not been disconnected. When the proximity state with the communication partner device has not been released (NO in step S809), the processes in and after step S807 are executed again. When the proximity state with the communication partner device is released (YES in step S809), the electronic device 10 clears the flag and releases the wait state (step S810).

  With the above processing, after the provision of one service between devices is completed, provision of a new service is started only when there is a service start request by the user, and the start of unnecessary services is suppressed. Can do.

  As described above, according to the present embodiment, provision of unnecessary services can be suppressed. When the electronic device 10 and the external device are set in the proximity state, the electronic device 10 establishes a CNL connection with the external device and executes a negotiation process for starting to provide a service. Then, the electronic device 10 executes the service determined by the negotiation process. When the execution of the service is completed, the electronic device 10 transitions to a wait state and waits for a service start request input by the user or a service start request transmitted from an external device. Then, in response to the input (reception) of the service start request, the electronic device 10 executes a process for starting a new service. With the above-described processing, after the execution of one service is completed, provision of a new service is automatically started without an instruction from the user, and it is possible to suppress unnecessary services from being executed.

  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.

  103a ... proximity wireless communication control program, 201 ... data communication unit, 40 ... protocol conversion layer, 401 ... control unit, 402 ... CNL connection monitoring unit, 403 ... negotiation processing unit, 404 ... mode control unit, 405 ... service processing unit, 406: Standby processing unit, 410: Database, 410a ... CNL connection state, 410b ... Connection mode, 50 ... Application layer, 501 ... Application unit.

Claims (4)

A communication module for performing close proximity wireless communication;
A connection establishment means for establishing a connection between the communication module and the external device when the communication module and the external device are in a proximity state;
When an application program using near field communication is selected, the communication module set in the second mode for receiving a service start request from the communication partner device is transmitted to the communication partner device. Mode control means for setting to the first mode;
When the communication module is set to the first mode, a service start request is transmitted to the external device, and the communication module and the external device are negotiated between the communication module and the external device. A negotiation means for determining the service to execute with
Electronic equipment comprising service execution means for executing the determined service.   2. The electronic apparatus according to claim 1, wherein the negotiation unit determines a service corresponding to the application program as a service to be executed between the communication module and the external device.   2. The electronic device according to claim 1, wherein the mode control unit sets the communication module set to the first mode to the second mode after execution of the determined service is completed. 3. machine. A communication control method for controlling communication between an electronic device including a communication module that performs close proximity wireless communication and an external device,
A connection establishing step for establishing a connection between the communication module and the external device when the communication module and the external device are in a proximity state;
When an application program using near field communication is selected, the communication module set in the second mode for receiving a service start request from the communication partner device is transmitted to the communication partner device. A mode control step to set to the first mode;
When the communication module is set to the first mode, a service start request is transmitted to the external device, and the communication module and the external device are negotiated between the communication module and the external device. A negotiation step to determine the service to execute with
And a service execution step of executing the determined service.

Images