JP5124375B2 - Information processing device - Google Patents

Information processing device Download PDF

Info

Publication number
JP5124375B2
JP5124375B2 JP2008187812A JP2008187812A JP5124375B2 JP 5124375 B2 JP5124375 B2 JP 5124375B2 JP 2008187812 A JP2008187812 A JP 2008187812A JP 2008187812 A JP2008187812 A JP 2008187812A JP 5124375 B2 JP5124375 B2 JP 5124375B2
Authority
JP
Japan
Prior art keywords
data
application
queue
transmission
information processing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2008187812A
Other languages
Japanese (ja)
Other versions
JP2010026815A (en
Inventor
俊晃 上向
剣明 呉
和幸 江口
Original Assignee
Kddi株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kddi株式会社 filed Critical Kddi株式会社
Priority to JP2008187812A priority Critical patent/JP5124375B2/en
Publication of JP2010026815A publication Critical patent/JP2010026815A/en
Application granted granted Critical
Publication of JP5124375B2 publication Critical patent/JP5124375B2/en
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Description

  The present invention relates to an information processing apparatus applied to a distributed equipment mutual control system having a communication function and configured by a plurality of information processing apparatuses that mutually transmit and receive signals.

  In recent years, mobile phones have advanced functions, large capacities, and high speeds. As a result, in addition to basic applications such as e-mail and schedule books, it has become common to install sophisticated applications such as viewing web pages for PCs and viewing terrestrial digital (terrestrial digital broadcast) images. It is coming. In addition to the socket communication function used for browsing the web and sending / receiving e-mail, the mobile phone communication function is also equipped with an infrared communication function, a Bluetooth (registered trademark) communication function, and a Felica (registered trademark) communication function. It has become to.

  This enables two-way data communication and users by configuring a local network and communicating with other terminals close to the mobile phone, such as a mobile phone and a PC, a mobile phone and a mobile phone, or a mobile phone and a dedicated small device. Interaction is possible.

  In particular, as a typical system in which a mobile phone and a PC are linked, there is a system that displays a liquid crystal screen display content of the PC on the screen of the mobile phone. The most famous system is VNC (Virtual Networking Computing). In this system, the screen of a server-side terminal is imaged and the image data is transferred to a client-side terminal. As a result, the user can access the PC from a remote location using a mobile phone, start an application that runs on the PC, check the display screen on the screen of the mobile phone, or use the numeric keypad on the mobile phone. The text data input in the above manner can be input into a text box of an application operating on the PC. For example, Patent Document 1 (Japanese Patent Laid-Open No. 2007-251630) or Patent Document 2 (Japanese Patent Laid-Open No. 2001-103568) discloses a technique for operating a PC from a remote location.

There is also a system for controlling the functions of a mobile phone. For example, in the technique disclosed in Patent Document 3 (Japanese Patent Laid-Open No. 2000-041012), a control signal is transmitted from a remote PC to a mobile phone, thereby invalidating key operations of the mobile phone or supplying power. Can be stopped. Furthermore, in the system disclosed in Patent Document 4 (Special Table 2007-522546), a function is shared between two wireless portable terminals (for example, a cellular phone and a PDA), and user interaction from both is enabled. In this system, in a state where two terminals are connected by wireless communication means such as Bluetooth (registered trademark), a phone call of a mobile phone is made by inputting on the touch panel of the PDA, or a picture in the PDA is displayed. The mobile phone can be browsed by operating the scroll wheel of the mobile phone on the color display of the mobile phone, and the image in the mobile phone can be edited on the PDA.
JP 2007-251630 A JP 2001-103568 A JP 2000-0110102 A Special table 2007-522546 gazette

  However, the systems described in Patent Document 1 and Patent Document 2 remotely access a PC from a mobile phone, image the content displayed on the liquid crystal screen of the PC, transfer the image data to the mobile phone, and display it. However, there is only one-way control from the mobile phone to the PC. Further, the system described in Patent Document 3 is not only for controlling the function of the mobile phone by transmitting a control signal from the PC to the mobile phone, but for controlling the mobile phone unilaterally from the PC side. Only it is. Patent Document 4 describes a system that shares the display content, function, and user interface of one of two portable terminals with the other. However, Patent Document 4 describes only a system configuration and a sequence chart in which two devices are close to each other, and when the screen sharing function is started, the function and operation of one device can be operated from the other device. It is not done and lacks concreteness. Although the concept of enhancing the functions of only one device by effectively utilizing the functions of the two devices is described, the detailed algorithm on each device is unknown when using each function. is there.

  In the above-described conventional technology, there is only one application that can be used simultaneously between the mobile phone and the PC. This is considered to be because it is assumed that only one application can be activated according to the specifications of the mobile phone. However, in the future, it is expected that a plurality of applications can be simultaneously activated on the mobile phone. When a plurality of applications are activated and data is transmitted / received between a PC and a mobile phone by a plurality of applications, it is expected that data transmission of one application is delayed due to the influence of other applications and usability is lowered.

  The present invention has been made in view of such circumstances, and even in a plurality of terminal devices, for example, a mobile phone and a PC, even when a plurality of applications are operated simultaneously, data communication can be performed efficiently. An object is to provide an information processing apparatus.

  (1) In order to achieve the above object, the present invention takes the following measures. That is, the information processing apparatus of the present invention is an information processing apparatus that is applied to a communication system in which a plurality of information processing apparatuses having a communication function mutually transmit and receive signals, and corresponds to a predetermined priority. A plurality of transmission side queues provided, and a transmission side queue insertion for selecting a queue corresponding to the priority and storing data to be transmitted to the selected queue when transmitting data to another information processing apparatus And a transmission side queue reading unit that sequentially reads data from the queue with a high priority.

  As described above, when data is transmitted to another information processing apparatus, the queue corresponding to the priority is selected, the data to be transmitted is stored in the selected queue, and the data is sequentially read from the queue with the higher priority. Therefore, it becomes possible to efficiently process transmission data according to a predetermined priority. In particular, when a plurality of applications are operated in parallel when only one transmission path can be established with another information processing apparatus, data of the plurality of applications can be transmitted and received by generating one data stream. It becomes possible.

  (2) The information processing apparatus of the present invention is an information processing apparatus applied to a communication system in which a plurality of information processing apparatuses having a communication function mutually transmit and receive signals, and has a predetermined priority. When receiving data from a plurality of corresponding receiving side queues and other information processing devices, a queue corresponding to the priority is selected based on the received data, and the reception is performed in the selected queue. A receiving-side queue insertion unit that stores the received data, and a receiving-side queue reading unit that sequentially reads data from the queue with the highest priority.

  In this way, when data is received from another information processing apparatus, a queue corresponding to the priority is selected based on the received data, the received data is stored in the selected queue, and a queue with high priority is selected. Since the data is sequentially read from the received data, it is possible to efficiently process the received data according to a predetermined priority. In particular, when a plurality of applications are operated in parallel when only one transmission path can be established with another information processing apparatus, data of the plurality of applications can be transmitted and received by generating one data stream. It becomes possible.

  (3) Further, the information processing apparatus of the present invention includes at least one self-application that is executed on an operating system, and the self-application transmits a queue type when transmitting data to another information processing apparatus. Also, information indicating whether or not ACK (Acknowledgement) is necessary is added.

  In this way, when transmitting data to other information processing apparatuses, information indicating the queue type and the necessity of ACK is added, so the priority is specified at the time of data transmission, and the necessity of ACK is determined. It can be specified.

  (4) In the information processing apparatus of the present invention, the transmission side queue insertion unit selects a queue corresponding to the queue type added to the data received from the self application, and transmits data to be transmitted to the selected queue. It is characterized by storing.

  In this way, since the queue corresponding to the queue type added to the data received from the self application is selected and the data to be transmitted is stored in the selected queue, the priority can be specified by the queue type.

  (5) Further, the information processing apparatus of the present invention acquires information indicating functions of the self-application and another application executed by the other information processing apparatus, and there is no function to be executed in the self-application. When there is a function to be executed in the other application, a control unit that outputs a signal to execute the other application to the other information processing apparatus, and an execution result of the self application A display unit that displays or displays an execution result of the other application input from the other information processing apparatus.

  As described above, when there is no function to be executed in the self application and there is a function to be executed in another application, a signal to execute the other application is output to the other information processing apparatus. Therefore, it is possible to use functions of other information processing apparatuses. Further, since the execution result of the self application is displayed or the execution result of another application input from another information processing apparatus is displayed, the user operates only this information processing apparatus, and this information processing apparatus or other It is possible to confirm the operation status of the information processing apparatus. As a result, the user can freely select an information processing apparatus to be used according to the TPO.

  (6) Moreover, in the information processing apparatus of the present invention, the control unit executes the self application when there is a function to be executed in the self application and a function to be executed in the other application. Or a signal indicating that the other application is executed is output to the other information processing apparatus.

  As described above, when a function to be executed exists in the self application and a function to be executed also exists in another application, the self application is executed or another application is made to another information processing apparatus. Is output, a single task can be processed using two information processing apparatuses. Thereby, the user can freely select an information processing apparatus to be used according to the TPO.

  According to the present invention, when transmitting data to another information processing apparatus, the queue corresponding to the priority is selected, the data to be transmitted is stored in the selected queue, and the data is sequentially transmitted from the queue with the highest priority. Therefore, transmission data can be processed efficiently according to a predetermined priority. In particular, when a plurality of applications are operated in parallel when only one transmission path can be established with another information processing apparatus, data of the plurality of applications can be transmitted and received by generating one data stream. It becomes possible.

(First embodiment)
Next, embodiments according to the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating a concept of a distributed device mutual control system according to the present embodiment. As shown in FIG. 1, in the distributed device mutual control system of the present embodiment, a mobile phone (MT) 10 and a PC 20 are connected by short-range wireless communication such as Bluetooth (registered trademark). Software is executed on each of the MT 10 and the PC 20. The operation performed on the MT 10 is processed by the software on the MT 10 and / or the software on the PC 20, and the processing result is reflected in the software on the MT 10 and / or the software on the PC 20.

  Similarly, the operation performed on the PC 20 is processed by the software on the PC 20 and / or the software on the MT 10 being processed, and the processing result is reflected in the software on the PC 20 and / or the software on the MT 10. At this time, the screen update of the MT 10 and / or the PC 20 may or may not be accompanied. The MT 10 and the PC 20 have a platform for operating various applications.

  Here, in the present embodiment, description will be made using the mobile phone (MT) 10 and the PC 20 as the two devices, but other devices may be used. For example, home appliances or in-vehicle terminals may be used. In addition, although a short-range wireless communication unit such as Bluetooth (registered trademark) will be described as a communication unit for two devices to cooperate with each other, other communication units may be used. For example, a USB compatible wired communication unit may be used.

  FIG. 2 is a block diagram showing a schematic configuration of the distributed device mutual control system according to the present embodiment. The input unit 11 of the MT 10 has a numeric keypad, and a user can input a signal by operating the numeric keypad. On the other hand, the input unit 21 of the PC 20 has input devices such as a touch panel, a keyboard, and a mouse, and a user can input signals by operating these devices. Operation information input by the user through the input unit 11 or 21 is transferred to the management unit 13 or 23. The output unit 12 of the MT 10 and the output unit 22 of the PC 20 have a liquid crystal screen and display information on the screen. When the screen display contents of the application are changed in the management units 13 and 23 and the application units 15 and 25, the rendering processing result is received and output as an image.

  The management unit 13 of the MT 10 and the management unit 23 of the PC 20 perform overall management of applications operating on the system. The operation information input by the user through the input unit 11 or 21 is transferred to the corresponding application unit 15 or 25. When the rendering content is changed in the application unit 15 or 25, the rendering processing result is transferred to the output unit 12 or 22. In addition, when receiving “in-app data” as transfer data from the application unit 15 or 25 to the opposite application unit 15 or 25, the management unit 13 or 23 transfers the data to the communication unit 14 or 24.

  The communication unit 14 of the MT 10 or the communication unit 24 of the PC 20 transmits the “in-app data” received from the management unit 13 or 23 to the counterpart terminal. In this embodiment, a device using a short-range wireless communication device such as Bluetooth (registered trademark) is shown, and a connection of Bluetooth (registered trademark) is established, and data transmission between two terminals is possible. Assuming that. When “in-app data” is received from the opposite communication unit, it is transferred to the management unit 13 or 23.

  The application unit 15 of the MT 10 or the application unit 25 of the PC 20 is an arbitrary application that operates on this system. In this system, one or more applications may be operating. In the internet communication unit 16 of the MT 10, the application unit 15 downloads data or uploads data in cooperation with the server.

  FIG. 3 is a block diagram illustrating a schematic configuration of the management unit 13 or 23. The management units 13 and 23 include a communication management unit 30, an application management unit 310, and a main management unit 320. The communication management unit 30 includes a transmission data control unit 30a, a reception data control unit 30b, and a communication cooperation unit 30c. The application management unit 310 includes an application management table 310a. The main management unit 320 manages the entire management units 13 and 23.

  The application cooperation unit 310b serves as an interface for cooperation with the upper application units 15 and 25. Data is transferred from the application units 15 and 25 to the application management unit 310 or from the application management unit 310 to the application units 15 and 25. The application management unit 310 notifies the transmission data control unit 30a to transfer the in-app data requested to be transferred from the application units 15 and 25 to the counterpart terminal while referring to the application management table 310a. In addition, the in-app data requested to be transferred from the reception data control unit 30b is notified to the application cooperation unit 310b to transfer the data to the application units 15 and 25.

  The communication cooperation unit 30c controls data transmission / reception with the counterpart terminal in cooperation with the communication units 14 and 24. The transmission data control unit 30a transfers the transmission data to the communication cooperation unit 30c while controlling the transmission of the in-app data requested to be transferred from the application management unit 310. In transmission control, as will be described later, two types of transmission queues are used. The reception data control unit 30b transfers the transmission data to the application management unit 310 while performing reception control on the in-app data requested to be transferred from the communication cooperation unit 30c.

  FIG. 4 is a diagram showing a configuration example of the application management table when registered in the application management table 310a shown in FIG. The application management table shown in FIG. 4 includes an application identifier, an application name, an MT application identifier, an MT itself identifier in which an application in the MT 10 operates, a PC application identifier, and an identifier of the PC itself in which the PC 20 application operates. Is done. Thereby, a plurality of applications that operate on the management units 13 and 23 can be operated. In addition, the management units 13 and 23 can grasp which application received the data and which application the data should be transmitted to.

  An arbitrary application operating on the system is downloaded from the web server using the cellular phone communication network from the Internet communication unit 16. The application to be downloaded is for both MT10 and PC20, and the downloaded application for MT10 is registered on the management unit 13 on MT10. On the other hand, the PC 20 application is registered on the management unit 23 on the PC 20 via the communication units 14 and 24.

  In addition, the PC 20 does not download via the mobile phone communication network, but copies data by connecting an external device such as a USB memory, or downloads it from a server using WiFi (registered trademark) or the like. Also good. When registering application information, both management units 13 and 23 register the managed application in the “application management table” together with the identification information of the application that is the communication partner of the registered application. Thereby, the management units 13 and 23 of the other party can grasp which application the data has arrived from and which application the data should be delivered to. In addition, since only one Bluetooth (registered trademark) transmission path built in the mobile phone can be established, it is necessary to transmit data of a plurality of applications when operating a plurality of applications in parallel. At this time, by embedding information of the transmission source and transmission destination in the Bluetooth (registered trademark) transmission data generated by both management units, one data stream is generated and a plurality of applications can be simultaneously started. .

  Next, in the transmission of in-app data from the application unit 15 or 25 (source application unit) to the opposite application unit 15 or 25 (destination application unit), data processing in each module in the management units 13 and 23 A method will be described. FIG. 5 shows data (“first transmission data”) that the transmission source application unit notifies the management unit (application cooperation unit) when the transmission source application unit requests transmission of in-app data to the transmission destination application unit. It is a figure which shows a structure.

  The “first transmission data” includes a transmission source application identifier, a transmission destination application identifier, a data size of in-app data to be transmitted, a start address on the memory of in-app data, a transmission queue identifier to be described later, and a transmission completion notification Consists of information. Here, the transmission source application identifier and the transmission destination application identifier are the same as the information described in the application management table 310a.

  The transmission completion notification information is information for the application cooperation unit 310b to notify the application units 15 and 25 when the application units 15 and 25 have completed transmission of in-app data to the opposite terminal. If there is “null” in the transmission completion notification information, the transmission completion notification may not be returned to the application units 15 and 25. In other words, depending on the function of the application, when the data transmission is completed, the confirmation message may or may not be necessary. For this reason, it is possible to specify that a confirmation message is not required by specifying “null”. Thereby, one-way data transfer like UDP (User Datagram Protocol) can be performed. This is effective when transmitting in-app data (for example, sensor data within 100 ms) with a small sampling period.

  The application cooperation unit 310b sequentially transfers the “first transmission data” notified from the application units 15 and 25 to the application management unit 310. Based on the “first transmission data” and the “application management table 310a”, the application management unit 310 converts the data to the “second transmission data” to be transferred to the transmission data control unit 30a.

  FIG. 6 is a diagram illustrating a configuration of “second transmission data” that the application management unit notifies the transmission data control unit. In “second transmission data”, “transmission source terminal identifier” and “transmission destination terminal identifier” are added to “first transmission data”. The transmission data control unit 30a inserts “second transmission data” into a transmission queue described later. Also, the transmission data control unit 30a reads the data to be transmitted from the transmission queue, converts it into a “communication data packet”, and transfers it to the communication cooperation unit 30c. There are two types of transmission queues. A method for reading data from both queues will be described later.

  FIG. 7 is a diagram illustrating a configuration of a “communication data packet” notified to the communication cooperation unit. In the “communication data packet”, a “packet identifier” is added to “second transmission data” instead of “transmission completion notification information”. The communication cooperation unit 30 c sequentially transfers the “communication data packet” to the communication units 14 and 24. As a result, the communication units 14 and 24 transmit the communication data packet to the connected destination terminal using a communication module such as Bluetooth (registered trademark). On the other hand, the destination terminal that has received the communication data packet transfers the data body to the corresponding application units 15 and 25 by processing in the reverse direction.

  FIG. 8 is a diagram illustrating a schematic configuration of the transmission data control unit. In this system, only one Bluetooth (registered trademark) transmission line with a built-in mobile phone can be established. Therefore, even if a plurality of applications are operating, it is necessary to generate only one data stream. A plurality of applications also have various features, and there are various operation modes depending on the applications. That is, there is a case where data having a somewhat large data size, such as image data, is transmitted to the partner terminal, or that having a minute data size, such as sensor detection data when characters are input, is transmitted to the partner terminal. For example, when character input is performed while image data is being transmitted, depending on the configuration of the data stream, if image data transmission is not completed, character input data will not be transmitted, and character input response will be delayed. there's a possibility that.

  Therefore, in this embodiment, the transmission data control unit is configured with two queues in order to increase the efficiency of data transmission. One is the “high-speed queue 81a” and the other is the “low-speed queue 81b”. The queue insertion unit 82 controls data insertion processing for both queues 81a and 81b, and the queue reading unit 83 controls data reading processing from both queues 81a and 81b.

  The low-speed queue 81b is used for data transmission after confirming data transmission / reception before both data transmission / reception. On the other hand, the high-speed queue 81a does not perform confirmation before data transmission / reception unlike the low-speed queue 81b, and is used for unilateral data transmission. Referring to the designation information from the application units 15 and 25 that transmit “in-app data”, the queue insertion unit 82 determines which queue 81a and 81b the received data is to be inserted into, and which queue Accumulate in 81a or 81b.

  FIG. 9 is a flowchart showing the operation of the queue insertion unit 82. The queue insertion unit 82 first determines whether or not the process is complete (step S90), and terminates if the process is complete. On the other hand, if the process is not completed in step S90, it is determined whether there is a data insertion request (step S91). If there is no data insertion request, the process proceeds to step S90. If there is a data insertion request, it is determined whether there is an insertion request to the high-speed queue (step S92). If there is a request for insertion into the high-speed queue, it is determined whether or not insertion into the high-speed queue is possible (step S93). If insertion into the high-speed queue is possible, data is inserted into the high-speed queue. (Step S94), the process proceeds to Step S90.

  On the other hand, if the insertion into the high-speed queue is not possible in step S93, an error response is made (step S95), and the process proceeds to step S90. In step S92, if there is no request for insertion into the high speed queue, it is determined whether there is a request for insertion into the low speed queue (step S96). If there is a request for insertion into the low-speed queue, it is determined whether or not insertion into the low-speed queue is possible (step S97). If insertion into the low-speed queue is possible, data is inserted into the low-speed queue. (Step S98), the process proceeds to Step S90.

  If there is no request for insertion into the low speed queue in step S96, and if insertion into the low speed queue is not possible in step S97, an error response is made (step S99), and the process proceeds to step S90.

  FIG. 10 is a flowchart showing the operation of the queue reading unit 83. The queue reading unit 83 reads data stored in each queue asynchronously with queue insertion. As shown in FIG. 10, the queue reading unit 83 determines whether or not the process is finished (step S100), and ends when the process is finished. On the other hand, if the processing is not completed in step S100, it is determined whether there is data in the high speed queue (step S101). If there is data in the high speed queue, data is read from the high speed queue. (Step S102). On the other hand, if there is no data in the high speed queue in step S101, it is determined whether there is data in the low speed queue (step S103). If there is no data in the low speed queue, the process proceeds to step S100. If there is data in the low speed queue, data is read from the low speed queue (step S104). And the data read in step S102 or step S104 are transferred to the communication cooperation part 30c (step S105), and it changes to step S100.

  In this embodiment, the configuration is such that the type of queue to be inserted is specified in the data packet, but the configuration is such that priority is given to the transmission data depending on the characteristics of the transmission data or the intention of the application developer. It may be. The priority is based on the data size of the transfer data, the priority of the application, the data type, and the like.

  Further, between the communication unit 14 of the MT 10 and the communication unit 24 of the PC 20, data is transferred from one to the other using near field communication such as Bluetooth (registered trademark). The data transfer control at this time follows a standard such as a conventional Bluetooth (registered trademark) SPP (System Platform Processor).

  Next, processing of the received queue will be described. The communication units 14 and 24 convert the “communication data packet” received from the opposite terminal into the following “first received data”. FIG. 11 is a diagram illustrating a configuration of “first received data”. As shown in FIG. 11, the first reception data has the same configuration as the communication data packet shown in FIG. The communication cooperation unit 30c transfers the first reception data to the reception data control unit 30b.

  FIG. 12 is a diagram illustrating a schematic configuration of the reception data control unit 30b. The reception data control unit 30b includes a high speed queue 120a and a low speed queue 120b. The high-speed queue 120a performs data transfer unilaterally without performing confirmation before data transmission / reception. The low-speed queue 120b is a person for confirming data transmission / reception before both data transmission / reception. The queue insertion unit 122 determines which queue 120a, 120b the “first received data” is to be inserted into, and stores it in any queue.

  FIG. 13 is a flowchart showing the operation of the queue insertion unit 122. The queue insertion unit 122 first determines whether or not the process has ended (step S130), and ends when the process ends. On the other hand, if the process is not completed in step S130, it is determined whether there is a data insertion request (step S131). If there is no data insertion request, the process proceeds to step S130. If there is a data insertion request, it is determined whether there is a high-speed queue insertion request (step S132). If there is a request to insert a high-speed queue, it is determined whether data can be inserted into the high-speed queue (step S133). If data can be inserted into the high-speed queue, data is inserted into the high-speed queue (step S134), and the process proceeds to step S130.

  On the other hand, if data cannot be inserted into the high-speed queue at step S133, an error response is made (step S135), and the process proceeds to step S130. If there is no data insertion request to the high speed queue in step S132, it is determined whether there is a data insertion request to the low speed queue (step S136). If there is a request to insert data into the low speed queue, it is determined whether data can be inserted into the low speed queue (step S137). If data can be inserted into the low speed queue, the data is inserted into the low speed queue (step S138), and the process proceeds to step S130.

  On the other hand, if there is no request to insert data into the low speed queue in step S136, or if data cannot be inserted into the low speed queue in step S137, an error response is made (step S139), and the process proceeds to step S130. .

  On the other hand, the queue reading unit 121 reads data stored in each queue asynchronously with queue insertion. FIG. 14 is a flowchart showing the operation of the queue reading unit 121. As illustrated in FIG. 14, the queue reading unit 121 determines whether or not the process has ended (step S140), and ends when the process has ended. On the other hand, if the processing is not completed in step S140, it is determined whether or not there is data in the high-speed queue (step S141). If there is data in the high-speed queue, data is read from the high-speed queue. (Step S142). On the other hand, if there is no data in the high speed queue in step S141, it is determined whether there is data in the low speed queue (step S143). If there is no data in the low speed queue, the process proceeds to step S140. If there is data in the low speed queue, data is read from the low speed queue (step S144). Then, the data read in step S142 or step S144 is transferred to the application management unit 310 (step S145), and the process proceeds to step S140.

  Based on the “first received data” and the “application management table” transferred from the received data control unit 30b, the application management unit 310 converts the data to the “second received data” to be transferred to the application cooperation unit 310b. FIG. 15 is a diagram illustrating a configuration of “second received data” that the application management unit 310 transfers to the application cooperation unit 310b. As shown in FIG. 15, the second reception data has the same configuration as the second transmission data shown in FIG. 6. The application cooperation unit 310b sequentially transfers the “second received data” to the application units 15 and 25.

  Next, transmission data generated in the transmission source application unit 15 or 25 is transmitted to the transmission destination application unit 15 or 25 via the transmission source management unit 13 or 23 and the transmission destination management unit 13 or 23. The operation will be described for each data type. FIG. 16 is a flowchart showing an operation in the case where transmission is performed by returning an ACK using a high-speed queue. Here, it is assumed that the transmission source is MT10 and the transmission destination is PC20.

  First, the transmission source application unit 15 in the transmission source MT10 makes a transmission request to the transmission source management unit 13 (step S160). The transmission source management unit 13 determines whether transmission is possible (step S161), and transmits the determination result to the transmission source application unit 15 (step S162). The transmission source application unit 15 receives the determination result from the transmission source management unit 13 (step S163). Next, when transmission is possible in step S161, the transmission source management unit 13 transmits data to the transmission destination management unit 23 (step S164). When receiving the data from the transmission source management unit 13 (step S165), the transmission destination management unit 23 transmits a reception notification to the transmission destination application unit 25 (step S166). The transmission destination application unit 25 receives a reception notification from the transmission destination management unit 23 (step S167) and receives data (step S168).

  On the other hand, the transmission source management unit 23 notifies the transmission source management unit 13 that the data reception has been successful in step S165 (step S169). Upon receiving the reception completion notification from the transmission source management unit 23, the transmission source management unit 13 transmits it to the transmission source application unit 15 (step S170), and the transmission source application unit 15 receives the reception completion notification (step S170). S171).

  FIG. 17 is a flowchart showing an operation in the case where the ACK is not returned using the high-speed queue. Here, it is assumed that the transmission source is MT10 and the transmission destination is PC20. First, the transmission source application unit 15 in the transmission source MT10 makes a transmission request to the transmission source management unit 13 (step S172). The transmission source management unit 13 determines whether transmission is possible (step S173), and transmits the determination result to the transmission source application unit 15 (step S174). The transmission source application unit 15 receives the determination result from the transmission source management unit 13 (step S175). Next, when transmission is possible in step S173, the transmission source management unit 13 transmits data to the transmission destination management unit 23 (step S176). When receiving the data from the transmission source management unit 13 (step S177), the transmission destination management unit 23 transmits a reception notification to the transmission destination application unit 25 (step S178). The transmission destination application unit 25 receives a reception notification from the transmission destination management unit 23 (step S179) and receives data (step S180).

  FIG. 18 is a flowchart showing an operation in the case where transmission is performed by returning an ACK using a low-speed queue. Here, it is assumed that the transmission source is MT10 and the transmission destination is PC20.

  First, the transmission source application unit 15 in the transmission source MT10 makes a transmission request to the transmission source management unit 13 (step S181). The transmission source management unit 13 determines whether transmission is possible (step S182), and transmits the determination result to the transmission source application unit 15 (step S183). The transmission source application unit 15 receives the determination result from the transmission source management unit 13 (step S184). Next, when transmission is possible in step S182, the transmission source management unit 13 sends a transmission request notification to the transmission destination management unit 23 (step S185). When receiving the transmission request notification from the transmission source management unit 13, the transmission destination management unit 23 transmits a transmission request notification to the transmission destination application unit 25 (step S186). The transmission destination application unit 25 receives the transmission request notification from the transmission destination management unit 23 (step S187) and returns a transmission request response (step S188).

  Upon receiving the transmission request response from the transmission destination application unit 25, the transmission destination management unit 23 transmits it to the transmission source management unit 13 (step S189). When receiving a transmission request response from the transmission destination management unit 23 (step S190), the transmission source management unit 13 transmits data to the transmission destination management unit 23 (step S191). When receiving data from the transmission source management unit 13 (step S192), the transmission destination management unit 23 transmits a data reception notification to the transmission destination application unit 25 (step S193). The transmission destination application unit 25 receives a reception notification from the transmission destination management unit 23 (step S194), and receives data (step S195).

  In addition, when receiving data in step S192, the transmission destination management unit 23 transmits a reception completion notification to the transmission source management unit 13 (step S196). When receiving the reception completion notification from the transmission destination management unit 23, the transmission source management unit 13 transmits the reception completion notification to the transmission source application unit 15 (step S197). The transmission source application unit 15 receives a reception completion notification from the transmission source management unit 13 (step S198).

  FIG. 19 is a flowchart showing an operation in the case where transmission is performed by not using the low-speed queue and returning ACK. Here, it is assumed that the transmission source is MT10 and the transmission destination is PC20.

  First, the transmission source application unit 15 in the transmission source MT10 makes a transmission request to the transmission source management unit 13 (step S199). The transmission source management unit 13 determines whether transmission is possible (step S200), and transmits the determination result to the transmission source application unit 15 (step S201). The transmission source application unit 15 receives the determination result from the transmission source management unit 13 (step S202). Next, when transmission is possible in step S200, the transmission source management unit 13 sends a transmission request notification to the transmission destination management unit 23 (step S203). Upon receiving the transmission request notification from the transmission source management unit 13, the transmission destination management unit 23 transmits a transmission request notification to the transmission destination application unit 25 (step S204). The transmission destination application unit 25 receives the transmission request notification from the transmission destination management unit 23 (step S205) and returns a transmission request response (step S206).

  Upon receiving the transmission request response from the transmission destination application unit 25, the transmission destination management unit 23 transmits it to the transmission source management unit 13 (step S207). When receiving the transmission request response from the transmission destination management unit 23 (step S208), the transmission source management unit 13 transmits data to the transmission destination management unit 23 (step S209). When receiving the data from the transmission source management unit 13 (step S210), the transmission destination management unit 23 transmits a data reception notification to the transmission destination application unit 25 (step S211). The transmission destination application unit 25 receives a reception notification from the transmission destination management unit 23 (step S212), and receives data (step S213).

(Second Embodiment)
The distributed device mutual control system according to the second embodiment does not have a function to be executed in its own application, and has other information when there is a function to be executed in another application included in another information processing apparatus. A signal to execute another application is output to the processing device. Then, the execution result of the self application is displayed, or the execution result of another application input from another information processing apparatus is displayed.

  FIG. 20 is a block diagram illustrating a schematic configuration of the management unit 13 or 23 according to the second embodiment. The configuration of a part of the management unit 13 or 23 according to the first embodiment is different. For this reason, the same number shall be attached | subjected to a common structure. The management units 13 and 23 according to the second embodiment include a communication management unit 30 and an application control unit 31. The communication management unit 30 includes a transmission data control unit 30a, a reception data control unit 30b, and a communication cooperation unit 30c. The application control unit 31 includes an application control library unit 31a and an application cooperation unit 31b.

  The application cooperation unit 31b serves as an interface for cooperation with the upper application units 15 and 25. Data transfer from the application units 15 and 25 to the application control unit 31 or from the application control unit 31 to the application units 15 and 25 is performed. The application control unit 31 refers to the application information 32 and the function information 33, and notifies the transmission data control unit 30a to transfer the in-app data requested by the application units 15 and 25 to the partner terminal. In addition, the application cooperation unit 31b is notified to transfer data to the application units 15 and 25 regarding the in-app data requested to be transferred from the reception data control unit 30b.

  The communication cooperation unit 30c controls data transmission / reception with the counterpart terminal in cooperation with the communication units 14 and 24. The transmission data control unit 30a adopts the same configuration as that of the first embodiment shown in FIG. 8 and performs the same function. Then, the transmission data is transferred to the communication cooperation unit 30c while the transmission control is performed with respect to the in-app data requested by the application control unit 31. The reception data control unit 30b has the same configuration as that of the first embodiment shown in FIG. 12 and performs the same function. Then, transmission data is transferred to the application control unit 31 while receiving control is performed on the in-app data for which there is a transfer request from the communication cooperation unit 30c.

  The application control library unit 31a is a function group necessary for an application registered in the upper application units 15 and 25 to operate in cooperation with other applications on the system. It has a wireless communication connection function between terminals, a data transmission / reception function via a communication link unit, a file operation function using a data folder common to two terminals, a drawing function on a liquid crystal screen, and the like. In addition, the function information includes information related to the functions of each terminal. When an application operates, this information is used to determine whether to use the function on the own terminal or the function on the opposite terminal. decide.

  FIG. 21 is a diagram showing a configuration example of an application information table when registered in the application information 32 shown in FIG. An arbitrary application operating on the system is downloaded from the web server using the cellular phone communication network from the Internet communication unit 16. The application to be downloaded is for both MT10 and PC20, and the downloaded application for MT10 is registered on the management unit 13 on MT10. On the other hand, the PC 20 application is registered on the management unit 23 on the PC 20 via the communication units 14 and 24.

  The PC 20 may copy data by connecting an external device such as a USB memory without downloading via the mobile phone communication network, or may download from a server using WiFi or the like. When registering application information, both management units 13 and 23 register the managed application in the “application information table” together with the identification information of the application that is the communication partner of the registered application.

  The application information table shown in FIG. 21 is composed of an application identifier, an application name, an MT application identifier, an MT10 itself identifier on which an application in MT10 operates, a PC20 application identifier, and an identifier of PC20 itself on which the PC20 application operates. Is done. Thereby, a plurality of applications that operate on the management units 13 and 23 can be operated. In addition, the management units 13 and 23 can grasp which application received the data and which application the data should be transmitted to.

  FIG. 22 is a diagram showing a configuration example of a function information table registered in the function information 33 shown in FIG. In this function information table, the functions possessed by the MT 10 and the PC 20 necessary for operating any application operating on the system are managed. As shown in FIG. 22, the function information table includes a function identifier, a function name, a device necessary for using the function, an input data format required when using the function, an output data format after using the function, and restrictions on using the function (rules). ). Thereby, the function information which both terminals have can be referred. The application control library 31a and the application control unit 31 use this information to determine whether there is a function for a normal operation of an application that operates at a higher level.

  Next, the application control library 31a shown in FIG. 20 will be described. This system assumes the following application control libraries.

(1) Wireless communication connection function The wireless communication connection function establishes a connection using a short-range wireless communication device and establishes a data transmission / reception path in order to transmit and receive data between applications running on both terminals.

(2) Data transmission / reception function The data transmission / reception function transmits and receives data between applications running on both terminals.

(3) File operation function The file operation function includes a data folder and a data file accessible from both applications, and performs file operations such as editing on the data file.

(4) Drawing Function The drawing function performs not only drawing on the liquid crystal screen of the own terminal but also drawing on the liquid crystal screen of the opposite terminal from one terminal.

(5) MT possession function The MT possession function uses functions and devices possessed by MT. For example, a function that uses a camera (starts, sets, shoots, and ends a camera), uses GPS (starts a GPS function, acquires GPS information, ends), and refers to an address book ( Start address book, search address book, get information, end), use network function (connect to Web server, download relevant information from Web server, cut communication connection), etc. is there.

(6) PC possession function The PC possession function uses functions and devices possessed by the PC. For example, there are a function that uses computing power (uses a CPU and a memory), a function that uses an input interface device (receives input from a touch panel, a mouse, a keyboard, and the like).

  Next, an application control method in the present embodiment will be described. Each application requests the application control unit 31 for a function to be used. At this time, the application control unit 31 checks whether or not the own terminal has a library that can process the function. When the library which can process the said function on the own terminal is held, after carrying out a library process in the application control part 31, the result is notified to the application parts 15 and 25. FIG.

  On the other hand, if the own terminal does not have a library that can process the function, the same request is made to the opposite application control unit 31. The opposite application control unit 31 checks whether or not the own terminal has a library that can process the function. After performing the corresponding library processing via the application units 15 and 25, the result is notified to the original application control unit 31 and the application units 15 and 25 via the application control unit 31.

  FIG. 23 is a sequence chart when the library on the partner terminal is used. Here, a case where the MT 10 uses the library of the PC 20 will be described. First, the application unit 15 of the MT 10 starts task processing (step S71). Next, the application unit 15 requests the application control unit 31 (MT) to call a library (step S72). The application control unit 31 (MT) receives the library call from the application unit 15 and determines the call (step S73). That is, it is determined whether or not the called library exists in the own terminal. The application control unit 31 (MT) performs call transfer to the PC 20 because the library that received the call does not exist in its own terminal (step S74).

  On the other hand, when receiving the call transfer from the application control unit 31 (MT) of the MT 10, the application control unit 31 (PC) of the PC 20 performs a call determination (step S75). That is, the application control unit 31 (PC) determines whether or not the called library exists in its own terminal. The application control unit 31 (PC) calls the library to the application unit 25 (steps S76 and S77) and performs library processing (step S78) because the library that has received the call exists in its own terminal. Then, the library processing result is notified to the application unit 25 (step S79).

  When receiving the library processing result from the application control unit 31 (PC) (step S80), the application unit 25 outputs a result notification (step S81). The result notification is transmitted to the application control unit 31 (MT) of the MT 10 via the application control unit 31 (PC) (step S82). When the application control unit 31 (MT) of the MT 10 receives the library processing result notification from the application control unit 31 (PC) of the PC 20 (step S83), the application control unit 31 (MT) notifies the application unit 15 of the result. Upon receiving the result notification from the application control unit 31 (MT) (step S84), the application unit 15 ends the task process (step S85).

  Note that the result of processing using the libraries held by both parties as described above can also be expressed in a sequence chart in the same manner when output and displayed on both liquid crystal screens. That is, the application units 15 and 25 make a display request to the application control unit 31 after creating the output contents. At this time, when the terminal to output is the own terminal, the application control unit 31 performs library processing so that the terminal is displayed on the own terminal. On the other hand, when outputting to the opposite terminal, the application control unit 31 outputs to the liquid crystal screen of the opposite terminal while performing the library processing.

  As described above, according to the present invention, as in the first embodiment, when performing data transmission, the high-speed queue and the low-speed queue can be used properly, and as in the second embodiment. This is a function that does not exist in MT, and can execute functions in the PC from MT. Therefore, the first and second embodiments can be implemented in combination. That is, as in the second embodiment, when a function in the PC is executed from the MT with a function that does not exist in the MT, the high-speed queue and the low-speed queue can be used properly.

  Using such an embodiment according to the present invention, a new service can be provided. That is, it is assumed that the user carries two mobile phones or one mobile phone and one PC. According to this embodiment, it is possible to provide a service that enables user interaction from both of two portable terminals. That is, recently, the need for mobile phones equipped with short-range wireless communication means such as Bluetooth (registered trademark) is expanding. For this reason, when using a function that the mobile phone has and a function that the PC does not have, the function of the mobile phone is used from the PC. On the other hand, when using a function that the PC has and a function that the mobile phone does not have, the function of the PC is used from the mobile phone. This invention implement | achieves such a utilization aspect. Furthermore, in order to reinforce the security in the short-range wireless communication means, a mechanism is provided in which the mobile phone and the PC can be used only when the mobile phone, the PC, and the user are gathered. Here, for example, biometric authentication technology or secret sharing technology is used. In addition, a mechanism for ensuring a data transmission rate using short-range wireless communication means and particularly avoiding a delay in data transmission is provided. The usability related to the user interface is improved by properly using a plurality of queues, for example, a high-speed queue and a low-speed queue according to the priority of data. Furthermore, a mechanism for reducing battery consumption caused by always starting the short-range wireless communication means is provided.

  This makes it possible to provide a service that can sufficiently meet the user's needs when the user is in a so-called “two-handed” situation.

  As described above, according to the present embodiment, when data is transmitted to another information processing apparatus, the queue corresponding to the priority is selected, the data to be transmitted is stored in the selected queue, and the priority is stored. Since the data is sequentially read from the queue having a high degree, it is possible to efficiently process the transmission data according to a predetermined priority. In particular, when a plurality of applications are operated in parallel when only one transmission path can be established with another information processing apparatus, data of the plurality of applications can be transmitted and received by generating one data stream. It becomes possible. Moreover, it becomes possible for either one of MT10 or PC20 to utilize the function which the other has. Also, one task can be processed using two portable terminals. The user can freely select a portable terminal to be used according to the TPO.

It is a figure which shows the concept of the distributed apparatus mutual control system which concerns on this embodiment. It is a block diagram which shows schematic structure of the distributed apparatus mutual control system which concerns on this embodiment. It is a block diagram which shows schematic structure of a management part. It is a figure which shows the structural example of the application management table at the time of registering in the application management table 310a shown in FIG. The figure which shows the structure of the data ("1st transmission data") which a transmission origin application part notifies a management part (application cooperation part) when a transmission origin application part requests | requires transmission of the data in an application to a transmission destination application part. It is. It is a figure which shows the structure of the "2nd transmission data" which an application management part notifies to a transmission data control part. It is a figure which shows the structure of the "communication data packet" notified to a communication cooperation part. It is a figure which shows schematic structure of a transmission data control part. 7 is a flowchart showing the operation of the queue insertion unit 82. 5 is a flowchart showing the operation of a queue reading unit 83. It is a figure which shows the structure of 1st reception data. It is a figure which shows schematic structure of the reception data control part 30b. 5 is a flowchart showing the operation of a queue insertion unit 122. 5 is a flowchart showing an operation of a queue reading unit 121. It is a figure which shows the structure of the "2nd reception data" which the application management part 310 transfers to the application cooperation part 310b. It is a flowchart which shows the operation | movement in the case of transmitting as returning ACK using a high-speed queue. It is a flowchart which shows the operation | movement in the case of transmitting as not returning ACK using a high-speed queue. It is a flowchart which shows the operation | movement in the case of transmitting as returning ACK using a low-speed queue. It is a flowchart which shows operation | movement in the case of transmitting as not returning ACK using a low-speed queue. It is a block diagram which shows schematic structure of the management part 13 or 23 which concerns on 2nd Embodiment. It is a figure which shows the structural example of the application information table at the time of registering in the application information 32 shown in FIG. It is a figure which shows the structural example of the function information table registered into the function information 33 shown in FIG. It is a sequence chart in the case of using the library on the other party terminal.

Explanation of symbols

10 MT
DESCRIPTION OF SYMBOLS 11, 21 Input part 12, 22 Output part 13, 23 Management part 14, 24 Communication part 15, 25 Application part 16 Internet communication part 30 Communication management part 30a Transmission data control part 30b Reception data control part 30c Communication cooperation part 81a, 120a High-speed queue 81b, 120b Low-speed queue 82, 121 Queue insertion unit 83, 122 Queue reading unit 310 Application management unit 310a Application management table 310b Application linkage unit 320 Main management unit

Claims (6)

  1. An information processing apparatus that is applied to a communication system that transmits and receives signals to and from each other through a single transmission path in which connections between information processing apparatuses are established by short-range wireless communication ,
    High-speed queue with high priority set in advance,
    A low-speed queue with a low priority set in advance,
    When transmitting data to another information processing apparatus, a queue corresponding to the priority is selected from the high-speed queue and the low-speed queue, and a transmission side queue is inserted to store data to be transmitted to the selected queue And
    A transmission-side queue reading unit that sequentially reads data from the high-speed queue ;
    When transmitting data stored in the high-speed queue, confirmation is not performed before data transmission / reception, but data transmission is unilaterally performed. When transmitting data stored in the low-speed queue, data transmission / reception is not performed. An information processing apparatus comprising: a communication unit that performs data transmission after confirming data transmission and reception in advance .
  2. An information processing apparatus that is applied to a communication system that transmits and receives signals to and from each other through a single transmission path in which connections between information processing apparatuses are established by short-range wireless communication ,
    High-speed queue with high priority set in advance,
    A low-speed queue with a low priority set in advance,
    When receiving data stored in the high-speed queue, without performing confirmation before data transmission / reception, unilaterally performing data transfer and receiving data stored in the low-speed queue,
    Before data transmission / reception, a communication unit that confirms data transmission / reception on both sides,
    When data is received from another information processing apparatus, a queue corresponding to the priority is selected from the high-speed queue and the low-speed queue based on the received data, and the received data is stored in the selected queue. A receiving side queue insertion part to store;
    An information processing apparatus comprising: a receiving side queue reading unit that sequentially reads data from the high-speed queue .
  3. With at least one self-application running on the operating system,
    The information processing apparatus according to claim 1, wherein the self application adds information indicating a queue type and necessity of ACK (Acknowledgement) when transmitting data to another information processing apparatus.
  4.   4. The information according to claim 3, wherein the transmission-side queue insertion unit selects a queue corresponding to a queue type added to data received from the self-application, and stores data to be transmitted to the selected queue. Processing equipment.
  5. Information indicating the functions of the self-application and another application executed in another information processing apparatus is acquired, and there is no function to be executed in the self-application, but there is a function to be executed in the other application. A control unit that outputs a signal to execute the other application to the other information processing apparatus;
    5. The display unit for displaying the execution result of the self application or displaying the execution result of the other application input from the other information processing apparatus. Information processing device.
  6.   When there is a function to be executed in the self application and a function to be executed in the other application, the control unit causes the self application to be executed or to the other information processing apparatus. 6. The information processing apparatus according to claim 5, wherein a signal to execute the other application is output.
JP2008187812A 2008-07-18 2008-07-18 Information processing device Active JP5124375B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2008187812A JP5124375B2 (en) 2008-07-18 2008-07-18 Information processing device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2008187812A JP5124375B2 (en) 2008-07-18 2008-07-18 Information processing device

Publications (2)

Publication Number Publication Date
JP2010026815A JP2010026815A (en) 2010-02-04
JP5124375B2 true JP5124375B2 (en) 2013-01-23

Family

ID=41732590

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2008187812A Active JP5124375B2 (en) 2008-07-18 2008-07-18 Information processing device

Country Status (1)

Country Link
JP (1) JP5124375B2 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9247023B2 (en) 2011-07-27 2016-01-26 Qualcomm Incorporated System and method for prioritizing requests to a SIM
JP6244816B2 (en) 2013-03-26 2017-12-13 日本電気株式会社 Data collection management system, data collection management method, terminal, and management apparatus
JP6501632B2 (en) 2015-06-05 2019-04-17 キヤノン株式会社 Information processing system and control method thereof

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04264945A (en) * 1991-02-20 1992-09-21 Pfu Ltd Data buffering processing system
JPH06244897A (en) * 1993-02-15 1994-09-02 Fujitsu Commun Syst Ltd Packet passing control system
US7275079B2 (en) * 2000-08-08 2007-09-25 International Business Machines Corporation Common application metamodel including C/C++ metamodel
JP4518719B2 (en) * 2001-12-10 2010-08-04 ソニー株式会社 Data processing system, information processing apparatus and method, and computer program

Also Published As

Publication number Publication date
JP2010026815A (en) 2010-02-04

Similar Documents

Publication Publication Date Title
JP4506658B2 (en) Wireless communication system, communication apparatus, setting information providing method, setting information obtaining method, and computer program
JP3499535B2 (en) Content server and network system
US7239891B2 (en) Portable telecommunication apparatus for controlling an electronic utility device
JP6055052B2 (en) Portable information terminal, portable information system, portable information terminal control program
CN100541512C (en) Application providing system and method, portable terminal device and server device
JP2007525894A (en) System and method for managing connection with an available network
JP5671137B2 (en) Method, apparatus, and computer program for automatically generating a proposed information layer in augmented reality
US10432698B2 (en) Information processing method, apparatus, terminal, and server
JP2005509960A (en) Handheld wireless conference technology
CN1254049C (en) Information processing method and information processing appts. having communication function
CN1625878B (en) Method and equipment for processing synchronous related information
JP2008287674A (en) Information processor, client device, information processing system and service connection method
US6862737B1 (en) Communication device and method therefor
JP4546801B2 (en) Method for providing synchronization notification to client device
KR101540475B1 (en) Method and system for sharing data in near field communication network
EP2649499B1 (en) Methods and systems for conducting a remote desktop session via html that supports a 2d canvas and dynamic drawing
JP2003502914A (en) Method and system for retrieving content from a server in a cellular communication system
CN1197322C (en) Radio terminal
US8850031B2 (en) Pairing system, pairing management device, pairing method, and program
BRPI0708224A2 (en) Method and device for automatic bluetooth pairing
KR101440766B1 (en) Method for virtual image delivery service using printed matter
US9800708B2 (en) Operation method and system of mobile terminal
CN101822020A (en) Pairing exchange
CN100535936C (en) Network visiting-card processing method and system
CN1244064C (en) Communication terminal with browser and system containing the same terminal

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20110128

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20120419

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20120501

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20120629

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20121016

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20121029

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20151102

Year of fee payment: 3

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150