Abstract: A network has a file system configured for providing a selected version of a first file to a client, having requested the file, based on detecting that the client has opened a second file having an identified relationship with the first file. Files are identified as having a relationship based on membership in a file group, wherein each file group identifies only one version of each file specified in the corresponding file group; hence, multiple file groups can identify files associated with respective versions of a file set. In response to determining the first file belongs to a file group, the file system identifies the version of the second file opened by the client, and selects the version of the first file to be provided to the client based on determining the file group associated with the version of the second file opened by the client.

Abstract: Mobile routers establish a tree-based network topology in an ad hoc mobile network, the tree-based network topology having a single clusterhead and attached mobile routers. Each attached mobile router has a default egress interface configured for sending messages toward the clusterhead, and ingress interfaces configured for receiving messages from attached network nodes that are away from the clusterhead. A neighbor advertisement message received from an ingress interface away from a clusterhead is used by the attached mobile router to identify specified network prefixes that are reachable via the source of the neighbor advertisement message. The attached mobile router outputs on its default upstream interface a second neighbor advertisement message that specifies the network prefix used by the attached mobile router, and the specified network prefixes from the neighbor advertisement message received on the ingress interface. Hence, connectivity is established with minimal routing overhead.

Abstract: Gateways providing connectivity for respective private IPv4 networks to an IPv6 network establish communications between IPv4 nodes in the private network. Network address translation-protocol translation (NAT-PT) state entries are created by gateway pairs enabling translation of IPv4 packets between first and second IPv4 nodes in respective first and second IPv4 private networks into IPv6 packets for transmission via the IPv6 network. Each NAT-PT state entry specifies the IPv6 addresses for the first and second IPv4 nodes, and the IPv4 addresses used to identify the first and second IPv4 nodes in the corresponding private IPv4 network. Each gateway is configured for generating the IPv6 address for each local IPv4 node based on prepending its corresponding assigned private IPv4 address with a corresponding prescribed IPv6 prefix assigned to the gateway.

Abstract: A router has at least one outbound interface configured for establishing multiple IP-based secure connections (i.e., tunnels) with respective destinations based on transmission of encrypted data packets via the IP-based secure connections. The encrypted data packets are generated by a cryptographic module, where each encrypted packet successively output from the cryptographic module includes a corresponding successively-unique sequence number. The supply of data packets to the cryptographic module is controlled by a queue controller: the queue controller assigns, for each secure connection, a corresponding queuing module configured for outputting a group of data packets associated with the corresponding secure connection according to a corresponding assigned maximum output bandwidth. Each queuing module also is configured for reordering the corresponding group of data packets according to a determined quality of service policy and the corresponding assigned maximum output bandwidth.

Abstract: An originating node is configured for generating a route management signaling message having a signaling link selection (SLS) value that is selected by the originating node based on an affected destination value. The affected destination value, distinct from a destination point code (DPC) that specifies a destination node for the route management signaling message, identifies an affected signaling node that is affected by the route management signaling message. Hence, route management signaling messages related to the affected signaling node are routed along the same signaling path, ensuring that all the related route management signaling messages remain in sequence. Further, different signaling path can be established for respective affected signaling nodes, providing load sharing of route management signaling messages relative to the respective affected signaling nodes.

Abstract: Mobile routers in a tree-based network topology with a single clusterhead in an ad hoc network establish connectivity based on each attached mobile router sending a neighbor advertisement message to an attachment mobile router via a corresponding egress interface. Any neighbor advertisement message received by a mobile router is used to identify specified network prefixes that are reachable via the source of the neighbor advertisement message. Each attached mobile router outputs to its attachment router another neighbor advertisement message that specifies the network prefix used by the mobile router, and the specified network prefixes from its attached mobile routers. The mobile router also identifies peer mobile routers having the same depth, and selectively shares limited routing information with the peer routers, enabling the mobile router to bypass the clusterhead and reach remote prefixes via the peer routers without burdening the tree.

Abstract: An application server includes an asynchronous event manager configured for selectively terminating an instance executing a messaging session, based on detecting a message from a gateway server that the incoming call is a call having a type that differs from the prescribed type intended for the messaging session. The asynchronous event manager terminates the instance by setting global variables accessible by the instance that specify that the call is rejected (i.e., the connection between the gateway and the instance executing the messaging session is terminated) due to the incoming call being of a different type than intended for that messaging session, for example the call being a fax call instead of a voice call.

Abstract: An application server, configured for dynamically generating a web page (e.g., HTML) document based on execution of XML documents, dynamically generates an HTML page having selected form elements based on a stored XML document that defines available HTML form elements and respective attributes, and based on user attributes retrieved by the application server from an open network database server (such as LDAP). The application server, in response to a request from a user, accesses an XML document configured for specifying attributes associated with the request; the XML document may specify as form elements menus that are available for generation based on qualified user attributes, or may specify HTML fields that can be generated for display on the HTML page based on the qualified user attributes. The application server also retrieves the user attributes, and dynamically generates the HTML page based on identifying the user attributes matching the qualified user attributes of the accessed XML document.

Abstract: A mobile router is configured for generating a local router prefix (i.e., a null or invalid address prefix that is not reachable via a wide area network) for use by mobile nodes that attempt to attach to the mobile router. The mobile router attaches to an attachment router using a care-of address with an attachment router address prefix, and outputs a router advertisement message that specifies the null address prefix. Upon receiving a message from a mobile host that includes a source address field specifying a mobile host care-of address that includes the null address prefix, the mobile router adds the mobile host care-of address to a reverse routing header and inserts its own care-of address into the source address field. The message is output to its destination with the reverse routing header, ensuring the IPv6 address of the mobile router remains anonymous in the wide area network.

Abstract: A network-enabled user interface device, for example a VoIP telephony device, includes a display, a user input interface, an interface controller, and an application controller. The interface controller is configured for generating display elements for the display, controlling the user input interface based on received commands, and outputting responses to the application controller. The application controller is configured for outputting the commands to the interface controller based on application operations executed locally (i.e., within the user interface device), or remotely (e.g., by a server in communication with the user interface device). Remote application operations may include communications between the application controller and the remote server. The interface controller also may generate the display elements based on messages received from the network.

Abstract: A unified web-based voice messaging system provides voice application control between a web browser and an application server via an hypertext transport protocol (HTTP) connection on an Internet Protocol (IP) network. The application server generates and maintains a server-side data record, also referred to as a “brownie”, that includes application state information and user attribute information for an identified user session with the web browser. The application server, in response to receiving a new web page request from the browser, initiates a web application instance to begin a transient application session with the browser. The brownie also includes a session identifier that uniquely identifies the session with the user of the application session. The application server stores the brownie in a memory resident within the server side of the network, and sends to the browser the session identifier and the corresponding web page requested by the web browser.

Abstract: A protocol emulator includes an executable emulation application configured for promiscuously detecting IP frames on a network interface. The executable emulation application generates response IP frames for each corresponding detected IP frame. The protocol emulator also includes a raw socket configured for outputting each response IP frame onto the network interface. Hence, the protocol emulator minimizes use of UNIX kernel resources by eliminating IP filtering of received IP frames from the network interface, and by using a raw socket for sending a response IP frame generated by the emulation application instead of the socket layer or the kernel. Hence, the minimal use of UNIX kernel resources enables scalable emulation of multiple logical IP addresses, effectively enabling an unlimited number of IP devices to be emulated without assignment of IP addresses to respective sockets.

Abstract: A Voice over IP network having multiple signaling message transfer nodes (e.g., call agents, signaling gateways), communicate with switched circuit network nodes using a single point code. A signaling gateway, upon receiving an SS7 signaling message specifying a destination point code corresponding to its provisioned point code and carrying a signaling application protocol message, selects a destination call agent based on the originating point code in the SS7 signaling message and independent of the destination point code. The signaling gateway selectively outputs to the selected destination call agent an IP-based message carrying the signaling application protocol message according to a prescribed IP-based signaling message transport protocol, based on a determined availability of the selected destination call agent. The signaling gateway uses the User Part Unavailable message to inform the originating PSTN switch that the selected destination call agent is unavailable.

Abstract: A unified messaging system is configured for encrypting messages. The calling party is prompted to encrypt the unified message, for example as part of an extended options menu. The unified messaging system encrypts the unified message based on an encryption key input by the user into an encrypted message, and generates an open-network destination header for identifying a destination location for the encrypted message according to an open-network protocol. The unified messaging system then outputs the open-network destination header and the encrypted message as an open-network encrypted message to an open-network message store. During retrieval of the message, the unified messaging system identifies the encrypted message and prompts the destination subscriber for a decryption key; the unified messaging system performs a decryption operation to recover a decrypted file, and outputs the decrypted file for playback to the user.

Abstract: Peer-to-peer endpoint devices discover a localized IP address realm that minimizes the traversal of the Network Address Translators. Each endpoint device sends a query from its corresponding local address realm to its corresponding destination endpoint device using the corresponding available address for the destination endpoint device. The available address has a value outside the address realm of the endpoint device sending the query. The query also specifies a unique identifier that is identifiable solely by the endpoint device. The destination endpoint device receives the query, having traversed one or more NATs and at least two address realms, and sends a response that specifies the unique identifier for the query source, a unique identifier for the destination endpoint device, and multiple alias addresses for reaching the destination endpoint device. The query source selects one of the alias addresses that is determined reachable by the query source.

Abstract: A network-enabled user interface device, for example a VoIP telephony device that serves as a Voice over IP endpoint, includes an executable presence resource configured for establishing and maintaining presence information for a user of the user interface device. The presence resource outputs the presence information to at least one selected destination, enabling other user interface devices on the network to detect the presence information for the user relative to the user interface device. The presence resource also is configured for retrieving presence information for other network subscribers, enabling the user interface device to select available services based on the retrieved presence information. Moreover, user interface device may present selected services or network subscriber data to the user based on the retrieved presence information, enabling the user to determine appropriate operation to perform based on the retrieved presence information.

Abstract: A unified communications system is configured for receiving, storing, and/or sending SMS messages based on management of the SMS messages according to a prescribed open standards-based protocol. The unified communications system includes an SMS module configured for receiving SMS messages according to SMPP protocol. The SMS module obtains source and destination information from the received SMS message, and accesses a subscriber profile directory for subscriber profile information based on at least one of the source and destination information. The SMS module generates a common format message that includes the SMS message, and selectively supplies the common format message to selected destinations based on the accessed subscriber profile information. The common format message may be stored in a prescribed message store, for example an IMAP directory, or output as an e-mail message to a prescribed destination.

Abstract: Advanced communication services are deployed for a user device, such as a VoIP telephony device, based on utilizing a model view controller architecture within a network system (e.g., a VoIP system) configured for communication with the VoIP telephony device. The VoIP telephony device and a service node of the VoIP system each are configured for executing at least one corresponding model object, view object, and controller object of a prescribed network service. The model object, view object, and controller object each are configured for utilizing transaction-based messages associated with the prescribed network service. Moreover, the service node is configured for selectively transferring any one of the model object, view object, and the controller object to another node, for example the VoIP telephony device or another network node, and terminating execution of the transferred object, without interruption in service for the user.

Abstract: An IP-based node in communication with IP-based gateway devices is configured for executing circuit selection for a prescribed trunk group having multiple sets of connected trunk groups, the multiple sets of connected trunk groups managed by the respective IP-based gateway devices. The prescribed trunk group is configured for connecting with a two-way trunk group of a switch, for example a PSTN-based switch, having substantially more circuits than any one of the multiple sets of connected trunk groups for the IP-based gateway devices. The IP-based node executes circuit selection at least based on a first message, received from one of the IP-based gateway devices via an IP connection and specifying circuit availability for at least a portion of the corresponding set of connected trunk groups.

Abstract: A unified web-based voice messaging system provides voice application control between a web browser and an application server via an hypertext transport protocol (HTTP) connection on an Internet Protocol (IP) network. The application server executes the voice-enabled web application by runtime execution of a first set of extensible markup language (XML) documents that define the voice-enabled web application to be executed. The application server generates an HTML form specifying selected application parameters from an XML document executable by the voice application. The HTML form is supplied to a browser, enabling a user of the browser to input or modify application parameters for the corresponding XML document into the form. The application server inserts the received input application parameters into the XML document, and stores the document.