US20110022727A1 - Handset cradle - Google Patents
Handset cradle Download PDFInfo
- Publication number
- US20110022727A1 US20110022727A1 US12/843,541 US84354110A US2011022727A1 US 20110022727 A1 US20110022727 A1 US 20110022727A1 US 84354110 A US84354110 A US 84354110A US 2011022727 A1 US2011022727 A1 US 2011022727A1
- Authority
- US
- United States
- Prior art keywords
- handset
- interface
- network
- component
- outbound
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
- H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/02—Constructional features of telephone sets
- H04M1/04—Supports for telephone transmitters or receivers
- H04M1/06—Hooks; Cradles
Definitions
- Different handset types can have different physical interface requirement for connecting to a computing device. Those handset types that do share the same physical interface requirements can often require different communication protocols for controlling the handset. The disparate physical interfaces and communication protocols make it difficult for a third party manufacturer to efficiently provide a product enabling the interaction between a computing device and the various types of available handsets.
- FIG. 1 illustrates an exemplary environment in which embodiments of the present invention can be implemented.
- FIGS. 2A and 2B schematically illustrate a handset cradle according to an embodiment of the present invention.
- FIG. 3 is a block diagram showing physical and logical components of a handset cradle according to an embodiment of the present invention.
- FIGS. 4-6 are exemplary flow diagram illustrating steps taken in performance of various embodiments of the present invention.
- I NTRODUCTION Current technology allows a handset such as cellular telephone to interact with a laptop or other computing device.
- a handset such as a cellular telephone can be used to connect a computing device to the Internet.
- Various embodiments described below utilize a handset cradle that provides an interface between one or more computing devices and handsets of various types.
- the handset cradle is modular incorporating a base component and a handset component.
- the base component provides the common functionality regardless of the type of handset. Different handset components are specialized to the physical interface and communication protocol requirements of different types of handsets. In short a handset component for a particular handset type provides an interface between a handset of that type and the base component. To provide a handset cradle for a given handset type, a handset component designed for that handset type is selected and coupled to a base component. To provide a handset cradle for another handset type, a handset component designed for that other handset type is selected and coupled to a base component.
- FIG. 1 illustrates exemplary environment 10 in which various embodiments of the present invention may be implemented.
- Environment 10 includes local network 12 and 12 ′, Internet service provider 14 and Internet 16 .
- Local network 12 includes network devices 18 handset cradle 20 , and handset 22 .
- local network 12 ′ includes network devices 18 ′ handset cradle 20 ′, and handset 22 ′.
- Network devices 18 and 18 ′ represent generally any devices capable of network communications. Examples include printers and computing devices such as laptop and desktop computer as well as PDAs (Personal Digital Assistants).
- Handsets 22 and 22 ′ represent generally any handheld electronic device. As shown handsets 22 and 22 ′ are cellular telephones capable of providing a connection to an external network—in this case—Internet service provider 14 and Internet 16 . Alternatively, for example, handsets 22 and 22 ′ could be cellular enabled PDAs. Handset cradles 20 and 20 ′, described in more detail below, are responsible for providing an interface between computing devices 18 and 18 ′ and handsets 22 and 22 ′ respectively. Handset cradles 20 and 20 ′ allow, for example local networks 12 and 12 ′ to access Internet 16 via handsets 22 and 22 ′.
- FIGS. 2A and 2B illustrate the modular construction of an exemplary handset cradle 20 .
- Handset cradle 20 includes base component 28 and handset component 30 .
- handset component 30 couples to base component 28 and is specifically configured to interface with handset 22 .
- handset component 30 allows base component 28 and handset 22 to interact.
- a different handset component (not shown) specifically configured to interface with a different type of handset (not shown) could instead be coupled to base component 28 . This would allow base component 28 and that different type of handset to interact.
- FIG. 3 is a block diagram illustrating physical and logical components of handset cradle 20 .
- handset cradle 20 includes base component 28 and handset component 30 .
- Handset component 30 includes handset interface 32 , base component interface 34 , and handset driver 36 .
- Handset interface 32 represents an interface through which a signal can be sent to a particular type of handset selected from a variety of handset types.
- handset interface 32 could be a physical interface shaped to support the particular handset while mating with that handset's physical connector—a male or female multi-pin connector for example.
- signals for controlling the operation of the particular type of handset can be sent through handset interface 32 and accepted by the handset via its own physical connector.
- a given signal may also include an electrical current for powering the handset or recharging the handset's battery.
- Base component interface 34 represents generally any interface capable of being utilized to couple handset component 30 to base component 28 .
- base component interface 34 may be a male or female multi-pin connector configured to mate with a matching connector supplied by base component 28 .
- Handset driver 36 represents generally any combination of hardware and/or program instructions capable of translating signals received through base component interface 34 into a format compatible with a specific type of handset selected from a variety of handset types—the particular type of handset being the same type of handset with which handset interface 32 is compatible. Handset driver 36 then can utilize handset interface 32 to send translated signals to a handset interfacing with handset component 30 .
- Handset driver 36 is also responsible for translating signals received from a handset into a format compatible with based component 28 .
- base component 28 includes handset component interface 42 , network interface 44 , user interface 46 , and power supply 48 .
- Handset component interface 42 represents generally any interface capable of being utilized to couple base component 28 to handset component 30 .
- handset component interface 42 may be a male or female multi-pin connector configured to mate with a matching base component interface 34 .
- Network interface 44 represent generally any hardware and/or program instructions capable of supplying an interface between based component 28 and one or more network devices (not shown).
- network interface 28 may include a transceiver operable to exchange network communications utilizing a wireless protocol such as ultrawideband (UWB), Bluetooth, or 802.11.
- network interface 44 may be a hub providing RJ45 (Registered Jack) connectors for connecting to one or more network devices.
- User interface 46 represents generally any hardware and/or program instructions enabling a user to interact directly with base component 28 .
- user interface 46 may include one or more buttons that when pressed send a corresponding signal.
- Power supply 48 represents generally any hardware capable of supplying power to a handset interfacing with handset component 30 .
- Base component 28 is also shown to include connector 50 , router 52 , and limiter 54 .
- Connector 50 represents hardware and/or program instructions for sending a signal to handset component 30 for a handset interfacing with handset component 30 to connect with an external network to which the handset can transmit outbound network communications. For example, where a handset is a cellular phone, connector 50 may send a signal to that when translated by handset component 30 causes a handset to dial a particular number through which an external network can be accessed.
- Router 52 represents hardware and/or program instructions for routing outbound network communication received through network interface 44 via handset component 30 to be transmitted by a handset to an external network. Router 52 is also responsible for routing inbound network communications received from the external network and directed via network interface 44 to a specified network device. Outbound and inbound network communications, for example can be an IP (internet Protocol) packets directed to a target on an external network or to a particular network device on the local area network.
- IP Internet Protocol
- Limiter 54 represents hardware and/or program instructions capable of limiting inbound and outbound network communications. Where a handset in the form of a cellular telephone is used to establish a connection to an external network, outbound and inbound network communications are transmitted wirelessly and consume bandwidth allotted to a particular cellular service provider. As will be described, limiter 54 functions to help reduce the risk of over-utilizing the limited bandwidth available to all cellular telephones.
- base component 56 is also shown to include handset module 56 , web server 58 , and configuration data 59 .
- Handset module 56 represents hardware and/or programming capable of initiating and/or performing an action taken with regard to a handset interfacing with handset component 30 .
- Handset module 56 might then be configured to interact with that handset via handset component 30 and retrieve one or more digital images and then send those images through network interface 44 to a network device such as a color printer for production. This process may be initiated by a user pressing a button supplied by user interface 46 .
- Handset module 56 might then be configured to interact with that handset via handset component 30 to access the personal data and then to synchronize or initiate the synchronization of that data with personal data stored on a network device. This process may by initiated be a handset module 56 upon detecting the handset being connected to handset component 30 .
- Web server 58 represents generally any hardware and or program instructions capable of serving an interface such as a web page that when requested and displayed by a network device allows a user to provide or otherwise select configuration settings related to the operation of handset cradle 20 .
- Configuration data 59 represents generally any memory for storing configuration settings so that they can be accessed by connector 50 , router 52 , limiter 54 , and handset module 56 parameter settings.
- Configuration settings can include a telephone number to call to establishing a connection with an external network.
- Configuration settings can include data identifying the maximum number of concurrent outbound network device sessions allowed.
- Configuration settings can also include data assigning a particular button provided user interface 48 to a particular function of handset module 56 .
- a configuration setting may indicate that when a user presses a user interface button, handset module 56 will retrieve a digital image or other file from a handset and send that file to a network device such as a printer.
- limiter 54 includes session limiter 60 and bandwidth limiter 61 .
- Session limiter 60 represents hardware and/or program instructions for limiting the routing of outbound network communications to those outbound network communications originating from one or more specified network devices.
- an outbound network communication sent from a particular network device may be received by base component 28 at a time when a handset interfacing to handset component 30 has not established a connection to an external network. In such a case, the outbound communication is held and connector 50 sends a signal resulting in the handset establishing a connection and the outbound network communication is routed.
- the outbound network communication will in some manner identify the network device from which it originated. The identification may, for example come in the form of an IP (Internet Protocol) address or MAC (Media Access Control) address. As long as a connection to the external network is maintained, Session limiter 60 will only allow outbound communications identifying that network device to be routed.
- IP Internet Protocol
- MAC Media Access Control
- session limiter 60 The period for which session limiter 60 routs of outbound communications from a particular network device is referred to as an outbound network device session.
- session limiter 60 only allowed one outbound network device session at a time—that session being for the network device whose outbound network communication caused a connection to be established with an external network.
- session limiter 60 may allow two or more concurrent outbound network device sessions up to a maximum number. In this case session limiter 60 would prevent the routing of an outbound communication from a particular network device if routing the outbound communication would cause the number of concurrent outbound network device sessions to exceed the maximum number allowed.
- data identifying the maximum number allowed may be received from a cellular service provider. This data may be received once a cellular phone handset initializes communication with a cellular service provider even before a connection is made to the external network.
- the maximum number allowed may be based on a subscription plan corresponding to the cellular phone handset, Handset component 30 would pass that data on to base component 28 —specifically session limiter 60 . Until the connection to the external network is dropped, limiter 54 could then keep a running count of the number of concurrent outbound network device sessions and prevent that number from exceeding the maximum number allowed.
- session limiter 60 might allow outbound network device sessions to be established for a given number of network devices—that number being the maximum number of concurrent network device sessions allowed.
- the first outbound network device session would be established for the network device that caused the connection to be made to the external network.
- Another outbound network device session is established for each additional network device from which an outbound network communication is received. Session limiter 60 allows this to continue until the routing of the next outbound network communication would cause the number of concurrent sessions to exceed the maximum number allowed.
- Bandwidth limiter 61 represents hardware and/or program instructions for selectively restricting outbound and inbound network communications based on one or more policies. Based on those policies, the restrictions may selectively limit or even cut off the available bandwidth for certain types or all types of inbound and outbound network communications.
- policies may be constant while other policies may be based on observed user behaviors.
- a constant policy may specify zero bandwidth availability for outbound and inbound network communications transferring specific file types such as ring tones, wallpaper, and larger files such copies of movies and other video files.
- outbound and inbound network communications are transmitted wirelessly and consume the limited bandwidth allotted to a particular cellular service provider. Users engaging in file sharing, computers infected with viruses, and denial of service attacks all pose risks that the allotted bandwidth will be over-utilized.
- a constant policy may specify a time duration for which inbound and outbound communications can consume a specified bandwidth. Once that duration expires, the policy may specify a second duration for which bandwidth will be limited. If the second duration is allowed to expire, the available bandwidth may be limited further. This process can repeat until the available bandwidth is clamped down to zero for yet another specified duration. Once this duration expires bandwidth limits may be removed or stepped back up.
- a running count may be—kept of the number of time the available bandwidth is clamped down to zero. Once that running count reaches a specified number, all outbound and/or inbound communications may be blocked until a reset signal is given by a cellular service provider.
- bandwidth limiter 61 may identify that on average, a user sends a specified number of electronic mail messages in a day or other specified duration. When that specified number is exceeded by a threshold amount, bandwidth limiter 61 may block outbound electronic mail messages for the remainder of the duration. This can help to limit the effect of viruses that hijack a network device and use that device to spread by sending copies of itself vial electronic mail messages.
- Bandwidth limiter 61 may identify on average that a user receives a specified number of electronic mail messages a day or other specified duration. When that specified number is exceeded by a threshold amount, bandwidth limiter 61 may block inbound electronic mail messages for the remainder of the duration. This can help to limit the effect of a denial of service attack.
- Bandwidth limiter 61 may identify average block sizes for outbound or inbound communications. When, for a specified duration, the block sizes exceed the average by a threshold level, inbound or outbound communication may be blocked or, as described above, clamped down.
- FIG. 4 is an exemplary flow diagram that helps illustrate the interaction between a base component and a handset component of a handset cradle.
- a base component receives a signal indicative of an action to be performed with respect to a handset interfacing with the handset component (step 62 ).
- this signal can come in the form of an outbound network communication receive from a network device.
- the signal can come from a user interacting with a user interface.
- the signal can also result from the handset being connected with the handset component.
- step 64 The base component then instructs the performance of the action (step 64 ).
- the handset component in response to the instructions from the base component, causes the performance of the action (step 66 ).
- step 64 can involve routing an outbound network communication via the handset component to be transmitted by the handset.
- Step 66 then involves the handset component forwarding the outbound network communication in the proper format to the handset for transmission.
- Step 64 can involve sending a signal to the handset component for use in causing the handset to perform a task such as returning a digital image to be produced or personal data to be synchronized.
- Step 66 then involves the handset component forwarding the signal in the proper format to be acted upon by the handset.
- FIG. 5 is an exemplary flow diagram that helps illustrate the interaction between a base component and a handset component of a handset cradle to route an outbound network communication.
- the base component receives an outbound network communication (step 68 ). It is determined if a handset interfacing with the handset component has established a connection to an external network (step 70 ). If a connection has already been established the process skips ahead to step 76 . Otherwise, the base component instructs that a connection be established (step 72 ). The handset component then causes the handset to establish a connection with an external network (step 74 ). The base component instructs that the outbound network communication be routed (step 76 ). The handset component causes the outbound network communication to be routed through the handset to the external network (step 78 ).
- FIG. 6 is an exemplary flow diagram that helps illustrate the interaction between a base component and a handset component of a handset cradle to limit the routing of an outbound network communication.
- the base component receives an outbound network communication (step 80 ).
- the source of the outbound network communication is identified (step 82 ). Where for example, the source of the outbound network communication is a particular network device, identifying the device may include identifying an address such as an IP or MAC address for that device.
- Step 84 It is determined if a handset interfacing with the handset component has established a connection to an external network (step 84 ). If a connection has already been established the process skips ahead to step 88 . Otherwise, the base component instructs that a connection be established and the handset component then causes the handset to establish a connection with an external network (step 86 ). It is then determined if there is an available network device session (step 88 ). Step 88 can, for example, involve determining if routing the outbound communication will cause the number of concurrent outbound network device session to exceed a maximum number allowed.
- routing the outbound communication will require a new session to be established.
- routing the outbound communication will not require a new session to be established.
- Establishing an outbound network device session may involve setting a flag or other indicator noting that an outbound communication received from a particular network device has been routed. That flag or indicator can be reset when once a connection to the external network is dropped.
- step 88 it is determined that there is an available outbound network device session, the outbound communication is routed (step 90 ). Where in step 88 it is determined that there is not an available outbound network device session, the outbound communication is blocked (step 92 ).
- FIG. 1 illustrates an exemplary environment in which embodiments of the present invention may be implemented. Implementation, however, is not limited to this environment.
- FIGS. 2 and 3 show the architecture, functionality, and operation of various embodiments of the present invention.
- a number of the blocks are defined as programs. Each of those blocks may represent in whole or in part a module, segment, or portion of code that comprises one or more executable instructions to implement the specified logical function(s). Each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).
- Computer-readable media can be any media that can contain, store, or maintain programs and data for use by or in connection with the instruction execution system.
- Computer readable media can comprise any one of many physical media such as, for example, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor media.
- suitable computer-readable media include, but are not limited to, a portable magnetic computer diskette such as floppy diskettes or hard drives, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory, or a portable compact disc.
- a portable magnetic computer diskette such as floppy diskettes or hard drives
- RAM random access memory
- ROM read-only memory
- erasable programmable read-only memory erasable programmable read-only memory
- FIGS. 4-6 show a specific orders of execution, the orders of execution may differ from that which is depicted.
- the order of execution of two or more blocks may be scrambled relative to the order shown.
- two or more blocks shown in succession may be executed concurrently or with partial concurrence. All such variations are within the scope of the present invention.
Abstract
Description
- Current technology allows a handset such as cellular telephone to interact with a laptop or other computing device. This typically requires physically connecting the handset to the computing device as well as installing and configuring specialized software. Such interactions can allow a computing device to utilize a handset to access the Internet.
- Different handset types can have different physical interface requirement for connecting to a computing device. Those handset types that do share the same physical interface requirements can often require different communication protocols for controlling the handset. The disparate physical interfaces and communication protocols make it difficult for a third party manufacturer to efficiently provide a product enabling the interaction between a computing device and the various types of available handsets.
-
FIG. 1 illustrates an exemplary environment in which embodiments of the present invention can be implemented. -
FIGS. 2A and 2B schematically illustrate a handset cradle according to an embodiment of the present invention. -
FIG. 3 is a block diagram showing physical and logical components of a handset cradle according to an embodiment of the present invention. -
FIGS. 4-6 are exemplary flow diagram illustrating steps taken in performance of various embodiments of the present invention. - I
NTRODUCTION : Current technology allows a handset such as cellular telephone to interact with a laptop or other computing device. For example, a handset such as a cellular telephone can be used to connect a computing device to the Internet. Various embodiments described below utilize a handset cradle that provides an interface between one or more computing devices and handsets of various types. - As is described below, the handset cradle is modular incorporating a base component and a handset component. The base component provides the common functionality regardless of the type of handset. Different handset components are specialized to the physical interface and communication protocol requirements of different types of handsets. In short a handset component for a particular handset type provides an interface between a handset of that type and the base component. To provide a handset cradle for a given handset type, a handset component designed for that handset type is selected and coupled to a base component. To provide a handset cradle for another handset type, a handset component designed for that other handset type is selected and coupled to a base component.
- E
NVIRONMENT :FIG. 1 illustratesexemplary environment 10 in which various embodiments of the present invention may be implemented.Environment 10 includeslocal network Internet service provider 14 and Internet 16.Local network 12 includesnetwork devices 18handset cradle 20, andhandset 22. Similarly,local network 12′ includesnetwork devices 18′ handset cradle 20′, andhandset 22′.Network devices -
Handsets handsets Internet service provider 14 and Internet 16. Alternatively, for example,handsets computing devices handsets local networks handsets - C
RADLE :FIGS. 2A and 2B illustrate the modular construction of anexemplary handset cradle 20.Handset cradle 20 includesbase component 28 andhandset component 30. As is shown,handset component 30 couples tobase component 28 and is specifically configured to interface withhandset 22. In this manner,handset component 30 allowsbase component 28 andhandset 22 to interact. A different handset component (not shown) specifically configured to interface with a different type of handset (not shown) could instead be coupled tobase component 28. This would allowbase component 28 and that different type of handset to interact. -
FIG. 3 is a block diagram illustrating physical and logical components ofhandset cradle 20. As described above,handset cradle 20 includesbase component 28 andhandset component 30.Handset component 30 includeshandset interface 32,base component interface 34, andhandset driver 36.Handset interface 32 represents an interface through which a signal can be sent to a particular type of handset selected from a variety of handset types. For example,handset interface 32 could be a physical interface shaped to support the particular handset while mating with that handset's physical connector—a male or female multi-pin connector for example. In this manner signals for controlling the operation of the particular type of handset can be sent throughhandset interface 32 and accepted by the handset via its own physical connector. In addition to controlling the functional aspects of the handset, a given signal may also include an electrical current for powering the handset or recharging the handset's battery. -
Base component interface 34 represents generally any interface capable of being utilized to couplehandset component 30 tobase component 28. For example,base component interface 34 may be a male or female multi-pin connector configured to mate with a matching connector supplied bybase component 28.Handset driver 36 represents generally any combination of hardware and/or program instructions capable of translating signals received throughbase component interface 34 into a format compatible with a specific type of handset selected from a variety of handset types—the particular type of handset being the same type of handset with whichhandset interface 32 is compatible.Handset driver 36 then can utilizehandset interface 32 to send translated signals to a handset interfacing withhandset component 30.Handset driver 36 is also responsible for translating signals received from a handset into a format compatible with basedcomponent 28. - In the example shown,
base component 28 includes handset component interface 42,network interface 44,user interface 46, andpower supply 48. Handset component interface 42 represents generally any interface capable of being utilized tocouple base component 28 tohandset component 30. For example, handset component interface 42 may be a male or female multi-pin connector configured to mate with a matchingbase component interface 34. -
Network interface 44 represent generally any hardware and/or program instructions capable of supplying an interface between basedcomponent 28 and one or more network devices (not shown). For example,network interface 28 may include a transceiver operable to exchange network communications utilizing a wireless protocol such as ultrawideband (UWB), Bluetooth, or 802.11. Alternatively,network interface 44 may be a hub providing RJ45 (Registered Jack) connectors for connecting to one or more network devices. -
User interface 46 represents generally any hardware and/or program instructions enabling a user to interact directly withbase component 28. For example,user interface 46 may include one or more buttons that when pressed send a corresponding signal.Power supply 48 represents generally any hardware capable of supplying power to a handset interfacing withhandset component 30. -
Base component 28 is also shown to includeconnector 50,router 52, andlimiter 54.Connector 50 represents hardware and/or program instructions for sending a signal tohandset component 30 for a handset interfacing withhandset component 30 to connect with an external network to which the handset can transmit outbound network communications. For example, where a handset is a cellular phone,connector 50 may send a signal to that when translated byhandset component 30 causes a handset to dial a particular number through which an external network can be accessed. -
Router 52 represents hardware and/or program instructions for routing outbound network communication received throughnetwork interface 44 viahandset component 30 to be transmitted by a handset to an external network.Router 52 is also responsible for routing inbound network communications received from the external network and directed vianetwork interface 44 to a specified network device. Outbound and inbound network communications, for example can be an IP (internet Protocol) packets directed to a target on an external network or to a particular network device on the local area network. -
Limiter 54, discussed in more detail below, represents hardware and/or program instructions capable of limiting inbound and outbound network communications. Where a handset in the form of a cellular telephone is used to establish a connection to an external network, outbound and inbound network communications are transmitted wirelessly and consume bandwidth allotted to a particular cellular service provider. As will be described, limiter 54 functions to help reduce the risk of over-utilizing the limited bandwidth available to all cellular telephones. - In the example of
FIG. 3 ,base component 56 is also shown to includehandset module 56,web server 58, andconfiguration data 59.Handset module 56 represents hardware and/or programming capable of initiating and/or performing an action taken with regard to a handset interfacing withhandset component 30. Imagine a handset capable of taking and storing digital images.Handset module 56 might then be configured to interact with that handset viahandset component 30 and retrieve one or more digital images and then send those images throughnetwork interface 44 to a network device such as a color printer for production. This process may be initiated by a user pressing a button supplied byuser interface 46. - Imagine a handset capable of storing personal data such as appointments and electronic mail messages.
Handset module 56 might then be configured to interact with that handset viahandset component 30 to access the personal data and then to synchronize or initiate the synchronization of that data with personal data stored on a network device. This process may by initiated be ahandset module 56 upon detecting the handset being connected tohandset component 30. -
Web server 58 represents generally any hardware and or program instructions capable of serving an interface such as a web page that when requested and displayed by a network device allows a user to provide or otherwise select configuration settings related to the operation ofhandset cradle 20.Configuration data 59 represents generally any memory for storing configuration settings so that they can be accessed byconnector 50,router 52,limiter 54, andhandset module 56 parameter settings. - Configuration settings can include a telephone number to call to establishing a connection with an external network. Configuration settings can include data identifying the maximum number of concurrent outbound network device sessions allowed. Configuration settings can also include data assigning a particular button provided
user interface 48 to a particular function ofhandset module 56. Using the example above a configuration setting may indicate that when a user presses a user interface button,handset module 56 will retrieve a digital image or other file from a handset and send that file to a network device such as a printer. - In the example of
FIG. 3 ,limiter 54 includessession limiter 60 andbandwidth limiter 61.Session limiter 60 represents hardware and/or program instructions for limiting the routing of outbound network communications to those outbound network communications originating from one or more specified network devices. As an example, an outbound network communication sent from a particular network device may be received bybase component 28 at a time when a handset interfacing tohandset component 30 has not established a connection to an external network. In such a case, the outbound communication is held andconnector 50 sends a signal resulting in the handset establishing a connection and the outbound network communication is routed. The outbound network communication will in some manner identify the network device from which it originated. The identification may, for example come in the form of an IP (Internet Protocol) address or MAC (Media Access Control) address. As long as a connection to the external network is maintained,Session limiter 60 will only allow outbound communications identifying that network device to be routed. - The period for which
session limiter 60 routs of outbound communications from a particular network device is referred to as an outbound network device session. In the example above,session limiter 60 only allowed one outbound network device session at a time—that session being for the network device whose outbound network communication caused a connection to be established with an external network. In an alternative embodiment,session limiter 60 may allow two or more concurrent outbound network device sessions up to a maximum number. In thiscase session limiter 60 would prevent the routing of an outbound communication from a particular network device if routing the outbound communication would cause the number of concurrent outbound network device sessions to exceed the maximum number allowed. - For example, data identifying the maximum number allowed may be received from a cellular service provider. This data may be received once a cellular phone handset initializes communication with a cellular service provider even before a connection is made to the external network. The maximum number allowed may be based on a subscription plan corresponding to the cellular phone handset,
Handset component 30 would pass that data on tobase component 28—specificallysession limiter 60. Until the connection to the external network is dropped,limiter 54 could then keep a running count of the number of concurrent outbound network device sessions and prevent that number from exceeding the maximum number allowed. - For example, on a first come first serve basis,
session limiter 60 might allow outbound network device sessions to be established for a given number of network devices—that number being the maximum number of concurrent network device sessions allowed. The first outbound network device session would be established for the network device that caused the connection to be made to the external network. Another outbound network device session is established for each additional network device from which an outbound network communication is received.Session limiter 60 allows this to continue until the routing of the next outbound network communication would cause the number of concurrent sessions to exceed the maximum number allowed. -
Bandwidth limiter 61 represents hardware and/or program instructions for selectively restricting outbound and inbound network communications based on one or more policies. Based on those policies, the restrictions may selectively limit or even cut off the available bandwidth for certain types or all types of inbound and outbound network communications. - Certain policies may be constant while other policies may be based on observed user behaviors. For example, a constant policy may specify zero bandwidth availability for outbound and inbound network communications transferring specific file types such as ring tones, wallpaper, and larger files such copies of movies and other video files.
- As noted above where a handset in the form of a cellular telephone is used to establish a connection to an external network, outbound and inbound network communications are transmitted wirelessly and consume the limited bandwidth allotted to a particular cellular service provider. Users engaging in file sharing, computers infected with viruses, and denial of service attacks all pose risks that the allotted bandwidth will be over-utilized.
- To deter file sharing, a constant policy may specify a time duration for which inbound and outbound communications can consume a specified bandwidth. Once that duration expires, the policy may specify a second duration for which bandwidth will be limited. If the second duration is allowed to expire, the available bandwidth may be limited further. This process can repeat until the available bandwidth is clamped down to zero for yet another specified duration. Once this duration expires bandwidth limits may be removed or stepped back up. A running count may be—kept of the number of time the available bandwidth is clamped down to zero. Once that running count reaches a specified number, all outbound and/or inbound communications may be blocked until a reset signal is given by a cellular service provider.
- Policies based on observed user behavior may also deter file sharing while helping limit the effects of virus and denial of service attacks. For example,
bandwidth limiter 61 may identify that on average, a user sends a specified number of electronic mail messages in a day or other specified duration. When that specified number is exceeded by a threshold amount,bandwidth limiter 61 may block outbound electronic mail messages for the remainder of the duration. This can help to limit the effect of viruses that hijack a network device and use that device to spread by sending copies of itself vial electronic mail messages. -
Bandwidth limiter 61 may identify on average that a user receives a specified number of electronic mail messages a day or other specified duration. When that specified number is exceeded by a threshold amount,bandwidth limiter 61 may block inbound electronic mail messages for the remainder of the duration. This can help to limit the effect of a denial of service attack. - When transferring larger files such as movies, block sizes for inbound and outbound communications are relatively large.
Bandwidth limiter 61 may identify average block sizes for outbound or inbound communications. When, for a specified duration, the block sizes exceed the average by a threshold level, inbound or outbound communication may be blocked or, as described above, clamped down. - OPERATION: The operation of embodiments of the present invention will now be described with reference to
FIGS. 4-6 .FIG. 4 is an exemplary flow diagram that helps illustrate the interaction between a base component and a handset component of a handset cradle. Initially a base component receives a signal indicative of an action to be performed with respect to a handset interfacing with the handset component (step 62). In the examples above, this signal can come in the form of an outbound network communication receive from a network device. The signal can come from a user interacting with a user interface. The signal can also result from the handset being connected with the handset component. - The base component then instructs the performance of the action (step 64). The handset component, in response to the instructions from the base component, causes the performance of the action (step 66). Using the examples again from above, step 64 can involve routing an outbound network communication via the handset component to be transmitted by the handset.
Step 66 then involves the handset component forwarding the outbound network communication in the proper format to the handset for transmission.Step 64 can involve sending a signal to the handset component for use in causing the handset to perform a task such as returning a digital image to be produced or personal data to be synchronized.Step 66 then involves the handset component forwarding the signal in the proper format to be acted upon by the handset. -
FIG. 5 is an exemplary flow diagram that helps illustrate the interaction between a base component and a handset component of a handset cradle to route an outbound network communication. Initially, the base component receives an outbound network communication (step 68). It is determined if a handset interfacing with the handset component has established a connection to an external network (step 70). If a connection has already been established the process skips ahead to step 76. Otherwise, the base component instructs that a connection be established (step 72). The handset component then causes the handset to establish a connection with an external network (step 74). The base component instructs that the outbound network communication be routed (step 76). The handset component causes the outbound network communication to be routed through the handset to the external network (step 78). -
FIG. 6 is an exemplary flow diagram that helps illustrate the interaction between a base component and a handset component of a handset cradle to limit the routing of an outbound network communication. Initially, the base component receives an outbound network communication (step 80). The source of the outbound network communication is identified (step 82). Where for example, the source of the outbound network communication is a particular network device, identifying the device may include identifying an address such as an IP or MAC address for that device. - It is determined if a handset interfacing with the handset component has established a connection to an external network (step 84). If a connection has already been established the process skips ahead to step 88. Otherwise, the base component instructs that a connection be established and the handset component then causes the handset to establish a connection with an external network (step 86). It is then determined if there is an available network device session (step 88).
Step 88 can, for example, involve determining if routing the outbound communication will cause the number of concurrent outbound network device session to exceed a maximum number allowed. - Where an outbound network device session has not already been established for the network device identified in
step 82, routing the outbound communication will require a new session to be established. Where an outbound network device session has already been established for the network device identified instep 82, routing the outbound communication will not require a new session to be established. Establishing an outbound network device session may involve setting a flag or other indicator noting that an outbound communication received from a particular network device has been routed. That flag or indicator can be reset when once a connection to the external network is dropped. - Where in
step 88 it is determined that there is an available outbound network device session, the outbound communication is routed (step 90). Where instep 88 it is determined that there is not an available outbound network device session, the outbound communication is blocked (step 92). - CONCLUSION: The schematic diagrams of
FIG. 1 illustrates an exemplary environment in which embodiments of the present invention may be implemented. Implementation, however, is not limited to this environment. The diagrams ofFIGS. 2 and 3 show the architecture, functionality, and operation of various embodiments of the present invention. A number of the blocks are defined as programs. Each of those blocks may represent in whole or in part a module, segment, or portion of code that comprises one or more executable instructions to implement the specified logical function(s). Each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s). - Also, the present invention can be embodied in any computer-readable media for use by or in connection with an instruction execution system such as a computer/processor based system or an ASIC (Application Specific Integrated Circuit) or other system that can fetch or obtain the logic from computer-readable media and execute the instructions contained therein. “Computer-readable media” can be any media that can contain, store, or maintain programs and data for use by or in connection with the instruction execution system. Computer readable media can comprise any one of many physical media such as, for example, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor media. More specific examples of suitable computer-readable media include, but are not limited to, a portable magnetic computer diskette such as floppy diskettes or hard drives, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory, or a portable compact disc.
- Although the flow diagram of
FIGS. 4-6 show a specific orders of execution, the orders of execution may differ from that which is depicted. For example, the order of execution of two or more blocks may be scrambled relative to the order shown. Also, two or more blocks shown in succession may be executed concurrently or with partial concurrence. All such variations are within the scope of the present invention. - The present invention has been shown and described with reference to the foregoing exemplary embodiments. It is to be understood, however, that other forms, details and embodiments may be made without departing from the spirit and scope of the invention that is defined in the following claims.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/843,541 US20110022727A1 (en) | 2004-09-08 | 2010-07-26 | Handset cradle |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/936,124 US7764784B2 (en) | 2004-09-08 | 2004-09-08 | Handset cradle |
US12/843,541 US20110022727A1 (en) | 2004-09-08 | 2010-07-26 | Handset cradle |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/936,124 Continuation US7764784B2 (en) | 2004-09-08 | 2004-09-08 | Handset cradle |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110022727A1 true US20110022727A1 (en) | 2011-01-27 |
Family
ID=35996218
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/936,124 Active 2025-12-29 US7764784B2 (en) | 2004-09-08 | 2004-09-08 | Handset cradle |
US12/843,541 Abandoned US20110022727A1 (en) | 2004-09-08 | 2010-07-26 | Handset cradle |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/936,124 Active 2025-12-29 US7764784B2 (en) | 2004-09-08 | 2004-09-08 | Handset cradle |
Country Status (2)
Country | Link |
---|---|
US (2) | US7764784B2 (en) |
WO (1) | WO2006029120A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016039484A (en) * | 2014-08-07 | 2016-03-22 | パナソニックIpマネジメント株式会社 | Repeater and intercom system |
US10135790B2 (en) | 2015-08-25 | 2018-11-20 | Anchorfree Inc. | Secure communications with internet-enabled devices |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9584406B2 (en) | 2004-09-08 | 2017-02-28 | Cradlepoint, Inc. | Data path switching |
US9237102B2 (en) | 2004-09-08 | 2016-01-12 | Cradlepoint, Inc. | Selecting a data path |
US8732808B2 (en) * | 2004-09-08 | 2014-05-20 | Cradlepoint, Inc. | Data plan activation and modification |
US9232461B2 (en) | 2004-09-08 | 2016-01-05 | Cradlepoint, Inc. | Hotspot communication limiter |
US8249052B2 (en) | 2004-09-08 | 2012-08-21 | Cradlepoint, Inc. | Automated access of an enhanced command set |
US7962569B2 (en) * | 2004-09-08 | 2011-06-14 | Cradlepoint, Inc. | Embedded DNS |
US8477639B2 (en) | 2004-09-08 | 2013-07-02 | Cradlepoint, Inc. | Communicating network status |
US7784096B2 (en) * | 2004-11-15 | 2010-08-24 | Microsoft Corporation | Outgoing connection attempt limiting to slow down spreading of viruses |
US8644272B2 (en) | 2007-02-12 | 2014-02-04 | Cradlepoint, Inc. | Initiating router functions |
US9021081B2 (en) | 2007-02-12 | 2015-04-28 | Cradlepoint, Inc. | System and method for collecting individualized network usage data in a personal hotspot wireless network |
KR20130048294A (en) * | 2007-04-13 | 2013-05-09 | 인터디지탈 테크날러지 코포레이션 | Method and apparatus for integrating a soft mobile voip client in a cellular pc card |
US8316236B2 (en) * | 2007-08-31 | 2012-11-20 | Cisco Technology, Inc. | Determining security states using binary output sequences |
WO2009064889A2 (en) | 2007-11-14 | 2009-05-22 | Cradlepoint, Inc. | Configuring a wireless router |
EP2279634B1 (en) * | 2008-05-09 | 2018-03-07 | BlackBerry Limited | Methods and apparatus for prioritizing assignment of a packet data session for a plurality of applications of a mobile communication device |
US7984226B2 (en) * | 2009-06-10 | 2011-07-19 | Hand Held Products, Inc. | Method for sensing and auto switching between two USB input ports to a single port on the PDA |
US8406207B2 (en) | 2010-07-02 | 2013-03-26 | At&T Mobility Ii Llc | Digital surveillance |
US20140049376A1 (en) * | 2010-12-01 | 2014-02-20 | Boon Hwee Burnette Ng | Attachable device support with a communication means |
US8780169B1 (en) | 2011-10-13 | 2014-07-15 | Mylon D. Ridgway | Phone landline and videophone handset allowing simultaneous exchange of video images over an internet network |
KR20130094402A (en) * | 2012-02-16 | 2013-08-26 | 삼성전자주식회사 | Desk top-type universal dock |
CN112751760B (en) * | 2019-10-29 | 2023-03-31 | 中盈优创资讯科技有限公司 | Automatic routing method and system based on two-layer multi-service path |
Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US585628A (en) * | 1897-06-29 | Wall-tie and anchor-iron | ||
US5231633A (en) * | 1990-07-11 | 1993-07-27 | Codex Corporation | Method for prioritizing, selectively discarding, and multiplexing differing traffic type fast packets |
US5594946A (en) * | 1995-02-28 | 1997-01-14 | Motorola, Inc. | Method and apparatus for mitigating interference produced by a communication unit in a communication system |
US5638359A (en) * | 1992-12-14 | 1997-06-10 | Nokia Telecommunications Oy | Method for congestion management in a frame relay network and a node in a frame relay network |
US5864539A (en) * | 1996-05-06 | 1999-01-26 | Bay Networks, Inc. | Method and apparatus for a rate-based congestion control in a shared memory switch |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6006264A (en) * | 1997-08-01 | 1999-12-21 | Arrowpoint Communications, Inc. | Method and system for directing a flow between a client and a server |
US6028848A (en) * | 1997-09-26 | 2000-02-22 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem utilizing internal DNS and DHCP servers for transparent translation of local host names to IP addresses |
US6031844A (en) * | 1996-12-24 | 2000-02-29 | National Science Council | Method of upstream multiple access control in a transmission system |
US20010039580A1 (en) * | 2000-05-03 | 2001-11-08 | Walker Richard C. | Network monitoring system with built-in monitoring data gathering |
US20010042215A1 (en) * | 1998-03-13 | 2001-11-15 | Sullivan James M. | Providing secure access to network services |
US20010046870A1 (en) * | 1999-01-08 | 2001-11-29 | True Position Inc. | Modified transmission method for improving accuracy for E-911 calls |
US20010048683A1 (en) * | 2000-03-10 | 2001-12-06 | Nortel Networks Limited | Transparent QoS using VC-merge capable access modules |
US20020025832A1 (en) * | 2000-02-18 | 2002-02-28 | Durian Michael B. | Controlling data transmission involving a wireless telephone |
US6377825B1 (en) * | 2000-02-18 | 2002-04-23 | Cellport Systems, Inc. | Hands-free wireless communication in a vehicle |
US6389462B1 (en) * | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
US20020062372A1 (en) * | 2000-08-04 | 2002-05-23 | Jack Hong | High performance server farm with tagging and pipelining |
US6434187B1 (en) * | 1997-10-14 | 2002-08-13 | Cypress Semiconductor Corp. | Digital radiofrequency transceiver |
US20020118663A1 (en) * | 2001-02-27 | 2002-08-29 | Motorola, Inc. | Mobile wireless router |
US20030037165A1 (en) * | 2001-07-06 | 2003-02-20 | Daisuke Shinomiya | Dynamic load sharing system using a virtual router |
US20030046396A1 (en) * | 2000-03-03 | 2003-03-06 | Richter Roger K. | Systems and methods for managing resource utilization in information management environments |
US20030045295A1 (en) * | 2000-11-13 | 2003-03-06 | Peter Stanforth | Prioritized-routing for an Ad-Hoc, peer-to-peer, mobile radio access system |
US20030043755A1 (en) * | 2001-09-03 | 2003-03-06 | Agilent Technologies, Inc. | Monitoring communications networks |
US6535592B1 (en) * | 2000-03-23 | 2003-03-18 | Soma Networks, Inc. | Establishing and managing communications over telecommunication networks |
US20030059005A1 (en) * | 2001-09-24 | 2003-03-27 | Teleware, Inc. | Multi-media communication management system with dynamic bypass routing of real time streaming media |
US6553028B1 (en) * | 1999-04-30 | 2003-04-22 | Cisco Technology, Inc. | Method and apparatus for multicast switching using a centralized switching engine |
US6560442B1 (en) * | 1999-08-12 | 2003-05-06 | Ericsson Inc. | System and method for profiling the location of mobile radio traffic in a wireless communications network |
US20030126252A1 (en) * | 2001-09-05 | 2003-07-03 | Eli Abir | Method and apparatus for dynamic client-side load balancing system |
US6609197B1 (en) * | 1999-04-22 | 2003-08-19 | 3Com Corporation | Method and system for secure emergency access to network devices |
US6611861B1 (en) * | 1998-02-27 | 2003-08-26 | Xo Communications, Inc. | Internet hosting and access system and method |
US6615262B2 (en) * | 1999-06-28 | 2003-09-02 | Xacct Technologies, Ltd. | Statistical gathering framework for extracting information from a network multi-layer stack |
US20030200308A1 (en) * | 2002-04-23 | 2003-10-23 | Seer Insight Security K.K. | Method and system for monitoring individual devices in networked environments |
US20030212800A1 (en) * | 2001-12-03 | 2003-11-13 | Jones Bryce A. | Method and system for allowing multiple service providers to serve users via a common access network |
US20030235175A1 (en) * | 2002-06-24 | 2003-12-25 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
US20040003071A1 (en) * | 2002-06-28 | 2004-01-01 | Microsoft Corporation | Parental controls customization and notification |
US20040038697A1 (en) * | 2002-08-23 | 2004-02-26 | Attar Rashid Ahmed | Method and system for a data transmission in a communication system |
US20040049576A1 (en) * | 2000-04-20 | 2004-03-11 | Limor Schweitzer | Method and apparatus for session reconstruction |
US20040068502A1 (en) * | 2002-10-02 | 2004-04-08 | Jerome Vogedes | Context information management in a communication device |
US6735447B1 (en) * | 1999-12-08 | 2004-05-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Transmission power control of a mobile station |
US20040110544A1 (en) * | 2001-04-03 | 2004-06-10 | Masayuki Oyagi | Cradle, security system, telephone, and monitoring method |
US20040133793A1 (en) * | 1995-02-13 | 2004-07-08 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US20040133689A1 (en) * | 2002-12-24 | 2004-07-08 | Samrat Vasisht | Method, system and device for automatically configuring a communications network |
US20040139170A1 (en) * | 2003-01-15 | 2004-07-15 | Ming-Teh Shen | Method and apparatus for management of shared wide area network connections |
US20040153676A1 (en) * | 2003-01-31 | 2004-08-05 | Microsoft Corporation | Method and apparatus for managing power in network interface modules |
US20040152449A1 (en) * | 2002-11-20 | 2004-08-05 | Ntt Docomo, Inc | Mail server, and mobile communication terminal |
US6795700B2 (en) * | 2002-09-12 | 2004-09-21 | Broadcom Corporation | Method of creating incentives for establishing hotspot locations |
US20040185876A1 (en) * | 2003-03-07 | 2004-09-23 | Computer Associates Think, Inc. | Mobility management in wireless networks |
US20040205155A1 (en) * | 2000-01-26 | 2004-10-14 | Viaclix, Inc. | User terminal for channel-based Internet network |
US20040205154A1 (en) * | 2003-03-26 | 2004-10-14 | Lockheed Martin Corporation | System for integrated mobile devices |
US20040218544A1 (en) * | 2003-05-02 | 2004-11-04 | Ray Lee | Router capable of displaying network system |
US20040250136A1 (en) * | 2003-04-18 | 2004-12-09 | Alcatel | Method, a network access system, a network access client device, a network access trading device, and a computer software product for establishing a network connection |
US20050008017A1 (en) * | 2000-12-29 | 2005-01-13 | Ragula Systems D/B/A Fatpipe Networks | Tools and techniques for directing packets over disparate networks |
US20050014525A1 (en) * | 2003-07-17 | 2005-01-20 | Hitachi, Ltd. | Base station and wireless communication system |
US20050022013A1 (en) * | 2001-10-04 | 2005-01-27 | Joerg Schwenk | Method for customized data output on a web site |
US6850495B1 (en) * | 2000-08-31 | 2005-02-01 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
US20050038905A1 (en) * | 2003-08-13 | 2005-02-17 | Banes John A. | Routing hints |
US6862444B2 (en) * | 2002-09-12 | 2005-03-01 | Broadcom Corporation | Billing control methods in wireless hot spots |
US6885859B2 (en) * | 2002-09-12 | 2005-04-26 | Broadcom Corporation | Apparatus for controlling and monitoring a wireless hotspot through an interface with a cellular telephone network |
US20050101340A1 (en) * | 2003-11-10 | 2005-05-12 | Archiable Donald P. | Wireless power control |
US20050108573A1 (en) * | 2003-09-11 | 2005-05-19 | Detica Limited | Real-time network monitoring and security |
US20050198234A1 (en) * | 2004-02-20 | 2005-09-08 | Gteko, Ltd. | System and unified setting interface for configuring network manageable devices |
US20050198319A1 (en) * | 2004-01-15 | 2005-09-08 | Yahoo! Inc. | Techniques for parental control of internet access including a guest mode |
US20050221850A1 (en) * | 2004-03-31 | 2005-10-06 | Kyocera Corporation | Dynamic identifier allotting method and wireless communications system |
US20050233728A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Location-aware application based quality of service (QOS) Via a broadband access gateway |
US20050245233A1 (en) * | 2004-04-28 | 2005-11-03 | Anderson Eric C | Establishing a home relationship between a wireless device and a sever in a wireless network |
US20050246434A1 (en) * | 2004-04-05 | 2005-11-03 | International Business Machines Corporation | Services for capturing and modeling computer usage |
US6967958B2 (en) * | 2000-02-24 | 2005-11-22 | Fujitsu Limited | Communication-status notification apparatus for communication system, communication-status display apparatus, communication-status notification method, medium in which communication-status notification program is recorded and communication apparatus |
US20050259654A1 (en) * | 2004-04-08 | 2005-11-24 | Faulk Robert L Jr | Dynamic access control lists |
US20050259645A1 (en) * | 2004-05-18 | 2005-11-24 | Chen John A | Thwarting denial of service attacks originating in a DOCSIS-compliant cable network |
US20050267965A1 (en) * | 2004-05-13 | 2005-12-01 | Ixi Mobile (R&D) Ltd. | Mobile router graceful shutdown system and method |
US6987726B1 (en) * | 2000-05-22 | 2006-01-17 | Bbnt Solutions Llc | Management of duplicated node identifiers in communication networks |
US20060047823A1 (en) * | 2004-06-22 | 2006-03-02 | Taiwan Semiconductor Manufacturing Company, Ltd. | Method and apparatus for detecting an unauthorized client in a network of computer systems |
US7009941B1 (en) * | 1999-04-08 | 2006-03-07 | Seiko Epson Corporation | Node-search method, device, and medium on which a node-search program is recorded |
US20060053290A1 (en) * | 2000-05-25 | 2006-03-09 | Randle William M | Secure network gateway |
US20060072474A1 (en) * | 2004-10-01 | 2006-04-06 | Kevin Mitchell | Monitoring traffic in a packet switched network |
US20060077607A1 (en) * | 2004-09-10 | 2006-04-13 | Henricks Michael C | Circuit protector monitoring assembly kit and method |
US20060133582A1 (en) * | 2004-12-06 | 2006-06-22 | Mcculloch Edward A | System and method for vital communications connectivity |
US20060153216A1 (en) * | 2004-11-19 | 2006-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Scheduling method for wireless packet data channel |
US20060171402A1 (en) * | 2003-03-06 | 2006-08-03 | Moore John A | Method and system for providing broadband multimedia services |
US20060184670A1 (en) * | 2003-08-29 | 2006-08-17 | Beeson Jesse D | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US7095335B2 (en) * | 2000-11-23 | 2006-08-22 | Koninklijke Philips Electronics N.V. | Arrangement including a remote control device and a first electronic device |
US20060187890A1 (en) * | 2005-01-30 | 2006-08-24 | Frank Lin | LCD display on wireless router |
US20070002846A1 (en) * | 2005-06-30 | 2007-01-04 | Patrick Rada | Peripheral device with visual indicators to show utilization of radio component |
US20070030857A1 (en) * | 2005-08-02 | 2007-02-08 | Fulknier John C | Mobile router device |
US7187923B2 (en) * | 2003-11-20 | 2007-03-06 | Research In Motion Limited | Seamless call switching in a dual mode environment |
US20070083606A1 (en) * | 2001-12-05 | 2007-04-12 | Bellsouth Intellectual Property Corporation | Foreign Network Spam Blocker |
US20070291711A1 (en) * | 2006-06-14 | 2007-12-20 | Ibahn General Holdings Corporation | Techniques for wireless deployment |
US20080005108A1 (en) * | 2006-06-28 | 2008-01-03 | Microsoft Corporation | Message mining to enhance ranking of documents for retrieval |
US20080008165A1 (en) * | 2004-11-04 | 2008-01-10 | Matsushita Electric Industrial Co., Ltd. | Multi-Interface Communication Device, Terminal, And Path Switching Method |
US20080049630A1 (en) * | 2006-08-22 | 2008-02-28 | Kozisek Steven E | System and method for monitoring and optimizing network performance to a wireless device |
US20080159167A1 (en) * | 2006-12-28 | 2008-07-03 | Fujitsu Limited | Monitoring control system, monitoring device, monitoring control method, and monitoring control program |
US7400903B2 (en) * | 2002-04-16 | 2008-07-15 | Texas Instruments Incorporated | Wireless communications system using both licensed and unlicensed frequency bands |
US7421265B1 (en) * | 2005-03-04 | 2008-09-02 | Cisco Technology, Inc. | Selectable network antenna systems and methods |
US20080262248A1 (en) * | 2005-11-10 | 2008-10-23 | Rodenstock Gmbh | Photochromic Spirodihydrophenanthropyrans |
US20090129319A1 (en) * | 2002-10-21 | 2009-05-21 | Buddhikot Milind M | Integrated web cache |
US20090138447A1 (en) * | 2007-11-27 | 2009-05-28 | Umber Systems | Method and apparatus for real-time collection of information about application level activity and other user information on a mobile data network |
US20090175285A1 (en) * | 2004-09-08 | 2009-07-09 | Steven Wood | Selecting a data path |
US20090180395A1 (en) * | 2004-09-08 | 2009-07-16 | Steven Wood | Communicating network status |
US7620065B2 (en) * | 2005-07-22 | 2009-11-17 | Trellia Networks, Inc. | Mobile connectivity solution |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995019030A1 (en) * | 1994-01-05 | 1995-07-13 | Pois, Inc. | Apparatus and method for a personal onboard information system |
JP3350012B2 (en) | 1999-12-24 | 2002-11-25 | 埼玉日本電気株式会社 | Mobile terminal authentication method |
AU2002216279A1 (en) * | 2000-12-27 | 2002-07-08 | Cellglide Technologies Corp. | Resource allocation in cellular telephone networks |
KR100819678B1 (en) | 2002-09-28 | 2008-04-04 | 주식회사 케이티 | Authentification Method of Public Wireless LAN Service using CDMA authentification information |
US7327682B2 (en) * | 2003-06-27 | 2008-02-05 | Cisco Technology, Inc. | Methods and devices for flexible bandwidth allocation |
US7523193B2 (en) | 2004-05-18 | 2009-04-21 | International Business Machines Corporation | Method and apparatus for DNS pre-fetching for multiple clients |
-
2004
- 2004-09-08 US US10/936,124 patent/US7764784B2/en active Active
-
2005
- 2005-09-07 WO PCT/US2005/031632 patent/WO2006029120A2/en active Application Filing
-
2010
- 2010-07-26 US US12/843,541 patent/US20110022727A1/en not_active Abandoned
Patent Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US585628A (en) * | 1897-06-29 | Wall-tie and anchor-iron | ||
US5231633A (en) * | 1990-07-11 | 1993-07-27 | Codex Corporation | Method for prioritizing, selectively discarding, and multiplexing differing traffic type fast packets |
US5638359A (en) * | 1992-12-14 | 1997-06-10 | Nokia Telecommunications Oy | Method for congestion management in a frame relay network and a node in a frame relay network |
US20040133793A1 (en) * | 1995-02-13 | 2004-07-08 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5594946A (en) * | 1995-02-28 | 1997-01-14 | Motorola, Inc. | Method and apparatus for mitigating interference produced by a communication unit in a communication system |
US5864539A (en) * | 1996-05-06 | 1999-01-26 | Bay Networks, Inc. | Method and apparatus for a rate-based congestion control in a shared memory switch |
US6006034A (en) * | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
US6031844A (en) * | 1996-12-24 | 2000-02-29 | National Science Council | Method of upstream multiple access control in a transmission system |
US6006264A (en) * | 1997-08-01 | 1999-12-21 | Arrowpoint Communications, Inc. | Method and system for directing a flow between a client and a server |
US6028848A (en) * | 1997-09-26 | 2000-02-22 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem utilizing internal DNS and DHCP servers for transparent translation of local host names to IP addresses |
US6434187B1 (en) * | 1997-10-14 | 2002-08-13 | Cypress Semiconductor Corp. | Digital radiofrequency transceiver |
US6611861B1 (en) * | 1998-02-27 | 2003-08-26 | Xo Communications, Inc. | Internet hosting and access system and method |
US20010042215A1 (en) * | 1998-03-13 | 2001-11-15 | Sullivan James M. | Providing secure access to network services |
US6389462B1 (en) * | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
US20010046870A1 (en) * | 1999-01-08 | 2001-11-29 | True Position Inc. | Modified transmission method for improving accuracy for E-911 calls |
US7009941B1 (en) * | 1999-04-08 | 2006-03-07 | Seiko Epson Corporation | Node-search method, device, and medium on which a node-search program is recorded |
US6609197B1 (en) * | 1999-04-22 | 2003-08-19 | 3Com Corporation | Method and system for secure emergency access to network devices |
US6553028B1 (en) * | 1999-04-30 | 2003-04-22 | Cisco Technology, Inc. | Method and apparatus for multicast switching using a centralized switching engine |
US6615262B2 (en) * | 1999-06-28 | 2003-09-02 | Xacct Technologies, Ltd. | Statistical gathering framework for extracting information from a network multi-layer stack |
US6560442B1 (en) * | 1999-08-12 | 2003-05-06 | Ericsson Inc. | System and method for profiling the location of mobile radio traffic in a wireless communications network |
US6735447B1 (en) * | 1999-12-08 | 2004-05-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Transmission power control of a mobile station |
US20040205155A1 (en) * | 2000-01-26 | 2004-10-14 | Viaclix, Inc. | User terminal for channel-based Internet network |
US6377825B1 (en) * | 2000-02-18 | 2002-04-23 | Cellport Systems, Inc. | Hands-free wireless communication in a vehicle |
US20020025832A1 (en) * | 2000-02-18 | 2002-02-28 | Durian Michael B. | Controlling data transmission involving a wireless telephone |
US6967958B2 (en) * | 2000-02-24 | 2005-11-22 | Fujitsu Limited | Communication-status notification apparatus for communication system, communication-status display apparatus, communication-status notification method, medium in which communication-status notification program is recorded and communication apparatus |
US20030046396A1 (en) * | 2000-03-03 | 2003-03-06 | Richter Roger K. | Systems and methods for managing resource utilization in information management environments |
US20010048683A1 (en) * | 2000-03-10 | 2001-12-06 | Nortel Networks Limited | Transparent QoS using VC-merge capable access modules |
US6535592B1 (en) * | 2000-03-23 | 2003-03-18 | Soma Networks, Inc. | Establishing and managing communications over telecommunication networks |
US20040049576A1 (en) * | 2000-04-20 | 2004-03-11 | Limor Schweitzer | Method and apparatus for session reconstruction |
US20010039580A1 (en) * | 2000-05-03 | 2001-11-08 | Walker Richard C. | Network monitoring system with built-in monitoring data gathering |
US6987726B1 (en) * | 2000-05-22 | 2006-01-17 | Bbnt Solutions Llc | Management of duplicated node identifiers in communication networks |
US20060053290A1 (en) * | 2000-05-25 | 2006-03-09 | Randle William M | Secure network gateway |
US20020062372A1 (en) * | 2000-08-04 | 2002-05-23 | Jack Hong | High performance server farm with tagging and pipelining |
US6850495B1 (en) * | 2000-08-31 | 2005-02-01 | Verizon Communications Inc. | Methods, apparatus and data structures for segmenting customers using at least a portion of a layer 2 address header or bits in the place of a layer 2 address header |
US20030045295A1 (en) * | 2000-11-13 | 2003-03-06 | Peter Stanforth | Prioritized-routing for an Ad-Hoc, peer-to-peer, mobile radio access system |
US7095335B2 (en) * | 2000-11-23 | 2006-08-22 | Koninklijke Philips Electronics N.V. | Arrangement including a remote control device and a first electronic device |
US20050008017A1 (en) * | 2000-12-29 | 2005-01-13 | Ragula Systems D/B/A Fatpipe Networks | Tools and techniques for directing packets over disparate networks |
US20020118663A1 (en) * | 2001-02-27 | 2002-08-29 | Motorola, Inc. | Mobile wireless router |
US20040110544A1 (en) * | 2001-04-03 | 2004-06-10 | Masayuki Oyagi | Cradle, security system, telephone, and monitoring method |
US20030037165A1 (en) * | 2001-07-06 | 2003-02-20 | Daisuke Shinomiya | Dynamic load sharing system using a virtual router |
US20030043755A1 (en) * | 2001-09-03 | 2003-03-06 | Agilent Technologies, Inc. | Monitoring communications networks |
US20030126252A1 (en) * | 2001-09-05 | 2003-07-03 | Eli Abir | Method and apparatus for dynamic client-side load balancing system |
US20030059005A1 (en) * | 2001-09-24 | 2003-03-27 | Teleware, Inc. | Multi-media communication management system with dynamic bypass routing of real time streaming media |
US20050022013A1 (en) * | 2001-10-04 | 2005-01-27 | Joerg Schwenk | Method for customized data output on a web site |
US20030212800A1 (en) * | 2001-12-03 | 2003-11-13 | Jones Bryce A. | Method and system for allowing multiple service providers to serve users via a common access network |
US20070083606A1 (en) * | 2001-12-05 | 2007-04-12 | Bellsouth Intellectual Property Corporation | Foreign Network Spam Blocker |
US7400903B2 (en) * | 2002-04-16 | 2008-07-15 | Texas Instruments Incorporated | Wireless communications system using both licensed and unlicensed frequency bands |
US20030200308A1 (en) * | 2002-04-23 | 2003-10-23 | Seer Insight Security K.K. | Method and system for monitoring individual devices in networked environments |
US20030235175A1 (en) * | 2002-06-24 | 2003-12-25 | Nokia Corporation | Mobile mesh Ad-Hoc networking |
US20040003071A1 (en) * | 2002-06-28 | 2004-01-01 | Microsoft Corporation | Parental controls customization and notification |
US20040038697A1 (en) * | 2002-08-23 | 2004-02-26 | Attar Rashid Ahmed | Method and system for a data transmission in a communication system |
US6862444B2 (en) * | 2002-09-12 | 2005-03-01 | Broadcom Corporation | Billing control methods in wireless hot spots |
US6885859B2 (en) * | 2002-09-12 | 2005-04-26 | Broadcom Corporation | Apparatus for controlling and monitoring a wireless hotspot through an interface with a cellular telephone network |
US6795700B2 (en) * | 2002-09-12 | 2004-09-21 | Broadcom Corporation | Method of creating incentives for establishing hotspot locations |
US20040068502A1 (en) * | 2002-10-02 | 2004-04-08 | Jerome Vogedes | Context information management in a communication device |
US20090129319A1 (en) * | 2002-10-21 | 2009-05-21 | Buddhikot Milind M | Integrated web cache |
US20040152449A1 (en) * | 2002-11-20 | 2004-08-05 | Ntt Docomo, Inc | Mail server, and mobile communication terminal |
US20040133689A1 (en) * | 2002-12-24 | 2004-07-08 | Samrat Vasisht | Method, system and device for automatically configuring a communications network |
US20040139170A1 (en) * | 2003-01-15 | 2004-07-15 | Ming-Teh Shen | Method and apparatus for management of shared wide area network connections |
US20040153676A1 (en) * | 2003-01-31 | 2004-08-05 | Microsoft Corporation | Method and apparatus for managing power in network interface modules |
US20060171402A1 (en) * | 2003-03-06 | 2006-08-03 | Moore John A | Method and system for providing broadband multimedia services |
US20040185876A1 (en) * | 2003-03-07 | 2004-09-23 | Computer Associates Think, Inc. | Mobility management in wireless networks |
US20040205154A1 (en) * | 2003-03-26 | 2004-10-14 | Lockheed Martin Corporation | System for integrated mobile devices |
US20040250136A1 (en) * | 2003-04-18 | 2004-12-09 | Alcatel | Method, a network access system, a network access client device, a network access trading device, and a computer software product for establishing a network connection |
US20040218544A1 (en) * | 2003-05-02 | 2004-11-04 | Ray Lee | Router capable of displaying network system |
US20050014525A1 (en) * | 2003-07-17 | 2005-01-20 | Hitachi, Ltd. | Base station and wireless communication system |
US20050038905A1 (en) * | 2003-08-13 | 2005-02-17 | Banes John A. | Routing hints |
US20060184670A1 (en) * | 2003-08-29 | 2006-08-17 | Beeson Jesse D | System and method for analyzing the performance of multiple transportation streams of streaming media in packet-based networks |
US20050108573A1 (en) * | 2003-09-11 | 2005-05-19 | Detica Limited | Real-time network monitoring and security |
US20050101340A1 (en) * | 2003-11-10 | 2005-05-12 | Archiable Donald P. | Wireless power control |
US7187923B2 (en) * | 2003-11-20 | 2007-03-06 | Research In Motion Limited | Seamless call switching in a dual mode environment |
US20050198319A1 (en) * | 2004-01-15 | 2005-09-08 | Yahoo! Inc. | Techniques for parental control of internet access including a guest mode |
US20050198234A1 (en) * | 2004-02-20 | 2005-09-08 | Gteko, Ltd. | System and unified setting interface for configuring network manageable devices |
US20050221850A1 (en) * | 2004-03-31 | 2005-10-06 | Kyocera Corporation | Dynamic identifier allotting method and wireless communications system |
US20050246434A1 (en) * | 2004-04-05 | 2005-11-03 | International Business Machines Corporation | Services for capturing and modeling computer usage |
US20050259654A1 (en) * | 2004-04-08 | 2005-11-24 | Faulk Robert L Jr | Dynamic access control lists |
US20050233728A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Location-aware application based quality of service (QOS) Via a broadband access gateway |
US20050245233A1 (en) * | 2004-04-28 | 2005-11-03 | Anderson Eric C | Establishing a home relationship between a wireless device and a sever in a wireless network |
US20050267965A1 (en) * | 2004-05-13 | 2005-12-01 | Ixi Mobile (R&D) Ltd. | Mobile router graceful shutdown system and method |
US20050259645A1 (en) * | 2004-05-18 | 2005-11-24 | Chen John A | Thwarting denial of service attacks originating in a DOCSIS-compliant cable network |
US20060047823A1 (en) * | 2004-06-22 | 2006-03-02 | Taiwan Semiconductor Manufacturing Company, Ltd. | Method and apparatus for detecting an unauthorized client in a network of computer systems |
US20090180395A1 (en) * | 2004-09-08 | 2009-07-16 | Steven Wood | Communicating network status |
US20090175285A1 (en) * | 2004-09-08 | 2009-07-09 | Steven Wood | Selecting a data path |
US20060077607A1 (en) * | 2004-09-10 | 2006-04-13 | Henricks Michael C | Circuit protector monitoring assembly kit and method |
US20060072474A1 (en) * | 2004-10-01 | 2006-04-06 | Kevin Mitchell | Monitoring traffic in a packet switched network |
US20080008165A1 (en) * | 2004-11-04 | 2008-01-10 | Matsushita Electric Industrial Co., Ltd. | Multi-Interface Communication Device, Terminal, And Path Switching Method |
US20060153216A1 (en) * | 2004-11-19 | 2006-07-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Scheduling method for wireless packet data channel |
US20060133582A1 (en) * | 2004-12-06 | 2006-06-22 | Mcculloch Edward A | System and method for vital communications connectivity |
US20060187890A1 (en) * | 2005-01-30 | 2006-08-24 | Frank Lin | LCD display on wireless router |
US7421265B1 (en) * | 2005-03-04 | 2008-09-02 | Cisco Technology, Inc. | Selectable network antenna systems and methods |
US20070002846A1 (en) * | 2005-06-30 | 2007-01-04 | Patrick Rada | Peripheral device with visual indicators to show utilization of radio component |
US7620065B2 (en) * | 2005-07-22 | 2009-11-17 | Trellia Networks, Inc. | Mobile connectivity solution |
US20070030857A1 (en) * | 2005-08-02 | 2007-02-08 | Fulknier John C | Mobile router device |
US20080262248A1 (en) * | 2005-11-10 | 2008-10-23 | Rodenstock Gmbh | Photochromic Spirodihydrophenanthropyrans |
US20070291711A1 (en) * | 2006-06-14 | 2007-12-20 | Ibahn General Holdings Corporation | Techniques for wireless deployment |
US20080005108A1 (en) * | 2006-06-28 | 2008-01-03 | Microsoft Corporation | Message mining to enhance ranking of documents for retrieval |
US20080049630A1 (en) * | 2006-08-22 | 2008-02-28 | Kozisek Steven E | System and method for monitoring and optimizing network performance to a wireless device |
US20080159167A1 (en) * | 2006-12-28 | 2008-07-03 | Fujitsu Limited | Monitoring control system, monitoring device, monitoring control method, and monitoring control program |
US20090138447A1 (en) * | 2007-11-27 | 2009-05-28 | Umber Systems | Method and apparatus for real-time collection of information about application level activity and other user information on a mobile data network |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016039484A (en) * | 2014-08-07 | 2016-03-22 | パナソニックIpマネジメント株式会社 | Repeater and intercom system |
US10135790B2 (en) | 2015-08-25 | 2018-11-20 | Anchorfree Inc. | Secure communications with internet-enabled devices |
US10135791B2 (en) | 2015-08-25 | 2018-11-20 | Anchorfree Inc. | Secure communications with internet-enabled devices |
US10135792B2 (en) | 2015-08-25 | 2018-11-20 | Anchorfree Inc. | Secure communications with internet-enabled devices |
Also Published As
Publication number | Publication date |
---|---|
WO2006029120A2 (en) | 2006-03-16 |
US7764784B2 (en) | 2010-07-27 |
US20060050866A1 (en) | 2006-03-09 |
WO2006029120A3 (en) | 2006-11-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20110022727A1 (en) | Handset cradle | |
US10599869B2 (en) | Separate privacy setting control for multiple application instances of a user | |
US9986591B2 (en) | Function execution apparatus | |
JP4404773B2 (en) | Method and apparatus for managing the use of data link resources | |
US20060015636A1 (en) | Method for selecting among network interfaces, device with multiple network interfaces and application | |
US9369940B2 (en) | Mobile handheld multi-media gateway and phone | |
US20180091581A1 (en) | Method of switching download mode, control method thereof and control system thereof | |
KR102138103B1 (en) | Method of application connection for devices in a network | |
JP2006254301A (en) | Ip address setting system | |
JP2007251450A (en) | Adhoc network, terminal equipment, and adhoc network setting method used therefor | |
EP2883367B1 (en) | Video call service | |
US20060093119A1 (en) | Leveraging real-time communications client | |
CN105451368B (en) | Communication method and device | |
CN104871481A (en) | Method and apparatus for cloud based power management of local network devices | |
US9203935B2 (en) | Communication apparatus, communication systems, methods, and non-transitory computer-readable media for processing data according to different protocols in response to packets received using different interface standards | |
CN108781217B (en) | Multimedia data transmission method, server and terminal | |
US20180213027A1 (en) | Receiving a communication event | |
US8160059B2 (en) | Wireless networking communication system and communicating method for VOIP | |
EP3101576A1 (en) | Access control device, communication system, program, and access control method | |
CN103283185A (en) | Prioritization of data communication | |
JP5477090B2 (en) | Terminal state control apparatus, terminal state control program, terminal state control method, and terminal state control system | |
CN110139210B (en) | Application connectivity for devices in a network | |
JP2007281684A (en) | Gateway device, information sharing system, and method | |
KR20020089644A (en) | Status information common possession method for internet phone system | |
KR101131232B1 (en) | Apparatus and method for prohibiting uploading data in mobile terminal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CRADLEPOINT, INC., IDAHO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SEWALL, PATRICK;SEWALL, LLC;REEL/FRAME:024740/0963 Effective date: 20070423 |
|
AS | Assignment |
Owner name: SILICON VALLEY BANK, CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:CRADLEPOINT, INC.;REEL/FRAME:026565/0764 Effective date: 20091002 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: CRADLEPOINT, INC., IDAHO Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:034276/0671 Effective date: 20141021 |