tech-invite   World Map     

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

Top          in Index          Prev          Next

draft-TR 23.729 (SA2)
Study on unlicensed spectrum offloading system enhancements

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V0.4.0    2017/06    37 p.


Rapporteur:  Mr. Zisimopoulos, Haris
See also:  –


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.


 

Here          Top

 

1 Scope    2 References    3 Definitions and abbreviations    3.1 Definitions    3.2 Abbreviations    4 Key Issues    4.1 Key Issue #1: Unlicensed spectrum identification handling in EPS    4.2 Key Issue #2: Unlicensed spectrum identification handling for IMS    4.3 Key Issue #3: Unlicensed data usage reporting activation/deactivation    4.4 Key Issue #4: Unlicensed spectrum data usage reporting mechanisms    4.5 Key Issue #5: Secondary RAT Restriction feature handling in EPS    4.6 Key Issue #6: Unlicensed spectrum charging handling    4.x Key Issue #x: <Title>    5 Architectural Requirements    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 RAN    6.5 Solution #5: Unlicensed data usage reporting activation/deactivation taking node capability into account    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 mechanisms    6.10 Solution#10 for Key Issue #6: Unlicensed spectrum handling in PCC    6.11 Solution #11: Secondary RAT identification and Secondary RAT data usage reporting (merge of solutions 4 and 8)    6.x Solution #x: <Solution Title>    7 Overall Evaluation    8 Conclusions    A Change history   

 

1   Scope   Word-p. 6
2   References
3   Definitions and abbreviations   Word-p. 7
4   Key Issues
5   Architectural Requirements
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 RAN   Word-p. 14
6.5   Solution #5: Unlicensed data usage reporting activation/deactivation taking node capability into account
6.6   Solution #6: uplink marking and downlink counters in RAN
6.7   Solution #7: Enforce Secondary RAT Restriction at the eNB   Word-p. 27
6.8   Solution #8: Data volume collection and reporting from RAN      Up
6.9   Solution #9: Data Usage Reporting and the reporting mechanisms
6.10   Solution#10 for Key Issue #6: Unlicensed spectrum handling in PCC
6.11   Solution #11: Secondary RAT identification and Secondary RAT data usage reporting (merge of solutions 4 and 8)
6.x   Solution #x: <Solution Title>
7   Overall Evaluation
8   Conclusions   Word-p. 36
A   Change history   Word-p. 37

Up          Top