Terminal device, data management server, terminal program, data management program, and data management system

Patent metadata

Field	Value
Publication number	US-9582679-B2
Application number	US-201514672340-A
Country	US
Kind code	B2
Filing date	Mar 30, 2015
Priority date	Apr 8, 2014
Publication date	Feb 28, 2017
Grant date	Feb 28, 2017

Abstract

A terminal device that includes a processor configured to execute a procedure. The procedure includes: receiving an electronic text data request; attaching to the electronic text data request a token associated with a ticket, and attaching to the electronic text data request a changed status ticket out of the ticket; and holding sending of a new electronic text data request when the new electronic text data request is received during an interval between sending the electronic text data request to the data management server and receiving a token, and relaying any held electronic text data requests in sequence to the data management server, when it is after the interval and there are no changed status tickets of the terminal present.

First claim

What is claimed is:

1. A terminal device, comprising:
a processor configured to execute a process, the process comprising:
receiving an electronic text data request requesting data managed by a data management server;
attaching, to the received electronic text data request, a token generated by the data management server, the token associated with at least one ticket used as an access right to the data and corresponding to a circumstance of the terminal, or a circumstance of a user using the terminal, or both;
from among the at least one ticket, further attaching, to the electronic text data request, a changed status ticket with a changed status corresponding to a change in the circumstance, the changed status ticket includes at least ticket type and ticket name indicating a specific content relating to the ticket type and in a case which the ticket name is changed, a status of the changed status ticket is changed; and
holding transmission of a new electronic text data request when the new electronic text data request is received during an interval between sending the electronic text data request, with the changed status ticket attached thereto, to the data management server and receiving an updated token based on the changed status ticket from the data management server, and relaying any held electronic text data requests to the data management server in sequence, after the interval when there are no changed status tickets of the terminal present.

2. The terminal device of claim 1 , wherein:
on receipt of the new electronic text data request during the interval, determination is made for each of the new electronic text data requests as to whether or not it is necessary to hold relay to the data management server; and
transmission of the new electronic text data request is held when holding is determined to be necessary, and the new electronic text data request is relayed to the data management server without holding when holding is determined to be unnecessary.

3. The terminal device of claim 2 , wherein an application that sent the new electronic text data request received during the interval is identified, and determination is made as to whether or not it is necessary to hold transmission of the new electronic text data request based on an attribute of the identified application.

4. The terminal device of claim 3 , wherein:
the attribute of the application is a transmission frequency at which electronic text data requests are sent by the application; and
determination is made to hold the new electronic text data request when the new electronic text data request is received during the interval from an application for which the transmission frequency is a predetermined defined frequency or higher.

5. The terminal device of claim 2 , wherein determination is made to hold the new electronic text data request in cases in which the new electronic text data request received during the interval has a number of changed status tickets of the terminal exceeding a predetermined number of tickets.

6. The terminal device of claim 2 , wherein determination is made as to whether or not it is necessary to hold transmission of the new electronic text data request based on a type of data requested by the new electronic text data request received during the interval.

7. The terminal device of claim 1 , wherein the electronic text data request is expressed in a format that conforms to HTTP.

8. A non-transitory recording medium storing a program that causes a computer to execute a terminal process, the process comprising:
receiving an electronic text data request requesting data managed by a data management server;
attaching, to the received electronic text data request, a token generated by the data management server, the token associated with at least one ticket used as an access right to the data and corresponding to a circumstance of the terminal, or a circumstance of a user using the terminal, or both;
from among the at least one ticket, further attaching, to the electronic text data request, a changed status ticket with a changed status corresponding to a change in the circumstance, the changed status ticket includes at least ticket type and ticket name indicating a specific content relating to the ticket type and in a case which the ticket name is changed, a status of the changed status ticket is changed; and
holding transmission of a new electronic text data request when the new electronic text data request is received during an interval between sending the electronic text data request, with the changed status ticket attached thereto, to the data management server and receiving an updated token based on the changed status ticket from the data management server, and relaying any held electronic text data requests to the data management server in sequence, after the interval when there are no changed status tickets of the terminal present.

9. The non-transitory recording medium of claim 8 , wherein the terminal process further comprises:
on receipt of the new electronic text data request during the interval, determining for each of the new electronic text data requests whether or not it is necessary to hold relay to the data management server; and
holding transmission of the new electronic text data request when holding is determined to be necessary, and relaying the new electronic text data request to the data management server without holding when holding is determined to be unnecessary.

10. The non-transitory recording medium of claim 9 , the terminal process further comprising identifying an application that sent the new electronic text data request received during the interval, and determining whether or not it is necessary to hold transmission of the new electronic text data request based on an attribute of the identified application.

11. The non-transitory recording medium of claim 10 , wherein:
the attribute of the application is a transmission frequency at which electronic text data requests are sent by the application; and
the terminal process further comprises determining to hold the new electronic text data request when the new electronic text data request is received during the interval from an application for which the sending frequency is a predetermined defined frequency or higher.

12. The non-transitory recording medium of claim 9 , the terminal process further comprising determining to hold the new electronic text data request in cases in which the new electronic text data request received during the interval has a number of changed status tickets of the terminal exceeding a predetermined number of tickets.

13. The non-transitory recording medium of claim 9 , the terminal process further comprising determining whether or not it is necessary to hold transmission of the new electronic text data request based on a type of data requested by the new electronic text data request received during the interval.

14. The non-transitory recording medium of claim 8 , wherein the electronic text data request is expressed in a format that conforms to HTTP.

15. A data management system, comprising:
a terminal device including:
a processor configured to execute a process, the process comprising:
receiving an electronic text data request requesting data managed by a data management server, and that relays the electronic text data request to the data management server;
attaching, to the electronic text data request, a token generated by the data management server and associated with at least one ticket used as an access right to the data and corresponding to a circumstance of the terminal, or a circumstance of a user

Assignees

• Fujitsu Ltd

Inventors

• Ohtani Takeshi
• Sasaki Kazuo

Classifications

• G06F21/6218 Primary

  to a system of files or objects, e.g. local or distributed file system or database · CPC title

• G06F21/30

  Authentication, i.e. establishing the identity or authorisation of security principals · CPC title

• G06F21/6209 Primary

  to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title