Computational Overhead Sample Clauses
Computational Overhead. In this section, we present the evaluation of the computational overhead. We define the notation for computational overhead as follows: exp: a round of the function , z(g, x), from which the output is gx. add: a round of the function, z(a, b), from which the output is a+b. mul: a round of the function, z(a, b), from which the output is a*b.
Computational Overhead. <.. image(グラフ, 棒グラフ 自動的に生成された説明) removed ..> <.. image(グラフ, 等高線グラフ 自動的に生成された説明) removed ..> representing the duration of the authentication process is measured at 8 ms. Key Agreement Time, the time spent in reaching an agreement between communicating entities, is noted as 15 ms. The Overall Session Establishment Time, encompassing key generation, authentication, and key agreement, sums up to 28 ms. Furthermore, the success rates for authentication and key agreement are crucial metrics. The Authentication Success Rate is at an impressive 95%, emphasizing the reliability of the authentication process. The Key Agreement Success Rate stands at 90%, signifying a high success rate in establishing secure key agreements. However, it's crucial to note a small failure rate, with Authentication Failure at 5% and Key Agreement <.. image(グラフ, 折れ線グラフ 自動的に生成された説明) removed ..> <.. image(グラフ, 折れ線グラフ 自動的に生成された説明) removed ..> <.. image(グラフ, 棒グラフ 自動的に生成された説明) removed ..>
Computational Overhead. According to the results shown in Figure 10, the average total delay time required by the BlendCAC operation of retrieving data from the client to server is 243 ms, which is almost the same as RBAC or ABAC. The total delay includes the round trip time (RTT), time for querying the capability data from the smart contract, time for parsing JSON data from the request, and time for access right validation. The token processing task is mainly responsible for fetching the token data from the smart contract and introduces the highest workload among the authorization operation stages. Owing to the fact that encapsulating the user–role relationship in the smart contract requires less data than the capability or attributes does, the RBAC incurred less computational cost than what BlendCAC and ABAC did in token processing stage. As the most computing intensive stage, the execution time of token processing is about 210 ms, which accounts for almost 86% of the entire process time.