Frame Bearing Capability Sample Clauses

Frame Bearing Capability. A bundle may be provisioned with a minimum acceptable level of operational bandwidth for the bundle. Operational bandwidth is available from a bundle link when BL_ACTIVATE indication is received. The total operational bandwidth available is calculated by adding the operational bandwidth available from each bundle link. Four classes of bandwidth requirements are shown in Table 2. One class is selected to determine the criteria that trigger activation or deactivation of the emulated physical interface. When the bundle's operational bandwidth meets the criteria for a selected class, the bundle must send a PH_ACTIVATE to the data link layer. When the bundle's operational bandwidth fails to meet the criteria for a selected class, the bundle must send a PH_DEACTIVATE to the data link layer. Class A (Default) Single link PH_ACTIVATE: PH_DEACTIVATE: One or more bundle links indicate BL_ACTIVATE. All bundle links indicate BL_DEACTIVATE. Class B All links PH_ACTIVATE: PH_DEACTIVATE: All bundle links indicate BL_ACTIVATE. Any bundle link indicates BL_DEACTIVATE. Class C Threshold A minimum threshold is provisioned through network management procedures. The threshold represents the minimum number of bundle links that must indicate BL_ACTIVATE. PH_ACTIVATE: Sufficient bundle links indicate BL_ACTIVATE. PH_DEACTIVATE: Insufficient bundle link indicates BL_DEACTIVATE. Class D Custom PH_ACTIVATE: PH_DEACTIVATE: Implementation specific. Implementation specific.
View SourceView Similar (2)

Related to Frame Bearing Capability

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as all line-side and trunk-side facilities, plus the features, functions, and capabilities of the switch. The features, functions, and capabilities of the switch shall include the basic switching function of connecting lines to lines, lines to trunks, trunks to lines, and trunks to trunks. Local circuit switching includes all vertical features that the switch is capable of providing, including custom calling, custom local area signalling service features, and Centrex, as well as any technically feasible customized routing functions. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for ▇▇▇▇ when ▇▇▇▇: (1) serves an End User with four (4) or more voice-grade (DS0) equivalents or lines served by BellSouth in Zone 1 of one of the following MSAs: Atlanta, GA;

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: 57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); 57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR ▇▇▇-▇▇▇-▇▇▇ and BR ▇▇▇-▇▇▇-▇▇▇; 57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. 57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Outputs Analogue and digital outputs of protected content are allowed if they meet the requirements in this section and if they are not forbidden elsewhere in this Agreement..