MSC Sample Clauses

MSC. As between the Parties, MSC shall own all Development Program Technology relating to (1) MSC Materials, (ii) all know-how and processes relating to the manufacture of MSC Materials, (iii) all analytical and/or quality control techniques used in the evaluation of MSC Materials, (iv) all uses of any MSC Materials (without the use or inclusion of any MPM Material) in any and all end-use applications, and (v) any and all products, materials, formulations and the like that are made from or include an MSC Material (does not include an MPM Material). MSC shall also own all Intellectual Property Rights derived from any of the foregoing in (i) through (v), developed pursuant to this Agreement as Development Program Technology, regardless of inventorship. All of the foregoing in (i) through (v) shall be referred to as “MSC Work Product.” MPM hereby assigns to MSC the entire right, title and interest in and to the MSC Work Product, including without limit, any Inventions and Intellectual Property Rights derived from the Development Program Technology associated with or applicable to such MPM Work Product.

MSC. 1.7 The MSC shall provide the ability to establish terminating and dialed digits triggers for an entire MSC and to generate IS-41 Rev. C messages when established trigger criteria are encountered.

MSC. 1/Circ.1259 - Interim Revised Technical Specifications for the LRIT System, as amended.

MSC. Subject to the exceptions specified in the Vendor's compliance and exceptions documentation (evaluation date 1/31/95) previously provided by the Vendor to the Owner to the following reference, the MSC shall meet the requirements of GR-317-CORE, Switching System Generic Requirements for Call Control Using the Integrated Services Digital Network User Part (ISDNUP) Issue 1, 2/94, Revision 1 (9/94) for interoffice trunk signaling between MSCs.

MSC. 2.2 Subject to the exceptions specified in the Vendor's compliance and exceptions documentation (completed 11/8/93) previously provided by the Vendor to the Owner to the following reference, the MSC shall meet the requirements of TR-NWT-000606, Issue 2, October 1992 LSSGR: Common Channel Signaling Section 6.5, for connection to the SS7 network via STP's.

MSC. 10.9 In accordance with Exhibit C, multiple MSCs must be able to be networked to form Soft Hand-off cluster allowing any BTS served by MSC-A to enter soft hand-off with any BTS served by MSC-B where MSC-A and MSC-B are from different vendors (IS-41). ATTACHMENT 1 TO EXHIBIT D.MSC North American Market BHCA Rating The system capacity for Autoplex 1000(R) North American markets is 200,000 BHCA based on the following assumptions: - Single MSC system EC - Release 9.0 (or later) - 3B21 Duplex ECP - OMP with Release 9.0 (or later) software - A single 5ESS-2000 Switch DCS carrying 100% of system traffic with a hand-off rate of 1.6 Soft HO/BHCA or less and 0.2 Hard HO/BHCA or less - 2.5 Autonomous Registrations (AR) per BHCA - Short Message per BHCA <10% - Voice Mail/CF/CW on 2.5% of BHCA - Available paging capacity in CDMA is approximately 51 pages/second - Maximum of two page messages per page attempt - Maximum "No Page Response" rate is 50% - Mobile terminated call attempts are 32% of BHCA or lower - Mobile terminated calls answered is 10% - Mobile originated calls are 68% of BHCA - Mobile originated answered calls are 55% of BHCA - Mobile to mobile calls are 10% of BHCA - Mobile busies is 3% or higher of BHCA Mobile originations limited to 18,000 calls/cell/hour on the access channel - BHCA per subscriber is 1.0 - Average Call Holding Time (ACHT) is 90 seconds. EXHIBIT D.NM LUCENT TECHNOLOGIES D.NM

MSC. 4.3 MSC Software modifications (whether considered to be Software Upgrades or Software Enhancements) that can be incorporated into the then-current releases will not require more than fifteen (15) minutes of downtime, and in addition, the Vendor will use its best efforts to reduce the amount of downtime required.

MSC. 2.3 Subject to the exceptions specified in the Vendor's compliance and exceptions documentation (dated 10/2/89) previously provided by the Vendor to the Owner to the following reference, the MSC shall support all interface types (except the SS7 option for Type 2C) in TR-NPL-000145, Compatibility Information for Interconnection of a Wireless Services Provider and a Local Exchange Carrier Network, Issue 2, 12/93.

MSC. 10.5 The T1 from the BTS to the MSC shall support multiple BTS sites on a single link. Thus a link that has been groomed with two or more separate BTS sites shall be terminated directly on the MSC.

MSC. 6.2 The Vendor shall provide engineering rules for determining the capacity of the MSC system. The engineering rules shall identify the parameters required in order to determine the MSC capacity required by the Owner.