WO2015081884A1 - 嵌入式通用集成电路卡的管理方法、相关设备及系统 - Google Patents
嵌入式通用集成电路卡的管理方法、相关设备及系统 Download PDFInfo
- Publication number
- WO2015081884A1 WO2015081884A1 PCT/CN2014/093119 CN2014093119W WO2015081884A1 WO 2015081884 A1 WO2015081884 A1 WO 2015081884A1 CN 2014093119 W CN2014093119 W CN 2014093119W WO 2015081884 A1 WO2015081884 A1 WO 2015081884A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- euicc
- entity
- profile
- communication connection
- target
- Prior art date
Links
Images
Classifications
-
- 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/20—Transfer of user or subscriber data
- H04W8/205—Transfer to or from user equipment or user record carrier
-
- 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
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
-
- 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
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/30—Security of mobile devices; Security of mobile applications
- H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/30—Security of mobile devices; Security of mobile applications
- H04W12/37—Managing security policies for mobile devices or for controlling mobile applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42136—Administration or customisation of services
- H04M3/42178—Administration or customisation of services by downloading data to substation equipment
Definitions
- the present invention relates to the field of communications, and in particular, to a method, a related device and a system for managing an embedded universal integrated circuit card.
- UICC Universal Integrated Circuit Card
- USIM Universal Integrated Circuit Card
- SIM card SIM card
- RUIM card embedded UICC
- embedded means that the UICC card, USIM card, SIM card or RUIM card is not used.
- the card holder is inserted into the M2M terminal, but is directly soldered or embedded on the M2M terminal board.
- embedded cards are usually required for shockproof or miniaturization of M2M terminals.
- eUICC embedded UICC
- M2M terminals are usually in outdoor or remote venues or in harsh environments. Since the eUICC itself is embedded in the user equipment, it is difficult to perform replacement operations. Therefore, the network subscription change for these M2M terminals becomes a problem, and there is an urgent need for a remote and secure method for configuring network access credential information to the eUICC, and needs to be able to proceed from one MNO (mobile network operator) to another. MNO's network signing changes.
- SM refers to the subscription manager
- DP refers to data preparation
- SR refers to secure routing.
- a profile is a combination of file structure, data, and application.
- An Enabled Profile whose files and/or applications (such as network access applications) can be selected via the UICC-Terminal interface.
- a profile is called a Provisioning profile. After the Provisioning profile is installed on the eUICC, it can be used to access the communication network, thus managing eUICC between the eUICC and remote entities (such as SM-SR, SM-DP).
- Profile management provides transport capabilities.
- a profile is called an operational profile, and the Operational Profile contains one or more network access applications and Network access credentials.
- the SM-DP entity is responsible for generating the profile and downloading and installing the profile to the eUICC.
- the SM-DP can also be called a profile installer.
- the SM-SR entity is responsible for managing the profile on the eUICC and is also responsible for ensuring the security of communication between the eUICC and remote entities (such as SM-SR, SM-DP).
- the SM-SR can also be called a profile manager.
- the MNO mobile operator
- the eUICC may be ordered by the communication module provider, the terminal provider, the network operator, or the M2M industry customer to the eUICC provider, and the eUICC is embedded in the M2M terminal (also referred to as the user equipment). It should be noted that the eUICC is applicable not only to the M2M terminal but also to the non-M2M terminal or the traditional terminal, such as a smart phone. The eUICC is beneficial to the design of the intelligent designer of the smart phone, and is also convenient for the user to sign the new one conveniently. Operator. The number of eUICCs ordered by the same customer may be very large, and the applicant finds that the prior art does not provide a method for managing batch eUICC.
- the technical problem to be solved by the present invention is to provide a management method, related device and system for an embedded universal integrated circuit card. It can realize the management of batch eUICC.
- the first aspect of the present invention provides a method for managing an embedded universal integrated circuit card, including:
- the subscription manager-secure routing SM-SR entity sends a push request including a trigger message and at least one user identity to the public land mobile network PLMN/push server, indicating that the PLMN/push server targets the target pointed to by the at least one user identity
- the trigger card is used to trigger the target eUICC to initiate communication with the SM-SR entity.
- the SM-SR entity performs a management operation on the target eUICC through the communication connection.
- the trigger information includes the Identification information and/or address information of the SM-SR entity.
- the trigger message includes:
- the eUICC manages an operation type and/or access control information, and the access control information is used by the target eUICC to initiate scheduling of communication with the SM-SR.
- the eUICC management operation type includes:
- the access control information includes:
- the access control information is calculated by the SM-SR entity according to its own load information.
- the SM-SR entity sends the trigger message and the at least one user identifier to the PLMN/push server Before the step of pushing the request, it also includes:
- an eUICC management service request sent by an external entity where the eUICC management service request includes at least one eUICC identifier, where the SM-SR entity queries at least one user identifier associated with the at least one eUICC identifier;
- the SM-SR entity receives an eUICC management service request sent by an external entity, where the eUICC management service request includes at least one user identifier and at least one eUICC identifier.
- the method further includes:
- the SM-SR entity returns to the external entity an eUICC identity of at least one target eUICC that successfully establishes a communication connection.
- the user identifier includes: an international mobile subscriber identity IMSI, a mobile subscriber Identification number MSISDN, public user ID or private user ID.
- a second aspect of the present invention provides a method for managing an embedded universal integrated circuit card, including:
- the embedded universal integrated circuit card eUICC After receiving the trigger message of the subscription manager-secure route SM-SR entity push, the embedded universal integrated circuit card eUICC establishes a communication connection with the SM-SR entity;
- the trigger message includes identification information and/or address information of the SM-SR entity.
- the trigger message includes:
- the eUICC manages an operation type and/or access control information for the scheduling of establishing a communication connection with the SM-SR entity.
- the eUICC management operation type includes:
- the access control information includes:
- the step of establishing a communication connection with the SM-SR entity includes:
- the eUICC generates an access time point according to the access control information
- the eUICC initiates a communication connection request to the SM-SR at the access time point, and establishes a communication connection.
- the eUICC before the eUICC receives the trigger message sent by the SM-SR entity, the eUICC further includes:
- the user profile device in the eUICC is configured to be attached to the carrier network by the user profile where the eUICC is located.
- a third aspect of the present invention provides an SM-SR entity, including:
- a push module configured to send, to the public land mobile network PLMN/push server, a push request including a trigger message and at least one user identifier, indicating the target embedded universal integrated circuit card pointed by the PLMN/push server to the at least one user identifier
- the eUICC pushes the trigger message, where the trigger message is used to trigger the target eUICC to initiate communication with the SM-SR entity;
- connection module configured to establish a communication connection with the target eUICC
- a management module configured to perform a management operation on the target eUICC through the communication connection.
- the trigger information includes identification information and/or address information of the SM-SR entity.
- the trigger message includes:
- the eUICC manages an operation type and/or access control information, and the access control information is used by the target eUICC to initiate scheduling of communication with the SM-SR.
- the eUICC management operation type includes:
- the access control information includes:
- the pushing module is configured to calculate the access control information according to the load information of the SM-SR entity.
- a first receiving module configured to receive an eUICC management service request sent by an external entity, where the eUICC management service request includes at least one eUICC identifier, where the SM-SR entity queries at least one user identifier associated with the at least one eUICC identifier;
- a second receiving module configured to receive an eUICC management service request sent by an external entity, where The eUICC management service request includes at least one user identifier;
- a third receiving module configured to receive an eUICC management service request sent by an external entity, where the eUICC management service request includes at least one user identifier and at least one eUICC identifier.
- the method further includes:
- a returning module configured to return, to the external entity, an eUICC identifier of the at least one target eUICC that successfully establishes a communication connection.
- the user identifier includes an International Mobile Subscriber Identity (IMSI), a Mobile Subscriber Identity (MSISDN), a public subscriber identity, or Private user ID.
- IMSI International Mobile Subscriber Identity
- MSISDN Mobile Subscriber Identity
- public subscriber identity a public subscriber identity
- Private user ID a private user ID
- a fourth aspect of the present invention provides an eUICC, including:
- a first module configured to establish a communication connection with the SM-SR entity after receiving a trigger message sent by the subscription manager-secure route SM-SR entity;
- a second module configured to acquire, by using the communication connection, a management operation of the eUICC by the SM-SR entity.
- the trigger message includes:
- the eUICC manages an operation type and/or access control information for the scheduling of establishing a communication connection with the SM-SR entity.
- the trigger message includes:
- the eUICC manages an operation type and/or access control information for the scheduling of establishing a communication connection with the SM-SR entity.
- the eUICC management operation type includes:
- the access control information includes:
- the first The module is configured to generate an access time point according to the access control information; initiate a communication connection request to the SM-SR at the access time point, and establish a communication connection.
- the method further includes:
- the third module is configured to attach the user equipment where the eUICC is located to the carrier network by using a configuration profile or an operation profile.
- a fifth aspect of the present invention provides a communication system comprising any of the SM-SR entities described above and any one of the embedded universal integrated circuit cards.
- the SM-SR entity sends a trigger message to the at least one target eUICC via the carrier network/push server to trigger the target eUICC that receives the trigger message to initiate a communication connection with the SM-SR entity, the SM-SR entity and the target eUICC
- the established communication connection performs management operations on the target eUICC, which can implement batch management of the eUICC and improve management efficiency.
- 1 is a logical architecture diagram of a prior art eUICC
- FIG. 2 is a schematic flow chart of a method for managing an embedded universal integrated circuit card according to a first embodiment of the present invention
- FIG. 3 is a schematic flow chart of a method for managing an embedded universal integrated circuit card according to a second embodiment of the present invention.
- FIG. 4 is a schematic flow chart of a method for managing an embedded universal integrated circuit card according to a third embodiment of the present invention.
- FIG. 5 is a schematic flow chart of a method for managing an embedded universal integrated circuit card according to a fourth embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of an SM-SR entity according to a first embodiment of the present invention.
- FIG. 7 is a schematic structural diagram of an SM-SR entity according to a second embodiment of the present invention.
- FIG. 8 is a schematic structural diagram of an SM-SR entity according to a third embodiment of the present invention.
- FIG. 9 is a schematic structural diagram of an eUICC according to a first embodiment of the present invention.
- FIG. 10 is a schematic structural diagram of an eUICC according to a second embodiment of the present invention.
- FIG. 11 is a schematic structural diagram of an eUICC according to a third embodiment of the present invention.
- FIG. 2 is a flowchart of a method for managing an embedded universal integrated circuit card according to an embodiment of the present invention, specifically including:
- the SM-SR sends a push message to the PLMN/Push Server.
- the PLMN/Push Server sends a trigger message to the target eUICC.
- the SM-SR establishes a communication connection with the target eUICC.
- a management operation flow is performed between S104, the SM-SR, and the target eUICC.
- an embedded universal integrated circuit card (eUICC, embedded universal integrated circuit card) is installed in the user equipment, and after the eUICC is activated, the profile (provisioning profile or operational profile) stored by the eUICC is used.
- the user equipment where the eUICC is located is attached to the carrier network.
- the carrier network is the same as or different from the PLMN (Public Land Mobile Network, PLMN, public land mobile network).
- PLMN Public Land Mobile Network, PLMN, public land mobile network.
- the PLMN is the home PLMN of the user equipment, and the carrier network is the PLMN currently attached to the user equipment.
- the SM-SR entity may send a push message to the PLMN/Push Server.
- the push message includes a trigger message and at least one user identifier.
- the PLMN/push server When the PLMN/push server receives the push message, parses out the push message. Triggering a message and sending a trigger message to the target pointed by the at least one user identification
- the eUICC when the target eUICC detects the trigger message, initiates a communication connection request to the SM-SR entity, and the SM-SR entity responds to the communication connection request, and successfully establishes a communication connection with the target eUICC in the user equipment, and the subsequent SM-SR entity and target Management operations between eUICCs are made through established communication connections.
- the management operation may be a profile installation, a profile download, a profile state change, and an SM-SR entity change associated with the eUICC in the target eUICC of the user equipment.
- the user identifier may be an IMSI (International Mobile Subscriber Identity, IMSI, International Mobile Subscriber Identity) or an MSISDN (Mobile Station International ISDN Number, MSISDN, Mobile Subscriber Identification Number) or a public user identifier or a private user identifier.
- IMSI International Mobile Subscriber Identity
- MSISDN Mobile Station International ISDN Number
- MSISDN Mobile Subscriber Identification Number
- FIG. 3 is a schematic flowchart of a method for managing an eUICC according to a second embodiment of the present invention.
- a network side initiates a profile installation operation, where the method specifically includes:
- the user equipment where the target eUICC is located attaches the profile in the target eUICC to the PLMN.
- the user equipment in which the target eUICC is located initiates a network attach request to the PLMN, and the network attach may be a CS (Circuit Switched) and/or a PS (Packet Switched) attach.
- CS Circuit Switched
- PS Packet Switched
- the SM-DP entity sends an eUICC management service request to the SM-SR entity.
- the eUICC management service request includes operation type information and an eUICC identifier
- the operation type may be profile download or profile installation
- the eUICC identifier may be an identifier of one or more target eUICCs.
- the operation type in this embodiment is profile installation
- the EID list includes at least one eUICC identifier.
- the eUICC management service request includes at least one user identifier, for example, the user identifier includes an IMSI or an MSISDN or a public user identifier or a private user identifier.
- the SM-SR entity sends a push request to the PLMN/Push Server push server.
- the SM-SR entity queries the user identifier corresponding to the eUICC identifier, and the SM-SR entity generates a trigger message according to the operation type information, and generates a trigger message according to the operation type information, and according to the user
- the identification and trigger messages generate a push request, and the push request includes a user identifier and a trigger message.
- the push request can be expressed as a push request (SID list, trigger (profile installation)), wherein the SID list is a user identifier list, and the table includes at least one target eUICC user identifier, and the trigger() is a trigger.
- the profile installation in the trigger message is the operation type information.
- the user ID of the target eUICC is used for the PLMN/Push Server Push Trigger message to the target eUICC.
- the trigger message further includes access control information, where the access control information is used to initiate a communication between the target eUICC and the SM-SR entity, that is, a time point for controlling the target eUICC to initiate communication with the SM-SR entity,
- the incoming control information includes back-off timer information or time window information.
- the trigger message may be represented as a trigger (profile installation, back_off time), where the back-off time is access control information, and the access control information may be generated by the SM-SR entity according to its own load information, for example, the load information is assumed to be The maximum load-bearing load of the SM-SR entity.
- the SM-SR obtains the current load information as 50% of the maximum load.
- the corresponding access control information is queried for 30 minutes according to the preset mapping relationship.
- the current load information is 60% of the maximum load, and the corresponding access control information is 40 minutes according to the preset mapping association.
- the push request is directly generated according to the operation type information and the user identifier of the eUICC management service request.
- the PLMN/push server sends a trigger message to the target eUICC.
- the PLMN/push server parses the user identifier in the push message, and sends a trigger message to the target eUICC to which the user identifier points.
- the PLMN/push server may send a trigger message to the target eUICC pointed to by the user identifier based on the CS or PS mode.
- the target eUICC generates an access time point for initiating communication with the SM-SR entity.
- the user equipment parses the access control information in the trigger message. For example, if the access control information is a time window (for example, within one hour), the eUICC generates an access time point within one hour, and the eUICC is connected. A communication connection request with the SM-SR is initiated at the point in time.
- the access control information is a time window (for example, within one hour)
- the eUICC generates an access time point within one hour, and the eUICC is connected.
- a communication connection request with the SM-SR is initiated at the point in time.
- a communication connection is established between the SR-SM entity and the target eUICC, and the communication connection may be a secure communication connection based on SSL or HTTPS.
- the SM-SR side maintains an eUICC identifier list in which the eUICC identifier of the target eUICC that successfully establishes the communication connection is recorded.
- the target eUICC initiates a service request to the SM-SR entity.
- the target eUICC parses the operation type information in the trigger message, and initiates a service request to the SM-SR entity according to the operation type information, where the service request carries the same as in the trigger message.
- Operation type information e.g., the service request further includes a management mode, where the service request is initiated, that is, a push (network-side initiated) or a pull (eUICC-side initiated).
- the service request may be represented as a service request (profile installation, Push), the profile installation is the operation type information, and the push is the management mode.
- the trigger message includes the identifier information and/or the address information (for example, an IP address, a URI) of the SM-SR entity, and the target eUICC determines the sending object of the service request according to the identifier information and/or the address information.
- the address information for example, an IP address, a URI
- S208 Call a corresponding service request of the corresponding processing module, and perform congestion control on the service request.
- the operation type information in the SM-SR entity parsing service request is a profile installation, and the SR-SM entity invokes a processing module corresponding to the profile installation to respond, and performs congestion control on the service request.
- the congestion control method may be: performing congestion control according to the operation type information and/or the management mode, for example, querying different priority levels corresponding to the operation type information and/or the management mode according to the preset mapping relationship, according to the priority order of the query. Process the batch of business requests initiated by the target eUICC.
- the destination eUICC sends a failure message to the service request, and the failure message carries the SM-SR entity.
- the status information and the retry time enable the target eUICC to re-initiate the service request to the SM-SR entity after the retry time.
- the failure message can be expressed as a failure message (busy, try_again time), and the busy is a status message indicating busy; try_again Time is the retry time.
- the SM-SR entity sends an eUICC management service response.
- the SM-SR entity obtains the eUICC identifier of the target eUICC that the service request is accepted, and generates an eUICC identifier list, where the table includes at least one eUICC identifier of the target eUICC, where the management service response carries the operation type information and the eUICC generated here.
- a list of identifiers A list of identifiers.
- the SM-SR entity instructs the target eUICC to perform profile container creation.
- the SM-SR entity sends a profile container creation confirmation message to the SM-DP.
- the SM-SR entity obtains the identifier of the target eUICC that the profile container is successfully created, and generates an eUICC identifier list, where the table includes at least one target that successfully creates the profile container.
- the eUICC identifier of the eUICC the SM-SR entity adds the eUICC identifier list generated here to the profile container creation confirmation message and sends it to the SM-DP entity.
- the profile container is initialized, the profile is downloaded and installed to the profile container.
- the SM-DP entity sends the profile to the target eUICC, so that the target eUICC installs the profile into the corresponding profile container, and returns a success message of successfully installing the profile to the SM-DP entity.
- the SM-DP entity obtains an eUICC identifier of the target eUICC that successfully obtains the profile according to the received success message, generates an eUICC identifier list, adds the generated eUICC list to the profile installation result, and sends the result to the SM-DP. entity.
- FIG. 4 is a schematic flowchart of a method for managing an embedded universal integrated circuit card according to a third embodiment of the present invention.
- an SR-SM entity change operation is initiated by the network side, where the method specifically includes:
- the user equipment in which the target eUICC is located attaches the profile in the target eUICC to the PLMN.
- the user equipment where the target eUICC is located initiates a network attach request to the PLMN, and the network attachment may be CS attach and/or PS attach.
- the MNO sends an eUICC management service request to the SM-SR entity.
- the eUICC management service request includes the operation type information, the eUICC identifier, and the PMC of the new SM-SR entity.
- the eUICC management service request can be expressed as a management service request (SM-SR change, EID list, PMC), SM.
- SM-SR change is the operation type information, here represents the SM-SR entity change operation
- EID list is the eUICC identifier list
- the table includes the eUICC identifier of at least one target eUICC
- the PMC is the PMC of the new SM-SR entity.
- the eUICC management service request includes the operation type information, the user identifier, and the PMC of the new SM-SR entity.
- the format of the eUICC management service request may be a management service request (SM-SR change, SID list, PMC).
- the SM-SR change is the operation type information
- the SID list is the user identification list
- the table includes the user identifier of the at least one target eUICC
- the PMC is the PMC of the new SM-SR entity.
- the user identity includes IMSI or MSISDN or public user ID or private user ID.
- the eUICC management service request may not include operation type information, and the operation type indicated by the eUICC management service may be identified according to a string of the eUICC management service request.
- the format of the eUICC management service request is an SM-SR change request (EID list, PMC). ).
- the SM-SR entity sends a push message to the PLMN/push server.
- the eUICC management service request includes the eUICC identifier
- the corresponding user identifier is queried according to the eUICC identifier, thereby obtaining the user identifier of the target eUICC
- the target eUICC is directly obtained from the eUICC management service request.
- User ID the operation type information is obtained from the eUICC management service request
- the trigger message is generated according to the operation type information
- the push message is generated according to the user identifier and the trigger message.
- the format of the push request may be a push request (SID list trigger (SM-SR) Change)
- SID list is a user identification list
- the table includes at least one user identifier of the target eUICC
- trigger() is a trigger message
- SM-SR change is operation type information, and here represents an SM-SR entity change operation.
- the trigger message further includes access control information, where the access control information is used for scheduling that the target eUICC initiates communication with the SM-SR, that is, a time point at which the user controls the target eUICC to initiate communication with the SM-SR entity, and the access control information
- the back-up timer information may be, for example, the push request may be in the form of a push request (SID list, trigger-type change (SID), and the access control information may be generated by the SM-SR entity according to the load information of the SM-SR entity.
- the SM-SR obtains the current load information as 50% of the total processing capability, and queries the corresponding access control information according to the preset mapping relationship to 30 minutes; and obtains the current load information of the current processing capacity as the total processing capability. 60%, according to the preset mapping association query to the corresponding access control information for 40 minutes.
- the PLMN/push server pushes a trigger message to the target eUICC.
- the PLMN/push server parses the trigger message and the user identifier in the obtained push request, and sends a trigger message to the target eUICC pointed to by the user identifier, and the PLMN/push server may send the target eUICC pointed to by the user identifier according to the CS or PS mode. Trigger a message.
- the target eUICC generates an access time point for establishing a communication connection with the SM-SR.
- the target eUICC generates a random number in the interval [0, 1], and multiplies the generated random number by The incoming control information is obtained at the access time point, so that the target eUICC initiates a communication connection request with the SM-SR at the access time point.
- the generation of the random number and the calculation of the access time point can be performed by the SM-SR entity, the SM-SR entity adds the calculated access time point to the trigger message, and the target eUICC parses the access in the trigger message.
- the time point for example, the format of the trigger message is trigger (SM-SR change, random time), and the random time is the access time point.
- the access time of the target eUICC to access the SM-SR entity is controlled by the access time point, which can effectively prevent a large number of target eUICCs from simultaneously accessing the SM-SR entity and causing congestion.
- the SM-SR establishes a communication connection with the target eUICC.
- the target eUICC initiates a communication connection request to the SM-SR entity at the corresponding access time point, and the SM-SR entity responds to the communication connection request to establish a communication connection with the target eUICC.
- the SM-SR entity maintains an eUICC identifier list in which the identifier of the target eUICC that successfully establishes a communication connection with itself is recorded.
- the target eUICC initiates a service request to the SM-SR entity.
- the target eUICC parses the operation type information in the trigger message, and initiates a service request to the SM-SR entity according to the operation type information, where the service request carries the same operation type information as in the trigger message.
- the service request includes a management mode, where the service request is initiated, that is, push (network-side initiation) or pull (eUICC-side initiation).
- the service request may be represented as a business request (profile installation, Push), the profile installation is the operation type information, and the push is the management mode.
- the operation type information is SM-SR change
- the SR-SM invokes a processing module corresponding to the profile installation to respond, and performs congestion control on the service request.
- the congestion control method may be: performing congestion control according to the operation type information and/or the management mode, for example, querying the operation type information and the different priorities corresponding to the management mode according to the preset mapping relationship.
- the device sends a failure message to the target eUICC, where the failure message carries the status information of the SM-SR entity and the retry time.
- the target eUICC re-initiates a service request to the SM-SR entity after the retry time.
- the SM-SR entity sends an eUICC management service response to the MNO.
- the SM-SR entity maintains an eUICC identifier list, where the eUICC identifier list is an eUICC identifier of the target eUICC received by the service request, and the eUICC identifier list is added to the eUICC management service response and sent to the MNO.
- the format of the eUICC management service response may be a management service response (EID list), where the EID list indicates the eUICC identifier of the target eUICC corresponding to the accepted service request.
- the SM-SR entity sends the PMC to the target eUICC, so that the target eUICC installs the PMC of the new SR-SM entity, and after the installation is successful, returns a success message to the SM-SR entity.
- the SM-SR entity adds the identifier of the target eUICC that successfully installs the PMC to the SM-SR change result, and sends the SM-SR change result to the MNO.
- the target eUICC initiates a service request
- the operation type information in the service request is profile installation.
- the method includes:
- the target eUICC initiates an attach request to the PLMN/push server, and attaches to the home PLMN by using the PP stored by itself.
- the target eUICC initiates a service request to the SM-SR entity, where the service request includes operation type information, a management mode, and an identifier of the SM-DP entity.
- the SM-SR entity invokes a corresponding service request of the corresponding module, and performs congestion control on the service request.
- the SM-SR entity sends a download request to the SM-DP.
- the download request includes an identifier of the target eUICC that successfully connects the communication connection.
- the SM-DP entity returns a download confirmation message to the SM-SR entity.
- the SM-DP entity sends a profile installation result to the SM-SR entity.
- FIG. 6 is a schematic structural diagram of an SM-SR entity according to a first embodiment of the present invention.
- the SM-SR entity includes a push module 10, a connection module 20, and a management module 30, where
- the pushing module 10 is configured to send, to the public land mobile network PLMN/push server, a push request including a trigger message and at least one user identifier, indicating that the PLMN/push server points to the target embedded general-purpose integrated circuit pointed to by the at least one user identifier
- the card eUICC pushes the trigger message, where the trigger message is used to trigger the target eUICC to initiate communication with the SM-SR entity;
- the connection module 20 is configured to establish a communication connection with the target eUICC
- the management module 30 is configured to perform a management operation on the target eUICC through the communication connection.
- a schematic structural diagram of an SM-SR entity includes, in addition to the push module 10, the connection module 20, and the management module 30, a receiving module 40, a second receiving module 50, a third receiving module 60, and a returning module 70, wherein
- the first receiving module 40 is configured to receive an eUICC management service request sent by an external entity, where the eUICC management service request includes at least one eUICC identifier, and the SM-SR entity queries the at least one user identifier associated with the at least one eUICC identifier ;or
- a second receiving module 50 configured to receive an eUICC management service request sent by an external entity, where the eUICC management service request includes at least one user identifier;
- the third receiving module 60 is configured to receive an eUICC management service request sent by an external entity, where the eUICC management service request includes at least one user identifier and at least one eUICC identifier.
- the returning module 70 is configured to return, to the external entity, an identifier of the eUICC of the at least one target eUICC that successfully establishes the communication connection.
- the pushing module 10 is configured to calculate the obtained access control information according to load information of the SM-SR entity.
- the SM-SR entity 1 includes a processor 61, a memory 62, an input device 63, and an output device 64.
- the number of the processors 61 in the SM-SR entity 1 may be one or more, and FIG. 8 takes a processor as an example.
- the processor 61, the memory 62, the input device 63, and the output device 64 may be connected by a bus or other means, and the bus connection is taken as an example in FIG.
- the memory 62 stores a set of program codes
- the processor 61 is configured to call the program code stored in the memory 62 for performing the following operations:
- a push request including a trigger message and at least one user identity, instructing the PLMN/push server to push the trigger to the target embedded universal integrated circuit card eUICC pointed to by the at least one user identifier a message, the trigger message is used to trigger the target eUICC to initiate communication with the SM-SR entity;
- a management operation on the target eUICC is performed through the communication connection.
- the processor 61 is further configured to perform access control information included in the trigger message calculated according to the load information of the self.
- the processor 61 is further configured to:
- eUICC management service request sent by an external entity, where the eUICC management service request includes at least one eUICC identifier, and the SM-SR entity queries at least one user identifier associated with the at least one eUICC identifier;
- eUICC management service request sent by an external entity, where the eUICC management service request includes at least one user identifier and at least one eUICC identifier.
- the processor 61 is further configured to:
- an eUICC identifier of at least one target eUICC that successfully establishes a communication connection is provided.
- FIG. 9 is a schematic structural diagram of an eUICC according to a first embodiment of the present invention.
- the eUICC includes a first module 11 and a second module 21, where
- the first module 11 is configured to establish a communication connection with the SM-SR entity after receiving a trigger message sent by the subscription manager-secure route SM-SR entity;
- the second module 21 is configured to acquire, by using the communication connection, a management operation of the eUICC by the SM-SR entity.
- FIG. 10 is a schematic structural diagram of an eUICC according to a second embodiment of the present invention.
- the eUICC further includes a third module 31.
- the third module 31 is configured to use the configuration profile provisioning profile or the operational profile operational profile for the user equipment where the eUICC is located to be attached to the carrier network.
- the trigger message further includes access control information, where the first module 11 is configured to generate an access time point according to the access control information, and initiate a communication connection request to the SM-SR at the access time point, where And establish a communication connection.
- FIG. 11 is a schematic structural diagram of an eUICC according to a third embodiment of the present invention.
- eUICC2 is included.
- the eUICC2 includes a processor 71 and a memory 72.
- the number of processors 71 in the eUICC2 may be one or more.
- FIG. 11 A processor is an example.
- the processor 71 and the memory 72 may be connected by a bus or other means, and a bus connection is taken as an example in FIG.
- the memory 72 stores a set of program codes
- the processor 71 is configured to call the program code stored in the memory 72 for performing the following operations:
- the processor 71 is configured to generate an access time point according to the access control information, initiate a communication connection request to the SM-SR at the access time point, and establish a communication connection. .
- the processor 71 is further configured to:
- the user equipment where the eUICC is located is attached to the carrier network by using the configuration profile or the operation profile.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
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)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims (33)
- 一种嵌入式通用集成电路卡的管理方法,其特征在于,包括:签约管理器-安全路由SM-SR实体向公共陆地移动网络PLMN/推送服务器发送包括触发消息和至少一个用户标识的推送请求,指示所述PLMN/推送服务器向所述至少一个用户标识指向的目标嵌入式通用集成电路卡eUICC推送所述触发消息,所述触发消息用于触发所述目标eUICC发起与所述SM-SR实体的通信;所述SM-SR实体与所述目标eUICC建立通信连接;所述SM-SR实体通过所述通信连接执行对所述目标eUICC的管理操作。
- 如权利要求1所述的方法,其特征在于,所述触发信息包括所述SM-SR实体的标识信息和/或地址信息。
- 如权利要求1所述的方法,其特征在于,所述触发消息包括:eUICC管理操作类型和/或接入控制信息,所述接入控制信息用于所述目标eUICC发起与所述SM-SR的通信的调度。
- 如权利要求3所述的方法,其特征在于,所述eUICC管理操作类型包括:轮廓profile下载、profile安装、profile删除、profile使能、profile去使能、profile状态变更或eUICC关联的SM-SR实体变更。
- 如权利要求3所述的方法,其特征在于,所述接入控制信息包括:回退定时器信息或时间窗口信息。
- 如权利要求3所述的方法,其特征在于,所述接入控制信息是由所述SM-SR实体根据自身的负载信息计算得到的。
- 如权利要求1-6任意一项所述的方法,其特征在于,所述SM-SR实体向所述PLMN/推送服务器发送包括触发消息和至少一个用户标识的推送请求的步骤之前,还包括:所述SM-SR实体接收外部实体发送的eUICC管理服务请求,所述eUICC管理服务请求中包括至少一个eUICC标识,所述SM-SR实体查询所述至少一个eUICC标识关联的至少一个用户标识;或所述SM-SR实体接收外部实体发送的eUICC管理服务请求,所述eUICC管理服务请求包括至少一个用户标识;或所述SM-SR实体接收外部实体发送的eUICC管理服务请求,所述eUICC管理服务请求中包括至少一个用户标识和至少一个eUICC标识。
- 如权利要求7所述的方法,其特征在于,所述SM-SR实体与所述目标eUICC建立通信连接的步骤之后,还包括:所述SM-SR实体向所述外部实体返回成功建立通信连接的至少一个目标eUICC的eUICC标识。
- 如权利要求1-8任意一种所述的方法,其特征在于,所述用户标识包括:国际移动用户识别码IMSI、移动用户识别号码MSISDN、公共用户标识或私有用户标识。
- 一种嵌入式通用集成电路卡的管理方法,其特征在于,包括:嵌入式通用集成电路卡eUICC接收到签约管理器-安全路由SM-SR实体推送的触发消息后,与所述SM-SR实体建立通信连接;所述eUICC通过所述通信连接获取所述SM-SR实体对所述eUICC的管理操作。
- 如权利要求10所述的方法,其特征在于,所述触发消息包括所述SM-SR实体的标识信息和/或地址信息。
- 如权利要求10所述的方法,其特征在于,所述触发消息包括:eUICC管理操作类型和/或接入控制信息,所述接入控制信息用于所述与所述SM-SR实体建立通信连接的调度。
- 如权利要求12所述的方法,其特征在于,所述eUICC管理操作类型包括:轮廓profile下载、profile安装、profile删除、profile使能、profile去使能、profile状态变更或eUICC关联的SM-SR实体变更。
- 如权利要求12所述的方法,其特征在于,所述接入控制信息包括:回退定时器信息或时间窗口信息。
- 如权利要求12所述的方法,其特征在于,所述与所述SM-SR实体建立通信连接的步骤包括:所述eUICC根据所述接入控制信息生成接入时间点;所述eUICC在所述接入时间点向所述SM-SR发起通信连接请求,并建立通信连接。
- 如权利要求10-15所述的方法,其特征在于,所述eUICC接收到SM-SR实体发送的触发消息之前,还包括:所述eUICC中的配置轮廓provisioning profile或运营轮廓operational profile用于所述eUICC所在的用户设备附着到运营商网络。
- 一种SM-SR实体,其特征在于,包括:推送模块,用于向公共陆地移动网络PLMN/推送服务器发送包括触发消息和至少一个用户标识的推送请求,指示所述PLMN/推送服务器向所述至少一个用户标识指向的目标嵌入式通用集成电路卡eUICC推送所述触发消息,所述触发消息用于触发所述目标eUICC发起与所述SM-SR实体的通信;连接模块,用于与所述目标eUICC建立通信连接;管理模块,用于通过所述通信连接执行对所述目标eUICC的管理操作。
- 如权利要求17所述的SM-SR实体,其特征在于,所述触发信息包括所述SM-SR实体的标识信息和/或地址信息。
- 如权利要求17所述的SM-SR实体,其特征在于,所述触发消息包括:eUICC管理操作类型和/或接入控制信息,所述接入控制信息用于所述目标eUICC发起与所述SM-SR的通信的调度。
- 如权利要求19所述的SM-SR实体,其特征在于,所所述eUICC管理操作类型包括:轮廓profile下载、profile安装、profile删除、profile使能、profile去使能、profile状态变更或eUICC关联的SM-SR实体变更。
- 如权利要求19所述的SM-SR实体,其特征在于,所述接入控制信息包括:回退定时器信息或时间窗口信息。
- 如权利要求19所述的方法,其特征在于,所述推送模块用于根据所述SM-SR实体的负载信息计算得到的所述接入控制信息。
- 如权利要求17-22任意一项所述的SM-SR实体,其特征在于,还包括:第一接收模块,用于接收外部实体发送的eUICC管理服务请求,所述eUICC管理服务请求中包括至少一个eUICC标识,所述SM-SR实体查询所述至少一个eUICC标识关联的至少一个用户标识;或第二接收模块,用于接收外部实体发送的eUICC管理服务请求,所述 eUICC管理服务请求包括至少一个用户标识;或第三接收模块,用于接收外部实体发送的eUICC管理服务请求,所述eUICC管理服务请求中包括至少一个用户标识和至少一个eUICC标识。
- 如权利要求23所述的SM-SR实体,其特征在于,还包括:返回模块,用于向所述外部实体返回成功建立通信连接的至少一个目标eUICC的eUICC标识。
- 如权利要求17-24任意一项所述的SM-SR实体,其特征在于,所述用户标识包括国际移动用户识别码IMSI、移动用户识别号码MSISDN、公共用户标识或私有用户标识。
- 一种eUICC,其特征在于,包括:第一模块,用于接收到签约管理器-安全路由SM-SR实体推送的触发消息后,与所述SM-SR实体建立通信连接;第二模块,用于通过所述通信连接获取所述SM-SR实体对所述eUICC的管理操作。
- 如权利要求26所述的eUICC,其特征在于,所述触发消息包括:eUICC管理操作类型和/或接入控制信息,所述接入控制信息用于所述与所述SM-SR实体建立通信连接的调度。
- 如权利要求27所述的eUICC,其特征在于,所述触发消息包括:eUICC管理操作类型和/或接入控制信息,所述接入控制信息用于所述与所述SM-SR实体建立通信连接的调度。
- 如权利要求28所述的eUICC,其特征在于,所述eUICC管理操作类型包括:轮廓profile下载、profile安装、profile删除、profile使能、profile去使 能、profile状态变更或eUICC关联的SM-SR实体变更。
- 如权利要求28所述的eUICC,其特征在于,所述接入控制信息包括:回退定时器信息或时间窗口信息。
- 如权利要求28所述的eUICC,其特征在于,所述第一模块用于根据所述接入控制信息生成接入时间点;在所述接入时间点向所述SM-SR发起通信连接请求,并建立通信连接。
- 如权利要求26-31任意一项所述的eUICC,其特征在于,还包括:第三模块,使用配置轮廓provisioning profile或运营轮廓operational profile用于所述eUICC所在的用户设备附着到运营商网络。
- 一种通信系统,其特征在于,包括如权利要求17-25任意一项所述的SM-SR实体和如权利要求26-32所述的嵌入式通用集成电路卡。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020167017782A KR101665492B1 (ko) | 2013-12-05 | 2014-12-05 | 내장형 범용 집적회로 카드 관리 방법, 관련 장치 및 시스템 |
EP14867628.1A EP3073777B1 (en) | 2013-12-05 | 2014-12-05 | Management method for embedded universal integrated circuit card and related device |
JP2016536840A JP6139800B2 (ja) | 2013-12-05 | 2014-12-05 | 埋込みユニバーサル集積回路カードのための管理方法、関係するデバイス、およびシステム |
US15/173,532 US20160286380A1 (en) | 2013-12-05 | 2016-06-03 | Management method for embedded universal integrated circuit card, related device, and system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310656256.3 | 2013-12-05 | ||
CN201310656256.3A CN104703199B (zh) | 2013-12-05 | 2013-12-05 | 嵌入式通用集成电路卡的管理方法、相关设备及系统 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/173,532 Continuation US20160286380A1 (en) | 2013-12-05 | 2016-06-03 | Management method for embedded universal integrated circuit card, related device, and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015081884A1 true WO2015081884A1 (zh) | 2015-06-11 |
Family
ID=53272909
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/093119 WO2015081884A1 (zh) | 2013-12-05 | 2014-12-05 | 嵌入式通用集成电路卡的管理方法、相关设备及系统 |
Country Status (6)
Country | Link |
---|---|
US (1) | US20160286380A1 (zh) |
EP (1) | EP3073777B1 (zh) |
JP (1) | JP6139800B2 (zh) |
KR (1) | KR101665492B1 (zh) |
CN (1) | CN104703199B (zh) |
WO (1) | WO2015081884A1 (zh) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107623908A (zh) * | 2016-07-15 | 2018-01-23 | 中国移动通信有限公司研究院 | 一种发卡方法及用户识别模块卡 |
EP3277004A1 (de) * | 2016-07-29 | 2018-01-31 | Deutsche Telekom AG | Teilnehmeridentitätsmodul für einen zugriff auf ein mobilfunknetzwerk |
CN107836122A (zh) * | 2015-06-30 | 2018-03-23 | 微软技术许可有限责任公司 | 选择订户身份模块简档主机 |
Families Citing this family (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104883674B (zh) * | 2014-02-28 | 2018-06-26 | 华为终端有限公司 | 一种Profile关联管理的方法及装置 |
WO2016091414A1 (en) * | 2014-12-10 | 2016-06-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Managing network connectivity of a device comprising an embedded uicc |
KR102303504B1 (ko) * | 2015-03-25 | 2021-09-17 | 삼성전자 주식회사 | 무선 통신 시스템에서 단말의 프로파일 설치 방법 및 장치 |
DE102015008179A1 (de) * | 2015-06-25 | 2016-12-29 | Giesecke & Devrient Gmbh | Kommunizieren eines Teilnehmeridentitätsmoduls zu einem Server, insbesondere bei Profilwechsel |
CN105050071B (zh) * | 2015-07-10 | 2019-09-24 | 惠州Tcl移动通信有限公司 | 一种基于eUICC的多设备管理方法及系统 |
KR102381377B1 (ko) * | 2015-10-07 | 2022-03-31 | 삼성전자주식회사 | 통신 시스템에서 프로파일을 원격으로 제공하는 방법 및 장치 |
CN105357771B (zh) * | 2015-10-16 | 2019-01-08 | 中国联合网络通信集团有限公司 | 连接建立方法和用户终端 |
KR102490497B1 (ko) * | 2015-12-28 | 2023-01-19 | 삼성전자주식회사 | 통신 시스템에서 프로파일을 송수신하는 방법 및 장치 |
CN109155910B (zh) * | 2016-05-27 | 2020-12-08 | 华为技术有限公司 | 一种下载签约信息的方法、相关设备及系统 |
WO2018018419A1 (zh) * | 2016-07-26 | 2018-02-01 | 华为技术有限公司 | 一种配置文件批量获取、下载方法、服务器及终端 |
CN107846663B (zh) * | 2016-09-21 | 2021-01-12 | 中国电信股份有限公司 | 实现用户签约数据集远程管理的方法、装置和系统 |
CN108093394B (zh) * | 2016-11-23 | 2020-11-06 | 中兴通讯股份有限公司 | 订购服务的方法及装置 |
CN108112011A (zh) * | 2016-11-24 | 2018-06-01 | 中国电信股份有限公司 | 远程管理嵌入式通用集成电路卡的方法、装置和系统 |
WO2018098713A1 (zh) * | 2016-11-30 | 2018-06-07 | 华为技术有限公司 | 一种获取授权文件的方法及设备 |
KR102237840B1 (ko) * | 2016-12-01 | 2021-04-08 | 삼성전자 주식회사 | eSIM 프로파일을 설치, 관리하는 방법 및 장치 |
US10659955B2 (en) | 2016-12-01 | 2020-05-19 | Samsung Electronics Co., Ltd. | Apparatus and method for installing and managing eSIM profiles |
CN106713651A (zh) * | 2016-12-30 | 2017-05-24 | 百度在线网络技术(北京)有限公司 | 信息显示方法和移动终端 |
CN110178393B (zh) * | 2017-01-13 | 2020-12-15 | 华为技术有限公司 | 一种签约数据集的下载方法、设备及服务器 |
CN109792604B (zh) * | 2017-01-16 | 2021-12-03 | 华为技术有限公司 | 一种eUICC配置文件管理方法及相关装置 |
FR3062767A1 (fr) * | 2017-02-09 | 2018-08-10 | Orange | Technique d'administration d'une souscription aupres d'un operateur |
CN110301146B (zh) * | 2017-03-01 | 2021-02-26 | 华为技术有限公司 | 网络配置方法及终端 |
WO2018165983A1 (zh) * | 2017-03-17 | 2018-09-20 | 华为技术有限公司 | 一种eUICC配置文件的删除方法和设备 |
CN107277798B (zh) * | 2017-06-12 | 2020-12-04 | 北京佰才邦技术有限公司 | 通信方法、装置及系统 |
CN108702386B (zh) * | 2017-06-14 | 2020-09-11 | 华为技术有限公司 | 一种嵌入式通用集成电路卡配置文件的管理方法及装置 |
WO2018227729A1 (zh) | 2017-06-14 | 2018-12-20 | 华为技术有限公司 | 一种嵌入式通用集成电路卡配置文件的管理方法及装置 |
US11768965B2 (en) | 2017-08-09 | 2023-09-26 | Icrypto, Inc | System and method for securely storing data in a SIM |
US10708763B2 (en) | 2017-11-30 | 2020-07-07 | T-Mobile Usa, Inc. | On-boarding entity for remote embedded universal integrated circuit card management |
CN110839232B (zh) * | 2018-08-15 | 2022-04-26 | 成都鼎桥通信技术有限公司 | 一种eSIM profile更新方法 |
CN109195139B (zh) * | 2018-09-04 | 2021-07-27 | 中国联合网络通信集团有限公司 | M2M管理平台与eSIM卡的数据传输方法、装置、平台及介质 |
KR20200101257A (ko) | 2019-02-19 | 2020-08-27 | 삼성전자주식회사 | 이동 통신 시스템의 기기변경 방법 및 장치 |
US10708759B1 (en) * | 2019-05-20 | 2020-07-07 | T-Mobile Usa, Inc. | M2M SM-SR to SM-DP notification |
CN110505618B (zh) * | 2019-07-10 | 2023-11-03 | 中国联合网络通信集团有限公司 | 一种业务处理方法和服务器 |
CN110781128A (zh) * | 2019-11-05 | 2020-02-11 | 武汉虹信通信技术有限责任公司 | 嵌入式设备的管控方法及管控适配装置 |
CN114554476B (zh) * | 2020-11-10 | 2023-04-07 | 荣耀终端有限公司 | eSIM卡控制方法、可读介质及电子设备 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103167465A (zh) * | 2013-02-04 | 2013-06-19 | 中国联合网络通信集团有限公司 | 一种嵌入式uicc卡激活处理方法和装置 |
CN103227991A (zh) * | 2012-01-29 | 2013-07-31 | 中兴通讯股份有限公司 | Mtc设备的触发方法、装置及系统 |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9332424B2 (en) * | 2005-08-05 | 2016-05-03 | Qualcomm Incorporated | Centrally managed solution for all device management activities |
US8271025B2 (en) * | 2008-10-20 | 2012-09-18 | At&T Mobility Ii Llc | Device network technology selection and display in multi-technology wireless environments |
KR20130012243A (ko) * | 2011-07-08 | 2013-02-01 | 주식회사 케이티 | 특수 권한 기반의 내장 sim의 mno 변경방법 및 그를 위한 내장 sim과 기록매체 |
KR101954450B1 (ko) * | 2011-09-05 | 2019-05-31 | 주식회사 케이티 | 내장 uicc의 인증정보를 이용한 인증방법과, 그를 이용한 프로비저닝 및 mno 변경 방법, 그를 위한 내장 uicc, mno 시스템 및 기록매체 |
US8989806B2 (en) * | 2011-09-16 | 2015-03-24 | Alcatel Lucent | Network operator-neutral provisioning of mobile devices |
KR20140086950A (ko) * | 2011-09-28 | 2014-07-08 | 주식회사 케이티 | 프로파일 관리 방법, 내장 uicc 및 내장 uicc 탑재 기기 |
US9241351B2 (en) * | 2011-11-04 | 2016-01-19 | Intel Corporation | Techniques and configurations for triggering a plurality of wireless devices |
KR101893934B1 (ko) * | 2012-04-09 | 2018-08-31 | 주식회사 케이티 | 정책 규칙 관리 및 실행을 위한 방법 및 eUICC |
US9485793B2 (en) * | 2012-04-10 | 2016-11-01 | Google Technology Holdings LLC | Method, apparatus and system for triggering wireless communication devices to attach to a wireless communications network |
KR102135240B1 (ko) * | 2012-05-25 | 2020-07-17 | 삼성전자주식회사 | eUICC의 가입자 프로파일 제공 방법 |
EP2747466B1 (en) * | 2012-12-21 | 2017-10-04 | Giesecke+Devrient Mobile Security GmbH | Methods and devices for ota subscription management |
EP3016420A4 (en) * | 2013-06-28 | 2016-12-21 | Ntt Docomo Inc | CONTROL DEVICE, CONTROL METHOD, COMMUNICATION SYSTEM AND PROGRAM |
FR3011652B1 (fr) * | 2013-10-07 | 2015-12-04 | Oberthur Technologies | Procede de personnalisation d'un element securise |
KR102200209B1 (ko) * | 2014-04-22 | 2021-01-08 | 삼성전자 주식회사 | 프로파일 설치 방법 및 장치 |
-
2013
- 2013-12-05 CN CN201310656256.3A patent/CN104703199B/zh active Active
-
2014
- 2014-12-05 JP JP2016536840A patent/JP6139800B2/ja active Active
- 2014-12-05 WO PCT/CN2014/093119 patent/WO2015081884A1/zh active Application Filing
- 2014-12-05 EP EP14867628.1A patent/EP3073777B1/en active Active
- 2014-12-05 KR KR1020167017782A patent/KR101665492B1/ko active IP Right Grant
-
2016
- 2016-06-03 US US15/173,532 patent/US20160286380A1/en not_active Abandoned
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103227991A (zh) * | 2012-01-29 | 2013-07-31 | 中兴通讯股份有限公司 | Mtc设备的触发方法、装置及系统 |
CN103167465A (zh) * | 2013-02-04 | 2013-06-19 | 中国联合网络通信集团有限公司 | 一种嵌入式uicc卡激活处理方法和装置 |
Non-Patent Citations (2)
Title |
---|
ROGERS WIRELESS.: "Tdoc SA3LI12_074", EMBEDDED UICC REMOTE PROVISIONING DISCUSSION, 19 July 2012 (2012-07-19), XP050637185 * |
See also references of EP3073777A4 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107836122A (zh) * | 2015-06-30 | 2018-03-23 | 微软技术许可有限责任公司 | 选择订户身份模块简档主机 |
CN107623908A (zh) * | 2016-07-15 | 2018-01-23 | 中国移动通信有限公司研究院 | 一种发卡方法及用户识别模块卡 |
CN107623908B (zh) * | 2016-07-15 | 2020-10-30 | 中国移动通信有限公司研究院 | 一种发卡方法及用户识别模块卡 |
EP3277004A1 (de) * | 2016-07-29 | 2018-01-31 | Deutsche Telekom AG | Teilnehmeridentitätsmodul für einen zugriff auf ein mobilfunknetzwerk |
WO2018019976A1 (de) * | 2016-07-29 | 2018-02-01 | Deutsche Telekom Ag | Teilnehmeridentitätsmodul für einen zugriff auf ein mobilfunknetzwerk |
Also Published As
Publication number | Publication date |
---|---|
JP6139800B2 (ja) | 2017-05-31 |
KR20160089522A (ko) | 2016-07-27 |
KR101665492B1 (ko) | 2016-10-12 |
EP3073777A1 (en) | 2016-09-28 |
CN104703199A (zh) | 2015-06-10 |
EP3073777A4 (en) | 2016-10-19 |
JP2016541200A (ja) | 2016-12-28 |
CN104703199B (zh) | 2018-05-11 |
US20160286380A1 (en) | 2016-09-29 |
EP3073777B1 (en) | 2018-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015081884A1 (zh) | 嵌入式通用集成电路卡的管理方法、相关设备及系统 | |
CN109429295B (zh) | 一种选择amf的方法、amf、系统及存储介质 | |
AU2021277736B2 (en) | Pdu type setting method, ue policy setting method, and related entity | |
US10958618B2 (en) | ESIM-based card pool system and control method thereof | |
CN105471686B (zh) | 终端控制方法、装置及系统 | |
CN106572517B (zh) | 网络切片的处理方法、接入网络的选择方法及装置 | |
US10721614B2 (en) | Enhancements to eSIM profile operation callbacks using a machine-to-machine (M2M) device | |
US10560929B2 (en) | Resource request method and system, device, and network side node | |
WO2015157949A1 (zh) | 无线局域网络wlan的接入方法、终端及服务器 | |
EP2983399B1 (en) | Method, device, and system for proximity service authorization | |
WO2016106778A1 (zh) | 数据更新方法、装置及嵌入式通用集成电路卡 | |
CN107950041A (zh) | 一种Profile切换的方法及终端 | |
JP6751088B2 (ja) | Apduスクリプトにおける黙示的ファイル生成 | |
CN106487528B (zh) | 一种用户VoLTE签约状态的获取方法及设备 | |
CN105025589A (zh) | 终端设备数据传输管理方法、装置、系统及相关设备 | |
CN106210023B (zh) | 虚拟sim卡同步管理方法和终端 | |
CN113572864B (zh) | 一种数据处理方法、网元设备以及可读存储介质 | |
CN106576285B (zh) | 一种apn配置方法、用户设备和配置服务器 | |
CN104751617A (zh) | 一种遥控器与主机的连接方法及遥控装置 | |
CN104519038A (zh) | 会话建立方法、装置及系统 | |
CN112954669A (zh) | 共享终端业务控制方法、装置、网元及存储介质 | |
CN106341851B (zh) | 一种用于为指定终端建立专有承载的方法 | |
CN111246405B (zh) | 短信下发方法及装置、融合短信中心 | |
WO2013000212A1 (zh) | 实现终端接入集群业务的方法、终端和基站 | |
CN109150671B (zh) | 接入设备模式切换方法、网络接入设备和智能组网系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14867628 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016536840 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2014867628 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014867628 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20167017782 Country of ref document: KR Kind code of ref document: A |