WO2017185647A1

WO2017185647A1 - Softsim-based imsi number management and calling methods, server and network side device

Info

Publication number: WO2017185647A1
Application number: PCT/CN2016/100676
Authority: WO
Inventors: 赵龙凯
Original assignee: 宇龙计算机通信科技(深圳)有限公司
Priority date: 2016-04-29
Filing date: 2016-09-28
Publication date: 2017-11-02
Also published as: CN105722063B; CN105722063A

Abstract

Disclosed is a SoftSIM-based international mobile subscriber identification (IMSI) number management method, for use in implementing one-to-one switching binding of a same SoftSIM number with multiple IMSI numbers. The method in embodiments of the present invention comprises: a SoftSIM management server checks whether a subscriber downloads a first SoftSIM data packet that pertains to a first network operator, the first SoftSIM data packet comprising a first IMSI number; if yes, the SoftSIM management server carries out one-to-one binding of a SoftSIM number with the first IMSI number based on a first mapping relationship, the SoftSIM number being allocated by the SoftSIM management server when the subscriber registers a SoftSIM account; the SoftSIM management server stores the first mapping relationship. The embodiments of the present invention also provide a SoftSIM-based IMSI number calling method, a SoftSIM server, and a network side device, such that a calling-party subscriber can still page a called-party subscriber corresponding to the same SoftSIM number even after the IMSI number is changed, thereby improving the convenience for the subscriber to use SoftSIM.

Description

SoftSIM-based IMSI number management and calling method, server and network side device

This application claims priority to Chinese Patent Application No. 201610281418.3, entitled "SoftSIM-based IMSI Number Management and Calling Method, Server and Network Side Equipment", submitted to the China Patent Office on April 29, 2016. The content is incorporated herein by reference.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a SIMSIM number management and calling method based on SoftSIM, a server, and a network side device.

Background technique

MSISDN (Mobile Subscriber International ISDN/PSTN number) refers to the number that the calling subscriber needs to dial to call a mobile subscriber in the GSM PLMN (GSM Public Land Mobile Network). The PSTN (Public Switched Telephone Network) number is the only number that can identify mobile users in the public telephone network switching network numbering plan.

IMSI (IMSI: International Mobile Subscriber Identification Number) is a logo that distinguishes mobile users and is stored in the SIM card and can be used to distinguish valid information of mobile users.

As is well known, each physical SIM card stores a unique IMSI, and the IMSI in the SIM card can be bound one-to-one with the user's MSISDN. In the prior art, when a user interacts with the network by dialing a telephone number, the network essentially interacts with the network by converting the MSISDN to the corresponding IMSI. However, in fact, the SIM is only a module of the universal integrated circuit card UICC hardware. The UICC, such as contacts, phone numbers and applications, etc., are ensured in the terminal to ensure the integrity and security of various sensitive information, while the SIM is a complete Can be based on the application of the software, and does not need to be bound to the UICC hardware, then with the trend that the smart terminal is gradually becoming a mobile PC, the existing SIM card will also be converted into SoftSIM, that is, after the UICC is embedded in the terminal motherboard, the terminal can Software-based support, log in to SoftSIM's user management center at any time, download the operator's SoftSIM data package from the cloud server, such as IMSI, Ki, Opc and other SoftSIM card parameters, and then access the network through authentication, so that the network can be used. Various voice or data services, etc.

It can be seen that SoftSIM technology allows users to log in to the user management center anytime and anywhere, and can apply for SoftSIM data packets based on different operators to access services of different operators. However, if the user frequently changes the SoftSIM card parameters to access the network of different operators, the user cannot timely broadcast the MSISDN corresponding to the IMSI number of the currently used SoftSIM to other users, thereby causing others to obtain the user in time. The latest MSISDN and timely contact with yourself, and frequent card change will also bring a lot of trouble to others to contact themselves, thus reducing the user experience.

Summary of the invention

The embodiment of the present invention provides a SIMSIM number management and calling method based on SoftSIM, a server, and a network side device, so that the same SoftSIM number can correspond to multiple IMSI numbers, that is, in the process of replacing the subsequent IMSI number, the same SoftSIM The number can still be mapped to a one-to-one binding relationship with the replaced one IMSI number, and the calling party user can still page the called party user corresponding to the same SoftSIM number, thereby improving the convenience of the user using SoftSIM.

In view of this, the first aspect of the present invention provides a method for managing an IMSI number based on SoftSIM, which may include:

The SoftSIM management server detects whether the user downloads the first SoftSIM data packet belonging to the first network operator, and the first SoftSIM data packet includes the first international mobile subscriber identity (IMSI) number;

If yes, the SoftSIM management server performs a one-to-one binding of the first mapping relationship between the SoftSIM number and the first IMSI number, and the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account;

The SoftSIM management server stores the first mapping relationship.

With reference to the first aspect of the embodiments of the present invention, in a first implementation manner of the first aspect of the embodiment, after the first mapping relationship is stored by the SoftSIM management server, the method further includes:

The SoftSIM management server receives the instruction to cancel the IMSI number sent by the user;

The SoftSIM management server releases the binding of the SoftSIM number and the first IMSI number according to the command to cancel the IMSI number, and deletes the first mapping relationship.

With reference to the first aspect of the embodiments of the present invention, in a second implementation manner of the first aspect of the embodiments of the present disclosure, after the first mapping relationship is stored by the SoftSIM management server, the method further includes:

If the first network operator detects that the first IMSI number meets the preset logout condition, the SoftSIM management server receives the logout IMSI number command sent by the first network operator;

With reference to the first aspect of the embodiments of the present invention, the first embodiment or the second embodiment of the first aspect of the embodiment of the present invention, in the third implementation manner of the first aspect of the embodiment of the present invention, in SoftSIM After the management server releases the binding of the SoftSIM number and the first IMSI number according to the command to cancel the IMSI number, and the first mapping relationship is deleted, the method further includes:

The SoftSIM management server detects whether the user downloads the second SoftSIM data packet belonging to the second network operator, and the second SoftSIM data packet includes the second IMSI number;

If yes, the SoftSIM management server performs a one-to-one binding of the second mapping relationship between the SoftSIM number and the second IMSI number;

The SoftSIM management server stores the second mapping relationship.

A second aspect of the present invention provides a method for calling an IMSI number based on SoftSIM, which may include:

The network side device receives the call instruction of the SoftSIM number, and the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account;

The network side device queries, according to the call instruction, whether the SoftSIM management server has a mapping relationship corresponding to the SoftSIM number;

If yes, the network side device determines the IMSI number corresponding to the SoftSIM number according to the mapping relationship, and makes a call to the IMSI number.

A third aspect of the present invention provides a SoftSIM management server, which may include:

a detecting module, configured to detect whether the user downloads a first SoftSIM data packet belonging to the first network operator, where the first SoftSIM data packet includes a first international mobile subscriber identity IMSI number;

The binding module is configured to: when the detecting module detects that the user downloads the first SoftSIM data packet belonging to the first network operator, the first mapping relationship between the SoftSIM number and the first IMSI number is first-to-one binding, and the SoftSIM number is used. Assigned to the SoftSIM management server when the user registers a SoftSIM account;

The storage module is configured to store the first mapping relationship.

With reference to the third aspect of the embodiments of the present invention, in a first implementation manner of the third aspect of the embodiment, the SoftSIM management server further includes:

The first receiving module is configured to receive a logout IMSI number command sent by the user;

The first releasing module is configured to release the binding of the SoftSIM number and the first IMSI number according to the deregistered IMSI number command received by the first receiving module;

Delete the module and set it to delete the first mapping.

With reference to the third aspect of the embodiments of the present invention, in a second implementation manner of the third aspect of the embodiment, the SoftSIM management server further includes:

The second receiving module is configured to: when the first network operator detects that the first IMSI number meets the preset cancellation condition, receive the cancellation IMSI number command sent by the first network operator;

The second releasing module is configured to release the binding of the SoftSIM number and the first IMSI number according to the cancellation IMSI number command received by the second receiving module;

Delete the module and set it to delete the first mapping.

With reference to the third aspect of the embodiments of the present invention, the first embodiment or the second embodiment of the third aspect of the embodiment of the present invention, in the third implementation manner of the third aspect of the embodiment of the present invention,

The detecting module is further configured to detect whether the user downloads a second SoftSIM data packet belonging to the second network operator, where the second SoftSIM data packet includes a second IMSI number;

The binding module is further configured to perform a one-to-one binding of the second mapping relationship between the SoftSIM number and the second IMSI number when the second detecting module detects that the user downloads the second SoftSIM data packet belonging to the second network operator. ;

The storage module is further configured to store the second mapping relationship.

A fourth aspect of the present invention provides a network side device, which may include:

The receiving module is configured to receive a call instruction of the SoftSIM number, and the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account;

The query module is configured to query, according to the call instruction received by the receiving unit, whether the SoftSIM management server has a mapping relationship corresponding to the SoftSIM number;

a determining module, configured to: when the query unit queries the SoftSIM management server to have a mapping relationship corresponding to the SoftSIM number, determine an IMSI number corresponding to the SoftSIM number according to the mapping relationship;

The calling module is configured to make a call to the IMSI number determined by the determining unit.

It can be seen from the above technical solutions that the embodiments of the present invention have the following advantages:

In this embodiment, the SoftSIM management server may detect whether the user downloads the first SoftSIM data packet belonging to the network operator, and the first SoftSIM data packet may include the first international mobile subscriber identity IMSI number, and if downloaded, the SoftSIM management server The one-to-one binding of the SoftSIM number to the first IMSI number may be performed. The SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account, and the SoftSIM management server may store the first mapping relationship. Therefore, by binding the SoftSIM number to the first IMSI number, the user can use the SoftSIM number as the MSISDN number as the contact mode of others, and other users can manage the SoftSIM number when they subscribe to the user corresponding to the SoftSIM number. The first mapping relationship stored by the server finds the first IMSI number and pages the first IMSI number, and in the process of replacing the subsequent IMSI number, the same SoftSIM number can still be mapped with the replaced one IMSI number. The one-to-one binding, thereby avoiding the trouble and inconvenience caused by frequent replacement of the IMSI number, and improving the user experience.

DRAWINGS

1 is a schematic diagram of an embodiment of a method for managing an IMSI number based on SoftSIM according to an embodiment of the present invention;

2 is a schematic diagram of another embodiment of a method for managing an IMSI number based on SoftSIM according to an embodiment of the present invention;

3 is a schematic diagram of another embodiment of a method for managing an IMSI number based on SoftSIM according to an embodiment of the present invention;

4 is a schematic diagram of an embodiment of a method for calling an IMSI number based on SoftSIM according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of another embodiment of a SoftSIM management server according to an embodiment of the present invention; FIG.

6 is a schematic diagram of another embodiment of a SoftSIM management server according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of another embodiment of a SoftSIM management server according to an embodiment of the present invention; FIG.

FIG. 8 is a schematic diagram of an embodiment of a network side device according to an embodiment of the present invention.

FIG. 9 is a schematic structural diagram of a server according to an embodiment of the present invention.

FIG. 10 is a schematic structural diagram of a network side device according to an embodiment of the present invention.

detailed description

The embodiment of the present invention provides an IMSI number management and calling method based on SoftSIM, a server, and a network side device, so that the same SoftSIM number can be switched and bound with multiple IMSI numbers, that is, in the process of replacing the subsequent IMSI number. The same SoftSIM number can still be mapped to a one-to-one binding with a replacement IMSI number. The calling party user can still page the called party user corresponding to the same SoftSIM number, thereby improving the user's use of SoftSIM. Convenience.

The terms "first", "second", "third", "fourth", etc. (if present) in the specification and claims of the present invention and the above figures are used to distinguish similar objects without having to use To describe a specific order or order. It is to be understood that the data so used may be interchanged where appropriate so that the embodiments described herein can be implemented in a sequence other than what is illustrated or described herein. In addition, the terms "comprises" and "comprises" and "the" and "the" are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or device that comprises a series of steps or units is not necessarily limited to Those steps or units may include other steps or units not explicitly listed or inherent to such processes, methods, products or devices.

With the development and maturity of communication technology, mobile terminals have become an indispensable part of people's daily life. The touch operation of smart terminals has gradually replaced the button operation, bringing more convenient performance. In order to meet the user's better visual experience, the size of the terminal screen is getting larger and larger, which makes the user have a blind zone that is difficult to control in the case of one-hand operation, and often requires two hands to cooperate to realize the manipulation of the icon on the terminal screen. However, in some cases, the user's one-hand operation is more convenient, and the large-screen design also brings inconvenience to the user.

For ease of understanding, the specific process in the embodiment of the present invention is described below. Referring to FIG. 1, an embodiment of the SIMSI number management method based on SoftSIM in the embodiment of the present invention includes:

101, the SoftSIM management server detects whether the user downloads the first SoftSIM data packet belonging to the first network operator, and if not, proceeds to step 102, and if yes, proceeds to step 103;

In this embodiment, the user can download the SoftSIM application on the terminal side, and the terminal can include, but is not limited to, a smart phone, a tablet computer, etc., when the user uses the SoftSIM application in the terminal, the user can log in to the SoftSIM management server, and can be independent based on SoftSIM. You can select and replace the SIM card service provided by the network operator. You can apply for the SoftSIM data packet belonging to the network operator through the SoftSIM management server. Specifically, the SoftSIM management server may detect whether the user downloads the first SoftSIM data packet belonging to the first network operator, and the first SoftSIM data packet may include the first International Mobile Subscriber Identity (IMSI) number.

It can be understood that the first SoftSIM data packet in this embodiment may include the first IMSI number as described above, and may also include SoftSIM card parameters such as Ki, Opc, etc. in the actual application, which is not limited herein. .

It should be noted that the first network operator in this embodiment may include any one of the network operators, such as China Mobile, China Unicom, China Telecom, and a virtual operator.

102. Perform other processes;

If the SoftSIM management server detects that the user does not download the first SoftSIM data packet belonging to the first network operator, no other operations may be performed, so that the SoftSIM number registered by the user does not have a corresponding IMSI number.

103. The SoftSIM management server performs a one-to-one binding of the first mapping relationship between the SoftSIM number and the first IMSI number.

If the SoftSIM management server detects that the user downloads the first SoftSIM data packet that belongs to the first network operator, the SoftSIM management server may perform a one-to-one binding of the first mapping relationship between the SoftSIM number and the first IMSI number, where the SoftSIM number is The SoftSIM Management Server is assigned when a user registers for a SoftSIM account.

Specifically, in the actual application, when the user logs in to the SoftSIM application for the first time, the SoftSIM account needs to be registered. After the user registers, the SoftSIM management server can assign a SoftSIM number to the user, which is the same as the MSISDN, but the same SoftSIM number can be used. Does not correspond to multiple IMSI numbers at the same time. In this embodiment, after detecting that the user downloads the first SoftSIM data packet that belongs to the first network operator, the SoftSIM management server may obtain the first IMSI number included in the first SoftSIM data packet, if the current SoftSIM number is not the same as the other The IMSI number is bound, and the SoftSIM management server can bind the SoftSIM number to the first IMSI number one-to-one.

It should be noted that the user can register different SoftSIM numbers according to different identity information, but the SoftSIM management server only assigns a unique SoftSIM number to one identity information, which is not limited hereafter.

Further, after the user registers the SoftSIM number, the SoftSIM number may also be requested to be logged off by the user, or may be logged off by the SoftSIM management server. In this embodiment, the logout mode may be specifically:

The SoftSIM management server receives the cancellation softSIM number command sent by the user;

The SoftSIM management server logs out the SoftSIM number registered by the user according to the cancellation of the SoftSIM number command; or,

If the SoftSIM management server detects that the SoftSIM number is not used within the preset duration, the SoftSIM management server logs out the SoftSIM number registered by the user.

In practical applications, if the user applies for multiple SoftSIM numbers, when the SoftSIM management server receives the logout SoftSIM command, it can log out one or more SoftSIM numbers according to the user's selection. It can be understood that after the SoftSIM number is logged off, the binding between the SoftSIM number and the IMSI will also be released, that is, there will be no corresponding mapping relationship between the SoftSIM number and the IMSI number.

104. The SoftSIM management server stores the first mapping relationship.

In this embodiment, after the one-to-one binding of the first mapping relationship between the SoftSIM number and the first IMSI number, the SoftSIM management server may store the first mapping relationship, such as storing in the user management center.

In this embodiment, the SoftSIM management server can perform the one-to-one binding of the SoftSIM number and the first IMSI number, and can store the first mapping relationship of the binding, so that other users can implement the pair after storing the SoftSIM number. The first IMSI number having the first mapping relationship with the SoftSIM number is used for the call, and the SoftSIM number is unique to the identity information of the user, so that the same SoftSIM number can be switched and bound with different IMSI numbers, so that frequent replacement is performed. The IMSI number also does not affect the convenience of the user to use the SoftSIM number.

It should be noted that, in an actual application, the user may cancel the first IMSI number and re-apply to use the second IMSI number. In this embodiment, the logout of the first IMSI number may be initiated by the user, or may be performed by the network. The merchants canceled the transaction and explained the following separately:

Referring to FIG. 2, another embodiment of the SoftSIM-based IMSI number management method in the embodiment of the present invention includes:

Steps 201 to 204 in this embodiment are the same as steps 101 to 104 in the embodiment shown in FIG. 1, and details are not described herein again.

205. The SoftSIM management server receives an instruction to cancel the IMSI number sent by the user.

In this embodiment, if the user wants to replace another IMSI number of the same network operator during the use of the current first IMSI number, or wants to replace another IMSI number of another network operator, the user may apply to the SoftSIM management server. Applying to cancel the first IMSI number, that is, the SoftSIM management server can receive the logout IMSI number command sent by the user.

206. The SoftSIM management server releases the binding of the SoftSIM number and the first IMSI number according to the command to cancel the IMSI number, and deletes the first mapping relationship.

After the SoftSIM management server receives the command to cancel the IMSI number sent by the user, the binding of the SoftSIM number to the first IMSI number may be released according to the revoked IMSI command, and the stored first mapping relationship may be deleted, so that other users may page the SoftSIM. When the number is not available, because there is no corresponding first IMSI number, other users can be alerted to the call failure. At the same time, the valid information in the first SoftSIM data packet stored by the user in the terminal is also deleted at the same time as the binding relationship is released, thereby effectively releasing the storage space of the terminal and avoiding the illegal use of the first SoftSIM data packet. information.

Further, in a practical application, when the SoftSIM management server releases the binding of the SoftSIM number to the first IMSI number and deletes the first mapping relationship, the first network operator may send a request to cancel the first IMSI number, so that The first network operator can update the first IMSI number to other user-selectable IMSI number resources in time.

207, the SoftSIM management server detects whether the user downloads the second SoftSIM data packet belonging to the second network operator, if not, step 202 is performed, and if yes, step 208 is performed;

In this embodiment, after the SoftSIM management server logs out the first IMSI number, the user can re-bind with other IMSI numbers by using the SoftSIM number, and the SoftSIM management server can detect whether the user downloads the second SoftSIM belonging to the second network operator. The data packet, the second SoftSIM data packet may include a second IMSI number.

It can be understood that the second SoftSIM data packet in this embodiment may include the second IMSI number as described above, and may also include SoftSIM card parameters such as Ki, Opc, etc. in the actual application, which is not limited herein. .

It should be noted that the second network operator in this embodiment may include any one of the network operators, such as China Mobile, China Unicom, China Telecom, and the virtual operator.

208. The SoftSIM management server performs a one-to-one binding of the second mapping relationship between the SoftSIM number and the second IMSI number.

Based on the content described in step 103 in the embodiment shown in FIG. 1, in this embodiment, the SoftSIM management server detects that the user downloads the second SoftSIM data packet belonging to the second network operator, and the SoftSIM management server may The two IMSI numbers perform a one-to-one binding of the second mapping relationship.

209. The SoftSIM management server stores the second mapping relationship.

After the one-to-one binding of the SoftSIM number and the second IMSI number in the second mapping relationship, the SoftSIM management server may store the second mapping relationship, so that when other users page the SoftSIM number, the mapping relationship may be utilized to the second IMSI. The number is called.

In this embodiment, a specific process for the user to apply for the first IMSI number to be replaced with the second IMSI number is described, that is, the mapping relationship between the IMSI number and the IMSI number to which the soft SIM number is unchanged is changed, so that the SoftSIM number is corresponding. After the change of the IMSI number, other users can still use the SoftSIM number to implement paging, which can reduce the impact on the user and other users of the SoftSIM number due to the change of the IMSI number, which is beneficial to improve the user experience.

Referring to FIG. 3, another embodiment of the SoftSIM-based IMSI number management method in the embodiment of the present invention includes:

Steps 301 to 304 in this embodiment are the same as steps 101 to 104 in the embodiment shown in FIG. 1, and details are not described herein again.

305. If the first network operator detects that the first IMSI number meets the preset logout condition, the SoftSIM management server receives the logout IMSI number command sent by the first network operator.

In this embodiment, in order to avoid waste of resources, the first network operator may also detect the first IMSI number in real time. If it is detected that the first IMSI number meets the preset logout condition, the SMIMS number command may be sent to the SoftSIM management server.

For example, in a practical application, assuming that SoftSIM is the same as an existing SIM, different network operators may have different charging methods, and then the first network operator detects that the first IMSI number is in arrears and is preset. The first network operator can actively log out the first IMSI number, that is, the SoftSIM management server can receive the cancellation IMSI number command sent by the first network operator.

It can be understood that, in this embodiment, only the foregoing example is used to describe the default cancellation condition for the network operator to send the command to cancel the IMSI number. In actual applications, the network operator can also detect that the first IMSI number meets other pre-conditions. When the logout condition is set, the command to cancel the IMSI number can be sent to the SoftSIM management server, which is not limited herein.

Steps 306 to 309 in this embodiment are the same as steps 206 to 209 in the embodiment shown in FIG. 2, and details are not described herein again.

Different from the embodiment shown in FIG. 2, the replacement of the first IMSI number into the second IMSI number in this embodiment is based on the first network operator's logout of the first IMSI number, but also indicates that the SoftSIM number is not logged out. If the user needs to re-apply for the second IMSI number, the same SoftSIM number can still achieve one-to-one binding with the second IMSI number, so that the replacement of the IMSI number is the same as that achieved by the embodiment shown in FIG. 2.

The above describes the management method of the IMSI number from the SoftSIM management server side. Based on the binding relationship between the SoftSIM and the IMSI number, the following describes the calling method of the IMSI number. Referring to FIG. 4, the SIMI based on SoftSIM in the embodiment of the present invention is described. An embodiment of the number calling method includes:

401. The network side device receives a call instruction of a SoftSIM number.

In this embodiment, the calling party side may perform contact storage on the SoftSIM number of the called party side, and when the calling party side needs to initiate a call request to the called party side, the calling party side terminal The call instruction of the SoftSIM number can be received, and the call instruction of the SoftSIM number is transmitted to the network side device, and the network side device specifically implements the call process, and the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account.

402, the network side device according to the call command to query whether the SoftSIM management server has a mapping relationship corresponding to the SoftSIM number, if not, proceed to step 403, and if so, proceed to step 404;

After receiving the call instruction of the SoftSIM number, the network side device may query, according to the call instruction, whether the SoftSIM management server has a mapping relationship corresponding to the SoftSIM number.

Specifically, in a practical application, the SoftSIM management server may be provided with each user management center, and each SoftSIM number of the user may have a belonging user management center in the SoftSIM management server, and the corresponding mapping relationship of the SoftSIM number is stored in the user management. The center, so that the network side device can determine the user management center corresponding to the SoftSIM number in the SoftSIM management server according to the call instruction, and query whether there is a mapping relationship corresponding to the SoftSIM number in the user management center.

It can be understood that, if the mapping relationship of the corresponding SoftSIM number is stored in other locations of the SoftSIM management server, the network side device may also use other methods for querying, which is not limited herein.

403. Perform other processes;

If the network side device does not have a mapping relationship with the SoftSIM number, the SoftSIM number does not have a corresponding IMSI number, and the network side device can prompt the calling party side to fail, such as an empty number.

404. The network side device determines, according to the mapping relationship, an IMSI number corresponding to the SoftSIM number, and performs a call on the IMSI number.

If the network side device queries the SoftSIM management server to have a mapping relationship corresponding to the SoftSIM number according to the call instruction, the network side device may determine the IMSI number corresponding to the SoftSIM number according to the mapping relationship, and may call the IMSI number.

In this embodiment, the specific process of the IMSI number paging is described from the network side device on the calling party side where the SoftSIM number is stored, and the network side device refers to the SoftSIM number paging, but finally the mapping with the SoftSIM number is implemented. The paging of the IMSI number of the relationship, that is, the SoftSIM number can be used as a unique identification code to implement paging of the user corresponding to the SoftSIM number, regardless of whether the IMSI number having a mapping relationship with the SoftSIM number is changed, thereby improving the user. Experience.

The SoftSIM-based IMSI number management and call method in the embodiment of the present invention is described above. The following describes the SoftSIM management server and the network side device in the embodiment of the present invention. Referring to FIG. 5, a SoftSIM management server is used in the embodiment of the present invention. Examples include:

The detecting module 501 is configured to detect whether the user downloads the first SoftSIM data packet belonging to the first network operator, where the first SoftSIM data packet includes the first international mobile subscriber identity (IMSI) number;

The binding module 502 is configured to: when the detecting module detects that the user downloads the first SoftSIM data packet that belongs to the first network operator, the first mapping relationship between the SoftSIM number and the first IMSI number is first-to-one, SoftSIM The number is assigned by the SoftSIM management server when the user registers for the SoftSIM account;

The storage module 503 is configured to store the first mapping relationship.

In this embodiment, the binding module 502 can bind the SoftSIM number to the first IMSI number one-to-one, and the storage module 503 can store the first mapping relationship of the binding, so that other users after storing the SoftSIM number, that is, The call can be made to the first IMSI number having the first mapping relationship with the SoftSIM number, and the SoftSIM number is unique to the identity information of the user, so that the same SoftSIM number can be switched and bound with different IMSI numbers. This makes it difficult to change the IMSI number frequently without affecting the user's use of the SoftSIM number.

Referring to FIG. 6, another embodiment of the SoftSIM management server in the embodiment of the present invention includes:

The module 601 in this embodiment is the same as the module 501 in the embodiment shown in FIG. 5. The module 602 is the same as the module 502 in the embodiment shown in FIG. 5. The module 603 is the same as the module 503 in the embodiment shown in FIG. I will not repeat them here.

The first receiving module 604 is configured to receive a logout IMSI number command sent by the user;

The first releasing module 605 is configured to release the binding of the SoftSIM number and the first IMSI number according to the deregistered IMSI number command received by the first receiving module;

The deleting module 606 is configured to delete the first mapping relationship.

Based on the execution function of the foregoing deletion module 606, the detection module 601, the binding module 602, and the storage module 603 in the embodiment may further perform the following processing:

The detecting module 601 is further configured to detect whether the user downloads a second SoftSIM data packet belonging to the second network operator, where the second SoftSIM data packet includes a second IMSI number;

The binding module 602 is further configured to perform a one-to-one binding of the second mapping relationship between the SoftSIM number and the second IMSI number when the detecting module detects that the user downloads the second SoftSIM data packet that belongs to the second network operator.

The storage module 603 is further configured to store the second mapping relationship.

In this embodiment, after the first receiving module 604 receives the canceled IMSI number command sent by the user for the first IMSI number, if the detecting module 601 detects that the user downloads the second SoftSIM data packet belonging to the second network operator, the binding is performed. The module 602 can bind the second IMSI number in the second SoftSIM data packet to the SoftSIM number, that is, update the mapping relationship of the IMSI number bound to the SoftSIM number, so that the IMSI number corresponding to the SoftSIM number is obtained. After the change occurs, other users can still use the SoftSIM number to implement paging, which can reduce the impact on the user and other users of the SoftSIM number due to the change of the IMSI number, which is beneficial to improve the user experience.

Referring to FIG. 7, another embodiment of the SoftSIM management server in the embodiment of the present invention includes:

The module 701 in this embodiment is the same as the module 601 in the embodiment shown in FIG. 6. The module 702 is the same as the module 602 in the embodiment shown in FIG. 6. The module 703 is the same as the module 603 in the embodiment shown in FIG. I will not repeat them here.

The second receiving module 704 is configured to: when the first network operator detects that the first IMSI number meets the preset cancellation condition, receive the cancellation IMSI number command sent by the first network operator;

The second releasing module 705 is configured to release the binding of the SoftSIM number and the first IMSI number according to the deregistered IMSI number command received by the second receiving module;

The module 706 in this embodiment is the same as the module 606 in the embodiment shown in FIG. 6, and details are not described herein again.

Different from the embodiment shown in FIG. 6, the replacement of the first IMSI number into the second IMSI number in this embodiment is based on the second receiving module 704 receiving the first IMSI number sent by the first network operator to cancel the IMSI number, but the same In the case that the SoftSIM number is not logged out, if the detecting module 701 detects that the user downloads the second SoftSIM data packet including the second IMSI number, the binding module 702 can implement one of the same SoftSIM number and the second IMSI number. The binding to a binding, and thus the replacement of the IMSI number is the same as that achieved by the embodiment shown in FIG.

Referring to FIG. 8, an embodiment of a network side device in an embodiment of the present invention includes:

The receiving module 801 is configured to receive a call instruction of the SoftSIM number, and the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account;

The querying module 802 is configured to query, according to the call instruction received by the receiving unit, whether the SoftSIM management server has a mapping relationship corresponding to the SoftSIM number;

The determining module 803 is configured to: when the query unit queries the SoftSIM management server to have a mapping relationship corresponding to the SoftSIM number, determine the IMSI number corresponding to the SoftSIM number according to the mapping relationship;

The calling module 804 is configured to make a call to the IMSI number determined by the determining unit.

In this embodiment, the specific process of the IMSI number paging is described from the network side device of the calling party side storing the SoftSIM number, and the receiving module 801 receives the call instruction of the SoftSIM number, but finally implements the call module 804. The paging of the IMSI number that has a mapping relationship with the SoftSIM number, that is, the SoftSIM number can be used as the unique identification code to implement paging of the user corresponding to the SoftSIM number, regardless of whether the IMSI number having a mapping relationship with the SoftSIM number changes. , thus improving the user experience.

FIG. 9 is a schematic structural diagram of a management server according to an embodiment of the present invention. In this embodiment of the present invention, the management server may be a SoftSIM management server. As shown in FIG. 9, the management server 900 in the embodiment of the present invention includes at least one processor 910, such as a CPU, at least one receiver 913, at least one memory 914, at least one transmitter 915, and at least one communication bus 912. The communication bus 912 is used to implement connection communication between these components. The receiver 913 and the transmitter 915 may be wired transmission ports, or may be wireless devices, for example, including antenna devices, for performing data communication with other devices. The memory 914 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.

The processor 910 can execute an operating system of the management server 900 and various installed application programs, program codes, and the like. For example, each module described above includes the modules described in FIG. 5, FIG. 6, and FIG.

Program code is stored in the memory 914, and the processor 910 can invoke program code stored in the memory 914 to perform related functions via the communication bus 912. For example, the modules described above in Figures 5, 6, and 7 are program code stored in the memory 914 and executed by the processor 910 to implement the functions of the various units to implement SoftSIM-based The IMSI number is called.

In one embodiment of the invention, the memory 914 stores a plurality of instructions that are executed by the processor 910 to implement a SoftSIM based IMSI number calling method. Specifically, the processor 910 detects whether the user downloads a first SoftSIM data packet belonging to the first network operator, where the first SoftSIM data packet includes a first international mobile subscriber identity IMSI number; if yes, the The processor 910 performs a one-to-one binding of the SoftSIM number to the first IMSI number in a first mapping relationship, where the SoftSIM number is allocated by the processor 910 when the user registers a SoftSIM account; 910 stores the first mapping relationship.

In a further embodiment, after storing the first mapping relationship, the processor 910 receives a logout IMSI number command sent by the user, and cancels the SoftSIM number and the first according to the logout IMSI number command. Binding of the IMSI number and deleting the first mapping relationship.

In a further embodiment, after storing the first mapping relationship, if the first network operator detects that the first IMSI number meets a preset logout condition, the processor 910 receives the first Deleting the IMSI number command sent by the network operator; releasing the binding of the SoftSIM number and the first IMSI number according to the cancellation IMSI number command, and deleting the first mapping relationship.

In a further embodiment, after the binding of the SoftSIM number to the first IMSI number is released according to the deregistered IMSI number command, and the first mapping relationship is deleted, the processor 910 detects the user. Whether to download a second SoftSIM data packet belonging to the second network operator, the second SoftSIM data packet includes a second IMSI number; if yes, the processor 910 performs the second soft SIM number and the second IMSI number A one-to-one binding of the mapping relationship; the processor 910 stores the second mapping relationship.

For a specific implementation of the above-mentioned instructions by the processor 910, reference may be made to the description of related steps in the corresponding embodiments in FIG. 1 to FIG. 3, and details are not described herein.

FIG. 10 is a schematic structural diagram of a network side device according to an embodiment of the present invention. In the embodiment of the present invention, the network side device may be different types of electronic devices, such as: a smart phone, a tablet computer, a palmtop computer, and a mobile internet device, a personal digital assistant, a media player, a smart TV, a smart watch, and smart glasses. , smart bracelets, etc. As shown in FIG. 10, the network side device 1000 in the embodiment of the present invention includes: at least one processor 1010, such as a CPU, at least one receiver 1013, at least one memory 1014, at least one transmitter 1015, and at least one communication bus 1012. The communication bus 1012 is used to implement connection communication between these components. The receiver 1013 and the transmitter 1015 may be wired transmission ports, or may be wireless devices, for example, including antenna devices for performing data communication with other devices. The memory 1014 may be a high speed RAM memory or a non-volatile memory such as at least one disk memory.

The processor 1010 can execute an operating system of the network side device 1000 and various installed application programs, program codes, and the like. For example, each module described above includes the modules described in FIG. 8 above.

Program code is stored in the memory 1014, and the processor 1010 can invoke program code stored in the memory 1014 to perform related functions via the communication bus 1012. For example, the modules described above in FIG. 8 are program code stored in the memory 1014 and executed by the processor 1010 to implement the functions of the various units to implement a SoftSIM-based IMSI number call.

In one embodiment of the invention, the memory 1014 stores a plurality of instructions that are executed by the processor 1010 to implement a SoftSIM-based IMSI number calling method. Specifically, the processor 1010 receives a call instruction of a SoftSIM number, where the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account, and queries whether the SoftSIM management server exists corresponding to the SoftSIM according to the call instruction. The mapping relationship of numbers. If yes, the processor 1010 determines an IMSI number corresponding to the SoftSIM number according to the mapping relationship, and performs a call on the IMSI number.

For details, refer to the description of the related steps in the corresponding embodiment of FIG. 4, and the details are not described here.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that The technical solutions described in the embodiments are modified, or the equivalents of the technical features are replaced by the equivalents of the technical solutions of the embodiments of the present invention.

Claims

A method for managing an IMSI number based on SoftSIM, comprising:

The SoftSIM management server detects whether the user downloads a first SoftSIM data packet belonging to the first network operator, where the first SoftSIM data packet includes a first international mobile subscriber identity IMSI number;

If yes, the SoftSIM management server performs a one-to-one binding of the SoftSIM number to the first IMSI number in a first mapping relationship, where the SoftSIM number is allocated by the SoftSIM management server when the user registers a SoftSIM account. ;

The SoftSIM management server stores the first mapping relationship.
The SoftSIM-based IMSI number management method according to claim 1, wherein after the SoftSIM management server stores the first mapping relationship, the method further includes:

Receiving, by the SoftSIM management server, a logout IMSI number command sent by the user;

The SoftSIM management server releases the binding of the SoftSIM number and the first IMSI number according to the revoked IMSI number command, and deletes the first mapping relationship.
The SoftSIM-based IMSI number management method according to claim 1, wherein after the SoftSIM management server stores the first mapping relationship, the method further includes:

If the first network operator detects that the first IMSI number meets a preset logout condition, the SoftSIM management server receives the logout IMSI number command sent by the first network operator;

The SoftSIM management server releases the binding of the SoftSIM number and the first IMSI number according to the revoked IMSI number command, and deletes the first mapping relationship.
The SoftSIM-based IMSI number management method according to any one of claims 1 to 3, wherein the SoftSIM management server cancels the SoftSIM number and the first IMSI number according to the logout IMSI number instruction. After the binding, and deleting the first mapping relationship, the method further includes:

The SoftSIM management server detects whether the user downloads a second SoftSIM data packet belonging to a second network operator, where the second SoftSIM data packet includes a second IMSI number;

If yes, the SoftSIM management server performs a one-to-one binding of the second mapping relationship between the SoftSIM number and the second IMSI number;

The SoftSIM management server stores the second mapping relationship.
A method for calling an IMSI number based on SoftSIM, comprising:

The network side device receives a call instruction of a SoftSIM number, and the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account;

The network side device queries, according to the call instruction, whether the SoftSIM management server has a mapping relationship corresponding to the SoftSIM number;

If yes, the network side device determines an IMSI number corresponding to the SoftSIM number according to the mapping relationship, and performs a call to the IMSI number.
A SoftSIM management server, comprising:

a detecting module, configured to detect whether the user downloads a first SoftSIM data packet belonging to the first network operator, where the first SoftSIM data packet includes a first international mobile subscriber identity IMSI number;

a binding module, configured to: when the detecting module detects that the user downloads the first SoftSIM data packet belonging to the first network operator, performing a first mapping relationship between the SoftSIM number and the first IMSI number a binding, the SoftSIM number is allocated by the SoftSIM management server when the user registers a SoftSIM account;

And a storage module, configured to store the first mapping relationship.
The SoftSIM management server according to claim 6, wherein the SoftSIM management server further comprises:

a first receiving module, configured to receive a logout IMSI number command sent by the user;

The first releasing module is configured to release the binding of the SoftSIM number and the first IMSI number according to the cancellation IMSI number command received by the first receiving module;

The module is deleted and is set to delete the first mapping relationship.
The SoftSIM management server according to claim 6, wherein the SoftSIM management server further comprises:

The second receiving module is configured to: when the first network operator detects that the first IMSI number meets a preset cancellation condition, receive a logout IMSI number command sent by the first network operator;

a second release module, configured to release the binding of the SoftSIM number and the first IMSI number according to the cancellation IMSI number command received by the second receiving module;

The module is deleted and is set to delete the first mapping relationship.
A SoftSIM management server according to any one of claims 6 to 8, wherein

The detecting module is further configured to detect whether the user downloads a second SoftSIM data packet belonging to a second network operator, where the second SoftSIM data packet includes a second IMSI number;

The binding module is further configured to: when the second detecting module detects that the user downloads a second SoftSIM data packet belonging to the second network operator, performing the second, the SoftSIM number and the second IMSI number. One-to-one binding of mapping relationships;

The storage module is further configured to store the second mapping relationship.
A network side device, comprising:

a receiving module, configured to receive a call instruction of a SoftSIM number, where the SoftSIM number is allocated by the SoftSIM management server when the user registers the SoftSIM account;

a querying module, configured to query, according to the call instruction received by the receiving unit, whether a SoftSIM management server has a mapping relationship corresponding to the SoftSIM number;

a determining module, configured to: when the query unit queries the SoftSIM management server to have the mapping relationship corresponding to the SoftSIM number, determine an IMSI number corresponding to the SoftSIM number according to the mapping relationship;

The calling module is configured to make a call to the IMSI number determined by the determining unit.