WO2011153714A1 - 支持多imsi的方法、装置和系统 - Google Patents

支持多imsi的方法、装置和系统 Download PDF

Info

Publication number
WO2011153714A1
WO2011153714A1 PCT/CN2010/073885 CN2010073885W WO2011153714A1 WO 2011153714 A1 WO2011153714 A1 WO 2011153714A1 CN 2010073885 W CN2010073885 W CN 2010073885W WO 2011153714 A1 WO2011153714 A1 WO 2011153714A1
Authority
WO
WIPO (PCT)
Prior art keywords
imsi
request message
smart card
information
update request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2010/073885
Other languages
English (en)
French (fr)
Inventor
石介平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Device Co Ltd
Original Assignee
Huawei Device Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to EP10852707.8A priority Critical patent/EP2538746B1/en
Priority to ES21186553T priority patent/ES2951581T3/es
Priority to EP19205832.9A priority patent/EP3668133B1/en
Priority to ES19205832T priority patent/ES2898304T3/es
Priority to PCT/CN2010/073885 priority patent/WO2011153714A1/zh
Priority to EP23166700.7A priority patent/EP4277237A3/en
Priority to EP21186553.0A priority patent/EP3962130B1/en
Priority to JP2013502984A priority patent/JP2013527656A/ja
Application filed by Huawei Device Co Ltd filed Critical Huawei Device Co Ltd
Priority to CN201080055036.XA priority patent/CN102668689B/zh
Publication of WO2011153714A1 publication Critical patent/WO2011153714A1/zh
Priority to US13/693,419 priority patent/US8718711B2/en
Anticipated expiration legal-status Critical
Priority to US17/405,904 priority patent/USRE49635E1/en
Priority to US18/235,723 priority patent/USRE50578E1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/654—International mobile subscriber identity [IMSI] numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity

Definitions

  • the present invention relates to the field of network communication technologies, and in particular to technologies supporting multiple IMSIs.
  • a smart card can be pre-set with multiple International Mobile Subscriber Identity (International Mobile Subscriber Identity, IMSI), that is, the user has opened multiple accounts. The user can select one of the multiple IMSIs to use as needed.
  • IMSI International Mobile Subscriber Identity
  • the above smart card can be Subscriber Identity Module (SIM) card, etc.
  • the inventor has found that the IMSI set in the existing smart card is relatively fixed, that is, after the IMSI is preset in the smart card, the IMSI in the smart card cannot be changed, and multiple IMSIs in the smart card only Can be used by one user, so that one user must occupy multiple IMSIs, resulting in low utilization of IMSI, resulting in waste of IMSI resources.
  • the method, device and system for supporting multiple IMSIs provided by the embodiments of the present invention can dynamically update the IMSI in the smart card, thereby avoiding the phenomenon that one user must always occupy multiple IMSIs, improving the utilization of the IMSI, and saving the IMSI resources.
  • the IMSI management operation includes: allocating a new IMSI and authentication data to the user terminal when the IMSI update request message includes an application IMSI request message, and/or, in the IMSI update request message, including deleting an IMSI request When the message is received, the IMSI is recovered according to the deleted IMSI request message.
  • a first receiving module configured to receive a response message returned by the server transmitted by the user terminal for the IMSI update request message
  • an update module configured to perform a smart card IMSI update operation according to the information carried by the response message, where the smart card is a smart card supporting multiple IMSI, the smart card IMSI update operation includes: adding an IMSI operation to the smart card and/or deleting from the smart card IMSI operation.
  • the user terminal provided by the embodiment of the present invention includes: a control module and a device supporting multiple IMSIs;
  • the control module is configured to send an IMSI update request message to the server, and after receiving the response message returned by the server for the IMSI update request message, send the response message to the device supporting the multiple IMSI; where the IMSI update request message includes: Applying for an IMSI request message and/or deleting an IMSI request message;
  • the apparatus for supporting multiple IMSIs is configured to receive a response message sent by the control module, and perform a smart card IMSI update operation according to the information carried in the response message, where the smart card is a smart card supporting multiple IMSIs, and the smart card IMSI update operation includes: Add IMSI operations to the smart card and/or remove IMSI operations from the smart card.
  • a second receiving module configured to receive an IMSI update request message sent by the user terminal
  • a management module configured to perform an IMSI management operation according to the IMSI update request message
  • a second sending module configured to return a response message to the user terminal according to the IMSI management operation execution result
  • the IMSI management operation includes: when the IMSI update request message includes an application IMSI request message, the management module allocates a new IMSI and authentication data to the user terminal, and/or, in the IMSI update request message When the IMSI request message is deleted, the management module reclaims the IMSI according to the delete IMSI request message.
  • the system for supporting multiple IMSIs provided by the embodiments of the present invention includes: the foregoing server and at least one of the foregoing user terminals.
  • Transmitting the response message to the smart card so that the smart card performs a smart card IMSI update operation according to the information carried by the response message; wherein the smart card is a smart card supporting multiple IMSI, and the smart card IMSI update operation includes: in a smart card Add IMSI operations and/or remove IMSI operations from the smart card.
  • the embodiment sends an IMSI update request message to the server, such as applying for an IMSI request message or deleting an IMSI request message, so that the server can return a corresponding response message to the user terminal according to the IMSI update request message, so that The IMSI operation may be performed in the smart card according to the response message returned by the server transmitted by the user terminal, or the IMSI operation may be deleted from the smart card, so that the IMSI in the smart card may be dynamically updated, so that the user terminal can dynamically occupy the IMSI, thereby avoiding one user.
  • the phenomenon of multiple IMSIs must be occupied at all times, the utilization of IMSI is improved, and IMSI resources are saved.
  • FIG. 1 is a flowchart of a method for supporting multiple IMSIs according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for supporting multiple IMSIs according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a method for supporting multiple IMSIs according to Embodiment 3 of the present invention.
  • FIG. 4 is a flowchart of a method for supporting multiple IMSIs according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic diagram of an apparatus supporting multiple IMSIs according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic diagram of a user terminal according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic diagram of a server according to Embodiment 7 of the present invention.
  • FIG. 8 is a schematic diagram of a system supporting multiple IMSIs according to Embodiment 8 of the present invention.
  • Embodiment 9 is a flow chart of a method for supporting multiple IMSIs according to Embodiment 9 of the present invention.
  • Embodiment 1 A method of supporting multiple IMSIs. The flow of the method is shown in Figure 1.
  • the flow in FIG. 1 includes S100, S110, S120, and S130, wherein S100 and S110 are optional steps, that is, Embodiment 1 may include only S120 and S130 shown in FIG. 1.
  • the IMSI update command may be a command transmitted by the user terminal, and the user terminal may generate an IMSI update command after receiving the externally requested request IMSI update information, and transmit the IMSI update command to the executor of S100.
  • the request IMSI update information received by the user terminal may indicate that the user needs to apply for a new IMSI or the user needs to delete an IMSI or the like.
  • the IMSI update command generated by the user terminal according to the request IMSI update information may also indicate that the user needs to apply for a new IMSI or the user needs to delete an IMSI or the like.
  • the above IMSI update command may be an IMSI update command based on an envelope command, that is, the IMSI update command takes the form of an envelope command.
  • the foregoing IMSI update command may also adopt other forms of commands than the envelope command. This embodiment does not limit the protocol type specifically adopted by the IMSI update command and the specific format of the command.
  • the IMSI update request message here may be an application IMSI request message or a delete IMSI request message.
  • the application IMSI request message is used to apply for a new IMSI for the user terminal, and the delete IMSI request message is used to cancel an IMSI that the user terminal has occupied.
  • the deleted IMSI request message may carry IMSI information that needs to be deleted, such as IMSI and authentication data.
  • the authentication data here is the authentication data corresponding to the IMSI.
  • the foregoing IMSI update request information may be sent to the user terminal in the form of an envelope command, or may be in other forms than the envelope command. This embodiment does not limit the protocol type and specific format used by the IMSI update request information.
  • the executor of S110 may encrypt the IMSI update request information and transmit the encrypted information to the user terminal.
  • the executive body of S110 may also transmit the information for security authentication and the encrypted information to the user terminal.
  • the information included in the security authentication may be set according to the specific form of the actual security authentication.
  • the information for the security authentication includes the smart card identity information, etc., and the specific implementation manner of the security authentication is not limited in this embodiment.
  • the above IMSI update request message can be passed through Over The The form of Air (over the air, OTA) short message is sent by the user terminal to the server.
  • OTA over the air
  • the IMSI update request message may also be sent to the server in other forms than the OTA short message, for example, through Bearer.
  • Independent Protocol Bearer Independent Protocol, BIP
  • BIP Backbone Independent Protocol
  • S100 and S110 described above describe the process in which the user terminal passively sends an IMSI update request message to the server according to the trigger.
  • the user terminal may also actively send an IMSI update request message to the server.
  • This embodiment does not limit the specific implementation manner in which the user terminal sends an IMSI update request message to the server.
  • the server that receives the user terminal transmission returns a response message for the received IMSI update request message.
  • the user terminal may transmit the response message to the S120 execution entity by using the protocol between the user terminal and the S120 execution entity.
  • the response message returned by the server may carry information for performing an IMSI operation in the smart card, such as a new IMSI allocated to the user terminal and authentication data corresponding to the IMSI; the response message may also be carried in the response message.
  • the information of the IMSI operation is deleted in the smart card, such as the deletion of the information (ie, the recovery success information), and the like, and the information used to perform the IMSI operation for deleting the IMSI may include: the IMSI to be deleted, or the IMSI to be deleted. Authentication data corresponding to the IMSI, and the like.
  • the user terminal may transmit the response message returned by the server to the execution body of S120 through the response message based on the envelope command.
  • This embodiment does not limit the protocol type specifically used by the response message transmitted by the user terminal to the executor of the S120, and the specific command format of the response message.
  • the smart card IMSI update operation described above may include at least one of adding an IMSI operation to the smart card and deleting the IMSI operation from the smart card. It should be noted that adding an IMSI operation in the smart card includes: adding an IMSI and an authentication data corresponding to the IMSI in the smart card. Deleting the IMSI operation from the smart card includes deleting the IMSI and the authentication data corresponding to the IMSI from the smart card. The same is true for the IMSI operation and the deletion IMSI operation described in the following embodiments, and will not be described one by one.
  • the executing entity may perform security authentication on the received response message according to the information carried in the response message, for example, using the server identity information carried in the response message to perform security authentication on the response message. After the security authentication is passed, the execution entity performs the smart card IMSI update operation according to the information carried in the response message. If the response message sent by the server is a response message that is subjected to the encryption process, the execution body of the S130 needs to decrypt the received response message after the security authentication is passed, and perform the smart card IMSI update operation according to the information obtained after the decryption. .
  • the execution body of the S130 can determine whether the information obtained after the decryption is complete and legal, and after determining that the complete legality is performed, perform the smart card IMSI update operation according to the information obtained after the decryption; after determining that the integrity is legal, The smart card IMSI update operation is no longer performed.
  • the information carried in the response message may include: a response command type indicating a new IMSI application, a newly applied IMSI (ie, a new IMSI allocated for the user terminal), and authentication data.
  • the information carried in the response message may also include: a response command type indicating that the IMSI is deleted, and a recovery success information.
  • the IMSI and the authentication data that need to be deleted may also be included.
  • the executor of S130 may add the IMSI and the authentication data of the new application in the response message to the smart card according to the response command type of applying for the new IMSI.
  • the executor of the S130 may also determine an IMSI that the user needs to delete according to the IMSI update command corresponding to the response message according to the type of the response command for deleting the IMSI, and delete the IMSI and the authentication data corresponding to the IMSI from the smart card.
  • the executor of the S130 may delete the IMSI carried in the response message and the authentication data corresponding to the IMSI from the smart card.
  • the executor of the S130 may output an execution status of the smart card IMSI update operation, so that the user can know whether the new IMSI is successfully applied, or whether the IMSI is successfully deleted.
  • the smart card is a smart card that is set independently of the user terminal, and in some cases, the smart card can also be solidified in the user terminal.
  • the smart card in this embodiment can be set independently of the user terminal.
  • the smart card can also be a smart card that is solidified in the user terminal.
  • the execution body in this embodiment may be disposed in the smart card, or may be set independently of the smart card. This embodiment does not limit the specific existence manner of the smart card and the execution subject.
  • the user terminal is triggered to send an IMSI update request message to the server, such as applying for an IMSI request message or deleting an IMSI request message, by sending an IMSI update request message to the user terminal, so that the server can update the request message according to the IMSI.
  • the user terminal returns a corresponding response message, so that the IMSI operation can be added to the smart card or the IMSI operation can be deleted from the smart card according to the response message received by the user terminal, so that the IMSI in the smart card can be dynamically updated, so that the user terminal can dynamically
  • the IMSI is occupied, thereby avoiding the phenomenon that one user must always occupy multiple IMSIs; the security authentication and decryption operations of the response message received by the user terminal ensure the security of the smart card IMSI update operation.
  • the first embodiment improves the IMSI utilization rate and saves IMSI resources.
  • Embodiment 2 A method of supporting multiple IMSIs. The flow of the method is shown in Figure 2.
  • S200 receives an IMSI update request message sent by a user terminal.
  • the IMSI update request message here may be an application IMSI request message or a delete IMSI request message.
  • the IMSI update request message received by the S200 may be in the form of an OTA short message or other forms.
  • the IMSI management operation herein may be: assigning a new IMSI and authentication data to the user terminal when the IMSI update request message is an application IMSI request message; the IMSI management operation may also be: deleting the IMSI request message in the IMSI update request message. At the time, the IMSI is recovered according to the delete IMSI request message. The IMSI is reclaimed, such as the binding relationship between the authentication data corresponding to the IMSI and the IMSI and the user terminal.
  • the security authentication may be performed according to the information carried in the IMSI update request message, for example, the IMSI update request message is authenticated by using the smart card identity information carried in the IMSI update request message. If the security authentication passes, the IMSI management operation is performed according to the received IMSI update request message, and if the security authentication fails (ie, fails), the IMSI management operation is not performed. In this embodiment, the security authentication is performed on the IMSI update request message by using the existing security authentication mode. This embodiment does not limit the specific implementation process of the security authentication.
  • the executor of S210 may perform decryption processing on the information carried in the IMSI update request message, and then perform an IMSI management operation according to the decrypted information. For example, after the security authentication is passed, the information carried in the IMSI update request message is decrypted, and the IMSI management operation is performed according to the decrypted information.
  • This embodiment does not limit the specific implementation process of the decryption process.
  • the response message herein carries information for performing a smart card IMSI update operation
  • the smart card IMSI update operation may include: adding at least one of an IMSI operation and an IMSI operation from the smart card in the smart card.
  • the executor of S220 may carry the new IMSI and the authentication data allocated for the user terminal in the response message, And returning the response message to the user terminal.
  • the executor of S220 may allow deletion of information (ie, recovery success information) or prohibition of deletion of information (ie, recovery failure information) Carrying in the response message and returning the response message to the user terminal.
  • the above response message may be sent to the user terminal in the form of an OTA short message.
  • the response message may also be sent to the user terminal in other forms than the OTA short message, for example, sending a response message to the user terminal through the BIP.
  • This embodiment does not limit the type of the protocol specifically used by the response message, the specific command format of the response message, and the like.
  • the executor of the S220 may perform encryption processing on the information that needs to be carried in the response message, carry the encrypted information in the response message, and return a response message carrying the encrypted information to the user terminal.
  • the allocated new IMSI and the authentication data corresponding to the IMSI are encrypted, and then the encrypted IMSI and the authentication data are carried in the response message and sent to the user terminal.
  • the information is allowed to be deleted or the information is prohibited from being deleted, and the encrypted information is carried in the response message and sent to the user terminal. This embodiment does not limit the specific implementation process of encryption.
  • Embodiment 3 A method of supporting multiple IMSIs. The flow of the method is shown in Figure 3.
  • S300 user through UE STK (User Equipment SIM Toolkit, User Equipment Smart Card Tool Set)
  • the application requests to increase the IMSI, such as the user adding IMSI request information through the UE STK input to request to increase the local IMSI in a certain area.
  • the UE After receiving the IMSI request information, the UE invokes an envelope command (such as menu selection MENU).
  • the Select command sends an IMSI update command to the SIM card to trigger the process of adding the IMSI.
  • the SIM card After receiving the IMSI update command, the SIM card sends an IMSI increase request security packet to the UE, to trigger the UE to send an OTA short message to the CAT server, that is, the server that manages and controls the SIM card file system through the air interface.
  • the IMSI Addition Request Security Packet includes information for security authentication and post-encryption information.
  • the UE After receiving the IMSI increase request security packet, the UE sends an OTA short message to the CAT server (that is, the IMSI increase request security packet is encapsulated in the OTA short message and sent to the CAT server) to request the CAT server to allocate a new IMSI to the user terminal. .
  • the CAT server After receiving the OTA short message, the CAT server performs security authentication on the IMSI request security packet in the OTA short message.
  • the CAT server sends the IMSI data security package to the user terminal.
  • the IMSI data security package carries the local IMSI of the local area newly allocated for the user terminal and the authentication data corresponding to the IMSI.
  • the newly allocated IMSI and the authentication data corresponding to the IMSI may be carried in the IMSI increase request security packet after being encrypted.
  • the IMSI Addition Request Security Packet may include information for security authentication and post-encryption information.
  • the IMSI data security packet is sent to the user terminal in the form of an OTA short message (ie, the IMSI data security packet is encapsulated in the OTA short message and sent to the user terminal).
  • the UE After receiving the IMSI data security packet in the form of an OTA short message transmitted by the CAT server, the UE does not perform an operation such as encryption and decryption processing on the IMSI data security packet in the OTA short message, and the IMSI data security package in the OTA short message.
  • Short Message Services point-to-point Download short message peer-to-peer download, SMS PP Download
  • the command is transmitted to the SIM card.
  • SIM card receives SMS PP After the Download command, the IMSI data security package in the command is authenticated, and after the security authentication is passed, the SIM card decrypts the IMSI data security packet. If it is determined that the decrypted information is complete and legal, the SIM card is stored. IMSI and authentication data obtained after decryption. If it is determined that the decrypted information is incomplete and legal, the SIM card does not perform an operation of storing the IMSI and the authentication data. After successfully adding a new IMSI, the SIM card sends a notification message to the UE that successfully adds a new IMSI. In addition, if the new IMSI is not successfully added, the SIM card should also send notification information to the UE that the new IMSI has not been successfully added.
  • the UE After receiving the notification information, the UE displays the notification information that the new IMSI is successfully added, so that the user is informed of the request to increase the execution result of the IMSI.
  • the UE will switch to the new IMSI request information and transmit the information to the SIM card, and the UE may invoke the MENU.
  • the Select command switches to the SIM card transmission to the new IMSI request information.
  • the SIM card executes the received MENU Select command, and the MENU
  • the Select command execution result information is transmitted to the UE through the Display Text command.
  • the UE displays the MENU in the Display Text command.
  • the Select command executes the result information to let the user know if the switch to the new IMSI is successful.
  • Embodiment 4 A method of supporting multiple IMSIs. The flow of the method is shown in Figure 4.
  • S400 the user requests to delete the IMSI through the UE STK application, such as the user passing the UE.
  • the STK input deletes the IMSI request message information to request the deletion of the local IMSI of a certain area.
  • the UE After receiving the information of deleting the IMSI request message, the UE invokes an envelope command (such as menu selection MENU).
  • the Select command sends an IMSI update command to the SIM card to trigger the process of deleting the IMSI.
  • the SIM card After receiving the IMSI update command, the SIM card sends an IMSI delete request security packet to the UE, to trigger the UE to send an OTA short message to the CAT server.
  • the IMSI deletion request security package includes: information for security authentication and post-encryption information.
  • the encrypted information includes: an IMSI to be deleted and authentication data corresponding to the IMSI.
  • the UE After receiving the IMSI deletion request security packet, the UE sends an OTA short message to the CAT server (that is, the IMSI deletion request security packet is encapsulated in the OTA short message and sent to the CAT server) to request the CAT server to delete the allocation that was once allocated to the user terminal. IMSI.
  • the S440 and the CAT server After receiving the OTA short message, the S440 and the CAT server perform security identification on the IMSI deletion request security packet in the OTA short message.
  • the CAT server decrypts the encrypted information carried in the IMSI data security package, obtains the IMSI and the authentication data that need to be deleted, and the CAT server recovers the IMSI according to the obtained IMSI and the authentication data, and then The CAT server sends an IMSI data security packet to the user terminal.
  • the IMSI data security package carries information for security authentication and encrypted information.
  • the encrypted information includes information obtained by encrypting the recovery success information.
  • the IMSI data security packet is sent to the user terminal in the form of an OTA short message (ie, the IMSI data security packet is encapsulated in the OTA short message and sent to the user terminal).
  • the UE After receiving the IMSI data security packet of the OTA short message transmitted by the CAT server, the UE does not perform an operation such as encryption and decryption processing on the IMSI data security packet in the OTA short message, and passes the IMSI data security packet in the OTA short message through the SMS.
  • the PP Download command is transmitted to the SIM card.
  • SIM card receives SMS PP After the Download command, the IMSI data security package in the command is authenticated, and after the security authentication is passed, the SIM card decrypts the IMSI data security packet. If it is determined that the decrypted information is complete and legal, the SIM card is based on The recovery success information obtained after decryption deletes the IMSI and authentication data stored in the SIM card that need to be deleted. If it is determined that the decrypted information is incomplete and legal, the SIM card does not perform the delete operation. After successfully deleting the IMSI, the SIM card sends a notification message for successfully deleting the IMSI to the UE. In addition, if the IMSI is not successfully deleted, the SIM card should also send notification information to the UE that the IMSI was not successfully deleted.
  • the UE After receiving the notification information, the UE displays the notification information of the IMSI that is successfully deleted, so that the user is informed of the request to delete the execution result of the IMSI.
  • the UE transmits the request information for switching to the specified IMSI to the SIM card, and the UE may invoke the MENU.
  • the Select command transfers the request information for switching to the specified IMSI to the SIM card.
  • SIM card executes the received MENU Select command, and MENU
  • the Select command execution result information is transmitted to the UE through the Display Text command.
  • the UE displays the MENU in the Display Text command.
  • the Select command executes the result information to let the user know whether to successfully switch to the specified IMSI.
  • Embodiment 5 A device supporting multiple IMSIs.
  • the device can be placed in a smart card (such as a SIM card) or it can be set independently of the smart card.
  • a smart card such as a SIM card
  • the structure of the device is shown in Figure 5.
  • the apparatus in FIG. 5 includes a first receiving module 500 and an updating module 520.
  • the device may further include: a first sending module 510.
  • the first receiving module 500 is configured to receive and receive a response message returned by the server transmitted by the user terminal for the IMSI update request message.
  • the first receiving module is further configured to receive an IMSI update command.
  • the IMSI update command received by the first receiving module 500 may be a command transmitted by the user terminal, and the user terminal may generate an IMSI update command after receiving the externally requested request IMSI update information, and transmit the IMSI update command to the device supporting multiple IMSIs. .
  • the request IMSI update information received by the user terminal may indicate that the user needs to apply for a new IMSI or the user needs to delete an IMSI or the like.
  • the IMSI update command generated by the user terminal according to the request IMSI update information may also indicate that the user needs to apply for a new IMSI or the user needs to delete an IMSI or the like.
  • the IMSI update command received by the first receiving module 500 may be an IMSI update command based on an envelope command.
  • the IMSI update command received by the first receiving module 500 may also use other forms of commands than the envelope command. This embodiment does not limit the protocol type and specific format of the command used by the IMSI update command.
  • the first sending module 510 is configured to send IMSI update request information to the user terminal according to the IMSI update command received by the first receiving module 500, to trigger the user terminal to send an IMSI update request message to the server according to the IMSI update request information.
  • the IMSI update request message here includes: requesting an IMSI request message or deleting an IMSI request message.
  • the IMSI update request message here may be an application IMSI request message or a delete IMSI request message.
  • the application IMSI request message is used to apply for a new IMSI for the user terminal, and the delete IMSI request message is used to delete an IMSI that the user terminal has occupied.
  • the deleted IMSI request message may carry IMSI information that needs to be deleted, such as IMSI and authentication data.
  • the authentication data here is the authentication data corresponding to the IMSI.
  • the first sending module 510 may send the IMSI update request information to the user terminal in the form of an envelope command, and the first sending module 510 may also send the IMSI update request information to the user terminal by using a command other than the envelope command.
  • the type of the protocol specifically used by the first sending module 500 to send the IMSI update request information, the specific format, and the like are not limited.
  • the first sending module 510 can include: a first sub-module 511 and a second sub-module 512.
  • the first submodule 511 is configured to determine the IMSI update request information according to the IMSI update command received by the first receiving module 500, and encrypt the IMSI update request information.
  • the second sub-module 512 is configured to transmit information obtained by encrypting the first sub-module 511 and information for security authentication to the user terminal.
  • the second sub-module 512 transmits the information obtained after the encryption and the information for the security authentication to the user terminal in the form of an envelope command.
  • the update module 520 is configured to perform a smart card IMSI update operation according to the information carried by the response message received by the first receiving module 500.
  • the smart card here is a smart card supporting multiple IMSIs, and the smart card IMSI update operation may be to add an IMSI operation to the smart card or to delete the IMSI operation from the smart card.
  • the update module 520 can output the execution status of the smart card IMSI update operation, so that the user can know whether the new IMSI is successfully applied, or whether the IMSI is successfully deleted.
  • the update module may include a third sub-module 521, a fourth sub-module 522, and a fifth sub-module 523.
  • the third sub-module 521 is configured to perform security authentication on the response message received by the first receiving module 500.
  • the third sub-module 521 performs security authentication on the response message by using the server identity information carried in the response message.
  • the fourth sub-module 522 is configured to decrypt the response message after the security authentication performed by the third sub-module 521 is passed.
  • the information obtained after decryption by the fourth sub-module 522 may include: new IMSI and authentication data allocated for the user terminal.
  • the information obtained after the fourth sub-module 522 is decrypted may also include: whether the recovery success information or the like. This embodiment does not limit the specific implementation process of the fourth sub-module 522 decrypting the response message.
  • the fifth sub-module 523 is configured to perform a smart card IMSI update operation according to the information obtained after the fourth sub-module 522 decrypts.
  • the fifth sub-module 523 can determine whether the information obtained after the decryption is complete and legal, and after determining that the complete legality, the fifth sub-module 523 performs the smart card IMSI update operation according to the information obtained after the decryption; After being fully legal, the fifth sub-module 523 may no longer perform the smart card IMSI update operation.
  • the fifth sub-module 523 can output the execution status of the smart card IMSI update operation, so that the user can know whether the new IMSI is successfully applied, or whether the IMSI is successfully deleted.
  • Embodiment 6 User terminal. The structure of the user terminal is as shown in FIG. 6.
  • the user terminal in FIG. 6 includes a control module 600 and a device 610 supporting multiple IMSIs.
  • the multi-IMSI-enabled device 610 herein can be a smart card (such as a SIM card) or can be independent of the smart card settings.
  • the control module 600 is configured to send an IMSI update request message to the server, and send the response message to the multi-IMSI-enabled device 610 after receiving the response message returned by the server for the IMSI update request message.
  • the IMSI update request message herein includes at least one of an application IMSI request message and a delete IMSI request message.
  • the control module 600 is further configured to send an IMSI update command to the multi-IMSI-enabled device 610 according to the received request IMSI update information, so that the multi-IMSI-enabled device 610 sends the IMSI update request information to the IMSI update request after receiving the IMSI update command, and
  • the IMSI update request message is sent to the server after receiving the IMSI update request information.
  • the control module 600 can also actively send an IMSI update request message to the server, that is, if the control module 600 does not receive the IMSI update request information sent by the device 610 supporting the multiple IMSI, the IMSI update request message is sent to the server.
  • the control module 600 can send an IMSI update request message to the server in the form of an OTA short message.
  • the control module 600 may also send an IMSI update request message to the server in other forms than the OTA short message.
  • the control module 600 sends an IMSI update request message to the server through the BIP. This embodiment does not limit the protocol type specifically used by the control module 600 to send the IMSI update request message, and the content specifically included in the IMSI update request message.
  • the control module 600 can transmit the response message to the multi-IMSI-enabled device 610 by using its protocol with the multi-IMSI-enabled device 610. For example, the control module 600 can transmit a response message returned by the server to the multi-IMSI-enabled device 610 through a response message based on the envelope command.
  • the response message returned by the server may carry information for performing an IMSI operation in the smart card, such as a new IMSI allocated by the server for the user terminal, and authentication data corresponding to the IMSI; the response message may also be carried in the response message.
  • the information of the IMSI operation is deleted from the smart card, such as the deletion of the information (ie, the recovery success information), and the like.
  • the information for performing the IMSI operation to be deleted from the smart card may include: the IMSI to be deleted, or the IMSI to be deleted. Authentication data and the like corresponding to the IMSI.
  • This embodiment does not limit the type of protocol specifically used by the control module 600 to transmit a response message to the device 610 supporting multiple IMSIs, and the specific command format of the response message.
  • the multi-IMSI-enabled device 610 is configured to receive a response message sent by the control module 600, and perform a smart card IMSI update operation according to the information carried in the response message.
  • the smart card here is a smart card supporting multiple IMSIs, where the smart card IMSI update operation includes at least one of adding an IMSI operation to the smart card and deleting the IMSI operation from the smart card.
  • the apparatus 610 supporting the multiple IMSI is further configured to receive the IMSI update command sent by the control module 600, and send the IMSI update request information to the control module 600 according to the IMSI update command.
  • Embodiment 7 Server. The structure of the server is as shown in FIG.
  • the server shown in FIG. 7 includes a second receiving module 700, a management module 710, and a second transmitting module 720.
  • the second receiving module 700 is configured to receive an IMSI update request message sent by the user terminal.
  • the IMSI update request message here may be an application IMSI request message or a delete IMSI request message.
  • the IMSI update request message received by the second receiving module 700 may be in the form of an OTA short message, or may be in other forms.
  • the management module 710 is configured to perform an IMSI management operation according to the IMSI update request message received by the second receiving module 700.
  • the IMSI management operation performed by the management module 710 includes: when the IMSI update request message includes an application IMSI request message, the management module 710 allocates a new IMSI and authentication data to the user terminal.
  • the management module 710 recovers the IMSI according to the delete IMSI request message, for example, the management module 710 releases the binding relationship between the IMSI to be deleted and the user terminal.
  • the management module 710 can include: a sixth sub-module 711, a seventh sub-module 712, and an eighth sub-module 713.
  • the sixth sub-module 711 is configured to perform security authentication on the IMSI update request message received by the second receiving module 700. For example, the sixth sub-module 711 performs security authentication on the IMSI update request message by using the smart card identity information carried in the IMSI update request message. The sixth sub-module 711 can perform security authentication on the IMSI update request message by using the existing security authentication mode. This embodiment does not limit the specific implementation process of the sixth sub-module 711 to perform security authentication.
  • the seventh sub-module 712 is configured to decrypt the IMSI update request message after the security authentication performed by the sixth sub-module 711 is passed. If the security authentication performed by the sixth sub-module 711 does not pass, the seventh sub-module 712 does not perform the decryption process. This embodiment does not limit the specific implementation process of the seventh sub-module 712 to perform the decryption process.
  • the eighth sub-module 713 is configured to perform an IMSI management operation according to the information obtained by decrypting the seventh sub-module 712.
  • the eighth sub-module 713 may allocate new IMSI and authentication data for the user terminal.
  • the eighth sub-module 713 may recover the IMSI according to the delete IMSI request message.
  • the second sending module 720 is configured to return a response message to the user terminal according to the execution result of the IMSI management operation performed by the management module 710.
  • the response message here carries information for performing a smart card IMSI update operation.
  • the second sending module 720 can carry the new IMSI and authentication data allocated by the management module 710 for the user terminal in the response message, and return the response message to the user terminal.
  • the second sending module 720 may also carry the deletion information (ie, the recovery success information) or the prohibition deletion information (ie, the recovery failure information) in the response message, and return the response message to the user terminal.
  • the second sending module 720 can send a response message to the user terminal in the form of an OTA short message.
  • the second sending module 720 can also send the user terminal to the user terminal in other forms than the OTA short message.
  • the second sending module 720 sends a response message to the user terminal through the BIP. This embodiment does not limit the specific protocol type used by the second sending module 720 to send a response message, the specific command format of the response message, and the like.
  • the second sending module 720 can include: a ninth sub-module 721 and a tenth sub-module 722.
  • the ninth sub-module 721 is configured to encrypt the execution result information of the IMSI management operation performed by the management module 710. For example, the ninth sub-module 721 encrypts the new IMSI assigned by the management module 710 and the authentication data corresponding to the IMSI. For another example, the ninth sub-module 721 encrypts the recovery success information or the recovery failure information. This embodiment does not limit the specific implementation process in which the ninth sub-module 721 performs encryption.
  • the tenth sub-module 722 is configured to carry the information obtained by encrypting the ninth sub-module 721 and the information for security authentication in the response message, and return the response message to the user terminal.
  • the information for security authentication such as the identity information of the server, and the like.
  • Embodiment 8 A system supporting multiple IMSIs. The structure of the system is shown in Figure 8.
  • the system shown in FIG. 8 includes a user terminal 800 (such as a UE) and a server 810. Although only one user terminal 800 is shown in FIG. 8, the number of user terminals 800 may be plural.
  • the user terminal 800 is configured to send an IMSI update request message to the server 810, where the IMSI update request message includes: at least one of an application IMSI request message and a delete IMSI request message; and a response message returned by the receiving server 810 for the IMSI update request message, according to
  • the smart card IMSI update operation is performed by the information carried in the response message, where the smart card is a smart card supporting multiple IMSIs, where the smart card IMSI update operation includes: adding an IMSI operation to the smart card or deleting the IMSI operation from the smart card.
  • the server 810 is configured to perform an IMSI management operation according to the IMSI update request message sent by the user terminal 800, and return a response message to the user terminal 800 according to the IMSI management operation execution result.
  • the IMSI management operation performed by the server 800 includes allocating a new IMSI and authentication data to the user terminal 800 when the received IMSI update request message includes an application IMSI request message, and the received IMSI update request message includes deleting the IMSI request message. At the time, the IMSI is recovered according to the delete IMSI request message.
  • Embodiment 9 A method of supporting multiple IMSIs. The flow of the method is as shown in FIG.
  • S900 sends an IMSI update request message to the server, where the IMSI update request message includes at least one of an application IMSI request message and a delete IMSI request message.
  • the ninth embodiment may further include: sending an IMSI update command to the smart card, receiving the IMSI update request information returned by the smart card, and then, in S900, sending the IMSI update to the server according to the received IMSI update request information. Request message.
  • the IMSI update command in this embodiment may be an IMSI update command based on an envelope command, that is, the IMSI update command takes the form of an envelope command.
  • the foregoing IMSI update command may also adopt other forms of commands than the envelope command. This embodiment does not limit the protocol type specifically adopted by the IMSI update command and the specific format of the command.
  • the IMSI update request message in this embodiment may be sent by the user terminal to the server in the form of an OTA short message.
  • the IMSI update request message may also be sent to the server in other forms than the OTA short message, for example, by sending an IMSI update request message to the server through the BIP.
  • This embodiment does not limit the protocol type specifically used by the IMSI update request message and the content specifically included in the IMSI update request message.
  • the IMSI update request information received by the execution body (such as the user terminal) in this embodiment may be the encrypted IMSI update request information. Additionally, the information for security authentication may be transmitted with the encrypted IMSI update request information, ie, the user terminal may receive information for security authentication.
  • the receiving server returns a response message according to the IMSI update request message.
  • S920 Transmit the response message to the smart card, so that the smart card performs a smart card IMSI update operation according to the information carried by the response message; wherein the smart card is a smart card supporting multiple IMSIs.
  • the smart card performing the smart card IMSI update operation according to the information carried in the response message includes: performing security authentication on the response message, decrypting the response message after the security authentication is passed, and performing the smart card IMSI update operation according to the decrypted information.
  • the smart card IMSI update operation includes at least one of adding an IMSI operation to the smart card and deleting the IMSI operation from the smart card.
  • the present invention can be implemented by means of software plus a necessary hardware platform, and of course, all can be implemented by hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product that can be used to perform the above-described method flow.
  • the computer software product can be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
  • Telephonic Communication Services (AREA)
  • Hardware Redundancy (AREA)
  • Stored Programmes (AREA)

Abstract

本发明实施例公开了支持多IMSI的方法、装置和系统。其中的方法包括：接收用户终端传输来的服务器针对IMSI更新请求消息返回的响应消息；根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作或者从智能卡中删除IMSI操作。上述技术方案可以动态的更新智能卡中的IMSI，从而避免一个用户必须始终占用多个IMSI的现象，提高了IMSI利用率，节约了IMSI资源。

Description

支持多IMSI的方法、装置和系统
技术领域
本发明涉及网络通讯技术领域，具体涉及支持多IMSI的技术。
发明背景
目前，一张智能卡可以预先设置多个International Mobile Subscriber Identity（国际移动用户识别码，IMSI），即用户开设了多个账号。用户可以根据需要选择多个IMSI中的一个IMSI使用。上述智能卡可以是Subscriber Identity Module（用户识别模块，SIM）卡等。
在实现本发明的过程中，发明人发现：现有的智能卡中设置的IMSI相对固定，即在智能卡中预先设置了IMSI后，智能卡中的IMSI不能够被更改，该智能卡中的多个IMSI只能供一个用户使用，从而使一个用户必须占用多个IMSI，致使IMSI利用率较低，最终造成了IMSI资源浪费。
发明内容
本发明实施方式提供的支持多IMSI的方法、装置和系统，可动态更新智能卡中的IMSI，从而避免一个用户必须始终占用多个IMSI的现象，提高了IMSI利用率，节约了IMSI资源。
本发明实施方式提供的支持多IMSI的方法，包括：
接收用户终端传输来的服务器针对IMSI更新请求消息返回的响应消息；
根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
本发明实施方式提供的支持多IMSI的方法，包括：
接收用户终端发送来的IMSI更新请求消息；
根据所述IMSI更新请求消息执行IMSI管理操作；
根据所述IMSI管理操作执行结果向所述用户终端返回响应消息；
所述IMSI管理操作包括：在所述IMSI更新请求消息包括申请IMSI请求消息时，为所述用户终端分配新的IMSI和鉴权数据，和/或，在所述IMSI更新请求消息包括删除IMSI请求消息时，根据所述删除IMSI请求消息回收IMSI。
本发明实施方式提供的支持多IMSI的装置，包括：
第一接收模块，用于接收用户终端传输来的服务器针对IMSI更新请求消息返回的响应消息；
更新模块，用于根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
本发明实施方式提供的用户终端，包括：控制模块和支持多IMSI的装置；
控制模块，用于向服务器发送IMSI更新请求消息，在接收到服务器针对IMSI更新请求消息返回的响应消息后，向支持多IMSI的装置发送所述响应消息；其中，所述IMSI更新请求消息包括：申请IMSI请求消息和/或删除IMSI请求消息；
支持多IMSI的装置，用于接收所述控制模块发送的响应消息，根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
本发明实施方式提供的服务器，包括：
第二接收模块，用于接收用户终端发送来的IMSI更新请求消息；
管理模块，用于根据所述IMSI更新请求消息执行IMSI管理操作；
第二发送模块，用于根据所述IMSI管理操作执行结果向所述用户终端返回响应消息；
所述IMSI管理操作包括：在所述IMSI更新请求消息包括申请IMSI请求消息时，所述管理模块为所述用户终端分配新的IMSI和鉴权数据，和/或，在所述IMSI更新请求消息包括删除IMSI请求消息时，所述管理模块根据所述删除IMSI请求消息回收IMSI。
本发明实施方式提供的支持多IMSI的系统，包括：上述服务器和至少一个上述用户终端。
本发明实施方式提供的支持多IMSI的方法，包括：
向服务器发送IMSI更新请求消息，所述IMSI更新请求消息包括：申请IMSI请求消息和/或删除IMSI请求消息；
接收服务器针对IMSI更新请求消息返回的响应消息；
向智能卡传输所述响应消息，以使所述智能卡根据所述响应消息携带的信息执行智能卡IMSI更新操作；其中，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
通过上述技术方案的描述可知，本实施例通过向服务器发送IMSI更新请求消息，如申请IMSI请求消息或者删除IMSI请求消息，使服务器能够根据IMSI更新请求消息为用户终端返回对应的响应消息，这样，可以根据用户终端传输来的服务器返回的响应消息执行在智能卡中增加IMSI操作或者执行从智能卡中删除IMSI操作，从而可动态更新智能卡中的IMSI，使用户终端可以动态占有IMSI，进而避免了一个用户必须始终占用多个IMSI的现象，提高了IMSI利用率，节约了IMSI资源。
附图简要说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例一的支持多IMSI的方法流程图；
图2是本发明实施例二的支持多IMSI的方法流程图；
图3是本发明实施例三的支持多IMSI的方法流程图；
图4是本发明实施例四的支持多IMSI的方法流程图；
图5是本发明实施例五的支持多IMSI的装置示意图；
图6是本发明实施例六的用户终端示意图；
图7是本发明实施例七的服务器示意图；
图8是本发明实施例八的支持多IMSI的系统示意图；
图9是本发明实施例九的支持多IMSI的方法流程图。
实施本发明的方式
下面通过实施例对本发明的支持多IMSI技术的具体实现过程进行例举说明。显然，下面所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
实施例一、支持多IMSI的方法。该方法的流程如附图1所示。
图1中的流程包括S100、S110、S120和S130，其中S100和S110为可选步骤，即实施例一可以仅包含图1示出的S120和S130。
S100、接收IMSI更新命令。该IMSI更新命令可以为用户终端传输来的命令，用户终端可以在接收到外部输入的请求IMSI更新信息后产生IMSI更新命令，并向S100的执行主体传输该IMSI更新命令。用户终端接收到的请求IMSI更新信息可以表示出用户需要申请新的IMSI或者用户需要删除某个IMSI等内容。用户终端根据请求IMSI更新信息产生的IMSI更新命令同样可以表示出用户需要申请新的IMSI或者用户需要删除某个IMSI等内容。上述IMSI更新命令可以为基于信封命令的IMSI更新命令，即IMSI更新命令采用了信封命令形式。上述IMSI更新命令也可以采用除信封命令之外的其它形式的命令，本实施例不限制IMSI更新命令具体采用的协议类型以及命令的具体格式等。
S110、在接收到IMSI更新命令后，根据IMSI更新命令向用户终端发送IMSI更新请求信息，以触发用户终端根据该IMSI更新请求信息向服务器发送IMSI更新请求消息。这里的IMSI更新请求消息可以为申请IMSI请求消息，也可以为删除IMSI请求消息。申请IMSI请求消息用于为用户终端申请新的IMSI，删除IMSI请求消息用于取消用户终端已占用的某个IMSI。删除IMSI请求消息中可以携带有需要删除的IMSI信息，如IMSI和鉴权数据等。这里的鉴权数据为IMSI对应的鉴权数据。上述IMSI更新请求信息可以基于信封命令的形式发送给用户终端，也可以采用除信封命令之外的其它形式的命令，本实施例不限制IMSI更新请求信息具体采用的协议类型以及具体格式等。
S110的执行主体可以对IMSI更新请求信息进行加密，并将加密后信息传输给用户终端。另外，S110的执行主体也可以将用于安全性鉴定的信息和上述加密后信息传输给用户终端。用于安全性鉴定的信息包括的内容可以根据实际的安全性鉴定的具体形式设置，如用于安全性鉴定的信息包括智能卡身份信息等，本实施例不限制安全性鉴定的具体实现方式、用于安全性鉴定的信息具体包括的内容、以及加密的具体实现方式等。
上述IMSI更新请求消息可以通过Over The Air（空中下载，OTA）短消息的形式由用户终端向服务器发送。当然，IMSI更新请求消息也可以采用除OTA短消息之外的其它形式向服务器发送，例如，通过Bearer Independent Protocol（承载独立协议，BIP）向服务器发送IMSI更新请求消息。本实施例不限制IMSI更新请求消息具体采用的协议类型以及IMSI更新请求消息具体包括的内容等。
针对上述S100和S110需要特别说明的是，上述S100和S110描述了用户终端被动的根据触发向服务器发送IMSI更新请求消息的过程，其实，用户终端也可以主动的向服务器发送IMSI更新请求消息。本实施例不限制用户终端向服务器发送IMSI更新请求消息的具体实现方式。
S120、接收用户终端传输来的服务器针对接收的IMSI更新请求消息返回响应消息。
用户终端在接收到服务器返回的响应消息后，可以利用用户终端与S120执行主体之间的协议向S120执行主体传输该响应消息。服务器返回的响应消息中可以携带有用于执行在智能卡中增加IMSI操作的信息，如为用户终端分配的新的IMSI和该IMSI对应的鉴权数据等；该响应消息中也可以携带有用于执行从智能卡中删除IMSI操作的信息，如允许删除信息（即回收成功信息）等，可选的，用于执行从智能卡中删除IMSI操作的信息可以包括：需要删除的IMSI，或者包括需要删除的IMSI和该IMSI对应的鉴权数据等。用户终端可以将服务器返回的响应消息通过基于信封命令的响应消息向S120的执行主体传输。本实施例不限制用户终端向S120的执行主体传输的响应消息具体采用的协议类型、以及响应消息的具体命令格式等。
S130、根据接收到的响应消息携带的信息执行智能卡IMSI更新操作，这里的智能卡为支持多IMSI的智能卡。上述智能卡IMSI更新操作可以包括：在智能卡中增加IMSI操作和从智能卡中删除IMSI操作中的至少一个。需要说明的是在智能卡中增加IMSI操作包括：在智能卡中增加IMSI和该IMSI对应的鉴权数据。从智能卡中删除IMSI操作包括：从智能卡中删除IMSI和该IMSI对应的鉴权数据。下述实施例中记载的增加IMSI操作和删除IMSI操作也是如此，不再一一说明。
在S130中，执行主体在接收到响应消息后，可以根据响应消息中携带的信息对接收到的响应消息进行安全性鉴定，如利用响应消息中携带的服务器身份信息对响应消息进行安全性鉴定。在安全性鉴定通过后，执行主体根据响应消息中携带的信息执行智能卡IMSI更新操作。如果服务器发送的响应消息为进行了加密处理的响应消息，则S130的执行主体在安全性鉴定通过后，还需要对接收到的响应消息进行解密，并根据解密后获得的信息执行智能卡IMSI更新操作。另外，S130的执行主体在解密后可以判断解密后获得的信息是否完整合法，并在判断出完整合法后，再根据解密后获得的信息执行智能卡IMSI更新操作；在判断出不完整合法后，可以不再执行智能卡IMSI更新操作。
上述响应消息中携带的信息可以包括：表示申请新的IMSI的响应命令类型、新申请的IMSI（即为用户终端分配的新的IMSI）和鉴权数据。响应消息中携带的信息也可以包括：表示删除IMSI的响应命令类型和回收是否成功信息，可选的，还可以包括：需要删除的IMSI和鉴权数据。
S130的执行主体可以根据申请新的IMSI的响应命令类型将响应消息中的新申请的IMSI和鉴权数据添加在智能卡中。S130的执行主体也可以根据删除IMSI的响应命令类型确定该响应消息对应的IMSI更新命令表示出的用户需要删除的某个IMSI，并从智能卡中删除该IMSI和该IMSI对应的鉴权数据。在响应消息中携带有需要删除的IMSI和鉴权数据的情况下，S130的执行主体可以从智能卡中删除响应消息中携带的IMSI和该IMSI对应的鉴权数据。
可选的，S130的执行主体可以输出智能卡IMSI更新操作的执行情况，以便使用户能够获知是否成功申请了新的IMSI，或者是否成功删除了某个IMSI。
需要特别说明的是，在通常情况下，智能卡为独立于用户终端设置的智能卡，而在某些情况下，智能卡也可以固化在用户终端中，本实施例中的智能卡可以为独立于用户终端设置的智能卡，也可以为固化在用户终端中的智能卡。另外，本实施例中的执行主体可以设置于智能卡中，也可以独立于智能卡设置。本实施例不限制智能卡以及执行主体的具体存在方式。
从上述实施例一的描述可知，通过向用户终端发送IMSI更新请求信息来触发用户终端向服务器发送IMSI更新请求消息，如申请IMSI请求消息或者删除IMSI请求消息，使服务器能够根据IMSI更新请求消息为用户终端返回对应的响应消息，这样，可以根据用户终端接收到的该响应消息执行在智能卡中增加IMSI操作或者执行从智能卡中删除IMSI操作，从而可动态更新智能卡中的IMSI，使用户终端可以动态占有IMSI，进而避免了一个用户必须始终占用多个IMSI的现象；通过对用户终端接收到的响应消息进行安全性鉴定以及解密等操作，保证了智能卡IMSI更新操作的安全性。最终实施例一提高了IMSI利用率，节约了IMSI资源。
实施例二、支持多IMSI的方法。该方法的流程如附图2所示。
图2中，S200、接收用户终端发送来的IMSI更新请求消息。这里的IMSI更新请求消息可以为申请IMSI请求消息，也可以为删除IMSI请求消息。S200接收到的IMSI更新请求消息可以为基于OTA短消息的形式，也可以为其它形式。
S210、根据接收到的IMSI更新请求消息执行IMSI管理操作。这里的IMSI管理操作可以为：在IMSI更新请求消息为申请IMSI请求消息时，为用户终端分配新的IMSI和鉴权数据；该IMSI管理操作也可以为：在IMSI更新请求消息为删除IMSI请求消息时，根据删除IMSI请求消息回收IMSI。回收IMSI如解除该IMSI和该IMSI对应的鉴权数据与用户终端之间的绑定关系等。
对接收到IMSI更新请求消息后，可以先根据IMSI更新请求消息中携带的信息进行安全性鉴定，如利用IMSI更新请求消息中携带的智能卡身份信息对IMSI更新请求消息进行安全性鉴定。如果安全性鉴定通过，则根据接收到的IMSI更新请求消息执行IMSI管理操作，如果安全性鉴定失败（即未通过），则不执行IMSI管理操作。本实施例可以采用现有的安全性鉴定方式对IMSI更新请求消息进行安全性鉴定，本实施例不限制安全性鉴定的具体实现过程。
如果IMSI更新请求消息进行了加密处理，则S210的执行主体可以对IMSI更新请求消息中携带的信息进行解密处理，之后，再根据解密后信息执行IMSI管理操作。例如，在安全性鉴定通过后，对IMSI更新请求消息中携带的信息进行解密处理，并根据解密后信息执行IMSI管理操作。本实施例不限制解密处理的具体实现过程。
S220、根据所述IMSI管理操作执行结果向所述用户终端返回响应消息。
这里的响应消息中携带有用于执行智能卡IMSI更新操作的信息，该智能卡IMSI更新操作可以包括：在智能卡中增加IMSI操作和从智能卡中删除IMSI操作中的至少一个。
当IMSI更新请求消息为申请IMSI请求消息（即智能卡IMSI更新操作为在智能卡中增加IMSI操作）时，S220的执行主体可以将为用户终端分配的新的IMSI和鉴权数据携带在响应消息中，并向用户终端返回该响应消息。
当IMSI更新请求消息为删除IMSI请求消息（即智能卡IMSI更新操作为从智能卡中删除IMSI操作）时，S220的执行主体可以将允许删除信息（即回收成功信息）或者禁止删除信息（即回收失败信息）携带在响应消息中，并向用户终端返回该响应消息。
上述响应消息可以通过OTA短消息的形式向用户终端发送。当然，响应消息也可以采用除OTA短消息之外的其它形式向用户终端发送，例如，通过BIP向用户终端发送响应消息。本实施例不限制响应消息具体采用的协议类型以及响应消息的具体命令格式等。
S220的执行主体可以对需要携带在响应消息中的信息进行加密处理，将加密处理后的信息携带在响应消息中，并向用户终端返回携带有加密处理后信息的响应消息。例如，对分配的新的IMSI和该IMSI对应的鉴权数据进行加密，之后将加密后的IMSI和鉴权数据携带在响应消息中向用户终端发送。再例如，对允许删除信息或者禁止删除信息进行加密，将加密后信息携带在响应消息中向用户终端发送。本实施例不限制加密的具体实现过程。
实施例三、支持多IMSI的方法。该方法的流程如附图3所示。
图3中，S300、用户通过UE STK（User Equipment SIM Toolkit，用户设备智能卡工具集）应用请求增加IMSI，如用户通过UE STK输入增加IMSI请求信息，以请求增加某地区本地的IMSI。
S310、UE接收到增加IMSI请求信息后，调用信封命令（如菜单选择MENU Select命令）向SIM卡发送IMSI更新命令，以触发增加IMSI的过程。
S320、SIM卡接收到IMSI更新命令后，向UE发送IMSI增加请求安全包，以触发UE向CAT服务器（即通过空中接口对SIM卡文件系统进行管理和控制的服务器）发送OTA短消息。该IMSI增加请求安全包中包括用于安全性鉴定的信息和加密后信息。
S330、UE接收到IMSI增加请求安全包后，向CAT服务器发送OTA短消息（即IMSI增加请求安全包被封装在OTA短消息中向CAT服务器发送），以请求CAT服务器为用户终端分配新的IMSI。
S340、CAT服务器接收到OTA短消息后，对OTA短消息中的IMSI增加请求安全包进行安全性鉴定。
S350、在安全性鉴定通过后，CAT服务器向用户终端发送IMSI数据安全包。该IMSI数据安全包中携带有为用户终端新分配的某地区本地的IMSI和该IMSI对应的鉴权数据。新分配的IMSI和该IMSI对应的鉴权数据可以在加密后携带在IMSI增加请求安全包中。该IMSI增加请求安全包中可以包括用于安全性鉴定的信息和加密后信息。该IMSI数据安全包以OTA短消息的形式向用户终端发送（即IMSI数据安全包被封装在OTA短消息中向用户终端发送）。
S360、UE接收到CAT服务器传输来的OTA短消息的形式的IMSI数据安全包后，不对该OTA短消息中的IMSI数据安全包进行加密解密处理等操作，将OTA短消息中的IMSI数据安全包通过Short Message Services point-to-point Download（短消息点对点下载，SMS PP Download）命令传输给SIM卡。
S370、SIM卡接收到SMS PP Download命令后，对命令中的IMSI数据安全包进行安全性鉴定，并在安全性鉴定通过后，SIM卡对IMSI数据安全包进行解密处理，如果确定出解密后的信息完整合法，则SIM卡存储解密后获得的IMSI和鉴权数据。如果确定出解密后的信息不完整合法，则SIM卡不进行存储IMSI和鉴权数据的操作。SIM卡在成功增加了新的IMSI之后，向UE发送成功增加新的IMSI的通知信息。另外，如果没有成功增加新的IMSI，SIM卡也应该向UE发送未成功增加新的IMSI的通知信息。
S380、UE接收到通知信息后，显示成功增加新的IMSI的通知信息，以使用户获知请求增加IMSI的执行结果。
S390、用户在选择使用新增加的IMSI时，输入切换到新的IMSI请求信息。
S391、UE将切换到新的IMSI请求信息传输给SIM卡，UE可以调用MENU Select命令向SIM卡传输切换到新的IMSI请求信息。
S392、SIM卡执行接收到的MENU Select命令，并将MENU Select命令执行结果信息通过Display Text（显示文本）命令传输给UE。
S393、UE显示Display Text命令中的MENU Select命令执行结果信息，使用户获知是否成功切换到新的IMSI。
实施例四、支持多IMSI的方法。该方法的流程如附图4所示。
图4中，S400、用户通过UE STK应用请求删除IMSI，如用户通过UE STK输入删除IMSI请求消息信息，以请求删除某地区本地的IMSI。
S410、UE接收到删除IMSI请求消息信息后，调用信封命令（如菜单选择MENU Select命令）向SIM卡发送IMSI更新命令，以触发删除IMSI的过程。
S420、SIM卡接收到IMSI更新命令后，向UE发送IMSI删除请求安全包，以触发UE向CAT服务器发送OTA短消息。该IMSI删除请求安全包中包括：用于安全性鉴定的信息和加密后信息。该加密后信息包括：需要删除的IMSI和该IMSI对应的鉴权数据。
S430、UE接收到IMSI删除请求安全包后，向CAT服务器发送OTA短消息（即IMSI删除请求安全包被封装在OTA短消息中向CAT服务器发送），以请求CAT服务器删除曾经为用户终端分配的IMSI。
S440、CAT服务器接收到OTA短消息后，对OTA短消息中的IMSI删除请求安全包进行安全性鉴定。
S450、在安全性鉴定通过后，CAT服务器对IMSI数据安全包中携带的加密信息进行解密处理，获得需要删除的IMSI和鉴权数据，CAT服务器根据获得的IMSI和鉴权数据回收该IMSI，之后，CAT服务器向用户终端发送IMSI数据安全包。该IMSI数据安全包中携带有用于安全性鉴定的信息和加密后的信息。该加密后信息包括对回收成功信息进行加密后获得的信息。该IMSI数据安全包以OTA短消息的形式向用户终端发送（即IMSI数据安全包被封装在OTA短消息中向用户终端发送）。
S460、UE接收到CAT服务器传输来的OTA短消息的IMSI数据安全包后，不对该OTA短消息中的IMSI数据安全包进行加密解密处理等操作，将OTA短消息中的IMSI数据安全包通过SMS PP Download命令传输给SIM卡。
S470、SIM卡接收到SMS PP Download命令后，对命令中的IMSI数据安全包进行安全性鉴定，并在安全性鉴定通过后，SIM卡对IMSI数据安全包进行解密处理，如果确定出解密后的信息完整合法，则SIM卡根据解密后获得的回收成功信息将SIM卡中存储的需要删除的IMSI和鉴权数据删除。如果确定出解密后的信息不完整合法，则SIM卡不进行删除操作。SIM卡在成功删除了IMSI之后，向UE发送成功删除IMSI的通知信息。另外，如果没有成功删除IMSI，则SIM卡也应该向UE发送未成功删除IMSI的通知信息。
S480、UE接收到通知信息后，显示成功删除IMSI的通知信息，以使用户获知请求删除IMSI的执行结果。
S490、用户在选择使用其它IMSI时，输入切换到指定IMSI的请求信息。
S491、UE将切换到指定IMSI的请求信息传输给SIM卡，UE可以调用MENU Select命令向SIM卡传输切换到指定IMSI的请求信息。
S492、SIM卡执行接收到的MENU Select命令，并将MENU Select命令执行结果信息通过Display Text命令传输给UE。
S493、UE显示Display Text命令中的MENU Select命令执行结果信息，使用户获知是否成功切换到指定的IMSI。
实施例五、支持多IMSI的装置。该装置可以设置在智能卡（如SIM卡）中，也可以独立于智能卡设置。该装置的结构如附图5所示。
附图5中的装置包括：第一接收模块500和更新模块520。可选的，该装置还可以包括：第一发送模块510。
第一接收模块500，用于并接收用户终端传输来的服务器针对IMSI更新请求消息返回的响应消息。可选的，第一接收模块还用于接收IMSI更新命令。
第一接收模块500接收的IMSI更新命令可以为用户终端传输来的命令，用户终端可以在接收到外部输入的请求IMSI更新信息后产生IMSI更新命令，并向支持多IMSI的装置传输该IMSI更新命令。用户终端接收到的请求IMSI更新信息可以表示出用户需要申请新的IMSI或者用户需要删除某个IMSI等内容。用户终端根据请求IMSI更新信息产生的IMSI更新命令同样可以表示出用户需要申请新的IMSI或者用户需要删除某个IMSI等内容。第一接收模块500接收的IMSI更新命令可以为基于信封命令的IMSI更新命令。第一接收模块500接收的IMSI更新命令也可以采用除信封命令之外的其它形式的命令，本实施例不限制IMSI更新命令具体采用的协议类型以及命令的具体格式等。
第一发送模块510，用于根据第一接收模块500接收的IMSI更新命令向用户终端发送IMSI更新请求信息，以触发用户终端根据IMSI更新请求信息向服务器发送IMSI更新请求消息。这里的IMSI更新请求消息包括：申请IMSI请求消息或者删除IMSI请求消息。
这里的IMSI更新请求消息可以为申请IMSI请求消息，也可以为删除IMSI请求消息。申请IMSI请求消息用于为用户终端申请新的IMSI，删除IMSI请求消息用于删除用户终端已占用的某个IMSI。删除IMSI请求消息中可以携带有需要删除的IMSI信息，如IMSI和鉴权数据等。这里的鉴权数据为IMSI对应的鉴权数据。第一发送模块510可以基于信封命令的形式向用户终端发送IMSI更新请求信息，第一发送模块510也可以采用除信封命令之外的其它形式的命令向用户终端发送IMSI更新请求信息，本实施例不限制第一发送模块500发送IMSI更新请求信息所具体采用的协议类型以及具体格式等。
第一发送模块510可以包括：第一子模块511和第二子模块512。
第一子模块511，用于根据第一接收模块500接收的IMSI更新命令确定IMSI更新请求信息，并加密IMSI更新请求信息。
第二子模块512，用于将第一子模块511加密后获得的信息和用于安全性鉴定的信息传输给用户终端。如第二子模块512基于信封命令的形式向用户终端发送上述加密后获得的信息和用于安全性鉴定的信息。
更新模块520，用于根据第一接收模块500接收的响应消息携带的信息执行智能卡IMSI更新操作。这里的智能卡为支持多IMSI的智能卡，该智能卡IMSI更新操作可以为在智能卡中增加IMSI操作，也可以为从智能卡中删除IMSI操作。可选的，更新模块520可以输出智能卡IMSI更新操作的执行情况，以便使用户能够获知是否成功申请了新的IMSI，或者是否成功删除了某个IMSI。
更新模块可以包括：第三子模块521、第四子模块522和第五子模块523。
第三子模块521，用于对第一接收模块500接收的响应消息进行安全性鉴定。如第三子模块521利用响应消息中携带的服务器身份信息对响应消息进行安全性鉴定。
第四子模块522，用于在第三子模块521进行的安全性鉴定通过后，解密该响应消息。第四子模块522解密后获得的信息可以包括：为用户终端分配的新的IMSI和鉴权数据。第四子模块522解密后获得的信息也可以包括：回收是否成功信息等。本实施例不限制第四子模块522解密响应消息的具体实现过程。
第五子模块523，用于根据第四子模块522解密后获得的信息执行智能卡IMSI更新操作。
可选的，第五子模块523可以判断解密后获得的信息是否完整合法，并在判断出完整合法后，第五子模块523再根据解密后获得的信息执行智能卡IMSI更新操作；在判断出不完整合法后，第五子模块523可以不再执行智能卡IMSI更新操作。
可选的，第五子模块523可以输出智能卡IMSI更新操作的执行情况，以便使用户能够获知是否成功申请了新的IMSI，或者是否成功删除了某个IMSI。
实施例六、用户终端。该用户终端的结构如附图6所示。
附图6中的用户终端包括：控制模块600和支持多IMSI的装置610。这里的支持多IMSI的装置610可以为智能卡（如SIM卡），也可以与智能卡设置独立。
控制模块600，用于向服务器发送IMSI更新请求消息，在接收到服务器针对IMSI更新请求消息返回的响应消息后，向支持多IMSI的装置610发送该响应消息。这里的IMSI更新请求消息包括：申请IMSI请求消息和删除IMSI请求消息中的至少一个。
控制模块600还可以用于根据接收到的请求IMSI更新信息向支持多IMSI的装置610发送IMSI更新命令，使支持多IMSI的装置610接收到IMSI更新命令后，向其发送IMSI更新请求信息，并在接收到IMSI更新请求信息后向服务器发送IMSI更新请求消息。当然，控制模块600也可以主动的向服务器发送IMSI更新请求消息，即控制模块600在没有接收到支持多IMSI的装置610发送来的IMSI更新请求信息的情况下，向服务器发送IMSI更新请求消息。
控制模块600可以通过OTA短消息的形式由向服务器发送IMSI更新请求消息。当然，控制模块600也可以采用除OTA短消息之外的其它形式向服务器发送IMSI更新请求消息，例如，控制模块600通过BIP向服务器发送IMSI更新请求消息。本实施例不限制控制模块600发送IMSI更新请求消息所具体采用的协议类型以及IMSI更新请求消息具体包括的内容等。
控制模块600在接收到服务器返回的响应消息后，可以利用其与支持多IMSI的装置610之间的协议向支持多IMSI的装置610传输该响应消息。如控制模块600可以将服务器返回的响应消息通过基于信封命令的响应消息向支持多IMSI的装置610传输。服务器返回的响应消息中可以携带有用于执行在智能卡中增加IMSI操作的信息，如服务器为用户终端分配的新的IMSI和该IMSI对应的鉴权数据等；该响应消息中也可以携带有用于执行从智能卡中删除IMSI操作的信息，如允许删除信息（即回收成功信息）等，可选的，用于执行从智能卡中删除IMSI操作的信息可以包括：需要删除的IMSI，或者包括需要删除的IMSI和该IMSI对应的鉴权数据等。本实施例不限制控制模块600向支持多IMSI的装置610传输响应消息所具体采用的协议类型、以及响应消息的具体命令格式等。
支持多IMSI的装置610，用于接收控制模块600发送的响应消息，根据响应消息携带的信息执行智能卡IMSI更新操作。这里的智能卡为支持多IMSI的智能卡，这里的智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和从智能卡中删除IMSI操作中的至少一个。
支持多IMSI的装置610还用于，接收控制模块600发送的IMSI更新命令，根据IMSI更新命令向控制模块600发送IMSI更新请求信息。
支持多IMSI的装置610的具体结构如上述实施例五的描述，在此不再重复说明。
实施例七、服务器。该服务器的结构如附图7所示。
附图7中示出的服务器包括：第二接收模块700、管理模块710和第二发送模块720。
第二接收模块700，用于接收用户终端发送来的IMSI更新请求消息。这里的IMSI更新请求消息可以为申请IMSI请求消息，也可以为删除IMSI请求消息。第二接收模块700接收到的IMSI更新请求消息可以为基于OTA短消息的形式，也可以为其它形式。
管理模块710，用于根据第二接收模块700接收的IMSI更新请求消息执行IMSI管理操作。管理模块710执行的IMSI管理操作包括：在所述IMSI更新请求消息包括申请IMSI请求消息时，管理模块710为用户终端分配新的IMSI和鉴权数据。在IMSI更新请求消息包括删除IMSI请求消息时，管理模块710根据删除IMSI请求消息回收IMSI，如管理模块710解除需要删除的IMSI与用户终端之间的绑定关系等。
管理模块710可以包括：第六子模块711、第七子模块712和第八子模块713。
第六子模块711，用于对第二接收模块700接收的IMSI更新请求消息进行安全性鉴定。如第六子模块711利用IMSI更新请求消息中携带的智能卡身份信息对IMSI更新请求消息进行安全性鉴定。第六子模块711可以采用现有的安全性鉴定方式对IMSI更新请求消息进行安全性鉴定，本实施例不限制第六子模块711执行安全性鉴定的具体实现过程。
第七子模块712，用于在第六子模块711执行的安全性鉴定通过后，对IMSI更新请求消息进行解密。如果第六子模块711执行的安全性鉴定未通过，则第七子模块712不执行解密处理。本实施例不限制第七子模块712执行解密处理的具体实现过程。
第八子模块713，用于根据第七子模块712解密获得的信息执行IMSI管理操作。当IMSI更新请求消息为申请IMSI请求消息时，第八子模块713可以为用户终端分配的新的IMSI和鉴权数据。当IMSI更新请求消息为删除IMSI请求消息时，第八子模块713可以根据删除IMSI请求消息回收IMSI。
第二发送模块720，用于根据管理模块710执行的IMSI管理操作的执行结果向用户终端返回响应消息。这里的响应消息中携带有用于执行智能卡IMSI更新操作的信息。
第二发送模块720可以将管理模块710为用户终端分配的新的IMSI和鉴权数据携带在响应消息中，并向用户终端返回该响应消息。第二发送模块720也可以将允许删除信息（即回收成功信息）或者禁止删除信息（即回收失败信息）携带在响应消息中，并向用户终端返回该响应消息。
第二发送模块720可以通过OTA短消息的形式向用户终端发送响应消息。当然，第二发送模块720也可以采用除OTA短消息之外的其它形式向用户终端发送，例如，第二发送模块720通过BIP向用户终端发送响应消息。本实施例不限制第二发送模块720发送响应消息所采用的具体协议类型以及响应消息的具体命令格式等。
第二发送模块720可以包括：第九子模块721和第十子模块722。
第九子模块721，用于对管理模块710执行IMSI管理操作的执行结果信息进行加密。例如，第九子模块721对管理模块710分配的新的IMSI和该IMSI对应的鉴权数据进行加密。再例如，第九子模块721对回收成功信息或者回收失败信息进行加密。本实施例不限制第九子模块721执行加密的具体实现过程。
第十子模块722，用于将第九子模块721加密后获得的信息和用于安全性鉴定的信息携带在响应消息中，并向用户终端返回该响应消息。该用于安全性鉴定的信息如服务器的身份信息等。
实施例八、支持多IMSI的系统。该系统的结构如附图8所示。
图8中示出的系统包括：用户终端800（如UE）和服务器810。虽然图8中仅示出了一个用户终端800，但是，用户终端800的数量可以是多个。
用户终端800，用于向服务器810发送IMSI更新请求消息，该IMSI更新请求消息包括：申请IMSI请求消息和删除IMSI请求消息中的至少一个；接收服务器810针对IMSI更新请求消息返回的响应消息，根据响应消息携带的信息执行智能卡IMSI更新操作，这里的智能卡为支持多IMSI的智能卡，这里的智能卡IMSI更新操作包括：在智能卡中增加IMSI操作或者从智能卡中删除IMSI操作。
服务器810，用于根据用户终端800发送来的IMSI更新请求消息执行IMSI管理操作，并根据IMSI管理操作执行结果向用户终端800返回响应消息。
服务器800执行的IMSI管理操作包括：在接收到的IMSI更新请求消息包括申请IMSI请求消息时，为用户终端800分配新的IMSI和鉴权数据，在接收到的IMSI更新请求消息包括删除IMSI请求消息时，根据删除IMSI请求消息回收IMSI。
用户终端800和服务器810具体执行的操作以及具体结构等如上述方法和装置实施例的描述，在此不再重复说明。
实施例九、支持多IMSI的方法。该方法的流程如附图9所示。
图9中，S900、向服务器发送IMSI更新请求消息，该IMSI更新请求消息包括：申请IMSI请求消息和删除IMSI请求消息中的至少一个。
可选的，在S900之前，实施例九还可以包括：向智能卡发送IMSI更新命令，接收智能卡返回的IMSI更新请求信息，之后，在S900中，可以根据接收的IMSI更新请求信息向服务器发送IMSI更新请求消息。
本实施例中的IMSI更新命令可以为基于信封命令的IMSI更新命令，即IMSI更新命令采用了信封命令形式。上述IMSI更新命令也可以采用除信封命令之外的其它形式的命令，本实施例不限制IMSI更新命令具体采用的协议类型以及命令的具体格式等。
本实施例中的IMSI更新请求消息可以通过OTA短消息的形式由用户终端向服务器发送。当然，IMSI更新请求消息也可以采用除OTA短消息之外的其它形式向服务器发送，例如，通过BIP向服务器发送IMSI更新请求消息。本实施例不限制IMSI更新请求消息具体采用的协议类型以及IMSI更新请求消息具体包括的内容等。
本实施例中的执行主体（如用户终端）接收到的IMSI更新请求信息可以是被加密的IMSI更新请求信息。另外，用于安全性鉴定的信息可以和被加密的IMSI更新请求信息一起传输，即用户终端可以接收到用于安全性鉴定的信息。
S910、接收服务器根据IMSI更新请求消息返回的响应消息。
S920、向智能卡传输该响应消息，以使智能卡根据该响应消息携带的信息执行智能卡IMSI更新操作；其中，智能卡为支持多IMSI的智能卡。
智能卡根据该响应消息携带的信息执行智能卡IMSI更新操作包括：对响应消息进行安全性鉴定，在安全性鉴定通过后，解密该响应消息，并根据解密后信息执行智能卡IMSI更新操作。智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和从智能卡中删除IMSI操作中的至少一个。智能卡执行的具体操作如上述实施例中的描述，在此不再重复说明。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到本发明可借助软件加必需的硬件平台的方式来实现，当然也可以全部通过硬件来实施，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案对背景技术做出贡献的全部或者部分可以以软件产品的形式体现出来，所述的软件产品在可以用于执行上述的方法流程。该计算机软件产品可以存储在存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备（可以是个人计算机，服务器，或者网络设备等）执行本发明各个实施例或者实施例的某些部分所述的方法。
虽然通过实施例描绘了本发明，本领域普通技术人员知道，本发明有许多变形和变化而不脱离本发明的精神，本发明的申请文件的权利要求包括这些变形和变化。

Claims (18)

  1. 一种支持多国际移动用户识别码IMSI的方法，其特征在于，包括：
    接收用户终端传输来的服务器针对IMSI更新请求消息返回的响应消息；
    根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
  2. 如权利要求1所述的方法，其特征在于，在接收用户终端传输来的响应消息之前，所述方法包括：接收IMSI更新命令，根据所述IMSI更新命令向用户终端发送IMSI更新请求信息，以触发用户终端根据所述IMSI更新请求信息向服务器发送IMSI更新请求消息，所述IMSI更新请求消息包括：申请IMSI请求消息和/或删除IMSI请求消息。
  3. 如权利要求1或2所述的方法，其特征在于，所述IMSI更新命令包括：基于信封命令的IMSI更新命令，和/或，所述IMSI更新请求消息通过空中下载OTA短消息的形式或承载独立协议的形式发送。
  4. 如权利要求2所述的方法，其特征在于：
    向用户终端发送IMSI更新请求信息包括：加密IMSI更新请求信息，并将加密后信息和用于安全性鉴定的信息传输给用户终端；
    和/或
    所述根据所述响应消息携带的信息执行智能卡IMSI更新操作包括：
    对所述响应消息进行安全性鉴定，在所述安全性鉴定通过后，解密所述响应消息，并根据所述解密后信息执行智能卡IMSI更新操作。
  5. 一种支持多IMSI的方法，其特征在于，包括：
    接收用户终端发送来的IMSI更新请求消息；
    根据所述IMSI更新请求消息执行IMSI管理操作；
    根据所述IMSI管理操作执行结果向所述用户终端返回响应消息；
    所述IMSI管理操作包括：在所述IMSI更新请求消息包括申请IMSI请求消息时，为所述用户终端分配新的IMSI和鉴权数据，和/或，在所述IMSI更新请求消息包括删除IMSI请求消息时，根据所述删除IMSI请求消息回收IMSI。
  6. 如权利要求5所述的方法，其特征在于：
    所述根据所述IMSI更新请求消息执行IMSI管理操作包括：对所述IMSI更新请求消息进行安全性鉴定，在所述安全性鉴定通过后，对所述IMSI更新请求消息进行解密，根据所述解密获得的信息执行IMSI管理操作；
    和/或
    根据所述IMSI管理操作执行结果向所述用户终端返回响应消息包括：加密所述IMSI管理操作执行结果信息，并将加密后信息和用于安全性鉴定的信息携带在响应消息中，向所述用户终端返回所述响应消息。
  7. 一种支持多IMSI的装置，其特征在于，包括：
    第一接收模块，用于接收用户终端传输来的服务器针对IMSI更新请求消息返回的响应消息；
    更新模块，用于根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
  8. 如权利要求7所述的装置，其特征在于，所述装置还包括第一发送模块；
    所述第一接收模块还用于接收IMSI更新命令；
    所述第一发送模块，用于根据所述第一接收模块接收的IMSI更新命令向用户终端发送IMSI更新请求信息，以触发用户终端根据所述IMSI更新请求信息向服务器发送IMSI更新请求消息，所述IMSI更新请求消息包括：申请IMSI请求消息和/或删除IMSI请求消息。
  9. 如权利要求8所述的装置，其特征在于，第一发送模块包括：
    第一子模块，用于根据所述IMSI更新命令确定IMSI更新请求信息，并加密所述IMSI更新请求信息；
    第二子模块，用于将所述加密后信息和用于安全性鉴定的信息传输给用户终端；
    和/或，所述更新模块包括：
    第三子模块，用于对所述响应消息进行安全性鉴定；
    第四子模块，用于在所述安全性鉴定通过后，解密所述响应消息；
    第五子模块，用于根据所述解密后信息执行智能卡IMSI更新操作。
  10. 一种用户终端，其特征在于，包括：控制模块和支持多IMSI的装置；
    控制模块，用于向服务器发送IMSI更新请求消息，在接收到服务器针对IMSI更新请求消息返回的响应消息后，向支持多IMSI的装置发送所述响应消息；其中，所述IMSI更新请求消息包括：申请IMSI请求消息和/或删除IMSI请求消息；
    支持多IMSI的装置，用于接收所述控制模块发送的响应消息，根据所述响应消息携带的信息执行智能卡IMSI更新操作，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
  11. 如权利要求10所述的用户终端，其特征在于，
    所述支持多IMSI的装置还用于，接收所述控制模块发送的IMSI更新命令，根据所述IMSI更新命令向所述控制模块发送IMSI更新请求信息；
    所述控制模块还用于，根据接收到的IMSI更新请求信息向服务器发送IMSI更新请求消息。
  12. 一种服务器，其特征在于，包括：
    第二接收模块，用于接收用户终端发送来的IMSI更新请求消息；
    管理模块，用于根据所述IMSI更新请求消息执行IMSI管理操作；
    第二发送模块，用于根据所述IMSI管理操作执行结果向所述用户终端返回响应消息；
    所述IMSI管理操作包括：在所述IMSI更新请求消息包括申请IMSI请求消息时，所述管理模块为所述用户终端分配新的IMSI和鉴权数据，和/或，在所述IMSI更新请求消息包括删除IMSI请求消息时，所述管理模块根据所述删除IMSI请求消息回收IMSI。
  13. 如权利要求12所述的服务器，其特征在于，所述管理模块包括：
    第六子模块，用于对所述IMSI更新请求消息进行安全性鉴定；
    第七子模块，用于在所述安全性鉴定通过后，对所述IMSI更新请求消息进行解密；
    第八子模块，用于根据所述解密获得的信息执行IMSI管理操作；
    和/或
    所述第二发送模块包括：
    第九子模块，用于加密所述管理模块执行IMSI管理操作的执行结果信息；
    第十子模块，用于将所述加密后信息和用于安全性鉴定的信息携带在响应消息中，向所述用户终端返回所述响应消息。
  14. 一种支持多IMSI的系统，其特征在于，包括：至少一个如权利要求10或11所述的用户终端，和如权利要求12或13所述的服务器。
  15. 一种支持多IMSI的方法，其特征在于，包括：
    向服务器发送IMSI更新请求消息，所述IMSI更新请求消息包括：申请IMSI请求消息和/或删除IMSI请求消息；
    接收服务器针对IMSI更新请求消息返回的响应消息；
    向智能卡传输所述响应消息，以使所述智能卡根据所述响应消息携带的信息执行智能卡IMSI更新操作；其中，所述智能卡为支持多IMSI的智能卡，所述智能卡IMSI更新操作包括：在智能卡中增加IMSI操作和/或从智能卡中删除IMSI操作。
  16. 如权利要求15所述的方法，其特征在于，在所述向服务器发送IMSI更新请求消息之前，所述方法还包括：向智能卡发送国际移动用户识别码IMSI更新命令，接收所述智能卡返回的IMSI更新请求信息，以便根据所述IMSI更新请求信息向服务器发送IMSI更新请求消息。
  17. 如权利要求15或16所述的方法，其特征在于，所述IMSI更新命令包括：基于信封命令的IMSI更新命令，和/或，所述IMSI更新请求消息通过空中下载OTA短消息的形式或承载独立协议的形式发送。
  18. 如权利要求16所述的方法，其特征在于：
    所述IMSI更新请求信息被加密，用户终端接收被加密的IMSI更新请求信息和用于安全性鉴定的信息；
    和/或
    所述根据所述响应消息携带的信息执行智能卡IMSI更新操作包括：
    对所述响应消息进行安全性鉴定，在所述安全性鉴定通过后，解密所述响应消息，并根据所述解密后信息执行智能卡IMSI更新操作。
PCT/CN2010/073885 2010-06-12 2010-06-12 支持多imsi的方法、装置和系统 Ceased WO2011153714A1 (zh)

Priority Applications (12)

Application Number Priority Date Filing Date Title
EP21186553.0A EP3962130B1 (en) 2010-06-12 2010-06-12 Method, apparatus, and system for supporting multiple imsis
EP19205832.9A EP3668133B1 (en) 2010-06-12 2010-06-12 Method, apparatus, and system for supporting multiple imsis
ES19205832T ES2898304T3 (es) 2010-06-12 2010-06-12 Método, aparato y sistema para soportar múltiples IMSI
PCT/CN2010/073885 WO2011153714A1 (zh) 2010-06-12 2010-06-12 支持多imsi的方法、装置和系统
EP23166700.7A EP4277237A3 (en) 2010-06-12 2010-06-12 Method, apparatus, and system for supporting multiple imsis
JP2013502984A JP2013527656A (ja) 2010-06-12 2010-06-12 複数のｉｍｓｉをサポートする方法、装置及びシステム
CN201080055036.XA CN102668689B (zh) 2010-06-12 2010-06-12 支持多imsi的方法、装置、用户终端和系统
EP10852707.8A EP2538746B1 (en) 2010-06-12 2010-06-12 Method, device and system for supporting multiple international mobile subscriber identities (imsis)
ES21186553T ES2951581T3 (es) 2010-06-12 2010-06-12 Método, aparato y sistema para soportar múltiples IMSI
US13/693,419 US8718711B2 (en) 2010-06-12 2012-12-04 Method, apparatus, and system for supporting multiple IMSIS
US17/405,904 USRE49635E1 (en) 2010-06-12 2021-08-18 Method, apparatus, and system for supporting multiple IMSIs
US18/235,723 USRE50578E1 (en) 2010-06-12 2023-08-18 Method, apparatus, and system for supporting multiple IMSIs

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/073885 WO2011153714A1 (zh) 2010-06-12 2010-06-12 支持多imsi的方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/693,419 Continuation US8718711B2 (en) 2010-06-12 2012-12-04 Method, apparatus, and system for supporting multiple IMSIS

Publications (1)

Publication Number Publication Date
WO2011153714A1 true WO2011153714A1 (zh) 2011-12-15

Family

ID=45097472

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/073885 Ceased WO2011153714A1 (zh) 2010-06-12 2010-06-12 支持多imsi的方法、装置和系统

Country Status (6)

Country Link
US (3) US8718711B2 (zh)
EP (4) EP3668133B1 (zh)
JP (1) JP2013527656A (zh)
CN (1) CN102668689B (zh)
ES (2) ES2951581T3 (zh)
WO (1) WO2011153714A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868992A (zh) * 2012-08-15 2013-01-09 北京握奇数据系统有限公司 终端信号屏蔽装置及方法、解除装置及方法、管理系统
DE102012016734A1 (de) * 2012-08-22 2014-02-27 Giesecke & Devrient Gmbh Verfahren zum Erhalten von Teilnehmeridentitätsdaten
DE102012020690A1 (de) * 2012-10-22 2014-04-24 Giesecke & Devrient Gmbh Verfahren zum Einbringen von Teilnehmeridentitätsdaten in ein Teilnehmeridentitätsmodul
CN103874051A (zh) * 2012-12-12 2014-06-18 中国联合网络通信集团有限公司 物联网预置资源处理方法及装置
JP2015509677A (ja) * 2012-02-24 2015-03-30 アルカテル−ルーセント スマートカードのパーソナライゼーション
JP2015534408A (ja) * 2012-10-29 2015-11-26 ジェムアルト エスアー 端末とリモートサーバとの間の、サードパーティのポータルを介した相互認証の方法
CN109842877A (zh) * 2019-04-09 2019-06-04 中国电子科技集团公司第三十研究所 一种在sim卡中实现imsi变更功能的方法
CN110944329A (zh) * 2019-11-28 2020-03-31 楚天龙股份有限公司 一种信息处理方法、终端和服务器

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9253630B2 (en) 2011-06-02 2016-02-02 Truphone Limited Identity management for mobile devices
US9603006B2 (en) 2011-09-19 2017-03-21 Truphone Limited Managing mobile device identities
US9686399B2 (en) * 2012-09-07 2017-06-20 Telefonaktiebolaget Lm Ericsson (Publ) Protection of a wireless communications device against unauthorized use
US9344875B2 (en) * 2012-11-19 2016-05-17 Qualcomm Incorporated Systems, apparatus, and methods for managing information in a smart storage device
US9661494B2 (en) * 2013-06-28 2017-05-23 Ntt Docomo, Inc. Control apparatus, control method, communication system and program
KR102235135B1 (ko) * 2013-11-12 2021-04-01 주식회사 엘지유플러스 사용자 단말의 네트워크 접속 정보 초기화 방법
US9525997B2 (en) 2013-11-25 2016-12-20 At&T Intellectual Property I, L.P. Method and apparatus for managing international mobile subscriber identity
EP2953388A1 (en) * 2014-06-06 2015-12-09 Buzzinbees Sas System and method for handling inactive SIM cards
EP3621332B1 (en) * 2014-04-18 2023-11-01 Huawei Technologies Co., Ltd. Method, terminal device, management server and system for distributing data of virtual subscriber identity module
CN107079282B (zh) 2014-11-21 2018-10-12 卡诺爱股份有限公司 用于提供多号码服务的方法
US9615250B2 (en) 2014-12-16 2017-04-04 Microsoft Technology Licensing, Llc Subscriber identification module pooling
WO2016108096A1 (en) * 2014-12-30 2016-07-07 Stmicroelectronics S.R.L. Methods for providing a response to a scp80 command requesting the execution of a proactive command, related universal integrated circuit card, mobile device, server and computer program product
KR102333395B1 (ko) * 2015-02-17 2021-12-03 삼성전자 주식회사 이동통신 시스템의 단말에서 프로파일 수신을 위한 방법 및 장치
US10334430B2 (en) * 2015-10-30 2019-06-25 Sharp Kabushiki Kaisha Information processing device, information processing method, and program
US9838991B1 (en) 2016-08-15 2017-12-05 At&T Intellectual Property I, L.P. Method and apparatus for managing mobile subscriber identification information according to registration requests
US9967732B2 (en) 2016-08-15 2018-05-08 At&T Intellectual Property I, L.P. Method and apparatus for managing mobile subscriber identification information according to registration errors
US9794905B1 (en) 2016-09-14 2017-10-17 At&T Mobility Ii Llc Method and apparatus for assigning mobile subscriber identification information to multiple devices according to location
US9843922B1 (en) * 2016-09-14 2017-12-12 At&T Intellectual Property I, L.P. Method and apparatus for utilizing mobile subscriber identification information with multiple devices based on registration errors
US9924347B1 (en) 2016-09-14 2018-03-20 At&T Intellectual Property I, L.P. Method and apparatus for reassigning mobile subscriber identification information
US10015764B2 (en) 2016-09-14 2018-07-03 At&T Intellectual Property I, L.P. Method and apparatus for assigning mobile subscriber identification information to multiple devices
US9814010B1 (en) 2016-09-14 2017-11-07 At&T Intellectual Property I, L.P. Method and apparatus for utilizing mobile subscriber identification information with multiple devices based on registration requests
US9906943B1 (en) 2016-09-29 2018-02-27 At&T Intellectual Property I, L.P. Method and apparatus for provisioning mobile subscriber identification information to multiple devices and provisioning network elements
US9918220B1 (en) 2016-10-17 2018-03-13 At&T Intellectual Property I, L.P. Method and apparatus for managing and reusing mobile subscriber identification information to multiple devices
US10070303B2 (en) 2016-11-11 2018-09-04 At&T Intellectual Property I, L.P. Method and apparatus for provisioning of multiple devices with mobile subscriber identification information
US10136305B2 (en) 2016-12-01 2018-11-20 At&T Intellectual Property I, L.P. Method and apparatus for using mobile subscriber identification information for multiple device profiles for a device
US10341842B2 (en) 2016-12-01 2019-07-02 At&T Intellectual Property I, L.P. Method and apparatus for using temporary mobile subscriber identification information in a device to provide services for a limited time period
US10070407B2 (en) 2016-12-01 2018-09-04 At&T Intellectual Property I, L.P. Method and apparatus for using active and inactive mobile subscriber identification information in a device to provide services for a limited time period
US10231204B2 (en) 2016-12-05 2019-03-12 At&T Intellectual Property I, L.P. Methods, systems, and devices for registering a communication device utilizing a virtual network
US9949113B1 (en) * 2017-06-02 2018-04-17 Apple Inc. Updating profiles for secondary wireless devices
CN108804125A (zh) * 2018-06-29 2018-11-13 四川科道芯国智能技术股份有限公司 应用管理方法、装置及终端设备
CN115866606B (zh) * 2022-11-25 2026-03-27 西安广和通无线软件有限公司 一种短信处理方法、装置、设备及可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1787681A (zh) * 2004-12-10 2006-06-14 华为技术有限公司 一种切换国际移动用户标识的方法
WO2008040848A1 (en) * 2006-10-05 2008-04-10 Elisa Oyj Control of a multisubscription
WO2009022978A1 (en) * 2007-08-16 2009-02-19 Telefonaktiebolaget L M Ericsson (Publ) A device and a method for multiple numbers for one user
CN101720085A (zh) * 2009-11-18 2010-06-02 深圳华为通信技术有限公司 智能卡应用方法、装置

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2756132B1 (fr) * 1996-11-19 1998-12-11 Alsthom Cge Alcatel Module d'identification d'abonne pour terminal mobile de telecommunications, et terminal mobile de telecommunications
FI104681B (fi) * 1997-06-04 2000-04-14 Sonera Oyj Menetelmä tilaajaidentiteettimoduulin hallitsemiseksi tietoliikennejärjestelmässä ja tietoliikennejärjestelmä
DE19828735A1 (de) 1998-06-29 1999-12-30 Giesecke & Devrient Gmbh Mobilfunksystem mit dynamisch änderbarer Identität
EP1045598A1 (en) 1999-04-12 2000-10-18 Lucent Technologies Inc. Personal mobility registration system for registration of a users identity in a telecommunications terminal
CN1281086C (zh) * 2002-03-12 2006-10-18 斯伦贝谢（北京）智能卡科技有限公司 用户识别模块卡、空中激活用户识别模块卡的方法和系统
JP3637337B2 (ja) * 2002-07-31 2005-04-13 株式会社東芝 移動通信端末
US7099309B2 (en) * 2003-10-10 2006-08-29 Air-Bank Llc Using a handheld communication device with a hot spot network
FR2871020B1 (fr) * 2004-05-27 2006-07-07 Radiotelephone Sfr Procede et systeme de duplication securisee des informations d'une carte sim vers au moins un objet communicant
KR100585791B1 (ko) 2004-12-28 2006-06-07 엘지전자 주식회사 휴대단말기의 다중 임시정보 운용장치 및 방법
EP1804539A1 (en) * 2005-12-14 2007-07-04 Research In Motion Limited Apparatus, and associated method, for facilitating formation of a call connection in a radio communication system with a service center identified by a short dialing code
EP2103165A1 (en) * 2006-12-21 2009-09-23 Telefonaktiebolaget LM Ericsson (PUBL) Imsi handling system
CN101312583B (zh) 2007-05-21 2011-07-06 展讯通信（上海）有限公司 一种手机加密选择方法、系统
JP4894925B2 (ja) * 2007-07-30 2012-03-14 富士通株式会社 携帯端末装置の初期化方法
CN101399659B (zh) 2007-09-30 2011-05-25 中兴通讯股份有限公司 用户识别模块与终端之间的密钥认证方法和装置
JP5215888B2 (ja) 2009-01-27 2013-06-19 株式会社エヌ・ティ・ティ・ドコモ 無線通信システム及び方法
US8306532B2 (en) 2009-06-26 2012-11-06 Cellco Partnership System and method for using multiple subscriber identities to provide differentiated services to subscribers
CN101692730B (zh) 2009-09-01 2012-02-01 厦门敏讯信息技术股份有限公司 一种sim卡与专用公话终端的加密交互方式与专用公话终端
CN102036222B (zh) 2009-09-25 2015-05-13 中兴通讯股份有限公司 一种m2m设备归属网络运营商变更的方法和系统
US8988249B2 (en) 2009-10-08 2015-03-24 Connectif Solutions Inc. System, method and integrated circuit chip for wireless multi-network meter reading
US8863240B2 (en) * 2010-10-20 2014-10-14 T-Mobile Usa, Inc. Method and system for smart card migration

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1787681A (zh) * 2004-12-10 2006-06-14 华为技术有限公司 一种切换国际移动用户标识的方法
WO2008040848A1 (en) * 2006-10-05 2008-04-10 Elisa Oyj Control of a multisubscription
WO2009022978A1 (en) * 2007-08-16 2009-02-19 Telefonaktiebolaget L M Ericsson (Publ) A device and a method for multiple numbers for one user
CN101720085A (zh) * 2009-11-18 2010-06-02 深圳华为通信技术有限公司 智能卡应用方法、装置

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015509677A (ja) * 2012-02-24 2015-03-30 アルカテル−ルーセント スマートカードのパーソナライゼーション
US9451441B2 (en) 2012-02-24 2016-09-20 Alcatel Lucent Smart card personnalization
CN102868992A (zh) * 2012-08-15 2013-01-09 北京握奇数据系统有限公司 终端信号屏蔽装置及方法、解除装置及方法、管理系统
DE102012016734A1 (de) * 2012-08-22 2014-02-27 Giesecke & Devrient Gmbh Verfahren zum Erhalten von Teilnehmeridentitätsdaten
DE102012020690A1 (de) * 2012-10-22 2014-04-24 Giesecke & Devrient Gmbh Verfahren zum Einbringen von Teilnehmeridentitätsdaten in ein Teilnehmeridentitätsmodul
WO2014063796A1 (de) * 2012-10-22 2014-05-01 Giesecke & Devrient Gmbh Verfahren zum einbringen von teilnehmeridentitätsdaten in ein teilnehmeridentitätsmodul
CN104737566A (zh) * 2012-10-22 2015-06-24 德国捷德有限公司 用于将用户身份数据引入到用户身份模块中的方法
US9439076B2 (en) 2012-10-22 2016-09-06 Giesecke & Devrient Gmbh Method for incorporating subscriber identity data into a subscriber identity module
JP2015534408A (ja) * 2012-10-29 2015-11-26 ジェムアルト エスアー 端末とリモートサーバとの間の、サードパーティのポータルを介した相互認証の方法
CN103874051A (zh) * 2012-12-12 2014-06-18 中国联合网络通信集团有限公司 物联网预置资源处理方法及装置
CN109842877A (zh) * 2019-04-09 2019-06-04 中国电子科技集团公司第三十研究所 一种在sim卡中实现imsi变更功能的方法
CN110944329A (zh) * 2019-11-28 2020-03-31 楚天龙股份有限公司 一种信息处理方法、终端和服务器

Also Published As

Publication number Publication date
US20130095795A1 (en) 2013-04-18
JP2013527656A (ja) 2013-06-27
USRE49635E1 (en) 2023-08-29
EP3668133B1 (en) 2021-08-25
EP3962130B1 (en) 2023-05-03
ES2898304T3 (es) 2022-03-07
CN102668689A (zh) 2012-09-12
US8718711B2 (en) 2014-05-06
EP2538746B1 (en) 2020-01-08
CN102668689B (zh) 2016-08-03
EP2538746A1 (en) 2012-12-26
EP2538746A4 (en) 2013-03-06
EP4277237A2 (en) 2023-11-15
ES2951581T3 (es) 2023-10-24
EP3668133A1 (en) 2020-06-17
EP4277237A3 (en) 2023-12-13
EP3962130A1 (en) 2022-03-02
USRE50578E1 (en) 2025-09-02

Similar Documents

Publication Publication Date Title
WO2011153714A1 (zh) 支持多imsi的方法、装置和系统
WO2018233352A1 (zh) 数据传输方法、装置、终端以及计算机可读存储介质
WO2013025085A2 (en) Apparatus and method for supporting family cloud in cloud computing system
WO2020147383A1 (zh) 基于区块链系统的流程审批方法、装置、系统及非易失性存储介质
WO2012141556A2 (en) Machine-to-machine node erase procedure
WO2014189318A1 (en) Proxy based communication scheme in docking structure
WO2013183971A1 (en) Method and system for selective protection of data exchanged between user equipment and network
WO2020224246A1 (zh) 基于区块链的数据管理方法、装置、设备和存储介质
WO2009107994A2 (ko) 이동 통신 단말기를 위한 개인 정보 제어 서비스 제공 방법 및 시스템
WO2021112603A1 (en) Method and electronic device for managing digital keys
WO2018149356A1 (zh) 一种基于rsp的lpa应用实现方法、实现系统及终端
WO2016010312A1 (ko) Euicc의 프로파일 설치 방법 및 장치
WO2015072788A1 (en) Method and apparatus for managing security key in a near fieldd2d communication system
WO2018145357A1 (zh) 邮件加密的方法及系统
WO2011129635A2 (ko) 이동통신 시스템에서 응용 서비스를 제공하는 방법 및 장치
WO2014063455A1 (zh) 即时通信方法和系统
WO2009145499A2 (en) Method and apparatus for managing tokens for digital rights management
WO2020253120A1 (zh) 网页注册方法、系统、设备和计算机存储介质
WO2021235893A1 (ko) 전자 디바이스 및 전자 디바이스가 레인징 기반 서비스를 제공하는 방법
WO2019182377A1 (ko) 블록체인 기반 암호화폐의 트랜잭션에 이용되는 주소 정보 생성 방법, 전자 장치 및 컴퓨터 판독 가능한 기록 매체
WO2025005456A1 (en) Method and device of multimedia playback for virtual system
WO2018076293A1 (zh) 多媒体通信的参数调整方法、装置及移动终端
WO2017185647A1 (zh) 基于SoftSIM的IMSI号码管理及呼叫方法、服务器及网络侧设备
WO2012109985A1 (zh) 基于java的移动终端鉴权系统和方法、服务器及终端
WO2018084548A1 (ko) 통신 시스템에서 발신자를 인증하기 위한 장치 및 방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080055036.X

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10852707

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2010852707

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013502984

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE