Technical Overview at the commencement of this Agreement, the Licensor undertakes to provide technical overview, and materials in relation to the use of the Software, to nominated employees of the Licensee, such overview and materials to be determined at the discretion of the Licensor.
Technical Overview. We now proceed to present our results in greater detail. The primitive—succinctly reconstructed distributed signatures (SRDS)—is a new type of a dis- tributed signature scheme, with a natural motivation: allowing a set of parties to jointly produce a signature on some message m, which can serve as a succinct certificate for proving that a ma- jority of the parties agree on m. Interestingly, this task does not seem to be attained by existing distributed signature notions, such as multi-signatures [64], aggregate signatures [14], or threshold signatures [47]. For example, while multi-signatures (and, similarly, aggregate signatures) can suc- cinctly combine signatures of many parties, to verify the signature, the (length-Θ(n)!) vector of contributing-parties identities must also be communicated.8 As discussed in the related-work sec- tion (Section 1.3), threshold signatures are implied by SRDS but also do not suffice: while identities of the signers are no longer needed to verify a combined signature, this information is necessary to reconstruct the combined signature in the first place (even within specific existing schemes, e.g., [54, 12]). We provide a more detailed comparison to different signature notions in Section 1.3. An SRDS scheme is based on a PKI for signatures, where every party is set with a secret signing key and a public verification key.9 The parties may receive additional setup information that may contain, for example, public parameters for the signature scheme or a common random string (CRS), depending on the actual construction. Given a message m, every party can locally generate a signature on m, and signatures on the same message can be succinctly aggregated into a new signature. The new aspect is that given a combined signature and a message m, it is possible to verify whether is was aggregated from a “large” number of “base” signatures on m, and both aggregation and verification can be done succinctly. Three properties are required from an SRDS scheme: robustness means that an adversary cannot prevent the honest parties from generating an accepting signature on a message; unforgeability prevents an adversary controlling a minority from forging a signature; and succinctness requires that the “final” signature (including all information needed for verification) is short (of size O˜(1)) and can be incrementally reconstructed from “base” signatures in small batches of size polylog(n).10 An SRDS scheme is t-secure if it satisfies the ab...
Technical Overview. Our application consists of a proprietary algorithm which operates agnostically across several mobile platforms. The algorithm is designed to function with the majority of popular embedded codes and necessarily is scalable to accommodate the mass market. The algorithm is compatible with WiFi (Wireless local area network Wireless fidelity IEEE 802.11), 3G (3rd Generation WCDMA network incorporating HSDPA- High-Speed Data Packet Access and UTMS- universal mobile telephone system). The algorithm is compatible with proprietary GSM standards essentially utilizing EDGE (Enhanced Data Rates for GSM). It represents a configuration of compiled data which interacts with wireless networks (including mobile telephony networks) and with internally hosted servers which correspond with mobile devices through multiple acccess sockets. Sockets are allocated primarily for proprietary applications. ARL (augmented reality link), VRL (voice recognition link) and GRL (geographic resource locator). A newly assigned algorithm includes a barcode scanner. The details of each facet are described below: ARL essentially utilizes Augmented reality (AR) and is a technology which provides a live direct or indirect view of a physical real-world environment whose elements are augmented by virtual computer-generated imagery. The link utilizes the mobile’s digital camera to take a photograph of an object, logo or word. The results are transmitted OA (over air) and submitted to a proprietary’s source database. Thereonafter, the information is balanced, moderated and processed within our vision cluster environment. Additionally, this link provides the user with an option to utilize image recognition both uplink and downlink interacting with proprietary server systems. By pointing the phone’s camera at the real world and receiving augmented information directly related to the view of the camera. This might include the position of points of interest or commercial outlets. Additional sockets are allocated for Voice Recognition Link (VRL) which uses the telephone’s inbuilt microphone to capture an audio file which is submitted it through to a proprietary server environment. This audio file specifically interacts between the production environment and the Nuance external voice recognition vocoding server. These same sockets are allocated for Geographic Resource Locator (GRL). This utilizes the telephone’s GPS (Global Position System) capabilities to correlate the location of the user and the search...
Technical Overview. The GoldSeal VaaS offer functions as a standalone Virtual Meeting Room (“VMR”) for meeting participants to connect via video and audio across the open Internet. VMR features include: • Reservation-less, standard definition and high definition (up to 1080p30) video and audio conferencing with content sharing • Accessible by Polycom end-point portfolio, both hard and soft clients • H.323 and SIP standards-based connectivity • Browser-based soft client video endpoint support through web real-time communication (WebRTC) Interoperability with Lync endpoints available through Open Federation for Microsoft® Lync • Access to free versions of Polycom® RealPresence® Desktop and Polycom® RealPresence® Mobile o Soft clients available to employees (“Internal Users”) within a subscribing enterprise • Content sharing enabled through access to free versions of Polycom’s People+Content IP application • US and EMEA toll based audio dial-in access • Each VMR instance is assigned by the VMR system administrator, to a specific individual who is the owner and host of that VMR. Each VMR includes a unique bridge number and customer-enabled PIN code. • Soft endpoint registration included with VMRs, hard endpoint registration services available separately as an option for an additional fee. • Point-to-point dialing, dial-in and dial-out services available for registered endpoints • A end-user Portal is provided as an online resource for GoldSeal VaaS users to access support resources, including dialing instructions, documentation, live conference control capabilities, FAQs and access to submit support questions to our GoldSeal Technical Support team. • Demo and Trial services are offered free of charge to allow customers to try the service before they buy • Enterprise user license (“EUL”) - an “all-you-can-eat” VMR subscription with no overage fees, assigned to an individual user, for up to 25 participants per session o As an extension of EUL, Enterprise Wide Licensing is also available for parent company's willing to commit to the strategic growth and standardization of video technology across their complete user based. o Enterprise Wide pricing is only available in prepaid 1, 2 or 3 year plans. Contact us to see if you qualify • Fixed Capacity VMR is a VMR subscription service intended to be shared among teams. The Fixed Capacity VMR service has 3 different offerings based on the number of participants (up to 5, 10 or 25 participants), without overage fees • Endpoint Subscription...
Technical Overview. We give an overview of the main techniques used in our protocol. Expand-and-Extract. Our starting point is the recent work by Xxxxx, Xxx- Xxxxx and Loss [FLL21], where the authors provide a new elegant way to design round-efficient BA protocols, called Expand-and-Extract. The Expand-and-Extract iteration paradigm consists of three steps. The first step is an expansion step, where an input bit is expanded into a value with range ℓ, via a so-called Proxcensus protocol. This protocol guarantees that the outputs of honest parties lie within two consecutive values (see Definition 2).
Technical Overview. The delivering of a turnkey system to meet the GIMDE 2000 Workflow / Production Management needs encompasses a variety of activities ranging from requirements definition to final system checkout. Template Software has developed an integration approach to execute these activities in a manner designed to minimize risk and field capabilities as soon as possible. This approach is founded on several key components. First and foremost, this effort is primarily a software development and integration task that has associate risks. These risks include requirements management, external interface control, integration of COTS and custom built software, and user satisfaction. The second key component is the time constraints associated with the Year 2000 issue. Unlike past efforts, where a delay in a program only meant that users had to wait longer for the capability, in this case, the lack of a working solution has direct day to day impact on NIMA operations. Without a working system in place by the end of 1999, NIMA is faced with operating without a production management system. Recognizing this Year 2000 issue calls for a management approach that assures software delivery of critical items early in the program. This will minimize the Y2K program risk. The approach Template has developed is designed around these two components by minimizing software risk and working toward near term software deliveries. The following description of Template's approach is divided into three primary sections: Requirements Management; Software Development; and System Deployment. Each section describes the roles and processes that will be used to execute their activities and describes how they contribute to the reduction of software development risks and early software deliveries.
Technical Overview. The EduSpace technical architecture seeks both focus and generality. We have designed the lower levels of the Eduspace system to be homogeneous, powerful, and generally transparent to the user. The interface is intuitive, powerful, and task specific. The following components of the technical architecture define the Instructional Development Workstation. Each component is described briefly below and in detail in the sections which follow.
Technical Overview. School Cash Suite is a SaaS offering built on top of the Microsoft stack and leverages a “database-per-district” configuration to ensure student and accounting data is not commingled with other districts. This data is hosted in the United States for US districts (and in Canada for Canadian districts). As a SaaS solution, the suite does not offer direct access to a database but supports imports/exports to enable seamless integrations with other systems, including reporting and dashboarding solutions.
Technical Overview. We give now give a more detailed overview over our techniques.
Technical Overview. The Search and Transformation Framework is split into a number of constituent parts, all of which are separate and independently deployable. These are listed below: ● Platform Primitives ● Contribution Framework ● Execution Framework ● Search Framework Each part can be developed, deployed and operated independently and in isolation. They each provide value individually and collectively, so a user can pick and choose which parts to adopt in an isolated and iterative way, facilitating pragmatic business and commercial integration. Furthermore, as described in D4.1, Smart Search Framework POC, for each framework, a modular development pattern has been followed (libraries, distributions, solutions) ensuring that even subsystems and subcomponents can be distributed and reused in different ways. The diagram above displays the relationship between the frameworks and constituent parts and can be summarised as follows. The Contribution Frameworks provides a means for individual contributors to develop and share vocabularies, classifiers and transformers in a consistent and interoperable way. Vocabularies, classifiers and transformers are deployed into the execution framework, where their capabilities can be advertised for classification, transformation and implicit and explicit chaining. The outputs of the execution framework, along with available transformation options, are ingested into the search framework and made available to the end user via a search user interface, demonstrated in D4.4 Smart Search Prototype. All the aforementioned frameworks depend on a variety of subsystems for network, security, storage and compute, which are provisioned as platform primitives.
