IEEE P802.15 Wireless Personal Area Networks Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs) Title Low-bandwidth LiFi PHY & MAC Date Submitted 02 May 2016 Source Tsonev, Dobroslav; Serafimovski, Nikola pureLiFi Ltd. Edinburgh Technology Transfer Centre Alrick Building Max Born Crescent EH9 3BF Edinburgh United Kingdom Voice: +44 131 472 4704 Fax: [ ] E-mail: Re: Abstract This document presents the Low-bandwidth PHY specification and the MAC proposal specification for inclusion into D0. Purpose The contents of this document shall be integrated into D0. Notice This document has been prepared to assist the IEEE P802.15. 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 acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.
PHY-RXSTART X PHY-RXEND X PHY-SET-LOADING X X PHY-PROVIDE-CSI X Table 6.7.2.1.2. presents the parameters used by the management service primitives. Table 6.7.2.1.2: PHY management service primitive parameters Parameter Associated Primitive Value TXVECTOR PHY-TXSTART.request A set of parameters RXVECTOR PHY-RXSTART.indicate A set of parameters RXERROR PHY-RXEND.indicate NoError, FormatViolation, Unsupported Rate BIT_LOADING_VECTOR A set of parameters CSI_VECTOR A set of parameters Table 6.7.2.1.3. presents the scalar parameters associated with the vector parameters in Table 6.7.2.1.2. Table 6.7.2.1.3: PHY management service primitive parameter vector descriptions Parameter Associated Vector DATARATE TXVECTOR RXVECTOR A 3-bit value setting the data rate according to the specification in Table 6.2.3.1.1.1 LENGTH TXVECTOR RXVECTOR The length of the data to be transmitted in octets as indicated by the LENGTH parameter described in subclause 6.2.3.1.3. BIT_LOADING TXVECTOR Indicates whether adaptive bit and energy loading should be used at the PHY to encode the data. The possible values are 'YES' or 'NO'.
6.2.3.1.1. RATE The RATE field consists of three bits and indicates the QAM constellation size and the FEC rate (achieved with the use of a convolutional encoder and puncturing) used for the subsequent payload. The values specified in Table 5 are valid for the RATE field. Table 6.2.3.1.1.1: Valid RATE values R0-R2 Modulation FEC rate Data rate (Mb/s) (40 MHz) Data rate (Mb/s) (20 MHz) Data rate (Mb/s) (15 MHz) Data rate (Mb/s) (10 MHz) Data rate (Mb/s) (5 MHz) 110 BPSK 1/2 12 6 4.5 3 1.5 111 3/4 18 9 6.75 4.5 2.25 010 4-QAM 1/2 24 12 9 6 3 011 3/4 36 18 13.5 9 4.5 100 16-QAM 1/2 48 24 18 12 6 101 3/4 72 36 27 18 9 000 64-QAM 2/3 96 48 36 24 12 001 3/4 108 54 40.5 27 13.5 6.2.3.1.2. Reserved bits (R) One bit is reserved for introducing additional transmission in future modifications of the standard. 6.2.3.1.3. LENGTH An 11-bit which indicates the size of the payload in octets. Hence, the size of the payload is between 0 and 2048 octets. 6.2.3.1.4. Advanced Modulation Header Bit (A) One bit indicating whether an Advanced Modulation Header is included in the next OFDM frame: 1 → The next OFDM frame is an Advanced Modulation Header. 0 → The next OFDM frame is part of the DATA portion (payload) of the PHY frame.
5.8.3.7 Sequence Control field In data frames, the Sequence Control field contains the information necessary to identify the MSDU or MMPDU sequence number. The information in this field has the format depicted in Fig. 5.8.3.7.1. Bits 4 to 15 identify the packet sequence number, while bits 0 to 3 are reserved for possible future extensions of the protocol functionality such as packet fragmentation support. This same information is used by the receiving station and placed in the Ack Info field of a subsequent frame used for package acknowledgment. 5.8.3.8 Reserved field This field contains 16 bits which are reserved for future references in an extension of the MAC protocol. 5.8.3.9 Body field The Frame Body is a variable length field that contains information specific to individual frame types and subtypes as defined in subclause 5.8.4. The minimum frame body is 0 octets. The maximum length frame body is defined by the maximum length (MSDU + ICV + higher layer overhead), where ICV stands for integrity check value. 5.8.3.10 Frame check sequence (FCS) field The FCS field is a 32-bit field containing a 32-bit CRC. The FCS is calculated over all the fields of the MAC header and the Frame Body field. These are referred to as the calculation fields. The FCS is calculated the following standard generator polynomial of degree 32: G(x) = x32 + x26 + x23 + x22 + x16 + x12 + x11 + x10 + x8 + x7 + x5 + x4 + x2 + x + 1 The FCS is the ones complement of the sum (modulo 2) of the following: a) The remainder of xk × (x31 + x30 + x29 + …+ x2 + x + 1) divided (modulo 2) by G(x), where k is the number of bits in the calculation fields, and
b) The remainder multiplication of the contents (treated as a polynomial) of the calculation fields by x32 and then division by G(x). The FCS field is transmitted commencing with the coefficient of the highest-order term. As a typical implementation, at the transmitter, the initial remainder of the division is preset to all ones and is then modified by division of the calculation fields by the generator polynomial G(x). The ones complement of this remainder is transmitted, with the highest-order bit first, as the FCS field. At the receiver, the initial remainder is preset to all ones and the serial incoming bits of the calculation fields and FCS, when divided by G(x), results in the absence of transmission errors, in a unique nonzero remainder value. The unique remainder value is the polynomial: x31 + x30 + x26 + x25 + x24 + x18 + x15 + x14 + x12 + x11 + x10 + x8 + x6 + x5 + x4 + x3 + x + 1 5.8.4 Specific Frame Formats 5.8.4.1. Management Frames Format 5.8.4.1.1. Management Frames Information Components 5.8.4.1.1.1 Beacon Frame Format The Beacon body contains the following information in the presented order: Table 5.8.4.1.1.1.1: Beacon Frame Body Order Information 1 Timestamp 2 Beacon Interval 3 Capability 4 Service Set Identifier (SSID) 5 Supported Rates 6 DS Parameter Set 7 Traffic Indication Map 8 Country 9 Extended Support Rates
'1' → RPO-OFDM is supported. '0' → RPO-OFDM is not supported. 5.8.4.3.1.4 Analog Dimming A single bit indicating whether the communication node transmitting the advanced modulation control frame supports analog dimming (adjusting the analog signal bias level): '1' → Analog dimming is supported. '0' → Analog dimming is not supported. 5.8.4.3.1.5 Relaying Four bits indicating types of relaying operations the communication node transmitting the advanced modulation control frame supports. The first bit (B7) indicates whether relaying in FD is supported: '1' → Relaying in FD is supported. '0' → Relaying in FD is not supported. The second bit (B8) indicates whether relaying in HD is supported: '1' → Relaying in HD is supported. '0' → Relaying in HD is not supported. The third bit (B9) indicates whether AF relaying is supported: '1' → AF relaying is supported. '0' → AF relaying is not supported. The fourth bit (B10) indicates whether DF relaying is supported: '1' → DF relaying is supported. '0' → DF relaying is not supported. 5.8.4.3.1.6 MIMO A single bit indicating whether the communication node transmitting the advanced modulation control frame supports MIMO communication: '1' → MIMO is supported. '0' → MIMO is not supported.