Difference between revisions of "Remote Secure Element"
(Created page with "==Full Title or Meme== ==Patents== May 19, 2015 A policy server that is associated with a secure element owner receives a request, from a service provider, to provision acces...") |
(→Patents) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
==Patents== | ==Patents== | ||
| − | May 19, 2015 | + | * Feb. 7, 2013 REMOTE LOCK OF A SECURE ELEMENT US 2013/0035071 A1 |
| + | A method for transmitting data between a mobile communication device and a server. The method includes running a mobile application on the mobile communication device. The mobile application is hosted on the mobile communication device through the server as a Software as a Service (SaaS). The method further includes transmitting data associated with the mobile application between the mobile communication device and the server, in which transmission of the data between the mobile communication device and the server is monitored through the server. | ||
| + | |||
| + | * May 19, 2015 US Patent Application for REMOTE SECURE ELEMENT POLICY MANAGEMENT Patent Application (Application #20160344560) | ||
A policy server that is associated with a secure element owner receives a request, from a service provider, to provision access, by an application, to the secure element. The policy server creates, in response to the request, a policy ticket, for the service provider, that defines privileges for the service provider to create a security domain or a new profile within the secure element. The policy server provides, to a service provider trusted service manager (TSM), the policy ticket and a signed certificate, the signed certificate corresponding to a root certificate that is inserted into a Controlling Authority Security Domain (CASD) portion of the secure element prior to receiving the request. When the CASD receives the policy ticket and signed certificate from the service provider TSM, the CASD validates based on the root certificate and provisions access to the secure element based on information in the policy ticket.<ref>https://patents.justia.com/patent/20160344560</ref> | A policy server that is associated with a secure element owner receives a request, from a service provider, to provision access, by an application, to the secure element. The policy server creates, in response to the request, a policy ticket, for the service provider, that defines privileges for the service provider to create a security domain or a new profile within the secure element. The policy server provides, to a service provider trusted service manager (TSM), the policy ticket and a signed certificate, the signed certificate corresponding to a root certificate that is inserted into a Controlling Authority Security Domain (CASD) portion of the secure element prior to receiving the request. When the CASD receives the policy ticket and signed certificate from the service provider TSM, the CASD validates based on the root certificate and provisions access to the secure element based on information in the policy ticket.<ref>https://patents.justia.com/patent/20160344560</ref> | ||
==References== | ==References== | ||
Latest revision as of 21:32, 8 November 2024
Full Title or Meme
Patents
- Feb. 7, 2013 REMOTE LOCK OF A SECURE ELEMENT US 2013/0035071 A1
A method for transmitting data between a mobile communication device and a server. The method includes running a mobile application on the mobile communication device. The mobile application is hosted on the mobile communication device through the server as a Software as a Service (SaaS). The method further includes transmitting data associated with the mobile application between the mobile communication device and the server, in which transmission of the data between the mobile communication device and the server is monitored through the server.
- May 19, 2015 US Patent Application for REMOTE SECURE ELEMENT POLICY MANAGEMENT Patent Application (Application #20160344560)
A policy server that is associated with a secure element owner receives a request, from a service provider, to provision access, by an application, to the secure element. The policy server creates, in response to the request, a policy ticket, for the service provider, that defines privileges for the service provider to create a security domain or a new profile within the secure element. The policy server provides, to a service provider trusted service manager (TSM), the policy ticket and a signed certificate, the signed certificate corresponding to a root certificate that is inserted into a Controlling Authority Security Domain (CASD) portion of the secure element prior to receiving the request. When the CASD receives the policy ticket and signed certificate from the service provider TSM, the CASD validates based on the root certificate and provisions access to the secure element based on information in the policy ticket.[1]
