en the associated service flows become inactive. Once established, the FID of the transport connection is not changed during handover. The detailed mechanism for addition, change, and deletion of the transport connections can be described as follows. CHAPTER 6 The IEEE 802. 16m MAC CPS (Part I) Dynamic Service Addition: A set of MAC management messages for addition of a new service flow, and thereby a new transport connection An AAI_DSA-REQ message is sent by an MS or BS to create a new service flow and may contain parameters for more than one service flow. The MS or BS generates an AAI_DSA-REQ message, including the following parameters: Control Message Type (i.e., type of the AAI_DSA-REQ message); Service Flow Parameters specify the service flow's traffic characteristics and scheduling requirements; Convergence Sub-layer Parameter Encodings specify the service flow's CS-specific parameters. The Sleep Cycle Identifier (SCID) may be included in the AAI_DSA-REQ to change sleep cycle settings. This message may also contain the Predefined BR Index of the 3-step bandwidth request procedure when initiated by the BS. The FID for the transport connection is not included in the MS- initiated AAI_DSA-REQ message. At the BS, the service flow within the AAI_DSA-REQ message is assigned a unique FID for the transport connection, which will be communicated via the AAI_DSA- RSP message. The MS-initiated AAI_DSA-REQ messages may use the service class name instead of the QoS parameters. The BS-initiated AAI_DSA-REQ messages for service class names include the QoS parameter set associated with that service class, as well as the target Security Association Identifier (SAID) for the service flow. An AAI_DSA-RSP message is generated in response to a AAI_DSA-REQ message. An MS or BS generated AAI_DSA-RSP message contains the following parameters: Control Message Type (i.e., type of the AAI_DSA-RSP message); Confirmation Code for the corresponding AAI_DSA-REQ message; Service Flow Parameters to characterize service flow traffic and sch