Patent Description:
Communication networks evolve constantly as capacity requirements change, operating environment changes and technology advances. When a physical change is made in the network, also network configuration in network operations system, e.g. operations support system, OSS, needs to be changed accordingly, and these changes are preferably done at the same time or nearly at the same time to ensure smooth change. In other words, on-site physical deployment work needs to be performed in synchronization with logical deployment work in network operations systems. The network operations system is a sensitive system that can be accessed and controlled only by authorized personnel. Therefore, personnel are required at the same time at the site and on the network operations system side. The physical change may relate to deployment of a new base station, replacing hardware in an existing base station, or changing physical setup in an existing base station. The changes may involve the whole base station, certain cells of the base station, or only one cell of the base station.

In conventional solutions, there is at least one first person at the site making the physical changes and a second person on network side making the logical changes in the network operations systems. The first and second persons coordinate timing of the changes with each other. In practice there may be <NUM>-<NUM> persons working at the site. <CIT> provides a method for managing configuration information of outsourced part and method and system for managing alarm.

The invention is defined in the appended independent claims, preferred embodiments are defined in the appended dependent claims.

Example embodiments of the present invention and its potential advantages are understood by referring to <FIG> of the drawings. In this document, like reference signs denote like parts or steps.

<FIG> illustrates a rough network design and deployment process for a mobile communication network. The process comprises following phases:.

The design phase <NUM> may take place for example <NUM>-<NUM> months before the deployment phase <NUM>. The pre-building phase <NUM> may take place for example <NUM>-<NUM> days before the deployment phase <NUM>. The deployment phase <NUM> may last for example <NUM>-<NUM> hours. The maintenance phase <NUM> starts when the deployment phase <NUM> is completed and continues from thereon.

Various embodiments of the invention provide automation for the deployment phase <NUM>.

<FIG> shows a conventional network deployment scenario. The scenario shows a base station <NUM> and a first person <NUM> with a mobile phone <NUM> at the site making physical changes in the base station <NUM> and/or performing physical deployment of the base station <NUM>. Further the scenario shows an operations support system, OSS, <NUM> depicting network operations systems and a second person <NUM> taking care of deployment of logical site configuration in the network operations systems. The first person <NUM> and the second person <NUM> coordinate timing of the physical and logical deployment with each other e.g. over phone. In practice, the first person <NUM> and the second person <NUM> need to be working at the same time and the second person <NUM> responsible for the deployment in network operations systems may not be able to simultaneously serve first persons at different sites. Any changes made in the network operations system <NUM> are conveyed to the physical base stations <NUM> and other network elements of the communication network and the network operates accordingly.

<FIG> shows a network deployment scenario according to an embodiment. The scenario shows a base station <NUM> and a first person <NUM> with a mobile phone <NUM> at the site making physical changes in the base station <NUM> and/or performing physical deployment of the base station <NUM>. Further the scenario shows an operations support system, OSS, <NUM> depicting network operations systems. Still further the scenario shows an automation system <NUM> and a design system <NUM>. The design system <NUM>, the automation system <NUM> and the network operations system <NUM> are communicatively connected to each other. The automation system <NUM> provides automatic deployment of logical site configuration in the network operations systems <NUM>. Any changes in the network operations system <NUM> are conveyed to the physical base stations <NUM> and other network elements of the communication network and the network operates accordingly.

The automation system is operable to obtain relevant network configuration from the design system <NUM>. Additionally or alternatively, the automation system may operable to trigger the design system <NUM> to automatically generate and/or update the relevant network configuration. The automation system <NUM> and the design system <NUM> may be different physical elements or logical elements executed in the same computer hardware. The first person <NUM> at the site interacts with the automation system <NUM> via a suitable user interface. The interface may be implemented for example as a web interface or as part of an application running in the mobile phone <NUM> of the first person <NUM>. The web interface may be implemented in the same device with the automation system or there may be physically and/or logically separate server providing the web interface. The interface may implement suitable access control.

<FIG> shows a flow diagram illustrating example methods according to certain embodiments. The shown flow diagram incorporates plurality of embodiments and may be split into parts. The order of phases conducted in the flow chart may be changed expect where otherwise explicitly defined. Furthermore, it is to be noted that performing all phases of the flow chart is not mandatory.

The methods of <FIG> are implemented in the automation system <NUM> of <FIG>. In general, the methods are implemented in a computer and do not require human interaction. It is to be noted that the methods are triggered by a human action and may provide output that may be further processed by humans.

The flow chart of <FIG> comprises following phases:
Phase <NUM>: Deployment of a target item is initialized. The target item comprises the base station <NUM> or one or more cells of the base station <NUM>. In an example embodiment the first person <NUM> at the site triggers the initialization and sends to the automation system <NUM> an initialization request (e.g. through a user interface). Alternatively, some other person may send the initialization request to the automation system <NUM>. The initialization request comprises identification of the target item. Additionally, the initialization request may identify time frame for the actual deployment. For example, deployments scheduled for certain day may be initialized in the morning of that day, or the deployments scheduled for certain week may be initialized in the beginning of the week.

The initialization request may additionally comprise identification of associated work definition. The work definition comprises information about the physical change that is being made. The work definition may be for example one of the following: deployment of new base station, replacement of existing hardware, changing existing hardware to newer technology, any combination of the foregoing.

Phase <NUM>: Responsive to the initialization request, the automation system <NUM> triggers updating a previously generated new configuration for the target item. Alternatively, the automation system <NUM> may trigger automatic generation of a new configuration for the target item. The new configuration may be updated or generated right after receiving the initialization request or the updating or generating may be scheduled for a later time. It may be defined for example that the new configuration will be updated or generated the same day the deployment takes place, e.g. few hours before the deployment. The new configuration may be updated automatically or manually and the updating may take place in the design system <NUM>. By updating or even generating the new configuration relatively close to the actual deployment, it is possible to take into account network changes that may have taken place after the pre-building phase. For example, neighbor relations in the new configuration may be updated to reflect up to date situation in the network. A freshly generated configuration clearly takes into account up to date situation in the network.

Phase <NUM>: The deployment is started. In an example embodiment the first person <NUM> at the site triggers the deployment and sends to the automation system <NUM> a request to start deployment (e.g. through the user interface). According to the invention the request to start deployment comprises identification of the target item and the work definition. The work definition comprises information about the physical change that is being made. The work definition may be for example one of the following: deployment of a new base station, replacement of existing hardware, changing existing hardware to newer technology, any combination of the foregoing.

It is to be noted that it is not mandatory to convey the work definition both in the initialization request and the request to start deployment. One of these may suffice.

Responsive to the request to start deployment the automation system <NUM> starts a process corresponding to the work definition. In an embodiment there is a data storage comprising process description for different work definitions and the automation system may fetch the process description form such data storage.

Phase <NUM>: The target item is deactivated in a controlled manner in case the target item is in use. After deactivation, a notification of completion of the deactivation phase may be conveyed to the first person <NUM> through the user interface or through some other communication means. After receiving the notification, the first person <NUM> may proceed to physically plugging off the target item and performing the physical changes in the target item without causing unexpected problems in user connections in the network.

The deactivation refers to a controlled shut down or locking of the target item (e.g. cell or base station) in the network operations system. The deactivation is so called merciful deactivation, wherein the network operations system moves any users that are being served by the target item to other base stations and cells of the network in a controlled manner. Calls and data connections of the users are moved and after deactivation the deactivated target item does not accept new users (that is, new calls or data connections). After deactivation it is possible to unplug power from the target item without causing disturbance to users of the communication network. Activation is the reverse action wherein the target item is brought up or opened in a controlled manner in the network operations system. After activation, the target item is in normal operating mode and accepts new users (that is, new calls or data connections).

Phase <NUM>: Any already existing configuration concerning the target item is deleted from the network operations systems. By completely deleting the configuration concerning the target item, the updated or generated new configuration for the target item can be built into the network operations system from scratch. In this way, complex changes in existing network configurations are not needed.

It is to be noted that phases <NUM> and <NUM> are not always mandatory. For example, if a completely new base station is deployed, these phases may not be needed.

Phase <NUM>: New configuration for the target item is fetched to the automation system <NUM> from the design system <NUM>. It is to be noted that this phase may be executed already in connection with phase <NUM> or <NUM>. Alternatively the generating or updating the new configuration of phase <NUM> may be implemented in this phase <NUM>, i.e. just before taking the new configuration into use in phase <NUM>.

Phase <NUM>: The new configuration for the target item is validated against design rules. The design rules may for example define certain preferred value ranges for one or more parameters of the configuration. For example, a parameter value may be in the range <NUM>. <NUM> but not <NUM> or <NUM> or <NUM>. If the configuration comprises values that are outside these ranges, an alert may be raised, and the deployment phase may be stopped until the values are fixed. It is to be noted that this phase may be executed already in connection with phase <NUM> or <NUM>. By performing the validation phase before deploying the new configuration in the network operations systems, it is possible to identify in advance such parameter values (if any) of the new configuration that may cause problems in network operation. In an alternative implementation the validation of phase <NUM> may be performed in connection with generating or updating the new configuration in phase <NUM>. Alternatively the generating or updating the new configuration of phase <NUM> may be implemented in this phase <NUM>, i.e. just before taking the new configuration into use in phase <NUM>.

By generating or updating the new configuration in the deployment phase just before taking the new configuration into use, one achieves the benefit of having the new configuration designed based on fresh view on the situation in the network. In this way up to date e.g. neighbor settings and other parameters depending on surrounding network configuration may be defined to correspond to up to date situation.

Phase <NUM>: The parameter values of the new configuration are deployed into the network operations systems (e.g. OSS) and the target item may be activated. In an embodiment, execution of this phase requires confirmation of that the physical changes at the site have been successfully completed and that the target item is ready for being physically plugged in and taken into use.

Phase <NUM>: The deployment on the network side is ready and completion of the deployment is reported. A notification of completion of the deployment may be conveyed to the first person <NUM> through the user interface or through some other communication means. After receiving the notification, the first person <NUM> may proceed to physically plugging in the target item. This phase may comprise reporting the parameter values that were deployed in the network enabling further check of the values to be made.

The methods of <FIG> provide that the first person <NUM> at the site is free to choose timing of the deployment without needing to coordinate the timing with the second person <NUM> of <FIG>.

<FIG> shows an apparatus <NUM> according to an embodiment. The apparatus <NUM> is for example a general-purpose computer or server or some other electronic data processing apparatus. The apparatus <NUM> can be used for implementing embodiments of the invention. That is, with suitable configuration the apparatus <NUM> is suited for operating for example as the automation system <NUM> of the foregoing disclosure.

The general structure of the apparatus <NUM> comprises a processor <NUM>, and a memory <NUM> coupled to the processor <NUM>. The apparatus <NUM> further comprises software <NUM> and database <NUM> stored in the memory <NUM> and operable to be loaded into and executed in the processor <NUM>. The software <NUM> may comprise one or more software modules and can be in the form of a computer program product. The database <NUM> may be usable for storing e.g. rules and patterns for use in data analysis. Further, the apparatus <NUM> comprises a communication interface <NUM> coupled to the processor <NUM>.

The processor <NUM> may comprise, e.g., a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a graphics processing unit, or the like. <FIG> shows one processor <NUM>, but the apparatus <NUM> may comprise a plurality of processors.

The memory <NUM> may be for example a non-volatile or a volatile memory, such as a read-only memory (ROM), a programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), a random-access memory (RAM), a flash memory, a data disk, an optical storage, a magnetic storage, a smart card, or the like. The apparatus <NUM> may comprise a plurality of memories. The memory <NUM> may be constructed as a part of the apparatus <NUM> or it may be inserted into a slot, port, or the like of the apparatus <NUM> by a user.

The communication interface <NUM> may comprise communication modules that implement data transmission to and from the apparatus <NUM>. The communication modules may comprise, e.g., a wireless or a wired interface module. The wireless interface may comprise such as a WLAN, Bluetooth, infrared (IR), radio frequency identification (RF ID), GSM/GPRS, CDMA, WCDMA, or LTE (Long Term Evolution) radio module. The wired interface may comprise such as Ethernet or universal serial bus (USB), for example. Further the apparatus <NUM> may comprise a user interface (not shown) for providing interaction with a user of the apparatus. The user interface may comprise a display and a keyboard, for example. The user interaction may be implemented through the communication interface <NUM>, too.

The database <NUM> may be certain memory area in the memory <NUM> or alternatively the database <NUM> may be a separate component or the database <NUM> may be located in a physically separate database server that is accessed for example through the communication unit <NUM>. The database unit <NUM> may be a relational (SQL) or a non-relational (NoSQL) database.

A skilled person appreciates that in addition to the elements shown in <FIG>, the apparatus <NUM> may comprise other elements, such as microphones, displays, as well as additional circuitry such as memory chips, application-specific integrated circuits (ASIC), other processing circuitry for specific purposes and the like. Further, it is noted that only one apparatus is shown in <FIG>, but the embodiments of the invention may equally be implemented in a cluster of shown apparatuses.

Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is resource savings. Both human resources and time can be saved as network deployment tasks are automated and human actions are needed only in rare cases.

Another technical effect of one or more of the example embodiments disclosed herein is that improved quality may be achieved. Human errors are reduced as actions are automated and sanity check performed for the site configuration prior to deployment further improves quality. Scheduling configuration update close to the deployment enables that the parameter values that will be deployed reflect up to date situation in the network.

Another technical effect of one or more of the example embodiments disclosed herein is enabling more freedom in timing of performing the physical changes at the site. The automation system on the network side may be always available.

Another technical effect of one or more of the example embodiments disclosed herein is that by removing any existing configuration and performing the deployment from the scratch failures in the automated deployment can be minimized.

Claim 1:
A computer implemented method for automated configuration deployment in network operations systems (<NUM>) of a communication network, the method performed in an automation system, the method comprising
receiving a start deployment request (<NUM>), wherein the start deployment request comprises identification of a target item (<NUM>) and a work definition, wherein the work definition comprises information about a physical change that is being made in the communication network;
responsive to the start deployment request, starting a process corresponding to the work definition;
deleting (<NUM>) from the network operations systems (<NUM>) any already existing configuration concerning the target item (<NUM>);
fetching (<NUM>) a new configuration for the target item (<NUM>) from a design system; and
deploying (<NUM>) the new configuration in the network operations systems (<NUM>).