Figure Res.09 - Resource Number - Number Specification (OLD RN.01)

MODA / Information Framework / Business Entity / Resource Domain / Resource Specification ABE / Figure Res.09 - Resource Number - Number Specification (OLD RN.01)

Project:

Figure Res.09 - Resource Number - Number Specification (OLD RN.01) : Class diagram

Created:	3/28/2022 3:51:09 PM
Modified:	10/1/2023 6:42:51 AM
Project:
Author:	Giu Platania
Version:	1.0.0
Advanced:
ID:	{B48EE6B1-7534-4a86-8D90-66E980E785A8}

This new ABE has only two entities, since it inherits everything needed and a figure to represent the relationship between them. This new entity called ResourceNumber exists not to only manage the specification, but to associate it with portability. The number is a very complex and broad entity, with specific things like format, ranges, area code and other characteristics for the number that vary for each country. Its purpose is to fill the number specification according to Number Portability, but it can be used for number inventory. Both, ResourceNumber and ResourceNumberSpecification, inherit from existing entities, LogicalResourceSpec (from LogicalResource Specification ABE) and LogicalResource (from LogicalResource ABE). ResourceNumber, as it shows, is a sub-class of the abstract class LogicalResource. This is the main class for numbers that relates to the number portability. It has an ID, name, description (inherited by RootEntity), a status (inherited by LogicalResource) and a dialedNumber (For Mobile, Fixed, or IP type of numbers). This entity encapsulates the whole concept of a number in the most general idea and has a relation of many-to-0.1 with the specification (new entity, as well). ResourceNumberSpecification is a sub-class of LogicalResourceSpec (existing entity) from LogicalResource Specification ABE. It defines the number and follows the path for the Characteristic/CharacteristicValue pattern to complete the complexity of the number itself. Resource Function: Support for Virtualization and Resource Abstraction ResourceFunction is a concept that allows resources to be represented by their functional capabilities, features and characteristics rather than exposing the detailed resources and their interconnection and configuration. The ResourceFunction abstraction mechanism is a solution responding to several significant concurrent changes in the industry: <ul>
<li>Virtualization: the transition from delivering communications using Network Appliances - such as core routers to Network Applications running on compute infrastructure such as with Network Function Virtualization and use of virtual Machine and Cloud Infrastructure. In these virtualization solutions tight static coupling of services to resources is infeasible as the resource and their relationships are changing dynamically in the course of providing communication services – hence, abstraction of the Functions from how they are realized is essential to handle volume and velocity of change especial in resource inventories.</li><li>Network Service Abstraction: Network as a Service (NaaS) is based on the notion of exposing Network Connectivity Capabilities as services to BSS and OSS systems. The exposed services - the ‘what ‘ - published in a catalog are decoupled from the detail of the ‘how’ the NaaS realized those service on resources. This is needed to decouple commerce systems from technical systems see IG 1187 ODA Functional Architecture [3] and IG 1194 Focus on Services not Slices [4] which is a practical 5G example of how decouple service and their features from resources. Abstraction is also referred to as Generalization.</li><li>Intent Management: Traditional Network management standards have been based on exposing detailed resource models with their relationship and constraints. This requires the consuming BSS and OSS to understand these models and lead to high coupling and detailed orchestration by the consuming systems. Use of ResourceFunction supports Intent based management interfaces which in turn enable autonomic resource management with use of Closed Control Loop, AI and Big Data analytics that realize the self-configuring, self-healing, self-optimizing, self-evolving networks of the future.</li></ul>
The following sections provide more detail on the practical use of ResourceFunctions for Virtualization, and Network Abstraction using Intent Based Management. Virtualization in the Telecom Domain and Beyond Virtualization of functions, now very common in the Telecom domain, is not specific and is used in many other domains, as we know. If we agree on the extremely simple definition of the very general term “function” below Function: A mechanism that transforms inputs and generates outputs. Then, we realize that depending on the context (e.g. IT, Telecom, game) and the layers, different, but more or less equivalent terms, may be used: application, service, network function. Below are three examples of the evolution of « Functions » from traditional style to virtual style: <ul>
<li>A single game as a single Function or a suite of games Functions Group (Backgammon, Chess, Othello, War games)</li><li>A single office application (e.g. text editor) as a single Function or a suite of office applications (text editor, spreadsheet, presentation)</li><li>A xDSL modem as a single network Function or a network Functions Group such as Firewall, NAT, DNS and routing function.</li></ul>
As will be described later the concepts of Functions and Function Group are modeled in the Information Framework as Resource Functions that can be composed. In the Open APIs Resource Functions are composed by using the ‘is bundled attribute of a ResourceFunctionSpecification. This avoids requiring two types of class and object.