Tech-invite  3GPPspecsRELsGlossariesSIP
21222324252627282931323334353637384‑5x

Top   in Index   Prev   Next

TR 23.729SA2
Study on
Unlicensed Spectrum Offloading
System enhancements

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V15.0.0 (Wzip)  2017/09  38 p.

WI Acronym:  FS_USOS
Rapporteur:  Mr. Zisimopoulos, HarisQualcomm UK Ltd

3GPP RAN in Rel-13 has worked on integrating "unlicensed access" in RAN, including LTE-WiFi aggregation and LAA. More generically, the work is targeted at several scenarios where the UE is connected to two accesses at once, i.e., a primary access and a secondary access, where the secondary access operates in unlicensed spectrum. The secondary access may be represented by a LAA cell or a WLAN including a set of one or more WLAN APs.
The following two scenarios are considered as per the rel.14 RAN architecture (TS 36.300):
  • eNB with LTE (primary) + LTE-LAA (secondary) access.
  • eNB with LTE (primary) + WLAN (secondary) access.
In both scenarios, the mechanisms defined so far are aiming to make the aggregation of licensed and unlicensed spectrum transparent to the core network elements. In particular, S-GW, PDN GW and PCC elements are not aware of whether the data packets of a PDN or Service Data Flow are being routed (on uplink, downlink or both) on the licensed spectrum cell or the unlicensed spectrum cell.
This TR will study mechanisms to:
  • Enable the 3GPP system to differentiate traffic which was transported over unlicensed access in non-roaming and roaming cases.
  • Ensure the granularity of data collected for data usage over unlicensed access is as required in order to enable its use for the particular operating purpose (e.g. accounting, charging and network planning). Depending on the operating purpose it can be determined whether the data usage collection is e.g. "per UE" or "average across multiple UEs" etc.
For the aspects above, it is desirable to develop a common framework for LAA and for LWA/LWIP taking into account the rel.14 RAN architecture, in order to minimize the system impacts and increase flexibility of introducing the LAA and LWA/LWIP solutions in the RAN deployment of an operator.
Interaction with RAN WGs is required to assess solutions that affect the RAN. This work will provide input to SA5 for the charging aspects if any identified.

full Table of Contents for  TR 23.729  Word version:   15.0.0

Here   Top

 

1  ScopeWord-p. 6
2  References
3  Definitions and abbreviationsWord-p. 7
4  Key Issues
5  Architectural RequirementsWord-p. 9
6  Solutions
6.1  Solution #1: Use of Bearer RAT type IE per bearer for unlicensed spectrum identification
6.2  Solution #2: Reporting of secondary RAT
6.3  Solution #3: Capability indication from RAN
6.4  Solution #4: Capability indication from RANWord-p. 14
6.5  Solution #5: Unlicensed data usage reporting activation/deactivation taking node capability into accountUp
6.6  Solution #6: uplink marking and downlink counters in RAN
6.7  Solution #7: Enforce Secondary RAT Restriction at the eNB
6.8  Solution #8: Data volume collection and reporting from RAN
6.9  Solution #9: Data Usage Reporting and the reporting mechanismsWord-p. 33
6.10  Solution#10 for Key Issue #6: Unlicensed spectrum handling in PCCWord-p. 35
6.11  Solution #11: Secondary RAT identification and Secondary RAT data usage reporting (merge of solutions 4 and 8)
7  Overall EvaluationWord-p. 37
8  Conclusions
A  Change historyWord-p. 38

Up   Top