1. July 2010
doc.: IEEE /0xxxr0
A summary of draft LS from 3GPP in response to IEEE 802 LS in March 2-017
1 May 2017
Authors:
Name
Company
Phone
Andrew Myles
Cisco
Andrew Myles, Cisco
Andrew Myles, Cisco

2. 802.19 WG needs to decide on how to deal with latest and future LS’s from 3GPP RAN1
Executive summary
IEEE 802 and 3GPP RAN/RAN1 have been playing “LS ping pong” for more almost three years
The next “shots” (LSs) from 3GPP RAN1 are still in draft form
As of 1 May 2017
Some issues are still not resolved, but others are resolved or heading in that direction
There is still fundamental disagreement between 3GPP and IEEE 802 on “blocking energy” and “ED” issues
Should IEEE 802 focus on resolving the important open issues with ETSI BRAN rather than 3GPP?
Andrew Myles, Cisco

3. IEEE 802 and 3GPP have been playing “LS ping pong” for almost three years …
Jun 2014: Reply LS on Areas of Mutual Interest to 802 LMSC and 3GPP
Jul 2014: Areas of Mutual Interest to 802 LMSC and 3GPP
Sep 2014: Licensed-Assisted Access using LTE
Nov 2014: Coexistence Lessons Learned
Mar 2015: Regarding Coexistence of Licensed Assisted Access (LAA) and IEEE 802
Jan 2015: Statement Regarding Coexistence of Licensed Assisted Access (LAA) and IEEE 802
Apr 2015: Coexistence
Mar 2015: Regarding 1) Clarification of LBT Categories and 2) LAA / Coexistence
Apr 2015: Clarification of LBT Categories
May 2015: Follow-up Liaison Statement Regarding LAA
Next page
Andrew Myles, Cisco

4. … IEEE 802 and 3GPP have been playing “LS ping pong” for almost three years …
Jun 2015: LS on LAA capabilities and scope
Previous page
Jun 2015: 3GPP RAN Workshop on Licensed-Assisted Access (LAA)
Jun 2015: LS on LAA capabilities and scope
Aug 2015: presentation at 29-Aug-15 LAA Workshop
Dec 2015: LAA CRs
Mar 2016: Comments related to the LAA Specification
Jun 2016: Response Liaison Statement to 802 regarding LAA
May 2016: Review of 3GPP LAA Specification Rel. 13
Jun 2016: Response Liaison Statement to 802 regarding LAA
Next page
Andrew Myles, Cisco

5. … IEEE 802 and 3GPP have been playing “LS ping pong” for almost three years
Previous page
July 2016: Review of 3GPP LAA Specification Rel. 13
Nov 2015: Response LS to IEEE regarding LAA
Nov 2016: LS related to ED issue
(developed by PDED ad hoc)
Apr 2015: Draft LS response to IEEE regarding non-ED issues
Today
Mar 2017: LS related to non-ED issues
Apr 2015: Draft LS response LS to IEEE regarding ED issues
Mar 2017: LS related to ED issues
(developed by PDED ad hoc)
May 2017: non-ED issues
(IEEE )
May 2017: ED issues
(IEEE PDED ad hoc)
Andrew Myles, Cisco

6. The next “shots” (LSs) from 3GPP RAN1 are still in draft form
3GPP RAN1 has been developing separate responses to the two LS’s that IEEE 802 sent in March on ED and non-ED issues
The drafts as of 1 May are embedded below
Non-ED issues: ED issues:
It appears that it is unlikely that these drafts will be approved until the next RAN1 meeting (15-19 May) because there are too many open issues
The draft editor wrote on 28 April 2017, “However, there are many major open issues which need to be resolved and I see that there is no agreement among the companies. I would request that we continue this discussion in the next RAN1 meeting as I don't see a possibility of resolution over . Hopefully some F2F discussion can help in this regard.”
Andrew Myles, Cisco

7. Some issues are still not resolved, but others are resolved or heading in that direction
The following slides contain a high level summary of the state of affairs based on the draft LS from 3GPP to IEEE 802 on non-ED issues
The high level summary is the current view of the author of this document
Key for “Issue resolved?” column:
 : not resolved
 : not resolved, but not clear very important
 : heading towards resolution
 : resolved
The draft responses from 3GPP to Issues 3 & 13 (the ED-issues) will be discussed in IEEE PDED ad hoc on Wednesday at PM1
Andrew Myles, Cisco

8. Some issues are still not resolved, but others are resolved or heading in that direction
IEEE 802 comment
Draft 3GPP response
Issue resolved? 1
Requested details on mechanisms to minimise blocking energy
Continues to claim that blocking energy is legitimate, without addressing IEEE 802 comments on the issue
Again notes that blocking energy is not part of standards, but others note it is part of “LAA agreements”
Don’t seem to have agreed on minimisation statement despite promising it in last LS
Notes multiple start positions (and lengths) WI is part of Rel15, scheduled for Dc 2017  2
Suggested wait for field experience on DRS overhead
Thanks IEEE 802 for its understanding.  3
See IEEE PDED discussion 4
Requested 3GPP RAN4 test for slot alignment issues
Declines the request on basis there is no evidence any slot alignment issues
Andrew Myles, Cisco

9. Some issues are still not resolved, but others are resolved or heading in that direction
IEEE 802 comment
Draft 3GPP response
Issue resolved? 5
Requested 3GPP RAN4 test for multi-channel issues
May further discuss alignment with various aspects of multi-carrier transmission and adopting the proposed scheme in ETSI BRAN  6
Requested details on mechanisms to support multiple ending positions
Notes work specifying the multiple starting and ending positions has already begun in RAN1 fro Rel-15 and expected to finish in Dec 2017
Notes mandatory/optional questions will be discussed in Jun2 0918
Notes shortened TTI is not in scope of Rel-15 7
Requested details on mechanisms to support multiple starting/ending positions 8
Requested 3GPP RAN4 test for TxOP limits
Notes RAN1 may discuss adopting the ETSI BRAN TxOP limits and also mechanisms for increasing the length to 8ms and 10ms as specified in ETSI BRAN
Did not respond to RAN4 question
Andrew Myles, Cisco

10. Some issues are still not resolved, but others are resolved or heading in that direction
IEEE 802 comment
Draft 3GPP response
Issue resolved? 9
Requested 3GPP RAN4 test for coexistence with medium to high loads
Declines the request on basis there is no evidence there are any issues medium to high loads  10
No action required  11 12
Requested LAA monitor channel to maintain synchronisation
Notes that while the exact details are up to implementation, an eNB is reasonably expected to actively monitor the medium 13
See IEEE PDED discussion 14
Noted no response to request for continued dialog
Notes that they welcome communication and continued dialog with IEEE 802
Notes that 3GPP RAN may discuss any further response in upcoming plenary meetings
Andrew Myles, Cisco

11. Should IEEE 802 focus on resolving the important open issues with ETSI BRAN rather than 3GPP?
There are three important issues for which there is significant disagreement and no obvious path to consensus
Issue 1: Blocking energy issues
Issues 3 & 13: ED/PD issues
It is interesting to note that both of these issues are probably within scope for the next ETSI BRAN revision of EN
Should IEEE 802 transition to working with ETSI BRAN (essentially the regulator in Europe, but with global impact) rather than 3GPP RAN1/RAN4?
There is probably more chance of success with ETSI BRAN (some) rather than 3GPP RAN1/RAN4 (almost none)
Any agreement within ETSI BRAN is enforceable, unlike agreements with 3GPP RAN1/RAN4 (noting that 3GPP broke the fundamental agreements with IEEE 802 from the original LAA Workshop in September 2015)
Andrew Myles, Cisco