-10, the management entity and the management information bases contained in the management-plane, configure and manage the functional entities in the data- and control-plane protocol layers. The IEEE 802.16 specification includes control and management SAPs as part of the management-plane that expose control-plane and management-plane functions to upper layers. Management-plane primitives and the C-SAP are used for more time sensitive control- plane primitives that support handovers, security context management, radio resource management, and low power system operations. In addition, under the IEEE 802.16 standard, a user can be associated with a number of service flows, each characterized with different QoS parameters. This information is provisioned in a subscriber management system (e.g., AAA database) or a policy server. There are two service models: (1) static service model, where the subscriber station is not allowed to change the parameters of provisioned service flows or create new service flows dynamically; and (2) dynamic service model, where an MS or BS may create, modify or delete service flows dynamically. In the latter case, IEEE 802.16 Management Plane Entity CS Management/Configuration MAC Management/Configuration Security Management/Configuration Management Information Base (MIB) PHY Management/Configuration FIGURE 3-10 The IEEE 802.16 management-plane entity [3] CHAPTER 3 IEEE 802. 16m Reference Model and Protocol Structure a dynamic service flow request is evaluated against the provisioned information to decide whether the request could be authorized. More precisely, the following steps are provisioned in the IEEE 802.16 specification for dynamic service flow creation [22]: 1. Permitted service flows and associated QoS parameters are provisioned for each subscriber via the management plane (management entity). 2. A service flow request initiated by the MS or BS is evaluated against the provisioned information, and the service flow is created if permissible. 3. A service flow thus created trans