Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L45/00—Routing or path finding of packets in data switching networks
  • H04L45/02—Topology update or discovery
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M7/00—Arrangements for interconnection between switching centres
  • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
  • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
  • H04M7/126—Interworking of session control protocols
  • H04M7/1265—Interworking of session control protocols where the session control protocols comprise H.323 and SS7
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M7/00—Arrangements for interconnection between switching centres
  • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
  • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
  • H04M7/126—Interworking of session control protocols
  • H04M7/127—Interworking of session control protocols where the session control protocols comprise SIP and SS7
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M7/00—Arrangements for interconnection between switching centres
  • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
  • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
  • H04M7/128—Details of addressing, directories or routing tables
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/0016—Arrangements providing connection between exchanges
  • H04Q3/0025—Provisions for signalling
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/0016—Arrangements providing connection between exchanges
  • H04Q3/0029—Provisions for intelligent networking
  • H04Q3/0045—Provisions for intelligent networking involving hybrid, i.e. a mixture of public and private, or multi-vendor systems

Definitions

• the present invention relates to systems and methods for providing communications from circuit switched network (CSN) telephone systems to packet data networks such as internet protocol (IP) telephone systems.
• CSN circuit switched network
• IP internet protocol
• Fig 1 illustrates a system diagram of a p ⁇ or art communication system 10 having a plurality (one has been illustrated) of telephone entities 12 which may be diverse in design, such as conventional telephones, which are part of a CSN 14
• the plurality of telephone entities 12 originate and receive first network communications in a conventional manner.
• the entities 12 have the first network communications addressed thereto by a first address type (e.g. dialed numbers).
• a first address type e.g. dialed numbers
• the first address type is based upon E.164 type numbers.
• a packet data network 16 which may be an IP network, also contains a plurality (one has been illustrated) of entities 18 which may be diverse in design, such as telephones, and are designed to operate with a packet data protocol (e g the IP protocol)
• the entities 18 o ⁇ ginate and receive packet data communications and have IP network packet data communications addressed thereto by a second type of address type (e.g. alphanume ⁇ c characters) associated therewith.
• the second network address type is based upon alphanume ⁇ c characters, such as those used with email-style or URL style addresses.
• the CSN 14 is coupled to the packet data network 16 by a gateway 20 permitting communications originating from the plurality of entities 12 to pass through the gateway 20 and be received by the plurality of entities 18
• Conventional CSN network telephone handsets have a nume ⁇ c keypad preventing entry of alphanume ⁇ c characters which precludes direct dialing of packet data network addresses
• the unavailability of an alphanumeric keypad necessitates a mechanism by which conventional telephone numbers based on the E.164 standard are assigned to entities 18 to which communications are to be directed by the plurality of entities 12 using only numbers. Work is currently underway with ETSITIPHON for assigning E.164 numbers to IP telephones and other devices.
• the caller from one of the plurality of entities 12 merely dials a numerical based number which is translated by a conversion mechanism into the necessary IP address in packet data IP network 16 which controls the delivery of the telephone call to at least one of the plurality of the entities 18 once the call has passed through the gateway 20.
• entity 18 further may be addressed by other addressing mechanisms, such as a domain name.
• arrow 22 represents a telephone call originated by one of the plurality of entities 12 of the CSN 14 which is dialed using the addressing type of the CSN (numerical digits) which is directed to one of the plurality of the entities 18 in the packet data IP network 16 via gateway 20.
• the number of the called entity 18, based upon the addressing type of the CSN 14 has already been assigned an IP address (or related address) when the telephone call is initiated.
• the process of obtaining the address of the called entity 18, based upon the second address type of the packet data IP network 16 is currently performed in the packet data network. Brown, "E.164 Resolution" Internet Draft, work in process, November 1998, describes this approach.
• the address mapping between the address of the called entity 18 based upon the addressing of the CSN 14 and the corresponding address of the called entity 18 in the packet data IP network 16 may be performed in the CSN.
• Standards have been proposed, such as H.323, for permitting communications via gateways, such as gateway 20 between CSN networks and packet data networks.
• gateways such as gateway 20 between CSN networks and packet data networks.
• such standards do not provide a mechanism by which the mapping between the address of the entities 18, based upon the CSN 14 addressing type and the corresponding address type of the packet data IP network 16 is accomplished.
• a mechanism is needed which facilitates the obtaining of the corresponding address of the second type used in the packet data IP network 16 which permits the completion of the communication to the called entity 18 upon the generation of a first network communication by an entity 12 using a first network address type which does not involve high complexity or additional expense to the cost of operating the CSN 14.
• Fig. 2 illustrates a block diagram of Signalling System #7 (SS7) from Chapter 5 of Telecommunications Protocols, Russell 1997, McGraw-Hill.
• the SS7 network 30 illustrated in Fig. 2 performs managing functions for CSNs used for providing conventional telephone functions and other applications, such as cellular.
• the SS7 network 30 is capable of managing operation of the CSN 14 illustrated in Fig. 1, including communications setup and routing of communications in the CSN and further provides control functions thereof.
• the SS7 network 30 performs mapping of 800/888 numbers (toll-free numbers in the United States) or 900 numbers (special toll numbers) to physical numbers.
• a typical SS7 network 30 is comprised of a plurality of service switching points (SSP) 32, a plurality of signal transfer points (STP) 34, and a plurality of service control points (SCP) 36.
• SSP service switching points
• STP signal transfer points
• SCP service control points
• the SSPs 32 originate SS7 messages and are typically found in an end office telephone switch.
• the SSPs 32 originate SS7 messages after determining which interoffice trunk will be used to connect the call.
• a SS7 message is sent to an end office on the remote end of the circuit and contains a request for connection.
• the SSPs 32 also originate an SS7 message when determination of an interoffice circuit to connect the call is to be made.
• the SSPs 32 originate a query to an SS7 node which will provide a connection to a database connected to the SCP 36.
• the SSPs 32 are responsible for routing SS7 messages through the network. Once the necessary routing information has been obtained through the STP 34 connectivity to a database, the SSP 32 begins connection of network parts to handle the call.
• the STP 34 is responsible for routing traffic through the SS7 network 30 and does not originate any traffic other than performing SS7 network management.
• the STP 34 is an intermediate point in the SS7 network 30 providing some processing and routing of SS7 messages.
• the traffic directed to the signal transfer point may be circuit related which is typically originated by a first SSP 30 and sent to another SSP to request a connection on a particular circuit which does not allow any processing by the STP 34 and results in the message simply being passed along to its destination STP.
• Circuit related traffic typically involves interactions with a database which is connected to the SCP 36. When a query is made to a database, the SSP 32 does not typically know the address of the specific database it needs to query.
• the STP 34 provides global title translation (GTT) to determine whether the query should be directed with the STP 34 looking at the signalling connection control part (SCCP) to determine which digits were dialed and makes its routing decision based on these global title digits.
• GTT global title translation
• SCCP signalling connection control part
• the SCPs 36 are the front end to subsystems, such as databases and manage access to databases and/or more than one subsystem. Each database is addressed through a subsystem number that identifies the application served by the database. The subsystem numbers are predefined by a network operator. Subsystem management is the responsibility of both the STP 34 and the SCP 36.
• TCAP transaction capabilities application part
• TCAP transaction capabilities application part
• TCAP provides management of the queries and support for multiple transactions in one transmission and also includes error detection/segmentation and reassembly.
• TCAP is divided into three portions, which are the transaction portion, which identifies whether or not a following component portion carries a single transaction or multiple ones, an invoke portion and a parameter set sequence portion.
• Fig. 2 represents one exemplary implementation of an SS7 network 30. It should be understood that numerous permutations of SSPs, STPs and SCPs are used in the prior art. Furthermore, the SS7 network 30, is illustrated in Fig. 2 without connection to the network which it manages, such as the circuit switched network 14 of Fig. 1. DISCLOSURE OF THE INVENTION
• the present invention is a communication system and a method of communication which utilizes a managing network, which is preferably an SS7 network, operating in association with a first network to perform management of the first network including first network communications setup, routing and control, and also providing address mapping between an address of a first type used by the first network and an address of a second type used by at least one second network to support communications between entities originating communications in the first network which are addressed to and delivered to entities in the second network.
• First network communications are addressed from the originating first network entities with a first address type which has an assigned address of the second type of the at least one second network entity which receives the first network communications.
• the first network entities (calling entities) are resident in the first network and the second network entities (called entities) are resident in the second network.
• the invention utilizes the already existent managing network of the first network to perform the aforementioned address mapping between the first and second address types of the second network entity to which the first network communications are addressed without requiring modification of the architecture of either the first network or the second network.
• the preferred form of the managing network is an SS7 network utilizing the transaction capability application part (TCAP) query utilized in the prior art for performing conventional SS7 network functions to additionally perform a new function of obtaining the destination address of at least one second network entity in the second network based upon the address type in the first network of the entity in the second network which is to receive the first network communication.
• TCAP transaction capability application part
• the managing network query optionally obtains additional information used for qualifying the first network communications between a first network entity originating the first network communications and the at least one second network entity receiving the first network communication
• the additional information which may have diverse applications may be the specification of a level of service, a secu ⁇ ty level, a quality of service, a billing mechanism used at least partially in the delivery of the first network communication from an o ⁇ gmating first network entity to at least one second network entity and furthermore, may specify one or more service providers to be used by the second network in dehve ⁇ ng the first network communications by the second network to the at least one second network entity, such as, but not limited to IP service providers
• a single TCAP query may be used to perform the conventional first network management functions as well as the performing of the additional function of address mapping between the addresses of the first and second network types of the second network entity receiving the first network communications in the second network and the obtaining of the additional information to perform the optional functions as discussed
• the first network is a CSN with the first address type used therein being an E 164 address and the second network is a packet data network which, in a preferred embodiment, is an IP network with the second address type used therein being an IP address
• a preferred application of the present invention is for providing address mapping permitting the connection of telephone communications o ⁇ ginating in a CSN to a packet data network
• the present invention is not limited thereto with the present invention also not being limited to the managing network being a SS7 network
• a communication system in accordance with the invention includes a first network containing a plurality of first network entities which o ⁇ ginate and receive first network communications and to which the first network communications are addressed by a first address type associated therewith, a second network, coupled to the first network, containing a plurality of second network entities which o ⁇ ginate and receive second network communications and to which the second network communications are addressed by a second address type associated therewith and which, in response to the second type of address, transmits second network communications associated with the second address type to at least one second network entity, the second network also receiving first network communications from the first network entities and dehve ⁇ ng the first network communications to at least one second network entity, and a managing network, associated with the first network, which manages operation of the first network including first network communication setup and routing and control thereof and which provides address mapping between an address of the first type of the at least one second network entity to which a first network communication is addressed and an assigned address of the second type of the at least one second network entity and provides the assigned address to the second network in association with the
• the first network may be a circuit switched network; and the second network may be a packet data network.
• the first address type may be an E.164 address; and the second address type may be an IP address.
• the first network communication may be a telephone communication.
• the managing network may be an SS7 network.
• the managing network may use at least one service control point (SCP) to provide the mapping between an address of the first type of at least one second network entity to which the first network communications are addressed from the first network entity and the associated address of the second type to which the first network communication is transmitted by the second network in response to the associated address.
• SCP service control point
• a transaction capability application part (TCAP) query may be used to obtain a routing number of the at least service control point storing the address mapping.
• TCAP transaction capability application part
• the managing network further may obtain from at least one service control point (SCP) information stored therein identifying a level of service to be used in completing the first network communications between the first network entity addressing the first network communications and the at least one second network entity to which the first network communications are addressed and may use the obtained information to complete the transmission of the first network communication between the first network entity and at least the second network entity with the level of service.
• the at least one service control point (SCP) may store additional information qualifying the first network communications between a first network entity originating the first network communications and at least one second network entity receiving the first network communications.
• the additional information may specify a security level to be used in the first network communications between the first network entity originating the first network communications and the at least one second network entity receiving the first network communications which controls operation of at least part of the first and second networks in transmitting the first network communications between the first and second network entities.
• the additional information may specify a quality of service to be used at least in part in transmitting the first network communications between the first network entity originating the first network communications and the at least one second network entity receiving the first network communications.
• the additional information may specify a billing mechanism to be used at least in part in charging for the first network communications transmitted between the first network entity originating the first network communications and the at least one second network entity receiving the first network communications.
• the additional information may identify at least one service provider to be used by the second network in delivering the first network communications by the second network to at least one second network entity.
• a single transaction capability application (TCAP) query may be used to provide setup of the first network communications addressed to the at least one second network entity and the address mapping and optional obtaining of the additional information.
• TCAP transaction capability application
• Fig. 1 illustrates a block diagram of a prior art data communications system which provides telephone communication between a CSN and a packet data network ;
• FIG. 2 illustrates a block diagram of a SS7 network in accordance with the prior art
• Fig. 3 illustrates a block diagram of a communication system in accordance with the present invention
• Fig. 4 illustrates communications in accordance with the invention for performing address mapping utilizing an existing managing network which controls a telephone network or another network in accordance with a first embodiment of the present invention
• Fig. 5 illustrates communications in accordance with the invention for performing address mapping utilizing an existing managing network which controls a telephone network or another network in accordance with a second embodiment of the present invention.
• Fig. 3 illustrates a communication system 100 in accordance with the present invention.
• the communication system is comprised of a first network 102 and a second network 104 which are connected by a signalling gateway 106 and a message gateway 108.
• the first network 102 may be in accordance with the CSN 14 of the prior art and the second network 104 may be in accordance with the packet data IP network 16 of the prior art of Fig. 1.
• the first network 102 includes a managing network 1 10 comprised of SSPs 32, STPs 34 and SCPs 36, which are in accordance with Fig. 2 as described above except that at least one additional function is performed by the managing network.
• the at least one additional function of the managing network 110 includes address mapping between an address of a destination entity 18 in the second network identified by an address of the first type used by the first network 102 to address entities 12 and an assigned address of the second type of the entity 18 used by the second network to deliver communications to second network entities and further may include identifying types of service, such as a level of service to be used in completing the first network communications between the first network entity 12 and at least one second network entity 18 and the optional storing of additional information in at least one SCP 36 qualifying the first network communications between the first network entity 12 originating the first network communications and at least one second network entity receiving the first network network communications.
• identifying types of service such as a level of service to be used in completing the first network communications between the first network entity 12 and at least one second network entity 18 and the optional storing of additional information in at least one SCP 36 qualifying the first network communications between the first network entity 12 originating the first network communications and at least one second network entity receiving the first network network communications.
• the additional information may perform diverse functions within the communication system 100 including, but not limited to, specifying a security level to be used at least in part in the first network communications between the first network entity originating first network communications and the at least one second network entity receiving the first network communications, a quality of service to be used at least in part in transmission of the first network communications between the first network entity originating the first network communications and the at least one second network entity receiving the network communications, and a billing mechanism to be used at least in part to charge for transmission of the first network communications between the first network entity originating the first network communications and the at least one second network entity receiving the first network communications.
• the additional information may further identify at least one service provider to be used by the second network 104 in delivering the first network communications by the second network to at least one second network entity 18.
• a single transition capability application part (TCAP) query is used by the managing network 110 to provide the prior art call setup and the present invention's address mapping, obtaining of the additional information specifying level of service, security level, quality of service, or a billing mechanism and at least one service provider to be used by the second network.
• TCAP transition capability application part
• the first network is further comprised of a plurality of switches 1 12 which may be implemented in many different ways with the illustrated architecture indicating a possible logical function without reference to a physical location.
• the switches 1 12 perform circuit switch routing of the first network communications 114 represented by dotted lines which originate from first network entities 12 and are delivered ultimately to second network entities 18 in the second network 104.
• the switches 1 12 may be located at the same or physically dispersed locations in the network.
• the first network communications 1 14 are transmitted between the first network entity 12 and the second network 18 after call setup is completed by the managing network 110 as is described in more detail below and further call setup is performed by the second network 104 which results in the first network communications passing through the aforementioned switches 1 12, message gateway 108, and through a series of routers 116 to the second network entity 18.
• the SS7 network 1 10 which functions as a managing network of the first network 102 to perform address mapping and other functions in accordance with the present invention, is described as follows.
• the first network entity 12 may be, without limitation, an ISDN telephone making a call to a second network entity 18 which is an IP telephone. It is assumed that a global code, e.g. 999, has been assigned as a prefix to E.164 numbers assigned to the second network entity 18 in the second network 104.
• a Q.931 setup message is sent from the first network entity 12 to the central office (not illustrated) as represented by message "1".
• the SSP 32 receiving message "1" is housed in a central office.
• the SSP 32 Based on the prefix 999 of the dialed number, the SSP 32 receiving the message “ 1 ", determines that the dialed number is an IP telephone message. The SSP 32, which receives the message "1", then decides to initiate a TCAP query to determine the routing number as well as the IP address assigned to the dialed E.164 number.
• the TCAP query is illustrated as message flows “2", “3", "4" and "5".
• the querying of the SCP 36 database is shown as message flows "6", “7", “8” and "9".
• the routing number (the address of the entity 18) as far as the circuit switched network
• the 102 is concerned is a combination of the destination point code (DPC) and a subsystem number (SSN).
• DPC-SSN pair facilitates routing of the initial addressing message (IAM) from the originating SSP 32 which receives the message "1 " via one or more SSPs 32 to a terminating STP 34.
• the terminating STP 34 is co-located with the signalling gateway 106 that interfaces to the IP network 104 on the other side.
• the flow of the IAM message from the initiating SSP 32, which receives the initial message "1" is identified by communications "10", "11", "12” and "13".
• the terminating STP 34 passes the IAM message on to the signalling gateway 106 (message "14").
• the signalling gateway 106 encapsulates the IAM message within an IP packet and transmits the IP packet onto a media gateway controller 130 (message "15").
• the message gateway controller 130 then instructs the appropriate media gateway 108 to setup a connection in the circuit switched portion of the first network 102 represented by the switches 112, (communications "16" and "17”).
• the MGC 130 also may optionally communicate with the entity 18.
• a H.323 RAS sequence and H.225.0 call sequence completes the portion of the call between the media gateway 108 and the entity 18 as represented by the dotted lines 114 between the media gateway 108 and the entity 18. Details of the call setup have been omitted in view of their being well known. But alternatively, the call setup may be implemented using the session initiation protocol (SIP).
• SIP session initiation protocol
• the SSP 32 associated with the first network entity 12 and that is associated with the media gateway 108 are shown to be distinct. However, these entities may be one and the same which is likely to be the dominant deployment scenario where the media gateway is located within a central office.
• Fig. 3 The advantages of the architecture of Fig. 3 are as follows. Cost reduction is achieved, rapid deployment of service is possible and experience gained in deployment of existing SS7 networks results in no significant increase in operation, administration and management overhead when E.164-IP service is initiated in view of use of the existing infrastructure.
• the architecture of Fig. 3 provides a highly efficient implementation in view of the managing network used by the present invention already being necessary for a user of the first network entity 12 dialing an E.164 number that has been assigned to a second network entity 18 already having to make a TCAP query to a SCP 36 to obtain the routing number (DPC-SSN pair) of the remote SCP 36.
• This TCAP query needs to be made irrespective of whether E.164 to IP address mapping occurs within the CSN portion of the first network 102 or within the IP network 104.
• Combining the E.164-IP address resolution process with the remote SSP routing number determination process results in a faster call setup. It is possible to use a single TCAP query to return both the service switching point, routing number, and the IP address associated with the E.164 number and the above-described optional additional information.
• Fig. 4 illustrates a simplified communication sequence for performing the aforementioned address mapping in which a TCAP query obtains only the address mapping information between the first and second address types of the entity from a SCP 36.
• the communication sequence is initiated from a SSP 32 with a command BEGIN.
• the original transaction identification (OTID) is set equal to X.
• the invoke portion of the TCAP query is set equal to 1 and includes the address in terms of an E.164 number identifying the second network entity 18.
• the invoke ID may be set to any integer value n which, as illustrated herein, is equal to 1 and contains an operation defining a macro to perform the E 164 to IP address translation and any parameters associated with the translation operation.
• the transmission 200 is received by a SCP 36 which responds with a reply 202 with a message type END.
• the destination transaction identification DTID is set equal to X.
• a return result contains the invoke ID which was utilized in the communication 200, the DPC-SSN pair of the SSP 32 and the IP address of the second network entity 18.
• Fig. 5 illustrates a communication sequence which includes both address mapping, as explained above in Fig. 4, and the obtaining of additional information from the SSP 36.
• the intermediate communications 204 and 206 indicate the fetching of additional information beyond the IP address of the second network device 18.
• the intermediate communication 204 provides an inquiry to the SSP 32 of which security level a communication from the first network entity 12 is to be used and the return 206 from the SSP specifying the security level to be used in transmitting the communications to the second network entity 18.
• the intermediate communications 204 and 206 which are transmitted in pairs, represent a mechanism for retrieving additional information from the SCP 36 which is stored in the database therein or associated therewith to provide additional information regarding the communications 114 between the first network entity 12 and the second network entity 18 which include, without limitation, information pertaining to level or quality of service, billing and/or the desired service provider to be used by the IP network 104 as requested by the first network entity user. While the invention has been described in terms of a preferred embodiment, it should be understood that numerous modifications may be made thereto without departing from the spirit and scope of the present invention.
• a prefe ⁇ ed embodiment of the present invention involves telephone functions
• the invention is not limited to telephone applications and furthermore, is applicable to permitting networks having different addressing mechanisms for entities therein to cross communicate through gateways with utilization of the managing control network of the initiating network.
• the communications are not limited to telephone functions and may be any type of information transmitted to the second network which preferably is information transmitted as packets in a packet data network. It is intended that all such modifications fall within the scope of the appended claims.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=23600779

Family Applications (1)

Country Status (4)

Families Citing this family (13)

Citations (2)

Family Cites Families (5)

• 2000
  • 2000-09-19 JP JP2001527546A patent/JP2003510977A/ja active Pending
  • 2000-09-19 EP EP00961966A patent/EP1131943A1/de not_active Withdrawn
  • 2000-09-19 WO PCT/US2000/025624 patent/WO2001024499A1/en not_active Application Discontinuation
  • 2000-09-19 AU AU73846/00A patent/AU7384600A/en not_active Abandoned

Patent Citations (2)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events