Content for TR 33.859 Word version: 11.1.0
4 General
5 Analysis and design
6 Comparison of proposed Solutions
7 Complexity versus benefit analysis
8 Conclusions
$ Change history
4 General p. 11
4.1 System overview p. 11
4.1.1 Architecture p. 11
4.1.2 Node and terminal types p. 11
4.2 Assumptions and requirements p. 12
4.3 Desired security properties p. 12
4.4 The UTRAN Key Hierarchy p. 13
4.4.1 Proposed solution 1 p. 13
4.4.2 Proposed solution 2 p. 15
4.4.3 Proposed solution 3 p. 16
4.4.4 Freshness options for vertical key derivations p. 17
4.4.5 Handling of START/COUNT-C/COUNT-I p. 19
5 Analysis and design p. 19
5.1 Proposed solution 1 p. 20
5.1.1 General p. 20
5.1.2 Key handling capability negotiation p. 20
5.1.2.1 General p. 20
5.1.2.2 UTRAN KH negotiation in the attach procedure p. 20
5.1.2.3 Capability indication at intra-UTRAN mobility p. 20
5.1.2.4 Capability indication at IRAT mobility p. 21
5.1.3 Signalling procedures p. 21
5.1.3.1 Attach p. 21
5.1.3.2 Context transfers p. 23
5.1.3.2.1 General p. 23
5.1.3.2.2 Inter CNN+ context transfer p. 23
5.1.3.2.3 CNN+ to CNN context transfer p. 23
5.1.3.2.4 CNN to CNN+ context transfer p. 23
5.1.3.2.5 Inter CNN context transfer p. 24
5.1.3.3 SRNS relocation p. 24
5.1.3.3.1 General p. 24
5.1.3.3.2 SRNS relocation with UE involvement p. 24
5.1.3.3.2.1 SRNC relocation key chaining p. 24
5.1.3.3.2.2 Network handling p. 25
5.1.3.3.2.3 Intra-SRNS relocation p. 26
5.1.3.3.3 ME handling p. 26
5.1.3.3.4 SRNS relocation without UE involvement p. 26
5.1.3.3.5 Using Enhanced SRNS Relocation p. 26
5.1.3.4 Idle mode mobility p. 28
5.1.3.5 Inter SGSN(*)/MME AV transfers p. 28
5.1.4 Inter-working with GERAN procedures p. 28
5.1.5 Inter-working with E-UTRAN p. 29
5.1.6 Summary of changes to messages p. 29
5.1.6.1 General p. 29
5.1.6.2 Changes to TS 24.008 p. 29
5.1.6.3 Changes to TS 24.301 p. 30
5.1.6.4 Changes to TS 29.060 p. 30
5.1.6.5 Changes to TS 29.274 p. 30
5.1.6.6 Changes to TS 25.413 p. 31
5.1.6.7 Changes to TS 25.423 p. 31
5.1.6.8 Changes to TS 25.331 p. 31
5.1.6.9 Changes to TS 36.413 p. 32
5.1.6.10 Changes to TS 36.331 p. 32
5.2 Proposed solution 2 p. 32
5.2.1 General p. 32
5.2.2 Overview of the solution p. 33
5.2.3 Proposed PS solution p. 33
5.2.3.1 Intra-UTRAN procedures p. 33
5.2.3.1.1 General p. 33
5.2.3.1.2 AKA p. 33
5.2.3.1.3 Attach, RAU and Service Requests p. 34
5.2.3.1.3.1 Initial message p. 34
5.2.3.1.3.2 Transfer of security context between SGSN p. 34
5.2.3.1.3.3 Security mode command procedure p. 34
5.2.3.1.4 Intra-UTRAN handovers p. 35
5.2.3.2 Inter-working with GERAN procedures p. 35
5.2.3.2.1 General p. 35
5.2.3.2.2 AKA p. 35
5.2.3.2.3 Attach, RAU and Service Requests p. 35
5.2.3.2.4 Handovers p. 36
5.2.3.3 Inter-working with E-UTRAN procedures p. 36
5.2.3.3.1 General p. 36
5.2.3.3.2 EPS AKA p. 36
5.2.3.3.3 Idle mobility p. 36
5.2.3.3.3.1 Attach and TAU procedures in EPS p. 36
5.2.3.3.3.2 Attach and RAU procedures in UTRAN/GERAN when TIN = 'GUTI' p. 37
5.2.3.3.4 Handovers p. 37
5.2.3.3.4.1 Intra-E-UTRAN S1 handovers p. 37
5.2.3.3.4.2 Handovers from E-UTRAN to UTRAN/GERAN p. 37
5.2.3.3.4.3 Handover from GERAN/UTRAN to E-UTRAN p. 37
5.2.3.3.5 Analysis of the benefits of inter-working with E-UTRAN p. 37
5.2.3.4 Summary of changes to messages for PS p. 38
5.2.4 CS related procedures p. 40
5.2.4.1 Intra-UTRAN procedures p. 40
5.2.4.1.1 General p. 40
5.2.4.1.2 AKA p. 40
5.2.4.1.3 Initial message and subsequent procedures p. 40
5.2.4.1.3.1 Initial message p. 40
5.2.4.1.3.2 Transfer of security context between MSCs p. 40
5.2.4.1.3.3 Security mode command procedure p. 41
5.2.4.1.4 Intra-UTRAN handovers p. 41
5.2.4.2 GERAN interworking procedures p. 41
5.2.4.3 Summary of changes to messages for CS domain p. 41
5.2.4.3.1 General p. 41
5.2.4.3.2 Changes to TS 24.008 p. 41
5.2.4.3.3 Changes to TS 44.018 p. 42
5.2.4.3.4 Changes to TS 29.002 p. 42
5.3 Proposed solution 3 p. 42
5.3.1 General p. 42
5.3.2 Key handling and capability negotiation p. 42
5.3.2.1 General p. 42
5.3.2.2 Initial NAS procedures p. 43
5.3.2.3 Key derivations and capability indication at intra-UTRAN mobility with SRNS relocation p. 43
5.3.2.4 Capability indication at IRAT mobility p. 47
5.3.3 Summary of changes to messages p. 47
5.4 Proposed solution 4 p. 48
5.4.1 General p. 48
5.4.2 Forward security based SRNS relocation with UE involvement p. 49
5.4.2.1 Key chaining p. 49
5.4.2.2 Network handling p. 49
5.4.2.3 ME handling p. 50
5.4.2.4 Intra-SRNS relocation p. 51
5.4.3 SRNS relocation without UE involvement p. 51
5.4.4 Interworking with GERAN p. 51
5.4.4a Interworking with E-UTRAN p. 51
5.4.5 Summary of changes to messages p. 51
5.4.5.1 General p. 51
5.4.5.2 Changes to TS 24.008 p. 51
5.4.5.3 Changes to TS 29.060 p. 52
5.4.5.4 Changes to TS 25.413 p. 52
5.4.5.5 Changes to TS 25.331 p. 53
6 Comparison of proposed Solutions p. 53
6.1 Signalling aspects p. 53
6.1.1 Initial authentication / AV fetch p. 53
6.1.2 Idle to Active transition p. 53
6.1.3 SRNS relocation and intra-UTRAN key-refresh p. 53
6.2 Compatibility aspects p. 54
6.3 Security p. 55
6.3.1 Threats p. 55
6.3.1.1 Handover from a collapsed RNC and NodeB p. 55
6.3.1.2 Handover from a separated RNC and NodeB p. 55
6.3.2 Forward security analysis p. 56
6.4 Messages comparisons p. 57
7 Complexity versus benefit analysis p. 61
7.1 Threats, use cases and protection level p. 61
7.1.1 Use case: temporarily stationary user p. 61
7.1.2 Use case: mobile users p. 62
7.1.2.1 Description p. 62
7.1.2.2 Attacker behaviour p. 62
7.1.2.3 Countermeasures p. 62
7.1.2.4 Conclusion p. 62
7.1.3 Theft of service p. 63
7.1.3.1 Threat p. 63
7.1.3.2 Analysis p. 63
7.1.4 CN and RAN level key separation p. 63
7.2 Cost and complexity analysis p. 64
8 Conclusions p. 64
$ Change history p. 67
