Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/08—Testing, supervising or monitoring using real traffic
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
  • H04W8/24—Transfer of terminal data
  • H04W8/245—Transfer of terminal data from a network towards a terminal

Definitions

• the present invention generally relates to computer networks and communications across wireless computer networks. More particularly, the invention relates to the collection and analysis of data from remote devices, provided from a device-resident diagnostic interface, on a wireless network.
• Wireless networking connects one or more wireless computer devices to other computer devices without a direct electrical connection, such as a copper wire or optical cable.
• Wireless computer devices communicate data, typically in the form of packets, across a wireless or partially wireless computer network and open a "data" or “communication” channel on the network such that the device can send and receive data packets.
• the computer devices often have computer device resources, such as programs and hardware components, which individually use open communication connections to transmit and receive data on the network.
• a peer-to-peer (or point-to-point) wireless network means that each computer can communicate directly with every other computer on the network.
• a cellular telecommunication network can be a wireless network wherein the cellular devices transmit voice or data packets across the cellular network.
• the term "cellular" includes a telecommunication network of any frequency band including, but not limited to the common wireless networks operating at 800MHz, 1900MHz, 450MHz, 1800MHz, and 2100MHz, and all forms of wireless networks, to include CDMA, GSM, TDMA, WCDMA, and UMTS.
• Some wireless networks are in client/server architecture, and have an access point, which is a wired controller that receives and transmits data to the wireless adapters installed in each computer.
• IrDA Infrared Data Association
• SWAP Shared Wireless Access Protocol
• SWAP devices make 50 hops per second and transmit at 1 Mbps. In most cases, SWAP-based networks are point-to-point.
• the Wireless Ethernet Compatibility Alliance (WECA) is essentially compliant with a variation of the IEEE 802.11 specification known as IEEE 802.11b. This specification focuses on direct -sequence spread spectrum (DSSS) transmission because of the higher data rate it can attain. Under 802.11b, devices communicate at a speed of 11 Mbps whenever possible.
• the existing wireless telecommunication devices include resident diagnostic tools on their computer platform which are typically included at the time of manufacture.
• the manufacture accesses the diagnostic tools through a serial port or other wired connection and evaluates the operating parameters of the wireless device and the manufacture will appropriately adjust the hardware or software parameters of the device to yield optimal performance.
• These diagnostic tools are normally inaccessible remotely without a serial port connection.
• the system and method may be implemented within existing software resident on the wireless device and without causing interruption of the existing data communication occurring across the wireless network. Further, such system should be able to take advantage of manipulating extant commands available on the chipset of the wireless device. It is thus to the provision of such a system and method of providing a remotely accessible diagnostic interface that the present invention is primarily directed.
• the present invention is a system, method, and program for accessing a remote diagnostic interface on a wireless device in a wireless network having at least data communication between computer devices selectively connected thereto, such as cellular telecommunication devices on a cellular telecommunication network.
• the system particularly utilizes existing diagnostic interfaces on the wireless device to obtain status data such as device performance parameters and/or other network information, and can use commands to the diagnostic tools to alter device operations.
• a wireless network with at least data communication from computer devices selectively connected thereto has and a plurality of wireless devices located remotely from each other and each in selective communication with other computer devices across the wireless network.
• Each wireless device includes a computer platform, which can have an end-user thereof, and the computer platform further includes a resident diagnostic interface for at least accessing status data that can include either device status data for the operating parameters of the wireless device, or network status data, or both, and the resident diagnostic interface is selectively accessible by other computer devices across the wireless network.
• other computer devices can access the diagnostic interface and at least get data therefrom, and alternately, can send commands to the diagnostic interface and alter the wireless device's and/or the wireless network's functionality.
• the method for remotely interacting with a diagnostic interface of a wireless device across a wireless network includes the steps of establishing the wireless network between computer devices, with at least one of the computer devices a remotely located wireless device including a computer platform.
• the wireless device includes a resident diagnostic interface through which at least the status data (either of the device, network, or both) is accessible, and the method includes the step of accessing the wireless device diagnostic interface from another computer device across the wireless network, and then gathering at least status data of the wireless device through the wireless device diagnostic interface. If so embodied, the method can include the step of transmitting commands to the diagnostic interface of the wireless device to manipulate the device's operating parameters.
• the system and method thus provide significant and valuable wireless device status and network status data detailing operation parameters to other devices on the network. Further, through commands to the diagnostic interface and manipulation of the wireless devices' diagnostic tools, the wireless device's functionality and network can be altered which assists in such functions as problem-solving and network optimization.
• the system and method thus provide an advantage in that the remote wireless devices in a wireless network, such as a cellular telecommunication network, can have their basic operational data accessed without compromising the functionality of the network, or the need to use external monitoring equipment or provide new equipment on the wireless device.
• the access to the diagnostic interface can be created with a simple software extension within the device operating system that allows direct access to the chipset diagnostic interface.
• an application or software agent
• Fig. 1 is a representative diagram of one embodiment of a wireless network, with a partial LAN, having several computer devices that communicate with each other across the network.
• Fig. 2 is a block diagram of the hardware components of the system embodied on a cellular wireless network providing communication between different wireless devices, such as cellular telephones, and computer devices.
• Fig. 3 is a flowchart illustrating one embodiment of the process executing on a wireless device status data-gathering server in communication with wireless devices across the network and gathering status data from the resident diagnostic interfaces of the wireless devices.
• Fig. 3 is a flowchart illustrating one embodiment of the process executing on a wireless device status data-gathering server in communication with wireless devices across the network and gathering status data from the resident diagnostic interfaces of the wireless devices.
• Fig. 4 is a flowchart illustrating the process executing on a wireless device receiving a software agent that accesses the resident diagnostic interface and causes status data to be transmitted to the server of Fig. 3.
• Fig. 5 is an architecture diagram of the interaction between the carrier-side devices and the diagnostic interface resident at the wireless device.
• Fig. 1 illustrates a wireless network 10 having a plurality of computer devices 12,18,20, and 22 in a wireless network area 28.
• the wireless network 14 is connected through an interface 26 to a LAN-based network 30, with preferably at least one wireless device status data-gathering and/or managing server 16, and in this embodiment, the server 16 can selectively download software applications or agents to the wireless devices 12,18,20,22 across the wireless interface 26 such that the wireless device can supply status data back to the server 16 as is further described herein.
• Such computer devices can include wireless devices, such as cellular telephone 12, a personal digital assistant 18, a two-way text pager 20, or even a separate computer platform 22 that has a wireless communication portal, and may otherwise have a wired connection 24 to a network or the Internet.
• the wireless device can be a remote-slave, or other device that does not have an end-user thereof but simply communicates data across the wireless network 14, such as remote sensors, diagnostic tools, data relays, and the like.
• the system and method can accordingly be performed on any form of computer device computer module including a wired or wireless communication portal, including without limitation, wireless modems, PCMCIA cards, access terminals, personal computers, access terminals, telephones without a display or keypad, or any combination or sub-combination thereof.
• FIG. 2 is a block diagram that more fully illustrates the components of a cellular wireless network and interrelation of the elements of the present system.
• the cellular wireless network is merely exemplary and can include any system whereby remote modules, such as wireless devices 12,18,20,22, communicate over-the-air between and among each other and/or between and among components of a wireless network 14, including, without limitation, wireless network carriers and/or servers.
• the system 10 can utilize the existing wireless device diagnostic interface and any resident tools that are manufactured with the device, such as data throughput, signal strength, ASIC diagnosis, graphics display, dropped call statistics, access probe statistics, RX sensitivity, transmission power, and other hardware and software diagnostic tools resident on the wireless device common in the art.
• the data at the diagnostic interface is indicative of wireless device performance, and some of the data can be indicative of network status and performance issues. Both types of data can be supplied in the system 10.
• the device operational parameter data are typically accessed from a serial connection at the time of manufacture or serving and are not traditionally available as data reads or writes from a wireless device computer platform 50 (Fig. 2).
• the wireless device 12,18,20,22 of the system 10 provides a software extension on the computer platform 50 of the wireless device such that program calls can be made to the resident diagnostic interface, and any individual diagnostic tools, from a resident layer on the wireless device, which can be as rudimentary as ASIC or processor microcode to as advanced as an OS layer of the wireless device, as is shown in Fig. 5.
• the access to the remote device diagnostic interface allows network optimization, customer interaction, remote wireless device monitoring, device testing and certification, and the gathering of specific user information for a wireless device.
• the server 16 can be in communication with a separate storage 32 for the data gathered from the remote wireless devices 12,18,20,22, such as device status data.
• the server 16 and its corresponding PC or data access can give a ready view of the wireless device status data collected from the wireless devices in any form, such as tables, maps, graphics views, plain text, or any other display as would be known to known of skill in the art.
• the server 16 (or plurality of servers) can send software agents or applications to wireless devices 12,18,20,22 in the wireless network area 28 such that the wireless devices return data from their resident diagnostic interface, such as system performance data, user ID, geographic position, Network ID, System ID, model ID, resident software, and the like.
• the wireless devices 12,18,20,22 then transmit the requested status data to the server 16, or other computer device on the network, wherein the data can be used for purposes such as network optimization, even in real-time or near-real-time if desired, device diagnosis, or data mining on end-user device usage.
• the data can be used for purposes such as network optimization, even in real-time or near-real-time if desired, device diagnosis, or data mining on end-user device usage.
• a separate data management server 34 resident that works in concert to provide data in usable formats to parties and/or a separate layer of control in the data flow between the wireless devices 12,18,20,22 and the server 16 or data storage 32.
• the wireless device status data-gathering server 16 and the wireless device status and, in this embodiment, a network optimization database 32, and data management server 34, will be present on the cellular data network with any other components that are needed to provide cellular telecommunication services.
• the server 16, and/or data management server 34 communicate with a carrier network through a data manager 40, through a data link, such as the Internet, a secure LAN, WAN, or other network.
• the carrier network controls messages (generally being data packets) sent to a messaging service controller ("MSC") 42.
• MSC messaging service controller
• the carrier network communicates with the MSC 42 by a network, the Internet, and/or POTS ("plain ordinary telephone system").
• the network or Internet connection between the carrier network and the MSC 42 transfers data, and the POTS transfers voice information.
• the MSC 42 is connected to multiple base stations ("BTS") 44.
• BTS base stations
• the MSC 42 is typically connected to the BTS 44 by both the network and/or Internet for data transfer and POTS for voice information.
• the BTS 44 ultimately broadcasts messages wirelessly to the wireless devices, such as cellular telephone 12, by short messaging service (“SMS”), or other over-the-air methods known in the art.
• SMS short messaging service
• Each wireless device such as cellular telephone 12, has a computer platform 50 that can receive and execute software applications and display data transmitted from the application download server 16 or other network servers 34.
• the computer platform 50 also includes an application-specific integrated circuit (“ASIC") 52, or other chipset, processor, microprocessor, logic circuit, or other data processing device.
• ASIC 52 is installed at the time of manufacture of the wireless device and is not normally upgradeable.
• the ASIC 52 or other processor executes the application programming interface (“API”) layer 54 that interfaces with any resident programs in the memory 56 of the wireless device.
• the memory can be comprised of read-only or random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, or any memory common to computer platforms.
• the computer platform 50 also includes a local database 58 that can hold the software applications, file, or data not actively used in memory 56, such as the software applications or data downloaded from the server 16.
• the local database 58 is typically comprised of one or more flash memory cells, but can be any secondary or tertiary storage device as known in the art, such as magnetic media, EPROM, EEPROM, optical media, tape, or soft or hard disk.
• the local database 58 can ultimately hold a resident copy of a network optimization application or agent as is further described herein
• the wireless device diagnostic interface can be accessed through a class of software commands on the wireless device 12,18,20,22.
• a software class extension can communicate with the diagnostic tools of the phone, which allows both data reads and commands.
• This class can send commands, including register for log messages and event notifications, on behalf of the applications that invoke it.
• the class object can then forward the responses of the diagnostic tools units to the applications or ultimately across the network. Notifications of connection and disconnection of external interfaces (outside the wireless device) can be sent to applications if they register with the device manager for notice.
• Each wireless device resident application can create an instance of this new software class to communicate with the diagnostic tools independently.
• Such internal connections, i.e. among applications and the diagnostic tools operate independently and can also operate simultaneously with an external interface, but the external interface has the option to also monitor the internal interface.
• the system 10 can push at least one network optimization application to be resident, at least temporarily, on the computer platform 50 of each wireless device 12,18,20,22 that causes that wireless device to selectively transmit wireless device status data for that wireless device and/or network status to another computer device on the wireless network.
• the network optimization application can be placed on the platform 50 at the time of manufacture or initial programming, or the wireless device 12,18,20,22 can "pull" the application from another computer device on the network, such as server, either with a request from the end-user, or automatically.
• the status data can include, but is not limited to, data from both the diagnostic tools and from other device components, such as signal strength, Ec/Io, Latitude-Longitude or other geographical data, Time, FER, BER, RSSI, PN, System ID, or Network ID, Model ID, and can capture wireless device 12,18,20,22 state data, such as idleness, data or voice call, dormancy or inoperation, which is generated from wireless device operation.
• the wireless device status data can allow for specific troubleshooting of a device within the wireless network 14 based upon the gathered status data.
• the network optimization application or agent can be permanently stored in the local database 58 of the wireless device computer platform 50, or can only be temporarily held in memory 56 thereof for a one time (or n-time) execution to transmit network status data.
• the network optimization application transmits the wireless device status data from that wireless device 12,18,20, 22 to a server 16 across the wireless network 14 when requested.
• the network status data is transmitted over an open communication connection from the wireless device 12,18,20,22 to the wireless network 14, and thus "piggybacked" across an open connection, such as a voice or data call at the cellular telephone 12.
• the wireless device status data can be transmitted to the server 12 through short message service.
• the specific process of the program executing on the server 16 for optimizing the wireless network 14 through use of the wireless device resident diagnostic interface is shown in the flowchart of Fig. 3.
• the process to send a data access agent to the wireless device starts, as shown at step 66, and a determination is made as to whether permission is required of the end-user to have the application pushed thereto, as shown at decision 68.
• a simple notification of the end-user may be all that is necessary to permit pushing of the application. If the end-user permission is required at decision 68, then a request to send a data access application (agent) is sent to a wireless device 12,18,20,22, as shown at step 70.
• step 74 the server 16 makes a determination as to whether an approval to transmit the agent has been received from the wireless device 12, 18,20,22, as shown at decision 72. If the approval has not been received at the server 16, then the process ends. Otherwise, if the approval has been received at the server 16 at decision 72, then the data access agent is transmitted to the wireless device 12,18,20,22 as shown at step 74, and then the wireless device 12,18,20,22 is prompted to transmit status data to the server 16, as shown at step 76.
• the prompting can be for any active status data, or any data stored at the wireless device 12,18, 20,22, or both.
• the server 16 also transmits the optimization command data back to the wireless device 12,18,20,22 such that the wireless device can modify its functionality in accord with the optimal network through, at least, manipulation of the diagnostic tools, as shown at step 84, although such step is preferable and not necessary to operation of the present system.
• a determination is made as to whether the wireless device has the requisite agents for future status data transmission, as shown at decision 86. If the wireless device 12,18,20,22 does have the proper network optimization application or agent to transmit status data, then the process returns to step 76 and selectively prompts the wireless device to transmit status data when necessary. Otherwise, if the wireless device 12,18,20,22 does not have the requisite application or agent, then the process returns to step 66 and attempts to load the specific application or agent onto the wireless device 12,18,20,22 with any end-user permission requested.
• Fig. 4 is a flowchart illustrating the process executing upon the computer platform 50 of a wireless device 12,18,20,22 in tandem with the process executing on the server 16 shown in the flowchart of Fig. 3.
• the wireless device 12,18,20,22 receives the attempted push of the agent, as shown at step 87, and then makes a determination as to whether end-user action is requested for the push attempt, as shown at decision 88. If end-user interaction is not requested, then the process forwards to step 96 and downloads the pushed agent. Otherwise, if end-user action is requested, the wireless device and prompts (or notifies) the end-user to download the network optimization application or agent, as shown at step 90.
• Such prompting could occur from an application installed on the wireless device 12,18,20,22 at manufacture and which prompts the end-user thereof for download permission during device configuration or at some other predefined moment.
• a determination is then made as to whether the end-user has accepted the download, as shown at decision 92. If not, the server 16 is notified of the end-user refusal to download the network optimization application or agent, as shown at step 94, and the download process terminates. Otherwise, if the end-user has accepted the download at decision 92, then the network optimization application or agent is downloaded (and preferably installed shortly thereafter) as shown at step 96.
• command data for network optimization has been sent from the server 16, as shown at decision 104.
• Such step corresponds to the command data transmission step 84 of the server 16 in Fig. 3, and is only one embodiment that can optimize the network through wireless device modification. If command data has been received at decision 104, then the wireless device 12,18,20,22 performance is modified based upon the received command data at least manipulating the device through the diagnostic interface to alter wireless device performance or operation, as shown at step 106. If there is no command data received at decision 104, or after wireless device modification at step 106, the process returns to determine if status data has been requested at decision 98. If the data access application or agent is only temporarily active, then the process will end after step 106, and will only resume upon the redownload of a data access application, i.e. return to step 90.
• Fig. 5 is an architecture diagram of the interaction between the carrier side devices and the diagnostic interface resident at the wireless device 12,18,20,22.
• the resident applications 110 include a diagnostic interface application 112 which allows the remote access of the diagnostic interface 118 of the chipset operating system (OS) 120.
• the Device OS 114 includes an application programming interface (API) extension to interface with the resident diagnostic interface 118 of the chipset OS 120.
• API application programming interface
• the diagnostic interface 118 is accessed through a software application extension in this embodiment, the interface can alternately be constructed in hardware or firmware, or combinations thereof with software.
• the importance of the interface is that the resident diagnostic interface 118, which is typically only accessible via a hardwire connection during manufacture or servicing, is accessible remotely such that the carrier or other network entity can access the diagnostic data and/or commands across the network, without a hardwire connection.
• 12,18,20,22 can then be uploaded from the wireless device through a standard HTTP, such as shown at block 124, or other FTP or data transfer protocols can be used.
• the device data is then gathered at a data server 126 and can be stored there or other processes can be executed thereupon, such as by post processor 130, which can include canonization, normalization, data mining or other process.
• post processor 130 which can include canonization, normalization, data mining or other process.
• Other business or commercial systems shown by block 128, can access the gathered data, preferably in a monitored fashion such as through a user manager 132 to maintain security and/or integrity of the data of the data server 126.
• Other computer devices, both storage and processing, can be located on the carrier side, and accordingly, the carrier architecture is readily scalable.
• the present system therefore provides a method for remotely interacting with a diagnostic interface 118 of a wireless device 12,18,20,22 across a wireless network 14, comprising the steps of establishing a wireless network 14 having at least data communication between computer devices selectively connected thereto, at least one of the computer devices a remotely located wireless device 12,18,20,22 including a computer platform 50, possibly having an end-user thereof, and the wireless device 12,18,20,22 including a resident diagnostic interface 118 through which at least status data include the wireless device status of the operating parameters of the wireless device and/or network 14 status data is accessible.
• the method can include the steps of accessing the wireless device diagnostic interface 118 from another computer device, such as server 16, across the wireless network 14, and gathering at least the status data of the wireless device 12,18,20,22 through the wireless device diagnostic interface 118.
• the method can further include the steps of selectively transmitting status data from at least one wireless device 12,18,20,22 to at least one other computer device, such as server 16, on the wireless network 14, and receiving the transmitted status data at the at least one other computer device.
• the method can include the step of optimizing the wireless network 14 based upon the received status data, and the step of transmitting wireless status data can occur from the execution of an application resident on the computer platform 50 of the at least one wireless device that accesses the diagnostic interface, such as diagnostic interface application 112.
• the method can also include the steps of transmitting command data across the wireless network 14 to the at least one wireless device 12,18,20,22, receiving the command data at the diagnostic interface 118 of the at least one wireless device, and modifying the wireless device operation through manipulation of operating parameters based upon the received command data.
• the method can include the step of pushing or pulling an application onto the computer platform 50 of the at least one wireless device 12,18,20,22 to provide access of one or more computer devices on the wireless network 14 to the diagnostic interface 118 of that wireless device, such as pushing diagnostic interface application 112 onto cellular telephone 12.
• the system can be implemented solely on the wireless device 12,18,20,22 that provides remote access to its resident diagnostic interface.
• the wireless device can have at least one application or agent resident (either permanent or temporarily) on the computer platform 50 thereof which causes the gathering of status data from the resident diagnostic tools, such as diagnostic interface application 112, which can effect selective transmission of the status data for that wireless device to another computer device (such as server 16) on the wireless network 14.
• the wireless device 12,18,20,22 is so embodied, the wireless device status data and/or network data is transmitted over an open communication connection from the wireless device 12,18,20,22 to the wireless network 14, such as an open voice or data call.
• the wireless device is a cellular telephone 12 and the wireless network is a cellular telecommunication network, such as shown in Fig. 2, the network status data can be transmitted through short message service or other wireless communication methods.
• the method includes a program resident in a computer readable medium, where the program directs a computer device 12,18,20,22 having a device platform 50 to perform the steps of the method.
• Such program can be executed on any single computer platform, or can be multithreaded among several computer platforms.
• the method can be implemented by a program that directs a computer device such as server 16 to perform the steps of optimizing the network through gathering and processing status data from the wireless devices 12,18,20,22.
• the computer readable medium can be the memory 56 of the computer platform
• the computer readable medium can be in a secondary storage media that is loadable onto a wireless device computer platform, such as a magnetic disk or tape, optical disk, hard disk, flash memory, or other storage media as is known in the art.
• the present method may be implemented, for example, by operating portion(s) of the wireless network 14 and/or LAN 30 to execute a sequence of machine-readable instructions, such as device platform 50 and server 16.
• the instructions can reside in various types of signal-bearing or data storage primary, secondary, or tertiary media.
• the media may comprise, for example, RAM (not shown) accessible by, or residing within, the components of the wireless network 14 or LAN 30.
• the instructions may be stored on a variety of machine-readable data storage media, such as DASD storage (e.g., a conventional "hard drive” or a RAID array), magnetic tape, electronic read-only memory (e.g., ROM, EPROM, or EEPROM), flash memory cards, an optical storage device (e.g. CD-ROM, WORM, DVD, digital optical tape), paper "punch” cards, or other suitable data storage media including digital and analog transmission media.
• DASD storage e.g., a conventional "hard drive” or a RAID array
• magnetic tape e.g., magnetic tape
• electronic read-only memory e.g., ROM, EPROM, or EEPROM
• flash memory cards e.g., an optical storage device
• an optical storage device e.g. CD-ROM, WORM, DVD, digital optical tape
• paper "punch” cards e.g. CD-ROM, WORM, DVD, digital optical tape
• paper "punch” cards e.g. CD

Priority Applications (8)

Applications Claiming Priority (4)

Publications (1)

Family

ID=30002690

Family Applications (1)

Country Status (11)

Cited By (13)

Families Citing this family (8)

Citations (2)

Family Cites Families (9)

• 2003
  • 2003-07-01 CN CN03815522.2A patent/CN1666543A/zh active Pending
  • 2003-07-01 EP EP03742417A patent/EP1518423A4/de not_active Withdrawn
  • 2003-07-01 BR BR0312352-9A patent/BR0312352A/pt not_active IP Right Cessation
  • 2003-07-01 AU AU2003280515A patent/AU2003280515A1/en not_active Abandoned
  • 2003-07-01 CA CA002490994A patent/CA2490994A1/en not_active Abandoned
  • 2003-07-01 JP JP2004518222A patent/JP2005532718A/ja active Pending
  • 2003-07-01 WO PCT/US2003/020920 patent/WO2004004381A1/en active Application Filing
  • 2003-07-01 NZ NZ537080A patent/NZ537080A/en not_active IP Right Cessation
  • 2003-07-01 RU RU2005102405/09A patent/RU2321968C2/ru not_active IP Right Cessation
  • 2003-07-01 MX MXPA04012321A patent/MXPA04012321A/es active IP Right Grant
• 2004
  • 2004-12-06 IL IL165579A patent/IL165579A/en not_active IP Right Cessation

Patent Citations (2)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events