Detailed Description
In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It may be evident, however, that the subject invention may be practiced without these specific details. The following description is, therefore, not to be taken as limiting the scope of the invention. In some example scenarios, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.
For purposes of this specification, an MNO is a service provider that owns or controls or owns and controls a cellular network and all necessary elements (including backhaul infrastructure, billing, customer services, provisioning computer systems) to provide wireless voice and data communication services to its subscribed mobile users. An MNO is also known as a wireless service provider, wireless carrier, cellular company, cellular network service provider, or mobile network carrier.
A cellular network operated by an MNO may be implemented using multiple radio access networks connected to a core network. Each regional portion of a cellular network may contain a plurality of base stations (also referred to as network elements). MNOs may provide telecommunication services in accordance with one or more technical standards, such as Enhanced Data Rates for GSM Evolution (EDGE), wideband Code Division Multiple Access (W-CDMA), high Speed Packet Access (HSPA), long Term Evolution (LTE), CDMA-2000 (Code Division Multiple Access2000 ), and 5th generation (5th generation, 5g).
The core network of the cellular network may be connected with one or more backend servers that provide backend services. Backend services may include Business Support Systems (BSSs) and/or embedded subscriber identity module (eSIM) subscription management servers (e.g., SM-DP +). In some exemplary embodiments, the eSIM subscription management server may also be referred to as a profile provisioning server. For example, the services provided by the BSS may include product management, order management, revenue management, and customer management. The services provided by SM-DP + can include creating an eSIM profile in response to a valid eSIM profile request and securely providing the eSIM profile to the user device for loading onto the eUICC.
The processing unit executes program instructions or code segments for implementing embodiments of the present invention. Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program instructions for performing the necessary tasks may be stored in a computer-readable storage medium.
The processing units, such as processing units 101, 155, and 181, may be Complex Programmable Logic Devices (CPLDs), field Programmable Gate Arrays (FPGAs), central Processing Units (CPUs), microprocessors, microcontrollers, digital Signal Processors (DSPs), any combination of those devices, or any other circuitry that can be configured to execute program instructions to implement the embodiments disclosed herein.
A system bus may carry signals between a main component (e.g., a processing unit) and peripheral components or between peripheral components. A system bus may contain multiple signal lines that connect components internal or external to the device. The system bus disclosed herein may be implemented using any of several types of bus structures, including a memory bus, a peripheral bus, or a local bus using any of a variety of bus architectures.
FIG. 1A is a schematic block diagram showing the hardware blocks of an exemplary MSA (e.g., MSA 100). MSA 100 includes a plurality of euiccs 116.eUICC can be adhered to MSA 100 and is not removable. As is generally known, an eUICC can be used to store and utilize multiple SIM profiles (i.e., eSIM profiles). For example, the eUICC 116a can be used to store eSIM profiles 111a-b, the eUICC 116b can be used to store eSIM profiles 111c-d, and the eUICC 116c can be used to store eSIM profile 111e.
The eSIM profile contains all necessary information for dialing into the cellular network to enable the corresponding device to obtain telecommunication services from an MNO of the cellular network. For example, each eSIM profile may contain information such as a unique International Mobile Subscriber Identity (IMSI) Number that authenticates a Subscriber to the cellular network, an Integrated Circuit Card Identifier (ICCID), a Mobile Station International Subscriber Directory Number (MSISDN), cellular network specific data, and security authentication information. The eSIM profile can be used to perform the same functions as a removable SIM or SIM card. The eSIM profile may also be referred to as an electronic SIM.
MSA 100 may further include one or more SIM interfaces. The SIM interface is connectable to a removable SIM. For purposes of illustration, one exemplary SIM interface is SIM interface 117, and one exemplary removable SIM is removable SIM 112. The removable SIM may be a Universal Integrated Circuit Card (UICC). The SIM interface 117 may connect to a SIM slot for placing or receiving a removable SIM.
Optionally, MSA 100 can also include at least one WCM, such as WCM 106. In some exemplary embodiments, when the MSA is used to download an eSIM configuration file according to the method in fig. 3 (discussed later), the MSA should include the WCM. However, in some exemplary embodiments, the MSA may not need to include the WCM when using the MSA to download an eSIM profile according to the methods in fig. 7, 8a, or 8b (discussed later). The WCM 106 may be configured to access the cellular network using either the eSIM profile or the removable SIM at a time. However, to reduce design complexity, it is preferable that the WCM 106 use one or more dedicated removable SIM or eSIM profiles. The WCM 106 may be a Profile Download (PD) capable WCM. A profile download capable WCM is one that is capable of downloading eSIM profiles.
In some exemplary scenarios, MSA may include a plurality of WCMs, where at least one WCM of the plurality of WCMs is a WCM with profile download capability and other WCMs may be WCMs without profile download capability. WCMs without profile download capability are WCMs that are not capable of downloading eSIM profiles. The WCM (e.g., WCM 106) may be connected to an embedded/external antenna to perform transmission and reception of radio signals through the antenna. In one variation, WCM 106 is removable, so it is attached to MSA 100 in a manner that can be flexibly removed and reattached.
A processing unit (e.g., processing unit 101) of MSA 100 can be connected to SIM interface 117, eUICC 116, WCM 106, and other hardware components, such as network interfaces 103a and 103b using a system bus (e.g., system bus 115). However, in some exemplary scenarios, when the processing unit 101 has sufficient pins, the processing unit 101 may be directly connected to some of the peripheral hardware components, such as one or more of a SIM interface, eUICC, WCM, and/or a memory unit; therefore, the system bus may not be used. The processing unit 101 may be directly connected to the main memory unit 110 and the system bus 115. Processing unit 101 may execute program instructions or code segments stored in main memory unit 110 for implementing exemplary embodiments of the present invention.
MSA 100 may also optionally include a camera module, such as camera module 114. According to some example embodiments, when the MSA is used to read a machine-readable code using a code-reading application stored in a storage unit of the MSA, the camera module may be used to scan the machine-readable code. The MSA can be used to read machine-readable code to activate eSIM profile download. There is no limitation on the hardware components of the processing unit that may be connected to MSA 100.
Fig. 1B is a schematic block diagram illustrating hardware blocks of an exemplary network device, such as network device 150, in accordance with some exemplary embodiments of the present invention. Network device 150 may include at least one SIM interface (e.g., SIM interface 157) capable of connecting at least one removable SIM, such as removable SIM 152. Optionally, the network apparatus 150 can also include at least one eUICC (e.g., eUICC 156) that can store multiple eSIM profiles, such as eSIM profiles 151a and 151b.
The network device 150 may also include a plurality of WCMs, such as WCM 161. The WCMs 161 may contain at least one WCM with configuration file download capability (e.g., WCM 161 a) and the remaining WCMs may be WCMs without configuration file download capability (e.g., WCMs 161b and 161 c). WCMs without profile download capability may be used to establish a cellular network connection using a removable SIM or eSIM profile.
One of the goals of using non-profile-downloading capable WCMs in a network device is to reduce the number of profile-downloading capable WCMs to reduce the manufacturing cost of profile-downloading capable WCMs, as non-profile-downloading capable WCMs are relatively less expensive than profile-downloading capable WCMs. The reduction in manufacturing costs of such network devices may also result in a reduction in the cost of implementing M2M network infrastructure using such network devices. Another benefit of using WCMs without profile download capability may be that hardware change requirements of legacy network infrastructure may be reduced when updating these network infrastructures to use the latest technologies (e.g., eSIM technologies), since in legacy network infrastructure, the most used network devices include WCMs without profile download capability.
As shown in fig. 1B, network device 150 may include a processing unit (e.g., processing unit 155) to execute program instructions or code segments stored in a memory unit (e.g., memory unit 160) or a storage unit (e.g., storage unit 153). For purposes of illustration, memory unit 160 is connected directly to processing unit 155. The memory unit 160 may also be connected to the processing unit 155 by a system bus, such as the system bus 154. The system bus 154 may also be used to connect the processing unit 155 with other peripheral hardware components, such as the WCMs 161a, 161b, and 161c, the network interfaces 158a and 158b, the storage unit 153, the eUICC 156, and the SIM interface 157. Optionally, the processing unit 155 may also be connected to a camera module (such as a camera 159), which may be used to scan the machine readable code. In a variant, the above-mentioned peripheral hardware components may also be connected directly to the processing unit 155, when the processing unit 155 has enough pins to connect these components, and therefore a system bus may not be used.
Fig. 1C illustrates an exemplary network connection established between MSA 100 and network device 150 according to some exemplary embodiments of the present invention. For example, MSA 100 and network device 150 can be connected by network connection 132 or 134 established by an interconnection network (e.g., interconnection network 138). The interconnection network 138 may represent a public interconnection network (such as the Internet), a private interconnection network, or a mixture of public and private interconnection networks. In some exemplary embodiments, the terms "interconnection network" and "internet" may be used interchangeably. For example, using TCP/UDP protocols, IP networks can be used over wired and/or wireless networks to establish network connections 132 and 134, which enables MSA 100 and network device 150 to connect over interconnection network 138. In one variation, network connections 132 and 134 may be aggregated together to form an aggregated connection, such as aggregated connection 136. There is no limit to the number of network connections that may be used in the aggregated connection. Further, there is no limit to the number of network connections that can be established between MSA 100 and network device 150. Nor are there any restrictions on the location of MSA 100 and network device 150. MSA 100 and network device 150 may be located in different geographic regions.
As shown in fig. 1A, MSA 100 can optionally include a WCM (e.g., WCM 106), and as shown in fig. 1B, network device 150 can include a plurality of WCMs (e.g., WCM 161). The plurality of WCMs 161 may include a plurality of WCMs without configuration file download capability (e.g., WCMs 161b and 161 c) and at least one WCM with configuration file download capability, e.g., WCM 161a. In one scenario, when MSA 100 does not include a WCM or in another scenario includes a WCM, the eSIM profile still cannot be downloaded from the geographic area being accessed by network device 150, and the profile-downloading capable WCM from network device 150 can be used.
Fig. 7, 8a, and 8b illustrate a more detailed disclosure of how an eSIM profile for a local cellular network from a visited geographic area of a network device may be downloaded in an MSA using the network device, according to some example embodiments. One of the goals of downloading the eSIM profile (in the MSA) from the local cellular network of the visited geographic area of the network device may be for the network device to use the eSIM profile to establish a cellular network connection and thereby enjoy local charges of the visited geographic area.
FIG. 1D is a schematic block diagram of an exemplary MSA management server, such as MSA management server 216. MSA management server 216 includes at least one processing unit 181 and at least one main memory unit 185. The processing unit 181 may be directly connected to the memory unit 185. MSA management server 216 may further include at least one secondary storage unit 182 and a plurality of network interfaces 183a and 183b. The secondary storage unit 182 and the network interfaces 183a and 183b may be coupled to the processing unit 181 directly or via a system bus (e.g., system bus 186).
Optionally, processing unit 181 of MSA management server 216 can also be connected with other internal or external hardware devices not shown in fig. 1D to avoid obscuring the description. Other internal or external hardware devices may include one or more input devices, one or more output devices, a camera module, one or more SIM interfaces, and/or one or more sensors, such as thermal sensors, position sensors, touch sensors, and/or motion sensors.
Fig. 2A is a schematic block diagram illustrating an exemplary network environment operable to communicate data with multiple SIMs in accordance with exemplary embodiments disclosed herein. The plurality of SIMs may include removable SIMs or electronic SIMs. An electronic SIM is an eSIM profile stored in one or more euiccs placed in one or more MSAs. For example, one or more MSAs are MSAs 212a and 212b.
There are three cellular networks, namely cellular networks 201a-201c as shown. Each cellular network may provide communication coverage for a corresponding geographic area using cellular technology. The cellular networks 201a-201c may be operated by the same or different MNOs. For example, cellular networks 201a-201C may be operated by MNOs A, B, and C, respectively.
Network device 200 may be similar to or the same as network device 150 shown in fig. 1B. Network device 200 is capable of communicating with web server 208, network node 210, MSA 212, and MSA management server 216 over internetwork 217. The interconnection network 217 may be similar or identical to the interconnection network 138. Network device 200 may connect with interconnection network 217 through one or more cellular network connections established by cellular networks 201a-201c. One or more cellular network connections can be established using any eSIM profile from MSA 212 or using a removable SIM placed in network device 200. When using an eSIM profile to establish a cellular network connection over a cellular network, the eSIM profile should be from the same MNO that operates the cellular network. For example, when establishing a cellular network connection over the cellular network 201a using an eSIM profile, the eSIM profile used should be from MNO a.
Optionally, fig. 2A also includes a satellite carrier network, such as satellite carrier network 205. The satellite carrier network 205 may include one or more of geostationary satellites or low earth orbit satellites. For example, network device 200 may be within the respective coverage area of satellite-borne network 205 and may be connected to interconnection network 217 through one or more satellite data connections established by satellite-borne network 205.
Optionally, the network device 200 can also be connected to one or more wired communication networks. An exemplary wired communication network may comprise at least one network node 209. Network device 200 may connect to interconnection network 217 through one or more wired data connections established using one or more network nodes, including network node 209.
Network device 200 may be connected to one or more hosts through a direct physical connection or through a connected Local Area Network (LAN). For illustration purposes, the network device 200 is connected directly to the host laptop 206 and through the LAN 202 to the host IoT 204. Hosts 204 and 206 may be connected through network device 200 to an interconnection network 217 or to a host or server reachable through interconnection network 217. Thus, network device 200 acts as a gateway between hosts (206, 204) and an interconnection network (217) to allow data packets to be routed over one or more cellular network connections established over cellular networks 201a-201c.
Fig. 2B is a schematic block diagram illustrating a more detailed view of an exemplary cellular network operated by an MNO. For example, the exemplary cellular network is cellular network 201a operated by MNO a. For illustration purposes, the cellular network 201a may include a core network 230, a base station 229, a service support system (BBS) 224, a Web portal 226, and an eSIM subscription management server (e.g., SM-DP +) 222. In some embodiments, the eSIM subscription management server may also be referred to as a profile setup server. The eSIM subscription management server can be controlled by an MNO, a manufacturer of the eUICC, or a third-party wireless communication service provider.
Core network 230 may be connected to BSS 224, web portal 226, base station 229, and SM-DP + server 222 through a WAN or LAN connection established by a WAN or LAN interface. The network device 200 may access the core network 230 through the internetwork 217 or the base station 229.
Interconnected network 217 may also be used by MSA management server 216, cellular network 201a, network device 200, and MSAs 212a-b for data communications over a Wide Area Network (WAN) connection. Network device 200 may be in data communication with interconnection network 217 or with a host accessible through interconnection network 217 via one or more wired or wireless network connections. The wireless network connection may be established using Wi-Fi, wiMax, bluetooth, or a cellular network. In some example environments, a user of network device 200 may prefer the network device to connect with the interconnection network 217 through a cellular network due to the ubiquitous availability, wide coverage, flexibility of use, etc., of network device 200. For example, the cellular network may be cellular network 201a. In order to connect with the interconnection network 217 through the cellular network 201a, the network apparatus 200 may need to access the core network 230 of the cellular network 201a. When the network apparatus 200 has at least one eSIM profile or removable SIM of an available MNO a, the network apparatus 200 may access the core network 230 through a base station 229 of the cellular network 201a. The at least one eSIM profile can be stored in at least one eUICC disposed in at least one MSA that is locally or remotely accessible by the network apparatus 200. The removable SIM may be placed in a SIM slot that is connected to the processing unit of network device 200 through a SIM interface.
However, when the network apparatus 200 does not have at least one eSIM profile or removable SIM of an available MNO a, the network apparatus 200 can send a request for the eSIM profile to the cellular network 201a. In this exemplary scenario, the network apparatus 200 may connect to the core network 230 of the cellular network 201a through the interconnection network 217 to send the request. Continuing with the exemplary scenario, network device 200 may be connected to the interconnection network 217 through a wired or wireless network connection. The wireless network connection may be established using Wi-Fi (RTM), bluetooth (RTM), or a different cellular network for which network device 200 has at least one eSIM profile or removable SIM available. For example, a request for an MNO's eSIM profile may be sent through a web portal 226 provided by the MNO a to its potential customers or subscribers. In one variant, the request may be sent using an application provided by the MNO a. The application may be for downloading by the MNO A in the web portal 226 or may be built-in by the eUICC or the manufacturer of the network apparatus 200. Upon receiving the eSIM profile in response to the request, the network device 200 can access the core network 230 through the base station 229 using the eSIM profile information. Thus, the network device 200 is capable of connecting to the interconnection network 217 through the cellular network 201a or to a host reachable through the interconnection network 217. The invention disclosed herein may be advantageous for reducing data communication costs and increasing flexibility in establishing data connections using cellular networks in visited geographic areas.
Fig. 3 is a process flow diagram illustrating a method for downloading at least one eSIM profile to an MSA comprising a plurality of euiccs, according to an example embodiment. The process disclosed in fig. 3 may be performed by a processing unit of the MSA. MSA may comprise at least one WCM with configuration file download capability connected to the processing unit of MSA either directly or through a system bus. For purposes of illustration, one exemplary MSA is MSA 100, and processing unit 101 is a processing unit of MSA 100, as shown in fig. 1A. In one variation, the process disclosed in figure 3 is performed by a processing unit of a network device when the network device includes at least one eUICC.
In process 301, MSA 100 receives a network address of a web portal of an MNO, such as MNO A's web portal 226. The network address of the web portal may be retrieved from machine-readable code or from an over-the-air (OTA) message sent by MNO a. The machine-readable code may be received by a mail from the MNO A or collected by an administrator or user of the MSA from the MNO A's offline point of sale. The machine-readable code may be in the form of a Quick Response (QR) code, aztec code, maxiCode, or in any other form of machine-readable code. Processing unit 101 of MSA 100 can retrieve the machine-readable code using a code reader application capable of reading the machine-readable code described above.
In one variation, MSA 100 may not receive the machine-readable code directly from MNO A. The machine-readable code may first be received at an external device connected to MSA 100. The external device may have a code reader application for decoding and a camera module for scanning the machine-readable code. The decoded data of the machine-readable code may then be received by MSA 100 from an external device via Near Field Communication (NFC) technology, LAN, WAN, or console connection.
In process 302, MSA 100 accesses web portal 226 using a website address from the machine-readable code and requests an eSIM configuration file. In response to the eSIM profile request, MSA 100 may receive a user information request and subscription plan options provided by MNO a in process 303. The information required as user information may vary based on the MNO. For example, some common information required by MNOs includes the primary location of use, name, contact details, social security number, date of birth, billing information, and the like. The subscription plan provided may be shown on a web portal. For example, some subscription plans may be used for only voice communications, some subscription plans may be used for only data communications, and some subscription plans may be used for both voice and data communications. There is no limit to the number of subscription plans shown in the options; it is completely MNO dependent. Each subscription plan may have a different pricing level. In one variation, the MNO a may also need the eUICC ID in process 303. The eUICC ID is an eUICC ID identification code and is used to uniquely identify the eUICC.
In process 304, MSA 100 sends the user information and subscription plan selection. MSA 100 may also send the eUICC ID of an eUICC selected from a plurality of euiccs when MNO a requires the eUICC ID. MSA 100 may receive user information from a user or administrator through an input unit connected to MSA 100. In a variant, user information may already be stored in a memory unit of MSA 100, and after process 303, MSA 100 may retrieve and send the user information to MNO a in process 304.
In process 305, when the provided subscriber information is verified by MNO a, MSA 100 may receive an instruction to download an eSIM profile corresponding to the specified subscription plan. On the other hand, when the user information fails to be authenticated by the MNO a, a notification of authentication failure may be received. In that case, MSA 100 may notify a user or administrator of the authentication failure and wait for further instructions from the user or administrator. In one variation, MSA 100 can stop the method described in FIG. 3 or run in standby mode after notifying a user or administrator of the validation failure.
However, for purposes of illustration, in this exemplary scenario, it is assumed that the user information provided by MSA 100 is verified by MNO a and an instruction to download an eSIM profile is received. Thus, in process 306, MSA 100 can download and install eSIM profiles onto the eUICC, which the eSIM profiles are assigned, according to instructions provided by MNO a. Based on its eUICC ID, an eSIM profile can be assigned to the eUICC. When MSA 100 accesses web portal 226, MNO A can detect the eUICC ID. In one variation, the eUICC ID can be sent with the user information as disclosed in process 304. When the eUICC ID of the selected eUICC is sent in process 304, the received eSIM profile will be installed on the selected eUICC. In another variation, the eUICC ID of the selected eUICC can be sent with the eSIM profile request in process 302. Once the eSIM profile is successfully downloaded and installed onto the selected eUICC, the eSIM profile can be used to establish a cellular network connection over the MNO a's cellular network 201a.
Fig. 4 is a process flow diagram illustrating a method for decoding a machine-readable code at an external device and sending the decoded data to an MSA or a network device. For purposes of illustration, decoded data is sent to an MSA (such as MSA 100). The flows shown herein may be stored as program instructions in a memory unit and executed by a processing unit connected to the memory unit. The memory unit and the processing unit may be placed in an external device. The external device may further include at least one camera module to scan the machine-readable code. The external device may be a computer, a laptop computer, a tablet computer, a Personal Digital Assistant (PDA), or a smartphone. The machine-readable code may be initially provided by the MNO by mail, in a voucher, or using any other applicable means.
In process 401, a machine-readable code is scanned using at least one camera module placed in an external device. The machine-readable code may be displayed on a printed medium such as paper, sticker, or voucher. Alternatively, the machine readable code may be displayed on an electronic display unit.
In process 402, the machine readable code is decoded using a code reading application to retrieve encoded data. The code reading application may be stored in a memory unit of the external device.
At process 403, a connection is established between an external device and MSA 100. The connection may be established using NFC, LAN, WAN or console lines. It is not limited that process 403 should be performed after process 402. Process 403 may also be performed before process 401 or 402.
At process 404, decoded data of the machine-readable code is sent to MSA 100. When an external device is connected to MSA 100 over a WAN connection, the decoded data should be encapsulated in one or more encapsulating IP packets before sending the decoded data to MSA 100. When decoded data is encapsulated in one or more encapsulating IP packets, MSA 100 may need to decapsulate the one or more encapsulating packets before retrieving the decoded data from the machine-readable code. MSA 100 can then use the decoded data to activate an eSIM profile download as discussed in fig. 3. There is no restriction that the decoded data can only be sent to the MSA. In one variation, the decoded data may also be sent to a network device, such as network device 150.
Fig. 5 is a process flow diagram illustrating a method for obtaining a threshold number of eSIM profiles to be stored corresponding to an MNO. For purposes of illustration, eSIM profiles are stored in one or more euiccs placed in an MSA (e.g., MSA 100). The method begins at process 501 when an eSIM profile is received at MSA 100. In process 502, MSA 100 identifies an MNO for the received eSIM profile. The MNO may be identified using its MNO ID. The MNO ID may be a Public Land Mobile Network (PLMN) ID consisting of a Mobile Country Code (MCC) and a Mobile Network Code (MNC). For illustration purposes, an eSIM profile is received from MNO a.
In process 503, processing unit 101 of MSA 100 determines the total number of eSIM profiles for MNO a stored in MSA 100. The total number of eSIM profiles for an MNO is equal to the sum of the eSIM profiles for an MNO stored in one or more euiccs placed in MSA 100 and the received eSIM profile. It should be noted that one or more euiccs can store eSIM profiles from different MNOs (e.g., from MNO B or MNO C) that will not be counted when counting the total number of eSIM profiles for MNO a. Processing unit 101 of MSA 100 can determine from the eSIM profile lookup table the number of eSIM profiles for MNO a stored in one or more euiccs placed in MSA 100. According to an exemplary embodiment of the invention, the eSIM profile lookup table includes all or part of the information for all eSIM profiles stored in one or more euiccs placed in MSA 100. The eSIM configuration file look-up table can be stored in a storage unit disposed in or connected to MSA 100.
In process 504, MSA 100 compares the total number of stored eSIM profiles for MNO a to a threshold number of eSIM profiles to be stored corresponding to the MNO. The threshold number of eSIM profiles to be stored corresponding to an MNO can be set manually by a user or administrator of MSA 100 or by default by the manufacturer of the MSA. The threshold number of eSIM profiles to be stored corresponding to MNOs should be lower than or equal to the number of euiccs placed in MSA 100.
In process 505, MSA 100 determines whether a threshold number of eSIM profiles to be stored corresponding to MNOs has been reached. The threshold is reached when the total number of stored eSIM profiles for the MNO a is equal to a threshold number of eSIM profiles to be stored corresponding to the MNO. For example, the threshold number of eSIM profiles to be stored corresponding to an MNO is five, and the total number of stored eSIM profiles for MNO a is three; therefore, the threshold value is not reached.
When the threshold is not reached, processing unit 101 of MSA 100 follows the "No" branch as shown in FIG. 5 and performs process 506. In process 506, an eUICC that does not already store an eSIM profile for an MNO a is selected from among one or more euiccs placed in MSA 100, and a request is sent to the MNO a to obtain the eSIM profile of the selected eUICC. The request for the eSIM profile can include an eUICC ID and user information of the selected eUICC. The operations of requesting and downloading the eSIM profile may be performed according to the exemplary method discussed in fig. 3 or according to the exemplary method of fig. 7 or 8 (discussed later). After performing process 506, processes 501-505 are repeated. Continuing the example, after repeating processes 501-505 once, the total number of stored eSIM profiles for MNO a becomes 4. When per example, the threshold number of eSIM profiles to be stored corresponding to an MNO is five; thus, the threshold has not been reached. Thus, process 506 is performed again. The process 506 is iterated until a threshold is reached, and at each iteration, an eUICC is selected that does not already store the eSIM profile for MNO a.
According to an example, the threshold is reached when the total number of stored eSIM profiles for MNO a becomes five. When a threshold number of eSIM profiles to be stored corresponding to MNOs is reached, the method ends. One of the benefits of storing a threshold number of eSIM profiles corresponding to an MNO may be to be able to establish a desired number of cellular network connections over the MNO's cellular network and thereby increase the speed of data communications. For purposes of illustration, when MSA 100 stores five eSIM profiles for MNO a in five euiccs, at least five cellular network connections can be simultaneously established using the five eSIM profiles simultaneously by one or more network devices.
Fig. 6A is a process flow diagram illustrating a method for establishing at least one cellular network connection at a network device in accordance with an exemplary embodiment of the present invention. For example, at least one cellular network connection will be established at network device 150.
In process 601, the processing unit 155 of the network device 150 identifies at least one cellular network available in its current geographic area. At least one cellular network may be identified by performing a scan by the network device 150 using the available WCMs. The WCM may be placed in the network device 150 or externally connected. The WCM may include an antenna for transmitting and receiving radio signals. The antenna may also be externally connected to the WCM. Without limiting the scope of the present invention, the network device 150 may be fixed for use within a particular geographic area or may be mobile and thus may be used in different geographic areas depending on the use case. Network device 150 may be located in a home geographic area or a visited geographic area.
In process 602, processing unit 155 of network device 150 sends cellular network identity information of the identified at least one cellular network to an MSA (e.g., MSA 100) and requests at least one eSIM profile of the identified at least one cellular network. Cellular network identity information can include an MNO ID (PLMN ID) of the identified at least one cellular network and/or other associated information that can be used by MSA 100 to identify an eSIM profile corresponding to the identified at least one cellular network. In one variation, in some exemplary scenarios, the MNO's cellular network may also be used by one or more Mobile Virtual Network Operators (MVNOs) to provide communication services. In such cases, the cellular network identity information may also include the identity of one or more MVNOs, and the request for at least one eSIM profile may correspond to the eSIM profile of the at least one MNO and/or MVNO of the identified at least one cellular website. However, for purposes of explanation in this disclosure, it is assumed that the cellular network corresponds to one MNO. The network device 150 can transmit the cellular network identity information and the request for the at least one eSIM profile over the internet. In one variation, the cellular network identity information and the request for the at least one eSIM profile may be sent via a Short Message Service (SMS) message.
In process 603, processing unit 101 of MSA 100 reads the eSIM profile lookup table to determine whether at least one eSIM profile corresponding to the identified at least one cellular network is available. The processing unit 101 can use the cellular network identity information to identify at least one eSIM profile that belongs to the identified at least one cellular network. The eSIM configuration file look-up table can be stored in a memory location that is placed in MSA 100 or externally connected to MSA 100. The storage unit is, for example, the storage device 105 shown in fig. 1A. The eSIM profile lookup table includes a list of all eSIM profiles stored in one or more euiccs placed in MSA 100. It is not a limitation that eUICC should be placed in the MSA. eUICC can be placed in an external device or another MSA connected to MSA 100.
In process 604, MSA 100 sends all or part of the information from the at least one eSIM profile of the at least one eSIM profile available to network device 150 when the at least one eSIM profile of the identified at least one cellular network is found to be available. All or part of the information may include subscriber identity information including IMSI, location Area Identity (LAI), user identity, and other associated information that may be needed by the MNO to identify the subscriber or user. In process 605, upon receiving all or part of the information of the at least one eSIM profile from MSA 100, network device 150 sends a request for data communication access to the at least one corresponding MNO that received the information of the at least one eSIM profile. The request is sent using all or a portion of the information received in process 604. The request may be sent via the internet. Thereafter, the at least one corresponding MNO receiving the information of the at least one eSIM profile can request authentication information from the network apparatus 150 in process 606.
However, when an eSIM profile in undiscovered process 603 is available, MSA 100 sends a negative response to network device 150 in process 604 instead of sending eSIM profile information. Upon receiving a negative response from MSA 100, network device 150 can notify the user or administrator that the eSIM profile was not discovered and end the method. The notification may be displayed on a display connected to the network device 150. Techniques for notifying a user or administrator are not limited; any manner of notification may be used. In another variation, upon receiving a negative response from MSA 100, processing unit 155 of network device 150 initiates operations to download at least one eSIM profile of the identified at least one cellular network.
In process 607, processing unit 155 of network device 150 forwards an authentication request sent by at least one corresponding MNO of the at least one eSIM profile to MSA 100. In process 608, processing unit 101 of MSA 100 retrieves authentication information responsive to the authentication request from a corresponding eSIM profile stored in an eUICC connected to, or placed in, MSA 100. For illustration, eSIM profiles can be stored in any of the euiccs 116.
In process 609, processing unit 101 of MSA 100 sends the retrieved authentication information to network device 150. In process 610, processing unit 155 of network device 150 forwards the authentication information received from MSA 100 to at least one corresponding MNO of at least one eSIM profile. In process 611, the MNO may provide access to network device 150 for data communications based on the validity of the authentication information sent by network device 150.
Fig. 6B is a process flow diagram illustrating a method for establishing one or more cellular network connections at a network device in accordance with an exemplary embodiment of the present invention. The process described in fig. 6B may be performed in the MSA, in the MSA management server, in a network device and/or in a device of an MNO by a corresponding processing unit. When using an MSA management server, the MSA management server can connect to one or more MSAs housing one or more euiccs, where the one or more MSAs can be remotely managed by the MSA management server. For purposes of illustration, exemplary network device may be network device 150, exemplary MSA may be MSA 100, and exemplary MSA management server may be MSA management server 216.
In process 621, the processing unit 155 of the network device 150 identifies one or more cellular networks that are available. One or more cellular networks may be identified in the same manner as disclosed in step 601 of fig. 6A. In process 622, the processing unit 155 of the network device 150 generates a first list of cellular networks based on the cellular networks identified in process 621. The number of cellular networks identified in process 621 and the number of cellular networks in the first list of cellular networks may be the same or different. In one variation, the first list of cellular networks may include the identities of all cellular networks identified in process 621.
In another variation, some of the identified cellular networks may be filtered out by examining a signal strength level threshold. Thus, the first list of cellular networks will only include cellular networks that meet the signal strength level threshold. The value of the signal strength level threshold may be set manually by an administrator, built into firmware by the manufacturer, or downloaded remotely from a remote server.
In process 623, the processing unit 155 of the network device 150 sends a first list of cellular networks to the MSA or MSA management server and requests to query whether any eSIM profiles for the cellular networks in the first list are available. For purposes of illustration, processing unit 155 of network device 150 sends a first list of cellular networks and requires a query for MSA 100.
In process 624, processing unit 101 of MSA 100 reads the eSIM profile lookup table to identify eSIM profiles corresponding to cellular networks in the first list of cellular networks. Alternatively, when using an MSA management server, the processing unit of the MSA management server will look for the corresponding eSIM profile of the cellular network in the first list of cellular networks in all connected MSAs.
Three possible outcomes of process 624 are possible. First, one or more eSIM profiles available to all cellular networks can be found in a first list of cellular networks. Second, when the first list of cellular networks includes a plurality of cellular networks, the one or more eSIM profiles can be deemed available only to some of the cellular networks in the first list of cellular networks. And third, no eSIM profile available to any of the cellular networks is found in the first list of cellular networks. Based on the result, processing unit 101 of MSA 100 sends a response to network device 150. For example, for the first result and the second result, processing unit 101 of MSA 100 or a processing unit of MSA management server generates a second list of cellular networks in a next process (process 625), wherein the second list of cellular networks includes cellular networks for which at least one corresponding eSIM profile is deemed available. However, for a third result, when no eSIM profile is found to be available, processing unit 101 of MSA 100 or a processing unit of the MSA management server sends a negative response to network node 150 to notify of the unavailability of the eSIM profile and stop the method. When a negative response is received, the same functions may be performed as discussed in fig. 6A.
In process 626, processing unit 101 of MSA 100 or a processing unit of MSA management server sends a second list of cellular networks to network device 150. In process 627, after receiving the second list of cellular networks, the processing unit 155 of the network device 150 selects a cellular network from the second list of cellular networks based on at least one condition. There is no limitation to selecting only one cellular network, and in one variation, multiple cellular networks may be selected. However, in some exemplary scenarios, the second list of cellular networks may contain only one cellular network. In such cases, the cellular networks in the second list of cellular web sites are selected without imposing any conditions.
The at least one condition may be based on signal strength. When the second list of cellular networks contains a plurality of cellular networks, the cellular network with the highest signal strength is selected. The signal strength of the cellular network may be detected by the network device.
The at least one condition for selecting a cellular network may also be based on one or more of the following criteria: tariff cost of an MNO of a cellular network, network performance, network type, administrator preference, and/or quality of service.
When selecting a cellular network based on quality of service, the cellular network that provides the MNO of better quality will be selected. The quality of service of an MNO may be evaluated based on different criteria including, but not limited to, configured network coverage, security, and simplicity.
When a cellular network is selected based on administrator preferences, an administrator of network device 150, MSA 100, or MSA management server 216 may assign a priority to each cellular network detected. When the priority is assigned, the cellular network with the higher priority will be selected. The administrator may assign priority levels to the cellular network based on the criteria described above or based on no criteria whatsoever.
In process 628, network device 150 requests data communication access to the selected at least one cellular network. In process 629, in response to a request for data communication access, a corresponding MNO of at least one cellular network may request subscriber identity information from network device 150. In process 630, network device 150 forwards the subscriber identity information request to MSA 100. In one variant, in process 630, processing unit 155 of network device 150 forwards the subscriber identity information request to MSA management server, which in such a scenario further forwards the subscriber identity information request to MSA 100. In process 631, after receiving the subscriber identity information request, processing unit 101 of MSA 100 retrieves subscriber identity information from at least one eUICC storing at least one eSIM profile of the selected at least one cellular website in response to the subscriber identity information request.
In process 632, processing unit 101 of MSA 100 sends the retrieved subscriber identity information to network device 150. In one variation, in process 632, when MSA 100 receives a subscriber identity information request through MSA management server, MSA 100 sends the retrieved subscriber identity information to MSA management server. MSA service manager then forwards the retrieved subscriber identity information to network device 100. After that, network device 150 forwards the subscriber identity information to the MNO of the selected at least one cellular network in process 633. After receiving the subscriber identity information, the corresponding MNO of the selected at least one cellular network may determine validity of the subscriber identity information. When the subscriber information is valid, steps 634-639 are performed similarly to steps 606-611 as described in FIG. 6A. After successful completion of steps 634-639, data communication is obtained through the selected at least one cellular network.
However, when the subscriber identity information is invalid, a validity error notification may be received at the network apparatus 150 from the corresponding MNO of the selected at least one cellular network, and data communication access may be denied. The processing unit of network device 150 may notify the administrator of the validity error and wait for further instructions or enter a standby mode. In standby mode, all processes of network device 150 may be suspended until the next instruction is received from the administrator, and thus unnecessary waste of resources may be reduced when there is a significant delay before any further instructions are received. In one variation, some processes may still run in a standby mode that is customized in this manner by an administrator or set by the manufacturer as a default.
Fig. 7 is a process flow diagram illustrating a method for downloading at least one eSIM configuration file in an MSA according to an exemplary embodiment of the present invention. At process 701, the method illustrated in fig. 7 starts when a negative response is received at a network device (e.g., at network device 150). As discussed in fig. 6A and 6B, when in response to an eSIM profile request sent by network device 150, MSA 100 does not find an eSIM profile in the eSIM profile lookup table, a negative response is sent by MSA 100 to network device 150. It should be noted that MSA 100 and network device 150 should be connected over the internet prior to process 701. Connection to the internet may be accomplished by network device 150 using a roaming cellular network connection, wi-Fi, or any other device that enables network device 150 to access the internet.
In process 702, the processing unit 155 of the network device 150 sends a request for at least one eSIM profile to an MNO of at least one selected cellular network over the internet. Selecting at least one cellular network from the plurality of identified cellular networks is discussed in fig. 6B. In one variation, the request for the at least one eSIM profile is sent to a respective MNO of each of the identified cellular networks.
In one variation, the request for at least one eSIM profile sent in process 702 is generated by the processing unit 155 of the network device 150 based on one or more event triggers and is not driven by process 701. For purposes of illustration, events of an event trigger may include, but are not limited to, detection by network device 150 of a change in its current geographic area, receipt of a negative response from MSA 100, or first detection of a cellular network. When process 702 is based on an event trigger, processing unit 155 of network device 150 may monitor for the event and match the event trigger. When the event matches any of the event triggers, the processing unit 155 of the network device 150 provides the necessary instructions to the profile download capable WCM to perform process 702. For example, process 702 is set to be triggered by an event of "receive a negative response from MSA 100". Thus, in the event a negative response from MSA 100 is received at network device 150, processing unit 155 performs process 702.
In a variant, in order to save data storage space, all events of the events containing the event trigger may be represented by a unique code. When the code is applied to the event trigger, if the event occurs, the processing unit 155 analyzes the unique code of the event to determine whether the event matches the code of the event trigger. When the code of the event matches the code of the event trigger, the processing unit 155 performs a function that is set to be triggered with the event trigger. When the code of the event does not match the code of the event trigger, the function is not triggered.
In process 703, the MNO of the selected at least one cellular network may request at least one eUICC ID in response to the at least one eSIM profile. In another variation, the MNO may also request other associated information that may be needed to provide an eSIM profile for the network device 150. When multiple eSIM profiles are requested from a particular MNO, the MNO may require multiple eUICC IDs so that each eUICC can be used to store one eSIM profile for the MNO. The network device 150 can request multiple eSIM profiles from a particular MNO in order to establish multiple concurrent cellular network connections through the MNO's cellular network using the multiple eSIM profiles.
In process 704, network apparatus 150 forwards the request for at least one eUICC ID and other associated information received from the MNO of the selected cellular website to MSA 100. In one variation, the network device 150 may already have the eUICC ID and associated information stored in a storage location disposed therein. Thus, when the network device receives a request for at least one eUICC ID and other associated information from the MNO of the selected cellular website, the network device retrieves the at least one eUICC ID and associated information from the storage unit and replies to the request.
In process 705, processing unit 101 of MSA 100 selects at least one available eUICC placed in MSA 100 and retrieves at least one eUICC ID information from the selected at least one eUICC. In a variant, processing unit 101 also retrieves the associated information from a storage unit connected to MSA 100.
In process 706, processing unit 101 of MSA 100 sends the retrieved at least one eUICC ID information to network device 150. In one variant, MSA 100 also sends other associated information along with the retrieved eUICC ID information in process 706 when the corresponding MNO requests the associated information and when the associated information is stored in a storage unit connected to MSA 100.
In process 707, the processing unit 155 of the network device 150 forwards the received at least one eUICC ID information to the MNO of the selected cellular website. In one variation, when the corresponding MNO requests the associated information, the network apparatus 150 also forwards the other associated information along with at least one eUICC ID information. Associated information may be received from MSA 100, retrieved from a storage unit connected to network device 150, or collected from an input unit connected to network device 150. The MNO of the selected at least one cellular network receives the at least one eUICC ID information or the at least one eUICC ID and associated information provided by the network apparatus 150 and decides whether to provide the at least one eSIM profile based on the validity of the provided information. When it is decided to provide the at least one eSIM profile, the BSS of the MNO of the selected at least one cellular website may send a request to an eSIM subscription management server (SM-DP +) to prepare and provide the at least one eSIM profile to the network apparatus 150.
In process 708, the SM-DP + server of the MNO corresponding to the selected at least one cellular website securely provides the at least one eSIM profile to the network apparatus 150 for installation in the selected at least one eUICC. The network device 150 receives at least one eSIM configuration file through the profile download capable WCM. Processing unit 155 of network device 150 then forwards the at least one eSIM configuration file to MSA 100 in process 709. Upon receiving the at least one eSIM profile, processing unit 101 of MSA 100 installs the at least one eSIM profile onto the selected at least one eUICC. Upon successful completion of the method illustrated in fig. 7, the at least one eSIM profile can be used to establish the at least one cellular website connection through the selected at least one cellular network.
Fig. 8A is a process flow diagram illustrating exemplary communications between an MSA, an MSA management server, a network device, and an MNO when downloading an eSIM profile onto one or more euiccs placed in the MSA. For example, exemplary MSA is MSA 100 shown in fig. 1A, MSA management server is MSA management server 216 shown in fig. 1D, and network device is network device 150 shown in fig. 1B. And does not limit the number of MSAs and MNOs that may be involved. For illustration purposes, one MSA and one MNO are shown. MSA management server 216, MSA 100, network device 150, and MNO can be connected through an interconnection network (e.g., the internet) such as interconnection network 217 as shown in fig. 2A. When the eSIM profile is downloaded onto an eUICC placed in one or more MSAs and also when eSIM profile information from the one or more MSAs is provided to the network device, the MSA management server can be used to manage the one or more MSAs to establish at least one cellular website connection.
The method described in FIG. 8A is initiated at process 801 based on an event trigger. Events may include, but are not limited to: receiving an instruction to download an eSIM configuration file from an administrator or user of MSA management server 216; receiving a request to download an eSIM configuration file from a network device; not finding at least one eSIM profile when performing eSIM profile lookup in the eSIM profile lookup table; and detecting a change in location of the network device. To detect a change in the location of a network device, MSA management server 216 can periodically check the location of one or more network devices (e.g., network device 150) connected thereto.
In process 801, processing unit 181 of MSA management server 216 sends a request to network device 150 to download one or more eSIM profiles stored in one or more euiccs placed in MSA 100.
In process 802, upon receiving a request from MSA management server 216 to download one or more eSIM profiles, processing unit 155 of network device 150 instructs the available WCMs connected to processing unit 155 to scan for available cellular networks. The WCM may be placed in the network device 150 or externally connected to the network device 150. Based on instructions from the processing unit 155, the WCM scans for available cellular networks in the current geographic area of the network device 150. The process 802 may have different results. For example, (i) only one cellular network may be detected, (ii) multiple cellular networks may be detected, and (iii) no cellular networks are detected. However, in this age of technology development, there is a greater likelihood of detecting multiple cellular networks due to more than one mobile network operator being available in a geographic region.
As such, in process 803, when multiple cellular networks are detected, the processing unit 155 of the network device 150 selects at least one cellular network from the detected cellular networks based on at least one condition. The at least one condition upon which the at least one cellular network is selected may be determined from a set of conditions including, but not limited to, signal strength of an MNO of the cellular network, tariff cost, network performance, network type, administrator preference, and/or quality of service. Information about conditions can be collected by network device 150, sent by MSA administration server 216, sent by MSA 100, and/or received by an administrator or user from one or more inputs.
However, when only one cellular network is detected in process 802, process 803 may be omitted and the next process performed with the detected cellular network as the selected cellular network. When no cellular network is detected in process 802, network device 150 can send a message to MSA management server 216 that no cellular network is detected and the process is stopped. In another variation, network device 150 sends a message to MSA 100 that no cellular network is detected and the process is stopped. In another variation, when no cellular network is detected, the network device 150 continues to repeatedly scan for available cellular networks at intervals until at least one cellular network is detected. In another variation, when no cellular network is detected, the network device 150 may repeatedly scan for available cellular networks upon detecting a change in distance in the location of the network device.
In process 804, the processing unit 155 of the network device 150 sends a request for at least one eSIM profile to the MNO of the selected cellular network. The request may be sent over the internet using a WCM capable of downloading eSIM configuration files. There is no limitation on the means for accessing the internet through the network device 150. For purposes of illustration, the network device 150 may access the internet through a wired internet connection (e.g., a cable-connected internet connection, a fiber-optic internet connection, or a Digital Subscriber Line (DSL) internet connection) or through a wireless internet connection (e.g., a Wi-Fi (RTM), satellite connection, or cellular network connection). When the network device 150 accesses the internet through a cellular network connection, the connection may be a roaming connection or a home cellular network connection. When the event of failing to find an eSIM profile while searching for the eSIM profile in the eSIM profile lookup table triggers the method of fig. 8A, the network device 150 may not be able to access the internet over the native cellular network connection because this event occurs when the network device 150 does not have an eSIM profile available to access the native cellular network.
In another variation, step 803 may be omitted and in step 804, at least one eSIM profile request is sent to the MNOs of all detected cellular networks in step 802. The benefit of doing so may be to diversify eSIM profile reserves at one or more MSAs similar to MSA 100. Thus, when a different cellular network becomes preferred due to a change in conditions, it would not be necessary to download the eSIM profile for the most recently preferred cellular network, as the eSIM profile for that cellular network may have already been downloaded.
In process 805, the MNO of the selected cellular network can request at least one eUICC ID and other associated information that may be needed to provide the eSIM profile from the network device 150. In one variant, the request is for at least one eUICC ID only, and the associated information may not be needed or may be collected by the MNO by any method known in the art. At least one eUICC ID shall belong to at least one eUICC where at least one eSIM profile is to be stored. It should be noted that the number of eUICC IDs required depends on the number of eSIM profiles requested from the selected cellular network. For example, when the number of eSIM profiles requested is two, the number of eUICC IDs required for the selected cellular network should also be two. In another variation, if such facilities are supported by an MNO of the selected cellular network, multiple eSIM profiles for the selected cellular network may be stored in a single eUICC. In that case, the selected cellular network may only require one eUICC ID, even though the network device 150 requests multiple eSIM profiles. Other associated information that an MNO may need along with the eUICC ID may vary from MNO to MNO. For illustration, the desired associated information may include identity information of the user, home location information of the user, billing information of the user, and/or contact details of the user.
In process 806, network device 150 forwards the request for at least one eUICC ID and associated information to MSA management server 216. In process 807, MSA management server 216 can generate another request based on at least a portion of the request received from network device 150 and send the request to MSA 100. The request sent by MSA management server 216 may simply comprise a request for at least one eUICC, wherein other associated information needed by an MNO may be retrieved from a storage unit or collected from an input unit by a processing unit of MSA management server 216. Both storage unit and input unit may be connected locally or remotely to MSA management server 216. When the input unit is remotely connected to MSA management server 216, the input data can be provided using a web interface. When the associated information required by the MNO of the selected cellular network is collected from the input unit, the input of the associated information may be provided by an administrator or user of MSA management server 216.
In process 808, processing unit 101 of MSA 100 selects at least one available eUICC from the plurality of euiccs and retrieves eUICC ID information from the selected at least one eUICC. Multiple euiccs may be placed in MSA 100 or in an external device connected to MSA 100. Selecting at least one eUICC to store at least one eSIM profile to be downloaded from the selected at least one cellular website.
In process 809, processing unit 101 of MSA 100 sends eUICC ID information of the selected at least one eUICC to MSA management server 216. In process 810, MSA management server 216 sends a response to the request received from network device 150 in process 806. The response includes the eUICC ID information received from MSA 100 and other associated information retrieved from a storage unit or collected through an input unit. In another variation, MSA management server 216 forwards the eUICC ID information received from MSA 100 to network device 150 in step 810 when the associated information is not needed.
In process 811, the processing unit 155 of the network device 150 forwards the eUICC ID information and associated information to the MNO of the selected cellular network. Upon receiving the eUICC ID information and associated information, the MNO of the selected cellular network may perform an authentication procedure. In process 812, the MNO of the selected cellular network can provide the at least one eSIM profile to the network appliance 150 through an eSIM subscription management server (SM-DP +) when the information is deemed valid. It should be noted that prior to providing the at least one eSIM profile, a number of internal processes may be performed at the MNO to prepare the at least one eSIM profile, which is not elaborated in this disclosure to avoid obscuring the description. For example, eUICC ID information and other associated information can be received at a service support system (BSS) of an MNO through an online portal provided by the MNO or from a terminal responsible for collecting subscriber information. The MNO's BSS may then validate the received information in the validation server. When the discovery information is valid, the BBS can send a request to an eSIM subscription management server (SM-DP +) to prepare and provide at least one eSIM profile for the network device 150.
Alternatively, in M2M eSIM profile settings, the BBS may request a subscription management data preparation (SM-DP) server of the MNO to prepare at least one eSIM profile based on the information. After preparing the at least one eSIM profile, the SM-DP can send the at least one eSIM profile to a subscription management secure routing (SM-SR) server of the MNO to securely provide the at least one eSIM profile to the network device or the at least one eUICC.
However, when the discovery information is invalid, the MNO of the selected cellular network may notify the network apparatus 150 of the invalidity event. Network device 150 may notify the user of the invalidation event by displaying a message on a display screen or by sending an invalidation notification message to MSA management server 216. However, for illustration purposes, it is assumed that the discovered eUICC ID information and associated information are valid.
In process 813, network device 150 forwards the at least one eSIM profile information received from the MNO of the selected cellular network to MSA management server 216. After this, MSA management server 216 forwards at least one eSIM configuration file to MSA 100 in process 814. In another variation, network device 150 sends at least one eSIM profile directly to MSA 100 in step 813, and step 814 is omitted.
In process 815, at least one eSIM profile is installed on at least one eUICC corresponding to the eUICC ID. Upon successful completion of the method illustrated in fig. 8A, the at least one eSIM profile can be used by the network device 150 or other network device to establish a cellular network connection.
Fig. 8B is a process flow diagram illustrating a method for downloading one or more eSIM profiles in an MSA according to an exemplary embodiment of the invention. For purposes of illustration, the eSIM profile will be stored in at least one eUICC disposed in MSA 100 shown in fig. 1A. In process 821, a request to download at least one eSIM configuration file is received at MSA 100. The request is sent by an MSA management server, such as MSA management server 216 shown in fig. 1D. Prior to process 821, MSA 100 and MSA management server 216 should be connected through an interconnection network (e.g., interconnection network 217). And does not limit the number of MSAs that can be connected to MSA management server 216.
MSA management server 216 can send a request for eSIM profile download when one or more of the following events occur: receiving an instruction to download an eSIM configuration file from an administrator or user of MSA management server 216; receiving a request to download an eSIM configuration file from a network device connected to MSA management server 216; failing to find the at least one eSIM profile when searching the eSIM profile lookup table for the at least one eSIM profile; and detecting a change in location of the network device. To detect a change in the location of a network device, MSA management server 216 can periodically check the location of one or more network devices connected thereto. In one variation, MSA 100 receives a request to download an eSIM configuration file directly from a user or administrator, rather than through an MSA management server.
In process 822, processing unit 101 of MSA 100 selects an eUICC from MSA 100 and retrieves eUICC ID information of the selected e UICC. In process 823, MSA 100 sends a request for eSIM profile download to a network device, such as network device 150. In order to receive a request from MSA 100, network device 150 should connect with MSA 100 prior to process 823. Network device 150 can be connected to MSA 100 through interconnection network 217. The request sent in process 823 may include the retrieved eUICC ID information. In another variation, the request sent in procedure 823 may also include other associated information that the MNO may need to provide the eSIM profile. In that case, the associated information may be stored in a storage unit connected to MSA 100.
In another variant, the associated information is collected from the input unit when requested by the MNO. For example, the network device 150 may include an input unit to allow an administrator or user to communicate information and commands to the processing unit of the network device 150. The input unit may be a touch-sensitive screen or a keypad installed on the network apparatus 150. A user or administrator of network device 150 may input data to network device 150 through a touch sensitive screen or keypad. In a modification, the input unit may also be indirectly connected to the network device 150 through an external device connected to the network device 150. The external device may be a desktop computer, a laptop computer, a mobile phone, a smart phone, a Personal Digital Assistant (PDA), or any other electronic device capable of connecting to a network interface.
Upon receiving a request to download at least one eSIM profile, the network device 150 identifies available cellular networks in its current geographic area. The network device 150 may identify available cellular networks by scanning for radio signals using available WCMs placed in the network device 150. The WCM may be a WCM with or without profile download capability.
In process 825, the network device 150 sends a request for an eSIM profile to the MNO of the identified cellular network. When a cellular network is identified in process 824, a request is sent to the corresponding MNO of the identified cellular network in process 825. When multiple cellular networks are identified in process 824, a request is sent to the respective MNO of each of the multiple identified cellular networks. For purposes of illustration, in this exemplary embodiment, multiple cellular networks have been identified in process 824. Accordingly, in process 825, the request is sent to a respective MNO for each of the plurality of identified cellular networks. The request sent in process 825 may include eUICC ID information sent by MSA 100.
However, when a cellular network is not identified in process 824, network device 150 can notify MSA 100 that a cellular network is not available and stop the method of downloading the eSIM profile. In another variation, network device 150 can notify MSA management server 216 that the cellular network is unavailable and stop the method of downloading the eSIM configuration file. Upon receiving notification that the cellular network is unavailable, MSA 100 or MSA management server 216 can also stop the method of downloading the eSIM configuration file or wait for additional instructions from the user or administrator. In another variation, network device 150 may notify a user or administrator of network device 150 that the cellular network is unavailable and awaits further instructions or turns on a standby mode via a message on a display screen.
Upon receiving the eUICC ID information or the eUICC ID and associated information, the MNO of the identified cellular network may perform authentication. When the information is valid, the MNO of each of the identified cellular networks may provide the eSIM profile to the network device 150 through the eSIM subscription management server (SM-DP +) in process 826. It should be noted that several internal processes not detailed in this disclosure to avoid obscuring the description may be performed at the MNO to prepare the at least one eSIM profile before providing the at least one eSIM profile. When the discovery information is invalid, the MNO of the identified cellular network may notify the network apparatus 150 of the invalidity event. Network device 150 may notify a user or administrator of the invalidation event by displaying a message on a display screen or by sending an invalidation notification message to MSA management server 216. However, for illustration purposes, it is assumed that the discovered eUICC ID information and associated information are valid.
In process 827, network device 150 forwards eSIM profile information received from the MNO of the identified cellular network to MSA 100. In process 828, the eSIM profile is installed on the selected eUICC corresponding to the eUICC ID. Upon successful completion of the method illustrated in fig. 8B, the eSIM profile can be used by the network device 150 or other network device.
Fig. 9 illustrates an exemplary eSIM profile lookup table 900 in accordance with an exemplary embodiment of the present invention. It should be noted that the design and structure of the eSIM profile lookup table shown herein is for illustration purposes only. In actual implementations, the eSIM profile lookup table can be a combination of a set of tables, cells, or information fields. In one variation, the eSIM profile lookup table may be implemented using a relational or non-relational database structure, such as a Sequential Query Language (SQL) database structure or a NoSQL database structure. The eSIM profile lookup table can be stored in a memory unit connected to the MSA (e.g., MSA 100). For purposes of illustration, eSIM profile lookup table 900 can be stored in memory unit 105 of MSA 100 shown in fig. 1A.
eSIM profile lookup table can record information for all eSIM profiles stored in one or more euiccs placed in MSA 100 or connected to MSA 100. For illustration purposes, the eSIM profile lookup table 900 can record information corresponding to each eSIM profile, such as MNO ID, ICCID, and eUICC ID. The eSIM profile lookup table can also record a status field to show the current status of an eSIM profile, whether the eSIM profile is in use or available for use. The MNO ID is used to identify the MNO of the eSIM profile. The ICCID is used to identify eSIM profiles. The eUICC ID is used to identify the eUICC that stores the eSIM profile.
For illustration purposes, in fig. 9, MNO IDs, such as "001", "002", "003", represent three different MNOs, where ICCIDs, such as "aaa", "bbb", "ccc", "ppp", "qqqq", and "sss", represent six different eSIM profiles, and euicids, such as "111111", "222222", "333333", represent three different euiccs. It should be noted that the numbers and letters shown as MNO ID, ICCID, and eUICC ID are for exemplary purposes only, and in practical embodiments, the MNO ID may be 5-6 digits, the ICCID may be 19-22 digits, and the eUICC ID may be up to 32 digits.
According to an exemplary embodiment of the invention, when a request for at least one eSIM profile for at least one MNO is received at MSA 100 from a network device, MSA 100 reads eSIM profile lookup table 900 to determine whether the eSIM profile for the at least one MNO is available. When at least one eSIM profile is available, MSA 100 sends information of the at least one available eSIM profile of the at least one MNO to the network device. The network device may then use the eSIM profile information to establish at least one cellular network connection through a cellular network of the at least one MNO. The procedure for performing an eSIM profile lookup will be discussed in more detail in fig. 11.
Fig. 10 is a process flow diagram illustrating a method for updating an exemplary eSIM profile lookup table 900 in accordance with an exemplary embodiment of the present invention. The process disclosed in FIG. 10 can be performed by a processing unit of an MSA (e.g., MSA 100). In a variant, the process of fig. 10 may also be performed by a processing unit of the MSA management server or network device.
In process 1001, MSA 100 receives at least one eSIM configuration file from at least one MNO. The at least one eSIM profile can be received directly from the at least one MNO or through a network device or an MSA management server. As a result of the process discussed in fig. 3, 7, 8A, or 8B, MSA 100 can receive at least one eSIM profile.
In process 1002, the received at least one eSIM profile is installed in at least one eUICC. The at least one eUICC in which the at least one eSIM profile is installed can be selected from a plurality of euiccs to install the at least one eSIM profile either before or after receiving the at least one eSIM profile. Multiple euiccs can be placed in MSA 100 or connected to MSA 100.
In process 1003, information about at least one eSIM profile received from at least one eUICC that has the at least one eSIM profile installed is retrieved. The retrieved information can include at least one MNO ID, at least one ICCID, and at least one eUICC ID of at least one eUICC that installs at least one eSIM profile.
In process 1004, eSIM profile lookup table 900 is updated according to the retrieved information. For example, the updated information regarding the installed at least one eSIM profile can include at least one MNO ID of the at least one MNO from which the at least one eSIM profile was received, at least one ICCID included in the at least one eSIM profile to uniquely identify the at least one eSIM profile, and at least one eUICC ID of the at least one eUICC in which the at least one eSIM profile is installed.
In process 1005, a status of at least one eSIM profile is set based on its availability. Each eSIM profile received by MSA 100 follows the process disclosed in fig. 10. The status of each installed eSIM profile can be set to indicate the availability of the eSIM profile. For example, the status is set to "available" when the eSIM profile is not in use, and is set to "in use" when the eSIM profile is in use. Typically, the status should be set to "available" for the eSIM configuration file just installed.
Fig. 11 is a process flow diagram illustrating a method for performing an eSIM profile lookup in an eSIM profile lookup table in accordance with an exemplary embodiment of the present invention. For illustration purposes, eSIM profile lookup is performed in eSIM profile lookup table 900. The process disclosed in FIG. 11 can be performed by a processing unit of an MSA (e.g., processing unit 101 of MSA 100). For example, eSIM profile lookup table 900 is stored in a memory unit (e.g., memory unit 105) of MSA 100. In a variant, the process of fig. 11 may also be performed by a processing unit of the MSA management server or by a processing unit of the network device.
The method begins in process 1101 when a request for at least one eSIM profile for at least one MNO is received at MSA 100 from a network device, such as network device 150. The request can include at least one MNO ID that specifies at least one eSIM profile requested by at least one MNO.
In process 1102, processing unit 101 of MSA 100 reads eSIM profile lookup table 900 to identify at least one eSIM profile associated with at least one MNO ID. In process 1103, processing unit 101 of MSA 100 determines whether at least one eSIM profile associated with at least one MNO ID is identified. When at least one eSIM profile is identified, processing unit 101 of MSA 100 determines whether at least one eSIM profile of the identified at least one eSIM profile is available in process 1104.
Process 1107 is performed when at least one eSIM profile associated with at least one MNO ID is not identified in process 1103. In process 1107, a negative response is sent to network device 150. Process 1107 is also performed when at least one of the identified at least one eSIM profile is not determined to be available in process 1104. A negative response is sent to inform network device 150 that the eSIM profile of at least one MNO is not stored in MSA 100 or is not available to MSA 100. After sending the negative response, the method can be stopped, or the act of starting downloading the at least one eSIM profile for the at least one MNO can be initiated as discussed in fig. 7, 8A, or 8B. In one variation, processes 1103 and 1104 may be performed simultaneously. In another variation, the process 1103 may be omitted, and only the process 1104 may be performed to determine whether at least one eSIM profile associated with at least one MNO ID is available.
Process 1105 is also performed when at least one of the identified at least one eSIM profile is determined to be available at process 1104. In process 1105, information regarding at least one eSIM profile from among the available at least one eSIM profile is transmitted to the network device 150. The transmitted information can include at least one IMSI of the at least one eSIM profile, at least one eUICC ID storing the at least one eSIM profile, and other associated information that may be needed by a cellular network of the at least one MNO. In one variation, the information is sent based on a specific information request from network device 150, where the specific information request may be initially received at network device 150 from at least one MNO.
In process 1106, a status related to at least one eSIM profile can be changed from "available" to "in use," information of the at least one eSIM profile being transmitted to the network apparatus 150. Upon receiving the notification from the network device 150, the state of the at least one eSIM profile can be changed back to "available". The notification can be a notification that MSA 100 network device 150 is not using at least one eSIM profile. In one variation, a notification can be sent to inform MSA 100 that network appliance 150 no longer requires use of at least one eSIM profile. In another variation, the status of at least one eSIM profile can be changed back to "available" when MSA 100 recognizes that the eSIM profile is not being used by network 150 for a particular period of time.
The notification can be sent by the network device 150 when the at least one cellular network connection established using the at least one eSIM profile is not used for data communications within a particular time period or when an administrator or user of the network device 150 manually disconnects the at least one cellular network connection established using the at least one eSIM profile. There is no limitation on the events that may trigger network device 150 to send a notification. Similarly, there is no limit to the number of times network device 150 may send notifications.
The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, and to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.