IEEE C802.16m-10/1275r1 Project IEEE 802.16 Broadband Wireless Access Working Group <http://ieee802.org/16> Title Proposal to make ASN.1 code Normative Date Submitted 2010-10-25 Source(s) Joey Chou Joey.Chou@intel.com Intel Re: Sponsor Ballot for P802.16m (IEEE P802.16m/D9) Abstract Proposal to make ASN.1 code Normative Purpose To be discussed and adopted Notice Release Patent Policy This document does not represent the agreed views of the IEEE 802.16 Working Group or any of its subgroups. It represents only the views of the participants listed in the “Source(s)” field above. It is offered as a basis for discussion. It is not binding on the contributor(s), who reserve(s) the right to add, amend or withdraw material contained herein. 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.16. The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>. Further information is located at <http://standards.ieee.org/board/pat/pat-material.html> and <http://standards.ieee.org/board/pat>. 1 IEEE C802.16m-10/1275r1 Proposal to make ASN.1 code Normative Joey Chou Intel Introduction This contribution provides two proposals to make ASN.1 code normative, as per agreement at the St. Petersburg meeting. Proposal #1 – The ASN.1 code will remain in Annex R.2. This proposal is to change Annex R and Annex R.2 to normative. Annex R.1 remains informative. Proposal #2 – This proposal is to colocate the ASN.1 code with the corresponding message table. Therefore, the ASN.1 code in Annex R.2 is moved to specific sections in 16.2.3, right below the message tables. Then, Annex R.2 can be removed. 802.16 TG can release a separate P802-16M-MAC-CONTROL-MESSAGES ASN.1 data file that can be used for compilation or development. These two proposals are indended to be used as the basis for group discussion. It proposes that one of the proposals should be adopted. Proposed Text 1. Text Proposal In the P802.16m/D9, section 16.2.3, Change as the following: -------------------------------------------------- Text Start ----------------------------------------------------------------- 16.2.3 MAC Control messages The peer-to-peer protocol of MAC layers in ABS and AMS communicate using the MAC control messages to perform the control plane functions. MAC control messages shall be carried in a MAC PDU to be transported in broadcast, unicast or random access connections. There is a single unicast Control connection and two control connection channels. HARQ shall be enabled for MAC control messages sent on the unicast Control connection. Encryption may be enabled for unicast MAC control messages. MAC control messages may be fragmented, but shall not be packed. Table 677 lists the MAC control messages that shall be defined in the ASN.1 format, as shown in Annex R. The indication to the receiver that the PDU is encrypted or not is indicated by the FID 0x1 and 0x0 in AGMH respectively. Whether the encryption is applied on a MAC control message or not shall be determined by the message type and MAC procedure context, which is defined in Table 677. A message included in a PDU whose encryption status indicated by the FlowID in AGMH does not match the combined message type and corresponding context defined in the Table 677 shall be discarded. Encrypted and non encrypted MAC control messages shall not be sent in the same PDU. Annex R (informative normative) Definition of AAI MAC control messages This Appendix defines MAC control messages using ASN.1 notation. The Packed Encoding Rules (PER) with byte unaligned option 2 IEEE C802.16m-10/1275r1 shall be used to produce compact transfer syntax for MAC control message to be transmitted over the air interface efficiently. In the event of conflict between the specification defined in this Annex R and other portions of the IEEE Std 802.16, those other portions shall take precedent. Annex R.2 MAC Control Message Definitions (Normative) -------------------------------------------------- Text End ----------------------------------------------------------------- 3