WO2014123082A1 - Système de transfert de fichier, procédé de transfert de fichier, terminal de communication, son procédé de commande, et programme d'application - Google Patents

Système de transfert de fichier, procédé de transfert de fichier, terminal de communication, son procédé de commande, et programme d'application Download PDF

Info

Publication number
WO2014123082A1
WO2014123082A1 PCT/JP2014/052429 JP2014052429W WO2014123082A1 WO 2014123082 A1 WO2014123082 A1 WO 2014123082A1 JP 2014052429 W JP2014052429 W JP 2014052429W WO 2014123082 A1 WO2014123082 A1 WO 2014123082A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
transfer
identifier
communication terminal
transfer source
Prior art date
Application number
PCT/JP2014/052429
Other languages
English (en)
Japanese (ja)
Inventor
蒲生竜哉
Original Assignee
Gamo Tatsuya
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
Priority claimed from JP2013019987A external-priority patent/JP5486706B1/ja
Priority claimed from JP2013249555A external-priority patent/JP6002119B2/ja
Application filed by Gamo Tatsuya filed Critical Gamo Tatsuya
Publication of WO2014123082A1 publication Critical patent/WO2014123082A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/02—Details of telephonic subscriber devices including a Bluetooth interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/64—Details of telephonic subscriber devices file transfer between terminals

Definitions

  • the present invention relates to a technique for transferring a file from a communication terminal to a communication terminal.
  • Patent Document 1 discloses that a mobile terminal includes a plurality of wireless communication units such as a wireless LAN, Bluetooth (registered trademark), non-contact communication, and infrared communication, and wireless communication corresponding to the data type and data size.
  • a technique for selecting and communicating a part is disclosed.
  • Patent Document 2 discloses an electronic device (cell phone) from an electronic camera at a shooting site by cooperation of identification information communication via short-range wireless communication such as Bluetooth and image data transfer via an image server. ) Discloses a technique for transferring large-capacity image data. Also, in an electronic camera, identification information of image data is generated based on the identification information of a transfer destination electronic device, added to the image data, and uploaded. A technique for downloading image data to which identification information of generated image data is added is described in the electronic device.
  • Patent Document 1 is a technique for improving wireless data transfer between mobile terminals in real time, and the user can transfer data between mobile terminals in the field no matter which wireless communication unit is used. You need to wait for it to complete. Therefore, particularly when transferring a large-capacity file between portable terminals, a wasteful time for waiting for the completion of the file transfer occurs, which is inefficient.
  • the technique described in Patent Document 2 uses the identification information of the transfer destination electronic device to generate the identification information of the image data, and therefore corresponds to the number of transmission destinations in the transfer source terminal that is an electronic camera. Identification information generation processing, identification information addition and upload processing are required.
  • the transfer of image data in Patent Document 2 is a cooperative process at a shooting site where short-range wireless communication is possible, and it is necessary to wait for the completion of image data transfer at the shooting site. Same as 1.
  • An object of the present invention is to provide a technique for solving the above-described problems.
  • a file transfer system provides: An identifier sharing means for sharing a transfer source identifier for identifying a transfer source and a file identifier of a file to be transferred between the transfer source communication terminal and the transfer destination communication terminal using near field communication; File transfer means for transferring a file identified by the transfer source identifier and the file identifier from the transfer source communication terminal to the transfer destination communication terminal via a server; Is provided.
  • a file transfer method includes: An identifier sharing step for sharing a transfer source identifier for identifying a transfer source and a file identifier of a file to be transferred between the transfer source communication terminal and the transfer destination communication terminal using near field communication, A file transfer step of transferring a file identified by the transfer source identifier and the file identifier from the transfer source communication terminal to the transfer destination communication terminal via a server; including.
  • a communication terminal provides: Proximity communication means for directly performing proximity communication with other communication terminals; When transferring the first file from the communication terminal to the transfer destination communication terminal, using the proximity communication means, a first file identifier for identifying the first file and a first transfer source identifier for identifying the transfer source When transmitting to the transfer destination communication terminal and transferring the second file from the transfer source communication terminal to the communication terminal, using the near field communication means, a second file identifier for identifying the second file and a transfer source are set.
  • Identifier exchange means for receiving a second transfer source identifier for identification from the transfer source communication terminal; When transferring a file from the communication terminal to the transfer destination communication terminal, the first transfer source identifier, the first file identifier, and the first file are transmitted to a server accessible by the transfer destination communication terminal. , When transferring a file from the transfer source communication terminal to the communication terminal, a file transfer means for receiving the second file identified by the second transfer source identifier and the second file identifier from a server; Is provided.
  • a communication terminal control method includes: A first file identifier for identifying the first file using a near field communication means for directly performing near field communication with another communication terminal when transferring the first file from the communication terminal to the destination communication terminal; When the first transfer source identifier for identifying the transfer source is transmitted to the transfer destination communication terminal and the second file is transferred from the transfer source communication terminal to the communication terminal, the proximity communication means is used to An identifier exchange step of receiving a second file identifier for identifying a file and a second transfer source identifier for identifying a transfer source from the transfer source communication terminal; When transferring a file from the communication terminal to the transfer destination communication terminal, the first transfer source identifier, the first file identifier, and the first file are transmitted to a server accessible by the transfer destination communication terminal. A file transfer step of receiving the second file identified by the second transfer source identifier and the second file identifier from a server when transferring a file from the transfer source communication terminal to the communication terminal; including.
  • an application program provides: A first file identifier for identifying the first file using a near field communication means for directly performing near field communication with another communication terminal when transferring the first file from the communication terminal to the destination communication terminal;
  • the proximity communication means is used to An identifier exchange step of receiving a second file identifier for identifying a file and a second transfer source identifier for identifying a transfer source from the transfer source communication terminal;
  • the first transfer source identifier, the first file identifier, and the first file are transmitted to a server accessible by the transfer destination communication terminal.
  • a mobile terminal smartphone will be described as a representative communication terminal.
  • the mobile terminal of the communication terminal may be a tablet or a mobile phone, and the communication terminal may be a notebook PC (Personal Computer) or a desktop PC, and the present invention is applied. Have the same effect.
  • a file transfer system as a first embodiment of the present invention will be described.
  • infrared communication that is proximity communication between the mobile terminals is used.
  • the file transfer application of the mobile terminal automatically operates and relays a file transfer server connected to the network to realize transfer of a large capacity file.
  • exchange of file information, transfer source information, and transfer destination information by infrared communication is instantaneous, and subsequent file transfer is automatically processed by the mobile terminal. Therefore, files can be transferred between mobile terminals even when the mobile terminal is out of the service area, and transfer of large files between mobile terminals can be performed without user operation without waiting for the completion of file transfer on site. Can be done.
  • each user who performs file transfer uses a transfer source identifier (hereinafter referred to as transfer source ID) and transfer destination specific to the file transfer system.
  • An identifier hereinafter referred to as transfer destination ID
  • a file identifier hereinafter referred to as a file ID
  • a transfer destination ID hereinafter referred to as a transfer destination ID
  • a transfer source ID is attached to the file to be transferred. Therefore, as described in the present embodiment, it is not essential for the user to register as a member in the file transfer server.
  • terminal ID which is a terminal identifier to each portable terminal from a file transfer server.
  • the terminal ID of the mobile terminal may be assigned by a user application.
  • the file transfer server can know the transfer destination ID and the transfer source ID from the IP address, the minimum necessary ID information may be attached to the file to be transferred. For example, a file ID and a transfer destination ID are attached to upload a file from the transfer source, and a file ID and a transfer destination ID are attached to the file download to the transfer destination in the case of the push method, and in the case of the polling method Attaches a file ID.
  • the file ID and the transfer source ID may be shared between portable terminals that transfer files.
  • the file ID and the transfer source ID are passed from the transfer source mobile terminal to the transfer destination mobile terminal by proximity communication. That is, the file ID and the transfer source ID are issued from the transfer source portable terminal to the transfer destination portable terminal as a voucher for the transfer destination portable terminal to reserve acquisition of the file.
  • the terminal can obtain a desired file from the file transfer server without making a mistake.
  • the transfer source communication terminal uploads one file to which the transfer source ID is added, any transfer destination mobile terminal that has been given a voucher can download the file. The file can be transferred efficiently.
  • FIG. 1 is a diagram showing an outline and configuration of a file transfer system 100 according to the present embodiment.
  • FIG. 1 shows a simplified configuration showing the concept of the present embodiment.
  • the male 101 and the female 102 identify a file to be transferred by proximity communication such as infrared communication. Since the file ID and the terminal ID to be shared are shared, for example, the file transfer can be realized by exchanging the terminal IDs with each other.
  • the file transfer can be realized by exchanging the terminal IDs with each other.
  • at least a file ID and a terminal ID that is a transfer source ID set in the mobile terminal 110 are passed from the mobile terminal 110 to the mobile terminal 120, and at least the mobile terminal is transferred from the mobile terminal 120 to the mobile terminal 110.
  • a terminal ID which is a transfer destination ID set to 120 is passed.
  • the process for file transfer at the site where the male 101 and the woman 102 meet ends with the exchange of the identifier (ID), and there is no need to wait for the completion of the file transfer at the site.
  • ID identifier
  • the processing ends in an instant. Moreover, it is not necessary to consider whether or not the mobile terminal is out of the service area.
  • the mobile terminals 110 and 120 that share the file ID of the file to be transferred, the transfer source ID, and the transfer destination ID respectively move to completely different locations when the male 101 and the female 102 are separated.
  • the above-described data transfer application attaches the file ID, the transfer destination ID, and the transfer source ID
  • the file to be transferred is uploaded from the portable terminal 110 to the file transfer server 130 having the server unit 131 and the file buffer 132.
  • the uploaded file is stored in the file buffer 132 in association with the file ID, transfer destination ID, and transfer source ID.
  • the portable terminal 120 held by the female 102 when the mobile terminal 120 enters any of the areas, that is, the area B in FIG. 1, the above-described data transfer application requests a file based on the file ID and transfers the file. Is downloaded from the file transfer server 130 to the portable terminal 120.
  • the portable terminal 120 For downloading from the file transfer server 130 to the portable terminal 120, there is a polling method in which the portable terminal 120 requests the file transfer server 130 for a file whose file ID and transfer source ID match. In addition, there is a push method in which when the file transfer server 130 holds a file in the file buffer 132, it is downloaded to the mobile terminal 120 having the transfer destination ID. In the case of the polling method, when the requested file has not yet been uploaded from the portable terminal 110, this is reported. Thereafter, the push method may be changed.
  • the file having the file ID exchanged by proximity communication such as infrared communication is transferred from the mobile terminal 110 having the transfer source ID to the mobile terminal 120 having the transfer destination ID via the file transfer server 130. It was. In this way, the file transfer is surely realized regardless of various disadvantageous conditions at the site where the file transfer is desired, such as a problem in the area and a problem of the capacity of the file to be transferred.
  • ⁇ Operation procedure of mobile terminal> 2A and 2B are diagrams illustrating an operation procedure of the mobile terminals 110 and 120 in the file transfer system 100 according to the present embodiment.
  • the left diagram and the middle diagram of the portable terminals 110 and 120 in FIG. 2A are diagrams showing an operation procedure of registration in the file transfer server 130 of the portable terminal. 2A, the display screen 211 of the mobile terminal 110 and the display screen 221 of the mobile terminal 120 are common, and are solicitation screens for file transfer services from the file transfer server 130.
  • the user inputs the user ID and password and the transfer terminal ID used by the user and selects the join button, registration to the file transfer server 130 is performed.
  • the file transfer server 130 downloads a file transfer application (hereinafter referred to as a file transfer application) for realizing a file transfer service to each registered mobile terminal. Then, as shown on the display screen 212 of the mobile terminal 110 and the display screen 222 of the mobile terminal 120, a file transfer button is displayed for user selection after downloading.
  • a file transfer application hereinafter referred to as a file transfer application
  • the file transfer button When attempting to transfer a file from the mobile terminal 110 to the mobile terminal 120, first, as shown in the right diagram of FIG. 2A, the file transfer button is selected to start the file transfer application. Then, from the display screen 213 of the mobile terminal 110, the file ID of the file to be transferred and the transfer source ID (terminal ID of the mobile terminal 110) are input. The input of the transfer source ID is necessary when the configuration is newly set, but is not necessary when it is assigned to the mobile terminal 110 in advance. On the other hand, a transfer destination ID (terminal ID of the portable terminal 120) is input from the display screen 223 of the portable terminal 120. Note that the input of the transfer destination ID is necessary when the configuration is newly set, but is not necessary when the transfer destination ID is assigned to the mobile terminal 120 in advance.
  • FIG. 2B shows the exchange between the portable terminals 110 and 120 of the file ID, the transfer source ID, and the transfer destination ID by infrared communication as proximity communication in the left half, and the right half passes through the file transfer server 130 by network communication. Indicates file transfer.
  • a message for inducing infrared communication is displayed on the display screen 214 of the portable terminal 110 and the display screen 224 of the portable terminal 120 in the vicinity of the portable terminal of the file transfer partner. Has been.
  • the file ID and the transmission source ID are passed from the portable terminal 110 to the portable terminal 120 by the infrared communication.
  • To the destination ID When transmission / reception by infrared communication is completed, the display screen 215 of the mobile terminal 110 and the display screen 225 of the mobile terminal 120 notify the completion of transmission / reception.
  • the portable terminals 110 and 120 have a common file ID, transmission source ID, and transmission destination ID related to file transfer.
  • the mobile terminal 110 transfers the file to be transferred together with the file ID and the transfer source ID at an appropriate time, for example, when entering the service area or at midnight when the communication fee is low, without the user's detection.
  • Upload to server 130 A display screen 216 of the portable terminal 110 indicates that a file is being uploaded. Note that there may be no display during uploading.
  • the file transfer server 130 holds the uploaded file in association with the file ID and the transmission source ID.
  • the file transfer application downloads the file to be transferred together with the file ID and the transfer source ID to the mobile terminal 120 at an appropriate time, for example, when entering the service area or at midnight when the communication charge is low, without the user's detection. Is done.
  • the display screen 226 of the mobile terminal 120 is displayed when the file download is completed. Then, the mobile terminal 120 notifies the file transfer server 130 of the completion of file transfer.
  • the file transfer server 130 receives the file transfer completion notification from the mobile terminal 120 and notifies that the file transfer of the mobile terminal 110 is completed.
  • the display screen 217 of the portable terminal 110 displays that the file transfer has been completed in response to the file transfer completion notification from the file transfer server 130.
  • FIG. 3 is a sequence diagram showing an operation procedure of the file transfer system 100 according to the present embodiment.
  • the serving base stations 311 to 313, 321, and 322 may be the same base station or different base stations.
  • step S ⁇ b> 301 the mobile terminal 110 performs a procedure for receiving a file transfer service from the file transfer server 130 via the located base station 311.
  • step S ⁇ b> 303 the file transfer server 130 downloads an application program for file transfer to the mobile terminal 110 via the located base station 311.
  • step S305 the mobile terminal 110 displays an application start button.
  • step S ⁇ b> 307 the portable terminal 120 performs a procedure for receiving the file transfer service from the file transfer server 130 via the located base station 321.
  • step S ⁇ b> 309 the file transfer server 130 downloads an application program for file transfer to the mobile terminal 120 via the located base station 321.
  • step S311 the mobile terminal 110 displays an application start button.
  • step S321 the portable terminal 110 sets a file ID and a transfer source ID in step S321, and generates a transmission message to the portable terminal 120.
  • step S321 the portable terminal 110 sets a file ID and a transfer source ID, and generates a transmission message to the portable terminal 120.
  • step S329 identifiers (file ID, transfer source ID, transfer destination ID) for file transfer are exchanged between the mobile terminal 110 and the mobile terminal 120 by infrared communication. By this identifier exchange, identifier sharing of the file ID, the transfer source ID, and the transfer destination ID is realized between the mobile terminal 110 and the mobile terminal 120.
  • both the mobile terminal 110 and the mobile terminal 120 are outside the coverage area of the visited base station 311 or the visited base station 321, and network communication is impossible.
  • the file to be transferred is transferred to the file ID, the transfer destination ID (terminal ID of the mobile terminal 120), and the transfer source ID (mobile terminal) in step S 331. 110 to the file transfer server 130 accessible from the portable terminal 120. If the terminal ID of the portable terminal 110 is registered in the file transfer server 130 in advance, the transfer source ID is not necessary.
  • the file transfer server 130 receives the file uploaded from the mobile terminal 110.
  • the file transfer server 130 holds the file in the file buffer 132 in step S335. At this time, the file is held in association with the file ID, transfer destination, and transfer source ID.
  • the file transfer server 130 downloads the file held via the located base station 322 to the portable terminal 120 in step S337.
  • the download from the file transfer server 130 to the portable terminal 120 may be a polling method (pull method) performed by a request from the portable terminal 120 or a push method sent from the file transfer server 130.
  • the file to be downloaded is confirmed by at least the file ID and the transfer source ID. Further, confirmation may be made by the transfer destination ID.
  • the portable terminal 120 receives the downloaded file and stores it in the file DB.
  • step S341 the portable terminal 120 notifies the user of the completion of the file transfer, and ends the file transfer application in step S343. Note that the notification of the completion of the file transfer in step S341 may be omitted.
  • the file transfer server 130 transmits a file transfer completion notification to the portable terminal 110 via the serving base station 313 in step S345.
  • the portable terminal 110 notifies the user of a file transfer completion notification in step S347, and ends the file transfer application in step S349. Note that the notification of the completion of the file transfer in step S347 may be omitted.
  • FIG. 4 is a diagram showing a software configuration for operating the file transfer system 100 according to the present embodiment.
  • a thick line frame indicates a file transfer application.
  • a server program 432 operates on an OS (Operation System) 431.
  • the server program 432 manages files held in the file buffer 132 via the file management module 433.
  • the file transfer application 434 of this embodiment includes a transfer source control module 435 and a transfer destination control module 436.
  • the transfer source control module 435 controls the communication control module 437 and receives a file uploaded from the file transfer application 415 of the transfer source portable terminal 110 via the communication control module 416. Then, the transfer source control module 435 passes the received file to the file management module 433 via the server program 432 and holds it in the file buffer 132.
  • the transfer source control module 435 reads a desired file from the file buffer 132 by the file management module 433 via the server program 432. Then, the transfer source control module 435 controls the communication control module 437 and downloads the file to the file transfer application 425 of the transfer destination mobile terminal 120 via the communication control module 426.
  • the portable terminal program 412 operates on the OS 411.
  • the portable terminal program 412 manages files by the file management module 413. Further, the portable terminal program 412 controls the near field communication using infrared rays by the infrared communication module 414.
  • the file transfer application 415 of the present embodiment exchanges identifiers with the transfer destination mobile terminal 120 by using the infrared communication module 414, acquires a file to be transferred by the file management module 413, and transmits a file transfer server via the communication control module 416. Upload to 130.
  • the portable terminal program 422 operates on the OS 421.
  • the portable terminal program 422 manages files by the file management module 423. Further, the portable terminal program 422 controls the near field communication using infrared rays by the infrared communication module 424.
  • the file transfer application 425 of the present embodiment exchanges identifiers with the transfer source mobile terminal 110 using the infrared communication module 424, downloads the file from the file transfer server 130 via the communication control module 426, and transfers the file using the file management module 423. Store the modified file.
  • FIG. 5 is a block diagram showing a functional configuration of the file transfer server 130 according to the present embodiment.
  • Each functional component in FIG. 5 may be configured by independent hardware, or each functional component is realized by executing a program stored in a memory or storage by a CPU (Central Processing Unit). May be.
  • a database hereinafter referred to as DB
  • a file buffer are stored in the storage, and data necessary for each process is temporarily stored in the memory.
  • the file transfer server 130 includes a communication control unit 501 that controls communication via a network.
  • the user registration information receiving unit 502 receives user registration information from the mobile terminal via the communication control unit 501.
  • the user registration information includes information such as a user ID and a password.
  • the registration information may include the terminal ID.
  • the user registration unit 503 registers the user registration information received by the user registration information reception unit 502 in the user DB 504.
  • the application DB 505 stores a file transfer application that is downloaded and executed by the mobile terminal in order to realize the file transfer of the present embodiment.
  • the application acquisition unit 506 acquires an application to be downloaded to the corresponding mobile terminal from the application DB 505 at the time of user registration.
  • the application transmission unit 507 transmits the application acquired by the application acquisition unit 506 to the corresponding mobile terminal via the communication control unit 501.
  • the transfer file receiving unit 508 receives the file uploaded from the transfer source mobile terminal via the communication control unit 501.
  • the transfer file storage unit 509 stores the transfer file received by the transfer file reception unit 508 in the file buffer 132.
  • the file buffer 132 holds files corresponding to the file ID, transfer destination ID, and transfer source ID.
  • the transfer file acquisition unit 511 acquires a file to be transferred from the file buffer 132 corresponding to at least the file ID and the transfer source ID.
  • the transfer file transmission unit 512 downloads the file acquired by the transfer file acquisition unit 511 to the transfer destination portable terminal via the communication control unit 501.
  • the transfer file request reception unit 513 receives a file request from the transfer source portable terminal via the communication control unit 501 in the case of the polling method.
  • the file request includes at least a file ID and a transfer source ID. Then, the transfer file request reception unit 513 passes reception of the file request to the transfer file acquisition unit 511.
  • the transfer file reception unit 508, the transfer file storage unit 509, the transfer file acquisition unit 511, the transfer file transmission unit 512, and the transfer file request reception unit 513 constitute the file transfer application 434 of this embodiment. .
  • the function of the file transfer application 434 is not limited to these.
  • FIG. 6 is a block diagram illustrating a functional configuration of the mobile terminals 110 and 120 according to the present embodiment. Note that there is no difference in the functional configuration of the present embodiment regardless of whether the mobile terminal is a node type PC or a smartphone. The operations of the mobile terminals 110 and 120 differ depending on whether they are the file transfer source or the transfer destination, but the configuration is the same.
  • Each functional component in FIG. 6 may be configured by independent hardware, or each functional component may be realized by executing a program stored in a memory or storage by a CPU (Central Processing Unit). May be. In this case, for example, the database is stored in the storage, and data necessary for each process is temporarily stored in the memory.
  • CPU Central Processing Unit
  • the mobile terminal 110 of this embodiment includes a communication control unit 601 as a network communication control unit that controls communication with the file transfer server 130 via the network.
  • the mobile terminal 110 includes an operation unit 602 including a touch panel and a keyboard, and a file transfer service / user registration unit 603 that requests user registration from the operation unit 602 to the file transfer server 130.
  • An operation related to the file transfer process from the operation unit 602 is transmitted to the file transfer application 415 (425 in the case of the portable terminal 120).
  • the file transfer application reception unit 604 receives the file transfer application 415 downloaded from the file transfer server 130.
  • the display unit 605 displays the operation screen, the status of the mobile terminal, or the reception screen.
  • the screen displayed on the display unit 605 includes a screen related to the file transfer application 415 and a general-purpose screen of the mobile terminal, which may be switched or combined and displayed as a plurality of areas.
  • the infrared communication unit 606 controls near field communication with other portable terminals using infrared rays as a near field communication control unit.
  • infrared communication is described as a representative of proximity communication. However, it may be communication between portable terminals by a facing user, such as electromagnetic non-contact communication or Bluetooth (registered trademark).
  • the file DB 607 stores files that the mobile terminal 110 has.
  • the file DB 607 stores a downloaded file, a file acquired by proximity communication, a video file acquired from a camera (not shown), a file acquired via a storage medium, and the like.
  • the downloaded file transfer application 415 of the present embodiment includes a transfer identifier exchange unit 611, a transfer identifier holding unit 612, a file acquisition unit 613, a file transmission unit 614, a file reception unit 615, and a file storage unit. 616. In the case of the polling method, a transfer file request transmission unit 617 is included. Note that the function of the file transfer application 415 is not limited to these.
  • the transfer identifier exchanging unit 611 exchanges each identifier used for file transfer with another portable terminal via the infrared communication unit 606 as an identifier exchange control unit.
  • the identifier to be exchanged includes a file ID, a transfer source ID, and a transfer destination ID.
  • the transfer identifier holding unit 612 holds an identifier exchanged with another portable terminal via the infrared communication unit 606 for use when transferring a file via the network and the file transfer server 130 later.
  • the identifier held by the transfer identifier holding unit 612 includes a file ID, a transfer source ID, and a transfer destination ID. Further, the transfer identifier holding unit 612 stores an identifier exchange date and time, a file transfer completed / untransfer flag, and the like.
  • the file transfer application 415 includes a file acquisition unit 613, a file transmission unit 614, a file reception unit 615, and a file storage unit 616 as file transfer control units. Furthermore, the file transfer application 415 may include a transfer file request transmission unit 617 as a file transfer control unit.
  • the file acquisition unit 613 acquires a file corresponding to the file ID held in the transfer identifier holding unit 612 from the file DB 607.
  • the file transmission unit 614 uploads the file acquired by the file acquisition unit 613 to the file transfer server 130 together with the file ID, the transfer destination ID, and the transfer source ID.
  • the file receiving unit 615 receives the transferred file downloaded from the file transfer server 130.
  • the file storage unit 616 stores the file received by the file receiving unit 615 in the file DB 607 corresponding to the file ID. If a file transfer history is left, the transfer source ID and the IP address of the transfer source may be stored in correspondence with the file ID.
  • the transfer file request transmission unit 617 receives a file request to the file transfer server 130 in the case of the polling method. The file request includes at least a file ID and a transfer source ID. Then, the transfer file request transmission unit 617 passes the file request to the file reception unit 615.
  • FIG. 7 is a diagram showing a format of a token exchanged by infrared communication between portable terminals according to the present embodiment. Note that FIG. 7 is a conceptual format, and for the detailed format, refer to the standardized specifications of the proximity communication protocol such as infrared communication and non-contact communication.
  • the token message 710 passed from the transfer source portable terminal 110 to the transfer destination portable terminal 120 includes a transfer source command 711, a file ID 712, a transfer source ID 713, and an error correction code 714.
  • the transfer source command 711 indicates that this token message 710 is from the transfer source.
  • the file ID 712 identifies a file to be transferred.
  • the transfer source ID 713 is a user-set identifier that identifies the mobile terminal 110 that is the transfer source of the file.
  • the error correction code 714 is an error correction code such as CRC that corrects an error of the token message 710, and is not limited.
  • the token message 720 passed from the transfer destination portable terminal 120 to the transfer source portable terminal 110 includes a transfer destination command 721, a transfer destination ID 722, and an error correction code 723.
  • the transfer destination command 721 indicates that this token message 720 is from the transfer destination.
  • the transfer destination ID 722 is a user-set identifier that identifies the portable terminal 120 that is the transfer destination of the file.
  • the error correction code 723 is an error correction code such as CRC that corrects the error of the token message 720, and is not limited.
  • FIG. 8 is a block diagram illustrating a configuration of the transfer identifier holding unit 612 in the mobile terminals 110 and 120 according to the present embodiment.
  • the transfer identifier holding unit 612 in FIG. 8 includes a terminal identifier holding unit 810 that holds a terminal ID set in the portable terminal, a transfer file information holding unit 820 that holds information of a file to be transferred, and transfer file information.
  • a transfer status table 830 indicating the status of the file held in the transfer status code 825 of the holding unit 820 is held.
  • the terminal identifier holding unit 810 stores a unique identifier 811, an IP address 812, an IP telephone number 813, and a file transfer terminal ID 815 used for file transfer according to the present embodiment in association with each other.
  • the terminal identifier is not limited to the above example.
  • the IP address 812 and the file transfer terminal ID 815 are essential.
  • the transfer file information holding unit 820 includes information 821 indicating whether the portable terminal is a file transfer source or transfer destination, a file ID 822 of a file to be transferred, a transfer partner 823, and a token exchange date / time 824 when the identifier is exchanged by proximity communication
  • the current transfer status code 825 is stored.
  • the transfer destination ID received by the token from the transfer destination is added to the transfer partner 823.
  • the file ID 822 received by the token from the transfer source and the transfer source ID are added to the transfer partner 823.
  • the transfer status table 830 is a table showing the contents of the transfer status code 825 of the terminal identifier holding unit 810.
  • the transfer status table 830 stores the status in association with each of information 831 divided into a transmission status when the mobile terminal is a transmission source and a reception status where the mobile terminal is a transfer destination.
  • the transfer status type 832 is classified into untransmitted, server transmitted, file transferred, error, and the like.
  • a transfer status code 833 corresponding to each transfer status type 832 is assigned.
  • the transfer status type 832 is classified into non-reception, server file wait, file transfer completed, error, and the like.
  • a transfer status code 833 corresponding to each transfer status type 832 is assigned.
  • the transfer status code 833 is assigned “0x” in the case of transmission at the transfer source and “1x” in the case of reception at the transfer destination.
  • the transfer status type 832 is not limited to the example of FIG.
  • terminal identifier holding unit 810 the terminal identifier holding unit 810, and the transfer status table 830 do not need to be held together in the transfer identifier holding unit 612, but are distributed to necessary function components. Also good.
  • FIG. 9 is a diagram showing a format of a message transferred in the file transfer system 100 according to the present embodiment. Note that FIG. 9 is a conceptual format, and for the detailed format, refer to the standardization specification of the protocol for network communication, particularly IP communication.
  • a transmission message 910 uploaded from the transfer source portable terminal 110 to the file transfer server 130 includes a header 911 for IP communication, a header 912 for file transfer according to the present embodiment, file information 913, an error correction code 914, including.
  • the header 911 for IP communication includes the IP address of the file transfer server 130 as a transmission destination and the IP address of the portable terminal 110 that is the transfer source as a transmission source.
  • the file transfer header 912 includes a terminal ID of the portable terminal 120 as a transfer destination ID and a terminal ID of the portable terminal 110 as a transfer source ID.
  • the file information 913 includes a file ID and file data.
  • the error correction code 914 is an error correction code such as CRC that corrects the error of the transmission message 910, and is not limited. If the terminal ID of the transfer source portable terminal 110 is registered in the file transfer server 130 in advance, the transfer source ID can be known by the file transfer server 130, so the transfer source ID of the file transfer header 912 is not essential. Absent.
  • the file transfer server 130 that has received the transmission message 910 stores a file ID, a transfer destination ID, a transfer source ID, and the like in the file buffer 132 in association with the file.
  • a transmission message 920 downloaded from the file transfer server 130 to the transfer destination mobile terminal 120 includes an IP communication header 921, the file transfer header 922 of the present embodiment, file information 923, an error correction code 924, including.
  • the header 921 for IP communication includes the IP address of the portable terminal 120 that is the transfer destination as the transmission destination and the IP address of the file transfer server 130 as the transmission source.
  • the file transfer header 922 includes the terminal ID of the portable terminal 120 as the transfer destination ID and the terminal ID of the portable terminal 110 as the transfer source ID.
  • the file information 923 includes a file ID and a file.
  • the error correction code 924 is an error correction code such as CRC that corrects the error of the transmission message 920, and is not limited. Note that the file transfer header 922 surrounded by a broken line is not essential if the polling method is from the transfer destination portable terminal 120 because file identification is performed in the file transfer server 130.
  • FIG. 10 is a diagram showing the configuration of the file buffer 132 in the file transfer server 130 according to the present embodiment.
  • the file buffer 132 includes a file holding unit 1010 that temporarily holds a file to be transferred from the transfer source portable terminal to the transfer destination portable terminal, and a transfer status table 1020 that indicates the status of the file held in the transfer status code 1014 of the file holding unit 1010. Including.
  • the file holding unit 1010 stores a file transfer source ID 1012, a file transfer destination ID 1013, a transfer status code 1014 indicating the current status, and a file pointer 1015 pointing to the file content in association with the file ID 1011.
  • the transfer status table 1020 is a table showing the contents of the transfer status code 1014 in the file buffer 132.
  • the transfer status table 1020 is classified as the transfer status type 1021 into file reception from the transfer source, file transfer waiting to the transfer destination, file transfer completed, error, and the like.
  • a transfer status code 1022 corresponding to each transfer status type 1021 is assigned.
  • the transfer status type 1021 is not limited to the example of FIG.
  • file holding unit 1010 and the transfer status table 1020 do not need to be held together in the file buffer 132, and may be distributed to necessary function components.
  • FIG. 11 is a flowchart showing a processing procedure of the file transfer server 130 according to the present embodiment. This flowchart is executed using the storage and the memory by the CPU of the file transfer server 130 to realize the functional configuration unit of FIG.
  • the flowchart of FIG. 11 starts when an event such as a registration application reception from a mobile terminal, a file upload request, or a file download request occurs.
  • step S1111 the file transfer server 130 determines whether or not it is a registration application for a file transfer service from a mobile terminal. Further, in step S1121, the file transfer server 130 determines whether or not it is an upload request for a file to be transferred from the transfer source portable terminal. In step S1131, the file transfer server 130 determines whether it is a download request for a file to be transferred from the transfer destination mobile terminal.
  • the file transfer server 130 acquires the user ID and password which the user input from the portable terminal in step S1113. In step S1115, the file transfer server 130 registers the user. Next, in step S1117, the file transfer server 130 downloads a file transfer application for the file transfer service to the registered mobile terminal of the user.
  • the file transfer server 130 receives the file to be transferred together with the file ID, transfer destination ID, transfer source ID, and the like from the transfer source communication terminal in step S1123.
  • the file transfer server 130 stores the received transfer file in the file buffer 132 in association with the file ID, the transfer destination ID, the transfer source ID, and the like.
  • the file transfer server 130 searches the file buffer 132 using the file ID, transfer destination ID, transfer source ID, etc. in step S1133. .
  • the file transfer server 130 transmits the searched transfer file to the transfer destination portable terminal together with the file ID, transfer destination ID, transfer source ID, and the like.
  • the transfer destination portable terminal is notified of the non-transmission from the transfer source. Further, the transfer source may be notified that there is a request from the transfer destination.
  • FIG. 12A is a flowchart illustrating a processing procedure of the mobile terminals 110 and 120 according to the present embodiment. This flowchart is executed using the storage and the memory by the CPUs of the mobile terminals 110 and 120 to realize the functional configuration unit of FIG.
  • the flowchart of FIG. 12A starts when an event such as a registration application to the file transfer server 130 or a file transfer application activation instruction occurs.
  • step S1211 the portable terminal determines whether or not it is a registration application for the file transfer service for the file transfer server 130.
  • step S1221 the mobile terminal determines whether the activation instruction for the file transfer application is issued.
  • the mobile terminal transmits the user ID and password input by the user to the file transfer server 130 in step S1213.
  • the mobile terminal receives the file transfer application used in the file transfer service downloaded from the file transfer server 130.
  • a button for starting a file transfer application may be displayed on the mobile terminal.
  • the portable terminal If it is a start instruction of the file transfer application, the portable terminal starts the file transfer application and receives a file transfer service in step S1223.
  • FIG. 12B is a flowchart showing the procedure of the file transfer application executed by the mobile terminals 110 and 120 according to the present embodiment. This flowchart is started in step S1223 of FIG. 12A.
  • step S1251 the mobile terminal determines whether the user has selected the file transfer source or the transfer destination from the inquiry of the file transfer application. Note that the selection of the transfer source and the transfer destination may be automatically selected as the transfer source, regardless of the user.
  • the portable terminal acquires the file ID of the file to be transferred in step S1253.
  • the mobile terminal generates a transfer source token (see FIG. 7).
  • the portable terminal transmits the generated transfer source token to the transfer destination portable terminal and receives the transfer destination token from the transfer destination portable terminal in step S1257.
  • token exchange is executed.
  • the portable terminal when the transfer destination is selected, the portable terminal generates a transfer destination token (see FIG. 7) in step S1259.
  • the portable terminal transmits the generated transfer destination token to the transfer source portable terminal and receives the transfer source token from the transfer source portable terminal in step S1261. Then, token exchange is executed.
  • the portable terminal When the token exchange is completed, the portable terminal adds information including the file ID to be transferred, the transfer destination ID, and the transfer source ID to the transfer file information holding unit 820 in step S1263. In this information, token exchange date / time and transfer status code non-transmission / non-reception are set (see FIG. 8).
  • step S1271 the portable terminal determines whether an upload condition from the portable terminal to the file transfer server 130 is satisfied, and in step S1281, whether a download condition from the file transfer server 130 to the portable terminal is satisfied. , Is determined.
  • the upload conditions are that the mobile device is within the service area, that the mobile device is not exchanging other files, that the file transfer application has passed a preset time interval, or that the user has set a time interval Etc. Further, a time zone based on the communication status of the network may be considered. Download conditions include that the mobile device is in the service area, that the mobile device is not exchanging other files, that the time interval preset by the file transfer application in the case of the polling method, Including a time interval set by the user. Further, a time zone based on the communication status of the network may be considered.
  • the mobile terminal process leaves the file transfer application and executes other processes on the mobile terminal. Then, for example, it is desirable to return to step S1271 of the file transfer application from another process according to the time sharing process without burden on the user operation or the like.
  • step S1273 the portable terminal generates a transmission message for upload in step S1273 (see FIG. 9). Then, the transfer file is transmitted to the file transfer server 130 by the generated transmission message.
  • the portable terminal sets the transfer status code of the transfer file information holding unit 820 to “transmitted” in step S1277.
  • step S1279 the portable terminal waits for a notification of completion of transmission to the file transfer destination. If there is no notification, the process of the mobile terminal leaves the file transfer application and executes another process of the mobile terminal. Then, for example, it is desirable to return to step S1279 of the file transfer application from another process according to the time sharing process, because there is no burden on the user operation or the like. Note that the process may advance to step S1287 without performing the process of waiting for the notification of completion of transmission to the file transfer destination in step S1279.
  • the mobile terminal negotiates with the file transfer server 130 in step S1283.
  • the download includes a polling method for requesting file transmission from the transfer destination mobile terminal to the file transfer server 130, a push method for sending file transmission from the file transfer server 130 to the transfer destination mobile terminal, and the like.
  • Negotiations include them.
  • the portable terminal receives a desired transfer file from the file transfer server 130 and stores it in the file DB 607 in step S1285.
  • step S1287 the portable terminal confirms the completion of the file transfer, sets the transfer status code of the transfer file information holding unit 820 to “transfer completed”, or deletes the information if the history is not saved.
  • step S1287 it is determined whether there is any transfer file information that has not been transferred in the transfer file information holding unit 820, and the process returns to step S1271.
  • the file transfer application may be run in the background without ending. In that case, when instructing the start of the file transfer application, the user may be inquired whether to end after file transfer or to run in the background.
  • exchange of file information, transfer source information, and transfer destination information by infrared communication is instantaneous, and subsequent file transfer is automatically processed by the mobile terminal. Therefore, it is possible to transfer a large-capacity file between portable terminals without a user operation without waiting for completion of file transfer at the site.
  • the configuration of the file buffer in the file transfer server is shown. Since other configurations and operations are the same as those of the first embodiment, detailed descriptions of the same configurations and operations are omitted.
  • uploading of the same file from the transfer source to the file transfer server can be omitted, the load on the transmission source mobile terminal can be reduced, and the communication throughput can be improved.
  • FIG. 13 is a diagram showing a configuration of a file buffer in the file transfer server according to the present embodiment.
  • items similar to those of the file holding unit 1010 of FIG. 1010 of FIG. 10 are similar to those of the file holding unit 1010 of FIG.
  • the transfer status code 1313 stores a file retention period 1311 corresponding to the file ID 1011.
  • a plurality of file transfer destination IDs 1312 and transfer status codes 1313 are provided corresponding to the file IDs 1011.
  • the transfer status code 1313 is set based on the transfer status table 1020 in FIG.
  • a file uploaded from a portable terminal having the same file ID and the same file transfer source ID can be downloaded to a plurality of portable terminals having different file transfer destination IDs within the file storage period 1311. It becomes. Therefore, if there is a file transfer to a portable terminal having a different file transfer destination ID within the file storage period 1311, the file transfer server can download the file to the transfer destination without requiring the file upload from the transfer source.
  • uploading of the same file from the transfer source to the file transfer server can be omitted, the load on the transmission source mobile terminal can be reduced, and the communication throughput can be improved.
  • the file transfer system according to the present embodiment is different from the first embodiment in that a file to be transferred is acquired from a file storage server or a file distribution server without being uploaded from the transfer source to the file transfer server.
  • the server transfer server in the present embodiment receives the terminal identifier of the transfer destination mobile terminal and the file identifier of the file to be transferred to the transfer destination mobile terminal from the transfer source mobile terminal. Based on the acquired file identifier, the server transfer server acquires a file to be passed from a file storage server that stores the file or a file distribution server that distributes the file. Then, the server transfer server downloads the acquired file to the transfer destination communication terminal without uploading the file from the transfer source portable terminal.
  • the load on the transmission source portable terminal is reduced and the throughput of network communication can be improved.
  • FIG. 14 is a diagram showing an outline of the configuration and operation of the file transfer system 1400 according to this embodiment.
  • the same reference numerals are assigned to the same components as those in FIG. 14
  • the identifier exchange related to the transfer file from the transfer source mobile terminal 110 to the transfer destination mobile terminal 120 is the same as that in FIG.
  • the file in the file transfer via the file transfer server 1430 by network communication, the file is not uploaded from the transmission source mobile terminal as shown in FIG.
  • the file is downloaded to the file transfer server 1430 from the file distribution server 1440 that distributes the file or the file storage server 1450 in which the file is stored in advance.
  • the file distribution server 1440 includes a server unit 1441 and a file DB 1442 that stores files to be distributed.
  • the file storage server 1450 includes a server unit 1451 and a file DB 1452 that stores files to be distributed.
  • the file storage server 1450 stores, for example, photos and videos uploaded in advance from the transmission source mobile terminal 110.
  • the server unit 1431 of the file transfer server 1430 receives only the file ID of a content file such as a photograph shown to a woman having the destination mobile terminal 120 from the source mobile terminal 110. Then, based on the file ID received from the transfer source, the file is searched from the file DB 1442 of the file distribution server 1440 and the file DB 1452 of the file storage server 1450 and downloaded to the file buffer 132. Then, the file downloaded to the file buffer 132 is further downloaded from the file transfer server 1430 to the mobile terminal 120 that is the transmission source.
  • the load on the transmission source portable terminal is reduced and the throughput of network communication can be improved.
  • the file transfer system according to the present embodiment when compared with the first embodiment, when the file information transferred by infrared communication, the transfer source, and the transfer destination information are not exchanged, It differs in that file retransfer is performed.
  • the file to be transferred can be reliably transferred to the transfer destination.
  • FIG. 15 is a flowchart showing the procedure of the file transfer application executed by the mobile terminals 110 and 120 according to the present embodiment.
  • the same steps as those in FIG. 12B of the first embodiment are denoted by the same step numbers, and the description thereof is omitted.
  • some of the same steps as in FIG. 12B are omitted.
  • step S1279 if there is no notification that the file to be transferred has been transmitted to the transfer destination portable terminal in step S1279, the portable terminal determines in step S1551 whether or not the elapsed date and time since the identifier exchange by proximity communication exceeds the threshold value ⁇ . To do. If it exceeds, it is determined that the file transfer has failed. In step S1553, the portable terminal does not transmit the transfer status code 825 of the transfer file information holding unit 820, returns to step S1273, and uploads the file again.
  • the elapsed date and time exceeds the threshold ⁇ because, for example, when the upload from the transmission source has not been performed, when the date and time has elapsed since the upload and the file is deleted from the file transfer server file buffer, the transmission destination is downloaded. There may not be. In any case, however, there is no file in the file buffer of the file transfer server, and the file is retried after re-uploading.
  • the threshold ⁇ is set to a date and time that meets the conditions. If the file storage period is long and the file is still in the file buffer of the file transfer server, the transfer destination is called for download.
  • the file to be transferred can be reliably transferred to the transfer destination.
  • the file transfer system according to the present embodiment performs file transfer via a file transfer server when file transfer is not possible by proximity communication such as infrared communication or non-contact communication. It is different.
  • the present embodiment it is possible to improve the throughput of network communication by eliminating the waste of network transfer using a file transfer server for the capacity transfer that can be performed in a short time by proximity communication such as infrared communication. it can.
  • FIG. 16 is a flowchart showing the procedure of the file transfer application executed by the mobile terminals 110 and 120 according to this embodiment.
  • the same steps as those in FIG. 12B of the first embodiment are denoted by the same step numbers, and description thereof is omitted.
  • some of the same steps as in FIG. 12B are omitted.
  • the portable terminal After exchanging the identifier of the transfer file by infrared communication, the portable terminal determines whether or not the file to be transferred is transferred by infrared communication in step S1651.
  • the length of time required for the transfer can be considered based on the file capacity and the transfer speed. Alternatively, not only the time required for the transfer but also the length of time allowed by the user is taken into consideration. Alternatively, there is a case where at least one of the mobile terminals is out of the service area and the file needs to be transferred on the spot even if it takes a little time. Alternatively, the file format may not be compatible with infrared communication. Note that the conditions for determining whether or not to transfer a file by infrared communication are not limited to these.
  • the portable terminal proceeds to step S1263, and thereafter executes the file transfer via the file transfer server by the network communication of the present embodiment.
  • step S1655 the portable terminal determines whether or not the file transfer process by infrared communication is completed. If the file transfer process by infrared communication is completed, the portable terminal displays transfer completion and notifies the user in step S1657. If the file transfer process by infrared communication is not completed, the portable terminal displays a transfer error in step S1659 to notify the user, and proceeds to step S1263, via the file transfer server by network communication of this embodiment. Perform file transfer.
  • the present embodiment it is possible to improve the throughput of network communication by eliminating the waste of network transfer using a file transfer server for the capacity transfer that can be performed in a short time by proximity communication such as infrared communication. it can.
  • the file transfer system according to this embodiment differs from the first to fifth embodiments in that the terminal identifiers set by the transfer source portable terminal and the transfer destination portable terminal are different, and the transfer source portable terminal and the transfer destination portable terminal are different.
  • the difference is that the terminal identifier shared by the terminal is at least one. According to this embodiment, since there are few identifiers to share, the communication amount by infrared communication can be reduced.
  • FIG. 17 is a sequence diagram showing an operation procedure of the file transfer system according to this embodiment.
  • FIG. 17 shows only the operation procedure for sharing an identifier by infrared communication.
  • the operation procedure of the other file transfer system is the same as that of FIG. Also, in FIG. 17, the same steps as those in FIG.
  • step S1723 the transfer source mobile terminal 110 sets a file ID, a transfer destination ID, and a transfer source ID.
  • the file ID and either the transfer destination ID or the transfer source ID are sent from the transfer source mobile terminal 110 to the transmission destination mobile terminal 120.
  • the destination mobile terminal 120 can confirm that the file to be transferred is a file for the terminal itself.
  • step S1733 the transfer-source mobile terminal 110 sets only the file ID.
  • step S1737 the transfer source portable terminal 120 sets the transfer source ID and the transfer destination ID.
  • step S1739 the file ID is transmitted from the transfer source portable terminal 110 to the transmission destination portable terminal 120, and either the transfer destination ID or the transfer source ID is transferred from the transfer destination portable terminal 120 to the transmission source portable terminal 110. Either one is sent. With this information, the transmission destination portable terminal 120 can confirm that the file to be transferred is a file for the terminal itself.
  • the example shown in FIG. 17 is an example, and as long as the transfer source portable terminal and the transfer destination portable terminal share either one of the file ID and the transfer destination ID or the transfer source ID, it is accurate. File transfer is possible.
  • the terminal identifier shared by the transfer source mobile terminal and the transfer destination mobile terminal is at least one is shown.
  • the transfer destination ID and the transfer source ID can be shared, In that case, the transfer source portable terminal and the transfer destination portable terminal share the file ID, the transfer destination ID, and the transfer source ID as in the first embodiment.
  • the file transfer system according to the present embodiment manages file communication, not the terminal identifier set for the communication terminal in the file transfer system, but the file transfer system. The difference is that the user identifier set for the user is used.
  • files that can be transferred among files of the communication terminal are selected based on the user identifier.
  • the file can be transferred in the same manner as the processing using the terminal identifier. Since other configurations and operations are the same as those of the first to fifth embodiments, detailed descriptions of the same configurations and operations are omitted.
  • a file identifier and a transfer source user identifier are passed from the transfer source mobile terminal to the transfer destination mobile terminal as a voucher for the file.
  • the transfer source user identifier is an identifier assigned to the transfer source user from the file transfer system, an identifier registered by the user in the file transfer system, or set by the transfer source user during proximity communication. Any identifier may be used.
  • the present embodiment it is possible to improve the throughput of network communication by eliminating the waste of performing network communication using a file transfer server for file transfer of a capacity that can be performed in a short time by near field communication such as infrared communication. .
  • the present invention may be applied to a system composed of a plurality of devices, or may be applied to a single device. Furthermore, the present invention can also be applied to a case where a control program that realizes the functions of the embodiments is supplied directly or remotely to a system or apparatus. Therefore, in order to realize the functions of the present invention with a computer, a control program installed in the computer, a medium storing the control program, and a WWW (World Wide Web) server that downloads the control program are also included in the scope of the present invention. include. In particular, at least non-transitory computer readable media are within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention porte sur un système de transfert de fichier permettant de transférer un fichier entre des terminaux de communication même si les terminaux de communication sont en dehors de zones de service, et de transférer un fichier de grande capacité entre les terminaux de communication sans attendre l'achèvement du transfert de fichier sur place. Ce système de transfert de fichier amène un terminal de communication source de transfert et un terminal de communication destination de transfert à partager, à l'aide d'une communication de proximité, un identificateur de source de transfert servant à identifier une source de transfert et l'identificateur de fichier d'un fichier à transférer, et transfère un fichier identifié par l'identificateur de source de transfert et l'identificateur de fichier du terminal de communication source de transfert au terminal de communication destination de transfert par l'intermédiaire d'un serveur.
PCT/JP2014/052429 2013-02-05 2014-02-03 Système de transfert de fichier, procédé de transfert de fichier, terminal de communication, son procédé de commande, et programme d'application WO2014123082A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
JP2013-019987 2013-02-05
JP2013019987A JP5486706B1 (ja) 2013-02-05 2013-02-05 ファイル転送システム、ファイル転送方法、通信端末およびその制御方法と制御プログラム、および、アプリケーションプログラム
JP2013249555A JP6002119B2 (ja) 2013-12-02 2013-12-02 ファイル転送システム、ファイル転送方法、サーバおよびその制御方法と制御プログラム、通信端末およびその制御方法と制御プログラム、および、アプリケーションプログラム
JP2013-249555 2013-12-02

Publications (1)

Publication Number Publication Date
WO2014123082A1 true WO2014123082A1 (fr) 2014-08-14

Family

ID=51299677

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/052429 WO2014123082A1 (fr) 2013-02-05 2014-02-03 Système de transfert de fichier, procédé de transfert de fichier, terminal de communication, son procédé de commande, et programme d'application

Country Status (1)

Country Link
WO (1) WO2014123082A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003179840A (ja) * 2001-12-10 2003-06-27 Nikon Corp 電子カメラ、電子機器、画像伝送システムおよび画像伝送方法
JP2006178527A (ja) * 2004-12-20 2006-07-06 Sharp Corp 通信端末装置および通信システム
JP2010073014A (ja) * 2008-09-19 2010-04-02 Canon Inc 情報処理装置およびその制御方法およびそのプログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003179840A (ja) * 2001-12-10 2003-06-27 Nikon Corp 電子カメラ、電子機器、画像伝送システムおよび画像伝送方法
JP2006178527A (ja) * 2004-12-20 2006-07-06 Sharp Corp 通信端末装置および通信システム
JP2010073014A (ja) * 2008-09-19 2010-04-02 Canon Inc 情報処理装置およびその制御方法およびそのプログラム

Similar Documents

Publication Publication Date Title
JP6014922B2 (ja) グループ通信のための方法およびシステム、グループサーバ並びにグループメンバーデバイス
JP6476672B2 (ja) 通信端末、情報処理方法およびプログラム
US8810839B2 (en) Information processing apparatus for transferring image data, server apparatus for receiving transferred image data, and control methods and storage media therefor
KR101332813B1 (ko) 무선 통신 장치 및 무선 통신 장치의 무선 접속 채널의 형성 방법
WO2017150015A1 (fr) Système d'impression et procédé de commande associé
TWI258944B (en) Data distribution device
JP6002119B2 (ja) ファイル転送システム、ファイル転送方法、サーバおよびその制御方法と制御プログラム、通信端末およびその制御方法と制御プログラム、および、アプリケーションプログラム
JP5171392B2 (ja) 通信システム、情報保有装置、および管理装置
US11018987B2 (en) Resource reservation system, setting method, and non-transitory computer readable storage medium
US20070050829A1 (en) Data transmitter and receiver, data transmitting/receiving system and method, and terminal device
JP5867236B2 (ja) データ収集方法、移動端末およびデータ保存装置
JP5486706B1 (ja) ファイル転送システム、ファイル転送方法、通信端末およびその制御方法と制御プログラム、および、アプリケーションプログラム
WO2014123082A1 (fr) Système de transfert de fichier, procédé de transfert de fichier, terminal de communication, son procédé de commande, et programme d'application
CN102638623A (zh) 基于二维图像在电子设备之间传递数据的方法及系统
JP4445302B2 (ja) 無線端末装置、サービス検索方法
JP2020087178A (ja) 情報処理装置、情報処理システム、情報処理方法及びプログラム
JP6922336B2 (ja) 情報処理装置、情報処理方法、情報処理プログラムおよび情報処理システム
CN111642031B (zh) 多设备间的连接方法及电子设备、计算机可读存储介质
CN106413123B (zh) 数据传输方法及装置
JP2006120065A (ja) 携帯電話端末、サーバ、データ共有システムおよび携帯電話端末のデータ共有方法
JP2014203201A (ja) 通信装置およびその制御方法、プログラム
JP2006268587A (ja) 情報処理装置
JP6048262B2 (ja) 通信装置
JP2019097083A (ja) 情報提供システム、プログラム、情報提供方法
US11196831B2 (en) Communication apparatus, communication method, and storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14749050

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14749050

Country of ref document: EP

Kind code of ref document: A1