WO2001013226A1 - Procede de distribution de mises a jour d'un logiciel dans un reseau dirige par les evenements - Google Patents

Procede de distribution de mises a jour d'un logiciel dans un reseau dirige par les evenements Download PDF

Info

Publication number
WO2001013226A1
WO2001013226A1 PCT/SE2000/001581 SE0001581W WO0113226A1 WO 2001013226 A1 WO2001013226 A1 WO 2001013226A1 SE 0001581 W SE0001581 W SE 0001581W WO 0113226 A1 WO0113226 A1 WO 0113226A1
Authority
WO
WIPO (PCT)
Prior art keywords
new
strategy
component
network
event
Prior art date
Application number
PCT/SE2000/001581
Other languages
English (en)
Inventor
Nicolas Gosselin
Edwin Tse
Fergus Kelledy
David O'flanagan
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to EP00957171A priority Critical patent/EP1277111A1/fr
Priority to AU68825/00A priority patent/AU768653B2/en
Priority to CA002402254A priority patent/CA2402254A1/fr
Publication of WO2001013226A1 publication Critical patent/WO2001013226A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates

Definitions

  • This invention relates to software systems, and more particularly, to a method of distributing software updates to handle previously unknown event types in a large multi-domain federation network of event-driven components.
  • Description of Related Art Currently, an increasing number of software systems (for example, telecommunication systems) rely on distributed architectures whose components are controlled across multiple administrative domains. The industry is looking for ways to avoid tightly coupled characteristics of components so that portions of the distributed system can be upgraded or changed without impact on other parts of the system.
  • NMSs Network Management Systems
  • various network elements under management are evolving rapidly over time.
  • cooperative management agreements for the management of network elements are also changing frequently due to the rapid making and breaking of business partnerships in the telecommunications industry.
  • These facts make it more critical that methods be devised to make upgrades or changes to network elements without adversely impacting other parts of the network.
  • a physical device like a switch
  • a logical device like a software application
  • problems may arise.
  • the existing installed management software may not be able to process the new event types, and the benefits of the new types of information generated by the new device are lost.
  • the introduction of previously undefined event types may introduce instability throughout the system.
  • the requirement to be backward-compatible may limit the capabilities that the new generation can have.
  • the older generation may be retired after installation of the new generation, thus making the effort and expense to achieve backward-compatibility unnecessary.
  • it would be advantageous to have a method of distributing software updates which does not require an operator to simultaneously update of all of the affected network components, and does not require the costly and sometimes unnecessary process of designing new event types to be backward-compatible with currently known event types. The present invention provides such a method.
  • the present invention is a method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven components which produce and consume events.
  • the method includes the steps of pushing a new software strategy for handling a new event type from a producer component into the network, and utilizing push technology to distribute the new strategy to the components in the network.
  • the step of distributing the new strategy may include selectively distributing the new strategy utilizing filtering capabilities in the push technology to determine whether the new strategy is applicable to each component in the network, and pushing the new strategy to those components for which the new strategy is applicable.
  • the method of the present invention may utilize a publish and push technology that does not utilize filtering in the individual components. Additionally, the invention may be applied only to update existing components.
  • the method comprises the steps of pushing a new software strategy for handling anew event type from a producer component to consumer components in the network, and utilizing the new strategy by the existing components to process events of the new type. If the method is to be utilized for new components as well, then the method also includes the steps of caching the new strategy in the components in the network, determining when a new consumer component binds into the network and subscribes to events of the new event type, and pushing the new strategy to the new component. The new strategy is then utilized by the new component to process events of the new type.
  • the method includes the steps of pushing a new software strategy for handling a new event type from a producer component into the network, and utilizing push technology to selectively distribute the new strategy to the components in the network. It is determined whether the new strategy is applicable to each component in the network, and upon determining that the new strategy is applicable to a given component, the strategy is cached by the given component and utilized by the given component to process events of the new type. Upon determining that the new strategy is not applicable to a given component, the strategy is cached by the given component for use by downstream components. When a new consumer component binds into the network and subscribes to events of the new event type, the new strategy is pushed to the new component.
  • the method may also begin by having the producer component first determine a plurality of new events occurring in the network as a result of a new event type.
  • the producer component classifies the plurality of new events into at least one event- specific class.
  • the producer component then pushes into the network, a single event of a first event-specific class along with a first new software strategy for handling the first event-specific class.
  • the first new strategy is selectively distributed to the components in the network utilizing push technology. If the first new strategy is applicable to a given component, the first new strategy is cached by the component and utilized to process events of the new type. If not applicable to the component, the first new strategy is cached by the component for use by downstream components. The process of distributing a strategy is then repeated for each event-specific class.
  • the strategies are cached in the network components and are pushed to new components that bind to the network and subscribe to events of the new type. Thereafter, the new strategies are utilized by the components that received them to process events of the new type.
  • FIG. 1 is a flow chart illustrating the steps performed by a producer component in the preferred embodiment of the method of the present invention
  • FIG. 2 is a flow chart illustrating the steps performed by the push technology in the preferred embodiment of the method of the present invention
  • FIG. 3 is a flow chart illustrating the steps performed by a consumer component in the preferred embodiment of the method of the present invention
  • FIG. 4 is an illustrative drawing of an exemplary scenario showing the introduction of a new event type in a federation network according to the teachings of the present invention.
  • the present invention describes a method of distributing software to handle previously unknown event types in a large multi-domain "federation" network of decoupled, event-driven components which manage, distribute, and process events.
  • One way to build such a decoupled-component network is to use "publish and push" technologies.
  • An information producer publishes the information and pushes it into the network.
  • One or more information consumer(s) registers itself with the network, and the network pushes information to the information consumer.
  • the information producer and the information consumer are decoupled by a store-and- forward medium. The producer need not be aware of the consumer(s), and states of the producers are independent from the states of the consumers (and vice versa).
  • the information may be network events such as network alarms, network performance data, network accounting data, etc.
  • Information producers may be network elements, and information consumers may be telecommunications Network Management Systems
  • publish and push technologies facilitate the construction of a federation of distributed, event-driven components.
  • each component produces and/or consumes events to fulfill its specific role in the federation.
  • Some of these components may be gateways that receive information emitted by devices or other systems, and translate the information into events. Then, they push the events into the network.
  • Other components interested in receiving those event types, subscribe to the network so that those events will be pushed to them in the future.
  • These components after receiving the events, process them and may generate new events based on the processed information which are also pushed into the network.
  • software updates are automatically distributed in the federation.
  • Components issuing new event types are responsible for supplying consumer components with appropriate software (hereinafter called Strategy) for handling the new event types.
  • Strategy which is normally stored within the event, may be entirely new code for handling events of the new type, or it may be a patch for existing code.
  • the consumer decides whether the strategy is applicable to it. If so, the Strategy is installed and thereafter affects the behavior of the consumer component according to information carried in the new event type.
  • FIG. 1 is a flow chart illustrating the steps performed by a producer component (Producer) 10 in the preferred embodiment of the method of the present invention.
  • a plurality of Producers represented as Producers 1-N may be performing the steps of FIG. 1 for different events.
  • the Producer creates a new event.
  • the Producer may use its knowledge of component types in the federation to determine a plurality of new events that will be generated by the introduction of a new event type in the federation.
  • the Producer classifies the new events into event-specific classes, and determines an associated Strategy for each event-specific class. The number of required Strategies depends on the number of roles anew event will affect.
  • the Producer determines whether or not the Strategy for the event has already been pushed into the network. If the Strategy has not been pushed, the method moves to step 13 where the strategy is stored in the event.
  • the event is then pushed to the push technology 15 for distribution in the network regardless of whether there are consumers for the event type or not.
  • the event conveying the class should include a release number corresponding to the format of the produced event type it is designed to handle. If it is determined at step 12 that the Strategy for the event has already been pushed, then the event is pushed at step 14 without Strategy.
  • FIG. 2 is a flow chart illustrating the steps performed by the push technology 15 in the preferred embodiment of the method of the present invention when an event is received from a Producer 10.
  • step 21 it is determined whether or not there is a filtering capability in the push technology. If so, it is determined at 22 whether or not the event is to be filtered. If so, the event is filtered out and discarded at 23. If there are no filtering capabilities, or the event is not to be filtered, the method moves to step 24 where the event is pushed to consumer components (Consumers) 25.
  • consumer components Conssumers
  • filters in the push technology selectively distribute the new Strategy to consumer components in the federation.
  • the filtering capabilities of the push technology being utilized in the network for inter-component communications determine whether or not a given Strategy is applicable to a given component. For example, if a filter is inserted upstream from a particular component, and the filter blocks the distribution of a particular Strategy, then the component has no knowledge of the Strategy until the filter is removed.
  • FIG. 3 is a flow chart illustrating the steps performed by a consumer component 25 in the preferred embodiment of the method of the present invention when an event with Strategy arrives from the push technology 15.
  • it is determined whether or not the Strategy is applicable for the receiving Consumer. If so, the Consumer installs the Strategy at 32 and then uses the Strategy to process events of the new type at 33. The Consumer then caches the Strategy at step 34. If it is determined at step 31 that the Strategy is not applicable for the receiving Consumer, the method moves directly to step 34 and caches the Strategy for subsequent distribution to downstream components that require it.
  • step 35 it is determined whether or not the Consumer 25 is also a Producer of events for downstream components. If so, the event with Strategy is then pushed to the push technology 15 for distribution to downstream components in the network. If the Consumer is not a Producer, the method moves to step 36 where the processing within the Consumer stops.
  • the distributed Strategies implement a role-based interface.
  • Each role a component can play is associated with an abstract interface.
  • a component responsible for storing information in a database may use a Strategy which implements an interface that returns a unique key for a given event (to be stored). That key is usually specific to one event type.
  • a producer of a new event type should then produce an appropriate Strategy that can create a key based on the new information in the new event type. If a new consumer binds into the federation and subscribes for events of the new type, the federation downloads the appropriate Strategy to the consumer in its initial download, and the new Strategy is then utilized by the new consumer to process events of the new type.
  • FIG. 4 is an illustrative drawing of an exemplary scenario showing the introduction of a new event type in a federation network according to the teachings of the present invention.
  • Components PI 41 and P2 42 are Producers of events 43 and 44, respectively, in the federation.
  • PI and P2 provide associated Strategies stored in the events regardless of whether there are consumers in the federation for those event types or not.
  • the events and Strategies are provided via push technology (PT) 15 to consumer Cl 45.
  • C3 is a component which correlates alarm messages it receives and issues correlation events 48 back into the federation through PT 15.
  • C4 is exemplified as a component which displays events to an operator through a user interface, and provides the operator with a software connection 49 to a physical device 51 connected to P2.
  • Producer P2 connects to the new physical device 51 , and determines a Strategy associated with this event.
  • the new event and the new Strategy are pushed through the federation, as described above, to consumer Cl where they are cached.
  • the new Strategy is pushed to consumers C3 and C4 where it is cached.
  • Consumer C3 in this example determines that the new Strategy is not applicable, and therefore disregards the new Strategy.
  • Consumer C4 determines that the new Strategy is applicable to it, and installs the new Strategy. C4 may then use the new Strategy to provide the software connection 49 to the physical device 51 , or to communicate with P2. If a new consumer C5 52 binds to the federation and subscribes to the new event, Cl sends the new Strategy to C5.
  • Consumer C5 caches the new Strategy and thereafter utilizes the new Strategy when it receives events of the new type.

Abstract

L'invention concerne un procédé permettant de distribuer un logiciel destiné à gérer des types d'événements antérieurement inconnus dans un vaste réseau 'fédération' multi-domaines de composants découplés et dirigés par les événements. Les composants comprennent des composants producteur (10) qui produisent des événements et des composants consommateurs (25) qui consomment les événements pour remplir leurs rôles spécifiques dans la fédération. Tout d'abord, un composant producteur détermine plusieurs nouveaux événements survenant dans le réseau comme résultat d'un nouveau type d'événement, et classifie ces nouveaux événements en au moins une classe spécifique événement. Ensuite, le composant producteur pousse un événement unique (14) d'une classe spécifique événement dans le réseau en même temps qu'une nouvelle stratégie logiciel (13) destinée à la gestion de la classe spécifique événements. La nouvelle stratégie est distribuée aux composants dans le réseau à l'aide de la technologie du pousser (15). Si la nouvelle stratégie est applicable à un composant donné (31), la nouvelle stratégie est prise (32) par le composant et utilisée pour traiter les événements du nouveau type. Si elle n'est pas applicable au composant, la nouvelle stratégie est prise (34) par le composant pour être utilisée par les composants aval. Le procédé de distribution d'une stratégie est ensuite répété pour chaque classe spécifique événement. Les stratégies sont prises dans les composants réseau et poussées jusqu'à de nouveaux composants qui sont liés au réseau et s'abonnent à des événements du nouveau type. Enfin, les nouvelles stratégies sont utilisées par les composants qui les ont reçues pour traiter les événements du nouveau type.
PCT/SE2000/001581 1999-08-16 2000-08-15 Procede de distribution de mises a jour d'un logiciel dans un reseau dirige par les evenements WO2001013226A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP00957171A EP1277111A1 (fr) 1999-08-16 2000-08-15 Procede de distribution de mises a jour d'un logiciel dans un reseau dirige par les evenements
AU68825/00A AU768653B2 (en) 1999-08-16 2000-08-15 Method of distributing software updates in an event-driven network
CA002402254A CA2402254A1 (fr) 1999-08-16 2000-08-15 Procede de distribution de mises a jour d'un logiciel dans un reseau dirige par les evenements

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US37517799A 1999-08-16 1999-08-16
US09/375,177 1999-08-16

Publications (1)

Publication Number Publication Date
WO2001013226A1 true WO2001013226A1 (fr) 2001-02-22

Family

ID=23479808

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2000/001581 WO2001013226A1 (fr) 1999-08-16 2000-08-15 Procede de distribution de mises a jour d'un logiciel dans un reseau dirige par les evenements

Country Status (5)

Country Link
EP (1) EP1277111A1 (fr)
CN (1) CN1153137C (fr)
AU (1) AU768653B2 (fr)
CA (1) CA2402254A1 (fr)
WO (1) WO2001013226A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7853609B2 (en) 2004-03-12 2010-12-14 Microsoft Corporation Update distribution system architecture and method for distributing software
US8612997B2 (en) 2008-01-15 2013-12-17 International Business Machines Corporation Event-driven component integration framework for implementing distributed systems

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7546582B2 (en) * 2005-03-30 2009-06-09 International Business Machines Corporation Managing dynamic configuration data for producer components in a computer infrastructure

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0537098A2 (fr) * 1991-10-11 1993-04-14 International Business Machines Corporation Dispositif de traitement d'évènement à procédés de filtrage et association d'action
EP0759591A1 (fr) * 1995-08-18 1997-02-26 International Business Machines Corporation Service de gestion d'événements
US5862325A (en) * 1996-02-29 1999-01-19 Intermind Corporation Computer-based communication system and method using metadata defining a control structure
US5933645A (en) * 1996-03-19 1999-08-03 Oracle Corporation Non-invasive extensibility of software applications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0537098A2 (fr) * 1991-10-11 1993-04-14 International Business Machines Corporation Dispositif de traitement d'évènement à procédés de filtrage et association d'action
EP0759591A1 (fr) * 1995-08-18 1997-02-26 International Business Machines Corporation Service de gestion d'événements
US5862325A (en) * 1996-02-29 1999-01-19 Intermind Corporation Computer-based communication system and method using metadata defining a control structure
US5933645A (en) * 1996-03-19 1999-08-03 Oracle Corporation Non-invasive extensibility of software applications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
GIL SEONG NA ET AL: "Interoperability of Event Service in Java ORB Environment", IEEE COMPUT SOC, USA. PROCEEDINGS TENTH INT WORKSHOP ON DATABASE AND EXPERT SYSTEMS APPLICATIONS, 1 September 1999 (1999-09-01) - 3 September 1999 (1999-09-03), LOS ALAMITOS, CA, USA, pages 29 - 32, Florence, Italy, XP002932719 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7853609B2 (en) 2004-03-12 2010-12-14 Microsoft Corporation Update distribution system architecture and method for distributing software
US8612997B2 (en) 2008-01-15 2013-12-17 International Business Machines Corporation Event-driven component integration framework for implementing distributed systems
US8799930B2 (en) 2008-01-15 2014-08-05 International Business Machines Corporation Event-driven component integration framework for implementing distributed systems

Also Published As

Publication number Publication date
CN1379876A (zh) 2002-11-13
EP1277111A1 (fr) 2003-01-22
CN1153137C (zh) 2004-06-09
AU768653B2 (en) 2003-12-18
AU6882500A (en) 2001-03-13
CA2402254A1 (fr) 2001-02-22

Similar Documents

Publication Publication Date Title
US8139509B2 (en) Installation and management of mobile device [{S]} configuration
US6684244B1 (en) Aggregated policy deployment and status propagation in network management systems
JP5391276B2 (ja) インテリジェント移動体デバイス管理クライアント
US20070169073A1 (en) Update package generation and distribution network
US7085822B1 (en) Managing pervasive devices
CN101960449B (zh) 用于对远程资源的web访问的基于XML的web订阅源
CN101416183B (zh) 保存无线设备当前数据的方法和系统
AU2005200345B2 (en) Update distribution system architecture and method for distributing software
CN101170446B (zh) 一种进行许可证管理的方法、服务器、客户端和系统
US20050267951A1 (en) Rolling upgrade of distributed software with automatic completion
JP2000512093A (ja) 総合電気通信サービス委託システムおよび方法
US8296198B2 (en) Method and system for distribution of information
US9047163B2 (en) Managing the distribution of client packages
CN105528205A (zh) 更新控制方法和更新控制系统
CN110389766A (zh) HBase容器集群部署方法、系统、设备及计算机可读存储介质
CN105653328A (zh) 大内存服务的多版本程序的并存方法和装置
CN107395385A (zh) 软件升级方法及装置
CN112463211A (zh) 一种兼容多种开发架构的系统架构改造方法及系统架构
CN108540509A (zh) 一种终端浏览器的处理方法、装置及服务器、智能终端
AU768653B2 (en) Method of distributing software updates in an event-driven network
SE529564C2 (sv) Förfarande och system för provisionering av innehåll i ett mobilt apparathanteringssystem
CN101820354B (zh) 基于tnds对象的配置方法、终端设备及服务器
US20090037493A1 (en) Method and device for updating an object with copyright attribute
CN102741829B (zh) 用于移动业务对象的基于消息的同步方法及其系统
WO2006032960A2 (fr) Methode et systeme de decouplage total de licences d'une configuration protegee associees a ces licences

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: IN/PCT/2002/00177/DE

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2000957171

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 68825/00

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 008143897

Country of ref document: CN

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWE Wipo information: entry into national phase

Ref document number: 2402254

Country of ref document: CA

WWP Wipo information: published in national office

Ref document number: 2000957171

Country of ref document: EP

WWG Wipo information: grant in national office

Ref document number: 68825/00

Country of ref document: AU

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Ref document number: 2000957171

Country of ref document: EP