802.16.1 Functional Requirements, Rev. 1 - LMSC, LAN/MAN ...

More documents

Recommendations

Info

1999-12-17 IEEE 802.16s-99/00r1M23 5.4 Since statistical atmospheric conditions vary widely in geography, the802.16.1 protocols MUST be flexible in consumed radio bandwidth(spectral efficiency), cell radius, and transmit power to accommodatea rain allowance that varies with geography.M24 5.5 The error rate, after application of the appropriate error correctionmechanism (e.g., FEC), delivered by the PHY layer to the MAClayer SHALL meet IEEE 802 functional requirements: The bit errorrate (BER) is 10E-9.M25 5.5 Each block of data delivered by the PHY to the MAC layer MUSTallow for detection of errors by the MAC (e.g., by CRC) with 1, 2 or3 errored bits (a Hamming Distance of 4).M26 5.6 The budget for the 802.16.1 system transit delay and access delayMUST be derived. The MAC layer may have different requirementsfor each direction, upstream and downstream.M27 5.6 In the upstream direction, time MUST be budgeted for requestingbandwidth and contending among nodes.M28 5.7 In a given 802.16.1 system instance, capacity MUST be carefullyplanned to ensure that subscribers’ quality of service guarantees andmaximum error rates are met.M29 5.7 The MAC and PHY protocols MUST accommodate channel capacityissues and changes in channel capacity to meet contracted servicelevels with customers.M30 5.7 As subscribers are added to 802.16.1 systems, the protocols MUSTaccommodate them in an automated fashion.M31 6 802.16.1 protocols MUST support classes of service (CoS) withvarious quality of service (QoS) guarantees to support the bearerservices that an 802.16.1 system MUST transport.M32 6 802.16.1 protocol standards MUST define interfaces and proceduresthat accommodate the needs of the bearer services with respect toallocation of prioritization of bandwidth.M33 6 802.16.1 protocols MUST provide the means to enforce QoScontracts and Service Level Agreements.M34 6 The 802.16.1 protocols MUST be capable of dedicating constantrate,provisioned, bandwidth for bearer services such as SDH/PDH.M35 6 For QoS-based, connectionless, but not circuit-based, bearerservices, the 802.16.1 protocols MUST support bandwidthnegotiation “on-demand.”M36 6 Table 1 provides a summary of the QoS requirements that the PHYand MAC SHALL provide.M37 6.2 802.16.1 protocols SHALL define a set of parameters that preservethe intent of QoS parameters for both ATM- and IP-based services.-24-MACPHYMGMTMACPHYPHYMACPHYMACMGMTMACPHYMGMTMACMGMTMACMACMACMGMTMACMACMACPHYMAC
1999-12-17 IEEE 802.16s-99/00r1M38 6.3 The classes of service and QoS parameters of bearer servicesSHALL be translated into a common set of parameters defined by802.16.1.M39 6.3 A network node that serves as an inter-working function (IWF)between a QoS-capable LAN or WAN and an 802.16.1 systemMUST participate in signaling protocols to set up QoS parametersfor connection-oriented services.M40 6.3 The IWF MUST participate in the ATM signaling protocol that setsup the circuit.M41 6.3 The IWF also MUST utilize 802.16.1 interface primitives (e.g., MAClayer user interface primitives) to request QoS.M42 6.3 If 802.16.1 is to be a “link” in the IP network, an IWF MUSTinterface with 802.16.1 to negotiate resource allocation.M43 6.3 The QoS parameters for 802.16.1 MUST be chosen and interfaceprimitives defined that allow for bearer services’ IWFs to negotiateQoS “through” an 802.16.1 system.M44 7.1 The 802.16.1 protocol MUST permit operators to enforce servicelevel agreements (SLAs) with subscribers by restricting access to theair link, discarding data, dynamically controlling bandwidth availableto a user or other appropriate means.M45 7.1 The 802.16.1 protocols MUST permit subscribers to monitorperformance service levels of the 802.16.1 services being provided atthe delivery point.M46 7.2 The operator MUST have means to shut down a subscriber station ifnecessary, remote from the subscriber station, in the face of amalfunction.-25-MACMACMACMACMACMACMACMGMTMACPHYMGMTMACPHYMGMTM47 7.2 The operator MUST have the means to shut down a BTS remotely. MACPHYMGMTM48 7.3 The 802.16.1 system management framework, architecture,protocols and managed objects MUST allow for operators toeffectively administer accounting and auditing.M49 7.3 An operator MUST be able to account for time- and bandwidthutilizationand the various QoS parameters for each subscriber.M50 8 The 802.16.1 system SHALL enforce security procedures describedin section 8.M51 8 The security system chosen by 802.16.1 SHALL be added to theprotocol stack (Figure 4-1) and reference points (Figure 2-3) toinclude security protocols, and “database” servers for authentication,authorization, key management, etc.MACMGMTMACMACSECM52 8.1 This initial authentication MUST be very strong in order to prevent MACSEC
Page 1 and 2: 1999-12-17 IEEE 802.16s-99/00r1Proj
Page 3: 1999-12-17 IEEE 802.16s-99/00r1Ackn
Page 6 and 7: 12345678910111213141516171819201999
Page 9 and 10: 123456789101112131415161718191999-1
Page 11 and 12: 1234567891011121999-12-17 IEEE 802.
Page 13: 12345678910111213141516171819202122
Page 16 and 17: 12345678910111213141516171819202122
Page 18 and 19: 12345678910111213141516171819202122
Page 20 and 21: 123456789101112131415161999-12-17 I
Page 22 and 23: 12345678910111213141516171819202122
Page 24 and 25: 12345678910111213141516171819202122
Page 26 and 27: 1234567891011121314151617181999-12-
Page 30 and 31: 12345671999-12-17 IEEE 802.16s-99/0
Page 32 and 33: 11999-12-17 IEEE 802.16s-99/00r1•
Page 34 and 35: 121999-12-17 IEEE 802.16s-99/00r1B
Page 36 and 37: 1999-12-17 IEEE 802.16s-99/00r1Core
Page 38 and 39: 1999-12-17 IEEE 802.16s-99/00r1Subs
Page 40 and 41: 1999-12-17 IEEE 802.16s-99/00r1ISDN
Page 42 and 43: 12345678910111213141516171819202122
Page 44 and 45: 12345678910111213141516171819202122

802.16.1 Functional Requirements, Rev. 1 - LMSC, LAN/MAN ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?