Profile deletion codes in subscription management systems
US-2017280320-A1 · Sep 28, 2017 · US
US12369019B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12369019-B2 |
| Application number | US-202418668849-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 20, 2024 |
| Priority date | Aug 7, 2018 |
| Publication date | Jul 22, 2025 |
| Grant date | Jul 22, 2025 |
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.
A method, performed by a user equipment (UE), of controlling a profile is provided. The method includes receiving a remote profile management command regarding a target profile from a profile server, determining whether an enabled profile exists, verifying whether profile owner information of the target profile corresponds to profile owner information or sub-owner information of the enabled profile, based a result of the determination, and selectively executing the remote profile management command based on a result of the verification.
Opening claim text (preview).
What is claimed is: 1. A method performed by a device, the method comprising: receiving a remote profile management command for enabling a target profile from a profile server; determining whether an enabled profile exists in the device, based on the remote profile management command being received; verifying whether information of a profile owner of the target profile is included in profile owner associated information of the enabled profile, in case that the enabled profile exists in the device, wherein the profile owner associated information comprises information of a profile owner of the enabled profile and information of an entity capable of implicitly disabling the enabled profile; and disabling the enabled profile and enabling the target profile, in case that the information of the profile owner of the target profile is included in the profile owner associated information of the enabled profile. 2. The method of claim 1 , wherein the profile owner includes at least one of a service provider or an operator. 3. The method of claim 1 , wherein in case that the information of the profile owner of the target profile is not included in the profile owner associated information of the enabled profile, the enabled profile is not capable of being implicitly disabled. 4. The method of claim 1 , wherein the disabling of the enabled profile comprises: disabling the enabled profile; or marking the enabled profile as to be disabled and disabling the enabled profile after performing an operation. 5. The method of claim 4 , wherein the operation comprises a refresh operation or a reset operation. 6. The method of claim 1 , wherein the enabling of the target profile comprises: enabling the target profile; or marking the target profile as to be enabled and enabling the target profile after performing an operation. 7. The method of claim 6 , wherein the operation comprises a refresh operation or a reset operation. 8. The method of claim 1 , further comprising: rejecting the remote profile management command in case that the information of the profile owner of the target profile is not included in the profile owner associated information of the enabled profile. 9. The method of claim 8 , further comprising: generating an error code indicating profile owner information mismatch. 10. A device comprising: a transceiver; and at least one processor coupled with the transceiver and configured to: receive a remote profile management command for enabling a target profile from a profile server, determine whether an enabled profile exists in the device, based on the remote profile management command being received, verify whether information of a profile owner of the target profile is included in profile owner associated information of the enabled profile, in case that the enabled profile exists in the device, wherein the profile owner associated information comprises information of a profile owner of the enabled profile and information of an entity capable of implicitly disabling the enabled profile, and disable the enabled profile and enable the target profile, in case that the information of the profile owner of the target profile is included in the profile owner associated information of the enabled profile. 11. The device of claim 10 , wherein the profile owner includes at least one of a service provider or an operator. 12. The device of claim 10 , wherein in case that the information of the profile owner of the target profile is not included in the profile owner associated information of the enabled profile, the enabled profile is not capable of being implicitly disabled. 13. The device of claim 10 , wherein the at least one processor is further configured to: disable the enabled profile, or mark the enabled profile as to be disabled and disable the enabled profile after performing an operation. 14. The device of claim 13 , wherein the operation comprises a refresh operation or a reset operation. 15. The device of claim 10 , wherein the at least one processor is further configured to: enable the target profile, or mark the target profile as to be enabled and enable the target profile after performing an operation. 16. The device of claim 15 , wherein the operation comprises a refresh operation or a reset operation. 17. The device of claim 10 , wherein the at least one processor is further configured to: reject the remote profile management command in case that the information of the profile owner of the target profile is not included in the profile owner associated information of the enabled profile. 18. The device of claim 17 , wherein the at least one processor is further configured to: generate an error code indicating profile owner information mismatch.
using certificates or pre-shared keys · CPC title
Key generation or derivation · CPC title
Terminal profiles · CPC title
using revocation of authorisation · CPC title
Protecting application or service provisioning, e.g. securing SIM application provisioning · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.