Use-case Based Licensing of SEPs Sample Clauses

Use-case Based Licensing of SEPs. Use-case based licensing of SEPs is generally inconsistent 4 with such FRAND licensing principles. Use-case based licensing inextricably ties the value 5 of the standardized technology with the other technology/innovation reflected in an end-user 6 product, even though such technology/innovation is outside the scope of the relevant SEPs. 7 Consequently, the use-case based licensing model is inconsistent with the FRAND approach 8 of calculating a royalty associated solely with the value of the standardized technology.
AutoNDA by SimpleDocs

Related to Use-case Based Licensing of SEPs

  • Web-based-WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the HTTP response for only one HTTP request. If Registry Operator implements a multiple-step process to get to the information, only the last step shall be measured. If the RTT is 5-times or more the corresponding SLR, the RTT will be considered undefined.

  • INTERNET-BASED SERVICES Microsoft provides Internet-based services with the software. It may change or cancel them at any time.

  • License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.

  • Quality-based Selection Services for assignments which the Bank agrees meet the requirements set forth in paragraph 3.2 of the Consultant Guidelines may be procured under contracts awarded on the basis of Quality-based Selection in accordance with the provisions of paragraphs 3.1 through 3.4 of the Consultant Guidelines.

  • Unbundled Voice Xxxx - XX0 (XXX-XX0). Loops are 2-wire loop start circuits, will be non-designed, and will not have remote access test points. OC will be offered as a chargeable option on XX0 Xxxxx when reuse of existing facilities has been requested by NewPhone, however, OC is always required on UCLs that involve the reuse of facilities that are currently providing service. NewPhone may also order OC-TS when a specified conversion time is requested. OC-TS is a chargeable option for any coordinated order and is billed in addition to the OC charge. An Engineering Information (EI) document can be ordered as a chargeable option. The EI document provides Loop Make-Up information which is similar to the information normally provided in a Design Layout Record (DLR). Upon issuance of a non-coordinated order in the service order system, XX0 Xxxxx will be activated on the due date in the same manner and time frames that BellSouth normally activates POTS-type Loops for its customers.

  • Misuse of Internet-based Services You may not use these services in any way that could harm them or impair anyone else’s use of them. You may not use the services to try to gain unauthorized access to any service, data, account or network by any means.

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • Non-Synchronous Generation The Interconnection Customer shall design its Small Generating Facility to maintain a composite power delivery at continuous rated power output at the high-side of the generator substation at a power factor within the range of 0.95 leading to 0.95 lagging, unless the NYISO or the Transmission Owner in whose Transmission District the Small Generating Facility interconnects has established a different power factor range that applies to all similarly situated non-synchronous generators in the control area or Transmission District (as applicable) on a comparable basis, in accordance with Good Utility Practice. This power factor range standard shall be dynamic and can be met using, for example, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors, or a combination of the two. This requirement shall only apply to newly interconnecting non-synchronous generators that have not yet executed a Facilities Study Agreement as of September 21, 2016.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • JOC - PRICING OF After Hours Coefficient What is your after hours coefficient for the RS Means Price Book for work performed after normal working hours? (FAILURE TO RESPOND PROHIBITS PART 2 JOC EVALUATION) Remember that this is a ceiling price proposed. You can discount to any TIPS Member customer a lower coefficient than your proposed contract coefficient, but not higher. This is one of three pricing questions that are required for consideration for award on this solicitation. Please consider your answer carefully. An explanation of the TIPS scoring of pricing titled "Pricing Coefficient Instruction" is included in the attachments for your information. The below is an EXAMPLE of how the pricing model works (It is not intended to influence your proposed coefficient, you should propose a coefficient that you determine is reasonable for your business for the life of the contract): The most common after hours coefficient is time and a half of the RS Means Unit Price Book prices. To illustrate this coefficient, if your regular hours coefficient is .95, your after hours coefficient would be 1.45.

Time is Money Join Law Insider Premium to draft better contracts faster.