Telecommunications network resource handling arrangement and method

• US 7,054,873 B2
• Filed: 11/05/2001
• Issued: 05/30/2006
• Est. Priority Date: 05/04/1999
• Status: Expired due to Fees

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Samuelsson, Lars, Augustsson, Hans, Nordström, Klas, Hofgren, Per-Anders, Svala, Elisabeth
• Primary Examiner(s): Gaffin, Jeffrey
• Assistant Examiner(s): Veillard, Jacques
• Application Number:
  US09/993,843
• Publication Number:
  US 20020073193A1
• Time in Patent Office: 1,667 Days
• Field of Search: 707/10, 707/100, 707/101, 707/104.1, 707/103.R, 709/223, 709/224, 709/226, 709/229, 709/202, 709/203
• US Class Current: 1/1
• CPC Class Codes: H04L 2012/5631 Resource management and allocation
• CPC Class Codes: H04L 41/024 using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
• CPC Class Codes: H04M 3/22 Arrangements for supervision, monitoring or testing
• CPC Class Codes: H04Q 11/0478 Provisions for broadband connections
• CPC Class Codes: H04Q 3/0062 Provisions for network management
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A resource handler for use in an operational support structure for managing a telecommunications network. The handler includes a service and resource database containing information regarding network resources. The database arrangement is structured so that each resource in the network has a time of existence as well as a place in a hierarchy of parent/child relations. The resource is defined by the following data: a point identifier that has characteristics associated with it, in the form of an abstract description of the resources capabilities; an abstraction of a common network element represented by a group of points that are considered to belong together, and a connection, which is defined by two connected points.

Claims

1. A resource handler for use in an operational support structure for managing a telecommunications network, the resource handler comprising a service and resource database arrangement containing information regarding network resources, wherein the database arrangement is structured so that each resource in the network has a time of existence as well as a place in a hierarchy of parent/child relations, and each resource being defined by data comprising:

a point identifier that has characteristics associated to it, representing an abstract description of the resources capabilities;

an abstraction of a common network element represented by a group of points that are considered to belong together; and

a connection being defined by two connected points;

wherein the database arrangement is structured so as to model a usage view, which includes what resources are combined to form a complete service instance and the time when that service instance exists.

2. The resource handler according to claim 1, wherein the point identifier also has characteristics associated with it in the form of a list of label/value pairs.

3. The resource handler according to claim 1, wherein the common network element acts as a container for points, with an implicit characteristic that points on elements may cross-connect.

4. The resource handler according to claim 1, wherein the database arrangement is structured so as to model a topological view.

5. The resource handler according to claim 1, wherein the database arrangement is structured so as to model a time view.

6. The resource handler according to claim 1, wherein the database arrangement is structured so as to model a hierarchic view.

7. The resource handler according to claim 1, wherein the database arrangement is structured so as to model a characteristic view, which includes a list of characteristics of each resource.

8. The resource handler according to claim 1, wherein the database arrangement structure is integrated in a data model for enabling control of each resource and the use of it in service instances.

9. The resource handler according to claim 1, wherein the database arrangement is separated into a first database comprising resource types and resource instances and a second database comprising service types and service instances.

10. The resource handler according to claim 1, wherein resource and/or service attributes are typed to distinguish between attribute types.

11. The resource handier according claim 1, wherein the resource handler is a service type handler in an operational support structure for a telecommunications network, for creating and maintaining service type recipes and their relations.

12. The resource handler according to claim 11, wherein the service type recipes provide a framework for service types, operations on service types, parameters on service types, hierarchical relations between service types, hierarchical parameter relationship, and translation of service types and associated parameters values into resource requirements and service type requirements.

13. The resource handler according to claim 11, wherein the resource handler supports selecting between different types of required services, different types of required resources and different service instances.

14. The resource handler according to claim 13, wherein the selected resources requirements are transferred to a resource handler that does the actual resource allocation.

15. A method of structuring information in a resource handler database for use in an operational support structure for managing a telecommunications network, the support structure comprising a service and resource database arrangement containing information regarding network resources, the method comprising the steps of:

allocating to each resource in the network a time of existence as well as a place in a hierarchy of parent/child relations; and

defining each resource by associating data comprising;

a point identifier That has characteristics associated with it representing an abstract description of its capabilities;

an abstraction of a common network element represented by a group of points that are considered to belong together; and

a connection being defined by two connected points;

wherein the database arrangement is structured so as to model a usage view, which includes what resources are combined to form a complete service instance and the time when that service instance exists.

16. The method according to claim 15, wherein the characteristics associated with the point identifier include a list of label/value pairs.

17. The method according to claim 15, wherein the common network element acts as a container for points, with the implicit characteristic that points on elements may cross-connect.

18. The method according to claim 15, wherein the database arrangement is structured so as to model a topological view.

19. The method according to claim 15, wherein the database arrangement is structured so as to model a time view.

20. The method according to claim 15, wherein the database arrangement is structured so as to model a hierarchic view.

21. The method according to claim 15, wherein the database arrangement is structured so as to model a characteristic view.

22. The method according to claim 15, wherein the database arrangement structure is integrated in a data model for enabling control of each resource and the use of it in service instances.

23. The method according to claim 15, further comprising the steps of:

separating the database arrangement into two separate databases, and

keeping resource type data and resource instance data in one of said separate databases, and

keeping service type data and service instance data in the other of said separate databases.

24. The method according to claim 15, further comprising the steps of:

assigning types to resource and/or service attributes, and

using said attribute types to distinguish between different types of attributes.