Abstract: A method may include receiving, by at least one network device and from a user device, a registration message including a service identifier and at least one of a network slice identifier or a network slice token. The method may also include determining, based on information included in the registration message, whether the user device is authorized to use a network slice associated with the service identifier. The method may further include setting up a data session to be serviced by the network slice, in response to determining that the user device is authorized to use the network slice.

Abstract: A device may receive a consent address from a user device accessing an application that requires application data associated with consent of a user of the user device, and may provide, to the user device, a consent form associated with the consent address. The device may receive, from the user device, user authentication data provided via the consent form and via a first option or a second option, and may provide, to an application server device associated with the application, a notification indicating that the user authentication data was received. The device may provide, to a cloud service provider web services device, an authorization code and an authorization token based on providing the notification. The cloud service provider web services device may cause the application data to be provided to the application server device based on receiving the authorization code and the authorization token.

Abstract: An application client on a user device receives an internal request from within the application client. The internal request is associated with edge application device(s) hosted by a computing platform. In response to the internal request, the application client obtains an authorization token from the computing platform and initiates an edge discovery request to the computing platform using the authorization token. In response to the edge discovery request, the application client receives connection information of a particular edge application device among the edge application device(s) that is identified for the application client by the computing platform. The application client establishes a connection between the application client and the particular edge application device using the connection information of the particular edge application device.

Abstract: Systems and methods described herein enable user-aware and application-aware dynamic slicing for mobile networks. A network device in a provider network receives a dynamic slice request from a client application. The dynamic slice request includes authorization credentials and a quality of service (QoS) indication for the client application. In response to the dynamic slice request, the network device generates a traffic descriptor value. The traffic descriptor value includes an access token that indicates the QoS authorized for the client application. The network device pushes updated UE Route Selection Policy (URSP) rules to a modem of the UE device, and also separately directs the traffic descriptor value to the client application. The network device receives, from the UE device, a protocol data unit (PDU) session establishment request that includes network slice selection information based on the traffic descriptor value.

Abstract: A device may receive, from a network device, a user equipment (UE) parameter update request notification indicating an update to a UE parameter of a universal subscriber identity module (USIM), and may generate an encrypted UE parameter update request. The device may cause the encrypted UE parameter update request to be provided to the USIM to cause the USIM to update the UE parameter and to generate an encrypted UE parameter update response. The device may receive, from the network device, the encrypted UE parameter update response, and may verify an authenticity of content of the encrypted UE parameter update response based on whether the encrypted UE parameter update response is signed by the USIM. The device may provide, to the network device, a result indicating whether the UE parameter is updated and whether the authenticity of the content of the encrypted UE parameter update response is verified.

Abstract: A device obtains a data structure from a computing device, and divides the data structure into data segments. The device obtains a list of user devices from the computing device and obtains, from one or more network devices, a respective location and a respective reachability of each user device. The device determines, based on the respective location of each user device, a set of user devices connected to a base station. The device determines a communication capability of the base station, and determines, based on the communication capability, a subset of the set of user devices and one or more sets of the data segments. The device sends, based on the respective reachability of each user device of the subset of user devices, the one or more sets of data segments to the subset of user devices via the base station.

Abstract: A device may receive, from a network device, a user equipment (UE) parameter update request notification indicating an update to a UE parameter of a universal subscriber identity module (USIM), and may generate an encrypted UE parameter update request. The device may cause the encrypted UE parameter update request to be provided to the USIM to cause the USIM to update the UE parameter and to generate an encrypted UE parameter update response. The device may receive, from the network device, the encrypted UE parameter update response, and may verify an authenticity of content of the encrypted UE parameter update response based on whether the encrypted UE parameter update response is signed by the USIM. The device may provide, to the network device, a result indicating whether the UE parameter is updated and whether the authenticity of the content of the encrypted UE parameter update response is verified.

Abstract: A device may receive, from a network device, a user equipment (UE) parameter update request notification indicating an update to a UE parameter of a universal subscriber identity module (USIM), and may generate an encrypted UE parameter update request. The device may cause the encrypted UE parameter update request to be provided to the USIM to cause the USIM to update the UE parameter and to generate an encrypted UE parameter update response. The device may receive, from the network device, the encrypted UE parameter update response, and may verify an authenticity of content of the encrypted UE parameter update response based on whether the encrypted UE parameter update response is signed by the USIM. The device may provide, to the network device, a result indicating whether the UE parameter is updated and whether the authenticity of the content of the encrypted UE parameter update response is verified.

Abstract: A device may receive, from a network device, a user equipment (UE) parameter update request notification indicating an update to a UE parameter of a universal subscriber identity module (USIM), and may generate an encrypted UE parameter update request. The device may cause the encrypted UE parameter update request to be provided to the USIM to cause the USIM to update the UE parameter and to generate an encrypted UE parameter update response. The device may receive, from the network device, the encrypted UE parameter update response, and may verify an authenticity of content of the encrypted UE parameter update response based on whether the encrypted UE parameter update response is signed by the USIM. The device may provide, to the network device, a result indicating whether the UE parameter is updated and whether the authenticity of the content of the encrypted UE parameter update response is verified.

Abstract: A device obtains a data structure from a computing device, and divides the data structure into data segments. The device obtains a list of user devices from the computing device and obtains, from one or more network devices, a respective location and a respective reachability of each user device. The device determines, based on the respective location of each user device, a set of user devices connected to a base station. The device determines a communication capability of the base station, and determines, based on the communication capability, a subset of the set of user devices and one or more sets of the data segments. The device sends, based on the respective reachability of each user device of the subset of user devices, the one or more sets of data segments to the subset of user devices via the base station.

Abstract: A device obtains a data structure from a computing device, and divides the data structure into data segments. The device obtains a list of user devices from the computing device and obtains, from one or more network devices, a respective location and a respective reachability of each user device. The device determines, based on the respective location of each user device, a set of user devices connected to a base station. The device determines a communication capability of the base station, and determines, based on the communication capability, a subset of the set of user devices and one or more sets of the data segments. The device sends, based on the respective reachability of each user device of the subset of user devices, the one or more sets of data segments to the subset of user devices via the base station.

Abstract: A device obtains a data structure from a computing device, and divides the data structure into data segments. The device obtains a list of user devices from the computing device and obtains, from one or more network devices, a respective location and a respective reachability of each user device. The device determines, based on the respective location of each user device, a set of user devices connected to a base station. The device determines a communication capability of the base station, and determines, based on the communication capability, a subset of the set of user devices and one or more sets of the data segments. The device sends, based on the respective reachability of each user device of the subset of user devices, the one or more sets of data segments to the subset of user devices via the base station.

Abstract: Techniques described herein may allow for the granting and revoking of temporary access, for User Equipment (“UE”) devices, to a wireless network. Multiple UEs may be registered with a group, where only a limited quantity of UEs in the group may be active at a given time. Once granted access, a UE device may have limits on the access, such as a maximum duration and/or a data limit. When a particular UE device, in a group, requests access to the network, a Group Device Authentication Server (“GDAS”) may determine whether to grant the access, based on how many other UEs in the group (if any) currently have access. The GDAS may also revoke the access once granted (e.g., once the maximum duration has been reached).

Abstract: Techniques described herein may allow for the granting and revoking of temporary access, for User Equipment (“UE”) devices, to a wireless network. Multiple UEs may be registered with a group, where only a limited quantity of UEs in the group may be active at a given time. Once granted access, a UE device may have limits on the access, such as a maximum duration and/or a data limit. When a particular UE device, in a group, requests access to the network, a Group Device Authentication Server (“GDAS”) may determine whether to grant the access, based on how many other UEs in the group (if any) currently have access. The GDAS may also revoke the access once granted (e.g., once the maximum duration has been reached).

Abstract: Techniques described herein may allow for the granting and revoking of temporary access, for User Equipment (“UE”) devices, to a wireless network. Multiple UEs may be registered with a group, where only a limited quantity of UEs in the group may be active at a given time. Once granted access, a UE device may have limits on the access, such as a maximum duration and/or a data limit. When a particular UE device, in a group, requests access to the network, a Group Device Authentication Server (“GDAS”) may determine whether to grant the access, based on how many other UEs in the group (if any) currently have access. The GDAS may also revoke the access once granted (e.g., once the maximum duration has been reached).

Abstract: A device can determine that a sender user equipment connected to a network has been authenticated. The device can cause another device associated with the network to provide configuration information to the sender user equipment after determining that the sender user equipment has been authenticated. The device can receive an RCS message from the sender user equipment after causing the other device to provide the configuration information. The device can determine a capability of a set of receiver user equipment utilizing capability information stored in a data structure. The device can selectively provide the RCS message to the set of receiver user equipment utilizing the non-IMS RCS messaging based on the capability of the set of receiver user equipment, or provide the RCS message to the set of receiver user equipment without utilizing the non-IMS RCS messaging based on the capability of the set of receiver user equipment.

Abstract: Techniques described herein may allow for the granting and revoking of temporary access, for User Equipment (“UE”) devices, to a wireless network. Multiple UEs may be registered with a group, where only a limited quantity of UEs in the group may be active at a given time. Once granted access, a UE device may have limits on the access, such as a maximum duration and/or a data limit. When a particular UE device, in a group, requests access to the network, a Group Device Authentication Server (“GDAS”) may determine whether to grant the access, based on how many other UEs in the group (if any) currently have access. The GDAS may also revoke the access once granted (e.g., once the maximum duration has been reached).

Abstract: A device includes one or more communication interfaces that communicate via at least one link or a network; a device memory; a device processing unit; and a Trusted Execution Environment (TEE) that is secure from the device processing unit and the device memory. The TEE obtains a public encryption key and a private encryption key pair, stores the private encryption key in a secure memory in the Trusted Execution Environment (TEE), and executes a first trusted application, within the TEE, to perform a PKI function using the private encryption key.

Abstract: A mobile terminal is configured to store information associated with accessing an application that requires bootstrapping; recognize an invocation of the application; identify a rule, included in the information, associated with accessing the application; determine whether the rule indicates that a user of the mobile terminal is allowed to access the application; determine whether the mobile terminal supports the bootstrapping; and provide access to the application when the rule indicates that the user of the mobile terminal is allowed to access the application and when the mobile terminal supports the bootstrapping.

Abstract: A device includes one or more communication interfaces that communicate via at least one link or a network; a device memory; a device processing unit; and a Trusted Execution Environment (TEE) that is secure from the device processing unit and the device memory. The TEE obtains a public encryption key and a private encryption key pair, stores the private encryption key in a secure memory in the Trusted Execution Environment (TEE), and executes a first trusted application, within the TEE, to perform a PKI function using the private encryption key.