Abstract: Disclosed herein are systems and methods for providing and using a decentralized network using a blockchain. A provider (and/or miner) may provide network coverage to one or more devices in return for tokens on the blockchain. The blockchain may employ a proof-of-coverage scheme to verify (and even guarantee) that the miners are honestly representing the wireless network coverage they are providing. In some instances, the proof of coverage may require the providers to prove coverage periodically, upon demand, and/or at random intervals.

Abstract: Provided herein are systems and methods for implementing a network consensus for a blockchain network that is characterized by one or more, or all, of the following attributes: (1) implementation of a Proof-of-Coverage scheme; (2) lack of permission for nodes to participate in the network; (3) decentralization, with lack of incentives to centralize; (4) byzantine fault tolerance; (5) based on useful work to the network; (6) high confirmed transaction rate; and (7) censor-resistant transactions.

Abstract: Disclosed herein are systems and methods for facilitating data transmission using a decentralized consensus network. The system comprising: a verified and decentralized consensus network comprising a plurality of node, wherein at least one of the nodes is configured to: (a) determine a target node from the plurality of nodes to be verified; verify the target node by validating a geographic location of the target node or a time of the target node; and (c) receive a token for verifying and validating the target node.

Abstract: Disclosed herein are systems and methods for providing and using a decentralized network using a blockchain. A provider (and/or miner) may provide network coverage to one or more devices in return for tokens on the blockchain. The blockchain may employ a proof-of-coverage scheme to verify (and even guarantee) that the miners are honestly representing the wireless network coverage they are providing. In some instances, the proof of coverage may require the providers to prove coverage periodically, upon demand, and/or at random intervals.

Abstract: Provided herein are systems and methods for implementing a network consensus for a blockchain network that is characterized by one or more, or all, of the following attributes: (1) implementation of a Proof-of-Coverage scheme; (2) lack of permission for nodes to participate in the network; (3) decentralization, with lack of incentives to centralize; (4) byzantine fault tolerance; (5) based on useful work to the network; (6) high confirmed transaction rate; and (7) censor-resistant transactions.

Abstract: Disclosed herein are systems and methods for facilitating data transmission using a decentralized consensus network. The system comprising: a verified and decentralized consensus network comprising a plurality of node, wherein at least one of the nodes is configured to: (a) determine a target node from the plurality of nodes to be verified; verify the target node by validating a geographic location of the target node or a time of the target node; and (c) receive a token for verifying and validating the target node.

Abstract: Various systems and methods are provided for maintaining an embedded network server. In one embodiment, one method includes the steps of providing a dynamic service loader in the embedded network server, receiving a service request to install a dynamic service in the embedded network server, and installing the dynamic service in the embedded network server with the dynamic service loader. The dynamic service may be installed in the embedded network server dynamically, thereby allowing other aspects of the embedded network server to operate without disruption.

Abstract: A method of processing a user interface component is provided and includes receiving one or more user interface components that can be communicated to a wireless device. A component risk level for each of the one or more user interface components is determined and assigned to each of the one or more user interface components. Each of the one or more user interface components can be digitally signed using an embedded risk code that indicates the assigned risk level. Further, the component risk level can be selected from a plurality of component risk levels. In a particular embodiment, the component risk level can be determined based on the type of the user interface component. Further, the component risk level can be determined based on a developer of the user interface component.

Abstract: A system and method for managing the deleting and reloading of software application components on a wireless device, such as a cellular telephone, personal digital assistant, pager, or other computer platform. The wireless device has one or more resident executable software applications wherein each application has one or more application components and application-associated data, such as software licenses and user-specific data. The wireless device selectively deletes one or more application components of the resident software applications without loss of the application-associated data to clear resources on the wireless device, and selectively prompts a backup device coupled to a wireless network to transmit deleted application components that need to be reinstalled on the wireless device to execute the application.

Abstract: System for application priority based on device operating mode. A method is provided for allocating a top visible resource on a device. The method includes receiving a request requesting allocation of the top visible resource to a requesting application, and determining that the top visible resource is allocated to an owning application. The method also includes associating owner information with requester information to form an arbitration request. The method also includes arbitrating the arbitration request to produce an arbitration decision that indicates that the top visible resource is to be allocated to the requesting application if the owner information indicates that the owning application is privileged and an identifier that identifies the requesting application is contained in a relinquish list associated with the owner information.

Abstract: A system for saving application state history information, containing an historical snap-shot of dynamic application state information associated with execution of a first application on a computing device. The application state history information is saved for use in a subsequent re-launch of the first application.

Abstract: Methods and apparatus for continuation passing in a virtual machine (VM). A method is provided for operating a virtual machine to provide continuation passing in a wireless device. The virtual machine comprises a stack memory. The method comprises encountering a context-creating trigger, constructing a continuation block in response to the trigger that comprises a stack fragment derived from the stack memory, encountering an evaluation instruction, and storing the stack fragment from the continuation block on the stack memory in response to the evaluation instruction.

Abstract: Various systems and methods are provided for maintaining an embedded network server. In one embodiment, one method includes the steps of providing a dynamic service loader in the embedded network server, receiving a service request to install a dynamic service in the embedded network server, and installing the dynamic service in the embedded network server with the dynamic service loader. The dynamic service may be installed in the embedded network server dynamically, thereby allowing other aspects of the embedded network server to operate without disruption.

Abstract: A method and system for modeling services available via a network include selecting a core service that is to be modeled, forming a discovery template that is specific to the selected core service, and automatically discovering the elements which cooperate to provide the core service. The discovery template includes instructions for implementing automated techniques for discovering service elements, and preferably services, which are anticipated as being cooperative in executing the core service. The system includes a number of discovery modules for generating outputs indicative of the services and service elements. A discovery engine is responsive to the discovery template to invoke the modules that are identified in the template as being relevant to discovering specified services and service elements. The template also identifies dependencies among the modules, so that the proper sequence of processing can be determined.