Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/10—Architectures or entities
  • H04L65/102—Gateways
  • H04L65/1023—Media gateways
  • H04L65/1026—Media gateways at the edge
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/10—Architectures or entities
  • H04L65/102—Gateways
  • H04L65/1033—Signalling gateways
  • H04L65/1036—Signalling gateways at the edge
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M1/00—Substation equipment, e.g. for use by subscribers
  • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
  • H04M1/725—Cordless telephones
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/58—Arrangements providing connection between main exchange and sub-exchange or satellite
  • H04Q3/62—Arrangements providing connection between main exchange and sub-exchange or satellite for connecting to private branch exchanges
• • 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
  • H04M—TELEPHONIC COMMUNICATION
  • H04M1/00—Substation equipment, e.g. for use by subscribers
  • H04M1/253—Telephone sets using digital voice transmission
  • H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/02—Inter-networking arrangements

Definitions

• the present invention relates to a method and a system for telecommunication and more particularly to the integrated use of public and private communication networks.
• IP Telephony is an emerging set of technologies that enables voice, data and video collaboration over existing IP-based Local Area Networks (LAN), Wide Area Networks (WAN), and the Internet. IP Telephony has many advantages and one of them is its use as a cost-efficient way of implementing conventional telephony services, e.g. making long distance calls.
• office stands for an environment with several users, which users have a connection to a business entity, e.g. a company, and are permanently or temporarily authorised to access communication services provided by that entity.
• Dual-mode phones accessing a local private network (e.g. DECT) while in the office and a public network (e.g. GSM) outside of the office are also suggested.
• a local private network e.g. DECT
• GSM public network
• the numbers can be mapped so that a subscriber can be reached using a single number.
• CTI Computer Telephony Integration
• a communication system comprising a network switching system and a first subsystem comprising one or more base stations for communicating with mobile terminals via an air interface; and a second subsystem comprising one or more base stations for communicating with the mobile terminals via an air interface.
• the second subsystem is accessible by a first group of mobile subscribers of the communication system, and comprises one or more network elements for transforming signals from the network switching system into data packets of the second subsystem and for transforming data packets from the second subsystem into signals of the network switching system, one or more network elements connected with one or more base stations of the second subsystem for transforming signals of the network switching system from the base station into data packets of the second subsystem and for transforming data packets from the second subsystem into signals of the network switching system for the base station.
• Said second subsystem further comprises means for delivering data packets in the second subsystem according to a network address assigned to network elements of the second subsystem; and means for mapping a number identifying a mobile subscriber in the communication system to a network address of the second subsystem when the mobile terminal of the mobile subscriber is able to communicate with a base station of the second subsystem.
• the benefit of the invention derives from the fact that the functions required for optimising the routing are transparent to him. Mobility in the office and outside it is extensively supported, but the task of considering the costs arising from the use of different networks no longer concerns the employee. One number can be used for one subscriber without considering whether the call is within the office or not. Furthermore, computer telephony integration enables a broad spectrum of enhanced services.
• Office network is preferably an IP (Internet Protocol) based network, which may be a simple LAN or a complex interconnected corporate WAN.
• Public mobile network is preferably a digital Public Land Mobile Network (PLMN) provided and maintained by the operator and providing cellular coverage to a mobile terminal in a considerably larger area than the office premises.
• PLMN Public Land Mobile Network
• GSM Global System for Mobile communications
• Figure 1 illustrates the basic concept of invented system
• Figure 2 illustrates handling different type of services through one network
• FIG. 3 illustrates the scope of H.323 specification
• Figure 4 illustrates different core functions of the invented solution and the way they are arranged in relation to the access functions
• Figure 5 illustrates the architecture of the invented system
• Figure 6 illustrates the implementation of the storage and retrieval functions concerning mobile subscriber information managed by the Intranet Location Register
• Figure 7 illustrates a functional architecture of the A-Gateway Element
• Figure 8 illustrates the architecture of the ISDN/IP Gateway
• Figure 9 illustrates the functional architecture of the Intranet Mobile Cluster
• FIG. 10 illustrates functional units and interfaces of the WIO Gatekeeper
• FIG. 11 illustrates functional elements of the Intranet Mobile Cluster
• Figure 12 illustrates interfaces of the presented embodiment
• Figure 13 illustrates the method of routing calls in the invented system
• the block diagram in Figure 1 illustrates the basic concept of invented system using GSM as the public mobile network.
• mobile stations MS are in connection with base stations BTS using radio communication.
• the base stations BTS are further, through a so-called Abis interface, connected to a base station controller BSC, which controls and manages several base stations.
• the entity formed by several base stations BTS and a single base station controller BSC controlling them are called a base station subsystem BSS.
• the base station controller BSC manages radio-communication channels, as well as handovers.
• the base station controller BSC is, through the so-called A interface, in connection with a mobile services switching centre (MSC), which co-ordinates the establishment of connections to and from mobile stations.
• MSC mobile services switching centre
• a connection can further be established to a subscriber not operating under the mobile communication network.
• a base station BTS in the office WIO (Wireless Internet Office) premises is functionally connected to a office network LAN, which is connected through a IP network to the MSC.
• a base station BTS mobile terminating and mobile originating calls, as well as other services e.g. GSM data, fax and short messages will be handled via office network LAN.
• services will be handled in a conventional way via BSS.
• Figure 1 is a simplified illustration of the solution.
• MSCs can be connected to several other communication networks, e.g. PLMN, PSTN and ISDN.
• the LAN can be connected to an other LAN of the same business entity in another location and they can be connected by IP/Intranet.
• IP Telephony blends voice, video and data by specifying a common transport medium, IP, for each.
• IP Telephony uses open IETF (Internet Engineering Task Force) and ITU (International Telecommunication Union) standards to move multimedia traffic over any network that uses IP thus offering users both flexibility in physical media (for example, plain old telephone service lines, ADSL, ISDN, leased lines, coaxial cable satellite and twisted pair) and flexibility in physical location.
• IETF Internet Engineering Task Force
• ITU International Telecommunication Union
• H.323 is an open standard for multimedia communications (voice, video and data) over connectionless networks, often thought of as the "Internet" videoconferencing standard, but actually designed to support any combination of audio, video and data and be implemented on any LAN protocol (IPX, TCP/IP).
• IPX IPX
• TCP/IP IP-to-IP
• the block chart of Figure 3 illustrates the scope of H.323 specification (dotted line).
• H.323 provides for call control, multimedia management and bandwidth management for point-to point and multipoint conferences.
• H.323 mandates support for standard audio and video codecs and supports data sharing via the T.120 standard.
• H.323 is also network, platform and application independent, allowing any H.323 compliant terminal to inter-operate with any other terminal.
• H.323 allows multimedia streaming over current packet switched networks. To counter the effects of LAN latency, H.323 uses Real-time Transport Protocol (RTP), which is an IETF standard designed to handle the requirements of streaming real-time audio and video over the Internet. Overhead per packet in H.323 are 12 bytes for RTP header, 8 bytes for UDP, 20 bytes for IP and about 1- 3 bytes for link-level header and framing. Any H.323 client is guaranteed to support the standards H.261 and G.711. H.261 is an ITU standard for video codec design to transmit compressed video at a rate of 64 kbps and at a resolution of 176x44 pixels (QCIF).
• RTP Real-time Transport Protocol
• G.711 is an ITU standard for audio codec designed to transmit A-law and ⁇ -law PCM audio bit rates of 48, 56, and 64 kbps.
• H.323 client may support additional codecs like H.263 and G.723.
• H263 is an ITU standard video codec
• G.723 is an ITU standard audio codec designed to operate at very low bit-rates.
• H.323 For system control H.323 standard specifies three command and control protocols, wherein H.245 is responsible for control messages governing operation of the H.323 terminal, including capability exchanges, commands and indications.
• H.225.0 (Q.931) is used to set up a connection between two terminals and RAS governs registration, admission and bandwidth functions between endpoints and gatekeepers.
• Terminals are the client endpoints on the network. All terminals must support voice communications; video and data support is optional.
• Gateways bridge H.323 conferences to other networks or communication protocols. Gateways are not required if connections to other networks, or non- H.323 compliant terminals, are not needed.
• Gatekeepers perform two important functions: address translation, and bandwidth management. These functions help the gatekeeper to maintain the healthy state of the network.
• the Gatekeeper also exercises call control functions to limit the number of H.323 connections, and the total bandwidth used by these connections, in a H.323 "zone."
• One H.323 zone is a collection of all terminals, gateways and multipoint control units (MCU) managed by a single gatekeeper.
• MCU multipoint control units
• a Gatekeeper is not required in a H.323 system. However, if a Gatekeeper is present, terminals must make use of its services.
• Multipoint Control Units support conferences between three or more endpoints.
• An MCU consists of a required Multipoint Controller (MC) and zero or more Multipoint Processors (MPs).
• the MC performs H.245 negotiations between all terminals to determine common audio and video processing capabilities, while the MP routes audio, video, and data streams between terminal endpoints.
• An MCU is also optional.
• the invented system is based on utilising the recent development in integrated communication systems for combining public mobile network with private networks in a way that is advantageous for different parties in the processes. Furthermore, for implementing said invented system new elements have been invented.
• the core functions of the invented system include directory services, call control service, mobility management, operation and maintenance, billing, quality of service guarantee and security services.
• the invented system can be seen as a new kind of GSM BSS/NSS with a specific location register or as an extension to the packet based multimedia communication system specified in the H.323 Recommendation.
• WIO Wireless Internet Office
• AGW AGW
• IGW IGW
• IMC IGW
• H.323 the gateway function according to H.323 is only one of the functions these components take care of.
• the WIO block comprises network elements AGW, IGW and ILR, the purpose and functions of which are now explained in more detail.
• A-interface gateway AGW is to handle communication between the office network and the public mobile network through MSC.
• AGW provides both signalling and traffic routing between the office network and MSC, and thereby forms a BSS interface to the MSC. From the MSC point of view WIO thus looks like one or more BSSs with a certain Location Area Code (LAC).
• LAC Location Area Code
• AGW can be connected to the MSC directly with A-interface. Anyhow, AGW does not necessarily need to provide transcoding functions, and therefore it can alternatively be connected using a Ater-interface to a transcoder (e.g. Nokia Transcoder TCSM2) typically arranged between the MSC and BSC.
• the transcoding function is thereby not performed in the AGW unit itself, but the function of the AGW is to convert PCM based traffic into IP and vice versa.
• FIG 7 a functional architecture of the AGW is illustrated.
• AGW is preferably implemented with a computer, e.g. NT server.
• the performance of AGW depends both on the server configuration as well as the used LAN (IP stack throughput, Ethernet, etc.).
• one logical AGW can be realised as a cluster of servers.
• the number of supported voice traffic channels varies. For example, to support one multiplexed E1 connection, a configuration of two servers is needed, thus creating around 120 traffic channels.
• the functions of the AGW comprise at least most of the following:
• TRAU Transcoding and Rate Adaption Unit
• IP DTX discontinuous speech over IP
• the signalling between all the WIO components is preferentially encrypted, and this relates to also to communication between the unit implementing O&M and AGW.
• AGW typically collects statistical information of its central transactions and especially of detected failures and disturbances.
• WIO Gatekeeper elements (presented later) constantly control status of other WIO network elements, and hence AGW provides responses to those enquiries as well.
• Ongoing WIO calls are disconnected by MSC. In case WIO network connection breakdown, AGW closes temporarily also the MSC signalling link.
• the second element in the operator side is the ISDN/IP Gateway (IGW) that manages communication between WIO and the public telephone network, and it is a gateway that is typically defined in the CTI concept.
• IGW Digital Signalling System No. 1
• DSS.1 Digital Signalling System No. 1
• Figure 8 a functional architecture of the IGW is illustrated.
• IGW has an interface to both MSC and PSTN. From MSC point of view IGW looks like a PBX.
• IGW supports transcoding between ITU-T standards G.71 1 and G.723 as well as G.711 and GSM 06.10.
• IGW collects statistical information of its central transactions and especially of detected failures and disturbances, and forwards the information to O&M application through WIO Gatekeeper (explained later).
• the architecture of IGW is based on a similar hardware as the AGW.
• the third element shown in the operator side is Intranet Location Register ILR that takes care of the directory services in WIO.
• GSM provides a Home Location Register (HLR), which is a register where all subscriber parameters of a mobile subscriber are permanently stored, and one or more Visitor Location Registers (VLR) where all subscriber parameters for call set-up are temporarily stored as long as a subscriber is in a location area controlled by the register.
• HLR Home Location Register
• VLR Visitor Location Registers
• the Intranet Location Register is a database taking care of the permanent subscriber data storage in WIO, while on the other hand it is an access manager to subscriber data in the HLR and the billing system.
• the purpose of the ILR is to provide a storage base for retrieving Mobile Station (MS) specific information configured for the WIO system. All the MS's configured to WIO have a permanent entry in the database. These MS specific settings are valid when the MS is logged into the WIO system.
• MS Mobile Station
• the WIO Gatekeeper in the office side updates the mapping of current address of each MS within the WIO region, in the directory.
• the ILR is connected to the HLR and VLR through the MAP interface.
• the main task for the ILR towards the HLR is to retrieve a subscriber's service profile information from the HLR, such as supplementary service settings, etc.
• the ILR runs e.g. on a Windows NT server based on industry standard Pentium technology. In order to fulfil its tasks well, the server shall provide high-availability, fault-tolerance and fast recovery.
• FIG. 6 a more detailed illustration of the implementation of the storage and retrieval functions concerning mobile subscriber information managed by the ILR is presented. It should be noted that the shown interfaces apply to the present embodiment and do not exclude equivalent implementations comprising more or less interfaces.
• the ILR Interface implements storage and retrieval functions concerning mobile subscriber information managed by the ILR. The function makes database related details transparent the WIO Gatekeeper, so that a change in the underlying storage method does not require any changes in the WIO Gatekeeper.
• the ILR provides the coding and decoding of requests asked for by the WIO Gatekeeper, and also returns information requested by the WIO Gatekeeper.
• the HLR Interface is used to retrieve a mobile subscriber's basic information as well as their supplementary service settings from the HLR.
• MS Gatekeeper location address is stored in the ILR and also the retrieval is carried out in connection with Location Update.
• the mobile location update request from the WIO Gatekeeper acts as a triggering event for HLR information retrieval.
• the VLR interface is used to request a subscriber's IMSI (International Mobile Subscriber Identity), if a mobile station identifies itself with the TMSI (Temporary Mobile Subscriber Identity) during the first location update to the WIO area. In both cases the MAP protocol is used.
• the LDAP Interface provides means to retrieve and maintain MS specific information stored in Directory service database connected to the ILR. This information is gathered from different sources like HLR Interface and IN Interface.
• the protocol used in the communication with Directory service is Lightweight Directory Access Protocol (LDAP).
• IN Interface is an optional interface that provides means for retrieving subscriber's additional service information from Intelligent Network e.g. private numbering enabling the use of short codes within WIO. This interface is based on e.g. Service Management Interface (SMI) provided by IN.
• SI Service Management Interface
• Billing Interface provides means for transferring billing related raw data into billing system to be post-processed.
• local database ILR acts as an intermediate storage for billing information collected by the WIO Gatekeeper.
• the network elements Intranet Mobile Cluster IMC and WIO Gatekeeper GK are shown in Figure 5.
• the Intranet Mobile Cluster (IMC) is substantially a gateway in H.323 terminology, and it is simulating the actions of the BSC in the WIO environment.
• the IMC uses LAPD based Q.931 and GSM specific signalling and generates TRAU frames for speech and data for an Abis interface. It also manages the radio resources and channel configurations, and handles configuration of the BTS.
• the IMC provides GSM signalling and stream conversions to other WIO components. It also detects the need for possible handover and power control actions during a call.
• the main functions of the IMC towards BTS are:
• the IMC is typically implemented as a radio-controlling unit, which is based e.g. on a PentiurrTPC with an E1 interface card.
• the IMC comprises substantially three functional elements as illustrated in Figure 11.
• the Radio Access part 111 comprises a radio receiver 112 and transmitting unit 113, E1 interface 114.
• the Data Processing Unit 116 is typically implemented with a computer; e.g. a Pentium ® based NT computer.
• the DPU 116 further comprises three functional elements: Radio Resource Handling Unit 117, Operation and Maintenance Unit 118 and Telecommunication Unit 119.
• WIO Interface Unit 120 is preferably a LAN interface card supporting a number of physical connections.
• the second element shown in the office side in Figure 5 is the WIO Gatekeeper.
• Gatekeeper is typically an element for providing services such as call forwarding, automatic re-routing and detailed departmental billing in an IP network.
• WIO Gatekeepers tasks in the WIO system comprise furthermore providing call control services to the WIO endpoints.
• the tasks the Gatekeeper comprise at least most of the following: address translation functions bandwidth management call management mobility management giving paging requests to the IMCs (explained later) checking service profiles and authorisation of WIO services collecting call data records (CDR) forwarding call data records to the ILR offering an interface for the O&M application checking functionality of other WIO components taking care of terminal registration and status handling.
• address translation functions bandwidth management call management mobility management giving paging requests to the IMCs (explained later) checking service profiles and authorisation of WIO services collecting call data records (CDR) forwarding call data records to the ILR offering an interface for the O&M application checking functionality of other WIO components taking care of terminal registration and status handling.
• CDR call data records
• Gatekeeper comprises several functional units and interfaces that are illustrated in Figure 10.
• Device Management 101 is responsible for status handling of other WIO entities as well as terminal registration.
• Device Manager stores WIO specific information to the Device Database 102.
• Operation and maintenance 103 comprises an optional WIO Gatekeeper charging function, which collects information from calls, creates charging records (CDR) out of them and sends them to the ILR.
• WIO Gatekeeper charging function which collects information from calls, creates charging records (CDR) out of them and sends them to the ILR.
• Call Management 104 can be defined as a set of functions that enable and control telecommunications between two or more parties.
• Call Management 104 can be defined as a set of functions that enable and control telecommunications between two or more parties.
• the WIO Gatekeeper is arranged to manage different call types, such as voice, data, facsimile, SMS, and conference calls. These calls can be established between two of the following: a mobile station, a network terminal and a fixed telephone. The call between a fixed and a mobile phone is established through MSC as long as there is no gateway between the PBX and the WIO infrastructure.
• Gatekeeper manages both internal and external calls. Internal calls are calls that are made either under the same WIO Gatekeeper, or between subscribers under two different WIO Gatekeepers of one office. External calls, are calls where either of the subscribers does not have access to the office network.
• WIO Gatekeeper manages a location area. When a subscriber in the office is called from the external network, the call is routed by the IGW or the AGW to the WIO Gatekeeper under which the called mobile station is currently located. The location data is queried by the IGW or the AGW from the ILR. After this the WIO Gatekeeper sends a broadcast-paging message to each IMC within the zone it is managing and routes the call to the right one.
• both subscribers are in the area of the same Gatekeeper.
• the WIO Gatekeeper detecting that the B-subscriber is under the same WIO Gatekeeper, sends a Paging broadcast message to each IMC under it.
• the IMC where the subscriber is registered to sends its answer to the WIO Gatekeeper, and the gatekeeper routes the call to this IMC.
• the WIO Gatekeeper checks the location of subscriber B. If it does not find the subscriber B, WIO Gatekeeper routes the call to the MSC through the AGW.
• Mobility management 105 includes tasks related to the mobility of the user, such as location updates and handovers.
• Location update is done each time a new subscriber having access to the office network arrives in the office environment.
• other subscribers e.g. visitors
• WIO Wireless Fidelity
• This function is preferably configured so that the operator can allow external subscribers to use base stations connected to WIO as well.
• the subscriber information is received from the ILR.
• a handover request message is sent to the WIO Gatekeeper by the IMC. This message includes a list of the best target cells. Handovers that work in the normal GSM network also work in WIO. One exception, however, is a handover from WIO to an external non-WIO cell. This is not possible if the phone call is an internal, non-MSC controlled call. If the phone call is a MSC controlled call, it means that A-subscriber is inside the office, and B-subscriber is outside the office, and handover is, in this case, possible. The exception provides for the tariffing scheme, which can be different for intra-office calls (i.e., low tariff or even free of charge). It is advantageous to have means to control the implementation of this special tariffing whenever the calling or the called mobile station is moving outside office coverage.
• the Gatekeeper preferably collects statistical information from all transactions made in WIO (i.e. voice and data call, facsimile, SMS, failed call, etc.). This information is stored to the file, then delivered to the ILR if the information is needed for billing purposes.
• the billing interface in the ILR collects information relating to 'call data records' (CDR), and sends it to the billing system.
• WIO has two interfaces towards MSC.
• IGW fulfils the DSS.1 standard requirements by providing layer 2 (LAPD) and layer 3 (Q.931 ) protocol services.
• the MSC interface is compliant with several standards, like E1 , 2048Mbit/s (based on G.703 and G.704), LAPD (Q.921 ) and Layer 3 where standards Q.931 and Q.932 are used.
• IGW uses D"".1 standard also towards PBX and PSTN.
• Towards Mobile station cellular standard e.g. GSM is used.
• the ILR implements MAP interface towards the HLR and VLR.
• WIO Gatekeeper uses H.323 protocol to communicate with other WIO entities in the following way:
• WIO uses Routed Signalling Model based on the H.323 standard. All signalling between WIO Gatekeeper and other WIO elements are preferably encrypted.
• step 131 the IMC receives a call set-up request from the subscriber A comprising the number of the subscriber B.
• the request is delivered to the WIO Gatekeeper that will check from the ILR (step 132) whether the subscriber B is a WIO subscriber or not (step 133). If the subscriber B is a WIO subscriber, WIO Gatekeeper pages all IMCs it controls (step 134) and checks whether it receives an answer (step 135). If, for some reason, no answer is received, the call will be cancelled (step 136).
• step 137 If the IMC to which the BTS communicating with the MS of the subscriber A answers, a connection is established by the IMC elements of subscriber A and subscriber B (step 137). If the subscriber B is not a WIO subscriber, WIO Gatekeeper will route the call via AGW (step 139) to the MSC, and the call set-up will be implemented in a conventional way (step 140), though the data transfer involves both GSM and H.323.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Multimedia (AREA)
• Physics & Mathematics (AREA)
• Astronomy & Astrophysics (AREA)
• General Physics & Mathematics (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (5)

Publications (1)

Family

ID=26160561

Family Applications (1)

Country Status (5)

Families Citing this family (18)

Family Cites Families (3)

• 1999
  • 1999-03-18 CN CN99804098.3A patent/CN1293876A/zh active Pending
  • 1999-03-18 AU AU28391/99A patent/AU2839199A/en not_active Abandoned
  • 1999-03-18 JP JP2000537388A patent/JP2002507869A/ja not_active Withdrawn
  • 1999-03-18 WO PCT/FI1999/000214 patent/WO1999048311A2/en not_active Application Discontinuation
  • 1999-03-18 EP EP99908992A patent/EP1064804A2/de not_active Withdrawn

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events