Profile Download Method and System, and Related Device
US-2019327605-A1 · Oct 24, 2019 · US
US12418785B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12418785-B2 |
| Application number | US-202418633368-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 11, 2024 |
| Priority date | Aug 26, 2020 |
| Publication date | Sep 16, 2025 |
| Grant date | Sep 16, 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.
The disclosure relates to a communication technique for combining an IoT technology with a 5G communication system for supporting a higher data transmission rate than that of a beyond-4G system, and a system therefor. The disclosure may be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, health care, digital education, retail businesses, security and safety related services, and the like) based on 5G communication technologies and IoT-related technologies. The disclosure provides a method and apparatus for recovering a profile in the case of a profile movement failure during a movement of a profile between smart security media.
Opening claim text (preview).
What is claimed is: 1. A method performed by a server in a communication system, the method comprising: receiving, from a first device including a first profile, a device change request for installing a second profile corresponding to the first profile onto a second device; transmitting, to the first device, a device change response instructing to delete the first profile, as a response to the device change request, the device change response including an indication indicating support of a profile recovery; and receiving, from the first device, a recovery request for recovery of the first profile deleted from an embedded universal integrated circuit card (eUICC) of the first device, the recovery request including information for the deleted first profile; and transmitting, to the first device, a recovery response for the recovery request. 2. The method of claim 1 , further comprising: identifying that there was a permanent error in profile installation on the second device, wherein the recovery response is transmitted to the first device based on the identification. 3. The method of claim 2 , wherein an error except for a temporary error is determined as the permanent error, wherein the temporary error includes insufficient memory for the second profile and interruption in the profile installation, and wherein the information for the deleted first profile includes an integrated circuit card identity (ICCID) of the deleted first profile. 4. The method of claim 1 , further comprising: transmitting, to the first device, a profile corresponding to the deleted first profile based on an activation code for the profile recovery, wherein the activation code for the profile recovery is included in the recovery response. 5. The method of claim 1 , further comprising: receiving, from the second device, information on a profile installation result for the second profile corresponding to the first profile. 6. The method of claim 1 , further comprising: performing a mutual authentication procedure with the first device, wherein the recovery request is received after performing the mutual authentication procedure. 7. The method of claim 1 , wherein an address of the server has been stored in the first device, and wherein the server is a subscription manager data preparation plus (SM-DP+). 8. A server in a communication system, the server comprising: a transceiver; and a controller configured to: receive, from a first device including a first profile via the transceiver, a device change request for installing a second profile corresponding to the first profile onto a second device, transmit, to the first device via the transceiver, a device change response instructing to delete the first profile, as a response to the device change request, the device change response including an indication indicating support of a profile recovery, receive, from the first device via the transceiver, a recovery request for recovery of the first profile deleted from an embedded universal integrated circuit card (eUICC) of the first device, the recovery request including information for the deleted first profile, and transmit, to the first device via the transceiver, a recovery response for the recovery request. 9. The server of claim 8 , wherein the controller is further configured to: identify that there was a permanent error in profile installation on the second device; and wherein the recovery response is transmitted to the first device based on the identification. 10. The server of claim 9 , wherein an error except for a temporary error is determined as the permanent error, wherein the temporary error includes insufficient memory for the second profile and interruption in the profile installation, and wherein the information for the deleted first profile includes an integrated circuit card identity (ICCID) of the deleted first profile. 11. The server of claim 8 , wherein the controller is further configured to transmit, to the first device via the transceiver, a profile corresponding to the deleted first profile based on an activation code for the profile recovery, and wherein the activation code for the profile recovery is included in the recovery response. 12. The server of claim 8 , wherein the controller is further configured to receive, from the second device via the transceiver, information on a profile installation result for the second profile corresponding to the first profile. 13. The server of claim 8 , wherein the controller is further configured to perform a mutual authentication procedure with the first device, and wherein the recovery request is received after performing the mutual authentication procedure. 14. The server of claim 8 , wherein an address of the server has been stored in the first device, and wherein the server is a subscription manager data preparation plus (SM-DP+).
Terminal profiles · CPC title
for initial configuration or provisioning, e.g. plug-and-play · CPC title
User profiles · CPC title
Network data restoration; {Network data reliability; Network data fault tolerance} · 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.