Methods for UE-to-UE relay reselection security and privacy
US-12156274-B1 · Nov 26, 2024 · US
US9232392B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9232392-B2 |
| Application number | US-201414292256-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 30, 2014 |
| Priority date | May 30, 2013 |
| Publication date | Jan 5, 2016 |
| Grant date | Jan 5, 2016 |
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 and apparatus for setting profiles are provided. The profile setting method Includes receiving, from a first terminal, a profile transfer request message that requests transfer of a first profile or portion thereof from a first secure element to a second secure element; sending, to the first terminal, a request message requesting the first profile or portion thereof; receiving, from the first terminal, the first profile or portion thereof; configuring a second profile using the received first profile or portion thereof; and sending, to a second terminal, the configured second profile.
Opening claim text (preview).
What is claimed is: 1. A method of setting profiles for a profile server, the method comprising: receiving, from a first terminal, a profile transfer request message that requests transfer of a first profile or portion thereof from a first secure element to a second secure element; sending, to the first terminal, a request message requesting the first profile or portion thereof; receiving, from the first terminal, the first profile or portion thereof; configuring a second profile using the received first profile or portion thereof; and sending, to a second terminal, the configured second profile. 2. The method of claim 1 , further comprising: sending, if the second profile is successfully installed in the second secure element, a message requesting update of a security value related to the second profile to an authentication center (AuC). 3. The method of claim 1 , wherein the first profile or portion thereof is encrypted and transmitted using a public key of the profile sever. 4. The method of claim 1 , wherein the profile server includes at least one of a profile manager server and a profile provider server. 5. The method of claim 1 , wherein the profile transfer request message includes at least one of an identifier of the first terminal, an identifier of the second terminal, a profile identifier, a Mobile Subscriber Integrated Services Digital Network-Number (MSISDN, phone number), and an International Mobile Subscriber Identity (IMSI). 6. A profile server, comprising: a communication unit configured to receive, from a first terminal, a profile transfer request message that requests transfer of a first profile or portion thereof from a first secure element to a second secure element, to send, to the first terminal, a request message requesting the first profile or a portion thereof, and to receive, from the first terminal, the first profile or a portion thereof; and a controller configured to configure a second profile using the received the first profile or portion thereof and to control sending, to a second terminal, the configured second profile. 7. The profile server of claim 6 , wherein the communication unit sends, if the second profile is successfully installed in the second secure element, a message requesting update of a security value related to the second profile to an authentication center (AuC). 8. The profile server of claim 6 , wherein the first profile or portion thereof is encrypted and transmitted using a public key of the profile sever. 9. The profile server of claim 6 , further comprising at least one of a profile manager server and a profile provider server. 10. The profile server of claim 6 , wherein the profile transfer request message includes at least one of an identifier of the first terminal, an identifier of the second terminal, a profile identifier, an MSISDN, phone number, and an IMSI. 11. A method of setting profiles for a terminal, the method comprising: sending, to a profile sever, a profile transfer request message that requests transfer of a first profile or portion thereof from a first secure element to a second secure element; receiving, from the profile server, a request message requesting the first profile or a portion thereof; and sending, to the profile sever, the first profile or a portion thereof, wherein a second profile for the second secure element is configured using the first profile or a portion thereof. 12. The method of claim 11 , further comprising: encrypting the first profile or a portion thereof using a public key of the profile sever. 13. The method of claim 11 , wherein the profile transfer request message includes at least one of an identifier of a first terminal, an identifier of a second terminal, a profile identifier, an MSISDN, phone number, and an IMSI. 14. A terminal, comprising: a communication unit configured to send, to a profile sever, a profile transfer request message that requests transfer of a first profile or a portion thereof from a first secure element to a second secure element and to receive, from the profile server, a request message requesting the first profile or a portion thereof; and a controller configured to control sending, to the profile sever, the first profile or a portion thereof, wherein a second profile for the second secure element is configured using the received first profile or portion thereof. 15. The terminal of claim 14 , wherein the controller encrypts the first profile or portion thereof using a public key of the profile sever.
for initial activation of new user · CPC title
Integrity · CPC title
Processing at user equipment or user record carrier · CPC title
Authentication, i.e. establishing the identity or authorisation of security principals · CPC title
Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.