{"component": "clause", "props": {"groups": [{"size": 3, "snippet_links": [{"key": "during-the-term", "type": "clause", "offset": [17, 32]}, {"key": "improvements-and-modifications", "type": "clause", "offset": [77, 107]}, {"key": "reference-design", "type": "definition", "offset": [146, 162]}, {"key": "conditions-for-the", "type": "clause", "offset": [174, 192]}, {"key": "the-parties", "type": "definition", "offset": [243, 254]}, {"key": "obligations-to-third-parties", "type": "clause", "offset": [283, 311]}, {"key": "if-either-party", "type": "clause", "offset": [317, 332]}, {"key": "to-disclose", "type": "definition", "offset": [341, 352]}, {"key": "customer-details", "type": "clause", "offset": [358, 374]}, {"key": "with-respect-to", "type": "clause", "offset": [375, 390]}, {"key": "such-party", "type": "clause", "offset": [391, 401]}, {"key": "development-of-a", "type": "clause", "offset": [409, 425]}, {"key": "to-be-added", "type": "clause", "offset": [436, 447]}, {"key": "change-to", "type": "definition", "offset": [502, 511]}, {"key": "other-party", "type": "definition", "offset": [635, 646]}, {"key": "in-writing", "type": "clause", "offset": [647, 657]}, {"key": "the-customer", "type": "definition", "offset": [705, 717]}, {"key": "the-foregoing", "type": "definition", "offset": [743, 756]}, {"key": "obligations-shall", "type": "definition", "offset": [757, 774]}, {"key": "material-impact", "type": "definition", "offset": [828, 843]}, {"key": "component-products", "type": "clause", "offset": [865, 883]}, {"key": "material-discrepancy", "type": "definition", "offset": [1033, 1053]}, {"key": "published-specifications", "type": "definition", "offset": [1066, 1090]}, {"key": "actual-performance", "type": "definition", "offset": [1121, 1139]}, {"key": "in-connection-with", "type": "clause", "offset": [1166, 1184]}, {"key": "the-interface", "type": "clause", "offset": [1252, 1265]}, {"key": "operation-of-the", "type": "clause", "offset": [1327, 1343]}, {"key": "nature-of-this", "type": "clause", "offset": [1404, 1418]}], "snippet": "(a) Each quarter during the Term, Wintegra and TI will discuss all subsystem improvements and modifications intended for the MP DSLAM Cooperative Reference Design and market conditions for the MP DSLAM Cooperative Reference Design, subject to the Parties\u2019 respective confidentiality obligations to third parties.\n(b) If either Party intends to disclose to a customer details with respect to such Party\u2019s: (i) development of a component to be added to the MP DSLAM Cooperative Reference Design, or (ii) change to any component already included in the MP DSLAM Cooperative Reference Design; such Party shall disclose such details to the other Party in writing at least as soon as disclosing such details to the customer; provided, however, that the foregoing obligations shall not apply with respect to changes that do not have a material impact on the other Party\u2019s Component Products (as implemented in the MP DSLAM Cooperative Reference Design) or the MP DSLAM Cooperative Reference Design as a whole.\n(c) If Wintegra discovers any material discrepancy between the published specifications for its Component Product and actual performance of such Component Product in connection with the MP DSLAM Cooperative Reference Design, such that it may affect the interface between the TI Components and the Wintegra Components or the operation of the Wintegra Components, it will immediately alert TI as to the nature of this discrepancy and what steps, if any, will be taken to correct such discrepancy. If TI discovers any material discrepancy between the published specifications for its Component Product and actual performance of such Components Products such that if may affect the interface between the TI Components and the Wintegra Components or the operation of the Wintegra Components, TI will immediately alert Wintegra as to the nature of this discrepancy and what steps, if any, will be taken to correct such discrepancy.", "samples": [{"hash": "bZVb0eexPcq", "uri": "/contracts/bZVb0eexPcq#design-updates", "label": "DSL Multi Protocol Dslam Agreement (Wintegra Inc)", "score": 21.0, "published": true}, {"hash": "9w9mQhzEf8h", "uri": "/contracts/9w9mQhzEf8h#design-updates", "label": "DSL Multi Protocol Dslam Agreement (Wintegra Inc)", "score": 21.0, "published": true}, {"hash": "9gkntClkyUd", "uri": "/contracts/9gkntClkyUd#design-updates", "label": "DSL Multi Protocol Dslam Agreement (Wintegra Inc)", "score": 21.0, "published": true}], "hash": "827816cf11fa0377b5079361216c3d9a", "id": 1}, {"size": 2, "snippet_links": [{"key": "seller-will", "type": "clause", "offset": [0, 11]}, {"key": "right-to-change", "type": "clause", "offset": [21, 36]}, {"key": "of-seller", "type": "clause", "offset": [103, 112]}, {"key": "general-function", "type": "clause", "offset": [145, 161]}, {"key": "the-products", "type": "clause", "offset": [165, 177]}], "snippet": "Seller will have the right to change the manufacture and/or design of its Products if, in the judgment of Seller, such change does not alter the general function of the Products.", "samples": [{"hash": "b2xCFbrOBhf", "uri": "/contracts/b2xCFbrOBhf#design-updates", "label": "Distributor Agreement (Stereotaxis, Inc.)", "score": 16.0, "published": true}, {"hash": "9qOdNCoulb0", "uri": "/contracts/9qOdNCoulb0#design-updates", "label": "Distributor Agreement (Stereotaxis, Inc.)", "score": 16.0, "published": true}], "hash": "eb381fcd695bccacdb65d99d9f84acb7", "id": 2}, {"size": 1, "snippet_links": [{"key": "design-change", "type": "definition", "offset": [32, 45]}, {"key": "related-to", "type": "clause", "offset": [49, 59]}, {"key": "secure-connection", "type": "definition", "offset": [186, 203]}, {"key": "the-network", "type": "clause", "offset": [293, 304]}, {"key": "network-entity", "type": "definition", "offset": [464, 478]}, {"key": "number-of", "type": "clause", "offset": [546, 555]}, {"key": "according-to", "type": "definition", "offset": [642, 654]}, {"key": "add-new", "type": "definition", "offset": [700, 707]}, {"key": "table-2", "type": "clause", "offset": [724, 731]}, {"key": "to-generate", "type": "definition", "offset": [753, 764]}, {"key": "the-connection", "type": "clause", "offset": [765, 779]}, {"key": "functions-of-the", "type": "clause", "offset": [863, 879]}, {"key": "strong-authentication", "type": "definition", "offset": [952, 973]}, {"key": "new-client", "type": "definition", "offset": [1131, 1141]}, {"key": "the-client", "type": "definition", "offset": [1179, 1189]}, {"key": "public-key", "type": "definition", "offset": [1214, 1224]}, {"key": "type-description", "type": "clause", "offset": [1243, 1259]}, {"key": "to-be-added", "type": "clause", "offset": [1310, 1321]}, {"key": "assigned-ip", "type": "definition", "offset": [1399, 1410]}], "snippet": "From Deliverable D4.1, the main design change is related to the deployment in the module. Previously, each client of a domain had to be configured as a client of the domain to which the secure connection was to be generated. Now, the inter-domain security module is designed to be deployed in the network gateways of each domain, so that they act as an intermediary between the end entities and the external domain. This reduces the complexity of configuring each network entity acting as a VPN client to the external domain. It also reduces the number of credentials required for the authentication and secure connection generation process. According to this design change, it has been necessary to add new interfaces (see Table 2-5) that are required to generate the connection between gateways. In this way, the connection can be generated directly by calling functions of the gateway acting as a client. In this sense, these interfaces should have strong authentication requirements, allowing only to trigger its functionality to trusted entities from external domains. These new interfaces are: Description This method adds a new client to the gateway acting as VPN server. The client is identified using its public key. Input Parameters Type Description client_public_key String Public key of the client to be added, in Curve25519 format. Output Parameters Type Description assigned_ip String Assigned IP to the new client. vpn_port Integer Port where the vpn server is running. server_public_key String Public key of the vpn server. Description This method adds a new client to the gateway acting as VPN server. The client is identified using its public key. Input Parameters Type Description ip_address_server String Public key of the client to be removed, in Curve25519 format. Output Parameters Type Description result Integer It indicates if the client public key has been removed successfully or not.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "2be958e6568549667fcb0d6a46ddf456", "id": 3}, {"size": 1, "snippet_links": [{"key": "provide-the", "type": "clause", "offset": [73, 84]}, {"key": "high-level", "type": "definition", "offset": [85, 95]}, {"key": "the-fact", "type": "clause", "offset": [271, 279]}, {"key": "the-final", "type": "clause", "offset": [337, 346]}, {"key": "implementation-phases", "type": "clause", "offset": [426, 447]}, {"key": "final-version", "type": "clause", "offset": [459, 472]}, {"key": "software-design", "type": "clause", "offset": [579, 594]}, {"key": "ready-to", "type": "clause", "offset": [627, 635]}, {"key": "figure-4", "type": "definition", "offset": [657, 665]}, {"key": "other-components", "type": "clause", "offset": [744, 760]}, {"key": "resource-manager", "type": "definition", "offset": [790, 806]}, {"key": "service-offer", "type": "definition", "offset": [887, 900]}, {"key": "the-target", "type": "clause", "offset": [928, 938]}, {"key": "network-controller", "type": "definition", "offset": [1179, 1197]}, {"key": "the-e", "type": "clause", "offset": [1230, 1235]}, {"key": "where-required", "type": "clause", "offset": [1455, 1469]}, {"key": "the-interface", "type": "clause", "offset": [1600, 1613]}, {"key": "the-provider", "type": "clause", "offset": [1769, 1781]}, {"key": "in-terms", "type": "clause", "offset": [1867, 1875]}, {"key": "when-required", "type": "definition", "offset": [1896, 1909]}, {"key": "references-to", "type": "definition", "offset": [1923, 1936]}, {"key": "a-reference-to", "type": "clause", "offset": [2007, 2021]}, {"key": "access-to-the", "type": "clause", "offset": [2173, 2186]}, {"key": "resource-information", "type": "clause", "offset": [2187, 2207]}, {"key": "the-connection", "type": "clause", "offset": [2209, 2223]}, {"key": "to-receive", "type": "definition", "offset": [2737, 2747]}, {"key": "the-current", "type": "clause", "offset": [2954, 2965]}, {"key": "depending-on-the", "type": "clause", "offset": [3025, 3041]}, {"key": "a-\u2587", "type": "clause", "offset": [3118, 3121]}], "snippet": "The VRM is designed to be a multi-container application, with the aim to provide the high level of flexibility required to immediately tackle any changes/updates in both resource composition and in the underlying 5G virtualised infrastructure. Due to this and in part to the fact that some features are still under definition or design, the final composition of such set of containers may vary during the following design and implementation phases, up to the final version of the prototype.\n1. In this section we describe the updates to such set of features and also the initial software design of the components that were not ready to be reported in D4.1. Figure 4-1 shows to two main elements building the VRM and their relationship with the other components of the 5GZORRO platform. The Resource Manager contains the logic to manage the resource DB and interact with the Resource and Service Offer Catalogue (RSOC), which is the target of the resource definition translation process. The Resource Manager also offers an interface the MDA exploits for retrieving information used to reach the different components of the 5G Virtualisation platform, namely NFVO, VIM, Radio and Network Controller. Same interface is exploited by the e-Licensing modules to retrieve the coordinates to access the NFVO. Focusing into the Resource Manager module, it consists of several modules in charge to implement the functionality of resource storage (descriptors and, where required, packages), model translation, and 5G virtualisation infrastructure DB, as depicted in Figure 4-2. The Infrastructure GW provides the interface and the logic to access the underlying 5G Virtualised infrastructure, avoiding the need for components like MDA and e-Licensing modules to directly access the provider internal infrastructure. The Resource DB contains the resource definitions expressed in terms of descriptors and, when required, in terms of references to certain resource packages (e.g., the DB contains a VNF descriptor and a reference to the corresponding VNF package). The resource DB is managed by the Resource Manager Catalogue Handler (RMCH) that offers the interface and the logic to access to the resource information. The connection between the RM Catalogue Handler and the 5G Virtualised Infrastructure represents the capability of the Resource Manager to access the internal catalogues of the different elements to add (onboard), update, and remove resources. Finally, the Resource Definition Translator provides the logic to translate the resources, as defined in the Resource DB, to the proper models defined by the TM Forum as well as the required interface to store such translations to the RSOC. As depicted in Figure 4-3, the MDA intends to receive from NSSO a monitoring spec with the needed information/identifiers and therefore starting the monitoring stage within the timeline defined. MDA collects metric values from the virtualization platform (for the current time, it collects from NFVO OSM), aggregates them (or not, depending on the measurement type), and forwards the encrypted hash of the monitored data to a \u2587\u2587\u2587\u2587\u2587 topic.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "f86bb72bd1189096f463e589b8561e29", "id": 4}, {"size": 1, "snippet_links": [{"key": "development-period", "type": "clause", "offset": [29, 47]}, {"key": "internal-communications", "type": "clause", "offset": [119, 142]}, {"key": "the-e", "type": "clause", "offset": [175, 180]}, {"key": "licensing-manager", "type": "definition", "offset": [181, 198]}, {"key": "license-manager", "type": "definition", "offset": [344, 359]}, {"key": "point-of-presence", "type": "definition", "offset": [384, 401]}, {"key": "the-objective", "type": "clause", "offset": [435, 448]}, {"key": "and-evaluation", "type": "clause", "offset": [601, 615]}, {"key": "external-entities", "type": "definition", "offset": [711, 728]}], "snippet": "The main updates during this development period are mainly due implementation decisions, that have been focused in the internal communications between the centralized part of the e-Licensing Manager and their distributed components. Thus, the e-Licensing Manager consists of a microservice-based application offered in two main subsystems: \u2022 e-License Manager Core (eLMC) as a single point of presence inside the 5GZORRO Platform with the objective of centralizing TX and RX communications with the NSSO, the Marketplace, VNF Vendors and Operators. In D4.1 it was introduced as the eLicensing Context and Evaluation Manager, and now has evolved to the eLMC to centralize all the mentioned communications to the external entities, and brokering the requests to the different eLMAs, acting as the brain of the eLicensing Manager.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "ce43a980c16177a83b074a005499b762", "id": 5}, {"size": 1, "snippet_links": [{"key": "with-respect-to", "type": "clause", "offset": [30, 45]}, {"key": "the-deliverable", "type": "definition", "offset": [46, 61]}, {"key": "main-focus", "type": "definition", "offset": [82, 92]}], "snippet": "No design update has occurred with respect to the deliverable D4.\n1. In fact, the main focus of the prototype for this intermediate 5GZORRO release has been on testing the SCONE framework capabilities.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "e1723458c7e5edcaf7f3bdd875541ee4", "id": 6}, {"size": 1, "snippet_links": [{"key": "design-and-implementation", "type": "clause", "offset": [4, 29]}, {"key": "figure-4", "type": "definition", "offset": [175, 183]}, {"key": "in-particular", "type": "clause", "offset": [187, 200]}, {"key": "the-interface", "type": "clause", "offset": [202, 215]}, {"key": "exposed-to", "type": "definition", "offset": [216, 226]}, {"key": "based-on", "type": "clause", "offset": [253, 261]}, {"key": "software-components", "type": "definition", "offset": [303, 322]}, {"key": "related-to", "type": "clause", "offset": [356, 366]}, {"key": "resource-allocations", "type": "clause", "offset": [434, 454]}, {"key": "smart-contracts", "type": "clause", "offset": [485, 500]}, {"key": "associated-with", "type": "definition", "offset": [501, 516]}, {"key": "the-offer", "type": "clause", "offset": [517, 526]}, {"key": "data-aggregation", "type": "clause", "offset": [574, 590]}, {"key": "the-e", "type": "clause", "offset": [601, 606]}, {"key": "licensing-manager", "type": "definition", "offset": [607, 624]}, {"key": "network-service", "type": "definition", "offset": [727, 742]}], "snippet": "The design and implementation of the NSSO has been evolved with a more mature definition and implementation of the interfaces between the different components, illustrated in Figure 4-5. In particular, the interface exposed to the ISSM has been defined based on the initial interface available from the software components and updated to allow passing IDs related to the 5G Offer transaction, which are passed to other modules to map resource allocations, and service instances to the smart contracts associated with the offer. The initial interfaces towards the Monitoring Data Aggregation (MDA) and the e-Licensing Manager modules have been established. Work is still ongoing to define the interface between the NSSO and the Network Service Mesh Manager (NSMM), to provision the connectivity between the different components of the end- to-end service, and between NSSOs in other domains to provision slices on top of 3rd party resources.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "0292912081ed6da29caf9e9a3ce89af2", "id": 7}, {"size": 1, "snippet_links": [{"key": "changes-in", "type": "clause", "offset": [25, 35]}], "snippet": "There are no significant changes in the ISSM-WFM design since deliverable D4.\n1. In deliverable D2.3 [18], updated orchestration workflows have been presented which better capture the intended behaviours in scenarios such as cross-domain slice establishment, scale-out and optimization. Moreover, always in D2.3 updates have been provided about how ISSM-WFM integrates with the rest of the functional 5GZORRO architecture.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "ec8aee776bdba3cdd2bfebaddc299736", "id": 8}, {"size": 1, "snippet_links": [{"key": "software-modules", "type": "definition", "offset": [45, 61]}, {"key": "previous-version", "type": "definition", "offset": [79, 95]}, {"key": "the-deliverable", "type": "definition", "offset": [99, 114]}], "snippet": "Currently there are no design updates as the software modules described in the previous version of the deliverable seem to work well. Well-defined and standardized software platforms are currently deployed and in use.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "32b5330af8367862370f924e4584677e", "id": 9}, {"size": 1, "snippet_links": [{"key": "related-to", "type": "clause", "offset": [21, 31]}, {"key": "management-framework", "type": "clause", "offset": [61, 81]}, {"key": "release-of", "type": "clause", "offset": [147, 157]}, {"key": "figure-2", "type": "clause", "offset": [407, 415]}, {"key": "application-module", "type": "definition", "offset": [467, 485]}, {"key": "initial-list", "type": "definition", "offset": [557, 569]}, {"key": "the-consumer", "type": "definition", "offset": [715, 727]}, {"key": "the-framework", "type": "clause", "offset": [807, 820]}, {"key": "collection-process", "type": "clause", "offset": [841, 859]}, {"key": "associated-with", "type": "definition", "offset": [881, 896]}, {"key": "key-pair", "type": "definition", "offset": [1073, 1081]}, {"key": "platform-participant", "type": "definition", "offset": [1163, 1183]}, {"key": "public-key", "type": "definition", "offset": [1220, 1230]}, {"key": "trust-data", "type": "definition", "offset": [1274, 1284]}, {"key": "to-provide", "type": "definition", "offset": [1497, 1507]}, {"key": "other-participants", "type": "clause", "offset": [1582, 1600]}, {"key": "specific-service", "type": "definition", "offset": [1646, 1662]}, {"key": "created-by", "type": "definition", "offset": [1727, 1737]}, {"key": "new-data", "type": "definition", "offset": [2092, 2100]}, {"key": "trust-information", "type": "clause", "offset": [2134, 2151]}, {"key": "step-5", "type": "clause", "offset": [2259, 2265]}, {"key": "to-the-trust", "type": "definition", "offset": [2407, 2419]}, {"key": "service-provider", "type": "definition", "offset": [2584, 2600]}, {"key": "information-from", "type": "clause", "offset": [2651, 2667]}, {"key": "to-establish", "type": "clause", "offset": [3003, 3015]}, {"key": "information-collected", "type": "clause", "offset": [3291, 3312]}, {"key": "given-that", "type": "clause", "offset": [3432, 3442]}, {"key": "the-final", "type": "clause", "offset": [3513, 3522]}, {"key": "product-offer", "type": "definition", "offset": [3657, 3670]}, {"key": "after-receiving", "type": "clause", "offset": [3706, 3721]}, {"key": "based-on", "type": "clause", "offset": [3860, 3868]}, {"key": "a-list", "type": "definition", "offset": [3935, 3941]}, {"key": "service-manager", "type": "clause", "offset": [3994, 4009]}, {"key": "available-at", "type": "definition", "offset": [4120, 4132]}, {"key": "notify-the", "type": "clause", "offset": [4218, 4228]}, {"key": "final-list", "type": "definition", "offset": [4229, 4239]}, {"key": "product-ordering", "type": "clause", "offset": [4258, 4274]}, {"key": "workflow-manager", "type": "clause", "offset": [4287, 4303]}, {"key": "the-network", "type": "clause", "offset": [4410, 4421]}, {"key": "final-decision", "type": "definition", "offset": [4580, 4594]}, {"key": "final-step", "type": "clause", "offset": [4635, 4645]}, {"key": "the-selected", "type": "clause", "offset": [4723, 4735]}, {"key": "in-the-case", "type": "clause", "offset": [4826, 4837]}, {"key": "defined-events", "type": "clause", "offset": [4846, 4860]}, {"key": "responsible-for", "type": "clause", "offset": [5087, 5102]}, {"key": "stopping-the", "type": "clause", "offset": [5116, 5128]}, {"key": "in-table-2", "type": "clause", "offset": [5520, 5530]}, {"key": "collection-data", "type": "definition", "offset": [5605, 5620]}, {"key": "management-service", "type": "definition", "offset": [5658, 5676]}, {"key": "type-description", "type": "clause", "offset": [5726, 5742]}, {"key": "the-process", "type": "clause", "offset": [5805, 5816]}, {"key": "an-event", "type": "clause", "offset": [6001, 6009]}, {"key": "collection-cycle", "type": "definition", "offset": [6175, 6191]}, {"key": "detailed-information", "type": "definition", "offset": [6215, 6235]}, {"key": "section-51", "type": "clause", "offset": [6273, 6284]}, {"key": "information-model", "type": "clause", "offset": [6332, 6349]}, {"key": "employed-by", "type": "definition", "offset": [6877, 6888]}, {"key": "the-method", "type": "definition", "offset": [7468, 7478]}, {"key": "the-operation", "type": "clause", "offset": [7871, 7884]}, {"key": "in-particular", "type": "clause", "offset": [7928, 7941]}, {"key": "updated-information", "type": "clause", "offset": [7947, 7966]}, {"key": "new-trust", "type": "definition", "offset": [7986, 7995]}, {"key": "services-and", "type": "clause", "offset": [8045, 8057]}, {"key": "more-specifically", "type": "clause", "offset": [8103, 8120]}], "snippet": "Novel considerations related to the integration of the Trust Management Framework with other 5GZORRO components (workflows) have emerged since the release of the related design in deliverable D4.1 (Jan. 2021). Therefore, a new internal workflow has been designed to better describe the interaction of the Trust Management Framework with other key modules and the triggered actions. As it can be observed in Figure 2-1, the Smart Resource and Service Discovery (SRSD) application module is the one in charge of launching the trust computation process for an initial list of offers pre-classified by the SRSD employing mechanisms such as intent-based priorities, imperative constraints and considerations provided by the consumer. Once the Trust Management Framework receives a set of offers to be evaluated, the framework will start the data collection process for each stakeholder associated with it. Hence, the following steps will be carried as many times as offers need to be assessed. The Trust Management Framework in each domain should possess a previously generated key pair (intra- domain keys), as well as a Decentralised Identifiers (DID). Each 5GZORRO Platform Participant of a particular domain must use the public key of its Trust Management Framework to share trust data into the Data Lake. Additionally, the Trust Management Framework should possess another global key pair (inter-domain keys) that could be used by other 5GZORRO Platform Participants (from other domains) in order to provide domain recommendations. These recommendations may subsequently be used by other participants who do not have previous information about a specific service or resource. Both key pairs (intra- and inter-domain) should be created by the Identity and Permission Manager before the 5GZORRO Platform Participant interacts with the Trust Management Framework. The impact of these changes is reflected in the workflow described in Figure 2-1. The Trust Management Framework will launch the startDataCollection method (see sec. 2.1 of deliverable\n4.1 for details). Such capability will create new Data Lake pipeline that will retrieve trust information for each 5GZORRO Platform Participant using the two templates defined in sec. 5.1 of deliverable 4.1 (ref. step 5 in Figure 2-1). As an outcome of this step, the Data Lake platform will generate a new input and output \u2587\u2587\u2587\u2587\u2587 topics which will be forwarded to the Trust Management Framework. It should be outlined that Data Lake ought to gather information not only from the specific resource or service but also from its resource or service provider. In the same way, the Data Lake ought to retrieve information from the 5GZORRO Platform Participant who triggered a business flow but also recommendations from other participants. Hence, we may acquire trust information from up to 4 levels: a particular resource or service history, a particular resource or service recommendation(s), 5GZORRO Platform Participant history (an entity with which we want to establish a relationship of trust), and 5GZORRO Platform Participant recommendation(s). Subsequently, the Trust Management Framework will be subscribed through its getInformation method as a consumer of the previous output \u2587\u2587\u2587\u2587\u2587 topic provided by the Data Lake and will obtain all the information collected in the templates. This information will be utilised to perform a final trust score that will be forwarded to the SRSD. Given that we are assessing the confidence scores of a set of product offers but the final selected offer is not known at this stage, the Trust Management Framework will disable the continuous data collection process of each product offer via the stopDataCollection method. After receiving all trust assessments from the list of offers, the Smart Resource and Service Discovery application will generate a ranked list of offers based on certain intent priorities as well as the trust scores. Then, such a list of offers will be sent to the Intelligent Slice and Service Manager. After that, the ISSM Optimizer (ISSM-O) will determine a cost-efficient allocation of resources and services available at the marketplace to implement the required slice or service. Hence, the ISSM-O should notify the final list of highest ranked product ordering to the ISSM Workflow Manager (ISSM-WFM). At this point, the ISSM-WFM will carry out multiple tasks, with the aid of other modules like the Network Slice and Service Orchestrator (NSSO), in order to configure and instantiate a slice. Once the slice is instantiated and active, the ISSM-WFM will notify the final decision to the Trust Management Framework. As a final step, the Trust Management Framework will launch a continuous data collection for the selected slice or service in order to start the entire trust lifecycle and update the trust score, in the case of some defined events or triggers are activated. Due to the changed workflow presented above, it has been necessary to adapt and define new interfaces for the Trust Management Framework service: \u2022 the previous startDataCollection method, which was responsible for starting and stopping the data collection, has been split into two methods the startDataCollection and stopDataCollection (see Table 2-1). \u2022 two new interfaces (requestTrustScores and notifyFinalSelection) have been created in order to enable the interaction of the Smart Resource and Service Discovery application and the ISSM-WFM with the Trust Management Framework. Details on these interface updates are reported in Table 2-1 below. Description This method is responsible for starting a continuous collection data (e.g., Monitoring Analytic, Security Management Service, etc.) from Data Lake platform. Input Parameters Type Description stakeholder_did String Stakeholder\u2019s DID on which it launches the process of continuous information recollection. trust_parameters Dictionary Empty template with the data to be collected in the Data Lake. specific_events* Boolean Set of triggers that enable an event drive pre-processing to take place directly in the Data Lake. Output Parameters Type Description data_collection_status Boolean It returns true or false if the data collection cycle is active or not. More detailed information about the dictionary can be found in Section 5.1 of Deliverable 4.1 (trust management framework information model). Specific_events* is an optional parameter. Description This method is responsible for stopping a continuous collection data (e.g., Monitoring Analytic, Security Management Service, etc.) from Data Lake platform. Input Parameters Type Description stakeholder_did String Stakeholder\u2019s DID on which it disables the process of continuous information recollection. Output Parameters Type Description data_collection_status Boolean It returns true or false if the data collection cycle is active or not. Description This method is employed by the Smart Service and Resource Discovery application in order to evaluate trust scores of a list of pre-classified offers. Input Parameters Type Description list_offers List of Product offers Set of offers matching stakeholder\u2019s criteria such as intent-based priorities. Output Parameters Type Description list_trust_scores List of double It returns the trust score computed for each offer. Operation name: notifyFinalSelection Description This method is employed by the ISSM-WFM to notify the Trust Management Framework the final resource or service/slice selected and on which the method will be launched internally. Input Parameters Type Description id_participant DID Distributed identifier of the 5GZORRO participant who request a slice or resource. id_candidate DID Distributed identifier of the final stakeholder candidate. id_offer DID Distributed identifier of the final selected resource or service/slice. Output Parameters Type Description result Boolean It indicates if the operation has been completed successfully or not.\n1. In particular, the updated information model contemplates new trust parameters in order to assess the trust score of services and resource providers and their product offers. More specifically, to correctly manage the new trust parameters defined in the Trust Management Framework Information Model, multiple equations have been defined which are used to compute the 5GZORRO stakeholder trust score (see Trust Management Framework Information Model). In particular, the Trust Management Framework leverages the well-known reputation model called PeerTrust [1] which is envisaged as a basis from which to design equations in line with the 5GZORRO ecosystem. Thus, these equations will be employed by one of the modules that make up the architecture of the TMF presented in deliverable D4.1, the Trust Assessment module. In this regard, all trust parameters as well as equations contemplated for calculating trust scores can be found in Appendix I.", "samples": [{"hash": "hNbF8VCjk9d", "uri": "/contracts/hNbF8VCjk9d#design-updates", "label": "Grant Agreement", "score": 30.4120854416, "published": true}], "hash": "d4dcc5e45f7378cd8ad3550c4c4a95a9", "id": 10}], "next_curs": "ClcSUWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjMLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhdkZXNpZ24tdXBkYXRlcyMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"title": "Design Updates", "size": 6, "parents": [["compliance-with-regulations", "Compliance With Regulations"], ["risk-of-loss-title", "Risk of Loss, Title"], ["security-and-trust-orchestration", "Security and Trust Orchestration"], ["trusted-execution-environment-security-management", "Trusted Execution Environment Security Management"], ["intra-domain-security-enablers", "Intra-domain Security enablers"]], "children": [], "id": "design-updates", "related": [["software-updates", "Software Updates", "Software Updates"], ["updates", "Updates", "Updates"], ["design-changes", "Design Changes", "Design Changes"], ["design-phase", "Design Phase", "Design Phase"], ["technology-upgrades", "Technology Upgrades", "Technology Upgrades"]], "related_snippets": [], "updated": "2025-07-07T12:36:18+00:00", "also_ask": [], "drafting_tip": null, "explanation": "The Design Updates clause establishes the process and conditions under which changes or modifications to a project's design can be made after initial approval. Typically, this clause outlines how updates are proposed, reviewed, and approved, and may specify who has authority to request or authorize such changes, as well as any associated costs or timelines. Its core practical function is to provide a clear framework for managing design changes, ensuring that all parties are aware of and agree to modifications, thereby minimizing disputes and maintaining project alignment."}, "json": true, "cursor": ""}}