{"component": "clause", "props": {"groups": [{"size": 1, "snippet_links": [{"key": "the-system", "type": "definition", "offset": [22, 32]}, {"key": "section-31", "type": "definition", "offset": [71, 82]}, {"key": "figure-1", "type": "definition", "offset": [84, 92]}, {"key": "the-european-union", "type": "clause", "offset": [172, 190]}, {"key": "horizon-2020", "type": "definition", "offset": [193, 205]}, {"key": "research-and-innovation", "type": "clause", "offset": [206, 229]}, {"key": "agreement-no", "type": "definition", "offset": [252, 264]}], "snippet": "This section contains the system architecture, derived as described in Section 3.1. Figure 1 (next page) displays this architecture. This project has received funding from the European Union\u2019s Horizon 2020 research and innovation programme under grand agreement No 773715 This project has received funding from the European Union\u2019s Horizon 2020 research and innovation programme under grand agreement No 773715", "samples": [{"hash": "bV9S6r1Nunt", "uri": "/contracts/bV9S6r1Nunt#system-architecture", "label": "Grant Agreement", "score": 28.1482830048, "published": true}], "hash": "06c2af6b5df8e03b9760df449c564604", "id": 5}, {"size": 3, "snippet_links": [], "snippet": "It is recommended that there be a single PCB-Design containing all interfaces for connectors, LCD, switches and buttons.", "samples": [{"hash": "igVaRQC1eGd", "uri": "/contracts/igVaRQC1eGd#system-architecture", "label": "Supply Agreement (WorldSpace, Inc)", "score": 21.0, "published": true}, {"hash": "e7k3X2iViu6", "uri": "/contracts/e7k3X2iViu6#system-architecture", "label": "Standard Production, Marketing and License Agreement (WorldSpace, Inc)", "score": 21.0, "published": true}, {"hash": "aj9tNR3akFy", "uri": "/contracts/aj9tNR3akFy#system-architecture", "label": "Standard Production, Marketing and License Agreement (WorldSpace, Inc)", "score": 21.0, "published": true}], "hash": "fcaa762f091e08a995e0eca55a3531fd", "id": 1}, {"size": 3, "snippet_links": [{"key": "description-of-the", "type": "clause", "offset": [3, 21]}, {"key": "physical-system", "type": "definition", "offset": [22, 37]}, {"key": "system-management", "type": "clause", "offset": [67, 84]}], "snippet": "<A description of the physical system architecture, to include the system management. A diagram will be needed here>", "samples": [{"hash": "8e5Zl4jPcBE", "uri": "/contracts/8e5Zl4jPcBE#system-architecture", "label": "Contract for Services", "score": 33.8355789185, "published": true}, {"hash": "kEBXA8GNfx", "uri": "/contracts/kEBXA8GNfx#system-architecture", "label": "Contract for Services", "score": 33.8317642212, "published": true}, {"hash": "2jyUxMmrWho", "uri": "/contracts/2jyUxMmrWho#system-architecture", "label": "Services Agreement", "score": 25.5284061432, "published": true}], "hash": "f80ef3a8d0ccea74a626613c5b65fa49", "id": 2}, {"size": 3, "snippet_links": [{"key": "security-features", "type": "clause", "offset": [49, 66]}], "snippet": "We start with a description on the architecture, security features and thread model.", "samples": [{"hash": "aGC0zqyLuTZ", "uri": "/contracts/aGC0zqyLuTZ#system-architecture", "label": "Publication Agreement", "score": 29.4798202515, "published": true}, {"hash": "j2MXezywqyw", "uri": "/contracts/j2MXezywqyw#system-architecture", "label": "Copyright Notice", "score": 24.3990421295, "published": true}, {"hash": "1579kw85Ie0", "uri": "/contracts/1579kw85Ie0#system-architecture", "label": "Research Paper", "score": 22.3990421295, "published": true}], "hash": "35139358aa372437323b3329cb2efb7e", "id": 3}, {"size": 2, "snippet_links": [{"key": "available-at", "type": "definition", "offset": [74, 86]}, {"key": "personal-computer", "type": "definition", "offset": [137, 154]}, {"key": "designed-for", "type": "definition", "offset": [162, 174]}, {"key": "the-personal", "type": "clause", "offset": [277, 289]}, {"key": "system-development", "type": "clause", "offset": [313, 331]}, {"key": "laptop-computer", "type": "clause", "offset": [357, 372]}, {"key": "operating-system", "type": "definition", "offset": [510, 526]}, {"key": "storage-media", "type": "definition", "offset": [673, 686]}, {"key": "the-location", "type": "clause", "offset": [824, 836]}, {"key": "video-camera", "type": "definition", "offset": [942, 954]}, {"key": "data-sources", "type": "definition", "offset": [1009, 1021]}, {"key": "figure-6", "type": "definition", "offset": [1035, 1043]}, {"key": "data-link", "type": "definition", "offset": [1053, 1062]}, {"key": "software-component", "type": "definition", "offset": [1094, 1112]}, {"key": "programming-language", "type": "clause", "offset": [1171, 1191]}, {"key": "user-input", "type": "definition", "offset": [1244, 1254]}, {"key": "vehicle-detection", "type": "clause", "offset": [1297, 1314]}, {"key": "details-of", "type": "clause", "offset": [1459, 1469]}, {"key": "yes-no", "type": "clause", "offset": [1624, 1630]}, {"key": "yes-yes", "type": "clause", "offset": [1654, 1661]}, {"key": "the-vehicle", "type": "clause", "offset": [1687, 1698]}], "snippet": "The VVDC system comprises a WinTV-USB device (details for this device are available at \u2587\u2587\u2587\u2587://\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587/html/usb_data.htm) and a personal computer. It is designed for both online and offline operations on a regular personal computer running Windows 2000 or Windows XP. The personal computer used for VVDC system development was a Dell Latitude D600 laptop computer with a Pentium M 1.6 GHz Central Computing Unit, 1-GB memory, and a 32-MB ATI Radeon 9000 video card. It ran the Windows XP Professional operating system. The WinTV-USB device is used for digitizing live video signals. When the VVDC system is executed offline, it reads digitized video images from a storage media, and the WinTV-USB device is not necessary. For online operations, the VVDC system reads real-time images from the WinTV-USB device from the location where a live video signal source is connected. The live video source can be a video cassette player or a video camera. The components of the VVDC system and possible video data sources are shown in Figure 6-1. Video Data link Computer Video Data Source The software component of the VVDC system was written in the Microsoft Visual C# programming language. It has six modules: a live video capture module, a user input module, a background extraction module, a vehicle detection module, a shadow removal module, and a length-based classification module. The relationships among these modules are illustrated in Figure 6-2. Details of each module are described in the following sections. Background Extraction Queue Image media Nth Image \u2026 2nd Image Live video No Detection line occupied? Yes No Vehicle registered? No Yes Yes Count long vehicle Count the vehicle USB Port Extracted background Pixel-based length New Frame Get Bounding Box Shadow sample LV threshold Virtual detector Vide capture Edge Detection Compute Centroid Shadow Removal Find the median of color values for each pixel 1st Image USB Port Live video Vide capture No Detection line Yes No Yes Count the vehicle", "samples": [{"hash": "gWrsXZk3Tef", "uri": "/contracts/gWrsXZk3Tef#system-architecture", "label": "Research Report Agreement", "score": 19.0, "published": true}, {"hash": "ac1m0snuc3S", "uri": "/contracts/ac1m0snuc3S#system-architecture", "label": "Research Report Agreement", "score": 19.0, "published": true}], "hash": "0d0b5ff187e530f319d3436e2c3e0bc9", "id": 4}, {"size": 1, "snippet_links": [{"key": "ongoing-requirements", "type": "clause", "offset": [8, 28]}, {"key": "figure-1", "type": "definition", "offset": [239, 247]}, {"key": "terms-of", "type": "clause", "offset": [296, 304]}, {"key": "functional-areas", "type": "clause", "offset": [347, 363]}, {"key": "system-functionality", "type": "clause", "offset": [469, 489]}, {"key": "the-system", "type": "definition", "offset": [601, 611]}, {"key": "assets-to-be", "type": "clause", "offset": [656, 668]}, {"key": "the-project", "type": "definition", "offset": [677, 688]}, {"key": "most-important", "type": "clause", "offset": [784, 798]}, {"key": "wrap-up", "type": "clause", "offset": [846, 853]}, {"key": "to-develop", "type": "definition", "offset": [896, 906]}, {"key": "based-on", "type": "definition", "offset": [1021, 1029]}, {"key": "specific-functions", "type": "clause", "offset": [1108, 1126]}, {"key": "generic-services", "type": "definition", "offset": [1221, 1237]}], "snippet": "Turning ongoing requirements analyses into solid initial technical foundations, partners have invested a significant effort at sketching a system architecture for structuring subsequent design and developments. The following diagram, i.e. figure 1, thus illustrates the resulting architecture in terms of logical software layers and corresponding functional areas. It introduces the notion of horizontal versus orthogonal layers, where respectively horizontals provide system functionality, whereas orthogonals address non-functional aspects impacting on horizontals. Starting from the very bottom of the system, i.e. \u201cBackends Middleware\u201d, with IT legacy assets to be used in the project such as grid and database infrastructures, various abstraction levels are then introduced. The most important one, so-called \u201cBackends Abstraction\u201d, aims to wrap up underlying backends and to allow partners to develop grid/ database agnostic software while still interacting with given technologies and corresponding specificities. Based on this abstraction, further layers are superimposed which deliver more and more specific functions as distance to end-users shrinks. As such, \u201cDomain Logic\u201d aims at grouping so-called \u201cmedical generic services\u201d \u2013", "samples": [{"hash": "1RGutTFXBfC", "uri": "/contracts/1RGutTFXBfC#system-architecture", "label": "Grant Agreement", "score": 21.0, "published": true}], "hash": "38dcbdf8edc32fa506e0e8bc902074fd", "id": 6}, {"size": 1, "snippet_links": [{"key": "provide-the", "type": "clause", "offset": [25, 36]}, {"key": "the-end-user", "type": "clause", "offset": [69, 81]}, {"key": "the-information", "type": "clause", "offset": [95, 110]}, {"key": "process-user", "type": "definition", "offset": [138, 150]}, {"key": "private-key", "type": "definition", "offset": [217, 228]}, {"key": "individual-user", "type": "definition", "offset": [233, 248]}], "snippet": "The architecture aims to provide the high bandwidth and low delay to the end user. It managing the information between admin and user. It process user request (uploading file, downloading file). Admin generate unique private key for individual user.", "samples": [{"hash": "5UscV6z40CJ", "uri": "/contracts/5UscV6z40CJ#system-architecture", "label": "Private Key Agreement for Group Data Sharing", "score": 27.3188610077, "published": true}], "hash": "46cde86c031f49a1b365fde45b89b8bc", "id": 7}, {"size": 1, "snippet_links": [{"key": "the-strategic", "type": "clause", "offset": [67, 80]}, {"key": "use-of-technology", "type": "clause", "offset": [81, 98]}, {"key": "access-to-the", "type": "clause", "offset": [128, 141]}, {"key": "its-data", "type": "definition", "offset": [149, 157]}, {"key": "new-technology", "type": "definition", "offset": [181, 195]}, {"key": "by-the-contractor", "type": "clause", "offset": [205, 222]}, {"key": "standards-and-policies", "type": "definition", "offset": [286, 308]}, {"key": "existing-technology", "type": "clause", "offset": [335, 354]}, {"key": "platforms-and-systems", "type": "clause", "offset": [355, 376]}, {"key": "characterized-by", "type": "definition", "offset": [419, 435]}, {"key": "business-application", "type": "definition", "offset": [454, 474]}, {"key": "sql-server", "type": "definition", "offset": [498, 508]}, {"key": "application-server", "type": "clause", "offset": [522, 540]}, {"key": "windows-server", "type": "definition", "offset": [610, 624]}], "snippet": "CHA utilizes a standardized technology environment that emphasizes the strategic use of technology and provides for appropriate access to the use of its data. CHA requires that any new technology proposed by the Contractor meets compatibility with existing environments, adheres to CHA standards and policies, and maximizes the use of existing technology platforms and systems. CHA\u2019s existing technology environment is characterized by the following:\na. Business Application Standards\ni. Database: SQL Server 2016\nii. Web Application Server: IIS 7.5, SharePoint 2016, SharePoint Online\niii. Operation Systems: Windows Server 2016, Windows Server 2019, VMWare 7.0", "samples": [{"hash": "hCdCQcZ6a2L", "uri": "/contracts/hCdCQcZ6a2L#system-architecture", "label": "Agreement for the Administration and Operation of the Chicago Housing Authority\u2019s Section 8 Programs", "score": 26.0581798553, "published": true}], "hash": "17a67af1f9d883da07d5692e172ce824", "id": 8}, {"size": 1, "snippet_links": [{"key": "external-interference", "type": "clause", "offset": [92, 113]}, {"key": "audit-trails", "type": "clause", "offset": [194, 206]}], "snippet": "Create and maintain a domain for execution to protect the Trusted Computing Base (TCB) from external interference or tampering, so that the TCB may protect its resources via access controls and audit trails.", "samples": [{"hash": "lQudYz4AS2Z", "uri": "/contracts/lQudYz4AS2Z#system-architecture", "label": "Subcontract (Xcarenet Inc)", "score": 18.0, "published": true}], "hash": "57ce6970f59b0c25525c5cb8a3f25fb9", "id": 9}, {"size": 1, "snippet_links": [{"key": "user-verification", "type": "clause", "offset": [22, 39]}, {"key": "access-control", "type": "definition", "offset": [83, 97]}, {"key": "data-sharing", "type": "clause", "offset": [128, 140]}, {"key": "cloud-storage", "type": "definition", "offset": [144, 157]}], "snippet": "MODULES:\n1. Authority User Verification\n2. Privacy-preserving\n3. Key distribution &Access control\n4. Collusion attack\n5. Secure data sharing\n6. Cloud storage", "samples": [{"hash": "5UscV6z40CJ", "uri": "/contracts/5UscV6z40CJ#system-architecture", "label": "Private Key Agreement for Group Data Sharing", "score": 27.3188610077, "published": true}], "hash": "3a81f22b97a4662b4c8c336b064adee6", "id": 10}], "next_curs": "ClwSVmoVc35sYXdpbnNpZGVyY29udHJhY3RzcjgLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhxzeXN0ZW0tYXJjaGl0ZWN0dXJlIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"children": [["", ""], ["system-architecture", "System Architecture"], ["distributed-system-architecture-study", "Distributed system architecture study"], ["subito-demonstration-architecture", "SUBITO Demonstration Architecture"], ["integration-with-existing-services", "Integration with existing services"]], "size": 66, "parents": [["system-architecture", "System Architecture"], ["physical-requirements", "Physical Requirements"], ["general-provisions", "General Provisions"], ["miscellaneous", "Miscellaneous"], ["length-based-classification", "LENGTH-BASED CLASSIFICATION"]], "title": "System Architecture", "id": "system-architecture", "related": [["architecture", "Architecture", "Architecture"], ["network-interconnection-architecture", "Network Interconnection Architecture", "Network Interconnection Architecture"], ["system-logging", "System Logging", "System Logging"], ["configuration-management", "Configuration Management", "Configuration Management"], ["design", "Design", "Design"]], "related_snippets": [], "updated": "2026-05-16T05:47:53+00:00"}, "json": true, "cursor": ""}}