China
Africa
Explore chapters and articles related to this topic
Fairness and Bandwidth Allocation
Published in Liansheng Tan, Resource Allocation and Performance Optimization in Communication Networks and the Internet, 2017
The centralized architecture model is a relatively simple and easy to manage solution. For example, as all contents are stored in centralized servers, it does not require a comprehensive content distribution system. Centralized architecture is generally good for a network that provides relatively small VOD service deployment, has adequate core and edge bandwidth, and has an efficient content delivery network. Distributed architecture is just as scalable as the centralized model; however, it has bandwidth usage advantages and inherent system management features that are essential for managing a larger server network. Operators who plan to deploy a relatively large system should, therefore, consider implementing a distributed architecture model right from the start. Distributed architecture requires intelligent and sophisticated content distribution technologies to augment effective delivery of multimedia contents over service provider's network.
Design
Published in Miroslav Popovic, Communication Protocol Engineering, 2018
The deployment of horizontal system partitions onto different processors or computers is used rather frequently by system designers. Examples include the client–server architecture, the multitier architecture, and others. This convenience is why most engineers think of it in the first place when deployment issues are raised. However, the deployment of a vertical system that partitions onto various processors is also possible. A typical example is the Bluetooth Host Controller Interface (HCI), which is a demarcation line between the host processor that executes the upper layers and the Bluetooth link controller (a microprocessor, a microcontroller, or a digital signal processor) that executes the lower layers.
Design
Published in Miroslav Popovic, Communication Protocol Engineering, 2018
The deployment of horizontal system partitions onto different processors or computers is used rather frequently by system designers. Examples include the client-server architecture, the multi-tier architecture, and others. This convenience is why most engineers think of it in the first place when deployment issues are raised. However, the deployment of vertical system partitions onto various processors is also possible. A typical example is the Bluetooth Host Controller Interface (HCI), which is a demarcation line between the host processor that executes the upper layers and the Bluetooth link controller (a microprocessor, a microcontroller, or a digital signal processor) that executes the lower layers.
Architecture and Governance of Digital Business Ecosystems: A Systematic Literature Review
Published in Information Systems Management, 2023
Abide Coskun-Setirek, Maria Carmela Annosi, William Hurst, Wilfred Dolfsma, Bedir Tekinerdogan
The selected DBE articles were also reviewed in terms of architectural design. Various architectural patterns, such as client-server, peer-to-peer (P2P), service-oriented architecture (SOA), layered, cloud, publish-subscribe (Pub/Sub), Representational State Transfer (REST), hub-and-spoke, and fog-based, reported either singly or combined in 32 DBE architecture articles. The client-server architecture, also known as a two-tier architecture application, involves a server application that is reached directly by multiple clients, receives client request and respond to the clients (Javed et al., 2020). Multitier (n-Tier) architecture, is a client-server architecture that functions are separated more than two tiers (Figay et al., 2012). In a P2P architecture, every participating system can play the client as well as the server role, the roles can be changed dynamically so that it does not depend on the central server (Kim & Kim, 2018). SOA integrates software components that have been separately deployed, and traditionally has an integration strategy based on the enterprise service bus (ESB) technology for communication among software applications in different modules (Appio et al., 2018; Kuk & Janssen, 2013; Reforgiato Recupero et al., 2016).
Anarchic manufacturing
Published in International Journal of Production Research, 2019
Andrew Ma, Aydin Nassehi, Chris Snider
Hierarchical architectures are those that have a layered management structure, with decreasing authority and autonomy. These hierarchical and centralised structures typically have a master/slave relationship and traditionally use structure to handle complexity (Heragu et al. 2002). They are the predominate management structure in industry, particularly for non-autonomous human-centred shop floors, which often use simple dispatch heuristics; for example a job shop queuing estimate heuristic (Chang 1997). There has been extensive research into advanced centralised methods, for example advanced search heuristics, to obtain optimal solutions in static environments. Centralised methods are criticised for being too rigid and very poor at reacting to dynamic situations (Scholz-Reiter, Rekersbrink, and Görges 2010). Recent related works in centralised systems cover advanced search algorithms for similar scenarios; Shamshirband et al. investigates a genetic-based open-shop scheduling on considering machine maintenance (Shamshirband et al. 2015), additionally Hosseinabadi et al. uses a gravitational emulation local search algorithm for multi-objective dynamic job shop scheduling (Hosseinabadi et al. 2015). For this study, a simple (First In First Out) FIFO heuristic is used to compare hierarchical systems relative to anarchic, this is sufficient to evaluate inherent traits of the two system types.
A reference architecture for IoT-based logistic information systems in agri-food supply chains
Published in Enterprise Information Systems, 2018
C.N. Verdouw, R.M. Robbemond, T. Verwaart, J. Wolfert, A.J.M. Beulens
The research reported upon in this paper is based on a design-oriented methodology. Design-oriented research focuses on building purposeful artefacts that address heretofore unsolved problems and are evaluated with respect to the utility provided in solving those problems (March and Smith 1995; Hevner et al. 2004). The design artefact developed in the present paper is a reference architecture for IoT-based logistic information systems in agri-food supply chains. Architecture can be defined as the fundamental organisation of a system embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution (IEEE 1471:2000). Reference architectures are predefined models of recommended practices that are used as a ‘frame of reference,’ and, as such, they improve quality, costs and lead-times of information modelling processes (Verdouw, Beulens, Trienekens, and Verwaart 2010). Reference architectures can represent different architectural views, depending on the purpose of usage. The present research aims to use Future Internet technologies for logistic applications in agri-food supply chains. Consequently, the architecture should especially represent the interactions between functionalities and technological implementation. For this reason, we have chosen a combination of a process view, service view and technical view. These views are modelled in the Archimate methodology (The Open Group 2012; Lankhorst 2013) using Archi, an open source Archimate modelling tool (Archi 2012).