CoMP Implementation Challenges Sample Clauses

CoMP Implementation Challenges. CoMP as a major enabler is envisioned for future mobile network generations. However, to reap the true performance gains, several limiting factors have been identified that require rectification. The extent to which performance measures of CoMP are compromised by any the following elements depend on the mode and deployment scenario at hand. Cooperation between the TPs in different sectors of the same base station does not require additional backhaul. Also the implemen- tation of this mode of cooperation is relatively simple since the scheduling and processing functions required for CoMP can easily be upgraded and are currently co-located [8]. In the case of inter-site CoMP however, base station cooperation requires con- stant exchange of control signalling over the air interface and the backhaul. User measurements of the channel state information (CSI), preprocessed or quantised user data and user control data need to be shared amongst TPs synchronously over the X2 [6]. The long-term and short-term reporting of CSI are used for the purpose of Hand Over (HO) preparation and link adaptation, respectively. This will consequently require a backhaul capacity of around a few Mbps to 4 Gbps and approximate backhaul latencies of no more than around a few millisec- onds. Large backhaul latencies will result in channel ageing [7] in which case, the outdating of the reported CSI will result in performance degradation of CoMP. To cater for this stringent backhaul requirement incurred by CoMP, base band processing unit (BBU) pooling offered by Cloud Radio Access Network (C-RAN) is identified as the most suitable candidate [13] [14]. Current backhaul latencies range from 100 Microseconds to about 20 milliseconds. Various factors that xx- xxxxxxx such delays can be either network technology related or stem from the choice of backhaul technology used. Processing delays introduced by network nodes and switching equipment are amongst examples of the former. The X2 backhaul connections such as conventional or millimetre microwave, multi-hop and fibre optic connections each contribute to latencies experienced in inter-site base station cooperation [6]. Another necessity for low backhaul latencies for CoMP to be feasibly realised is to avoid the limiting effect of such delays on the Hybrid Automatic Repeat Request (HARQ) that CoMP will need to be implemented with. To control the volume of feedback and control signalling traversing the X2, efficient feedback compression schemes...
AutoNDA by SimpleDocs

Related to CoMP Implementation Challenges

  • COOPERATION IN IMPLEMENTATION On demand of the other Spouse and without undue delay or expense, each Spouse shall execute, acknowledge, or deliver any instrument, furnish any information, or perform any other acts reasonably necessary to carry out the provisions of this Agreement. If a Spouse fails to execute any document as required by this provision, the court may appoint the court clerk or his or her authorized designee to execute the document on that Xxxxxx’s behalf.

  • Project Implementation The Borrower shall:

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Implementation of Corrective Action Plan After the Corrective Action Plan is finalized, the Purchasers shall use reasonable best efforts to implement the finalized Corrective Action Plan on the timeline set forth therein and provide periodic reports (as provided for therein) to the Sellers on the status of their implementation of the Corrective Action Plan.

  • Implementation and Review The Parties shall consult annually, or as otherwise agreed, to review the implementation of this Chapter and consider other matters of mutual interest affecting trade in services. (10) 10 Such consultations will be addressed under Article 170 (Free Trade Commission) of Chapter 14 (Administration of the Agreement).

  • Implementation i) Where the job/time sharing arrangement arises out of the filling of a vacant full-time position, the full-time position will be posted first and in the event that there are no successful applicants, then both job/time sharing positions will be posted and selection will be based on the criteria set out in the Collective Agreement. ii) An incumbent full-time employee wishing to share her or his position may do so without having her or his half of the position posted. The other half of the job/time sharing position will be posted and selection will be made on the criteria set out in the Collective Agreement. iii) It is understood and agreed that the arrangement is for a trial period of six (6) months for the full-time employee originating the request. Once the trial period is over, the employee cannot revert to her former position except under (v) below. iv) Where two (2) full-time employees wish to job/time share one (1) position, neither half will be posted providing this would create one (1) full-time position to be posted and filled according to the collective agreement. v) If one of the job/time sharers leaves the arrangement, her or his position will be posted. If there is no successful applicant to the position, the remaining employee will revert to her or his former status. If the remaining employee was previously full-time, the shared position will become her/his position. If the remaining employee was previously part-time and there is no part-time position available, she or he shall exercise her or his layoff bumping rights to obtain a part-time position. The shared position would then revert to a full-time position and be posted according to the Collective Agreement.

  • Application of Funding Techniques to Programs 6.3.1 The State shall apply the following funding techniques when requesting Federal funds for the component cash flows of the programs listed in sections 4.2 and 4.3 of this Agreement. 6.3.2 Programs Below are programs listed in Section 4.2 and Section 4.3.

  • Implementation of Agreement Each Party must promptly execute all documents and do all such acts and things as is necessary or desirable to implement and give full effect to the provisions of this Agreement.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Implementation Services Vendor shall provide the Implementation Services, if any, described in Exhibit A. The Services Fees for any Implementation Services shall be described in Exhibit A.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!