{"component": "clause", "props": {"groups": [{"size": 2, "snippet_links": [{"key": "as-shown", "type": "definition", "offset": [34, 42]}, {"key": "mission-area", "type": "definition", "offset": [261, 273]}, {"key": "number-of", "type": "clause", "offset": [374, 383]}, {"key": "physical-layer", "type": "clause", "offset": [502, 516]}, {"key": "data-link", "type": "definition", "offset": [532, 541]}, {"key": "data-transmission", "type": "clause", "offset": [847, 864]}, {"key": "power-consumption", "type": "definition", "offset": [889, 906]}, {"key": "proposed-system", "type": "definition", "offset": [928, 943]}, {"key": "the-process", "type": "clause", "offset": [945, 956]}, {"key": "the-information", "type": "clause", "offset": [1056, 1071]}, {"key": "gps-unit", "type": "definition", "offset": [1195, 1203]}, {"key": "transmission-of-data", "type": "clause", "offset": [1351, 1371]}, {"key": "frequency-of", "type": "clause", "offset": [1449, 1461]}, {"key": "the-other-hand", "type": "clause", "offset": [1474, 1488]}, {"key": "the-data", "type": "clause", "offset": [1490, 1498]}, {"key": "pay-off", "type": "clause", "offset": [1608, 1615]}, {"key": "of-the-scheme", "type": "clause", "offset": [1616, 1629]}, {"key": "computational-cost", "type": "clause", "offset": [1639, 1657]}, {"key": "on-the-ground", "type": "definition", "offset": [1658, 1671]}, {"key": "directed-to", "type": "definition", "offset": [1718, 1729]}], "samples": [{"hash": "e9x49qE6Szm", "uri": "/contracts/e9x49qE6Szm#network-model", "label": "Certificate Based Access Control and Key Agreement Scheme", "score": 25.0944558522, "published": true}, {"hash": "aafUISsLArX", "uri": "/contracts/aafUISsLArX#network-model", "label": "Certificate Based Access Control and Key Agreement Scheme", "score": 25.0109514031, "published": true}], "snippet": "There are \u201cn\u201d drones, where n \u2265 2 as shown in Fig.1. The drones are categorized into either of the two groups: Sensor Drone (S-Drone) and Gateway Drone (G-Drone). Drones from both the groups are placed in the geographical clusters that collectively make up the mission area. Each of the drones, from both G-Drones and S-Drones, are assigned a unique ID. A cluster has fixed number of drones out of which there must be a G-Drone that is linked to the ground station. A drone has following three layers: physical layer (bottom part), data link layer (middle part) and upper layer (top port). The IEEE 802.15.4 (ZigBee) system is installed on Sensor Drones (S- Drones). Gateway Drones (G-Drones) leverage both the radio technologies i.e. IEEE 802.15.4 (ZigBee) and IEEE 802.11a (Wi-Fi). In this way, the features promised by IEEE 802.11a (high-speed data transmission) and IEEE 802.15.4 (low-power consumption) are utilized by the proposed system. The process of network formation kicks off as soon as a drone lifts off. Here, the drones are, supposedly, fed the information about neighbor\u2019s zone ID, location, altitude and speed etc. Further, the information does include the height sensors, IMU, GPS unit and the flight controller etc. The associated drones are interlinked together using the discovery function, which makes use of the beacon signals. Transmission of data between the S-Drones and G-Drones is accomplished using IEEE 802.15.4 at the frequency of 2.4 GHz. On the other hand, the data is routed between G-Drones and the ground station using IEEE 802.11a at the frequency of 5 GHz. An immediate pay off of the scheme is lower computational cost on the ground station since it only retains the information directed to it.\nFig.1. Network model", "hash": "d58c853c731b6cdfbce4e2c2db51deac", "id": 1}, {"size": 2, "snippet_links": [{"key": "access-point", "type": "definition", "offset": [147, 159]}, {"key": "wide-area-network", "type": "clause", "offset": [175, 192]}, {"key": "a-fixed", "type": "clause", "offset": [296, 303]}, {"key": "the-future", "type": "clause", "offset": [318, 328]}, {"key": "number-of", "type": "clause", "offset": [348, 357]}, {"key": "available-channels", "type": "definition", "offset": [358, 376]}], "samples": [{"hash": "gNYuXV5xyM2", "uri": "/contracts/gNYuXV5xyM2#network-model", "label": "Dynamic Contract for Spectrum Reservation", "score": 25.214840108, "published": true}, {"hash": "9oxjMwal5Tu", "uri": "/contracts/9oxjMwal5Tu#network-model", "label": "Dynamic Contract for Spectrum Reservation", "score": 21.1095140315, "published": true}], "snippet": "We assume that a single IoT operator is coordinating the communication between low power IoT devices using UNB transmissions. We consider a single access point (AP) serving a wide area network of IoT devices. The AP reserves TF blocks in the available whitespace in existing licensed spectra for a fixed duration T in the future. Let nt denote the number of available channels of equal bandwidth \u03b2 at time", "hash": "baab48c91c201ebe763515d25c04b670", "id": 2}, {"size": 1, "snippet_links": [{"key": "a-geographic", "type": "definition", "offset": [248, 260]}, {"key": "reporting-data", "type": "clause", "offset": [548, 562]}, {"key": "to-operate", "type": "definition", "offset": [581, 591]}, {"key": "space-construction", "type": "clause", "offset": [638, 656]}, {"key": "information-distribution", "type": "clause", "offset": [668, 692]}], "samples": [{"hash": "isLVIYWiyOR", "uri": "/contracts/isLVIYWiyOR#network-model", "label": "Self Configuring Scheme for Location Aware Key Establishment in Wireless Sensor Networks", "score": 19.0, "published": true}], "snippet": "We consider a large-scale stationary sensor network de- ployed in outdoor environments. Sensors are able to position themselves through any of the techniques proposed in liter- ature (e.g. [8], [18]), and they communicate with each other following a geographic routing protocol (e.g. [13]). We assume homogeneous sensors densely deployed in a given region. Sensors are preloaded with several system pa- rameters, and differentiate themselves as either worker sensors or service sensors after deployment. Worker sensors are in charge of sensing and reporting data, and are expected to operate for years. Service sensors take charge of key space construction and keying information distribution. They may die after their duty is complete.", "hash": "943a7ccfc23311861b69e4d3c035f9b3", "id": 3}, {"size": 1, "snippet_links": [{"key": "figure-2", "type": "clause", "offset": [0, 8]}, {"key": "the-network", "type": "clause", "offset": [15, 26]}], "samples": [{"hash": "ead1wMyaY1J", "uri": "/contracts/ead1wMyaY1J#network-model", "label": "Machine to Machine Authenticated Key Agreement With Forward Secrecy for Internet of Things", "score": 34.9277262478, "published": true}], "snippet": "Figure 2 shows the network environment and its description is as follows:", "hash": "6677e846758edddbafab0912b8d066c3", "id": 4}, {"size": 1, "snippet_links": [{"key": "the-network", "type": "clause", "offset": [22, 33]}, {"key": "single-cell", "type": "definition", "offset": [55, 66]}, {"key": "our-system", "type": "definition", "offset": [148, 158]}, {"key": "purpose-of-this", "type": "clause", "offset": [212, 227]}, {"key": "transmit-power", "type": "clause", "offset": [432, 446]}, {"key": "caused-by", "type": "clause", "offset": [693, 702]}, {"key": "communication-requirements", "type": "definition", "offset": [1251, 1277]}, {"key": "power-of", "type": "clause", "offset": [1558, 1566]}, {"key": "be-calculated-as-follows", "type": "clause", "offset": [1710, 1734]}], "samples": [{"hash": "5xXbxva9Ifm", "uri": "/contracts/5xXbxva9Ifm#network-model", "label": "End User License Agreement", "score": 23.704312115, "published": true}], "snippet": "\u200c Fig 3.1 illustrates the network model. We consider a single cell two-tier HetNet that consists of a macrocell and multiple N dense femtocells. In our system, we consider a single MUE and multiple FUE. The main purpose of this work is to achieve the required QoS by managing the interference in the downlink of dense two-tier HetNets. High transmission power triggers significant interference to the UE in a BS vicinity, while low transmit power results in the UE not receiving the desired signal. It is assumed that the spectrum of all transmitted signals to be the same; narrowband signaling or single subcarriers of wideband multicarrier signals [74]. In the downlink, the interference is caused by the MBSs and the FAPs. Concretely, there are mainly three interference scenarios: \u2022 FAP interferes with neighboring \u2587\u2587\u2587\u2587. Although the FAP transmit power being significantly lower than the MBS, the MUE is prone to interference from the FAP if nearly located, leading to a QoS degradation. Consequently, to avoid significant interference to the neighboring MUE, FAPs transmit power should be as low as possible. \u2022 MBS interferes with FUE. MBS high transmit power may initiate interference to the FUE, so the FAP transmit power must ensure the FUE\u2019s communication requirements.\nFig. 3.1 Two-tier Femtocell HetNet \u2022 The interference from the FAP to the other FUE. Since the FAPs are basically deployed indoors, the associated FUEs will be prone to interference when the neighboring FAP select channels of the same frequency. However, because the transmitted power of FAP is inconspicuous, interference only exists between nearby femtocells. The Signal to Interference and Noise Ratio (SINR) of MUE and FUE can be calculated as follows. SINRMUE = Pmhm,MUE\n(3.1) \u2211\ni=1 Pih fi,MUE + \u03c3 2 Similarly, SINRFUE = Pih fi,FUEi\n(3.2) i Pmhm,FUE + \u2211N Pjhf ,FUE + \u03c3 2 i j=1, j i j i Pm and Pi denote MBS and FAP transmit powers, respectively. The fading coefficient between an MBS m and the typical UE is denoted by hm. Comparably, the fading coefficient between a FAP f and the typical user UE is denoted by h fi, j .", "hash": "97651fd4b0d45f98938ed18e7c32511c", "id": 5}, {"size": 1, "snippet_links": [{"key": "s-s", "type": "clause", "offset": [14, 17]}, {"key": "number-of", "type": "clause", "offset": [266, 275]}, {"key": "the-network", "type": "clause", "offset": [285, 296]}, {"key": "our-scheme", "type": "definition", "offset": [351, 361]}, {"key": "the-non", "type": "clause", "offset": [428, 435]}], "samples": [{"hash": "kZ8kiHG4iSG", "uri": "/contracts/kZ8kiHG4iSG#network-model", "label": "Key Agreement Scheme", "score": 19.0, "published": true}], "snippet": "S \u00d7 S \u00d7 \u00b7\u00b7\u00b7 \u00d7 S S \u2282 S\n1) ni is a positive integer drawn from a subspace i, for i = 1, 2,... , k;\n2) Any two subspaces have no intersection, i.e., Si Sj = \u03c6, for i, j = 1, 2,... ,k and i \u0192= j;\n3) The cardinality |Si| = Ni, for i = 1, 2,... , k. N = Hence the maximum number of nodes in the network can be and KTC is worse than non-interactive schemes. Our scheme tries to achieve a trade-off between the interactive approach and the non-interactive approach, thus the memory cost per node can be reduced.", "hash": "ce254905c1ea41366545c29cb7fa2dc1", "id": 6}, {"size": 1, "snippet_links": [{"key": "ta-group", "type": "definition", "offset": [9, 17]}, {"key": "wireless-connection", "type": "definition", "offset": [26, 45]}], "samples": [{"hash": "fClZHCyZMJs", "uri": "/contracts/fClZHCyZMJs#network-model", "label": "Self Authentication and Deniable Efficient Group Key Agreement Protocol", "score": 25.539571149, "published": true}], "snippet": "Internet TA Group RSU RSU Wireless connection Wire connection", "hash": "5fcd2848568feb3ea8c4e581dc66eb8f", "id": 7}, {"size": 1, "snippet_links": [{"key": "the-network", "type": "clause", "offset": [0, 11]}, {"key": "the-proposed-scheme", "type": "clause", "offset": [22, 41]}, {"key": "network-architecture", "type": "clause", "offset": [86, 106]}, {"key": "authentication-server", "type": "definition", "offset": [226, 247]}, {"key": "to-register", "type": "clause", "offset": [279, 290]}, {"key": "other-entities", "type": "clause", "offset": [291, 305]}, {"key": "registration-authority", "type": "clause", "offset": [358, 380]}, {"key": "the-gs", "type": "clause", "offset": [410, 416]}, {"key": "registration-process", "type": "definition", "offset": [482, 502]}, {"key": "and-authentication", "type": "clause", "offset": [562, 580]}, {"key": "working-areas", "type": "clause", "offset": [737, 750]}, {"key": "locking-system", "type": "definition", "offset": [786, 800]}, {"key": "information-from", "type": "clause", "offset": [814, 830]}, {"key": "cloud-server", "type": "definition", "offset": [938, 950]}, {"key": "the-data", "type": "clause", "offset": [1000, 1008]}], "samples": [{"hash": "9F7C3c7cXmz", "uri": "/contracts/9F7C3c7cXmz#network-model", "label": "Biometric Based Key Agreement Scheme", "score": 34.8321718245, "published": true}], "snippet": "The network model for the proposed scheme (BioKA-ASVN) is provided in Fig. 1. In this network architecture, we consider the communication entities as a) user (Ui), b) drone (DRj), and c) a ground server (also considered as an authentication server) (GS). GS has a responsibility to register other entities in the network and is assumed to be a fully trusted registration authority. A user Ui can register with the GS by providing minimal information securely, and at the end of the registration process, GS gives some secret credentials for future communication and authentication. The GS registers a drone with unique and distinct credentials for each DRj. Once the registration is over, the entities are deployed into their respective working areas, and GS is placed under a physical locking system. DRj detects information from a drone\u2019s airspace and sends it to the associated GS, which is forwarded to an attached peer-to-peer (P2P) cloud server (CS) network, also known as a blockchain center. The data is finally stored in a blockchain for secure storage.\u200c", "hash": "920b256877af9fe70bdb754c24b06e11", "id": 8}, {"size": 1, "snippet_links": [], "samples": [{"hash": "6QCezgypGfI", "uri": "/contracts/6QCezgypGfI#network-model", "label": "Key Agreement Scheme", "score": 19.0, "published": true}], "snippet": "where ni = 0, 1,..., Ni \u2212 1 for i = 1, 2,..., k. Thus, the k credentials are drawn from different zones in that c1 \u2208 [1, N1] and ci [N1 + + Ni\u22121 + 1, N1 + + Ni] for i = 2,... k, which guarantee they are positive and pairwise different (Fig. 1). For a node (n1, n2,..., nk), a polynomial share \u03a3 We assume each node is identified by an index-tuple 1 (n ,n ,...,n ), where n = 0, 1,...,N \u2212 1,i \u2208 fk+1(xk+1) = f (c1, c2,... , ck, xk+1) = ik+1=0 bik+1 ik+1 k+1", "hash": "03efae1e8ae76d566b5ce870632fe8cb", "id": 9}, {"size": 1, "snippet_links": [{"key": "general-architecture", "type": "clause", "offset": [7, 27]}, {"key": "communication-of", "type": "clause", "offset": [55, 71]}, {"key": "other-vehicles", "type": "definition", "offset": [91, 105]}, {"key": "based-on", "type": "clause", "offset": [144, 152]}, {"key": "the-vehicles", "type": "clause", "offset": [281, 293]}], "samples": [{"hash": "9QLsiIE75eI", "uri": "/contracts/9QLsiIE75eI#network-model", "label": "Secure Key Agreement and Authentication Protocol", "score": 24.3456536619, "published": true}], "snippet": "In the general architecture of vehicular networks, the communication of vehicles among the other vehicles or with the road side units (RSUs) is based on dedicated short-range communication [20], where the vehicle-to-Infrastructure (V2I) communication is the external network among the vehicles and RSUs. Vehicular Cloud Trusted Authority", "hash": "326ff9d2240b8635f57b4f82b34e3581", "id": 10}], "next_curs": "ClYSUGoVc35sYXdpbnNpZGVyY29udHJhY3RzcjILEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhZuZXR3b3JrLW1vZGVsIzAwMDAwMDBhDKIBAmVuGAAgAA==", "clause": {"children": [["", ""], ["master-controller-node-mcn", "Master Controller Node (MCN)"], ["smart-sensing-devices", "Smart Sensing Devices"], ["users", "Users"], ["trusted-registration-authority-ta", "Trusted Registration Authority (TA)"]], "size": 22, "parents": [["introduction", "INTRODUCTION"], ["system-models", "System Models"], ["review-and-analysis-of-\u2587\u2587\u2587-et-al", "REVIEW AND ANALYSIS OF \u2587\u2587\u2587 et al"], ["background", "BACKGROUND"], ["related-works", "Related Works"]], "title": "Network Model", "id": "network-model", "related": [["model", "Model", "Model"], ["network-upgrades", "Network Upgrades", "Network Upgrades"], ["network-services", "Network Services", "Network Services"], ["functionality", "Functionality", "Functionality"], ["interface", "Interface", "Interface"]], "related_snippets": [], "updated": "2025-07-07T12:37:53+00:00", "also_ask": [], "drafting_tip": null, "explanation": "The Network Model clause defines the structure and operation of the network through which services, data, or communications are delivered under the agreement. It typically outlines the technical architecture, connectivity requirements, and responsibilities for maintaining the network, such as specifying whether a centralized or distributed model is used and who is responsible for network security and uptime. This clause ensures both parties have a clear understanding of how the network will function, reducing the risk of disputes over performance or responsibilities."}, "json": true, "cursor": ""}}