Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: A mobile network operator (MNO) may receive a request to provide an embedded Subscriber Identity Module (eSIM) profile to an embedded Universal Integrated Circuit Card (eUICC) of a user device. The user device is configured to receive telecommunication services from the MNO. Thus, if it is determined that a particular remote SIM provisioning (RSP) platform of a plurality of RSP platforms is able to provide the eSIM profile, the particular RSP platform is directed to provision the eUICC of the user device with the eSIM profile. However, if a condition that affects an ability of the particular RSP platform to provide the eSIM profile is detected, an alternative RSP platform may be directed to provide the eUICC of the user device with the eSIM profile.

Abstract: Provided is a load drive device comprising: a first input terminal for accepting an input of a first input current from a power source; a second input terminal for accepting an input of a second input current from the power source via an external resistor; an output terminal for outputting an output current to a load; a current distribution unit for summing the first input current and second input current at a prescribed distribution ratio and generating the output current and a control unit for controlling the distribution ratio. As one example, it would be appropriate for the control unit to control the distribution ratio according to the difference between a first terminal voltage present in the second input terminal and a second terminal voltage present in the output terminal.

Abstract: 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.

Abstract: A request identifier is employed with various systems and methods in order to enable an application to pause execution during a failure and subsequently resume execution and communication with a storage system once the failure is resolved. An application residing on a node may attempt to access target data on a storage system. The application sends a request to access the target data. The request may be associated with a request identifier that identifies the application. When the storage system experiences a failure, the application receives a failure notification. The application pauses execution as a result of the notification. When the node reestablishes a connection to the storage system, the application resumes execution using the same request identifier. If the resume request is granted, the application is guaranteed that the target data was not modified during the failure.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: An approach for standardizing access to user registries, the approach involving providing a first schema extension to an identity management system and a bridge component to an identity management application wherein the bridge component comprises a second schema extension to the identity management application, receiving a request in a first data format associated with the identity management system, converting the request into a second data format associated with the identity management application and executing the request in the identity management application, receiving a response to the request in the second data format, converting the response into the first data format and returning the response to an end user via the identity management system.

Abstract: 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.

Abstract: Determining a mobile device's location, includes receiving, by the mobile device, a first packet from a first access point and generating a first time-stamp representing the first packet's arrival time; receiving, by the mobile device, a second packet from a second access point and generating a second time-stamp representing the second packet's arrival time; using these to determine the difference between the arrival times of the first and second packet at the mobile device; receiving, by the mobile device, first information representative of the first packet transmission time and second information representative of the second packet transmission time, the first and second information used to find the interval between the transmission of the first and second packets from the first and second access points respectively; determining, by the mobile device, the difference between the flight-times of the first and second packets to the mobile device; and determining, by the mobile device, the difference between t

Abstract: An approach for standardizing access to user registries, the approach involving providing a first schema extension to an identity management system and a bridge component to an identity management application wherein the bridge component comprises a second schema extension to the identity management application, receiving a request in a first data format associated with the identity management system, converting the request into a second data format associated with the identity management application and executing the request in the identity management application, receiving a response to the request in the second data format, converting the response into the first data format and returning the response to an end user via the identity management system.

Abstract: An approach for standardizing access to user registries, the approach involving providing a first schema extension to an identity management system and a bridge component to an identity management application wherein the bridge component comprises a second schema extension to the identity management application, receiving a request in a first data format associated with the identity management system, converting the request into a second data format associated with the identity management application and executing the request in the identity management application, receiving a response to the request in the second data format, converting the response into the first data format and returning the response to an end user via the identity management system.

Abstract: A request identifier is employed with various systems and methods in order to enable an application to pause execution during a failure and subsequently resume execution and communication with a storage system once the failure is resolved. An application residing on a node may attempt to access target data on a storage system. The application sends a request to access the target data. The request may be associated with a request identifier that identifies the application. When the storage system experiences a failure, the application receives a failure notification. The application pauses execution as a result of the notification. When the node reestablishes a connection to the storage system, the application resumes execution using the same request identifier. If the resume request is granted, the application is guaranteed that the target data was not modified during the failure.

Abstract: Improved methods and systems for granular opportunistic locking mechanisms (oplocks) are provided for increasing file caching efficiency. Oplocks can be specified with a combination of three possible granular caching intentions: read, write, and/or handle. An oplock can be specified with an identifier that indicates a client/specific caller to avoid breaking the original oplock due to an incompatibility from other requests of the same client. An atomic oplock flag is added to create operations that allow callers to request an atomic open with an oplock with a given file.

Abstract: A request identifier is employed with various systems and methods in order to enable an application to pause execution during a failure and subsequently resume execution and communication with a storage system once the failure is resolved. An application residing on a node may attempt to access target data on a storage system. The application sends a request to access the target data. The request may be associated with a request identifier that identifies the application. When the storage system experiences a failure, the application receives a failure notification. The application pauses execution as a result of the notification. When the node reestablishes a connection to the storage system, the application resumes execution using the same request identifier. If the resume request is granted, the application is guaranteed that the target data was not modified during the failure.

Abstract: Methods for enhancing and disrupting activity of the aryl hydrocarbon receptor (AHR) and cells having disrupted or enhanced AHR activity. The methods and cells may be used to enhance production of specific cell populations during hemato-endothelial cell or hemato-lymphoid cell development.

Abstract: A system and method for distribution center fulfillment capacity availability tracking is presented herein. A method can include determining an initial value for a fulfillment capacity of each location of one or more locations. The initial value for the fulfillment capacity is an estimation of how many units can be shipped from the location in a particular time period. Thereafter, the fulfillment capacity is adjusted for each order received. The fulfillment capacity is published as an availability to promise. Orders are prioritized using the availability to promise. Orders are then processed for shipment shipped based on the prioritization. Other embodiments are also disclosed herein.