WO2013050059A1

WO2013050059A1 - Method and system for providing license control in a telecommunications network

Info

Publication number: WO2013050059A1
Application number: PCT/EP2011/067239
Authority: WO
Inventors: Giuseppe CELOZZI
Original assignee: Telefonaktiebolaget L M Ericsson (Publ)
Priority date: 2011-10-03
Filing date: 2011-10-03
Publication date: 2013-04-11

Abstract

A method and apparatus for controlling the use of licensed Operation support system application services in the of a telecommunications network (10), the network comprising first and second network element management systems (11,12) for independently managing network elements (14) of the network using respective licensed application services, wherein the network element management systems (11,12) are interconnected by a communication link (13). In use, the use of unauthorized application services can be prevented by determining if the first network element management system (11) is able to contact the second network element management system (12) via the communication link and then by invoking a termination procedure for at least partially disabling the licensed application service on the first network element management system (11) if the first network element management system (11) is unable to contact the second network element management system via said communication link (13).

Description

Method and system for providing license control in a

telecommunications network

Technical Field

The present invention relates to a method and system for providing software licence control in a telecommunications network, and more particularly but not solely to a method and system for providing licence control in geographical redundant systems.

Background

Operation support systems (OSS) of telecommunications networks are often configured as redundant in order to minimise the absence of the OSS in the event of a hardware or connection failure of the OSS. In the redundant configuration there exists a networked grouping of network element management systems with sufficient redundancy of hardware and software that a single point of failure (SPOF) will not significantly disrupt service. In such a configuration, the failure of single service, node, network or other resource prompts the automatic transfer of control of the relevant software package to a stand-by network element management system, thereby allowing services to remain available with minimal interruption.

The pricing of OSS systems is calculated based on the number of software licenses purchased with the system. Each license is valid for a given number of network element management systems (EMS), network elements (NE), boards, ports etc, so any given telecommunications network may require more than one license in order to deliver the desired capabilities to the end-user.

I n a redundant configuration, only one network element management system provides capability to the end-user at any one time. Accordingly, the cost of the licence should reflect this. However, since a redundant system comprises more than one network element management system, there is the potential to reconfigure the system such that the individual network element management systems operate simultaneously and independently, thereby doubling the capability offered to the end- user. Currently there is no means of determining whether the network is operating as a redundant system or whether the network element management systems are operating independently. Consequently, the only way to ensure that the licence supplier suffers no loss of revenue is to assume that the network element management systems will be operating independently i.e. the cost of a licence for a redundant system must be equivalent to the total cost of the licences for all of the individual network element management systems. We have now devised a method and system for providing licence control in a telecom m un icati ons network com prisi ng more than one network element management system though monitoring of the configuration of the network.

Summary

In accordance with the present invention, there is provided a method of controlling the use of a licensed application service in a telecommunications network. The telecommunications network com prises fi rst and second network el em ent management systems for independently managing network elements of the network using respective licensed application services, wherein the network element management systems are interconnected by a communication link. The method comprises determining if the first network element management system is able to contact the second network element management system via said communication link. The method further comprises invoking a termination procedure for at least partially disabling the licensed application service on the first network element management system if the first network element management system is unable to contact the second network element management system via said communication link.

The first and second network element management systems may respectively provide the primary and stand-by OSS functions in the telecommunications network. The inability of the primary network to contact the stand-by network may indicate that the secondary network is not being used within the terms of the licence and so a termination procedure may be invoked.

In the event that communication is established , the invoking the termination procedure may also be invoked if at least one of the network element management systems is determined not to be authorized to run the application service that is installed thereon.

The termination procedure may also be invoked if the first and second network element management systems are determined to be managing different network elements of the network. The first and second network element management systems have respective management roles of primary and stand-by and the method of the present invention is able to establish whether the roles of the first and second network element management systems are the same so that the management role of the first or second network element management system can be reconfigured if the network element management systems are determined to have the same roles.

In the course of establishing the roles, the first network element management system has to contact the second network element management system via the communication link, the termination procedure then being invoked if the first network element management system is unable to contact the second network element management system via the communication link.

The termination procedure may comprise measuring a disrupted time period over which the first network element management system is unable to contact the second network element management system via said communication link and at least partially disabling the application service if said disrupted time period exceeds a first threshold value. In this way short period of disruption do not trigger the termination procedure to be invoked. However, termination procedure may be invoked if the period between successive disrupted time periods is too short.

Also, in accordance with the present invention, there is provided an apparatus for use in a network element management system for controlling the use of a licensed application service in a telecommunications network. The telecommunications network comprises first and second network element management systems for independently managing network elements of the network using respective licensed application services. The network element management systems are interconnected by a communication link. The apparatus comprises a monitor for determining if the first network element management system is able to contact the second network element management system via said communication link. The apparatus also comprises a processor for invoking a termination procedure for at least partially disabling the licensed application service on the first network element management system if the first network element management system is unable to contact the second network element management system via said communication link.

Also, in accordance with the present invention, there is provided a telecommunication system incorporating the aforementioned apparatus. Brief description of the drawings

An embodiment of the present invention will now be described by way of example only and with reference to the accompanying drawings, in which:

Figure 1 is a block diagram of a telecommunications network comprising two network element management systems in accordance with an embodiment of the present invention;

Figure 2 is a block diagram of a network element management system of the network of Figure 1 ;

Figure 3 is a flow diagram illustrating an embodiment of the method of the present invention;

Figure 4 is a flow diagram illustrating one embodiment of the termination procedure of the present invention;

Figure 5 is a flow diagram illustrating an example message exchange between two network element management systems of the present invention; and Figure 6 is is a flow diagram illustrating an embodiment of the method of the present invention.

Detailed description Referring to Figure 1 of the drawings, there is shown in a telecommunications network 10 comprising a pair of Operation support system (OSS) nodes A, B arranged in redundant configuration. The configuration illustrated is a two-node cluster but other redundant configurations such 1 :N are also possible. The two-node cluster incorporates two respective network element management systems (EMS) 1 1 , 12 in communicative contact via a network link 13. The two network element management systems 11 , 12 are arranged for communication with the same set of network elements (NE) 14 of the communications network; however, whilst in the redundant configuration, only one of the two network element management systems 1 1 , 12 communicates with the network elements 14 at any given time. It will henceforth be assumed that a first network element management system 1 1 is the primary network element management system, and a second network element management system 12 is a stand-by network element management system. The first network element management system 1 1 (primary) controls the network elements 14 in the "normal" mode of operation, but control of the network elements 14 can be switched to the second (or stand-by) network element management system 12 if required. The switchover can be carried out in a manual, controlled fashion for planned system maintenance, or can be automatic in the event of an unplanned failure of the first network element management system 1 1 (primary).

Referring to Figure 2 of the drawings, each of the two network element management systems 1 1 , 12 comprises an apparatus 30 for controlling the use of a licensed application eg 32 thereon. The apparatus 30 comprises a monitor 22 for monitoring the communication link 13. The monitoring is performed in order to determine if the first network element management 1 1 system can contact the second network element management system 12. The apparatus also has a processor 20. The processor 20 is arranged to invoke a termination procedure to disable the licensed application service 17A on the first network element management system 11 if the first network element management system 11 is unable to contact the second network element management system. In preferred embodiments the apparatus further comprises one or two timers (first timer 21 , second timer 23).

In one embodiment the elements of the apparatus 30, i.e. the processor 20, monitor 22, the first and second timers, 21 and 23 are implemented as software modules. In alternative embodiments these elements are implemented in hardware. In alternative embodiments the apparatus 30 can be implemented as a combination of hardware and software modules.

Figure 6 illustrates one embodiment of a method of controlling use of a licensed application service in a telecommunications network. The telecommunications network, as illustrated in embodiments depicted in Figures 1 and 2 comprises first and second network element management system s , wh i ch a re used for independently managing network elements of the network using licensed application services operable on these network element management systems. The network element management systems are interconnected by a communication link. The method determines, 602, if the first network element management system is able to contact the second network element management system via the communication link. If the communication is possible the method terminates and the first and second network element management systems continue to operate. If, however, the communication is not possible then a termination procedure is invoked to disable, 604, at least partially, the licensed application service on the first network element management system.

Referring to Figure 3 of the drawings, each of the two network element management systems 1 1 , 12 is associated with an identification code at step 100. At step 101 , the identification codes of the two network element management systems are sent to a remote license centre (not shown), where license files for an application service are remotely created. A license file 31 created for use with the first network element management system 1 1 contains the identification code associated with said first network element management system 1 1 ; likewise, the license file created for use with a second network element management system 12 contains the identification code associated with said second network element management system 12. The license file 31 contains licences for all the application/function/capabilities that the customer has purchased for the primary network element management system 1 1. The licence files 31 are delivered to the customer to store in respective databases 16 on the primary and secondary network element management system 1 1 , 12. The licence files contain respective fingerprints that are tied to the physical host i.e. network element management system 11 or 12.

There are two categories of license: a right-to-use license and a right-to-connect license. For the case of a right-to-use license, a license manager 15A in the network element management system 1 1 is contacted the first time the application service 17A is initiated but not contacted again thereafter. For the case of a right-to-connect license, the license manager 15A is contacted whenever the application service 17A is initiated or whenever the quantity of network elements 14 managed by the operative network element management system 1 1 or 12 is altered. The second network element management system 12 comprises corresponding license manager 15B. Accordingly, the license files for an application service with right-to-connect licensing additionally contain information on quantities such as the number of network elements 14 allowed to access the application service at any time. The present invention therefore prevents the operation of application services 17A, 17B with right-to-connect licensing on more network elements than the license permits. At step 102, the processor 20 in each network element management system 1 1 , 12 acts as a licence manager and compares the identification code associated with the network element management system 1 1 , 12 to the identification code contained within the license file 31. If the two identification codes are identical, the processor 20 enables the network element management system 1 1 , 12 to run the application service 1 7A, 17B. If, however, the two identification codes are different, the processor 20 at least partially disables the application service at step 108A. It will be appreciated that the network 10 illustrated in Figures 1 and 2 of the drawings is just one example of the way in which components such as a license manager and license database may be configured. It is also possible, for example, to configure a network such that one license manager and license database serves all network element managers within a network.

Assuming the identification codes are identical, at step 103 the processor 20 determines the set of network elements 14 that each network element management system 1 1 , 12 is operable with. It the network 10 is arranged in a redundant configuration, the first and second network element management systems 1 1 , 12 will be operable on the same set of network elements 14 (although only one network element management system will operate on the network elements 14 at any given time). Therefore, if it is discovered that the two network element management systems 1 1 , 12 are not operable on the same set of network elements 14, the processor 20 will at least partially disable the application service at step 108B.

If it is found that the first and second network element management systems 1 1 , 12 are operating on the same set of network elements 14, the monitor 22 attempts to monitor the role of the first network element management system 1 1 at step 104. The role of the first network element management system 1 1 may be one of either PRIMARY, STAND-BY or FAILED. If the step of monitoring the role of the first network element management system 1 1 is successful , the role of the second network element management system 12 is subsequently monitored at step 105. The step of monitoring of the second network element management system 12 may be affected by the same monitor 20 or by a separate monitor (not shown). Again, the role of the second network element management system 12 may be one of either PRIMARY, STAND-BY or FAILED.

Upon monitoring the roles of both, first and second, network element management systems 1 1 , 12, the two roles are compared at step 106. If it is found that both network element management systems 11 , 12 are configured as primaries, either the first network element management system 1 1 or the second network element management system 12 is reconfigured as stand-by. This ensures that only one network element management system is configured as a primary and thus the network 10 is arranged in a redundant configuration.

If either the monitoring of the first network element management system 1 1 (step

104) or the monitoring of the second network element management system 12 (step

105) is unsuccessful, there is no means by which to determine whether both network element management systems 1 1 , 12 are configured as hosts. Consequently, the potential (undetectable) violation of the terms of the license requires the initiation of a termination procedure at steps 109A or 109B.

In the case the two network element management systems are not connected for a long time there may be differences between the sets of network elements managed as network configuration can be changed during the time the two systems are separated. The configuration of a PRIMARY server can be changed by adding and removing network elements, even though this can be done as long as there are enough RTC licenses for that feature. The two network element management systems will align the network elements databases using a procedure that periodically aligns the databases as soon as the connection is up and the roles are compatible (only one server is PRIMARY). The two databases are aligned in the following way: the STAND-BY server will align its database to the PRIMARY server database, so the misalignment will only last as long as there they are disconnected and as long as they are both configured as PRIMARY servers, which is a temporary situation.

Referring to Figure 4 of the drawings, in an embodiment of the present invention, the termination procedure 109 performed at steps 109A or 109B incorporates a "grace period" in order to allow a network operator time to return the network to a configuration that is within the terms of the license. At step 1 10, the first timer 21 is initiated for measuring the disrupted monitoring time period i.e. the time period over which the monitor 22 is unable to monitor the role of the other network element management system 1 1 , 12 (i.e. either step 104 or step 105). At step 1 1 1 the network operator is alerted to the state of the network: this provides the network operator with the opportunity to reconfigure the network to a configuration within the terms of the license.

At step 1 12, continued attempts are made to monitor the role of the first network element management system 1 1 (as described in step 104) and to monitor the role of the second network element management system 12 (as described in step 105). If these attempts are successful in relation to both network element management systems 1 1 , 12 then the first timer 21 is stopped, signifying the end of the disrupted monitoring time period. If, however, the disrupted monitoring time period exceeds a first threshold value without successful monitoring of the roles of both network element management systems 1 1 , 12, the application service is at least partially disabled at step 108C. One possible benefit of allowing a grace period between the initial failure in the steps of monitoring the role of the first and second network element management systems 1 1 , 12 (steps 104 and 105) and the disabling of the application service is to give the network operator time to detect the problem and return the network to a configuration that meets the terms of the application service license. Another possible benefit is to account for the possibility that the disrupted communication between the first and second network element management systems 1 1 , 12 may be due to an intermittent fault in monitoring hardware as opposed to a deliberate reconfiguration of the network from a redundant configuration to one in which the two network element management systems operate independently. The first threshold value for the maximum allowable disrupted monitoring time period must therefore be such that in the case of major disruption, such as a failure requiring hardware replacement in an network element management system or a break in the communication link 13, the network operator is given sufficient time to order new hardware and a new license appropriate to the replacement hardware. A suggested grace period is in the region of 14 to 30 days.

If attempts to monitor the role of both the first network element management system 1 1 and the second network element management system 12 are successful before the disrupted monitoring time period exceeds the first threshold value, the second timer 23 starts measuring the stable monitoring time period i.e. the time period over which the monitor 22 is able to monitor the role of both the first and the second network element management systems 1 1 , 12. If the stable monitoring time period, i.e. a period between successive disrupted monitoring time periods, exceeds a second threshold value it is assumed that the underlying reason for the failure in the steps of monitoring the role of the first network element management system 1 1 (step 105) and/or monitoring the role of the second network element management system 12 (step 106) has been resolved and thus the disrupted monitoring time period is reset. If, however, the monitor 22 detects failure in the steps of monitoring the roles of either of the two network element management systems 1 1 , 12 (steps 105 and 106) before the stable communication period reaches the second threshold value, it is assumed that the underlying reason for the monitoring failure has not been successfully resolved and thus the first timer 21 for measuring the disrupted monitoring time period is not reset. One possible advantage of defining a stable monitoring time period is to prevent the effects associated with the connection 13 going up and down.

It will be appreciated that steps to allow a "grace period" such as those described above could also be incorporated into termination of the application service in the event of violation of other terms of the license agreement including but not limited to using the application service with network element management systems other than those for which the license was issued.

Referring to Figure 5 of the drawings, one possible method of carrying out the steps of monitoring the role of the network element management systems 11 , 12 (steps 104 and 105) is via a message exchange between the first and second network element management systems 11 , 12. Communication between the first and second network element management systems 11 , 12 may potentially take the form of Text Value Length messages sent using a secure protocol, thereby ensuring that messages are not tampered with. The first network element management system 11 periodically sends a message to the second network element management system 12. The message contains information such as: a) The role of the sender (PRIMARY, STAND-BY or FAILED);

b) The identification code of the first or second network element management system 11 , 12 (EMS A 1 1 or EMS B 12); c) The status of the connection with the network elements 14 (UP when the connection to the network elements is available, DOWN when the connection to the network elements is not available, and NONE when the network element management system is in stand-by role).

For example, the messages illustrated by numerals 1 to 6 in Figure 5 of the drawings may take the form:

1 : PRIMARY, identification code: EMS A>, UP

2: STANDBY, identification code: EMS B>, NONE

Where:

EMS A is the primary network element management system 11

EMS B is the stand-by or secondary network element management system 12

In the event that the connection between the first network element management system 11 and the network elements 14 fails, but there is still communicative contact (via link 13) between the first network element management system 11 and the second network element management system 12, the first network element management system 11 will send the message:

3: PRIMARY, identification code: EMS A>, DOWN

And EMS B will reply:

4: STAND-BY, identification code: EMS B>, NONE

Or, in the event that EMS A fails, EMS A 11 will send the message:

5: FAILED, identification code: EMS A>, NONE

And EMS B will reply with a take-over message:

6: PRIMARY, identification code: EMS B, UP

In the above example, it can be seen that the message exchange ensures that the terms of the license are not violated: if the two network element management systems 11 , 12 are in communicative contact (and thus monitoring of the roles of the two network element management systems 11 , 12 is possible) only one of the two network element management systems 1 1 , 12 is allowed to act as the primary. If, however, the two network element management systems 11 , 12 are not in communicative contact then it is not possible to simultaneously know the roles of the two network element management systems and thus a termination procedure is initiated, thereby ensuring that the two network element management systems 1 1 , 12 are not independently operating as primaries. Furthermore, the message exchange as detailed above provides a means to switch control to the stand-by network element management system 12 in the event of failure of the primary network element management system 1 1.

It will be appreciated that whilst the terms of the license demand that only one network element management system to act as primary, it is not necessary for that network element management system to own the total capacity permitted by the license. Providing the two network element management systems 1 1 , 12 are in communicative contact it is possible to allow a dynamic distribution of capacity between the two network element management systems 1 1 , 12 through the exchange of messages. For example, if the first network element management 1 1 system requires new capacity it will send a RESERVE message such as:

RESERVE, identification code: EMS A>, <capability>, <total quantity> (The italicised font in the above message indicates that the generic terms should be respectively replaced with the capability associated with the license, and the total quantity requested by the first network element management system 1 1.) For the case of on ly two network elem ent m anagem ent system s 1 1 , 12 in the telecommunications network 10 as illustrated in Figure 1 , the second network element management system 12 replies with a COMMIT message such as:

COMMIT, identification code: EMS B>, <capability>, <total quantity> The COMMIT message indicates that the capacity has been acknowledged by the second network element management system 12. As a result of this message exchange, the capacity of the first network element management system 1 1 is increased, and the capacity of the second network element management system 12 is decreased by the same amount, thereby ensuring that the total capacity remains within the terms of the license despite being split between two network element management systems 1 1 , 12. The present invention thus firstly ensures that any two network element management systems 1 1 , 12 are forced to run in a redundant configuration (i.e. only one network element management system may assume the role of primary at any time) if it is possible to monitor the roles of both network element management systems 1 1 , 12. The present invention secondly ensures that the application service is eventually d isabled if it is not possi ble to monitor the roles of both network element management systems 1 1 , 12. The combination of the above mentioned capabilities provides an effective means to prevent misuse of licensed application services for networks arranged in a redundant configuration.

Claims

1) A method of controlling the use of a licensed application service in a telecommunications network, the telecommunications network comprising first and second network element management systems for independently managing network elements of the network using respective licensed application services, wherein the network element management systems are interconnected by a communication link, the method comprising: determining if the first network element management system is able to contact the second network el ement managem ent system via said communication link; and

invoking a termination procedure for at least partially disabling the licensed application service on the first network element management system if the first network element management system is unable to contact the second network element management system via said communication link.

2) A method as claimed in claim 1 , comprising:

determining the identity of the first and second network element management systems;

determining the identity of the respective licensed application services of the first and second network element management systems;

determining from said identities whether the first and second network element management systems are each authorized to run the licensed application service; and

invoking said termination procedure for at least partially disabling the licensed application service on the first or second network element management system if at least one of the network element management systems is determined not to be authorized to run said licensed application service.

3) A method as claimed in claim 1 or 2, comprising: determining whether the first and second network element management systems are managing different network elements of the network; and invoking said termination procedure for at least partially disabling the licensed application service on the first or second network element management system if the network element management systems are determined to be managing different network elements of the network.

4) A method as claimed in any preceding claim, comprising:

monitoring a management role of the first network element management system;

monitoring a management role of the second network element management system;

determining whether the roles of the first and second network element management systems are the same; and

- reconfiguring the management role of the first or second network element management system if the network element management systems are determined to have the same roles.

5) A method as claimed in any preceding claim, in which the step of determining if the first network element management system is able to contact the second network element management system via said communication link comprises attempting to monitor the second network element management system from the first network element management system. 6) A method as claimed in any preceding claim, in which the termination procedure comprises measuring a disrupted monitoring time period over which the first network element management system is unable to contact the second network element management system via said communication link and at least partially disabling the application service if said disrupted monitoring time period exceeds a first threshold value.

7) A method as claimed in claim 6, in which the termination procedure further comprises continuing to measure the disrupted monitoring time period if the period between successive disrupted monitoring time periods is below a second threshold value. 8) An apparatus for use in an network element management system for controlling the use of a licensed application service in a telecommunications network, the telecommunications network comprising first and second network element management systems for independently managing network elements of the network using respective licensed application services, wherein the network element management systems are interconnected by a communication link, the apparatus comprising: a monitor for determining if the first network element management system is able to contact the second network element management system via said communication link; and

a processor for invoking a termination procedure for at least partially disabling the licensed application service on the first network element management system if the first network element management system is unable to contact the second network element management system via said communication link.

9) An apparatus as claimed in claim 8, in which the processor is arranged to:

determine the identity of the first and second network element management systems;

determine the identity of the respective licensed application services of the first and second network element management systems;

determine from said identities whether the first and second network element management systems are each authorized to run the licensed application service; and

- to invoke said termination procedure for at least partially disabling the licensed application service on the first or second network element management system if at least one of the network element management systems is determined not to be authorized to run said licensed application service.

10) A apparatus as claimed in claims 8 or 9, in which the processor is arranged to: determine whether the first and second network element management systems are managing different network elements of the network; and

- to invoke said termination procedure for at least partially disabling the licensed application service on the fi rst or second network element management system if the network element management systems are determined to be managing different network elements of the network.

1 1) An apparatus as claimed in any of claims 8 to 10, in which the processor is arranged to:

monitor a management role of the first network element management system; monitor a management role of the second network element management system;

determine whether the roles of the first and second network element management systems are the same; and

reconfigure the management role of the first or second network element management system if the network element management systems are determined to have the same roles. 12) An apparatus as claimed in any of claims 8 to 1 1 , in which the processor is arranged to determine if the first network element management system is able to contact the second network element management system via said communication link by attempting to monitor the second network element management system from the first network element management system.

13) An apparatus as claimed in any of claims 8 to 12, comprising a first timer, the processor being arranged to implement the termination procedure by measuring a disrupted monitoring time period over which the first network element management system is unable to contact the second network element management system via said communication link and at least partially disabling the application service if said disrupted monitoring time period exceeds a first threshold value.

14) An apparatus as claimed in claim 13, comprising a second timer, the processor being arranged to continue measuring the disrupted monitoring time period measured by the first timer if the second timer measures that a period between successive disrupted monitoring time periods is below a second threshold value.

15) A telecommunication system incorporating the apparatus of any of claims 8 to 14.