JP2013161415A - Data exchange server and data exchange method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To specify the sending candidate of the exchange data of each user terminal without increasing the processing load of a data exchange server.SOLUTION: A data exchange method includes: processes (S102, S104, S106) of storing the reception time of a login request from user terminals (10A to 10C); a process (S108) of, when the search request of the sending candidate of exchange data is received from the user terminal (10A), searching the other user terminal (10) whose stored reception time of the login request exists within a predetermined time from the reception time of the above mentioned search request; and a process (S109) of notifying the user terminal (10A) of the searched other user terminal (10) as the sending candidate of the exchange data of the user terminal (10A).

Description

  The present invention relates to a data exchange server, a user terminal, and a data exchange method for exchanging data between a plurality of user terminals.

  2. Description of the Related Art In recent years, a data exchange system is known that electronically exchanges data such as user names and contact information between user terminals so as to expand and facilitate communication between users. In such a data exchange system, a data exchange server manages exchange data (for example, the name and contact information of a user of one user terminal) that one user terminal desires to exchange with another user terminal. Other user terminals that are candidates for sending exchange data of the user terminal are identified. For example, the data exchange server identifies other user terminals that are located in the same area or other user terminals that have registered the exchange data in the data exchange server within the same time period as candidates for exchange data for one user terminal. It is known to do (for example, patent document 1).

JP 2011-186711 A

  In the data exchange system as described above, when specifying other user terminals that registered the exchange data in the data exchange server within the same time as the exchange data candidate of each user terminal, for example, the data exchange server manages the timer. Can also be considered. Specifically, the data exchange server starts a timer each time exchange data is registered by each user terminal, and exchanges each user terminal with another user terminal that has registered the exchange data before the timer expires. Identifies as a candidate for sending data.

  However, each time the exchange data is registered in the data exchange server by each user terminal, when the timer management is performed and the registered exchange data candidate is specified, the processing load of the data exchange server accompanying the timer management increases. There was a problem.

  The present invention has been made in view of such problems, and provides a data exchange server and a data exchange method capable of specifying exchange data transmission candidates of each user terminal without increasing the processing load of the data exchange server. The purpose is to do.

  A data exchange server according to a first aspect of the present invention includes a first storage unit that stores reception times of login requests from a plurality of user terminals, and sending exchange data from one user terminal among the plurality of user terminals. When a candidate search request is received, search for another user terminal whose reception time of the login request stored in the first storage unit is between the reception time of the search request and a time before a predetermined time. A search unit; and a notification unit that notifies the other user terminal searched by the search unit to the one user terminal as a transmission candidate of exchange data of the one user terminal.

  According to this configuration, when a search request for a candidate for sending exchange data is received from one user terminal, the data exchange server receives the login request stored in the first storage unit as the reception time of the search request. Another user terminal is searched between the time and a time before a predetermined time, and the other user terminal found is notified to one user terminal as an exchange data transmission candidate of the one user terminal. For this reason, the data exchange server does not need to perform timer management every time a login request is received from each user terminal, and specifies exchange data transmission candidates for each user terminal without applying the processing load of the data exchange server. it can.

  A data exchange method according to a second aspect of the present invention is a data exchange method in a data exchange server that manages data exchange between a plurality of user terminals, and stores reception times of login requests from the plurality of user terminals. And when a search request for exchange data transmission candidates is received from one user terminal of the plurality of user terminals, the reception time of the stored login request is a predetermined time before the search request reception time. A step of searching for another user terminal up to the time of time, and a step of notifying the one user terminal of the searched other user terminal as a transmission candidate of the exchange data of the one user terminal. It is characterized by having.

  ADVANTAGE OF THE INVENTION According to this invention, the data exchange server and data exchange method which can identify the transmission candidate of the exchange data of each user terminal, without increasing the processing load of a data exchange server can be provided.

1 is a schematic configuration diagram of a data exchange system according to a first embodiment. It is a detailed functional block diagram of the data exchange server which concerns on 1st Embodiment. It is a figure which shows an example of the memory content of the registration information storage part which concerns on 1st Embodiment. It is a figure which shows an example of the memory content of the exchange state memory | storage part which concerns on 1st Embodiment. It is a sequence diagram which shows the search operation | movement of the data exchange system which concerns on 1st Embodiment. It is a flowchart which shows the search operation | movement of the data exchange server which concerns on 1st Embodiment. It is a sequence diagram which shows the exchange operation | movement of the data exchange system which concerns on 1st Embodiment. It is a schematic block diagram of the data exchange system which concerns on the example of a change. It is a sequence diagram which shows the exchange operation | movement of the data exchange system which concerns on the example of a change.

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

(First embodiment)
FIG. 1 is a schematic configuration diagram of a data exchange system according to the first embodiment. As shown in FIG. 1, the data exchange system 1 includes user terminals 10 </ b> A to 10 </ b> C, and data exchange servers 40 that communicate with the user terminals 10 </ b> A to 10 </ b> C via the radio base station 20 and the core network 30.

  In the data exchange system 1 shown in FIG. 1, the data exchange server 40 manages data exchange between the user terminals 10A to 10C. Here, the exchange data exchanged between the user terminals 10A to 10C includes, for example, telephone numbers and email addresses of the user terminals 10A to 10C, names, addresses, titles of the users of the user terminals 10A to 10C, and other information of the user. This includes, but is not limited to, e-mail addresses, business card information such as the social network service (SNS) -ID of the user, image information such as photos and avatars, and profile information such as hobbies and birthplaces. .

  Further, the data exchange system 1 is not limited to the configuration shown in FIG. For example, in the data exchange system 1, an authentication node, an interface node, etc. (not shown) may be provided between the core network 30 and the data exchange server 40. Further, the number of user terminals 10A to 10C and the number of radio base stations 20 are not limited to the numbers shown in FIG. Hereinafter, the user terminals 10 </ b> A to 10 </ b> C are collectively referred to as the user terminal 10 when not distinguished.

  Next, a functional configuration of the data exchange system according to the first embodiment will be described. Note that each device (specifically, the data exchange server 40, the user terminal 10 and the like) constituting the data exchange system 1 includes hardware including a communication interface, a processor, a memory, a transmission / reception circuit, a display, operation keys, a touch panel, and the like. The memory stores software modules that are executed by the processor. A functional configuration to be described later may be realized by the hardware described above, may be realized by a software module executed by a processor, or may be realized by a combination of both.

  FIG. 2 is a detailed functional configuration diagram of the data exchange server 40 according to the first embodiment. As shown in FIG. 2, the data exchange server 40 includes a transmission / reception unit 401 (notification unit, transmission unit), a registration processing unit 402, a registration information storage unit 403 (first storage unit), a search processing unit 404 (search unit), An exchange management unit 405, an exchange state storage unit 406 (second storage unit), and an exchange data storage unit 407 are provided.

  The transmission / reception unit 401 transmits / receives information to / from the user terminal 10 via the radio base station 20 and the core network 30. Specifically, the transmission / reception unit 401 receives a login request, a search request, a status acquisition request, exchange data, and the like described later from the user terminal 10. In addition, the transmission / reception unit 401 transmits a transmission candidate list input from a search processing unit 404 described later, status information input from an exchange management unit 405 described later, exchange data, and the like to the user terminal 10. The transmission / reception unit 401 transmits and receives the information using, for example, an HTTP protocol.

  When the transmission / reception unit 401 receives a login request from the user terminal 10, the registration processing unit 402 registers registration information regarding the user terminal 10 in the registration information storage unit 403. Here, the login request is a request for login to the data exchange server 40. The login request may include user identification information of the user terminal 10 (for example, user ID), location information (for example, latitude and longitude, information acquired from GPS, in-zone cell information, etc.), secret words, and the like. .

  Specifically, the registration processing unit 402 associates the user identification information of the user terminal 10 with the reception time of the login request received from the user terminal 10 (hereinafter referred to as login request reception time) in the registration information storage unit 403. sign up. Further, when the login request received by the transmission / reception unit 401 includes a password or position information, the registration processing unit 402 associates the position information and the password in addition to the user identification information of the user terminal 10 and the login request reception time. Registration may be performed in the registration information storage unit 403.

  FIG. 3 is a diagram illustrating an example of a registration information storage unit according to the first embodiment. For example, when the login request from the user terminal 10A is received by the transmission / reception unit 401, the registration processing unit 402, as shown in FIG. 3, the user identification information “#A” of the user terminal 10A and the location information of the user terminal 10A “E137, N42 (longitude 137 degrees, latitude 42 degrees)”, login request reception time “09:50 (9:50)” from the user terminal 10A, and the password “docomo” of the user terminal 10 are stored in association with each other. Registered in the unit 403. Note that the notation shown in FIG. 3 is merely an example. In FIG. 3, the login request reception time is registered in units of hours and minutes, but is not limited to this, and may be registered in units of hours, minutes and seconds. In addition, the longitude and latitude of the position information are registered in degrees, but may be registered in degrees and seconds.

  Note that the registration processing unit 402 may re-register registration information related to the user terminal 10 in the registration information storage unit 403 when the transmission / reception unit 401 receives a re-login request from the user terminal 10. Here, the re-login request means that the user terminal 10 that has already logged in to the data exchange server 40 requests the login again. For example, when the position information is changed as the user terminal 10 moves. When the registration information of the user terminal 10 needs to be changed, such as when the password is changed or the password is changed, it is transmitted from the user terminal 10. When the re-login request is received by the transmission / reception unit 401, the registration processing unit 402 may update the login request reception time in the registration information storage unit 403 to the re-login request reception time. Further, the registration processing unit 402 may update such information when a password or position information is included in the re-login request.

  When the search request from the user terminal 10 is received by the transmission / reception unit 401, the search processing unit 404 refers to the registration information storage unit 403 to search for another user terminal 10 that is a candidate for sending exchange data of the user terminal 10. To do. Here, the search request is to request the data exchange server 40 to search for another user terminal 10 that is a candidate for sending exchange data of the user terminal 10. The search request may include user identification information of the user terminal 10. Further, as described above, the exchange data is the telephone number or mail address of the user terminal 10A, the user's name, and the like.

  Specifically, when the search request from the user terminal 10 is received by the transmission / reception unit 401, the search processing unit 404 uses the login request reception time stored in the registration information storage unit 403 as the reception time of the search request (hereinafter referred to as the search request reception time). Search for other user terminals 10 between the time when the search request is received and the time before a predetermined time. For example, if the search request reception time from the user terminal 10 is “10:05 (10: 5)” and the predetermined time is 30 minutes, the search processing unit 404 stores the information in the registration information storage unit 403. Search for another user terminal 10 whose login request reception time is between “09:35 (9:35)” 30 minutes before the search request reception time “10:05 (10:05)” To do.

  Further, when the search request from the user terminal 10 is received by the transmission / reception unit 401, the search processing unit 404 is based on whether or not the password of the user terminal 10 is stored in the registration information storage unit 403. Other user terminals 10 that are candidates for sending exchange data may be searched. When the password of the user terminal 10 is stored, the search processing unit 404 may search for another user terminal 10 that stores the same password as the password of the user terminal 10. On the other hand, when the password of the user terminal 10 is not stored, the search processing unit 404 may search for another user terminal 10 that does not store the password.

  For example, in FIG. 3, since the password “docomo” is stored in association with the user identification information “#A” of the user terminal 10A, the search processing unit 404 receives the search request from the user terminal 10A. Other user terminals 10 (here, user terminals 10B and 10C) in which the same password as the password “DOCOMO” is stored are searched. Further, in FIG. 3, since no secret word is stored in association with the user identification information “#D” of the user terminal 10D, the search processing unit 404 stores the secret word when a search request from the user terminal 10D is received. The other user terminal 10 (here, the user terminal 10E) that has not been searched is searched.

  The search processing unit 404 may search for another user terminal 10 located in the same area as the user terminal 10 when the search request from the user terminal 10 is received by the transmission / reception unit 401. Specifically, the search processing unit 404 calculates the distance between the user terminals 10 based on the position information of the user terminal 10 and the position information of other user terminals 10 stored in the registration information storage unit 403, and calculates Another user terminal 10 whose distance is within a predetermined distance may be searched.

  The search processing based on the login request reception time and the search request time, the search processing based on the secret word, and the search processing based on the position information may be combined in part or all. Also, these search processes may be performed in any order.

  In addition, when the transmission / reception unit 401 receives a re-search request from the user terminal 10, the search processing unit 404 may perform the search processing described above. Here, the re-search request means that the user terminal 10 that has already been searched for a transmission candidate requests a search for a transmission candidate again. For example, when the login request reception time from another user terminal 10 is later than the search request reception time from the user terminal 10, the other user terminal 10 is not searched as a transmission candidate of the user terminal 10. Therefore, the user terminal 10 makes a re-search request so that another user terminal 10 that has made a login request after the initial search request can be detected as a transmission candidate. In this case, the above-described search request reception time becomes the reception time of the re-search request, and the search processing unit 404 has another user whose login request reception time is between the reception time of the re-search request and a time before a predetermined time. The terminal 10 is searched.

  In addition, the search processing unit 404 outputs a transmission candidate list including user identification information of other user terminals 10 searched as transmission data transmission candidates of the user terminal 10 to the transmission / reception unit 401. The transmission / reception unit 401 transmits the transmission candidate list output from the search processing unit 404 to the user terminal 10.

  The exchange management unit 405, when the search processing unit 404 searches for another user terminal 10 as a candidate for sending exchange data of the user terminal 10, the user identification information of the user terminal 10 and the searched other user terminal 10 User identification information, transmission status of exchange data from the user terminal 10 with respect to the other user terminal 10 searched (here, “not yet transmitted”), from the user terminal 10 by the other user terminal 10 searched for The exchange data receiving state (here, “not received (not received)”) is associated and stored in the exchange status storage unit 406.

  FIG. 4 is a diagram illustrating an example of the exchange state storage unit 406 according to the first embodiment. For example, when the search processing unit 404 searches for user terminals 10A and 10B as transmission candidates for exchange data (hereinafter referred to as exchange data #C) of the user terminal 10C, as shown in FIG. 4, the user of the user terminal 10C In association with the identification information “#C”, the user identification information “#A” and “#B” of the user terminals 10A and 10B are associated as transmission candidates for the exchange data #C and stored in the exchange state storage unit 406. In addition, the exchange state storage unit 406 transmits, as an initial state, the transmission state “unsent (not transmitted)” of the exchange data #C from the user terminal 10C to the user terminals 10A and 10B, and the exchange data #C of the user terminals 10A and 10B. The reception state “unreceived (not received)” is associated and stored in the exchange state storage unit 406.

  When the transmission / reception unit 401 receives a status acquisition request from the user terminal 10, the exchange management unit 405 acquires a transmission state for the user terminal 10 and outputs the transmission state to the transmission / reception unit 401. Here, the status acquisition request requests acquisition of the transmission status of exchange data from another user terminal 10 to the own terminal, that is, whether or not exchange data that can be received by the own terminal exists in the data exchange server 40. It is for confirming.

  For example, when a status acquisition request is received from the user terminal 10A, the exchange management unit 405 exchanges data of the user terminals 10B and 10C including the user terminal 10A as a candidate for transmission (hereinafter referred to as exchange data #B and #C). ) Is acquired from the exchange state storage unit 406. In FIG. 4, the transmission state of the exchange data #B from the user terminal 10B to the user terminal 10A is “completed (transmitted)”, while the transmission state of the exchange data #C from the user terminal 10C to the user terminal 10A is “ "Not (not sent)". Therefore, the exchange management unit 405 outputs status information indicating that the exchange data #B from the user terminal 10B can be received to the transmission / reception unit 401. The transmission / reception unit 401 transmits the state information input from the exchange management unit 405 to the user terminal 10A.

  When the transmission / reception unit 401 receives exchange data for another user terminal 10 from the user terminal 10, the exchange management unit 405 sets the transmission status of the exchange data from the user terminal 10 to the other user terminal 10 as “completed”. (Sent) ”. For example, in FIG. 4, the transmission state of the exchange data #B from the user terminal 10B to the user terminals 10A and 10C is updated to “completed (transmitted)”.

  In addition, when the exchange data is received from the user terminal 10 by the transmission / reception unit 401, the exchange management unit 405 stores the exchange data in the exchange data storage unit 407. The exchange management unit 405 may store the exchange data in association with the data identification information (for example, business card ID) of the exchange data.

  Further, when the exchange data reception request is received by the transmission / reception unit 401, the exchange management unit 405 acquires the exchange data from the exchange data storage unit 407 and outputs the exchange data to the transmission / reception unit 401. The transmission / reception unit 401 transmits the exchange data input from the exchange management unit 405 to the user terminal 10.

  In addition, when the exchange data is transmitted to the user terminal 10 by the transmission / reception unit 401 in response to the exchange data reception request, the exchange management unit 405 sets the reception state of the user terminal 10 in the exchange state storage unit 406 to “completed (received). ) ". For example, when the exchange data #B is transmitted from the user terminal 10B to the user terminals 10A and 10C by the transmission / reception unit 401, the reception state of the exchange data #B by the user terminals 10A and 10C is as shown in FIG. Updated to “Done (Received)”.

  Next, the operation of the data exchange system according to the first embodiment will be described. Specifically, (1) a search operation for sending exchange data of each user terminal 10 (hereinafter referred to as a search operation), and (2) an exchange operation of exchange data for each user terminal 10 (hereinafter referred to as an exchange operation). Will be explained. In the following search operation and exchange operation, the communication between the user terminals 10A to 10C and the data exchange server 40 is performed using, for example, the HTTP protocol. May be used. Communication between the user terminals 10A to 10C and the data exchange server 40 may be performed via a relay node (not shown) (for example, MAPS, a node on the core network, the radio base station 20, etc.).

(1) Search Operation The search operation in the data exchange system according to the first embodiment will be described with reference to FIGS. FIG. 5 is a sequence diagram showing a search operation in the data exchange system according to the first embodiment. FIG. 6 is a flowchart showing a search operation in the data exchange server according to the first embodiment.

  As shown in FIG. 5, the user terminal 10A transmits a login request to the data exchange server 40 (step S101). Here, it is assumed that the login request from the user terminal 10A includes the user identification information of the user terminal 10A, the position information (for example, longitude and latitude) of the user terminal 10A, and a password, but the position information of the user terminal 10A. And secret words may be omitted. The user terminal 10A starts a search request limit timer (described later) triggered by transmission of a login request to the data exchange server 40.

  When the data exchange server 40 receives the login request from the user terminal 10A, the data exchange server 40 associates the user identification information of the user terminal 10A, the position information, the secret word, and the login request reception time with each other and stores them in the registration information storage unit 403 (step S102). For example, in the case illustrated in FIG. 3, user identification information “#A”, position information “E137, N42”, password “DOCOMO”, and login request reception time “09:50” of the user terminal 10A are stored in association with each other.

  Similarly, the user terminal 10B transmits a login request to the data exchange server 40 (step S103). When the data exchange server 40 receives the login request from the user terminal 10B, the data exchange server 40 associates the user identification information of the user terminal 10B, the position information, the password, and the login request reception time and stores them in the registration information storage unit 403 (step S104). For example, in the case illustrated in FIG. 3, user identification information “#B”, position information “E137, N42”, password “DOCOMO”, and login request reception time “09:55” of the user terminal 10B are stored in association with each other.

  Further, the user terminal 10C transmits a login request for requesting registration of exchange data of the user terminal 10C to the data exchange server 40 (step S105). When the data exchange server 40 receives the login request from the user terminal 10C, the data exchange server 40 associates the user identification information of the user terminal 10C, the position information, the password, and the login request reception time and stores them in the registration information storage unit 403 (step S106). For example, in the case illustrated in FIG. 3, user identification information “#C”, position information “E137, N42”, password “DOCOMO”, and login request reception time “10:00” of the user terminal 10C are stored in association with each other.

  When the search request limit timer started when the login request is transmitted expires, the user terminal 10A transmits a search request that requests the data exchange server 40 to search for transmission candidates for the exchange data #A of the user terminal 10A. (Step S107).

  When the data exchange server 40 receives the search request from the user terminal 10A, the data exchange server 40 performs a search process for the transmission candidate of the exchange data #A of the user terminal 10A (step S108). The search operation in the data exchange server 40 will be described in detail with reference to FIG. In the following, a case where a search request from the user terminal 10A is received will be described as an example. However, a similar search operation is performed when a search request from a user terminal 10 other than the user terminal 10A is received. Shall.

  As shown in FIG. 5, when the data exchange server 40 receives the search request from the user terminal 10A, the login request reception time stored in the registration information storage unit 403 is the reception time of the search request (hereinafter referred to as search request reception). Search for another user terminal 10 between the (time) and a time before a predetermined time (step S201). For example, when a search request from the user terminal 10A is received at 10: 5 and the predetermined time is set to 30 minutes, the data exchange server 40 determines that the login request reception time is “10:05 ”Is searched for the user terminal 10 between 30 minutes before the time“ 09:35 ”. In the case shown in FIG. 3, since the login request reception times of the user terminals 10B to 10E are between the search request reception time “10:05” and the time “09:35” 30 minutes before, 10B to 10E are searched.

  When the other user terminal 10 whose login request reception time is between the search request reception time from the user terminal 10A and the time before the predetermined time is not searched (step S201; No), the exchange data #A is sent. This operation ends with no candidate.

  On the other hand, when another user terminal 10 is searched for when the login request reception time is between the search request reception time from the user terminal 10A and the time before the predetermined time (step S201; Yes), the data exchange server 40 Then, it is determined whether or not the secret word of the user terminal 10A is stored in the registration information storage unit 403 (step S202). Specifically, the data exchange server 40 determines whether or not a secret word is stored in the registration information storage unit 403 in association with the user identification information “#A” of the user terminal 10A. In the case illustrated in FIG. 3, the password “docomo” is stored in association with the user identification information “#A” of the user terminal 10 </ b> A.

  When the password of the user terminal 10A is stored (step S202; Yes), the data exchange server 40 registers the same password as the password of the user terminal 10A among the other user terminals 10 searched in step S201. The user terminal 10 stored in the information storage unit 403 is searched (step S203). In the case illustrated in FIG. 3, the same secret “DOCOMO” as the secret of the user terminal 10A is stored in association with the user identification information “#B” and “#C” of the user terminals 10B and 10C. For this reason, user terminals 10B and 10C are further searched from the user terminals 10B to 10E searched in step S201.

  On the other hand, when the password of the user terminal 10A is not stored (step S202; No), the data exchange server 40 stores the password in the registration information storage unit 403 among the other user terminals 10 searched in step S201. The user terminal 10 that has not been searched is searched (step S204). In the case shown in FIG. 3, the user terminals 10D and 10E in which no secret word is stored are searched.

  When the password of the user terminal 10A is stored (step S202; Yes), and another user terminal 10 that sets the same password as the password of the user terminal 10A is searched (step S203; Yes), The data exchange server 40 searches for the user terminal 10 located within a predetermined distance from the position of the user terminal 10A among the other user terminals 10 searched in step S203 (step S205). Specifically, the data exchange server 40 calculates the distance between each user terminal 10 searched in step S203 and the user terminal 10A based on the position information stored in the registration information storage unit 403, and calculates It is determined whether the measured distance is within a predetermined distance. In the case illustrated in FIG. 3, based on the location information “E137, N42” of the user terminals 10B and 10C and the location information “E137, N42” of the user terminal 10A retrieved in step S203, the user terminals 10A and 10B and Each of the distances to 10C is calculated, and it is determined whether the calculated distances are within a predetermined distance. Here, it is assumed that the distance between the user terminal 10A and the user terminals 10B and 10C is within a predetermined distance.

  When the password of the user terminal 10A is stored (step S202; Yes) and another user terminal 10 in which the same password as the password of the user terminal 10A is stored is not searched (step S203; No), This operation ends with no exchange data #A sending candidate.

  When the password of the user terminal 10A is not stored (step S202; No) and another user terminal 10 that does not store the password is searched (step S204; Yes), the data exchange server 40 performs the step Among the other user terminals 10 searched in S204, the user terminal 10 located within a predetermined distance from the position of the user terminal 10A is searched (step S205).

  When the user terminal 10 located within a predetermined distance from the position of the user terminal 10A is searched from the user terminals 10 searched in step S203 or step S204 (step S205; Yes), the data exchange server 40 searches The registered user terminal 10 is stored in the registered information storage unit 403 as a candidate for sending the exchange data #A (step S206). In the case shown in FIG. 3, since the user terminals 10B and 10C are searched by the above-described search process, the user identification information “#B” and “#C” of the user terminals 10B and 10C are registered as the transmission candidates for the exchange data #A. It is stored in the information storage unit 403.

  On the other hand, when the user terminal 10 located within a predetermined distance from the position of the user terminal 10A is not searched from the user terminals 10 searched in step S203 or step S204 (step S205; No), the exchange data #A This operation ends as there is no transmission candidate.

  As described above, in step S108 of FIG. 5, the data exchange server 40 performs a process for searching for a candidate for exchange data #A. In FIG. 6, the search process based on the secret word (steps S202 to S204) and the search process based on the position information (step S205) may all be omitted, or only one of them may be omitted. In addition, the order of the search process based on the login request reception time (step S201), the search process based on secret words (steps S202 to S204), and the search process based on position information (step S205) is not limited to that shown in FIG. It may be replaced as appropriate.

  As described above, the data exchange server 40 notifies the user terminal 10A of the other user terminals 10 searched as candidates for exchange data #A (step S109). Specifically, the data exchange server 40 transmits a transmission candidate list including the user identification information of the searched user terminal 10 to the user terminal 10A. In the search process described above, as shown in FIG. 3, the user terminals 10B and 10C are searched as transmission candidates for the exchange data #A. Therefore, the user identification information “#B” and “#C” of the user terminals 10B and 10C are searched. Is sent to the user terminal 10A.

  Similarly, when the search request limit timer started when the login request is transmitted expires, the user terminal 10B requests the data exchange server 40 to search for a transmission candidate for the exchange data #B of the user terminal 10B. A request is transmitted (step S110). When the data exchange server 40 receives the search request from the user terminal 10B, the data exchange server 40 performs a search process for the candidate for sending the exchange data #B as described with reference to FIG. 6 (step S111). The user terminal 10B is notified (step S112). In the case illustrated in FIG. 3, the user identification information “#A” and “#C” of the user terminals 10 </ b> A and 10 </ b> C searched by the search process are stored in the registration information storage unit 403 as transmission candidates for the exchange data #B. In addition, a transmission candidate list including the user identification information “#A” and “#C” of the user terminals 10A and 10C is transmitted to the user terminal 10B.

  Further, the user terminal 10C requests the data exchange server 40 to search for the transmission candidate of the exchange data #C of the user terminal 10C when the search request limit timer started when the login request is transmitted expires. Is transmitted (step S113). When receiving the search request from the user terminal 10C, the data exchange server 40 performs a search process for the candidate for sending the exchange data #C as described with reference to FIG. 6 (step S114). The user terminal 10C is notified (step S115). In the case illustrated in FIG. 3, user identification information “#A” and “#B” of the user terminals 10 </ b> A and 10 </ b> B searched by the search process are stored in the registration information storage unit 403 as transmission candidates for the exchange data #C. In addition, a transmission candidate list including the user identification information “#A” and “#B” of the user terminals 10A and 10B is transmitted to the user terminal 10C.

  As described above, according to the search operation in the data exchange system according to the first embodiment, when the data exchange server 40 receives a search request for a candidate for exchange data #A from the user terminal 10A, The user terminals 10B and 10C in which the login request reception time stored in the registration information storage unit 403 is between the search request reception time and the time before the predetermined time are searched, and the searched user terminals 10B and 10C are replaced with the exchange data #. The user terminal 10A is notified as a sending candidate of A. For this reason, the data exchange server 40 does not need to perform timer management every time a login request from each user terminal 10 is received, and the exchange data of each user terminal 10 is not subject to the processing load of the data exchange server 40. Can identify sending candidates.

  Further, according to the search operation in the data exchange system according to the first embodiment, when the data exchange server 40 receives a search request for a candidate for sending exchange data #A from the user terminal 10A, the user terminal 10A Since the user terminal 10 in which the same secret word is set as the candidate for sending the exchange data #A is searched, the search accuracy of the desired sending candidate can be improved.

  Also, according to the search operation in the data exchange system according to the first embodiment, the search process based on the location information with the highest processing load is performed after narrowing down the transmission candidates using the login request reception time and the secret word. The processing load due to the search process in the data exchange server can be reduced.

(2) Exchange Operation Next, an exchange operation in the data exchange system according to the first embodiment will be described with reference to FIG. FIG. 7 is a sequence diagram showing an exchange operation in the data exchange system according to the first embodiment. In FIG. 7, it is assumed that the user terminals 10 </ b> A to 10 </ b> C perform the sending candidate search operation described with reference to FIGS. 5 and 6. That is, each of the user terminals 10A to 10C has the above-described sending candidate list. In the following, it is assumed that user terminals 10A to 10C are candidates for sending exchange data #A to #C as shown in FIG.

  As illustrated in FIG. 7, the user terminal 10A transmits a status acquisition request to the data exchange server 40 (step S301). As described above, the status acquisition request requests acquisition of the transmission status of the exchange data #B and #C from the user terminals 10B and 10C to the user terminal 10A, that is, the exchange data # that can be received by the user terminal 10A. This is for confirming whether B and #C exist in the data exchange server 40. Note that the user terminal 10A periodically makes a status acquisition request at a predetermined time interval T, for example, triggered by reception of the sending candidate list.

  In response to the status acquisition request from the user terminal 10A, the data exchange server 40 acquires the transmission status of the exchange data #B and #C from the user terminals 10B and 10C to the user terminal 10A from the exchange status storage unit 406 (step S302).

  The data exchange server 40 transmits status information indicating the transmission status of the exchange data #B and #C to the user terminal 10A acquired from the exchange status storage unit 406 to the user terminal 10A (step S303). Here, since exchange data #B and #C for user terminal 10A are not transmitted to data exchange server 40, status information indicating that there is no exchange data that can be received by user terminal 10A is transmitted to user terminal 10A. .

  The user terminal 10A selects the user terminal 10B as the destination of the exchange data #A from the sending candidate list, and transmits the exchange data #A for the selected user terminal 10B to the data exchange server 40 (step S304). Note that the user terminal 10A may display the sending candidate list on the display screen and allow the user to select the user terminal 10 that is the sending destination. Alternatively, the user terminal 10A may select all the user terminals 10 included in the transmission candidate list as the transmission destinations.

  Upon receiving the exchange data #A for the user terminal 10B, the data exchange server 40 updates the transmission state of the exchange data #A for the user terminal 10B in the exchange state storage unit 406 to “completed (transmitted)” (step S305). . Specifically, as shown in FIG. 4, the data exchange server 40 transmits the transmission status associated with the user identification information “#B” of the user terminal 10 </ b> B as a candidate for sending the exchange data #A in the exchange status storage unit 406. Is updated to “completed (sent)”.

  Similarly to step S301, the user terminal 10B transmits a status acquisition request to the data exchange server 40 at a predetermined time interval T (step S306). Similarly to step S302, the data exchange server 40 acquires the transmission state of the exchange data #A and #C from the user terminals 10A and 10C to the user terminal 10B from the exchange state storage unit 406 (step S307). Here, since the transmission state of the exchange data #A to the user terminal 10B is updated to “completed (transmitted)”, the state information indicating that the exchange data #A from the user terminal 10A can be received is the user. It is transmitted to the terminal 10B (step S308).

  Similarly to steps S301 to S303, the user terminal 10C performs state acquisition processing (steps S309 to S311).

  The user terminal 10B transmits a reception request for exchange data #A to the data exchange server 40 based on the status information received in step S308 (step S312). Note that the user terminal 10B displays a selection screen as to whether or not to receive the exchange data #A from the user terminal 10A based on the status information received in step S308, and receives a reception instruction from the user. A reception request for exchange data #A may be transmitted.

  The data exchange server 40 acquires the exchange data #A from the exchange data storage unit 407 in response to the reception request from the user terminal 10B, and transmits it to the user terminal 10B (step S313).

  The data exchange server 40 updates the reception state of the exchange data #A for the user terminal 10B in the exchange state storage unit 406 to “completed (received)” (step S314). Specifically, as shown in FIG. 4, the data exchange server 40 receives the reception status associated with the user identification information “#B” of the user terminal 10B as a candidate for sending the exchange data #A in the exchange status storage unit 406. Is updated to “completed (received)”.

  Similarly to step S304, the user terminal 10B selects the user terminal 10A as the destination of the exchange data #B from the transmission candidate list, and transmits the exchange data #B for the selected user terminal 10A to the data exchange server 40 ( Step S315).

  Similarly to step S305, when receiving the exchange data #B for the user terminal 10A, the data exchange server 40 sets the transmission state of the exchange data #B for the user terminal 10A in the exchange state storage unit 406 to “completed (transmitted)”. Update (step S316). Specifically, as shown in FIG. 4, the data exchange server 40 transmits the transmission status associated with the user identification information “#A” of the user terminal 10 </ b> A as a candidate for sending the exchange data #B in the exchange status storage unit 406. Is updated to “completed (sent)”.

  After a predetermined time has elapsed from the status acquisition request in step S301, the user terminal 10A transmits the status acquisition request to the data exchange server 40 again (step S317). Similarly to step S302, the data exchange server 40 acquires the transmission state of the exchange data #B and #C from the user terminals 10B and 10C to the user terminal 10A from the exchange state storage unit 406 (step S318). Here, since the transmission state of the exchange data #B to the user terminal 10A has been updated to “completed (transmitted)”, the status information indicating that the exchange data #B from the user terminal 10B can be received is the user. It is transmitted to the terminal 10A (step S319).

  The user terminal 10A transmits a reception request for exchange data #B to the data exchange server 40 based on the status information received in step S319 (step S320). The data exchange server 40 acquires the exchange data #B from the exchange data storage unit 407 in response to the reception request from the user terminal 10A, and transmits it to the user terminal 10A (step S321).

  The data exchange server 40 updates the reception state of the exchange data #B for the user terminal 10A in the exchange state storage unit 406 to “completed (received)” (step S322). Specifically, as shown in FIG. 4, the data exchange server 40 receives the reception status associated with the user identification information “#A” of the user terminal 10A as a candidate for sending the exchange data #B in the exchange status storage unit 406. Is updated to “completed (received)”.

  As described above, according to the exchange operation by the data exchange system according to the first embodiment, the data exchange server 40 changes the transmission state of the exchange data #A from the user terminal 10A to the user terminals 10B and 10C that are transmission candidates. I manage. Therefore, whether or not there is exchange data #A that can be received by the user terminals 10B and 10C by transmitting the status acquisition request to the data exchange server 40 by the user terminals 10B and 10C that are candidates for sending the exchange data #A. Can be easily confirmed.

  Further, according to the exchange operation by the data exchange system according to the first embodiment, the user terminal 10A can select a desired user terminal 10 (for example, a user) among the user terminals 10B and 10C searched by the search operation described above. Exchange data can only be sent to the terminal 10B). For this reason, it is possible to prevent the exchange data from being sent to the unintended user terminal 10.

  Further, according to the exchange operation by the data exchange system according to the first embodiment, the user terminals 10B and 10C that are candidates for sending the exchange data #A make a reception request for the exchange data #A and then exchange data #A. A is received. For this reason, even if the transmission state of the exchange data #A with respect to the user terminals 10B and 10C is “completed (transmitted)”, the user terminals 10B and 10C may exchange the exchange data #A if they do not want to receive the exchange data #A. There is no need to receive data #A. Therefore, for example, even when the malicious user terminal 10A sends the exchange data #A to a large number of user terminals 10, the exchange data #A from the malicious user terminal 10A is prevented from being received unnecessarily. can do.

(Example of change)
A modified example of the data exchange system 1 according to the first embodiment will be described focusing on differences from the first embodiment. The data exchange system 2 according to the modification is different from the first embodiment in that a short message server (SMS) 50 is used in the exchange operation.

  FIG. 8 is a schematic configuration diagram of a data exchange system according to a modified example. As shown in FIG. 8, in the data exchange system 2 according to the modification, an SMS 50 is connected to the core network 30. The SMS 50 transmits / receives information to / from the data exchange server 40 via the core network 30. Further, the SMS 50 transmits a short message to the user terminal 10 via the radio base station 20. Note that communication between the SMS 50 and the data exchange server 40 or the user terminal 10 may be performed via a node (not shown).

  FIG. 9 is a sequence diagram showing an exchange operation in the data exchange system according to the modified example. In the exchange operation according to the first embodiment shown in FIG. 7, the user terminals 10 </ b> A to 10 </ b> C have been described as performing state acquisition processing on the data exchange server 40 at a predetermined time interval T. As shown in FIG. 9, in the exchange operation according to the modified example, the user terminals 10 </ b> A to 10 </ b> C perform the state acquisition process for the data exchange server 40 in response to the notification from the SMS 50, and the first embodiment. Different.

  Steps S401 and S402 in FIG. 9 are the same as steps S304 and S305 in FIG. When data exchange server 40 receives exchange data #A from user terminal 10A for user terminal 10B, data exchange server 40 transmits a short message (SM) transmission request to user terminal 10B to SMS 50 (step S403). Here, the SM transmission request is a request to the SMS 50 to transmit a short message (SM) requesting transmission of a status acquisition request.

  In response to the SM transmission request from the data exchange server 40 to the user terminal 10B, the SMS 50 transmits a short message (SM) requesting transmission of a status acquisition request to the user terminal 10B (step S404).

  In response to the short message from the SMS 50, the user terminal 10B transmits a status acquisition request to the data exchange server 40 (step S405). Steps S406 to S412 are the same as steps S306 to S316 in FIG.

  When the exchange data #B is received from the user terminal 10B for the user terminal 10A, the data exchange server 40 transmits a short message (SM) transmission request for the user terminal 10A to the SMS 50 (step S413). In response to the SM transmission request from the data exchange server 40 to the user terminal 10A, the SMS 50 transmits a short message (SM) requesting the user terminal 10A to transmit a status acquisition request (step S414).

  In response to the short message from the SMS 50, the user terminal 10A transmits a status acquisition request to the data exchange server 40 (step S415). Steps S416 to S419 are the same as steps S317 to S322 in FIG.

  As described above, according to the exchange operation according to the modified example, when the exchange data #A for the user terminal 10B is received by the data exchange server 40, the SMS 50 requests the user terminal 10B to transmit a status acquisition request. A short message is sent. For this reason, the user terminal 10B does not need to make a status acquisition request to the data exchange server 40 at the predetermined time interval T. As a result, the data exchange server 40 does not need to perform a state acquisition process at a predetermined time interval T from many user terminals 10 and can reduce the processing load.

  In step S403 in FIG. 9, the SMS 50 transmits a short message requesting the user terminal 10B to transmit a status acquisition request, but the user terminal 10B can receive the exchange data #A from the user terminal 10A. A short message for notifying may be transmitted. In such a case, the user terminal 10B that has received the short message from the SMS 50 may omit the state acquisition process in steps S407 and S408 and transmit a reception request for the exchange data #A to the data exchange server 40. .

  Although the present invention has been described in detail using the above-described embodiments, it will be apparent to those skilled in the art that the present invention is not limited to the embodiments described herein.

  For example, in the above-described embodiment, the data exchange server 40 includes the three storage units of the registration information storage unit 403, the exchange information storage unit 406, and the exchange data storage unit 407, but the configuration of the storage unit is not limited thereto. There is nothing to be done, and these may be composed of one or a plurality of storage units.

  The present invention can be implemented as a modified and updated mode without departing from the spirit and scope of the present invention defined by the description of the scope of claims. Therefore, the description of the present specification is for illustrative purposes and does not have any limiting meaning to the present invention.

DESCRIPTION OF SYMBOLS 1 ... Data exchange system 10 ... User terminal 20 ... Wireless base station 30 ... Core network 40 ... Data exchange server 50 ... SMS
401 ... transmission / reception unit 402 ... registration processing unit 403 ... registration information storage unit 404 ... search processing unit 405 ... exchange management unit 406 ... exchange state storage unit 407 ... exchange data storage unit 2 ... data exchange system

Claims (8)

A first storage unit for storing reception times of login requests from a plurality of user terminals;
When a search request for exchange data transmission candidates is received from one of the plurality of user terminals, the reception time of the login request stored in the first storage unit is determined from the reception time of the search request. A search unit for searching for other user terminals between the time before a predetermined time;
A notification unit for notifying the one user terminal of the other user terminal searched by the search unit as a candidate for sending exchange data of the one user terminal;
A data exchange server comprising: The first storage unit, when a password is included in the login requests from the plurality of user terminals, stores the password along with a reception time of the login request,
When the password of the one user terminal is stored in the first storage unit, the search unit searches for another user terminal in which the same password as the password is stored in the first storage unit. The data exchange server according to claim 1, wherein:   The search unit searches for another user terminal in which no secret word is stored in the first storage unit when the secret word of the one user terminal is not stored in the first storage unit. Item 3. The data exchange server according to Item 2.   The data exchange server according to any one of claims 1 to 3, wherein the search unit searches for another user terminal located within a predetermined distance from the position of the one user terminal. A second storage unit that stores a transmission state of exchange data from the one user terminal with respect to the other user terminal searched by the search unit;
The said notification part notifies the said transmission state memorize | stored in the said 2nd memory | storage part to the said other user terminal, when the status acquisition request from the said other user terminal is received. The data exchange server according to claim 4.   When exchange data from the one user terminal for the other user terminal is received, an update unit is further provided for updating the transmission state stored in the second storage unit to transmitted. The data exchange server according to claim 5.   When the transmission state stored in the storage unit is updated to transmitted, the transmission unit further includes a transmission unit that transmits a request message for requesting transmission of the short message to the other user terminal to the short message server. The data exchange server according to claim 6. A data exchange method in a data exchange server for managing data exchange between a plurality of user terminals,
Storing login request reception times from the plurality of user terminals;
When a search request for exchange data transmission candidates is received from one user terminal among the plurality of user terminals, the stored reception time of the login request is from a reception time of the search request to a time before a predetermined time. Searching for other user terminals in between,
Notifying the other user terminal of the one user terminal as a candidate for sending exchange data of the one user terminal;
A data exchange method characterized by comprising:

Images