tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top        in Index        Prev        Next

TR 22.852 (SA1)
Study on Radio Access Network (RAN) sharing enhancements

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V13.1.0    2014/09    34 p.
(W-zip) V12.0.0    2013/06    29 p.


Rapporteur:  Dr. Swetina, Joerg
See also:  Network-Sharing-related TS/TR    


This TR provides a study on scenarios of multiple operators sharing radio network resources and creates potential requirements that complement existing system capabilities for sharing common E-UTRAN resources.

The scenarios illustrate e.g.:
  • Means for efficiently sharing common E-UTRAN resources according to identified RAN sharing scenarios (e.g. pooling of unallocated radio resources).
  • Means to verify that the shared network elements provide allocated E-UTRAN resources according to sharing agreements/policies.
  • Indication of and potential actions upon overload situation in consideration of sharing agreements/policies.


 

Here        Top

 

1  Scope    2 References    3 Definitions, symbols and abbreviations    3.1 Definitions    3.2 Abbreviations    4 Scenarios and use cases    4.1 General    4.2 Scenario and use case 1 (RAN Sharing Monitoring)    4.3 Scenario and use case 2 (MDT Support for RAN operator)    4.4 Scenario and use case 3 (Use case regarding RAN sharing granularity)    4.5 Scenario and use case 4 (maximizing RAN sharing revenue)    4.6 Scenario and use case 5.a (Asymmetric RAN Resource Allocation)    4.7 Scenario and use case 5.b (Asymmetric RAN Resource Allocation in a static way)    4.8 Use case 6 (Dynamic RAN Sharing Enhancements)    4.9 Scenario and use case 7 (On-demand Automated Capacity Brokering)    4.10 Scenario and use case 8 (Participating Operator managing allocated resources)    4.11 Scenario and use case 9 (Load balancing in shared RAN)    4.12 Scenario and use case 10 (RAN Sharing Charging Event Triggering)    4.13 Scenario and use case 11 (RAN Sharing Charging Reconciliation)    4.14 Scenario and use case 12 (PLMN selection enhancements towards a shared RAN)    4.15 Scenario and use case 13 (PWS in shared RAN)    4.16 Scenario and use case 14 (Common network shared by multiple operators)    4.17 Scenario and use case 15 (Interworking between shared RATs)    5 Considerations    5.1 General    5.2 Considerations on network evolution/rollout    5.3 Considerations on security    5.4 Difference with pre-Release-12 RAN sharing specification    5.5 Impact on RANs    6 Potential requirements    6.1 General    6.2 Consolidated requirements    7 Conclusion and recommendations    A Change history   

 

1   Scope   Word-p. 7
2   References
3   Definitions, symbols and abbreviations
4   Scenarios and use cases
4.1   General
4.2   Scenario and use case 1 (RAN Sharing Monitoring)   Word-p. 10
4.3   Scenario and use case 2 (MDT Support for RAN operator)
4.4   Scenario and use case 3 (Use case regarding RAN sharing granularity)   Word-p. 12
4.5   Scenario and use case 4 (maximizing RAN sharing revenue)
4.6   Scenario and use case 5.a (Asymmetric RAN Resource Allocation)   Word-p. 14
4.7   Scenario and use case 5.b (Asymmetric RAN Resource Allocation in a static way)
4.8   Use case 6 (Dynamic RAN Sharing Enhancements)   Word-p. 17
4.9   Scenario and use case 7 (On-demand Automated Capacity Brokering)   Word-p. 18
4.10   Scenario and use case 8 (Participating Operator managing allocated resources)
4.11   Scenario and use case 9 (Load balancing in shared RAN)
4.12   Scenario and use case 10 (RAN Sharing Charging Event Triggering)
4.13   Scenario and use case 11 (RAN Sharing Charging Reconciliation)
4.14   Scenario and use case 12 (PLMN selection enhancements towards a shared RAN)
4.15   Scenario and use case 13 (PWS in shared RAN)
4.16   Scenario and use case 14 (Common network shared by multiple operators)
4.17   Scenario and use case 15 (Interworking between shared RATs)
5   Considerations   Word-p. 29
6   Potential requirements
7   Conclusion and recommendations   Word-p. 33      Up
A   Change history   Word-p. 34

Up        Top