You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.163.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 17:28, 10 March 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.163.179.242. The blocked range is 54.163.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((more citations needed|date=June 2016))

'''Remote SIM provisioning''' is a specification realized by [[GSMA]] that allows consumers to remotely activate the [[subscriber identity module]] (SIM) embedded in a portable device such as a [[smart phone]], [[smart watch]], [[fitness band]] or [[tablet computer]].<ref>((Cite web|last=|first=|date=|title=eSIM — Что это и как подключить в России|url=https://droidblog.org/help/esim-russia|access-date=2020-09-22|website=|language=ru-RU))</ref><ref>GSMA releases remote provisioning specification to help consumers connect mobile devices  http://www.gsma.com/rsp/</ref> The specification was originally part of the GSMA's work on [[eSIM]]<ref>((Cite web|url=https://www.gsma.com/esim/|title=The SIM for the next Generation of Connected Consumer Devices - eSIM|website=eSIM|language=en-GB|access-date=2018-03-01))</ref> and it is important to note that remote SIM provisioning is just one of the aspects that this eSIM specification includes. The other aspects being that the SIM is now structured into "domains" that separate the operator profile from the security and application "domains". In practise "eSIM upgrade" in the form of a normal SIM card<ref>((Cite web |title=eSIM.me Store |url=https://esim.me/ |access-date=2022-05-28 |website=esim.me |language=en))</ref> is possible (using the Android 9 eSIM APIs) or eSIM can be included into an [[System on a chip|SOC]].<ref>((Cite web |title=Vodafone, Qualcomm Technologies, and Thales Deliver World-First Smartphone Demonstration of Integrated SIM (iSIM) Technology ((!)) Qualcomm |url=https://www.qualcomm.com/news/releases/2022/01/vodafone-qualcomm-technologies-and-thales-deliver-world-first-smartphone |access-date=2022-05-28 |website=www.qualcomm.com |language=en))</ref> The requirement of GSMA certification is that personalisation packet is decoded inside the chip and so there is no way to dump Ki, OPc and 5G keys. Another important aspect is that the eSIM is owned by the enterprise((Clarification needed|reason=Not clear which "enterprise" is referenced here|date=February 2022)), and this means that the enterprise now has full control of the security and applications in the eSIM, and which operators profiles are to be used.

== Background to the specification ==

In the background of the technology looked to address the following issues:
* The development of non-removable SIM technology - a new generation of SIM-cards like [[MFF (SIM)|MFF]] which are soldered into the device.
* The appearance and support by mobile operators of the concept of ABC (always best connected) – the opportunity get quality connections from any mobile operator at any point in time.
* The explosive growth of the [[Internet of things|Internet of Things]] (IoT) - according to Gartner about 8.4 billion connections in 2017 (up 31% from 2016).<ref>((Cite news|url=https://www.gartner.com/en/newsroom/press-releases/2017-02-07-gartner-says-8-billion-connected-things-will-be-in-use-in-2017-up-31-percent-from-2016|title=Gartner Says 8.4 Billion Connected|access-date=2018-03-01|language=en))</ref>
* The cost and effort required to swap a SIM in a device that has been deployed in the field.

== Origin ==

The GSM Association ([[GSMA]]) which brings together about 800 operators and 250 mobile ecosystem companies became the first to come up with the Consumer Remote SIM Provisioning initiative. The beginning of creation the technology was announced in the summer 2014. The complete version of the specification was realized in February, 2016.
Initially, the specification was supposed to be used just by [[Machine to machine|M2M]] devices, but since December, 2015 it has begun being spread over various custom wearable devices, and into enterprise applications like authentication and identity management.<ref>((Cite news|url=https://www.btg.org/2016/06/14/btg-e-sim-project-next-phase/|title=BTG E-SIM project enters next phase - BTG|date=2016-06-14|work=BTG|access-date=2018-03-01|language=nl-NL))</ref>
<blockquote>"This new specification gives consumers the freedom to remotely connect devices, such as wearables, to a mobile network of their choice and continues to evolve the process of connecting new and innovative devices," ''Alex Sinclair, Chief Technology Officer, GSMA.''<ref>((Cite web|url=https://www.gsma.com/newsroom/press-release/gsma-releases-remote-provisioning-specification/|title=GSMA Remote Provisioning Release))</ref></blockquote>
Besides, the right of independent service providers to transmit commands of loading profiles to SIM-cards in the device has been amended and the possibility to store arrays of profiles in independent certified data centers (Subscriptions manager) has appeared.

== Functions and benefits ==

The specification that covers the carrier selection aspects aims to allow consumers to choose a mobile network operator from a wide range to activate the SIM embedded in a device via a subscription. It aims to simplify the users’ life by connecting their multiple devices through the same subscription. It should also motivate mobile device manufacturers to develop the next generation of the mobile-connected devices that will suit better the [[wearable technology]] applications. The specification that covers the carrier selection for M2M devices is simpler since typically there is no subscriber involved (e.g. changing the operator in an electricity meter).

The language that is used to describe these specification is a little confusing since eSIM is not a physical format (or "form factor" - the phrase that is used to describe the various SIM sizes). The eSIM describes the functionality in the SIM, not the physical size of the SIM - and there are eSIMs in many formats (2FF, 3FF, 4FF, MFF).

GSMA have also developed a compliance framework<ref>((Cite web|url=https://www.gsma.com/esim/guide-rsp-compliance-process/|title=GSMA eSIM Compliance Process))</ref> for eSIM devices, eUICCs, and subscription management products - to help with interoperability and security for products supporting eSIM. This is published by the GSMA as SGP.24,<ref>((Cite web|url=https://www.gsma.com/newsroom/all-documents/sgp-24-rsp-compliance-process/|title=GSMA SGP 24))</ref> the eSIM compliance process describes common compliance requirements for:

* Functional interoperability
* eUICC security
* eUICC production site security
* Subscription Management site security

== Operation ==
Remote provisioning on the host device is initiated by the Local Profile Assistant (LPA), a software package that follows the RSP specification.

When the LPA wants to retrieve a carrier profile it contacts a subscription manager (SM) service on the internet via [[HTTPS]]. The address of the SM can be defined:

* in a [[QR code]] scanned by the user
* by manually entering the SM's [[Name resolution (computer systems)|host name]]/Activation code on screen
* [[Hard-coded|hard coded]] by the host device manufacturer in firmware.
* via a universal discovery service operated by the GSMA.

The LPA is responsible for validating the [[X.509 certificate]] of the SM is valid and issued by the GSMA [[certificate authority]].<ref>((Cite web|title=GSMA Certificate Issuer (CI)|url=https://www.gsma.com/esim/gsma-root-ci/|access-date=2022-01-22|website=eSIM|language=en-US))</ref> Once validation is complete the LPA will coordinate a secure channel between the eUICC and the SM using [[Challenge–response authentication|challenge-response authentication]] to enter programming mode. The LPA will request carrier profiles available for download, either by submitting the activation code provided by the user or the eSIM ID (EID) of the eUICC. The SM will provide the requested profile encrypted in a way that only the eUICC can decrypt/install to ensure the network authentication key remains secure.  

== References ==
((Reflist))

[[Category:Mobile phone standards]]
[[Category:Computer access control protocols]]

Pages transcluded onto the current version of this page (help):

Remote SIM provisioning (edit)
Template:Ambox (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Cite news (view source) (protected)
Template:Cite web (view source) (protected)
Template:Clarification needed (view source) (semi-protected)
Template:Clarify (view source) (template editor protected)
Template:Delink (view source) (template editor protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix-span (view source) (template editor protected)
Template:Fix/category (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:DecodeEncode (view source) (template editor protected)
Module:Delink (view source) (template editor protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Remote SIM provisioning.

Retrieved from "https://en.wikipedia.org/wiki/Remote_SIM_provisioning"