WO2014090307A1 - Method of operating a communication network - Google Patents

Method of operating a communication network Download PDF

Info

Publication number
WO2014090307A1
WO2014090307A1 PCT/EP2012/075367 EP2012075367W WO2014090307A1 WO 2014090307 A1 WO2014090307 A1 WO 2014090307A1 EP 2012075367 W EP2012075367 W EP 2012075367W WO 2014090307 A1 WO2014090307 A1 WO 2014090307A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication network
specific
properties
network element
abstracted
Prior art date
Application number
PCT/EP2012/075367
Other languages
French (fr)
Inventor
Haitao Tang
Seppo Olavi HAMALAINEN
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2012/075367 priority Critical patent/WO2014090307A1/en
Publication of WO2014090307A1 publication Critical patent/WO2014090307A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/02Arrangements for optimising operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0226Mapping or translating multiple network management protocols

Definitions

  • the present invention relates to the field of methods of operating a communication network, in particular a mobile communication network comprising managed communication network elements and managing communication elements.
  • the invention relates to a mapping module. Moreover, the invention relates to a program element, and a computer-readable medium.
  • the management of a communication network typically has to consider specifics of the entities, elements or devices used in the communication network.
  • the management is some kind of vendor specific.
  • their parameters, their semantics, their related network functions, and their related network operation methods are usually specific to the vendor (s) of the communication network and, are possibly also specific to the specific product release of the same vendor.
  • CSP communication service provider
  • 3GPP specifies detailed parameters (usually specific to a specific release) and values of the
  • a method of operating a communication network e.g. a managed communication network element and/or a managing communication network element, which may enable an efficient and easy operating of a heterogeneous communication network.
  • a method of operating a communication network comprising at least a first
  • the first communication network element may be a managed entity, i.e. a communication network element which is managed by another communication network element, e.g. the second communication network element.
  • the first communication network element may be a mobile phone, PDA or laptop having vendor and/or release specific network properties, a base station or relay station having vendor and/or specific network properties.
  • the second communication network element may be a managed entity, i.e. a communication network element which is managed by another communication network element, e.g. the second communication network element.
  • the first communication network element may be a mobile phone, PDA or laptop having vendor and/or release specific network properties, a base station or relay station having vendor and/or specific network properties.
  • the communication network element may be a managing entity, i.e. a communication network element which is managing another or a plurality of other communication network element.
  • the first communication network element may be a managing entity while the second communication network element may be a managed communication network element .
  • a method of operating a communication network comprising at least a first
  • the method comprises instructing the first communication network element by sending abstracted network properties which are common for a plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements; and mapping the abstracted network properties to specific network properties which are specific to the first
  • mapping may be performed by the first communication network element or the second communication network element.
  • mapping may be performed by a dedicated third communication network element, e.g. a communication network element or entity which comprises or forms a mapping module.
  • sending of the abstracted network properties may be directly from the second to the first communication network element or may be indirectly, e.g. via a third
  • the sent abstracted network properties may relate to a specific function requested to be performed by the first communication network element.
  • mapping module for a communication network, wherein the mapping module is adapted to map abstracted network properties of communication network entities, wherein the abstracted network properties are common for a plurality of
  • mapping module may be adapted to perform the mapping in both directions, i.e. starting with the abstracted network properties and outputting the specific network properties and/or the associated specific
  • mapping module may be implemented by hardware module, e.g. comprising a processing unit adapted to perform the specific functions of the mapping module, or may be implemented by a dedicated software module which may be loaded into a processing unit. Even a hybrid mapping module is possible including both hardware and software modules or components.
  • mapping module may be defined by a vendor according to abstracted or common interface
  • mapping module may be adapted or may be able to map between the common interface procedures of network operation and the vendor/release-specific interface procedures of network operation.
  • the mapping may be performed as an one-to-one mapping, one-to-many mapping, or many-to-many mapping, depending on the specific mapping needs. That is, the mapping module may map the common interface procedures between the vendor/release-specific procedures with the information elements represented by the vendor/release- specific network properties (e.g., vendor-specific network parameters and function properties) .
  • the vendor/release-specific network properties e.g., vendor-specific network parameters and function properties
  • a program element which, when being executed by a processor, is adapted to control or carry out a method according to an exemplary aspect.
  • a computer-readable medium in which a computer program is stored which, when being executed by a processor, is adapted to control or carry out a method according to an exemplary aspect.
  • network element and “network entities” may be used interchangeably.
  • abstract network properties may in particular denote properties of a communication network element which are common for a plurality or all communication network elements of the communication network. These abstracted network properties may particularly describe and/or define the properties, functions, operation parameters and/or the values associated with the respective operation parameters, of the plurality or all communication network elements of the communication network.
  • specific network properties may in particular denote properties of a communication network element which are specific for a communication network element of the communication network. These specific network properties may particularly describe and/or define the properties, functions, operation parameters and/or the values
  • the specific network properties may be different for
  • information element may particularly denote data which are describing or relating to a specific parameter or function defining a network property.
  • an information element may be formed by the data indicating a value of a given parameter.
  • Examples for an information element may be data defining the coverage or capacity of a cell, the size of the cell, a set of predefined user classes and so on.
  • a managing entity e.g. a communication service provider (CSP) .
  • CSP communication service provider
  • an integrator e.g. the CSP
  • An advantage of the method may be the possibility to avoid exchange of detailed configuration/management info between communication network elements. Instead, general properties may be transferred and interpreted locally to detailed parameters.
  • the respective method may be made as a vendor specific, proprietary solution, where the products of the vendors may benefit through product differentiation.
  • the method may also be standardized (e.g. in 3GPP SA5) . In this case achieved benefit may come through flexibility and possibility to leave vendor specifics as detailed
  • a gist of an exemplary aspect may be seen in the fact that a method of operating a communication network or a
  • communication network entity or element which can be used in a heterogeneous communication network, i.e. a communication network comprising a plurality of different network elements or entities having different often vendor and/or release specific network properties.
  • a heterogeneous communication network i.e. a communication network comprising a plurality of different network elements or entities having different often vendor and/or release specific network properties.
  • These specific network properties may correspond to different parameters and/or functions and can be described by specific
  • these specific network properties and/or the corresponding specific information may be mapped to abstracted network properties and/or to corresponding abstracted information elements which are common or understandable by the
  • the communication service provider may be able to manage the communication network as long as all relevant communication network elements can interpret and/or process the respective abstracted network properties and/or the corresponding abstracted information elements.
  • the abstracted network properties may include abstracted parameters and abstracted function properties that are common to all the different network elements or entities of different vendors and/or releases being present in the managed communication network.
  • the gist of an exemplary aspect may be seen in providing a method of operating a communication network comprising a plurality of communication network elements.
  • the method comprises the basic step of mapping between abstracted network properties which are common for the plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements to specific network properties which are specific to one of the plurality of communication network elements and which are described by information elements specific to the one of the communication network elements. According to this method it is possible to transmit the abstracted and/or the specific network properties between different communication network elements.
  • the specific network properties are described by information elements .
  • the information elements may be parameters or values of parameters which are relevant for defining or representing a corresponding or associated network
  • the mapping is performed by a mapping module.
  • the mapping module may be implemented in the first communication network element.
  • the mapping module may be implemented in a third communication network element.
  • the third communication network element may be a radio network controller or a vendor specific element manager, for example.
  • the sending is performed through common interface procedures.
  • common interface procedures may particularly denote interface procedures which are common for a
  • common interface procedures may be procedures which are defined in a communication standard or which are at least common for the plurality of communication network elements.
  • the mapping may be performed by the first communication network element .
  • mapping may be p rformed as well by the second communication network element
  • the first communication network element may be a managed entity of the communication network.
  • mapping is performed by a third communication network element .
  • the third communication network element may be a communication network element dedicated or
  • the third communication network element may comprise a mapping module which may be formed by a dedicated software or hardware component.
  • a mapping module may comprise a mapping table linking the specific network property and the respective abstracted network property.
  • communication network element may be implemented in the first or second communication network element as a specific component or module.
  • mapping is performed by the third communication network element and further comprising the step of sending the information elements specific to the first communication network element to the first communication network element.
  • the third communication network element may comprise a mapping module.
  • the abstracted network properties relate to at least one item selected out of the group consisting of: Cell, Processing, Radiolnterface, Peerlnterface, Backhaullnterface,
  • Summarizing an exemplary aspect may relate to a
  • vendor/release-independent network operation method which may allow a network operator or communication service provider to properly operate its communication network (e.g., cellular network) with the procedures using the information elements represented by a set of abstracted or common network properties (e.g., abstracted network
  • the operated network may be built with network entities or elements from
  • An update to the communication network e.g., adding new network
  • mapping module may be done seamlessly without change to the network operation.
  • the communication service provider or operator only needs to add/update the corresponding mapping module.
  • vendor/release-independent network operation method the method works as the following:
  • the element (usually vendor/release specific) can notify the vendor/release-independent manager or second communication network element concerning certain network status.
  • this notification may be performed through operation procedure (s) (usually vendor/release specific) with the relevant information elements represented by its specific or own network properties (usually vendor/release specific).
  • the corresponding mapping module associated with the first communication network element will map the entity-specific notification, into the notification ( s ) of the abstracted or common interface procedure ( s ) , where the information elements specific to the managed entity are mapped into the information elements represented by the set of common network properties.
  • the vendor/release-independent manager or second communication network element receives the mapped notification ( s ) that are fully understood by the manager .
  • the manager sends the instruction to the corresponding mapping module of the managed entity through common or abstracted interface procedure (s) with the information elements represented by the set of common network properties.
  • the corresponding mapping module will map the instruction into the entity-specific instruction ( s ) and then send it/they to the managed entity through the entity-specific procedure (s) with the information elements specific to the managed entity.
  • the managed entity receives the mapped instruction ( s ) that are fully understood by the managed entity.
  • OAM operation, administration and maintenance
  • Fig. 1 shows schematically a vendor/release independent network operation by a network manager
  • Fig. 2 shows schematically an exemplary method of operating a communication network comprising at least a first
  • common interface procedures may denote any procedures used when communication between different communication network elements is performed during operation of a communication network or when using a communication network entity in a communication network, which are common for different communication network entities, e.g. communication network entities of different releases or vendors.
  • common interface procedures may be procedures which are necessarily
  • a common interface procedure may relate to information concerning the element coverage, a size of the cell corresponding to a specific base station or mobile phone, a global cell ID, a radio mode, a cell status, or the like.
  • ⁇ > denotes an optional element, e.g., in a
  • a defined property can be used for the definition of a latter property, with
  • CellularNetwork (a set of Cells, Processing,
  • RadioMode RadioNature, RelatedCell, QoSClass
  • cell may be a network property which is defined by information elements, i.e. the values of: GlobalCelllD, CellPurpose, CellSize, RadioMode,
  • RadioNature, RelatedCell, QoSClass, UserClass, CellStatus RadioNature, RelatedCell, QoSClass, UserClass, CellStatus.
  • RadioMode OmniDirectional
  • 2DGeoLocation a two-dimension location represented with the coordinates based on a datum (e.g., UTM or WGS84) that describe this earth
  • 3DGeoLocation a three-dimension location represented with the coordinates based on a datum (e.g., UTM or WGS84) that describe this earth
  • the heading degrees are determined based on the
  • RadioNature interferenceLimited
  • noiseLimited
  • RelatedCell list of (globalCelllD of a related cell, CellRelation with this cell)
  • CampEachOther CampFromNeighbor &
  • QoSClass a set of traffic QoS classes that this cell supports
  • QoSClass CellStatus InterfaceLoad
  • RadiolnterfaceLoad ( % of the capacity used) I (zero, small, medium, or large part of the capacity used)
  • PeerlnterfaceLoad ( % of the capacity used) I (zero, small, medium, or large part of the capacity used)
  • Radiolnterface All radio interfaces logically connecting the cell and its related user devices
  • Peerlnterface All interfaces logically connecting the cell and its neighboring or related cells
  • RadioModeUpdate OmniDirectional
  • RadioNatureUpdate interferenceLimited
  • QoSClassUpdate a set of traffic QoS classes that this cell supports
  • UserClassUpdate a set of user classes that this cell supports, where a user class has none traffic QoS class that is not defined by QoSClass and not selected by QoSClassUpdate
  • CellStatusUpdate CellState
  • CellReport CellStatus
  • IdleMobilityUpdate MoreDifficultCampIn
  • AccessDirect AmountOf ( ⁇ QoSClass>, ⁇ UserClass>) go from ⁇ SourceCell> to ( TargetCell
  • o TargetNetwork CellularNetwork
  • the traffic steering settings are any settings define the actual traffic steering state, which could also be "no traffic steering” where the traffic steering is disabled
  • CellularNetworkOAM a logical OAM entity that manages a CellularNetwork
  • Fig. 1 shows schematically a vendor/release independent network operation by a network manager.
  • Fig. 1 shows schematically part of a communication network 100 comprising a plurality of managed entities or elements 101, 102 and 103.
  • the different managed entities may be vendor and/or release specific.
  • a mapping module is provided for each of the managed entities.
  • Fig. 1 schematically shows three mapping modules 104, 105 and 106 including a mapping scheme or mapping table one mapping module may be associated to a plurality of identical managed entities.
  • the mapping modules performs mapping between abstracted properties and vendor and/or release specific properties.
  • the managed entities communicate with their corresponding or associated mapping modules via a vendor and/or release specific network operation or network procedure.
  • the mapping modules 104, 105 and 106 are commonly connected, via an OAM interface defined with a set of abstracted properties common for all vendors and
  • a vendor and/or release independent network operation may be provided.
  • the method proposes to define an OAM interface with a set of common interface procedures and a set of common network properties (e.g., abstracted
  • This interface serves an OAM manager with a set of common interface procedures using the information elements represented by the set of common network
  • Fig. 2 shows schematically an exemplary method of operating a communication network comprising at least a first
  • box 202 there may be performed notifying the second communication network element of the specific network properties of the first communication network element by sending the mapped abstracted network properties to the second communication network element.
  • the CSP may lack knowledge of the vendor/release-specific parameters and their related network functions and operation relating to the
  • a method is provided to prevent such difficulty of network operation.
  • the method is to allow the CSP to operate the network with a set of abstracted network properties including abstracted parameters and abstracted function properties that are common to all the different network entities of different vendors and releases.
  • the CSP or the communication network elements understands all the abstracted parameters, the abstracted function properties, and their operation.
  • the vendor/release-specific network elements or entities may thus be operated as what the CSP has expected, via mapping between the abstracted network properties and the vendor/release-specific network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Amethod of operating a communication network comprising at least a first communicationnetwork element and a second communication network element is provided, wherein the method comprises mapping specific network properties which are described by information elements to abstracted network properties which are common for a plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements; and notifying the second communication network element of the specific network properties of the first communication network element by sending the mapped abstracted network properties to the second communication network element. Fig.

Description

DESCRIPTION Method of operating a communication network
Field of invention
The present invention relates to the field of methods of operating a communication network, in particular a mobile communication network comprising managed communication network elements and managing communication elements.
Furthermore, the invention relates to a mapping module. Moreover, the invention relates to a program element, and a computer-readable medium.
Art Background
The management of a communication network, such as a cellular network, typically has to consider specifics of the entities, elements or devices used in the communication network. Thus, the management is some kind of vendor specific. For example, their parameters, their semantics, their related network functions, and their related network operation methods are usually specific to the vendor (s) of the communication network and, are possibly also specific to the specific product release of the same vendor. This typically creates a big burden for a communication service provider (CSP) to operate a network where its network entities are from multiple vendors and/or concerning multiple product releases (e.g., LTE Release 8, 9, 10..., different vendor product releases, management of LTE or HSPA software versions executed ever multi-radio
platforms) .
For example, 3GPP specifies detailed parameters (usually specific to a specific release) and values of the
respective parameters that can be exchanged between domain managers and network managers. Even so, many of them are left for specific vendor/operator to determine their specific semantics and specific ways of usage.
Thus, there may be a need to provide a method of operating a communication network, e.g. a managed communication network element and/or a managing communication network element, which may enable an efficient and easy operating of a heterogeneous communication network.
Summary of the Invention
This need may be met by a method of operating a
communication network, a mapping module, a communication network, a program element, and a computer-readable medium according to the independent claims. Advantageous
embodiments of the present invention are described by the dependent claims.
According to an exemplary aspect a method of operating a communication network comprising at least a first
communication network element and a second communication network element is provided, wherein the method comprises mapping specific network properties which are specific to the first communication network element and which are described by information elements specific to the first communication network element to abstracted network
properties which are common for a plurality of
communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements; and notifying the second communication network element of the specific network properties of the first communication network element by sending the mapped abstracted network properties to the second communication network element.
The first communication network element may be a managed entity, i.e. a communication network element which is managed by another communication network element, e.g. the second communication network element. For example the first communication network element may be a mobile phone, PDA or laptop having vendor and/or release specific network properties, a base station or relay station having vendor and/or specific network properties. The second
communication network element may be a managing entity, i.e. a communication network element which is managing another or a plurality of other communication network element. However, the first communication network element may be a managing entity while the second communication network element may be a managed communication network element .
According to an exemplary aspect a method of operating a communication network comprising at least a first
communication network element and a second communication network element is provided, wherein the method comprises instructing the first communication network element by sending abstracted network properties which are common for a plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements; and mapping the abstracted network properties to specific network properties which are specific to the first
communication network element and which are described by information elements specific to the first communication network element.
In particular, the mapping may be performed by the first communication network element or the second communication network element. Alternatively or additionally the mapping may be performed by a dedicated third communication network element, e.g. a communication network element or entity which comprises or forms a mapping module. In particular, the sending of the abstracted network properties may be directly from the second to the first communication network element or may be indirectly, e.g. via a third
communication network element.
In particular, the sent abstracted network properties may relate to a specific function requested to be performed by the first communication network element.
According to an exemplary aspect a mapping module for a communication network is provided, wherein the mapping module is adapted to map abstracted network properties of communication network entities, wherein the abstracted network properties are common for a plurality of
communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements, with specific network properties, wherein the specific network properties are specific for a communication network element and which are described by specific information elements which are specific for the communication network element.
In particular, the mapping module may be adapted to perform the mapping in both directions, i.e. starting with the abstracted network properties and outputting the specific network properties and/or the associated specific
information elements or the other way around, i.e. starting with the specific network properties and outputting the abstracted network properties and/or the associated
abstracted information elements.
In particular, the mapping module may be implemented by hardware module, e.g. comprising a processing unit adapted to perform the specific functions of the mapping module, or may be implemented by a dedicated software module which may be loaded into a processing unit. Even a hybrid mapping module is possible including both hardware and software modules or components.
In particular, the mapping module may be defined by a vendor according to abstracted or common interface
procedures and abstracted or common network properties. In particular, the mapping module may be adapted or may be able to map between the common interface procedures of network operation and the vendor/release-specific interface procedures of network operation. According to some
exemplary embodiments the mapping may be performed as an one-to-one mapping, one-to-many mapping, or many-to-many mapping, depending on the specific mapping needs. That is, the mapping module may map the common interface procedures between the vendor/release-specific procedures with the information elements represented by the vendor/release- specific network properties (e.g., vendor-specific network parameters and function properties) .
According to an exemplary aspect a program element is provided, which, when being executed by a processor, is adapted to control or carry out a method according to an exemplary aspect.
According to an exemplary aspect a computer-readable medium, in which a computer program is stored which, when being executed by a processor, is adapted to control or carry out a method according to an exemplary aspect.
Throughout this description the terms "network element" and "network entities" may be used interchangeably.
The term "abstracted network properties" may in particular denote properties of a communication network element which are common for a plurality or all communication network elements of the communication network. These abstracted network properties may particularly describe and/or define the properties, functions, operation parameters and/or the values associated with the respective operation parameters, of the plurality or all communication network elements of the communication network.
The term "specific network properties" may in particular denote properties of a communication network element which are specific for a communication network element of the communication network. These specific network properties may particularly describe and/or define the properties, functions, operation parameters and/or the values
associated with the respective operation parameters, of a specific communication network element. In particular, the specific network properties may be different for
communication network elements of different vendors or even different for different releases of communication network elements of the same vendor.
The term "information element" may particularly denote data which are describing or relating to a specific parameter or function defining a network property. In particular an information element may be formed by the data indicating a value of a given parameter. Examples for an information element may be data defining the coverage or capacity of a cell, the size of the cell, a set of predefined user classes and so on.
By using the method according to an exemplary aspect it may be possible to enable an efficient and easy operating or managing of a heterogeneous communication network. In particular, it may be possible to still enable that
specific integration for low level parameters are made at a first communication network element or entity while at a high level or abstracted level abstracted network
properties or parameters defining abstracted network properties are used, which may be understandable or
interpretable by a managing entity, e.g. a communication service provider (CSP) . Thus, it may be possible to omit the necessity that the special integration is provided to the managing entity on a case by case basis which would be time consuming and expensive. In addition, it may be avoidable that an integrator, e.g. the CSP, needs to have the complete information of the specific parameters and properties of all of the different communication network elements of the communication network he manages, which network elements are to be integrated, which would be often an expensive or even not feasible requirement. An advantage of the method may be the possibility to avoid exchange of detailed configuration/management info between communication network elements. Instead, general properties may be transferred and interpreted locally to detailed parameters. The respective method may be made as a vendor specific, proprietary solution, where the products of the vendors may benefit through product differentiation. The method may also be standardized (e.g. in 3GPP SA5) . In this case achieved benefit may come through flexibility and possibility to leave vendor specifics as detailed
parameters that are not standardized. Therefore vendor may still use own set of parameters for their own purposes, while interface would make them or their corresponding properties understandable to any CSP operator. A gist of an exemplary aspect may be seen in the fact that a method of operating a communication network or a
communication network entity or element is provided which can be used in a heterogeneous communication network, i.e. a communication network comprising a plurality of different network elements or entities having different often vendor and/or release specific network properties. These specific network properties may correspond to different parameters and/or functions and can be described by specific
information elements. According to the exemplary aspect these specific network properties and/or the corresponding specific information may be mapped to abstracted network properties and/or to corresponding abstracted information elements which are common or understandable by the
different types of network elements of the heterogeneous communication network. Thus, it may be possible for a communication service provider to manage the heterogeneous communication network even without detailed knowledge of the specific network properties of the network elements or entities. In particular, the communication service provider may be able to manage the communication network as long as all relevant communication network elements can interpret and/or process the respective abstracted network properties and/or the corresponding abstracted information elements. In particular, the abstracted network properties may include abstracted parameters and abstracted function properties that are common to all the different network elements or entities of different vendors and/or releases being present in the managed communication network.
In another formulation the gist of an exemplary aspect may be seen in providing a method of operating a communication network comprising a plurality of communication network elements. The method comprises the basic step of mapping between abstracted network properties which are common for the plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements to specific network properties which are specific to one of the plurality of communication network elements and which are described by information elements specific to the one of the communication network elements. According to this method it is possible to transmit the abstracted and/or the specific network properties between different communication network elements.
Next, further exemplary embodiments of the method of operating a communication network are described. However, these embodiments also apply to the mapping module, the program element, and the computer-readable medium.
According to an exemplary embodiment of the method the specific network properties are described by information elements .
In particular, the information elements may be parameters or values of parameters which are relevant for defining or representing a corresponding or associated network
property, in particular of the first communication network entity.
According to an exemplary embodiment of the method the mapping is performed by a mapping module. In particular, the mapping module may be implemented in the first communication network element. However, the mapping module may be implemented in a third communication network element. The third communication network element may be a radio network controller or a vendor specific element manager, for example. According to an exemplary embodiment of the method the sending is performed through common interface procedures.
The term "common interface procedures" may particularly denote interface procedures which are common for a
plurality of communication network elements and which may in particular not specific for a specific vendor and/or release of a communication network element. That is, common interface procedures may be procedures which are defined in a communication standard or which are at least common for the plurality of communication network elements.
According to an exemplary embodiment of the method the mapping may be performed by the first communication network element .
However, the mapping may be p rformed as well by the second communication network element In particular, the first communication network element may be a managed entity of the communication network.
According to an exemplary embodiment of the method the mapping is performed by a third communication network element .
In particular, the third communication network element may be a communication network element dedicated or
specifically adapted to perform the mapping. For example, the third communication network element may comprise a mapping module which may be formed by a dedicated software or hardware component. In particular, such a mapping module may comprise a mapping table linking the specific network property and the respective abstracted network property. However, it should be mentioned that the third
communication network element may be implemented in the first or second communication network element as a specific component or module.
According to an exemplary embodiment of the method the abstracted network properties are sent to a third
communication network element.
According to an exemplary embodiment of the method the mapping is performed by the third communication network element and further comprising the step of sending the information elements specific to the first communication network element to the first communication network element.
In particular, the third communication network element may comprise a mapping module. According to an exemplary embodiment of the method the abstracted network properties relate to at least one item selected out of the group consisting of: Cell, Processing, Radiolnterface, Peerlnterface, Backhaullnterface,
CellUpdate, CellReport, HandoverUpdate, IdleMobilityUpdate, LoadBalacingUpdate, TrafficSteeringUpdate,
RequestForOperation, NotificationOfOperation, and
DesicionOnOperation .
Summarizing an exemplary aspect may relate to a
vendor/release-independent network operation method which may allow a network operator or communication service provider to properly operate its communication network (e.g., cellular network) with the procedures using the information elements represented by a set of abstracted or common network properties (e.g., abstracted network
parameters and function properties) . The operated network may be built with network entities or elements from
different vendors and their product releases. An update to the communication network (e.g., adding new network
entities, release upgrade, etc.) may be done seamlessly without change to the network operation. The communication service provider or operator only needs to add/update the corresponding mapping module.
According to a specific implementation of the
vendor/release-independent network operation method the method works as the following:
• A managed entity or first communication network
element (usually vendor/release specific) can notify the vendor/release-independent manager or second communication network element concerning certain network status. In particular this notification may be performed through operation procedure (s) (usually vendor/release specific) with the relevant information elements represented by its specific or own network properties (usually vendor/release specific).
• The corresponding mapping module associated with the first communication network element will map the entity-specific notification, into the notification ( s ) of the abstracted or common interface procedure ( s ) , where the information elements specific to the managed entity are mapped into the information elements represented by the set of common network properties. • The vendor/release-independent manager or second communication network element receives the mapped notification ( s ) that are fully understood by the manager .
· When the vendor/release-independent manager or second communication network element needs to send an
instruction to a managed entity (usually
vendor/release specific) or first communication network element, the manager sends the instruction to the corresponding mapping module of the managed entity through common or abstracted interface procedure (s) with the information elements represented by the set of common network properties. The corresponding mapping module will map the instruction into the entity-specific instruction ( s ) and then send it/they to the managed entity through the entity-specific procedure (s) with the information elements specific to the managed entity. The managed entity receives the mapped instruction ( s ) that are fully understood by the managed entity.
There may be other types of messages sent and mapped between the manager and a managed entity. In general they may use the same method as defined above. In addition, existing operation, administration and maintenance (OAM) procedures (e.g., the operations and notifications of an Itf-N interface standardized by 3GPP SA5) may be utilize to realize the common interface procedures as long as their information elements are represented with the information elements from the set of the common network properties. The aspects and exemplary embodiments defined above and further aspects of the invention are apparent from the example of embodiment to be described hereinafter and are explained with reference to these examples of embodiment.
Brief Description of the Drawings
Fig. 1 shows schematically a vendor/release independent network operation by a network manager and
Fig. 2 shows schematically an exemplary method of operating a communication network comprising at least a first
communication network element and a second communication network element. Detailed Description
The illustration in the drawings is schematic.
Exemplary definitions and implementations of the common properties and procedures for an exemplary module or method will be explained in the following.
In particular, the term "common interface procedures" may denote any procedures used when communication between different communication network elements is performed during operation of a communication network or when using a communication network entity in a communication network, which are common for different communication network entities, e.g. communication network entities of different releases or vendors. In particular, common interface procedures may be procedures which are necessarily
performed or interpreted by any communication network entity. For example, a common interface procedure may relate to information concerning the element coverage, a size of the cell corresponding to a specific base station or mobile phone, a global cell ID, a radio mode, a cell status, or the like.
For simplicity of definition and clarity, some
abbreviations and simple syntax are used in the following when the properties and procedures are defined:
"=" denotes a definition, i.e. has the meaning of "is", "consists of", or "composes"
" I " denoted a logical "OR"
"&" denotes a logical "AND"
"()" denotes a group, i.e. has the meaning of a "set" or "union"
"//" denotes a comment given concerning the definition immediately before/above the comment
"<>" denotes an optional element, e.g., in a
definition
For further clarification it should be mentioned that: A defined property can be used for the definition of a latter property, with
the assumption that the definition of properties is fulfilled in the top-to-down manner and the reading of the definition shall follow this order.
Abstracted (cellular) network properties: In particular, in the definitions below the term being defined (left side of the may be a network property and the parameter defining the term may relate or form an information element)
CellularNetwork = (a set of Cells, Processing,
Radiolnterface, Peerlnterface, Backhaullnterface)
Cell = (GlobalCelllD, CellPurpose, CellSize,
RadioMode, RadioNature, RelatedCell, QoSClass,
UserClass, CellStatus)
(In this case the term "cell" may be a network property which is defined by information elements, i.e. the values of: GlobalCelllD, CellPurpose, CellSize, RadioMode,
RadioNature, RelatedCell, QoSClass, UserClass, CellStatus.
GlobalCelllD = charaterString
// a global identity that identifies uniquely the cell
CellPurpose = coverage | capacity
// this cell is assigned to add coverage or capacity
CellSize = small | medium | large
//the coverage scale of the cell
RadioMode = OmniDirectional | Directional
o OmniDirectional = (AntennaGeoLocation, 360) // here, 360 means 360 degree or a circle o Directional = (AntennaGeoLocation,
DirectionFromThisGeoLocation)
AntennaGeoLocation = (2DGeoLocation |
3DGeoLocation) • 2DGeoLocation = a two-dimension location represented with the coordinates based on a datum (e.g., UTM or WGS84) that describe this earth
• 3DGeoLocation = a three-dimension location represented with the coordinates based on a datum (e.g., UTM or WGS84) that describe this earth
DirectionFromThisGeoLocation = the
heading of the radio beam of this antenna on the earth surface based on the datum
// For example, the heading degrees are determined based on the
AntennaGeoLocation and its direction degree clockwise, referring the
specific datum used.
• RadioNature = interferenceLimited | noiseLimited · RelatedCell = list of (globalCelllD of a related cell, CellRelation with this cell)
o CellRelation = HORelation | CampingRelation | RadioRelation
HORelation = HOFromNeighbor |
HOToNeighbor | HOEachOther
• HOEachOther = HOFromNeighbor &
HOToNeighbor
CampingRelation = CampFromNeighbor |
CampToNeighbor | CampEachOther
· CampEachOther = CampFromNeighbor &
CampToNeighbor RadioRelation = interfered | interfering I interferingEachOther
• interferingEachOther = interfered & interfering
QoSClass = a set of traffic QoS classes that this cell supports
UserClass = a set of predefined user classes that this cell supports, where a user class has none traffic QoS class that is not defined by QoSClass CellStatus = InterfaceLoad | CellState |
AccessPerforamnce | <OtherGeneralStatus>
o InterfaceLoad = RadiolnterfaceLoad |
ProcessingLoad | BackhaullnterfaceLoad |
PeerlnterfaceLoad
RadiolnterfaceLoad = ( % of the capacity used) I (zero, small, medium, or large part of the capacity used)
ProcessingLoad = ( % of the capacity
used) I (zero, small, medium, or large part of the capacity used)
BackhaullnterfaceLoad = ( % of the capacity used) | (zero, small, medium, or large part of the capacity used)
PeerlnterfaceLoad = ( % of the capacity used) I (zero, small, medium, or large part of the capacity used)
o CellState = operational | underMaintenance
I turnedOff
o AccessPerformance = AttachPerformance |
HandoverPerformance | CoveragePerformance // performance relative to the set target AttachPerformance = bad | okay | good | perfect
HandoverPerformance = bad | okay | good | perfect
■ CoveragePerformance = bad | okay | good | perfect
o OtherGeneralStatus = any further status
defined later
Processing = All information processing done logically at the cell
Radiolnterface = All radio interfaces logically connecting the cell and its related user devices
Peerlnterface = All interfaces logically connecting the cell and its neighboring or related cells
Backhaullnterface = All interfaces logically
connecting the cell and the core network or,
connecting the cell and an egress/ingress network node for the cellular network
CellularNetworkOperation = CellUpdate | CellReport |
HandoverUpdate | IdleMobilityUpdate | LoadBalancingUpdate TrafficSteeringUpdate | <OtherUpdate> >· CellUpdate = MainPurposeUpdate | CellSizeUpdate |
RadioModeUpdate | RadioNatureUpdate |
RelatedCellUpdate | QoSClassUpdate | UserClassUpdate |
CellstatusUpdate
// Here, all the operations are the operations relative to the results of their former operations. For example, a current operation "EasierHandoverln (small)" means this operation will make the handover a bit easier than the handover under the last setting (s) configured by the last handover-related operation.
MainPurposeUpdate = CellPurpose
CellSizeUpdate = ( x% change from current cell size) I zeroCoverage | lastCellSize
o zeroCoverage = turn off the radio of this cell o lastCellSize = use the last used cell size
instead of the current cell size
RadioModeUpdate = OmniDirectional | Directional
RadioNatureUpdate = interferenceLimited |
noiseLimited
RelatedCellUpdate = RelatedCell
QoSClassUpdate = a set of traffic QoS classes that this cell supports
UserClassUpdate = a set of user classes that this cell supports, where a user class has none traffic QoS class that is not defined by QoSClass and not selected by QoSClassUpdate
CellStatusUpdate = CellState | <OtherGeneralStatus> CellReport = CellStatus | (globalCelllD of a related cell, CellRelation with this cell)
HandoverUpdate = MoreDifficultHandoverln |
EasierHandoverln | MoreDifficultHandoverOut |
EasierHandoverOut | ReturnToLastHOSetting
• MoreDifficultHandoverln = small | medium | large
// the change relative to the current handover parameter • EasierHandoverln = small | medium | large
//the change relative to the current handover parameter
• MoreDifficultHandoverOut = small | medium | large // the change relative to the current handover parameter
• EasierHandoverOut = small | medium | large
// the change relative to the current handover parameter
• ReturnToLatestHOSetting = return back to the
handover settings lastly used before the current settings
IdleMobilityUpdate = MoreDifficultCampIn |
EasierCampIn | MoreDifficultCampOut | EasierCampOut ReturnToLastIdleMobilitySetting
• MoreDifficultCampIn = small | medium | large
// the change relative to the current cell selection parameter
• EasierCampIn = small | medium | large
// the change relative to the current cell selection parameter
• MoreDifficultCampOut = small | medium | large // the change relative to the current cell selection parameter
• EasierCampOut = small | medium | large
// the change relative to the current cell selection parameter
• ReturnToLastIdleMobilitySetting = return back to the idle mobility settings lastly used before the current settings LoadBalancingUpdate = HandoverUpdate | IdleMobilityUpdate | ReturnToLastLBSetting
• ReturnToLastLBSetting = return back to the load balance settings lastly used before the current settings
TrafficSteeringUpdate = LoadBalancingUpdate |
AccessDirect | ReturnToLastTSSetting
• AccessDirect = AmountOf (<QoSClass>, <UserClass>) go from <SourceCell> to ( TargetCell |
TargetNetwork)
// where <a> means the attribute xa' is optional o AmountOf = small | medium | large | all o SourceCell = Cell
o TargetCell = Cell
o TargetNetwork = CellularNetwork
• ReturnToLastTSSetting = return back to the traffic steering settings lastly used instead of the current settings
// the traffic steering settings are any settings define the actual traffic steering state, which could also be "no traffic steering" where the traffic steering is disabled
OtherUpdate = any further update defined later
CellularNetworkOAM = a logical OAM entity that manages a CellularNetwork
// OAM = operation administration and management CellularNetworkOAMProcedure = RequestForOperation |
NotificationOfOperation | DecisionOnOperation
^ RequestForOperation = CellularNetwork requests
CellularNetworkOAM for the permission to take an
CellularNetworkOperation
^ NotificationOfOperation = CellularNetwork informs
CellularNetworkOAM concerning an
CellularNetworkOperation (with possibly the result of the operation) that the network has just taken
^ DecisionOnOperation = CellularNetworkOAM provides a
Decision on a RequestForOperation | CellularNetworkOAM demands CellularNetwork to take an
CellularNetworkOperation
· Decision = Accept | Reject | other
Fig. 1 shows schematically a vendor/release independent network operation by a network manager. In particular, Fig. 1 shows schematically part of a communication network 100 comprising a plurality of managed entities or elements 101, 102 and 103. The different managed entities may be vendor and/or release specific. For each of the managed entities a mapping module is provided. Although Fig. 1 schematically shows three mapping modules 104, 105 and 106 including a mapping scheme or mapping table one mapping module may be associated to a plurality of identical managed entities. The mapping modules performs mapping between abstracted properties and vendor and/or release specific properties. The managed entities communicate with their corresponding or associated mapping modules via a vendor and/or release specific network operation or network procedure. The mapping modules 104, 105 and 106 are commonly connected, via an OAM interface defined with a set of abstracted properties common for all vendors and
releases, with a vendor and release-independent manager 107. Thus, a vendor and/or release independent network operation may be provided.
As shown in Fig. 1, the method proposes to define an OAM interface with a set of common interface procedures and a set of common network properties (e.g., abstracted
parameters and function properties) , for example, as explained above. This interface serves an OAM manager with a set of common interface procedures using the information elements represented by the set of common network
properties .
Fig. 2 shows schematically an exemplary method of operating a communication network comprising at least a first
communication network element and a second communication network element. In box 201 there may be performed mapping specific network properties which are specific to the first communication network element and which are described by information elements specific to the first communication network element to abstracted network properties which are common for a plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements. In box 202 there may be performed notifying the second communication network element of the specific network properties of the first communication network element by sending the mapped abstracted network properties to the second communication network element. Summarizing a method according to an exemplary embodiment may serve to solve problems or disadvantages arising due to the fact that a communication service provider (CSP) is usually lacking sufficient knowledge of specific
communication network elements of different vendors, for example. For example, the CSP may lack knowledge of the vendor/release-specific parameters and their related network functions and operation relating to the
communication network element. This would make the CSP very difficult to directly operate these vendor/release-specific parameters and functions. Thus, according to an exemplary aspect a method is provided to prevent such difficulty of network operation. The method is to allow the CSP to operate the network with a set of abstracted network properties including abstracted parameters and abstracted function properties that are common to all the different network entities of different vendors and releases. The CSP or the communication network elements understands all the abstracted parameters, the abstracted function properties, and their operation. The vendor/release-specific network elements or entities may thus be operated as what the CSP has expected, via mapping between the abstracted network properties and the vendor/release-specific network
properties .
Finally, it should be noted that the above-mentioned embodiments illustrate rather then limit the invention, and that those skilled in the art will be capable of designing many alternative embodiments without departing from the scope of the invention as defined by the appended claims. In the claims, any reference signs placed in parentheses shall not be construed as limiting the claims. The word "comprising" and "comprises", and the like, does not exclude the presence of elements or steps other than those listed in any claim or the specification as a whole. The singular reference of an element does not exclude the plural reference of such elements and vice-versa. In a device claim enumerating several means, several of these means may be embodied by one and the same item of software or hardware. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
List of reference signs:
100 communication network
101 managed entity
102 managed entity
103 managed entity
104 mapping module
105 mapping module
106 mapping module
107 vendor/release-independent manager

Claims

CLAIMS :
1. A method of operating a communication network
comprising at least a first communication network element and a second communication network element, the method comprising :
mapping specific network properties which are specific to the first communication network element and which are described by information elements specific to the first communication network element to abstracted network properties which are common for a plurality of
communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements; and
notifying the second communication network element of the specific network properties of the first communication network element by sending the mapped abstracted network properties to the second communication network element.
2. The method according to claim 1, wherein specific network properties are described by information elements.
3. The method according to claim 1 or 2, wherein the mapping is performed by a mapping module.
4. The method according to any one of the claims 1 to 3, wherein the sending is performed through common interface procedures .
5. The method according to any one of the claims 1 to 4, wherein the mapping may be performed by the first
communication network element.
6. The method according to any one of the claims 1 to 4, wherein the mapping is performed by a third communication network element.
7. A method of operating a communication network
comprising at least a first communication network element and a second communication network element, the method comprising :
instructing the first communication network element by sending abstracted network properties which are common for a plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements; and
mapping the abstracted network properties to specific network properties which are specific to the first
communication network element and which are described by information elements specific to the first communication network element.
8. The method according to claim 7, wherein the
abstracted network properties are sent to a third
communication network element.
9. The method according to claim 8, wherein the mapping is performed by the third communication network element and further comprising the step of sending the information elements specific to the first communication network element to the first communication network element.
10. The method according to any one of the claims 1 to wherein the abstracted network properties relate to at least one item selected out of the group consisting of:
Cell,
Processing,
RadioInterface,
Peerlnterface,
Backhaul Interface,
CellUpdate,
CellReport ,
HandoverUpdate,
IdleMobilityUpdate,
LoadBalacingUpdate,
TrafficSteeringUpdate,
RequestForOperation,
NotificationOfOperation, and
DesicionOnOperation .
11. A mapping module for a communication network, wherein the mapping module is adapted to map abstracted network properties of communication network entities, wherein the abstracted network properties are common for a plurality of communication network elements and which are described by abstracted information elements which are common for the plurality of communication network elements with specific network properties, wherein the specific network properties are specific for a communication network element and which are described by specific information elements which are specific for the communication network element.
12. A program element, which, when being executed by a processor, is adapted to control or carry out a method according to any one of the claims 1 to 10.
13. A computer-readable medium, in which a computer program is stored which, when being executed by a processor, is adapted to control or carry out a method according to any one of the claims 1 to 10.
PCT/EP2012/075367 2012-12-13 2012-12-13 Method of operating a communication network WO2014090307A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/075367 WO2014090307A1 (en) 2012-12-13 2012-12-13 Method of operating a communication network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2012/075367 WO2014090307A1 (en) 2012-12-13 2012-12-13 Method of operating a communication network

Publications (1)

Publication Number Publication Date
WO2014090307A1 true WO2014090307A1 (en) 2014-06-19

Family

ID=47471749

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2012/075367 WO2014090307A1 (en) 2012-12-13 2012-12-13 Method of operating a communication network

Country Status (1)

Country Link
WO (1) WO2014090307A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11102664B2 (en) 2016-11-24 2021-08-24 Nokia Solutions And Networks Oy SON coordination under the occurrence of an anomaly

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1152625A1 (en) * 2000-05-04 2001-11-07 Siemens Aktiengesellschaft Updating of manufacturer specific harware informations at the manufacturer independent OMC-NMC interface of a mobile radio network
EP2296429A1 (en) * 2008-08-04 2011-03-16 Huawei Technologies Co., Ltd. Management method, device and system for interface circuit between access network and core network
WO2012166927A1 (en) * 2011-06-02 2012-12-06 Numerex Corp. Wireless snmp agent gateway

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1152625A1 (en) * 2000-05-04 2001-11-07 Siemens Aktiengesellschaft Updating of manufacturer specific harware informations at the manufacturer independent OMC-NMC interface of a mobile radio network
EP2296429A1 (en) * 2008-08-04 2011-03-16 Huawei Technologies Co., Ltd. Management method, device and system for interface circuit between access network and core network
WO2012166927A1 (en) * 2011-06-02 2012-12-06 Numerex Corp. Wireless snmp agent gateway

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11102664B2 (en) 2016-11-24 2021-08-24 Nokia Solutions And Networks Oy SON coordination under the occurrence of an anomaly

Similar Documents

Publication Publication Date Title
US10939333B2 (en) Communication method and communications apparatus to implement a network slice based service in a central unit (CU)-distributed unit (DU) architecture
CN109951877B (en) Slice information updating method and device
US20240015644A1 (en) Methods and apparatuses for reconfiguring a data connection
US11057799B2 (en) Devices and methods for slice-compliant handover control
US20210153278A1 (en) Network interconnectivity
WO2019236755A1 (en) Vehicle-to-everything session and service continuity in automotive edge computing systems
US20220167229A1 (en) Centralized and distributed self-organizing networks for physical cell identifier configuration and automatic neighbor relation
US11356898B2 (en) MEC support for multi-access convergence
CN108282773B (en) Information sending method, resource configuration method, device, control node and network element
US20150026327A1 (en) Multi-level self-organizing network coordination
US9413763B2 (en) Coordination between self-organizing networks
WO2019024617A1 (en) Method for accessing core network by terminal, base station, and terminal
EP4080932A1 (en) Method, apparatus and system for sending report information
CN111246365B (en) Mobile route management and control method, device and system
WO2019061189A1 (en) Mobility management in wireless networks
CN110730487B (en) Method, device and system for selecting session management function network element
KR101725791B1 (en) Methods and apparatuses for function coordination control
US11825316B2 (en) Random access channel (RACH) optimization in 5G networks
WO2014090307A1 (en) Method of operating a communication network
US10581983B2 (en) Method and system for management of mobile network slices over a federated infrastructure
KR20190034357A (en) Information interaction device, base station and communication system
EP4369678A1 (en) Conflict management of functions and services
CN112449389B (en) Switching method, source base station, target base station and terminal
US20220407621A1 (en) Controlling duplicate transmissions in multi-connectivity mode
CN117812650A (en) Switching method and communication device

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12809185

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12809185

Country of ref document: EP

Kind code of ref document: A1