CLAIM OF PRIORITY

[0001] This application claims priority to U.S. Provisional Application No.

62/789,912, filed on January 8, 2019, the contents of which are hereby incorporated by reference.

TECHNICAL FIELD

[0002] This disclosure relates to hydraulic fracturing operations.

BACKGROUND

[0003] Natural rocks are discontinuum materials due to the existence of various cracks, fractures, weak planes, or discontinuities (for example, a joint, foliation, schistosity, gneissosity, vein, dyke, bedding plane, or lamination). Due to the presence of discontinuities, natural rocks show anisotropy and heterogeneity, which affect the mechanical properties of rocks.

[0004] Oil and natural gas production in unconventional reservoirs depend on a stimulated rock volume (SRV) that is defined by the hydraulic fracture geometry (for example, height, length, and aperture). The growth of these fractures is controlled by the anisotropy and heterogeneity of the reservoir and its mineral composition. However, predicting the SRV can be difficult if the intended fracture height is reached during stimulation.

SUMMARY

[0005] Modeling the SRV is used to identify fraccable zones and fracture barriers (also referred to as“frac barriers”) along the direction of a wellbore. Fraccable zones are the favorable propagation of hydraulically induced fractures. Fracture barriers, on the other hand, stop hydraulic fracture propagation, perhaps by dissipating the energy for propagating the fracture. Given the information provided by the SRV model, a more accurate model is better for more accurate engineering decisions, successful hydraulic fracturing operations, and improved business performance. Traditionally, a stress contrast profile is used for modeling the SRV. However, this approach has several limitations, particularly in complex formations.

[0006] The present disclosure is directed to a strength-based method for accurately modeling a formation to identify fracture barriers in the formation. The strength-based method is more accurate than the stress-based method, particularly in complex formations. Rather than generating a stress contrast profile, as is done in the stress-based method, the strength-based method generates a strength contrast profile based on rebound hardness values and mineralogy, which can be used to derive accurate indicators of the rock’s mechanical properties. The strength contrast profile can be used to identify fracture barriers in the formation.

[0007] Aspects of the subject matter described in this specification may be embodied in methods that include operations for identifying fracture barriers in a well. The operations include converting rebound hardness values of a rock specimen from the well to unconfmed compressive strength (UCS) values, where each of the rebound hardness values corresponds to a respective coordinate of a measurement grid imposed on the rock specimen. The operations further include, for each column of the grid, plotting the UCS values versus depth. Further, the operations include mapping, based on a maximum UCS value and a minimum UCS value, a relative strength contour plot for the rock specimen. Yet further, the operations include mapping, based on a fixed strength range, an absolute strength contour plot for the rock specimen. In addition, the operations include determining, based on the relative strength contour, the absolute strength contour, and mineralogy of the rock specimen, that the rock specimen is indicative of a fracture barrier in the well.

[0008] The previously-described implementation is implementable using a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium. These and other embodiments may each optionally include one or more of the following features.

[0009] In a first aspect, where the measurement grid is a square grid pattern, and further including: imposing the square grid pattern on the rock specimen; developing a coordinate system depending on mineral particle size distributions or data resolution of a device used to measure rebound hardness values; and measuring, at intersections in the square grid pattern, rebound hardness values of the rock specimen.

[0010] In a second aspect, wherein converting rebound hardness values of the rock specimen to UCS values includes: if the rock specimen is a 1/3 slab section core: using a first empirical calibration equation y = 3.7727 e ^{0 005x} to convert the rebound hardness values to UCS values, and if the rock specimen is a 2/3 butt section cores: using a second empirical calibration equation y = 2.1454e ^{0 0058} to convert the rebound hardness values to UCS values.

[0011] In a third aspect, further including: plotting, using UCS values and corresponding depths for a plurality of rock specimens from the well, a strength contrast profile for the well, wherein determining that the rock specimen is indicative of a fracture barrier in the well is further based on the strength contrast profile for the well.

[0012] In a fourth aspect, further including: applying a rock strength classification to the strength contrast profile to quantitatively classify the strength contrast profile.

[0013] In a fifth aspect, where the mineralogy of the rock specimen is a micro-

X-ray fluorescence (m-XRF) elemental map generated using m-XRF analysis of the rock specimen.

[0014] In a sixth aspect, further including updating fracking parameters based on the fracture barrier.

[0015] The details of one or more implementations of the subject matter of this specification are set forth in the Detailed Description, the accompanying drawings, and the claims. Other features, aspects, and advantages of the subject matter will become apparent from the Detailed Description, the claims, and the accompanying drawings.

DESCRIPTION OF DRAWINGS

[0016] FIG. 1 is a schematic diagram of a rebound hardness tester, according to some implementations of the present disclosure.

[0017] FIG. 2A and 2B are plots of unconfined compressive strength (UCS) versus empirical rebound hardness values for 1/3 slab section cores and 2/3 butt section cores, respectively, according to some implementations of the present disclosure.

[0018] FIG. 3 is a flowchart of a method for identifying fracture barriers, according to some implementations of the present disclosure.

[0019] FIGs. 4A, 4B, and 4C are example images of preparing a rock sample and taking rebound hardness measurements of the rock sample, according to some implementations of the present disclosure. [0020] FIG. 4D is a plot of UCS values versus depth for the rock sample of

FIG. 4A, according to some implementations of the present disclosure.

[0021] FIG. 4E is a plot of average UCS values versus depth for the rock sample of FIG. 4A, according to some implementations of the present disclosure.

[0022] FIG. 4F is a relative strength contour plot for the rock sample of FIG. 4 A, according to some implementations of the present disclosure.

[0023] FIG. 4G is an absolute strength contour plot for the rock sample of

FIG. 4A, according to some implementations of the present disclosure.

[0024] FIGS. 5A, 5B, 5C, 5D, 5E, and 5F illustrate an example of identifying a fracture barrier in a rock sample, according to some implementations of the present disclosure.

[0025] FIGS. 6A, 6B, 6C, 6D, 6E, 6F, and 6G illustrate another example of identifying a fracture barrier in a rock sample, according to some implementations of the present disclosure.

[0026] FIG. 7 is a strength contrast profile for identifying fracture barriers, according to some implementations of the present disclosure.

[0027] FIG. 8 is a strength contrast profile with rock strength classifications, according to some implementations of the present disclosure.

[0028] FIG. 9 illustrates an example computing environment, according to some implementations of the present disclosure.

[0029] Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

[0030] Traditionally, hydraulic fracturing has employed a stress contrast profile generated by elastic properties (for example, Young’s modulus and Poisson’s ratio) for modeling a subsurface. When a stress contrast profile is generated, completion engineers input the profile into a fracture design software for modeling the dimension and geometry of hydraulically induced fractures. This approach detects fracture barrier regions where there is a threshold difference of minimum horizontal stress. This is based on the finding that energy for propagating a hydraulically induced fracture will dissipate when it meets a formation under a threshold minimum horizontal stress. Conversely, if a constant range of minimum horizontal stress continues throughout a formation, a hydraulically induced fracture can continue to propagate in different directions (for example, vertically and horizontally). There are at least two limitations with this approach.

[0031] First, the threshold stress contrast indicative of a fracture barrier varies based on different factors (for example, location, geological, stress, and structural conditions), but stress contrast profiles do not account for these factors. For example, a first formation that contains many thin beds of different lithology may have a greater stress contrast than a second formation that is divided by different rock types. In this example, a stress contrast of 3000 - 4000 pounds per square inch (psi) is indicative of a fracture barrier in the first formation, and a stress contrast less than 1000 psi is indicative of a fracture barrier in the second formation. As such, relative stress contrast is not clearly indicative of fracture barriers since the threshold or range may be different under different reservoir conditions.

[0032] A second limitation of the existing approach is that elastic properties indicate a rock’s deformation, which is not an accurate indicator of the rock’s mechanical properties. In rock mechanics, a rock’s deformation is represented using Young’s modulus and Poisson’s ratio. Young’s modulus defines a rock’s resistance to axial stress and Poisson’s ratio defines a rock’s expansion to axial shrinkage when the rock is under axial stress. In hydraulic fracturing, Young’s modulus is interpreted as the rock’s sustainability of a fracture opened and Poisson’s ratio is interpreted as an easiness by which the rock propagates a fracture. Generally, the greater the value of Young’s modulus the better the fractures are opened, and the lesser the value of Poisson’s ratio the better the fractures are propagated. However, these values are neither indicative of rock strength nor fracture toughness, which are better indicators of a rock’s mechanical properties. Strength can be defined as a peak stress level at the point of rock failure. Strength can quantify how strong or weak a rock is in absolute terms (as opposed to relative terms, as in Young’s modulus and Poisson’s ratio). Fracture toughness can be defined as a rock’s resistance to fracture extension. Under this definition, the greater the fracture toughness, the greater the amount of energy that is needed to propagate a fracture in a rock.

[0033] Due to its limitations, the existing approach cannot be accurately used to identify fracture barriers, particularly in unconventional formations. For example, unconventional formations, such as shales, can include ductile clay minerals. Such ductile rocks require more energy to initiate a crack, propagate a fracture, and sustain the resulting aperture. The existing approach would not accurately identify fracture barriers (due to the described limitations). Rather, as described in this disclosure, rock strength can be used to more accurately identify fracture barriers. However, measuring rock strength can be difficult in unconventional reservoirs.

[0034] The present disclosure is directed to a strength-based method that uses a rebound hardness test and mineralogy to identify fracture barriers in a formation. In an implementation, a slabbed rock sample is retrieved from a well. Non-destructive rebound hardness measurements are collected across the rock surface, which is specifically gridded, to provide an estimate of the rock strength. The collected rebound hardness values are converted into unconfmed compressive strength (UCS) values. The UCS values are used to represent the rock’s mechanical characteristics using, for example, contour maps mapped across the surface of the rock. The contour maps are correlated to the mineralogy of the rock surface, which is quantified and mapped using, for example, micro-X-ray fluorescence analysis. Using the mineralogy of the rock, the UCS can be correlated to the changing mineral content of the rock surface, which further facilitates an assessment of the strength of the rock surface.

[0035] This non-destructive method addresses the challenge of relating core scale measurements to reservoir-scale analysis to improve hydraulic fracturing designs in unconventional source rocks. For example, the method reveals differences in the rock strength, which is indicative of where fractures either propagate or fail due to fracture barriers. In some implementations, the method utilizes an Equotip® hardness tester (illustrated in FIG. 1), which was originally developed by Dietmar Leeb in the 1970s to measure rebound hardness numbers of metals. The unitless rebound hardness numbers can be converted to the corresponding UCS values using the empirical calibration equations developed for unconventional rocks. Example results of the conversion for different rock types and the empirical calibration equations are illustrated in FIGs. 2A and 2B. FIG. 2A illustrates the equation and results for 1/3 slab section cores, and FIG. 2B illustrates the equation and results for 2/3 butt section cores.

[0036] FIG. 3 is an example of a method 300 for identifying fracture barriers in a well, according to some implementations. For clarity of presentation, the description that follows generally describes method 300 in the context of FIGS. 1, 2A-2B, 4A-4G, 5A-5F, 6A-6G, 7, 8, and 9. However, it will be understood that process 300 may be performed, for example, by any other suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of process 300 can be run in parallel, in combination, in loops, or in any order.

[0037] Method 300 is described by applying the steps of the method to an example rock sample illustrated in FIG. 4A. FIGS. 4B-4G illustrate the steps of the method 300 applied to the rock sample of FIG. 4A.

[0038] Method 300 begins at step 302 where rebound hardness values for a rock sample (illustrated in FIG. 4A) from the well are determined. In an implementation, a grid pattern is imposed on the rock sample and rebound hardness values are determined at each intersection of the grid pattern, as illustrated in FIGS. 4B and 4C. The grid pattern can form squares, rectangles, or other patterns without departing from the scope of the disclosure. As an example, the grid in FIG. 4B is a 5 millimeter (mm) by 5 mm square grid pattern. Accordingly, and as shown by the dents in FIG. 4C, the rebound hardness test is performed on the sample rock every 5mm by 5mm. In some implementations, the rebound hardness values are determined using, for example, an Equotip® hardness tester 100 illustrated in FIG. 1.

[0039] At step 304, the rebound hardness values are converted to UCS values.

In an example, empirical calibration Equation (1) is used to convert the unitless rebound hardness numbers to UCS values for 1/3 slab section cores and empirical calibration Equation (2) is used for 2/3 butt section cores:

In Equations (1) and (2), x is the input rebound hardness values. The determined UCS values are then plotted versus depth. As described in this disclosure, the UCS plots are used to identify potential fracture barriers by identifying where the strength difference is dominant in the rock sample. FIG. 4D illustrates an example UCS values versus depth plot for each column in the grid of FIG. 4B.

Table 1: Engineering Classification of Rock by Strength

[0040] At step 306, and as illustrated in FIG. 4E, the average UCS value for each depth is determined and plotted. In this example, the UCS values vary between about 2500 psi and 4000 psi, which indicates a very low level of strength according to the engineering classifications (based on UCS values) of intact rocks. Example engineering classification tables are shown in Table 1 and Table 2. The rock strength classification shown in these tables is used to quantitatively classify the UCS values.

Table 2: Uniaxial Compressive Strength

Class Level of Strength MPa psi

[0041] At step 308, a range of UCS values is determined. In an example, the range of UCS values is determined by determining minimum and maximum UCS values. In another example, the range of UCS values is determined by determining a minimum average UCS value and a maximum average UCS value.

[0042] Next, at step 310, a relative strength contour is plotted using the minimum and maximum UCS values. In an implementation, the relative strength contour maps the strength range between the minimum and maximum values for the rock sample. In the example relative strength contour illustrated in FIG. 4F, the maximum and minimum UCS values are determined from the values plotted in FIG. 4D. As shoxvn in FIG. 4D, the maximum and minimum UCS values in this example are 5330 psi and 1850 psi, respectively. In FIG. 4F, the relative strength contour is plotted using this range, perhaps using color or shading coding (for example, lower strengths are depicted in blue and greater strengths are depicted in red).

[0043] The advantage of the relative strength contour is to visualize strength contrasts in each rock sample that is collected. However, relative strength contours highlight the contrast with different amounts of strength from different samples (since different samples have different maximum and minimum UCS values). When the results from all samples in a well need to be compared, the respective relative strength contour of each sample does not provide a reference for comparison due to the case-by- case results.

[0044] In order to overcome the limitation of the relative strength contour, at step 312, an absolute strength contour is plotted for a fixed strength range. The absolute strength contour for a well is based on a global scale. As such, the absolute strength contour resolves the disadvantage of the relative strength contour. FIG. 4G illustrates an example absolute strength contour. In this example, the absolute strength contour is mapped at a fixed range between 0 to 13,000 psi. Given that the UCS values for the rock sample are mapped at the global scale, the UCS values for the rock sample can be compared to other UCS values for other rock samples collected from the well. In the example of FIG. 4G, 13,000 psi is a maximum that was selected based on the finding that UCS values of rock specimens generally do not exceed this value. If other rock samples at a different location show greater UCS values, then the upper limit will be increased. Contrarily, if rock samples at another location have much lower UCS values, the upper limit will be decreased. This is because the relative strength contour contrasts the difference in the strength at each case (each sample).

[0045] The advantage of the absolute strength contour is that the results of all the samples from a well can be compared with a clear and constant condition. However, absolute strength contours do not depict a weak contrast when a rock has a lower strength range, but the contrast is shown in a relative strength contour for the rock. Therefore, it is important to use both the relative and the absolute strength contour plots to understand the strength on a local and global scale in a well.

[0046] At step 314, low strength and high strength intervals are identified. In an implementation, the relative strength contour and the absolute strength contour are analyzed for low strength and high strength intervals. In an example, a high strength interval (for example, greater than a threshold) is indicative of a fracture barrier. In another example, a clear boundary between a high strength contrast interval and a low strength contrast interval is indicative of a fracture barrier. That is, there is a significant strength contrast (for example, greater than a threshold) across the clear boundary. Another feature indicative of a fracture barrier is a region of substantial thickness (for example, greater than a threshold) of both high and low strength intervals. Thus, in some examples, thickness of the intervals may be determined.

[0047] At step 316, a mineralogical analysis is mapped to the rock sample. In an implementation, the mineralogical analysis is a micro-X-ray fluorescence (m-XRF) analysis of the rock sample that generates a m-XRF elemental map. The m-XRF elemental map is indicative of mineral types and respective amounts of the mineral types for a measurement area. In an example, the measurement area for the mineralogical analysis is identical to the measurement area that was used for the rebound hardness test (for example, a 5 mm by 5 mm square grid). In some implementations, elemental maps can be used to quantify and map mineralogy and organic matter in source rocks at the nanometer scale. The mineralogical analysis addresses the challenge of using pore- scaled and core-scaled analysis to predict reservoir properties. Thus, it pursues the non destructive quantification of the mineral matrix that can be used to determine rock properties of the reservoir. In short, it can quantify mineralogy at the core scale for identifying fracture barriers with the combination of rebound hardness test.

[0048] At step 318, based on the relative strength contour, the absolute strength contour, and the mineralogical analysis of the rock sample, a determination is made whether a fracture barrier exists. In an example, the relative strength contour is analyzed for any features indicative of fracture barriers (for example, a significant strength contrast). The relative strength contour assists in identifying fracture barriers at each specific depth at a local scale. In the example of FIG. 4F, the relative strength contour does not include any strength-based features indicative of a fracture barrier. As such, the relative strength contour of FIG. 4F is indicative of a fraccable interval because a fracture barrier is not detected. Similarly, the absolute strength contour of FIG. 4G does not include any strength-based features indicative of a fracture barrier. As result, the absolute strength contour of FIG. 4G confirms that the rock sample is indicative of a fraccable interval because a fracture barrier is not detected in the rock sample.

[0049] In an implementation, the mineralogical analysis is used as an additional assessment of the strength of the rock sample. By way of example, a strong mineral of calcite can be distributed along a certain horizontal layer with substantial thickness, which contributes to an abrupt increase in rock strength. As a result, there is a substantial strength contrast above and below this layer, which results in this layer becoming a fracture barrier. As will be illustrated in the examples of FIGS. 5 and 6, a mineralogical analysis of a rock sample can be used jointly with the relative and absolute strength contours to identify fracture barriers.

[0050] FIGS. 5A-5F (collectively referred to as FIG. 5) and FIGS. 6A-6G (collectively referred to as FIG. 6) illustrate two examples of identifying fracture barriers in respective wells using respective rock samples from the wells. In an implementation, the method 300 of FIG. 3 is applied to the respective rock samples. In both examples, it is determined that the respective rock sample has a significant strength contrast based on the following observations from the results applying the method 300 to the rock samples. First, there is a clear boundary between high and low strength intervals in the strength contours of the rock samples. Second, there is a significant strength contrast of nearly 6000 psi between the high and low strength intervals. Third, both the high and low strength intervals have a substantial thickness.

[0051] Starting with the example of FIG. 5, FIGs. 5A-5D illustrate results that are generated based on the rebound hardness test. FIG. 5A illustrates a plot of the UCS for each column versus depth for the rock sample. FIG. 5B illustrates a plot of the average UCS at each depth of the rock sample. FIG. 5C illustrates a relative strength contour for the rock sample, and FIG. 5D illustrates an absolute strength contour for the rock sample.

[0052] As described previously, the relative strength contour and the absolute strength contour can be used to identify a frac barrier in a well. In particular, the relative strength contour is analyzed to determine whether a strength contrast exists locally in the rock sample. In an implementation, a strength contrast is identified in the relative strength contour by analyzing a color-coded (or shade intensity coded) relative strength contour plot for a threshold strength contrast. The threshold strength contrast can be identified manually be a user or can be identified automatically by a computing device by comparing strength contrasts to a predetermined threshold (for example, provided by a user). In an example, the predetermined threshold is 3000 psi at closely located mineralogical layers or geological structures. In the example of FIG. 5, the strength contrast is identified by detecting a strength difference (contrast) greater than 3000 psi at closely located mineralogical layers or geological structures. Note that the predetermined threshold can be a value other than 3000 psi. Once the threshold strength contrast is identified locally, the absolute strength contour is analyzed to determine how the locally identified strength contrast compares on a global scale (that is, compared to other samples collected from the well). For example, the strength contrast is compared to the global scale (of the well) by analyzing a color-coded (or shade intensity coded) absolute strength contour plot for a threshold strength contrast, which can be identified manually by a user or can be identified automatically by a computing device by comparing strength contrasts to a predetermined threshold.

[0053] Additionally, a mineralogical analysis is performed on the rock sample.

In an example, the mineralogical analysis is performed on the frac barrier that was identified using the rebound hardness test. As explained previously, the mineralogical analysis can be used to confirm that the frac barrier identified using the rebound hardness test is in fact a frac barrier. Alternatively, the mineralogical analysis can be used to characterize the frac barrier.

[0054] FIG. 5E and FIG. 5F illustrate the mineralogical analysis. In particular,

FIG. 5E shows a cal cite vein (that is, a boundary) with a thickness of over 10 mm found in the rock sample. In an implementation, an X-ray diffraction (XRD) analysis is performed on the calcite vein of FIG. 5E. FIG. 5F illustrates the results of the XRD analysis. As shown in FIG. 5F, the XRD analysis indicates that the calcite vein is 90% calcite, which is a brittle mineral. This analysis determined that a strong mineral of calcite is distributed along a certain horizontal layer with substantial thickness (for example, greater than 10 mm). The calcite contributed to the abruptly increasing the rock strength. As a result, there is a substantial strength contrast above and below this layer, further indicating that the identified layer is a frac barrier.

[0055] Turning to the example of FIG. 6, FIG. 6A-6D illustrate results that are generated based on the rebound hardness test. FIG. 6A illustrates a plot of the UCS values for each column in the specimen, and FIG. 6B illustrates a plot of the average UCS at each depth of the specimen. FIG. 6C illustrates a relative strength contour map of the rock specimen, and FIG. 6D illustrates an absolute strength contour map of the rock specimen. As described in the example of FIG. 5, the relative strength contour map and the absolute strength contour map can be used to identify a fracture barrier.

[0056] Additionally, a mineralogical analysis can be performed on the rock sample. In this example, an XRD analysis was conducted at three points, as shown in FIG. 6E. This analysis directly correlates the XRD results with the individual UCS at the same spot. In an example, the spots can be selected at three different levels of UCS values, such as a greater strength spot, a transition strength spot, and a lower strength spots. Doing so facilitates investigating the different mineral compositions and comparing them at the three different levels. FIG. 6F illustrates a scan of the rock sample that shows that the rock sample includes a boundary between different minerals, which results in the contrast of strength. The XRD analysis depicted in FIG. 6G indicates that the mineral composition of the frac barrier is 94.7% calcite.

[0057] In some implementations, a plurality of rock samples collected and analyzed from a well can be used to generate a strength contrast profile for the well. The strength contrast profile can be used to identify potential frac barriers in the well. In particular, the strength contrast profile enables easy detection of features indicative of frac barriers and determination of the thickness of features. In an implementation, a rock strength classification system of rock engineering is applied to the strength contrast profile. This can contribute the engineering designs and management of frac operations quantitatively. FIG. 7 illustrates an example strength contrast profile for a well. FIG. 8 illustrates an example strength contrast profile to which a rock strength classification has been applied.

[0058] FIG. 7 is a plot 700 of UCS values versus depth. As illustrated, the UCS scale is between 0 - 15000 psi for the strength contrast profile. In particular, the plot 700 represents a strength contrast profile for identifying potential fracture barriers. In an example, a greater strength difference with a closer distance can be identified as a fracture barrier. Thus, this logging of the strength contrast profile can bring additional value for identifying fracture barriers. In FIG. 7, individual UCS values from each specimen from the well and the mean UCS value from each specimen are logged. The mean UCS plot represents the trend of formation strength. Specifically, in FIG. 7, the individual UCS values for 25 samples and the mean of the UCS values are plotted over depth.

[0059] FIG. 8 illustrates a plot 800 of UCS values versus depth. In particular, the plot 800 is generated by applying a rock strength classification to the plot 700, perhaps by using the rock strength classification system of rock engineering from Tables 1 and 2. As shown in FIG. 8, the plot 800 enables management of fracture operations quantitatively since the strength of the rocks can be easily extracted from the plot 800.

[0060] FIG. 9 shows an example of a generic computing device 900 and a generic mobile computing device 950, which are used with the techniques described here. Computing device 900 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Mobile computing device 950 is intended to represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, and other similar computing devices. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and claimed in this document.

[0061] Computing device 900 includes a processor 902, memory 904, a storage device 906, a high-speed interface 908 connecting to memory 904 and high-speed expansion ports 910, and a low-speed interface 912 connecting to low-speed bus 914 and storage device 906. Each of the components 902, 904, 906, 908, 910, and 912, are interconnected using various busses, and are mounted on a common motherboard or in other manners as appropriate. The processor 902 processes instructions for execution within the computing device 900, including instructions stored in the memory 904 or on the storage device 906 to display graphical information for a GUI on an external input/output device, such as display 916 coupled to high-speed interface 908. In other implementations, multiple processors, multiple buses, or both are used, as appropriate, along with multiple memories and types of memory. Also, multiple computing devices 900 are connected, with each device providing portions of the necessary operations (for example, as a server bank, a group of blade servers, or a multi-processor system).

[0062] The memory 904 stores information within the computing device 900.

In one implementation, the memory 904 is a volatile memory unit or units. In another implementation, the memory 904 is a non-volatile memory unit or units. The memory 904 may also be another form of computer-readable medium, such as a magnetic or optical disk.

[0063] The storage device 906 is capable of providing mass storage for the computing device 900. In one implementation, the storage device 906 may be or contain a computer-readable medium, such as a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, including devices in a storage area network or other configurations. A computer program product may be tangibly embodied in an information carrier. The computer program product may also contain instructions that, when executed, perform one or more methods. The information carrier is a computer- or machine-readable medium, such as the memory 904, the storage device 906, or a memory on processor 902.

[0064] The high-speed interface 908 manages bandwidth-intensive operations for the computing device 900. The low-speed interface 912 manages lower bandwidth intensive operations. Such allocation of functions is exemplary only. In one implementation, the high-speed interface 908 is coupled to memory 904, display 916 (for example, through a graphics processor or accelerator), and to high-speed expansion ports 910, which accepts various expansion cards (not shown). In the implementation, low-speed interface 912 is coupled to storage device 906 and low-speed bus 914. The low-speed expansion port, which may include various communication ports (for example, USB (Universal Serial Bus), Bluetooth, Ethernet, wireless Ethernet) may be coupled to one or more input/output devices, such as a keyboard, a pointing device, a scanner, or a networking device such as a switch or router, for example, through a network adapter.

[0065] The computing device 900 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a standard server 920, or multiple times in a group of such servers. It may also be implemented as part of a rack server system 924. In addition, it may be implemented in a personal computer such as a laptop computer 922. Alternatively, components from computing device 900 may be combined with other components in a mobile device (not shown), such as mobile computing device 950. Each of such devices may contain one or more of computing device 900, 950, and an entire system may be made up of multiple computing devices 900, 950 communicating with each other.

[0066] Mobile computing device 950 includes a processor 952, memory 964, an input/output device such as a display 954, a communication interface 976, and a transceiver 968, among other components. The mobile computing device 950 may also be provided with a storage device, such as a microdrive or other device, for additional storage. Each of the components 950, 952, 964, 954, 960, and 968, are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate.

[0067] The processor 952 may execute instructions within the mobile computing device 950, including instructions stored in the memory 964. The processor may be implemented as a chipset of chips that include separate and multiple analog and digital processors. The processor may provide, for example, for coordination of the other components of the mobile computing device 950, such as control of user interfaces, applications run by mobile computing device 950, and wireless communication by mobile computing device 950.

[0068] Processor 952 may communicate with a user through control interface

958 and display interface 956 coupled to a display 954. The display 954 may be, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display) or an OLED (Organic Light Emitting Diode) display, or other appropriate display technology. The display interface 956 may comprise appropriate circuitry for driving the display 954 to present graphical and other information to a user. The control interface 958 may receive commands from a user and convert them for submission to the processor 952.

[0069] In addition, an external interface 962 may be provide in communication with processor 952, so as to enable near area communication of mobile computing device 950 with other devices. External interface 962 may provide, for example, for wired communication in some implementations, or for wireless communication in other implementations, and multiple interfaces may also be used.

[0070] The memory 964 stores information within the mobile computing device

950. The memory 964 may be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. Expansion memory 974 may also be provided and connected to mobile computing device 950 through an expansion interface 972, which may include, for example, a SIMM (Single In Line Memory Module) card interface. Such expansion memory 974 may provide extra storage space for mobile computing device 950, or may also store applications or other information for mobile computing device 950. Specifically, expansion memory 974 may include instructions to carry out or supplement the processes described herein, and may include secure information also. Thus, for example, expansion memory 974 may be provide as a security module for mobile computing device 950, and may be programmed with instructions that permit secure use of mobile computing device 950. In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner.

[0071] The memory may include, for example, flash memory, NVRAM memory, or both, as discussed below. In one implementation, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described herein. The information carrier is a computer- or machine-readable medium, such as the memory 964, expansion memory 974, memory on processor 952, or a propagated signal that may be received, for example, over transceiver 968 or external interface 962.

[0072] Mobile computing device 950 may communicate wirelessly through communication interface 976, which may include digital signal processing circuitry where necessary. Communication interface 976 may provide for communications under various modes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Such communication may occur, for example, through transceiver 968. In addition, short- range communication may occur, such as using a Bluetooth, WiFi, or other such transceiver (not shown). In addition, GPS (Global Positioning System) receiver module 970 may provide additional navigation- and location-related wireless data to mobile computing device 950, which may be used as appropriate by applications running on mobile computing device 950.

[0073] Mobile computing device 950 may also communicate audibly using audio codec 960, which may receive spoken information from a user and convert it to usable digital information. Audio codec 960 may likewise generate audible sound for a user, such as through a speaker, for example, in a handset of mobile computing device 950. Such sound may include sound from voice telephone calls, may include recorded sound (for example, voice messages, music files, etc.) and may also include sound generated by applications operating on mobile computing device 950.

[0074] The mobile computing device 950 may be implemented in a number of different forms, as shown in the figure. For example, it may be implemented as a cellular telephone 980. It may also be implemented as part of a smartphone 982, personal digital assistant, or other similar mobile device.

[0075] Various implementations of the systems and techniques described here may be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device.

[0076] These computer programs (also known as programs, software, software applications, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural, object-oriented programming language, or in assembly/machine language. As used herein, the terms “machine-readable medium” and“computer-readable medium” refer to any computer program product, apparatus, or device (for example, magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term“machine-readable signal” refers to any signal used to provide machine instructions and data to a programmable processor.

[0077] To provide for interaction with a user, the systems and techniques described here may be implemented on a computer having a display device (for example, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user, a keyboard, and a pointing device (for example, a mouse or a trackball) by which the user may provide input to the computer. Other kinds of devices may be used to provide for interaction with a user as well; for example, feedback provided to the user may be any form of sensory feedback (for example, visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

[0078] The systems and techniques described here may be implemented in a computing system that includes a back end component (for example, as a data server), or that includes a middleware component (for example, an application server), or that includes a front end component (for example, a client computer having a graphical user interface or a Web browser through which a user may interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. The components of the system may be interconnected by any form or medium of digital data communication (for example, a communication network). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.

[0079] The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[0080] While this disclosure includes some specifics, these should not be construed as limitations on the scope of the disclosure or of what may be claimed, but rather as descriptions of features of example implementations of the disclosure. Certain features described in this disclosure in the context of separate implementations can also be provided in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be provided in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described herein as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0081] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described herein should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0082] The description is presented to enable any person skilled in the art to make and use the disclosed subject matter, and is provided in the context of one or more particular implementations. Various modifications to the disclosed implementations will be readily apparent to those skilled in the art. The general principles defined in this disclosure may be applied to other implementations and applications without departing from scope of the disclosure. Thus, the present disclosure is not intended to be limited to the described or illustrated implementations, but is to be accorded the widest scope consistent with the principles and features disclosed in this disclosure.

[0083] Thus, particular implementations of the present disclosure have been described. Other implementations are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the disclosure. For example, various forms of the flows shown above may be used, with steps re-ordered, added, or removed. Accordingly, other implementations are within the scope of the following claims.