The UNCAP Data Broker (UDB Sample Clauses

The UNCAP Data Broker (UDB. This is a module of the UNCAP Cloud services providing communication support among the different components of the UNCAP platform and the devices/data sources connected to it. The UDB exposes an API allowing devices and data sources to register to the platform itself and to inject updates (measurements, alarms, etc.). Several protocols (HTTP/HTTPs, MQTT, STOMP) are supported for accessing the API and an internal authentication and authorization system allows multi-user management and device data/functionalities access according to specific, configurable permissions. Data received by UDB is stored (through dedicated API) into CHINO, a platform allowing the storage of sensitive health information in compliance with the EU data protection laws. Data can be retrieved by authorized users via CHINO API. In addition to this, the UDB implements a pub/sub mechanism allowing external entities (users, applications, other devices, etc.) to be notified of any new update generated by a device/data source registered in UNCAP. UDB forwards the newly generated update to all the subscribers: the subscription is a simple service that can be triggered via UDB API. Finally, in order to help new users subscribe for updates regarding specific categories (i.e., measurements, positions, alarms), an update aggregator has been implemented (named Paperboy). Such a piece of software is in charge of: • collecting all the updates that are injected into the UDB, • aggregating the updates according to their type, • exposing the aggregated updates for external subscribers. By doing so, Paperboy implements a single entry point for all the subscribers interested in messages related to a specific category. The component has the advantage of allowing users to: • subscribe all the devices/data sources generating a given kind of information, • detect the newly created/deleted devices/data sources associated to the type of information of interest, • update the subscriptions. Moreover, the aggregation performed by Paperboy can be seen as the starting point for more advanced services that can be implemented through the integration with other platform modules, in particular with the Complex Event Processor module (CEP).
Sample 1
AutoNDA by SimpleDocs

Related to The UNCAP Data Broker (UDB

  • Record and File Retention Grantee must maintain these files for five years after the end of the applicable fiscal year, except that, if any litigation, claim or audit is commenced with respect to the transactions documented by such files before the end of the aforementioned five-year period and extends beyond the expiration of the five-year period, these files must be retained until all litigation, claims, or audit findings involving the files have been resolved.

  • Your Billing Rights: Keep This Document For Future Use This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Information Transfer and Storage Supplier will use Industry Standard encryption to encrypt Accenture Data that is in transit. Supplier will also use Industry Standard encryption to restrict access to Accenture Data stored on physical media that is transported outside of Supplier facilities.

  • Provide Data In Compliance With State and Federal Law LEA shall provide data for the purposes of the Service Agreement in compliance with FERPA, COPPA, PPRA, Texas Education Code Chapter 32, and all other Texas privacy statutes cited in this DPA as these laws and regulations apply to the contracted services. The LEA shall not be required to provide Data in violation of applicable laws. Operator may not require LEA or users to waive rights under applicable laws in connection with use of the Services.

  • Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:

  • YOUR BILLING RIGHTS - KEEP THIS NOTICE FOR FUTURE USE This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Non-discrimination Based on National Origin as evidenced by Limited English Proficiency The Contractor agrees to comply with the non-discrimination requirements of Title VI of the Civil Rights Act of 1964, 42 USC Section 2000d, et seq., and with the federal guidelines promulgated pursuant to Executive Order 13166 of 2000, which require that contractors and subcontractors receiving federal funds must assure that persons with limited English proficiency can meaningfully access services. To the extent the Contractor provides assistance to individuals with limited English proficiency through the use of oral or written translation or interpretive services in compliance with this requirement, such individuals cannot be required to pay for such services.

  • Liability for Failure to Stop Payment of Preauthorized Transfers If you order us to stop payment of a preauthorized transfer three (3) business days or more before the transfer is scheduled and we do not do so, we will be liable for your losses or damages.

  • Provisions for Covered Entity to Inform Business Associate of Privacy Practices and Restrictions (a) Covered Entity shall notify Business Associate of any limitation(s) in the notice of privacy practices of Covered Entity under 45 CFR 164.520, to the extent that such limitation may affect Business Associate’s use or disclosure of protected health information.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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