WO1996015635A1 - Controlling elements of a telecommunications network - Google Patents
Controlling elements of a telecommunications network Download PDFInfo
- Publication number
- WO1996015635A1 WO1996015635A1 PCT/GB1995/002617 GB9502617W WO9615635A1 WO 1996015635 A1 WO1996015635 A1 WO 1996015635A1 GB 9502617 W GB9502617 W GB 9502617W WO 9615635 A1 WO9615635 A1 WO 9615635A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- instruction
- elements
- control
- generic
- switches
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/0016—Arrangements providing connection between exchanges
- H04Q3/0062—Provisions for network management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q3/00—Selecting arrangements
- H04Q3/64—Distributing or queueing
- H04Q3/66—Traffic distributors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13533—Indexing scheme relating to selecting arrangements in general and for multiplex systems multivendor and hybrid, e.g. public/private, networks, inc. international
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
- H04Q2213/13566—Indexing scheme relating to selecting arrangements in general and for multiplex systems mediation
Definitions
- This invention concerns controlling elements of a telecommunications network, particularly but not exclusively for traffic management.
- modern telecommunications networks are highly automated, they still require some monitoring and centralised control in order to deal with unusual circumstances such as overload conditions.
- a typical instance is a sudden surge in the number of calls made to a given telephone number, perhaps as a result of the number being given out on a television broadcast in an advertisement, during a phone-in show, or if an emergency contact number is given out on a news bulletin reporting a major accident or natural disaster.
- call blocking arranges that a proportion of calls to a target number are failed by the originating exchange.
- Call gapping arranges that, after a call attempt is made to a target number, no further call attempts can be made to that number until a predetermined interval has elapsed. Both these systems reduce unnecessary use of the trunk network by failed call attempts.
- a problem which arises in applying centralised control to a telecommunications network is that, in a typical network, exchanges are not identical. This is because in a developing network, at any given time, more than one type of exchange will be in use. Moreover, the different characteristics of the areas served by different exchanges may make different types of exchange appropriate in different locations. Consequently, certain functionality may only be available to certain exchanges or, even where the functionality is universal, individual instructions may be required to operate them. It is therefore necessary to tailor the instructions for each exchange. Furthermore certain services, such as call-gapping and call blocking, may be required only for a selected subset of exchanges, such as those serving the area in which the number has been broadcast.
- a method of controlling a plurality of elements of a telecommunications network comprising the steps o ⁇ generating a generic instruction, selecting the elements for which the instruction is directed, and transmitting the instruction to the respective elements.
- a controller for a telecommunications network having a plurality of functional elements, comprising means for generating a generic instruction, and means for transmitting the instruction to the respective elements, characterised in having means ⁇ or selecting the elements to which the instruction is directed.
- a generic instruction By transmitting a generic instruction applicable to all relevant elements, the operator of the system can control all the elements with a single instruction.
- a generic instruction can be translated into separate instructions applicable to each individual element or defined groups of elements.
- Certain elements may not have the ability to carry out certain functions, accor ⁇ ingly the method may provide that if one or more of the selected elements is not capable of performing the required instruction no instruction is transmitted to that element or elements.
- the ability of the network as a whole to carry out the desired functions may be dependent on the ability of each individual element to carry out a predetermined function.
- the method may therefore provide that, if any element is incapable of performing the required instruction, no instruction is transmitted to any of the elements. In other words, no instruction is transmitted to any element unless all the elements required to co-operate can carry out their individual instructions.
- certain network functions may be performable by parts of the network independently of the ability of other elements to do so, so the method may provide that if any elements are incapable of performing the instruction, the instruction is sent only to the elements which are capable of performing the instruction.
- instructions may be prepared and stored for onward transmission in response to a predetermined condition.
- the predetermined condition may be the expiry of a pre-set time interval, allowing advance scheduling of network controls. For regular events, such as weekly or daily 'phone-in' programmes, the time interval may be re-set after each transmission of the instruction. However, for one-off situations such as special events the time interval is not re-set.
- the instructions to the network elements may be arranged to cause the inhibition of a signalling function.
- calls to that number can be gapped or blocked by inhibiting call set-up signals being sent to the number translation network element. This prevents aoonive call set-up attempts clogging the signalling network, as wei- as free.riq » - attic network itself.
- the method comprises the steps of generating an instruction in high-level language, a selection pattern output, and an interface type message, converting the high-level instruction into instructions in formats compatible with each of a respective element type; and comparing the selection pattern data with stored information to select the elements to which the instruction is to be sent.
- Figure 1 a shows a simple telecommunications network controlled by a network manager, illustrating one arrangement according to the invention
- Figure 1 b is a diagram of a telecommunications network having a separate signalling network, illustrating a further arrangement according to the invention
- Figure 2 shows the functional components of a network manager embodying the present invention and their relationship with a number of switching centres;
- FIGS 3 and 4 show simplified details of the store element 1 7 of Figure 2;
- Figure 5 shows an illustration of a single shot schedule operated according to the invention
- Figure 6 shows an illustration of a multi-shot schedule operated according to the invention
- Figure 7 shows how such scheduled controls can be implemented according to the invention.
- Figure 1 a shows a simple telecommunications network having six switches (exchanges) A1 , A2, B1 , B2, B3, C1 all operating under the centralised control of a network manager M.
- the switches are interconnected by traffic- carrying links ( 1 , - 2, 3, 4, 5, 6, 7, 8, 9, 10; solid lines) and each switch is connected to the network manager M by a respective control link (40, 41 , 42, 43, 44, 45: dotted lines).
- Figure 1 b shows a variant of Figure 1 a. Only three exchanges A1 , B2, B3 are shown for simplicity, connected, as in Figure 1 a, by a traffic network 4, 9, 10 and also by a signalling network 31 , 32, 33 to a signalling element T which includes a number translator Tx.
- the exchanges A 1 , B2, B3 and signalling element T are under the control of the network management centre M, by means of links 40, 42, 45, 46 respectively.
- Each exchange A1 , B2, B3 is connected to a number of user terminals (only one shown in each case, 21 , 22, 23 respectively).
- the functional components of the network manager M which embody the invention, and their relationship to the network are illustrated in Figure 2. It includes a store 1 7 which stores various attributes relating to the switches and the links between them. Such attributes include the types of equipment installed at each switch (in this example identified as type A, type B and type C which may for example be the System X, AXE 10 and 5ESS types currently in use by British Telecommunications pic) and the geographical location (in this example identified as area X (centres A1 , B1 , B2), area Y (centres A2, CD and area Z (centre B3). These areas may be defined by any suitable criterion or combination of such criteria.
- a television coverage area may be appropriate for defining the switches to be controlled for call-gapping purposes when a phone-in number is broadcast, whilst for an enquiry line for a utility service such as transport, power, water etc. call-gapping may be required according to that utility's regional structure. More than one such geographical overlay may be defined.
- the data stored in store 1 7 may also include data on the current state of the elements, updated by input from the network elements.
- the construction of network managers is well known to those skilled in the art. Typically a network manager is embodied by a computer whose software provides the necessary functional components.
- the network manager M has three types of input, namely a time indication from a clock 1 1 , a human interface 1 2 and a monitor 13 which receives inputs from the network N and either transmits a message to the operator by means of the human interface 1 2 or generates an automatic response from the network manager.
- the human interface 1 2 is associated with a network traffic control library 20 in which may be stored standard input formats.
- a generic instruction generator 14 receives inputs from the human interface 1 2 and the monitor 1 3.
- the generic instruction generator 14 provides three outputs: an instruction in high-level language which is passed to a group of translators 1 5a, 1 5b, 1 5c, a selection pattern output which is passed to a data matcher 1 6, and an interface type message transmitted to an interface module 19.
- the translators 15a, 1 5b, 1 5c are each configured to convert the high-level instructions received from the generic instruction generator 14 into an instruction in a format compatible with a respective switch type A, B or C.
- the data matcher 1 6 receives selection pattern data from the generic instruction generator 14 and compares this data with the information stored in store 17 in order to select the switches to which the instruction is to be sent.
- the data stored in the store 17 can be updated in response to inputs from the network N through the monitor 1 3.
- Figures 3 and 4 show the organisation of data in the store 17.
- Figure 3 shows the data stored for the switches A1 , A2, B1 , B2, B3, and C; by geographical area and type of switching equipment.
- the store 1 7 may also hold data relating to the current condition of the switches.
- Figure 4 shows similar inherent data held for each link ( 1 to 10) in the system. This data includes the termination points and the capacity of each link.
- An instruction generator 18a, 18b, 18c is provided for each type of switch
- Each instruction generator 18a, 18b, 18c receives data from the matcher 1 6, the clock 1 1 and, via the interface module 1 9, the respective translator 1 5a, 1 5b or 1 5c, from which instructions are generated for transmission to appropriate elements of the network N.
- the instructions may be transmitted by the instruction generators 1 8a,
- the instructions may be transmitted to the network N on a regular basis, such as at a predetermined time and day of the week to coincide with the broadcast times of a phone-in television or radio show.
- the interface module 1 9 ensures that a generic instruction which requires the co-operation of two or more switches is compatible with all the switches involved.
- the interface module 1 9 controls the operation of the instruction generators 1 8, 1 8b, 1 8c in the event that the instruction required is incompatible with the capabilities of one or more types of switch A.
- a message is transmitted to the human interface 1 2 to indicate whether, or to what extent, the instruction can be executed.
- the function to be controlled is call-gapping, to be initiated at a set time once a week or in response to an overload condition detected by the monitor 1 3.
- call-gapping is only required for switches in geographical areas X and Y, and that equipment of type A is not capable of providing call-gapping functionality
- the human operator provides an input through the human interface 12 to the generic instruction generator 14.
- This input identifies the function required (call-gapping), the proportion of calls to be gapped, the geographical area to be covered (in this example zones X and Y), and the time that the function should operate (for example with immediate effect until manually cancelled, or from 1 900 to 2030 every Tuesday, or in response to an external stimulus such as an overload detected by the monitor 13).
- the generic instruction generated in the generator 14 is transmitted to the bank of translators 1 5a, 1 5b, 1 5c which each translate the instruction into a form which can be handled by a respective switching system type A, B, C. In this case type A is incapable of performing call-gapping so an error message is generated by the translator 1 5a.
- the generic instruction generator 1 4 has two further outputs. Firstly, it transmits the selection criteria to the matcher 16.
- the switches to be call-gapped are selected by geographical area.
- the selection of the set of switches to be selected may be done on the basis of the intrinsic architecture of the network, e.g. a set may comprise a DMSU (digital main switching unit) and its daughter DLEs (digital local exchanges). Alternatively the set may be manually selected, in order to meet a non-intrinsic criterion such as the coverage area of a television station, or the administrative regions of a utility company.
- the identities of the switches which meet the criteria are transmitted from the matcher 1 6 to the bank of instruction generators 18a, 1 8b, 18c.
- the identities of the switches A 1 and A2 are transmitted to the instruction generator 1 8a, the switches B1 and B2 to the instruction generator 18b, and the switch C1 to the instruction generator 18c.
- the identity of the switch B3 is not transmitted to instruction generator 18c because it is in zone Z and therefore does not meet the geographical requirement.
- the other output from the generic instruction generator 14 relates to the type of instruction, and is transmitted to the interface module 1 9.
- This output identifies to the interface module 19 whether the operation should be partially executed even if some switches lack the necessary functionality. In the case of call-gapping or call blocking the operation can be partially executed in this way, so the interface module 1 9 transmits the instructions generated by the translators 1 5b and 1 5c to the respective instruction generators 18b, 18c, but transmits no instruction to the instruction generator 1 8a as only an error message was received from the translator 1 5a.
- the arrival of an error message from any one of the translators 1 5a, 1 5b, 1 5c prevents the interface module 1 9 from transmitting any instruction to any of the instruction generators 18 a, b, c.
- the generic instruction requires a route to be established between a first switch having the required functionality and a second switch lacking that functionality the route is not established. However, this does not prevent the first switch establishing routes to other switches in accordance with the generic instruction, provided these other switches have the required functionality.
- the instructions generated in the instruction generator 1 8b, are transmitted to the switches B1 and B2, and the instruction generated in the instruction generator 18c is transmitted to the switch C1 .
- the instructions are transmitted under the control of the clock 1 1 , at the times programmed by the generic instruction generator 14.
- the required function can be performed by all switching elements having suitable functionality within the geographical area spacified, without the human operator needing to generate separate instructions for each type of switch or to specifically identify the switches to be controlled.
- the system is configured so that the signalling network 31 , 32, 33 is prevented from overloading with unsuccessful call attempts.
- Call set-up signals are carried over the signalling network 31 , 32, 33 in order to set-up the necessary connections in the traffic network 4, 9, 10 between the exchanges A1 , B2, B3.
- the user 23 is subject to a number translation service carried out by a number translator Tx in the signalling element T.
- the users 21 , 22 can call the user 23 using a special number (e.g. a toll-free number) which is translated by the translator Tx to control the signalling element T to set-up a call to the user 23.
- the network manager M can control the switches A1 , B2, B3 to inhibit the transmission over the signalling network 31 , 32, 33 of call requests to that number. This releases capacity not only in the traffic network 4, 9, 10, but also in the signalling network 31 , 32, 33. If one of the switches (e.g. A1 ) does not have the capability to inhibit the transmission of such call requests, they can still be inhibited by the network manager M at the signalling element T. This does not prevent unsuccessful call requests appearing on the signalling link 31 , between the exchange A 1 and the signalling element T, but it does prevent them propagating over the rest of the network
- control definition e.g. control scheduling
- control implementation e.g. control scheduling
- PPCs pre-planned controls
- the PPC may be saved in the network traffic control library 20 for later use or may be scheduled.
- the primary function of the library 20 is to provide a repertoire of PPCs which may be quickly retrieved to deal with network problems.
- PPCs in the library 20 may be retrieved for control scheduling. Users schedule a PPC by selecting one from the library 20 and specifying the schedule details and if necessary the control target and control parameters may be added (if they are not already defined), or changed (if they are defined). The PPC in the library 20 is not affected. Once scheduled, the control is entered onto the list of currently scheduled controls.
- Scheduled controls may be positively authorised at any time within N minutes of their due implementation (where N is a pre-defined parameter), otherwise the control will not be implemented. If authorisation is not given within the pre-defined time period specified by N a report is generated.
- Authorised controls are automatically implemented (inserted and removed) according the schedule attached to the PPC. Users can monitor the progress of controls implementation in real-time.
- the network traffic control library 20 allows users to build up and maintain a repertoire of PPCs. This allows users to save time by having access to templates to commonly used controls (e.g. to deal with focused overloads) where only the control target is different. It also allows the accurate implementation of a prepared complex sequence of controls. Network problems which require the fast and accurate deployment of a number of controls can be dealt with promptly.
- the library 20 may also be used as a source from which to build new controls.
- the control targets may be specified, or may be left for the user to select.
- a linked PPC consists of a sequence of PPCs. PPCs may be stored with all or only some of the control parameters and the control target blank. The network manager will check that a PPC is fully specified when it is selected for scheduling.
- a basic PPC with a single exchange/route as a control target is the simplest type of control
- a basic PPC with an exchange set as a control target is also referred to as a broadcast control
- a broadcast control is a control which is applied to a number of exchanges (exchange set).
- a facility is provided for defining and maintaining a library of exchange sets.
- a linked PPC is a composite control and is defined by linking together a number of basic PPCs in a sequence to form a linked PPC. When the linked PPC is implemented, each PPC in the chain is implemented sequentially starting with the first.
- Exchanges can be grouped together into exchange sets. Commonly used exchange set definitions may be stored in store 17 and used when defining broadcast controls These are referred to as static exchange sets.
- Exchanges can also be grouped by exchange type into dynamic exchange sets.
- the following default dynamic exchange sets are provided:-
- a traffic control is scheduled to deal with a particular problem on the network Users have two sources for PPCs when scheduling, namely PPCs stored in the network traffic control library; or by defining a control for the purpose, allowing users to schedule new controls rapidly without following the normal sequence of storing a control definition in the library and then retrieving it.
- the network manager will perform the same sequence of operations but this will be transparent to the user.
- a network traffic control is applied to an exchange in two stages. It is defined using the facilities of the network traffic control library, and the schedule to be applied at specified times. The control could be applied immediately or stored for later application.
- Both single-shot and multi-shot (repeating) schedules are provided: single-shot where only one insertion (and removal) is involved multi-shot where multiple insertions (and removals) are involved.
- Scheduled controls may be named in such a way as to link them to specific events, e.g. Christmas Day.
- a schedule may be specified without a removal time.
- the single-shot timing mechanism provides the opportunity to define a period during which the traffic control should be applied. This is achieved in terms of a control insertion time, and a control removal time.
- Figure 5 provides an illustration of the type of schedule that may be achieved using a single-shot schedule.
- the hatched area represents the time over which the control is in force.
- 'A' represents the application time, and 'R' the removal time.
- a control may be scheduled without a specified removal time; such a control is effective indefinitely. Facilities are provided to add later a removal time to the schedule; immediate removal is also possible.
- the control insertion time is specified as a specific time e.g. 10:30 14
- the control removal time is specified in the same format as the insertion time, e.g. 13: 15 14 NOV 94 or it may be specified as a delta time (i.e. the control duration): e.g. 002 02.45
- the delta time in the example means remove the control after an elapsed time of 2 days 2 hours and 45 minutes.
- a multi-shot (repeating) schedule is a single-shot schedule but with the addition of a schedule start and end time and some repeating criteria (e.g. on Monday of every week)
- the facility of multi-shot schedules provides the opportunity to define a repeating traffic control application pattern.
- the application pattern is defined in terms of: a schedule start time; a schedule end time; a control inserting time (within the period specified by the schedule start a control removal time (within the period specified by the schedule start and end time); and repeat criteria.
- Figure 6 provides an illustration of the type of schedule that may be achieved using a multi-shot schedule.
- the hatched area represents the time over which the control is in-force. It is possible for the control m-force period to span a midnight boundary (i.e. control removal occurs on a different day to control insertion). A control is removed when its associated schedule expires.
- control is not applied until Schedule Start Time SST and is removed at Scheduled End Time SET, although these do not necessarily coincide with control insertion and removal times.
- the scheduled start time SST, control insertion time A and control removal time R are specified in the same format as for the single shot control above.
- the scheduled end time defines a time after which no further applications occur.
- the scheduled end time is specified in one of the formats specified for the control removal time above.
- the repeating criteria are identified in terms of: days of the week, or days of the month (but not both), and calendar months of the year in which the above applies.
- a multi-shot schedule specifies a schedule start and end time and the days of the week or days of the month in which the control insertions and control removals apply within the specified schedule start and end
- a more specialised repeating pattern based on the above can be defined, by further identifying the months within the specified schedule start and end time in which the control insertions and control removals apply.
- schedules it is possible for schedules to expire automatically, or be forced to expire by operator action.
- the schedule automatically expires on removal.
- automatic expiry occurs on the schedule end time.
- the network manager After a control from the network traffic control library 20 is scheduled, the network manager maintains details of the scheduled control and will implement the control as specified in the schedule.
- a facility is provided to allow users to track and monitor the current list of scheduled controls on the network manager and to monitor which of the scheduled controls are in-force (active).
- Figure 7 shows how scheduled controls are tracked by the network manager through the scheduled control and active control lists. In the event of a scheduled control application failing, the application is periodically retried until it is successful or the end of the scheduling period has been reached. The number of retries and the retry interval are configurable parameters.
- a message is sent to the human interface 1 2 if the network manager fails to implement a scheduled control after the maximum number of retry attempts or the end of the scheduling period has been reached.
- the implementation of a scheduled control can fail for several reasons. Firstly there may be inconsistent scheduled requests or other reasons (failure within network manager). Secondly there may be communications failure. There may also be communications failures, maintenance failures (e.g. failure to process a job request), or exchange failures (e.g. the exchange does not accept a control request from the network manager).
- the network manager will continue to apply the retry logic as specified in order to attempt to successfully implement the control. However, in the event of an exchange failure the network manager will stop the retry logic as soon as an exchange fails to accept a control request.
- Overlapping schedules can be allowed subject to any traffic control implementation rules defined in the network manager, as described below.
- the network manager checks if there is an existing control on the control target, and if so, the actual control requests issued by the network manager are modified.
- the rules specified below, are general rules to be applied when implementing controls.
- the network manager may issue a real-time "control status read" request before applying a control.
- a basic PPC Single Exchange/Route and Exchange Set
- the network manager checks for a control of the same type on the target (which may consist of members of an exchange set). If a control of the same type is already in force, and if the schedule creation date of the scheduled control is earlier than the in force control, the scheduled control is not implemented; otherwise the scheduled control is implemented.
- the user is able to suspend scheduled controls, which may be authorised, prior to implementation. Suspended controls can be reinstated at any time, however a control will not be implemented if the scheduled insertion time has been exceeded. Multi-shot controls will be implemented until the next insertion time after the reinstatement.
- the network manager Before inserting a Basic PPC (Single/Exchange/Route and Exchange Set) control the network manager may issue a request to read the real-time control status.
- a Basic PPC Single/Exchange/Route and Exchange Set
- the network manager may be arranged such that if it discovers a control of the same type and detects that it did not insert the discovered control, the network manager alerts users, updates the controls database and sends a message to the central system mailbox. The scheduled control will then only be applied if agreed by a user with the Control Authorisation access privilege, and otherwise will be removed.
- the network manager checks for a scheduled control of the same type on the target (which may consist of members of an exchange set). If a control of the same type is scheduled and due to be enforce (but not implemented due to the application of the first rule above - see Figure 7) the control is applied using the second rule above.
- a Basic PPC Single Exchange/Route and Exchange Set
- the network manager issues a real-time control status read request. If a control is already in-force on the exchange or the resource already exists a recover exchange specific command is issued.
- each PPC in the chain would only be implemented if the implementation of the previous PPC was successful.
- Implementation of constituent PPCs in the chain would be according to the rules specified above for PPCs. Removal of the PPCs in the chain is in the reverse order to that of insertion.
- Scheduled controls which have been authorised are implemented by the network manager at the specified times.
- the network manager maps the generic control to an exchange-specific control if the generic control is a linked control then each individual control in the linked control is mapped to the exchange-specific format when the individual control is implemented.
- the network manager then transmits the control request(s) to the appropriate instruction generator 1 8a, 1 8b, or 1 8c for each exchange, and saves the corresponding control response(s) returned by the instruction generator 18. Finally, the network manager updates the internal control database with the new status of the control.
- control may be inserted, removed, or cancelled.
- control status read requests may be issued to obtain the status of a network resource prior to inserting or removing a control on it.
- the cancel request does not result in any control requests to the network communications manager.
- Control responses are matched with the control requests to form a complete control transaction. Each control transaction corresponds to an insertion or removal of a scheduled control.
- Network traffic management controls are instructions sent to an exchange (via a Network Communications Manager) to modify exchange resources, with the purpose of overcoming problems existing on the network (e.g. by causing traffic to be re-routed).
- Each equipment type (e.g. System X Phase 3) manages a different set of resources to perform its switching operations.
- the network manager attempts to modify exchange resources on different exchange equipment types with the intention of modifying traffic patterns in similar ways.
- Each generic control stored on the network manager M has a defined set of parameters.
- the controller sends exchange specific control requests to the network elements when a scheduled control is implemented.
- the translators 1 5 convert generic controls stored in the network manager to exchange-specific versions at the point of implementation via a set of mapping rules.
- the network manager When a user creates a Destination Volume Control such as call blocking, the network manager stores the values for the generic parameters defined for the control and not values for the exchange specific parameters.
- the exchange specific parameters are calculated according to a set of mapping rules at implementation time. A separate set of rules is required for each target equipment type.
- Exchange specific parameters which cannot be calculated or derived from the generic parameters are assigned default values cy the network manager. If however, a user creates the generic instruction knowing nat "- targetis) of the control includes exchanges having additional fu ⁇ ct can * ' " v alues for the exchange-specific parameters, such as traffic category ana can disposition, may be specified at control creation time. Mapping rules are defined for each exchange specific control on each target equipment type supported by the control M.
- mapping the generic set of parameters to the exchange specific set the mapping process will use the nearest available value for an exchange specific parameter if the required value is not available.
- Non-generic controls such as System X Loopback can be stored and manipulated in their exchange specific form in the network manager. At implementation time, no mapping process is performed by the network manager and the control details are sent directly to the switches for implementation on the exchange.
Abstract
Description
Claims
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU38494/95A AU686470B2 (en) | 1994-11-10 | 1995-11-07 | Controlling elements of a telecommunications network |
JP8515820A JPH10508991A (en) | 1994-11-10 | 1995-11-07 | Control elements for telecommunication networks |
US08/836,301 US6377988B1 (en) | 1994-11-10 | 1995-11-07 | Controling elements of a telecommunications network |
EP95936636A EP0791275B1 (en) | 1994-11-10 | 1995-11-07 | Controlling elements of a telecommunications network |
DE69532452T DE69532452T2 (en) | 1994-11-10 | 1995-11-07 | Elements for the control of a telecommunications network |
FI971943A FI971943A0 (en) | 1994-11-10 | 1997-05-07 | Controlling elements in a telecommunications network |
NO972154A NO972154D0 (en) | 1994-11-10 | 1997-05-09 | Management of elements in a telecommunications network |
MXPA/A/1997/003436A MXPA97003436A (en) | 1994-11-10 | 1997-05-09 | Elements of control of a telecommunication network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB9422722.0 | 1994-11-10 | ||
GB9422722A GB9422722D0 (en) | 1994-11-10 | 1994-11-10 | Traffic management |
Publications (2)
Publication Number | Publication Date |
---|---|
WO1996015635A1 true WO1996015635A1 (en) | 1996-05-23 |
WO1996015635A9 WO1996015635A9 (en) | 1997-07-03 |
Family
ID=10764194
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/GB1995/002617 WO1996015635A1 (en) | 1994-11-10 | 1995-11-07 | Controlling elements of a telecommunications network |
Country Status (12)
Country | Link |
---|---|
US (1) | US6377988B1 (en) |
EP (1) | EP0791275B1 (en) |
JP (1) | JPH10508991A (en) |
KR (1) | KR970707689A (en) |
AU (1) | AU686470B2 (en) |
CA (1) | CA2203671A1 (en) |
DE (1) | DE69532452T2 (en) |
FI (1) | FI971943A0 (en) |
GB (1) | GB9422722D0 (en) |
NO (1) | NO972154D0 (en) |
NZ (1) | NZ295205A (en) |
WO (1) | WO1996015635A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6269397B1 (en) | 1997-05-05 | 2001-07-31 | Nokia Networks Oy | System and method for network element management in a Telecommunications network |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE10021738A1 (en) * | 2000-05-04 | 2001-11-22 | Siemens Ag | Coordinated network-wide administration of switching centers |
US7051101B1 (en) * | 2000-09-13 | 2006-05-23 | Emc Corporation | Methods and apparatus for controlling devices within storage network |
US8326965B2 (en) * | 2001-05-03 | 2012-12-04 | Hewlett-Packard Development Company, L.P. | Method and apparatus to extract the health of a service from a host machine |
US7003527B1 (en) | 2002-06-27 | 2006-02-21 | Emc Corporation | Methods and apparatus for managing devices within storage area networks |
US20100280855A1 (en) * | 2009-04-30 | 2010-11-04 | Vinay Gupta | Management of a first stand-alone system used as a subsystem within a second system |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1993018598A1 (en) * | 1992-03-10 | 1993-09-16 | Nokia Telecommunications Oy | Network management system |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4419667A (en) * | 1979-07-02 | 1983-12-06 | Sangamo Weston, Inc. | System for controlling power distribution to customer loads |
US4611320A (en) * | 1984-05-21 | 1986-09-09 | Siemens Corporate Research And Support, Inc. | Programmable testing analyzer |
US5426421A (en) * | 1986-04-21 | 1995-06-20 | Gray; William F. | Method of automatically managing a network or remote function-excecuting apparatus from a programable network control center |
US5008879B1 (en) * | 1988-11-14 | 2000-05-30 | Datapoint Corp | Lan with interoperative multiple operational capabilities |
FI83007C (en) * | 1989-10-05 | 1991-05-10 | Nokia Data Systems | Digital data transfer system |
US5193152A (en) * | 1989-11-03 | 1993-03-09 | Racal-Datacom, Inc. | Network management system with group naming |
US5182750A (en) * | 1990-12-31 | 1993-01-26 | At&T Bell Laboratories | Transparent remoting of switching network control over a standard interface link |
US5317742A (en) * | 1991-06-21 | 1994-05-31 | Racal-Datacom, Inc. | Dynamic translation of network management primitives to queries to a database |
JPH05236138A (en) * | 1992-02-20 | 1993-09-10 | Nec Corp | Electronic exchange |
US5583928A (en) * | 1992-06-19 | 1996-12-10 | British Telecommunications Public Limited Company | Detecting local exchange failure and resultant control of a communications network |
-
1994
- 1994-11-10 GB GB9422722A patent/GB9422722D0/en active Pending
-
1995
- 1995-11-07 AU AU38494/95A patent/AU686470B2/en not_active Ceased
- 1995-11-07 JP JP8515820A patent/JPH10508991A/en active Pending
- 1995-11-07 EP EP95936636A patent/EP0791275B1/en not_active Expired - Lifetime
- 1995-11-07 CA CA002203671A patent/CA2203671A1/en not_active Abandoned
- 1995-11-07 WO PCT/GB1995/002617 patent/WO1996015635A1/en active IP Right Grant
- 1995-11-07 DE DE69532452T patent/DE69532452T2/en not_active Expired - Lifetime
- 1995-11-07 US US08/836,301 patent/US6377988B1/en not_active Expired - Lifetime
- 1995-11-07 NZ NZ295205A patent/NZ295205A/en unknown
- 1995-11-07 KR KR1019970703096A patent/KR970707689A/en not_active Application Discontinuation
-
1997
- 1997-05-07 FI FI971943A patent/FI971943A0/en unknown
- 1997-05-09 NO NO972154A patent/NO972154D0/en not_active Application Discontinuation
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1993018598A1 (en) * | 1992-03-10 | 1993-09-16 | Nokia Telecommunications Oy | Network management system |
Non-Patent Citations (6)
Title |
---|
CAMERON ET AL.: "Integrated network operations architecture and its application to network maintenance", IEEE COMMUNICATIONS MAGAZINE, vol. 25, no. 8, NEW YORK, US, pages 48 - 53 * |
GARRISON ET AL.: "The BT Network Traffic Management System: a window on the network", BRITISH TELECOMMUNICATIONS ENGINEERING, vol. 10, no. 3, LONDON, GB, pages 222 - 229, XP000279042 * |
HONG ET AL.: "Design and implementation of a generic distributed application management system", GLOBECOM 93, vol. 1, 29 November 1993 (1993-11-29), HOUSTON, US, pages 207 - 211, XP000428055 * |
KIRIHA ET AL.: "An automatic generation of management information base (MIB) for OSI based network management system", GLOBECOM 91, SESSION 19, PAPER 5, vol. 1, 2 December 1991 (1991-12-02), PHOENIX, US, pages 649 - 653, XP000326045 * |
LIAO ET AL.: "Toward the Intelligent Integrated Network Management", GLOBECOM '90, SESSION 802, PAPER 6, vol. 3, 2 December 1990 (1990-12-02), SAN DIEGO, US, pages 1498 - 1502, XP000218826 * |
RABIE: "Evolution to multivendor Intelligent Network management", INTERNATIONAL SWITCHING SYMPOSIUM 1992, SESSION C1, PAPER 1, vol. 1, 25 October 1992 (1992-10-25), YOKOHAMA, JP, pages 60 - 64, XP000337617 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6269397B1 (en) | 1997-05-05 | 2001-07-31 | Nokia Networks Oy | System and method for network element management in a Telecommunications network |
Also Published As
Publication number | Publication date |
---|---|
US6377988B1 (en) | 2002-04-23 |
MX9703436A (en) | 1997-07-31 |
CA2203671A1 (en) | 1996-05-23 |
EP0791275A1 (en) | 1997-08-27 |
AU686470B2 (en) | 1998-02-05 |
GB9422722D0 (en) | 1995-01-04 |
DE69532452D1 (en) | 2004-02-19 |
AU3849495A (en) | 1996-06-06 |
NO972154L (en) | 1997-05-09 |
JPH10508991A (en) | 1998-09-02 |
FI971943A (en) | 1997-05-07 |
NZ295205A (en) | 1997-07-27 |
EP0791275B1 (en) | 2004-01-14 |
KR970707689A (en) | 1997-12-01 |
NO972154D0 (en) | 1997-05-09 |
FI971943A0 (en) | 1997-05-07 |
DE69532452T2 (en) | 2004-11-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5917898A (en) | Telecommunications network traffic management system | |
US5848132A (en) | Telecommunications network having resident ability to pre-book scheduled call back services | |
EP0606353B1 (en) | Congestion tuning of telecommunications networks | |
RU2157595C2 (en) | Device, system and method for remote communication to upgraded signal transmission center | |
EP0791276B1 (en) | Overload prevention in a telecommunications network node | |
WO1995015635A1 (en) | Communications network management | |
CA2298608A1 (en) | Queue system and method for point-to-point message passing | |
AU686470B2 (en) | Controlling elements of a telecommunications network | |
CA2084430C (en) | Method of transferring between centres the handling of an active connection between a user, on the one hand, and a mobile terminal, on the other hand | |
WO1996015635A9 (en) | Controlling elements of a telecommunications network | |
EP0726018B1 (en) | Telecommunications network traffic management system | |
EP0655182B1 (en) | Centralized command system for a telecommunications network | |
US20040131171A1 (en) | Call center apparatus for automatically distributing call through public telephone network and controlling method for call center apparatus | |
EP1086594B1 (en) | Programming call-processing application in a switching system | |
CN112583622B (en) | Method and system for reporting fault event information | |
CN101159885A (en) | Method of implementing bandwidth distribution service on demand | |
MXPA97003436A (en) | Elements of control of a telecommunication network | |
US6064726A (en) | Fully flexible routing system | |
US6047385A (en) | Digital cross-connect system restoration technique | |
WO1996029830A1 (en) | Service provision in a telecommunications network | |
US6732169B1 (en) | Network transmission circuit control method and system | |
KR930006359B1 (en) | Method for controlling a particular route using cancel from function | |
CA2237623C (en) | Load sharing group of service control points connected to a mediation point for traffic management control | |
CN100446582C (en) | Method for allowing information quantity management | |
CN1162382A (en) | Controlling elements of telecommunications network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 95196007.5 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AL AM AT AU BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU IS JP KE KG KP KR KZ LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TT UA UG US UZ VN |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): KE LS MW SD SZ UG AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 295205 Country of ref document: NZ |
|
ENP | Entry into the national phase |
Ref document number: 2203671 Country of ref document: CA Ref document number: 2203671 Country of ref document: CA Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1995936636 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 971943 Country of ref document: FI |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/1997/003436 Country of ref document: MX Ref document number: 1019970703096 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 08836301 Country of ref document: US |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 1-18,DESCRIPTION,PAGES 19-22,CLAIMS,AND PAGES 1/5-5/5,DRAWINGS,REPLACED BY CORRECTED PAGES BEARING THE SAME NUMBER |
|
WWP | Wipo information: published in national office |
Ref document number: 1995936636 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 1019970703096 Country of ref document: KR |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1019970703096 Country of ref document: KR |
|
WWG | Wipo information: grant in national office |
Ref document number: 1995936636 Country of ref document: EP |