Mirrored communication devices in carrier networks

In some embodiments, an apparatus includes one or more communication sub-systems; and an identity mirror component in communication with the one or more communication sub-systems. In response to selection, on an another device, of the apparatus from among a plurality of devices, receive, from the another device, carrier user identity information and carrier authentication key information associated with the carrier user identity information. Cause the one or more communication sub-systems to connect to a carrier network using the carrier user identity information and the carrier authentication key information, wherein to connect to the carrier network is conditioned on the another device being disconnected from the carrier network and the another device is to retain the carrier user identity information and the carrier authentication key information in an Internet protocol (IP) multimedia services identity module (ISIM).

FIELD OF THE INVENTION

The present disclosure relates generally to the technical fields of computing and communication, and more particularly, to computing systems for extending use of information associated with Internet protocol (IP) multimedia services identity modules (ISIMs) for communication purposes.

BACKGROUND

Mobile communication devices, such as smart phones, have proliferated in recent years with their capabilities also increasing over time. But as capabilities have increased, so have the size, price, and/or fragility of such mobile communication devices. While a person may wish to have access to his or her smart phone at all times, so that he/she may have ready access to voice calls or texts, for example, carrying around a smart phone may not be feasible and/or unadvised given the activity or environment surrounding the person at a given point in time. For example, if the person is engaging in a sport activity, such as kayaking, a smart phone exposed to such an environment may be damaged, permanently made inoperable, lost, and/or lack a place in which to be safely carried.

Even if a smaller and/or inexpensive device may be capable of communications such as voice calls or texts, a network carrier service account associated with such a device may be required. It may be difficult and/or cumbersome for a person to extend use of his/her network carrier service account associated with a smart phone to another device, such as a smaller and/or inexpensive device.

DETAILED DESCRIPTION

Embodiments of apparatuses and methods related to implementing mirrored communication devices in a carrier network are described. In some embodiments, an apparatus may include one or more communication sub-systems; and an identity mirror component in communication with the one or more communication sub-systems. The identity mirror component may be to, in response to selection, on an another device, of the apparatus from among a plurality of devices, receive, from the another device, carrier user identity information and carrier authentication key information associated with the carrier user identity information; and cause the one or more communication sub-systems to connect to a carrier network using the carrier user identity information and the carrier authentication key information, wherein to connect to the carrier network is conditioned on the another device being disconnected from the carrier network and the another device is to retain the carrier user identity information and the carrier authentication key information in an Internet protocol (IP) multimedia services identity module (ISIM). These and other aspects of the present disclosure will be more fully described below.

The disclosed embodiments may be implemented, in some cases, in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried by or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors. A machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or non-volatile memory, a media disc, or other media device). As used herein, the term “logic” and “module” may refer to, be part of, or include an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs having machine instructions (generated from an assembler and/or a compiler), a combinational logic circuit, and/or other suitable components that provide the described functionality.

FIG. 1depicts a block diagram illustrating a network view of an example system100incorporated with the mirroring technology of the present disclosure, according to some embodiments. System100may include a network102; a server104; a database106; a primary device108; and a secondary device110. Each of the server104, database106, primary device108, and secondary device110may communicate with the network102. Primary device108and second device110may be incorporated with the mirroring technology of the present disclosure to allow secondary device110to communicate assuming an identity associated with primary device108, to be described more fully below.

Network102may comprise one or more wired and/or wireless communications networks. Network102may include one or more network elements (not shown) to physically and/or logically connect computer devices to exchange data with each other. In some embodiments, network102may be the Internet, a wide area network (WAN), a personal area network (PAN), a local area network (LAN), a campus area network (CAN), a metropolitan area network (MAN), a virtual local area network (VLAN), a cellular network, a carrier network, a WiFi network, a WiMax network, and/or the like. Additionally, in some embodiments, network102may be a private, public, and/or secure network, which may be used by a single entity (e.g., a business, school, government agency, household, person, and the like). Although not shown, network102may include, without limitation, servers, databases, switches, routers, gateways, base stations, repeaters, software, firmware, intermediating servers, and/or other components to facilitate communication.

Server104may comprise one or more computers, processors, cellular infrastructure, network infrastructure, back haul infrastructure, or servers to facilitate communication between and among primary device108, secondary device110, and a plurality of other devices (not shown). In some embodiments, server104may communicate with database106(directly or indirectly via network102), primary device108, and/or secondary device110, via network102. In some embodiments, server104may include one or more web servers, one or more application servers, one or more intermediating servers, and the like. In some embodiments, server104may comprise one or more communication components associated with one or more mobile network operators, mobile virtual network operators, wireless service providers, wireless carriers, cellular companies, and the like to facilitate long range wireless data, telephony, and/or Internet communications by the primary and/or secondary device108,110.

Database106may comprise one or more storage devices to store data and/or instructions for use by server104, primary device108, and/or secondary device110. The content of database106may be accessed via network102and/or directly by the server104. The content of database106may be arranged in a structured format to facilitate selective retrieval. In some embodiments, database106may comprise more than one database. In some embodiments, database106may be included within server104.

Primary device108may comprise one or more wired and/or wireless communication computing devices in communication with server104(via network102) and/or secondary device110. Primary device108may also be referred to as a main device, first device, master device, or the like. Primary device108may comprise, without limitation, one or more work stations, personal computers, general purpose computers, laptops, Internet appliances, hand-held devices, wireless devices, Internet of Things (IoT) devices, wearable devices, set top boxes, appliances, vehicles, wired devices, portable or mobile devices, cellular or mobile phones, portable digital assistants (PDAs), smart phones, tablets, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, network PCs, mini-computers, and the like.

In some embodiments, primary device108may include user identity information, user identity authentication information (also referred to as authentication information, authentication key information, key information, and the like), and other information for interfacing/connecting/accessing one or more carrier networks and the like, to be described more fully below. In some embodiments, the user identity information may comprise an international mobile subscriber identity (IMSI) number and the authentication information may comprise the authentication key information associated with the IMSI number. In some embodiments, the user identity information and associated authentication information may comprise parameters included in an Internet protocol (IP) multimedia services identity module (ISIM) for identifying and authenticating a user114to an IP multimedia system or IP multimedia core network subsystem (IMS). In some embodiments, the ISIM may be included in fixed or removable hardware and/or firmware included in the primary device108. For example, the user identity information, authentication information, and other information (which may be contained within the ISIM) may be included in a subscriber identity module (SIM), a SIM card, SIM circuitry, SIM chip, universal integrated circuit card (UICC), UICC card, UICC circuitry, UICC chip, universal subscriber identity module (USIM), USIM circuitry, USIM, chip, or the like.

Primary device108may also include hardware, firmware, circuitry, applications, software, and/or other executable instructions to facilitate various aspects of the techniques described herein. In some embodiments, primary device108may include a communication associated user identity mirror component112(also referred to as an identity mirror component). As described in detail below, the communication associated user identity mirror component112may be configured to securely and easily transfer or mirror user identity information associated with communication over network carrier infrastructure included in the primary device108to a different device, such as the secondary device110, under control of a user, such as the user114, without network carrier involvement and without cloning the user identity and authentication. The component112may also be configured to ensure carrier network access using the user identity information by only one device at a given time (e.g., either primary device108or secondary device110). The component112may be further configured to facilitate use of the user identity information back on the primary device108, under control of the user114. And component112may also provide housekeeping functionalities associated with maintenance of the user identity information in more than one device.

Secondary device110may comprise one or more wired and/or wireless communication computing devices in communication with server104(via network102) and/or primary device108. Secondary device110may also be referred to as a second device, mirror device, slave device, auxiliary device, inexpensive device, robust device, or the like. Secondary device110may comprise, without limitation, one or more devices having fewer functionalities or features, smaller size, smaller form factor, less fragile, lower manufacturing cost, fewer components, and/or lower price than the primary device108; Internet devices; hand-held devices; wireless devices; Internet of Things (IoT) devices; wearable devices; portable or mobile devices; cellular or mobile phones; and the like.

In some embodiments, secondary device110may include hardware, firmware, circuitry, applications, software, and/or other executable instructions to facilitate various aspects of the techniques described herein. In some embodiments, secondary device110may include the communication associated user identity mirror component112, which may be further configured to facilitate receipt of the user identity and authentication information from the primary device108, maintenance of the user identity and authentication information at the secondary device110, use of the user identity and authentication information by the secondary device110, and return of use of the user identity and authentication information to the primary device108.

In some embodiments, primary device108may comprise a smart phone or a tablet that (normally) includes the user identity and associated authentication information in the ISIM, and the secondary device110may comprise a small, robust, and/or inexpensive device configured to mirror the primary device's108user identity and associated authentication information. Each of the primary and secondary devices108,110may be capable of long range wireless communication (e.g., cellular communication) and short range wireless communication (e.g., Bluetooth) similar or compatible with each other. In some embodiments, primary and secondary devices108,110may communicate with each other in association with component112via short range wireless communication; and the primary and secondary devices108,110may be capable of phone calls, texts, or other typical carrier network communications via long range wireless communication.

In some embodiments, the secondary device110may be configured for a specific purpose, such as being waterproof for use in water sports, being small for use in activities such as jogging or running, and the like. Primary and secondary devices108,110may both belong to and/or be under the control of the same user114. Although not shown inFIG. 1, more than one secondary device110may be associated with primary device108, in which the user identity and authentication information included in the primary device108may be transferred to and used by a particular one of the devices from among the primary device108and one or more of the secondary devices110at a particular point in time, in accordance with the user114's direction, thereby allowing the particular secondary device110engage in long range communications “uninterrupted” from the primary device108.

In some embodiments, the component112(or a portion thereof) may be implemented as software comprising one or more instructions to be executed by one or more processors included in respective primary device108and/or secondary device110. In some embodiments, the one or more instructions comprising the component112may be stored and/or executed in a trusted execution environment (TEE) of respective primary device108and/or secondary device110. In some embodiments, the TEE may be included in a dedicated core of respective primary device108and/or secondary device110. In alternative embodiments, the component112(or a portion thereof) may be implemented as firmware or hardware such as, but not limited, to, application specific integrated circuit (ASIC), programmable array logic (PAL), field programmable gate array (FPGA), and the like included in the respective primary device108and/or secondary device110. In some embodiments, component112may be implemented as software in one of the primary device108or secondary device110and implemented as hardware in the other one of the primary device108or secondary device110, or vice versa.

FIG. 2depicts a block diagram of example components included in the secondary device110, according to some embodiments. In some embodiments, secondary device110may include, without limitation, a display202, a processor204, a memory206, user input(s)208, communication sub-system(s)210, and other component(s)212.

In some embodiments, display202may comprise a screen that is smaller than included in the primary device108. Processor204may comprise one or more processors, each having one or more processor cores, configured to execute software included in memory206. If component112is implemented at least in part in software, then memory206may include a portion or the entire software component112, to be executed by the processor204, to perform one or more of the techniques described herein. User input(s)208may comprise one or more physical and/or virtual user input mechanisms (e.g., buttons, switches, physical keypad, virtual keypad, physical keyboard, virtual keyboard, voice control or commands, etc.) appropriate for the form factor constraints of the secondary device110. Communication sub-system(s)210may comprise one or more communication components (e.g., antennas, receivers, transmitters, transceivers, circuitry, controller, etc.) capable of short range communication (e.g., Bluetooth, WiFi) and long range communication (e.g., cellular).

Other component(s)212may comprise one or more components specific to the type of device of the secondary device110. For example, if secondary device110includes radio functionalities, other component(s)212may include radio circuitry and antenna. As another example, if secondary device110provides image capture capabilities, other component(s)212may include a camera. In some embodiments, other component(s)212may comprise hardware configured to implement and/or is associated with the component112. For example, other component(s)212may include the portion or the entirety of component112implemented in an ASIC, PAL, FPGA, circuitry, or the like. As another example, other component(s)212may include a TEE or a dedicated core to protectively execute the software portion of component112. As still another example, other component(s)212may include a memory in which the component112may be stored as one or more instructions to be executed by one or more processors of the secondary device110.

In some embodiments, the user identity information and authentication information included in the primary device108may be mirrored in the secondary device110via the component112that may be maintained in the memory206. Alternatively, other component(s)212may include, for example, SIM, UICC, or USIM circuitry or other dedicated hardware and/or firmware to store and maintain the user identity information and authentication information transmitted from the primary device108. In still other embodiments, information associated with secure handover and use of the user identity-related information between the primary and secondary devices108,110may be stored in any component included in the secondary device110.

FIG. 3depicts an example block diagram illustrating a logical view of the system100, the block diagram illustrating algorithmic structures and data associated with the processes performed by the algorithmic structures, according to some embodiments.FIG. 3illustrates example modules and data that may be included and/or used by the component112to selectively “share” and use network carrier-related user identity information from the primary device108in both the primary and secondary devices108,110, according to some embodiments. The various modules and/or data shown inFIG. 3may be implemented at least partially by hardware at one or more computing devices, such as one or more hardware processors executing instructions stored in one or more memories for performing various functions described herein. The modules and/or data may be communicatively coupled (e.g., via appropriate interfaces) to each other and to various data sources, so as to allow information to be passed between the modules and/or to share and access common data.FIG. 3illustrates only one of many possible arrangements of modules and data configured to perform the functionalities described herein. Other arrangements may include fewer or different modules and/or data, and the division of work between the modules and/or data may vary depending on the arrangement. In some embodiments, modules302-312may comprise one or more software components, programs, applications, or other units of code base or instructions configured to be executed by one or more processors, or may comprise one or more firmware or hardware components or circuitry, included in the primary device108and/or secondary device110. Although modules302-312may be depicted as distinct components inFIG. 3, modules302-312may be implemented as fewer or more components than illustrated.

In some embodiments, device detection module302may be configured to cause the primary device108to detect the presence of nearby devices, such as secondary device110. For each of one or more detected nearby devices indicated as of interest by the user114, initial pairing module304may be configured to facilitate an initial pairing, handshake, configuration, or other preparation between the primary device108and the device of interest (e.g., secondary device110). User interface module306may facilitate presentation and acceptance of one or more user inputs associated with the component112. In some embodiments, initial pairing module304may facilitate generation and sharing of one or more security keys320between the primary device108and the device of interest. The security keys320may be subsequently used to encrypt and decrypt network carrier-related user identity information and other associated information shared from the primary device108to the device of interest. The security keys320between a given pair of the primary device108and device of interest pair may be unique from security keys320for another pair of the primary device108and a device of interest, in some embodiments.

Once the initialization process is complete, user identity transfer module308may be configured to transfer, share, or otherwise provide network carrier-related user identity information included in the primary device108to the device of interest, without, for example, removing the SIM card from the primary device108and inserting into the device of interest. The network carrier-related user identity information may be appropriately encrypted prior to transmission and decrypted after receipt. In some embodiments, the carrier network-related user identity information may comprise network carrier associated user identity information322(e.g., IMSI number) and network carrier associated authentication key information324(e.g., authentication key K1).

Active network control module310may be configured to ensure that only a particular device authorized to use the network carrier-related user identity information associated with the primary device108may be active on the carrier network (e.g., a cellular network) at any given time. For instance, although primary device108retains its SIM card after sharing network carrier-related user identity information with the secondary device110, and accordingly, have user identity information sufficient to connect to the carrier network after sharing, active network control module310may cause primary device108to disconnect from the carrier network prior to the secondary device110connecting to the carrier network. And furthermore, prevent the primary device108from reconnecting with the carrier network until the user114requests handover or control back from the secondary device110to the primary device108.

User identity receipt module312may be configured to facilitate receipt of the network carrier-related user identity information from the primary device108to the secondary device110, and to handle decryption, storage, and other associated functions for the secondary device110to connect to the carrier network.

In some embodiments, all of modules302-312may be included in each of the primary and secondary devices108,110, with one or more of certain of modules302-312being inactive, inert, or inactivated in a particular device. For example, the user identity transfer module308may exist in both the primary and secondary devices108,110but may be active in only the primary device108(because the primary device108may be the device from which the transfer will occur) and inactive in the secondary device110. As another example, the user identity receipt module312may exist in both the primary and secondary devices108,110but may be active in only the secondary device110(because the secondary device110may be device that receives the user identity information) and inactive in the primary device108. Alternatively, less than all of the modules302-312may be included in each of the primary and secondary devices108,110, with only those modules to be used by a particular device being included in the particular device.

FIGS. 4A-4Cdepict example processes that may be performed and/or facilitated by component112to securely share network carrier-related user identity information across more than one mobile device, under control of the user114, and selectively access a carrier network by at most one of the mobile devices, from among a plurality of mobile devices, for telephony, data, and/or Internet communications using the network carrier-associated or related user identity information. Such processes may be accomplished, for example, without removal or cloning of a SIM card associated with the user identity information, without network carrier involvement, nor in violation of network carrier policy for user identity information usage, according to some embodiments.FIG. 5depicts an example timing diagram500relating to the processes ofFIGS. 4A-4C, according to some embodiments.FIGS. 4A-4Care described below in conjunction withFIG. 5. In some embodiments, the communications between the primary device108and secondary device110described below may occur via short range communication protocols such as, but not limited to, Bluetooth, infrared (IR), WiFi, near field communication (NFC), radio frequency identification (RFID), and the like.

FIG. 4Adepicts an example process400to initially configure or pair a particular device (e.g., secondary device110) with the primary device108to subsequently practice mirroring techniques, in accordance with some embodiments. In some embodiments, the initialization process may be initiated by the user114interfacing with the primary device108. For example, the user114may open an app associated with the component112at the primary device108. In response, at a block402, the device detection module302included in the primary device108may detect and authenticate devices that are nearby or in proximity to the primary device108. In some embodiments, detection may occur via a peer-to-peer exchange protocol such as, but not limited to, Bluetooth, IR, WiFi, NFC, or any communication protocol based on device physical proximity to each other. Near range proximity may be used to ensure that the device(s) on which mirroring may take place are all devices likely to be under control of and be physically accessible by the same user114. Such consideration may be further taken into account as initiation progresses and as mirroring may be practiced, as described in detail below. In some embodiments, device detection module302may be configured to facilitate detection of nearby devices using conventional peer-to-peer communication protocols already included in the primary device108. In other words, dedicated detection and authentication hardware, firmware, and/or software components may not be required, and instead, already existing components may be used.

Next, at block404, user interface module306in conjunction with the device detection module302in the primary device108may provide a list of the detected nearby devices to be displayed on a display of the primary device108. In some embodiments, if the initialization process or setup has already occurred for one or more devices of the detected devices, then those device(s) may be omitted from the displayed list since re-initialization may not be required.

In response to the displayed list of detected nearby devices, the user114may select, on the primary device108, a particular device from among the displayed list, such as the secondary device110. At block406, the user interface module306of the primary device108may receive such selection.

At block408, the initial pairing module304included in the primary device108may generate one or more security keys320(also referred to as secure keys, encryption-decryption keys, cryptographic keys, and the like) to be used between the primary device108and the selected particular device (e.g., secondary device110) during the mirroring process. In some embodiments, the generated security keys320may be unique between the particular pair of the primary device108and the selected particular device, and each of the other devices that may be paired with the primary device108may have security keys different from each other. For example, one or more security keys320may comprise one or more symmetric cryptographic keys or the like.

Upon generation of the security keys320, the user interface module306of the primary device108may provide to be displayed on the display of the primary device108, at least a portion of the security keys320or some variation thereof that may permit proper encryption/decryption by the selected particular device, at block410.

In some embodiments, the user114may view the security key(s) or code displayed on the primary device108and enter such security key(s) or code into the selected particular device (e.g., secondary device110). For example, user114may enter the security key(s) or code using the user input(s)208of secondary device110. Having the user114perform the “sharing” of the security key(s) or code between the primary and secondary devices108,110may serve as a security check, since such “sharing” may not be possible if the user114does not have physical access to both devices at the same time. Moreover, by having the user114manually provide the security key(s) from the primary device108to the selected particular device, such security key(s) may be even more secure by not putting them on a network they may be intercepted. In response, the user interface module306included in the secondary device110may receive the entered security key(s) or code at block412.

Next at block414, the secondary device110may save the received security key(s) or code for later use.

Note that throughout the initiation process400, the only device that may be connect to, have access to, and/or be active on the carrier network using the user identity information and authentication key associated with the ISIM included in the primary device108may be primary device108(as shown in a carrier network activity indicator502inFIG. 5).

FIG. 4Bdepicts an example (mirroring) process420to transfer network carrier-related user identity information and associated information to a particular device (e.g., secondary device110) and mirror carrier network access on the particular device in place of the primary device108, according to some embodiments. In some embodiments, blocks422-426may be similar to blocks402-406ofFIG. 4A, except in block424, the displayed list of detected nearby devices may comprise those devices from among the plurality of detected nearby devices for which initialization process or pairing (such as the process400) have previously been completed.

At block428, the user identity transfer module308included in the primary device108may generate one or more codes, such as a random code that may be, for example, four digits, for purposes of confirming that the selected particular device may currently be physically accessible and under control of the same user114also currently controlling the primary device108. The user interface module306in conjunction with the user identity transfer module308included in the primary device108may provide the generated one or more codes to be displayed on the primary device108, at block430.

The user114may view the displayed one or more codes on the primary device108and enter or input the same code(s) into the selected particular device (e.g., via the user input(s)208of the secondary device110). The user interface module306included in the secondary device110may receive the entered code(s) at block432. Next, at block434, the user identity receipt module312included in the secondary device110may generate and transmit a return code in accordance with the received code(s) to the primary device108. In some embodiments, the return code may be the same as the received code(s). In other embodiments, the return code may be any code that may be evaluated by the primary device108to determine whether the return code was generated based on the code transmitted in block430.

Back at the primary device108, at block435, the user identity transfer module308of the primary device108may receive the return code from the secondary device110. Next at block436, the user identity transfer module308of the primary device may determine whether the return code received in block435is a validated or valid code. In some embodiments, when the code generated in block428matches the return code received in block435, a code validation may be deemed to have occurred. In other embodiments, when the return code received in block435satisfies a pre-determined criteria or characteristic or otherwise matches what the primary device108expects, then a code validation may be deemed to have occurred. If there is no code validation (no branch of block436), then process420ends for security reasons because the secondary device110may not be under the user114's control.

If there is code validation (yes branch of block436), then a preliminary or first level security check has been satisfied—that of both the primary and secondary devices108,110being in the user114's possession and the user114being desirous of mirroring to the secondary device110at the current time. Thus, mirroring may continue and the active network control module310included in the primary device108may terminate its connection with the carrier network, if there is currently a session in progress with the carrier network, in block438. Carrier networks may comprise long range wireless networks, cellular networks, mobile networks, radio networks, low power wide area networks (LPWA), and the like.

Next at block439, the user identity transfer module308included in the primary device108may access and/or retrieve at least the user identity information and associated authentication key information from where they normally reside in the primary device108. For example, they may be maintained in the ISIM included in the primary device108.

In some embodiments, the user identity information and associated authentication key information to be encrypted in block440may comprise information copied from the ISIM (or equivalent) included in the primary device108, in which the original user identity information and authentication key information may be information that is registered or activated with the carrier or service provider associated with the carrier network. The user identity information (also referred to as the network carrier associated user identity information322) may comprise at least the IMSI number. The authentication key information (also referred to as the network carrier associated authentication key information324) may comprise at least the authentication key K1.

At block440, the user identity transfer module308included in the primary device108may encrypt the copied information and transmit at least encrypted user identity information and associated authentication key information to the secondary device110. In some embodiments, the information transmitted to the secondary device110may also include additional information such as, but not limited to, one or more of a portion of or whole address book information, call history, text history, and the like. Note that the ISIM (or equivalent) included in the primary card108, and its content, remains as is in the primary card108. Only a (minimal) portion of the network carrier-related information may be mirrored (e.g., IMSI number and authentication key K1) in a particular another device selected by the user114, e.g., the secondary device110, sufficient for network carrier-based communications to continue at the secondary device110in a seamless handed over manner.

In some embodiments, the user identity transfer module308may encrypt the user identity information, associated authentication key information, and other possible information to be transmitted using the particular security key(s)320shared between the primary device108and secondary device110during the initialization or pairing set up performed in the process400.

In response, the user identity receipt module312included in the secondary device110may receive the encrypted user identity information and authentication key information (and other possible information) from the primary device108, at block442. Next, at block444, the user identity receipt module312at the secondary device110may decrypt and save the received information (e.g., in memory206or other component(s)212). Decryption may be performed using the particular security key(s)320received from the primary device108and which was previously stored in the secondary device110.

Now in possession of at least the same user identity information and associated authentication key information normally associated with the primary device108, the active network control module310included in the secondary device110may connect to or start a session with the same carrier network that the primary device108was previously connected with, using the locally stored user identity information and associated authentication key information, at block446. The secondary device110may now carry out carrier network-based communications that were previously carried out on the primary device108, with recipients of such communications unable to detect a change in a phone number or user identifier, for example. For instance, phone calls, texts, and other carrier network-based communications associated with the phone number of primary device108may continue on the secondary device110. Since only the secondary device110is active on the carrier network at this point in time for the particular user identity information, which conforms to the carrier policy, rule, or requirement of only one device at a time using a particular user identity information, the carrier need not be informed of the mirroring. For example, it may merely appear to the carrier network as if the user114physically moved a SIM card from the primary device108to the secondary device110.

With mirroring or handover complete, at block448, the user identity receipt module312included in the secondary device110may generate and transmit an acknowledgement or mirror completion message to the primary device108. Such message may be received by the primary device108, at block450. And in response, the user interface module306of the primary device108may provide a message to be displayed on the primary device108to confirm to the user114that mirroring or handover to the secondary device110is complete.

From this point onward, the user114may use the secondary device110, instead of the primary device108, for carrier network-based communications. Secondary device110may continue in this capacity until the user114requests handover back to the primary device108.FIG. 4Cdepicts an example process460to return carrier network-based communication functionality back to the primary device108in response to user114command, according to some embodiments.

At block462, the user interface module306of the primary device108may receive a command or request from the user114to take back or return control of at least the carrier network-based communications to be carried out from the primary device108. In response, the network identity transfer module308included in the primary device108may transmit a take back control message or relinquish message to the secondary device110, at block464.

The transmitted message of block464may be received by the user identity receipt module312included in the secondary device110, at block466. In response to the received message, the active network control module310included in the secondary device110may cause the secondary device110to disconnect from the carrier network, at block468. In addition, at block470, the user identity receipt module312of the secondary device110may delete the locally stored user identity information, authentication key information, and other possible information previously sent from the primary device108for mirroring purposes. Then at block472, the user identity receipt module312of the secondary device110may generate and transmit an acknowledgement or relinquish complete message to the primary device108.

Upon receipt of the acknowledgement or relinquish complete message sent by the secondary device110at the primary device108, at block474, primary device108may resume carrier network-based communications by (re)connecting to the carrier network (block476) and providing a relinquish or control back complete message to be displayed for the user114(block478).

In some embodiments, the primary device108may be enabled with an override capability so that the carrier network-based communications can occur again from the primary device108even if the secondary device110fails to respond to the take back control/relinquish message. For example, if the secondary device110may be lost, stolen, damaged, battery is too low, out of range, or otherwise unable to respond to the take back control/relinquish message, then the primary device108may reconnect with the carrier network, even if the secondary device110may still be connected to the carrier network. In alternative embodiments, rather than implementing the override capability, the user114may contact the carrier and request the user identity to be disabled or invalidated if the user114knows that the secondary device110continues to be connected to the carrier network but may, for example, be lost to the user114.

After the take back control message transmission at block464, the active network control module310included in the primary device108may wait for a pre-set time period during which a response from the secondary device110may be expected and/or blocks466-472may reasonably be performed. If the pre-set time period has lapsed (yes branch of block465), then process460may proceed to block476to perform an override regardless of whether or not the secondary device110has disconnected from the carrier network. If the pre-set time period has not lapsed (no branch of block465), then the active network control module310in the primary device108may wait in case relinquishment by the secondary device110may be in progress. Connecting the primary device108to the carrier network while the secondary device110may already be connected to the same carrier network using the same user identity information may be a last resort scenario because the carrier or service provider associated with the carrier network may consider more than one device accessing the carrier network using the same user identity information as a cloned device that is unauthorized and cause for the account associated with the user identity information to be disabled.

In this manner, a device, such as the secondary device110, may be configured to serve a specific need at a lower cost, smaller form factor, more robust, and the like than a smart phone or tablet. A user having two or more communication devices may wish to be accessible on different devices at different times using the same carrier network identity. For example, when the user may be kayaking, the user may prefer a communication device that may be waterproof, robust, and potentially hands-free rather than a smart phone. As another example, when the user may be jogging, the user may prefer a communication device that may be small, robust, and potentially waterproof. As still another example, when clubbing, the user may prefer having a communication device that may be small since pockets or bags may be small or non-existent.

In some embodiments, the secondary device110may include features or capabilities such as, but not limited to: small size or form factor; robustness; low cost; voice calls, text, and, optionally, minimal address book functionalities; communication capability for proximate device detection and data transfer/communication with the primary device108; runs mobile operating system supporting apps; cryptography capability for secure data transfer/communication; simple user input mechanism(s) to facilitate hands-free, limited hand mobility (e.g., gloves), etc.; and the like. In some embodiments, component112may also include features to synchronize the address book, call history, text history, or the like upon return of control back to the primary device108; provide location services on the secondary device110; and the like.

The present disclosure provides mirroring carrier network communication functionalities conventionally performed on the primary device108at a device from among a plurality of devices different from the primary device108without, for example, physically transferring the SIM card included in the primary device108to another device, without using another user identity associated with the carrier network (e.g., having two accounts associated with different phone numbers), without cloning the ISIM included in the primary device108, without carrier network involvement, and/or without having more than one device accessing the carrier network using the same user identity information at the same time (which may be blocked by the carrier to avoid fraud or misrouting of calls/texts). The mirroring may be performed under user control and may be initiated only from the primary device108. The transfer or sharing of the user identity information associated with the SIM card at the primary device108may be securely performed and under full control of the user at each stage of the processes. Because of the particular manner in which the user identity information (and associated information) may be transferred and handled by the receiving device, such information may be securely used by the receiving device. And the present disclosure ensures that only one device using a given user identity information may be active on the carrier network at any given time.

FIG. 6illustrates an example computer device600suitable for use to practice aspects of the present disclosure, in accordance with various embodiments. In some embodiments, computer device600may comprise any of the server104, database104, primary device108, and/or secondary device110. As shown, computer device600may include one or more processors602, and system memory604. The processor602may include any type of processors. The processor602may be implemented as an integrated circuit having a single core or multi-cores, e.g., a multi-core microprocessor. The computer device600may include mass storage devices606(such as diskette, hard drive, volatile memory (e.g., DRAM), compact disc read only memory (CD-ROM), digital versatile disk (DVD), flash memory, solid state memory, and so forth). In general, system memory604and/or mass storage devices606may be temporal and/or persistent storage of any type, including, but not limited to, volatile and non-volatile memory, optical, magnetic, and/or solid state mass storage, and so forth. Volatile memory may include, but not be limited to, static and/or dynamic random access memory. Non-volatile memory may include, but not be limited to, electrically erasable programmable read only memory, phase change memory, resistive memory, and so forth.

The computer device600may further include input/output (I/O) devices608(such as a display602), keyboard, cursor control, remote control, gaming controller, image capture device, and so forth and communication interfaces610(such as network interface cards, modems, infrared receivers, radio receivers (e.g., Bluetooth)), and so forth.

The communication interfaces610may include communication chips (not shown) that may be configured to operate the device600in accordance with a Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Evolved HSPA (E-HSPA), or LTE network. The communication chips may also be configured to operate in accordance with Enhanced Data for GSM Evolution (EDGE), GSM EDGE Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN), or Evolved UTRAN (E-UTRAN). The communication chips may be configured to operate in accordance with Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Digital Enhanced Cordless Telecommunications (DECT), Evolution-Data Optimized (EV-DO), derivatives thereof, as well as any other wireless protocols that are designated as 3G, 4G, 5G, and beyond. The communication interfaces610may operate in accordance with other wireless protocols in other embodiments.

The above-described computer device600elements may be coupled to each other via a system bus612, which may represent one or more buses. In the case of multiple buses, they may be bridged by one or more bus bridges (not shown). Each of these elements may perform its conventional functions known in the art. In particular, system memory604and mass storage devices606may be employed to store a working copy and a permanent copy of the programming instructions implementing the operations associated with system100, e.g., operations associated with providing one or more of modules302-312as described above, generally shown as computational logic622. Computational logic622may be implemented by assembler instructions supported by processor(s)602or high-level languages that may be compiled into such instructions. The permanent copy of the programming instructions may be placed into mass storage devices606in the factory, or in the field, through, for example, a distribution medium (not shown), such as a compact disc (CD), or through communication interfaces610(from a distribution server (not shown)).

In some embodiments, one or more of modules302-312, e.g., device detection module302, initial pairing module304, and so forth, may be implemented in hardware integrated with, e.g., communication interface610. In other embodiments, one or more of modules302-312, e.g., user identity module308and so forth, may be implemented in hardware integrated with, e.g., processor602.

FIG. 7illustrates an example non-transitory computer-readable storage media702having instructions configured to practice all or selected ones of the operations associated with the processes described above. As illustrated, non-transitory computer-readable storage medium702may include a number of programming instructions704(e.g., one or more of modules302-312). Programming instructions704may be configured to enable a device, e.g., computer device600, in response to execution of the programming instructions, to perform one or more operations of the processes described in reference toFIGS. 1-5. In alternate embodiments, programming instructions704may be disposed on multiple non-transitory computer-readable storage media702instead. In still other embodiments, programming instructions804may be encoded in transitory computer-readable signals.

Referring again toFIG. 6, the number, capability, and/or capacity of the elements608,610,612may vary, depending on whether computer device600is used as a stationary computing device, such as a set-top box or desktop computer, or a mobile computing device, such as a tablet computing device, laptop computer, game console, an Internet of Things (IoT), or smartphone. Their constitutions are otherwise known, and accordingly will not be further described.

At least one of processors602may be packaged together with memory having computational logic622(or portion thereof) configured to practice aspects of embodiments described in reference toFIGS. 1-5. For example, computational logic622may be configured to include or access one or more of modules302-312. In some embodiments, at least one of the processors602(or portion thereof) may be packaged together with memory having computational logic622configured to practice aspects of processes300,500to form a System in Package (SiP) or a System on Chip (SoC).

In various implementations, the computer device600may comprise a laptop, a netbook, a notebook, an ultrabook, a smartphone, a tablet, an Internet of Things (IoT) device, a personal digital assistant (PDA), an ultra mobile PC, a mobile phone, a desktop computer, a server, a printer, a scanner, a monitor, a set-top box, an entertainment control unit, a digital camera, a portable music player, or a digital video recorder. In further implementations, the computer device600may be any other electronic device that processes data.

Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein.

Examples of the devices, systems, and/or methods of various embodiments are provided below. An embodiment of the devices, systems, and/or methods may include any one or more, and any combination of, the examples described below.

Example 1 is an apparatus including one or more communication sub-systems; and an identity mirror component in communication with the one or more communication sub-systems, wherein the identity mirror component is to: in response to selection, on an another device, of the apparatus from among a plurality of devices, receive, from the another device, carrier user identity information and carrier authentication key information associated with the carrier user identity information; and cause the one or more communication sub-systems to connect to a carrier network using the carrier user identity information and the carrier authentication key information, wherein to connect to the carrier network is conditioned on the another device being disconnected from the carrier network and the another device is to retain the carrier user identity information and the carrier authentication key information in an Internet protocol (IP) multimedia services identity module (ISIM).

Example 2 may include the subject matter of Example 1, and may further include wherein the identity mirror component is to further receive, from a user, a code generated by and displayed on the another device, and to further transmit, to the another device, a return code based on the code.

Example 3 may include the subject matter of any of Examples 1-2, and may further include wherein to receive the carrier user identity information and the carrier authentication key information requires a determination of validation of the return code by the another device.

Example 4 may include the subject matter of any of Examples 1-3, and may further include wherein the one or more communication sub-systems includes a short range wireless communication sub-system to receive the carrier user identity information and the carrier authentication key information and a long range wireless communication sub-system to connect to the carrier network.

Example 5 may include the subject matter of any of Examples 1-4, and may further include wherein the short range wireless communication sub-system includes one or more of Bluetooth, infrared (IR), WiFi, near field communication (NFC), or radio frequency identification (RF ID).

Example 6 may include the subject matter of any of Examples 1-5, and may further include wherein the identity mirror component is to further receive, from the another device, a message to relinquish use of the carrier user identity information, wherein the message to relinquish is initiated by a user interfacing with the another device.

Example 7 may include the subject matter of any of Examples 1-6, and may further include wherein the one or more communication sub-systems, in response to the received message to relinquish, is to disconnect from the carrier network and the identity mirror component is to delete storage of the carrier user identity information and the carrier authentication key information.

Example 8 may include the subject matter of any of Examples 1-7, and may further include wherein the carrier network comprises a long range wireless network, a cellular network, a mobile network, a radio network, or a low power wide area network (LPWA).

Example 9 may include the subject matter of any of Examples 1-8, and may further include wherein the apparatus comprises a mobile communication device having a smaller size, smaller form factor, lower manufacturing cost, fewer components, fewer features, or different features than the another device.

Example 10 may include the subject matter of any of Examples 1-9, and may further include one or more processors, and wherein the identity mirror component comprises one or more instructions to be executed by the one or more processors.

Example 11 may include the subject matter of any of Examples 1-10, and may further include wherein the one or more instructions are one or both of stored and executed in a trusted execution environment (TEE).

Example 12 may include the subject matter of any of Examples 1-11, and may further include wherein the TEE is included in a dedicated core.

Example 13 may include the subject matter of any of Examples 1-12, and may further include wherein the received carrier user identity information and the received carrier authentication key information are in an encrypted format, wherein the identity mirror component is to decrypt the received carrier user identity information and the received carrier authentication key information using one or more security keys previously provided by the another device, wherein the one or more communication sub-systems is to connect to the carrier network using the received carrier user identity information and the received carrier authentication key information decrypted using the one or more security keys.

Example 14 is a computerized method including, in response to a user request to initiate device mirroring, providing a list of nearby devices; receiving a selection by the user of a particular device from the list; in response to the selection by the user, generating and transmitting a first code to the particular device; when a second code received from the particular device is valid, terminating connection with a long range communication network; and sharing at least a portion of the information included in an Internet protocol (IP) multimedia services identity module (ISIM) with the particular device, wherein the particular device is to connect to the long range communication network using the at least a portion of the information.

Example 15 may include the subject matter of Example 14, and may further include wherein transmitting the first code to the particular device comprises transmitting the first code using a short range communication protocol.

Example 16 may include the subject matter of any of Examples 14-15, and may further include wherein the short range communication protocol comprises Bluetooth, infrared (IR), WiFi, near field communication (NFC), or radio frequency identification (RFID).

Example 17 may include the subject matter of any of Examples 14-16, and may further include, prior to providing the list of nearby devices, detecting the nearby devices using a short range communication protocol.

Example 18 may include the subject matter of any of Examples 14-17, and may further include, prior to sharing the at least a portion of the information, retrieving the at least a portion of the information from the ISIM and encrypting the at least a portion of the information, and wherein sharing the at least a portion of the information comprises sharing an encrypted version of the at least a portion of the information.

Example 19 may include the subject matter of any of Examples 14-18, and may further include wherein the list of nearby devices comprises only devices which had previously been provided one or more security keys for device mirroring.

Example 20 may include the subject matter of any of Examples 14-19, and may further include generating the encrypted version of the at least a portion of the information using the one or more security keys.

Example 21 may include the subject matter of any of Examples 14-20, and may further include wherein the one or more security keys comprise symmetric cryptographic keys.

Example 22 may include the subject matter of any of Examples 14-21, and may further include wherein the at least a portion of the information comprises user identity information and authentication key information associated with the user identity information, wherein the user identity information and the authentication key information comprise credentials to connect with the long range communication network.

Example 23 may include the subject matter of any of Examples 14-22, and may further include wherein the long range communication network comprises a wireless network, a cellular network, a mobile network, a radio network, or a low power wide area network (LPWA).

Example 24 may include the subject matter of any of Examples 14-23, and may further include maintaining no connection with the long range communication network while the particular device is connected to the long range communication network.

Example 25 is a first device including a short range communication sub-system and a long range communication sub-system; an Internet protocol (IP) multimedia services identity module (ISIM) storing at least user identity information and authentication key information associated with a long range communication network; and an identity mirror component in communication with the short and long range communication sub-systems and the ISIM, wherein the identity mirror component is to: in response to a request by a user on the first device to have long range communication capabilities at a second device, cause the long range communication sub-system to terminate connection with the long range communication network; and cause the short range communication sub-system to provide at least the user identity information and the authentication key information to the second device upon satisfaction of one or more security checks between the first and second devices, wherein the second device is to connect to the long range communication network using the user identity information and the authentication key information that have been provided.

Example 26 may include the subject matter of Example 25, and may further include wherein the identity mirror component is further to: retrieve the user identity information and the authentication key information from the ISIM; encrypt the retrieved user identity information and authentication key information in accordance with one or more security keys already known between the first and second devices; and wherein to cause the short range communication sub-system to provide at least the user identity information and the authentication key information to the second device comprises to cause the encrypted user identity information and the authentication key information to be provided to the second device.

Example 27 may include the subject matter of any of Examples 25-26, and may further include a subscriber identity module (SIM) card, SIM circuitry, SIM chip, universal integrated circuit card (UICC), UICC circuitry, UICC chip, universal subscriber identity module (USIM), USIM card, USIM circuitry, or USIM chip, and wherein the ISIM is included in one of the SIM card, SIM circuitry, SIM chip, UICC, UICC circuitry, UICC chip, USIM, USIM card, USIM circuity, or USIM chip.

Example 28 may include the subject matter of any of Examples 25-27, and may further include wherein the identity mirror component is further to: in response to another request by the user on the first device, cause the short range communication sub-system to transmit a control message to the second device, wherein the control message comprises a command for the second device to disconnect from the long range communication network and delete the user identity information and the authentication key information on the second device.

Example 29 may include the subject matter of any of Examples 25-28, and may further include wherein the identity mirror component is further to: receive an acknowledgement, from the second device, of disconnection and deletion that have occurred; and in response to receipt of the acknowledgement, cause the long range communication sub-system to reconnect to the long range communication network using the user identity information and the authentication key information.

Example 30 may include the subject matter of any of Examples 25-29, and may further include wherein the identity mirror component is further to: detect a pre-set time period after which the control message is transmitted, in which no response is returned by the second device; and cause the long range communication sub-system to reconnect to the long range communication network using the user identity information and the authentication key information.

Example 31 may include the subject matter of any of Examples 25-30, and may further include wherein the long range communication network comprises a wireless network, a cellular network, a mobile network, a radio network, or a low power wide area network (LPWA).

Example 32 may include the subject matter of any of Examples 25-31, and may further include wherein the short range wireless communication sub-system includes one or more of Bluetooth, infrared (IR), WiFi, near field communication (NFC), or radio frequency identification (RFID) sub-system.

Example 33 is one or more computer-readable storage medium comprising a plurality of instructions to cause an apparatus, in response to execution by one or more processors of the apparatus, to including receive one or more security keys generated by a device; receive, from the device, user identity information and authentication key information associated with the user identity information; and connect to a carrier network using the user identity information and the authentication key information, wherein to connect to the carrier network is conditioned on the device being disconnected from the carrier network and the device is to retain the user identity information and the authentication key information in an Internet protocol (IP) multimedia services identity module (ISIM).

Example 34 may include the subject matter of Example 33, and may further include wherein the plurality of instructions, in response to execution by the one or more processors of the apparatus, further cause to receive, from a user, a code generated by and displayed on the device, and to further transmit, to the device, a return code based on the code.

Example 35 may include the subject matter of any of Examples 33-34, and may further include wherein to receive the user identity information and the authentication key information requires a determination of validation of the return code by the device.

Example 36 may include the subject matter of any of Examples 33-35, and may further include wherein the user identity information and the authentication key information are received via a short range wireless communication protocol, and the carrier network comprises a long range wireless communication network.

Example 37 may include the subject matter of any of Examples 33-36, and may further include wherein the user identity information and the authentication key information are received in an encrypted format, and wherein the plurality of instructions, in response to execution by the one or more processors of the apparatus, further cause to decrypt the user identity information and the authentication key information in the encrypted format using the one or more security keys.