he context also includes a set of service flows and corresponding mapping to connections associated with the MS, current authentication, and encryption keys associated with the connections. 4. Seamless Handover: in addition to optimized HHO, MS and BS may perform seamless HO, which is a variant of HHO, to reduce handover latency and message overhead. The capability of seamless handover is negotiated via REG-REQ/REG-RSP management messages. An authorization policy, except No Authorization, is negotiated between the MS and the serving BS. The seamless handover also requires support for counter-based Traffic Encryption Key (TEK) generation for handover. The seamless handover is only enabled if the MS, the serving BS, and the target base stations support seamless handover. A BS supporting seamless handover must include the connection identifier descriptor in the system information. In seamless handover, a target BS calculates primary management CID, secondary management CID, and transport CIDs for an MS by using the descriptor. During seamless HO, a serving BS must include the pre-allocated basic CID in MOB_BSHO-REQ/RSP messages for the MS. When a BS allocates a basic CID to an MS in advance, the primary management CID is allocated autonomously without explicit assignment Traffic Encryption Key (TEK) is a symmetric key that is used to encrypt messages. TEKs are typically changed frequently, in some systems daily and in others for every message. 6.4 Mobility management and handover in the message. Once CIDs are pre-assigned, the BS indicates whether it will perform seamless handover by including the seamless handover mode flag in MOB-BSHO-REQ/RSP management messages. When the MS receives a MOB_BSHO-REQ or MOB_BSHO-RSP message with the seamless handover mode flag set, the MS can perform seamless handover by transmitting an HO-IND message including the BS-ID of a BS among the recommended base stations that indicated support for seamless handover, i.e., a BS for which the seamless handover mode flag was set in a MOB_BSHO