Broadcast MAC Protocol Rules

1. The Broadcast MAC Protocol serves the Broadcast Security Protocol as well as the
Security Layer.
a. Broadcast Security Packet from the Broadcast Security Protocol
b. Security Layer Packets destined for the Broadcast channel from the Security
Layer
Max Length of Security Layer Packet = 124 Octets per ECB.
2. Data from the ECB is transmitted using Broadcast MAC Packets
1002 bits each with
1000 bits (125 octets) of payload and 2 bits of MAC Trailer. The MAC Trailer is set to
00 by AN, but AT SHALL ignore the MAC Trailer of the broadcast packets.
3. Each row of the ECB contains ‘MACPacketsPerECBRow’ number of Broadcast MAC
Packets.
4. The Broadcast MAC Packets are sent to the Broadcast Physical Layer Protocol for
transmission on ONE or MORE interlace-multiplex pairs of the Broadcast channel.
5. The AN SHOULD NOT overwrite ONE or MORE slots of one or more Broadcast MAC
packets with Control Channel packets or Forward Traffic Channel packets.
6. The burst length for an interlace-multiplex pair SHALL be a non-zero positive integer
multiple of the number of slots required to transmit a single Broadcast Physical Layer
packet on that interlace-multiplex pair.
7. An ECB belonging to a logical channel is transmitted on ONE or MORE interlace-
multiplex pairs of the Broadcast Channel.
8. All interlace-multiplex pairs that are assigned to carry a Logical channel on a given
CDMA channel shall be transmitted at the SAME Broadcast Physical Layer data rate.
9. A Logical channel SHALL occupy the SAME slots on all sectors from which the AT is
allowed to soft-combine the Logical channel.
10. An interlace-multiplex pair SHALL NOT be assigned to more than one Logical channel.
11. A BCMCS Flow is carried on one Broadcast Logical channel.
12. Each Logical channel may carry ONE or MORE BCMCS Flows.
13. If a BCMCS Flow is also carried on additional CDMA channels, the BCMCS Flow to
physical channel mapping NEED NOT be the same on all CDMA channels on which the
BCMCS Flow is transmitted.
14. The BroadcastOverhead message contains the Logical to physical channel mapping.
15. The AN SHALL transmit a BroadcastOverhead message periodically in the Synchronous
Capsule of the Control Channel, once every BroadcastOverheadPeriod Control-Channel
cycles (default value is once every 7 cycles).
16. A Logical channel SHALL use Error Control Blocks (ECBs) with the same values of N,
K, and MACPacketesPerECBRow on all sectors that the AT is allowed to soft-combine
the Logical channel.
17. The value of MACPacketsPerECBRow SHALL be a non-zero positive integer multiple
of the number of the Broadcast MAC Packets carried in a single Broadcast Physical
Layer packet assigned to carry the payload for this Logical channel.
18. The value of MACPacketsPerECBRow for a given ECB SHALL be less than or equal to
SIXTEEN.
19. The values of MACPacketsPerECBRow for ALL ECBs that the AN EXPECTS the AT to
be able to monitor simultaneously shall collectively satisfy the following Equation:
N16 = Sum of number of MACPacketsPerECBRow for all ECBs with N=16
N32 = Sum of number of MACPacketsPerECBRow for all ECBs with N=32
Then: ( N16 + 2 • N32 ) <= 32
20. The MultiplexCount field (2bits) of the BroadcastOverheadMessage from AN indicates
the number of multiplexes-per-interlace being used by the AN. Currently there can be
either 4 or 8 or 16 multiplexes per interlace.
21. The Burst length of each of the multiplex on each of the interlace can be configured to be
anywhere from 1 to 64 slots by AN by use of BurstLengthX fields in the
BroadcastOverhead message.
22. The AN SHALL populate all BurstLengthX fields included in the BroadcastOverhead
message EVEN IF the corresponding interlace-multiplex pair does not carry any BCMCS
Flows.
23. If any of the BCMCS Flows are carried on an interlace-Y of the physical channel, then the
AN SHALL set the ‘InterlaceYIncluded’ field to ‘1’. Otherwise AN SHALL set
‘InterlaceYIncluded’ field of the BroadcastOverhead message to ‘0’.
In other words, if none of the multiplexes on a given interlaces carry BCMCS
Flow, that interlace can be excluded by clearing the corresponding ‘InterlaceYIncluded’
fields of the BroadcastOverhead message.
24. The ‘BCMCSFlowCount’ field (7 bits) of the BroadcastOverhead message indicates the
number of BCMCS flow identifiers included in the message.
Each BCMCS flow identifier may be configured to belong to a different Logical
channel (and therefore a different ECB) by the AN. So, strictly speaking, there can be as
many as 127 different Logical channels being broadcast by the AN.
25. Records for all BCMCS Flow Ids that share the SAME Logical channel SHALL be
placed consecutively in the BroadcastOverhead message.
26. The BroadcastOverhead message also provides the following fields for EACH of the
Logical channel (unless they happen to be same as those for previous Logical channel):
a. PhysicalChannelCount
Number of interlace-multiplex pairs that comprise this
Logical channel in the range from 0 to 64 inclusive.
b. DataRate (4-bit field) with valid values from ‘0000’ (38.4kbps) to ‘1101’
(2457.6kbps). Values ‘1110’ to ‘1111’ are reserved.
Indicates the data rate of
the physical layer for this Logical channel (and indirectly the Preamble-length
and the number of slots being used to transmit ONE Physical-Layer packet).
c. OuterCode (4-bit field) –-> Indicates (N,K,R) Reed-Solomon outer code being
used for this Logical channel.
i. ‘0000’  (1, 1, 0) i.e. No Outer Code.
ii. ‘0001’  (16, 12, 4)
iii. ‘0010’  (16, 13, 3)
iv. ‘0011’  (16, 14, 2)
 v. ‘0100’  (32, 24, 8)
vi. ‘0101’  (32, 26, 6)
vii. ‘0110’  (32, 28, 4)
All other values are reserved.
d. MACPacketsPerECBRow
AN SHALL set this field to one less than the
number of Broadcast MAC packets required to carry each row of the ECB.
e. Interlace
AN SHALL set this field to the interlace index of this interlace-
multiplex pair for this Logical channel.
f. Multiplex
AN SHALL set this field to the multiplex index of this interlace-
multiplex pair for this Logical channel.
g. SoftCombine
The AN SHALL set this field as follows: Each occurrence of
this field corresponds to a NeighborPilotPN included in the SectorParameters
message with signature equal to SectorSignature. The AN SHALL use the same
order for occurrences of this field as is used for NeighborPilotPNs that are listed
in the SectorParameter message. The AN SHALL set the ith occurrence of this
field to ‘1’ if the AT is allowed to soft combine this Logical channel on the
current PilotPN, and the ith NeighborPilotPN in the SectorParameter message.
Otherwise, the AN SHALL set the ith occurrence of this field to ‘0’.
h. AdditionalCDMAChannelCount
The AN SHALL set this field to the number
of additional CDMA channels on which this BCMCS Flow is transmitted. If this
BCMCS Flow is NOT assigned to ANY interlace-multiplex pairs of THIS
CDMA channel, then the AN SHALL NOT set AdditionalCDMAChannelCount
to Zero.
i. AdditionalCDMAChannel
The AN SHALL set this field to the channel record
specifications for the additional CDMA channel on which this BCMCS Flow is
transmitted. The channel record format is specified in the Section 10.1 of
C.S0054.