Hardware resource access systems and techniques

• US 10,334,056 B2
• Filed: 09/07/2017
• Issued: 06/25/2019
• Est. Priority Date: 09/26/2014
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Olcese, Jose A., Morin, Ricardo A., Gore, Vadim, Sharma, Suman, Gadiraju, Narasimham
• Primary Examiner(s): Lazaro, David R
• Assistant Examiner(s): Shitayewoldetadik, Berhanu
• Application Number:
  US15/698,575
• Publication Number:
  US 20180183880A1
• Time in Patent Office: 656 Days
• Field of Search: 709225
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3228 One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/50 Secure pairing of devices

Abstract

Systems and techniques for hardware resource access are disclosed herein. In some embodiments, an apparatus may receive, via a stateless protocol message, a request from an application to pair with a hardware resource of a computing device remote from the apparatus. The apparatus may provide to the computing device, via a stateless protocol message, identifiers of the application and the hardware resource, and may receive, via a stateless protocol message, pairing approval from the computing device. In response to receiving the pairing approval, the apparatus may generate a pairing token that may be used by the application to pair the application with the hardware resource. Other embodiments may be disclosed and/or claimed.

Claims

1. A computer device to be employed as a server in a cloud computing environment the computer device comprising:

Communication circuitry to;

receive a first stateless protocol message from an application implemented by another computer device via a cloud pathway, the first stateless protocol message to include a pairing request, wherein the pairing request is to indicate a hardware resource to which the application requests pairing,

transmit a second stateless protocol message to the application via the cloud pathway, the second stateless protocol message to include a pairing request identifier to be provisioned in or to the application, wherein the pairing request identifier is to trigger a request for pairing request data,

receive a third stateless protocol message from a capability proxy via the cloud pathway, the third stateless protocol message to include the request for pairing request data, wherein the request for pairing request data includes the pairing request identifier, and

transmit a fourth stateless protocol message to the capability proxy via the cloud pathway, the fourth stateless protocol message to include the pairing request data, wherein the pairing request data is for verification of the pairing request to permit the application to access the hardware resource, and the pairing request data includes an identifier of the application and an identifier of the hardware resource; and

processor circuitry communicatively coupled with the communication circuitry, the processor circuitry to;

generate the pairing request identifier in response to receipt of the pairing request, the pairing request identifier to trigger a request for pairing request data, wherein the pairing request identifier is to be provisioned in or to the application, and

in response to receipt of the third stateless protocol message, generate the pairing request data or obtain the pairing request data from storage, wherein the pairing request data includes an identifier of the application and an identifier of the hardware resource, and the pairing request data is to trigger verification of the pairing request for permitting access to the hardware resource.

2. The computer device of claim 1, wherein:

the communication circuitry is to receive, based on the fourth stateless protocol message, a fifth stateless protocol message from the capability proxy via the cloud pathway, where in the fifth stateless protocol message is to include a pairing approval, wherein the pairing approval is generated based at least on some or all of the pairing request data; and

the processor circuitry is to generate, based on the pairing approval, a pairing token to pair the application with the hardware resource, wherein the pairing token is to be provisioned to the application.

3. The computer device of claim 2, wherein the fifth stateless protocol message is to include an identifier of the capability proxy, and the processor circuitry is to generate the pairing token using the identifier of the capability proxy.

4. The computer device of claim 3, wherein:

the communication circuitry is to;

receive a sixth stateless protocol message from the application via the cloud pathway, and

transmit a seventh stateless protocol message to the application via the cloud pathway, the seventh stateless protocol message to include the pairing token; and

the processor circuitry to generate the seventh stateless protocol message when the sixth stateless protocol message includes the pairing request identifier.

5. The computer device of claim 4, wherein the communication circuitry is to:

receive a status check request stateless protocol message from the application via the cloud pathway, the status check request stateless protocol message to request a status of approval for access to the hardware resource, and

transmit a status check response stateless protocol message to the application via the cloud pathway, the status check response stateless protocol message to indicate the status of approval for access to the hardware resource.

6. The computer device of claim 1, wherein the other computer device is a first other computer device, and the hardware resource is disposed in the first other computer device or a second other computer device that is remote from the first computer device and the server.

7. The computer device of claim 6, wherein the capability proxy is implemented by the first other computer device when the hardware resource is disposed in the first other computer device, and the capability proxy is implemented by the second other computer device when the hardware resource is disposed in the second other computer device.

8. The computer device of claim 1, wherein the first, second, third, and fourth stateless protocol messages are Representational State Transfer (REST) messages, wherein the identifier of the application included in the pairing request data is an Internet Protocol (IP) address of the application, and the pairing request data further includes an application programming interface key.

9. One or more non-transitory computer readable storage media (NTCRSM) including instructions, wherein execution of the instructions by one or more processors of a server in a cloud computing environment is to cause the server to:

control receipt of a first stateless protocol message from an application implemented by another computer device via a cloud pathway, the first stateless protocol message to include a pairing request, wherein the pairing request is to indicate a hardware resource to which the application requests pairing;

generate, in response to receipt of the pairing request, a temporary token to trigger a request for pairing request data, wherein the temporary token is to be provisioned in or to the application;

control transmission of a second stateless protocol message to the application via the cloud pathway, the second stateless protocol message to include the temporary token,

control receipt of a third stateless protocol message from a capability proxy via the cloud pathway, the third stateless protocol message to include the temporary token;

generate, in response to receipt of the third stateless protocol message, the pairing request data, or obtain the pairing request data from storage, wherein the pairing request data includes an identifier of the application and an identifier of the hardware resource, and the pairing request data is to trigger verification of the pairing request for permitting access to the hardware resource; and

control transmission of a fourth stateless protocol message to the capability proxy via the cloud pathway, the fourth stateless protocol message to include the pairing request data.

10. The one or more NTCRSM of claim 9, wherein execution of the instructions is to cause the server to:

control receipt of a fifth stateless protocol message from the capability proxy via the cloud pathway, wherein the fifth stateless protocol message is to include a pairing approval, wherein the pairing approval is generated based at least on some or all of the pairing request data; and

generate, based on the pairing approval, a pairing token to pair the application with the hardware resource, wherein the pairing token is to be provisioned to the application.

11. The one or more NTCRSM of claim 10, wherein the fifth stateless protocol message is to include an identifier of the capability proxy, and execution of the instructions is to cause the server to generate the pairing token based on the identifier of the capability proxy.

12. The one or more NTCRSM of claim 11, wherein execution of the instructions is to cause the server to:

control receipt of a sixth stateless protocol message from the application via the cloud pathway;

generate a seventh stateless protocol message to include the pairing token when the sixth stateless protocol message includes the temporary token, or

generate the seventh stateless protocol message to include an access denial message when the sixth stateless protocol message does not include the temporary token; and

control transmission of the seventh stateless protocol message to the application via the cloud pathway.

13. The one or more NTCRSM of claim 12, wherein execution of the instructions is to cause the server to:

control receipt of a status check request stateless protocol message from the application via the cloud pathway, the status check request stateless protocol message to request a status of approval for access to the hardware resource, and

control transmission of a status check response stateless protocol mess age to the application via the cloud pathway, the status check response stateless protocol message to indicate the status of approval for access to the hardware resource.

14. A computer device to implement a capability proxy, the computer device comprising:

processor circuitry to operate the capability proxy to authorize access to a hardware resource; and

communication circuitry communicatively coupled with the processor circuitry, the communication circuitry to;

receive a first stateless protocol message from a server via a cloud device-to-device (D2D) pathway, the first stateless protocol message to include a routing ticket number (RN) that is based on a pairing request provided to the server by an application for pairing with the hardware resource, wherein the RTN is to trigger a request a request for pairing request data, and wherein the RTN is to be provisioned in or to the application,

transmit a second stateless protocol message to the server via the cloud D2D pathway, the second stateless protocol message to include the RTN and the request for pairing request data,

receive a third stateless protocol message from the server via the cloud D2D pathway, the third stateless protocol message to include the pairing request data, wherein the pairing request data includes an application identifier and a hardware resource identifier, and the pairing request data is to trigger verification of the pairing request for permitting access to the hardware resource, and

transmit a fourth stateless protocol message to the server via the cloud D2D pathway, the fourth stateless protocol message to include a pairing approval or a pairing denial, wherein the pairing approval is to indicate that the application is authorized to access the hardware resource and the pairing denial is to indicate that the application is not authorized to access the hardware resource; and

wherein the processor circuitry is to generate the pairing approval or the pairing denial based at least on some or all of the pairing request data.

15. The computer device of claim 14, wherein the processor circuitry is to verify the application based on the pairing request data, and to generate the pairing approval upon properly verifying the application.

16. The computer device of claim 14, wherein the RTN is to trigger the processor circuitry to initiate execution of the capability proxy or to trigger the capability proxy to establish a network connection with the server.

17. The computer device of claim 14, wherein the second stateless protocol message or the fourth stateless protocol message is to indicate a status of the pairing request verification at the capability proxy.

18. The computer device of claim 14, wherein the computer device is a first computer device, the hardware resource is disposed in the first computer device, and the application is implemented by the processor circuitry, or the application is implemented by processor circuitry of a second computer device that is remote from the first computer device and the server.

19. The computer device of claim 18, wherein, when the application is implemented by the second computer device, the processor circuitry is to:

provide a prompt for approval via a user interface; and

generate the pairing approval in response to receipt of approval via the user interface.

20. The computer device of claim 14, wherein the processor circuitry is to:

permit establishment of a direct D2 D communications link with a computer device that implements the application when the pairing approval is generated.

21. The computer device of claim 20, wherein:

the processor circuitry is to;

control access to the hardware resource in response to receipt of a request to access the hardware resource, and

generate data based on the access to the hardware resource; and

the communication circuitry is to;

receive a fifth stateless protocol message directly from the application, the fifth stateless protocol message to include the request to access the hardware resource, and

transmit a sixth stateless protocol message, the sixth stateless protocol message to include the generated data based on the access to the hardware resource.

22. The computer device of claim 21, wherein:

the first, second, third, fourth, fifth, and sixth stateless protocol messages are Representational State Transfer (REST) messages;

the application identifier included in the pairing request data is an Internet Protocol (IP) address of the application, and the pairing request data further includes an application programming interface key; and

the processor circuitry is implemented as one or more application processors, a controller of a network interface card, or a manageability engine, wherein the capability proxy is a kernel application when the processor circuitry is implemented as the one or more application processors.

23. One or more non-transitory computer readable storage media (NTCRSM) including instructions, wherein execution of the instructions by one or more processors of a computer device is to cause the computer device to:

control receipt of a first stateless protocol message from a server via a cloud device-to-device (D2D) pathway, the first stateless protocol message to include a routing ticket number (RTN) that is based on a pairing request provided to the server by an application for pairing with a hardware resource, the RTN to trigger a request for pairing request data, and wherein the RTN is to be provisioned in or to the application;

control transmission of a second stateless protocol message to the server via the cloud D2D pathway, the second stateless protocol message to include the RTN and the request for pairing request data;

control receipt of a third stateless protocol message from the server via the cloud D2D pathway, the third stateless protocol message to include the pairing request data, wherein the pairing request data includes an application identifier and a hardware resource identifier, and the pairing request data is to trigger verification of the pairing request for permitting access to the hardware resource;

generate a pairing approval or a pairing denial based at least on some or all of the pairing request data and in response to receipt of approval via the user interface, wherein the pairing approval is to indicate that the application is authorized to access the hardware resource and the pairing denial is to indicate that the application is not authorized to access the hardware resource;

control transmission of a fourth stateless protocol message to the server via the cloud D2D pathway, the fourth stateless protocol message to include the pairing approval or the pairing denial;

cause establishment of a direct D2D communication link with a computer device that implements the application when the pairing approval is generated;

control receipt of a fifth stateless protocol message directly from the application, the fifth stateless protocol message to include a request to access the hardware resource;

access the hardware resource in response to receipt of a request to access the hardware resource;

generate data based on the access to the hardware resource; and

control transmission of a sixth stateless protocol message, the sixth stateless protocol message to include the generated data based on the access to the hardware resource.

24. The one or more NTCRSM of claim 23, wherein execution of the instructions is to cause the computer device to:

verify the application based on the pairing request data; and

generate the pairing approval upon properly verifying the application.

25. The one or more NTCRSM of claim 23, wherein:

the first, second, third, fourth, fifth, and sixth stateless protocol messages are Representational State Transfer (REST) messages;

the application identifier included in the pairing request data is an Internet Protocol (IP) address of the application, and the pairing request data further includes an application programming interface key;

the request to access the hardware resource includes the token and information for accessing the hardware resource; and

the direct D2 D communication link comprises an embedded web server (EWS) pathway.