WO2014059941A1 - Procédé et dispositif de résiliation d'abonnement de terminal - Google Patents

Procédé et dispositif de résiliation d'abonnement de terminal Download PDF

Info

Publication number
WO2014059941A1
WO2014059941A1 PCT/CN2013/085423 CN2013085423W WO2014059941A1 WO 2014059941 A1 WO2014059941 A1 WO 2014059941A1 CN 2013085423 W CN2013085423 W CN 2013085423W WO 2014059941 A1 WO2014059941 A1 WO 2014059941A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
server
request
stop
application
Prior art date
Application number
PCT/CN2013/085423
Other languages
English (en)
Chinese (zh)
Inventor
王涛
薛国栋
金辉
衣强
Original Assignee
华为终端有限公司
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
Application filed by 华为终端有限公司 filed Critical 华为终端有限公司
Publication of WO2014059941A1 publication Critical patent/WO2014059941A1/fr

Links

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

Definitions

  • UICC Universal Integrated Circuit Card
  • 3G Third-generation, third-generation mobile communication technology
  • UICC is mainly used to store information such as user information, keys, subscription information, and payment methods.
  • the network access test of the 3G user terminal it is required to meet the conformance test requirements of the UICC.
  • Different service providers can provide different kinds of services for users of mobile terminals by installing various applications on mobile terminals, and users will use different service providers in the process of using mobile terminals. Signing up to use various applications, for example, a network access application signed with the MNO (Mobi le Network Operator) is necessary for the mobile terminal to access the network of the MN0.
  • MNO Moobi le Network Operator
  • the traditional UICC is customized by the operator and contains relevant information of the operator when it leaves the factory. Once shipped, the operator information cannot be changed. If the user signs up with other operators, the corresponding UICC needs to be replaced, which brings great inconvenience to the user.
  • the eUICC (embedded UICC) is embedded in the terminal device.
  • the eUICC can be remotely managed by the SM (Subscription Manager) system on the network side.
  • the eUICC can be downloaded through the SM server.
  • the mobile operator data is deleted or changed, so that the terminal can switch the mobile operator network without replacing the eUICC.
  • the existing standard does not provide a method for the eUICC to stop signing the application for the contract, that is, the terminal configuring the eUICC cannot stop signing the application that has already been contracted.
  • an embodiment of the present invention provides a method and apparatus for stopping a subscription of a terminal, so as to stop signing an application that has been contracted on a terminal configured with the eUICC.
  • the technical solution is as follows:
  • a method for stopping a subscription of a terminal includes:
  • the SM server receives the stop signing request, and the stop signing request carries the terminal identifier and the application identifier; the SM server queries whether the account corresponding to the terminal identifier and the application identifier is settled;
  • the SM server deletes the corresponding subscription data stored locally according to the terminal identifier and the application identifier, and notifies the terminal corresponding to the terminal identifier and the MN0 server to delete the corresponding subscription data;
  • the SM server rejects the stop signing request.
  • the SM server receives the stop signing request, specifically:
  • the SM server receives the stop subscription request sent by the M2M-SP server.
  • the terminal identifier is specifically an MEI of the terminal and/or an eID of the eUICC on the terminal.
  • the stop signing request further carries authentication data
  • the SM server After receiving the stop signing request, the SM server further includes: the SM server sending an authentication request carrying the terminal identifier, the application identifier, and the authentication data to the MN0 server, so that the MN0 server is configured according to the terminal Identifying, applying, and authenticating data, determining whether the terminal has the right to stop signing; the SM server receiving the authentication result sent by the MN0 server, and rejecting the stop signing request if the terminal does not have the stop signing right .
  • the SM server queries whether the account corresponding to the terminal identifier and the application identifier is settled, specifically:
  • the SM server determines whether the settlement completion identifier is carried in the stop signing request
  • the SM server sends a query request that carries the terminal identifier and the application identifier to the server corresponding to the application identifier, so that the server corresponding to the application identifier queries whether the account corresponding to the terminal identifier and the application identifier is settled.
  • the SM server receives the query result sent by the server corresponding to the application identifier.
  • the query result carries balance information or arrears information of the account
  • the SM server rejects the stop signing request, specifically: the SM server sends a reject request notification to the sender of the stop signing request, where the reject request notification carries the account balance information or the arrears information .
  • the SM server includes an SM-SR and an SM-DP;
  • the SM server deletes the corresponding subscription data stored locally according to the terminal identifier and the application identifier, where the SM server deletes the subscription data corresponding to the terminal identifier and the application identifier stored in the SM-DP. .
  • the SM server notifies the MN0 server to delete the corresponding subscription data according to the terminal identifier and the application identifier, specifically:
  • the SM server sends a deletion request carrying the terminal identifier and the application identifier to the MN0 server, so that the MN0 server deletes the subscription data corresponding to the terminal identifier and the application identifier;
  • the SM server receives the deletion success notification sent by the MN0 server.
  • the SM server deletes the corresponding subscription data stored locally according to the terminal identifier and the application identifier, and notifies the terminal corresponding to the terminal identifier and the MN0 server to delete the corresponding subscription data, and further includes:
  • the SM server sends a stop signing success notification to the sender that stops the signing request.
  • a method for stopping a subscription of a terminal includes:
  • deletion request sent by the SM server, where the deletion request carries the application identifier; and deleting the subscription data corresponding to the application identifier.
  • the terminal identifier is specifically an international mobile device number top EI of the terminal and/or an embedded identity identifier eID of the embedded universal integrated circuit card eUICC on the terminal.
  • the stop signing request further carries authentication data.
  • an apparatus for stopping a subscription of a terminal comprising:
  • a receiving module configured to receive a stop signing request, where the stop signing request carries a terminal identifier and an application identifier;
  • a querying module configured to query whether the account corresponding to the terminal identifier and the application identifier is settled; if the settlement has been completed, deleting the corresponding subscription data stored locally according to the terminal identifier and the application identifier, and notifying the terminal identifier
  • the corresponding terminal and the MN0 server delete the corresponding subscription data; if the settlement is not completed, the stop subscription request is rejected.
  • the receiving module is specifically configured to:
  • the terminal identifier is specifically an MEI of the terminal and/or an eID of the eUICC on the terminal.
  • the stop signing request further carries authentication data
  • the device further includes an authentication module, configured to send, to the MN0 server, an authentication request that carries the terminal identifier, the application identifier, and the authentication data, so that the MN0 server is configured according to the terminal identifier, the application identifier, and the authentication. Data, determining whether the terminal has the right to stop signing; receiving the authentication result sent by the MN0 server, and rejecting the stop signing request if the terminal does not have the stop signing right.
  • an authentication module configured to send, to the MN0 server, an authentication request that carries the terminal identifier, the application identifier, and the authentication data, so that the MN0 server is configured according to the terminal identifier, the application identifier, and the authentication.
  • Data determining whether the terminal has the right to stop signing; receiving the authentication result sent by the MN0 server, and rejecting the stop signing request if the terminal does not have the stop signing right.
  • the query module is specifically configured to:
  • the query result carries balance information or arrears information of the account
  • the querying module is specifically configured to send a rejection request notification to the sender of the stop signing request, where the rejection request notification carries balance information or arrears information of the account.
  • the query module is specifically configured to:
  • the subscription data corresponding to the terminal identifier and the application identifier stored in the local SM-DP is deleted.
  • the query module is specifically configured to:
  • the method further includes:
  • the notification module is configured to send a stop signing success notification to the sender that stops the signing request.
  • a terminal where the terminal includes:
  • a sending module configured to send a stop signing request to the subscription management SM server, where the stop signing request carries a terminal identifier and an application identifier;
  • a receiving module configured to receive a deletion request sent by the SM server, where the deletion request carries the application identifier
  • the deleting module is configured to delete the subscription data corresponding to the application identifier.
  • the terminal identifier is specifically an international mobile device number EI of the terminal and/or embedded on the terminal.
  • the embedded identity eID is defined by the integrated circuit card eUICC.
  • the stop signing request further carries authentication data.
  • a terminal in another aspect, includes an embedded universal integrated circuit card eUICC, a processor, and a radio frequency module, where:
  • the eUICC is configured to store subscription data and a subscription management access certificate, where the storage subscription data includes an application identifier;
  • the processor is configured to generate a stop signing request, where the stop signing request carries a terminal identifier and an application identifier;
  • the radio frequency module is configured to send the stop signing request generated by the processor to the subscription management SM server, and receive the deletion request sent by the SM server, where the deletion request carries the application identifier;
  • the processor is further configured to delete the subscription data corresponding to the application identifier stored in the eUICC according to the deletion request received by the radio frequency module.
  • the terminal identifier is specifically an international mobile device number top EI of the terminal and/or an embedded identity identifier eID of the eUICC on the terminal.
  • the processor is further configured to acquire the authentication data stored in the eUICC, and when the stop signing request is generated, carry the authentication data in the stop signing request.
  • a system for stopping a contract of a terminal comprising means for stopping the subscription of the terminal as described above and the terminal as described above.
  • FIG. 1 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 1 of the present invention
  • 2 is a network architecture diagram provided by an embodiment of the present invention
  • 3 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 3 of the present invention
  • FIG. 4 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 4 of the present invention.
  • FIG. 5 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 5 of the present invention.
  • FIG. 6 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 6 of the present invention.
  • FIG. 7 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 7 of the present invention.
  • Embodiment 8 is a flowchart of a method for stopping a subscription of a terminal according to Embodiment 8 of the present invention.
  • FIG. 9 is a schematic structural diagram of an apparatus for stopping a subscription of a terminal according to Embodiment 9 of the present invention.
  • FIG. 10 is a schematic structural diagram of a terminal according to Embodiment 10 of the present invention.
  • FIG. 11 is a schematic structural diagram of a terminal according to Embodiment 11 of the present invention.
  • An embodiment of the present invention provides a method for stopping a subscription of a terminal.
  • the processing procedure of the method may include the following steps:
  • Step 101 The SM server receives the stop signing request, and the stop signing request carries the terminal identifier and the application identifier.
  • Step 102 The SM server queries whether the account corresponding to the terminal identifier and the application identifier is settled. If the settlement has been completed, step 103 is performed, and if the settlement is not completed, step 104 is performed.
  • Step 103 The SM server deletes the corresponding subscription data stored locally according to the terminal identifier and the application identifier, and notifies the terminal corresponding to the terminal identifier and the MN0 server to delete the corresponding subscription data.
  • Step 104 The SM server rejects the stop signing request.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • Embodiment 2
  • the embodiment of the invention provides a method for stopping the signing of the terminal.
  • the process flow shown in FIG. 1 will be analyzed in detail below.
  • Step 101 The SM server receives the stop signing request, and the stop signing request carries the terminal identifier and the application identifier.
  • the terminal identification and the application identification may identify which application of which terminal is to stop the contracting process.
  • the application identifier is used to identify various applications provided by MN0 or other service providers.
  • the application identifier may be one, or may be a list of multiple application identifiers, that is, requesting to stop signing for multiple applications, and the application identifier may also be an overall identifier, which is used to identify all applications on the terminal (ie, stop the subscription request to carry the entire identifier) At the time, it is requested to stop signing all applications on the terminal).
  • the SM server can include SM-SR (Subscription Manager-Securely Routing) and SM-DP (Subscription Management Unit-Data Preparation).
  • the SM-SR can be used as a control unit to receive various requests (such as stopping the subscription request), perform corresponding processing, and complete communication with other SM-SRs and terminals.
  • the SM-DP can be used as a storage unit for storing data such as subscription data, and can communicate with the MN0 server to complete communication with the MN0 server.
  • the information sent by the MN0 server to the SM-SR can be forwarded by the SM-DP, SM-SR.
  • the information sent to the MN0 server can also be forwarded through the SM-DP.
  • the network architecture diagram can be as shown in Figure 2.
  • the SM-SR is at the higher layer of the LSI server.
  • Each MN0 corresponds to the SM-SR.
  • Each SM-SR is connected to each other and can communicate with each other to form a unified SM system.
  • the SM server may also include only the SM-SR, and the SM-DP responsible for data storage may be set on the MN0 server side.
  • the stop signing request received by the SM server may be from the terminal, that is, the user may directly send the stop signing request to the SM server through the terminal; the stop signing request may also be from the MN0 server, that is, the user may go to the business hall or send a text message to the terminal.
  • MN0 applies to stop signing, and sends a stop signing request to the SM server through the MN0 server (the MN0 server can send the stop signing request to the SM-DP, and the SM-DP forwards it to the SM-SR); the stop signing request can also come from other An application server, such as M2M (Machine to Machine) - SP (Service Provider) server, that is, if the user wants to stop signing an application provided by an M2M-SP, he can contact the M2M-SP.
  • M2M-SP server sends a stop signing request to the SM server.
  • the terminal identifier carried in the stop signing request may be an MEI (International Mobile Equipment Identifier) of the terminal, or an eD (embedded identification) of the eUICC on the terminal, or may be The combination of the two, because the eUICC is embedded in the terminal and bound to the terminal, so as long as the terminal identifier can uniquely identify the terminal or its eUICC, the SM server, the MN0 server or the M2M-SP server obtains the terminal identifier. You can confirm its IMEI and eID.
  • MEI International Mobile Equipment Identifier
  • eD embedded identification
  • the terminal that initiates the stop signing request may perform authentication and authentication to determine whether the terminal has the right to stop signing, that is, the authentication data may be carried in the stop signing request, and after the SM server receives the stop signing request,
  • the following operations can be performed:
  • the SM server sends the terminal identifier and the application to the MN0 server. Identifying and authenticating the authentication request data, so that the MN0 server determines whether the terminal has the stop signing authority according to the terminal identifier, the application identifier, and the authentication data; then, the SM server receives the authentication result sent by the MN0 server, if the terminal does not have the stop If the signing authority is denied, the stop signing request is rejected. If the terminal has the right to stop signing, the subsequent steps are normally performed.
  • the MN0 server it is possible to record whether each application signed by each terminal has the right to stop signing.
  • the MN0 server can verify the authenticity of the terminal through the authentication data, and further determine the stop signing authority of the terminal according to the above record.
  • the authentication authentication process may be performed before sending the stop signing request to the SM server.
  • the user goes to the MN0 business hall to submit an application for stopping the signing, and the MN0 can directly obtain the authentication data, the terminal identifier, and the application identifier provided by the user. It is determined whether the user's terminal has the right to stop signing, and if there is no permission to stop signing, the user's application is rejected.
  • Step 102 The SM server queries whether the account corresponding to the terminal identifier and the application identifier is settled. If the settlement has been completed, step 103 is performed, and if the settlement is not completed, step 104 is performed.
  • the SM server determines whether the settlement completion identifier is carried in the stop signing request, and if yes, determines that the account is settled, otherwise the SM server may send a query request carrying the terminal identifier and the application identifier to the server corresponding to the application identifier, to The server corresponding to the application identifier is queried whether the account corresponding to the terminal identifier and the application identifier is settled. Then, the SM server receives the query result sent by the server corresponding to the application identifier.
  • the end user can submit an application for stopping the contract to the business hall of MN0, or submit the application for stopping the contract through the website of MN0 or M2M-SP, and submit the application for stopping the signing by SMS, etc.
  • the MN0 server or the M2M-SP server sends a stop signing request to the SM server. If the end user requests to stop signing the application provided by the MN0 (or M2M-SP) to the business hall or website of the MN0 (or M2M-SP), the MN0 (or M2M-SP) may first query the account of the application applying to stop the contract.
  • the stop signing request is sent to the SM server, and the settlement completion identifier is carried in the stop signing request. If the settlement completion request is not carried in the stop signing request, the sender of the stop signing request does not query whether the corresponding account is settled, and the SM server is required to perform corresponding query processing.
  • the application identifier represents an application that requests to stop the subscription.
  • the server corresponding to the application identifier is the server of the provider of the application.
  • the provider of the network access application is MN0
  • the server corresponding to the network access application identifier is the MN0 server. If the provider of an M2M application is an M2M-SP, the server corresponding to the M2M application identifier is the M2M-SP server.
  • each application subscribed by each terminal each terminal and the application provider can sign an application or sign a plurality of applications
  • the fee of the account corresponding to each application subscribed by the terminal It can be recorded by means of a fee schedule.
  • the account status of the account may include balance information or arrears information, the balance information is used to record the available balance in the account, and the arrears information is used to record the arrears of the account.
  • the server of the application provider When the server of the application provider receives the query request, it can query whether the account corresponding to the terminal identifier and the application identifier has a balance or arrears in the case of the recorded fee, and if it exists, the account is not settled, if the balance and the debt are If the payment is 0, the account is settled, and the result of the query is sent to the SM server.
  • the inquiry result carries the account balance information or the arrears information (the balance information or the arrears information may both be 0).
  • the SM server may send a rejection request notification to the sender (terminal, MN0 server, M2M-SP server, etc.) that stops the subscription request, and the rejection request notification is carried in the rejection request notification.
  • the sender terminal, MN0 server, M2M-SP server, etc.
  • Step 103 The SM server deletes the corresponding subscription data stored locally according to the terminal identifier and the application identifier, and notifies the terminal corresponding to the terminal identifier and the MN0 server to delete the corresponding subscription data.
  • the SM server deletes the corresponding subscription data stored in the SM-DP and the terminal identifier when the SM server deletes the corresponding subscription data stored locally according to the terminal identifier and the application identifier.
  • the subscription data of the application signed by each terminal may be stored corresponding to the application identifier and the terminal identifier, and may be stored in the form of a subscription data table.
  • the corresponding subscription data can be found according to the terminal identifier and the application identifier for deletion.
  • the SM server when the SM server notifies the MN0 server to delete the corresponding subscription data according to the terminal identifier and the application identifier, the SM server sends a deletion request carrying the terminal identifier and the application identifier to the MN0 server, so that the MN0 server deletes the terminal identifier.
  • the SM-SR may send the deletion request to the MN0 server through the SM-DP, and the MN0 server may send a deletion success notification to the SM-SR through the SM-DP.
  • the above-mentioned SM-DP can store the subscription data in the MN server, and when receiving the deletion request, the corresponding subscription data is searched according to the terminal identifier and the application identifier for deletion.
  • the deletion success notification may also be sent to the SM server.
  • the SM server may also send a stop signing success notification to the sender who stopped the signing request.
  • the stop signing request initiated by the MN0 server after performing step 103, the SM-SR may send a stop signing success notification to the MN0 server through the SM-DP.
  • the SM server rejects the stop signing request.
  • the SM server can stop the signing request.
  • the sender (terminal, MN0 server or M2M-SP server, etc.) sends a rejection request notification, and may carry the rejection reason in the rejection request notification, and may also carry information such as balance information or debt payment information.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • Embodiment 3
  • An embodiment of the present invention provides a method for stopping a subscription of a terminal.
  • an execution body of the method may be a terminal, and the specific processing procedure may include the following steps:
  • Step 301 Send a stop signing request to the SM server, where the stop signing request carries the terminal identifier and the application identifier.
  • the terminal identifier may be specifically the MEI of the terminal and/or the eID of the eUICC on the terminal.
  • the authentication data may be carried in the stop-requesting request for the authentication and authentication of the terminal by the SM server.
  • the specific authentication and authentication process refer to the second embodiment.
  • Step 302 Receive a deletion request sent by the SM server, where the application identifier is carried in the deletion request.
  • Step 303 Delete the subscription data corresponding to the application identifier.
  • the terminal can search for the corresponding subscription data stored by the terminal according to the application identifier, and delete the data.
  • the terminal sends a stop signing request to the SM server, so that the SM server performs the corresponding stop signing process, and after receiving the delete request sent by the SM server, the terminal deletes the subscription data corresponding to the application identifier. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • FIG. 4 is a flowchart of a process for stopping a subscription of a terminal in a specific application scenario according to an embodiment of the present invention.
  • a terminal initiates a stop subscription request to terminate a contract of an M2M application, and the process includes the following: Steps:
  • Step 401 The terminal sends a stop subscription request to the SM-SR, and stops the MEI carrying the terminal in the subscription request, the eID of the eUICC on the terminal, the list of application identifiers requesting to stop the subscription, and the authentication data.
  • the user may operate the terminal to issue a command to stop the subscription to the terminal, and after receiving the command, the processor on the terminal may obtain a corresponding subscription management access certificate to the eUICC (the certificate is used for the terminal to access the SM-SR). Authentication), then, according to the certificate, a stop signing request is generated, and the generated stop signing request is sent to the SM-SR through the radio frequency module on the terminal.
  • Step 402 The SM-SR sends an authentication request to the SM-DP, where the authentication request carries a MEI, an eID, a list of application identifiers, and authentication data.
  • Step 403 The SM-DP sends an authentication request to the MN0 server.
  • Step 404 The MN0 server determines whether the terminal has the stop signing authority, and sends the authentication result to the SM-DP.
  • Step 405 The SM-DP sends the authentication result to the SM-SR.
  • Step 406 The SM-SR sends a query request to the M2M-SP server (here, authentication is passed), which carries a list of elD and application identifiers.
  • Step 407 The M2M-SP server queries whether the corresponding account is settled according to the elD and the application identifier.
  • step 408 is executed, and the M2M-SP server sends the settlement result of the settlement to step 409, and the SM-SR sends a deletion request to the terminal, where the list of elD and the application identifier is carried.
  • Step 410 The terminal deletes the subscription data corresponding to the elD and each application identifier.
  • Step 411 The SM-SR sends a delete request to the SM-DP, where the elD and the application identifier are carried.
  • Step 412 The SM-DP deletes the subscription data corresponding to the elD and each application identifier.
  • Step 413 The SM-DP sends the deletion request to the MN0 server. Step 412 and step 413 have no necessary sequential relationship in timing.
  • Step 414 The MN0 server deletes the subscription data corresponding to the elD and each application identifier.
  • Step 415 The MN0 server sends a deletion success notification to the SM-DP.
  • Step 416 The SM-DP forwards the deletion success notification to the SM-SR.
  • the M2M-SP server sends the uncompleted query result to the SM-SR, and carries the balance information or the arrears information of the corresponding account; the SM-SR sends a rejection request notification to the terminal, which carries the corresponding account. Balance information or arrears information.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • Embodiment 5
  • FIG. 5 is a process flow in a specific application scenario of a method for stopping a subscription of a terminal according to an embodiment of the present invention.
  • a terminal initiates a stop subscription request and terminates an application contract provided by MN0. Includes the following steps:
  • Step 501 The terminal sends a stop subscription request to the SM-SR, and stops the IMEI of the terminal in the subscription request.
  • Step 502 The SM-SR sends an authentication request to the SM-DP, where the authentication request carries an IMEI, an eID, a list of application identifiers, and authentication data.
  • Step 503 The SM-DP sends an authentication request to the MN0 server.
  • Step 504 The MN0 server determines whether the terminal has the stop signing authority, and sends the authentication result to the SM-DP.
  • Step 505 The SM-DP sends the authentication result to the SM-SR.
  • Step 506 The SM-SR sends a query request (here, authentication pass) to the MN0 server through the SM-DP, where the list of elD and application identifiers is carried.
  • a query request here, authentication pass
  • Step 507 The MN0 server queries, according to the elD and the application identifier, whether the corresponding account is settled.
  • step 508 is executed, and the MN0 server sends the completed query result to the SM-SRo through the SM-DP.
  • Step 509 The SM-SR sends a delete request to the terminal, where the elD and the application identifier are carried.
  • Step 510 The terminal deletes the subscription data corresponding to the elD and each application identifier.
  • Step 511 The SM-SR sends a delete request to the SM-DP, where the elD and the application identifier are carried.
  • Step 512 The SM-DP deletes the subscription data corresponding to the elD and each application identifier.
  • Step 513 The SM-DP sends the deletion request to the MN0 server. Steps 512 and 513 have no necessary sequential relationship in timing.
  • Step 514 The MN0 server deletes the subscription data corresponding to the elD and each application identifier.
  • Step 515 The MN0 server sends a deletion success notification to the SM-DP.
  • Step 516 The SM-DP forwards the deletion success notification to the SM-SR.
  • the MN0 server sends the inquiry result that has not been settled to the SM-SR through the SM-DP, and carries the balance information or the arrears information of the corresponding account; the SM-SR sends a rejection request notification to the terminal, which carries Balance information or arrears information for the corresponding account.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • FIG. 6 is a flowchart of a process for stopping a subscription of a terminal in a specific application scenario according to an embodiment of the present invention.
  • the MN0 server initiates a stop subscription request, and terminates the contract of the M2M application, where the process includes the following: step: Step 601:
  • the MNO server sends a stop subscription request to the SM-SR through the SM-DP, and stops the MEI carrying the terminal in the subscription request, the eID of the eUICC on the terminal, the list of application identifiers requesting to stop the subscription, and the authentication data.
  • the user of the terminal may apply to stop the signing of the application to the MN0 business hall, or stop the signing application by means of a short message, etc., and the MN0 sends a stop signing request of the terminal user to the SM-SR through its server.
  • MN0 can also authenticate the terminal to determine whether it has the right to stop signing. If the signing authority is not stopped, the user's application is rejected.
  • Step 602 The SM-SR sends a query request to the M2M-SP server, where the list of the elD and the application identifier is carried.
  • Step 603 The M2M-SP server queries whether the corresponding account is settled according to the elD and the application identifier.
  • step 604 is executed, and the M2M-SP server sends the completed query result to the query.
  • Step 605 The SM-SR sends a delete request to the terminal, where the elD and the application identifier are carried.
  • Step 606 The terminal deletes the subscription data corresponding to the elD and each application identifier.
  • Step 607 The SM-SR sends a delete request to the SM-DP, where the elD and the application identifier are carried.
  • Step 608 The SM-DP deletes the subscription data corresponding to the elD and each application identifier.
  • Step 609 The SM-DP sends the deletion request to the MN0 server. Steps 608 and 609 have no necessary sequential relationship in timing.
  • Step 610 The MN0 server deletes the subscription data corresponding to the elD and each application identifier.
  • Step 611 The MN0 server sends a deletion success notification to the SM-DP.
  • Step 612 The SM-DP forwards the deletion success notification to the SM-SR.
  • Step 613 The SM-SR sends a stop signing success notification to the MN0 through the SM-DP.
  • the M2M-SP server sends the uncompleted query result to the SM-SR, and carries the balance information or the arrears information of the corresponding account; the SM-SR sends a rejection request notification to the MN0 server through the SM-DP. It carries the balance information or the arrears information of the corresponding account.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • FIG. 7 is a flowchart of a process for stopping a subscription of a terminal in a specific application scenario according to an embodiment of the present invention.
  • the MN0 server initiates a stop subscription request, and terminates the application provided by the MN0.
  • the process includes the following steps:
  • Step 701 The MN0 server sends a stop subscription request to the SM-SR through the SM-DP, stops the MEI carrying the terminal in the subscription request, the eID of the eUICC on the terminal, the list of application identifiers requesting to stop the subscription, and the authentication data.
  • the user of the terminal may apply to stop the signing of the application to the MN0 business hall, or stop the signing application by means of a short message, etc., and the MN0 sends a stop signing request of the terminal user to the SM-SR through its server.
  • MN0 Before sending the stop signing request, MN0 can also authenticate the terminal to determine whether it has the right to stop signing. If the signing authority is not stopped, the user's application is rejected. Moreover, if the application requested by the user to stop the subscription is the application provided by the MN0, the MN0 may also query whether the account corresponding to the terminal identifier and the application identifier is settled, and if the settlement is completed, send a stop signing request to the SM-SR, and stop signing the contract. The request carries the settlement completion identifier. If the settlement is not completed, the user's application can be directly rejected without sending a stop signing request.
  • Step 702 The SM-SR sends a delete request to the terminal, where the elD and the application identifier are carried.
  • the stop signing request carries the settlement completion identifier, so the SM-SR can determine that the corresponding account has been settled.
  • Step 703 The terminal deletes the subscription data corresponding to the elD and each application identifier.
  • Step 704 The SM-SR sends a delete request to the SM-DP, where the elD and the application identifier are carried.
  • Step 705 The SM-DP deletes the subscription data corresponding to the elD and each application identifier.
  • Step 706 The SM-DP sends the deletion request to the MN0 server. Step 705 and step 706 have no necessary sequential relationship in timing.
  • Step 707 The MN0 server deletes the subscription data corresponding to the elD and each application identifier.
  • Step 708 The MN0 server sends a deletion success notification to the SM-DP.
  • Step 709 The SM-DP forwards the deletion success notification to the SM-SR.
  • Step 710 The SM-SR sends a stop signing success notification to the MN0 server through the SM-DP.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • Example eight
  • FIG. 8 is a flowchart of a process for stopping a subscription of a terminal in a specific application scenario according to an embodiment of the present invention.
  • the M2M-SP server initiates a stop subscription request, and terminates the application provided by the M2M-SP. Contract, the process includes the following steps:
  • Step 801 The M2M-SP server sends a stop signing request to the SM-SR, and stops the bearer request in the signing request.
  • stop The signing request carries a settlement completion identifier.
  • the user of the terminal can submit a stop signing application to the M2M-SP website, and the M2M-SP sends the end user's stop signing request to the SM-SR through its server.
  • the M2M-SP may further query whether the account corresponding to the terminal identifier and the application identifier is settled, and if the settlement is completed, send a stop signing request to the SM-SR, and carry the settlement completion identifier in the stop signing request. If the settlement is not completed, the user's application can be directly rejected without sending a stop signing request.
  • Step 802 The SM-SR sends an authentication request to the SM-DP, where the authentication request carries an IMEI, an eID, a list of application identifiers, and authentication data.
  • Step 803 The SM-DP sends an authentication request to the MN0 server.
  • Step 804 The MN0 server determines whether the terminal has the stop signing authority, and sends the authentication result to the SM-DP.
  • Step 805 The SM-DP sends the authentication result to the SM-SR.
  • Step 806 The SM-SR sends a delete request to the terminal (here, authentication is passed), which carries a list of elD and application identifiers.
  • the stop signing request carries the settlement completion flag, so the SM-SR can determine that the corresponding account has been settled.
  • Step 807 The terminal deletes the subscription data corresponding to the elD and each application identifier.
  • Step 808 The SM-SR sends a delete request to the SM-DP, where the elD and the application identifier are carried.
  • Step 809 The SM-DP deletes the subscription data corresponding to the elD and each application identifier.
  • Step 810 The SM-DP sends the deletion request to the MN0 server. Steps 809 and 810 have no necessary sequential relationship in timing.
  • Step 811 The MN0 server deletes the subscription data corresponding to the elD and each application identifier.
  • Step 812 The MN0 server sends a deletion success notification to the SM-DP.
  • Step 813 The SM-DP forwards the deletion success notification to the SM-SR.
  • Step 814 The SM-SR sends a stop signing success notification to the M2M-SP server.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • an embodiment of the present invention further provides a device for stopping a subscription of a terminal.
  • the device includes:
  • the receiving module 910 is configured to receive a stop signing request, where the stop signing request carries a terminal identifier and should Use the logo;
  • the querying module 920 is configured to query whether the account corresponding to the terminal identifier and the application identifier is settled; if the settlement has been completed, delete the corresponding subscription data stored locally according to the terminal identifier and the application identifier, and notify the terminal The corresponding terminal and the MN0 server are deleted to delete the corresponding subscription data; if the settlement is not completed, the stop subscription request is rejected.
  • the receiving module 910 is specifically configured to:
  • the terminal identifier is specifically an MEI of the terminal and/or an eID of the eUICC on the terminal.
  • the stop signing request further carries authentication data
  • the device further includes an authentication module, configured to send, to the MN0 server, an authentication request that carries the terminal identifier, the application identifier, and the authentication data, so that the MN0 server is configured according to the terminal identifier, the application identifier, and the authentication. Data, determining whether the terminal has the right to stop signing; receiving the authentication result sent by the MN0 server, and rejecting the stop signing request if the terminal does not have the stop signing right.
  • an authentication module configured to send, to the MN0 server, an authentication request that carries the terminal identifier, the application identifier, and the authentication data, so that the MN0 server is configured according to the terminal identifier, the application identifier, and the authentication.
  • Data determining whether the terminal has the right to stop signing; receiving the authentication result sent by the MN0 server, and rejecting the stop signing request if the terminal does not have the stop signing right.
  • the query module 920 is specifically configured to:
  • the query result carries balance information or arrears information of the account
  • the querying module 920 is specifically configured to send a rejection request notification to the sender of the stop signing request, where the rejection request notification carries balance information or arrears information of the account.
  • the querying module 920 is specifically configured to: delete the subscription data corresponding to the terminal identifier and the application identifier stored in the local SM-DP.
  • the querying module 920 is specifically configured to: send, to the MN0 server, a deletion request that carries the terminal identifier and the application identifier, so that the MN0 server deletes the subscription data corresponding to the terminal identifier and the application identifier. ;
  • the method further includes: a notification module, configured to send a stop signing success notification to the sender that stops the signing request.
  • the SM server receives the stop signing request, and queries whether the corresponding account is settled. If the settlement is completed, the contract data in the local server, the terminal, and the MN0 server is deleted, otherwise the contract request is refused. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • the embodiment of the present invention further provides a terminal.
  • the terminal includes: a sending module 1010, configured to send a stop signing request to a subscription management SM server, where the stop signing request carries a terminal Identification and application identification;
  • the receiving module 1020 is configured to receive a deletion request sent by the SM server, where the deletion request carries the application identifier;
  • the deleting module 1030 is configured to delete the subscription data corresponding to the application identifier.
  • the terminal identifier is specifically an international mobile device number top EI of the terminal and/or an embedded identity identifier eID of the embedded universal integrated circuit card eUICC on the terminal.
  • the stop signing request further carries authentication data.
  • the terminal sends a stop signing request to the SM server, so that the SM server performs the corresponding stop signing process, and after receiving the delete request sent by the SM server, the terminal deletes the subscription data corresponding to the application identifier. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • an embodiment of the present invention further provides a terminal.
  • the terminal includes an eUICC1110, a processor 1120, and a radio frequency module 1130, where:
  • the eUICCl l lO is configured to store subscription data and a subscription management access certificate, where the storage subscription data includes an application identifier;
  • the processor 1120 is configured to generate a stop signing request, where the stop signing request carries a terminal identifier and an application identifier;
  • the radio frequency module 1130 is configured to send a stop signing request generated by the processor 1120 to the SM server, and receive a delete request sent by the SM server, where the delete request carries the application identifier;
  • the processor 1120 is further configured to delete the subscription data corresponding to the application identifier stored in the eUICCl 10 according to the deletion request received by the radio frequency module 1130.
  • the terminal identifier is specifically an international mobile device number MEI of the terminal and/or an embedded identity identifier eID of the eUICC on the terminal.
  • the processor 1120 is further configured to acquire the authentication data stored in the eUICCl 10, and when the stop subscription request is generated, carry the authentication data in the stop subscription request.
  • the terminal sends a stop signing request to the SM server, so that the SM server performs the corresponding stop signing process, and after receiving the delete request sent by the SM server, the terminal deletes the subscription data corresponding to the application identifier. Therefore, it is possible to stop signing the contracted application on the terminal configuring the eUICC.
  • the embodiment of the present invention further provides a system for stopping subscription of a terminal, and the system may include the device for stopping the subscription of the terminal in the above-mentioned Embodiment 9 and the terminal in Embodiment 10 or 11.
  • the device for stopping the subscription of the terminal provided by the foregoing embodiment processes the stop-subscription service, only the division of the above-mentioned functional modules is illustrated. In actual applications, the functions may be allocated differently according to requirements.
  • the function module is completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the method for stopping the signing of the terminal provided by the foregoing embodiment is the same as the method for stopping the signing of the terminal. For the specific implementation process, refer to the method embodiment, and details are not described herein again.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne le domaine technique des communications sans fil. Un procédé et un dispositif de résiliation d'abonnement de terminal sont décrits. Le procédé comprend les opérations suivantes : un serveur SM reçoit une requête de résiliation d'abonnement, la requête de résiliation d'abonnement véhiculant une identité de terminal et une identité d'application ; le serveur SM s'enquiert si le règlement d'un compte correspondant à l'identité de terminal et à l'identité d'application est achevé ou non ; si le règlement est achevé, le serveur SM supprime, conformément à l'identité de terminal et à l'identité d'application, des données d'abonnement correspondantes stockées localement, et ordonne à un terminal correspondant à l'identité de terminal et à un serveur MNO de supprimer des données d'abonnement correspondantes ; et si le règlement n'est pas achevé, le serveur SM rejette la requête de résiliation d'abonnement. La présente invention peut résilier un abonnement à une application qui a été souscrite sur un terminal configuré avec une eUICC.
PCT/CN2013/085423 2012-10-19 2013-10-18 Procédé et dispositif de résiliation d'abonnement de terminal WO2014059941A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210401125.6A CN103781054A (zh) 2012-10-19 2012-10-19 一种终端的停止签约的方法和装置
CN201210401125.6 2012-10-19

Publications (1)

Publication Number Publication Date
WO2014059941A1 true WO2014059941A1 (fr) 2014-04-24

Family

ID=50487586

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/085423 WO2014059941A1 (fr) 2012-10-19 2013-10-18 Procédé et dispositif de résiliation d'abonnement de terminal

Country Status (2)

Country Link
CN (1) CN103781054A (fr)
WO (1) WO2014059941A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9992607B2 (en) 2016-10-07 2018-06-05 Microsoft Technology Licensing, Llc eSIM identification data

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017166906A1 (fr) * 2016-03-30 2017-10-05 华为技术有限公司 Procédé de gestion d'un profil d'abonnement euicc et appareil associé
MX2018015011A (es) 2016-06-23 2019-03-06 Ericsson Telefon Ab L M Metodos y entidades para finalizar una suscripcion.
CN108574683A (zh) * 2017-03-13 2018-09-25 中兴通讯股份有限公司 签约数据处理方法、签约管理服务器及签约数据处理装置
CN110352605B (zh) * 2017-03-31 2020-12-08 华为技术有限公司 一种鉴权算法程序的添加方法、相关设备及系统
CN110809266A (zh) * 2018-08-05 2020-02-18 王正伟 基于时间标签的移动通信控制方法
CN110248355B (zh) * 2019-05-07 2022-03-08 深圳联想懂的通信有限公司 基于物联网设备eUICC卡的码号管理方法、设备、平台和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119197A (zh) * 2006-08-04 2008-02-06 华为技术有限公司 一种签约方法及系统
WO2008049959A2 (fr) * 2006-10-23 2008-05-02 Valimo Wireless Oy Procédé et système pour utiliser l'enregistrement par cryptographie à clé publique sur un environnement mobile
CN101546401A (zh) * 2008-03-28 2009-09-30 海尔集团公司 基于nfc移动终端的电子支付方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119197A (zh) * 2006-08-04 2008-02-06 华为技术有限公司 一种签约方法及系统
WO2008049959A2 (fr) * 2006-10-23 2008-05-02 Valimo Wireless Oy Procédé et système pour utiliser l'enregistrement par cryptographie à clé publique sur un environnement mobile
CN101546401A (zh) * 2008-03-28 2009-09-30 海尔集团公司 基于nfc移动终端的电子支付方法及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9992607B2 (en) 2016-10-07 2018-06-05 Microsoft Technology Licensing, Llc eSIM identification data

Also Published As

Publication number Publication date
CN103781054A (zh) 2014-05-07

Similar Documents

Publication Publication Date Title
WO2014059941A1 (fr) Procédé et dispositif de résiliation d'abonnement de terminal
US9661666B2 (en) Apparatus and methods of identity management in a multi-network system
EP2919497B1 (fr) Procédé d'activation d'une carte sim logicielle, procédé et terminal d'association d'une carte sim logicielle à un réseau, et dispositif d'accès à un réseau
EP2854433B1 (fr) Procédé, système et dispositif associé destinés à réaliser une carte sim virtuelle
US10764746B1 (en) Electronic subscriber identity module (eSIM) transfer from inactive device
EP2708069B1 (fr) Verrouillage sim pour un environnement à plusieurs sim
CN109716805B (zh) 一种签约数据集的安装方法、终端及服务器
US11989543B2 (en) Method for interoperating between bundle download process and eSIM profile download process by SSP terminal
CN111148088B (zh) 管理移动终端的方法、装置、设备和存储介质以及系统
WO2018129754A1 (fr) Procédé de gestion de fichier de configuration d'euicc et dispositif associé
WO2012024796A1 (fr) Procédé et appareil adaptés pour transférer des données d'identité à un dispositif sans fil en vue de leur utilisation temporaire
WO2017041562A1 (fr) Procédé et dispositif d'identification d'une identité d'utilisateur d'un dispositif terminal
US11678176B1 (en) Electronic subscriber identity module (eSIM) transfer via activation code
US20140331295A1 (en) Credential management gateway and method
WO2021168829A1 (fr) Procédé de vérification d'identifiant d'utilisateur et dispositif associé
JP2012199751A (ja) 管理サーバ、通信システム、管理方法およびプログラム
WO2019161939A1 (fr) Procédés, dispositifs et programmes d'ordinateur pour fournir ou commander des profils d'opérateur dans des terminaux
WO2022062889A1 (fr) Procédé et appareil de gestion de tranche, et dispositif de communication
WO2015089969A1 (fr) Procédé et dispositif de gestion d'accessibilité pour terminal/périphérique de terminal m2m
CN111163063B (zh) 边缘应用管理方法及相关产品
CN103124252A (zh) 客户端应用访问鉴权处理方法和装置
WO2018007461A1 (fr) Procédé, serveur et système pour envoyer des données d'un dispositif source à un dispositif de destination
JP2013513986A (ja) サーバにおけるスマートカード・セキュリティ機能プロファイル
CN115362700A (zh) 用于管理智能安全平台的事件的方法和装置
WO2011029297A1 (fr) Système et procédé permettant de doter un équipement machine-à-machine d'un module d'identité de communication machine

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: 13846979

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13846979

Country of ref document: EP

Kind code of ref document: A1