Use case introduction Sample Clauses

Use case introduction. This use case will address large-scale application of Unified Communication Services using HTML5 based Web Browsers on Embedded Systems. HTML5 offers new capabilities to create web pages, especially in terms of dynamic elements. WebRTC is set of technologies that are being standardized by the IET, W3C and 3GPP. WebRTC allows the possibility to have multimedia sessions (audio, video, chat, etc) from any browser and device with no need to install or update anything, so this technology is called to be the next big thing in unified communications during the next years. WebRTC defines an API in the browser so that it can be used as a real-time multimedia terminal (audio, video, file transfer, screen sharing, etc.). Websocket new transport protocol, defined by HTML5, is a perfect complement to WebRTC technology as it allows to easily exchange signalling information between the browser and the server. WebRTC technology was initially designed having browser-to-browser real-time communication in mind, but it allows to be used in conjunction with different kinds of servers to provide additional and interesting services such as videoconferencing and connection to PSTN. The independence from the platform or the type of device, together with the fact that there is no need to install or update anything, is going to make easier the adoption by end users. This represents a big opportunity for telecoms and enterprises to offer or expose new services. The main goal of this use case is to implement HTML5 and WebRTC in small embedded systems. As these services are available in any device with a browser with WebRTC support, different options are available to evaluate results of EMC2. Devices like Raspberry Pi, Firefox OS smartphones, devices based on Intel smart devices for WebRTC, HDMI dongles, Chromecast are some examples of embedded devices ready to work with WebRTC. Attending to the motivation on the use case and taking into account the possibility to evaluate the results and indicators we have chosen a device of the family of Android TVs that have a reduced size, runs an Android OS with browsers with WebRTC support and have the possibility to add multimedia peripherals (camera and microphone). The application will be a peer-to-peer videoconferencing solution between two devices that can help to evaluate the quality of experience (and multi-core processing performance). In addition, a method to exchange data via datachannels will be available, as a tool to promote this sol...
AutoNDA by SimpleDocs
Use case introduction. This use case targets to demonstrate that the developments conducted within the WPs of this project with respect to open deterministic networks have been taken to the next level in cross domain industrial applications. The aim is to showcase the potential of open deterministic networking by connecting a variety of local embedded systems to other embedded systems. While the IoT today is characterized and dominated by uncritical (i.e. non-safety related) applications that follow best-effort communication scheme, the increasing integration of also safety-critical domains such as transportation or (industrial) automation is the today a megatrend. Hard real-time networking and control are traditionally fields in which safety, security and guaranteed operation are key requirements. Such systems have typically remained closed or semi-open to the wider Internet network. The real-time IoT is the trend that will drive the application of IoT connectivity to hard real-time systems. For example: Wind turbines that are precisely controlled in hard real-time over the same infrastructure as data is being transmitted and analysed remotely, autonomous cars that are controlled in-vehicle but can also interact with their physical environment, and robots that are able to safely move around factory floors and work together with the human workforce. Last but not least, the real-time IoT as envisioned in this demonstrator is an enabling technology for future System-of-systems (SoS), where distributed components or systems will be connected and integrated towards larger systems only when adequate networking infrastructure becomes available that is in particular suited for mixed-criticality integration,.
Use case introduction. The Smart Grid combines electricity and IT infrastructure to integrate and inter-connect all users (producers, operators, marketers, consumers etc) in order to continue to efficiently balance demand and supply over an increasingly complex network.
Use case introduction. This use case addresses large-scale application of Unified Communication Services using HTML5 based Web Browsers on Embedded Systems. A device of the family of Android TVs was selected to act as one of the web points with the possibility to add multimedia peripherals like camera and microphone. The application is a peer-to-peer videoconferencing solution between two devices which has been explained in “D11.3 Detailed design and first prototype”.
Use case introduction. The use-case demonstrates a novel approach for monitoring people on airports and measuring passenger data by interconnecting cameras, servers and clients. The person tracking application, which creates metadata by extracting semantic information from image data and the additional middleware, both being developed in WP12, are used to implement the demonstrator’s passenger monitoring. Cameras (servers) and clients are specifically connected via Ethernet to stream video and TTEthernet for exchanging generated metadata. TTEthernet is based on a deterministic communication architecture which is standard for hard real-time systems for example in aircrafts and vehicles. The specific system behaviour enables two applications: 1. Cameras (servers) and clients are specifically connected via TTEthernet for ensuring that the transmission of metadata (e.g. alerts) does not fail even during a network congestion (Figure 4). Such latency is a serious problem when seeing camera networks as part of future cyber-physical airport systems, for example the rapidly emerging demand of measuring passenger waiting times in real-time at security gates for automated proactive intervention into the gate process.
Use case introduction. The Autonomic home networking use case aims to deal with numerous multi – criticality issues in an autonomic smart – building environment, through the design and development of a de- centralized system consisting of autonomic distributed decision making units, which can be connected to and control multiple building devices. The decisions of these units may lead to a set of “solutions” si S={s1, s2, … , sN} where each si corresponds to a different combination of the home‘s devices operations. The envisioned system will be able to manage multiple data flows of information and requirements, with different weights of importance, and come up with the best solution of this solution set. The main requirements of the system may be categorized as follows: (i) Building’s total energy consumption minimization, (ii) Services’ delivery delay minimization and (iii) Users’ satisfaction level. The planned demonstrator / prototype, described in detail in the next section, will be based on an autonomous smart building system. Data will be gathered from a set of sensors embedded inside the house, regarding both the environment and the state of the user. The data will be available through a registry unit, and will be accessed in a service – based basis. Each time the system is triggered by a service, data will be analyzed in a distributed manner, and the system will decide upon how devices in the house should operate in order to meet the user’s needs, meaning that the system will choose from one of the N possible solutions.

Related to Use case introduction

  • Use Cases Subscription Services are provided for Software only when used for its supported purpose (“Use Case”). The Use Case determines which Subscription is required and what fees are charged. If you use or deploy the Software in a manner contrary to a supported Use Case, you are responsible for purchasing the appropriate Subscription(s) to cover such usage. For example, if you are using a Red Hat Enterprise Linux Desktop Subscription as a server, you are obligated to purchase a Red Hat Enterprise Linux Server Subscription.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Early Construction of Base Case Facilities Developer may request Connecting Transmission Owner to construct, and Connecting Transmission Owner shall construct, subject to a binding cost allocation agreement reached in accordance with Attachment S to the ISO OATT, including Section 25.8.7 thereof, using Reasonable Efforts to accommodate Developer’s In-Service Date, all or any portion of any System Upgrade Facilities or System Deliverability Upgrades required for Developer to be interconnected to the New York State Transmission System which are included in the Base Case of the Class Year Study for the Developer, and which also are required to be constructed for another Developer, but where such construction is not scheduled to be completed in time to achieve Developer’s In-Service Date.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (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 Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer 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. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Case Management Prompt resolution of any dispute is important to both parties; and the parties agree that the arbitration of any dispute shall be conducted expeditiously. The arbitrators are instructed and directed to assume case management initiative and control over the arbitration process (including scheduling of events, pre-hearing discovery and activities, and the conduct of the hearing), in order to complete the arbitration as expeditiously as is reasonably practical for obtaining a just resolution of the dispute.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • SCOPE OF SERVICES/CASE HANDLING A. Upon execution by GPM, attorneys are retained to provide legal services for the purpose of seeking damages and other relief in the Litigation. Client provides authorization to seek appointment as Lead Plaintiff in the class action, while the Attorneys will seek to be appointed Class Counsel. If this occurs, the Litigation will be prosecuted as a class action. B. If you obtain access to non-public information during the pendency of the Litigation, you must not engage in transactions in securities. C. Attorneys are authorized to prosecute the Litigation. The appointed Lead Plaintiffs will monitor, review and participate with counsel in the prosecution of the Litigation. The Attorneys shall consult with the appointed Lead Plaintiffs concerning all major substantive matters related to the Litigation, including, but not limited to, the complaint, dispositive motions and settlement. Because of potential differences of opinion between Clients concerning, among other things, strategy, goals and objectives of the Litigation, the Attorneys shall consult with the appointed Lead Plaintiffs as to the courses of action to pursue. The Client agrees to abide by the decisions of the appointed Lead Plaintiffs, which shall be final and binding on all Clients. D. GPM is given the authority to opt the Client out of any class action proceeding relating to the claims authorized herein and/or pursue the Client claim individually in a group action, if the Client is not appointed Lead Plaintiff and GPM is not appointed Class Counsel. E. The Attorneys shall provide sufficient resources, including attorney time and capital for payment of costs and expenses, to vigorously prosecute the Litigation. F. Any recovery from defendants that the Attorneys are responsible for will be divided among class members based on the recognized loss by each class member as calculated by a damage allocation plan which will be prepared by a financial expert or consultant, provided to the appointed Lead Plaintiffs, be subject to the Court's approval and will account for such factors as size of securities ownership, date of purchase, date of sale and continued holdings, if any. Under the rules governing class action litigation, while the Lead Plaintiffs recover according to the same formula as other class members, the Court may approve, upon application therefore, reimbursement of the Lead Plaintiffs’ reasonable costs and expenses directly related to the representation of the class. Examples are lost wages and travel expenses associated with testifying in the action.

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