Abstract: A mobile content management system includes a plurality of content source devices (beacons, QR codes, NFC tags) at respective fixed locations, each associated with a source URL comprising a hosted server domain and a unique identifier. The hosted server generates a hosted user interface enabling authorized designation of destination URLs and optionally associated preview metadata for respective content source devices. A hosted SDK-implemented mobile application residing on a client device, upon obtaining source URL(s), generates selectable tokens comprising the preview metadata corresponding to each of the respective content source devices, and further upon user selection of one of the tokens, generates a request to the hosted server comprising at least the associated source URL. The hosted server, upon receiving the request from the client device, generates a return message to the client device comprising at least one of the destination URLs designated for the respective content source device.

Abstract: A mobile content management system includes a plurality of location-based source devices (e.g., beacon transmitters, QR codes, NFC tags), each associated with a source URL comprising a hosted domain and a unique identifier. A hosted user interface enables designation by an authorized user of destination URLs for the respective source devices. A client device with a resident hosted mobile application reads the source URL from a source device and generates a first call to the hosted server comprising the source device identifier, wherein selectable tokens are generated on the client device interface comprising displayed metadata corresponding to the source device and previewing selectable destination content. Upon user selection of a token, the application generates a second call to the hosted server, wherein the hosted server directs the client device to at least one of the one or more destination URLs designated for the respective source device.

Abstract: A mobile content management system includes a plurality of distributed beacon transmitters, each configured to continuously broadcast messages including a URL, the URL having a host domain address and an identifier unique to the respective beacon embedded therein. Client devices proximate to one or more of the beacons, and having appropriate browser applications executed thereon, are able to receive the broadcast messages and subsequently transmit content requests to the host server associated with the URL. The host server is further configured to identify the beacon from the unique identifier, and return an appropriate destination URL to the client device for user selection, at which point the browser may for example be redirected to a content server associated with the destination URL for content presentation. The system may further include a hosted and administrator-facing web portal wherein at least destination URLs associated with the respective beacons may be remotely designated.

Abstract: A mobile content management system includes a plurality of distributed beacon transmitters, each configured to continuously broadcast messages including a URL, the URL having a host domain address and an identifier unique to the respective beacon embedded therein. Client devices proximate to one or more of the beacons, and having appropriate browser applications executed thereon, are able to receive the broadcast messages and subsequently transmit content requests to the host server associated with the URL. The host server is further configured to identify the beacon from the unique identifier, and return an appropriate destination URL to the client device for user selection, at which point the browser may for example be redirected to a content server associated with the destination URL for content presentation. The system may further include a hosted and administrator-facing web portal wherein at least destination URLs associated with the respective beacons may be remotely designated.

Abstract: Improved systems and methods for call and call feature setup, administration and processing on PSTN and other telecommunications networks are provided. Calls are set up on a service plane of a conceptual switch that includes a switch plane, control plane, and service plane that are analogous to the OSI layered model of networks including a physical layer, network layer and application layer. Call set-up logic is separated from the switching fabric, allowing for flexible, on-demand, modification of service options using software while maintaining the same switching fabric in hardware. Call set-up is accomplished by a call request made upon connection of a call to the switch. This causes a call agent to search an eXtensible Markup Language knowledge base to find a web page corresponding to the initiating caller. The Web page may be collocated with the switch or on a LAN with the switch or on the “Web,” even on the caller's termination equipment (telephone).

Abstract: Improved systems and methods for call and call feature setup, administration and processing on PSTN and other telecommunications networks are provided. Calls are set up on a service plane of a conceptual switch that includes a switch plane, control plane, and service plane that are analogous to the OSI layered model of networks including a physical layer, network layer and application layer. Call set-up logic is separated from the switching fabric, allowing for flexible, on-demand, modification of service options using software while maintaining the same switching fabric in hardware. Call set-up is accomplished by a call request made upon connection of a call to the switch. This causes a call agent to search an eXtensible Markup Language knowledge base to find a web page corresponding to the initiating caller. The Web page may be collocated with the switch or on a LAN with the switch or on the “Web,” even on the caller's termination equipment (telephone).