Search 250 million research papers

Service Layer

Spiro Buzharovski · Apress eBooks · 2022

“Layered” by Filip Rizov

Cited by 0

The Service Layer

Uwe Hansmann, Martin S. Nicklous, Thomas Schäck et al. · 2000

Cited by 0

The Service Layer

2016

The chapter focuses on designing service layers to the system. It also discusses scaling out and scaling up the nodes and which to choose to make the services highly scalable. The key to making compute nodes as scalable as possible is to make them autonomous and stateless. In order to create a highly efficient and scalable service, people need to be able to optimize the inbound and outbound communications. One way to do that is to have separate channels for inbound and outbound communications. The chapter looks at technologies and approaches to designing scalable mobile app services, such as Command Query Responsibility Separation (CQRS). CQRS draws form the Domain Driven Design (DDD) approach to software design. Event Sourcing (ES) is an important concept to have a good understanding of when talking about CQRS/ES systems and separated read and write sides.

Cited by 0

Service Layer Architecture

Enler, Emirhan · University of Debrecen Electronic Archive (University of Debrecen) · 2018

Many implementations of web applications require a service layer between presen-
\ntation and data storage layers. To be able to implement such layers, business logic
\nshould be analyzed to support all requirements of the consumer, suiting architectures
\nmust be designed and a plan of implementation should be executed. However, with
\nthe recent innovations in Computer Science, for example, networking speed and more
\nstorage space, such implementations of service layer architectures might fail to answer
\ncustomer or business demands. If such systems are to be able to ful ll customer and
\ntechnological requirements, the architectures should adapt to the current innovations.
\nThe purpose of this study is to lay out the de nitions and use case examples of
\nexisting service layer architectures, determine what do they provide in order to ful ll
\ndemands, where do they fail to do so and what are the advantages of each of them
\nover the others. In this context, ful lling demands is the extent to the question of how
\nmuch a well-de ned architecture for the requirements can run successfully in relation
\nto the other types of architectures considered in the research.
\nThis research question will be answered by studying the materials published in
\nthe eld, implementation cases, and methodologies in industry, tools, and software
\nused for analyzing and designing such systems. These studies will be subject to
\nclassi cation in regards to the relationships between their advantages, disadvantages
\nor possible pitfalls. Based on these classi cations, results will be compared to each
\nother in order to represent a reasonable answer to the given question.

Cited by 0

OSGi Service Layer Enhancements

2008

Abstract – In recent years software development design shifted from the art of crafting a home tailored solution to the art of component composition. These components are offered in various formats, such as software libraries (Java Archives,.NET Assemblies) or web services and are provided by many different vendors. In these multi-vendor environments there is a genuine need for integration and interoperability. Integration and interoperability is a first step, once this is achieved components can seamlessly use services from different providers, and that is when service policies come into play. A policy mechanism allows fine grained control over the service usage. The OSGi Service Platform is a service container which allows seamless integration of components and services but its service layer lacks a well defined mechanism for dynamic service policy management. Two approaches are presented for enhancing the service layer with policies. The first approach extends the platform while the second one adapts the plug-in components. Finally they are compared and evaluated against multiple requirements; usability, performance, transparency and backward compatibility.

Cited by 0

OSGi service layer enhancements

Nico Goeminne, Gregory De Jans, Jan Hollez et al. · Ghent University Academic Bibliography (Ghent University) · 2006

Cited by 0Open access

3GPP based tv service layer

Thomas Stockhammer, Frédéric Gabin, Gilles Teniou · 2016

Video consumption on mobile devices is getting more and more popular. Among others, a significant amount of traffic is TV centric, but generally delivered Over-The-Top. 3GPP is addressing needs to migrate TV services to 3GPP-based distribution systems by enhancing LTE Broadcast, developing new codec and service extensions and providing solutions to fulfil TV centric requirements. This document presents the latest developments in 3GPP standards from an operator's, end device and network manufacturer's point of view.

Cited by 4

An Efficient Data Service Layer

Rui Yin, Xinfeng Ye · 2010

In service-oriented architecture, the system normally has a data service layer to provide a uniform view of the data in the system. As the users might locate at different locations, how to access the data efficiently becomes a challenging issue. This paper proposed a scheme for implementing the data service layer efficiently.

Cited by 1

A TCP-layer name service

Sérgio Manuel Silva Freire · Portuguese National Funding Agency for Science, Research and Technology (RCAAP Project by FCT) · 2008

A Internet ´e hoje a maior rede mundial mas para al´em disso, ´e tamb´em e essencialmente um meio de disponibiliza¸c˜ao de acesso a conhecimento e a servi¸cos diversos. Tendo como base o protocolo de encaminhamento IP, ´e poss´ıvel endere¸car e comunicar com pessoas, servi¸cos, m´aquinas e dispositivos variados. Uma forma de comunica¸c˜ao usual assenta no protocolo TCP, que permite um di´alogo bidirecional entre servi¸cos locais e/ou remotos, com tolerˆancia e recupera¸c˜ao face a erros e perda de pacotes. No TCP, um servi¸co ´e identificado pelo n´umero do porto a que fica associado, o que tem algumas consequˆencias menos positivas. A mais ´obvia ´e o varrimento de portos (port scanning) para posteriores tentativas de ataque a vulnerabilidades nos servi¸cos identificados/associados a esses portos. Esta tese pretende extender o conceito de endere¸camento dum determinado servi¸co associando-o primordialmente a um nome, ou seja, dotar o TCP dum servi¸co pr´oprio de resolu¸c˜ao de nomes. A fase de estabelecimento da liga¸c˜ao TCP, baseada no three-way handshake, pode ser substancialmente evolu´ıda para suportar mecanismos de resolu¸c˜ao e de autentica¸c˜ao. A solu¸c˜ao encontrada tem a seguran¸ca sempre como um aspecto presente e essencial, por forma a combater diversos tipos de ataque. A resolu¸c˜ao de nomes sugerida pode ser integrada com mecanismos de autentica¸c˜ao/valida¸c˜ao atrav´es do uso de dom´ınios de interpreta¸c˜ao (DOI - domain of interpretation). Os DOIs possibilitam uma forma flex´ıvel de adicionar mecanismos de resolu¸c˜ao e autentica¸c˜ao mais ou menos complexos ao pr´oprio estabelecimento da liga¸c˜ao TCP. ABSTRACT: Internet is the largest network deployed worldwide but besides that it’s also and essentially a way of accessing and distributing knowledge and a way to to interact with services. By using the IP routing protocol it’s possible to address and communicate with other persons, services, hosts or network enabled devices. An usual way for establishing a dialogue between internet endpoints is based on the TCP protocol, permitting a bidirectional, reliable and fault-tolerant data exchange. In TCP a service is identified by an associated port number which by itself has some less positive consequences. The obvious one consists on guessing which services are available by find out the available port numbers (port scanning) so that attacks on service vulnerabilities can take place. The purpose of this thesis is to extend the current concept used for addressing TCP services by associating them with names, or simply to provide TCP an in-band name resolution. The connection establishment phase, three-way handshake, can be improved in order to support simple name resolution mechanisms or even complex authentication. Security aspects towards avoiding attacks was a major concern that is present in the foundations of the proposed architecture. The name resolution model can be integrated with several mechanisms for authentication/validation, implemented as logic defined within domains of interpretation (DOI). DOIs allow a flexible and extensible way for adding those mechanisms to the connection establishment procedures of TCP.

Cited by 0Open access

Application layer versus cross-layer service discovery protocols in MANETs

Fatma Outay, Véronique Vèque, Ridha Bouallègue · 2011

Service discovery in mobile ad hoc networks is challenging because of the absence of any central intelligence in the network. Traditional solutions as used in the Internet are hence not well suited for mobile ad hoc networks. This paper focuses on traditional application layer service discovery protocols (SDP) shortcomings by presenting a fair comparison between application layer and cross-layer protocols. We present and examine our simulation results for both BF-SD-ZRP and SLPManet protocols in order to demonstrate their efficiency and shortcomings in terms of overhead, energy consumption and service discoverability using the scalable network simulator Jist/Swans.

Cited by 2

Forest Service Regional Boundaries (Feature Layer)

U.S. Forest Service (17476914) · Figshare · 2017

An area encompassing all the National Forest System lands administered by a Region. The area encompasses private lands, other governmental agency lands. All National Forest System lands fall within one and only one Administrative Region Area. <a href="https://data.fs.usda.gov/geodata/edw/edw_resources/meta/S_USA.AdministrativeRegion.xml" rel="nofollow ugc noopener noreferrer" target="_blank">Metadata</a><div><br>This record was taken from the USDA Enterprise Data Inventory that feeds into the <a href="https://data.gov">https://data.gov</a> catalog. Data for this record includes the following resources:</div><ul><li> <a href="https://www.arcgis.com/sharing/rest/content/items/d5f88e90e2dd4e86b65ab51f8fe174a6/info/metadata/metadata.xml?format=iso19139 "> ISO-19139 metadata</a></li><li> <a href="https://data-usfs.hub.arcgis.com/datasets/usfs::forest-service-regional-boundaries-feature-layer "> ArcGIS Hub Dataset</a></li><li> <a href="https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_RegionBoundaries_01/MapServer/1 "> ArcGIS GeoService</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/d5f88e90e2dd4e86b65ab51f8fe174a6/csv?layers=1 "> CSV</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/d5f88e90e2dd4e86b65ab51f8fe174a6/shapefile?layers=1 "> Shapefile</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/d5f88e90e2dd4e86b65ab51f8fe174a6/geojson?layers=1 "> GeoJSON</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/d5f88e90e2dd4e86b65ab51f8fe174a6/kml?layers=1 "> KML</a></li></ul><div> For complete information, please visit <a href="https://data.gov">https://data.gov</a>.</div>

Cited by 0Open access

Dynamic Layer Instantiation as a Service

Flavio Esposito, Yuefeng Wang, Ibrahim Matta et al. · 2013

Motivation: one of many fundamental problems with the current Internet architecture is the inability of a higher layer to request the service it requires from the lower layer. This inability, together with the desire to offer virtualized network services, have compounded existing network service manage-ment challenges. For example, in Virtual Private Clouds [1], some of these challenges include network isolation, custom addressing, and dynamic acquisition and release of virtual resources, with different Service Level Objectives (SLOs) and policies. In response to these and other requirements, e.g. security or mobility, many clean-slate architectures arose. For example, XIA [2] provides a mechanism to securely support different address spaces (principals), NDN [3] offers a content distribution application architecture, Mobility-First [4] and

Cited by 0

An anonymity layer for JXTA service

Arnedo Moreno, Joan, Domingo Prieto, Marc · The Oberta in Open Access (Universitat Oberta de Catalunya) · 2011

Cited by 0Open access

Forest Service Office Locations (Feature Layer)

U.S. Forest Service (17476914) · Figshare · 2021

<div>This data includes offices where Forest Service employees work or where IT equipment is housed. There is no Personally Identifiable Information (PII) data in this dataset, nor telework locations. It includes owned, leased and shared offices. Shared offices are buildings owned or leased by another entity (i.e. a university, other federal agency, etc.) but one or more Forest Service employee(s) work at the building or IT equipment is housed at the building.<br></div><div><br></div><div>Depicts the spatial locations for Office locations from the Forest Service CIO Asset Management Office. It includes owned, leased and shared offices. Data is collected, maintained and stewarded by the CIO Asset Management Office. EDW data loading tools extract the office location data from the CIO Asset Mgt. database. Latitude and longitude values are validated and then converted to spatial point data. Spatial point data and associated attributed data describing the office location are inserted into the Office Location Feature class in the Enterprise Data Warehouse. Changes to the Office Location data are checked daily by EDW data loading tools. Data is updated weekly. Data is visible at all scales and zoom levels. <a href="https://data.fs.usda.gov/geodata/edw/datasets.php?xmlKeyword=office+locations" rel="nofollow ugc noopener noreferrer" target="_blank">Metadata and Downloads</a>.<br></div><div><br>This record was taken from the USDA Enterprise Data Inventory that feeds into the <a href="https://data.gov">https://data.gov</a> catalog. Data for this record includes the following resources:</div><ul><li> <a href="https://www.arcgis.com/sharing/rest/content/items/6a2a912a2e0c4804a266c4d77fcaa953/info/metadata/metadata.xml?format=iso19139 "> ISO-19139 metadata</a></li><li> <a href="https://data-usfs.hub.arcgis.com/datasets/usfs::forest-service-office-locations-feature-layer "> ArcGIS Hub Dataset</a></li><li> <a href="https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_FSOfficeLocations_01/MapServer/0 "> ArcGIS GeoService</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/6a2a912a2e0c4804a266c4d77fcaa953/csv?layers=0 "> CSV</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/6a2a912a2e0c4804a266c4d77fcaa953/shapefile?layers=0 "> Shapefile</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/6a2a912a2e0c4804a266c4d77fcaa953/geojson?layers=0 "> GeoJSON</a></li><li> <a href="https://data-usfs.hub.arcgis.com/api/download/v1/items/6a2a912a2e0c4804a266c4d77fcaa953/kml?layers=0 "> KML</a></li></ul><div> For complete information, please visit <a href="https://data.gov">https://data.gov</a>.</div>

Cited by 0Open access

Layer Integrated Quality of Service Management

Tino Hutschenreuther, Sebastian Schönberg · OpenGrey (Institut de l'Information Scientifique et Technique) · 1998

. Emerging high speed networks give rise to new classes of applications like teleconferencing or video-on-demand which demand Quality of Service (QoS). To provide QoS support on an end-to-end basis, the demand of integrating network, transport, and operating system appears since applications compete for network access, processor time and QoS guarantees. This paper discusses QoS requirements to the transport and operating system. Several approaches for QoS management schemes are discussed and problems identified. A possible solution is presented and explained which operates on end-system management on the basis of an admission control for resources. Further QoS specification on the basis of a structured description of the application data contents at the transport system interface is presented. A generic description is presented and the resulting management functionalities inside the transport system are discussed. Keywords: Quality of Service, QoS specification, QoS management, operat...

Cited by 0

Principle of the Pervasive Service Layer

Hongke Zhang, Wei Su, Wei Quan · 2016

Cited by 1

Define Library Systems Data Service Layer

OCLC Research;

Develop a program to design and bring to acceptance a definition of a Library Systems Data Service Layer (an agreement on optimal location of data, data ingest, export and exposure activities of library systems).

Cited by 0

Cross-layer Visibility as a Service

Ramana Rao Kompella, Albert Greenberg, Jennifer Rexford et al. · 2005

Abstract. Accurate cross-layer associations play an essential role in today’s network management tasks such as backbone planning, maintenance, and failure diagnosis. Current techniques for manually maintaining these associations are complex, tedious, and error prone. One possible approach is to widen the interfaces between layers to support auto discovery. We argue instead that it is less useful to export additional data between layers than to import information into a separate management plane. The specification of a management interface enables independent evolution of individual layers, side-stepping the challenges inherent in wide layer interfaces. Further, the management plane can leverage network-wide crosslayer visibility to provide enhanced services that depend on physical- or link-layer diversity. 1

Cited by 0

Service layer components for decentralized applications.

Fabian Stäber · 2008

Im Vortrag wird gezeigt, wie diese Ergebnisse in industriellen Anwendungen genutzt werden konnen. Drei Anwendungsszenarien aus verschiedenen Industrieprojekten werden analysiert. Ausgehend vom Ergebnis dieser Analyse wird eine komponentenbasierte Architektur vorgeschlagen, die es erlaubt, aktuelle Forschungsarbeiten in industrielle Anwendungsbereiche zu ubertragen und fehlende Funktionalitat zu identifizieren. Fur jedes der drei Anwendungsszenarien wird eine neue Softwarekomponente vorgestellt, die die fehlende Funktionalitat bereitstellt und so den Einsatz von peer-to-peer-basierter Dezentralisierung in dem entsprechenden Szenario ermoglicht.

Cited by 4

Architecture of a Personal Network service layer

Joosten, H.J.M., Hartog, F.T.H. den, Selgert, F. · TNO Repository · 2009

We describe a basic service architecture that extends the currently dominant device-oriented approach of Personal Networks (PNs). It specifies functionality for runtime selection and execution of appropriate service components available in the PN, resulting in a highly dynamic, personalized, and context-aware provisioning of PN services to the user. The architectural model clearly connects the responsibilities of the various business roles with the individual properties (resources) of the PN Entities involved.

Cited by 0Open access