WO1996010313A1 - Systemes d'acces a distance - Google Patents

Systemes d'acces a distance Download PDF

Info

Publication number
WO1996010313A1
WO1996010313A1 PCT/GB1995/002301 GB9502301W WO9610313A1 WO 1996010313 A1 WO1996010313 A1 WO 1996010313A1 GB 9502301 W GB9502301 W GB 9502301W WO 9610313 A1 WO9610313 A1 WO 9610313A1
Authority
WO
WIPO (PCT)
Prior art keywords
remote access
target equipment
data
management system
request
Prior art date
Application number
PCT/GB1995/002301
Other languages
English (en)
Inventor
Alastair Montgomerie
Jeffrey Edward Deslandes
Robert Malcolm Ball
Dennis John Tricker
Keith Eric Nolde
Original Assignee
British Telecommunications Public Limited Company
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 British Telecommunications Public Limited Company filed Critical British Telecommunications Public Limited Company
Priority to AU35715/95A priority Critical patent/AU3571595A/en
Priority to EP95932821A priority patent/EP0784900A1/fr
Priority to CA002200862A priority patent/CA2200862C/fr
Priority to JP8511510A priority patent/JPH10506250A/ja
Publication of WO1996010313A1 publication Critical patent/WO1996010313A1/fr
Priority to US08/822,132 priority patent/US6073174A/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M11/00Telephonic communication systems specially adapted for combination with other electrical systems
    • H04M11/002Telephonic communication systems specially adapted for combination with other electrical systems with telemetering systems

Definitions

  • the present invention relates to remote access for distributed equipment, and particularly, but not exclusively, to telemetry and telemetry systems.
  • the cost to utility companies, such as gas, electricity and water suppliers, of manually reading meters is substantial. Consequently, meters are read infrequently and householders frequently receive estimated accounts rather than those based on actual consumption. Further difficulty can arise when meter readers are unable to obtain access to meters.
  • Telemetry is a remote access process whereby meters are connected to a communications network and can be accessed and read over the network typically from a single location, for example at premises owned by a utility. The process of reading the meters is typically carried out by a suitable computer system connected to the network by a modem and running appropriate communications and data retrieval software.
  • a remote access management system for accessing remote units to obtain data therefrom by means of a communications network, the system comprising:
  • an access operation initiator responsive to an access operation request to initiate an access operation by outputting control information, including the routeing data, to the communications network;
  • Embodiments of the present invention can be described as a remote access management system for managing communication with distributed target equipment over a communications network, said system comprising: means for receiving a request for an access operation to selected target equipment; means for providing routing information for target equipment identified by said request; means for initiating an access operation to said target equipment, said means including means arranged to transmit control information, including said routing information, to a communications network platform arranged to receive said control information and operate said access operation over a communications network; means for receiving and storing data from said network platform in response to said access operation; and, means for forwarding to the originator of said request data indicative of said stored data.
  • the person or organisation requesting an access operation for example a utility
  • the customer or the request originator
  • the person or organisation to whose equipment the operation is directed will be called “the target” . This reflects the fact that it is likely to be the person or organisation requesting access who will be responsible for the costs at first instance.
  • Such markets may include: stock monitoring, eg in vending machines, petrol stations, and bulk storage tanks; and, environmental monitoring, eg temperature, water, purity, or pollen count.
  • the remote access system can be provided by the communications network operator, or by an independent entity, and not necessarily by a customer such as a utility
  • the customer does not then need to know the routing information, for example a directory number (DN), necessary to initiate a remote access call to target equipment since this information is provided by the remote access management system.
  • DN directory number
  • PSTN public switched telephone network
  • the communications network is a PSTN, this potentially gives extremely wide access to equipment with which remote access operations might be recognised.
  • the network could be any other suitable type of communications network, for example a packet switched data network.
  • the initiating means is preferably arranged to provide control information which includes an indication of the type of communications operation to be initiated with the target equipment.
  • a communications operation preferably can be either substantially a read operation or substantially a write operation.
  • a read operation involves reading information from target equipment, although the setting-up of the read operation does involve sending some controlling information to the target equipment.
  • the write operation involves sending information to the target equipment, although status information will typically be returned to indicate whether the write operation was successful or not.
  • the remote access management system preferably comprises means for validating requests, the requests including data identifying the originator of the request and the validating means including means to compare the identity of the request originator with a stored set of valid request originators.
  • the rights of request originators to access equipment identified in the request can be checked against respective information stored with respect to the system
  • the remote access management system operator can maintain control over which customers have access to the system, and to which target equipment each customer has access.
  • the remote access management system includes a stored set of unique references, where each of the references corresponds to one or more pieces of target equipment.
  • a valid request typically includes at least one reference which matches one of the stored references. Obviously, therefore, customers making requests need to be aware of their valid references.
  • An advantage of this arrangement is that a customer can request access to multiple pieces of target equipment with a single equipment reference in a single request.
  • the remote access management system preferably comprises timed trigger means for triggering the initiating means to initiate calls to target equipment at pre ⁇ selected intervals or times. In this way, customers can be supplied with, for example, meter readings for all their target meters at regular intervals, with the minimum of effort on the part of the customer.
  • the remote access system has facility to initiate one or more calls on demand. This facility enables, for example, a customer to check a single meter reading on demand.
  • the remote access management system further comprises up-datable database means containing information including network addresses of all potential target connections accessible over the communications network and the physical locations of said network addresses. This information is particularly useful for establishing lists of targets which would be accessible by the system when suitable target equipment is installed
  • the remote access management system comprises up-datable database means containing for each piece of target equipment accessible by said system information including the type of each piece of the target equipment and respective data communications access requirements for said target equipment. This information forms part of the control information which passes to the communications network platform and is essential when different types of target equipment can be accessed by the system and the access requirements of the system are not provided by the customer in a request. An arrangement of this type minimises the amount of information which needs to be known by customers.
  • the remote access management system is arranged to provide target equipment routing information, for at least some pieces of target equipment, including the communication network line termination address of an interface means and a port number of said interface means, whereby individual pieces of target equipment connected to said interface means are accessible by specifying the respective port on said interface means Therefore, multiple pieces of target equipment can be connected to one interface means and can be accessed individually.
  • the present invention provides a remote access system for communicating with distributed target equipment over a communications network, said system comprising a remote access management system as described above and a communications network platform comprising. means to receive control information, including target equipment routing information, from said remote access management system; means to establish access with said target equipment and to receive data, in response to said access, from said target equipment; and means to return at least some of said received data to said remote access management system.
  • control information including target equipment routing information
  • the present invention may be important that normal telephony is substantially undisturbed. Therefore, for instance in telemetry, one aspect of the present invention may be to ensure that a telephone call always takes precedence over a telemetry call.
  • a telemetry call will, preferably, clear down if an adjacent telephone (or other communications equipment) goes off-hook, and also an incoming telephony call will be put through over an on-going telemetry call.
  • This aspect of the present invention is discussed in more detail in the Applicants' co-pending application number EP94302620.3.
  • the target equipment co- terminates a line in the communications network with other communications equipment, for example a telephone or a facsimile. It may then be preferable that the call to the target equipment is a no-ring call (NRC). In this way, the call does not cause, for example, a telephone co-terminated with the target equipment or interface to ring. The whole operation is therefore transparent to customers at target sites.
  • the means to establish the access with the target equipment preferably includes means to schedule calls to target equipment.
  • a request which comprises one or more lists of references to target equipment to be accessed, received from the management system can take place at non-peak periods for the relevant communications network, for example during the night with regard to a PSTN, and any results can be delivered back to the customer in a single communication after the whole process is complete.
  • the remote access system further comprises means for billing customers.
  • a utility would be the customer and, hence, would be billed for the relevant data transfer operation.
  • the owner of the target equipment is likely also to be the customer and, hence, would be billed.
  • customers are billed on a per successful operation basis rather than on communication network connection time. This has the advantage that costs to customers are easily predictable and customers do not get billed for failed operations (which might actually incur some communication network connection time).
  • the remote access system preferably provides further functionality.
  • the management system may further comprise means for converting a non-standard customer request format to a format readable by the request processing means.
  • the means for converting could be for instance a software filter which simply reads the customer request, and re-formats it to the format required by the request processing means
  • the means for converting could be part of the management system per se, or it could be part of a customer system which is arranged to interface with the management system during request operations.
  • the remote access system may further provide means for detecting fraudulent behaviour, for example, by detecting if there is an attempt to credit a utility meter using telemetry by someone who is not authorised to do so
  • the system may include means for detecting leaks in utility supply, for example, by recognising when meter readings rise at times when they should not
  • a remote access management system for controlling communications between customers and distributed target equipment over a communications network, said system comprising: means for managing communications with a customer, means for managing communications with communications equipment in the communications network, whereby communications with target equipment can be managed; means for storing data received from either the customer or the communications equipment; and means for forwarding data representative to data stored by said means for storing to either said customer or said communications equipment.
  • the remote access management system is arranged to receive data from said communications equipment, store said data, and forward data representative of said stored data to a customer.
  • remote access may be initiated by target equipment instead of, or as well as, by the customer. Remote access may then be initiated by the target equipment to the customer or other designated destination.
  • Examples of circumstances in which it might be beneficial to have a bi ⁇ directional target equipment access capability are for vending machines to indicate when they are near empty and for fuel storage facilities to indicate when fuel reserves are low Such information may be communicated back to the customer Also, in more serious situations, for example as a result of on-going vandalism of customer equipment or failed refrigeration in a large food storage premises, where a faster response would be desirable, a target equipment-initiated remote access might automatically trigger an alert being sent to the police, or to an engineer via, for example, a radio pager.
  • Figure 1 represents a logical architecture for a telemetry system, showing system domains and relationships between the domains;
  • Figures 2 to 7 represent the views which each system domain has in the logical architecture, with respect to the other system domains;
  • FIG 8 is a flow diagram representing TIU and meter enrolment procedure
  • Figure 9 is a flow diagram representing TIU and meter installation procedure
  • Figure 10 is a flow diagram representing an automatic meter read process
  • Figure 1 1 is a flow diagram representing a multiple meter broadcast process
  • Figure 1 2 is a diagram which illustrates features of the present invention applied to a vending machine.
  • FIG. 1 shows a schematic, overall architecture for a telemetry system suitable for automatic meter reading (AMR) operations over a PSTN
  • AMR automatic meter reading
  • a network management domain A2 contains systems and functionality to provide network and element management for telemetry
  • a billing domain A3 contains systems and functionality to provide billing and log information to the utilities
  • a network domain A4 contains all network speech transmission paths and telemetry call initiation equipment.
  • Utilities which require AMR operations are represented by the a utility domain A5, and the consumers are represented by a consumer domain A6
  • the lines adjoining the domains represent relationships which exist between domains The following description deals in turn with each domain, and the view each domain has of its relationships to the other domains
  • the service management view in Figure 2 shows the architecture from the perspective of the service management domain A 1
  • the service management domain A 1 comprises a telemetry service centre (TSC) 1 1 , a telemetry service management system (TSMS) 1 2, a consumer service system (CSS) 14, a consumer service centre (CSC) 1 6 and a pre-process database (DB) 1 5.
  • TSC telemetry service centre
  • TSMS telemetry service management system
  • SCS consumer service system
  • CSC consumer service centre
  • DB pre-process database
  • the TSC 1 1 is the primary contact point for utilities for queries or fault reporting.
  • the TSC 1 1 has access into the TSMS 1 2, the CSS 14 and the billing domain A3, whereby a utility can contact a TSC operator with a query, and the operator can attempt to answer the query. Any query which highlights a telemetry fault or a network fault, which cannot be dealt with by the operator, is passed to a respective technical division to be dealt with. Consumers are also able to log queries or faults to the TSC 1 1 via the CSC 1 6.
  • the TSC 1 1 has access to call logs held on the TSMS 1 2, and also access to a telemetry platform (TP) 41 (described in more detail below in the 'Network
  • the TSMS 1 2 is responsible for processing AMR requests from the utility and for utility enrolment, consumer list registration and consumer list updating.
  • the TSMS 1 2 is also responsible for supplying information to the billing domain A3 for billing purposes.
  • the basic information which needs to be provided for utility enrolment includes: utility ID/name, for the utility to be able to identify itself for an AMR service; a telemetry reference number, which is an identifier common to the PSTN operator and the utility which uniquely identifies the telemetry interface unit (TIU)/meter address to both parties; a meter reference number, which is the key data component which the utility uses to identify their consumer for AMR service, which is unique to a utility; • a meter address, which is used as a cross-reference to check that the requested meter corresponds to the telephone number and address for a consumer held by the PSTN operator; a TIU type, which defines the protocol used to access the TIU; and a TIU address/port number, which consists of the unique
  • the TSMS 1 2 comprises a data interface 1 1 1 for connecting the TSMS 1 2 with other components of the architecture, a programmable processor 1 1 3 connected to the interface 1 1 1 via a data bus 1 1 2, and a storage device 1 14 connected to the programmable processor 1 1 3.
  • a suitable programmable processor 1 1 3 is a SUN Microsystems, SPARCStation
  • the interface 1 1 1 1 provides line connections between to the billing domain A3, the utility domain A5, the DB 1 5, the TP 41 and the TSC 1 1 .
  • the interface 1 1 2 is connected to the programmable processor 1 1 3 over the data bus 1 1 2.
  • the interface 1 1 1 1 receives transmissions to the TSMS 1 2 and codes the transmissions to identify their origin to the programmable processor 1 13. Likewise, the interface 1 1 1 also sends transmissions from the processor 1 1 3, by directing them to the correct destinations.
  • a suitable interface 1 1 1 is an Ethernet interface having a connection to the data bus 1 1 2 and a connection to an Ethernet local area network to which the other components of the architecture are connected.
  • AMR requests are made to the TSMS 1 2 from a utility's telemetry interface system (TIS) 51 , via the interface 1 1 1 .
  • TIS utility's telemetry interface system
  • a request comprises, a utility ID, a meter reference number, and a meter address for cross-referencing purposes.
  • the TSMS 1 2 validates each AMR request from the TIS 51 by checking the access rights a utility has in relation to the meter(s) specified in the request, by cross-referencing each request with a list of all the valid meter addresses held in a database stored on the storage device 1 14 (where the list was registered by the utility when the utility was originally enrolled, and may have been updated since).
  • the TSMS 1 2 When validated, the TSMS 1 2 adds directory numbers (DN) to the AMR requests, which numbers it obtains from the CSS 14, via the DB 1 5. The information is then forwarded to the TP 41 . This enables calls to consumers to be set up by the TP 41 .
  • DN directory numbers
  • the TSMS 1 2 is able to deal with batch AMR requests in which a utility sends a list of requests for AMR, in one operation, which are stored on the storage device 1 14.
  • the TSMS 1 2 then processes the whole list of requests, as described above, and sends the list to the TP 41 .
  • the TP schedules the calls to be initiated at a suitable time, typically at a non-peak time for the communications network.
  • the TP 41 receives all the results of successful, or unsuccessful, AMR, it sends them, en masse, via the TSMS 1 2, to the utility (this process is discussed in more detail below) .
  • the TSMS 1 2 is also able to initiate AMRs for predefined lists of consumers (which were supplied by a utility at an earlier date and are stored in the storage device 1 14) .
  • This facility can be instigated by a simple request from a utility, or automatically, whereby the TSMS 1 2 adds routing information to the requests in the list, and, at regular, predefined intervals, automatically sends the list to the TP 41 which schedules and initiates the AMR calls.
  • the TSMS 1 2 keeps call logs on the storage device 1 14, including a valid readings log and an exceptions log which can be accessed by the TSC 1 1 , or directly by the utility domain A5 via the TIS 51 . Direct access by the utility domain A5 makes accessible to the utility up-to-the-minute information on performance and potential billing.
  • the CSS 14 is a programmable database which holds records of the availability of telemetry services for each telephone line in the PSTN.
  • a suitable programmable database is an IBM compatible personal computer, with hard disk storage for holding the database, and with suitable communications and database software for accepting manually entered information (or electronically transmitted information) and using this information to update the database as required.
  • the database information is provided by the PSTN operator from the network management domain A2.
  • the CSS 14 holds a corresponding DN (also provided by the PSTN operator) and a corresponding meter reference number which is an identifier common to the PSTN operator and the utility, which uniquely identifies a meter/consumer addresses to both parties.
  • the CSS data also includes a flag against each line which supports telemetry. This flag assists in normal line fault repair by indicating to an engineer that an extra piece of CPE may need to be disconnected to fix a fault.
  • the CSS 14 forwards DN data records to the DB 1 5, as required, in response to the arrival of new or updated DN data records.
  • the DB 1 5 also receives details of corresponding telephone exchange access requirements from the network management domain A2.
  • the telephone exchange access details typically include exchange type and required method of call set-up, for example which signalling is required to set up a no-ring call
  • the required DN is retrieved from the DB 1 5 along with the telephone exchange access details, ready to be sent to the TP 41 .
  • the information stored on the CSS and the DB is updated regularly by the network management domain A2 and the utility domain A5 (via the TSC or the TSMS 1 2).
  • the CSC 16 is the main contact point for the consumer domain A6.
  • the CSC 1 6 like the TSC 1 1 , is a human operator with the ability to access the CSS 14 and the TSC 1 1 for the purposes of receiving fault reports from the consumer domain, entering details of fault reports onto the CSS, and forwarding telemetry faults to the TSC 1 1 where appropriate.
  • the fault reporting procedures are in common with those commonly adopted for standard communication networks.
  • the network management role in the telemetry system is similar to the network management role in a standard communications system.
  • the role includes monitoring for and raising alarms, monitoring performance, and varying traffic flow where required, to prevent line overloads or to re-direct traffic around line failures.
  • Figure 3 represents the relationships between the network management domain A2, the service management domain A1 and the network domain A4.
  • the network management domain A2 comprises components including an operations management centre (OMC) 23, a network traffic management system
  • NTMS network management centre
  • NMC network management centre
  • NOU network operations unit
  • the NMC 21 handles network traffic in the normal way. However, it is also able to prevent network overloads by reducing the telemetry call rate of the TP 41 , if necessary, as well as controlling restoration of control rate.
  • the NOU 22 receives consumer fault reports from a network CSS which may be resolved in the normal way: any unresolved faults being returned to the
  • the NOU 22 also receives alarms raised by the TP 41 , in connection with failed call attempts, which again are either dealt with in the normal way or sent to the TSC 1 1 .
  • the OMC 23 receives requests from the NMC 21 via the NTMS 25 to control the calling rate of the TP 41 , and sends controlling signals to the TP 41 to modify the calling rate accordingly.
  • the NTMS 25 polls the exchanges in the network in the normal way and provides performance data from which network management reports can be compiled.
  • the NTMS also sends control information from the NMC 21 to the OMC relating to call flow modification, and receives from the TP 41 details of calls made by the TP for performance measurement purposes.
  • Billing View Figure 4 represents the relationship between the billing domain A3, the service management domain A1 and the utility domain A5.
  • the billing domain A5 comprises a billing system 31 which receives information from the TSMS 1 2, which it converts to billing information
  • the billing information may be passed to the utility as a paper bill, or may be forwarded to the utility electronically, for example by communications line directly into the TIS 51
  • the billing system comprises a computer system, for example an IBM compatible personal computer, running software for collating the information into itemised bills for each utility.
  • Typical billing information received from the TSMS 1 2 includes - date of reading, time of read/write, whether successful or unsuccessful, and utility reference number
  • the billing system collates the billing information into an itemised bill and initiates the sending of the bill to the utility by computer communications over a suitable link to the TIS 51
  • the billing criteria in this case is on a per-read operation basis rather than on the basis of network connection
  • the network domain A4 and the service management domain A1 , the utility domain A5, the network management domain A2, and the consumer domain A6, are represented in Figure 5.
  • the network domain comprises a TP 41 , local exchanges (LE) 42 and digital main switching units (DMSU) 43 (only one of each shown) .
  • the TP is responsible for accepting AMR requests from the TSMS 1 2 and initiating an AMR over the communications network.
  • the role of the TP 41 can be carried out by a call processing system
  • a suitable call processing system is BT's speech applications platform (SAP), which is described in detail in the applicant's co-pending PCT patent application number WO/GB94/01429 filed on 1 st July 1 994, the contents of which are incorporated herein by reference.
  • SAP BT's speech applications platform
  • the TP 41 which takes call requests from the TSMS 14, sets up calls to a TIU 63 in the consumer domain A6, over a PSTN.
  • the TP 41 is connected into a DMSU 43 in the trunk network of the PSTN, which enables calls to be sent to any TIU connected to the PSTN.
  • the TP 41 schedules one or more no-ring calls (NRC) to TIUs on the PSTN.
  • NRC no-ring calls
  • the details of how NRCs are established are discussed in detail in the applicants co-pending European patent application number EP94302756.5, the contents of which are incorporated herein by reference
  • the signalling protocol for managing no-ring calls is the BT variant of the CCITT Signalling System Number 7, commonly known as C7 signalling.
  • the TP 41 has the facility to re-schedule and re-try failed calls a specified number of times, based on a re-try algorithm.
  • the algorithm re-schedules a failed call for the same night, then for several subsequent nights, and eventually during the day if the call continually fails All details of successful and failed calls are sent to the TSMS 14 to be logged. Apart from telemetry equipment or network failures, calls fail when a telephone line is busy for other reasons, for example a telephone line is engaged.
  • the TP 41 is designed so that if a telemetry call is in progress when an incoming or outgoing telephone call is attempted, the telemetry call is cleared down immediately in favour of the telephone call.
  • This form of call prio ⁇ tisation is covered in greater detail in the applicant's co-pending European patent application number EP94302620.3, the content of which is incorporated herein by reference. Again, the procedures are managed using C7 signalling.
  • the TP 41 is able to scatter calls by geographic area, if necessary, to prevent call failures due to too few multi- frequency (MF) detectors in the LEs.
  • MF multi- frequency
  • the performance of the TP 41 can be monitored, and statistics taken, by the NTMS 25.
  • call rates made by the TP 41 can be decreased or increased by the OMC 23 in response to increases and decreases in PSTN line demand, flagged by the NMC 21 .
  • the TP is able to initiate standard 'ring' calls over the PSTN for consumers configured to activate on a ringing call.
  • the nature of the relationship between the utility domain A5 and the other domains could depend entirely on the level of automation of each utility.
  • the utility is provided with a TIS 51 which includes a suitable interface which enables the telemetry system (via the TSMS 1 2) to deal with utilities at all levels of automation. With this interface, the utilities can use whichever legacy system they are running, without needing to upgrade. However, the applicants believe that in time all utilities will upgrade their legacy systems to be directly compatible with telemetry systems.
  • a TIS 51 comprises a software application running on a computer system, for example a SUN Microsystems SPARCStation 5 workstation.
  • the workstation provides a windows, icons, menus and pointer (WIMP) desktop from within which the TIS 51 application can be selected from a menu.
  • the TIS 51 application runs within a VT100 window within the desktop.
  • the TIS 51 application interface uses a character based forms application, using Oracle SQL * Forms V3. This allows the utility to access the TIS 51 system functionality and therefore the telemetry system. All telemetry functions accessible by the utility are accessed via the TIS 51 , which is connected to the
  • TSMS 1 2 by a communications link, which is typically an analogue PSTN line.
  • the TIS 51 also provides a simple interface to the legacy billing and consumer information systems of the utility. This supports simple conversion from existing information held by the utility to information which is compatible with the telemetry system.
  • the main functions supported by the TIS 51 are: maintenance of customer and meter information; maintenance of meter access lists; • requests for meter consumption measurement (single tariff), on a priority ad hoc or regular basis; interpretation of return results, and management reporting; error handling; meter/TIU installation and enrolment; security; retention of data for a number of weeks.
  • the TIS 51 also receives billing information from the billing domain A3, via the TSMS 1 2.
  • the billing information is processed by the utility and distributed to consumers in the consumer domain A6 in the normal way
  • the consumers have access to the service management domain A1 to report faults or make queries, usually by telephone, although in future consumers may own suitable terminal equipment to communicate directly with the CSC 16
  • the TIU 63 connected to a meter 631 at a consumer premises, is connected to a telephone line termination, and is accessible by the TP
  • billing information could be forwarded directly from the utility domain A5 to consumers in the consumer domain A6 via the TSMS 1 2
  • Suitable terminal equipment would be a display device such as a printer or VDU
  • Construction occurs on the TIS 51 , for example using information from the utilities' 30 legacy billing and customer information system.
  • the information on the TIS 51 is arranged into a format readable by the TSMS 1 2.
  • the information might include, for example, the following- customer reference; property address; postcode; house number; house name. This information is then transmitted to the TSMS 1 2.
  • the TSMS 12 extracts the postcodes from the TIS 51 details and forwards the postcodes to the CSS 14.
  • the CSS 14 compares the postcodes from the lists created by the TSMS 1 2 with postcodes of customers which can be supported by the telemetry service.
  • the criteria for selecting which consumers are accessible also includes whether a consumer is attached to a local exchange which can support a no-ring call (if no-ring calls are essential).
  • the TSMS 1 2 compares the details of the properties returned by the CSS 14 with the original address information provided by the TIS 51 , to provide a list of accessible consumers.
  • PINs the utility creates a register of consumers who have recently or will shortly have meters and TIUs 63 installed to support the telemetry service For each consumer selected, an installer PIN is defined. This PIN is used once a TIU 63 and meter have been installed to enrol these to the telemetry service. The list is sent to the TSMS 1 2.
  • the TSMS 12 sends a list of consumer locations which already have occurred to the utility TIS 51 .
  • the TIS 51 receives the list and updates its records accordingly.
  • the utility is now in a position where it can request meter reads from meters which have been installed.
  • TIU 63 and a meter The physical operation of installing a TIU 63 and a meter is carried out by an installer at, or nearby, a consumer's premises. Once installed, both TIU 63 and meter need to be registered with both the telemetry service provider and the utility.
  • the 0800 call from a telephone which co-terminates the telephone line connected to the target equipment 63 on the PSTN.
  • LE 42 receives the call request and forwards it with the CLI of the calling line to the DMSU 43, as it would with any 5 telephony call.
  • the DMSU 43 translates the 0800 call to the DN of the TP 41 and routes a call to the TP.
  • the TP 41 answers the call and receives the CLI information of the caller.
  • the CLI is the first identification of the target equipment received by the TP 41 .
  • the TP 41 in response to the call, the TP 41 prompts, 10 using a pre-recorded voice message, for enrolment data from the installer.
  • CLI are forwarded by the TP 41 to the TSMS 1 2.
  • Request test call the TSMS 1 2 initiates an NRC to the TIU 63 or meter.
  • NRC the TP 41 receives the request from the TSMS 1 2 and initiates the call to the TIU 63.
  • Request meter reading the TIU 63 receives the request and indicates to the meter that a reading is required.
  • the TIU 63 receives the reading and returns it to the TP 41 .
  • the TP 41 initiates a call to the installer and sends a pre-recorded announcement indicating the result of the test.
  • the utility TIS 51 identifies the meter(s) to be read, either by reference to a list, stored on a database and accessible by the
  • Validate and store list the TSMS 1 2 checks that this utility is allowed to read the meter(s) on the list and obtains the DNs for the NRCs and the alert tones to be used from information held on the DB The exceptions log on the TSMS 1 2 is updated with any invalid meter read requests.
  • Schedule read request the list, as amended, is forwarded from the TSMS 1 2 to the TP 41 .
  • the list has a low scheduling priority so that the calls are made at the most convenient time for the network, for example at low network usage times during the night.
  • a single read has a high scheduling priority so that it is initiated as soon as possible, for example, so that a utility making a billing enquiry can access a meter in near-real time to provide a rapid response to a consumer enquiry.
  • Schedule readings the TP 41 schedules the start of the task.
  • 420 Initiate NRC: for each read request in the list in turn, the TP 41 tries to set up a NRC to the TIU 63. If successful a speech path is established. If unsuccessful, a message to that effect, with a reason, is logged in an exceptions log on the TP 41 . The exact details of the NRC setup and clear down are dealt with in the applicants' co-pending European patent application number EP94302756.5.
  • 430 Send reading 1 : the meter sends the meter reading to the TIU 63 (if not pulsed metering) .
  • the TIU 63 checks the reading received from the meter, and if valid, sends the meter reading to the TP 41 ; otherwise it send a failure reason code.
  • Receive meter reading the TP 41 checks and records the received reading in a valid readings log, or updates the exceptions log with any failure reason code, and re-schedules a call dependant on the failure code (eg. if line engaged).
  • Call clearing the TP 41 requests the DMSU 43 to clear the call. The DMSU 43 passes the request to the LE 42 which clears the call. The LE 42 returns a message to the TP 41 that the call is cleared.
  • 450 Repeat 'initiate NRC to 'clear call" as necessary: the TP 41 attempts a NRC for the next request in the list, if there is one.
  • TSC 1 1 others are referred back to the utility.
  • billing information is derived from the valid readings and exceptions logs by the TSMS 1 2, and billing information is returned to the billing domain via the TSC 1 1 . Bills for telemetry are then forwarded periodically to utility.
  • a broadcast function is required so that certain desirable features of a telemetry service can be supported.
  • Features include, for example, automatic modification of the value of one unit of measure on a number of meters in response to a change in the cost of supply (eg 1 unit of water may change from 100 litres to 85 litres).
  • a broadcast function may also form the basis whereby remote control of equipment, for example central heating systems and the like, can be achieved, although strictly speaking this would not be 'broadcast' .
  • the utility TIS 51 identifies the meter(s) to be broadcast to, either by reference to a list, stored on a database and accessible by the TSMS 1 2, or by sending a list to the TSMS 1 2.
  • 505 Validate and store list the TSMS 1 2 checks that this utility is allowed to broadcast to the meter(s) on the list and obtains the DNs for the NRCs and the alert tones to be used from information held on the DB 1 5. The exceptions log on the TSMS 1 2 is updated with invalid meter broadcast requests.
  • Schedule broadcast request the list, as amended, is forwarded from the TSMS 1 2 to the TP 41 .
  • the list has a low scheduling priority so that the calls are made at the most convenient time for the network, for example at low network usage times during the night.
  • a single broadcast has a high scheduling priority so that it is initiated as soon as possible, for example, when a consumer pays an overdue bill, the meter needs to be credited immediately if re-connection of a consumer's supply is required.
  • the TP 41 If the download is unsuccessful, a failure message is sent to the TP 41 with a reason code, which updates the TP's exceptions log If the download is successful, the meter sends a corresponding report to the TIU 63, which is forwarded to the TP 41 .
  • Call clearing the TP 41 requests that the DMSU 43 clears the call. The request is forwarded to the LE 42 to clear the call The LE 42 sends a response of call cleared back to the TP 41 .
  • 550 Repeat steps 'schedule calls' to 'clean call' as necessary: the next request on the list, if any, if processed.
  • billing information is derived from the valid download log and the exceptions log by the TSMS 1 2, and billing information is returned to the billing domain via the TSC 1 1 , which information is used to bill the utility.
  • a template is a data structure comprising fixed and replaceable parameters
  • the fixed parameters comprise information required to tell the TP 41 how to communicate with a certain type of meter TIU combination (eg baud rate of TIU, login sequence and shutdown sequence) .
  • the replaceable parameters comprise identifiers which correspond to information required to allow the TP 41 to connect to a specific meter of the specified type at a specific consumer premises (eg TIU port number and meter authentication code). Replaceable parameters may also define the type of operation required, for example meter read operations or broadcast to meter operations.
  • templates greatly enhances the flexibility of the remote access systems to access different types of target equipment, since information relating to all known types of target equipment is maintained by the TSMS 1 2 and can be passed as required with all requests to the TP 41 .
  • a basic TIU 63 is line powered, and has a fairly low modem speed ( 1 200 bit/s) . However, once a call is established, typically there is a transparent connection between the remote access system and the TIU 63, and data transfer rates can therefore be chosen for maximum efficiency. TIUs 63 can have various levels of functionality and use modems of various speeds. Basic TIUs 63 can be made very cheaply with the provision for more elaborate design for high-usage sites.
  • the remote access system supports communications to as many types of equipment as possible.
  • the focus is likely to be communications with utility meters.
  • Standard protocols are used where they exist, in particular IEC1 107 (FLAG), and any software which enables translation between different protocols (eg CHIRPS) .
  • CHIRPS any software which enables translation between different protocols
  • Templates are stored as ASCII-formatted data files in memory on, or associated with, the TP 41 (an example template is shown in Table 3).
  • a template exists for each TlU/meter combination supported by the telemetry system.
  • a template is chosen on a per call basis by the TP 41 , according to meter type, TIU
  • the call request also includes the replaceable parameter values to be combined with the fixed parameter information in the template which in combination form a complete data record necessary to carry out an AMR or other operation with a specific TIU 63 and meter.
  • parameters have various types according to Table 1 .
  • Parameter types may exist, but these are the main types. Parameter types closely resemble those found in general purpose computer programming languages, for example the C programming language. Parameter types are recognised by data interpreters associated with both the TP 41 and the TIU 63, which interpret each character in turn on receipt of a data record.
  • Table 2 lists all the replaceable parameter types which have been defined for this example.
  • Table 3 illustrates an example template which would be stored on the TP for a specific TlU/meter combination.
  • a "%" followed by an alphanumeric character indicates a replaceable parameter.
  • the call request includes what is known as a WRITE_DATA block, which holds all the information used for replaceable parameters. %0 is taken to be the first parameter in the block, % 1 the second, %A is the eleventh and %Z is the thirty-sixth parameter in the block. Each parameter can be referenced zero or more times in the template. Each parameter comprises a parameter data type, a data length indicator and the data itself .
  • the record illustrated in Table 4 would also contain standard protocol information used for communication management purposes.
  • the information would include a message header which is recognised by the TIU 63, which header would indicate the start of the record to the TIU 63 and would include an indication of the length of the whole record, and checksum information to ensure that data has been transmitted without error.
  • the information in the data record is compiled by the TP 41 in response to a call request.
  • the record is then transmitted to the TIU 63 and a reply is awaited up to a maximum time-out of 5 seconds.
  • a time-out would result in one or more re-tries by the TP 41 , followed by an entry by the TP 41 into an exception log to the effect a failure has occurred.
  • Data transmission is supported by a standard transmission protocol supported by the TP 41 and the TIU 63, for example the V.23 protocol.
  • the TIU 63 replies to the message from the TP 41 , the information is validated and the meter information is returned to the originator via the READ DATA field in the record passed back to the TSMS 1 2.
  • the response to the "K” command is verified using an internal challenge/response function in the TP 41
  • the response to the "R" command a read data string, is returned to the originator via the TSMS 1 2, in the READ_DATA block.
  • the block holds the value 896543.
  • the above example does not include communication management data, for example header and checksum information. However, this information would be included in practice, and would conform to a known standard, for example X.25.
  • the link between the TIS 51 and TSMS 1 2 is based on the TCP/IP protocol. Each message is encapsulated within a file which is transferred over
  • TCP/IP using a file transfer program (ftp).
  • the actual medium of the connection is a dial-up link which is dependent on a utility's requirements, such as X.25, PSTN or ISDN.
  • a vending machine 700 includes a micro-processor 705 for controlling the reporting process.
  • a suitable micro-processor is an Intel 80286 processor running an operating system and software suitable for control and communication applications.
  • the software is stored in a main memory 710 accessible by the processor 705.
  • Software for controlling the communications operations is also stored in the main memory 710.
  • the processor 705 has a data bus 720 via which all data external to the processor can be transmitted or received.
  • the data bus 720 is connected to a data interface 730.
  • the data interface 730 has two further connections of which one connection is to an interface unit 740 (IU) which comprises a modem (not shown).
  • the interface unit 740 is equivalent in operation to a TIU 63.
  • the IU 740 is connected via a telephone line, or other suitable communications link, to a LE 42.
  • Standard communications software for example the Procomm script language, can be arranged to support all communications between the equipment and the outside world using, for example, a Hayes compatible modem.
  • the other connection from the data interface 730 is to sensing equipment
  • the sensing equipment 750 for sensing, via sensing lines a, b and c, whether products A, B or C have run out or are depleted beyond an acceptable product-low threshold.
  • the sensing equipment 750 comprises digital circuitry to convert an electrical signal received from one of the sensing lines into a coded signal representative of the signalling line. The coded signal is sent to the processor 705 running the control software.
  • sensors 751 , 752 and 753 detect when the products run out.
  • the sensors could be pressure sensitive or light sensitive, or they could be sensitive to any other variable condition which might change when a product runs out.
  • the sensor would comprise a fuel level indicator, for example a float attached to a digital switch. When the fuel level drops sufficiently, the float switches the polarity of the switch, which in turn indicates (using simple logic circuitry) to the sensing equipment 750 that a call needs to be made to the tank's owner.
  • a similar arrangement could be used to sense when no products, for example cans of drink, are in a storage area within the vending machine.
  • the procedure for establishing a call initiated by the vending machine 700 is as follows.
  • Product B runs out, the sensor 752 sends, via the line b, a signal to the sensing equipment 750 which, in turn, sends a signal, indicating that the signal was sent by the sensor 752 for Product B, to the processor 705.
  • the processor 705 recognises the signal from the sensing equipment 750 and initiates a call to establish a communications channel with, for example, the TP 41 of the remote access system described above
  • the actual procedure for setting up the communications channel is the same as the step 302 in the procedure described for TIU/Meter Enrolment and therefore will not be repeated here.
  • data can be transmitted from the IU 740 to the TSMS 1 2 via the TP 41
  • Data transmission follows the scheme described above in which the data from the IU 740 is transmitted in the READ-DATA block to the TSMS 1 2
  • the TSMS 1 2 sends the information to the TIS 51 owned by the vending machine owner
  • the TSMS 1 2 initiates a specific call to the TIS 51 to enable the sending of the data to the owner
  • the owner might own many vending machines and prefer to receive information from all vending machines at the same time In this case the TIS 51 or the owner could initiate one call each day to receive a batch of information.
  • the TSMS 1 2 or the TP 41 could be configured to contact the police automatically in response to a call from the target equipment indicating vandalism of the target equipment is taking place
  • the READ_DATA block would then hold a pre-defined message indicating to the police the whereabouts of the target equipment and the nature of the offence
  • the police would need a suitable interface, similar to a TIS, to receive such information.
  • commercial remote equipment such as a vending machine, which can initiate calls to the TSMS, will not co-terminate a communications line with other communications equipment, for example a telephone, in the same way a utility meter might.
  • the processor in the equipment will need to be pre-programmed with suitable software to carry out the dialogue which would otherwise be carried out by the installer.
  • a dialogue can be controlled very simply with commercially available software, for example the Procomm script language, however it is envisaged that dedicated software would be provided for this task.
  • Specific enrolment processes will be developed by consultation with manufacturers of the target equipment.
  • a refrigeration plant might fail, jeopardising large quantities of frozen food.
  • target equipment sensitive to ambient temperature changes in the refrigeration plant could initiate a call to the TP 41 .
  • the TSMS 1 2 or the TP 41 could then initiate a call to an engineer, for example by radio pager via a radio pager network, where the READ_DATA block would contain a pre-defined message and location of the plant.

Abstract

Un système de gestion (A1) permet d'accéder à distance à des unités d'équipement situées à des emplacements répartis sur un réseau de télécommunications (A4). Il permet, par exemple, à des sociétés de service public d'effectuer une lecture automatique de compteurs à travers un réseau téléphonique commuté public (RTPC). Ce système de gestion (A1) lance des appels à travers le réseau (A4) vers des unités sélectionnées, normalement prédéterminées, en réponse à des demandes d'appel et peut réaliser des performances efficaces, telles que l'authentification et le traitement groupé de la demande. Il permet d'éviter des incompatibilités de trafic ordinaire sur le réseau (A4) au moyen du contrôle d'appels de trafic ordinaire et de la libération de tous appels incompatibles d'accès à distance en cours ou du blocage de tous appels demandés d'accès à distance potentiellement incompatibles. Les appels d'accès à distance non établis ou bloqués sont reprogrammés automatiquement par le système de gestion (A1).
PCT/GB1995/002301 1994-09-27 1995-09-27 Systemes d'acces a distance WO1996010313A1 (fr)

Priority Applications (5)

Application Number Priority Date Filing Date Title
AU35715/95A AU3571595A (en) 1994-09-27 1995-09-27 Remote access systems
EP95932821A EP0784900A1 (fr) 1994-09-27 1995-09-27 Systemes d'acces a distance
CA002200862A CA2200862C (fr) 1994-09-27 1995-09-27 Systemes d'acces a distance
JP8511510A JPH10506250A (ja) 1994-09-27 1995-09-27 遠隔アクセスシステム
US08/822,132 US6073174A (en) 1994-09-27 1997-03-21 Remote access systems

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP94307055 1994-09-27
EP94307055.7 1994-09-27
US41901195A 1995-04-07 1995-04-07
US419,011 1995-04-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US08/822,132 Continuation US6073174A (en) 1994-09-27 1997-03-21 Remote access systems

Publications (1)

Publication Number Publication Date
WO1996010313A1 true WO1996010313A1 (fr) 1996-04-04

Family

ID=26137309

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB1995/002301 WO1996010313A1 (fr) 1994-09-27 1995-09-27 Systemes d'acces a distance

Country Status (6)

Country Link
EP (1) EP0784900A1 (fr)
JP (1) JPH10506250A (fr)
AU (1) AU3571595A (fr)
CA (1) CA2200862C (fr)
NZ (1) NZ293305A (fr)
WO (1) WO1996010313A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997041493A2 (fr) * 1996-04-26 1997-11-06 Siemens Aktiengesellschaft Procede et dispositif d'application pour affichage avec alarme, de valeurs de mesure sur des terminaux de telecommunications
WO1997047126A1 (fr) * 1996-06-03 1997-12-11 Et Communications, Inc. Procede et dispositif de telemesure
NL1010981C2 (nl) * 1999-01-07 2000-07-11 Delft Instr Intellectual Prope Systeem en werkwijze voor het overdragen van ijkwaardige gegevens, meetsysteem voor een dergelijk systeem en toepassing van het systeem.
WO2001018694A2 (fr) * 1999-09-03 2001-03-15 Marathon Products, Inc. Procede et systeme pour fournir, stocker et distribuer des donnees d'acces distant reunies par des dispositifs d'enregistrements electroniques
WO2002025987A2 (fr) * 2000-09-21 2002-03-28 James Robert Orlosky Systeme automatise de traitement des releves de compteur, de facturation et de paiement
FR2845846A1 (fr) * 2002-10-10 2004-04-16 France Telecom Systeme de surveillance et d'analyse a distance du fonctionnement d'une installation
GB2416640A (en) * 2004-07-01 2006-02-01 Actaris Uk Ltd Collection of Automatic Meter Readings dependent upon spare capacity of exisiting networks

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SG187229A1 (en) * 2010-07-30 2013-02-28 Accenture Global Services Ltd Intelligent core engine

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1991015074A1 (fr) * 1990-03-19 1991-10-03 Ameritech Services, Inc. Reseau de commutation telephonique, systeme automatique de lecture du compteur base sur l'adresse de service
EP0474407A1 (fr) * 1990-08-31 1992-03-11 AT&T Corp. Système d'accès pour télémétrie
GB2262682A (en) * 1991-11-27 1993-06-23 Thames Water Utilities Remote meter reading system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1991015074A1 (fr) * 1990-03-19 1991-10-03 Ameritech Services, Inc. Reseau de commutation telephonique, systeme automatique de lecture du compteur base sur l'adresse de service
EP0474407A1 (fr) * 1990-08-31 1992-03-11 AT&T Corp. Système d'accès pour télémétrie
GB2262682A (en) * 1991-11-27 1993-06-23 Thames Water Utilities Remote meter reading system

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997041493A3 (fr) * 1996-04-26 1997-12-04 Siemens Ag Procede et dispositif d'application pour affichage avec alarme, de valeurs de mesure sur des terminaux de telecommunications
US6160484A (en) * 1996-04-26 2000-12-12 Siemens Aktiengesellschaft Process and apparatus for the display and provision of alarm means for measured values on communications terminals
WO1997041493A2 (fr) * 1996-04-26 1997-11-06 Siemens Aktiengesellschaft Procede et dispositif d'application pour affichage avec alarme, de valeurs de mesure sur des terminaux de telecommunications
WO1997047126A1 (fr) * 1996-06-03 1997-12-11 Et Communications, Inc. Procede et dispositif de telemesure
NL1010981C2 (nl) * 1999-01-07 2000-07-11 Delft Instr Intellectual Prope Systeem en werkwijze voor het overdragen van ijkwaardige gegevens, meetsysteem voor een dergelijk systeem en toepassing van het systeem.
WO2001018694A3 (fr) * 1999-09-03 2002-11-21 Marathon Products Inc Procede et systeme pour fournir, stocker et distribuer des donnees d'acces distant reunies par des dispositifs d'enregistrements electroniques
WO2001018694A2 (fr) * 1999-09-03 2001-03-15 Marathon Products, Inc. Procede et systeme pour fournir, stocker et distribuer des donnees d'acces distant reunies par des dispositifs d'enregistrements electroniques
WO2002025987A2 (fr) * 2000-09-21 2002-03-28 James Robert Orlosky Systeme automatise de traitement des releves de compteur, de facturation et de paiement
WO2002025987A3 (fr) * 2000-09-21 2002-12-27 James Robert Orlosky Systeme automatise de traitement des releves de compteur, de facturation et de paiement
FR2845846A1 (fr) * 2002-10-10 2004-04-16 France Telecom Systeme de surveillance et d'analyse a distance du fonctionnement d'une installation
GB2416640A (en) * 2004-07-01 2006-02-01 Actaris Uk Ltd Collection of Automatic Meter Readings dependent upon spare capacity of exisiting networks
GB2416640B (en) * 2004-07-01 2007-05-09 Actaris Uk Ltd A method of remote collection of data for the account of an entity,using a third party data communication network,eg for automatic meter reading
US7720459B2 (en) 2004-07-01 2010-05-18 Actaris Uk Limited Method of remote collection of data for the account of an entity, using a third party data communication network, e.g. for automatic meter reading

Also Published As

Publication number Publication date
NZ293305A (en) 1997-06-24
AU3571595A (en) 1996-04-19
JPH10506250A (ja) 1998-06-16
CA2200862C (fr) 2002-02-26
CA2200862A1 (fr) 1996-04-04
EP0784900A1 (fr) 1997-07-23

Similar Documents

Publication Publication Date Title
US6073174A (en) Remote access systems
US6452490B1 (en) Home/commercial security monitoring system
US6529591B1 (en) Method and system for communication caller identification information between a remote site and a central monitoring station over PSTN
US6795852B1 (en) Automatic network connection
US6169791B1 (en) System and method for least cost call routing
US20070036315A1 (en) Platform for rapid development of telecommunication services
CN100566362C (zh) 通信设备、通信系统以及通信方法
CN101584150A (zh) 监听基于ip的语音通信和其它数据通信
JPS59160360A (ja) 通信方式
WO1991015074A1 (fr) Reseau de commutation telephonique, systeme automatique de lecture du compteur base sur l'adresse de service
CA2200862C (fr) Systemes d'acces a distance
US6351524B1 (en) Toll saving method and apparatus for a remote access system
CN101184014A (zh) 辅助桥接设备/电路、电话架构及桥接操作方法
US6321253B1 (en) Systems and methods for simultaneous network management of voice and data signals
US10002480B2 (en) Apparatus and methods for entry control over a cellular network
AU735817B2 (en) Remote access systems
KR20000016463A (ko) 원격 계측 방법 및 그 장치
US20010012343A1 (en) System and method for redirecting long distance transmissions over a computer network
US6674764B1 (en) Communications system and method with telemetry device identification capabilities
US20050201543A1 (en) Status monitoring system utilizing an RFID monitoring system
US7734018B2 (en) System and method for establishing a call between a calling party and a called party over a wired network
US7372955B1 (en) System and method for accessing a wireless network from a handset connected to a public wiring network
EP0845896A1 (fr) Accès de données à distance par téléphone
GB2369904A (en) Web page, database and program creation
WO2003036933A1 (fr) Procede et systeme pour acheminer une communication electronique d'une premiere partie a une deuxieme partie via un fournisseur de services de communications souhaite

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 95196009.1

Country of ref document: CN

AK Designated states

Kind code of ref document: A1

Designated state(s): 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 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 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: 1995932821

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 293305

Country of ref document: NZ

ENP Entry into the national phase

Ref document number: 2200862

Country of ref document: CA

Ref document number: 2200862

Country of ref document: CA

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1019970701962

Country of ref document: KR

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWP Wipo information: published in national office

Ref document number: 1995932821

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1019970701962

Country of ref document: KR

WWW Wipo information: withdrawn in national office

Ref document number: 1019970701962

Country of ref document: KR

WWW Wipo information: withdrawn in national office

Ref document number: 1995932821

Country of ref document: EP