Design Requirement
A Wi-Fi sharing network must prevent the risk of overcharging users through failure of service invoicing.
01
Producer metadata and the represented concept document.
Concept identity
design-knowledge/wifi-sharing-payment-channels-dr-ar-rodesign-knowledge/wifi-sharing-payment-channels-dr-ar-ro.mdA Wi-Fi sharing network must prevent the risk of overcharging users through failure of service invoicing.
This design requirement is proposed by An Architecture Using Payment Channel Networks for Blockchain-based Wi-Fi Sharing (Christian Janiesch, Marcus Fischer, Florian Imgrund, Adrian Hofmann, Axel Winkelmann, 2023).
02
Concepts connected by incoming or outgoing native Markdown links.
design-knowledge/wifi-sharing-payment-channels-dp6Provide the system with a mutually trusted intermediary requiring a transaction history that records a user's data traffic, resource consumption and incurred costs, in order to ensure that connection data cannot be manipulated or corrupted.
design-knowledge/wifi-sharing-payment-channels-dp7Provide the system with a module to keep transaction costs to a minimum in order to prevent large numbers of micro-payments.
design-knowledge/wifi-sharing-payment-channels-dp8Provide the system with a module to forgo transaction costs for the execution of instant payments in order to regulate the duration of the connection.
design-knowledge/wifi-sharing-payment-channels-dp9Provide the system with a module to set up the transaction in order to enable host and user to mutually agree on the usage cost.
design-knowledge/wifi-sharing-payment-channels-dp11Provide the system with accounting mechanisms using a dynamic trust-score in order to facilitate cooperative host behavior and ensure high service levels by rewarding hosts for cooperation or high availability.
design-knowledge/wifi-sharing-payment-channels-dp13Provide the system with a protocol that incrementally increases provided bandwidth together with instant payment functionalities that transfer outstanding payments immediately to unlock further resources, in order to prevent fraudulent behavior.
03
Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.
Derived heading context: Design knowledge
Derived heading context: Addresses
Derived heading context: Addresses
Derived heading context: Addresses
Derived heading context: Addresses
Derived heading context: Addresses
Derived heading context: Addresses
04
One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.
8 of 8 concepts · 20 directed relationships
05
The complete producer frontmatter, serialized without server paths or runtime data.
{
"type": "design-requirement",
"title": "AR#RO - Risk of overcharging",
"description": "A Wi-Fi sharing network must prevent the risk of overcharging users through failure of service invoicing.",
"resource": "https://doi.org/10.1145/3529097",
"source_paper": "An Architecture Using Payment Channel Networks for Blockchain-based Wi-Fi Sharing",
"label": "AR#RO",
"tags": [
"wifi-sharing-payment-channels",
"design-requirement",
"sharing-economy",
"telecommunications",
"payment-channels",
"architecture"
]
}