Device Change-Procedure


Start Conditions:
• The Service Provider has provided to the SM-DP+ the relevant information and configuration for the Device Change (see Annex O).
• The End User has an old Device containing a Profile.
• The eUICC and the LPAd of the old Device support Device Change.
• The Profile on the old Device contains a Device Change Configuration with the information as provided by the Service Provider.
• None of the Profile Policy Rules is set for the Profile with a Device Change Configuration.
• The End User gets a new Device
• User Intent is acquired as defined in SGP.21 [4] in the old Device.Procedure:1. The End User initiates the Device Change operation from the LPAd of the old Device and selects the Profile to be installed in their new Device.
2. The LPAd of the old Device retrieves the DeviceChangeConfiguration from the Profile Metadata of the selected Profile. The LPAd of the old Device SHALL check the
retrieved DeviceChangeConfiguration and proceed based upon its value as follows:• If the DeviceChangeConfiguration indicates requestToDp, the procedure continues with step (3).• If the DeviceChangeConfiguration indicates usingStoredAc, the procedure continues with step (17).3. The LPAd of the old Device SHALL determine the SM-DP+ address from smdpAddressForDc in DeviceChangeConfiguration of the Profile.
4. If the DeviceChangeConfiguration indicates any of the EID and/or TAC of the new Device is required, the LPAd of the old Device SHALL retrieve the required information from the new Device. The detailed interface and mechanism to retrieve the required information is out of scope of the specification.If the DeviceChangeConfiguration indicates that any of the EID and/or TAC of the new Device is required but the LPAd of the old Device cannot retrieve the required information, the LPAd SHALL display an appropriate error state to the End User and stop the procedure.NOTE: For instance, the LPAd of the old Device can guide the End User to use "Show EID" menu of the LPAd of the new Device, and then provide a means to scan/input the EID in a QR code format or human-readable text format.5. The LPAd of the old Device initiates the Common Mutual Authentication procedure defined in section 3.0.1 to the retrieved SM-DP+ address. During the Common Mutual
Authentication procedure, if the DeviceChangeConfiguration includes an allowed eSIM CA RootCA public key identifier, the LPAd SHALL restrict the allowed eSIM CA RootCA public key identifiers to that value.
During the Common Mutual Authentication procedure at step (10), the LPAd SHALL build the ctxParams1 data object with ctxParamsForDeviceChange comprising
the ICCID of the selected Profile and, if indicated as required in DeviceChangeConfiguration, any of the EID and/or TAC of the new Device.6. If configured by the Service Provider, the SM-DP+ SHALL call ES2+.HandleDeviceChangeRequest function comprising the ICCID and, if present in the ctxParamsForDeviceChange data object, the EID and/or TAC of the new Device. The Service Provider SHALL provide isNewProfileRequired and optionally
a Service Provider Message for Device Change in the response of ES2+.HandleDeviceChangeRequest function.
If it is required for the End User to enter a Confirmation Code in order to proceed with the Device Change of the Profile, the Service Provider SHALL provide the value of the Confirmation Code in the response of ES2+.HandleDeviceChangeRequest function.7. If the SM-DP+ does not support Device Change, the SM-DP+ SHALL return an error status "Device Change – Unsupported" and the procedure SHALL stop. If the Device Change is not allowed for the Profile identified by the ICCID, the SM-DP+ SHALL return an error status "Device Change – Not Allowed" and the procedure SHALL stop.If the LPAd of the old Device receives any error status, the LPAd of the old Device MAY display an appropriate error state to the End User and SHALL stop the procedure.NOTE: This provides compatibility with SM-DP+ that does not understand or cannot appropriately process the Device Change request (e.g., v3 SMDP+ not supporting the Device Change feature or v2 SM-DP+).
NOTE: If the procedure stopped due to an error, the LPAd MAY send "ES10b.CancelSession" to the eUICC with a reason sessionAborted8. If configured by the Service Provider, the SM-DP+ SHALL notify the Service Provider of the Device Change request by calling ES2+.HandleNotification function.
9. If the Device Change is allowed for the Profile identified by the ICCID, the SM-DP+ returns ES9+.AuthenticateClient response comprising transactionId, smdpSigned4, smdpSignature4 and optionally Service Provider Message for Device Change.
10. If isNewProfileRequired was set to TRUE in the response to ES2+.HandleDeviceChangeRequest function and/or if there is an agreed behaviour between the Service Provider and the SM-DP+ on the Profile identified by the ICCID, the Service Provider SHALL run the Download Preparation Process, as defined in 3.1.1.2 and optionally the Subscription Activation Process, as defined in 3.1.1.4.NOTE: This process can be performed in parallel to steps 6 to 19. The Profile identified by the ICCID has to be in 'Released' state before step 20.11. The LPAd of the old Device SHALL ask for the Strong Confirmation on the Device Change. If Service Provider Message for Device Change was provided in the ES9+.AuthenticateClient response, it SHOULD be presented to the End User.If ccRequiredFlag is set to TRUE in smdpSigned4, the LPAd of the old Device SHALL ask for the End User to enter the Confirmation Code which was provided by the Operator that MAY be considered as a Strong Confirmation. The Confirmation Requests described above MAY:• display profileName or any relevant information contained in the Profile Metadata and smdpSigned4 to the End User.• be combined, if prompted, into a single prompt with the highest Confirmation Level therefore requiring a single confirmation by the End User.If the End User does not confirm the Device Change of the Profile, the LPAd SHALL continue with the Common Cancel Session procedure with reason code 'endUserRejection'. If the End User does not respond to the LPAd prompt within an implementation-dependent timeout interval, the LPAd SHALL cancel the Profile download by performing the Common Cancel Session procedure with the reason 'timeout'. For both cases, the notificationEvent SHALL be set to 'Device Change confirmation failure' if a notification is sent to the Service Provider.12. The LPA of the old Device SHALL call the "ES10b.PrepareDeviceChange" function including the smdpSigned4, smdpSignature4 and optionally the Hashed Confirmation Code. The Hashed Confirmation Code SHALL be calculated with the UTF-8-encoded representation of the Confirmation Code as follows:Hashed Confirmation Code = SHA256 (SHA256(Confirmation Code) | TransactionID), where '|' means concatenation of data13. The LPAd of the old Device SHALL call ES9+.ConfirmDeviceChange function comprising transactionId, prepareDeviceChangeResponse.
14. If configured by the Service Provider or if isNewProfileRequired was set to TRUE in the response to ES2+.HandleDeviceChangeRequest function, the SM-DP+ SHALL notify the Service Provider of the End User's confirmation result by calling ES2+.HandleNotification function. If the End User accepted the Device Change, the procedure continues with the next step. Otherwise, the procedure continues with step (16). 15. If isNewProfileRequired was set to FALSE in the response to ES2+.HandleDeviceChangeRequest function or if configured by the Service Provider, the SM-DP+ SHALL prepare a Profile for download and the associated MatchingID. If an EID was provided in the Device Change Request in the step 5, the SM-DP+ SHALL link the prepared Profile download with the EID. The SM-DP+ SHALL determine the deletion of the Profile on the old Device as per Service Provider's configuration and SHALL generate the associated Activation Code. If the Activation Code is to be encrypted as per section 5.6.6, the SM-DP+ SHALL use a MatchingID that has not previously been used in the Activation Code. The SM-DP+ SHALL notify the Service Provider of the Profile preparation result by calling ES2+.HandleNotification function if configured by the Service Provider. 16. If the End User accepted the Device Change, the SM-DP+ SHALL return the ES9+.ConfirmDeviceChange response comprising the Device Change response. Upon receiving the response, the LPAd of the old Device SHOULD disable the installed Profile if the response contains encryptedDeviceChangeData, and SHALL call "ES10b.VerifyDeviceChange" function comprising deviceChangeConfirmation to verify the SM-DP+ signature and optionally decrypt the Device Change Response via eUICC as described in section 5.7.27. If the eUICC returns a profileNotInDisabledState error, the LPA MAY disable the installed Profile and retry the "ES10b.VerifyDeviceChange" function call. If the eUICC returns any other error or the LPA does not retry the "ES10b.VerifyDeviceChange" function call, the procedure SHALL stop. If the End User rejected the Device Change, the SM-DP+ SHALL return the ES9+.ConfirmDeviceChange response without the Device Change response, and the procedure SHALL stop. NOTE 1: The use of an SM-DS in the context of Device Change is FFS.NOTE 2: If the LPA does not retry the "ES10b.VerifyDeviceChange" function call, the LPA can terminate the RSP session by calling "ES10b.CancelSession" with the reason sessionAborted. 17. If the LPAd of the old Device has been instructed in the Device Change Response to delete the installed Profile or the DeviceChangeConfiguration indicates that the deletion of the installed profile is required, the LPAd of the old Device SHALL delete the installed Profile from the eUICC using ES10c.DeleteProfile and retrieve the corresponding Delete Notification from the eUICC. Additionally, if the DeviceChangeConfiguration indicates requestToDp and the SM-DP+ has indicated in the Device Change Response that it supports the recovery of the deleted Profile, the LPAd of the old Device SHOULD store the following values of the deleted Profile: • ICCID, and• from DeviceChangeConfiguration: the smdpAddressForDc and, if present, the allowedCiPKId.If the deletion of the installed Profile is not required, the procedure continues with step (19).
NOTE: The LPA of the old Device should store the Profile Recovery Information until the expiration of time indicated in profileRecoveryValidityPeriod in the deviceChangeResponse or successful Profile Recovery, whichever comes first. 18. The LPAd of the old Device SHALL send the Delete Notification of the deleted Profile to the corresponding Recipient Address. For that, the LPAd MAY perform one of the following: • The LPAd MAY call ES9+.HandleNotification function (as defined in section 3.5) and receive the acknowledgement of the Delete Notification.• The LPAd MAY send the Delete Notification to the LPAd of the new Device via implementation-specific channel. In this case the LPAd of the new Device SHALL relay the Delete Notification by calling ES9+.HandleNotification function (as defined in section 3.5) before executing step (20).• If the SM-DP+ has indicated that it supports the Delete Notification for Device Change of the deleted Profile in the Device Change Response, the LPAd MAY embed the Delete Notification for Device Change corresponding to the notificationAddress in the Device Change Response in an Activation Code (as defined in section 4.1 and 4.1.3).The procedure SHALL stop if the LPAd of the old Device cannot send the Delete Notification. NOTE1: The Recipient Address may not be the FQDN of the SM-DP+ in figure 21b. In such a case, it is out of scope of this document how the Notification receiver delivers the Delete Notification to the SM-DP+ in figure 21b.
NOTE2: The LPAd of the old Device MAY send additional Notifications to the SMDP+(s) other than the SM-DP+ in figure 21b.
NOTE3: Execution of this step MAY require an extended period of time. For instance, if the LPAd does not presently have network connectivity, it can wait until connectivity is available in order to deliver the notification. 19. The LPAd of the old Device provides the Activation Code to the LPAd of the new Device.• If the DeviceChangeConfiguration indicates requestToDp, the LPAd SHALL use the Activation Code in the ES9+.ConfirmDeviceChange response or the Activation Code at step (18), if generated.• If the DeviceChangeConfiguration indicates usingStoredAc, the LPAd SHALL use the Activation Code from the activationCodeForDc. The LPAd of the old Device SHOULD provide to the new Device the state of the Profile during the procedure in order to allow the LPAd of the new Device to restore the state of the Profile of the old Device.The LPAd of the old Device MAY present the information via the LUI. Additional means to provide the information to the LPAd of the new Device is out of scope of this specification. 20. The Profile is downloaded from the SM-DP+ to the new Device via the Profile download and installation procedure as defined in section 3.1.3, based upon the Activation Code.• If the Activation Code, provided at step (19), contains the Delete Notification for Device Change, the LPAd of the new Device SHALL provide the Delete Notification for Device Change by calling ES9+.AuthenticateClient function comprising a deleteNotificationForDc.• If the Activation Code, provided at step (19), indicates Confirmation Code Required Flag, the Confirmation Code that was used in this procedure has to be used at step (8) of the Profile download and installation procedure defined in section 3.1.3. End Conditions: The Profile and its associated Profile Metadata have been installed on the End User’s eUICC of the new Device.

这是一段关于远程SIM配置（RSP）技术规范中设备变更（Device Change）流程的描述。该流程允许用户将旧设备中的SIM配置文件迁移到新设备中。以下是该流程的核心内容概述：

**启动条件：**
- 服务提供商已向SM-DP+提供了进行设备变更所需的相关信息和配置。
- 用户拥有一个含有配置文件的旧设备。
- 旧设备的eUICC和LPAd支持设备变更。
- 旧设备中的配置文件包含服务提供商提供的信息的设备变更配置。
- 配置文件没有设置任何与设备变更配置相关的配置文件策略规则。
- 用户获得了一个新设备。
- 在旧设备中根据SGP.21 [4]获取了用户意图。

**步骤：**
1. 用户从旧设备的LPAd发起设备变更操作，并选择要安装到新设备的配置文件。
2. 旧设备的LPAd从所选配置文件的配置文件元数据中检索设备变更配置。根据检索到的设备变更配置的值，旧设备的LPAd将按照以下方式进行操作：
   - 如果设备变更配置指示为requestToDp，程序继续执行步骤3。
   - 如果设备变更配置指示为usingStoredAc，程序继续执行步骤17。

3. 旧设备的LPAd将从配置文件的设备变更配置中的smdpAddressForDc确定SM-DP+地址。
4. 如果设备变更配置指示新设备需要EID和/或TAC，旧设备的LPAd将从新设备中检索所需信息。
5. 旧设备的LPAd对检索到的SM-DP+地址启动共同相互认证程序。如果设备变更配置包括允许的eSIM CA RootCA公钥标识符，LPAd将限制允许的eSIM CA RootCA公钥标识符为该值。
6. 如果服务提供商配置了，SM-DP+将调用ES2+.HandleDeviceChangeRequest函数，包括ICCID和新设备的EID和/或TAC。
7. 如果SM-DP+不支持设备变更，将返回错误状态"设备变更 - 不支持"，程序将停止。
8. 如果服务提供商配置了，SM-DP+将通过调用ES2+.HandleNotification函数通知服务提供商设备变更请求。
9. 如果设备变更对于ICCID识别的配置文件是允许的，SM-DP+将返回包含事务ID、smdpSigned4、smdpSignature4的ES9+.AuthenticateClient响应。
10. 如果isNewProfileRequired在ES2+.HandleDeviceChangeRequest函数的响应中被设置为TRUE，或者服务提供商和SM-DP+对于ICCID识别的配置文件有一致的行为，服务提供商将运行下载准备过程。
11. 旧设备的LPAd将要求对设备变更进行强确认。如果ES9+.AuthenticateClient响应中提供了服务提供商消息用于设备变更，应向用户展示。
12. 旧设备的LPAd将调用"ES10b.PrepareDeviceChange"函数，包括smdpSigned4、smdpSignature4和可选的哈希确认代码。
13. 旧设备的LPAd将调用ES9+.ConfirmDeviceChange函数，包括事务ID和prepareDeviceChangeResponse。
14. 如果服务提供商配置了或isNewProfileRequired在ES2+.HandleDeviceChangeRequest函数的响应中被设置为TRUE，SM-DP+将通过调用ES2+.HandleNotification函数通知服务提供商用户确认结果。
15. 如果isNewProfileRequired在ES2+.HandleDeviceChangeRequest函数的响应中被设置为FALSE，或者服务提供商配置了，SM-DP+将准备一个配置文件用于下载并生成相关的匹配ID。
16. 如果用户接受了设备变更，SM-DP+将返回包含设备变更响应的ES9+.ConfirmDeviceChange响应。
17. 如果旧设备的LPAd在设备变更响应中被指示删除已安装的配置文件，或者设备变更配置指示需要删除已安装的配置文件，旧设备的LPAd将使用ES10c.DeleteProfile从eUICC中删除已安装的配置文件，并检索相应的删除通知。
18. 旧设备的LPAd将删除通知发送给相应的接收地址。
19. 旧设备的LPAd将向新设备的LPAd提供激活代码。
20. 配置文件从SM-DP+下载到新设备，基于激活代码。

**结束条件：**配置文件及其相关的配置文件元数据已安装在用户新的eUICC上。

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处：http://www.mzph.cn/news/785083.shtml

如若内容造成侵权/违法违规/事实不符，请联系多彩编程网进行投诉反馈email:809451989@qq.com，一经查实，立即删除！

相关文章

python---基础(一)

python---基础(一)

文章目录 前言1.对象的基本组成2.变量和常量2.1.变量的声明2.2.常量_链式赋值_系列解包赋值2.2.1.常量是不是真的常量？2.2.2.链式赋值2.2.3.系列解包赋值 3.内置数据类型_基本算数运算符3.1四种内置数据类型3.2.基本运算符3.3.divmod() 前言 这几年，随着…
阅读更多...
【Python】——变量名的命名规则

【Python】——变量名的命名规则

🎃个人专栏： 🐬 算法设计与分析：算法设计与分析_IT闫的博客-CSDN博客 🐳Java基础：Java基础_IT闫的博客-CSDN博客 🐋c语言：c语言_IT闫的博客-CSDN博客 🐟MySQL&#xff1a…
阅读更多...
【C脚本】计算PCM的DBFS（分贝全尺度）

【C脚本】计算PCM的DBFS（分贝全尺度）

DBFS是分贝全尺度（Decibels Full Scale）的缩写，是一种用于衡量音频信号强度的单位。DBFS是相对于数字音频的最大可能幅度而言的，它的取值范围通常是从0到-∞。在DBFS中，0表示音频信号的最大幅度，-∞表示完全…
阅读更多...
Dijkstra堆优化之蓝桥王国

Dijkstra堆优化之蓝桥王国

Dijkstra堆优化 Dijkstra算法是一种用于解决单源最短路径问题的算法，即从图中的一个顶点出发到所有其他顶点的最短路径。然而，处理大图时，常规的Dijkstra算法可能会遇到性能问题。这就是Dijkstra的堆优化算法派上用场的地方。在堆优化版本中…
阅读更多...
Python 用pygame简简单单实现一个打砖块

Python 用pygame简简单单实现一个打砖块

# -*- coding: utf-8 -*- # # # Copyright (C) 2024 , Inc. All Rights Reserved # # # Time : 2024/3/30 14:34 # Author : 赫凯 # Email : hekaiiii163.com # File : ballgame.py # Software: PyCharm import math import randomimport pygame import sys#…
阅读更多...
（23）3.31 进阶指针

（23）3.31 进阶指针

int main() { //指针数组 int* arr[4]; char* ch[5]; //数组指针 int arr2[5]; int(*pa)[5] &arr2; char* arr3[6]; char* (*p3)[6] &arr3; return 0; } int test(const char* str) { return 0; } int main() { …
阅读更多...
OpenHarmony实战开发-如何使用rating组件实现星级打分功能。

OpenHarmony实战开发-如何使用rating组件实现星级打分功能。

介绍 本篇Codelab将引导开发者使用rating组件实现星级打分功能。 相关概念 rating组件：评分条，可根据用户判断进行打分。 环境搭建 软件要求 DevEco Studio版本：DevEco Studio 3.1 Release及以上版本。OpenHarmony SDK版本：A…
阅读更多...
linux 一些命令

linux 一些命令

文章目录 linux 一些命令fdisk 磁盘分区parted 分区文件系统mkfs 格式化文件系统fsck 修复文件系统 mount 挂载swap 交换分区清除linux缓存df du 命令raid 命令基本原理硬raid 和 软raid案例raid 10 故障修复，重启与卸载 lvm逻辑卷技术LVM的使用方式LVM 常见名词解析…
阅读更多...
Python爬虫详解：原理、常用库与实战案例

Python爬虫详解：原理、常用库与实战案例

前言 前些天发现了一个巨牛的人工智能学习网站，通俗易懂，风趣幽默，忍不住分享一下给大家：https://www.captainbed.cn/z ChatGPT体验地址 文章目录 前言引言：一、爬虫原理1. HTTP请求与响应过程2. 常用爬虫技术 二、P…
阅读更多...
【经典算法】LeetCode1:两数之和(Java/C/Python3实现含注释说明,Easy)

【经典算法】LeetCode1:两数之和(Java/C/Python3实现含注释说明,Easy)

两数之和 题目思路及实现方式一：暴力解法（不推荐）思路代码实现Java版本C语言版本Python3版本 复杂度分析 方式二：哈希表（推荐）思路代码实现Java版本C语言版本Python3版本 复杂度分析 方式三：双指…
阅读更多...
【C++程序员的自我修炼】基础语法篇（二）

【C++程序员的自我修炼】基础语法篇（二）

风力掀天浪打头 只须一笑不须愁 目录 内联函数 概念💞 性质 ⭐ 不建议变量分离 inline的优劣势 inline的局限性 auto关键字 auto的概念💞 auto的使用细则💞 auto不能推导的场景 💞 auto基于范围的for循环💞 指针空值n…
阅读更多...
nginx的安装教程

nginx的安装教程

文章目录 简介nginx安装windows下安装linux下安装 简介 nginx是一个开源的web服务器和反向代理服务器，可以用作负载均衡和HTTP缓存。它处理并发能力是十分强大的，能够经受高负载的考验。 正向代理 Nginx不仅可以做反向代理，实现负载均衡&am…
阅读更多...
简单说清楚什么是SQL Injection？

简单说清楚什么是SQL Injection？

最近看完了《The Pragmatic Programmer: 20th Anniversary Edition, 2nd Edition: Your Journey to Mastery》，在第7章：While You Are Coding的footnotes中，提到了一幅漫画： 这不仅用简单的方式说清楚了什么是SQL Injection&#…
阅读更多...
C语言数据结构易错知识点（6）（快速排序、归并排序、计数排序）

C语言数据结构易错知识点（6）（快速排序、归并排序、计数排序）

快速排序属于交换排序，交换排序还有冒泡排序，这个太简单了，这里就不再讲解。 归并排序和快速排序都是采用分治法实现的排序，理解它们对分支思想的感悟会更深。 计数排序属于非比较排序，在数据集中的情况下可以考虑使…
阅读更多...
百度贝塞尔曲线证码识别代码

百度贝塞尔曲线证码识别代码

一、前言 百度出了如图所示的验证码，需要拖动滑块，与如图所示的曲线轨迹进行重合。经过不断研究，终于解决了这个问题。我把识别代码分享给大家。 下面是使用selenium进行验证的，这样可以看到轨迹滑动的过程，如果需要…
阅读更多...
关于c# 没有显式头文件的优劣分析

关于c# 没有显式头文件的优劣分析

在C#中，没有像C或C中的显式头文件（header files）的概念。在C#中，源代码文件通常包含类、接口、结构和其他类型的定义，这些源文件直接包含在项目中，并且通过命名空间（namespace）来组织…
阅读更多...
Windows11系统缺少相关DLL解决办法

Windows11系统缺少相关DLL解决办法

一.缺少msvcp120.dll 下载Mircrosoft Visual C 2015等系统关键组件 Microsoft Visual C 2015-2022 Redistributable (x86) - 14.34.31931 Installation Error etc.. - Microsoft Q&A 二.缺少python27.dll 重新下载python2.7进行安装(选择Windows x86-64 MSI installer)…
阅读更多...
Mybatis分页原理

Mybatis分页原理

MyBatis在数据库查询中执行分页操作时，通常会使用分页插件来处理。分页插件能够根据数据库的不同，生成适当的分页查询语句，并将查询结果进行分页处理。下面我将解释MyBatis如何进行分页以及分页插件的一般原理。 MyBatis的分页原理&#xff…
阅读更多...
DS2438Z+TR智能电池监测器多场景行业应用解决方案

DS2438Z+TR智能电池监测器多场景行业应用解决方案

DS2438ZT&R智能电池监视器为电池组提供了若干很有价值的功能：可用于标识电池组的唯一序列号；直接数字化的温度传感器省掉了电池组内的热敏电阻；可测量电池电压和电流的A/D转换器；集成电流累积器用于记录进入和流出电池的电流总…
阅读更多...
前端学习＜二＞CSS基础——14-CSS3属性详解：Web字体

前端学习＜二＞CSS基础——14-CSS3属性详解：Web字体

前言 开发人员可以为自已的网页指定特殊的字体（将指定字体提前下载到站点中），无需考虑用户电脑上是否安装了此特殊字体。从此，把特殊字体处理成图片的方式便成为了过去。 支持程度比较好，甚至 IE 低版本的浏览器也能…
阅读更多...
最新文章

Copyright @ 2022~2023