Abstract: An extended reality (XR) support system establishes a communicative link between an XR presentation system and a multi-access edge compute (MEC) system operating on a cellular network. The XR support system identifies a parameter associated with a computing task to be performed in connection with an XR experience presented by the XR presentation system. The XR support system also identifies a condition associated with a capability of the XR presentation system or the MEC system to perform the computing task. Based on the identified parameter and the identified condition, the XR support system selects at least one of the XR presentation system or the MEC system to perform the computing task and then directs the selected system to perform the computing task. Corresponding methods and systems are also disclosed.

Abstract: Disclosed is a substrate and associated patterning device. The substrate comprises at least one target arrangement suitable for metrology of a lithographic process, the target arrangement comprising at least one pair of similar target regions which are arranged such that the target arrangement is, or at least the target regions for measurement in a single direction together are, centrosymmetric. A metrology method is also disclosed for measuring the substrate. A metrology method is also disclosed comprising which comprises measuring such a target arrangement and determining a value for a parameter of interest from the scattered radiation, while correcting for distortion of the metrology apparatus used.

Abstract: A system described herein may provide for multiple levels of authentication, such that a User Equipment (“UE”) may receive secure content from an application server, which may include or may be implemented by a multi-access edge computing (“MEC”) system. As described herein, a user associated with a UE may register the UE and/or a particular application with an authentication system and/or the application server. The registration of the UE and/or the application may establish a “trust” relationship between the authentication system and the UE, such that a user-level authentication performed by the UE, such as biometric authentication, may be accepted by the authentication system and/or the application system as an authentication of the user.

Abstract: An extended reality (XR) support system establishes a communicative link between an XR presentation system and a multi-access edge compute (MEC) system operating on a cellular network. The XR support system identifies a parameter associated with a computing task to be performed in connection with an XR experience presented by the XR presentation system. The XR support system also identifies a condition associated with a capability of the XR presentation system or the MEC system to perform the computing task. Based on the identified parameter and the identified condition, the XR support system selects at least one of the XR presentation system or the MEC system to perform the computing task and then directs the selected system to perform the computing task. Corresponding methods and systems are also disclosed.

Abstract: A system described herein may provide for multiple levels of authentication, such that a User Equipment (“UE”) may receive secure content from an application server, which may include or may be implemented by a multi-access edge computing (“MEC”) system. As described herein, a user associated with a UE may register the UE and/or a particular application with an authentication system and/or the application server. The registration of the UE and/or the application may establish a “trust” relationship between the authentication system and the UE, such that a user-level authentication performed by the UE, such as biometric authentication, may be accepted by the authentication system and/or the application system as an authentication of the user.

Abstract: A system described herein may provide for multiple levels of authentication, such that a User Equipment (“UE”) may receive secure content from an application server, which may include or may be implemented by a multi-access edge computing (“MEC”) system. As described herein, a user associated with a UE may register the UE and/or a particular application with an authentication system and/or the application server. The registration of the UE and/or the application may establish a “trust” relationship between the authentication system and the UE, such that a user-level authentication performed by the UE, such as biometric authentication, may be accepted by the authentication system and/or the application system as an authentication of the user.

Abstract: A system described herein may use automated techniques, such as machine learning techniques, to analyze device snapshots from a group of User Equipment (“UEs”), and determine trouble conditions that are experienced by the UEs. The system may identify markers of the trouble conditions based on the snapshots, and may use these markers to predict or identify trouble conditions at other UEs based on snapshots received from the other UEs. Further, once a trouble condition is predicted or identified at the other UEs, the trouble condition may be proactively addressed, without requiring an explicit request from the other UEs to address the trouble condition.

Abstract: A system described herein may use automated techniques, such as machine learning techniques, to analyze device snapshots from a group of User Equipment (“UEs”), and determine trouble conditions that are experienced by the UEs. The system may identify markers of the trouble conditions based on the snapshots, and may use these markers to predict or identify trouble conditions at other UEs based on snapshots received from the other UEs. Further, once a trouble condition is predicted or identified at the other UEs, the trouble condition may be proactively addressed, without requiring an explicit request from the other UEs to address the trouble condition.

Abstract: A device can store a plurality of variants of an application. The device can receive, from a user device that is associated with a first variant of the application, a request for a second variant of the application. The first variant can include a first set of features and include a file size that is different than the second variant. The second variant can include a second set of features. The device can determine a first version identifier of the first variant of the application, and determine that a second version identifier associated with the second variant of the application is different than the first version identifier. The device can provide, to the user device, the second variant of the application to permit the user device to install the second variant of the application.

Abstract: Systems and methods for generating and transmitting multimedia messaging service (MMS) messages are disclosed. In some implementations, a mobile device presents, at a touchscreen, a visual user interface. The visual user interface includes multiple thumbnails and multiple contact blocks. Each thumbnail identifies a file. Each contact block identifies a contact having a messaging address. The mobile device receives, via the touchscreen, a selection of a first thumbnail from the multiple thumbnails. The mobile device receives, via the touchscreen, an indication of dragging the first thumbnail across the visual user interface to a first contact block. The mobile device transmits, responsive to the dragging of the first thumbnail to the first contact block, the file identified in the thumbnail to the messaging address of the contact identified in the first contact block.

Abstract: A user device may request an account type identifier that identifies an account type associated with the user device. The user device may receive the account type identifier based on requesting the account type identifier. The user device may compare the account type identifier and a set of account type identifiers corresponding to a set of user device configurations to be enabled or disabled by the user device based on the account type identifier. The user device may enable a first subset of user device configurations, included in the set of user device configurations that are associated with the account type identifier. The user device may disable a second subset of user device configurations, included in the set of user device configurations that are not associated with the account type identifier.

Abstract: A device may determine a group of dynamic applications to which to provide access. The device may configure a set of dynamic application parameters to provide access to the group of dynamic applications. The set of dynamic application parameters may be configured based on one or more static applications to be provided, by a mobile device, with the group of dynamic applications. The device may provide access to the group of dynamic applications based on configuring the set of dynamic application parameters.

Abstract: A device can store a plurality of variants of an application. The device can receive, from a user device that is associated with a first variant of the application, a request for a second variant of the application. The first variant can include a first set of features and include a file size that is different than the second variant. The second variant can include a second set of features. The device can determine a first version identifier of the first variant of the application, and determine that a second version identifier associated with the second variant of the application is different than the first version identifier. The device can provide, to the user device, the second variant of the application to permit the user device to install the second variant of the application.

Abstract: Systems and methods for generating and transmitting multimedia messaging service (MMS) messages are disclosed. In some implementations, a mobile device presents, at a touchscreen, a visual user interface. The visual user interface includes multiple thumbnails and multiple contact blocks. Each thumbnail identifies a file. Each contact block identifies a contact having a messaging address. The mobile device receives, via the touchscreen, a selection of a first thumbnail from the multiple thumbnails. The mobile device receives, via the touchscreen, an indication of dragging the first thumbnail across the visual user interface to a first contact block. The mobile device transmits, responsive to the dragging of the first thumbnail to the first contact block, the file identified in the thumbnail to the messaging address of the contact identified in the first contact block.

Abstract: A primary application and a secondary application installed on a mobile communication device are both configured to obtain input from a user of the device through an application session of the primary application. The primary application transmits a notification to cause the secondary application to begin execution in the background. The primary application further transmits a request for user interface (UI) information to the secondary application. Based on UI information received from the secondary application, the primary application generates a graphical user interface (GUI) including an interface for receiving user input relating to the secondary application. The generated GUI is displayed on the device in the application session of the primary application, and user input relating to the secondary application is received in the application session of the primary application. The primary application then transmits to the secondary application user input identified as relating to the secondary application.

Abstract: Systems and methods for generating and transmitting multimedia messaging service (MMS) messages are disclosed. In some implementations, a mobile device presents, at a touchscreen, a visual user interface. The visual user interface includes multiple thumbnails and multiple contact blocks. Each thumbnail identifies a file. Each contact block identifies a contact having a messaging address. The mobile device receives, via the touchscreen, a selection of a first thumbnail from the multiple thumbnails. The mobile device receives, via the touchscreen, an indication of dragging the first thumbnail across the visual user interface to a first contact block. The mobile device transmits, responsive to the dragging of the first thumbnail to the first contact block, the file identified in the thumbnail to the messaging address of the contact identified in the first contact block.

Abstract: A smart hook system for a store display including a hook configured to hang smart items having a resistor and a capacitor for display in a store. The hook at least one resistive electrical contact configured to come into electrical circuit contact with the resistor of the smart items hanging on the hook, and at least one capacitive electrical contact configured to come into electrical contact with the capacitor of the smart items that are hanging on hook. The smart hook also includes a processor configured to measure the resistance and capacitance of the smart items that are hanging on hook, and determine a quantity of the smart items hanging on the hook and identity of the smart items hanging on the hook based on the measured resistance and capacitance.

Abstract: A wireless communication device may include logic configured to receive a voice request, wherein the voice request includes a request to access information stored in another wireless communication device, a request for device status information associated with the other wireless communication device, or a request to configure an alert trigger in the other wireless communication device; identify the other wireless communication device; convert the received voice request into a text request; send the text request to the other wireless communication device; and receive a response from the other wireless communication device, wherein the response includes the requested information stored in the wireless communication device, the requested device status information, or an indication that the requested alert trigger has been configured.

Abstract: A wireless communication device may include logic configured to receive a voice request, wherein the voice request includes a request to access information stored in another wireless communication device, a request for device status information associated with the other wireless communication device, or a request to configure an alert trigger in the other wireless communication device; identify the other wireless communication device; convert the received voice request into a text request; send the text request to the other wireless communication device; and receive a response from the other wireless communication device, wherein the response includes the requested information stored in the wireless communication device, the requested device status information, or an indication that the requested alert trigger has been configured.

Abstract: A user device may request an account type identifier that identifies an account type associated with the user device. The user device may receive the account type identifier based on requesting the account type identifier. The user device may compare the account type identifier and a set of account type identifiers corresponding to a set of user device configurations to be enabled or disabled by the user device based on the account type identifier. The user device may enable a first subset of user device configurations, included in the set of user device configurations that are associated with the account type identifier. The user device may disable a second subset of user device configurations, included in the set of user device configurations that are not associated with the account type identifier.