Downlink HeNB/eNB ICIC with no direct cooperation capabilities Sample Clauses

Downlink HeNB/eNB ICIC with no direct cooperation capabilities. In [ARTD13], we have presented a power setting strategy for HeNB deployments in order to protect the macro UE located outside and close to a building of a HeNB. We define a high interference zone (HIZ) as the locations where eNB UEs experience a SINR bellow a given threshold. In our scenario, the SINR mainly depends on the useful signal power received by the eNB, on the interference received by the HeNB, and also on the interference from the neighboring macro stations. We neglect the impact of the other HeNBs by observing that the coverage of a HeNB is limited, which induces that the probability to be interfered by more than one HeNB is low. By consequence, when all HeNBs are set with the same transmit power, the HIZ area varies with the position of the HeNB. For HeNBs deployed at the cell center, the HIZ is small because the eNB useful power is large with respect to the interference from the other nodes and from the HeNB. For HeNBs deployed at the cell edge, the HIZ is large since the impact of the HeNB on the SINR is non-negligible for eNB-UEs located around the HeNB. Thus, a first strategy is to try to equalize the size of the HIZ so that each HeNB has an equivalent impact on the eNB UEs, and to tune the power control strategy so as to reach a target trade-off between the eNB and HeNB network cell edge throughput. As introduced in [ARTD13] and further developped in [GUI11-1], we first compute a function g() as the macro performance degradation in the HIZ gP , I, Psol = SINR P /SINR 0. where M SINRM t, F P = t ,F M N  I t, F M PM ,  P G O t ,F F and where Pt , F is the transmit power of the most interfering HeNB for a given eNB-UE, GF the path gain from this HeNB to the eNB-UE, PM is the received power from the eNB, N the constant AWGN power level at the UEs, and IO the interference power level received from other eNBs. As a remark, SINRM 0 denotes the SINR of the eNB-UE when the HeNB is turned off. Then, we compute the HeNB transmit power for a target macro performance degradation gth.
AutoNDA by SimpleDocs

Related to Downlink HeNB/eNB ICIC with no direct cooperation capabilities

  • Independent Contractor; No Partnership; No Agency; No Utility Services 15.1 Company and Developer shall be independent contractors. This Agreement shall not be interpreted or construed to create an association, joint venture, agency relationship, or partnership between the Parties or to impose any partnership obligation or partnership liability upon any Party. No Party shall have any right, power or authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an agent or representative of, or to otherwise bind, the other Party. This Agreement is not an agreement to provide or take utility services of any kind, including, without limitation, interconnection or other electric transmission services.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • DEPENDENT PERSONAL SERVICES 1. Subject to the provisions of Articles 16, 18 and 19, salaries, wages and other similar remuneration derived by a resident of a Contracting State in respect of an employment shall be taxable only in that State unless the employment is exercised in the other Contracting State. If the employment is so exercised, such remuneration as is derived therefrom may be taxed in that other State.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Traditional Medicine Cooperation 1. The aims of Traditional Medicine cooperation will be: (a) to build on existing agreements or arrangements already in place for Traditional Medicine cooperation; and (b) to promote information exchanges on Traditional Medicine between the Parties. 2. In pursuit of the objectives in Article 149 (Objectives), the Parties will encourage and facilitate, as appropriate, the following activities, including, but not limited to: (a) encouraging dialogue on Traditional Medicine policies and promotion of respective Traditional Medicine; (b) raising awareness of active effects of Traditional Medicine; (c) encouraging exchange of experience in conservation and restoration of Traditional Medicine; (d) encouraging exchange of experience on management, research and development for Traditional Medicine; (e) encouraging cooperation in the Traditional Medicine education field, mainly through training programs and means of communication; (f) having a consultation mechanism between the Parties' Traditional Medicine authorities; (g) encouraging cooperation in Traditional Medicine therapeutic services and products manufacturing; and (h) encouraging cooperation in research in the fields of Traditional Medicine in order to contribute in efficacy and safety assessments of natural resources and products used in health care.

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • Contractor Certification regarding Business with Certain Countries and Organizations Pursuant to Subchapter F, Chapter 2252, Texas Government Code], Contractor certifies Contractor is not engaged in business with Iran, Sudan, or a foreign terrorist organization. Contractor acknowledges this Agreement may be terminated and payment withheld if this certification is inaccurate.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

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