System Information Distribution Sample Clauses

System Information Distribution. System information in LTE is acquired through broadcasting a certain amount of information in each cell. In LTE is structured by means of System Information Blocks (SIBs), each of which contains a set of functionally-related parameters. The SIB types that have been defined include:  The Master Information Block (MIB), which includes a limited number of the most frequently transmitted parameters which are essential for a UE’s initial access to the network.  System Information Block Type 1 (SIB1), which contains parameters needed to determine if a cell is suitable for cell selection, as well as information about the time-domain scheduling of the other SIBs.  System Information Block Type 2 (SIB2), which includes common and shared channel information.  SIB3–SIB8, which include parameters used to control intra-frequency, inter-frequency and inter-RAT cell reselection.  SIB9, which is used to signal the name of a Home eNodeB (HeNB).  SIB10–SIB12, which includes the Earthquake and Tsunami Warning Service (ETWS) notifications and Commercial Mobile Alert System (CMAS) warning messages.  SIB13, which includes MBMS related control information.  SIB14, which is used to configure Extended Access Class Barring.  SIB15, which is used for convey MBMS mobility related information.  SIB16, which is used to convey GPS-related information. This list of System Information Block Types has been expanding over the years and is expected to keep increasing during the upcoming 3GPP releases. Information transmission presented afore is considered a key aspect. First of all, it is important to mention that this information is constantly broadcasted, but depending on the type of information, different periodicities are assumed. In LTE the time-domain scheduling of the MIB and SIB1 messages is fixed with periodicities of 40 ms and 80 ms. Furthermore, for the MIB the transmission is repeated four times during each period, i.e., once every 10 ms. SIB1 is also repeated four times within its period, i.e., every 20 ms, but with different redundancy version for each transmission. The time-domain scheduling of the SI messages (for the other SIBs) is flexible: each SI message is transmitted in a predefined periodic time window, while physical layer control signaling indicates in which subframes within this window the SI is actually scheduled. The scheduling windows of the different SI messages (referred to as SI-windows) are consecutive (i.e. there are neither overlaps nor gaps betwe...
AutoNDA by SimpleDocs

Related to System Information Distribution

  • Payroll Information Payroll checks shall include all required information, a clear designation as to the amount and category, e.g., regular, overtime or holiday pay, of compensation for which payment is being made.

  • Account Information Disclosure We will disclose information to third parties about your account or the transfers you make:

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

  • Confidential System Information HHSC prohibits the unauthorized disclosure of Other Confidential Information. Grantee and all Grantee Agents will not disclose or use any Other Confidential Information in any manner except as is necessary for the Project or the proper discharge of obligations and securing of rights under the Contract. Grantee will have a system in effect to protect Other Confidential Information. Any disclosure or transfer of Other Confidential Information by Xxxxxxx, including information requested to do so by HHSC, will be in accordance with the Contract. If Grantee receives a request for Other Confidential Information, Xxxxxxx will immediately notify HHSC of the request, and will make reasonable efforts to protect the Other Confidential Information from disclosure until further instructed by the HHSC. Grantee will notify HHSC promptly of any unauthorized possession, use, knowledge, or attempt thereof, of any Other Confidential Information by any person or entity that may become known to Grantee. Grantee will furnish to HHSC all known details of the unauthorized possession, use, or knowledge, or attempt thereof, and use reasonable efforts to assist HHSC in investigating or preventing the reoccurrence of any unauthorized possession, use, or knowledge, or attempt thereof, of Other Confidential Information. HHSC will have the right to recover from Grantee all damages and liabilities caused by or arising from Grantee or Grantee Agents’ failure to protect HHSC’s Confidential Information as required by this section.

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

  • Distribution and Pool Performance Information Item 1121(a) - Distribution and Pool Performance Information

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Furnishing of Information; Public Information (a) Until the earliest of the time that (i) no Purchaser owns Securities or (ii) the Warrants have expired, the Company covenants to maintain the registration of the Common Stock under Section 12(b) or 12(g) of the Exchange Act and to timely file (or obtain extensions in respect thereof and file within the applicable grace period) all reports required to be filed by the Company after the date hereof pursuant to the Exchange Act even if the Company is not then subject to the reporting requirements of the Exchange Act. (b) At any time during the period commencing from the six (6) month anniversary of the date hereof and ending at such time that all of the Securities may be sold without the requirement for the Company to be in compliance with Rule 144(c)(1) and otherwise without restriction or limitation pursuant to Rule 144, if the Company (i) shall fail for any reason to satisfy the current public information requirement under Rule 144(c) or (ii) has ever been an issuer described in Rule 144(i)(1)(i) or becomes an issuer in the future, and the Company shall fail to satisfy any condition set forth in Rule 144(i)(2) (a “Public Information Failure”) then, in addition to such Purchaser’s other available remedies, the Company shall pay to a Purchaser, in cash, as partial liquidated damages and not as a penalty, by reason of any such delay in or reduction of its ability to sell the Securities, an amount in cash equal to two percent (2.0%) of the aggregate Subscription Amount of such Purchaser’s Securities on the day of a Public Information Failure and on every thirtieth (30th) day (pro rated for periods totaling less than thirty days) thereafter until the earlier of (a) the date such Public Information Failure is cured and (b) such time that such public information is no longer required for the Purchasers to transfer the Shares and Warrant Shares pursuant to Rule 144. The payments to which a Purchaser shall be entitled pursuant to this Section 4.2(b) are referred to herein as “Public Information Failure Payments.” Public Information Failure Payments shall be paid on the earlier of (i) the last day of the calendar month during which such Public Information Failure Payments are incurred and (ii) the third (3rd) Business Day after the event or failure giving rise to the Public Information Failure Payments is cured. In the event the Company fails to make Public Information Failure Payments in a timely manner, such Public Information Failure Payments shall bear interest at the rate of 1.5% per month (prorated for partial months) until paid in full. Nothing herein shall limit such Purchaser’s right to pursue actual damages for the Public Information Failure, and such Purchaser shall have the right to pursue all remedies available to it at law or in equity including, without limitation, a decree of specific performance and/or injunctive relief.

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