Publication

Service Management: From definition to information modeling

Jean-Pierre Hubaux
1996
Conference Papers

Abstract

In this paper, we split the service management layer, as defined in the Telecommunication Management Network (TMN), into two sublayers, namely the service application management sublayer and the service network management sublayer. The former deals with managing the mapping of the non functional requirements into functional constraints over the telecommunication service of interest, while the second reveals the management details related to meeting the functional requirements over that service. At each sublayer, we propose an information model and emphasize the correspondence with the other sublayer.

Official source

https://infoscience.epfl.ch/entities/publication/47e38cf0-b8ba-4f88-8635-86e90946d301

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

Jean-Pierre Hubaux
1996
Conference Papers

Abstract

Official source

https://infoscience.epfl.ch/entities/publication/47e38cf0-b8ba-4f88-8635-86e90946d301

About this result

Related concepts (32)

Application layer

An application layer is an abstraction layer that specifies the shared communications protocols and interface methods used by hosts in a communications network. An application layer abstraction is specified in both the Internet Protocol Suite (TCP/IP) and the OSI model. Although both models use the same term for their respective highest-level layer, the detailed definitions and purposes are different. In the Internet protocol suite, the application layer contains the communications protocols and interface methods used in process-to-process communications across an Internet Protocol (IP) computer network.

Functional requirement

In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a summary (or specification or statement) of behavior between inputs and outputs. Functional requirements may involve calculations, technical details, data manipulation and processing, and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describe all the cases where the system uses the functional requirements, these are captured in use cases.

Non-functional requirement

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.

Related publications (21)

Service Management: From definition to information modeling

Chat with Graph Search

Neuromorphic iontronic devices based on soft ionic conductors

Scalable and Resource-Efficient Stream Processing

Refolding-assisted purification of native full-length TDP-43 compatible with BSL-2 safety regulations