Impact on the RRC Idle State Clause Samples

Impact on the RRC Idle State. The need for Idle mode has been questioned in 5G as the “Always on Applications” used in the smart phones need to send and receive small packets frequently to keep IP connectivity open. Essentially the frequent connection requests are related to push services where the UE is checking if there is any new information in their application server. Typically, this is UE initiated and happens in un-controlled way from the radio network perspective. Another problem from network perspective is the “heart beat” or “keep alive” messaging that may occur once per minute, or once every few minutes, and the amount of data is very small (<<1 Kbyte). These messages are used to keep the device connectivity towards network in RRC Connected state. METIS-II assumes that the UEs (including smart phones, MTC devices or other kinds of terminals) can be always connected to network and that the operational state transition in UE between inactive/connected and active/connected can provide power savings during inactivity and optimized performance during active state, and that the state transition is introducing minimum system access latency. The new RRC Connected Inactive state has many features of the existing LTE IDLE state, such as low activity towards network and UE based mobility using the cell reselection procedure. Despite the enhanced features/functionality, the IDLE state in 5G mobile systems may be needed. One major reason is that the needed fault recovery mechanism will add complexity to the new Connected Inactive state. It is an essential requirement for the UE to be able to revert or fallback to a recovery state in case of sudden connectivity fault or network failure. The IDLE state in 5G can for example support the bootstrap procedures, initial PLMN selection, UE controlled mobility, contention based uplink transmission and core network based location tracking.
View Source

Related to Impact on the RRC Idle State

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (▇▇▇▇▇://▇▇▇▇▇.▇▇▇.▇▇▇▇▇.▇▇.▇▇/tpasscmblsearch/index.jsp) or by contacting

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including RTU for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG shall immediately after each synchronization/tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Reporting Frequency During any period of time when you are subject to the requirement in paragraph 1 of this award term and condition, you must report proceedings information through ▇▇▇ for the most recent five year period, either to report new information about any proceeding(s) that you have not reported previously or affirm that there is no new information to report. Recipients that have Federal contract, grant, and cooperative agreement awards with a cumulative total value greater than $10,000,000 must disclose semiannually any information about the criminal, civil, and administrative proceedings.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.