Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 33.812 Word version: 9.2.0

0… 4… 6…

4 Use cases and requirements p. 10

4.1 Use cases p. 10

4.2 Use case analysis p. 10

4.3 Requirements p. 12

4.3.1 Security requirements p. 12

4.3.2 Other Requirements p. 14

4.4 Evaluation criteria p. 14

5 Candidate solutions p. 15

5.1 Alternative 1a: TRE based solution with remote subscription provisioning and change p. 15

5.1.1 MCIM p. 15

5.1.1.1 Lifecycle of MCIMs p. 15

5.1.1.2 Contents of a Typical Downloadable MCIM p. 16

5.1.2 Trusted Environment (TRE) p. 16

5.1.2.1 Notes p. 16

5.1.2.2 General Functions of a TRE p. 16

5.1.2.3 TRE Functions Related to the Management of MCIMs p. 17

5.1.2.4 TRE Functions Related to the Remote Provisioning of MCIMs p. 18

5.1.3 Network architecture p. 19

5.1.3.1 Introduction p. 19

5.1.3.2 Principles of the Network Architecture p. 19

5.1.3.3 Services p. 19

5.1.3.3.1 Summary p. 19

5.1.3.3.2 Connectivity Services p. 20

5.1.3.3.2.1 Initial Network Connectivity Service p. 20

5.1.3.3.2.2 Operational Connectivity p. 21

5.1.3.3.3 Application Services p. 21

5.1.3.3.3.1 Discovery and Registration Service p. 21

5.1.3.3.3.2 MCIM Download and Provisioning Service p. 21

5.1.3.3.4 M2ME Supply Services p. 21

5.1.3.4 Technical Functions (in alphabetical order) p. 21

5.1.3.4.1 Connectivity Credential Issuing Function (CCIF) p. 21

5.1.3.4.2 Discovery and Registration Function (DRF) p. 22

5.1.3.4.3 MCIM Download and Provisioning Function (DPF) p. 22

5.1.3.4.4 Initial Connectivity Function (ICF) p. 22

5.1.3.5 Roles p. 23

5.1.3.5.1 Summary p. 23

5.1.3.5.2 M2ME Subscriber p. 23

5.1.3.5.3 M2M Equipment Supplier (M2MES) p. 23

5.1.3.5.4 Registration Operator p. 24

5.1.3.5.5 3GPP Visited Network Operator (VNO) p. 24

5.1.3.5.6 3GPP Selected Home Operator (SHO) p. 24

5.1.3.5.7 Non-3GPP Initial Connectivity Service Provider p. 24

5.1.3.5.8 Platform Validation Authority (PVA) p. 24

5.1.3.5.9 Regulator p. 25

5.1.3.6 Network Interactions for Remote Provisioning p. 25

5.1.3.6.1 General p. 25

5.1.3.6.2 Overview of network architecture p. 25

5.1.3.6.3 Network Interactions for MCIM Provisioning in case of 3GPP Access p. 26

5.1.3.6.4 Network Interactions for MCIM Provisioning in case of Non-3GPP Access p. 29

5.1.3.7 How to change to a new operator p. 29

5.1.3.7.1 General p. 29

5.1.3.7.2 Design principles p. 29

5.1.3.7.4 Network architecture support for operator change p. 29

5.1.3.7.4.1 General p. 29

5.1.3.7.4.2 Re-provisioning using connectivity provided by old SHO p. 29

5.1.3.7.4.3 Reverting to the pristine state p. 32

5.2 Alternative 2: UICC based solution with no remote subscription provisioning and change p. 32

5.2.1 General p. 32

5.2.2 Initial provision of a new M2M equipment with a new USIM application from an operator of M2M subscriber's choice p. 33

5.2.3 Changing subscription to a different operator p. 33

5.2.4 Cloning prevention p. 34

5.2.5 Unauthorized removal and reuse of a UICC from the M2ME p. 34

5.2.5.1 Physical protection p. 34

5.2.5.2 Logical protection p. 34

5.2.5.3 Network protection p. 35

5.3 Alternative 3: UICC based solution with remote subscription change p. 35

5.3.1 Alternative 3a: IMSI change and key transfer between operators p. 35

5.3.1.1 General p. 35

5.3.1.2 Principles p. 35

5.3.1.3 Requirements p. 36

5.3.2 Alternative 3b: IMSI change and pre-configured key list on UICC p. 37

5.3.2.1 General p. 37

5.3.2.2 Principles p. 37

5.3.2.3 Requirements and scheme variants p. 39

5.3.3 Requirements for removable UICC-based solution p. 39

5.3.3.1 Initial provisioning of a new M2ME with a new USIM application from an operator of the M2M subscriber's choice p. 39

5.3.3.2 Cloning prevention p. 40

5.3.3.3 Prevention from unauthorized removal of a UICC from the M2ME p. 40