Detailed design of the Sample Clauses

Detailed design of the first prototype The first prototype is designed as a proof of concept using off the shelf components to demonstrate the functionality of multi-secure element handler. A block diagram representation of the prototype is given in Figure 14. Figure 14 - First prototype representation (top), Off-the-shelf implementation (bottom left) and development board (bottom right) A brief description about the components of the test setup is given below • MSE Handler: It is a generic microcontroller (ARM Cortex M3) that interfaces multiple secure elements on one side and Test Bench (or Host in actual deployment environment) on the other side using standard serial protocols. It acts as a scheduler that queues the multiple asynchronous security requests of the networked clients connected to the host. MSEH arbitrates the requests, assigns priority and allocates suitable secure element for execution based on the type of service demanded by clients. It configures (& reconfigures) individual SEs to service the request based on its type (increased utilization factor) and offers parallel processing of requests (increased throughput). It simply routes the client’s request to SE and doesn’t perform any crypto operations by itself. It supports all standard communication interfaces like USART, SPI, Ethernet, USB etc. to the host and hence can be connected to any decentralized (free) bus of it [REQ_01R_NXP_001]. • Secure element: It is a Common Criteria certified NXP secure crypto controller that supports standard crypto operations like authentication, encryption/decryption, digital signatures (SHA1, SHA224, SHA256 & MD5), certificates (X.509 based & PKCS#15 format) and secure storage. It finds application mainly in smartcard domains for banking, e-Gov, transportation, loyalty, health- insurance cards, smart-meters and identity sectors. It has asymmetric or PKI coprocessors (RSA up to 2048 bit keys & ECC over GF (p) up to 320 bit keys) [REQ_01R_NXP_005] & symmetric coprocessors (SEED, 2/3 key triple-DES & 128/192/256 bit keys AES {in ECB, CBC & CBC-MAC modes}) [REQ_01R_NXP_006] and compliant with JavaCard v3.0.1 & Global platform specs. In addition, it has true random number generator & supports CRC calculations. Its powerful cryptographic core is robust against attacks and possesses several countermeasures for protection of device assets. • Test Bench: It simulates the host interface to the MSEH. It generates multiple client requests and simulates different load scenarios with differ...
Sample 1
AutoNDA by SimpleDocs
Detailed design of the first prototype A first prototype has been developed as a proof of concept of how is possible to enable parallelism for a function of the 3D reconstruction software. In the following examples it is illustrated how OpenMP is applied to some functions of the software, where the background/foreground segmentation task is carried out. In the future, the parallelization of the other tasks will respect this schema. Next, a list of OpenMP directives used in the partial parallelization of the 3D reconstruction prototype is provided: • Disable dynamic threading. It means to force the number of threads within a team to be constant. A use example is: #ifdef _OPENMP omp_set_dynamic(0); #endif • Nested parallelism. It can be enable or disabled at any point by explicit calls to OpenMP. When enabled, all possible parallelism will be achieved at nested loops in the source code. Next a use example is shown: #ifdef _OPENMP omp_set_nested(1); // enable for (i=0; i<n; i++) { for (j=0; j<m; j++ { compute(a); } } #endif • Active threads. By setting the number of active threads OpenMP will create a set of execution threads that can be directly assigned to the available cores of the execution platform. Example: #ifdef _OPENMP omp_set_num_threads(n); #endif Finally, an example of the combined use of the previous directives in the first prototype is listed: • Silhouette segmentation. Source code example: void segment_silhouette(i3d_reconstruc_data_t* rd) { // set number of active threads for external loop done on images set_num_threads(num_threads_ext); // this instruction use OMP framework and each loop are done using several threads #pragma omp parallel for for (int ic = 0; ic < rd->num_cameras; ic++) { // reserve memory for silhouette image rd->silhouette_images[ic] = cvCreateImage(cvSize(rd->cameras[ic].calibration_info.width, rd->cameras[ic].calibration_info.height), IPL_DEPTH_8U, 1); // set number of active threads for internal segmentation computing // if nested parallelism is active, segmentation of one single image is done in parallel // if not, next instruction has no effect and segmentation is performed by 1 thread set_num_threads(num_threads_int); // compute silhouette get_silhouette_segmentation(rd->target_images[ic], rd->background_images[ic], &rd->config->segmentation_settings, rd->silhouette_images[ic]); }
Sample 1

Related to Detailed design of the

  • Schematic Design Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE

  • Final Design Phase A. After acceptance by Owner of the Preliminary Design Phase documents, revised opinion of probable Construction Cost as determined in the Preliminary Design Phase, and/or any other Right of Way plan documents, subject to any Owner-directed modifications or changes in the scope, extent, character, or design requirements of or for the Project, and upon written authorization from Owner, Engineer shall:

  • Design Development Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • Preliminary Design Phase During the Preliminary Design Phase, the CONSULTANT shall, if requested by the CITY and accepted by the CONSULTANT as part of a Services Authorization:

  • Design Phase All Basic Services set forth in the Agreement with the exception of Interdisciplinary Document Coordination Review, conducting a Card Trick session, Value-Engineering services, Estimating services. Bidding Phase • All Basic Services set forth in the Agreement. Construction Phase • All Basic Services set forth in the Agreement. Post-Construction • All Basic Services set forth in the Agreement.

  • Design Review Consumer shall provide Holy Cross an electrical one-line diagram and a relaying and metering one-line diagram prior to completion of detailed designs, unless the Consumer is installing a packaged system that is pre-certified to IEEE 1547.1 and UL 1741 standards. Packaged systems pre-certified under IEEE Standard 1547.1 and UL Standard 1741 will not require a relaying and metering one-line diagram. The submitted application and diagrams will be processed, reviewed, and acted upon in accordance with the Holy Cross Interconnection Policy.

  • Project Design Applicants must design a project that provides access to health services to enable eligible women and men experiencing health needs to secure and maintain safe and accessible quality screening and diagnostic services, comprehensive family planning, and/ or other women’s health services.

  • Design Development An interim step in the design process. Design Development documents consist of plans, elevations, and other drawings and outline specifications. These documents will fix and illustrate the size and character of the entire project in its essentials as to kinds of materials, type of structure, grade elevations, sidewalks, utilities, roads, parking areas, mechanical and electrical systems, and such other work as may be required.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

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