doc.: 22-14-0116-02-000b submission sep 2014 chang-woo pyo (nict)slide 1 ieee p802.22b sep 2014 plan...

doc.: 22-14-0116-02-000b

Submission

Sep 2014

Chang-woo Pyo (NICT)Slide 1

IEEE P802.22b Sep 2014 Plan & Report

IEEE P802.22 Wireless RANs Date: 2013-9-15

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 July 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 contribu-tion July be made public by IEEE 802.22. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http://standards.ieee.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards July 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 develop-ment process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair Apurva Mody <[email protected]> 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 <[email protected]>.

Name Company Address Phone email

Chang-woo Pyo NICT Japan 81-46-847-5120 [email protected]

SungHyun Hwang ETRI Korea 82-42-860-1133 [email protected]

http://standards.ieee.org/guides/bylaws/sb-bylaws.pdf

mailto:[email protected]





doc.: 22-14-0116-02-000b

Submission

Meeting Protocol

• Please announce your affiliation when you first address the group during a meeting slot

Sep 2014


doc.: 22-14-0116-02-000b

Submission

Attendee

• https://imat.ieee.org/attendance

1. Register

2. Indicate attendance

Sep 2014


https://imat.ieee.org/attendance

doc.: 22-14-0116-02-000b

Submission

Introduction

• Welcome to the IEEE P802.22b Sep, Plenary Meeting in Sandiego• TG Chairs and secretary

– Chair: Chang-woo Pyo (NICT)– Vice-chair : 　 Sunghyun Hwang (ETRI)– Recording Secretary: Gabriel (NICT)

• Recording your attendance– Send email to:

Sep 2014


doc.: 22-14-0116-02-000b

Submission

New Member

• Welcome to 802.22b TG• Introduction

Sep 2014


doc.: 22-14-0116-02-000b

Submission

802.22b Title, PAR Scope and Purpose• Title

– Enhancement for Broadband Services and Monitoring Applications

• PAR– This amendment specifies alternate Physical Layer (PHY) and necessary Medium Access Con-

trol Layer (MAC) enhancements to IEEE std. 802.22-2011 for operation in Very High Fre-quency (VHF)/ Ultra High Frequency (UHF) TV broadcast bands between 54 MHz and 862 MHz to support enhanced broadband services and monitoring applications. The standard sup-ports aggregate data rates greater than the maximum data rate supported by the IEEE Std. 802.22-2011. This standard defines new classes of 802.22 devices to address these applications and supports more than 512 devices in a network. This standard also specifies techniques to enhance communications among the devices and makes necessary amendments to the cognit-ive, security & parameters and connection management clauses. This amendment supports mechanisms to enable coexistence with other 802 systems in the same band.

• Purpose– The purpose of this amendment is to enhance the MAC and define an alternate PHY to ac-

commodate broadband extensions and monitoring use cases for IEEE 802.22 devices operating is VHF/UHF TV broadcast bands between 54 MHz and 862 MHz.

Sep 2014


doc.: 22-14-0116-02-000b

Submission

Tentative TG 802.22b Agenda for the Week

• Agenda

• Motion to approve 802.22b agenda as contained in 22-14-00114-00-000b

• Move: Chang-woo Pyo• Second: Sunghyun Hwang

• No objection. Motion passes

Sep 2014


doc.: 22-14-0116-02-000b

Submission

TGb Slot 1

• Time: Tuesday Sep 16th AM2

• Review from July• Approve minutes from July• Discussion Items• Time slot for Presentation

Sep 2014


doc.: 22-14-0116-02-000b

Submission

Review of July Meeting• Contributions

Sep 2014


Date Contributions Doc. # Presenter

Tuesday AM2

Wednesday PM1 • PHY Mode 2 (30m)• MAC (30m)

• 83/r0, 84/r0, 85/r0• 78/r0, 81/r1, 99/r0

Dr. OodoDr. Pyo

Wednesday PM2 • Security •82/r0 Ranga

Thursday AM1 • Segmentation (30 m)• MD-TCM (20m)• Multi-channel (30m)

•100/r0• 101/r0• 95/r0, 96/r0, 97/r0

Dr.HwangProf. SasakiDr. Toh

Thursday AM2

doc.: 22-14-0116-02-000b

Submission

July Minutes

• Motion to approve July 802.22b minutes as contained in 802.22-14-0118-00-000b

• Move: Chang-woo Pyo• Second: SungHyun Hwang

• No objection, Motion passes.

Sep 2014


doc.: 22-14-0116-02-000b

Submission

Review of Teleconference Calls

Sep 2014


• 31st July (Thursday)– Comment Categorization of LB2

• Frame Modifications (https://mentor.ieee.org/802.22/dcn/14/22-14-0104-00-000b-frame-modification.docx)

• 7th Aug. (Thursday)– Comment Categorization of LB2

• Frame Modifications (https://mentor.ieee.org/802.22/dcn/14/22-14-0104-00-000b-frame-modification.docx)

• 28th Aug. (Thursday)– Segmentation :

https://mentor.ieee.org/802.22/dcn/14/22-14-0100-01-000b-preamble-design-for-ieee-802-22b-segmentation.ppt

– Definitions: https://mentor.ieee.org/802.22/dcn/14/22-14-0078-01-000b-tgb-lb2-comment-resolution-for-section-3-and-4.docx

• 11th Sep. (Thursday)– MAC PDU Construction & Subheader Management:

https://mentor.ieee.org/802.22/dcn/14/22-14-0109-01-000b-mac-pdu-construction-subheader-management.docx

– Local Cell Management: https://mentor.ieee.org/802.22/dcn/14/22-14-0110-01-000b-local-cell-management.docx



https://mentor.ieee.org/802.22/dcn/14/22-14-0078-01-000b-tgb-lb2-comment-resolution-for-section-3-and-4.docx

https://mentor.ieee.org/802.22/dcn/14/22-14-0078-01-000b-tgb-lb2-comment-resolution-for-section-3-and-4.docx



https://mentor.ieee.org/802.22/dcn/14/22-14-0110-01-000b-local-cell-management.docx

doc.: 22-14-0116-02-000b

Submission

Conference Call Minutes

• Motion to approve 802.22b minutes of telecon-ferences as contained in 22-14-0117-00-000b

• Move: Chang-woo Pyo• Second: SungHyun Hwang

• No objection, Motion passes.

Sep 2014


doc.: 22-14-0116-02-000b

Submission

Discussion Items• Comment Resolution

Sep 2014


Date Contributions Doc. # Presenter

Tuesday AM2

Wednesday AM1 • Segmentation • Group Resource Allocation• MAC Comment Resolution

• 100r2• 108r0, 119r0• 81r4, 99r1, 78r3

Dr. HwangDr. HwangDr. Pyo

Wednesday AM2 • Multi-channel related to Security (30m)• MIMO Comment Resolution (CID 57)• MIMO Comment Resolution (CID 63, 64, 67, 68)

• 120r0, 121r0•122r0, 123r0

Dr. TohDr. GabrielDr. Gabriel

Wednesday PM1

Thursday AM1 • MD-TCM• PHY Mode 2

Prof. SasakiDr. Pyo

Thursday AM2 • Security and Frame Modification •82r0, 109r1, 110r2, 104r2

Dr. Pyo

doc.: 22-14-0116-02-000b

Submission

Pyo (14)ID

Commenter Name

Comment Suggested Remedy Implementation Status

5 Changwoo Pyo Access Zone is used in both PHY mode 1 and PHY mode 2, but the description is not complete for PHY mode .

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 us-ing the modulation/coding specified in 9.4.1.2 and Table 202 respectively.." 22-14-81/r4

8 Changwoo Pyo Permananent Station ID is shown in 7.7.7.3.4.12 Remove 7.7.7.3.6.12 22-14-81/r49 Changwoo Pyo CPE operational capability is shown in 7.7.7.3.4.13 Remove 7.7.7.3.6.13 22-14-81/r4

10 Changwoo Pyo Message Type = xx in Table Y1 is not defined Remove it 22-14-81/r411 Changwoo Pyo Unnecessary Information elements (Ies) in Table Y1 Remove IE 22-14-81/r412 Changwoo Pyo "Wait for Local Cell Update RSP " in figure AX1 is

unncessaryChange to "Done"

22-14-81/r416 Changwoo Pyo Timer "Txx" (Figure AQ1, Figure AR1) is not defined Define Timer "Txx" 22-14-81/r417 Changwoo Pyo Timer "Txx" (Figure AT1, AU1, AV1, AW1) is not de-

fined Define Timer "Txx"

22-14-81/r418 Changwoo Pyo Timer "Txx" (Figure AY1, AZ1) is not defined Define Timer "Txx" 22-14-81/r420 Shigenobu

SasakiAdditional definitions on Advanced BS (A-BS) and Advenced CPE (A-CPE) are necessary. It is also nec-essary to clarify the diffrence of these A-BS and A-CPE from conventional BS and CPE defiend in the IEEE 802.22-2011 main standard.

Add additional definitions on Advanced BS (A-BS) and Advenced CPE (A-CPE) . Clarification of the diffrence of these A-BS and A-CPE from conven-tional BS and CPE defiend in the IEEE 802.22-2011 main standard should be described. Creating addi-tional table to show the comparison of A-BS, A-CPE and conventional BS and CPE looks desirable. 22-14-99/r1

21 Shigenobu Sasaki

Add additional abbreviations and acronyms, if nec-essary.

Add additional abbreviations and acronyms, if nec-essary.

22-14-78/r347 Sunghyun

HwangThe "Local SID Group" in Table P1 seems same as the "SID Bitmap of Group" in Table AR1.

If right, remove subclause 7.7.7.3.6 and replace "Local SID Group" with "SID of Group". 　 22-14-81/r4

48 Sunghyun Hwang

QPSK and code rate 1/2 are not defined. The coding scheme should also be defined.

Define MCS scheme of QPSK-code rate 1/2 and cod-ing scheme to the CPE demodulator capability IE. 22-14-81/r4

49Sunghyun

Hwang

What is the purpose of "Local Cell Update" in sub-cluase 7.7.25? Is it same as the "GRA-UPD" in sub-clause 7.7.30.2?

If right, remove subclause 7.7.25 and replace "Local Cell Update" with "GRA-UPD". 　 22-14-81/r4

doc.: 22-14-0116-02-000b

Submission

Gabriel (5)

IDCommenter

NameComment Suggested Remedy

Implementation Sta-tus

57 Sunghyun Hwang

MIMO scheme is a kind of PHY layer technology.

Move properly clause 14 to clause 9 or 9a. Refer to other IEEE 802 standard.

　 22-14-122r1

63Sunghyun

Hwang

The receiver side is an implementation issue. There is no need to describe the implementation method in this sub-clause.

Remove the implementation method, such as combiner, estimator, etc. Or move it to appendix as an informative text.

　 22-14-123r1

64Sunghyun

Hwang


Remove the implementation method, such as combiner, estimator, etc. Or move it to appendix as an informative text.

, 22-14-123r1

67Sunghyun

Hwang


Remove the implementation method, such as detection, etc. Or move it to appendix as an informative text.

　 22-14-123r1

68Sunghyun

Hwang


Remove the implementation method, such as detection, etc. Or move it to appendix as an informative text.

　 22-14-123r1

doc.: 22-14-0116-02-000b

Submission

Oodo (7)ID

Commenter Name

Comment Suggested RemedyImplementation Sta-

tus38 Shigenobu

SasakiConsider to add the optional PHY mode as in subclause 9.2 in this table.

Consider to add the optional PHY mode as in subclause 9.2 in this table. 22-14-111/r1

53Sunghyun

Hwang

There is no data rate and spectral effi-ciency for MIMO and multiple channel op-eration.

Add the data rate and spectral efficiency for MIMO and multiple channel operation.

22-14-111/r156

Sunghyun Hwang

There is an incomplete subcluase, such as 9a.7.1, 9a.8.1, 9a.8.2, 9a.9.1, 9a.9.2, 9a.9.4, 9a.10, 9a.11, 9a.12, and 9a.13.

Complete the subclase in sentences.22-14-83/r0

59Sunghyun

HwangThe pilot allocation should be orthogonal for each antenna.

In the rightmost pilot pattern of Figure CE1, the pilot of symbol 0 should be null subcarrier. 22-14-84/r0

60Sunghyun

HwangThe pilot allocation should be orthogonal for each antenna.

In the rightmost pilot pattern of Figure CF1, the pilot of symbol 0 should be null subcarrier. 22-14-84/r0

79 Masayuki Oodo

In Table 198, on the row of "Data rate", the maximumm data rate is 31.78 Mbit/s. In Table GQ1, on the other hand, on the column of 1/16CP of 6MHz BW, the maxi-mum data rate is 32.12 Mbit/s. The maxi-mum data rate should be the same value. This may affect the data rate in PHY Mode2.

How to calculate the maximum data rate (for 4D-192TCM) should be made clear and the maximum data rate in Table 198 and in Table GQ1 should be the same.

22-14-111/r183 Ivan Reed My major disagreement with the draft as

it stands is the fact that the 2k FFT has been reduced to a 1k FFT. This causes problems on both channel B operation and on filtering in compliance to the FCC spectrum mask. In order to convince me of the contrary, one would have to show me simultations of a 802.22b transmitter, operating within the spectral mask re-quirements set forth by the FCC, transmit-ting through channel B and properly re-covering the transmitted data. This, in our opinion, will NOT work.

Accept in principle. Add a paragraph in the purpose of 802.22b to th e effect that "The standard has been deisgned to meet the needs required by channels A & C (check up please). In the rare cases where propagation conditions are as severe as those expressed by channels B and D, it may be required to revert to the base 802.22 2K modulation scheme.

22-14-85/r1

doc.: 22-14-0116-02-000b

Submission

Hwang (7)ID

Commenter Name

TypeComment Suggested Remedy Implementation Status

26 Shigenobu Sasaki

T In Table 202, PHY Mode 1 to 4 are re-served for 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.

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.

45

Sunghyun Hwang

T Define the local frame preamble to sup-port segmentation scheme.

For the local frame preamble, the num-ber 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/r0

58 Sunghyun Hwang T

There is no MIMO pilot pattern for PHY mode 1.

Define the MIMO pilot pattern for PHY mode 1. 22-14-124/r0

87 Ranga Reddy

TR Why have a separate GID here? This just add bits to the message.

Identify groups by the SID of the group manageer, make that the first SID in the SID bitmap of GRA-CFG message. This also applies to the GRA-UPD message

22-14-119/r0

88 Ranga Reddy

TR able AS1 does not indicate clearly if De-vice_flag and Group_Flag are both neces-sary,

Try using a message type field 2-3 bits, and structure the message accordingly.

22-14-108/r0

89 Ranga Reddy

TR the GRA-UPD doesn't allow deleting more than one CPE from the group at once. This would cause multiple Tx's to delete more than one CPE

Update message to include structure to handle deletion of more than one CPE from a group

22-14-108/r0

90 Ranga Reddy

TR here we say that the Backup/Candidate IE of DCD can be used to update a group backup/candidate list. The statement in the text here refers to modifications in table 22. Are these modifications to Ta-ble 22 even necessary, assuming that GRA methods are only applicable to dis-tributed relays, which could transmit their own DCD/UCD in their zone.

Provide text indicating that grouping should be limited to distributed relays, and we don’t need modifications to DCD. similar changes would be applicable to UCD as well.

22-14-119/r0

doc.: 22-14-0116-02-000b

Submission

Toh (9)ID

Commenter Name

TypeComment Suggested Remedy Implementation Status

19 Changwoo Pyo

T/E BS must be A-BS Change "BS" to "A-BS"22-14-95/r0

27 Shigenobu Sasaki

T Only the case of single channel and single spatial stream is mandatory. Other cases should be optional.

Add the following description: "Single channel and single spatial stream is mandatory. Other cases should be optional. " 22-14-96/r0

51

Sunghyun Hwang

T What does the "AIF" stand for?

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/r0, 22-14-121/r0

92 Ranga Reddy

TR What MIB information might be ex-changed? Also MIB info is usually ex-changed using SNMP messages trans-mitted on the Secondary Management connection

Please be specific here, or develop an amendment to the MIBs to include the objects required to operate multi-chan-nel operation (same goes for 7.24.1.1.4)

93 Ranga Reddy

TR What specific DCD IE or new manage-ment message is to be used?

Please be specific, either name the ex-isting IE/message, or define a new one to carry this information

94 Ranga Reddy

TR his section seems to detail a specific procedure that requires 2 BS-CHUs and CPE-CHUs. Are we to implying here that there can only channel aggrega-tion used across 2 channels simultane-ously at a max.

Update section to imply this is an ex-ample, or define channel aggregation as a process that aggregates up to 2 channels mostly.

95 Ranga Reddy

TR this procedure is facilitated by the CAM-STP message. Is this additional mes-sage necessary, can this not be acheived by the DREG-CMD

Consider modifications to DREG-CMD to a llow for the functionality of the CAM-STP message

96 Ranga Reddy

BS-CHU sends a CAM-SWH message to indicate a channel switch event. Is this additional message necessary, can we not initiate a switch with the DREG-REQ/CMD.or the CHS-REQ

Consider modifications to DREG-CMD/REQ message and or use of CHS-REQ method to replace usage of CAM-STP message.

97 Ranga Reddy

TR This IE doesn't indicate how many CHU's that the CPE has? How can BS al-locate/initiate more CHUs than the CPE has

Add a field or another IE that indicates how many CHUs the CPE can handle.

doc.: 22-14-0116-02-000b

Submission

Sasaki (4)

IDCommenter


Implementation Status

29 Shigenobu Sasaki

Some part of figure is not clear. Replace the figure into clearer ver-sion.

Change to edito-rial

31 Shigenobu Sasaki

K_MOD for 4D-TCM 48QAM and 4D-TCM 192QAM should be specified.

Put appropriate numbers of K__MOD.22-14-101/r0

35 Shigenobu Sasaki

Fill all the TBDs in the table. Fill all the TBDs in the table.　 22-14-125/r0

54Sunghyun

Hwang

MD-TCM is a kind of data modulation. There is no need to make subclause for MD-TCM only.

Merge subclause 9.8.1.1 to subclause 9.8.1. 　 Accept

doc.: 22-14-0116-02-000b

Submission

Ranga (2)

IDCommenter


Implementation Sta-tus

81 Ranga Reddy

There is no description here as to what modifications/updates are needed to se-curity sublayer, if needed to support new R-CPEs

Provided description and technical re-quired for security sublayer concerning R-CPEs and MR-BS operation.

22-14-82/r0,22-14-109/r1, 22-14-110/r222-14-104/r2

82 Peter Flynn A significant opportunity exists to use 802.22 for small cell backhaul applica-tions. The ability to transport 3GPP frames efficiently over an 802.22 net-work will be a highly valuable objective. It would also be highly valuable to show how LTE MAC layer would inter-operate with 802.22 MAC layer. Closer alignment with this industry standard will promote adoption of the 802.22 in the existing market place by both device manufac-turers and the wireless cellular carrier community.

Consider alignment with .5ms 3GPP frame size and super frame structure. Consider a third PHY structure which would be aligned with 3GPP frames, which is a well established industry standard (http://www.3gpp.org), to achieve a seemless integration and highest possible efficiency when used in LTE small cell backhaul.

　 Reject: Out of scope

doc.: 22-14-0116-02-000b

Submission

Motion

• Motion to approve the resolutions as indicated in the following slides (pg. 14-20) related to LB#2 comments

Move: Dr. Sunghyun Hwang

Second: Dr. Villardi Gabriel

Yes: 5

No: 0

Abstain : 0

Motion passed

May 2014


doc.: 22-14-0116-02-000b

Submission

Teleconference Plan

• Eastern Time 8pm• (Japan/Korean Time 10am)

Sep 2014


Mod Tue Wed Thu Fri Sat Sun

Sep

Oct

22 23 24 25 26 27 28

29 30 1 2 3 4 5

6 7 8 9 10 11 12

13 14 15 16 17 18 19

20 21 22 23 24 25 26

Nov 27 28 29 30 31 1 2

3 4 5 6 7 8 9

15 16 17 18 19 20 21

doc.: 22-14-0116-02-000b

Submission

802.22b Task Group Updated Timeline


Sep 2014

2012 2013 2014 2015

1 3 5 7 9 11 1 3 5 7 9 11 1 3 5 7 9 11 1 3 5 7 9 11Task Group formed x

Process document x x 　　　　　　　　　　　　　　　　　　　　　　Functional Requirements x x

Call for Proposals issued 　 x 　　　　　　　　　　　　　　　　　　　　　　Selection Criteria x x x

Technical/Informative Contributions 　　 x x x 　

Proposal presentations x 　　　　

Processing to create a working document 　 x x x x x

Draft for 1st letter ballot 　　　　 x

　

1st letter ballot completed 　　　　 x x

Comment Resolution 　　　　　 x

2nd letter ballot completed 　　　　　　

x Comment Resolution and recirculation 　　　　　　　　　　　　　 x 　　　　　　　　　　Sponsor ballot 　　　　　　　　　　　　　　 x 　　　　　　　　　Comment Resolution and recirculation 　　　　　　　　　　　　　　　 x x 　　　　　　　RevCom/NesCom Approval 　　　　　　　　　　　　　　　　　 x x 　　　　　

doc.: 22-14-0116-02-000b submission sep 2014 chang-woo pyo (nict)slide 1 ieee p802.22b sep 2014 plan...

Documents