Management Method and Management Server for Utilizing Multiple SIM Cards

Abstract

A management method and a management server for using multiple SIM cards enable a large number of users to start using them easily. First, an MVNO (230A) that has obtained one or more SIM cards logs in to a management screen provided in association with the user ID of the MVNO (230A) by the MVNE (210). From the perspective of the MVNE (210), it is determined whether the user ID of the user accessing the management screen of its management server is under an MVNO contract (S301). If it is under an MVNO contract, the identification numbers assigned to the respective SIM cards and, if necessary, the passwords for authentication are received as registration information (S302). When the management server of the MVNE (210) has received the required registration information, each SIM card whose identification number is determined by the registration information is registered as the SIM card used by the MVNO (230A) in a manner associated with the user ID in the management server of the MVNE (210) or in a database (221) accessible from the management server of the MVNE (210) (S303).

Description

[0001] This application is a divisional application of the following application,

[0002] The filing date of the original application: June 9, 2016,

[0003] The application number of the original application: 201680033805.3,

[0004] The invention name of the original application: Management method and management server for using multiple SIM cards. Technical Field

[0005] The present invention relates to a management method and a management server for using multiple SIM cards. Background Art

[0006] In recent years, the emergence of MVNOs (Mobile Virtual Network Operators) has led to the continuous development of the retail of wireless communication lines. In the past, it was MNOs (Mobile Network Operators) with wireless communication infrastructure that directly provided wireless communication services to end users, while MVNOs use the wireless communication infrastructure of MNOs to provide unique wireless communication services to end users.

[0007] MVNOs can be roughly classified into the following forms, that is, those without any communication infrastructure of their own company, and those with their own communication infrastructure, connecting this communication infrastructure to the communication infrastructure of MNOs to provide wireless communication services (refer to Figure 1 ). Compared with the former, since the latter also has its own communication infrastructure, it can set prices corresponding to communication qualities such as communication speed and communication capacity, and thus try to respond to various demands. For example, SIM cards for wireless communication services with prices suppressed by setting the maximum communication capacity capable of high-speed data communication are available in the market.

[0008] Specifically, such MVNOs receive the provision of SIM cards from MNOs and then provide them to end users. MVNOs use a database to manage communication qualities such as speed limits and capacity limits set for each SIM card and the identification numbers of each SIM card, and provide wireless communication services according to the contract content of mobile terminals such as smartphones and tablet computers that request access to the Internet.

[0009] There is also a situation where an MVNE (Mobile Virtual Network Enabler) that provides support services for MVNOs to smoothly carry out their businesses is interposed between MNOs and MVNOs. The MVNE receives the provision of SIM cards from MNOs and then provides them to MVNOs.

[0010] When an MVNO or MVNE retains the endpoints of the core network, i.e., the gateway (GGSN under 3G and P-GW under LTE), as its own company's communication infrastructure, it can establish an L2 connection with the communication infrastructure of the MNO (SGSN under 3G and S-GW under LTE) (full MVNO connection (S5 / S8 interface under LTE and Gn interface under 3G)), forming an L2 tunnel between the wireless terminal equipped with the end-user's SIM card and the gateway. Compared with the L3 connection (light MVNO connection), the degree of freedom in designing wireless communication services is increased, which has attracted the attention of the industry. Summary of the Invention

[0011] Problems to be Solved by the Invention

[0012] In recent years, with the development of the Internet of Things (IoT), the demand for wireless communication services has increased significantly. The IoT adds wireless communication capabilities to all objects and connects them to the Internet. Hereinafter, a wireless device that can be connected to a computer network including the Internet is called an "IoT device".

[0013] Although IoT devices also include mobile terminals such as smartphones and tablet computers held by people, their scope has expanded to transportation means such as cars that move at high speeds compared to people, and conversely, devices such as sensors that do not move away from a specific location very much and need to communicate in a different form from people. Along with this, the required communication speeds and frequencies vary. It can also be said that the optimal communication quality changes. For example, when considering IoT-izing 10 or 100 industrial machines by embedding SIM cards and enabling them to communicate remotely with other devices, even if each IoT device only communicates at a low frequency and with a low capacity, a large number of SIM cards need to be installed.

[0014] With the popularization of IoT devices, the number of enterprises and other users who manage multiple IoT devices is increasing. On the other hand, it is currently difficult for each user to uniformly manage multiple IoT devices, that is, multiple SIM cards installed in these IoT devices, by signing a contract with an MNO as an MVNO. First, consider the following scenario: With the popularization of IoT devices, demands become diversified, and thus a small number of SIM cards, such as several or dozens of SIM cards, are used experimentally for IoT implementation of devices. If one wants to manage SIM cards uniformly instead of using them by signing individual contracts, the MVNO needs to sign a contract with the MNO. However, in many cases, such small-scale MVNOs are unable to sign contracts with the MNO from the beginning. Second, even if a contract is signed in the form of a small-scale MVNO, if one wants to add several or dozens of SIM cards, the MNO needs to be requested to associate the additional SIM cards with the ID of the MVNO (hereinafter referred to as "user ID"). After the association is completed, the additional SIM cards are received and utilization begins. Specifically, the association is performed through the following operations: The identification numbers of each SIM card, such as the name, IMSI, and ICCID of the MVNO, as well as the status such as in use or suspended, are manually input into each SIM card through a dedicated device and registered in the MNO's database. The series of procedures associated with the circulation of the SIM cards to the MVNO is rather complicated, and sometimes it takes several weeks. In addition, initial investment is required economically, and thus the needs of users who hope to use the required number of SIM cards for IoT devices as needed cannot be met.

[0015] The industry has anticipated the rapid increase in the number of such small-scale and medium-scale MVNOs, and thus strongly hopes for an environment in which a large number of users can easily become MVNOs.

[0016] The present invention has been made in view of such problems, and its object is to enable a large number of users to easily start utilization in a management method and a management server for using multiple SIM cards.

[0017] Technical means for solving the problem

[0018] To achieve this object, a first aspect of the present invention is a management method for using multiple SIM cards, characterized by including the following steps: receiving registration information for registering one or more SIM cards; and associating one or more SIM cards whose identification numbers are determined by the received registration information with the user ID of the user of the multiple SIM cards.

[0019] In addition, a second aspect of the present invention is characterized in that, in the first aspect, the communication status of the associated one or more SIM cards is set to suspended to start management.

[0020] In addition, the third aspect of the present invention is characterized in that, in the second aspect, the communication status can be changed on the management screen provided for the user ID.

[0021] In addition, the fourth aspect of the present invention is characterized in that, in the third aspect, the communication status can be changed by selecting at least multiple ones from among suspended, in use, cancelled, and in transit.

[0022] In addition, the fifth aspect of the present invention is characterized in that, in the third or fourth aspect, the communication quality of each SIM card can be changed on the management screen.

[0023] In addition, the sixth aspect of the present invention is characterized in that, in the fifth aspect, the communication quality is at least one of speed limit, capacity limit, and time period limit.

[0024] In addition, the seventh aspect of the present invention is characterized in that, in the fifth or sixth aspect, the management of the communication status or the communication quality is executed in an instance on the cloud.

[0025] In addition, the eighth aspect of the present invention is characterized in that, in any one of the first to seventh aspects, it includes the following steps: receiving a change application from a user of one or more SIM cards associated with the user ID; and generating registration information for one or more SIM cards that are the object of the change application based on the change application.

[0026] In addition, the ninth aspect of the present invention is characterized in that, in the eighth aspect, the communication status of one or more SIM cards that are the object of the change application is changed upon receipt of the change application.

[0027] In addition, the tenth aspect of the present invention is characterized in that, in any one of the first to ninth aspects, the registration information includes the identification numbers of the one or more SIM cards, and the step of receiving the registration information includes the following steps: detecting on the management screen provided for the user ID that a registration button has been clicked or tapped; displaying an input screen for registering the one or more SIM cards based on the detection; and associating the one or more SIM cards for which identification numbers have been input on the input screen with the user ID.

[0028] In addition, the eleventh aspect of the present invention is characterized in that, in any one of the first to ninth aspects, the registration information includes a group ID that assigns the one or more SIM cards as a group of SIM cards, and this management method includes the following steps: determining the identification numbers of the one or more SIM cards by referring to a correspondence table of the group ID obtained from the received registration information and the one or more SIM cards assigned the group ID.

[0029] In addition, the twelfth aspect of the present invention is characterized in that, in the eleventh aspect, the registration information includes a password corresponding to the group ID.

[0030] In addition, the thirteenth aspect of the present invention is characterized in that, in the eleventh or twelfth aspect, it further includes the following steps: generating a registration code corresponding to the registration information; and sending the registration code to the user's terminal.

[0031] In addition, the fourteenth aspect of the present invention is characterized in that, in any one of the first to thirteenth aspects, the association between the one or more SIM cards and the user ID is performed after obtaining the group ID without requiring additional input from the user.

[0032] In addition, the fifteenth aspect of the present invention is characterized in that, in any one of the eleventh to thirteenth aspects, it further includes the following steps: after obtaining the group ID, displaying an input screen for specifying the group name of the one or more SIM cards, associating the one or more SIM cards with the user ID, and the registration information further includes the group name.

[0033] In addition, the sixteenth aspect of the present invention is characterized in that, in the fourteenth or fifteenth aspect, after the association, the SIM cards associated with the user ID are displayed on the management screen provided for the user ID.

[0034] In addition, the seventeenth aspect of the present invention is a program for causing a computer to execute a management method for using multiple SIM cards. The program is characterized in that the management method includes the following steps: receiving registration information for registering one or more SIM cards; and associating the one or more SIM cards whose identification numbers are determined by the received registration information with the user ID of the user of the multiple SIM cards.

[0035] In addition, the eighteenth aspect of the present invention is a management server for using multiple SIM cards. The management server is characterized in that it includes: a receiving unit that receives registration information for registering one or more SIM cards; and a registration unit that associates and registers the one or more SIM cards whose identification numbers are determined by the received registration information with the user ID of the user of the multiple SIM cards.

[0036] Effects of the Invention

[0037] In the past, an MVNO could not obtain the supply of SIM cards without going through a series of complicated procedures with an MNO. However, according to an embodiment of the present invention that makes full use of the user ID, an MVNO that has obtained the supply of SIM cards can associate with its own user ID afterwards. Therefore, SIM cards can also be placed on the distribution network in a state where they have not been associated with the user ID of the MVNO, enabling a large number of MVNOs to easily start using multiple SIM cards. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 A diagram schematically showing an MVNO that connects its own communication infrastructure to the communication infrastructure of an MNO to provide wireless communication services.

[0039] Figure 2 A diagram showing the distribution route of multiple SIM cards that can be realized by an embodiment of the present invention.

[0040] Figure 3 A diagram showing an initial setting method for using multiple SIM cards according to an embodiment of the present invention.

[0041] Figure 4 A diagram showing a management screen for multiple SIM cards according to an embodiment of the present invention.

[0042] Figure 5 A diagram showing a registration screen for a SIM card according to an embodiment of the present invention.

[0043] Figure 6 A diagram showing an example of a gateway on the cloud that performs the functions of a management server according to an embodiment of the present invention.

[0044] Figure 7 A diagram showing another example of a gateway on the cloud that performs the functions of a management server according to an embodiment of the present invention.

[0045] Figure 8 A diagram showing a management screen for multiple SIM cards according to an embodiment of the present invention.

[0046] Figure 9 A diagram showing a method for selecting a group of multiple SIM cards according to an embodiment of the invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0047] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

[0048] Furthermore, in this specification, a user who manages and uses multiple SIM cards in a unified manner is also referred to as an "MVNO".

[0049] In addition, the definitions of terms such as MNO and MVNE sometimes vary by country. In this specification, a case where an MNO has an SGSN for 3G and an S-GW for LTE as communication infrastructure like in Japan, and an MVNE has a GGSN for 3G and a P-GW for LTE as communication infrastructure is used as an example for explanation.

[0050] (First Embodiment)

[0051] Figure 2 Shows the distribution routes of multiple SIM cards that can be achieved through an embodiment of the present invention.

[0052] First, when the MVNE 210 requests the MNO 220 to provide a certain quantity of SIM cards, the MNO 220 manually inputs the name of the MVNE 210, the identification number of each SIM card, states such as in use and suspended, etc. into each SIM card through a dedicated device, and registers them in the database 221 of the MNO 220, and provides these SIM cards to the MVNE 210 by methods such as mailing. By the MVNE 210 pre-storing a large number of registered SIM cards in advance, it is possible to quickly supply one or more SIM cards to multiple MVNOs 230A and 230B as users. This is a business model where the MVNE 210 holds SIM cards for multiple MVNOs 230A and 230B as a shared resource in a manner that can provide the required quantity when needed, and thus distributes them on demand.

[0053] As the distribution routes for the MVNOs 230A and 230B to obtain SIM cards, it can be roughly divided into the following cases: directly receiving supplies from the MVNE 210, and indirectly receiving supplies via retail channels such as e-commerce websites and stores. As will be described below, according to an embodiment of the present invention that makes full use of the user ID, it is possible to use retail channels for the distribution of SIM cards to the MVNOs 230A and 230B, and thus meet the needs of users who hope to use SIM cards for IoT devices in a unified management environment in the required quantity as needed. In particular, it will greatly promote the emergence of a large number of small-scale and medium-scale MVNOs required in the future.

[0054] The MVNE 210 enters into a contract by receiving user data such as name, address, payment card number or account number from each MVNO 230A and 230B in a random order, and then assigns a user ID to each MVNO 230A and 230B in advance. The user data is stored in the management server of the MVNE 210 or a database 211 that can be accessed from the management server of the MVNE 210. This state is defined as "under MVNO contract". The MVNE 210 can provide a management screen for each MVNO 230A and 230B on the management server. Since the contract with the MNO 220 is carried out between the MVNE 210, depending on the decision of the MVNE 210, users who wish to become MVNOs can uniformly manage multiple SIM cards as MVNOs as long as they meet the minimum conditions that are looser than the contract with the MNO.

[0055] Here, referring to Figure 3 , an initial setting method for using multiple SIM cards according to an embodiment of the present invention that makes full use of the user ID will be described. The description starts from the stage of receiving one or more SIM cards from a certain MVNO 230A. At this time, the MVNO 230A may have SIM cards that are already in use, or may be in a situation where the use starts for the first time with the SIM cards received this time.

[0056] First, the MVNO 230A that has obtained one or more SIM cards logs in to the management screen provided in association with the user ID of the MVNO 230A on the MVNE 210. From the perspective of the MVNE 210, it is determined whether the user ID of the user accessing the management screen of the management server of the MVNE 210 is under MVNO contract (S301).

[0057] In the case of being under MVNO contract and having logged in, the identification numbers assigned to each SIM card and the passwords for authentication assigned as needed are received as registration information (S302).

[0058] When the management server of the MVNE 210 can receive the required registration information, each SIM card whose identification number is determined by the registration information is registered in association with the user ID in the management server of the MVNE 210 or a database 221 that can be accessed from the management server of the MVNE 210 as the SIM card used by the MVNO 230A (S303).

[0059] For example, it can be used Figure 4The management screen 400 as shown can be logged in using a user ID (e.g., "user1@xxxx.jp") 410. After that, by clicking or tapping the "SIM Registration" button 420, according to the detection of the click or tap, an input screen for inputting required input items as shown is displayed. It is also possible to photograph a physical medium on which the identification number of each SIM card etc. is recorded in image form and upload it, and the management server side of the MVNE 210 that receives the image performs image analysis, thereby determining the required input items. The password given to each SIM card can be set as a one-time password that becomes invalid once it is associated with the user ID. Figure 5 An input screen for inputting required input items as shown. It is also possible to photograph a physical medium on which the identification number of each SIM card etc. is recorded in image form and upload it, and the management server side of the MVNE 210 that receives the image performs image analysis, thereby determining the required input items. The password given to each SIM card can be set as a one-time password that becomes invalid once it is associated with the user ID.

[0060] The above description was made assuming that the management screen is provided on the management server of the MVNE 210, but the management screen can also be displayed within an application running on a wireless terminal such as a smartphone or a tablet computer.

[0061] On the management screen, the SIM cards associated with the user ID can also be continuously displayed after the association with the user ID.

[0062] In the past, an MVNO could not obtain the supply of SIM cards without going through a series of complicated procedures with an MNO. However, according to one embodiment of the present invention that makes full use of the user ID, an MVNO that has obtained the supply of SIM cards can be associated with its own account (user ID) afterwards, so that SIM cards can also be placed on the circulation network in a state where they have not been associated with the account of the MVNO.

[0063] Being able to be placed on the circulation network without determining the MVNO to be used means, for example, that SIM cards can be supplied to an MVNO via retail channels such as e-commerce websites and stores, which plays a great role in the supply of SIM cards for a large number of small-scale and medium-scale MVNOs that will emerge in the future.

[0064] Furthermore, although it is now also possible to purchase single SIM cards via retail channels such as e-commerce websites and stores, it should be clearly pointed out that these cards must be managed individually, and unified management of several or dozens of SIM cards cannot be achieved.

[0065] In addition, the management server of one embodiment of the present invention includes a processing unit such as a CPU and a storage unit, and by the processing unit reading and executing a program stored in the storage unit, each function of the above management method can be realized to constitute the management server.

[0066] (Second Embodiment)

[0067] In the first embodiment, an example was described in which the "SIM registration" button 420 on the click management screen 400 is clicked to input required registration information. However, the registration information can be simultaneously marked on one or more SIM cards received by the MVNO 230A in the form of a QR code (registered trademark) or the like, and the registration information is read at the MVNO 230A, so that the received SIM card is associated with the user ID. This is effective even in the case of one SIM card, and in the case of multiple SIM cards, it makes the association with the user ID extremely simple.

[0068] Specifically, first, in the management server of the MVNE 210, a group ID (e.g., "group123456789") that has not been associated with a specific user ID is assigned to a group of SIM cards including one or more SIM cards. The management server of the MVNE 210 maintains a correspondence table representing the correspondence between the group ID and the identification numbers of the group of SIM cards to which the group ID is assigned for each group ID.

[0069] Then, the management server of the MVNE 210 generates a registration code such as a barcode, a QR code (registered trademark), or a URL representing the registration information including the group ID and an authentication password given as needed. The password or the registration information including the password can also be set as a hash value. The registration information or the registration code can be stored in the management server in a manner associated with the group ID or in a storage medium accessible from the management server. The URL can be set as a URL including the group ID and the required password or its hash value, and can include a part representing the management server of the MVNE 210 and a part representing the group ID and the required password or its hash value (e.g., "https: / / www.soracom.io / group123456789 / ").

[0070] The MVNO 230A that receives the registration code can, for example, receive the registration code in an application running on a wireless terminal and input the registration information represented by the registration code to the management server of the MVNE 210. In the case where the registration code is a URL, by accessing the URL corresponding to the registration code, such as a web page uniquely specified for each group ID, the registration information can be input to the management server of the MVNE 210. That is, when the management server of the MVNE 210 receives the registration information, in the case where the user ID is in the MVNO contract and logged in, the identification numbers of the SIM cards assigned the group ID included in the registration information can be determined with reference to the correspondence table. The association between a group of SIM cards and the user ID can also be performed after obtaining the group ID from the registration information without additional input from the user. The password corresponding to each group ID can be set as a one-time password that becomes invalid once the SIM card assigned the group ID is associated with the user ID.

[0071] In the past, user data had to be registered for each SIM card. By providing a management method using such a group ID, the initial setting of an MVNO that requires multiple SIM cards can be significantly simplified.

[0072] Furthermore, in the above example, the case of providing a registration code to MVNO 230A has been described, but it is also possible to directly transmit the registration information including the group ID.

[0073] In addition, an input screen for specifying the group name of a group of SIM cards for associating with the user ID can be displayed after, at the time of, or before obtaining the group ID from the registration information. Thus, the SIM cards that have been registered in association with the user ID can be managed separately from the newly added SIM cards. When the registration code is a URL, the group name can also be given using URL parameters instead of the input screen, so that the registration information includes the group name.

[0074] For example, taking the case where an IoT device provider is MVNO 230A as an example, consider the situation where the IoT device provider provides its devices to multiple enterprises in the form of a lease contract. At this time, the IoT device provider can assign a group name to each enterprise and manage the wireless communication services provided to each enterprise separately as an MVNO.

[0075] In addition, when the MVNE 210 has determined the MVNO 230A, the registration code or registration information can also be sent digitally to the MVNO 230A, and the SIM cards themselves are delivered separately. For example, also taking the case where an IoT device provider is MVNO 230A as an example here, the registration code or registration information can be sent to the IoT device provider to make it associate with the user ID, and the SIM cards themselves are sent to the enterprises that receive the supply of IoT devices from the IoT device provider.

[0076] (Third Embodiment)

[0077] In the first and second embodiments, the description is made assuming that the management server of the MVNE 210 is composed of one or more servers, but the management server can also be set as an instance on the cloud.

[0078] More specifically, at least a part of the gateway (for enabling data from a wireless terminal to pass through an IP network, etc.) held by the MVNE 210 can be installed on the cloud, and the above management server function is assumed by the gateway or an instance on the cloud that can be accessed from the gateway.

[0079] Here, in this specification, the so-called "cloud" refers to a system that can dynamically set and provide computing resources such as CPUs, memory, storage devices, and network bandwidth as needed over a network. For example, the cloud can be utilized through AWS or the like.

[0080] In the gateway, controls such as speed limit, capacity limit, and time period limit for wireless terminals can be performed. Therefore, for example, on the management screen, the communication quality, communication status, etc. of one or more SIM cards associated with the user ID can be changed.

[0081] Performing such processing in the gateway will inevitably lead to a decrease in the number of simultaneously connectable devices required by the gateway due to the physical limitations of the server on which the gateway is installed. Also, in most cases, the number of gateways that the MVNE 210 can perform L2 connections (or L3 connections) with the communication infrastructure of the MNO 220 is pre-specified by the MNO 220 and set with a limit on the number of units. Therefore, even without considering cost, the situation of adding hardware more than the limited number to increase the number of simultaneously connectable devices is not acceptable. Thus, as Figure 6 shown, in the gateway 610 constituting the communication system 600, it is split into a first server group 611 that is the part connected to the communication infrastructure of the MNO 220 and a second server group 612 that is the part for performing additional data processing, etc. The management server function is borne by the second server group 612 or a server group 620 that can be accessed from the second server group 612. Thus, even if additional data processing in the gateway 610 is added, the occupation of computing resources that suppresses the increase in the number of simultaneously connectable devices of the gateway 610 can be avoided, and thus rich and complex functions can be installed on the gateway 610.

[0082] Both the first server group 611 and the second server group 612 can also be cloudified. In particular, by setting each server constituting the second server group 612 as an instance on the cloud, the number of instances can be increased as needed to expand the scale, and thus computing resources can be used substantially infinitely.

[0083] Ideally, it is configured like the example of the gateway 710 shown in Figure 7 such that the number of servers constituting the second server group 712 exceeds the number of servers constituting the first server group 711. If the number of servers constituting the second server group 712 is less than or equal to the number of servers constituting the first server group 711, resources such as the number of sessions and the number of IP flows determined by the number of servers or instances will not increase, and thus there may be a situation where sufficient scalability cannot be achieved. Figure 7 In, an example where the second server group 712 is shared by each server of the first server group 711 is shown, but it is not limited to this example. Furthermore, an example where the management server function is borne by the second server group 712 is envisioned here.

[0084] Furthermore, each server constituting the first server group 611 can be set as an instance on the cloud. As a result, the IP addresses of the servers can be virtualized to improve fault tolerance. Even if a certain server crashes, for example, by maintaining the correspondence between the first server group 611 and the second server group 612 in the latest state in real time on the database of the third server group 620, the fault recovery can be instantaneously achieved by changing the IP address to another server. In addition, by cloudifying, the expansion and contraction can be freely performed. Therefore, an instance with the optimal CPU, memory, storage device, and network bandwidth corresponding to the processing load can be selected. As a result, there is no need to always prepare hardware that meets the maximum demand during peak hours, and thus the optimization of costs can be achieved. The same applies to the cloudification of the second server group 612.

[0085] Regarding the communication from the MNO 220 to the MVNE 210, the IP addresses of the first server group 611 are pre-registered in the database of the MNO 220. For example, it is possible to determine which server in the first server group 611 to transfer data from the wireless terminal to in a round-robin scheduling manner. The registered information can be set as a transmission destination address such as a MAC address for identifying the transmission destination in addition to the IP address.

[0086] Each server constituting the first server group 611 includes: a receiving unit that receives data from the wireless terminal; a selection unit that selects one from a plurality of transmission destination addresses based on the header of the received data; and a forwarding unit that forwards the received data to the transmission destination address selected by the selection unit.

[0087] The transfer of data from the wireless terminal, that is, a data packet including a payload and a header, from the first server group 611 to the second server group 612 can be performed by rewriting the IP address indicated by the header attached to the payload received from the wireless terminal in the first server group 611 to one of the plurality of IP addresses corresponding to the second server group 312. Subsequently, each server of the first server group 611 transfers the data to the server constituting the second server group 612 corresponding to one of the rewritten plurality of IP addresses. The rewriting is an example of the processing required when selecting an IP address for transferring the data received by each server of the first server group 611 to the server constituting the second server group 612, and other tunneling technologies (IPIP, GRE, IPsec, GTP, etc.) can also be implemented for the transfer.

[0088] In the third server group 620, the number of servers constituting the second server group 612 is controlled according to the index of processing capacity to expand or contract the scale. The third server group 620 monitors the indexes of the processing capacity of the instances used in the first server group 611 and the second server group 212. Whenever a connection request is sent from a wireless terminal, the connection can be allocated to an instance with a lower processing load. Examples of the indexes for monitoring include CPU load, memory utilization rate, disk read, disk write, network receive traffic, network transmit traffic, etc.

[0089] In addition, the third server group 620 can be used to select the correspondence between the first server group 611 and the second server group 612. When the first server group 611 receives a GTP connection start request (GTP-C) containing the IMSI, TEID, etc. of a wireless terminal, it sends a CreateSession message to the third server group 6200. The third server group 620 that receives this message can select the second server group 612 as the transfer destination according to the index of processing capacity created by continuously or intermittently monitoring the utilization status of the computing resources of the second server group 612, i.e., CPU, memory, storage device, network traffic, etc. By using the third server group 620 to record the correspondence of the identifier of the L2 tunnel, the identification number of the wireless terminal, the IP address of the first server group 611, and the IP address of the second server group 612 at the time of the GTP connection start request, the session of the L2 tunnel can be restored in case of a failure of the first server group 611 or the second server group 612.

[0090] Although the connection start request can also be received in the first server group 611 so that the first server group 611 also executes the functions on the control plane (C-Plane), a control plane (C-Plane) server group that executes the functions on the control plane (C-Plane) can be separately prepared in the form of a part of the gateway 610 or a part of the communication system 600. Thus, the computing resources of the first server group 611 can be used for simultaneous connections with more devices. In this case, the first server group 611 does not receive the connection start request and thus does not have the functions on the control plane (C-Plane).

[0091] As additional data processing in the gateway, for example, generating an alarm according to the communication status of a group of SIM cards assigned with a group ID can be cited. The communication status of each SIM card can be monitored, and an alarm can be issued when the specified traffic set by the contract of the SIM card is exceeded. In addition, the communication frequency band can be adjusted.

[0092] Examples of an IP network or the like that is an access target of a wireless terminal include a private system in addition to the Internet. When implementing at least a part of an on-premises private system and a gateway 610 on a cloud, different IP networks on the same cloud or IP networks on different clouds are included in the private system, and the communication system 600 or the gateway 610 can be connected to these private systems through a dedicated line or a virtual dedicated line.

[0093] (Fourth Embodiment)

[0094] Figure 8 A setting change screen 800 for multiple SIM cards showing an embodiment of the present invention. When an MVNO 230A, which is a user of a SIM card, accesses a web page on a management server of an MVNE 210 or a server that can access information stored in the management server, a management screen 800 for multiple SIM cards of the MVNO 230A for the user can be viewed.

[0095] In addition to displaying the identification number 801 assigned to each SIM card, it also displays a name 802, a group name 803, a usage status 804, a type 805 of communication quality assigned to the SIM card, an expiration date 806, and the like.

[0096] Here, the type 805 of communication quality can be selected by clicking or the like, and if necessary, settings such as speed limits, capacity limits, and time period limits can be changed. The changed communication quality is stored in the management server together with the identification number of the SIM card.

[0097] When there are multiple groups 803, for example, by selecting a group using a drop-down menu 900 for selecting search conditions arranged on the right side of the Figure 9 search window, a search specifying the group can be performed. When performing a search specifying a group, as Figure 8 shown, a list of SIM cards associated with the corresponding group, here "Test Group 1", appears, so the check box on the left can be selected, and for example, selections can be made as appropriate from "Operations" to uniformly change the setting contents.

[0098] For example, when a list of SIM cards associated with "Test Group 1" is displayed and the group is changed to "Test Group 3", it is possible to easily transfer SIM registrations between groups.

[0099] After associating one or more SIM cards with a user ID, the communication status 804 can be set to "Inactive" to start management. By setting it to Inactive, communication costs can be suppressed until actual need.

[0100] When the MVNE 210 has determined the MVNO 230A and sends the registration code or registration information digitally to the MVNO 230A while the SIM card itself is delivered separately, the communication status 804 can also be set to "in transit" when the SIM card is sent, and the communication status 804 can be set and changed to "in use" on the occasion of inputting the registration information by inputting the registration code, etc. by the MVNO 230A. In addition, it can also be set and changed to "in use" when a specified date or a specified period has passed.

[0101] (Fifth Embodiment)

[0102] Taking the case where the IoT device provider listed in the first embodiment is the MVNO 230A as an example again, consider the case of transferring the IoT devices leased by the IoT device provider. At this time, the user of the SIM card installed in the IoT device also changes from the first MVNO to the second MVNO, but this change can be reflected in the management server of the MVNE 210.

[0103] The first MVNO that wants to change the user of one or more SIM cards used previously through transfer, sub-lending, etc. first makes a user change application to the MVNE 210. After receiving the change application, the MVNE 210 generates registration information including a password or a registration code indicating the registration information. At this time, the management server of the MVNE 210 can change the communication status 804 of the SIM card with the change application to "inactive", etc. In addition, it can be set not to be displayed on the management screen 800 of the first MVNO.

[0104] The first MVNO receives the registration code or registration information generated by the MVNE 210 and provides it to the second MVNO together with the device as appropriate. As described in the first embodiment or the second embodiment, the second MVNO inputs the received registration code or registration information into the management server of the MVNE 210, whereby these SIM cards can be associated with the user ID of the second MVNO.

[0105] Thus, the transfer of the SIM card between MVNOs, that is, the change of the user ID, can be performed simply and safely, and for example, the transfer or sub-lending of IoT devices can be easily achieved.

[0106] Symbol Explanation

[0107] 210 MVNE

[0108] 211 Database of MVNE

[0109] 220 MNO

[0110] 221 Database of MNO

[0111] 230A, 230B MVNO

[0112] 400 Management Screen

[0113] 410 User ID

[0114] 420 "SIM Registration" Button

[0115] 403 Group Name Corresponding to Group Identifier

[0116] 600 Communication System (Communication Platform)

[0117] 610 Gateway

[0118] 611 First Server Group

[0119] 612 Second Server Group

[0120] 620 Servers Accessible from the Second Server Group (Third Server Group)

[0121] 700 Communication System (Communication Platform)

[0122] 710 Gateway

[0123] 711 First Server Group

[0124] 712 Second Server Group

[0125] 800 Setting Change Screen (Management Screen)

[0126] 801 Identification Number

[0127] 802 Name of SIM Card

[0128] 803 Group Name

[0129] 804 Status

[0130] 805 SIM Type

[0131] 806 Expiration Date

[0132] 900 Drop - down Menu for Selecting Search Conditions

Claims

1. A management method, which is a management method for using multiple SIM cards. The management method is characterized by including the following steps: The server receives registration information for registering one or more SIM cards. The registration information includes a group ID that assigns the one or more SIM cards as a group of SIM cards; Determine the identification numbers of the one or more SIM cards with reference to the correspondence between the group ID obtained from the received registration information and the one or more SIM cards assigned with the group ID; and The server associates the one or more SIM cards with the identification numbers determined with the user ID of the user of the multiple SIM cards, Either the communication quality or the communication status for each identification number can be changed from the management screen provided by the server to the user ID.

2. The management method according to claim 1, characterized in that, Either the communication quality or the communication status for multiple identification numbers can be uniformly changed from the management screen.

3. The management method according to claim 1, characterized in that The management of either the communication quality or the communication status is performed in the server, which is an instance on the cloud.

4. The management method according to claim 1, wherein The registration information includes a password corresponding to the group ID.

5. The management method according to claim 1, wherein It further includes the following steps: Generate a registration code corresponding to the registration information; and Send the registration code to the user's terminal.

6. The management method according to claim 1, characterized in that, The association of the one or more SIM cards with the user ID is performed after the acquisition of the group ID without additional input from the user.

7. The management method according to claim 1, wherein It further includes the following steps: after the acquisition of the group ID, display an input screen for specifying the group name of the one or more SIM cards, and the one or more SIM cards are associated with the user ID, The registration information further includes the group name.

8. The management method according to any one of claims 1 to 7, characterized in that, After the association, display the SIM cards associated with the user ID on the management screen provided to the user ID.

9. A memory that stores a program for causing a computer to execute a management method for using multiple SIM cards. The memory is characterized in that The management method includes the following steps: The server receives registration information for registering one or more SIM cards. The registration information includes a group ID that assigns the one or more SIM cards as a group of SIM cards; Determine the identification numbers of the one or more SIM cards with reference to the correspondence between the group ID obtained from the received registration information and the one or more SIM cards assigned with the group ID; and The server associates the one or more SIM cards with the identification numbers determined with the user ID of the user of the multiple SIM cards, Either the communication quality or the communication status for each identification number can be changed from the management screen provided by the server to the user ID.

10. A management server, which is a management server as an instance on the cloud for using multiple SIM cards. The management server is characterized in that Receive registration information for registering one or more SIM cards, where the registration information includes a group ID that assigns the one or more SIM cards as a group of SIM cards. Determine the identification numbers of the one or more SIM cards with reference to the correspondence between the group ID obtained from the received registration information and the one or more SIM cards assigned with the group ID. Register by associating the one or more SIM cards with determined identification numbers with the user ID of the user of the multiple SIM cards. Either the communication quality or the communication status for each identification number can be changed from the management screen provided by the server to the user ID.

Images