eUICC Subscription Change
US-2016286379-A1 · Sep 29, 2016 · US
US9668122B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9668122-B2 |
| Application number | US-201514787894-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 29, 2015 |
| Priority date | Dec 10, 2014 |
| Publication date | May 30, 2017 |
| Grant date | May 30, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The invention relates to a node for managing network connectivity of a device comprising an embedded Universal Integrated Circuit Card (eUICC). The node is configured to provision the eUICC for network connectivity of the device. The method comprises acquiring an identity of at least one Subscription Manager-Data Preparation (SM-DP) entity, acquiring an identity of at least one Subscription Manager-Secure Router (SM-SR) entity, creating an association between the identity of the at least one SM-DP entity, the identity of the at least one SM-SR entity and an identity of the eUICC, and storing the created association, wherein the stored association subsequently can be changed for the eUICC by changing at least one of the identity of the at least one SM-DP entity and the identity of the at least one SM-SR entity with which the eUICC is to be associated.
Opening claim text (preview).
The invention claimed is: 1. A method performed by a node for managing connectivity of a device comprising an embedded Universal Integrated Circuit Card, eUICC, the node being configured to provision the eUICC for network connectivity of the device, comprising: acquiring at the node an identity of at least one Subscription Manager-Secure Router, SM-SR, entity that is separate from the node; acquiring at the node an identity of at least one Subscription Manager-Data Preparation, SM-DP, entity that is separate from the node; creating an association between the identity of the at least one SM-DP entity, the identity of the at least one SM-SR entity and an identity of the eUICC; and storing the created association, wherein the stored association subsequently can be changed for the eUICC by replacing at least one of the identity of the at least one SM-DP entity and the identity of the at least one SM-SR entity with which the eUICC is to be associated. 2. The method of claim 1 , wherein the creating of the association comprises: creating an association between the identities of a plurality of SM-DP entities, the identity of the at least one SM-SR entity and the identity of the eUICC. 3. The method of claim 1 , wherein the creating of the association comprises: creating an association between the identity of the at least one SM-DP entity, the identities of a plurality of SM-SR entities and the identity of the eUICC, wherein the plurality of SM-SR entities comprise a first SM-SR entity and a second SM-SR entity, different from the first SM-SR entity. 4. The method of claim 1 , the eUICC comprising a plurality of subscription profiles, wherein the creating of the association comprises: creating an association between the identities of a plurality of SM-DP entities, the identity of a single SM-SR entity and the identity of the eUICC, where the identity of each of the plurality of SM-DP entities is associated with a corresponding subscription profile among the plurality of subscription profiles. 5. The method of claim 1 , wherein the acquiring of an identity of at least one SM-SR entity comprises: requesting the identity of the at least one SM-SR entity, the at least one SM-SR identity being provided in an eUICC data file. 6. The method of claim 5 , the entity to which the request is made being an Embedded UICC Manufacturer, EUM, of the eUICC or an SM-SR entity for which the identity is requested. 7. The method of claim 1 , wherein the acquiring of an identity of at least one SM-DP entity comprises: requesting the identity of the at least one SM-DP entity, the at least one SM-DP entity being provided in a subscription profile data file. 8. The method of claim 7 , the entity to which the request is made being an SM-DP entity for which the identity is requested. 9. The method according to claim 1 , the identities being configured to designate a destination address of the respective SM-SR and SM-DP entities. 10. The method according to claim 9 , the destination address being an Internet Protocol, IP, address. 11. A computer program product comprising a non-transitory computer readable storage medium storing computer-executable instructions for causing a node to perform steps recited in claim 1 when the computer-executable instructions are executed on a processor comprised in the node. 12. A node configured to manage connectivity of a device comprising an embedded Universal Integrated Circuit Card, eUICC, the node being configured to provision the eUICC for managing the network connectivity of the device, which node comprises a processing unit and a memory, said memory containing instructions executable by said processing unit, whereby said node is configured to: acquire at the node an identity of at least one Subscription Manager-Secure Router, SM-SR, entity that is separate from the node; acquire at the node an identity of at least one Subscription Manager-Data Preparation, SM-DP, entity that is separate from the node; create an association between the identity of the at least one SM-DP entity, the identity of the at least one SM-SR entity and an identity of the eUICC; and store the created association, wherein the stored association subsequently can be changed for the eUICC by replacing at least one of the identity of the at least one SM-DP entity and the identity of the at least one SM-SR entity with which the eUICC is to be associated. 13. The node of claim 12 , further configured to, when creating the association: create an association between the identities of a plurality of SM-DP entities, the identity of the at least one SM-SR entity and the identity of the eUICC. 14. The node of claim 12 , further being configured to, when creating the association: create an association between the identity of the at least one SM-DP entity, the identities of a plurality of SM-SR entities and the identity of the eUICC, wherein the plurality of SM-SR entities comprise a first SM-SR entity and a second SM-SR entity, different from the first SM-SR entity. 15. The node of claim 12 , the eUICC comprising a plurality of subscription profiles, and the node further configured to, when creating the association: create an association between the identities of a plurality of SM-DP entities, the identity of a single SM-SR entity and the identity of the eUICC, where the identity of each of the plurality of SM-DP entities is associated with a corresponding subscription profile among the plurality of subscription profiles. 16. The node of claim 12 , further configured to, when acquiring an identity of at least one SM-SR entity: request the identity of the at least one SM-SR entity, the identity being provided in an eUICC data file. 17. The node of claim 16 , further configured to make the request to an Embedded UICC Manufacturer, EUM, of the eUICC or an SM-SR entity for which the identity is requested. 18. The node of claim 12 , further configured to, when acquiring an identity of at least one SM-DP entity: request the identity of the at least one SM-DP entity, the at least one SM-DP identity being provided in a subscription profile data file. 19. The node of claim 18 , further configured to make the request to an SM-DP entity for which the identity is requested. 20. The node of claim 12 , wherein the identities are configured to designate a destination address of the respective SM-SR and SM-DP entities. 21. The node according to claim 20 , wherein the destination address is an Internet Protocol, IP, address. 22. The node of claim 12 , further configured to store the created association in a memory of the node and/or on the eUICC of the device.
involving the use of external additional devices, e.g. dongles or smart cards · CPC title
Transfer of user or subscriber data · CPC title
using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234) · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
Processing at user equipment or user record carrier · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.