to Per User Figure mapping is Info instead: into wrong and For MU-BAR, Per User therefore it needs to Info's the text carry several Trigger needs to BARs Dependent be targeted to Per User modified. several Info Proposed STAs. The subfield resolution current instead. is to mapping is And fix the specify that wrong. subclause the Type Instead, for 9.3.1.23.1 depended MU-BAR, its text to common Common info describe info field’s field's Tigger the new length is 0. Dependent mapping (a The BAR Common Info technical Control field can be contribution information omitted, or will be and BAR defined for followed Information other later) is mapped purpose. And to Type map the depended current Per User defined Info Trigger subfield. Dependent Common Info field into each STAs' Per User Info fields, and hence map the BAR Control & BAR Information subfields into Per User Info's Trigger Dependent Per User Info subfield. (A technical contribution will be followed later) 2220 Tomoko 22.01 The Correct the Revised. Adachi explanation explanation Current of the of the text in variant section needs to be variant. 9.3.1.23.1 reconsidered. is removed Figure 9-51d and text as is completely specified in the same current with Figure
to Per User Info instead: For MU-BAR, it needs to carry several BARs targeted to several STAs. The current mapping is wrong. Instead, for MU-BAR, its Common info field's Tigger Dependent Common Info field can be omitted, or defined for other purpose. And map the current defined Trigger Dependent Common Info field into each STAs' Per User Info fields, and hence map the BAR Control & BAR Information subfields into Per User Info's Trigger Dependent Per User Info subfield. (A technical contribution will be followed later) Figure into Per User Info's Trigger Dependent Per User Info subfield instead. And fix the subclause 9.3.1.23.1 text to describe the new mapping (a technical contribution will be followed later) mapping is wrong and therefore the text needs to be modified. Proposed resolution is to specify that the Type depended common info field’s length is 0. The BAR Control information and BAR Information is mapped to Type depended Per User Info subfield. 2220 Tomoko Adachi 22.01 The explanation of the variant needs to be reconsidered. Figure 9-51d is completely the same with Figure Correct the explanation of the variant. Revised. Current text in section 9.3.1.23.1 is removed and text as specified in current
11-16-1241-01-00ax-crs-on-mu-bar-part2.docx