hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.5.1 General description | NOTE: This subclause is intended as illustration and baseline for CT1’s analysis. It does not mandate anything for RAN groups’ work; in case of conflict between this and RAN workgroups’ description the latter takes precedence.
Power adaptation of capacity enhancing cells can be utilized for energy saving in the case of overlaid cell coverage, as shown in figure 5.5.1-1. Here a case is shown where the target cell remains in operation, but with reduced power, thus reduced coverage; another case could be if the power for the target cell is reduced to a minimum, so that subsequently it can be switched off without any further impact on UEs (as they then will have re-selected other cells). Obviously the process can be performed slowly enough not to create a similar issue as described in subclause 5.1.5.
Figure 5.5.1-1: Power adaption for capacity enhancing cells in 3GPP macro network, due to energy saving (left: normal mode, right: energy saving mode)
Power adaptation of cells allows an overall power saving even in the case of non-overlaid cell coverage. This use case is described in more detail in annex A of 3GPP TS 32.551 [6], and the adaptation process is depicted in figure 5.5.1-2.
Figure 5.5.1-2: Power adaption for non-overlaid cells in 3GPP macro network, due to energy saving of one cell (left: normal mode, right: energy saving mode)
Again, target cells for energy saving decrease their power until their coverage has become sufficiently small, so that subsequently they can be switched off. Neighbouring cells correspondingly increase their power and coverage and thus fill the area. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.5.2 Key issue: Coverage boundaries | NOTE 1: This subclause does not mandate anything for RAN groups’ work; in case of conflict between this and RAN workgroups’ description the latter takes precedence.
Although the principle of power adaptation of macro cells as described in subclause 5.5.1 avoids coverage holes in the (overall, outdoor) macro cell coverage itself, there is no co-operation with non-3GPP accesses. It thus seems unlikely that it can avoid additional dynamics of the coverage boundaries on the smaller scale e.g. towards indoor areas. Especially for these areas alternatives, e.g. non-3GPP accesses, are foreseen.
Editor's note: details of coverage dynamics with power adaptation are out of scope here and should be characterized by RAN groups.
If the movement of macro cell coverage boundary, due to power adaptation of a macro cell for energy saving purpose, is such that it reduces the overlap with the indoor radio access, it potentially forces some/more UEs to use the alternative radio access (by inter-RAT handovers). Figure 5.5.2-1 illustrates the principle of this possible change in coverage boundaries due to power adaptation. (Note that in the worst case, if the coverage overlap is totally eliminated, it could lead to lack of service for UEs; this could happen if the non-3GPP access dimensioning is done for the macro cell configuration without energy saving.)
Figure 5.5.2-1: Illustration of coverage boundaries between macro and indoor coverage with and without power adaptation of macro cells
NOTE 2: For some UEs a reduced overlap of coverage can also have a positive side-effect (reduced toggling between accesses).
The above described effect from UE to network signalling per single power adaptation action is expected to be small, due to the limited amount of affected UEs and spreading out over time. However, if aggregation occurs over a larger area of the network within a short time, the issue like described in subclause 5.6.1 "Key issue: Increased ANDSF load" will arise.
Additionally (independent of aggregation), for I-WLAN as the chosen alternative access, an analogous effect as described in subclause 5.3.2 "Key issue: Latency associated with WLAN access network re-selection after switch-off (WLAN 3GPP IP access)" will apply for affected UEs.
NOTE 3: The combination of switch off of macro cell and subsequent (forced) WLAN access network selection has not been captured as a separate scenario, due to the assumption that any energy saving mechanism in 3GPP access will avoid coverage holes. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.6 Common issues | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.6.1 Key issue: Increased ANDSF load | ANDSF can be interrogated by a UE for delivery of access network discovery information for non-3GPP accesses at any time after a secure connection has been set up between these two entities. The triggers for such queries are not specified.
There are potential relations between switch-off of RATs and UE-ANDSF communication, which could act as triggers for ANDSF interrogation:
1) Update of location information due to switch-off of radio equipment for inter-RAT energy saving:
If a RAT is no longer visible to a UE due to switch-off (e.g. E-UTRAN switched off), any previously delivered location information associated with this RAT parameter delivered to the ANDSF is no longer useful. Consequently, the UE would most likely try to update ANDSF; although this is implementation specific behaviour, it is a reasonable and plausible one. For switch-on of a RAT a similar argument holds.
2) Refresh of ANDSF information, due to UE's pull policy:
The UE could always want to have best options for its decision about usage of access networks; if a RAT is switched off and was before deemed a suitable candidate (e.g. for a particular type of applications), the UE is left with fewer alternatives and could want to have reconsidered this fact by ANDSF (again, this is implementation specific, but likely). If a RAT, previously switched off and thus not visible to the UE, is switched on and the UE detects it newly in radio scanning, the UE could expect that previously delivered access network discovery information is outdated and could equally try to refresh this data.
NOTE 1: How the UE infers that a RAT is switched off is implementation dependent.
NOTE 2: As stated in 3GPP TS 24.302 [7], mechanisms to limit the frequency of queries transmission from the UE to the ANDSF are implementation dependant.
Both cases listed above seem uncritical for switch-off/on of single cells, but can become critical if many cells are switched off/on nearly at the same time. Due to the centralized nature of ANDSF this mass effect can aggregate over large areas. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.6.2 Key issue: Signalling overload for multi-access and flow mobility | A UE can initiate, via the maintained access network, the removal of an access network from a PDN connection, after it has detected the loss of the associated radio coverage (see figure 5.5-1 of 3GPP TS 23.261 [17]). This procedure is started by a DSMIPv6 Binding Update message sent from the UE to the PDN GW/Home Agent and leads to subsequent further steps (Binding Acknowledgement, release of resources including security association).
If the switch-off, i.e. loss of an access network, happens in a large area at the same time, there is the danger that many UEs perform the DSMIPv6 update signalling within a short time. This can potentially lead to overload and delay in the control plane functionality of the PDN GW/Home Agent.
NOTE: When a radio access is switched off, IP packets in the user plane being routed via the corresponding interface will likely be lost.
In the opposite direction of switching (radio access is switched on again), the issue also exists in principle but seems less critical, because in this case UEs likely will show larger variance with respect to the latency regarding flow redistribution .The difference stems from the fact that UEs are not forced to act immediately in order to receive continuous service for all IP flows. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.7 Additional analysis | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 5.7.1 Potential interaction between machine type communication and energy saving | Some type of machine type communication, e.g. reading out meter/sensor values or stock lists, is flexible with regards to the transaction time and is therefore thought to be suitable for handling in off-peak, especially night, hours. But this is also exactly the target time window for energy saving; therefore potential interactions between these two features need to be considered. In case of competing targets this needs to be resolved by intelligent configuration and use of the corresponding mechanisms.
Especially for support of machine type communication (but not limited to it) some extensions to NAS signalling procedures are defined in 3GPP TS 24.008 [21] and 3GPP TS 24.301 [12], as well as NAS protocol related configuration parameters defined in 3GPP TS 24.368 [20]. They can influence UE to core network signalling in a way relevant to energy saving, e.g.
- use of MM and SM backoff timers; and
- increase of periodic registration (LAU/RAU/TAU) timers.
Table 5.7.1-1 collects and analyzes potential interactions on NAS signalling level between these features in more detail.
Table 5.7.1-1: Potential interactions between (a) extensions to NAS signalling procedures and NAS protocol configuration parameters and (b) energy saving
Mechanism (reference)
Description
NAS signalling aspect relevant for this study
Comment
MM and SM backoff timers (see 3GPP TR 23.888 [8], subclause 6.22)
Under high load conditions, some MM and SM requests (Attach, PDP/PDN Activation, Service Request, …) might be rejected, in which case the request is repeated at a later time.
1) An attach to the remaining active RAT (due to inter-RAT energy saving) could fall into this handling and experience delay.
Only relevant for devices with multiple radio interfaces.
2) Peaks in NAS signalling become spread out over time; as a consequence, the net time window for energy saving could become smaller.
Relevant if signalling peaks are scheduled close to the intended target time for energy saving.
It is assumed that the time window for energy saving is determined (also) based on signalling traffic.
Optimized periodic registration timer (see 3GPP TR 23.888 [8], subclause 6.20)
Possibility of longer periodic registration timers (defined locally at MME/SGSN or by subscription), so that the amount of registration update signalling is minimized.
1) Long enough periodic registration timer values, and their reset close enough to start of energy saving time window could avoid signalling traffic within this time.
Can allow a peaceful coexistence of both features, but requires careful, coordinated configuration.
2) Location registrations induced by energy saving counteract the original optimization principle.
An additional aspect to be considered is that a wide range of devices for the use cases described above is expected to be very price sensitive, thus they will likely support only one radio interface; this reduces the options for energy saving (no inter-RAT energy saving possible). |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6 Potential optimizations and enhancements in procedures | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.1 Solution "Optimized configuration of tracking areas and TAI lists" | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.1.1 Description | This solution addresses key issues "Tracking Area Update signalling resulting from switch-off/on of macro cells" described in subclause 5.1.5 and "Idle mode UEs with emergency bearer services" as described in subclause 5.1.7.
The solution consists in overall configuration
1) of TAs in the network; or
2) TAI lists to be assigned to UEs,
in such a way that cells targeted for switch off are preferably avoided on boundaries of TAs or boundaries of the areas defined by TAI lists, respectively. The first variant means static configuration, while the second one allows for more dynamic handling (by MME).
NOTE 1: Solution variant 1) can be extrapolated in a straightforward manner to LA and RA configurations. Solution variant 2) can be applied only to TAs/E-UTRAN.
NOTE 2: Even if the TA/TAI list configuration fulfills the above criterion only partially, this reduces the severity of the related issues proportionally. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.1.2 Benefits | No standardization effort is required for this solution. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.1.3 Limitations | No full flexibility is possible, e.g. for deployment of capacity enhancing cells under changing conditions.
The effort for guaranteeing the optimized configuration increases with the number of affected cells and thus can become large if energy saving is applied massively (e.g. network wide). |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.1.4 Impacts on 3GPP Specifications | None. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.2 Solution "Adding time dependence to configuration settings in MOs" | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.2.1 Description | This solution addresses key issue "Cross layer aspects” as described in subsection 5.1.6, in particular for inter-RAT energy saving.
The solution consists in adding time parameters to the following configuration parameters in OMA DM MOs, related to voice calls and multimedia sessions and defined in 3GPP TS 24.167 [10] and 3GPP TS 24.216 [11]:
3GPP TS 24.167: Voice_Domain_Preference_E_UTRAN, Voice_Domain_Preference_UTRAN.
3GPP TS 24.216: Preferred_domain
The time information is to be taken into account by UEs when initiating communication, in order to avoid the need for (possibly synchronized) domain transfer at the switch-off time of a RAT. As an example, if E-UTRAN is to be switched off at 24:00 h, the voice domain preference could be set to "CS Voice only" for a time window which starts sufficiently long before the target time for switch-off, e.g. to 23:40 h. The safety margin (here 20 minutes) should be chosen based on average call/session durations, so that most of the calls/sessions can be expected to end before the target switch-off time. This is illustrated in figure 6.2.1-1.
NOTE: Introducing time dependence to MOs does not imply that MO data has to be updated more often than before or close to points in time where the settings change.
Figure 6.2.1-1: Example behaviour of UEs with/without time dependent operator preferences for voice domain selection
Some configuration settings currently do not differentiate between RATs, but only between CS and PS domains, and so the control per RAT is not directly possible. However, a preference for CS implicitly excludes E-UTRAN.
Additionally, these configuration settings could be made fully RAT specific. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.2.2 Benefits | The solution reduces the amount of signalling for domain transfer (which is also time critical) both for the network and affected UEs, if these need to originate communication just before a RAT is switched off for the purpose of inter-RAT energy saving. Also, a potential but unnecessary deterioration of service experience can be avoided in a majority of cases. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.2.3 Limitations | These operator preferences are specific for selected services (voice calls and multimedia sessions). These settings are currently not per PLMN; thus either a differentiation per PLMN has to be introduced, or the described time dependence is to be limited to the HPLMN.
This solutions requires changes in UEs, and therefore the benefits do not apply for legacy UEs.
No full traffic steering is achievable with preferences only.
A certain fraction of calls with longer duration than the time margin configured before switch-off of the RAT will occur; for these the above mentioned benefit does not apply. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.2.4 Impacts on 3GPP Specifications | Additions in 3GPP TS 24.167 [10] and 3GPP TS 24.216 [11], and enhancements in specifications of corresponding procedures (3GPP TS 24.301 [12] and 3GPP TS 24.237 [13]). |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.3 Solution "Dynamic radio access network sharing" | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.3.1 Description | This solution addresses all key issues listed in subclause 5.1.
Network Sharing with a Multi-Operator Core Network (MOCN), as defined in 3GPP TS 23.251 [14], is an established means to leverage reduced operator's expense for radio access infrastructure. Even though currently it is assumed to be firmly and permanently configured, it can also be used in a more dynamical form, i.e. the radio access can be shared between two or several operators only during off-peak hours for the purpose of energy saving. To this end, no normative modifications are required in 3GPP specifications. In particular, no impacts on UE functionality are foreseen, but it needs to be recognized that the solution works more efficiently for network sharing supporting UEs (see below).
The solution scheme is shown in figure 6.3.1-1 for the example of two operators switching off their RANs and also sharing them on alternate days. Consequently they gain alternately the complete saving of energy of radio nodes for the switch off period. In more detail, in a period when the RAN of PLMN A is switched off, the configuration of PLMN B is changed to enable RAN sharing with PLMN A; after the RAN of PLMN A has been switched on again, the configuration of .PLMN B is changed back to normal, to avoid the RAN sharing. As the switch-off of the RAN and the configuration change cannot be assumed to be perfectly synchronized, a small time safety margin needs to be applied.
Figure 6.3.1-1: Dynamic network sharing scheme for energy saving (two operators)
According to TS 23.251 [14], during the time of sharing, radio nodes broadcast PLMN information for both PLMNs. Subsequently the behaviour differs for supporting and non-supporting UEs:
- supporting UEs (see subclause 7.1.3 in 3GPP TS 23.251 [14]): they are able to decode the multiple PLMN information in the system broadcast information and select the PLMN on their own. The RPLMN should again be broadcast in the shared state, so no additional PLMN selection is triggered.
- non-supporting UEs (see subclause 7.1.4 in 3GPP TS 23.251 [14]): these are not able to decode the multiple PLMN information and consequently cannot control network selection. Instead, the RAN and core network perform this task by initial routing and potential re-direction. The impact on NAS signalling is that for these UEs additional registration updates and Identity Request/Response and Authentication dialogues can result. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.3.2 Benefits | This solution allows to save the energy consumption of the RAN of at least one operator completely during off-peak time. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.3.3 Limitations | This solution requires tight coordination between participating operators. National roaming (at least for non-supporting UEs during sharing period) must be allowed, and scheduling of network sharing for one PLMN must always match correctly the switch off times of the other PLMN(s).
The additional NAS signalling for non-supporting UEs has to be taken into account properly; e.g. it could be necessary to spread out the switch-off time sufficiently over time and areas.
The dynamic change of network configuration related to RAN sharing could require enhancements of current OAM procedures and data.
NOTE: the OAM aspects need to be considered by SA5 WG. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.3.4 Impacts on 3GPP Specifications | No impacts of normative character are needed. It could be worth to include clarifications for this use case, e.g. in 3GPP TS 23.401 [15]. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.4 Solution "Network based handling for multi-access and flow mobility" | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.4.1 Description | This solution addresses the key issue "Signalling overload for multi access and flow mobility" as described in subclause 5.6.2.
In this solution the Home Agent functionality in the PDN GW is enhanced by some knowledge about availability of access networks. The already existing procedure "network initiated removal of an access network from a PDN connection" as specified in subclause 5.9 of 3GPP TS 24.303 [18] is used to redistribute the IP flows via the access networks remaining operational, in a smooth manner and early enough. To this end, the Binding Revocation Indication (BRI) messages sent to all affected UEs could be spread out over time, while still allowing completion of the process before the access network is switched off. This is illustrated in figure 6.4.1-1.
Figure 6.4.1-1: Overall scheme of signalling with network based handling for multi access and flow mobility
In the upper part of figure 6.4.1-1 the principal sequence of steps in signalling between the UE and Home Agent is shown for one UE. In the lower part the aggregated behavior, including desired safety margin before switch-off and expectable latency after switch-on is sketched. Because the redistribution of IP flows after switch-on is purely UE dependent, the signalling will be more irregular.
No further assumptions can be made regarding how the Home Agent acquires its knowledge about the scheduled downtimes of access networks, as this is out of scope of this study. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.4.2 Benefits | Potential overload on PDN GW/Home Agent can be avoided. IP flows can be moved from access networks subject to switch-off to access networks remaining operational; this reduces packet loss and thus improves user experience. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.4.3 Limitations | How the HA acquires knowledge about downtime of access networks is left unspecified. Although static provisioning of data seems possible for small scale deployments, a fully standardized solution for this part would require additional specification effort (in CT4's or SA5's domain of work). |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.4.4 Impacts on 3GPP Specifications | No normative impacts foreseen; however, it could be worthwhile to document this use case in an informative manner.
6.5 Solution "Activation times in ANDSF data" |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.5.1 Description | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.5.1.1 Variant 1 | This variant of the solution consists in enhancing access network discovery information data, stored and provided by ANDSF for non-3GPP access networks, with activation status information (activation time windows). If lacking (default) it means that these access networks are assumed to be always active.
The information on activation time can be taken into account for UEs decisions on:
- access network (re-)selection: it can be avoided that the UE tries to select an access network which actually is not switched on. Although the UE would detect this situation by access specific means (e.g. probing or scanning) it is more efficient to know it in advance;
- (non-optimized) handover: if the UE is using an access network known to be switched off soon, it can initiate the handover early enough, so that the whole procedure can be completed before the current radio is lost;
- flow re-distribution: if the UE is using an access network known to be switched off soon, it can initiate the flow-redistribution early enough, so that the whole procedure can be completed before the current radio is lost; and
- ANDSF interrogation: the UE, when probing or scanning for a radio access, will not detect a mismatch with ANDSF data. Therefore a potential cause for ANDSF interrogation is avoided. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.5.1.2 Variant 2 | In this variant the activation times of access networks are considered implicitly with all relevant ISMP and ISRP rules. Evaluating these enhanced policy rules will result in optimized UE behavior equivalent to the one described above for variant 1. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.5.2 Benefits | This solution helps to solve the key issue "Increased ANDSF load" described in subclause 5.6.1. The additionally provided information avoids that the UE, due to finding a persistent mismatch between data received from ANDSF and the real availability of access networks, would deem the data being outdated and try to refresh it from ANDSF.
This solution can also mitigate key issues "Latency associated with WLAN access network re-selection after switch-off (WLAN 3GPP IP access)" described in subclause 5.3.2 and "Mass effect resulting from WLAN access network re-selection after switch-off " described in subclause 5.3.3, as it allows UEs to re-select WLAN access network pro-actively.
This solution alleviates key issue "Degradation of service due to switch-off of non-3GPP access networks" described in subclause 5.4.2, due to the fact that handovers can be initiated timely enough.
This solution mitigates key issue "Signalling overload for multi-access and flow mobility" as described in subclause 5.6.2, because flow-redistribution can be done timely enough (similar to the solution described in subclause 6.4, but initiated by the UE instead of the Home Agent). |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.5.3 Limitations | There can be no guarantee that the activation times announced explicitly or considered implicitly in policy rules by ANDSF match perfectly the reality; e.g. it could happen that a radio access is still switched off, despite being announced as active, and vice versa.
Announcing activation times could lead advanced users to wait and start requesting their services immediately after the switch-on of a particular radio access; this behavior should be considered by including sufficient margins with activation times.
Dynamic handling e.g. for taking into account current load cannot be achieved by this solution. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 6.5.4 Impacts on 3GPP Specifications | For variant 1, the following 3GPP specifications require enhancements for this solution:
- 3GPP TS 23.402 and potentially 3GPP TS 23.261: enhancement in functional description (stage 2);
- 3GPP TS 24.312: additional information elements defining the activation time windows of e.g. GERAN_CI, UTRAN_CI, EUTRA_CI, Sector-ID, BS-ID, HESSID, SSID, BSSID; and
- 3GPP TS 24.302: reflect the usage of additional information (activation time windows) in procedural descriptions.
For variant 2 there is no impact on 3GPP specifications. |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 7 Conclusions | |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 7.1 General overview of key issues and solutions | Table 7.1-1 lists the key issues and how they are covered by documented solutions.
Table 7.1-1: Key issues and solutions
Sub-clause
Energy saving scenario / Key issue
Solution (sub-clause)
Comment
5.1
Switch-off/on of Macro cells
5.1.5
Registration signalling resulting from switch-off/on of macro cells
6.1, 6.3
5.1.6
Cross layer aspects
6.1, 6.2, 6.3
5.1.7
Idle mode UEs with emergency bearer services
6.3
5.1.8
impact of inter-RAT energy saving on signalling over SGs
6.3
5.2
Switch-off/on of home cells
5.2.2
Incidental synchronization of H(e)NB switch-off/switch-on
Solution(s) potentially by other WGs or vendors
5.3
Switch-off/on of I-WLAN
5.3.2
Latency associated with WLAN access network re-selection after switch-off (WLAN 3GPP IP access)
6.5
5.3.3
Mass effect resulting from WLAN access network re-selection after switch-off
6.5
5.4
Switch-off/on of non-3GPP accesses
5.4.2
Degradation of service due to switch-off of non-3GPP access networks
6.5
5.5
Power adaptation for 3GPP macro cells
5.5.2
Coverage boundaries
Dependence on more details from RAN WGs
5.6
Common issues
5.6.1
Increased ANDSF load
6.5
5.6.2
Impacts for multi-access and flow mobility
6.4, 6.5 |
2d016e763d82d2bbce817fafc33663a6 | 24.826 | 7.2 Detailed conclusions | The following conclusions are drawn:
- Several key issues (in particular those in subclauses 5.1.5, 5.1.8, 5.2.2, 5.3.3, 5.6.1 and 5.6.2) are related to potential widescale synchronized UE behaviour. As a general strategy, and independent of individual solutions, these issues can be mitigated by spreading out switching (on/off) times sufficiently.
- Several possible solutions have been defined which do not have any impact on the 3GPP specifications (those described in subclause 6.1, 6.3, 6.4 and partially 6.5 [variant 2]), and as an implementation option they could be exploited as of today.
- For energy saving in 3GPP access, subclauses 6.1 and 6.3 provide some proposed solutions which relate also to functionalities in the RAN. Taking into account the fact that the solution described in subclause 6.1 is an intra-operator one, an operator can consider this solution for deployment in the first place. In addition, if an operator has to meet high targets for energy saving and tight coordination including network sharing with other operator(s) is feasible, s/he could consider the solution described in subclause 6.3.
- For energy saving in non-3GPP access, the solution described in subclause 6.5 solves several key issues. However as variant 1 would introduce new normative requirements onto 3GPP entities while variant 2 does not, it seems logical to propose, in the initial phase of implementing an energy saving strategy, variant 2 as a way forward.
Annex A (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-06
Initial skeleton provided by rapporteur
0.0.0
2010-07
Contributions agreed in CT1#65: C1-102713, C1-102714, C1-102715, C1-102716, C1-102717; editorial alignment
0.0.0
0.1.0
2010-07
Further editorial improvement incl. enforcement of drafting rules.
0.1.0
0.1.1
2010-09
Contributions agreed in CT1#66: C1-103134, C1-103251, C1-103252, C1-103253, C1-103548
0.1.1
0.2.0
2010-09
Correct implementation of C1-103134 and further editorial improvements
0.2.0
0.2.1
2010-10
Contributions agreed in CT1#67: C1-104245,C1-104246, C1-104247, C1-10443; editorial corrections and re-drawing of figures in Visio
0.2.1
0.3.0
2010-11
Contributions agreed in CT1#68: C1-104759, C1-105145, C1-105147, C1-105246
0.3.0
0.4.0
2011-02
Contributions agreed in CT1#69: C1-110228, C1-110722, C1-110723, C1-110724, C1-110725, C1-110726
0.4.0
0.5.0
2011-03
Contributions agreed in CT1#70: C1-111447, C1-111448, C1-111449, C1-111507; editorial corrections
0.5.0
0.6.0
2011-03
CT-51
CP-110149
Version 1.0.0 created for presentation to CT-51 for information.
0.6.0
1.0.0
2011-05
Contributions agreed in CT1#71: C1-111921, C1-112175
1.0.0
1.1.0
2011-05
CT-52
Version 2.0.0 created for presentation to CT-52 for approval.
1.1.0
2.0.0
2011-06
CT-52
Version 11.0.0 created after approval at CT-52
2.0.0
11.0.0 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 1 Scope | The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
Status list of Work items can be found in Annex A of the present document. |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] http://www.3gpp.org/ftp/Information/WORK_PLAN/
[2] http://www.3gpp.org/ftp/Information/WI_Sheet/ |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 1 Charging for Network Provided Location Information for IMS | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 1.1 Charging for Network Provided Location Information for IMS (NWK-PL2IMS_CH) UID_490029 | TSG SA Meeting #51 SP-110125
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110356
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of SP-100638
TSG SA Meeting #49 SP-100638
20-23 Sep 2010, San Antonio, USA |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 1 3GPP Work Area | X
Radio Access
Core Network
Services |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2 Classification of WI and linked work items | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2.0 Primary classification | This work item is a …
X
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
Work Task (go to 2.4) |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2.1 Study Item | Related Work Item(s) (if any]
Unique ID
Title
Nature of relationship |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2.2 Feature | Related Study Item or Feature (if any) *
Unique ID
Title
Nature of relationship
Go to §3. |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2.3 Building Block | Parent Feature (or Study Item)
Unique ID
Title
TS
This work item is … *
Stage 1 (go to 2.3.1)
Stage 2 (go to 2.3.2)
Stage 3 (go to 2.3.3)
Test spec (go to 2.3.4)
Other (go to 2.3.5)
2.3.1 Stage 1
Source of external requirements (if any) *
Organization
Document
Remarks
Go to §3.
2.3.2 Stage 2 *
Corresponding stage 1 work item
Unique ID
Title
TS
Other source of stage 1 information
TS or CR(s)
Clause
Remarks
If no identified source of stage 1 information, justify: *
Go to §3.
2.3.3 Stage 3 *
Corresponding stage 2 work item (if any)
Unique ID
Title
TS
Else, corresponding stage 1 work item
Unique ID
Title
TS
Other justification
TS or CR(s)
Or external document
Clause
Remarks
If no identified source of stage 2 information, justify: *
Go to §3.
2.3.4 Test spec *
Related Work Item(s)
Unique ID
Title
TS
Go to §3.
2.3.5 Other *
Related Work Item(s)
Unique ID
Title
Nature of relationship
TS / TR
Go to §3.
2.4 Work task *
Parent Building Block
Unique ID
Title
TS |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3 Justification | Sustainable development is a long-term commitment in which all of us should take part. As part of sustainable development, our fight against global warming should be without respite.
Most mobile network operators aim at reducing their greenhouse emissions, by several means such as limiting their networks' energy consumption. Furthermore, energy costs are rising and form a growing share of the operational expenses of mobile network operators.
SA5 up to now has defined Energy Saving Management functionality for LTE (OAM aspects of Energy Saving in Radio Networks (OAM-ES) UID_470037. Such definitions are not yet present for 3G and 2G mobile networks. But also for these a standardized Energy Saving Management functionality is required. This study will also involve Inter-RAT Energy Saving Management, e.g. when network redundancy is leveraged.
By initiating this Study and the intended follow-up implementation Work Item about OAM aspects of Inter-RAT Energy Savings, SA5 hopes to contribute to the protection of our environment and the environment of future generations. |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 4 Objective | The objective of this study is to:
Identify the most important Inter-RAT energy saving scenarios and use cases
Identify OAM based concept and requirements for these use cases
Analyse how existing IRPs can be re-used, adapted or extended to fulfil these requirements or if a new IRP is needed.
Select information that should be used to decide if an energy saving cell shall enter or leave energy saving mode.
New elements in IRPs, adaptations or extensions to IRPs may be considered in this study item, but the study item is not limited to them:
LTE ES management functionality for Inter-RAT scenarios
Suitable traffic load measurements (potentially with short granularity periods)
Energy consumption measurements
“low consumption mode” of network resources
Adjust Network Resources Models
Note that SA5 is willing to work in cooperation with RAN WGs where needed.
The time frame for this study item is intentionally set very short. It is intended to create, based on the results of the study, within the Rel-11 time frame a dedicated work item for OAM aspects of Inter-RAT Energy Saving.
*) Note: The following concrete use cases were considered when this study item was created: General scenario: There are two RAT layers.
Use case 1: cells of the different RATs are collocated and have a similar coverage area.
Use case 2: cells of one RATs are not collocated and have a significantly smaller coverage area than the other RAT.
Typically cells of the RAT working on higher frequency can be switched off / brought into lower energy consumption mode in low traffic periods, can be switched on again if traffic indicators shows higher traffic than typical in backing cell (potentially also other information can be used to decide if switching cell/s on can really bring benefits to the customer). |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 5 Service Aspects | None |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6 MMI-Aspects | None |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 7 Charging Aspects | None |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 8 Security Aspects | None |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 9 Impacts | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
No
X
X
X
Don't know |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 10 Expected Output and Time scale | New specifications
[If Study Item, one TR is anticipated]
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
TR 32.834Study on OAM aspects of inter-RAT Energy Saving
SA5
SA#53, Sep 2011
SA#54, Dec 2011
The TR shall describe use cases, concepts and requirements for Inter-RAT Energy Savings Management and proposals how to re-use, adapt, extend existing IRPs.
Affected existing specifications
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
11 Work item Rapporteur(s)
Nokia Siemens Networks ([email protected])
12 Work item leadership
SA5
13 Supporting Individual Members
Supporting IM name
Deutsche Telekom
Nokia Siemens Networks
Telia Sonera
Orange
Motorola
Huawei
Vodafone
Ericsson
Alcatel-Lucent
China Mobile
China Unicom
NEC
ZTE |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2 QoS Control Based on Subscriber Spending Limits | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2.1 Charging for QoS Control Based on Subscriber Spending Limits (QoS_SSL) UID_500029 | 3GPP TSG SA Meeting #53 SP-110519
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG-SA5 (Telecom Management) S5-112662
SA5#78, 22-26 August 2011, Istanbul, Turkey
Source: SA5
Title: Revised SP-100644 WID on QoS Control Based on Subscriber Spending Limits (QoS_SSL)
Document for: Approval
Agenda Item: 7.2 New Charging Work Item proposals |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 1 3GPP Work Area * | X
Radio Access
Core Network
Services |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 2.0 Primary classification * | This work item is a … *
X
Study Item (go to 2.1)
Feature (go to 2.2)
Building Block (go to 2.3)
Work Task (go to 2.4) |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3 Justification * | A Heterogeneous Network consists of different types of Base Stations (BSs), such as macro, micro and pico BSs.
These types of BSs will be mixed in an operating network. Using low power BSs like micro and pico to enhance coverage and capacity, it is foreseen that there will be very many of these low power BSs in operation. Each of them will cover an area that is significantly smaller than a macro BS. Each of the low power BSs will correspond to a number of objects with attributes and measurements to manage. At the same time, each low power BS is a node in itself and the requirement to manage them are similar as for macro BSs. What performance management information that is wanted is very similar as for macro. The configuration requirements for the cellular network supported by low power nodes are still very similar as for macro nodes. The requirements for being able to generate alarm are still very similar as for macro nodes. As the amount of low power nodes can be very many, a different approach to manage the nodes are needed. They do not necessarily always need be actively connected to the management system. They can use "On Demand" management paradigm. But it is up to the operator to choose which nodes shall use the "on demand" paradigm. "On Demand" paradigm means that nodes are not constantly connected over Itf-N to the IRPManager via the IRPAgent and that the IRPManager can connect to "On Demand" managed nodes via the IRPAgent to perform management actions. The IRPManager can also decide whether a node shall be managed via "On Demand Management" or "Constantly Connected management" paradigm.
Femto is not included in this study. |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 4 Objective * | The objective is to study "On Demand" management over Itf-N:
Nodes on which "On Demand" management can be applied to
A subscription mechanism for an "On Demand" paradigm for heterogeneous networks
The necessary operations, objects and attributes for an "On Demand" paradigm |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 9 Impacts * | Affects:
UICC apps
ME
AN
CN
Others
Yes
X
No
X
X
X
Don't know
X |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 10 Expected Output and Time scale * | New specifications *
[If Study Item, one TR is anticipated]
Spec No.
Title
Prime rsp. WG
2ndary rsp. WG(s)
Presented for information at plenary#
Approved at plenary#
Comments
32.8xy
Study on management of Heterogeneous Networks
SA5
SA#54 Dec 2011
SA#54 Dec 2011
Affected existing specifications *
[None in the case of Study Items]
Spec No.
CR
Subject
Approved at plenary#
Comments
11 Work item rapporteur(s) *
YunXi Li, Ericsson ([email protected])
12 Work item leadership *
SA5
13 Supporting Individual Members *
Supporting IM name
Ericsson
Vodafone
NEC
Huawei
AlcatelLucent
ZTE
Qualcomm
Annex A:
Status of SA5 Work Items
This list reflects work items that are, new, ongoing, completed or stopped.
Unique_ID
Name
Acronym
500029
Charging for QoS Control Based on Subscriber Spending Limits (Stage 2)
QoS_SSL
490029
Charging for Network Provided Location Information for IMS
NWK-PL2IMS_CH
510051
Rel-11 Operations, Administration, Maintenance and Provisioning (OAM&P)
OAM11
510151
Network Infrastructure Management
OAM11-NIM
510056
IRP framework enhancements to support Management of Converged Networks
OAM-FMC-IRP
530049
Management for Carrier Aggregation for LTE
OAM-CA
530050
Network Management for 3GPP Interworking WLAN
OAM-IWLAN
510251
Performance Management
OAM11-PM
510057
IMS Performance Management enhancements
OAM-ePM-IMS
510058
Enhanced Management of UE based network performance measurements
OAM-ePM-UE
520034
CN performance measurements enhancement
OAM-ePM-CN
510351
Self-Organizing Networks (SON) - OAM aspects
OAM11-SON
510059
UTRAN Self-Organizing Networks (SON) management
OAM-SON-UTRAN
530051
LTE Self-Organizing Networks (SON) coordination management
OAM-SON-LTE_COORD
510052
Rel-11 Charging Management small Enhancements
CH11
470045
Add solutions for Rc - reference point within the Online Charging System (OCS)
CH-Rc
510060
Charging for Policy Enhancements for Sponsored Connectivity and Coherent Access to Policy related Data Bases
PEST-CH
510229
Stage 2/3 SA5 part of Transit Inter Operator Identifier for IMS Interconnection Charging in multi operator environment
IOI_IMS_CH
520235
SA5 part of FS_UMONC
FS_UMONC
470050
Study on version handling
FS_OAM_VH
480047
Study on Management of Converged Networks
FS_ManCon
490039
Study on User Data Convergence (UDC) information model handling and provisioning: Example Use Cases
FS_UDC_AppUseCase
510045
Study on OAM aspects of inter-RAT Energy Saving
FS_OAM_ES_iRAT
510046
Study on management of Heterogeneous Networks
FS_OAM_HetNet
Annex B:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
Jan 2011
S5-75
S5-110019
--
--
First draft
---
0.1.0
Apr 2011
S5-77
S5-111618
--
--
Post SA#51 update
0.1.0
0.2.0
May 2011
S5-78
S5-112218
--
--
Post SA#52 update
0.2.0
0.3.0
May 2011
S5-78
S5-112262
--
--
Add 32.8xy Study on Usage Monitoring Control OCS enhancement
0.3.0
0.3.1
Sep 2011
S5-79
S5-112818
--
--
Post SA#53 update
0.3.1
0.4.0 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3 OAM&P 11 | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.1 Network Infrastructure Management | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.1.1 IRP framework enhancements to support Management of Converged Networks (OAM-FMC-IRP) UID_510056 | TSG SA Meeting #51 SP-110139
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111490
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111199 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.1.2 Management for Carrier Aggregation for LTE (CA-OAM) UID_ 530049 | 3GPP TSG SA Meeting #53 SP-110520
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG SA WG5 (Telecom Management) Meeting #78 S5-112694
22 - 26 August 2011; Istanbul, Turkey revision of S5-112339 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.1.3 Network Management for 3GPP Interworking WLAN (IWLAN-OAM&P) UID_530050 | 3GPP TSG SA Meeting #53 SP-110521
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG SA WG5 (Telecom Management) Meeting #78 S5-112696
22 - 26 August 2011; Istanbul, Turkey revision of S5-112557 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.2 Performance Management | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.2.1 IMS Performance Management enhancements (OAM-ePM-IMS) UID_510057 | TSG SA Meeting #51 SP-110134
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110518
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of S5-110494 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.2.2 Enhanced Management of UE based network performance measurements (OAM-ePM-UE) UID_510058 | TSG SA Meeting #51 SP-110135
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110537
SA5#75, 24 - 28 Jan 2011, Sorrento, ITALY revision of S5-110517 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.2.3 CN performance measurements enhancement (OAM-ePM-CN) UID_520034 | 3GPP TSG SA Meeting #52 SP-110275
Bratislava, Slovakia, 06 – 08 June, 2011
3GPP TSG-SA5 (Telecom Management) S5-112134
SA5#77, 9-13 May 2011; Shenzhen, P.R. China revision of S5-111868, S5-112111 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.3 Self-Organizing Networks (SON) - OAM aspects | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.3.1 UTRAN Self-Organizing Networks (SON) management (OAM-SON-UTRAN) UID_510059 | 3GPP TSG SA Meeting #53 SP-110518
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG SA WG5 (Telecom Management) Meeting #78 S5-112587
22 - 26 August 2011; Istanbul, Turkey revision of S5-112325 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 3.3.2 LTE Self-Organizing Networks (SON) coordination management (OAM-SON-COOR) UID_510051 | 3GPP TSG SA Meeting #53 SP-110522
Fukoka, Japan; 19-21 Sep 2011
3GPP TSG SA WG5 (Telecom Management) Meeting #78 S5-112711
22 - 26 August 2011; Istanbul, Turkey revision of S5-112708 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 4 Charging Management small Enhancements (CH11) UID_510052 | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 4.1 Add solutions for Rc - reference point within the Online Charging System (OCS) (CH-Rc) UID_470045 Moved from Rel-10 | TSG SA Meeting #51 SP-110129
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111437
Meeting SA5#76, 28 February - 4 March 2011, San Diego, USA revision of SP-100078
Technical Specification Group Services and System Aspects TSGS#47(10)0078
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100993
Meeting SA5#70, 1 - 5 Mar 2010, Xiamen, China revision of S5-100822 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 4.2 Charging for Policy Enhancements for Sponsored Connectivity and Coherent Access to Policy related Data Bases (PEST-CH) UID_510060 | TSG SA Meeting #51 SP-110127
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110535
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of SP-110502
TSG SA Meeting #51 SP-110126
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111374
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111309 3GPP Work Area *
Radio Access
X
Core Network
Services |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 5 Transit Inter Operator Identifier for IMS Interconnection Charging in multi operator environment (IOI_IMS_CH) UID_510029 | TSG SA Meeting #51 SP-110132
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-110422
SA5#75, 24 - 28 Jan 2011; Sorrento, ITALY revision of S5-110248 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6 Studies | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6.0 Study on Usage Monitoring Control Enhancement (FS_UMONC) UID_520035 | TSG SA Meeting #51 SP-110349
Bratislava, Slovakia, 06 - 08 June, 2011 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6 MMI Aspects | N/A |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6.1 Study on version handling (FS_OAM_VH) UID_470050 Moved from Rel-10 | Technical Specification Group Services and System Aspects TSGS#47(10)0082
Meeting #47; Vienna, Austria; 22-25 March 2010
3GPP TSG-SA5 (Telecom Management) S5-100338
Meeting SA5#70, 1-5 Mar 2010, Xiamen, P.R. China |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6.2 Study on Management of Converged Networks (FS_ManCon) UID_480047 Moved from Rel-10 | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6.3 Study on User Data Convergence (UDC) information model handling and provisioning: Example Use Cases (FS_UDC_AppUseCase) UID_490039 Moved from Rel-10 | |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6.4 Study on OAM aspects of inter-RAT Energy Saving (FS_OAM_ES_iRAT) UID_510045 | TSG SA Meeting #51 SP-110138
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111491
Meeting SA5#76, 28 Feb – 4 March 2011, San Diego, USA revision of S5-111342 |
f0d098a37eb34f0b432bf0e46089ec9a | 30.821 | 6.5 Study on management of Heterogeneous Networks (FS_OAM_HetNet) UID_510046 | TSG SA Meeting #51 SP-110140
21 - 23 Mar 2011, Kansas City, USA
3GPP TSG-SA5 (Telecom Management) S5-111492
SA5#76, 28 Feb - 4 Mar 2011; San Diego, USA revision of S5-111345 |
db79454f376b7d1b792302faef07c1bd | 32.791 | 32.791 Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements | |
db79454f376b7d1b792302faef07c1bd | 32.791 | 32.792 Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) | |
db79454f376b7d1b792302faef07c1bd | 32.791 | 32.796 Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP): Solution Set (SS) definitions | |
db79454f376b7d1b792302faef07c1bd | 32.791 | 1 Scope | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.600 [4], the Requirements for the Common RAT NRM IRP for equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
The present document can be used also for managing the equipment that can be shared by several RATs, even in the cases when it is not being shared. |
db79454f376b7d1b792302faef07c1bd | 32.791 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements".
[3] 3GPP TS 32.102: "Telecommunication management; Architecture".
[4] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements".
[5] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept and definitions". |
db79454f376b7d1b792302faef07c1bd | 32.791 | 3 Definitions and abbreviations | |
db79454f376b7d1b792302faef07c1bd | 32.791 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 3GPP TS 32.150 [5], 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TS 32.150 [5], 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TR 21.905 [1], in this order. |
db79454f376b7d1b792302faef07c1bd | 32.791 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
BSS Base Station Subsystem
CAPEX Capital Expenditure
E-UTRAN Evolved UTRAN
GSM Global System for Mobile communications
IRP Integration Reference Point
NRM Network Resource Model
RAN Radio Access Network
RAT Radio Access Technology
UTRAN Universal Terrestrial Radio Access Network |
db79454f376b7d1b792302faef07c1bd | 32.791 | 4 Concepts and background | It becomes more and more common that operators operate more than one RAT. To save CAPEX, some radio equipment can be shared between the different RATs. Radio equipment can also be shared within a RAT. This NRM makes it easy to operate such shared radio equipment and to understand the consequences in all affected RATs when a change is made in a shared equipment. |
db79454f376b7d1b792302faef07c1bd | 32.791 | 5 Requirements | The following general and high-level requirement applies for the present IRP:
A. IRP-related requirements in 3GPP TS 32.101 [2].
B. IRP-related requirements in 3GPP TS 32.102 [3].
C. IRP-related requirements in 3GPP TS 32.600 [4].
In addition to the above, the following more specific requirements apply:
REQ-GRAN_NRM-CON-001: The NRM defined by this IRP shall contain IOCs and related definitions, supporting equipment that may be shared between BSS, UTRAN and E-UTRAN networks.
REQ-GRAN_NRM-CON-002: The IRPAgent shall support a capability allowing the IRPManager to know which RATs are served by each managed object.
Annex A (informative):
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2010-12
SP-50
SP-100769
Submitted to SA#50 for Information
0.1.1
1.0.0
2011-03
SP-51
SP-110178
--
--
Presentation to SA for Approval
1.0.0
2.0.0
2011-03
--
--
--
--
Publication
2.0.0
10.0.0
2012-09
-
-
-
-
Update to Rel-11 version (MCC)
10.0.0
11.0.0 |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 1 Scope | This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TS 25.102 (V4.0.0): "UTRA (UE) TDD; Radio Transmission and Reception (TDD)".
[2] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)".
[3] 3GPP TS 34.108 "Common Test Environments for User Equipment (UE) Conformance Testing"
[4] 3GPP TS 34.109: "Terminal logical test interface; Special conformance testing functions".
[5] 3GPP TS 25.224: "Physical Layer Procedures (TDD)".
[6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[7] 3GPP TR 25.990: "Vocabulary".
[8] ITU-R Recommendation SM.328-9: "Spectra and bandwidth of emissions".
[9] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification".
[10] 3GPP TS 25.433 "UTRAN Iub Interface NBAP Signalling".
[11] ITU-R Recommendation SM.329: "Spurious emissions".
[12] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode".
[13] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode".
[14] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification".
[15] 3GPP TS 25.223: "Spreading and modulation (TDD)".
[16] ETSI ETR 273-1-2: "Improvement of radiated methods of measurement (using test sites) and evaluation of the corresponding measurement uncertainties; Part 1: Uncertainties in the measuremement of mobile radio equipment characteristics; Sub-part 2: Examples and annexes".
[17] 3GPP TR 25.926: "UE Radio Access Capabilities".
[18] 3GPP TR 21.904: "UE capability requirements".
[19] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".
[20] 3GPP TS 45.008: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".
[21] 3GPP TS 34.123-1: "User Equipment (UE) Conformance Specification; Part 1: Protocol Conformance Specification".
[22] 3GPP TS 25.225: "Physical Layer – Measurements (TDD)".
[23] 3GPP TS 51.010-1: " Mobile Station (MS) conformance specification; Part 1: Conformance specification".
[24] 3GPP TS 25.306: "UE Radio Access capabilities definition".
[25] ITU-T recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate".
[26] 3GPP TS 36.133: "Requirements for support of radio resource management"
[27] 3GPP TS 36.101: “User Equipment (UE) radio transmission and reception”
[28] 3GPP TS 36.508: "Technical Specification Group Radio Access Network; E-UTRA and EPC; Common test environments for User Equipment (UE)"
[29] 3GPP TS 36.133: "E-UTRA requirements for support of radio resource management".
[30] 3GPP TS 36.211: "Physical Channels and Modulation".
[31] 3GPP TS 36.331: "E-UTRA Radio Resource Control (RRC): protocol specification".
[32] 3GPP TS 36.101: "E-UTRA UE radio transmission and reception".
[33] 3GPP TS 36.521-3: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) conformance specification; Radio transmission and reception; Part 3: Radio Resource Management (RRM) conformance testing". |
40bd05ebf1e9d686c3dc55dd3e817398 | 34.122 | 3 Definitions, abbreviations and equations | For the purposes of the present document, the definitions, symbols, abbreviations and equations used in the present document are listed in TR 21.905 [6] and TR 25.990 [7]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.