Index,Date,SA PIN,Name,Comment,Category,Page Number,Subclause,Line Number,Proposed Change,Must Be Satisfied
1,05/27/2014 15:44:54 GMT,54827,Tim Godfrey,"The identifier ""gap.safety"" is an unusual syntax. Is is supposed to be ""gap/safety""?",General,69,17.3.1.2,62,"Clarify, or add definition if different than normal meaning for DIUC=13 Gap",0
2,05/27/2014 15:50:56 GMT,54827,Tim Godfrey,"The sentence: ""For interference mitigation of DL, the BS may make the best use of empty region to zero energy region"" is unclear.",General,70,17.3.1.2,5,"Is this the intended meaning?
""For interference mitigation of DL, the BS may make the best use of opportunities to convert empty regions to zero energy regions""",0
3,05/30/2014 20:23:00 GMT,3074,Roger Marks,Paragraph grammar and clarity could be improved.,Editorial,2,1.9,9,"Change to ""Multi-tier networks utilize base stations of a variety of power level tiers in order to improve network capacity and efficiently manage radio resources, in comparison to networks using only macro base stations of a uniform power level tier. In such multi-tier networks, coordination techniques among subscriber stations, among base stations across multiple tiers, and among base stations in the same tier are important to achieve system capacity enhancements. Interference mitigation techniques across tiers is also critical to achieving user throughput enhancements.""",1
4,05/30/2014 20:23:00 GMT,3074,Roger Marks,Paragraph grammar and clarity could be improved.,Editorial,2,1.9,17,"Change to ""Multi-tier network operation is specified in this standard to support efficient cooperation among base stations in multi-tier networks in order to enhance interference mitigation and mobility management, with base station power management. Associated management protocol among base stations and among base stations and mobile stations enables efficient cooperation and coordination. Multi-tier network operation is supported by a specific set of MAC management messages, without physical layer customization of mobile stations. This standard address two tiers of network, with higher-power base stations known as macro BSs, capable of signaling to lower-power stations, known as small BSs.""",1
5,05/30/2014 20:23:00 GMT,3074,Roger Marks,missing definition,Editorial,4,3,9,macro BS: a BS that controls at least one small BS,1
6,05/30/2014 20:23:00 GMT,3074,Roger Marks,missing definition,Editorial,4,3,9,"small BS: a BS controlled by at least one macro BS, typically transmitting with less power than a macro BS [but ""controlled"" should be expanded to something more definite]",1
7,05/30/2014 20:23:00 GMT,3074,Roger Marks,missing definition,Editorial,4,3,9,Open Subscriber Group:,1
8,05/30/2014 20:23:00 GMT,3074,Roger Marks,missing definition,Editorial,4,3,9,Closed Subscriber Group:,1
9,05/30/2014 20:23:00 GMT,3074,Roger Marks,missing term,Editorial,5,4,21,FA frequency assignment,1
10,05/30/2014 20:23:00 GMT,3074,Roger Marks,"""a governmental body like FCC"" is unclear and needlessly references a specific example (even if similar language is used in base standard)",Editorial,24,11.18.3,48,"change to ""an appropriate regulator""",1
11,05/30/2014 20:23:00 GMT,3074,Roger Marks,"There is an editorial issue here (through line 48): some elements are underlined, which appears to indicate that they are additional to the standard, even though the content is identical to the standard.",Editorial,30,14.1.1,21,Remove underlining unrelated to changes.,1
12,05/30/2014 20:23:00 GMT,3074,Roger Marks,"""is set to Get for request operation"" is unclear",Editorial,32,14.1.2.1,49,"change to ""= Get, then""",1
13,05/30/2014 20:23:00 GMT,3074,Roger Marks,"""only"" is unneeded",Editorial,32,14.1.2.1,50,"delete ""only""",1
14,05/30/2014 20:23:00 GMT,3074,Roger Marks,"""Otherwise if Attribute_list is present, Attribute_list is Array of the pair"" is too long and confusing",Editorial,32,14.1.2.1,51,"change to ""Otherwise Attribute_list (if present) is array of the pairs (Attribute_ID, Attribute_value)""",1
15,05/30/2014 20:23:00 GMT,3074,Roger Marks,"""If Attribute_list is present, Attribute_list is Array of pair (Attribute_ID, Attribute_value)"" is confusing",Editorial,33,14.1.2.2,57,"change to ""Attribute_list (if present) is array of the pairs (Attribute_ID, Attribute_value)""",1
16,05/30/2014 20:23:00 GMT,3074,Roger Marks,"""service provider"" is not a defined term; however, it may (or may not) mean the same thing as the specific term ""network service provider"". It is better to use a less specific term that is used in the base standard.",Editorial,39,14.2.12.2.2.4,48,"change ""service provider"" to ""operator"" throughout the draft",1
17,05/30/2014 20:23:00 GMT,3074,Roger Marks,"What exactly does ""controlled by"" mean here? This is not at all obvious. It needs to be more clear in this sentence.",Editorial,63,17.1,11,"Explained ""controlled by"" here.",1
18,05/30/2014 20:23:00 GMT,3074,Roger Marks,"This draft does indicate how a small BS could be controlled by an ""ASN gateway""; in fact, it cannot, because no ASN gateway is specified.",Editorial,63,17.1,11,"delete ""or an ASN gateway""",1
19,05/30/2014 20:23:01 GMT,3074,Roger Marks,"Nothing after the first sentence of this paragraph is relevant to the standard, and many of the terms are not defined here.",Editorial,63,17.1,13,"""Small BSs provide different cell coverage and perform different roles according to their types. For example, a Femto BS is typically installed by a subscriber and/or the access provider. The Femto BS is typically connected to the service providerOs network subscriber in the home or SOHO to provide the access to closed or open groups of users as configured by the via one (or multiple) wired and/or wireless broadband connection (cable, DSL, WirelessMAN-OFDMA systems, etc.)""",1
20,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""public users like an Open Subscriber Group (OSG)"" is incorrect because it confuses users with groups",Editorial,63,17.1,25,"change ""like"" to ""in""",1
21,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""serve a Closed Subscriber Group (CSG)"" is incorrect because it confuses users with groups",Editorial,63,17.1,25,"change to ""serve private users in a Closed Subscriber Group (CSG).""",1
22,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""which is a set of subscribers authorized by the small BS owner or the network service provider"" includes needlessly restrictive information about who does the authorizing",Editorial,63,17.1,27,"change to ""which comprises a set of authorized subscribers""",1
23,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""CSG can be modified by the service level agreement between the subscriber and the network service provider."" is irrelevant",Editorial,63,17.1,28,"delete ""CSG can be modified by the service level agreement between the subscriber and the network service provider.""",1
24,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""may belong"" is meaningless",Editorial,63,17.1.1,35,"change to ""belongs""",1
25,05/30/2014 20:23:01 GMT,3074,Roger Marks,""", which are"" unintentionally alters the meaning",Editorial,63,17.1.1,37,"delete "", which are""",1
26,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""CSG-Closed small BS:"" is the wrong heading, because this is a list of ""subscription types""",Editorial,63,17.1.1,37,"change ""CSG-Closed small BS:"" to ""CSG-Closed subscription type""",1
27,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""CSG-Open small BS:"" is the wrong heading, because this is a list of ""subscription types""",Editorial,63,17.1.1,41,"change ""CSG-Open small BS:"" to ""CSG-Open subscription type""",1
28,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""OSG (Open Subscriber Group) small BS:"" is the wrong heading, because this is a list of ""subscription types""",Editorial,63,17.1.1,46,"change ""OSG (Open Subscriber Group) small BS:"" to ""OSG subscription type""",1
29,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""An OSG small BS is accessible to any MS."" is incorrect; some MSs are not allowed.",Editorial,63,17.1.1,46,"change to ""An OSG small BS is an MS without CSG membership requirements.""",1
30,05/30/2014 20:23:01 GMT,3074,Roger Marks,capitalize heading,Editorial,63,17.1.2,49,capitalize heading,1
31,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""Power-On"" seems to imply a defined term, but it is not.",Editorial,63,17.1.2,52,"change ""On Power-On"" to ""Upon startup""",1
32,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""should be"" is not specific enough",Editorial,63,17.1.2,55,"change ""should be"" to ""are""",1
33,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""service providers network"" is not specific enough",Editorial,63,17.1.2,57,"change ""service providers network"" to ""core network""",1
34,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""backbone network interface"" is not specified",Editorial,64,17.1.2,2,"delete ""except backbone network interface""",1
35,05/30/2014 20:23:01 GMT,3074,Roger Marks,"This is confusing. How many states are there? Which state can transition to which? Figure seems to say that ""Power On/Off"" is a state, but it actually is not. Can we replace this with a version of Figure R-1 from Annex R?",Editorial,64,17.1.2,25,"replace Fig 17-1 with a version of Figure R-1 from Annex R, including elements of the existing Fig 17-1 that are missing from Fig R-1. Where the figure is references, include a reference to the subclause numbers where the associated messages are specified. (i.e., ""see subclause XYZ for specification of the messages included in Fig. 17-1."")",1
36,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""CSG, which has the same group of authorized MSs."" is confusing",Editorial,64,17.1.3,35,"change to ""CSG, which shares a group of authorized MSs""",1
37,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""by the service provider"" needlessly restricts the provider of the list",Editorial,64,17.1.3,64,"delete ""by the service provider""",1
38,05/30/2014 20:23:01 GMT,3074,Roger Marks,"""the connection with the service provider network"" needlessly references a service provider",Editorial,65,17.1.4.2,22,"delete ""service provider""",1
39,05/30/2014 20:23:01 GMT,3074,Roger Marks,"no need to refer to ""devices""",Editorial,69,17.3.1.2,61,"change ""transceiver devices"" to ""transceivers""",1
40,05/30/2014 20:23:01 GMT,3074,Roger Marks,Annex R needs to be introduced in the body.,Editorial,84,R,2,Introduce Annex R in the body of the draft in such a way that the reader can understand the relevance of Annex R to the body.,1
41,05/30/2014 20:23:01 GMT,3074,Roger Marks,There should be some explanatory text here.,Editorial,84,R,16,Add some sentences to explain why Annex R is included and how it is relevant.,1
42,05/30/2014 20:23:02 GMT,3074,Roger Marks,"It's hard to understand the meaning of the labels, since the transitions are label almost identically.",Editorial,84,R,26,Customize the transition labels so the reader can understand what event leads to or accompanies each transition.,1
43,05/30/2014 20:23:02 GMT,3074,Roger Marks,Why is Fig R-1 different from Fig 17-1? Why is the initialization state of Fig 17-1 not included here?,Editorial,84,R,26,"Include elements of the existing Fig 17-1 that are missing from Fig R-1. If the two figures can be merged, delete Annex R.",1
44,05/30/2014 20:34:22 GMT,3074,Roger Marks,PAR and Five Criteria should be carefully reviewed and updated as necessary.,Editorial,,,,Review PAR (IEEE 802.16-12-0526-00) and Five Criteria (IEEE 802.16-12-0394-06) and update as appropriate.,1
45,06/01/2014 06:27:47 GMT,8529,Jaesun Cha,"Coordination techniques between mobile stations are not defined in the current draft. In addition, coordination between mobile stations may happen regardless of network architecture type. So, it's better to delete the coordination between devices from the description on the multi-tier networks.",Technical,9,1.9,9,"Multi-tier networks are an overlay deployments which consists of macro base stations and a variety of overlaid smaller base stations in order to further improve network capacity and efficiently manage radio resource. In multi-tier networks, coordination techniques between devices, between base stations across the multiple tiers, and between base stations in the same tier are important aspects of multi-tier network design to achieve system capacity enhancements and interference mitigation techniques across tiers are also critical to achieving the user throughput enhancements.",0
46,06/01/2014 06:29:01 GMT,8529,Jaesun Cha,'ABS' shall be changed to 'BS',Technical,64,17.1.3.1,56,"The MS¡¯s local white list may contain the allowable BS IDs or common identifiers of CSGs and relevant
information to help derivation of the allowable BS IDs from common identifier. Besides this the whitelist
may include absolute/relative location information of CSG small BS, such as GPS information and overlay
Macro ABSBS BSID.",0
47,06/01/2014 06:29:57 GMT,8529,Jaesun Cha,editorial correction,Editorial,65,17.1.4.1,6,"The small BS shall perform small BS initialization procedures to register itself to the network and to configure itself through the backhaul connection. During the initialization procedure, the small BS obtains and configures small BS operation parameters from a network entity and negotiate the capabilities of the small BS, such as support of duty-cycle mode and standby mode, with the network entity. The details of the small BS initialization procedure are out of scope of this specification.",0
48,06/01/2014 06:45:19 GMT,8529,Jaesun Cha,The texts need to be refined.,Technical,66,17.1.6.2,7,"If the small BS is an OSG small BS, then the small BS ignores the CSGID(s) (if sent by the MS) in the
RNG-REQ message and goes ahead with the next steps. If the small BS is a CSG small BS, the small BS
receives the RNG-REQ message and, if needed, it looks at the received CSGID(s) in the received RNG-REQ message and checks if it matches with at least one of its CSGID(s). If there is match of the CSGID, then the small BS knows that the MS is a member of the small BS and goes ahead with the next steps.",0
49,06/01/2014 06:45:50 GMT,8529,Jaesun Cha,For clarification,Technical,67,17.2.2,56,"A small BS may support idle mode.
A small BS that supports idle mode shall follow the same procedure as specified in 6.3.22 for macro BSs with the exceptions given in this subclause.
A CSG-Closed small BS shall not broadcast paging for a non-member MS.
An MS in Idle mode shall not attach to an unsubscribed CSG-Closed small BS.",0
50,06/01/2014 06:46:27 GMT,8529,Jaesun Cha,"According to the description in 17.1.6, an MS may include CSGID(s) in RNG-REQ message during initial network entry as well as network reentry. But, the current texts say that CSGID TLV may be included in RNG-REQ message only when an MS performs initial network entry.",Technical,6,6.3.2.3.5,40,"The following TLV may be included in the RNG-REQ message when the MS is attempting to perform initial network entry or network reentry.
CSGID
CSGID is a common identifier used to identify the BSs belonging to the same CSG. (see 17.1.3)",0
51,06/01/2014 06:47:03 GMT,8529,Jaesun Cha,Editorial change,Editorial,6,6.3.2.3.6,56,The following TLV may be included in the RNG-RSP message for the BS to redirect an MS to neighbor BSs during network (re)entry.,0
52,06/01/2014 06:47:43 GMT,8529,Jaesun Cha,Multi-BS CT support TLV is used to indicate whether an MS has a capability of Multi-BS CT or not. This means that this TLV shall be included in SBC-REQ message if the MS supports Multi-BS CT.,Technical,7,6.3.2.3.23,1,"6.3.2.3.23 SBC-REQ (SS and RS basic capability request) message
Insert the following text at the end of 6.3.2.3.23:
The following parameter shallmay be included if the MS is capable of supportingsupports the capability to support the Multi-BS CT.
Multi-BS CT support (11.8.25)
6.3.2.3.24 SBC-RSP (SS and RS basic capability response) message
Insert the following text at the end of 6.3.2.3.24:
The following parameter shallmay be included in SBC-RSP message if the corresponding SBC-REQ message contains Multi-BS CT support TLV.
Multi-BS CT support (11.8.25)",0
53,06/01/2014 06:48:12 GMT,8529,Jaesun Cha,"In multi-tier networks, a serving macro BS may not include system information of neighbor small BSs in MOB_NBR-ADV message. But, the serving macro BS may need to instruct an MS to scan neighbor small BSs that are not defined in the MOB_NBR-ADV message. In this case, the serving macro BS shall include further information in MOB_SCN-RSP message to help for the MS to identify which neighbor small BS it has to scan. Recommeded small BS information TLV has been defined for this purpose. But, the current description on the Recommended small BS information TLV is somewhat ambiguous and it needs to be refined.",Technical,8,6.3.2.3.44,6,"The following TLVs may be included in the MOB_SCN-RSP message to indicate the neighbor small BSs of which BSIDs are not defined in the MOB_NBR-ADV message or not shared with the MS. If BSIDs of neighbor small BSs included in MOB_SCN-RSP as recommeded BSs for scanning are not defined in the MOB_NBR-ADV message or are not shared between the BS and the MS, If Recommended BSIDs of which BSIDs are not included in the MOB_NBR-ADV message or not shared with the MS is included in the MOB_SCN-RSP message, the following TLVs shall be included in the MOB_SCN-RSP message to provide further information of the neighbor small BSs.
Recommended small BS information
Information of the recommended small BS to be scanned. (see 11.20.4)",0
54,06/01/2014 06:48:43 GMT,8529,Jaesun Cha,"In general, neighbor BSs that are scanned are indicated by BSIDs. But, if an MS detects neighbor small BSs that are not defiend in MOB_NBR-ADV and MOB_SCN-RSP message, then the MS shall use another parameter, which is Scanning result, to indicate the measured neighbor small BSs. But, the current description is not consistent with this usage.",Technical,8,6.3.2.3.45,37,"The following TLVs may be included in the MOB_SCN-REP message to report the scanning measurement ofindicate neighbor small BSs reported in this message and of which BSIDs are not defined in MOB_NBR-ADV and MOB_SCN-RSP messageshared with the serving BS.
Scanning result
Measurement reportInformation of the scanning measurement of the recommended BS to be scanned. (see 11.19.4)",0
55,06/01/2014 06:49:16 GMT,8529,Jaesun Cha,Editorial change,Editorial,32,14.1.2.1,37,Change 'Duty-cycled mode' in Table 14-1 to 'Duty-cycle mode'.,0
56,06/01/2014 06:49:47 GMT,8529,Jaesun Cha,Editorial change,Editorial,34,14.2.12,64,"Change the title of Figure 14-49 from
'Figure 14-49 - Primitive flow for duty-cycled mode transition'
to
'Figure 14-49 - Primitive flow for duty-cycle mode transition'",0
57,06/01/2014 06:50:25 GMT,8529,Jaesun Cha,"M-BPM-REQ primitive is used to request two kinds of operation, which is operational mode change and update of operation parameters. But, those operations does not happen at the same time.",Technical,35,14.2.12.1,43,"[Remedy #1] Change texts on page 35, line 43 as follows;
This primitive is used by a BS or an NCMS to control BS power management operation. The NCMS
generates this primitive to request the IEEE 802.16 entity (BS) to perform operational mode transition orand update of operation parameters for a specific operation mode. The possible Action_Types for this primitive are listed in table below:
[Remedy #2] Change texts on page 36, line 6 as follows;
This primitive is used by the NCMS to control an operational mode of a BS orand to update operational parameters for duty-cycle mode. This primitive is also used by the BS to request a termination of duty-cycle mode to the NCMS. The primitive is only used between IEEE 802.16 entity and NCMS at BS side.",0
58,06/01/2014 06:53:28 GMT,8529,Jaesun Cha,Is BS power management functions defined in this draft applicable to both a small BS and a macro BS? It should be clarified.,Technical,80,17.4,43,Adopt texts in contribution 16-14-0040-00-000q,0
59,06/02/2014 04:57:08 GMT,8549,Eunkyung Kim,"For the clarification, including the cross reference.",Technical,17,6.3.2.3.105,27,"IM CT CH Report Request
Compound TLV that shall contain the measurement report request (see 11.33)",0
60,06/02/2014 05:02:00 GMT,8549,Eunkyung Kim,editorial change to indent.,Editorial,27,11.33,33,"line 33, ""Bit 7: Reserved; shall be set to zero."" shall not be indented.",0
61,06/02/2014 05:03:14 GMT,8549,Eunkyung Kim,"""Partioning configuration complete"" shall be included in the type of report in C-IM-IND.",Technical,57,14.2.13.3.1.2,42,"Indication Type
Type of report profiles:
Partitioning configuration complete
Resource Usage Report
PHY Report
When Indication Type is set to ""Partitioning configuration complete"", following attribute lists are valid:",0
62,06/02/2014 05:04:27 GMT,8549,Eunkyung Kim,For the clarification,Technical,68,17.3,6,"Change the text ""In addition, a small/macro cell may generate co-tier interference to adjacent small/macro cell(s)."" in line6, page68 to
""In addition, a small and/or macro cell may generate co-tier interference to adjacent small and/or macro cell(s), respectively.""",0
63,06/02/2014 05:05:43 GMT,8549,Eunkyung Kim,Interference management is applicable to any type of base station such as macro base station and small base station.,Technical,68,17.3,11,"[Insert the following text in line 11, page 68:]
Note that base station includes any type of base station such as macro base station and small base station in this subclause.",0
64,06/02/2014 05:07:01 GMT,8549,Eunkyung Kim,gap.safety zone shall be safety zone.,Technical,69,17.3.1.2,62,The DL-MAP IE with DIUC = 13 as gap.safety a safety zone indicates that the zero energy region is assigned in a DL frame or a DL subframe.,0
65,06/02/2014 05:15:47 GMT,8549,Eunkyung Kim,"Clarification on the Multi-BS cooperative transmission in the draft, including editorial correction.",Technical,71,17.3.2.1.6,24,Adopt the text proposal in IEEE 802.16-14-0041-00-000q or its lastest revision.,0
66,06/02/2014 19:16:01 GMT,77571,ANTONIO BOVO,"1) In the messages IM_CT-REQ/RESP is it possible to add the temporary identifier of the mobile?
2) In some messages sent as mean value, is it possible to send also the max value measured in the meas. interval (if it make sense considered the meas. interval itself)?
Some pages related to these comments: 8,12,14,64
3) At page 64, is it really out of scope defining a method to derive CSG ID from BS ID? It will be useful to have a recommendation for that.",Technical,8,,,,0