Installation of embedded subscriber identity module profiles on cellular devices

Abstract

There is provided a computer-implemented method (800) of installing an embedded or 10 integrated subscriber identity module ‘eSIM / iSIM’ profile onto a cellular device, the cellular device having a boo

Description

Field

[0001] The subject matter disclosed herein relates to the field of electronic communication and, more specifically, to the installation of embedded or integrated subscriber identity module (eSIM or iSIM) profiles on cellular devices. This document defines methods for installing an eSIM / iSIM profile onto a cellular device having a bootstrap connectivity profile. Background

[0002] Traditional physical subscriber identity module (SIM) cards have long been used in wireless / cellular devices such as mobile devices for mobile network access. However, with the advent of eSIM technology, the need for a physical card is eliminated. An eSIM is a digital SIM that allows an end user, or a system, to activate a cellular plan from a mobile carrier without using a traditional physical SIM card. The ability of eSIMs to be programmable, enabling the change of mobile network operator (MNO) remotely, without the need to swap a physical SIM card, marks a significant step forward in terms of convenience and flexibility.

[0003] The eSIM technology is governed by specifications provided by the GSM Association (GSMA), an organisation representing the interests of mobile operators worldwide. An eSIM is an embedded Universal Integrated Circuit Card (eUICC) that resides in a device and provides the same functionalities as a physical SIM card. It stores multiple operator profiles and can be remotely provisioned with new profiles. Summary

[0004] To install an eSIM or iSIM on demand (i.e., without prior access to a printed eSIM QR code or similar), a wireless / cellular device requires an Internet connection. This Internet connection serves at least two purposes.

[0005] A first purpose is obtaining the eSIM / iSIM profile details for installation (i.e., an Activation code and address for a server provisioning eSIM / iSIM profiles, such as a subscription manager data preparation plus (SM-DP+) server URL). Typically, these eSIM / iSIM profile details are obtained by a user of a cellular device purchasing an eSIM / iSIM profile via an online e-commerce checkout or via some other kind of eSIM / iSIM distribution process (i.e., an employee Enterprise portal).

[0006] A second purpose is using the obtained eSIM / iSIM profile details on the cellular device to trigger the download and installation of the eSIM / iSIM into the cellular device. Triggering the download and installation is a standardized process documented in GSMA specifications SGP.21 and SGP.22 titled, “eSIM Consumer Architecture Specification” and “eSIM Consumer Technical Specifications” respectively that are herein incorporated by reference. This step takes eSIM profile details (the activation code and address) and uses these details to download the eSIM profile, over the ES9+ interface, from a provisioning server such as the SM-DP+ server. The eSIM profile can then be installed and used by the cellular device to connect to a wireless communication network / mobile network.

[0007] However, scenarios can arise where a user of a cellular device temporarily has no active Internet connection. For example, a user of a cellular device may have no WiFi or cellular service when roaming or in some scenarios, domestically. Such a scenario can arise, for instance, when a user arrives at a foreign destination, such as an airport in a country where their mobile subscription does not extend. Should the user of a cellular device require use of a software application on their cellular device, this may not be achievable in situations where there is no active Internet connection.

[0008] In the abovementioned scenarios, a user of a cellular device faces the problem of needing to locate and use a WiFi connection (i.e., at a shop); locate and install a SIM card from a SIM card vendor (who may sell a physical SIM card or an eSIM profile in the form of a QR code); or enable roaming on their domestic SIM / eSIM / iSIM, if available in their domestic subscription, incurring costly roaming charges.

[0009] Disclosed herein are procedures for mitigating these problems by triggering the installation of an eSIM or iSIM profile on a cellular device even when the device does not have a currently active Internet connection. Said procedures may be implemented by methods, apparatuses and systems for installing an eSIM / iSIM profile onto a cellular device having a bootstrap connectivity profile.

[0010] In a first aspect, there is provided a computer-implemented method of installing an embedded or integrated subscriber identity module (eSIM / iSIM) profile onto a cellular device, the cellular device having a bootstrap connectivity profile, the method comprising: caching, into a memory of the cellular device, an activation code and address for an eSIM profile; determining a requirement for use of the eSIM / iSIM profile; determining that the cellular device lacks an active Internet connection; triggering, using the activation code and address cached in the memory of the cellular device, an activation of the bootstrap connectivity profile to provide a temporary Internet connection for obtaining the eSIM / iSIM profile; and installing via the temporary Internet connection, using the activation code and address cached in the memory of the cellular device, the eSIM / iSIM profile onto the cellular device.

[0011] In a second aspect, there is further provided a computer program comprising instructions which when executed by a processor of a cellular device, causes the cellular device to perform the method of the first aspect.

[0012] In a third aspect, there is further provided a non-transitory computer readable medium comprising the computer program of the second aspect.

[0013] In a fourth aspect, there is further provided a cellular device comprising: at least one memory; and at least one processor; wherein the at least one memory comprises computer-readable instructions, which when executed by the at least one processor, causes the cellular device to perform the method of the first aspect.

[0014] The present disclosure concerns the installation of eSIM or iSIM (hereinafter collectively referred to as eSIM or as eSIM / iSIM) profiles onto cellular devices (i.e., smartphones, laptops, tablets, Internet of Things devices) have bootstrap connectivity.

[0015] The approaches described herein tend to provide a solution that allows applications on cellular devices to trigger bootstrap connectivity profiles on the cellular devices in order to obtain a temporary Internet connection. This temporary Internet connection can be used to access, download and install an operational eSIM for the user’s cellular device.

[0016] More specifically, the approaches described herein tend to provide a solution for getting eSIM profile details (activation code and address i.e., SM-DP+ URL) to a cellular device before a user of the cellular device arrives in a scenario without an active Internet connection. The approaches described herein tend to cache the eSIM profile details with an application installed onto the cellular device, such that an application can trigger an eSIM profile installation process via the bootstrap connectivity profile of the cellular device, when no active Internet connection is available.

[0017] Such an approach tends to allow an application on a cellular device to offer Internet connections to a user that are restricted to the application itself or more widely usable (and optionally as a free or paid for subscription).

[0018] Such an approach tends to provide seamless and immediate Internet access for users in situations where WiFi or cellular Internet connectivity options are not available to a cellular device. Brief description of the drawings

[0019] In order to describe the manner in which advantages and features of the disclosure can be obtained, a description of the disclosure is rendered by reference to certain apparatus and methods which are illustrated in the appended drawings. Each of these drawings depict only certain aspects of the disclosure and are not therefore to be considered to be limiting of its scope. The drawings may have been simplified for clarity and are not necessarily drawn to scale.

[0020] Methods and apparatus for installation of eSIM profiles on cellular devices will now be described, by way of example only, with reference to the accompanying drawings, in which: Figure 1 illustrates an example, useful for understanding aspects of the disclosure herein, of a wireless communication system. Figure 2 illustrates an example, useful for understanding aspects of the disclosure herein, of a cellular device. Figure 3 illustrates an example, useful for understanding aspects of the disclosure herein, of a network apparatus. Figure 4 illustrates an example, useful for understanding aspects of the disclosure herein, of a current eSIM activation process. Figure 5 illustrates an example, useful for understanding aspects of the disclosure herein, of a current eSIM transfer process. Figure 6 provides an example depiction, useful for understanding aspects of the disclosure herein, of how a SIM card is the linkage between users, mobile service providers and mobile devices. Figure 7 provides an example depiction, useful for understanding aspects of the disclosure herein, of the relationships between an eSIM profile, a mobile device, a mobile service provider and a user. Figure 8 provides an example of a method in accordance with aspects of the disclosure herein. Figure 9 provides an example of a preferred method in accordance with aspects of the disclosure herein. Figure 10 provides a further example of a preferred method in accordance with aspects of the disclosure herein. Detailed description

[0021] As will be appreciated by one skilled in the art, aspects of this disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, arrangements described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, micro-code, etc) or a form combining software and hardware aspects.

[0022] For example, the disclosed methods and apparatus may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.

[0023] Furthermore, the methods and apparatus may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and / or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and / or non-transmission. The storage devices may not embody signals. In certain arrangements, the storage devices only employ signals for accessing code.

[0024] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0025] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store, a program for use by or in connection with an instruction execution system, apparatus, or device.

[0026] Reference throughout this specification to an example of a particular method or apparatus, or similar language, means that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the method and apparatus described herein. Thus, reference to features of an example of a particular method or apparatus, or similar language, may, but do not necessarily, all refer to the same example, but mean “one or more but not all examples” unless expressly specified otherwise. The terms “including”, “comprising”, “having”, and variations thereof, mean “including but not limited to”, unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a”, “an”, and “the” also refer to “one or more”, unless expressly specified otherwise.

[0027] As used herein, a list with a conjunction of “and / or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of’ includes one, and only one, of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.

[0028] Furthermore, the described features, structures, or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed methods and apparatus may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

[0029] Aspects of the disclosed method and apparatus are described below with reference to schematic flowchart diagrams and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flowchart diagrams and / or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the schematic flowchart diagrams and / or schematic block diagrams.

[0030] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function / act specified in the schematic flowchart diagrams and / or schematic block diagrams.

[0031] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions / acts specified in the schematic flowchart diagrams and / or schematic block diagram.

[0032] The schematic flowchart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products. In this regard, each block in the schematic flowchart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0033] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0034] The description of elements in each figure may refer to elements of proceeding Figures. Like numbers may refer to like elements in all Figures.

[0035] Figure 1 depicts an example of a wireless communication system 100 that is useful for understanding aspects of the present disclosure. The wireless communication system 100 may include wireless / cellular devices 102 and network apparatus / units 104. Even though a specific number of wireless / cellular devices 102 and network apparatus / units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of wireless / cellular devices 102 and network apparatus / units 104 may be included in the wireless communication system 100.

[0036] The wireless / cellular devices 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle onboard computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. The wireless / cellular devices 102 may include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the wireless / cellular devices 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The wireless / cellular devices 102 may communicate directly with one or more of the network apparatus / units 104. The wireless / cellular devices 102 may communicate directly with other wireless / cellular devices 102.

[0037] The network apparatus / units 104 may be distributed over a geographic region. A network apparatus / unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a radio access network (RAN), a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, or generally as a network entity or function. The network apparatus / units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network apparatus / units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0038] Generally, the wireless communication system 100 may implement an open or proprietary communication protocol, for example, third generation partnership project (3GPP) protocols, New Radio (NR) protocols, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0039] The network apparatus / units 104 may serve a number of wireless / cellular devices 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network apparatus / units 104 transmit DL communication signals to serve the wireless / cellular devices 102 in the time, frequency, and / or spatial domain.

[0040] It will be understood that the wireless communication system 100 is provided as an example to illustrate certain communications and interactions between wireless / cellular devices 102 and network apparatus / units 104.

[0041] Figure 2 depicts an example of a wireless / cellular device 200 that is useful for understanding aspects of the disclosure herein. The wireless / cellular device 200 may be used for implementing aspects of the methods described herein. For instance, the wireless / cellular device 200 may perform aspects of the methods 800, 900, 1000 of Figures 8, 9 and 10. The wireless / cellular device 200 may be in accordance with one or more of the wireless / cellular devices described in examples herein. In particular, the wireless / cellular device 200 may be in accordance with the wireless / cellular devices 102 of Figure 1. The wireless / cellular device 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.

[0042] The input device 215 and the output device 220 may be combined into a single device, such as a touchscreen. In some implementations, the wireless / cellular device 200 does not include any input device 215 and / or output device 220. The wireless / cellular device 200 may include one or more of: the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and / or the output device 220.

[0043] As depicted, the transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The transceiver 225 may communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 225 may be operable on an unlicensed spectrum. Moreover, the transceiver 225 may support one or more beams. Additionally, the transceiver 225 may support at least one network interface 240 and / or application interface 245. The application interface(s) 245 may support one or more APIs. The network interface(s) 240 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 240 may be supported, as understood by one of ordinary skill in the art.

[0044] The processor 205 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 205 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. The processor 205 may execute instructions stored in the memory 210 to perform aspects of the methods and routines described herein. The processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225.

[0045] The processor 205 may control the wireless / cellular device 200 to implement the wireless / cellular device behaviors described herein. The processor 205 may include an application processor (also known as “main processor”) which manages applicationdomain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.

[0046] The memory 210 may be a computer readable storage medium. The memory 210 may include volatile computer storage media. For example, the memory 210 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). The memory 210 may include non-volatile computer storage media. For example, the memory 210 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 210 may include both volatile and non-volatile computer storage media.

[0047] The memory 210 may also store program code and related data, such as an operating system (OS) or other controller algorithms operating on the wireless / cellular device 200.

[0048] The input device 215 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. The input device 215 may be integrated with the output device 220, for example, as a touchscreen or similar touch-sensitive display. The input device 215 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. The input device 215 may include two or more different devices, such as a keyboard and a touch panel.

[0049] The output device 220 may be designed to output visual, audible, and / or haptic signals. The output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 220 may include, but is not limited to, a Liquid Crystal Display (“LCD”), a Light-Emitting Diode (“LED”) display, an Organic LED (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 220 may include a wearable display separate from, but communicatively coupled to, the rest of the wireless device 200, such as a smartwatch, smart glasses, a heads-up display, or the like. Further, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0050] The output device 220 may include one or more speakers for producing sound. For example, the output device 220 may produce an audible alert or notification (e.g., a beep or chime). The output device 220 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 220 may be integrated with the input device 215. For example, the input device 215 and output device 220 may form a touchscreen or similar touch-sensitive display. The output device 220 may be located near the input device 215.

[0051] The transceiver 225 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times in order to send and receive messages.

[0052] The transceiver 225 includes at least one transmitter 230 and at least one receiver 235. The one or more transmitters 230 may be used to provide uplink communication signals to a base unit of a wireless communications network. Similarly, the one or more receivers 235 may be used to receive downlink communication signals from the base unit. Although only one transmitter 230 and one receiver 235 are illustrated, the wireless / cellular device 200 may have any suitable number of transmitters 230 and receivers 235. Further, the transmitter(s) 230 and the receiver(s) 235 may be any suitable type of transmitters and receivers. The transceiver 225 may include a first transmitter / receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

[0053] The first transmitter / receiver pair may be used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter / receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. The first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, certain transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access a shared hardware resource and / or software resource, such as for example, the network interface 240.

[0054] One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated into a single hardware component, such as a multitransceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component. One or more transmitters 230 and / or one or more receivers 235 may be implemented and / or integrated into a multi-chip module. Other components such as the network interface 240 or other hardware components / circuits may be integrated with any number of transmitters 230 and / or receivers 235 into a single chip. The transmitters 230 and receivers 235 may be logically configured as a transceiver 225 that uses one more common control signals or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or in a multi-chip module.

[0055] The wireless / cellular device 200 may represent a wireless / cellular mobile device, for instance an eUICC enabled wireless mobile device or an integrated eUICC wireless mobile device. Such devices may include a smartphone, a tablet, a laptop, a wearable sensor, a machine-to-machine (M2M) device, or a vehicle. The wireless / cellular device 200 may comprise eSIM functionality implemented on a hardware tamper-resistant element (TRE) within a host system-on-chip (SoC) included in the wireless / cellular device 200. The eSIM functionality tends to provide the same functionality as a physical SIM card and can store multiple operator profiles (eSIM profiles) and can be remotely provisioned with new eSIM profiles.

[0056] Figure 3 depicts an example of a network apparatus / unit 300 that is useful for understanding aspects of the disclosure herein. The network apparatus / unit 300 may be one implementation of an entity in a wireless communications network, e.g., in one or more of the wireless communications networks described herein. The network apparatus / unit 300 may be, for example, a Network Function (NF) or Application Function (AF), or another entity, such as the network apparatus / units 104 of Figure 1 or of one or more of the wireless communications networks described herein. The network apparatus / unit 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.

[0057] The input device 315 and the output device 320 may be combined into a single device, such as a touchscreen. In some implementations, the network apparatus / unit 300 does not include any input device 315 and / or output device 320. The network apparatus / unit 300 may include one or more of: the processor 305, the memory 310, and the transceiver 325, and may not include the input device 315 and / or the output device 320.

[0058] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with one or more wireless / cellular devices 200. Additionally, the transceiver 325 may support at least one network interface 340 and / or application interface 345. The application interface(s) 345 may support one or more APIs. The network interface(s) 340 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 340 may be supported, as understood by one of ordinary skill in the art.

[0059] The processor 305 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. The processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0060] The memory 310 may be a computer readable storage medium. The memory 310 may include volatile computer storage media. For example, the memory 310 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). The memory 310 may include non-volatile computer storage media. For example, the memory 310 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 310 may include both volatile and non-volatile computer storage media.

[0061] The memory 310 may store data related to establishing a multipath unicast link and / or mobile operation. For example, the memory 310 may store parameters, configurations, resource assignments, policies, and the like, as described herein. The memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network apparatus / unit 300.

[0062] The input device 315 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. The input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display. The input device 315 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. The input device 315 may include two or more different devices, such as a keyboard and a touch panel.

[0063] The output device 320 may be designed to output visual, audible, and / or haptic signals. The output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 320 may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus / unit 300, such as a smartwatch, smart glasses, a heads-up display, or the like. Further, the output device 320 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0064] The output device 320 may include one or more speakers for producing sound. For example, the output device 320 may produce an audible alert or notification (e.g., a beep or chime). The output device 320 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 320 may be integrated with the input device 315. For example, the input device 315 and output device 320 may form a touchscreen or similar touch-sensitive display. The output device 320 may be located near the input device 315.

[0065] The transceiver 325 includes at least one transmitter 330 and at least one receiver 335. The one or more transmitters 330 may be used to communicate with a wireless / cellular device 200, as described herein. Similarly, the one or more receivers 335 may be used to communicate with other network functions or entities, as described herein. Although only one transmitter 330 and one receiver 335 are illustrated, the network apparatus / unit 300 may have any suitable number of transmitters 330 and receivers 335. Further, the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitters and receivers.

[0066] Currently, the eSIM activation process for a wireless / cellular device such as wireless / cellular device 200 of Figure 2, is enabled through GSMA specifications. Figure 4 provides an example, useful for understanding aspects of the disclosure herein, of a current eSIM activation process 400.

[0067] In a first step 401, there is device purchase. A user purchases an eSIM-capable device such as wireless / cellular device 200. This device has an eSIM chip embedded inside it, which can't be removed like traditional SIM cards. Such an eSIM is usually preinstalled by the device manufacturer. Alternatively, the user may not purchase the device themselves, but may have access to the device freely, through a lease agreement or may have access to the device through their employer.

[0068] A user must then perform a profile download. The user initiates the eSIM activation process, often via a mobile operator's application or website. In a further step 402, the user may need to purchase or select a mobile plan during this process from a service provider of their choosing. In a further step 403, the service provider activates the mobile service. In a further step 404, the service provider issues an eSIM profile. In a further step 405, an eSIM activation method is determined. Various activation methods may be used including: ‘push install’ 406a of eSIM profile linked to a device eUICC ID; ‘pull install’ 406b using automated install via an application; and the issuance of a QR code 406c to activate an eSIM profile.

[0069] As depicted by the further step 406c, the operator sends an activation code or a QR code to the user. The user then uses this code to download the operator's eSIM profile onto their device using software installed on their device.

[0070] In a further step 407 there is eSIM profile installation. The wireless / cellular device connects to the mobile operator's remote provisioning server, through a Wi-Fi or cellular data connection. The installation procedure can vary dependent on deployment scenario. For instance, for M2M deployments the server may send or ‘push’ the eSIM profile, which includes the operator's credentials and network settings, to the device. The eSIM then installs this profile, making it active. In consumer deployment / specifications the wireless / cellular device may download the eSIM profile from the server and ensure it reaches the eUICC chip embedded in that device, for installation.

[0071] In a further step 408, there is network connection. Once the profile is installed, the device can connect to the mobile operator's network, just like it would with a physical SIM card. The user can start making calls, sending messages, and using data.

[0072] In a further step 409, there is profile switching or deletion. The eSIM technology allows users to switch between different operator profiles stored on the eSIM, without needing to change physical SIM cards. If a user wishes to change their mobile operator, they can download a new operator's eSIM profile and make it active. Similarly, the user can disable 409a or delete 409b an operator's profile if they no longer wish to use it.

[0073] Figure 5 depicts an example, useful for understanding aspects of the disclosure herein, of a current eSIM transfer process 500. The process for transferring an eSIM is broadly standardised as follows.

[0074] In a first step 501, there is new device purchase. A user purchases a new eSIM-capable device. This device also has an eSIM embedded inside it. As previously discussed with regard to Figure 4, alternatively the user may not directly purchase the device but may instead have access to the device freely, through a lease agreement, or through their employer, for instance.

[0075] In a further step 502, there is eSIM transfer. The user needs to initiate the eSIM transfer process from their old device. This varies depending on their service provider, type of device and operating system of the device. Either the device initiates the transfer 502a via the device setup process on the new device, or the service provider initiates a transfer of the mobile service 502b via the mobile operator's app, website or call centre.

[0076] In a further step 503, once the transfer process is initiated (either via device or service provider) a new eSIM profile is provided and a SIM swap is performed in the service provider systems. The old eSIM profile will no longer function. The user will then need to install the new eSIM profile.

[0077] In a further step 504, it is necessary to determine the eSIM install and activation method. The install can be triggered in multiple ways either via an automated push command 504a, an application-based trigger or ‘pull install’ 504b, or a user scanning a QR code 504c.

[0078] In a further step 505, there is eSIM profile installation. The device connects to the mobile operator's remote provisioning server, usually through a Wi-Fi or cellular data connection. The installation procedure may vary dependent upon deployment scenario (as previously discussed with respect to Figure 4 and the M2M / consumer deployments). For the purposes of illustration in this particular example, the server sends or ‘pushes’ the eSIM profile, which includes the operator's credentials and network settings, to the device. The eSIM then installs this profile, making it active.

[0079] A further step 506 comprises performing network connection. Once the new profile is installed, the device can connect to the mobile operator's network, just like it would with a physical SIM card. The user can start making calls, sending messages, and using data on their new device.

[0080] In a further step 507, the customer can manage their eSIM profile. This can include disabling an eSIM profile 507a or deleting an eSIM profile 507b.

[0081] It will be understood that service providers for mobile communications following 3GPP specifications require that communications devices have the proper credentials to access and enable the use of mobile network services. These credentials securely and uniquely identify a subscription with the service provider and enable the device to access and use the services associated with that subscription. Examples of services for mobile service providers (MNO’s / MVNO’s) may include, mobile voice calling, text messaging, or Internet data service.

[0082] The credentials for a mobile service provider may reside in a secure container called a Universal Integrated Circuit Card (UICC) or “SIM card”. Credentials for a subscriber in 3GPP (LTE / GSM / UMTS) networks generally have an International Mobile Subscriber Identity (IMSI) that identifies them in a service provider network. These credentials are stored within the SIM Card.

[0083] Traditionally the SIM card was distributed by mobile service providers as a discrete physical component via different distribution channels. For example, retail stores, online, 3rd party resellers or pre-integrated into a mobile device.

[0084] Each UICC (or SIM Card) is identified by a unique identifier called an ICCID (Integrated Circuit Card ID). An ICCID will be associated with different network identifiers such as one or more IMSI (International Mobile Subscriber Identifier), one or more MSISDN (Mobile Station Integrated Services Digital Network) and network credentials (Ki, OpC).

[0085] The activation of a SIM card to have a valid subscription is required to enable various services on a mobile service provider's network. This involves associating the ICCID with a valid subscription and ensuring the relevant network components are configured to provide service to the device when it establishes a connection (identified by the IMSI or, in some cases the IMEI).

[0086] The evolution of the UICC now supports the remote provisioning of credentials to an eUICC (Embedded UICC). Every eUICC has a permanent unique identifier called the eUICC ID (EID). The service providers credentials may be called an eUICC profile or iUICC profile and are installed via a Remote SIM Provisioning platform (SM-DP or SM-DP+). An eUICC profile is still identified by a mobile operator via a unique identifier, ICCID.

[0087] Devices may be equipped with an eUICC or iUICC via a discrete hardware element, removable hardware element or integrated component. Regardless of the form factor, the eUICC / iUICC will still have a unique identifier, eUICC ID (EID). A mobile operator can request that an eSIM profile (ICCID) be associated with a specific eUICC card (EID). The EID may be shared with the mobile operator when ordering a new subscription and associated eSIM profile (ICCID). The mobile operator can link the profile to the EID via an SM-DP+. The mobile operator may notify an eSIM Discovery Service that an eSIM profile is now associated with that particular EID in order for the eSIM profile to be installed into the end device.

[0088] When the EID is unknown, the mobile operator may issue an Activation Code to a customer that uniquely identifies the eSIM profile to install. The Activation Code is a download link to the specific eSIM profile and follows a defined format prescribed by the GMSA, e.g., “1$SMDP.GSMA.COM$04386-AGYFT-A74Y8-3F815”.

[0089] An Activation Code will include an identifier and be issued with the remote server address in order to correctly identify an eSIM Profile stored on the SM-DP or SM-DP+.

[0090] The Activation Code may be provided to the customer as plain text or encoded as a QR code distributed digitally (e.g., via email, website, mobile application) or physically (e.g., printed and sent via mail or at a retail store).

[0091] The wireless / cellular device will use the activation code to remotely install the eSIM profile to the eUICC using a method standardised by the GSMA. It is also possible that the installation of a new eSIM profile to an eUICC is triggered automatically via a Remote SIM Provisioning with no interaction from the wireless / cellular device.

[0092] The eUICC profile will be installed by a defined protocol standard from the GSMA and manage an eUICC profile on a defined set of eUICC’s (by EID).

[0093] In the well-established practices of issuing a SIM card to users to securely connect to mobile networks, the physical nature of the SIM has provided a permanent and immutable object for users and service providers to control the activation, usage and transfer of mobile services forwireless / cellular devices. Figure 6 provides an example depiction 600, useful for understanding aspects of the disclosure herein, of how a SIM card 610 is the linkage between Users 640, Mobile Service Providers 630 and Mobile / wireless / cellular Devices 620.

[0094] With the introduction of eSIM, the relationships have been disrupted and introduced changes for the way users activate and manage their connectivity. Mobile service providers issue methods of activating eSIM profiles to users in order to activate mobile connectivity in their devices using eSIM. The user manages the linkage of eSIM profiles in these devices and interacts with both the mobile device and mobile service provider to manage the activation and changes throughout the lifecycle. Figure 7 provides an example depiction 700, useful for understanding aspects of the disclosure herein, of the relationships between an eSIM profile 710, a wireless / cellular / mobile device 720, a mobile service provider 730 and a user 740.

[0095] As will be apparent from the discussion of Figures 4-7, eSIM profile details are made up primarily of two things: an activation code; and an address for a provisioning server that manages eSIM profiles, such as a SM-DP+ URL. The process to install an eSIM can be triggered by scanning a QR code, using an API in a mobile application or via a push message. The payload of these eSIM trigger functions is typically a string made up of an address / URL handler, the activation code and the SM-DP+ URL. An example might be the string, ‘EPxP1$dp-plus-exampEcom$267UN-KM4El4-6E7E8-CD82N’’ wherein ‘DPA:'! $’is the handler, ‘dp-plus-example.com’is the SM-DP+ URL and, ‘267UN-KM4H4-6E7E8-CD82N’ is the activation code. The combination of the SM-DP+ URL and the activation code links to an eSIM profile on a SM-DP+ server, with the activation code being unique to a specific profile (i.e., a 1:1 relationship) or generic to a specific pool of eSIMs (i.e., a l:many relationship).

[0096] As will also be apparent from the discussion of Figures 4-7, the installation of an eSIM to a cellular device requires that the cellular device has a currently active Internet connection. The Internet connection provides a mechanism through which the eSIM details can be provided to the cellular device (i.e., getting the activation code and SM-DP+ URL to the device), and also provides a mechanism through which the actual eSIM can be downloaded and installed.

[0097] Cellular devices presently exist having pre-installed bootstrap connectivity profiles. Examples include the iPhone (RTM) 14 or 15 in the USA. A bootstrap connectivity profile is a cellular connection that the cellular device can enable / disable on demand. The bootstrap connectivity can be triggered when the cellular device detects that is has no Internet connection but the end user is attempting to install an eSIM. Whilst the presence of a bootstrap in certain cellular devices may allow for download of an eSIM when the cellular device does not have Internet connectivity, this presumes that the user of the cellular device has already obtained the eSIM profile details (activation code and SM-DP+ URL) to trigger the eSIM installation procedure. As described herein, scenarios exist where a user of a cellular device can find itself in a situation where no currently active Internet connection is available (i.e., when landing at an airport abroad) and eSIM profile details have not been previously purchased by the user to allow for cellular connection. An example scenario will now be described.

[0098] A user of cellular device may travel from the USA to the UK. The user has no roaming service for their cellular device or a roaming service that is limited only to the USA. The user, upon arrival in the UK, desires to order a taxi from the airport to their final destination. The user has an application on their cellular device that allows for ordering of taxis. However, the user of cellular device has no immediate access to WiFi nor a cellular service in the UK permitting roaming. Hence the application is unable to operate properly.

[0099] In the example scenario, the user of cellular device may have to seek our WiFi access from an airport cafe or similar, locate and buy a local SIM from an airport shop, or enable roaming from their domestic USA supplier and incur the associated expense.

[0100] The solutions described herein allow the application on the cellular device to trigger an eSIM installation process using the bootstrap connectivity profile of the cellular device. When originally downloading and installing the application (i.e., when the user had an Internet connection), eSIM details (activation code and SM-DP+ URL) were cached with the application. These eSIM details are cached until the point they are called upon by the application. Hence when the user of the cellular device arrives in the UK, has no Internet connection but attempts to use the application, the application determines a requirement for use of the eSIM associated with the eSIM profile details and triggers the eSIM installation process using the bootstrap connectivity profile. There is no requirement to obtain the eSIM profile details from an e-commerce portal or similar, as the details were already cached with the application. The OS of the cellular device is triggered to enable the bootstrap connectivity and install the new eSIM. The user can then use the application on the cellular device to order a taxi from the airport using the Internet connection provisioned by the new eSIM (which may be restricted to the use of the application itself or more broadly usable).

[0101] More generally, the disclosure herein tends to solve the problem of allowing an application on a cellular device to trigger the installation of an eSIM / iSIM profile onto the cellular device when the cellular device does not have a currently active Internet connection.

[0102] According to a first aspect, there is provided a computer-implemented method of installing an embedded or integrated subscriber identity module (eSIM / iSIM) profile onto a cellular device, the cellular device having a bootstrap connectivity profile, the method comprising: caching, into a memory of the cellular device, an activation code and address for an eSIM / iSIM profile; determining a requirement for use of the eSIM / iSIM profile; determining that the cellular device lacks an active Internet connection; triggering, using the activation code and address cached in the memory of the cellular device, an activation of the bootstrap connectivity profile to provide a temporary Internet connection for obtaining the eSIM / iSIM profile; and installing via the temporary Internet connection, using the activation code and address cached in the memory of the cellular device, the eSIM / iSIM profile onto the cellular device.

[0103] A user of a cellular device (for instance a smartphone, a laptop, a tablet or an Internet of Things device) may temporarily have no active Internet connection (i.e., no WiFi access, or cellular service when roaming or domestically). Byway of example, a user travelling abroad may not have obtained a local eSIM for their destination and may be away from other forms of Internet access such as WiFi. However, the user may still require use of their cellular device, more specifically the use of an application on their cellular device.

[0104] For cellular devices having eSIM (or equivalently iSIM) functionality, a cellular service is provided through the eSIM / iSIM profile. An eSIM / iSIM installation typically requires an active Internet connection for two reasons. A first reason is to obtain eSIM / iSIM profile details for an eSIM / iSIM to be installed (the activation code and SM-DP+ address or URL). These eSIM / iSIM profile details are typically obtained via an online purchase or e-commerce checkout or some other process, such as an Enterprise employee portal. A second reason is to trigger, using the eSIM / iSIM profile details, a SIM installation process on the cellular device. However, without an active Internet connection, the eSIM / iSIM profile details themselves cannot be obtained to allow for installation of an eSIM / iSIM to enable cellular connectivity.

[0105] The inventors have found that caching / preinstalling eSIM / iSIM profile details (an activation code and address / SM-DP+ address and optionally one or more rules) with an application on a cellular device, allows the application to be used to trigger activation of a bootstrap connectivity profile already pre-installed on the cellular device. The application can forward the eSIM / iSIM profile details to the cellular device OS to trigger an eSIM / iSIM installation process. Hence, even when an active Internet connection is not available, the bootstrap connectivity can be exploited to allow for an operational eSIM / iSIM to be installed and subsequently used by the triggering application or more broadly to provide cellular connectivity.

[0106] As referred to herein, the cellular device may be a device having eSIM or equivalently iSIM capability. It has an ability to connect with cellular networks. The term ‘cellular device’ may include, for example, a wireless mobile device (also referred to herein as a mobile device) such as a mobile phone or cellular enabled tablet. A ‘cellular device’ may include eUICC enabled devices supporting eSIM or equivalently iSIM.

[0107] The “bootstrap connectivity profile” may be an eSIM profile, iSIM profile, or other suitable connectivity bearer profile. The bootstrap connectivity profile is a connectivity profile that can be activated by the cellular device (for instance by an OS of the cellular device) when no Internet connection is available. The bootstrap connectivity profile provides a temporary cellular connection, enabling download and installation of a new eSIM / iSIM profile when no other Internet connection is available. As referred to herein, ‘obtaining’ the eSIM / iSIM profile may comprise accessing / downloading the eSIM / iSIM profile.

[0108] The computer-implemented method may be installed on the cellular device as part of a software application. Such a software application may detect when the cellular device lacks an Internet connection and has the functionality to trigger an eSIM / iSIM profile installation process when a user requirement for such has been determined. The user requirement may comprise the use / attempted use of the software application, for instance, or an indication by a user made towards an application (in response to options presented by the application) for a free or paid for Internet connection. Determining the user requirement may involve determining the user requirement based on one or more additional attributes such as a type of the cellular device; a geographic location of the cellular device; a network capacity of the cellular device; a network capability of the cellular device; an internet protocol, IP, address of the cellular device; an operating system, OS, version of the cellular device; a time of day, for instance.

[0109] The caching mechanism itself may be integrated with a software application that performs the method on the cellular device. The activation code and address (i.e., a server address such as an SM-DP+ address, also referred to herein as the SMDP+ address, which may be a URT or other identifier pointing to a location of a server responsible for managing eSIM profiles), herein also referred to as eSIM / iSIM profile details, may be cached during initial application setup, installation or during subsequent application updates. The activation code itself may be determined using an algorithm that has also been cached.

[0110] As referred to herein, the activation code and address (i.e., SMDP+ address) cached in the memory of the cellular device may be referred to as the cached activation code and address. The cached activation code and address is the activation code and address locally cached into the memory of the cellular device. The caching occurs when the cellular device has an active Internet connection i.e., before it is determined that no active Internet connection is available. An ‘Internet connection’ may be considered ‘active’ when it is currently available for Internet access.

[0111] The method may be performed by an application on a cellular device, by the OS of the cellular device, or a combination thereof. The caching may comprise caching the activation code and address with the application.

[0112] The caching may comprise caching the activation code and address with an application when the application is installed or opened for the first time on the cellular device; and / or caching the activation code and address with an application when the application is updated on the cellular device.

[0113] Caching the activation code and address on first use of an application tends to ensure that the application developer has the option to trigger the install of an eSIM / iSIM for the end user when they have no Internet connection. Hence an application developer has control over which scenarios to offer the eSIM / iSIM install to the end user, as the cached eSIM / iSIM profile tends to be always available. Caching upfront tends to ensure that new users for an application are mapped to a connectivity profile for that user. This may reduce the developer’s overhead in managing multiple codes and simplify the support process. This may also simplify the data storage and retrieval requirements, resulting in faster application performance and reduced complexity in code maintenance.

[0114] Alternatively, or in addition, there could be dozens of connectivity providers, each with different activation codes and addresses. Caching the activation code and address when the application is updated, tends to ensure that the application provides the latest eSIM / iSIM profiles which can foster trust and reliability in the application’s services by offering an improved temporary connectivity service. Furthermore, such an approach tends to reduce manual update procedures and allows new eSIM / iSIM profiles to be pushed as part of the regular application update cycle for a developer.

[0115] Application developers may implement a background service within the application to handle updates and maintain the most recently required cached eSIM / iSIM information for application functionality.

[0116] The caching may comprise caching a single unified activation code for a plurality of eSIM / iSIM profiles.

[0117] A single unified activation code may be a common string that is used as the activation code across all instances of a particular application. By way of example, all applications from a particular service provider may have / use the same activation code (such that ABC1234-ABC5678-ABC910). A single unified activation code tends to simplify the developer’s distribution strategy for eSIM / iSIM profiles. The scalability of the application’s eSIM / iSIM service tends to be enhanced by using a one-size-fits-all approach, reducing the need for rule-specific eSIM / iSIM activation codes. Such an approach tends to offer simplicity of a single code pathway, making it easier to implement, test, and maintain within an application infrastructure.

[0118] Furthermore, eSIM / iSIM profile allocation can be performed by a backend server (such as a SM-DP+ server) based on an IP address of the cellular device. Hence, developers tend to be able to delegate the complexity of profile management to the backend server, streamlining an application’s operational logic. Such a capability can be built into the backend server allowing developers to modify profile allocation rules without updating the application deployed to the cellular device. This tends to allow for a reduction in an application’s footprint and complexity, as the rules for eSIM / iSIM profile distribution are handled by the backend server.

[0119] The caching may comprise: caching a plurality of activation codes and addresses for respective eSIM / iSIM profiles; and caching one or more rules for selecting an activation code and address from the plurality of activation codes and addresses.

[0120] One or more rules may be cached alongside the plurality of activation codes and addresses for determining, based on the user requirement, which of the activation codes and addresses are to be used for installing the respective eSIM / iSIM profile.

[0121] Having a plurality of activation codes and addresses allows developers to offer tailored services by region or user type, potentially increasing application engagement in different markets. This tends to enhance the value of the solutions described herein by dynamically offering the best connectivity option, which can be a strong selling point for quality, reliability, regulatory requirements etc. For application developers, this tends to introduce the flexibility to ensure the right profile can be delivered to the end user and device, based on a set of rules and requirements (e.g., regulatory) that might be unviable with a single global connectivity partner.

[0122] The caching may comprise: caching an algorithm for generating the activation code.

[0123] The use of an algorithm tends to add a further layer of customisation and security, allowing code generation to be based on deterministic logic written into an application’s software rather than caching one or more actual activation codes themselves. This tends to reduce the need for a large database of pre-generated codes to be maintained by an application’s backend servers. This tends to provide a scalable solution for eSIM / iSIM profile generation that can adapt as the application’s user base grows.

[0124] The triggering of the activation of the bootstrap connectivity profile may comprise: passing the cached activation code and address to an application programming interface (API), optionally an API of an operating system (OS) of the cellular device.

[0125] The API may be considered as a general method used to trigger the installation of the eSIM and could vary by device type and OS. The API of the OS may be an interface provided by the OS that allows applications to request installation of eSIM / iSIM profiles using the cached application code and address.

[0126] Whilst the triggering via the API provides an example of triggering the activation of the bootstrap connectivity profile, other options include the use of a previously sent / cached clickable QR code, or a previously sent / cached hyperlink which can trigger the eSIM / iSIM installation.

[0127] The method may further comprise establishing an Internet connection using the eSIM / iSIM profile.

[0128] The method may further comprise triggering a payment transaction for the Internet connection.

[0129] Once a valid cellular / Intemet connection has been established using the eSIM / iSIM profile (not the bootstrap connectivity profile), the cellular / Internet connection may allow one or more services to be enabled and operated. The use of the cellular / Internet connection may be conditional upon payment of a fee which can be debited from an account of a user of the cellular device using the payment transaction.

[0130] The cellular device may be a cellular device selected from the list of cellular devices consisting of: a smartphone; a tablet; a cellular enabled laptop; an Internet of Things ToT’ device. The cellular device may be an embedded universal integrated circuit card, eUICC, device; an integrated eUICC, wireless device; awearable sensor; a machine to machine, M2M, device; or a vehicle. An integrated eUICC is where the SIM or eSIM functionality is implemented on a hardware Tamper Resistant Element (TRE) within a host System-on-Chip (SoC) and included in the cellular device.

[0131] The determining the requirement for use of the eSIM / iSIM profile may comprise: outputting, via a user interface of the cellular device, a first message to a user of the cellular device, wherein the first message comprises one or more user-selectable options for providing an Internet connection for the cellular device; receiving, via the user interface of the cellular device, a first response comprising a selected one of the one or more user-selectable options; and determining the requirement for use of the eSIM / iSIM profile based at least partly on the selected one of the user-selectable options.

[0132] The user interface may be a display, touch screen, speaker and microphone, for example.

[0133] The one or more user-selectable options may comprise: a payment-free Internet connection; a payment-free Internet connection with one or more restrictions, optionally restricted to a specific application; a payment-based Internet connection; and a payment based Internet connection with one or more restrictions, optionally restricted to a specific application.

[0134] The payment-free / payment-based Internet connection may be based on a user status or profile or tiering of a user / user group. For instance, a user of the cellular device may have a certain status or tier within an application and hence may be entitled to a payment-free, payment-based, and / or restricted Internet connection accordingly. The restriction may be a restriction to an application or to a data limit (i.e., download limit), for instance.

[0135] The determining of a user requirement for use of the eSIM / iSIM profile comprises determining: a location of a user of the cellular device; and / or a classification of a user of the cellular device or an application on the cellular device.

[0136] The address may be a Subscription Manager Data Preparation Plus (SM-DP+) address.

[0137] After installing the eSIM / iSIM profile, the bootstrap connectivity profile may be deactivated.

[0138] The methods described herein may be performed by at least one of: an application for a smartphone; an application for a tablet; an application for a cellular enabled laptop; an application for an loT device; and an OS of the cellular device.

[0139] The methods described herein may be performed by an application or by an OS of the cellular device. Specifically, the cellular device OS may contain logic to automatically enable an eSIM / iSIM when specific applications are opened without an Internet connection, and the application indicates it can facilitate connectivity. Such an approach can provide a deeper integration into the device's OS, allowing for a more automated user experience in which the need for internet connectivity is anticipated and resolved by the cellular device itself. Rules may be codified within the device's OS, which could include parameters such as application identity (e.g., a service provider name or application name), lack of internet connectivity, user preferences, and historical data usage patterns. Having the method performed by an OS tends to contribute to Context-Aware Connectivity, wherein the device can make intelligent decisions on when to activate the eSIM / iSIM based on the user's current context and the application's capabilities. In addition, there tends to be reduced user friction by minimising the need for user decisions in enabling connectivity, allowing the user experience to be streamlined, making it more likely that the user will engage with the service. Furthermore, there tends to be enhanced security, with the OS enforcing strict rules on when eSIM / iSIMs can be activated, potentially reducing unauthorised use and enhancing overall device security. Resource management tends also to be improved - by allowing the OS to manage connectivity, the system can optimise data usage across applications, potentially extending the eSIM / iSIM's benefits to other device functions when needed. This level of integration may require collaboration between application developers and device OS manufacturers to ensure seamless communication and rule execution. It could be based on a specification from the device OS provider. The integration of the method with the OS effectively tends to turn the cellular device into a smart connectivity manager, further simplifying the process for the user and increasing the value proposition of both the application and the device itself.

[0140] According to a second aspect, there is provided a computer program comprising instructions which when executed by a processor of a cellular device, causes the cellular device to perform the method of the first aspect.

[0141] The computer program may be an application or OS for a cellular device. The computer program may be selected from the list of computer programs consisting of: an application for a smartphone; an application for a tablet; an application for a cellular enabled laptop; an application for an loT device; and an OS for a cellular device.

[0142] According to a third aspect, there is provided a non-transitory computer readable medium comprising the computer program of the second aspect.

[0143] According to a fourth aspect, there is provided a cellular device comprising: at least one memory; and at least one processor; wherein the at least one memory comprises computer-readable instructions, which when executed by the at least one processor, causes the cellular device to perform the method of the first aspect.

[0144] The cellular device may be referred to herein as an apparatus. The cellular device may comprise a transceiver (or a separate transmitter and receiver) for providing cellular connectivity.

[0145] It will be appreciated that particular advantages of the first aspect may be applicable to the other aspects described herein.

[0146] Exemplar methods in accordance with aspects of the present disclosure will now be described with reference to Figures 8, 9 and 10. The methods refer to the operation of an application on a cellular device having bootstrap connectivity. Certain features of a cellular device are referred to in the discussion of the Figures. These features will now be briefly introduced.

[0147] The cellular device has eSIM capability. The device may be a smartphone, tablet, or laptop equipped with eSIM or iSIM functionality and the ability to connect to cellular networks. The cellular device supports a bootstrap eSIM profile that can be activated by the device’s operating system when no other Internet connection is available the operating system detects the need to install an eSIM.

[0148] The application is a software application installed on the cellular device, such as a taxi ordering application, capable of detecting when the device lacks on Internet connection. The application includes functionality to prompt a user of the cellular device to initiate an eSIM profile installation process for temporary Internet access.

[0149] A caching mechanism is integrated with the application, such a mechanism caching eSIM profile details (an activation code and SM-DP+ URL) that are needed to install a new eSIM profile. These details are cached during initial application installation / setup or during periodic updates whenever the application accesses the Internet. An algorithm may also be used in the application to generate activation code / s.

[0150] The cellular device has an operating system API. This is an interface provided by the device’s operating system that allows installed applications to request the installation of an eSIM profile using the cached eSIM profile details. The cellular device may also support scanning or QR codes or clicking or eSIM links (i.e., a URL) to trigger eSIM installation.

[0151] A bootstrap eSIM profile is pre-installed on the cellular device that can be activated by the device’s operating system to provide a temporary cellular connection. This enables the download and installation of a new eSIM profile when no other Internet connection is available.

[0152] Figure 8 provides an example of a method 800 in accordance with aspects of the disclosure herein. More specifically the method 800 is a computer-implemented method of installing an eSIM / iSIM profile onto a cellular device, the cellular device having a bootstrap connectivity profile. The cellular device may be the cellular device 200 of Figure 2, for instance.

[0153] A first step 801 comprises caching, into a memory of the cellular device, an activation code and address for an eSIM / iSIM profile.

[0154] A further step 802 comprises determining a requirement for use of the eSIM / iSIM profile.

[0155] A further step 803 comprises determining that the cellular device lacks an active Internet connection.

[0156] A further step 804 comprises triggering, using the activation code and address cached in the memory of the cellular device, an activation of the bootstrap connectivity profile to provide a temporary Internet connection for obtaining the eSIM / iSIM profile.

[0157] A further step 805 comprises installing via the temporary Internet connection, using the activation code and address cached in the memory of the cellular device, the eSIM / iSIM profile onto the cellular device.

[0158] Figure 9 provides an example of a preferred method 900 in accordance with aspects of the disclosure herein.

[0159] In the preferred method 900, a cellular device already has a bootstrap eSIM profile installed which is triggered when the OS of the cellular device detects that a user of the cellular device is attempting to install an eSIM.

[0160] In the preferred method 900, the software / application that supports the method 900 is already installed on the cellular device. The software / application supporting the method 900 can detect whether the cellular device is compatible with the method 900. Furthermore, the software / application supporting the method 900 caches the eSIM profile details into a memory (i.e., an application datastore) on the cellular device (which may be performed, for instance, the first time the software / application was installed or executed. More generally, the step 801 of Figure 8 has already been performed.

[0161] These precursor steps to method 900 do not require the user of the cellular device to do anything specific related to eSIM, or even be aware of it. The user may simply have installed the application on the cellular device.

[0162] A first step 901 comprises lack of Internet detection. In this step 901, the application on the cellular device detects that the device is attempting to access the Internet but no connection is available (e.g., the user trying to use the application at an international airport without Wi-Fi or roaming services).

[0163] A further step 902 comprises user prompt. In this step 902, the application prompts the user of the cellular device with options for temporary Internet access, either free (locked to the application’s services) or paid (providing broader Internet access). The steps 901 and 902 combined correspond to the steps 802 and 803 of Figure 8.

[0164] A further step 903 comprises selection and eSIM profile installation request. In this step 903, upon a user selection, the application reads the appropriate cached eSIM profile details and calls the cellular device OS API to initiate the eSIM installation process.

[0165] A further step 904 comprises bootstrap eSIM activation. In this step 904, the cellular device’s OS detects the request to install a new eSIM profile without an Internet connection and automatically activates the bootstrap eSIM profile, providing a temporary cellular connection. The steps 903 and 904 combined correspond to step 804 of Figure 8.

[0166] A further step 905 comprises eSIM profile download and installation. In this step 905, utilizing the temporary cellular connection, the device downloads and installs the new eSIM profile based on the provided Activation Code and SM-DP+ URL. The step 905 corresponds to step 805 of Figure 8.

[0167] A further step 906 comprises switching to new eSIM profile. In this step 906, after installation, the device OS disables the bootstrap profile, switches to the new eSIM profile for Internet connectivity, and returns control to the application.

[0168] A further step 907 comprises application functionality being resumed. In this step 907, the application detects the new Internet connection and resumes normal operation, allowing the user to access its services. If a broader Internet access eSIM profile was selected, other applications and services on the cellular device also gain Internet connectivity.

[0169] Figure 10 provides a further example of a preferred method 1000 in accordance with aspects of the disclosure herein. The preferred method 1000 is described from the perspective of an application.

[0170] In the preferred method 1000, an end user opens an application on their cellular device in order to, for example, order a taxi. The application detects a lack of Internet meaning the application cannot function as intended i.e., a taxi, for example, cannot be ordered and payment cannot be taken. To avoid missing out on a sale, the application requires an Internet connection as soon as possible. Hence the application presents the user with an option to obtain an Internet connection which may be free or paid for and may have restrictions such as being locked down to the application only, or more widely usable. This may depend on the payment amount, or a data allowance (which may be usable for other services as well such as social media, email). Should the user of the cellular device decide to accept the offer of an Internet connection, the application may trigger the method 1000. Cached data may have been cached according to step 801 of Figure 8. A user requirement for an eSIM may have been obtained according to step 802 of Figure 8. Furthermore, the application may have determined a lack of Internet connection according to step 803 of Figure 8.

[0171] In a first step 1001, the application reads from some cached data in the application to decide which eSIM profile it should install for the end user — this may vary depending on several factors such as the option the end user chose above, the location of the end user, and the user classification the application has for the end user.

[0172] In a further step 1002, the application will then take the cached data and call the cellular device’s OS API to trigger an eSIM installation process. Alternatively, the application may take the cached data and present the user with an appropriate means of installing the eSIM (clickable QR code, eSIM URL, etc). The application would pass an Activation Code and SMDP+ URL (from the cached data) to the device’s OS API. This will trigger the eSIM installation process. The cellular device at this point still has no Internet connection. The steps 1001-1002 may correspond to step 804 of Figure 8.

[0173] In a further step 1003, the cellular device OS would detect that the end user is trying to install an eSIM profile, but that no Internet connection is available — therefore the device OS will automatically enable a bootstrap cellular connection which will allow the application triggered eSIM profile to download and install. This step 1003 may correspond to step 805 of Figure 8.

[0174] In a further step 1004, once installed, the cellular device OS will disable the bootstrap profile automatically and enable the eSIM profile installed from the application and it will obtain an Internet connection. The cellular device OS will then pass the ‘context’ (i.e., the screen) back to the application.

[0175] In a further step 1005, the application will detect there is now a valid internet connection and the application will function as normal.

[0176] In a further step 1006, if the user chose an eSIM profile which provides Internet connectivity for other services rather than just the specific application, then these services will also work. The application may also take a payment automatically from the end user’s saved payment details once the cellular device establishes Internet connectivity.

[0177] The disclosure herein further provides a method of provisioning eSIM / iSIM profile details to a cellular device for installing an eSIM profile for use with an application on the cellular device when the cellular device has no active Internet connection. The cellular device has a bootstrap connectivity profile. The method comprises caching, into a memory of the cellular device, eSIM / iSIM profile details comprising an activation code and address for the eSIM / iSIM profile, such that the application can trigger, using the activation code and address cached in the memory of the cellular device, an activation of the bootstrap connectivity profile to provide a temporary Internet connection for obtaining / installing the eSIM / iSIM profile.

[0178] The disclosure herein further provides the use, by an application installed on a cellular device, of a cached activation code and address associated with an eSIM / iSIM profile, to trigger (when the cellular device has no active Internet connection) the activation of a bootstrap connectivity profile of the cellular device to provide a temporary Internet connection for obtaining / installing the eSIM / iSIM profile.

[0179] It should be noted that the above-mentioned methods and apparatus illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims. Any reference signs in the claims shall not be construed so as to limit their scope.

[0180] Further, while examples have been given in the context of particular communications standards, these examples are not intended to be the limit of the communications standards to which the disclosed method and apparatus may be applied. For example, while specific examples have been given in the context of 3GPP, the principles disclosed herein can also be applied to another wireless communications system, and indeed any communications system which uses routing rules.

[0181] The method may also be embodied in a set of instructions, stored on a computer readable medium, which when loaded into a computer processor, Digital Signal Processor (DSP) or similar, causes the processor to carry out the hereinbefore described methods.

[0182] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

[0183] Whilst the examples disclosed herein may refer to an ‘Internet connection’ this will be understood more generally to refer to a cellular data connection or data connectivity to the Internet to enable the download of an eSIM.

[0184] Furthermore, whilst the examples described herein may refer to an application performing the method steps on a cellular device, an OS of the cellular device itself could detect a lack of Internet connection and offer a similar eSIM-based connectivity service to the user of the cellular device as a paid for or free service.

[0185] Whilst the examples described herein may refer to caching eSIM profile details the first time an application is installed, the caching may also occur when the application is first opened, or during updates of the application. There may be several cached sets of eSIM profile details (activation code and address i.e., SM-DP+ URL) with rules determining which eSIM profile details are to be used. There may also be an algorithm to generate the activation code for a valid eSIM profile.

[0186] The methods, apparatuses and systems may use a single cached activation code and SM-DP+ URL cached on an application’s first use. Alternatively, multiple activation codes and SM-DP+ URLs may be cached and used based on one or more rules. Alternatively, the cached activation code / s and SM-DP+ URL / s may be automatically updated. Alternatively, a single unified activation code may be used for a plurality of eSIM profiles with, optionally, dynamic eSIM profile allocation by an SM-DP+ server based on a cellular device’s IP address. Alternatively, activation codes may be generated algorithmically by the application.

[0187] Furthermore, whilst the examples may refer to logic performed by an application, a device OS-integrated rule-based eSIM activation may also be provided by including logic in a cellular device OS to automatically enable an eSIM when specific applications are opened without an Internet connection.

[0188] The methods, apparatuses and systems described herein tend to cache eSIM profile details (activation code and address i.e., SM-DP+ URL) device-side before the device is in the state of having no Internet connection.

[0189] The methods, apparatuses and systems described herein tend to establish Internet connectivity and application usability for a user within 60 seconds.

[0190] The methods, apparatuses and systems described herein tend to provide preemptive caching of eSIM details i.e., caching the eSIM activation code and SMDP+ URL directly on the cellular device before the user encounters a situation without Internet access. This pre-emptive measure tends to ensure that the user can acquire cellular connectivity without needing to seek out Wi-Fi or purchase a local SIM card upon arrival in a new country.

[0191] The methods, apparatuses and systems described herein tend to enable integration with applications i.e., empowering an application (e.g., a taxi ordering application) to solve the lack of Internet connectivity by initiating the installation of the eSIM profile without requiring an initial active Internet connection. This tends to directly benefit both the user, who gains Internet access, and the application provider, who retains the customer's engagement with the service provided by the application.

[0192] The methods, apparatuses and systems described herein tend to provide a new revenue opportunity for applications. The same operational eSIM installed according to the methods described herein tends to be able to be usable to sell actual connectivity packages to the end user via the application (e.g., a taxi ordering application), creating a new revenue-generating product.

[0193] The methods, apparatuses and systems described herein tend to provide user experience enhancement. More specifically the methods tend to enhance the user experience by simplifying connecting to the Internet in situations without Wi-Fi or cellular data. This tends to eliminate the need for manual eSIM installation or searching for alternative connectivity solutions, providing a more streamlined and hassle-free experience all from the cellular device itself.

[0194] The methods, apparatuses and systems described herein tend to improve ease of use. The automated process tends to simplify eSIM installation for users, especially in stressful situations like arriving in a new country without connectivity. The Internet connection is also provided / offered by a trusted brand (e.g. the application service provider) with whom the end user has some brand affiliation.

[0195] The methods, apparatuses and systems described herein tend to provide rapid connectivity. Almost instantaneous Internet connectivity tends to be provided when needed, thereby tending to prevent the user from being disconnected at any point.

[0196] The methods, apparatuses and systems described herein tend to provide costeffectiveness. More specifically, the methods tend to save the user money by avoiding expensive roaming charges or the purchase of local SIM cards.

[0197] The methods, apparatuses and systems described herein tend to provide for retention of engagement. For application providers, the methods tend to ensure that users remain connected to their services, which can be critical for applications dependent on constant connectivity.

[0198] The methods, apparatuses and systems described herein tend to provide for broad compatibility. This methods tend to be designed to be implemented within applications and potentially device operating systems, so tend to have the potential for wide-ranging compatibility across different platforms and cellular devices.

[0199] Overall, the methods, apparatuses and systems described herein tend to combine caching the eSIM profile details, integration with applications for immediate connectivity 5 needs, and device bootstrap connections, for eSIM installations that tend to have far superior user experience than what is presently available.

Claims

1. A computer-implemented method of installing an embedded or integrated subscriber identity module ‘eSIM / iSIM’ profile onto a cellular device, the cellular device having a bootstrap connectivity profile, the method comprising:caching, into a memory of the cellular device, an activation code and address for the eSIM / iSIM profile;determining a requirement for use of the eSIM / iSIM profile;determining that the cellular device lacks an active Internet connection;triggering, using the activation code and address cached in the memory of the cellular device, an activation of the bootstrap connectivity profile to provide a temporary Internet connection for obtaining the eSIM / iSIM profile; andinstalling via the temporary Internet connection, using the activation code and address cached in the memory of the cellular device, the eSIM / iSIM profile onto the cellular device;wherein the caching comprises:caching the activation code and address with an application when the application is installed or opened for the first time on the cellular device; and / orcaching the activation code and address with an application when the application is updated on the cellular device.

2. The computer-implemented method of any preceding claim, wherein the caching comprises:caching a single unified activation code for a plurality of eSIM / iSIM profiles.

3. The computer-implemented method of any preceding claim, wherein the caching comprises:caching a plurality of activation codes and addresses for respective eSIM / iSIM profiles; andcaching one or more rules for selecting an activation code and address from the plurality of activation codes and addresses.

4. The computer-implemented method of any preceding claim, wherein the caching comprises:caching an algorithm for generating the activation code.

5. The computer-implemented method of any preceding claim, wherein the triggering the activation of the bootstrap connectivity profile comprises:passing the activation code and address to an application programming interface ‘API’, optionally an API of an operating system ‘OS’ of the cellular device.

6. The computer-implemented method of any preceding claim, wherein the method further comprises:establishing an Internet connection using the eSIM / iSIM profile.

7. The computer-implemented method of claim 6, wherein the method further comprises:triggering a payment transaction for the Internet connection.

8. The computer-implemented method of any preceding claim, wherein the cellular device is a cellular device selected from the list of cellular devices consisting of:a smartphone;a tablet;a cellular enabled laptop; andan Internet of Things ‘IoT’ device.

9. The computer-implemented method of any preceding claim, wherein the determining the requirement for use of the eSIM / iSIM profile comprises:outputting, via a user interface of the cellular device, a first message to a user of the cellular device, wherein the first message comprises one or more user-selectable options for providing an Internet connection for the cellular device;receiving, via the user interface of the cellular device, a first response comprising a selected one of the one or more user-selectable options; anddetermining the requirement for use of the eSIM / iSIM profile based at least partly on the selected one of the user-selectable options.

10. The computer-implemented method of claim 9, wherein the one or more user-selectable options comprise:a payment-free Internet connection;a payment-free Internet connection with one or more restrictions, optionally restricted to a specific application;a payment-based Internet connection; anda payment-based Internet connection with one or more restrictions, optionally restricted to a specific application.

11. The computer-implemented method of any preceding claim, wherein the determining a user requirement for use of the eSIM / iSIM profile comprises determining:a location of a user of the cellular device; and / ora classification of a user of the cellular device or an application on the cellular device.

12. The computer-implemented method of any preceding claim, wherein the address is a Subscription Manager Data Preparation Plus ‘SM-DP+’ address.

13. The computer-implemented method of any preceding claim wherein the method is performed by at least one of:an application for a smartphone;an application for a tablet;an application for a cellular enabled laptop;an application for an loT device; and an OS of the cellular device.

14. A computer program comprising instructions which when executed by a processor of a cellular device, causes the cellular device to perform the method of any preceding claim.

15. The computer program of claim 14, wherein the computer program is a computer program selected from the list of computer programs consisting of:an application for a smartphone;an application for a tablet;an application for a cellular enabled laptop;an application for an loT device; andan OS for a cellular device.

16. A non-transitory computer readable medium comprising the computer program of any one of claims 14-15.

517. A cellular device comprising:at least one memory; andat least one processor;wherein the at least one memory comprises computer-readable instructions, 10 which when executed by the at least one processor, causes the cellular device to perform the method of any one of claims 1-13.

Images