Data management with a networked mobile device

• US 8,789,156 B2
• Filed: 08/19/2011
• Issued: 07/22/2014
• Est. Priority Date: 08/19/2011
• Status: Active Grant

• Current Assignee: HCL Technologies Limited
• Original Assignee: International Business Machines Corporation
• Inventors: Fisk, Frank C., Ramanathan, Sri, Terry, Matthew A., Trevathan, Matthew B.
• Primary Examiner(s): Patel, Nirav B
• Assistant Examiner(s): Waliullah, Mohammed
• Application Number:
  US13/213,261
• Publication Number:
  US 20130047233A1
• Time in Patent Office: 1,068 Days
• US Class Current: 726/7
• CPC Class Codes: G06F 21/30 Authentication, i.e. establishing the identity or authorisation of security principals
• CPC Class Codes: G06F 21/606 by securing the transmission between two devices or processes
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: G06F 2221/2129 Authenticate client device independently of the user
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: H04L 63/0492 by using a location-limited connection, e.g. near-field communication or limited proximity of entities
• CPC Class Codes: H04L 63/18 using different networks or channels, e.g. using out of band channels cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals

Abstract

A tool for establishing a wireless connection from a mobile device to another device in proximity to the mobile device. The mobile device receives requests for data, such as a user profile, medical records, etc. from the device. The mobile device has the ability to register/preapprove the requesting device allowing the device to access the requested data. The mobile device also has the ability to give varying devices different authorization levels. The mobile device has the ability to store the data on another system, and in response to the request, validate the requesting device and the device'"'"'s authorization level, request the data from the other system through a network, and return the data to the requesting device.

Claims

1. A method for managing data with a mobile device, the method comprising the steps of:

the mobile device establishing a wireless Near-Field Communication (NFC) connection with an electronic device;

the mobile device receiving, from the electronic device, an indication of an emergency involving a user of the mobile device who will not be asked to help obtain a data file needed to handle the emergency, the indication including a secure token unique to the electronic device and a request for the electronic device to connect to the mobile device without approval from the user;

the mobile device, without involvement of the user, automatically wirelessly connecting, via a network, to a server which has access to the data file, and automatically sending, to the server, authentication information identifying the mobile device;

the mobile device receiving, from the server, approval of the authentication information, and, in response, the mobile device automatically sending the secure token to the server for validation;

the mobile device receiving, from the server, validation of the secure token, and in response, the mobile device connecting to the electronic device;

the mobile device receiving a request, via the wireless NFC connection, from the electronic device for the data file;

the mobile device sending the request for the data file to the server;

the mobile device receiving the data file from the server; and

the mobile device sending the data file to the electronic device.

2. The method of claim 1, further comprising the prior step of the mobile device scanning a surrounding area for compatible electronic devices, and in response, locating the electronic device.

3. The method of claim 1, wherein the authentication information is selected from a list consisting of:

a secure token, a passphrase, cookies, an encrypted key, a unique ID, a userID and password, and combinations thereof.

4. The method of claim 1, further comprising the steps of:

the mobile device determining an authorization level of the secure token in response to receiving validation of the secure token;

the mobile device determining a required authorization level of the requested data file; and

the mobile device determining the authorization level of the secure token meets or exceeds the required authorization level of the requested data file, and in response to the determination, the mobile device sending the requested data file to the electronic device.

5. The method of claim 4, wherein the mobile device determines the authorization level of the secure token does not meet or exceed the required authorization level of the requested data file, and the mobile device disconnects from the electronic device.

6. The method of claim 1, wherein the step of receiving the secure token from the electronic device is responsive to the mobile device determining that the electronic device is not currently authorized to access the data file.

7. The method of claim 1 further comprising the step of sending a message to a known user of the mobile device notifying the known user of the mobile device that the data file was requested.

8. The method of claim 1, wherein, subsequent to receiving the data file on the mobile device, the mobile device determining whether the data file can be stored on the mobile device;

and

responsive to determining the data file can be stored on the mobile device, the mobile device storing the data file.

9. A computer system comprising one or more processors, one or more computer-readable memories, one or more computer-readable, tangible storage devices and program instructions which are stored on the one or more storage devices for execution by the one or more processors via the one or more memories and when executed by the one or more processors perform the method of claim 1.

10. The method of claim 1,

wherein the electronic device requesting the data file is operated by a medical service provider;

wherein the requested data file is a medical record of a registered user of the mobile device; and

wherein validation of the secure token unique to the electronic device verifies that the electronic device is operated by the medical service provider.

11. A computer program product for managing data with a mobile device, the computer program product comprising:

one or more computer-readable storage devices and program instructions stored on the one or more storage devices, the program instructions comprising;

program instructions to establish a wireless Near-Field Communication (NFC) connection with an electronic device;

program instructions to receive, from the electronic device, an indication of an emergency involving a user of the mobile device who will not be asked to help obtain a data file needed to handle the emergency, the indication including a secure token unique to the electronic device and a request for the electronic device to connect to the mobile device without approval from the user;

program instructions to, without involvement of the user, automatically wirelessly connect, via a network, to a server which has access to the data file, and automatically send, to the server authentication information identifying the mobile device;

program instructions to receive, from the server, approval of the authentication information, and, in response, the mobile device automatically sending the secure token to the server for validation;

program instructions to receive, from the server, validation of the secure token, and in response, program instructions to connect to the electronic device;

program instructions to receive a request, via the wireless NFC connection, from the electronic device for the data file;

program instructions to send the request for the data file to the server;

program instructions to receive the data file from the server; and

program instructions to send the data file to the electronic device.

12. The computer program product of claim 11, further comprising program instructions, stored on the one or more storage devices, to scan a surrounding area for compatible electronic devices, and in response, locate the electronic device.

13. The computer program product of claim 11, wherein the authentication information is selected from a list consisting of:

a secure token, a passphrase, cookies, an encrypted key, a unique ID, a userID and password, and combinations thereof.

14. The computer program product of claim 11, further comprising program instructions, stored on the one or more storage devices, to:

determine an authorization level of the secure token in response to receiving validation of the secure token;

determine a required authorization level of the requested data files; and

determine the authorization level of the secure token meets or exceeds the required authorization level of the requested data file, and in response to the determination, send the requested data file to the electronic device.

15. The computer program product of claim 11, wherein the program instructions to receive the secure token from the electronic device are executed responsive to determining that the electronic device is not currently authorized to access the data file.

16. The computer program product of claim 11, further comprising program instructions, stored on the one or more storage devices, to send a message to a known user of the mobile device notifying the known user of the mobile device that the data file was requested.

17. The computer program product of claim 11, further comprising, subsequent to receiving the data file on the mobile device, program instructions, stored on the one or more storage devices, to determine whether the data file can be stored on the mobile device;

and

responsive to determining the data file can be stored on the mobile device, program instructions to store the data file.

18. A computer system for managing data with a mobile device, the computer system comprising:

one or more processors, one or more computer-readable memories, one or more computer-readable, storage devices and program instructions which are stored on the one or more storage devices for execution by the one or more processors via the one or more memories, the program instructions comprising;

program instructions to establish a wireless Near-Field Communication (NFC) connection with an electronic device;

program instructions to receive, from the electronic device, an indication of an emergency involving a user of the mobile device who will not be asked to help obtain a data file needed to handle the emergency, the indication including a secure token unique to the electronic device and a request for the electronic device to connect to the mobile device without approval from the user;

program instructions to, without involvement of the user, automatically wirelessly connect, via a network, to a server which has access to the data file, and automatically send, to the server, authentication information identifying the mobile device;

program instructions to receive, from the server, approval of the authentication information, and, in response, the mobile device automatically sending the secure token to the server for validation;

program instructions to receive, from the server, validation of the secure token, and in response, program instructions to connect to the electronic device;

program instructions to receive a request, via the wireless NFC connection, from the electronic device for the data file;

program instructions to send the request for the data file to the server;

program instructions to receive the data file from the server; and

program instructions to send the data file to the electronic device.

19. The computer system of claim 18, further comprising program instructions, stored on the one or more storage devices for execution by the one or more processors via the one or more memories, to scan a surrounding area for compatible electronic devices, and in response, locate the electronic device.

20. The computer system of claim 18, wherein the authentication information is selected from a list consisting of:

a secure token, a passphrase, cookies, an encrypted key, a unique ID, a userID and password, and combinations thereof.

21. The computer system of claim 18, further comprising program instructions, stored on the one or more storage devices for execution by the one or more processors via the one or more memories, to:

determine an authorization level of the secure token in response to receiving validation of the secure token;

determine a required authorization level of the requested data files; and

determine the authorization level of the secure token meets or exceeds the required authorization level of the requested data file, and in response to the determination, send the requested data file to the electronic device.

22. The computer system of claim 18, wherein the program instructions to receive the secure token from the electronic device are executed responsive to determining that the electronic device is not currently authorized to access the data file.

23. The computer system of claim 18, further comprising program instructions, stored on the one or more storage devices for execution by the one or more processors via the one or more memories, to send a message to a known user of the mobile device notifying the known user of the mobile device that the data file was requested.

24. The computer system of claim 18, further comprising, subsequent to receiving the data file on the mobile device, program instructions, stored on the one or more storage devices for execution by the one or more processors via the one or more memories, to determine whether the data file can be stored on the mobile device;

and

responsive to determining the data file can be stored on the mobile device, program instructions to store the data file.