JP2012231429A - Communication device, control method of communication device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the number of required processing steps when a collision occurs in processing requested by both or one device in a communication device which establishes a radio link by being close to an opposite device and performs data communication.SOLUTION: The communication device which establishes the radio link and communicates with the opposite device comprises: a detection unit for, when the radio link with the opposite device is established, detecting occurrence of a request collision caused by transmission of a connection request for establishing the radio link by the communication device to the opposite device and transmission of a connection request to the communication device by the opposite device; a determination unit for determining the processing order of the processing requested by the communication device and the processing requested by the opposite device on the basis of information included in the connection requests; and a communication unit for communicating with the opposite device and executing the processing in the processing order determined by the determination unit when the request collision is detected.

Description

  The present invention relates to a communication device, a communication device control method, and a program, and in particular, establishes a wireless link in a one-to-one manner by performing close communication so that the distance to the partner device is within a predetermined range. The present invention relates to a communication device to be performed, a communication device control method, and a program.

  In recent years, contactless communication (proximity wireless communication) such as NFC (Near Field Communication) and TransferJet (registered trademark) is known. In these non-contact communications, the communication distance is very short, and the wireless links are connected when the devices that communicate with each other are within a few centimeters (for example, NFC is within 10 cm, TransferJet (registered trademark) is within 3 cm). It is controlled so that the radio link is disconnected when it is moved away.

  Note that TransferJet (registered trademark) assumes that devices perform data communication on a one-to-one basis, and currently, a white paper describing use cases and the like is disclosed (see Non-Patent Document 1). Non-Patent Document 1 discloses that TransferJet (registered trademark) allows users to transmit data by bringing their devices close to each other. As a method for data transmission by TransferJet (registered trademark), a method of performing data communication by allowing a user to perform an operation such as selection of transmission data and then approaching to a counterpart device can be considered. This is because, in non-contact communication, the radio link is disconnected if the distance between the devices is out of the communication range even a little, so that it is difficult to perform operations such as selection of transmission data while maintaining the connection of the radio link. Non-Patent Document 1 also discloses that when such data transmission is performed, negotiation for obtaining an agreement to perform data transmission between the two devices is performed.

  In addition, a technique is disclosed in which both devices transmit data to each other using this negotiation (see Patent Document 1). A specific data communication method will be described below. The user operates both devices to select transmission target data and starts a transmission application. In this state, when the devices are wirelessly connected, by exchanging information indicating the presence / absence of data to be transmitted between the devices, it is recognized that both devices transmit data to each other, and each data is continuously received. Perform transmission.

JP 2010-283951 A

“Worlds are About to Touch” [online] [searched on April 13, 2011], Internet <URL: http: // www. transferjet. org / tj / transferjet_whitepaper. pdf>

  In the case of the data communication method according to Patent Document 1, the information indicating that there is no transmission target data is notified to the partner apparatus even when there is no transmission target data regardless of the presence or absence of a connection request conflict. Therefore, transmission / reception of information indicating the presence / absence of transmission target data and processing for analyzing the information are required between each device and the actual transmission of data after the devices are wirelessly connected. .

  However, non-contact communication such as TransferJet (registered trademark) is often mounted on a portable terminal having a low CPU capability, and therefore, it is required to minimize the number of processing steps.

  In view of the above problems, the present invention is necessary in a communication device that establishes a wireless link by making it close to a partner device and performs data communication when a collision occurs in processing required by both or one of the devices. An object is to provide a technique for reducing the number of processing steps.

A communication device according to the present invention that achieves the above object is as follows.
A communication device that establishes a wireless link with a counterpart device and communicates,
The occurrence of a request collision caused by the communication device transmitting a connection request for establishing a wireless link to the partner device and the partner device transmitting the connection request to the communication device. Detecting means for detecting when is established;
Determining means for determining a processing order of processing requested by the communication device and processing requested by the counterpart device based on information included in the connection request;
When the request collision is detected, communication means for performing processing by communicating with the counterpart device in the processing order determined by the determining means;
It is characterized by providing.

  According to the present invention, in a communication device that establishes a wireless link by making it close to a partner device and performs data communication, when a collision occurs in the processing required by both or one of the devices, the required number of processing steps is set. Can be reduced.

The functional block diagram of the communication apparatus which concerns on 1st Embodiment. The system block diagram provided with the communication apparatus which concerns on 1st and 2nd embodiment. The flowchart which shows the process sequence of 1st and 2nd embodiment. The flowchart which shows the process sequence of 1st and 2nd embodiment. The flowchart which shows the process sequence of 1st Embodiment. The flowchart which shows the process sequence of 1st and 2nd embodiment. The sequence diagram of a 1st embodiment. The sequence diagram of a 1st embodiment. The functional block diagram of the communication apparatus which concerns on 2nd Embodiment. The flowchart which shows the process sequence of 2nd Embodiment. The flowchart which shows the process sequence of 2nd Embodiment. The figure which shows the example of a display of 2nd Embodiment.

(First embodiment)
With reference to FIG. 1, an example of a functional block diagram of the communication apparatus 101 according to the first embodiment having a proximity wireless communication (non-contact communication) function will be described. The communication device 101 establishes a wireless link with a counterpart device existing within a predetermined distance range and communicates data. The communication apparatus 101 includes a communication control unit 102, a connection request collision control unit 103, a control message creation unit 104, a control message confirmation unit 105, a user interface unit 106, an application unit 107, an application manager unit 108, A storage unit 109, a process execution order determination unit 110, a multi-process execution confirmation unit 111, and a timing unit 112 are provided.

  The communication control unit 102 performs establishment and disconnection of a wireless link and data transmission control when transmitting and receiving data wirelessly using proximity wireless transfer. TransferJet (registered trademark), NFC, or the like can be applied as a proximity wireless transfer method. In the close proximity wireless communication according to the present embodiment, it is assumed that, when transmission / reception of a connection request and connection response is completed, establishment (connection) of a wireless link is completed and data communication is possible. Note that the device on the side that transmitted the connection request is referred to as a master, and the device on the side that transmitted the connection response is referred to as a slave.

  The connection request collision control unit 103 detects that both the own device and the partner device have transmitted a connection request. When a connection request collision is detected, a device ID (device identification) uniquely assigned to each device is detected. Either device sends a connection response according to the result of comparing the size of (information), and makes it a slave.

  The control message creation unit 104 creates a request message for requesting control of the counterpart device and a response message in response to a control request from the counterpart device. In this embodiment, it is assumed that the master device can transmit a request message and the slave device can transmit a response message. In addition, a connection request, a disconnection request, an execution process acquisition request, and a process execution request are defined as request messages, and a connection response and an execution process acquisition response are defined as response messages. The connection request is a message for requesting connection of near field communication to the counterpart device. The disconnection request is a message that requests the counterpart device to disconnect the proximity wireless communication. The execution process acquisition request is a message requesting an execution process acquisition response to the slave. The process execution request is a message that includes information indicating the process to be executed and requests the slave to execute the process. The connection response is a message that notifies the partner device that a link for close proximity wireless communication has been established. The execution process acquisition response is a message indicating a process according to an instruction from a user (operator) in the slave. The message indicating the process execution request and the execution process acquisition response includes information indicating the direction of data transfer such as “PUSH transmission” and “PUSH reception”. In addition, information indicating data transfer protocols such as “OBEX” and “SCSI”, information indicating data types such as “image file” and “text file”, and operations other than data transfer such as “image playback” and “image printing” May also be included.

  The control message confirmation unit 105 confirms the content of the control message received from the counterpart device. The user interface unit 106 displays an image, an operation menu, a data transmission status, and various other information, and accepts various operations by a user (operator). In response to a user instruction from the user interface unit 106, the application unit 107 activates an application such as transmission or reception, and processes each application. Each application can also notify the application manager unit 108 that the application has ended. The application manager unit 108 mediates messages between the application unit 107 and the communication control unit 102, and controls application activation in the application unit 107 and accepts an end notification.

  The storage unit 109 stores data to be transmitted, data received from the partner device, and various other information. For example, the storage unit 109 includes information indicating whether the device operates on the master side or the slave side of data transmission, information indicating that a connection request collision has been detected, information on the application startup order, and the like. Remembered.

  The process execution order determination unit 110 determines the execution order of the process instructed by the user on the own apparatus side and the process instructed on the counterpart apparatus side based on information included in the connection request. The multi-processing execution confirmation unit 111 confirms with the user using the user interface unit 106 that the two processes are performed when the processing of both apparatuses is performed. The time measuring unit 112 is used as a timer for measuring the duration of link establishment by the communication control unit 102.

  All the functional blocks have a mutual relationship in terms of software or hardware. Further, the configuration of the functional blocks described above is an example, and a plurality of functional blocks may constitute one functional block, or any functional block may be further divided into blocks that perform a plurality of functions. .

  FIG. 2 is a diagram illustrating a configuration of a system including a communication device according to the present embodiment. The wireless communication device 201 and the wireless communication device 203 can communicate with each other via the proximity wireless transfer interface 202 and the proximity wireless transfer interface 204. Both the wireless communication device 201 and the wireless communication device 203 have the functional block configuration of FIG. The proximity wireless transfer interface may be built in the device or externally attached by a cable or the like.

  3 to 6 are flowcharts showing the procedure of the operation in this embodiment. FIG. 7 shows a sequence when a data transmission operation is performed in both the wireless communication apparatus 201 and the wireless communication apparatus 203. FIG. 8 shows a sequence when a data transmission operation is performed in the wireless communication apparatus 201. Hereinafter, the flowcharts of FIGS. 3 to 6 and the sequences of FIGS. 7 and 8 will be described.

  In the following description, focusing on the wireless communication device 201, the wireless communication device 201 is defined as the own device and the wireless communication device 203 is defined as the partner device. However, which device is the own device or the partner device is described. Any operation is possible.

  First, the relationship between FIG. 3 and FIGS. 4 to 6 will be described. In FIG. 3, as an initial state, it is assumed that the own device 201 and the partner device 203 are arranged at a sufficiently long distance that short-range wireless communication by the close proximity wireless transfer interface 202 and the close proximity wireless transfer interface 204 is not possible. In FIG. 3, when the entire process starts, first, a connection process is performed in S301. Details of this connection processing are shown in FIG. After the connection process is completed, in S302, the connection request collision control unit 103 determines whether or not a connection request collision has occurred. When it is determined that a connection request collision has occurred (S302; YES), the process proceeds to S303. On the other hand, if it is determined that a connection request collision has not occurred (S302; NO), the process proceeds to S304. In S303, a plurality of processes are performed. Details of this multi-processing implementation are shown in FIG. In S304, a single process is performed. Details of this multi-processing implementation are shown in FIG. After S303 or S304, the entire process ends.

  In FIG. 4, when the connection process starts, in step S <b> 401, the own apparatus 201 determines whether or not an instruction related to processing such as selection of transmission data and a transmission instruction has been performed by operating the user interface 106. When it is determined that an instruction has been given (S401; YES), the process proceeds to S402. On the other hand, when it is determined that no instruction has been given (S401; NO), the process proceeds to S409.

  In step S <b> 402, the communication control unit 102 of the own device 201 transmits a connection request including the device ID information of the own device 201 to the partner device 203. In this state, when the user brings both devices close to each other so that the device 201 and the partner device 203 are within a predetermined distance range, the communication control unit 102 of the device 201 issues a connection request from the partner device 203 in S403. It is determined whether or not it has been received. If it is determined that a connection request has been received (S403; YES), the process proceeds to S404. On the other hand, when it is determined that a connection request has not been received (S403; NO), the process proceeds to S407.

  In S <b> 404, the connection request collision control unit 103 of the own device 201 determines that the connection request has collided, and whether or not the device ID of the own device is larger than the device ID included in the connection request received from the partner device 203. Determine. When it is determined that the device ID of the own device 201 is larger than the device ID of the counterpart device 203 (S404; YES), the process proceeds to S405. On the other hand, when it is determined that the device ID of the own device 201 is smaller than the device ID of the counterpart device 203 (S404; NO), the process proceeds to S406.

  In S405, the connection request collision control unit 103 of the own device 201 stores information indicating that the connection request has collided and information indicating that the own device 201 is the master in the storage unit 109, and ends the connection process. . In step S406, the connection request collision control unit 103 of the own device 201 stores information indicating that the connection request has collided and information indicating that the own device 201 is a slave in the storage unit 109, and ends the connection process. .

  In step S <b> 407, the communication control unit 102 of the own device 201 determines whether a connection response from the partner device 203 has been received. If it is determined that a connection response has been received (S407; YES), the process proceeds to S408. On the other hand, when it is determined that the connection response has not been received (S407; NO), the process returns to S403.

  In step S408, the communication control unit 102 of the own device 201 stores information indicating that the own device 201 is the master in the storage unit 109, and ends the connection process. In step S409, the communication control unit 102 of the own device 201 determines whether a connection request from the partner device 203 has been received.

  When it is determined that the connection request has been received (S409; YES), the process proceeds to S410. On the other hand, when it is determined that the connection request has not been received (S409; NO), the process returns to S401.

  In step S <b> 410, the communication control unit 102 of the own device 201 transmits a connection response to the partner device 203. Thereafter, in S411, the communication control unit 102 of the own device 201 stores information indicating that the own device 201 is a slave in the storage unit 109, and ends the connection process.

  When the connection process shown in FIG. 4 is completed, in S302 of FIG. 3, the connection request collision control unit 103 refers to the storage unit 109 and determines whether there is a connection request collision. If there is a connection request conflict (S302; YES), it is considered that there has been an instruction for processing by the user in both apparatuses, so the process proceeds to S303, and a process of performing a plurality of processes shown in FIG. 5 is started. .

  On the other hand, if there is no collision of connection requests (S302; NO), it is considered that the user has instructed processing only on one device, so the process proceeds to S304, and the single processing shown in FIG. 6 is performed. Start the process.

  First, the operation procedure of the multi-process execution process will be described with reference to the flowchart of FIG.

  In step S <b> 501, the own apparatus 201 refers to the storage unit 109 and determines whether the own apparatus 201 is a master. If it is determined that the device 201 is the master (S501; YES), the process proceeds to S502. On the other hand, when it is determined that the own device is a slave (S501; NO), the process proceeds to S513.

  In step S <b> 502, the communication control unit 102 of the own device 201 transmits the execution process acquisition request message created by the control message creation unit 104 to the counterpart device 203.

  In step S503, the communication control unit 102 of the own apparatus 201 determines whether or not an implementation process acquisition response message has been received. When it is determined that the execution process acquisition response message has been received (S503; YES), the process proceeds to S504. On the other hand, if it is determined that the implementation process acquisition response message has not been received (S503; NO), the process waits until it is received.

  In step S <b> 504, the control message confirmation unit 105 of the own device 201 confirms the processing instructed by the counterpart device 203 from the received execution process acquisition response message. Next, in S505, the processing execution order determination unit 110 of the own device 201 first performs the processing instructed on the master side (the own device 201 side), and the processing instructed on the slave side (the counterpart device 203 side). The processing order is determined to be executed later.

  It should be noted that the processing order may be determined such that processing that does not require user operation of the user interface unit 106 during the processing is performed first, and processing that requires user operation during processing is performed later. In addition, the execution order may be determined according to the size of data to be transmitted in both apparatuses. For example, the processing order may be determined so that the processing with the smaller data size is performed first. In these cases, the connection request may include operation information indicating whether or not the user needs to operate the user interface unit 106 and size information indicating the data size.

  In step S <b> 506, the communication control unit 102 of the own device 201 transmits a processing execution request message created by the control message creating unit 104 including information indicating processing instructed by the own device 201 to the partner device 203.

  In S507, the application manager unit 108 of the own device 201 further notifies the application unit 107 of the start of processing, whereby the application unit 107 activates an application corresponding to the processing instructed by the own device 201, and Processing is performed.

  In step S <b> 508, when the process ends, the application unit 107 of the apparatus 201 notifies the application manager unit 108 of the end of the process.

  In step S <b> 509, the communication control unit 102 of the own apparatus 201 transmits a process execution request message including information indicating the process instructed by the partner apparatus 203 to the partner apparatus 203. Further, the application manager unit 108 of the own device 201 notifies the application unit 107 of the start of processing.

  In step S <b> 510, the application unit 107 of the own apparatus 201 activates an application corresponding to the process instructed by the counterpart apparatus 203 and performs the process. In step S511, the application unit 107 of the device 201 notifies the application manager unit 108 of the end of processing.

  In step S <b> 512, the communication control unit 102 of the own device 201 transmits a disconnection request to the partner device 203. Thereafter, the multi-process execution process is terminated.

  In step S <b> 513, the communication control unit 102 of the own device 201 determines whether a request message has been received from the counterpart device 203. If it is determined that the request message has been received from the counterpart device 203 (S513; YES), the process proceeds to S514. On the other hand, if it is determined that a request message has not been received from the counterpart device 203 (S513; NO), the system waits until it is received.

  In step S514, the control message confirmation unit 105 of the own device 201 confirms the content of the request message. When the content of the request message is an execution process acquisition request, the process proceeds to S515. When the content of the request message is a processing execution request, the process proceeds to S516. If the content of the request message is a disconnection request, the multi-process execution process is terminated.

  In step S <b> 515, the communication control unit 102 of the own device 201 transmits an execution process acquisition response message created by the control message creation unit 104 including information indicating the process instructed by the own device 201 to the partner device 203. Thereafter, the process returns to S513.

  In step S <b> 516, the application manager unit 108 of the own apparatus 201 notifies the application unit 107 of processing start. Then, the application unit 107 activates an application corresponding to the process indicated in the process execution request.

  In S517, when the process ends, the application unit 107 notifies the application manager unit 108 of the end of the process. Thereafter, the process returns to S513. Furthermore, with reference to FIG. 7, the sequence of the multiple processing execution process will be described. Here, as an example, the own device 201 will be described as the master side, and the counterpart device 203 will be described as the slave side. In addition, the process instructed by the own apparatus 201 is data PUSH from the own apparatus 201 to the partner apparatus 203, and the process instructed by the partner apparatus 203 is data PUSH from the partner apparatus 203 to the own apparatus 201.

  First, when an execution process acquisition request is transmitted from the own apparatus 201 to the counterpart apparatus 203 (F701), the counterpart apparatus 203 sends an execution process acquisition response indicating the processing of data PUSH from the counterpart apparatus 203 to the own apparatus 201. It transmits to 201 (F702).

  Next, the own apparatus 201 transmits a process execution request indicating the process instructed by the own apparatus 201 in accordance with the process execution order determined by the process execution order determining unit 110 (F703).

  As a result, in both apparatuses, a transmission / reception application for executing processing of data PUSH from the own apparatus 201 to the partner apparatus 203 is activated, and the process is performed (F704).

  When the PUSH process instructed by the own device 201 is completed, a PUSH completion notification is transmitted from the own device 201 to the partner device 203 (F705). Further, the own device 201 transmits a processing execution request indicating the processing instructed by the partner device 203 to the partner device 203 (F706), and the processing of the data PUSH from the partner device 203 to the own device 201 is performed in both devices. The transmission / reception application for execution is activated and the processing is performed (F707).

  When the PUSH process instructed by the partner apparatus 203 is completed, the partner apparatus 203 transmits a PUSH completion notification to the self apparatus 201 (F708), and the self apparatus 201 transmits a disconnection request to the partner apparatus (203) (F709). . The process ends here. Next, the operation procedure of the single process execution process will be described with reference to FIG.

  In step S <b> 601, the own apparatus 201 refers to the storage unit 109 and determines whether the own apparatus 201 is a master. When it is determined that the device 201 is the master (S601; YES), the process proceeds to S602. On the other hand, when it is determined that the own apparatus is a slave (S601; NO), the process proceeds to S606.

  In step S <b> 602, the communication control unit 102 of the own device 201 transmits the processing execution request message created by the control message creation unit (104) including information indicating the process instructed by the own device 201 to the partner device 203. .

  In S603, the application manager unit 108 of the own device 201 further notifies the application unit 107 of processing start, whereby the application unit 107 activates an application corresponding to the processing instructed by the own device 201, and Perform the process.

  In step S604, when the process ends, the application unit 107 notifies the application manager unit 108 of the end of the process. In step S <b> 605, the communication control unit 102 of the own device 201 transmits a disconnection request to the partner device 203. Thereafter, the single processing execution process is terminated.

  On the other hand, when it is determined that the own device is a slave (S601; NO), the processing after S606 is performed, which is basically the same as the operation of the slave in the multi-processing execution process. The difference from the operation of the slave in the multi-processing execution process is that no operation processing acquisition request message from the counterpart device 203 is received, and therefore the operation related to the execution processing acquisition response as in S515 of FIG. 5 is not necessary.

  In step S <b> 606, the communication control unit 102 of the own apparatus 201 determines whether a request message has been received from the partner apparatus 203. If it is determined that the request message has been received from the counterpart device 203 (S606; YES), the process proceeds to S514. On the other hand, if it is determined that a request message has not been received from the counterpart device 203 (S606; NO), the system waits until it is received.

  In step S607, the control message confirmation unit 105 of the own device 201 confirms the content of the request message. If the content of the request message is a processing execution request, the process proceeds to S608. If the content of the request message is a disconnection request, the single process execution process is terminated. In step S <b> 608, the application manager unit 108 of the own apparatus 201 notifies the application unit 107 of processing start. Then, the application unit 107 activates an application corresponding to the process indicated in the process execution request.

  In step S609, when the process ends, the application unit 107 notifies the application manager unit 108 of the end of the process. Thereafter, the process returns to S606. Further, the sequence of the single processing execution process will be described with reference to FIG.

  Here, as an example, the own device 201 is the master side, the counterpart device 203 is the slave side, and the processing instructed by the own device 201 is data PUSH from the own device 201 to the counterpart device 203.

  First, a processing execution request indicating processing instructed by the own device 201 is transmitted (F801), and a transmission / reception application is started to execute processing of data PUSH from the own device 201 to the partner device 203 in both devices. Then, the process is performed (F802). When the PUSH process instructed by the own apparatus 201 is completed, a PUSH completion notice is transmitted from the own apparatus 201 to the partner apparatus 203 (F803), and a disconnection request is transmitted (F804).

  As described above, according to the present embodiment, all the processes instructed by the user are realized with the minimum number of processing steps by determining the number of processes to be performed according to the presence or absence of a collision of connection requests. To do.

  In this embodiment, the timing for determining the number of processes to be performed based on the presence or absence of a connection request conflict is set before starting the multi-process execution process and the single-process execution process, but the determination is performed at other timings. May be. For example, when the connection process is completed (S301), the master immediately starts the single process execution process (S304). If there is a connection request collision after the single process execution process ends, the master continuously A method such as executing processing instructed by the slave is conceivable.

  Information indicating processing instructed by the user may be included in a message other than the control message defined in the present embodiment. For example, when using a message notifying a list of processes that can be performed, a method of including information indicating a process instructed by the user in the message is conceivable.

(Second Embodiment)
With reference to FIG. 9, an example of a functional block diagram of a communication device 901 according to the second embodiment having a proximity wireless communication (non-contact communication) function will be described. The communication device 901 includes a communication control unit 902, a connection request collision control unit 903, a control message creation unit 904, a control message confirmation unit 905, a user interface unit 906, an application unit 907, an application manager unit 908, A storage unit 909, a processing execution order determination unit 910, a multiple processing execution confirmation unit 911, and a timing unit 912 are provided.

  Hereinafter, only differences from the functional blocks of the first embodiment described with reference to FIG. 1 will be described. The multi-processing execution confirmation unit 911 confirms to the user using the user interface unit 906 that two processes are performed when performing the processing of both apparatuses. The time measuring unit 912 is used as a timer for measuring the duration of the link establishment state by the communication control unit 902. The system configuration in this embodiment is the same as that shown in FIG.

  The operation procedure in the present embodiment will be described with reference to the flowcharts of FIGS. 3, 4, 6, 10, and 11.

  Hereinafter, differences from the operation flowchart (FIGS. 3 to 7) of the first embodiment will be mainly described. As an initial state, the own device 201 and the partner device 203 are arranged at a sufficiently long distance where short-distance wireless communication by the close proximity wireless transfer interface 202 and the close proximity wireless transfer interface 204 is not possible, as shown in S301 of FIG. 3 and FIG. The connection process is started. In the state where instructions regarding processing such as transmission data selection and transmission instruction are performed by the operation of the user interface 106 in both apparatuses, the user has a distance between the own apparatus 201 and the partner apparatus 203 within a predetermined communication range. Move closer together.

  When the connection process is performed in S301 and it is determined that there is a connection request collision (S302; Yes), the multi-process execution process shown in S303 and FIG. 10 starts.

  The multi-process execution process according to this embodiment will be described with reference to the flowchart of FIG.

  In step S <b> 1001, the own apparatus 201 refers to the storage unit 109 and determines whether the own apparatus 201 is a master. When it is determined that the device 201 is the master (S1001; YES), the process proceeds to S1002. On the other hand, when it is determined that the own apparatus is a slave (S1001; NO), the process proceeds to S1015.

  Since each process of S1002 to S1005 is the same as each process of S502 to S505 described in the first embodiment, a description thereof will be omitted.

  In step S1006, the multi-process execution confirmation unit 911 of the own apparatus 201 confirms with the user whether or not a plurality of processes instructed by both apparatuses may be performed continuously. Details of this user confirmation processing will be described with reference to the flowchart of FIG.

  In step S <b> 1101, the multi-process execution confirmation unit 911 of the own apparatus 201 displays a display for confirming whether or not to perform multi-process on the user interface unit 906. In the present embodiment, as shown in FIG. 12, the contents and order of the processing to be performed are displayed, and the user selects “OK” or “Cancel”. This selection reception process may be received by a touch panel on the display screen. In addition, information regarding a transmission target file, time required for file transfer, and the like may be displayed.

  Next, in S1102, the time measuring unit 912 of the own apparatus 201 starts measuring the duration of the link establishment state.

  In step S <b> 1103, the multiple processing execution confirmation unit 911 of the own device 201 determines whether or not a predetermined time has elapsed since the start of time measurement.

  When it is determined that the predetermined time has elapsed (S1103; YES), the process proceeds to S1104. On the other hand, if it is determined that the predetermined time has not elapsed (S1103; NO), the process proceeds to S1105.

  In step S1104, the multi-process execution confirmation unit 911 of the own apparatus 201 stores information (“OK”) indicating that the multi-process execution is performed in the storage unit 909, and ends the user confirmation process. In step S <b> 1105, the communication control unit 902 of the own apparatus 201 determines whether the link with the partner apparatus 203 is disconnected. When it is determined that the link is disconnected (S1105; YES), the process proceeds to S1106. On the other hand, if it is determined that the link is not disconnected (S1105; NO), the process proceeds to S1107.

  In step S <b> 1106, the multiple processing execution confirmation unit 911 of the own apparatus 201 stores information (“Cancel”) indicating that the multiple processing execution is not performed in the storage unit 909, and ends the user confirmation processing. In step S <b> 1107, the multi-process execution confirmation unit 911 of the own apparatus 201 determines whether the user has selected “OK” or “Cancel” by operating the user interface unit 906.

  If the user selects “OK”, the process advances to step S1108. If the user selects “Cancel”, the process advances to step S1109. If the user has not made a selection, the process returns to S1103.

  In step S <b> 1108, the multi-process execution confirmation unit 911 of the own apparatus 201 stores information (“OK”) indicating that multi-process execution is performed in the storage unit 909, and ends the user confirmation process. In step S <b> 1109, the multi-process execution confirmation unit 911 of the own apparatus 201 stores information (“Cancel”) indicating that multi-process execution is not performed in the storage unit 909, and ends the user confirmation process.

  When the process of the flowchart of FIG. 11 ends, the process proceeds to S1007. In step S <b> 1007, the multiple processing execution confirmation unit 911 of the own apparatus 201 determines whether to perform the multiple processing with reference to the storage unit 909. If it is determined that multiple processing is to be performed (S1007; YES), the process proceeds to S1008. On the other hand, if it is determined not to perform multiple processing (S1007; NO), the process proceeds to S1014.

  Since the processes of S1008 to S1014 are the same as the processes of S506 to S512 described in the first embodiment, a description thereof will be omitted. On the other hand, when the own apparatus is a slave, the processes of S1015 to S1019 are performed. Since these processes are the same as the processes of S513 to S517 described in the first embodiment, description thereof is omitted.

  As described above, according to the present embodiment, when a data transmission operation is performed by a user in both apparatuses, even if a wireless link connection is completed and data transmission is possible, data transmission is immediately performed. Confirm with the user whether multiple processing can be performed continuously without starting.

(Other embodiments)
The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (9)

A communication device that establishes a wireless link with a counterpart device and communicates,
The occurrence of a request collision caused by the communication device transmitting a connection request for establishing a wireless link to the partner device and the partner device transmitting the connection request to the communication device. Detecting means for detecting when is established;
Determining means for determining a processing order of processing requested by the communication device and processing requested by the counterpart device based on information included in the connection request;
When the request collision is detected, communication means for performing processing by communicating with the counterpart device in the processing order determined by the determining means;
A communication apparatus comprising:   The communication means, when the request collision is not detected and the connection request is transmitted by the communication device, performs a process requested by the communication device by communicating with the counterpart device. The communication apparatus according to 1.   Acceptance of accepting an operation for selecting whether to execute the processing requested by the communication device and the processing requested by the counterpart device in the processing order determined by the determining means when the request collision is detected The communication apparatus according to claim 1, further comprising means. Further comprising time measuring means for measuring the duration of the establishment of the wireless link between the communication device and the counterpart device,
When the duration is longer than a predetermined time, the communication unit performs processing by communicating with the counterpart device in the processing order determined by the determination unit, the duration is shorter than the predetermined time, and the communication device 4. The communication according to claim 1, wherein, when the connection request is transmitted by the communication device, the communication unit communicates with the counterpart device to perform processing requested by the communication device. 5. apparatus. The connection request includes device identification information of the communication device or the counterpart device,
The determining means sets each of the communication device or the counterpart device as a master or a slave based on the device identification information, and is a master device among a process requested by the communication device and a process requested by the counterpart device. The communication apparatus according to any one of claims 1 to 4, wherein the processing order is determined so that the processing requested by the device is executed first. The connection request includes operation information indicating whether or not an operation is performed by an operator when performing the processing requested by the communication device or the processing requested by the counterpart device,
Based on the operation information, the determination means sets a processing order so that a process in which an operation by the operator is not performed is performed first among a process requested by the communication apparatus and a process requested by the counterpart apparatus. The communication device according to claim 1, wherein the communication device is determined. The connection request includes size information indicating a data size to be transmitted for the processing when the processing requested by the communication device or the processing requested by the counterpart device is performed,
5. The communication according to claim 1, wherein the determination unit determines a processing order based on the size information so that the processing with the smaller data size is performed first. 6. apparatus. A method for controlling a communication device that establishes a wireless link with a counterpart device and communicates with the counterpart device,
A wireless link is established when a request collision occurs when the communication device transmits a connection request for establishing the wireless link to the partner device and the partner device transmits the connection request to the communication device. A detection step to detect when,
A determination step of determining a processing order of processing requested by the communication device and processing requested by the counterpart device based on information included in the connection request;
When the request collision is detected, a communication step for performing processing by communicating with the counterpart device in the processing order determined in the determination step;
A method for controlling a communication apparatus, comprising:   The program for making a computer perform each process of the control method of the communication apparatus of Claim 8.