US20110122774A1 - Time or Condition-Based Reestablishment of a Secure Connection - Google Patents
Time or Condition-Based Reestablishment of a Secure Connection Download PDFInfo
- Publication number
- US20110122774A1 US20110122774A1 US12/692,551 US69255110A US2011122774A1 US 20110122774 A1 US20110122774 A1 US 20110122774A1 US 69255110 A US69255110 A US 69255110A US 2011122774 A1 US2011122774 A1 US 2011122774A1
- Authority
- US
- United States
- Prior art keywords
- network
- home router
- home
- remote server
- attempting
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/283—Processing of data at an internetworking point of a home automation network
- H04L12/2834—Switching of information between an external network and a home network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1073—Registration or de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
Definitions
- VPNs Virtual Private Networks
- IPSec Internet Protocol Security
- FIGS. 3 a and 3 b illustrate interaction diagrams of the secured registration of a home network device with the service provider network, in accordance with various embodiments.
- FIG. 10 illustrates a component level view of a server of the service provider network, in accordance with various embodiments.
- the home router 102 serves as a gateway to the service provider network 106 for other devices 114 of the home network 104 .
- the home router 102 is configured to establish the network tunnel 108 with a device of the service provider network 106 to secure communications between the home network 104 and service provider network 106 and to reestablish the network tunnel 108 when secure communication fails.
- the home router 102 is configured to receive remote management 110 from the service provider network 106 , to enable remote management 110 of a device 114 of the home network 104 , and to act as a registrar for devices 114 of the home network 104 , providing registration requests to the service provider network 106 on behalf of devices 114 of the home network 104 .
- the devices 114 are also configured to establish a secure connection via a network tunnel 108 with the service provider network 106 when the devices 114 are outside of the home network 104 and to reestablish the secured connection when the secured connection fails.
- the home network 104 includes other devices besides those shown. Such other devices could include at least one of a workstation, a server system, a television, a media player, a digital video recorder, a game device, a set-top box, or a camera.
- An example device 114 is illustrated in greater detail in FIG. 9 and is described in detail below with reference to that figure.
- the IMS network may include one or both of the RMS 118 or the SMSC 120 .
- the RMS 118 and SMSC 120 belong to the service provider network 106 but do not form a part of the IMS network of the service provider network 106 .
- the RMS 118 is configured to remotely manage 110 the home router 102 and/or other devices of the home network 104 and may include a proxy VPN server to establish the network tunnel 108 .
- the RMS 118 also provides a graphic user interface (GUI) to an administrative user of the service provider network 106 or communicates with another server device to enable that device to provide a GUI.
- GUI graphic user interface
- either the RMS 118 or the other server device may provide a web GUI accessible by a user of the home network 104 to, for example, request service or some other type of remote management 110 .
- the RMS 118 may also be configured to trigger the SMSC 120 to send an SMS to the home router 102 to cause the home router 102 to initiate a secure connection with the service provider network 106 .
- the SMSC 120 is complementarily configured to receive a command from the RMS 118 to send an SMS to the home router 102 and to send, in response to that command, an SMS to the home router 102 .
- the network tunnels 108 shown in FIG. 1 between the SBC 116 and the home router 102 and between the SBC 116 and the tablet computer 114 d represent secure communication channels, such as those associated with VPNs. While the device 114 of the home network 104 having its own network tunnel 108 with the service provider network 106 is shown as the tablet computer 114 d , any of the devices 114 of home network 104 can establish a network tunnel 108 when traveling away from a geographic location associated with the home network 104 .
- FIGS. 2 , 3 a , 3 b , and 6 are described in greater detail below with reference to those figures.
- the networking fabric 126 represents any one or more networks known in the art, such as cellular networks and/or data networks, including wide area networks (WANs), LANs, PANs, and/or the Internet.
- a connection between the home network 104 and the service provider network 106 may be through a number of routers, base stations, and/or devices acting as bridges between cellular and data networks.
- Communications between the home network 104 and the service provider network 106 utilize any sort of communication protocol known in the art for sending and receiving messages, such as TCP/IP and/or HTTP.
- network fabric 126 also includes an Internet service provider (ISP) providing Internet connectivity to the home network 104 .
- ISP Internet service provider
- the registration 112 shown in FIG. 1 comprises the registration of one or more of the devices 114 and/or the home router 102 with the service provider network 106 .
- the registration 112 includes providing a pre-provisioned public identifier and receiving a public identifier useable in communications in response.
- the home router 102 may act as a registrar for other devices 114 , and the devices 114 may either register themselves or register through the home router 102 depending on whether they are located within the home network 104 .
- the details of the registration 112 process are illustrated in FIGS. 3 a and 3 b and are described below in greater detail with reference to those figures.
- an endpoint of one of the network tunnels 108 is configured to attempt, in response to determining that the network tunnel 108 has failed, to reestablish the network tunnel 108 .
- the reestablishing of a network tunnel 108 is illustrated in FIG. 6 and is described below in greater detail with reference to that figure.
- the remote management 110 is responsive to status reports or schemas provided 202 by the home router 102 to, for example, the RMS 118 .
- the home router 102 provides 202 the status report or schema to the RMS 118 through the SBC 116 , which provides the home router 102 with connectivity to the service provider network 106 .
- the status report includes performance metrics associated with the home router 102 , with devices 114 , and with other aspects of the home network 104 .
- the schema includes information associated with configurations and versions of various modules and processes of the home router 102 and devices 114 .
- the status reports and schemas may be created on a pre-determined basis, such as every n time units by module(s) of the home router 102 and/or devices 114 .
- the module(s) of the home router 102 and/or devices 114 can create the status reports or schemas in response to the occurrence of an event, such as a configuration change or performance exceeding a threshold.
- the RMS 118 instructs the SMSC 120 to send 204 a an SMS to the home router 102 to trigger the home router 102 to request a secure connection, such as a VPN.
- the RMS 118 may instruct the SMSC 120 in response to a status report or schema, as discussed above, or in response to an entry or selection made by an administrative user of the service provider network 106 .
- a user of a home network 104 may call the service provider of the service provider network 106 to complain about a problem with the home router 102 or a device 114 , such as slow performance, or in regards to setting up the home router 102 or a device 114 .
- the RMS 118 is notified of the establishment 208 of the network tunnel 108 by either the SBC 116 or the home router 102 . Or, in other embodiments, the RMS 118 discovers by monitoring that a network tunnel 108 has been established 208 .
- the RMS 118 remotely manages 212 the home router 102 by transmitting the updated software module to the home router 102 , installing the updated software module, and verifying that the home router 102 functions properly with the updated software module installed.
- the RMS 118 also remotely manages 214 a device 114 by transmitting the updated software module to the device 114 , installing the updated software module, and verifying that the device 114 functions properly with the updated software module installed.
- the RMS 118 upon completion of remote management 110 , sends 218 a command to terminate the network tunnel 108 .
- the request is sent to the home router 102 through the SBC 116 and network tunnel 108 .
- the command may be manually initiated by the service provider or automatically initiated in response to an event, such as the occurrence of a pre-determined idle time.
- the home router Upon receiving the command to terminate the network tunnel 108 , the home router terminates 220 the network tunnel 108 . In other embodiments, the home router 102 terminates the network tunnel 108 without receiving any sort of command to do so. For example, the home router 102 may also monitor for events such as the occurrence of a pre-determined idle time and, in response to detecting the occurrence of the event, may terminate 220 the network tunnel 108 .
- FIGS. 3 a and 3 b illustrate interaction diagrams of the secured registration of a home network device with the service provider network, in accordance with various embodiments.
- FIG. 3 a includes representations of the home router 102 , a device 114 , the SBC 116 , the CSCF 122 , and the HSS 124 , each representation including a graphic depiction and a vertical line descending across the figure.
- FIG. 3 b includes representations of a device 114 , the SBC 116 , the CSCF 122 , and the HSS 124 , each representation including a graphic depiction and a vertical line descending across the figure.
- Each horizontal line represents a single interaction or a group of interactions.
- one of the horizontal lines crosses a vertical line, terminates at an arrow, and then resumes, this indicates that the system associated with the crossed line is involved in the interaction.
- a device 114 of a home network 104 registers 112 itself with the service provider network 106 through a series of interactions illustrated in FIGS. 3 a - 3 b .
- the device 114 registers 112 itself the first time that the device 114 is used.
- the device 114 may also register itself on subsequent occasions, such as when initiating a communication such as a phone call or electronic message.
- the device 114 initiates the registering 112 automatically, without any interaction with a device user.
- the user must take some action, such as pushing a button or entering a key sequence, to cause the device 114 to register 112 itself.
- the network registration request comprises a registration set containing at least one of a globally unique private device identifier and a pre-provisioned public identifier.
- the private identifier and/or pre-provisioned public identifier are stored in memory of the device 114 .
- the private identifier and/or pre-provisioned public identifier is obtained from another device, such as home router 102 .
- Either of the private identifier or the pre-provisioned public identifier may be one of a telephone number, an IP address, or a messaging identifier.
- the device 114 utilizes a wireless interface, such as a Wi-Fi, Bluetooth, Wi-Max, or DECT interface to contact and connect to the home router 102 .
- FIG. 3 a illustrates further interactions in response to the device 114 determining 304 that the device 114 is connected to the home router 102 .
- FIG. 3 b illustrates further interaction in response to the device 114 determining that the device 114 is not connected to the home router 102 .
- the network tunnel 108 is established when the home router 102 is powered on or at some other time previous to receipt of the network registration request. In such embodiments, the network tunnel 108 is maintained while the home router 102 is powered on so that a secure connection for transmission of voice and data communications is available and does not have to be established anew each time a new communication is received.
- the device 114 determines 304 that the home router 102 is unreachable when the device 114 is away from a geographic location associated with the home network 104 . Upon determining formulating 302 the network registration request and determining 304 that the device 114 is not connected to (or connectable to) the home router 102 , the device 114 proceeds to establish a network tunnel 108 by sending a VPN request to the SBC 116 . In such embodiments, the VPN request is transmitted over the networking fabric 126 or some other networking fabric.
- the device 114 may be a cellular device and the networking fabric 126 may include a cellular network capable of transmitting the VPN request to the SBC 116 .
- the UA leg 404 are coupled to interfaces 408 , such as remote access, DECT, and PSTN interfaces capable of receiving signals and transforming those signals into a form readable by the UA legs 404 . While not shown, other interfaces 408 known in the art may be utilized as well.
- the UA leg 406 provides IMS-compliant SIP communications to the service provider network 106 , such as IMS-compliant SIP network registration requests on behalf of the devices 114 and receives SIP responses, such as the above mentioned network registration responses.
- the UA legs 404 and 406 can act as UA clients/servers.
- the internetworking block includes an SIP registrar 410 and a security and identity module 412 .
- the SIP registrar 410 stores the network registration requests for later transmission if the service provider network 106 is unavailable, thereby acting as a proxy registrar of the devices 114 for the service provider network 106 .
- the security and identity module 412 is used by the UA client 406 to authenticate the home router 102 to the IMS network of the service provider.
- the attempting 608 also or instead includes utilizing 616 a binary exponential back-off (BEB) algorithm in timing repeated attempts 608 to reestablish the secure connection.
- the home router 102 utilizes 616 the BEB algorithm to schedule a further attempt 608 when an attempt 608 fails.
- the BEB algorithm schedules a first retry after a certain wait (e.g., 10 seconds) and, if that retry also fails, schedules a further retry after double the wait (e.g., 20 seconds).
- the BEB algorithm iteratively doubles the wait with each attempt until a max wait is reached (e.g., 24 hours). If a retry after the max wait also fails, the home router 102 ceases to attempt 608 to reestablish the secure connection.
- FIG. 7 illustrates a flowchart showing a method of determining 602 whether a secured connection has failed, in accordance with various embodiments.
- one or more modules of the home router 102 monitor at least one of network connectivity, network congestion, or server reachability.
- the modules operate continuously while the secure connection is utilized.
- the monitoring can include ascertaining network connectivity, congestion, and server reachability in a sequential fashion.
- the modules first determine 702 whether a network outage has occurred. Determining 702 whether a network outage has occurred involves at least one of checking a status of a physical link, checking whether an IP address is a valid IP address, or performing a name server lookup.
- FIG. 8 illustrates a component level view of an example home router 102 , in accordance with various embodiments.
- the home router 102 includes a memory 802 , the memory storing a reporting module 804 , a VPN client 806 , a remote management client 808 , a menu module 810 , an SMS client 812 , a registration module 814 , an internetworking block 816 , a retry module 818 , a network status monitor 820 , and other modules and data 822 .
- the reporting module 804 is configured to gather performance metrics and create schemas and to provide those performance metrics and schemas as reports to the service provider network 106 .
- Techniques for generating and providing reports by the home router 102 are shown in FIG. 2 and described above in detail with reference to that figure.
- the registration module 814 is configured to enable registration 112 of a device 114 that is locally connected or coupled to the home router 102 with the service provider network 106 . Techniques for registering 112 a device 114 by the home router 102 are shown in FIG. 3 a and are described above in greater detail.
- the internetworking block 816 shown in FIG. 8 is a component level view of the internetworking block 400 , which is shown in FIG. 4 and described above in detail with reference to that figure.
- FIG. 9 illustrates a component level view of an example device 114 of the home network 104 , in accordance with various embodiments.
- the device 114 may include a memory 902 , the memory storing a VPN client 904 , a remote management client 906 , a registration module 908 , an SMS client 910 , a SIP client 912 , a retry module 914 , a connectivity monitor 916 , and other modules and data 918 .
- the device 114 further includes processor(s) 920 , interfaces 922 , a display 924 , transceivers 926 , output devices 928 , input devices 930 , and drive unit 932 including a machine readable medium 934 .
- the registration module 908 is configured to formulate a network registration request and receive a network registration response, the response including a public identifier that is useable by the device 114 in voice and data communication. Techniques for registering 112 the device 112 , which are shown in FIGS. 3 a - 3 b , are described above in greater detail.
- the other modules and data 918 are modules for enabling voice and data communications to and from the device 114 as well as other modules for any other number of device functions for telecommunications, media, and computing devices known in the art.
- the near field interface can include a Bluetooth® interface or RFID for transmitting and receiving near field radio communications via a near field antenna.
- the near field interface may be used for functions, as is known in the art, such as communicating directly with nearby devices that are also, for instance, Bluetooth® or RFID enabled.
- a reader/interrogator may be incorporated into device 114 .
- the display 924 is a liquid crystal display or any other type of display commonly used in telecommunication devices.
- display 924 may be a touch-sensitive display screen, and can then also act as an input device or keypad, such as for providing a soft-key keyboard, navigation buttons, or the like.
- the transceivers 926 include any sort of transceivers known in the art.
- transceivers 926 may include a radio transceiver and interface that performs the function of transmitting and receiving radio frequency communications via an antenna.
- the radio interface facilitates wireless connectivity between the device 114 and various cell towers, base stations and/or access points.
- the VPN server 1004 is configured to establish a network tunnel 108 with another device, such as the home router 102 .
- Techniques for establishing and reestablishing the network tunnel 108 which are shown in FIGS. 2 , 3 a - 3 b , and 6 , are described above in greater detail. Such techniques are performed by a VPN server 1004 .
- the VPN server 1004 instead is a component of another device, such as a component of the SBC 116 .
- the processor(s) 1012 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or other processing unit or component known in the art.
- CPU central processing unit
- GPU graphics processing unit
- the processor(s) 1012 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or other processing unit or component known in the art.
- RMS 118 also contains communication connections 1022 that allow the RMS 118 to communicate with other computing devices 1022 , such as other servers of the service provider network 106 , including the SBC 116 , the SMSC 120 , the CSCF 122 , and the HSS 124 .
- other computing devices 1022 such as other servers of the service provider network 106 , including the SBC 116 , the SMSC 120 , the CSCF 122 , and the HSS 124 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
- User Interface Of Digital Computer (AREA)
- Telephone Function (AREA)
Abstract
Description
- This application claims priority to U.S. Provisional Application No. 61/264,627, entitled “Connected Home” and filed on Nov. 25, 2009. Application No. 61/264,627 is fully incorporated herein by this reference.
- Increasingly, a variety of networks for a variety of modes of communication are being consolidated into a single network for those modes. Previously, phone calls have been transmitted over circuit-switched networks, while electronic messages have been transmitted over data networks, such as the Internet. Multiple devices that reside in the same home have used such disparate networks and thus have not been in communication with one another. To enable this variety of communication modes to share a common network, a number of communication service provider have adopted Session Initiation Protocol (SIP) to initiate or terminate Internet Protocol (IP) services. Some service providers have deployed Internet Protocol Multimedia Subsystem (IMS), an architectural framework for delivering Internet Protocol (IP) multimedia services using SIP as a major protocol, within their IP networks. SIP enabled phone (or IMS enabled phone) calls, electronic messages, and other voice and data communications to be transmitted together over a common data network. An alternative is to rely on the Extensible Messaging and Presence Protocol (XMPP) for these services.
- This consolidation of communication modes raises concerns about security. Communications such as phone calls have not previously been exposed to the security weaknesses of data networks. A number of security mechanisms are used for securing communications across data networks, however. Virtual Private Networks (VPNs), for example, have been use to create a secure connection between two devices located remotely from one another and connected via a public data network. These VPNs include network tunnels associated with data packets that have been encrypted using the Internet Protocol Security (IPSec) protocol suite.
- The detailed description is set forth with reference to the accompanying figures, in which the left-most digit of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.
-
FIG. 1 illustrates an overview of secured communications between devices of home and service provider networks, in accordance with various embodiments. -
FIG. 2 illustrates an interaction diagram of the remote management of home network devices, in accordance with various embodiments. -
FIGS. 3 a and 3 b illustrate interaction diagrams of the secured registration of a home network device with the service provider network, in accordance with various embodiments. -
FIG. 4 a illustrates an internetworking block of a home router of the home network, the internetworking block enabling the home router to act as a registrar of home network devices, in accordance with various embodiments. -
FIG. 4 b illustrates an interworking block of a home router where devices in the home network support either non-SIP protocols e.g. universal Plug and Play (uPnP), Digital Living Network Alliance (DLNA) or Extensible Messaging and Presence Protocol (XMPP). -
FIG. 4 c illustrates an interworking block of a home router where the Service Provider Network supports a different protocol (e.g. Extensible Messaging and Presence Protocol). -
FIG. 5 illustrates a subscription profile utilized in registering a device of the home network, in accordance with various embodiments. -
FIG. 6 illustrates a flowchart showing a method of attempting to reestablish a secure connection between a home router of the home network and the service provider network, in accordance with various embodiments. -
FIG. 7 illustrates a flowchart showing a method of determining whether a secure connection has failed, in accordance with various embodiments. -
FIG. 8 illustrates a component level view of a home router of the home network, in accordance with various embodiments. -
FIG. 9 illustrates a component level view of a home network device, in accordance with various embodiments. -
FIG. 10 illustrates a component level view of a server of the service provider network, in accordance with various embodiments. - Described herein are techniques for reestablishing a secure connection based on the passage of time or network conditions. A router of a local or personal network (hereinafter, “home network”) is one endpoint of the secure connection and is configured to reestablish the secure connection when that connection fails. The other endpoint of the secure connection is a service provider network. That service provider network is associated with a service provider which a user of the home network subscribes to for voice or data communication services. The router and service provider network utilize the secure connection to transmit voice and data communications.
- The router monitors the secure connection and network conditions to determine when the secure connection has failed. Once the router determines that the secure connection has failed, the router either waits a period of time after determining the occurrence of the failure or waits until network conditions change. After the period of time or change in network conditions, the router attempts to reestablish the secure connection. If successful, the secure connection is reestablished. If not successful, the router waits another period of time or waits for a further change in network conditions.
-
FIG. 1 illustrates an overview of secured communications between devices of home and service provider networks, in accordance with various embodiments. As shown inFIG. 1 , ahome router 102 of ahome network 104 is securely connected to aservice provider network 106 via anetwork tunnel 108. Devices of thehome network 104 andservice provider network 106 utilize thenetwork tunnel 108 forremote management 110 andregistration 112 of devices of thehome network 104. In various embodiments, the devices of thehome network 104 include thehome router 102 and other devices such as telecommunication devices 114 a, personal digital assistants (PDAs) 114 b, personal computers (PCs) 114 c, and tablet computers 114 d, collectively referred to as “devices 114”. Theservice provider network 106 may include an IMS network having a session border controller (SBC) 116, a remote management server (RMS) 118, a short message service center (SMSC) 120, a call session control function device (CSCF) 122, and a home subscriber server (HSS) 124. In some embodiments, thehome network 104 andservice provider network 106 are private networks connected by anetworking fabric 126. - In various embodiments, the
home router 102 serves as a gateway to theservice provider network 106 forother devices 114 of thehome network 104. Thehome router 102 is configured to establish thenetwork tunnel 108 with a device of theservice provider network 106 to secure communications between thehome network 104 andservice provider network 106 and to reestablish thenetwork tunnel 108 when secure communication fails. Also, thehome router 102 is configured to receiveremote management 110 from theservice provider network 106, to enableremote management 110 of adevice 114 of thehome network 104, and to act as a registrar fordevices 114 of thehome network 104, providing registration requests to theservice provider network 106 on behalf ofdevices 114 of thehome network 104. In some embodiments, thehome router 102 enables voice and data communications between thedevices 114 of thehome network 104 and theservice provider network 106. For example, thehome router 102 may serve as a gateway for phone calls, electronic messages such as email, SMS, and MMS messages, and web browsing. Anexample home router 102 is illustrated in greater detail inFIG. 8 and is described in detail below with reference to that figure. - The home network, as illustrated in
FIG. 1 , includes a plurality ofdevices 114 communicatively coupled via ahome router 102. In some embodiments, thehome network 104 comprises a private network between thesedevices 114, such as a Wide-Area Network (WAN), a local area network (LAN) or personal area network (PAN). Communications between thedevices 114 of thehome network 104 may be wired, wireless, or both. For example, a PC 114 c may be connected to thehome router 102 via an Ethernet cable and a tablet computer 114 d may be connected to thehome router 102 via a Wi-Fi connection—or some other wireless connection, such as a Wi-Max or DECT connection. Also, communications between thedevices 114 of thehome network 104 utilize any sort of communication protocol known in the art for sending and receiving messages, such as the Transmission Control Protocol/Internet Protocol (TCP/IP), the Hypertext Transfer Protocol (HTTP), Extensible Messaging and Presence Protocol (XMPP), and/or the Session Initiation Protocol (SIP). In one embodiment, communications conform to SIP for later transmission by thehome router 102 to theservice provider network 106 and also conform to TCP/IP and/or HTTP for transmission across thehome network 104. In some embodiments, thehome network 104 is associated with a geographic location, such as a residence of a subscriber to theservice provider network 106. In such embodiments, thehome router 102 is located at the geographic location and theother devices 114 of thehome network 104 may also be located at the geographic location or may roam away from the location and, thus, outside of thehome network 104.FIG. 1 , for instance, shows a tablet computer 114 d both within thehome network 104 when at the geographic location of thehome network 104 and outside of thehome network 104 when away from the geographic location. - As mentioned above, the
home router 102 servers as a router and gateway for the communications of thehome network 104, receiving communications overhome network 104 from theother devices 114 of thehome network 104 and providing communications over thehome network 104 to the other devices. As also mentioned above, the devices of thehome network 104 include computing systems such as a telecommunication device 114 a, a PDA 114 b, aPC 114 c, and a tablet computer 114 d. Each of thesedevices 114 is configured to be remotely managed 110 and/or to register 112 with theservice provider network 106. In some embodiments, thedevices 114 are also configured to establish a secure connection via anetwork tunnel 108 with theservice provider network 106 when thedevices 114 are outside of thehome network 104 and to reestablish the secured connection when the secured connection fails. In further embodiments, thehome network 104 includes other devices besides those shown. Such other devices could include at least one of a workstation, a server system, a television, a media player, a digital video recorder, a game device, a set-top box, or a camera. Anexample device 114 is illustrated in greater detail inFIG. 9 and is described in detail below with reference to that figure. - Also, in addition to the
home router 102 anddevices 114, thehome network 104 may include a modem or other computing device that provides connectivity to thenetworking fabric 126 and, throughnetworking fabric 126, to theservice provider network 106. Thus, the modem would serve as a first gateway and could provide networking fabric access to the home router and one or more other devices. In such embodiments, thehome router 102 would be a second gateway providing connectivity fordevices 114 connecting to theservice provider network 106 through thehome router 102 and the modem. Also in such embodiments, both the modem and thehome router 102 are each assigned a public Internet Protocol (IP) address. - In various embodiments, the
service provider network 106 is associated with a service provider, such as a provider of telecommunication services, data services, messaging services, etc. Theservice provider network 106 is a private network of that service provider and includes any one or more networks known in the art, such as cellular networks and/or data networks, including wide area networks (WANs), local area networks (LANs), personal area networks (PANs), and/or the Internet. Communications between the devices of theservice provider network 106 utilize any sort of communication protocol known in the art for sending and receiving messages, such as TCP/IP, HTTP, and/or SIP. The devices of theservice provider network 106 are also connected to each other via wired and/or wireless connections, such as through Ethernet and Wi-Fi connections. Also, theservice provider network 106 may be associated with a single geographic location or with a number of dispersed geographic locations. Because the devices of theservice provider network 106 may be remote from each other geographically, communications between the devices may be secured by VPNs and network tunnels (not shown) or by point-to-point connections. - As shown in
FIG. 1 , theservice provider network 106 includes a plurality of devices 116-124. All or some of these devices 116-124 in turn comprise an IMS network of theservice provider network 106. As mentioned above, an IMS network provides a framework for multimedia voice and data communications, replacing mobile networks such as the Global System for Mobile Communications (GSM). IMS networks rely on data networks such as the Internet and utilize Internet standard protocols, such as SIP, TCP/IP, HTTP, etc. - In various embodiments, the IMS network includes
SBC 116.SBC 116 is further configured to act as a VPN server to provide a secure connection between thehome network 104 and theservice provider network 106. In some embodiments, theSBC 116 sits at the edge of the border of theservice provider network 106 and thenetworking fabric 126 and controls the flow of data and signaling between thenetworking fabric 126 and theservice provider network 106. - The IMS network also includes
CSCF 122.CSCF 122 comprises one or more SIP servers or proxies and processes and routes SIP packets for the IMS network. In one embodiment,CSCF 122 includes at least one of a proxy CSCF, which serves as a SIP proxy and which is integrated in theSBC 116, an interrogating CSCF, which routes SIP requests to a serving CSCF assigned to a system that sent the SIP requests, and a serving CSCF, which interfaces with an HSS of the IMS network and handles SIP registrations. - In some embodiments, the IMS network also includes
HSS 124.HSS 124 is a master user database that stores subscriber-related information (subscriber profiles) and is configured to work with a servingCSCF 122 to perform the registering 112 of devices of thehome network 104. The HSS also performs authentication and authorization of the user, and can provide information about the subscriber's location and IP information. To this end, theHSS 124 is provisioned with subscriber profiles comprising one or more registration sets for each device of thehome network 104. These registration sets are illustrated inFIG. 5 and described in greater detail below with reference to that figure. In some embodiments, theHSS 124 is also called a User Profile Server Function (UPSF). As used herein,HSS 124 refers to an HSS, a User Profile Server Function, or a database containing the subscription-related information. - In addition to the
SBC 116, theCSCF 122, and theHSS 124, the IMS network may include one or both of theRMS 118 or theSMSC 120. In other embodiments, theRMS 118 andSMSC 120 belong to theservice provider network 106 but do not form a part of the IMS network of theservice provider network 106. TheRMS 118 is configured to remotely manage 110 thehome router 102 and/or other devices of thehome network 104 and may include a proxy VPN server to establish thenetwork tunnel 108. TheRMS 118 also provides a graphic user interface (GUI) to an administrative user of theservice provider network 106 or communicates with another server device to enable that device to provide a GUI. Also, either theRMS 118 or the other server device may provide a web GUI accessible by a user of thehome network 104 to, for example, request service or some other type ofremote management 110. TheRMS 118 may also be configured to trigger theSMSC 120 to send an SMS to thehome router 102 to cause thehome router 102 to initiate a secure connection with theservice provider network 106. And theSMSC 120 is complementarily configured to receive a command from theRMS 118 to send an SMS to thehome router 102 and to send, in response to that command, an SMS to thehome router 102. - In various embodiments, the devices 116-124 may be implemented in any sort of computer system, such as a personal computer (PC), a laptop computer, a workstation, a server system, a mainframe, or a server farm. An example device 116-124 is illustrated in greater detail in
FIG. 10 and is described in detail below with reference to that figure. - In addition to the devices 116-124 shown in
FIG. 1 , theservice provider network 106 may also include one or more other devices, such as a voicemail server, a border gateway, an Internet messaging platform, a multimedia telephony application server, a presence server, a media resource function, a multimedia message service center, a content server, or a home location register. Each of these devices performs the function(s) for which it is known in the art. - In various embodiments, the
network tunnels 108 shown inFIG. 1 between theSBC 116 and thehome router 102 and between theSBC 116 and the tablet computer 114 d represent secure communication channels, such as those associated with VPNs. While thedevice 114 of thehome network 104 having itsown network tunnel 108 with theservice provider network 106 is shown as the tablet computer 114 d, any of thedevices 114 ofhome network 104 can establish anetwork tunnel 108 when traveling away from a geographic location associated with thehome network 104. Various techniques for establishing and reestablishing thenetwork tunnels 108 are shown inFIGS. 2 , 3 a, 3 b, and 6 and are described in greater detail below with reference to those figures. Packets transmitted across the network tunnels are encrypted according to the IPSec protocol suite by a VPN client of thehome router 102 or of adevice 114 of thehome network 104 and thenetwork tunnels 108 are thus considered IPSec tunnels. In other embodiments, Secure Socket Layer (SSL) or Transport Layer Security (TLS) may be used in place of or in addition to the IPSec protocol - In some embodiments, the
networking fabric 126 represents any one or more networks known in the art, such as cellular networks and/or data networks, including wide area networks (WANs), LANs, PANs, and/or the Internet. A connection between thehome network 104 and theservice provider network 106 may be through a number of routers, base stations, and/or devices acting as bridges between cellular and data networks. Communications between thehome network 104 and theservice provider network 106 utilize any sort of communication protocol known in the art for sending and receiving messages, such as TCP/IP and/or HTTP. In some embodiments,network fabric 126 also includes an Internet service provider (ISP) providing Internet connectivity to thehome network 104. - In various embodiments, the
remote management 110 shown inFIG. 1 comprises the remote management of thehome router 102 and one ormore devices 114 by theRMS 118. Theremote management 110 includes at least one of repairing, maintaining, updating, configuring, provisioning, or analytics. The details of theremote management 110 are illustrated inFIG. 2 and are described below in greater detail with reference to that figure. - The
registration 112 shown inFIG. 1 comprises the registration of one or more of thedevices 114 and/or thehome router 102 with theservice provider network 106. Theregistration 112 includes providing a pre-provisioned public identifier and receiving a public identifier useable in communications in response. Also, in performing the registering 112, thehome router 102 may act as a registrar forother devices 114, and thedevices 114 may either register themselves or register through thehome router 102 depending on whether they are located within thehome network 104. The details of theregistration 112 process are illustrated inFIGS. 3 a and 3 b and are described below in greater detail with reference to those figures. - Also, in some embodiments, an endpoint of one of the
network tunnels 108 is configured to attempt, in response to determining that thenetwork tunnel 108 has failed, to reestablish thenetwork tunnel 108. The reestablishing of anetwork tunnel 108 is illustrated inFIG. 6 and is described below in greater detail with reference to that figure. -
FIG. 2 illustrates an interaction diagram of the remote management of home network devices, in accordance with various embodiments. The figure includes representations of thehome router 102, adevice 114, theSBC 116, theRMS 118, and theSMSC 120, each representation including a graphic depiction and a vertical line descending across the figure. Between these vertical lines are horizontal lines terminating in arrows representing interactions between ones of thehome router 102, adevice 114, theSBC 116, theRMS 118, and theSMSC 120. Each horizontal line represents a single interaction or a group of interactions. When one of the horizontal lines crosses a vertical line without terminating at an arrow, this indicates that the system associated with the crossed line is not involved in the interaction. When one of the horizontal lines crosses a vertical line, terminates at an arrow, and then resumes, this indicates that the system associated with the crossed line is involved in the interaction. For example, if a horizontal line extends between a first vertical line and a third vertical line, crosses a second vertical line, and terminates with arrows at each of the second and third vertical lines, this indicates that devices associated with each of the first, second, and third vertical lines are involved in the interaction. - In various embodiments, the interactions shown in
FIG. 2 are example interactions associated with theremote management 110 of thehome router 102 and thedevice 114. As mentioned above,remote management 110 enables a device of theservice provider network 106, such as theRMS 118, to provide repair, maintenance, configuration, and other services to devices of thehome network 104 via anetwork tunnel 108 between thehome network 104 andservice provider network 106. - In various embodiments, the
remote management 110 is responsive to status reports or schemas provided 202 by thehome router 102 to, for example, theRMS 118. As illustrated, thehome router 102 provides 202 the status report or schema to theRMS 118 through theSBC 116, which provides thehome router 102 with connectivity to theservice provider network 106. The status report includes performance metrics associated with thehome router 102, withdevices 114, and with other aspects of thehome network 104. The schema includes information associated with configurations and versions of various modules and processes of thehome router 102 anddevices 114. The status reports and schemas may be created on a pre-determined basis, such as every n time units by module(s) of thehome router 102 and/ordevices 114. Also or instead, the module(s) of thehome router 102 and/ordevices 114 can create the status reports or schemas in response to the occurrence of an event, such as a configuration change or performance exceeding a threshold. - In some embodiments, when the
RMS 118 receives a status report or schema, theRMS 118 stores that status report or schema. Also, theRMS 118 evaluates the received status report or schema to determine whether or not to performremote management 110 of thehome router 102 ordevices 114. For example, if the schema indicates that thehome router 102 has version A of a software patch and the service provider now requires version B, theRMS 118 would triggerremote management 110 of thehome router 102. Thus,RMS 118 utilizes one or more factors such as specifications of current configurations or versions or performance thresholds to determine whether or not to initiateremote management 110 of thehome router 102 and/ordevices 114 in response to the provided 202 status report or schema. - To trigger
remote management 110, theRMS 118 instructs theSMSC 120 to send 204 a an SMS to thehome router 102 to trigger thehome router 102 to request a secure connection, such as a VPN. TheRMS 118 may instruct theSMSC 120 in response to a status report or schema, as discussed above, or in response to an entry or selection made by an administrative user of theservice provider network 106. For example, a user of ahome network 104 may call the service provider of theservice provider network 106 to complain about a problem with thehome router 102 or adevice 114, such as slow performance, or in regards to setting up thehome router 102 or adevice 114. The call is then connected to an administrative user of theservice provider network 106, such as a customer care representative or the like. The administrative user then enters or selects a command which causes theSMSC 120 to send 204 a an SMS to thehome router 102. In one embodiment, the command is selected or entered via a GUI associated with theRMS 118 or with another device of theservice provider network 106. - Upon receiving a command to send 204 a an SMS, whether in response to a status report or schema or in response to input received from an administrative user, the
SMSC 120 formulates an SMS and sends 204 a the SMS to thehome router 102. In some embodiments, the SMS is not sent through theRMS 118 orSBC 116, but rather is communicated directly across thenetworking fabric 126. In other embodiments (not shown), one or both of theRMS 118 orSBC 116 is involved in the transmission of the SMS. The SMS sent 204 a includes at least a command instructing thehome router 102 to request a VPN. In addition to this command, the SMS may include additional information, such as information including an address or locator of theRMS 118 orSBC 116, a time at which to request the VPN, and retry behavior for utilization in the event that the VPN fails. - In various embodiments, as shown by
FIG. 2 , the VPN request is triggered byactivation 204 b of a control of thehome router 102 rather than in response to an SMS being sent 204 a. As described further herein, thehome router 102 is equipped with one or more controls, such as physical push buttons or soft keys of a touch-sensitive graphic user interface. In one embodiment, the physical push button is a dedicated key for triggering a VPN request. A user of thehome router 102 activates 204 b the control by touching or pressing on the control, the touching or pressing of the control signaling module(s) within thehome router 102 to formulate and transmit a VPN request. A user of thehome router 102 might activate the control in response to a performance issue, such as slow operation, or to request help setting up or configuring thehome network 104 - While triggering of a VPN request is shown in
FIG. 2 as resulting from the sending 204 a of an SMS or from theactivation 204 b of a control, any other number of mechanisms known in the art for triggering a VPN request may also be practiced by thehome router 102. For example, the SMS may be sent 204 a in response to the interaction of a user of the home network or an administrative user of the service provider with a GUI offered by a web page. - In various embodiments, the
home router 102 sends 206 a VPN request in response to being triggered to do so. As illustrated inFIG. 2 , the secure connection request is transmitted to theSBC 116, which implements a VPN server for establishing secure connections, such asnetwork tunnel 108. In other embodiments (not shown), the VPN request is relayed to theRMS 118 or another device implementing a VPN server or proxy VPN server. To send 206 the VPN request, thehome router 102 first determines an address or locator of a device to send 206 the request to, such as an address or locator of theSBC 116. Thehome router 102 may determine the address by examining an SMS, if received, or by retrieving and address or locator that has previously been provided to thehome router 102. In some embodiments, the address is an IP address and is hard coded on thehome router 102 or provided with an update. Also, in some embodiments, the VPN request specifies an IP address and port number of thehome router 102 or an IP address of a modem to which thehome router 102 is connected and a port number on which thehome router 102 is listening. In various embodiments, the operations utilized to formulate and send 206 the VPN request are performed by a VPN client of thehome router 102. - In some embodiments, the
home router 102 may be connected to thenetworking fabric 126 and reachable via thatnetworking fabric 126. As mentioned above, thehome router 102 may be connected via a modem which serves as a gateway to thenetworking fabric 126 for thehome router 102. In such a situation, the modem may implement port forwarding to enable connectivity to thehome router 102. Or if the modem does not implement port forwarding, thehome router 102 may at least be associated with a public IP address, such as an IP address assigned by an ISP. In one embodiment, the modem is a Network Address Translation (NAT) gateway which assigns private IP addresses to thehome router 102 anddevices 114. - In another embodiment, the modem is a Network Address Translation/Protocol Translation which translates IPv4 to IPv6 (and vice versa) or acts as a DHCP server.
- Also, as mentioned above, the packets communicated across the secure connection, which may be a
network tunnel 108 of a VPN, are encrypted according to the IPSec protocol suite. Further, each packet to be communicated is encapsulated inside another packet. The header of this other packet used for encapsulating may be modified as the packet crosses different networks, but the payload and header of the encapsulated packet are not modified. Additionally, if thehome router 102 is accessed through a NAT gateway, the encapsulated packet is again encapsulated in a further packet, the further packet being a User Datagram Protocol (UDP) packet for NAT traversal. - Once the
SBC 116 receives the VPN request, theSBC 116 establishes 208 thenetwork tunnel 108. In various embodiments, in establishing 208 thenetwork tunnel 108, theSBC 116 assigns 210 an IP address, such as a private IP address, to thehome router 102 for use in secure communication between theSBC 116 andhome router 102. That IP address is then used for communications across thenetwork tunnel 108. TheSBC 116 andhome router 102 may each also perform a number of other operations to establish 208 thenetwork tunnel 108. Operations used to establish anetwork tunnel 108 are known to those skilled in the art and thus need not be described further. - Once the
network tunnel 108 between theSBC 116 andhome router 102 has been established, theRMS 118 utilizes thenetwork tunnel 108 to remotely manage 110 thehome network 104. Remotely managing 110 thehome network 104 includes any or all of remotely managing 212 thehome router 102, remotely managing 214 adevice 114, or accessing 216 a UI, such as a GUI, of thehome router 102 or of adevice 114. As shown inFIG. 2 , theremote management 212 and 214 andaccess 216 are transmitted through theSBC 116 and thenetwork tunnel 108. Also, the remote management 214 of thedevice 114 is further transmitted through thehome router 102 and across thehome network 104. In some embodiments, theremote management 212 and 214 andaccess 216 are transmitted in the form of commands and/or data. - In some embodiments, the
RMS 118 is notified of theestablishment 208 of thenetwork tunnel 108 by either theSBC 116 or thehome router 102. Or, in other embodiments, theRMS 118 discovers by monitoring that anetwork tunnel 108 has been established 208. - In various embodiments, whether the
RMS 118 remotely manages 212 thehome router 102, remotely manages 214 adevice 114, or both depends on the reason for triggering thenetwork tunnel 108. For example, if thehome router 102 sent 202 a schema indicating versions of a software module on thehome router 102 and on adevice 114 that are out of date, theRMS 118 may have triggered 204 a the initiating of thenetwork tunnel 108 to provide thehome router 102 anddevice 114 with updated versions of the software module. In such an example, theRMS 118 remotely manages 212 thehome router 102 by transmitting the updated software module to thehome router 102, installing the updated software module, and verifying that thehome router 102 functions properly with the updated software module installed. TheRMS 118 also remotely manages 214 adevice 114 by transmitting the updated software module to thedevice 114, installing the updated software module, and verifying that thedevice 114 functions properly with the updated software module installed. - In another example, the
home router 102 is not functioning properly and its user calls a customer care representative of the service provider. That representative, who acts as the above-described administrative user, instructs the user to push a button or actuate a soft key to trigger initiation of anetwork tunnel 108. The representative then interacts with theRMS 118 to remotely manage 212 thehome router 102, theremote management 212 including investigating potential causes of the improper functioning. To enable investigating, thehome router 102 may include a module which performs diagnostic tests and provides access to system settings and metrics toRMS 118. In response to the investigating, theRMS 118 might, for example, updatehome router 102 settings, modify settings of a firewall associated with thehome router 102, or download and install a software patch. - In some embodiments, the investigating includes accessing 216 a UI of the
home router 102 ordevice 114, such as a GUI. The UI may convey an error message, for example, and theRMS 118 may access 216 the UI to review the error message. In various embodiments, theRMS 118 may access 216 the UI for other reasons. For example, the user may be attempting to set up thehome router 102 for use the first time. In such circumstances, the representative of the service provider utilizes theRMS 118 to access 216 the UI to walk the user through the set up. - In addition to the examples of
remote management 110 provided above, theremote management 110 includes at least one of repairing, maintaining, updating, configuring, provisioning, or analytics. The repairing, maintaining, updating, configuring, provisioning, or analytics may comprise theremote management 212 of thehome router 102, the remote management of adevice 114, or both. - In various embodiments, upon completion of
remote management 110, theRMS 118 sends 218 a command to terminate thenetwork tunnel 108. The request is sent to thehome router 102 through theSBC 116 andnetwork tunnel 108. The command may be manually initiated by the service provider or automatically initiated in response to an event, such as the occurrence of a pre-determined idle time. - Upon receiving the command to terminate the
network tunnel 108, the home router terminates 220 thenetwork tunnel 108. In other embodiments, thehome router 102 terminates thenetwork tunnel 108 without receiving any sort of command to do so. For example, thehome router 102 may also monitor for events such as the occurrence of a pre-determined idle time and, in response to detecting the occurrence of the event, may terminate 220 thenetwork tunnel 108. -
FIGS. 3 a and 3 b illustrate interaction diagrams of the secured registration of a home network device with the service provider network, in accordance with various embodiments.FIG. 3 a includes representations of thehome router 102, adevice 114, theSBC 116, theCSCF 122, and theHSS 124, each representation including a graphic depiction and a vertical line descending across the figure.FIG. 3 b includes representations of adevice 114, theSBC 116, theCSCF 122, and theHSS 124, each representation including a graphic depiction and a vertical line descending across the figure. Between these vertical lines are horizontal lines terminating in arrows representing interactions between ones of thehome router 102, adevice 114, theSBC 116, theCSCF 122, and theHSS 124. Each horizontal line represents a single interaction or a group of interactions. When one of the horizontal lines crosses a vertical line without terminating at an arrow, this indicates that the system associated with the crossed line is not involved in the interaction. When one of the horizontal lines crosses a vertical line, terminates at an arrow, and then resumes, this indicates that the system associated with the crossed line is involved in the interaction. For example, if a horizontal line extends between a first vertical line and a third vertical line, crosses a second vertical line, and terminates with arrows at each of the second and third vertical lines, this indicates that devices associated with each of the first, second, and third vertical lines are involved in the interaction. - In various embodiments, a
device 114 of ahome network 104registers 112 itself with theservice provider network 106 through a series of interactions illustrated inFIGS. 3 a-3 b. Thedevice 114registers 112 itself the first time that thedevice 114 is used. Thedevice 114 may also register itself on subsequent occasions, such as when initiating a communication such as a phone call or electronic message. In some embodiments, thedevice 114 initiates the registering 112 automatically, without any interaction with a device user. In other embodiments, the user must take some action, such as pushing a button or entering a key sequence, to cause thedevice 114 to register 112 itself. - As shown in
FIGS. 3 a and 3 b, once thedevice 114 determines to register 112 itself, thedevice 114 formulates 302 a network registration request. In some embodiments, the network registration request is formulated 302 as a SIP register request by a SIP client of thedevice 114. In other embodiments, thedevice 114 is not equipped with a SIP client and formulates 302 the request in some other form. Other forms can include text, Extensible Markup Language (XML), etc. - The network registration request comprises a registration set containing at least one of a globally unique private device identifier and a pre-provisioned public identifier. In some embodiments, the private identifier and/or pre-provisioned public identifier are stored in memory of the
device 114. In other embodiments, the private identifier and/or pre-provisioned public identifier is obtained from another device, such ashome router 102. Either of the private identifier or the pre-provisioned public identifier may be one of a telephone number, an IP address, or a messaging identifier. In one embodiment, the private identifier may be an IP Multimedia Private Identity (IMPI) and the pre-provisioned public identifier may be an IP Multimedia Public Identity (IMPU) for use in an IMS network of the service provider. In some embodiments, the pre-provisioned public identifier is only used for registering 112 thedevice 114, and thedevice 114 receives another public identifier for use in voice and data communication in response to the registering 112. In such embodiments, the pre-provisioned public identifier is not useable in voice and data communications. The other public identifier may also be an IMPU and may be one of a telephone number, an IP address, or a messaging identifier. - In various embodiments, once the
device 114 has formulated 302 the network registration request, thedevice 114 determines 304 whether it is connected to thehome router 102 and thus to thehome network 104. Thedevice 114 is equipped with module(s) for performing the determining 304. Such module(s) may examine existing connections of thedevice 114 and/or may attempt to ping or otherwise contact thehome router 102 to determine whether thehome router 102 is reachable. If thehome router 102 is reachable, but thedevice 114 is not connected to the home router, thedevice 114 establishes a connection with thehome router 102, such as a LAN or PAN connection. In some embodiments, thedevice 114 utilizes a wireless interface, such as a Wi-Fi, Bluetooth, Wi-Max, or DECT interface to contact and connect to thehome router 102.FIG. 3 a illustrates further interactions in response to thedevice 114 determining 304 that thedevice 114 is connected to thehome router 102.FIG. 3 b illustrates further interaction in response to thedevice 114 determining that thedevice 114 is not connected to thehome router 102. - As shown in
FIG. 3 a, if thedevice 114 determines 304 that thedevice 114 is connected to thehome router 102, thedevice 114 sends 306 the network registration request to thehome router 102. Thedevice 114 sends 306 the network registration request via the LAN or PAN comprising thehome network 104 and connecting thedevice 114 to thehome router 102. Once thehome router 102 receives the network registration request, it determines whether the network registration request is a SIP register request. If it is not a SIP register request, the home router transforms the network registration request into a SIP register request using an Internetworking block of thehome router 102. An example Internetworking block is illustrated inFIG. 4 and described below in greater detail with reference to that figure. - In various embodiments, the
home router 102 next establishes 308 a secure connection, such as anetwork tunnel 108 of a VPN, in response to receiving the network registration request from thedevice 114. To establish 308 thenetwork tunnel 108, thehome router 102 first sends a secure connection request, such as a VPN request, to theSBC 116 of theservice provider network 106. To send the VPN request, thehome router 102 first determines an address or locator of a device to send the request to, such as an address or locator of theSBC 116. Thehome router 102 may determine the address by retrieving an address or locator that has previously been provided to thehome router 102. In some embodiments, the address is an IP address and is hard coded on thehome router 102 or provided with an update. Also, in some embodiments, the VPN request specifies an IP address and port number of thehome router 102 or an IP address of a modem to which thehome router 102 is connected and a port number on which thehome router 102 is listening. In various embodiments, the operations utilized to formulate and send the VPN request are performed by a VPN client of thehome router 102. - In some embodiments the
home router 102 may be connected to thenetworking fabric 126 and reachable via thatnetworking fabric 126. As mentioned above, thehome router 102 may be connected via a modem which serves as a gateway to thenetworking fabric 126 for thehome router 102. In such a situation, the modem may implement port forwarding to enable connectivity to thehome router 102. Or if the modem does not implement port forwarding, thehome router 102 may at least be associated with a public IP address, such as an IP address assigned by an ISP. In one embodiment, the modem is a Network Address Translation (NAT) gateway which assigns IP addresses, such as private IP addresses, to thehome router 102 anddevices 114. - Also, as mentioned above, the packets communicated across the
network tunnel 108 are encrypted according to the IPSec protocol suite. Further, each packet to be communicated is encapsulated inside another packet. The header of this other packet used for encapsulating may be modified as the packet crosses different networks, but the payload and header of the encapsulated packet are not modified. Additionally, if thehome router 102 is accessed through a NAT gateway, the encapsulated packet is again encapsulated in a further packet, the further packet being a User Datagram Protocol (UDP) packet for NAT traversal. - In various embodiments, in establishing 308 the
network tunnel 108, theSBC 116 assigns an IP address, such as a private IP address to thehome router 102 for use in secure communication between theSBC 116 andhome router 102. That IP address is then used for communications across thenetwork tunnel 108. TheSBC 116 andhome router 102 may each also perform a number of other operations to establish 308 thenetwork tunnel 108. Operations used to establish anetwork tunnel 108 are known to those skilled in the art and thus need not be described further. - In other embodiments, not illustrated in
FIG. 3 a, thenetwork tunnel 108 is established when thehome router 102 is powered on or at some other time previous to receipt of the network registration request. In such embodiments, thenetwork tunnel 108 is maintained while thehome router 102 is powered on so that a secure connection for transmission of voice and data communications is available and does not have to be established anew each time a new communication is received. - As illustrated in
FIG. 3 a, thehome router 102 provides 310 the network registration request of thedevice 114 to theHSS 124. The network registration request is sent via thenetwork tunnel 108 to theSBC 116, fromSBC 116 to theCSCF 122, and from theCSCF 122 to theHSS 124. As mentioned above, theservice provider network 106 may include multiple HSSs and theCSCF 122 selects among these multiple HSSs. Also, in receiving the network registration request and providing 310 that request to theservice provider network 106, thehome router 102 acts as a registrar and back-to-back user agent (B2BUA). As B2BUA and registrar, thehome router 102 implements a user agent server to receive the network registration request, convert the request to SIP if necessary, and store the request for later transmission if theservice provider network 106 is unavailable. Thehome router 102 also implements a user agent client to make the network registration request on behalf of thedevice 114 by providing 310 the request and waiting for a response. - Once the network registration request is received by the
HSS 124, theHSS 124 compares the registration set(s) of the network registration request to mappings stored 312 by theHSS 124. The storing 312 of the mappings, which is shown as occurring after theHSS 124 receives the network registration request and before theHSS 124 sends a response, can occur at any time. The mappings may have been stored 312, for example, in theHSS 124 at the time that thedevice 114 was purchased. A subscription to services offered by the service provider can be purchased at the same time as thedevice 114, and mappings which include a subscription profile corresponding to that subscription can be created and stored 312 when that subscription is purchased. - The mappings stored 312 by the
HSS 124 include subscription profiles associated with a plurality of subscriptions for services offered by the service provider. Each subscription profile is in turn associated with one or more registration sets. Each registration set in turn includes one or more private identifiers, each private identifier being associated with a pre-provisioned public identifier and another public identifier for use in voice and data communications. Each public identifier is associated with a service profile. Further details of an example subscription plan are illustrated inFIG. 5 and described below in reference to that figure. - In some embodiments, the
HSS 124 utilizes the pre-provisioned identifier and/or private identifier included in the network registration request to locate all matching registration sets that include that identifier or identifiers. Once those matching registration sets are located, the other public identifiers stored in those matching registration sets are noted as being registered, thereby allowing those other public identifiers to be used in voice or data communication. Noting a public identifier (and, thus, its associated device 114) as being registered may involve altering anHSS 124 setting or notifying another device or devices of theservice provider network 106 that the public identifier is registered and ready for use. - Next, the
HSS 124 sends a response to the network registration request to thehome router 102, the response including the other public identifier(s) of the matching registration sets and the private identifier (if not included in the network registration request). The response is sent to theCSCF 122, from theCSCF 122 to theSBC 116, and from theSBC 116 to thehome router 102 via thenetwork tunnel 108. Once thehome router 102 receives 314 the network registration response, thehome router 102 determines whichdevice 114 of thehome network 104 to send the network registration response to. In some embodiments, the response includes an identification of thedevice 114. In other embodiments, thehome router 102 stores records of the network registration requests and maps responses to those stored requests. - The
home router 102 then sends 316 the network registration response to thedevice 114. Thedevice 114 examines the received response to ascertain other public identifiers included in the response, and private identifiers(s) (if included in the response). Thedevice 114 stores these other public identifiers and private identifiers in memory and then assigns device settings based on the other public identifiers. For example, one of the other public identifiers may be a phone number that thedevice 114 is to use in making and receiving calls. Upon ascertaining that phone number from the response, thedevice 114 sets an internal phone number setting to the received phone number. - As mentioned above, if the
device 114 determines 304 that it is not connected to thehome router 102 and that thehome router 102 is unreachable, thedevice 114 will establish 318 anetwork tunnel 108 between itself and theSBC 116 and provide 320 the network registration request through thatnetwork tunnel 108.FIG. 3 b illustrates such establishing 318 and providing 320. - In various embodiments, the
device 114 determines 304 that thehome router 102 is unreachable when thedevice 114 is away from a geographic location associated with thehome network 104. Upon determining formulating 302 the network registration request and determining 304 that thedevice 114 is not connected to (or connectable to) thehome router 102, thedevice 114 proceeds to establish anetwork tunnel 108 by sending a VPN request to theSBC 116. In such embodiments, the VPN request is transmitted over thenetworking fabric 126 or some other networking fabric. For example, thedevice 114 may be a cellular device and thenetworking fabric 126 may include a cellular network capable of transmitting the VPN request to theSBC 116. - To send the VPN request, the
device 114 first determines an address or locator of theSBC 116. Thedevice 114 may determine the address by retrieving an address or locator that has previously been provided to thedevice 114. In some embodiments, the address is an IP address and is hard coded on thedevice 114 or provided with an update. Also, in some embodiments, the VPN request specifies an IP address and port number of thedevice 114. In various embodiments, the operations utilized to formulate and send the VPN request are performed by a VPN client of thedevice 114. - Also, as mentioned above, the packets communicated across the
network tunnel 108 are encrypted according to the IPSec protocol suite. Further, each packet to be communicated is encapsulated inside another packet. The header of this other packet used for encapsulating may be modified as the packet crosses different networks, but the payload and header of the encapsulated packet are not modified. - In various embodiments, in establishing 318 the
network tunnel 108, theSBC 116 assigns an IP address, such as a private IP address, to thedevice 114 for use in secure communication between theSBC 116 anddevice 114. That IP address is then used for communications across thenetwork tunnel 108. TheSBC 116 anddevice 114 may each also perform a number of other operations to establish 308 thenetwork tunnel 108. - Once the
network tunnel 108 is established 318, thedevice 114 provides 320 the network registration request to theHSS 124 of the service provider network via thenetwork tunnel 108,SBC 116, andCSCF 122 and receives 322, in response, a network registration response including a public identifier for use in voice and data communications. The providing 320 and receiving 322 performed by thedevice 114 is similar to the above described providing 306/310 and receiving 314/316, except that thehome router 102 is bypassed and does not act as a registrar or B2BUA. Also, the storing 312 of mappings shown inFIG. 3 b is performed in the same manner as the storing 312 shown inFIG. 3 a. The result of these interactions, as described above in regard toFIG. 3 a, is that thedevice 114 receives a public identifier and modifies internal settings based on the received public identifier. - In various embodiments, once the
device 114 is registered 112, thedevice 114 utilizes the public identifier received through registering 112 in subsequent voice and data communications. -
FIG. 4 a illustrates an internetworking block of ahome router 102 of thehome network 102, in accordance with various embodiments. As mentioned above, theinternetworking block 400 enables thehome router 102 to act as a registrar and B2BUA ofdevices 114. Theinternetworking block 400 includesB2BUA 402, the B2BUA including a plurality of user agent legs (UA legs) 404 and aUA leg 406. TheUA legs 404 receive network registration requests from thedevices 114 and convert the requests to IMS-compliant SIP if necessary. Some of theUA legs 404 are coupled tointerfaces 408, such as remote access, DECT, and PSTN interfaces capable of receiving signals and transforming those signals into a form readable by theUA legs 404. While not shown,other interfaces 408 known in the art may be utilized as well. TheUA leg 406 provides IMS-compliant SIP communications to theservice provider network 106, such as IMS-compliant SIP network registration requests on behalf of thedevices 114 and receives SIP responses, such as the above mentioned network registration responses. TheUA legs - In addition to
B2BUA 502, the internetworking block includes anSIP registrar 410 and a security andidentity module 412. TheSIP registrar 410 stores the network registration requests for later transmission if theservice provider network 106 is unavailable, thereby acting as a proxy registrar of thedevices 114 for theservice provider network 106. The security andidentity module 412 is used by theUA client 406 to authenticate thehome router 102 to the IMS network of the service provider. -
FIG. 4 b illustrates an internetworking block of ahome router 102 interfacing devices in the home network supporting other protocols such as Universal Plug and Play (UPnP), or Digital Living Network Alliance (DLNA), or Extensible Messaging and Presence Protocol (XMPP). One difference fromFIG. 4 a is the interface which interacts with the IMS B2BUA (Back-to-Back User Agent). The UPnP interface behaves as an UPnP server. The DLNA interface behaves as a DLNA server. Also, when an XMPP client registers in thehome network 104, the XMPP/SIP gateway maps the XMPP identities to SIP/IMS identities and generates a network registration toward theservice provider network 106. The XMPP/SIP Bridge 430 translates XMPP to SIP. -
FIG. 4 c illustrates an internetworking block of ahome router 102 in which theservice provider network 106 supports Extensible Messaging and Presence Protocol (XMPP). TheXMPP Bridge 430 needs to manage different identities, translates protocols such as Real Time Streaming Protocol (RTSP) or Session Initiation Protocol (possibly on different transport protocols such as UDP and TCP) and performs network registration. TheXMPP UA 431 leg interfaces theservice provider network 106 possibly thru another network (e.g. WAN) not shown in the figure. TheXMPP interface 432 interacts with an XMPP device of thehome network 104; it acts as an XMPP server. -
FIG. 5 illustrates a subscription profile utilized in registering a device of the home network, in accordance with various embodiments. As illustrated, asubscription profile 500 stored by theHSS 124 includes one or more registration sets 502. TheHSS 124 may store a plurality ofsubscription profiles 500 for a plurality of subscribers. Eachsubscriber profile 500 can include registration information for ahome router 102 and a plurality ofdevices 114, or information for just onehome router 102 ordevice 114. Each subscriber profile may also comprise a unique identifier of the subscriber, such as an account number. - In various embodiments, each registration set 502 includes a
private identifier 504, such as an IMPI, a pre-provisionedpublic identifier 506, another public identifier 508 (bothpublic identifiers service profile 510 for each of thepublic identifiers home router 102 ordevice 114, or specific to a communication channel, such as a phone line. When specific to a communication channel, ahome router 102 ordevice 114 having multiple such channels transfers multiple registration sets in the network registration request. Thus, inFIG. 5 , the two registration sets 502 bounded in the first box are for multiple channels of a single device, and the other registration set 502 is specific to a single device or is associated with a device having a single channel. - As mentioned before, the pre-provisioned
public identifiers 506 are used in matching public identifiers included in the network registration requests but not in publicly identifying thehome router 102 ordevice 114 for voice or communication services. The service profiles 510 associated with the pre-provisionedpublic identifiers 506 are either dummy service profiles or are duplicates of the service profiles associated with the otherpublic identifiers 508. - In various embodiments, the other
public identifiers 508 are returned by theHSS 124 in a network registration response to enable thehome router 102 and devices to utilize thosepublic identifiers 508 in voice and data communication. In some embodiments, the samepublic identifier 508 is associated with multiple registration sets 502 and with multiple devices. Thus, thehome router 102 and adevice 114 may share apublic identifier 508,multiple devices 114 may share apublic identifier 508, etc. In one embodiment, all devices of thehome network 104 share at least one public identifier. The sharing of a public identifier between multiple devices enables, for example, simultaneous ringing of the multiple devices in response to an incoming call. While multiple registration sets 502 include the samepublic identifier 508, however, each of the samepublic identifiers 508 is associated with adifferent service profile 510. Each of theseservice profiles 510 is utilized by an IMS server, such as theCSCF 122 in handling communications to and from adevice 114 associated with a public identifier. - In some embodiments, the pre-provisioned public identifier can be used to enable device-unique 911 calling. As mentioned above, the pre-provisioned public identifier is used to register a
device 114 to theservice provider network 106 and that device is provided in return with a public identifier that may not be unique to the device. Since the provided public identifier may not be unique, thedevice 114 may be required to initiate 911 calls from its pre-provisioned public identifier, as it is important to uniquely identify thecalling device 114 in a 911 call scenario. To enable the pre-provisioned public identifier to be used to make 911 calls, the pre-provisioned public identifier may be associated with a service profile that is enabled for outgoing 911 calls (i.e. 911 calls placed by end-users). As end-users are often unaware of their pre-provisioned public identifier, the pre-provisioned public identifier could also be mapped to a public identifier with which end-users are familiar. One way is to map the pre-provisioned public identifier on which the call is placed to a known public identifier by end-users with the addition of a unique extension per device. This mapping could be performed by thedevice 114, by thehome router 102, or by theservice provider 106. - In some embodiments, if a 911 call is dropped, a public safety answering point (PSAP) may be able to call back the
device 114 on which the call was placed. Theservice provider network 106 shall maintain mappings (for some time) between the pre-provisioned public identifier and the identity provided to PSAP (which may be, for example, another public identifier known to an end-user or an extension of such a public identifier. For example, the mapping may result from the pre-provisioned public identifier being used in a SIP INVITE to the terminated S-CSCF when the other public identifiers are not unique (shared among devices). -
FIG. 6 illustrates a flowchart showing a method of attempting to reestablish a secured connection between ahome router 102 of thehome network 104 and theservice provider network 106, in accordance with various embodiments. In various embodiments, thehome router 102 initiates the method of reestablishing when thehome router 102 determines 602 that a secured connection between the home router and a remote server of theservice provider 106, such as anetwork tunnel 108 of a VPN, has failed. Thehome router 102 includes one or more modules capable of monitoring the secure connection, network conditions, and the reachability of theservice provider network 106. The operations performed by these one or more modules are shown inFIG. 7 and described below in greater detail with reference to that figure. - In some embodiments, the one or more monitoring modules continuously perform their operations while the
home router 102 and secure connection are utilized. As described above, thehome router 102 and secure connection can be utilized forremote management 110 of thehome router 102 and/or of adevice 114 of thehome network 104, or forregistration 112 of adevice 114 of thehome network 104. The secure connection may have been established to perform theremote management 110 orregistration 112, or may have been established, for example, when thehome router 102 was powered-on. - Also, as described above, the secure connection may be terminated when the
remote management 110 orregistration 112 are complete. To prevent the one or more monitoring modules from erroneously noting a secure connection failure when the secure connection has been purposefully terminated, other modules of thehome router 102 instruct the one or more monitoring modules to cease monitoring when the secure connection is terminated. - In various embodiments, after determining 602 that the secure connection has failed, the
home router 102 determines whether a condition has been met before reestablishing the secure connection. As illustrated inFIG. 6 , determining whether a condition has been met includes either determining 604 a time since the secure connection failed and comparing the determined time to a threshold or monitoring 606 network conditions. To determine 604 the time since the secure connection failed, thehome router 102 ascertains a time at which the one or more monitoring modules indicated that the secure connection had failed, a current system time, and a difference between those times. That determined 604 time is then compared by thehome router 102 to the threshold. In some embodiments, the threshold corresponds to a pre-determined time that thehome router 102 is configured to wait before attempting 608 to reestablish the secure connection. The pre-determined time may be set by the service provider and provided to thehome router 102 in an update, for example. Also, the pre-determined time may be experimentally determined. - In some embodiments, the modules monitoring 606 the network conditions are the same as the one or more modules that determined 602 that the secure connection had failed. In other embodiments, other modules of the
home router 102 perform themonitoring 606. In either case, themonitoring 606 includes at least one of monitoring network connectivity, monitoring network congestion, or ascertaining whether theservice provider network 106 is reachable. - In response to determining 604 that the time since secure connection failure meets or exceeds the threshold, or in response to determining the occurrence of at least one network condition (e.g.,
service provider network 106 determined to be reachable), thehome router 102attempts 608 to reestablish the secure connection between thehome router 102 and a remote server of theservice provider network 106, such asSBC 116. As shown inFIG. 6 , the attempting 608 can involve any one or more of operations 610-620. - In some embodiments, the attempting 608 includes performing the attempting in response to activation 610 of a control of the
home router 102 or in response to a receiving 612 a message instructing thehome router 102 to perform the attempting 608. In one embodiment, thehome router 102attempts 608 to reestablish the secure connection in response to an activation 610 or received message 612, without first determining 604 that the time meets the threshold and without monitoring 606 network conditions. Both activation 610 of a home router control and receipt 612 of a message, such as an SMS, are discussed above in greater detail. With respect to receiving 612 a message, a server of theservice provider network 106 may monitor network connectivity, congestion, and reachability of thehome router 102 and cause a message to be sent by, for example, theSMSC 120 of theservice provider network 106 when the monitoring indicates that the secure connection can be successfully reestablished. In some embodiments, the monitoring indicates that the secure connection can be successfully reestablished when, for example, thehome router 102 is determined to be reachable. - In various embodiments, the attempting 608 also or instead includes sending 614 a secure connection request, such as a VPN request. To send 614 the VPN request, the
home router 102 first determines an address or locator of a device to send the request to, such as an address or locator of theSBC 116. Thehome router 102 may determine the address by retrieving an address or locator that has previously been provided to thehome router 102. In some embodiments, the address is an IP address and is hard coded on thehome router 102 or provided with an update. Also, in some embodiments, the VPN request specifies an IP address and port number of thehome router 102 or an IP address of a modem to which thehome router 102 is connected and a port number on which thehome router 102 is listening. In various embodiments, the operations utilized to formulate and send the VPN request are performed by a VPN client of thehome router 102. - In some embodiments, the attempting 608 also or instead includes utilizing 616 a binary exponential back-off (BEB) algorithm in timing repeated
attempts 608 to reestablish the secure connection. Thehome router 102 utilizes 616 the BEB algorithm to schedule afurther attempt 608 when anattempt 608 fails. The BEB algorithm schedules a first retry after a certain wait (e.g., 10 seconds) and, if that retry also fails, schedules a further retry after double the wait (e.g., 20 seconds). The BEB algorithm iteratively doubles the wait with each attempt until a max wait is reached (e.g., 24 hours). If a retry after the max wait also fails, thehome router 102 ceases to attempt 608 to reestablish the secure connection. - In various embodiments, the attempting 608 also or instead includes attempting 618 to reestablish at time intervals (as with the BEB algorithm) and, if unsuccessful, attempting 618 based on network conditions. Thus, the
home router 102 may attempt to reestablish the secure connection for a time limit, attempting at multiple intervals, and then wait for the presence of a network condition, such as network connectivity, before attempting 618 again. - Additionally, the attempting 608 also or instead includes attempting 620 to establish a secure connection with a second server if the first server is determined to be unreachable by monitoring 606. An identifier for the second server may be hard-coded on the
home router 102 or received with an update from theservice provider network 106 and stored on thehome router 102. - As further illustrated in
FIG. 6 , asuccessful attempt 608 to reestablish the secure connection results in the establishing 622 of a secure connection between thehome router 102 and a server of theservice provider network 106. In various embodiments, in establishing 622 the secure connection, the server of theservice provider network 106 assigns an IP address, such as a private IP address, to thehome router 102 for use in secure communication between the server and thehome router 102. That IP address is then used for communications across the secure connection. The server andhome router 102 may each also perform a number of other operations to establish 622 the secure connection. Operations used to establish a secure connection such as anetwork tunnel 108 are known to those skilled in the art and thus need not be described further. - In various embodiments, the method illustrated in
FIG. 6 is performed by adevice 114 rather than inhome router 102 when the secure connection is between thedevice 114 and theservice provider network 106. -
FIG. 7 illustrates a flowchart showing a method of determining 602 whether a secured connection has failed, in accordance with various embodiments. As mentioned above, one or more modules of thehome router 102 monitor at least one of network connectivity, network congestion, or server reachability. The modules operate continuously while the secure connection is utilized. As illustrated inFIG. 7 , the monitoring can include ascertaining network connectivity, congestion, and server reachability in a sequential fashion. In some embodiments, the modules first determine 702 whether a network outage has occurred. Determining 702 whether a network outage has occurred involves at least one of checking a status of a physical link, checking whether an IP address is a valid IP address, or performing a name server lookup. If the determining 702 indicates that an outage has occurred, the modules determine 602 that the secure connection has failed. If, on the other hand, the determining 702 indicates that an outage has not occurred, the modules determine 704 whether the network is congested. If the determining 704 indicates that the network is congested, the modules determine 602 that the secure connection has failed. If, on the other hand, the determining 704 indicates that the network is not congested, the modules determine 706 whether the server of theservice provider network 106 is unreachable. If the determining 706 indicates that the server is unreachable, the modules determine 602 that the secure connection has failed. If, on the other hand, the determining 706 indicates that the server is reachable, the modules determine 708 that the secure connection remains in place. In various embodiments, upon makingdetermination 708, the modules of thehome router 102 repeat determining 702. -
FIG. 8 illustrates a component level view of anexample home router 102, in accordance with various embodiments. As shown, thehome router 102 includes amemory 802, the memory storing areporting module 804, aVPN client 806, aremote management client 808, amenu module 810, anSMS client 812, aregistration module 814, aninternetworking block 816, a retrymodule 818, anetwork status monitor 820, and other modules anddata 822. Thehome router 102 further includes processor(s) 824,interfaces 826, adisplay 828,transceivers 830,output devices 832,input devices 834, and adrive unit 836 including a machinereadable medium 838. - In various embodiments,
memory 802 generally includes both volatile memory and non-volatile memory (e.g., RAM, ROM, Flash Memory, miniature hard drive, memory card, or the like). Additionally, in some embodiments,memory 802 includes one or more SIM (subscriber identity module) cards, which are removable memory cards used to identify a user of thehome router 102 to theservice provider network 106. - In some embodiments, the
reporting module 804 is configured to gather performance metrics and create schemas and to provide those performance metrics and schemas as reports to theservice provider network 106. Techniques for generating and providing reports by thehome router 102 are shown inFIG. 2 and described above in detail with reference to that figure. - The
VPN client 806 is configured to request the establishment of thenetwork tunnel 108 between thehome router 102 and theservice provider network 106. Techniques for establishing and reestablishing thenetwork tunnel 108 by thehome router 102, which are shown inFIGS. 2 and 6 , are described above in greater detail. - In various embodiments, the
remote management client 808 is configured to enableremote management 110 of thehome router 102 by theservice provider network 106. Commands and data comprising theremote management 110 are received via thenetwork tunnel 108 and are applied by theremote management client 808 to repair, maintain, update and configure thehome router 102. Also, theremote management client 808 is configured to access settings and information about thehome router 102 and to transmit these settings and information to theservice provider network 106. Techniques for remotely managing 110 thehome router 102, which are shown inFIGS. 1 and 2 , are described above in greater detail. - The
menu module 810 is configured to provide theservice provider network 106 with access to a home router UI to enable troubleshooting, etc. Techniques for providing GUI access by thehome router 102, which are shown inFIG. 2 , are described above in greater detail. - In some embodiments, the
SMS client 812 is configured to receive SMS messages from theservice provider network 106 and to interpret the SMS messages to cause, for example, theVPN client 806 to request the establishment ofnetwork tunnel 108. Techniques for receiving and utilizing SMS messages are shown inFIGS. 2 and 6 and are described above in greater detail. - The
registration module 814 is configured to enableregistration 112 of adevice 114 that is locally connected or coupled to thehome router 102 with theservice provider network 106. Techniques for registering 112 adevice 114 by thehome router 102 are shown inFIG. 3 a and are described above in greater detail. - In various embodiments, the
internetworking block 816 shown inFIG. 8 is a component level view of theinternetworking block 400, which is shown inFIG. 4 and described above in detail with reference to that figure. - The retry
module 818 is configured to attempt to reestablish a secure connection when the secure connection fails. The retrymodule 818 performs the attempting based on a pre-determined time or one network conditions. Techniques for attempting to reestablish a secure connection are shown inFIG. 6 and are described further above in reference to that figure. - In some embodiments, the network status monitor 820 is configured to monitor network connectivity and congestion, as well as service provider network reachability. Techniques for determining network conditions and reachability by the
home router 102 are shown inFIGS. 6 and 7 and are described above in greater detail. - The other modules and
data 822 are configured to route voice and data communications between thedevices 114 of thehome network 104 and theservice provider network 106, as well as to performother home router 102 functions. - In some embodiments, the processor(s) 824 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or other processing unit or component known in the art.
- In various embodiments, the
interfaces 826 are any sort of interfaces known in the art.Interfaces 826 include any one or more of an Ethernet interface, wireless LAN interface, a near field interface, a DECT chipset, or an interface for an RJ-11 or RJ-45 port. The a wireless LAN interface can include a Wi-Fi interface or a Wi-Max interface, or a Bluetooth interface that performs the function of transmitting and receiving wireless communications using, for example, the IEEE 802.11, 802.16 and/or 802.20 standards. For instance, thehome router 102 can use a Wi-Fi interface to communicate directly with anearby device 114 of thehome network 104. The near field interface can include a Bluetooth® interface or RFID for transmitting and receiving near field radio communications via a near field antenna. For example, the near field interface may be used for functions, as is known in the art, such as communicating directly with nearby devices that are also, for instance, Bluetooth® or RFID enabled. A reader/interrogator may be incorporated intohome router 102.Interfaces 826 can also include theinterfaces 408 associated with theinternetworking block 816. - In various embodiments, the
display 828 is a liquid crystal display or any other type of display commonly used in telecommunication devices. For example,display 828 may be a touch-sensitive touch screen, and can then also act as an input device or keypad, such as for providing a soft-key keyboard, navigation buttons, or the like. - In some embodiments, the transceiver(s) 830 includes any sort of transceivers known in the art. For example, transceiver(s) 830 may include a radio transceiver and interface that performs the function of transmitting and receiving radio frequency communications via an antenna. The radio interface facilitates wireless connectivity between the
home router 102 and various cell towers, base stations and/or access points. - In some embodiments, the
output devices 832 include any sort of output devices known in the art, such as a display (already described as display 828), speakers, a vibrating mechanism, or a tactile feedback mechanism.Output devices 832 also include ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display. - In various embodiments,
input devices 834 include any sort of input devices known in the art. For example,input devices 834 may include a microphone, a keyboard/keypad, or a touch-sensitive display (such as the touch-sensitive display screen described above). A keyboard/keypad may be a push button numeric dialing pad (such as on a typical telecommunication device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons, or the like. - The machine readable medium 838 stores one or more sets of instructions (e.g., software) embodying any one or more of the methodologies or functions described herein. The instructions may also reside, completely or at least partially, within the
memory 802 and within theprocessor 824 during execution thereof by thehome router 102. Thememory 802 and theprocessor 824 also may constitute machinereadable media 838. -
FIG. 9 illustrates a component level view of anexample device 114 of thehome network 104, in accordance with various embodiments. As shown, thedevice 114 may include amemory 902, the memory storing aVPN client 904, aremote management client 906, aregistration module 908, anSMS client 910, aSIP client 912, a retrymodule 914, aconnectivity monitor 916, and other modules anddata 918. Thedevice 114 further includes processor(s) 920,interfaces 922, adisplay 924,transceivers 926,output devices 928,input devices 930, and driveunit 932 including a machinereadable medium 934. - In various embodiments,
memory 902 generally includes both volatile memory and non-volatile memory (e.g., RAM, ROM, Flash Memory, miniature hard drive, memory card, or the like). Additionally, in some embodiments,memory 902 includes a SIM (subscriber identity module) card, which is a removable memory card used to identify a user of thedevice 114 to theservice provider network 106. - In some embodiments, the
VPN client 904 is configured to request the establishment of thenetwork tunnel 108 between thedevice 114 and theservice provider network 106. Techniques for establishing and reestablishing thenetwork tunnel 108 by thedevice 114, which are shown inFIGS. 3 a-3 b and 6, are described above in greater detail. - The
remote management client 906 is configured to enableremote management 110 of thedevice 114 by theservice provider network 106. Commands and data comprising theremote management 110 are received via thehome router 102 andnetwork tunnel 108 and are applied by theremote management client 906 to repair, maintain, update and configure thedevice 114. Also, theremote management client 906 is configured to access settings and information about thedevice 114 and to provide those settings and information to thehome router 102 for transmission to theservice provider network 106. Techniques for remotely managing 110 thedevice 114, which are shown inFIGS. 1 and 2 , are described above in greater detail. - In various embodiments, the
registration module 908 is configured to formulate a network registration request and receive a network registration response, the response including a public identifier that is useable by thedevice 114 in voice and data communication. Techniques for registering 112 thedevice 112, which are shown inFIGS. 3 a-3 b, are described above in greater detail. - The
SMS client 910 is configured to receive SMS messages from theservice provider network 106 and to interpret and/or make available the SMS messages to cause, for example, theVPN client 904 to request the establishment ofnetwork tunnel 108. Techniques for receiving and utilizing SMS messages are shown inFIGS. 3 a-3 b and 6 and are described above in greater detail. - In some embodiments, the
SIP client 912 is configured to formulate the network registration request provided by theregistration module 908 as a SIP register request. Techniques for formulating a request as a SIP register request are shown inFIGS. 3 a-3 b and are described above in greater detail. - The retry
module 914 is configured to attempt to reestablish a secure connection when the secure connection fails. The retrymodule 914 performs the attempting based on a pre-determined time or one network conditions. Techniques for attempting to reestablish a secure connection are shown inFIG. 6 and are described further above in reference to that figure. - In various embodiments, the
connectivity module 916 is configured to determine network conditions and server reachability, as well as whether thedevice 114 is connected to or in the vicinity of thehome router 102. Techniques for determining conditions and connectivity are shown inFIGS. 3 a-3 b, 6, and 7 and are described above in greater detail. - The other modules and
data 918 are modules for enabling voice and data communications to and from thedevice 114 as well as other modules for any other number of device functions for telecommunications, media, and computing devices known in the art. - In some embodiments, the processor(s) 920 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or other processing unit or component known in the art.
- In various embodiments, the
interfaces 922 are any sort of interfaces known in the art.Interfaces 922 include any one or more of an Ethernet interface, wireless LAN interface, a near field interface, a DECT chipset, or an interface for an RJ-11 or RJ-45 port. The a wireless LAN interface can include a Wi-Fi interface or a Wi-Max interface, or a Bluetooth interface that performs the function of transmitting and receiving wireless communications using, for example, the IEEE 802.11, 802.16 and/or 802.20 standards. For instance, thedevice 114 can use a Wi-Fi interface to communicate directly with anearby home router 102 of thehome network 104. The near field interface can include a Bluetooth® interface or RFID for transmitting and receiving near field radio communications via a near field antenna. For example, the near field interface may be used for functions, as is known in the art, such as communicating directly with nearby devices that are also, for instance, Bluetooth® or RFID enabled. A reader/interrogator may be incorporated intodevice 114. - In various embodiments, the
display 924 is a liquid crystal display or any other type of display commonly used in telecommunication devices. For example,display 924 may be a touch-sensitive display screen, and can then also act as an input device or keypad, such as for providing a soft-key keyboard, navigation buttons, or the like. - In some embodiments, the
transceivers 926 include any sort of transceivers known in the art. For example,transceivers 926 may include a radio transceiver and interface that performs the function of transmitting and receiving radio frequency communications via an antenna. The radio interface facilitates wireless connectivity between thedevice 114 and various cell towers, base stations and/or access points. - In some embodiments, the
output devices 928 include any sort of output devices known in the art, such as a display (already described as display 924), speakers, a vibrating mechanism, or a tactile feedback mechanism.Output devices 928 also include ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display. - In various embodiments,
input devices 930 include any sort of input devices known in the art. For example,input devices 930 may include a microphone, a keyboard/keypad, or a touch-sensitive display (such as the touch-sensitive display screen described above). A keyboard/keypad may be a push button numeric dialing pad (such as on a typical telecommunication device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons, or the like. - The machine readable medium 934 stores one or more sets of instructions (e.g., software) embodying any one or more of the methodologies or functions described herein. The instructions may also reside, completely or at least partially, within the
memory 902 and within theprocessor 920 during execution thereof by thedevice 114. Thememory 902 and theprocessor 920 also may constitute machinereadable media 934. -
FIG. 10 illustrates a component level view of a server of theservice provider network 106, in accordance with various embodiments. While the server illustrated inFIG. 10 is shown asRMS 118, the component level view shown inFIG. 10 may also represent components of other servers of theservice provider network 106, such asSBC 116,SMSC 120,CSCF 122, andHSS 124. As illustrated,RMS 118 comprises asystem memory 1002 storing aVPN server 1004, anSMS server 1006, a remote management module 1008, and other modules anddata 1010. Also,RMS 118 includes processor(s) 1012, a removable storage 1014 and non-removable storage 1016, input device(s) 1018, output device(s) 1020 andcommunication connections 1022 for communicating withother computing devices 1024. - In various embodiments,
system memory 1002 is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. - The
VPN server 1004 is configured to establish anetwork tunnel 108 with another device, such as thehome router 102. Techniques for establishing and reestablishing thenetwork tunnel 108, which are shown inFIGS. 2 , 3 a-3 b, and 6, are described above in greater detail. Such techniques are performed by aVPN server 1004. In some embodiments, rather than forming a part of theRMS 118, theVPN server 1004 instead is a component of another device, such as a component of theSBC 116. - The
SMS server 1006 is configured to send an SMS message to another device, such as ahome router 102. Techniques for sending an SMS—and causing an SMS to be sent—are shown inFIGS. 2 and 6 and are described above in greater detail. Such techniques are performed by aSMS server 1006. In some embodiments, rather than forming a part of theRMS 118, theSMS server 1006 instead is a component of another device, such as a component of theSMSC 120. - In various embodiments, the
remote management module 1006 is configured to remotely manage 110 devices such as thehome router 102 anddevices 114. Techniques remotely managing 110 devices are shown inFIG. 2 and are described above in greater detail. Such techniques are performed by theremote management module 1006. - In some embodiments, other modules and data perform or enable performing any other action taken by the
service provider network 106. Such additional actions are shown inFIGS. 2 and 3 a-3 b and are described above in greater detail. - In some embodiments, the processor(s) 1012 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or other processing unit or component known in the art.
-
RMS 118 also includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated inFIG. 10 by removable storage 1014 and non-removable storage 1016. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.System memory 1002, removable storage 1014 and non-removable storage 1016 are all examples of computer-readable storage media. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed byRMS 118. Any such computer-readable storage media may be part ofRMS 118. - In various embodiment, any or all of
system memory 1002, removable storage 1014, and non-removable storage 1016, store programming instructions which, when executed, implement some or all of the above-described operations of theRMS 118. -
RMS 118 also has input device(s) 1018, such as a keyboard, a mouse, a touch-sensitive display, voice input device, etc., and output device(s) 1020 such as a display, speakers, a printer, etc. These devices are well known in the art and need not be discussed at length here. -
RMS 118 also containscommunication connections 1022 that allow theRMS 118 to communicate withother computing devices 1022, such as other servers of theservice provider network 106, including theSBC 116, theSMSC 120, theCSCF 122, and theHSS 124. - Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.
Claims (20)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/692,551 US20110122774A1 (en) | 2009-11-25 | 2010-01-22 | Time or Condition-Based Reestablishment of a Secure Connection |
PCT/US2010/057466 WO2011066196A2 (en) | 2009-11-25 | 2010-11-19 | Time or condition-based reestablishment of a secure connection |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US26462709P | 2009-11-25 | 2009-11-25 | |
US12/692,551 US20110122774A1 (en) | 2009-11-25 | 2010-01-22 | Time or Condition-Based Reestablishment of a Secure Connection |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110122774A1 true US20110122774A1 (en) | 2011-05-26 |
Family
ID=44062011
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/692,535 Active 2030-05-03 US8874741B2 (en) | 2009-11-25 | 2010-01-22 | Secured remote management of a home network |
US12/692,498 Abandoned US20110126095A1 (en) | 2009-11-25 | 2010-01-22 | Router Management via Touch-Sensitive Display |
US12/692,551 Abandoned US20110122774A1 (en) | 2009-11-25 | 2010-01-22 | Time or Condition-Based Reestablishment of a Secure Connection |
US12/692,509 Abandoned US20110122810A1 (en) | 2009-11-25 | 2010-01-22 | Router-Based Home Network Synchronization |
US12/692,541 Active 2030-07-28 US8346976B2 (en) | 2009-11-25 | 2010-01-22 | Secured registration of a home network device |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/692,535 Active 2030-05-03 US8874741B2 (en) | 2009-11-25 | 2010-01-22 | Secured remote management of a home network |
US12/692,498 Abandoned US20110126095A1 (en) | 2009-11-25 | 2010-01-22 | Router Management via Touch-Sensitive Display |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/692,509 Abandoned US20110122810A1 (en) | 2009-11-25 | 2010-01-22 | Router-Based Home Network Synchronization |
US12/692,541 Active 2030-07-28 US8346976B2 (en) | 2009-11-25 | 2010-01-22 | Secured registration of a home network device |
Country Status (3)
Country | Link |
---|---|
US (5) | US8874741B2 (en) |
EP (2) | EP2504965B1 (en) |
WO (5) | WO2011066153A2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090052675A1 (en) * | 2007-08-23 | 2009-02-26 | Barracuda Inc. | Secure remote support automation process |
US20110122810A1 (en) * | 2009-11-25 | 2011-05-26 | T-Mobile Usa, Inc. | Router-Based Home Network Synchronization |
CN102347950A (en) * | 2011-09-29 | 2012-02-08 | 中兴通讯股份有限公司 | Method and system for telecommunication network to provide session services for internet |
WO2014078639A1 (en) * | 2012-11-15 | 2014-05-22 | Cisco Technology, Inc. | Trigger message routing according to a service class |
CN105472645A (en) * | 2014-07-01 | 2016-04-06 | 北京奇虎科技有限公司 | Remote diagnosis method and remote diagnosis device for wireless router equipment |
US20160173450A1 (en) * | 2014-12-11 | 2016-06-16 | Bitdefender IPR Management Ltd. | Systems And Methods For Automatic Device Detection, Device Management, And Remote Assistance |
WO2016126491A1 (en) * | 2015-02-02 | 2016-08-11 | Eero, Inc. | Systems and methods for intuitive home networking |
WO2016193123A1 (en) * | 2015-06-01 | 2016-12-08 | Thomson Licensing | Network management infrastructure |
CN106487513A (en) * | 2015-09-01 | 2017-03-08 | 微软技术许可有限责任公司 | Remote router request relaying |
US9736019B2 (en) | 2015-05-14 | 2017-08-15 | Eero Inc. | Methods for dynamic router configuration in a mesh network |
AU2015361318B2 (en) * | 2014-12-11 | 2019-09-26 | Bitdefender Ipr Management Ltd | Systems and methods for automatic device detection, device management, and remote assistance |
WO2020035150A1 (en) * | 2018-08-17 | 2020-02-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of subscription profiles for a set of wireless devices |
EP3661147A4 (en) * | 2017-07-25 | 2020-07-08 | Cloudminds (Shenzhen) Robotics Systems Co., Ltd. | Control method, control apparatus and control system for intelligent device |
WO2021017919A1 (en) * | 2019-07-31 | 2021-02-04 | 中兴通讯股份有限公司 | Ota update diagnostic method and apparatus, wireless routing device, and terminal device |
Families Citing this family (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8069230B2 (en) * | 2007-10-31 | 2011-11-29 | Affinegy, Inc. | System and method of configuring a network |
US8542588B2 (en) * | 2008-06-25 | 2013-09-24 | Qualcomm Incorporated | Invoking different wireless link rate selection operations for different traffic classes |
US8601115B2 (en) * | 2010-06-26 | 2013-12-03 | Cisco Technology, Inc. | Providing state information and remote command execution in a managed media device |
US9894047B2 (en) * | 2010-09-09 | 2018-02-13 | Kaseya Limited | Method and apparatus of providing messaging service and callback feature to mobile stations |
US8832794B2 (en) * | 2010-10-20 | 2014-09-09 | Jeffry David Aronson | Single-point-of-access cyber system |
EP2464054A1 (en) * | 2010-12-07 | 2012-06-13 | British Telecommunications Public Limited Company | Communications device |
WO2012079648A1 (en) * | 2010-12-17 | 2012-06-21 | Telefonaktiebolaget L M Ericsson (Publ) | Enabling a communication server to use msc-s related functions |
US9219615B2 (en) * | 2011-01-28 | 2015-12-22 | Throughtek Co., Ltd. | Remote information communication system and linking method thereof |
US8612808B2 (en) | 2011-05-05 | 2013-12-17 | International Business Machines Corporation | Touch-sensitive user input device failure prediction |
US8954542B2 (en) * | 2011-06-14 | 2015-02-10 | Avaya Inc. | Method and system for transmitting and receiving configuration and registration information for session initiation protocol devices |
US9148381B2 (en) | 2011-10-21 | 2015-09-29 | Qualcomm Incorporated | Cloud computing enhanced gateway for communication networks |
US9116893B2 (en) | 2011-10-21 | 2015-08-25 | Qualcomm Incorporated | Network connected media gateway for communication networks |
US9559859B2 (en) * | 2012-01-05 | 2017-01-31 | Dell Products L.P. | Home hub |
US9641899B2 (en) * | 2012-03-06 | 2017-05-02 | Verizon Patent And Licensing Inc. | Social network creation and interaction |
US8799518B2 (en) * | 2012-04-04 | 2014-08-05 | Verisign, Inc. | Process for selecting an authoritative name server |
US9923787B2 (en) * | 2012-04-27 | 2018-03-20 | International Business Machines Corporation | Network configuration predictive analytics engine |
US9253621B2 (en) | 2012-05-18 | 2016-02-02 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for associating service provider network identifiers with access network identifiers |
US9451594B2 (en) | 2012-05-25 | 2016-09-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for associating service provider network identifiers with access network identifiers |
CN103476106B (en) * | 2012-06-06 | 2017-05-10 | 华为技术有限公司 | Terminal registration method, equipment and system |
US9779260B1 (en) | 2012-06-11 | 2017-10-03 | Dell Software Inc. | Aggregation and classification of secure data |
US9306810B2 (en) * | 2012-06-11 | 2016-04-05 | WiFiZapper, Inc. | WiFi zapper smart phone application |
US8464180B1 (en) * | 2012-06-15 | 2013-06-11 | Google Inc. | Organizing graphical representations on computing devices |
US9497567B2 (en) | 2012-06-22 | 2016-11-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Selection of M2M devices by external triggering |
US20140219164A1 (en) * | 2013-02-07 | 2014-08-07 | David Sanders | Hardware-Based Private Network Using WiMAX |
JP6171568B2 (en) * | 2013-05-28 | 2017-08-02 | 大日本印刷株式会社 | Network relay device |
JP5438236B1 (en) | 2013-06-06 | 2014-03-12 | パナソニック株式会社 | Cordless telephone equipment |
US20150089053A1 (en) * | 2013-09-25 | 2015-03-26 | RIFT.io Inc. | Dynamically scriptable ip traffic load balancing function |
FR3011418A1 (en) * | 2013-09-30 | 2015-04-03 | Orange | TECHNIQUE FOR REMOTE ADMINISTRATION OF A DEVICE BELONGING TO A PRIVATE NETWORK |
US10033723B2 (en) | 2013-12-18 | 2018-07-24 | At&T Intellectual Property I, L.P. | Methods, devices, and computer readable storage devices for authenticating devices having non-SIM based clients |
US9515875B2 (en) * | 2014-03-14 | 2016-12-06 | Cisco Technology, Inc. | Zero touch deployment of multi-tenant services in a home network environment |
US20150358399A1 (en) * | 2014-06-09 | 2015-12-10 | Cisco Technology, Inc. | Provisioning and managing slices of a consumer premises equipment device |
GB2533348B (en) * | 2014-12-17 | 2021-07-07 | Arm Ip Ltd | Management of relationships between a device and a service provider |
US9743299B2 (en) * | 2014-12-22 | 2017-08-22 | International Business Machines Corporation | Network performance testing in non-homogeneous networks |
US10326748B1 (en) | 2015-02-25 | 2019-06-18 | Quest Software Inc. | Systems and methods for event-based authentication |
US9769646B2 (en) * | 2015-02-26 | 2017-09-19 | T-Mobile Usa, Inc. | Realm translation in an IMS network |
US10417613B1 (en) | 2015-03-17 | 2019-09-17 | Quest Software Inc. | Systems and methods of patternizing logged user-initiated events for scheduling functions |
US10496974B2 (en) * | 2015-03-25 | 2019-12-03 | Intel Corporation | Secure transactions with connected peripherals |
US9842220B1 (en) | 2015-04-10 | 2017-12-12 | Dell Software Inc. | Systems and methods of secure self-service access to content |
JP6590276B2 (en) * | 2015-07-15 | 2019-10-16 | パナソニックIpマネジメント株式会社 | Communication device |
US10536352B1 (en) | 2015-08-05 | 2020-01-14 | Quest Software Inc. | Systems and methods for tuning cross-platform data collection |
US10157358B1 (en) | 2015-10-05 | 2018-12-18 | Quest Software Inc. | Systems and methods for multi-stream performance patternization and interval-based prediction |
US10218588B1 (en) | 2015-10-05 | 2019-02-26 | Quest Software Inc. | Systems and methods for multi-stream performance patternization and optimization of virtual meetings |
US20180146352A1 (en) * | 2016-11-22 | 2018-05-24 | Tracfone Wireless, Inc. | Wireless Replacement Line also Known as a Wireless Home Phone Configured for Receiving Wireless Emergency Alerts |
US11057732B2 (en) * | 2015-11-23 | 2021-07-06 | Tracfone Wireless, Inc. | Wireless home phone configured for receiving emergency alerts |
US11570609B2 (en) | 2015-11-23 | 2023-01-31 | Tracfone Wireless, Inc. | Wireless replacement line also known as a wireless home phone configured for receiving wireless emergency alerts |
US10212167B2 (en) * | 2016-02-27 | 2019-02-19 | Gryphon Online Safety, Inc. | Method and system to enable controlled safe internet browsing |
US11405399B2 (en) * | 2016-02-27 | 2022-08-02 | Gryphon Online Safety Inc. | Method of protecting mobile devices from vulnerabilities like malware, enabling content filtering, screen time restrictions and other parental control rules while on public network by forwarding the internet traffic to a smart, secured home router |
US11743264B2 (en) * | 2016-02-27 | 2023-08-29 | Gryphon Online Safety Inc. | Method of protecting mobile devices from vulnerabilities like malware, enabling content filtering, screen time restrictions and other parental control rules while on public network by forwarding the internet traffic to a smart, secured home router |
US10142391B1 (en) * | 2016-03-25 | 2018-11-27 | Quest Software Inc. | Systems and methods of diagnosing down-layer performance problems via multi-stream performance patternization |
US10038793B2 (en) * | 2016-04-06 | 2018-07-31 | T-Mobile Usa, Inc. | VoIP adapter for connecting landline phones to IP routers |
US10630507B2 (en) * | 2016-11-29 | 2020-04-21 | Ale International | System for and method of establishing a connection between a first electronic device and a second electronic device |
US20180248759A1 (en) * | 2017-02-27 | 2018-08-30 | Alcatel-Lucent Usa Inc. | Troubleshooting in remote management services |
US10505787B2 (en) | 2017-02-27 | 2019-12-10 | Nokia Of America Corporation | Automatic recovery in remote management services |
BR112020010007A2 (en) * | 2017-11-21 | 2020-11-03 | Telefonaktiebolaget Lm Ericsson (Publ) | device for establishing communication and method performed by wireless device |
US10812445B2 (en) * | 2018-02-13 | 2020-10-20 | Sling Media Pvt Ltd | Cloud access to local network addresses |
WO2020002159A1 (en) | 2018-06-25 | 2020-01-02 | British Telecommunications Public Limited Company | Processing local area network diagnostic data |
US11196649B2 (en) * | 2018-06-25 | 2021-12-07 | British Telecommunications Public Limited Company | Processing local area network diagnostic data |
EP4038840A1 (en) | 2019-09-30 | 2022-08-10 | British Telecommunications public limited company | Processing local area network diagnostic data |
US11477643B2 (en) * | 2020-02-12 | 2022-10-18 | Charter Communications Operating, Llc | Systems and methods for access point device recovery using mobile devices |
US11526825B2 (en) * | 2020-07-27 | 2022-12-13 | Cygnvs Inc. | Cloud-based multi-tenancy computing systems and methods for providing response control and analytics |
US12041062B2 (en) | 2021-09-15 | 2024-07-16 | Cygnvs Inc. | Systems for securely tracking incident data and automatically generating data incident reports using collaboration rooms with dynamic tenancy |
US11477208B1 (en) | 2021-09-15 | 2022-10-18 | Cygnvs Inc. | Systems and methods for providing collaboration rooms with dynamic tenancy and role-based security |
US11354430B1 (en) | 2021-09-16 | 2022-06-07 | Cygnvs Inc. | Systems and methods for dynamically establishing and managing tenancy using templates |
US20230171620A1 (en) * | 2021-11-26 | 2023-06-01 | Dish Network, L.L.C. | Enhanced network reliability and/or boosted network speed |
US20230376375A1 (en) * | 2022-05-21 | 2023-11-23 | Jpmorgan Chase Bank, N.A. | Method and system for automatically identifying and resolving errors in log file |
Citations (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4475806A (en) * | 1982-09-21 | 1984-10-09 | Xerox Corporation | Copier display panel |
US5555077A (en) * | 1994-12-01 | 1996-09-10 | Xerox Corporation | Printer having an active user interface feature |
US6052725A (en) * | 1998-07-02 | 2000-04-18 | Lucent Technologies, Inc. | Non-local dynamic internet protocol addressing system and method |
US20010010516A1 (en) * | 2000-02-01 | 2001-08-02 | Roh Young Hoon | Internet refrigerator and operating method thereof |
US6310634B1 (en) * | 1997-08-04 | 2001-10-30 | Starfish Software, Inc. | User interface methodology supporting light data entry for microprocessor device having limited user input |
US6366302B1 (en) * | 1998-12-22 | 2002-04-02 | Motorola, Inc. | Enhanced graphic user interface for mobile radiotelephones |
US20020131402A1 (en) * | 2001-03-16 | 2002-09-19 | Gordon Lee | Registering an IP phone with an IP phone switch |
US20030088698A1 (en) * | 2001-11-06 | 2003-05-08 | Inderpreet Singh | VPN failure recovery |
US20030101459A1 (en) * | 1999-08-03 | 2003-05-29 | Ucentric Holdings, Llc | Multi-service in-home network with an open interface |
US6598183B1 (en) * | 2000-01-04 | 2003-07-22 | Cisco Systems, Inc. | Software tool for automated diagnosis and resolution of problems of voice, data and VoIP communications networks |
US6633571B1 (en) * | 1999-05-27 | 2003-10-14 | Hitachi, Ltd. | VPN composing method, interwork router, packet communication method, data communication apparatus, and packet relaying apparatus |
US6671729B1 (en) * | 2000-04-13 | 2003-12-30 | Lockheed Martin Corporation | Autonomously established secure and persistent internet connection and autonomously reestablished without user intervention that connection if it lost |
US6675208B1 (en) * | 1997-10-14 | 2004-01-06 | Lucent Technologies Inc. | Registration scheme for network |
US6680922B1 (en) * | 1998-07-10 | 2004-01-20 | Malibu Networks, Inc. | Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system |
US20040034702A1 (en) * | 2002-08-16 | 2004-02-19 | Nortel Networks Limited | Method and apparatus for exchanging intra-domain routing information between VPN sites |
US6704282B1 (en) * | 1999-06-30 | 2004-03-09 | 3Com Corporation | VPN tunnel redirection |
US20040052045A1 (en) * | 2002-09-16 | 2004-03-18 | Robert Botchek | Hard disk storage device incorporating dedicated user interface |
US6754844B1 (en) * | 2000-10-31 | 2004-06-22 | Intel Corporation | Diagnostic configuration management of embedded network devices |
US20040142711A1 (en) * | 2002-09-11 | 2004-07-22 | Nokia Corporation | Method, device and system for automated synchronization between terminals |
US6773396B2 (en) * | 1995-11-13 | 2004-08-10 | Ge Medical Systems Information Technologies, Inc. | Cellular architecture and data transfer methods for real time patient monitoring within medical facilities |
US6778498B2 (en) * | 2001-03-20 | 2004-08-17 | Mci, Inc. | Virtual private network (VPN)-aware customer premises equipment (CPE) edge router |
US6810263B1 (en) * | 1999-12-22 | 2004-10-26 | Denso Corporation | Packet data reconnection timing control in mobile communication systems |
US20040255192A1 (en) * | 2003-01-30 | 2004-12-16 | Hiroyuki Watanabe | Information processing apparatus and network connection diagnostic method used in the same apparatus |
US20050044235A1 (en) * | 2003-07-30 | 2005-02-24 | Balahura Robert Eugene | System, computer product and method for enabling wireless data synchronization |
US20050071183A1 (en) * | 2003-09-29 | 2005-03-31 | Fujitsu Limited | Registration management apparatus and registration management program |
US6886060B2 (en) * | 2003-03-21 | 2005-04-26 | Industrial Technology Research Institute | Computer system for integrating car electronic devices |
US20050114534A1 (en) * | 2003-11-25 | 2005-05-26 | Aaron Lee | Apparatus, method and system for providing automated services to heterogenous devices across multiple platforms |
US20050114500A1 (en) * | 2003-11-24 | 2005-05-26 | Monk John M. | Graphical user interface for adding measurements to existing distributed network troubleshooting system |
US20050232284A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Providing automatic format conversion via an access gateway in a home |
US20050233743A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Digital personal assistance via a broadband access gateway |
US20050281577A1 (en) * | 2004-06-17 | 2005-12-22 | Kyocera Mita Corporation | Display control device for touch panel-type setting-operation unit, electronic apparatus and image forming apparatus |
US20060101515A1 (en) * | 2004-08-19 | 2006-05-11 | Edward Amoroso | System and method for monitoring network traffic |
US20060230446A1 (en) * | 2005-04-06 | 2006-10-12 | Vu Lan N | Hybrid SSL/IPSec network management system |
US20060230183A1 (en) * | 2005-04-07 | 2006-10-12 | Samsung Electronics Co., Ltd. | Method and apparatus for synchronizing content with a collection of home devices |
US20060236388A1 (en) * | 2005-04-14 | 2006-10-19 | Sbc Knowledge Ventures, L.P. | Method and apparatus for voice over internet protocol telephony using a virtual private network |
US7136709B2 (en) * | 2003-11-04 | 2006-11-14 | Universal Electronics Inc. | Home appliance control system and methods in a networked environment |
US20060262935A1 (en) * | 2005-05-17 | 2006-11-23 | Stuart Goose | System and method for creating personalized sound zones |
US20060260752A1 (en) * | 2005-05-23 | 2006-11-23 | Ward/Kraft | System and method for producing small production runs of products having removable coatings |
US7149792B1 (en) * | 2000-11-20 | 2006-12-12 | Axeda Corporation | Device registration mechanism |
US7151780B1 (en) * | 2002-03-06 | 2006-12-19 | Cisco Technology, Inc. | Arrangement for automated teller machine communications based on bisync to IP conversion |
US7155305B2 (en) * | 2003-11-04 | 2006-12-26 | Universal Electronics Inc. | System and methods for home appliance identification and control in a networked environment |
US20070050673A1 (en) * | 2005-08-26 | 2007-03-01 | Dibartolomeo Jeffrey A | Dynamic system diagnosis |
US7188002B2 (en) * | 2004-01-08 | 2007-03-06 | Maple Chase Company | Appliance diagnostic display apparatus and network incorporating same |
US20070078941A1 (en) * | 2005-08-15 | 2007-04-05 | Microsoft Corporation | Partial item change tracking and synchronization |
US7209479B2 (en) * | 2001-01-18 | 2007-04-24 | Science Application International Corp. | Third party VPN certification |
US20070105548A1 (en) * | 2003-11-13 | 2007-05-10 | Thomason Licensing S.A. | Integrated cellular/pcs-pots communication system |
US20070113275A1 (en) * | 2005-11-15 | 2007-05-17 | Nortel Networks Limited | IP security with seamless roaming and load balancing |
US7252230B1 (en) * | 2005-05-09 | 2007-08-07 | Cisco Technology, Inc. | Method and apparatus for real-time tracking of inventory using active RFID technology |
US20070186180A1 (en) * | 2005-12-30 | 2007-08-09 | Barrett Morgan | Ubiquitous navbar user interface across multiple heterogeneous digital media devices |
US7257741B1 (en) * | 2003-01-28 | 2007-08-14 | At&T Intellectual Property, Inc. | Methods and systems for communications device troubleshooting |
US20070191057A1 (en) * | 2004-03-04 | 2007-08-16 | Access Co., Ltd | Wireless communication terminal synchronization method, wireless communication system, wireless communication terminal, and server |
US20070199066A1 (en) * | 2005-02-14 | 2007-08-23 | Smith Robert D | Systems and methods for automatically configuring network devices |
US20070195805A1 (en) * | 2004-10-27 | 2007-08-23 | Telefonaktiebolaget Lm Ericsson (Publ) | IP multimedia subsystem access method and apparatus |
US20070210101A1 (en) * | 2003-02-04 | 2007-09-13 | Reckitt Benckiser (Uk) Limited | Vapour Dispensing Device |
US20070218912A1 (en) * | 2006-03-20 | 2007-09-20 | Samsung Electronics Co., Ltd. | Method and system for mobile secure socket layer in virtual private networks |
US20070237159A1 (en) * | 2006-04-10 | 2007-10-11 | Mariko Yamada | Communication equipment |
US20070250761A1 (en) * | 2004-06-04 | 2007-10-25 | Bob Bradley | System and method for synchronizing media presentation at multiple recipients |
US20070260751A1 (en) * | 2006-03-28 | 2007-11-08 | Scott Meesseman | System and method for synchronizing personal data among a plurality of devices storing such data |
US20070266107A1 (en) * | 2001-08-07 | 2007-11-15 | John Friend | System and method for full wireless synchronization of a data processing apparatus with a data service |
US20070271606A1 (en) * | 2006-05-17 | 2007-11-22 | Amann Keith R | Apparatus and method for establishing a VPN tunnel between a wireless device and a LAN |
US20070271532A1 (en) * | 2006-05-19 | 2007-11-22 | Nguyen Loc V | Method and apparatus for displaying layered user interface |
US20070280247A1 (en) * | 2006-03-13 | 2007-12-06 | Kabushiki Kaisha Toshiba | Method and apparatus for detecting VPN communication |
US20080005791A1 (en) * | 2006-06-30 | 2008-01-03 | Ajay Gupta | Method and apparatus for supporting a virtual private network architecture on a partitioned platform |
US20080022377A1 (en) * | 2006-07-21 | 2008-01-24 | Kai Chen | Device Authentication |
US20080028225A1 (en) * | 2006-07-26 | 2008-01-31 | Toerless Eckert | Authorizing physical access-links for secure network connections |
US20080043640A1 (en) * | 2005-02-14 | 2008-02-21 | Smith Robert D | Systems and Methods for Automatically Reconfiguring Virtual Private Networks |
US20080076425A1 (en) * | 2006-09-22 | 2008-03-27 | Amit Khetawat | Method and apparatus for resource management |
US20080133775A1 (en) * | 2006-11-30 | 2008-06-05 | Intellisync Corporation | Method, Apparatus and Computer Program Product for Providing Intelligent Synchronization |
US20080216167A1 (en) * | 2007-03-03 | 2008-09-04 | Kddi Corporation | Proxy connection method and adapter to ims/mmd network |
US20080254807A1 (en) * | 2005-11-15 | 2008-10-16 | Alcatel Lucent | Access Network, Gateway and Management Server For a Cellular Wireless Communication System |
US20080311959A1 (en) * | 2007-06-15 | 2008-12-18 | D-Link Corporation | Network device with display module |
US20090029676A1 (en) * | 2007-02-12 | 2009-01-29 | Guru Thalapaneni | Systems and methods for managing information in mobile devices |
US20090131018A1 (en) * | 2007-06-21 | 2009-05-21 | Airwalk Communications, Inc. | System, method, and computer-readable medium for user equipment registration and authentication processing by a femtocell system |
US20090143052A1 (en) * | 2007-11-29 | 2009-06-04 | Michael Bates | Systems and methods for personal information management and contact picture synchronization and distribution |
US20090156213A1 (en) * | 2007-10-25 | 2009-06-18 | Spinelli Vincent | Interworking gateway for mobile nodes |
US20090157732A1 (en) * | 2007-12-13 | 2009-06-18 | Verizon Data Services Llc | Networked address book |
US20090193469A1 (en) * | 2006-03-07 | 2009-07-30 | Tatsuya Igarashi | Information processing apparatus and information processing method, and computer program |
US20090237573A1 (en) * | 2007-11-16 | 2009-09-24 | Audiovox Corporation | Remote control and method of using same for controlling entertainment equipment |
US20090282470A1 (en) * | 2008-05-06 | 2009-11-12 | Cisco Technology, Inc. | Content aggregation server on virtual universal plug-n-play network |
US20090327354A1 (en) * | 2008-06-26 | 2009-12-31 | Microsoft Corporation | Notification and synchronization of updated data |
US20100014518A1 (en) * | 1997-10-03 | 2010-01-21 | Alcatel-Lucent Canada Inc. | Method and apparatus for forwarding packets |
US7675537B2 (en) * | 2006-03-31 | 2010-03-09 | Polycom, Inc. | System, method, and apparatus for extending wireless personal area networks using conferencing connection |
US20100082759A1 (en) * | 2008-09-30 | 2010-04-01 | Microsoft Corporation | Communications grouped as conversations |
US20100180206A1 (en) * | 2009-01-15 | 2010-07-15 | NexAira, Inc. | Systems and methods for iconic graphical user interface and embedded device manager |
US20100217837A1 (en) * | 2006-12-29 | 2010-08-26 | Prodea Systems , Inc. | Multi-services application gateway and system employing the same |
US20100273534A1 (en) * | 2007-12-21 | 2010-10-28 | Ström Jacob | Portable Electronic Apparatus, and a Method of Controlling a User Interface Thereof |
US20100312759A1 (en) * | 2009-06-05 | 2010-12-09 | Karl Martin Groethe | Throttling to reduce synchronizations of excessively changing data |
US7853560B1 (en) * | 2007-04-16 | 2010-12-14 | Cellco Partnership | Methods for address book synchronization and subscription status notification |
US20110199338A1 (en) * | 2008-09-10 | 2011-08-18 | Kim Hyun Kyu | Touch screen apparatus and method for inputting user information on a screen through context awareness |
US8019067B2 (en) * | 2006-03-07 | 2011-09-13 | Microsoft Corporation | User interface for telephone system administration |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6141341A (en) * | 1998-09-09 | 2000-10-31 | Motorola, Inc. | Voice over internet protocol telephone system and method |
US7142560B2 (en) | 2001-08-14 | 2006-11-28 | Sharp Laboratories Of America, Inc. | System and method for virtual multiline telephony in a home-network telephone |
US7363045B2 (en) | 2003-01-03 | 2008-04-22 | Vtech Telecommunications Limited | Systems and methods for exchanging data and audio between cellular telephones and landline telephones |
US7142852B2 (en) | 2003-11-13 | 2006-11-28 | Motorola, Inc. | Method and gateway for controlling call routing |
US7403544B2 (en) | 2004-06-04 | 2008-07-22 | Broadcom Corporation | VoIP WLAN conference calling via home wireless routers |
KR100714100B1 (en) | 2004-10-29 | 2007-05-02 | 한국전자통신연구원 | Method and system for user authentication in home network system |
KR20060039825A (en) | 2004-11-03 | 2006-05-09 | (주)알피에이네트웍스 | Apparatus of gateway for home network systems |
US7215258B2 (en) * | 2005-02-22 | 2007-05-08 | Research In Motion Limited | Handheld electronic device having reduced keyboard and multiple password access, and associated methods |
US20070178843A1 (en) * | 2006-02-01 | 2007-08-02 | Fmr Corp. | Automated testing of a handheld device over a network |
KR20090011502A (en) | 2007-07-26 | 2009-02-02 | 엘지전자 주식회사 | Portable terminal and method for controlling the same |
US20090059907A1 (en) * | 2007-08-30 | 2009-03-05 | Texas Instruments Incorporated | System, method and device for docking station for communication device |
KR100901967B1 (en) | 2007-12-24 | 2009-06-10 | 에스케이 텔레콤주식회사 | System and method for synchonizing contents, server applied to the same |
US20100223096A1 (en) * | 2009-02-27 | 2010-09-02 | Sorel Bosan | Subsidized Mobile Device Usage |
US8693466B2 (en) * | 2009-04-08 | 2014-04-08 | Apple Inc. | Apparatus and methods for bridging calls or data between heterogeneous network domains |
US8874741B2 (en) * | 2009-11-25 | 2014-10-28 | T-Mobile Usa, Inc. | Secured remote management of a home network |
-
2010
- 2010-01-22 US US12/692,535 patent/US8874741B2/en active Active
- 2010-01-22 US US12/692,498 patent/US20110126095A1/en not_active Abandoned
- 2010-01-22 US US12/692,551 patent/US20110122774A1/en not_active Abandoned
- 2010-01-22 US US12/692,509 patent/US20110122810A1/en not_active Abandoned
- 2010-01-22 US US12/692,541 patent/US8346976B2/en active Active
- 2010-11-17 WO PCT/US2010/057086 patent/WO2011066153A2/en active Application Filing
- 2010-11-19 WO PCT/US2010/057343 patent/WO2011066180A2/en active Application Filing
- 2010-11-19 WO PCT/US2010/057466 patent/WO2011066196A2/en active Application Filing
- 2010-11-19 WO PCT/US2010/057348 patent/WO2011066181A2/en active Application Filing
- 2010-11-19 EP EP10833799.9A patent/EP2504965B1/en active Active
- 2010-11-19 WO PCT/US2010/057473 patent/WO2011066197A2/en active Application Filing
- 2010-11-19 EP EP10833798.1A patent/EP2504964B1/en active Active
Patent Citations (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4475806A (en) * | 1982-09-21 | 1984-10-09 | Xerox Corporation | Copier display panel |
US5555077A (en) * | 1994-12-01 | 1996-09-10 | Xerox Corporation | Printer having an active user interface feature |
US6773396B2 (en) * | 1995-11-13 | 2004-08-10 | Ge Medical Systems Information Technologies, Inc. | Cellular architecture and data transfer methods for real time patient monitoring within medical facilities |
US6310634B1 (en) * | 1997-08-04 | 2001-10-30 | Starfish Software, Inc. | User interface methodology supporting light data entry for microprocessor device having limited user input |
US20100014518A1 (en) * | 1997-10-03 | 2010-01-21 | Alcatel-Lucent Canada Inc. | Method and apparatus for forwarding packets |
US6675208B1 (en) * | 1997-10-14 | 2004-01-06 | Lucent Technologies Inc. | Registration scheme for network |
US6052725A (en) * | 1998-07-02 | 2000-04-18 | Lucent Technologies, Inc. | Non-local dynamic internet protocol addressing system and method |
US6680922B1 (en) * | 1998-07-10 | 2004-01-20 | Malibu Networks, Inc. | Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system |
US6366302B1 (en) * | 1998-12-22 | 2002-04-02 | Motorola, Inc. | Enhanced graphic user interface for mobile radiotelephones |
US6633571B1 (en) * | 1999-05-27 | 2003-10-14 | Hitachi, Ltd. | VPN composing method, interwork router, packet communication method, data communication apparatus, and packet relaying apparatus |
US6704282B1 (en) * | 1999-06-30 | 2004-03-09 | 3Com Corporation | VPN tunnel redirection |
US20030101459A1 (en) * | 1999-08-03 | 2003-05-29 | Ucentric Holdings, Llc | Multi-service in-home network with an open interface |
US6810263B1 (en) * | 1999-12-22 | 2004-10-26 | Denso Corporation | Packet data reconnection timing control in mobile communication systems |
US6598183B1 (en) * | 2000-01-04 | 2003-07-22 | Cisco Systems, Inc. | Software tool for automated diagnosis and resolution of problems of voice, data and VoIP communications networks |
US20010010516A1 (en) * | 2000-02-01 | 2001-08-02 | Roh Young Hoon | Internet refrigerator and operating method thereof |
US6671729B1 (en) * | 2000-04-13 | 2003-12-30 | Lockheed Martin Corporation | Autonomously established secure and persistent internet connection and autonomously reestablished without user intervention that connection if it lost |
US6754844B1 (en) * | 2000-10-31 | 2004-06-22 | Intel Corporation | Diagnostic configuration management of embedded network devices |
US7149792B1 (en) * | 2000-11-20 | 2006-12-12 | Axeda Corporation | Device registration mechanism |
US7209479B2 (en) * | 2001-01-18 | 2007-04-24 | Science Application International Corp. | Third party VPN certification |
US20020131402A1 (en) * | 2001-03-16 | 2002-09-19 | Gordon Lee | Registering an IP phone with an IP phone switch |
US6778498B2 (en) * | 2001-03-20 | 2004-08-17 | Mci, Inc. | Virtual private network (VPN)-aware customer premises equipment (CPE) edge router |
US20070266107A1 (en) * | 2001-08-07 | 2007-11-15 | John Friend | System and method for full wireless synchronization of a data processing apparatus with a data service |
US20030088698A1 (en) * | 2001-11-06 | 2003-05-08 | Inderpreet Singh | VPN failure recovery |
US7151780B1 (en) * | 2002-03-06 | 2006-12-19 | Cisco Technology, Inc. | Arrangement for automated teller machine communications based on bisync to IP conversion |
US20040034702A1 (en) * | 2002-08-16 | 2004-02-19 | Nortel Networks Limited | Method and apparatus for exchanging intra-domain routing information between VPN sites |
US20040142711A1 (en) * | 2002-09-11 | 2004-07-22 | Nokia Corporation | Method, device and system for automated synchronization between terminals |
US20040052045A1 (en) * | 2002-09-16 | 2004-03-18 | Robert Botchek | Hard disk storage device incorporating dedicated user interface |
US7257741B1 (en) * | 2003-01-28 | 2007-08-14 | At&T Intellectual Property, Inc. | Methods and systems for communications device troubleshooting |
US20040255192A1 (en) * | 2003-01-30 | 2004-12-16 | Hiroyuki Watanabe | Information processing apparatus and network connection diagnostic method used in the same apparatus |
US20070210101A1 (en) * | 2003-02-04 | 2007-09-13 | Reckitt Benckiser (Uk) Limited | Vapour Dispensing Device |
US6886060B2 (en) * | 2003-03-21 | 2005-04-26 | Industrial Technology Research Institute | Computer system for integrating car electronic devices |
US20050044235A1 (en) * | 2003-07-30 | 2005-02-24 | Balahura Robert Eugene | System, computer product and method for enabling wireless data synchronization |
US20050071183A1 (en) * | 2003-09-29 | 2005-03-31 | Fujitsu Limited | Registration management apparatus and registration management program |
US7155305B2 (en) * | 2003-11-04 | 2006-12-26 | Universal Electronics Inc. | System and methods for home appliance identification and control in a networked environment |
US7136709B2 (en) * | 2003-11-04 | 2006-11-14 | Universal Electronics Inc. | Home appliance control system and methods in a networked environment |
US20070105548A1 (en) * | 2003-11-13 | 2007-05-10 | Thomason Licensing S.A. | Integrated cellular/pcs-pots communication system |
US20050114500A1 (en) * | 2003-11-24 | 2005-05-26 | Monk John M. | Graphical user interface for adding measurements to existing distributed network troubleshooting system |
US20050114534A1 (en) * | 2003-11-25 | 2005-05-26 | Aaron Lee | Apparatus, method and system for providing automated services to heterogenous devices across multiple platforms |
US7188002B2 (en) * | 2004-01-08 | 2007-03-06 | Maple Chase Company | Appliance diagnostic display apparatus and network incorporating same |
US20070191057A1 (en) * | 2004-03-04 | 2007-08-16 | Access Co., Ltd | Wireless communication terminal synchronization method, wireless communication system, wireless communication terminal, and server |
US20050232284A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Providing automatic format conversion via an access gateway in a home |
US20050233743A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Digital personal assistance via a broadband access gateway |
US20070250761A1 (en) * | 2004-06-04 | 2007-10-25 | Bob Bradley | System and method for synchronizing media presentation at multiple recipients |
US20050281577A1 (en) * | 2004-06-17 | 2005-12-22 | Kyocera Mita Corporation | Display control device for touch panel-type setting-operation unit, electronic apparatus and image forming apparatus |
US20060101515A1 (en) * | 2004-08-19 | 2006-05-11 | Edward Amoroso | System and method for monitoring network traffic |
US20070195805A1 (en) * | 2004-10-27 | 2007-08-23 | Telefonaktiebolaget Lm Ericsson (Publ) | IP multimedia subsystem access method and apparatus |
US20070199066A1 (en) * | 2005-02-14 | 2007-08-23 | Smith Robert D | Systems and methods for automatically configuring network devices |
US20080043640A1 (en) * | 2005-02-14 | 2008-02-21 | Smith Robert D | Systems and Methods for Automatically Reconfiguring Virtual Private Networks |
US20060230446A1 (en) * | 2005-04-06 | 2006-10-12 | Vu Lan N | Hybrid SSL/IPSec network management system |
US20060230183A1 (en) * | 2005-04-07 | 2006-10-12 | Samsung Electronics Co., Ltd. | Method and apparatus for synchronizing content with a collection of home devices |
US20060236388A1 (en) * | 2005-04-14 | 2006-10-19 | Sbc Knowledge Ventures, L.P. | Method and apparatus for voice over internet protocol telephony using a virtual private network |
US7252230B1 (en) * | 2005-05-09 | 2007-08-07 | Cisco Technology, Inc. | Method and apparatus for real-time tracking of inventory using active RFID technology |
US20060262935A1 (en) * | 2005-05-17 | 2006-11-23 | Stuart Goose | System and method for creating personalized sound zones |
US20060260752A1 (en) * | 2005-05-23 | 2006-11-23 | Ward/Kraft | System and method for producing small production runs of products having removable coatings |
US20070078941A1 (en) * | 2005-08-15 | 2007-04-05 | Microsoft Corporation | Partial item change tracking and synchronization |
US20070050673A1 (en) * | 2005-08-26 | 2007-03-01 | Dibartolomeo Jeffrey A | Dynamic system diagnosis |
US20070113275A1 (en) * | 2005-11-15 | 2007-05-17 | Nortel Networks Limited | IP security with seamless roaming and load balancing |
US20080254807A1 (en) * | 2005-11-15 | 2008-10-16 | Alcatel Lucent | Access Network, Gateway and Management Server For a Cellular Wireless Communication System |
US20070186180A1 (en) * | 2005-12-30 | 2007-08-09 | Barrett Morgan | Ubiquitous navbar user interface across multiple heterogeneous digital media devices |
US8019067B2 (en) * | 2006-03-07 | 2011-09-13 | Microsoft Corporation | User interface for telephone system administration |
US20090193469A1 (en) * | 2006-03-07 | 2009-07-30 | Tatsuya Igarashi | Information processing apparatus and information processing method, and computer program |
US20070280247A1 (en) * | 2006-03-13 | 2007-12-06 | Kabushiki Kaisha Toshiba | Method and apparatus for detecting VPN communication |
US20070218912A1 (en) * | 2006-03-20 | 2007-09-20 | Samsung Electronics Co., Ltd. | Method and system for mobile secure socket layer in virtual private networks |
US20070260751A1 (en) * | 2006-03-28 | 2007-11-08 | Scott Meesseman | System and method for synchronizing personal data among a plurality of devices storing such data |
US7675537B2 (en) * | 2006-03-31 | 2010-03-09 | Polycom, Inc. | System, method, and apparatus for extending wireless personal area networks using conferencing connection |
US20070237159A1 (en) * | 2006-04-10 | 2007-10-11 | Mariko Yamada | Communication equipment |
US20070271606A1 (en) * | 2006-05-17 | 2007-11-22 | Amann Keith R | Apparatus and method for establishing a VPN tunnel between a wireless device and a LAN |
US20070271532A1 (en) * | 2006-05-19 | 2007-11-22 | Nguyen Loc V | Method and apparatus for displaying layered user interface |
US20080005791A1 (en) * | 2006-06-30 | 2008-01-03 | Ajay Gupta | Method and apparatus for supporting a virtual private network architecture on a partitioned platform |
US20080022377A1 (en) * | 2006-07-21 | 2008-01-24 | Kai Chen | Device Authentication |
US20080028225A1 (en) * | 2006-07-26 | 2008-01-31 | Toerless Eckert | Authorizing physical access-links for secure network connections |
US20080076425A1 (en) * | 2006-09-22 | 2008-03-27 | Amit Khetawat | Method and apparatus for resource management |
US20080133775A1 (en) * | 2006-11-30 | 2008-06-05 | Intellisync Corporation | Method, Apparatus and Computer Program Product for Providing Intelligent Synchronization |
US20100217837A1 (en) * | 2006-12-29 | 2010-08-26 | Prodea Systems , Inc. | Multi-services application gateway and system employing the same |
US20090029676A1 (en) * | 2007-02-12 | 2009-01-29 | Guru Thalapaneni | Systems and methods for managing information in mobile devices |
US20080216167A1 (en) * | 2007-03-03 | 2008-09-04 | Kddi Corporation | Proxy connection method and adapter to ims/mmd network |
US7853560B1 (en) * | 2007-04-16 | 2010-12-14 | Cellco Partnership | Methods for address book synchronization and subscription status notification |
US20080311959A1 (en) * | 2007-06-15 | 2008-12-18 | D-Link Corporation | Network device with display module |
US20090131018A1 (en) * | 2007-06-21 | 2009-05-21 | Airwalk Communications, Inc. | System, method, and computer-readable medium for user equipment registration and authentication processing by a femtocell system |
US20090156213A1 (en) * | 2007-10-25 | 2009-06-18 | Spinelli Vincent | Interworking gateway for mobile nodes |
US20090237573A1 (en) * | 2007-11-16 | 2009-09-24 | Audiovox Corporation | Remote control and method of using same for controlling entertainment equipment |
US20090143052A1 (en) * | 2007-11-29 | 2009-06-04 | Michael Bates | Systems and methods for personal information management and contact picture synchronization and distribution |
US20090157732A1 (en) * | 2007-12-13 | 2009-06-18 | Verizon Data Services Llc | Networked address book |
US20100273534A1 (en) * | 2007-12-21 | 2010-10-28 | Ström Jacob | Portable Electronic Apparatus, and a Method of Controlling a User Interface Thereof |
US20090282470A1 (en) * | 2008-05-06 | 2009-11-12 | Cisco Technology, Inc. | Content aggregation server on virtual universal plug-n-play network |
US20090327354A1 (en) * | 2008-06-26 | 2009-12-31 | Microsoft Corporation | Notification and synchronization of updated data |
US20110199338A1 (en) * | 2008-09-10 | 2011-08-18 | Kim Hyun Kyu | Touch screen apparatus and method for inputting user information on a screen through context awareness |
US20100082759A1 (en) * | 2008-09-30 | 2010-04-01 | Microsoft Corporation | Communications grouped as conversations |
US20100180206A1 (en) * | 2009-01-15 | 2010-07-15 | NexAira, Inc. | Systems and methods for iconic graphical user interface and embedded device manager |
US20100312759A1 (en) * | 2009-06-05 | 2010-12-09 | Karl Martin Groethe | Throttling to reduce synchronizations of excessively changing data |
Cited By (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090052675A1 (en) * | 2007-08-23 | 2009-02-26 | Barracuda Inc. | Secure remote support automation process |
US8838965B2 (en) * | 2007-08-23 | 2014-09-16 | Barracuda Networks, Inc. | Secure remote support automation process |
US20110122810A1 (en) * | 2009-11-25 | 2011-05-26 | T-Mobile Usa, Inc. | Router-Based Home Network Synchronization |
US20110125898A1 (en) * | 2009-11-25 | 2011-05-26 | T-Mobile Usa, Inc. | Secured Remote Management of a Home Network |
US8874741B2 (en) | 2009-11-25 | 2014-10-28 | T-Mobile Usa, Inc. | Secured remote management of a home network |
CN102347950A (en) * | 2011-09-29 | 2012-02-08 | 中兴通讯股份有限公司 | Method and system for telecommunication network to provide session services for internet |
EP2763369A1 (en) * | 2011-09-29 | 2014-08-06 | ZTE Corporation | Method and system for telecom network providing session service to internet |
EP2763369A4 (en) * | 2011-09-29 | 2015-01-07 | Zte Corp | Method and system for telecom network providing session service to internet |
WO2014078639A1 (en) * | 2012-11-15 | 2014-05-22 | Cisco Technology, Inc. | Trigger message routing according to a service class |
US9253081B2 (en) | 2012-11-15 | 2016-02-02 | Cisco Technology, Inc. | Trigger message routing according to a service class |
CN105472645A (en) * | 2014-07-01 | 2016-04-06 | 北京奇虎科技有限公司 | Remote diagnosis method and remote diagnosis device for wireless router equipment |
KR20170095854A (en) * | 2014-12-11 | 2017-08-23 | 비트데펜더 아이피알 매니지먼트 엘티디 | Systems and methods for automatic device detection, device management, and remote assistance |
US20190021005A1 (en) * | 2014-12-11 | 2019-01-17 | Bitdefender IPR Management Ltd. | Systems And Methods For Automatic Device Detection, Device Management, And Remote Assistance |
WO2016093723A1 (en) * | 2014-12-11 | 2016-06-16 | Bitdefender Ipr Management Ltd | Systems and methods for automatic device detection, device management, and remote assistance |
WO2016093722A1 (en) * | 2014-12-11 | 2016-06-16 | Bitdefender Ipr Management Ltd | Systems and methods for securing network endpoints |
KR102137276B1 (en) * | 2014-12-11 | 2020-07-24 | 비트데펜더 아이피알 매니지먼트 엘티디 | Systems and methods for automatic device detection, device management, and remote assistance |
US11706051B2 (en) * | 2014-12-11 | 2023-07-18 | Bitdefender IPR Management Ltd. | Systems and methods for automatic device detection, device management, and remote assistance |
AU2015361318B2 (en) * | 2014-12-11 | 2019-09-26 | Bitdefender Ipr Management Ltd | Systems and methods for automatic device detection, device management, and remote assistance |
US10375572B2 (en) | 2014-12-11 | 2019-08-06 | Bitdefender IPR Management Ltd. | User interface for security protection and remote management of network endpoints |
CN107005566A (en) * | 2014-12-11 | 2017-08-01 | 比特梵德知识产权管理有限公司 | System and method for automatics detection, device management and remote assistance |
WO2016093724A1 (en) * | 2014-12-11 | 2016-06-16 | Bitdefender Ipr Management Ltd | Systems and methods for automatic device detection, device management, and remote assistance |
KR20170095853A (en) * | 2014-12-11 | 2017-08-23 | 비트데펜더 아이피알 매니지먼트 엘티디 | Systems and methods for automatic device detection, device management, and remote assistance |
US20160173450A1 (en) * | 2014-12-11 | 2016-06-16 | Bitdefender IPR Management Ltd. | Systems And Methods For Automatic Device Detection, Device Management, And Remote Assistance |
JP2017537562A (en) * | 2014-12-11 | 2017-12-14 | ビットディフェンダー アイピーアール マネジメント リミテッド | System and method for automatic device detection, device management and remote assistance |
RU2694022C2 (en) * | 2014-12-11 | 2019-07-08 | БИТДЕФЕНДЕР АйПиАр МЕНЕДЖМЕНТ ЛТД | Systems and methods for automatic device detection, device control and remote assistance |
US9936388B2 (en) | 2014-12-11 | 2018-04-03 | Bitdefender IPR Management Ltd. | Systems and methods for automatic device detection, device management, and remote assistance |
US10045217B2 (en) | 2014-12-11 | 2018-08-07 | Bitdefender IPR Management Ltd. | Network appliance for protecting network endpoints against computer security threats |
KR102137275B1 (en) * | 2014-12-11 | 2020-07-24 | 비트데펜더 아이피알 매니지먼트 엘티디 | Systems and methods for automatic device detection, device management, and remote assistance |
US9882774B2 (en) | 2015-02-02 | 2018-01-30 | Eero Inc. | Systems and methods for intuitive home networking |
US10833927B2 (en) | 2015-02-02 | 2020-11-10 | A9.Com, Inc. | Systems and methods for intuitive home networking |
US11133985B2 (en) | 2015-02-02 | 2021-09-28 | A9.Com, Inc. | Systems and methods for intuitive home networking |
WO2016126491A1 (en) * | 2015-02-02 | 2016-08-11 | Eero, Inc. | Systems and methods for intuitive home networking |
US10594552B2 (en) | 2015-02-02 | 2020-03-17 | A9.Com, Inc. | Systems and methods for intuitive home networking |
US9736019B2 (en) | 2015-05-14 | 2017-08-15 | Eero Inc. | Methods for dynamic router configuration in a mesh network |
US11075802B2 (en) | 2015-05-14 | 2021-07-27 | A9.Com, Inc. | Methods for dynamic router configuration in a mesh network |
WO2016193123A1 (en) * | 2015-06-01 | 2016-12-08 | Thomson Licensing | Network management infrastructure |
WO2017040552A1 (en) * | 2015-09-01 | 2017-03-09 | Microsoft Technology Licensing, Llc | Remote router request relaying |
CN106487513A (en) * | 2015-09-01 | 2017-03-08 | 微软技术许可有限责任公司 | Remote router request relaying |
EP3661147A4 (en) * | 2017-07-25 | 2020-07-08 | Cloudminds (Shenzhen) Robotics Systems Co., Ltd. | Control method, control apparatus and control system for intelligent device |
JP2020527317A (en) * | 2017-07-25 | 2020-09-03 | 深▲せん▼前海達闥雲端智能科技有限公司Cloudminds (Shenzhen) Robotics Systems Co., Ltd. | Smart device control methods, control devices and control systems |
JP7089142B2 (en) | 2017-07-25 | 2022-06-22 | 達闥機器人股▲分▼有限公司 | Smart device control methods, control devices and control systems |
WO2020035150A1 (en) * | 2018-08-17 | 2020-02-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of subscription profiles for a set of wireless devices |
US20210385635A1 (en) * | 2018-08-17 | 2021-12-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of subscription profiles for a set of wireless devices |
US11523261B2 (en) * | 2018-08-17 | 2022-12-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of subscription profiles for a set of wireless devices |
WO2021017919A1 (en) * | 2019-07-31 | 2021-02-04 | 中兴通讯股份有限公司 | Ota update diagnostic method and apparatus, wireless routing device, and terminal device |
Also Published As
Publication number | Publication date |
---|---|
EP2504964A2 (en) | 2012-10-03 |
WO2011066153A2 (en) | 2011-06-03 |
WO2011066196A3 (en) | 2011-10-27 |
US8346976B2 (en) | 2013-01-01 |
EP2504964B1 (en) | 2018-09-19 |
US20110125898A1 (en) | 2011-05-26 |
US20110122810A1 (en) | 2011-05-26 |
EP2504965A2 (en) | 2012-10-03 |
US20110126095A1 (en) | 2011-05-26 |
WO2011066181A3 (en) | 2011-09-29 |
WO2011066181A2 (en) | 2011-06-03 |
US8874741B2 (en) | 2014-10-28 |
WO2011066197A2 (en) | 2011-06-03 |
WO2011066196A2 (en) | 2011-06-03 |
WO2011066180A2 (en) | 2011-06-03 |
EP2504964A4 (en) | 2015-01-21 |
US20110125925A1 (en) | 2011-05-26 |
WO2011066153A3 (en) | 2011-09-22 |
EP2504965B1 (en) | 2019-07-24 |
WO2011066180A3 (en) | 2011-08-18 |
WO2011066197A3 (en) | 2011-11-24 |
EP2504965A4 (en) | 2014-04-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8346976B2 (en) | Secured registration of a home network device | |
US10530598B2 (en) | Voice control of endpoint devices through a multi-services gateway device at the user premises | |
US8127028B2 (en) | Method and arrangement of a multimedia gateway and communication terminals | |
US9756011B2 (en) | System and method for logging communications | |
US20110182205A1 (en) | Method and apparatus for service discovery | |
US8060624B1 (en) | Initiating a communication session from a presence enabled media host device | |
US8356091B2 (en) | Apparatus and method for managing a network | |
US8233474B2 (en) | Communication of location information for an IP telephony communication device | |
US20110173687A1 (en) | Methods and Arrangements for an Internet Multimedia Subsystem (IMS) | |
US20220408251A1 (en) | Method for supporting authentication of a user equipment | |
EP2465240B1 (en) | Method and arrangement for enabling multimedia services for a device in a local network | |
US10230800B2 (en) | Method for establishing management session, customer premises equipment, and auto-configuration server | |
US20160241642A1 (en) | Multimedia sharing method, registration method, server and proxy server | |
EP2987295A1 (en) | Local control of additional media session for a packet based call | |
US9712392B2 (en) | SIP endpoint configuration in VoIP networks | |
US20230126313A1 (en) | Collecting client data for wireless client devices | |
US20130339531A1 (en) | Method and apparatus for transmitting an identity | |
US20090064313A1 (en) | Apparatus and method for monitoring communications | |
JP2010527536A (en) | System and method for sending a notification message to a mobile station using Session Initiation Protocol (SIP) and IP-Push | |
US8743688B2 (en) | Method and apparatus for dynamically controlling internet protocol packet handling in a voice over internet protocol network | |
US10097643B2 (en) | Technique for remote administration of a device belonging to a private network | |
US20220166751A1 (en) | Phone call endpoint security | |
Cho et al. | A management for the deployment of presence service using a dynamic routing algoritm in the IMS nodes | |
CN102547971B (en) | Method and device for registering user terminal in IMS (IP multimedia subsystem) network | |
Cho et al. | A Management for the Deployment of PoC Using Dynamic Routing Algorithm in the IMS Nodes |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HASSAN, OMAR;HODROJ, SAMIR M.;REEL/FRAME:023836/0467 Effective date: 20100122 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: DEUTSCHE TELEKOM AG, GERMANY Free format text: INTELLECTUAL PROPERTY SECURITY AGREEMENT;ASSIGNOR:T-MOBILE USA, INC.;REEL/FRAME:041225/0910 Effective date: 20161229 |
|
AS | Assignment |
Owner name: METROPCS WIRELESS, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 Owner name: PUSHSPRING, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 Owner name: METROPCS COMMUNICATIONS, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 Owner name: T-MOBILE SUBSIDIARY IV CORPORATION, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 Owner name: IBSV LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 Owner name: T-MOBILE USA, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE TELEKOM AG;REEL/FRAME:052969/0381 Effective date: 20200401 Owner name: IBSV LLC, WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE TELEKOM AG;REEL/FRAME:052969/0381 Effective date: 20200401 Owner name: LAYER3 TV, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK AG NEW YORK BRANCH;REEL/FRAME:052969/0314 Effective date: 20200401 |