Patent Application
20220400368
The present invention relates generally to a method for optimizing mobile device roaming and optimization and in particular to a method and associated system for improving mobile device and software technology.
A first aspect of the invention provides a remote mobile device roaming optimization method comprising: receiving, by a processor of a hardware device from a user, a selection for specified services associated with a first mobile device provider for activation during travel to a specified geographical location associated with mobile device roaming attributes with respect to a mobile device of the user; generating, by the processor, a blockchain structure comprising details associated with the specified services; generating, by the processor, a first hash masking sensitive data of the user within the blockchain structure; detecting, by the processor via a plurality of sensors, that the user and the mobile device have traveled from an initial residence location to the specified geographical location; enabling for a second mobile device provider, by the processor in response to results of the detecting, access, via the first hash, to the details of the blockchain structure; analyzing, by the processor via the blockchain structure, common attributes between the first mobile device provider and the second mobile device provider; determining, by the processor in response to results of the analyzing, usage attributes associated with roaming usage of the mobile device at the specified geographical location with respect to the first mobile device provider and the second mobile device provider; and enabling, by the processor in response to the determining, operational functionality of the mobile device at the specified geographical location via roaming usage of a network of the second mobile device provider.
A second aspect of the invention provides a computer program product, comprising a computer readable hardware storage device storing a computer readable program code, the computer readable program code comprising an algorithm that when executed by a processor of hardware device implements a remote mobile device roaming optimization method, the method comprising: receiving, by the processor from a user, a selection for specified services associated with a first mobile device provider for activation during travel to a specified geographical location associated with mobile device roaming attributes with respect to a mobile device of the user; generating, by the processor, a blockchain structure comprising details associated with the specified services; generating, by the processor, a first hash masking sensitive data of the user within the blockchain structure; detecting, by the processor via a plurality of sensors, that the user and the mobile device have traveled from an initial residence location to the specified geographical location; enabling for a second mobile device provider, by the processor in response to results of the detecting, access, via the first hash, to the details of the blockchain structure; analyzing, by the processor via the blockchain structure, common attributes between the first mobile device provider and the second mobile device provider; determining, by the processor in response to results of the analyzing, usage attributes associated with roaming usage of the mobile device at the specified geographical location with respect to the first mobile device provider and the second mobile device provider; and enabling, by the processor in response to the determining, operational functionality of the mobile device at the specified geographical location via roaming usage of a network of the second mobile device provider.
A third aspect of the invention provides a hardware device comprising a processor coupled to a computer-readable memory unit, the memory unit comprising instructions that when executed by the computer processor implements a remote mobile device roaming optimization method comprising: receiving, by the processor from a user, a selection for specified services associated with a first mobile device provider for activation during travel to a specified geographical location associated with mobile device roaming attributes with respect to a mobile device of the user; generating, by the processor, a blockchain structure comprising details associated with the specified services; generating, by the processor, a first hash masking sensitive data of the user within the blockchain structure; detecting, by the processor via a plurality of sensors, that the user and the mobile device have traveled from an initial residence location to the specified geographical location; enabling for a second mobile device provider, by the processor in response to results of the detecting, access, via the first hash, to the details of the blockchain structure; analyzing, by the processor via the blockchain structure, common attributes between the first mobile device provider and the second mobile device provider; determining, by the processor in response to results of the analyzing, usage attributes associated with roaming usage of the mobile device at the specified geographical location with respect to the first mobile device provider and the second mobile device provider; and enabling, by the processor in response to the determining, operational functionality of the mobile device at the specified geographical location via roaming usage of a network of the second mobile device provider.
The present invention advantageously provides a simple method and associated system capable of optimizing remote mobile device roaming.
Typical data call roaming solutions provide cost reductions associated with invoice settlements but hinder a data residency aspect thereby constraining movement of data across borders. For example, service usage and billing rate data are used for authentication processes resulting in data (e.g., subscriber (user) subscription information, subscriber identity information via shared ledger, etc.) being shared between telecom operator networks which may be used to automatically define a usage/rate boundary of a subscriber via predefined rules. Likewise, a user travelling to a different (from a home region) region may enable use of a service such as access to a location via authentication with respect to a payment mechanism thereby requiring user data to be available at the location of service utilization. Actual services used and associated payment details are required to be bound to a visiting location. Associated information may have restricted availability with respect to a home location. Therefore, a process for resolving a conflict at a home location relating to services used by a subscriber may be implemented via a color coding process used to define different dimensions of services thereby masking actual data related to services while providing information required to handle conflicts. Furthermore, an authorization level of a subscriber (at a visiting location) using a service may be identified via a color scheme (instead of subscription information sharing). For example, a subscriber may be identified as associated with a hotel comprising multiple locations. The subscriber (at a visiting location) may attempt to access a service provided by a hotel (e.g., requesting access to the premise and utilize an associated food service available to members only). In response, the visiting location (hotel) may require information associated with the subscriber (e.g., service access attributes). Therefore, different levels of service may comprise different color tokens to identify the services a subscriber may access in combination with subscriber authentication. A multi-level color token system acting as a control mechanism in combination with subscriber initiated authentication may enable the subscriber to access the service. Likewise (at a home location) a multi-level color token and proof of authentication system, may enable a home operator to settle an invoice with a subscriber and with a visiting operator without actual data sharing and conflicts. Therefore system 100 is configured to execute a code implemented process for enabling billing integrity for mobile device roaming customers and service providers while complying with legal regulations with respect to data residency as follows:
1. Maintaining privacy of data by grounding a data hash with respect to a distributed ledger while actual data is stored within a private data as per a data residency requirement
2. Illustrating a correctness of a bill generated for customers without sharing sensitive data with a visiting telecom service prover (VTSP) or usage data with a home telecom service prover (HTSP).
3. Illustrating a correct settlement between the two operators (HTSP and VTSP) without sharing of data by the VTSP.
System 100 is further configured to:
1. Ensure compliance of data residency and personal data exchange in cross border scenarios.
2. Resolve billing integrity issues arising due to data residency & usage in cross border transactions.
3. Ensure correctness of a bill generated for customers without sharing a data plan with a VTSP or usage data with a HTSP.
4. Ensure compliance of data residency & personal data exchange during a process for consuming edge services such as visual consent identity services associated with data exchange during edge service consumption and cross border transactions.
Therefore, system 100 is configured to enable token and sub-token definitions required for final settlement as follows:
A data grounding step is initiated such that an HTSP generates a hash masking a service plan with respect to a customer and ledger (e.g., token types, function of charge computation, etc.). Additionally, the HTSP generates a hash masking an agreement with an VTSP (e.g., token types, charge computation logic, etc.). Subsequently, a VTSP provider generates a hash masking data usage of a customer with respect to a ledger (e.g., token types, quantity, etc.). Additionally, parties may endorse the aforementioned hashes. A corrected bill generation step is further executed for a customer such that a customer self generates a bill without proof that the bill is consistent with the aforementioned hashes. Likewise, the corrected bill generation step may be executed by the VTSP with respect to the HTSP such that the VTSP generates a bill for the HTSP that is consistent with the aforementioned hashes.
System 100 of
System 100 is enabled to execute a remote mobile device roaming optimization process via execution of blockchain and hash structures as follows:
The process is initiated when a user registers with a home telecom service provider to set-up an associated account and services. Likewise, the user may provide customer information applicable in each geographical location (e.g., country). Additionally, the user may sign up for several value-added services requiring user preference selections and key data associated with the customer. Subsequently (when the user is planning to travel to another country), the user may subscribe to a roaming package from the home telecom service provider. Therefore, the user may select services (including base and value-added services) for execution during a duration of roaming. In response, the home telecom service provider initiates the account and contract details (e.g., roaming) as a blockchain structure and obtains a hash structure including the user's personal details, services subscribed, etc. A color coding scheme may be implemented to represent a level of information shared for a service.
When the user travels to a new country and enables a roaming pack, the visiting telecom service provider accesses contract details from the blockchain structure (provided by the home telecom service provider) as a hash structure in a shared ledger. The blockchain structure is configured to automatically analyze a contract between the home telecom service provider and a visiting telecom service provider with respect to predefined rules, a value/boundary for usage for the subscriber with respect to the contract. System 100 allows subscription information, a subscriber's identity, and a usage limit based on the subscription with the home telecom service provider to be made available to the visiting telecom service provider. Subsequently (when the user reaches threshold of limit of usage based on a roaming subscription contract with the home telecom service provider), the visiting telecom service provider is enabled to obtain information from the blockchain structure and associated hash structure and notify the subscriber that a roaming limit has been exceeded. Accessed information is protected by the visiting telecom service provider based on local in-country data protection regulations stored within a private database (e.g., database 115 in
The process is initiated when the user provides identification for service authentication. The services are registered within the roaming contract such that when the user accesses the services via their mobile device, a visiting telecom service provider submits a request for user related information obtained from a hash structure within a shared ledger. Subsequently, the user consumes the services and the visiting telecom service provider registers the associated transaction and attaches a color code schema to transaction information and a service price within the hash structure provided by visiting telecom service provider to the home telecom service provider. Additionally, the user orders food from a global food chain and identifies themselves for the order delivery (i.e., a peer to the visiting telecom service provider) with a same mobile based service they use at a home location. Shared information is labeled via a color code identifier used as a tag by the visiting telecom service provider with respect to the hash structure. When the user returns home a bill is generated for services consumed in the visiting location. The bill illustrates the color codes associated with different transactions and associated price, etc. The user is enabled to track through the tags to determine what information has been exchanged and when the service was consumed. The home telecom service provider uses this information to bill the user and settle fees with the visiting telecom service provider. If the user locates a dispute with respect to a specified service as a paid service (e.g., using specialized equipment in the gym) via the color code schema, the home telecom service provider may be configured to track a transaction with respect to the service usage provided to the user for acceptance of the service price. The visiting telecom service provider may charge the home telecom service provider for usage costs beyond a normal limit at a premium price. A blockchain contract (associated with the blockchain structure) contains a limit associated with the home telecom service provider. A resulting dispute may be easily resolved by the home telecom service provider via analysis of the blockchain. Likewise, the visiting telecom service provider may generate charges for various services consumed via analysis of the hash structure shared with the home telecom service provider. The visiting telecom service provider may additionally generate a cross-charge bill for the home telecom service provider. The aforementioned functionality may be independent from different benefits that the home telecom service provider may provide to the user and which may not be passed on to the user when the user requests the bill from the home telecom service provider.
The following first scenario is associated with a protocol for resolving a billing dispute associated with a customer self-generating a roaming bill based on private data associated with a consumption of services. The first scenario is initiated when a customer signs a roaming contract with a home telecom service provider. In response, the customer utilizes different services at a roaming destination and the customer self-computes a bill and initiates a payment. The aforementioned first scenario enables protection for customer usage data and any billing disputes may be resolved without revealing any private data.
The following second scenario is associated with a protocol for resolving a billing dispute associated with a VSTP self-generating a bill for HTSP based on user data consumption. The second scenario is initiated when a VTSP roaming contract with home telecom service provider is executed and a customer utilizes different services at a roaming destination. In response, the VTSP self-computes a bill and HTSP initiates a payment. The aforementioned second scenario enables protection for customer usage data and any billing disputes may be resolved without revealing any private data.
In step 202, a blockchain structure comprising details associated with the specified services is generated. In step 204, a first hash is generated. The first hash is configured to mask sensitive data of the user within the blockchain structure. In step 208, a plurality of sensors detects that the user and mobile device have traveled from an initial residence location to the specified geographical location. In step 210, access to details of the blockchain structure is enabled for a second mobile device provider. The access is enabled (via the first hash) in response to results of the detection. In step 212, common attributes between the first mobile device provider and the second mobile device provider are analyzed via the blockchain structure. In step 214, usage attributes are determined in response to results of the analysis of step 212. The usage attributes are associated with roaming usage of the mobile device at the specified geographical location with respect to the first mobile device provider and second mobile device provider. In step 216, operational functionality of the mobile device at the specified geographical location is enabled via roaming usage of a network of the second mobile device provider in response to step 214.
In step 218, it is detected that the mobile device has exceeded a usage threshold associated with the roaming attributes with respect to a contract between the user and the first mobile device provider. In response, a second hash is generated. The second hash masks residency related sensitive data of the user and indicates that the mobile device has exceeded the usage threshold. Subsequently, the second hash is transmitted to the first service provider. Alternatively (in step 218), it is detected that the mobile device has accessed additional services during the roaming usage. In response, a second hash is generated. The second hash indicates that the mobile device has accessed additional services. Subsequently, the second hash is transmitted to the first service provider.
In step 220, it is detected (via sensors) that the user and mobile device have traveled from the specified geographical location back to the initial residence location and contract attributes are tracked via digital tags. The contract attributes are associated with the first service provider with respect to the roaming usage. Results of the tracking process may be used to determine a dispute associated with services enabled during the roaming usage such that terms of the contract attributes may be modified. Additionally or alternatively, results of the tracking process may be used to determine a dispute associated with compensation attributes associated with the roaming usage such that terms of the contract attributes may be modified. Additionally, the first hash and second hash may be analyzed and compensation attributes associated with the roaming usage may be generated. Likewise, class indicators may be generated. The class indicators are associated with shared user information with respect to the roaming usage for enabling ease of consumption correlation actions.
Aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module,” or “system.”
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing apparatus receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, spark, R language, or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, device (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing device, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing device, or other device to cause a series of operational steps to be performed on the computer, other programmable device or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable device, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be accomplished as one step, executed concurrently, substantially concurrently, in a partially or wholly temporally overlapping manner, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
The computer system 90 illustrated in
In some embodiments, rather than being stored and accessed from a hard drive, optical disc or other writeable, rewriteable, or removable hardware memory device 95, stored computer program code 84 (e.g., including algorithms) may be stored on a static, nonremovable, read-only storage medium such as a Read-Only Memory (ROM) device 85, or may be accessed by processor 91 directly from such a static, nonremovable, read-only medium 85. Similarly, in some embodiments, stored computer program code 97 may be stored as computer-readable firmware 85, or may be accessed by processor 91 directly from such firmware 85, rather than from a more dynamic or removable hardware data-storage device 95, such as a hard drive or optical disc.
Still yet, any of the components of the present invention could be created, integrated, hosted, maintained, deployed, managed, serviced, etc. by a service supplier who offers to improve mobile device and software technology associated with generating a blockchain structure and associated hash masking details associated with specified services, analyzing common attributes between mobile device providers, determining usage attributes associated with roaming usage of a mobile device with respect to the mobile device providers, and enabling operational functionality of the mobile device at via roaming usage of a network of one of the mobile device providers. Thus, the present invention discloses a process for deploying, creating, integrating, hosting, maintaining, and/or integrating computing infrastructure, including integrating computer-readable code into the computer system 90, wherein the code in combination with the computer system 90 is capable of performing a method for enabling a process for improving mobile device and software technology associated with generating a blockchain structure and associated hash masking details associated with specified services, analyzing common attributes between mobile device providers, determining usage attributes associated with roaming usage of a mobile device with respect to the mobile device providers, and enabling operational functionality of the mobile device at via roaming usage of a network of one of the mobile device providers. In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising, and/or fee basis. That is, a service supplier, such as a Solution Integrator, could offer to enable a process for improving mobile device and software technology associated with generating a blockchain structure and associated hash masking details associated with specified services, analyzing common attributes between mobile device providers, determining usage attributes associated with roaming usage of a mobile device with respect to the mobile device providers, and enabling operational functionality of the mobile device at via roaming usage of a network of one of the mobile device providers. In this case, the service supplier can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service supplier can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service supplier can receive payment from the sale of advertising content to one or more third parties.
While
It is to be understood that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure that includes a network of interconnected nodes.
Referring now to
Referring now to
Hardware and software layer 60 includes hardware and software components. Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.
Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.
In one example, management layer 80 may provide the functions described below. Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may include application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 87 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 88 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.
Workloads layer 101 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 102; software development and lifecycle management 103; virtual classroom education delivery 133; data analytics processing 134; transaction processing 106; and for improving mobile device and software technology associated with generating a blockchain structure and associated hash masking details associated with specified services, analyzing common attributes between mobile device providers, determining usage attributes associated with roaming usage of a mobile device with respect to the mobile device providers, and enabling operational functionality of the mobile device at via roaming usage of a network of one of the mobile device providers 107.
While embodiments of the present invention have been described herein for purposes of illustration, many modifications and changes will become apparent to those skilled in the art. Accordingly, the appended claims are intended to encompass all such modifications and changes as fall within the true spirit and scope of this invention.
