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

Description

  The present invention relates to a data exchange server 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, a data exchange server manages exchange data transmitted from each user terminal. Since the exchange data from each user terminal is sequentially registered in the data exchange server, it is assumed that the memory capacity of the data exchange server is insufficient due to the exchange data stored in the data exchange server and its management information.

  In order to prevent such a shortage of memory capacity, the data exchange server periodically deletes accumulated exchange data and its management information. Specifically, the data exchange server deletes exchange data for another user terminal from the one user terminal when a predetermined time elapses after the one user terminal logs into the data exchange server. For this reason, even if another user terminal tries to acquire the exchange data from the one user terminal from the data exchange server, there is a problem that the exchange data has already been deleted and cannot be obtained. .

  The present invention has been made in view of such a problem, and when the other user terminal tries to acquire the exchange data for the other user terminal from the one user terminal from the data exchange server, the exchange data An object of the present invention is to provide a data exchange server and a data exchange method that can prevent a situation in which data has already been deleted.

  The data exchange server according to the first aspect of the present invention includes a receiving unit that receives login requests from a plurality of user terminals, and exchange data from one user terminal of the plurality of user terminals to another user terminal. Based on the elapsed time from the reception time of the login request from the other user terminal when a predetermined time has elapsed since the reception time of the login request from the one user terminal and the exchange data storage unit to be stored A determination unit that determines whether or not the other user terminal may acquire the exchange data from the one user terminal; and the other user terminal performs the exchange from the one user terminal. And a deletion unit that deletes the exchange data from the one user terminal from the exchange data storage unit when it is determined that there is no possibility of acquiring data. And butterflies.

  According to this configuration, the data exchange server deletes the exchange data from the exchange data storage unit when there is no possibility that the other user terminal acquires the exchange data for the other user terminal from the one user terminal. Therefore, when another user terminal tries to acquire exchange data from one user terminal, it is possible to prevent a situation in which the exchange data has already been deleted.

  A data exchange method according to a second aspect of the present invention includes a step of receiving login requests from a plurality of user terminals, and storing exchange data from one user terminal of the plurality of user terminals to another user terminal. And when the predetermined time has elapsed from the reception time of the login request from the one user terminal, based on the elapsed time from the reception time of the login request from the other user terminal, Determining whether there is a possibility that one user terminal may obtain the exchange data from the one user terminal, and the other user terminal may obtain the exchange data from the one user terminal. And a step of deleting the exchange data from the one user terminal from the exchange data storage unit when it is determined that there is no compatibility.

  According to the present invention, when exchange data from one user terminal to another user terminal is acquired from the data exchange server by the other user terminal, the situation in which the exchange data has already been deleted is prevented. A data exchange server and a data exchange method that can be provided 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 management information storage part which concerns on 1st Embodiment. It is a flowchart which shows the periodical deletion process operation | movement in the data exchange server which concerns on 1st Embodiment. It is a flowchart which shows the periodical deletion process operation | movement in the data exchange server which concerns on 1st Embodiment. It is a sequence diagram which shows the example of application of the periodical deletion processing operation in the data exchange system which concerns on 1st Embodiment.

  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 (reception unit), a registration processing unit 402, a search processing unit 403 (search unit), an exchange management unit 404, a management information storage unit 405, and an exchange data storage unit. 406, a periodic deletion processing unit 407 (determination unit, deletion unit).

  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, exchange data, a reception request, and the like, which will be described later, from the user terminal 10. Further, the transmission / reception unit 401 transmits a transmission candidate list, 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 login request from the user terminal 10 is received by the transmission / reception unit 401, the registration processing unit 402 receives the user identification information of the user terminal 10 and the reception time of the login request from the user terminal 10 (hereinafter referred to as login request reception time). ) Are stored in the management information storage unit 405 (see FIG. 3).

  Here, the login request is a request for login to the data exchange server 40 in order to use the data exchange service. The login request includes user identification information (for example, a user ID) of the user terminal 10, position information (for example, latitude and longitude, information acquired from GPS, in-zone cell information, etc.), secret words, exchange data, and the like. May be. These pieces of information may be stored in the management information storage unit 405.

  Also, the registration processing unit 402 causes the exchange data storage unit 406 to store the exchange data included in the login request from the user terminal 10. The registration processing unit 402 may store the exchange data in the exchange data storage unit 406 in association with exchange data identification information (for example, a business card ID) or user identification information.

  Also, when the re-login request from the user terminal 10 is received by the transmission / reception unit 401, the registration processing unit 402 updates the login request reception time stored in the management information storage unit 405 to the reception time of the re-login request. Also good. 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. Or when the registration information of the user terminal 10 needs to be changed, such as when the secret password is changed.

  When the search request from the user terminal 10 is received by the transmission / reception unit 401, the search processing unit 403 refers to the management information storage unit 405 and searches 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 10, the user's name, and the like.

  For example, the search processing unit 403 has another login request reception time stored in the management information storage unit 405 between the reception time of the search request (hereinafter referred to as a search request reception time) and a time before a predetermined time. The user terminal 10, that is, another user terminal 10 logged in the data exchange server 40 in the same time zone may be searched. Alternatively, the search processing unit 403 may search for another user terminal 10 located in the same area based on the position information included in the login request. Alternatively, the search processing unit 403 may search for another user terminal 10 having the same password based on the password included in the login request.

  In addition, when the transmission / reception unit 401 receives a re-search request from the user terminal 10, the search processing unit 403 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 403 allows other users 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.

  Note that the search processing unit 403 may update the login request reception time stored in the management information storage unit 405 when the transmission / reception unit 401 receives a search request or a re-search request from the user terminal 10. In such a case, the login request reception time is updated to the reception time of the search request or the re-search request. In this way, by updating the login request reception time, even if the user terminal 10 has passed the time since the login request was received, if the search request or the re-search request is received, the transmission candidate Will be searched.

  Further, the search processing unit 403 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 403 to the user terminal 10.

  When the search processing unit 403 searches for another user terminal 10 as a candidate for sending exchange data of the user terminal 10, the exchange management unit 404 searches the user identification information of the other user terminal 10 searched for and other In the management information storage unit 405 (see FIG. 3), the transmission state of the exchange data from the user terminal 10 to the user terminal 10 and the reception state of the exchange data from the user terminal 10 by other searched user terminals 10 are associated with each other. Remember.

  FIG. 3 is a diagram illustrating an example of the management information storage unit 405 according to the first embodiment. As shown in FIG. 3, in the management information storage unit 405, as the management information of the user terminal 10A, the user identification information “#A” of the user terminal 10A and the login request reception time “09:50” from the user terminal 10A are displayed. , The user identification information “#B” and “#C” of the user terminals 10B and 10C searched as the transmission candidates of the exchange data #A of the user terminal 10A, and the exchange data # for the user terminals 10B and 10C from the user terminal 10A The transmission state of A and the reception state of exchange data #A by the user terminals 10B and 10C are stored in association with each other.

  The configuration of the management information storage unit 405 is not limited to that shown in FIG. The management information storage unit 405 may be composed of two or more storage units (tables). Further, as the management information of the user terminal 10, other item information (not shown) (for example, location information of the user terminal 10, secret words, etc.) may be stored in association with each other.

  When the transmission / reception unit 401 receives a transmission request from the user terminal 10 to another user terminal 10, the exchange management unit 404 sets the transmission state of the exchange data from the user terminal 10 to the other user terminal 10 as “completed (transmission). Update) ”. Here, the transmission request is a request from the user terminal 10 to transmit the exchange data stored in the exchange data storage unit 406 to another user terminal 10 that is a candidate for transmission. For example, in FIG. 3, in response to a transmission request from the user terminal 10A, the transmission state of the exchange data #A from the user terminal 10A to the user terminals 10B and 10C is changed from “Not (not transmitted)” to “Completed (transmitted). ) ”.

  When the exchange data reception request is received by the transmission / reception unit 401, the exchange management unit 404 acquires the exchange data from the exchange data storage unit 406 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 404 to the user terminal 10. The exchange data reception request may include exchange data identification information (for example, a business card ID), and the exchange management unit 404 stores the exchange data associated with the exchange data identification information in the exchange data storage. You may acquire from the part 406.

  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 404 sets the reception state of the user terminal 10 in the management information storage unit 405 to “completed (received). ) ". For example, in FIG. 3, the reception state of the exchange data #A by the user terminal 10B is updated from “not yet received” to “completed (received)”.

  The periodic deletion processing unit 407 performs periodic deletion processing periodically (for example, every hour at 00 minutes). Here, the periodic deletion process is the management information of the user terminal 10 stored in the management information storage unit 405 and the exchange data for the other user terminal 10 from the user terminal 10 stored in the exchange data storage unit 406. This is a process of periodically deleting at least one. The periodic deletion processing unit 407 constitutes a determination unit and a deletion unit.

  Specifically, when a predetermined time (for example, 1 hour) has elapsed from the login request reception time of the user terminal 10, the periodic deletion processing unit 407 sends exchange data for the transmission candidate from the user terminal 10 to the transmission candidate. It is determined whether or not there is a possibility of acquisition.

  For example, when the management information of another user terminal 10 that is a candidate for sending exchange data of the user terminal 10 has been deleted from the management information storage unit 405, the periodic deletion processing unit 407 It may be determined that there is no possibility of acquiring the exchange data. In such a case, the other user terminal 10 cannot acquire the exchange data. Note that the management information of another user terminal 10 is deleted from the management information storage unit 405 by a periodic deletion process when a predetermined time has elapsed from the login request time from the other user terminal 10.

  Further, when a predetermined time has elapsed from the reception time of the login request from another user terminal 10 that is a candidate for sending exchange data of the user terminal 10, the periodic deletion processing unit 407 determines that the sending candidate is the user terminal 10 It may be determined that there is no possibility of acquiring exchange data from In such a case, it is considered that the other user terminals 10 did not intentionally acquire the exchange data.

  Further, the periodic deletion processing unit 407 indicates that the exchange data is received by another user terminal 10 that is a candidate for sending exchange data of the user terminal 10, that is, the reception state of the management information storage unit 405 is “completed ( If it is “received”, the sending candidate may determine that there is no possibility of acquiring exchange data from the user terminal 10. In such a case, the other user terminals have already obtained the exchange data, and therefore there is no need to obtain the exchange data.

  The periodic deletion processing unit 407 is (1) when the management information of another user terminal 10 that is a candidate for sending exchange data of the user terminal 10 has not been deleted from the management information storage unit 405, and (2) If the reception time of the login request from the other user terminal 10 has not elapsed, and (3) if exchange data has not been received by the other user terminal 10, the sending candidate is the user terminal 10 It may be determined that there is a possibility of obtaining exchange data from

  In addition, the determination order of said (1)-(3) is not restricted to this, You may replace. In addition, even when some of the above conditions (1) to (3) are satisfied, the periodic deletion processing unit 407 determines that there is a possibility that the sending candidate may acquire exchange data from the user terminal 10. Good. Further, when conditions other than the above (1) to (3) are satisfied, the periodic deletion processing unit 407 may determine that there is a possibility that the sending candidate may acquire exchange data from the user terminal 10.

  If the periodic deletion processing unit 407 determines that the sending candidate has no possibility of acquiring exchange data from the user terminal 10, the management information of the user terminal 10 stored in the management information storage unit 405 and the exchange data storage unit The exchange data from the user terminal 10 stored in 406 is deleted. On the other hand, if the periodic deletion processing unit 407 determines that there is a possibility that the sending candidate may acquire exchange data from the user terminal 10, the management information of the user terminal 10 stored in the management information storage unit 405 and the exchange data The deletion of the exchange data from the user terminal 10 stored in the storage unit 406 is stopped.

  Next, the operation of the data exchange system according to the first embodiment will be described. Specifically, (1) the periodic deletion processing operation in the periodic deletion processing unit 407 of the data exchange server 40 and (2) an application example of the periodic deletion processing operation in the data exchange system 1 will be described.

(1) Periodic Deletion Processing Operation FIGS. 4 and 5 are flowcharts showing the periodic deletion processing operation in the data exchange server 40 according to the first embodiment. Note that the data exchange server 40 periodically repeats the periodic deletion processing operation shown in FIGS. 4 and 5 (for example, every hour at 00 minutes).

  In FIG. 4, “X” indicates the number of user terminals for which the data exchange server 40 manages the management information. “I” is a subscript indicating the i-th user terminal 10. For example, as shown in FIG. 3, when the data exchange server 40 manages the data of the user terminals 10A to 10C, X = 3. In the following, it is assumed that the first to third user terminals 10 are user terminals 10A to 10C.

  As illustrated in FIG. 4, the data exchange server 40 initializes the subscript “i” of the user terminal 10 when the start time of the periodic deletion process comes (step S <b> 101). Further, the data exchange server 40 adds 1 to the subscript “i” of the user terminal 10 (step S102). Further, the data exchange server 40 repeats the following operations until the determination process of all the user terminals 10 in which the management information is stored in the management information storage unit 405 is completed (that is, until i = X) (step 1). S103).

  The data exchange server 40 determines whether or not a predetermined time (for example, 1 hour) has elapsed since the login request reception time of the i-th user terminal 10 (step S104).

  When the predetermined time has not elapsed since the login request time of the i-th user terminal 10 (step S104; No), the operation returns to step S102. That is, the determination process of the (i + 1) th user terminal 10 is started without deleting the management information of the i th user terminal 10.

  On the other hand, when the predetermined time has elapsed since the login request time of the i-th user terminal 10 (step S104; Yes), the data exchange server 40 sends the exchange data of the i-th user terminal 10 from the management information storage unit 405. The transmission candidate whose transmission state is “completed (transmission completed)” is extracted (step S105).

  When the sending candidate whose exchange data transmission state of the i-th user terminal 10 is “completed (sent)” is not extracted (step S106; No), the data exchange server 40 determines that the i-th user terminal 10 The management information is deleted from the management information storage unit 405, and the exchange data of the i-th user terminal 10 is deleted from the exchange data storage unit 406 (step S107).

  On the other hand, when a sending candidate whose exchange data transmission state of the i-th user terminal 10 is “completed (sent)” is extracted (step S106; Yes), the data exchange server 40 determines that the sending candidate is i-th. It is determined according to the flow shown in FIG. 5 whether there is a possibility of obtaining exchange data of the user terminal 10.

In FIG. 5, “Y _i ” indicates the number of transmission candidates whose exchange data transmission state of the i-th user terminal 10 is “completed (transmitted)”. “J” is a subscript indicating a transmission candidate whose exchange data transmission state is “completed (transmitted)”. For example, in FIG. 3, Y ₁ = 2 because the transmission state of the exchange data from the first user terminal 10A to the transmission candidates (user terminals 10B and 10C) is “completed (transmitted)”.

  As illustrated in FIG. 5, the data exchange server 40 extracts the transmission candidate subscript “submission” when the transmission state of the exchange data from the i-th user terminal 10 is “completed (sent)”. j "and the stop flag are initialized (step S201). Further, the data exchange server 40 determines whether or not the cancel flag is ON (step S202). If the stop flag is not ON (step S202; No), the data exchange server 40 adds 1 to the transmission candidate subscript “j” (step S203). Further, the data exchange server 40 repeats the following operation until the determination process for all the transmission candidates extracted in step S105 in FIG. 4 is completed (that is, until j = Yi) (step S204).

  The data exchange server 40 determines whether the management information of the j-th sending candidate has been deleted from the management information storage unit 405 (step S205).

  If the management information of the j-th sending candidate has been deleted (step S205; Yes), the operation returns to step S202. In such a case, since there is no possibility that the j-th sending candidate acquires the exchange data from the i-th user terminal 10, the data exchange server 40 starts the determination process for the j + 1-th sending candidate.

  If the management information of the jth delivery candidate has not been deleted (step S205; No), the data exchange server 40 determines whether or not a predetermined time has elapsed since the login request time of the jth delivery candidate ( Step S206).

  When a predetermined time has elapsed from the login request time of the j-th sending candidate (step S206; Yes), the operation returns to step S202. In such a case, it is considered that the j-th sending candidate did not intentionally obtain the exchange data from the i-th user terminal 10. That is, since there is no possibility that the j-th sending candidate acquires the exchange data from the i-th user terminal 10, the data exchange server 40 starts the determination process for the j + 1-th sending candidate.

  If the predetermined time has not elapsed since the log-in request time of the j-th sending candidate (step S206; No), the data exchange server 40 has received the exchange data reception status of the i-th user terminal 10 by the j-th sending candidate. It is determined whether or not “completed (received)” (step S207).

  When the reception state of the exchange data of the i-th user terminal 10 by the j-th transmission candidate is “completed (received)” (step S207; Yes), the operation returns to step S202. In this case, the j-th sending candidate has already received the exchange data of the i-th user terminal 10. That is, thereafter, since there is no possibility that the j-th sending candidate acquires the exchange data from the i-th user terminal 10, the data exchange server 40 starts the determination process for the j + 1-th sending candidate.

  When the reception state of the exchange data of the i-th user terminal 10 by the j-th sending candidate is not “completed (received)” (step S207; No), the data exchange server 40 sets the cancel flag to ON (step S207). (S208), this operation returns to step S202. Here, the cancellation flag indicates that the deletion of the data of the i-th user terminal 10 should be canceled when there is a possibility that the j-th sending candidate may acquire the exchange data of the i-th user terminal 10. Flag.

  When the stop flag is set to ON (step S202; Yes), the data exchange server 40 stops data deletion of the exchange data of the i-th user terminal 10 (step S209). And this operation | movement returns to step S102 of FIG. That is, since there is a possibility that the j-th sending candidate acquires the exchange data of the i-th user terminal 10, the data exchange server 40 cancels the deletion of the exchange data and management information of the i-th user terminal 10. The determination process of the (i + 1) th user terminal 10 is started.

  On the other hand, when it is determined that there is no possibility of acquiring the exchange data of the i-th user terminal 10 for the first to Yi-th sending candidates (step S204; Yes), the data exchange server 40 determines that the i-th user terminal The ten pieces of exchange data are deleted from the exchange data storage unit 406, and the management information of the i-th user terminal 10 is deleted from the management information storage unit 405 (step S210). And this operation | movement returns to FIG.4 S102, and the determination process of the i + 1th user terminal 10 is started.

  In FIG. 5, the determination order of steps S205 to S207 is not limited to this. Moreover, a part of steps S205 to S207 may be omitted, or another determination step may be added. The exchange data deletion flow is not limited to that shown in FIG. 5. For example, by performing the determination in step S 207 before step S 201, the reception state of the transmission candidates of the i-th user terminal 10 is “completed”. ”May be excluded from loop control targets in advance. In this case, the number of sending candidates that need to be determined in steps S205 and S206 (that is, a determination that the management information storage unit 405 needs to be searched) can be reduced, so that the determination process can be performed more efficiently.

(2) Application Example of Periodic Deletion Processing Operation FIG. 6 is a sequence diagram showing an application example of the periodic deletion processing operation in the data exchange system according to the first embodiment. In addition, in FIG. 6, the application example in case the some user terminal 10A-10C is logging in to the data exchange server 40 is demonstrated. Further, the data exchange server 40 starts the periodic deletion process shown in FIGS. 4 and 5 periodically (for example, every hour at 00 minutes).

  In FIG. 6, communication between the user terminals 10A to 10C and the data exchange server 40 is performed using, for example, the HTTP protocol, but any protocol may be used as long as communication is possible. . 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.).

  As shown in FIG. 6, each of the user terminals 10A to 10C transmits a login request to the data exchange server 40 (steps S301a to S301c).

  Assume that the data exchange server 40 receives a login request from the user terminals 10A to 10C at 9:50. In such a case, the data exchange server 40, as shown in FIG. 3, the user identification information “#A” to “#C” of the user terminals 10A to 10C and the login request reception time “09: from the user terminals 10A to 10C”. 50 ”is stored in the management information storage unit 405 in association with each other. Further, the data exchange server 40 stores the exchange data included in the login request of the user terminals 10 </ b> A to 10 </ b> C in the exchange data storage unit 406. In exchange data storage unit 406, exchange data of user terminals 10A to 10C may be stored in association with user identification information “#A” to “#C”, exchange data identification information, or the like.

  When the start time (for example, 10:00) of the periodical deletion process comes, the data exchange server 40 performs the periodical deletion process operation described with reference to FIGS. 4 and 5 (step S302). Here, since the start time of the periodic deletion process is 10:00, a predetermined time (for example, 1 hour) has elapsed from the login request reception time “09:50” for any of the user terminals 10A to 10C. Absent. For this reason, any of the user terminals 10A to 10C is excluded from the periodic deletion process (step S104 in FIG. 4; No).

  When the search request limit timer (not shown) started when the login request is transmitted expires, the user terminal 10A requests the data exchange server 40 to search for a transmission candidate for the exchange data #A of the user terminal 10A. A search request is transmitted (step S303).

  Upon receiving the search request from the user terminal 10A, the data exchange server 40 searches for a transmission candidate for the exchange data #A of the user terminal 10A and transmits a transmission candidate list indicating the searched transmission candidate to the user terminal 10A ( Step S304). Here, it is assumed that user terminals 10B and 10C are searched as transmission candidates for exchange data #A.

  The user terminal 10A sends a transmission request for the exchange data #A to the transmission candidates (user terminals 10B and 10C) until the next periodic deletion process is started in the data exchange server 40 (for example, at 10:30). It transmits to the data exchange server 40 (step S305).

  When receiving the exchange data #A for the user terminals 10B and 10C, the data exchange server 40 stores the received exchange data #A in the exchange data storage unit 406. Further, as shown in FIG. 3, the data exchange server 40 updates the transmission state of the exchange data #A to the user terminals 10B and 10C in the management information storage unit 405 to “completed (transmitted)”.

  The user terminal 10B transmits a re-login request to the data exchange server 40 (step S306). As described above, the re-login request is for the user terminal 10B that has already logged in to the data exchange server 40 to request the login again.

  When the data exchange server 40 receives the re-login request from the user terminal 10B, the management information storage unit 405 updates the login request reception time associated with the user identification information “#B” of the user terminal 10B. Here, it is assumed that the data exchange server 40 updates the login request reception time of the user terminal 10B to “10:30”. Although not shown, the data exchange server 40 may update the login request reception time associated with the user identification information “#B” of the user terminal 10B when receiving a re-search request from the user terminal 10B. Good.

  When the start time (for example, 11:00) of the periodic deletion process comes, the data exchange server 40 performs the periodic deletion process operation described with reference to FIGS. 4 and 5 (step S307). Here, since the start time of the periodic deletion process is 11:00, a predetermined time (for example, 1 hour) has elapsed since the login request reception time “09:50” of the user terminals 10A and 10C. For this reason, the records of the user terminals 10 </ b> A and 10 </ b> C are subject to periodic deletion processing (step S <b> 104 in FIG. 4; Yes). Since the login request time of the user terminal 10B is updated to “10:30” by the above-described re-login request, the record of the user terminal 10B is excluded from the periodic deletion process (step S104 in FIG. 4; No).

  As described above, since the transmission state of the exchange data #A of the user terminal 10A for the transmission candidates (user terminals 10B and 10C) has been updated to “completed (transmitted)”, the data exchange server 40 is shown in FIG. In accordance with the flow, it is determined whether or not there is a possibility that the transmission candidate (user terminals 10B and 10C) acquires the exchange data #A.

  At the present time (for example, 11:00), the management information of the user terminal 10C has not been deleted (step S205; No in FIG. 5), and the predetermined time has elapsed from the login request reception time “09:50” of the user terminal 10C. It has elapsed (step S206 in FIG. 5; Yes). For this reason, it is determined that the user terminal 10C, which is a candidate for sending the exchange data #A, has no possibility of acquiring the exchange data #A.

  On the other hand, at the present time (for example, 11:00), the management information of the user terminal 10B is not deleted (step S205 in FIG. 5; No), and the updated login request reception time “10:30” of the user terminal 10B. The predetermined time (for example, 1 hour) has not elapsed since the time (step S206 in FIG. 5; No), and the reception state of the exchange data #A by the user terminal 10B is “not received (not received)” (FIG. 5). Step S207; No). For this reason, it is determined that the user terminal 10B, which is a candidate for sending the exchange data #A, may acquire the exchange data #A, and the record deletion flag of the user terminal 10A is set to ON (FIG. 5). Step S208).

  As described above, the deletion of the management information and the exchange data #A of the user terminal 10A is canceled in the periodic deletion process of step S307 of FIG. 6 (step S209 of FIG. 5). In addition, for the user terminal 10C that is the target of the periodic deletion process, the transmission candidate whose exchange data #C is “completed (sent)” is not extracted (step S106 in FIG. 4; No). For this reason, the management information of the user terminal 10C is deleted from the management information storage unit 405 (step S107 in FIG. 5).

  The user terminal 10B receives the exchange data #A of the user terminal 10A from the data exchange server 40 until the next periodic deletion process is started in the data exchange server 40 (for example, at 11:30) (step S308). ). In this case, the data exchange server 40 updates the reception state of the exchange data #A by the user terminal 10B to “completed (received)”.

  When the start time (for example, 12:00) of the periodic deletion process comes, the data exchange server 40 performs the periodic deletion process operation described in FIGS. 4 and 5 (step S309). As described above, since the management information of the user terminal 10C has been deleted in the previous periodic deletion process, the user terminals 10A and 10B that have passed a predetermined time from the login request reception time are targeted for the periodic deletion process.

  Since the management information of the user terminal 10C has been deleted at the present time (for example, 12:00) (step S205 in FIG. 5; Yes), the user terminal 10C that is a candidate for sending the exchange data #A of the user terminal 10A is It is determined that there is no possibility of acquiring the exchange data #A. Further, since a predetermined time has elapsed from the updated login request time “10:30” of the user terminal 10B (step S206 in FIG. 5; Yes), it is a candidate for sending the exchange data #A of the user terminal 10A. It is determined that the user terminal 10B has no possibility of acquiring the exchange data #A.

  As a result, the management information and the exchange data #A of the user terminal 10A are deleted in the periodic deletion process in step S307 in FIG. 6 (step S210 in FIG. 5). In addition, for the user terminal 10B that is the target of the periodic deletion process this time, a transmission candidate with the transmission state of the exchange data #B of “completed (transmitted)” is not extracted (step S106 in FIG. 4; No). For this reason, the management information of the user terminal 10B is deleted from the management information storage unit 405 (step S107 in FIG. 5).

  As described above, according to the data exchange system according to the first embodiment, even if a predetermined time has elapsed since the login request reception time of the user terminal 10A, the exchange data #A of the user terminal 10A. If there is a possibility that the sending candidate of the user can acquire the exchange data #A, the management information of the user terminal 10A and the exchange data #A are not deleted. For this reason, when the transmission candidate (user terminals 10B and 10C) tries to acquire the exchange data #A for the transmission candidate (user terminals 10B and 10C) from the user terminal 10A, the exchange data #A is already deleted. Can be prevented. Therefore, even if the sending candidate performs re-login or re-search, the sending candidate can appropriately acquire the exchange data #A.

  Moreover, according to the data exchange system which concerns on 1st Embodiment, when the transmission candidates of the exchange data #A of the user terminal 10A are the user terminals 10B and 10C, the user terminal 10B can acquire the exchange data #A. If there is a possibility, the deletion of the exchange data #A and management information of the user terminal 10A is canceled even if the user terminal 10C does not have the possibility of acquiring the exchange data #A. For this reason, even when there are a plurality of sending candidates, it is possible to prevent a situation where the exchange data #A has already been deleted when the sending candidate tries to acquire the exchange data #A.

  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 two storage units of the management information storage unit 405 and the exchange data storage unit 406. However, the configuration of the storage unit is not limited to these, 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 401 ... Transmission / reception part 402 ... Registration process part 403 ... Search process part 404 ... Exchange management part 405 ... Management information storage part 406 ... Exchange data storage unit 407 ... periodic deletion processing unit

Claims (8)

A receiving unit for receiving login requests from a plurality of user terminals;
An exchange data storage unit for storing exchange data from one user terminal of the plurality of user terminals to another user terminal;
When a predetermined time has elapsed since the reception time of the login request from the one user terminal, the other user terminal A determination unit for determining whether or not there is a possibility of acquiring the exchange data from the user terminal;
A deletion unit that deletes the exchange data from the one user terminal from the exchange data storage unit when it is determined that there is no possibility that the other user terminal acquires the exchange data from the one user terminal When,
A data exchange server comprising:   The determination unit determines that there is no possibility that the other user terminal acquires the exchange data when a predetermined time has elapsed from a reception time of a login request from the other user terminal. The data exchange server according to claim 1.   The determination unit has already acquired the exchange data from the one user terminal by the other user terminal even when a predetermined time has not elapsed since the reception time of the login request from the other user terminal. 3. The data exchange server according to claim 1, wherein, when it is determined, the other user terminal determines that there is no possibility of acquiring the exchange data from the one user terminal. The determination unit is a case where a predetermined time has not elapsed since the reception time of the login request from the other user terminal, and the exchange data from the one user terminal has already been acquired by the other user terminal. If not, it is determined that the other user terminal may obtain the exchange data from the one user terminal,
When it is determined that there is a possibility that the other user terminal acquires the exchange data from the one user terminal, the deletion unit, the exchange data from the one user terminal and the one user terminal The data exchange server according to any one of claims 1 to 3, wherein deletion of the management information is canceled. A management information storage unit for storing management information of the plurality of user terminals including reception times of the login requests from the plurality of user terminals;
The deletion unit deletes the management information of the one user terminal from the management information storage unit when it is determined that there is no possibility that the other user terminal acquires the exchange data from the one user terminal. The data exchange server according to claim 1, wherein the data exchange server is a data exchange server.   If the management information of the other user terminal has been deleted from the management information storage unit due to the elapse of a predetermined time from the reception time of the login request from the other user terminal, the determination unit 6. The data exchange server according to claim 5, wherein the terminal determines that there is no possibility of acquiring the exchange data from the one user terminal. The other user terminal includes a first user terminal and a second user terminal,
Even if it is determined that there is no possibility that the first user terminal acquires the exchange data from the one user terminal, the deletion unit is configured such that the second user terminal is the one user terminal. The deletion of the exchange data from the one user terminal and the management information of the one user terminal is stopped when it is determined that there is a possibility of acquiring the exchange data from the one user terminal. The data exchange server described. Receiving login requests from a plurality of user terminals;
Storing exchange data from one user terminal of the plurality of user terminals to another user terminal; and
When a predetermined time has elapsed from the time when the login request is received from the one user terminal, the other user terminal is determined based on the elapsed time from the time when the login request is received from the other user terminal. Determining whether or not there is a possibility of acquiring the exchange data from the user terminal;
A step of deleting the exchange data from the one user terminal from the exchange data storage unit when it is determined that there is no possibility that the other user terminal acquires the exchange data from the one user terminal; ,
A data exchange method characterized by comprising:

Images