Profile download method and device
This application relates to the field of communications technologies, and in particular, to a profile download technology. In a profile download method, a primary device obtains an embedded integrated circuit card identifier (EID) of a secondary device, where the EID is used by the primary device to obtain, from a mobile operator server, profile download information that matches the EID; receives the profile download information from the mobile operator server; and sends the profile download information to the secondary device, where the profile download information is used by the secondary device to download a profile from a profile management server, and the profile is installed in an embedded UICC (eUICC) of the secondary device after the download is complete.
1. A system, comprising:
a first device; and
a second device,
wherein the first device is configured to:
obtain an embedded universal integrated circuit card (eUICC) identifier (EID) of the second device;
send a first message to a mobile operator network indicating a profile download request, wherein the first message comprises the EID of the second device;
receive a profile associated with the EID from the mobile operator network; and
send the profile to the second device;
wherein the second device is configured to:
install the profile in an eUICC of the second device, wherein a mobile subscriber integrated services digital network number (MSISDN) of the first device is shared by the second device; and,
wherein the first device is further configured to:
send a unbinding request to the mobile operator network for unbinding a multiple devices single MSISDN service binding relationship between the first device and the second device; and
receive a unbinding operation result from the mobile operator network; and
send the unbinding operation result to the second device; and
wherein the second device is further configured to:
delete the profile in the eUICC of the second device in response to receiving the unbinding operation result.
2. The system of claim 1 , wherein obtaining the EID of the second device comprises: obtaining the EID of the eUICC of the second device via a Bluetooth connection with the second device.
3. The system of claim 1 , wherein the first message further comprises an identifier of the first device, the identifier of the first device comprises any one of an integrated circuit card identify (ICCID), a MSISDN, or an international mobile subscriber identity (IMSI).
4. The system of claim 1 , wherein the first device is further configured to:
display a web page comprising contract information;
receive a user input for approving a service term of the contract information.
5. The system of claim 1 , wherein receiving the profile associated with the EID comprises receiving the profile associated with the EID from a profile management server.
6. The system of claim 1 , wherein the unbinding request comprises a first identifier of the first device and a second identifier of the second device.
7. The system of claim 1 , wherein the first device is further configured to:
perform an authentication process with the mobile operator network;
obtain authentication success information from the mobile operator network, wherein the authentication process comprises an Extensible Authentication Protocol-Authentication and Key Agreement (EAP-AKA) authentication process.
8. The system of claim 5 , wherein the deleting the profile in the eUICC of the second device comprises:
sending a profile release request to the profile management server;
receiving a profile release result from the profile management server; and
deleting the profile in the eUICC of the second device in response to the profile release result.
9. A first device, comprising:
a universal integrated circuit card (UICC);
at least one processor; and
a memory coupled to the at least one processor and storing programming instructions that, when executed by the at least one processor, cause the first device to:
obtain an embedded universal integrated circuit card (eUICC) identifier (EID) of a second device;
send a first message to a mobile operator network indicating a profile download request, wherein the first message comprises the EID of the second device;
receive a profile associated with the EID from the mobile operator network; and
send the profile to the second device, wherein the profile is installed in an eUICC of the second device, wherein a mobile subscriber integrated services digital network number (MSISDN) of the first device is shared by the second device;
send a unbinding request to the mobile operator network for unbinding a multiple devices single MSISDN service binding relationship between the first device and the second device;
receive a unbinding operation result from the mobile operator network; and
send the unbinding operation result to the second device for deleting the profile in the eUICC of the second device.
10. The first device of claim 9 , wherein obtaining the EID of the second device comprises: obtaining the EID of the eUICC of the second device via a Bluetooth connection with the second device.
11. The first device of claim 9 , wherein the first message further comprises an identifier of the first device, the identifier of the first device comprises any one of an integrated circuit card identify (ICCID), MSISDN, or an international mobile subscriber identity (IMSI).
12. The first device of claim 9 , wherein the memory further stores programming instructions that, when executed by the at least one processor, cause the first device to:
display a web page comprising contract information;
receive a user input for approving a service term of the contract information.
13. The first device of claim 9 , wherein the profile download information comprises an address of the profile management server.
14. The first device of claim 9 , wherein the unbinding request comprises a first identifier of the first device and a second identifier of the second device.
15. The first device of claim 9 , wherein the memory further stores programming instructions that, when executed by the at least one processor, cause the first device to:
perform an authentication process with the mobile operator network;
obtain authentication success information from the mobile operator network.
16. The first device of claim 15 , wherein the authentication process is an Extensible Authentication Protocol-Authentication and Key Agreement (EAP−AKA) authentication process.
17. A first device, comprising:
at least one processor; and
a memory coupled to the at least one processor and storing programming instructions that, when executed by the at least one processor, cause the first device to:
obtain an embedded universal integrated circuit card identifier (EID) of a second device;
send a first message to a mobile operator network indicating a profile download request, wherein the first message comprises the EID of the second device;
receive an activation code associated with the EID from the mobile operator network;
send the activation code to the second device for downloading a profile from a profile management server to the second device, wherein a mobile subscriber integrated services digital network number (MSISDN) of the first device is shared by the second device;
send a unbinding request to the mobile operator network for unbinding a multiple devices single MSISDN service binding relationship between the terminal and the second device;
receive a unbinding operation result from the mobile operator network; and
send the unbinding operation result to the second device for deleting the profile in the eUICC of the second device.
18. The first device of claim 17 , wherein the first message further comprises an identifier of the terminal, the identifier of the terminal comprises any one of an integrated circuit card identify (ICCID), a mobile subscriber ISDN number (MSISDN), or an international mobile subscriber identity (IMSI).
19. The first device of claim 17 , wherein the memory further stores programming instructions that, when executed by the at least one processor, cause the first device to:
display a web page comprising contract information;
receive a user input for approving a service term of the contract information.
20. The first device of claim 17 , wherein the memory further stores programming instructions that, when executed by the at least one processor, cause the first device to:
receive a profile from a profile management server
perform an authentication process with the mobile operator network;
obtain authentication success information from the mobile operator network.