Microsoft Technology Licensing, LLC

T-mobile Usa, Inc.

Mathew George

David Matthew Kruse

James T Pinkerton

Phani Ramisetty

Thomas Ewan Jolly

Kyeong Hun An

Roopesh C Battepati

Cristian Asandului

Neal Robert Christiansen

Sarosh Cyrus Havewala

Vladimir Petter

Christian Gregory Allred

Ryan King

Tanmay Roy

Daniel Edward Lovinger

Prashanth Prahalad

Mingdong Shang

Rajsekhar Das

Ahmed Hassan Mohamed

Pradeep Madhavarapu

Senthil Rajaram

Jeffrey Che Fuller

Ramanathan Ganapathy

Sundar Subbarayan

Nandagopal Kirubanandan

Paul R Swan

Yasmin Karimli

Shelby Seward

David Allen Dion

Senthil Kumar Mulluppadi Velusamy

Henry Gabryjelski

Lokesh Srinivas Koppolu

Thomas P Lucht

Poornima Magadevan

Iuliu Rus

Jeffrey Song

Vladimirs Petters

Tom Jolly

Nilesh Ranjan

Nandita Sharma

Michael C Johnson

Diaa E Fathalla

Matthew Stuart Garson

Qibo Zhu

Thomas J Ootjers

MingDong (Gary) Shang

Roopesh Battepati

Thomas E Jolly

Prahalad Prashanth

Some storage systems are configured with VDL (valid data length) type controls that are implemented on a per cluster basis and, in some instances, on a sub-cluster basis, rather than simply a per file basis. In some instances, per-cluster VDL metadata for the storage clusters is stored and referenced at the edge data volume nodes of a distributed network for the storage system rather than, and/or without, storing or synchronizing the per-cluster VDL metadata at a master node that manages the corresponding storage clusters for the different data volume nodes. Sequence controls are also provided and managed by the master node and synchronized with the edge data volume nodes to further control access to data contained in the storage clusters.

Systems and methods for managing data storage cluster synchronization

Examples described herein generally relate to a scalable multi-tier storage system. An entry may be added and/or deleted within the storage system. To delete an entry, the storage system may determine whether the entry corresponds to the file or the directory based on directory metadata, and request deletion of the directory metadata associated with the entry from the directory volume based on determining that the entry corresponds to the directory, and further requesting deletion of the file from a file volume based on a determination that the entry corresponds to the file. To add a file, the storage system may generate directory metadata associated with the entry in the directory volume based on a determination that the entry corresponds to the directory, and may further allocate file metadata in the file volume based on a determination that the entry corresponds to the file.

Scalable multi-tier storage structures and techniques for accessing entries therein

Scale out file system using refs and scale out volume

Intelligent network access technology (NAT) control is described herein. An event associated with a mobile computing device can be detected. Responsive to the event being detected, a subscriber identity module (SIM) associated with the mobile computing device can access location information associated with a location of the mobile computing device. The SIM can access a configuration table storing NAT data provided by a network for controlling which NATs the mobile computing device is permitted to use to access the network. The SIM can determine, based at least in part on the NAT data and the location information, that a requested NAT of the mobile computing device is not a permissible NAT for the mobile computing device in the location and the SIM can cause the mobile computing device to connect to the network via an alternate NAT.

Intelligent network access technology (NAT) selection

Examples described herein generally relate to maintaining a snapshot of a multitier distributed file system. A snapshot directory volume of a directory volume can be created at least in part by copying, to the snapshot directory volume, metadata of the directory volume. Based on a file access request, it can be determined whether the file has not been snapshotted. If not, a snapshot file record of the file, and associated with the snapshot directory volume.

Techniques for snapshotting scalable multitier storage structures

Telecommunication services are received at a user device using an embedded subscriber identity module (eSIM) profile stored on the user device while the user device is located in a first geographical area. A list of preferred remote SIM provisioning (RSP) platforms that provide eSIM profiles specific to a partner MNO of the MNO in a second geographical area is also received from an eSIM management platform of an MNO; The user device is then determined to have moved to a second geographical area based on a geolocation of the user device. Subsequently, an additional eSIM profile specific to the partner MNO of the MNO is downloaded to the user device from an RSP platform of one or more RSP platforms included in the list of preferred RSP platforms.

Rsp platform selection for providing esim profiles to user devices

Systems and methods are disclosed for clients and servers operating in a scaled cluster environment. Efficiencies are introduced to the process of connecting a client to a clustered environment by providing the client with the ability to attempt a connection with multiple servers in parallel. Servers operating the in the clustered environment are also capable of providing persistent storage of file handles and other state information. Ownership of the state information and persistent handles may be transferred between servers, thereby providing clients with the opportunity to move from one server to another while maintaining access to resources in the clustered environment.

SMB2 scaleout

A network terminal, e.g., a smartphone, can retrieve, from a datastore, a cryptographically-signed configuration record including a device identifier of the terminal. The terminal can transmit a request message comprising the configuration record and the device identifier. A network device can verify authenticity of the device identifier and a match between the identifier in the record and the identifier in the message. In response to confirmation of the request by a policy engine, the network device can determine a reply message comprising a cryptographically-signed second configuration record that includes a second device identifier. The terminal can verify that the signature is valid and that the second device identifier matches the device identifier. In response, the terminal can modify data in the datastore according to the second configuration record. The configuration record can lock or unlock the terminal, or determine permitted services or network peers.

Secure updating of telecommunication terminal configuration

Systems and methods discussed herein are directed to handling the identity and authentication of server security certificates on SIMs, and establishing secure channels with cloud servers via a wireless communication network using the security certificates and Public Key Infrastructure (PKI) libraries on SIMs. A mechanism to manage the security certificates on SIMs using an Over-the-Air (OTA) platform of the wireless communication network and certificate authority network elements is provided. Multiple cloud systems and their cloud servers are supported by storing multiple cloud certificates on SIMs and enabling features of a dynamic selection of the appropriate server certificate by the OTA platform for secure communication. Accordingly, electronic devices may be used within the wireless communication network for exchanging data with multiple cloud servers without changing codes/software devices, SIMs, etc.

Providing multiple server security certificates on SIMs of electronic devices

The methods, systems, and computer readable media discussed herein are directed to enabling a fifth generation cellular-wireless access technology (5G) user equipment (UE) to receive 5G service using a fourth generation cellular-wireless access technology (4G) subscriber identity module (SIM). Upon powering on, the 5G UE may determine whether a mobile network operator (MNO) public key file exists in the 4G SIM. Upon determining that the MNO public key file exists in the 4G SIM, the 5G UE may retrieve a MNO public key value from the MNO public key file, read a subscription permanent identifier (SUPI) from the 4G SIM, generate a subscription concealed identifier (SUCI) based on the SUPI and the MNO public key value, send the SUCI to a 5G mobile network for registering the 5G UE, and begin receiving 5G services from the 5G mobile network.

5G service compatible 4G SIM

Techniques for provisioning electronic devices that may not have a local provisioning agent (LPA), such as Internet of Things (IoT) devices, to a mobile network of a mobile network operator (MNO), are discussed herein. The IoT devices and/or the associated embedded subscriber identity module (eSIM) may have one or more device profile templates stored thereon, where individual ones of the device profile templates are associated with a particular MNO. A device provisioning system of an MNO may provision the IoT device in a machine-to-machine (M2M) manner over the air (OTA) by communicating, such as via a radio node, one or more configuration parameters to the IoT device. The IoT device may identify a device profile template associated with the MNO to which the IoT device is to be provisioned and configure that device profile template based at least in part on the configuration parameters received from the device provisioning system.

Over the air provisioning of embedded subscriber identification module devices

A 5G user equipment (UE) can register for 5G services with a telecommunication network in part using a Subscription Concealed Identifier (SUCI), an encrypted version of a subscriber identifier, so that the actual subscriber identifier is not exposed during network registration. Legacy SIMs originally deployed for 4G/LTE and other legacy wireless access technologies store an international mobile subscriber identity (IMSI), but do not store a network public key needed to generate a SUCI. However, a 5G UE can still use a legacy SIM to securely obtain 5G services by encrypting the IMSI from the legacy SIM using a network public key stored in the 5G UE's own memory to generate a SUCI, and then transmitting the generated SUCI to the telecommunication network during network registration. Accordingly, the IMSI on the legacy SIM is not exposed during network registration.

5G device compatibility with legacy SIM

Growing community of inventors

Bellevue, WA, United States of America

Mathew George