Joint Transmission (JT) Sample Clauses

Joint Transmission (JT). With no standardised support in Release 11 for JT, simultaneous transmission of the same signal is arranged from multiple transmission points (TPs). In Long Term Evolution (LTE), the same resource blocks (RBs) are used for transmission to the same user in the downlink and therefore the suitability of JT is only limited to lightly-loaded networks [9]. This technique enhances the received SINR at the receiver as the interference signals transmitted from neighbouring base stations now become part of the final desired signal. This is particularly useful at the cell-edge of dense heterogeneous deployments in which, due to the vicinity of mobile users to other base stations, inter-cell interference effects place heavier performance burden on the network. Joint transmission (JT) requires copies of the same user data signals to be available at different sites. The scheme can be implemented coherently or non-coherently based on backhaul capabilities and operator requirements. Backhaul requirements of this scheme is significantly higher than other CoMP techniques. Since the CSI are quantised and can be outdated very rapidly, JT remains sensitive to the errors in the reported CSI [7]. Fast changing propagation channel information between users and base stations need to be reported to base stations taking part in JT in order to dynamically perform link adaptation. Such frequent CSI reporting also avoids CSI out-dating which is best achieved through the joint base station scheduling. A joint scheduler’s performance will be enhanced if signalling delay between base station is re- duced. Baseband processing units (BBU) of multiple cooperating TPs can be grouped together in the C-RAN allowing for resource pooling and this way, low latency coordination can be made possible amongst base stations [8]. A fast backhaul solution such as a centralised BBU is particularly important to realise coherent JP in which precoding of transmission signals are carried out with consideration to those of other TPs’ (i.e. spatial CSI feedback), requir- ing better synchronisation and lower backhaul latency. In non-coherent JT, transmission signals are precoded individually with no knowledge about the neighbouring base stations’ radio link quality with the users being served. Di- versity gain is exploited in this mode of JT and strongest copy of the same signal arriving from different TPs is chosen and the rest discarded. Such a scheme will have the disadvantage of generating interference to ot...
Sample 1
AutoNDA by SimpleDocs

Related to Joint Transmission (JT)

  • Merchant Transmission Facilities “Controllable A.C. Merchant Transmission Facilities” shall mean transmission facilities that (1) employ technology which Transmission Provider reviews and verifies will permit control of the amount and/or direction of power flow on such facilities to such extent as to effectively enable the controllable facilities to be operated as if they were direct current transmission facilities, and

  • Firm Point-To-Point Transmission Service “Non-Firm Point-To-Point Transmission Service” shall mean Point-To-Point Transmission Service under the Tariff that is reserved and scheduled on an as-available basis and is subject to Curtailment or Interruption as set forth in Tariff, Part II, section 14.7. Non-Firm Point-To-Point Transmission Service is available on a stand-alone basis for periods ranging from one hour to one month. Non-Firm Sale:

  • Data Transmission The procedures for transmitting load obligation data to PJM for DS Supplier’s DS Load shall be as set forth by PJM.

  • Data Transmission Control Except as necessary for the provision of the Cloud Services in accordance with the Agreement, Personal Data must not be read, copied, modified or removed without authorization during transfer. Where data carriers are physically transported, adequate measures are implemented at SAP to provide the agreed-upon service levels (for example, encryption and lead-lined containers). Measures: • Personal Data in transfer over SAP internal networks is protected according to SAP Security Policy. • When data is transferred between SAP and its customers, the protection measures for the transferred Personal Data are mutually agreed upon and made part of the relevant agreement. This applies to both physical and network based data transfer. In any case, the Customer assumes responsibility for any data transfer once it is outside of SAP-controlled systems (e.g. data being transmitted outside the firewall of the SAP Data Center).

  • Connecting Transmission Owner Obligations Connecting Transmission Owner shall maintain its transmission facilities and Attachment Facilities in a safe and reliable manner and in accordance with this Agreement.

  • Transmission Control In-transit: We make HTTPS encryption (also referred to as SSL or TLS) available on every one of its login interfaces and for free on every customer site hosted on the HubSpot products. Our HTTPS implementation uses industry standard algorithms and certificates. At-rest: We store user passwords following policies that follow industry standard practices for security. We have implemented technologies to ensure that stored data is encrypted at rest.

  • Loop Transmission Types 3.1 Subject to the conditions set forth in Section 1 of this Attachment, Verizon shall allow CBB to access Loops unbundled from local switching and local transport, in accordance with this Section 3 and the rates and charges provided in the Pricing Attachment. Verizon shall allow CBB access to Loops in accordance with, but only to extent required by, Applicable Law. The available Loop types are as set forth below:

  • Transmission encryption All data transmissions of County PHI or PI outside the secure internal network must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as AES. Encryption can be end to end at the network level, or the data files containing PHI can be encrypted. This requirement pertains to any type of PHI or PI in motion such as website access, file transfer, and E-Mail.

  • Other Transmission Rights Notwithstanding any other provision of this Agreement, nothing herein shall be construed as relinquishing or foreclosing any rights, including but not limited to firm transmission rights, capacity rights, or transmission congestion rights that the Developer shall be entitled to, now or in the future under any other agreement or tariff as a result of, or otherwise associated with, the transmission capacity, if any, created by the System Upgrade Facilities and System Deliverability Upgrades.

  • Transmission Service Point-To-Point Transmission Service provided under Part II of the Tariff on a firm and non-firm basis.

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