In various embodiments, the wireless access point may send information about the accessible N11 services to the user device. In some embodiments, such information may be sent in a public action frame response message. In various embodiment, based on the information received from the access point, the N11 application on the user device may collect, store, and display information about the accessible N11 services provided by the network in the current location. Specifically, the N11 application may display on the user device the N11 services that are available for selection by a user.

In various embodiments, in response to detecting a user selection invoking an N11 service request through the application, the user device may use conventional methods to associate to the network (i.e., WLAN), such as using 802.11 open system authentication. The user selection may be, for example, dialing of a short code associated with one of the non-emergency community services displayed through the application interface. The N11 application may map the user's selection to a location-based destination call center number for the service. The N11 application may establish the call with the appropriate N11 service call center through the operator's core network. In some embodiments, establishing the call with an N11 service call center may be accomplished via a gateway using voice-over-IP or voice-over-WLAN calling.

In various embodiments, telecommunications services may be provided to user wireless devices via a connection to a network, such as a cellular telephone network, WAN, LAN, WLAN, terrestrial network, satellite network, etc., and/or other well-known technologies. Such networks may be accessed via any of a number of wireless and/or wired connections, including through a radio frequency (RF) resource, wireless adapter, coaxial cable, fiber optic cables, DSL interface, Worldwide Interoperability for Microwave Access (WiMAX), or an Integrated Service Digital Network (ISDN) interface.

The various embodiments may be implemented within a variety of communications systems, an example of which is illustrated in FIG. 1. The communications system 100 may be used by a multiple system operator (MSO), internet service provider (ISP), cellular service provider, or other type of service provider that facilitates messaging and/or other network-based messaging/signaling between one or more server connected to the Internet or other external network.

The communications system 100 may include a plurality of end user devices 102, which may be configured to communicate via a Wi-Fi network, an Ethernet network, a cellular telephone network, a radio access network, a WiMAX network, and/or other well-known technologies. The end user devices 102 may each be configured to receive and transmit data and control signals to and from an access point 104 (e.g., a wireless access point, router, hub, broadband gateway, base station, etc.), which may be coupled to a controller operable to transmit the data and control signals between to other network destinations. The controller may be, for example, a service gateway, wireless LAN controller (WLC), cellular base station, radio network controller, etc. For each end user device 102, signaling with the access point 104 may be performed via a wireless and/or a wired connection.

The access point 104 may communicate with an access gateway 106 of a communications service provider (e.g., a packet data network gateway (PGW), a cable modem termination system (CMTS), a wireless access gateway (WAG), broadband network gateway, etc.) that serves as the primary point of entry and exit for end user device traffic. The access gateway 106 may be implemented in a single computing device or in many computing devices.

Functions of the access gateway 106 may include, but are not limited to, forwarding data and control signals to network components as user data packets, providing connectivity to external data sources/networks, managing and storing network/internal routing information, and/or acting as an anchor between different technologies (e.g., Wi-Fi, broadband, 3G/4G/5G systems, etc.). The access gateway 106 may also coordinate the transmission and reception of data to and from the Internet 108, and the transmission and reception of voice, data and control information to and from an external service network connected to the Internet 108, as well as other access points 104.

Through the access gateway 106, the end user devices 102 may be connected to a service network 110 either directly or via the Internet 108. The service network 110 may control a number of services for individual subscribers, such as management of billing data and selective transmission of data, such as multimedia data, to a specific end user device 102. The service network 110 may be implemented in a single computing device or in many computing devices, and typically includes one or more server 112, such as a media server of a content provider, a communication server, etc.

Each end user device 102 may be, as noted above, a variety of devices. For example, each end user device 102 may be a smartphone, a laptop computer, a tablet computer, a smartphone, or any other suitable end point device capable of connecting to a LAN. In general, the end user devices 102 may include a platform that can receive and execute software applications, data and/or commands transmitted over the communication network that may ultimately come from the service network 110, the Internet 108 and/or other remote servers and networks.

The various embodiments are particularly useful with Wi-Fi or other IEEE networks to obtain access to service provider core network. However, the embodiments may also be implemented over any combination of wireless and/or wired networks and access protocols, with no changes to the methods, such as broadband networks (e.g., optical network, wireless satellite, cable modem or DSL modem etc.).

In various embodiments, a WLAN may be represented by one or more wireless access points (e.g., access point 104), an interface to the WLAN, and the medium carrying data between one or more user wireless communication device and the interface to the WLAN (i.e., the air interface). An architecture of an embodiment system to support non-emergency community services over WLAN implemented by a service provider network is illustrated in FIG. 2. With reference to FIGS. 1 and 2, the system 200 may be similar to communications system 100 and/or components thereof. The system 200, which may be configured to provide communications services to one or more end user device(s) 202, may include at least one wireless access point, shown as wireless access point (“WAP”) 204a and WAP 204b, and a wireless community services provisioning server 206 including a controller 208, and service profiles 210.

In various embodiments, a mobile application may be installed on an end user device 202, and may be specifically designed to display the non-emergency community services supported by service providers. The installed application (i.e., “N11 application”) may monitor surrounding wireless access points (e.g., WAP 204a, 204b), and detect networks supporting non-emergency community service calls. Through the N11 application, the end user device(s) 202 may collect information about the capabilities and N11 services provided by the wireless access point(s) 204 serving the device's current location prior to associating with a network. The N11 application may use the collected information to display available N11 services on the end user device(s) 202.

The wireless access point(s) 204a, 204b may be operative to wirelessly communicate with end user device(s) 202, such as a wireless device. In some embodiments, the wireless access points 204a, 204b may implement the wireless network protocol specified in the IEEE 802.11 WLAN specification. While the example coverage area for the end user device(s) 202 is illustrated in FIG. 2, as including two wireless access points 204a, 204b, it should be understood that any number of access points may be included. In various embodiments, each wireless access point 204 (i.e., 204a, 204b) in the coverage area that is able to support non-emergency community services over WLAN may include an N11 services module.

While shown only for wireless access point 204a, it should be understood by those of ordinary skill in the art that the N11 services module may be included in all wireless access points 204 (i.e., 204a, 204b) that are configured to support non-emergency community service voice calls according to the various embodiments.

The N11 services module according to various embodiments may be an application that may be configured to implement steps to recognize that information about available N11 services has been requested, to retrieve such information, and to provide a response with the requested information, according to various embodiments. In particular, the N11 services module of the wireless access point(s) 204 may relay requests about available N11 services to the community services provisioning server 206, along with location information (e.g., location of the end user device(s) 202 and/or the wireless access point 204) and information about the capabilities of the end user device(s) 202.

The community services provisioning server 206 may include a database/repository capable of storing service profiles 210 as configuration objects. In various embodiments, the service profiles 210 may link the N11 services offered by one or more service provider with various geographical locations.

In some embodiments the controller 208 of the provisioning server 206 may be configured to manage and distribute N11 service profiles 210 to the wireless access points 204 associated with a service provider/network operator.

In various embodiments, the community services provisioning server 206 may implement location based N11 services availability provisioning and rendering service logic. Specifically, service providers and network operators may use provisioning interfaces to define the N11 services offered in different communities or geographical regions. Such service information may be processed by the controller 208 and stored as one or more service profile 210.

In some embodiments, the controller 208 may be configured to receive a notification from at least one wireless access point 204 in which a end user device(s) 202 within the coverage area has requested information about N11 services available (e.g., by a probe response frame sent from the wireless access point 204 to the wireless device 202). In some embodiments, the controller 208 may coordinate selection of a serving access point (e.g., WAP 204a or WAP 204b). In some embodiments, the controller 208 may provide an N11 services profile to a requesting access point (e.g., WAP 204a or WAP 204b) based on location (e.g., of the end user device(s) 202 and/or the access point 204) and end user device(s) 202 capabilities.

In various embodiments, the selected access point (e.g., WAP 204a or WAP 204b) may provide details about N11 services available to an end user device (e.g., wireless device 202) using the N11 services profile received from the controller 208 of the provisioning server 206. In some embodiments, the selected access point (e.g., WAP 204a or WAP 204b) may send a public action frame response to the end user device. Such functions may be implemented as one or more software module in an application executed on a processor, as one or more hardware module (e.g., hardware component(s) wired to perform such functions), or as combinations of hardware component(s) and software module(s) running on one or more processors.

In some embodiments, the functions of the controller 208 may include further tasks to manage establishing a non-emergency community services call routed to a an N11 service call center 212 via a wireless access point 204 and at least one core network 214. In various embodiments, the controller 208 may be implemented by one or several interlinked computers, i.e., a hardware platform, a software platform basing on the hardware platform and several application programs executed by the system platform formed by the software and hardware platform. The functionalities of the controller 208 may be provided by the execution of these application programs.

In some embodiments, additional network elements may provide access control to the communication network associated with the service provider (e.g., core network(s) 214), such as by providing access control rules that may be stored in memory, and filtering arriving data packets before admitting them to the communication network based on such rules. In various embodiments, access control/location service may be implemented by one or more server such as an authentication, authorization, and accounting (AAA) server.

Access control/location service may also include functions to locate and store information regarding the location of end user device 202 that seeks to associate with the communication network (i.e., create a communication link between the end user device 202 and the communication network). In various embodiments, the location of a user end user device 202 may be identified and/or updated by extracting information from messages received from that end user device 202 during association with a wireless access point 204 (e.g., 204a). Such information may be provided from the serving wireless access point 204 using any of a number of supported networking protocols, such as Remote Authentication Dial-In User Service (RADIUS)) messaging. The access control/location service may also use any of a number of supported networking protocols for communication with other entities in the system (e.g., with elements of the core network(s) 214).

The system 200 may also include components of various core networks. The core network(s) 214 may include an IP core network (e.g., Wi-Fi), as well as one or more mobile core network (e.g., an LTE network, 2G/3G network, etc.). The IP core network may provide a gateway between a WLAN and the one or more mobile core network. Components of an IP core network may include, for example, a Tunnel Termination Gateway (TTG)/Packet Data Gateway (PDG). The IP core network may also include network services such as a DHCP server that allocates a unique Internet Protocol (IP) address to each wireless device 202 upon association with a wireless access point 204 in order to access the network. In some embodiments, the DHCP server may be connected to a DHCP database. Additionally or alternatively, the DHCP server may be used to assign address or access information using other protocols.

In some embodiments, an LTE mobile core network may be an evolved packet core (EPC) that includes, for example, at least one Mobility Management Entity (MME), a Serving Gateway (SGW), and a Packet Data Network (PDN) Gateway (PGW).

In some embodiments, the system 200 may include one or more radio access network that uses cellular network protocols, for example, an LTE radio access network (e.g., Evolved UMTS Terrestrial Radio Access Network (E-UTRAN)). The E-UTRAN may connect to the EPC through the SGW, which may be logically connected to the PGW. The MME may handle tracking and paging of a wireless device 202 and security for E-UTRAN access on the EPC. The MME may be linked to a Home Subscriber Server (HSS), which may support a database containing user subscription, profile, and authentication information. Further, the MME may provide bearer and connection management for user Internet protocol (IP) packets, which are transferred through the SGW. The SGW may route, via external IP networks (e.g., PDN(s)), incoming and outgoing IP packets for wireless devices connected to the SGW. The E-UTRAN. The SGW may also provide an anchor point for handovers between access points of the E-UTRAN (e.g., eNodeBs). The SGW may be logically connected to a PDN Gateway (PGW), which may route packets to and from PDNs to form a connection between the EPC and various PDNs. The PGW may be logically connected to a Policy Charging and Rules Function (PCRF), a software component that may enforce minimum quality of service parameters, and manage and control data sessions. The PGW may also provide connections with other public or private networks (e.g., the Internet, an Intranet, an IP Multimedia Subsystem (IMS), etc.). The mobile core network(s) may further include a circuit switched network and/or packet switched network. For example, a PS core may be a UMTS core network that includes a Serving GPRS support node (SGSN) and a Gateway GPRS support node (GGSN). The SGSN may provide an interface with (or gateway to) an access network (e.g., a radio access network or a WLAN), and the GGSN which may be connected to external PS networks (i.e., the Internet, various PDNs, etc.).

The system 200 may also include IMS/Public Switched Telephone Network (PSTN) 216, which may be in communication with the core network(s) 214. For example, a PGW may provide the connection to the IMS in an LTE network (e.g., EPC). In this manner, the IMS may provide communication between the mobile core network (e.g., EPC) with the PSTN. Further, the IMS may provide an interface with additional external packet data networks. In this manner, voice calls may take place over both traditional telephony services and IP-based services.

The system 200 may also include one or more N11 service call center 212, to which data packets related to non-emergency community service voice calls may be routed via the core network(s) 214 and IMS/PSTN 216. The dialing of a short code for non-emergency community service through the N11 application may connect the end user device 202 to an appropriate N11 service call center 212 based on location.

In some embodiments, additional location information associated with the serving wireless access point 204 may be used to connect an end user device 202 to the N11 service call center 212. In some embodiments, such location information may be provided through SIP messaging with the core network(s) 214, such as in a portion of a SIP INVITE message. The wireless access point 204 location may be stored in a wireless network registry of an end user device 202 upon establishing a call. Thus, in embodiments in which an outbound call from an end user device 202 is a SIP-based communication, a SIP location field may be utilized to forward the location of the wireless access point 204 in the SIP INVITE message. The identification and/or location of the wireless access point 204 may be used by the core network to assist with routing the non-emergency community service call to the appropriate N11 service call center 212.

The term “system-on-chip” or “SoC” is used herein to refer to a set of interconnected electronic circuits typically, but not exclusively, including multiple hardware cores, a memory, and a communication interface. The hardware cores may be of a variety of different types of processors, such as a multi-core central processing unit (CPU), a multi-core digital signal processor (DSP), a multi-core accelerated processing unit (APU), and a multi-core auxiliary processor.

FIG. 3 illustrates an example of an access point 300 configured to obtain and to signal to end user devices information about non-emergency community services supported by the network/WLAN. With reference to FIGS. 1-3, the access point 300 may be an example of one or more wireless access point 204.

The access point 300 may include a SoC 302 with a processor 304, a memory 306, a communication interface 308, and a storage memory interface 310. The access point 300 may further include one or more communication component 312, such as a network interface (e.g., an 802.3 interface) for communication with a LAN, a wireless network interface 320 (e.g., an IEEE 802.11 WLAN interface) for wireless communication with one or more wireless communication devices over Wi-Fi, a radio frequency (RF) transceiver (or other receiver and transmitter circuitry) configured to perform transmit/receive functions in particular RF spectrum frequency range(s), etc.

The communication component(s) 312 and corresponding antenna(s) 314 may be configured to send data to, and receive data from, devices within a WLAN using a supported wireless communication protocol. Further, a communication component(s) 312 and corresponding antenna 314 may be configured to access an external wireless network 316 for additional features and/or network services. A connection 318 to the wireless network 316 may use any of a number of wireless standards, for example, Wi-Fi, WiMAX, or mobile VoIP, and/or may be based on mobile broadband or cellular network technology. Examples of wireless networks based on cellular network technology may include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, and Frequency Division Multiple Access (FDMA) networks. The wireless network 316 may utilize various radio technologies such as Wideband-CDMA (W-CDMA), cdma2000, Global System for Mobile Communications (GSM), etc.

The communications component(s) 312 may also be coupled to a network interface 320 that supports a wired connection 322 to the Internet 324. The home gateway 300 may communicate with, for example, one or more remote computing device 326 over the wireless connection 318 and/or the wired connection 322. In some embodiments, the remote computing device may be a server associated with a service provider.

The wireless access point 300 may also include software modules (including Dynamic Host Configuration Protocol (DHCP) clients, and device drivers (e.g., network and WLAN interface drivers) stored in the memory 306 (e.g., a hard disk drive, flash memory, EEPROM, etc.). At start up, these software components may be loaded into system memory and then accessed and executed by processor 304.

The access point 300 may include one or more controller, on which any of a variety of processing devices of the SoC 302 (e.g., processor(s) 304) may be implemented, and may include a number of processing cores. The access point 300 may also include processors that are not associated with a SoC 302. In various embodiments, the processor(s) 324 may execute any number of applications, including an emergency service module.

The memory 306 of the SoC 302 may be configured for storing data and processor-executable code for access by the processor 304. The memory 306 may include, for example, volatile memory configured to temporarily hold a limited amount of data received from a data sensor or subsystem.

The access point 300 may also include a storage component 328, which may be a non-volatile memory device (e.g., a read-only memory, flash memory, hard disk drive, solid state drive, etc.). The storage memory interface 310 and storage component 328 may work in unison to allow the access point to store data (e.g., SSID template(s)) and processor-executable code on a storage medium. The storage memory interface 310 may control access to the storage component 328, and may allow the processor 304 to read data from and write data to the storage component 328.

The communication interface 308, communication component(s) 312, antenna(s) 314, and/or network interface 320 may work in unison to enable the home gateway 300 to communicate over the wireless network 316 via a wireless connection 318, and/or a wired connection 322 with the remote computing device 326. As described, the wireless network 316 may be implemented using a variety of wireless communication technologies, including, for example, radio frequency spectrum used for wireless communications, to provide the home gateway 300 with a connection to the Internet 324 by which it may exchange data with the remote computing device 326.

It should be noted that some or all of the components of the access point 300 may be differently arranged and/or combined while still serving the necessary functions. Moreover, the access point 300 may not be limited to one of each of the components, and multiple instances of each component, in various configurations, may be included in the access point 300.

In various embodiments, an operator (or service provider) may support non-emergency community service calls over WLAN by preconfiguring the provisioning server with information about N11 services offered in different geographic locations. Using this information, at least one N11 service profile may be developed and stored as a configuration object on the provisioning server, and sent to a wireless access point when needed. That is, the wireless access point may retrieve an N11 service profile that is stored by the provisioning server.

In various embodiments, a non-emergency service call request may be triggered on a user wireless device by the native call dialer (e.g., dialing an N-1-1 short code), and/or through an interface of the N11 application running on the wireless device. In various embodiments, the coordination and selection of a serving access point (i.e., 104, 204, 300) may be performed by the N11 application on a wireless device based on the user selecting a desired N11 service from those available. Such available services may be displayed to the user through an N11 application interface on the device.

FIGS. 4A and 4B illustrate a method 400 of implementing non-emergency voice-over-WLAN call support on an end user device 202 according to some embodiments. With reference to FIGS. 1-4B, the operations of the method 400 may be implemented by one or more control module, such as on processor(s) of an end user device 202. Some operations of the method 400 may additionally or alternatively be implemented on one or more processor (e.g., 304) of a wireless access point (e.g., 204, 300), or one or more control entity of a wireless network manager.

While described with reference to one entity (e.g., a wireless access point) and end user device 202, such references are merely used as an example, as the method 400 may be applied by and to any of a number of different end user device(s) 202 and/or access point(s) 204 within the service network 100.

In block 402, the processor of an end user device 202 may detect that an N11 application installed on the end user device 202 has been activated to monitor surrounding wireless networks. In some embodiments, activation of the N11 application monitoring may be the result of a user selection, such as selecting to open/start the application, or selection of a specific instruction/command when the application is already running. In some embodiments, the N11 application may already be running as a background process on the end user device 202, and network monitoring may be automatically activated as a result of various conditions (travel on an interstate, through a previously-tagged region, etc.).

In block 404, the processor of an end user device 202 may receive beacon frames from one or more wireless access point(s) (e.g., WAP 204a and/or WAP 204b). As described herein, the beacon frames transmitted by wireless access points to advertise WLAN presence may include an indicator of network support for non-emergency community services (i.e., N11 services).

In determination block 406, the processor of an end user device 202 may determine whether N11 services are supported by an identified WLAN. Such determination may be made based on the information in the received beacon frames. In response to determining that the identified WLAN does not support N11 services (i.e., determination block 406=“No”), the processor of an end user device 202 may return to block 404 for receipt of beacon frames from a different wireless access point.

In response to determining that the identified WLAN supports N11 services (i.e., determination block 406=“Yes”), the processor of an end user device 202 may request information about the WLAN capabilities including the available N11 services in block 408. Such request may be sent, for example, as a probe request frame to the wireless access point 204 associated with the identified WLAN (i.e., based on the beacon frames received in block 404). In various embodiments, the wireless access point 204 may relay such request to a community services provisioning server (e.g., 206) along with information about the end user device 202 (e.g., location, device capabilities, etc.).

In block 410, the processor of an end user device 202 may receive N11 service details from the wireless access point 204 associated with the identified WLAN. Such details may be provided, for example, in a public action frame response message sent to the processor of an end user device 202 by the wireless access point 204. In various embodiments, the N11 service details sent to the processor of an end user device 202 may be based on an N11 profile that the wireless access point 204 retrieved from the provisioning server.

In block 412, the processor of an end user device 202 may store and display the available N11 services through the N11 application running on the end user device 202. Specifically, based on the details received from the wireless access point 204, the N11 application may be populated with a list of location-based N11 services that are currently available to the end user device 202.

In determination block 414, the processor of an end user device 202 may determine whether an N11 service request is detected. For example, an N11 service request may be based on user input (e.g., through a touchscreen, keyboard, etc.) as a selection through the N11 application interface.

In response to determining that an N11 service request is not detected (i.e., determination block 414=“No”), the processor of an end user device 202 may continue to monitor for a N11 service request in determination block 414. In response to determining that an N11 service request is detected (i.e., determination block 414=“Yes”), the processor of an end user device 202 may associate to the WLAN for the requested N11 service, block 416. In some embodiments in which more than one WLAN may support the requested N11 service in the current location, the processor of an end user device 202 may select the WLAN with which to associate based on additional criteria (e.g., signal strength, proximity of the corresponding wireless access point, preferred network settings, etc.). In various embodiments, association of the end user device 202 to the WLAN network may performed using established IEEE 802.11 standards and protocols.

In block 418, the processor of an end user device 202 may, through the N11 application, map the short code for the requested N11 service to a location-based N11 service call center number. For example, if a user has navigated the N11 application on the wireless device to select the “811” service (e.g., through dialing “8-1-1” or using another input mechanism), the N11 application may internally cause the processor of an end user device 202 to dial the location-specific 811 call center. In some embodiments, the contact numbers for the various location-specific call centers may be provided in the N11 service details received from the corresponding wireless access point (i.e., in block 410).

In block 420, the processor of an end user device 202 may establish a WLAN voice call with the target N11 service call center. In various embodiments, establishing such call may be through the service provider's/operator's core network, and may utilize a gateway. The established WLAN voice call may use any of a variety of communication protocols (e.g., VoIP, Wi-Fi, etc.), depending on the capabilities of the target N11 service call center.

Following completion of the N11 service call, the processor of an end user device 202 may return to block 404 to continue receiving beacon frames from nearby wireless access points 204.

FIG. 5 illustrates a method 500 of implementing non-emergency voice-over-WLAN call support in a wireless communication network according to some embodiments. With reference to FIGS. 1-5, the operations of the method 500 may be implemented by one or more control entity managed by or associated with a service network (e.g., service network 110), such as on processor(s) (e.g., 304) of a wireless access point (e.g., 204, 300). Some operations of the method 500 may additionally or alternatively be implemented by one or more control entity of a wireless network manager.

While described with reference to one entity (e.g., a wireless access point) and one end user device 202, such references are merely used as an example, as the method 400 may be applied by and to any of a number of different access point(s) 204 and end user device(s) 202 within the service network.

In block 502, the service network processor (e.g., processor 304 of a WAP 204) may cause the wireless access point 204 to broadcast beacon frames that have, among other information (e.g., SSID, etc.), an indication that N11 services are supported by the associated WLAN.

In determination block 504, the service network processor may determine whether a request for N11 service details for the corresponding WLAN has been received from an end user device 202. In response to determining that a request for N11 service details for the corresponding WLAN has not been received (i.e., determination block 504=“No”), the service network processor may return to broadcast beacon frames in block 502.

In response to determining that a request for N11 service details for the corresponding WLAN has been received (i.e., determination block 504=“Yes”), in block 506 the service network processor may send the request for N11 service details to the provisioning server (i.e., 206) along with location information and end user device's 202 capabilities.

In block 508, the service network processor may receive one or more N11 services profile from the provisioning server 206. Specifically, the N11 services profile(s) may have been configured by the service provider/network operator and stored on the provisioning server 206.

In block 510, the service network processor may send location-based N11 service details to the end user device 202. Specifically, such location-based N11 service details may be based on the profile(s) that were received from the provisioning server 206. The service network processor may return to block 502 to continue broadcasting beacon frames.

The references to various end user device(s) 202 and/or wireless access points 204 are arbitrary and used merely for the purposes of describing the embodiments. That is, any indicator, name, or other designation to differentiate messaging associated with different access points and devices may be assigned, without changing the embodiment methods.

The various embodiments may be implemented on any of a variety of commercially available server devices, such as the server 600 illustrated in FIG. 6. For example, with reference to FIGS. 1-6, a server 600 (which may correspond, for example, to the server 600 and/or the remote computing device 326 in FIGS. 1 and 3, respectively) may include a processor 601 coupled to volatile memory 602 and a large capacity nonvolatile memory, such as a disk drive 603. The server 600 may also include a floppy disc drive, compact disc (CD) or DVD disc drive 604 coupled to the processor 601. The server 600 may also include network access ports 606 coupled to the processor 601 for establishing network interface connections with a network 607, such as a local area network coupled to other broadcast system computers and servers, the Internet, the public switched telephone network, and/or a cellular data network (e.g., CDMA, TDMA, GSM, PCS, 3G, 4G, LTE, or any other type of cellular data network).

Various embodiments may also be implemented in any of a variety of end user device(s) 202, an example of which is illustrated in FIG. 7. For example, with reference to FIGS. 1-7, a wireless device 700 (which may correspond, for example, the end user wireless devices 102, 202) may include a processor