Sep 2014 doc 22 14 0112 00 000

  • Slides: 15
Download presentation
Sep. 2014 doc. : 22 -14 -0112 -00 -000 b IEEE P 802. 22

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b IEEE P 802. 22 b Teleconferences IEEE P 802. 22 Wireless RANs Date: 2014 -9 -11 Authors: Notice: This document has been prepared to assist IEEE 802. 22. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802. 22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures , including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard. " Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair Apurva Mody as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802. 22 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at . Submission Slide 1 Chang-woo Pyo (NICT)

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Abstract • This presentation

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Abstract • This presentation is the agenda for the Sep, 11 th , 2014 IEEE 802. 22 b teleconference. Submission Slide 2 Chang-woo Pyo (NICT)

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Agenda: Teleconference Sep. 11

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Agenda: Teleconference Sep. 11 th, 09: 00 PM-10: 00 PM EDT • Introduction (1 min) • IEEE patent policy (1 min) • Issues to discuss – Comment Resolution for LB 2 • Any other business • Adjourn (1 min) Submission Slide 3 Chang-woo Pyo (NICT)

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Introduction • Welcome to

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Introduction • Welcome to the IEEE P 802. 22 b Sep. 11 th, 2014 teleconference • Chairs and secretary – Chair: Chang-woo Pyo (NICT) – Vice-chair : Syunghyun Hwang (ETRI) – Recording Secretary: • Recording your attendance – Send email to: Submission Slide 4 Chang-woo Pyo (NICT)

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b IEEE Patent Policy •

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b IEEE Patent Policy • http: //standards. ieee. org/board/pat-slideset. pdf Submission Slide 5 Chang-woo Pyo (NICT)

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Comment Resolution • Current

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Comment Resolution • Current Comment Resolution Status – – – – Submission Pyo : 14 comments Gabriel : 5 Comments Oodo : 7 Comments Hwang: 7 Comments Toh : 9 Comments Sasaki : 4 Comments Ranga : 2 Comments Slide 6 Chang-woo Pyo (NICT)

doc. : 22 -14 -0112 -00 -000 b Pyo (14) ID 5 8 9

doc. : 22 -14 -0112 -00 -000 b Pyo (14) ID 5 8 9 10 11 12 16 17 18 20 21 Commenter Name Changwoo Pyo Sunghyun Hwang 49 Suggested Remedy Implementation Status Add the following description at the begining "At the beginning of every superframe in AZ on PHY mode 1, the A-BS shall transmit the superframe preamble and the SCH on the operating channel using the modulation/coding specified in 9. 4. 1. 2 and Table 202 respectively. . " 22 -14 -81/r 2 Changwoo Pyo Permananent Station ID is shown in 7. 7. 7. 3. 4. 12 Remove 7. 7. 7. 3. 6. 12 22 -14 -81/r 2 Changwoo Pyo CPE operational capability is shown in 7. 7. 7. 3. 4. 13 Remove 7. 7. 7. 3. 6. 13 22 -14 -81/r 2 Changwoo Pyo Message Type = xx in Table Y 1 is not defined Remove it 22 -14 -81/r 2 Changwoo Pyo Unnecessary Information elements (Ies) in Table Y 1 Remove IE 22 -14 -81/r 2 Changwoo Pyo "Wait for Local Cell Update RSP " in figure AX 1 is unncessary Change to "Done" 22 -14 -81/r 2 Changwoo Pyo Timer "Txx" (Figure AQ 1, Figure AR 1) is not defined Define Timer "Txx" 22 -14 -81/r 2 Changwoo Pyo Timer "Txx" (Figure AT 1, AU 1, AV 1, AW 1) is not defined Define Timer "Txx" 22 -14 -81/r 2 Changwoo Pyo Timer "Txx" (Figure AY 1, AZ 1) is not defined Define Timer "Txx" 22 -14 -81/r 2 Shigenobu Sasaki Additional definitions on Advanced BS (A-BS) and Advenced Add additional definitions on Advanced BS (A-BS) and CPE (A-CPE) are necessary. It is also necessary to clarify the Advenced CPE (A-CPE). Clarification of the diffrence of these A-BS and A-CPE from conventional BS and CPE defiend in the IEEE 802. 22 -2011 main standard should be described. Creating additional table to show the comparison of A-BS, A-CPE and conventional BS and CPE looks desirable. 22 -14 -99/r 0 Shigenobu Sasaki Add additional abbreviations and acronyms, if necessary. 47 48 Comment Access Zone is used in both PHY mode 1 and PHY mode 2, but the description is not complete for PHY mode. The "Local SID Group" in Table P 1 seems same as the "SID If right, remove subclause 7. 7. 7. 3. 6 and replace "Local SID Bitmap of Group" in Table AR 1. Group" with "SID of Group". QPSK and code rate 1/2 are not defined. The coding scheme should also be defined. What is the purpose of "Local Cell Update" in subcluase Sunghyun Hwang 7. 7. 25? Is it same as the "GRA-UPD" in subclause 7. 7. 30. 2? Sunghyun Hwang Submission Define MCS scheme of QPSK-code rate 1/2 and coding scheme to the CPE demodulator capability IE. If right, remove subclause 7. 7. 25 and replace "Local Cell Update" with "GRA-UPD". 22 -14 -78/r 1  Reject. Local Cell is not the same concept of Group, thus Local SID Group is required  22 -14 -81/r 2  Reject. Local cell updata is

doc. : 22 -14 -0112 -00 -000 b Gabriel (5) ID 57 63 64

doc. : 22 -14 -0112 -00 -000 b Gabriel (5) ID 57 63 64 67 68 Commenter Comment Name Sunghyun MIMO scheme is a kind of PHY layer Hwang technology. The receiver side is an implementation issue. Sunghyun There is no need to describe the Hwang implementation method in this subclause. Submission Implementation Status Suggested Remedy Move properly clause 14 to clause 9 or 9 a. Refer to other IEEE 802 standard. Remove the implementation method, such as combiner, estimator, etc. Or move it to appendix as an informative text. Remove the implementation method, such as detection, etc. Or move it to appendix as an informative text.      

doc. : 22 -14 -0112 -00 -000 b Oodo (7) Commenter Name 38 Shigenobu

doc. : 22 -14 -0112 -00 -000 b Oodo (7) Commenter Name 38 Shigenobu Sasaki 53 Sunghyun Hwang 56 Sunghyun Hwang ID 59 60 79 83 Comment Suggested Remedy Implementation Status  22 -14 -xx/r 0 Consider to add the optional PHY mode as in subclause 9. 2 in this table. There is no data rate and spectral efficiency for Add the data rate and spectral efficiency for MIMO  22 -14 -xx/r 0 MIMO and multiple channel operation. There is an incomplete subcluase, such as 9 a. 7. 1, 9 a. 8. 2, 9 a. 9. 1, 9 a. 9. 2, 9 a. 9. 4, 9 a. 10, 9 a. 11, Complete the subclase in sentences. 9 a. 12, and 9 a. 13. 22 -14 -83/r 0 Sunghyun The pilot allocation should be orthogonal for each In the rightmost pilot pattern of Figure CE 1, the Hwang antenna. pilot of symbol 0 should be null subcarrier. 22 -14 -84/r 0 Sunghyun The pilot allocation should be orthogonal for each In the rightmost pilot pattern of Figure CF 1, the Hwang antenna. pilot of symbol 0 should be null subcarrier. 22 -14 -84/r 0 Masayuki Oodo In Table 198, on the row of "Data rate", the How to calculate the maximum data rate (for 4 Dmaximumm data rate is 31. 78 Mbit/s. In Table GQ 1, 192 TCM) should be made clear and the maximum on the other hand, on the column of 1/16 CP of data rate in Table 198 and in Table GQ 1 should be 6 MHz BW, the maximum data rate is 32. 12 Mbit/s. the same. The maximum data rate should be the same value.  22 -14 -xx/r 0 This may affect the data rate in PHY Mode 2. Ivan Reed My major disagreement with the draft as it Accept in principle. Add a paragraph in the purpose 22 -14 -85/r 0 stands is the fact that the 2 k FFT has been of 802. 22 b to th e effect that "The standard has reduced to a 1 k FFT. This causes problems on been deisgned to meet the needs required by both channel B operation and on filtering in channels A & C (check up please). In the rare compliance to the FCC spectrum mask. In order to cases where propagation conditions are as severe convince me of the contrary, one would have to as those expressed by channels B and D, it may be show me simultations of a 802. 22 b transmitter, required to revert to the base 802. 22 2 K operating within the spectral mask requirements modulation scheme. set forth by the FCC, transmitting through channel B and properly recovering the transmitted data. This, in our opinion, will NOT work. Submission

doc. : 22 -14 -0112 -00 -000 b Hwang (7) Commenter Type Comment Name

doc. : 22 -14 -0112 -00 -000 b Hwang (7) Commenter Type Comment Name 26 Shigenobu T In Table 202, PHY Mode 1 to 4 are reserved for Sasaki SCH, FCH, etc. These PHY mode should be retained as it is in the modified tables. It is not necessary to list all data rate corresponding to differennt CP in the tables. ID 45 Sunghyun Hwang 58 Sunghyun Hwang 87 Ranga Reddy 88 Ranga Reddy 89 Ranga Reddy 90 Ranga Reddy Submission Define the local frame preamble to support T segmentation scheme. Suggested Remedy Implementation Status PHY mode number should start from 5 (five) in the new tables. Pick up just one or two cases of CP ratio, and remove rest of them from data rate tables. I suggest to cover at least 1/16 CP, and 1/4 CP as an option. Accept: PHY mode number should start from 5 (five) in the new tables. Reject : : Pick up just one or two cases of CP ratio, and remove rest of them from data rate tables. I suggest to cover at least 1/16 CP, and 1/4 CP as an option. For the local frame preamble, the number of PN sequence should be defined considering the number of the used subcarriers for PHY mode 1 and PHY mode 2, respectively. 22 -14 -100/r 0 T There is no MIMO pilot pattern for PHY mode 1. Define the MIMO pilot pattern for PHY mode 1. TR Why have a separate GID here? This just add bits Identify groups by the SID of the group manageer, to the message. make that the first SID in the SID bitmap of GRACFG message. This also applies to the GRA-UPD message TR able AS 1 does not indicate clearly if Device_flag Try using a message type field 2 -3 bits, and 22 -14 -108/r 0 and Group_Flag are both necessary, structure the message accordingly. TR the GRA-UPD doesn't allow deleting more than Update message to include structure to handle 22 -14 -108/r 0 one CPE from the group at once. This would deletion of more than one CPE from a group cause multiple Tx's to delete more than one CPE TR here we say that the Backup/Candidate IE of Provide text indicating that grouping should be DCD can be used to update a group limited to distributed relays, and we don’t need backup/candidate list. The statement in the text modifications to DCD. similar changes would be here refers to modifications in table 22. Are applicable to UCD as well. these modifications to Table 22 even necessary, assuming that GRA methods are only applicable to distributed relays, which could transmit their own DCD/UCD in their zone.

doc. : 22 -14 -0112 -00 -000 b Toh (9) Commenter Type Comment Name

doc. : 22 -14 -0112 -00 -000 b Toh (9) Commenter Type Comment Name 19 Changwoo Pyo T/E BS must be A-BS 27 Shigenobu T Only the case of single channel and single Sasaki spatial stream is mandatory. Other cases should be optional. 51 Sunghyun T What does the "AIF" stand for? Hwang ID 92 Ranga Reddy TR 93 Ranga Reddy TR 94 Ranga Reddy TR 95 Ranga Reddy TR 96 Ranga Reddy 97 Ranga Reddy Submission TR Suggested Remedy Implementation Status Change "BS" to "A-BS" 22 -14 -95/r 0 Add the following description: "Single channel and single spatial stream is mandatory. Other cases should be optional. " 22 -14 -96/r 0 Like the other abbrevations, such as STP(stop operating channel) and SWH(switch operating channel), change AIF to ADD(add operating channel). 22 -14 -97/r 0 What MIB information might be exchanged? Also. Please be specific here, or develop an MIB info is usually exchanged using SNMP amendment to the MIBs to include the objects messages transmitted on the Secondary required to operate multi-channel operation Management connection (same goes for 7. 24. 1. 1. 4) What specific DCD IE or new management Please be specific, either name the existing message is to be used? IE/message, or define a new one to carry this information his section seems to detail a specific procedure Update section to imply this is an example, or that requires 2 BS-CHUs and CPE-CHUs. Are define channel aggregation as a process that we to implying here that there can only channel aggregates up to 2 channels mostly. aggregation used across 2 channels simultaneously at a max. this procedure is facilitated by the CAM-STP Consider modifications to DREG-CMD to a llow message. Is this additional message necessary, for the functionality of the CAM-STP message can this not be acheived by the DREG-CMD BS-CHU sends a CAM-SWH message to Consider modifications to DREG-CMD/REQ indicate a channel switch event. Is this message and or use of CHS-REQ method to additional message necessary, can we not replace usage of CAM-STP message. initiate a switch with the DREG-REQ/CMD. or the CHS-REQ This IE doesn't indicate how many CHU's that Add a field or another IE that indicates how the CPE has? How can BS allocate/initiate many CHUs the CPE can handle. more CHUs than the CPE has

doc. : 22 -14 -0112 -00 -000 b Sasaki (4) ID 29 31 35

doc. : 22 -14 -0112 -00 -000 b Sasaki (4) ID 29 31 35 54 Commenter Comment Name Shigenobu Some part of figure is not clear. Sasaki Shigenobu K_MOD for 4 D-TCM 48 QAM and 4 D-TCM Sasaki 192 QAM should be specified. Shigenobu Fill all the TBDs in the table. Sasaki MD-TCM is a kind of data modulation. There Sunghyun is no need to make subclause for MD-TCM Hwang only. Submission Implementation Status Suggested Remedy Replace the figure into clearer version. Change to editorial Put appropriate numbers of K__MOD. 22 -14 -101/r 0 Fill all the TBDs in the table.   Merge subclause 9. 8. 1. 1 to subclause 9. 8. 1.  Accept

doc. : 22 -14 -0112 -00 -000 b Ranga (2) Commenter Implementation Comment Suggested

doc. : 22 -14 -0112 -00 -000 b Ranga (2) Commenter Implementation Comment Suggested Remedy Name Status 81 Ranga Reddy There is no description here as to what Provided description and technical required for 22 -14 -82/r 0, modifications/updates are needed to security sublayer concerning R-CPEs and MR- 22 -14 -109/r 0 sublayer, if needed to support new R-CPEs BS operation. 22 -14 -104/r 2 82 Peter Flynn A significant opportunity exists to use 802. 22 for Consider alignment with. 5 ms 3 GPP frame size small cell backhaul applications. The ability to and super frame structure. Consider a third PHY transport 3 GPP frames efficiently over an 802. 22 structure which would be aligned with 3 GPP network will be a highly valuable objective. It frames, which is a well established industry would also be highly valuable to show LTE standard (http: //www. 3 gpp. org), to achieve a MAC layer would inter-operate with 802. 22 MAC seemless integration and highest possible layer. Closer alignment with this industry efficiency when used in LTE small cell backhaul. standard will promote adoption of the 802. 22 in the existing market place by both device manufacturers and the wireless cellular carrier   community. ID Submission

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Teleconference Plan Mod July

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b Teleconference Plan Mod July Aug Sep Tue 21 28 4 11 18 25 1 8 15 Wed 22 29 5 12 19 26 2 9 16 Thu 23 30 6 13 20 27 3 10 17 Fri 24 31 7 14 21 28 4 11 18 Sat 25 1 8 15 22 29 5 12 19 Sun 26 2 9 16 23 30 6 13 20 27 3 10 17 24 31 7 14 21 • Eastern Time 8 pm • (Japan/Korean Time 10 am) Submission Slide 14 Chang-woo Pyo (NICT)

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b 802. 22 b Task

Sep. 2014 doc. : 22 -14 -0112 -00 -000 b 802. 22 b Task Group Updated Timeline 2012 1 3 5 x Process document x x     Functional Requirements x x Call for Proposals issued   x     Technical/Informative Contributions 7 9 11 2014 Task Group formed Selection Criteria x x x 1 3 5 7 9 11 1 3 5 7 9 11             x x x x x           x    x                         x         x x x x     Processing to create a working document   x x x Draft for 1 st letter ballot     1 st letter ballot completed x       x x Comment Resolution       2 nd letter ballot completed       Rev. Com/Nes. Com Approval 11 Comment Resolution and recirculation 1 3 5 7 9 Sponsor ballot 2015 Proposal presentations Comment Resolution and recirculation Submission 2013 x x x       Slide 15       Chang-woo Pyo (NICT)