Content for TR 32.851 Word version: 12.2.0
2 References
3 Definitions and abbreviations
4 Operational scenarios for network sharing
5 Recommendation on OAM impacts for Network sharing
6 System description (system roles)
$ Change History
2 References p. 7
3 Definitions and abbreviations p. 7
3.1 Definitions p. 7
3.2 Abbreviations p. 8
4 Operational scenarios for network sharing p. 10
4.1 Scenario 1: Multiple Operators Core Network sharing common radio access network p. 10
4.1.1 General description p. 10
4.1.2 Use case description p. 11
4.1.2.1 Scenario 1A: Shared node managed by Master Operator p. 11
4.1.2.2 Scenario 1B: S-RAN managed by Master Operator (3GPP defined) p. 12
4.1.2.3 Scenario 1C: Master Operator manages all RAN p. 13
4.1.2.4 Scenario 1D: Master Operator manages all RAN (3GPP defined) p. 14
4.1.2.5 Scenario 1E: Network sharing between operators who own independent equipment and no DM/NM sharing p. 15
4.1.3 Fault Management impact p. 16
4.1.4 Performance Management impact p. 16
4.1.5 Configuration Management impact p. 16
4.1.6 Security Management impact p. 16
4.1.7 MDT/Call Trace impact p. 17
4.1.7.1 UE Selection in Area based MDT p. 17
4.1.7.2 UE Selection and Data Retrieval in MDT p. 17
4.1.7.3 Rel-11 solution p. 20
4.1.8 Impact on management of SON and related topics p. 21
4.1.9 Architectural impact p. 21
4.1.10 Other impacts p. 21
4.2 Scenario 2: Relay Node (RN) in a RAN sharing scenario p. 22
4.2.1 General description p. 22
4.2.2 Use case description p. 22
4.2.3 Fault Management impact p. 22
4.2.4 Performance Management impact p. 22
4.2.5 Configuration Management impact p. 23
4.2.6 Security Management impact p. 23
4.2.7 MDT/Call Trace impact p. 23
4.2.8 Impact on management of SON and related topics p. 23
4.2.9 Other Impacts p. 23
4.3 Scenario 3: DM shared between Operators affiliates p. 24
4.3.1 General description p. 24
4.3.2 Use case description p. 24
4.3.3 Fault Management impact p. 24
4.3.4 Performance Management impact p. 24
4.3.5 Configuration Management impact p. 25
4.3.6 Security Management impact p. 25
4.3.7 MDT/Call Trace impact p. 25
4.3.8 Impact on management of SON and related topics p. 25
4.3.9 Other impacts p. 25
4.4 Scenario 4: Gateway Core Network (GWCN) p. 26
4.4.1 General description p. 26
4.4.2 Use case description p. 26
4.4.2.1 Scenario 4.4a: Management Model for GWCN (Option #1) p. 26
4.4.2.2 Scenario 4.4b: Management Model for GWCN (Option #2, conformant with 3GPP current management architecture) p. 27
4.4.3 Fault Management impact p. 27
4.4.4 Performance Management impact p. 27
4.4.5 Configuration Management impact p. 27
4.4.6 Security Management impact p. 27
4.4.7 MDT/Call Trace impact p. 28
4.4.8 Impact on management of SON and related topics p. 28
4.4.9 Other impacts p. 28
4.5 Scenario 5: Shared Core with independent RAN p. 29
4.5.1 General description p. 29
4.5.2 Use case description p. 29
4.5.2.1 Scenario 4.5a: Shared Core with independent RANs (Option #1) p. 29
4.5.2.2 Scenario 4.5b: Shared Core with independent RANs (Option #2, conformant with 3GPP current management architecture) p. 30
4.5.3 Fault Management impact p. 30
4.5.4 Performance Management impact p. 30
4.5.5 Configuration Management impact p. 30
4.5.6 Security Management impact p. 30
4.5.7 MDT/Call Trace impact p. 30
4.5.8 Impact on management of SON and related topics p. 30
4.5.9 Other Impacts p. 30
5 Recommendation on OAM impacts for Network sharing p. 32
5.1 Summary and way forward p. 32
5.2 Scenario 2 related changes p. 32
5.3 Impact on existing specifications p. 32
5.4 Need for new specifications p. 39
5.5 Need LS p. 39
6 System description (system roles) p. 39
$ Change History p. 41
