241 to the electrical input or signal 221. The signal converter 246 can, for example, shape the call receiver input 241 and/or set the voltage value of the electrical signal 221 based on the requirements of the memory resource 218. Once the call is received, the signal interface 216 signals the electrical signal 221 over the signal line 219 to the memory resource 218, so that the memory resource is in the on-state. As described in greater detail, when the memory resource 218 is in the on-state, the memory resource 218 is accessible to a network communication channel, represented by IP channel 231. Conversely, when the memory resource 218 is in the off-state, the memory resource 218 is not active, and/or not connected to the IP channel 231.

FIG. 2C illustrates another example of a signal interface for a storage module 210. In an example of FIG. 2C, the storage module 210 implements the signal interface 216 to include a switching mechanism 256 that is triggered to switch states by the call receiver 212, based on the call receiver input 241 (e.g., based on whether the incoming call is received). Prior to the incoming telephone call, the signal interface 216 may be an open switch (as shown in FIG. 2C), and once the telephone call is received by the call receiver 212, the switching mechanism 256 is closed. By way of example, the storage module 210 may use a battery or other power source to provide electrical input to the memory resource 218 over the signal line 219 when the signal interface 216 is a closed switch.

FIG. 2D illustrates another variation of a signal interface for a storage module 210. In an example of FIG. 2D, each storage module 210 implements the signal interface 216 to include a robotic mechanism 266 that includes a seat 268 (e.g., housing element) that moves (e.g., translates, rotates) or otherwise positions (e.g., aligns, orients, etc.) the memory resource 218 and/or signal line 219 with respect to one another. The robotic mechanism 266 can, for example, move the memory resource 218 (as well as the memory microprocessor 222 and IP channel 231) between a seated and unseated position. In the seated position, the memory resource 218 connects to the signal line 219 to receive electrical signal 221. The electrical signal 221 may be provided by various sources, such as by an external power source or battery. Thus, depending on implementation, the electrical signal 221 can be persistent, or intermittent (e.g., when the call receiver 212 receives an incoming call). In such an example, the robotic mechanism 266 may maintain the seat 268 in the unseated position (or detached state), such that an airgap exists between the memory resource 218 and the signal line 219 (from which the electrical signal 221 is provided). Once the telephone call is received, the robotic mechanism 266 moves the seat 268 and the memory resource 218 relative to the signal line 219 into the seated or attached state, so that the memory resource 218 switch receives electrical signal 221.

FIG. 2E illustrates another variation of a signal interface for a storage module 210. In FIG. 2E, each storage module 210 implements the signal interface 216 to include the robotic mechanism 266 connecting the memory resource 218 to the memory microprocessor 222 and/or IP channel 231 when in the seated position. By default, the robotic mechanism 266 may keep the seat 268 unseated or detached, until the call receiver input 241 is received. The call receiver input 241 triggers the robotic mechanism 266 to move the seat 268 from the unseated position (or detached state) to the seated and attached state. As described with an example of FIG. 2D, in one variation, the memory resource 218 may only receive electrical signal 221 when in the seated position. As an addition or variation, FIG. 2E illustrates an example in which the memory resource 218 connects to the memory microprocessor 222 and IP channel 231 only when the seat 268 is in the seated position. This, when in the seated position, the memory resource 218 may be remotely accessible (e.g., for read and write operations) via the IP channel 231 and memory microprocessor 222. As with other examples, the duration of the seated position may be based on the call receiver input 241 (e.g., duration of incoming call). Once termination is signaled, the robotic mechanism 266 may reposition or otherwise move the seat 268 so that the memory resource 218 is not accessible via the IP channel 231.

While some examples of FIG. 2A through 2E provide for access to the memory resource 218 to be terminated based on the call receiver signal 241 (e.g., while incoming call connection is present, or call is terminated), in variations, access to the memory resource 218 may be terminated based on the occurrence of other conditions. In an example, signal interface 216 may cause the switching element (e.g., see FIG. 2C) or robotic mechanism 266 to switch states or positions in response to the occurrence of one or more multiple conditions, such as, for example, (i) a timer condition (e.g., initiated when the call receiver 212 receives incoming call, or terminates incoming call); and/or (ii) user command, provided by, for example, DTMF input or through the IP channel 231.

With further reference to an example of FIG. 2A, the authentication component 214 can include logic to authenticate an incoming call 211. The authentication component 214 may authenticate an incoming call as a trigger signal to activate the memory resource 218 based on, for example, caller information (e.g., telephone number of caller) or other metadata associated with the incoming telephone call. In variations, when the call receiver 212 connects to an incoming telephone call (specifying the corresponding telephone number associated with the storage device), the authentication component 214 uses audio information to authenticate the telephone call as the trigger signal for activating the memory resource 218. By way of example, the audio information may correspond to, for example, a voice signal or pattern, which the authentication component 214 may recognize as belonging to a specific authorized caller. Once recognized, the authentication component 214 may authenticate the incoming telephone call before the signal interface 216 is triggered to switch the memory resource 218 to the on-state.

In variations, the audio information may correspond to a spoken utterance, a dual tone multi-frequency signal (“DTMF”) or another audio signal which can be recognized, or otherwise correlated to an authentication input. If the incoming telephone call is authenticated, the authentication component 214 may generate an electrical signal 221 via the signal interface 216 to activate (or switch to on-state) the memory resource 218. While the memory resource 218 is in the on-state with application of the electrical signal 221, the memory resource 218 may be accessible to read and write operations via the IP channel 231.

In some examples, read and/or write operations may be communicated for memory resource 218 when in the on-state, using a memory microprocessor 222. In an example, the memory microprocessor 222 can process read and/or write operations received through the incoming telephone call 211. For example, the read and/or operation can be communicated through a pattern or sequence of tones of the incoming telephone call 211.

As a variation, the memory microprocessor 222 can receive read and/or write operations and communicate respective responses to the operations through an alternative data channel (e.g., IP channel 231). In such examples, the network connection may thus be active when the memory resource 218 is in the on-state. In some variations, the memory microprocessor 222 may include additional security logic, such as additional authentication logic to authenticate a user who attempts to access the memory resource 218 while it is active.

FIG. 3 illustrates another example of a storage system, according to one or more embodiments. In an example of FIG. 3, a storage system 300 includes a control sub-system 302 and an array 330 of memory resource components 332. In an example of FIG. 3, the array 330 includes a plurality of memory resource components 332, with each memory resource component being associated with a specific account and/or identifier. In examples, the memory resource components 332 of the array 330 are disabled by default. The control sub-system 302 uses an incoming telephone call from a user to enable a corresponding memory resource component 332 associated with the incoming call to be accessible to the user via a data network 303.

In examples, the memory resource components 332 of the array 330 are physically separated from one another. In variations, each memory resource component 332 includes a discrete memory resource, such as described with an example of FIG. 1. In some variations, the memory resource component 332 can include an associated memory access controller that can receive read operation commands from another computing source. In variations, the memory resource component 332 can correspond to a micro-computer. In other examples, the memory resource components 332 can share resources, such as a central processor that accesses discrete memory resources of the respective memory resource components 332.

According to examples, the control sub-system 302 includes a call handling component 310 to receive incoming calls, and a switching component 320 that enables network access to specific memory resource component 332 of the array 330 that are identified by respective incoming calls. As described with some examples, the call handling component 310 can identify a memory resource component 332 of the array 330 from an incoming call initiated by the user device 305. The switching component 320 can implement a switching operation or action to enable the memory resource component 332 identified by the incoming call to be accessible over a data network (e.g., IP network, the Internet).

In some examples, the switching component 320 is implemented as a mechanism that closes an airgap, in order to enable an identified memory resource component 332 to be accessible on a data network. In variations, the switching component 320 is implemented as a mechanism that electrically connects the identified memory resource component 332.

In more detail, the call handling component 310 may be accessible to user devices (or collection of user devices) over a telephony connection. In some examples, the call handling component 310 is accessible over a Public Switch Telephony Network (“PSTN”) 201 to receive telephony calls from a telephony-enabled user device 305. The call handling component 310 can include, for example, a receiver 312 to receive the incoming call. The receiver 312 can initiate one or more processes in response to the incoming call. Additionally, the receiver 312 can convert the incoming call to a digital output that identifies a specific account.

Once the call is authenticated, a memory resource component 332 that is associated with an account of the user can be enabled for access over a data network (e.g., IP network, Internet). In examples, the memory resource component 332 can be switched from an unconnected state to a connected or activated state, where, for example, network connectivity and/or power is provided to the memory resource component 332. Thus, for example, the user can operate a computing device (e.g., the telephony-enabled computing device 305, or another user device) to access the memory resource component 332 over the data network.

In some variations, the receiver 312 includes caller authentication logic 316. The receiver 312 can execute the caller authentication logic 316 to authenticate the caller based on one or more signal characteristics carried by the incoming call signal. The caller authentication logic 316 can include, for example an authentication data store that stores authentication tokens (e.g., number passcode, password, answers to secret questions, etc.) for each user account (e.g., for individual account identifiers). Depending on implementation, the receiver 312 can identify one or more authentication data items and an account identifier from an incoming call, and then perform a comparison operation to compare the authentication item with a stored token of the account identifier. In one implementation, the caller authentication logic 316 processes a sequence of acoustic tones, where the sequence correlates to numbers of a dial pad that a user is interfacing with on the respective user device 305. In another implementation, the receiver 312 implements the caller authentication logic 316 to perform recognition of a user's voice input, to determine, for example, utterances of the user corresponding to a number, password, or secret. Still further, the receiver 312 can implement the caller authentication logic 316 to recognize the user's voice.

Still further, the memory resource component 332 of the array 330 includes a switch interface 335 that can selectively link to at least one of a power resource 336 or a network communication resource 338. The power resource 336 can correspond to a battery, a power inlet, or a power bridge that is shared with other memory resource components 332 of the array 330. In some variations, the network communication resource 338 can correspond to a data port and/or transceiver for receiving network communications over a data network (e.g., Internet Protocol (IP) network, the Internet). In other variations, the network communication resource 338 can include a data port and link for an external gateway to a data network (e.g., the Internet).

The call handling component 310 can respond to an incoming call by generating a trigger signal 325 for the switching component 320. According to examples, the trigger signal 325 (i) identifies the particular memory resource component 332 that is associated with an identifier provided by the incoming call, and (ii) causes the switching component to form a connection 334 (e.g., closes an airgap 339 or electrical switch) to link the memory resource component 332 to the power resource and/or the network communication resource 338 via the switch interface 335 of the memory resource component 332. The connection 334 enables the identified memory resource component 332 to be accessed by the user device 305 over the data network 303. In some variations, the switching component 320 can be implemented as a mechanism that responds to the trigger signal 325 by forming the connection 334 using the switch interface 335 of the identified memory resource component 332 and the corresponding network communication resource 338. The connection 334 enables the user to access the memory resource component 332 over the corresponding data network 303 (e.g., IP network, the Internet, etc.).

As an addition or variation, the switching component 320 can be implemented as a mechanism that responds to the trigger signal 325 by forming the connection 334 to connect the memory resource component 332 to the power resource 336. In such examples, the switching component 320 forms the connection 334 to enable the memory resource component 332 to be accessible (e.g., available for read operations) using a network communication resource of that memory resource component 332.

In some examples, the switching component 320 can include timing logic that maintains the formed connection for the identified memory resource component 332 for a duration of time following, for example, the respective incoming call connection being made or terminated. As an addition or variation, the switching component 320 can communicate with the receiver 312 to detect when the incoming call is received and terminated. The switching component 320 can then maintain the connection that enables access to the identified memory resource component 332 for a duration that correlates to when the incoming call is received and terminated. Still further, in other variations, the switching component 320 can implement logic to form the connection for enabling the identified memory resource component 332 upon the respective incoming call being received. The switching component 320 can terminate the connection for enabling the memory resource component 332 upon the receiver 312 receiving a second call that specifies the identified memory resource component 332.

In some examples, the call handling component 310 can be implemented as a server, or combination of servers, which match an incoming phone number to a port identifier that is assigned to the memory resource component 332. The call handling component 310 can implement the authentication logic 316 to authenticate the caller. Once the caller is authenticated, the call handling component 310 generates the trigger signal 325 for the switching component 320. In one implementation, the switching component 320 responds to the trigger signal 325 by connecting the network communication resource 338 to the port identified by the incoming call. The switching component 320 can, for example, implement an A/B gang relay that links the port corresponding to the identified memory resource component 332 to the network communication resource 338.

FIG. 4 illustrates a method for providing a storage module that is inaccessible until remotely activated using a non-IP network communication channel or link. A method such as described with an example of FIG. 4 may be implemented using, for example, a storage system such as described with an example of FIG. 2A through FIG. 2E. Accordingly, reference may be made to elements of FIG. 2A through FIG. 2E for purpose of illustrating suitable components for performing a step or sub-step being described.

With respect to an example of FIG. 4, storage system 200 receives an incoming telephone call (410). The incoming telephone call may be received over the PSTN network. In variations, the storage system 200 receives an incoming communication over another type of non-IP network. For example, the storage system 200 may directly interface with an analog network or communication medium, which in turn may be accessible to other types of networks (e.g., the Internet).

The system 200 may route the incoming telephone call to one of multiple available storage modules 210, based on the telephone number associated with the incoming telephone call (420). Once the telephone call is routed and the call connection is made, the memory resource 218 of the selected storage module 210 may be switched from an unconnected state to a connected or activated state. In one implementation, the storage module 210 is powered when in the connected or activated state. As an addition or variation, the storage module 210 is accessible over an IP-network (e.g., the Internet) when in the connected or activated state. Conversely, the storage module 210 may be unconnected or without power when the unconnected state.

In one example, the storage module 210 uses the incoming telephone call to supply electrical input to the memory resource 218, thereby causing the memory resource 218 to become available (e.g., in the on-state). For example, the signal interface 216 can draw power from the call receiver 212 when the incoming telephone call is received, and the drawn power can be signaled over the electrical signal line 219 to the memory resource 218.

In another example, the storage module 210 physically manipulates the memory resource to make contact with an electrical input line. For example, the signal interface 216 may correspond to a robotic component that manipulates the orientation of the memory resource 218 relative to the storage module 210, in order to cause physical contact between the electrical input line 219 (or switch thereto) and the memory resource 218.

The electrical input signal causes the memory resource 218 to be accessible for a duration that can be determined by the incoming telephone call (430). When accessible, the memory resource 218 is accessible over an IP channel 231, so that it can be read or written to by a remote terminal. In variations, the duration can be determined from the telephone call, such as from user input (e.g., user enters DTMF command). Still further, the memory resource 218 may be accessible for a duration that is determined by the user input, received from, for example, the IP channel 231. Alternatively, the duration may be determined from a timer and/or predetermined condition.

In some examples, the telephone call to the storage module 210 is terminated, the memory resource 218 is switched to the off-state (440). In one example, the signal interface 216 terminates the electrical input provided over the electrical signal line 219, as the signal interface 216 can no longer draw power from the call receiver 212. In a variation, the signal interface 216 responds to termination of the telephone call by manipulating the memory resource 218 relative to the storage device, to disconnect or force an air gap with an electrical input signal line. In this way, once the telephone call is terminated, the memory resource is switched to the off-state, so that it is no longer accessible over the IP channel 231.

While some examples provide for access to the storage module 210 to be terminated based on the incoming call (e.g., termination of incoming call causes termination of access to the memory resource), in variation, the termination to the memory resource 218 may be provided by other triggers or conditions. For example, access to the memory resource 218 may be terminated when the user makes a second call that is received by the call receiver 212. Alternatively, access to the memory resource 218 may be terminated by a timer condition (e.g., timer initiated when incoming call is received or terminated), after which access to the memory resource 218 is terminated. Still further, access to the memory resource 218 may be terminated in response to the user signaling a command over the IP channel 231 when access is present.

FIG. 5 illustrates a method for managing an array of memory resource components, where each memory resource component of the array is selectively activated (e.g., switched to an on-state or otherwise connected to a network link) through an initial connection made through a non-IP network channel or link. A method such as described with an example of FIG. 5 may be implemented using, for example, a system such as described with an example of FIG. 3. Accordingly, reference may be made to elements of FIG. 3 for purpose of illustrating suitable components for performing a step or sub-step being described.

With respect to an example of FIG. 5, storage system 200 receives an incoming telephone call over the PSTN network, or alternatively, over another type of non-IP network (510). For example, the control sub-system 302 of the storage system 300 directly interfaces with an analog network or other communication medium, which in turn may be accessible to other types of networks (e.g., the Internet). By way of example, the incoming call may be received on a server control sub-system 302 that manages incoming phone calls, separate from the array 330 of memory resource components 332.

Based on information determined from the call, the storage system 200 identifies the memory resource component 332 associated with the caller (520). In some examples, the memory resource component 332 is identified from the phone number that is used to access the storage system 300. As an addition or variation, the storage system 300 can use input from the user (e.g., sequence code, voice authentication) to authenticate that the caller is to have access to the identified memory resource component 332.

According to an example, the control sub-system 302 uses a switching component 320 to activate the memory resource component 332 identified by the incoming call (530). In some examples, the switching component 320 provides closure of an airgap 339 to each of multiple memory resources components 332 of the array 330. For example, each airgap closure may be implemented using an A/B gangway having a physical layer relay that can be programmatically triggered between open and closed states. The switching component 320 can utilize a switch management component (e.g., SWITCHMASTER R6100) to house and manage each switch, so that activation results in closure of the airgap corresponding to a particular memory resource component 332 identified by the incoming call. In some examples, the activation results in the corresponding memory resource component 332 being connected to the network communication resource 338 (e.g., Internet gateway), thereby enabling the memory resource component 332 to be accessible over the data network 303.

The control sub-system 302 may further terminate activation in response to a condition or event (540). For example, the control sub-system 302 may activate a particular memory resource component in response to receipt of a corresponding telephone call (e.g., phone call using phone number of particular memory resource component 332). The activation of the memory resource component 332 may also initiate a timer that deactivates the memory resource component 332 after a designated time period. As an addition or variation, the control sub-system 302 can deactivate the identified memory resource component 332 upon receiving a second phone call for the same phone number of the activated memory resource 332.

CLIENT SYSTEM AND USER DEVICES

FIG. 6 illustrates a client system to access a remote memory resource component of a user account, according to one or more examples. A user of client system 600 may have authorization to access a memory resource component that is maintained by a storage system, such as described with an example of FIG. 3. Accordingly, reference may be made to elements of FIG. 3 for purpose of illustrating suitable components for use in implementing or using functionality and components described with an example of FIG. 6.

In an example, the client system 600 can be implemented by one or multiple computing devices of the user. For example, the client system 600 can be implemented using a telephony-enabled device and a browser-enabled device. In variations, the client system 600 can be implemented by a multi-purpose computing device that is capable of telephony and IP communications. According to examples, the client system 600 can include a programmatic component or interface that is provided for use with a service of storage system 300. For example, the client system 600 can be implemented using a service application that executes on the user's mobile computing devices. In variations, the client system 600 can be implemented by a platform, including applications, plug-ins, or other programmatic components that operate on multiple devices of the user.

According to an example, the client system 600 includes a presentation layer 612, a telephonic component 614, and a service interface component 616. Based on implementation, the components can be implemented through, for example, a service application on a single device, or distributed in whole or in part on multiple devices of a user. In some variations, the client system 600 also includes a framework 608, which implements rules with respect to the operations of the respective components.

In examples, the service interface component 616 can utilize one or more IP networks (e.g., Internet) to establish a communication channel with the storage system 300. In implementation, the service interface component 616 can include or be implemented as a browser component. In variations, the service interface component 616 can be implemented as an interface (e.g., plug-in, extension, etc.) for a local third-party browser of the client system 600. In such examples, the framework 608 can restrict use of the operations of the service interface component 616, such that the service interface component 616 has, or can be operated in a mode which is dedicated for communications with the storage system 300, under rules of framework 608. By way of example, the framework 608 can implement rules that result in functionality such as (i) dedicating the service interface component 616 to access a designated network site or location, as provided by the storage system 300 or other approved source; (ii) implementing encryption for any communication channel or exchange with the storage system 300; (iii) concealing the network address used to access the memory resource component 332 of the user; and/or (iv) restricting access to the service interface component 616 and/or storage system 300 without additional authentication being provided by a user (e.g., login and password credentials from user, biometric input through device of the service interface component 616, etc.).

In examples, the telephonic component 614 can enable telephony communications using a cellular or wireless receiver of a local user device. In variations, telephonic component 614 can be implemented as an interface to a phone application or resource for making a call connection on the computing device. In variations, the telephonic component 614 can interface with a voice service, such as a cellular voice service or a voice over Internet Protocol (VOIP) service. The framework 608 can also implement rules that restrict use or functionality of the telephony component 614. For example, the framework 608 can implement rules to (i) specify a phone number, and/or source for obtaining the phone number that can be automatically dialed through the presentation layer 612, to access the storage network 300; (ii) restricting use of the telephony component 614 to making call connections for only the designated phone number(s); and/or (iii) concealing the phone number that is being called from the user or other source.

In examples, the telephony component 614 can automate or facilitate additional functionality. For example, the telephonic component 614 can receive, or decode a signal from the storage system 300 that identifies a credential or the network address that the service interface component 616 is to use. In variations, the telephonic component 614 can also implement an authentication process using a local login or biometric credential of the user. The telephonic component 614 can also trigger execution of the service interface component 616, such that, for example, the service interface component 616 accesses the memory resource component 332 (or a service of the 300) using the corresponding network address, once a predetermined event is detected through the telephonic component 614 (e.g., the telephonic component 614 terminating initial phone call, the telephonic component 614 providing authentication credentials over call connection, etc.). Still further, the telephonic component 614 can receive or obtain the network address for the service interface component 616.

In variations, the presentation layer 612 can be provided as part of the platform or application(s) that run on device(s) of the client system 600. In an example, the client system 600 provides a call feature that the user can interact with in order to initiate a phone call to the remote site of the storage system 300 (or related service). Accordingly, in some examples, the user selects or otherwise interacts with the call feature provided through the presentation layer 612, without specifying a phone number that is linked to a remote site. In some examples, the service can change the phone number associated with the particular memory resource component 332 of the user. Moreover, in some variations, the phone number can be specific to the account or device(s) of the user. In variations, once the user interaction is received, the telephonic component 614 automatically identifies the phone number from an application memory. For example, the client system 600 can establish a background process that causes, for example, a service application or other program running on the user's mobile device to periodically receive check and/or update the current phone number that is to be used by the particular user. In other variations, the service application or other program of the client system 600 can acquire the phone number as a response to an event or condition, such as the user indicating a desire to access protected data stored with a service that uses or is provided with the storage system 300.

In examples, the client system 600 can initiate a timer based on a condition or event such as the call connection being made or terminated. In some examples, the service interface component 616 is able to use the network address to access the memory resource component 332 during a defined duration that is defined in part by the timer. As an addition or variation, the service interface component 616 can be enabled for a duration that extends until the user operates the telephonic interface 614 to make a second call connection to the service. While the service interface component 616 is enabled, the client system 600 can use the communication channel to access and use the memory resource component.

FIG. 7 is a block diagram that illustrates a computing device upon which examples described herein may be implemented. In one embodiment, a computing device 700 may correspond to a mobile computing device, such as a cellular device that is capable of telephony, messaging, and data services. By way of example, the computing device 700 can correspond to a smartphone (or feature phone) on which an application (“app”) can execute. In variations, the user device 700 can correspond to a tablet, ultraportable computing device, laptop or desktop computer.

The computing device 700 includes a processor 710, memory resources 720, a display device 730 (e.g., such as a touch-sensitive display device), one or more communication sub-systems 740 (including wireless communication sub-systems), one or more sensors 750 (e.g., accelerometer, gyroscope, barometer, altimeter, microphone, camera), and one or more location detection mechanisms (e.g., GPS component) 760. In one example, at least one of the communication sub-systems 740 sends and receives cellular data over both data channels (e.g., IP networks) and voice channels. The communications sub-systems 740 can include a cellular transceiver and one or more short-range wireless transceivers to enable (i) placement of a phone call, and (ii) communication with a remote service that utilizes a storage system such as described with FIG. 1 through FIG. 3.

The memory resources 720 can also store instructions for a service application 725 that can implement a client system for remotely accessing a memory resource component of a user, as described by examples of FIG. 6. In an example, the service application 725 initiates and automates communications with, for example, storage system 300. For example, the processor 710 can be configured with software and/or other logic to perform one or more processes, steps, and other functions described with client system 600 (see FIG. 6). For example, the service application 725 can run to provide telephonic component 614 (see FIG. 6) and service interface component 616 (see FIG. 6). Additionally, the service application 725 can provide presentation layer 612 (see FIG. 6) to enable, for example, programmatic use of a storage service provided with the storage system 300.

When installed and running on the mobile computing device 700, the service application 725 can implement functionality of client system 600, such as described by examples of FIG. 6. In examples, the service application 725 can be associated with an account identifier 711 and/or other credential information 715 that is specific to the user, user account or device (e.g., mobile device phone number).

The service application 725 can include processes for implementing the telephonic component 614 and the service interface component 616, as described with examples of FIG. 6. In implementation, the service application 725 can be configured to enable the service interface component 616 in response to an event and/or condition that is caused by the telephonic process 614, using the phone number to make the call connection. For example, the service application 725 can enable the service interface component 616 in response to one or more events that include the call connection being made, the user providing additional authentication information using the call connection, and/or the user terminating the call connection. In examples, the service interface component 616 is enabled once the user is authenticated during the phone call. For example, the service can communicate the network address to the application, and the service interface component 616 can utilize the address to access the remote service once the user is authenticated during the call connection. The service interface component 616 can establish, for example, an Internet Protocol data communication channel with the service.

In examples, a user can access data stored on the user's memory resource component 332, as hosted by the storage system 300, by launching the service application 725. Once launched, the service application 725 automatically or programmatically (e.g., in response to a single user input) makes a call connection to the storage system 300, using a unique phone number that is specific to the user or account. From the call connection, the user can be provided a duration of time during which the service application 725 can be used to access the memory resource component 332. In variations, the user can utilize a phone number that contacts the 300, and then subsequently provide additional authentication information to enable network access to the memory resource component 332 of the user or account. Once access to the memory resource component 332 is enabled, the service application 725 can be used to access the memory resource component 332. The service application 725 can, for example, implement a browser process to make the network connection with the memory resource component 332, by automatically acquiring and/or using the network address for locating the memory resource component 332 over one or more IP networks.

While examples provide for the client system 600 and/or mobile computing device 700 to be operated by a user, in variations, the user can correspond to a group of users (e.g., enterprise). In such variations, an administrator, for example, can provide the mobile computing device 700 with a set of credentials and/or other identifiers (e.g., phone number for use in contacting the storage system 300). The administrator can also provide the individual user with additional credentials for locally authenticating the user, and/or authenticating the user with the storage system 300. In this way, the memory resource component 332 can be shared amongst multiple users.

In examples, the service application 725 can generate a user interface that indicates a status of a memory resource component 332 that is assigned to the user. The user can interact with the service application 725 to activate the memory resource component 732. For example, the user can initiate a trigger for the telephonic component 614 (see FIG. 6) through the service application 725 to cause the mobile computing device 700 to initiate a telephony call to a storage service that is provided with storage system 300. In variations, the service application 725 can execute to generate DTMF tones (or other analog input) for the storage service. In this way, the service application 725 can identify and/or authenticate the user to the storage service. Once the user is identified and authenticated, the service application 725 can use the service interface component 616 to establish a data connection with the storage service. The data connection can be used to generate content for the presentation layer 612 (see FIG. 6) to, for example, view contents of the memory resource component, such as, for example, a value of a user's current crypto-currency.

In some variations, the operations of the service application 725 following an initial user trigger can be substantially automated. For example, the service application 725 can monitor the telephony connection for an acknowledgement that the memory resource component 332 that is assigned to the user has been activated, then automatically perform operations that establish the connection with the memory resource component 332 over the data network. Likewise, the computing device 700 may execute to monitor for one or more events (e.g., passage of time) that result in termination of the memory resource activation, and/or cause the mobile computing device to generate a command to terminate the activation.

FIG. 8 illustrates a method for operating a computing device of a user to access a service that provides a memory resource component to store sensitive data of the user, according to one or more examples. A method such as described with an example of FIG. 8 may be implemented using, for example, a client system such as described with an example of FIG. 6, or a mobile computing device such as described with an example of FIG. 7. Accordingly, reference may be made to elements of FIG. 6 and FIG. 7 for purpose of illustrating suitable components for performing a step or sub-step being described.

With reference to an example of FIG. 8, a user can operate client system 600 to make a call connection (e.g., place a phone call) with a storage service that is provided in conjunction with storage system 300 (810). In examples, the client system 600 can be implemented using the mobile computing device 700, executing the service application 725. In such examples, the service application 725 can be used to place a phone call to a storage service provided by the storage system 300. using telephony resources of the computing device. For example, the service application 725 may execute to transparently initiate a phone call via phone application and cellular telephony capabilities of the computing device. In variations, the user may place the phone call to store system