US20020133598A1

Network communication

Claim Score by NHIP

Abstract

Mobile devices are networked to servers using connections. The connections are monitored to select one or more connections as the active connection. Information from applications is aggregated and transmitted across the active connection in order to network the mobile devices to the servers.

US20020133598A1, drawing sheet 1 — Sheet 1 of 8

Term

Term ended

Projected expiry passed 16 March 2021, 5.5 years ago.

30 claims: 5 independent, 25 dependent

1
A method comprising:at a device, opening a first connection to a server;establishing an information exchange protocol for communicating on the first connection;at a device, opening a second connection to the server;selecting an active connection from connections including the second connection;and communicating information configured for the information exchange protocol using the active connection.
12
Broadest claimClaim Score 92, very broad(NHIP)A method comprising:at a server, accepting connections from a device for communicating information configured by an information exchange protocol;detecting or selecting one or more of the connections of as an active connection;and communicating information configured by the information exchange protocol using the active connection.
19
An apparatus comprising a processor and software configured to cause the processor to:open a first connection to a server;establish an information exchange protocol;open a second connection to a server;select an active connection from connections including the second connection;and communicate information configured for the information exchange protocol using the active connection.
23
An article comprising a machine-readable medium that stores machine-executable instructions, the instructions causing a machine to:open a first connection to a server;establish an information exchange protocol;open a second connection to a server;select an active connection from the connections;and communicate information configured for the information exchange protocol using the active connection.
28
A system comprising:a device, a server, and communication links, in which the device is configured to: open a first connection to the server using one of the communication links;establish an information exchange protocol;open a second connection to the server using another of the communication links;select an active connection from connections including the second connection;communicate information configured for the information exchange protocol using the active connection.

Independent claims5

60 paragraphs in 3 sections, as filed

BACKGROUND

[0001] This invention relates to network communication.

[0002] Mobile devices, such as laptop computers, mobile phones, and handheld digital assistants, for example, communicate on wireless networks to enable their users to work in multiple locations and while in transit, such as in homes, airports, airplanes, and public spaces. Typically, the mobile devices run applications that access a server on the Internet by communicating using a single “connection.”

DESCRIPTION OF DRAWINGS

[0003]FIG. 1 is a diagram of network connections between a mobile client and a home agent.

[0004]FIG. 2 is a schematic of a tunnel state machine.

[0005]FIG. 3 is a flow chart of a process for connecting a mobile client.

[0006]FIG. 4 is a schematic of a mobile device.

[0007]FIG. 5 is a schematic of a stack for providing information to an application.

[0008]FIG. 6 is a schematic of information processing units implemented by a mobile client.

[0009]FIG. 7 is a schematic of information processing units implemented by a home agent or server.

DETAILED DESCRIPTION

[0010] A seamless and robust information exchange protocol for connecting a device to a secure network can include two or more open connections. The connections may be wireless and may be selectively and efficiently used to enhance information transmission speed and reliability.

[0011] Referring to the example shown in FIG. 1, a mobile (or immobile) device 110 establishes four exemplary connections or tunnels with a home agent 160. Examples of mobile devices include laptop computers, handheld computers (e.g., PalmPilots™, handheld digital assistants, key pads), pagers, mobile telephones (e.g., Wireless Application Protocol (WAP) enabled phones), Moving Picture Experts Group Audio Layer 3 (MP3) players, and game and/or entertainment stations. Examples of immobile devices include desktop computers, large appliances, and factory machines.

[0012] The terms “connection” and “tunnel” refer to a route for sending and/or receiving information. Information refers to both data (e.g., text, numeric, Boolean, addresses, graphical content, and the like) and commands (e.g., requests, instructions, queries and the like). The home agent can be a computer system (such as a desktop computer, a server, a server farm, or a mainframe).

[0013] Connection 114 is a wireless phone link (e.g., third generation wireless networks (3G), second-and-a-half generation wireless networks (2.5G), General Packet Radio Service (GPRS)), i-mode™ (NTT DoCoMo, Japan), Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), or Time Division Multiple Access (TDMA)/Digital Advanced Mobile Phone Service (D-AMPS) wireless link). This connection can be a modem connection that is relayed to an Internet service provider that connects the mobile client 110 to the Internet 140.

[0014] Connection 116 is a wireless connection to a local area network (LAN) 130 (e.g., a wireless LAN such as provided by wireless Ethernet, BlueTooth, the Institute of Electrical and Electronics Engineers (IEEE) 802.11a or 802.11b standard (IEEE std. 802.11-1999, published 1999), or Cellular Digital Packet Data (CDPD) connections). Information from this connection can optionally traverse a Foreign Network Address Translator (NAT)/Proxy 132 to connect from the intranet 130 to the Internet 140.

[0015] Connection 118 is a wired network connection, e.g., to a corporate intranet 130. Information from this connection also traverses the Foreign NAT/Proxy 132 to connect to the Internet 140.

[0016] Connection 120 is a direct connection to the Internet 140, e.g., a Digital Subscriber Line (DSL), Integrated Services Digital Network (ISDN), or cable modem connection. The Internet 140 directs the connections to the home agent 160 that is linked to the Internet by a corporate firewall 152. The home agent 160 can also be linked to a second intranet 150.

[0017] The mobile client 110 can be designed to flexibly use a variety of communication protocols (e.g., Transmission Control Protocol (TCP)/Internet Protocol (TCP/IP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), Post Office Protocol 3 (POP3), or other Internet protocols) for the purpose of communicating to the home agent 160, e.g., on the intranet 150. In some examples, the mobile client 110 is assigned an Internet Protocol (IP) address on the secure intranet 150. Applications running on the mobile client 110 issue network calls using the assigned IP address, typically, using a proxy module on the home agent 160. However, the connections between the mobile client 110 and the home agent 160 may require a different set of addresses. For example, the mobile client 110 may be a guest system having a guest IP address on a second intranet 130 or may be connected to the Internet 140 using a temporary Internet IP address, e.g., through a third party service provider. Addresses, such as the guest IP address and the temporary IP address, are invisible to applications running on the mobile client 110, but are used, e.g., by the network interfaces or operating system, to connect to the home agent 160.

[0018] The communication connections may use network address translation (NAT). NAT enables machines within a secure intranet to use a set of assigned IP addresses. NAT translates these assigned IP addresses to external IP addresses for communication with devices outside of the intranet. This protocol enhances network security and allows more efficient assignment of IP addresses within an intranet. Generally, the mobile client 110 will establish connections with the home agent through NAT, e.g., Foreign NAT/Proxy, 132. NAT 132 forwards information, e.g., across a public or insecure network, to the home agent 160 that resides securely behind a firewall 152. The home agent 160 processes the information from the mobile client 110, e.g., decompresses and decrypts the information, to allow the mobile client 110 to function securely with the advantages of a direct connection to an intranet or virtual private network (VPN) 150.

[0019] Referring to FIG. 2, each connection operates as a finite state machine. The connection can be disconnected 210, connecting 220, passive 230, or active 240. In the active state, a connection sends and receives information with the server. An active connection 240 is switched to passive 230 under certain circumstances, for example, if another connection is more efficient, secure, or economical. A user or system administrator may define parameters for such a switch. The system may monitor the active connection 240 and/or the passive connections 230 for one or more of the following parameters: signal strength, transmittal rate, latency, cost of transmittal, and connection integrity. Monitoring and switching of connections may be performed without the cognizance of the user.

[0020] An active connection 240 is switched to the disconnected state 210, for example, in the event of a loss of connection integrity (e.g. an abrupt break or a security breach). A disconnected connection 210 is switched to connecting 220 when appropriate.

[0021] A connecting connection 220 is switched to passive 230 once it is established and properly initialized. A passive connection 230 is generally not used to send or receive information except as necessary to monitor or maintain its integrity. In particular, a passive connection 230 is not used to send or receive application information. The passive connection 230 may be used to send instructions for its own activation. For example, if there is an abrupt disconnection of the active connection 240, either or both of the server 160 and the mobile client 110 can issue commands on a passive connection 230 indicating that it should be activated.

[0022] More than one connection may be active at a given time. Information is divided between such active connections 240, e.g., in proportion to the transfer rate of the particular connection, its latency, its reliability and so forth. The use of multiple connections at one time increases overall information transfer rates.

[0023] Referring now also to FIG. 3, the mobile client 110 scans 310 available network interfaces checking for ones that permit connection to the home agent 160. The connection process includes initializing communication protocols 320. Typically, the steps included in process 320 are only required for the initial connection 312. Thus, adding additional passive connections 230 and switching among active connections 240 are rapid and efficient.

[0024] To initialize a connection 320, network addressing 322 is initialized. For example, the mobile client 110 receives a Dynamic Host Configuration Protocol (DHCP) address from the home agent 160 or from another server. The mobile client 110 can also detect the presence of a proxy module on the home agent 160. Security protocols are established and authenticated 324 as are compression protocols 326. Examples of security protocols include transport layer security (TLS), secure sockets layers (SSL), and wireless TLS (WTLS). Non-limiting examples of a compression protocol include: “Lossless Compression” (LZS®) and Microcom Networking Protocol-5 (MNP5). Optionally, the mobile client 110 and home agent 160 exchange secondary authentication information, such as authenticated names, digital certificates and cookies.

[0025] Once the protocols are initialized for a session, initiation of additional connections (e.g., at least a second connection) to the home agent 160 only requires authentication 314 to verify that a new connection is between a mobile client 110 and/or a home agent 160 that are already party to a session. The same network, security, and compression protocols and parameters are used for information exchange as for the initial connection. For example, the common parameters for multiple sessions may include cryptographic keys, network address assignments, and compression formats (e.g., compression dictionaries). Accordingly, in such examples, all passive 230 and active connections 240 use the same security level. The precise level can be determined by a system administrator or user.

[0026] In other examples, the system uses different security protocols and/or compression levels for the different connections. The home agent 160 and mobile device 110 establish different security procedures for each connection, e.g., each passive or active tunnel, depending on the connection type. Thus, a connection that requires firewall traversal, e.g., a mobile phone link to the Internet, requires high level security, whereas a wired Ethernet connection to a LAN does not require such a high level of security.

[0027] The mobile client 110 and/or home agent 160 can be programmed to determine if additional connections should be opened 342. For example, parameters can be set for opening connections, e.g., based on the fee levied for using a particular connection, the connection speed, power drain (e.g., battery power required), and security. The system can scan available passive connections 230 and active connections 240 for a variety of criteria. For example, the mobile client 110 can assess the number of current connections (e.g. active or passive connections), their signal strength, and connection speed. The mobile client 110 can also detect its own geographic location to determine if it is in transit or leaving the effective range of a current connection, e.g., by using the global positioning system (GPS). Such parameters can be used to determine if additional connections should be opened 342, if active connections 240 should be switched 344, and if existing connections should be closed.

[0028] Similarly, the mobile client 110 and/or home agent 160 can be programmed to determine if the active connection 240 should be switched 360. Parameters for the decision can include the relative signal strength, latency, transmittal rate, security, cost (e.g., charge per minute or per byte), power drain, and reliability of the different connections. The process of switching 360 one connection from active 240 to passive 230 and another from passive 230 to active 240 is termed a “handoff.” The use of common information exchange protocols for all connections can facilitate handoff. For example, TCP timers, packet size and windows do not need to be reconfigured for handoff. This is important for abrupt handoffs when the active connection 240 is unexpectedly lost and a passive connection 230 must be promoted to active 240.

[0029] Referring to FIG. 4, an exemplary device 110 is equipped with a memory 412, and a processor 413 for executing instructions. The device 110 also has a console 414 (e.g., including a keyboard and display) for sending results to the user and for receiving user commands. The device 410 includes a chipset 420 or other interface for connecting the device's subsystems. The chipset 420 includes an input/output (I/O) interface 430 such as an I/O controller hub (ICH) or a basic I/O system (BIOS). For example, the ICH can be the Intel® 82801 ICH. The I/O interface is connected to two or more I/O units 432 and 434. These I/O units 432 and 434 are used to establish communication channels with the home agent 160. For example, the I/O units can include a modem, (e.g., a modem connected to an internal or external mobile phone, a cable modem), an I/R port, a network card, BlueTooth, packet cellular communicator, a satellite connection or a wireless interface (e.g., a wireless interface for CDPD, GPRS, GSM, 802.11a, 802.11b or BlueTooth).

[0030] Referring to FIG. 5, information from an application 510 running on a mobile client 110 is mapped to an application 560 running on a destination server 170 (i.e. a server other than the home agent 160). The mobile client 110 is connected to the destination server 170 through the home agent 160. The information is passed to a rate limiter 520 that monitors information transfer rates and quality of service parameters of the application.

[0031] In some examples, the rate limiter 520 implements the desired quality of service policy such that some application data is given bandwidth priority over other application data. The rate limiter 520 also guards against the mobile client 110 sending data to the home agent 160 faster than the home agent 160 can forward the data to its final destination, e.g., a destination server 170. The home agent 160 can instruct the rate limiter 520 on the client to slow down or stop sending data for a specific destination (e.g., the destination server 170) when the home agent 160 is excessively buffering data. This situation can occur, for example, when the mobile client 160 is sending data to a system with a slower wireless connection (e.g., the mobile client 160 is sending information to another mobile client through the home agent 160).

[0032] The flow indexer 521 monitors outgoing and incoming requests and information for the application. The flow indexer 521 can also frame information from the application with information for other applications. The mobility buffer 522 stores outgoing information (e.g., as packets) until an acknowledgement of its receipt is obtained from the home agent 160. If not receipt is received after an interval, the active connection 240 can be switched and the information (e.g., information packet) can be resent. Likewise, the mobility buffer 522 issues acknowledgments for information received from the home agent 160. The acknowledgements can be sent occasionally, e.g., along with outgoing data, to clear the other-side's mobility buffer. The acknowledgment can be time-insensitive. For example, the other-side's mobility buffer can send additional information before acknowledgments are received. The number of acknowledgments sent can be tailored to reflect the capacity of the other-size's mobility buffer. The mobility buffer sizes can be negotiated when opening the first connection between the client and home agent.

[0033] The information is then sent across a firewall 523. This process can include compression or decompression and/or encryption or decryption. Next, the information is sent to the transport socket 524 of the active connection 240.

[0034] The information is sent through the active connection 240 from the transport socket 524 on the mobile device 110 to the transport socket 534 on the home agent 160. The home agent 160 processes the information in a corresponding manner with firewall traversal 5337 mobility buffering and acknowledgement 532, application socket control 531, which similarly dissembles framed information and routes the data to its final destination on the network (e.g., an intranet or the Internet), and mobility rate control 530. These processes map incoming information to an application socket 540 on the home agent 160. This socket, in turn, can be linked to an application socket 550 on a destination server 170 that is networked to the home agent 160 by a VPN 150. Although the processes described above relates to information sent from the mobile device 110 to the home agent 160, the same processes can be executed for information flowing from the home agent 160 to the mobile device 110.

[0035] Application-specific information may be directed into the active connection 240 in various ways. Applications can be individually notified of the active connection 240 and can themselves direct information to the active connection 240. In other examples, all application-specific information is directed to a network interceptor that routes the information to the active connection 240. For example, applications network calls and data may be captured directly from the applications and forwarded to the home agent 160. In other examples, applications use local proxies, e.g., proxies running on the mobile client 110 to send traffic to the active connection 240.

[0036] In some examples, “sockets” are created as software objects which connect an application input/output stream to a network interface. Proxies are also used to process information from other applications.

[0037] Referring to FIG. 6 and proceeding from right to left, the mobile device 110 is running applications that use three application sockets 610, 611, and 612. An application that requires a network connection can employ one or more of the application sockets 610, 611, and 612. Information exchange to and from a socket is monitored by the flow indexer 616 and by socket control 620.

[0038] Outgoing information is processed by the flow indexer 616 and the rate limiter 622. Rate limiter 622 provides quality of service and protects against overflow of the home agent 160 buffer; the home agent 160 provides the rate limiter 622 with flow control notifications. Flow control systems (e.g., XON/XOFF or rate-based flow control systems) monitor information transfer rates, buffer load, and receipt acknowledgements. Flow control can be implemented on application and transport sockets on both the mobile client 110 and the home agent 160. For example, if the home agent 160 is unable to send information to a third destination 170 as fast as it receives it from the mobile client 110, the overflowing socket on the mobile client 110 is notified. Such measures can prevent the home agent 160 from buffering excessive data.

[0039] Outgoing information from multiple application sockets is packaged, compressed, encrypted and framed, by units including the upper encoder 624 and the lower encoder 630 via the mobility buffer 626. The mobility buffer 626 keeps a copy of the outgoing data until reception is acknowledged. If the active connection is lost and re-established (possibly on a different network interface), the content of mobility buffer 626 can be resent immediately, or, the computer (home agent or client) can wait for a mobility buffer acknowledgement (sent when a connection becomes active) before resending the exact amount of data the other side requires from the mobility buffer. The decision to send or wait before sending can be made based on the amount of data in the mobility buffer, the estimated bit rate of the active interface, cost of the interface and other values.

[0040] Router 640 directs traffic from the lower encoder 630 to the active transport socket (e.g., one of 660, 670, or 680). The active transport socket is a dedicated portal for information flow to the active connection 240. Information from the transport sockets to the application sockets is bi-directional. Information is secured using TLS or SSL protocols 666. The information is sent across the network firewall by the firewall traversal unit 664. Overflow information is buffered by the mobile client 110 using the outgoing overflow buffer 662. This information is stored until the home agent 160 acknowledges receipt of the contents, e.g., each segment of the contents).

[0041] Each transport socket 660, 670 and 680 is also monitored by a transport monitor 661, 671, and 681. General transport control 692 is overseen by the mobility control unit 642. General information flow is also monitored by the Statistics (Stats) collector 646.

[0042] Incoming information is processed to traverse the firewall 664, and then verified and decrypted by the TLS/SSL unit 666. Once processed the information is sent via unit 640 to the lower decoder 636, the lower dispatcher 638 and the upper decoder 634 and the upper dispatcher 632. These units can effect multiple information processing steps, e.g., removing framing information and decompressing and decrypting the information stream or packet. For example, socket control 620 routes information packets to the appropriate application socket 610, 611 and 612.

[0043] The flow indexer 622 determines the information transmittal rate of the transport socket and appropriately buffers and/or compresses the information. For example, for a slow connection, information is compressed to minimize information size, e.g., number of bytes, despite overhead in computational time to process the information. In contrast, for rapid connections, e.g., when the transmittal rate is not limiting, information is either not compressed or compressed using rapid algorithms that achieve more modest reduction in information size.

[0044] Information transmittal rates can also monitored by applications to indicate the capacity of the active connection 240. For example, if capacity is available, applications can process low-level background networking tasks, such as backing up and updating files. If capacity is limited, applications can reduce their communications burden, e.g., by requesting text or WAP pages instead of graphics.

[0045] Referring now to FIG. 7 and proceeding from left to right, the home agent 160 has a process configuration similar to the one for the mobile client 110. Information from connections is mapped to transport sockets 760 and 770. The information is sent for firewall traversal 764 and 774 and then for security verification and decryption 766 and 776. A router 740 directs incoming information to the lower decoder 736. Outgoing information is also directed by the router 740 toward the transport sockets 760 and 770 by way of output overflow buffers 762 and 772.

[0046] Mobility control 742 monitors the information overflow in these buffers 762 and 772, and can appropriately regulate outgoing information through the rate limiter 772, the router 740, and the lower encoder 730.

[0047] Incoming information is processed by the lower decoder 736 and the upper decoder 734. These decoders are linked to the lower dispatcher 738, which can issue tunnel or connection specific commands, and the upper dispatcher 732, which can issue application specific commands. The decoded information is dissembled into individual items and then distributed to the correct application sockets 710, 711, and 712 on the home agent 160. Hence, information from the application sockets 610, 611, and 612 running on the home agent 160, is mapped to corresponding application sockets 710, 711, and 712 on the home agent 160. As described above, these application sockets also generate outgoing information for delivery to the mobile device 110.

[0048] The information can be transmitted through the active connection 240 by a variety of methods, for example, in packets or as a continuous stream.

[0049] The information sent as packets can be framed. The information from different application sockets can be aggregated such that individual commands and data items from different applications are included in a single information packet. This packet is encrypted and compressed as a single unit using the previously initialized protocols thus obviating the need to include authentication, cryptographic, and compression headers. The packet is framed with minimal header information, such as a checksum and a packet identifier. On reception of the packet, an acknowledgement is issued for the entire packet, e.g., an identifier and/or checksum for the received information. The aggregation of data is in contrast to systems that emit individual data packets for each network call made or data item sent by individual applications. In addition to reducing overhead, framing multiple items together enables larger individual information packets, which can include related items. By placing related items together, the latency due to packet mis-alignment, such as occurs when conventional packets arrive out of order, is reduced.

[0050] Optionally, the protocol includes the reduction of “round trip” information exchanges. When desired, this feature determines if multiple information exchanges between the mobile device and a destination system 170 (i.e., a system other than the home agent 160) can by emulated by a proxy module running on the home agent 160. The proxy module interacts with the destination system 170 on behalf of the mobile client 110 without having to exchange information with the mobile client 110. The use of the proxy module reduces network traffic and overcomes inefficiencies due to the latency of some wireless connections. Proxy modules can be generic, e.g., able to support more than one application, or can be dedicated, e.g., application specific.

[0051] For example, the use of a web browser requires at least three round trips that can be obviated by a proxy module. Conventionally, when a user enters a uniform resource locator (URL) for a web site, the web browser on the mobile client 110 first sends a request to a domain name server to obtain the actual IP address of the URL. The mobile client 110 then initiates a TCP connection with the web server at the IP address. Only after confirmation does the mobile client 110 send a hypertext transfer protocol (HTTP) request to the web server and subsequently receive the hypertext content.

[0052] The use of a proxy module for the web browser instead replaces the three network roundtrips with a single exchange between the home agent 160 and the mobile client 110, thus reducing information traffic in the active connection 240. When a user enters a URL for a web site, this URL request is sent on the active connection 240 to a proxy module on the home agent 160 or on a destination server 170. The proxy module queries the domain name server, initiates the TCP connection, and sends the HTTP request. These steps are done without contacting the mobile client 110. When the proxy module receives the hypertext content, it directs it back over the active connection 240 to the mobile client 110.

[0053] An additional method to reduce network traffic is the use of application specific content re-purposing. This feature reformats information, particularly content. Extraneous content can be removed to reduce the amount of data. For example, data is translated by the home agent 160 from hypertext markup language (HTML) and graphics formats to i-mode or WAP compatible information.

[0054] Frequently, the client 110 and/or server 160 have more than one application sending information along a single active connection. Quality of service protocols are utilized to determine which application has priority for communicating information. Quality of service parameters can be implemented at many levels, for example, at the level of the upper encoder 624 and lower encoder 630 which frame network calls and data for different applications. The relative content of each framed data packet can be varied in accordance to quality of service parameters.

[0055] Further, the home agent 160, as well as the mobile client 110, can determine quality of service. Quality of service can be asymmetric such that an application may have high priority on the home agent 160 to send data to the mobile device 110, but may have low priority on the mobile device 110 for sending data to the home agent 160. A quality of service parameter indicating priority for information exchange can be transmitted from the home agent 160 to the mobile device 110 or from the mobile device 110 to the home agent 160.

[0056] Other implementations are within the scope of the claims.

[0057] For example, the techniques described here are not limited to any particular hardware or software configuration; they may find applicability in any computing or processing environment. The techniques may be implemented in hardware, software, or a combination of the two. The techniques may be implemented in programs executing on programmable machines such as mobile or stationary computers, personal digital assistants, and similar devices that each include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices.

[0058] Each program may be implemented in a high level procedural or object oriented programming language to communicate with a machine system. However, the programs can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language

[0059] Each such program may be stored on a storage medium or device, e.g., compact disc read only memory (CD-ROM), hard disk, magnetic diskette, or similar medium or device, that is readable by a general or special purpose programmable machine for configuring and operating the machine when the storage medium or device is read by the computer to perform the procedures described in this document. The system may also be implemented as a machine-readable storage medium, configured with a program, where the storage medium so configured causes a machine to operate in a specific and predefined manner.

[0060] The processes described here may be executed by an embedded system.

Contents3

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US7681202B2	Cited by	United States of America	Search report
US2004210528A1	Cited by	United States of America	Pre-grant
US8707291B2	Cited by	United States of America	Search report
US7437548B1	Cited by	United States of America	Applicant
US2008109560A1	Cited by	United States of America	Pre-grant
US8744936B2	Cited by	United States of America	Search report
US2010281162A1	Cited by	United States of America	Pre-grant
US2011099280A1	Cited by	United States of America	Pre-grant
US8601566B2	Cited by	United States of America	Search report
US7965633B2	Cited by	United States of America	Search report
US8475280B2	Cited by	United States of America	Search report
WO03036438A2	Cited by	World Intellectual Property Organization (WIPO)	International search
US2010115576A1	Cited by	United States of America	Pre-grant
US9246878B2	Cited by	United States of America	Applicant
US2006017972A1	Cited by	United States of America	Pre-grant
US8819274B2	Cited by	United States of America	Applicant
US8020201B2	Cited by	United States of America	Search report
US2003208601A1	Cited by	United States of America	Pre-grant
US7624165B2	Cited by	United States of America	Search report
US9479565B2	Cited by	United States of America	Applicant
US8572721B2	Cited by	United States of America	Applicant
US2010316047A1	Cited by	United States of America	Pre-grant
US7769869B2	Cited by	United States of America	Search report
US2008043760A1	Cited by	United States of America	Pre-grant
US2004063497A1	Cited by	United States of America	Pre-grant
FR2867004A1	Cited by	France	Search report
US2007043691A1	Cited by	United States of America	Pre-grant
US7716343B2	Cited by	United States of America	Search report
US7558873B1	Cited by	United States of America	Search report
US2007081512A1	Cited by	United States of America	Pre-grant
US9220010B2	Cited by	United States of America	Applicant
US8024416B2	Cited by	United States of America	Applicant
FR2867004A1	Cited by	France	Search report
US2006268820A1	Cited by	United States of America	Pre-grant
DE10244710A1	Cited by	Germany	Search report
US8271661B2	Cited by	United States of America	Applicant
US2003097592A1	Cited by	United States of America	Pre-grant
US2006041890A1	Cited by	United States of America	Pre-grant
US7734281B2	Cited by	United States of America	Search report
US8437345B2	Cited by	United States of America	Search report
US9277376B2	Cited by	United States of America	Applicant
US2016156507A1	Cited by	United States of America	Pre-grant
US2010128602A1	Cited by	United States of America	Pre-grant
WO03036438A3	Cited by	World Intellectual Property Organization (WIPO)	International search
US2015327101A1	Cited by	United States of America	Pre-grant
US2015236904A1	Cited by	United States of America	Pre-grant
US8522337B2	Cited by	United States of America	Search report
US7305252B2	Cited by	United States of America	Search report
US2008077707A1	Cited by	United States of America	Pre-grant
US10142806B2	Cited by	United States of America	Applicant
US8996678B2	Cited by	United States of America	Search report
US2003081783A1	Cited by	United States of America	Pre-grant
US2011296167A1	Cited by	United States of America	Pre-grant
US7918734B2	Cited by	United States of America	Search report
US2005124382A1	Cited by	United States of America	Pre-grant
US2006053223A1	Cited by	United States of America	Pre-grant
US2011065500A1	Cited by	United States of America	Pre-grant
US2013145434A1	Cited by	United States of America	Pre-grant
US2008034416A1	Cited by	United States of America	Pre-grant
US8200829B2	Cited by	United States of America	Search report
US2010268782A1	Cited by	United States of America	Pre-grant
US8160079B1	Cited by	United States of America	Search report
US7913294B1	Cited by	United States of America	Applicant
US8180879B2	Cited by	United States of America	Applicant
US2004151186A1	Cited by	United States of America	Pre-grant
US8667115B2	Cited by	United States of America	Applicant
US2014179362A1	Cited by	United States of America	Pre-grant
US8391181B2	Cited by	United States of America	Search report
US2007133411A1	Cited by	United States of America	Pre-grant
US7266365B2	Cited by	United States of America	Search report
US2002062384A1	Cites	United States of America	Pre-grant
US2004022191A1	Cites	United States of America	Pre-grant
US2005132049A1	Cites	United States of America	Pre-grant
US5812784A	Cites	United States of America	Pre-grant
US6198920B1	Cites	United States of America	Pre-grant
US6243581B1	Cites	United States of America	Pre-grant
US6400946B1	Cites	United States of America	Pre-grant
US6470390B1	Cites	United States of America	Pre-grant
US6614808B1	Cites	United States of America	Pre-grant
US6674713B1	Cites	United States of America	Pre-grant

16 members in 7 offices

This recordMember, by publication datePriority claim

Priority claims2

Priority claims
Document	Office	Kind	Date
81116101	United States of America	A	2001-03-16
US20010811161	–	–	–

Members16

Family members, oldest first
Document	Office	Kind
US2002133598A1	United States of America	A1	2002-09-19
WO02076063A1	World Intellectual Property Organization (WIPO)	A1	2002-09-26
AU2002248651A1	Australia	A1	2002-10-03
WO02076063A8	World Intellectual Property Organization (WIPO)	A8	2002-11-14
SE0302435D0	Sweden	D0	2003-09-12
FI20031292A	Finland	A	2003-11-12
SE0302435L	Sweden	L	2003-11-17
GB2389497A	United Kingdom	A	2003-12-10
GB2389497A8	United Kingdom	A8	2004-01-07
CN1498489A	China	A	2004-05-19
GB2389497B	United Kingdom	B	2004-08-04
SE526563C2	Sweden	C2	2005-10-11
FI120073B	Finland	B	2009-06-15
CN1498489B	China	B	2010-12-15
US2011096741A1	United States of America	A1	2011-04-28
US9282011B2	United States of America	B2	2016-03-08

126 transactions on the USPTO file

Abandoned after 3 non-final rejections, 3 final rejections, 2 RCEs and 1 appeal.

Non-final rejections: 3
Final rejections: 3
RCEs: 2
Appeals: 1

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event
2011-12-21	Change in Power of Attorney (May Include Associate POA)
2011-12-15	Correspondence Address Change
2011-10-14	Email Notification
2011-10-14	Mail of Abandonment after Examiner's Answer or PTAB DecisionAbandoned
2011-10-06	Abandonment after Examiner's Answer or PTAB DecisionAbandoned
2011-08-01	Case Docketed to Examiner in GAU
2011-07-22	Electronic Review
2011-07-22	Email Notification
2011-07-22	Mail PTAB Decision on Appeal - Affirmed
2011-07-20	PTAB Decision - Examiner Affirmed
2010-05-17	Change in Power of Attorney (May Include Associate POA)
2010-05-13	Correspondence Address Change
2009-06-17	Email Notification
2009-06-17	Docketing Notice Mailed to Appellant
2009-06-15	Assignment of Appeal Number
2009-06-08	Appeal Awaiting PTAB Docketing
2009-06-08	Email Notification
2009-06-08	Mail Reply Brief Noted by Examiner
2009-06-05	Case Docketed to Examiner in GAU
2009-06-03	Reply Brief Noted by Examiner
2009-04-24	Date Forwarded to Examiner
2009-04-16	Reply Brief Filed
2009-03-03	Exam. Ans. Review Complete
2009-02-17	Electronic Review
2009-02-17	Email Notification
2009-02-17	Mail Examiner's Answer
2009-02-12	Examiner's Answer to Appeal Brief
2008-12-04	Date Forwarded to Examiner
2008-11-07	Appeal Brief Filed
2008-10-10	Case Docketed to Examiner in GAU
2008-10-07	Email Notification
2008-10-07	Notice -- Defective Appeal Brief
2008-10-02	Appeal Brief Review Complete
2008-10-02	Date Forwarded to Examiner
2008-09-15	Defective / Incomplete Appeal Brief Filed
2008-09-15	Appeal Brief Filed
2008-08-13	Miscellaneous Incoming Letter
2008-07-14	Notice of Appeal Filed
2008-06-24	Mail Examiner Interview Summary (PTOL - 413)
2008-06-18	Interview Summary Record
2008-04-14	Mail Final Rejection (PTOL - 326)Final rejection
2008-04-11	Final RejectionFinal rejection
2008-02-06	Date Forwarded to Examiner
2008-01-28	Response after Non-Final Action
2008-01-28	Request for Extension of Time - Granted
2007-10-09	Information Disclosure Statement considered
2007-10-09	Information Disclosure Statement (IDS) Filed
2007-10-09	Information Disclosure Statement (IDS) Filed
2007-09-26	Mail Non-Final RejectionNon-final rejection
2007-09-20	Non-Final RejectionNon-final rejection
2007-07-19	Date Forwarded to Examiner
2007-07-19	Date Forwarded to Examiner
2007-07-19	Disposal for a RCE / CPA / R129
2007-07-16	Request for Continued Examination (RCE)
2007-07-16	Workflow - Request for RCE - Begin
2007-06-27	Mail Advisory Action (PTOL - 303)
2007-06-22	Advisory Action (PTOL-303)
2007-06-21	Date Forwarded to Examiner
2007-06-18	Response after Final Action
2007-03-16	Mail Final Rejection (PTOL - 326)Final rejection
2007-03-15	Final RejectionFinal rejection
2007-01-12	Date Forwarded to Examiner
2006-06-21	Response after Non-Final Action
2006-04-11	Mail Non-Final RejectionNon-final rejection
2006-04-10	Non-Final RejectionNon-final rejection
2006-02-08	Date Forwarded to Examiner
2006-02-08	Date Forwarded to Examiner
2006-02-08	Disposal for a RCE / CPA / R129
2006-01-27	Information Disclosure Statement considered
2006-01-27	Information Disclosure Statement (IDS) Filed
2006-01-27	Information Disclosure Statement (IDS) Filed
2006-01-27	Request for Continued Examination (RCE)
2006-01-27	Request for Extension of Time - Granted
2006-01-27	Workflow - Request for RCE - Begin
2005-10-27	Mail Advisory Action (PTOL - 303)
2005-10-26	Advisory Action (PTOL-303)
2005-10-17	Date Forwarded to Examiner
2005-09-26	Response after Final Action
2005-07-28	Mail Final Rejection (PTOL - 326)Final rejection
2005-07-25	Final RejectionFinal rejection
2005-06-17	Date Forwarded to Examiner
2005-06-09	Response after Non-Final Action
2005-06-09	Request for Extension of Time - Granted
2005-05-16	Case Docketed to Examiner in GAU
2005-04-05	Mail Notice of Informal or Non-Responsive Amendment
2005-03-30	Date Forwarded to Examiner
2005-03-02	Informal or Non-Responsive Amendment after Examiner Action
2005-03-02	Response after Non-Final Action
2005-02-04	Mail Notice of Informal or Non-Responsive Amendment
2004-12-07	IFW TSS Processing by Tech Center Complete
2004-12-07	Date Forwarded to Examiner
2004-10-15	Miscellaneous Incoming Letter
2004-10-15	Oath or Declaration Filed (Including Supplemental)
2004-10-15	Informal or Non-Responsive Amendment after Examiner Action
2004-10-15	Response after Non-Final Action
2004-10-15	Request for Extension of Time - Granted
2004-10-15	Workflow incoming amendment IFW
2004-07-14	Mail Non-Final RejectionNon-final rejection
2004-07-09	Non-Final RejectionNon-final rejection
2004-07-08	Preliminary Amendment

Showing 100 of 126

2 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2011-10-06	Information on status: application discontinuationABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISIONSTCB	STCB
2002-01-14	AssignmentAS	AS